Bug#923769: unblock: spl-linux/0.7.13-1

[Mo Zhou]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-CC: a...@debian.org

Please unblock package spl-linux
which will land on unstable shortly.

(explain the reason for the unblock here)

  New upstream release (released several hours ago).

(include/attach the debdiff against the package in testing)

  Maybe this is much better than the hard-to-review debdiff:
  
https://salsa.debian.org/zfsonlinux-team/spl/compare/debian%2F0.7.12-2...debian%2F0.7.13-1

unblock spl-linux/0.7.13-1

-- 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.19.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#923768: python-matplotlib: UnicodeDecodeError on importing pyplot in python2

[Andrey Skvortsov]

Package: python-matplotlib
Version: 2.2.3-6
Severity: normal
Tags: upstream, fixed-upstream

Dear Maintainer,

UnicodeDecodeError on importing pyplot If some module in call stack is
located in directory with non-ascii character in path. The problem is
that traceback.format_stack() returns list of 'str' objects in
python2. This problem happens only on python2.

Code for reproduction
Create two modules in a directory with a non-ascii character in the path.

#!/usr/bin/env python
# first_module.py
import second_module

# second_module.py
import matplotlib.pyplot

Run first module.

$ python2 first_module.py


Following traceback happens

Traceback (most recent call last):
  File "./a.py", line 3, in 
import second_module
  File "/home/developer/WorkData/PLC/beremiz/tmp/xыв/beremiz/second_module.py", 
line 3, in 
import matplotlib.pyplot
  File "/usr/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 71, in 

from matplotlib.backends import pylab_setup
  File "/usr/lib/python2.7/dist-packages/matplotlib/backends/__init__.py", line 
16, in 
line for line in traceback.format_stack()
  File "/usr/lib/python2.7/dist-packages/matplotlib/backends/__init__.py", line 
18, in 
if not line.startswith('  File "https://github.com/matplotlib/matplotlib/issues/11955

and it was fixed and release as part of 2.2.4 release
https://github.com/matplotlib/matplotlib/commit/69b4233a7d8ef0750f83aa63ff20b939e996cc4f

It makes python programs installed in user's directories with non-ascii symbols 
in path unusable.
Would be nice to get this minor change backported to be included in Buster.


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

Kernel: Linux 4.19.0-1-rt-amd64 (SMP w/8 CPU cores; PREEMPT)
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 python-matplotlib depends on:
ii  libc6 2.28-7
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.2.0-21
ii  libjs-jquery  3.3.1~dfsg-1
ii  libjs-jquery-ui   1.12.1+dfsg-5
ii  libpng16-16   1.6.36-5
ii  libstdc++68.2.0-21
ii  python2.7.15-4
ii  python-backports.functools-lru-cache  1.5-2
ii  python-cycler 0.10.0-1
ii  python-dateutil   2.7.3-3
ii  python-kiwisolver 1.0.1-2+b1
ii  python-matplotlib2-data   2.2.3-6
ii  python-numpy [python-numpy-abi9]  1:1.16.1-1
ii  python-pyparsing  2.2.0+dfsg1-2
ii  python-six1.12.0-1
ii  python-subprocess32   3.5.3-1
ii  python-tz 2018.9-1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages python-matplotlib recommends:
ii  python-pil  5.4.1-1
ii  python-tk   2.7.15-1+b1

Versions of packages python-matplotlib suggests:
pn  dvipng  
ii  ffmpeg  7:4.1.1-1
ii  ghostscript 9.26a~dfsg-2
ii  gir1.2-gtk-3.0  3.24.5-1
ii  inkscape0.92.4-2
pn  ipython 
ii  librsvg2-common 2.44.10-1
pn  python-cairocffi
pn  python-configobj
pn  python-excelerator  
ii  python-gi   3.30.4-1
ii  python-gobject-22.28.6-13+b1
pn  python-matplotlib2-doc  
ii  python-nose 1.3.7-4
ii  python-qt4  4.12.1+dfsg-2+b1
pn  python-scipy
ii  python-sip  4.19.13+dfsg-2
pn  python-tornado  
pn  python-traits   
ii  python-wxgtk3.0 3.0.2.0+dfsg-8
pn  texlive-extra-utils 
ii  texlive-latex-extra 2018.20190131-1
pn  ttf-staypuft

-- no debconf information

Bug#923750: gdcm: FTBFS in buster/sid

[Mathieu Malaterre]

On Tue, Mar 5, 2019 at 1:21 AM Santiago Vila  wrote:
> make[2]: *** [Makefile:6: refman.pdf] Error 1

That must be a regression in one of the tex (sid) packages. I can
build the pdf documentation just fine from my jessie Debian system:

https://sourceforge.net/projects/gdcm/files/gdcm%202.x/GDCM%202.8.9/gdcm-2.8.9.pdf

I'll check pdf build ASAP.

-M

Bug#923756: [Debian-med-packaging] Bug#923756: libhac-java: FTBFS in buster/sid

[Olivier Sallou]

- Andreas Tille  a écrit :
> Hi Debian Java team,
> 
> On Tue, Mar 05, 2019 at 12:19:40AM +, Santiago Vila wrote:
> > jh_build -J hac.jar src
> > find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
> > /usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.hac -d 
> > debian/_jh_build.hac -source 1.7 -target 1.7 -encoding ISO8859-1
> > warning: [options] bootstrap class path not set in conjunction with -source 
> > 7
> > 1 warning
> > find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
> > /usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
> > /usr/share/doc/default-jdk-doc/api -link 
> > /usr/share/doc/default-jre-headless/api -classpath :debian/_jh_build.hac -d 
> > debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp 
> > -source 1.7
> > Creating destination directory: "debian/_jh_build.javadoc/api/"
> > javadoc: error - The code being documented uses packages in the unnamed 
> > module, but the packages defined in /usr/share/doc/default-jdk-doc/api/ are 
> > in named modules.
> > javadoc: error - The code being documented uses packages in the unnamed 
> > module, but the packages defined in 
> > /usr/share/doc/default-jre-headless/api/ are in named modules.
> > 2 errors
> > make[1]: *** [debian/rules:9: override_dh_auto_build] Error 123
> 
> Any idea how to fix this?

Short term workaround would be to disable javadoc generation and related package

Found many related bugs but no quick resolution and patching code may be a long 
task

Olivier
> 
> Kind regards
> 
> Andreas.
> 
> -- 
> http://fam-tille.de
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

Bug#918881: broken distutils on python3.6.8-1

[Michael Psomaidis]

Woops, the specific way i resolved that was the following

   cd /usr/lib
   sudo cp -arv python3.7/distutils python3.6/

On Tue, 5 Mar 2019 17:21:49 +1100 raspberry wrote:

> The only way I was able to get this to work was to copy the version of
> distutils installed in the /usr/lib/python3.7/distutils to
> /usr/lib/python3.6/distutils folder which isn't ideal.
>
> I thought it was weird to not have distutils on 3.6 in the package from
> scratch and that's where i looked this bug up. Surely this isn't 
intended?

>
> The specific way I resolved this was the following, I've also listed
> package versions.
>
> cd /usr/lib
> python3.6/distutils/distutils/util.py
>
> python3.7/testing,now 3.7.2-2 amd64 [installed,automatic]
> python3.6/unstable,now 3.6.8-1 amd64 [installed]
>
> $ python3.6 -m virtualenv venv
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
>     "__main__", mod_spec)
>   File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
>     exec(code, run_globals)
>   File "/usr/local/lib/python3.6/dist-packages/virtualenv.py", line 22,
> in
>     import distutils.spawn
> ModuleNotFoundError: No module named 'distutils.spawn'
>
> $ python3.6 -m virtualenv venv
> Using base prefix '/usr'
> New python executable in /home/michael/redacted/venv/bin/python3.6
> Also creating executable in /home/michael/redacted/venv/bin/python
> Installing setuptools, pip, wheel...
> done.
>
> On Thu, 28 Feb 2019 10:36:02 +0100 j...@o2w.es
> (=?utf-8?B?Sm9zw6kgU8OhbmNoZXo=?= Moreno) wrote:
>
> > Is there any posibility to create a virtualenv on python3.6 in debian
> > sid right now?
> >
> > I'm looking for alternatives and I haven't found any property solution.
> >
> >
> > --
> > José Sánchez Moreno
> > O2W Leading Software - www.o2w.es
> > C/ Trovero Marin, 5 30730 San Javier (Murcia)
> > Tlf: 968 192 905 - 656 817 548
> > Condiciones Legales de este e-mail en: http://www.o2w.es/email
> >
> >
>
> --
> Michael Psomiadis
> https://raspberry.id.au/
>

Bug#872553: RC bugs in synaptic

[Jeremy Bicha]

These bugs are almost certainly duplicate of https://bugs.debian.org/818366

Could you handle marking them as duplicates? (Sorry, I find it tedious
to do that in Debian.)

I don't think Synaptic is going to work on Wayland in time for Buster
regardless of how many RC bugs we file against it. Maybe severity:
important is good enough with a mention in the Release Notes that
Debian GNOME uses Wayland by default and you'll need to log in to
"GNOME on Xorg" if you want to use certain apps like Synaptic or most
screen recording apps.

Jeremy

Bug#923767: RFP: node-runas -- Run command synchronously

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: node-runas
  Version : 3.1.1
  Upstream Author : Microsoft
* URL : https://salsa.debian.org/themusicgod1-guest/
* License : MIT
  Programming Lang: c
  Description : Run command synchronously

Launches a new process with the given command, with command line arguments in 
args.
This function is synchronous and returns the exit code when the command 
finished.

runas is a dependency of meteor ( #842425 ).

Bug#921757: Ping bug to make sure package will migrate to testing before automatic removal

[Andreas Tille]

I just ping thia bug to make sure package will migrate to testing before
automatic removal since I suspect there might be a racing condition
between removal and acceptance to testing.


-- 
http://fam-tille.de

Bug#923766: ITP: magiclantern -- Canon EOS camera deluxe featrues by firmware add on

[Gürkan Myczko]

Package: wnpp
Severity: wishlist

* Package name: magiclantern
  Version : 0+git20190405
  Upstream Authors: Trammell Hudson 
* URL : https://magiclantern.fm/
* License : GPL-2
  Description : Canon EOS camera deluxe featrues by firmware add on
 This is a free software add-on that runs from the SD/CF card and adds a 
host
 of new features to Canon EOS cameras that weren't included from the 
factory

 by Canon.
 .
 Supported cameras:
 - 5D Mark II, III
 - 6D, 7D, 50D, 60D
 - 500D/T1i, 550D/T2i, 600D/T3i, 650D/T4i, 700D/T5i
 - 1100D/T3
 - EOS M

Package will be availabe at http://phd-sid.ethz.ch/debian/magiclantern/

Interested people join #magiclantern on IRC (irc.gnu.org)

Bug#918881: broken distutils on python3.6.8-1

[raspberry]

The only way I was able to get this to work was to copy the version of 
distutils installed in the /usr/lib/python3.7/distutils to 
/usr/lib/python3.6/distutils folder which isn't ideal.


I thought it was weird to not have distutils on 3.6 in the package from 
scratch and that's where i looked this bug up. Surely this isn't intended?


The specific way I resolved this was the following, I've also listed 
package versions.


   cd /usr/lib
   python3.6/distutils/distutils/util.py

python3.7/testing,now 3.7.2-2 amd64 [installed,automatic]
python3.6/unstable,now 3.6.8-1 amd64 [installed]

$ python3.6 -m virtualenv venv
Traceback (most recent call last):
  File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.6/dist-packages/virtualenv.py", line 22, 
in 

    import distutils.spawn
ModuleNotFoundError: No module named 'distutils.spawn'

$ python3.6 -m virtualenv venv
Using base prefix '/usr'
New python executable in /home/michael/redacted/venv/bin/python3.6
Also creating executable in /home/michael/redacted/venv/bin/python
Installing setuptools, pip, wheel...
done.

On Thu, 28 Feb 2019 10:36:02 +0100 j...@o2w.es 
(=?utf-8?B?Sm9zw6kgU8OhbmNoZXo=?= Moreno) wrote:


> Is there any posibility to create a virtualenv on python3.6 in debian
> sid right now?
>
> I'm looking for alternatives and I haven't found any property solution.
>
>
> --
> José Sánchez Moreno
> O2W Leading Software - www.o2w.es
> C/ Trovero Marin, 5 30730 San Javier (Murcia)
> Tlf: 968 192 905 - 656 817 548
> Condiciones Legales de este e-mail en: http://www.o2w.es/email
>
>

--
Michael Psomiadis 
https://raspberry.id.au/

Bug#910249: Bumping up encryption to AES-256 by default

[Jeremy Bicha]

I just uploaded libblockdev 2.20-7. Please check if it fixes your issue.

If it does, would you be interested in filing the unblock bug to get
the fix in to Debian Buster?

https://release.debian.org/buster/freeze_policy.html

Thanks,
Jeremy Bicha

Bug#923740: unblock: pacemaker/2.0.1-1

[Niels Thykier]

Ferenc Wágner:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Dear Release Team,
> 
> Please advise about the situation with Pacemaker.
> 
> At the moment pacemaker_2.0.1~rc5-1 is 6 days old in unstable (it was
> uploaded on the day following its release) and now that it finally built
> on all architectures (it triggered a linker bug on amd64) I expect it to
> migrate to testing this week, well before the full freeze.
> 
> However, Pacemaker 2.0.1 final was released today and includes a single
> code change only, with the following commit message (the change itself
> is the deletion of lines at the end of the debdiff below):
> 
> High: libcrmcommon: complete interrupted live migrations correctly
> 
> 8435966 (2.0.0) got the sense of compare_version() wrong when
> attempting to remove the old behavior for recording partial live
> migrations, instead re-introducing it.
> 
> This causes a regression in behavior when a transition containing a
> live migration is aborted after the migrate_to has been initiated
> but before the migrate_from has been initiated. In that case, it
> would schedule a full start on the destination node rather than a
> migrate_from.
> 
> I think we should release buster with Pacemaker 2.0.1, thus with this
> fix and the small documentation fixes also bundled with it.  The added
> include directives just make previously indirect includes explicit, and
> our build doesn't use the abi-check script, so that change is a no-op.
> Full debdiff from 2.0.1~rc5-1 (which is on its way to testing):
> 
> [...]
> 
> Even if I uploaded 2.0.1-1 now, it would miss the freeze date by a day,
> kicking out 2.0.1~rc5-1 as well, which would be quite a shame,
> considering that it's almost as good as the final, and definitely better
> than 2.0.1~rc4-1 currently in testing.  Could you please provide a way
> for 2.0.1-1 final (not uploaded yet) to reach buster?
> 
> Thanks,
> Feri.
> 
> unblock pacemaker/2.0.1-1
> 

Hi Feri,

Thanks for filing the report.

Please let the current version of pacemaker as it is and then ping us on
this bug once it have.

Thanks,
~Niels

Bug#922730: cannot browse anything

[積丹尼 Dan Jacobson]

I'm instead going to give up on 32 bit completely, and buy a new
computer. So feel free to close this bug (if you confirm you can't
reproduce it on 32 bit.)

Bug#922730: cannot browse anything

[Jeremy Bicha]

On Tue, Mar 5, 2019 at 12:51 AM 積丹尼 Dan Jacobson  wrote:
> I'm instead going to give up on 32 bit completely, and buy a new
> computer. So feel free to close this bug (if you confirm you can't
> reproduce it on 32 bit.)

There may be a valid bug here. But it would take a significant amount
of time for me to test on 32-bit so I won't be doing that this week.

Jeremy

Bug#923765: libotf FTCBFS: uses the wrong pkg-config

[Helmut Grohne]

Source: libotf
Version: 0.9.13-4
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

libotf regressed cross building. It recently gained an invocation of the
wrong pkg-config. The attached patch fixes that using the
PKG_CHECK_MODULES macro. It automatically substitutes _CFLAGS and _LIBS
variables, so I renamed them in the build system. Furthermore,
PKG_CHECK_MODULES must not be used in an if (but can be used in AS_IF),
because it uses AC_REQUIRE. Please consider applying the patch.

Helmut
--- libotf-0.9.13.orig/configure.ac
+++ libotf-0.9.13/configure.ac
@@ -50,25 +50,22 @@
 
 # Check for Freetype2 usability.
 AC_CHECK_PROG(HAVE_PKG_CONFIG, pkg-config, yes)
-if test "x$HAVE_PKG_CONFIG" = "xyes"; then
-  FREETYPE_INC=`pkg-config freetype2 --cflags`
-  CPPFLAGS="$CPPFLAGS $FREETYPE_INC"
+AS_IF([test "x$HAVE_PKG_CONFIG" = "xyes"],[
+  PKG_CHECK_MODULES([FREETYPE],[freetype2],[],[HAVE_FREETYPE=no])
+  CPPFLAGS="$CPPFLAGS $FREETYPE_CFLAGS"
   AC_CHECK_HEADER(ft2build.h, HAVE_FREETYPE=yes,
   			  HAVE_FREETYPE=no CPPFLAGS=$save_CPPFLAGS)
   if test "x$HAVE_FREETYPE" = "xyes" ; then
-FREETYPE_LD_FLAGS=`pkg-config freetype2 --libs`;
-LIBS="$LIBS $FREETYPE_LD_FLAGS"
+LIBS="$LIBS $FREETYPE_LIBS"
 AC_CHECK_LIB(freetype, FT_Init_FreeType, HAVE_FREETYPE=yes,
 			   		 HAVE_FREETYPE=no)
   fi
-fi
+])
 
 if test "x$HAVE_FREETYPE" != "xyes" ; then
   echo "Freetype library wan't found in your system!"
   exit 1
 fi
-AC_SUBST(FREETYPE_INC)
-AC_SUBST(FREETYPE_LD_FLAGS)
 
 if test "x$no_x" != "xyes"; then
   X11_XT_XAW_XMU="-lX11 -lXt -lXaw -lXmu"
--- libotf-0.9.13.orig/libotf.pc.in
+++ libotf-0.9.13/libotf.pc.in
@@ -7,5 +7,5 @@
 Description: OpenType font library
 Version: @PACKAGE_VERSION@
 Requires: freetype2
-Libs: @FREETYPE_LD_FLAGS@ -L${libdir} -lotf
-Cflags: @FREETYPE_INC@ -I${includedir}
+Libs: @FREETYPE_LIBS@ -L${libdir} -lotf
+Cflags: @FREETYPE_CFLAGS@ -I${includedir}

Bug#922730: cannot browse anything

[Jeremy Bicha]

On Fri, Mar 1, 2019 at 5:57 PM 積丹尼 Dan Jacobson  wrote:
> Here's the situation on i686. Be sure to test on i686, not amd64, where
> it works fine.

Please report this issue upstream. I think you'll need to report it to
webkit instead of epiphany.

I think I'll be downgrading the severity of this bug this week so that
we can get 3.31.91 in to Buster. (Note that we may remove
epiphany-browser from Buster completely if the Debian Security Team is
not willing to try to maintain webkit2gtk in Buster.)

Thanks,
Jeremy Bicha

Bug#921637: Fixed in ronn-NG 0.8.1

[Andrew Janke]

Hi folks,

I have released a non-beta Ronn-NG 0.8.1 release which includes this 
fix, if you wanted to include a version that does not require bugfix 
patches.


Cheers,
Andrew

Bug#923764: console-setup-linux: boot script needs to label /run/console-setup on SE Linux systems

[Russell Coker]

Package: console-setup-linux
Version: 1.190
Severity: normal

The following patch makes it correctly label /run/console-setup.  If SE Linux
isn't enabled then restorecon does nothing, if restorecon isn't installed then
nothing happens.

--- /lib/console-setup/console-setup.sh.orig2019-03-05 16:15:58.324868518 
+1100
+++ /lib/console-setup/console-setup.sh 2019-03-05 16:16:07.916893505 +1100
@@ -10,6 +10,7 @@
 # Skip only the first time (i.e. when the system boots)
 [ ! -f /run/console-setup/boot_completed ] || do_configure=yes
 mkdir -p /run/console-setup
+   [ -x /sbin/restorecon ] && /sbin/restorecon /run/console-setup
 > /run/console-setup/boot_completed
 
 [ /etc/console-setup/cached_setup_terminal.sh \

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

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

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.56+nmu1
ii  kbd 2.0.4-4
ii  keyboard-configuration  1.190

console-setup-linux recommends no packages.

Versions of packages console-setup-linux suggests:
ii  console-setup  1.190

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.70
ii  liblocale-gettext-perl  1.07-3+b4

Versions of packages console-setup depends on:
ii  debconf 1.5.70
ii  keyboard-configuration  1.190
ii  xkb-data2.23.1-1

Versions of packages console-setup suggests:
ii  locales   2.28-5
ii  lsb-base  10.2018112800

Versions of packages console-setup-linux is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.0.4-4
ii  systemd   240-4

-- debconf information excluded

-- debsums errors found:
debsums: changed file /lib/console-setup/console-setup.sh (from 
console-setup-linux package)

Bug#923756: libhac-java: FTBFS in buster/sid

[Andreas Tille]

Hi Debian Java team,

On Tue, Mar 05, 2019 at 12:19:40AM +, Santiago Vila wrote:
> jh_build -J hac.jar src
> find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
> /usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.hac -d 
> debian/_jh_build.hac -source 1.7 -target 1.7 -encoding ISO8859-1
> warning: [options] bootstrap class path not set in conjunction with -source 7
> 1 warning
> find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
> /usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
> /usr/share/doc/default-jdk-doc/api -link 
> /usr/share/doc/default-jre-headless/api -classpath :debian/_jh_build.hac -d 
> debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp -source 
> 1.7
> Creating destination directory: "debian/_jh_build.javadoc/api/"
> javadoc: error - The code being documented uses packages in the unnamed 
> module, but the packages defined in /usr/share/doc/default-jdk-doc/api/ are 
> in named modules.
> javadoc: error - The code being documented uses packages in the unnamed 
> module, but the packages defined in /usr/share/doc/default-jre-headless/api/ 
> are in named modules.
> 2 errors
> make[1]: *** [debian/rules:9: override_dh_auto_build] Error 123

Any idea how to fix this?

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#764786: initscripts: forced fsck on root filesystem doesn't give progress after installing sysvinit-core

[Pierre Ynard]

tags 764786 moreinfo
severity 764786 minor
thanks

> After installing sysvinit-core and associated systemd stuff, I had a
> situation where the root filesystem had been mounted 34 times without
> checking and an fsck was forced.

I'm confused by your setup. Which init was in use then, systemd or
sysvinit? What changed compared to before?

> The fsck completed successfully but there was no progress indication
> unlike previously and I could not even tell if fsck was running or if
> the boot process had hung until it completed.

Could you give more details about the fsck that gave no progress
indication, and how it differed from fsck previously? It was on the same
system, same disk and same root filesystem as before, wasn't it? Which
filesystem type was it? Did you use some graphical boot, was the boot
sequence simply less verbose than before?

Could this be some issue similar to #813176 affecting systemd-fsck?

-- 
Pierre Ynard

Bug#923763: usb3

[Eutychios]

Bug happens because i plugged the mobile phon in a usb3 port switching 
it over to a usb2 port completely resolved the issue.

Bug#923763: mtp-detect output

[Eutychios]

sudo mtp-detect:

libmtp version: 1.1.16

Listing raw device(s)
Device 0 (VID=19d2 and PID=0307) is a ZTE V880E.
   Found 1 device(s):
   ZTE: V880E (19d2:0307) @ bus 2, dev 70
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB 
interface

LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
libusb_open() failed!: No such device
LIBMTP PANIC: Could not init USB on second attempt
Unable to open raw device 0
OK.

Bug#923763: gvfs-backends: Cannot mount MTP mobile Device

[siyia]

Package: gvfs-backends
Version: 1.38.1-3
Severity: important
Tags: a11y

Dear Maintainer,

Hello i installed gvfs-backends gvfs-fuse and libmtp, but i canot mount my
adroid mobile phone,as an mtp device and as a usb device (sdcard) on debian
10.I expected mounting my mobile phone both as an mtp and a usb device (sdcard)
to work like on other distros.



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

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

Versions of packages gvfs-backends depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gvfs 1.38.1-3
ii  gvfs-common  1.38.1-3
ii  gvfs-daemons 1.38.1-3
ii  gvfs-libs1.38.1-3
ii  libarchive13 3.3.3-4
ii  libavahi-client3 0.7-4+b1
ii  libavahi-common3 0.7-4+b1
ii  libavahi-glib1   0.7-4+b1
ii  libc62.28-7
ii  libcdio-cdda210.2+0.94+2-4
ii  libcdio-paranoia210.2+0.94+2-4
ii  libcdio182.0.0-2
ii  libgcrypt20  1.8.4-5
ii  libgdata22   0.17.9-3
ii  libglib2.0-0 2.58.3-1
ii  libgoa-1.0-0b3.30.1-2
ii  libgphoto2-6 2.5.22-3
ii  libgphoto2-port122.5.22-3
ii  libgudev-1.0-0   232-2
ii  libimobiledevice61.2.1~git20181030.92c5462-1
ii  libmtp9  1.1.16-2
ii  libnfs12 3.0.0-2
ii  libplist32.0.1~git20190104.3f96731-1
ii  libpolkit-gobject-1-00.105-25
ii  libsmbclient 2:4.9.4+dfsg-3
ii  libsoup2.4-1 2.64.2-2
ii  libusb-1.0-0 2:1.0.22-2
ii  libxml2  2.9.4+dfsg1-7+b3
ii  psmisc   23.2-1

Versions of packages gvfs-backends recommends:
ii  gnome-keyring  3.28.2-2

Versions of packages gvfs-backends suggests:
pn  bluez-obexd   
pn  samba-common  

-- no debconf information

Bug#686895: initscripts: /forcefsck: fsck -f undefined (e2fsck-ism)

[Pierre Ynard]

reopen 686895
thanks

/etc/init.d/checkfs.sh also checks forcefsck to pass -f to fsck,
so it needs to be fixed too. It won't be as simple as checkroot.sh
because fsck -A can apply to any number of filesystems of any type and
checkfs.sh doesn't track specifics when calling it.

Perhaps the simplest approach, if forcefsck is requested, would be to
add a first pass of fsck -A -f -t ext3,... and then let the normal code
proceed: this saves a lot of complexity and the worst that should happen
is that fsck wastes a bit of time doing a fast and clean second check of
the involved filesystems after the forced slow check.

Also, I can see that at least reiserfsck too honors -f as --force with
the same meaning, so I suppose it should be added alongside ext*.

-- 
Pierre Ynard

Bug#923734: closed by Matthias Klose (Re: Bug#923734: closed by Matthias Klose (Re: Bug#923734: Python needs updating: version push))

[Brian Holaday]

Hi Matthias,

I did not know if someone would get a reply if the ticket was closed: can
you confirm this for me. I am new: so I would ask that you review your
comments carefully even if it means just helping/self resolving with good
feedback: relevant information.

On Mon, Mar 4, 2019 at 4:09 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the python package:
>
> #923734: Python needs updating: version push
>
> It has been closed by Matthias Klose .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Matthias Klose <
> d...@debian.org> by
> replying to this email.
>
>
> --
> 923734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923734
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Matthias Klose 
> To: 923...@bugs.debian.org, 923734-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 5 Mar 2019 00:06:02 +0100
> Subject: Re: Bug#923734: closed by Matthias Klose  (Re:
> Bug#923734: Python needs updating: version push)
> On 04.03.19 23:29, Brian Holaday wrote:
> > I seem to be having issues then with installing: 3.5.3 on Stretch.
> >
> > # sudo apt-get install python3.5
> >> #python3.5 is already the newest version (3.5.3-1+deb9u1).
> >
> > Is Python 3.5 only for Buster or SID?
>
> no, for stretch. There is no 3.5 and 3.6. for buster.  Please stop
> re-opening
> this issue.
>
> > On Mon, Mar 4, 2019 at 12:48 PM Debian Bug Tracking System <
> > ow...@bugs.debian.org> wrote:
> >
> >> This is an automatic notification regarding your Bug report
> >> which was filed against the python package:
> >>
> >> #923734: Python needs updating: version push
> >>
> >> It has been closed by Matthias Klose .
> >>
> >> Their explanation is attached below along with your original report.
> >> If this explanation is unsatisfactory and you have not received a
> >> better one in a separate message then please contact Matthias Klose <
> >> d...@debian.org> by
> >> replying to this email.
> >>
> >>
> >> --
> >> 923734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923734
> >> Debian Bug Tracking System
> >> Contact ow...@bugs.debian.org with problems
> >>
> >>
> >>
> >> -- Forwarded message --
> >> From: Matthias Klose 
> >> To: Brian Holaday , 923...@bugs.debian.org,
> >> 923734-d...@bugs.debian.org
> >> Cc:
> >> Bcc:
> >> Date: Mon, 4 Mar 2019 20:46:16 +0100
> >> Subject: Re: Bug#923734: Python needs updating: version push
> >> On 04.03.19 19:37, Brian Holaday wrote:
> >>> Package: python
> >>> Version: 2.7.13-2
> >>> severity: important
> >>>
> >>> Issue:
> >>>
> >>> Python 3.7.2 has been released out for some time now. Can we get an
> >> update
> >>> pushed out to stretch-backports
> >>
> >> no, not doing that.
> >>
> >>> or SID at some point?
> >>
> >> it's there "for some time now"
> >>
> >>
> >> -- Forwarded message --
> >> From: Brian Holaday 
> >> To: sub...@bugs.debian.org
> >> Cc:
> >> Bcc:
> >> Date: Mon, 4 Mar 2019 11:37:37 -0700
> >> Subject: Python needs updating: version push
> >> Package: python
> >> Version: 2.7.13-2
> >> severity: important
> >>
> >> Issue:
> >>
> >> Python 3.7.2 has been released out for some time now. Can we get an
> update
> >> pushed out to stretch-backports or SID at some point?
> >>
> >
>
>
> -- Forwarded message --
> From: Brian Holaday 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 4 Mar 2019 11:37:37 -0700
> Subject: Python needs updating: version push
> Package: python
> Version: 2.7.13-2
> severity: important
>
> Issue:
>
> Python 3.7.2 has been released out for some time now. Can we get an update
> pushed out to stretch-backports or SID at some point?
>

Bug#923741: new upstream release

[Antoine Beaupré]

On 2019-03-04 18:26:13, Jason Pleau wrote:
> Hi
>
> On 2019-03-04 4:53 p.m., Antoine Beaupre wrote:
>> Package: rofi
>> Version: 1.5.1-1
>> Severity: wishlist
>> 
>> A new release (1.5.2) of rofi was published:
>> 
>> https://github.com/DaveDavenport/rofi/releases/tag/1.5.2
>> 
>> I've tried to upgrade this myself but there's weird stuff going on, as
>> "git diff 1.5.0..upstream/1.5.0" differs, yet there's no +dfsg tag or
>> a clear way to reproduce the orig tarball from the git repo.
>> 
>
> I don't use the github-generated tarballs, they are missing certain
> files (an active contributor to rofi has different projects that aren't
> meant to be distributed separately, but are included in rofi. Those are
> pulled in when they run 'make dist' iirc)
>
>
> I used gbp import-orig --upstream-vcs-tag=1.5.1 rofi-1.5.1.tar.gz (file
> taken from
> https://github.com/DaveDavenport/rofi/releases/download/1.5.2/rofi-1.5.1.tar.gz,
> different than the github tag tarball).
>
> Hope that helps. Thanks for looking into the update, I've been busy with
> other stuff for a little while now =/

I understand. I mistakenly thought the debian git repo was derived from
upstream, I must have misunderstood.

I'm mostly interested in getting this issue fixed:

https://github.com/DaveDavenport/rofi/issues/928

.. but this will require not only 1.5.2 but whatever the "next" branch
is going to be, so I doubt that will make it into buster, especially
considering how extensive the changes are between rofi patch releases.

So I'm not sure I'll be working on this any time soon... But at least
this is documented for the next one that stumbles upon that issue. ;)

That being said, should I take your comment as a go-ahead for a
low-delay NMU? :)

https://wiki.debian.org/LowThresholdNmu

Thanks!

A.

--
La nature n'a créé ni maîtres ni esclaves
Je ne veux ni donner ni recevoir de lois.
- Denis Diderot

Bug#524094: base: Sometimes usb disk fails to mount on boot

[Pierre Ynard]

severity 637054 normal
merge 510367 524094 637054
thanks

> The disk has some powersaving feature and takes a few seconds to 'wake
> up.' I wonder if the boot scripts call the mount command before the
> device nodes have been created??

Yes, this is what happens. Unfortunately there is no way to predict how
long a USB disk is going to take to be detected, if it ever is, so this
is not an easy problem to solve.

> mount_all_local() {
> mount -a -t nonfs,nfs4,smbfs,cifs,ncp,ncpfs,coda,ocfs2,gfs,gfs2 -O 
> no_netdev
> }
>
> Now that function is supposed to mount all local filesystems?? But it
> will only mount the ones of the specified types, and the list omits
> common types like ext2 and ext3 (my problem partitions being ext3).

No, the list starts with "no" which means that on the contrary, it
really specifies a list of filesystem types that will not be mounted.
ext3 and others will be mounted fine by this, changing this line won't
solve the problem.

-- 
Pierre Ynard

Bug#601054: add comments to /etc/init.d/.depend.* saying what program put them there

[Jesse Smith]

On 2/4/19 7:22 AM, Dmitry Bogatov wrote:
> [2019-02-02 11:38] Jesse Smith 
>> On 2/2/19 6:26 AM, Dmitry Bogatov wrote:
>>> I believe we already discussed this issue and came to conclusion, that
>>> the right thing to do would be to generate .depends files in
>>> /var/lib/insserv and adjust `startpar' accordingly.
>> Someone suggested doing this, it was an option on the table. But no
>> agreement has been come to so far as I know.
> I take off my Debian hat, and as regular user ask you, upstream
> maintainer, can you please .depends files from /etc/ to /var, to improve
> compliance with FHS.


This how now been done upstream and it will be implemented in the next
releases of insserv and startpar.  Both programs will default to using
/var in the future, with a legacy option to use /etc if the
administration wishes.

- Jesse

Bug#923762: unblock: mblaze/0.5.1-1

[Nicolas Braud-Santoni]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

I uploaded a new version of mblaze, which reset the package's transition
countdown, which will cause it to miss the hard freeze window:

  https://qa.debian.org/excuses.php?package=mblaze


I did so as the newest upstream release includes security-relevant changes:

  mblaze (0.5.1-1) unstable; urgency=high (security fixes)
  
* New upstream release (2019-03-03)
  + Fixes for buffer-overflows, found by fuzzing.
  + Fixes for memleaks.
  
* Remove unused lintian override
* debian/rules: Remove useless dh_missing invocation.
  A single binary package is being produced.
  
   -- Nicolas Braud-Santoni   Mon, 04 Mar 2019 18:40:01 +0100


Moreover, version 0.5-1 closes several Debian bugs (including a RC one):

  mblaze (0.5-1) unstable; urgency=medium
  
* New upstream release (2019-02-09)
  + Closes: 921891
  + GNUmakefile: correct reference to SOURCE_DATE_EPOCH, patch by Chris Lamb
Closes: #907537 
  
* Rename mless and msort to mblaze-less and mblaze-sort
  Closes: #887988 correctly, avoids conflicts on mpdtoys & msort
  
* Switch to debhelper 12.
  The compatibility level is now controlled by a Build-Depends.
  
* Declare compliance with policy v4.2.1.
  No change required.
  
* debian/rules
  + Make dh_missing fail the build
  + Symlink docs from mblaze-* to mblaze
  
   -- Nicolas Braud-Santoni   Tue, 12 Feb 2019 11:44:33 +0100


The debdiff is attached.


Best,

  nicoo

unblock mblaze/0.5.1-1

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAlx9wacRHG5pY29vQGRl
Ymlhbi5vcmcACgkQ5vmO4pLV7MsdVw//X2febyz+EoW+0lN1iSGZYSeqJhIzC11m
zOippy/KMeCjbjPuqgI1xBTuLBzNYbV+Y6gwf94+4O8KdqRcxHhjP1zE5ttWqVQD
bzMmIB4hr1xIua11OG9Oy1FdG+Fs49nqmaYvo4q7k0qg0VfohwBJEuHnPZEea14y
iT/7o/nnhqNnhZIlNv1dhCJWA00hlMt18/7QjG9bSdYRo8iJUdNmkVY750Adv1+S
MicSLHtnGy+/2AGYxU/0oW6sPFPBLiXli9gpqN6KhwdF4L6aroRnMswfbThxtc/s
GmFETyK/UIJ/6N5pt3ff9fSeU3CHvJclNm4TljKFPfGg4r49Oj+rZeXepddg5Acv
7AaXhB3gMZEwgKtmM02kqwMDdWPRZ3Fwlo6La/3ZJuflNnaBgytlr90Bh8lCAyPI
rMjrtP0jcWq1EIRWUgqCaIPFMfvwPMAyTRtORfzOdGtC9ZOBnEBzuqNgHqv5qpEt
dLQGHFRQJwDrpFc0veWqXZ01UcIO39fNFIMxUf1nAYw80NRcMRvvCT8IUucCLybq
PKn6lLwUfyu+MbfIdyuw7F9hSgMVINmTX1lH8u+Mk1L9p2sn+96JXh1YWAVtrVhn
+k8sSA2P5lOBWQLrRtq34VIjv9zlNRKz+5JO4vbdQ9AuZI+0C77PKK08nnixPCrc
EL4q69REWC0=
=AOMb
-END PGP SIGNATURE-
diff -Nru mblaze-0.4/blaze822.c mblaze-0.5.1/blaze822.c
--- mblaze-0.4/blaze822.c   2018-08-15 17:16:45.0 +0200
+++ mblaze-0.5.1/blaze822.c 2019-03-03 17:12:56.0 +0100
@@ -152,14 +152,20 @@
 // never writes more than dstmax to dst
 // returns how many bytes were appended
 static size_t
-safe_append(char *dst, size_t dstmax, char *strbeg, char *strend)
+safe_append(char *dst, size_t dstmax, char *srcbeg, char *srcend)
 {
-   size_t dstlen = strlen(dst);
-   if (dstmax - dstlen - 1 < strend - strbeg)
-   strend = strbeg + (dstmax - dstlen - 1);
-   memcpy(dst + dstlen, strbeg, strend - strbeg);
-   dst[dstlen + (strend - strbeg)] = 0;
-   return strend - strbeg;
+   size_t srclen = srcend - srcbeg;
+   size_t dstlen = strnlen(dst, dstmax);
+
+   if (dstlen == dstmax)
+   return 0;
+
+   if (dstmax - dstlen < srclen + 1)
+   srclen = dstmax - dstlen - 1;
+   memcpy(dst + dstlen, srcbeg, srclen);
+   dst[dstlen + srclen] = 0;
+
+   return srclen;
 }
 
 static size_t
@@ -213,8 +219,9 @@
s++;
if (*addr || *disp)
break;
+   } else {
+   s++;
}
-   s++;
} else if (*s == '<') {
char tok[1024] = { 0 };
char *c = tok;
@@ -222,7 +229,9 @@
s++;
while (*s && c < e && *s != '>') {
s = skip_comment(s);
-   if (*s == '"') {
+   if (!*s) {
+   break;
+   } else if (*s == '"') {
   

Bug#923739: RM: apache-mod-auth-ntlm-winbind -- RoQA; Orphaned, dead upstream, insecure protocol

[Olly Betts]

BTW, there don't seem to be any rdeps (I checked with dak rm).

Cheers,
Olly

Bug#895632: kdav: autopkgtest fails with new release while succeeded in the past

[Sandro Knauß]

Version: 18.08.3-1

As the build tests are flaky anyways, we disabled the autopkgtest for Buster.

hefee

--
On Freitag, 13. April 2018 19:54:40 CET Paul Gevers wrote:
> Source: kdav
> Version: 17.12.3-1
> Severity: normal
> User: ci-t...@tracker.debian.org
> Usertags: regression
> 
> With the upload of version 17.12.3-1 of kdav, the
> autopkgtest¹ started to fail with the following error:
> 
> Running tests...
> /usr/bin/ctest --force-new-ctest-process -j1
> Test project
> /tmp/autopkgtest-lxc.m0yqmrr9/downtmp/build.7In/src/obj-x86_64-linux-gnu
> Start 1: kdav-davcollection
> 1/5 Test #1: kdav-davcollection ...   Passed0.03 sec
> Start 2: kdav-davitem
> 2/5 Test #2: kdav-davitem .   Passed0.01 sec
> Start 3: kdav-davurl
> 3/5 Test #3: kdav-davurl ..   Passed0.01 sec
> Start 4: kdav-davitemfetchjob
> 4/5 Test #4: kdav-davitemfetchjob .***Failed0.02 sec
> * Start testing of DavItemFetchJobTest *
> Config: Using QtTest library 5.9.2, Qt 5.9.2 (x86_64-little_endian-lp64
> shared (dynamic) release build; by GCC 7.3.0)
> PASS   : DavItemFetchJobTest::initTestCase()
> QWARN  : DavItemFetchJobTest::runSuccessfullTest() kf5.kdbusaddons: Can
> not find 'kdeinit5' executable at
> "/usr/share/pkg-kde-tools/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:
> /usr/games"
> "/tmp/autopkgtest-lxc.m0yqmrr9/downtmp/build.7In/src/obj-x86_64-linux-gnu/b
> in, /usr/lib/qt5/bin"
> QWARN  : DavItemFetchJobTest::runSuccessfullTest() kf5.kio.core: KIO
> Connection server not listening, could not connect
> QWARN  : DavItemFetchJobTest::runSuccessfullTest() kf5.kio.core:
> couldn't create slave: "Can not create socket for launching io-slave for
> protocol 'http'."
> FAIL!  : DavItemFetchJobTest::runSuccessfullTest()
> 'fakeServer.isAllScenarioDone()' returned FALSE. ()
>Loc:
> [/tmp/autopkgtest-lxc.m0yqmrr9/downtmp/build.7In/src/autotests/davitemfetchj
> obtest.cpp(42)] PASS   : DavItemFetchJobTest::cleanupTestCase()
> Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 9ms
> * Finished testing of DavItemFetchJobTest *
> 
> Start 5: kdav-davitemslistjob
> 5/5 Test #5: kdav-davitemslistjob .   Passed0.01 sec
> 
> 80% tests passed, 1 tests failed out of 5
> 
> Total Test time (real) =   0.09 sec
> 
> The following tests FAILED:
> 4 - kdav-davitemfetchjob (Failed)
> Errors while running CTest
> make[3]: *** [Makefile:99: test] Error 8
> 
> 
> Paul
> 
> ¹ https://ci.debian.net/packages/k/kdav/unstable/amd64/



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

Bug#923755: libcsv-java: FTBFS in buster/sid

[Santiago Vila]

Package: src:libcsv-java
Version: 2.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   jh_linkjars -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# Leave empty to avoid a FTBFS
make[1]: Leaving directory '/<>'
   jh_build -i
find src/com -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.csv -d 
debian/_jh_build.csv -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 7
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: src/com/csvreader/CsvReader.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 warning
find src/com -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
/usr/share/doc/default-jdk-doc/api -link 
/usr/share/doc/default-jre-headless/api -classpath :debian/_jh_build.csv -d 
debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp -source 1.7
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
2 errors
make: *** [debian/rules:6: build-indep] Error 123
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

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

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

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

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

Thanks.

Bug#923761: skyview: FTBFS in buster/sid

[Santiago Vila]

Package: src:skyview
Version: 3.4.2+repack-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with javahelper 
   dh_update_autotools_config -i
   dh_autoreconf -i
   jh_linkjars -i
   debian/rules override_jh_build
make[1]: Entering directory '/<>/skyview-3.4.2+repack'
jh_build -mskyview.executive.Imager
find skyview net ij heasarc -name *.java -and -type f -print0 | xargs -s 512000 
-0 /usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/jsamp.jar:/usr/share/java/fits.jar:/usr/share/java/ij.jar:/usr/share/java/commons-io.jar:/usr/share/java/commons-math3.jar:debian/_jh_build.skyview
 -d debian/_jh_build.skyview -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 7
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 warning
find skyview net ij heasarc -name *.java -and -type f -print0 | xargs -s 512000 
-0 /usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
/usr/share/doc/default-jdk-doc/api -link 
/usr/share/doc/default-jre-headless/api -classpath 
/usr/share/java/jsamp.jar:/usr/share/java/fits.jar:/usr/share/java/ij.jar:/usr/share/java/commons-io.jar:/usr/share/java/commons-math3.jar:debian/_jh_build.skyview
 -d debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp 
-source 1.7
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
skyview/geometry/Rotater.java:190: warning - Tag @author cannot be used in 
constructor documentation.  It can only be used in the following types of 
documentation: overview, module, package, class/interface.
skyview/process/imagefinder/Checker.java:305: warning - Parameter "valid" is 
documented more than once.
skyview/process/imagefinder/RectRecurse.java:396: warning - Parameter "valid" 
is documented more than once.
skyview/util/Utilities.java:16: warning - Parameter "cy1" is documented more 
than once.
2 errors
4 warnings
make[1]: *** [debian/rules:10: override_jh_build] Error 123
make[1]: Leaving directory '/<>/skyview-3.4.2+repack'
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

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

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

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

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

Thanks.

Bug#923754: jesd: FTBFS in buster/sid

[Santiago Vila]

Package: src:jesd
Version: 0.0.7-4
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
test -x debian/rules
mkdir -p "."
rm -f com/jcraft/jesd/vorbis/Sample.java
rm -f com/jcraft/jesd/vorbis/StreamPlayer.java
jh_linkjars
jh_build -J  esd.jar com
find com -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/jorbis.jar:/usr/share/java/jogg.jar:debian/_jh_build.esd -d 
debian/_jh_build.esd -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 7
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 warning
find com -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
/usr/share/doc/default-jdk-doc/api -link 
/usr/share/doc/default-jre-headless/api -classpath 
/usr/share/java/jorbis.jar:/usr/share/java/jogg.jar:debian/_jh_build.esd -d 
debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp -source 1.7
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
2 errors
make: *** [/usr/share/cdbs/1/class/javahelper.mk:37: debian/jh_build_stamp] 
Error 123
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

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

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

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

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

Thanks.

Bug#923748: colorpicker: FTBFS in buster/sid

[Santiago Vila]

Package: src:colorpicker
Version: 1.0.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   jh_linkjars -i
   debian/rules override_jh_build
make[1]: Entering directory '/<>'
jh_build --javacopts="-source 1.8 -target 1.8" --javadoc-opts="-source 1.8"
find com -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.ColorPicker -d 
debian/_jh_build.ColorPicker -encoding ISO8859-1 -source 1.8 -target 1.8
warning: [options] bootstrap class path not set in conjunction with -source 8
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 warning
find com -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
/usr/share/doc/default-jdk-doc/api -link 
/usr/share/doc/default-jre-headless/api -classpath 
:debian/_jh_build.ColorPicker -d debian/_jh_build.javadoc/api -quiet -encoding 
ISO8859-1 -notimestamp -source 1.8
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
com/bric/swing/DialogFooter.java:58: warning - Tag @link: reference not found: 
com.bric.swing.QDialog
com/bric/swing/DialogFooter.java:102: warning - Tag @link: reference not found: 
com.bric.swing.JLink
com/bric/util/JVM.java:40: warning - invalid usage of tag &
com/bric/util/JVM.java:33: warning - invalid usage of tag &
com/bric/util/JVM.java:33: warning - invalid usage of tag &
com/bric/util/JVM.java:40: warning - invalid usage of tag &
com/bric/util/JVM.java:40: warning - invalid usage of tag &
com/bric/util/JVM.java:33: warning - invalid usage of tag &
2 errors
8 warnings
make[1]: *** [debian/rules:18: override_jh_build] Error 123
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

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

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

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

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

Thanks.

Bug#923757: libirclib-java: FTBFS in buster/sid

[Santiago Vila]

Package: src:libirclib-java
Version: 1.10-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh --with javahelper build-indep
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i
   jh_linkjars -i
   jh_build -i
find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.irclib -d 
debian/_jh_build.irclib -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 7
src/org/schwering/irc/lib/ssl/SSLSocketFactoryFactory.java:147: warning: 
non-varargs call of varargs method with inexact argument type for last 
parameter;
Method getSocketFactoryMethod = 
contextClass.getMethod("getSocketFactory", null);

   ^
  cast to Class for a varargs call
  cast to Class[] for a non-varargs call and to suppress this warning
src/org/schwering/irc/lib/ssl/SSLSocketFactoryFactory.java:155: warning: 
non-varargs call of varargs method with inexact argument type for last 
parameter;
Object socketFactory = getSocketFactoryMethod.invoke(context, 
null);
  ^
  cast to Object for a varargs call
  cast to Object[] for a non-varargs call and to suppress this warning
src/org/schwering/irc/lib/ssl/SSLSocketFactoryFactory.java:209: warning: 
non-varargs call of varargs method with inexact argument type for last 
parameter;
Method getSocketFactoryMethod = 
contextClass.getMethod("getSocketFactory", null);

   ^
  cast to Class for a varargs call
  cast to Class[] for a non-varargs call and to suppress this warning
src/org/schwering/irc/lib/ssl/SSLSocketFactoryFactory.java:217: warning: 
non-varargs call of varargs method with inexact argument type for last 
parameter;
Object socketFactory = getSocketFactoryMethod.invoke(context, 
null);
  ^
  cast to Object for a varargs call
  cast to Object[] for a non-varargs call and to suppress this warning
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
5 warnings
find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
/usr/share/doc/default-jdk-doc/api -link 
/usr/share/doc/default-jre-headless/api -classpath :debian/_jh_build.irclib -d 
debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp -source 1.7
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
src/org/schwering/irc/lib/IRCConstants.java:854: warning - invalid usage of tag 
&
src/org/schwering/irc/lib/IRCConstants.java:854: warning - invalid usage of tag 
&
src/org/schwering/irc/lib/IRCConstants.java:854: warning - invalid usage of tag 
&
2 errors
3 warnings
make: *** [debian/rules:9: build-indep] Error 123
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

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

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

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

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

Thanks.

Bug#923749: fannj: FTBFS in buster/sid

[Santiago Vila]

Package: src:fannj
Version: 0.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh --with javahelper build-indep
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i
   jh_linkjars -i
   debian/rules override_jh_build
make[1]: Entering directory '/<>'
jh_build --javadoc-opts='-link /usr/share/doc/default-jdk-doc/api'
find src/main -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/jna.jar:/usr/share/java/junit.jar:debian/_jh_build.fannj -d 
debian/_jh_build.fannj -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 7
1 warning
find src/main -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
/usr/share/doc/default-jdk-doc/api -link 
/usr/share/doc/default-jre-headless/api -classpath 
/usr/share/java/jna.jar:/usr/share/java/junit.jar:debian/_jh_build.fannj -d 
debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp -source 
1.7 -link /usr/share/doc/default-jdk-doc/api
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
src/main/java/com/googlecode/fannj/Layer.java:33: warning - Tag @link: 
reference not found: Neuron.DEFAULT_ACTIVATION_FUNCTION
src/main/java/com/googlecode/fannj/Layer.java:34: warning - Tag @link: 
reference not found: Neuron.DEFAULT_ACTIVATION_STEEPNESS
src/main/java/com/googlecode/fannj/Layer.java:47: warning - Tag @link: 
reference not found: Neuron.DEFAULT_ACTIVATION_STEEPNESS
src/main/java/com/googlecode/fannj/Layer.java:33: warning - Tag @link: 
reference not found: Neuron.DEFAULT_ACTIVATION_FUNCTION
src/main/java/com/googlecode/fannj/Layer.java:34: warning - Tag @link: 
reference not found: Neuron.DEFAULT_ACTIVATION_STEEPNESS
src/main/java/com/googlecode/fannj/Layer.java:47: warning - Tag @link: 
reference not found: Neuron.DEFAULT_ACTIVATION_STEEPNESS
src/main/java/com/googlecode/fannj/Layer.java:33: warning - Tag @link: 
reference not found: Neuron.DEFAULT_ACTIVATION_FUNCTION
src/main/java/com/googlecode/fannj/Layer.java:34: warning - Tag @link: 
reference not found: Neuron.DEFAULT_ACTIVATION_STEEPNESS
src/main/java/com/googlecode/fannj/Layer.java:47: warning - Tag @link: 
reference not found: Neuron.DEFAULT_ACTIVATION_STEEPNESS
3 errors
9 warnings
make[1]: *** [debian/rules:13: override_jh_build] Error 123
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

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

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

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

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

Thanks.

Bug#923759: mtj: FTBFS in buster/sid

[Santiago Vila]

Package: src:mtj
Version: 0.9.14+dfsg-5
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   jh_linkjars -i
   dh_auto_build -i
ant -Duser.name debian
Buildfile: /<>/mtj-0.9.14+dfsg/build.xml

-pre-init:

-init-private:

-pre-init-libraries:

-init-private-libraries:

-init-libraries:

-init-user:

-init-project:

-init-macrodef-property:

-do-init:

-post-init:

-init-check:

-init-ap-cmdline-properties:

-init-macrodef-javac-with-processors:

-init-macrodef-javac-without-processors:

-init-macrodef-javac:

-init-macrodef-junit:

-init-debug-args:

-init-macrodef-nbjpda:

-init-macrodef-debug:

-init-macrodef-java:

-init-presetdef-jar:

-init-ap-cmdline-supported:

-init-ap-cmdline:

init:

-deps-jar-init:

deps-jar:
[mkdir] Created dir: /<>/mtj-0.9.14+dfsg/build

-warn-already-built-jar:
[propertyfile] Updating property file: 
/<>/mtj-0.9.14+dfsg/build/built-jar.properties

-check-automatic-build:

-clean-after-automatic-build:

-verify-automatic-build:

-pre-pre-compile:
[mkdir] Created dir: /<>/mtj-0.9.14+dfsg/build/classes

-pre-compile:

-copy-persistence-xml:

-compile-depend:

-do-compile:
[mkdir] Created dir: /<>/mtj-0.9.14+dfsg/build/empty
[mkdir] Created dir: 
/<>/mtj-0.9.14+dfsg/build/generated-sources/ap-source-output
[javac] Compiling 129 source files to 
/<>/mtj-0.9.14+dfsg/build/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractSymmBandMatrix.java:25:
 error: package org.netlib.blas does not exist
[javac] import org.netlib.blas.BLAS;
[javac]   ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractSymmBandMatrix.java:26:
 error: package org.netlib.lapack does not exist
[javac] import org.netlib.lapack.LAPACK;
[javac] ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractSymmDenseMatrix.java:23:
 error: package org.netlib.blas does not exist
[javac] import org.netlib.blas.BLAS;
[javac]   ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractSymmDenseMatrix.java:24:
 error: package org.netlib.lapack does not exist
[javac] import org.netlib.lapack.LAPACK;
[javac] ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractSymmPackMatrix.java:23:
 error: package org.netlib.blas does not exist
[javac] import org.netlib.blas.BLAS;
[javac]   ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractSymmPackMatrix.java:24:
 error: package org.netlib.lapack does not exist
[javac] import org.netlib.lapack.LAPACK;
[javac] ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractTriangBandMatrix.java:23:
 error: package org.netlib.blas does not exist
[javac] import org.netlib.blas.BLAS;
[javac]   ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractTriangBandMatrix.java:24:
 error: package org.netlib.lapack does not exist
[javac] import org.netlib.lapack.LAPACK;
[javac] ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractTriangDenseMatrix.java:25:
 error: package org.netlib.blas does not exist
[javac] import org.netlib.blas.BLAS;
[javac]   ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractTriangDenseMatrix.java:26:
 error: package org.netlib.lapack does not exist
[javac] import org.netlib.lapack.LAPACK;
[javac] ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractTriangPackMatrix.java:25:
 error: package org.netlib.blas does not exist
[javac] import org.netlib.blas.BLAS;
[javac]   ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractTriangPackMatrix.java:26:
 error: package org.netlib.lapack does not exist
[javac] import org.netlib.lapack.LAPACK;
[javac] ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/BandCholesky.java:25: 
error: package org.netlib.lapack does not exist
[javac] import org.netlib.lapack.LAPACK;
[javac] ^
[javac] 
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/DenseMatrix.java:29: 
error: package org.netlib.blas does not exist
[javac] import 

Bug#923756: libhac-java: FTBFS in buster/sid

[Santiago Vila]

Package: src:libhac-java
Version: 0.20110510-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   jh_linkjars -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
jh_build -J hac.jar src
find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.hac -d 
debian/_jh_build.hac -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 7
1 warning
find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
/usr/share/doc/default-jdk-doc/api -link 
/usr/share/doc/default-jre-headless/api -classpath :debian/_jh_build.hac -d 
debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp -source 1.7
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
2 errors
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 123
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

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

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

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

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

Thanks.

Bug#923758: libnanoxml2-java: FTBFS in buster/sid

[Santiago Vila]

Package: src:libnanoxml2-java
Version: 2.2.3.dfsg-6
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   jh_linkjars -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
jh_build -o'-source 1.8 -nowarn' -N nanoxml-lite.jar Sources/Lite/
find Sources/Lite/ -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.nanoxml-lite -d 
debian/_jh_build.nanoxml-lite -encoding ISO8859-1 -source 1.8 -nowarn
Note: Sources/Lite/nanoxml/XMLElement.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
/usr/lib/jvm/default-java/bin/jar cfm /<>/nanoxml-lite.jar 
../_jh_manifest.nanoxml-lite nanoxml
jh_build -o'-source 1.8 -nowarn' -N nanoxml.jar Sources/Java/
find Sources/Java/ -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.nanoxml -d 
debian/_jh_build.nanoxml -encoding ISO8859-1 -source 1.8 -nowarn
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
/usr/lib/jvm/default-java/bin/jar cfm /<>/nanoxml.jar 
../_jh_manifest.nanoxml net
CLASSPATH=nanoxml.jar jh_build -o'-source 1.8 -nowarn' -N nanoxml-sax.jar 
Sources/SAX/
find Sources/SAX/ -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp 
nanoxml.jar:debian/_jh_build.nanoxml-sax -d debian/_jh_build.nanoxml-sax 
-encoding ISO8859-1 -source 1.8 -nowarn
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
/usr/lib/jvm/default-java/bin/jar cfm /<>/nanoxml-sax.jar 
../_jh_manifest.nanoxml-sax net
jh_manifest -c /usr/share/java/nanoxml.jar nanoxml-sax.jar
bnd wrap --output nanoxml.jar.tmp nanoxml.jar
-
Warnings
000: Using defaults for wrap, which means no export versions
bnd wrap --output nanoxml-lite.jar.tmp nanoxml-lite.jar
-
Warnings
000: Using defaults for wrap, which means no export versions
bnd wrap --output nanoxml-sax.jar.tmp nanoxml-sax.jar
-
Warnings
000: Using defaults for wrap, which means no export versions
mv nanoxml.jar.tmp nanoxml.jar
mv nanoxml-lite.jar.tmp nanoxml-lite.jar
mv nanoxml-sax.jar.tmp nanoxml-sax.jar
/usr/lib/jvm/default-java/bin/javadoc -author -link 
/usr/share/doc/default-jdk-doc/api -quiet \
-sourcepath Sources/Java/:Sources/Lite/:Sources/SAX/ -source 1.8 \
nanoxml net.n3.nanoxml net.n3.nanoxml.sax -d api
Creating destination directory: "api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
Sources/Lite/nanoxml/XMLElement.java:263: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:264: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:265: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:266: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:267: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:268: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:269: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:298: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:299: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:300: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:301: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:302: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:303: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:304: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:329: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:330: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:331: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:332: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:333: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:334: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:335: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:367: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:368: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:369: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:370: warning - invalid usage of tag >
Sources/Lite/nanoxml/XMLElement.java:371: warning 

Bug#923760: png-sixlegs: FTBFS in buster/sid

[Santiago Vila]

Package: src:png-sixlegs
Version: 2.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --sourcedirectory=javapng-2.0 --with javahelper
   dh_update_autotools_config -i -O--sourcedirectory=javapng-2.0
   dh_autoreconf -i -O--sourcedirectory=javapng-2.0
   dh_auto_configure -i -O--sourcedirectory=javapng-2.0
   jh_linkjars -i -O--sourcedirectory=javapng-2.0
   dh_auto_build -i -O--sourcedirectory=javapng-2.0
cd javapng-2.0 && ant -Duser.name debian
Buildfile: /<>/javapng-2.0/build.xml

init:

compile:
[mkdir] Created dir: /<>/javapng-2.0/build/main
 [copy] Copied 3 empty directories to 3 empty directories under 
/<>/javapng-2.0/build/main
[javac] /<>/javapng-2.0/build.xml:107: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.2 is no longer supported, switching to 6
[javac] Using javac -target 1.2 is no longer supported, switching to 6
[javac] Compiling 26 source files to /<>/javapng-2.0/build/main
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 4 warnings
[mkdir] Created dir: /<>/javapng-2.0/build/apng
 [copy] Copied 3 empty directories to 3 empty directories under 
/<>/javapng-2.0/build/apng
[javac] /<>/javapng-2.0/build.xml:107: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.2 is no longer supported, switching to 6
[javac] Using javac -target 1.2 is no longer supported, switching to 6
[javac] Compiling 5 source files to /<>/javapng-2.0/build/apng
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 4 warnings

compile-iio:
[mkdir] Created dir: /<>/javapng-2.0/build/iio
 [copy] Copied 4 empty directories to 4 empty directories under 
/<>/javapng-2.0/build/iio
[javac] /<>/javapng-2.0/build.xml:107: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 6
[javac] Using javac -target 1.4 is no longer supported, switching to 6
[javac] Compiling 5 source files to /<>/javapng-2.0/build/iio
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] Note: 
/<>/javapng-2.0/src/iio/com/sixlegs/png/iio/PngImageReader.java 
uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 4 warnings

compile-examples:
[mkdir] Created dir: /<>/javapng-2.0/build/examples
 [copy] Copied 4 empty directories to 4 empty directories under 
/<>/javapng-2.0/build/examples
[javac] /<>/javapng-2.0/build.xml:107: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 6
[javac] Using javac -target 1.5 is no longer supported, switching to 6
[javac] Compiling 7 source files to 
/<>/javapng-2.0/build/examples
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release

Bug#923751: gentlyweb-utils: FTBFS in buster/sid

[Santiago Vila]

Package: src:gentlyweb-utils
Version: 1.5-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with javahelper --with maven_repo_helper
   dh_update_autotools_config -i
   dh_autoreconf -i
   jh_linkjars -i
   jh_build -i
find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/jdom1.jar:/usr/share/java/javax.activation.jar:debian/_jh_build.gentlyweb-utils
 -d debian/_jh_build.gentlyweb-utils -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 7
src/utils/com/gentlyweb/utils/Getter.java:384: warning: non-varargs call of 
varargs method with inexact argument type for last parameter;
 null);
 ^
  cast to Class for a varargs call
  cast to Class[] for a non-varargs call and to suppress this warning
src/utils/com/gentlyweb/utils/Getter.java:413: warning: non-varargs call of 
varargs method with inexact argument type for last parameter;
 null);
 ^
  cast to Class for a varargs call
  cast to Class[] for a non-varargs call and to suppress this warning
src/utils/com/gentlyweb/utils/Getter.java:432: warning: non-varargs call of 
varargs method with inexact argument type for last parameter;
null);
^
  cast to Class for a varargs call
  cast to Class[] for a non-varargs call and to suppress this warning
Note: src/utils/com/gentlyweb/utils/GeneralFilter.java uses or overrides a 
deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
4 warnings
find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
/usr/share/doc/default-jdk-doc/api -link 
/usr/share/doc/default-jre-headless/api -classpath 
/usr/share/java/jdom1.jar:/usr/share/java/javax.activation.jar:debian/_jh_build.gentlyweb-utils
 -d debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp 
-source 1.7
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
src/utils/com/gentlyweb/utils/Accessor.java:322: warning - @param argument 
"field" is not a parameter name.
src/utils/com/gentlyweb/utils/GeneralComparator.java:161: warning - invalid 
usage of tag {@
src/utils/com/gentlyweb/utils/GeneralComparator.java:208: warning - Tag @link: 
reference not found: ConfigList
src/utils/com/gentlyweb/utils/GeneralComparator.java:208: warning - Tag @link: 
reference not found: ConfigMap
src/utils/com/gentlyweb/utils/GeneralComparator.java:214: warning - Tag @link: 
reference not found: #getAsJDOMElement()
src/utils/com/gentlyweb/utils/GeneralComparator.java:215: warning - Tag @link: 
reference not found: #GeneralComparator(Element)
src/utils/com/gentlyweb/utils/GeneralComparator.java:218: warning - invalid 
usage of tag 

Bug#923750: gdcm: FTBFS in buster/sid

[Santiago Vila]

Package: src:gdcm
Version: 2.8.8-6
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep --with cli --with python3 --with javahelper  
--buildsystem=cmake+ninja
   dh_update_autotools_config -i -O--buildsystem=cmake\+ninja
   dh_autoreconf -i -O--buildsystem=cmake\+ninja
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_SKIP_RPATH=ON -DCMAKE_BUILD_TYPE:STRING=None 
-DGDCM_DOXYGEN_NO_FOOTER:BOOL=ON -DGDCM_BUILD_APPLICATIONS:BOOL=ON 
-DGDCM_DOCUMENTATION:BOOL=ON -DGDCM_VTK_DOCUMENTATION:BOOL=ON 
-DDOCUMENTATION_DOWNLOAD_VTK_TAGFILE:BOOL=OFF -DGDCM_PDF_DOCUMENTATION:BOOL=ON 
-DGDCM_BUILD_SHARED_LIBS:BOOL=ON -DGDCM_WRAP_PYTHON:BOOL=ON 
-DGDCM_WRAP_CSHARP:BOOL=0 -DGDCM_WRAP_JAVA:BOOL=ON 
-DGDCM_DEFAULT_JAVA_VERSION:STRING=1.8 -DGDCM_WRAP_PHP:BOOL=OFF 
-DGDCM_USE_PVRG:BOOL=ON -DGDCM_USE_SYSTEM_PVRG:BOOL=ON 
-DGMCS_EXECUTABLE:FILEPATH=/usr/bin/mono-csc -DGDCM_BUILD_TESTING:BOOL=OFF 
-DGDCM_USE_SYSTEM_EXPAT:BOOL=ON -DGDCM_USE_SYSTEM_UUID:BOOL=ON 
-DGDCM_USE_SYSTEM_ZLIB:BOOL=ON -DGDCM_USE_SYSTEM_OPENJPEG:BOOL=ON 
-DGDCM_USE_SYSTEM_OPENSSL:BOOL=ON -DGDCM_USE_SYSTEM_CHARLS:BOOL=ON 
-DGDCM_USE_SYSTEM_POPPLER:BOOL=ON -DGDCM_USE_SYSTEM_LIBXML2:BOOL=ON 
-DGDCM_USE_SYSTEM_JSON:BOOL=ON -DGDCM_USE_PARAVIEW:BOOL=OFF 
-DGDCM_USE_ACTIVIZ:BOOL=OFF -DGDCM_USE_SYSTEM_PAPYRUS3:BOOL=ON 
-DGDCM_USE_SYSTEM_SOCKET
 XX:BOOL=ON -DPython_ADDITIONAL_VERSIONS:STRING=3.7 
-DGDCM_INSTALL_DOC_DIR:STRING=share/doc/gdcm-doc 
-DTAGFILES:STRING="/usr/share/doc/vtk-doc/html/vtk7.1.tag=/usr/share/doc/vtk-doc/html/"
 -DGDCM_INSTALL_PYTHONMODULE_DIR:STRING=lib/python/dist-packages 
-DGDCM_INSTALL_JAVAMODULE_DIR:STRING=lib/x86_64-linux-gnu/jni 
-DGDCM_NO_PYTHON_LIBS_LINKING:BOOL=ON -DGDCM_NO_VTKJAVA_LIBS_LINKING:BOOL=ON 
-DGDCM_INSTALL_LIB_DIR:STRING=lib/x86_64-linux-gnu -DGDCM_USE_VTK:BOOL=ON 
-DVTK_JAVA_JAR=/usr/share/java/vtk7.jar
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
-GNinja -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DCMAKE_SKIP_RPATH=ON -DCMAKE_BUILD_TYPE:STRING=None 
-DGDCM_DOXYGEN_NO_FOOTER:BOOL=ON -DGDCM_BUILD_APPLICATIONS:BOOL=ON 
-DGDCM_DOCUMENTATION:BOOL=ON -DGDCM_VTK_DOCUMENTATION:BOOL=ON 
-DDOCUMENTATION_DOWNLOAD_VTK_TAGFILE:BOOL=OFF -DGDCM_PDF_DOCUMENTATION:BOOL=ON 
-DGDCM_BUILD_SHARED_LIBS:BOOL=ON -DGDCM_WRAP_PYTHON:BOOL=ON 
-DGDCM_WRAP_CSHARP:BOOL=0 -DGDCM_WRAP_JAVA:BOOL=ON 
-DGDCM_DEFAULT_JAVA_VERSION:STRING=1.8 -DGDCM_WRAP_PHP:BOOL=OFF 
-DGDCM_USE_PVRG:BOOL=ON -DGDCM_USE_SYSTEM_PVRG:BOOL=ON 
-DGMCS_EXECUTABLE:FILEPATH=/usr/bin/mono-csc -DGDCM_BUILD_TESTING:BOOL=OFF 
-DGDCM_USE_SYSTEM_EXPAT:BOOL=ON -DGDCM_USE_SYSTEM_UUID:BOOL=ON 
-DGDCM_USE_SYSTEM_ZLI
 B:BOOL=ON -DGDCM_USE_SYSTEM_OPENJPEG:BOOL=ON -DGDCM_USE_SYSTEM_OPENSSL:BOOL=ON 
-DGDCM_USE_SYSTEM_CHARLS:BOOL=ON -DGDCM_USE_SYSTEM_POPPLER:BOOL=ON 
-DGDCM_USE_SYSTEM_LIBXML2:BOOL=ON -DGDCM_USE_SYSTEM_JSON:BOOL=ON 
-DGDCM_USE_PARAVIEW:BOOL=OFF -DGDCM_USE_ACTIVIZ:BOOL=OFF 
-DGDCM_USE_SYSTEM_PAPYRUS3:BOOL=ON -DGDCM_USE_SYSTEM_SOCKETXX:BOOL=ON 
-DPython_ADDITIONAL_VERSIONS:STRING=3.7 
-DGDCM_INSTALL_DOC_DIR:STRING=share/doc/gdcm-doc 
-DTAGFILES:STRING=/usr/share/doc/vtk-doc/html/vtk7.1.tag=/usr/share/doc/vtk-doc/html/
 -DGDCM_INSTALL_PYTHONMODULE_DIR:STRING=lib/python/dist-packages 
-DGDCM_INSTALL_JAVAMODULE_DIR:STRING=lib/x86_64-linux-gnu/jni 
-DGDCM_NO_PYTHON_LIBS_LINKING:BOOL=ON -DGDCM_NO_VTKJAVA_LIBS_LINKING:BOOL=ON 
-DGDCM_INSTALL_LIB_DIR:STRING=lib/x86_64-linux-gnu -DGDCM_USE_VTK:BOOL=ON 
-DVTK_JAVA_JAR=/usr/share/java/vtk7.jar ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for inttypes.h
-- Looking for inttypes.h - found
-- Found POPPLER: /usr/lib/x86_64-linux-gnu/libpoppler.so
-- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.4") 
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") 
-- Checking for module 'libopenjp2'
--   Found libopenjp2, version 2.3.0
-- Found OpenJPEG: openjp2 (found suitable version "2.3.0", minimum required is 
"2.0.0") 

Bug#923752: healpix-java: FTBFS in buster/sid

[Santiago Vila]

Package: src:healpix-java
Version: 3.40-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   jh_linkjars -i
   debian/rules override_jh_build
make[1]: Entering directory '/<>'
jh_build
/usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/fits.jar:debian/_jh_build.healpix -d debian/_jh_build.healpix 
-source 1.7 -target 1.7 -encoding ISO8859-1 
src/healpix/essentials/CircleFinder.java src/healpix/essentials/Compressor.java 
src/healpix/essentials/Constants.java src/healpix/essentials/FastMath.java 
src/healpix/essentials/FitsUtil.java src/healpix/essentials/Fxyf.java 
src/healpix/essentials/HealpixBase.java 
src/healpix/essentials/HealpixMapDouble.java 
src/healpix/essentials/HealpixMapFloat.java 
src/healpix/essentials/HealpixProc.java 
src/healpix/essentials/HealpixTables.java 
src/healpix/essentials/HealpixUtils.java src/healpix/essentials/Hploc.java 
src/healpix/essentials/Moc.java src/healpix/essentials/MocFitsIO.java 
src/healpix/essentials/MocQuery.java src/healpix/essentials/MocStringIO.java 
src/healpix/essentials/Pointing.java src/healpix/essentials/RangeSet.java 
src/healpix/essentials/Scheme.java src/healpix/essentials/Vec3.java 
src/healpix/essentials/Zphi.java 
 src/healpix/essentials/package-info.java
warning: [options] bootstrap class path not set in conjunction with -source 7
1 warning
/usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
/usr/share/doc/default-jdk-doc/api -link 
/usr/share/doc/default-jre-headless/api -classpath 
/usr/share/java/fits.jar:debian/_jh_build.healpix -d 
debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp -source 
1.7 src/healpix/essentials/CircleFinder.java 
src/healpix/essentials/Compressor.java src/healpix/essentials/Constants.java 
src/healpix/essentials/FastMath.java src/healpix/essentials/FitsUtil.java 
src/healpix/essentials/Fxyf.java src/healpix/essentials/HealpixBase.java 
src/healpix/essentials/HealpixMapDouble.java 
src/healpix/essentials/HealpixMapFloat.java 
src/healpix/essentials/HealpixProc.java 
src/healpix/essentials/HealpixTables.java 
src/healpix/essentials/HealpixUtils.java src/healpix/essentials/Hploc.java 
src/healpix/essentials/Moc.java src/healpix/essentials/MocFitsIO.java 
src/healpix/essentials/MocQuery.java src/healpix/essentials/MocStringIO.java 
src/healpix/essentials/Pointing.java src/healpix/essenti
 als/RangeSet.java src/healpix/essentials/Scheme.java 
src/healpix/essentials/Vec3.java src/healpix/essentials/Zphi.java 
src/healpix/essentials/package-info.java
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
2 errors
make[1]: *** [debian/rules:10: override_jh_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

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

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

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

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

Thanks.

Bug#923753: jcm: FTBFS in buster/sid

[Santiago Vila]

Package: src:jcm
Version: 1.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with javahelper
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
rm Makefile
dh_auto_configure
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
make[1]: Leaving directory '/<>'
   jh_linkjars -i
   jh_build -i
find edu -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.jcm -d 
debian/_jh_build.jcm -source 1.7 -target 1.7 -encoding ISO8859-1 
AnimatedGraph.java Derivatives.java EpsilonDelta.java Evaluator.java 
FamiliesOfGraphs.java FunctionComposition.java GenericGraphApplet.java 
IntegralCurves.java MultiGraph.java Parametric.java RiemannSums.java 
ScatterPlotApplet.java SecantTangent.java SimpleGraph.java
warning: [options] bootstrap class path not set in conjunction with -source 7
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 warning
find edu -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
/usr/share/doc/default-jdk-doc/api -link 
/usr/share/doc/default-jre-headless/api -classpath :debian/_jh_build.jcm -d 
debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp -source 
1.7 AnimatedGraph.java Derivatives.java EpsilonDelta.java Evaluator.java 
FamiliesOfGraphs.java FunctionComposition.java GenericGraphApplet.java 
IntegralCurves.java MultiGraph.java Parametric.java RiemannSums.java 
ScatterPlotApplet.java SecantTangent.java SimpleGraph.java
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
GenericGraphApplet.java:557: warning - @param argument "defaultValue" is not a 
parameter name.
edu/hws/jcm/awt/Limits.java:56: warning - @param argument "A" is not a 
parameter name.
edu/hws/jcm/awt/VariableSlider.java:168: warning - invalid usage of tag <
edu/hws/jcm/data/ConditionalExpression.java:38: warning - invalid usage of tag >
edu/hws/jcm/data/ConditionalExpression.java:39: warning - invalid usage of tag <
edu/hws/jcm/data/ConditionalExpression.java:39: warning - invalid usage of tag >
edu/hws/jcm/data/ExpressionProgram.java:45: warning - invalid usage of tag <
edu/hws/jcm/data/ExpressionProgram.java:45: warning - invalid usage of tag <
edu/hws/jcm/data/ExpressionProgram.java:48: warning - invalid usage of tag >
edu/hws/jcm/data/ExpressionProgram.java:236: warning - invalid usage of tag <
edu/hws/jcm/data/ExpressionProgram.java:236: warning - invalid usage of tag <
edu/hws/jcm/data/Parser.java:99: warning - invalid usage of tag &
edu/hws/jcm/data/Parser.java:99: warning - invalid usage of tag <
edu/hws/jcm/data/Parser.java:99: warning - invalid usage of tag >
edu/hws/jcm/data/Parser.java:99: warning - invalid usage of tag <
edu/hws/jcm/data/Parser.java:99: warning - invalid usage of tag >
edu/hws/jcm/data/Parser.java:99: warning - invalid usage of tag <
edu/hws/jcm/data/Parser.java:99: warning - invalid usage of tag >
edu/hws/jcm/data/Parser.java:101: warning - invalid usage of tag &
edu/hws/jcm/data/Parser.java:267: warning - invalid usage of tag >
edu/hws/jcm/data/ParserContext.java:76: warning - invalid usage of tag <
edu/hws/jcm/data/ParserContext.java:76: warning - invalid usage of tag >
edu/hws/jcm/data/ParserContext.java:76: warning - invalid usage of tag <
edu/hws/jcm/data/ParserContext.java:76: warning - invalid usage of tag <
edu/hws/jcm/data/ParserContext.java:80: warning - invalid usage of tag &
edu/hws/jcm/data/ParserContext.java:80: warning - invalid usage of tag &
edu/hws/jcm/data/StackOfDouble.java:54: warning - invalid usage of tag <
edu/hws/jcm/draw/Axes.java:58: warning - @param argument "xlabel" is not a 
parameter name.
edu/hws/jcm/draw/Axes.java:59: warning - @param argument "ylabel" is not a 
parameter name.
edu/hws/jcm/draw/CoordinateRect.java:44: warning - invalid usage of tag <
edu/hws/jcm/draw/CoordinateRect.java:44: warning - invalid usage of tag <
edu/hws/jcm/draw/LimitControlPanel.java:212: warning - Parameter "xmaxName" is 
documented more than once.
edu/hws/jcm/draw/Panner.java:83: warning - @param argument "modifiers" is not a 
parameter name.
edu/hws/jcm/draw/ParametricCurve.java:102: warning 

Bug#910731: kaddressbook: crashes at startup

[Sandro Knauß]

Hey,

okay the initial issue is solved, that is great.

Btw. please use the bugnumber-qu...@bugs.debian.org rarely, because than 
maintainers like me don't gets any mails, that's why I missed your 
conversation.

> > I suppose this means that kaddressbook should depend on akonadi-server.

thanls for spotting this, I'll fix that soon. Often people use complete kdepim 
that's why these inter kdepim dependencies are sometimes not complete.

hefee



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

Bug#922659: Workaround

[Peter.Chubb]

I rebuilt emacs without the in-built GNUTLS --- and everything now
works properly.

I added the line:
confflags += --without-gnutls
to debian/rules and rebuilt.

Peter C
-- 
Dr Peter Chubb Tel: +61 2 9490 5852  http://ts.data61.csiro.au/
Trustworthy Systems Group Data61, CSIRO (formerly NICTA)

Bug#923741: new upstream release

[Jason Pleau]

Hi

On 2019-03-04 4:53 p.m., Antoine Beaupre wrote:
> Package: rofi
> Version: 1.5.1-1
> Severity: wishlist
> 
> A new release (1.5.2) of rofi was published:
> 
> https://github.com/DaveDavenport/rofi/releases/tag/1.5.2
> 
> I've tried to upgrade this myself but there's weird stuff going on, as
> "git diff 1.5.0..upstream/1.5.0" differs, yet there's no +dfsg tag or
> a clear way to reproduce the orig tarball from the git repo.
> 

I don't use the github-generated tarballs, they are missing certain
files (an active contributor to rofi has different projects that aren't
meant to be distributed separately, but are included in rofi. Those are
pulled in when they run 'make dist' iirc)


I used gbp import-orig --upstream-vcs-tag=1.5.1 rofi-1.5.1.tar.gz (file
taken from
https://github.com/DaveDavenport/rofi/releases/download/1.5.2/rofi-1.5.1.tar.gz,
different than the github tag tarball).

Hope that helps. Thanks for looking into the update, I've been busy with
other stuff for a little while now =/


> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), 
> LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages rofi depends on:
> ii  libc6 2.28-7
> ii  libcairo2 1.16.0-2
> ii  libglib2.0-0  2.58.3-1
> ii  libpango-1.0-01.42.4-6
> ii  libpangocairo-1.0-0   1.42.4-6
> ii  librsvg2-22.44.10-1
> ii  libstartup-notification0  0.12-6
> ii  libxcb-ewmh2  0.4.1-1.1
> ii  libxcb-icccm4 0.4.1-1.1
> ii  libxcb-randr0 1.13.1-2
> ii  libxcb-util0  0.3.8-3+b2
> ii  libxcb-xinerama0  1.13.1-2
> ii  libxcb-xkb1   1.13.1-2
> ii  libxcb-xrm0   1.0-3
> ii  libxcb1   1.13.1-2
> ii  libxkbcommon-x11-00.8.2-1
> ii  libxkbcommon0 0.8.2-1
> 
> rofi recommends no packages.
> 
> rofi suggests no packages.
> 
> -- no debconf information
> 

-- 
Jason Pleau

Bug#923295: src:jruby-joni: tests fail with invalid character property name

[Santiago Vila]

severity 923295 serious
thanks

On Mon, 25 Feb 2019, Andrej Shadura wrote:

> As you already know, jruby-joni fails build-time tests in the current
> unstable:

The tests are part of the build as a whole, making the build as a
whole to fail as well, so this is really a FTBFS bug.

The package currently FTBFS in both buster and sid:

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

> This bug has already been reported upstream, but I though it would be
> good to track it in Debian too.

I would even say that it's more than good: it is necessary, because
packages in buster must build in buster.

Thanks.

Bug#923747: linux-image-amd64: Request to enable CONFIG_USER_NS=y in kernel config

[Nikolas Nyby]

Package: linux-image-amd64
Version: 4.19+102
Severity: normal

Dear Maintainer,

   * What led up to the situation?

When I start Brave browser (https://brave.com) in Debian buster/testing,
I get an error that my kernel isn't configured correctly:

$ brave-browser 
[8918:8918:0304/181514.182194:FATAL:zygote_host_impl_linux.cc(116)] No 
usable sandbox! Update your kernel or see 
https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md
 for more information on developing with the SUID sandbox. If you want to live 
dangerously and need an immediate workaround, you can try using --no-sandbox.
Trace/breakpoint trap

This is resolved by adding CONFIG_USER_NS=y to the kernel configuration.


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

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

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.19.0-2-amd64  4.19.16-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

Bug#893879: Inspect graph broken

[Alex]

The reason for this is that rrdtool changed its behavior between 1.4
and 1.5. It used to include timestamps in the xport command, and now
it does not by default. You can add --showtime to rrdtool xport to
restore the previous behavior.  In ganglia, this ends up being in
/usr/share/ganglia-webfrontend/graph.php on line 1089:
--
  // This command will export values for the specified format in XML
  $command = $rrdtool .
" xport --start '" . $rrdtool_graph_start .
"' --end '" .  $rrdtool_graph_end . "' --showtime"


Modifying it as above fixes the bug. I think this should be patched in
debian 9 as it is low impact and only fixes a bug.

See: https://sourceforge.net/p/ganglia/mailman/message/35440616/
and: https://github.com/oetiker/rrdtool-1.x/issues/672


-- 
  -Alex

Bug#923734: closed by Matthias Klose (Re: Bug#923734: Python needs updating: version push)

[Matthias Klose]

On 04.03.19 23:29, Brian Holaday wrote:
> I seem to be having issues then with installing: 3.5.3 on Stretch.
> 
> # sudo apt-get install python3.5
>> #python3.5 is already the newest version (3.5.3-1+deb9u1).
> 
> Is Python 3.5 only for Buster or SID?

no, for stretch. There is no 3.5 and 3.6. for buster.  Please stop re-opening
this issue.

> On Mon, Mar 4, 2019 at 12:48 PM Debian Bug Tracking System <
> ow...@bugs.debian.org> wrote:
> 
>> This is an automatic notification regarding your Bug report
>> which was filed against the python package:
>>
>> #923734: Python needs updating: version push
>>
>> It has been closed by Matthias Klose .
>>
>> Their explanation is attached below along with your original report.
>> If this explanation is unsatisfactory and you have not received a
>> better one in a separate message then please contact Matthias Klose <
>> d...@debian.org> by
>> replying to this email.
>>
>>
>> --
>> 923734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923734
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>>
>>
>> -- Forwarded message --
>> From: Matthias Klose 
>> To: Brian Holaday , 923...@bugs.debian.org,
>> 923734-d...@bugs.debian.org
>> Cc:
>> Bcc:
>> Date: Mon, 4 Mar 2019 20:46:16 +0100
>> Subject: Re: Bug#923734: Python needs updating: version push
>> On 04.03.19 19:37, Brian Holaday wrote:
>>> Package: python
>>> Version: 2.7.13-2
>>> severity: important
>>>
>>> Issue:
>>>
>>> Python 3.7.2 has been released out for some time now. Can we get an
>> update
>>> pushed out to stretch-backports
>>
>> no, not doing that.
>>
>>> or SID at some point?
>>
>> it's there "for some time now"
>>
>>
>> -- Forwarded message --
>> From: Brian Holaday 
>> To: sub...@bugs.debian.org
>> Cc:
>> Bcc:
>> Date: Mon, 4 Mar 2019 11:37:37 -0700
>> Subject: Python needs updating: version push
>> Package: python
>> Version: 2.7.13-2
>> severity: important
>>
>> Issue:
>>
>> Python 3.7.2 has been released out for some time now. Can we get an update
>> pushed out to stretch-backports or SID at some point?
>>
> 

Bug#923746: dnsmasq: ra advertises wrong ipv6 link MTU

[Chris Carr]

Package: dnsmasq
Version: 2.76-5+deb9u1
Severity: normal
Tags: ipv6

Dear Maintainer,

   * What led up to the situation?

My browsing from my Windows box suddenly went weird

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

I checked the MTU sizes the Windows box was using: 1500 for both ipv4 
and ipv6. The ipv6 one should be 1280 (I'm using an HE tunnel). So I 
fixed it in windows using


netsh interface ipv6 set subinterface "Local Area Connection" mtu=1280 
store=persistent


   * What was the outcome of this action?

Minutes later it was back to 1500 so I looked at my dnsmasq.conf 
(attached) - all seems tickety boo so I checked 
/proc/sys/net/ipv6/conf/he-ipv6/mtu and that is correctly set to 1280, 
so for some reason dnsmasq is not picking that up and advertising it for 
my he-ipv6 interface. I checked with wireshark and the ra packets are 
being sent out with MTU 1500 not 1280.


   * What outcome did you expect instead?

I expected Windows to receive the correct MTU size of 1280 as set in 
/proc/sys/net/ipv6/conf/he-ipv6/mtu


Many thanks for a great piece of software,

CC


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

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

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

Versions of packages dnsmasq depends on:
ii  dnsmasq-base 2.76-5+deb9u1
ii  init-system-helpers  1.48
ii  netbase  5.4

dnsmasq recommends no packages.

Versions of packages dnsmasq suggests:
pn  resolvconf  

-- Configuration Files:
/etc/dnsmasq.conf changed:
domain-needed
bogus-priv
no-resolv
no-poll
server=2606:4700:4700::
server=2606:4700:4700::1001
server=1.1.1.1
server=1.0.0.1
local=/sadnet/
interface=int0
bind-interfaces
expand-hosts
domain=sadnet
dhcp-range=192.168.4.1,192.168.4.127,255.255.255.0,192.168.4.255,24h
read-ethers
dhcp-option=42,0.0.0.0
dhcp-option=19,0   # option ip-forwarding off
dhcp-option=44,0.0.0.0 # set netbios-over-TCP/IP nameserver(s) aka 
WINS server(s)

dhcp-option=45,0.0.0.0 # netbios datagram distribution server
dhcp-option=46,8   # netbios node type
dhcp-option=47 # empty netbios scope.
dhcp-option=vendor:PXEClient,1,192.168.4.30
dhcp-option=vendor:MSFT,2,1i
dhcp-option=vendor:Etherboot,60,"Etherboot"
dhcp-boot=pxelinux.0

enable-tftp
tftp-root=/srv/Linux/images/Debian-netboot
dhcp-authoritative
bogus-nxdomain=64.94.110.11
bogus-nxdomain=81.200.64.50
mx-target=mail.sadnet
localmx
log-dhcp
bootp-dynamic
cname=ntinstall,fatboy
cname=uranos,fatboy
enable-ra
dhcp-range=tag:int0,::1,constructor:int0,ra-names,24h
dhcp-option=option6:dns-server,2001:470:1f1d:1d3::1


-- no debconf information

Bug#623537: virt-manager: Confirms issue

[Nils Jarle Haugen]

Dear maintainer,


I can confirm that i fixed the issue after consulting with some support 
over at the #virt channel on OFTC.
The issue was that the libvirt system user account (libvirt-qemu) was 
not a member of the plugdev group, which owns /dev/kvm.


After adding the libvirt-qemu to the plugdev group, libvirt recognises 
KVM and runs as normal.


I'm not sure how this happend, as I've never done any changes to that group.



Kind regards,

Nils J. Haugen


On Mon, 25 Feb 2019 11:30:40 +0100 nils+bugl...@gaupne.net wrote:
> Package: virt-manager
> Version: 1:2.0.0-3
> Followup-For: Bug #623537
>
> Dear Maintainer,
>
>
> I can confirm to experience the same issue, virt-manager/libvirt are
> unable to detect the presence of KVM on the system. It stopped working
> after updating to version 1.2.0.0-3. Virt-manager the tries to run the
> virtual machines with QEMU TCG...
>
> I've checked with both lsmod and kvm-ok and they reports that the
> required modules are
> loaded.  Intel Virtualisation Technology is enabled in BIOS.
> The CPU running on the machineis an i7 7820HQ. I've tried purging all
> qemu-system-* libvirt-* packages and reinstalling qemu-kvm, 
libvirt-client,

> qemu-utils and libvirt-daemon-system
>
> As opposed to using libivirt I can run the virtual machines fine with
> qemu-system and
> experience bare-metal performance. So my guess is that this might be a
> bug in libvirt/ virt-manager, as the other systems can detect KVM us
> usual ?
>
> Best regards,
> Nils J. Haugen
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=nn_NO.UTF-8, LC_CTYPE=nn_NO.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages virt-manager depends on:
> ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
> ii  gir1.2-gtk-3.0   3.24.5-1
> ii  gir1.2-gtk-vnc-2.0   0.9.0-1
> ii  gir1.2-libosinfo-1.0 1.2.0-1
> ii  gir1.2-libvirt-glib-1.0  1.0.0-1
> ii  gir1.2-vte-2.91  0.54.2-2
> ii  librsvg2-common  2.44.10-1
> ii  python-requests  2.20.0-2
> ii  python3  3.7.2-1
> ii  python3-dbus 1.2.8-3
> ii  python3-gi   3.30.4-1
> ii  python3-gi-cairo 3.30.4-1
> ii  python3-libvirt  5.0.0-1
> ii  virtinst 1:2.0.0-3
>
> Versions of packages virt-manager recommends:

Bug#923745: python-pandas: import pandas hanging Flask 0.11.1 / Apache 2.4.18

[Andreas Bussjaeger]

Package: python-pandas
Version: 0.19.2-5.1
Severity: important
Tags: patch



-- System Information:
Debian Release: 9.8
Architecture: amd64 (x86_64)

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

Versions of packages python-pandas depends on:
ii  python2.7.13-2
ii  python-dateutil   2.5.3-2
ii  python-numpy  1:1.12.1-3
ii  python-pandas-lib 0.19.2-5.1
ii  python-pkg-resources  33.1.1-1
ii  python-six1.10.0-3
ii  python-tz 2016.7-0.3

Versions of packages python-pandas recommends:
ii  python-bs4  4.5.3-1
ii  python-html5lib 0.9-1
ii  python-lxml 3.7.1-1
ii  python-matplotlib   2.0.0+dfsg1-2
ii  python-numexpr  2.6.1-4
ii  python-openpyxl 2.3.0-3
ii  python-scipy0.18.1-2
ii  python-statsmodels  0.8.0~rc1+git59-gef47cd9-5
ii  python-tables   3.3.0-5
ii  python-xlrd 1.0.0-1
ii  python-xlwt 0.7.5+debian1-1

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

-- no debconf information


In python-pandas 0.19.2-5.1 there is a known bug 
(https://github.com/pandas-dev/pandas/issues/14641)

An application (privacyidea) hangs during initialization phase of python pandas 
library 

This bug was also discussed here:

https://github.com/jzwinck/pandas/commit/dadb97c6e3fa684466b4e1b89c66cad677d3da03

In later versions (0.20 and 0.22) of this package the solution was to 
statically define "_eps":

root@ecs-privacyidea01:/tmp# wget 
https://github.com/pandas-dev/pandas/archive/v0.20.0.tar.gz
root@ecs-privacyidea01:/tmp# tar -xzvf v0.20.0.tar.gz 
root@ecs-privacyidea01:/tmp# grep -R _eps pandas-0.20.0/
pandas-0.20.0/pandas/core/indexing.py:_eps = 1.1920929e-07
pandas-0.20.0/pandas/core/indexing.py:np.allclose(x, int(x), 
rtol=_eps, atol=0))

root@ecs-privacyidea01:/tmp# grep -R _eps pandas-0.22.0/
pandas-0.22.0/pandas/core/indexing.py:_eps = 1.1920929e-07
pandas-0.22.0/pandas/core/indexing.py:np.allclose(x, int(x), 
rtol=_eps, atol=0))

Please provide this patch also for 0.19 versions in debian 9.x

Bug#923744: python3-periodictable: bad Suggests

[Jakub Wilk]

Package: python3-periodictable
Version: 1.5.0-7

python3-periodictable has "python-python-periodictable-doc" in Suggests.
That's one "python-" too many.

--
Jakub Wilk

Bug#923743: pcre3: FTBFS (dh_makeshlibs fails)

[Santiago Vila]

Package: src:pcre3
Version: 2:8.39-11
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
debian/jit-test.c:9:4: warning: #warning JIT enabled [-Wcpp]
   #warning JIT enabled
^~~
debian/jit-test.c:9:4: warning: #warning JIT enabled [-Wcpp]
   #warning JIT enabled
^~~
dh_testdir
# Add here commands to configure the package.
dh_autoreconf
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'

[... snipped ...]

dh_testroot -a
dh_install -a
# This man page is in the main package, don't want it in -dev
rm debian/libpcre3-dev/usr/share/man/man3/pcrepattern.3
# Move actual library to /lib
mkdir -p debian/libpcre3/lib/x86_64-linux-gnu
mv debian/libpcre3/usr/lib/x86_64-linux-gnu/libpcre.so.* 
debian/libpcre3/lib/x86_64-linux-gnu
ln -sf /lib/x86_64-linux-gnu/libpcre.so.3 
debian/libpcre3-dev/usr/lib/x86_64-linux-gnu/libpcre.so
# we never need to reference the library path in pcre-config on
# Debian, so clip it out so that the script will be multiarch-safe.
sed -i -e"s,/x86_64-linux-gnu,,g" debian/libpcre3-dev/usr/bin/pcre-config
dh_link -a
dh_installdocs -a
dh_installexamples -a
dh_installman -a
dh_installinfo -a
dh_installchangelogs -a ChangeLog
dh_strip -a --dbg-package=libpcre3-dbg
dh_compress -a
dh_fixperms -a
sed -e 's/JIT//' debian/libpcre3.symbols.in > debian/libpcre3.symbols
sed -e 's/JIT//' debian/libpcre16-3.symbols.in > debian/libpcre16-3.symbols
sed -e 's/JIT//' debian/libpcre32-3.symbols.in > debian/libpcre32-3.symbols
dh_makeshlibs -plibpcre3 --add-udeb="libpcre3-udeb" -V 'libpcre3 (>= 1:8.35)' 
-- -c4
dh_makeshlibs -plibpcrecpp0v5 -V 'libpcrecpp0v5 (>= 7.7)' -- -c4
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libpcrecpp0v5/DEBIAN/symbols doesn't match 
completely debian/libpcrecpp0v5.symbols
--- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-11_amd64)
+++ dpkg-gensymbolsV2Wi2n   2019-03-04 12:36:00.103243818 +
@@ -80,9 +80,9 @@
  (c++)"pcrecpp::Scanner::SetSkipExpression(char const*)@Base" 7.7
  (c++)"pcrecpp::Scanner::Skip(char const*)@Base" 7.7
  (c++)"pcrecpp::Scanner::~Scanner()@Base" 7.7
-#MISSING: 2:8.39-9# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
+#MISSING: 2:8.39-11# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
  (c++|optional=STL)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*, std::forward_iterator_tag)@Base" 2:8.39-10
-#MISSING: 2:8.39-9# (c++|optional=STL)"void std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
+#MISSING: 2:8.39-11# (c++|optional=STL)"void std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
  (c++|optional=STL)"void std::vector >::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 2:8.39-4
  (c++|optional=STL)"void std::vector 
>::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece&&)@Base" 2:8.39-9
- (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
+#MISSING: 2:8.39-11# (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:116: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


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

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

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

Thanks.

Bug#923561: parted: Incorrect optimal alignment for USB device

[Kevin Locke]

After a bit more research, I found that this issue has been mentioned
on linux-usb[1] and that Martin K. Petersen weighed in on the issue in
a util-linux-ng thread[2]:

On 17 June 2015 at 01:08, Martin K. Petersen  wrote:
> There's only so much we can do about devices that report garbage.
> 
> Also, the kernel only reports things. It is up to Karel to decide
> whether to sanity check the values before he uses them.

If we are going to bring it up again, I'd like to have a specific
recommendation or request.  More discussion below:

On Mon, 2019-03-04 at 13:42 -0500, Phillip Susi wrote:
> On 3/4/2019 11:50 AM, Kevin Locke wrote:
>> optimal_io_size is defined in the kernel ABI[1] as "the preferred
>> request size for workloads where sustained throughput is desired".  In
>> this case, I think it comes from scsi_disk.opt_xfer_blocks[2] which
>> comes from the VPD block limits page[3] which my disk reports as 65535
>> blocks (according to sg_vpd).
> 
> Yes, I was looking over the definition earlier in the kernel
> documentation, and it seems to me that part of the definition indicates
> it is simply an optimal size to transfer in, and has nothing to do with
> alignment.  But parted treats it as having to do with alignment, because
> the same kernel documentation mentions that is what the md driver uses
> the field for.

Could you point me to the kernel documentation that mentions how the
md driver uses optimal_io_size?

>> However, whether or not this is changed in the kernel, I would argue
>> it should be handled in parted.  Both to support previous+current
>> kernels and because I think the optimal_io_size ABI definition allows
>> optimal_io_size which is not a multiple of minimum_io_size for
>> transports where that truly is the case.
> 
> Unfortunately, that means parted needs to simply ignore the value of
> optimal io size as totally meaningless garbage, and I don't much like
> the thought of that.  If parted has always been wrong and the intended
> meaning of the kernel parameter has never had anything to do with
> alignment, then yes, parted needs to ignore it because it read meaning
> into it that was never intended.  But if it is supposed to have
> something to do with optimal alignment, then md is right and usb is
> wrong, and usb needs to be fixed.

My current reading is that optimal_io_size has the same definition as
SCSI VPD Optimal Transfer Length.  It has a loosely defined meaning,
but its value for any particular use is contingent on sanity checking.

Do you have a particular proposal for how to improve the kernel
documentation or how optimal_io_size behaves?  I worked up a patch
which only uses logical_to_bytes(sdp, sdkp->opt_xfer_blocks) for
io_opt if it is a multiple of sdkp->physical_block_size, but I am not
convinced enough that it is universally applicable to advocate for it.
Any alternative suggestions?

Thanks,
Kevin

[1]: https://www.spinics.net/lists/linux-usb/msg125988.html
[2]: https://www.spinics.net/lists/util-linux-ng/msg11702.html

Bug#923734: closed by Matthias Klose (Re: Bug#923734: Python needs updating: version push)

[Brian Holaday]

I seem to be having issues then with installing: 3.5.3 on Stretch.

# sudo apt-get install python3.5
> #python3.5 is already the newest version (3.5.3-1+deb9u1).

Is Python 3.5 only for Buster or SID?

On Mon, Mar 4, 2019 at 12:48 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the python package:
>
> #923734: Python needs updating: version push
>
> It has been closed by Matthias Klose .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Matthias Klose <
> d...@debian.org> by
> replying to this email.
>
>
> --
> 923734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923734
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Matthias Klose 
> To: Brian Holaday , 923...@bugs.debian.org,
> 923734-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 4 Mar 2019 20:46:16 +0100
> Subject: Re: Bug#923734: Python needs updating: version push
> On 04.03.19 19:37, Brian Holaday wrote:
> > Package: python
> > Version: 2.7.13-2
> > severity: important
> >
> > Issue:
> >
> > Python 3.7.2 has been released out for some time now. Can we get an
> update
> > pushed out to stretch-backports
>
> no, not doing that.
>
> > or SID at some point?
>
> it's there "for some time now"
>
>
> -- Forwarded message --
> From: Brian Holaday 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 4 Mar 2019 11:37:37 -0700
> Subject: Python needs updating: version push
> Package: python
> Version: 2.7.13-2
> severity: important
>
> Issue:
>
> Python 3.7.2 has been released out for some time now. Can we get an update
> pushed out to stretch-backports or SID at some point?
>

Bug#923742: RFS: ghostwriter/1.7.4-1~bpo9+1 [ITA] -- Distraction-free, themeable Markdown editor

[Sebastien CHAVAUX]

Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "ghostwriter" in backport.

 * Package name    : ghostwriter
   Version : 1.7.4-1~bpo9+1

  Upstream Author : wereturtle 

 * URL : https://wereturtle.github.io/ghostwriter/

 * License : GPL-3.0+

   Section : editors

  It builds those binary packages:

    ghostwriter - Distraction-free, themeable Markdown editor

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


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


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


    dget -x 
https://mentors.debian.net/debian/pool/main/g/ghostwriter/ghostwriter_1.7.4-1~bpo9+1.dsc 



  More information about ghostwriter can be obtained from 
https://wereturtle.github.io/ghostwriter/.



  Changes since the last upload:

gnome-commander (1.8.1-1) unstable; urgency=medium

  * New upstream release

 -- Sebastien CHAVAUX   Mon, 04 Mar 2019 22:25:55 
+0100



 Regards,
   Sebastien CHAVAUX

Bug#889089: zziplib: diff for NMU version 0.13.62-3.2

[Salvatore Bonaccorso]

Control: tags 910335 + patch

Dear maintainer,

Updated debdiff to include as well fixes for #910335.

Regards,
Salvatore
diff -Nru zziplib-0.13.62/debian/changelog zziplib-0.13.62/debian/changelog
--- zziplib-0.13.62/debian/changelog	2017-06-04 09:03:20.0 +0200
+++ zziplib-0.13.62/debian/changelog	2019-03-04 22:43:14.0 +0100
@@ -1,3 +1,22 @@
+zziplib (0.13.62-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Invalid memory access in zzip_disk_fread (CVE-2018-6381) (Closes: #889096)
+  * Reject the ZIP file and report it as corrupt if the size of the central
+directory and/or the offset of start of central directory point beyond the
+end of the ZIP file (CVE-2018-6484, CVE-2018-6541, CVE-2018-6869)
+(Closes: #889089)
+  * bus error in zzip_disk_findfirst function in zzip/mmapped.c
+(CVE-2018-6540) (Closes: #923659)
+  * out of bound read in mmapped.c:zzip_disk_fread() causes crash
+(CVE-2018-7725) (Closes: #913165)
+  * Bus error in zip.c:__zzip_parse_root_directory() cause crash via crafted
+zip file (CVE-2018-7726) (Closes: #913165)
+  * Memory leak triggered in the function __zzip_parse_root_directory in zip.c
+(CVE-2018-16548) (Closes: #910335)
+
+ -- Salvatore Bonaccorso   Mon, 04 Mar 2019 22:43:14 +0100
+
 zziplib (0.13.62-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru zziplib-0.13.62/debian/patches/Avoid-memory-leak-from-__zzip_parse_root_directory-1.patch zziplib-0.13.62/debian/patches/Avoid-memory-leak-from-__zzip_parse_root_directory-1.patch
--- zziplib-0.13.62/debian/patches/Avoid-memory-leak-from-__zzip_parse_root_directory-1.patch	1970-01-01 01:00:00.0 +0100
+++ zziplib-0.13.62/debian/patches/Avoid-memory-leak-from-__zzip_parse_root_directory-1.patch	2019-03-04 22:43:14.0 +0100
@@ -0,0 +1,74 @@
+From: jmoellers 
+Date: Fri, 7 Sep 2018 11:32:04 +0200
+Subject: Avoid memory leak from __zzip_parse_root_directory().
+Origin: https://github.com/gdraheim/zziplib/commit/9411bde3e4a70a81ff3ffd256b71927b2d90dcbb
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-16548
+Bug-Debian: https://bugs.debian.org/910335
+Bug: https://github.com/gdraheim/zziplib/issues/58
+
+---
+
+diff --git a/zzip/zip.c b/zzip/zip.c
+index 88b833b2533d..a6852802f87e 100644
+--- a/zzip/zip.c
 b/zzip/zip.c
+@@ -475,9 +475,15 @@ __zzip_parse_root_directory(int fd,
+ } else
+ {
+ if (io->fd.seeks(fd, zz_rootseek + zz_offset, SEEK_SET) < 0)
++	{
++		free(hdr0);
+ return ZZIP_DIR_SEEK;
++	}
+ if (io->fd.read(fd, , sizeof(dirent)) < __sizeof(dirent))
++	{
++		free(hdr0);
+ return ZZIP_DIR_READ;
++	}
+ d = 
+ }
+ 
+@@ -577,12 +583,38 @@ __zzip_parse_root_directory(int fd,
+ 
+ if (hdr_return)
+ *hdr_return = hdr0;
++	else
++	{
++	/* If it is not assigned to *hdr_return, it will never be free()'d */
++	free(hdr0);
++	/* Make sure we don't free it again in case of error */
++	hdr0 = NULL;
++	}
+ }   /* else zero (sane) entries */
+ #  ifndef ZZIP_ALLOW_MODULO_ENTRIES
+-return (entries != zz_entries ? ZZIP_CORRUPTED : 0);
++if (entries != zz_entries)
++{
++	/* If it was assigned to *hdr_return, undo assignment */
++	if (p_reclen && hdr_return)
++	*hdr_return = NULL;
++	/* Free it, if it was not already free()'d */
++	if (hdr0 != NULL)
++	free(hdr0);
++	return ZZIP_CORRUPTED;
++}
+ #  else
+-return ((entries & (unsigned)0x) != zz_entries ? ZZIP_CORRUPTED : 0);
++if (((entries & (unsigned)0x) != zz_entries)
++{
++	/* If it was assigned to *hdr_return, undo assignment */
++	if (p_reclen && hdr_return)
++	*hdr_return = NULL;
++	/* Free it, if it was not already free()'d */
++	if (hdr0 != NULL)
++	free(hdr0);
++	return ZZIP_CORRUPTED;
++}
+ #  endif
++return 0;
+ }
+ 
+ /* - high-level interface - */
+-- 
+2.11.0
+
diff -Nru zziplib-0.13.62/debian/patches/Avoid-memory-leak-from-__zzip_parse_root_directory-2.patch zziplib-0.13.62/debian/patches/Avoid-memory-leak-from-__zzip_parse_root_directory-2.patch
--- zziplib-0.13.62/debian/patches/Avoid-memory-leak-from-__zzip_parse_root_directory-2.patch	1970-01-01 01:00:00.0 +0100
+++ zziplib-0.13.62/debian/patches/Avoid-memory-leak-from-__zzip_parse_root_directory-2.patch	2019-03-04 22:43:14.0 +0100
@@ -0,0 +1,56 @@
+From: jmoellers 
+Date: Fri, 7 Sep 2018 11:49:28 +0200
+Subject: Avoid memory leak from __zzip_parse_root_directory().
+Origin: https://github.com/gdraheim/zziplib/commit/d2e5d5c53212e54a97ad64b793a4389193fec687
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-16548
+Bug-Debian: https://bugs.debian.org/910335
+Bug: https://github.com/gdraheim/zziplib/issues/58
+
+---
+ zzip/zip.c | 25 ++---
+ 1 file changed, 2 

Bug#923741: new upstream release

[Antoine Beaupre]

Package: rofi
Version: 1.5.1-1
Severity: wishlist

A new release (1.5.2) of rofi was published:

https://github.com/DaveDavenport/rofi/releases/tag/1.5.2

I've tried to upgrade this myself but there's weird stuff going on, as
"git diff 1.5.0..upstream/1.5.0" differs, yet there's no +dfsg tag or
a clear way to reproduce the orig tarball from the git repo.

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

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

Versions of packages rofi depends on:
ii  libc6 2.28-7
ii  libcairo2 1.16.0-2
ii  libglib2.0-0  2.58.3-1
ii  libpango-1.0-01.42.4-6
ii  libpangocairo-1.0-0   1.42.4-6
ii  librsvg2-22.44.10-1
ii  libstartup-notification0  0.12-6
ii  libxcb-ewmh2  0.4.1-1.1
ii  libxcb-icccm4 0.4.1-1.1
ii  libxcb-randr0 1.13.1-2
ii  libxcb-util0  0.3.8-3+b2
ii  libxcb-xinerama0  1.13.1-2
ii  libxcb-xkb1   1.13.1-2
ii  libxcb-xrm0   1.0-3
ii  libxcb1   1.13.1-2
ii  libxkbcommon-x11-00.8.2-1
ii  libxkbcommon0 0.8.2-1

rofi recommends no packages.

rofi suggests no packages.

-- no debconf information

Bug#923740: unblock: pacemaker/2.0.1-1

[Ferenc Wágner]

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

Dear Release Team,

Please advise about the situation with Pacemaker.

At the moment pacemaker_2.0.1~rc5-1 is 6 days old in unstable (it was
uploaded on the day following its release) and now that it finally built
on all architectures (it triggered a linker bug on amd64) I expect it to
migrate to testing this week, well before the full freeze.

However, Pacemaker 2.0.1 final was released today and includes a single
code change only, with the following commit message (the change itself
is the deletion of lines at the end of the debdiff below):

High: libcrmcommon: complete interrupted live migrations correctly

8435966 (2.0.0) got the sense of compare_version() wrong when
attempting to remove the old behavior for recording partial live
migrations, instead re-introducing it.

This causes a regression in behavior when a transition containing a
live migration is aborted after the migrate_to has been initiated
but before the migrate_from has been initiated. In that case, it
would schedule a full start on the destination node rather than a
migrate_from.

I think we should release buster with Pacemaker 2.0.1, thus with this
fix and the small documentation fixes also bundled with it.  The added
include directives just make previously indirect includes explicit, and
our build doesn't use the abi-check script, so that change is a no-op.
Full debdiff from 2.0.1~rc5-1 (which is on its way to testing):

diff -Nru pacemaker-2.0.1~rc5/abi-check pacemaker-2.0.1/abi-check
--- pacemaker-2.0.1~rc5/abi-check   2019-02-25 22:35:40.0 +0100
+++ pacemaker-2.0.1/abi-check   2019-03-04 20:55:07.0 +0100
@@ -76,7 +76,8 @@
 
 EOF
 
-abi-compliance-checker -l $PACKAGE -dump_abi $DESC
+abi-compliance-checker -l $PACKAGE -dump_abi $DESC \
+-dump-path abi_dumps/${PACKAGE}/${PACKAGE}_${VERSION}.abi.tar.gz
 rm -rf $BUILD_ROOT
 }
 
diff -Nru pacemaker-2.0.1~rc5/ChangeLog pacemaker-2.0.1/ChangeLog
--- pacemaker-2.0.1~rc5/ChangeLog   2019-02-25 22:35:40.0 +0100
+++ pacemaker-2.0.1/ChangeLog   2019-03-04 20:55:07.0 +0100
@@ -1,103 +1,75 @@
-* Mon Feb 25 2019 Ken Gaillot  Pacemaker-2.0.1-rc5
-- Changesets: 17
-- Diff:   15 files changed, 1037 insertions(+), 677 deletions(-)
-
-- Changes since Pacemaker-2.0.1-rc4
-  + scheduler: regression test compatibility with glib 2.59.0
-
-* Tue Jan 29 2019 Ken Gaillot  Pacemaker-2.0.1-rc4
-- Changesets: 42
- 15 files changed, 216 insertions(+), 137 deletions(-)
-
-- Changes since Pacemaker-2.0.1-rc3
-  + attrd: clear election dampening when the writer leaves
-  + controller: clear election dampening when DC is lost
-  + scheduler: don't order non-DC shutdowns before DC fencing
-  + libcrmservice: cancel DBus call when cancelling systemd/upstart actions
-  + tools: remove duplicate fence history state in crm_mon XML output
-  + build: offer configure option to disable tests broken with glib 2.59.0
-  + build: minor logging fixes to allow compatibility with GCC 9 -Werror
-
-* Thu Jan 10 2019 Ken Gaillot  Pacemaker-2.0.1-rc3
-- Changesets: 27
-- Diff:   20 files changed, 375 insertions(+), 195 deletions(-)
-
-- Changes since Pacemaker-2.0.1-rc2
-  + attrd: start new election immediately if writer is lost
-  + attrd: detect alert configuration changes when CIB is entirely replaced
-  + controller: avoid transition timeout if resource cleaned while operation
-is in-flight (regression in 2.0.1-rc1)
-  + libstonithd: restore C++ compatibility (regression in 2.0.1-rc1)
-  + tools: fix crm_resource --clear when lifetime was used with ban/move
-  + tools: fix crm_resource --move when lifetime was used with previous move
-
-* Wed Dec 19 2018 Ken Gaillot  Pacemaker-2.0.1-rc2
-- Changesets: 12
-- Diff:   2 files changed, 6 insertions(+), 2 deletions(-)
-
-- Changes since Pacemaker-2.0.1-rc1
-  + libpe_status: avoid double free of stop_needed list (regression in 
2.0.1-rc1)
-  + tools: stonith_admin -I doesn't require an agent (regression in 2.0.1-rc1)
-
-* Wed Dec 12 2018 Ken Gaillot  Pacemaker-2.0.1-rc1
-- Changesets: 481
- 164 files changed, 7717 insertions(+), 4398 deletions(-)
+* Mon Mar 4 2019 Ken Gaillot  Pacemaker-2.0.1-1
+- Changesets: 592
+ 173 files changed, 9268 insertions(+), 5344 deletions(-)
 
 - Features added since Pacemaker-2.0.0
-  + Pacemaker bundles now support podman container management
-  + fencing: SBD may now be used in a cluster that has guest nodes or bundles
-  + fencing: synchronize fencing history among all nodes
-  + fencing: stonith_admin now has option to clear fence history
-  + tools: crm_mon now supports showing fencing action failures and history
+  + Pacemaker bundles support podman for container management
+  + fencing: SBD may be used in a cluster that has guest nodes or bundles
+  + fencing: fencing history is synchronized among all nodes
+  + fencing: 

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

[Margarita Manterola]

Hi,

> - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> 
> The winners are:
>Option M `middle`
>Option H `hard`
> 
> - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> 
> Dear Marga, as Chair, could you please make use of your casting vote to break 
> this tie?

I'm using my casting vote to vote in favor of M `middle` (i.e. consider
that the desirable situation at the time of bullseye is that both directory
schemes are allowed, all packages can be built on either).

My rationale for taking this decision is as follows:

Right now we are not ready to migrate to building on merged-usr systems in
Debian, there are still 29 known packages that are broken and need to be
fixed.  My expectation is that those packages will be fixed in the not so
distant future (i.e.  before bullseye) and that after that, the buildd
profile in debootstrap will default to having a merged /usr, so that new
buildd chroots will use that setup.

However, we have no control over how fast individual developers and
derivative distributions will migrate to the new format. It's possible that
more time will be required until everyone is ready to migrate.

Additionally, as of our current understanding of the issue, there are no
known problems for building on a non-merged system. Supporting this
setup does not imply additional work from the point of view of our
maintainers (for now).

In the future, it would be a bug if a problem is discovered with building a
package on a non-merged /usr system. I understand that this would mean
additional work to the maintainers of such a package, but at least as of
today this is a non-issue. Eventually, when fixing such bugs becomes a
significant burden for our maintainers, it can be decided that the setup is
no-longer supported, but my personal recommendation would be to wait at
least until bullseye+1. That's why I'm voting "Middle" for bullseye.

-- 
Thanks,
Marga


signature.asc
Description: PGP signature

Bug#890780: closed by Paul Gevers (Re: release-notes: document that s390x now require at least a z196 CPU)

[Aurelien Jarno]

On 2019-03-04 13:51, Debian Bug Tracking System wrote:
> Hi Aurelien,
> 
> On Sun, 18 Feb 2018 21:52:07 +0100 Aurelien Jarno 
> wrote:> The s390x baseline ISA has been raised to z196 in buster [1]. This
> > should be mentioned in the release notes.
> > 
> > I'll try to work on a patch in the next days. I am filling this bug to
> > make sure I do not forget.
> 
> I have committed a (first) version:
> https://salsa.debian.org/ddp-team/release-notes/commit/97071d6
> 

Thanks for working on that. It looks good to me.

Aurelien

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


signature.asc
Description: PGP signature

Bug#658759: [kirkwood] squeeze-backports kernel fails to boot on SheevaPlug

[Ben Hutchings]

On Mon, 2019-03-04 at 20:35 +0100, Paul Gevers wrote:
> Hi all,
> 
> On Fri, 24 Aug 2012 09:44:47 +0100 Ian Campbell  wrote:
> > On Fri, 2012-08-24 at 00:31 -0700, Jonathan Nieder wrote:
> > > Any ideas for how to word a hint about this for
> > > the wheezy release-notes?
> > 
> > Hrm, how about:
> > 
> > The version of u-boot shipped from the factory on many
> > kirkwood(???) devices, as well as u-boot shipped in versions of
> > Debian prior to Wheezy, contain a bug (#658759) which renders
> > them unable to boot kernel versions 3.2(???) or newer. This
> > includes the kernel in Wheezy.
> > 
> > Users are advised to upgrade u-boot before upgrading their
> > kernel. XXX link to suitable documentation?
> > http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html 
> > and similar?
> > 
> > (??? fact needs checking). 
> 
> This bug is marked as affecting the release-notes. I don't think this is
> relevant for stretch or buster anymore? If not, I'll like to remove the
> "affects", to not clutter the release-notes bug list.

Again, it should have been mentioned and I don't believe the kernel has
a workaround for this, but it would probably be pointless to mention
now.

Ben.

-- 
Ben Hutchings
A free society is one where it is safe to be unpopular.
  - Adlai Stevenson




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

Bug#923582: New active fork

[Scott Talbert]

On Sat, 2 Mar 2019, Bastian Germann wrote:


There is a new active fork available at
https://github.com/suds-community/suds. Please consider switching to the
suds-community version because suds-jurko is not maintained anymore
(https://bitbucket.org/jurko/suds/issues/117/please-release-new-version).


Will look into it post-buster.

Bug#923739: RM: apache-mod-auth-ntlm-winbind -- RoQA; Orphaned, dead upstream, insecure protocol

[Olly Betts]

Package: ftp.debian.org
Severity: normal

I think it's time we dropped apache-mod-auth-ntlm-winbind.

It's been orphaned in Debian for just over 3 years (I was the last
maintainer).

It's not been updated upstream for many years.  I can't easily check
exactly when as the upstream SVN repo which actually had the latest
version seems to have gone away, and their git mirror seems to be
missing the 16 most recent commits, but the packaged source is more than
8 years old and the git mirror's most recent change is from 2007-11-08.

There are problems with NTLM's design which mean it's just not secure enough
especially given the computing power that's now easily available to an
attacker.  Wikipedia has a summary:

https://en.wikipedia.org/wiki/NT_LAN_Manager#Weakness_and_Vulnerabilities

HTTP Negotiate Auth offers a more secure replacement option, provided
you're able to run it over https.  But thanks to LE https certificates
can be had for free now.

I didn't request removal when I orphaned the package in case it was
still useful to someone in particular circumstances, but that was just
over 3 years ago and the likelihood of that will have decreased still
further.

Cheers,
Olly


signature.asc
Description: PGP signature

Bug#697029: [ilk] using GNOME 3 makes computer sluggish after a few minutes

[Ben Hutchings]

On Mon, 2019-03-04 at 20:45 +0100, Paul Gevers wrote:
> Hi,
> 
> On Sun, 24 Feb 2013 07:08:14 + Ben Hutchings 
> wrote:
> 
> > "Graphics rendering may be very slow on Intel 'Ironlake M' GPUs (PCI
> > ID 8086:0046) when an IOMMU (VT-d) is enabled.  The IOMMU
> > functionality can be disabled for the GPU by adding the kernel
> > parameter 'intel_iommu=igfx_off'."
> 
> This bug is marked as affecting the release-notes. I don't think this is
> still relevant for stretch or buster? If not, I'll like to remove the
> "affects", to not clutter the release-notes bug list.

This should have been included in release notes, and I don't think the
issue has been solved, but at this point it's probably pointless to
mention it.

Ben.

-- 
Ben Hutchings
A free society is one where it is safe to be unpopular.
  - Adlai Stevenson




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

Bug#520712: projekt charytatywny

[Wang Jianlin]

 

-- 
Mam zamiar przekazać ci część mojego majątku jako darowiznę pieniężną w
postaci wolnej woli, Odpowiadać, aby wziąć udział.
Wang Jianlin
Grupa Wanda
 

Bug#923738: pms: run without terminal and passworded mpd results in infinite loop filling xsession-errors

[Joshua Honeycutt]

Package: pms
Version: 0.42-1+b3
Severity: important

Dear Maintainer,

I have a mpd instance with password, but pms was not configured for it 
yet. I ran pms from dmenu_run instead of a terminal. The result was an 
infinite loop on the password prompt. This gets logged to 
.xsession-errors. This filled my disk which is how I found out.


Attached is a patch that causes pms to exit if fgets() returns a null 
string (not just an empty string). This prevents the infinite loop in 
my case but seems to still allow pms to prompt indefinitely when run 
properly from a terminal.


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

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

Versions of packages pms depends on:
ii  libc6 2.28-7
ii  libgcc1   1:8.2.0-21
ii  libglib2.0-0  2.58.3-1
ii  libncursesw6  6.1+20181013-2
ii  libstdc++68.2.0-21
ii  libtinfo6 6.1+20181013-2

Versions of packages pms recommends:
ii  mpd  0.21.4-1+b1

pms suggests no packages.

-- no debconf information
diff --git a/src/pms.cpp b/src/pms.cpp
index 2c60585..4c8e798 100644
--- a/src/pms.cpp
+++ b/src/pms.cpp
@@ -471,7 +471,8 @@ Pms::main()
 		printf(_("This mpd server requires a password.\n"));
 		printf(_("Password: "));
 
-		fgets(pass, 512, stdin) ? 1 : 0; //ternary here is a hack to get rid of a warn_unused_result warning
+		if (fgets(pass, 512, stdin) == 0)
+			return PMS_EXIT_BADPASS;
 		if (pass[strlen(pass)-1] == '\n') {
 			pass[strlen(pass)-1] = '\0';
 		}

Bug#923737: therion: Segfault when producing SVG output

[Olly Betts]

Package: therion
Version: 5.4.3ds1-4
Severity: important
Tags: patch

On the upstream therion list Andrew Atkinson reported that SVG output
fails with therion from Debian testing:

> Using 5.4.3ds1-4 on Debian testing
> 
> The thconfig.thc at
> 
> http://www.cave-registry.org.uk/svn/WookeyCatchment/SludgePit/
> 
> works fine for pdf map output, but if I try to output svg a file is
> produced that does not display in any of the svg programs I have. It
> also does not finishing compiling giving a red ERROR in xtherion
> 
> The log file just seems to stop
[...]

Full version at:
https://mailman.speleo.sk/pipermail/therion/2019-February/007490.html

Upstream has fixed this (it turns out to be due to a segfault):

https://github.com/therion/therion/commit/947e9454814cb3c55d838bc45e52b832e752579a

This makes the therion unusable for anyone wanting to produce SVG output,
so it would be good to get this fixed for buster.

Cheers,
Olly

Bug#444821: pppoe: Source address patch forces promiscuous mode

[Bastian Schmidt]

Package: pppoe
Version: 3.12-2

The current version in testing (3.12-2) is still exhibiting this 
behavior, which essentially causes pppoe to always set the interface to 
promiscous mode.


On Mon, 01 Oct 2007 11:29:14 +0200 Norman Rasmussen 
 wrote:


> Package: pppoe
> Version: 3.8-3
> Severity: important
> Tags: patch
>
> Re: the last comment for bug 298202 [1] highlights a bug caused by the
> patch from bug 419677 [2].
>
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298202
> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419677
>
> Basically with the new code, the interface is _ALWAYS_ set to
> promiscuous mode, which is bad in my books.
>
> The reason for this is that the myEth variable is being populated
> during discovery, and then it's non-zero when the connection is
> actually being established - so the connect 'thinks' that it was
> specified manually. (i.e. the patch doesn't have a side effect if
> discovery is disabled, which probably happens in server mode only)
>
> I've created a patch that adds an optForceMAC variable, the code is a
> bit ugly (it re-zeros myEth if -H was _not_ passed), but it works.
>
> I also have a copy of the fixed/updated the iproute2 patch [3] in my git
> repo [4].
>
> [3] 
http://www.linuxfromscratch.org/patches/downloads/rp-pppoe/rp-pppoe-3.5-iproute2-1.patch

> [4] http://darkskies.za.net/~norman/rp-pppoe.git
>
> -- System Information:
> Debian Release: lenny/sid
> APT prefers stable
> APT policy: (750, 'stable'), (700, 'testing'), (600, 'unstable'), 
(550, 'experimental')

> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.17-2-686 (SMP w/1 CPU core)
> Locale: LANG=en_ZA, LC_CTYPE=en_ZA (charmap=ISO-8859-1)
> Shell: /bin/sh linked to /bin/bash
>
> Versions of packages pppoe depends on:
> ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries
> ii ppp 2.4.4rel-9 Point-to-Point Protocol (PPP) daem
>
> pppoe recommends no packages.
>
> -- no debconf information
>
>
>

Bug#923366: packaging-tutorial: [INTL:pt] Updated Portuguese translation

[Américo Monteiro]

A segunda-feira, 4 de março de 2019 21:00:55 WET Lucas Nussbaum escreveu:
> On 26/02/19 at 23:29 +, Américo Monteiro wrote:
> > Package:  packaging-tutorial
> > Version: 0.22
> > Tags: l10n, patch
> > Severity: wishlist
> > 
> > Updated Portuguese translation for  packaging-tutorial
> > Translator: Américo Monteiro 
> > Feel free to use it.
> > 
> > For translation updates please contact 'Last Translator'
> 
> Hi,
> 
> I think your forgot the attachment?
> 
> Lucas

yes i did...


Best regards
Américo


packaging-tutorial_0.22_pt.po.gz
Description: application/gzip

Bug#923366: packaging-tutorial: [INTL:pt] Updated Portuguese translation

[Lucas Nussbaum]

On 26/02/19 at 23:29 +, Américo Monteiro wrote:
> Package:  packaging-tutorial
> Version: 0.22
> Tags: l10n, patch
> Severity: wishlist
> 
> Updated Portuguese translation for  packaging-tutorial
> Translator: Américo Monteiro 
> Feel free to use it.
> 
> For translation updates please contact 'Last Translator' 

Hi,

I think your forgot the attachment?

Lucas

Bug#923622: packaging-tutorial: Typo in Slide 49

[Lucas Nussbaum]

On 04/03/19 at 18:55 +0600, Judit Foglszinger wrote:
> tags 923622 +patch
> 
> Added patch for fixing typo (and unfuzzy translations).

thanks! applied.

Bug#922270: kmail - "Name" column in message window can not made smaller

[Hans]

Hi Sandro, 

great! This did the trick. I deleted the line beginning with "Headerstate" and 
everything is working fine again. 

However, I knew, that the entry must have been in kmail2rc, but I could not 
really understand the values in this line. I can only confirm what you said:
not really readable by humans! 

Thank you for very much your solution. 

This bugreport can safely be closed.

To all helpers: Thank you very much for your efforts!

Best regards

Hans
> Well it working for me. The setting is inside .config/kmail2rc:
> 
> [CollectionFolderView]
> HeaderState
> HozizonalScroll
> VericalScroll
> 
> deleting those three keys should trigger kmail ti preset them with default
> values. Unfortunatelly HeaderState is not really readable by humans, this is
> some Qt interal dump.
> 
> hefee



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

Bug#923735: Don't autocomplete external modules under secure boot

[Alkis Georgopoulos]

Package: grub2
Version: 2.02+dfsg1-12
Severity: wishlist

Pressing  under secure boot lists the "regexp" module,
which is available under grub/x86_64-efi, but not loadable under secure 
boot,

so I think it should be hidden from the available commands list.

Thanks!

Bug#908796: udev (with sysvinit) fails to find devices at boot

[Trek]

Control: tag -1 patch

hello,

the new dpkg version finally landed to testing, so I send you a little
patch to enable both --notify-await and --wait-daemon options

this patch was tested against dpkg 1.19.5 and udev 241-1 (unstable)

all is running fine! (boot and shutdown)

I would say a big thank you to everyone involved :)

Trekdiff --git a/debian/udev.init b/debian/udev.init
index 6a3c9b3926..cf9310734c 100644
--- a/debian/udev.init
+++ b/debian/udev.init
@@ -166,7 +166,8 @@ case "$1" in
 
 log_daemon_msg "Starting $DESC" "$NAME"
 if start-stop-daemon --start --name $NAME --user root --quiet \
---pidfile $PIDFILE --exec $DAEMON --background --make-pidfile; then
+--pidfile $PIDFILE --exec $DAEMON --background --make-pidfile \
+--notify-await; then
 # prevents udevd to be killed by sendsigs (see #791944)
 mkdir -p $OMITDIR
 ln -sf $PIDFILE $OMITDIR/$NAME
@@ -178,7 +179,7 @@ case "$1" in
 fi
 
 log_action_begin_msg "Synthesizing the initial hotplug events (subsystems)"
-if udevadm trigger --type=subsystems --action=add; then
+if udevadm trigger --type=subsystems --action=add --wait-daemon; then
 log_action_end_msg $?
 else
 log_action_end_msg $?
@@ -226,7 +227,8 @@ case "$1" in
 
 log_daemon_msg "Starting $DESC" "$NAME"
 if start-stop-daemon --start --name $NAME --user root --quiet \
---pidfile $PIDFILE --exec $DAEMON --background --make-pidfile; then
+--pidfile $PIDFILE --exec $DAEMON --background --make-pidfile \
+--notify-await; then
 # prevents udevd to be killed by sendsigs (see #791944)
 mkdir -p $OMITDIR
 ln -sf $PIDFILE $OMITDIR/$NAME

Bug#921741: cups: Cups sheduler stops with program error when using JobPreserveHistory

[Brian Potkin]

On Mon 04 Mar 2019 at 19:39:24 +0100, Emin Kaya wrote:

> Hi Brian,

Hello Emin. Thank you for the level of detail.
 
> Am Mo., 4. März 2019 um 16:49 Uhr schrieb Brian Potkin <
> claremont...@gmail.com>:
> 
> > [...]
> 
> 
> 
> > > To do this, we found "JobPreserveHistory " as root option in
> > > the documentation for /etc/cups/cupsd.conf, which would do the job
> > > perfectly.
> >
> > PreserveJobHistory?
> >
> 
> Yes, you're right. I shouldn't send out mail after a long shift.. Upps.

Just checking. It seemed like a typo. Try not to work so hard.

> [...]
> 
> > > within the last 86400 seconds, the /var/log/cups/error.log contain the
> > > Error message
> > > "E:[Timpestamp] cups sheduler stops through a program error"
> >
> > I cannot reproduce this. Do you still experience it?
> >
> 
> We still have this behaviour, we tested it either with "1d" for one day and
> also with
> the equivalent "86400" in seconds.
> 
> We tried it via the webinterface, as also by manually modifying
> /etc/cups/cupsd.conf
> and restarting cups with "systemctl restart cups".
> 
> In both cases, the job history is empty and the error_log contain this
> error message.
> 
> [...]
> 
> > From my tests it seems that PreserveJobHistory cannot handle being
> > given any seconds value, small or large. What do you get with 30 for
> > PreserveJobHistory?
> >
> 
> I will test it, but if it work that way, either the implementation is buggy
> or the documentation
> for this option isn't correct... I prefer the first one to be fixed. ;-)
> 
> Edit: I tested "PreserveJobHistory" with several values: 60, 1024, 86400 by
> manually editing /etc/cups/cupsd.conf
> and after each modification, I did a service restart.

I used 'cupsctl PreserveJobHistory=30', but it amounts to the same thing.

> Expecting: JobHistory will listing test print jobs within the specified
> time frame, not listing them after the given time frame exeeds
> 
> What happened: In each case, all job files (*.c, *.d) under /var/spool/cups
> are deleted, even the creation date of the file was not exeeding the tested
> value.
> Instead of originally reported, the error_log contained no error after a
> service restart.
> 
> I did not test also by changing the values via the webinterface.
> 
> PreserveJobHistory seems not handling numeric values as otherwise described
> as possible value in the cupsd.conf(5)-documentation.
> Instead, it handle numeric values like the option value "No" and disable
> the job history completely.

That is more or less the conclusion I came to too. I will forward this
report upstream tomorrow after doing a few more tests.

-- 
Brian.

Bug#923734: Python needs updating: version push

[Matthias Klose]

On 04.03.19 19:37, Brian Holaday wrote:
> Package: python
> Version: 2.7.13-2
> severity: important
> 
> Issue:
> 
> Python 3.7.2 has been released out for some time now. Can we get an update
> pushed out to stretch-backports

no, not doing that.

> or SID at some point?

it's there "for some time now"

Bug#697029: [ilk] using GNOME 3 makes computer sluggish after a few minutes

[Paul Gevers]

Hi,

On Sun, 24 Feb 2013 07:08:14 + Ben Hutchings 
wrote:

> "Graphics rendering may be very slow on Intel 'Ironlake M' GPUs (PCI
> ID 8086:0046) when an IOMMU (VT-d) is enabled.  The IOMMU
> functionality can be disabled for the GPU by adding the kernel
> parameter 'intel_iommu=igfx_off'."

This bug is marked as affecting the release-notes. I don't think this is
still relevant for stretch or buster? If not, I'll like to remove the
"affects", to not clutter the release-notes bug list.

Paul
PS: please CC me, I am not subscribed to this bug.



signature.asc
Description: OpenPGP digital signature

Bug#658759: [kirkwood] squeeze-backports kernel fails to boot on SheevaPlug

[Paul Gevers]

Hi all,

On Fri, 24 Aug 2012 09:44:47 +0100 Ian Campbell  wrote:
> On Fri, 2012-08-24 at 00:31 -0700, Jonathan Nieder wrote:
> > Any ideas for how to word a hint about this for
> > the wheezy release-notes?
> 
> Hrm, how about:
> 
> The version of u-boot shipped from the factory on many
> kirkwood(???) devices, as well as u-boot shipped in versions of
> Debian prior to Wheezy, contain a bug (#658759) which renders
> them unable to boot kernel versions 3.2(???) or newer. This
> includes the kernel in Wheezy.
> 
> Users are advised to upgrade u-boot before upgrading their
> kernel. XXX link to suitable documentation?
> http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html 
> and similar?
> 
> (??? fact needs checking). 

This bug is marked as affecting the release-notes. I don't think this is
relevant for stretch or buster anymore? If not, I'll like to remove the
"affects", to not clutter the release-notes bug list.

Paul
PS: please CC me, I am not subscribed to this bug.



signature.asc
Description: OpenPGP digital signature

Bug#923733: epiphany-browser: GLib-GIO-ERROR **: Settings schema 'org.gnome.Epiphany.web' does not contain a key named 'hardware-acceleration-policy'

[Jason Crain]

On Mon, Mar 04, 2019 at 07:37:22PM +0100, Christoph Anton Mitterer wrote:
> iu  epiphany-browser-data 3.31.91-2

Did something go wrong with the upgrade? That line should probably show
'i' for installed instead of 'u' for, I think, unpacked?

Bug#923623: jobs run from .bash_profile are appended to the wrong sub-tree

[Craig Small]

Hi Dan,

On Sun, 3 Mar 2019 at 11:03, 積丹尼 Dan Jacobson  wrote:

>   |   `-bash /home/jidanni/.xsession
>   |   |-bash /home/jidanni/.xsession
>   |   |   `-sleep 4m
>

The process tree comes from the parent PID.

Can you tell me what the PID and PPID are for the relevant processes?
I think the sleep will have a PPID of that second bash and the second bash
have a PPID of the first, which is how the tree gets formed.

 - Craig

Bug#923688: [keepassxc] KeepassXC not showing in the icon bar

[Nazar Zhuk]

Synthea,

Could you check that the icon is not under "hidden icons" in the tray?
(A small up arrow in the tray.)

If it's there you can make it always visible in System Tray Settings
(right click on the tray).

-- Nazar

Bug#923561: parted: Incorrect optimal alignment for USB device

[Phillip Susi]

On 3/4/2019 11:50 AM, Kevin Locke wrote:
> optimal_io_size is defined in the kernel ABI[1] as "the preferred
> request size for workloads where sustained throughput is desired".  In
> this case, I think it comes from scsi_disk.opt_xfer_blocks[2] which
> comes from the VPD block limits page[3] which my disk reports as 65535
> blocks (according to sg_vpd).

Yes, I was looking over the definition earlier in the kernel
documentation, and it seems to me that part of the definition indicates
it is simply an optimal size to transfer in, and has nothing to do with
alignment.  But parted treats it as having to do with alignment, because
the same kernel documentation mentions that is what the md driver uses
the field for.

> The definition seems reasonable, but it would not surprise me if 65535
> were bogus.  I am not familiar enough with USB+UAS to know if this
> might be an optimal size for the protocols involved.  I can raise the
> issue on linux-scsi/linux-usb.

I think the issue needs raised in a few places; I just couldn't decide
where.

> However, whether or not this is changed in the kernel, I would argue
> it should be handled in parted.  Both to support previous+current
> kernels and because I think the optimal_io_size ABI definition allows
> optimal_io_size which is not a multiple of minimum_io_size for
> transports where that truly is the case.

Unfortunately, that means parted needs to simply ignore the value of
optimal io size as totally meaningless garbage, and I don't much like
the thought of that.  If parted has always been wrong and the intended
meaning of the kernel parameter has never had anything to do with
alignment, then yes, parted needs to ignore it because it read meaning
into it that was never intended.  But if it is supposed to have
something to do with optimal alignment, then md is right and usb is
wrong, and usb needs to be fixed.

Bug#921741: cups: Cups sheduler stops with program error when using JobPreserveHistory

[Emin Kaya]

Hi Brian,

Am Mo., 4. März 2019 um 16:49 Uhr schrieb Brian Potkin <
claremont...@gmail.com>:

> [...]



> > To do this, we found "JobPreserveHistory " as root option in
> > the documentation for /etc/cups/cupsd.conf, which would do the job
> > perfectly.
>
> PreserveJobHistory?
>

Yes, you're right. I shouldn't send out mail after a long shift.. Upps.

[...]

> > within the last 86400 seconds, the /var/log/cups/error.log contain the
> > Error message
> > "E:[Timpestamp] cups sheduler stops through a program error"
>
> I cannot reproduce this. Do you still experience it?
>

We still have this behaviour, we tested it either with "1d" for one day and
also with
the equivalent "86400" in seconds.

We tried it via the webinterface, as also by manually modifying
/etc/cups/cupsd.conf
and restarting cups with "systemctl restart cups".

In both cases, the job history is empty and the error_log contain this
error message.

[...]

> From my tests it seems that PreserveJobHistory cannot handle being
> given any seconds value, small or large. What do you get with 30 for
> PreserveJobHistory?
>

I will test it, but if it work that way, either the implementation is buggy
or the documentation
for this option isn't correct... I prefer the first one to be fixed. ;-)

Edit: I tested "PreserveJobHistory" with several values: 60, 1024, 86400 by
manually editing /etc/cups/cupsd.conf
and after each modification, I did a service restart.

Expecting: JobHistory will listing test print jobs within the specified
time frame, not listing them after the given time frame exeeds

What happened: In each case, all job files (*.c, *.d) under /var/spool/cups
are deleted, even the creation date of the file was not exeeding the tested
value.
Instead of originally reported, the error_log contained no error after a
service restart.

I did not test also by changing the values via the webinterface.

PreserveJobHistory seems not handling numeric values as otherwise described
as possible value in the cupsd.conf(5)-documentation.
Instead, it handle numeric values like the option value "No" and disable
the job history completely.


Kind regards.

Emin Kaya

Bug#923734: Python needs updating: version push

[Brian Holaday]

Package: python
Version: 2.7.13-2
severity: important

Issue:

Python 3.7.2 has been released out for some time now. Can we get an update
pushed out to stretch-backports or SID at some point?

Bug#923733: epiphany-browser: GLib-GIO-ERROR **: Settings schema 'org.gnome.Epiphany.web' does not contain a key named 'hardware-acceleration-policy'

[Christoph Anton Mitterer]

Package: epiphany-browser
Version: 3.31.91-2
Severity: grave
Justification: renders package unusable


Hi.

When starting epiphany it crashes:
$  epiphany

(epiphany:1935): GLib-GIO-ERROR **: 19:35:05.423: Settings schema 
'org.gnome.Epiphany.web' does not contain a key named 
'hardware-acceleration-policy'
Trace/breakpoint trap


Cheers,
Chris.


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

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

Versions of packages epiphany-browser depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.12-1
ii  dbus-x11 [dbus-session-bus]   1.12.12-1
iu  epiphany-browser-data 3.31.91-2
ii  gsettings-desktop-schemas 3.28.1-1
ii  iso-codes 4.2-1
ii  libc6 2.28-7
ii  libcairo2 1.16.0-3
ii  libdazzle-1.0-0   3.30.2-2
ii  libgcr-base-3-1   3.28.1-1
ii  libgcr-ui-3-1 3.28.1-1
ii  libgdk-pixbuf2.0-02.38.0+dfsg-7
it  libglib2.0-0  2.58.3-1
ii  libgmp10  2:6.1.2+dfsg-4
ii  libgtk-3-03.24.5-1
ii  libhogweed4   3.4.1-1
ii  libicu63  63.1-6
ii  libjavascriptcoregtk-4.0-18   2.22.6-1
ii  libjson-glib-1.0-01.4.4-2
ii  libnettle63.4.1-1
ii  libnotify40.7.7-4
ii  libpango-1.0-01.42.4-6
ii  libsecret-1-0 0.18.7-1
ii  libsoup2.4-1  2.64.2-2
iu  libsqlite3-0  3.27.2-1
ii  libwebkit2gtk-4.0-37  2.22.6-1
ii  libxml2   2.9.4+dfsg1-7+b3

Versions of packages epiphany-browser recommends:
ii  ca-certificates  20190110
ii  evince   3.30.2-3
ii  yelp 3.31.90-1

epiphany-browser suggests no packages.

-- no debconf information

Bug#921792: Did you filed a bug for manual testing transition? (Was: log4c: FTBFS (LaTeX error))

[Andreas Tille]

Hi Sergei,

all fine for me - thanks for caring, Andreas.

On Mon, Mar 04, 2019 at 09:09:05PM +0300, Sergei Golovan wrote:
> Hi Andreas,
> 
> On Mon, Mar 4, 2019 at 7:50 PM Andreas Tille  wrote:
> >
> > Hi Sergei,
> >
> > thanks for your upload of log4c and fixing the open bugs.  Since the
> > testing transition will not happen before deep freeze.  So did you
> > followed "Applying for an unblock"[1] and filed a bug report against
> > release.debian.org (I've checked BTS but did not found a bug)?
> 
> Looks like I overlooked something. My upload doesn't fix 921792, I'm afraid.
> The package successfully builds on sid, but not on buster (I've just checked).
> Also, I've checked if the original 1.2.1-3 builds on sid, and it does
> (looks like
> the newer texlive packages fixed it)!
> Another concern is that the diff between 1.2.1-3 and 1.2.4-1 is fairly large.
> I'm not sure it justifies a freeze exception.
> 
> So, as for now I'd do the following:
> 1) reopen the bug
> 2) wait until the texlive enters buster and then close the bug for 1.2.1-3
> (which will cancel the package autoremoval)
> 3) keep 1.2.4-1 for bullseye
> 
> Cheers!
> -- 
> Sergei Golovan
> 

-- 
http://fam-tille.de

Bug#923732: dgit-infrastructure: --deliberately-include-questionable-history required for every single push

[Sean Whitton]

Hello,

On Mon 04 Mar 2019 at 06:03PM +00, Ian Jackson wrote:

> AFAIAA there is no way for dgit-infrastructure or dgit to know whether
> something was dcut or rejected.

Right.

>> Shouldn't --deliberately-include-questionable-history be required only
>> once?  Shouldn't dgit-infrastructure learn that the commits it thinks
>> are tainted aren't actually tainted?
>
> Each time the thing is cut and repushed, presumably there are new
> commits that might be tainted.
>
> Ie,
>push ...A
>cut  now ...A is tainted
>push ...A+B  needs reassurance that A is OK
>cut  now ...B is tainted
>push ...A+B  needs reassurance that A+B is OK
> etc.
>
> Don't you think ?

Once I --deliberately the 1.2-1 upload, and dgit sees that it was
ACCEPTed, can't it safely untaint everything in the 1.2-1 history?

That way, eventually, all commits will be marked as untainted and I
won't have to keep passing the option until the end of time.

If not, I think there needs to be some moderately standard way to
request that the whole current history of a package on dgit-repos be
marked as untainted.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#601203: #601203: tested patch for adding support for recursivly including recommends (NORECOMMENDS=0)

[Holger Levsen]

Hi Steve,

Wolfgang tested a patch for "#601203: tested patch for adding support for
recursivly including recommends" and asked me for review and pushing it
into debian-cd.git.

As I know how busy you are incl. with the shim-signed stuff, I've
decided to push it to a h01ger/601203 branch and not master :)

This patch (or rather these two small patches...) have been proven to work 
using the simple-cdd wrapper for debian-cd to build an ISO image like this:
DISKTYPE=BD NORECOMMENDS=0 build-simple-cdd --dist buster --profiles xfce

where xfce refers to a profile file ./profiles/xfce.packages which has a single
entry, 'task-xfce-desktop'. This causes all recommends to be on the
generated ISO.

If called with NORECOMMENDS=1 (or NORECOMMENDS unset) it works as
expected and doesnt include any recommends on the ISO (just the depends
are there then.).

(A second test has made with the same results using the
education-ltsp-server metapackage instead of xfce.)

We (Debian Edu) really really really would like to see this merged, as else
the maintenance of the Edu BD image will be a PITA as the education-tasks-*
metapackages heavily use recommends (due to the design of the blends-dev
framework).

For convinience I've also attached the patches to this mail.


-- 
tschau,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
From 84878a80ab0f0560e9a55b2d5956c8707fd7b74e Mon Sep 17 00:00:00 2001
From: Wolfgang Schweer 
Date: Fri, 1 Mar 2019 11:27:46 +0100
Subject: [PATCH 1/3] Enable to pull in Recommends recursively

To enable set NORECOMMENDS=0 in the build environment. (Closes: #601203)
---
 tools/sort_deps | 51 +++
 1 file changed, 31 insertions(+), 20 deletions(-)

diff --git a/tools/sort_deps b/tools/sort_deps
index 2bdbfcf..8582b90 100755
--- a/tools/sort_deps
+++ b/tools/sort_deps
@@ -24,7 +24,7 @@ my $extranonfree = read_env('EXTRANONFREE', 0);
 my $force_firmware = read_env('FORCE_FIRMWARE', 0);
 my $local = read_env('LOCAL', 0);
 my $complete = read_env('COMPLETE', 0);
-my $norecommends = read_env('NORECOMMENDS', 1);
+my $norecommends = (defined $ENV{'NORECOMMENDS'} ? $ENV{'NORECOMMENDS'} : 1);
 my $nosuggests = read_env('NOSUGGESTS', 1);
 my $verbose = read_env('VERBOSE', 0);
 my $max_pkg_size = read_env('MAX_PKG_SIZE', 9);
@@ -87,8 +87,8 @@ msg(1, "Include non-free packages: ");
 msg(1, yesno($nonfree)."\n");
 msg(1, "Force inclusion of firmware packages: ");
 msg(1, yesno($force_firmware)."\n");
-msg(1, "Ignore Recommends: ");
-msg(1, yesno($norecommends)."\n");
+msg(1, "Include Recommends: ");
+msg(1, yesno(!$norecommends)."\n");
 msg(1, "Ignore Suggests: ");
 msg(1, yesno($nosuggests)."\n");
 msg(1, "Maximum allowed package size: $max_pkg_size bytes\n");
@@ -647,6 +647,7 @@ sub check_versions {
 # Check if a specific dependency package is installed already
 sub dep_pkg_included {
 	my $p = shift;
+	my $add_rec = shift;
 	my $check_backports = shift;
 	my %d = %$p;
 	my $pn = $d{"Package"};
@@ -741,16 +742,17 @@ sub fix_backport_depends {
 # dependency or any one of an OR array
 sub dep_satisfied {
 my $p = shift;
+my $add_rec = shift;
 my $check_backports = shift;
 
 if ("ARRAY" eq ref $p) {
 	foreach (@{$p}) {
-	if (dep_pkg_included($_, $check_backports)) {
+	if (dep_pkg_included($_, $add_rec, $check_backports)) {
 		return 1;
 	}
 	}
 } elsif ("HASH" eq ref $p) {
-	return dep_pkg_included($p, $check_backports);
+	return dep_pkg_included($p, $add_rec, $check_backports);
 } else {
 }
 return 0;
@@ -864,7 +866,7 @@ sub add_package {
 	}
 	
 	# Get all dependencies (not yet included) of each package
-	my (@dep) = (get_missing ($p, $check_backports));
+	my (@dep) = (get_missing ($p, $add_rec, $check_backports));
 
 	# Stop here if apt failed
 	if (not scalar(@dep)) {
@@ -881,7 +883,7 @@ sub add_package {
 	msg(3, "  \@dep before checklist = " . dump_depend(\@dep) . "\n");
 	
 	# Check if all packages are allowed (fail if one cannot)
-	($ok, $reasons) = check_list (\@dep, 1, $check_backports);
+	($ok, $reasons) = check_list (\@dep, 1, $add_rec, $check_backports);
 	if (not $ok) {
 		msg(2, "Can't add $p ... one of the packages needed has " .
 		   "been refused. Reasons: $reasons\n"); 
@@ -891,12 +893,11 @@ sub add_package {
 	msg(3, "  \@dep after checklist = " . dump_depend(\@dep) . "\n");
 	
 	if ($add_rec) {
-		#TODO: Look for recommends (not yet included !!)
-		add_recommends (\@dep, $p, $check_backports);
+		add_recommends (\@dep, $p, $add_rec, $check_backports);
 		msg(3, "  \@dep after add_recommends = " . dump_depend(\@dep) . "\n");
 		# Check again but doesn't fail if one of the package cannot be
 		# installed, just ignore it (it will be removed from @dep)
-		($ok, $reasons) = check_list (\@dep, 0, 

Bug#906016: transition: gjs built with mozjs60

[Cyril Brulebois]

Hi,

Simon McVittie  (2019-03-02):
> On Tue, 05 Feb 2019 at 10:16:56 +, Simon McVittie wrote:
> > > > * Require task-gnome-desktop to be installable on s390x, but modify
> > > >   meta-gnome3 so that on s390x, gnome-core installs something that is 
> > > > not
> > > >   the full GNOME 3 desktop used on other architectures, for example
> > > >   the GNOME-2-derived gnome-session-flashback
> 
> In the absence of other progress, I've staged this in git. I'll release
> it soon if nobody else in the team gets there first. The resulting
> metapackage appears to be installable on a s390x buster qemu VM with only
> sid as an apt source (so, only able to see the version of gjs in sid that
> we want to migrate, and not the one in buster that we want to supersede).
> 
> On Fri, 08 Feb 2019 at 18:10:01 +0100, Emilio Pozuelo Monfort wrote:
> > My worry if I were to do that is that the installer would still offer to 
> > install
> > GNOME on s390x, and I don't know what would happen if one chose that (I 
> > suppose
> > apt would realise it's uninstallable and give a proper error, but maybe 
> > things
> > would explode).
> > 
> > So if we're going to make task-gnome-desktop uninstallable there, maybe the
> > installer shouldn't offer to install it, and that needs changes somewhere in
> > tasksel or d-i.
> 
> Some questions whose answers I think might be relevant to determining
> how much effort is justifiable here:
> 
> * Do s390x users install with debian-installer?
> * If so, do they install desktop tasks that way?
> * Does GNOME (the desktop, as opposed to individual apps) work on s390x
>   in earlier Debian releases? (If, as I suspect, the answer is "we don't
>   know, nobody has tried it" then that is itself useful information.)

I don't have any answers here. My searching debian-boot@ for “s390x” in
the body and “installation-report” in the subject returned this small
list of bug reports: #575682, #296930, #608407, #694771, #851790,
#859889, #923524 (which you know about…).


Anyway, just to confirm: if one hacks an archive to get gnome-core out
of the amd64's Packages file, tasksel (run from a chroot rather than
from d-i, configured with this hacked repository) still lists the gnome
desktop task as an available option…


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#921792: Did you filed a bug for manual testing transition? (Was: log4c: FTBFS (LaTeX error))

[Sergei Golovan]

Hi Andreas,

On Mon, Mar 4, 2019 at 7:50 PM Andreas Tille  wrote:
>
> Hi Sergei,
>
> thanks for your upload of log4c and fixing the open bugs.  Since the
> testing transition will not happen before deep freeze.  So did you
> followed "Applying for an unblock"[1] and filed a bug report against
> release.debian.org (I've checked BTS but did not found a bug)?

Looks like I overlooked something. My upload doesn't fix 921792, I'm afraid.
The package successfully builds on sid, but not on buster (I've just checked).
Also, I've checked if the original 1.2.1-3 builds on sid, and it does
(looks like
the newer texlive packages fixed it)!
Another concern is that the diff between 1.2.1-3 and 1.2.4-1 is fairly large.
I'm not sure it justifies a freeze exception.

So, as for now I'd do the following:
1) reopen the bug
2) wait until the texlive enters buster and then close the bug for 1.2.1-3
(which will cancel the package autoremoval)
3) keep 1.2.4-1 for bullseye

Cheers!
-- 
Sergei Golovan

Bug#919628: Apply Julia's LLVM patches

[Sylvestre Ledru]

Hello,


Le 28/02/2019 à 03:09, Mo Zhou a écrit :

Hi Sylvestre,

Should I file freeze exception requests against llvm-6.0 and julia,
so that we will have some more time to work on this?


I guess :)

I would appreciate help with fixing the application of the patches on 
llvm-toolchain-6. I am too busy lately to finish in the next couple of 
weeks.


Thanks

S

Bug#923732: dgit-infrastructure: --deliberately-include-questionable-history required for every single push

[Ian Jackson]

Sean Whitton writes ("Bug#923732: dgit-infrastructure: 
--deliberately-include-questionable-history required for every single push"):
> Package: dgit-infrastructure
> Version: 8.4
...
> swayidle was not actually ever rejected from NEW but was instead dcut
> from DEFERRED and uploaded again a few times.

AFAIAA there is no way for dgit-infrastructure or dgit to know whether
something was dcut or rejected.

> Shouldn't --deliberately-include-questionable-history be required only
> once?  Shouldn't dgit-infrastructure learn that the commits it thinks
> are tainted aren't actually tainted?

Each time the thing is cut and repushed, presumably there are new
commits that might be tainted.

Ie,
   push ...A
   cut  now ...A is tainted
   push ...A+B  needs reassurance that A is OK
   cut  now ...B is tainted
   push ...A+B  needs reassurance that A+B is OK
etc.

Don't you think ?

Ian.

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

[Nicolas Braud-Santoni]

On Mon, Feb 18, 2019 at 02:36:07PM -0800, Cameron Norman wrote:
> Control: retitle -1 ITA: json-c -- JSON manipulation library
> 
> I intend to adopt this package.

Hi Cameron !

Thanks for your interest in adopting this package.

FYI, I started a transition for a new version of json-c (0.13.1+dfsg-2), cf:
  #904418
  https://release.debian.org/transitions/html/auto-json-c.html

It is blocked on some reverse dependencies that do not build cleanly with the
new version, but we can get that in after Buster is released.


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#923732: dgit-infrastructure: --deliberately-include-questionable-history required for every single push

[Sean Whitton]

Package: dgit-infrastructure
Version: 8.4

Hello,

swayidle was not actually ever rejected from NEW but was instead dcut
from DEFERRED and uploaded again a few times.

Shouldn't --deliberately-include-questionable-history be required only
once?  Shouldn't dgit-infrastructure learn that the commits it thinks
are tainted aren't actually tainted?

Total 47 (delta 8), reused 19 (delta 0)
remote: gpgv: Signature made Mon 04 Mar 2019 05:36:37 PM UTC
remote: gpgv:using RSA key 
9B917007AE030E36E4FC248B695B7AE4BF066240
remote: gpgv: Good signature from "Sean Whitton "
remote: gpgv: aka "Sean Whitton "
remote: gpgv: aka "Sean Whitton "
remote: gpgv: aka "Sean Whitton "
remote: gpgv: aka "Sean Whitton "
remote: To 
/srv/dgit.debian.org/dispatch-dir/distro=debian/repos/_tmp/swayidle_prospective
remote:  * [new branch]  a719af136406276be15bd51270c2c36cf42575cc -> 
refs/dgit/sid
remote:  * [new tag] e4a96dfac0f651a6f46a2a255dfda3e806c6115a -> 
archive/debian/1.2-2
remote:  * [new tag] a1d2c059f0157a8e307b9202378d7466dd0015ab -> 
debian/1.2-2
remote: To 
/srv/dgit.debian.org/dispatch-dir/distro=debian/repos/_tmp/swayidle_prospective
remote:  * [new branch]  a719af136406276be15bd51270c2c36cf42575cc -> master
remote:
remote: History contains tainted commit 2ddf9061f6aba7ee03c7da1d5dec6a4225c2e77e
remote: Taint recorded at time 2019-02-09 21:39:02 Z for package swayidle
remote: Reason: tag archive/debian/1.2-1 referred to this object in git tree 
but all previously pushed versions were found to have been removed from NEW 
(ie, rejected) (or never arrived)
remote: Could be forced using --deliberately.  Consult documentation.
remote:
remote: Rejecting push due to questionable history.
dgit-repos-server: policy hook failed (or rejected) (256)
remote: dgit-repos-server: policy hook failed (or rejected) (256)
To git+ssh://push.dgit.debian.org/dgit/debian/repos/swayidle.git
 ! [remote rejected] a719af136406276be15bd51270c2c36cf42575cc -> refs/dgit/sid 
(pre-receive hook declined)
 ! [remote rejected] archive/debian/1.2-2 -> archive/debian/1.2-2 (pre-receive 
hook declined)
 ! [remote rejected] debian/1.2-2 -> debian/1.2-2 (pre-receive hook declined)
error: failed to push some refs to 
'git+ssh://d...@push.dgit.debian.org/dgit/debian/repos/swayidle.git'
dgit: failed command: git -c push.followTags=false push 
'git+ssh://d...@push.dgit.debian.org/dgit/debian/repos/swayidle.git' 
a719af136406276be15bd51270c2c36cf42575cc:refs/dgit/sid 
refs/tags/archive/debian/1.2-2 refs/tags/debian/1.2-2

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#887905: Fixed on 2.4.0+

[Gabriel Potter]

Hi,

Please note that this is fixed on 2.4.0+