Bug#941467: marked as pending in samba

2019-10-02 Thread Mathieu Parent
Control: tag -1 pending

Hello,

Bug #941467 in samba reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/samba-team/samba/commit/50178f6cd1de0ef874a32cecec3ea3a7ee5e1da4


Force one job during configure step with -j 1 (Closes: #941467)

Not setting -j leads to default which is number of cpus.

See 
https://salsa.debian.org/samba-team/samba/blob/478603e68024a9c352072c20e0f4f712dd4c5a1c/third_party/waf/waflib/Options.py#L177-212


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941467



Processed: Bug#941467 marked as pending in samba

2019-10-02 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #941467 [src:samba] samba: FTBFS on armel, armhf, mipsel
Added tag(s) pending.

-- 
941467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#905206: Do you have some spare cycles to have a look at this (Was: profnet is marked for autoremoval from testing)

2019-10-02 Thread Andreas Tille
Hi Shayan,

more pinging the bug to extend the period the package stays in testing but
in case you might have any temporary results for this issue feel free to
post these here.

Kind regards, Andreas.

On Sat, Sep 21, 2019 at 07:05:27PM +0200, Andreas Tille wrote:
> Hi Shayan,
> 
> On Sat, Sep 21, 2019 at 05:23:49PM +0100, Shayan Doust wrote:
> > This is new territory - I have spent some time looking at this and so far I
> > could only reproduce all of what was already mentioned above.
> 
> It might become time consuming.
>  
> > I will later go more in-depth and try using mem profiling / debugging and
> > some trial and error to try figure out why this gets a segmentation fault
> > because this issue is really annoying and needs rectifying.
> 
> In any case yes. While I guess the program is not used in really security
> relevant context you can never know and this kind of crash is a security
> issue (besides the fact that it just does not the job its supposed to do).
> 
> Thanks for working at this
> 
>   Andreas. 
> 
> -- 
> http://fam-tille.de
> 

-- 
http://fam-tille.de



Bug#941467: fixed in samba 2:4.11.0+dfsg-7

2019-10-02 Thread Mathieu Parent
Le jeudi 3 octobre 2019, Jeremy Bicha  a écrit :
> Control: reopen 941467
>
> Oops, it looks like this fix didn't work either.

Argh!

At least ldb is now fixed.

>
> https://buildd.debian.org/status/package.php?p=samba
>
> Thanks,
> Jeremy
>

-- 
Mathieu


Processed: notfound 941124 in erlang/1:22.0.7+dfsg-3

2019-10-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 941124 erlang/1:22.0.7+dfsg-3
Bug #941124 [src:erlang,src:elixir-lang] elixir-lang (autopkgtest) fails with 
new erlang
Ignoring request to alter found versions of bug #941124 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
941124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#933573: Bug#933548: transition: gnome-desktop3

2019-10-02 Thread Jeremy Bicha
On Wed, Oct 2, 2019 at 3:00 PM Paul Gevers  wrote:
> If my view of things is
> up-to-date and correct, it's the last piece of the puzzle

There are also several autopkgtest failures triggered by glib2.0 and
gobject-introspection.

Jeremy



Bug#941552: marked as done (stealth: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Oct 2019 00:34:33 +
with message-id 
and subject line Bug#941552: fixed in stealth 4.02.00-2
has caused the Debian Bug report #941552,
regarding stealth: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
941552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: stealth
Version: 4.02.00-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Dear maintainers,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru stealth-4.02.00/debian/control stealth-4.02.00/debian/control
--- stealth-4.02.00/debian/control  2019-07-24 20:31:05.0 -0700
+++ stealth-4.02.00/debian/control  2019-10-01 15:10:03.0 -0700
@@ -9,7 +9,7 @@
icmake (>= 9.02.04),
yodl (>= 4.02.00)
 Build-Depends-Indep: texlive-latex-base,
-   texlive-generic-recommended,
+   texlive-plain-generic,
texlive-latex-recommended,
texlive-fonts-recommended,
texlive-latex-extra,
--- End Message ---
--- Begin Message ---
Source: stealth
Source-Version: 4.02.00-2

We believe that the bug you reported is fixed in the latest version of
stealth, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated stealth package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Oct 2019 16:57:49 -0700
Source: stealth
Architecture: source
Version: 4.02.00-2
Distribution: unstable
Urgency: medium
Maintainer: Frank B. Brokken 
Changed-By: tony mancill 
Closes: 941552
Changes:
 stealth (4.02.00-2) unstable; urgency=medium
 .
   * Replace build-dep on texlive-generic-recommended with
 texlive-plain-generic (Closes: #941552)
   * Bump Standards-Version to 4.4.1
Checksums-Sha1:
 a6866f2f282d6520ab0d66362a0f40c7bb37df23 2229 stealth_4.02.00-2.dsc
 6f9ccc9fcc8f6df5847177e6286acbb5b3426bb7 10200 stealth_4.02.00-2.debian.tar.xz
 eef0e2e3535ca0bb2b968398a6039102182d6104 9439 stealth_4.02.00-2_amd64.buildinfo
Checksums-Sha256:
 4d0a6de0dfe92ba9413ef99245ed64e0699100d0b3467ed253da06c936f8b56d 2229 
stealth_4.02.00-2.dsc
 700af350c567efa63f31c39e5731909efba271d091c66ddb7ec18f53a45b7851 10200 
stealth_4.02.00-2.debian.tar.xz
 3a150f7e1a73fc0bf3ec73c5282d7a2b687b106c9da63d973d9dac19d44cdc7b 9439 
stealth_4.02.00-2_amd64.buildinfo
Files:
 183e442200a0881f8a22f7a9f4ba44f0 2229 admin optional stealth_4.02.00-2.dsc
 67c981c8fc7f056d02f1eee763c93c19 10200 admin optional 
stealth_4.02.00-2.debian.tar.xz
 2dd1d53b5e3c6610b2b7595459b98824 9439 admin optional 
stealth_4.02.00-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl2VPg0UHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZXoBAAqpB8krZknQOLxxqeV/fURibh6pMJ
M0nVL9blKYLIr9niIAh/2lmK1Gq0YnnNGTjjyQMsJgxulXWFQFCUQ04DzW4ybtM7
PLRWoavMAC5BfqOndVS/U3+Ci6dXSYszkf10sJ7Ww/QgDufxTe+tGI4HhoSrnAgc
tiuiPsXRdUUXXdBxMvfes53pnz5N9Arhalj/2qD4um/kH9t54HxnRzQsRVgFr7Hk
xB6lHFs+RjCT8GPlJ3S/rA3VGFJz7VBLMiHG84scpYpcIjhyC7L57CKl/9vlKdA/
96mApRKd+ugcMHVOUEWLh89TEi0LnAIHPnVgTW7S9ZVCZLhSpjJjTF0VecgAGtKG
TCdFa5n46GXvs82i3lhdU+7xmPXJyvZkKJaIeB2YCcqOgHcmBuqILy3Yr3HEo/2m
tfFCo+4lKysuMd1wiHTRIIV7eUZqM1JUj0vVJfd/LlpIPJ83MNLSqjnsTbbhmUey
4Xo7hVE2FRn6BuS8S37yR7jucL2mUFarPzaCWEFLY4wMrcCmQEJG9uLHA8/XkijS
cHEsLyZSv5mbq2W9dM0WBvR3NIxWVB1I/qErPS/TUQifA1rtXnERDrYmNHbzbK/0
LCLXDTff4l8VlgXqIMGAsc2RZsz2Jwm8MyGHQ7ShTrT4GTnJHSi7wj3NlrVhsgQ6
lvBOlT1EoEYdj0g=
=k4kT
-END PGP 

Bug#941467: fixed in samba 2:4.11.0+dfsg-7

2019-10-02 Thread Jeremy Bicha
Control: reopen 941467

Oops, it looks like this fix didn't work either.

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

Thanks,
Jeremy



Processed: Re: Bug#941467: fixed in samba 2:4.11.0+dfsg-7

2019-10-02 Thread Debian Bug Tracking System
Processing control commands:

> reopen 941467
Bug #941467 {Done: Mathieu Parent } [src:samba] samba: 
FTBFS on armel, armhf, mipsel
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions samba/2:4.11.0+dfsg-7.

-- 
941467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#936764: marked as done (jhbuild: Python2 removal in sid/bullseye)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Oct 2019 00:19:04 +
with message-id 
and subject line Bug#936764: fixed in jhbuild 3.35.1-1
has caused the Debian Bug report #936764,
regarding jhbuild: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
936764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jhbuild
Version: 3.15.92+20180504~8974bbc4-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:jhbuild

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: jhbuild
Source-Version: 3.35.1-1

We believe that the bug you reported is fixed in the latest version of
jhbuild, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 936...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated jhbuild package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Oct 2019 19:55:22 -0400
Source: jhbuild
Architecture: source
Version: 3.35.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 936764
Changes:
 jhbuild (3.35.1-1) unstable; urgency=medium
 .
   * New upstream release
   * Build with python3 (Closes: #936764)
   * Set $HOME for dh_auto_test
Checksums-Sha1:
 8535792479349d0c682d604744ee4e8de0aa5726 2076 jhbuild_3.35.1-1.dsc
 318afb491cf9699daffc88e4c46c9638606ee6b1 1006804 jhbuild_3.35.1.orig.tar.xz
 a49460824752578fd2cb100aa51c9d596931871a 5936 jhbuild_3.35.1-1.debian.tar.xz
 84d80502af84a48933aeb9d09e649379efa722d0 10714 
jhbuild_3.35.1-1_source.buildinfo
Checksums-Sha256:
 12b58ef3997f47916a6cd7691116834031b111f71735f30bffd3638420e43fc9 2076 
jhbuild_3.35.1-1.dsc
 6ee681fcd6868360653a1cfb935d727b327a33ab3aa78b5b1ec6c7eed5cf1ace 1006804 
jhbuild_3.35.1.orig.tar.xz
 d218bb844052e263ee9320eae4f09a9ab19a4243b2d9080083e23013ecfe3a00 

Bug#941511: marked as done (c++-annotations: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Oct 2019 00:04:09 +
with message-id 
and subject line Bug#941511: fixed in c++-annotations 11.1.1-2
has caused the Debian Bug report #941511,
regarding c++-annotations: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
941511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: c++-annotations
Version: 11.1.1-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Dear maintainers,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency (and Recommends)
to texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru c++-annotations-11.1.1/debian/control 
c++-annotations-11.1.1/debian/control
--- c++-annotations-11.1.1/debian/control   2019-05-17 11:15:04.0 
-0700
+++ c++-annotations-11.1.1/debian/control   2019-10-01 11:34:47.0 
-0700
@@ -7,7 +7,7 @@
 Build-Depends: debhelper (>= 12)
 Build-Depends-Indep: icmake (>= 9.02.07), yodl (>= 4.02.00),
 libbobcat-dev (>= 4.08.05), flex, zip, texlive-latex-base,
-texlive-generic-recommended, texlive-latex-recommended,
+texlive-plain-generic, texlive-latex-recommended,
 texlive-fonts-recommended, texlive-latex-extra, ghostscript,
 libfl-dev
 Standards-Version: 4.3.0
--- End Message ---
--- Begin Message ---
Source: c++-annotations
Source-Version: 11.1.1-2

We believe that the bug you reported is fixed in the latest version of
c++-annotations, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated c++-annotations package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Oct 2019 16:40:59 -0700
Source: c++-annotations
Architecture: source
Version: 11.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Frank B. Brokken 
Changed-By: tony mancill 
Closes: 941511
Changes:
 c++-annotations (11.1.1-2) unstable; urgency=medium
 .
   * Replace build dependency on texlive-generic-recommended with
 texlive-plain-generic (Closes: #941511)
   * Bump Standards-Version to 4.4.1
   * Freshen years in debian/copyright
Checksums-Sha1:
 9621ed52918bcaae57bd80cc7fbeae4ef4b0119c 2752 c++-annotations_11.1.1-2.dsc
 cfee0a006b693c1ede924748458bb6b15e4ecfa0 7820 
c++-annotations_11.1.1-2.debian.tar.xz
 3034dea4e92f98085c0489333c7bd8ab9436d0b1 5 
c++-annotations_11.1.1-2_amd64.buildinfo
Checksums-Sha256:
 dfeb6dbe567f13a87659dc96626dc4f7f030247a93278c4b78068cdec15cc7d6 2752 
c++-annotations_11.1.1-2.dsc
 54b2fd4eb5e7a2e16b7dd853eed122d65306d6e955449e8527aca4f14ea83bf4 7820 
c++-annotations_11.1.1-2.debian.tar.xz
 eecd27fc37b073707c3534e3653594198243b302ea810d28f5094ae0feb4fd74 5 
c++-annotations_11.1.1-2_amd64.buildinfo
Files:
 9b3274acbc1d5b08797d4d194b111caa 2752 doc optional c++-annotations_11.1.1-2.dsc
 ecdbcc4ec34116303e3a8ea729112749 7820 doc optional 
c++-annotations_11.1.1-2.debian.tar.xz
 3b2053bb549eaa6b42bb9368131c0da4 5 doc optional 
c++-annotations_11.1.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl2VOMgUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpbBRw/+PPC4kwYFo5azBfJM+ltdI4lug29g
9Zwq1oQXXVtD4eJ+BUHOXefca4RqFWqLoib7cwMMULfHw2783cfDKWHYGeFibQeF
VB8X+g03FzByJ7+6Zhrh3K5bMc5PRDNB7Ig9W8d6M/2qfE5mxrb7UY3EyRejMfL/
mn1hU9OHfo0qg3Y8lRdnv5/JYa1+vkS8+Dt/epSs+Rg7ssuBXMhgHnYJxt0FDagz
9D1fBIh/mYCapGeniTpNY5afPzCikHVP1uXm1OFaP8JLwMy0JU+5t3UruEwJx7jF
e3/MhfnC2iFOkEvPWyKoH2w3e8BEy2WtsvjUISoTzzm/nq60cK655DdyNXM1n7al

Bug#936764: marked as pending in jhbuild

2019-10-02 Thread Jeremy Bicha
Control: tag -1 pending

Hello,

Bug #936764 in jhbuild reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/jhbuild/commit/b5bdcf2a81d5f9099613b0356cfd782ae862dc66


Build with python3

Closes: #936764


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/936764



Processed: Bug#936764 marked as pending in jhbuild

2019-10-02 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #936764 [src:jhbuild] jhbuild: Python2 removal in sid/bullseye
Added tag(s) pending.

-- 
936764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#941554: marked as done (yodl: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 22:35:26 +
with message-id 
and subject line Bug#941554: fixed in yodl 4.02.01-3
has caused the Debian Bug report #941554,
regarding yodl: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
941554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yodl
Version: 4.02.01-2
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Dear maintainers,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru yodl-4.02.01/debian/control yodl-4.02.01/debian/control
--- yodl-4.02.01/debian/control 2019-08-05 17:45:27.0 -0700
+++ yodl-4.02.01/debian/control 2019-10-01 15:14:05.0 -0700
@@ -7,7 +7,7 @@
 Standards-Version: 4.4.0
 Homepage: https://gitlab.com/fbb-git/yodl
 Build-Depends: debhelper (>= 12), icmake (>= 9.02.07),
- texlive-latex-base, texlive-generic-recommended,
+ texlive-latex-base, texlive-plain-generic,
  texlive-latex-recommended, texlive-fonts-recommended,
  texlive-latex-extra,  ghostscript
 Build-Depends-Indep: cm-super-minimal
--- End Message ---
--- Begin Message ---
Source: yodl
Source-Version: 4.02.01-3

We believe that the bug you reported is fixed in the latest version of
yodl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Frank B. Brokken  (supplier of updated yodl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Oct 2019 09:54:34 +0200
Source: yodl
Architecture: source
Version: 4.02.01-3
Distribution: unstable
Urgency: medium
Maintainer: Frank B. Brokken 
Changed-By: Frank B. Brokken 
Closes: 941554
Changes:
 yodl (4.02.01-3) unstable; urgency=medium
 .
   * Updated the Build-Depends list (Closes: #941554)
   * Bump Standards-Version to 4.4.1
Checksums-Sha1:
 82e569933b237237a0ffd3492e0447dced95377f 2140 yodl_4.02.01-3.dsc
 49a4997c1e794302b35f8631642d7d255ba08c8e 11444 yodl_4.02.01-3.debian.tar.xz
 ef441bbad2e933876cc0d539dd4769a088c3fe3d 9279 yodl_4.02.01-3_amd64.buildinfo
Checksums-Sha256:
 fe0c049d395dea3ee726da2a31b33d3fd3b7dbbb5acfa7ee4845f93a0cdb17f8 2140 
yodl_4.02.01-3.dsc
 73c86318f16733581898852ddb43b9ccab7b2d352715c71d216519a7da8e6b51 11444 
yodl_4.02.01-3.debian.tar.xz
 d267486c35ac2e07b3c9d2c235e4f21e086cfc16eba2da5457ce35e9fc27a0d4 9279 
yodl_4.02.01-3_amd64.buildinfo
Files:
 dc49109d0c0fde42f4ba01eba011def2 2140 text optional yodl_4.02.01-3.dsc
 dc6146af7a5000e74c8f54ba07f2ea57 11444 text optional 
yodl_4.02.01-3.debian.tar.xz
 16851d91e5b6e1719d4a363c033826eb 9279 text optional 
yodl_4.02.01-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl2VIjsUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpafahAAqA+lzPKZBYtWEdzdYaefeZ3oS06/
BJMFQVAAIXZ1T8Lvihhe6hnE+XSVHt1ZlN/8DwRtF8ct8msz/sfSmp3dQ3HOStmC
szrEVFHvqkJHLZqEf0mi/oMsqO2kCKlMZLl1aQZeXPh5TJISC1Ioi2YanSLrfbY0
zkdE572oc6lTjnIYMl+xVmdffLqJAYzVITpTs+9mtcUZ6cjDyjcEmRyVVvFxxRQI
Qgw2ZyuWwSMTw/iFCaxIvpl1f5JN2/kj9Dflb+lEi2yzCDfOPFPFvwM0seZXt812
KZ8w+pyKmpq9TBTn9IYd0itoBNsBmzZYLZMd3CAS484gz3btsm/FvMF4K5x+aXrX
KHvhU5DeIpOZcgfLjhUEJAucDXTGjZCpqGXVbEDsu/c94NQNkonWvuKgS9xzGskQ
hYdhm9kToHsI0NITvUl5kiKLM+p/W/fZqdWYfD8cu+TIbR4W28mx42JdL1tHxl8f
fiKS294yUafyhp4QEZf7X6SWN8TTPXZNmDJbuWqjhpGsG/DhTFR4tEz5/7BLV91H
P1LHqRrOPM++b61T/728+0Pn9cK8zAFYSvTBIHnR/TgqNvmpGy9qCnNyP/anb2YB
ZBENovxRJ3uFCCSeR87q3BCNY0yquD9HnUr+zKASHBwBHgzlBCjEwaBXOydieieg
bpv0ta51X2kxh2g=
=iANm
-END PGP SIGNATURE End Message ---


Bug#941559: libxvidcore4: immediately crashes on amd64 since binNMU

2019-10-02 Thread James Cowgill
Hi,

On 02/10/2019 11:47, Fabian Greffrath wrote:
> Hi James,
> 
> Am 02.10.2019 01:45, schrieb James Cowgill:
>> Indeed readelf contains some non-executable program headers in
>> 2:1.3.5-1+b1 which do not appear in 2:1.3.5-1 in buster. The
>> ".rotext" section sounds suspicious.
> 
> indeed, the check_cpu_feature() function is defined in
> src/utils/x86_asm/cpuid.asm [1] which includes src/nasm.inc, which in
> turn declares a .rotext section [2] for any other output format than
> macho32 and macho64.
> 
> It would probably be the best patch this to simply declare a .text
> section for all output formats. The question remains, however, why this
> is an issue now but not when xvidcore_2:1.3.5-1 was uploaded?

I had a play around and I think this is caused by the "-z separate-code"
option being enabled by default in binutils >= 2.31. With that option
binutils will put "text" and "rodata" into different segments.
Previously it bundled both of those (along with any other read only
data) into a single executable segment.

Second bullet point in the announcement:
https://sourceware.org/ml/binutils/2018-07/msg00213.html

In theory that also means the bug affects buster if the package is ever
rebuilt / updated there.

James



signature.asc
Description: OpenPGP digital signature


Bug#941619: ruby-odbc: ODBC dlopen regression in Debian 10

2019-10-02 Thread Amit Brahmbhatt
Package: ruby-odbc
Version: 0.8-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)

Simple execution of Ruby (2.5) on Buster (Debian-10) fails with;

server:~/work/misc/tools/tdutils$ ./dump-customer-list.rb | grep -i hulu
Traceback (most recent call last):
6: from ./dump-customer-list.rb:7:in `'
5: from /home/abrahmbhatt/work/misc/tools/tdutils/td-customers.rb:33:in
`load'
4: from /home/abrahmbhatt/work/misc/libs/ruby/makeTdConnection.rb:6:in
`makeTdConnection'
3: from /usr/lib/ruby/vendor_ruby/dbi.rb:137:in `connect'
2: from /usr/lib/ruby/vendor_ruby/dbi/handles/driver.rb:33:in `connect'
1: from /usr/lib/ruby/vendor_ruby/dbd/odbc/driver.rb:15:in `connect'
/usr/lib/ruby/vendor_ruby/dbd/odbc/driver.rb:36:in `rescue in connect': INTERN
(0) [RubyODBC]Cannot allocate SQLHENV (DBI::DatabaseError)
server:~/work/misc/tools/tdutils$ ruby -v
ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux-gnu]
server:~/work/misc/tools/tdutils$

/usr/include/ruby-2.5.0/ruby/ruby.h:2197:12: error: invalid operands to binary
/ (have ‘int’ and ‘char *’)
 ((vari)/(!fmt[ofs] || rb_scan_args_bad_format(fmt)))
^~~~

And pages and pages more errors.  That first one at least appears to have been
fixed as:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889025
ruby-odbc: FTBFS with ruby2.5: invalid operands to binary / (have 'char *' and
'char *')

Subject: Bug#889025: fixed in ruby-odbc 0.8-1

However, as noted by https://rubygems.org/gems/rdbi-driver-odbc/versions/0.1.2:

0.1.2 - December 15, 2010 (6 KB)
0.1.1 - December 14, 2010 (6 KB)
0.1.0 - December 08, 2010 (5.5 KB)
RUNTIME DEPENDENCIES (2):
rdbi ~> 0.9
ruby-odbc = 0.2

That's hardcoded an unfixed version of ruby-odbc.  The upstream project:

https://github.com/semmons99/rdbi-driver-odbc

... appears to have become moribund in 2011.  There's only one Issue, open or
closed, and no sign of any fix.

With Google's help, we trial-and-errored our way to:


server:~/download/rdbi-driver-odbc$ git diff
diff --git a/Rakefile b/Rakefile
index 5180ca5..067f31d 100644
--- a/Rakefile
+++ b/Rakefile
@@ -27,8 +27,8 @@ rescue LoadError
 end

 begin
-  require 'rake/gempackagetask'
-  Rake::GemPackageTask.new(gemspec) do |pkg|
+  require 'rubygems/package_task'
+  Gem::PackageTask.new(gemspec) do |pkg|
 pkg.gem_spec = gemspec
   end
   task :gem => :gemspec
@@ -45,3 +45,7 @@ desc "Validate the gemspec"
 task :gemspec do
   gemspec.validate
 end
+
+task :default => :gem do
+  puts "generated latest version"
+end
diff --git a/lib/rdbi/driver/odbc.rb b/lib/rdbi/driver/odbc.rb
index 29ab15e..f1b5338 100644
--- a/lib/rdbi/driver/odbc.rb
+++ b/lib/rdbi/driver/odbc.rb
@@ -1,6 +1,6 @@
 require 'rdbi'
 require 'rubygems'
-gem 'ruby-odbc', '= 0.4'
+gem 'ruby-odbc', '>= 0.4'
 require 'odbc'
 require 'time'

diff --git a/rdbi-driver-odbc.gemspec b/rdbi-driver-odbc.gemspec
index dafc3ad..ca635ee 100644
--- a/rdbi-driver-odbc.gemspec
+++ b/rdbi-driver-odbc.gemspec
@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name= "rdbi-driver-odbc"
-  s.version = "0.1.2"
+  s.version = "0.1.2.77"
   s.platform= Gem::Platform::RUBY
   s.authors = ["Shane Emmons"]
   s.email   = "semmon...@gmail.com"
@@ -11,7 +11,7 @@ Gem::Specification.new do |s|
   s.required_rubygems_version = ">= 1.3.6"

   s.add_dependency "rdbi",  "~> 1"
-  s.add_dependency "ruby-odbc", "= 0.4"
+  s.add_dependency "ruby-odbc", ">= 0.4"

   s.add_development_dependency "rdbi-dbrc", "~> 0.1"
   s.add_development_dependency "rspec", "~> 2"
server:~/download/rdbi-driver-odbc$

... which was enough to get "rake" to agree to make a gem.  That installed
seamlessly.  This was then enough to try to use it:

server:~/work/misc/libs/ruby$ bk diffs
= CommonDbi.rb 1.1 vs edited =
--- 1.1/libs/ruby/CommonDbi.rb2013-06-24 21:37:30 -07:00
+++ edited/libs/ruby/CommonDbi.rb2019-09-30 16:24:04 -07:00
@@ -2,5 +2,5 @@

 $PREVIOUS_VERBOSE = $VERBOSE
 $VERBOSE = false
-require "dbi"
+require "rdbi-driver-odbc"
 $VERBOSE = $PREVIOUS_VERBOSE
= makeTdConnection.rb 1.8 vs edited =
--- 1.8/libs/ruby/makeTdConnection.rb2013-06-24 21:37:30 -07:00
+++ edited/libs/ruby/makeTdConnection.rb2019-09-30 16:23:45 -07:00
@@ -3,7 +3,7 @@
 require "CommonDbi"

 def makeTdConnection()
-return DBI.connect("dbi:ODBC:TestDirector", "devTDdb", "devtest")
+return RDBI.connect(:ODBC, :db => "TestDirector", :user => "devTDdb",
:password => )
 end

 if __FILE__ == $0
server:~/work/misc/libs/ruby$

... which promptly failed with the same error we had from the old stuff:
server:~/work/misc/libs/ruby$ ./makeTdConnection.rb
/var/lib/gems/2.5.0/gems/rdbi-1.1.0/lib/rdbi/types.rb:178: warning: constant
::Fixnum is deprecated
Traceback (most recent call last):
7: from ./makeTdConnection.rb:10:in 

Bug#936764: jhbuild: Python2 removal in sid/bullseye

2019-10-02 Thread Christoph Reiter
On Mon, 30 Sep 2019 00:00:01 +0200 Christoph Reiter
 wrote:
> On Sun, Sep 29, 2019 at 11:38 PM Jeremy Bicha  wrote:
> > It's easier to package from a tarball release than to do a git
> > snapshot, so I will probably wait for a 3.35 release to package the
> > new py3 jhbuild.
>
> OK, I'll create a release next week.

Done: https://download.gnome.org/sources/jhbuild/3.35/



Bug#941467: [Pkg-samba-maint] Bug#941467: fixed in samba 2:4.11.0+dfsg-6

2019-10-02 Thread Mathieu Parent
Le mer. 2 oct. 2019 à 21:12, Paul Gevers  a écrit :
>
> Control: reopen 941467
>
> On Tue, 01 Oct 2019 21:07:24 + Mathieu Parent 
> wrote:
> >  samba (2:4.11.0+dfsg-6) unstable; urgency=medium
> >  .
> >* Do not run waf configure in parallel. Fix FTBFS on arm (Closes: 
> > #941467)
>
> Apparently this wasn't enough to fix the failures, as armel, armhf and
> mipsel still FTBFS.

Only armel and armhf were affected by this FTBFS. And this is fixed in
-7 (I forgot about make lazy vars).


> Additionally mips64el and ppc64el now have an
> unfulfilled Build-Depends. This is the remaining blocker in the
> gnome-desktop3/mutter/evolution-data-server transition.

Yes. This is also in progress (ldb 2:2.0.7-3 is coming soon).


Regards

-- 
Mathieu Parent



Bug#940963: marked as done (samba doesn't start anymore)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 19:21:03 +
with message-id 
and subject line Bug#940963: fixed in samba 2:4.11.0+dfsg-7
has caused the Debian Bug report #940963,
regarding samba doesn't start anymore
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
940963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.10.8+dfsg-1
Severity: normal


This server runs sysvinit!

[2019/09/22 12:44:28.672896,  0] ../../source3/smbd/server.c:1850(main)
  server role = 'active directory domain controller' not compatible with 
running smbd standalone. 
  You should start 'samba' instead, and it will control starting smbd if 
required
[2019/09/22 12:44:30.809747,  0] ../../source3/nmbd/nmbd.c:921(main)
  server role = 'active directory domain controller' not compatible with 
running nmbd standalone. 
  You should start 'samba' instead, and it will control starting the internal 
nbt server

smb.conf isn't modified since last successful start:

# Global parameters
[global]
workgroup = LXTEC
realm = HOME.LXTEC.NET
netbios name = TOY
server role = active directory domain controller
server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, 
winbind, ntp_signd, kcc, dnsupdate
idmap_ldb:use rfc2307 = yes
interfaces = ???.???.???.???

..

-- Package-specific info:
* /var/lib/samba/dhcp.conf not present

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

Kernel: Linux 4.19.75-toy-lxtec-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages samba depends on:
ii  adduser  3.118
ii  dpkg 1.19.7
ii  init-system-helpers  1.57
ii  libbsd0  0.10.0-1
ii  libc62.29-2
ii  libldb1  2:1.5.5-2
ii  libpam-modules   1.3.1-5
ii  libpam-runtime   1.3.1-5
ii  libpopt0 1.16-12
ii  libpython3.7 3.7.4-4
ii  libtalloc2   2.3.0-2
ii  libtdb1  1.4.2-2
ii  libtevent0   0.10.1-3
ii  libwbclient0 2:4.10.8+dfsg-1
ii  lsb-base 11.1.0
ii  procps   2:3.3.15-2+b1
ii  python3  3.7.3-1
ii  python3-dnspython1.16.0-1
ii  python3-samba2:4.10.8+dfsg-1
ii  samba-common 2:4.10.8+dfsg-1
ii  samba-common-bin 2:4.10.8+dfsg-1
ii  samba-libs   2:4.10.8+dfsg-1
ii  tdb-tools1.4.2-2

Versions of packages samba recommends:
ii  attr1:2.4.48-4
ii  logrotate   3.15.1-1
ii  samba-dsdb-modules  2:4.10.8+dfsg-1
ii  samba-vfs-modules   2:4.10.8+dfsg-1

Versions of packages samba suggests:
ii  bind9  1:9.11.5.P4+dfsg-5.1+b1
ii  bind9utils 1:9.11.5.P4+dfsg-5.1+b1
pn  ctdb   
ii  ldb-tools  2:1.5.5-2
ii  ntp1:4.2.8p13+dfsg-2
ii  smbldap-tools  0.9.9-1
pn  ufw
pn  winbind

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.11.0+dfsg-7

We believe that the bug you reported is fixed in the latest version of
samba, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 940...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathieu Parent  (supplier of updated samba package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Oct 2019 20:45:24 +0200
Source: samba
Architecture: source
Version: 2:4.11.0+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Samba Maintainers 
Changed-By: Mathieu Parent 
Closes: 940963 941467
Changes:
 samba (2:4.11.0+dfsg-7) unstable; urgency=medium
 .
   * Always evaluate WAF_NO_PARALLEL to ensure correct value (Closes: #941467)
   * This version is built with talloc from sid (Closes: #940963)
Checksums-Sha1:
 97fc84c3f81ef47835d2c5f42c76e6440c0b8f27 4313 

Bug#941467: marked as done (samba: FTBFS on armel, armhf, mipsel)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 19:21:03 +
with message-id 
and subject line Bug#941467: fixed in samba 2:4.11.0+dfsg-7
has caused the Debian Bug report #941467,
regarding samba: FTBFS on armel, armhf, mipsel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
941467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: samba
Version: 2:4.10.8+dfsg-1
Severity: serious
Justification: FTBFS

Dear Maintainer,

As you're probably well aware of the samba package fails to build  from
source on a few architectures in unstable (and I didn't see an open bug
report about it so I'm filing this for tracking/discussion purposes).

The problem has now become more problematic as the transitions related
to gnome 3.34 was started yesterday. The gnome-control-center package
build-depends on samba and is now thus blocked in "BD-Uninstallable".

As release-team resources are scarse and there are many other
transitions waiting we'll need to figure out a way to unblock things.
Ideas?

(I see the new upstream version in experimental also has build
issues...)

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.11.0+dfsg-7

We believe that the bug you reported is fixed in the latest version of
samba, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathieu Parent  (supplier of updated samba package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Oct 2019 20:45:24 +0200
Source: samba
Architecture: source
Version: 2:4.11.0+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Samba Maintainers 
Changed-By: Mathieu Parent 
Closes: 940963 941467
Changes:
 samba (2:4.11.0+dfsg-7) unstable; urgency=medium
 .
   * Always evaluate WAF_NO_PARALLEL to ensure correct value (Closes: #941467)
   * This version is built with talloc from sid (Closes: #940963)
Checksums-Sha1:
 97fc84c3f81ef47835d2c5f42c76e6440c0b8f27 4313 samba_4.11.0+dfsg-7.dsc
 f43baa1d6da062abd00d90197ccd37d32cbad80a 243544 
samba_4.11.0+dfsg-7.debian.tar.xz
 b836ed687ade68d5e870cb791659ecb858f79f5f 6153 
samba_4.11.0+dfsg-7_source.buildinfo
Checksums-Sha256:
 969129e19b3061a2f42a8a8015167bfbe3394731e53ec341b0de913bbc14430f 4313 
samba_4.11.0+dfsg-7.dsc
 9040c3b0d548344c40f1d108ea817f73eafc93e6d58c68031d3b107e713c7cdc 243544 
samba_4.11.0+dfsg-7.debian.tar.xz
 03f809e43225b8c5f6a6e870534c828b83c8424fce2a56c5f4d3178077257072 6153 
samba_4.11.0+dfsg-7_source.buildinfo
Files:
 2d954a1d490089b258afab7c3df189ae 4313 net optional samba_4.11.0+dfsg-7.dsc
 33f1a938e7a014481d5da221e146417e 243544 net optional 
samba_4.11.0+dfsg-7.debian.tar.xz
 63b41cdc3b17322647a4c642395c9992 6153 net optional 
samba_4.11.0+dfsg-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEqqWLhC6ILPQU4Lqxp8cqHHgrjD8FAl2U9GgTHHNhdGhpZXVA
ZGViaWFuLm9yZwAKCRCnxyoceCuMPzKaD/4mOuUGxjjSiVJeeohO5Tq2L+lNjlSv
fQ2hZHYFjQ2u6vRVdS2uVfYMfIUb+l7cHa7LiA6Vfct4gc9IgGcTqtN4usozDxmg
qX/JXDTHy1WlX1Pc59JuWH4mgcUSmr62lJUa8DRa8R1equJ4UL/VcDCv2JjBFPEw
pyVRyN2YYwAxJjjDdAKqJF6tV+g+xxjx1WfJmsXdy89m+W5Nr/LuJxc4HaqLpEV2
+3Q0865BfJeVWCeeSZB/z2RGvXec5lNqBkUZeRGf+ppMxs6ikASINwFDxptDt9hz
kFwgQWe4fP9vCMoIkaqGF9NJne0PJFUTB7EUOhr4xYzqs+JNfn51iJaDs+1kN+fM
HUuwuK+LS2mtEC+xrKnGdbAjxQl/li6aGom2HnI3UsAzu1jbmqncTxpWdcP/9IBX
7A+PBQn6Hkw7uA2ZeqJRSPCoFic9CvCVqgU8pssuqNkJEWlQFtW08MjSEaOr53sb
kPmL3I834IhS3msM61wDsMhDC8T7KQiZpo8+a4ejHla6m/OKxybiZC8C/OutGnSQ
y7dwywTIBkeR5uy/RdnNFL/N/wmtq7QHlzIZbPuzkqaA0/Tkjo4w3cElEWIH74yq
r8BRhBFFnnWTBgNbstabCw9T/KVSdy/Vv/GvrLhUgqTkPTJLy/L9Cm01YZkpjNq+
9ap06nXYsRtFlg==
=lGDk
-END PGP SIGNATURE End Message ---


Bug#941467: fixed in samba 2:4.11.0+dfsg-6

2019-10-02 Thread Paul Gevers
Control: reopen 941467

On Tue, 01 Oct 2019 21:07:24 + Mathieu Parent 
wrote:
>  samba (2:4.11.0+dfsg-6) unstable; urgency=medium
>  .
>* Do not run waf configure in parallel. Fix FTBFS on arm (Closes: #941467)

Apparently this wasn't enough to fix the failures, as armel, armhf and
mipsel still FTBFS. Additionally mips64el and ppc64el now have an
unfulfilled Build-Depends. This is the remaining blocker in the
gnome-desktop3/mutter/evolution-data-server transition.

Paul



signature.asc
Description: OpenPGP digital signature


Processed: Re: Bug#941467: fixed in samba 2:4.11.0+dfsg-6

2019-10-02 Thread Debian Bug Tracking System
Processing control commands:

> reopen 941467
Bug #941467 [src:samba] samba: FTBFS on armel, armhf, mipsel
Bug 941467 is not marked as done; doing nothing.

-- 
941467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: your mail

2019-10-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reopen 941467
Bug #941467 {Done: Mathieu Parent } [src:samba] samba: 
FTBFS on armel, armhf, mipsel
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions samba/2:4.11.0+dfsg-6.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
941467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#933573: Bug#933548: transition: gnome-desktop3

2019-10-02 Thread Paul Gevers
Hi,

On 02-10-2019 03:31, Jeremy Bicha wrote:
> https://bugs.debian.org/933573 has a patch for eweouz

If somebody could please do an upload that fixes eweouz, that would be
great, than we don't need to resort to removal. If my view of things is
up-to-date and correct, it's the last piece of the puzzle together with
the samba situation (assuming LO will just build on mips64el).

Paul



signature.asc
Description: OpenPGP digital signature


Bug#941538: marked as done (mathgl: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 18:50:01 +
with message-id 
and subject line Bug#941538: fixed in mathgl 2.4.4-4
has caused the Debian Bug report #941538,
regarding mathgl: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
941538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mathgl
Version: 2.4.4-3
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Dear maintainers,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru mathgl-2.4.4/debian/control mathgl-2.4.4/debian/control
--- mathgl-2.4.4/debian/control 2019-07-31 02:21:43.0 -0700
+++ mathgl-2.4.4/debian/control 2019-10-01 14:20:14.0 -0700
@@ -11,7 +11,7 @@
  python-numpy,
  qtwebengine5-dev [amd64 arm64 armhf i386 mipsel], 
  libwxgtk3.0-gtk3-dev,
- texinfo, texlive, texlive-generic-recommended, liblua5.1-dev, libxcursor-dev,
+ texinfo, texlive, texlive-plain-generic, liblua5.1-dev, libxcursor-dev,
  libgif-dev, libfontconfig1-dev, libqt5webkit5-dev,
  libhdf4-dev, chrpath, libxinerama-dev, libxmu-dev, libxi-dev, libhpdf-dev,
  mpi-default-dev, swig3.0, cmake, libxft-dev, liboctave-dev, fluid
--- End Message ---
--- Begin Message ---
Source: mathgl
Source-Version: 2.4.4-4

We believe that the bug you reported is fixed in the latest version of
mathgl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated mathgl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 Oct 2019 19:23:33 +0100
Source: mathgl
Architecture: source
Version: 2.4.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 941538
Changes:
 mathgl (2.4.4-4) unstable; urgency=medium
 .
   [ Alastair McKinstry ]
   * Switch from obsolete texlive-generic-recommended  to texlive-plain-generic
 Closes: #941538
   * Filter format-security warnings which break autogenerated code
   * Standard-Version: 4.4.1.0
Checksums-Sha1:
 79244fe0a602ab8306ac62d047d318536292b6c8 3159 mathgl_2.4.4-4.dsc
 54d9e07cf0cfc199f7b499e8c07156f1973d847a 14044 mathgl_2.4.4-4.debian.tar.xz
Checksums-Sha256:
 862c5eba8aac8ea23493307a0ef163d38032435101f3501e92ce5f54804bc0c3 3159 
mathgl_2.4.4-4.dsc
 65afc9369cc95b12770a0ffceecc9e28adc02fa6c1aa00f56438ae3e27280607 14044 
mathgl_2.4.4-4.debian.tar.xz
Files:
 451a0deb82477731cb5fba54d84aca86 3159 science optional mathgl_2.4.4-4.dsc
 2f4d478fe065c246def300108d94ae04 14044 science optional 
mathgl_2.4.4-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl2U7t4ACgkQy+a7Tl2a
06UIlxAAogtiUf4QysPTGUeRMKjetM6FUxm5TxMhxzkYuN/NmrV2GBD2mdBdVWwE
QMGecIEGvHZSAxB+qdr19MysTc/R7yCV+OcSpeqzyqo7GtBdIHDwimRtoLezEUgo
dpApvlVRZ0viL0vsXERzp01nifsFHXc/BPJoDdqyfGOLPSPmdH5X+ZHWVvfOG6za
N4HbO2Le+yJsBaGbxpqVTf4Ijt/4roxljllr6gN9FAHhoASdTx1qV6ZYBpXAMTYS
pHJfcamHI6mkfJkffTTEw4eog8n2H/ukZHuMzN7hobBmuTjeBZpPpyhVLJ2WGy/Q
HMTROlzGdijNS3JcSjZ/OXc5fsI+sAqe9NiZPsI/1gwRgnomsCW11K0IO6zFwsAv
Mc3fJNVfjw78rtCbooGmU8mgTL4D098ubD82LmqG4ffBTeNaff1r1uZMOm8c1xW8
dt3nRNLLtvX1EIW23N9KCyM8G0+Zws7DhTINXpI4r2nxCPKNHDmfrlWMMl9qvtoS
drpS4UvkIin+O78Pwfeqi44PAH0p7nHwEKJ/ZGW3Lwz5ZN23vlcBdxs50gMfEE+E
a2gWez4ZeZkhG2oEcWYLk54VP/diNzea1LRM0s/LSy99KVMX4BYRRdAt32A/QGiC
UJ+xG8HOMAU7B1UTdmIkUSyYoZLih5wMi1sdubHA5dC5mVsD+wY=
=NuW/
-END PGP SIGNATURE End Message ---


Bug#941526: gnutls28: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended

2019-10-02 Thread Andreas Metzler
Control: tags -1 pending

On 2019-10-01 Steve Langasek  wrote:
> Package: gnutls28
> Version: 3.6.9-5
> Severity: serious
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu eoan ubuntu-patch

> Dear maintainers,

> The texlive-generic-recommended transitional package has been dropped from
> texlive-base in sid.  Please update your build-dependency to
> texlive-plain-generic instead.
[...]

Hello Steve,

fixed in 3.6.10-2, stuck in NEW.

cu Andreas



Processed: Re: Bug#941526: gnutls28: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended

2019-10-02 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 pending
Bug #941526 [gnutls28] gnutls28: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) pending.

-- 
941526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#941536: marked as done (libgcrypt20: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 18:06:49 +
with message-id 
and subject line Bug#941536: fixed in libgcrypt20 1.8.5-3
has caused the Debian Bug report #941536,
regarding libgcrypt20: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
941536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgcrypt20
Version: 1.8.4-5
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Dear maintainers,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libgcrypt20-1.8.4/debian/control libgcrypt20-1.8.4/debian/control
--- libgcrypt20-1.8.4/debian/control2019-04-23 02:41:15.0 -0700
+++ libgcrypt20-1.8.4/debian/control2019-10-01 14:13:42.0 -0700
@@ -12,7 +12,7 @@
  libgpg-error-mingw-w64-dev,
  mingw-w64,
  texinfo (>= 4.6-0),
- texlive-generic-recommended,
+ texlive-plain-generic,
  texlive-latex-base
 Standards-Version: 4.3.0
 Vcs-Git: https://salsa.debian.org/gnutls-team/libgcrypt.git -b branch1.6
--- End Message ---
--- Begin Message ---
Source: libgcrypt20
Source-Version: 1.8.5-3

We believe that the bug you reported is fixed in the latest version of
libgcrypt20, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated libgcrypt20 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Oct 2019 19:37:25 +0200
Source: libgcrypt20
Architecture: source
Version: 1.8.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuTLS Maintainers 
Changed-By: Andreas Metzler 
Closes: 941536
Changes:
 libgcrypt20 (1.8.5-3) unstable; urgency=medium
 .
   * Switch b-d from texlive-generic-recommended to texlive-plain-generic.
 Closes: #941536
Checksums-Sha1: 
 36bc0ddab3322275e93eed70f8dea76e0a348cd8 2800 libgcrypt20_1.8.5-3.dsc
 6d6f2c4381a0cbab5cfb336c5565dff68e6361ac 29196 
libgcrypt20_1.8.5-3.debian.tar.xz
Checksums-Sha256: 
 ef350e54eb285cfe08436ff4ba637c1d7d29852cb5c03d694015dfb46e6c21d1 2800 
libgcrypt20_1.8.5-3.dsc
 3b6bdabf8b4cca03c4621a509d4685e7846e555db68372664d913cbccf0f55db 29196 
libgcrypt20_1.8.5-3.debian.tar.xz
Files: 
 3b8058474664194dcbb3cba77844fc35 2800 libs optional libgcrypt20_1.8.5-3.dsc
 f6fa74a7df8baad6b7d49f785fe6f312 29196 libs optional 
libgcrypt20_1.8.5-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAl2U4ZgACgkQpU8BhUOC
FIRgjg//al7CARaxtpF+gY1JwGtWPivE7FONVCPTwgvDiTxpoobxef/xYurkatk8
8OdX9CGjRHaN89kPMWV/AXhDh0T9Ad7AJyFZSh0T6f0ihalu4E+0v37Amn2g2ZIj
AApTw4YNKIsp+G+ZDPjbp5rfiBA2KUcoEVccoI2y1HuHzMAgFdU8RLBzyQQLwtGD
erqwjlUEwhXpsG/UKW9vQ8dzAdohdel40kU4e6pwtpLg70q2t2byIaba1uIRzARa
MCqVOe8XuGgFOmCbc6XaB0NfOVbhQE4eQ5GwfWnXm3Y5+nk5EnM6N2ESCxQrujaC
NL7CrsobvWtS12K9fbjv3qakn8U4X+mf3J/KTwJEd1lMJXnBTh46p8ljyYoo6zF2
P9QVHzA/qvVJ90wIPzT+okUes0wTQgAq2MGb+IwFExefcuOJJbCUOYyRXjaNNyro
Lt9lD9rtfnxVRRDaPfQ4bjGdzKOpKEjlRkH1Nc/nUcEN3Qu/ENIzUCQf2OP3/qVl
7WVqP0RBLKrmF51U6X1LnynQ6tSgih9VWhTHHLJUGjbszR5PUZufP+EWFr+Cualr
LENWrE0Mt02CH17vRbvREg471VW3bUYuTKO+PKOHka7EBNAZEkXR0cvqvWDXtMXl
hyyFZRsGuaooyrBuw1m9SIwzvdQGbzpJo+A4SqO2c5tq44OtV7Y=
=zGko
-END PGP SIGNATURE End Message ---


Bug#941519: marked as done (expeyes-doc: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 16:07:29 +
with message-id 
and subject line Bug#941519: fixed in expeyes-doc 4.3-2
has caused the Debian Bug report #941519,
regarding expeyes-doc: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
941519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: expeyes-doc
Version: 4.3-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Hi Georges,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru expeyes-doc-4.3/debian/control expeyes-doc-4.3/debian/control
--- expeyes-doc-4.3/debian/control  2017-09-30 14:19:24.0 -0700
+++ expeyes-doc-4.3/debian/control  2019-10-01 12:52:47.0 -0700
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Georges Khaznadar 
 Build-Depends: debhelper (>= 9), lyx,
- texlive-latex-base, texlive-latex-extra, texlive-generic-recommended,
+ texlive-latex-base, texlive-latex-extra, texlive-plain-generic,
  lmodern, imagemagick, librsvg2-bin
 Standards-Version: 4.1.0
 Homepage: http://expeyes.in
--- End Message ---
--- Begin Message ---
Source: expeyes-doc
Source-Version: 4.3-2

We believe that the bug you reported is fixed in the latest version of
expeyes-doc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated expeyes-doc 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 Oct 2019 17:24:13 +0200
Source: expeyes-doc
Architecture: source
Version: 4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 941519
Changes:
 expeyes-doc (4.3-2) unstable; urgency=medium
 .
   * replaced the dependency on texlive-generic-recommended by
 texlive-plain-generic. Closes: #941519
   * upgraded dh level and Standards-Version
Checksums-Sha1:
 a9c0ce442a9a40a17e793e8c583a2e16a2e34bcf 1981 expeyes-doc_4.3-2.dsc
 2e2c064bb44ea6c413944d0a8f2a8097de0ce9d0 45828 expeyes-doc_4.3-2.debian.tar.xz
 a8451dade878530f7eea4eaa9d488505ae5d83a8 13227 
expeyes-doc_4.3-2_source.buildinfo
Checksums-Sha256:
 485e3a1ac5ea67c9fe28cf94f410ee67fd8cefd4da1ee47b2b7f75f0dd5aa4a2 1981 
expeyes-doc_4.3-2.dsc
 10e8cfe38f6e5de7f443d31231a29a12a893f696f30fced5cddf34725524 45828 
expeyes-doc_4.3-2.debian.tar.xz
 c369096e013f782b0b6cf58a7972f3b58411cabd84865f0096b6a7b2512db8cd 13227 
expeyes-doc_4.3-2_source.buildinfo
Files:
 f0345c68d2a13670f36dbd601c36127d 1981 science optional expeyes-doc_4.3-2.dsc
 95f35180c125346ef53ed9a0b668d106 45828 science optional 
expeyes-doc_4.3-2.debian.tar.xz
 fc0ffd53388d53ae1e8f7482be35ed3f 13227 science optional 
expeyes-doc_4.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAl2UxGYUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjkcjw/+LIz/UZvZeF4YBsAM1XTua8TX+iGB
7Li1ZLwfv9qrVvQN6/pKaKVE1kf9XZB2Efay+lbGBhIa45ZEfqLjYw0YwQ3zmnil
7w6t73+FBiAeMPcG9G27WBi8FCq5kQ6QSVlnShzA5McTGMlptSTB9c/wIyNk8UGd
TXTs9yijmJ8CiRSGUrP0N3cOd7gDqIXk9PgUJj0S/SbK1/9qc8PrLVGnIGwk0jL6
iq66uvQmTyv2DRvR5bRgmrDZ4ye1N0I7RXMMAUlzr5W2BjY4NCjZ4FmJ4oFqvYS8
uSqCzScB/aWvQFrIayN5t9u5gU+yGYJVh7YeyOOjVA7bTcHNtbNtDX8Jnitu38mM
ogty19s7i7k3ZL0d/MkNF8B4EVCbKMyDO/7HOXgBwOq60q2gg7+c3R/j3V3pkH5F
gZrCpn5T5tl3+Zkt7UyPZr1jyBT2xoSsG+YS44MoyGKSJi03FQmDFzsCIurw+vxY
OPN42YqQwwkxNrxzWxKfCxyi4PQRbxiFmXHWVZbcdUe0KbmQA0vfNqSIpFiM6e0/
e3d0pZ++ZbFABgkdT2l68cIozoxPDCp970XZ9PMX0M1XXHLURfMpPERID1JIREzP
1m0nqzHTPl0SOYBYr9CheAGghMgUHWSUpTQauyMpvHrH8zW/5mBla0a6KXAliU6k

Bug#940839: Same bug with 2.4.4

2019-10-02 Thread Gianpaolo Cugola
Same situation here with openshot 2.4.4 from debian sid. I have an intel gpu.



Bug#940159: marked as done (realmd: FTBFS with GLib 2.62: ERROR: missing test)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 15:50:01 +
with message-id 
and subject line Bug#940159: fixed in realmd 0.16.3-3
has caused the Debian Bug report #940159,
regarding realmd: FTBFS with GLib 2.62: ERROR: missing test
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
940159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: realmd
Version: 0.16.3-2
Severity: important
Tags: ftbfs bullseye sid patch fixed-upstream

When built against GLib 2.62, realmd FTBFS with test failures like this:

> make  check-TESTS
> make[4]: Entering directory '/<>'
> make[5]: Entering directory '/<>'
> ERROR: test-dn-util 1 - missing test
> ERROR: test-dn-util 2 - missing test
> ERROR: test-dn-util 3 - missing test
> ERROR: test-dn-util 4 - missing test
> ...

This is because it has essentially the same bug that was recently fixed
in gcr: its test scripts (taken from Cockpit) assume GLib tests default to
GTester output syntax (and translate it into TAP in a wrapper script), but
in GLib 2.62+, GLib tests default to TAP (which the wrapper cannot parse).

GLib 2.62 is currently only available in experimental, but we should
upload it to unstable soon.

Fixed upstream in:
https://gitlab.freedesktop.org/realmd/realmd/commit/5ae42c176e7bb550fc6cf10f29e75f58c733ae4f

smcv
>From 5ae42c176e7bb550fc6cf10f29e75f58c733ae4f Mon Sep 17 00:00:00 2001
From: Sumit Bose 
Date: Fri, 2 Aug 2019 12:10:43 +0200
Subject: [PATCH] Remove support for deprecated gtester format

Support for the already deprecated gtester format was remove from recent
versions of glib2 but the test still call the tab-gtester conversion
tool.

This patch removes tab-gtester and the tab format is used directly.

Related to https://gitlab.freedesktop.org/realmd/realmd/issues/21
---
 Makefile.am   |   3 +-
 build/tap-gtester | 204 --
 2 files changed, 1 insertion(+), 206 deletions(-)
 delete mode 100755 build/tap-gtester

diff --git a/Makefile.am b/Makefile.am
index 27e3494..4ffd5b4 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -161,7 +161,7 @@ endif
 #
 
 LOG_DRIVER = $(top_srcdir)/build/tap-driver
-LOG_COMPILER = $(top_srcdir)/build/tap-gtester
+LOG_COMPILER = sh -c '"$$0" "$$@" --tap'
 
 VALGRIND_ARGS = --trace-children=no --quiet --error-exitcode=33 \
 	--suppressions=valgrind-suppressions --gen-suppressions=all \
@@ -183,7 +183,6 @@ recheck-memory: valgrind-suppressions
 
 EXTRA_DIST += \
 	$(LOG_DRIVER) \
-	$(LOG_COMPILER) \
 	$(VALGRIND_SUPPRESSIONS) \
 	$(NULL)
 
diff --git a/build/tap-gtester b/build/tap-gtester
deleted file mode 100755
index bbda266..000
--- a/build/tap-gtester
+++ /dev/null
@@ -1,204 +0,0 @@
-#!/usr/bin/python3
-# This can also be run with Python 2.
-
-# Copyright (C) 2014 Red Hat, Inc.
-#
-# Cockpit is free software; you can redistribute it and/or modify it
-# under the terms of the GNU Lesser General Public License as published by
-# the Free Software Foundation; either version 2.1 of the License, or
-# (at your option) any later version.
-#
-# Cockpit is distributed in the hope that it will be useful, but
-# WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-# Lesser General Public License for more details.
-#
-# You should have received a copy of the GNU Lesser General Public License
-# along with Cockpit; If not, see .
-
-#
-# This is a test output compiler which produces TAP from GTest output
-# if GTest output is detected.
-#
-# Versions of glib later than 2.38.x output TAP natively when tests are
-# run with the --tap option. However we can't depend on such a recent
-# version of glib for our purposes.
-#
-# This implements the Test Anything Protocol (ie: TAP)
-# https://metacpan.org/pod/release/PETDANCE/Test-Harness-2.64/lib/Test/Harness/TAP.pod
-#
-
-import argparse
-import os
-import select
-import signal
-import subprocess
-import sys
-
-# Yes, it's dumb, but strsignal is not exposed in python
-# In addition signal numbers varify heavily from arch to arch
-def strsignal(sig):
-for name in dir(signal):
-if name.startswith("SIG") and sig == getattr(signal, name):
-return name
-return str(sig)
-
-
-class NullCompiler:
-def __init__(self, command):
-self.command = command
-
-def input(self, line):
-sys.stdout.write(line)
-
-def process(self, proc):
-while True:
-line = proc.stdout.readline()
-if not line:
- 

Bug#935294: marked as done (realmd: FTBFS on amd64)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 15:50:01 +
with message-id 
and subject line Bug#935294: fixed in realmd 0.16.3-3
has caused the Debian Bug report #935294,
regarding realmd: FTBFS on amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
935294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:realmd
version: 0.16.3-2
severity: serious
tags: ftbfs

Hi,

A binnmu of realmd in unstable fails on amd64:

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

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: realmd
Source-Version: 0.16.3-3

We believe that the bug you reported is fixed in the latest version of
realmd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 935...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated realmd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 Oct 2019 17:26:19 +0200
Source: realmd
Architecture: source
Version: 0.16.3-3
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Laurent Bigonville 
Closes: 935294 938339 940159
Changes:
 realmd (0.16.3-3) unstable; urgency=medium
 .
   [ Andreas Henriksson ]
   * Switch to using python3 during build (Closes: #938339)
   * Cherry-pick patch from upstream to fix test failure (Closes: #935294)
 .
   [ Laurent Bigonville ]
   * Fix FTBFS with glib 2.62 (patch from upstream) (Closes: #940159)
   * debian/control: Bump Standards-Version to 4.4.1 (no further changes)
   * Bump debhelper compatibility to 12
Checksums-Sha1:
 1907524a50cf629256053e92e6b6c9889b206155 1763 realmd_0.16.3-3.dsc
 765dddb210ebcc679ca0dc3ad638623ef47f7194 25892 realmd_0.16.3-3.debian.tar.xz
 781e5a6a49936de0b5461e1aa16891257cc50002 6235 realmd_0.16.3-3_source.buildinfo
Checksums-Sha256:
 7b4562d78f01f3d799cc3a207608aa68051c03fd941421ea334d0b5fba5c6a66 1763 
realmd_0.16.3-3.dsc
 da934b3c88f62c5331681408e8590217f31f052f2682abfa27e2143e3bbceda6 25892 
realmd_0.16.3-3.debian.tar.xz
 5fbcbcf8476b52e88fe02df77f8530f68d8eea3d1e3e08c42522e4589b511480 6235 
realmd_0.16.3-3_source.buildinfo
Files:
 376dea1174bbf70caffe01f0f6990b18 1763 admin optional realmd_0.16.3-3.dsc
 a817cc1d202f6c2102a99f39deaf77ba 25892 admin optional 
realmd_0.16.3-3.debian.tar.xz
 59bf4fa199b883b16c7d6e344f86a7d1 6235 admin optional 
realmd_0.16.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl2UwbARHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9XJeQf/QDiPAhsSnl+/JRyOu+IkU033nWG1dIQ9
glcsKx1+/juaPuDJFMLt+h1g1Q+Jz/9g08M93EPGsa30hJ41gMv4t1wLR+km/Fa9
99QrDRSd2W7eXE9H5yubKu+Ctwenk7cAeeij5xj+N3b665KuKQOQbq+SUsQIKKyQ
LPvs6Q11IMPe8rppLdYuidt8hpE8TfxgS5+UyPkpkig+UUif52HRWNS/eyqNhJkT
2C4oqy8/IQmaNTTV3Ex9r6Xd1LrpZQ7WNrahwmuIa5u4GpLM8MwIeWGJpZUZ/yS+
m/bCFfw0ngxC/Vm2A/h3L2jP7GHmIFB529K1oOQPmtCYO5yJxXC+LQ==
=aq2P
-END PGP SIGNATURE End Message ---


Bug#941545: marked as done (pycode-browser: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 15:22:21 +
with message-id 
and subject line Bug#941545: fixed in pycode-browser 1:1.02+git20181006-5
has caused the Debian Bug report #941545,
regarding pycode-browser: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
941545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pycode-browser
Version: 1:1.02+git20181006-3
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Hi Georges,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru pycode-browser-1.02+git20181006/debian/control 
pycode-browser-1.02+git20181006/debian/control
--- pycode-browser-1.02+git20181006/debian/control  2019-01-06 
11:09:38.0 -0800
+++ pycode-browser-1.02+git20181006/debian/control  2019-10-01 
14:45:49.0 -0700
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Georges Khaznadar 
 Build-Depends: debhelper (>= 11.0.0), python-all, lyx,
- texlive-latex-base, texlive-generic-recommended,
+ texlive-latex-base, texlive-plain-generic,
  texlive-latex-recommended, texlive-fonts-recommended,
  cm-super-minimal
 Standards-Version: 4.2.1
--- End Message ---
--- Begin Message ---
Source: pycode-browser
Source-Version: 1:1.02+git20181006-5

We believe that the bug you reported is fixed in the latest version of
pycode-browser, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated pycode-browser 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 Oct 2019 16:49:42 +0200
Source: pycode-browser
Architecture: source
Version: 1:1.02+git20181006-5
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 941545
Changes:
 pycode-browser (1:1.02+git20181006-5) unstable; urgency=medium
 .
   * applied Steve Langasek's patch (thanks). Closes: #941545
Checksums-Sha1:
 9bfcc447c7671a26b26d84e53008afb238eb5138 2165 
pycode-browser_1.02+git20181006-5.dsc
 ce06a8adcb7d9b8d5e494cb19be8433edcc4ce2c 16864 
pycode-browser_1.02+git20181006-5.debian.tar.xz
 27de2d8820e4c724255972feea75e51d3426b829 10513 
pycode-browser_1.02+git20181006-5_source.buildinfo
Checksums-Sha256:
 eafbf12cf785af67f52aaab3108c5f9e7d6d5e8f9f602dfcd24e583f4c7d6e13 2165 
pycode-browser_1.02+git20181006-5.dsc
 cee2d46a1b6d47c7002dbb45707c2cbf256ae41b92719d2f74ab3b2ce0e3aa96 16864 
pycode-browser_1.02+git20181006-5.debian.tar.xz
 cca82ab009ab5f6ec4949ff0b426155dc2afe1982b85a9c096f6b18a25c839db 10513 
pycode-browser_1.02+git20181006-5_source.buildinfo
Files:
 fd95b4fc8bb46db73d3c777e113d5a4c 2165 education optional 
pycode-browser_1.02+git20181006-5.dsc
 b026b0a7d4bcadf511f80e73ccda6200 16864 education optional 
pycode-browser_1.02+git20181006-5.debian.tar.xz
 ae11610982a6acac36841cad03faed04 10513 education optional 
pycode-browser_1.02+git20181006-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAl2UuWQUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjmZrA/+KlnXDXwRthJMiy554BuIeEaKE9mu
srYnAlY8G3QuUFU8NPFrwhTfZfVTO9iNiAs2T1JZZZ4a+K+YrAzU91SXfIUGDixd
mHZMHixkVu86d4mIj3xWW9IPHr50tBscmFksjpNC4mY+gCrk0T48TQYvklN9U7nT
tXSb9e5sAanBVthYI+IV3z4D/LGSj4SmUDryvILrn/FJRkQQ5PCtJEIuP4U2IhUi
5MJHGd3v9pWjsdlDTaoKhL/KIoZtX6EIK7qfpsciXEk7T/bOZhzzyq0Bvme8MmLB
9Ru47DJJdz9L9nFS5e2MYjlJSZ3y2HYxm2XnkBoewvNpbXhHFjT8xm09kfh0c3/j
QXrNjpBPdiuqkdvjcBewvhQs+UrzTcfuzNvXderKEvyuF+cP9EKQ9TWKpaLEGTro

Bug#941542: [Pkg-electronics-devel] Bug#941542: ngspice: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended

2019-10-02 Thread Carsten Schoenert
Control: tags -1 + pending

Hello Steve,

Am 01.10.19 um 23:33 schrieb Steve Langasek:
> Dear maintainers,
> 
> The texlive-generic-recommended transitional package has been dropped from
> texlive-base in sid.  Please update your build-dependency to
> texlive-plain-generic instead.

thanks for the diff. I applied your modification.
I wasn't aware of this change.

-- 
Regards
Carsten Schoenert



Processed: Re: [Pkg-electronics-devel] Bug#941542: ngspice: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended

2019-10-02 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + pending
Bug #941542 [ngspice] ngspice: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) pending.

-- 
941542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#941591: binutils FTBFS: makeinfo failure

2019-10-02 Thread Norbert Preining
> binutils fails to build from source in unstable on amd64. A build log
> ends as follows:

Most probably a bug in texinfo 6.7.0.dfsg.2-2 which uses the XS parser,
which seems to be incomplete.

6.7.0.dfsg.2-3 is already uploaded and in sid which switches back to the
Perl parser, this should fix all the problems here.

Norbert

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



Bug#941592: plasma-discover FTBFS: dh_install: Cannot find (any matches for) "etc/dbus-1/system.d/org.kde.discover.libsnapclient.conf" (tried in ., debian/tmp)

2019-10-02 Thread Helmut Grohne
Source: plasma-discover
Version: 5.14.5.1-1
Severity: serious
Tags: ftbfs

plasma-discover fails to build from source in sbuild on amd64. A build
ends with:

| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
|dh_install -O--buildsystem=kf5
| dh_install: Cannot find (any matches for) 
"etc/dbus-1/system.d/org.kde.discover.libsnapclient.conf" (tried in ., 
debian/tmp)
| 
| dh_install: plasma-discover-backend-snap missing files: 
etc/dbus-1/system.d/org.kde.discover.libsnapclient.conf
| dh_install: missing files, aborting
| make: *** [debian/rules:12: binary] Error 255
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Reproducible by reproducible builds:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/plasma-discover_5.14.5.1-1.rbuild.log.gz

Helmut



Bug#941558: marked as done (check-manifest: autopkgtest failure with transitional bzr package.)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 14:34:39 +
with message-id 
and subject line Bug#941558: fixed in check-manifest 0.39-1
has caused the Debian Bug report #941558,
regarding check-manifest: autopkgtest failure with transitional bzr package.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
941558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: check-manifest
Version: 0.37-1
Tags: bullseye, sid
Severity: serious
x-debbugs-cc: b...@packages.debian.org

bzr recently became a transitional package to breezy (a fork of bzr), 
unfortunately this is causing the autopkgtest of check-manifest to fail.


==
ERROR: test_get_vcs_files (tests.TestBzr)
--
Traceback (most recent call last):
   File "/tmp/autopkgtest-lxc.97siff98/downtmp/build.JQe/src/tests.py", line 
900, in test_get_vcs_files
 self.assertEqual(get_vcs_files(),
   File 
"/tmp/autopkgtest-lxc.97siff98/downtmp/build.JQe/src/check_manifest.py", line 
480, in get_vcs_files
 return normalize_names(vcs.get_versioned_files())
   File 
"/tmp/autopkgtest-lxc.97siff98/downtmp/build.JQe/src/check_manifest.py", line 
405, in get_versioned_files
 output = run(['bzr', 'ls', '-VR'], encoding=encoding)
   File 
"/tmp/autopkgtest-lxc.97siff98/downtmp/build.JQe/src/check_manifest.py", line 
157, in run
 raise CommandFailed(command, status, output)
check_manifest.CommandFailed: ['bzr', 'ls', '-VR'] failed (status 3):
a.txt
b/
b/b.txt
b/c/
b/c/d.txt
brz: ERROR: [Errno 2] No such file or directory: '/home/debci/.config/breezy'

Can you fix your package and/or it's autopkgtest so that the transitional bzr 
package can migrate to testing?


--- End Message ---
--- Begin Message ---
Source: check-manifest
Source-Version: 0.39-1

We believe that the bug you reported is fixed in the latest version of
check-manifest, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sergio Durigan Junior  (supplier of updated check-manifest 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Oct 2019 10:10:14 -0400
Source: check-manifest
Binary: check-manifest
Architecture: source all
Version: 0.39-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sergio Durigan Junior 
Description:
 check-manifest - Tool to check the completeness of MANIFEST.in for Python 
packages
Closes: 941558
Changes:
 check-manifest (0.39-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
   * d/control: Remove ancient X-Python3-Version field.
 .
   [ Sergio Durigan Junior ]
   * New upstream version 0.39.
   * Depend on 'brz' (breezy) instead of 'bzr' (Bazaar).
 Bazaar is being deprecated, and breezy is the replacement for it.  We
 now depend on 'brz' (breezy) for our testing purposes.
   * Build-Depend on python3-toml.
   * Make sure we create $HOME/.config/breezy when testing breezy.
 (Closes: #941558)
   * Bump Standards-Version to 4.4.1.
   * Bump compat version to 12.
   * Cleanup d/watch file.
Checksums-Sha1:
 0efc262789151095913a7873d4a3c04fc9e162ab 2261 check-manifest_0.39-1.dsc
 b951fcd16b1bffeea785ab13a91d42a41c5fe42d 29794 check-manifest_0.39.orig.tar.gz
 e81c584c7ccedefaab9d5732382c6094de1f7e27 4404 
check-manifest_0.39-1.debian.tar.xz
 ed55dee0b52522de52dbded1e39ffcf03527d6e4 25484 check-manifest_0.39-1_all.deb
 980ade49927209cdecb0c0d78ab8feb2e96d4c16 7779 
check-manifest_0.39-1_amd64.buildinfo
Checksums-Sha256:
 15d9dbb15d2d9a0c7ed10ac63feee6f178f9aa1bde41ccddeaa325238d9266db 2261 
check-manifest_0.39-1.dsc
 8e00ad260ae2ad99732166bbe1fd39ae01172166d75537a9b82c4288f13c12a2 29794 
check-manifest_0.39.orig.tar.gz
 818ae9d87fa0167a77fb86aa7024fa8c82ca8acf6d4e52f533e1984e2e7c3c9f 4404 
check-manifest_0.39-1.debian.tar.xz
 5dfbdfdd5816b7c3b14bd4d0248934c54aa3fb0b98e05b6e8ab2324497c23324 25484 

Bug#934185: marked as done (libkscreenlocker5: fails to accept correct pin after entering pin less than 6 chars with libpam-poldi)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 14:37:13 +
with message-id 
and subject line Bug#934185: fixed in kscreenlocker 5.14.5-2
has caused the Debian Bug report #934185,
regarding libkscreenlocker5: fails to accept correct pin after entering pin 
less than 6 chars with libpam-poldi
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
934185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkscreenlocker5
Version: 5.14.5-1
Severity: grave
Justification: causes non-serious data loss

Greetings,

I am working on a machine that is configured to use libpam-poldi for
user authentication with GPG smart cards.

When the screen locker is engaged and the user enters a PIN that is under
six characters in length, two things happen:

  1. The screen locker will no longer accept a valid PIN.
  2. The /var/log/auth.log file fills up with "PIN too short" messages.

The messages in auth.log appear as below:

  Aug  2 09:10:46 hostname kcheckpass[9734]: PIN too short
  Aug  2 09:10:46 hostname kcheckpass[9734]: PIN too short
  Aug  2 09:10:46 hostname kcheckpass[9734]: PIN too short
  ...

This problem is clearly due to some issue at the boundary of kcheckpass
and libpam-poldi.  However, I am not yet able to determine which of the
two is responsible.

I have pulled down the source code of both packages, and I am actively
working on fixing the problem.  I can see where libpam-poldi obviously
will not accept a PIN less than 6 chars in length.  Refer to the
libpam-poldi source tree in the file...

  src/pam/auth-support/getpin-cb.c

to confirm this. 

Ideally, I would need to do the following to fix this issue:

  1. Compile libpam-poldi with debugging support.
  2. Compile kcheckpass with debugging support.
  3. Run kcheckpass with GDB to find where the conversation breaks down
 when a short PIN is provided.

This would tell us if the bug is with kcheckpass or with libpam-poldi.
Let me know if you can help me implement the plan of attack above,
especially if you can offer or refer me to instructions on building and
running kcheckpass from the shell.  That would be very helpful!

I am quite invested in fixing this, and I'll gladly help in any way
I can.  Please advise on a course of action.

Best wishes,
Jason Franklin

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable'), (100, 'unstable'), (10, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libkscreenlocker5 depends on:
ii  kpackagetool5  5.54.0-1
ii  libc6  2.28-10
ii  libkf5configcore5  5.54.0-1
ii  libkf5configgui5   5.54.0-1
ii  libkf5coreaddons5  5.54.0-1
ii  libkf5crash5   5.54.0-1
ii  libkf5declarative5 5.54.0-1
ii  libkf5globalaccel-bin  5.54.0-1
ii  libkf5globalaccel5 5.54.0-1
ii  libkf5i18n55.54.0-1
ii  libkf5idletime55.54.0-1
ii  libkf5notifications5   5.54.0-1
ii  libkf5package5 5.54.0-1
ii  libkf5quickaddons5 5.54.0-1
ii  libkf5waylandclient5   4:5.54.0-1
ii  libkf5waylandserver5   4:5.54.0-1
ii  libkf5windowsystem55.54.0-1
ii  libpam0g   1.3.1-5
ii  libqt5core5a   5.11.3+dfsg1-1
ii  libqt5dbus55.11.3+dfsg1-1
ii  libqt5gui5 5.11.3+dfsg1-1
ii  libqt5network5 5.11.3+dfsg1-1
ii  libqt5qml5 5.11.3-4
ii  libqt5quick5   5.11.3-4
ii  libqt5widgets5 5.11.3+dfsg1-1
ii  libqt5x11extras5   5.11.3-2
ii  libseccomp22.3.3-4
ii  libstdc++6 8.3.0-6
ii  libwayland-client0 1.16.0-1
ii  libwayland-server0 1.16.0-1
ii  libx11-6   2:1.6.7-1
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb11.13.1-2
ii  libxi6 2:1.7.9-1

Versions of packages libkscreenlocker5 recommends:
ii  kde-config-screenlocker  5.14.5-1

libkscreenlocker5 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: kscreenlocker
Source-Version: 5.14.5-2

We believe that the bug you reported is fixed in the latest version of
kscreenlocker, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please 

Bug#941591: binutils FTBFS: makeinfo failure

2019-10-02 Thread Helmut Grohne
Source: binutils
Version: 2.32.51.20190909-1
Severity: serious
Tags: ftbfs

binutils fails to build from source in unstable on amd64. A build log
ends as follows:

| restore=: && backupdir=".am$$" && \
| rm -rf $backupdir && mkdir $backupdir && \
| if (makeinfo --split-size=500 --split-size=500 --version) >/dev/null 
2>&1; then \
|   for f in as.info as.info-[0-9] as.info-[0-9][0-9] as.i[0-9] as.i[0-9][0-9]; 
do \
| if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
|   done; \
| else :; fi && \
| if makeinfo --split-size=500 --split-size=500 -I "../../../gas/doc" 
-I "../../../gas/../libiberty" -I "../../../gas/../bfd/doc" -I ../../bfd/doc  
-I ../../../gas/doc \
|  -o as.info `test -f 'as.texi' || echo '../../../gas/doc/'`as.texi; \
| then \
|   rc=0; \
| else \
|   rc=$?; \
|   $restore $backupdir/* `echo "./as.info" | sed 's|[^/]*$||'`; \
| fi; \
| rm -rf $backupdir; exit $rc
| touch as.1
| perl ../../../gas/doc/../../etc/texi2pod.pl -I "../../../gas/doc" -I 
"../../../gas/../libiberty" -I "../../../gas/../bfd/doc" -I ../../bfd/doc -Dman 
< ../../../gas/doc/as.texi > as.pod
| (pod2man --center="GNU Development Tools" --release="binutils-2.32.51" 
--section=1 as.pod | \
| sed -e '/^.if n .na/d' > as.1.T$$ && \
| mv -f as.1.T$$ as.1) || \
| (rm -f as.1.T$$ && exit 1)
| rm -f as.pod
| as.texi:37: bad name for @ifset
| as.texi:46: bad name for @ifset
| as.texi:651: warning: @include should only appear at the beginning of a line
| as.texi:651: warning: @include should not appear in @table
| as.texi:657: warning: @item should not appear in @table
| as.texi:657: @item outside of table or list
| as.texi:954: warning: @item should not appear in @table
| as.texi:954: @item outside of table or list
| as.texi:968: warning: @item should not appear in @table
| as.texi:968: @item outside of table or list
| as.texi:1059: warning: @cindex should only appear at the beginning of a line
| as.texi:1059: warning: @cindex should not appear in @table
| as.texi:1070: warning: @cindex should only appear at the beginning of a line
| as.texi:1070: warning: @cindex should not appear in @table
| as.texi:1257: warning: @item should not appear in @table
| as.texi:1257: @item outside of table or list
| as.texi:1376: warning: @item should not appear in @table
| as.texi:1376: @item outside of table or list
| as.texi:1377: warning: @itemx should not begin @table
| as.texi:1400: warning: @item should not appear in @table
| as.texi:1400: @item outside of table or list
| as.texi:1417: warning: @item should not appear in @table
| as.texi:1417: @item outside of table or list
| as.texi:1715: warning: @item should not appear in @table
| as.texi:1715: @item outside of table or list
| as.texi:1716: warning: @itemx should not begin @table
| as.texi:1834: warning: @item should not appear in @table
| as.texi:1834: @item outside of table or list
| as.texi:1835: warning: @itemx should not begin @table
| as.texi:1939: warning: @item should not appear in @table
| as.texi:1939: @item outside of table or list
| as.texi:2504: warning: @item should not appear in @table
| as.texi:2504: @item outside of table or list
| as.texi:7185: warning: @item should not appear in @table
| as.texi:7185: @item outside of table or list
| as.texi:7186: warning: @itemx should not begin @table
| as.texi:7670: bad name for @ifset
| c-alpha.texi:43: warning: @cindex should only appear at the beginning of a 
line
| c-alpha.texi:43: warning: @cindex should not appear in @table
| c-csky.texi:151: warning: @cindex should only appear at the beginning of a 
line
| c-csky.texi:151: warning: @cindex should not appear in @table
| as.texi:7885: bad name for @ifset
| c-i386.texi:57: warning: @cindex should only appear at the beginning of a line
| c-i386.texi:57: warning: @cindex should not appear in @table
| c-ppc.texi:39: warning: @item should not appear in @table
| c-ppc.texi:39: @item outside of table or list
| c-tilegx.texi:30: warning: @cindex should only appear at the beginning of a 
line
| c-tilegx.texi:30: warning: @cindex should not appear in @table
| c-visium.texi:33: warning: @cindex should only appear at the beginning of a 
line
| c-visium.texi:33: warning: @cindex should not appear in @table
| make[5]: *** [Makefile:507: as.info] Error 1
| make[5]: Leaving directory '/<>/builddir-single/gas/doc'
| make[4]: *** [Makefile:1274: all-recursive] Error 1
| make[4]: Leaving directory '/<>/builddir-single/gas'
| make[3]: *** [Makefile:816: all] Error 2
| make[3]: Leaving directory '/<>/builddir-single/gas'
| make[2]: *** [Makefile:4902: all-gas] Error 2
| make[2]: Leaving directory '/<>/builddir-single'
| make[1]: *** [Makefile:852: all] Error 2
| make[1]: Leaving directory '/<>/builddir-single'
| make: *** [debian/rules:647: stamps/build-single] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Likely this is some kind of regression in makeinfo. tex maintainers
Cced.

Helmut



Bug#941558: marked as pending in check-manifest

2019-10-02 Thread Sergio Durigan Junior
Control: tag -1 pending

Hello,

Bug #941558 in check-manifest reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/check-manifest/commit/a56de23a02ae4f7191ba2df9bb2894c0ff8d6218


Make sure we create $HOME/.config/breezy when testing breezy.

Closes: #941558


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941558



Processed: Bug#941558 marked as pending in check-manifest

2019-10-02 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #941558 [check-manifest] check-manifest: autopkgtest failure with 
transitional bzr package.
Added tag(s) pending.

-- 
941558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#941558: check-manifest: autopkgtest failure with transitional bzr package.

2019-10-02 Thread Sergio Durigan Junior
On Tuesday, October 01 2019, peter green wrote:

> bzr recently became a transitional package to breezy (a fork of bzr), 
> unfortunately this is causing the autopkgtest of check-manifest to fail.
>
>> ==
>> ERROR: test_get_vcs_files (tests.TestBzr)
>> --
>> Traceback (most recent call last):
>>File "/tmp/autopkgtest-lxc.97siff98/downtmp/build.JQe/src/tests.py", line 
>> 900, in test_get_vcs_files
>>  self.assertEqual(get_vcs_files(),
>>File 
>> "/tmp/autopkgtest-lxc.97siff98/downtmp/build.JQe/src/check_manifest.py", 
>> line 480, in get_vcs_files
>>  return normalize_names(vcs.get_versioned_files())
>>File 
>> "/tmp/autopkgtest-lxc.97siff98/downtmp/build.JQe/src/check_manifest.py", 
>> line 405, in get_versioned_files
>>  output = run(['bzr', 'ls', '-VR'], encoding=encoding)
>>File 
>> "/tmp/autopkgtest-lxc.97siff98/downtmp/build.JQe/src/check_manifest.py", 
>> line 157, in run
>>  raise CommandFailed(command, status, output)
>> check_manifest.CommandFailed: ['bzr', 'ls', '-VR'] failed (status 3):
>> a.txt
>> b/
>> b/b.txt
>> b/c/
>> b/c/d.txt
>> brz: ERROR: [Errno 2] No such file or directory: '/home/debci/.config/breezy'
> Can you fix your package and/or it's autopkgtest so that the transitional bzr 
> package can migrate to testing?

This is a bug on breezy.  It took me quite some time to understand what
is going on (I still don't know the full details) and to come up with a
fix.  It's basically a hack: check-manifest will create a
~/.config/breezy directory tree if it doesn't exist.  breezy absolutely
shouldn't fail if this directory isn't there, but unfortunately it
does.

I also decided to force $HOME to be /tmp, since it's not always possible
to guarantee that it will be set or be writable.

I'll upload a fixed package soon, but thought I'd let you know.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature


Bug#941432: [pkg-uWSGI-devel] Bug#941432: Bug#941432: Bug#941432: uwsgi-core: Dependency libmatheval is getting out of bullseye

2019-10-02 Thread Alexandre Rossi
> > > > Do you have plans/solutions regarding this issue? Is it possible 
> > > > to drop uwsgi-core dependency on libmatheval1?
> > > 
> > > It should be as simple as not building the matheval plugin which is 
> > > not critical to uwsgi. Should I go on with this?
> > 
> > Yeah, I just wasn't sure that it'd be an acceptable solution for you.
> > 
> > But it's perfectly fine with me. :)
> 
> Well, I would say "tolerable" rather than "acceptable" - it is a real 
> annoyance since it will directly remove features now offered in uwsgi.

upstream says in 1.9.20 changelog:

The matheval support has been removed, while a generic “matheval” plugin
(for internal routing) is available (but not compiled in by default).
See below for the new way for making “math” in config files.

> @Alexandre: Make sure to add a NEWS entry warning users of the removal 
> of matheval - ideally enumerating explicitly all uwsgi options which has 
> disappeared and may silently wreak havoc on local systems.
> 
> Also, better check e.g. with codesearch.debian.net if any packages rely 
> on matheval-related uwsgi config options, and if so alert them with 
> bugreports.

Search on "uwsgi matheval" or "uwsgi math" yields no result.

Thanks,

Alex



Bug#941432: [pkg-uWSGI-devel] Bug#941432: Bug#941432: uwsgi-core: Dependency libmatheval is getting out of bullseye

2019-10-02 Thread Jonas Smedegaard
[sent again with ASCII-only header, to not upset Debian mailservers]

Quoting Pierre-Elliott Bécue (2019-10-02 12:14:02)
> Le mercredi 02 octobre 2019 à 12:02:20+0200, Alexandre Rossi a écrit :
> > > uwsgi-core depends on libmatheval1, which future in the archive 
> > > seems compromised, this implies that src:uwsgi and all packages 
> > > which depend on it will get out of the archive sooner or later.
> > > 
> > > Do you have plans/solutions regarding this issue? Is it possible 
> > > to drop uwsgi-core dependency on libmatheval1?
> > 
> > It should be as simple as not building the matheval plugin which is 
> > not critical to uwsgi. Should I go on with this?
> 
> Yeah, I just wasn't sure that it'd be an acceptable solution for you.
> 
> But it's perfectly fine with me. :)

Well, I would say "tolerable" rather than "acceptable" - it is a real 
annoyance since it will directly remove features now offered in uwsgi.

...which reminds me...:

@Alexandre: Make sure to add a NEWS entry warning users of the removal 
of matheval - ideally enumerating explicitly all uwsgi options which has 
disappeared and may silently wreak havoc on local systems.

Also, better check e.g. with codesearch.debian.net if any packages rely 
on matheval-related uwsgi config options, and if so alert them with 
bugreports.


 - Jonas

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

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


signature.asc
Description: signature


Bug#940277: marked as done (FTBFS with recent PHPUnit (8))

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 11:04:28 +
with message-id 
and subject line Bug#940277: fixed in php-klogger 1.2.1-3
has caused the Debian Bug report #940277,
regarding FTBFS with recent PHPUnit (8)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
940277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-klogger
Version: 1.2.1-2
Severity: serious

Hi,

This package FTBFS with recent PHPUnit (8). Even if the fix may be
trivial, I open this bug report to see php-klogger removed from testing
(at least until it is actually used by Debian packages), unless there is
a good reason to keep it in Debian.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: php-klogger
Source-Version: 1.2.1-3

We believe that the bug you reported is fixed in the latest version of
php-klogger, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 940...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Valleroy  (supplier of updated php-klogger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Oct 2019 06:43:33 -0400
Source: php-klogger
Architecture: source
Version: 1.2.1-3
Distribution: unstable
Urgency: low
Maintainer: FreedomBox packaging team 

Changed-By: James Valleroy 
Closes: 940277
Changes:
 php-klogger (1.2.1-3) unstable; urgency=low
 .
   [ Sunil Mohan Adapa ]
   * Add patch to support phpunit v8 (Closes: #940277).
   * Update VCS URLs to salsa.debian.org.
   * Update debhelper compatibility to 12.
   * Update Standards-Version to 4.4.0.
   * Cleanup phpunit results cache file.
   * Add myself to list of uploaders.
 .
   [ James Valleroy ]
   * d/control: Add Rules-Requires-Root: no
   * d/watch: Replace template with project name
   * Add upstream/metadata
   * Add salsa-ci.yml
Checksums-Sha1:
 31cdb1de52c848404eb3ecf41442747d77b4788a 2143 php-klogger_1.2.1-3.dsc
 d8fcec9368638ab0e5cd8225f3381d0d29298bc0 3632 php-klogger_1.2.1-3.debian.tar.xz
 062cfca2784314b2c47011badbf2746b67e931ff 7340 
php-klogger_1.2.1-3_amd64.buildinfo
Checksums-Sha256:
 1e1d8b8676b903a4ccd95d5f1e23ace3f444cff6ac27e9b197f5e299ef9201e6 2143 
php-klogger_1.2.1-3.dsc
 f8061c2fa5e9633a861d5c6b68d80965594118533f9eb99ac2ff5e50fee6862c 3632 
php-klogger_1.2.1-3.debian.tar.xz
 3ff98a8c3f68b2617641cbf8770c1b18964e4f9c538ebf2ab2fd9a26ea82caaa 7340 
php-klogger_1.2.1-3_amd64.buildinfo
Files:
 752a13f7c2c53553d65cfe3522ae2d77 2143 php optional php-klogger_1.2.1-3.dsc
 f5c0ebecb5ac8bf1b4ac8361927bb59a 3632 php optional 
php-klogger_1.2.1-3.debian.tar.xz
 e478864e7f1371e6cda7625d4ff39767 7340 php optional 
php-klogger_1.2.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAl2UgSoWHGp2YWxsZXJv
eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICO9ND/94eSjcaJIiXAHJlNeXWI41NTqy
ZeU5xhSQo9CtXQubWOvfBqCUgBU1wGA9xXT3ZN3if8sKQCvQ5GGP5tI8qebz1vL5
hWs/c8FKoZWlTyB/Gc/msjZFskWdVHWL+kDdOGE+yHACTKfIDu2asqpEzUXpIuDk
mNKGFu4yZ8uGcLYn2VsAiA3Z5QRO1hkxJZRkaI2YnFP31gf2kgkHzViXsvfwM7dQ
sHIZ1X/6HDg3zFwAcoP5q+cPgVM2DbyBOX+nl0n8VccfGbm+T1u7ZVIMYp4tKy2g
pQYsDBjNPc3hLGfFFsLT790+fMP6S1bd6Snm6TfZErlSkydzz0Tynk6xvIMMKPzz
1TOtsqTyc4E6/UmmagqW3PgvX3Pa3QPAlL/XtKDxs7PG5ZrhFYpYyqYOz5+6wfsI
+mP+tZ7+RXvo2bzSz+o94yyIfZpc0LVG0w5ZjMpNQsZ6ZoPaQ4BCY6QVal7H4Lf8
YMKcckQf7GYbCnaKQPgKyp0JTkesZifYaFVau8qxNpA1N2Qq7W2HlnP//PEiPUqH
VQ4bh9YbyNmI3I9gTLKbQncmBGiXaOgBQBgyVRi1HB83b15RnJRxvaeDhXZroK3I
qOpwQvzDZbjNor3TWyigyzYkPUW9udeW9F+7+TgOrVZPEgXPbGHtEmb1fmmO+38L
Al38NZsfz1TYZFtw9A==
=FoYj
-END PGP SIGNATURE End Message ---


Bug#941559: libxvidcore4: immediately crashes on amd64 since binNMU

2019-10-02 Thread Fabian Greffrath

Hi James,

Am 02.10.2019 01:45, schrieb James Cowgill:

Indeed readelf contains some non-executable program headers in
2:1.3.5-1+b1 which do not appear in 2:1.3.5-1 in buster. The
".rotext" section sounds suspicious.


indeed, the check_cpu_feature() function is defined in 
src/utils/x86_asm/cpuid.asm [1] which includes src/nasm.inc, which in 
turn declares a .rotext section [2] for any other output format than 
macho32 and macho64.


It would probably be the best patch this to simply declare a .text 
section for all output formats. The question remains, however, why this 
is an issue now but not when xvidcore_2:1.3.5-1 was uploaded?


 - Fabian

[1] 
https://sources.debian.org/src/xvidcore/2:1.3.5-1/src/utils/x86_asm/cpuid.asm/?hl=94#L94

[2] https://sources.debian.org/src/xvidcore/2:1.3.5-1/src/nasm.inc/#L177



Bug#941551: marked as done (splash: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Oct 2019 10:35:28 +
with message-id 
and subject line Bug#941551: fixed in splash 2.9.0-2
has caused the Debian Bug report #941551,
regarding splash: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
941551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: splash
Version: 2.9.0-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Hi Ole,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru splash-2.9.0/debian/control splash-2.9.0/debian/control
--- splash-2.9.0/debian/control 2019-07-25 06:07:42.0 -0700
+++ splash-2.9.0/debian/control 2019-10-01 15:08:26.0 -0700
@@ -8,7 +8,7 @@
giza-dev,
help2man,
texlive-fonts-recommended,
-   texlive-generic-recommended,
+   texlive-plain-generic,
texlive-latex-base,
texlive-latex-recommended
 Standards-Version: 4.4.0
--- End Message ---
--- Begin Message ---
Source: splash
Source-Version: 2.9.0-2

We believe that the bug you reported is fixed in the latest version of
splash, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated splash package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Oct 2019 12:05:45 +0200
Source: splash
Architecture: source
Version: 2.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 941551
Changes:
 splash (2.9.0-2) unstable; urgency=medium
 .
   [ Steve Langasek ]
   * Build-depend on texlive-plain-generic (Closes: 941551)
 .
   [ Ole Streicher ]
   * Use FFLAGS provided by the system
   * Add gitlab-ci.yml for salsa
Checksums-Sha1:
 c082f2a624f5b2efb409ae1c38fbe61e3ee63334 2043 splash_2.9.0-2.dsc
 0aa606a9d2969b79dab05bcaf0692e4af08d2889 6120 splash_2.9.0-2.debian.tar.xz
Checksums-Sha256:
 3ff3ce3eb32178777cc29e5ab25fc00aa30ce95bdc1f53d374813ab42a771867 2043 
splash_2.9.0-2.dsc
 36a18a24651fbb721fcee0cc59a3a0ebb9b802a236f18f85e299279258c4acf6 6120 
splash_2.9.0-2.debian.tar.xz
Files:
 f064cea0a989cc309b89421d49a1f75c 2043 science optional splash_2.9.0-2.dsc
 35b025193d372be0541b812fe7ac6c9c 6120 science optional 
splash_2.9.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl2Ud00ACgkQcRWv0HcQ
3Pd3ng//U+JYcLilGQBfK3Po96YdRUxcgZRaqLhLDkflMExhisJ/EMUligxl52Pk
Io10aNYx0mIdtkSAZQl+mXv01iasiRUs2GJ2a1GOnT4tU57tbORF7x8/WuPLBGje
N74CvCfi01Y8XeCKo6VS7OqhhUYTF+Wu30wwWdappqYhPY1ugs1PArG106N0VmUn
S2Y3+QlHwGXxQFtfTFNvyRJo23SHoljwhq+Vp4n9vdnCRCvNVI8HbHmmk3zGF6xH
emg+/bth6WGUhkH6oqhnjDRFp+4YqcL7JCgllBeaHCbf++7ZLPqrK01NwwGhofsw
lW+bPEljBQ+GcKc9Jq1RGlN0iq1ua+Fli5jo47NHCed0vmt/zvnxPMfjNEqce0uX
LwlyZ4IJWz1GTBUpiTrIcFDCZ6VFZi6XIMr17BHDygcVZW4VdTPrE5uwnbibiuMn
H3suTlGx9tWGxZtO7HF3/VIa5zOM1zNB2gvDiLoDRzEocKH1zY8KWUBT9U0NT2XE
QCfDBUxx0MaxuhJvEG9M9OLBxWWc0/QNHomeCJnUNxyhiMnoOlT2qTJgNIPuTaQt
1TnC993SMBdQ0U6VKKyISJ8QBqpPe6PHBadlt3/i6vJ2fnAGT+iYBbt0DPohP49Y
v6jsyfxRIUZU0EjG1OthTxCj64DFM8whYH/Ys7KdWn9NJkAJgIY=
=M9M1
-END PGP SIGNATURE End Message ---


Bug#941432: [pkg-uWSGI-devel] Bug#941432: uwsgi-core: Dependency libmatheval is getting out of bullseye

2019-10-02 Thread Pierre-Elliott Bécue
Le mercredi 02 octobre 2019 à 12:02:20+0200, Alexandre Rossi a écrit :
> Hi,
> 
> > uwsgi-core depends on libmatheval1, which future in the archive seems
> > compromised, this implies that src:uwsgi and all packages which depend
> > on it will get out of the archive sooner or later.
> > 
> > Do you have plans/solutions regarding this issue? Is it possible to drop
> > uwsgi-core dependency on libmatheval1?
> 
> It should be as simple as not building the matheval plugin which is not
> critical to uwsgi. Should I go on with this?

Yeah, I just wasn't sure that it'd be an acceptable solution for you.

But it's perfectly fine with me. :)

Cheers!

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



Bug#941432: [pkg-uWSGI-devel] Bug#941432: Bug#941432: uwsgi-core: Dependency libmatheval is getting out of bullseye

2019-10-02 Thread Jonas Smedegaard
Quoting Alexandre Rossi (2019-10-02 12:02:20)
> > uwsgi-core depends on libmatheval1, which future in the archive 
> > seems compromised, this implies that src:uwsgi and all packages 
> > which depend on it will get out of the archive sooner or later.
> > 
> > Do you have plans/solutions regarding this issue? Is it possible to 
> > drop uwsgi-core dependency on libmatheval1?
> 
> It should be as simple as not building the matheval plugin which is 
> not critical to uwsgi. Should I go on with this?

Agreed.  Nice f you could handle this, Alexandre.

 - Jonas

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

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


signature.asc
Description: signature


Bug#941575: node-typescript 3.6.3-2 adds a regression

2019-10-02 Thread Pirate Praveen

Package: node-typescript
Version: 3.6.3-2
Severity: grave

Adding rc bug to block testing migration. I think the patch to add 
/usr/share/nodejs should be reverted and we should do more tests before 
adding it again.




Bug#941432: [pkg-uWSGI-devel] Bug#941432: uwsgi-core: Dependency libmatheval is getting out of bullseye

2019-10-02 Thread Alexandre Rossi
Hi,

> uwsgi-core depends on libmatheval1, which future in the archive seems
> compromised, this implies that src:uwsgi and all packages which depend
> on it will get out of the archive sooner or later.
> 
> Do you have plans/solutions regarding this issue? Is it possible to drop
> uwsgi-core dependency on libmatheval1?

It should be as simple as not building the matheval plugin which is not
critical to uwsgi. Should I go on with this?

Alex



Bug#941488: dbus-test-runner: diff for NMU version 16.10.0~bzr100+repack1-4.1

2019-10-02 Thread Iain Lane
Control: tags 941488 + patch
Control: tags 941488 + pending

Hiya,

I thought I'd be helpful (to speed along the glib2.0 migration), so I've
prepared an NMU for dbus-test-runner (versioned as
16.10.0~bzr100+repack1-4.1) and uploaded it to DELAYED/5. Please feel
free to tell me if I should delay it longer, or cancel it yourself,
upload it under your own name or anything similar.

Cheers!

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]
diff -Nru dbus-test-runner-16.10.0~bzr100+repack1/debian/changelog dbus-test-runner-16.10.0~bzr100+repack1/debian/changelog
--- dbus-test-runner-16.10.0~bzr100+repack1/debian/changelog	2018-11-02 21:43:17.0 +
+++ dbus-test-runner-16.10.0~bzr100+repack1/debian/changelog	2019-10-02 10:02:52.0 +0100
@@ -1,3 +1,15 @@
+dbus-test-runner (16.10.0~bzr100+repack1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/dont-build-with-werror.patch: Don't build with -Werror;
+this is a bad idea for release builds as it means you get build failures
+for deprecations (Closes: #941488)
+  * debian/patches/replace-deprecated-functions.patch: tests: Replace
+deprecated g_main_{pending,iteration} with current
+g_main_context_{pending,iteration}
+
+ -- Iain Lane   Wed, 02 Oct 2019 10:02:52 +0100
+
 dbus-test-runner (16.10.0~bzr100+repack1-4) unstable; urgency=medium
 
   * debian/control:
diff -Nru dbus-test-runner-16.10.0~bzr100+repack1/debian/patches/dont-build-with-werror.patch dbus-test-runner-16.10.0~bzr100+repack1/debian/patches/dont-build-with-werror.patch
--- dbus-test-runner-16.10.0~bzr100+repack1/debian/patches/dont-build-with-werror.patch	1970-01-01 01:00:00.0 +0100
+++ dbus-test-runner-16.10.0~bzr100+repack1/debian/patches/dont-build-with-werror.patch	2019-10-02 09:59:33.0 +0100
@@ -0,0 +1,97 @@
+Description: Don't build with -Werror; this is a bad idea for release builds as it means you get build failures for deprecations
+Author: Iain Lane 
+Origin: https://bazaar.launchpad.net/~indicator-applet-developers/dbus-test-runner/trunk.16.10/revision/102
+
+diff --git a/src/Makefile.am b/src/Makefile.am
+index 24a3f1f..7c44544 100644
+--- a/src/Makefile.am
 b/src/Makefile.am
+@@ -6,7 +6,7 @@
+ 	$(COVERAGE_CFLAGS) \
+ 	-I$(top_srcdir) \
+ 	-DDEFAULT_SESSION_CONF="\"$(datadir)/dbus-test-runner/session.conf\"" \
+-	-Wall -Werror -Wextra
++	-Wall -Wextra
+ dbus_test_runner_LDADD   = $(DBUS_TEST_RUNNER_LIBS) \
+ 	$(top_builddir)/libdbustest/libdbustest.la
+ dbus_test_runner_LDFLAGS = $(COVERAGE_LDFLAGS)
+diff --git a/build.sh b/build.sh
+index 11bd1ed..4c691ab 100755
+--- a/build.sh
 b/build.sh
+@@ -1,3 +1,3 @@
+ #!/bin/sh
+ 
+-gcc -o dbus-test-runner `pkg-config --cflags --libs glib-2.0 gobject-2.0` dbus-test-runner.c -Wall -Werror
++gcc -o dbus-test-runner `pkg-config --cflags --libs glib-2.0 gobject-2.0` dbus-test-runner.c -Wall
+diff --git a/libdbustest/Makefile.am b/libdbustest/Makefile.am
+index d76ff52..d048a83 100644
+--- a/libdbustest/Makefile.am
 b/libdbustest/Makefile.am
+@@ -40,7 +40,7 @@
+ 	-DBUSTLE_DUAL_MONITOR="\"$(pkgdatadir)/dbus-test-bustle-handler\"" \
+ 	-DWATCHDOG="\"$(pkglibexecdir)/dbus-test-watchdog\"" \
+ 	-DG_LOG_DOMAIN=\"libdbustest\" \
+-	-Wall -Werror -Wextra
++	-Wall -Wextra
+ 
+ libdbustest_la_LIBADD = \
+ 	libdbustest-generated.la \
+@@ -59,7 +59,7 @@
+ 	$(DBUS_TEST_RUNNER_CFLAGS) \
+ 	-I$(builddir) \
+ 	-DG_LOG_DOMAIN=\"libdbustest\" \
+-	-Wall -Werror
++	-Wall
+ 
+ libdbustest_generated_la_SOURCES = \
+ 	dbus-mock-iface.h \
+diff --git a/tests/Makefile.am b/tests/Makefile.am
+index 7eccc63..4f4aad9 100644
+--- a/tests/Makefile.am
 b/tests/Makefile.am
+@@ -245,7 +245,7 @@
+ 	test-own-name.c
+ test_own_name_CFLAGS = \
+ 	$(DBUS_TEST_RUNNER_CFLAGS) \
+-	-Wall -Werror
++	-Wall
+ test_own_name_LDADD = \
+ 	$(DBUS_TEST_RUNNER_LIBS)
+ 
+@@ -253,7 +253,7 @@
+ 	test-check-name.c
+ test_check_name_CFLAGS = \
+ 	$(DBUS_TEST_RUNNER_CFLAGS) \
+-	-Wall -Werror
++	-Wall
+ test_check_name_LDADD = \
+ 	$(DBUS_TEST_RUNNER_LIBS)
+ 
+@@ -351,7 +351,7 @@
+ 	-I$(top_srcdir) \
+ 	-DSESSION_CONF="\"$(top_srcdir)/data/session.conf\"" \
+ 	-DGETNAME_PATH="\"$(abs_builddir)/test-libdbustest-getname\"" \
+-	-Wall -Werror
++	-Wall
+ test_libdbustest_LDADD = \
+ 	$(DBUS_TEST_RUNNER_LIBS) \
+ 	$(top_builddir)/libdbustest/libdbustest.la
+@@ -360,7 +360,7 @@
+ 	test-libdbustest-getname.c
+ test_libdbustest_getname_CFLAGS = \
+ 	$(DBUS_TEST_RUNNER_CFLAGS) \
+-	-Wall -Werror
++	-Wall
+ test_libdbustest_getname_LDADD = \
+ 	$(DBUS_TEST_RUNNER_LIBS)
+ 
+@@ -389,7 +389,7 @@
+ 	-I$(top_srcdir) \
+ 	-DSESSION_CONF="\"$(top_srcdir)/data/session.conf\"" \
+ 	-DGETNAME_PATH="\"$(abs_builddir)/test-libdbustest-getname\"" \
+-	-Wall -Werror
++	-Wall
+ test_libdbustest_mock_LDADD = \
+ 	$(DBUS_TEST_RUNNER_LIBS) \
+ 	

Processed: dbus-test-runner: diff for NMU version 16.10.0~bzr100+repack1-4.1

2019-10-02 Thread Debian Bug Tracking System
Processing control commands:

> tags 941488 + patch
Bug #941488 [src:dbus-test-runner] dbus-test-runner: autopkgtest fails with 
libglib2.0-0 (>= 2.62)
Added tag(s) patch.
> tags 941488 + pending
Bug #941488 [src:dbus-test-runner] dbus-test-runner: autopkgtest fails with 
libglib2.0-0 (>= 2.62)
Added tag(s) pending.

-- 
941488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#941554: yodl: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended

2019-10-02 Thread Frank B. Brokken
Dear Steve Langasek, you wrote:
> Package: yodl
> Version: 4.02.01-2
> Severity: serious
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu eoan ubuntu-patch
> 
> Dear maintainers,
> 
> The texlive-generic-recommended transitional package has been dropped from
> texlive-base in sid.  Please update your build-dependency to
> texlive-plain-generic instead.

Thanks for the bug report: I'll handle that either today or tomorrow.


-- 
Frank B. Brokken
(+31) 6 5353 2509
PGP Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA



Bug#941530: jackson-databind: CVE-2019-16942 CVE-2019-16943

2019-10-02 Thread Salvatore Bonaccorso
Hi Markus,

On Tue, Oct 01, 2019 at 10:46:16PM +0200, Markus Koschany wrote:
> Hi Salvatore,
> 
> Am 01.10.19 um 22:34 schrieb Salvatore Bonaccorso:
> > Source: jackson-databind
> > Version: 2.10.0-1
> > Severity: grave
> > Tags: security upstream
> > Justification: user security hole
> > Forwarded: https://github.com/FasterXML/jackson-databind/issues/2478
> > Control: found -1 2.9.8-3
> > Control: found -1 2.8.6-1+deb9u5
> > Control: found -1 2.8.6-1
> > 
> > Hi,
> > 
> > Tony, Markus, As it was already expected ;-). Upstream, whilst it
> > affects as well 2.10.0, seemigly is not considering doing an update
> > for 2.10 specifically but have fixed this one as well for older
> > versions. Previous point, that this is just going to start to be silly
> > upholds.
> > 
> > That said, let's follow with the usual information:
> > 
> > The following vulnerabilities were published for jackson-databind.
> [...]
> 
> First of all, thank you very much for taking care of reporting these issues.
> 
> Please let me know if you think this is a DSA-worthy issue. Otherwise I
> will just ask the release team for an update. Personally I believe we
> can treat that as an important issue from now on.

Whilst I'm not yet sure if we should really release a futher DSA for
jackson-databind (we will come back to you on that), a possible idea
for bullseye (might be better cloned/filled as new bug, but want to
mention it here already):

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

Red Hat recently had fixed a CVE for codehaus. The approach they took
there was to rather continuing on jackson-databind side (that is my
interpretation), they started a whitelist approach on the applications
side which use jackson-databind.

This might be something to consider for bullseye as well for the
reverse dependencies. Not sure if this is feasible in our case, but
this might be worth investigating.

Regards,
Salvatore



Bug#941507: marked as done (ocaml-nox: Unable to install ocaml-nox 4.08 from experimental)

2019-10-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Oct 2019 08:24:57 +0200
with message-id <0981f598-7a7a-535e-ca47-3c2a476d8...@debian.org>
and subject line Re: Bug#941507: ocaml-nox: Unable to install ocaml-nox 4.08 
from experimental
has caused the Debian Bug report #941507,
regarding ocaml-nox: Unable to install ocaml-nox 4.08 from experimental
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
941507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ocaml-nox
Version: 4.05.0-12
Severity: serious

Dear Maintainer,

Installing ocaml-nox is currently broken in experimental:

The following packages have unmet dependencies:
 ocaml-nox : Depends: ocaml-base-nox-4.08.1
 Depends: ocaml-interp (= 4.08.1-1) but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.
Command apt-get --dry-run install -- ocaml-nox/experimental exited with exit 
code 1.

Thanks

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

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

Versions of packages ocaml-nox depends on:
ii  binutils2.32.51.20190909-1
ii  gcc 4:9.2.1-3.1
ii  libc6   2.29-2
ii  libncurses-dev [libncurses5-dev]6.1+20190803-1
ii  libncurses6 6.1+20190803-1
ii  libtinfo6   6.1+20190803-1
ii  ocaml-base-nox [ocaml-base-nox-4.05.0]  4.05.0-12
ii  ocaml-interp4.05.0-12
ii  zlib1g  1:1.2.11.dfsg-1+b1

Versions of packages ocaml-nox recommends:
ii  file  1:5.37-5

Versions of packages ocaml-nox suggests:
pn  ocaml-doc 
pn  tuareg-mode | ocaml-mode  

-- no debconf information
--- End Message ---
--- Begin Message ---
Le 01/10/2019 à 18:57, Kyle Robbertze a écrit :
> Installing ocaml-nox is currently broken in experimental:
> 
> The following packages have unmet dependencies:
>  ocaml-nox : Depends: ocaml-base-nox-4.08.1
>  Depends: ocaml-interp (= 4.08.1-1) but it is not going to be 
> installed
> E: Unable to correct problems, you have held broken packages.
> Command apt-get --dry-run install -- ocaml-nox/experimental exited with exit 
> code 1.

This is a limitation in apt. You have to be explicit about all packages
that are to be taken from experimental:

  apt install ocaml-nox/experimental ocaml-interp/experimental
ocaml-base-nox/experimental

or

  apt install -t experimental ocaml-nox


Cheers,

-- 
Stéphane--- End Message ---