Bug#879857: xserver-xorg-video-intel: [i915] GPU hang after every suspend or hibernate on Debian 9 stretch

[Ferdinand Rau]

This issue is not resolved.

Dear Maintainer:

Could you kindly confirm that this bug was reported correctly?

Could you please comment on the next steps? Even if it is not possible or not 
reasonable to work on this bug, I would love to know this.

Should I report another bug, e.g. against the kernel package or against the 
upstream xorg project?

Kind regards,
Ferdinand Rau

Bug#873408: [Pkg-julia-devel] Bug#873408: julia: Please update to llvm-toolchain 4.0 or, better, 5.0

[Graham Inggs]

On 20 November 2017 at 20:54, Emilio Pozuelo Monfort  wrote:
> It should be fine now with 4.0. Would be good if this could move to either
> unversioned llvm/clang (which defaults to 4.0 now) or to versioned 4.0. 
> Bumping
> to serious as we want to remove 3.8 soon to reduce the high number of llvm
> versions that we currently ship.

Unfortunately julia 0.4.7 doesn't build with llvm/clang 4.0.
Julia 0.6.1 is available (#839668) but we are blocked by a lack of
support for https in libgit2 (#832798).
There is ongoing activity in the upstream PR, so we remain hopeful.

For now, julia can be removed from testing.

Bug#881097: Removing libnet-ping-external-perl from jessie, stretch and unstable

[Salvatore Bonaccorso]

Hi Tony!

Thanks for your reply, dropping LTS list since reply is specific for
oldstable, stable and unstable.

On Wed, Nov 22, 2017 at 03:32:36PM -0800, tony mancill wrote:
> On Wed, Nov 22, 2017 at 09:00:59PM +0100, Emilio Pozuelo Monfort wrote:
> > On 08/11/17 20:19, Ola Lundqvist wrote:
> > > Hi
> > > 
> > > Considering that this package is about to be removed from jessie I
> > > guess it should be removed from wheezy too. How is that done? Should I
> > > contact the FTP maintainers about it, or do we simply ignore the
> > > issue?
> > 
> > We don't have point releases, so I'm not sure we can get a package removed 
> > at
> > this stage without extra work by the ftp masters. So our options would be:
> > 
> > - mark as no-dsa if it's not important enough
> > - mark as unsupported / end-of-life
> > - fix it
> > - get it removed
> > 
> > The issue seems only exploitable if it's used by a service that is exposed
> > remotely or to other issues... and has no rdeps in wheezy. OTOH there is at
> > least one sponsor using that package. So removing it may not be the best 
> > course
> > given there is a proposed patch. So I'd go with either no-dsa or fix it,
> > depending on the assessed importance.
> 
> Hi,
> 
> My apologies for taking a while to join the thread.  As the most recent
> uploader of this package, I feel responsible for helping get it into a
> safe state if we opt to keep it.  However, I am not an active user, so
> if the package is to remain in Debian, it might be better to transition
> it to the Debian Perl Team (assuming that is amenable to the team).
> 
> I tend to agree with Emilio that removing it might not be the best
> course of action for our users, particularly given that we have a patch
> and the popcon [1] is non-zero.  Removing it from the distribution seems
> like it merely leaves users with a known vulnerability.  Also, the
> package might be used in derivatives.
> 
> I agree with Simon that it's a little odd for the patch to bump the
> version.  (OTOH, it makes it much easier to differentiate from the
> vulnerable 0.15.)  Still, I am inclined to take the patch as a patch
> against upstream 0.15 for the upload to unstable and then backport it
> for 0.13 for stable and oldstable.  Or perhaps Alexandr Ciornii (on the
> cc) would be willing to release 0.16 including the patch.
> 
> Thoughts?

The package is basically "unmaintained" (upstream)[*] and for almost
10 years did not address
https://rt.cpan.org/Public/Bug/Display.html?id=33230 (maybe you can
argue, as well a fault for various "downstreams" to not notice and
bring that earlier up, defintively. I wonder why only now it got
attention on oss-security, for which I then requested a CVE)

IMHO the best course of action is still to have it removed, in all
suites. For unstable, so that it's not included in buster. And for
oldstable and stable (as scheduled for the upcoming point releases)
via the point release announcements. The announcement will contain a
section which packages are removed from Debian, and for which reason,
so still users of Net::Ping::External are informed.

I agree as well that if one starts to argue that way that there are
old packages which do not see updates from upstream, then a whole more
should be removed from Debian ;-). My point was not this though, I'm
concernend that there was a bug with security implications for almost
10 years reported in public bugtracker, without even a reply to it to
acknowledge the problem.

Regards,
Salvatore

 [*] well not exactly, I know there was e.g. 0.15, so there is
 activity, but see remaining of sentence.

Bug#876191: most: configure cannot be built from source

[Helmut Grohne]

On Fri, Nov 24, 2017 at 06:22:05PM -0800, Benj. Mako Hill wrote:
> I'll also say that I'm skeptical about both the severity you've chosen
> here (serious), about describing this as a FTBFS issue, and about your
> suggestion that this is a DFSG issue.

I deliberately avoided the FTBFS language, because it is not a FTBFS.
It's different. It's like shipping a binary that cannot be regenerated
and using that during build. The term FTBFS is well defined and does not
cover this case.

> If there is a serious DFSG issue here, it's not a FTBFS issue but
> rather a question of whether or not the source package contains the
> full source in the first place. I'm open to being convinced otherwise
> but I think it does.

I do believe that this is a DFSG issue.

> If I generate a configure file with autoconf and then modify it by
> hand in order to create a working build script, I don't I've somehow
> made it impossible to provide source for that package. I think I'm
> still providing the preferred form of modification (as the GPL defines
> source). I agree that that situation is brittle and bad and should be
> avoided.  But I don't think it's a DFSG issue.

Would you say the same if you compile a binary, use a hex editor to fix
the binary and then ship the binary in your source package? I mean you
preferred to edit the binary with a hex editor, so wouldn't it be
preferred form for modification?

Now consider my case. Most commonly, I want to change AC_RUN_IFELSE into
AC_TRY_COMPILE or AC_COMPUTE_INT. That's a very simple change on
configure.ac that produces a big diff on the generated configure.

Also consider that autoconf projects tend to ship embedded copies of .m4
files. A bug in those .m4 files is often fixed upstream. Fixing it could
be a simple matter of updating the embedded copy if one could regenerate
configure.

In both of these examples, I very much do not prefer working with the
generated configure as it feels very much like editing a binary with a
hex editor. Thus I argue that configure is not the preferred form for
modification. Shipping only configure makes DFGS #3 practically moot.

> If this has been discussed elsewhere or if there is Debian policy on
> this I don't know about, I'd appreciate being pointed to this and I'm
> happy to defer to this. In the meantime, I'd appreciate help fixing
> this issue. I'm not likely to have bandwidth for a few more weeks.

I guess we should document this issue class centrally. It is similar to
the javascript bundling issue (where people suppose that minified or
concatenated javascript files could be considered source). A very
similar bu is #874261. #882538 could be called related.

This issue comes about every time Debian is bootstrapped for a new
architecture as configure tends to have bugs (e.g. ppc64el). I'm seeing
it now as I bootstrap Debian for something like a new architecture
(cross building). So this is the class of bugs to watch out.

Helmut

Bug#876191: most: configure cannot be built from source

[Benj. Mako Hill]

Greetings Helmut!


> I was trying to fix a bug in most that requires modifying configure.
> Thus I tried to regenerate it and ... failed.

I'll start by saying that this is a real bug and that I agree that it
should be fixed. And thanks so much for notice and submitting it! And
for trying to fix the other issue!

I'll also say that I'm skeptical about both the severity you've chosen
here (serious), about describing this as a FTBFS issue, and about your
suggestion that this is a DFSG issue.

After all, the package still builds from its source and I think we
have everything that upstream has.

If there is a serious DFSG issue here, it's not a FTBFS issue but
rather a question of whether or not the source package contains the
full source in the first place. I'm open to being convinced otherwise
but I think it does.

If I generate a configure file with autoconf and then modify it by
hand in order to create a working build script, I don't I've somehow
made it impossible to provide source for that package. I think I'm
still providing the preferred form of modification (as the GPL defines
source). I agree that that situation is brittle and bad and should be
avoided.  But I don't think it's a DFSG issue.

If this has been discussed elsewhere or if there is Debian policy on
this I don't know about, I'd appreciate being pointed to this and I'm
happy to defer to this. In the meantime, I'd appreciate help fixing
this issue. I'm not likely to have bandwidth for a few more weeks.

Regards,
Mako


-- 
Benjamin Mako Hill
http://mako.cc/

Creativity can be a social contribution, but only in so far
as society is free to use the results. --GNU Manifesto


signature.asc
Description: PGP signature

Processed: Re: file conflict (lacks Replaces:) with fonts-noto-unhinted << 20171026-1

[Debian Bug Tracking System]

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

> notfound 880141 fonts-noto/20171026-1
Bug #880141 {Done: Jonas Smedegaard } [fonts-noto-hinted] file 
conflict (lacks Replaces:) with fonts-noto-unhinted << 20171026-1
No longer marked as found in versions fonts-noto/20171026-1.
> thanks
Stopping processing here.

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

Bug#882625: ring FTBFS with libopendht-dev 1.5.0-1

[Adrian Bunk]

Source: ring
Version: 20171024.1.eadbdeb~ds1-1
Severity: serious

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

...
ringaccount.cpp: In member function 'void 
ring::RingAccount::loadAccountFromDHT(const string&, const string&)':
ringaccount.cpp:1139:33: error: no matching function for call to 
'dht::DhtRunner::bootstrap(std::vector >&)'
 dht_.bootstrap(bootstrap);
 ^
In file included from ringaccount.h:35:0,
 from ringaccount.cpp:24:
/usr/include/opendht/dhtrunner.h:205:10: note: candidate: void 
dht::DhtRunner::bootstrap(const std::vector&, 
dht::DoneCallbackSimple&&)
 void bootstrap(const std::vector& nodes, DoneCallbackSimple&& 
cb={});
  ^
/usr/include/opendht/dhtrunner.h:205:10: note:   no known conversion for 
argument 1 from 'std::vector >' to 
'const std::vector&'
/usr/include/opendht/dhtrunner.h:206:10: note: candidate: void 
dht::DhtRunner::bootstrap(const dht::SockAddr&, dht::DoneCallbackSimple&&)
 void bootstrap(const SockAddr& addr, DoneCallbackSimple&& cb={});
  ^
/usr/include/opendht/dhtrunner.h:206:10: note:   no known conversion for 
argument 1 from 'std::vector >' to 
'const dht::SockAddr&'
/usr/include/opendht/dhtrunner.h:212:10: note: candidate: void 
dht::DhtRunner::bootstrap(const std::vector&)
 void bootstrap(const std::vector& nodes);
  ^
/usr/include/opendht/dhtrunner.h:212:10: note:   no known conversion for 
argument 1 from 'std::vector >' to 
'const std::vector&'
/usr/include/opendht/dhtrunner.h:220:10: note: candidate: void 
dht::DhtRunner::bootstrap(const string&, const string&)
 void bootstrap(const std::string& host, const std::string& service);
  ^
/usr/include/opendht/dhtrunner.h:220:10: note:   candidate expects 2 arguments, 
1 provided
ringaccount.cpp: In member function 'void ring::RingAccount::doRegister_()':
ringaccount.cpp:2067:37: error: no matching function for call to 
'dht::DhtRunner::bootstrap(std::vector >&)'
 dht_.bootstrap(bootstrap);
 ^
In file included from ringaccount.h:35:0,
 from ringaccount.cpp:24:
/usr/include/opendht/dhtrunner.h:205:10: note: candidate: void 
dht::DhtRunner::bootstrap(const std::vector&, 
dht::DoneCallbackSimple&&)
 void bootstrap(const std::vector& nodes, DoneCallbackSimple&& 
cb={});
  ^
/usr/include/opendht/dhtrunner.h:205:10: note:   no known conversion for 
argument 1 from 'std::vector >' to 
'const std::vector&'
/usr/include/opendht/dhtrunner.h:206:10: note: candidate: void 
dht::DhtRunner::bootstrap(const dht::SockAddr&, dht::DoneCallbackSimple&&)
 void bootstrap(const SockAddr& addr, DoneCallbackSimple&& cb={});
  ^
/usr/include/opendht/dhtrunner.h:206:10: note:   no known conversion for 
argument 1 from 'std::vector >' to 
'const dht::SockAddr&'
/usr/include/opendht/dhtrunner.h:212:10: note: candidate: void 
dht::DhtRunner::bootstrap(const std::vector&)
 void bootstrap(const std::vector& nodes);
  ^
/usr/include/opendht/dhtrunner.h:212:10: note:   no known conversion for 
argument 1 from 'std::vector >' to 
'const std::vector&'
/usr/include/opendht/dhtrunner.h:220:10: note: candidate: void 
dht::DhtRunner::bootstrap(const string&, const string&)
 void bootstrap(const std::string& host, const std::string& service);
  ^
/usr/include/opendht/dhtrunner.h:220:10: note:   candidate expects 2 arguments, 
1 provided
mv -f .deps/libringacc_la-namedirectory.Tpo 
.deps/libringacc_la-namedirectory.Plo
Makefile:573: recipe for target 'libringacc_la-ringaccount.lo' failed
make[6]: *** [libringacc_la-ringaccount.lo] Error 1

Bug#882623: mahimahi FTBFS with glibc 2.25

[Adrian Bunk]

Source: mahimahi
Version: 0.97-1
Severity: serious

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

...
g++ -DHAVE_CONFIG_H -I. -I../..  -std=c++11 -pthread -Wdate-time 
-D_FORTIFY_SOURCE=2 -pedantic -Wall -Wextra -Weffc++ -Werror -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c -o socketpair.o 
socketpair.cc
socketpair.cc: In member function 'FileDescriptor UnixDomainSocket::recv_fd()':
socketpair.cc:73:67: error: reinterpret_cast from type 'const unsigned char*' 
to type 'int*' casts away qualifiers
 return *reinterpret_cast( CMSG_DATA( control_message ) );
   ^
Makefile:440: recipe for target 'socketpair.o' failed
make[4]: *** [socketpair.o] Error 1

Bug#882624: sbd FTBFS with glibc 2.25

[Adrian Bunk]

Source: sbd
Version: 1.3.1-1
Severity: serious

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

...
sbd-common.c: In function 'watchdog_populate_list':
sbd-common.c:268:13: error: In the GNU C Library, "makedev" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "makedev", include 
 directly. If you did not intend to use a system-defined macro
 "makedev", you should undefine it after including . [-Werror]
   {makedev(10,130), 0};
 ^~~



   
sbd-common.c:293:13: error: In the GNU C Library, "makedev" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "makedev", include 
 directly. If you did not intend to use a system-defined macro
 "makedev", you should undefine it after including . [-Werror]
   watchdogs[num_watchdogs++] = makedev(major, minor);
 ^  



   
sbd-common.c:342:13: error: In the GNU C Library, "major" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "major", include 
 directly. If you did not intend to use a system-defined macro
 "major", you should undefine it after including . [-Werror]
 major(watchdogs[i]), minor(watchdogs[i]));
 ^~ 



 
sbd-common.c:342:13: error: In the GNU C Library, "minor" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "minor", include 
 directly. If you did not intend to use a system-defined macro
 "minor", you should undefine it after including . [-Werror]
cc1: all warnings being treated as errors
Makefile:397: recipe for target 'sbd-common.o' failed
make[3]: *** [sbd-common.o] Error 1

Bug#882622: networking-mlnx FTBFS: test failures

[Adrian Bunk]

Source: networking-mlnx
Version: 1:9.0.0~b1-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes networking-mlnx FTBFS:

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

...
==
FAIL: 
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test__output_hosts_file_log_only_twice
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test__output_hosts_file_log_only_twice
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File 
"/usr/lib/python2.7/dist-packages/neutron/tests/unit/agent/linux/test_dhcp.py", 
line 2178, in test__output_hosts_file_log_only_twice
dm._output_hosts_file()
  File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/dhcp.py", line 
702, in _output_hosts_file
if self._get_port_extra_dhcp_opts(port):
  File "networking_mlnx/dhcp/mlnx_dhcp.py", line 45, in 
_get_port_extra_dhcp_opts
if hasattr(port, edo_ext.EXTRADHCPOPTS):
AttributeError: 'module' object has no attribute 'EXTRADHCPOPTS'


==
FAIL: 
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_host_and_opts_file_on_net_with_V6_stateless_and_V4_subnets
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_host_and_opts_file_on_net_with_V6_stateless_and_V4_subnets
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File "networking_mlnx/tests/unit/dhcp/test_mlnx_dhcp.py", line 219, in 
test_host_and_opts_file_on_net_with_V6_stateless_and_V4_subnets
dm._output_hosts_file()
  File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/dhcp.py", line 
691, in _output_hosts_file
if not no_opts and self._get_port_extra_dhcp_opts(port):
  File "networking_mlnx/dhcp/mlnx_dhcp.py", line 45, in 
_get_port_extra_dhcp_opts
if hasattr(port, edo_ext.EXTRADHCPOPTS):
AttributeError: 'module' object has no attribute 'EXTRADHCPOPTS'


==
FAIL: 
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_host_and_opts_file_on_stateless_dhcpv6_network
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_host_and_opts_file_on_stateless_dhcpv6_network
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File 
"/usr/lib/python2.7/dist-packages/neutron/tests/unit/agent/linux/test_dhcp.py", 
line 2237, in test_host_and_opts_file_on_stateless_dhcpv6_network
dm._output_hosts_file()
  File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/dhcp.py", line 
691, in _output_hosts_file
if not no_opts and self._get_port_extra_dhcp_opts(port):
  File "networking_mlnx/dhcp/mlnx_dhcp.py", line 45, in 
_get_port_extra_dhcp_opts
if hasattr(port, edo_ext.EXTRADHCPOPTS):
AttributeError: 'module' object has no attribute 'EXTRADHCPOPTS'


==
FAIL: 
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_host_file_on_net_with_v6_slaac_and_v4
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_host_file_on_net_with_v6_slaac_and_v4
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File "networking_mlnx/tests/unit/dhcp/test_mlnx_dhcp.py", line 260, in 
test_host_file_on_net_with_v6_slaac_and_v4
dm._output_hosts_file()
  File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/dhcp.py", line 
702, in _output_hosts_file
if self._get_port_extra_dhcp_opts(port):
  File "networking_mlnx/dhcp/mlnx_dhcp.py", line 45, in 
_get_port_extra_dhcp_opts
if hasattr(port, edo_ext.EXTRADHCPOPTS):
AttributeError: 'module' object has no attribute 'EXTRADHCPOPTS'


==
FAIL: 
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_non_local_subnets

Processed: Re: Processed: The packages in stretch/buster/sid do (build) depend on qtwebkit

[Debian Bug Tracking System]

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

> notfound 784514 qgis/2.14.7+dfsg-1~exp1
Bug #784514 [src:qgis] [qgis] Qt4's WebKit removal
No longer marked as found in versions qgis/2.14.7+dfsg-1~exp1.
> close 784514
Bug #784514 [src:qgis] [qgis] Qt4's WebKit removal
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: The packages in stretch/buster/sid do (build) depend on qtwebkit

[Debian Bug Tracking System]

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

> found 784514 2.14.7+dfsg-1~exp1
Bug #784514 {Done: Bas Couwenberg } [src:qgis] [qgis] 
Qt4's WebKit removal
Marked as found in versions qgis/2.14.7+dfsg-1~exp1 and reopened.
> thanks
Stopping processing here.

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

Bug#882618: libdbix-class-schema-loader-perl: Test failures

[gregor herrmann]

Package: libdbix-class-schema-loader-perl
Version: 0.07047-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=123681

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first seen on ci.debian.net [0], libdbix-class-schema-loader-perl's
test suite fails since recent changes in prerequsites. The same
happens during build which leads to a FTBFS bug:

DBIx::Class::ResultSource::schema(): Unable to perform storage-dependent 
operations with a detached result source (source 'Bar' is not associated with a 
schema). You need to use $schema->thaw() or manually set 
$DBIx::Class::ResultSourceHandle::thaw_schema while thawing. at 
t/20invocations.t line 18
# Looks like your test exited with 255 just after 7.
t/20invocations.t ... 
1..68
ok 1 - 'hardcode' isa 'DBIx::Class::Schema'
ok 2 - 'hardcode' isa 'DBIx::Class::ResultSet'
ok 3 - 'hardcode' isa 'DBICTest::Schema::_hardcode::Foo'
ok 4 - hardcode correct object
ok 5 - hardcode object created
ok 6 - No warnings during hardcode invocations
ok 7 - 'normal' isa 'DBIx::Class::Schema'
rmdir t/var/DDzUVkb6WU
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 61/68 subtests 

DBIx::Class::ResultSource::schema(): Unable to perform storage-dependent 
operations with a detached result source (source 'Bar' is not associated with a 
schema). You need to use $schema->thaw() or manually set 
$DBIx::Class::ResultSourceHandle::thaw_schema while thawing. at 
t/backcompat/0.04006/20invocations.t line 21
# Looks like your test exited with 255 just after 5.
t/backcompat/0.04006/20invocations.t  
1..32
ok 1 - 'hardcode' isa 'DBIx::Class::Schema'
ok 2 - 'hardcode' isa 'DBIx::Class::ResultSet'
ok 3 - hardcode
ok 4
ok 5 - 'normal' isa 'DBIx::Class::Schema'
rmdir t/var/BdN94D7OJ3
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 27/32 subtests 


While this is probably a bug in libhash-merge-perl (or one of its
dependencies), we have a problem here, and should update the
dependencies once it's fixed.


Cheers,
gregor


[0]
https://ci.debian.net/packages/libd/libdbix-class-schema-loader-perl/unstable/amd64/


-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAloYlZxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYwzhAAxUrKJzSLaKMPQmrPVnau1NDrJBMRq4VcVcBBfFlwKul4f3hvSDIopGKO
JrQrqvq2Z53mwHAfMh1kCoCYUoQ3CDiQvsv5sPI1noKIRCBkebLne7kkxWIAMb5U
0TO4n/6nNMEF0lY4Ir2pUEaCC50/UuFRw8T+btb01gUcNP2TguTdvalM3YF+qSC/
YDHlYTnoIvB1gR/qpRvwxuIED0/mq3RiOsFdEJTAERJknlbpWkD4JZApXiAtOgeD
E0QQBJ3/+7Yk6qkgru/O+Gxb7gTpFW3Gur0C2uJ4UxMYt6xvZFysQHOU8GJzM+oC
RxgsMf96iLoF7IkMzChNmYVvbBgrjEuNOtEpYqPYvQk9ZcBVN6LY8JGXYhFCJcWk
rF1hZgjO7XOPNE0UrznPFqe36r5BKpfFIP7HqH2UdIBhTGBq8Xt33993SkQZ+1Pj
KEw3etFtPrI/H93LMRDnB09UlspJ+zRibzODRzK2Rt9RNeRdZ2EHQkliVL8kt9g/
YBdWW/kMMURB9+R/cLuQjMqmVm4JRyfM4tD14GmHl18+ZQI0ck2pB6xVGAW8dyZV
XV23yCuMqg0SChhrKk6jDtjSolcNWtWW1Ok8dfsS3GhQ9YxFtTvTk0HnAXGhikDq
JvMjtYt2CPcs24A1MWzyp2HH+gbXXiPUEZF6gfRmXn1AvhTCGSM=
=q5E3
-END PGP SIGNATURE-

Processed: notfound 784514 in qgis/2.14.7+dfsg-1~exp1, closing 784514

[Debian Bug Tracking System]

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

> notfound 784514 qgis/2.14.7+dfsg-1~exp1
Bug #784514 [src:qgis] [qgis] Qt4's WebKit removal
No longer marked as found in versions qgis/2.14.7+dfsg-1~exp1.
> close 784514
Bug #784514 [src:qgis] [qgis] Qt4's WebKit removal
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: libqtwebkit4 dependency is back since 2.14.7+dfsg-1~exp1

[Debian Bug Tracking System]

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

> unarchive 784514
Bug #784514 {Done: Bas Couwenberg } [src:qgis] [qgis] 
Qt4's WebKit removal
Unarchived Bug 784514
> found 784514 2.14.7+dfsg-1~exp1
Bug #784514 {Done: Bas Couwenberg } [src:qgis] [qgis] 
Qt4's WebKit removal
Marked as found in versions qgis/2.14.7+dfsg-1~exp1 and reopened.
> tags 784514 buster sid
Bug #784514 [src:qgis] [qgis] Qt4's WebKit removal
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: Pending fixes for bugs in the libnet-ping-external-perl package

[Debian Bug Tracking System]

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

> tag 881097 + pending
Bug #881097 [libnet-ping-external-perl] libnet-ping-external-perl: 
CVE-2008-7319: command injection via crafted arguments
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#881097: Pending fixes for bugs in the libnet-ping-external-perl package

[pkg-perl-maintainers]

tag 881097 + pending
thanks

Some bugs in the libnet-ping-external-perl package are closed in
revision 701578a27f699b5b3b1540ee0e4a4f65333869b9 in branch 'master'
by tony mancill

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libnet-ping-external-perl.git/commit/?id=701578a

Commit message:

Add patch for CVE-2008-7319 (Closes: #881097)

Processed: cl-plus-ssl: Please migrate to openssl1.1 in Buster

[Debian Bug Tracking System]

Processing control commands:

> block 871056 by -1
Bug #871056 [release.debian.org] transition: openssl
871056 was blocked by: 858931 882549 828520 848680 859224 859742 859544 850897 
858929 859542 858937 828572 851076 859232 859146 859367 858993 870775 828483 
858936 859674 859225 828451 858857 859297 851078 859055 859053 859715 859669 
858927 851069 828329 859718 859671 858939 858990 859785 874699 828481 859054 
858436 859552 859550 851054 828441 844303 859545 859740 828471 882562 859673 
859786 859782 851077 859554 859675 858828 859548 851079 851084 859834 859226 
858930 882561 859229 858435 859145 870779 859783 873647 850895 859716 859543 
859826 854583 851085 859540 851073 851424 859555 859416 859222 828522 859790 
871939 858992 851086 859838 853778 859789 859829 851094 859831 859852 850890 
859750 853782 872885 858386 828449 859844 827076 850888 858398 859717 851093 
828503 859228 859841 850898 875349 863568 859853 858989 858935 851087 828557 
851074 835801 859719 867140 859553 859052 828475 859050 851090 859791 859784 
859556 828413 859851 859720 851091 828420 858991 851081 851070 859840 870778 
828477 859546 847611 859551 858928 851080 859721 859557 850886 859558 859230 
873574 858938 828429
871056 was not blocking any bugs.
Added blocking bug(s) of 871056: 882615

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

Bug#882615: cl-plus-ssl: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Source: cl-plus-ssl
Version: 20170630-1
Severity: serious
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans
Control: block 871056 by -1

Please migrate to libssl-dev in the Buster cycle. I am very sorry for
this late report but this package was never on my list. It slipped
because it never B-D on libssl1.0-dev and it builds perfectly fine
against libssl1.1.
I have actually no idea why the package in archive links against
libssl1.0.2 because it B-D on libssl-dev and if I rebuild then it
depends on libssl1.1 instead.

If you move torvards libssl1.1 you should make sure it loads libssl1.1
and not "just" libssl1.0.2.

Function wise:
SSL_library_init() and a few other macros towards "OPENSSL_init_ssl(0, NULL)"
  so "normal" C will work but if nim is accessing the functions directly
  then it will fail.

SSLv23_client_method() and friends are also macros. 1.1 Code should use
  TLS_client_method() instead. Functions like TLSv1_method() should be
  avoided because they give you _only_ TLSv1 and _never_ TLSv1.1, and/or
  TLSv1.2 like SSLv23_client_method(). 
  If you want to exclude a certain TLS version you should use something
  like SSL_OP_NO_TLSv1 to disable TLSv1 only (and keep other version
  like v1.1 and v1.2 around).

Data strucures. All structures are opaque and you need to tell libssl to
allocate it and free it (especially in crypto code). I can't tell if you 
dereference them, I can't read lisp.

A larger collection of what changed in OpenSSL 1.0.2->1.1 is at
   https://wiki.openssl.org/index.php/OpenSSL_1.1.0_Changes

Sebastian

Bug#882598: libavutil55: segfault after upgrade

[James Cowgill]

Hi,

On 24/11/17 15:40, James Cowgill wrote:
> Control: severity -1 grave
> Control: retitle -1 libavutil55: ABI broken by "add vector_dmac_scalar()"
> Control: forwarded -1 https://trac.ffmpeg.org/ticket/6861
> Control: tag -1 - moreinfo
> Control: found -1 7:3.4-1
> 
> On 24/11/17 14:46, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> I created FFmpeg ticket #6861, thank you for the report!
>> https://trac.ffmpeg.org/ticket/6861
> 
> That is not a nice bug.
> 
> I'll have to think about the best way to handle this. I guess we will
> have to revert the ABI breaking commit, identify the packages which are
> broken (including ffmpeg itself like in this bug), add some Breaks for
> them, and finally binNMU them. Alternatively we could force an ABI
> transition and rebuild everything, but I'm not sure if I want to do
> that (especially since we'll have to do another in a few months anyway).

On closer inspection (and reading the upstream bug), the ABI break
occurs in the private float_dsp.h header and the only consumers are
libavcodec and libavfilter. This makes things much easier than I
originally thought since the breakage is internal to ffmpeg.

I think this can be fixed by keeping the new ABI and use package
dependencies to enforce that it's used only with 3.4.

We need to ensure 3.4 libavcodec/libavfilter uses 3.4 libavutil, but
this is already guaranteed through the existing symbols system. We then
need to prevent 3.4 libavutil from being used with pre-3.4
libavcodec/libavfilter by adding this to libavutil55:

Breaks:
 libavcodec57 (<< 7:3.4),
 libavcodec-extra57 (<< 7:3.4),
 libavfilter6 (<< 7:3.4),
 libavfilter-extra6 (<< 7:3.4)

I think that will fix the bug. Can anyone see anything I've missed?

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#859852: in telegram-desktop marked as pending

[Nicholas Guriev]

Control: tag 859852 pending

Hello,

Bug #859852 in telegram-desktop reported by you has been fixed in the Git 
repository. You can
see the commit message below, and you can check the diff of the fix at:


https://anonscm.debian.org/git/collab-maint/telegram-desktop.git/commit/?id=cacda19

(this message was generated automatically based on the git commit message)
---
commit cacda19c0b3bfb84dcad3414fa713aef514e4636
Author: Nicholas Guriev 
Date:   Sat Nov 11 21:45:35 2017 +0300

Add Use-OpenSSL-v1.1.patch

Closes: #859852

Processed: Bug#859852 in telegram-desktop marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 859852 pending
Bug #859852 [telegram-desktop] telegram-desktop: Please migrate to openssl1.1 
in Buster
Added tag(s) pending.

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

Bug#784479: Patch available

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 patch

There is patch available for this at 

We might want to wait for the last tandem of KF5 apps though.

-- 
A group of politicians deciding to dump a President because his morals
are bad is like the Mafia getting together to bump off the Godfather for
not going to church on Sunday.
  Russell Baker

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


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

Processed: Patch available

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #784479 [src:kde4libs] [kde4libs] Qt4's WebKit removal
Added tag(s) patch.

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

Bug#882295: marked as done (ploop FTBFS with glibc 2.25)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 19:34:12 +
with message-id 
and subject line Bug#882295: fixed in ploop 1.15-4
has caused the Debian Bug report #882295,
regarding ploop FTBFS with glibc 2.25
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.)


-- 
882295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ploop
Version: 1.15-3
Severity: serious

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

...
  CC   delta_sysfs.o
delta_sysfs.c: In function 'get_dev_num':
delta_sysfs.c:241:13: error: In the GNU C Library, "makedev" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "makedev", include 
 directly. If you did not intend to use a system-defined macro
 "makedev", you should undefine it after including . [-Werror]
  *dev_num = makedev(maj, min);
 ^~ 



   
cc1: all warnings being treated as errors
../Makefile.inc:48: recipe for target 'delta_sysfs.o' failed
make[2]: *** [delta_sysfs.o] Error 1
--- End Message ---
--- Begin Message ---
Source: ploop
Source-Version: 1.15-4

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated ploop 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, 24 Nov 2017 21:07:16 +0200
Source: ploop
Binary: ploop libploop-dev libploop1
Architecture: source
Version: 1.15-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 libploop-dev - ploop API development library
 libploop1  - ploop API library
 ploop  - tools to work with ploop devices and images
Closes: 882295
Changes:
 ploop (1.15-4) unstable; urgency=medium
 .
   * QA upload.
   * Fix FTBFS with glibc 2.25. (Closes: #882295)
   * Unhide the compiler flags during the build.
   * Priority extra -> optional.
Checksums-Sha1:
 0c6dce2425f5a43f8d520c3e144f3fcb2dd95e72 1899 ploop_1.15-4.dsc
 a81673e14116d052470f58d9fb65c2ba5ea26f6d 4624 ploop_1.15-4.debian.tar.xz
Checksums-Sha256:
 5d0ac1a1464c6108e3f885358a4b80187a0f2d04991ef6f5054768fcc59731f3 1899 
ploop_1.15-4.dsc
 4b3979a7231350e80bbf0734c093469033a9547d5effd6f8ade5836541fbca25 4624 
ploop_1.15-4.debian.tar.xz
Files:
 798f5b0d9a80463510b0e218d29af06e 1899 libs optional ploop_1.15-4.dsc
 8d24b61f70268f3ba2dce6cd24aa65a8 4624 libs optional ploop_1.15-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAloYb5EACgkQiNJCh6LY
mLF/RRAAhVKaXBpKvpImSrtUrrsS3KI21dDzyhNHYgPTIx+y1/YG0p1FIYTJX86D
NZYgVbURAoaprMz1t24YHXR+jQ0yUI9JHBjk6rL4wwoJDi9hUL1Yt3OooGjADyDr
fTEPkoBlSCwpOeQYjwT1UArA0NnVFYrcFbbItCfQPZgUzf7goM146v1g9h0bAowj
Z14sstaCKOMZZUteUwn1W6wLZea6YwGRXMjdP+TKghM+hJ9zWRco4keClAGxPRCc
weqaRUV5qY8bmX8Jxy+C8CWGzAVkYtoL6LUC0ENBlRtjU+gCbQYUckxhVZeaBozt
gHm2f4sVmj0QvCBXaXBYgTmDkFnv22cJbsT6gLpESYlICTPTDbhJ6YO7iUAY0RRP
sd7UeC3pabcMu0AMK6/AK8VH9fqEDIo0hohorQ1zOT+9x6sf/vdSELao1YckPJJE
nMqR98iAaMOG38zdGIK6RtIyMawgR/cFeDX4awLjDyqYYz8DZvnENo0zD+Hrl1Bq
p1ZbT5InYlVSN6aq4cXKf1lNzOfvnZnPpBzFYyNOU4G8UC7w4nobzJW5O/g75RsL
Mu5S6YYHm+uz0d17tklpbobltWEN1cfayW/iby7tMa+gCbguutchckrjHPNi19A/
GOYXEQ1pc0s499Jwz7nFjnLRxgrja0gPvfyIRS5Z6kLHMZgBADQ=
=i+5E
-END PGP SIGNATURE End Message ---

Bug#882608: ruby-mechanize: FTBFS and Debci failure with ruby 2.3.5

[Adrian Bunk]

Source: ruby-mechanize
Version: 2.7.5-1
Severity: serious
Tags: buster sid

https://ci.debian.net/packages/r/ruby-mechanize/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-mechanize.html

...

┌──┐
│ Run tests for ruby2.3 from debian/ruby-test-files.yaml   │
└──┘

RUBYLIB=/build/1st/ruby-mechanize-2.7.5/debian/ruby-mechanize/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-mechanize/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
Run options: --seed 47730

# Running:

...DEPRECATED: Use assert_nil if 
expecting nil from 
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize_page_meta_refresh.rb:115. 
This will fail in Minitest 6.
...E..DEPRECATED: assert_send. From 
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize.rb:984
.F..E...EDEPRECATED: 
assert_send. From /build/1st/ruby-mechanize-2.7.5/test/test_mechanize.rb:946
..DEPRECATED: assert_send. From 
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize.rb:965
.DEPRECATED: Use assert_nil if 
expecting nil from 
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize_cookie.rb:461. This will 
fail in Minitest 6.
...DEPRECATED: Use assert_nil if expecting nil from 
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize_util.rb:30. This will fail 
in Minitest 6.
.DEPRECATED: Use assert_nil if expecting nil from 
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize_form_encoding.rb:70. This 
will fail in Minitest 6.
.DEPRECATED:
 Use assert_nil if expecting nil from 
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize_page_link.rb:342. This will 
fail in Minitest 6.
..DEPRECATED: Use assert_nil if expecting nil from 
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize_page_link.rb:75. This will 
fail in Minitest 6.
..

Finished in 1.713436s, 384.0237 runs/s, 1220.9387 assertions/s.

  1) Error:
TestMechanize#test_get_http_refresh_disabled:
ArgumentError: header field value cannnot include CR/LF
/usr/lib/ruby/2.3.0/net/http/header.rb:76:in `set_field'
/usr/lib/ruby/2.3.0/net/http/header.rb:41:in `[]='

/build/1st/ruby-mechanize-2.7.5/debian/ruby-mechanize/usr/lib/ruby/vendor_ruby/mechanize/test_case/http_refresh_servlet.rb:6:in
 `do_GET'

/build/1st/ruby-mechanize-2.7.5/debian/ruby-mechanize/usr/lib/ruby/vendor_ruby/mechanize/test_case.rb:234:in
 `request'
/usr/lib/ruby/vendor_ruby/net/http/persistent.rb:999:in `request'

/build/1st/ruby-mechanize-2.7.5/debian/ruby-mechanize/usr/lib/ruby/vendor_ruby/mechanize/http/agent.rb:274:in
 `fetch'

/build/1st/ruby-mechanize-2.7.5/debian/ruby-mechanize/usr/lib/ruby/vendor_ruby/mechanize.rb:464:in
 `get'
/build/1st/ruby-mechanize-2.7.5/test/test_mechanize.rb:614:in 
`test_get_http_refresh_disabled'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:839:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:311:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `each'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest.rb:337:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest.rb:309:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `block in __run'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `map'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `__run'

Bug#882537: biber FTBFS:

[Adrian Bunk]

On Fri, Nov 24, 2017 at 09:58:27AM +0900, Norbert Preining wrote:
> > # -  \\field{sortinithash}{f615fb9c6fba11c6f962fb3fd599810e}
> > # +  \\field{sortinithash}{07bbd5a529b5beaa311df5be05b874bc}
> 
> Yeah, usual mix up between libunicode-collate-perl as shipped with
> perl internally and with extra module.
> 
> Did you install libunicode-collate-perl package or used the perl
> internal provided?

The build log I linked to says:
  Unpacking libunicode-collate-perl (1.24-1) ...

> It is very unfortunate that perl provides a package but is not 100%
> compatible with it.
> 
> Norbert

cu
Adrian

-- 

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

Bug#882292: acpica-unix FTBFS on 32bit big endian: test failures

[James Cowgill]

Control: tags -1 patch

Hi,

On 23/11/17 18:01, James Cowgill wrote:
> On 21/11/17 07:28, Adrian Bunk wrote:
>> Begin compiling test package: [operand]
>> Begin compiling test package: [tests]
>> Begin compiling test package: [oarg]
>> Test path: 
>> /<>/tests/aslts/src/runtime/collections/complex/operand/tests/oarg
>> Type: nopt/32 Compile => Removing filesrm: cannot remove 'MAIN.asm': No 
>> such file or directory
>> rm: cannot remove 'MAIN.c': No such file or directory
>> rm: cannot remove 'MAIN.h': No such file or directory
>> rm: cannot remove 'MAIN.i': No such file or directory
>> rm: cannot remove 'MAIN.hex': No such file or directory
>> rm: cannot remove 'MAIN.lst': No such file or directory
>> rm: cannot remove 'MAIN.map': No such file or directory
>> rm: cannot remove 'MAIN.nsp': No such file or directory
>> rm: cannot remove 'MAIN.offset.h': No such file or directory
>> rm: cannot remove 'MAIN.src': No such file or directory
>>  => Done 
>> ls: cannot access 'oarg.aml': No such file or directory
>> mv: cannot stat 'oarg.aml': No such file or directory
>> Compiled test package: [oarg]
>> ...
>> WARNING: some test cases dont have AML code! (168)
>> ...
>> iASL: Segmentation Fault
> 
> I think this is caused by this in aslrules.y:
>> String
>> : PARSEOP_STRING_LITERAL{$$ = TrCreateValuedLeafOp 
>> (PARSEOP_STRING_LITERAL,
>> (ACPI_NATIVE_INT) 
>> AslCompilerlval.s);}
>> ;
> 
> Here we cast a (char*) to uint64.
> 
> In aslparseop.c we assign this uint64 into a union:
>> ACPI_PARSE_OBJECT *
>> TrCreateValuedLeafOp (
>> UINT32  ParseOpcode,
>> UINT64  Value)
>> {
>> ACPI_PARSE_OBJECT   *Op;
>>
>>
>> Op = TrAllocateOp (ParseOpcode);
>> Op->Asl.Value.Integer = Value;
> 
> This union us defined like this (aclocal.h):
>> typedef union acpi_parse_value
>> {
>> UINT64  Integer;/* Integer constant (Up 
>> to 64 bits) */
>> UINT32  Size;   /* bytelist or field 
>> size */
>> char*String;/* NULL terminated 
>> string */
>> UINT8   *Buffer;/* buffer or string */
>> char*Name;  /* NULL terminated 
>> string */
>> union acpi_parse_object *Arg;   /* arguments and 
>> contained ops */
>> ACPI_TAG_INFO   Tag;/* Resource descriptor 
>> tag info  */
>>
>> } ACPI_PARSE_VALUE;
> 
> On 32-bit big endian we end up putting the pointer into the _lower_ half
> of "Integer" which does not work when later reading from "String" (which
> will read from the _upper_ half).
> 
> I might have a go at getting a patch working for this. These bad casts
> make me despair :(

The attached patch works on mips. I didn't test the other failing
architectures.

Thanks,
James
--- a/source/compiler/aslparseop.c
+++ b/source/compiler/aslparseop.c
@@ -283,7 +283,16 @@ TrCreateValuedLeafOp (
 
 
 Op = TrAllocateOp (ParseOpcode);
-Op->Asl.Value.Integer = Value;
+if (ParseOpcode == PARSEOP_NAMESTRING ||
+ParseOpcode == PARSEOP_NAMESEG ||
+ParseOpcode == PARSEOP_STRING_LITERAL)
+{
+Op->Asl.Value.String = (char *) Value;
+}
+else
+{
+Op->Asl.Value.Integer = Value;
+}
 
 DbgPrint (ASL_PARSE_OUTPUT,
 "\nCreateValuedLeafOp  Ln/Col %u/%u NewOp %p  "
--- a/source/include/platform/aclinux.h
+++ b/source/include/platform/aclinux.h
@@ -225,10 +225,8 @@
 #endif
 
 #if __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__
-#if defined(__PPC64__) || defined(__s390x__)
 #define ACPI_BIG_ENDIAN
 #endif
-#endif
 
 #endif /* __KERNEL__ */
 


signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#882292: acpica-unix FTBFS on 32bit big endian: test failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #882292 [src:acpica-unix] acpica-unix FTBFS on 32bit big endian: test 
failures
Added tag(s) patch.

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

Processed: libspdlog-dev: spdlog/fmt/bundled/format.h not usable with glibc 2.25

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:rapmap
Bug #882606 [libspdlog-dev] libspdlog-dev: spdlog/fmt/bundled/format.h not 
usable with glibc 2.25
Added indication that 882606 affects src:rapmap

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

Bug#882606: libspdlog-dev: spdlog/fmt/bundled/format.h not usable with glibc 2.25

[Adrian Bunk]

Package: libspdlog-dev
Version: 1:0.11.0-3
Severity: serious
Tags: fixed-upstream
Forwarded: https://github.com/gabime/spdlog/issues/300
Control: affects -1 src:rapmap

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

...
/usr/include/spdlog/fmt/bundled/format.h: In member function 'void 
fmt::internal::ArgFormatterBase::visit_char(int)':
/usr/include/spdlog/fmt/bundled/format.h:2236:24: error: expected 
unqualified-id before numeric constant
 const unsigned CHAR_WIDTH = 1;
^


This seems to be fixed in spdlog 0.12.0

Bug#882605: uima-as FTBFS without libcommons-net-java

[Adrian Bunk]

Source: uima-as
Version: 2.3.1-6
Severity: serious

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

...
[INFO] 
[INFO] 
[INFO] Skipping UIMA-AS: uima-as
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] UIMA-AS: uima-as-parent  SUCCESS [  1.154 s]
[INFO] UIMA-AS: uimaj-as-core . SUCCESS [ 13.964 s]
[INFO] UIMA-AS: uimaj-as-jms .. SUCCESS [  4.314 s]
[INFO] UIMA-AS: uimaj-as-activemq . FAILURE [  0.093 s]
[INFO] UIMA AS: uimaj-as-osgi-runtime . SKIPPED
[INFO] UIMA-AS Aggregate: aggregate-uima-as-eclipse-plugins SKIPPED
[INFO] UIMA-AS Aggregate: aggregate-uima-as ... SKIPPED
[INFO] UIMA-AS: uima-as ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 20.193 s
[INFO] Finished at: 2018-12-27T02:55:37-12:00
[INFO] Final Memory: 29M/877M
[INFO] 
[ERROR] Failed to execute goal on project uimaj-as-activemq: Could not resolve 
dependencies for project org.apache.uima:uimaj-as-activemq:jar:2.3.1: Cannot 
access eclipsePlugins (http://repo1.maven.org/eclipse) in offline mode and the 
artifact commons-net:commons-net:jar:debian has not been downloaded from it 
before. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :uimaj-as-activemq
dh_auto_build: cd uima-as && /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/uima-as-2.3.1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/uima-as-2.3.1/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/uima-as-2.3.1/debian 
-Dmaven.repo.local=/build/1st/uima-as-2.3.1/debian/maven-repo --batch-mode 
package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true 
-Dlocale=en_US returned exit code 1
debian/rules:9: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1


The bug might be missing dependency on libcommons-net-java
in a build dependency.

Bug#882248: marked as done (sympathy FTBFS with glibc 2.25)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 16:34:07 +
with message-id 
and subject line Bug#882248: fixed in sympathy 1.2.1+woking+cvs+git20171124
has caused the Debian Bug report #882248,
regarding sympathy FTBFS with glibc 2.25
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.)


-- 
882248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sympathy
Version: 1.2.1+woking+cvs+git20161222
Severity: serious
Tags: buster sid

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

...
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -g -Werror -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
libsympathy_a-lockfile.o `test -f 'lockfile.c' || echo './'`lockfile.c
lockfile.c: In function 'lockfile_add_name_from_dev':
lockfile.c:317:13: error: In the GNU C Library, "major" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "major", include 
 directly. If you did not intend to use a system-defined macro
 "major", you should undefine it after including . [-Werror]
   sprintf (buf, "LCK.%03d.%03d", major (dev), minor (dev));
 ^~~



 
lockfile.c:317:13: error: In the GNU C Library, "minor" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "minor", include 
 directly. If you did not intend to use a system-defined macro
 "minor", you should undefine it after including . [-Werror]
   sprintf (buf, "LCK.%03d.%03d", major (dev), minor (dev));
 ^~~



 
cc1: all warnings being treated as errors
Makefile:988: recipe for target 'libsympathy_a-lockfile.o' failed
make[3]: *** [libsympathy_a-lockfile.o] Error 1
--- End Message ---
--- Begin Message ---
Source: sympathy
Source-Version: 1.2.1+woking+cvs+git20171124

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated sympathy 
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: Fri, 24 Nov 2017 16:11:35 +
Source: sympathy
Binary: sympathy
Architecture: source
Version: 1.2.1+woking+cvs+git20171124
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Description:
 sympathy   - serial port concentrator system - server/client program
Closes: 882248
Changes:
 sympathy (1.2.1+woking+cvs+git20171124) unstable; urgency=medium
 .
   * #include  to fix FTBFS.  Closes:#882248.
Checksums-Sha1:
 78b0e51d3c29733752b10fcf074b9fec12f717e9 1355 
sympathy_1.2.1+woking+cvs+git20171124.dsc
 9fa0e1af4d40a9c62527f600ffe95abdd7f65819 285146 
sympathy_1.2.1+woking+cvs+git20171124.tar.gz
Checksums-Sha256:
 7169737784c54865144d620b3e391df2c6a988d6c76bf4a3070423f937fb7d01 1355 
sympathy_1.2.1+woking+cvs+git20171124.dsc
 c29a2f57808bdfa3997af3e472324ffa81b1c984823d6714b97fb91c092a0114 285146 
sympathy_1.2.1+woking+cvs+git20171124.tar.gz
Files:
 62f51c3883a813de83f7f43c6bd9bfb3 1355 comm optional 
sympathy_1.2.1+woking+cvs+git20171124.dsc
 e883e329302e9f5428df9a754ec88c93 285146 comm 

Bug#868059: marked as done (tc: m_xt: Segfault with iptables-1.6.0)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 16:32:08 +
with message-id 
and subject line Bug#868059: fixed in iproute2 4.9.0-1+deb9u1
has caused the Debian Bug report #868059,
regarding tc: m_xt: Segfault with iptables-1.6.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.)


-- 
868059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iproute2
Version: 4.9.0-1
Severity: normal
Tags: patch

# tc qdisc add dev enp0s3 ingress
# tc filter add dev enp0s3 parent : protocol ip u32 match u32 0 0 flowid 
1:1 action xt -j MARK  --set-mark 0xa
Segmentation fault

This is a known and corrected bug in the mainstream.
See:
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?h=v4.10.0=97a02cabefb2e2dcfe27f89943709afa84be5525

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

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

Versions of packages iproute2 depends on:
ii  libc62.24-11+deb9u1
ii  libdb5.3 5.3.28-12+b1
ii  libelf1  0.168-1
ii  libmnl0  1.0.4-2
ii  libselinux1  2.6-3+b1

Versions of packages iproute2 recommends:
pn  libatm1   
ii  libxtables12  1.6.0+snapshot20161117-6

Versions of packages iproute2 suggests:
pn  iproute2-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: iproute2
Source-Version: 4.9.0-1+deb9u1

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

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated iproute2 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: Fri, 24 Nov 2017 09:22:10 +
Source: iproute2
Binary: iproute2 iproute2-doc iproute iproute-doc
Architecture: source
Version: 4.9.0-1+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian iproute2 Maintainers 
Changed-By: Cyril Brulebois 
Description:
 iproute- transitional dummy package for iproute2
 iproute-doc - transitional dummy package for iproute2-doc
 iproute2   - networking and traffic control tools
 iproute2-doc - networking and traffic control tools - documentation
Closes: 868059
Changes:
 iproute2 (4.9.0-1+deb9u1) stretch; urgency=medium
 .
   * Backport upstream commit 97a02cabef to fix segfault with iptables 1.6;
 the xtables_globals structure needs to have its new member compat_rev
 initialized. (Closes: #868059)
   * Sync include/xtables.h from iptables to make sure the right offset is
 used when accessing structure members defined in libxtables. One could
 get “Extension does not know id …” otherwise. (See also: #868059)
Checksums-Sha1:
 5db793c57f00571746a19e480f51ba05d96fee29 2425 iproute2_4.9.0-1+deb9u1.dsc
 0be548a4b42e093127b01d44ea07d1d2e6004063 28316 
iproute2_4.9.0-1+deb9u1.debian.tar.xz
 d8ef094d45dd8ac9583ce58928ed9792a7398efa 8531 
iproute2_4.9.0-1+deb9u1_source.buildinfo
Checksums-Sha256:
 ad3365cc61f116f8dc8cc2a615549ffc9ed0217223393078b68e1d96649b2ce7 2425 
iproute2_4.9.0-1+deb9u1.dsc
 c5056293c85daf0a96550c0bfa6ae2851c78cec4ed5932909c976607caa1e561 28316 
iproute2_4.9.0-1+deb9u1.debian.tar.xz
 ec4ab63e859090b39812120079af797c51f3d05c8342b6c4de9b60a83edebfe7 8531 
iproute2_4.9.0-1+deb9u1_source.buildinfo
Files:
 e4e3c920ab004caceefd53b39144f0f3 2425 net optional iproute2_4.9.0-1+deb9u1.dsc
 6bdd99cb846afa0c42abe0a4968057f9 28316 net optional 
iproute2_4.9.0-1+deb9u1.debian.tar.xz
 bfef50c12c96470b2d4c69200a0d8556 8531 net optional 
iproute2_4.9.0-1+deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAloX+h8ACgkQ/5FK8MKz

Processed: Re: Bug#882598: libavutil55: segfault after upgrade

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #882598 [libavutil55] libavutil55: segfault after upgrade
Severity set to 'grave' from 'normal'
> retitle -1 libavutil55: ABI broken by "add vector_dmac_scalar()"
Bug #882598 [libavutil55] libavutil55: segfault after upgrade
Changed Bug title to 'libavutil55: ABI broken by "add vector_dmac_scalar()"' 
from 'libavutil55: segfault after upgrade'.
> forwarded -1 https://trac.ffmpeg.org/ticket/6861
Bug #882598 [libavutil55] libavutil55: ABI broken by "add vector_dmac_scalar()"
Set Bug forwarded-to-address to 'https://trac.ffmpeg.org/ticket/6861'.
> tag -1 - moreinfo
Bug #882598 [libavutil55] libavutil55: ABI broken by "add vector_dmac_scalar()"
Removed tag(s) moreinfo.
> found -1 7:3.4-1
Bug #882598 [libavutil55] libavutil55: ABI broken by "add vector_dmac_scalar()"
Marked as found in versions ffmpeg/7:3.4-1.

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

Bug#882033: libpmi2-0-dev,libpmix-dev: error when trying to install together: both ship libpmi2.so

[Alastair McKinstry]

On 23/11/2017 16:05, Andreas Beckmann wrote:
> On 2017-11-23 16:28, Alastair McKinstry wrote:
>> There are three _implementations_ of the Process Management Interface
>> (PMI): the Slurm one, the OpenMPI ("PMix") and the MPICH one.  They are
>> all expected to have the same ABI.
>> Unlike jpeg, the three implementations will converge on the SOVERSION(s)
>> as they are in the agreed ABI.
>> Hence we will have differing behaviours with libraries with the same name.
> Which is *not* the case now, as they have different SOVERSIONs currently
> (slurm:0, pmix:1, mpich:?nosharedlib?), so you shouldn't use
> alternatives to mix them *now*.
alternatives need not be implemented now (and so won't be, to mimimize
code to debug), but file layout would be done
to make alternatives trivial.
That is, the prefix for pmix pmi libs and includes will be
/usr/lib/${multiarch}/pmi/{include, lib}
with a symlink for the library
/usr/lib/${multiarch}/libpmi.so.2.1.3 ->
/usr/lib/${multiarch}/pmi/lib/libpmi.so.2.1.3


>> Currently we have three possible 'users' of PMI: SLURM and the two MPI
>> implementations, OpenMPI and MPICH.
>> Each can be configured to use either its 'own' PMI or another; the
>> libraries do the same thing but can have
>> different implementation behaviours, (eg. MPICH calls its version
>> 'simple' while PMIX from OpenMPI aims to scale well at ~10^6 processes).
>>
>> Its a realistic use case then to ship a simple PMI as default, but also
>> allow another high-performance version to be available via alternatives,
>> switchable at runtime.
> In that case you would still only need one -dev package, that can be
> used with the different implementations. Or does each one have different
> "extensions" beyond the common API subset?
We currently ship a static libpmi.a in the -dev package; this would be
different in each implementation, so a different
-dev is still needed.
> BTW, how do you plan to do library alternatives in multiarch? Keep them
> in sync? How? or Why not?
See for example blas and lapack, which are in the same situation. The
alternatives file in /etc/alternatives has the multiarch extension
attached, eg.; liblapack.a-x86_64-linux-gnu

> Andreas
Alastair

-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Commander Vimes didn’t like the phrase “The innocent have nothing to fear,”
 believing the innocent had everything to fear, mostly from the guilty but in 
the longer term
 even more from those who say things like “The innocent have nothing to fear.”
 - T. Pratchett, Snuff

Bug#881453: marked as done (primesieve FTBFS on i386: test failures)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 15:07:19 +
with message-id 
and subject line Bug#881453: fixed in primesieve 6.3+ds-1
has caused the Debian Bug report #881453,
regarding primesieve FTBFS on i386: test failures
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.)


-- 
881453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: primesieve
Version: 6.2+ds-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/fetch.php?pkg=primesieve=i386=6.2%2Bds-1=1510442732=0

...
   dh_auto_test -a -O--builddirectory=_build
cd _build && make -j4 test ARGS\+=-j4
make[1]: Entering directory '/<>/primesieve-6.2+ds/_build'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j4
Test project /<>/primesieve-6.2+ds/_build
  Start  1: atomic
  Start  2: count_primes1
  Start  3: count_primes2
  Start  4: count_primes3
 1/24 Test  #1: atomic ...   Passed0.28 sec
 2/24 Test  #2: count_primes1    Passed0.30 sec
  Start  5: count_quadruplets
  Start  6: count_quintuplets
 3/24 Test  #5: count_quadruplets    Passed0.90 sec
 4/24 Test  #6: count_quintuplets    Passed1.08 sec
  Start  7: count_sextuplets
  Start  8: count_triplets
 5/24 Test  #8: count_triplets ...   Passed0.89 sec
 6/24 Test  #7: count_sextuplets .   Passed1.11 sec
  Start  9: count_twins
  Start 10: cpu_info
 7/24 Test #10: cpu_info .   Passed0.31 sec
  Start 11: floorPow2
 8/24 Test #11: floorPow2 ***Failed0.21 sec
floorPow2(1) = 1   OK
floorPow2(2) = 2   OK
floorPow2(3) = 2   OK
floorPow2(4) = 4   OK
floorPow2(5) = 4   OK
floorPow2(6) = 4   OK
floorPow2(7) = 4   OK
floorPow2(8) = 8   ERROR

  Start 12: generate_n_primes1
 9/24 Test  #9: count_twins ..   Passed0.94 sec
  Start 13: generate_primes1
10/24 Test #13: generate_primes1 .   Passed0.30 sec
  Start 14: ilog2
11/24 Test #14: ilog2 ***Failed0.30 sec
ilog2(1) = 0   OK
ilog2(2) = 1   OK
ilog2(3) = 1   OK
ilog2(4) = 2   OK
ilog2(5) = 2   OK
ilog2(6) = 2   OK
ilog2(7) = 2   OK
ilog2(8) = 3   ERROR

  Start 15: isqrt
12/24 Test #15: isqrt    Passed0.89 sec
  Start 16: next_prime1
13/24 Test #16: next_prime1 ..   Passed3.21 sec
  Start 17: nth_prime1
14/24 Test #17: nth_prime1 ...   Passed3.52 sec
  Start 18: nth_prime2
15/24 Test #12: generate_n_primes1 ...   Passed   15.50 sec
  Start 19: nth_prime3
16/24 Test  #3: count_primes2    Passed   22.85 sec
  Start 20: prev_prime1
17/24 Test #18: nth_prime2 ...   Passed   16.06 sec
  Start 21: generate_n_primes2
18/24 Test #21: generate_n_primes2 ...   Passed0.61 sec
  Start 22: generate_primes2
19/24 Test  #4: count_primes3    Passed   29.38 sec
  Start 23: next_prime2
20/24 Test #19: nth_prime3 ...   Passed   23.31 sec
  Start 24: prev_prime2
21/24 Test #20: prev_prime1 ..   Passed   22.00 sec
22/24 Test #24: prev_prime2 ..   Passed3.24 sec
23/24 Test #22: generate_primes2 .   Passed   19.13 sec
24/24 Test #23: next_prime2 ..   Passed   21.86 sec

92% tests passed, 2 tests failed out of 24

Total Test time (real) =  51.51 sec

The following tests FAILED:
 11 - floorPow2 (Failed)
 14 - ilog2 (Failed)
Errors while running CTest
Makefile:121: recipe for target 'test' failed
make[1]: *** [test] Error 8


This can be fixed with:

--- debian/rules.old2017-11-12 00:16:05.0 +
+++ debian/rules2017-11-12 00:17:52.0 +
@@ -17,6 +17,11 @@
CXXFLAGS := $(subst -O2,-O3,$(CXXFLAGS))
 endif
 
+ifeq ($(DEB_HOST_ARCH),i386)
+CFLAGS   += -ffloat-store
+CXXFLAGS += -ffloat-store
+endif
+
 default:
@uscan --no-conf --dehs --report || true
 
--- End Message ---
--- Begin Message ---
Source: primesieve
Source-Version: 6.3+ds-1

We believe that the bug you reported is fixed in the latest version of
primesieve, 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 

Bug#881678: marked as done (primesieve: FTBFS: __atomic_fetch_add_8 undefined)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 15:07:19 +
with message-id 
and subject line Bug#881678: fixed in primesieve 6.3+ds-1
has caused the Debian Bug report #881678,
regarding primesieve: FTBFS: __atomic_fetch_add_8 undefined
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.)


-- 
881678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: primesieve
Version: 6.2+ds-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Builds of primesieve for armel, mips, mipsel, and the non-release
architectures m68k, powerpc, powerpcspe, and sh4 have started failing:

  libprimesieve.so.8.2.0: undefined reference to `__atomic_fetch_add_8'
  collect2: error: ld returned 1 exit status

On these architectures, you should be able to find this symbol in
libatomic.  I'd suggest linking with -Wl,--as-needed -latomic
everywhere so that you don't have to special-case any platforms or get
formal dependencies on libatomic on the platforms that don't need it
here.

Could you please take a look?

Thanks!

--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: primesieve
Source-Version: 6.3+ds-1

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated primesieve 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, 24 Nov 2017 13:51:00 +
Source: primesieve
Binary: primesieve libprimesieve8 libprimesieve-dev libprimesieve-dev-common 
primesieve-bin primesieve-doc
Architecture: source
Version: 6.3+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jerome Benoit 
Description:
 libprimesieve-dev - fast prime number generator C/C++ library -- libdev
 libprimesieve-dev-common - fast prime number generator C/C++ library -- headers
 libprimesieve8 - fast prime number generator C/C++ library -- lib
 primesieve - fast prime number generator C/C++ library
 primesieve-bin - fast prime number generator C/C++ library -- bin
 primesieve-doc - fast prime number generator C/C++ library -- doc
Closes: 881453 881678
Changes:
 primesieve (6.3+ds-1) unstable; urgency=medium
 .
   * New upstream minor release (Closes: #881453, #881678).
   * Debianization:
 - debian/rules, simplify;
 - debian/patches/*:
   - d/p/upstream-fix-cmake_machinery-libatomic.patch, introduce.
Checksums-Sha1:
 2b344c4754ecc529ed278bf682b1c8b65840a202 3192 primesieve_6.3+ds-1.dsc
 0aa557076ee741b1ef70b2c85334e99a1c130728 126516 primesieve_6.3+ds.orig.tar.xz
 2d8d9718de98e96e5ef1e6f8f6bf78f7a464ab27 6336 primesieve_6.3+ds-1.debian.tar.xz
 695c22cdb5b5e6ed53c955ef3f567e7b9bbce88c 6858 
primesieve_6.3+ds-1_source.buildinfo
Checksums-Sha256:
 fcac12a997b857dce4ac06159d96cacdae72bea2e3ec5300a34723ce3da8398a 3192 
primesieve_6.3+ds-1.dsc
 c5f746c7d21003a322ce92897d7d4bae609719813d1b642c7c56f85fc20e9ca0 126516 
primesieve_6.3+ds.orig.tar.xz
 8eab9f92af4c7069fe3f9b5e2589c35e027b0ccb037c7c988db8a8a1a11cec6b 6336 
primesieve_6.3+ds-1.debian.tar.xz
 3a4460b538688179c0d32b3eaa7c609946df2431dfceab1a06244393b38f4f25 6858 
primesieve_6.3+ds-1_source.buildinfo
Files:
 d0fd6cc5535f98e0dabfb33241d8c729 3192 math optional primesieve_6.3+ds-1.dsc
 fb13d211f322480f5c7a2001debbfc71 126516 math optional 
primesieve_6.3+ds.orig.tar.xz
 d1c16dcd871465ce726034b0f8b5d8d0 6336 math optional 
primesieve_6.3+ds-1.debian.tar.xz
 1cbdbe3e0079a248d7a0f5264ead55d3 6858 math optional 
primesieve_6.3+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAloYJNsVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLQicf/2bugha+y7X3K2ZUsUdpnuVj7DkV

Bug#882589: marked as done (maven-common-artifact-filters FTBFS: The following artifacts could not be resolved: org.eclipse.aether:aether-api:jar:debian, org.eclipse.aether:aether-util:jar:debian)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 13:38:06 +
with message-id 
and subject line Bug#882589: fixed in maven-common-artifact-filters 3.0.1-2
has caused the Debian Bug report #882589,
regarding maven-common-artifact-filters FTBFS: The following artifacts could 
not be resolved: org.eclipse.aether:aether-api:jar:debian, 
org.eclipse.aether:aether-util:jar:debian
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.)


-- 
882589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maven-common-artifact-filters
Version: 3.0.1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/maven-common-artifact-filters.html

...
[INFO] 
[INFO] 
[INFO] Skipping Apache Maven Common Artifact Filters
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 1.102 s
[INFO] Finished at: 2018-12-27T04:14:10-12:00
[INFO] Final Memory: 19M/724M
[INFO] 
[ERROR] Failed to execute goal on project maven-common-artifact-filters: Could 
not resolve dependencies for project 
org.apache.maven.shared:maven-common-artifact-filters:jar:3.0.1: The following 
artifacts could not be resolved: org.eclipse.aether:aether-api:jar:debian, 
org.eclipse.aether:aether-util:jar:debian: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.eclipse.aether:aether-api:jar:debian has not been downloaded from it 
before. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/maven-common-artifact-filters-3.0.1
 -Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/maven-common-artifact-filters-3.0.1/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/maven-common-artifact-filters-3.0.1/debian 
-Dmaven.repo.local=/build/1st/maven-common-artifact-filters-3.0.1/debian/maven-repo
 --batch-mode package javadoc:jar javadoc:aggregate -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
--- End Message ---
--- Begin Message ---
Source: maven-common-artifact-filters
Source-Version: 3.0.1-2

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated 
maven-common-artifact-filters 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, 24 Nov 2017 14:21:42 +0100
Source: maven-common-artifact-filters
Binary: libmaven-common-artifact-filters-java 
libmaven-common-artifact-filters-java-doc
Architecture: source
Version: 3.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libmaven-common-artifact-filters-java - Maven Common Artifact Filters
 

Processed: Pending fixes for bugs in the maven-common-artifact-filters package

[Debian Bug Tracking System]

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

> tag 882589 + pending
Bug #882589 [src:maven-common-artifact-filters] maven-common-artifact-filters 
FTBFS: The following artifacts could not be resolved: 
org.eclipse.aether:aether-api:jar:debian, 
org.eclipse.aether:aether-util:jar:debian
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882589: Pending fixes for bugs in the maven-common-artifact-filters package

[pkg-java-maintainers]

tag 882589 + pending
thanks

Some bugs in the maven-common-artifact-filters package are closed in
revision de421b18644623048da5c894735880774b04184e in branch 'master'
by Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/maven-common-artifact-filters.git/commit/?id=de421b1

Commit message:

Fixed the build failure caused by the removal of eclipse-aether (Closes: 
#882589)

Bug#882528: marked as done (dealer: test hang on architectures where char is unsigned)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 12:33:38 +
with message-id 
and subject line Bug#882528: fixed in dealer 20161012-3
has caused the Debian Bug report #882528,
regarding dealer: test hang on architectures where char is unsigned
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.)


-- 
882528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dealer
Version: 20161012-2
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
./dealer -s 1 Examples/Descr.6c | tee test.out
E: Build killed with signal TERM after 150 minutes of inactivity
--- End Message ---
--- Begin Message ---
Source: dealer
Source-Version: 20161012-3

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated dealer 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: Fri, 24 Nov 2017 13:09:15 +0100
Source: dealer
Binary: dealer
Architecture: source
Version: 20161012-3
Distribution: unstable
Urgency: medium
Maintainer: Christoph Berg 
Changed-By: Christoph Berg 
Description:
 dealer - bridge hand generator
Closes: 882528
Changes:
 dealer (20161012-3) unstable; urgency=medium
 .
   * Team upload.
   * Fix infinite loop on architectures where char is unsigned, thanks to
 Adrian Bunk for the initial hint! (Closes: #882528)
Checksums-Sha1:
 ea01c7b1e971304b5d223f15526d800027f5b6b2 1909 dealer_20161012-3.dsc
 18efc7885ed5b84b087b5631e699c7126e850631 8136 dealer_20161012-3.debian.tar.xz
 d912ff6794e5f16cfeee9dac255007f3d9651716 5192 
dealer_20161012-3_source.buildinfo
Checksums-Sha256:
 0452e7d2a4869a03ccd446d204d007ed4b7b9311d20b9fa5bd081a02b85e4968 1909 
dealer_20161012-3.dsc
 f36af2e76d966dab4a6b7b66287bf9ff2a7e92594c4e13047c6d6d7ff6c3610c 8136 
dealer_20161012-3.debian.tar.xz
 bf357384efb6e0e604a06a6902a236d61ac1c605ab9ef665727888484d7a 5192 
dealer_20161012-3_source.buildinfo
Files:
 1f6770a8cb76d52eb23ee32239e45da6 1909 games optional dealer_20161012-3.dsc
 69b45b8dec874ada2fffe49cea57c638 8136 games optional 
dealer_20161012-3.debian.tar.xz
 820ce759c8a233fea4bb0fa8d2b5a1cd 5192 games optional 
dealer_20161012-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAloYDUYACgkQTFprqxLS
p67fYRAApvdw/GDzeg5KAU/13TpxPFGNCHe2DmxHShx03zjEE58WGCyDFJGq5wpf
R5WQ+lNANgAQxzsmwUK9ppIqUiTXm7/Xbb6JGF/Kf39F4lzrRikIVOabAr4WJ41P
zaYFWkkpYapPscRK3KiP47m1qu82aqAApSbkUosyA/VuhinHXFVM6Fxpnu66gNrw
ywDLxRgCqeoxC1ywSr5Co/Uk7Tr5LnLYp1JT6FDeBvgzyM311E4NakcSbX7AZiwH
Dj9llBs+ildkF02MaUYelVFzvrHhanBuEOqD/hL0R1kJZnvZ6PdO/AQa4W378YaJ
rXtWlhKkpks6nKMj8qvYH1TtXWjX5DbEFarE8mfUNwh8ZnwGcbNz5kG9/rNoHW2J
7ythCNMjeT0zBzbsWuqxrh3O9QnaH8CNK8gKMoe3FAZivbhQYXbYfwE2yIxncHy7
mNKnWZLmQF8XPrXqy1MOSoFbG6kfYWzNV2BB88r9c5CfmNPhc2Pt27dgskWvALE9
4sjaPB3Fatv/vvrzRi1eT6dZiQ8hzGWcocP9FFMb5C5QJowk4hu5ejtiekh1B7rS
sBzbS4WXWMAM0IFKTIUsymeH7xuEqToYUQlhsd9lH+40Tt6YYxybgCutL55V8LxY
XWQwvdDPF/eQZSHlRHr3eE5RLRafsBzRPgv/4RA92YLo1z5kokQ=
=9kPs
-END PGP SIGNATURE End Message ---

Bug#881332: marked as done (django-auth-ldap FTBFS with mockldap 0.3.0)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 11:33:44 +
with message-id 
and subject line Bug#881332: fixed in django-auth-ldap 1.3.0-1
has caused the Debian Bug report #881332,
regarding django-auth-ldap FTBFS with mockldap 0.3.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.)


-- 
881332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-auth-ldap
Version: 1.2.15-1
Severity: serious

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

...
==
FAIL: test_populate_with_attrlist (django_auth_ldap.tests.LDAPTest)
--
Traceback (most recent call last):
  File "/build/1st/django-auth-ldap-1.2.15/django_auth_ldap/tests.py", line 
692, in test_populate_with_attrlist
self.assertEqual(user.first_name, 'Alice')
AssertionError: u'' != 'Alice'

--
Ran 79 tests in 0.640s

FAILED (failures=1, skipped=2)
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
Destroying test database for alias 'default'...
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: 
PYTHONPATH=. python2.7 /build/1st/django-auth-ldap-1.2.15/test/manage.py test 
django_auth_ldap
dh_auto_test: pybuild --test -i python{version} -p 2.7 --system=custom 
"--test-args=PYTHONPATH=. {interpreter} {dir}/test/manage.py test 
django_auth_ldap" returned exit code 13
debian/rules:18: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: django-auth-ldap
Source-Version: 1.3.0-1

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated django-auth-ldap 
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, 24 Nov 2017 12:17:08 +0100
Source: django-auth-ldap
Binary: python-django-auth-ldap python-django-auth-ldap-doc 
python3-django-auth-ldap
Architecture: source all
Version: 1.3.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-auth-ldap - Django LDAP authentication backend (Python2 version)
 python-django-auth-ldap-doc - Django LDAP authentication backend 
(documentation)
 python3-django-auth-ldap - Django LDAP authentication backend (Python3 version)
Closes: 881332
Changes:
 django-auth-ldap (1.3.0-1) unstable; urgency=low
 .
   * New upstream release (Closes: #881332).
   * Move upstream signing key to debian/upstream/signing-key.asc.
   * Refresh patches.
   * Update test runner to work with upstream changes (no more
 manage.py).
   * Bump Standards-Version to 4.1.1.
   * Run wrap-and-sort -bast to reduce diff size of future changes.
   * Enable autopkgtest-pkg-python testsuite.
   * Use https:// for uscan URL.
Checksums-Sha1:
 55d721fef6c96c0cd131488c88497ab7f6f0141e 2172 django-auth-ldap_1.3.0-1.dsc
 37c462825cd2b870dd9c2817fdbd617272b6dab1 108516 
django-auth-ldap_1.3.0.orig.tar.gz
 2feb9d5b2b6b995a8239edc5124b021eda8158b7 12452 
django-auth-ldap_1.3.0-1.debian.tar.xz
 565b1208e9323c1a4993ab2375bcbe970f72c4ab 8821 
django-auth-ldap_1.3.0-1_amd64.buildinfo
 d71b8b6e3d93c10cd9f9e5ee6ad00c0c0ea725bf 51540 
python-django-auth-ldap-doc_1.3.0-1_all.deb
 c63e3188a2703a8bc12c084aa9ff4af3ad766a1c 22124 
python-django-auth-ldap_1.3.0-1_all.deb
 b53c91ce3ef5ce79ca7b028d358c8f389766bd48 22188 
python3-django-auth-ldap_1.3.0-1_all.deb
Checksums-Sha256:
 530ded27231cc27ba8c07829ff43b96f7e61b4e3a139722744fb9178cd4cd1f5 2172 
django-auth-ldap_1.3.0-1.dsc
 71587d28e43d0292f825c6f9ba1257eb4acaa84f8453296e9979416629548f73 108516 

Bug#881332: marked as pending

[Michael Fladischer]

tag 881332 pending
thanks

Hello,

Bug #881332 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/python-modules/packages/django-auth-ldap.git/commit/?id=93af52f

---
commit 93af52fabd8f00d71ad7164b4d381a83915b3194
Author: Michael Fladischer 
Date:   Fri Nov 24 12:18:07 2017 +0100

Upload to unstable (Closes: #881332).

diff --git a/debian/changelog b/debian/changelog
index 8a93cc2..0a0a4dd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,6 @@
-django-auth-ldap (1.3.0-1) UNRELEASED; urgency=low
+django-auth-ldap (1.3.0-1) unstable; urgency=low
 
-  * New upstream release.
+  * New upstream release (Closes: #881332).
   * Move upstream signing key to debian/upstream/signing-key.asc.
   * Refresh patches.
   * Update test runner to work with upstream changes (no more
@@ -10,7 +10,7 @@ django-auth-ldap (1.3.0-1) UNRELEASED; urgency=low
   * Enable autopkgtest-pkg-python testsuite.
   * Use https:// for uscan URL.
 
- -- Michael Fladischer   Fri, 24 Nov 2017 10:59:09 +0100
+ -- Michael Fladischer   Fri, 24 Nov 2017 12:17:08 +0100
 
 django-auth-ldap (1.2.15-1) unstable; urgency=low
 

Processed: Bug#881332 marked as pending

[Debian Bug Tracking System]

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

> tag 881332 pending
Bug #881332 [src:django-auth-ldap] django-auth-ldap FTBFS with mockldap 0.3.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Version tracking fix

[Debian Bug Tracking System]

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

> notfound 882592 1.6.3-1
Bug #882592 [libinput10] libinput10: Trackpad behaves erratic after upgrade to 
1.9.2-1, after rolling back to 1.6.3-1 the trackpad works fine.
No longer marked as found in versions libinput/1.6.3-1.
> found 882592 1.9.2-1
Bug #882592 [libinput10] libinput10: Trackpad behaves erratic after upgrade to 
1.9.2-1, after rolling back to 1.6.3-1 the trackpad works fine.
Marked as found in versions libinput/1.9.2-1.
> thanks
Stopping processing here.

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

Bug#882370: marked as done (otrs2: CVE-2017-16664: OSA-2017-07: privilege escalation)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 11:02:07 +
with message-id 
and subject line Bug#882370: fixed in otrs2 5.0.16-1+deb9u3
has caused the Debian Bug report #882370,
regarding otrs2: CVE-2017-16664: OSA-2017-07: privilege escalation
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.)


-- 
882370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: otrs2
Version: 3.3.9-1
Severity: grave
Tags: patch security upstream fixed-upstream

Hi,

the following vulnerability was published for otrs2.

CVE-2017-16664[0]:
| Code injection exists in Kernel/System/Spelling.pm in Open Ticket
| Request System (OTRS) 5 before 5.0.24, 4 before 4.0.26, and 3.3 before
| 3.3.20. In the agent interface, an authenticated remote attackeer can
| execute shell commands as the webserver user via URL manipulation.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-16664
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16664
[1] 
https://www.otrs.com/security-advisory-2017-07-security-update-otrs-framework/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: otrs2
Source-Version: 5.0.16-1+deb9u3

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated otrs2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Nov 2017 15:16:23 +0100
Source: otrs2
Binary: otrs2 otrs
Architecture: source all
Version: 5.0.16-1+deb9u3
Distribution: stretch-security
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 otrs   - Open Ticket Request System (OTRS 5)
 otrs2  - Open Ticket Request System
Closes: 882370
Changes:
 otrs2 (5.0.16-1+deb9u3) stretch-security; urgency=high
 .
   * Add patch 17-CVE-2017-16664:
 This fixes OSA-2017-07, also known as CVE-2017-16664: An attacker who is
 logged into OTRS as an agent can request special URLs from OTRS which can
 lead to the execution of shell commands with the permissions of the web
 server user.
 Closes: #882370
Checksums-Sha1:
 302bea080cc1a77886e2b4ecd627f382d2bdfde8 1838 otrs2_5.0.16-1+deb9u3.dsc
 898049f899bd8859fa2c17df1bc4ec2bc13c614c 49600 
otrs2_5.0.16-1+deb9u3.debian.tar.xz
 7c17549665d3808200bfc3107800b17f8255d89c 7052652 otrs2_5.0.16-1+deb9u3_all.deb
 b4fc5e5e50c747594e3bc73fe7a106e4a1571168 7244 
otrs2_5.0.16-1+deb9u3_amd64.buildinfo
 97da148da8d1b6fe7db6004b827618ca6b17fe27 213116 otrs_5.0.16-1+deb9u3_all.deb
Checksums-Sha256:
 9effda6496f6f98f42a43a0b4eeaf458d6e4f1b9e185e8e036d830e50a7131b3 1838 
otrs2_5.0.16-1+deb9u3.dsc
 12a56d047f3c6c41adf7dc4469bf8b18e415dfef39da0106fef32acd9fdcebb5 49600 
otrs2_5.0.16-1+deb9u3.debian.tar.xz
 ec18c5f49bd863233908048b7f87aed061bba727e57130875ab9789b1d709be4 7052652 
otrs2_5.0.16-1+deb9u3_all.deb
 02a5ec25cbbc41417510c05437222c84151d03c06abaed7ef75db7ab17ea268a 7244 
otrs2_5.0.16-1+deb9u3_amd64.buildinfo
 e3ae8c205d8c7e848f1d85bae41e82b79b04b6e44a467c5593fb5993badd2764 213116 
otrs_5.0.16-1+deb9u3_all.deb
Files:
 e4879549dcfb7d821484cee9e206a827 1838 non-free/web optional 
otrs2_5.0.16-1+deb9u3.dsc
 412cee7efd05a7c7b78a9e9e4dcc1122 49600 non-free/web optional 
otrs2_5.0.16-1+deb9u3.debian.tar.xz
 afcc90c2acb9e20840c4cc0ee64373f4 7052652 non-free/web optional 
otrs2_5.0.16-1+deb9u3_all.deb
 7858e3e3ae32418b719d757077baf0ca 7244 non-free/web optional 
otrs2_5.0.16-1+deb9u3_amd64.buildinfo
 0abb3bb7c1d2ce9ea18328413aa413a0 213116 non-free/web optional 
otrs_5.0.16-1+deb9u3_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWKA9xYJCWk3IuQ4TEtmwSpDL2OQFAloVlZ8ACgkQEtmwSpDL

Bug#882370: marked as done (otrs2: CVE-2017-16664: OSA-2017-07: privilege escalation)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 11:02:23 +
with message-id 
and subject line Bug#882370: fixed in otrs2 3.3.18-1+deb8u2
has caused the Debian Bug report #882370,
regarding otrs2: CVE-2017-16664: OSA-2017-07: privilege escalation
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.)


-- 
882370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: otrs2
Version: 3.3.9-1
Severity: grave
Tags: patch security upstream fixed-upstream

Hi,

the following vulnerability was published for otrs2.

CVE-2017-16664[0]:
| Code injection exists in Kernel/System/Spelling.pm in Open Ticket
| Request System (OTRS) 5 before 5.0.24, 4 before 4.0.26, and 3.3 before
| 3.3.20. In the agent interface, an authenticated remote attackeer can
| execute shell commands as the webserver user via URL manipulation.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-16664
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16664
[1] 
https://www.otrs.com/security-advisory-2017-07-security-update-otrs-framework/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: otrs2
Source-Version: 3.3.18-1+deb8u2

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated otrs2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Nov 2017 15:03:02 +0100
Source: otrs2
Binary: otrs2 otrs
Architecture: source all
Version: 3.3.18-1+deb8u2
Distribution: jessie-security
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 otrs   - Open Ticket Request System (OTRS 3)
 otrs2  - Open Ticket Request System
Closes: 882370
Changes:
 otrs2 (3.3.18-1+deb8u2) jessie-security; urgency=high
 .
   * Add patch 16-OSA-2017-06 which fixes OSA-2017-06, also known as
 CVE-2017-15864: An attacker who is logged into OTRS as an agent can request
 special URLs from OTRS which can lead to the disclosure of any
 configuration information, including database credentials.
   * Add patch 17-OSA-2017-07 which fixes OSA-2017-07, also known as
 CVE-2017-16664: An attacker who is logged into OTRS as an agent can request
 special URLs from OTRS which can lead to the execution of shell commands
 with the permissions of the web server user.
 Closes: #882370
Checksums-Sha1:
 27c9cca1a50b3571b03f61eded065025e9616b84 1820 otrs2_3.3.18-1+deb8u2.dsc
 acf3b42b22a0abd76e6e6640d1eb1aa5bda2e6fc 40360 
otrs2_3.3.18-1+deb8u2.debian.tar.xz
 923c79ad2769a451b15bd75de3fc9ed5a333050b 5644592 otrs2_3.3.18-1+deb8u2_all.deb
 287c43a90c60c5617ef7a7e3d443ba2b3f55dd46 188454 otrs_3.3.18-1+deb8u2_all.deb
Checksums-Sha256:
 7f2fd625275993aba9841b85231f8a4eca1388e7447d23277db3239ce1521bd5 1820 
otrs2_3.3.18-1+deb8u2.dsc
 b5b01ce9fcd8f92ef92f8454c98f2622af54bcaa4b438cfca0da5f816cb6daa0 40360 
otrs2_3.3.18-1+deb8u2.debian.tar.xz
 fc43ed2e1242cefaa5040005e7974272106e89cdb7bc14fc7faac452716c286c 5644592 
otrs2_3.3.18-1+deb8u2_all.deb
 d9c099a91f6d78701f7fc1bc5a50139719f5104d8e0eb11e5d25b9c26dbaacf8 188454 
otrs_3.3.18-1+deb8u2_all.deb
Files:
 8dc8728850d446d72c07b604002b5ca8 1820 web optional otrs2_3.3.18-1+deb8u2.dsc
 8fd520cb5ad031c5f14e7dc90e79cecf 40360 web optional 
otrs2_3.3.18-1+deb8u2.debian.tar.xz
 3f4aa9fe0505a273fc2293a6587b1822 5644592 web optional 
otrs2_3.3.18-1+deb8u2_all.deb
 b917bfe33ff6bbc4c6b3781c8f8a54c1 188454 web optional 
otrs_3.3.18-1+deb8u2_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWKA9xYJCWk3IuQ4TEtmwSpDL2OQFAloVlZ8ACgkQEtmwSpDL
2OR4aBAAj82Mk/grW0u9V57FyVGBIjUQV9kdqen3upXbuBopaaKzfcR7UpTknzOy

Bug#882592: libinput10: Trackpad behaves erratic after upgrade to 1.9.2-1, after rolling back to 1.6.3-1 the trackpad works fine.

[Guilala]

Package: libinput10
Version: 1.6.3-1
Severity: critical
Tags: upstream
Justification: breaks unrelated software

Dear Maintainer,

   * In GNOME Shell 3.26.2 running Wayland
   * sid / testing upgrade to libinput10 1.9.2-1
   * Try using trackpad (HID device, Apple Wireless Trackpad 1)
   * Trackpad starts behaving erratic:
  - two- finger scrolling often doesn't start
  - when moving mouse position, dragging occurs unexpectedly
   * A roll back of libinput10 to 1.6.3-1 solves the problems




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

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

Versions of packages libinput10 depends on:
ii  libc6 2.25-2
ii  libevdev2 1.5.7+dfsg-1
ii  libinput-bin  1.9.2-1
ii  libmtdev1 1.1.5-1+b1
ii  libudev1  235-3
ii  libwacom2 0.26-1

libinput10 recommends no packages.

libinput10 suggests no packages.

-- no debconf information

Bug#882591: gazebo FTBFS: /usr/include/boost/predef/language/stdc.h:52: Parse error at "defined"

[Adrian Bunk]

Source: gazebo
Version: 7.8.1+dfsg-2
Severity: serious

Some recent change in unstable makes gazebo FTBFS:

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

...
/usr/include/boost/predef/language/stdc.h:52: Parse error at "defined"
gazebo/gui/CMakeFiles/gazebo_gui.dir/build.make:75: recipe for target 
'gazebo/gui/moc_ApplyWrenchDialog.cxx' failed
make[3]: *** [gazebo/gui/moc_ApplyWrenchDialog.cxx] Error 1

Bug#882589: maven-common-artifact-filters FTBFS: The following artifacts could not be resolved: org.eclipse.aether:aether-api:jar:debian, org.eclipse.aether:aether-util:jar:debian

[Adrian Bunk]

Source: maven-common-artifact-filters
Version: 3.0.1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/maven-common-artifact-filters.html

...
[INFO] 
[INFO] 
[INFO] Skipping Apache Maven Common Artifact Filters
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 1.102 s
[INFO] Finished at: 2018-12-27T04:14:10-12:00
[INFO] Final Memory: 19M/724M
[INFO] 
[ERROR] Failed to execute goal on project maven-common-artifact-filters: Could 
not resolve dependencies for project 
org.apache.maven.shared:maven-common-artifact-filters:jar:3.0.1: The following 
artifacts could not be resolved: org.eclipse.aether:aether-api:jar:debian, 
org.eclipse.aether:aether-util:jar:debian: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.eclipse.aether:aether-api:jar:debian has not been downloaded from it 
before. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/maven-common-artifact-filters-3.0.1
 -Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/maven-common-artifact-filters-3.0.1/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/maven-common-artifact-filters-3.0.1/debian 
-Dmaven.repo.local=/build/1st/maven-common-artifact-filters-3.0.1/debian/maven-repo
 --batch-mode package javadoc:jar javadoc:aggregate -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2

Bug#882356: marked as done (cacti: fails to install properly)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 10:19:36 +
with message-id 
and subject line Bug#882356: fixed in cacti 1.1.28+ds1-2
has caused the Debian Bug report #882356,
regarding cacti: fails to install properly
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.)


-- 
882356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cacti
Version: 1.1.28+ds1-1
Severity: serious
Tags: upstream
Justification: fails to install

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

cacti 1.1.28+ds-1 fails to install without errors as can be seen in the
autopkgtest¹:
populating database via sql...  error encountered populating database:
mysql said: ERROR 1227 (42000) at line 6: Access denied; you need (at least one 
of) the SUPER privilege(s) for this operation

I believe the issue is that Version 1.1.28 of cacti upstream includes a commit²
that adds the following sql command to the generation script:
SET GLOBAL sql_mode = 'NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION';

Let's block migration until the solution has been found.

Paul

¹ 
https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cacti/20171121_034951/log.gz
² https://github.com/Cacti/cacti/commit/bf6f5c3a71b7a31d0224136dd4d60ee79928bf1f

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

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

Versions of packages cacti depends on:
ii  dbconfig-common   2.0.9
ii  dbconfig-mysql2.0.9
ii  debconf [debconf-2.0] 1.5.65
ii  fonts-dejavu-core 2.37-1
ii  fonts-dejavu-extra2.37-1
ii  fonts-font-awesome4.7.0~dfsg-3
ii  javascript-common 11
ii  libapache2-mod-php1:7.0+56
ii  libapache2-mod-php7.0 [libapache2-mod-ph  7.0.25-1
ii  libjs-c3  0.4.11+dfsg-2
ii  libjs-chartjs 1.0.2-1
ii  libjs-d3  3.5.17-2
ii  libjs-jquery  3.2.1-1
ii  libjs-jquery-colorpicker  1.2.13-2
ii  libjs-jquery-cookie   12-1
ii  libjs-jquery-hotkeys  0~20130707+git2d51e3a9+dfsg-2
ii  libjs-jquery-jstree   3.3.4+dfsg1-2
ii  libjs-jquery-metadata 12-1
ii  libjs-jquery-tablesorter  1:2.29.0+dfsg1-1
ii  libjs-jquery-timepicker   1.2-1
ii  libjs-jquery-ui   1.12.1+dfsg-5
ii  libjs-jquery-ui-theme-smoothness  1.12.1+dfsg-1
ii  libjs-jquery-ui-theme-south-street1.12.1+dfsg-1
ii  libjs-jquery-ui-theme-ui-darkness 1.12.1+dfsg-1
ii  libjs-jquery-ui-touch-punch   0.0~git20141218.2.4bc0091+dfsg1-1
ii  libphp-phpmailer  5.2.14+dfsg-2.3
ii  perl  5.26.1-2
ii  php-cli   1:7.0+56
ii  php-gd1:7.0+56
ii  php-json  1:7.0+56
ii  php-ldap  1:7.0+56
ii  php-mbstring  1:7.0+56
ii  php-mysql 1:7.0+56
ii  php-php-gettext   1.0.12-0.1
ii  php-phpseclib 2.0.7-1
ii  php-snmp  1:7.0+56
ii  php-twig  1.24.0-2
ii  php-xml   1:7.0+56
ii  php7.0-cli [php-cli]  7.0.25-1
ii  php7.0-gd [php-gd]7.0.25-1
ii  php7.0-json [php-json]7.0.25-1
ii  php7.0-ldap [php-ldap]7.0.25-1
ii  php7.0-mbstring [php-mbstring]7.0.25-1
ii  php7.0-mysql [php-mysqlnd]7.0.25-1
ii  php7.0-snmp [php-snmp]7.0.25-1
ii  php7.0-xml [php-xml]  7.0.25-1
ii  rrdtool   1.6.0-1+b4
ii  snmp  5.7.3+dfsg-1.7+b2
ii  ucf   3.0036

Versions of packages cacti recommends:
ii  

Bug#881915: marked as done (libidn FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 09:20:19 +
with message-id 
and subject line Bug#881915: fixed in libidn2 2.0.4-1.1
has caused the Debian Bug report #881915,
regarding libidn FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer 
available
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.)


-- 
881915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libidn2
Version: 2.0.4-1
Severity: serious

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

...
touch scan-build.stamp
gtkdoc-mktmpl --module=libidn2 
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:1259: recipe for target 'tmpl-build.stamp' failed
make[6]: *** [tmpl-build.stamp] Error 127
--- End Message ---
--- Begin Message ---
Source: libidn2
Source-Version: 2.0.4-1.1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated libidn2 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: Thu, 23 Nov 2017 11:11:41 +
Source: libidn2
Binary: libidn2-0 libidn2-dev libidn2-0-dev idn2 libidn2-doc
Architecture: source
Version: 2.0.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Libidn team 
Changed-By: Simon McVittie 
Description:
 idn2   - Internationalized domain names (IDNA2008/TR46) command line tool
 libidn2-0  - Internationalized domain names (IDNA2008/TR46) library
 libidn2-0-dev - Internationalized domain names (IDNA2008/TR46) development 
files
 libidn2-dev - Internationalized domain names (IDNA2008/TR46) development files
 libidn2-doc - Internationalized domain names (IDNA2008/TR46) documentation
Closes: 881915 881968
Changes:
 libidn2 (2.0.4-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Helmut Grohne ]
   * Fix FTBFS: gtkdocize and add dblatex to Build-Depends. (Closes: #881915)
 .
   [ Simon McVittie ]
   * Run gtkdocize via a script debian/autogen.sh passed as a parameter
 to dh_autoreconf, so that the changed gtk-doc.make will be recorded
 by dh_autoreconf and deleted by dh_autoreconf_clean
 - Use gtkdocize --copy to avoid gtk-doc.make becoming a symlink, which
   dh_autoreconf doesn't currently handle
   * libidn2-doc Breaks/Replaces older versions of both libidn2-dev and
 libidn2-0-dev (Closes: #881968)
Checksums-Sha1:
 30dc4e77725e24ad2c1a53336ce0d91a60a3de9d 2292 libidn2_2.0.4-1.1.dsc
 df9d704951845d90a7badb182428100b0862d10b 10285032 
libidn2_2.0.4-1.1.debian.tar.xz
 dca482c8b99d978e97f6d1b95dde119e3f3b043e 11028 
libidn2_2.0.4-1.1_source.buildinfo
Checksums-Sha256:
 501fe84ff95ad94d7ef8a4a7225c0d3da9969333aeceb7c46b61e7c7b970c240 2292 
libidn2_2.0.4-1.1.dsc
 434c590d238e7fd86ead3c9e201ade52d1b415d453824817747ed77179e6793b 10285032 
libidn2_2.0.4-1.1.debian.tar.xz
 0518a398d01ec1f9a1e6bea50f3daf1da1856ccfcae309c5b5d040642057fe94 11028 
libidn2_2.0.4-1.1_source.buildinfo
Files:
 3468ca4793bc79982cdbb273f661ea45 2292 libs optional libidn2_2.0.4-1.1.dsc
 85b9d8968f7e6beb6e718f3926c8e922 10285032 libs optional 
libidn2_2.0.4-1.1.debian.tar.xz
 13fe1241807c192e288ada290dbab2ac 11028 libs optional 
libidn2_2.0.4-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAloX0KYACgkQ4FrhR4+B
TE/tWw//YH0m589Oc343v8XDEt4O+UarcSmvv7EhBIz2QD9QJho1gOv1DPHyOMTk
aCh7PqWjIBJuuEBXhsaEWiYDHeTleLZ61R7W602ff2Nh9jBoHbWgnb+sTBlyWdeY
CIXcr+5lmCB93WjYC4WUuqTVJBp7bRZnMJ2B6+tyJA7er05IHTJQOyNr/ZniKrhI
R4qC8q2TsFJNs0GKhiDQ+jPIKDn0zU8vHWOD2v4HbjuyTibckFxyRCH7ZXjn5vit
UUhvz/AC5zhkTlJJNcBXK0ksf5S7imcjXeg52pDxN8Zqw3g8Vg1Mt4OlKhW96CwQ
Kklh/HGB2ESt3xebp/NzcejPlBtX3osS4fI7FYZ00scxeAPqu5CkWZLN5AEy3Nm+
6jyV+MSgFKekB2jJOSssEZsARDyY7sfCEbHG4rdjGdjYD74vy8sO3mr9hemSQ128
WC/mCNMbJ+pKn3jmJkVPw6RFXO2RHECmE3kOUHXfN0eccrxE7wB1Iz8EHYy/02JC
8IwLwpxcuRxP0u3i+iFIx4PmOqmSyPgqEQLzKCB3xSxzILZK/dyQ47K0TEXGBFYN

Bug#881968: marked as done (libidn2-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/info/libidn2.info.gz)

[Debian Bug Tracking System]

Your message dated Fri, 24 Nov 2017 09:20:19 +
with message-id 
and subject line Bug#881968: fixed in libidn2 2.0.4-1.1
has caused the Debian Bug report #881968,
regarding libidn2-doc: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/info/libidn2.info.gz
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.)


-- 
881968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libidn2-doc
Version: 2.0.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libidn2-doc.
  Preparing to unpack .../libidn2-doc_2.0.4-1_all.deb ...
  Unpacking libidn2-doc (2.0.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libidn2-doc_2.0.4-1_all.deb (--unpack):
   trying to overwrite '/usr/share/info/libidn2.info.gz', which is also in 
package libidn2-dev:amd64 2.0.2-5
  Errors were encountered while processing:
   /var/cache/apt/archives/libidn2-doc_2.0.4-1_all.deb


cheers,

Andreas


libidn2-dev=2.0.2-5_libidn2-doc=2.0.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libidn2
Source-Version: 2.0.4-1.1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated libidn2 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: Thu, 23 Nov 2017 11:11:41 +
Source: libidn2
Binary: libidn2-0 libidn2-dev libidn2-0-dev idn2 libidn2-doc
Architecture: source
Version: 2.0.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Libidn team 
Changed-By: Simon McVittie 
Description:
 idn2   - Internationalized domain names (IDNA2008/TR46) command line tool
 libidn2-0  - Internationalized domain names (IDNA2008/TR46) library
 libidn2-0-dev - Internationalized domain names (IDNA2008/TR46) development 
files
 libidn2-dev - Internationalized domain names (IDNA2008/TR46) development files
 libidn2-doc - Internationalized domain names (IDNA2008/TR46) documentation
Closes: 881915 881968
Changes:
 libidn2 (2.0.4-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Helmut Grohne ]
   * Fix FTBFS: gtkdocize and add dblatex to Build-Depends. (Closes: #881915)
 .
   [ Simon McVittie ]
   * Run gtkdocize via a script debian/autogen.sh passed as a parameter
 to dh_autoreconf, so that the changed gtk-doc.make will be recorded
 by dh_autoreconf and deleted by dh_autoreconf_clean
 - Use gtkdocize --copy to avoid gtk-doc.make becoming a symlink, which
   dh_autoreconf doesn't currently handle
   * libidn2-doc Breaks/Replaces older versions of both libidn2-dev and
 libidn2-0-dev (Closes: #881968)
Checksums-Sha1:
 30dc4e77725e24ad2c1a53336ce0d91a60a3de9d 2292 libidn2_2.0.4-1.1.dsc
 df9d704951845d90a7badb182428100b0862d10b 10285032 
libidn2_2.0.4-1.1.debian.tar.xz
 dca482c8b99d978e97f6d1b95dde119e3f3b043e 11028 
libidn2_2.0.4-1.1_source.buildinfo
Checksums-Sha256:
 501fe84ff95ad94d7ef8a4a7225c0d3da9969333aeceb7c46b61e7c7b970c240 2292 
libidn2_2.0.4-1.1.dsc
 434c590d238e7fd86ead3c9e201ade52d1b415d453824817747ed77179e6793b 10285032 
libidn2_2.0.4-1.1.debian.tar.xz
 0518a398d01ec1f9a1e6bea50f3daf1da1856ccfcae309c5b5d040642057fe94 11028 
libidn2_2.0.4-1.1_source.buildinfo
Files:
 3468ca4793bc79982cdbb273f661ea45 2292 libs optional libidn2_2.0.4-1.1.dsc
 85b9d8968f7e6beb6e718f3926c8e922 10285032 libs optional 
libidn2_2.0.4-1.1.debian.tar.xz
 13fe1241807c192e288ada290dbab2ac 11028 libs 

Bug#881915: libidn FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available

[Simon McVittie]

On Fri, 24 Nov 2017 at 09:24:22 +0100, Tim Rühsen wrote:
> On 11/23/2017 03:37 PM, Helmut Grohne wrote:
> > The bug is
> > supposedly fixed upstream, so I expected it to be fixed with a new
> > upstream release rather than applying my patch.
> 
> If it helps, I can make up a new upstream release.
> Let me know if there is something that should be applied before.

I don't think anything special needs to be done upstream now: I've changed
the Debian packaging to refresh the gtk-doc files before build, which
(if accepted by the libidn Debian maintainers) will decouple libidn from
the version of gtk-doc used when the upstream release was prepared. This is
a bit better from the point of view of ensuring Debian is self-contained
and built from "the real source code" anyway.

For future libidn releases, it might be helpful to other downstream
distributions if you could prepare the release (make dist) on a system
with gtk-doc-tools >= 1.26.

Regards,
smcv

Bug#881915: libidn2: NMU for FTBFS #881968 and upgrade issues #881915

[Simon McVittie]

I've uploaded the attached NMU. Please note that applying the debdiff with
patch(1) is not sufficient: debian/autogen.sh needs to be executable,
which isn't represented in the diff. The git patches might be more
convenient.

These changes should also be available soon from
.

On Thu, 23 Nov 2017 at 17:31:33 +0200, Adrian Bunk wrote:
> The only thing special about libidn2 is that it missed the original
> round of RC bugs due to being in NEW for 2.5 months.

If the maintainer-built binaries were discarded when a NEW package
was accepted () then at least it would
have failed everywhere, avoiding cross-architecture skew. It's
unfortunate that NEW requires binary uploads for at least one
architecture.

Regards,
smcv
diffstat for libidn2-2.0.4 libidn2-2.0.4

 autogen.sh |4 
 changelog  |   51 +++
 control|7 ---
 rules  |3 +++
 4 files changed, 62 insertions(+), 3 deletions(-)

diff -Nru libidn2-2.0.4/debian/autogen.sh libidn2-2.0.4/debian/autogen.sh
--- libidn2-2.0.4/debian/autogen.sh	1970-01-01 01:00:00.0 +0100
+++ libidn2-2.0.4/debian/autogen.sh	2017-11-23 11:11:41.0 +
@@ -0,0 +1,4 @@
+#!/bin/sh
+set -e
+gtkdocize --copy
+autoreconf -fi
diff -Nru libidn2-2.0.4/debian/changelog libidn2-2.0.4/debian/changelog
--- libidn2-2.0.4/debian/changelog	2017-09-04 13:17:51.0 +0100
+++ libidn2-2.0.4/debian/changelog	2017-11-23 11:11:41.0 +
@@ -1,3 +1,21 @@
+libidn2 (2.0.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Fix FTBFS: gtkdocize and add dblatex to Build-Depends. (Closes: #881915)
+
+  [ Simon McVittie ]
+  * Run gtkdocize via a script debian/autogen.sh passed as a parameter
+to dh_autoreconf, so that the changed gtk-doc.make will be recorded
+by dh_autoreconf and deleted by dh_autoreconf_clean
+- Use gtkdocize --copy to avoid gtk-doc.make becoming a symlink, which
+  dh_autoreconf doesn't currently handle
+  * libidn2-doc Breaks/Replaces older versions of both libidn2-dev and
+libidn2-0-dev (Closes: #881968)
+
+ -- Simon McVittie   Thu, 23 Nov 2017 11:11:41 +
+
 libidn2 (2.0.4-1) unstable; urgency=medium
 
   * Add myself to Uploaders
@@ -38,6 +56,39 @@
 
  -- Simon Josefsson   Mon, 04 Sep 2017 11:01:44 +0200
 
+libidn2-0 (2.0.2-5) unstable; urgency=medium
+
+  [ Simon Josefsson ]
+  * Switch libidn2-0-dev back to arch:any again. (Closes: #872567)
+
+  [ Ondřej Surý ]
+  * Make libidn2-dev multi-arch compatible (Closes: #872550)
+
+ -- Ondřej Surý   Mon, 18 Sep 2017 08:00:10 +0200
+
+libidn2-0 (2.0.2-4) unstable; urgency=medium
+
+  * CVE-2017-14061: Fix integer overflow in _isBidi function (Closes: #873904)
+  * CVE-2017-14062: Fix integer overflow in decode_digit (Closes: #873902)
+  * Add upstream fix to stop stripping underscores (Closes: #869561)
+  * Add myself to Uploaders:
+
+ -- Ondřej Surý   Tue, 12 Sep 2017 10:42:14 +0200
+
+libidn2-0 (2.0.2-3) unstable; urgency=low
+
+  * Rename libidn2-0-dev to libidn2-dev.
+  * Ship new transitional package libidn2-0-dev.
+  * Update libidn2-dev.doc-base.
+
+ -- Simon Josefsson   Wed, 02 Aug 2017 20:27:38 +0200
+
+libidn2-0 (2.0.2-2) unstable; urgency=low
+
+  * Ship pkg-config file in libidn2-0-dev.  Closes: #855948.
+
+ -- Simon Josefsson   Mon, 17 Jul 2017 08:50:44 +0200
+
 libidn2-0 (2.0.2-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru libidn2-2.0.4/debian/control libidn2-2.0.4/debian/control
--- libidn2-2.0.4/debian/control	2017-09-04 13:17:51.0 +0100
+++ libidn2-2.0.4/debian/control	2017-11-23 11:11:41.0 +
@@ -12,7 +12,8 @@
ruby-ronn,
texinfo,
texlive,
-   gtk-doc-tools
+   gtk-doc-tools,
+   dblatex,
 Standards-Version: 4.1.0
 Priority: optional
 Homepage: https://www.gnu.org/software/libidn/#libidn2
@@ -71,8 +72,8 @@
 Section: doc
 Architecture: all
 Depends: ${misc:Depends}
-Replaces: libidn2-0-dev (<< 2.0.3-1~)
-Breaks: libidn2-0-dev (<< 2.0.3-1~)
+Replaces: libidn2-0-dev (<< 2.0.3-1~), libidn2-dev (<< 2.0.3-1~)
+Breaks: libidn2-0-dev (<< 2.0.3-1~), libidn2-dev (<< 2.0.3-1~)
 Recommends: libidn2-dev
 Description: Internationalized domain names (IDNA2008/TR46) documentation
  Libidn2 implements the revised algorithm for internationalized domain
diff -Nru libidn2-2.0.4/debian/rules libidn2-2.0.4/debian/rules
--- libidn2-2.0.4/debian/rules	2017-09-04 13:17:51.0 +0100
+++ libidn2-2.0.4/debian/rules	2017-11-23 11:11:41.0 +
@@ -5,6 +5,9 @@
 %:
 	dh $@ --parallel --with autoreconf --fail-missing -O--dbgsym-migration="libidn2-0-dbg (<< 2.0.2-1~)" -X.la
 
+override_dh_autoreconf:
+	dh_autoreconf debian/autogen.sh
+
 

Processed: your mail

[Debian Bug Tracking System]

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

> severity 882203 serious
Bug #882203 [freedv] freedv: FTBFS with sox 14.4.2
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#881915: libidn FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available

[Tim Rühsen]

On 11/23/2017 03:37 PM, Helmut Grohne wrote:
> On Thu, Nov 23, 2017 at 11:32:06AM +, Simon McVittie wrote:
>> It looks as though plain gtkdocize replaces gtk-doc.make with a symbolic
>> link, which dh-autoreconf won't delete (bug filed), breaking the ability
>> to build twice in a row; so gtkdocize --copy (which works like I expected)
>> is probably better, at least until/unless dh-autoreconf can be taught
>> to remove files that were replaced with a symlink. I've changed flatpak
>> in git to use gtkdocize --copy.
> 
> Thank you for your attention to detail.
> 
>> Helmut: similarly, is there a reason that I'm not seeing why explicitly
>> removing gtk-doc.make before gtkdocize was necessary, or were you only
>> doing that as a way to be completely sure that the old one wasn't used, or
>> was it a workaround for gtkdocize turning the plain file into a symlink?
> 
> I was under the impression that my first attempt was just running
> gtkdocize without removing gtk-doc.make and that didn't work. I might be
> wrong here.
> 
> Call me careless, but I am a bit annoyed by libidn2 now, as it keeps
> breaking in new ways. I was in need of a patch to make bootstrap builds
> proceed, so I only looked as far as making it barely build. The bug is
> supposedly fixed upstream, so I expected it to be fixed with a new
> upstream release rather than applying my patch.


If it helps, I can make up a new upstream release.
Let me know if there is something that should be applied before.


With Best Regards, Tim



signature.asc
Description: OpenPGP digital signature