Bug#897676: ITP: ruby-markdown-it-html5-embed -- A plugin implementation in ruby

[Naga Durga]

Package Repository Url:
https://salsa.debian.org/ruby-team/ruby-markdown-it-html5-embed

On Fri, May 4, 2018 at 11:51 AM, Naga Durga  wrote:

> Package: ruby-markdown-it-html5-embed
> Severity: wishlist
>
> * Package name: ruby-markdown-it-html5-embed
>   Version : 1.0.0
>   Upstream Author : Cmrd Senya 
> * URL : https://github.com/cmrd-senya/markdown-it-html5-embed
> * License : Mozilla Public License Version 2.0
>   Programming Lang: Ruby
>   Description : ruby-markdown-it-html5-embed is a plugin for markdown-it 
> which adds support for embedding audio/video in the HTML5 way.
>
>

Bug#897464: [DRE-maint] Bug#897464: ruby-cairo: FTBFS: ERROR: Test "ruby2.5" failed: Error: test: time(PDFSurfaceTest::#set_metadata::modified date): Poppler::Error::Invalid: Failed to load document

[dai]

Control: reassign -1 libpoppler-glib8 0.63.0-2
Control: forcemerge 896596 -1
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Bug#897672: #897672 ITP: python-pyfftw -- a pythonic wrapper around FFTW

[Drew Parsons]

Ghis has started a repo at https://salsa.debian.org/science-team/pyfftw
I'll pick up from there.

Bug#897605: How to deal with non-functional package in stretch? (Was: Bug#897605: profphd failure in stretch)

[Andreas Tille]

Hi release team,

it turned out that profphd is non-functional in stretch (see bug
#897605).  Since its not obviously a security issue we are wondering
whether there is some way to integrate this admittedly low popcon
package into Debian 9.5 (whenever this might be released).

While we can certainly do a backport not all users will realise / profit
from this.

On Fri, May 04, 2018 at 04:01:48AM +, olivier sallou wrote:
> Le jeu. 3 mai 2018 21:55, Andreas Tille  a écrit :
> 
> > On Thu, May 03, 2018 at 02:58:58PM +, olivier sallou wrote:
> > >
> > > newer version in sid (1.0.42-2) added a patch to allow new perl release.
> > A
> > > quick test on sid works (at least no error, just calling program with no
> > > argument), so maybe backporting this release would do the job
> >
> > Ahhh, right - I remember that Tatiana had to do some heavy patching.
> >
> > > > We definitely need some CI test for this package obviously.
> >
> > That was also done by Tatiana.
> >
> > However, a backport does not really close a bug in stretch and the issue
> > is also not really a security issue, right?
> >
> 
> This is indeed not a security issue, but package is unusable. Backport
> would at least make software available.
> I don't know know what is usual debian policy regarding this use case. I
> suppose it occured multiple times.
> 
> I can't be sure that sid version is really working, it just does not show
> any error. Could tatiana do some 'real' testing?

As far as I understood Tatiana she did some effort to make the program
functional.  She has done some real life tests.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#830230: systemd disable wake-on-lan

[Norbert Schulz]

Norbert Schulz schrieb:
> 
> Michael Biebl schrieb:
>> On Tue, 19 Jul 2016 17:39:40 +0200 Norbert Schulz
>>  wrote:
>>> Christian Hofstaedtler schrieb:
 * Norbert Schulz  [160718 09:24]:
> Here are the required and some more information.
 Thanks for following up on this. Unfortunately, I have no idea
 either on what is happening here.

>>> Is there any possibility to get some output if I send a wake-on-lan packet 
>>> (with
>>> etherwake) to the ethernet card when the system is running?
>>>
>> Is this still reproducible with an up-to-date stretch or sid system?
>>
> Sorry, until today I did not upgrade to stretch.
> 
> 
> Norbert Schulz
> 

In the meantime I upgraded to an up-to-date stretch and the system can be wake
up with the wake-on-lan packet with etherwake under systemd. So the bug can be
closed.


Norbert Schulz

Bug#897098: ppl FTBFS with TeX Live 2018

[Roberto Bagnara]

On 04/28/2018 03:15 PM, Adrian Bunk wrote:
> Source: ppl
> Version: 1:1.2-2
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ppl.html
> 
> ...
> pl-1.2/doc/bugseng_logo.pdf>] [4] [1] [2] (./index.tex
> Underfull \hbox (badness 1) detected at line 9
> [][][]
> pdfTeX warning (ext4): destination with the same identifier (name{page.1}) 
> has 
> been already used, duplicate ignored
>  
>\relax 
> l.25 
>   [1]) (/build/1st/ppl-1.2/doc/gpl.tex
> 
> ! LaTeX Error: Can be used only in preamble.
> 
> See the LaTeX manual or LaTeX Companion for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.1 \documentclass
>   [a4paper,12pt]{article}
> ? 
> ! Emergency stop.
>  ...  
>   
> l.1 \documentclass
>   [a4paper,12pt]{article}
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on refman.log.
> make[2]: *** [Makefile:6: refman.pdf] Error 1
> 

Thanks for the report.  This has just been fixed with the
following commit.

commit addd0535f36e4a2734b9b5321e2e0ad398c5e20c
Author: Roberto Bagnara 
Date:   Fri May 4 09:26:25 2018 +0200

Disable Kpathsea case-insensitive filename matching.
Case-insensitive filename matching is done by default in non-system
directories starting from TeX Live 2018.

diff --git a/doc/Makefile.am b/doc/Makefile.am
index 3daf9ccea..ffc3c12d5 100644
--- a/doc/Makefile.am
+++ b/doc/Makefile.am
@@ -866,7 +866,7 @@ devref-configured-ocaml-interface.latex-dir \
 user-configured-java-interface.latex-dir \
 devref-configured-java-interface.latex-dir

-TEX_ENV = TEXINPUTS=$(abs_srcdir):$(TEXINPUTS)
+TEX_ENV = TEXINPUTS=$(abs_srcdir):$(TEXINPUTS) texmf_casefold_search=0

 .SECONDARY: $(LATEX_DIRS)




-- 
 Prof. Roberto Bagnara

Applied Formal Methods Laboratory - University of Parma, Italy
mailto:bagn...@cs.unipr.it
  BUGSENG srl - http://bugseng.com
  mailto:roberto.bagn...@bugseng.com



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#859130: watch file

[Geert Stappers]

On Thu, Apr 26, 2018 at 01:35:33PM +0200, Albert van der Horst wrote:
> Verder kan je iets zeggen over watch files?

The file debian/watch is an essential link
in what this bugreport is about:
 Source from  https://github.com/albertvanderhorst/ciforth into Debian.

Releases on github can be detected with it.
I mean https://github.com/albertvanderhorst/ciforth/releases
Not https://github.com/albertvanderhorst/ciforth/tree/master/release
Which is regular directory in a git repository. That is not the place
to store .tar.gz files


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#897679: [trilinos] some test fails with openmpi 3

[Christophe CT. TROPHIME]

Package: trilinos
Version: 12.12.1-5 Severity: normal

When rebuilding trilinos against openmpi 3
some tests hangs
"
516/863 Test #516: EpetraExt_Permutation_test_MPI_4 
...   Passed0.23 sec

Start 517: EpetraExt_Permutation_test_LL_MPI_4
517/863 Test #517: EpetraExt_Permutation_test_LL_MPI_4 
   Passed0.25 sec

Start 518: EpetraExt_Block_test_MPI_4
"

--- System information. ---
Architecture: Kernel:   Linux 4.15.0-2-amd64

Debian Release: buster/sid
  500 testing ftp.fr.debian.org   500 testing euler 
500 stretch build.openmodelica.org   500 data 
neurodebian.g-node.org   500 buster  neurodebian.g-node.org 
500 buster  download.docker.com

Bug#897661: libsynctex1: Texmaker-libsynctex1:amd64 2018.20180416.47457-1

[Hilmar Preuße]

reassign 897661 texmaker
severity 897661 grave
merge 897661 896656
stop

On 04.05.2018 00:29, wrote:

Hi,

> Texmaker doesn't start sice upgrade libsynctex1:amd64
> 2018.20180416.47457-1.Texmaker star  when downgrade manually
> libsynctex1:amd64 2018.20180416.47457-1 -> 2014.20140926.35254-6
> 
Known problem. TeXmaker needs to be linked w/ libsynctex2, available in
unstable and testing. This version of libsynctex1, should have never
entered testing (see #896563). Please downgrade and pin that version
until new TeXmaker is out.

Reassign, merge.

Hilmar
-- 
#206401 http://counter.li.org

Bug#897680: nmu: p4est_1.1-5+b1

[Alastair McKinstry]

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

There were problems in p4est with the usage of an internal version of pmix by 
openmpi3.
This has been resolved by making pmix work for all architectures
(as of pmix 2.1.1~rc1-4,  openmpi 3.0.1.real-3). So, p4est needs to be rebuilt 
using these.

nmu p4est_1.1-5+b1 . ANY . unstable . -m "rebuild for openmpi3, pmix"

-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-6-686-pae (SMP w/1 CPU core)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_IE.UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_IE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#897613: RM: redmine/3.0~20140825-8~deb8u4

[Sébastien Delafond]

On May/03, Adam D. Barratt wrote:
> There's a few r-deps. Walking the tree gives us:
> 
> - redmine-plugin-pretend
> - redmine-plugin-recaptcha
> - redmine-recaptcha
> 
> I assume the intent is that those also be removed.

That is correct, sorry for not mentioning the r-deps initially.

Cheers,

--Seb

Bug#896191: FTBFS with TeX Live 2018

[Norbert Preining]

> dblatex converts a ` (back-tick) from the xml input from into \`{} in
> the LaTeX source. AFAIK (I'm not 100% sure) this was never correct, the

This was a bug in xecjk which is already fixed, will be in one of the
next uploads.

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#897634: libvirt-daemon: I also experience the same issue

[unsigned_nerd]

Package: libvirt-daemon
Version: 1.2.9-9+deb8u5
Followup-For: Bug #897634

Dear Maintainer,

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

   * What led up to the situation?

   I run multiple VMs.  I upgraded software on my Debian 8.10 which
   included the kernel (3.16.0-6-amd64) on May 3, 2018 GMT+7.  After
   the reboot, I could run only 1 VM at a time.  Note that if I remove
   the network interface from the second VM, then I can still run the
   send instance but that is not a workaround as I need network access
   for my VMs.

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

   I googled hard and the most relevance issue I found is:
   https://bugzilla.redhat.com/show_bug.cgi?id=1506822 .  That's when I
   decide to upgrade my system from Debian 8 to Debian 9 so that I could
   get the newer version of libvirt-daemon.  After that, the problem is
   gone.  I can run multiple VMs once again.

   * What was the outcome of this action?

   The problem is gone.

   * What outcome did you expect instead?

   That's what I expected.

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


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

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

Versions of packages libvirt-daemon depends on:
ii  libapparmor12.9.0-3
ii  libaudit1   1:2.4-1+b1
ii  libavahi-client30.6.31-5
ii  libavahi-common30.6.31-5
ii  libblkid1   2.25.2-6
ii  libc6   2.19-18+deb8u10
ii  libcap-ng0  0.7.4-2
ii  libdbus-1-3 1.8.22-0+deb8u1
ii  libdevmapper1.02.1  2:1.02.90-2.2+deb8u1
ii  libfuse22.9.3-15+deb8u2
ii  libgnutls-deb0-28   3.3.8-6+deb8u7
ii  libnetcf1   1:0.2.3-4.1
ii  libnl-3-200 3.2.24-2
ii  libnl-route-3-200   3.2.24-2
ii  libnuma12.0.10-1
ii  libparted2  3.2-7
ii  libpcap0.8  1.6.2-2
ii  libpciaccess0   0.13.2-3+b1
ii  librados2   0.80.7-2+deb8u2
ii  librbd1 0.80.7-2+deb8u2
ii  libsasl2-2  2.1.26.dfsg1-13+deb8u1
ii  libselinux1 2.3-2
ii  libssh2-1   1.4.3-4.1+deb8u1
ii  libsystemd0 215-17+deb8u7
ii  libudev1215-17+deb8u7
ii  libvirt01.2.9-9+deb8u5
ii  libxen-4.4  4.4.1-9+deb8u10
ii  libxenstore3.0  4.4.1-9+deb8u10
ii  libxml2 2.9.1+dfsg1-5+deb8u6
ii  libyajl22.1.0-2

Versions of packages libvirt-daemon recommends:
ii  libxml2-utils   2.9.1+dfsg1-5+deb8u6
ii  netcat-openbsd  1.105-7
ii  qemu-kvm1:2.1+dfsg-12+deb8u6

Versions of packages libvirt-daemon suggests:
ii  libvirt-daemon-system  1.2.9-9+deb8u5

-- no debconf information

Bug#897634: Libvirt cannot start more than one vm after upgrading kernel from 3.16.0-5 to 3.16.0-6

[Sebastian Schweizer]

It looks like the issue has already been reported to the kernel: #897427

Feel free to close this bug here if nothing needs to be done in libvirt.
Sorry for the noise.

Bug#897635: pdfposter: please move pdfposter from python2 to python3

[Elena ``of Valhalla'']

On 2018-05-03 at 13:39:23 -0400, Daniel Kahn Gillmor wrote:
> Package: pdfposter
> Version: 0.6.0-2
> Severity: wishlist
> 
> It would be great if pdfposter didn't have any python2 dependencies.
> i believe python3-pypdf2 is already available, so it should just be a
> matter of ensuring that pdfposter itself i is python3-compliant and
> shifting the dependencies directly.

python3 support has been added upstream about one year ago, in 

https://gitlab.com/pdftools/pdfposter/commit/663081f71bf855273aa22a211e7f1151347e191c

but is still not in a release.

As you already know[1] :) I had pinged upstream for a release, but it's
still pending (thanks for the further ping, btw)

[1] https://gitlab.com/pdftools/pdfposter/issues/5#note_71467160

the patch does look pretty simple, but I don't believe that it applies as
is to the old code in the packaged version, so I would prefer to wait
for the new upstream release to deliver code that has been actually
tested on py3.

-- 
Elena ``of Valhalla''

Bug#892267: 3dldf: FTBFS on mips64el, hurd-i386, ia64, powerpc, x32 - "src/3dldf tngnts_1.ldf" segfaults

[Hilmar Preuße]

On 07.03.2018 13:13, James Cowgill wrote:

> 3dldf FTBFS on the above architectures with the error:
>> ../src/3dldf tngnts_1.ldf
>> GNU 3DLDF Version 2.0.3
>> Copyright (C) 2013 The Free Software Foundation
>> Author:  Laurence D. Finston
>>

Just for the records: I tried to build the package using gcc-8. The
program can be compiled but using it is still a pain as the program
still crashes:

Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".

Core was generated by `./3dldf sample2.ldf'.

Program terminated with signal SIGSEGV, Segmentation fault.

#0  0xb7adeb35 in std::locale::~locale() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6

(gdb) bt

#0  0xb7adeb35 in std::locale::~locale() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6

#1  0x004c78ef in std::basic_streambuf
>::~basic_streambuf (this=0x2257cc4, __in_chrg=)

at /usr/include/c++/8/streambuf:204

#2  std::basic_filebuf >::~basic_filebuf
(this=0x2257cc4, __in_chrg=) at
/usr/include/c++/8/fstream:247

#3  std::basic_ofstream >::~basic_ofstream
(this=0x2257cc0, __in_chrg=, __vtt_parm=)

at /usr/include/c++/8/fstream:793

#4  Thread_Info_Type::~Thread_Info_Type (this=,
__in_chrg=) at ./pspglb.web:1626

#5  0x0052f614 in yyparse(void*) () at parser.y++:22016

#6  0x00517499 in main () at /usr/include/c++/8/bits/stl_vector.h:930

#7  0xb7756e81 in __libc_start_main (main=0x516500 , argc=2,
argv=0xbfed44a4, init=0x7c7a30 <__libc_csu_init>,

fini=0x7c7a90 <__libc_csu_fini>, rtld_fini=0xb7ef29a0 <_dl_fini>,
stack_end=0xbfed449c) at ../csu/libc-start.c:310

#8  0x005197f9 in _start () at ./main.web:1735

For using gcc-8 I simply changed the symlinks gcc, g++, cpp to version
8. Not sure if this is sufficient. Yes, I could install gcc from
experimental too.

sid:/usr/bin# ls -l gcc* g++* cpp*

lrwxrwxrwx 1 root root  5 May  4 09:53 cpp -> cpp-8

lrwxrwxrwx 1 root root 20 Apr 28 15:20 cpp-7 -> i686-linux-gnu-cpp-7

lrwxrwxrwx 1 root root 20 May  2 11:43 cpp-8 -> i686-linux-gnu-cpp-8

lrwxrwxrwx 1 root root  5 May  4 09:53 g++ -> g++-8

lrwxrwxrwx 1 root root 20 Apr 28 15:20 g++-7 -> i686-linux-gnu-g++-7

lrwxrwxrwx 1 root root 20 May  2 11:43 g++-8 -> i686-linux-gnu-g++-8

lrwxrwxrwx 1 root root  5 May  4 09:53 gcc -> gcc-8

lrwxrwxrwx 1 root root 20 Apr 28 15:20 gcc-7 -> i686-linux-gnu-gcc-7

lrwxrwxrwx 1 root root 20 May  2 11:43 gcc-8 -> i686-linux-gnu-gcc-8

lrwxrwxrwx 1 root root  8 Apr  4 12:16 gcc-ar -> gcc-ar-7


Hilmar
-- 
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#896844: auctex: Preview latex doesn't work - fixed upstream.

[Davide G. M. Salvetti]

Dear Benjamin,

thanks for the report, I will work on it.

--
Regards,
Davide

Bug#897681: nmu: lammps_0~20161109.git9806da6-7+b1

[Alastair McKinstry]

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

There were problems in lammps with the usage of an internal version of pmix by 
openmpi3.
This has been resolved by making pmix work for all architectures
(as of pmix 2.1.1~rc1-4,  openmpi 3.0.1.real-3). So, lammps needs to be rebuilt 
using these.

nmu lammps_0~20161109.git9806da6-7+b1 . sh4 x32 riscv64 powerpcspe m68k 
hurd-i386 powerpc kfreebsd-i386 kfreebsd-amd64 . unstable . -m "Rebuild for 
openmpi3, pmix fix"

-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-6-686-pae (SMP w/1 CPU core)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_IE.UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_IE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#767874: RFH: ejabberd -- distributed, fault-tolerant Jabber/XMPP server written in Erlang

[W. Martin Borgert]

Note, that ejabberd is now maintained by the Ejabberd
Packaging Team  in Debians
Gitlab (https://salsa.debian.org/ejabberd-packaging-team).

Bug#897634: [Pkg-libvirt-maintainers] Bug#897634: libvirt-daemon: I also experience the same issue

[Guido Günther]

On Fri, May 04, 2018 at 03:18:39PM +0700, unsigned_nerd wrote:
> Package: libvirt-daemon
> Version: 1.2.9-9+deb8u5
> Followup-For: Bug #897634
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> 
>I run multiple VMs.  I upgraded software on my Debian 8.10 which
>included the kernel (3.16.0-6-amd64) on May 3, 2018 GMT+7.  After
>the reboot, I could run only 1 VM at a time.  Note that if I remove
>the network interface from the second VM, then I can still run the
>send instance but that is not a workaround as I need network access
>for my VMs.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
>I googled hard and the most relevance issue I found is:
>https://bugzilla.redhat.com/show_bug.cgi?id=1506822 .  That's when I
>decide to upgrade my system from Debian 8 to Debian 9 so that I could
>get the newer version of libvirt-daemon.  After that, the problem is
>gone.  I can run multiple VMs once again.
> 
>* What was the outcome of this action?
> 
>The problem is gone.
> 
>* What outcome did you expect instead?
> 
>That's what I expected.

[NB: I'm not running Jessie currently]
Since this is triggered by a kernel upgrade could you guys take that up
with the kernel maintainers please? It's a regression caused by the
kernel update after all.
There's also a newer version in Jessie backports (but the bug should be
fixed in Jessie nevertheless).

Cheers,
 -- Guido

Bug#897682: nmu: med-fichier_3.0.6-12+b1

[Alastair McKinstry]

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

There were problems in med-fichier with the usage of an internal version of 
pmix by openmpi3.
This has been resolved by making pmix work for all architectures
(as of pmix 2.1.1~rc1-4,  openmpi 3.0.1.real-3). So, med-fichier needs to be 
rebuilt using these.

nmu med-fichier_3.0.6-12+b1 . hppa armhf i386 kfreebsd-i386 kfreebsd-amd64 
powerpc riscv64 x32 . unstable . -m "Rebuild for openmpi3, pmix fix"

-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-6-686-pae (SMP w/1 CPU core)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_IE.UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_IE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#887490: backuppc 4+ help

[Gürkan Myczko]

Ludovic I am interested in the work you've done so far.
And I could also help on this package. Version 4 looks a bit nicer than 
the old 3.x versions...


Best

Bug#897683: RFA: postfixadmin -- Virtual mail hosting interface for Postfix

[Christoph Martin]

Package: wnpp
Severity: normal

I request an adopter for the postfixadmin package.

I did the last uploads to make shure that it stays in Debian, but I
can't test the package thoroughly. I don't have enough knowledge of
postfix.

The original maintainer Normal stated that he also has no time to work
on it.

I'll try to do the current new upstream version, but would prefer to
see someone more experienced working on postfixadmin.

The package description is:
 Postfixadmin is a web interface to manage virtual users and domains
 for a Postfix mail transport agent. It supports Virtual mailboxes,
 aliases, forwarders and vacation.
 .
 Postfixadmin allows administrators to delegate account handling
 to domain administrators and allows users to login and change their own
 settings (e.g. forwarders, vacation, passwords etc).
 .
 It provides easy integration into dovecot, courier or cyrus.
 .
 Postfixadmin is written in PHP.

Christoph

-- 

Christoph Martin, Leiter Unix-Systeme
Zentrum für Datenverarbeitung, Uni-Mainz, Germany
 Anselm Franz von Bentzel-Weg 12, 55128 Mainz
 Telefon: +49(6131)3926337
 Instant-Messaging: Jabber/XMPP: mar...@jabber.uni-mainz.de

<>

signature.asc
Description: OpenPGP digital signature

Bug#897684: libguestfs-tools: virt-p2v-make-disk looks for virt-p2v.xz in the wrong place

[David Rabel]

Package: libguestfs-tools
Version: 1:1.34.6-2
Severity: normal

Dear Maintainer,

virt-p2v-make-disk expects /lib/x86_64-linux-gnu/virt-p2v/virt-p2v.xz , but
it's in /usr/lib/x86_64-linux-gnu/virt-p2v/virt-p2v.xz .

# virt-p2v-make-disk -o p2v.img
virt-p2v-make-disk: cannot find /lib/x86_64-linux-gnu/virt-p2v/virt-p2v.xz

# dpkg --listfiles libguestfs-tools | grep virt-p2v.xz
/usr/lib/x86_64-linux-gnu/virt-p2v/virt-p2v.xz

Regards
 David



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

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

Versions of packages libguestfs-tools depends on:
ii  curl   7.52.1-5+deb9u5
ii  libc6  2.24-11+deb9u1
ii  libconfig9 1.5-0.3
ii  libfuse2   2.9.7-1
ii  libguestfs-perl1:1.34.6-2
ii  libguestfs01:1.34.6-2
ii  libintl-perl   1.26-2
ii  liblzma5   5.2.2-1.2+b1
ii  libncurses56.0+20161126-1
ii  libreadline7   7.0-3
ii  libstring-shellquote-perl  1.03-1.2
ii  libsys-virt-perl   3.0.0-1
ii  libtinfo5  6.0+20161126-1
ii  libvirt0   3.0.0-4+deb9u3
ii  libwin-hivex-perl  1.3.13-2+b2
ii  libxml22.9.4+dfsg1-2.2+deb9u2
ii  libyajl2   2.1.0-2+b3

Versions of packages libguestfs-tools recommends:
ii  gnupg  2.1.18-8~deb9u1

libguestfs-tools suggests no packages.

-- no debconf information

Bug#897605: profphd failure in stretch

[Dominic Hargreaves]

On Fri, May 04, 2018 at 04:01:48AM +, olivier sallou wrote:
> Le jeu. 3 mai 2018 21:55, Andreas Tille  a écrit :
> 
> > On Thu, May 03, 2018 at 02:58:58PM +, olivier sallou wrote:
> > >
> > > newer version in sid (1.0.42-2) added a patch to allow new perl release.
> > A
> > > quick test on sid works (at least no error, just calling program with no
> > > argument), so maybe backporting this release would do the job
> >
> > Ahhh, right - I remember that Tatiana had to do some heavy patching.
> >
> > > > We definitely need some CI test for this package obviously.
> >
> > That was also done by Tatiana.
> >
> > However, a backport does not really close a bug in stretch and the issue
> > is also not really a security issue, right?
> >
> 
> This is indeed not a security issue, but package is unusable. Backport
> would at least make software available.
> I don't know know what is usual debian policy regarding this use case. I
> suppose it occured multiple times.
> 
> I can't be sure that sid version is really working, it just does not show
> any error. Could tatiana do some 'real' testing?

You should file a bug against release.debian.org with a proposed patch for
stretch to get their opinion of whether it should be fixed in stretch.
It is certainly serious enough if it's unusable, so they only question
will be how invasive the changes are.

If it's too broken (ie can't be realistically fixed) it should probably
be removed from stretch. Agains the release team are the people to
consult about this. If this were the case, then a backport would indeed
be worthwhile.

Cheers,
Dominic.

Bug#897644: python-gwcs depends on cruft package python-asdf

[Ole Streicher]

Hi,

since version 2, upstream of asdf does no longer support Python 2 [1];
therefore it is removed from the package. I therefore would recommend to
also remove the Python 2 version of gwcs.

[1] http://asdf.readthedocs.io/en/latest/asdf/changes.html

Best regards

Ole

Bug#897685: linux-image-3.16.0-6-amd64: Unable to start multiple KVM instances with libvirt

[Richard Braun]

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

Dear Maintainer,

The kernel package linux-image-3.16.0-6-amd64 introduced a regression
apparently preventing multiple KVM libvirt instances from running
concurrently. Here is the error message when attempting to start a second
instance :

# virsh start 
error: Failed to start domain 
error: Cannot get interface MAC on 'vnet%d': No such device

Running this command doesn't produce any dmesg log.

It may simply be a regression affecting tun/tap interfaces only.

See 
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1602078.html


-- Package-specific info:
** Version:
Linux version 3.16.0-6-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10+deb8u1) ) #1 SMP Debian 3.16.56-1 (2018-04-28)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-amd64 root=/dev/md2 ro rootdelay=10 
elevator=deadline hugepagesz=1GB hugepages=9

** Not tainted

** Model information
sys_vendor: Supermicro
product_name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
product_version: 0123456789
chassis_vendor: Supermicro
chassis_version: 0123456789
bios_vendor: American Megatrends Inc.
bios_version: 3.0a
board_vendor: Supermicro
board_name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
board_version: 0123456789

** Loaded modules:
tun
cpufreq_conservative
binfmt_misc
cpufreq_stats
cpufreq_powersave
cpufreq_userspace
bridge
stp
llc
quota_v2
quota_tree
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
kvm
crc32_pclmul
aesni_intel
aes_x86_64
lrw
gf128mul
glue_helper
ablk_helper
cryptd
ttm
drm_kms_helper
drm
serio_raw
pcspkr
iTCO_wdt
iTCO_vendor_support
sb_edac
joydev
evdev
edac_core
tpm_tis
tpm
wmi
processor
mei_me
thermal_sys
shpchp
mei
lpc_ich
ioatdma
mfd_core
button
ipmi_watchdog
ipmi_si
ipmi_poweroff
ipmi_devintf
ipmi_msghandler
fuse
autofs4
ext4
crc16
mbcache
jbd2
btrfs
ohci_hcd
uhci_hcd
pata_via
netxen_nic
3w_9xxx
qlge
ixgbe
mdio
sata_nv
forcedeth
via686a
mptctl
mptsas
mptspi
mptscsih
mptbase
dm_crypt
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
raid0
raid1
md_mod
dm_mirror
dm_region_hash
dm_log
dm_mod
sata_via
ata_piix
sata_sis
pata_sis
sym53c8xx
megaraid_sas
megaraid
aic7xxx
scsi_transport_spi
3w_
sky2
r8169
skge
e1000e
e1000
via_rhine
sis900
8139too
e100
mii
hid_generic
usbhid
hid
sg
sd_mod
crc_t10dif
crct10dif_generic
crct10dif_pclmul
crct10dif_common
ehci_pci
isci
crc32c_intel
ehci_hcd
ahci
libsas
libahci
psmouse
igb
libata
scsi_transport_sas
i2c_algo_bit
i2c_i801
i2c_core
dca
usbcore
ptp
scsi_mod
usb_common
pps_core

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 
DMI2 [8086:0e00] (rev 04)
Subsystem: Super Micro Computer Inc Device [15d9:062b]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI 
Express Root Port 1a [8086:0e02] (rev 04) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 PCI bridge [0604]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI 
Express Root Port 2a [8086:0e04] (rev 04) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.0 PCI bridge [0604]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI 
Express Root Port 3a [8086:0e08] (rev 04) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.2 PCI bridge [0604]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI 
Express Root Port 3c [8086:0e0a] (rev 04) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:04.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core 
i7 Crystal Beach DM

Bug#897686: environment-modules: module function not working with ZSH

[Christophe Garion]

Package: environment-modules
Version: 4.1.2-1
Severity: normal

Dear Maintainer,

I have a problem with environment-modules and ZSH: the module function
defined as

module () {
_moduleraw "$*" 2>&1
}

does not work correctly on my system with ZSH (the module command works
with Bash although). When using it without option, it works perfectly,
but using options like -t for module list or module avail does not work:
with list it leads to an error and with avail it leads to an empty
answer even if module avail is not "empty".

As I loads lots of ZSH config files, I have also tested module with a
new user without loading any ZSH config files and observed the same
behavior.

I am using ZSH 5.5.1.

The attached patch solves the problem for modules 4.1.2: it consists in
removing the " encapsulating the $* argument of _moduleraw.

Best,

Christophe

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (986, 'testing'), (984, 'stable'), (982, 'stable'), (98, 
'unstable'), (96, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.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

Versions of packages environment-modules depends on:
ii  less   487-0.1
ii  libc6  2.27-3
ii  libtcl8.6  8.6.8+dfsg-4
ii  procps 2:3.3.14-1
ii  tcl8.6.0+9
ii  tcl8.6 8.6.8+dfsg-4

environment-modules recommends no packages.

environment-modules suggests no packages.

-- no debconf information

-- 
Christophe Garion
GPG: 1982 15B2 64AC 3C34 532D  BF19 6CD6 246C 62DA 5A7F

Index: modules-4.1.2/modulecmd.tcl.in
===
--- modules-4.1.2.orig/modulecmd.tcl.in
+++ modules-4.1.2/modulecmd.tcl.in
@@ -3659,7 +3659,7 @@ $g_shell \$*`;
return $_mlstatus;}
  append fdef "\n};"
  if {[isStderrTty]} {
-append fdef "\nmodule() { _moduleraw \"\$*\" 2>&1; };"
+append fdef "\nmodule() { _moduleraw \$* 2>&1; };"
  }
   }
   {fish} {

Bug#897508: [Debian-ha-maintainers] Bug#897508: Bug#897508: gfs2-utils: FTBFS: dh_auto_test: make -j8 -Oline check VERBOSE=1 returned exit code 2

[Valentin Vidic]

On Wed, May 02, 2018 at 11:02:55PM +0200, Valentin Vidic wrote:
> Thanks, I can reproduce the errors too and will try to figure it out.
> The build was definitely working less than month ago when the last
> version was released, so something else in the system has changed.

After updating linux-libc-dev from 4.15.17-1 to 4.16.5-1 mkfs.gfs2
starts to segfault due to a change in gfs2_ondisk.h. I've contacted
cluster-de...@redhat.com to see if they have a fix already...

-- 
Valentin

Bug#897687: libpam-kwallet5: kwallet stopped working under Openbox after libpam-kwallet5 upgrade (5.12.1-1->5.12.1-2)

[Mikhail Morfikov]

Package: libpam-kwallet5
Version: 5.12.1-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

I've been using kwallet on my Openbox for some time now. It was working well,
but after today's system upgrade, kwallet doesn't really work anymore. When the
libpam-kwallet5 package is downgraded to the previous version (5.12.1-1),
kwallet backs to life, and works as before.

This problem only concerns Openbox. When I checked whether Plasma5 has the same
issue, it turns out it doesn't and in the case of Plasma5 everything is just
fine.



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

Kernel: Linux 4.16.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=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libpam-kwallet5 depends on:
ii  libc6  2.27-3
ii  libgcrypt201.8.2-2
ii  libpam-kwallet-common  5.12.1-1
ii  libpam0g   1.1.8-3.7

libpam-kwallet5 recommends no packages.

libpam-kwallet5 suggests no packages.




-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE5JPPWm5C7TFDUMqpzQRoEHcbZSAFAlrsLjMACgkQzQRoEHcb
ZSC0Jw//cRMSwmkqN2YlLlJjzbd7xIodqxFE1F6mT2ml2BYmbIefNO1veNoIeB7I
GOuNU/2uGVyC4NgCO++ylAq2fouqGO6KLBSC3Av55F8iwQaDtvS1NvR50veWFOpp
WweGcKaJFIzzD20f+dQai6U4t1wC6me26RPH2QQzzBjC6xYipW0hPTM9xP1OPL0a
moUwh6ng80jx50WR7rUYEh/f9V/SmfkxJSLWSQVpJuBivuaTngR5hG0Muuadvpa5
90OQC9Vrt6ZAVV739L2K9gIzabY5qyAF5VXMfhcz6PbSMK4qvShUPYfJtoO3r9EO
4O7EYM5Q/al0eW7i27oaNvnEBzfWpbmHanKyNi/tQIMqg6bDRB2xX23rtAhS7a5k
1uVn0Ki8mTxwRAJaPbJNi9KzC+1IYFkj4xg6/1Hq8C771aG+iK35MBz6nYtlKvCU
ppDVThChgwqU7bIUkXUIX82PoG/WBcXdwI9n2Bu8VSxIB9QJn/fCDZ1XU73zfGer
cM8OhHx83/ARsihEaX4RbMkz9epTFYRPERwzPGYmXFkV72HmMPczORE9g4ItZ0LI
hGD4xDo3ED3Y3chqSmNIGsuEx1lbL2Nl566VfXnCiq2YpgrkRy3Q+hhgKOuD8K5J
brCz0XFjA7fzoovaIY5x/o+nNcA9JDpsV0iZxqk8IimmbQeyX/8=
=J/US
-END PGP SIGNATURE-

Bug#897688: RFP: tomboy-ng -- simple note-taking application

[Erik Brangs]

Package: wnpp
Severity: wishlist

* Package name: tomboy-ng
  Version : 0.14
  Upstream Author : David Bannon 
* URL : https://wiki.gnome.org/Apps/Tomboy/tomboy-ng , 
https://github.com/tomboy-notes/tomboy-ng
* License : GPL-3.0
  Programming Lang: Pascal
  Description : simple note-taking application

The GNOME application tomboy-ng is still in development. It is supposed to 
replace Tomboy Notes
when it is far enough along. The original Tomboy Notes provides the essential 
features needed
for note taking (simple formatting, links, synchronization of notes). It is 
very useful for simple
notes.

According to its authors, tomboy-ng is not yet ready for general use. 
Nevertheless, I'd like to
see it packaged for Debian so that it will be available when it's ready. 
Additionally, the original
Tomboy notes is currently not in testing and I'd rather have an unstable Tomboy 
variant in the next
release than no Tomboy at all.

Bug#873698: Finally a working watch file that also downloads correctly

[Moritz Schlarb]

Control: tags -1 + patch

Hi everyone,

I added some filenamemangle options so that the core and masterfiles
tarball get named correctly after download.

Best wishes,
-- 
Moritz Schlarb
Unix-Gruppe | Systembetreuung
Zentrum für Datenverarbeitung
Johannes Gutenberg-Universität Mainz
Raum 01-331 - Tel. +49 6131 39-29441
OpenPGP Fingerprint: DF01 2247 BFC6
5501 AFF2 8445 0C24 B841 C7DD BAAF
diff --git a/debian/watch b/debian/watch
index 714580b..298f059 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,3 +1,13 @@
 version=4
-https://cfengine.com/product/community/ .*/cfengine-(\d.*).tar.gz
-opts="component=masterfiles" https://cfengine.com/product/community/ .*/cfengine-masterfiles-(\d.*).tar.gz
+# Since the official upstream download page at https://cfengine.com/product/community/
+# is dynamically generated from many layers of JSON files, we instead look at the
+# GitHub releases page to get a list of versions and then construct the URLs for
+# release tarballs from them.
+# Therefore, the following looks pretty ugly. If someone finds a sane way to improve it,
+# please do so!
+opts=downloadurlmangle=s%https://github.com/cfengine/core/archive/(@ANY_VERSION@@ARCHIVE_EXT@)%https://cfengine-package-repos.s3.amazonaws.com/tarballs/cfengine-$1%,\
+		filenamemangle=s%.*/(@ANY_VERSION@)(@ARCHIVE_EXT@)%cfengine-$1$3% \
+	https://github.com/cfengine/core/releases .*/([\.\d]+)@ARCHIVE_EXT@
+opts=component=masterfiles,downloadurlmangle=s%https://github.com/cfengine/masterfiles/archive/(@ANY_VERSION@@ARCHIVE_EXT@)%https://cfengine-package-repos.s3.amazonaws.com/tarballs/cfengine-masterfiles-$1%,\
+		filenamemangle=s%.*/(@ANY_VERSION@)(@ARCHIVE_EXT@)%cfengine-masterfiles-$1$3% \
+	https://github.com/cfengine/masterfiles/releases .*/([\.\d]+)@ARCHIVE_EXT@
<>

signature.asc
Description: OpenPGP digital signature

Bug#897667: qt4-x11: Please add support for new architecture "riscv64"

[Lisandro Damián Nicanor Pérez Meyer]

¡Hola Manuel!

El jueves, 3 de mayo de 2018 22:07:25 -03 Manuel A. Fernandez Montecelo 
escribió:
> Source: qt4-x11
> Version: 4:4.8.7+dfsg-15
> Severity: normal
> Tags: patch upstream
> User: debian-ri...@lists.debian.org
> Usertags: riscv64
> 
> Hello,
> 
> We need support in this package to bootstrap the riscv64 architecture.
> 
> Yes, I know that you want to get rid of Qt4 once and for all and ASAP, and I
> fully agree with the goal.  However, a bazillion of packages depend on
> qt4-x11 indirectly,

A little less than 300 source packages.

> for example libsdl2 needs it (through fcitx, then
> cmake-extra-modules, then qt5-qmake, then qtchooser that depends on Qt4
> stuff); many package still need it directly; etc.

fcitx: yes. The rest: they do not need Qt4. But the sole fact that you mention 
it means we better take a look here. Please give us more info with respect how 
this is happening (or something I can dig into).

> So without support in this package, progress becomes impossible at an early
> stage.

Let's try to see exactly what's happening here, the list you wrote here look 
really suspicious to me.
 
> I am attaching a patch that adds support for the architecture.  AFAIK
> (please confirm) upstream doesn't accept patches since long ago, so no
> point in sending it there.

Yes, Qt4 is **dead** upstream. Adding whatever support means becoming it's 
maintainer. And adding more probable life to something that should be not be 
here already.

> For Qt5 we're already sending it upstream, e.g.
> webkit stuff.

*Thanks* a lot for that. If you need help prodding upstream please be sure to 
contact us.

> It would be great if you could include these changes and release a new
> version for unstable, for the time being the patched version lives in
> "unreleased".

I must admit that the patch looks good. But before accepting it I really want 
to dig into the dependency chain you wrote above. This seems like a great 
opportunity to find possibly wrong stuff.

By the way: in http://deb.li/qt5builds I noticed that most qt5 submodules have 
been built but not qtbase! How did you achieve that?

Cheers, and thanks for trying to bootstrap riscv64!

-- 
http://xkcd.com/162/

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#891906: Solved: tigervnc-standalone-server: Fails to interpret comand line parameters

[Georg Herrmann]

Hello Joachim,

the fault is on my side! Finally your script showed me the reason for
the strange behaviour of vncserver on my system. Some time ago I've set
an alias in my bashrc, which sets some default options. That makes no
sense when vncserver is called with -kill-option, so it fails. 

Whenever I call vncserver qualified, or as another user, ignoring my
bashrc (e. g. /usr/bin/vncserver -kill :2), it work's flawless. 

I beg your pardon,
Georg

Bug#897691: python3-hbmqtt: overly generic python module name: /usr/lib/python3/dist-packages/scripts/__init__.py

[Andreas Beckmann]

Package: python3-hbmqtt
Version: 0.9.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package uses a very generic
python module name that now clashes with other packages:

/usr/lib/python3/dist-packages/scripts/__init__.py


Andreas

Bug#897690: Inline Etherpad widget does not work

[martin f krafft]

Package: revolt
Version: 0.0+git20170627.3f5112b-3
Severity: normal

The Etherpad widget that I can add to a room seems to load forever,
but never actually works.

-- 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.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages revolt depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.28.0-2
ii  gir1.2-webkit2-4.0   2.20.1-1
ii  python3  3.6.5-3
ii  python3-gi   3.28.2-1

revolt recommends no packages.

revolt suggests no packages.

-- no debconf information


-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


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

Bug#897689: python3-cclib: overly generic python module name: /usr/lib/python3/dist-packages/scripts/__init__.py

[Andreas Beckmann]

Package: python3-cclib
Version: 1.5.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package uses a very generic
python module name that now clashes with other packages:

/usr/lib/python3/dist-packages/scripts/__init__.py


Andreas

Bug#897692: lintian: overly generic python module file name: /usr/lib/python3/dist-packages/scripts/__init__.py

[Andreas Beckmann]

Package: lintian
Version: 2.5.84
Severity: normal

Hi,

recently python3-cclib and python3-hbmqtt started shipping a "scripts"
python module.


Andreas

Bug#894510: [debhelper-devel] Bug#894510: debhelper: Because it is listing tmpfiles in systemd's only, conf overriding is not working

[Seyeong Kim]

Could somebody check this issue if you have time?

I would really appreciate it.

Thanks

On 11 Apr 2018, 2:17 PM +0900, Seyeong Kim , wrote:
> Right. Missed it.
>
> Thanks!
>
> > 2018. 4. 11. 오후 2:13, Niels Thykier  작성:
> >
> > Seyeong Kim:
> > > Please take a look this if you have time.
> > >
> > > Thanks
> > >
> > > [...]
> > Hi Seyeong,
> >
> > Please remember to Cc Felipe and Michael on this bug if you want them to
> > see the follow ups. :)
> >
> > Thanks,
> > ~Niels
>

Bug#897671: u-boot does not work on sheevaplug

[Martin Michlmayr]

* Markus Krebs  [2018-05-04 06:33]:
> Version: 2018.03+dfsg1-2
> 
> The u-boot.kwb provided at https://forum.doozan.com/read.php?3,12381 works.

That is version 2017.07.  If you have time, could you try some
versions from http://snapshot.debian.org/package/u-boot/  Not all of
them but maybe

2018.01+dfsg1-2
2017.11+dfsg1-3
2017.09+dfsg1-3
2017.07+dfsg1-3

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#897693: lldpad: Segfault in get_saddr6

[Gerben Meijer]

Source: lldpad
Version: 1.0.1+git20150824.036e314-2
Severity: important

Running lldpad on some systems causes a segfault.

The issue is described here: https://bugzilla.redhat.com/show_bug.cgi?id=1513337

A patch is attached to that bugreport which fixes the issue. Please
apply it in the next package version.


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

Kernel: Linux 4.16.2 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#897627: tex: please support SOURCE_DATE_EPOCH for dvi too

[Bill Allombert]

On Fri, May 04, 2018 at 12:37:36PM +0900, Norbert Preining wrote:
> Hi Bill,
> 
> On Thu, 03 May 2018, Bill Allombert wrote:
> > While pdftex handles SOURCE_DATE_EPOCH, tex does not, which leads to
> > unreproducible DVI files.
> 
> tex is tex as DEK wanted it. Please use etex, which is the pdftex binary
> producing dvi.

Maybe this could be documented in the manpage ? There is already:

BUGS
   This version of TeX implements a number of optional extensions.
  In fact, many of these extensions  conflict  to  a  greater or lesser
  extent with the definition of TeX.  When such extensions are enabled,
  the banner printed when TeX starts is  changed  to  print TeXk instead
  of TeX.

I think it is likely that if this bug is closed without changes, someone
else will open it again.

What about latex ?

Cheers,
Bill.

Bug#894510: debhelper: Because it is listing tmpfiles in systemd's only, conf overriding is not working

[Michael Biebl]

On Sat, 31 Mar 2018 08:58:21 -0700 Seyeong Kim
 wrote:
> Package: debhelper
> Version: 9.20160115ubuntu3
> Severity: normal
> Tags: d-i
> 
> In autoscripts/postinst-init-tmpfiles, There is TMPFILE containing conf in 
> systemd pkg only.
> Then if there is 00rsyslog.conf from rsyslog pkg. and installing or upgrading 
> systemd
> 
> /var/log's permission is 755(which is default) not 775(which is in 
> 00rsyslog.conf)
> overriding doesn't work when upgrading.
> 
> Please refer to below LP
> ubuntu lp bug : https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748147
> 
> removing TMPFILE from autoscripts/postinst-init-tmpfiles solves this issue.
> e.g. change like below
> systemd-tmpfiles --create #TMPFILES# >/dev/null || true
> to
> systemd-tmpfiles --create >/dev/null || true

Dropping #TMPFILES# means, systemd-tmpfiles will act on all tmpfiles.
This would be a bit like if upgrading rsyslog would restart all system
services (including rsyslog). That doesn't feel right.
So I don't think dropping #TMPFILES# is the right approach.

If I understand you correctly, your issue is the following:
The systemd package ships /usr/lib/tmpfiles.d/var.conf containing
d /var/log 0755 - - -
The rsyslog package ships /usr/lib/tmpfiles.d/00rsyslog.conf containing
z /var/log 0775 root syslog -

So you have conflicting definitions for /var/log and you rely on the
systemd-tmpfiles to always process all .conf files and you rely on the
sort-order to ensure that the definition in var.conf is skipped?

systemd.postinst has a call
systemd-tmpfiles --create ... /usr/lib/tmpfiles.d/var.conf

That means if the postinst of systemd is processed after rsyslog or only
the systemd package is upgraded, your /var/log/ permissions are reset to
the systemd defaults?

TBH, that all sounds like a very brittle setup, to rely on the
sort-ordering and systemd-tmpfiles always acting on all files.
Overriding existing tmpfiles configs this way seems hacky, not sure if
upstream intended it to be used like this.

I note that this is an Ubuntu specific problem, the Debian rsyslog
package does not ship such a config.

Dunno what the best solution is for your specific case.
Maybe diverting /usr/lib/tmpfiles.d/var.conf in the rsyslog package?

You could also ask upstream, maybe they have an idea how to solve this
in a more robust way.
-- 
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#894510: debhelper: Because it is listing tmpfiles in systemd's only, conf overriding is not working

[Michael Biebl]

Am 04.05.2018 um 13:47 schrieb Michael Biebl:
> If I understand you correctly, your issue is the following:
> The systemd package ships /usr/lib/tmpfiles.d/var.conf containing
> d /var/log 0755 - - -
> The rsyslog package ships /usr/lib/tmpfiles.d/00rsyslog.conf containing
> z /var/log 0775 root syslog -

..

> Dunno what the best solution is for your specific case.
> Maybe diverting /usr/lib/tmpfiles.d/var.conf in the rsyslog package?

Or you patch /usr/lib/tmpfiles.d/var.conf from the systemd package to
already include the "correct" definition for /var/log.

That said, I dunno, if rsyslog is the only supported syslog daemon in
Ubuntu and if other syslog daemons in Ubuntu have other, conflicting
requirements in that regard.

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#897449: django-allauth: Invalid character reference 138 in "Last Translator" field in some .po files (Bug#881727 reappeared when uploading 0.35 version)

[Pierre-Elliott Bécue]

Le mercredi 02 mai 2018 à 21:20:53+0200, Laura Arjona Reina a écrit :
> Package: django-allauth
> Severity: wishlist
> Tags: patch l10n upstream
> 
> Dear Maintainer,
> 
> When uploading the 0.35 version, the bug Bug#881727 reappeared again:
> 
> Some of the upstream .po files, in the "Last translator" field, include
> a name of translator with a bad encoded character (numeric character
> reference 138 instead of Š). This produces "Tidy Validation" warning
> messages when building the Debian website pages.
> The .PO files do not include mail address for the translator with the
> bad encoding, so I've requested to join the django-allauth translation
> team in Transifex, with the hope of contacting Jannis Š and request them
> to fix the encoding in their profile in Transifex.
> 
> Meanwhile, I'm attaching a patch that uses the correct UTF-8 character.

Hi,

This is very weird.

As you can see in the salsa repository, your patch is still there, and it
applied correctly (I rebased it on the new release).

As I did the upload myself, I took the .deb package I sent to the archive,
and extracted it, and placed myself in
usr/lib/python3/dist-packages/allauth/locale and ran this:

.-(.../dependencies/django-allauth/toto/usr/lib/python3/dist-packages/allauth/locale)-
`---> cat {es,pt_PT,sv,tr}/LC_MESSAGES/django.po|grep 'Jannis'
"Last-Translator: Jannis Š\n"
"Last-Translator: Jannis Š\n"
"Last-Translator: Jannis Š\n"
"Last-Translator: Jannis Š\n"

All seem fine.

As the package is also installed on my server, I also did this:

.-(13:50:00)-(~)-(peb@pimeys)-
`---> acp python-django-allauth
python-django-allauth:
  Installé : 0.35.0-1~bpo9+3
  Candidat : 0.35.0-1~bpo9+3
 Table de version :
 0.35.0-2 99
 99 http://ftp.fr.debian.org/debian sid/main amd64 Packages
 *** 0.35.0-1~bpo9+3 100
100 http://ftp.fr.debian.org/debian stretch-backports/main amd64 
Packages
100 /var/lib/dpkg/status
.-(13:50:04)-(~)-(peb@pimeys)-
`---> cd /usr/lib/python2.7/dist-packages/allauth/locale/
.-(13:50:26)-(/usr/lib/python2.7/dist-packages/allauth/locale)---(peb@pimeys)-
`---> cat {es,pt_PT,sv,tr}/LC_MESSAGES/django.po|grep 'Jannis'
"Last-Translator: Jannis Š\n"
"Last-Translator: Jannis Š\n"
"Last-Translator: Jannis Š\n"
"Last-Translator: Jannis Š\n"

Your patch really seems to work fine.

So, I wonder, maybe this error is triggered because the *source* actually
still contains this wrongfully encoded character? But theoretically I'm not
supposed to alter upstream's source.

Cheers,

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#897627: tex: please support SOURCE_DATE_EPOCH for dvi too

[Hilmar Preuße]

On 04.05.2018 13:38, Bill Allombert wrote:

Hi,

> Maybe this could be documented in the manpage? There is already:
> 
> BUGS
>This version of TeX implements a number of optional extensions.
>   In fact, many of these extensions  conflict  to  a  greater or lesser
>   extent with the definition of TeX.  When such extensions are enabled,
>   the banner printed when TeX starts is  changed  to  print TeXk instead
>   of TeX.
> 
Hmm, you mean we should document every difference between our TeXk and
TeX? Not sure if that should be put into a /manual/ page.

> I think it is likely that if this bug is closed without changes, someone
> else will open it again.
> 
What bug? According to Norbert the behavior of TeX is more close the
DEK's TeX than pdfTeX. So one could complain about a bug in pdfTeX, but
not in TeX (as you did).
We could implement a README.Debian  documenting, which version of TeX to
use, when one needs a reproducible build.

> What about latex?
> 
hille@amd64-sid:~$ latex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018/Debian)
(preloaded format=latex)
 restricted \write18 enabled.
**^C
hille@amd64-sid:~$ tex
This is TeX, Version 3.14159265 (TeX Live 2018/Debian) (preloaded
format=tex)
**^C

--> uses pdfTeX.

H.
-- 
#206401 http://counter.li.org

Bug#897694: plank: Shouldn't plank depends on dbus-x11 cause it's not working properly without it

[Drakos]

Package: plank
Version: 0.11.4-2
Severity: normal

Tested on 0.11.3-2 and 0.11.4-2. If I run plank without dbus-x11 I'm getting 
the following errors 
and plank doesn't work properly for example programs may not apear and settings 
cannot be set 
but after I install the dbus-x11 everything just works fine and erros disappear.

[CRITICAL 15:00:32.526658] [GLib-GIO] g_dbus_proxy_new_sync: assertion 
'G_IS_DBUS_CONNECTION (connection)' failed
[CRITICAL 15:00:32.52] [GLib-GIO] g_dbus_proxy_get_name_owner: assertion 
'G_IS_DBUS_PROXY (proxy)' failed
[WARN 15:00:32.533462] [Environment:161] XDG_SESSION_CLASS not set in this 
environment!
[WARN 15:00:32.533492] [Environment:179] Neither of XDG_SESSION_DESKTOP, 
XDG_CURRENT_DESKTOP or DESKTOP_SESSION is set in this environment!
[WARN 15:00:32.533516] [Environment:192] XDG_SESSION_TYPE not set in this 
environment!
[CRITICAL 15:00:32.560216] [DBusManager:168] Not able to register our interfaces
[WARN 15:00:32.575423] [dconf] failed to commit changes to dconf: Failed to 
execute child process "dbus-launch" (No such file or directory)
[WARN 15:00:32.591727] [dconf] failed to commit changes to dconf: Failed to 
execute child process "dbus-launch" (No such file or directory)
[WARN 15:00:32.605656] [Preferences:192] 
'/usr/share/plank/themes/Default/dock.theme' is read-only!
[WARN 15:00:32.607952] [dconf] failed to commit changes to dconf: Failed to 
execute child process "dbus-launch" (No such file or directory)
[WARN 15:00:32.622891] Unable to get org.ayatana.bamf matcher: Failed to 
execute child process "dbus-launch" (No such file or directory)
[WARN 15:00:32.625221] [dconf] failed to commit changes to dconf: Failed to 
execute child process "dbus-launch" (No such file or directory)
[CRITICAL 15:00:32.631284] [GLib-GIO] g_dbus_proxy_set_default_timeout: 
assertion 'G_IS_DBUS_PROXY (proxy)' failed
[WARN 15:00:32.631323] [GLib-GObject] invalid (NULL) pointer instance
[CRITICAL 15:00:32.639105] [GLib-GObject] g_signal_connect_data: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
[WARN 15:00:32.639131] [GLib-GObject] invalid (NULL) pointer instance
[WARN 15:00:32.641190] [dconf] failed to commit changes to dconf: Failed to 
execute child process "dbus-launch" (No such file or directory)
[CRITICAL 15:00:32.647037] [GLib-GObject] g_signal_connect_data: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
[WARN 15:00:32.647064] [GLib-GObject] invalid (NULL) pointer instance
[CRITICAL 15:00:32.655311] [GLib-GObject] g_signal_connect_data: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
[WARN 15:00:32.655337] [GLib-GObject] invalid (NULL) pointer instance
[WARN 15:00:32.657206] [dconf] failed to commit changes to dconf: Failed to 
execute child process "dbus-launch" (No such file or directory)
[CRITICAL 15:00:32.663468] [GLib-GObject] g_signal_connect_data: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
[WARN 15:00:32.663499] [GLib-GObject] invalid (NULL) pointer instance
[CRITICAL 15:00:32.671284] [GLib-GObject] g_signal_connect_data: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
[WARN 15:00:32.671305] [GLib-GObject] invalid (NULL) pointer instance
[WARN 15:00:32.673235] [dconf] failed to commit changes to dconf: Failed to 
execute child process "dbus-launch" (No such file or directory)
[CRITICAL 15:00:32.679100] [GLib-GObject] g_signal_connect_data: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
[CRITICAL 15:00:32.689241] [GLib-GIO] g_dbus_proxy_call_sync_internal: 
assertion 'G_IS_DBUS_PROXY (proxy)' failed
[WARN 15:00:32.689590] [dconf] failed to commit changes to dconf: Failed to 
execute child process "dbus-launch" (No such file or directory)
[WARN 15:00:32.690011] Failed to get running applications: 
[CRITICAL 15:00:32.691652] [GLib] g_error_free: assertion 'error != NULL' failed
[WARN 15:00:32.703478] (Services/Matcher.c:294):plank_matcher_active_launchers: 
runtime check failed: (_tmp3_ != NULL)
[WARN 15:00:32.705245] [dconf] failed to commit changes to dconf: Failed to 
execute child process "dbus-launch" (No such file or directory)
[CRITICAL 15:00:32.711210] [GLib-GIO] g_dbus_proxy_call_sync_internal: 
assertion 'G_IS_DBUS_PROXY (proxy)' failed
[WARN 15:00:32.711717] Failed to register favorites: 
[CRITICAL 15:00:32.713413] [GLib] g_error_free: assertion 'error != NULL' failed
[WARN 15:00:32.714962] [Unity:92] Failed to execute child process "dbus-launch" 
(No such file or directory)
[WARN 15:00:32.716621] [Unity:92] Failed to execute child process "dbus-launch" 
(No such file or directory)
[WARN 15:00:32.717917] [Environment:179] Neither of XDG_SESSION_DESKTOP, 
XDG_CURRENT_DESKTOP or DESKTOP_SESSION is set in this environment!
[WARN 15:00:32.723126] [dconf] failed to commit changes to dconf: Failed to 
execute child process "dbus-launch" (No such file or directory)
[WARN 15:00:32.740058] [dconf] failed to commit changes to dconf: Failed to 
execute child process "dbus-launch" (No such file or directory)
[WARN 15:00:32.756545] [dc

Bug#894510: debhelper: Because it is listing tmpfiles in systemd's only, conf overriding is not working

[Michael Biebl]

Am 04.05.2018 um 13:47 schrieb Michael Biebl:
> Dropping #TMPFILES# means, systemd-tmpfiles will act on all tmpfiles.
> This would be a bit like if upgrading rsyslog would restart all system
> services (including rsyslog). That doesn't feel right.
> So I don't think dropping #TMPFILES# is the right approach.

To iterate on that:
We ship quite a few tmpfile configs and during a (dist-)upgrade
systemd-tmpfiles will be called multiple times. It seems wasteful, if
systemd-tmpfile would act on all files over and over again.

More importantly though, not all resources, as required in the tmpfile
might be available when such a systemd-tmpfiles call is made. There is a
time window between the package being unpacked and the tmpfile existing
on disk and the package postinst being run, which e.g. needs to setup a
user that is referenced in the tmpfile.

Admittedly, this is less of an issue for tmpfiles then for service files.

One valid use cases this touches though is, that overriding tmpfiles in
/etc/tmpfiles.d should be supported. I.e. if there is a
/usr/lib/tmpfiles.d/dbus.conf and an admin wants to tweak that by
shipping a /etc/tmpfiles.d/dbus.conf, I don't think the package should
override that.
Afaics, this could easily be fixed by only using the name of the .conf
file, not the full path, so dh_installsystemd/dh_installinit would have
to generate
systemd-tmpfiles --create dbus.conf
instead of
systemd-tmpfiles --create /usr/lib/tmpfiles.d/dbus.conf

Felipe et al, what do you think?

(CC pkg-systemd-maintainers to have more eyes on this)

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#890614: gdm3 not working with 4.9.0-6

[Andreas Pflug]

Today, my machines (stretch) got the same problem
gnome-session-binary[1201]: WARNING: IceLockAuthFile failed: File exists.

Apparently the problem is invented by linux-image-4.9.0-6 which was
automatically installed yesterday. Reverted to 4.9.0-5, problem is gone.

Bug#897250: FTBFS with libonig 6.8.1-1

[Moritz Muehlenhoff]

On Wed, May 02, 2018 at 12:02:03PM +0200, Moritz Muehlenhoff wrote:
> Hi Jörg,
> 
> On Mon, Apr 30, 2018 at 09:59:11PM +0200, Jörg Frings-Fürst wrote:
> > 
> > for the liboinig transition I testing the build of hhvm again libonig 
> > 6.8.1-1.
> > 
> > The build fails with
> > 
> > [quote]
> > In file included from /build/hhvm-3.21.0+dfsg/hphp/runtime/base/program-
> > functions.cpp:117:0:
> > /usr/include/oniguruma.h:347:1: error: 'UChar' does not name a type; did you
> > mean 'char'?
> >  UChar* onigenc_strdup P_((OnigEncoding enc, const UChar* s, const UChar*
> > end));
> >  ^
> >  char
> 
> But that's a problem in the lobonig headers? 
> hphp/runtime/base/program-functions.cpp:117 simply does a
> 
> #include 

Actually this needs some changes on the HHVM end, found a fix.

Cheers,
Moritz

Bug#897695: blktrace: CVE-2018-10689: Buffer overflow in the dev_map_read function

[Salvatore Bonaccorso]

Source: blktrace
Version: 1.0.5-1
Severity: normal
Tags: patch security upstream
Forwarded: https://www.spinics.net/lists/linux-btrace/msg00847.html

Hi,

The following vulnerability was published for blktrace.

CVE-2018-10689[0]:
| blktrace (aka Block IO Tracing) 1.2.0, as used with the Linux kernel
| and Android, has a buffer overflow in the dev_map_read function in
| btt/devmap.c because the device and devno arrays are too small, as
| demonstrated by an invalid free when using the btt program with a
| crafted file.

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-10689
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10689
[1] https://www.spinics.net/lists/linux-btrace/msg00847.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#897688: RFP: tomboy-ng -- simple note-taking application

[Michael Biebl]

Am 04.05.2018 um 12:18 schrieb Erik Brangs:
> Package: wnpp
> Severity: wishlist
> 
> * Package name: tomboy-ng
>   Version : 0.14
>   Upstream Author : David Bannon 
> * URL : https://wiki.gnome.org/Apps/Tomboy/tomboy-ng , 
> https://github.com/tomboy-notes/tomboy-ng
> * License : GPL-3.0
>   Programming Lang: Pascal
>   Description : simple note-taking application
> 
> The GNOME application tomboy-ng is still in development. It is supposed to 
> replace Tomboy Notes
> when it is far enough along. The original Tomboy Notes provides the essential 
> features needed
> for note taking (simple formatting, links, synchronization of notes). It is 
> very useful for simple
> notes.
> 
> According to its authors, tomboy-ng is not yet ready for general use. 
> Nevertheless, I'd like to
> see it packaged for Debian so that it will be available when it's ready. 
> Additionally, the original
> Tomboy notes is currently not in testing and I'd rather have an unstable 
> Tomboy variant in the next
> release than no Tomboy at all.

By CCing pkg-gnome-maintainers I assume you wanted the Debian GNOME team
to provide some feedback on this.

Let me note, that we already have tomboy itself in the archive
(maintained by the mono team), then gnote (maintained by the GNOME team)
and bijiben (maintained by the GNOME team).

I don't think there will be a huge interest by the GNOME team to
maintain yet another note taking application. Especially since tomboy-ng
doesn't seem to provide a proper build system and is written in Pascal,
and I don't think anyone in the team has experience with that language.

Regards,
Michael


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



signature.asc
Description: OpenPGP digital signature

Bug#897627: tex: please support SOURCE_DATE_EPOCH for dvi too

[Bill Allombert]

On Fri, May 04, 2018 at 02:00:26PM +0200, Hilmar Preuße wrote:
> On 04.05.2018 13:38, Bill Allombert wrote:
> 
> Hi,
> 
> > Maybe this could be documented in the manpage? There is already:
> > 
> > BUGS
> >This version of TeX implements a number of optional extensions.
> >   In fact, many of these extensions  conflict  to  a  greater or lesser
> >   extent with the definition of TeX.  When such extensions are enabled,
> >   the banner printed when TeX starts is  changed  to  print TeXk instead
> >   of TeX.
> > 
> Hmm, you mean we should document every difference between our TeXk and
> TeX? Not sure if that should be put into a /manual/ page.
> 
> > I think it is likely that if this bug is closed without changes, someone
> > else will open it again.
> > 
> What bug?

Sorry, I meant bug as in 'an entry in the Debian BTS' not as "a problem
that need to be solved". And actually #897627 is a wishlist item.

Developpers generally expect every programs that generates files with
timestamp to honor SOURCE_DATE_EPOCH at some point.
That tex will not implement it for legacy reason, and that etex needs to
be used instead is OK, even if potentially inconvenient (if tex is
hardcoded in upstream makefile).

However, if this is not clearly documented, developpers might report
this wishlist again and again.

Cheers,
Bill.

Bug#897772: transition: miniupnpc

[Thomas Goirand]

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

Hi there!

We've uploaded miniupnpc to Experimental, and my sponsoree said he attempted
a rebuild against all the reverse dependencies listed here:
https://release.debian.org/transitions/html/auto-miniupnpc.html

There was no FTBFS problem, so we would like to upload miniupnpc 2.0.20180410-2
to unstable ASAP. Please let me know when I can upload.

Ben file:

title = "miniupnpc";
is_affected = .depends ~ "libminiupnpc16" | .depends ~ "libminiupnpc17";
is_good = .depends ~ "libminiupnpc17";
is_bad = .depends ~ "libminiupnpc16";


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

Kernel: Linux 4.9.0-6-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#897250: FTBFS with libonig 6.8.1-1

[Moritz Muehlenhoff]

B0;115;0cOn Fri, May 04, 2018 at 02:21:41PM +0200, Moritz Muehlenhoff wrote:
> On Wed, May 02, 2018 at 12:02:03PM +0200, Moritz Muehlenhoff wrote:
> > Hi Jörg,
> > 
> > On Mon, Apr 30, 2018 at 09:59:11PM +0200, Jörg Frings-Fürst wrote:
> > > 
> > > for the liboinig transition I testing the build of hhvm again libonig 
> > > 6.8.1-1.
> > > 
> > > The build fails with
> > > 
> > > [quote]
> > > In file included from /build/hhvm-3.21.0+dfsg/hphp/runtime/base/program-
> > > functions.cpp:117:0:
> > > /usr/include/oniguruma.h:347:1: error: 'UChar' does not name a type; did 
> > > you
> > > mean 'char'?
> > >  UChar* onigenc_strdup P_((OnigEncoding enc, const UChar* s, const UChar*
> > > end));
> > >  ^
> > >  char
> > 
> > But that's a problem in the lobonig headers? 
> > hphp/runtime/base/program-functions.cpp:117 simply does a
> > 
> > #include 
> 
> Actually this needs some changes on the HHVM end, found a fix.

The patch for HHVM is still needed to fix that the regex struc was moved to a
private header.

It also adds a workaround to address a bug in Oniguruma, though:
HHVM uses ONIG_ESCAPE_UCHAR_COLLISION and that is broken in 6.8.0/6.8.1
(see the comment in 
https://github.com/facebook/hhvm/commit/0bbbf67adc2643d04353cf2bdda2e1aa7c92d36f)

Cheers,
Moritz

Bug#897893: Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver

[Eugene Budanov]

Package: linux-image-4.9.0-6-amd64
Version: 4.9.82-1+deb9u3

Hi!

Here's a short problem description.

We have some Supermicro servers with the same configuration for all machines 
(hardware, kernels, packages, etc). A month ago, or maybe a bit later, all of 
these machines began crashing into kernel panic. I can't find any pattern of 
failure at all. But it happens very often. Some machines may drop into kernel 
panic a couple times a day! But usually machines crash about every 3 to 6 days. 
All of these machines have intensive network and i/o operations.

I saved dmesg log from one of these machines after the crash (see the 
attachment).

As far as I see, every machine probably has problems with mlx4_en or GRO. Also 
I see list_add double add => list_del corruption. Can I do anything to get more 
detailed logs? What additional information do you need for better problem 
diagnostics?



---
С уважением,
Буданов Евгений.
Системный администратор
Компания «Рестрим»


dmesg.log
Description: Binary data


lspci
Description: Binary data

Bug#897767: highwayhash: ftbfs with GCC-8

[Lumin]

On Fri, May 04, 2018 at 12:21:55PM +, Matthias Klose wrote:
> dpkg-gensymbols: warning: debian/libhighwayhash0/DEBIAN/symbols doesn't match 
> completely debian/libhighwayhash0.symbols
> --- debian/libhighwayhash0.symbols 
> (libhighwayhash0_0~20180209-g14dedec-3_amd64)
> +++ dpkg-gensymbolsJArbQP 2018-05-02 11:58:36.131189433 +
> @@ -14,8 +14,8 @@
>   
> _ZSt7shuffleIN9__gnu_cxx17__normal_iteratorIPmSt6vectorImSaImRSt23mersenne_twister_engineImLm64ELm312ELm156ELm31ELm13043109905998158313ELm29ELm6148914691236517205ELm17ELm8202884508482404352ELm37ELm1873444759240704ELm43ELm6364136223846793005EEEvT_SA_OT0_@Base
>  0~20180209-g14dedec
>   _ZZN11highwayhash4AVX211ConcatenateERKNS0_4V128IjEEmS4_E5table@Base 
> 0~20170419-g1f4a24f
>   _ZZN11highwayhash8Portable15HHStatePortable5ResetEPKmE5init0@Base 
> 0~20170419-g1f4a24f
> dh_makeshlibs: failing due to earlier errors
> make: *** [debian/rules:22: binary-arch] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess 
> returned exit status 2

Hi Matthias,

Thank you for reporting this. The build failure was simply due to the
symbol change. This issue can be fixed by a symbols patch when GCC-8
becomes the default compiler.


signature.asc
Description: PGP signature

Bug#897894: lua-torch-torch7 test failed with MKL

[Lumin]

Package: lua-torch-torch7
Version: 0~20170926-g89ede3b-3
Severity: minor

When we switch the alternative libblas.so.3 to MKL, torch will fail to
run the unittests:

  $ th
  > torch.test()

I havn't looked into this problem yet, but this failure could be avoided
by switch back to openblas or some other BLAS libraries.

Bug#897687: libpam-kwallet5: kwallet stopped working

[Sylvain L. Sauvage]

Hi,

  I’m using Plasma5 and kwallet did stop working.

-- 
 Sylvain L. Sauvage

Bug#897772: transition: miniupnpc

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 04/05/18 14:24, Thomas Goirand wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hi there!
> 
> We've uploaded miniupnpc to Experimental, and my sponsoree said he attempted
> a rebuild against all the reverse dependencies listed here:
> https://release.debian.org/transitions/html/auto-miniupnpc.html
> 
> There was no FTBFS problem, so we would like to upload miniupnpc 
> 2.0.20180410-2
> to unstable ASAP. Please let me know when I can upload.

Go ahead.

I will schedule the binNMUs when miniupnpc is built everywhere.

Cheers,
Emilio

Bug#897560: [Pkg-cmake-team] Bug#897560: cmake: CHECK_FUNCTION_EXISTS is broken

[Pirate Praveen]

On Thu, 3 May 2018 17:45:26 +0200 Felix Geyer  wrote:
> I guess you are taking about check_symbol_exists()?
> Access to the source and a full error log (what's the check_symbol_exists() 
> call that failed?)
> would help a lot.

https://anonscm.debian.org/cgit/collab-maint/libgit2.git/

unstable seems broken today so can't share a log right now.

Got this error with sbuild.

The following packages have unmet dependencies:
 sbuild-build-depends-libgit2-dummy : Depends: cmake but it is not going
to be installed
  Depends: libcurl4-gnutls-dev but
it is not going to be installed
E: Unable to correct problems, you have held broken packages.

and ...

native-architecture: amd64
report:
 -
  package: sbuild-build-depends-libgit2-dummy
  version: 0.invalid.0
  architecture: amd64
  status: broken
  reasons:
   -
missing:
 pkg:
  package: libldap-2.4-2
  version: 2.4.46+dfsg-1
  architecture: amd64
  unsat-dependency: libldap-common:amd64 (>= 2.4.46+dfsg-1)
 depchains:
  -
   depchain:
-
 package: sbuild-build-depends-libgit2-dummy
 version: 0.invalid.0
 architecture: amd64
 depends: cmake:amd64
-
 package: cmake
 version: 3.11.1-1
 architecture: amd64
 depends: libcurl3:amd64 (>= 7.16.2)
-
 package: libcurl3
 version: 7.58.0-2
 architecture: amd64
 depends: libldap-2.4-2:amd64 (>= 2.4.7)

> From a first glance though this looks like expected behavior.
> You are testing for a library function so you need to set 
> CMAKE_REQUIRED_LIBRARIES accordingly.
> 
> > As this results in other packages failing to build, please consider fixing 
> > ASAP.
> 
> Which packages? Can you give some examples?

libgit2 0.27 (in git linked above)

> Cheers,



signature.asc
Description: OpenPGP digital signature

Bug#897560: [Pkg-cmake-team] Bug#897560: Bug#897560: cmake: CHECK_FUNCTION_EXISTS is broken

[Lisandro Damián Nicanor Pérez Meyer]

On 4 May 2018 at 10:15, Pirate Praveen  wrote:
> On Thu, 3 May 2018 17:45:26 +0200 Felix Geyer  wrote:
>> I guess you are taking about check_symbol_exists()?
>> Access to the source and a full error log (what's the check_symbol_exists() 
>> call that failed?)
>> would help a lot.
>
> https://anonscm.debian.org/cgit/collab-maint/libgit2.git/
>
> unstable seems broken today so can't share a log right now.
>
> Got this error with sbuild.
>
> The following packages have unmet dependencies:
>  sbuild-build-depends-libgit2-dummy : Depends: cmake but it is not going
> to be installed
>   Depends: libcurl4-gnutls-dev but

There is curl transition marked as "planned", but maybe it has started already?

Bug#897897: Kernel security fix (for CVE-2018-1108) -> AutoFS won't start

[Cédric Dufour - Idiap Research Institute]

Package: autofs
Version: 5.1.2-1
Severity: important

Hello,

Following latest Debian/Stretch kernel (security) update - and the fix for 
CVE-2018-1108 - autofs blocks until the kernel RNG reports its proper 
initialization ("random: crng init done" in dmesg), which can take up to 
*several minutes* in entropy-starving VMs.

Problem is the corresponding systemd unit is configured to timeout after 180 
seconds. Past this timeout, AutoFS will be failed and won't start at all (until 
manually restarted).

One can fix this issue by having entropy poured into the VMs using rng-tools 
(along virtio-rng), haveged, etc.

I was wondering whether this might/ought not to be fixed in autofs itself ?

Best,

Cédric

PS: the (root) issue (kernel RNG blocking at boot) is already being discussed 
on LKML: https://lkml.org/lkml/2018/4/29/121

-- 
Cédric Dufour @ Idiap Research Institute

Bug#897896: gcc-7: "gcc" doesn't run "as" from $PATH

[Philipp Marek]

Package: gcc-7
Version: 7.3.0-17
Severity: normal

"gcc" doesn't run "as" from $PATH, but uses a hardcoded location; the issue 
seems to arise from
  
https://anonscm.debian.org/viewvc/gcccvs/branches/sid/gcc-7/debian/rules2?r1=10122&r2=10123&;
(see gcc/gcc.c, "find_a_file()" function and the DEFAULT_ASSEMBLER macro).

This means that I can't have the compiler output processed before piping it 
to /usr/bin/as any more; sadly neither the "-B" option (see also #896057) 
nor $COMPILER_PATH nor $GCC_EXEC_PREFIX work, these are deactivated by the 
"--with-as" => DEFAULT_ASSEMBLER setting.

Please revert, and/or give me another way to redirect the assembler output.

Thank you very much!



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

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

Versions of packages gcc-7 depends on:
ii  binutils  2.30-15
ii  cpp-7 7.3.0-17
ii  gcc-7-base7.3.0-17
ii  libc6 2.27-3
ii  libcc1-0  8-20180425-1
ii  libgcc-7-dev  7.3.0-17
ii  libgcc1   1:8-20180425-1
ii  libgmp10  2:6.1.2+dfsg-3
ii  libisl19  0.19-1
ii  libmpc3   1.1.0-1
ii  libmpfr6  4.0.1-1
ii  libstdc++68-20180425-1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages gcc-7 recommends:
ii  libc6-dev  2.27-3

Versions of packages gcc-7 suggests:
ii  gcc-7-doc 7.2.0-1
pn  gcc-7-locales 
pn  gcc-7-multilib
pn  libasan4-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information

-- 

Bug#897898: libldap-common is missing

[Mathieu Mitchell]

Package: openldap
Version: 2.4.46+dfsg-2

The libldap-common package is missing from the packages list.

This means common packages, such as curl, or even reportbug, cannot be
installed because they eventually depend on this package.
Digging the list of requirements leads to the missing package,
libldap-common.

root@f74a0b1dd389:/# apt-get update
Hit:1 http://cdn-fastly.deb.debian.org/debian sid InRelease
Reading package lists... Done
root@f74a0b1dd389:/# apt-get install libldap-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libldap-common is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libldap-common' has no installation candidate

root@f74a0b1dd389:/# apt-cache policy libldap-common
libldap-common:
  Installed: (none)
  Candidate: (none)
  Version table:

Additionally, the filelist link for the package crashes with a No such
package: https://packages.debian.org/sid/all/libldap-common/filelist

Also, the following command indicates the package is missing from the main
package list:
curl http://ftp.ca.debian.org/debian/dists/sid/main/binary-amd64/Packages.gz
| zgrep
'^Package: libldap-common'

Bug#897893: Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver

[Ben Hutchings]

Control: tag -1 moreinfo

On Fri, 2018-05-04 at 15:35 +0300, Eugene Budanov wrote:
> Package: linux-image-4.9.0-6-amd64
> Version: 4.9.82-1+deb9u3
> 
> Hi!
> 
> Here's a short problem description.
> 
> We have some Supermicro servers with the same configuration for all
> machines (hardware, kernels, packages, etc). A month ago, or maybe a
> bit later, all of these machines began crashing into kernel panic. I
> can't find any pattern of failure at all. But it happens very often.
> Some machines may drop into kernel panic a couple times a day! But
> usually machines crash about every 3 to 6 days. All of these machines
> have intensive network and i/o operations.
> 
> I saved dmesg log from one of these machines after the crash (see the
> attachment).
> 
> As far as I see, every machine probably has problems with mlx4_en or
> GRO. Also I see list_add double add => list_del corruption. Can I do
> anything to get more detailed logs? What additional information do
> you need for better problem diagnostics?

The WARNING messages show that there are out-of-tree modules (i.e. not
part of the kernel package) loaded.  What are those?

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug



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

Bug#874457: More info needed

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 moreinfo

Hi! Can you still reproduce this bug?

-- 
Gabardinas "Windows 95". Se cuelgan solas.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2

[Benjamin Kaduk]

Hi Lucas,

On Wed, May 02, 2018 at 10:52:53PM +0200, Lucas Nussbaum wrote:
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > rx/perf.ok
> > volser/vos-man..ok
> > volser/vos..FAILED 5
> > bucoord/backup-man..ok
> > kauth/kas-man...ok
> > 
> > Failed Set Fail/Total (%) Skip Stat  Failing Tests
> > -- --    
> > 
> > volser/vos1/6 17%00  5

Unfortunately the upstream build system does not capture verbose
test output for display in case of failure, but from the test number
we can deduce that what is failing is that an outputted list of
addresses does not match the expected string:
char expecting[] = "10.0.0.0\n10.0.0.1\n10.0.0.2\n10.0.0.3\n10.0.0.4\n"
   "10.0.0.5\n10.0.0.6\n10.0.0.7\n10.0.0.8\n10.0.0.9\n"
   "10.0.0.10\n10.0.0.11\n10.0.0.12\n10.0.0.13\n"
   "10.0.0.14\n10.0.0.15\n";

I note that this test is disabled when the system's hostname
resolves to a loopback address because those addresses are forbidden
from being entered into the database as fileserver addresses, but
even when I change my local configuration to avoid that, I still
cannot reproduce the test failure locally.

I surmise that the AWS machine may be getting assigned a 10/8
address as its primary address, and perhaps that would interfere
with some of what the test is doing.  Do you happen to know more
about the network configuration on the AWS systems used for these
autopkgtests?

Thanks,

Ben

Bug#773350: More info

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 moreinfo

Hi! Can you still reproduce this behavior? Although I think it's expected, as 
Qt Creator needs at least OpenGL 2 due to QML usage.

-- 
Primero te ignorarán, luego se reirán,
luego te combatirán, luego ganarás.
 Mahatma Gandhi

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#875747: libgrpc-dev: Please package latest upstream version

[Pirate Praveen]

On Mon, 16 Apr 2018 19:03:28 +0530 Pirate Praveen 
wrote:
> On Thu, 14 Sep 2017 10:10:46 +0100 "George B."  
> wrote:> Please package the latest version from upstream (1.6.0 at this 
> time).
> 
> 
> I'd like to have grpc 1.10 for gitlab. Any plans for updating?

I have started working on this and have a basic version that builds in
experimental.

I have pushed my changes to https://salsa.debian.org/debian/grpc I'm
planning to do an nmu once I fix all the lintian warnings and errors.



signature.asc
Description: OpenPGP digital signature

Bug#897898: [Pkg-openldap-devel] Bug#897898: libldap-common is missing

[Ryan Tandy]

Hi,

On Fri, May 04, 2018 at 01:57:10PM +, Mathieu Mitchell wrote:

Package: openldap
Version: 2.4.46+dfsg-2

The libldap-common package is missing from the packages list.


In the version you mention I did include libldap-common in the upload, 
and rmadison claims it's present in unstable:


libldap-common | 2.4.46+dfsg-2   | unstable  | all

And yet, you're right, it's missing from Packages on every architecture 
(except, for some reason, armhf). Talking to the relevant people to get 
this fixed now... Apologies for the inconvenience.

Bug#816445: More info needed

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 moreinfo

Hi! Can you still reproduce this bug?

-- 
Combata las características. Si una característica no es absolutamente
esencial, descártela, especialmente si tiene el mismo efecto que se
puede alcanzar mediante la combinación de otras características.
  Andrew S. Tanenbaum, de su libro "Computer Networks"

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#833446: More info needed

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 moreinfo

Hi! Can you still reproduce this bug?


-- 
6: Cual es el boton del mouse que permite acceder a las acciones mas
comunes del manejo de archivos
* Depende el tipo de accion mas comun
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#875747: libgrpc-dev: Please package latest upstream version

[Pirate Praveen]

On Fri, 4 May 2018 19:52:39 +0530 Pirate Praveen
 wrote:
> I have pushed my changes to https://salsa.debian.org/debian/grpc I'm
> planning to do an nmu once I fix all the lintian warnings and errors.
> 

W: grpc source: debian-rules-uses-unnecessary-dh-argument dh ...
--parallel (line 25)

This is an easy fix I guess.

W: grpc source: changelog-should-mention-nmu

Fixed already.

W: grpc source: patch-file-present-but-not-mentioned-in-series
make-pkg-config-files-nonexecutable.diff
W: grpc source: patch-file-present-but-not-mentioned-in-series
openssl-1.1.0.diff

I will remove these file.

W: grpc source: pear-package-without-pkg-php-tools-builddep

I will add this to build deps.

E: grpc source: missing-notice-file-for-apache-license NOTICE.txt

I will install this file.

W: libgrpc-dev: pkg-config-unavailable-for-cross-compilation
usr/lib/pkgconfig/grpc.pc
W: libgrpc-dev: pkg-config-unavailable-for-cross-compilation
usr/lib/pkgconfig/grpc_unsecure.pc
W: libgrpc++-dev: pkg-config-unavailable-for-cross-compilation
usr/lib/pkgconfig/grpc++.pc
W: libgrpc++-dev: pkg-config-unavailable-for-cross-compilation
usr/lib/pkgconfig/grpc++_unsecure.pc

I will need some help here.

W: libgrpc3: package-name-doesnt-match-sonames libgpr6 libgrpc6
libgrpc-cronet6 libgrpc-unsecure6

Hopefully updating in control will be enough.



signature.asc
Description: OpenPGP digital signature

Bug#897893: Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver

[Eugene Budanov]

Hi!

This is only one driver, mpt2sas downloaded from LSI site version 22.00 instead 
13.0 from Debian package. Because from beggining we think that is was a 
problems in RAID controller. But this hypothesis turned out as erroneous. On 
other machines we use mpt2sas in-kernel driver only. No 3rd party drivers.

---
С уважением,
Буданов Евгений.
Системный администратор
Компания «Рестрим»

On 4 мая 2018 г., 17:08 +0300, Ben Hutchings , wrote:
> Control: tag -1 moreinfo
>
> On Fri, 2018-05-04 at 15:35 +0300, Eugene Budanov wrote:
> > Package: linux-image-4.9.0-6-amd64
> > Version: 4.9.82-1+deb9u3
> >
> > Hi!
> >
> > Here's a short problem description.
> >
> > We have some Supermicro servers with the same configuration for all
> > machines (hardware, kernels, packages, etc). A month ago, or maybe a
> > bit later, all of these machines began crashing into kernel panic. I
> > can't find any pattern of failure at all. But it happens very often.
> > Some machines may drop into kernel panic a couple times a day! But
> > usually machines crash about every 3 to 6 days. All of these machines
> > have intensive network and i/o operations.
> >
> > I saved dmesg log from one of these machines after the crash (see the
> > attachment).
> >
> > As far as I see, every machine probably has problems with mlx4_en or
> > GRO. Also I see list_add double add => list_del corruption. Can I do
> > anything to get more detailed logs? What additional information do
> > you need for better problem diagnostics?
>
> The WARNING messages show that there are out-of-tree modules (i.e. not
> part of the kernel package) loaded. What are those?
>
> Ben.
>
> --
> Ben Hutchings
> Every program is either trivial or else contains at least one bug
>

Bug#740588: Reassigning

[Lisandro Damián Nicanor Pérez Meyer]

reassign 740588 src:qtbase-opensource-src
tag 740588 wontfix
thanks

Indeed this is a qmake limitation which won't get fixed. Except maybe if 
someone jumps in to do it in upstream, but I find that difficult.

-- 
 me cago en el gato, es como la tercera vez que me apreta
backspace mientras tengo apretados ctrl y alt
  Visto en #lugfi, irc.freenode.net

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#834543: Upstream bug

[Lisandro Damián Nicanor Pérez Meyer]

forwarded 834543 https://bugreports.qt.io/browse/QTCREATORBUG-20373
tag 834543 upstream
thanks

Thanks for your bug report! The bug has been reported to upstream in the URL 
above. I do strongly suggest you to subscribe to the upstream bug.

Kinds regards, Lisandro.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#890673: eboard: watch file update further details

[Amy Kos]

For further details, please see eboard author website:
https://www.bergo.eng.br/eboard/

Bug#897900: ITP: node-turbolinks -- Turbolinks makes navigating your web application faster

[Sruthi Chandran]

Package: wnpp
Severity: wishlist
Owner: Sruthi Chandran 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-turbolinks
  Version : 5.1.1
  Upstream Author : packagethief, sstephenson
* URL : https://github.com/turbolinks/turbolinks#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Turbolinks makes navigating your web application faster
 Get the performance benefits of a single-page application without the added
 complexity of a client-side JavaScript framework. Use HTML to render your
 views on the server side and link to pages as usual. When you follow a
link,
 Turbolinks automatically fetches the page, swaps in its , and merges
 its , all without incurring the cost of a full page load.
 .
 Node.js is an event-based server-side JavaScript engine.



signature.asc
Description: OpenPGP digital signature

Bug#897627: tex: please support SOURCE_DATE_EPOCH for dvi too

[Norbert Preining]

Hi Bill,

> > tex is tex as DEK wanted it. Please use etex, which is the pdftex binary
> > producing dvi.

Well, tex the name has already a copyright that makes this necessary.

> Maybe this could be documented in the manpage ? There is already:

Any suggestion for a paragraph?

> I think it is likely that if this bug is closed without changes, someone
> else will open it again.

Then again, it is about knowing the TeX & friends setup, which is not
completely trivial a thing.

> What about latex ?

latex is a format, and since some years already requires the etex
extensions, so if you run any kind of latex you know that it will
necessarily have etex extensions. That is, with latex/pdflatex you are
using the pdfetex engine, which has support for SDE.

Best

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#897627: tex: please support SOURCE_DATE_EPOCH for dvi too

[Norbert Preining]

> Developpers generally expect every programs that generates files with
> timestamp to honor SOURCE_DATE_EPOCH at some point.

Huuu? SDE was introduced really recently, I wouldn't say that
someone *generally* expect it to work. I (as developer) don't expect it. 
It is pushed by a certain initiative, it has a reason of existence, but
I wouldn't call it standard, by far.

> However, if this is not clearly documented, developpers might report
> this wishlist again and again.

And I will close it again and again. I have a rather rough stance
concerning the BTS. Too many rubbish bugs accumulating (well, ok, it is
still much better than Ubuntu, but still often a PITA where the problem
is between chair and keyboard).

Do you really think *any* developer will read man pages or README.Debian
to find out whether program xyz supports SDE? I would be surprised.

Best

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#897654: libpam-systemd: "Failed to create session: No such process"

[Michael Biebl]

Am 03.05.2018 um 23:56 schrieb Michael Gold:
> On Thu, May 03, 2018 at 23:42:34 +0200, Michael Biebl wrote:
>> Am 03.05.2018 um 23:12 schrieb Michael Gold:
>>> Is this problem already tracked?
>> I'd say this is a duplicate of #892585
> 
> Agreed.

That bug report mentioned, that dropping gid= was sufficient for him to
fix the issue.


-- 
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#897525: access-modifier-checker: FTBFS: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar

[Emmanuel Bourg]

Control: fixed -1 3.7-1
Control: close -1

Bug#897633: ITP: bolt -- system daemon to manage thunderbolt 3 devices

[intrigeri]

Is this different from #884363 or a duplicate?

In any case: thanks a lot for working on this!

Bug#847085: Clone and retitle

[Lisandro Damián Nicanor Pérez Meyer]

clone 847085 -1
retitle -1 .desktop metadata needs fixing
retitle 847085 Desktop file should be shipped in qtcreator and not in 
qtcreator-data

Hi! I see this as two separate bugs.

Matthias: any chance you can provide us a patch for 
https://appstream.debian.org/sid/main/issues/qtcreator.html ?
If you can I'll make sure to upstream it.

Thanks!


-- 
16: De quien es Internet
* De DIOS dado que todas las cosas del mundo le pertenecen
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#889706: gnome-shell: Gnome on Wayland causes GUI to freeze every ~1.5 seconds

[Peter Bašista]

It turns out that the issue was in the following GNOME Shell extension:

https://extensions.gnome.org/extension/120/system-monitor/

homepage:

https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet

When I disable it, the problem is gone.

This extension is probably blocking the main drawing or execution thread
(if there is such a thing in GNOME Shell) which then causes the entire GUI
to regularly freeze for a moment. But I am not fully sure.

Bug#897902: tweeny: please make the build reproducible

[Chris Lamb]

Source: tweeny
Version: 2+git20171120.b94ce07-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpaths
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

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

Patch attached.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible_build 1969-12-31 16:00:00.0 -0800
--- b/debian/patches/reproducible_build 2018-05-04 08:22:48.945029520 -0700
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2018-05-04
+
+--- tweeny-2+git20171120.b94ce07.orig/doc/Doxyfile.in
 tweeny-2+git20171120.b94ce07/doc/Doxyfile.in
+@@ -140,7 +140,7 @@ INLINE_INHERITED_MEMB  = NO
+ # shortest path that makes the file name unique will be used
+ # The default value is: YES.
+ 
+-FULL_PATH_NAMES= YES
++FULL_PATH_NAMES= NO
+ 
+ # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the 
path.
+ # Stripping is only done if one of the specified strings matches the left-hand
--- a/debian/patches/series 2018-05-04 08:19:02.625588291 -0700
--- b/debian/patches/series 2018-05-04 08:22:48.041016041 -0700
@@ -1,2 +1,3 @@
 no_analytics
 local_css
+reproducible_build

Bug#897788: libfm-qt: ftbfs with GCC-8

[Alf Gaida]

Hi doko,
thanks for the heads up - default in exp is gcc-9?

Thanks Alf

Bug#897592: ebtables: randomly FTBFS - makefile is not parallel safe

[James Cowgill]

Hi,

On 03/05/18 16:27, Alberto Molina Coballes wrote:
> Thanks James, these kinds of errors are often difficult to deal with.
> 
> Do you think that it should be enough disabling parallel build in dh?
> Tested on amd64 seems to work properly.

Yes that should workaround the problem.

It seems to me that these issues are caused by the rearrangements in the
last two hunks of the "makefile_adjustments.patch" patch. Maybe you can
remove those hunks? The package seems to build ok without them (except
that ebtables-config needs moving).

James



signature.asc
Description: OpenPGP digital signature

Bug#897904: libzstd: please make the build reproducible

[Chris Lamb]

Source: libzstd
Version: 1.3.4+dfsg-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: environment
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

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

This is because it encodes the number of CPUs of the build machine
into the documentation.

Patch attached.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/0014-Reproducible-build.patch  1969-12-31 
16:00:00.0 -0800
--- b/debian/patches/0014-Reproducible-build.patch  2018-05-04 
08:29:31.826847092 -0700
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2018-05-04
+
+--- libzstd-1.3.4+dfsg.orig/contrib/pzstd/Options.cpp
 libzstd-1.3.4+dfsg/contrib/pzstd/Options.cpp
+@@ -88,7 +88,7 @@ void usage() {
+   std::fprintf(stderr, "  -p, --processes   #: number of threads to use 
for (de)compression (default:%d)\n", defaultNumThreads());
+ 
+   std::fprintf(stderr, "ZSTD options:\n");
+-  std::fprintf(stderr, "  -# : # compression level (1-%d, 
default:%d)\n", kMaxNonUltraCompressionLevel, kDefaultCompressionLevel);
++  std::fprintf(stderr, "  -# : # compression level (1-%d, 
default:)\n", kMaxNonUltraCompressionLevel);
+   std::fprintf(stderr, "  -d, --decompress   : decompression\n");
+   std::fprintf(stderr, "  -ofile : result stored into `file` 
(only if 1 input file)\n");
+   std::fprintf(stderr, "  -f, --force: overwrite output without 
prompting, (de)compress links\n");
--- a/debian/patches/series 2018-05-04 08:18:10.696779480 -0700
--- b/debian/patches/series 2018-05-04 08:29:29.170809935 -0700
@@ -3,3 +3,4 @@
 0012-typos.patch
 pthread.patch
 0013-skip-memory-greedy-tests.patch
+0014-Reproducible-build.patch

Bug#897903: ITP: soapsnp -- resequencing utility that can assemble consensus sequence of genomes

[Steffen Moeller]

Package: wnpp
Severity: wishlist
Owner: Steffen Moeller 

* Package name: soapsnp
* URL : http://soap.genomics.org.cn/soapsnp.html
* License : GPL
  Description : resequencing utility that can assemble consensus sequence 
of genomes

Packaging team-maintained on https://salsa.debian.org:med-team/soapsnp

Bug#896343: Bug#896281: python-networkmanager: NetworkManager fails to import

[W. Martin Borgert]

NetworkManager.py says:

# We completely dynamically generate all classes using introspection data. As
# this is done at import time, use a special dbus connection that does not get
# in the way of setting a mainloop and doing async stuff later.
init_bus = dbus.SystemBus(private=True)

Maybe better have a module init function, that should be called
by the user of the library after import?

Bug#897633: ITP: bolt -- system daemon to manage thunderbolt 3 devices

[Jeremy Bicha]

Control: owner 884363 jbi...@debian.org
Control: forcemerge -1 884363

On Fri, May 4, 2018 at 11:14 AM, intrigeri  wrote:
> Is this different from #884363 or a duplicate?

same package

Jeremy Bicha

Bug#897671: u-boot does not work on sheevaplug

[Vagrant Cascadian]

On 2018-05-04, Martin Michlmayr  wrote:
> * Markus Krebs  [2018-05-04 06:33]:
>> Version: 2018.03+dfsg1-2
>> 
>> The u-boot.kwb provided at https://forum.doozan.com/read.php?3,12381 works.
>
> That is version 2017.07.  If you have time, could you try some
> versions from http://snapshot.debian.org/package/u-boot/  Not all of
> them but maybe
>
> 2018.01+dfsg1-2
> 2017.11+dfsg1-3
> 2017.09+dfsg1-3
> 2017.07+dfsg1-3

And also 2018.05-rc3+dfsg-1, currently in debian experimental; maybe
it's fixed in the newest version.

I do recall that there was some incompatible change regarding the
environment size on some of the marvell platforms, as u-boot.kwb grew
large enough to overwrite the environment section.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#897904: libzstd: please make the build reproducible

[Chris Lamb]

forwarded 897904 https://github.com/facebook/zstd/pull/1120
thanks

I've forwarded this upstream here:

  https://github.com/facebook/zstd/pull/1120


Regards,

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

Bug#897902: tweeny: please make the build reproducible

[Chris Lamb]

forwarded 897902 https://github.com/mobius3/tweeny/pull/6
thanks

I've forwarded this upstream here:

  https://github.com/mobius3/tweeny/pull/6


Regards,

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

Bug#897905: [pushover] segfault on some levels

[Sylvain L. Sauvage]

Package: pushover
Version: 0.0.5+git20180420-2
Severity: important

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

Some levels, for instance original levels 67 to 77, trigger a
segfault at loading.


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

Debian Release: buster/sid
  500 unstableftp.fr.debian.org 
  500 testing ftp.fr.debian.org 

--- Package information. ---
Depends  (Version) | Installed
==-+-=
libboost-filesystem1.62.0  | 1.62.0+dfsg-5+b1
libboost-system1.62.0  | 1.62.0+dfsg-5+b1
libc6(>= 2.14) | 
libfribidi0(>= 0.19.2) | 
libgcc1 (>= 1:3.0) | 
liblua5.3-0| 
libpng16-16   (>= 1.6.2-1) | 
libsdl-mixer1.2| 
libsdl-ttf2.0-0| 
libsdl1.2debian(>= 1.2.11) | 
libstdc++6(>= 5.2) | 
zlib1g(>= 1:1.1.4) | 


Package's Recommends field is empty.

Package's Suggests field is empty.


-- 
 Sylvain L. Sauvage

Bug#897906: Stop installing deprecated /etc/NetworkManager/VPN/nm-strongswan-service.name

[Michael Biebl]

Package: network-manager-strongswan
Version: 1.4.3-2
Severity: minor

Hi,

/etc/NetworkManager/VPN/nm-strongswan-service.name is required if you
have support for the deprecated libnm-glib enabled.

This is no longer the case for network-manager-strongswan, so this
conffile should be dropped from the package. Please remove the conffile
on upgrades as well (see man dh_installdeb .maintscript)

Regards,
Michael


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

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

Versions of packages network-manager-strongswan depends on:
ii  libatk1.0-0  2.28.1-1
ii  libc62.27-3
ii  libcairo-gobject21.15.10-3
ii  libcairo21.15.10-3
ii  libfribidi0  0.19.7-2
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.30-1
ii  libnm0   1.11.3-1
ii  libnma0  1.8.10-5
ii  libpango-1.0-0   1.42.1-1
ii  libpangocairo-1.0-0  1.42.1-1
ii  libsecret-1-00.18.6-2
ii  network-manager  1.11.3-1
pn  strongswan-nm

network-manager-strongswan recommends no packages.

network-manager-strongswan suggests no packages.

Bug#889469: Package on Mentors

[Andreas Schwarz]

I've done the packaging and uploaded it to mentors.debian.net
In the meanwhile Version 0.2.2

So it should be easier for everyone to get an idea.




signature.asc
Description: OpenPGP digital signature

Bug#897907: ITP: hashcheck -- verifies the files on a live mounted ISO image

[Kyle Robbertze]

Package: wnpp
Severity: wishlist
Owner: Kyle Robbertze 

* Package name: hashcheck
  Version : 1.0.0
  Upstream Author : Kyle Robbertze 
* URL : https://gitlab.com/paddatrapper/hashcheck
* License : GPL-3+
  Programming Lang: C++
  Description : verifies the files on a live mounted ISO image

Provides a graphical interface to verify a live mounted ISO image.
The image is expected to be mounted under /lib/live/mount/medium
It is useful as part of a live environment

This is a part of AIMS desktop and will be packaged for use in that,
though it is useful in Debian too.