Bug#911187: marked as done (axis: FTBFS with Java 11 due to javax.rmi and CORBA removal)

[Debian Bug Tracking System]

Your message dated Mon, 03 Dec 2018 07:49:09 +
with message-id 
and subject line Bug#911187: fixed in axis 1.4-28
has caused the Debian Bug report #911187,
regarding axis: FTBFS with Java 11 due to javax.rmi and CORBA removal
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.)


-- 
911187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: axis
Severity: important
Tags: sid buster
User: debian-j...@lists.debian.org
Usertags: default-java11

axis fails to build with Java 11 due to the removal of the javax.rmi
and org.omg.CORBA packages:


  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:25: 
error: package org.omg.CORBA does not exist
  [javac] import org.omg.CORBA.ORB;
  [javac] ^
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:26: 
error: package org.omg.CosNaming does not exist
  [javac] import org.omg.CosNaming.NameComponent;
  [javac] ^
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:27: 
error: package org.omg.CosNaming does not exist
  [javac] import org.omg.CosNaming.NamingContext;
  [javac] ^
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:28: 
error: package org.omg.CosNaming does not exist
  [javac] import org.omg.CosNaming.NamingContextHelper;
  [javac] ^
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:85: 
error: cannot find symbol
  [javac] ORB orb = ORB.init(new String[0], orbProps);
  [javac] ^
  [javac]   symbol:   class ORB
  [javac]   location: class CORBAProvider
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:85: 
error: cannot find symbol
  [javac] ORB orb = ORB.init(new String[0], orbProps);
  [javac]   ^
  [javac]   symbol:   variable ORB
  [javac]   location: class CORBAProvider
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:88: 
error: cannot find symbol
  [javac] NamingContext root = 
NamingContextHelper.narrow(orb.resolve_initial_references("NameService"));
  [javac] ^
  [javac]   symbol:   class NamingContext
  [javac]   location: class CORBAProvider
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:88: 
error: cannot find symbol
  [javac] NamingContext root = 
NamingContextHelper.narrow(orb.resolve_initial_references("NameService"));
  [javac]  ^
  [javac]   symbol:   variable NamingContextHelper
  [javac]   location: class CORBAProvider
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:89: 
error: cannot find symbol
  [javac] NameComponent nc = new NameComponent(nameId, nameKind);
  [javac] ^
  [javac]   symbol:   class NameComponent
  [javac]   location: class CORBAProvider
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:89: 
error: cannot find symbol
  [javac] NameComponent nc = new NameComponent(nameId, nameKind);
  [javac]^
  [javac]   symbol:   class NameComponent
  [javac]   location: class CORBAProvider
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:90: 
error: cannot find symbol
  [javac] NameComponent[] ncs = {nc};
  [javac] ^
  [javac]   symbol:   class NameComponent
  [javac]   location: class CORBAProvider
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:91: 
error: package org.omg.CORBA does not exist
  [javac] org.omg.CORBA.Object corbaObject = root.resolve(ncs);
  [javac]  ^
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:101: 
error: package org.omg.CORBA does not exist
  [javac] private static final Class[] CORBA_OBJECT_CLASS = new Class[] 
{org.omg.CORBA.Object.class};
  [javac]   
  ^
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/EJBProvider.java:129: error: 
package javax.rmi does not exist
  [javac] Object ehome = javax.rmi.PortableRemoteObject.narrow(ejbHome, 
homeClass);
  [javac] ^
  [javac] 
/build/axis-1.4/src/org/apache/axis/providers/java/EJBProvider.java:254: error: 
package javax.rmi does not exist
  [javac] Object ehome = 

Processed: Bug #911187 in axis marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #911187 {Done: Emmanuel Bourg } [src:axis] axis: FTBFS 
with Java 11 due to javax.rmi and CORBA removal
Added tag(s) pending.

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

Bug#911187: Bug #911187 in axis marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #911187 in axis 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/java-team/axis/commit/ff342518d2de6fe674bba30dfb80de3bd77bf472


Fixed the build failure with Java 11 (Closes: #911187)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/911187

Bug#915342: marked as done (libbpp-seq FTBFS: symbol changes)

[Debian Bug Tracking System]

Your message dated Mon, 03 Dec 2018 07:50:00 +
with message-id 
and subject line Bug#915342: fixed in libbpp-seq 2.4.1-2
has caused the Debian Bug report #915342,
regarding libbpp-seq FTBFS: symbol changes
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.)


-- 
915342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbpp-seq
Version: 2.4.1-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes libbpp-seq FTBFS:

https://tests.reproducible-builds.org/debian/history/libbpp-seq.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbpp-seq.html

...
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/build/1st/libbpp-seq-2.4.1'
echo "Architecture amd64 is the only one where a symbols file is provided"
Architecture amd64 is the only one where a symbols file is provided
dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libbpp-seq12/DEBIAN/symbols doesn't match 
completely debian/libbpp-seq12.symbols
--- debian/libbpp-seq12.symbols (libbpp-seq12_2.4.1-1_amd64)
+++ dpkg-gensymbols_nPCUn   2020-01-04 12:03:13.926707545 -1200
@@ -1813,7 +1813,8 @@
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE11equal_rangeERS7_@Base
 2.4.1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE12_M_erase_auxESt23_Rb_tree_const_iteratorISB_E@Base
 2.4.1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSJ_PSt13_Rb_tree_nodeISB_E@Base
 2.4.1
- 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE16_M_insert_uniqueIS6_IS5_SA_EEES6_ISt17_Rb_tree_iteratorISB_EbEOT_@Base
 2.4.1
+#MISSING: 2.4.1-1# 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE16_M_insert_uniqueIS6_IS5_SA_EEES6_ISt17_Rb_tree_iteratorISB_EbEOT_@Base
 2.4.1
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE17_M_emplace_uniqueIJS6_IS5_SA_S6_ISt17_Rb_tree_iteratorISB_EbEDpOT_@Base
 2.4.1-1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base
 2.4.1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base
 2.4.1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS7_@Base
 2.4.1
dh_makeshlibs: failing due to earlier errors
make[1]: *** [debian/rules:15: override_dh_makeshlibs] Error 2
--- End Message ---
--- Begin Message ---
Source: libbpp-seq
Source-Version: 2.4.1-2

We believe that the bug you reported is fixed in the latest version of
libbpp-seq, 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 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libbpp-seq 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: Mon, 03 Dec 2018 08:15:45 +0100
Source: libbpp-seq
Binary: libbpp-seq-dev libbpp-seq12
Architecture: source
Version: 2.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libbpp-seq-dev - 

Bug#915207: gnudatalanguage: autopkgtests fail: test_bug_n000720, test_idlneturl, test_point_lun, test_save_restore, test_zip

[Gilles Filippini]

Hi Sebastian,

On 03.12.18 00:15, Sebastiaan Couwenberg wrote:> Unfortunately the
autopkgtests for 0.9.9-1 still fail [0], and since> it's blocking the
migration of hdf5 it makes the package unsuitable for> release
justifying the RC severity [1].
Sorry, but I don't see this: gdl does not *break* hdf5 ("break" means
IMO that a package that worked before does not work anymore -- but hdf5
still works nicely, right?), and it also does not block the transition.

As far as I know, CI tests are currently setup in a non-blocking way.
And when I look into the maintainer page of hdf5, it says

"Required age increased by 30 days because of autopkgtest".

This is not a block, this is just a delay. There never was a statement
that failing CI tests are RC (or would become so before buster).

So, you you please be a bit more explicit how the RC policy applies here?

Best regards

Ole

Bug#914897: debating the wrong thing

[Ansgar Burchardt]

Adam Borowski writes:
> I see that we're debating the merits of merged-usr vs non-merged-usr, while
> expending lots of effort and filing bugs (requiring further urgent action of
> unrelated maintainers), for little gain.

There is no "urgent action" required (unlike, say, for the last glibc
update).

If you don't want support for merged-/usr, could you please discuss this
back in 2016 or before that?  Also I feel a general discussion would
probably just be too long-winded and touch too many unrelated issues;
there is not even a terse list of claimed problems.

It is very demotivating to have discussed and implemented something
mostly years ago, for people then to come and complain "let's not do
this at all" years later.

Maybe we should also revisit Multi-Arch now that we know that
`Multi-Arch: foreign` relations as implemented can result in non-booting
systems...

Or really revisit the init system question before people file bugs that
require further urgent action for little gain (it's probably too late in
the release cycle to push in elogind anyway).  There is also the
question if it is still worth to spend maintainer efforts to ship
sysvinit scripts if this means we lose the advantages of declarative
service files (which means far more work than merged-/usr changes)...

We could also open a tech-ctte bug for secure boot before I spend any
more time on it (there are still a few things).  Luckily having this
discussion delays me spending time on the remaining things I wanted to
look at, so at least not more time is wasted.  (Not that I currently
have too much time for Debian anyway, and secure boot is quite a lot of
work for something I don't need...)

Ansgar

Bug#915343: marked as done (libbpp-core FTBFS: symbol changes)

[Debian Bug Tracking System]

Your message dated Mon, 03 Dec 2018 07:18:59 +
with message-id 
and subject line Bug#915343: fixed in libbpp-core 2.4.1-2
has caused the Debian Bug report #915343,
regarding libbpp-core FTBFS: symbol changes
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.)


-- 
915343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbpp-core
Version: 2.4.1-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes libbpp-core FTBFS:

https://tests.reproducible-builds.org/debian/history/libbpp-core.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbpp-core.html

...
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/build/1st/libbpp-core-2.4.1'
echo "Architecture amd64 is the only one where a symbols file is provided"
Architecture amd64 is the only one where a symbols file is provided
dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libbpp-core4/DEBIAN/symbols doesn't match 
completely debian/libbpp-core4.symbols
--- debian/libbpp-core4.symbols (libbpp-core4_2.4.1-1_amd64)
+++ dpkg-gensymbolsf79BBX   2020-01-04 12:02:29.920104286 -1200
@@ -2266,7 +2266,9 @@
  
_ZNSt8_Rb_treeIjSt4pairIKjS0_IjjEESt10_Select1stIS3_ESt4lessIjESaIS3_EE8_M_eraseEPSt13_Rb_tree_nodeIS3_E@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjS0_IjjEESt10_Select1stIS3_ESt4lessIjESaIS3_EEaSERKS9_@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE12_M_erase_auxESt23_Rb_tree_const_iteratorIS2_E@Base
 2.4.1
- 
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE16_M_insert_uniqueIS0_IjjEEES0_ISt17_Rb_tree_iteratorIS2_EbEOT_@Base
 2.4.1
+ 
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSA_PSt13_Rb_tree_nodeIS2_E@Base
 2.4.1-1
+#MISSING: 2.4.1-1# 
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE16_M_insert_uniqueIS0_IjjEEES0_ISt17_Rb_tree_iteratorIS2_EbEOT_@Base
 2.4.1
+ 
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE17_M_emplace_uniqueIJS0_IjjS0_ISt17_Rb_tree_iteratorIS2_EbEDpOT_@Base
 2.4.1-1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE7_M_copyINS8_11_Alloc_nodeEEEPSt13_Rb_tree_nodeIS2_EPKSC_PSt18_Rb_tree_node_baseRT_@Base
 2.4.1
dh_makeshlibs: failing due to earlier errors
make[1]: *** [debian/rules:15: override_dh_makeshlibs] Error 2
--- End Message ---
--- Begin Message ---
Source: libbpp-core
Source-Version: 2.4.1-2

We believe that the bug you reported is fixed in the latest version of
libbpp-core, 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 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libbpp-core 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: Mon, 03 Dec 2018 07:39:32 +0100
Source: libbpp-core
Binary: libbpp-core-dev libbpp-core4
Architecture: source
Version: 2.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libbpp-core-dev - Bio++ Core library development files
 libbpp-core4 - Bio++ Core library
Closes: 915343
Changes:
 libbpp-core (2.4.1-2) unstable; urgency=medium
 .
   [ Jelmer Vernooij ]
   * Use secure copyright file specification URI.
   * Trim trailing whitespace.
 .
   [ Andreas Tille ]
   * Fix symbols file
 Closes: #915343
   * Standards-Version: 4.2.1
   * Remove trailing whitespace in debian/copyright
Checksums-Sha1:
 93cbdcdbdc798bde1b0f506e3077ec4891f81250 2114 libbpp-core_2.4.1-2.dsc
 e742de1b20b4f53b823a561c5045c1f55b1f4661 32556 
libbpp-core_2.4.1-2.debian.tar.xz

Bug#915084: marked as done (ros-robot-model is being replaced by several packages)

[Debian Bug Tracking System]

Your message dated Mon, 03 Dec 2018 06:49:28 +
with message-id 
and subject line Bug#915084: fixed in ros-robot-model 1.12.6-3
has caused the Debian Bug report #915084,
regarding ros-robot-model is being replaced by several packages
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.)


-- 
915084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-robot-model
Version: 1.12.6-2
Severity: serious

ros-robot-model is being replaced by several packages
and can no longer be uploaded with some of its binary
packages already being built by other source packages.
--- End Message ---
--- Begin Message ---
Source: ros-robot-model
Source-Version: 1.12.6-3

We believe that the bug you reported is fixed in the latest version of
ros-robot-model, 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 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-robot-model 
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: Fri, 30 Nov 2018 17:56:13 +0100
Source: ros-robot-model
Binary: libcollada-parser-dev libcollada-parser0d libcollada-urdf-dev 
libcollada-urdf0d collada-urdf-tools joint-state-publisher
Architecture: source
Version: 1.12.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 collada-urdf-tools - ROS collada_urdf tools
 joint-state-publisher - ROS joint_state_publisher
 libcollada-parser-dev - Development files for ROS collada_parser library
 libcollada-parser0d - ROS collada_parser library
 libcollada-urdf-dev - Development files for ROS collada_urdf library
 libcollada-urdf0d - ROS collada_urdf library
Closes: 915084
Changes:
 ros-robot-model (1.12.6-3) unstable; urgency=medium
 .
   * Drop split out packages (Closes: #915084)
Checksums-Sha1:
 0de7d4d2d4d8d3fd206e2decfa98d66658ddfea9 2942 ros-robot-model_1.12.6-3.dsc
 c0c2f4d48e5ca1061b594544f0dc867d22d035c3 4708 
ros-robot-model_1.12.6-3.debian.tar.xz
 f1372e5a9f97252b96e69cdaf4fe7b04cc35b86e 10766 
ros-robot-model_1.12.6-3_source.buildinfo
Checksums-Sha256:
 989f86fe5029fd4019f9a1a892cf8e8d2c27c557a189e8445bb342ad4695a256 2942 
ros-robot-model_1.12.6-3.dsc
 816e4cfdb94e93dce7e9c7ce1c432b92799f4e47688528b88596c59827a67273 4708 
ros-robot-model_1.12.6-3.debian.tar.xz
 11889c7cee7ffa321e81772ce54d1d7e4873fc031d2714e85b37c90bb9db97e2 10766 
ros-robot-model_1.12.6-3_source.buildinfo
Files:
 1b04dc9d669f258ef3c7a42532aa80ee 2942 libs optional 
ros-robot-model_1.12.6-3.dsc
 a6f0ad55bc4ad171b072cd51b2dceb00 4708 libs optional 
ros-robot-model_1.12.6-3.debian.tar.xz
 e6479001b039bd2171eef792ee06420d 10766 libs optional 
ros-robot-model_1.12.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAlwEzGoUHGpzcHJpY2tl
QGRlYmlhbi5vcmcACgkQW//cwljmlDOeSRAAnFz9uvijEDm/d1MqmmVzLWZNOHja
gVHlJIPHHLPQqtTaAYVeKAlvl0ltjSUVNhberTTRVgrHk9vaqQO7iO076pD6+Dfx
DK3xjmZZ3BejfgEU3P7qR4zCBMlNXicMgZIoz+D/JkLA+88Ax6EopKvm37b5FTbd
nCGR0I421deBdCQ+vnwdiXr0e0hDIpiGP9Mu4EdZsi0LQT7xbyAMylzMZJ60ZgI0
k2E2UpQ17OS8+UEivSTNpvti5EfemQwb56onyTvd3oWEjuE+S/uaNmMCO96VurVK
0BLfAe7Ud2rhGVPYPc7DILcqp0M+ncrA5y5vw+NBg/BFsra2ux6ax9pj68zrnUWD
JL9DwxbBX4bymcxpO8lckOcfH7L1ivh+xIiWXJKjmUZsMORR5wcWwlOJjic5dgZU
QbSUAI4zzEkXAKG+N9OYUlCamqeiAxfXuOoj4waw1hIRMIkeo4LVFLv7BeKGD+rO
3DAUnA9n9Rd9dW0EUAxNBGs2G93yeBwrpg1Kg4MC0xljxKtcLjLVG9HfmnJJB/lV
PTLB+TNMMb5iO5GczL7qTHfgDvhb3Ds4wGK0ATIFnThximO+c8jymduceyZ93gnd
WyIjwY5yBAOv3Kn0nlZxTJASTU+6o4kwGg0R4y14+D/+8J0r2srzRyN3aTtbP5lL
/rYdZh2p14+rXtk=
=tJG7
-END PGP SIGNATURE End Message ---

Bug#915069: libphp-predis: Useless in Debian, superseded by php-nrk-predis

[Cyril Bouthors]

Hi David,

No problem with me.
-- 
Cyril Bouthors | Founder & President
Go-Managed.com  | +33-184-16-16-17 

We ensure that your critical website is running under heavy load

> On Nov 30, 2018, at 3:19 AM, David Prévot  wrote:
> 
> Package: libphp-predis
> Version: 0.8.3-1
> Severity: serious
> 
> libphp-predis was packaged a few years ago, and is not used by any
> Debian anymore. The php-nrk-predis is a more recent version of the same
> package, so there is a priori little point to ship libphp-predis in a
> stable Debian release.
> 
> I intend to follow up with an RM request in a few months if nobody
> objects (but feel free to beat me to it).
> 
> Regards
> 
> David

Bug#907396: kopano-server: Tools all fail with: MAPI error 80040111 (MAPI_E_LOGON_FAILED)

[Carsten Schoenert]

Hello David,

Am 02.12.18 um 21:51 schrieb David Gabriel:
>> No, this is not planned.
> 
> Happy to hear that - I was referring to the statement on
> https://tracker.debian.org/pkg/kopanocore (...removal on Dec 8...)
> must have mis-interpreted that.

these removals are happen automatically to ensure the packages from
Testing are mostly useful. It also helps, like now, to reduce potential
broken packages go into the next stable release. So yes, if the
maintainers don't act the packages will not go into Buster.

>> Please note the packages here might get changed or get dropped later. If
>> you could do some testing we would like to get some feedback if possible.
> 
> I understand - that's a lot of changes, thank you all for your hard work! I'll
> gladly test the provided packages and report back. However since I'm traveling
> abroad at the moment (and I'll have to revert my kopano install for which I 
> used
> the .deb packages provided by download.kopano.io for now) this might take me
> about 2 weeks.

Oh, this sounds like a install from scratch (except the import of your
existing database at some point). Good possibility to see then if all is
running as you might expect. For sure there is room for improvements in
Readme's or package descriptions e.g. Please make notes where you have
figured out some problems or issues.

> Whom/were should I report back? This bug is probably not the
> right place to continue to talk about packaging issues.

Yes, this bug report isn't about the original issue which is fixed a
while ago as Mark already mentioned.

There are two mailing list were we discuss problems, plannings or
packaging things. The amount of emails is rather slow, so you wont be
flooded by a lot of traffic from here.

List for talking about the what things and how them to do, the list we
typically do most of discussions
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-giraffe-discuss

Talking about packaging related things, also the list for emails from
the archive (used address for the Maintainer field)
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-giraffe-maintainers

And there is also a wiki site in the Debian Wiki with a lot of partial
information. It's not that up2date, it was the place were we have
written down the various status of the interaction packages.

https://wiki.debian.org/Groupware/Kopano

> Br and thanks again for the comprehensive update,

You are welcome!

-- 
Regards
Carsten Schoenert

Processed: retitle 915332 to policykit-1: CVE-2018-19788: unprivileged users with UID can successfully execute any systemctl command

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 915332 policykit-1: CVE-2018-19788: unprivileged users with UID can 
> successfully execute any systemctl command
Bug #915332 [src:policykit-1] policykit: unprivileged users with UID > INT_MAX 
can successfully execute any systemctl command
Changed Bug title to 'policykit-1: CVE-2018-19788: unprivileged users with UID 
can successfully execute any systemctl command' from 'policykit: unprivileged 
users with UID > INT_MAX can successfully execute any systemctl command'.
> thanks
Stopping processing here.

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

Processed: forcibly merging 915261 915361

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 915261 915361
Bug #915261 [udev] SysV init regression thanks to broken "container detection" 
logic
Bug #915361 [udev] udev refuses to start with sysvinit because it misdetects a 
container
Severity set to 'important' from 'grave'
Marked as found in versions systemd/239-14.
Added tag(s) pending.
Merged 915261 915361
> thanks
Stopping processing here.

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

Bug#915365: historical.packages.debian.org: 404 for any page other than root

[Paul Wise]

On Mon, Dec 3, 2018 at 11:54 AM Keian Rao wrote:

> historical.packages.debian.org does not [work].

This website has not yet been fully setup yet so it isn't surprising
that it is broken. It might be fixed eventually but I've no idea when
the folks responsible will have time.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#915365: historical.packages.debian.org: 404 for any page other than root

[Keian Rao]

Package: www.debian.org
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Although packages.debian.org works fine, historical.packages.debian.org
does not.

Steps to reproduce:

(1) Open historical.packages.debian.org in a browser.

(2) Do any of the following:

(a) Click the link to the list of packages for any distribution.

(b) Search for a package under 'Search package directories'

(c) Use the search shortcut by appending a package name to the URL,
e.g. historical.packages.debian.org/rosegarden or
historical.packages.debian.org/src:rosegarden

(d) Search for something under 'Search the contents of packages'

(e) Switch to another language, with the language links at the bottom
of the page

Alternatively,
(3) Use the search shortcut with wget, e.g. wget 
historical.packages.debian.org/coreutils


Results:

All of the above result in a 404 Not Found error.

On a web browser, the following is given: 
"The requested URL /cgi-bin/dispatcher.fcgi/search was not found on this
server", or
"The requested URL /cgi-bin/dispatcher.fcgi/lenny was not found on this
server"


This appears to be a server configuration error.


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

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

Bug#913251: marked as done (SSL: renegotiation initiated by client, killing connection)

[Debian Bug Tracking System]

Your message dated Mon, 03 Dec 2018 03:49:23 +
with message-id 
and subject line Bug#913251: fixed in lighttpd 1.4.49-2
has caused the Debian Bug report #913251,
regarding SSL: renegotiation initiated by client, killing connection
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.)


-- 
913251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lighttpd
Version: 1.4.49-1.1+b1
Severity: important

Dear Maintainer,

TLS appears to be unusable.. probably fixed in 1.4.51

Gr,

Olaf

https://redmine.lighttpd.net/issues/2912

2018-11-08 19:00:46: (mod_openssl.c.1419) SSL: renegotiation initiated by 
client, killing connection 
2018-11-08 19:00:46: (mod_openssl.c.1419) SSL: renegotiation initiated by 
client, killing connection 
2018-11-08 19:00:54: (mod_openssl.c.1419) SSL: renegotiation initiated by 
client, killing connection 
2018-11-08 19:00:54: (mod_openssl.c.1419) SSL: renegotiation initiated by 
client, killing connection 
2018-11-08 19:00:54: (mod_openssl.c.1419) SSL: renegotiation initiated by 
client, killing connection 
2018-11-08 19:00:54: (mod_openssl.c.1419) SSL: renegotiation initiated by 
client, killing connection 

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

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

Versions of packages lighttpd depends on:
ii  libattr11:2.4.47-2+b2
ii  libbz2-1.0  1.0.6-9
ii  libc6   2.27-8
ii  libfam0 2.7.0-17.2+b1
ii  libldap-2.4-2   2.4.46+dfsg-5+b1
ii  libmariadbclient18  1:10.1.37-1
ii  libpcre32:8.39-11
ii  libssl1.1   1.1.1-2
ii  lsb-base9.20170808
ii  mime-support3.61
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages lighttpd recommends:
ii  spawn-fcgi  1.6.4-2

Versions of packages lighttpd suggests:
pn  apache2-utils  
pn  lighttpd-doc   
ii  openssl1.1.1-2
pn  php-cgi
pn  rrdtool

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lighttpd
Source-Version: 1.4.49-2

We believe that the bug you reported is fixed in the latest version of
lighttpd, 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 913...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated lighttpd 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: Sun, 02 Dec 2018 19:26:05 -0800
Source: lighttpd
Binary: lighttpd lighttpd-doc lighttpd-mod-mysql-vhost 
lighttpd-mod-trigger-b4-dl lighttpd-mod-cml lighttpd-mod-magnet 
lighttpd-mod-webdav lighttpd-mod-authn-gssapi lighttpd-mod-authn-ldap 
lighttpd-mod-authn-mysql lighttpd-mod-geoip
Architecture: source
Version: 1.4.49-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Ximin Luo 
Description:
 lighttpd   - fast webserver with minimal memory footprint
 lighttpd-doc - documentation for lighttpd
 lighttpd-mod-authn-gssapi - GGSAPI authentication for lighttpd
 lighttpd-mod-authn-ldap - LDAP authentication for lighttpd
 lighttpd-mod-authn-mysql - MySQL authentication for lighttpd
 lighttpd-mod-cml - cache meta language module for lighttpd
 lighttpd-mod-geoip - GeoIP restrictions for lighttpd
 lighttpd-mod-magnet - control the request handling module for lighttpd
 lighttpd-mod-mysql-vhost - MySQL-based virtual host configuration for lighttpd
 lighttpd-mod-trigger-b4-dl - anti-deep-linking module for lighttpd
 lighttpd-mod-webdav - WebDAV module for lighttpd
Closes: 913249 913251
Changes:
 lighttpd (1.4.49-2) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Ondřej Nový ]
   * d/copyright: Change Format URL to correct one
 .
   [ Ximin Luo ]
   * Add a patch to work against openssl 1.1.1. (Closes: #913251)
   * Add Depends: perl. (Closes: #913249)
Checksums-Sha1:
 a6a6c0f6e51ff4e7b7bd58eda750256e5ff5d0e0 2330 

Bug#913249: marked as done (lighttpd: Can't locate Term/ReadLine.pm in @INC)

[Debian Bug Tracking System]

Your message dated Mon, 03 Dec 2018 03:49:23 +
with message-id 
and subject line Bug#913249: fixed in lighttpd 1.4.49-2
has caused the Debian Bug report #913249,
regarding lighttpd: Can't locate Term/ReadLine.pm in @INC
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.)


-- 
913249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lighttpd
Version: 1.4.49-1.1+b1
Severity: normal

Dear Maintainer,

# lighty-enable-mod ssl

Can't locate Term/ReadLine.pm in @INC (you may need to install the 
Term::ReadLine module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.0 /usr/local/share/perl/5.28.0 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/sbin/lighty-enable-mod line 17.
BEGIN failed--compilation aborted at /usr/sbin/lighty-enable-mod line 17.

Gr,

Olaf

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

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

Versions of packages lighttpd depends on:
ii  libattr11:2.4.47-2+b2
ii  libbz2-1.0  1.0.6-9
ii  libc6   2.27-8
ii  libfam0 2.7.0-17.2+b1
ii  libldap-2.4-2   2.4.46+dfsg-5+b1
ii  libmariadbclient18  1:10.1.37-1
ii  libpcre32:8.39-11
ii  libssl1.1   1.1.1-2
ii  lsb-base9.20170808
ii  mime-support3.61
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages lighttpd recommends:
ii  spawn-fcgi  1.6.4-2

Versions of packages lighttpd suggests:
pn  apache2-utils  
pn  lighttpd-doc   
ii  openssl1.1.1-2
pn  php-cgi
pn  rrdtool

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lighttpd
Source-Version: 1.4.49-2

We believe that the bug you reported is fixed in the latest version of
lighttpd, 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 913...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated lighttpd 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: Sun, 02 Dec 2018 19:26:05 -0800
Source: lighttpd
Binary: lighttpd lighttpd-doc lighttpd-mod-mysql-vhost 
lighttpd-mod-trigger-b4-dl lighttpd-mod-cml lighttpd-mod-magnet 
lighttpd-mod-webdav lighttpd-mod-authn-gssapi lighttpd-mod-authn-ldap 
lighttpd-mod-authn-mysql lighttpd-mod-geoip
Architecture: source
Version: 1.4.49-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Ximin Luo 
Description:
 lighttpd   - fast webserver with minimal memory footprint
 lighttpd-doc - documentation for lighttpd
 lighttpd-mod-authn-gssapi - GGSAPI authentication for lighttpd
 lighttpd-mod-authn-ldap - LDAP authentication for lighttpd
 lighttpd-mod-authn-mysql - MySQL authentication for lighttpd
 lighttpd-mod-cml - cache meta language module for lighttpd
 lighttpd-mod-geoip - GeoIP restrictions for lighttpd
 lighttpd-mod-magnet - control the request handling module for lighttpd
 lighttpd-mod-mysql-vhost - MySQL-based virtual host configuration for lighttpd
 lighttpd-mod-trigger-b4-dl - anti-deep-linking module for lighttpd
 lighttpd-mod-webdav - WebDAV module for lighttpd
Closes: 913249 913251
Changes:
 lighttpd (1.4.49-2) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Ondřej Nový ]
   * d/copyright: Change Format URL to correct one
 .
   [ Ximin Luo ]
   * Add a patch to work against openssl 1.1.1. (Closes: #913251)
   * Add Depends: perl. (Closes: #913249)
Checksums-Sha1:
 a6a6c0f6e51ff4e7b7bd58eda750256e5ff5d0e0 2330 lighttpd_1.4.49-2.dsc
 eb7cc4e53ffd1809edf466a8414b5c20f2dcadb9 47324 lighttpd_1.4.49-2.debian.tar.xz
 08537ec9e410929d83d9539300526045ccb028bd 7799 
lighttpd_1.4.49-2_source.buildinfo
Checksums-Sha256:
 

Bug#915364: qbittorrent again crashes when starting talks of symbol lookup error

[Martin Haase]

Package: qbittorrent
Version: 4.1.4-1
Severity: grave
Justification: renders package unusable

qbittorrent: symbol lookup error: qbittorrent: undefined symbol:
_ZN10libtorrent7session5startEiRKNS_13settings_packEPN5boost4asio10io_contextE

The incident had been reported as bug #913953 and was subsequently declared as
resolved. However, after I've upgraded qbittorrent it appeared again.
Meaning, the bug doesn't seem to have been resolved after all.


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 
(charmap=ISO-8859-15) (ignored: LC_ALL set to en_GB.ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages qbittorrent depends on:
ii  geoip-database 20160111-1
ii  libboost-system1.67.0  1.67.0-11
ii  libc6  2.27-6
ii  libgcc11:7.3.0-1
ii  libqt5core5a   5.11.2+dfsg-7
ii  libqt5dbus55.11.2+dfsg-7
ii  libqt5gui5 5.11.2+dfsg-7
ii  libqt5network5 5.11.2+dfsg-7
ii  libqt5widgets5 5.11.2+dfsg-7
ii  libqt5xml5 5.11.2+dfsg-7
ii  libstdc++6 7.3.0-1
ii  libtorrent-rasterbar9  1.1.9-1
ii  python 2.7.11-1
ii  zlib1g 1:1.2.11.dfsg-1

qbittorrent recommends no packages.

Versions of packages qbittorrent suggests:
pn  qbittorrent-dbg  

-- no debconf information

Bug#911830: FTBFS on multiple architectures

[Yaroslav Halchenko]

On Sun, 02 Dec 2018, Yaroslav Halchenko wrote:

> > There's no visible progress on this problem in git -- is there progress 
> > elsewhere?

> you could find some traces of the progress which lead to i386 fixes on
> https://github.com/scikit-learn/scikit-learn/issues?utf8=%E2%9C%93=is%3Aissue+author%3Ayarikoptic+

> I welcome you to review/analyze failures on other platforms and/or just
> report them upstream.  or I would do it whenever I get a chance 

s390x (and also arm64) issue is here upstream
https://github.com/scikit-learn/scikit-learn/issues/10561

if you care to help, please try to figure out WTF with ppc64el:
https://buildd.debian.org/status/fetch.php?pkg=scikit-learn=ppc64el=0.20.1%2Bdfsg-1=1543512601=0
where it even doesn't build... might be a cython issue

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


signature.asc
Description: PGP signature

Bug#911830: FTBFS on multiple architectures

[Yaroslav Halchenko]

On Sun, 02 Dec 2018, Stuart Prescott wrote:

> Dear Yaroslav & Michael,

> scikit-learn currently FTBFS everywhere. 

please define your version of "everywhere".  From
https://buildd.debian.org/status/package.php?p=scikit-learn=unstable
I see that 0.20.1+dfsg-1 builds fine on all intel and mips architectures

I would not upload a version which FTBFS on amd64, and unlikely to
upload the one which FTBFS on i386

> I've had a bit of a poke at it and 
> not got very far:

> - if run as a parallel build, I can't figure out what actually fails

> - if run with only one job (sbuild -j1), the build does not actually attempt 
> to build with either python 3.6 or 3.7 at all. (which sounds like a separate 
> bug in d/rules)

I guess any relevant "parallelism" effects (although there was a recent
fix also for joblib and non-parallel runs) stem from

2b495fe013 (yangfl 2018-10-19 23:22:43 +0800  72) # silly distutils does not 
support parallelism! waste hours of time
2b495fe013 (yangfl 2018-10-19 23:22:43 +0800  73) .PHONY: build
32438ee441 (yangfl 2018-10-20 16:06:58 +0800  74) build build-arch build-indep:
32438ee441 (yangfl 2018-10-20 16:06:58 +0800  75)   $(MAKE) -j $(JOBS) -f 
debian/rules _$@

so CCing Yangfl who worked on improving packaging at some point.  Unfortunately
neither from those commits messages, nor from debian/changelog I could not
figure out what was the purpose of this act really and either it is kosher at
all  (e.g. wouldn't confuse dh)

> There's no visible progress on this problem in git -- is there progress 
> elsewhere?

you could find some traces of the progress which lead to i386 fixes on
https://github.com/scikit-learn/scikit-learn/issues?utf8=%E2%9C%93=is%3Aissue+author%3Ayarikoptic+

I welcome you to review/analyze failures on other platforms and/or just
report them upstream.  or I would do it whenever I get a chance 

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#915200: marked as done (pyjwt FTBFS with pytest 3.10.1-1)

[Debian Bug Tracking System]

Your message dated Mon, 03 Dec 2018 01:19:47 +
with message-id 
and subject line Bug#915200: fixed in pyjwt 1.7.0-1
has caused the Debian Bug report #915200,
regarding pyjwt FTBFS with pytest 3.10.1-1
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.)


-- 
915200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyjwt
Version: 1.6.4-1
Severity: serious
Tags: ftbfs

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd /build/1st/pyjwt-1.6.4/.pybuild/cpython2_2.7_jwt/build; 
python2.7 -m pytest tests
= test session starts ==
platform linux2 -- Python 2.7.15+, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
rootdir: /build/1st/pyjwt-1.6.4, inifile: setup.cfg
plugins: cov-2.6.0
collected 188 items

tests/test_algorithms.py .   [ 23%]
tests/test_api_jws.py .F.s.. [ 50%]
..   [ 53%]
tests/test_api_jwt.py ..F[ 76%]
tests/test_cli.py .  [ 83%]
tests/test_compat.py ... [ 85%]
tests/test_exceptions.py .   [ 85%]
tests/test_jwt.py .  [ 86%]
tests/test_utils.py .x...[ 93%]
tests/contrib/test_algorithms.py s   [100%]

=== FAILURES ===
___ TestJWS.test_decode_no_algorithms_verify_signature_false ___

self = 
jws = 

def test_decode_no_algorithms_verify_signature_false(self, jws):
example_secret = 'secret'
example_jws = (
b'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.'
b'aGVsbG8gd29ybGQ.'
b'SIr03zM64awWRdPrAM_61QWsZchAtgDV3pphfHPPWkI'
)

try:
pytest.deprecated_call(
jws.decode, example_jws, key=example_secret,
>   options={'verify_signature': False},
)
E   Failed: DID NOT WARN. No warnings of type (, ) was emitted. The list of emitted 
warnings is: [].

tests/test_api_jws.py:295: Failed
 TestJWT.test_decode_no_algorithms_verify_false 

self = 
jwt = 
payload = {'claim': 'insanity', 'exp': 1543624411, 'iss': 'jeff'}

def test_decode_no_algorithms_verify_false(self, jwt, payload):
secret = 'secret'
jwt_message = jwt.encode(payload, secret)

try:
pytest.deprecated_call(
>   jwt.decode, jwt_message, secret, verify=False,
)
E   Failed: DID NOT WARN. No warnings of type (, ) was emitted. The list of emitted 
warnings is: [].

tests/test_api_jwt.py:517: Failed

-- coverage: platform linux2, python 2.7.15-final-0 --
Name Stmts   Miss  Cover   Missing
--
jwt/__init__.py  9  0   100%
jwt/__main__.py 63  0   100%
jwt/algorithms.py  173  299%   31-32
jwt/api_jws.py 130  199%   119
jwt/api_jwt.py 121  0   100%
jwt/compat.py   35 1751%   15-16, 26-42, 46-54
jwt/contrib/__init__.py  0  0   100%
jwt/contrib/algorithms/__init__.py   0  0   100%
jwt/contrib/algorithms/py_ecdsa.py  29 27 7%   8-60
jwt/contrib/algorithms/pycrypto.py  26 25 4%   2-46
jwt/exceptions.py   30  0   100%
jwt/help.py 31 31 0%   1-61
jwt/utils.py70  396%   11-12, 19
tests/__init__.py0  0   100%
tests/compat.py  7  271%   8-9
tests/contrib/__init__.py0  0   100%
tests/contrib/test_algorithms.py   104 7726%   11, 17, 25-28, 
31-34, 37-40, 43-63, 66-84, 87-103, 106-112, 118-121, 124-127, 130-147, 
150-165, 168-181, 184-190
tests/keys/__init__.py  34  779%   28-29, 33-34, 41-44
tests/test_algorithms.py   280  

Bug#915311: dumb-init FTBFS on mips*: test failures

[Chris Kuehl]

Hi Adrian,

Thanks for filing this. I can't be certain, but I have a strong
suspicion that this is caused by a bug that we fixed upstream with
dumb-init 1.2.2 which was causing flakiness in the test suite on
certain environments and architectures.

The bug was: https://github.com/Yelp/dumb-init/issues/136
The patch was: https://github.com/Yelp/dumb-init/pull/174

If possible, I would suggest packaging the latest version of dumb-init
(currently 1.2.2) as the easiest way to fix this.

Please let me know if there's any way we can help from the upstream side.

On Sun, Dec 2, 2018 at 9:39 AM Adrian Bunk  wrote:
>
> Source: dumb-init
> Version: 1.2.0-1
> Severity: serious
> Tags: ftbfs
>
> https://buildd.debian.org/status/package.php?p=dumb-init
>
> ...
> === FAILURES 
> ===
> _ test_all_processes_receive_term_on_exit_if_setsid[1] 
> _
>
> @pytest.mark.usefixtures('both_debug_modes', 'setsid_enabled')
> def test_all_processes_receive_term_on_exit_if_setsid():
> """If the child exits for some reason, dumb-init should send TERM to 
> all
> processes in its session if setsid mode is enabled."""
> >   child_pid, child_stdout = spawn_process_which_dies_with_children()
>
> tests/child_processes_test.py:109:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _
>
> def spawn_process_which_dies_with_children():
> """Spawn a process which spawns some children and then dies without
> signaling them, wrapped in dumb-init.
>
> Returns a tuple (child pid, child stdout pipe), where the child is
> print_signals. This is useful because you can signal the PID and see 
> if
> anything gets printed onto the stdout pipe.
> """
> proc = Popen(
> (
> 'dumb-init',
> 'sh', '-c',
>
> # we need to sleep before the shell exits, or dumb-init might 
> send
> # TERM to print_signals before it has had time to register 
> custom
> # signal handlers
> '{python} -m testing.print_signals & sleep 0.1'.format(
> python=sys.executable,
> ),
> ),
> stdout=PIPE,
> )
> proc.wait()
> assert proc.returncode == 0
>
> # read a line from print_signals, figure out its pid
> line = proc.stdout.readline()
> match = re.match(b'ready \(pid: ([0-9]+)\)\n', line)
> >   assert match, line
> E   AssertionError:
> E   assert None
>
> tests/child_processes_test.py:95: AssertionError
> - Captured stderr call 
> -
> [dumb-init] Running in debug mode.
> [dumb-init] Unable to detach from controlling tty (errno=25 Inappropriate 
> ioctl for device).
> [dumb-init] Child spawned with PID 7035.
> [dumb-init] Unable to attach to controlling tty (errno=25 Inappropriate ioctl 
> for device).
> [dumb-init] setsid complete.
> [dumb-init] Received signal 18.
> [dumb-init] A child with PID 7035 exited with exit status 0.
> [dumb-init] Forwarded signal 15 to children.
> [dumb-init] Child exited with status 0. Goodbye.
> _ test_all_processes_receive_term_on_exit_if_setsid[0] 
> _
>
> @pytest.mark.usefixtures('both_debug_modes', 'setsid_enabled')
> def test_all_processes_receive_term_on_exit_if_setsid():
> """If the child exits for some reason, dumb-init should send TERM to 
> all
> processes in its session if setsid mode is enabled."""
> >   child_pid, child_stdout = spawn_process_which_dies_with_children()
>
> tests/child_processes_test.py:109:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _
>
> def spawn_process_which_dies_with_children():
> """Spawn a process which spawns some children and then dies without
> signaling them, wrapped in dumb-init.
>
> Returns a tuple (child pid, child stdout pipe), where the child is
> print_signals. This is useful because you can signal the PID and see 
> if
> anything gets printed onto the stdout pipe.
> """
> proc = Popen(
> (
> 'dumb-init',
> 'sh', '-c',
>
> # we need to sleep before the shell exits, or dumb-init might 
> send
> # TERM to print_signals before it has had time to register 
> custom
> # signal handlers
> '{python} -m testing.print_signals & sleep 0.1'.format(
> python=sys.executable,
> ),
> ),
> stdout=PIPE,
> )
> proc.wait()
> assert proc.returncode == 0
>
> # read a line from print_signals, figure out its pid
> line = proc.stdout.readline()
> match = re.match(b'ready \(pid: ([0-9]+)\)\n', 

Bug#915143: Thanks and happy holidays! (Was: Bug#915143)

[Kingsley G. Morse Jr.]

Hi Matteo,

Thanks for the good news!

I look forward to testing the fix.

Happy holidays,
Kingsley

On 12/02/2018 21:50, Matteo F. Vescovi wrote:
> Control: tag -1 pending
> 
> Hello,
> 
> Bug #915143 in blender 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/multimedia-team/blender/commit/5db4afd64d9849001bb5d92ce3c45205aea2de4d
> 
> 
> debian/patches/: patchset updated
> 
> - 0010-fix_PyRNA_with_Python3.7.patch added
> 
> Closes: #915143
> 
> 
> 
> (this message was generated automatically)
> -- 
> Greetings
> 
> https://bugs.debian.org/915143

-- 
Time is the fire in which we all burn.

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

[Wouter Verhelst]

On Sun, Dec 02, 2018 at 11:31:13PM +0100, Marco d'Itri wrote:
> On Dec 02, Wouter Verhelst  wrote:
> 
> > One thing that has not been answered yet in this discussion (and if the
> > TC is to make a decision about it, I think it should be) is "why are we
> > doing this". That is, what is the problem that usrmerge is meant to
> > solve, and how does it attempt to solve it? As far as I know, the reason
> > usrmerge exists is so that no files will be installed in /bin anymore;
> > but that seems like an XY problem.
> https://lists.debian.org/20181121140542.ga31...@espresso.pseudorandom.co.uk

Thanks; somehow I missed that, sorry.

> > Also, I would like to ask why the traditional solution in Debian -- make
> > a policy change that says no package can ship anything in /bin except
> > for a compatibility symlink, and make that rule RC at some point in the
> > future -- is not being considered. That seems like a solution that would
> > cause far less pain than what we're going through right now.
> This is not a solution. For a start it would take many years.

The fact that doing something in one particular way takes longer does
not in and of itself make it a bad solution.

It also need not take that long. We can declare *right now* that
shipping something in /bin (as opposed to /usr/bin) that is not a
compatibility symlink will be RC in bullseye. This would be plenty of
time for maintainers to be aware of it and to start looking at updating
their packages. With your usrmerge package, it's not at all clear to me
when the migration would be finished.

> Even ignoring that, it would not bring any improvement over the current 
> plan:

This is incorrect. The current plan has some systems be merged-/usr and
others not while we are in the transition. It therefore introduces
Debian-wide complexity in that maintainers are expected to support both
merged and unmerged /usr, which causes problems (as we see here). It
also effects a change without the maintainers of the software in
question being involved, which could have unintended side effects with
some packages that we don't know yet (and that we probably won't know
about until the release of buster).

Changing this through a policy change, as we've always done, would not
have those problems:

- Maintainers are expected to move their own package to merged-/usr, so
  they would be aware of issues that might ensue and would be able to
  deal with them.
- We are not expected to be supporting merged-/usr and unmerged-/usr at
  the same time; instead, we'll be gradually moving towards a
  merged-/usr situation.
- We don't end up with packages' files being moved from under them.

> even if your idea were executed perfectly and quickly then the 
> conversion program would still be in the same exact situation as it is 
> now:

Yes, obviously, that's the whole point.

[...]
> So this would make the transition unacceptably slow while providing no 
> benefit at all,

I don't agree with both these statements.

> but it would also cost a huge amount of work to change many packages.

Yes, and at the same time it would reduce a huge amount of *different*
work, since packages now won't need to be changed so that "being built
on merged-/usr" won't result in packages that don't build on
unmerged-/usr.

-- 
To the thief who stole my anti-depressants: I hope you're happy

  -- seen somewhere on the Internet on a photo of a billboard

Bug#914897: debating the wrong thing

[Adam Borowski]

I see that we're debating the merits of merged-usr vs non-merged-usr, while
expending lots of effort and filing bugs (requiring further urgent action of
unrelated maintainers), for little gain.

In the above, note that the debate vs effort touch different problems:

1. is usrmerge good?
vs
2. how to support both?

I say that 1. is a relatively small issue.  After dropping support for
booting from split /-vs-/usr without initrd, the difference doesn't really
matter.  I'm against pointless moves, but it's not worth an endless debate.
My objection is: repainting the house is a lot of work, paint fumes are bad
for health, the old color was fine and the old paint isn't noticeably flaky.

On the other hand, 2. is madness.  It's taking down load-bearing walls just
so you can have visible sides of both colours.

All the bugs you folks just filed are completely moot if we go all-in,
all-out or step-back-then-in.  So please at least stop filing extra bugs
before the TC decides on the course.

So, let's enumerate possible outcomes:

1. no usrmerge
  1a. no moves at all (no effort needed!)
  1b. moves via some dh_usrmove tool, until /bin is empty
2. supporting both merged-usr and unmerged-usr
3. mandatory usrmerge
  3a. by Bullseye
  3b. by Buster

Unless the TC decides for 2., all this work will be a pure waste of yours
and maintainers' time.

With 1a, 1b, 3a the result will be "revert the change in debootstrap" (in
3a "for now").  With 3b you need some way to make sure existing systems are
converted (also with 3a except for far more time for testing).

And any effort spent doing one of the numbered choices is wasted if we end
up with a choice with a different number.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Ivan was a wordly man: born in St. Petersburg, raised in
⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned
⠈⠳⣄ to the city of his birth to die.

Bug#915321: Mutex creation failed

[Aurelien Jarno]

On 2018-12-03 00:59, Adrian Bunk wrote:
> Control: unmerge -1 915339
> Control: reassign -1 r-cran-later 0.7.4+dfsg-1
> Control: retitle -1 r-cran-later: Mutex creation failed with glibc 2.28
> Control: forwarded -1 https://github.com/r-lib/later/issues/77
> Control: block 915339 by -1
> Control: retitle 915339 libc6 needs Conflicts with unfixed r-cran-later
> 
> On Sun, Dec 02, 2018 at 09:11:06PM +0200, Theodore Lytras wrote:
> > Package: libc6
> > Version: 2.28-1
> > Severity: critical
> > 
> > Just after updating libc6 from 2.27-8 to 2.28-1 in Debian Unstable, loading 
> > package "httpuv" in R leads to a crash:
> > 
> >bones@equinox2:~$ R
> >
> >R version 3.5.1 (2018-07-02) -- "Feather Spray"
> >Copyright (C) 2018 The R Foundation for Statistical Computing
> >Platform: x86_64-pc-linux-gnu (64-bit)
> >
> >R is free software and comes with ABSOLUTELY NO WARRANTY.
> >You are welcome to redistribute it under certain conditions.
> >Type 'license()' or 'licence()' for distribution details.
> >
> >R is a collaborative project with many contributors.
> >Type 'contributors()' for more information and
> >'citation()' on how to cite R or R packages in publications.
> >
> >Type 'demo()' for some demos, 'help()' for on-line help, or
> >'help.start()' for an HTML browser interface to help.
> >Type 'q()' to quit R.
> >
> >> library(httpuv)
> >terminate called after throwing an instance of 'std::runtime_error'
> >  what():  Mutex creation failed
> >Ακυρώθηκε
> >bones@equinox2:~$ 
> > 
> > From the message I understand this is directly related to libc6 and not R 
> > or httpuv. 
> > Also, there was no update to R or httpuv done recently. The problem started 
> > just as I updated libc6.
> >...
> 
> This seems to be a bug in r-cran-later, I'm reassigning this bug there 
> and leave another bug here for adding a Conflicts with the unfixed
> r-cran-later afterwards.

While the pointer to the bug is correct, I am not sure we need to
reassign the bug there. Nothing has to be changed in r-cran-later, it
just has to be binNMued against glibc 2.28. OTOH, we need to add a Break
on the glibc side.

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

Processed: And set the blocking in the wrong direction

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unblock 915321 by 915339
Bug #915321 [r-cran-later] r-cran-later: Mutex creation failed with glibc 2.28
915321 was blocked by: 915339
915321 was not blocking any bugs.
Removed blocking bug(s) of 915321: 915339
> block 915339 by 915321
Bug #915339 [libc6] libc6 needs Conflicts with unfixed r-cran-later
915339 was not blocked by any bugs.
915339 was not blocking any bugs.
Added blocking bug(s) of 915339: 915321
> thanks
Stopping processing here.

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

Processed: Re: Bug#915207: gnudatalanguage: autopkgtests fail: test_bug_n000720, test_idlneturl, test_point_lun, test_save_restore, test_zip

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #915207 {Done: Ole Streicher } [src:gnudatalanguage] 
gnudatalanguage: autopkgtests fail: test_bug_n000720, test_idlneturl, 
test_point_lun, test_save_restore, test_zip
'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 gnudatalanguage/0.9.9-1.
> notfixed -1 gnudatalanguage/0.9.9-1
Bug #915207 [src:gnudatalanguage] gnudatalanguage: autopkgtests fail: 
test_bug_n000720, test_idlneturl, test_point_lun, test_save_restore, test_zip
Ignoring request to alter fixed versions of bug #915207 to the same values 
previously set
> severity -1 serious
Bug #915207 [src:gnudatalanguage] gnudatalanguage: autopkgtests fail: 
test_bug_n000720, test_idlneturl, test_point_lun, test_save_restore, test_zip
Severity set to 'serious' from 'important'
> block 913837 by -1
Bug #913837 [release.debian.org] transition: hdf5
913837 was blocked by: 914493
913837 was not blocking any bugs.
Added blocking bug(s) of 913837: 915207

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

Bug#900160: closed by Didier Raboud (Bug#900160: fixed in ruby-eventmachine 1.0.7-4.1)

[Kurt Roeckx]

On Sun, Dec 02, 2018 at 11:36:06PM +0100, gregor herrmann wrote:
> On Sun, 02 Dec 2018 23:18:38 +0100, Sebastian Andrzej Siewior wrote:
> 
> > On 2018-12-02 13:06:04 [+], Debian Bug Tracking System wrote:
> > > #900160: ruby-eventmachine: FTBFS against openssl 1.1.1
> > >  ruby-eventmachine (1.0.7-4.1) unstable; urgency=medium
> > >  .
> > >* Non-maintainer upload.
> > >* Build-Depend against libssl1.0-dev; aka OpenSSL << 1.1
> > >  (Closes: #900160)
> > 
> > Please revert that one. We don't want more dependencies on
> > libssl1.0-dev. We want it actually out of testing and are down to one
> > package.
> > I wouldn't care much but since ruby-eventmachine is a key package it
> > might migrate to testing…
> 
> Raising the severity of the cloned #915287 which tracks this problem
> should prevent the migration.

It won't, since it affects also the version in testing, it can
just migrate.


Kurt

Processed: Cleanup the mess created by my syntax error

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unmerge 915339
Bug #915339 [r-cran-later] libc6 needs Conflicts with unfixed r-cran-later
Bug #915321 [r-cran-later] libc6 needs Conflicts with unfixed r-cran-later
Disconnected #915339 from all other report(s).
> retitle 915321 r-cran-later: Mutex creation failed with glibc 2.28
Bug #915321 [r-cran-later] libc6 needs Conflicts with unfixed r-cran-later
Changed Bug title to 'r-cran-later: Mutex creation failed with glibc 2.28' from 
'libc6 needs Conflicts with unfixed r-cran-later'.
> reassign 915339 libc6 2.28-1
Bug #915339 [r-cran-later] libc6 needs Conflicts with unfixed r-cran-later
Bug reassigned from package 'r-cran-later' to 'libc6'.
No longer marked as found in versions r-cran-later/0.7.4+dfsg-1.
Ignoring request to alter fixed versions of bug #915339 to the same values 
previously set
Bug #915339 [libc6] libc6 needs Conflicts with unfixed r-cran-later
Marked as found in versions glibc/2.28-1.
> severity 915339 serious
Bug #915339 [libc6] libc6 needs Conflicts with unfixed r-cran-later
Ignoring request to change severity of Bug 915339 to the same value.
> notforwarded 915339
Bug #915339 [libc6] libc6 needs Conflicts with unfixed r-cran-later
Unset Bug forwarded-to-address
> block 915321 by 915339
Bug #915321 [r-cran-later] r-cran-later: Mutex creation failed with glibc 2.28
915321 was not blocked by any bugs.
915321 was not blocking any bugs.
Added blocking bug(s) of 915321: 915339
> thanks
Stopping processing here.

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

Bug#915321: Mutex creation failed

[Aurelien Jarno]

On 2018-12-02 21:11, Theodore Lytras wrote:
> Package: libc6
> Version: 2.28-1
> Severity: critical
> 
> Just after updating libc6 from 2.27-8 to 2.28-1 in Debian Unstable, loading 
> package "httpuv" in R leads to a crash:
> 
>bones@equinox2:~$ R
>
>R version 3.5.1 (2018-07-02) -- "Feather Spray"
>Copyright (C) 2018 The R Foundation for Statistical Computing
>Platform: x86_64-pc-linux-gnu (64-bit)
>
>R is free software and comes with ABSOLUTELY NO WARRANTY.
>You are welcome to redistribute it under certain conditions.
>Type 'license()' or 'licence()' for distribution details.
>
>R is a collaborative project with many contributors.
>Type 'contributors()' for more information and
>'citation()' on how to cite R or R packages in publications.
>
>Type 'demo()' for some demos, 'help()' for on-line help, or
>'help.start()' for an HTML browser interface to help.
>Type 'q()' to quit R.
>
>> library(httpuv)
>terminate called after throwing an instance of 'std::runtime_error'
>  what():  Mutex creation failed
>Ακυρώθηκε
>bones@equinox2:~$ 
> 
> From the message I understand this is directly related to libc6 and not R or 
> httpuv. 
> Also, there was no update to R or httpuv done recently. The problem started 
> just as I updated libc6.

From what I have been able to find, it seems to be a namespace conflict
issue between r-cran-later and glibc 2.28. r-cran-later requires C11
threads support, and when it is not available from glibc (like in 2.27),
it uses tinycthread. When upgrading to glibc 2.28, r-cran-later tries to
use the mtx_init symbol from tinycthread, but end-up using the glibc one,
leading to the above crash.

Rebuilding r-cran-later against glibc 2.28 to enable C11 threads support
from glibc is enough to fix the issue. I believe we should binNMU it and
add Breaks: on the glibc side.

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

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

[Adam Borowski]

On Sun, Dec 02, 2018 at 11:31:13PM +0100, Marco d'Itri wrote:
> On Dec 02, Wouter Verhelst  wrote:> 
> > One thing that has not been answered yet in this discussion (and if the
> > TC is to make a decision about it, I think it should be) is "why are we
> > doing this". That is, what is the problem that usrmerge is meant to
> > solve, and how does it attempt to solve it? As far as I know, the reason
> > usrmerge exists is so that no files will be installed in /bin anymore;
> > but that seems like an XY problem.
> https://lists.debian.org/20181121140542.ga31...@espresso.pseudorandom.co.uk

That post is too long-winded and touches so many unrelated issues that it's
difficult to respond to it.  Could you please give us a terse list of
claimed benefits?  Without a clear claim, it's too easy to both do or be
accused of doing a straw-man.

By my reading, most of that post either falls into the XY problem or
explains how merged-usr fixes problems caused by merged-usr itself.
That leaves only one concrete claim:
* that merged-usr makes it easier to have a part of the system immutable
  (be it for recovery purposes or for sharing)

My response to that claim is: there's a long list of techniques that can be
used for such an effect without sweeping distribution-wide changes.  Heck,
not even a couple of hours ago I restored from a snapshot multiple times in
order to troubleshoot a broken udev problem.  Here's your "This means you
always have a known-working filesystem to fall back on (if the most recently
updated filesystem doesn't boot, use the other one)".  Or, container
sharing: works fine for me without merged-usr either.  Thus, in order to
make this claim stick, you need to not only list its benefits but also
explain how it's better than other approaches: filesystem-based (btrfs, ZFS,
XFS), vfs-based (various overlays), lvm-based/-like, block-device based,
multiple mounts, etc.  And, many of those can do CoW which is so much better
than immutability.


(Please explain if I understood you wrong.)


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Ivan was a wordly man: born in St. Petersburg, raised in
⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned
⠈⠳⣄ to the city of his birth to die.

Bug#915321: Mutex creation failed

[Adrian Bunk]

Control: unmerge -1 915339
Control: reassign -1 r-cran-later 0.7.4+dfsg-1
Control: retitle -1 r-cran-later: Mutex creation failed with glibc 2.28
Control: forwarded -1 https://github.com/r-lib/later/issues/77
Control: block 915339 by -1
Control: retitle 915339 libc6 needs Conflicts with unfixed r-cran-later

On Sun, Dec 02, 2018 at 09:11:06PM +0200, Theodore Lytras wrote:
> Package: libc6
> Version: 2.28-1
> Severity: critical
> 
> Just after updating libc6 from 2.27-8 to 2.28-1 in Debian Unstable, loading 
> package "httpuv" in R leads to a crash:
> 
>bones@equinox2:~$ R
>
>R version 3.5.1 (2018-07-02) -- "Feather Spray"
>Copyright (C) 2018 The R Foundation for Statistical Computing
>Platform: x86_64-pc-linux-gnu (64-bit)
>
>R is free software and comes with ABSOLUTELY NO WARRANTY.
>You are welcome to redistribute it under certain conditions.
>Type 'license()' or 'licence()' for distribution details.
>
>R is a collaborative project with many contributors.
>Type 'contributors()' for more information and
>'citation()' on how to cite R or R packages in publications.
>
>Type 'demo()' for some demos, 'help()' for on-line help, or
>'help.start()' for an HTML browser interface to help.
>Type 'q()' to quit R.
>
>> library(httpuv)
>terminate called after throwing an instance of 'std::runtime_error'
>  what():  Mutex creation failed
>Ακυρώθηκε
>bones@equinox2:~$ 
> 
> From the message I understand this is directly related to libc6 and not R or 
> httpuv. 
> Also, there was no update to R or httpuv done recently. The problem started 
> just as I updated libc6.
>...

This seems to be a bug in r-cran-later, I'm reassigning this bug there 
and leave another bug here for adding a Conflicts with the unfixed
r-cran-later afterwards.

cu
Adrian

-- 

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

Processed (with 2 errors): Re: Bug#915321: Mutex creation failed

[Debian Bug Tracking System]

Processing control commands:

> unmerge -1 915339
Unknown command or malformed arguments to command.

> reassign -1 r-cran-later 0.7.4+dfsg-1
Bug #915321 [libc6] Mutex creation failed
Bug #915339 [libc6] r-cran-treespace FTBFS: terminate called after throwing an 
instance of 'std::runtime_error'
Bug reassigned from package 'libc6' to 'r-cran-later'.
Bug reassigned from package 'libc6' to 'r-cran-later'.
No longer marked as found in versions glibc/2.28-1.
No longer marked as found in versions glibc/2.28-1.
Ignoring request to alter fixed versions of bug #915321 to the same values 
previously set
Ignoring request to alter fixed versions of bug #915339 to the same values 
previously set
Bug #915321 [r-cran-later] Mutex creation failed
Bug #915339 [r-cran-later] r-cran-treespace FTBFS: terminate called after 
throwing an instance of 'std::runtime_error'
Marked as found in versions r-cran-later/0.7.4+dfsg-1.
Marked as found in versions r-cran-later/0.7.4+dfsg-1.
> retitle -1 r-cran-later: Mutex creation failed with glibc 2.28
Bug #915321 [r-cran-later] Mutex creation failed
Bug #915339 [r-cran-later] r-cran-treespace FTBFS: terminate called after 
throwing an instance of 'std::runtime_error'
Changed Bug title to 'r-cran-later: Mutex creation failed with glibc 2.28' from 
'Mutex creation failed'.
Changed Bug title to 'r-cran-later: Mutex creation failed with glibc 2.28' from 
'r-cran-treespace FTBFS: terminate called after throwing an instance of 
'std::runtime_error''.
> forwarded -1 https://github.com/r-lib/later/issues/77
Bug #915321 [r-cran-later] r-cran-later: Mutex creation failed with glibc 2.28
Bug #915339 [r-cran-later] r-cran-later: Mutex creation failed with glibc 2.28
Set Bug forwarded-to-address to 'https://github.com/r-lib/later/issues/77'.
Set Bug forwarded-to-address to 'https://github.com/r-lib/later/issues/77'.
> block 915339 by -1
Bug #915339 [r-cran-later] r-cran-later: Mutex creation failed with glibc 2.28
Bug #915321 [r-cran-later] r-cran-later: Mutex creation failed with glibc 2.28
Failed to set blocking bugs of 915339: It is nonsensical for a bug to block 
itself (or a merged partner): 915321.

> retitle 915339 libc6 needs Conflicts with unfixed r-cran-later
Bug #915339 [r-cran-later] r-cran-later: Mutex creation failed with glibc 2.28
Bug #915321 [r-cran-later] r-cran-later: Mutex creation failed with glibc 2.28
Changed Bug title to 'libc6 needs Conflicts with unfixed r-cran-later' from 
'r-cran-later: Mutex creation failed with glibc 2.28'.
Changed Bug title to 'libc6 needs Conflicts with unfixed r-cran-later' from 
'r-cran-later: Mutex creation failed with glibc 2.28'.

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

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

[Simon McVittie]

On Sun, 02 Dec 2018 at 21:04:55 +0100, Marc Haber wrote:
> The next debhelper change might choose to give / instead of /usr as a
> target directory by default, moving hundreds of megabytes from /usr to /
> over time.

I don't think anyone is proposing that. There's no reason why it would be
preferred over the merged /usr arrangement implemented in both usrmerge
and debhelper --merged-usr, which is the same as is implemented in some
other Linux distributions (e.g. Fedora): /usr is a real directory, and
/bin, /sbin, /lib* are symlinks to the corresponding directories in /usr.

Unifying /usr with / by making /usr a symlink to / is the opposite of
the merged /usr arrangement that is currently implemented. The Debian
hurd-i386 port did try having a /usr -> / symlink a few years ago as a
simplification, but it has all the same transitional issues as merged
/usr, with fewer advantages, which makes it unappealing.

The purpose of merged /usr is to group together all the static files
(/bin, /sbin, /lib* and the current /usr), which are more similar than
they are diferent, into one place that can be a (maybe read-only) mount
point (/usr). If you do the opposite, your root filesystem is still a
mixture of mutable files in /etc and static files in /bin, /sbin, /lib*,
so you haven't gained as much simplification as you would have had with
merged /usr.

(You talk about "default target directories", but there is nothing
so elaborate: debootstrap --merged-usr simply unpacks packages into a
chroot that already contains the symbolic links like /bin -> /usr/bin,
instead of into an empty chroot.)

smcv

Bug#914680: libplplotada3: missing Breaks+Replaces: libplplotada2

[Nicolas Boulenguez]

Package: libplplotada3
Version: 5.13.0+dfsg-10
Followup-For: Bug #914680

The short attachment contains untested suggestions
* for this bug
* for #821278 (Ada project)
* to set build flags (maybe fixing the empty -dbgsym packages)
* for a cosmetic change in debian/watch
>From 809d9fca94489f0845d8c5c053989150fc1b8130 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Sun, 2 Dec 2018 23:39:09 +0100
Subject: [PATCH 1/4] Improve readability of watch file thanks to version 4 of
 uscan format.

---
 debian/watch | 10 +++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/debian/watch b/debian/watch
index 0b81469a..a6be85a3 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,3 +1,7 @@
-version=3
-opts="uversionmangle=s/-/~/,dversionmangle=s/\+dfsg$//,repacksuffix=+dfsg" \
-  http://sf.net/plplot/plplot-(.*)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
+version=4
+
+opts="\
+  uversionmangle=s/-/~/,\
+  dversionmangle=s/\+dfsg$//,\
+  repacksuffix=+dfsg" \
+http://sf.net/@PACKAGE@/@PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@
-- 
2.19.2

>From 961efce2cecfb5b3acae4086d2bd842f602b1977 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Sun, 2 Dec 2018 23:39:43 +0100
Subject: [PATCH 2/4] Complete the link step of the Ada project.  Closes:
 #821278.

Copy bindings/ada/CMakeLists.txt, which only passes -lplplot to
pkg-config.
---
 debian/plplotada.gpr.in | 6 +-
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/debian/plplotada.gpr.in b/debian/plplotada.gpr.in
index 9d0bae03..e3877141 100644
--- a/debian/plplotada.gpr.in
+++ b/debian/plplotada.gpr.in
@@ -5,11 +5,7 @@ library project Plplotada is
for Library_Ali_Dir use  "/usr/lib/@DEB_HOST_MULTIARCH@/adalib/plplotada";
for Library_Dir use  "/usr/lib/@DEB_HOST_MULTIARCH@");
for Externally_Built use True;
-TODO:
-   --  If options must be added to the command line after
-   --  -L$(Library_Dir) -l$(Library_Name) when linking an executable:
package Linker is
- for Linker_Options use ("-lplplot", "-lor", "-lsomething", "-lsimilar");
+ for Linker_Options use ("-lplplot");
end Linker;
-   --  Else remove all from TODO: to this line.
 end Plplotada;
-- 
2.19.2

>From 28451d48642cefeac83f5704f4430435696d8e71 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Sun, 2 Dec 2018 23:41:17 +0100
Subject: [PATCH 3/4] Delegate selection of default build flags to
 dpkg-buildflags.

Also, enable hardening flags. This setting can cause problems,
dpkg-buildflags(1) describes howto refine it.
---
 debian/rules | 18 --
 1 file changed, 12 insertions(+), 6 deletions(-)

diff --git a/debian/rules b/debian/rules
index 6580e849..b9e2274c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,15 +6,21 @@
 # Paths for Octave
 OCTDIR = $(shell octave-config --print LOCALAPIOCTFILEDIR)
 
-# Note cmake ignores CPPFLAGS so add them to CFLAGS and CXXFLAGS as a
-# work around
-CPPFLAGS += $(shell mkoctfile -p INCFLAGS)
-CFLAGS += $(CPPFLAGS) -fvisibility=hidden
+DEB_BUILD_MAINT_OPTIONS   := hardening=+all
+DPKG_EXPORT_BUILDFLAGS:= 1
+DEB_CFLAGS_MAINT_APPEND   := -fvisibility=hidden
+DEB_FFLAGS_MAINT_APPEND   := -fvisibility=hidden
 # Don't add -fvisibility=hidden to CXXFLAGS for now as this breaks the
 # octave bindings.
+DEB_CPPFLAGS_MAINT_APPEND := $(shell mkoctfile -p INCFLAGS)
+DEB_LDFLAGS_MAINT_APPEND  := -Wl,--as-needed
+include /usr/share/dpkg/default.mk
+
+# Note cmake ignores CPPFLAGS so add them to CFLAGS and CXXFLAGS as a
+# work around, see #653916.
+CFLAGS   += $(CPPFLAGS)
 CXXFLAGS += $(CPPFLAGS)
-FFLAGS += -fvisibility=hidden
-LDFLAGS += -Wl,--as-needed
+
 HOME=$(shell mktemp -d)
 
 export verbose_test = on
-- 
2.19.2

>From 24225167500a55815cf87b56db53860221637b46 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Sun, 2 Dec 2018 23:42:53 +0100
Subject: [PATCH 4/4] Set the shared object version of the Ada library. Closes:
 #914680.

The policy requires that the shared object version of the Ada library
matches the name of the binary package installing it, preventing such
bugs.
---
 debian/rules | 8 
 1 file changed, 8 insertions(+)

diff --git a/debian/rules b/debian/rules
index b9e2274c..c2eb8053 100755
--- a/debian/rules
+++ b/debian/rules
@@ -34,6 +34,14 @@ CONFIGURE_OPTIONS = \
 	-DBUILD_DOC=ON \
 	-DCMAKE_INSTALL_LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH) 
 
+# The soversion used to build and install the Ada shared library must
+# match the end of the library package name.
+ada_lib_pkg_vsn := $(shell sed -n \
+  '/^Package: libplplotada\([0-9.]\+\)$$/{s//\1/;p;q}' debian/control)
+ada_soname := libplplotada.so.$(ada_soversion)
+CONFIGURE_OPTIONS += \
+  '-DCMAKE_SHARED_LIBRARY_SONAME_Ada_FLAG=-Wl,-soname -Wl,$(ada_soname)'
+
 ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS)))
   CONFIGURE_OPTIONS += -DBUILD_TEST=ON
 endif
-- 
2.19.2

Processed: affects 915321

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 915321 src:r-cran-plumber src:rgl src:r-cran-miniui 
> src:r-cran-treescape src:r-cran-threejs src:r-cran-promises 
> src:r-cran-rglwidget src:r-cran-rlumshiny src:r-cran-shinybs
Bug #915321 [libc6] Mutex creation failed
Bug #915339 [libc6] r-cran-treespace FTBFS: terminate called after throwing an 
instance of 'std::runtime_error'
Added indication that 915321 affects src:r-cran-plumber, src:rgl, 
src:r-cran-miniui, src:r-cran-treescape, src:r-cran-threejs, 
src:r-cran-promises, src:r-cran-rglwidget, src:r-cran-rlumshiny, and 
src:r-cran-shinybs
Added indication that 915339 affects src:r-cran-plumber, src:rgl, 
src:r-cran-miniui, src:r-cran-treescape, src:r-cran-threejs, 
src:r-cran-promises, src:r-cran-rglwidget, src:r-cran-rlumshiny, and 
src:r-cran-shinybs
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 915339 libc6
Bug #915339 [src:r-cran-treespace] r-cran-treespace FTBFS: terminate called 
after throwing an instance of 'std::runtime_error'
Bug reassigned from package 'src:r-cran-treespace' to 'libc6'.
No longer marked as found in versions r-cran-treespace/1.1.3+dfsg-1.
Ignoring request to alter fixed versions of bug #915339 to the same values 
previously set
> forcemerge 915321 915339
Bug #915321 [libc6] Mutex creation failed
Bug #915339 [libc6] r-cran-treespace FTBFS: terminate called after throwing an 
instance of 'std::runtime_error'
Marked as found in versions glibc/2.28-1.
Bug #915321 [libc6] Mutex creation failed
Added tag(s) ftbfs.
Merged 915321 915339
> affects 915321 src:r-cran-treespace
Bug #915321 [libc6] Mutex creation failed
Bug #915339 [libc6] r-cran-treespace FTBFS: terminate called after throwing an 
instance of 'std::runtime_error'
Added indication that 915321 affects src:r-cran-treespace
Added indication that 915339 affects src:r-cran-treespace
> thanks
Stopping processing here.

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

Bug#900160: closed by Didier Raboud (Bug#900160: fixed in ruby-eventmachine 1.0.7-4.1)

[gregor herrmann]

On Sun, 02 Dec 2018 23:18:38 +0100, Sebastian Andrzej Siewior wrote:

> On 2018-12-02 13:06:04 [+], Debian Bug Tracking System wrote:
> > #900160: ruby-eventmachine: FTBFS against openssl 1.1.1
> >  ruby-eventmachine (1.0.7-4.1) unstable; urgency=medium
> >  .
> >* Non-maintainer upload.
> >* Build-Depend against libssl1.0-dev; aka OpenSSL << 1.1
> >  (Closes: #900160)
> 
> Please revert that one. We don't want more dependencies on
> libssl1.0-dev. We want it actually out of testing and are down to one
> package.
> I wouldn't care much but since ruby-eventmachine is a key package it
> might migrate to testing…

Raising the severity of the cloned #915287 which tracks this problem
should prevent the migration.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Bob Dylan: The Ballad Of Frankie Lee And Judas Priest


signature.asc
Description: Digital Signature

Bug#891753: marked as done (python-django FTBFS: ERROR: test_load_empty_dir (migrations.test_loader.LoaderTests))

[Debian Bug Tracking System]

Your message dated Sun, 02 Dec 2018 22:37:02 +
with message-id 
and subject line Bug#891753: fixed in python-django 1:1.11.16-4
has caused the Debian Bug report #891753,
regarding python-django FTBFS: ERROR: test_load_empty_dir 
(migrations.test_loader.LoaderTests)
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.)


-- 
891753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 1:1.11.10-1
Severity: serious
Control: found -1 2:2.0.2-1

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

...
==
ERROR: test_load_empty_dir (migrations.test_loader.LoaderTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.6/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.6/unittest/case.py", line 605, in run
testMethod()
  File "/build/1st/python-django-1.11.10/tests/migrations/test_loader.py", line 
178, in test_load_empty_dir
loader = MigrationLoader(connection)
  File "/build/1st/python-django-1.11.10/django/db/migrations/loader.py", line 
52, in __init__
self.build_graph()
  File "/build/1st/python-django-1.11.10/django/db/migrations/loader.py", line 
203, in build_graph
self.load_disk()
  File "/build/1st/python-django-1.11.10/django/db/migrations/loader.py", line 
104, in load_disk
directory = os.path.dirname(module.__file__)
  File "/usr/lib/python3.6/posixpath.py", line 156, in dirname
p = os.fspath(p)
TypeError: expected str, bytes or os.PathLike object, not NoneType

--
Ran 11584 tests in 171.304s
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 1:1.11.16-4

We believe that the bug you reported is fixed in the latest version of
python-django, 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 891...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django 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: Sun, 02 Dec 2018 23:13:07 +0100
Source: python-django
Binary: python-django python-django-common python-django-doc python3-django
Built-For-Profiles: nocheck
Architecture: source all
Version: 1:1.11.16-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Description:
 python-django - High-level Python web development framework (Python 2 version)
 python-django-common - High-level Python web development framework (common)
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework (Python 3 version)
Closes: 891753
Changes:
 python-django (1:1.11.16-4) unstable; urgency=medium
 .
   * Cherry-pick two patches from upstream to fix test failures under Python
 3.7. Thanks to Gaudenz Steinlin for the in-depth investigation.
 (Closes: #891753)
   * Add libsqlite3-mod-spatialite to Build-Depends to ensure we test our patch
 for Spatialite 4.2 introduced as part of the fix for #910240.
Checksums-Sha1:
 c3f6789348f236b5b8f49d4f0f0ff3ac8e659d82 3198 python-django_1.11.16-4.dsc
 003ac7e2ceb2e31fe8fe9b7a8f39d5e3ced54ad2 26584 
python-django_1.11.16-4.debian.tar.xz
 4a57b3e44505654f0958694c34d28089360c5460 1536448 
python-django-common_1.11.16-4_all.deb
 8f93e3b28b80ab116b673bd336a305347c8e756e 2632904 
python-django-doc_1.11.16-4_all.deb
 95d8eb247e8ae4d9dc0b26be79a2c7e52ae71906 915428 python-django_1.11.16-4_all.deb
 a33c3e1c1bf061b90fe9f0ac9d6c59ef31bf2edc 8408 
python-django_1.11.16-4_amd64.buildinfo
 a2984c13e9af73d5519acf463967f1ea90521dfa 915184 
python3-django_1.11.16-4_all.deb
Checksums-Sha256:
 9e339009933d0a046680de0fafeedbcb5838c8d44a9174b1bcab8a5aba331f53 3198 
python-django_1.11.16-4.dsc
 607cc2b4bf8f276f17eef53e9b3fa506ea1cc943819176e48ae95a5eca2ea3b8 26584 
python-django_1.11.16-4.debian.tar.xz
 

Bug#915361: udev refuses to start with sysvinit because it misdetects a container

[Gianluigi Tiesi]

Package: udev
Severity: grave

After upgrading kernel from 4.18.0-2 to 4.18.0-3 udev refuses to start if using 
sysvinit scripts

if [ -w /sys ]; then
  log_warning_msg "udev does not support containers, not started"
  exit 0
fi

/sys is mounted rw and it misdetects a container


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

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

Versions of packages udev depends on:
ii  adduser  3.118
ii  libacl1  2.2.52-3+b1
ii  libblkid12.32.1-0.2
ii  libc62.28-1
pn  libkmod2 
ii  libselinux1  2.8-1+b1
ii  libudev1 239-14
ii  lsb-base 10.2018112800
ii  util-linux   2.32.1-0.2

udev recommends no packages.

udev suggests no packages.

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

[Marco d'Itri]

On Dec 02, Wouter Verhelst  wrote:

> One thing that has not been answered yet in this discussion (and if the
> TC is to make a decision about it, I think it should be) is "why are we
> doing this". That is, what is the problem that usrmerge is meant to
> solve, and how does it attempt to solve it? As far as I know, the reason
> usrmerge exists is so that no files will be installed in /bin anymore;
> but that seems like an XY problem.
https://lists.debian.org/20181121140542.ga31...@espresso.pseudorandom.co.uk

> Also, I would like to ask why the traditional solution in Debian -- make
> a policy change that says no package can ship anything in /bin except
> for a compatibility symlink, and make that rule RC at some point in the
> future -- is not being considered. That seems like a solution that would
> cause far less pain than what we're going through right now.
This is not a solution. For a start it would take many years.
Even ignoring that, it would not bring any improvement over the current 
plan: even if your idea were executed perfectly and quickly then the 
conversion program would still be in the same exact situation as it is 
now: either everything in /bin/, /sbin and /lib (and its own 
subdirectories) was created by the packaging system, and then we already 
know that it can be converted automatically, or it was not, and then we 
know that there are a few cases when the local administrator has to 
decide what to do about things that were installed by himself in the 
past in the wrong place.
So this would make the transition unacceptably slow while providing no 
benefit at all, but it would also cost a huge amount of work to change 
many packages.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Processed: Bug #891753 in python-django marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #891753 [src:python-django] python-django FTBFS: ERROR: test_load_empty_dir 
(migrations.test_loader.LoaderTests)
Added tag(s) pending.

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

Bug#891753: Bug #891753 in python-django marked as pending

[Chris Lamb]

Control: tag -1 pending

Hello,

Bug #891753 in python-django 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/python-django/commit/e1dfcdae55d9033604e26d25d5f310a918f0c6e9


Cherry-pick two patches from upstream to fix test failures under Python 3.7. 
Thanks to Gaudenz Steinlin for the in-depth investigation. (Closes: #891753)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/891753

Processed: Re: Bug#915307: magic-wormhole FTBFS with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> fixed 915307 0.11.2-1
Bug #915307 [src:magic-wormhole] magic-wormhole FTBFS with Python 3.7
The source 'magic-wormhole' and version '0.11.2-1' do not appear to match any 
binary packages
Marked as fixed in versions magic-wormhole/0.11.2-1.

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

Bug#915307: magic-wormhole FTBFS with Python 3.7

[anarcat]

Control: fixed 915307 0.11.2-1

I believe the latest upstream release fixes that, or at least it
compiles here in a sid schroot with py 3.7.

I meant to fix this in the changelog but forgot about it before doing
the upload... :/

Thanks for the heads up though!


signature.asc
Description: PGP signature

Bug#900160: closed by Didier Raboud (Bug#900160: fixed in ruby-eventmachine 1.0.7-4.1)

[Sebastian Andrzej Siewior]

On 2018-12-02 13:06:04 [+], Debian Bug Tracking System wrote:
> #900160: ruby-eventmachine: FTBFS against openssl 1.1.1
>  ruby-eventmachine (1.0.7-4.1) unstable; urgency=medium
>  .
>* Non-maintainer upload.
>* Build-Depend against libssl1.0-dev; aka OpenSSL << 1.1
>  (Closes: #900160)

Please revert that one. We don't want more dependencies on
libssl1.0-dev. We want it actually out of testing and are down to one
package.
I wouldn't care much but since ruby-eventmachine is a key package it
might migrate to testing…

Sebastian

Processed: severity of 915352 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 915352 important
Bug #915352 [packagekit] packagekit: Uses vendor-specific patch series file 
(ubuntu.series)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: severity of 915350 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 915350 important
Bug #915350 [hexchat] hexchat: Uses vendor-specific patch series file 
(ubuntu.series)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: affects 915345

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 915345 src:cmus
Bug #915345 [src:roaraudio] roaraudio FTBFS with glibc 2.28
Added indication that 915345 affects src:cmus
> thanks
Stopping processing here.

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

Bug#915337: rr: baseline violation on i386

[Stephen Kitt]

Hi Adrian,

On Sun, 02 Dec 2018 23:01:23 +0200, Adrian Bunk  wrote:
> MMX and SSE are not part of the i386 baseline.

From the package description:

 rr is incompatible with ptrace hardening, and currently only supports
 Intel CPUs with Nehalem or later microarchitectures.

All supported CPUs support MMX and SSE. The package is useful on i386, but I
can drop it if you think I shouldn’t ship it there.

Regards,

Stephen


pgpcp0kBQCLlb.pgp
Description: OpenPGP digital signature

Bug#915341: marked as done (x2gothinclient-common: File conflict)

[Debian Bug Tracking System]

Your message dated Sun, 2 Dec 2018 23:01:13 +0100
with message-id <661ca7a2-c08f-919a-9bb8-629e1c340...@web.de>
and subject line Re: Bug#915341: Acknowledgement (x2gothinclient-common: File 
conflict)
has caused the Debian Bug report #915341,
regarding x2gothinclient-common: File conflict
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.)


-- 
915341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: x2gothinclient-common
Version: 1.5.0.0-0x2go1+git20181202.691+9
Severity: grave
Justification: renders package unusable

hille@haka:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  pinentry-x2go x2gothinclient-common x2gothinclient-displaymanager
The following packages will be upgraded:
  x2gothinclient
1 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 437 kB of archives.
After this operation, 597 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.de.debian.org/debian stretch/main amd64 pinentry-x2go amd64
0.7.5.9-2 [389 kB]
Get:2 http://packages.x2go.org/debian stretch/main amd64 x2gothinclient all
1.5.0.0-0x2go1+git20181202.691+9.main.1 [12,3 kB]
Get:3 http://packages.x2go.org/debian stretch/main amd64 x2gothinclient-common
all 1.5.0.0-0x2go1+git20181202.691+9.main.1 [14,0 kB]
Get:4 http://packages.x2go.org/debian stretch/main amd64 x2gothinclient-
displaymanager all 1.5.0.0-0x2go1+git20181202.691+9.main.1 [22,2 kB]
Fetched 437 kB in 0s (557 kB/s)
Reading changelogs... Done
apt-listchanges: Do you want to continue? [Y/n] y
apt-listchanges: Mailing hille: apt-listchanges: changelogs for haka
Preconfiguring packages ...
Selecting previously unselected package pinentry-x2go.
(Reading database ... 320804 files and directories currently installed.)
Preparing to unpack .../pinentry-x2go_0.7.5.9-2_amd64.deb ...
Unpacking pinentry-x2go (0.7.5.9-2) ...
Preparing to unpack
.../x2gothinclient_1.5.0.0-0x2go1+git20181202.691+9.main.1_all.deb ...
Unpacking x2gothinclient (1.5.0.0-0x2go1+git20181202.691+9.main.1) over
(1.1.0.2-0x2go1+git20180205.485+9.main.1) ...
dpkg: warning: unable to delete old directory '/etc/x2go/freerdp': Directory
not empty
Selecting previously unselected package x2gothinclient-common.
Preparing to unpack .../x2gothinclient-
common_1.5.0.0-0x2go1+git20181202.691+9.main.1_all.deb ...
Unpacking x2gothinclient-common (1.5.0.0-0x2go1+git20181202.691+9.main.1) ...
dpkg: error processing archive /var/cache/apt/archives/x2gothinclient-
common_1.5.0.0-0x2go1+git20181202.691+9.main.1_all.deb (--unpack):
 trying to overwrite '/etc/x2go/x2gothinclient_init', which is also in package
x2gothinclient 1.5.0.0-0x2go1+git20181202.691+9.main.1
Selecting previously unselected package x2gothinclient-displaymanager.
Preparing to unpack .../x2gothinclient-
displaymanager_1.5.0.0-0x2go1+git20181202.691+9.main.1_all.deb ...
Unpacking x2gothinclient-displaymanager
(1.5.0.0-0x2go1+git20181202.691+9.main.1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/x2gothinclient-
common_1.5.0.0-0x2go1+git20181202.691+9.main.1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
hille@haka:~$ sudo apt upgrade



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

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

Versions of packages x2gothinclient-common depends on:
ii  adduser 3.115
ii  x2goclient  4.1.2.1-0x2go1+git20180626.1801+9.main.1

x2gothinclient-common recommends no packages.

x2gothinclient-common suggests no packages.
--- End Message ---
--- Begin Message ---

Am 02.12.2018 um 22:36 teilte Debian Bug Tracking System mit:

Thank you for filing a new Bug report with Debian.



--
#206401 http://counter.li.org--- End Message ---

Bug#915353: vdr-plugin-skinenigmang FTBFS due to using freetype-config that was removed in Debian

[Adrian Bunk]

Source: vdr-plugin-skinenigmang
Version: 0.1.2+git20180128-2
Severity: serious
Tags: ftbfs patch

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-skinenigmang.html

...
In file included from config.h:20,
 from skinenigmang.c:9:
font.h:16:10: error: #include expects "FILENAME" or 
 #include FT_FREETYPE_H
  ^


Fix attached.
Description: freetype-config was removed in Debian, switch to pkg-config
Author: Adrian Bunk 

--- vdr-plugin-skinenigmang-0.1.2+git20180128.orig/Makefile
+++ vdr-plugin-skinenigmang-0.1.2+git20180128/Makefile
@@ -138,9 +138,9 @@ INCLUDES += $(shell pkg-config --cflags
 endif
 endif
 
-ifneq ($(shell which freetype-config),)
-   INCLUDES += $(shell freetype-config --cflags)
-   LIBS += $(shell freetype-config --libs)
+ifneq ($(shell which pkg-config),)
+   INCLUDES += $(shell pkg-config --cflags freetype2)
+   LIBS += $(shell pkg-config --libs freetype2)
 else
INCLUDES += -I/usr/include/freetype -I/usr/local/include/freetype
LIBS += -lfreetype

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

[Wouter Verhelst]

On Wed, Nov 28, 2018 at 01:49:45PM +, Ian Jackson wrote:
> Control: reassign -1 tech-ctte
> 
> Dear Technical Committee.  I don't know if you are all aware of the
> discussion surrounding this, so I will recap:
> 
> Recently debootstrap was changed to do merged-/usr by default, so that
> /bin -> /usr/bin etc.
> 
> It was discovered that when this change took effect on the Debian
> buildds, the buildds started to build packages which do not work on
> non-merged-/usr systems.
> 
> This is a special case of a general problem: buster systems with
> merged-/usr sometimes build packages which are broken on
> non-merged-/usr systems.
> 
> Some people have suggested that this should be fixed by making
> merged-/usr mandatory for buster.  However, there is no transition
> plan for this as yet and I don't think Debian is ready to commit to do
> that.
> 
> So I believe that this change should be immediately reverted in sid
> and buster, so that we do not prejudge the situation by increasing the
> number of buster installs in the field which generate packages which
> are broken on non-merged-/usr systemss.

One thing that has not been answered yet in this discussion (and if the
TC is to make a decision about it, I think it should be) is "why are we
doing this". That is, what is the problem that usrmerge is meant to
solve, and how does it attempt to solve it? As far as I know, the reason
usrmerge exists is so that no files will be installed in /bin anymore;
but that seems like an XY problem.

Also, I would like to ask why the traditional solution in Debian -- make
a policy change that says no package can ship anything in /bin except
for a compatibility symlink, and make that rule RC at some point in the
future -- is not being considered. That seems like a solution that would
cause far less pain than what we're going through right now.

-- 
To the thief who stole my anti-depressants: I hope you're happy

  -- seen somewhere on the Internet on a photo of a billboard

Bug#915350: hexchat: Uses vendor-specific patch series file (ubuntu.series)

[Chris Lamb]

Package: hexchat
Version: 2.14.2-2+b2
Severity: serious

Hi,

Hexchat appears to use a vendor-specific patch series file (debian/
patches/ubuntu.series)

This is feature of dpkg that can be used to apply a different series
of quilt patches when the source package is unpacked on different
systems. However, since Debian source packages are usually treated as
a pure transport format this can cause confusion and frustration.

Please migrate away from such series files and consider alternatives
such differing source packages or modify the build process to behave
conditionally or to conditionally patch files explicitly.

Refer to https://bugs.debian.org/904302 and https://lists.debian.org/
debian-devel-announce/2018/11/msg4.html for more details.


Regards,

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

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Wouter Verhelst]

On Fri, Nov 30, 2018 at 06:01:26PM +0200, Jan Groenewald wrote:
> Hi
> 
> On Fri, 30 Nov 2018 at 16:43, Holger Levsen  wrote:
> 
> On Fri, Nov 30, 2018 at 07:39:20PM +0530, Pirate Praveen wrote:
> > >Backports are *always* from testing because a backport is
> > >supposed to be replaced by the regular stable version of
> > >the subsequent release.
> > That is indeed the current definition.
> 
> Me too is very happy with it.
> 
> > Another option could be to have personal package archive for gitlab.
> 
> That. And if you don't want to wait until they arrive in Debian proper,
> I'd suggest you'd host such an archive yourself.
> 
> 
> There is  https://packages.gitlab.com/gitlab/gitlab-ce
> 
> (deb https://packages.gitlab.com/gitlab/gitlab-ce/debian/ stretch main)

That "omnibus package" which contains everything and the kitchen sink is
awful.

-- 
To the thief who stole my anti-depressants: I hope you're happy

  -- seen somewhere on the Internet on a photo of a billboard

Processed: Bug #915143 in blender marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #915143 [blender] blender: Upgrading to 2.79.b+dfsg0-4+b2 gives console 
errors and empty panels
Added tag(s) pending.

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

Bug#915143: Bug #915143 in blender marked as pending

[Matteo F. Vescovi]

Control: tag -1 pending

Hello,

Bug #915143 in blender 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/multimedia-team/blender/commit/5db4afd64d9849001bb5d92ce3c45205aea2de4d


debian/patches/: patchset updated

- 0010-fix_PyRNA_with_Python3.7.patch added

Closes: #915143



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/915143

Bug#915352: packagekit: Uses vendor-specific patch series file (ubuntu.series)

[Chris Lamb]

Package: packagekit
Version: 1.1.11-1
Severity: serious

Hi,

packagekit appears to use a vendor-specific patch series file (debian/
patches/ubuntu.series)

This is feature of dpkg that can be used to apply a different series
of quilt patches when the source package is unpacked on different
systems. However, since Debian source packages are usually treated as
a pure transport format this can cause confusion and frustration.

Please migrate away from such series files and consider alternatives
such differing source packages or modify the build process to behave
conditionally or to conditionally patch files explicitly.

Refer to https://bugs.debian.org/904302 and https://lists.debian.org/
debian-devel-announce/2018/11/msg4.html for more details.


Regards,

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

Bug#915349: giada FTBFS with juce 5.4.1

[Adrian Bunk]

Source: giada
Version: 0.15.2+ds1-1
Severity: serious
Tags: ftbfs

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

...
In file included from 
src/deps/juce/modules/juce_audio_processors/juce_audio_processors.cpp:164:
src/deps/juce/modules/juce_audio_processors/format_types/juce_VSTPluginFormat.cpp:49:10:
 fatal error: pluginterfaces/vst2.x/aeffect.h: No such file or directory
 #include 
  ^
compilation terminated.
make[2]: *** [Makefile:5250: 
src/deps/juce/modules/juce_audio_processors/giada-juce_audio_processors.o] 
Error 1

Bug#915346: mosquitto-auth-plugin FTBFS with mosquitto 1.5.4-1

[Adrian Bunk]

Source: mosquitto-auth-plugin
Version: 0.1.2-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mosquitto-auth-plugin.html

...
../auth-plug.c:102:5: error: conflicting types for 'mosquitto_auth_plugin_init'
 int mosquitto_auth_plugin_init(void **userdata, struct mosquitto_auth_opt 
*auth_opts, int auth_opt_count)
 ^~
In file included from ../auth-plug.c:35:
/usr/include/mosquitto_plugin.h:118:5: note: previous declaration of 
'mosquitto_auth_plugin_init' was here
 int mosquitto_auth_plugin_init(void **user_data, struct mosquitto_opt *opts, 
int opt_count);
 ^~
...

Bug#915345: roaraudio FTBFS with glibc 2.28

[Adrian Bunk]

Source: roaraudio
Version: 1.0~beta11-11
Severity: serious
Tags: ftbfs

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

...
x86_64-linux-gnu-gcc -g -O2 -ffile-prefix-map=/build/1st/roaraudio-1.0~beta11=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-ffile-prefix-map=/build/1st/roaraudio-1.0~beta11=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 
-ffile-prefix-map=/build/1st/roaraudio-1.0~beta11=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -Wall -O2  -I../include 
-I../include/libroar   -fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o libroar.o 
libroar.c
In file included from ../include/libroar/libroar.h:173,
 from libroar.c:40:
../include/libroar/vio_stdio.h:50:46: error: unknown type name '_IO_off64_t'; 
did you mean '__off64_t'?
 int roar_vio_to_stdio_lseek (void *__cookie, _IO_off64_t *__pos, int __w);
  ^~~
  __off64_t
make[2]: *** [: libroar.o] Error 1

Bug#915344: openfoam FTBFS with glibc 2.28

[Adrian Bunk]

Source: openfoam
Version: 4.1+dfsg1-2.2
Severity: serious
Tags: ftbfs

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

...
fileStat.C: In member function 'bool Foam::fileStat::sameDevice(const 
Foam::fileStat&) const':
fileStat.C:78:13: error: 'major' was not declared in this scope
 major(status_.st_dev) == major(stat2.status().st_dev)
 ^
fileStat.C:79:13: error: 'minor' was not declared in this scope
  && minor(status_.st_dev) == minor(stat2.status().st_dev)
 ^
fileStat.C:79:13: note: suggested alternative: 'mknod'
  && minor(status_.st_dev) == minor(stat2.status().st_dev)
 ^
 mknod
fileStat.C: In function 'Foam::Istream& Foam::operator>>(Foam::Istream&, 
Foam::fileStat&)':
fileStat.C:104:20: error: 'makedev' was not declared in this scope
 dev_t st_dev = makedev(stat[1], stat[2]);
^~~
fileStat.C: In function 'Foam::Ostream& Foam::operator<<(Foam::Ostream&, const 
Foam::fileStat&)':
fileStat.C:132:21: error: 'major' was not declared in this scope
 stat[1] = label(major(fStat.status_.st_dev));
 ^
fileStat.C:133:21: error: 'minor' was not declared in this scope
 stat[2] = label(minor(fStat.status_.st_dev));
 ^
fileStat.C:133:21: note: suggested alternative: 'mknod'
 stat[2] = label(minor(fStat.status_.st_dev));
 ^
 mknod
make[2]: *** [/build/1st/openfoam-4.1+dfsg1/wmake/rules/General/transform:8: 
/build/1st/openfoam-4.1+dfsg1/platforms/linux64Gcc51/src/OSspecific/POSIX/fileStat.o]
 Error 1

Bug#915341: x2gothinclient-common: File conflict

[Hilmar Preuße]

Package: x2gothinclient-common
Version: 1.5.0.0-0x2go1+git20181202.691+9
Severity: grave
Justification: renders package unusable

hille@haka:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  pinentry-x2go x2gothinclient-common x2gothinclient-displaymanager
The following packages will be upgraded:
  x2gothinclient
1 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 437 kB of archives.
After this operation, 597 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.de.debian.org/debian stretch/main amd64 pinentry-x2go amd64
0.7.5.9-2 [389 kB]
Get:2 http://packages.x2go.org/debian stretch/main amd64 x2gothinclient all
1.5.0.0-0x2go1+git20181202.691+9.main.1 [12,3 kB]
Get:3 http://packages.x2go.org/debian stretch/main amd64 x2gothinclient-common
all 1.5.0.0-0x2go1+git20181202.691+9.main.1 [14,0 kB]
Get:4 http://packages.x2go.org/debian stretch/main amd64 x2gothinclient-
displaymanager all 1.5.0.0-0x2go1+git20181202.691+9.main.1 [22,2 kB]
Fetched 437 kB in 0s (557 kB/s)
Reading changelogs... Done
apt-listchanges: Do you want to continue? [Y/n] y
apt-listchanges: Mailing hille: apt-listchanges: changelogs for haka
Preconfiguring packages ...
Selecting previously unselected package pinentry-x2go.
(Reading database ... 320804 files and directories currently installed.)
Preparing to unpack .../pinentry-x2go_0.7.5.9-2_amd64.deb ...
Unpacking pinentry-x2go (0.7.5.9-2) ...
Preparing to unpack
.../x2gothinclient_1.5.0.0-0x2go1+git20181202.691+9.main.1_all.deb ...
Unpacking x2gothinclient (1.5.0.0-0x2go1+git20181202.691+9.main.1) over
(1.1.0.2-0x2go1+git20180205.485+9.main.1) ...
dpkg: warning: unable to delete old directory '/etc/x2go/freerdp': Directory
not empty
Selecting previously unselected package x2gothinclient-common.
Preparing to unpack .../x2gothinclient-
common_1.5.0.0-0x2go1+git20181202.691+9.main.1_all.deb ...
Unpacking x2gothinclient-common (1.5.0.0-0x2go1+git20181202.691+9.main.1) ...
dpkg: error processing archive /var/cache/apt/archives/x2gothinclient-
common_1.5.0.0-0x2go1+git20181202.691+9.main.1_all.deb (--unpack):
 trying to overwrite '/etc/x2go/x2gothinclient_init', which is also in package
x2gothinclient 1.5.0.0-0x2go1+git20181202.691+9.main.1
Selecting previously unselected package x2gothinclient-displaymanager.
Preparing to unpack .../x2gothinclient-
displaymanager_1.5.0.0-0x2go1+git20181202.691+9.main.1_all.deb ...
Unpacking x2gothinclient-displaymanager
(1.5.0.0-0x2go1+git20181202.691+9.main.1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/x2gothinclient-
common_1.5.0.0-0x2go1+git20181202.691+9.main.1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
hille@haka:~$ sudo apt upgrade



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

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

Versions of packages x2gothinclient-common depends on:
ii  adduser 3.115
ii  x2goclient  4.1.2.1-0x2go1+git20180626.1801+9.main.1

x2gothinclient-common recommends no packages.

x2gothinclient-common suggests no packages.

Bug#915342: libbpp-seq FTBFS: symbol changes

[Adrian Bunk]

Source: libbpp-seq
Version: 2.4.1-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes libbpp-seq FTBFS:

https://tests.reproducible-builds.org/debian/history/libbpp-seq.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbpp-seq.html

...
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/build/1st/libbpp-seq-2.4.1'
echo "Architecture amd64 is the only one where a symbols file is provided"
Architecture amd64 is the only one where a symbols file is provided
dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libbpp-seq12/DEBIAN/symbols doesn't match 
completely debian/libbpp-seq12.symbols
--- debian/libbpp-seq12.symbols (libbpp-seq12_2.4.1-1_amd64)
+++ dpkg-gensymbols_nPCUn   2020-01-04 12:03:13.926707545 -1200
@@ -1813,7 +1813,8 @@
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE11equal_rangeERS7_@Base
 2.4.1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE12_M_erase_auxESt23_Rb_tree_const_iteratorISB_E@Base
 2.4.1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSJ_PSt13_Rb_tree_nodeISB_E@Base
 2.4.1
- 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE16_M_insert_uniqueIS6_IS5_SA_EEES6_ISt17_Rb_tree_iteratorISB_EbEOT_@Base
 2.4.1
+#MISSING: 2.4.1-1# 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE16_M_insert_uniqueIS6_IS5_SA_EEES6_ISt17_Rb_tree_iteratorISB_EbEOT_@Base
 2.4.1
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE17_M_emplace_uniqueIJS6_IS5_SA_S6_ISt17_Rb_tree_iteratorISB_EbEDpOT_@Base
 2.4.1-1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base
 2.4.1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base
 2.4.1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS7_@Base
 2.4.1
dh_makeshlibs: failing due to earlier errors
make[1]: *** [debian/rules:15: override_dh_makeshlibs] Error 2

Bug#915343: libbpp-core FTBFS: symbol changes

[Adrian Bunk]

Source: libbpp-core
Version: 2.4.1-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes libbpp-core FTBFS:

https://tests.reproducible-builds.org/debian/history/libbpp-core.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbpp-core.html

...
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/build/1st/libbpp-core-2.4.1'
echo "Architecture amd64 is the only one where a symbols file is provided"
Architecture amd64 is the only one where a symbols file is provided
dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libbpp-core4/DEBIAN/symbols doesn't match 
completely debian/libbpp-core4.symbols
--- debian/libbpp-core4.symbols (libbpp-core4_2.4.1-1_amd64)
+++ dpkg-gensymbolsf79BBX   2020-01-04 12:02:29.920104286 -1200
@@ -2266,7 +2266,9 @@
  
_ZNSt8_Rb_treeIjSt4pairIKjS0_IjjEESt10_Select1stIS3_ESt4lessIjESaIS3_EE8_M_eraseEPSt13_Rb_tree_nodeIS3_E@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjS0_IjjEESt10_Select1stIS3_ESt4lessIjESaIS3_EEaSERKS9_@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE12_M_erase_auxESt23_Rb_tree_const_iteratorIS2_E@Base
 2.4.1
- 
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE16_M_insert_uniqueIS0_IjjEEES0_ISt17_Rb_tree_iteratorIS2_EbEOT_@Base
 2.4.1
+ 
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSA_PSt13_Rb_tree_nodeIS2_E@Base
 2.4.1-1
+#MISSING: 2.4.1-1# 
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE16_M_insert_uniqueIS0_IjjEEES0_ISt17_Rb_tree_iteratorIS2_EbEOT_@Base
 2.4.1
+ 
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE17_M_emplace_uniqueIJS0_IjjS0_ISt17_Rb_tree_iteratorIS2_EbEDpOT_@Base
 2.4.1-1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE7_M_copyINS8_11_Alloc_nodeEEEPSt13_Rb_tree_nodeIS2_EPKSC_PSt18_Rb_tree_node_baseRT_@Base
 2.4.1
dh_makeshlibs: failing due to earlier errors
make[1]: *** [debian/rules:15: override_dh_makeshlibs] Error 2

Bug#915339: r-cran-treespace FTBFS: terminate called after throwing an instance of 'std::runtime_error'

[Adrian Bunk]

Source: r-cran-treespace
Version: 1.1.3+dfsg-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes r-cran-treespace FTBFS:

https://tests.reproducible-builds.org/debian/history/r-cran-treespace.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/r-cran-treespace.html

...
installing to 
/build/1st/r-cran-treespace-1.1.3+dfsg/debian/r-cran-treespace/usr/lib/R/site-library/treespace/libs
** R
** data
*** moving datasets to lazyload DB
** inst
** byte-compile and prepare package for lazy loading
terminate called after throwing an instance of 'std::runtime_error'
  what():  Mutex creation failed
Aborted
dh_auto_install: R CMD INSTALL -l 
/build/1st/r-cran-treespace-1.1.3\+dfsg/debian/r-cran-treespace/usr/lib/R/site-library
 --clean . "--built-timestamp='Thu, 07 Jun 2018 11:53:16 +0200'" returned exit 
code 134
make: *** [debian/rules:4: binary] Error 2

Bug#915340: ruby-psych FTBFS: error: incompatible types: Character cannot be converted to ScalarStyle

[Adrian Bunk]

Source: ruby-psych
Version: 3.0.3~pre1-2
Severity: serious
Tags: ftbfs

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

...
javac  -target 1.7 -source 1.7 -Xlint:unchecked  -cp 
"/usr/share/jruby/lib/jruby.jar:/usr/share/maven-repo/org/yaml/snakeyaml/1.x/snakeyaml-1.x.jar"
 -d tmp/java/psych ext/java/PsychEmitter.java ext/java/PsychLibrary.java 
ext/java/PsychParser.java ext/java/PsychToRuby.java ext/java/PsychYamlTree.java
warning: [options] bootstrap class path not set in conjunction with -source 7
ext/java/PsychParser.java:299: error: incompatible types: Character cannot be 
converted to ScalarStyle
IRubyObject style = runtime.newFixnum(translateStyle(se.getStyle()));
^
Note: ext/java/PsychParser.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some messages have been simplified; recompile with -Xdiags:verbose to get 
full output
1 error
1 warning

Bug#911985: marked as done (libvoikko FTBFS with hfst-ospell 0.5.0)

[Debian Bug Tracking System]

Your message dated Sun, 02 Dec 2018 21:19:33 +
with message-id 
and subject line Bug#911985: fixed in libvoikko 4.2-0.1
has caused the Debian Bug report #911985,
regarding libvoikko FTBFS with hfst-ospell 0.5.0
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.)


-- 
911985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvoikko
Version: 4.1.1-1.1
Severity: serious
Tags: ftbfs

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

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

We believe that the bug you reported is fixed in the latest version of
libvoikko, 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 911...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
libvoikko 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: Sun, 25 Nov 2018 21:36:52 +0100
Source: libvoikko
Binary: libvoikko-dev libvoikko1 python-libvoikko python3-libvoikko
Architecture: source
Version: 4.2-0.1
Distribution: sid
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: John Paul Adrian Glaubitz 
Description:
 libvoikko-dev - Development files for libvoikko
 libvoikko1 - Library of free natural language processing tools
 python-libvoikko - transitional dummy package for Python bindings for libvoikko
 python3-libvoikko - Python bindings for libvoikko
Closes: 911985
Changes:
 libvoikko (4.2-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release. (Closes: #911985)
Checksums-Sha1:
 cb18fb76520ce5b0fd7e9a07473f978131031a74 2135 libvoikko_4.2-0.1.dsc
 0ac7eab0ade2b621a63b564db793126f8e2f6464 653769 libvoikko_4.2.orig.tar.gz
 8214e5abf72e67ca5fe3b686bc3b185ec0145344 6400 libvoikko_4.2-0.1.debian.tar.xz
 3d20ff8635ccf7955462934038e9b2275c46267a 7503 libvoikko_4.2-0.1_amd64.buildinfo
Checksums-Sha256:
 0c80b8e730d294e6976590bf28ba576bbf615944db324095e409ebec0ab93d3e 2135 
libvoikko_4.2-0.1.dsc
 f13c59825f36152f388cd96f638e447744199775277f4e6bcd0b9483f0eebeca 653769 
libvoikko_4.2.orig.tar.gz
 ec1ec68be46b577b92a9559dc8b124d6061926045f74e310eeb44422102f 6400 
libvoikko_4.2-0.1.debian.tar.xz
 5beef09ad6bfd82f8a128f85c49d0520c726ecc811c2036092844af0e26e8337 7503 
libvoikko_4.2-0.1_amd64.buildinfo
Files:
 94301b19fb468fbd72007cd7a709b716 2135 libs optional libvoikko_4.2-0.1.dsc
 138e188844d522371e5c3df1fed9e66e 653769 libs optional libvoikko_4.2.orig.tar.gz
 58fdcaf28d9ee8d9dbe80bb4c69588c3 6400 libs optional 
libvoikko_4.2-0.1.debian.tar.xz
 fe2b806030b8d8322400fb058efddacd 7503 libs optional 
libvoikko_4.2-0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAlv7CTEACgkQdCY7N/W1
+RMcOA//WJhZWN3n38WqzohydmpP8glwHKR7ywRTyfl2fu92ZyFs36eB3axOH2zw
U3H43+2QRqWoCvAJYc+9Mbedwut7cd0Vw61LaaPlnBw5meZprthxADuQI0iy+ERF
Cfheq8mGMw6o+Hj6JLF7DHEIBUSSXQcoVYh6H223b7u77ZQMsEHAXgRL8GwtfXx2
y2Lgbi+UxR1svcbmuKulIE5WRwC8PZKJ/mY4oLf3eBCWX67Fi2h+CJ9wzahIrYul
+WrwcvKuC4N0DGsBx4LVvDovAsq8ZufLtzSR1SNHICb2tMpkYmGErykLxMn4YCdK
RcXeXw3RNCH9Z5WmTuLWCVqpCTUPVQs6MlMOHqfdPXLVAeonNNHyRDO1gWsqqhZA
uKl6XJcp5vkhfWRddLpN+1qjDOLI4YnuyCoOWum+yBQvIaHKi3eYl0aUtUv88jFo
t7ZtcqmGAGfCTnUbp1o4Gw0HaVMmpqhrcP2rcXGfUWNanlxoaTHYQhdlL5AW0fyn
BCxi6U4b1tmCXhagpn2/rL3/8Nqus7X1lt5J1K7a8jXiG+HzbWLEXG3QBXDKlCSZ
fED5QM7VJ1sQ1ii1ZpwTrgCO1xXyJ1wC0VdvnamYn60Hi8oeZQVSsUCAgzOqmzKu
pdwm7wDRJZOoUAbhwtWPHrxEbSnvw5aTWgZxE77urfo03CAGy6g=
=mC1K
-END PGP SIGNATURE End Message ---

Bug#890086: ufraw: diff for NMU version 0.22-3.1

[Salvatore Bonaccorso]

Hi!

On Sun, Dec 02, 2018 at 03:40:44PM -0500, Hubert Chathi wrote:
> On Sun, 2 Dec 2018 11:04:25 +0100, Salvatore Bonaccorso  
> said:
> 
> > Dear maintainer,
> 
> > I've prepared an NMU for ufraw (versioned as 0.22-3.1) and uploaded it
> > to DELAYED/5. Please feel free to tell me if I should delay it longer.
> 
> Hi Salvatore,
> 
> Thank you very much for the NMU.  I have no objections to it.

Thanks for your feedback. Any preference from you to keep it in the
delayed queue or speed processing up? (feel free as well to just
reschedule it).

Regards,
Salvatore

Bug#915338: rr FTBFS with glibc 2.28

[Adrian Bunk]

Source: rr
Version: 5.2.0-2
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/mozilla/rr/issues/2237

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/rr.html

...
/build/1st/rr-5.2.0/src/kernel_abi.cc:54:17: error: static assertion failed: 
type ::ucontext_t not correctly defined
   static_assert(Verifier::same_size,
\
 ^~~
/build/1st/rr-5.2.0/src/kernel_abi.h:1813:3: note: in expansion of macro 
'RR_VERIFY_TYPE_ARCH'
   RR_VERIFY_TYPE_ARCH(SupportedArch::x86_64, ::ucontext_t, ucontext_t);
   ^~~

Bug#890086: ufraw: diff for NMU version 0.22-3.1

[Hubert Chathi]

On Sun, 2 Dec 2018 11:04:25 +0100, Salvatore Bonaccorso  
said:

> Dear maintainer,

> I've prepared an NMU for ufraw (versioned as 0.22-3.1) and uploaded it
> to DELAYED/5. Please feel free to tell me if I should delay it longer.

Hi Salvatore,

Thank you very much for the NMU.  I have no objections to it.

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Bug#915337: rr: baseline violation on i386

[Adrian Bunk]

Source: rr
Version: 5.2.0-2
Severity: serious

MMX and SSE are not part of the i386 baseline.

Bug#915336: python-pyramid-chameleon downloads from the internet during the build

[Adrian Bunk]

Source: python-pyramid-chameleon
Version: 0.3-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-pyramid-chameleon.html

...
sphinx-build -b html -d _build/doctrees  -W . _build/html
Running Sphinx v1.7.9
loading pickled environment... not yet created
loading intersphinx inventory from 
http://docs.pylonsproject.org/projects/pyramid/en/latest/objects.inv...

Warning, treated as error:
failed to reach any of the inventories with the following issues:
make[2]: *** [Makefile:30: html] Error 2

Processed: Re: dgit autopkgtest breaks with git 2.20

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Ian Jackson wrote:
> #
> # > FTR, I get this correct output in stretch and buster.
> #
> # Thanks for testing!  I've run into problems with the BTS version
> # tracking with this kind of annotation before (i.e. with using
> # "fixed" to track known-good versions of a package that later
> # regressed) so I'm removing the annotation but am grateful for the
> # test results.
> #
> notfixed 914695 git/1:2.11.0-3+deb9u3
Bug #914695 {Done: Jonathan Nieder } [git] dgit autopkgtest 
breaks with git 2.20
No longer marked as fixed in versions git/1:2.11.0-3+deb9u3.
> notfixed 914695 git/1:2.19.2-1
Bug #914695 {Done: Jonathan Nieder } [git] dgit autopkgtest 
breaks with git 2.20
No longer marked as fixed in versions git/1:2.19.2-1.
>
End of message, stopping processing here.

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

Processed: reassign badly re-assigned ipxe issue

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 906365 src:ipxe
Bug #906365 [src:gcc-8] ipxe: FTBFS in buster/sid (Error: can't resolve 
`__table_entries.2701')
Bug reassigned from package 'src:gcc-8' to 'src:ipxe'.
Ignoring request to alter found versions of bug #906365 to the same values 
previously set
Ignoring request to alter fixed versions of bug #906365 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#915334: icon FTBFS with glibc 2.28

[Adrian Bunk]

Source: icon
Version: 9.4.3-6
Severity: serious
Tags: ftbfs

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

...
gcc -Wall -g -O2 -fno-strict-aliasing -fno-strict-overflow -fPIC -c fpoll.c
fpoll.c: In function 'fpoll':
fpoll.c:66:9: error: 'FILE' {aka 'struct _IO_FILE'} has no member named '__bufp'
if (f->__bufp < f->__get_limit)
 ^~
fpoll.c:66:21: error: 'FILE' {aka 'struct _IO_FILE'} has no member named 
'__get_limit'
if (f->__bufp < f->__get_limit)
 ^~
make[4]: *** [Makefile:15: fpoll.o] Error 1

Bug#907396: kopano-server: Tools all fail with: MAPI error 80040111 (MAPI_E_LOGON_FAILED)

[David Gabriel]

-Original Message-
From: Carsten Schoenert 
To: Mark Dufour , 907...@bugs.debian.org, 
b...@dest-unreachable.net 
Subject: Re: Bug#907396: kopano-server: Tools all fail with: MAPI error 80040111
(MAPI_E_LOGON_FAILED)
Date: Sun, 2 Dec 2018 17:40:26 +0100

> Hello Mark, hello David,
Hi Carsten,

> Hi David,
> any update on this?

> a lot of updates did happen.
> https://qa.debian.org/cgi-bin/vcswatch?package=kopanocore

thanks for the link, didn't know about that!

> > kopano-core and its deps are scheduled for removal in testing in a
> > couple of days, and the package has not been updated ever since 
> > 8.6.5. has kopano been abandoned for debian buster?

> No, this is not planned.

Happy to hear that - I was referring to the statement on
https://tracker.debian.org/pkg/kopanocore (...removal on Dec 8...)
must have mis-interpreted that.

...

> The current changes that happen in the past week are more than the usual
> updates between package versions. It's not that far away from a complete
> re-create of the packaging from scratch due the massive changes that had
> taken place. The current preparations for the next upload are holding a
> drop of the Python2 based packages and will introduce Python3 based
> packages that have required some changes to the source too. This has
> happen in cooperation with upstream.
> Also PHP has changed in unstable to version 7.2 which will require
> changes to the webapp later too. So it's all a bit complex.

> David, if you like to test the current packages I've uploaded a snapshot
> version to
> https://people.debian.org/~tijuca/kopanocore/

> Please note the packages here might get changed or get dropped later. If
> you could do some testing we would like to get some feedback if possible.

I understand - that's a lot of changes, thank you all for your hard work! I'll
gladly test the provided packages and report back. However since I'm traveling
abroad at the moment (and I'll have to revert my kopano install for which I used
the .deb packages provided by download.kopano.io for now) this might take me
about 2 weeks. Whom/were should I report back? This bug is probably not the
right place to continue to talk about packaging issues.

Br and thanks again for the comprehensive update,
David

Bug#915335: checkstyle FTBFS: head() in com.puppycrawl.tools.checkstyle.xpath.AbstractNode cannot implement head() in net.sf.saxon.om.Item

[Adrian Bunk]

Source: checkstyle
Version: 8.14-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes checkstyle FTBFS:

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

...
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/checkstyle-8.14/src/main/java/com/puppycrawl/tools/checkstyle/xpath/AbstractNode.java:[279,23]
 head() in com.puppycrawl.tools.checkstyle.xpath.AbstractNode cannot implement 
head() in net.sf.saxon.om.Item
  return type net.sf.saxon.om.Item is not compatible with 
net.sf.saxon.om.NodeInfo
[ERROR] 
/build/1st/checkstyle-8.14/src/main/java/com/puppycrawl/tools/checkstyle/xpath/AbstractNode.java:[278,5]
 method does not override or implement a method from a supertype
[ERROR] 
/build/1st/checkstyle-8.14/src/main/java/com/puppycrawl/tools/checkstyle/filters/XpathFilter.java:[190,45]
 incompatible types: java.util.List> cannot be 
converted to java.util.List
[ERROR] 
/build/1st/checkstyle-8.14/src/main/java/com/puppycrawl/tools/checkstyle/xpath/ElementNode.java:[38,8]
 com.puppycrawl.tools.checkstyle.xpath.ElementNode is not abstract and does not 
override abstract method head() in net.sf.saxon.om.GroundedValue
[ERROR] 
/build/1st/checkstyle-8.14/src/main/java/com/puppycrawl/tools/checkstyle/xpath/RootNode.java:[39,8]
 com.puppycrawl.tools.checkstyle.xpath.RootNode is not abstract and does not 
override abstract method head() in net.sf.saxon.om.GroundedValue
[ERROR] 
/build/1st/checkstyle-8.14/src/main/java/com/puppycrawl/tools/checkstyle/xpath/AttributeNode.java:[31,8]
 com.puppycrawl.tools.checkstyle.xpath.AttributeNode is not abstract and does 
not override abstract method head() in net.sf.saxon.om.GroundedValue
[INFO] 6 errors 

Processed: affects 914419

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 914419 src:iverilog
Bug #914419 [debhelper] debhelper mustn't set pass V to make
Added indication that 914419 affects src:iverilog
> thanks
Stopping processing here.

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

Bug#914695: marked as done (dgit autopkgtest breaks with git 2.20)

[Debian Bug Tracking System]

Your message dated Sun, 02 Dec 2018 20:44:52 +
with message-id 
and subject line Bug#914695: fixed in git 1:2.20.0~rc2-1
has caused the Debian Bug report #914695,
regarding dgit autopkgtest breaks with git 2.20
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.)


-- 
914695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dgit
Version: 8.1
Severity: serious
X-Debbugs-CC: g...@packages.debian.org

My cron job writes:

> autopkgtest regression
> in dgit (8.1) on amd64
> due to git (1:2.19.2-1 to 1:2.20.0~rc1-1)
> test info
> REGRESSION
> https://ci.debian.net/data/autopkgtest/testing/amd64/d/dgit/1382882/log.gz
> https://ci.debian.net/packages/d/dgit/testing/amd64
> null
> https://ci.debian.net/api/v1/retry/1382882
> migration excuses for git
> Maintainer: Gerrit Pape
> Too young, only 0 of 38 days old
> missing build on mips64el: git (from 1:2.19.2-1)
> old binaries left on all: git-all, git-cvs, git-daemon-run, 
> git-daemon-sysvinit, git-doc, git-el, git-email, git-gui, git-man, 
> git-mediawiki, git-svn, gitk, gitweb (from 1:2.19.2-1) (but ignoring cruft, 
> so nevermind)
> Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git.html
> Required age increased by 28 days because of autopkgtest

Currently this regression is contributing to the delay of the
migration of git to testing.

Looking at the test log did not immediately suggest a cause to me.
But it is probably much easier for me to (at least initially)
investigate this, since I will hopefully understand what the test case
was trying to do.

I intend to investigate properly in the next few days.  For the moment
I have filed this bug against dgit.  When I know more about the issue
I will update this bug, including reassigning it if appropriate.

To the git maintainers: please let me know if this update was urgent
so that I can prioritise appropriately.

This mail is not a CI team mail, but
  https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
may be of some interest.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
Source: git
Source-Version: 1:2.20.0~rc2-1

We believe that the bug you reported is fixed in the latest version of
git, 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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Nieder  (supplier of updated git 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: Sun, 02 Dec 2018 12:11:19 -0800
Source: git
Binary: git git-man git-doc git-cvs git-svn git-mediawiki git-email 
git-daemon-run git-daemon-sysvinit git-gui gitk git-el gitweb git-all
Architecture: source all amd64
Version: 1:2.20.0~rc2-1
Distribution: unstable
Urgency: low
Maintainer: Gerrit Pape 
Changed-By: Jonathan Nieder 
Description:
 git- fast, scalable, distributed revision control system
 git-all- fast, scalable, distributed revision control system (all subpacka
 git-cvs- fast, scalable, distributed revision control system (cvs interope
 git-daemon-run - fast, scalable, distributed revision control system 
(git-daemon s
 git-daemon-sysvinit - fast, scalable, distributed revision control system 
(git-daemon s
 git-doc- fast, scalable, distributed revision control system (documentatio
 git-el - fast, scalable, distributed revision control system (emacs suppor
 git-email  - fast, scalable, distributed revision control system (email add-on
 git-gui- fast, scalable, distributed revision control system (GUI)
 git-man- fast, scalable, distributed revision control system (manual pages
 git-mediawiki - fast, scalable, distributed revision control system (MediaWiki 
re
 git-svn- fast, scalable, distributed revision control system (svn interope
 gitk   - fast, scalable, distributed revision control system (revision tre
 gitweb - fast, scalable, distributed revision 

Processed: found 915332 in 0.105-18

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 915332 0.105-18
Bug #915332 [src:policykit-1] policykit: unprivileged users with UID > INT_MAX 
can successfully execute any systemctl command
Marked as found in versions policykit-1/0.105-18.
> thanks
Stopping processing here.

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

Bug#910219: marked as done (libdeps-renderer-dot-perl: copyright file missing after upgrade (policy 12.5))

[Debian Bug Tracking System]

Your message dated Sun, 02 Dec 2018 20:43:17 +
with message-id 
and subject line Bug#910219: fixed in deps 0.13-4
has caused the Debian Bug report #910219,
regarding libdeps-renderer-dot-perl: copyright file missing after upgrade 
(policy 12.5)
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.)


-- 
910219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdeps-renderer-dot-perl
Version: 0.13-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  stretch -> buster

>From the attached log (scroll to the bottom...):

0m42.9s ERROR: WARN: Inadequate results from running adequate!
  libdeps-renderer-dot-perl: missing-copyright-file 
/usr/share/doc/libdeps-renderer-dot-perl/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libdeps-renderer-dot-perl/copyright
  # ls -lad /usr/share/doc/libdeps-renderer-dot-perl
  drwxr-xr-x 2 root root 40 Aug  2 13:53 
/usr/share/doc/libdeps-renderer-dot-perl
  # ls -la /usr/share/doc/libdeps-renderer-dot-perl/
  total 0
  drwxr-xr-x   2 root root   40 Aug  2 13:53 .
  drwxr-xr-x 153 root root 3180 Aug  2 13:53 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


libdeps-renderer-dot-perl_0.13-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: deps
Source-Version: 0.13-4

We believe that the bug you reported is fixed in the latest version of
deps, 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 910...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yann Dirson  (supplier of updated deps 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: Sun, 02 Dec 2018 20:46:46 +0100
Source: deps
Binary: libdeps-perl libdeps-renderer-dot-perl deps-tools-cli
Architecture: source all
Version: 0.13-4
Distribution: unstable
Urgency: medium
Maintainer: Yann Dirson 
Changed-By: Yann Dirson 
Description:
 deps-tools-cli - DEPS command-line tools
 libdeps-perl - Dependency Extraction and Processing System
 libdeps-renderer-dot-perl - DEPS renderer plugin using GraphViz/dot
Closes: 910219
Changes:
 deps (0.13-4) unstable; urgency=medium
 .
   * Stop using symlinks for doc dir (still unclear why the code removed
 here was not honored before -3) (Closes: #910219).
   * Add Vcs-* fields.
Checksums-Sha1:
 b849d3ee6cf70ca4f922c12785e34533e3405bac 1883 deps_0.13-4.dsc
 9a1dcc5eef0d950b35e54cacedc0be7a6cc101f6 3367 deps_0.13-4.diff.gz
 28dbb92f5d1f39f6e4d8035f696dd7218af067b0 6408 deps-tools-cli_0.13-4_all.deb
 8c414b0c51516999b7b02a9732237b75ee6b392c 5793 deps_0.13-4_amd64.buildinfo
 42935d1a49de8db87b95bd99875a09d24e29cce3 18080 libdeps-perl_0.13-4_all.deb
 0069a375b92b73c88443d634cc5510ec5051fa02 4204 
libdeps-renderer-dot-perl_0.13-4_all.deb
Checksums-Sha256:
 bc33222c86691750b2e11b9507d20fec1bea7f3a1bd16786ec940ecbb354148d 1883 
deps_0.13-4.dsc
 a32e5d98dfd92fa07dc85c9bca32a1293cc4f773d8e41d5ca1c7d102b6c2bf2d 3367 
deps_0.13-4.diff.gz
 3b02383ab169081e88a63006f275a37bf965db69c1b3067029abed791791bbbc 6408 
deps-tools-cli_0.13-4_all.deb
 

Bug#915332: policykit: unprivileged users with UID > INT_MAX can successfully execute any systemctl command

[Salvatore Bonaccorso]

Source: policykit-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://gitlab.freedesktop.org/polkit/polkit/issues/74

As reported in https://gitlab.freedesktop.org/polkit/polkit/issues/74
, a unprivileged user with UID > INT_MAX can successfully execute any
systemctl command .

Regards,
Salvatore

Processed: closing 898165

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 898165 3.16.57-1
Bug #898165 [src:linux] linux-image-3.16.0-6-amd64: can't mount NFS shares via 
nfs referrals
The source 'linux' and version '3.16.57-1' do not appear to match any binary 
packages
Marked as fixed in versions linux/3.16.57-1.
Bug #898165 [src:linux] linux-image-3.16.0-6-amd64: can't mount NFS shares via 
nfs referrals
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#915331: iem-plugin-suite FTBFS with juce-tools 5.4.1~repack-1

[Adrian Bunk]

Source: iem-plugin-suite
Version: 1.7.1-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/iem-plugin-suite.html

...
make V=1 -j1 "INSTALL=install --strip-program=true"
make[2]: Entering directory '/build/1st/iem-plugin-suite-1.7.1'
Projucer -resave "DualDelay/DualDelay.jucer"
JUCE v5.4.1

**
Projucer 5.4.1  ---  Build date: Nov 14 2018
Log started: 1 Dec 2018 2:35:18am

Linux
CPU: 2800MHz  Cores: 15  48298MB
Unrecognised command: "-resave"
make[2]: *** [Makefile:128: DualDelay/Builds/LinuxMakefile/Makefile] Error 1

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

[Ansgar Burchardt]

Marc Haber writes:
> The next debhelper change might choose to give / instead of /usr as a
> target directory by default, moving hundreds of megabytes from /usr to /
> over time. My question was about the distant future, and not the current
> snapshot of things.

If anything then /usr would be the prefix for all packages; nothing
would be installed to /bin, /sbin or /lib.  (And there is no /share or
/local.)

But this is obviously only possible if non-merged-/usr is not supported
at all as that would mean shipping only /usr/bin/sh and no /bin/sh; the
/bin -> /usr/bin symlink would then be required.

Ansgar

Bug#914680: libplplotada3: must change the SOversion

[Nicolas Boulenguez]

Package: libplplotada3
Version: 5.13.0+dfsg-10
Followup-For: Bug #914680

Hello.

Lintian has spotted the error leading to this situation:
the shared library package named
  libplplotada$(soversion)
is supposed to contain a file named:
  /usr/lib/$(multiarch)/libplplotada.so.$(soversion)
but libplplotada3 currently contains /u/l/*/libplplotada.so.2.1.1.

The correct fix to both problems is to rename the library.  Keeping
2.1.1 makes the promise that the new library offers the same ABI to
executables linked with the previous version, which is is probably
false because they were built with gnat-7.

You may
- rename the library as libplplotada.so.3 and keep the package name
- rename both the library and the package if you prefer something like
  2.1.1.3 for consistency with the other languages.

Bug#915329: gigedit FTBFS with libgtkmm-3.0-dev 3.24.0-1

[Adrian Bunk]

Source: gigedit
Version: 1.1.0-2
Severity: serious
Tags: ftbfs

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

...
In file included from builtinpix.cpp:2:
../compat.h: In constructor 'HBox::HBox()':
../compat.h:140:41: error: 'HORIZONTAL' is not a member of 'Gtk::Orientation'
 HBox() : Gtk::Box(Gtk::Orientation::HORIZONTAL) {}
 ^~
../compat.h: In constructor 'VBox::VBox()':
../compat.h:145:41: error: 'VERTICAL' is not a member of 'Gtk::Orientation'
 VBox() : Gtk::Box(Gtk::Orientation::VERTICAL) {}
 ^~~~
../compat.h: In constructor 'HButtonBox::HButtonBox()':
../compat.h:150:53: error: 'HORIZONTAL' is not a member of 'Gtk::Orientation'
 HButtonBox() : Gtk::ButtonBox(Gtk::Orientation::HORIZONTAL) {}
 ^~
../compat.h: In constructor 'HScale::HScale()':
../compat.h:155:45: error: 'HORIZONTAL' is not a member of 'Gtk::Orientation'
 HScale() : Gtk::Scale(Gtk::Orientation::HORIZONTAL) {}
 ^~
../compat.h: In constructor 'HScale::HScale(const 
Glib::RefPtr&)':
../compat.h:156:104: error: 'HORIZONTAL' is not a member of 'Gtk::Orientation'
 HScale(const Glib::RefPtr& adjustment) : 
Gtk::Scale(adjustment, Gtk::Orientation::HORIZONTAL)
...

Bug#915328: coinor-symphony FTBFSwith latest TeX Live: LaTeX Error: Option clash for package color.

[Adrian Bunk]

Source: coinor-symphony
Version: 5.6.16+repack1-1
Severity: serious
Tags: ftbfs

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

...
make[2]: Leaving directory '/build/1st/coinor-symphony-5.6.16+repack1'
cd Doc && ( latex man ; latex man ; dvipdfm man )
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./man.tex
LaTeX2e <2018-04-01> patch level 5
(/usr/share/texlive/texmf-dist/tex/latex/base/book.cls
Document Class: book 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/bk11.clo))
(/usr/share/texlive/texmf-dist/tex/latex/graphics/epsfig.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/dvips.def
(/usr/share/texmf/tex/latex/html/html.sty)
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
For additional information on amsmath, use the `?' option.
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
(/usr/share/texlive/texmf-dist/tex/latex/preprint/fullpage.sty)
(/usr/share/texlive/texmf-dist/tex/latex/easy/easyeqn.sty
Document Style `easyeqn' v1.94 <2002/03/18>.
(/usr/share/texlive/texmf-dist/tex/latex/easy/easy.sty
Document Style `easy' v1.1 <2001/05/31>.
)) (/usr/share/texlive/texmf-dist/tex/latex/fancyvrb/fancyvrb.sty
Style option: `fancyvrb' v3.0 <2018/11/01> (tvz)
(/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)))
(/usr/share/texlive/texmf-dist/tex/latex/listings/listings.sty
(/usr/share/texlive/texmf-dist/tex/latex/listings/lstmisc.sty)
(/usr/share/texlive/texmf-dist/tex/latex/listings/listings.cfg))
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)
(/usr/share/texlive/texmf-dist/tex/latex/splitindex/splitidx.sty)

! LaTeX Error: Option clash for package color.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...  
  
l.85 
 
? 
! Emergency stop.

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

[Marc Haber]

On Sun, Dec 02, 2018 at 07:54:39PM +, Simon McVittie wrote:
> I would encourage anyone with questions about the behaviour of merged and
> unmerged /usr systems to try them, either by building one chroot, container
> or VM with merged /usr and one without, or by building a chroot, container
> or VM with unmerged /usr, copying it, and installing usrmerge in the copy.

That would give me an impression about how things are today.

> The answer to your question is that non-/usr-merged systems behave the
> same way they always have: binaries end up wherever the source package
> chooses to put them when it builds the .deb (typically determined by
> where they appear under debian/tmp).

The next debhelper change might choose to give / instead of /usr as a
target directory by default, moving hundreds of megabytes from /usr to /
over time. My question was about the distant future, and not the current
snapshot of things.

And, it has been satisfactorily answered by now.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

[Simon McVittie]

On Sun, 02 Dec 2018 at 19:54:39 +, Simon McVittie wrote:
> When installed on a merged /usr system:

Oops, of course this should have said:

.deb contains -> /bin/grep/usr/bin/perl
/bin/fooexists thanks to /bin symlink   exists thanks to /bin symlink
/usr/bin/foo   physical locationphysical location

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

[Ansgar Burchardt]

Marc Haber writes:
> On Sat, Dec 01, 2018 at 11:36:45PM +0100, Didier 'OdyX' Raboud wrote:
>> Le samedi, 1 décembre 2018, 19.29:59 h CET Marc Haber a écrit :
>> > Will binaries move from /usr/bin to /bin? Or will binaries move from
>> > /bin to /usr/bin?
>> 
>> A merged-/usr has a /bin → /usr/bin symlink; so a .deb package unpacking
>> /bin/grep will make that binary end up in /usr/bin/grep; but the
>> /bin → /usr/bin symlink ensures that you can either access /usr/bin/grep  
>> directly or /bin/grep through the symlink.
>
> And where will the binaries and up on an un-usrmerged system with a
> dedicated /usr? in /usr, I hope?

They won't move on a system that doesn't have merged-/usr.  /bin/bash
will stay in /bin/bash.  If you switch to a merged-/usr (for example by
installing usrmerge) then they will be moved to /usr.

Ansgar

Bug#915326: ksh FTBFS with glibc 2.28

[Adrian Bunk]

Source: ksh
Version: 93u+20120801-3.3
Severity: serious
Tags: ftbfs

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

...
/build/1st/ksh-93u+20120801/src/lib/libast/string/fmtdev.c: In function 
'fmtdev':
/build/1st/ksh-93u+20120801/src/lib/libast/string/fmtdev.c:44:16: error: 
expected expression before ';' token
  ma = major(mm);
^
/build/1st/ksh-93u+20120801/src/lib/libast/string/fmtdev.c:45:16: error: 
expected expression before ';' token
  mi = minor(mm);
^
mamake [lib/libast]: *** exit code 1 making fmtdev.o

Bug#915316: ansible: FTBFS due to missing build dependency on python-jinja2

[Jeremy Bicha]

Control: tags -1 +ftbfs

Here's an additional patch you'll need too.

By the way, I encourage you to do source-only uploads which would have
caught this build failure sooner.

Thanks,
Jeremy Bicha
From ebe6e2cdde25e1a918d93a2c696b92bd1a2dfc6c Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Sun, 2 Dec 2018 14:51:23 -0500
Subject: [PATCH] Set HOME=$(CURDIR) to fix docs build

Unable to create local directories(/sbuild-nonexistent/.ansible/tmp):
 [Errno 13] Permission denied: '/sbuild-nonexistent'

Closes: #915316
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index f6f8ad5a..098355e6 100755
--- a/debian/rules
+++ b/debian/rules
@@ -7,7 +7,7 @@ override_dh_clean:
 	dh_clean --exclude=test/units/inventory_test_data/group_vars/noparse/all.yml~
 
 override_dh_installdocs:
-	make docs
+	HOME=$(CURDIR) make docs
 	dh_installdocs
 
 #override_dh_auto_build:
-- 
2.19.1

Processed: Re: ansible: FTBFS due to missing build dependency on python-jinja2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +ftbfs
Bug #915316 [ansible] ansible: FTBFS due to missing build dependency on 
python-jinja2
Added tag(s) ftbfs.

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

Processed: affects 906365

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 906365 src:ipxe
Bug #906365 [src:gcc-8] ipxe: FTBFS in buster/sid (Error: can't resolve 
`__table_entries.2701')
Added indication that 906365 affects src:ipxe
> thanks
Stopping processing here.

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

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

[Simon McVittie]

On Sun, 02 Dec 2018 at 20:16:10 +0100, Marc Haber wrote:
> On Sat, Dec 01, 2018 at 11:36:45PM +0100, Didier 'OdyX' Raboud wrote:
> > A merged-/usr has a /bin → /usr/bin symlink; so a .deb package unpacking
> > /bin/grep will make that binary end up in /usr/bin/grep; but the
> > /bin → /usr/bin symlink ensures that you can either access /usr/bin/grep  
> > directly or /bin/grep through the symlink.
> 
> And where will the binaries and up on an un-usrmerged system with a
> dedicated /usr? in /usr, I hope?

I would encourage anyone with questions about the behaviour of merged and
unmerged /usr systems to try them, either by building one chroot, container
or VM with merged /usr and one without, or by building a chroot, container
or VM with unmerged /usr, copying it, and installing usrmerge in the copy.

The answer to your question is that non-/usr-merged systems behave the
same way they always have: binaries end up wherever the source package
chooses to put them when it builds the .deb (typically determined by
where they appear under debian/tmp).

To avoid breaking hard-coded paths on existing non-/usr-merged systems,
that has to be where the package has traditionally put them, unless
the package takes special steps to create a compatibility symlink on
non-merged-/usr systems (which I would not recommend[1]).

When installed on an unmerged-/usr system:

.deb contains -> /bin/grep/usr/bin/perl
/bin/foo  physical location   does not exist
/usr/bin/foo   does not exist   physical location

When installed on a merged /usr system:

.deb contains -> /bin/grep/usr/bin/perl
/bin/fooexists thanks to /bin symlink   physical location
/usr/bin/fooexists thanks to /bin symlink   physical location

None of the above depends on whether /usr is a mount point. If /usr is a
mount point, then /bin/grep is physically located on the /usr filesystem
if the system is merged-/usr, or on the root filesystem otherwise.

Replace /bin/grep in the above with any executable that is canonically
in /bin or /sbin (its source package would typically install
something like debian/tmp/bin/grep), and replace /usr/bin/perl with any
executable that is canonically in /usr/bin or /usr/sbin (its source
package would typically install something like debian/tmp/usr/bin/perl).

smcv

[1] 
https://lists.debian.org/msgid-search/20181122205532.ga2...@espresso.pseudorandom.co.uk

Processed: severity of 915321 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Possibly lower
> severity 915321 serious
Bug #915321 [libc6] Mutex creation failed
Severity set to 'serious' from 'critical'
> thanks
Stopping processing here.

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

Bug#914835: python3-defaults breaks aiocoap autopkgtest

[Paul Gevers]

Hi

On 02-12-2018 20:21, Mattia Rizzolo wrote:
> Else, Paul: I see this failure concern the tests only, I think this
> could be force-badtest'ed or something to let py3-defaults in.

Done.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: severity of 913854 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 913854 serious
Bug #913854 [src:siril] siril ftbfs with glibc-2.28
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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