Bug#912001: ocrmypdf: autopkgtest needs update for new version of tesseract

[Paul Gevers]

Source: ocrmypdf
Version: 6.2.4-1
X-Debbugs-CC: debian...@lists.debian.org, tesser...@packages.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:tesseract

Dear maintainers,

With a recent upload of tesseract the autopkgtest of ocrmypdf fails in
testing when that autopkgtest is run with the binary packages of
tesseract from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
tesseract  from testing4.00~git3241-1066f696-1
ocrmypdf   from testing6.2.4-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems
tesseract change the p into a P in the warning.

Currently this regression is contributing to the delay of the migration
of tesseract to testing [1]. Of course, tesseract shouldn't just break
your autopkgtest (or even worse, your package), but it seems to me that
the change in tesseract was intended and your package needs to update to
the new situation. If needed, please change the bug's severity.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from tesseract should really
add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

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

Paul

[1] https://qa.debian.org/excuses.php?package=tesseract

https://ci.debian.net/data/autopkgtest/testing/amd64/o/ocrmypdf/1209359/log.gz

=== FAILURES
===
_ test_tesseract_config_invalid[hocr]
__

renderer = 'hocr'
resources =
PosixPath('/tmp/autopkgtest-lxc.n8pgwx8u/downtmp/build.pIk/src/tests/resources')
outdir =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_tesseract_config_invalid_0')

@pytest.mark.parametrize('renderer', RENDERERS)
def test_tesseract_config_invalid(renderer, resources, outdir):
cfg_file = outdir / 'test.cfg'
with cfg_file.open('w') as f:
f.write('''\
THIS FILE IS INVALID
''')

p, out, err = run_ocrmypdf(
resources / 'ccitt.pdf', outdir / 'out.pdf',
'--pdf-renderer', renderer,
'--tesseract-config', cfg_file)
>   assert "parameter not found" in err, "No error message"
E   AssertionError: No error message
E   assert 'parameter not found' in 'WARNING -1: [tesseract]
Warning: Parameter not found: THIS\n   INFO - Output file is a PDF/A-2B
(as expected)\n'

tests/test_main.py:737: AssertionError
___ test_tesseract_config_invalid[tesseract]
___

renderer = 'tesseract'
resources =
PosixPath('/tmp/autopkgtest-lxc.n8pgwx8u/downtmp/build.pIk/src/tests/resources')
outdir =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_tesseract_config_invalid_1')

@pytest.mark.parametrize('renderer', RENDERERS)
def test_tesseract_config_invalid(renderer, resources, outdir):
cfg_file = outdir / 'test.cfg'
with cfg_file.open('w') as f:
f.write('''\
THIS FILE IS INVALID
''')

p, out, err = run_ocrmypdf(
resources / 'ccitt.pdf', outdir / 'out.pdf',
'--pdf-renderer', renderer,
'--tesseract-config', cfg_file)
>   assert "parameter not found" in err, "No error message"
E   AssertionError: No error message
E   assert 'parameter not found' in 'WARNING - The argument
--pdf-renderer=tesseract provides support for versions of tesseract
older than your version. F\nWARNING -1: [tesseract] Warning:
Parameter not found: THIS\n   INFO - Output file is a PDF/A-2B (as
expected)\n'

tests/test_main.py:737: AssertionError
___ test_tesseract_config_invalid[sandwich]


renderer = 'sandwich'
resources =
PosixPath('/tmp/autopkgtest-lxc.n8pgwx8u/downtmp/build.pIk/src/tests/resources')
outdir =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_tesseract_config_invalid_2')

@pytest.mark.parametrize('renderer', RENDERERS)
def test_tesseract_config_invalid(renderer, resources, outdir):
cfg_file = outdir / 'test.cfg'
with cfg_file.open('w') as f:
f.write('''\
THIS FILE IS INVALID
''')

p, out, err = run_ocrmypdf(
resources / 'ccitt.pdf', outdir / 'out.pdf',
'--pdf-renderer', renderer,
'--tesseract-config', cfg_file)
>   assert "parameter not found" in err, "No error message"
E   AssertionError: No error message
E   assert 'parameter not found' in 'WARNING -1: [tesseract]
Warning: Parameter not found: THIS\n   INFO - Output file is a PDF/A-2B
(as 

Bug#700576: cowsay: Please add a kangaroo cow

[Paul Hardy]

Control: tags -1 + pending - help

I am going to prepare an NMU to fix this bug using the patch that I
submitted previously.

Thanks,


Paul Hardy

Bug#586709: closed by Thomas Goirand

[Daniel Richard G.]

On Fri, 2018 Oct 26 11:56-0300, Jesse Smith wrote:
>
> It's not documented in the halt manual page because it's not a
> limitation of the halt command. It's a problem with the
> /etc/init.d/halt script. The halt command is working as expected, it's
> the script that is overriding the command line behaviour.

The halt(8) (and poweroff(8)) commands are *not* working as expected, or
else I would not have filed this bug report. You could say that the
frontend program is working correctly, and the backend (init script) is
not, but user expectation is about the whole unit. And a bug in the
backend is still a bug in this package.

> Agreed. I'm just saying this isn't a coding problem with halt, or a
> problem with its documentation. I'm saying that my opinion is that
> this is a problem with the way /etc/default/halt and its corresponding
> script change behaviour vs what the user expects from running halt
> from the command line. Those scripts are doing what they're told to do
> (override halt's command line behaviour).

Bear in mind that there is a distinction between default behavior (e.g.
running halt(8) with no arguments) versus requested behavior ("halt -p").
The config file changes the former, but there is nothing to indicate
that the latter will not be respected.

> It's basically a case of one person telling halt to always stop the
> system (in /etc/default/halt) and another person telling halt to
> poweroff (via the command line). Debian currently is set up so the
> first user "wins". Both settings can't be right, so the implementation
> (as it is now) follows the first user's instruction.

In other words, as it is now, the implementation has a bug.

> It might be possible to change this using various tricks so the second
> user "wins", but that means overriding /etc/default/init

(Did you mean /etc/default/halt?)

Yes, overriding the config file is exactly what is supposed to happen
when the user requests non-default behavior (like "halt -p").

I don't know if you or Thomas intend to fix the implementation, but if
the behavior is going to remain as it is now, then the documentation
needs to be updated to reflect that. This bug isn't as urgent for me now
as it was eight years ago, when I needed proper halt behavior for a UPS-
connected server. But if this bug report is going to be closed, then for
God's sake at least do it right.


--Daniel


-- 
Daniel Richard G. || sk...@iskunk.org
My ASCII-art .sig got a bad case of Times New Roman.

Bug#912000: RM: dh-haskell -- ROM; Not used anymore

[Dmitry Bogatov]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello.

I am maintainer and primary author of dh-haskell package. It was
intended to replace cdbs-based build system of Haskell packages, but,
well, it did not.

I do not plan to work on it anymore, and it serves no purpose. Hence I
request its removal.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEhnHVzDbtdH7ktKj4SBLY3qgmEeYFAlvT6fEACgkQSBLY3qgm
EeaECBAAhR2UR3Nn6BaYgjtrEuW91a/J42kjMXIQu/4Qz3ayZfMwod9un/OkEqVN
oIFlaEHwVOsNAUult7z6wdknvGQx+rwTaAVU/+jA5hwDOf2P51DgXtbDoPc9cq/t
HLSp2u4SDCDGIn8Eh/hcp3UjfqLbxmEoAEDejEaq4Mqd6ccm1ppX6WkK2JlrPEK9
UU5d7CTNKqgk7RetrGgW0VvkrIz5vKfDK6klQhY4lyFmw5AIPSDxsNS6v47bDXvY
/i2xbQwy8jBeiSMjW9T2fb/oQWxACspl0Si2G3zw1m9jtCAqsXkhSy3UoXa+kKdu
/vyi1mZVO8qyVJ8F0KyzPM0GhuTrl9In9bWBtc1xADmxP1KBnCv/XyPDtb44AklP
Us9V+60TvDmDJ+AJ7rpV/IHmH44HB9LaGxS4SjfkeoP0tp4yb9+Zo4oNrs8hOsy7
59iQChEk16tFcRM73phTZvPaGHXX+VpO/CkwXFxrFMvIn0XSvbZbTfg4IJF8kNfH
DbV5TzHF1IkMsHs2r8baZSqc79nm1lWE2nBVBGrN1jH+fjYA4eYRuKqeed2YHR4C
FkqmbIrBa31bfypiGyJ6wSxDNL3JYCRCNWR8cK7FyoaFzJ813grS2TBPHLK+1+8R
5Y80Xb0Jbb5iKcW4JOq9+o9ZJ4aQ4bnXP8TaZQVAqhg5WEDcX34=
=7/+q
-END PGP SIGNATURE-

Bug#911999: Undeclared dependency on tracker

[Ben Hutchings]

Package: nautilus
Version: 3.30.0-4
Severity: serious

If tracker is not installed:

~$ nautilus

(nautilus:23136): Tracker-ERROR **: 05:13:49.548: Unable to find default domain 
ontology rule /usr/share/tracker/domain-ontologies/default.rule
Trace/breakpoint trap

Please either make tracker optional again (which I would prefer)
or move it from Suggests to Depends.

Ben.

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

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

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

Versions of packages nautilus recommends:
ii  gnome-sushi  3.30.0-1
ii  gvfs-backends1.38.0-2
ii  librsvg2-common  2.40.20-3

Versions of packages nautilus suggests:
ii  eog3.28.4-1
ii  evince [pdf-viewer]3.30.1-1
ii  nautilus-extension-brasero 3.12.2-4
ii  nautilus-sendto3.8.6-2
ii  opencubicplayer [mp3-decoder]  1:0.1.21-3
ii  totem  3.26.2-1
ii  tracker2.1.4-1
ii  vlc [mp3-decoder]  3.0.4-3+b2
ii  xdg-user-dirs  0.17-1

-- no debconf information

Bug#911957: [src:rquantlib] FTBFS with boost1.67

[Dirk Eddelbuettel]

Giovanni,

On 26 October 2018 at 17:13, Giovanni Mascellani wrote:
| Package: src:rquantlib
| Version: 0.4.5-1
| Severity: wishlist
| Tags: patch
| User: team+bo...@tracker.debian.org
| Usertags: boost1.67
| 
| Dear Maintainer,
| 
| your package fails to build with boost1.67. You can find a build log
| attached. If you want to attempt the build yourself, an updated version
| of boost-defaults which brings in boost1.67 dependencies can be found
| adding this line to your sources.list file:
| 
|   deb https://people.debian.org/~gio/reprepro unstable main
| 
| This bug has severity whishlist for the moment, but it will raised to RC
| as soon as version 1.67 of Boost is promoted to default.
| 
| More specifically, your package fails building because
| boost::posix_time::minutes and similar calls now require an integral
| argument. The attached patch should fix this issue.

Thanks for that. I shall try that in a chroot or Docker container. I'll take
a look at what upstream does in QuantLib 1.14 -- try probably apply a similar
cast. 

| Please consider applying the attached patch as soon as boost1.67 is made
| default in order to avoid FTBFS.

I should be able to apply it before as well.

Cheers, Dirk
 
| Thanks and all the best, Giovanni.
| -- 
| Giovanni Mascellani 
| Postdoc researcher - Université Libre de Bruxelles
| x[DELETED ATTACHMENT 0001-Fix-build-with-Boost-1.67.patch, text/x-patch]
| x[DELETED ATTACHMENT build-rquantlib.log, text/x-log]
| x[DELETED ATTACHMENT signature.asc, application/pgp-signature]

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

Bug#910964: libprotobuf17 might need Breaks: libprotobuf10

[Pirate Praveen]

On 2018, ഒക്‌ടോബർ 27 2:38:23 AM IST, Adrian Bunk  wrote:
>No, it is not.
>
>I would expect everything that fails during build time to fail the same
>
>way at runtime.
>

Can you reproduce the bug? Once it is built against the correct version, it 
will use that version only.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#911998: linux: Please enable CONFIG_KEY_DH_OPERATIONS

[Sebastian Reichel]

Source: linux
Version: 4.18.8-1
Severity: wishlist

Hi,

The new iwd wireless daemon asks for the following configuration
option:

# journalctl -u iwd
Okt 27 03:33:40 earth systemd[1]: Starting Wireless service...
Okt 27 03:33:40 earth iwd[18336]: No Diffie-Hellman support found, WPS will not 
be available
Okt 27 03:33:40 earth iwd[18336]: The following options are missing in the 
kernel:
Okt 27 03:33:40 earth iwd[18336]: CONFIG_KEY_DH_OPERATIONS
Okt 27 03:33:40 earth iwd[18336]: The following optimized implementations might 
be available:
Okt 27 03:33:40 earth iwd[18336]: Wireless daemon version 0.10
...

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

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

Bug#911911: gir1.2-granite-1.0 bindings nonfunctional

[Ivan Krasilnikov]

Fixing gir files manually as follows fixes the problem on my system, so this 
confirms that the bug is with these packages (libgranite-dev, 
gir1.2-granite-1.0).

$ sed -i -e 's//usr/lib/x86_64-linux-gnu/girepository-1.0/Granite-1.0.typelib

--
Ivan

Bug#838480: One more attempt

[Dmitry Bogatov]

Hello!

I was long time. I again propose to add runit-init as one of
alternatives in Pre-Depends. I did quite a work to make transition
sysvinit -> runit as smooth, as possible.

Right now, it is matter of `apt-get install runit-init' and typing
fearsome `Yes, do as I say!'.


pgpPS0vQm9YMl.pgp
Description: PGP signature

Bug#811377: closed by Dmitry Bogatov (Bug#811377: fixed in sysvinit 2.88dsf-60)

[Axel Beckert]

Hi Dmitry,

Dmitry Bogatov wrote:
> Even if it just removed from Policy, not archives, it would be calamity.

*nod*

> > > I am sorry, if I stepped on someone's toes. I would greatly appericate
> > > any help in maintaining sysvinit.
> > Then you should probably use the common (debian group) repository...
> 
> Somewhy GitLab does not allow me to push into debian/sysvinit, so I
> pushed to my branch.
> 
> Every DD should be able to push in every repo under debian/ namespace,
> right?

Yes, by default all DDs, but only DDs can push to a repo under
/debian/. But in comparison to Alioth, it's easy to add write access
for single guest accounts to a single repo.

If Ian and Benda don't oppose, I'd give Dmitry write access to
/debian/sysvinit/.

> Also, maybe it worth creating separate namespace for 
> sysvinit/startpar/insserv?

Given that this is more restricting write access than a repo under
/debian/ and the past contribution history of Debian's sysvinit
package, I suggest to stay with the /debian/ namespace and add write
access for guest account to non-DD contributors.

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


signature.asc
Description: Digital signature

Bug#911997: git: Apply diff from Ubuntu

[Jeremy Bicha]

Source: git
Version: 1:2.19.1-1
Tags: patch

I believe you were interested before in getting the Debian and Ubuntu
packaging for git in sync so that Ubuntu would automatically sync the
latest stable git release (at least until the Debian Import Freeze
deadline).

Please see my commits at
https://salsa.debian.org/jbicha/git/merge_requests/1 which should make
this possible.

If we're lucky, maybe Ubuntu will promote pcre2 to main this cycle,
but it's probably best not to assume that will happen.

Thanks,
Jeremy Bicha

Bug#911949: [polymake] FTBFS with boost1.67

[David Bremner]

Giovanni Mascellani  writes:

> ---
>  external/permlib/include/permlib/bsgs.h | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/external/permlib/include/permlib/bsgs.h 
> b/external/permlib/include/permlib/bsgs.h
> index 5a78234..3c0ceab 100644
> --- a/external/permlib/include/permlib/bsgs.h
> +++ b/external/permlib/include/permlib/bsgs.h
> @@ -42,6 +42,7 @@
>  #include 
>  #include 
>  #include 
> +#include 
>  
>  #include 
>  

Thanks for the report and the patch. I generally wait for feedback from
polymake upstream (Hi Benjamin!), so please ping again if this becomes
urgent.

d

Bug#906281: lintian: Severity and Certainty of emacsen-common-without-dh-elpa are wrong / false positives despite "Certainty: certain"

[Axel Beckert]

Hi,

David Bremner wrote:
> I fixed the dh_elpa bug #905464 which originally triggered this
> discussion, so from my point of view the lintian warning is OK. Maybe
> Axel can comment if/when he has a chance to try converting tpp dh_elpa
> again? I did a quick and dirty conversion myself, but there could still
> be e.g. documentation issues.

Looks good on a first glance, thanks!

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

Bug#811377: closed by Dmitry Bogatov (Bug#811377: fixed in sysvinit 2.88dsf-60)

[Dmitry Bogatov]

[2018-10-26 23:18] Ben Hutchings 
> > Sysvinit have undecided maintainance status for years, which prevented
> > me from taking actions previously. But now danger is grave and immediate
> > (see recent discussions about removal of sysvinit on debian-devel@), so
> > I took libery to take action right now.
> I don't believe that sysvinit is or was in *immediate* danger of being
> removed.

Even if it just removed from Policy, not archives, it would be calamity.

> > I am sorry, if I stepped on someone's toes. I would greatly appericate
> > any help in maintaining sysvinit.
> Then you should probably use the common (debian group) repository...

Somewhy GitLab does not allow me to push into debian/sysvinit, so I
pushed to my branch.

Every DD should be able to push in every repo under debian/ namespace,
right?

Also, maybe it worth creating separate namespace for sysvinit/startpar/insserv?

Bug#892434: marked as done (scorched3d: Please use 'pkg-config' to find FreeType 2)

[Adrian Bunk]

Control: tags -1 patch

On Tue, Jun 05, 2018 at 12:28:18PM +0100, James Cowgill wrote:
> Control: reopen -1
> 
> Hi,
> 
> On 04/06/18 23:09, Debian Bug Tracking System wrote:
> > Package: scorched3d
> > Followup-For: Bug #892434
> > 
> > 
> > Given the dependency on pkg-config and work in the changelog, I believe
> > this is a false positive for scorched3d. Not exactly sure how to test,
> > but if it FTBFS, then it can be dealt with then.
> 
> The build log states that it used freetype-config to detect freetype:
> > checking for freetype-config... /usr/bin/freetype-config
> > checking for FreeType -- version >= 7.0.1... yes
> 
> The code for this is in acinclude.m4 which has no mentions of pkg-config
> in it.

Fix is attached.

> James

cu
Adrian

-- 

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

Description: Use pkg-config instead of freetype-config
Author: Adrian Bunk 
Bug-Debian: https://bugs.debian.org/892434

--- scorched3d-44+dfsg.orig/configure.ac
+++ scorched3d-44+dfsg/configure.ac
@@ -40,7 +40,7 @@ m4_include([configure-gl.m4])
 m4_include([configure-al.m4])
 m4_include([configure-wx.m4])
 m4_include([configure-ogg.m4])
-m4_include([configure-ft.m4])
+PKG_CHECK_MODULES(FT2, freetype2)
 m4_include([configure-fftw.m4])
 S3D_SUBDIRS="launcher client server"
 else

Bug#911996: libqt5serialport5 version in Debian stable is wrong

[Rudolf Polzer]

Package: libqt5serialport5
Version: 5.7.1 is available, 5.9.x is missing

I run Debian stable and need libqt5serialport5 version 5.9 instead of 
5.7 - other parts of Debian stable do not accept qt5 version lower than 5.9

Bug#892333: Patch

[Hilko Bengen]

Control: tag -1 patch

Hi,

greetings from the BSP in Karlsruhe.

Here's a patch that uses the proper Autoconf mechanism for calling
pkg-config. I have successfully tested building in a clean sid chroot.

Cheers,
-Hilko

From: Hilko Bengen 
Date: Sat, 27 Oct 2018 00:53:35 +0200
Subject: Use pkg-config for freetype

---
 configure.ac | 29 -
 1 file changed, 8 insertions(+), 21 deletions(-)

diff --git a/configure.ac b/configure.ac
index 5cbcc8b..a1b35d6 100644
--- a/configure.ac
+++ b/configure.ac
@@ -48,27 +48,14 @@ AM_CONDITIONAL([X11_UNAVAILABLE], [test x$no_x = xyes])
 AC_FUNC_ALLOCA
 AC_FUNC_MALLOC
 
-# Check for Freetype2 usability.
-AC_CHECK_PROG(HAVE_FREETYPE_CONFIG, freetype-config, yes)
-if test "x$HAVE_FREETYPE_CONFIG" = "xyes"; then
-  FREETYPE_INC=`freetype-config --cflags`
-  CPPFLAGS="$CPPFLAGS $FREETYPE_INC"
-  AC_CHECK_HEADER(ft2build.h, HAVE_FREETYPE=yes,
-  			  HAVE_FREETYPE=no CPPFLAGS=$save_CPPFLAGS)
-  if test "x$HAVE_FREETYPE" = "xyes" ; then
-FREETYPE_LD_FLAGS=`freetype-config --libs`;
-LIBS="$LIBS $FREETYPE_LD_FLAGS"
-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)
+PKG_CHECK_MODULES(
+[FREETYPE],
+[freetype2],
+[
+CFLAGS="$CFLAGS $FREETYPE_CFLAGS"
+LIBS="$LIBS $FREETYPE_LIBS"
+],
+[AC_MSG_ERROR([Can't find Freetype library])])
 
 if test "x$no_x" != "xyes"; then
   X11_XT_XAW_XMU="-lX11 -lXt -lXaw -lXmu"

Bug#906281: lintian: Severity and Certainty of emacsen-common-without-dh-elpa are wrong / false positives despite "Certainty: certain"

[Axel Beckert]

Hi,

David Bremner wrote:
> >> So, what are the next, concrete, steps for Lintian here? I don't
> >> currently see a consensus...?
> >
> > Gentle ping on this folks?
> 
> I fixed the dh_elpa bug #905464 which originally triggered this
> discussion, so from my point of view the lintian warning is OK. Maybe
> Axel can comment if/when he has a chance to try converting tpp dh_elpa
> again? I did a quick and dirty conversion myself, but there could still
> be e.g. documentation issues.

Will check, thanks for the reminder.

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

Bug#911995: icedtea-netx needs Provides: icedtea-netx-common

[Adrian Bunk]

Package: icedtea-netx
Version: 1.7.1-1
Severity: serious

icedtea-web (1.7.1-1) unstable; urgency=medium
...
  * Merged icedtea-netx-common into icedtea-netx (Closes: #798946)
...


This needs Provides: icedtea-netx-common to make the reverse
dependencies installable again.

Bug#811377: closed by Dmitry Bogatov (Bug#811377: fixed in sysvinit 2.88dsf-60)

[Ben Hutchings]

On Fri, 2018-10-26 at 20:55 +, Dmitry Bogatov wrote:
> [2018-10-26 13:58] Ben Hutchings 
> > part 1 text/plain1014
> > On Fri, 2018-10-26 at 10:39 +, Debian Bug Tracking System wrote:
> > > This is an automatic notification regarding your Bug report
> > > which was filed against the wnpp package:
> > > 
> > > #811377: RFA: sysvinit -- System-V-like init utilities - transitional 
> > > package
> > > 
> > > It has been closed by Dmitry Bogatov .
> > Benda created a git repository at 
> > ;.
> 
> My repository is fork of 'debian/sysvinit'. As far as I can tell, the
> following work was done on debian/sysvinit:
> 
>  * import history from alioth up to 2.89-59.10
>  * create (very) incomplete upgrade to 2.90 in branch dgit/experimental

I also committed a bug fix on the dgit/sid branch.

> What I done:
> 
>  * incorporated NMU 2.89-59.11
>  * modernized package a bit
> 
> > You seem to have missed that Ian and Benda already started to adopt
> > sysvinit.  (While they missed closing this bug.)
> 
> Sysvinit have undecided maintainance status for years, which prevented
> me from taking actions previously. But now danger is grave and immediate
> (see recent discussions about removal of sysvinit on debian-devel@), so
> I took libery to take action right now.

I don't believe that sysvinit is or was in *immediate* danger of being
removed.

> I am sorry, if I stepped on someone's toes. I would greatly appericate
> any help in maintaining sysvinit.

Then you should probably use the common (debian group) repository...

Ben.

> Oh, and surely, while I did my best to not introduce any functional
> changes in 2.89-60, brave souls to test upload are more then welcome.
-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
   - Bill Gates




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

Bug#911994: repmgr: postgresql-11-repmgr missing as alternative in the dependencies

[Adrian Bunk]

Package: repmgr
Version: 4.2.0-1
Severity: serious

The following packages have unmet dependencies:
 repmgr : Depends: postgresql-10-repmgr but it is not installable or
   postgresql-9.6-repmgr but it is not installable or
   postgresql-9.5-repmgr but it is not installable or
   postgresql-9.4-repmgr but it is not installable or
   postgresql-9.3-repmgr but it is not installable or
   postgresql-9.2-repmgr but it is not installable or
   postgresql-9.1-repmgr but it is not installable or
   postgresql-9.0-repmgr but it is not installable

Bug#892444: Patch

[Hilko Bengen]

Control: tag -1 patch

Dear maintainer,

greetings from the BSP in Karlsruhe.

Here's a patch for the configure script, teaching it to use pkg-config
for detecting the freetype library.

Cheers,
-Hilko
>From 354ca4e5dcb779ca3e2cd028d8815dbb0513a6bd Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Sat, 27 Oct 2018 00:07:58 +0200
Subject: [PATCH] Add patch to detect freetype2 via pkg-config (Closes:
 #892444)

---
 debian/patches/series |   1 +
 .../patches/use-pkg-config-for-freetype.patch | 106 ++
 2 files changed, 107 insertions(+)
 create mode 100644 debian/patches/use-pkg-config-for-freetype.patch

diff --git a/debian/patches/series b/debian/patches/series
index 0cd2622..ffde4ab 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 fix-silent-compilation.patch
+use-pkg-config-for-freetype.patch
diff --git a/debian/patches/use-pkg-config-for-freetype.patch b/debian/patches/use-pkg-config-for-freetype.patch
new file mode 100644
index 000..d646a42
--- /dev/null
+++ b/debian/patches/use-pkg-config-for-freetype.patch
@@ -0,0 +1,106 @@
+Index: ttfautohint/configure.ac
+===
+--- ttfautohint.orig/configure.ac
 ttfautohint/configure.ac
+@@ -123,96 +123,16 @@ AC_ARG_WITH([doc],
+ [],
+ [with_doc=yes])
+ 
+-AC_ARG_WITH([freetype-config],
+-[AS_HELP_STRING([--with-freetype-config=PROG],
+-[use FreeType configuration program PROG])],
+-[freetype_config=$withval],
+-[freetype_config=yes])
+-
+-if test "$freetype_config" = "yes"; then
+-  AC_PATH_TOOL(ft_config,
+-   freetype-config,
+-   no)
+-  if test "$ft_config" = "no"; then
+-AC_MSG_ERROR([FreeType library is missing; see http://www.freetype.org/])
+-  fi
+-else
+-  ft_config="$freetype_config"
+-fi
+-
+-FREETYPE_CPPFLAGS="`$ft_config --cflags`"
+-FREETYPE_LIBS="`$ft_config --libtool`"
+-
+-# many platforms no longer install .la files for system libraries
+-if test ! -f "$FREETYPE_LIBS"; then
+-  FREETYPE_LIBS="`$ft_config --libs`"
+-fi
++PKG_CHECK_MODULES(
++[FREETYPE],
++[freetype2 >= 2.4.5],
++[FREETYPE_CPPFLAGS="$FREETYPE_CFLAGS"],
++[AC_MSG_ERROR([Can't find Freetype library])])
+ 
+ AC_SUBST([FREETYPE_CPPFLAGS])
+ AC_SUBST([FREETYPE_LIBS])
+ 
+ 
+-AC_MSG_CHECKING([whether FreeType header files are version 2.4.5 or higher])
+-old_CPPFLAGS="$CPPFLAGS"
+-CPPFLAGS=$FREETYPE_CPPFLAGS
+-AC_PREPROC_IFELSE([AC_LANG_SOURCE([[
+-
+-#include 
+-#include FT_FREETYPE_H
+-#if (FREETYPE_MAJOR*1000 + FREETYPE_MINOR)*1000 + FREETYPE_PATCH < 2004005
+-#error Freetype version too low.
+-#endif
+-
+-]])],
+-[AC_MSG_RESULT(yes)
+- CPPFLAGS="$old_CPPFLAGS"],
+-[AC_MSG_ERROR([Need FreeType version 2.4.5 or higher])])
+-
+-
+-AC_MSG_CHECKING([whether FreeType library is version 2.4.5 or higher])
+-old_CPPFLAGS="$CPPFLAGS"
+-CPPFLAGS=$FREETYPE_CPPFLAGS
+-old_LIBS="$LIBS"
+-LIBS=$FREETYPE_LIBS
+-AC_LANG_PUSH([LTLIZED C])
+-AC_RUN_IFELSE([AC_LANG_SOURCE([[
+-
+-#include 
+-#include 
+-#include FT_FREETYPE_H
+-
+-int
+-main()
+-{
+-  FT_Error error;
+-  FT_Library library;
+-  FT_Int major, minor, patch;
+-
+-  error = FT_Init_FreeType();
+-  if (error)
+-  {
+-printf("(test program reports error code %d)... ", error);
+-exit(EXIT_FAILURE);
+-  }
+-
+-  FT_Library_Version(library, , , );
+-
+-  printf("(found %d.%d.%d)... ", major, minor, patch);
+-
+-  if (((major*1000 + minor)*1000 + patch) >= 2004005)
+-exit(EXIT_SUCCESS);
+-  exit(EXIT_FAILURE);
+-}
+-
+-]])],
+-[AC_MSG_RESULT(yes)
+- CPPFLAGS="$old_CPPFLAGS"
+- LIBS="$old_LIBS"],
+-[AC_MSG_ERROR([Need FreeType version 2.4.5 or higher])],
+-[AC_MSG_RESULT([skipped due to cross-compilation])])
+-AC_LANG_POP
+-
+-
+ if test $cross_compiling = no; then
+   AM_MISSING_PROG(HELP2MAN, help2man)
+ else
-- 
2.19.1

Bug#911993: structure-synth FTBFS on armel/armhf: error: glVertex3f was not declared in this scope

[Adrian Bunk]

Source: structure-synth
Version: 1.5.0-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=structure-synth=sid

...
In file included from 
StructureSynth/GUI/../../SyntopiaCore/GLEngine/EngineWidget.h:12,
 from StructureSynth/GUI/MainWindow.h:8,
 from Main.cpp:3:
StructureSynth/GUI/../../SyntopiaCore/GLEngine/Object3D.h: In member function 
'void SyntopiaCore::GLEngine::Object3D::vertex(SyntopiaCore::Math::Vector3f) 
const':
StructureSynth/GUI/../../SyntopiaCore/GLEngine/Object3D.h:70:56: error: 
'glVertex3f' was not declared in this scope
void vertex(SyntopiaCore::Math::Vector3f v) const { glVertex3f(v.x(), 
v.y(), v.z()); }
^~
StructureSynth/GUI/../../SyntopiaCore/GLEngine/Object3D.h:70:56: note: 
suggested alternative: 'vertex3n'
void vertex(SyntopiaCore::Math::Vector3f v) const { glVertex3f(v.x(), 
v.y(), v.z()); }
^~
vertex3n
StructureSynth/GUI/../../SyntopiaCore/GLEngine/Object3D.h: In member function 
'void SyntopiaCore::GLEngine::Object3D::normal(SyntopiaCore::Math::Vector3f) 
const':
StructureSynth/GUI/../../SyntopiaCore/GLEngine/Object3D.h:71:56: error: 
'glNormal3f' was not declared in this scope
void normal(SyntopiaCore::Math::Vector3f v) const { glNormal3f(v.x(), 
v.y(), v.z()); }
^~
StructureSynth/GUI/../../SyntopiaCore/GLEngine/Object3D.h:71:56: note: 
suggested alternative: 'normal'
void normal(SyntopiaCore::Math::Vector3f v) const { glNormal3f(v.x(), 
v.y(), v.z()); }
^~
normal
make[1]: *** [Makefile:756: Main.o] Error 1


The root cause is that on armel/armhf (and arm64 in Ubuntu)
Qt5 is compiled with OpenGL ES instead of OpenGL.

Ideally structure-synth should be fixed to build and work with OpenGL ES,
but if this is not easily possible please
- change the build dependency from libqt5opengl5-dev
  to libqt5opengl5-desktop-dev (which will stop trying
  to build structure-synth on armel/aarmhf), and
- file a removal bug for the old armel+armhf binaries
  of structure-synth against ftp.debian.org

Bug#906438: nsd initscript improve stop action

[harald]

Hi Daniel,

you're right, it should work without the nsd-control - it seems the problem is 
the missing defintion of PIDFILE - adding the following line to the init script 
makes nsd terminate instantly:

PIDFILE=$(nsd-checkconf -o pidfile /etc/nsd/nsd.conf)

Without PIDFILE the TERM signal doesn't reach nsd and the KILL signal finally 
kills the daemon.

Kind regards
Harald Jenny

Bug#619757: Bug #619757 breaks DVD reading by default now

[Pali Rohár]

On Thursday 25 October 2018 22:47:15 Anthony DeRobertis wrote:
> I just finally managed to figure out why DVDs were not working on my machine
> after a few hours of banging my head against a wall and ultimately grabbing
> another drive... Turns out it was because of this bug. Except I never
> explicitly enabled this; it now happens by default via
> /lib/udev/rules.d/80-pktsetup.rules.
> 
> # blockdev --getsize64 /dev/sr0
> 3847454720
> # pktsetup -d 252:0
> # blockdev --getsize64 /dev/sr0
> 7235895296
> 
> ... yeah, works a lot better after that!

Hi! This sounds like a kernel bug.

Can you provide dmesg output and kernel version?

Also can you reproduce it with different DVD discs or with different DVD
drive?

-- 
Pali Rohár
pali.ro...@gmail.com


signature.asc
Description: PGP signature

Bug#911925: Latest OpenJDK breaks various builds

[Erich Schubert]

severity 911925 grave
thanks

Grave because this causes odd errors in various Java compilation tasks, 
and possibly in some Java applications, to make sure this version 
doesn't easily enter testing.



Apparently this upload causes various build problems in particular with 
Maven (surefire) but also ant.


Here is an ant error when trying to "ant compile" UMLgraph: 
https://github.com/dspinellis/UMLGraph

---

compile:
    [javac] Compiling 20 source files to 
/home/erich/workspace/UMLGraph/build
    [javac] 
/home/erich/workspace/UMLGraph/src/main/java/org/umlgraph/doclet/ClassGraph.java:323: 
error: cannot access ClassDoc
    [javac]         optionProvider.getOptionsFor(c instanceof ClassDoc 
? (ClassDoc) c : c.containingClass()) //

    [javac]           ^
    [javac]   class file for ClassDoc not found

---

Now tools.jar is on the classpath, it seems to be in the package (but 
possibly the binary is broken?)


With maven, I get a different failure:

---

[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ umlgraph ---
[INFO] Surefire report directory: 
/home/erich/workspace/UMLGraph/target/surefire-reports


---
 T E S T S
---
Error: Could not find or load main class 
org.apache.maven.surefire.booter.ForkedBooter


[...]

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test 
(default-test) on project umlgraph: Execution default-test of goal 
org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The 
forked VM terminated without saying properly goodbye. VM crash or 
System.exit called ? -> [Help 1]


---

The same surefire problem was also reported here: 
https://stackoverflow.com/questions/53010200/maven-surefire-could-not-find-forkedbooter-class/53016532#53016532


On other systems, the package builds fine, including on Travis CI.


It seems this only affects certain (system?) class loader scenarios - 
surefire adds a jar, and the ant build needs the tools.jar.


My guess is that the backport of the security fixes didn't completely 
work...


Regards,
Erich

Bug#911992: stretch-pu: package spice-gtk/0.33-3.3+deb9u1

[Salvatore Bonaccorso]

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

Hi

spice-gtk is affected by the CVE-2018-10873 issue, as well tracked in
the Debian BTS as #906316. Whilst for src:spice itself we released a
DSA, for spice-gtk this does not warrant a DSA (the issue would be
other way around so a malicious spice server triggering the issue in
the client).

Basic smoke test was performed with the resulting package, but not
specifically tried to trigger the issue.

The changelog reads as

+spice-gtk (0.33-3.3+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix flexible array buffer overflow (CVE-2018-10873) (Closes: #906316)
+
+ -- Salvatore Bonaccorso   Fri, 26 Oct 2018 17:52:24 +0200

Full debdiff attached.

Thanks for considering including the update in the next stretch point
release.

Regards,
Salvatore
diff -Nru spice-gtk-0.33/debian/changelog spice-gtk-0.33/debian/changelog
--- spice-gtk-0.33/debian/changelog 2017-01-14 12:34:36.0 +0100
+++ spice-gtk-0.33/debian/changelog 2018-10-26 17:52:24.0 +0200
@@ -1,3 +1,10 @@
+spice-gtk (0.33-3.3+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix flexible array buffer overflow (CVE-2018-10873) (Closes: #906316)
+
+ -- Salvatore Bonaccorso   Fri, 26 Oct 2018 17:52:24 +0200
+
 spice-gtk (0.33-3.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru 
spice-gtk-0.33/debian/patches/Fix-flexible-array-buffer-overflow.patch 
spice-gtk-0.33/debian/patches/Fix-flexible-array-buffer-overflow.patch
--- spice-gtk-0.33/debian/patches/Fix-flexible-array-buffer-overflow.patch  
1970-01-01 01:00:00.0 +0100
+++ spice-gtk-0.33/debian/patches/Fix-flexible-array-buffer-overflow.patch  
2018-10-26 17:52:24.0 +0200
@@ -0,0 +1,68 @@
+From: Frediano Ziglio 
+Date: Fri, 18 May 2018 11:41:57 +0100
+Subject: Fix flexible array buffer overflow
+Origin: 
https://gitlab.freedesktop.org/spice/spice-common/commit/bb15d4815ab586b4c4a20f4a565970a44824c42c
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-10873
+Bug-Debian: https://bugs.debian.org/906316
+
+This is kind of a DoS, possibly flexible array in the protocol
+causes the network size check to be ignored due to integer overflows.
+
+The size of flexible array is computed as (message_end - position),
+then this size is added to the number of bytes before the array and
+this number is used to check if we overflow initial message.
+
+An example is:
+
+message {
+uint32 dummy[2];
+uint8 data[] @end;
+} LenMessage;
+
+which generated this (simplified remove useless code) code:
+
+{ /* data */
+data__nelements = message_end - (start + 8);
+
+data__nw_size = data__nelements;
+}
+
+nw_size = 8 + data__nw_size;
+
+/* Check if message fits in reported side */
+if (nw_size > (uintptr_t) (message_end - start)) {
+return NULL;
+}
+
+Following code:
+- data__nelements == message_end - (start + 8)
+- data__nw_size == data__nelements == message_end - (start + 8)
+- nw_size == 8 + data__nw_size == 8 + message_end - (start + 8) ==
+  8 + message_end - start - 8 == message_end -start
+- the check for overflow is (nw_size > (message_end - start)) but
+  nw_size == message_end - start so the check is doing
+  ((message_end - start) > (message_end - start)) which is always false.
+
+If message_end - start < 8 then data__nelements (number of element
+on the array above) computation generate an integer underflow that
+later create a buffer overflow.
+
+Add a check to make sure that the array starts before the message ends
+to avoid the overflow.
+
+Signed-off-by: Frediano Ziglio 
+Signed-off-by: Christophe Fergeau 
+[Salvatore Bonaccorso: Drop generated diff from commit messages causing
+ problem when applying with quilt. Remove addition to testsuite]
+---
+
+--- a/spice-common/python_modules/demarshal.py
 b/spice-common/python_modules/demarshal.py
+@@ -318,6 +318,7 @@ def write_validate_array_item(writer, co
+ writer.assign(nelements, array.size)
+ elif array.is_remaining_length():
+ if element_type.is_fixed_nw_size():
++writer.error_check("%s > message_end" % item.get_position())
+ if element_type.get_fixed_nw_size() == 1:
+ writer.assign(nelements, "message_end - %s" % 
item.get_position())
+ else:
diff -Nru spice-gtk-0.33/debian/patches/series 
spice-gtk-0.33/debian/patches/series
--- spice-gtk-0.33/debian/patches/series2017-01-14 12:34:36.0 
+0100
+++ spice-gtk-0.33/debian/patches/series2018-10-26 17:52:24.0 
+0200
@@ -3,3 +3,4 @@
 ssl-Stop-creating-our-own-X509_LOOKUP_METHOD.patch
 ssl-Rework-our-custom-BIO-type.patch
 ssl-Use-accessors-rather-than-direct-struct-access.patch
+Fix-flexible-array-buffer-overflow.patch

Bug#880245: New version of statsmodels is out possibly fixing important bug - any volunteer

[Andreas Tille]

Hi Yaroslav,

On Fri, Oct 26, 2018 at 08:59:57AM -0400, Yaroslav Halchenko wrote:
> 
> > I guess this went out of your focus.  I tried my best to update Git[1] to
> > version 0.9.0.  The package build process stumbles about doc creation:
> 
> THANKS!

You (and all other Uploaders) are welcome.
 
> > #../tools/examples_rst.py
> > ../tools/fold_toc.py build/html/index.html
> > Traceback (most recent call last):
> >   File "../tools/fold_toc.py", line 12, in 
> > doc = open(filename, encoding='utf8').read()
> 
> so the script now is python3. adjust shebang?

Only adjusting shebang is not sufficient.  The file tools/fold_toc.py
is definitely Python2.  I tried:

$ 2to3 -w fold_toc.py 
RefactoringTool: Skipping optional fixer: buffer
RefactoringTool: Skipping optional fixer: idioms
RefactoringTool: Skipping optional fixer: set_literal
RefactoringTool: Skipping optional fixer: ws_comma
RefactoringTool: No changes to fold_toc.py
RefactoringTool: Files that need to be modified:
RefactoringTool: fold_toc.py


But for whatever reason it is not changed automatically.  Am I missing
something?


> alternative might work to patch it with smth like
> 
>   from io import open

I have not tried this yet.

Any further hint (preferably somebody else taking over)?

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#911991: python-phonenumbers: New upstream version (8.9.16) available

[Nelson A. de Oliveira]

Source: python-phonenumbers
Version: 8.9.10-1
Severity: wishlist

Hi,

If possible, it would be good to update the package to the latest
version available (8.9.16 -
https://github.com/daviddrysdale/python-phonenumbers/releases)

Thank you!

Best regards,
Nelson

Bug#911988: reintroduce fixed python2 package for rdepends

[Julian Taylor]

tags 911988 + patch
thanks

Ops I forgot to adapt a runtime check, attached a fixed debdiff
diff --git a/debian/changelog b/debian/changelog
index f266461..a94e1bb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+txtorcon (18.0.2-3) unstable; urgency=medium
+
+  * reintroduce fixed Python 2 package needed by reverse dependencies
+do not install python3 files to avoid failure during installation
+add fix-controller-py3check.patch to correct the python3 runtime check
+Closes: #911271
+
+ -- Julian Taylor   Fri, 26 Oct 2018 22:30:43 
+0200
+
 txtorcon (18.0.2-2) unstable; urgency=medium
 
   * No longer builds a Python 2 package (Closes: #905253)
diff --git a/debian/control b/debian/control
index 0eac5fa..a20741c 100644
--- a/debian/control
+++ b/debian/control
@@ -8,6 +8,14 @@ Build-Depends: debhelper (>= 9),
dh-python,
graphviz,
lsof,
+   python-all,
+   python-geoip,
+   python-ipaddress,
+   python-mock,
+   python-repoze.sphinx.autointerface,
+   python-setuptools,
+   python-sphinx,
+   python-twisted,
python3-all,
python3-geoip,
python3-mock,
@@ -21,6 +29,29 @@ Vcs-Browser: 
https://salsa.debian.org/pkg-privacy-team/txtorcon
 Vcs-Git: https://salsa.debian.org/pkg-privacy-team/txtorcon.git
 Homepage: https://github.com/meejah/txtorcon
 
+Package: python-txtorcon
+Architecture: all
+Depends: python-geoip,
+ python-ipaddress,
+ python-twisted,
+ python-zope.interface,
+ ${misc:Depends},
+ ${python:Depends}
+Suggests: tor
+Provides: ${python:Provides}
+Description: Twisted-based asynchronous Tor control protocol implementation 
(Python 2)
+ txtorcon main feature is to present an asynchronous API to speak the Tor
+ client protocol in Python. It also provides abstractions to track and get
+ updates about Tor's state and current configuration (including writing it to
+ Tor or disk), along with helpers to asynchronously launch slave instances of
+ Tor including Twisted endpoint support.
+ .
+ Twisted is an event-driven networking engine written in Python and Tor is an
+ onion-routing network designed to improve people's privacy and anonymity on 
the
+ Internet.
+ .
+ This package contains the Python 2 module.
+
 Package: python3-txtorcon
 Architecture: all
 Depends: python3-geoip,
diff --git a/debian/patches/fix-controller-py3check.patch 
b/debian/patches/fix-controller-py3check.patch
new file mode 100644
index 000..3e38df3
--- /dev/null
+++ b/debian/patches/fix-controller-py3check.patch
@@ -0,0 +1,20 @@
+Description: adapt python3 check for missing file
+Author: Julian Taylor 
+
+The file is not installed in python2 to avoid pycompile trying to compile it
+with python2.
+For this the runtime check needs to be adapted.
+
+Index: txtorcon/txtorcon/controller.py
+===
+--- txtorcon.orig/txtorcon/controller.py
 txtorcon/txtorcon/controller.py
+@@ -42,7 +42,7 @@ from .interface import ITor
+ try:
+ from .controller_py3 import _AsyncOnionAuthContext
+ HAVE_ASYNC = True
+-except SyntaxError:
++except Exception:
+ HAVE_ASYNC = False
+ 
+ if sys.platform in ('linux', 'linux2', 'darwin'):
diff --git a/debian/patches/series b/debian/patches/series
index ed80250..6bfd16d 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
+fix-controller-py3check.patch
 disable_test_for_invalid_geoip.patch
 remove-privacy-infringing-buttons.patch
 remove-privacy-infringing-JS.patch
diff --git a/debian/rules b/debian/rules
index a334f92..aa0b193 100755
--- a/debian/rules
+++ b/debian/rules
@@ -3,7 +3,7 @@
 export PYBUILD_NAME=txtorcon
 
 %:
-   dh $@ --with=python3,sphinxdoc --buildsystem=pybuild
+   dh $@ --with=python2,python3,sphinxdoc --buildsystem=pybuild
 
 override_dh_auto_build:
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ 
docs/_build/html # HTML generator
@@ -11,17 +11,28 @@ override_dh_auto_build:
 
 override_dh_auto_install:
dh_auto_install -O--buildsystem=pybuild
+   # don't install py3 files in py2 as they don't compile during 
installation
+   find debian/python-txtorcon/ -name controller_py3.py -delete
+   mkdir -p debian/python-txtorcon/usr/share/doc/python-txtorcon
mkdir -p debian/python3-txtorcon/usr/share/doc/python3-txtorcon
set -e && \
+   for data_src in README.rst TODO examples; do \
+   mv debian/python-txtorcon/usr/share/txtorcon/$$data_src \
+   debian/python-txtorcon/usr/share/doc/python-txtorcon; \
+   done
+   set -e && \
for data_src in README.rst TODO examples; do \
mv debian/python3-txtorcon/usr/share/txtorcon/$$data_src \

Bug#911271: txtorcon patch submitted

[Julian Taylor]

I have submitted a patch to reintroduce the patch in txtorcon:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911988

Bug#893864: xiphos webkitgtk dependency fixed

[Jeremy Bicha]

> A new version of Xiphos was uploaded to Debian just now.
> It no longer depends on libwebkitgtk.

Sorry, it's a hard dependency and now xiphos fails to build in a clean
build environment.

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

By the way, please CC me on bug email like this if you want me to see
it. The BTS doesn't CC the bug reporter or commenters by default and I
think it's a hassle subscribing to all the bugs I file.

Thanks,
Jeremy Bicha

Bug#887602: dia: Detect freetype via pkg-config

[Christoph Biedl]

Control: tags 887602 patch

Hugh McMaster wrote...

> The next version of libfreetype6-dev will *not* ship the 'freetype-config'
> script.
> 
> Please use pkg-config to detect the freetype headers and libraries instead.

The patch attached, taken from Hilko Bengen's fix for otf2bdf, make
configure pass.

However, this unveils a segmentation fault in the test suite:

I: make  check-local
I: make[4]: Entering directory '/<>/dia-0.97.3+git20160930/tests'
I: ../app/run_dia.sh ../samples/render-test.dia --export=rt.shape && \
I: xmllint --dtdvalid ../doc/shape.dtd rt.shape && rm rt.shape && rm rt.png
I: /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: 
could not open display
I:   warnings.warn(str(e), _gtk.Warning)
I: sys:1: GtkWarning: IA__gdk_pango_context_get_for_screen: assertion 
'GDK_IS_SCREEN (screen)' failed
I: sys:1: PangoWarning: pango_context_set_language: assertion 'context != NULL' 
failed
I: sys:1: Warning: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
I: sys:1: GtkWarning: IA__gdk_screen_get_root_window: assertion 'GDK_IS_SCREEN 
(screen)' failed
I: sys:1: GtkWarning: IA__gdk_drawable_get_depth: assertion 'GDK_IS_DRAWABLE 
(drawable)' failed
I: ../app/run_dia.sh: line 24: 623075 Segmentation fault  
"$DIA_APP_PATH/dia" "$@"

Greetings from the Karlsruhe BSP,

Christoph
--- a/configure.ac
+++ b/configure.ac
@@ -83,34 +83,14 @@
 if test "$have_pangoft2" = "true"; then
   dnl On Solaris with Forte C, at least, need to link app/dia with -lfreetype.
   dnl It's not enough that -lpangoft2 implicitly pulls it in.
-  have_freetype=false
-  AC_CHECK_LIB(freetype,FT_Init_FreeType,have_freetype=true,have_freetype=false,`freetype-config --libs`)
-  if test "$have_freetype" = "true"; then
-dnl Need 2.0.9, as a bug was fixed for us there.
-dnl However, freetype-config doesn't give a meaningful version, so we must
-dnl do it like this.
-AC_MSG_CHECKING([if FreeType version is 2.0.9 or higher])
-old_CPPFLAGS="$CPPFLAGS"
-CPPFLAGS="$CPPFLAGS `freetype-config --cflags`"
-AC_TRY_CPP([#include 
-#include FT_FREETYPE_H
-#if (FREETYPE_MAJOR*1000+FREETYPE_MINOR)*1000+FREETYPE_PATCH < 209
-#error Freetype version too low.
-#endif
-],
-[AC_MSG_RESULT(yes)
-	 FREETYPE_LIBS=`freetype-config --libs`
-	 AC_SUBST(FREETYPE_LIBS)
-	 FREETYPE_CFLAGS=`freetype-config --cflags`
-	 AC_SUBST(FREETYPE_CFLAGS)
-	 GTK_MODULES="$GTK_MODULES pangoft2"
-	 AC_DEFINE(HAVE_FREETYPE,1,[Define if you have the FreeType2 library])]
-,
-	[AC_MSG_ERROR([Need FreeType library version 2.0.9 or higher])])
-CPPFLAGS="$old_CPPFLAGS"
-  else
-AC_MSG_ERROR(Can't find FreeType library)
-  fi
+  PKG_CHECK_MODULES(
+[FREETYPE],
+[freetype2],
+[
+CFLAGS="$CFLAGS $FREETYPE_CFLAGS"
+LIBS="$LIBS $FREETYPE_LIBS"
+],
+[AC_MSG_ERROR([Can't find Freetype library])])
 else
   AC_MSG_ERROR(Can't find PangoFT2 library)
 fi


signature.asc
Description: PGP signature

Bug#892336: Patch, Non-maintainer upload

[Hilko Bengen]

Control: tag -1 patch

Dear maintainer,

greetings from the BSP currently taking place in Karlsruhe.

Here's a patch that fixes the configure script to make use of pkg-config
to detect freetype2. Because I could not be bothered to find out how to
use dh-autoreconf with old Debhelper-based debian/rules, I took the
liberty to clean up debian/rules and bump the DH compat level...

I have uploaded the resulting package to DELAYED/15; feel free to
reschedule or cancel my upload as you see fit.

Cheers,
-Hilko
diff -Nru otf2bdf-3.1/debian/changelog otf2bdf-3.1/debian/changelog
--- otf2bdf-3.1/debian/changelog	2017-10-24 10:40:21.0 +0200
+++ otf2bdf-3.1/debian/changelog	2018-10-26 22:55:05.0 +0200
@@ -1,3 +1,10 @@
+otf2bdf (3.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Detect freetype2 via pkg-config, modernize package (Closes: #892336)
+
+ -- Hilko Bengen   Fri, 26 Oct 2018 22:55:05 +0200
+
 otf2bdf (3.1-4) unstable; urgency=medium
 
   * Upgraded Standards-Version from 3.9.3 to 4.1.1
diff -Nru otf2bdf-3.1/debian/compat otf2bdf-3.1/debian/compat
--- otf2bdf-3.1/debian/compat	2012-11-30 14:20:41.0 +0100
+++ otf2bdf-3.1/debian/compat	2018-10-26 22:36:05.0 +0200
@@ -1 +1 @@
-9
+10
diff -Nru otf2bdf-3.1/debian/control otf2bdf-3.1/debian/control
--- otf2bdf-3.1/debian/control	2017-10-24 10:40:21.0 +0200
+++ otf2bdf-3.1/debian/control	2018-10-26 22:36:02.0 +0200
@@ -2,8 +2,9 @@
 Section: utils
 Priority: optional
 Maintainer: Miriam Ruiz 
-Build-Depends: debhelper (>= 9), quilt, autotools-dev,
- zlib1g-dev, libfreetype6-dev
+Build-Depends: debhelper (>= 10), quilt, autotools-dev,
+ zlib1g-dev, libfreetype6-dev,
+ pkg-config,
 Standards-Version: 4.1.1
 Homepage: http://www.math.nmsu.edu/~mleisher/Software/otf2bdf/
 
diff -Nru otf2bdf-3.1/debian/patches/freetype2.patch otf2bdf-3.1/debian/patches/freetype2.patch
--- otf2bdf-3.1/debian/patches/freetype2.patch	1970-01-01 01:00:00.0 +0100
+++ otf2bdf-3.1/debian/patches/freetype2.patch	2018-10-26 22:43:23.0 +0200
@@ -0,0 +1,26 @@
+Index: otf2bdf/configure.in
+===
+--- otf2bdf.orig/configure.in
 otf2bdf/configure.in
+@@ -3,12 +3,16 @@ dnl Process this file with autoconf to p
+ AC_INIT(otf2bdf.c)
+ 
+ AC_PROG_CC
++PKG_PROG_PKG_CONFIG
+ 
+-OLDLIBS=$LIBS
+-LIBS="$LIBS `freetype-config --libs`"
+-CPPFLAGS="$CPPFLAGS `freetype-config --cflags`"
+-AC_CHECK_LIB(freetype, FT_Init_FreeType, LIBS="$LIBS -lfreetype",[
+- AC_MSG_ERROR([Can't find Freetype library! Compile FreeType first.])])
++PKG_CHECK_MODULES(
++	[FREETYPE],
++	[freetype2],
++	[
++		CFLAGS="$CFLAGS $FREETYPE_CFLAGS"
++		LIBS="$LIBS $FREETYPE_LIBS"
++	],
++	[AC_MSG_ERROR([Can't find Freetype library])])
+ AC_SUBST(LIBS)
+ 
+ dnl get Compiler flags right.
diff -Nru otf2bdf-3.1/debian/patches/series otf2bdf-3.1/debian/patches/series
--- otf2bdf-3.1/debian/patches/series	2017-10-24 10:40:21.0 +0200
+++ otf2bdf-3.1/debian/patches/series	2018-10-26 22:17:06.0 +0200
@@ -1,2 +1,3 @@
 mkinstalldirs.patch
 args.patch
+freetype2.patch
diff -Nru otf2bdf-3.1/debian/rules otf2bdf-3.1/debian/rules
--- otf2bdf-3.1/debian/rules	2012-11-30 14:22:48.0 +0100
+++ otf2bdf-3.1/debian/rules	2018-10-26 22:47:45.0 +0200
@@ -3,85 +3,10 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS)
-CFLAGS:=$(shell dpkg-buildflags --get CFLAGS)
-CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS)
-LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS)
-LDFLAGS2:=-Wl,-z,defs  -Wl,-as-needed -Wl,--no-undefined
-
-config.status: configure
-	dh_testdir
-	[ ! -d debian/patches ] || $(MAKE) -f /usr/share/quilt/quilt.make patch
-	[ ! -d debian/pixmaps ] || { cd debian/pixmaps && for i in *.sng; do sng "$$i"; done; }
-
-ifneq "$(wildcard /usr/share/misc/config.sub)" ""
-	cp -f /usr/share/misc/config.sub config.sub
-endif
-ifneq "$(wildcard /usr/share/misc/config.guess)" ""
-	cp -f /usr/share/misc/config.guess config.guess
-endif
-
-	./configure \
-		--prefix=/usr \
-		--mandir=\$${prefix}/share/man \
-		--infodir=\$${prefix}/share/info \
-		CFLAGS="$(CFLAGS) $(CPPFLAGS)" \
-		CXXFLAGS="$(CXXFLAGS) $(CPPFLAGS)" \
-		LDFLAGS="$(LDFLAGS) $(LDFLAGS2)"
-
-build-stamp:  config.status
-	dh_testdir
-	$(MAKE)
-	touch $@
-
-build-indep: build-stamp
-
-build-arch: build-stamp
-
-build: build-arch build-indep
-
-clean:
-	dh_testdir
-	dh_testroot
-	rm -f build-stamp 
-	[ ! -f Makefile ] || $(MAKE) distclean
-	rm -rf config.sub config.guess config.status config.log config.cache
-	[ ! -d debian/patches ] || $(MAKE) -f /usr/share/quilt/quilt.make unpatch
-	[ ! -d debian/pixmaps ] || rm -vf debian/pixmaps/*.png
-	dh_clean 
-
-install: build
-	dh_testdir
-	dh_testroot
-	dh_prep
-	dh_installdirs
-	$(MAKE) \
-		prefix=$(CURDIR)/debian/otf2bdf/usr \
+override_dh_auto_install:
+	dh_auto_install -- \
 		MKINSTALLDIRS="mkdir -p" \
-		

Bug#910964: libprotobuf17 might need Breaks: libprotobuf10

[Adrian Bunk]

Control: severity -1 serious
Control: retitle -1 libprotobuf17 needs Breaks: libprotobuf10

On Sun, Oct 21, 2018 at 01:27:52PM +0530, Pirate Praveen wrote:
> On Sat, 20 Oct 2018 11:36:55 +0200
> =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?=  wrote:
> >  Let's break it to parts.
> > 1) Can libprotobuf10 and libprotobuf17 installed together and
> > independent packages working correctly with these libraries? Yes,
> > these are possible. I don't see the need to break the old
> > libprotobuf10 package.
> 
> OK. Since its only an issue during build time and not runtime, I think
> we can reduce the severity of this bug.

No, it is not.

I would expect everything that fails during build time to fail the same 
way at runtime.

> > 2) Packages that depend on each other, need to be compiled with the
> > same ProtoBuf version. This should be expressed in those package
> > dependencies.
>...

How exactly do you want this to be "expressed in those package 
dependencies" so that it is ensured that any kind of stretch/buster/sid
mixing that is permitted by the package dependencies is also working?

If you actually have a complete solution that is better than a
Breaks: libprotobuf10 in libprotobuf17, please share the details.

cu
Adrian

-- 

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

Bug#591430: xserver-xorg-core: "Maximum number of clients reached" hardcoded

[David Fries]

xserver-xorg-core 1.19 in stretch does have the option to increase the
client limit to 512, any chance of have this the default option?  I
only stumbled on this when I was looking for a different bug.

Section "ServerFlags"
Option "MaxClients"  "512"

I also think this bug report should be closed now that it is fixed
upstream and is in a Debian stable release.

-- 
David Fries 

Bug#911989: ITP: r-cran-usethis -- Automate Package and Project Setup

[Dylan Aïssi]

Package: wnpp
Owner: Dylan Aïssi 
Severity: wishlist

* Package name: r-cran-usethis
  Version : 1.4.0
  Upstream Author : Hadley Wickham, Jennifer Bryan, RStudio
* URL : https://cran.r-project.org/package=usethis
* License : GPL-3
  Programming Lang: GNU R
  Description : Automate Package and Project Setup
 Automate package and project setup tasks that are otherwise
 performed manually. This includes setting up unit testing, test
 coverage, continuous integration, Git, 'GitHub', licenses, 'Rcpp', 'RStudio'
 projects, and more.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-usethis

Bug#911988: reintroduce fixed python2 package for rdepends

[Julian Taylor]

Package: txtorcon
Version:  18.0.2-2
Severity: important

The removal of the python2 package in #905253 due to a packaging bug
made its reverse dependencies RC buggy.
As upstream still supports python2 [0], it is tested in the package
build and its rdepends and buster will still ship with python2 please
reintroduce the python2 package.

Attached a debdiff that fixes the installation of the python3 only file
in the python2 package.


[0] https://github.com/meejah/txtorcon
diff --git a/debian/changelog b/debian/changelog
index f266461..b644918 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+txtorcon (18.0.2-3) unstable; urgency=medium
+
+  * reintroduce fixed Python 2 package needed by reverse dependencies
+Closes: #911271
+
+ -- Julian Taylor   Fri, 26 Oct 2018 22:30:43 
+0200
+
 txtorcon (18.0.2-2) unstable; urgency=medium
 
   * No longer builds a Python 2 package (Closes: #905253)
diff --git a/debian/control b/debian/control
index 0eac5fa..a20741c 100644
--- a/debian/control
+++ b/debian/control
@@ -8,6 +8,14 @@ Build-Depends: debhelper (>= 9),
dh-python,
graphviz,
lsof,
+   python-all,
+   python-geoip,
+   python-ipaddress,
+   python-mock,
+   python-repoze.sphinx.autointerface,
+   python-setuptools,
+   python-sphinx,
+   python-twisted,
python3-all,
python3-geoip,
python3-mock,
@@ -21,6 +29,29 @@ Vcs-Browser: 
https://salsa.debian.org/pkg-privacy-team/txtorcon
 Vcs-Git: https://salsa.debian.org/pkg-privacy-team/txtorcon.git
 Homepage: https://github.com/meejah/txtorcon
 
+Package: python-txtorcon
+Architecture: all
+Depends: python-geoip,
+ python-ipaddress,
+ python-twisted,
+ python-zope.interface,
+ ${misc:Depends},
+ ${python:Depends}
+Suggests: tor
+Provides: ${python:Provides}
+Description: Twisted-based asynchronous Tor control protocol implementation 
(Python 2)
+ txtorcon main feature is to present an asynchronous API to speak the Tor
+ client protocol in Python. It also provides abstractions to track and get
+ updates about Tor's state and current configuration (including writing it to
+ Tor or disk), along with helpers to asynchronously launch slave instances of
+ Tor including Twisted endpoint support.
+ .
+ Twisted is an event-driven networking engine written in Python and Tor is an
+ onion-routing network designed to improve people's privacy and anonymity on 
the
+ Internet.
+ .
+ This package contains the Python 2 module.
+
 Package: python3-txtorcon
 Architecture: all
 Depends: python3-geoip,
diff --git a/debian/rules b/debian/rules
index a334f92..aa0b193 100755
--- a/debian/rules
+++ b/debian/rules
@@ -3,7 +3,7 @@
 export PYBUILD_NAME=txtorcon
 
 %:
-   dh $@ --with=python3,sphinxdoc --buildsystem=pybuild
+   dh $@ --with=python2,python3,sphinxdoc --buildsystem=pybuild
 
 override_dh_auto_build:
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ 
docs/_build/html # HTML generator
@@ -11,17 +11,28 @@ override_dh_auto_build:
 
 override_dh_auto_install:
dh_auto_install -O--buildsystem=pybuild
+   # don't install py3 files in py2 as they don't compile during 
installation
+   find debian/python-txtorcon/ -name controller_py3.py -delete
+   mkdir -p debian/python-txtorcon/usr/share/doc/python-txtorcon
mkdir -p debian/python3-txtorcon/usr/share/doc/python3-txtorcon
set -e && \
+   for data_src in README.rst TODO examples; do \
+   mv debian/python-txtorcon/usr/share/txtorcon/$$data_src \
+   debian/python-txtorcon/usr/share/doc/python-txtorcon; \
+   done
+   set -e && \
for data_src in README.rst TODO examples; do \
mv debian/python3-txtorcon/usr/share/txtorcon/$$data_src \
debian/python3-txtorcon/usr/share/doc/python3-txtorcon; 
\
done
+   chmod 644 
debian/python-txtorcon/usr/share/doc/python-txtorcon/examples/*.py
chmod 644 
debian/python3-txtorcon/usr/share/doc/python3-txtorcon/examples/*.py
+   rm -r debian/python-txtorcon/usr/share/txtorcon
rm -r debian/python3-txtorcon/usr/share/txtorcon
 
 override_dh_compress:
dh_compress -Xlaunch_tor_with_simplehttpd.py -O--buildsystem=pybuild
 
 override_dh_auto_test:
+   PYTHONPATH=. trial --reporter=text test
PYTHONPATH=. trial3 --reporter=text test

Bug#811377: closed by Dmitry Bogatov (Bug#811377: fixed in sysvinit 2.88dsf-60)

[Dmitry Bogatov]

[2018-10-26 13:58] Ben Hutchings 
> part 1 text/plain1014
> On Fri, 2018-10-26 at 10:39 +, Debian Bug Tracking System wrote:
> > This is an automatic notification regarding your Bug report
> > which was filed against the wnpp package:
> > 
> > #811377: RFA: sysvinit -- System-V-like init utilities - transitional 
> > package
> > 
> > It has been closed by Dmitry Bogatov .
> Benda created a git repository at .

My repository is fork of 'debian/sysvinit'. As far as I can tell, the
following work was done on debian/sysvinit:

 * import history from alioth up to 2.89-59.10
 * create (very) incomplete upgrade to 2.90 in branch dgit/experimental

What I done:

 * incorporated NMU 2.89-59.11
 * modernized package a bit

> You seem to have missed that Ian and Benda already started to adopt
> sysvinit.  (While they missed closing this bug.)

Sysvinit have undecided maintainance status for years, which prevented
me from taking actions previously. But now danger is grave and immediate
(see recent discussions about removal of sysvinit on debian-devel@), so
I took libery to take action right now.

I am sorry, if I stepped on someone's toes. I would greatly appericate
any help in maintaining sysvinit.

Oh, and surely, while I did my best to not introduce any functional
changes in 2.89-60, brave souls to test upload are more then welcome.

Bug#911864: lintian gives E: statically-linked-binary for golang project's binary

[Chris Lamb]

Jeffrey,

> I had tried with golang-go, with gcc-go, same thing happens. I haven't
> tried golang-any though.

I just tried building package after uncommenting out "golang-go"
from the Build-Depends.

This silenced the warning for me, so I suggest there is something
amiss with your testcase.


Best wishes,

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

Bug#907815: gosa: UI behaves strangely, some data not saved

[Dominik George]

Control: severity -1 important

Here are two errors I get when continuing to use GoSA after the error
occurred:


Fatal error: Uncaught ArgumentCountError: Too few arguments to function
userManagement::filterLockLabel(), 0 passed in
/usr/share/gosa/include/class_listing.inc on line 856 and exactly 1 expected
in /usr/share/gosa/plugins/admin/users/class_userManagement.inc:856 Stack
trace: #0 /usr/share/gosa/include/class_listing.inc(856):
userManagement::filterLockLabel() #1
/usr/share/gosa/include/class_listing.inc(980):
listing->processElementFilter('%{filter:lockLa...', Array, 0) #2
/usr/share/gosa/include/class_listing.inc(853):
listing->filterActions('cn=nik,ou=group...', 0, Array) #3
/usr/share/gosa/include/class_listing.inc(764):
listing->processElementFilter('%{filter:action...', Array, 0) #4
/usr/share/gosa/include/class_listing.inc(407):
listing->renderCell('%{filter:action...', Array, 0) #5
/usr/share/gosa/include/class_management.inc(225): listing->render() #6
/usr/share/gosa/include/class_management.inc(214): management->renderList()
#7 /usr/share/gosa/plugins/admin/users/main.inc(44): management->execute()
#8 /usr/share/ in
/usr/share/gosa/plugins/admin/users/class_userManagement.inc on line 856

Fatal error: Uncaught Error: Call to undefined method aclResolver::update()
in /usr/share/gosa/include/class_management.inc:167 Stack trace: #0
/usr/share/gosa/plugins/admin/users/main.inc(44): management->execute() #1
/usr/share/gosa/html/main.php(407): require('/usr/share/gosa...') #2 {main}
thrown in /usr/share/gosa/include/class_management.inc on line 167


Seems like some random errors triggered by some corruption of I do not know
what kind.

Going back to main.php, logging out and back in again returns GoSA to a
usable state again, until it happens next time.

The bug also happens in a new Debian Edu install, both stretch and buster,
and can also be triggered by using any list views in some random order, e.g.
when editing roles and groups of a few users in a row.


signature.asc
Description: PGP signature

Bug#864925: wiki.debian.org: gridlines in tables

[Antoine Beaupré]

Sorry, some typos:

On 2018-10-26 16:30:52, Antoine Beaupre wrote:
> Before:
>
> https://screenshots.firefox.com/KCOr4HJHKqiNqcbQ/wiki.debian.ogr

This should be:

https://screenshots.firefox.com/KCOr4HJHKqiNqcbQ/wiki.debian.org

> After:
>
> https://screenshots.firefox.com/KCOr4HJHKqiNqcbQ/wiki.debian.org

And:

https://screenshots.firefox.com/vf7OcIbrRf0FT0Oa/wiki.debian.org

A.

-- 
The future is already here – it's just not very evenly distributed.
   - William Gibson

Bug#907348: closed by Thorsten Alteholz (Bug#907348: fixed in dateutils 0.4.5-1)

[Adrian Bunk]

Control: reopen -1

On Wed, Oct 17, 2018 at 09:33:03PM +, Debian Bug Tracking System wrote:
>...
>  dateutils (0.4.5-1) unstable; urgency=medium
>  .
>* New upstream release (Closes: #907348, #909031)
>...

Still FTBFS:
https://buildd.debian.org/status/package.php?p=dateutils=sid

cu
Adrian

-- 

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

Bug#911987: delly: missing build dependency on chrpath

[Adrian Bunk]

Source: delly
Version: 0.7.9-1
Severity: serious
Tags: ftbfs

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

...
make[2]: Leaving directory '/<>'
chrpath -d src/dpe src/delly
make[1]: chrpath: Command not found
make[1]: *** [debian/rules:13: override_dh_auto_build] Error 127

Bug#879665: ITP

[Jeffrey Cliff]

Pirate Praveen, A year ago you expressed interest in packaging
node-prettier...are you still working on this?  Are you stuck on anything?
Thanks,
Jeff Cliff

Bug#877202: Gentle reminder

[Emmanouil Kampitakis]

Dear maintainers,

  during a BSP I stumbled uppon this Bug and it seems that there is
  merely an upload missing. Consider this a gentle reminder to do so.

Greetings,
 madonius


pgpQriDMfBwvq.pgp
Description: OpenPGP digital signature

Bug#907815: gosa: UI behaves strangely, some data not saved

[Wolfgang Schweer]

On Sun, Sep 02, 2018 at 08:06:54PM +0200, Dominik George wrote:
> > The UI immediately started to behave oddly.  When switching through the
> > views, without doing anything else, at some point the values in the tables
> > vanish, or strange values (e.g.  the number 1) is displayed instead of,
> > e.g., group names.
> 
> Attached is a screencast.

Error message after clicking randomly some main menu items:

Fatal error: Uncaught ArgumentCountError:
Too few arguments to function ogroupManagement::filterProperties(),
1 passed in /usr/share/gosa/include/class_listing.inc on line 856 and exactly 2
expected in /usr/share/gosa/plugins/admin/ogroups/class_ogroupManagement.inc:122

Stack trace:
#0 /usr/share/gosa/include/class_listing.inc(856): 
ogroupManagement::filterProperties(0)
#1 /usr/share/gosa/include/class_listing.inc(764): 
listing->processElementFilter('%{filter:filter...', Array, 0)
#2 /usr/share/gosa/include/class_listing.inc(407): 
listing->renderCell('%{filter:filter...', Array, 0)
#3 /usr/share/gosa/include/class_management.inc(225): listing->render()
#4 /usr/share/gosa/include/class_management.inc(214): management->renderList()
#5 /usr/share/gosa/plugins/admin/ogroups/main.inc(44): management->execute()
#6 /usr/share/gosa/html/main.php(407): require('/usr/share/gosa...')
#7 {main} thrown in 
/usr/share/gosa/plugins/admin/ogroups/class_ogroupManagement.inc on line 122

Wolfgang


signature.asc
Description: PGP signature

Bug#911864: lintian gives E: statically-linked-binary for golang project's binary

[Jeffrey Cliff]

I had tried with golang-go, with gcc-go, same thing happens. I haven't
tried golang-any though.
E: golang-notabug-themusicgod1-panicparse-dev: statically-linked-binary
usr/bin/panic

Trying with golang-any...and the same thing happens.

On Fri, 26 Oct 2018 at 00:28, Chris Lamb  wrote:

> tags 911864 + moreinfo
> thanks
>
> Hi Jeff,
>
> > According to #718404, golang packages aren't supposed to give an error
> > of statically-linked-binary because all go language packages are
> > apparently statically linked.
>
> lintian uses whether a package build-depends against golang-go or
> golang-any to determine whether this is "Go" package and, if so,
> skips emission of the statically-linked-binary tag for the reasons
> you state.
>
> However, your package does not have such a build-depends, ie:
>
>   https://notabug.org/themusicgod1/panicparse/src/master/debian/control#L9
>
> (Is there a reason for this, etc. etc.)
>
>
> Best wishes,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>


-- 
GENERATION 26: The first time you see this, copy it into your sig on any
forum and add 1 to the generation

Bug#864925: wiki.debian.org: gridlines in tables

[Antoine Beaupre]

Package: wiki.debian.org
Followup-For: Bug #864925

I'm using the following custom style to godd effect:

th, td { border-bottom: 1px solid #d2d3d7; }

Sample page:

https://wiki.debian.org/SystemBuildTools

Before:

https://screenshots.firefox.com/KCOr4HJHKqiNqcbQ/wiki.debian.ogr

After:

https://screenshots.firefox.com/KCOr4HJHKqiNqcbQ/wiki.debian.org

Seems way more readable to me! :)

Do notice how it will outline structure problems in some tables (see
the "General tools" section for an example). I consider that a
feature.

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

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

Bug#911030: bugs.debian.org: [bugreport.cgi] contains Perl error in page source

[Chris Lamb]

tags 911030 + patch
thanks

Hi,

> bugs.debian.org: [bugreport.cgi] contains Perl error in page source

This was probably added by me in:

  https://bugs.debian.org/890338

Patch attached, I hope.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/templates/en_US/cgi/bugreport.tmpl 
b/templates/en_US/cgi/bugreport.tmpl
index d264df6..c076509 100644
--- a/templates/en_US/cgi/bugreport.tmpl
+++ b/templates/en_US/cgi/bugreport.tmpl
@@ -1,5 +1,5 @@
 {include(q(html/pre_title))}#{$bug_num} - {html_escape($status{subject})} - 
{html_escape($config{project})} {html_escape($config{bug})} report 
logs{include(q(html/post_title.tmpl))}
-
+
 

Bug#911946: Bug #911946: rc-status: double free or corruption (!prev)

[Bernhard Übelacker]

Just for reference attached some notes how to
switch to openrc and some debugging attempts.

# switch to unstable
nano /etc/apt/sources.list

apt update
apt dist-upgrade
apt autoremove
reboot

nano /etc/default/grub
# remove quiet
# add init=/sbin/openrc-init
update-grub

apt install initscripts
apt install tmux
apt install openrc

tmux# in virtual console

tmux attach # in ssh
for file in /etc/rc0.d/K*; do s=`basename $(readlink "$file")` ; /etc/init.d/$s 
stop; done

reboot


# just ssh works, after a little wait time - no virtual console

dpkg --purge systemd systemd-sysv systemd-shim libpam-systemd sysvinit-core init

openrc-shutdown -r


apt install psmisc tmux valgrind openrc-dbgsym librc1-dbgsym devscripts 
dpkg-dev mc quilt
apt build-dep openrc




mkdir openrc/orig -p
cdopenrc/orig
apt source openrc
cd ../..

mkdir libc6/orig -p
cdlibc6/orig
apt source libc6
cd ../..





gdb -q --args rc-status

set height 0
set width 0
set pagination off
directory /root/openrc/orig/openrc-0.38/src/librc
run

---

...
Dynamic Runlevel: hotplugged
corrupted double-linked list

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht 
gefunden.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x77bb42f1 in __GI_abort () at abort.c:79
#2  0x77bf5867 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x77cff273 "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x77bfbe0a in malloc_printerr (str=str@entry=0x77cfd3d6 
"corrupted double-linked list") at malloc.c:5350
#4  0x77bfc024 in malloc_consolidate (av=av@entry=0x77d34c40 
) at malloc.c:4456
#5  0x77bfedad in _int_malloc (av=av@entry=0x77d34c40 , 
bytes=bytes@entry=32816) at malloc.c:3703
#6  0x77c0064c in __GI___libc_malloc (bytes=32816) at malloc.c:3057
#7  0x77c3d743 in __alloc_dir (fd=3, close_fd=, 
flags=, statp=) at ../sysdeps/posix/opendir.c:216
#8  0x77c3d85d in opendir_tail (fd=3) at ../sysdeps/posix/opendir.c:136
#9  0x77d62aa9 in ?? () from /lib/x86_64-linux-gnu/librc.so.1
#10 0x77d6497d in rc_services_in_state () from 
/lib/x86_64-linux-gnu/librc.so.1
#11 0x7b8b in ?? ()
#12 0x77b9fb17 in __libc_start_main (main=0x75c0, argc=1, 
argv=0x7fffed18, init=, fini=, 
rtld_fini=, stack_end=0x7fffed08) at ../csu/libc-start.c:310
#13 0x7efa in ?? ()


---

Dynamic Runlevel: hotplugged
corrupted double-linked list

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht 
gefunden.
(gdb) set height 0
(gdb) set width 0
(gdb) set pagination off
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x77bb42f1 in __GI_abort () at abort.c:79
#2  0x77bf5867 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x77cff273 "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x77bfbe0a in malloc_printerr (str=str@entry=0x77cfd3d6 
"corrupted double-linked list") at malloc.c:5350
#4  0x77bfc024 in malloc_consolidate (av=av@entry=0x77d34c40 
) at malloc.c:4456
#5  0x77bfedad in _int_malloc (av=av@entry=0x77d34c40 , 
bytes=bytes@entry=32816) at malloc.c:3703
#6  0x77c0064c in __GI___libc_malloc (bytes=32816) at malloc.c:3057
#7  0x77c3d743 in __alloc_dir (fd=3, close_fd=, 
flags=, statp=) at ../sysdeps/posix/opendir.c:216
#8  0x77c3d85d in opendir_tail (fd=3) at ../sysdeps/posix/opendir.c:136
#9  0x77c3d910 in __opendir (name=name@entry=0x7fffdba0 
"/run/openrc/hotplugged") at ../sysdeps/posix/opendir.c:190
#10 0x77d62aa9 in ls_dir (dir=dir@entry=0x7fffdba0 
"/run/openrc/hotplugged", options=options@entry=1) at librc.c:71
#11 0x77d6497d in __RC_rc_services_in_state (state=) at 
librc.c:1006
#12 0x7b8b in main (argc=, argv=) at 
rc-status.c:353


---

root@debian:~# valgrind rc-status
==2542== Memcheck, a memory error detector
==2542== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==2542== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==2542== Command: rc-status
==2542== 
Runlevel: default
==2542== Conditional jump or move depends on uninitialised value(s)
==2542==at 0x10C416: print_service (rc-status.c:160)
==2542==by 0x10C6FB: print_services (rc-status.c:215)
==2542==by 0x10BAAB: main (rc-status.c:342)
==2542== 
==2542== Conditional jump or move depends on uninitialised value(s)
==2542==at 0x4B2597C: vfprintf (vfprintf.c:1643)
==2542==by 0x4BDDAE8: __vsnprintf_chk (vsnprintf_chk.c:63)
==2542==by 0x10C141: vsnprintf (stdio2.h:77)
==2542==by 0x10C141: xasprintf 

Bug#911986: ufw is disabled on startup after the most recent update. also ufw enable returns "ERROR: could nkt load logging rules". ufw reload tells me that the firewall is inactive. if i run ufw stat

[Aryan]

Package: ufw
Version: 0.35-6
Severity: important
Tags: a11y



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

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

Versions of packages ufw depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  iptables   1.8.1-2
ii  lsb-base   9.20170808
ii  python33.6.7-1
ii  ucf3.0038

ufw recommends no packages.

Versions of packages ufw suggests:
ii  rsyslog  8.38.0-1+b1

-- Configuration Files:
/etc/default/ufw changed:
IPV6=yes
DEFAULT_INPUT_POLICY="REJECT"
DEFAULT_OUTPUT_POLICY="ACCEPT"
DEFAULT_FORWARD_POLICY="DROP"
DEFAULT_APPLICATION_POLICY="SKIP"
MANAGE_BUILTINS=no
IPT_SYSCTL=/etc/ufw/sysctl.conf
IPT_MODULES="nf_conntrack_ftp nf_nat_ftp nf_conntrack_netbios_ns"


-- debconf information:
  ufw/allow_known_ports:
  ufw/allow_custom_ports:
  ufw/enable: true
* ufw/existing_configuration:

Bug#911985: libvoikko FTBFS with hfst-ospell 0.5.0

[Adrian Bunk]

Source: libvoikko
Version: 4.1.1-1.1
Severity: serious
Tags: ftbfs

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

...
In file included from morphology/AnalyzerFactory.cpp:43:
./morphology/HfstAnalyzer.hpp:52:3: error: 'hfst_ol' does not name a type; did 
you mean 'wcstol'?
   hfst_ol::Transducer *t;
   ^~~
   wcstol
make[4]: *** [Makefile:1472: morphology/AnalyzerFactory.lo] Error 1

Bug#911983: phast FTBFS on architectures where char is unsigned

[Adrian Bunk]

Source: phast
Version: 1.5+dfsg-1
Severity: serious
Tags: ftbfs

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>/phast-1.5+dfsg'
cd test && 
PATH=/<>/phast-1.5+dfsg/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 make msa_view
make[2]: Entering directory '/<>/phast-1.5+dfsg/test'
*** Testing msa_view ***
msa_view hmrc.ss -i SS --end 1 > hmrc.fa
E: Build killed with signal TERM after 150 minutes of inactivity

Bug#911984: ITP: r-cran-xopen -- Open System Files, 'URLs', Anything

[Dylan Aïssi]

Package: wnpp
Owner: Dylan Aïssi 
Severity: wishlist

* Package name: r-cran-xopen
  Version : 1.0.0
  Upstream Author : Gábor Csárdi
* URL : https://cran.r-project.org/package=xopen
* License : MIT
  Programming Lang: GNU R
  Description : Open System Files, 'URLs', Anything
 Cross platform solution to open files, directories or 'URLs'
 with their associated programs.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-xopen

Bug#911946: Bug #911946: rc-status: double free or corruption (!prev)

[Bernhard Übelacker]

Hello Mo Zhou,
I just tried to reproduce the issue and thats my findings:

...
corrupted double-linked list

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht 
gefunden.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x77bb42f1 in __GI_abort () at abort.c:79
#2  0x77bf5867 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x77cff273 "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x77bfbe0a in malloc_printerr (str=str@entry=0x77cfd3d6 
"corrupted double-linked list") at malloc.c:5350
#4  0x77bfc024 in malloc_consolidate (av=av@entry=0x77d34c40 
) at malloc.c:4456
#5  0x77bfedad in _int_malloc (av=av@entry=0x77d34c40 , 
bytes=bytes@entry=32816) at malloc.c:3703
#6  0x77c0064c in __GI___libc_malloc (bytes=32816) at malloc.c:3057
#7  0x77c3d743 in __alloc_dir (fd=3, close_fd=, 
flags=, statp=) at ../sysdeps/posix/opendir.c:216
#8  0x77c3d85d in opendir_tail (fd=3) at ../sysdeps/posix/opendir.c:136
#9  0x77c3d910 in __opendir (name=name@entry=0x7fffdba0 
"/run/openrc/hotplugged") at ../sysdeps/posix/opendir.c:190
#10 0x77d62aa9 in ls_dir (dir=dir@entry=0x7fffdba0 
"/run/openrc/hotplugged", options=options@entry=1) at librc.c:71
#11 0x77d6497d in __RC_rc_services_in_state (state=) at 
librc.c:1006
#12 0x7b8b in main (argc=, argv=) at 
rc-status.c:353


Running with valgrind starts with this message
that seems to be already the problem:

==2542== Conditional jump or move depends on uninitialised value(s)
==2542==at 0x10C416: print_service (rc-status.c:160)
==2542==by 0x10C6FB: print_services (rc-status.c:215)
==2542==by 0x10BAAB: main (rc-status.c:342)
==2542== 


rc-status.c:
159 uptime = get_uptime(service);
160 if (uptime) {


In the end we see here upstream pull request [1]
that got applied in commit [2].


A local built package that initilizes the variable upstream
does not crash and shows no problem again with valgrind.

That commit would be already included in upstream release 0.39.

Kind regards,
Bernhard


[1] https://github.com/OpenRC/openrc/pull/231
[2] 
https://gitweb.gentoo.org/proj/openrc.git/commit/src/rc/rc-status.c?id=79648ac1c6355975abca6acf6076e7022037523f

Bug#890468: lintian: source-is-missing false positive when d/missing-sources/foo has no known suffix

[Chris Lamb]

tags 890468 - moreinfo
thanks

Dear dkg,

> hm, thanks for the ping!  I've just tried to replicate it and the
> problem is subtly different than i thought it was beforehand.

Ah, neat. These are the best bugs!

> Does that sound reasonable?

Alas I haven't absorbed the above yet, just ACKing your quick
response and removing the `moreinfo` tag to match. Thank you.


Best wishes,

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

Bug#873327: aegisub FTBFS with luajit 2.1

[Pascal Mons]

I believe I have successfully build from the latest Debian source 
aegisub_3.2.2+dfsg.orig the application Aegisub.


This build follows the Debian guidelines and use the latest available system 
libraries e.g. luajit_2.1.0~beta3+dfsg-5.1

To achieve the result I did use the patch mentioned here by Paul and coming 
from openSUSE taking care of luajit 2.1.


https://build.opensuse.org/package/view_file/multimedia:apps/aegisub/luabins.patch?expand=1


I did as well add a add-unicode-international-include-unistr.h.patch


I am using this list of patches in order to build properly (from 
debian/patches/series):


fix-pthread.patch
only-add-timestamp-in-build-credit.patch
change-aegisub-command.patch
openal-workaround.patch
change-default-dictionary-search-path.patch
#link-against-system-luajit.patch
escape-sequence-lua-5.2.patch
link-against-system-luajit-and-remove-vendor-luajit-dependency.patch
add-libatomic-dependency.patch
add-unicode-international-include-unistr.h.patch
add-luabins-support-for-lua5.2-luajit-2.1.patch


The aegisub Debian packages are build and available for the last 4 maintained 
Ubuntu releases in my Launchpad PPA Photo Video Applications.


https://launchpad.net/~anton+/+archive/ubuntu/photo-video-apps


Unfortunately the upstream source currently hosted at 
GitHub and previously mentioned here, is 
poorly maintained to say the least since 2014 / 2015, as it looks like there 
isn't any active developer to speak of, taking care of it.


I did just verify in the GitHub git how they did manage to solve the luajit 2.1 
FTBFS as Paul commented earlier:


'The upstream IRC channel mentioned that this bug is fixed in git master

...

I wasn't able to find the patch in upstream, likely fixed another way.'


For sure, they just ditched the system luajit 2.1 libraries and forced use of 
the older luajit bundled in their vendor sources. Here is the commit describing 
the action in their 'master' git:


commit bc157d9bbc00860fb7019b9c869317809a350ef7
Author: Thomas Goyne 
Date:   Sat Mar 3 12:44:31 2018 -0800

Also stub out the `system` lua module that newer versions of busted use


I believe their master git maintained at GitHub is utterly not properly 
maintained at all and unreliable period.


If properly patched, the Debian source aegisub_3.2.2+dfsg can still be build 
properly.

I believe as well that aegisub should be back soon in debian testing.


https://tracker.debian.org/news/874946/aegisub-removed-from-testing/

Bug#897865: Code compiles just fine with current commit in Salsa

[Hilko Bengen]

Hi,

greetings from BSP in Karlsruhe.

The current commit in Salsa -- 00b7e79dd144ebfc5d187c331353b50239b032db,
marked "snapd (2.35.5-1) UNRELEASED" -- builds the test code including
locking-test.c just fine, but various tests then fail.

Cheers,
-Hilko

Bug#879722: lintian: W-shlibs-symbol-not-found: false positive

[Chris Lamb]

[re-adding 879...@bugs.debian.org to CC; please do not silently drop CCs]

Dear Shawn,

> I struggle with debbigs and do not know how to close this.

No problem; I will go ahead and close it.


Best wishes,

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

Bug#890468: lintian: source-is-missing false positive when d/missing-sources/foo has no known suffix

[Daniel Kahn Gillmor]

Control: retitle 890468 lintian: source-is-missing false positive when 
d/missing-sources/foo has no known suffix

On Fri 2018-10-26 14:52:38 -0400, Chris Lamb wrote:
> Chris Lamb wrote:
>
>> Thanks for the bug report but unfortunately I think I'm either
>> parsing the problem incorrectly or think we are handling this
>> correctly already. I've added a testcase here:
>> 
>> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=2c09091df0c8425e96ac2104b6f49fab8f1f7b10
>
> Gentle ping on this?

hm, thanks for the ping!  I've just tried to replicate it and the
problem is subtly different than i thought it was beforehand.

I'm attaching an example_1.0.orig.tar.gz and a
example_1.0-1.debian.tar.xz

The relevant lintian tags printed are:

P: example source: source-contains-prebuilt-binary bar
E: example source: source-is-missing bar
P: example source: source-contains-prebuilt-binary foo
E: example source: source-is-missing foo

and here's the missing-sources:

0 dkg@alice:~/src/bugs/890468/example$ find debian/missing-sources/ -ls
  4973159  4 drwxr-xr-x   3 dkg  dkg  4096 Oct 26 15:53 
debian/missing-sources/
  4973200  0 lrwxrwxrwx   1 dkg  dkg 3 Oct 26 15:53 
debian/missing-sources/foo -> bar
  4973197  4 drwxr-xr-x   2 dkg  dkg  4096 Oct 26 15:48 
debian/missing-sources/bar
  4973198  4 -rw-r--r--   1 dkg  dkg27 Oct 26 15:37 
debian/missing-sources/bar/main.c
  4973199  4 -rw-r--r--   1 dkg  dkg63 Oct 26 15:37 
debian/missing-sources/bar/Makefile
0 dkg@alice:~/src/bugs/890468/example$ 

so from debian/missing-sources, you can "make foo" and "make bar" with
no problem, but lintian doesn't notice that, because it's looking for
debian/missing-sources/bar.c or debian/missing-sources/bar.cpp or
whatever, but it does not accept not debian/missing-sources/bar/ (a
directory) or debian/missing-sources/foo (a symlink) as the source.

if i "mv debian/missing-sources/foo{,.c}" then lintian doesn't report
"source-is-missing foo" any longer, even though it remains a symlink!

Anyway, i think if lintian is looking for source for file FFF and it
finds debian/missing-sources/FFF , it should treat that as a match.

Does that sound reasonable?

 --dkg



example_1.0.orig.tar.gz
Description: application/gzip


example_1.0-1.debian.tar.xz
Description: application/xz

Bug#911982: ITP: r-cran-clisymbols -- Unicode Symbols at the R Prompt

[Dylan Aïssi]

Package: wnpp
Owner: Dylan Aïssi 
Severity: wishlist

* Package name: r-cran-clisymbols
  Version : 1.2.0
  Upstream Author : Gábor Csárdi, Sindre Sorhus
* URL : https://cran.r-project.org/package=clisymbols
* License : MIT
  Programming Lang: GNU R
  Description : Unicode Symbols at the R Prompt
 A small subset of Unicode symbols, that are useful
 when building command line applications. They fall back to
 alternatives on terminals that do not support Unicode.
 Many symbols were taken from the 'figures' 'npm' package
 (see ).

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-clisymbols

Bug#911981: qemu server warns about missing CPU features

[Antoine Beaupre]

Package: autopkgtest
Version: 5.6
Severity: normal

It looks like the way autopkgtest calls qemu is suboptimal:

gnupg2-2.1.1816$ autopkgtest . -- qemu 
/var/lib/libvirt/images/debian9-amd64-autopkgtest.qcow2
autopkgtest [15:26:43]: version 5.6
autopkgtest [15:26:43]: host curie; command line: /usr/bin/autopkgtest . -- 
qemu /var/lib/libvirt/images/debian9-amd64-autopkgtest.qcow2
qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.01H:ECX.vmx [bit 5]
autopkgtest [15:26:54]: testbed dpkg architecture: amd64
autopkgtest [15:26:57]: testbed running kernel: Linux 4.9.0-7-amd64 #1 SMP 
Debian 4.9.110-1 (2018-07-05)
autopkgtest [15:26:57]:  unbuilt-tree .
[...]

>From there on the build proceeds on fine, but I suspect it's not using
the hardware support for virtualization.

I do not get that warning when launching qemu by hand, for example
this works flawlessly:

qemu-system-x86_64  -enable-kvm -snapshot -m 1G,slots=3,maxmem=4G 
/var/lib/libvirt/images/debian9-amd64-autopkgtest.qcow2

Maybe qemu needs to be launched with `-enable-kvm`? Strangely, later
in the tests, I see this in my process list:

28937 pts/4Sl+7:45 qemu-system-x86_64 -m 1024 -smp 1 [...] -monitor 
[...]  -enable-kvm -cpu kvm64,+vmx,+lahf_lm

So maybe this is something else?

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
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 autopkgtest depends on:
ii  apt-utils   1.7.0
ii  libdpkg-perl1.19.2
ii  procps  2:3.3.15-2
ii  python3 3.6.6-1
ii  python3-debian  0.1.33

Versions of packages autopkgtest recommends:
ii  autodep8  0.14

Versions of packages autopkgtest suggests:
ii  lxc   1:2.0.9-6.1
pn  lxd   
pn  ovmf  
ii  qemu-efi-aarch64  0~20180812.cb5f4f45-1
pn  qemu-efi-arm  
ii  qemu-system   1:2.12+dfsg-3+b1
ii  qemu-utils1:2.12+dfsg-3+b1
ii  schroot   1.6.10-5
ii  vmdb2 0.13.2-1

-- debconf-show failed

Bug#911980: objenesis FTBFS: test failure

[Adrian Bunk]

Source: objenesis
Version: 3.0.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=objenesis=all=3.0.1-1=1540137557=0

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Objenesis parent project 3.0.1 . SUCCESS [  0.006 s]
[INFO] Objenesis 3.0.1  FAILURE [ 12.305 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 14.046 s
[INFO] Finished at: 2018-10-21T15:59:03Z
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on 
project objenesis: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/main/target/surefire-reports for the 
individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
System.exit called?
[ERROR] Command was /bin/sh -c cd /<>/main && 
/usr/lib/jvm/java-10-openjdk-amd64/bin/java -jar 
/<>/main/target/surefire/surefirebooter10304618814861781140.jar 
/<>/main/target/surefire 2018-10-21T15-58-52_666-jvmRun1 
surefire6817057575982457300tmp surefire_04795030640410075527tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
forked VM terminated without properly saying goodbye. VM crash or System.exit 
called?
[ERROR] Command was /bin/sh -c cd /<>/main && 
/usr/lib/jvm/java-10-openjdk-amd64/bin/java -jar 
/<>/main/target/surefire/surefirebooter10304618814861781140.jar 
/<>/main/target/surefire 2018-10-21T15-58-52_666-jvmRun1 
surefire6817057575982457300tmp surefire_04795030640410075527tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:671)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:278)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:244)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1194)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1022)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:868)
[ERROR] at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
[ERROR] at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
[ERROR] at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
[ERROR] at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
[ERROR] at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at 
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
[ERROR] at 
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
[ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:954)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:181)
[ERROR] at org.debian.maven.Wrapper.main(Wrapper.java:89)
[ERROR] at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at 

Bug#911965: [Pkg-electronics-devel] Bug#911965: kicad: Add libngspice to dependancy list

[Felix Salfelder]

On Fri, Oct 26, 2018 at 08:22:45PM +0200, Carsten Schoenert wrote:
> partially correct.
> KiCad in Debian now supports ngspice based simulations provided by the
> library libngspice.so.0.0.0 from the package libngspice0.
> 
> The question is why the packaging doesn't detect this dependency
> automatically ... I will have a look.

Dear Carsten.

It seems to me that kicad does not link against ngspice, but rather
dlopens the shared library on demand.

While the reasons are probably different, this approach is very similar
to how gnucap-python uses libgnucap. The issue is related to the
SONAME and file name used in lib${simulator}0 vs lib${simulator}-dev.

Probably the approach used in gnucap-python will work here as well:
- find the SONAME in ./configure, tweak the dlopen call, see [1],
- tweak d/rules: link a dummy executable, inject shlibdeps [2].

I am curious if there is a better way..

hth
felix

[1] 
https://salsa.debian.org/electronics-team/Gnucap/gnucap-python/blob/master/configure.ac
[2] 
https://salsa.debian.org/electronics-team/Gnucap/gnucap-python/blob/master/debian/rules

Bug#528344: exim4-daemon-heavy: Please add SPF support

[Matthias-Christian Ott]

Package: exim4-daemon-heavy
Followup-For: Bug #528344

As of Exim 4.91 SPF is no longer marked experimental. Therefore, I see
no reason why it can't be enabled.

Bug#911979: fails on chown in autopkgtest-qemu backend

[Antoine Beaupre]

Package: sbuild
Version: 0.77.1-1
Severity: normal

I have tried to use the autopkgtest backend with the qemu server but
it completely failed to launch the build:

gnupg2-2.1.181$ sbuild --chroot-mode=autopkgtest --autopkgtest-virt-server=qemu 
--autopkgtest-virt-server-opt=/var/lib/libvirt/images/debian9-amd64-autopkgtest.qcow2
dpkg-source: info: using options from gnupg2-2.1.18/debian/source/options: 
--compression=bzip2 --compression-level=9
dh clean --with=autoreconf --builddirectory=build
   dh_auto_clean -O--builddirectory=build
   dh_autoreconf_clean -O--builddirectory=build
   dh_clean -O--builddirectory=build
dpkg-source: info: using options from gnupg2-2.1.18/debian/source/options: 
--compression=bzip2 --compression-level=9
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building gnupg2 using existing ./gnupg2_2.1.18.orig.tar.bz2
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: warning: ignoring deletion of file po/sk.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/fi.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/ca.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/cs.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/zh_CN.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/nb.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/da.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/zh_TW.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/e...@quot.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/pt.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/et.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/pl.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/e...@boldquot.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/ro.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/es.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/eo.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/hu.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/de.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/id.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/fr.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/stamp-po, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/el.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/tr.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/uk.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/gl.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/it.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/ja.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/ru.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file po/sv.gmo, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file doc/gnupg.info, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file doc/gnupg.info-1, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file doc/gnupg.info-2, use 
--include-removal to override
dpkg-source: info: building gnupg2 in gnupg2_2.1.18-8~deb9u3.debian.tar.bz2
dpkg-source: info: building gnupg2 in gnupg2_2.1.18-8~deb9u3.dsc
dpkg-source: info: using options from gnupg2-2.1.18/debian/source/options: 
--compression=bzip2 --compression-level=9
sbuild (Debian sbuild) 0.77.1 (10 September 2018) on curie.anarc.at

+==+
| gnupg2 2.1.18-8~deb9u3 (amd64)   Fri, 26 Oct 2018 19:19:15 + |
+==+

Package: gnupg2
Version: 2.1.18-8~deb9u3
Source Version: 2.1.18-8~deb9u3
Distribution: stretch
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.01H:ECX.vmx [bit 5]
chown: invalid user: 'sbuild:sbuild'
E: Failed to set sbuild:sbuild ownership on /build
Failed to set up chroot
E: Error creating chroot session: 

Bug#906281: lintian: Severity and Certainty of emacsen-common-without-dh-elpa are wrong / false positives despite "Certainty: certain"

[David Bremner]

Chris Lamb  writes:

> Chris Lamb wrote:
>
>> tags 906281 + moreinfo
>> thanks
>> 
>> Hi all,
>> 
>> > lintian: Severity and Certainty of emacsen-common-without-dh-elpa
>> > are wrong / false positives despite "Certainty: certain"
>> 
>> So, what are the next, concrete, steps for Lintian here? I don't
>> currently see a consensus...?
>
> Gentle ping on this folks?
>

I fixed the dh_elpa bug #905464 which originally triggered this
discussion, so from my point of view the lintian warning is OK. Maybe
Axel can comment if/when he has a chance to try converting tpp dh_elpa
again? I did a quick and dirty conversion myself, but there could still
be e.g. documentation issues.

Or, we could close the lintian bug for now, and revisit the bug if there
seem to be intractable problems / large classes of packages that it is
not possible to use dh_elpa with.

I just this week had a look at some custom emacsen-install scripts that
reminded me that replacing maintainer scripts with declarative tools
really is a good thing for Debian.

d




signature.asc
Description: PGP signature

Bug#881506: xul-ext-gnome-keyring doesn't work with firefox >=57

[Lorenz]

On Fri, 28 Sep 2018 21:18:54 +0200 Moritz Mühlenhoff wrote:

On Wed, Sep 26, 2018 at 02:27:00AM +, Ximin Luo wrote:
> Pretty sure it doesn't work with TB60, I just upgraded myself and am no 
longer using this extension.
Shall we remove it from the archive?


I can confirm that upstream version 0.13 does work with Thunderbird 60, 
see also https://github.com/swick/mozilla-gnome-keyring/pull/56.


Please consider updating the package instead of removing it.

Cheers,
Lorenz

Bug#911978: gau2grid builds with -march=native

[Adrian Bunk]

Source: gau2grid
Version: 1.0.1-1
Severity: serious

gau2grid builds with -march=native, which makes the resulting binaries
only run on machines that are compatible with whatever buildd
built the package.

Please remove -march=native.

Bug#911977: how do we correctly guess the VM name in autopkgtest?

[Antoine Beaupre]

Package: sbuild
Version: 0.77.1-1
Severity: wishlist

One of the nice things with the schroot backend is that it
automatically guesses which schroot to use based on internal sbuild
logic. If I build a stretch-security update, it will find my stretch
chroot, for example.

This doesn't seem to work with the autopkgtest backend:

$ sbuild --chroot-mode=autopkgtest --autopkgtest-virt-server=qemu
[...]
dpkg-source: info: building gnupg2 in gnupg2_2.1.18-8~deb9u3.debian.tar.bz2
dpkg-source: info: building gnupg2 in gnupg2_2.1.18-8~deb9u3.dsc
dpkg-source: info: using options from gnupg2-2.1.18/debian/source/options: 
--compression=bzip2 --compression-level=9
sbuild (Debian sbuild) 0.77.1 (10 September 2018) on curie.anarc.at

+==+
| gnupg2 2.1.18-8~deb9u3 (amd64)   Fri, 26 Oct 2018 19:13:13 + |
+==+

Package: gnupg2
Version: 2.1.18-8~deb9u3
Source Version: 2.1.18-8~deb9u3
Distribution: stretch
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

usage: autopkgtest-virt-qemu [-h] [-q QEMU_COMMAND] [-o OVERLAY_DIR] [-u USER]
 [-p PASSWORD] [-c CPUS] [--ram-size RAM_SIZE]
 [--timeout-reboot SECONDS] [--show-boot] [-d]
 [--qemu-options QEMU_OPTIONS] [--baseimage]
 [--efi]
 image [image ...]
autopkgtest-virt-qemu: error: the following arguments are required: image
Undefined chroot status
E: Error creating chroot session: skipping gnupg2

Now of course I can fix this by passing the image in an argument, but
then I am hardcoding that image path which is release dependent.

Shouldn't it be better for sbuild to correctly figure that out?

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
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 sbuild depends on:
ii  adduser 3.118
ii  libsbuild-perl  0.77.1-1
ii  perl5.26.2-7+b1

Versions of packages sbuild recommends:
ii  autopkgtest  5.6
ii  debootstrap  1.0.109
ii  schroot  1.6.10-5

Versions of packages sbuild suggests:
ii  deborphan  1.7.30
ii  kmod   25-1
ii  wget   1.19.5-1

-- debconf-show failed

Bug#911976: bind-dyndb-ldap FTBFS with bind 9.11.5

[Adrian Bunk]

Source: bind-dyndb-ldap
Version: 11.1-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=bind-dyndb-ldap=sid

...
In file included from ../../src/settings.h:12,
 from ../../src/zone_register.h:10,
 from ../../src/empty_zones.c:13:
../../src/types.h:50:2: error: unknown type name 'isc_uint32_t'
  isc_uint32_t seqid;
  ^~~~
In file included from ../../src/zone_register.h:10,
 from ../../src/empty_zones.c:13:
../../src/settings.h:35:3: error: unknown type name 'isc_uint32_t'
   isc_uint32_t value_uint;
   ^~~~
../../src/settings.h:101:4: error: unknown type name 'isc_uint32_t'; did you 
mean 'u_int32_t'?
isc_uint32_t * target) ATTR_NONNULLS ATTR_CHECKRESULT;
^~~~
u_int32_t
In file included from ../../src/ldap_entry.h:14,
 from ../../src/fwd.h:9,
 from ../../src/fwd.c:17:
../../src/types.h:50:2: error: unknown type name 'isc_uint32_t'
  isc_uint32_t seqid;
  ^~~~
In file included from ../../src/fwd.c:20:
../../src/settings.h:35:3: error: unknown type name 'isc_uint32_t'
   isc_uint32_t value_uint;
   ^~~~
In file included from ../../src/ldap_entry.h:14,
 from ../../src/acl.h:10,
 from ../../src/acl.c:30:
../../src/types.h:50:2: error: unknown type name 'isc_uint32_t'
  isc_uint32_t seqid;
  ^~~~
make[3]: *** [Makefile:556: ldap_la-empty_zones.lo] Error 1

Bug#911975: isc-dhcp FTBFS with bind 9.11.5

[Adrian Bunk]

Source: isc-dhcp
Version: 4.3.5-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=isc-dhcp=sid

...
gcc -DHAVE_CONFIG_H -I. -I../includes  -I.. -DLOCALSTATEDIR='"/var"' 
-Wdate-time -D_FORTIFY_SOURCE=2 -DLDAP_CONFIGURATION -DLDAP_USE_SSL -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -I/usr/include/bind-export -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -D_PATH_DHCPD_CONF='"/etc/dhcp/dhcpd.conf"' 
-D_PATH_DHCPD_DB='"/var/lib/dhcp/dhcpd.leases"' 
-D_PATH_DHCPD6_DB='"/var/lib/dhcp/dhcpd6.leases"' 
-D_PATH_DHCLIENT_SCRIPT='"/sbin/dhclient-script"' 
-D_PATH_DHCLIENT_CONF='"/etc/dhcp/dhclient.conf"' 
-D_PATH_DHCLIENT_DB='"/var/lib/dhcp/dhclient.leases"' 
-D_PATH_DHCLIENT6_DB='"/var/lib/dhcp/dhclient6.leases"' -DNSUPDATE  
-I../includes -I../bind/include -MT alloc.o -MD -MP -MF .deps/alloc.Tpo -c -o 
alloc.o alloc.c
In file included from ../includes/dhcpd.h:99,
 from alloc.c:29:
../includes/tree.h:308:30: error: unknown type name 'isc_boolean_t'; did you 
mean 'isc_token_t'?
   struct option_cache *, isc_boolean_t);
  ^
  isc_token_t
In file included from ../includes/omapip/omapip_p.h:67,
 from ../includes/dhcpd.h:103,
 from alloc.c:29:
../includes/omapip/omapip.h:268:1: error: unknown type name 'isc_boolean_t'; 
did you mean 'isc_token_t'?
 isc_boolean_t omapi_protocol_authenticated (omapi_object_t *);
 ^
 isc_token_t
In file included from ../includes/dhcpd.h:103,
 from alloc.c:29:
../includes/omapip/omapip_p.h:154:2: error: unknown type name 'isc_boolean_t'
  isc_boolean_t insecure;  /* Set to allow unauthenticated
  ^
../includes/omapip/omapip_p.h:163:2: error: unknown type name 'isc_boolean_t'
  isc_boolean_t insecure;  /* Set to allow unauthenticated
  ^
In file included from ../includes/dhcpd.h:103,
 from alloc.c:29:
../includes/omapip/omapip_p.h:213:2: error: unknown type name 'isc_boolean_t'
  isc_boolean_t closed; /* ISC_TRUE = closed, do not use */
  ^
In file included from alloc.c:29:
../includes/dhcpd.h:466:2: error: unknown type name 'isc_boolean_t'
  isc_boolean_t agent_options_stashed;
  ^
../includes/dhcpd.h:472:2: error: unknown type name 'isc_boolean_t'
  isc_boolean_t unicast;
  ^
../includes/dhcpd.h:1162:2: error: unknown type name 'isc_boolean_t'
  isc_boolean_t released;
  ^
In file included from alloc.c:29:
../includes/dhcpd.h:1679:2: error: unknown type name 'isc_uint64_t'
  isc_uint64_t num_active;  /* count of active leases */
  ^~~~
../includes/dhcpd.h:1680:2: error: unknown type name 'isc_uint64_t'
  isc_uint64_t num_abandoned;  /* count of abandoned leases */
  ^~~~
../includes/dhcpd.h:1716:2: error: unknown type name 'isc_uint64_t'
  isc_uint64_t num_total; /* Total number of elements in the pond */
  ^~~~
../includes/dhcpd.h:1717:2: error: unknown type name 'isc_uint64_t'
  isc_uint64_t num_active;/* Number of elements in the pond in use */
  ^~~~
../includes/dhcpd.h:1718:2: error: unknown type name 'isc_uint64_t'
  isc_uint64_t num_abandoned; /* count of abandoned leases */
  ^~~~
../includes/dhcpd.h:1720:2: error: unknown type name 'isc_uint64_t'
  isc_uint64_t low_threshold; /* low threshold to restart logging */
  ^~~~
../includes/dhcpd.h:1839:30: error: unknown type name 'isc_boolean_t'; did you 
mean 'isc_token_t'?
 struct option_cache *oc, isc_boolean_t appendp);
  ^
  isc_token_t
../includes/dhcpd.h:1924:27: error: unknown type name 'isc_boolean_t'; did you 
mean 'isc_token_t'?
struct option_cache *, isc_boolean_t appendp);
   ^
   isc_token_t
../includes/dhcpd.h:2012:27: error: unknown type name 'isc_boolean_t'; did you 
mean 'isc_token_t'?
struct option_cache *, isc_boolean_t appendp);
   ^
   isc_token_t
../includes/dhcpd.h:2040:35: error: unknown type name 'isc_boolean_t'; did you 
mean 'isc_token_t'?
   int, int, const struct iaddr *, isc_boolean_t);
   ^
   isc_token_t
../includes/dhcpd.h:2184:30: error: unknown type name 'isc_boolean_t'; did you 
mean 'isc_token_t'?
   struct dhcp_ddns_cb *, isc_boolean_t);
  ^
  isc_token_t
../includes/dhcpd.h:2407:1: error: unknown type name 'isc_boolean_t'; did you 
mean 'isc_token_t'?
 isc_boolean_t server_duid_isset(void);
 ^
 isc_token_t
../includes/dhcpd.h:2805:37: error: unknown type name 'isc_boolean_t'; did you 
mean 'isc_token_t'?
  int, const 

Bug#911974: openssh-client: please avoid shipping setuid ssh-keysign by default

[Daniel Kahn Gillmor]

Package: openssh-client
Version: 1:7.9p1-1
Severity: wishlist

/usr/lib/openssh/ssh-keysign is one of only a few setuid programs left
on a modern system.  It looks like it is *probably* relatively safe --
not enabled by default due to configurations set in
/etc/ssh/ssh_config, checking that config file early before doing much
else, etc.

however, i suspect that this file isn't used at all by most people
(host-based authentication is generally discouraged), and those admins
that do require it can probably install a separate package, or answer
a non-default debconf question, or something comparable that doesn't
leave a setuid binary on most installations.

Reducing the setuid attack surface would be nice!

 --dkg

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

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

Versions of packages openssh-client depends on:
ii  adduser   3.118
ii  dpkg  1.19.2
ii  libc6 2.27-6
ii  libedit2  3.1-20180525-1
ii  libgssapi-krb5-2  1.16.1-1
ii  libselinux1   2.8-1+b1
ii  libssl1.1 1.1.1-1
ii  passwd1:4.5-1.1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages openssh-client recommends:
ii  xauth  1:1.0.10-1

Versions of packages openssh-client suggests:
pn  keychain  
pn  libpam-ssh
ii  monkeysphere  0.42-2
ii  ssh-askpass   1:1.2.4.1-10

-- Configuration Files:
/etc/ssh/ssh_config changed [not included]

-- no debconf information

Bug#765017: SECURITY - normal users are allowed full access to USB devices per default

[Daniel Kahn Gillmor]

Is it possible that libspice-client-glib-2.0-8 should merely Recommend:
spice-client-glib-usb-acl-helper, rather than Depend: ing on it?

spice-client-glib-usb-acl-helper is one of the few setuid binaries on
debian systems, and if it isn't installed, it seems like the attack
surface would be reduced.

I'd be a perfectly happy spice-client user *without* the ability to
redirect USB devices to the VM i'm playing with, if it meant i didn't
have to worry about yet another setuid binary on my system.

 --dkg


signature.asc
Description: PGP signature

Bug#911973: poor config file support

[Harald Dunkel]

Package: gerbera
Version: 1.1.0+dfsg-2+b2
Severity: wishlist

Modifying the gerbera/config.xml is *more* than painful. xml was
made to be written and read by machines, not humans.

To improve means of configuration it would be very helpful if gerbera
could support the usual "option = value" syntax known from 99% of all
other config files. Not to mention the usual comment lines starting
with '#'.

This could help to make the configuration guide easier to read, too.


Just a suggestion, of course.

Regards
Harri

Bug#908117: RFP: yq -- yq is a lightweight and portable command-line YAML processor The aim of the project is to be the jq or sed of yaml files.

[Antoine Beaupré]

On 2018-10-26 14:55:28, Antoine Beaupré wrote:
> In any case, someone should probably let those upstreams know about the
> naming conflict.

Done:

https://github.com/kislyuk/yq/issues/41
https://github.com/mikefarah/yq/issues/189

we'll see how that flies.

That said, how is packaging going? :)

A.

Bug#911972: greenbone-security-assistant Default-Start contains no runlevels

[Frederik Himpe]

Package: greenbone-security-assistant
Version: 7.0.3+dfsg.1-1
Severity: normal

Dear Maintainer,

Trying to prevent greenbone-security-assistant from starting by default,
fails with this error:

# systemctl disable greenbone-security-assistant
Synchronizing state of greenbone-security-assistant.service with SysV service 
script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable 
greenbone-security-assistant
update-rc.d: error: greenbone-security-assistant Default-Start contains no 
runlevels, aborting.


-- System Information:
Debian Release: 9.5
  APT prefers stable
  APT policy: (600, 'stable'), (550, 'proposed-updates'), (500, 'oldstable'), 
(450, 'oldstable-proposed-updates'), (420, 'testing'), (200, 'unstable'), (160, 
'experimental'), (150, 'oldoldstable'), (140, 'oldoldstable-proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-3-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 greenbone-security-assistant depends on:
ii  greenbone-security-assistant-common  7.0.3+dfsg.1-1
ii  libc62.27-6
ii  libgcrypt20  1.8.3-1
ii  libglib2.0-0 2.50.3-2
ii  libgnutls30  3.5.19-1
ii  libmicrohttpd12  0.9.59-1
ii  libopenvas9  9.0.3-1+b1
ii  libxml2  2.9.4+dfsg1-2.2+deb9u2
ii  libxslt1.1   1.1.29-2.1
ii  lsb-base 9.20161125

greenbone-security-assistant recommends no packages.

greenbone-security-assistant suggests no packages.

-- no debconf information

Bug#911971: t50 builds with -march=native

[Adrian Bunk]

Source: t50
Version: 5.8.2-1
Severity: serious

t50 builds with -march=native, which makes the resulting binaries
only run on machines that are compatible with whatever buildd
built the package.

Please remove -march=native.

Bug#906211: lintian: python-script-but-no-python-dep despite Recommends

[Thorsten Glaser]

Hi Chris,

> > Just wondering what the next steps for Lintian are here?
> 
> Gentle ping on this?

sorry, this got lost in the INBOX pile.

As you pointed out, there’s currently no way to model
the right thing, given the implicit choice in the
shebang line.

So I think there’s nothing left to do for lintian
(feel free to close the bug if you agree), and I’ll
go with an override, for now. In this particular
case, being a Recommends, needed only for a helper
script shipped by the package, and given that half
the package relationship matches, I think that’s ok.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#911970: spoa builds with -march=native

[Adrian Bunk]

Source: spoa
Version: 1.1.3-2
Severity: serious

spoa builds with -march=native, which makes the resulting binaries
only run on machines that are compatible with whatever buildd
built the package.

Please remove -march=native.

Bug#880475: internal lintian shlib error running lintian -F on gcc-8-cross_1_amd64-changes

[Chris Lamb]

Niels Thykier wrote:

>  * @Matthias; can you confirm whether the binary is as intended?

Matthias, did you see this? Just doing some Lintian bug triage here.


Regards,

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

Bug#908117: RFP: yq -- yq is a lightweight and portable command-line YAML processor The aim of the project is to be the jq or sed of yaml files.

[Antoine Beaupré]

On 2018-09-06 12:29:37, Varac wrote:
> Package: wnpp
> Severity: wishlist
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> * Package name: yq
>   Version : 2.1.2
>   Upstream Author : Mike Farah 
> * URL : http://mikefarah.github.io/yq/
> * License : MIT License
>   Programming Lang: Go
>   Description : yq is a lightweight and portable command-line YAML 
> processor The aim of the project is to be the jq or sed of yaml files.

Just for the record, there's also a Python implementation, also called
yq, which also handles XML:

https://yq.readthedocs.io/en/latest/

I think it's slightly more interesting because it does more than just
YAML.. But maybe the python one should be called "xq" (or "xyq"?)
instead. ;)

In any case, someone should probably let those upstreams know about the
naming conflict.

A.

-- 
Be who you are and say what you feel
Because those who mind don't matter
And those who matter don't mind.
 - Dr. Seuss

Bug#856128: debian-watch-may-check-gpg-signature: false positives

[Chris Lamb]

Mattia Rizzolo wrote:

> Yes, if upstream does not publish gpg signatures, you are stuck with
> that tag.  You may override it if you wish so (I personally wouldn't),
> but the idea is that you should talk with upstream and "convince" him to
> start doing so.

Martin-Éric, does this resolve your query? If so, please go ahead and
close this bug. Thanks!


Regards,

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

Bug#911969: devscripts: more bad signal handling leading to insecure use of /tmp

[Jakub Wilk]

Package: devscripts
Version: 2.18.7
Tags: security

I've found quite a few bugs similar to #911720 in devscripts codebase. 
Here are excerpts of buggy code (with boring parts omitted):


* cvs-debi, cvs-debrelease:

  TEMPDIR=$(mktemp -dt cvs-debi.) || ...
  TEMPFILE=$TEMPDIR/cl-tmp
  trap "rm -f $TEMPFILE; rmdir $TEMPDIR" 0 1 2 3 7 10 13 15

* deb-reversion:

  TMPDIR=$(mktemp -d --tmpdir deb-reversion.XX)
  trap "rm -rf $TMPDIR" 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

* debsign:

  trap "cleanup_tmpdir" EXIT HUP INT QUIT KILL SEGV PIPE TERM

  mksigningdir () {
  ...
  signingdir="$(mktemp -dt debsign.)" || ...
  ...
  }
  
  mkremotefilesdir () {

  ...
  remotefilesdir="$(mktemp -dt debsign.)" || ...
  ...
  }
  ...
  cleanup_tmpdir () {
  ... # removes $remotefilesdir and $signingdir, but doesn't exit
  }

* dscextract:

  WORKDIR=$(mktemp -d --tmpdir dscextract.XX)
  trap "rm -rf $WORKDIR" 0 2 3 15

* getbuildlog:

  ALL_LOGS=`mktemp`
  trap "rm -f $ALL_LOGS" EXIT INT QUIT TERM

* mergechanges:

  OUTPUT=`tempfile`
  DESCFILE=`tempfile`
  trap "rm -f '${OUTPUT}' '${DESCFILE}'" 0 1 2 3 7 10 13 15

* pts-subscribe:

  TEMPFILE=$(mktemp) || ...
  trap "rm -f '$TEMPFILE'" 0 1 2 3 7 10 13 15

* wnpp-alert:

  INSTALLED=`mktemp -t wnppalert-installed.XX`
  trap "rm -f '$INSTALLED'" 0 1 2 3 7 10 13 15
  WNPP=`mktemp -t wnppalert-wnpp.XX`
  WNPPTMP=`mktemp -t wnppalert-wnpp.XX`
  trap "rm -f '$INSTALLED' '$WNPP' '$WNPPTMP'" 0 1 2 3 7 10 13 15
  WNPP_PACKAGES=`mktemp -t wnppalert-wnpp_packages.XX`
  trap "rm -f '$INSTALLED' '$WNPP' '$WNPPTMP' '$WNPP_PACKAGES'" \
0 1 2 3 7 10 13 15

  ...

  WNPP_DIFF=`mktemp -t wnppalert-wnpp_diff.XX`
  trap "rm -f '$INSTALLED' '$WNPP' '$WNPPTMP' '$WNPP_PACKAGES' 
'$WNPP_DIFF'" \
0 1 2 3 7 10 13 15

* wnpp-check:

  WNPP=`mktemp -t wnppcheck-wnpp.XX`
  WNPPTMP=`mktemp -t wnppcheck-wnpp.XX`
  trap "rm -f '$WNPP' '$WNPPTMP'" 0 1 2 3 7 10 13 15
  WNPP_PACKAGES=`mktemp -t wnppcheck-wnpp_packages.XX`
  trap "rm -f '$WNPP' '$WNPPTMP' '$WNPP_PACKAGES'" \
0 1 2 3 7 10 13 15

--
Jakub Wilk

Bug#911968: gvpe: missing build dependency on pkg-config

[Adrian Bunk]

Source: gvpe
Version: 3.3.1-1
Severity: serious
Tags: ftbfs

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

...
checking for nanosleep... yes
checking for library containing floor... -lm
checking for linux/if_tun.h... default
./configure: line 8330: syntax error near unexpected token `LIBCRYPTO,'
./configure: line 8330: `PKG_CHECK_MODULES(LIBCRYPTO, libcrypto >= 1)'

Bug#879722: lintian: W-shlibs-symbol-not-found: false positive

[Chris Lamb]

Chris Lamb wrote:

> > dpkg-shlibdeps: warning: symbol __aeabi_atexit@CXXABI_ARM_1.3.3 used by 
> > debian/libkyotocabinet16v5/usr/lib/arm-linux-gnueabi/libkyotocabinet.so.16.13.0
> >  found in none of the libraries
> 
> I'm not sure I understand your report, sorry. :)  These are warnings
> from dpkg-shlibdeps, not in Lintian. Also, there is no such tag
> "shlibs-symbol-not-found" in Lintian, and nor has there ever been
> one similar.

Gentle ping on this Shawn… ?


Regards,

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

Bug#890468: lintian: source-is-missing false positive when d/missing-sources/foo is a symlink

[Chris Lamb]

Chris Lamb wrote:

> Thanks for the bug report but unfortunately I think I'm either
> parsing the problem incorrectly or think we are handling this
> correctly already. I've added a testcase here:
> 
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=2c09091df0c8425e96ac2104b6f49fab8f1f7b10

Gentle ping on this?


Regards,

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

Bug#898721: lintian -- maybe false positive on description-starts-with-package-name

[Chris Lamb]

Chris Lamb wrote:

> > I am not sure whether this is a good english expression, but if so, this 
> > is a false positive:
> > 
> > Description: base58 encode/decode: command-line interface
> 
> It's "valid" but very clunky. Could you suggest they use, for example:
> 
>   command-line interface to encode and decode base58 integers
> 
> ?
> 
> Moreover, I'm not sure what pattern would deterministically detect
> this as a false-positive...

Gentle ping on this? Just trying to work out what to do next with respect to
Lintian and this bug number.


Regards,

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

Bug#898867: lintian: embedded-php-library libmarkdown-php vs. php-markdown confusion

[Chris Lamb]

Hey Thorsten,

> > Let's await input from the markdown maintainers themselves - I have
> > not used these libraries.
>
> indeed, just mind that Nik and I just took over php-markdown by request
> of Florian, the former maintainer.

Sure. Did you get a reply on this? Would be nice to make some
progress on this bug either way...


Regards,

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

Bug#906211: lintian: python-script-but-no-python-dep despite Recommends

[Chris Lamb]

Chris Lamb wrote:

> tags 906211 + moreinfo
> thanks
> 
> Chris Lamb wrote:
> 
> > If you want to keep using Python 2.x then simply leaving the script as-
> > is and recommending only python (ie. Python 2.x) is the correct
> > solution here.
> > 
> > Once this customer moves to (and is comfortable with) deploying Python
> > 3, you can update the shebang and the Recommends.
> > 
> > "Silencing" Lintian is not the correct approachas "python | python3"
> > is, alas, simply not correct.
> 
> Just wondering what the next steps for Lintian are here?

Gentle ping on this?


Regards,

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

Bug#903669: lintian -- false positive on using-first-person-in-description

[Chris Lamb]

Hi Thorsten,

> So, as it happens, the fix for #891794 was actually to /remove/ that
> correction rather than add an exception for that correction.. :) But you
> are right that Lintian does have some exception lists.
> 
> However, this one just "feels" too esoteric and package-specific.
> Please override :)

Would you be happy closing this bug in Lintian?


Regards,

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

Bug#906281: lintian: Severity and Certainty of emacsen-common-without-dh-elpa are wrong / false positives despite "Certainty: certain"

[Chris Lamb]

Chris Lamb wrote:

> tags 906281 + moreinfo
> thanks
> 
> Hi all,
> 
> > lintian: Severity and Certainty of emacsen-common-without-dh-elpa
> > are wrong / false positives despite "Certainty: certain"
> 
> So, what are the next, concrete, steps for Lintian here? I don't
> currently see a consensus...?

Gentle ping on this folks?


Regards,

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

Bug#909239: lintian: ancient-python-version-field is wrong

[Chris Lamb]

Chris Lamb wrote:

> > I found these warning very misleading, and IMO, they should be removed,
> 
> To clarify, by "these warnings" you mean the one emitted by py{,3}
> versions and not the Lintian warnings?
> 
> > Now, why exactly is your autopkgtests failing? This isn't clear at all
> > in your bug report.
> 
> Without the "allow-stderr" flag, autopkgtests will fail if they emit
> anything to standard error. If possible, it is best to leave this at
> the default as it catches various non-fatal errors that are worth
> knowing about.
> 
> (I am guessing that the py{,3} versions warning emits to this output
> stream and thus the apt (?) tests fail.)

Gentle ping on this?


Regards,

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

Bug#909696: lintian: debian-rules-should-not-use-custom-compression-settings overzealously also reports -Zgzip

[Chris Lamb]

Chris Lamb wrote:

> tags 909696 + moreinfo
> thanks
> 
> Axel Beckert wrote:
> 
> > according to the bugreport https://bugs.debian.org/829100 this tag was
> > primarily meant to catch too high xz compression settings. Also the
> > lintian long description seems to be targetted towards that case.
> 
> (CCing the submitter of #906614 for their input as this is the salient
> recent change.)

Gentle ping on this?


Regards,

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

Bug#893864: dependency fixed

[Teus Benschop]

A new version of Xiphos was uploaded to Debian just now.
It no longer depends on libwebkitgtk.
If that works out well, then Xiphos can migrate to testing normally.
It will required a couple of days from now on.

-- 
Teus Benschop
teusjanne...@gmail.com
0318 712046

Bug#911967: libedlib FTBFS on architectures where char is unsigned

[Adrian Bunk]

Source: libedlib
Version: 1.2.3-3
Severity: important
Tags: ftbfs

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

...
/<>/test/runTests.cpp: In function 'bool test11()':
/<>/test/runTests.cpp:415:62: error: narrowing conversion of 
'-127' from 'int' to 'char' inside { } [-Wnarrowing]
 char query[8] =  {-127, 127, -55, 0, 42, 0,  127, -55};
  ^
/<>/test/runTests.cpp:415:62: error: narrowing conversion of '-55' 
from 'int' to 'char' inside { } [-Wnarrowing]
/<>/test/runTests.cpp:415:62: error: narrowing conversion of '-55' 
from 'int' to 'char' inside { } [-Wnarrowing]
/<>/test/runTests.cpp:416:62: error: narrowing conversion of 
'-127' from 'int' to 'char' inside { } [-Wnarrowing]
 char target[8] = {-127, 127,  0, 42, 0, -55, 127,  42};
  ^
/<>/test/runTests.cpp:416:62: error: narrowing conversion of '-55' 
from 'int' to 'char' inside { } [-Wnarrowing]
make[3]: *** [CMakeFiles/runTests.dir/build.make:66: 
CMakeFiles/runTests.dir/test/runTests.cpp.o] Error 1

Bug#866657: dependency fixed

[Teus Benschop]

A new version of Xiphos was uploaded just now.
It no longer depends on libwebkitgtk.
If it works out fine, then soon Xiphos can be migrated to testing again.

-- 
Teus Benschop
teusjanne...@gmail.com
0318 712046

Bug#911965: kicad: Add libngspice to dependancy list

[Carsten Schoenert]

Hello Matsievskiy,

Am 26.10.18 um 20:07 schrieb Matsievskiy S.V.:
> Circuit simulator depends on libngspice.so, provided by a libngspice0-dev
> package but it's not in the dependency list. So, libngspice0-dev it should be
> included in it. Or, better yet, libngspice0 should be fixed to symlink its
> libngspice.so.0 file to libngspice.so and be added to dependency list instead
> of the development package.

partially correct.
KiCad in Debian now supports ngspice based simulations provided by the
library libngspice.so.0.0.0 from the package libngspice0.

The question is why the packaging doesn't detect this dependency
automatically ... I will have a look.

-- 
Regards
Carsten Schoenert