Bug#902470: influxdb-python: FTBFS in buster/sid (failing tests)

[Andreas Tille]

Control: tags -1 help

Hi,

the diff can be found here

 'foo,hello=there 0="1",1=1i,2=1.1 0\nfoo,hello=there 
0="2",1=2i,2=2.2 36000\n' !=
 'foo,hello=there 0="1",1=1i,2=1.111 0\nfoo,hello=there 
0="2",1=2i,2=2.222 36000\n'
^^  
  ^^

So the precision of floats is to digits less than expected.

May be somebody has a clue why this is happening.

Kind regards

  Andreas.

Disclaimer: I'm not involved in influxdb-python packaging - I just had
a quick look whether I can help since this bug affects some Debian Med
packages.  Unfortunately I have no idea what to do to fix the precision
issue.

-- 
http://fam-tille.de

Processed: Re: influxdb-python: FTBFS in buster/sid (failing tests)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #902470 [src:influxdb-python] influxdb-python: FTBFS in buster/sid (failing 
tests)
Added tag(s) help.

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

Processed: Re: Bug#902774: jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 CVE-2018-12536 CVE-2018-12538

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 jetty9: CVE-2018-12536
Bug #902774 [jetty9] jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2018-12536
Changed Bug title to 'jetty9: CVE-2018-12536' from 'jetty9: CVE-2017-7656 
CVE-2017-7657 CVE-2018-12536'.
> retitle 902953 jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658
Bug #902953 [jetty9] jetty9: CVE-2017-7658
Changed Bug title to 'jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658' from 
'jetty9: CVE-2017-7658'.

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

Processed: Re: Bug#902774: jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 CVE-2018-12536 CVE-2018-12538

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 jetty9: CVE-2018-12536
Bug #902774 [jetty9] jetty9: CVE-2018-12536
Ignoring request to change the title of bug#902774 to the same title
> retitle 902953 jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658
Bug #902953 [jetty9] jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658
Ignoring request to change the title of bug#902953 to the same title

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

Bug#902774: jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 CVE-2018-12536 CVE-2018-12538

[Salvatore Bonaccorso]

Control: retitle -1 jetty9: CVE-2018-12536
Control: retitle 902953 jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658
Hi

After discussion with Emmanuel, CVE-2017-7656, CVE-2017-7657 and
VE-2017-7658 are fixed all in 9.2.25-1 with
https://github.com/eclipse/jetty.project/commit/a285deea .

So keeping this bug for the remaining one open for CVE-2018-12536.

Regards,
Salvatore

Bug#902466: marked as done (golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 03:34:02 +
with message-id 
and subject line Bug#902466: fixed in 
golang-github-grpc-ecosystem-go-grpc-prometheus 1.2.0-1
has caused the Debian Bug report #902466,
regarding golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid 
(failing tests)
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.)


-- 
902466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-github-grpc-ecosystem-go-grpc-prometheus
Version: 1.1+git20170826.0dafe0d-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   debian/rules override_dh_auto_build
make[1]: Entering directory 
'/<>/golang-github-grpc-ecosystem-go-grpc-prometheus-1.1+git20170826.0dafe0d'
cd 
obj-x86_64-linux-gnu/src/github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto
 && \
GOPATH=obj-x86_64-linux-gnu make 
make[2]: Entering directory 
'/<>/golang-github-grpc-ecosystem-go-grpc-prometheus-1.1+git20170826.0dafe0d/obj-x86_64-linux-gnu/src/github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto'
PATH="obj-x86_64-linux-gnu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
 protoc \
  -I. \
-Iobj-x86_64-linux-gnu/src \

[... snipped ...]

=== RUN   TestServerInterceptorSuite/TestUnaryIncrementsStarted
--- FAIL: TestServerInterceptorSuite (0.08s)
--- PASS: TestServerInterceptorSuite/TestRegisterPresetsStuff (0.02s)
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsHandled (0.01s)
server_test.go:218: 
Error Trace:server_test.go:218
Error:  Not equal: 
expected: 1
actual  : 0
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHandled
Messages:   grpc_server_handled_total should be 
incremented for PingList FailedPrecondition
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsHistograms 
(0.01s)
server_test.go:186: 
Error Trace:server_test.go:186
Error:  Not equal: 
expected: 2
actual  : 3
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHistograms
Messages:   grpc_server_handling_seconds_count 
should be incremented for PingList OK
server_test.go:193: 
Error Trace:server_test.go:193
Error:  Not equal: 
expected: 4
actual  : 3
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHistograms
Messages:   grpc_server_handling_seconds_count 
should be incremented for PingList FailedPrecondition
--- PASS: TestServerInterceptorSuite/TestStreamingIncrementsMessageCounts 
(0.01s)
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsStarted (0.00s)
server_test.go:168: 
Error Trace:server_test.go:168
Error:  Not equal: 
expected: 6
actual  : 5
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsStarted
Messages:   grpc_server_started_total should be 
incremented for PingList
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsHandled (0.01s)
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsHistograms (0.01s)
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsStarted (0.01s)
server_test.go:86: stopped grpc.Server at: 127.0.0.1:33315
FAIL
FAILgithub.com/grpc-ecosystem/go-grpc-prometheus0.124s
?   github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto [no 
test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 

Processed: tagging 902467

[Debian Bug Tracking System]

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

> tags 902467 + upstream
Bug #902467 [src:golang-github-kardianos-osext] golang-github-kardianos-osext: 
FTBFS in buster/sid (failing tests)
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: bug 902467 is forwarded to https://github.com/kardianos/osext/issues/21

[Debian Bug Tracking System]

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

> forwarded 902467 https://github.com/kardianos/osext/issues/21
Bug #902467 [src:golang-github-kardianos-osext] golang-github-kardianos-osext: 
FTBFS in buster/sid (failing tests)
Set Bug forwarded-to-address to 'https://github.com/kardianos/osext/issues/21'.
> thanks
Stopping processing here.

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

Processed: retitle 866371

[Debian Bug Tracking System]

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

> retitle 866371 FP register corruption on ppc64el with lock elision
Bug #866371 [src:linux] openldap FTBFS on ppc64{,el}: slapd-mtread failed (139)
Bug #866122 [src:linux] test060-mt-hot failing on ppc64el buildd
Changed Bug title to 'FP register corruption on ppc64el with lock elision' from 
'openldap FTBFS on ppc64{,el}: slapd-mtread failed (139)'.
Changed Bug title to 'FP register corruption on ppc64el with lock elision' from 
'test060-mt-hot failing on ppc64el buildd'.
> tag 866371 = upstream
Bug #866371 [src:linux] FP register corruption on ppc64el with lock elision
Bug #866122 [src:linux] FP register corruption on ppc64el with lock elision
Removed tag(s) ftbfs and moreinfo.
Removed tag(s) moreinfo and ftbfs.
> thanks
Stopping processing here.

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

Processed: Re: Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.17.3-1
Bug #866122 [src:linux] test060-mt-hot failing on ppc64el buildd
Bug #866371 [src:linux] openldap FTBFS on ppc64{,el}: slapd-mtread failed (139)
Marked as found in versions linux/4.17.3-1.
Marked as found in versions linux/4.17.3-1.

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

Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid

[Ryan Tandy]

Control: found -1 4.17.3-1

Hi,

On Mon, Jul 02, 2018 at 08:42:45PM -0700, Ryan Tandy wrote:
However it looks like it might be resolved with the kernel in 
unstable. I will run some more iterations and let you know.


The issue still reproduces with stretch userland and the current 
unstable kernel.


It cannot be reproduced with buster's glibc because lock elision was 
disabled in #878071, citing this issue.


Thanks
Ryan

Processed: Re: Bug#902946: Fails to load autofs module through autofs4 alias

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 239-1
Bug #902946 [systemd] Fails to load autofs module through autofs4 alias
No longer marked as found in versions systemd/239-1.
> found -1 238-5
Bug #902946 [systemd] Fails to load autofs module through autofs4 alias
Marked as found in versions systemd/238-5.
> found -1 239-3
Bug #902946 [systemd] Fails to load autofs module through autofs4 alias
Marked as found in versions systemd/239-3.

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

Bug#902946: Fails to load autofs module through autofs4 alias

[Ben Hutchings]

Control: notfound -1 239-1
Control: found -1 238-5
Control: found -1 239-3

On Tue, 2018-07-03 at 23:42 +0200, Michael Biebl wrote:
> Am 03.07.2018 um 23:10 schrieb Ben Hutchings:
> > On Tue, 2018-07-03 at 23:08 +0200, Michael Biebl wrote:
> > > Am 03.07.2018 um 20:11 schrieb Ben Hutchings:
> > > > Package: systemd
> > > > Version: 239-1
> > > > Severity: serious
> > > > 
> > > > Starting with Linux 4.18, the autofs4 kernel module is renamed
> > > > to autofs, but retaining an 'autofs4' alias.
> > > > 
> > > > Despite the presence of the alias, systemd fails to load the
> > > > autofs module:
> > > > 
> > > > systemd[1]: Failed to insert module 'autofs4': No such file or 
> > > > directory
> > > > 
> > > > Opened as 'serious' since I think autofs supports critical
> > > > functionality in systemd.
> > > 
> > > Is there a 4.18 kernel available where this can be tested?
> > 
> > I've uploaded it to experimental and it's currently in NEW.
> 
> Ok, thanks.
> 
> Just to be sure: Since you marked this found in version 239-1, is this
> is a regression or already reproducible with v238. I'm asking because
> this bug will block systemd from entering testing.

Just tested, and it's not a regression.  I'm correcting the found
versions to be those I've actually tested with Linux 4.18.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug



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

Bug#902962: mandelbulber2: Missing Replaces: header

[Matthias Urlichs]

Package: mandelbulber2
Version: 2.08.3-1+b1
Severity: serious
Justification: file conflicts

Unpacking mandelbulber2 (2.13.2-3) over (2.08.3-1+b1) ...
dpkg: error processing archive 
/var/cache/apt/archives/mandelbulber2_2.13.2-3_amd64.deb (--unpack):
 trying to overwrite '/usr/share/mandelbulber2/language/de.qm', which is also 
in package mandelbulber2-data 2.08.3-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../mandelbulber2-data_2.13.2-3_all.deb ...
Unpacking mandelbulber2-data (2.13.2-3) over (2.08.3-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/mandelbulber2-data_2.13.2-3_all.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/mandelbulber2.1.gz', which is also in 
package mandelbulber2 2.08.3-1+b1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages mandelbulber2 depends on:
ii  libc6   2.27-3
ii  libgcc1 1:8.1.0-9
ii  libgl1  1.0.0+git20180308-3
ii  libgl1-mesa-glx 18.1.2-1
ii  libgomp18.1.0-9
ii  libgsl232.4+dfsg-6
ii  libgslcblas02.4+dfsg-6
ii  libpng16-16 1.6.34-1
ii  libqt5core5a5.10.1+dfsg-7
ii  libqt5gui5  5.10.1+dfsg-7
ii  libqt5network5  5.10.1+dfsg-7
ii  libqt5test5 5.10.1+dfsg-7
ii  libqt5widgets5  5.10.1+dfsg-7
ii  libstdc++6  8.1.0-9
ii  mandelbulber2-data  2.08.3-1

mandelbulber2 recommends no packages.

mandelbulber2 suggests no packages.

-- no debconf information

Bug#902197: mozjs52 FTBFS with icu 60.2

[Simon McVittie]

On Wed, 04 Jul 2018 at 00:14:25 +0100, Simon McVittie wrote:
> Having fixed that, I get a different FTBFS

This is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902961

Processed: tagging 902961

[Debian Bug Tracking System]

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

> tags 902961 + ftbfs help
Bug #902961 [src:mozjs52] mozjs52: FTBFS in recent unstable: 
ReserveProcessExecutableMemory() fails during tests
Added tag(s) help and ftbfs.
> thanks
Stopping processing here.

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

Bug#902961: mozjs52: FTBFS in recent unstable: ReserveProcessExecutableMemory() fails during tests

[Simon McVittie]

Source: mozjs52
Version: 52.3.1-8
Severity: serious
Justification: fails to build from source (but built successfully in the past)

(X-Debbugs-Cc to contributors to #897178, to which this seems related,
and #902197)

After fixing #902197, the mozjs52 build-time tests failed on the amd64
Debian porterbox barriere. Specifically, the smoke-test in debian/test.sh
that's run before trying the actual test suite:

"$SRCDIR/js/src/js" -e 'print("Hello, world")'

fails, with js exiting 1.

Running it under gdb reveals that this is because
ReserveProcessExecutableMemory() in js/src/jit/ProcessExecutableMemory.cpp
fails during startup, causing JS_Init() to fail. js helpfully has no
diagnostics at all for this, it just silently exits with EXIT_FAILURE.
(Ignore the first implementation of ReserveProcessExecutableMemory(),
which is for Windows; the Unix implementation is around line 300.)

That function gets a random address, and passes it as the first argument
of mmap(., 1 gigabyte, PROT_NONE, MAP_PRIVATE | MAP_ANON, -1, 0) on
64-bit machines, or the same but with 128M instead of 1G on 32-bit.
This now seems to be failing and returning NULL.

I was surprised to find that on the same machine, if I install gjs (a
GNOME wrapper around mozjs) and the slightly older mozjs 52.3.1-7 that it
depends on, gjs-console -c 'print("hello")' works OK. (We don't package
mozjs' own command-line tool 'js' any more, so no precompiled copy is
available.) The changes between 52.3.1-7 and what I'm compiling all seem
to be specific to non-amd64 architectures, so maybe this is about the
environment in which mozjs was built, rather than the source code used?

A hack that works to avoid this is to retry the mmap() without the address
hint, like in Jason Duerstock's debian/patches/ia64-support.patch,
but for non-IA64 architectures as well; see attached. I suspect this
might be the wrong solution, but perhaps it points someone who knows
this better than I do in the direction of a better solution...

This also makes me wonder whether the failure addressed by
ia64-support.patch was in fact a generic issue with newer $something
(kernel? compiler? dpkg-buildflags?), which happened to only be seen
by ia64 porters because everyone else was compiling and testing mozjs52
with an older $something?

smcv
From: Simon McVittie 
Date: Tue, 3 Jul 2018 23:47:20 +0100
Subject: If executable memory can't be mapped,
 retry without randomization on all architectures

---
 js/src/jit/ProcessExecutableMemory.cpp | 6 --
 1 file changed, 6 deletions(-)

diff --git a/js/src/jit/ProcessExecutableMemory.cpp b/js/src/jit/ProcessExecutableMemory.cpp
index 31836f1..5e7ea5c 100644
--- a/js/src/jit/ProcessExecutableMemory.cpp
+++ b/js/src/jit/ProcessExecutableMemory.cpp
@@ -291,19 +291,13 @@ ReserveProcessExecutableMemory(size_t bytes)
 void* p = MozTaggedAnonymousMmap(randomAddr, bytes, PROT_NONE, MAP_PRIVATE | MAP_ANON,
  -1, 0, "js-executable-memory");
 
-#ifndef __ia64__
-if (p == MAP_FAILED)
-return nullptr;
-#else
 if (p == MAP_FAILED) {
-// the comment above appears to be incorrect on ia64, so retry without the hint
 p = MozTaggedAnonymousMmap(NULL, bytes, PROT_NONE, MAP_PRIVATE | MAP_ANON,
  -1, 0, "js-executable-memory");
 if (p == MAP_FAILED)
 return nullptr;
 }
 return p;
-#endif
 }
 
 static void

Processed: Re: Bug#902197: mozjs52 FTBFS with icu 60.2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #902197 [src:mozjs52] mozjs52 FTBFS with icu 60.2
Added tag(s) patch.

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

Bug#902197: mozjs52 FTBFS with icu 60.2

[Simon McVittie]

Control: tags -1 + patch

On Sat, 23 Jun 2018 at 16:33:40 +0100, Simon McVittie wrote:
> On Sat, 23 Jun 2018 at 12:52:01 +0300, Adrian Bunk wrote:
> > make[3]: *** No rule to make target 'ParagraphLayout.ao', needed by 
> > '../lib/libiculx.a'.  Stop.
> 
> It looks as though Ubuntu might have a fix for this
> ...
> +  * Don't build-depend on libicu-dev

This didn't work for me: even with a Build-Conflicts, I got the same
failure. However, a better solution seems to be to pass --disable-layoutex
to the bundled icu's configure script, as in the attached. That makes
some sense to me at least: the bundled icu's configure script has an
"automagic" dependency on the icu-le-hb layout engine library, which until
recently we didn't have. However, the bundled icu is incomplete/minimal
and doesn't actually have the source code for the optional paragraph
layout feature that requires icu-le-hb. We can resolve that by turning
the feature off, which isn't a regression because the versions of mozjs52
that compiled successfully didn't have it either.

Having fixed that, I get a different FTBFS: the mozjs command-line entry
point fails to start up. I'll open a separate bug to track that. I can
work around it, but I'm reasonably sure my workaround isn't the proper
solution.

smcv
From: Mike Hommey 
Date: Sat, 19 May 2018 11:23:18 +0900
Subject: Add --disable-layoutex when running ICU configure. r=froydnj,
 a=RyanVM

In some recent ICU update, --enable-layoutex changed from defaulting
to the "same-as-layout" to "yes", so --disable-layout doesn't imply
--disable-layoutex anymore, but we removed the layoutex files.

Applied-upstream: https://hg.mozilla.org/mozilla-unified/rev/31d4880fde31
---
 intl/icu_sources_data.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/intl/icu_sources_data.py b/intl/icu_sources_data.py
index 7d2d983..fc95d6a 100644
--- a/intl/icu_sources_data.py
+++ b/intl/icu_sources_data.py
@@ -122,6 +122,7 @@ def update_data_file(topsrcdir):
  '--disable-extras',
  '--disable-icuio',
  '--disable-layout',
+ '--disable-layoutex',
  '--disable-tests',
  '--disable-samples',
  '--disable-strict'],

Bug#899693: marked as done (sunpinyin: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jul 2018 22:20:35 +
with message-id 
and subject line Bug#899693: fixed in sunpinyin 3.0.0~rc1+ds1-1
has caused the Debian Bug report #899693,
regarding sunpinyin: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
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.)


-- 
899693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sunpinyin
Version: 3.0.0~git20160910-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of sunpinyin,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package sunpinyin since the list address
pkg-ime-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-ime-de...@lists.alioth.debian.org is 68.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: sunpinyin
Source-Version: 3.0.0~rc1+ds1-1

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

Debian distribution maintenance software
pp.
Boyuan Yang <073p...@gmail.com> (supplier of updated sunpinyin 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: Sat, 30 Jun 2018 08:27:47 +0800
Source: sunpinyin
Binary: libsunpinyin-dev libsunpinyin3v5 python-sunpinyin sunpinyin-utils
Architecture: source
Version: 3.0.0~rc1+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang <073p...@gmail.com>
Description:
 libsunpinyin-dev - Simplified Chinese Input Method from SUN (development)
 libsunpinyin3v5 - Simplified Chinese Input Method from SUN (runtime)
 python-sunpinyin - Simplified Chinese Input Method from SUN (Python binding)
 sunpinyin-utils - Simplified Chinese Input Method from SUN (utilities)
Closes: 860201 860202 898019 899693
Changes:
 sunpinyin (3.0.0~rc1+ds1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream snapshot 20180629.
 + Added support for riscv64 architecture. (Closes: #898019)
 + Made the build reproducible. (Closes: #860201)
 + Various fixes.
   * debian: Apply "wrap-and-sort -abst".
   * debian/control:
 + Update Maintainer field with debian-input-method mailing list address.
   (Closes: #899693)
 + Bump debhelper compat to v11.
 + Bump Standards-Version to 4.1.4.
 + Update homepage information. (Closes: #860202)
 + Drop unnecessary build 

Processed: severity of 901404 is serious, severity of 901405 is serious

[Debian Bug Tracking System]

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

> severity 901404 serious
Bug #901404 [systemd-shim] systemd-shim: Please dpkg-divert the dbus services 
you want dbus-activatable
Severity set to 'serious' from 'important'
> severity 901405 serious
Bug #901405 [systemd-shim] systemd-shim: Please add a sysvinit service to 
create directories on /run at boot
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#902959: pluginhook: switch Build-Depends to golang-golang-x-crypto-dev

[Andreas Beckmann]

Source: pluginhook
Version: 0~20150216.0~a320158-2
Severity: serious
Tags: sid buster

The transitional package golang-go.crypto-dev is gone. Please adjust
the Build-Depends and use golang-golang-x-crypto-dev instead.


Andreas

Bug#902958: obfs4proxy: switch Build-Depends to golang-golang-x-crypto-dev

[Andreas Beckmann]

Source: obfs4proxy
Version: 0.0.7-3
Severity: serious

The transitional package golang-go.crypto-dev is gone. Please adjust
the Build-Depends and use golang-golang-x-crypto-dev instead.


Andreas

Bug#902957: golang-ed25519-dev: switch Build-Depends to golang-golang-x-crypto-dev

[Andreas Beckmann]

Source: golang-ed25519-dev
Version: 0~20140907.d2b94fd-3
Severity: serious

The transitional package golang-go.crypto-dev is gone. Please adjust
the Build-Depends and use golang-golang-x-crypto-dev instead.


Andreas

Bug#902946: Fails to load autofs module through autofs4 alias

[Michael Biebl]

Am 03.07.2018 um 23:10 schrieb Ben Hutchings:
> On Tue, 2018-07-03 at 23:08 +0200, Michael Biebl wrote:
>> Am 03.07.2018 um 20:11 schrieb Ben Hutchings:
>>> Package: systemd
>>> Version: 239-1
>>> Severity: serious
>>>
>>> Starting with Linux 4.18, the autofs4 kernel module is renamed
>>> to autofs, but retaining an 'autofs4' alias.
>>>
>>> Despite the presence of the alias, systemd fails to load the
>>> autofs module:
>>>
>>> systemd[1]: Failed to insert module 'autofs4': No such file or directory
>>>
>>> Opened as 'serious' since I think autofs supports critical
>>> functionality in systemd.
>>
>> Is there a 4.18 kernel available where this can be tested?
> 
> I've uploaded it to experimental and it's currently in NEW.

Ok, thanks.

Just to be sure: Since you marked this found in version 239-1, is this
is a regression or already reproducible with v238. I'm asking because
this bug will block systemd from entering testing.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#902946: Fails to load autofs module through autofs4 alias

[Ben Hutchings]

On Tue, 2018-07-03 at 23:08 +0200, Michael Biebl wrote:
> Am 03.07.2018 um 20:11 schrieb Ben Hutchings:
> > Package: systemd
> > Version: 239-1
> > Severity: serious
> > 
> > Starting with Linux 4.18, the autofs4 kernel module is renamed
> > to autofs, but retaining an 'autofs4' alias.
> > 
> > Despite the presence of the alias, systemd fails to load the
> > autofs module:
> > 
> > systemd[1]: Failed to insert module 'autofs4': No such file or directory
> > 
> > Opened as 'serious' since I think autofs supports critical
> > functionality in systemd.
> 
> Is there a 4.18 kernel available where this can be tested?

I've uploaded it to experimental and it's currently in NEW.

Ben.

-- 
Ben Hutchings
Power corrupts.  Absolute power is kind of neat. - John Lehman



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

Bug#902946: Fails to load autofs module through autofs4 alias

[Michael Biebl]

Am 03.07.2018 um 20:11 schrieb Ben Hutchings:
> Package: systemd
> Version: 239-1
> Severity: serious
> 
> Starting with Linux 4.18, the autofs4 kernel module is renamed
> to autofs, but retaining an 'autofs4' alias.
> 
> Despite the presence of the alias, systemd fails to load the
> autofs module:
> 
> systemd[1]: Failed to insert module 'autofs4': No such file or directory
> 
> Opened as 'serious' since I think autofs supports critical
> functionality in systemd.

Is there a 4.18 kernel available where this can be tested?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#902943: cryptsetup-initramfs: Encrypted rootfs in LVM is not found after upgrade

[Guilhem Moulin]

On Tue, 03 Jul 2018 at 20:01:02 +0200, doak wrote:
> After system upgrade the system is not bootable anymore due the
> initramfs is unable to find the "source" for the rootfs and boot
> hangs.

Not forever, though.  It drops to a debug shell after ‘rootdelay’
(default 180) seconds, unless you've set the ‘panic=’ boot
parameter.

> linux-debian_crypt UUID=979d71b4-f9a9-45cb-b72e-6c81754ab504 none luks

We're now relying on lvm2's /scripts/local-block/lvm2 to activate the VG
holding our source device, which doesn't work with UUIDs:


https://sources.debian.org/src/lvm2/2.02.176-4.1/debian/initramfs-tools/lvm2/scripts/local-block/lvm2/

I'd argue that this is a bug in lvm2's local-block script.  The very
same problem happens if /usr is held by a dedicated LV (whether / is
held by a different LV in the same VG, in another VG, or by a non mapped
device) and the FS is specified using its UUID in the fstab(5).

If you specify the source device as /dev/mapper/linux-debian or
/dev/linux/debian then you should be able to boot.  “Should”, because
for LUKS we're using UUIDs internally, so right now this won't work.

When the source device is mapped we can use its (mangled) name instead.
But coming up with our own logic to activate VGs is beyond the scope of
cryptsetup IMHO.

-- 
Guilhem.


signature.asc
Description: PGP signature

Processed: severity of 898406 is grave

[Debian Bug Tracking System]

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

> severity 898406 grave
Bug #898406 [src:flif] flif: CVE-2018-10971
Warning: Unknown package 'src:flif'
Severity set to 'grave' from 'important'
Warning: Unknown package 'src:flif'
> thanks
Stopping processing here.

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

Processed: cloning 902774, retitle 902774 to jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2018-12536 ...

[Debian Bug Tracking System]

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

> clone 902774 -1
Bug #902774 [jetty9] jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 
CVE-2018-12536
Bug 902774 cloned as bug 902953
> retitle 902774 jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2018-12536
Bug #902774 [jetty9] jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 
CVE-2018-12536
Changed Bug title to 'jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2018-12536' from 
'jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 CVE-2018-12536'.
> retitle -1 jetty9: CVE-2017-7658
Bug #902953 [jetty9] jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 
CVE-2018-12536
Changed Bug title to 'jetty9: CVE-2017-7658' from 'jetty9: CVE-2017-7656 
CVE-2017-7657 CVE-2017-7658 CVE-2018-12536'.
> fixed -1 9.2.25-1
Bug #902953 [jetty9] jetty9: CVE-2017-7658
Marked as fixed in versions jetty9/9.2.25-1.
> thanks
Stopping processing here.

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

Processed: bug 902946 is forwarded to https://github.com/systemd/systemd/issues/9501

[Debian Bug Tracking System]

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

> forwarded 902946 https://github.com/systemd/systemd/issues/9501
Bug #902946 [systemd] Fails to load autofs module through autofs4 alias
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/9501'.
> thanks
Stopping processing here.

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

Processed: Re: this is a bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #253513 [mailutils] sender (From:) - policy specifies use of /etc/mailname 
on Debian
Severity set to 'important' from 'serious'

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

Bug#253513: this is a bug

[Niels Thykier]

Control: severity -1 important

On Wed, 6 Sep 2017 10:52:32 +0100 Daniel Pocock  wrote:
> 
> According to policy
> 
> /usr/share/doc/debian-policy/policy.txt.gz
> 
> "Non-conformance with
>  guidelines denoted by _should_ (or _recommended_) will generally be
>  considered a bug, but will not necessarily render a package unsuitable
>  for distribution."
> 
> and further down:
> 
> "If your package needs to know what hostname to use on (for example)
>  outgoing news and mail messages which are generated locally, you
>  should use the file `/etc/mailname'.  It will contain the portion
>  after the username and `@' (at) sign for email addresses of users on
>  the machine (followed by a newline)."
> 
> Note that policy uses the word "should" for mailname, so wishlist doesn't 
> appear to be a suitable severity for this issue.
> 
> [...]
> 

I am downgrading to important.  While I agree this is not a wishlist
item, "should" is not sufficient to consider it sufficiently important
to potentially block a release (and nor is the fact that it affects new
installations either).

Thanks,
~Niels

Bug#902934: [pkg-php-pear] Bug#902934: phpunit: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org

[David Prévot]

On Tue, Jul 03, 2018 at 07:25:09PM +, Thorsten Glaser wrote:
> David Prévot dixit:
> 
> >pkg-php-pear != pkg-php-maint
> 
> But all those Alioth lists no longer exist.

This one does, thanks to the lists.alioth.debian.org migration. I do get
your messages to the BTS through it.

https://lists.debian.org/debian-devel-announce/2018/04/msg4.html
https://alioth-lists.debian.net/pipermail/pkg-php-pear/2018-July/011192.html

Regards

David


signature.asc
Description: PGP signature

Processed: reassign 902898 to libreoffice-core, found 902898 in 1:6.1.0~beta2-1

[Debian Bug Tracking System]

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

> reassign 902898 libreoffice-core
Bug #902898 [libreoffice] libreoffice: missing versioned dependency to 
uno-libs3 >= 6.1
Bug reassigned from package 'libreoffice' to 'libreoffice-core'.
No longer marked as found in versions libreoffice/1:6.1.0~beta2-1.
Ignoring request to alter fixed versions of bug #902898 to the same values 
previously set
> found 902898 1:6.1.0~beta2-1
Bug #902898 [libreoffice-core] libreoffice: missing versioned dependency to 
uno-libs3 >= 6.1
Marked as found in versions libreoffice/1:6.1.0~beta2-1.
> thanks
Stopping processing here.

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

Processed: severity of 902898 is serious ...

[Debian Bug Tracking System]

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

> severity 902898 serious
Bug #902898 [libreoffice] libreoffice: missing dependency to uno-libs3
Severity set to 'serious' from 'normal'
> retitle 902898 libreoffice: missing versioned dependency to uno-libs3 >= 6.1
Bug #902898 [libreoffice] libreoffice: missing dependency to uno-libs3
Changed Bug title to 'libreoffice: missing versioned dependency to uno-libs3 >= 
6.1' from 'libreoffice: missing dependency to uno-libs3'.
> thanks
Stopping processing here.

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

Bug#902934: marked as done (phpunit: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 3 Jul 2018 08:56:05 -1000
with message-id <4cffadfb-bb80-082f-9004-477755dd4...@tilapin.org>
and subject line [pkg-php-pear] Bug#902934: phpunit: Invalid maintainer address 
pkg-php-p...@lists.alioth.debian.org
has caused the Debian Bug report #902934,
regarding phpunit: Invalid maintainer address 
pkg-php-p...@lists.alioth.debian.org
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.)


-- 
902934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpunit
Version: 7.2.4-1
Severity: serious
Justification: Policy 3.3

See #899636 et al. for all the gory details.

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

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

Versions of packages phpunit depends on:
ii  php-cli 1:7.2+61
ii  php-codecoverage6.0.7+dfsg-1
ii  php-common  1:61
ii  php-deepcopy1.8.1-1
ii  php-doctrine-instantiator   1.1.0-2
ii  php-file-iterator   2.0.1-1
ii  php-mbstring1:7.2+61
ii  php-phar-io-manifest1.0.1-2
ii  php-phar-io-version 1.0.1-1
ii  php-phpspec-prophecy1.7.6-1
ii  php-text-template   1.2.1-2
ii  php-timer   2.0.0-2
ii  php-xml 1:7.2+61
ii  php7.0-cli [php-cli]7.0.29-1+b2
ii  php7.0-json [php-json]  7.0.29-1+b2
ii  php7.0-mbstring [php-mbstring]  7.0.29-1+b2
ii  php7.0-xml [php-xml]7.0.29-1+b2
ii  php7.1-cli [php-cli]7.1.16-1+b2
ii  php7.1-json [php-json]  7.1.16-1+b2
ii  php7.1-mbstring [php-mbstring]  7.1.16-1+b2
ii  php7.2-cli [php-cli]7.2.4-1+b2
ii  php7.2-json [php-json]  7.2.4-1+b2
ii  php7.2-mbstring [php-mbstring]  7.2.4-1+b2
ii  php7.2-xml [php-xml]7.2.4-1+b2
ii  phpunit-comparator  3.0.1-1
ii  phpunit-diff3.0.1-1
ii  phpunit-environment 3.1.0-2
ii  phpunit-exporter3.1.0-2
ii  phpunit-global-state2.0.0really2.0.0-2
ii  phpunit-object-enumerator   3.0.3-2
ii  phpunit-resource-operations 1.0.0-2
ii  phpunit-version 2.0.1-1

phpunit recommends no packages.

Versions of packages phpunit suggests:
pn  php-invoker 
pn  php-soap
pn  php-xdebug  
pn  phpunit-dbunit  

-- no debconf information
--- End Message ---
--- Begin Message ---
Le 03/07/2018 à 06:48, Thorsten Glaser a écrit :
> Package: phpunit
> Version: 7.2.4-1
> Severity: serious
> Justification: Policy 3.3
> 
> See #899636 et al. for all the gory details.

pkg-php-pear != pkg-php-maint






signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#902945: igraph: FTBFS with ARPACK 3.6

[Andreas Tille]

Control: forwarded -1 https://github.com/igraph/igraph/issues/1107
Control: tags -1 help
Control: tags -1 upstream

Hi,

thanks for the bug report.  I've forwarded the issue upstream.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#902945: igraph: FTBFS with ARPACK 3.6

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/igraph/igraph/issues/1107
Bug #902945 [src:igraph] igraph: FTBFS with ARPACK 3.6
Set Bug forwarded-to-address to 'https://github.com/igraph/igraph/issues/1107'.
> tags -1 help
Bug #902945 [src:igraph] igraph: FTBFS with ARPACK 3.6
Added tag(s) help.
> tags -1 upstream
Bug #902945 [src:igraph] igraph: FTBFS with ARPACK 3.6
Added tag(s) upstream.

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

Bug#902934: [pkg-php-pear] Bug#902934: phpunit: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org

[Thorsten Glaser]

David Prévot dixit:

>pkg-php-pear != pkg-php-maint

But all those Alioth lists no longer exist.

bye,
//mirabilos
-- 
18:47⎜ well channels… you see, I see everything in the
same window anyway  18:48⎜ i know, you have some kind of
telnet with automatic pong 18:48⎜ haha, yes :D
18:49⎜ though that's more tinyirc – sirc is more comfy

Bug#902632: nvidia-legacy-340xx-kernel-dkms: the compiled module fails to load with error 'Invalid module format'

[François Revol]

I also had this bug when upgrading today.

I had this in dmesg:

module: nvidia: Unknown rela relocation: 4

Possibly some issue with the linker or the elf loader in the newer kernel.


Anyway, I just upgraded the kernel to 4.16 and added the correct arg to
/etc/defaults/grub and it's working again.

Bug#902933: marked as done (phpunit : Depends: php-phar-io-version (< 2~~) but 2.0.0-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jul 2018 19:03:59 +
with message-id 
and subject line Bug#902933: fixed in phpunit 7.2.6-1
has caused the Debian Bug report #902933,
regarding phpunit : Depends: php-phar-io-version (< 2~~) but 2.0.0-1 is to be 
installed
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.)


-- 
902933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpunit
Version: 7.2.4-1
Severity: serious
Justification: package no longer installable in sid

The recent upload of php-phar-io-version broke even the
most recent upload of phpunit.

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

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

Versions of packages phpunit depends on:
ii  php-cli 1:7.2+61
ii  php-codecoverage6.0.7+dfsg-1
ii  php-common  1:61
ii  php-deepcopy1.8.1-1
ii  php-doctrine-instantiator   1.1.0-2
ii  php-file-iterator   2.0.1-1
ii  php-mbstring1:7.2+61
ii  php-phar-io-manifest1.0.1-2
ii  php-phar-io-version 1.0.1-1
ii  php-phpspec-prophecy1.7.6-1
ii  php-text-template   1.2.1-2
ii  php-timer   2.0.0-2
ii  php-xml 1:7.2+61
ii  php7.0-cli [php-cli]7.0.29-1+b2
ii  php7.0-json [php-json]  7.0.29-1+b2
ii  php7.0-mbstring [php-mbstring]  7.0.29-1+b2
ii  php7.0-xml [php-xml]7.0.29-1+b2
ii  php7.1-cli [php-cli]7.1.16-1+b2
ii  php7.1-json [php-json]  7.1.16-1+b2
ii  php7.1-mbstring [php-mbstring]  7.1.16-1+b2
ii  php7.2-cli [php-cli]7.2.4-1+b2
ii  php7.2-json [php-json]  7.2.4-1+b2
ii  php7.2-mbstring [php-mbstring]  7.2.4-1+b2
ii  php7.2-xml [php-xml]7.2.4-1+b2
ii  phpunit-comparator  3.0.1-1
ii  phpunit-diff3.0.1-1
ii  phpunit-environment 3.1.0-2
ii  phpunit-exporter3.1.0-2
ii  phpunit-global-state2.0.0really2.0.0-2
ii  phpunit-object-enumerator   3.0.3-2
ii  phpunit-resource-operations 1.0.0-2
ii  phpunit-version 2.0.1-1

phpunit recommends no packages.

Versions of packages phpunit suggests:
pn  php-invoker 
pn  php-soap
pn  php-xdebug  
pn  phpunit-dbunit  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: phpunit
Source-Version: 7.2.6-1

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated phpunit 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: Tue, 03 Jul 2018 08:40:21 -1000
Source: phpunit
Binary: phpunit
Architecture: source
Version: 7.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Description:
 phpunit- Unit testing suite for PHP
Closes: 902933
Changes:
 phpunit (7.2.6-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Sebastian Bergmann ]
   * Prepare release
 .
   [ David Prévot ]
   * Bump phar-io versioned dependencies (Closes: #902933)
Checksums-Sha1:
 5e2c6fb0594d080f9c6c017993c0450d05e03443 2011 phpunit_7.2.6-1.dsc
 fb842a763e0c60ff1f9802350d1e067490a39f81 250396 phpunit_7.2.6.orig.tar.gz
 a4fe95debaba1c5f38cc1fa88d81bd7ddd58ef82 13028 phpunit_7.2.6-1.debian.tar.xz
Checksums-Sha256:
 148eedd1c36c448945535580713df2b8beb6cc67f6271f492bdae2f9327be971 2011 
phpunit_7.2.6-1.dsc
 7b22f4c96a8a9605d4769a3a9ae5a5de07ea76ab9a90cd0cd45d51a67d83b149 250396 
phpunit_7.2.6.orig.tar.gz
 

Processed: limit source to phpunit, tagging 902933

[Debian Bug Tracking System]

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

> limit source phpunit
Limiting to bugs with field 'source' containing at least one of 'phpunit'
Limit currently set to 'source':'phpunit'

> tags 902933 + pending
Bug #902933 [phpunit] phpunit : Depends: php-phar-io-version (< 2~~) but 
2.0.0-1 is to be installed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#902947: seafile-daemon and seafile-cli are unusable in 6.2.0

[Moritz Schlarb]

Source: seafile
Version: 6.2.0-1
Severity: serious
Tags: upstream
Justification: Policy 3.5

This bug is mainly to prevent migration of the 6.2.0 package.

Upstream is working on removing the ccnet dependency, but right now they've
only done that for the non-python parts of the package.



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

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

Bug#902945: igraph: FTBFS with ARPACK 3.6

[Graham Inggs]

Source: igraph
Version: 0.7.1-2.1
Severity: serious
Tags: ftbfs

Hi maintainer

Since the upload of arpack 3.6.0-1 to unstable, igraph FTBFS [1] with
the following test failures:

BLAS, LAPACK and ARPACK based functions

191: Basic BLAS functions (igraph_blas_*):   ok
192: Dense symmetric eigenvalues and eigenvectors (igraph_lapack_dsyevr): ok
193: Dense non-symmetric eigenvalues and eigenvectors (igraph_lapack_dgeev): ok
194: Dense non-symmetric eigenvalues and eigenvectors (igraph_lapack_dgeevx): ok
195: Solving linear systems with LU factorization (igraph_lapack_dgesv): ok
196: Upper Hessenberg transformation (igraph_lapack_dgehrd): ok
197: Eigenvector centrality (igraph_eigenvector_centrality): FAILED
(arpack.at:59)
198: Non-symmetric ARPACK solver (igraph_arpack_rnsolve): FAILED (arpack.at:66)

Bipartite graphs

199: Create bipartite graphs (igraph_create_bipartite): ok
200: Projection of bipartite graphs (igraph_bipartite_projection): ok

Centralization

201: Centralization (igraph_centralization_*):   FAILED
(centralization.at:26)

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/history/amd64/igraph.html

Bug#902946: Fails to load autofs module through autofs4 alias

[Ben Hutchings]

Package: systemd
Version: 239-1
Severity: serious

Starting with Linux 4.18, the autofs4 kernel module is renamed
to autofs, but retaining an 'autofs4' alias.

Despite the presence of the alias, systemd fails to load the
autofs module:

systemd[1]: Failed to insert module 'autofs4': No such file or directory

Opened as 'serious' since I think autofs supports critical
functionality in systemd.

Ben.

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.117
ii  libacl1  2.2.52-3+b1
ii  libapparmor1 2.12-4
ii  libaudit11:2.8.3-1
ii  libblkid12.32-0.1
ii  libc62.27-3
ii  libcap2  1:2.25-1.2
ii  libcryptsetup12  2:2.0.3-4
ii  libgcrypt20  1.8.3-1
ii  libgnutls30  3.5.18-1
ii  libgpg-error01.31-1
ii  libidn11 1.33-2.2
ii  libip4tc01.6.2-1
ii  libkmod2 25-1
ii  liblz4-1 1.8.2-1
ii  liblzma5 5.2.2-1.3
ii  libmount12.32-0.1
ii  libpam0g 1.1.8-3.7
ii  libseccomp2  2.3.3-2
ii  libselinux1  2.8-1
ii  libsystemd0  239-1
ii  mount2.32-0.1
ii  procps   2:3.3.15-2
ii  util-linux   2.32-0.1

Versions of packages systemd recommends:
ii  dbus1.12.8-3
ii  libpam-systemd  239-1

Versions of packages systemd suggests:
ii  policykit-10.105-20
ii  systemd-container  239-1

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.131~1.gbp0170b7
ii  udev 239-1

-- no debconf information

Bug#902943: cryptsetup-initramfs: Encrypted rootfs in LVM is not found after upgrade

[doak]

Package: cryptsetup-initramfs
Version: 2:2.0.3-4
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   After system upgrade the system is not bootable anymore due the
   initramfs is unable to find the "source" for the rootfs and boot
   hangs.
   Before the upgrade this worked seamlessly for a long time, UUID of FS
   did not change recently.

   When breaking into initramfs (kernel argument 'break'), I am able to
   activate the LVM logical volume manually with 'lvm lvchange -a y linux'.
   Resuming the boot after that works, i.e. the passphrase is asked and
   boot continues after successful decryption.

   Please let me know if I should provide more detailed debug
   information.

   Regards,
   doak


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.16.0-2-amd64 root=/dev/mapper/linux-debian_crypt ro quiet

-- /etc/crypttab
linux-debian_crypt UUID=979d71b4-f9a9-45cb-b72e-6c81754ab504 none luks

-- /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
/dev/mapper/linux-debian_crypt /   ext4errors=remount-ro 0  
 1
# /boot was on /dev/sda5 during installation
UUID=42edef9b-e7dc-4ceb-a5e1-05d958d6ea6f /boot ext4 defaults 0 2
/SWAP   noneswapdefaults0   0

-- lsmod
Module  Size  Used by
ctr16384  6
ccm20480  9
cmac   16384  0
rfcomm 86016  0
fuse  118784  3
ipt_MASQUERADE 16384  1
nf_nat_masquerade_ipv416384  1 ipt_MASQUERADE
nf_conntrack_netlink49152  0
nfnetlink  16384  2 nf_conntrack_netlink
xfrm_user  45056  1
xfrm_algo  16384  1 xfrm_user
iptable_nat16384  1
nf_conntrack_ipv4  16384  3
nf_defrag_ipv4 16384  1 nf_conntrack_ipv4
nf_nat_ipv416384  1 iptable_nat
xt_addrtype16384  2
xt_conntrack   16384  1
nf_nat 36864  2 nf_nat_masquerade_ipv4,nf_nat_ipv4
nf_conntrack  151552  7 
nf_conntrack_ipv4,ipt_MASQUERADE,nf_conntrack_netlink,nf_nat_masquerade_ipv4,xt_conntrack,nf_nat_ipv4,nf_nat
libcrc32c  16384  2 nf_conntrack,nf_nat
br_netfilter   24576  0
bridge184320  1 br_netfilter
stp16384  1 bridge
llc16384  2 bridge,stp
bnep   24576  2
overlay   102400  0
ebtable_filter 16384  0
ebtables   36864  1 ebtable_filter
devlink61440  0
ip6table_filter16384  0
ip6_tables 32768  1 ip6table_filter
iptable_filter 16384  1
snd_hda_codec_hdmi 57344  1
binfmt_misc20480  1
intel_rapl 24576  0
x86_pkg_temp_thermal16384  0
intel_powerclamp   16384  0
coretemp   16384  0
kvm_intel 180224  0
uvcvideo  106496  0
arc4   16384  2
kvm   704512  1 kvm_intel
videobuf2_vmalloc  16384  1 uvcvideo
videobuf2_memops   16384  1 videobuf2_vmalloc
videobuf2_v4l2 28672  1 uvcvideo
videobuf2_common   49152  2 uvcvideo,videobuf2_v4l2
irqbypass  16384  1 kvm
iTCO_wdt   16384  0
cdc_mbim   16384  0
wmi_bmof   16384  0
btusb  53248  0
iwlmvm290816  0
iTCO_vendor_support16384  1 iTCO_wdt
videodev  204800  3 uvcvideo,videobuf2_common,videobuf2_v4l2
mac80211  802816  1 iwlmvm
cdc_wdm24576  1 cdc_mbim
btrtl  16384  1 btusb
intel_cstate   16384  0
btbcm  16384  1 btusb
media  45056  2 uvcvideo,videodev
cdc_ncm40960  1 cdc_mbim
btintel24576  1 btusb
intel_uncore  131072  0
usbnet 49152  2 cdc_mbim,cdc_ncm
iwlwifi   225280  1 iwlmvm
i915 1650688  20
bluetooth 626688  14 btrtl,btintel,bnep,btbcm,rfcomm,btusb
mii16384  1 usbnet
cdc_acm32768  2
intel_rapl_perf16384  0
evdev  28672  29
joydev 24576  0
snd_hda_codec_realtek   110592  1
serio_raw  16384  0
snd_hda_codec_generic86016  1 snd_hda_codec_realtek
pcspkr 16384  0
snd_hda_intel  45056  8
drbg   28672  1
ansi_cprng 16384  0
snd_hda_codec 151552  4 
snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
ecdh_generic   24576  1 bluetooth
cfg80211  737280  3 iwlmvm,iwlwifi,mac80211
sg 36864  0
rtsx_pci_ms20480  0
snd_hda_core   94208  5 

Bug#790196: Rasmol needs severe contribution to stay in Debian

[Drew Parsons]

On Tue, 2018-07-03 at 15:25 +0100, Carnë Draug wrote:
> On 3 July 2018 at 14:59, Andreas Tille  wrote:
> > Hi,
> > 
> > the bug log of #790196[1] shows that rasmol in its current state
> > will
> > not be distributable with Buster.  Upstream is dead so if we want
> > to
> > keep it in Debian we have the option:
> > 
> >1) Port it to Gtk+ 3 (see porting guide [2])
> >2) Find a Gtk+ 2 replacement for libvte
> >3) Give up and remove this package from Debian
> > 
> > 
...
> Maybe option 3 is not that bad.  Debian also packages pymol which is
> used even more [4] so it's not like rasmol users will be left without
> an
> alternative.

I'd be joyful if someone kept rasmol alive.

But viewmol is also an alternative which I've continued to find useful.

Drew

Bug#902934: phpunit: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org

[Thorsten Glaser]

Package: phpunit
Version: 7.2.4-1
Severity: serious
Justification: Policy 3.3

See #899636 et al. for all the gory details.

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

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

Versions of packages phpunit depends on:
ii  php-cli 1:7.2+61
ii  php-codecoverage6.0.7+dfsg-1
ii  php-common  1:61
ii  php-deepcopy1.8.1-1
ii  php-doctrine-instantiator   1.1.0-2
ii  php-file-iterator   2.0.1-1
ii  php-mbstring1:7.2+61
ii  php-phar-io-manifest1.0.1-2
ii  php-phar-io-version 1.0.1-1
ii  php-phpspec-prophecy1.7.6-1
ii  php-text-template   1.2.1-2
ii  php-timer   2.0.0-2
ii  php-xml 1:7.2+61
ii  php7.0-cli [php-cli]7.0.29-1+b2
ii  php7.0-json [php-json]  7.0.29-1+b2
ii  php7.0-mbstring [php-mbstring]  7.0.29-1+b2
ii  php7.0-xml [php-xml]7.0.29-1+b2
ii  php7.1-cli [php-cli]7.1.16-1+b2
ii  php7.1-json [php-json]  7.1.16-1+b2
ii  php7.1-mbstring [php-mbstring]  7.1.16-1+b2
ii  php7.2-cli [php-cli]7.2.4-1+b2
ii  php7.2-json [php-json]  7.2.4-1+b2
ii  php7.2-mbstring [php-mbstring]  7.2.4-1+b2
ii  php7.2-xml [php-xml]7.2.4-1+b2
ii  phpunit-comparator  3.0.1-1
ii  phpunit-diff3.0.1-1
ii  phpunit-environment 3.1.0-2
ii  phpunit-exporter3.1.0-2
ii  phpunit-global-state2.0.0really2.0.0-2
ii  phpunit-object-enumerator   3.0.3-2
ii  phpunit-resource-operations 1.0.0-2
ii  phpunit-version 2.0.1-1

phpunit recommends no packages.

Versions of packages phpunit suggests:
pn  php-invoker 
pn  php-soap
pn  php-xdebug  
pn  phpunit-dbunit  

-- no debconf information

Bug#902933: phpunit : Depends: php-phar-io-version (< 2~~) but 2.0.0-1 is to be installed

[Thorsten Glaser]

Package: phpunit
Version: 7.2.4-1
Severity: serious
Justification: package no longer installable in sid

The recent upload of php-phar-io-version broke even the
most recent upload of phpunit.

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

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

Versions of packages phpunit depends on:
ii  php-cli 1:7.2+61
ii  php-codecoverage6.0.7+dfsg-1
ii  php-common  1:61
ii  php-deepcopy1.8.1-1
ii  php-doctrine-instantiator   1.1.0-2
ii  php-file-iterator   2.0.1-1
ii  php-mbstring1:7.2+61
ii  php-phar-io-manifest1.0.1-2
ii  php-phar-io-version 1.0.1-1
ii  php-phpspec-prophecy1.7.6-1
ii  php-text-template   1.2.1-2
ii  php-timer   2.0.0-2
ii  php-xml 1:7.2+61
ii  php7.0-cli [php-cli]7.0.29-1+b2
ii  php7.0-json [php-json]  7.0.29-1+b2
ii  php7.0-mbstring [php-mbstring]  7.0.29-1+b2
ii  php7.0-xml [php-xml]7.0.29-1+b2
ii  php7.1-cli [php-cli]7.1.16-1+b2
ii  php7.1-json [php-json]  7.1.16-1+b2
ii  php7.1-mbstring [php-mbstring]  7.1.16-1+b2
ii  php7.2-cli [php-cli]7.2.4-1+b2
ii  php7.2-json [php-json]  7.2.4-1+b2
ii  php7.2-mbstring [php-mbstring]  7.2.4-1+b2
ii  php7.2-xml [php-xml]7.2.4-1+b2
ii  phpunit-comparator  3.0.1-1
ii  phpunit-diff3.0.1-1
ii  phpunit-environment 3.1.0-2
ii  phpunit-exporter3.1.0-2
ii  phpunit-global-state2.0.0really2.0.0-2
ii  phpunit-object-enumerator   3.0.3-2
ii  phpunit-resource-operations 1.0.0-2
ii  phpunit-version 2.0.1-1

phpunit recommends no packages.

Versions of packages phpunit suggests:
pn  php-invoker 
pn  php-soap
pn  php-xdebug  
pn  phpunit-dbunit  

-- no debconf information

Bug#902921: boost1.63: FTBFS with python3.7 supported: libs/python/src/converter/builtin_converters.cpp:51:35: error: invalid conversion from 'const void*' to 'void*' [-fpermissive]

[Giovanni Mascellani]

Hi,

Il 03/07/2018 17:01, Simon McVittie ha scritto:> Similar to #902702,
boost1.63 fails to build when binNMU'd against
> python3.7. This example build log is from amd64:
Thanks for reporting. My feeling here is that it would be advisable to
just remove boost1.63 from unstable. No package depends on it (as it was
never promoted to the default boost version) and hopefully both 1.62 and
1.63 will be soon replaced by 1.67, which is close to being ready now.

What do other boost maintainers propose?

Giovanni.
-- 
Giovanni Mascellani 
Postdoc researcher - Université Libre de Bruxelles



signature.asc
Description: OpenPGP digital signature

Bug#902644: upower: Upower breaks power saving settings after upgrade to 0.99.8-1

[Adilson dos Santos Dantas]

It worked here. Commenting out this option fixes the bug.

Thank you for the solution.

Em ter, 3 de jul de 2018 às 11:49, Michael Biebl 
escreveu:

> Hi
>
> On Thu, 28 Jun 2018 21:55:01 -0300 Adilson dos Santos Dantas
>  wrote:
> > Package: upower
> > Version: 0.99.8-1
> > Severity: important
> >
> > Dear Maintainer,
> >
> > After upgrading upower to 0.99.8-1, my KDE power saving settings stops
> working.
> > There is no reaction when I unplug and plug back my notebook AC power.
> > Only the battery charge status changes after a few minutes.
> >
> > The only workaround found, for this problem, is a downgrade back to
> 0.99.7-2.
>
> Could you please test 0.99.8-1 again and comment out (or remove) the
> following line in /lib/systemd/system/upower.service:
>
> PrivateNetwork=true
>
> After that run (as root)
> systemctl daemon-reload; systemctl restart upower
>
> Please report back if that fixes your problem.
>
> Regards,
> Michael
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>

-- 
Adilson dos Santos Dantas
http://www.adilson.net.br
http://twitter.com/adilsond

Bug#864309: marked as done (pgloader: crashes on startup if libssl1.0.2 is not installed)

[Debian Bug Tracking System]

Your message dated Tue, 3 Jul 2018 18:26:52 +0200
with message-id <20180703162652.ga3...@msg.df7cb.de>
and subject line Re: Bug#864309: pgloader: crashes on startup if libssl1.0.2 is 
not installed
has caused the Debian Bug report #864309,
regarding pgloader: crashes on startup if libssl1.0.2 is not installed
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.)


-- 
864309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pgloader
Version: 3.3.2+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

in a fresh stretch chroot, apt-get installing pgloader and running it
without arguments results in:

(stretch_amd64-dchroot)mbanck@barriere:~$ pgloader

debugger invoked on a SIMPLE-ERROR in thread
#:
  Error opening shared object "libssl.so.1.0.2":
  libssl.so.1.0.2: cannot open shared object file: No such file or
directory.

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [CONTINUE   ] Skip this shared object and continue.
  1: [RETRY  ] Retry loading this shared object.
  2: [CHANGE-PATHNAME] Specify a different pathname to load the shared
object from.

(SB-SYS:DLOPEN-OR-LOSE #S(SB-ALIEN::SHARED-OBJECT :PATHNAME
#P"libssl.so.1.0.2" :NAMESTRING "libssl.so.1.0.2" :HANDLE NIL :DONT-SAVE
NIL))
0] (SB-EXT:EXIT)
(stretch_amd64-dchroot)mbanck@barriere:~$ 

If I install libssl1.0.2, it no longer crashes.  Just rebuilding the
package does not help, as libssl1.0.2 get dragged in via Build-Depends.
I tried to rebuild cl-plus-ssl as well, but that does not help either.

Maybe a band-aid for stretch would be to manually add the libssl1.0.2
Depends?


Michael
--- End Message ---
--- Begin Message ---
Version: 3.5.2-1

Re: Andreas Beckmann 2017-06-07 
<20170607170636.17741.92278.report...@zam581.zam.kfa-juelich.de>
> Followup-For: Bug #864309
> Control: tag -1 patch
> 
> For completeness, the diff of my NMU.
> 
> 
> Andreas

> diff -Nru pgloader-3.3.2+dfsg/debian/changelog 
> pgloader-3.3.2+dfsg/debian/changelog
> --- pgloader-3.3.2+dfsg/debian/changelog  2016-12-03 17:36:56.0 
> +0100
> +++ pgloader-3.3.2+dfsg/debian/changelog  2017-06-07 12:19:48.0 
> +0200
> @@ -1,3 +1,11 @@
> +pgloader (3.3.2+dfsg-1.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * pgloader: Add Depends: libssl1.0.2, dlopen()ed at runtime.

Hi,

sorry that this NMU got lost in the last version. Now the problem is
properly fixed by having cl-plus-ssl depending on the correct libssl
package, and making pgloader mirror that dependency.

Will add the Closes tag to the changelog now.

Christoph--- End Message ---

Bug#875885: marked as done (netkit-tftp: does not trap ./configure errors)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jul 2018 16:04:17 +
with message-id 
and subject line Bug#875885: fixed in netkit-tftp 0.17-20
has caused the Debian Bug report #875885,
regarding netkit-tftp: does not trap ./configure errors
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.)


-- 
875885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netkit-tftp
Version: 0.17-18.1
Severity: serious
Justification: policy 4.6

netkit-tftp's debian/rules does not trap errors from ./configure. In
case ./configure fails, the build continues. This can produces
apparently successful misbuilds and is prohibited by the Debian policy
in section 4.6.

Helmut
--- End Message ---
--- Begin Message ---
Source: netkit-tftp
Source-Version: 0.17-20

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

Debian distribution maintenance software
pp.
Alberto Gonzalez Iniesta  (supplier of updated netkit-tftp 
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: Tue, 03 Jul 2018 17:30:38 +0200
Source: netkit-tftp
Binary: tftp tftpd
Architecture: source amd64
Version: 0.17-20
Distribution: unstable
Urgency: medium
Maintainer: Alberto Gonzalez Iniesta 
Changed-By: Alberto Gonzalez Iniesta 
Description:
 tftp   - Trivial file transfer protocol client
 tftpd  - Trivial file transfer protocol server
Closes: 875885
Changes:
 netkit-tftp (0.17-20) unstable; urgency=medium
 .
   * configure: Exit with appropiate return code so that
 build fails on configure errors. (Closes: #875885)
Checksums-Sha1:
 b045184047d7167e6587c6eae38ba0ac795192a1 1745 netkit-tftp_0.17-20.dsc
 4898ac83d65df99b3ce52d1acdc1b4f4e519eb6e 11976 
netkit-tftp_0.17-20.debian.tar.xz
 fee05ad298618c0f74157f11b223182f0247c241 6396 
netkit-tftp_0.17-20_amd64.buildinfo
 03ae76bca9b98804d7a539cbd3d5a0c7363bc0e0 3588 tftp-dbgsym_0.17-20_amd64.deb
 b768f9ccae876e4edc447aad80fc689fec3a8614 18092 tftp_0.17-20_amd64.deb
 ca0a7dbfde2b37e9be8c030a56a4f687809f1d19 3064 tftpd-dbgsym_0.17-20_amd64.deb
 3dc0f21dd433e4216f406e8b6d68c9222f9fa1ea 16192 tftpd_0.17-20_amd64.deb
Checksums-Sha256:
 01cf76e7ed695f9f6823f2c73479fe70e68c523bf5eff7aafdc4b0eefcb778dd 1745 
netkit-tftp_0.17-20.dsc
 ab9b38bc407dfc8973dc0e0de42c03f92f20503f8552e6a2c7e9dd601d256e88 11976 
netkit-tftp_0.17-20.debian.tar.xz
 1b33b1181f1ba703e138252dc06b592e1d0d086e36a50d552188a05208b680f1 6396 
netkit-tftp_0.17-20_amd64.buildinfo
 f16fd5abb3ef78a78e0c2551ceef0a41df81abc74923f62398bc5175f4fd30d8 3588 
tftp-dbgsym_0.17-20_amd64.deb
 feae9551097d0a7f9461c86e5f7177a2316df54adab4a83d0a83887b7734016b 18092 
tftp_0.17-20_amd64.deb
 1298edf80f836c841967a0c71b9401b986e268e888419449528ad1cfcb491190 3064 
tftpd-dbgsym_0.17-20_amd64.deb
 97de3a5ca290fd7b793725c9c6f74c6473f8de56aaa1d0f2d9b5b8b05ef0a124 16192 
tftpd_0.17-20_amd64.deb
Files:
 e4899fe96002d2a4622acd246a152f3b 1745 net optional netkit-tftp_0.17-20.dsc
 79cdc609494eefb83ac5a59286e18981 11976 net optional 
netkit-tftp_0.17-20.debian.tar.xz
 5561084ed879c0421feeaf655006464f 6396 net optional 
netkit-tftp_0.17-20_amd64.buildinfo
 e12c73e44984759f9a11903dd80a41b3 3588 debug optional 
tftp-dbgsym_0.17-20_amd64.deb
 04e8c48ef7af249f11d4ee01086507f5 18092 net optional tftp_0.17-20_amd64.deb
 adb3a516237accb872136b01769c331d 3064 debug optional 
tftpd-dbgsym_0.17-20_amd64.deb
 b4eab24a3dc18da4024d53619c5f6455 16192 net optional tftpd_0.17-20_amd64.deb

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEEU0fL2D4wqetNfUvyAJszdWuaqlUFAls7l7EQHGFnaUBpbml0
dGFiLm9yZwAKCRAAmzN1a5qqVW5eEACuE2oNdHYo57Z52emarV6j8K0vG4f2CM3V
faM9AAmHawsuMCGHf4/uGUYMSXbpUbUx6Ky0TjLUDFzs0oQUjW0zafImVWNJq6Ep
nIY5HSzugPd4pWCAxSvgn7SnzYi5IGfc5V/pxX3jtvqMP3txnA9+DJs2ZQcyBzmi
9mS+mNWSWxI0X1nmIdiilkerdNV9uGIQUSZHVMr5Lwabuq/WyxD7BHBlGcN1ky+q
ase2ebNCZpVYGv15FRfi980pK2bYgE7wYn7jH0S3pzd8iobkE60ZQLB/QV2J9453
J/2HnnviQWfRR7kwj+yrFTOTqnocjTweulZGl9Cgkg6sVT3RA9R/ljG43jIrxjzg
v0Zz3MwaS1C1ihB1FCdJtYWEAoSoC8XivYUl0phicpKzsS0be+OECF1SSaM8oUrG

Bug#897533: marked as done (sunflow: FTBFS: convert-im6.q16: unable to open file `/tmp/magick-22610UfLlJYiQTV4q': No such file or directory @ error/constitute.c/ReadImage/544.)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jul 2018 15:49:50 +
with message-id 
and subject line Bug#897533: fixed in sunflow 0.07.2.svn396+dfsg-17
has caused the Debian Bug report #897533,
regarding sunflow: FTBFS: convert-im6.q16: unable to open file 
`/tmp/magick-22610UfLlJYiQTV4q': No such file or directory @ 
error/constitute.c/ReadImage/544.
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.)


-- 
897533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sunflow
Version: 0.07.2.svn396+dfsg-16
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> cd . && /usr/lib/jvm/default-java/bin/java -classpath 
> /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/janino.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dcompile.debug=true 
> -Dcompile.optimize=true jars javadoc
> Buildfile: /<>/sunflow-0.07.2.svn396+dfsg/build.xml
> 
> init:
> 
> compile:
> [mkdir] Created dir: 
> /<>/sunflow-0.07.2.svn396+dfsg/build/classes
> [javac] /<>/sunflow-0.07.2.svn396+dfsg/build.xml:37: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable builds
> [javac] Using javac -source 5 is no longer supported, switching to 1.7
> [javac] Using javac -target 5 is no longer supported, switching to 1.7
> [javac] Compiling 208 source files to 
> /<>/sunflow-0.07.2.svn396+dfsg/build/classes
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 7
> [javac] 
> /<>/sunflow-0.07.2.svn396+dfsg/src/org/sunflow/system/RenderGlobalsPanel.java:182:
>  warning: [unchecked] unchecked call to DefaultComboBoxModel(E[]) as a member 
> of the raw type DefaultComboBoxModel
> [javac] ComboBoxModel 
> minSamplingComboBoxModel = new DefaultComboBoxModel(new String[] {
> [javac]   
>^
> [javac]   where E is a type-variable:
> [javac] E extends Object declared in class DefaultComboBoxModel
> [javac] 
> /<>/sunflow-0.07.2.svn396+dfsg/src/org/sunflow/system/RenderGlobalsPanel.java:186:
>  warning: [unchecked] unchecked call to setModel(ComboBoxModel) as a 
> member of the raw type JComboBox
> [javac] 
> minSamplingComboBox.setModel(minSamplingComboBoxModel);
> [javac] ^
> [javac]   where E is a type-variable:
> [javac] E extends Object declared in class JComboBox
> [javac] 
> /<>/sunflow-0.07.2.svn396+dfsg/src/org/sunflow/system/RenderGlobalsPanel.java:194:
>  warning: [unchecked] unchecked call to DefaultComboBoxModel(E[]) as a member 
> of the raw type DefaultComboBoxModel
> [javac] ComboBoxModel 
> maxSamplingComboxBoxModel = new DefaultComboBoxModel(new String[] {
> [javac]   
> ^
> [javac]   where E is a type-variable:
> [javac] E extends Object declared in class DefaultComboBoxModel
> [javac] 
> /<>/sunflow-0.07.2.svn396+dfsg/src/org/sunflow/system/RenderGlobalsPanel.java:198:
>  warning: [unchecked] unchecked call to setModel(ComboBoxModel) as a 
> member of the raw type JComboBox
> [javac] 
> maxSamplingComboxBox.setModel(maxSamplingComboxBoxModel);
> [javac]  ^
> [javac]   where E is a type-variable:
> [javac] E extends Object declared in class JComboBox
> [javac] Note: 
> /<>/sunflow-0.07.2.svn396+dfsg/src/org/sunflow/system/Plugins.java 
> uses or overrides a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] 5 warnings
> 
> create_manifest:
> 
> jars:
> [mkdir] Created dir: /<>/sunflow-0.07.2.svn396+dfsg/release
>   [jar] Building jar: 
> /<>/sunflow-0.07.2.svn396+dfsg/release/sunflow.jar
>   [jar] Building jar: 
> /<>/sunflow-0.07.2.svn396+dfsg/release/sunflowGUI.jar
> 
> init:
> 
> javadoc:
> [mkdir] Created dir: 
> /<>/sunflow-0.07.2.svn396+dfsg/release/javadoc
>   [javadoc] /<>/sunflow-0.07.2.svn396+dfsg/src contains 

Processed: Bug #897533 in sunflow marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #897533 [src:sunflow] sunflow: FTBFS: convert-im6.q16: unable to open file 
`/tmp/magick-22610UfLlJYiQTV4q': No such file or directory @ 
error/constitute.c/ReadImage/544.
Added tag(s) pending.

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

Bug#897533: Bug #897533 in sunflow marked as pending

[Markus Koschany]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/sunflow/commit/a714f09cb61abb13f7ccdda24d91e903cb6ea57e


Don't convert svg icon into xpm or png format. Install the svg icon

into hicolor icon directory and use that as our preferred desktop icon.

Closes: #897533



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/897533

Bug#875885: netkit-tftp: does not trap ./configure errors

[Helmut Grohne]

On Tue, Jul 03, 2018 at 12:29:00PM +0200, Alberto Gonzalez Iniesta wrote:
> Have you tested your assertion? Because if ./configure fails, MCONFIG is
> not created and the build (make) fails:

That was a general statement. I think it doesn't really matter whether
it practically does cause misbuilds: The cost/benefit ratio is fairly
obvious. Fixing such issues is generally trivial. Checking whether they
really can result in misbuilds is generally expensive. Thus the policy
prohibits this bad pattern.

The other issue is that delayed failure costs time when diagnosing build
failures. You look at the failing step and then notice that some
prerequisite was missing/broken until you find the root cause. For
instance, a cross build of netkit-tftp fails in dh_strip even though the
cause is in the ./configure invocation. That is another reason for not
allowing the delaying of failure.

The policy not just prohibits silent misbuilds, it goes further and
disallows the pattern than can make them happen.

Helmut

Bug#902921: boost1.63: FTBFS with python3.7 supported: libs/python/src/converter/builtin_converters.cpp:51:35: error: invalid conversion from 'const void*' to 'void*' [-fpermissive]

[Simon McVittie]

Source: boost1.63
Version: 1.63.0+dfsg-1.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Similar to #902702, boost1.63 fails to build when binNMU'd against
python3.7. This example build log is from amd64:

https://buildd.debian.org/status/fetch.php?pkg=boost1.63=amd64=1.63.0%2Bdfsg-1.1%2Bb3=1530274967=0
> libs/python/src/converter/builtin_converters.cpp: In function 'void* 
> boost::python::converter::{anonymous}::convert_to_cstring(PyObject*)':
> libs/python/src/converter/builtin_converters.cpp:51:35: error: invalid 
> conversion from 'const void*' to 'void*' [-fpermissive]
>return PyUnicode_Check(obj) ? _PyUnicode_AsString(obj) : 0;

The same patch would probably work.

Regards,
smcv

Bug#902644: upower: Upower breaks power saving settings after upgrade to 0.99.8-1

[Michael Biebl]

Hi

On Thu, 28 Jun 2018 21:55:01 -0300 Adilson dos Santos Dantas
 wrote:
> Package: upower
> Version: 0.99.8-1
> Severity: important
> 
> Dear Maintainer,
> 
> After upgrading upower to 0.99.8-1, my KDE power saving settings stops 
> working.
> There is no reaction when I unplug and plug back my notebook AC power.
> Only the battery charge status changes after a few minutes.
> 
> The only workaround found, for this problem, is a downgrade back to 0.99.7-2.

Could you please test 0.99.8-1 again and comment out (or remove) the
following line in /lib/systemd/system/upower.service:

PrivateNetwork=true

After that run (as root)
systemctl daemon-reload; systemctl restart upower

Please report back if that fixes your problem.

Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#790196: Rasmol needs severe contribution to stay in Debian

[Carnë Draug]

On 3 July 2018 at 14:59, Andreas Tille  wrote:
> Hi,
>
> the bug log of #790196[1] shows that rasmol in its current state will
> not be distributable with Buster.  Upstream is dead so if we want to
> keep it in Debian we have the option:
>
>1) Port it to Gtk+ 3 (see porting guide [2])
>2) Find a Gtk+ 2 replacement for libvte
>3) Give up and remove this package from Debian
>
> Since option 3 would be a shame for a package with quite some users[3]
> (at least in the field of scientific software) I'm hereby making some
> noise about this.  My recent upload updates metadata (Salsa migration),
> fixed all other bugs and most of the lintian issues.
>
> I'd be really happy if someone could spent some time into this
>
>   Andreas.
>
>
> [1] https://bugs.debian.org/790196
> [2] https://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html
> [3] https://qa.debian.org/popcon.php?package=rasmol

Maybe option 3 is not that bad.  Debian also packages pymol which is
used even more [4] so it's not like rasmol users will be left without an
alternative.

David

[4] https://qa.debian.org/popcon.php?package=pymol

Bug#790196: Rasmol needs severe contribution to stay in Debian

[Andreas Tille]

Hi,

the bug log of #790196[1] shows that rasmol in its current state will
not be distributable with Buster.  Upstream is dead so if we want to
keep it in Debian we have the option:

   1) Port it to Gtk+ 3 (see porting guide [2])
   2) Find a Gtk+ 2 replacement for libvte
   3) Give up and remove this package from Debian

Since option 3 would be a shame for a package with quite some users[3]
(at least in the field of scientific software) I'm hereby making some
noise about this.  My recent upload updates metadata (Salsa migration),
fixed all other bugs and most of the lintian issues.

I'd be really happy if someone could spent some time into this

  Andreas.


[1] https://bugs.debian.org/790196
[2] https://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html
[3] https://qa.debian.org/popcon.php?package=rasmol

-- 
http://fam-tille.de

Bug#897504: fixed in golang-github-hashicorp-go-plugin 0.0~git20170621.5ee1a665-1

[Santiago Vila]

found 897504 0.0~git20170621.5ee1a665-1
thanks

Hello. I tried to rebuild this package in buster and it failed with
the same error initially posted by Lucas Nussbaum:

--- FAIL: TestClient_syncStreams (0.10s)
rpc_client_test.go:59: bad:
stdouttest^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

This also happens in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/golang-github-hashicorp-go-plugin.html

So apparently the problem is still there.

Thanks.

Processed: Re: Bug#897504: fixed in golang-github-hashicorp-go-plugin 0.0~git20170621.5ee1a665-1

[Debian Bug Tracking System]

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

> found 897504 0.0~git20170621.5ee1a665-1
Bug #897504 {Done: Dmitry Smirnov } 
[src:golang-github-hashicorp-go-plugin] golang-github-hashicorp-go-plugin: 
FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/hashicorp/go-plugin returned exit code 1
Marked as found in versions 
golang-github-hashicorp-go-plugin/0.0~git20170621.5ee1a665-1; no longer marked 
as fixed in versions 
golang-github-hashicorp-go-plugin/0.0~git20170621.5ee1a665-1 and reopened.
> thanks
Stopping processing here.

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

Bug#900772: marked as done (cakephp: depends on php-mcrypt which is no longer available in php7.2)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jul 2018 12:49:05 +
with message-id 
and subject line Bug#900772: fixed in cakephp 2.10.11-1
has caused the Debian Bug report #900772,
regarding cakephp: depends on php-mcrypt which is no longer available in php7.2
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.)


-- 
900772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cakephp
Version: 2.8.5-1
Severity: serious
Tags: sid buster

Your package depends on php-mcrypt, which is no longer provided since php7.2.
Since we are removing php versions older than that for buster, you should
update your package to no longer require that module.

Emilio
--- End Message ---
--- Begin Message ---
Source: cakephp
Source-Version: 2.10.11-1

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated cakephp 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: Tue, 03 Jul 2018 21:49:47 +1000
Source: cakephp
Binary: cakephp cakephp-scripts
Architecture: source all
Version: 2.10.11-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 cakephp- rapid application development framework for PHP
 cakephp-scripts - rapid application development framework for PHP (scripts)
Closes: 900772
Changes:
 cakephp (2.10.11-1) unstable; urgency=medium
 .
   * New upstream release.
   * Depends:
 - php-mcrypt (Closes: #900772).
   * rules: invoke dh --with "phpcomposer".
   * Removed "cakephp-instaweb" from Suggests.
   * debhelper & compat to version 11.
   * Standards-Version: 4.1.4.
   * Vcs URLs to Salsa.
Checksums-Sha1:
 a1a4cba782dda8ede3edd12f1a9bcc009af62729 1941 cakephp_2.10.11-1.dsc
 25085adbaa38a988770425f503cf907799c16fb7 1110520 cakephp_2.10.11.orig.tar.xz
 b0d82fbcddcc343e6970e5aeba8fde6fa05ab891 8236 cakephp_2.10.11-1.debian.tar.xz
 d19801e07e4f12f07ca922393f757f7ba00ee2a6 38164 
cakephp-scripts_2.10.11-1_all.deb
 e65999c028856450e18009bc301bd21de5e97e86 1130652 cakephp_2.10.11-1_all.deb
 73ae9bd971a6aad3f5c091209cfe36995bb9498a 6449 cakephp_2.10.11-1_amd64.buildinfo
Checksums-Sha256:
 b05b04abd4c1620a0dba52d7bfdd47d769f7bd97a12681d7714d63ff0d1681d5 1941 
cakephp_2.10.11-1.dsc
 fd769d0474ce846a2ed4ca48c0f2fde8fdbc95254da4e1ae1d6a46ac17da16ee 1110520 
cakephp_2.10.11.orig.tar.xz
 7dca88571f045257f0ee24a1e608f0dfcb1b58ff1e8755e45e8fd20147df5b73 8236 
cakephp_2.10.11-1.debian.tar.xz
 980dcf1efbcd21a8a26e00915ec1f4db0f278908a822bc458cb3c09292cc934d 38164 
cakephp-scripts_2.10.11-1_all.deb
 1613de5ca99cc52abb639c38a88f6dc00ca308fb028c421835fe9de4c19c6fef 1130652 
cakephp_2.10.11-1_all.deb
 ebbe18ee0622b0fd5f3422d6d1df69e760a3b4d6e3151c2f8b3bd2d0d2ab0be5 6449 
cakephp_2.10.11-1_amd64.buildinfo
Files:
 53641dc35869917f9c8823fd98e5f578 1941 web optional cakephp_2.10.11-1.dsc
 8ba1737ec4bab7b4ae52bfb16ea59da4 1110520 web optional 
cakephp_2.10.11.orig.tar.xz
 e2e02175914e01d475c500f7c12a4877 8236 web optional 
cakephp_2.10.11-1.debian.tar.xz
 9b1a992e21bbbc63cbbb186bfc6b19f6 38164 web optional 
cakephp-scripts_2.10.11-1_all.deb
 fe6fef2c837906b07342d6464fc59795 1130652 web optional cakephp_2.10.11-1_all.deb
 6103c7eee6041627815f298d22413d66 6449 web optional 
cakephp_2.10.11-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAls7ZmwACgkQUra72VOW
jRs0Mw/7BOX1e9DYwzkft7NtTLdmCIJ51dbGvclbp30PlFY6RolQvhvFHJ21GKO5
feATt5MMkaYuOCSEW9Xe49o30JKLlgh+c+SluKCaGA9N24oLFtW5wphdRgO60ysS
0HjJ9wz7HrcIJRackZU/19UMSPXzIi/URKgc9jl1F4Qd8TZGbqwWJ7AWLL2aaUJf
WgU4CschD/EsT1wS+ESheC9aN8UZOQmd+qSdx5MbPQ6A2A5PujnbLNwQZ+wa/dpX
XVSDLKLDm/8jRu+aNtLnetPjORbNfhM8i0h+lPmCucVqydbNYONyPKPLnxPWflzo
GbDdaHubFFwfBAbmWNYMVL8dNShk6ODpu4ldw5/ra4USTFCPkNiGbEhbO1Xq1w5G
EA3RSA19DK9vfFuOckyz+GL9VgKveuCdObnIT4PR5qGA4fvVfRFkV4VlRpFQxvd1
I9LEklEwHa3dve3b8gy9eBUPZD5BAhGv+DTRTAJmotzKQnRbJpOBkXHRCZtAdCcU
xqx+ByIR/WIJL+X493sMWj5eW1TTb8F5X2KYi89iR9JxddMVfszTjSRB1nymO0xk

Bug#900399: It's confirmed: memtest86+ can kill lenovo mainboard

[Tomas Janousek]

Hi,

On Wed, Jun 06, 2018 at 03:35:36PM +0600, Сергей Коган wrote:
> [...]
> It looks like T6x, T400/500, T410/510, T420/520 laptop families could be
> affected by this problem. Starting from the T430/530 series, a communication
> protocol with the EC was changed - breaking tp_smapi driver and fixing the
> described problem as a side effect.
> [...]

This may be completely unrelated, but it seems somewhat relevant:

When pressing and holding a key during memtest86+ on an otherwise perfectly
working T420, there are errors due to a different value being read than was
written. Initially I thought my memory/motherboard is faulty and the keyboard
pressure is triggering this, but the patterns are totally deterministic: the
same key always does the same "damage" to the bits.

Perhaps there is indeed something mapped into the memory... :-)

-- 
Tomáš Janoušek, a.k.a. Pivník, a.k.a. Liskni_si, http://work.lisk.in/

Bug#871068: marked as done (cbmc: FTBFS: wmm/abstract_event.h:23:7: error: '.abstract_eventt::operation' may be used uninitialized in this function [-Werror=maybe-uninitialized])

[Debian Bug Tracking System]

Your message dated Tue, 03 Jul 2018 12:20:05 +
with message-id 
and subject line Bug#871068: fixed in cbmc 5.9-1
has caused the Debian Bug report #871068,
regarding cbmc: FTBFS: wmm/abstract_event.h:23:7: error: 
'.abstract_eventt::operation' may be used uninitialized in this 
function [-Werror=maybe-uninitialized]
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.)


-- 
871068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cbmc
Version: 5.6-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> g++ -c -MMD -MP -std=c++11 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -O2 -g 
> -Werror -Wno-long-long -Wno-sign-compare -Wno-parentheses 
> -Wno-strict-aliasing -pedantic -I .. -DHAVE_JAVA_BYTECODE -o wmm/goto2graph.o 
> wmm/goto2graph.cpp
> In file included from wmm/event_graph.h:21:0,
>  from wmm/goto2graph.h:22,
>  from wmm/goto2graph.cpp:28:
> wmm/abstract_event.h: In member function 'graph::node_indext 
> graph::add_node() [with N = abstract_eventt]':
> wmm/abstract_event.h:23:7: error: '.abstract_eventt::operation' 
> may be used uninitialized in this function [-Werror=maybe-uninitialized]
>  class abstract_eventt:public graph_nodet
>^~~
> wmm/abstract_event.h:23:7: error: '.abstract_eventt::thread' may 
> be used uninitialized in this function [-Werror=maybe-uninitialized]
> wmm/abstract_event.h:23:7: error: '.abstract_eventt::id' may be 
> used uninitialized in this function [-Werror=maybe-uninitialized]
> wmm/abstract_event.h:23:7: error: '.abstract_eventt::local' may be 
> used uninitialized in this function [-Werror=maybe-uninitialized]
> wmm/abstract_event.h:23:7: error: '.abstract_eventt::WRfence' may 
> be used uninitialized in this function [-Werror=maybe-uninitialized]
> wmm/abstract_event.h:23:7: error: '.abstract_eventt::WWfence' may 
> be used uninitialized in this function [-Werror=maybe-uninitialized]
> wmm/abstract_event.h:23:7: error: '.abstract_eventt::RRfence' may 
> be used uninitialized in this function [-Werror=maybe-uninitialized]
> wmm/abstract_event.h:23:7: error: '.abstract_eventt::RWfence' may 
> be used uninitialized in this function [-Werror=maybe-uninitialized]
> wmm/abstract_event.h:23:7: error: '.abstract_eventt::WWcumul' may 
> be used uninitialized in this function [-Werror=maybe-uninitialized]
> wmm/abstract_event.h:23:7: error: '.abstract_eventt::RWcumul' may 
> be used uninitialized in this function [-Werror=maybe-uninitialized]
> wmm/abstract_event.h:23:7: error: '.abstract_eventt::RRcumul' may 
> be used uninitialized in this function [-Werror=maybe-uninitialized]
> cc1plus: all warnings being treated as errors
> ../common:167: recipe for target 'wmm/goto2graph.o' failed
> make[3]: *** [wmm/goto2graph.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/cbmc_5.6-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: cbmc
Source-Version: 5.9-1

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

Debian distribution maintenance software
pp.
Michael Tautschnig  (supplier of updated cbmc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 02 Jul 2018 17:12:01 +0100
Source: cbmc
Binary: cbmc
Architecture: source i386
Version: 5.9-1
Distribution: unstable
Urgency: low
Maintainer: Michael Tautschnig 
Changed-By: Michael 

Bug#875885: netkit-tftp: does not trap ./configure errors

[Alberto Gonzalez Iniesta]

On Fri, Sep 15, 2017 at 05:17:44PM +0200, Helmut Grohne wrote:
> Source: netkit-tftp
> Version: 0.17-18.1
> Severity: serious
> Justification: policy 4.6
> 
> netkit-tftp's debian/rules does not trap errors from ./configure. In
> case ./configure fails, the build continues. This can produces
> apparently successful misbuilds and is prohibited by the Debian policy
> in section 4.6.
> 
> Helmut

Hello, Helmut.

Have you tested your assertion? Because if ./configure fails, MCONFIG is
not created and the build (make) fails:

make[1]: Entering directory '/home/agi/debian/netkit-tftp/netkit-tftp/tftp'
Makefile:3: ../MCONFIG: No such file or directory
make[1]: *** No rule to make target '../MCONFIG'.  Stop.
make[1]: Leaving directory '/home/agi/debian/netkit-tftp/netkit-tftp/tftp'
make: *** [Makefile:7: tftp.build] Error 2

Could you let me know how to reproduce a misbuild?

Regards,

Alberto

-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55

Processed: Re: Bug#902900: python3-celery: python3-celery fails to install with Python 3.7

[Debian Bug Tracking System]

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

> found 902900 4.2.0-1
Bug #902900 [python3-celery] python3-celery: python3-celery fails to install 
with Python 3.7
Marked as found in versions celery/4.2.0-1.
> tags 902900 + upstream
Bug #902900 [python3-celery] python3-celery: python3-celery fails to install 
with Python 3.7
Added tag(s) upstream.
> forwarded 902900 https://github.com/celery/celery/pull/4852
Bug #902900 [python3-celery] python3-celery: python3-celery fails to install 
with Python 3.7
Set Bug forwarded-to-address to 'https://github.com/celery/celery/pull/4852'.
> user debian-pyt...@lists.debian.org
Setting user to debian-pyt...@lists.debian.org (was ol...@debian.org).
> usertag 902900 + python3.7
There were no usertags set.
Usertags are now: python3.7.
> thanks
Stopping processing here.

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

Bug#902900: python3-celery: python3-celery fails to install with Python 3.7

[Nicolas Dandrimont]

found 902900 4.2.0-1
tags 902900 + upstream
forwarded 902900 https://github.com/celery/celery/pull/4852
user debian-pyt...@lists.debian.org
usertag 902900 + python3.7
thanks

* Antoine R. Dumont  [2018-07-03 10:09:56 
+0200]:

> Package: python3-celery
> Version: 4.1.0-4
> Severity: serious
> Hello,
> 
> Setting up python3-celery (4.2.0-1) ...
>   File "/usr/lib/python3/dist-packages/celery/backends/redis.py", line 22
> from . import async, base
>   ^
> SyntaxError: invalid syntax
> 
>   File "/usr/lib/python3/dist-packages/celery/backends/rpc.py", line 20
> from .async import AsyncBackendMixin, BaseResultConsumer
>   ^
> SyntaxError: invalid syntax
> 
> dpkg: error processing package python3-celery (--configure):
>  installed python3-celery package post-installation script subprocess
>  returned error exit status 1

Hi,

Work on this issue seems to be ongoing upstream. Adding the relevant tags.

Cheers,
-- 
Nicolas Dandrimont


signature.asc
Description: PGP signature

Bug#902895: marked as done (ant: Automatically setting the value of the javac --release attribute breaks josm build.)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jul 2018 10:19:04 +
with message-id 
and subject line Bug#902895: fixed in ant 1.10.4-2
has caused the Debian Bug report #902895,
regarding ant: Automatically setting the value of the javac --release attribute 
breaks josm build.
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.)


-- 
902895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ant
Version: 1.10.3-2
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:josm

Dear Maintainer,

As mentioned on the list [0], the change in ant (1.10.3-2) to
automatically set the value of the javac --release attribute breaks the
josm build.

Please revent this change which is not included upstream.

IMHO it's perfectly fine to require JRE 9 or later when building with
JDK 9 or later. JDK 8 is EOL for ordinary humans.

[0] https://lists.debian.org/debian-java/2018/07/msg6.html

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: ant
Source-Version: 1.10.4-2

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated ant 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: Tue, 03 Jul 2018 10:53:12 +0200
Source: ant
Binary: ant ant-optional ant-doc
Architecture: source
Version: 1.10.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 ant- Java based build tool like make
 ant-doc- Java based build tool like make - API documentation and manual
 ant-optional - Java based build tool like make - optional libraries
Closes: 902895
Changes:
 ant (1.10.4-2) unstable; urgency=medium
 .
   * Team upload.
   * Reverted the modification setting the 'release' attribute automatically
 since this renders the internal JDK APIs unavailable at compile time.
 (Closes: #902895)
Checksums-Sha1:
 d369295f58a8e3a67f9b0b4a6b833797ae778cbe 2411 ant_1.10.4-2.dsc
 f6f05961fd268d077a611484b4eaeeb02f16f084 19164 ant_1.10.4-2.debian.tar.xz
 459d0f9a15f30e2dc1d2046090f3f302c71d17fd 11383 ant_1.10.4-2_source.buildinfo
Checksums-Sha256:
 776345e912401d29361743e685bfdd192fd1710d0a55c4aac16923f44c06c97b 2411 
ant_1.10.4-2.dsc
 29d7940865c3998ae14fe10b721b332760bbba90fd4562b0e4406ab3869e36c3 19164 
ant_1.10.4-2.debian.tar.xz
 66781e0d3824a169267662803c801eb394723b7e009985055513c8d1413f5b06 11383 
ant_1.10.4-2_source.buildinfo
Files:
 a489c7bd209dc93506e4d571e250f521 2411 java optional ant_1.10.4-2.dsc
 d9e04123d88be15b43ab6b24f56ff202 19164 java optional ant_1.10.4-2.debian.tar.xz
 41f16740eaebe3dc4c2a0f7f2794db55 11383 java optional 
ant_1.10.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAls7SIMSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCs9G8P+wbYzr8TJHXAEFcSmIzByrPcnQp9UHHB
6t1hAUmQo4TKviPZonPii2C9mNWs5dEifWAuqyoIDiZjIK/rS9TQedkxyw8e94GR
K5fDUcTuvq/GMDGKV8KQvd8UVs4f9vvYxvEEvL62jqEGK5JFXiPZZSKWQfnS25DS
UR2K1ggEQaw1Z2UwDdnvhJSErE6/loNs/HRnMpJprN3XbgV7E5uM0zVPRdI30T9v
o7ZjVxBeL8bt1zZ49UrVhRsgYGXSHOiFk1qtem+acOJmBPNS2nxl8tLwoTNikwe/
vH1kfZy2aRpODVDfUNkUl+kOHeEXdKfka0CIBR5t1VropeXaiX7KXkNs/RFAllzE
2OC6rb3hDI/RTG1bYInIj6bdFviJlNYejkrx+ZrSw+lMQpoPa69KEUADImU82/96
o8c+zusl4bzjlFgZeZSlXVLiscjKi0YgYO/sRIwvZzHEcEDW0p58/CAWjRJ4g4x2
rO7Z75g5s/HMxXRS0LNnWVBM8Khye7hf8ntMns+WKjZnxmDZOUgOBESmsCnd0rcK
IOh3lxVhzmSGibWWOAR8YtDyeyKmmTEpWSTiNkEoFMv/YB34/yBCnigdPxOxzkes
RgoO2UucKtC6tHwOH8JnU4OXf1/FeQ8pQG+q8FD0khs5jjaTlQzqSB9pQfcqy+BH
dskZAvGnwpmk
=P4hY
-END PGP SIGNATURE End Message ---

Processed: merge 901919 902891 901919

[Debian Bug Tracking System]

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

> reassign 902868 nvidia-driver
Bug #902868 [src:nvidia-graphics-drivers] linux-image-4.16.0-2-amd64 fails to 
boot
Bug reassigned from package 'src:nvidia-graphics-drivers' to 'nvidia-driver'.
Ignoring request to alter found versions of bug #902868 to the same values 
previously set
Ignoring request to alter fixed versions of bug #902868 to the same values 
previously set
> reassign 902891 nvidia-driver
Bug #902891 [nvidia-kernel-source] nvidia-kernel-source: usercopy: Kernel 
memory exposure attempt detected from SLUB object 'nvidia_stack_cache'
Bug reassigned from package 'nvidia-kernel-source' to 'nvidia-driver'.
No longer marked as found in versions nvidia-graphics-drivers/390.67-1.
Ignoring request to alter fixed versions of bug #902891 to the same values 
previously set
> forcemerge 901919 902868 902891
Bug #901919 [nvidia-driver] nvidia-driver: black screen with the latest Linux 
kernel - general protection fault
Bug #901932 [nvidia-driver] linux-image-4.16.0-2-amd64: Blank screen after 
update kernel 4.16.16
Bug #901990 [nvidia-driver] linux-image-4.16.0-2-amd64: kernel BUG at startup 
in usercopy.c ; impossible to boot
Bug #902248 [nvidia-driver] linux-image-4.16.0-2-amd64: General protection 
fault (with nvidia driver) redulting in Xork proces hanging in "D" state
Bug #902661 [nvidia-driver] linux-image-4.16.0-2-amd64: kernel BUG at 
/build/linux-uwVqDp/linux-4.16.16/mm/usercopy.c:100!
Bug #902773 [nvidia-driver] nvidia-driver: Kernel BUG on 4.16.16 with 390.67-1, 
crashes on desktop boot
Bug #902819 [nvidia-driver] system freeze (hang task) when launching Xorg(1) 
after a new version of linux-image installed
Bug #902868 [nvidia-driver] linux-image-4.16.0-2-amd64 fails to boot
Set Bug forwarded-to-address to 
'https://devtalk.nvidia.com/default/topic/1031067'.
Severity set to 'important' from 'critical'
Marked as found in versions nvidia-graphics-drivers/390.48-3, 
nvidia-graphics-drivers/390.67-1, and nvidia-graphics-drivers/390.59-1.
Bug #902891 [nvidia-driver] nvidia-kernel-source: usercopy: Kernel memory 
exposure attempt detected from SLUB object 'nvidia_stack_cache'
Set Bug forwarded-to-address to 
'https://devtalk.nvidia.com/default/topic/1031067'.
Marked as found in versions nvidia-graphics-drivers/390.48-3, 
nvidia-graphics-drivers/390.67-1, and nvidia-graphics-drivers/390.59-1.
Bug #901932 [nvidia-driver] linux-image-4.16.0-2-amd64: Blank screen after 
update kernel 4.16.16
Bug #901990 [nvidia-driver] linux-image-4.16.0-2-amd64: kernel BUG at startup 
in usercopy.c ; impossible to boot
Bug #902248 [nvidia-driver] linux-image-4.16.0-2-amd64: General protection 
fault (with nvidia driver) redulting in Xork proces hanging in "D" state
Bug #902661 [nvidia-driver] linux-image-4.16.0-2-amd64: kernel BUG at 
/build/linux-uwVqDp/linux-4.16.16/mm/usercopy.c:100!
Bug #902773 [nvidia-driver] nvidia-driver: Kernel BUG on 4.16.16 with 390.67-1, 
crashes on desktop boot
Bug #902819 [nvidia-driver] system freeze (hang task) when launching Xorg(1) 
after a new version of linux-image installed
Merged 901919 901932 901990 902248 902661 902773 902819 902868 902891
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
901919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919
901932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901932
901990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901990
902248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902248
902661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902661
902773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902773
902819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902819
902868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902868
902891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902895: Bug #902895 in ant marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/ant/commit/d28ae18aa81495efd9bf33dbcc84838fd586315c


Reverted the modification setting the 'release' attribute automatically 
(Closes: #902895)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/902895

Processed: Bug #902895 in ant marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #902895 [src:ant] ant: Automatically setting the value of the javac 
--release attribute breaks josm build.
Added tag(s) pending.

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

Bug#845786: marked as done (gammaray FTBFS on arm64, armel, mips* and s390x: QFatal in quickinspectortest)

[Debian Bug Tracking System]

Your message dated Tue, 3 Jul 2018 11:52:38 +0200
with message-id <8f97d421-0329-e1f3-194c-a43e43d75...@debian.org>
and subject line Re: gammaray FTBFS on armhf: QFatal in quickinspectortest
has caused the Debian Bug report #845786,
regarding gammaray FTBFS on arm64, armel, mips* and s390x: QFatal in 
quickinspectortest
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=gammaray=armhf=2.6.0-1=1480176282

...
  Start 36: quickinspectortest

36: Test command: /«PKGBUILDDIR»/obj-qt5/bin/quickinspectortest
36: Test timeout computed to be: 9.99988e+06
36: * Start testing of QuickInspectorTest *
36: Config: Using QtTest library 5.7.1, Qt 5.7.1 
(arm-little_endian-ilp32-eabi-hardfloat shared (dynamic) release build; by GCC 
6.2.0 20161103)
36: PASS   : QuickInspectorTest::initTestCase()
36: QWARN  : QuickInspectorTest::testModelsReparent() Failed to connect to 
launcher, can't receive probe settings! "QLocalSocket::connectToServer: Invalid 
name"
36: 
...
36: QFatal in quickinspectortest (/«PKGBUILDDIR»/obj-qt5/bin/quickinspectortest)
36: START BACKTRACE:
36: 1   
/«PKGBUILDDIR»/obj-qt5/lib/libgammaray_core-qt5_7-arm.so.2.6.0(+0x7fdb4) 
[0xb6e0edb4]
36: 2   
/«PKGBUILDDIR»/obj-qt5/lib/libgammaray_core-qt5_7-arm.so.2.6.0(+0x62e58) 
[0xb6df1e58]
36: 3   /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5(+0x808f2) [0xb649b8f2]
36: 4   /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5(QMessageLogger::fatal(char 
const*, ...) const+0x27) [0xb649c7e8]
36: 5   /usr/lib/arm-linux-gnueabihf/libQt5Test.so.5(+0x97ec) [0xb6d6c7ec]
36: 6   /lib/arm-linux-gnueabihf/libc.so.6(+0x24fd0) [0xb621dfd0]
36: END BACKTRACE
...
--- End Message ---
--- Begin Message ---
On Sat, 26 Nov 2016 19:41:22 +0200 Adrian Bunk  wrote:
> Source: gammaray
> Version: 2.6.0-1
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=gammaray=armhf=2.6.0-1=1480176282
> 
> ...
>   Start 36: quickinspectortest
> 
> 36: Test command: /«PKGBUILDDIR»/obj-qt5/bin/quickinspectortest
> 36: Test timeout computed to be: 9.99988e+06
> 36: * Start testing of QuickInspectorTest *
> 36: Config: Using QtTest library 5.7.1, Qt 5.7.1 
> (arm-little_endian-ilp32-eabi-hardfloat shared (dynamic) release build; by 
> GCC 6.2.0 20161103)
> 36: PASS   : QuickInspectorTest::initTestCase()
> 36: QWARN  : QuickInspectorTest::testModelsReparent() Failed to connect to 
> launcher, can't receive probe settings! "QLocalSocket::connectToServer: 
> Invalid name"
> 36: 
> ...
> 36: QFatal in quickinspectortest 
> (/«PKGBUILDDIR»/obj-qt5/bin/quickinspectortest)
> 36: START BACKTRACE:
> 36: 1 
> /«PKGBUILDDIR»/obj-qt5/lib/libgammaray_core-qt5_7-arm.so.2.6.0(+0x7fdb4) 
> [0xb6e0edb4]
> 36: 2 
> /«PKGBUILDDIR»/obj-qt5/lib/libgammaray_core-qt5_7-arm.so.2.6.0(+0x62e58) 
> [0xb6df1e58]
> 36: 3 /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5(+0x808f2) [0xb649b8f2]
> 36: 4 /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5(QMessageLogger::fatal(char 
> const*, ...) const+0x27) [0xb649c7e8]
> 36: 5 /usr/lib/arm-linux-gnueabihf/libQt5Test.so.5(+0x97ec) [0xb6d6c7ec]
> 36: 6 /lib/arm-linux-gnueabihf/libc.so.6(+0x24fd0) [0xb621dfd0]
> 36: END BACKTRACE
> ...


now it seems to build fine with new gammaray and new qt stack.
And some architectures are now BD-uninstallable, so the situation has somewhat 
improved :)

G.
> 
> --- End Message ---

Bug#891156: Bug #891156 in mutter marked as pending

[Simon McVittie]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/mutter/commit/89cfeb4fd996d90b5780e55135543e579321337c


d/copyright: Copy many licenses and copyright holders

Closes: #891156



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/891156

Processed: Bug #891156 in mutter marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #891156 [src:mutter] mutter: Incomplete debian/copyright?
Added tag(s) pending.

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

Bug#902098: marked as done (gammaray: Cannot install gammaray on sid, please rebuild it with qt 5.10)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jul 2018 08:34:12 +
with message-id 
and subject line Bug#902098: fixed in gammaray 2.9.0-2.1
has caused the Debian Bug report #902098,
regarding gammaray: Cannot install gammaray on sid, please rebuild it with qt 
5.10
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.)


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

Gammaray is not installable on sid, because it still depends qtbase-abi-5-9-2.
Please handle qtbase transition and reupload.

The following is what I saw when trying to install it on sid.

$  ~ sudo apt install gammaray  
[sudo] password for hao: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gammaray : Depends: qtbase-abi-5-9-2 but it is not installable
E: Unable to correct problems, you have held broken packages.

-- 
Yanhao Mo


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gammaray
Source-Version: 2.9.0-2.1

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

Debian distribution maintenance software
pp.
Yanhao Mo  (supplier of updated gammaray 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, 22 Jun 2018 11:35:28 +0800
Source: gammaray
Binary: gammaray gammaray-plugin-quickinspector 
gammaray-plugin-waylandinspector gammaray-plugin-kjobtracker 
gammaray-plugin-bluetooth gammaray-plugin-positioning gammaray-dev
Architecture: source
Version: 2.9.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Yanhao Mo 
Description:
 gammaray   - Tool for examining the internals of Qt application
 gammaray-dev - GammaRay plugin development files
 gammaray-plugin-bluetooth - QtBluetooth type support for GammaRay
 gammaray-plugin-kjobtracker - KJob tracker plugin for GammaRay
 gammaray-plugin-positioning - Qt5Positioning type support for GammaRay
 gammaray-plugin-quickinspector - GammaRay plugin for inspecting QtQuick2 
applications
 gammaray-plugin-waylandinspector - Wayland compositor inspector plugin for 
GammaRay
Closes: 902098
Changes:
 gammaray (2.9.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 - Rebuild with Qt 5.10 (Closes: #902098).
   * d/gammaray.install: Remove the 2nd line about *gammaray_3dinspector*
 because they don't get compiled.
Checksums-Sha1:
 291c35e0dbff21df9e7907944aa97ae47ab1641e 3024 gammaray_2.9.0-2.1.dsc
 eb5c1690ac2c1ef10cf3206742713cd306f7cfdf 16644 gammaray_2.9.0-2.1.debian.tar.xz
 f0dd3f3775ddcd1b0131fe71f06894ad30537d8c 15660 
gammaray_2.9.0-2.1_source.buildinfo
Checksums-Sha256:
 6f91f8c96f7331b51dfdb44e620b6d4f191ac738ea26b10c329785c2244aa2eb 3024 
gammaray_2.9.0-2.1.dsc
 c65eb1d8732e7fd6d0daddb25d16f88843c803715d7fb0544af5e546f3e18706 16644 
gammaray_2.9.0-2.1.debian.tar.xz
 5311acff347d386911467b2bbd7f99231419bd63172eae362514ff5ca2347209 15660 
gammaray_2.9.0-2.1_source.buildinfo
Files:
 e7bff514bdcc65b8787930aa44e871fc 3024 devel optional gammaray_2.9.0-2.1.dsc
 eca5f6f3c47aa57e15ba0765bf193cde 16644 devel optional 
gammaray_2.9.0-2.1.debian.tar.xz
 bad1f1a30f07485aea71d5e004eb5ffa 15660 devel optional 
gammaray_2.9.0-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAls7Lo8ACgkQ808JdE6f
XdkAIQ/+MK35OL56X9OAf7vZ/K/pcpCjtouPD4iwqCXp9zghe3rdm94Uk0ChvNTb
z4Y9yw0+P5VN3/tk8VwDYfGikj6m6tRvcJmwt7HwXOT2x9im46XxW7LEFDl0kNWr
GoLG/NBRzG3PEVNMVDrlcDC28r4UMhOQus+Bn34Fc85ZwFHFeWtAJp9n9cWZOilz
oJLEsxHiqTP8h0OlQelQDcaDzWcRilSuS7ttXdoWZm5JsSOOr9Ys+hWMVQvjD2rt

Bug#902409: Bug #902409 in devscripts marked as pending

[Mattia Rizzolo]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/devscripts/commit/73539f21ec470de727e1242bd6392615b2c5f9ef


grep-excuse: Avoid unintended blessing during YAML loading.

CVE-2018-13043

Closes: #902409
Thanks: Ansgar Burchardt  for reporting and providing a 
patch.
Signed-off-by: Mattia Rizzolo 



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/902409

Processed: Bug #902409 in devscripts marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #902409 [devscripts] devscripts: CVE-2018-13043 - grep-excuses uses 
YAML::Syck in a unsafe way
Added tag(s) pending.

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

Bug#902098: gammaray: uploaded

[Gianfranco Costamagna]

Control: tags 902098 + patch
Control: tags 902098 + pending

Dear maintainer,

I've prepared an NMU for gammaray (versioned as 2.9.0-2.1) and
uploaded it to DELAYED/0. Please feel free to tell me if I
should delay it longer.

Regards.

G.
diff -Nru gammaray-2.9.0/debian/changelog gammaray-2.9.0/debian/changelog
--- gammaray-2.9.0/debian/changelog	2018-03-28 01:00:57.0 +0200
+++ gammaray-2.9.0/debian/changelog	2018-06-22 05:35:28.0 +0200
@@ -1,3 +1,12 @@
+gammaray (2.9.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+- Rebuild with Qt 5.10 (Closes: #902098).
+  * d/gammaray.install: Remove the 2nd line about *gammaray_3dinspector*
+because they don't get compiled.
+
+ -- Yanhao Mo   Fri, 22 Jun 2018 11:35:28 +0800
+
 gammaray (2.9.0-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru gammaray-2.9.0/debian/gammaray.install gammaray-2.9.0/debian/gammaray.install
--- gammaray-2.9.0/debian/gammaray.install	2018-03-28 01:00:57.0 +0200
+++ gammaray-2.9.0/debian/gammaray.install	2018-06-22 05:35:28.0 +0200
@@ -1,5 +1,4 @@
 usr/bin
-usr/lib/*/gammaray/*/qt5*/gammaray_3dinspector*
 usr/lib/*/gammaray/*/qt5*/gammaray_actioninspector*
 usr/lib/*/gammaray/*/qt5*/gammaray_codecbrowser*
 usr/lib/*/gammaray/*/qt5*/gammaray_fontbrowser*

Processed: gammaray: uploaded

[Debian Bug Tracking System]

Processing control commands:

> tags 902098 + patch
Bug #902098 [gammaray] gammaray: Cannot install gammaray on sid, please rebuild 
it with qt 5.10
Added tag(s) patch.
> tags 902098 + pending
Bug #902098 [gammaray] gammaray: Cannot install gammaray on sid, please rebuild 
it with qt 5.10
Added tag(s) pending.

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

Bug#901712: marked as done (linux: FTBFS when built with dpkg-buildpackage -A (needs bison))

[Debian Bug Tracking System]

Your message dated Tue, 03 Jul 2018 08:10:29 +
with message-id 
and subject line Bug#901712: fixed in linux 4.17.3-1
has caused the Debian Bug report #901712,
regarding linux: FTBFS when built with dpkg-buildpackage -A (needs bison)
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.)


-- 
901712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.16.12-1
Severity: serious

Hello Ben.

I tried to build this package with "dpkg-buildpackage -A" and it
failed in this way:

[...]
/bin/sh: 1: bison: not found
scripts/Makefile.lib:217: recipe for target 'scripts/kconfig/zconf.tab.c' failed
make[5]: *** [scripts/kconfig/zconf.tab.c] Error 127
/<>/Makefile:513: recipe for target 'listnewconfig' failed
make[4]: *** [listnewconfig] Error 2
make[4]: Leaving directory
'/<>/debian/build/build_alpha_none_alpha-generic'
Makefile:146: recipe for target 'sub-make' failed


I see that bison is currently in Build-Depends-Arch, maybe it should
be in Build-Depends.

Thanks.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.17.3-1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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: Mon, 02 Jul 2018 22:13:27 +0100
Source: linux
Binary: linux-source-4.17 linux-support-4.17.0-1 linux-doc-4.17 linux-cpupower 
libcpupower1 libcpupower-dev usbip hyperv-daemons lockdep liblockdep4.17 
liblockdep-dev linux-kbuild-4.17 linux-perf-4.17 linux-headers-4.17.0-1-common 
linux-libc-dev linux-headers-4.17.0-1-all linux-headers-4.17.0-1-all-alpha 
kernel-image-4.17.0-1-alpha-generic-di nic-modules-4.17.0-1-alpha-generic-di 
nic-wireless-modules-4.17.0-1-alpha-generic-di 
nic-shared-modules-4.17.0-1-alpha-generic-di 
serial-modules-4.17.0-1-alpha-generic-di 
usb-serial-modules-4.17.0-1-alpha-generic-di 
ppp-modules-4.17.0-1-alpha-generic-di pata-modules-4.17.0-1-alpha-generic-di 
cdrom-core-modules-4.17.0-1-alpha-generic-di 
scsi-core-modules-4.17.0-1-alpha-generic-di 
scsi-modules-4.17.0-1-alpha-generic-di loop-modules-4.17.0-1-alpha-generic-di 
btrfs-modules-4.17.0-1-alpha-generic-di ext4-modules-4.17.0-1-alpha-generic-di 
isofs-modules-4.17.0-1-alpha-generic-di jfs-modules-4.17.0-1-alpha-generic-di
 xfs-modules-4.17.0-1-alpha-generic-di fat-modules-4.17.0-1-alpha-generic-di 
md-modules-4.17.0-1-alpha-generic-di 
multipath-modules-4.17.0-1-alpha-generic-di 
usb-modules-4.17.0-1-alpha-generic-di 
usb-storage-modules-4.17.0-1-alpha-generic-di 
input-modules-4.17.0-1-alpha-generic-di event-modules-4.17.0-1-alpha-generic-di 
mouse-modules-4.17.0-1-alpha-generic-di 
nic-pcmcia-modules-4.17.0-1-alpha-generic-di 
pcmcia-modules-4.17.0-1-alpha-generic-di 
nic-usb-modules-4.17.0-1-alpha-generic-di 
sata-modules-4.17.0-1-alpha-generic-di i2c-modules-4.17.0-1-alpha-generic-di 
crc-modules-4.17.0-1-alpha-generic-di crypto-modules-4.17.0-1-alpha-generic-di 
crypto-dm-modules-4.17.0-1-alpha-generic-di 
ata-modules-4.17.0-1-alpha-generic-di nbd-modules-4.17.0-1-alpha-generic-di 
squashfs-modules-4.17.0-1-alpha-generic-di 
virtio-modules-4.17.0-1-alpha-generic-di zlib-modules-4.17.0-1-alpha-generic-di 
compress-modules-4.17.0-1-alpha-generic-di 
fuse-modules-4.17.0-1-alpha-generic-di
 srm-modules-4.17.0-1-alpha-generic-di linux-image-4.17.0-1-alpha-generic 
linux-headers-4.17.0-1-alpha-generic linux-image-4.17.0-1-alpha-generic-dbg 
linux-image-4.17.0-1-alpha-smp linux-headers-4.17.0-1-alpha-smp 
linux-image-4.17.0-1-alpha-smp-dbg linux-headers-4.17.0-1-all-amd64 
kernel-image-4.17.0-1-amd64-di nic-modules-4.17.0-1-amd64-di 
nic-wireless-modules-4.17.0-1-amd64-di nic-shared-modules-4.17.0-1-amd64-di 
serial-modules-4.17.0-1-amd64-di usb-serial-modules-4.17.0-1-amd64-di 
ppp-modules-4.17.0-1-amd64-di pata-modules-4.17.0-1-amd64-di 
cdrom-core-modules-4.17.0-1-amd64-di firewire-core-modules-4.17.0-1-amd64-di 

Bug#902901: FTBFS: Tests fail

[Ilias Tsitsimpis]

Source: haskell-polynomial
Version: 0.7.3-3
Severity: serious
Tags: upstream ftbfs
Forwarded: https://github.com/mokus0/polynomial/issues/13


$ ./dist/build/polynomial-test/polynomial-test --test-seed 1421927705 -t 
chebyshevFit
Math.Polynomial.Chebyshev:
  chebyshevFit:
sane (Double): [OK, passed 100 tests]
sane (Float): [Failed]
*** Failed! Falsifiable (after 97 tests):
NonNegative {getNonNegative = 16}

(used seed 1421927705)

 Properties  Total
 Passed  1   1
 Failed  1   1
 Total   2   2

-- 
Ilias

Bug#875400: marked as done (gammaray: B-D on qt3d-assimpsceneio-plugin which was removed)

[Debian Bug Tracking System]

Your message dated Tue, 3 Jul 2018 10:08:59 +0200
with message-id 
and subject line Re: gammaray: B-D on qt3d-assimpsceneio-plugin which was 
removed
has caused the Debian Bug report #875400,
regarding gammaray: B-D on qt3d-assimpsceneio-plugin which was removed
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.)


-- 
875400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gammaray
Version: 2.7.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Usertags: piuparts

gammaray can no longer be built in sid since qt3d-assimpsceneio-plugin
is gone from the archive.


Andreas
--- End Message ---
--- Begin Message ---
On Mon, 11 Sep 2017 10:20:49 +0200 Andreas Beckmann  wrote:
> Source: gammaray
> Version: 2.7.0-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> gammaray can no longer be built in sid since qt3d-assimpsceneio-plugin
> is gone from the archive.
> 

I think this is already fixed since a while...

G.

> 
> Andreas
> 
> --- End Message ---

Bug#864825: gammaray: crashes target program on attach

[Gianfranco Costamagna]

Control: severity -1 important

Hello, can you please try again with the new gammaray in sid?
(it will build in a few hours)

please set back the severity to serious if you still experience this crash

thanks!

Gianfranco

Processed: gammaray: crashes target program on attach

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #864825 [gammaray] gammaray: crashes target program on attach
Severity set to 'important' from 'grave'

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

Bug#902900: python3-celery: python3-celery fails to install with Python 3.7

[Antoine R. Dumont]

Package: python3-celery
Version: 4.1.0-4
Severity: serious
Hello,

Setting up python3-celery (4.2.0-1) ...
  File "/usr/lib/python3/dist-packages/celery/backends/redis.py", line 22
from . import async, base
  ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/celery/backends/rpc.py", line 20
from .async import AsyncBackendMixin, BaseResultConsumer
  ^
SyntaxError: invalid syntax

dpkg: error processing package python3-celery (--configure):
 installed python3-celery package post-installation script subprocess
 returned error exit status 1


Note:
- main environment: testing
- architecture: x86_64
- Action: using sbuild with sid chroot to build a package whose
  build/runtime dependency is python3-celery
- Expected outcome: package build success
- Actual outcome: package build failed

Cheers,
--
tony / @ardumont

-
gpg fingerprint BF00 203D 741A C9D5 46A8 BE07 52E2 E984 0D10 C3B8


signature.asc
Description: PGP signature

Bug#875885: netkit-tftp: does not trap ./configure errors

[Alberto Gonzalez Iniesta]

Hello, Raphael.

Dead upstream requires few updates to a package. Anyway, I was just
looking into that now.

Regards,

Alberto

On Tue, Jul 03, 2018 at 09:44:46AM +0200, Raphael Hertzog wrote:
> Hello Alberto,
> 
> it's been 8 years that you haven't touched netkit-tftp and the package
> has been removed from Debian testing due to the bug I'm replying to.
> 
> Can you take care of fixing the bug and/or properly orphaning the package
> if you are no longer interested in it?
> 
> Regards,
> 
> On Fri, 15 Sep 2017, Helmut Grohne wrote:
> > Source: netkit-tftp
> > Version: 0.17-18.1
> > Severity: serious
> > Justification: policy 4.6
> > 
> > netkit-tftp's debian/rules does not trap errors from ./configure. In
> > case ./configure fails, the build continues. This can produces
> > apparently successful misbuilds and is prohibited by the Debian policy
> > in section 4.6.
> > 
> > Helmut
> 

-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55

Bug#889048: Votre boîte aux lettres est

[Helene LEMIERE]

Votre boîte aux lettres est pleine et doit être validée pour éviter la 
désactivation. Cliquez sur le lien ci-dessous pour éviter que votre compte ne 
soit désactivé.

Cliquez ici

Support Zimbra / Webmail

Bug#875885: netkit-tftp: does not trap ./configure errors

[Raphael Hertzog]

Hello Alberto,

it's been 8 years that you haven't touched netkit-tftp and the package
has been removed from Debian testing due to the bug I'm replying to.

Can you take care of fixing the bug and/or properly orphaning the package
if you are no longer interested in it?

Regards,

On Fri, 15 Sep 2017, Helmut Grohne wrote:
> Source: netkit-tftp
> Version: 0.17-18.1
> Severity: serious
> Justification: policy 4.6
> 
> netkit-tftp's debian/rules does not trap errors from ./configure. In
> case ./configure fails, the build continues. This can produces
> apparently successful misbuilds and is prohibited by the Debian policy
> in section 4.6.
> 
> Helmut

-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#860064: 8.11 update breaks dnsmasq

[Henrik Riomar]

Hi,

The Debian 8.11 update (20180623) included the problematic version of
dns-root-data.

Hence dnsmasq can not be started if the init.d script is not patched.

Regards,
 Henrik