Bug#857544: groovebasin: Please package groovebasin 1.5.1

[Petter Reinholdtsen]

[Stefan Fritsch 2017-03-12]
> version 1.5.1 has been released on 2015-05-15 while Debian still has
> 1.4.0. 1.5.1 seems to have many bug fixes and nice features.

Yeah, would be great with a more recent version of groovebasin available. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#907785: Get "TypeError: mime.lookup is not a function" and failing to run

[Petter Reinholdtsen]

Package: groovebasin
Version: 1.4.0-1
Severity: important

Dear Maintainer,

I have groovebasing installed on a Freedombox machine running testing,
and tried to run it today.  It is installed since a while back, when
groovebasin was available in testing.

This is the output when running it, and hte program refuse to start:

DEPRECATED use https://github.com/pillarjs/path-to-regexp
/usr/lib/nodejs/groovebasin/node_modules/connect-static/index.js:38
  mime: mime.lookup(relName),
 ^

TypeError: mime.lookup is not a function
at EventEmitter. 
(/usr/lib/nodejs/groovebasin/node_modules/connect-static/index.js:38:18)
at emitThree (events.js:136:13)
at EventEmitter.emit (events.js:217:7)
at /usr/lib/nodejs/findit2/index.js:64:19
at FSReqWrap.oncomplete (fs.js:153:5)

Is there some missing dependency or some other unrelated problem
blocking it form running?

-- 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/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UT$
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages groovebasin depends on:
ii  node-content-disposition  0.5.0-1
ii  node-cookies  0.5.0-1
ii  node-express  4.1.1~dfsg-1
ii  node-findit2  2.2.3-2
ii  node-groove   2.5.0-2+b2
ii  node-keese1.0.4-1
ii  node-lastfm   0.9.2-1
ii  node-leveldown1.5.0+dfsg-1+b2
ii  node-mess 0.1.2-1
ii  node-mime 2.3.1-1
ii  node-mkdirp   0.5.1-1
ii  node-multiparty   4.0.0-1
ii  node-music-library-index  1.2.2-1
ii  node-ncp  0.6.0-1
ii  node-osenv0.1.4-1
ii  node-pend 1.2.0-1
ii  node-rimraf   2.6.2-1
ii  node-semver   5.4.1-1
ii  node-serve-static 1.6.4-2
ii  node-ws   1.1.0+ds1.e6ddaae4-3+b2
ii  node-yauzl2.1.0-1
ii  node-yazl 2.0.2-1
ii  node-ytdl-core0.2.4+dfsg-1
ii  nodejs8.11.2~dfsg-1

groovebasin recommends no packages.

groovebasin suggests no packages.

-- no debconf information

Bug#876675: snapper: Avoid filling up btrfs, as it break the system?

[Petter Reinholdtsen]

[Sunil Mohan Adapa]
> The solution to this part is to trigger a number cleanup after every
> snapshot. The fix is available as part of patch in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880144 . Hence, adding
> patch tag. Please consider accepting the simple patch to fix both bugs.

I suspect you talk about the second patch in bug #880144, ie this:

diff --git a/debian/80snapper b/debian/80snapper
index 0007402..ddf1f8b 100644
--- a/debian/80snapper
+++ b/debian/80snapper
@@ -1,3 +1,3 @@
 # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770938
-  DPkg::Pre-Invoke  { "if [ -x /usr/bin/snapper -a -e 
/etc/snapper/configs/root ]; then rm /var/tmp/snapper-apt || true ; snapper 
create -d apt -c number -t pre -p > /var/tmp/snapper-apt || true ; fi"; };
-  DPkg::Post-Invoke { "if [ -x /usr/bin/snapper -a -e /var/tmp/snapper-apt ]; 
then snapper create -d apt -c number -t post --pre-number=`cat 
/var/tmp/snapper-apt` || true ; fi"; };
+  DPkg::Pre-Invoke  { "if [ -e /etc/default/snapper ]; then . 
/etc/default/snapper; fi; if [ -x /usr/bin/snapper -a ! x$DISABLE_APT_SNAPSHOT 
= 'xyes' -a -e /etc/snapper/configs/root ]; then rm /var/tmp/snapper-apt || 
true ; snapper create -d apt -c number -t pre -p > /var/tmp/snapper-apt || true 
; snapper cleanup number || true ; fi"; };
+  DPkg::Post-Invoke { "if [ -e /etc/default/snapper ]; then . 
/etc/default/snapper; fi; if [ -x /usr/bin/snapper -a ! x$DISABLE_APT_SNAPSHOT 
= 'xyes' -a -e /var/tmp/snapper-apt ]; then snapper create -d apt -c number -t 
post --pre-number=`cat /var/tmp/snapper-apt` || true ; snapper cleanup number 
|| true ; fi"; };

It has already been applied in the snapper git repository.  Did it
help with this issue too?
-- 
Happy hacking
Petter Reinholdtsen

Bug#907784: Figures for the .tex file

[Lu Wang]

Dear Maintainer

Here is the figures for the .tex file. Please decompress the .bz2 file and 
locate the directory in the same one with the .tex file. Thank you.


Best Regards


Lu Wang


pic.tar.bz2
Description: pic.tar.bz2

Bug#907784: texlive-xetex: The output is damaged if one compiles the tex file twice

[Lu Wang]

Package: texlive-xetex
Version: 2018.20180824-1
Severity: normal

Dear Maintainer,

-- Package-specific info:
<#part type="text/plain" disposition=attachment description="Bug script output">
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource.

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file
newfile1.tex

##
other files
figures in texfile.tar.bz2
##
 List of ls-R files

-rw-r--r-- 1 root root 1503 Aug 29 15:25 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Aug 17  2017 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Aug 24 10:11 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Aug 24 10:11 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Mar 30 10:44 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Aug 24 10:11 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Aug 24 10:11 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 3501 Aug 29 15:25 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Aug 17  2017 mktex.cnf
-rw-r--r-- 1 root root 475 Mar 30 10:44 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf
<#/part>

I have a long tex file with ctexbook and xeCJK. I put the "pic1b" directory and 
the tex file in the same directory. If I compile the .tex file twice, with
"xelatex newfile1.tex",
the output PDF file is damaged. If one only compiles the .tex file once,
the output is OK. If I delete the generated .aux file, the output is OK. But 
there are lots of cross references, I need to compile the .tex file twice.

I also try to compile the .tex file with pdflatex with
the "CJKutf8" package and the output is OK.

The bug is very subtle. If I delete arbitrary
equations, figures or Chinese characters, the output is OK. Thus, I cannot
show you a short example. I have tried my best to compress the tex file,
but the output is still 50 pages.

Because the limit of the attachment, I cannot give you my figures. Maybe I can 
sent you the figures in another way.

Best Regards

Lu Wang


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

Kernel: Linux 4.17.0-3-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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages texlive-xetex depends on:
ii  tex-common   6.09
ii  texlive-base 2018.20180824-1
ii  texlive-binaries 2018.20180824.48463-1
ii  texlive-latex-base   2018.20180824-1
ii  texlive-latex-extra  2018.20180824-1
ii  tipa 2:1.3-20

Versions of packages texlive-xetex recommends:
ii  lmodern  2.004.5-5

texlive-xetex suggests no packages.

Versions of packages tex-common depends on:
ii  dpkg  1.19.0.5+b1
ii  ucf   3.0038

Versions of packages tex-common suggests:
pn  debhelper  

Versions of packages texlive-xetex is related to:
ii  tex-common6.09
ii  texlive-binaries  2018.20180824.48463-1

Bug#907783: telnet not parsing telnetrc

[Brad Barnett]

Package: telnet
Version: 0.17-41

After an upgrade from jessie to stretch, and moving my jessie .telnetrc
file into my homedir, I noticed that it was no longer parsed correctly.

# cat .telnetrc
172.16.1.1
mode char

Yet stretch's version of telnet does not switch to character mode.

A bit of digging on Google shows this:

https://bugzilla.redhat.com/show_bug.cgi?id=1505954

I suspect the same bug exists for stretch's .telnetrc parsing.

I couldn't find the package repo or homepage on

https://packages.debian.org/source/stretch/netkit-telnet

or anything central repo 'for all' via Google, so I'm not sure if everyone
is just maintaining everything on their own?

Bug#902567: tasksel: Please remove occurrences of "kdesudo" and coordinate with d-i

[Boyuan Yang]

X-Debbugs-CC: Holger Wansing 

On Fri, 24 Aug 2018 20:08:19 +0200 Holger Wansing  
wrote:
> Hi,
> 
> Boyuan Yang <073p...@gmail.com> wrote:
> > Control: tags -1 + patch
> > Control: forwarded -1 https://salsa.debian.org/installer-team/tasksel/
merge_requests/3
> > X-Debbugs-CC: hwans...@mailbox.org
> > 
> > Dear tasksel maintainers,
> > 
> > I have prepared a patch (Merge Request) on Debian Salsa to solve this bug.
> > Please review it and merge it if you find it acceptable.
> > 
> > The d-i package (user-setup) is no longer using kdesudo thus this 
dependency can
> > be removed safely.
> 
> Anyone objections against this ?
> 
> Holger

Hi Holger,

A week has passed and there seems to be no objections. Besides, package 
kdesudo has long disappeared from unstable / testing so it doesn't make sense 
to continue keeping this entry. Could you please consider committing the fix 
recently?

--
Regards,
Boyuan Yang

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

Bug#907732: maildir-utils: May need versioned depend on libxapian30

[Norbert Preining]

Hi Mark,

> It's a regular testing system, but yeah, partially updated. Maybe it's a

Ah, that explains it.

> library it bumps the >= in the dependency, but in this case the
> unversioned depends on libxapian30 meant the upgrade didn't get pulled
> in. I see the point about complicating backports though, especially if
> xapian's upstream isn't carefully versioning its symbols.

The problem I see is that during build even an old version can be used,
and during run time a version at least as new as the version it was
compiled against.

But AFAIS this cannot be expressed in debian/control, and I would prefer
not introducing a strict dependency.

Are you fine with closing this bug?

Thanks

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#906789: Launchpad Bug#1784103 remove yapf from cosmic (Debian Bug#906789: missing python3-pkg-resources dependency)

[Nicholas D Steeves]

Hi Matthias,

I just wanted to let you know that I'm working with Ana to get yapf
into a good state ASAP.  On a PR on salsa she writes that she plans to
upload the fixes after next Thursday.

I don't know when the final sync from Debian will be, but I hope this
means the yapf and its rdeps won't be cut from Ubuntu 18.10.  P.S. I
maintain Elpy, one of yapf's rdeps, and if any Ubuntu users find bugs
in Elpy then I plan to fix them in Debian without delay.

https://bugs.launchpad.net/ubuntu/+source/elpy/+bug/1784103

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#897642: RFS: gpgme1.0/1.11.1-1~bpo9+1

[Roger Shimizu]

[ Resend for the record with the lists below ]
+ debian-backports@l.d.o
+ pkg-gnupg-maint@l.alioth.d.o

On Sat, Sep 1, 2018 at 11:15 PM, Jacob Adams  wrote:
> control: tag -1 -moreinfo
>
> On Sep 1, 2018, at 04:49, Roger Shimizu  wrote:
>
> control: tag -1 +moreinfo
>
> Dear Jacob,
>
> On Fri, May 4, 2018 at 3:27 AM, Jacob Adams  wrote:
>
> Package: sponsorship-requests
>
> Severity: normal
>
>
>  Dear mentors,
>
>
>  I am looking for a sponsor for my package "gpgme1.0"
>
>
> Thanks for your interest in contribution to debian!
>
>  Changes since the last upload:
>
>
> gpgme1.0 (1.11.1-1~bpo9+1) stretch-backports; urgency=medium
>
>
>  * Rebuild for stretch-backports.
>
>
> -- Jacob Adams   Thu, 26 Apr 2018 13:13:54 -0400
>
>
>
> This package will also require libgpgerror, which you can find here:
>
>
> https://mentors.debian.net/package/libgpg-error
>
>
> https://mentors.debian.net/debian/pool/main/libg/libgpg-error/libgpg-error_1.29-4~bpo9+1.dsc
>
>
> It already has an RFS: #897045
>
>
> I would like to be able to use the latest version of GPGME in my GSoC
>
> 2018 project. In order to do that I would prefer to use a backport as
>
> the PGP Clean Room CD is based off of stretch.
>
>
> I see the project seems already released as beta [1], so maybe there's
> no need to do this backports upload?
>
>
> My project does require a newer version of GPGME than is shipped in stretch.
> However, I didn’t want to wait on the backport, so I’ve been including the
> deb files directly in my build:
> https://salsa.debian.org/tookmund-guest/make-pgp-clean-room/tree/master/resources/config/packages.chroot
>
>
> And what's the benefit for this backports pkg? Any new feature or
> bugfix you're particularly interested in?
>
>
> There has been significant improvement in GPGME’s python binding since
> stretch, and my project relies on these features, such as the new key
> generation function.
>
> It would be nice to be able to pull these packages from backports instead of
> including them directly.

I compiled this pkg under stretch, and meet the following error.


cJSON.c:45:20: fatal error: gpgrt.h: No such file or directory
 # include 
^


I see you updated libgpg-error to 1.29, so I tried to compile with
latest backported sid version, 1.32, and it succeeded.
So I updated D-B on libgpg-error to >= 1.29.

I uploaded this backported pkg to DELAYED/6.
So If you don't like the backports upload, just kindly cancel it.

Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#907747: [Pkg-utopia-maintainers] Bug#907747: network-manager manages interface managed by /etc/network/interfaces

[Michael Biebl]

On 9/2/18 00:43, Michael Biebl wrote:
> On 9/1/18 23:58, Arian Sanusi wrote:
>> I have these interfaces:
>> "bridge": a bridge without any ports connected on start, LXCs connect here. 
>> It's configured in /etc/network/interfaces, and I expect NM not to touch it
>> "mlan0": wifi, not in interfaces, expected to be handled by NM
>> "lo": for completeness sake
>> "eth0": not alway there (USB-interface) expected to be handled by NM.
>>
>> The one thing that's not as expected is that NM does regard "bridge" even 
>> though it should not.
> 
> I still don't undestand: Are you saying that NM tries to manage your
> "bridge" interface while it shouldn't?
> Or are you expecting NM to manager your bridge interface but it does not?
> 
> I don't see anything in the logs which would indicate that NM manages
> your bridge interface, it simply shows, that such a device has been
> detected.

I'm not saying, the /etc/network/interfaces parser couldn't be improved
(it's actually pretty shitty). That said, I'm not sure if your problem
is really caused by that or if it's just a red herring.

Anyway, if want to mark a device as unmanaged by NM, you have more
explicit ways then relying on the eni parser.
E.g. you could create a conf file like this:

# cat /etc/NetworkManager/conf.d/unmanaged.conf
[keyfile]
unmanaged-devices=interface-name:bridge



-- 
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#907399: Logs with systemd-coredump

[Bernhard Übelacker]

Hello,
was not sure what to test also.

At least these steps led me to a crashing cups-browsed:

- Rebuilt cups-browsed and installed to know the issue remains in the rebuilt 
package:
dpkg-buildpackage -b
dpkg -i cups-browsed_1.21.1-1_amd64.deb 
cups-browsed-dbgsym_1.21.1-1_amd64.deb libcupsfilters1_1.21.1-1_amd64.deb

- Start "/usr/sbin/cups-browsed" as regular user in one terminal.

- In another terminal execute "killall -SIGTERM cups-browsed"

- First terminal shows now:
benutzer@debian:~/cups-browsed/try3$ /usr/sbin/cups-browsed
munmap_chunk(): invalid pointer
Abgebrochen (Speicherabzug geschrieben)


Now applied your last patch to the package directory:
wget 
"https://github.com/OpenPrinting/cups-filters/commit/58eaaf20b995de24db5918561315dcbc393281c9.patch;
 -O - | patch -p 1

And build again, and installed.
Now a cups-browsed started and stopped like above does
give no output into the starting terminal.


Kind regards,
Bernhard

Bug#905000: minetest: does not use fullscreen resolution over VGA

[Markus Koschany]

Hi,

On Mon, 30 Jul 2018 11:55:19 +0100 Phil Morrell  wrote:
> Package: minetest
> Version: 0.4.17.1+repack-1~bpo9+1
> Severity: normal
> 
> 
> Hi,
> 
> With my current monitor the maximum resolution is not autodetected, so I
> have configured xrandr to add a new mode and this works perfectly for
> lightdm/xfce.
> 
> Unfortunately, minetest somehow does not find this configuration so
> always shows the titlebar unless I drop the resolution to at most
> 848x480, which is then really blurry. Additionally, the desktop
> resolution is not reverted to the previous setting when quitting.
> --
> Phil Morrell (emorrp1)
> 
> 
> 
> $ xrandr -q
> Screen 0: minimum 320 x 200, current 1600 x 900, maximum 16384 x 16384
> VGA-0 connected 1600x900+0+0 (normal left inverted right x axis y axis) 0mm x 
> 0mm
>1024x768  60.00  
>800x600   60.3256.25  
>848x480   60.00  
>640x480   59.94  
>1600x900  59.95* 
> 
> $ tail -3 ~/.minetest/minetest.conf
> fullscreen = true
> screenW = 1600
> screenH = 900
> 
> $ minetest
> 2018-07-30 11:46:38: WARNING[Main]: Irrlicht: Could not find specified video 
> mode, running windowed.

I'm not sure if minetest is to blame here. This could also be an
underlying issue in the Irrlicht engine which minetest depends on.
Perhaps you can create a new issue at
https://github.com/minetest/minetest. I'm quite sure they are more
likely to help you. This doesn't sound like a Debian issue for me at the
moment and should be better raised upstream.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#907747: [Pkg-utopia-maintainers] Bug#907747: network-manager manages interface managed by /etc/network/interfaces

[Michael Biebl]

On 9/1/18 23:58, Arian Sanusi wrote:
> I have these interfaces:
> "bridge": a bridge without any ports connected on start, LXCs connect here. 
> It's configured in /etc/network/interfaces, and I expect NM not to touch it
> "mlan0": wifi, not in interfaces, expected to be handled by NM
> "lo": for completeness sake
> "eth0": not alway there (USB-interface) expected to be handled by NM.
> 
> The one thing that's not as expected is that NM does regard "bridge" even 
> though it should not.

I still don't undestand: Are you saying that NM tries to manage your
"bridge" interface while it shouldn't?
Or are you expecting NM to manager your bridge interface but it does not?

I don't see anything in the logs which would indicate that NM manages
your bridge interface, it simply shows, that such a device has been
detected.

-- 
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#886146: stretch-pu: package sqlcipher/3.2.0-2+deb9u1

[Philipp Berger]

It now has been more than four months since the last reply by anyone.

PLEASE, is there anything I can to to push this through? It can not be
that hard!


Problem: The package is completely broken and unusable.

History:

  * 2017/11/15: First mention of this issue in my post to
    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863530
  * 2017/12/01: I submitted a patch for the problem to #863530
  * 2018/01/02: This issue was opened to fix the problem against
    release.debian.org

It now has been EIGHT months since the patch was initially submitted.

Bug#907747: [Pkg-utopia-maintainers] Bug#907747: network-manager manages interface managed by /etc/network/interfaces

[Arian Sanusi]

I have these interfaces:
"bridge": a bridge without any ports connected on start, LXCs connect here. 
It's configured in /etc/network/interfaces, and I expect NM not to touch it
"mlan0": wifi, not in interfaces, expected to be handled by NM
"lo": for completeness sake
"eth0": not alway there (USB-interface) expected to be handled by NM.

The one thing that's not as expected is that NM does regard "bridge" even 
though it should not.



signature.asc
Description: OpenPGP digital signature

Bug#799626: Status of beancount

[Dr. Tobias Quathamer]

Hi Nicolas,

are you planning to upload your packaging of beancount soon? From
reading the bug log, I got the impression that you're almost done.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#902900: python3-celery: python3-celery fails to install with Python 3.7

[Hector Oron]

On Tue, Jul 03, 2018 at 10:09:56AM +0200, Antoine R. Dumont wrote:
> Package: python3-celery
> Version: 4.1.0-4
> Severity: serious
> Hello,
> 
> Setting up python3-celery (4.2.0-1) ...
>   File "/usr/lib/python3/dist-packages/celery/backends/redis.py", line 22
> from . import async, base
>   ^
> SyntaxError: invalid syntax
> 
>   File "/usr/lib/python3/dist-packages/celery/backends/rpc.py", line 20
> from .async import AsyncBackendMixin, BaseResultConsumer
>   ^
> SyntaxError: invalid syntax
> 
> dpkg: error processing package python3-celery (--configure):
>  installed python3-celery package post-installation script subprocess
>  returned error exit status 1

I have submitted a backported patch from upstream as MR#1 in salsa:
https://salsa.debian.org/python-team/modules/celery/merge_requests/1

I have been able to build the package and install it, I have not done any 
further testing.

Regards,
 Héctor Orón Martínez


signature.asc
Description: PGP signature

Bug#907399: Logs with systemd-coredump

[Francois Marier]

On 2018-09-01 at 14:44:16, Till Kamppeter wrote:
> Bernhard, thank for the patch. I have applied it now (and also done an
> additional fix for DomainSocket) and committed it to the upstream GIT repo.
> 
> Please test.

Happy to test things. Just to be clear, do you want me to clone the repo,
build the package from master and install/test that?

Francois

-- 
https://fmarier.org/

Bug#907725: xfonts packages are not using the x11 section in practice

[Russ Allbery]

Chris Lamb  writes:

> Hi Russ,

>> […] standardize the other direction and fix packages.debian.org to remove
>> "fonts" from the definition of the x11 section.  I think this also fits the
>> general classification rubric of preferring the narrower, less general
>> section when a package could fall into multiple sections.

> Sounds good to me.
>  
>> (I'm not sure where to report the packages.debian.org bug.  Do you know?)

> Against the "www.debian.org" pseudo-package.

Thanks, filed as #907782.

-- 
Russ Allbery (r...@debian.org)   

Bug#907782: packages.debian.org: section documentation unclear on X11 fonts

[Russ Allbery]

Package: www.debian.org
Severity: minor

Lintian bugs #907725 and #878609 were due to some confusion because the
section documentation at https://packages.debian.org/en/sid/ says both:

X Window System software
  X servers, libraries, fonts, window managers, terminal emulators and
  many related applications.

Fonts
  Font packages.

which leaves ambiguous where X-only fonts should go.  However, in practice,
they're all in the fonts section:

wanderer:~$ grep-aptavail -F Package -s Section -r ^xfonts- | sort | uniq -c
 73 Section: fonts
  1 Section: non-free/fonts
  2 Section: x11

Could you just remove ", fonts" from the description of the x11 section to
avoid the ambiguity?

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

Kernel: Linux 4.17.0-3-amd64 (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/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#907781: mdns-scan: wrong TLD in Homepage field

[itd]

Package: mdns-scan
Version: 0.5-4
Severity: minor

Dear Maintainer,

debian/control contains:
> Homepage: https://github.org/alteholz/mdns-scan
   ^~ 'org' should be 'com'

Thanks!

Regards,
itd



signature.asc
Description: OpenPGP digital signature

Bug#907780: RFP: node-babel-helper-is-nodes-equiv -- babel node equivalence helper function

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: node-babel-helper-is-nodes-equiv
  Version : 0.0.1
  Upstream Author : Amjad Masad
* URL : https://cnpmjs.org/package/babel-helper-is-nodes-equiv
* License : MIT
  Programming Lang: javascript
  Description : babel node equivalence helper function

Hard to imagine why something so small would be its own separate package, but
so it is.  It's a single function, an 'equiv' that takes 2 nodes and compares
them, and some assumed internally shared internal structure.

( this package is a prerequisite for meteor and 2 other node packages )

Bug#905891: libsane1: Please provide a libsane virtual package

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

after upload sane-backends 1.0.27-1 I close this bug.

CU
Jörg

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

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

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


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

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


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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAluK/rUACgkQCfifPIyh
0l38Ag/+NEPduztlWajBhxzUq/caSm0mJ7ZaR2hggfGwyGH+GCGKy0bCUT0wyyyh
3QbUYFwoF9+ZJ27ygA5QqPEIDmddT1H/l7rQPr7Hp7yNov2wX8A5gISeDXipYW3a
8o1d0aKMgEyZP9JpAxe2B3QPC3OIAsqPz9d0NWYCdh0i3liS4Nu63bjDZoiRdGyA
gSnJ1xxLfysEM4Ay5r8W7P0G6HfDRD9Z9k0Phb08g0QRDhkmzkz8wAOQ9XVSRpEs
pFNQ/UjLQCdQCpXTqclDiUHPzLUbkhylBc6TTrwQ3gmD4XsL9uWWSEhFA/VCmmAk
6iv54gWsBOCiEm9DYLjp9vGGQFF91cuQnpKuzKWTH5Yv8x3le5vcKvx6LYgE/fkO
sL0QLnfjh9H0EIfX4tKct7KRB9olLNz4d6UGf/HXumDpDOhYNg7ZSaUPRrGxNaUj
TY29WqQQZvnb256qxUYzQPlY85cFAv59CTY4kgQuHFO5itevJXdozHop0a/Am+nr
cInj/j11sQl5CfUwVRwyptgkjNjDxeQ+2/yyyEDAkIVRIileZlINj0THqq8h/w69
CQRnhKFEaL/ndNKDPi1uxI5MaN7oxppDrKsbnOCVG8qOL3XtmaNyBZYBgIgvb/iz
g1YcAjIBapAQLz7AYJVolNk2GxsLwz8Kduqu5IvnaUlp5Ku8aWU=
=q2E+
-END PGP SIGNATURE-

Bug#879845: sane-backends: please release 1.0.27 to unstable (not only experimental)

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

after upload sane-backends 1.0.27-1 I close this bug.

CU
Jörg

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

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

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


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

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


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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAluK/r8ACgkQCfifPIyh
0l2v1xAAzIEk/pXAH38+xTI+t2mvKVeQ240HJmyMTh5c/e+3B2Uy/VLmu8rvnnTu
oKPmBybiKYy6qAwnfQbGtsS9T22D0RYGO0NGP9wkkRhaFgcieqyKk+WSATDnxXfH
tarCEu6VyiMyzAehaXi9dFcV+NtXsnnb+tYKVHlHFPzNEYM2B0hrey4A9j3/8W+n
l/b3jyrnnytAzW+NjD0ry8jsjSGLVSQE8qLPEysgRu2VXE4bLLfdmuWwIzx9wzh4
IXr6Fd8YhUgNh2U3tkM7bKOJUiRf76Ul7kxW8zFtnJhnf2F+0bPWX6jfw8vggDjP
0t0B/pPnP9ezCHPxd50oE1OoQdQQFSUXyBnnPExSz+cJozoIkaeDRUztrIwqh3RS
DdrbPGv9WKiyWLKuLTupBzQfvgoC3FRWvrnRnN38UpYUrnsRzvXkYODD+pQFxuYF
VzPppTSDTZUhzGrj+ps1wN3UgH60igr6wcomAOrzG8QSTv6JNuvJBTFzq9N+FTJS
M4dVWe76RKQNHRh0tqshaMszju+NY2ni25z7l9eIAB8TW4DqADirOG5NmP9qpvsS
KjBKow3nKN/moEZUP1XsqS++8o5zFIExIAfBJEWpACMPfUfcffQqro4/XWk4KqQD
DCDPipmAs0EPYjbSMO+NPl10JRoBN3muQPNoG3qw4KK/upyRsRQ=
=U21Z
-END PGP SIGNATURE-

Bug#870078: libsane1 breaks all 3rd party scanner drivers

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

after upload sane-backends 1.0.27-1 I close this bug.

CU
Jörg

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

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

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


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

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


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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAluK/sMACgkQCfifPIyh
0l0H6Q//dXpIO/CNjon3+/6ullth8lEYv0QXCmSndA2T4g19DP6hFqhsLZlkyJOh
9RAmvmwAmekC3X4RnMt5BMQWVijGEhMIwEbJJArsfqHzcLoJhXFZhVLKw+UQ2QsI
TNF54al1od3jDpU6SuV9NQmj9xqS7QAD0dV4O4wxTT2NmO/U7lmk1uOdl5R2Ztl/
h5vOqR/u2kPgv16PKcDQSvdJdHFO1Xn6a9wGL1Rl984A8K/zZBcgWcRZf/16jMX3
hyYzO1VeetTx5V1DF9FylduTx1dtiext6/KJ3XE+T8lRx/ydDkKz1oYEAvT5oNY2
j9MZ+YtzTfTgnSh3oOuAc3Awe9Y1GcikejqpG4b+0sxDDhdwnuUKfTXuOKuj+VoI
ZfX3BS49Ce+auNHXNglnNe7SuFqJlNx1viuF4BowqNpc+w+WNpCWifMMDBDToD3E
zlOd0X04Sg9HpYYBD0HG2jU1xIf8D4GNbBh+ZzfjRCm4SRFNV93uDVxQGfNYMXC6
nEbXAFTpKK+wgE5yGNGHNLlC8WmHt+CC2yG46mLl77NBJmj3l4fzK/eMnj5zO8SG
e1XZ0mfFYv9NMIyw2z1bl0T21XU+1KWoNCXDNJzBFZrjC0sbrYU+D4t57PGkk4VV
MrVYqL0ArIUagbfRbmIXgwT6jxUIj8JhdflBaYs4o/hfcO/cgtg=
=UxYR
-END PGP SIGNATURE-

Bug#907779: debian-reference: Wrong example of variable DEB_BUILD_OPTIONS

[Rafael Laboissière]

Source: debian-reference
Version: 2.73
Severity: normal

In section 12.4.2 of the Debian Reference manual, entitled "Debugging 
the Debian package", this example is given:


export DEB_BUILD_OPTIONS=nostrip,noopt

According to the section 4.9.1 of the Debian Policy, entitled 
"debian/rules and DEB_BUILD_OPTIONS":


"This variable can contain several flags to change how a package is 
compiled and built. Each flag must be in the form flag or 
flag=options. If multiple flags are given, they must be separated by 
whitespace."


Please, change the example to:

export DEB_BUILD_OPTIONS="nostrip noopt"

Best,

Rafael Laboissière

Bug#907664: RFS: budgie-desktop/10.4+git20180830.01.f2dbc215fdb-1

[Herbert Fortes]

Hi David Mohammed,

I am giving you budgie-desktop upload permission.



Regards,
Herver

Bug#907778: 389-ds-base: CVE-2018-14624: server crash through modify command with large DN

[Salvatore Bonaccorso]

Source: 389-ds-base
Severity: important
Tags: security upstream

Hi

This bug is to start tracking the issue in the BTS, at the moment
there is not much informtation available. Reference to the CVE is at
https://bugzilla.redhat.com/show_bug.cgi?id=1619450 .

Have you more information on the issue/fix?

Regards,
Salvatore

Bug#897642: RFS: gpgme1.0/1.11.1-1~bpo9+1

[Jacob Adams]

> On Sep 1, 2018, at 12:45, Roger Shimizu  wrote:
> 
> I compiled this pkg under stretch, and meet the following error.
> 
> 
> cJSON.c:45:20: fatal error: gpgrt.h: No such file or directory
> # include 
>^
> 
> 
> I see you updated libgpg-error to 1.29, so I tried to compile with
> latest backported sid version, 1.32, and it succeeded.
> So I updated D-B on libgpg-error to >= 1.29.
> 

Should’ve mentioned that it required a newer version of libgpg-error sorry. 
Thanks for fixing that and updating the backport. 

> I uploaded this backported pkg to DELAYED=6.
> So If you don't like the backports upload, just kindly cancel it.
> 

Thank you!
Looking into why you did a gnupg2 backport I probably should use that too, to 
support newer ECC keys.

Thanks again,
Jacob

Bug#907777: crashing: crashed browser

[Alan Christopher Gormley]

Package: crashing
Version: iceweasel
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

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

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



-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Bug#907381: python-sphinx: missing dependency on python-stemmer

[Dmitry Shachnev]

Control: reassign -1 src:bzr 2.7.0+bzr6622-11
Control: affects -1 - src:bzr
Control: retitle -1 bzr: FTBFS with Sphinx ≥ 1.7.7-1, needs build-dep on 
python-stemmer

Hi Adrian and bzr maintainers,

On Sat, Sep 01, 2018 at 08:05:34PM +0300, Adrian Bunk wrote:
> You already fixed ubuntu-packaging-guide, and this is the only one 
> I found in addition to bzr.
>
> So reassigning this bug to bzr sounds like an option.

Thanks, doing so then.

Note for bzr maintainers: search in non-English Sphinx projects has been
disabled for several releases. Now I finally re-enabled it, but projects
which use non-English language or html_search_language [1] need to depend
on python-stemmer or python3-stemmer.

[1]: 
http://www.sphinx-doc.org/en/master/usage/configuration.html#confval-html_search_language

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#907776: imagemagick: CVE-2018-16323

[Salvatore Bonaccorso]

Source: imagemagick
Version: 8:6.9.10.8+dfsg-1
Severity: important
Tags: patch security upstream

Hi,

The following vulnerability was published for imagemagick.

CVE-2018-16323[0]:
| ReadXBMImage in coders/xbm.c in ImageMagick before 7.0.8-9 leaves data
| uninitialized when processing an XBM file that has a negative pixel
| value. If the affected code is used as a library loaded into a process
| that includes sensitive information, that information sometimes can be
| leaked via the image data.

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-16323
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16323
[1] 
https://github.com/ImageMagick/ImageMagick/commit/216d117f05bff87b9dc4db55a1b1fadb38bcb786

Please adjust the affected versions in the BTS as needed, looking at
the code this at least seem to affect 8:6.9.10.8+dfsg-1 for unstable,
but please double check as I might have missed something.

Regards,
Salvatore

Bug#907725: xfonts packages are not using the x11 section in practice

[Chris Lamb]

Hi Russ,

> […] standardize the other direction and fix packages.debian.org to remove
> "fonts" from the definition of the x11 section.  I think this also fits the
> general classification rubric of preferring the narrower, less general
> section when a package could fall into multiple sections.

Sounds good to me.
 
> (I'm not sure where to report the packages.debian.org bug.  Do you know?)

Against the "www.debian.org" pseudo-package.


Regards,

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

Bug#907775: devscripts: [uscan] fails to create git archive, when download-version is specified

[Benjamin Mesing]

Package: devscripts
Version: 2.18.3
Severity: normal

Hi,

uscan --download-version fails for git repositories, since the clone happens 
"bare" and therfore no
tags are available.
See the log for details:

> uscan --download-version 2.5.1 --rename -v
uscan info: uscan (version 2.18.3) See uscan(1) for help
uscan info: Scan watch files in .
uscan info: Check debian/watch and debian/changelog in .
uscan info: package="javaparser" version="1.0.11-1" (as seen in 
debian/changelog)
uscan info: package="javaparser" version="1.0.11" (no epoch/revision)
uscan info: ./debian/changelog sets package="javaparser" version="1.0.11"
uscan info: Process watch file at: debian/watch
package = javaparser
version = 1.0.11
pkg_dir = .
uscan info: opts: mode=git,repack,compression=xz
uscan info: line: https://github.com/javaparser/javaparser 
refs/tags/javaparser(?:-parent)?-([\d\.]+)
uscan info: Parsing mode=git
uscan info: Parsing repack
uscan info: Parsing compression=xz
uscan info: line: https://github.com/javaparser/javaparser 
refs/tags/javaparser(?:-parent)?-([\d\.]+)
uscan info: Last orig.tar.* tarball version (from debian/changelog): 1.0.11
uscan info: Download the --download-version specified version: 2.5.1
uscan info: Execute: git ls-remote https://github.com/javaparser/javaparser
uscan info: Found the following matching refs:
...
 refs/tags/javaparser-parent-3.1.2 (3.1.2)
 refs/tags/javaparser-parent-3.1.1 (3.1.1)
 refs/tags/javaparser-parent-3.1.0 (3.1.0)
 refs/tags/javaparser-parent-3.0.1 (3.0.1)
 refs/tags/javaparser-parent-3.0.0 (3.0.0)
 refs/tags/javaparser-parent-2.5.1 (2.5.1)
 refs/tags/javaparser-parent-2.5.0 (2.5.0)
 refs/tags/javaparser-parent-2.4.0 (2.4.0)
 refs/tags/javaparser-parent-2.3.0 (2.3.0)
 refs/tags/javaparser-parent-2.2.2 (2.2.2)
   ...
uscan info: Looking at $base = https://github.com/javaparser/javaparser with
$filepattern = refs/tags/javaparser(?:-parent)?-([\d\.]+) found
$newfile = refs/tags/javaparser-parent-2.5.1
$newversion  = 2.5.1 which is newer than
$lastversion = 1.0.11
uscan info: Upstream URL(+tag) to download is identified as
https://github.com/javaparser/javaparser refs/tags/javaparser-parent-2.5.1
uscan info: Filename (filenamemangled) for downloaded file: 
javaparser-2.5.1.tar.xz
uscan: Newest version of javaparser on remote site is 2.5.1, specified download 
version is 2.5.1
uscan info: Downloading upstream package: javaparser-2.5.1.tar.xz
uscan info: Execute: git clone --bare --depth=1 
https://github.com/javaparser/javaparser ../javaparser-temporary.10008.git
Cloning into bare repository '../javaparser-temporary.10008.git'...
remote: Counting objects: 2256, done.
remote: Compressing objects: 100% (1512/1512), done.
remote: Total 2256 (delta 1120), reused 1090 (delta 568), pack-reused 0
Receiving objects: 100% (2256/2256), 7.00 MiB | 3.15 MiB/s, done.
Resolving deltas: 100% (1120/1120), done.
uscan info: Execute: git --git-dir=../javaparser-temporary.10008.git archive 
--format=tar --prefix=javaparser-2.5.1/ 
--output=/home/ben/debian/javaparser/../javaparser-2.5.1.tar 
refs/tags/javaparser-parent-2.5.1
fatal: Not a valid object name
uscan die: git archive failed


Regards
Benjamin



-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
export DEBSIGN_KEYID=FFA943F1

-- 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.16.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages devscripts depends on:
ii  dpkg-dev  1.19.0.5
ii  libc6 2.27-3
ii  libfile-homedir-perl  1.004-1
ii  perl  5.26.2-6
ii  python3   3.6.6-1
ii  sensible-utils0.0.12

Versions of packages devscripts recommends:
ii  apt 1.6.2
ii  at  3.1.20-6
ii  curl7.60.0-2
ii  dctrl-tools 2.24-2+b1
ii  debian-keyring  2018.06.24
ii  dput1.0.2
ii  equivs  2.1.0
ii  fakeroot1.22-2
ii  file1:5.33-3
ii  gnupg   2.2.8-3
ii  gnupg2  2.2.8-3
ii  libdistro-info-perl 0.18
ii  libdpkg-perl1.19.0.5
ii  libencode-locale-perl   1.05-1
ii  libgit-wrapper-perl 0.048-1
ii  liblist-compare-perl0.53-1
ii  liblwp-protocol-https-perl  6.07-2
ii  libsoap-lite-perl   1.27-1
ii  libstring-shellquote-perl   1.04-1
ii  libtry-tiny-perl0.30-1
ii  liburi-perl 1.74-1
ii  

Bug#866699: hexchat sends the on connect server command before nickserv is fully identified

[Mattia Rizzolo]

Control: tag -1 wontfix
Control: close -1

On Fri, Jun 30, 2017 at 09:59:00PM -0600, Arcademan wrote:
> 1. Start up HexChat
> 2. Add a client command like "me %u" to the server on connect tab.
> 3. Restart HexChat - You will notice that some commands that use nickserv fire
> off before fully identifing with the network. A good example would be "join
> #debian" would fire before your hostmask has been properly identified.
> 
> 4. Solution: Suggest there might be a checkbox or setting that would allow
> nickserv to identify then run the on connect command.

I talked a bit with upstream regarding this.  There is and won't be a
definite solution in hexchat itself.  The best solution for this is to
use SASL authentication (which is available on both Freenode and OFTC,
given that you mentioned #debian), followed maybe by client cert auth.
There are other network-specific workaround (e.g. some allow to use the
nickserv password as server password) for some networks, or you could
set irc_join_delay to set a dumb arbitrarly delay before joining.

Thank you for reporting this issue nonetheless.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#907774: [libqt5network5] Requires openssl >= 1.1.1

[Adrien]

Package: libqt5network5
Version: 5.11.1+dfsg-7
Severity: important

--- Please enter the report below this line. ---

Hi,

I'm using owncloud-client, and connection failed with the following log:


[ warning sync.connectionvalidator ]:
QNetworkReply::NetworkError(UnknownNetworkError) "Error while setting
the maximum protocol version" ""


After running gdb, it seems that in
src/network/ssl/qsslcontext_openssl11.cpp on line 151, the
sslContext->sslConfiguration.protocol() is set to QSsl::SecureProtocols,
so minVersion is set to TLS1_VERSION and maxVersion is set
TLS_MAX_VERSION. However, I have currently blocked the upgrading to
openssl1.1.1 so on my system, with openssl1.1.0, the TLS_MAX_VERSION is
defined to TLS1_2_VERSION.

But gdb reports me that maxVersion is set to 0x0304, which is the value
of TLS_MAX_VERSION in openssl1.1.1 as it as an alias for TLS1_3_VERSION.


Thus, I think that you should require a version of openssl greater or
equal than 1.1.1 to avoid those issues.


Thanks for maintaining the package,

Adrien


--- System information. ---
Architecture:
Kernel: Linux 4.17.0-3-amd64

Debian Release: buster/sid
500 unstable-debug debug.mirrors.debian.org
500 unstable ftp.fr.debian.org
500 testing download.jitsi.org
1 experimental ftp.fr.debian.org

--- Package information. ---
Depends (Version) | Installed
=-+-
libssl1.1 | 1.1.0h-4
libc6 (>= 2.14) | 2.27-5
libqt5core5a (>= 5.11.0~rc1) | 5.11.1+dfsg-7
libqt5dbus5 (>= 5.0.2) | 5.11.1+dfsg-7
libstdc++6 (>= 5) | 8.2.0-4
qtbase-abi-5-11-0 |
zlib1g (>= 1:1.1.4) | 1:1.2.11.dfsg-1


Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#897426: Unix pathnames being misinterpreted as commands

[Mattia Rizzolo]

Hi Matthew,

On Thu, May 03, 2018 at 10:39:45AM +0200, Mattia Rizzolo wrote:
> The concept sounds good to me, could you please try to get this uptream?
> 
> The github project is https://github.com/hexchat/hexchat

Looking if you had the time to submit a PR upstream for this :)

I privately pointed this bug to the upstream developer, and it looked
like he would be in favor of this change!

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#302584: [installation-guide] Problems with the hppa installer-manual

[Dean Ware]

UNSUBSCRIBE

On Fri, Aug 31, 2018 at 10:00 PM Holger Wansing 
wrote:

> Control: tags -1 + wontfix
>
>
> > I just took a little time to review the sarge installation manual
> > at http://www.debian.org/releases/testing/hppa/ .
> > It's a big improvement over the woody one!
> > I do have some nits I'd like fixed before release:
>
>
> Since hppa is not a release architecture for years, I'm tagging this bug
> as wont-fix
>
>
> --
> Holger Wansing 
> PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
>
>

Bug#897072: RFS: btrfs-progs/4.17-1~bpo9+1

[Nicholas D Steeves]

retitle 897072 RFS: btrfs-progs/4.17-1~bpo9+1
stop

Hi Gianfranco!

I noticed that this RFS bug has been open since 4.15.1-2~bpo9+1
(April).  Are there any problems with the package I haven't addressed?
Upstream has recently started grumbling again about ancient Debian
packages ;-)

Future changes: Dmitri doesn't want to allow no-change backports
anymore (See #900314), so after this upload I will merge the changelog
entries for unstable in between the ones for stretch-backports.

See below for updated links:

On Fri, Apr 27, 2018 at 09:16:05PM -0400, Nicholas D Steeves wrote:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my continued support of backported
> "btrfs-progs".  There was an RC bug against btrfs-progs for some time,
> which is why it didn't migrate to testing, and why I was unable to
> provide an updated backport.
> 
> Hi Gianfranco!
> 
> I've CCed you as usual, because you usually take care of sponsoring
> this package.  Thank you very much for your continued support :-)
> 
> Package name: btrfs-progs
> Version : 4.15.1-2~bpo9+1
> Upstream Author : linux-bt...@vger.kernel.org
> URL : http://btrfs.wiki.kernel.org/
> License : GPL-2
> Section : admin
> 
> It builds these binary packages:
> 
>   btrfs-progs - Checksumming Copy on Write Filesystem utilities
>   btrfs-progs-udeb - Checksumming Copy on Write Filesystem utilities (udeb) 
> (udeb)
>   btrfs-tools - transitional dummy package
> 
> To access further information about this package, please visit the following 
> URL:
> 
>   https://mentors.debian.net/package/btrfs-progs
> 
> Alternatively, one can download the package with dget using this command:
> 
> dget -x 
> https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.15.1-2~bpo9+1.dsc
> 

dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.17-1~bpo9+1.dsc

> More information about btrfs-progs can be obtained from 
> http://btrfs.wiki.kernel.org/
> 
> Changes since the last upload:

btrfs-progs (4.17-1~bpo9+1) stretch-backports; urgency=medium

  * Rebuild for stretch-backports.
  * Relax debhelper Build-Depends to 11~ to allow backporting.
  * Restore btrfs-tools transitional package.  This is needed for the
following packages on stretch: xen-tools, schroot, lxc,
linaro-image-tools, kvpm, fsarchiver, and libguestfs0.
  * Add Breaks snapper (<< 0.5.4-4~).  Needed because upstream
btrfs-progs-4.16.1 changed some library names and locations.
See Bug #900314 for more information.
  * Remove debian/source/options, because this source option forces
regeneration of a new orig.tarball, when the existing one in the
archive must be used for backports.

 -- Nicholas D Steeves   Sat, 01 Sep 2018 14:59:26 -0400

btrfs-progs (4.17-1) unstable; urgency=medium

  * New upstream release.

 -- Dimitri John Ledkov   Mon, 23 Jul 2018 14:31:22 +0100

btrfs-progs (4.16.1-2) unstable; urgency=medium

  * Do not copy_exec btrfs-zero-log into initramfs, superseeded by `btrfs
rescue zero-log` sub-command. Closes: #898720, #898719.

 -- Dimitri John Ledkov   Tue, 15 May 2018 14:15:27 +0100

btrfs-progs (4.16.1-1) unstable; urgency=medium

  * New upstream release.
  * Drop transitional btrfs-tools package.
  * Drop cross.patch, similar change done upstream.
  * Package libbtrfs, libbtrfsutil, and python bindings.

 -- Dimitri John Ledkov   Tue, 08 May 2018 14:17:03 -0700

btrfs-progs (4.15.1-2) unstable; urgency=medium

  * If libzstd is provided in both deb & udeb variants (such as Ubuntu
bionic) enable zstd support. If libzstd is not provided with both deb
& udeb variants (such as current Debian unstable) disable zstd
support. If and when libzstd is provided in both deb & udeb variants,
a binNMU of this package is sufficient to enable zstd support. Closes:
#886968
  * Drop obsolete lintian overrides.
  * Add alternative email address as uploader.

 -- Dimitri John Ledkov   Sat, 21 Apr 2018 11:59:50 +0100

btrfs-progs (4.15.1-1) unstable; urgency=medium

  * New upstream release

 -- Dimitri John Ledkov   Mon, 19 Feb 2018 15:50:12 +

btrfs-progs (4.14.1-1) unstable; urgency=medium

  * New upstream release.
  * Add libzstd-dev build dependency.

 -- Dimitri John Ledkov   Thu, 11 Jan 2018 15:43:20 +


Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#907667: lintian: should html escape output if --color=html is used

[Chris Lamb]

Hi Niels,

> Though, reminder - if you introduce a new dependency, you will have to
> get DSA to install it on lindsay.d.o before you can upgrade lintian there.

(Oh, I forgot to mention; it's already installed on lindsay)


Regards,

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

Bug#862873: RFA: vblade-persist

[Christoph Biedl]

Daniel Kahn Gillmor wrote...

> It'd take a bit of thinking about how to handle mac address
> limitations, and the decision about whether to place the symlink or
> not, to bring this up to parity with the current implementation, but
> then this work could be donated directly to the vblade upstream, and
> we could leave it at that.

As you might already have seen, I've suggested a solution for
persistence at upstream. Assuming things go well - I'm fairly certain -
vblade will soon provide persistence on its own and we can RM
vblade-persist in time before the buster release.

This is mostly to inform potential adopters their work will probably be
in vain.

To ease transition for users of vblade-persist, I've already prepared a
migration script to convert configurations into the new format, it will
be part of the vblade for quite some time.

Christoph, wearing the vblade maintainer's hat


signature.asc
Description: PGP signature

Bug#907773: RFS: btrfsmaintenance/0.4.1-3

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: normal

Dear Sven and mentors,

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

Package name: btrfsmaintenance
Version : 0.4.1-3
URL : https://github.com/kdave/btrfsmaintenance
License : GPL-2

It builds this binary package:

  btrfsmaintenance - automate btrfs maintenance tasks on mountpoints or 
directories

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfsmaintenance/btrfsmaintenance_0.4.1-3.dsc

Alternatively, checkout this repository:

  git clone https://salsa.debian.org/sten-guest/btrfsmaintenance.git

Changes since the last upload:

btrfsmaintenance (0.4.1-3) unstable; urgency=medium 

  * Import 0003-btrfs-defrag.sh-add-functions-library-to-fix-missing.patch  
from upstream pull request, to address failure of scheduled 
defragmentation in btrfs-defrag.sh due to missing 'is_btrfs' function.  
  * Declare Standards-Version: 4.2.1. (No additional changes needed)

 -- Nicholas D Steeves   Sat, 01 Sep 2018 14:35:13 -0400

btrfsmaintenance (0.4.1-2) unstable; urgency=high

Regards,
Nicholas D Steeves

Bug#907772: dpkg-maintscript-helper debug output assumes DPKG_MAINTSCRIPT_PACKAGE is set

[Ferenc Wágner]

Package: dpkg
Version: 1.18.25
Severity: minor

Dear Maintainer,

If the package name is provided on the dpkg_maintscript_helper command
line, the DPKG_MAINTSCRIPT_HELPER variable is still used for generating
debug output, which gets broken without warning if the variable isn't set
(for example during testing from the command line).  Please consider
adding an extra check for this.
-- 
Thanks,
Feri.

Bug#905107: gnome-shell-pomodoro: global.screen is not available in GNOME Shell 3.29

[Joseph Herlant]

Hi Simon,

Sorry for the late, I just saw this bug.
Thanks for forwarding it upstream. I'll work on a PR for that this weekend.

Joseph

Bug#907770: tarantool-lts-modules: The package names in the Recommends are incorrect

[Adrian Bunk]

Package: tarantool-lts-modules
Version: tarantool-lts
Severity: important

Recommends: tarantool-postgresql-module (= 1.5.5.37.g1687c02-1), 
tarantool-mysql-module (= 1.5.5.37.g1687c02-1), tarantool-sophia-module (= 
1.5.5.37.g1687c02-1)

The actual package names are tarantool-lts-*.

Bug#907771: transition: qcustomplot

[Anton Gladky]

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

Dear release team,

please schedule the transition of the qcustomplot package. It seems
that the bost dependent packages are building fine against the
new package version.


Ben file:

title = "qcustomplot";
is_affected = .depends ~ "libqcustomplot1.3" | .depends ~ "libqcustomplot2.0";
is_good = .depends ~ "libqcustomplot2.0";
is_bad = .depends ~ "libqcustomplot1.3";

Thanks

Anton

Bug#907769: chromium: tab consistently crashes when visiting arduino webpage

[Marius Mikucionis]

Package: chromium
Version: 69.0.3497.12-1
Severity: normal

Hi,
The browser tab crashes when loading the pages from the following popular 
website:
https://store.arduino.cc/

It loads descriptions and pictures, but crashes with "Aw, Snap!" message just 
before the menu appears.
The terminal shows segfault for each reload, here are two subconsequent ones:

Calling _exit(1). Core file will not be generated.
Received signal 11 SEGV_MAPERR 
#0 0x5647c97242be 
#1 0x5647c97246bb 
#2 0x5647c9724d3e 
#3 0x7fe84e5b28e0 
#4 0x5647cc0ec593 
#5 0x5647cc1006c5 
#6 0x5647c8db28d2 
#7 0x5647c8eb9981 
#8 0x5647c9223dce 
  r8: 5647cc100945  r9: 00f8 r10: 5647cf0e9c50 r11: 
064707389ca9
 r12:  r13: 7fff03654b50 r14: 7fff03654b60 r15: 
7fff03654b38
  di: 7fff03654b60  si: 5647cce6da60  bp: 7fff03654d50  bx: 
1d5e19c47d50
  dx: 5647cc0ec588  ax:   cx: 00e1  sp: 
7fff03654b10
  ip: 5647cc0ec593 efl: 00010206 cgf: 002b0033 erf: 
0004
 trp: 000e msk:  cr2: 
[end of stack trace]
Calling _exit(1). Core file will not be generated.
Received signal 11 SEGV_MAPERR 
#0 0x5647c97242be 
#1 0x5647c97246bb 
#2 0x5647c9724d3e 
#3 0x7fe84e5b28e0 
#4 0x5647cc0ec593 
#5 0x5647cc1006c5 
#6 0x5647c8db28d2 
#7 0x5647c8eb9981 
#8 0x5647c9223dce 
  r8: 5647cc100945  r9: 00f8 r10: 5647cf0e99c0 r11: 
31e892189ca9
 r12:  r13: 7fff03654b50 r14: 7fff03654b60 r15: 
7fff03654b38
  di: 7fff03654b60  si: 5647cce6da60  bp: 7fff03654d50  bx: 
38ddf1847d50
  dx: 5647cc0ec588  ax:   cx: 00e1  sp: 
7fff03654b10
  ip: 5647cc0ec593 efl: 00010206 cgf: 002b0033 erf: 
0004
 trp: 000e msk:  cr2: 
[end of stack trace]

I have tried clearing the cache, opening in privacy mode, guest user (no 
plugins nor extensions),
another (fresh) user profile -- exactly the same symptoms.

I have tried downgrading and the following versions are also affected:
Version: 69.0.3497.12-1
Version: 68.0.3440.75-2
Version: 68.0.3440.75-1~deb9u1

Firefox does not have such issues.

I use nvidia-driver=390.48-3

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

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

Versions of packages chromium depends on:
ii  chromium-common  69.0.3497.12-1
ii  libasound2   1.1.6-1
ii  libatk-bridge2.0-0   2.26.2-1
ii  libatk1.0-0  2.28.1-1
ii  libatomic1   8.2.0-4
ii  libavcodec58 10:4.0.2-dmo2
ii  libavformat5810:4.0.2-dmo2
ii  libavutil56  10:4.0.2-dmo2
ii  libc62.27-5
ii  libcairo-gobject21.15.12-1
ii  libcairo21.15.12-1
ii  libcups2 2.2.8-5
ii  libdbus-1-3  1.12.10-1
ii  libdrm2  2.4.93-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.6-1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.2.0-4
ii  libgdk-pixbuf2.0-0   2.36.12-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.30-2
ii  libharfbuzz0b1.8.8-2
ii  libicu60 60.2-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.19-3
ii  libnss3  2:3.38-1
ii  libopenjp2-7 2.3.0-1
ii  libopus0 1.3~beta+20180518-1
ii  libpango-1.0-0   1.42.4-1
ii  libpangocairo-1.0-0  1.42.4-1
ii  libpci3  1:3.5.2-1
ii  libpng16-16  1.6.34-2
ii  libpulse012.0-1
ii  libre2-4 20180701+dfsg-1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.2.0-4
ii  libvpx5  1.7.0-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.6-1
ii  libx11-xcb1  2:1.6.6-1
ii  libxcb1  1.13-3
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-1
ii  libxdamage1  1:1.1.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7+b1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2
ii  libxss1  1:1.2.2-1+b2
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

chromium recommends no packages.

Versions of 

Bug#907290: propellor: Apt.trustsKey should not call apt-key

[David Bremner]

Sean Whitton  writes:

> control: tag -1 + confirmed upstream
> control: forwarded -1 
> https://propellor.branchable.com/todo/Apt.trustsKey_should_not_invoke_apt-key/
>
>
> What we are talking about here are public keys, and in fact
> Apt.trustsKey does not work with any privcontent, but simply with a
> String, i.e., it implicitly expects the output of `gpg -a --export`
> right there in your config.hs.
>
> So Apt.trustsKey should be implemented with File.hasContents.
>

that makes sense to me.

Bug#907717: linux-image-4.17.0-0.bpo.3-amd64: another backtrace with result of unusable system till reboot

[m . alfaeko]

Package: linux-image-4.17.0-0.bpo.3-amd64
Followup-For: Bug #907717

Dear Maintainer,

Today i experienced a backtrace which resulted to a system without a graphic
output. In logs i found a entry about a bug with a message Unable to handle
kernel NULL pointer deference. The process involved in Oops was again Xorg.
It looks like the kernel 4.16.0-0.bpo2-amd64 is good without this kind of
failures.

Thank you
2018-09-01T19:23:00.289544+02:00 debian kernel: [25854.565534] refcount_t: 
increment on 0; use-after-free.
2018-09-01T19:23:00.289546+02:00 debian kernel: [25854.565570] WARNING: CPU: 0 
PID: 26032 at /build/linux-h2pQxc/linux-4.17.17/lib/refcount.c:153 
refcount_inc+0x27/0x30
2018-09-01T19:23:00.289547+02:00 debian kernel: [25854.565571] Modules linked 
in: pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) xt_tcpudp 
xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat 
nf_conntrack iptable_filter binfmt_misc dm_thin_pool amdkfd dm_persistent_data 
dm_bio_prison dm_bufio libcrc32c amdgpu eeepc_wmi asus_wmi sparse_keymap rfkill 
wmi_bmof snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi 
snd_hda_intel snd_hda_codec chash gpu_sched ttm edac_mce_amd kvm_amd 
snd_hda_core ccp drm_kms_helper snd_hwdep rng_core snd_pcm kvm snd_timer snd 
drm soundcore sg fam15h_power irqbypass evdev crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel serio_raw k10temp pcspkr shpchp i2c_algo_bit sp5100_tco 
video wmi button pcc_cpufreq acpi_cpufreq parport_pc ppdev lp parport ip_tables 
x_tables autofs4 ext4
2018-09-01T19:23:00.289549+02:00 debian kernel: [25854.565621]  crc16 mbcache 
jbd2 crc32c_generic fscrypto ecb sr_mod cdrom dm_mod hid_generic uas usbhid 
usb_storage hid sd_mod crc32c_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper xhci_pci ahci i2c_piix4 libahci xhci_hcd libata r8169 mii usbcore 
scsi_mod usb_common gpio_amdpt gpio_generic
2018-09-01T19:23:00.289550+02:00 debian kernel: [25854.565647] CPU: 0 PID: 
26032 Comm: Xorg Tainted: G   O  4.17.0-0.bpo.3-amd64 #1 Debian 
4.17.17-1~bpo9+1
2018-09-01T19:23:00.289551+02:00 debian kernel: [25854.565648] Hardware name: 
System manufacturer System Product Name/PRIME A320M-K, BIOS 3401 12/04/2017
2018-09-01T19:23:00.289552+02:00 debian kernel: [25854.565650] RIP: 
0010:refcount_inc+0x27/0x30
2018-09-01T19:23:00.289553+02:00 debian kernel: [25854.565651] RSP: 
0018:abd18333b9f0 EFLAGS: 00010282
2018-09-01T19:23:00.289554+02:00 debian kernel: [25854.565652] RAX: 
 RBX: 8c7c838cdc00 RCX: 0006
2018-09-01T19:23:00.289555+02:00 debian kernel: [25854.565653] RDX: 
0007 RSI: 0092 RDI: 8c7c8a616730
2018-09-01T19:23:00.289575+02:00 debian kernel: [25854.565654] RBP: 
8c7c838ca000 R08: 0001 R09: 03c2
2018-09-01T19:23:00.289577+02:00 debian kernel: [25854.565655] R10: 
abd18333bb70 R11: 03c2 R12: abd18333ba30
2018-09-01T19:23:00.289578+02:00 debian kernel: [25854.565656] R13: 
 R14: 8c7c86627000 R15: 
2018-09-01T19:23:00.289578+02:00 debian kernel: [25854.565658] FS:  
7f268bacda40() GS:8c7c8a60() knlGS:
2018-09-01T19:23:00.289579+02:00 debian kernel: [25854.565659] CS:  0010 DS: 
 ES:  CR0: 80050033
2018-09-01T19:23:00.289580+02:00 debian kernel: [25854.565659] CR2: 
7f26799cd000 CR3: 000102764000 CR4: 001406f0
2018-09-01T19:23:00.289581+02:00 debian kernel: [25854.565661] Call Trace:
2018-09-01T19:23:00.289582+02:00 debian kernel: [25854.565777]  
dc_create_stream_for_sink+0x4e/0x190 [amdgpu]
2018-09-01T19:23:00.289583+02:00 debian kernel: [25854.565822]  
create_stream_for_sink+0x6d/0x5f0 [amdgpu]
2018-09-01T19:23:00.289584+02:00 debian kernel: [25854.565868]  ? 
amdgpu_dm_connector_mode_valid+0x62/0x1f0 [amdgpu]
2018-09-01T19:23:00.289584+02:00 debian kernel: [25854.565945]  ? 
drm_mode_connector_list_update+0xb3/0x1b0 [drm]
2018-09-01T19:23:00.289585+02:00 debian kernel: [25854.565987]  
amdgpu_dm_connector_mode_valid+0x62/0x1f0 [amdgpu]
2018-09-01T19:23:00.289586+02:00 debian kernel: [25854.566023]  
drm_helper_probe_single_connector_modes+0x52a/0x6f0 [drm_kms_helper]
2018-09-01T19:23:00.289587+02:00 debian kernel: [25854.566038]  
drm_mode_getconnector+0x2ea/0x320 [drm]
2018-09-01T19:23:00.289587+02:00 debian kernel: [25854.566052]  ? 
drm_mode_connector_property_set_ioctl+0x60/0x60 [drm]
2018-09-01T19:23:00.289588+02:00 debian kernel: [25854.566061]  
drm_ioctl_kernel+0x67/0xb0 [drm]
2018-09-01T19:23:00.289589+02:00 debian kernel: [25854.566073]  
drm_ioctl+0x2c5/0x360 [drm]
2018-09-01T19:23:00.289590+02:00 debian kernel: [25854.566084]  ? 
drm_mode_connector_property_set_ioctl+0x60/0x60 [drm]
2018-09-01T19:23:00.289591+02:00 debian kernel: [25854.566112]  
amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
2018-09-01T19:23:00.289592+02:00 debian kernel: [25854.566121]  
do_vfs_ioctl+0xa2/0x620

Bug#805711: light-locker: no login possible after suspend

[Michael Becker]

Package: light-locker
Version: 1.8.0-1
Followup-For: Bug #805711

I have started light-locker from an X-terminal with debug option.
light-locker was started at 19:43:16
Lid was closed at 19:43:24
Lid was opened at 19:43:29
light-locker was killed from VT1 at 19:43:42

hope the log helps ...


$ light-locker --lock-on-lid --debug
[gs_debug_init] gs-debug.c:106 (19:43:16):   Debugging enabled
[main] light-locker.c:142 (19:43:16):initializing light-locker 1.8.0
[main] light-locker.c:164 (19:43:16):Platform:
gtk:3
systemd:yes
ConsoleKit: yes
UPower: yes
[main] light-locker.c:196 (19:43:16):Features:
lock-after-screensaver: yes
late-locking:   yes
lock-on-suspend:yes
lock-on-lid:yes
settings backend:   GSETTINGS
[main] light-locker.c:198 (19:43:16):lock after screensaver 5
[main] light-locker.c:199 (19:43:16):late locking 0
[main] light-locker.c:200 (19:43:16):lock on suspend 1
[main] light-locker.c:201 (19:43:16):lock on lid 1
[main] light-locker.c:202 (19:43:16):idle hint 0
[init_session_id] gs-listener-dbus.c:2193 (19:43:16):Got session-id: 
/org/freedesktop/login1/session/_32
[init_session_id] gs-listener-dbus.c:2198 (19:43:16):Got sd-session-id: 2
[init_seat_path] gs-listener-dbus.c:2279 (19:43:16): Got seat: 
/org/freedesktop/DisplayManager/Seat0
[gs_listener_delay_suspend] gs-listener-dbus.c:449 (19:43:16):   Delay suspend
[gs_listener_x11_acquire] gs-listener-x11.c:172 (19:43:16):  ScreenSaver 
Registered
[listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (19:43:16):   
 obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus 
method=NameAcquired destination=:1.280
[listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (19:43:24):   
 obj_path=/org/freedesktop/UPower interface=org.freedesktop.DBus.Properties 
method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:1382 (19:43:24):   
 UPower notified LidIsClosed 1
[gs_grab_grab_root] gs-grab-x11.c:647 (19:43:24):Grabbing the root 
window
[gs_grab_get_keyboard] gs-grab-x11.c:153 (19:43:25): Grabbing keyboard 
widget=1AA
[gs_grab_get_mouse] gs-grab-x11.c:213 (19:43:25):Grabbing mouse 
widget=1AA
[gs_manager_create_windows_for_screen] gs-manager.c:548 (19:43:25):  
Creating 1 windows for screen 0
[gs_manager_create_window_for_monitor] gs-manager.c:324 (19:43:25):  
Creating window for monitor 0 [0,0] (3840x2160)
[update_geometry] gs-window-x11.c:197 (19:43:25):got geometry for 
monitor 0: x=0 y=0 w=3840 h=2160
[update_geometry] gs-window-x11.c:210 (19:43:25):using geometry for 
monitor 0: x=0 y=0 w=3840 h=2160
[update_geometry] gs-window-x11.c:197 (19:43:25):got geometry for 
monitor 0: x=0 y=0 w=3840 h=2160
[update_geometry] gs-window-x11.c:210 (19:43:25):using geometry for 
monitor 0: x=0 y=0 w=3840 h=2160
[gs_window_move_resize_window] gs-window-x11.c:243 (19:43:25):   Move and/or 
resize window on monitor 0: x=0 y=0 w=3840 h=2160
[update_geometry] gs-window-x11.c:197 (19:43:25):got geometry for 
monitor 0: x=0 y=0 w=3840 h=2160
[update_geometry] gs-window-x11.c:210 (19:43:25):using geometry for 
monitor 0: x=0 y=0 w=3840 h=2160
[gs_window_move_resize_window] gs-window-x11.c:243 (19:43:25):   Move and/or 
resize window on monitor 0: x=0 y=0 w=3840 h=2160
[update_geometry] gs-window-x11.c:197 (19:43:25):got geometry for 
monitor 0: x=0 y=0 w=3840 h=2160
[update_geometry] gs-window-x11.c:210 (19:43:25):using geometry for 
monitor 0: x=0 y=0 w=3840 h=2160
[gs_window_move_resize_window] gs-window-x11.c:243 (19:43:25):   Move and/or 
resize window on monitor 0: x=0 y=0 w=3840 h=2160
[on_screen_monitors_changed] gs-manager.c:351 (19:43:25):Monitors 
changed for screen 0: num=1
[listener_dbus_handle_session_message] gs-listener-dbus.c:1010 (19:43:25):  
 Received Lock request
[on_screen_monitors_changed] gs-manager.c:351 (19:43:25):Monitors 
changed for screen 0: num=1
[gs_window_raise] gs-window-x11.c:328 (19:43:25):Raising screensaver 
window
[gs_window_xevent] gs-window-x11.c:369 (19:43:25):   not raising our windows
[window_map_event_cb] gs-manager.c:233 (19:43:25):   Handling window 
map_event event
[gs_listener_resume_suspend] gs-listener-dbus.c:513 (19:43:25):  Resume 
suspend: fd=14
[manager_maybe_grab_window] gs-manager.c:204 (19:43:25): Moving grab to 
0x55a4f9934470
[gs_grab_move_keyboard] gs-grab-x11.c:450 (19:43:25):Moving keyboard grab 
from 1AA to 2CC
[gs_grab_move_keyboard] gs-grab-x11.c:457 (19:43:25):*** doing X server grab
[gs_grab_release_keyboard] gs-grab-x11.c:279 (19:43:25): Ungrabbing 
keyboard
[gs_grab_get_keyboard] gs-grab-x11.c:153 (19:43:25): Grabbing keyboard 
widget=2CC
[gs_grab_move_keyboard] gs-grab-x11.c:479 (19:43:25):*** releasing X server 
grab
[gs_grab_move_mouse] 

Bug#892717: If there is a MIME header: then no additional tags are needed

[Власенко Михаил Викторович]

Package: dicoweb
Version: 2.3-2
Tags: patch
Followup-For: Bug #892717

Dear Maintainer,

This should fix it. My patch for solving this problem I send as an attachment. 
Can you test this and see if it works?

... Michael


dicoweb-content-type.patch
Description: Binary data

Bug#907768: debian-installer: gfx and txt installer fail on new System76 oryx pro 17in 1080P disp w nvidia GTX1070

[Carl Myers]

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

Dear Maintainer,

Booting to the installer on my new Oryx Pro is failing for both the text and
graphical installer.  I have produced a 5minute video showing exactly what it 
looks like:

https://drive.google.com/file/d/1qSKTsWiLbauBi8ALDtzV1D225i7Zgrtn/view?usp=sharing

When booting into the text installer, the screen is scaled so tiny it is only
1cm by 1cm, and tiled horizontally across the screen.  If you zoom in you can
see the screen is "really there" but it is so tiny you can't make out any of
the options.

When booting into the graphical installer, I just see a blank screen and the
machine seems to hang forever.

The machine came with ubuntu pre-installed and it boots into that system just 
fine.

I was able to reproduce this problem with the following images:
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.5.0-amd64-xfce-CD-1.iso
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.5.0-amd64-netinst.iso
https://cdimage.debian.org/cdimage/buster_di_alpha3/amd64/iso-cd/debian-buster-DI-alpha3-amd64-netinst.iso

I confirmed the checksum of the ISO and the validity of the usb drive, and
confirmed it worked in another machine.

The machine includes both intel and nvidia graphics, which are switched by
software.  I have tried putting it in both NVIDIA and Intel graphics modes and
see the same behavior:
https://support.system76.com/articles/graphics-switch-ubuntu/

I've tried several boot parameters including "nomodeset" and "vga=", DEBIAN_FRONT_END=text, fb=false, gfxpayload=1920x1080, etc.

When I boot into the ubuntu install, the native resolution appears to be 
1920x1080.

Because I currently have it set to Intel graphics mode, the nvidia hardware
doesn't even show up in $(lspci), the intel hardware is "Intel Corporation
Device 3e9b" using kernel driver i915.  I can get the nvidia details if needed
but system76 says it is a 8GB GTX 1070.

I am filing this report from another machine, so the system information below
is not relevant.

I am happy to try things if you have any suggestions for a workaround, at this
point I have to imagine the possibilities are a (very very weird) hardware
problem, or a hardware incompatibility.

Thanks!
-Carl Myers


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

Kernel: Linux 4.8.0-2-amd64 (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/dash
Init: systemd (via /run/systemd/system)

Bug#907423: lintian should give an error when both foo-dbg and foo-dbgsym are built

[Adrian Bunk]

On Mon, Aug 27, 2018 at 09:18:43PM +0100, Chris Lamb wrote:
> Hi Adrian,
> 
> > lintian should give an error when both foo-dbg and foo-dbgsym are
> > built
> 
> Could you provide another draft description? Thank you in advance.

Both -dbg and -dbgsym are built for this package.
Only one should be built for the debug symbols.

Usually the -dbg should be dropped in favour of the -dbgsym.

In some cases (e.g. for Python modules) the -dbg contains more than just 
the debug symbols. In these cases the -dbgsym should not be built.

> Regards,

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#893319: Crash

[Ian Eure]

I’ve been experiencing this crash for a while as well, using mu4e.
Because I use exwm, it’s extra annoying -- my whole X session 
crashes.


Multiple stretch machines don’t experience the issue.

My workaround is to launch Emacs in a terminal and archive the
offending message(s).

I’d very much like to see this fixed.

Bug#907290: propellor: Apt.trustsKey should not call apt-key

[Sean Whitton]

control: tag -1 + confirmed upstream
control: forwarded -1 
https://propellor.branchable.com/todo/Apt.trustsKey_should_not_invoke_apt-key/

Hello,

On Sat 25 Aug 2018 at 09:29PM -0300, David Bremner wrote:

> Prior to upstream commit 1d39a530, Propellor did something like
>
> (proc "gpg" ["--no-default-keyring", "--keyring", f, "--import", "-"])
>
> which created a a gpg keyring, and the format of those changed at some
> point to something that apt-key does not support. To fix this breakage
> Propeller switched to calling apt-key add, which works, for now, but
> it complains, and will probably break at some point.
>
> According to the apt-key manpage
>
>  "Instead of using this [add] command a keyring should be placed
>directly in the /etc/apt/trusted.gpg.d/ directory with a
>descriptive name and either "gpg" or "asc" as file extension."
>
> As far as I can tell, if the privdata is in the right format (which is
> always an issue with propellor), no call to gpg should be necessary,
> and trustsKey could be implimented e.g. with File.hasPrivContent.

What we are talking about here are public keys, and in fact
Apt.trustsKey does not work with any privcontent, but simply with a
String, i.e., it implicitly expects the output of `gpg -a --export`
right there in your config.hs.

So Apt.trustsKey should be implemented with File.hasContents.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#907171: prometheus FTBFS:

[Adrian Bunk]

Control: severity -1 normal

On Mon, Aug 27, 2018 at 07:18:30PM +0100, Martín Ferrari wrote:
> On 27/08/18 17:08, Adrian Bunk wrote:
> 
> > How often did you try?
> > 
> > I would say the probability to hit is somewhere around 50%:
> > https://tests.reproducible-builds.org/debian/history/prometheus.html
> 
> I just tried 20 builds, while using desktop applications that put some
> extra strain on tHE CPU, and none failed..

It didn't fail this way on the buildds, so I agree that whatever 
triggers this problem does not look RC right now.

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#907381: python-sphinx: missing dependency on python-stemmer

[Adrian Bunk]

On Mon, Aug 27, 2018 at 01:31:36PM +0300, Dmitry Shachnev wrote:
> Hi Adrian!

Hi Dmitry!

> On Mon, Aug 27, 2018 at 11:20:20AM +0300, Adrian Bunk wrote:
> > Package: python-sphinx
> > Version: 1.7.7-1
> > Severity: serious
> > Control: affects -1 src:bzr
> >
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/bzr.html
> >
> > ...
> > Exception occurred:
> >   File "/usr/lib/python2.7/dist-packages/sphinx/search/es.py", line 14, in 
> > 
> > import Stemmer
> > ImportError: No module named Stemmer
> 
> I did not want to make pystemmer a hard dependency because this only affects
> non-English documentation.
> 
> Indeed it is my bad that I did not check what packages will be broken with
> this, but maybe you can estimate how many of them got broken now? If it is
> < 10 source packages, I would rather file bugs on them.

You already fixed ubuntu-packaging-guide, and this is the only one 
I found in addition to bzr.

So reassigning this bug to bzr sounds like an option.

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#907767: mozplugger seems to be useless now

[Adrian Bunk]

Package: mozplugger
Version: 1.14.5-2
Severity: serious
Tags: buster sid

As far as I can see, not a single one of the 15 (sic) browser packages
in the dependencies does both still exist in unstable and still work
with mozplugger.

Bug#907737: liblucy-perl: Project Lucy has retired

[Dominic Hargreaves]

On Sat, Sep 01, 2018 at 04:42:36PM +0200, Jonas Smedegaard wrote:
> Quoting Xavier Guimard (2018-09-01 08:46:22)
> > Package: liblucy-perl
> > Version: Project Lucy has retired
> > Severity: important
> > 
> > As announced in http://lucy.apache.org/, project Lucy has retired. I
> > think we should remove it from buster
> 
> liblucy-perl has two reverse dependencies:
> 
>   * openguides
>   * libcatmandu-store-lucy-perl
> 
> It is fine by me to drop libcatmandu-store-lucy-perl with liblucy-perl: 
> Other Catmandu search backends exist but need to be packaged, but 
> shipping no Catmandu search backend is better than shipping a backend 
> dead upstream!
> 
> @Dominique: Is it ok to drop openguides, or can it be made to not depend 
> on liblucy-perl?

I am still interested in OpenGuides (I run several instances using
the Debian package).

I suspect not that many users use Lucy, so I'm fine with dropping that
dependency. Please ping me in a couple of weeks if I haven't got around
to that.

Ironically, Lucy is more alive than Plucene, which saw it last upstream
release in 2005, and which is probably used by most OpenGuides sites.

Cheers,
Dominic.

Bug#897642: RFS: gpgme1.0/1.11.1-1~bpo9+1

[Roger Shimizu]

On Sat, Sep 1, 2018 at 11:15 PM, Jacob Adams  wrote:
> control: tag -1 -moreinfo
>
> On Sep 1, 2018, at 04:49, Roger Shimizu  wrote:
>
> control: tag -1 +moreinfo
>
> Dear Jacob,
>
> On Fri, May 4, 2018 at 3:27 AM, Jacob Adams  wrote:
>
> Package: sponsorship-requests
>
> Severity: normal
>
>
>  Dear mentors,
>
>
>  I am looking for a sponsor for my package "gpgme1.0"
>
>
> Thanks for your interest in contribution to debian!
>
>  Changes since the last upload:
>
>
> gpgme1.0 (1.11.1-1~bpo9+1) stretch-backports; urgency=medium
>
>
>  * Rebuild for stretch-backports.
>
>
> -- Jacob Adams   Thu, 26 Apr 2018 13:13:54 -0400
>
>
>
> This package will also require libgpgerror, which you can find here:
>
>
> https://mentors.debian.net/package/libgpg-error
>
>
> https://mentors.debian.net/debian/pool/main/libg/libgpg-error/libgpg-error_1.29-4~bpo9+1.dsc
>
>
> It already has an RFS: #897045
>
>
> I would like to be able to use the latest version of GPGME in my GSoC
>
> 2018 project. In order to do that I would prefer to use a backport as
>
> the PGP Clean Room CD is based off of stretch.
>
>
> I see the project seems already released as beta [1], so maybe there's
> no need to do this backports upload?
>
>
> My project does require a newer version of GPGME than is shipped in stretch.
> However, I didn’t want to wait on the backport, so I’ve been including the
> deb files directly in my build:
> https://salsa.debian.org/tookmund-guest/make-pgp-clean-room/tree/master/resources/config/packages.chroot
>
>
> And what's the benefit for this backports pkg? Any new feature or
> bugfix you're particularly interested in?
>
>
> There has been significant improvement in GPGME’s python binding since
> stretch, and my project relies on these features, such as the new key
> generation function.
>
> It would be nice to be able to pull these packages from backports instead of
> including them directly.

I compiled this pkg under stretch, and meet the following error.


cJSON.c:45:20: fatal error: gpgrt.h: No such file or directory
 # include 
^


I see you updated libgpg-error to 1.29, so I tried to compile with
latest backported sid version, 1.32, and it succeeded.
So I updated D-B on libgpg-error to >= 1.29.

I uploaded this backported pkg to DELAYED=6.
So If you don't like the backports upload, just kindly cancel it.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#907763: ant-contrib: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:ant-contrib
Version: 1.0~b3+svn177-9
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with maven-repo-helper
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/ant-contrib-1.0~b3+svn177'
dh_auto_build -- jar
ant -propertyfile ./debian/ant.properties -Duser.name debian jar
Buildfile: /<>/ant-contrib-1.0~b3+svn177/build.xml

init:

configure:

resolve:

classpath-ivy:

classpath-no-ivy:

classpath:

compile:
[mkdir] Created dir: /<>/ant-contrib-1.0~b3+svn177/target/classes
[javac] /<>/ant-contrib-1.0~b3+svn177/build.xml:113: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 7
[javac] Using javac -target 1.4 is no longer supported, switching to 7
[javac] Compiling 111 source files to 
/<>/ant-contrib-1.0~b3+svn177/target/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 7
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 warning
 [copy] Copying 2 files to 
/<>/ant-contrib-1.0~b3+svn177/target/classes

jar:
  [jar] Building jar: 
/<>/ant-contrib-1.0~b3+svn177/target/ant-contrib.jar

BUILD SUCCESSFUL
Total time: 4 seconds
make[1]: Leaving directory '/<>/ant-contrib-1.0~b3+svn177'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>/ant-contrib-1.0~b3+svn177'
dh_auto_build -- test
ant -propertyfile ./debian/ant.properties -Duser.name debian test
Buildfile: /<>/ant-contrib-1.0~b3+svn177/build.xml

init:

configure:

resolve:

classpath-ivy:

classpath-no-ivy:

classpath:

compile:
[javac] /<>/ant-contrib-1.0~b3+svn177/build.xml:113: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 7
[javac] Using javac -target 1.4 is no longer supported, switching to 7

compile-tests:
[mkdir] Created dir: 
/<>/ant-contrib-1.0~b3+svn177/target/test-classes
[javac] /<>/ant-contrib-1.0~b3+svn177/build.xml:127: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 7
[javac] Using javac -target 1.4 is no longer supported, switching to 7
[javac] Compiling 25 source files to 
/<>/ant-contrib-1.0~b3+svn177/target/test-classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 7
[javac] 1 warning
 [copy] Copying 74 files to 
/<>/ant-contrib-1.0~b3+svn177/target/test-classes

gump-safe-test:

init:

configure:

resolve:

classpath-ivy:

classpath-no-ivy:

classpath:

compile:
[javac] /<>/ant-contrib-1.0~b3+svn177/build.xml:113: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 7
[javac] Using javac -target 1.4 is no longer supported, switching to 7

compile-tests:
[javac] /<>/ant-contrib-1.0~b3+svn177/build.xml:127: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 7
[javac] Using javac -target 1.4 is no longer supported, switching to 7

jar:

run-test:
[junit] Testsuite: net.sf.antcontrib.design.VerifyDesignTest
[junit] Tests run: 41, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
8.467 sec
[junit] 
[junit] Testsuite: net.sf.antcontrib.logic.AntCallBackTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.252 sec
[junit] 
[junit] Testsuite: net.sf.antcontrib.logic.AssertTest
[junit] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.423 sec
[junit] 
[junit] Testsuite: net.sf.antcontrib.logic.ForTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.138 sec
[junit] 
[junit] Testsuite: net.sf.antcontrib.logic.ForeachTaskTest
[junit] Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.659 sec
[junit] 
[junit] Testsuite: net.sf.antcontrib.logic.IfTaskTest
[junit] Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.588 sec
[junit] 
[junit] Testsuite: net.sf.antcontrib.logic.OutOfDateTest

Bug#907766: node-chokidar: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:node-chokidar
Version: 1.7.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha --exit --reporter spec


  chokidar
✓ should expose public API methods
fs.watch (non-polling)
  watch a directory
✓ should produce an instance of chokidar.FSWatcher
✓ should expose public API methods
✓ should emit `add` event when file was added (57ms)
✓ should emit `addDir` event when directory was added (56ms)
✓ should emit `change` event when file was changed
✓ should emit `unlink` event when file was removed (104ms)
✓ should emit `unlinkDir` event when a directory was removed (53ms)
✓ should emit `unlink` and `add` events when a file is renamed (156ms)
✓ should emit `add`, not `change`, when previously deleted file is 
re-added (161ms)
✓ should not emit `unlink` for previously moved files (404ms)
✓ should survive ENOENT for missing subdirectories
✓ should notice when a file appears in a new directory
✓ should watch removed and re-added directories (1514ms)
  watch individual files
✓ should detect changes
✓ should detect unlinks (156ms)
✓ should detect unlink and re-add (257ms)
✓ should ignore unwatched siblings (55ms)
  renamed directory
✓ should emit `add` for a file in a renamed directory (1017ms)
  watch non-existent paths
✓ should watch non-existent file and detect add (56ms)
✓ should watch non-existent dir and detect addDir/add (106ms)
  watch glob patterns
✓ should correctly watch and emit based on glob input (62ms)
✓ should respect negated glob patterns (156ms)
✓ should traverse subdirs to match globstar patterns (216ms)
✓ should resolve relative paths with glob patterns (72ms)
✓ should correctly handle conflicting glob patterns (158ms)
✓ should correctly handle intersecting glob patterns (58ms)
✓ should not confuse glob-like filenames with globs (103ms)
✓ should treat glob-like directory names as literal directory names 
when globbing is disabled (64ms)
✓ should treat glob-like filenames as literal filenames when globbing 
is disabled (51ms)
✓ should not prematurely filter dirs against complex globstar 
patterns (62ms)
✓ should emit matching dir events
  watch symlinks
✓ should watch symlinked dirs
✓ should watch symlinked files
✓ should follow symlinked files within a normal dir
✓ should watch paths with a symlinked parent
✓ should not recurse indefinitely on circular symlinks
✓ should recognize changes following symlinked dirs
✓ should follow newly created symlinks (57ms)
✓ should watch symlinks as files when followSymlinks:false
✓ should watch symlinks within a watched dir as files when 
followSymlinks:false (310ms)
✓ should not reuse watcher when following a symlink to elsewhere 
(115ms)
✓ should properly match glob patterns that include a symlinked dir
  watch arrays of paths/globs
✓ should watch all paths in an array
✓ should accommodate nested arrays in input
✓ should throw if provided any non-string paths
  watch options
ignoreInitial
  false
✓ should emit `add` events for preexisting files
✓ should emit `addDir` event for watched dir
✓ should emit `addDir` events for preexisting dirs
  true
✓ should ignore inital add events (51ms)
✓ should ignore add events on a subsequent .add() (1002ms)
✓ should notice when a file appears in an empty directory
✓ should emit a change on a preexisting file as a change
✓ should not emit for preexisting dirs when depth is 0 (418ms)
ignored
  ✓ should check ignore after stating
  ✓ should not choke on an ignored watch path
  ✓ should ignore the contents of ignored dirs (359ms)
  ✓ should allow regex/fn ignores (57ms)
depth
  ✓ should not recurse if depth is 0
  ✓ should recurse to specified depth (66ms)
  ✓ should respect depth setting when following symlinks (65ms)
  ✓ should respect depth setting when following a new symlink
  ✓ should correctly handle dir events when depth is 0 (68ms)
atomic
  ✓ should ignore vim/emacs/Sublime swapfiles (906ms)
  ✓ should ignore stale tilde files (53ms)
cwd
  

Bug#907765: honeysql-clojure: FTBFS in buster/sid (Could not locate honeysql/format_test__init.class or honeysql/format_test.clj on classpath.)

[Santiago Vila]

Package: src:honeysql-clojure
Version: 0.8.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with javahelper --with jh_maven_repo_helper
   dh_update_autotools_config -i
   dh_autoreconf -i
   jh_linkjars -i
   debian/rules override_jh_build
make[1]: Entering directory '/<>'
cat debian/header.html > /<>/CHANGES.html
sed -i'' -e 's#@TITLE@#0.8.2#g' /<>/CHANGES.html
markdown /<>/CHANGES.md >> /<>/CHANGES.html
cat debian/footer.html >> /<>/CHANGES.html
cat debian/header.html > /<>/README.html
sed -i'' -e 's#@TITLE@#Honey SQL#g' /<>/README.html
markdown /<>/README.md >> /<>/README.html
cat debian/footer.html >> /<>/README.html
jar cf honeysql.jar -C src .
mkdir -p /<>/doc/html && mv /<>/*.html 
/<>/doc/html
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
(cd test && find . -name '*.cljc' | \
xargs clojure -cp /<>/honeysql.jar)
Exception in thread "main" java.io.FileNotFoundException: Could not locate 
honeysql/format_test__init.class or honeysql/format_test.clj on classpath. 
Please check that namespaces with dashes use underscores in the Clojure file 
name., compiling:(/<>/test/./honeysql/core_test.cljc:1:1)
at clojure.lang.Compiler.load(Compiler.java:7526)
at clojure.lang.Compiler.loadFile(Compiler.java:7452)
at clojure.main$load_script.invokeStatic(main.clj:278)
at clojure.main$script_opt.invokeStatic(main.clj:338)
at clojure.main$script_opt.invoke(main.clj:333)
at clojure.main$main.invokeStatic(main.clj:424)
at clojure.main$main.doInvoke(main.clj:387)
at clojure.lang.RestFn.applyTo(RestFn.java:137)
at clojure.lang.Var.applyTo(Var.java:702)
at clojure.main.main(main.java:37)
Caused by: java.io.FileNotFoundException: Could not locate 
honeysql/format_test__init.class or honeysql/format_test.clj on classpath. 
Please check that namespaces with dashes use underscores in the Clojure file 
name.
at clojure.lang.RT.load(RT.java:463)
at clojure.lang.RT.load(RT.java:426)
at clojure.core$load$fn__9115.invoke(core.clj:6046)
at clojure.core$load.invokeStatic(core.clj:6045)
at clojure.core$load.doInvoke(core.clj:6029)
at clojure.lang.RestFn.invoke(RestFn.java:408)
at clojure.core$load_one.invokeStatic(core.clj:5848)
at clojure.core$load_one.invoke(core.clj:5843)
at clojure.core$load_lib$fn__9060.invoke(core.clj:5888)
at clojure.core$load_lib.invokeStatic(core.clj:5887)
at clojure.core$load_lib.doInvoke(core.clj:5868)
at clojure.lang.RestFn.applyTo(RestFn.java:142)
at clojure.core$apply.invokeStatic(core.clj:659)
at clojure.core$load_libs.invokeStatic(core.clj:5925)
at clojure.core$load_libs.doInvoke(core.clj:5909)
at clojure.lang.RestFn.applyTo(RestFn.java:137)
at clojure.core$apply.invokeStatic(core.clj:659)
at clojure.core$require.invokeStatic(core.clj:5947)
at clojure.core$require.doInvoke(core.clj:5947)
at clojure.lang.RestFn.invoke(RestFn.java:457)
at 
honeysql.core_test$eval2694$loading__9001__auto2695.invoke(core_test.cljc:1)
at honeysql.core_test$eval2694.invokeStatic(core_test.cljc:1)
at honeysql.core_test$eval2694.invoke(core_test.cljc:1)
at clojure.lang.Compiler.eval(Compiler.java:7062)
at clojure.lang.Compiler.eval(Compiler.java:7051)
at clojure.lang.Compiler.load(Compiler.java:7514)
... 9 more
make[1]: *** [debian/rules:26: override_dh_auto_test] Error 123
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

In reproducible builds it seems to be random, but I tried to build it 50 times
on GCE n1-standard-1 machines today and it failed each and every time.
If you need a test machine to reproduce please say so.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#907764: golang-github-hashicorp-raft: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-github-hashicorp-raft
Version: 1.0.0+git20180118.077966db-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-hashicorp-raft-1.0.0\+git20180118.077966db/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-hashicorp-raft-1.0.0\+git20180118.077966db/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/hashicorp/raft github.com/hashicorp/raft/bench
github.com/hashicorp/golang-lru/simplelru
github.com/hashicorp/go-immutable-radix
github.com/armon/go-metrics
github.com/hashicorp/go-msgpack/codec
github.com/hashicorp/raft
github.com/hashicorp/raft/bench
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/hashicorp/raft github.com/hashicorp/raft/bench
=== RUN   TestCommitment_setVoters
--- PASS: TestCommitment_setVoters (0.00s)
=== RUN   TestCommitment_match_max
--- PASS: TestCommitment_match_max (0.00s)
=== RUN   TestCommitment_match_nonVoting
--- PASS: TestCommitment_match_nonVoting (0.00s)
=== RUN   TestCommitment_recalculate
--- PASS: TestCommitment_recalculate (0.00s)
=== RUN   TestCommitment_recalculate_startIndex
--- PASS: TestCommitment_recalculate_startIndex (0.00s)
=== RUN   TestCommitment_noVoterSanity
--- PASS: TestCommitment_noVoterSanity (0.00s)
=== RUN   TestCommitment_singleVoter
--- PASS: TestCommitment_singleVoter (0.00s)
=== RUN   TestConfiguration_Configuration_Clone
--- PASS: TestConfiguration_Configuration_Clone (0.00s)
=== RUN   TestConfiguration_configurations_Clone
--- PASS: TestConfiguration_configurations_Clone (0.00s)
=== RUN   TestConfiguration_hasVote
--- PASS: TestConfiguration_hasVote (0.00s)
=== RUN   TestConfiguration_checkConfiguration
--- PASS: TestConfiguration_checkConfiguration (0.00s)
=== RUN   TestConfiguration_nextConfiguration_table
--- PASS: TestConfiguration_nextConfiguration_table (0.00s)
=== RUN   TestConfiguration_nextConfiguration_prevIndex
--- PASS: TestConfiguration_nextConfiguration_prevIndex (0.00s)
=== RUN   TestConfiguration_nextConfiguration_checkConfiguration
--- PASS: TestConfiguration_nextConfiguration_checkConfiguration (0.00s)
=== RUN   TestConfiguration_encodeDecodePeers
--- PASS: TestConfiguration_encodeDecodePeers (0.00s)
=== RUN   TestConfiguration_encodeDecodeConfiguration
--- PASS: TestConfiguration_encodeDecodeConfiguration (0.00s)
=== RUN   TestDiscardSnapshotStoreImpl
--- PASS: TestDiscardSnapshotStoreImpl (0.00s)
=== RUN   TestDiscardSnapshotSinkImpl
--- PASS: TestDiscardSnapshotSinkImpl (0.00s)
=== RUN   TestFileSnapshotStoreImpl
--- PASS: TestFileSnapshotStoreImpl (0.00s)
=== RUN   TestFileSnapshotSinkImpl
--- PASS: TestFileSnapshotSinkImpl (0.00s)
=== RUN   TestFileSS_CreateSnapshotMissingParentDir
--- PASS: TestFileSS_CreateSnapshotMissingParentDir (0.14s)
raft_test.go:101: 21:34:33.261773 [INFO] snapshot: Creating new 
snapshot at /tmp/raft068757217/raft335529164/snapshots/3-10-1533504873261.tmp
=== RUN   TestFileSS_CreateSnapshot
--- PASS: TestFileSS_CreateSnapshot (0.50s)
raft_test.go:101: 21:34:33.401289 [INFO] snapshot: Creating new 
snapshot at /tmp/raft997309883/snapshots/3-10-1533504873401.tmp
raft_test.go:101: 21:34:33.534238 [WARN] snapshot: Found temporary 
snapshot: 3-10-1533504873401.tmp
=== RUN   TestFileSS_CancelSnapshot
--- PASS: TestFileSS_CancelSnapshot (0.13s)
raft_test.go:101: 21:34:33.899206 [INFO] snapshot: Creating new 
snapshot at /tmp/raft437327838/snapshots/3-10-1533504873899.tmp
=== RUN   TestFileSS_Retention
--- PASS: TestFileSS_Retention (2.67s)
raft_test.go:101: 21:34:34.032449 [INFO] snapshot: Creating new 
snapshot at /tmp/raft011354021/snapshots/3-10-1533504874032.tmp
raft_test.go:101: 21:34:34.591751 [INFO] snapshot: Creating new 
snapshot at /tmp/raft011354021/snapshots/3-11-1533504874591.tmp
raft_test.go:101: 21:34:35.192120 [INFO] snapshot: Creating new 
snapshot at /tmp/raft011354021/snapshots/3-12-1533504875192.tmp
raft_test.go:101: 21:34:35.691391 [INFO] snapshot: reaping snapshot 
/tmp/raft011354021/snapshots/3-10-1533504874032
raft_test.go:101: 21:34:35.691859 [INFO] snapshot: Creating new 
snapshot at /tmp/raft011354021/snapshots/3-13-1533504875691.tmp
raft_test.go:101: 21:34:36.206487 [INFO] snapshot: reaping snapshot 
/tmp/raft011354021/snapshots/3-11-1533504874591
raft_test.go:101: 21:34:36.206936 [INFO] snapshot: Creating new 
snapshot at /tmp/raft011354021/snapshots/3-14-1533504876206.tmp
raft_test.go:101: 21:34:36.703417 [INFO] snapshot: reaping snapshot 

Bug#865912: smartd: please start with Type=forking to wait for successful initialisation

[Christian Franke]

See also upstream tickets:
https://www.smartmontools.org/ticket/1080
https://www.smartmontools.org/ticket/1081

Bug#905301: eject: When I want to open the CD-ROM drive, either it does nothing or the CD-ROM drive starts to open but it goes back and closes.

[Gilles CHARABOT]

# dmesg | grep cdr
[1.628450] cdrom: Uniform CD-ROM driver Revision: 3.20




# cat /proc/sys/dev/cdrom/info
CD-ROM information, Id: cdrom.c 3.20 2003/12/17

drive name: sr0
drive speed:40
drive # of slots:   1
Can close tray: 1
Can open tray:  1
Can lock tray:  1
Can change speed:   1
Can select disk:0
Can read multisession:  1
Can read MCN:   1
Reports media changed:  1
Can play audio: 1
Can write CD-R: 1
Can write CD-RW:1
Can read DVD:   1
Can write DVD-R:1
Can write DVD-RAM:  1
Can read MRW:   1
Can write MRW:  1
Can write RAM:  1





/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0
/etc/fstab (END)





# modinfo cdrom
filename:   /lib/modules/4.17.0-3-amd64/kernel/drivers/cdrom/cdrom.ko
license:GPL
depends:
retpoline:  Y
intree: Y
name:   cdrom
vermagic:   4.17.0-3-amd64 SMP mod_unload modversions 
parm:   debug:bool
parm:   autoclose:bool
parm:   autoeject:bool
parm:   lockdoor:bool
parm:   check_media_type:bool
parm:   mrw_format_restart:bool

Bug#907732: maildir-utils: May need versioned depend on libxapian30

[Mark J. Nelson]

Norbert Preining  writes:

> But 1.4.7-2 is in testing, so there is not necessarily a need for having
> a stricted dependency, as it would only complicate backporting.
>
> Upgrades from stable require full upgrade which also would bring in a
> new libxapian30, so I don't really see the need to add this.
>
> Did you have a mixed system of partially updated one?

It's a regular testing system, but yeah, partially updated. Maybe it's a
bad habit nowadays, but I got in the habit years ago, when I had a
slower internet connection, of updating software in aptitude
individually, which I also like because it lets me keep tabs on what's
pulling in what.

Usually this works fine, because if software needs a newer version of a
library it bumps the >= in the dependency, but in this case the
unversioned depends on libxapian30 meant the upgrade didn't get pulled
in. I see the point about complicating backports though, especially if
xapian's upstream isn't carefully versioning its symbols.

-Mark

-- 
Mark J. Nelson
Falmouth University
http://www.kmjn.org

Bug#907761: etcd-fs: FTBFS in buster/sid (cannot use file (type *etcdFile) as type nodefs.File in return argument)

[Santiago Vila]

Package: src:etcd-fs
Version: 0.0+git20140621.0.395eacb-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --buildsystem=golang --with=golang --builddirectory=_build
   dh_update_autotools_config -a -O--buildsystem=golang 
-O--builddirectory=_build
   dh_autoreconf -a -O--buildsystem=golang -O--builddirectory=_build
   dh_auto_configure -a -O--buildsystem=golang -O--builddirectory=_build
   dh_auto_build -a -O--buildsystem=golang -O--builddirectory=_build
cd _build && go install 
-gcflags=\"-trimpath=/<>/etcd-fs-0.0\+git20140621.0.395eacb/_build/src\"
 
-asmflags=\"-trimpath=/<>/etcd-fs-0.0\+git20140621.0.395eacb/_build/src\"
 -v -p 1 github.com/xetorthio/etcd-fs github.com/xetorthio/etcd-fs/src/etcdfs
github.com/hanwen/go-fuse/splice
golang.org/x/sys/unix
github.com/hanwen/go-fuse/fuse
github.com/hanwen/go-fuse/fuse/nodefs
github.com/hanwen/go-fuse/fuse/pathfs
github.com/coreos/go-etcd/etcd
github.com/xetorthio/etcd-fs/src/etcdfs
# github.com/xetorthio/etcd-fs/src/etcdfs
src/github.com/xetorthio/etcd-fs/src/etcdfs/file.go:21:3: cannot use file (type 
*etcdFile) as type nodefs.File in return argument:
*etcdFile does not implement nodefs.File (missing GetLk method)
dh_auto_build: cd _build && go install 
-gcflags=\"-trimpath=/<>/etcd-fs-0.0\+git20140621.0.395eacb/_build/src\"
 
-asmflags=\"-trimpath=/<>/etcd-fs-0.0\+git20140621.0.395eacb/_build/src\"
 -v -p 1 github.com/xetorthio/etcd-fs github.com/xetorthio/etcd-fs/src/etcdfs 
returned exit code 2
make: *** [debian/rules:12: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The above error also happens here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#907762: postbooks: FTBFS with Qt 5.11

[Santiago Vila]

Package: src:postbooks
Version: 4.11.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --builddirectory=. --parallel
   dh_update_autotools_config -a -O--builddirectory=. -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
# FIXME: find will not fail on error!
find . -name '*.ts' -exec lrelease {} \;
Updating './share/dict/xTuple.ja.qm'...
Generated 12957 translation(s) (10490 finished and 2467 unfinished)
Ignored 8016 untranslated source text(s)
Updating './share/dict/xTuple.fr_ca.qm'...
Generated 17547 translation(s) (15814 finished and 1733 unfinished)
Ignored 3424 untranslated source text(s)
Updating './share/dict/xTuple.et_ee.qm'...

[... snipped ...]

 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: note:   template 
argument deduction/substitution failed:
adjustmentTrans.cpp:34:89: note:   candidate expects 3 arguments, 4 provided
   connect(_adjustmentTypeGroupInt,SIGNAL(buttonClicked(int)), this, 
SLOT(sPopulateQty()));

 ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:46,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QAction:1,
 from guiclient.h:14,
 from adjustmentTrans.h:14,
 from adjustmentTrans.cpp:11:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note: candidate: 
'template static typename 
std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) 
&& (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, const QObject *context, Func2 slot,
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note:   template 
argument deduction/substitution failed:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 
'template static typename 
std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) 
&& (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType) [with Func1 = const char*; Func2 = const char*]':
adjustmentTrans.cpp:34:89:   required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: error: no type named 
'type' in 'struct std::enable_if'
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note: candidate: 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, Func2)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, Func2 slot)
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note:   template 
argument deduction/substitution failed:
adjustmentTrans.cpp:34:89: note:   candidate expects 3 arguments, 4 provided
   connect(_adjustmentTypeGroupInt,SIGNAL(buttonClicked(int)), this, 
SLOT(sPopulateQty()));

 ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:46,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QAction:1,
 from guiclient.h:14,
 from adjustmentTrans.h:14,
 from adjustmentTrans.cpp:11:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:308:13: note: candidate: 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, const QObject *context, Func2 slot,
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:308:13: note:   template 
argument deduction/substitution failed:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 

Bug#903783: fixed in minissdpd 1.5.20180223-3

[Adrian Immanuel Kieß]

Dear Maintainer,

thank you for closing this bug.

Sincerely yours,

Adrian

On Sun, 19 Aug 2018 22:23:48 + Yangfl  wrote:
> Source: minissdpd
> Source-Version: 1.5.20180223-3
> 
> We believe that the bug you reported is fixed in the latest version
of
> minissdpd, which is due to be installed in the Debian FTP archive.
> 
> A summary of the changes between this version and the previous one is
> attached.
> 
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 903...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Yangfl  (supplier of updated minissdpd package)
> 
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Thu, 26 Jul 2018 20:39:35 +0800
> Source: minissdpd
> Binary: minissdpd
> Architecture: source amd64
> Version: 1.5.20180223-3
> Distribution: unstable
> Urgency: medium
> Maintainer: Thomas Goirand 
> Changed-By: Yangfl 
> Description:
>  minissdpd  - keep memory of all UPnP devices that announced
themselves
> Closes: 901605 901658 903357 903783 905758
> Changes:
>  minissdpd (1.5.20180223-3) unstable; urgency=medium
>  .
>* debian/minissdpd.config: Always prefer configs in debconf to
prevent config
>  loss during fresh installation (Closes: #901605, #903783).
>* debian/rules: Disable auto enabling systemd service (Closes:
#901658).
>* Add Debconf translations, with thanks to:
>  - Brazilian Portuguese, Adriano Rafael Gomes (Closes: #903357).
>  - German, Helge Kreutzmann (Closes: #905758).
>* Bump Standards-Version to 4.2.0.
> Checksums-Sha1:
>  145d4fac0e138f693b37eb87cfd12d456f8823a4 2042
minissdpd_1.5.20180223-3.dsc
>  bdf1aca97fcd215299c49d6de3c102c46680b5fc 11516
minissdpd_1.5.20180223-3.debian.tar.xz
>  0c2a97f3e5bcd8fb71f2e76e9b9f0d8dd9ad8ada 63184 minissdpd-
dbgsym_1.5.20180223-3_amd64.deb
>  68bc83faec9195952bcf23d44f20b5ec5e313ad1 6028
minissdpd_1.5.20180223-3_amd64.buildinfo
>  15e37f4be4f9fcde4718b2bd67cb7107e4bd8405 31732
minissdpd_1.5.20180223-3_amd64.deb
> Checksums-Sha256:
>  8497de6c54901a1d704c457a7525b1498a46b4f7a3f7e3d7e9f609639c58df30
2042 minissdpd_1.5.20180223-3.dsc
>  af5b4ef8bf688a65814d3cb495697d976132eabfd0d04d60e694cc387e65f1d8
11516 minissdpd_1.5.20180223-3.debian.tar.xz
>  117b2de641671c1d7d41f0283d4ce79409143ef2a9c59958a4f2e14fb90922ba
63184 minissdpd-dbgsym_1.5.20180223-3_amd64.deb
>  517f0e3ef1a1284727a072c5fd6e3181a4a2e27df5b28f4423b5ac7b50efae09
6028 minissdpd_1.5.20180223-3_amd64.buildinfo
>  e2510e8daa9d2f9b25cd3910bbdef02ec5263868a36ab7b1566981a7aa439f87
31732 minissdpd_1.5.20180223-3_amd64.deb
-- 
With many greetings from Leipzig, Germany.
Adrian Immanuel Kieß 

Gothaer Straße 34
D-04155 Leipzig

Administrator & programmer
Unix ∧ Perl ∧ Java ∧ LaTeX

 — < adr...@kiess.onl >
 — https://www.kiess.onl # Dem Ingenieur ist nichts zu schwör
☕ — https://gedankenlautwerden.kiess.onl # Site for people who hear voices
 — https://arosusi.kiess.onl # Nickpage of Adrian Immanuel Kieß

--SYSTEM--
echo "Your fortune cookie: " && /usr/games/fortune -c -s
> (perl) % Obviously I was either onto something, or on something. -- Larry 
> Wall on the creation of Perl

echo "KIESS.ONL uptime: " && /usr/bin/uptime
> 17:04:20 up 8 days, 3:07, 7 users, load average: 1.48, 1.48, 1.80



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

Bug#907760: hgview FTBFS with mercurial 4.7

[Adrian Bunk]

Source: hgview
Version: 1.9.0-1.1
Severity: serious
Tags: buster sid ftbfs

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

...
 fakeroot debian/rules clean
dh clean
   dh_auto_clean
dh_auto_clean: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_clean: This feature will be removed in compat 12.
python setup.py clean -a
Traceback (most recent call last):
  File "setup.py", line 60, in 
from hgviewlib.__pkginfo__ import modname, version, license, description, \
  File "/build/1st/hgview-1.9.0/hgviewlib/__init__.py", line 26, in 
demandimport.ignore.append('roman')
AttributeError: 'module' object has no attribute 'ignore'
dh_auto_clean: python setup.py clean -a returned exit code 1
make: *** [debian/rules:18: clean] Error 1

Bug#907737: liblucy-perl: Project Lucy has retired

[Jonas Smedegaard]

Quoting Xavier Guimard (2018-09-01 08:46:22)
> Package: liblucy-perl
> Version: Project Lucy has retired
> Severity: important
> 
> As announced in http://lucy.apache.org/, project Lucy has retired. I
> think we should remove it from buster

liblucy-perl has two reverse dependencies:

  * openguides
  * libcatmandu-store-lucy-perl

It is fine by me to drop libcatmandu-store-lucy-perl with liblucy-perl: 
Other Catmandu search backends exist but need to be packaged, but 
shipping no Catmandu search backend is better than shipping a backend 
dead upstream!

@Dominique: Is it ok to drop openguides, or can it be made to not depend 
on liblucy-perl?


 - Jonas

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

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


signature.asc
Description: signature

Bug#907668: dicoweb: Search feature does not work

[أحمد المحمودي]

Description of python-memcached package:
This software is a 100% Python interface to the memcached memory cache 
daemon. It is the client side software which allows storing values in 
one or more, possibly remote, memcached servers.

it seems that the support of *remote* memcached servers, is why the 
package only suggests memcached. Hence I can't enforce a dependency on 
memcached, instead the user needs to install himself if he decides to 
use a local memcached. But I will add it to recommends.

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#874085: smartmontools: [smartd.conf] UNRECOGNIZED OPTION: U

[Christian Franke]

There is no smartd command line option -U (see 'smartd -h' or 'man 
smartd') but a smartd.conf directive -U (see 'smartd -D' or 'man 
smartd.conf').


Conclusion: Place '-U 198+' in the file /etc/smartd.conf instead.

Bug#906355: dh_webext: SyntaxError: invalid syntax

[Juhani Numminen]

Control: notfound -1 2.0.3.2+dfsg-1
Control: reassign -1 mozilla-devscripts
Control: found -1 mozilla-devscripts/0.49
Control: retitle -1 dh_webext: SyntaxError: invalid syntax

On Fri, 17 Aug 2018 11:19:38 + Santiago Vila  wrote:> I 
tried to build this package in buster but it failed:
> 
> [...]
>  debian/rules build-indep
> dh build-indep --with webext
>dh_update_autotools_config -i
>dh_autoreconf -i
>create-stamp debian/debhelper-build-stamp
>  fakeroot debian/rules binary-indep
> dh binary-indep --with webext
>dh_testroot -i
>dh_prep -i
>debian/rules override_dh_webext
> make[1]: Entering directory '/<>/form-history-control-2.0.3.2+dfsg'
> dh_webext . form-history-control
>   File "/usr/bin/dh_webext", line 64
> print(self_script + ":", *args)
>  ^
> SyntaxError: invalid syntax
[...]
> The build was made with "dpkg-buildpackage -A" in my autobuilder.
> Most probably, it also fails here in reproducible builds:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/form-history-control.html

Dear maintainer,

Reassigning to mozilla-devscripts since dh_webext causes the FTBFS
in form-history-control.

Trying to invoke dh_webext on my system running testing looks like this:

$ dh_webext
  File "/usr/bin/dh_webext", line 64
print(self_script + ":", *args)
 ^
SyntaxError: invalid syntax

$ dh_webext --help
  File "/usr/bin/dh_webext", line 64
print(self_script + ":", *args)
 ^
SyntaxError: invalid syntax

Python 3 interpreter works a bit better:

$ python3 /usr/bin/dh_webext
usage: dh_webext [-h] [-p PACKAGE] [-I ARG] [-v] PATH [NAME]
dh_webext: error: the following arguments are required: PATH

$ python3 /usr/bin/dh_webext --help
usage: dh_webext [-h] [-p PACKAGE] [-I ARG] [-v] PATH [NAME]

Debhelper command to install an unpacked WebExtension

positional arguments:
  PATH  Path to the main directory. (Default: .)
  NAME  Short name of the extension.

optional arguments:
  -h, --helpshow this help message and exit
  -p PACKAGE, --package PACKAGE
calculate substvars only for the specified PACKAGE
  -I ARG, --dh-install-arg ARG
extra arguments to pass to dh_install
  -v, --verbose print more information


With best regards,
Juhani

Bug#897642: RFS: gpgme1.0/1.11.1-1~bpo9+1

[Jacob Adams]

control: tag -1 -moreinfo

> On Sep 1, 2018, at 04:49, Roger Shimizu  wrote:
> 
> control: tag -1 +moreinfo
> 
> Dear Jacob,
> 
>> On Fri, May 4, 2018 at 3:27 AM, Jacob Adams  wrote:
>> Package: sponsorship-requests
>> Severity: normal
>> 
>>  Dear mentors,
>> 
>>  I am looking for a sponsor for my package "gpgme1.0"
> 
> Thanks for your interest in contribution to debian!
> 
>>  Changes since the last upload:
>> 
>> gpgme1.0 (1.11.1-1~bpo9+1) stretch-backports; urgency=medium
>> 
>>  * Rebuild for stretch-backports.
>> 
>> -- Jacob Adams   Thu, 26 Apr 2018 13:13:54 -0400
>> 
>> 
>> This package will also require libgpgerror, which you can find here:
>> 
>> https://mentors.debian.net/package/libgpg-error
>> 
>> https://mentors.debian.net/debian/pool/main/libg/libgpg-error/libgpg-error_1.29-4~bpo9+1.dsc
>> 
>> It already has an RFS: #897045
>> 
>> I would like to be able to use the latest version of GPGME in my GSoC
>> 2018 project. In order to do that I would prefer to use a backport as
>> the PGP Clean Room CD is based off of stretch.
> 
> I see the project seems already released as beta [1], so maybe there's
> no need to do this backports upload?

My project does require a newer version of GPGME than is shipped in stretch. 
However, I didn’t want to wait on the backport, so I’ve been including the deb 
files directly in my build:
https://salsa.debian.org/tookmund-guest/make-pgp-clean-room/tree/master/resources/config/packages.chroot

> 
> And what's the benefit for this backports pkg? Any new feature or
> bugfix you're particularly interested in?

There has been significant improvement in GPGME’s python binding since stretch, 
and my project relies on these features, such as the new key generation 
function. 

It would be nice to be able to pull these packages from backports instead of 
including them directly. 

Thanks,
Jacob

Bug#907756: freecol: multiple warnings from AppStream metadata

[Jeremy Bicha]

On Sat, Sep 1, 2018 at 9:23 AM Markus Koschany  wrote:
>
> Am 01.09.2018 um 14:53 schrieb Jeremy Bicha:
> [...]
> > In my testing, these issues seem to prevent FreeCol from showing up in
> > the GNOME Software app.
>
> Just tested it with GNOME Software in Buster. FreeCol shows up there.

Make sure you try when FreeCol is not already installed.

I hesitated submitting a patch because I wanted to test the Appstream
metadata on Ubuntu first but Ubuntu's Appstream service isn't
generating updates right now.

Thanks,
Jeremy Bicha

Bug#902221: Bug#895046: RM: vgabios -- ROM; an old not-used-anymore package

[Stephen Kitt]

Control: retitle 745170 ITA: vgabios -- VGA BIOS software for the Bochs 
emulated VGA card
Control: owner 745170 !
Control: retitle 902221 Bochs should use SeaBIOS instead of VGABios
Control: severity 902221 wishlist

On Fri, Apr 06, 2018 at 02:07:45PM -0400, Scott Kitterman wrote:
> On Friday, April 06, 2018 05:31:10 PM Michael Tokarev wrote:
> > 06.04.2018 17:27, Michael Tokarev пишет:
> > > Package: ftp.debian.org
> > > Severity: normal
> > > 
> > > This package was used by old qemu/kvm. Now qemu, for a very long time now
> > > (several debian releases) uses vgabios from seabios package, so that
> > > vgabios isn't needed anymore.
> > 
> > Hmm. Bochs is using it. Which is orphan but still present in Debian... Oh
> > well..
> > 
> > /mjt
> 
> That'll need to be addressed first then.

I’ve been trying to get Bochs to work consistently with SeaBIOS,
without success so far. So I’ll adopt VGABios, which has seen some
recent activity upstream, and continue trying to switch away from it.

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#907667: lintian: should html escape output if --color=html is used

[Niels Thykier]

Chris Lamb:
> Hi Niels,
> 
>> Any reason for introducing the CGI dependency over simply applying the
>> same escape rules for the $information variable?
> 
> Only because well-used libraries are preferred, particularly for data
> sanitisation (!) operations.
> 
> Is the extra dependency problematic? We use some far-more esoteric
> libraries than CGI, so I did not think it would be an issue.
> 
> 
> Regards,
> 

If we are consistent with how we perform the quoting, I do not mind the
extra dependency.  Particularly because it should be doable to reduce it
to a suggests given --color=html is not a default (which we can add
later if relevant).

Though, reminder - if you introduce a new dependency, you will have to
get DSA to install it on lindsay.d.o before you can upgrade lintian there.

Thanks,
~Niels

Bug#907729: knot-resolver: kresd fails on arm64 with "PANIC: unprotected error in call to Lua API (bad light userdata pointer)"

[Daniel Kahn Gillmor]

On Fri 2018-08-31 19:53:42 -0400, Daniel Kahn Gillmor wrote:
> On the arm64 build daemons, kresd fails with the error:
>
>  PANIC: unprotected error in call to Lua API (bad light userdata pointer)
>
> https://buildd.debian.org/status/fetch.php?pkg=knot-resolver=arm64=3.0.0-4=1535740254=0
>
> This happens despite all the official upstream test suites passing.
>
> This same failure causes the test suite for hddemux 0.4-5 to fail on
> this platform, which is why i'm marking this bug as affecting hddemux.
>
> The error message seems to be derived from LJ_ERR_BADLU, which i think
> is raised by the checklightudptr within luajit, from either
> lua_pushlightuserdata() or lua_cpcall() [0].  i have not tracked down
> the specific instance yet (i'm not on an arm64 machine at the moment).
> But as the knot-resolver codebase never invokes lua_cpcall(), i suspect it
> is lua_pushlightuserdata() that is causing the crash.

here's what i'm seeing on amdahl, the debian arm64 porterbox, where
kresd.conf is an empty file:

0 $ gdb /usr/sbin/kresd
GNU gdb (Debian 8.1-4) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/kresd...Reading symbols from 
/usr/lib/debug/.build-id/76/a5136c4d835203c93718fa64f4a252b5a8f499.debug...done.
done.
(gdb) break lua_pushlightuserdata
Breakpoint 1 at 0x6f44
(gdb) run -c kresd.conf
Starting program: /usr/sbin/kresd -c kresd.conf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".

Breakpoint 1, lua_pushlightuserdata (L=0x2dbdd75cd378, 
p=p@entry=0xf038) at lj_api.c:699
699 lj_api.c: No such file or directory.
(gdb) bt
#0  lua_pushlightuserdata (L=0x2dbdd75cd378, p=p@entry=0xf038) at 
lj_api.c:699
#1  0xaaab594c in init_state (engine=0xf038) at 
daemon/engine.c:679
#2  engine_init (engine=0xf038, pool=0xef80) at 
daemon/engine.c:722
#3  0xaaab2348 in main (argc=, argv=) at 
daemon/main.c:680
(gdb) cont
Continuing.
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
[Inferior 1 (process 4706) exited with code 01]
(gdb) 


by contrast, on amd64, i see it continuing after the first invocation
with no problem:

$ gdb /usr/sbin/kresd 
GNU gdb (Debian 8.1-4) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/kresd...Reading symbols from 
/usr/lib/debug/.build-id/19/ab3dcf739a6495245566f5c7692a180a3bfff1.debug...done.
done.
(gdb) break lua_pushlightuserdata
Breakpoint 1 at 0x76f0
(gdb) run -c kresd.conf
Starting program: /usr/sbin/kresd -c kresd.conf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Breakpoint 1, lua_pushlightuserdata (L=0x4378, p=0x7fffdfd0)
at lj_api.c:699
699 lj_api.c: No such file or directory.
(gdb) bt
#0  lua_pushlightuserdata (L=0x4378, p=0x7fffdfd0) at lj_api.c:699
#1  0x555606b3 in init_state (engine=0x7fffdfd0) at 
daemon/engine.c:679
#2  engine_init (engine=0x7fffdfd0, pool=) at 
daemon/engine.c:722
#3  0xcc12 in main (argc=, argv=) at 
daemon/main.c:680
(gdb) cont
Continuing.

Breakpoint 1, lua_pushlightuserdata (L=0x4378, p=p@entry=0x759a8010) at 
lj_api.c:699
699 in lj_api.c
(gdb) cont


perhaps someone who knows lua better than me can make an even simpler
reproducer?

--dkg

Bug#895614: the fontconfig error comes almost everywhere.

[shirish शिरीष]

Reply in-line :-

On 01/09/2018, Peter Nowee  wrote:
> @Shirish:
>

@Peter Nowee,

> I'm not sure if you are seeing the same problem as the original poster
> of this bug report, but I had the same problem you describe: The error
> `Fontconfig error: failed reading config file` appearing exactly 5
> times. I could reproduce it by running `fc-cache`.
>
> Through the links below, I found it was caused by Debian bugs #854166
> and #866052, related to 5 packages: fonts-beng-extra, fonts-deva-extra,
> fonts-gujr-extra, fonts-guru-extra and fonts-orya-extra. (In my case,
> these fonts got installed as dependencies of tuxtype.)
>
> After manually reorganizing /etc/fonts/conf.avail/ to match the goal
> described in #866052, the error messages disappeared.

At my end it isn't the case as I do not get the older packages
left-over. This is/was a new install.

My /etc/fonts/conf.avail/ shows no font directories underneath.

Also doing

$ fc-cache and $ fc-cache --verbose doesn't show anything but I do see
that fontconfig issue flare up every now and then .

I did see https://gitlab.freedesktop.org/fontconfig/fontconfig/commits/master
and specifically

https://gitlab.freedesktop.org/fontconfig/fontconfig/commit/cfb21c7d85d2b1fc457dcd644e6b850b5cccf26a

which ensures that in the future we at least will know from where the
issue is arising.  The latest release which upstream has released i.e.
2.13.1 should give us more info. provided somebody does an NMU upload
of the patch shared in #906380 and we should be ready for the new
release from upstream

Sources -

https://gitlab.freedesktop.org/fontconfig/fontconfig/tree/master
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906380

I am hopeful both of these get in before freeze is in place

https://nthykier.wordpress.com/2018/08/06/buster-is-headed-for-a-long-hard-freeze/

>
> HTH,
> Peter
>
> Sources:
> -
> https://unix.stackexchange.com/questions/454130/how-to-fix-fontconfig-error-failed-reading-config-file
> - https://bugs.freedesktop.org/show_bug.cgi?id=106497
> - https://bugs.debian.org/854166
> - https://bugs.debian.org/866052
>
> --
> To unsubscribe, send mail to 895614-unsubscr...@bugs.debian.org.
>


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#907759: taopm in unstable is broken

[Adrian Bunk]

Package: taopm
Version: 1.0-4
Severity: serious

$ tao test

|Tao (c) 1996-2000 Mark Pearson|
| Sound Synthesis with Physical Models |


Parsing "test.tao"

Error in line 3 of "test.tao": 
Circle c(800 Hz
 ^
If this error message doesn't help, try checking
for missing ;'s or ...'s on, or just before line 3
/usr/bin/tao: 113: /usr/bin/tao: Syntax error: Bad fd number
$ 


Works after downgrading the to package in stretch.

Bug#789129: closed by Tiago Bortoletto Vaz (Bug#789129: fixed in taopm 1.0-4)

[Adrian Bunk]

Control: reopen -1

On Tue, Jul 31, 2018 at 12:09:05PM +, Debian Bug Tracking System wrote:
>...
>  taopm (1.0-4) unstable; urgency=medium
>  .
>* Depends on libxi-dev. Thanks to Philip Chung & John O'Hagan.
>  (Closes: #789129)
>...

This added a build dependency, not a dependency.

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#907718: python-dateutil breaks python-vobject autopkgtest

[Guido Günther]

Hi,
On Sat, Sep 01, 2018 at 02:54:25PM +0300, Adrian Bunk wrote:
> Control: reassign -1 src:python-dateutil 2.7.3-1
> Control: retitle -1 python-dateutil: RRULE UNTIL values must be specified in 
> UTC when DTSTART is timezone-aware
> Control: severity -1 serious
> Control: affects -1 python-dateutil python3-dateutil src:python-vobject 
> src:python-icalendar

Thanks!

> 
> On Fri, Aug 31, 2018 at 09:41:32PM +0200, Paul Gevers wrote:
> > Source: python-dateutil, python-vobject
> > Control: found -1 python-dateutil/2.7.3-1
> > Control: found -1 python-vobject/0.9.5-2
> > X-Debbugs-CC: debian...@lists.debian.org
> > User: debian...@lists.debian.org
> > Usertags: breaks needs-update
> > 
> > Dear maintainers,
> > 
> > With a recent upload of python-dateutil the autopkgtest of
> > python-vobject started to fail in testing. I copied some of the output
> > below.
> >...
> 
> This also causes FTBFS, the first two seen are:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-icalendar.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-vobject.html
> 
> I strongly suspect that there will also be runtime issues with other 
> packages using python-dateutil currently in stretch and buster, so even 
> in case this is considered a bug in reverse dependencies there will 
> still be Breaks required in python{,3}-dateutil against packages in 
> stretch and buster that got broken (unless it was only a broken test).

This was broken by efba12d3 due to

https://github.com/dateutil/dateutil/issues/620

so we likely want reverse deps to catch up and fix this.
Cheers,
 -- Guido

Bug#907732: maildir-utils: May need versioned depend on libxapian30

[Norbert Preining]

Hi Mark,

> Since I suspected this was some kind of mu/xapian version mismatch error, I 
> upgraded libxapian30 from 1.4.5-1 to 1.4.7-2, which fixed the issue. 
> Therefore I suspect that a more narrowly 
> versioned depends is necessary.

But 1.4.7-2 is in testing, so there is not necessarily a need for having
a stricted dependency, as it would only complicate backporting.

Upgrades from stable require full upgrade which also would bring in a
new libxapian30, so I don't really see the need to add this.

Did you have a mixed system of partially updated one?

Thanks

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#907755: rsyslog: Pattern for logcheck no longer matches

[Michael Biebl]

Control: forwarded -1 https://github.com/rsyslog/rsyslog/issues/2979
On 9/1/18 14:57, Michael Biebl wrote:

>> The pattern for rsyslog are displayed. Reason is that 
>> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
>> swVersion="[0-9.]+" x-pid="[0-9]+" 

> Hm, maybe a better fix is to no add two spaces in the first place.

Filed https://github.com/rsyslog/rsyslog/issues/2979 for that.
Let's see what upstream has to say.


-- 
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#907756: freecol: multiple warnings from AppStream metadata

[Markus Koschany]

Am 01.09.2018 um 14:53 schrieb Jeremy Bicha:
[...]
> In my testing, these issues seem to prevent FreeCol from showing up in
> the GNOME Software app.

Just tested it with GNOME Software in Buster. FreeCol shows up there.





signature.asc
Description: OpenPGP digital signature

Bug#907758: taopm: Please add a real package as alternative to c++-compiler

[Adrian Bunk]

Package: taopm
Version: 1.0-4
Severity: important

Depending on a virtual package provided by several packages
without specifying one package as first alternative can
cause problems in various places.

Please change
  Depends: ..., c++-compiler
to
  Depends: ..., g++ | c++-compiler

Bug#907756: freecol: multiple warnings from AppStream metadata

[Markus Koschany]

Am 01.09.2018 um 14:53 schrieb Jeremy Bicha:
> Source: freecol
> Version: 0.11.6+dfsg2-2
> 
> There are still multiple issues with the Appstream metadata for
> freecol. See the reference below.
> 
> In my testing, these issues seem to prevent FreeCol from showing up in
> the GNOME Software app.
> 
> Honestly, I'm not too concerned about the reverse domain name style
> for the id, but the other issues shouldn't be too difficult to solve.
> 
> update_contact
> The screenshot should be in an image tag.
> 
> References
> 
> https://appstream.debian.org/sid/main/issues/freecol.html
> 
> https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-screenshots

I am pretty sure that I used the appstreamcli tool to validate the
appstream file and it didn't show any errors back then. At the moment

https://appstream.debian.org/sid/main/issues/freecol.html

shows only warnings. Why are they fatal? In my opinion GNOME Software
app should fallback to the desktop file if it encounters any serious
issues. At least the icon would show up this way.

When I run

appstreamcli validate /usr/share/metainfo/freecol.appdata.xml in Buster,
I get four errors and one warning now. Even the reverse domain-name is
an error...

I accept patches to fix this.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#907755: rsyslog: Pattern for logcheck no longer matches

[Helge Kreutzmann]

Hello Michael,
On Sat, Sep 01, 2018 at 03:05:14PM +0200, Michael Biebl wrote:
> On 9/1/18 14:49, Helge Kreutzmann wrote:
> > Package: rsyslog
> > Version: 8.37.0-2
> > Severity: normal
> > 
> > The pattern for rsyslog are displayed. Reason is that 
> > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> > swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] start$
> > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> > swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] 
> > exiting on signal [0-9]+.$
> > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> > swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] 
> > rsyslogd was HUPed$
> > 
> > is missing a space (there are two spaces) after rsyslogd:
> 
> This most have been broken for a really long time and apparently went
> unnoticed, which makes me wonder if I shouldn't just dropped the
> logcheck rules from the rsyslog package. I'm not using logcheck myself,
> so I feel uncomfortable shipping stuff that no-one really cares about.

Yes, it is broken for quite some time, so far I only fixed it locally
but I finally decided to report it. So it is my fault for not
reporting this earlier (I thought it was so minor, sorry).

So, if possible, keep the logcheck rules, it is really appreciated.
And they do not harm people not using logcheck.

Thanks.

Greetings

 Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#907757: libedataserverui1.2-dev: missing dependency on libecal1.2-dev

[Adrian Bunk]

Package: libedataserverui1.2-dev
Version: 3.29.92-1
Severity: serious
Control: affects -1 src:gnome-contacts

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

...
Called `/usr/bin/pkg-config --cflags libedataserverui-1.2` -> 1


meson.build:44:0: ERROR:  Could not generate cargs for libedataserverui-1.2:


dh_auto_configure: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu 
--libexecdir=lib/x86_64-linux-gnu --libexecdir=/usr/lib/gnome-contacts 
-Dwith-cheese=yes returned exit code 1
make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2

Bug#907755: rsyslog: Pattern for logcheck no longer matches

[Michael Biebl]

On 9/1/18 14:49, Helge Kreutzmann wrote:
> Package: rsyslog
> Version: 8.37.0-2
> Severity: normal
> 
> The pattern for rsyslog are displayed. Reason is that 
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] start$
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] exiting 
> on signal [0-9]+.$
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] rsyslogd 
> was HUPed$
> 
> is missing a space (there are two spaces) after rsyslogd:

This most have been broken for a really long time and apparently went
unnoticed, which makes me wonder if I shouldn't just dropped the
logcheck rules from the rsyslog package. I'm not using logcheck myself,
so I feel uncomfortable shipping stuff that no-one really cares about.


-- 
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#907755: rsyslog: Pattern for logcheck no longer matches

[Helge Kreutzmann]

On Sat, Sep 01, 2018 at 02:57:59PM +0200, Michael Biebl wrote:
> On 9/1/18 14:49, Helge Kreutzmann wrote:
> > Package: rsyslog
> > Version: 8.37.0-2
> > Severity: normal
> > 
> > The pattern for rsyslog are displayed. Reason is that 
> > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> > swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] start$
> > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> > swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] 
> > exiting on signal [0-9]+.$
> > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> > swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] 
> > rsyslogd was HUPed$
> > 
> > is missing a space (there are two spaces) after rsyslogd:
> 
> Hm, maybe a better fix is to no add two spaces in the first place.

There are two options: either rsyslogd emits only one space after the
colon, then the logcheck pattern can stay as is or the log check
pattern needs an additional space.

For the latter I can provide a patch, but not for the former.

Greetings

 Helge


-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#907755: rsyslog: Pattern for logcheck no longer matches

[Helge Kreutzmann]

Hello Michael,
On Sat, Sep 01, 2018 at 02:53:37PM +0200, Michael Biebl wrote:
> On 9/1/18 14:49, Helge Kreutzmann wrote:
> > Package: rsyslog
> > Version: 8.37.0-2
> > Severity: normal
> > 
> > The pattern for rsyslog are displayed. Reason is that 
> > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> > swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] start$
> > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> > swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] 
> > exiting on signal [0-9]+.$
> > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> > swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] 
> > rsyslogd was HUPed$
> > 
> > is missing a space (there are two spaces) after rsyslogd:
> > 
> 
> Can you please send a merge request at
> https://salsa.debian.org/debian/rsyslog
> with your proposed changes.

Wow. Thanks for your ultrafast reply.

However, I'm a bit lost at your request. I do not have any repository
for rsyslog nor I'm sure how I would go about creating such merge
request[1]. Would it be possible that I send you a patch, or the updated
file?

Greetings

 Helge

[1] Sure, I can probably search on the net, find an explanation and
hopefully do every step right, but for roundabout 4 space
characters this is a lot of work.



-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#907755: rsyslog: Pattern for logcheck no longer matches

[Michael Biebl]

On 9/1/18 14:49, Helge Kreutzmann wrote:
> Package: rsyslog
> Version: 8.37.0-2
> Severity: normal
> 
> The pattern for rsyslog are displayed. Reason is that 
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] start$
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] exiting 
> on signal [0-9]+.$
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] rsyslogd 
> was HUPed$
> 
> is missing a space (there are two spaces) after rsyslogd:

Hm, maybe a better fix is to no add two spaces in the first place.


-- 
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#907756: freecol: multiple warnings from AppStream metadata

[Jeremy Bicha]

Source: freecol
Version: 0.11.6+dfsg2-2

There are still multiple issues with the Appstream metadata for
freecol. See the reference below.

In my testing, these issues seem to prevent FreeCol from showing up in
the GNOME Software app.

Honestly, I'm not too concerned about the reverse domain name style
for the id, but the other issues shouldn't be too difficult to solve.

update_contact
The screenshot should be in an image tag.

References

https://appstream.debian.org/sid/main/issues/freecol.html

https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-screenshots

Thanks,
Jeremy Bicha

Bug#907755: rsyslog: Pattern for logcheck no longer matches

[Michael Biebl]

On 9/1/18 14:49, Helge Kreutzmann wrote:
> Package: rsyslog
> Version: 8.37.0-2
> Severity: normal
> 
> The pattern for rsyslog are displayed. Reason is that 
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] start$
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] exiting 
> on signal [0-9]+.$
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
> swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] rsyslogd 
> was HUPed$
> 
> is missing a space (there are two spaces) after rsyslogd:
> 

Can you please send a merge request at
https://salsa.debian.org/debian/rsyslog
with your proposed changes.

Thanks,
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#907754: webdis: FTBFS on i386, mips64el

[Mattia Rizzolo]

Source: webdis
Version: 0.1.4+dfsg-1
Severity: serious

Dear maintainer,

the package FTBFS on the buildds on i386 and mips64el:

https://buildd.debian.org/status/fetch.php?pkg=webdis=i386=0.1.4%2Bdfsg-1=1535395313=0
|...
|   debian/rules override_dh_auto_test
|make[1]: Entering directory '/<>/webdis-0.1.4+dfsg'
|/<>/webdis-0.1.4+dfsg/debian/test.sh /usr/bin/make test
|Generating config files..
|Starting redis-server..
|25930:C 27 Aug 18:41:41.949 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
|25930:C 27 Aug 18:41:41.950 # Redis version=4.0.11, bits=32, commit=, 
modified=0, pid=25930, just started
|25930:C 27 Aug 18:41:41.950 # Configuration loaded
|Starting webdis..
|webdis is listening on port 44739
|Running test commands: /usr/bin/make test
|make[2]: Entering directory '/<>/webdis-0.1.4+dfsg'
|python tests/basic.py
|..EE..
|==
|ERROR: test_list (__main__.TestCustom)
|List responses with custom format
|--
|Traceback (most recent call last):
|  File "tests/basic.py", line 95, in test_list
|self.query('RPUSH/hello/a/b/c')
|  File "tests/basic.py", line 20, in query
|return urllib2.urlopen(r)
|  File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
|return opener.open(url, data, timeout)
|  File "/usr/lib/python2.7/urllib2.py", line 435, in open
|response = meth(req, response)
|  File "/usr/lib/python2.7/urllib2.py", line 548, in http_response
|'http', request, response, code, msg, hdrs)
|  File "/usr/lib/python2.7/urllib2.py", line 473, in error
|return self._call_chain(*args)
|  File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
|result = func(*args)
|  File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default
|raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
|HTTPError: HTTP Error 503: Service Unavailable
|
|==
|ERROR: test_separator (__main__.TestCustom)
|Separator in list responses with custom format
|--
|Traceback (most recent call last):
|  File "tests/basic.py", line 103, in test_separator
|self.query('RPUSH/hello/a/b/c')
|  File "tests/basic.py", line 20, in query
|return urllib2.urlopen(r)
|  File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
|return opener.open(url, data, timeout)
|  File "/usr/lib/python2.7/urllib2.py", line 435, in open
|response = meth(req, response)
|  File "/usr/lib/python2.7/urllib2.py", line 548, in http_response
|'http', request, response, code, msg, hdrs)
|  File "/usr/lib/python2.7/urllib2.py", line 473, in error
|return self._call_chain(*args)
|  File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
|result = func(*args)
|  File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default
|raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
|HTTPError: HTTP Error 503: Service Unavailable
|
|--
|Ran 22 tests in 0.062s
|
|FAILED (errors=2)
|make[2]: *** [Makefile:66: test] Error 1
|make[2]: Leaving directory '/<>/webdis-0.1.4+dfsg'
|Shutting down webdis..
|Stopped webdis (pid 25933).
|Shutting down redis-server..
|Stopped redis-server (pid 25931).
|make[1]: *** [debian/rules:39: override_dh_auto_test] Error 2
|make[1]: Leaving directory '/<>/webdis-0.1.4+dfsg'
|make: *** [debian/rules:19: binary-arch] Error 2
|dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


https://buildd.debian.org/status/fetch.php?pkg=webdis=mips64el=0.1.4%2Bdfsg-1=1535805316=0
|...
|   debian/rules override_dh_auto_test
|make[1]: Entering directory '/<>/webdis-0.1.4+dfsg'
|/<>/webdis-0.1.4+dfsg/debian/test.sh /usr/bin/make test
|Generating config files..
|Starting redis-server..
|6182:C 01 Sep 10:04:49.962 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
|6182:C 01 Sep 10:04:49.962 # Redis version=4.0.11, bits=64, commit=, 
modified=0, pid=6182, just started
|6182:C 01 Sep 10:04:49.962 # Configuration loaded
|Starting webdis..
|webdis is listening on port 44557
|Running test commands: /usr/bin/make test
|make[2]: Entering directory '/<>/webdis-0.1.4+dfsg'
|python tests/basic.py
|..
|--
|Ran 22 tests in 0.273s
|
|OK
|python tests/limits.py
|..
|--
|Ran 2 tests in 2.629s
|
|OK
|./tests/pubsub -p 44557
|E: Build killed with signal TERM after 150 minutes of inactivity


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  

Bug#907755: rsyslog: Pattern for logcheck no longer matches

[Helge Kreutzmann]

Package: rsyslog
Version: 8.37.0-2
Severity: normal

The pattern for rsyslog are displayed. Reason is that 
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] start$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] exiting on 
signal [0-9]+.$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" 
swVersion="[0-9.]+" x-pid="[0-9]+" x-info="http://www.rsyslog.com"\] rsyslogd 
was HUPed$

is missing a space (there are two spaces) after rsyslogd:


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

Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rsyslog depends on:
ii  libc6 2.27-5
ii  libestr0  0.1.10-2.1
ii  libfastjson4  0.99.8-2
ii  liblognorm5   2.0.5-1
ii  libsystemd0   239-7
ii  libuuid1  2.32.1-0.1
ii  lsb-base  9.20170808
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages rsyslog recommends:
ii  logrotate  3.14.0-4

Versions of packages rsyslog suggests:
pn  rsyslog-doc
pn  rsyslog-gnutls 
pn  rsyslog-gssapi 
pn  rsyslog-mongodb
pn  rsyslog-mysql | rsyslog-pgsql  
pn  rsyslog-relp   

-- Configuration Files:
/etc/logcheck/ignore.d.server/rsyslog [Errno 13] Keine Berechtigung: 
'/etc/logcheck/ignore.d.server/rsyslog'

-- no debconf information

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature