Bug#893172: python-sagenb depends on cruft package python-flask-autoindex

[peter green]

Package: python-sagenb
Severity: serious
Tags: buster,sid

python-sagenb depends on python-flask-autoindex which is no longer built by 
source package flask-autoindex

Bug#889877: marked as done (acmetool: FTBFS on ppc64el: cannot find package "golang.org/x/sys/unix")

[Debian Bug Tracking System]

Your message dated Sat, 17 Mar 2018 01:38:49 -0400
with message-id <20180317053849.GA24962@alcyone>
and subject line Re: Bug#889877: acmetool: FTBFS on ppc64el: cannot find 
package "golang.org/x/sys/unix"
has caused the Debian Bug report #889877,
regarding acmetool: FTBFS on ppc64el: cannot find package 
"golang.org/x/sys/unix"
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.)


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

Hi,

Your package failed to build on ppc64el:

dh_auto_build -- -ldflags "-X 
github.com/hlandau/acme/hooks.DefaultPath=/etc/acme/hooks -X 
github.com/hlandau/buildinfo.RawBuildInfo=YWNtZXRvb2wgRGViaWFuIHZlcnNpb24gMC4wLjYyLTE="
cd obj-powerpc64le-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/obj-powerpc64le-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/obj-powerpc64le-linux-gnu/src\" -v -p 4 
-ldflags "-X github.com/hlandau/acme/hooks.DefaultPath=/etc/acme/hooks -X 
github.com/hlandau/buildinfo.RawBuildInfo=YWNtZXRvb2wgRGViaWFuIHZlcnNpb24gMC4wLjYyLTE="
 github.com/hlandau/acme/acmeapi github.com/hlandau/acme/acmeapi/acmeendpoints 
github.com/hlandau/acme/acmeapi/acmeutils github.com/hlandau/acme/cmd/acmetool 
github.com/hlandau/acme/fdb github.com/hlandau/acme/hooks 
github.com/hlandau/acme/interaction github.com/hlandau/acme/redirector 
github.com/hlandau/acme/responder github.com/hlandau/acme/solver 
github.com/hlandau/acme/storage github.com/hlandau/acme/storageops
src/github.com/mattn/go-isatty/isatty_linux_ppc64x.go:9:2: cannot find package 
"golang.org/x/sys/unix" in any of:
/usr/lib/go-1.9/src/golang.org/x/sys/unix (from $GOROOT)
/<>/obj-powerpc64le-linux-gnu/src/golang.org/x/sys/unix 
(from $GOPATH)
dh_auto_build: cd obj-powerpc64le-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/obj-powerpc64le-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/obj-powerpc64le-linux-gnu/src\" -v -p 4 
-ldflags "-X github.com/hlandau/acme/hooks.DefaultPath=/etc/acme/hooks -X 
github.com/hlandau/buildinfo.RawBuildInfo=YWNtZXRvb2wgRGViaWFuIHZlcnNpb24gMC4wLjYyLTE="
 github.com/hlandau/acme/acmeapi github.com/hlandau/acme/acmeapi/acmeendpoints 
github.com/hlandau/acme/acmeapi/acmeutils github.com/hlandau/acme/cmd/acmetool 
github.com/hlandau/acme/fdb github.com/hlandau/acme/hooks 
github.com/hlandau/acme/interaction github.com/hlandau/acme/redirector 
github.com/hlandau/acme/responder github.com/hlandau/acme/solver 
github.com/hlandau/acme/storage github.com/hlandau/acme/storageops returned 
exit code 1
debian/rules:14: recipe for target 'override_dh_auto_build' failed

Maybe something (golang-github-mattn-go-isatty-dev ?) needs to depend on 
golang-golang-x-sys-dev

Full logs at 
https://buildd.debian.org/status/logs.php?pkg=acmetool=0.0.62-1=ppc64el

Emilio
--- End Message ---
--- Begin Message ---
Version: 0.0.62-2

On Thu, Mar 08, 2018 at 04:52:49PM +0100, Frédéric Bonnard wrote:
> it seems that we can't reproduce this bug anymore as golang went from
> 1.9 to 1.10 now.
> Well, it fails on another issue on ppc64el, but it seems to be the same on 
> amd64 .
> Should we close that bug ?

Indeed, acmetool has built successfully on ppc64el.

https://buildd.debian.org/status/fetch.php?pkg=acmetool=ppc64el=0.0.62-2=1521264499=0

Peter--- End Message ---

Bug#892467: marked as done (spfquery (libspf2-2?) and spf-milter-python falsely report "Void lookup limit exceeded")

[Debian Bug Tracking System]

Your message dated Sat, 17 Mar 2018 05:16:00 +
with message-id 
and subject line Not a bug
has caused the Debian Bug report #892467,
regarding spfquery (libspf2-2?) and spf-milter-python falsely report "Void 
lookup limit exceeded"
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.)


-- 
892467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spfquery
Version: 1.2.10-7+b2
Severity: grave
Tags: ipv6
Justification: causes non-serious data loss

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I got notified that another organization was unable to mail us. This didn't 
happen
all the time, but every few e-mail. The error logged by sendmail was 'Void 
lookup limit exceeded'.
I then had a loop running, doing spfquery for that domain every 5 seconds. When 
the next
fail in the mail-log came, the spfquery test succeeded. 

I then noted that running spfquery for that domain, with an IPv6 address always 
returns
"void lookup limit of 2 exceeded"

 spfquery --sender=some.u...@mdh.se --ip=2001:708:170:33::200
permerror
SPF Permanent Error: Void lookup limit of 2 exceeded
spfquery: permanent error in processing domain of mdh.se: Void lookup limit of 
2 exceeded
Received-SPF: PermError (spfquery: permanent error in processing domain of 
mdh.se: Void lookup limit of 2 exceeded) client-ip=2001:708:170:33::200; 
envelope-from="some.u...@mdh.se"; receiver=spfquery; identity=mailfrom

# apt-show-versions spfquery libspf2-2
libspf2-2:amd64/stretch 1.2.10-7+b2 uptodate
spfquery:amd64/stretch 1.2.10-7+b2 uptodate

Running the same on an Ubuntu 17.10 always succeeds;

$ spfquery --sender=some.u...@mdh.se --ip=2a01:0111:f400:fe1e::0712 
pass

spfquery: domain of mdh.se designates 2a01:111:f400:fe1e::712 as permitted 
sender
Received-SPF: pass (spfquery: domain of mdh.se designates 
2a01:111:f400:fe1e::712 as permitted sender) client-ip=2a01:111:f400:fe1e::712; 
envelope-from=some.u...@mdh.se;

$ apt-show-versions spfquery libspf2-2
libspf2-2:amd64/artful 1.2.10-7build2 uptodate
libspf2-2:i386 not installed
spfquery:amd64/artful 1.2.10-7build2 uptodate
spfquery:i386 not installed


This leads me to believe there's a bug in debian's implementation.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Versions of packages spfquery depends on:
ii  libc6  2.24-11+deb9u1
ii  libspf2-2  1.2.10-7+b2

spfquery recommends no packages.

spfquery suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 87369--- End Message ---

Bug#890925: marked as done (acmetool FTBFS with golang-1.10-go: FAIL: TestRedirector)

[Debian Bug Tracking System]

Your message dated Sat, 17 Mar 2018 04:49:22 +
with message-id 
and subject line Bug#890925: fixed in acmetool 0.0.62-2
has caused the Debian Bug report #890925,
regarding acmetool FTBFS with golang-1.10-go: FAIL: TestRedirector
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.)


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

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

...
=== RUN   TestRedirector
20190325090136 [DEBUG] acme.redirector: redirector running
2019/03/25 09:01:36 http: panic serving 127.0.0.1:34622: invalid WriteHeader 
code 0
goroutine 50 [running]:
net/http.(*conn).serve.func1(0xc4201e4000)
/usr/lib/go-1.10/src/net/http/server.go:1726 +0xd0
panic(0x6a37e0, 0xc420202060)
/usr/lib/go-1.10/src/runtime/panic.go:505 +0x229
net/http.checkWriteHeaderCode(0x0)
/usr/lib/go-1.10/src/net/http/server.go:1070 +0xf3
net/http.(*response).WriteHeader(0xc42023, 0x0)
/usr/lib/go-1.10/src/net/http/server.go:1083 +0x67
github.com/hlandau/acme/redirector.(*Redirector).handleRedirect(0xc420186000, 
0x759920, 0xc42023, 0xc420218000)

acmetool_0.0.62-1/obj-x86_64-linux-gnu/src/github.com/hlandau/acme/redirector/redirector.go:205
 +0x17f
github.com/hlandau/acme/redirector.(*Redirector).(github.com/hlandau/acme/redirector.handleRedirect)-fm(0x759920,
 0xc42023, 0xc420218000)

acmetool_0.0.62-1/obj-x86_64-linux-gnu/src/github.com/hlandau/acme/redirector/redirector.go:148
 +0x48
net/http.HandlerFunc.ServeHTTP(0xc4200aacf0, 0x759920, 0xc42023, 
0xc420218000)
/usr/lib/go-1.10/src/net/http/server.go:1947 +0x44
net/http.(*ServeMux).ServeHTTP(0xc4200b1110, 0x759920, 0xc42023, 
0xc420218000)
/usr/lib/go-1.10/src/net/http/server.go:2337 +0x130
github.com/hlandau/acme/redirector.(*Redirector).commonHandler.func1(0x759920, 
0xc42023, 0xc420218000)

acmetool_0.0.62-1/obj-x86_64-linux-gnu/src/github.com/hlandau/acme/redirector/redirector.go:134
 +0xfd
net/http.HandlerFunc.ServeHTTP(0xc42013c3e0, 0x759920, 0xc42023, 
0xc420218000)
/usr/lib/go-1.10/src/net/http/server.go:1947 +0x44
net/http.serverHandler.ServeHTTP(0xc4200b31e0, 0x759920, 0xc42023, 
0xc420218000)
/usr/lib/go-1.10/src/net/http/server.go:2694 +0xbc
net/http.(*conn).serve(0xc4201e4000, 0x759b60, 0xc420200040)
/usr/lib/go-1.10/src/net/http/server.go:1830 +0x651
created by net/http.(*Server).Serve
/usr/lib/go-1.10/src/net/http/server.go:2795 +0x27b
--- FAIL: TestRedirector (0.00s)
redirector_test.go:42: EOF
FAIL
FAILgithub.com/hlandau/acme/redirector  0.011s
?   github.com/hlandau/acme/responder   [no test files]
?   github.com/hlandau/acme/solver  [no test files]
=== RUN   TestKeyID
--- PASS: TestKeyID (0.52s)
PASS
ok  github.com/hlandau/acme/storage 0.531s
?   github.com/hlandau/acme/storageops  [no test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 16 -run 
^Test\(\[^O\]\|O\[^C\]\|OC\[^S\]\|OCS\[^P\]\) github.com/hlandau/acme/acmeapi 
github.com/hlandau/acme/acmeapi/acmeendpoints 
github.com/hlandau/acme/acmeapi/acmeutils github.com/hlandau/acme/cmd/acmetool 
github.com/hlandau/acme/fdb github.com/hlandau/acme/hooks 
github.com/hlandau/acme/interaction github.com/hlandau/acme/redirector 
github.com/hlandau/acme/responder github.com/hlandau/acme/solver 
github.com/hlandau/acme/storage github.com/hlandau/acme/storageops returned 
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: acmetool
Source-Version: 0.0.62-2

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

Debian distribution maintenance software
pp.
Peter Colberg  (supplier of updated acmetool 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: 

Bug#893169: marked as done (rkhunter won't update definitions: Invalid WEB_CMD)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 21:29:13 -0700
with message-id <20180317042913.ga4...@akranes.dyn.fmarier.org>
and subject line Re: Bug#893169: rkhunter won't update definitions: Invalid 
WEB_CMD
has caused the Debian Bug report #893169,
regarding rkhunter won't update definitions: Invalid WEB_CMD
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.)


-- 
893169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: rkhunter
version: 1.4.2-6+deb9u1
severity: grave

When trying to do rkhunter --update it returns the following:

Invalid WEB_CMD configuration option: Relative pathname: "/bin/false"

wget is installed as per the manpage suggestion for using the --update argument
--- End Message ---
--- Begin Message ---
On 2018-03-16 at 23:32:41, Chillfan wrote:
> When trying to do rkhunter --update it returns the following:
> 
> Invalid WEB_CMD configuration option: Relative pathname: "/bin/false"

This is actually intended. The update mechanism is not secure and therefore
is disabled in Debian.

See bug #893169 for the details.

Francois

-- 
https://fmarier.org/--- End Message ---

Bug#893169: rkhunter won't update definitions: Invalid WEB_CMD

[Chillfan]

package: rkhunter
version: 1.4.2-6+deb9u1
severity: grave

When trying to do rkhunter --update it returns the following:

Invalid WEB_CMD configuration option: Relative pathname: "/bin/false"

wget is installed as per the manpage suggestion for using the --update argument

Bug#893167: Stack smashing protection trigged in eboard

[Chillfan]

Package: eboard
Version: 1.1.1-6.1+b1
Severity: grave

Bug is present in stable/stretch, others not tested.

Stock 4.9 kernel on amd64.

If you need any more info than this please let me know. I've been able to 
reproduce on two different systems both amd64.

To reproduce:

When eboard is started go to settings > preferences > click squares to change 
the colours for > choose any colour from the palet> click OK

This will result in a crash.

The output:

\*\*\* stack smashing detected ***: eboard terminated

=== Backtrace: =

/lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)\[0x7f8923036bfb\]

/lib/x86\_64-linux-gnu/libc.so.6(\_\_fortify_fail+0x37)\[0x7f89230bf1f7\]

/lib/x86\_64-linux-gnu/libc.so.6(\_\_fortify_fail+0x0)\[0x7f89230bf1c0\]

eboard(+0x92e8c)\[0x55aeeb1fce8c\]

/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0(g\_closure_invoke+0x145)\[0x7f8924645f75\]

/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x21f82)\[0x7f8924657f82\]

/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0(g\_signal\_emit\_valist+0xe3c)\[0x7f8924660bdc\]

/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0(g\_signal_emit+0x8f)\[0x7f8924660fbf\]

/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x8d0c5)\[0x7f8925d2e0c5\]

/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0(g\_closure_invoke+0x145)\[0x7f8924645f75\]

/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x2195c)\[0x7f892465795c\]

/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0(g\_signal\_emit\_valist+0xe3c)\[0x7f8924660bdc\]

/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0(g\_signal_emit+0x8f)\[0x7f8924660fbf\]

/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x8c029)\[0x7f8925d2d029\]

/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x1317bc)\[0x7f8925dd27bc\]

/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0(g\_closure_invoke+0x145)\[0x7f8924645f75\]

/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x2237d)\[0x7f892465837d\]

/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0(g\_signal\_emit\_valist+0x8df)\[0x7f892466067f\]

/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0(g\_signal_emit+0x8f)\[0x7f8924660fbf\]

/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x2498ac)\[0x7f8925eea8ac\]

/usr/lib/x86\_64-linux-gnu/libgtk-x11-2.0.so.0(gtk\_propagate_event+0xc4)\[0x7f8925dd0f84\]

/usr/lib/x86\_64-linux-gnu/libgtk-x11-2.0.so.0(gtk\_main\_do\_event+0x2cb)\[0x7f8925dd133b\]

/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x5acbc)\[0x7f8925a46cbc\]

/lib/x86\_64-linux-gnu/libglib-2.0.so.0(g\_main\_context\_dispatch+0x2a7)\[0x7f892436c7f7\]

/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4aa60)\[0x7f892436ca60\]

/lib/x86\_64-linux-gnu/libglib-2.0.so.0(g\_main\_loop\_run+0xc2)\[0x7f892436cd82\]

/usr/lib/x86\_64-linux-gnu/libgtk-x11-2.0.so.0(gtk\_main+0xb7)\[0x7f8925dd03b7\]

eboard(+0x25cb2)\[0x55aeeb18fcb2\]

/lib/x86\_64-linux-gnu/libc.so.6(\_\_libc\_start\_main+0xf1)\[0x7f8922fe62e1\]

eboard(+0x2645a)\[0x55aeeb19045a\]

=== Memory map: 

55aeeb16a000-55aeeb23 r-xp  fe:01 1179928    
/usr/games/eboard

55aeeb42f000-55aeeb433000 r--p 000c5000 fe:01 1179928    
/usr/games/eboard

55aeeb433000-55aeeb43c000 rw-p 000c9000 fe:01 1179928    
/usr/games/eboard

55aeeb43c000-55aeeb441000 rw-p  00:00 0

55aeec46d000-55aeec835000 rw-p  00:00 0  
\[heap\]

7f891e2f5000-7f891e3f5000 rw-s  00:05 421101572  
/SYSV (deleted)

7f891e3f5000-7f891e449000 r--p  fe:01 1310053    
/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf

7f891e449000-7f891e46c000 rw-p  00:00 0

7f891e4af000-7f891e55c000 r--p  fe:01 1310050    
/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf

7f891e55c000-7f891e615000 r--p  fe:01 1310051    
/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf

7f891e659000-7f891e6b9000 rw-s  00:05 419561475  
/SYSV (deleted)

7f891e6b9000-7f891e6bf000 r-xp  fe:01 1184048    
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so

7f891e6bf000-7f891e8be000 ---p 6000 fe:01 1184048    
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so

7f891e8be000-7f891e8bf000 r--p 5000 fe:01 1184048    
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so

7f891e8bf000-7f891e8c rw-p 6000 fe:01 1184048    
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so

7f891e8c-7f891e8c4000 r-xp  fe:01 261221 
/lib/x86_64-linux-gnu/libuuid.so.1.3.0

7f891e8c4000-7f891eac3000 ---p 4000 fe:01 261221 
/lib/x86_64-linux-gnu/libuuid.so.1.3.0

7f891eac3000-7f891eac4000 r--p 3000 fe:01 261221 
/lib/x86_64-linux-gnu/libuuid.so.1.3.0

7f891eac4000-7f891eac5000 rw-p 4000 fe:01 261221 

Processed: closing 892738

[Debian Bug Tracking System]

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

> close 892738
Bug #892738 [consolekit] consolekit: consolekit removal causes a regression
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#892738: consolekit: consolekit removal causes a regression

[Michael Biebl]

On Mon, 12 Mar 2018 12:51:35 +0100 Benedikt Spranger
 wrote:
> Package: consolekit
> Version: 0.4.6-6
> Severity: serious
> 
> Dear Maintainer,
> 
> please readd consolekit to the archive. Without consolekit the
> dependency to libpam-systemd as alternative to consolekit forces me to
> install systemd without any further benefit.
> 
> Since my systems works fine before (and till now, since consolekit
> 0.4.6-6 is installed) the removal of consolekit from the archive causes
> a regression. As my understanding of init system dependencies this is a
> serious bug, since it forces a dependency to a special system init
> system without any need. 

This is incorrect. The removal of consolekit does not enforce a switch
to a different init system. You are probably mistaking systemd with
systemd-sysv. Please read the package descriptions carefully.

So please readd consolekit to the archive.

Since this bug report is based on a false premise, I'm closing it.
Please read why consolekit was removed from Linux-architectures in the
first place.



-- 
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#890939: marked as done (etcd FTBFS)

[Debian Bug Tracking System]

Your message dated Sat, 17 Mar 2018 01:35:26 +
with message-id 
and subject line Bug#890939: fixed in etcd 3.2.17+dfsg-1
has caused the Debian Bug report #890939,
regarding etcd FTBFS
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.)


-- 
890939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: etcd
Version: 3.2.9+dfsg-3
Severity: serious
Control: affects -1 src:docker-libkv src:golang-github-spf13-viper 
src:golang-github-xordataexchange-crypt src:skydns

Some recent change in unstable makes etcd FTBFS:

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

...
github.com/coreos/etcd/mvcc
# github.com/coreos/etcd/etcdserver/api/v3election/v3electionpb/gw
src/github.com/coreos/etcd/etcdserver/api/v3election/v3electionpb/gw/v3election.pb.gw.go:147:39:
 not enough arguments in call to runtime.AnnotateContext
have ("golang.org/x/net/context".Context, *http.Request)
want ("golang.org/x/net/context".Context, *runtime.ServeMux, 
*http.Request)
src/github.com/coreos/etcd/etcdserver/api/v3election/v3electionpb/gw/v3election.pb.gw.go:149:21:
 not enough arguments in call to runtime.HTTPError
have ("golang.org/x/net/context".Context, runtime.Marshaler, 
http.ResponseWriter, *http.Request, error)
want ("golang.org/x/net/context".Context, *runtime.ServeMux, 
runtime.Marshaler, http.ResponseWriter, *http.Request, error)
src/github.com/coreos/etcd/etcdserver/api/v3election/v3electionpb/gw/v3election.pb.gw.go:154:21:
 not enough arguments in call to runtime.HTTPError
have ("golang.org/x/net/context".Context, runtime.Marshaler, 
http.ResponseWriter, *http.Request, error)
want ("golang.org/x/net/context".Context, *runtime.ServeMux, 
runtime.Marshaler, http.ResponseWriter, *http.Request, error)
src/github.com/coreos/etcd/etcdserver/api/v3election/v3electionpb/gw/v3election.pb.gw.go:158:30:
 not enough arguments in call to forward_Election_Campaign_0
have ("golang.org/x/net/context".Context, runtime.Marshaler, 
http.ResponseWriter, *http.Request, proto.Message, 
[]func("golang.org/x/net/context".Context, http.ResponseWriter, proto.Message) 
error...)
want ("golang.org/x/net/context".Context, *runtime.ServeMux, 
runtime.Marshaler, http.ResponseWriter, *http.Request, proto.Message, 
...func("golang.org/x/net/context".Context, http.ResponseWriter, proto.Message) 
error)
src/github.com/coreos/etcd/etcdserver/api/v3election/v3electionpb/gw/v3election.pb.gw.go:175:39:
 not enough arguments in call to runtime.AnnotateContext
have ("golang.org/x/net/context".Context, *http.Request)
want ("golang.org/x/net/context".Context, *runtime.ServeMux, 
*http.Request)
src/github.com/coreos/etcd/etcdserver/api/v3election/v3electionpb/gw/v3election.pb.gw.go:177:21:
 not enough arguments in call to runtime.HTTPError
have ("golang.org/x/net/context".Context, runtime.Marshaler, 
http.ResponseWriter, *http.Request, error)
want ("golang.org/x/net/context".Context, *runtime.ServeMux, 
runtime.Marshaler, http.ResponseWriter, *http.Request, error)
src/github.com/coreos/etcd/etcdserver/api/v3election/v3electionpb/gw/v3election.pb.gw.go:182:21:
 not enough arguments in call to runtime.HTTPError
have ("golang.org/x/net/context".Context, runtime.Marshaler, 
http.ResponseWriter, *http.Request, error)
want ("golang.org/x/net/context".Context, *runtime.ServeMux, 
runtime.Marshaler, http.ResponseWriter, *http.Request, error)
src/github.com/coreos/etcd/etcdserver/api/v3election/v3electionpb/gw/v3election.pb.gw.go:186:30:
 not enough arguments in call to forward_Election_Proclaim_0
have ("golang.org/x/net/context".Context, runtime.Marshaler, 
http.ResponseWriter, *http.Request, proto.Message, 
[]func("golang.org/x/net/context".Context, http.ResponseWriter, proto.Message) 
error...)
want ("golang.org/x/net/context".Context, *runtime.ServeMux, 
runtime.Marshaler, http.ResponseWriter, *http.Request, proto.Message, 
...func("golang.org/x/net/context".Context, http.ResponseWriter, proto.Message) 
error)
src/github.com/coreos/etcd/etcdserver/api/v3election/v3electionpb/gw/v3election.pb.gw.go:203:39:
 not enough arguments in call to runtime.AnnotateContext
have ("golang.org/x/net/context".Context, *http.Request)
want ("golang.org/x/net/context".Context, *runtime.ServeMux, 
*http.Request)

Bug#893097: marked as done (lynkeos.app: FTBFS on many architectures - PAGE_SIZE undeclared)

[Debian Bug Tracking System]

Your message dated Sat, 17 Mar 2018 01:04:33 +
with message-id 
and subject line Bug#893097: fixed in lynkeos.app 2.10+dfsg1-2
has caused the Debian Bug report #893097,
regarding lynkeos.app: FTBFS on many architectures - PAGE_SIZE undeclared
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.)


-- 
893097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lynkeos.app
Version: 2.10+dfsg1-1
Severity: serious
Tags: sid buster

Hi,

lynkeos.app FTBFS on many architectures (all except for x86, s390x and
alpha) with the error:
> /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyCachePrefs.m: In 
> function '-[MyCachePrefs(Private) initPrefs]':
> /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyCachePrefs.m:60:33: 
> error: 'PAGE_SIZE' undeclared (first use in this function); did you mean 
> '_GSC_SIZE'?
> memSize = get_phys_pages() * PAGE_SIZE;
>  ^
>  _GSC_SIZE
> /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyCachePrefs.m:60:33: 
> note: each undeclared identifier is reported only once for each function it 
> appears in
> make[5]: *** [/usr/share/GNUstep/Makefiles/rules.make:479: 
> obj/Lynkeos.obj/MyCachePrefs.m.o] Error 1
> make[5]: *** Waiting for unfinished jobs
> gcc 
> /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/LynkeosStandardImageBuffer.m
>  -c \
>   -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I.. 
> -I/<>/lynkeos.app-2.10+dfsg1/GNUstep.. 
> -I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources 
> -I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThreadConnectionSources 
> -I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThirdPartySources/SMDoubleSlider
>  -DNO_FRAMEWORK_CHECK=1 -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 
> -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 
> -fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS 
> -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -O2 -g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime 
> -Wno-unknown-pragmas -Wno-cpp -fconstant-string-class=NSConstantString -I. 
> -I/usr/local/include/GNUstep -I/usr/include/GNUstep \
>-o obj/Lynkeos.obj/LynkeosStandardImageBuffer.m.o
> make[4]: *** [/usr/share/GNUstep/Makefiles/Instance/application.make:147: 
> internal-app-run-compile-submake] Error 2
> make[3]: *** [/usr/share/GNUstep/Makefiles/Master/rules.make:297: 
> Lynkeos.all.app.variables] Error 2
> make[2]: *** [/usr/share/GNUstep/Makefiles/Master/application.make:38: 
> internal-all] Error 2
> dh_auto_build: cd GNUstep && make -j2 -O "INSTALL=install 
> --strip-program=true" messages=yes "CFLAGS=-g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security" 
> "CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2" "CXXFLAGS=-g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security" "FCFLAGS=-g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong" "FFLAGS=-g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong" "GCJFLAGS=-g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong" "LDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--no-undefined 
> -Wl,--as-needed" "OBJCFLAGS=-g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security" "OBJCXXFLAGS=-g 
> -O2 -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security" returned exit code 
> 2
> make[1]: *** [debian/rules:15: override_dh_auto_build] Error 25
> make[1]: Leaving directory '/<>/lynkeos.app-2.10+dfsg1'
> make: *** [debian/rules:12: build-arch] Error 2
> dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
> status 2

There are two problems here:

PAGE_SIZE is not necessarily a constant. For example, MIPS kernels can
be compiled with different flags to change the page size. If you need to
use the page size, you should use sysconf(_SC_PAGESIZE) instead which
will calculate it at runtime.

In this case, the PAGE_SIZE constant is provided by . The
entire contents of this header is highly architecture specific and
portable applications should not include it at all.

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: lynkeos.app

Bug#891698: cause removed, but not closing it myself

[Adam Borowski]

I wrote:
> The daemon's init script has the following line:
> apm_available || exit 0
> which makes it always silently fail, as apm_available contains:

> # APM support was removed from kernel 2.6.40 in 2011.
> exit 1

> The comment is untrue:
> ./config/i386/config:CONFIG_APM=m
> but regardless whether APM still works or not, the daemon will not.

I've changed apm_available to actually check /proc/apm again, which on the
face value fixes this bug.  However: the daemon was completely unusable for
4 years, yet no one said a thing.  Thus, I'll leave it to you to actually
close the bug (or do nothing and let the package get autoremoved from
Buster).

Also, laptops have a much shorter lifespan than desktops or servers: the
chances of a 20 years battery to still work are about nil, other components
are also more fragile and harder to replace.  Thus, if any such laptops are
still alive, they probably are stationary, thus without much use for APM.

Having APM in the kernel is still useful (needed for poweroff), but, with no
one noticing the daemon broken, you might consider sending it off to a nice
pasture.  You know your package far better than me...


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.

Processed: Re: [scidavis] Future Qt4 removal from Buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #875251 [src:scidavis] [scidavis] Future Qt4 removal from Buster
Bug #875257 [src:scidavis] [scidavis] Future Qt4 removal from Buster
Severity set to 'grave' from 'wishlist'
Severity set to 'grave' from 'wishlist'
> tags -1 sid
Bug #875251 [src:scidavis] [scidavis] Future Qt4 removal from Buster
Bug #875257 [src:scidavis] [scidavis] Future Qt4 removal from Buster
Added tag(s) sid.
Added tag(s) sid.

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

Bug#882934: Crash debugging

[Dima Kogan]

Let's move this back to the bug list.

Thanks for the debugging traces. I didn't see any smoking gun, but
there're things I'd like to follow-up on to isolate the issue and then
to hopefully allow me to reproduce it.

1. You have a customized gtk configuration that uses a theme no longer
   in Debian. Can you please try to rename your ~/.gtkrc-2.0 file to
   something else to see if that makes the crash go away? I'm guessing
   this doesn't matter, but checking would be good.

2. The crash makes me suspect that something related to graphics is at
   fault. You have a radeon graphics card of some sort it looks like,
   which could explain why I can't reproduce (my hardware is different).
   How old/new is your graphics drivers? Can you try to run pcb without
   hardware acceleration? You can do this with

 LIBGL_ALWAYS_SOFTWARE=true pcb-gtk

   Also please try

 LIBGL_ALWAYS_INDIRECT=true pcb-gtk

Hopefully one of these resolves the crash, which would tell us where to
look next.

Thanks!

Bug#888189: [DRE-maint] Bug#888189: ruby-innertube: FTBFS on ruby2.5: undefined method mock

[Hector Oron]

Hello,

2018-03-16 23:05 GMT+01:00 Georg Faerber :
> On 18-01-23 20:31:56, Chris West (Faux) wrote:
>> This package fails to build against ruby2.5. Soon, there will be a
>> transition to ruby2.5, and this package will FTBFS in sid.
>
> Upstream seems rather dead, popcon lists 11 installations.

Indeed, upstream seems dead.

> @Héctor: You've tagged this help: Are you using it personally, or DSA?

Open Build Service (obs-api) needs it for the webUI ruby on rails
application, that's why I am interested on getting it fixed.

It has nothing to do with DSA, for those see
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-ad...@lists.debian.org

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.



-- Would you like to make a donation towards the upcoming Debian conference?
   Brochure: 
https://media.debconf.org/dc18/fundraising/debconf18_sponsorship_brochure_en.pdf

   ** https://debconf18.debconf.org/sponsors/become-a-sponsor/ **

Bug#893158: httpunit FTBFS with openjdk-9

[Adrian Bunk]

Source: httpunit
Version: 1.7+dfsg-12
Severity: serious
Tags: buster sid

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

...
compile:
[mkdir] Created dir: /build/1st/httpunit-1.7+dfsg/build/classes
[javac] /build/1st/httpunit-1.7+dfsg/build.xml:136: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 195 source files to 
/build/1st/httpunit-1.7+dfsg/build/classes
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.source 1.5 is no longer supported, switching 
to 1.6
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/httpunit-1.7+dfsg/src/com/meterware/httpunit/HttpWebResponse.java:92:
 error: unmappable character (0xF6) for encoding US-ASCII
[javac] // by Roger Lindsj?
[javac]   ^
[javac] 
/build/1st/httpunit-1.7+dfsg/src/com/meterware/servletunit/ServletUnitServletContext.java:127:
 error: unmappable character (0xE4) for encoding US-ASCII
[javac] // by Timo Westk?mper
[javac] ^
[javac] 2 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/httpunit-1.7+dfsg/build.xml:136: Compile failed; see the compiler 
error output for details.

Total time: 2 seconds
make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1

Bug#892956: Request for testing

[Jussi Pakkanen]

Hi

We have a proposed patch (not yet ready for merging but almost there)
available here:

https://github.com/mesonbuild/meson/pull/3251

Could people who who encountered this issue test if that fixes the
issue for them? Thanks.

Also, earlier in this someone said this:

> -llibinput-util would be liblibinput-util.a, that's clearly bogus.

That's not actually true. If you look at the build definitions of
libinput, it uses the following declaration:

static_library('libinput-util', ...

Meson automatically adds the library prefix to the target name so the
file name is indeed "liblibinput-util" and the contents of the
pkg-config file are correct in this regard (of course the library
should not be in the output at all but that is a different issue).

Bug#893153: geronimo-interceptor-3.0-spec FTBFS with openjdk-9

[Adrian Bunk]

Source: geronimo-interceptor-3.0-spec
Version: 1.0.1-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/geronimo-interceptor-3.0-spec.html

...
compile:
[mkdir] Created dir: 
/build/1st/geronimo-interceptor-3.0-spec-1.0.1/build/classes
[javac] /build/1st/geronimo-interceptor-3.0-spec-1.0.1/debian/build.xml:31: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Using javac -target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 7 source files to 
/build/1st/geronimo-interceptor-3.0-spec-1.0.1/build/classes
[javac] 
/build/1st/geronimo-interceptor-3.0-spec-1.0.1/src/main/java/javax/interceptor/InterceptorBinding.java:31:
 error: unmappable character (0xC2) for encoding US-ASCII
[javac]  * @version $Rev$??$Id: InterceptorBindingType.java 782259 
2009-06-06 13:31:32Z gerdogdu $
[javac]  ^
[javac] 
/build/1st/geronimo-interceptor-3.0-spec-1.0.1/src/main/java/javax/interceptor/InterceptorBinding.java:31:
 error: unmappable character (0xA0) for encoding US-ASCII
[javac]  * @version $Rev$??$Id: InterceptorBindingType.java 782259 
2009-06-06 13:31:32Z gerdogdu $
[javac]   ^
[javac] 2 errors

BUILD FAILED
/build/1st/geronimo-interceptor-3.0-spec-1.0.1/debian/build.xml:31: Compile 
failed; see the compiler error output for details.

Total time: 36 seconds
make: *** [/usr/share/cdbs/1/class/ant.mk:39: debian/stamp-ant-build] Error 1

Bug#888189: [DRE-maint] Bug#888189: ruby-innertube: FTBFS on ruby2.5: undefined method mock

[Georg Faerber]

On 18-01-23 20:31:56, Chris West (Faux) wrote:
> This package fails to build against ruby2.5. Soon, there will be a
> transition to ruby2.5, and this package will FTBFS in sid.

Upstream seems rather dead, popcon lists 11 installations.
@Héctor: You've tagged this help: Are you using it personally, or DSA?

Cheers,
Georg


signature.asc
Description: Digital signature

Processed: affects 873227

[Debian Bug Tracking System]

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

> affects 873227 src:freeplane
Bug #873227 [src:gradle] Please upgrade to 4.1: Java 9 support
Added indication that 873227 affects src:freeplane
> thanks
Stopping processing here.

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

Bug#893150: fop FTBFS with openjdk-9

[Adrian Bunk]

Source: fop
Version: 1:2.1-7
Severity: serious

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

...
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/complexscripts/bidi/DelimitedTextRange.java:41:
 error: unmappable character (0xC2) for encoding US-ASCII
[javac]  * by XML-FO 1.1 ??5.8, which contains a flattened sequence of 
characters. Any FO that generates
[javac]  ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/complexscripts/bidi/DelimitedTextRange.java:41:
 error: unmappable character (0xA7) for encoding US-ASCII
[javac]  * by XML-FO 1.1 ??5.8, which contains a flattened sequence of 
characters. Any FO that generates
[javac]   ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/intermediate/ArcToBezierCurveTransformer.java:50:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac] //  Drawing an elliptical arc using polylines, 
quadratic or cubic B??zier curves
[javac] 
   ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/intermediate/ArcToBezierCurveTransformer.java:50:
 error: unmappable character (0xA9) for encoding US-ASCII
[javac] //  Drawing an elliptical arc using polylines, 
quadratic or cubic B??zier curves
[javac] 
^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/TableAttributesConverter.java:39:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * Boris Poud??rous (boris.pouder...@eads-telecom.com),
[javac]  ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/TableAttributesConverter.java:39:
 error: unmappable character (0xA9) for encoding US-ASCII
[javac]  * Boris Poud??rous (boris.pouder...@eads-telecom.com),
[javac]   ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/TableAttributesConverter.java:40:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * Normand Mass??, and
[javac]^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/TableAttributesConverter.java:40:
 error: unmappable character (0xA9) for encoding US-ASCII
[javac]  * Normand Mass??, and
[javac] ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/TextAttributesConverter.java:55:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * Boris Poud??rous (boris.pouder...@eads-telecom.com),
[javac]  ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/TextAttributesConverter.java:55:
 error: unmappable character (0xA9) for encoding US-ASCII
[javac]  * Boris Poud??rous (boris.pouder...@eads-telecom.com),
[javac]   ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/TextAttributesConverter.java:57:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * Normand Mass??,
[javac]^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/TextAttributesConverter.java:57:
 error: unmappable character (0xA9) for encoding US-ASCII
[javac]  * Normand Mass??,
[javac] ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/rtflib/rtfdoc/IRtfTableContainer.java:35:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * and Boris Poud??rous.
[javac]  ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/rtflib/rtfdoc/IRtfTableContainer.java:35:
 error: unmappable character (0xA9) for encoding US-ASCII
[javac]  * and Boris Poud??rous.
[javac]   ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/rtflib/rtfdoc/RtfAfterBeforeBase.java:111:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * @param tc added by Boris Poud??rous on july 2002 in order to 
process
[javac] ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/rtflib/rtfdoc/RtfAfterBeforeBase.java:111:
 error: unmappable character (0xA9) for encoding US-ASCII
[javac]  * @param tc added by Boris Poud??rous on july 2002 in order to 
process
[javac]  ^
[javac] 
/build/1st/fop-2.1/src/java/org/apache/fop/render/rtf/rtflib/rtfdoc/RtfContainer.java:44:
 error: unmappable character (0xC3) 

Bug#893149: ceph FTBFS with openjdk-9

[Adrian Bunk]

Source: ceph
Version: 10.2.5-7
Severity: serious
Tags: buster sid

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

...
Making all in java
make[4]: Entering directory '/build/1st/ceph-10.2.5/src/java'
export CLASSPATH=java/ ; \
javac -classpath java -source 1.5 -target 1.5 -Xlint:-options 
java/com/ceph/fs/*.java
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make[4]: *** [Makefile:647: java/com/ceph/fs/CephMount.class] Error 2

Bug#893143: easyconf FTBFS with openjdk-9

[Adrian Bunk]

Source: easyconf
Version: 0.9.5-5
Severity: serious
Tags: buster sid

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

...
compile:
[mkdir] Created dir: /build/1st/easyconf-0.9.5/target/classes
[javac] /build/1st/easyconf-0.9.5/build.xml:36: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 27 source files to 
/build/1st/easyconf-0.9.5/target/classes
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.source 1.5 is no longer supported, switching 
to 1.6
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/ClassParameter.java:25:
 error: unmappable character (0xE9) for encoding US-ASCII
[javac]  * M?todos de utilidad para trabajar con par?metros de 
configuraci?n que representan
[javac] ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/ClassParameter.java:25:
 error: unmappable character (0xE1) for encoding US-ASCII
[javac]  * M?todos de utilidad para trabajar con par?metros de 
configuraci?n que representan
[javac] ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/ClassParameter.java:25:
 error: unmappable character (0xF3) for encoding US-ASCII
[javac]  * M?todos de utilidad para trabajar con par?metros de 
configuraci?n que representan
[javac]   ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/ClassParameter.java:28:
 error: unmappable character (0xFA) for encoding US-ASCII
[javac]  * @author Jes?s J?imez Rodr?guez 
[javac]   ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/ClassParameter.java:28:
 error: unmappable character (0xE1) for encoding US-ASCII
[javac]  * @author Jes?s J?imez Rodr?guez 
[javac]   ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/ClassParameter.java:28:
 error: unmappable character (0xED) for encoding US-ASCII
[javac]  * @author Jes?s J?imez Rodr?guez 
[javac] ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/jmx/ComponentConfigurationDynamicMBean.java:49:
 error: unmappable character (0xEF) for encoding US-ASCII
[javac]  * @author Alvaro Gonz???lez
[javac]   ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/jmx/ComponentConfigurationDynamicMBean.java:49:
 error: unmappable character (0xBF) for encoding US-ASCII
[javac]  * @author Alvaro Gonz???lez
[javac]^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/jmx/ComponentConfigurationDynamicMBean.java:49:
 error: unmappable character (0xBD) for encoding US-ASCII
[javac]  * @author Alvaro Gonz???lez
[javac] ^
[javac] 9 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/easyconf-0.9.5/build.xml:36: Compile failed; see the compiler error 
output for details.

Total time: 9 seconds
make: *** [/usr/share/cdbs/1/class/ant.mk:39: debian/stamp-ant-build] Error 1

Bug#893144: entagged FTBFS with openjdk-9

[Adrian Bunk]

Source: entagged
Version: 0.35-5
Severity: serious
Tags: buster sid

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

...
compile:
[javac] /build/1st/entagged-0.35/build.xml:55: warning: 'includeantruntime' 
was not set, defaulting to build.sysclasspath=last; set to false for repeatable 
builds
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Compiling 338 source files
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] /build/1st/entagged-0.35/entagged/audioformats/AudioFile.java:3: 
error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] 
/build/1st/entagged-0.35/entagged/audioformats/AudioFileFilter.java:3: error: 
unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] /build/1st/entagged-0.35/entagged/audioformats/AudioFileIO.java:3: 
error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] /build/1st/entagged-0.35/entagged/audioformats/EncodingInfo.java:3: 
error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] /build/1st/entagged-0.35/entagged/audioformats/Tag.java:3: error: 
unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] /build/1st/entagged-0.35/entagged/audioformats/Tag.java:48: error: 
unmappable character (0xEB) for encoding US-ASCII
[javac]  * @author Rapha?l Slinckx
[javac] ^
[javac] /build/1st/entagged-0.35/entagged/audioformats/ape/ApeTag.java:3: 
error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] 
/build/1st/entagged-0.35/entagged/audioformats/ape/MonkeyFileReader.java:3: 
error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] 
/build/1st/entagged-0.35/entagged/audioformats/ape/MonkeyFileWriter.java:3: 
error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] 
/build/1st/entagged-0.35/entagged/audioformats/ape/util/ApeTagBinaryField.java:3:
 error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] 
/build/1st/entagged-0.35/entagged/audioformats/ape/util/ApeTagCreator.java:3: 
error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] 
/build/1st/entagged-0.35/entagged/audioformats/ape/util/ApeTagField.java:3: 
error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] 
/build/1st/entagged-0.35/entagged/audioformats/ape/util/ApeTagReader.java:3: 
error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] 
/build/1st/entagged-0.35/entagged/audioformats/ape/util/ApeTagTextField.java:3: 
error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] 
/build/1st/entagged-0.35/entagged/audioformats/ape/util/ApeTagWriter.java:3: 
error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] 
/build/1st/entagged-0.35/entagged/audioformats/ape/util/MonkeyDescriptor.java:3:
 error: unmappable character (0xEB) for encoding US-ASCII
[javac]  * Copyright (c) 2003-2005 Rapha?l Slinckx 
[javac] ^
[javac] 

Bug#893145: excalibur-logkit FTBFS with openjdk-9

[Adrian Bunk]

Source: excalibur-logkit
Version: 2.0-11
Severity: serious
Tags: buster sid

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

...
compile:
[mkdir] Created dir: /build/1st/excalibur-logkit-2.0/target/classes
[javac] /build/1st/excalibur-logkit-2.0/build.xml:34: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 61 source files to 
/build/1st/excalibur-logkit-2.0/target/classes
[javac] Using ant.build.javac.target 1.4 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.target 1.4 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.source 1.4 is no longer supported, switching 
to 1.6
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/ContextMap.java:32: 
error: unmappable character (0xEF) for encoding US-ASCII
[javac]  * caller ??? 
???-com.biz.MyCaller.method(MyCaller.java:18)
[javac]   ^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/ContextMap.java:32: 
error: unmappable character (0xBF) for encoding US-ASCII
[javac]  * caller ??? 
???-com.biz.MyCaller.method(MyCaller.java:18)
[javac]^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/ContextMap.java:32: 
error: unmappable character (0xBD) for encoding US-ASCII
[javac]  * caller ??? 
???-com.biz.MyCaller.method(MyCaller.java:18)
[javac] ^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/ContextMap.java:32: 
error: unmappable character (0xEF) for encoding US-ASCII
[javac]  * caller ??? 
???-com.biz.MyCaller.method(MyCaller.java:18)
[javac]   ^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/ContextMap.java:32: 
error: unmappable character (0xBF) for encoding US-ASCII
[javac]  * caller ??? 
???-com.biz.MyCaller.method(MyCaller.java:18)
[javac]^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/ContextMap.java:32: 
error: unmappable character (0xBD) for encoding US-ASCII
[javac]  * caller ??? 
???-com.biz.MyCaller.method(MyCaller.java:18)
[javac] ^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/ContextMap.java:33: 
error: unmappable character (0xEF) for encoding US-ASCII
[javac]  * source ??? ???-1.6.3.2:33
[javac]   ^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/ContextMap.java:33: 
error: unmappable character (0xBF) for encoding US-ASCII
[javac]  * source ??? ???-1.6.3.2:33
[javac]^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/ContextMap.java:33: 
error: unmappable character (0xBD) for encoding US-ASCII
[javac]  * source ??? ???-1.6.3.2:33
[javac] ^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/ContextMap.java:33: 
error: unmappable character (0xEF) for encoding US-ASCII
[javac]  * source ??? ???-1.6.3.2:33
[javac]   ^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/ContextMap.java:33: 
error: unmappable character (0xBF) for encoding US-ASCII
[javac]  * source ??? ???-1.6.3.2:33
[javac]^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/ContextMap.java:33: 
error: unmappable character (0xBD) for encoding US-ASCII
[javac]  * source ??? ???-1.6.3.2:33
[javac] ^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/Logger.java:298: error: 
unmappable character (0xEF) for encoding US-ASCII
[javac]  * Determine if messages of priority ???will be logged.
[javac]  ^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/Logger.java:298: error: 
unmappable character (0xBF) for encoding US-ASCII
[javac]  * Determine if messages of priority ???will be logged.
[javac]   ^
[javac] 
/build/1st/excalibur-logkit-2.0/src/java/org/apache/log/Logger.java:298: error: 
unmappable character (0xBD) for encoding US-ASCII
[javac]  * Determine if messages of priority ???will be logged.
[javac]^
[javac] 15 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/excalibur-logkit-2.0/build.xml:34: Compile failed; see the compiler 
error output for details.

Total time: 1 second

Bug#893110: gupnp-igd: FTBFS (randomly?) testsuite failures - gupnp-simple-igd SIGTRAP

[Jeremy Bicha]

On Fri, Mar 16, 2018 at 11:42 AM, James Cowgill  wrote:
> While it built on amd64 on the buildds, the package fails with the same
> error when I locally rebuild it. I notice it build fine on all the
> Ubuntu builders. I'm afraid I have no idea what is going on here.

Thank you for taking the time to file this bug.

I think the tests are flaky and I may have needed to retry some of
those builds on Ubuntu. It's a bit easier for an Ubuntu Developer to
retry builds than for a Debian Developer to do it in Debian.

I don't really care that much about this package and I intend to do
another upload where I just ignore test failures. (Before this upload,
the tests weren't even being run.)

Thanks,
Jeremy Bicha

Bug#893142: dogtag-pki FTBFS with openjdk-9

[Adrian Bunk]

Source: dogtag-pki
Version: 10.5.5-1
Severity: serious

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

...
netscape/security/x509/RevocationReasonAdapter.java:20: error: package 
javax.xml.bind.annotation.adapters is not visible
import javax.xml.bind.annotation.adapters.XmlAdapter;
^
  (package javax.xml.bind.annotation.adapters is declared in module 
java.xml.bind, which is not in the module graph)

Bug#893141: dumbster FTBFS with openjdk-9

[Adrian Bunk]

Source: dumbster
Version: 1.6+debian-3
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/dumbster-1.6+debian'
dh_auto_build -- test
ant -propertyfile ./debian/ant.properties -Duser.name debian test
Buildfile: /build/1st/dumbster-1.6+debian/build.xml

init:

compile-tests:
[javac] /build/1st/dumbster-1.6+debian/build.xml:82: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 4 source files to 
/build/1st/dumbster-1.6+debian/build/test

test:
[junit] Running com.dumbster.smtp.SimpleSmtpServerTest
[junit] Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 
0.233 sec

BUILD FAILED
/build/1st/dumbster-1.6+debian/build.xml:89: Test 
com.dumbster.smtp.SimpleSmtpServerTest failed

Total time: 3 seconds
dh_auto_build: ant -propertyfile ./debian/ant.properties -Duser.name debian 
test returned exit code 1
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 2

Bug#893132: marked as done (libvorbisidec: CVE-2018-5147: out-of-bounds memory write)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 20:55:03 +
with message-id 
and subject line Bug#893132: fixed in libvorbisidec 1.2.1+git20180316-1
has caused the Debian Bug report #893132,
regarding libvorbisidec: CVE-2018-5147: out-of-bounds memory write
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.)


-- 
893132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvorbisidec
Version: 1.0.2+svn18153-0.2
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for libvorbisidec.

CVE-2018-5147[0]:
out-of-bounds memory write

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-5147
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5147
[1] https://www.mozilla.org/en-US/security/advisories/mfsa2018-08/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libvorbisidec
Source-Version: 1.2.1+git20180316-1

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated libvorbisidec 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, 16 Mar 2018 21:00:36 +0100
Source: libvorbisidec
Binary: libvorbisidec-dev libvorbisidec1
Architecture: source
Version: 1.2.1+git20180316-1
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Julien Cristau 
Description:
 libvorbisidec-dev - Integer-only Ogg Vorbis decoder, AKA "tremor" (Development 
Files)
 libvorbisidec1 - Integer-only Ogg Vorbis decoder, AKA "tremor"
Closes: 893132
Changes:
 libvorbisidec (1.2.1+git20180316-1) unstable; urgency=high
 .
   * QA upload.
   * Update from upstream git.
   * Includes fix for CVE-2018-5147 (closes: #893132).
Checksums-Sha1:
 e0fd0abbc2195a84831dc121c94b71a01a768836 1959 
libvorbisidec_1.2.1+git20180316-1.dsc
 0650fb3b5387d769384fc55428c369c3290e64d5 147673 
libvorbisidec_1.2.1+git20180316.orig.tar.gz
 df8100f99b94ad0f6e20d3f6b562d647ca2cbab5 5733 
libvorbisidec_1.2.1+git20180316-1.diff.gz
Checksums-Sha256:
 4807cfb1380dc740089f96d3030b644c9a09d4070435ad4f0fdf8be4dacd7572 1959 
libvorbisidec_1.2.1+git20180316-1.dsc
 491b88661544f55b17154407420b5d78d2ac35d12786ee030d0925eb6aec03da 147673 
libvorbisidec_1.2.1+git20180316.orig.tar.gz
 a7041c6685ac38795f7cdfc41f7688443b959d04b9bd08236d836aa75501592e 5733 
libvorbisidec_1.2.1+git20180316-1.diff.gz
Files:
 a630e3d9a2b404b582345da9d4acfb65 1959 libs extra 
libvorbisidec_1.2.1+git20180316-1.dsc
 477c0b353fb9f9287b5133f19b1fd0c2 147673 libs extra 
libvorbisidec_1.2.1+git20180316.orig.tar.gz
 6116d60c3dc769f2d8b7cb906107b8c5 5733 libs extra 
libvorbisidec_1.2.1+git20180316-1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAlqsKGAACgkQnbAjVVb4
z61y+w//SPDHzvKBKTA4lcyI+Ha4sf5sgtE6YvmAXjgCEZjFYCrGTntgJT7+79o0
RI9uY5OliVNROCsNK+7M28fwKc6EB4qi4ovaAOQ4ERcON+OOiXhSP3/u6IlCTGo0
DlBtpcvBvTz5UPUtj3Rc+HBHDyyxmlOogo62JDeiRDU1RIg2hW49DNt/MTmY3tbL
eqSEy04k2IQVsaZIm55qAkadTg3xTLEGCUqdqC8DUIS1lhlXZ5mxPLyUvMLUXCyd
mqTfGZHXEDCCBs1rteyar0dEJRWKYaLDQTkhc57eQdtLKEVNlaGe2CqRg0kKfQrl
yujK/YDxVnc3v7A4nb09m+lGyjYug8p03Pm9DkK+6d+Jdd0q0KCuABik5cagCgg7
TQD67ynaMJvvg5N5o2H7augASlRm6u9HaQb8SLWPg9arYEL67z8LuWqWpKAKL27Z
zMGRG4gYdK+6azmKjVfxt0pM3FwKyuWAPKgDwBcqCas9M/T5jlLieG9cJaNzV9RR
hX3YkKr9IoNOwPC6wAHZfw9m2hTQjlj8Kq9XUQTdNQ1gugaONXaJBFoJuLLg10WR
63BTxSuetIzt0yP0wiq11gVE9qzfgQYOrIBWUMOATQhGB2tLdeTqD+szKINozB9A
MpmM6c0+ioHsdjpXhEkYaP9scQ5y7eMFe3O2vubIgskN1wNTx9U=
=1tXT
-END PGP SIGNATURE End Message ---

Processed: Pending fixes for bugs in the jabref package

[Debian Bug Tracking System]

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

> tag 890905 + pending
Bug #890905 [jabref] jabref: doesn't build/run with default-jdk/-jre
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: cloning 890905, retitle 890905 to jabref: doesn't build/run with default-jdk/-jre ...

[Debian Bug Tracking System]

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

> clone 890905 -1
Bug #890905 [jabref] jabref: fails to build and start with openjdk-9
Bug 890905 cloned as bug 893138
> retitle 890905 jabref: doesn't build/run with default-jdk/-jre
Bug #890905 [jabref] jabref: fails to build and start with openjdk-9
Changed Bug title to 'jabref: doesn't build/run with default-jdk/-jre' from 
'jabref: fails to build and start with openjdk-9'.
> severity -1 important
Bug #893138 [jabref] jabref: fails to build and start with openjdk-9
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#890905: Pending fixes for bugs in the jabref package

[pkg-java-maintainers]

tag 890905 + pending
thanks

Some bugs in the jabref package are closed in revision
eb5c1b0e2c48612c16198e34f244bea501e59e56 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jabref.git/commit/?id=eb5c1b0

Commit message:

Force openjdk-8 at buildtime and runtime.

JabRef doesn't work and run with openjdk-9 which is the default now.

Closes: #890905

Bug#893119: marked as done (tktreectl: FTBFS - ./configure not found)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 19:21:03 +
with message-id 
and subject line Bug#893119: fixed in tktreectrl 2.2.8-3
has caused the Debian Bug report #893119,
regarding tktreectl: FTBFS - ./configure not found
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.)


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

Hi,

tktreectl FTBFS everywhere with:
>  debian/rules build-arch
> dh_testdir
> cp -f /usr/share/misc/config.sub config.sub
> cp -f /usr/share/misc/config.guess config.guess
> ./configure --build aarch64-linux-gnu \
> --prefix=/usr \
> --mandir=\${prefix}/share/man \
> --infodir=\${prefix}/share/info \
> --with-tcl=/usr/lib \
> --with-tk=/usr/lib \
> --with-tclinclude=/usr/include/tcl \
> --with-tkinclude=/usr/include/tcl \
> CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security" \
> LDFLAGS="-lm -Wl,-z,defs -Wl,--no-undefined -Wl,--as-needed"
> /bin/sh: 1: ./configure: not found
> debian/rules:20: recipe for target 'config-stamp' failed
> make: *** [config-stamp] Error 127
> dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
> status 2

This was caused by this change:
> @@ -16,8 +18,6 @@
>  config: config-stamp
>  config-stamp: 
> dh_testdir
> -   $(MAKE) -f /usr/share/quilt/quilt.make patch
> -   autoreconf --force
>  ifneq "$(wildcard /usr/share/misc/config.sub)" ""
> cp -f /usr/share/misc/config.sub config.sub
>  endif

You need to keep the call to autoreconf.

Please consider converting the package to use dh or at least use
dh_autoreconf instead.

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: tktreectrl
Source-Version: 2.2.8-3

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

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated tktreectrl 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, 16 Mar 2018 21:55:53 +0300
Source: tktreectrl
Binary: tktreectrl
Architecture: source amd64
Version: 2.2.8-3
Distribution: unstable
Urgency: medium
Maintainer: Tcl/Tk Debian Packagers 
Changed-By: Sergei Golovan 
Description:
 tktreectrl - flexible listbox widget for Tcl/Tk
Closes: 893119
Changes:
 tktreectrl (2.2.8-3) unstable; urgency=medium
 .
   * Team upload.
   * Fix FTBFS because of deleting the configure script (closes: #893119).
Checksums-Sha1:
 714241bcbe91fda34c26d3d675dcf4d802e501b2 1944 tktreectrl_2.2.8-3.dsc
 94f2fcbbf0eff46e779138cdd3ee746037b3800f 34808 tktreectrl_2.2.8-3.debian.tar.xz
 2e8a67e1f289190381ce21fd3e9d3f4e2cc83e59 843756 
tktreectrl-dbgsym_2.2.8-3_amd64.deb
 92ffc21d3e14cf53ffdafdc403ae890f641fbdef 7370 
tktreectrl_2.2.8-3_amd64.buildinfo
 ff733a6721a158c61d9ab403e2a2053d6a6b03f4 259840 tktreectrl_2.2.8-3_amd64.deb
Checksums-Sha256:
 a8f212abea99bbca783481e50bb25eeb54b57bff5fad1f6cd52ae8e41d5f94fd 1944 
tktreectrl_2.2.8-3.dsc
 e198fb12f318a7ab3355cbebc31d43d1c56b1268b8d47112faafbec5592ecba3 34808 
tktreectrl_2.2.8-3.debian.tar.xz
 994f95f2ab008ef8ce46126e2eab44dfe996b9ef59276702ed57f781bb62d268 843756 
tktreectrl-dbgsym_2.2.8-3_amd64.deb
 996511034929dc813071885a9f4de2616ac1eec2287c1a4e98e8f0113be4011d 7370 
tktreectrl_2.2.8-3_amd64.buildinfo
 c770c2f78026da07c83d9c22342833e4b72685acd7bc02600bee05edb2ea9a66 259840 
tktreectrl_2.2.8-3_amd64.deb
Files:
 f32354491b902c8b0f5afce5f39ecc75 1944 devel optional tktreectrl_2.2.8-3.dsc
 7b17d9d2ef80a5bcc9b734de01408dee 34808 devel optional 
tktreectrl_2.2.8-3.debian.tar.xz
 352a08b64ebe7ee078feb995a4a8a745 843756 debug optional 
tktreectrl-dbgsym_2.2.8-3_amd64.deb
 7abc247613a6f1a2d2c65f22112a6ede 7370 devel optional 
tktreectrl_2.2.8-3_amd64.buildinfo
 944f9e4a8d85c9665ac5c812828c070a 

Processed: Re: Bug#892849: marked as done (cura: Exception while launching cura)

[Debian Bug Tracking System]

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

> notfound 892849 3.1.0-1
Bug #892849 {Done: Gregor Riepl } [cura] cura: Exception 
while launching cura
No longer marked as found in versions cura/3.1.0-1.
> thanks
Stopping processing here.

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

Bug#892849: marked as done (cura: Exception while launching cura)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 19:45:33 +0100
with message-id <1f256fd8-0060-b6a2-17d8-d99eb1c73...@gmail.com>
and subject line 
has caused the Debian Bug report #892849,
regarding cura: Exception while launching cura
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

While laaunching cura, I get the following:
Error in sys.excepthook:
Traceback (most recent call last):
  File "", line 983, in _find_and_load
  File "", line 967, in _find_and_load_unlocked
  File "", line 677, in _load_unlocked
  File "", line 678, in exec_module
  File "", line 219, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/cura/CrashHandler.py", line 20, in 

from UM.Application import Application
  File "/usr/lib/python3/dist-packages/UM/Application.py", line 15, in 
from UM.Settings.ContainerRegistry import ContainerRegistry
  File "/usr/lib/python3/dist-packages/UM/Settings/ContainerRegistry.py", line 
36, in 
import UM.Qt.QtApplication
  File "/usr/lib/python3/dist-packages/UM/Qt/QtApplication.py", line 15, in 

from UM.FileHandler.ReadFileJob import ReadFileJob
  File "/usr/lib/python3/dist-packages/UM/FileHandler/ReadFileJob.py", line 5, 
in 
from UM.Application import Application
ImportError: cannot import name 'Application'

Original exception was:
Traceback (most recent call last):
  File "/usr/bin/cura", line 54, in 
import Arcus #@UnusedImport
RuntimeError: the sip module implements API v12.0 to v12.2 but the Arcus module 
requires API v12.3


Regards

Jean-Luc


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

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

Versions of packages cura depends on:
ii  cura-engine 1:3.1.0-2
ii  fonts-open-sans 1.11-1
ii  python3 3.6.4-1
ii  python3-pyqt5   5.9.2+dfsg-1
ii  python3-pyqt5.qtopengl  5.9.2+dfsg-1
ii  python3-savitar 3.1.0-1
ii  python3-serial  3.4-1
ii  python3-uranium 3.1.0-1
ii  qml-module-qt-labs-folderlistmodel  5.9.2-3
ii  qml-module-qt-labs-settings 5.9.2-3
ii  qml-module-qtqml-models25.9.2-3
ii  qml-module-qtquick-controls 5.9.2-2
ii  qml-module-qtquick-dialogs  5.9.2-2
ii  uranium-plugins 3.1.0-1

Versions of packages cura recommends:
ii  fdm-materials 3.1.0-1
ii  python3-zeroconf  0.19.1-1

cura suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWqgdMQAKCRBR0YZfPMac
0E/FAJ41rnMVzefh1QCGodicZkcNUbPH5gCffL6QLGqTuOgyQOGxU/9uo1Gj/P4=
=nEEw
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 3.1.0-1

Bug not reproduceable, issue was fixed on the user side.--- End Message ---

Bug#893132: libvorbisidec: CVE-2018-5147: out-of-bounds memory write

[Salvatore Bonaccorso]

Source: libvorbisidec
Version: 1.0.2+svn18153-0.2
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for libvorbisidec.

CVE-2018-5147[0]:
out-of-bounds memory write

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-5147
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5147
[1] https://www.mozilla.org/en-US/security/advisories/mfsa2018-08/

Regards,
Salvatore

Processed: libvorbis: CVE-2018-5146: out-of-bounds memory write

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.3.4-2+deb8u1
Bug #893130 [src:libvorbis] libvorbis: CVE-2018-5146: out-of-bounds memory write
The source 'libvorbis' and version '1.3.4-2+deb8u1' do not appear to match any 
binary packages
Marked as fixed in versions libvorbis/1.3.4-2+deb8u1.
> fixed -1 1.3.5-4+deb9u2
Bug #893130 [src:libvorbis] libvorbis: CVE-2018-5146: out-of-bounds memory write
The source 'libvorbis' and version '1.3.5-4+deb9u2' do not appear to match any 
binary packages
Marked as fixed in versions libvorbis/1.3.5-4+deb9u2.

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

Bug#893130: libvorbis: CVE-2018-5146: out-of-bounds memory write

[Salvatore Bonaccorso]

Source: libvorbis
Version: 1.3.4-2
Severity: grave
Tags: patch security upstream
Control: fixed -1 1.3.4-2+deb8u1
Control: fixed -1 1.3.5-4+deb9u2

Hi,

the following vulnerability was published for libvorbis.

CVE-2018-5146[0]:
out-of-bounds memory write

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-5146
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5146
[1] https://www.mozilla.org/en-US/security/advisories/mfsa2018-08/
[2] 
https://git.xiph.org/?p=vorbis.git;a=commit;h=667ceb4aab60c1f74060143bb24e5f427b3cce5f

Regards,
Salvatore

Processed: affects 873227

[Debian Bug Tracking System]

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

> affects 873227 src:jcommander
Bug #873227 [src:gradle] Please upgrade to 4.1: Java 9 support
Added indication that 873227 affects src:jcommander
> thanks
Stopping processing here.

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

Bug#893129: dita-ot FTBFS with openjdk-9

[Adrian Bunk]

Source: dita-ot
Version: 1.5.3-2
Severity: serious
Tags: buster sid

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

...
compile:
 [copy] Copying 216 files to /build/1st/dita-ot-1.5.3/output2/build
[javac] /build/1st/dita-ot-1.5.3/buildPackage.xml:75: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Using javac -target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 133 source files to /build/1st/dita-ot-1.5.3/output2
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:332:
 error: unmappable character (0xE2) for encoding US-ASCII
[javac]  * token ::= ( alphanum | ???_??? | ???-??? )+
[javac]   ^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:332:
 error: unmappable character (0x80) for encoding US-ASCII
[javac]  * token ::= ( alphanum | ???_??? | ???-??? )+
[javac]^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:332:
 error: unmappable character (0x99) for encoding US-ASCII
[javac]  * token ::= ( alphanum | ???_??? | ???-??? )+
[javac] ^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:332:
 error: unmappable character (0xE2) for encoding US-ASCII
[javac]  * token ::= ( alphanum | ???_??? | ???-??? )+
[javac]   ^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:332:
 error: unmappable character (0x80) for encoding US-ASCII
[javac]  * token ::= ( alphanum | ???_??? | ???-??? )+
[javac]^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:332:
 error: unmappable character (0x99) for encoding US-ASCII
[javac]  * token ::= ( alphanum | ???_??? | ???-??? )+
[javac] ^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:332:
 error: unmappable character (0xE2) for encoding US-ASCII
[javac]  * token ::= ( alphanum | ???_??? | ???-??? )+
[javac] ^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:332:
 error: unmappable character (0x80) for encoding US-ASCII
[javac]  * token ::= ( alphanum | ???_??? | ???-??? )+
[javac]  ^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:332:
 error: unmappable character (0x99) for encoding US-ASCII
[javac]  * token ::= ( alphanum | ???_??? | ???-??? )+
[javac]   ^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:332:
 error: unmappable character (0xE2) for encoding US-ASCII
[javac]  * token ::= ( alphanum | ???_??? | ???-??? )+
[javac] ^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:332:
 error: unmappable character (0x80) for encoding US-ASCII
[javac]  * token ::= ( alphanum | ???_??? | ???-??? )+
[javac]  ^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:332:
 error: unmappable character (0x99) for encoding US-ASCII
[javac]  * token ::= ( alphanum | ???_??? | ???-??? )+
[javac]   ^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:343:
 error: unmappable character (0xE2) for encoding US-ASCII
[javac]  * qualifier ::= ( alphanum | ???_??? | '-' )+
[javac]   ^
[javac] 
/build/1st/dita-ot-1.5.3/output2/build/org/dita/dost/platform/Integrator.java:343:
 error: unmappable character (0x80) for encoding US-ASCII
[javac]  * qualifier ::= ( alphanum | ???_??? | '-' )+
[javac]^
[javac] 

Bug#893128: cortado FTBFS with openjdk-9

[Adrian Bunk]

Source: cortado
Version: 0.6.0-3
Severity: serious
Tags: buster sid

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

...
compile-jheora:
[javac] /build/1st/cortado-0.6.0/build.xml:337: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.3 is no longer supported, switching to 1.6
[javac] Using javac -target 1.1 is no longer supported, switching to 1.6
[javac] Compiling 26 source files to 
/build/1st/cortado-0.6.0/output/build/stripped
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:52: 
error: unmappable character (0xC3) for encoding US-ASCII
[javac] /* A 2 ?? 3 array containing the number of quant ranges for a
[javac]^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:52: 
error: unmappable character (0x97) for encoding US-ASCII
[javac] /* A 2 ?? 3 array containing the number of quant ranges for a
[javac] ^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:56: 
error: unmappable character (0xC3) for encoding US-ASCII
[javac] /* A 2 ?? 3 ?? 63 array of the sizes of each quant range for a
[javac]^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:56: 
error: unmappable character (0x97) for encoding US-ASCII
[javac] /* A 2 ?? 3 ?? 63 array of the sizes of each quant range for a
[javac] ^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:56: 
error: unmappable character (0xC3) for encoding US-ASCII
[javac] /* A 2 ?? 3 ?? 63 array of the sizes of each quant range for a
[javac] ^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:56: 
error: unmappable character (0x97) for encoding US-ASCII
[javac] /* A 2 ?? 3 ?? 63 array of the sizes of each quant range for a
[javac]  ^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:61: 
error: unmappable character (0xC3) for encoding US-ASCII
[javac] /* A 2 ?? 3 ?? 64 array of the bmi ???s used for each quant
[javac]^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:61: 
error: unmappable character (0x97) for encoding US-ASCII
[javac] /* A 2 ?? 3 ?? 64 array of the bmi ???s used for each quant
[javac] ^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:61: 
error: unmappable character (0xC3) for encoding US-ASCII
[javac] /* A 2 ?? 3 ?? 64 array of the bmi ???s used for each quant
[javac] ^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:61: 
error: unmappable character (0x97) for encoding US-ASCII
[javac] /* A 2 ?? 3 ?? 64 array of the bmi ???s used for each quant
[javac]  ^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:61: 
error: unmappable character (0xE2) for encoding US-ASCII
[javac] /* A 2 ?? 3 ?? 64 array of the bmi ???s used for each quant
[javac]^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:61: 
error: unmappable character (0x80) for encoding US-ASCII
[javac] /* A 2 ?? 3 ?? 64 array of the bmi ???s used for each quant
[javac] ^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:61: 
error: unmappable character (0x99) for encoding US-ASCII
[javac] /* A 2 ?? 3 ?? 64 array of the bmi ???s used for each quant
[javac]  ^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:283: 
error: unmappable character (0xE2) for encoding US-ASCII
[javac]   (2 ??? (QIEND ??? qi ) ??? BMS[bmi ][ci ]
[javac]  ^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:283: 
error: unmappable character (0x88) for encoding US-ASCII
[javac]   (2 ??? (QIEND ??? qi ) ??? BMS[bmi ][ci ]
[javac]   ^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:283: 
error: unmappable character (0x97) for encoding US-ASCII
[javac]   (2 ??? (QIEND ??? qi ) ??? BMS[bmi ][ci ]
[javac]^
[javac] /build/1st/cortado-0.6.0/src/com/fluendo/jheora/Quant.java:283: 
error: unmappable character (0xE2) for encoding US-ASCII
[javac]  

Processed: forcibly merging 888123 892798

[Debian Bug Tracking System]

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

> forcemerge 888123 892798
Bug #888123 {Done: Cédric Boutillier } [src:ruby-safe-yaml] 
ruby-crack: FTBFS on ruby2.5: uninitialized constant 
SafeYAML::Parse::Date::DateTime
Bug #888194 {Done: Cédric Boutillier } [src:ruby-safe-yaml] 
ruby-safe-yaml: FTBFS on ruby2.5: uninitialized constant 
SafeYAML::Parse::Date::DateTime
Bug #888194 {Done: Cédric Boutillier } [src:ruby-safe-yaml] 
ruby-safe-yaml: FTBFS on ruby2.5: uninitialized constant 
SafeYAML::Parse::Date::DateTime
Removed indication that 888194 affects ruby-crack and src:ruby-crack
Added indication that 888194 affects ruby-crack,src:ruby-crack
Removed indication that 888123 affects ruby-crack and src:ruby-crack
Added indication that 888123 affects ruby-crack,src:ruby-crack
Bug #892798 {Done: Cédric Boutillier } [src:ruby-safe-yaml] 
ruby-crack FTBFS uninitialized constant SafeYAML::Parse::Date::DateTime 
(NameError)
Set Bug forwarded-to-address to 'https://github.com/dtao/safe_yaml/issues/80'.
Added indication that 892798 affects ruby-crack,src:ruby-crack
Marked as fixed in versions ruby-safe-yaml/1.0.4-2.
Marked as found in versions ruby-safe-yaml/1.0.4-1.
Added tag(s) buster, fixed-upstream, upstream, and sid.
Merged 888123 888194 892798
> thanks
Stopping processing here.

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

Processed: reassign 892798 to src:ruby-safe-yaml

[Debian Bug Tracking System]

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

> reassign 892798 src:ruby-safe-yaml
Bug #892798 {Done: Cédric Boutillier } [ruby-safe-yaml] 
ruby-crack FTBFS uninitialized constant SafeYAML::Parse::Date::DateTime 
(NameError)
Bug reassigned from package 'ruby-safe-yaml' to 'src:ruby-safe-yaml'.
Ignoring request to alter found versions of bug #892798 to the same values 
previously set
Ignoring request to alter fixed versions of bug #892798 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#892798: closed by ruby-safe-yaml 1.0.4-2

[Cédric Boutillier]

Hi,
closing, as it has been fixed by uploading ruby-safe-yaml 1.0.4-2.
This bug is a duplicate of #888123.

Cheers,

Cédric


signature.asc
Description: PGP signature

Processed (with 1 error): forcibly merging 888123 892798

[Debian Bug Tracking System]

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

> forcemerge 888123 892798
Bug #888123 {Done: Cédric Boutillier } [src:ruby-safe-yaml] 
ruby-crack: FTBFS on ruby2.5: uninitialized constant 
SafeYAML::Parse::Date::DateTime
Bug #888194 {Done: Cédric Boutillier } [src:ruby-safe-yaml] 
ruby-safe-yaml: FTBFS on ruby2.5: uninitialized constant 
SafeYAML::Parse::Date::DateTime
Unable to merge bugs because:
package of #892798 is 'ruby-safe-yaml' not 'src:ruby-safe-yaml'
Failed to forcibly merge 888123: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: closing 892798

[Debian Bug Tracking System]

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

> close 892798
Bug #892798 [ruby-safe-yaml] ruby-crack FTBFS uninitialized constant 
SafeYAML::Parse::Date::DateTime (NameError)
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: scim-unikey: FTBFS with GCC 6: narrowing conversion

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #811766 [src:scim-unikey] scim-unikey: FTBFS with GCC 6: narrowing 
conversion
Bug #831158 [src:scim-unikey] scim-unikey: FTBFS with GCC 6: data.cpp:242:1: 
error: narrowing conversion of ''\3777670'' from 'char' to 'unsigned char' 
inside { } [-Wnarrowing]
Added tag(s) pending.
Added tag(s) pending.

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

Bug#811766: scim-unikey: FTBFS with GCC 6: narrowing conversion

[James Cowgill]

Control: tags -1 pending

Hi,

On Tue, 19 Jan 2016 17:55:39 -0800 Martin Michlmayr  wrote:
> Package: scim-unikey
> Version: 0.3.1+debian-3.1
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-6 gcc-6-narrowing
> 
> This package fails to build with GCC 6.  GCC 6 has not been released
> yet, but it's expected that GCC 6 will become the default compiler for
> stretch.

I've uploaded the attached NMU to DELAYED/2 which fixes this bug by
applying the upstream patch already mentioned in this bug report. I have
also taken the opportunity to add the mandatory build-{arch,indep}
targets to debian/rules. Please tell me if I should cancel it / delay it
longer.

Thanks,
James
diff -Nru scim-unikey-0.3.1+debian/debian/changelog 
scim-unikey-0.3.1+debian/debian/changelog
--- scim-unikey-0.3.1+debian/debian/changelog   2012-07-12 16:51:22.0 
+0100
+++ scim-unikey-0.3.1+debian/debian/changelog   2018-03-16 17:26:15.0 
+
@@ -1,3 +1,13 @@
+scim-unikey (0.3.1+debian-3.2) unstable; urgency=medium
+
+  * debian/patches:
+- Add upstream patch to fix FTBFS with GCC 6 due to narrowing conversions.
+  (Closes: #811766)
+  * debian/rules:
+- Add mandatory build-{arch,indep} targets.
+
+ -- James Cowgill   Fri, 16 Mar 2018 17:26:15 +
+
 scim-unikey (0.3.1+debian-3.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru scim-unikey-0.3.1+debian/debian/patches/gcc6.patch 
scim-unikey-0.3.1+debian/debian/patches/gcc6.patch
--- scim-unikey-0.3.1+debian/debian/patches/gcc6.patch  1970-01-01 
01:00:00.0 +0100
+++ scim-unikey-0.3.1+debian/debian/patches/gcc6.patch  2018-03-16 
17:02:48.0 +
@@ -0,0 +1,269 @@
+Description: Fix FTBFS with GCC 6 caused by narrowing conversions
+Author: marguerite 
+Origin: upstream, 
https://github.com/scim-im/scim-unikey/commit/dcc2ef6057a72d5babc49c51c1a5f998c9a31131
+Bug-Debian: https://bugs.debian.org/811766
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+--- a/ukengine/data.cpp
 b/ukengine/data.cpp
+@@ -96,145 +96,145 @@ See TCVN3 & VPS below for examples
+ unsigned char SingleByteTables[][TOTAL_VNCHARS] = 
+ 
+ // TCVN3
+-{{'A','a','¸','¸','µ','µ','¶','¶','·','·','¹','¹',  // 0: a
+-  '¢','©','Ê','Ê','Ç','Ç','È','È','É','É','Ë','Ë',// 1: a^
+-  '¡','¨','¾','¾','»','»','¼','¼','½','½','Æ','Æ',// 2: a(
+-  'B','b','C','c','D','d',
+-  '§','®',
+-  'E','e','Ð','Ð','Ì','Ì','Î','Î','Ï','Ï','Ñ','Ñ',// 3: e
+-  '£','ª','Õ','Õ','Ò','Ò','Ó','Ó','Ô','Ô','Ö','Ö',  // 4: e^
+-  'F','f','G','g','H','h',
+-  'I','i','Ý','Ý','×','×','Ø','Ø','Ü','Ü','Þ','Þ',// 5: i
+-  'J','j','K','k','L','l','M','m','N','n',
+-  'O','o','ã','ã','ß','ß','á','á','â','â','ä','ä',// 6: o
+-  '¤','«','è','è','å','å','æ','æ','ç','ç','é','é',// 7: o^
+-  '¥','¬','í','í','ê','ê','ë','ë','ì','ì','î','î',// 8: o+
+-  'P','p','Q','q','R','r','S','s','T','t',
+-  'U','u','ó','ó','ï','ï','ñ','ñ','ò','ò','ô','ô',// 9: u
+-  '¦','­','ø','ø','õ','õ','ö','ö','÷','÷','ù','ù',//10: u+ 
+-  'V','v','W','w','X','x',
+-  'Y','y','ý','ý','ú','ú','û','û','ü','ü','þ','þ',//11: y
+-  'Z','z',
++{{static_cast('A'),static_cast('a'),static_cast('¸'),static_cast('¸'),static_cast('µ'),static_cast('µ'),static_cast('¶'),static_cast('¶'),static_cast('·'),static_cast('·'),static_cast('¹'),static_cast('¹'), 
 // 0: a
++  static_cast('¢'),static_cast('©'),static_cast('Ê'),static_cast('Ê'),static_cast('Ç'),static_cast('Ç'),static_cast('È'),static_cast('È'),static_cast('É'),static_cast('É'),static_cast('Ë'),static_cast('Ë'), 
   // 1: a^
++  static_cast('¡'),static_cast('¨'),static_cast('¾'),static_cast('¾'),static_cast('»'),static_cast('»'),static_cast('¼'),static_cast('¼'),static_cast('½'),static_cast('½'),static_cast('Æ'),static_cast('Æ'), 
   // 2: a(
++  static_cast('B'),static_cast('b'),static_cast('C'),static_cast('c'),static_cast('D'),static_cast('d'),
++  static_cast('§'),static_cast('®'),
++  static_cast('E'),static_cast('e'),static_cast('Ð'),static_cast('Ð'),static_cast('Ì'),static_cast('Ì'),static_cast('Î'),static_cast('Î'),static_cast('Ï'),static_cast('Ï'),static_cast('Ñ'),static_cast('Ñ'), 
   // 3: e
++  static_cast('£'),static_cast('ª'),static_cast('Õ'),static_cast('Õ'),static_cast('Ò'),static_cast('Ò'),static_cast('Ó'),static_cast('Ó'),static_cast('Ô'),static_cast('Ô'),static_cast('Ö'),static_cast('Ö'), 
 // 4: e^
++  static_cast('F'),static_cast('f'),static_cast('G'),static_cast('g'),static_cast('H'),static_cast('h'),
++  static_cast('I'),static_cast('i'),static_cast('Ý'),static_cast('Ý'),static_cast('×'),static_cast('×'),static_cast('Ø'),static_cast('Ø'),static_cast('Ü'),static_cast('Ü'),static_cast('Þ'),static_cast('Þ'), 
   // 5: i
++  

Processed: Re: Bug#890905: jabref: does not launch

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 jabref: fails to build and start with openjdk-9
Bug #890905 [jabref] jabref: fails to start with openjdk-9-jre
Changed Bug title to 'jabref: fails to build and start with openjdk-9' from 
'jabref: fails to start with openjdk-9-jre'.
> severity -1 serious
Bug #890905 [jabref] jabref: fails to build and start with openjdk-9
Severity set to 'serious' from 'important'
> tag -1 + patch
Bug #890905 [jabref] jabref: fails to build and start with openjdk-9
Added tag(s) patch.

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

Bug#797639: marked as done (scim-unikey: Not loading on AMD64)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 17:25:39 +
with message-id 
and subject line Re: scim-unikey: Not loading on AMD64
has caused the Debian Bug report #797639,
regarding scim-unikey: Not loading on AMD64
to be marked as done.

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

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


-- 
797639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scim-unikey
Version: 0.3.1+debian-3.1
Severity: important

Dear Maintainer,

The scim-unikey package installs its libraries in
scim-unikey: /usr/lib/scim-1.0/1.4.0/Helper/unikey-helper.so
scim-unikey: /usr/lib/scim-1.0/1.4.0/IMEngine/unikey.so

On my AMD64 system, when scim searches for engines, it does not found scim-
unikey.
As a consequence, unikey is not usable.

I noticed that other engine methods install their libraries in
/usr/lib/x86_64-linux-gnu/scim-1.0/1.4.0/IMEngine/ and
/usr/lib/x86_64-linux-gnu/scim-1.0/1.4.0/Helper/

For example, see scim-skk, scim-thai.

As a workaround, creating symbolic links solves the issue.

Regards



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

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

Versions of packages scim-unikey depends on:
ii  libc6 2.19-19
ii  libgcc1   1:5.1.1-14
ii  libglib2.0-0  2.44.1-1.1
ii  libgtk-3-03.16.6-1
ii  libscim8c2a   1.4.15-3
ii  libstdc++65.1.1-14
ii  scim  1.4.15-3

scim-unikey recommends no packages.

scim-unikey suggests no packages.
--- End Message ---
--- Begin Message ---
Hi,

On Tue, 01 Sep 2015 09:02:00 +0200 Viet Hang Nguyen
 wrote:
> Package: scim-unikey
> Version: 0.3.1+debian-3.1
> Severity: important
> 
> Dear Maintainer,
> 
> The scim-unikey package installs its libraries in
> scim-unikey: /usr/lib/scim-1.0/1.4.0/Helper/unikey-helper.so
> scim-unikey: /usr/lib/scim-1.0/1.4.0/IMEngine/unikey.so
> 
> On my AMD64 system, when scim searches for engines, it does not found scim-
> unikey.
> As a consequence, unikey is not usable.
> 
> I noticed that other engine methods install their libraries in
> /usr/lib/x86_64-linux-gnu/scim-1.0/1.4.0/IMEngine/ and
> /usr/lib/x86_64-linux-gnu/scim-1.0/1.4.0/Helper/
> 
> For example, see scim-skk, scim-thai.
> 
> As a workaround, creating symbolic links solves the issue.

This should have been fixed since scim-unikey was binNMUed after the GCC
5 transition. 0.3.1+debian-3.1+b1 has files installed in the correct
locations.

James



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

Processed: affects 892956

[Debian Bug Tracking System]

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

> affects 892956 src:fwupd
Bug #892956 [meson] meson creates bogus pkgconfig files
Added indication that 892956 affects src:fwupd
> thanks
Stopping processing here.

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

Bug#893122: cronometer FTBFS with openjdk-9

[Adrian Bunk]

Source: cronometer
Version: 0.9.9+dfsg-1
Severity: serious
Tags: buster sid

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

...
compile:
[javac] /build/1st/cronometer-0.9.9+dfsg/build.xml:26: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Compiling 174 source files to /build/1st/cronometer-0.9.9+dfsg/bin
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] /build/1st/cronometer-0.9.9+dfsg/src/ca/spaz/util/XMLNode.java:157: 
error: unmappable character (0x93) for encoding US-ASCII
[javac]  else if (c == '?') sb.append("");
[javac] ^
[javac] /build/1st/cronometer-0.9.9+dfsg/src/ca/spaz/util/XMLNode.java:158: 
error: unmappable character (0x94) for encoding US-ASCII
[javac]  else if (c == '?') sb.append("");
[javac] ^
[javac] /build/1st/cronometer-0.9.9+dfsg/src/ca/spaz/util/XMLNode.java:159: 
error: unmappable character (0x91) for encoding US-ASCII
[javac]  else if (c == '?') sb.append("'");
[javac] ^
[javac] /build/1st/cronometer-0.9.9+dfsg/src/ca/spaz/util/XMLNode.java:160: 
error: unmappable character (0x92) for encoding US-ASCII
[javac]  else if (c == '?') sb.append("'"); 
[javac] ^
[javac] 4 errors
[javac] 3 warnings

BUILD FAILED
/build/1st/cronometer-0.9.9+dfsg/build.xml:26: Compile failed; see the compiler 
error output for details.

Total time: 34 seconds
dh_auto_build: ant -Duser.name debian returned exit code 1
make[1]: *** [debian/rules:16: override_dh_auto_build] Error 2

Bug#893085: marked as done (apache-log4j2 FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 16:34:31 +
with message-id 
and subject line Bug#893085: fixed in apache-log4j2 2.10.0-1
has caused the Debian Bug report #893085,
regarding apache-log4j2 FTBFS with openjdk-9
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.)


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

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

...
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (default-cli) on 
project log4j-core: MavenReportException: Error while generating Javadoc: 
[ERROR] Exit code: 1 - 
/build/1st/apache-log4j2-2.8.2/log4j-core/src/main/java/org/apache/logging/log4j/core/config/plugins/convert/TypeConverters.java:35:
 error: package javax.xml.bind is not visible
[ERROR] import javax.xml.bind.DatatypeConverter;
[ERROR] ^
[ERROR]   (package javax.xml.bind is declared in module java.xml.bind, which is 
not in the module graph)
[ERROR] 
/build/1st/apache-log4j2-2.8.2/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/mom/kafka/KafkaProducerFactory.java:22:
 error: package org.apache.kafka.clients.producer does not exist
[ERROR] import org.apache.kafka.clients.producer.Producer;
[ERROR] ^
[ERROR] 
/build/1st/apache-log4j2-2.8.2/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/mom/kafka/KafkaProducerFactory.java:37:
 error: cannot find symbol
[ERROR] Producer newKafkaProducer(Properties config);
[ERROR] ^
[ERROR]   symbol:   class Producer
[ERROR]   location: interface KafkaProducerFactory
[ERROR] 
/build/1st/apache-log4j2-2.8.2/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/mom/kafka/KafkaManager.java:27:
 error: package org.apache.kafka.clients.producer does not exist
[ERROR] import org.apache.kafka.clients.producer.Callback;
[ERROR] ^
[ERROR] 
/build/1st/apache-log4j2-2.8.2/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/mom/kafka/KafkaManager.java:28:
 error: package org.apache.kafka.clients.producer does not exist
[ERROR] import org.apache.kafka.clients.producer.Producer;
[ERROR] ^
[ERROR] 
/build/1st/apache-log4j2-2.8.2/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/mom/kafka/KafkaManager.java:29:
 error: package org.apache.kafka.clients.producer does not exist
[ERROR] import org.apache.kafka.clients.producer.ProducerRecord;
[ERROR] ^
[ERROR] 
/build/1st/apache-log4j2-2.8.2/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/mom/kafka/KafkaManager.java:30:
 error: package org.apache.kafka.clients.producer does not exist
[ERROR] import org.apache.kafka.clients.producer.RecordMetadata;
[ERROR] ^
[ERROR] 
/build/1st/apache-log4j2-2.8.2/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/mom/kafka/KafkaManager.java:46:
 error: cannot find symbol
[ERROR] private Producer producer;
[ERROR] ^
[ERROR]   symbol:   class Producer
[ERROR]   location: class KafkaManager
[ERROR] 
/build/1st/apache-log4j2-2.8.2/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/mom/kafka/DefaultKafkaProducerFactory.java:22:
 error: package org.apache.kafka.clients.producer does not exist
[ERROR] import org.apache.kafka.clients.producer.KafkaProducer;
[ERROR] ^
[ERROR] 
/build/1st/apache-log4j2-2.8.2/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/mom/kafka/DefaultKafkaProducerFactory.java:23:
 error: package org.apache.kafka.clients.producer does not exist
[ERROR] import org.apache.kafka.clients.producer.Producer;
[ERROR] ^
[ERROR] 
/build/1st/apache-log4j2-2.8.2/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/mom/kafka/DefaultKafkaProducerFactory.java:39:
 error: cannot find symbol
[ERROR] public Producer newKafkaProducer(final Properties 
config) {
[ERROR]^
[ERROR]   symbol:   class Producer
[ERROR]   location: class DefaultKafkaProducerFactory
[ERROR] 
[ERROR] Command line was: /usr/lib/jvm/java-9-openjdk-amd64/bin/javadoc 
@options @packages
[ERROR] 
[ERROR] Refer to the generated Javadoc files in 

Bug#893120: debian-edu-install: uninstallable on ahrd disk thrice the size mentioned in manual

[Holger Levsen]

control: severity -1 important
thanks

On Fri, Mar 16, 2018 at 05:19:01PM +0100, Dominik George wrote:
> Severity: grave
> Justification: renders package unusable

but not for everyone, so its just "important". we have had several many
successful installation reports since last year.

> I spent two days trying to install Debian Edu (combined server) in a
> virtual machine. I started with 100 GiB hard disk, then tried 150 GiB,
> and finally 220 GiB. The LTSP chroot installation always fails with no
> space left in /opt/var/cache/apt.

strange. as a workaround you could install a plain main-server and then
turn that into an LTSP server after installation.


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Processed: Re: Bug#893120: debian-edu-install: uninstallable on ahrd disk thrice the size mentioned in manual

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #893120 [src:debian-edu-install] debian-edu-install: uninstallable on ahrd 
disk thrice the size mentioned in manual
Severity set to 'important' from 'grave'

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

Bug#893120: debian-edu-install: uninstallable on ahrd disk thrice the size mentioned in manual

[Dominik George]

Source: debian-edu-install
Version: 1.916
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I spent two days trying to install Debian Edu (combined server) in a
virtual machine. I started with 100 GiB hard disk, then tried 150 GiB,
and finally 220 GiB. The LTSP chroot installation always fails with no
space left in /opt/var/cache/apt.

Installing Debain Edu is not possible.

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlqr7nQxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pb2bxAAvIZSU7BE0+ucGg5SEzrzvk0GHzuv
OfhwhpxuggDzKgTf2vq5fsEXm9DafxyIXhq9ZfYgbGCRqXlWbO3hjlmneZx1OCzt
ow3kpLZJy5LwerRYe2lYlJY8O8ZYnKPUMuWxblpVCU9tQUXw/+edtmu+KGRNcEmX
L8u5/y1LNp5846Xb9wSKgJP93DaYInUndv9+i9EOGps+uoZlO67yyDgYJUJmmkJf
0q9zoU7KBOO2fJv8i1rcbxmgNaT9gcqZLtlLXPvFUm526ipZHT1nktteHJQEtwqf
KNhGA2tsNwxJrWJgnJG/Vtppwj9wgbdJ9q9cPxVqS9sLVi3hoUPeDRA6kBVmkebB
nbxDLI8tl5DtdR6FLQKOT8nfich9V5XDmW4379jCL+g7P+ixigBiWLouwMwnBCr/
EpBK8Qwv0KCnRhs9geC9i5HBpU4oKB4nJr5L24jEy9kbwaduN1w3mpRQZ81WtsCC
MdYEmJl0VhW4UH5MYjxrkPZ1lI5b9f4pSFI5wmA1FGSC12+swTWFWKY3ivVhObDE
exQfsdRUhuLj4NpPVvE3rIqxLOCAi75X5R9/cdJ5uMxyG0kzUwzi87dv9VIBy+FT
0SpH1QYhSz/ORRA4FjlDBn726Bwk6OpudECPn1JMBoziZ6k/ASwSfSG74q8MPDRI
70iu0yXdiLct/3M=
=HyOM
-END PGP SIGNATURE-

Bug#893119: tktreectl: FTBFS - ./configure not found

[James Cowgill]

Source: tktreectrl
Version: 2.2.8-2
Severity: serious
Tags: sid buster

Hi,

tktreectl FTBFS everywhere with:
>  debian/rules build-arch
> dh_testdir
> cp -f /usr/share/misc/config.sub config.sub
> cp -f /usr/share/misc/config.guess config.guess
> ./configure --build aarch64-linux-gnu \
> --prefix=/usr \
> --mandir=\${prefix}/share/man \
> --infodir=\${prefix}/share/info \
> --with-tcl=/usr/lib \
> --with-tk=/usr/lib \
> --with-tclinclude=/usr/include/tcl \
> --with-tkinclude=/usr/include/tcl \
> CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security" \
> LDFLAGS="-lm -Wl,-z,defs -Wl,--no-undefined -Wl,--as-needed"
> /bin/sh: 1: ./configure: not found
> debian/rules:20: recipe for target 'config-stamp' failed
> make: *** [config-stamp] Error 127
> dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
> status 2

This was caused by this change:
> @@ -16,8 +18,6 @@
>  config: config-stamp
>  config-stamp: 
> dh_testdir
> -   $(MAKE) -f /usr/share/quilt/quilt.make patch
> -   autoreconf --force
>  ifneq "$(wildcard /usr/share/misc/config.sub)" ""
> cp -f /usr/share/misc/config.sub config.sub
>  endif

You need to keep the call to autoreconf.

Please consider converting the package to use dh or at least use
dh_autoreconf instead.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed: Pending fixes for bugs in the apache-log4j2 package

[Debian Bug Tracking System]

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

> tag 893085 + pending
Bug #893085 [src:apache-log4j2] apache-log4j2 FTBFS with openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#893085: Pending fixes for bugs in the apache-log4j2 package

[pkg-java-maintainers]

tag 893085 + pending
thanks

Some bugs in the apache-log4j2 package are closed in revision
4d2db9d21005ae6334ed9685065be30c008d6c8d in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/apache-log4j2.git/commit/?id=4d2db9d

Commit message:

Fixed the build failure with Java 9 (Closes: #893085)

Bug#893118: codenarc FTBFS with openjdk-9

[Adrian Bunk]

Source: codenarc
Version: 0.23-4
Severity: serious

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

...
compile:
  [groovyc] Compiling 452 source files to 
/build/1st/codenarc-0.23/target/classes
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
org.codehaus.groovy.reflection.CachedClass 
(file:/usr/share/java/groovy-all.jar) to method java.lang.Object.finalize()
WARNING: Please consider reporting this to the maintainers of 
org.codehaus.groovy.reflection.CachedClass
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
  [groovyc] org.codehaus.groovy.control.MultipleCompilationErrorsException: 
startup failed:
  [groovyc] Invalid commandline usage for javac.
  [groovyc] warning: [options] bootstrap class path not set in conjunction with 
-source 1.5
  [groovyc] error: Source option 1.5 is no longer supported. Use 1.6 or later.
  [groovyc] error: Target option 1.5 is no longer supported. Use 1.6 or later.
  [groovyc] 
  [groovyc] 
  [groovyc] 1 error

BUILD FAILED
/build/1st/codenarc-0.23/debian/build.xml:28: Compilation Failed

Total time: 1 minute 7 seconds
make[1]: *** [debian/rules:7: override_jh_build] Error 1

Bug#893117: node-readable-stream: FTBFS and Debci failure with node-process-nextick-args 2.0.0-1

[Adrian Bunk]

Source: node-readable-stream
Version: 2.3.3-1
Severity: serious

https://ci.debian.net/packages/n/node-readable-stream/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-readable-stream.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-readable-stream-2.3.3'
tape test/parallel/*.js test/ours/*.js
/build/1st/node-readable-stream-2.3.3/lib/_stream_readable.js:776
processNextTick(resume_, stream, state);
^

TypeError: processNextTick is not a function
at resume 
(/build/1st/node-readable-stream-2.3.3/lib/_stream_readable.js:776:5)
at PassThrough.Readable.resume 
(/build/1st/node-readable-stream-2.3.3/lib/_stream_readable.js:768:5)
at PassThrough.Readable.on 
(/build/1st/node-readable-stream-2.3.3/lib/_stream_readable.js:738:53)
at PassThrough.Readable.pipe 
(/build/1st/node-readable-stream-2.3.3/lib/_stream_readable.js:608:7)
at Object. 
(/build/1st/node-readable-stream-2.3.3/test/parallel/test-stream-big-packet.js:56:4)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1

Bug#893114: dablin: FTBFS on armel, mips, mipsel, m68k, powerpc, powerpcspe, sh4 - undefined reference to `__atomic_load_8'

[James Cowgill]

Source: dablin
Version: 1.8.0-1
Severity: serious
Tags: sid buster

Hi

dablin FTBFS on the above architectures with these errors:
> [ 96%] Linking CXX executable dablin
> cd /<>/obj-mips-linux-gnu/src && /usr/bin/cmake -E 
> cmake_link_script CMakeFiles/dablin.dir/link.txt --verbose=1
> /usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wl,-z,relro -Wl,-z,now -rdynamic 
> CMakeFiles/dablin.dir/sdl_output.cpp.o 
> CMakeFiles/dablin.dir/dabplus_decoder.cpp.o 
> CMakeFiles/dablin.dir/eti_source.cpp.o CMakeFiles/dablin.dir/eti_player.cpp.o 
> CMakeFiles/dablin.dir/dab_decoder.cpp.o 
> CMakeFiles/dablin.dir/fic_decoder.cpp.o 
> CMakeFiles/dablin.dir/pcm_output.cpp.o CMakeFiles/dablin.dir/tools.cpp.o 
> CMakeFiles/dablin.dir/version.cpp.o CMakeFiles/dablin.dir/dablin.cpp.o  -o 
> dablin ../fec/libfec.a -lpthread -lmpg123 -lSDL2 -lfaad -lc -lm 
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:239: 
> undefined reference to `__atomic_store_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:239: 
> undefined reference to `__atomic_store_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o: In function 
> `SDLOutput::GetAudio(unsigned char*, unsigned int)':
> ./obj-mips-linux-gnu/src/./src/sdl_output.cpp:167: undefined reference to 
> `__atomic_load_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:250: 
> undefined reference to `__atomic_load_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:250: 
> undefined reference to `__atomic_load_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:250: 
> undefined reference to `__atomic_load_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:250: 
> undefined reference to `__atomic_load_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:250: more 
> undefined references to `__atomic_load_8' follow
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:239: 
> undefined reference to `__atomic_store_8'
> CMakeFiles/dablin.dir/sdl_output.cpp.o:/usr/include/c++/7/atomic:239: 
> undefined reference to `__atomic_store_8'
> collect2: error: ld returned 1 exit status
> make[3]: *** [src/CMakeFiles/dablin.dir/build.make:336: src/dablin] Error 1
> make[3]: Leaving directory '/<>/obj-mips-linux-gnu'
> make[2]: *** [CMakeFiles/Makefile2:311: src/CMakeFiles/dablin.dir/all] Error 2
> make[2]: *** Waiting for unfinished jobs
> make[3]: Entering directory '/<>/obj-mips-linux-gnu'
> [ 71%] Building CXX object src/CMakeFiles/dablin_gtk.dir/dablin_gtk.cpp.o
> cd /<>/obj-mips-linux-gnu/src && /usr/bin/c++  
> -DDABLIN_AAC_FAAD2 -I/usr/include/SDL2 -I/usr/include/gtkmm-3.0 
> -I/usr/lib/mips-linux-gnu/gtkmm-3.0/include -I/usr/include/atkmm-1.6 
> -I/usr/include/gtk-3.0/unix-print -I/usr/include/gdkmm-3.0 
> -I/usr/lib/mips-linux-gnu/gdkmm-3.0/include -I/usr/include/giomm-2.4 
> -I/usr/lib/mips-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 
> -I/usr/lib/mips-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 
> -I/usr/lib/mips-linux-gnu/glibmm-2.4/include -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/mips-linux-gnu/dbus-1.0/include 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairomm-1.0 
> -I/usr/lib/mips-linux-gnu/cairomm-1.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/sigc++-2.0 
> -I/usr/lib/mips-linux-gnu/sigc++-2.0/include -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/glib-2.0 -I/usr/lib/mips-linux-gnu/glib-2.0/include 
> -I/<>/src/../fec  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -std=c++0x -Wall -Wextra -o 
> CMakeFiles/dablin_gtk.dir/dablin_gtk.cpp.o -c 
> /<>/src/dablin_gtk.cpp
> make[3]: Leaving directory '/<>/obj-mips-linux-gnu'
> make[3]: Entering directory '/<>/obj-mips-linux-gnu'
> [100%] Linking CXX executable dablin_gtk
> cd /<>/obj-mips-linux-gnu/src && /usr/bin/cmake -E 
> cmake_link_script CMakeFiles/dablin_gtk.dir/link.txt --verbose=1
> /usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wl,-z,relro -Wl,-z,now -rdynamic 
> CMakeFiles/dablin_gtk.dir/sdl_output.cpp.o 
> CMakeFiles/dablin_gtk.dir/dabplus_decoder.cpp.o 
> CMakeFiles/dablin_gtk.dir/eti_source.cpp.o 
> CMakeFiles/dablin_gtk.dir/eti_player.cpp.o 
> CMakeFiles/dablin_gtk.dir/dab_decoder.cpp.o 
> CMakeFiles/dablin_gtk.dir/fic_decoder.cpp.o 
> CMakeFiles/dablin_gtk.dir/pcm_output.cpp.o 
> CMakeFiles/dablin_gtk.dir/tools.cpp.o CMakeFiles/dablin_gtk.dir/version.cpp.o 
> CMakeFiles/dablin_gtk.dir/mot_manager.cpp.o 
> CMakeFiles/dablin_gtk.dir/pad_decoder.cpp.o 
> 

Bug#893112: eclipse-titan depends on gcc < 7.2.0, but unstable has gcc-7.3.0

[Harald Welte]

Package: eclipse-titan
Severity: grave

This is history repeating itself, see debian bug 879816

I would hope this can be solved in a generic way, without breaking the 
eclipse-titan
package every few months when debian updates the gcc version.

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

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

Versions of packages eclipse-titan depends on:
ii  default-jdk   2:1.9-61
ii  expect5.45.4-1
ii  gcc   4:7.3.0-1
ii  libc6 2.27-2
ii  libgcc1   1:8-20180312-2
ii  libncurses5   6.1-1
ii  libpcap-dev   1.8.1-6
ii  libpcre3-dev  2:8.39-9
ii  libsctp-dev   1.0.17+dfsg-2
ii  libssl-dev1.1.0g-2
ii  libssl1.1 1.1.0g-2
ii  libstdc++68-20180312-2
ii  libtinfo5 6.1-1
ii  libxml2   2.9.4+dfsg1-6.1
ii  libxml2-dev   2.9.4+dfsg1-6.1
ii  make  4.2.1-1
ii  perl  5.26.1-5
ii  python2.7.14-4

eclipse-titan recommends no packages.

eclipse-titan suggests no packages.

Bug#892045: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: usbguard-applet-qt: upgrading libqt5 to experimental's 5.10 breaks the applet)

[Lisandro Damián Nicanor Pérez Meyer]

El 16 mar. 2018 11:55 a.m., "Adrian Bunk"

> sorry but we can't enforce such dependencies, specially with experimental
versions of qt.

We can, and we should.


And we do, +/- bugs.


> The stack needs to be still fully bootstrapped and built, this is why it
is in experimental.

And then the stack goes piece by piece slowly into testing,
breaking everything there (and in Debian derivatives using testing).


Adrian: no, and the sole fact that you are stating this means to have no
idea of how we handle packages.


> Stuff will and should self heal in a matter of days, if not, when the qt
will go in unstable, if a rebuild
> will be necessary, please open a bug against qtbase, for not providing a
stable ABI, and then affect this package.


Non stable API is provided in -private packages, tracked and rebuilt with
every transition. Each and every transition is managed to get a coordinated
entry to testing, and when bugs showed up we went ahead to solve them. You
are free to ask the release team about that.

I'll kindly ask you two to not close or reopen our team's bugs. If you
consider it's needed do mail the bug in question.

Bug#893110: gupnp-igd: FTBFS (randomly?) testsuite failures - gupnp-simple-igd SIGTRAP

[James Cowgill]

Source: gupnp-igd
Version: 0.2.5-1
Severity: serious
Tags: sid buster

Hi,

gupnp-igd FTBFS on some of the buildds with this error:
> make[6]: Entering directory '/<>/tests/gtest'
> ../../test-driver: line 107: 11204 Trace/breakpoint trap   "$@" > $log_file 
> 2>&1
> FAIL: gupnp-simple-igd
> make[6]: Leaving directory '/<>/tests/gtest'
> make[6]: Entering directory '/<>/tests/gtest'
> =
>gupnp-igd 0.2.5: tests/gtest/test-suite.log
> =
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: gupnp-simple-igd
> ==
> 
> /simpleigd/new: 
> (/<>/tests/gtest/.libs/gupnp-simple-igd:11204): 
> GUPnP-ContextManager-Linux-WARNING **: Got new address for device 1 but 
> device is not active
> FAIL gupnp-simple-igd (exit status: 133)
> 
> 
> Testsuite summary for gupnp-igd 0.2.5
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See tests/gtest/test-suite.log
> Please report to http://www.gupnp.org/
> 

While it built on amd64 on the buildds, the package fails with the same
error when I locally rebuild it. I notice it build fine on all the
Ubuntu builders. I'm afraid I have no idea what is going on here.

James



signature.asc
Description: OpenPGP digital signature

Bug#892091: marked as done (ayatana-indicator-power: FTBFS randomly - gschemas.compiled generated twice)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 15:34:32 +
with message-id 
and subject line Bug#892091: fixed in ayatana-indicator-power 2.0.93-1
has caused the Debian Bug report #892091,
regarding ayatana-indicator-power: FTBFS randomly - gschemas.compiled generated 
twice
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.)


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

Hi,

On the buildds, ayatana-indicator-power FTBFS on armhf, mips, ia64, m68k
and sh4 with an error similar to this:
> [ 84%] Generating gschemas.compiled
> cd /<>/obj-mips-linux-gnu/tests && cp -f 
> /<>/obj-mips-linux-gnu/data/*gschema.xml 
> /<>/obj-mips-linux-gnu/tests
> cp: cannot create regular file 
> '/<>/obj-mips-linux-gnu/tests/org.ayatana.indicator.power.gschema.xml':
>  File exists
> make[3]: *** [tests/CMakeFiles/test-device.dir/build.make:65: 
> tests/gschemas.compiled] Error 1
> make[3]: Leaving directory '/<>/obj-mips-linux-gnu'
> make[2]: *** [CMakeFiles/Makefile2:464: tests/CMakeFiles/test-device.dir/all] 
> Error 2
> make[2]: *** Waiting for unfinished jobs
> make[3]: Entering directory '/<>/obj-mips-linux-gnu'
> [ 84%] Generating gschemas.compiled
> cd /<>/obj-mips-linux-gnu/tests && cp -f 
> /<>/obj-mips-linux-gnu/data/*gschema.xml 
> /<>/obj-mips-linux-gnu/tests
> cd /<>/obj-mips-linux-gnu/tests && 
> /usr/lib/mips-linux-gnu/glib-2.0/glib-compile-schemas 
> /<>/obj-mips-linux-gnu/tests
> make[3]: Leaving directory '/<>/obj-mips-linux-gnu'

This looks like a random error induced by parallel builds. Here you can
see that CMake is attempting to generate "gschemas.compiled" twice when
it should only generate it once.

tests/CMakeLists.txt contains:
> set (SCHEMA_DIR ${CMAKE_CURRENT_BINARY_DIR})
> add_definitions(-DSCHEMA_DIR="${SCHEMA_DIR}")
> execute_process (COMMAND ${PKG_CONFIG_EXECUTABLE} gio-2.0 --variable 
> glib_compile_schemas
>  OUTPUT_VARIABLE COMPILE_SCHEMA_EXECUTABLE
>  OUTPUT_STRIP_TRAILING_WHITESPACE)
> add_custom_command (OUTPUT gschemas.compiled
> DEPENDS 
> ${CMAKE_BINARY_DIR}/data/org.ayatana.indicator.power.gschema.xml
> COMMAND cp -f ${CMAKE_BINARY_DIR}/data/*gschema.xml 
> ${SCHEMA_DIR}
> COMMAND ${COMPILE_SCHEMA_EXECUTABLE} ${SCHEMA_DIR})
[...]
> function(add_test_by_name name)
>   set (TEST_NAME ${name})
>   add_executable (${TEST_NAME} ${TEST_NAME}.cc gschemas.compiled)
>   add_test (${TEST_NAME} ${TEST_NAME})
>   add_dependencies (${TEST_NAME} ayatanaindicatorpowerservice)
>   target_link_libraries (${TEST_NAME} ayatanaindicatorpowerservice gtest 
> ${DBUSTEST_LIBRARIES} ${SERVICE_DEPS_LIBRARIES} ${GTEST_LIBS})
> endfunction()
> add_test_by_name(test-notify)
> add_test(NAME dear-reader-the-next-test-takes-80-seconds COMMAND true)
> add_test_by_name(test-device)

From cmake-commands(7) - add_custom_command:
"Do not list the output in more than one independent target that may
build in parallel or the two instances of the rule may conflict (instead
use the add_custom_target() command to drive the command and make the
other targets depend on that one)."

There are three independent targets here which use gschemas.compiled
(the three tests).

I found this blog which tries to explain it (number 4):
https://samthursfield.wordpress.com/2015/11/21/cmake-dependencies-between-targets-and-files-and-custom-commands/

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ayatana-indicator-power
Source-Version: 2.0.93-1

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated 
ayatana-indicator-power 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, 16 Mar 2018 

Bug#893049: libfiu FTBFS: recipe for target 'run-test-basic_ctrl.py' failed

[Chris Lamb]

Hi Alberto and Adrian

> https://github.com/lamby/pkg-libfiu/commit/9bf63e144117fbd382f4053a4338041b975b8c67
[…]
> Thanks for coming up with a patch for this!

Actually the patch doesn't work. Or, rather, it's stranger than that. If
I build the package using fairly vanilla scripts (or on the official buildds
as Adrian as pointed out and reopened to match) the package fails to build,
even with this patch.

However, if I then go into the failed build directory and run `make test`
the test passes (same chroot/container!). Does that help diagnose it at
all? :)


Regards,

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

Bug#892045: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: usbguard-applet-qt: upgrading libqt5 to experimental's 5.10 breaks the applet)

[Lisandro Damián Nicanor Pérez Meyer]

This bug does not exists until I get a proper log. To the best of or
knowledge the necessary dependencies are there, I don't see a way for this
to happen without the user forcing stuff.

I'll close this bug in a week if no further information is provided.

El 16 mar. 2018 11:57 a.m., "Adrian Bunk"  escribió:

Control: reopen -1
Control: reassign -1 libqt5widgets5 5.10.1+dfsg-2
Control: affects -1 usbguard-applet-qt

On Fri, Mar 16, 2018 at 12:03:03PM +, Debian Bug Tracking System wrote:
>...
> Date: Fri, 16 Mar 2018 12:59:37 +0100
> From: Gianfranco Costamagna 
> To: 892045-d...@bugs.debian.org
> Subject: Re: usbguard-applet-qt: upgrading libqt5 to experimental's 5.10
>  breaks the applet
>
> Hello,
>
> On Sun, 04 Mar 2018 17:07:11 +0200 Mykola Nikishov  wrote:
> > Package: usbguard-applet-qt
> > Version: 0.7.0+ds1-2+b1
> > Severity: grave
> > Justification: renders package unusable
> >
> > Nothing prevents the user from installing an incompatible Qt 5.10
> > libraries:
> >
> > --8<---cut here---start->8---
> > $ usbguard-applet-qt
> > Cannot mix incompatible Qt library (version 0x50a00) with this library
(version 0x50a01)
> > Aborted
> > --8<---cut here---end--->8---
> >
>
> sorry but we can't enforce such dependencies, specially with experimental
versions of qt.

We can, and we should.

> The stack needs to be still fully bootstrapped and built, this is why it
is in experimental.

And then the stack goes piece by piece slowly into testing,
breaking everything there (and in Debian derivatives using testing).

> Stuff will and should self heal in a matter of days, if not, when the qt
will go in unstable, if a rebuild
> will be necessary, please open a bug against qtbase, for not providing a
stable ABI, and then affect this package.

Doing this now.

> G.
>...

cu
Adrian

--

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

--
To unsubscribe, send mail to 892045-unsubscr...@bugs.debian.org.

Bug#893102: marked as done (brltty FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 15:04:47 +
with message-id 
and subject line Bug#893102: fixed in brltty 5.6-3
has caused the Debian Bug report #893102,
regarding brltty FTBFS with openjdk-9
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.)


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

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

...
'/usr/lib/jvm/java-9-openjdk-amd64/bin/javac' -encoding UTF-8 -source 1.5 
-target 1.5 -d classes -classpath . ../../../Bindings/Java/Brlapi.java 
../../../Bindings/Java/ConnectionSettings.java 
../../../Bindings/Java/DisplaySize.java ../../../Bindings/Java/Error.java 
../../../Bindings/Java/Exception.java ../../../Bindings/Java/Key.java 
../../../Bindings/Java/Native.java ../../../Bindings/Java/Test.java 
../../../Bindings/Java/WriteArguments.java Constants.java
warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make[3]: *** [Makefile:96: classes.made] Error 2
--- End Message ---
--- Begin Message ---
Source: brltty
Source-Version: 5.6-3

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated brltty package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 16 Mar 2018 15:20:39 +0100
Source: brltty
Binary: brltty libbrlapi0.6 libbrlapi-dev libbrlapi-jni libbrlapi-java 
brltty-flite brltty-speechd brltty-espeak brltty-udeb brltty-x11 xbrlapi 
cl-brlapi python-brlapi python3-brlapi
Architecture: source
Version: 5.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Description:
 brltty - Access software for a blind person using a braille display
 brltty-espeak - Access software for a blind person - espeak driver
 brltty-flite - Access software for a blind person - Flite speech driver
 brltty-speechd - Access software for a blind person - Speech Dispatcher driver
 brltty-udeb - Access software for a blind person using a braille display (udeb)
 brltty-x11 - Access software for a blind person using a braille display - X11
 cl-brlapi  - Common Lisp bindings for BrlAPI
 libbrlapi-dev - Library for communication with BRLTTY - static libs and headers
 libbrlapi-java - Java bindings for BrlAPI
 libbrlapi-jni - Java bindings for BrlAPI (native library)
 libbrlapi0.6 - braille display access via BRLTTY - shared library
 python-brlapi - Braille display access via BRLTTY - Python bindings
 python3-brlapi - Braille display access via BRLTTY - Python3 bindings
 xbrlapi- Access software for a blind person using a braille display - xbrl
Closes: 893102
Changes:
 brltty (5.6-3) unstable; urgency=medium
 .
   * debian/patches/41-java-bytecode-compat.patch: Bump java compatability to
 1.6 and later (Closes: Bug#893102).
Checksums-Sha1:
 ea608dc4fe53e15e6ce7b7e6f651333083005834 3213 brltty_5.6-3.dsc
 c6bf782b145bfe8db6acd2de04e4c4fbc5928549 28920 brltty_5.6-3.debian.tar.xz
Checksums-Sha256:
 4c8cc3fb1fee1f428db295d790b2a02ecd665557a1397f70b8955ccceef87602 3213 
brltty_5.6-3.dsc
 4010946e83c79783c6daa213804f8a351ba53a43a33bcd71cac79831efa20790 28920 
brltty_5.6-3.debian.tar.xz
Files:
 5cfc86484a0bdf29008ff68bee9371e9 3213 admin optional brltty_5.6-3.dsc
 8facfabd53e20f15f2330f519ff0f1b4 28920 admin optional 
brltty_5.6-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmjc9NmSo3GLaCjT9nlEeAcc38HUFAlqr1GMACgkQnlEeAcc3
8HWsIhAAgVTCKeuUTEhKFJdAGoHbIN7NOU3+JLJoBKKvdoXO7OjJvU2rJKNw2sbK
miSpTHH7NXKeC+E2cAKb57Fqd0UQyzilmWrgVBKawVMgQDEO4UrgZ10A+YZz8bvv
YU7Sl5X1Fm2PcsFCBTFFx+m4ullJbrvhf5qd7NOe+S6Gn/+h9sufU58uw6Herz4c

Bug#892733: gettext: msgfmt doesn't work with Java 9 (fwd)

[Santiago Vila]

Dear Gettext maintainers:

I've received the following report from the Debian BTS.

This is now serious for us because it makes a lot of packages to fail
to build from source.

[ Question for Emmanuel: Whenever a new GCC breaks a lot of packages,
  individual packages are still allowed to build-depend: old-gcc
  as a last resort. Would this be a possibility here? ]

Thanks.

-- Forwarded message --
From: Emmanuel Bourg 
To: Debian Bug Tracking System 
Date: Mon, 12 Mar 2018 12:04:37 +0100
Subject: gettext: msgfmt doesn't work with Java 9

Package: gettext
Version: 0.19.8.1-4
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

Hi,

msgfmt doesn't work with Java 9, when invoked with the --java2 parameter
it fails to detect the JDK and returns this error message:

  msgfmt: Java compiler not found, try installing gcj or set $JAVAC
  msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC

This issue breaks the build of at least two packages (plm and salliere).

It's possible to reproduce this issue by installing default-jdk/0.59+exp2
from experimental.

Emmanuel Bourg

Bug#892733: marked as forwarded (gettext: msgfmt doesn't work with Java 9)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 15:53:03 +0100 (CET)
with message-id 
has caused the   report #892733,
regarding gettext: msgfmt doesn't work with Java 9
to be marked as having been forwarded to the upstream software
author(s) bug-gnu-gett...@gnu.org

(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.)


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

I've received the following report from the Debian BTS.

This is now serious for us because it makes a lot of packages to fail
to build from source.

[ Question for Emmanuel: Whenever a new GCC breaks a lot of packages,
  individual packages are still allowed to build-depend: old-gcc
  as a last resort. Would this be a possibility here? ]

Thanks.

-- Forwarded message --
From: Emmanuel Bourg 
To: Debian Bug Tracking System 
Date: Mon, 12 Mar 2018 12:04:37 +0100
Subject: gettext: msgfmt doesn't work with Java 9

Package: gettext
Version: 0.19.8.1-4
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

Hi,

msgfmt doesn't work with Java 9, when invoked with the --java2 parameter
it fails to detect the JDK and returns this error message:

  msgfmt: Java compiler not found, try installing gcj or set $JAVAC
  msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC

This issue breaks the build of at least two packages (plm and salliere).

It's possible to reproduce this issue by installing default-jdk/0.59+exp2
from experimental.

Emmanuel Bourg--- End Message ---

Bug#892045: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: usbguard-applet-qt: upgrading libqt5 to experimental's 5.10 breaks the applet)

[Adrian Bunk]

Control: reopen -1
Control: reassign -1 libqt5widgets5 5.10.1+dfsg-2
Control: affects -1 usbguard-applet-qt

On Fri, Mar 16, 2018 at 12:03:03PM +, Debian Bug Tracking System wrote:
>...
> Date: Fri, 16 Mar 2018 12:59:37 +0100
> From: Gianfranco Costamagna 
> To: 892045-d...@bugs.debian.org
> Subject: Re: usbguard-applet-qt: upgrading libqt5 to experimental's 5.10
>  breaks the applet
> 
> Hello,
> 
> On Sun, 04 Mar 2018 17:07:11 +0200 Mykola Nikishov  wrote:
> > Package: usbguard-applet-qt
> > Version: 0.7.0+ds1-2+b1
> > Severity: grave
> > Justification: renders package unusable
> > 
> > Nothing prevents the user from installing an incompatible Qt 5.10
> > libraries:
> > 
> > --8<---cut here---start->8---
> > $ usbguard-applet-qt 
> > Cannot mix incompatible Qt library (version 0x50a00) with this library 
> > (version 0x50a01)
> > Aborted
> > --8<---cut here---end--->8---
> > 
> 
> sorry but we can't enforce such dependencies, specially with experimental 
> versions of qt.

We can, and we should.

> The stack needs to be still fully bootstrapped and built, this is why it is 
> in experimental.

And then the stack goes piece by piece slowly into testing,
breaking everything there (and in Debian derivatives using testing).

> Stuff will and should self heal in a matter of days, if not, when the qt will 
> go in unstable, if a rebuild
> will be necessary, please open a bug against qtbase, for not providing a 
> stable ABI, and then affect this package.

Doing this now.

> G.
>...

cu
Adrian

-- 

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

Processed: Re: Bug#892045 closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: usbguard-applet-qt: upgrading libqt5 to experimental's 5.10 breaks the applet)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #892045 {Done: Gianfranco Costamagna } 
[usbguard-applet-qt] usbguard-applet-qt: upgrading libqt5 to experimental's 
5.10 breaks the applet
Bug reopened
Ignoring request to alter fixed versions of bug #892045 to the same values 
previously set
> reassign -1 libqt5widgets5 5.10.1+dfsg-2
Bug #892045 [usbguard-applet-qt] usbguard-applet-qt: upgrading libqt5 to 
experimental's 5.10 breaks the applet
Bug reassigned from package 'usbguard-applet-qt' to 'libqt5widgets5'.
No longer marked as found in versions usbguard/0.7.0+ds1-2.
Ignoring request to alter fixed versions of bug #892045 to the same values 
previously set
Bug #892045 [libqt5widgets5] usbguard-applet-qt: upgrading libqt5 to 
experimental's 5.10 breaks the applet
Marked as found in versions qtbase-opensource-src/5.10.1+dfsg-2.
> affects -1 usbguard-applet-qt
Bug #892045 [libqt5widgets5] usbguard-applet-qt: upgrading libqt5 to 
experimental's 5.10 breaks the applet
Added indication that 892045 affects usbguard-applet-qt

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

Processed: tagging 890925, tagging 889877

[Debian Bug Tracking System]

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

> tags 890925 + pending
Bug #890925 [src:acmetool] acmetool FTBFS with golang-1.10-go: FAIL: 
TestRedirector
Added tag(s) pending.
> tags 889877 + pending
Bug #889877 [acmetool] acmetool: FTBFS on ppc64el: cannot find package 
"golang.org/x/sys/unix"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: affects 873227

[Debian Bug Tracking System]

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

> affects 873227 src:bnd src:triplea
Bug #873227 [src:gradle] Please upgrade to 4.1: Java 9 support
Added indication that 873227 affects src:bnd and src:triplea
> thanks
Stopping processing here.

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

Processed: Also add the epoch

[Debian Bug Tracking System]

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

> notfound 875365 2.1.1-b31g+dfsg1-4
Bug #875365 [src:glassfish] FTBFS with Java 9: sun.misc
The source 'glassfish' and version '2.1.1-b31g+dfsg1-4' do not appear to match 
any binary packages
No longer marked as found in versions glassfish/2.1.1-b31g+dfsg1-4.
> found 875365 1:2.1.1-b31g+dfsg1-4
Bug #875365 [src:glassfish] FTBFS with Java 9: sun.misc
Marked as found in versions glassfish/1:2.1.1-b31g+dfsg1-4.
> thanks
Stopping processing here.

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

Processed: tagging 873972

[Debian Bug Tracking System]

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

> tags 873972 + buster sid
Bug #873972 [src:cadencii] FTBFS with Java 9 due to -source/-target only
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: block 875336 with 873227

[Debian Bug Tracking System]

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

> block 875336 with 873227
Bug #875336 [src:bnd] FTBFS with Java 9: _ as identifier
875336 was not blocked by any bugs.
875336 was not blocking any bugs.
Added blocking bug(s) of 875336: 873227
> thanks
Stopping processing here.

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

Processed: tagging 893102

[Debian Bug Tracking System]

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

> tags 893102 + pending
Bug #893102 [src:brltty] brltty FTBFS with openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#893105: clirr FTBFS with openjdk-9

[Adrian Bunk]

Source: clirr
Version: 0.6-5
Severity: serious
Tags: buster sid

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

...
compile:
[mkdir] Created dir: /build/1st/clirr-0.6/build/generated-sources
[javac] /usr/share/maven-ant-helper/maven-build.xml:356: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Using javac -target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 46 source files to /build/1st/clirr-0.6/build/classes
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/ant/AntLogger.java:3: error: 
unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] /build/1st/clirr-0.6/core/src/java/net/sf/clirr/ant/AntTask.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/ant/ChangeCounter.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/ant/PatternSetFilter.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] /build/1st/clirr-0.6/core/src/java/net/sf/clirr/cli/Clirr.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/ApiDifference.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/Checker.java:3: error: 
unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/CheckerException.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/ClassFilter.java:3: error: 
unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/ClassSelector.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/DiffListener.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/DiffListenerAdapter.java:3:
 error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/EventMessages.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/FileDiffListener.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/Message.java:3: error: 
unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/MessageManager.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/MessageTranslator.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/PlainDiffListener.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII

Bug#893101: bridge-method-injector FTBFS with openjdk-9

[Adrian Bunk]

Source: bridge-method-injector
Version: 1.18-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bridge-method-injector.html

...
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:1.8:run (default) on project 
bridge-method-injector: An Ant BuildException has occured: Compile failed; see 
the compiler error output for details.
[ERROR] around Ant part .. 
@ 17:125 in 
/build/1st/bridge-method-injector-1.18/injector/target/antrun/build-main.xml
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :bridge-method-injector
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/bridge-method-injector-1.18 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/bridge-method-injector-1.18/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/bridge-method-injector-1.18/debian 
-Dmaven.repo.local=/build/1st/bridge-method-injector-1.18/debian/maven-repo 
--batch-mode package javadoc:jar javadoc:aggregate -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 2

Bug#893102: brltty FTBFS with openjdk-9

[Adrian Bunk]

Source: brltty
Version: 5.6-2
Severity: serious

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

...
'/usr/lib/jvm/java-9-openjdk-amd64/bin/javac' -encoding UTF-8 -source 1.5 
-target 1.5 -d classes -classpath . ../../../Bindings/Java/Brlapi.java 
../../../Bindings/Java/ConnectionSettings.java 
../../../Bindings/Java/DisplaySize.java ../../../Bindings/Java/Error.java 
../../../Bindings/Java/Exception.java ../../../Bindings/Java/Key.java 
../../../Bindings/Java/Native.java ../../../Bindings/Java/Test.java 
../../../Bindings/Java/WriteArguments.java Constants.java
warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make[3]: *** [Makefile:96: classes.made] Error 2

Bug#893097: lynkeos.app: FTBFS on many architectures - PAGE_SIZE undeclared

[Yavor Doganov]

tags 893097 + pending
thanks

James Cowgill wrote:
> lynkeos.app FTBFS on many architectures (all except for x86, s390x and
> alpha) with the error:

Right; I've already fixed this in the Git repository, exactly in the
way you suggest.

Processed: Re: Bug#893097: lynkeos.app: FTBFS on many architectures - PAGE_SIZE undeclared

[Debian Bug Tracking System]

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

> tags 893097 + pending
Bug #893097 [src:lynkeos.app] lynkeos.app: FTBFS on many architectures - 
PAGE_SIZE undeclared
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#877457: stretch update for trafficserver

[Jean Baptiste Favre]

Hello Adrian,
I'd love to fix  it for Stretch.

But, I'm only a Debian Maintainer and I'm not sure I've upload rights.

Besides, I don't know the exact procedure I'll have to follow to
propagate such fixes to stable (but I'm eager to learn it :) )

Cheers,
Jean Baptiste

On 14/03/2018 18:58, Adrian Bunk wrote:
> On Wed, Jan 17, 2018 at 09:42:09AM +, Debian Bug Tracking System wrote:
>> ...
>>  trafficserver (7.1.1-1) unstable; urgency=medium
>>  .
>>* Fix trafficserver-dev dependencies. (Closes: #877457)
>> ...
> 
> Thanks a lot for fixing this bug for unstable.
> 
> It is still present in stretch, could you also fix it there?
> Alternatively, I can fix it for stretch if you don't object.
> 
> Thanks
> Adrian
> 

Bug#893100: beansbinding FTBFS with openjdk-9

[Adrian Bunk]

Source: beansbinding
Version: 1.2.1-3
Severity: serious

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

...
-do-compile:
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Using javac -target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 123 source files to 
/build/1st/beansbinding-1.2.1/build/classes
[javac] javac: source release 1.6 requires target release 1.6

BUILD FAILED
/build/1st/beansbinding-1.2.1/nbproject/build-impl.xml:245: The following error 
occurred while executing this line:
/build/1st/beansbinding-1.2.1/nbproject/build-impl.xml:126: Compile failed; see 
the compiler error output for details.

Total time: 3 minutes 52 seconds
make[1]: *** [debian/rules:10: override_dh_auto_build] Error 1

Bug#893097: lynkeos.app: FTBFS on many architectures - PAGE_SIZE undeclared

[James Cowgill]

Source: lynkeos.app
Version: 2.10+dfsg1-1
Severity: serious
Tags: sid buster

Hi,

lynkeos.app FTBFS on many architectures (all except for x86, s390x and
alpha) with the error:
> /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyCachePrefs.m: In 
> function '-[MyCachePrefs(Private) initPrefs]':
> /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyCachePrefs.m:60:33: 
> error: 'PAGE_SIZE' undeclared (first use in this function); did you mean 
> '_GSC_SIZE'?
> memSize = get_phys_pages() * PAGE_SIZE;
>  ^
>  _GSC_SIZE
> /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyCachePrefs.m:60:33: 
> note: each undeclared identifier is reported only once for each function it 
> appears in
> make[5]: *** [/usr/share/GNUstep/Makefiles/rules.make:479: 
> obj/Lynkeos.obj/MyCachePrefs.m.o] Error 1
> make[5]: *** Waiting for unfinished jobs
> gcc 
> /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/LynkeosStandardImageBuffer.m
>  -c \
>   -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I.. 
> -I/<>/lynkeos.app-2.10+dfsg1/GNUstep.. 
> -I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources 
> -I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThreadConnectionSources 
> -I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThirdPartySources/SMDoubleSlider
>  -DNO_FRAMEWORK_CHECK=1 -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 
> -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 
> -fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS 
> -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -O2 -g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime 
> -Wno-unknown-pragmas -Wno-cpp -fconstant-string-class=NSConstantString -I. 
> -I/usr/local/include/GNUstep -I/usr/include/GNUstep \
>-o obj/Lynkeos.obj/LynkeosStandardImageBuffer.m.o
> make[4]: *** [/usr/share/GNUstep/Makefiles/Instance/application.make:147: 
> internal-app-run-compile-submake] Error 2
> make[3]: *** [/usr/share/GNUstep/Makefiles/Master/rules.make:297: 
> Lynkeos.all.app.variables] Error 2
> make[2]: *** [/usr/share/GNUstep/Makefiles/Master/application.make:38: 
> internal-all] Error 2
> dh_auto_build: cd GNUstep && make -j2 -O "INSTALL=install 
> --strip-program=true" messages=yes "CFLAGS=-g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security" 
> "CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2" "CXXFLAGS=-g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security" "FCFLAGS=-g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong" "FFLAGS=-g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong" "GCJFLAGS=-g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong" "LDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--no-undefined 
> -Wl,--as-needed" "OBJCFLAGS=-g -O2 
> -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security" "OBJCXXFLAGS=-g 
> -O2 -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security" returned exit code 
> 2
> make[1]: *** [debian/rules:15: override_dh_auto_build] Error 25
> make[1]: Leaving directory '/<>/lynkeos.app-2.10+dfsg1'
> make: *** [debian/rules:12: build-arch] Error 2
> dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
> status 2

There are two problems here:

PAGE_SIZE is not necessarily a constant. For example, MIPS kernels can
be compiled with different flags to change the page size. If you need to
use the page size, you should use sysconf(_SC_PAGESIZE) instead which
will calculate it at runtime.

In this case, the PAGE_SIZE constant is provided by . The
entire contents of this header is highly architecture specific and
portable applications should not include it at all.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#893096: node-stream-browserify: FTBFS and Debci failure with node-process-nextick-args 2.0.0-1

[Adrian Bunk]

Source: node-stream-browserify
Version: 2.0.1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-stream-browserify.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-stream-browserify-2.0.1'
tape test/*.js
TAP version 13
# .writable writing ArrayBuffer
/usr/lib/nodejs/readable-stream/lib/_stream_writable.js:458
  asyncWrite(afterWrite, stream, state, finished, cb);
  ^

TypeError: asyncWrite is not a function
at onwrite (/usr/lib/nodejs/readable-stream/lib/_stream_writable.js:458:7)
at WritableState.onwrite 
(/usr/lib/nodejs/readable-stream/lib/_stream_writable.js:169:5)
at TestWritable._write 
(/build/1st/node-stream-browserify-2.0.1/test/buf.js:18:5)
at doWrite (/usr/lib/nodejs/readable-stream/lib/_stream_writable.js:406:64)
at writeOrBuffer 
(/usr/lib/nodejs/readable-stream/lib/_stream_writable.js:395:5)
at TestWritable.Writable.write 
(/usr/lib/nodejs/readable-stream/lib/_stream_writable.js:322:11)
at Test. 
(/build/1st/node-stream-browserify-2.0.1/test/buf.js:26:14)
at Test.bound [as _cb] (/usr/lib/nodejs/tape/lib/test.js:76:32)
at Test.run (/usr/lib/nodejs/tape/lib/test.js:95:10)
at Test.bound [as run] (/usr/lib/nodejs/tape/lib/test.js:76:32)
make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1

Bug#893098: axis FTBFS with openjdk-9

[Adrian Bunk]

Source: axis
Version: 1.4-25
Severity: serious
Tags: buster sid

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

...
compile:
[javac] /build/1st/axis-1.4/build.xml:99: warning: 'includeantruntime' was 
not set, defaulting to build.sysclasspath=last; set to false for repeatable 
builds
[javac] Using javac -source 1.3 is no longer supported, switching to 1.6
[javac] Using javac -target 1.3 is no longer supported, switching to 1.6
[javac] Compiling 633 source files to /build/1st/axis-1.4/build/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/axis-1.4/src/org/apache/axis/attachments/DimeAttachmentStreams.java:14:
 error: unmappable character (0x92) for encoding US-ASCII
[javac]  * use of Axis? DimeDelimitedInputStream to parse the data in the 
HTTP stream
[javac]   ^
[javac] 
/build/1st/axis-1.4/src/org/apache/axis/attachments/MultipartAttachmentStreams.java:27:
 error: unmappable character (0x92) for encoding US-ASCII
[javac]  * the root part of the multipart-related message). Our DIME 
counterpart didn?t
[javac] 
 ^
[javac] 
/build/1st/axis-1.4/src/org/apache/axis/components/net/JSSESocketFactory.java:419:
 error: unmappable character (0xE2) for encoding US-ASCII
[javac] // server???
[javac]  ^
[javac] 
/build/1st/axis-1.4/src/org/apache/axis/components/net/JSSESocketFactory.java:419:
 error: unmappable character (0x88) for encoding US-ASCII
[javac] // server???
[javac]   ^
[javac] 
/build/1st/axis-1.4/src/org/apache/axis/components/net/JSSESocketFactory.java:419:
 error: unmappable character (0x97) for encoding US-ASCII
[javac] // server???
[javac]^
[javac] 
/build/1st/axis-1.4/src/org/apache/axis/components/net/JSSESocketFactory.java:431:
 error: unmappable character (0xE2) for encoding US-ASCII
[javac] // I f we ??? r e i n s t r i c t mode ,
[javac]   ^
[javac] 
/build/1st/axis-1.4/src/org/apache/axis/components/net/JSSESocketFactory.java:431:
 error: unmappable character (0x80) for encoding US-ASCII
[javac] // I f we ??? r e i n s t r i c t mode ,
[javac]^
[javac] 
/build/1st/axis-1.4/src/org/apache/axis/components/net/JSSESocketFactory.java:431:
 error: unmappable character (0x99) for encoding US-ASCII
[javac] // I f we ??? r e i n s t r i c t mode ,
[javac] ^
[javac] 
/build/1st/axis-1.4/src/org/apache/axis/components/net/JSSESocketFactory.java:432:
 error: unmappable character (0xE2) for encoding US-ASCII
[javac] // [ ???.foo.com] is not allowed to match 
[a.b.foo.com]
[javac]  ^
[javac] 
/build/1st/axis-1.4/src/org/apache/axis/components/net/JSSESocketFactory.java:432:
 error: unmappable character (0x88) for encoding US-ASCII
[javac] // [ ???.foo.com] is not allowed to match 
[a.b.foo.com]
[javac]   ^
[javac] 
/build/1st/axis-1.4/src/org/apache/axis/components/net/JSSESocketFactory.java:432:
 error: unmappable character (0x97) for encoding US-ASCII
[javac] // [ ???.foo.com] is not allowed to match 
[a.b.foo.com]
[javac]^
[javac] /build/1st/axis-1.4/src/org/apache/axis/enum/Scope.java:17: error: 
as of release 5, 'enum' is a keyword, and may not be used as an identifier
[javac] package org.apache.axis.enum;
[javac] ^
[javac] /build/1st/axis-1.4/src/org/apache/axis/enum/Style.java:17: error: 
as of release 5, 'enum' is a keyword, and may not be used as an identifier
[javac] package org.apache.axis.enum;
[javac] ^
[javac] /build/1st/axis-1.4/src/org/apache/axis/enum/Use.java:17: error: as 
of release 5, 'enum' is a keyword, and may not be used as an identifier
[javac] package org.apache.axis.enum;
[javac] ^
[javac] 14 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/axis-1.4/build.xml:99: Compile failed; see the compiler error output 
for details.

Total time: 3 seconds
make: *** [/usr/share/cdbs/1/class/ant.mk:39: debian/stamp-ant-build] Error 1

Bug#875333: marked as done (FTBFS with Java 9: tools.jar)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 15:39:36 +0200
with message-id <20180316133936.GA1359@localhost>
and subject line Seems to be already fixed in unstable
has caused the Debian Bug report #875333,
regarding FTBFS with Java 9: tools.jar
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.)


-- 
875333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aspectj-maven-plugin
Version: 1.7-1
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

It's looking for tools.jar, which has gone.
There is an upstream issue:
https://github.com/mojohaus/aspectj-maven-plugin/issues/24

Build log:

INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] 'dependencies.dependency.systemPath' for com.sun:tools:jar must specify 
an absolute path but is ${toolsjarSystemPath} @ line 175, column 16
 @ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project org.codehaus.mojo:aspectj-maven-plugin:1.7 
(/build/aspectj-maven-plugin-1.7/pom.xml) has 1 error
[ERROR] 'dependencies.dependency.systemPath' for com.sun:tools:jar must 
specify an absolute path but is ${toolsjarSystemPath} @ line 175, column 16
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException




Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Version: 1.10-1

Seems to be already fixed in unstable:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/aspectj-maven-plugin.html

cu
Adrian

-- 

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

Bug#893084: marked as done (libxpp3-java FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 13:35:19 +
with message-id 
and subject line Bug#893084: fixed in libxpp3-java 1.1.4c-3
has caused the Debian Bug report #893084,
regarding libxpp3-java FTBFS with openjdk-9
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.)


-- 
893084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxpp3-java
Version: 1.1.4c-2
Severity: serious
Tags: buster sid

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

...
tests_main:
[mkdir] Created dir: /build/1st/libxpp3-java-1.1.4c/build/tests
[javac] /build/1st/libxpp3-java-1.1.4c/build.xml:438: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.3 is no longer supported, switching to 1.6
[javac] Using javac -target 1.3 is no longer supported, switching to 1.6
[javac] Compiling 25 source files to 
/build/1st/libxpp3-java-1.1.4c/build/tests
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/libxpp3-java-1.1.4c/src/java/tests/org/xmlpull/v1/tests/TestProcessDocdecl.java:104:
 error: unmappable character (0xA9) for encoding US-ASCII
[javac] //"? 1947 ?ditions Gallimard. ";
[javac]^
[javac] 
/build/1st/libxpp3-java-1.1.4c/src/java/tests/org/xmlpull/v1/tests/TestProcessDocdecl.java:104:
 error: unmappable character (0xC9) for encoding US-ASCII
[javac] //"? 1947 ?ditions Gallimard. ";
[javac]   ^
[javac] 
/build/1st/libxpp3-java-1.1.4c/src/java/tests/org/xmlpull/v1/tests/TestProcessDocdecl.java:112:
 error: unmappable character (0xA9) for encoding US-ASCII
[javac] "? 1947 ?ditions Gallimard. All rights reserved";
[javac]  ^
[javac] 
/build/1st/libxpp3-java-1.1.4c/src/java/tests/org/xmlpull/v1/tests/TestProcessDocdecl.java:112:
 error: unmappable character (0xC9) for encoding US-ASCII
[javac] "? 1947 ?ditions Gallimard. All rights reserved";
[javac] ^
[javac] 4 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/libxpp3-java-1.1.4c/build.xml:438: Compile failed; see the compiler 
error output for details.

Total time: 1 minute 10 seconds
make: *** [/usr/share/cdbs/1/class/ant.mk:39: debian/stamp-ant-build] Error 1
--- End Message ---
--- Begin Message ---
Source: libxpp3-java
Source-Version: 1.1.4c-3

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated libxpp3-java package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 16 Mar 2018 13:28:02 +0100
Source: libxpp3-java
Binary: libxpp3-java
Architecture: source
Version: 1.1.4c-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libxpp3-java - XML pull parser library for java
Closes: 893084
Changes:
 libxpp3-java (1.1.4c-3) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with Java 9 (Closes: #893084)
   * Removed the javadoc from the binary package
   * Build with the DH sequencer instead of CDBS
   * Moved the package to Git
   * Standards-Version updated to 4.1.3
   * Switch to debhelper level 11
   * Updated debian/copyright to the Copyright Format 1.0
Checksums-Sha1:
 5dfa573651bff8a79b2cb3f8671a6b88054e4d68 2145 

Processed: Not a problem in stretch, and fix version numbers

[Debian Bug Tracking System]

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

> tags 873213 buster sid
Bug #873213 [src:aspectj] FTBFS with Java 9
Added tag(s) sid and buster.
> tags 875333 buster sid
Bug #875333 [src:aspectj-maven-plugin] FTBFS with Java 9: tools.jar
Added tag(s) buster and sid.
> tags 873210 buster sid
Bug #873210 [src:basex] FTBFS with Java 9
Added tag(s) sid and buster.
> notfound 875336 2.4.1
Bug #875336 [src:bnd] FTBFS with Java 9: _ as identifier
The source 'bnd' and version '2.4.1' do not appear to match any binary packages
No longer marked as found in versions bnd/2.4.1.
> found 875336 2.4.1-7
Bug #875336 [src:bnd] FTBFS with Java 9: _ as identifier
Marked as found in versions bnd/2.4.1-7.
> notfound 873972 3.3.9+svn20110818.r1732
Bug #873972 [src:cadencii] FTBFS with Java 9 due to -source/-target only
The source 'cadencii' and version '3.3.9+svn20110818.r1732' do not appear to 
match any binary packages
No longer marked as found in versions cadencii/3.3.9+svn20110818.r1732.
> found 873972 3.3.9+svn20110818.r1732-5
Bug #873972 [src:cadencii] FTBFS with Java 9 due to -source/-target only
Marked as found in versions cadencii/3.3.9+svn20110818.r1732-5.
> tags 872946 buster sid
Bug #872946 [src:charactermanaj] FTBFS with openjdk-9
Added tag(s) sid and buster.
> notfound 875346 6.15
Bug #875346 [src:checkstyle] FTBFS with Java 9: tools.jar
The source 'checkstyle' and version '6.15' do not appear to match any binary 
packages
No longer marked as found in versions checkstyle/6.15.
> found 875346 6.15-1
Bug #875346 [src:checkstyle] FTBFS with Java 9: tools.jar
Marked as found in versions checkstyle/6.15-1.
> tags 875346 buster sid
Bug #875346 [src:checkstyle] FTBFS with Java 9: tools.jar
Added tag(s) buster and sid.
> notfound 873973 20110419
Bug #873973 [src:coco-java] FTBFS with Java 9 due to -source/-target only
The source 'coco-java' and version '20110419' do not appear to match any binary 
packages
No longer marked as found in versions coco-java/20110419.
> found 873973 20110419-3.1
Bug #873973 [src:coco-java] FTBFS with Java 9 due to -source/-target only
Marked as found in versions coco-java/20110419-3.1.
> tags 873973 buster sid
Bug #873973 [src:coco-java] FTBFS with Java 9 due to -source/-target only
Added tag(s) buster and sid.
> notfound 873975 2.4.1
Bug #873975 [src:cvc3] FTBFS with Java 9 due to -source/-target only
The source 'cvc3' and version '2.4.1' do not appear to match any binary packages
No longer marked as found in versions cvc3/2.4.1.
> found 873975 2.4.1-5.1
Bug #873975 [src:cvc3] FTBFS with Java 9 due to -source/-target only
Marked as found in versions cvc3/2.4.1-5.1.
> tags 873975 buster sid
Bug #873975 [src:cvc3] FTBFS with Java 9 due to -source/-target only
Added tag(s) buster and sid.
> notfound 873976 5.3.28
Bug #873976 [src:db5.3] FTBFS with Java 9 due to -source/-target only
The source 'db5.3' and version '5.3.28' do not appear to match any binary 
packages
No longer marked as found in versions db5.3/5.3.28.
> found 873976 5.3.28-13.1
Bug #873976 [src:db5.3] FTBFS with Java 9 due to -source/-target only
Marked as found in versions db5.3/5.3.28-13.1.
> notfound 875365 2.1.1-b31g+dfsg1
Bug #875365 [src:glassfish] FTBFS with Java 9: sun.misc
The source 'glassfish' and version '2.1.1-b31g+dfsg1' do not appear to match 
any binary packages
No longer marked as found in versions glassfish/2.1.1-b31g+dfsg1.
> found 875365 2.1.1-b31g+dfsg1-4
Bug #875365 [src:glassfish] FTBFS with Java 9: sun.misc
The source 'glassfish' and version '2.1.1-b31g+dfsg1-4' do not appear to match 
any binary packages
Marked as found in versions glassfish/2.1.1-b31g+dfsg1-4.
> tags 875365 buster sid
Bug #875365 [src:glassfish] FTBFS with Java 9: sun.misc
Added tag(s) buster and sid.
> notfound 875404 8.1.9+dfsg
Bug #875404 [src:gridengine] FTBFS with Java 9: sun.rmi.server
The source 'gridengine' and version '8.1.9+dfsg' do not appear to match any 
binary packages
No longer marked as found in versions gridengine/8.1.9+dfsg.
> found 875404 8.1.9+dfsg-5
Bug #875404 [src:gridengine] FTBFS with Java 9: sun.rmi.server
Marked as found in versions gridengine/8.1.9+dfsg-5.
> notfound 875369 1.4.13
Bug #875369 [src:hyperestraier] FTBFS with Java 9: fails to find javac
The source 'hyperestraier' and version '1.4.13' do not appear to match any 
binary packages
No longer marked as found in versions hyperestraier/1.4.13.
> found 875369 1.4.13-15
Bug #875369 [src:hyperestraier] FTBFS with Java 9: fails to find javac
Marked as found in versions hyperestraier/1.4.13-15.
> notfound 875582 0.3.2.1
Bug #875582 [src:jclic] FTBFS with Java 9: boot classpath misdetected
The source 'jclic' and version '0.3.2.1' do not appear to match any binary 
packages
No longer marked as found in versions jclic/0.3.2.1.
> found 875582 0.3.2.1-1
Bug #875582 [src:jclic] FTBFS with Java 9: boot classpath misdetected
Marked as found in versions jclic/0.3.2.1-1.
> tags 875582 buster sid
Bug #875582 [src:jclic] FTBFS with Java 9: boot classpath misdetected

Bug#891188: blends-dev: created d/control recommends packages not in main

[Andreas Tille]

Hi Ole,

On Fri, Mar 16, 2018 at 01:51:25PM +0100, Ole Streicher wrote:
> On 15.03.2018 19:41, Andreas Tille wrote:
> > I've commited a fix to Git which for me creates now sensible Debian
> > Astro metapackages.
> 
> For me, it actually upgrades the "Recommends" with to "Depends". For
> example, the "education" task (shortened):
> 
> ```
> Task: Education
> Install: true
> Description: Educational astronomy applications [...]
> 
> Recommends: celestia-gnome, gpredict, kstars
> Suggests: sunclock, xtide
> ```
> 
> becomes in d/control:
> 
> ```
> Package: astro-education
> Section: metapackages
> Architecture: all
> Depends: ${misc:Depends},
>  astro-tasks (= ${source:Version}),
>  gpredict,
>  kstars
> Recommends: celestia-gnome
> Suggests: sunclock,
>  xtide
> Description: Educational astronomy applications [...]
> ```

This does not sound good. :-(
 
> celestia-gnome is a package that does not exist in unstable.
> GENCONTROL_DEPENDS is set to TRUE.

My short term recommendation would be to set this to FALSE.

> In the moment, I would tend to rewrite blend-gen-control from scratch,
> using Python 3 and the standard Debian Python packages (debian.deb822,
> apt) in  a modular fashion. This would make the script much more
> maintainable (given the knowledge of Python is a bit better than Perl),
> and could also lead to create a "debian.blends" Python package that
> could be re-used for the Web pages.

I can only repeat:  Blends-dev *was* rewritten and creates correct
results:

https://salsa.debian.org/blends-team/blends-gsoc

I repeat again: This creates *architecture* dependent metapackages (I
explained here why only this makes sense).  I'm all for switching to
Python3 but a complete rewrite should not be necessary.  There are some
glithes in the code (for instance line breaking in the auto generated
part of d/changelog) and it definitely needs testing.

> Any thoughts on that? I'd volunteer here.

I *really* appreciate your effort but may be 80% of the work is just
done and you try blends-gsoc first.  As we all know the last 20% is
the harder part - but I urgently vote for using UDD as base for
anything we use.  May me using the public UDD mirror can help to not
force everybody who wants to run blends-dev having a local clone.
 
> Best regards

Thanks a lot for pushing things

  Andreas.
 

-- 
http://fam-tille.de

Processed: Pending fixes for bugs in the libxpp3-java package

[Debian Bug Tracking System]

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

> tag 893084 + pending
Bug #893084 [src:libxpp3-java] libxpp3-java FTBFS with openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#893084: Pending fixes for bugs in the libxpp3-java package

[pkg-java-maintainers]

tag 893084 + pending
thanks

Some bugs in the libxpp3-java package are closed in revision
e5aa0e11a517c5570d42f8cfae2650fecc7df35f in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libxpp3-java.git/commit/?id=e5aa0e1

Commit message:

Fixed the build failure with Java 9 (Closes: #893084)

Bug#891188: blends-dev: created d/control recommends packages not in main

[Ole Streicher]

Hi Andreas,

On 15.03.2018 19:41, Andreas Tille wrote:
> I've commited a fix to Git which for me creates now sensible Debian
> Astro metapackages.

For me, it actually upgrades the "Recommends" with to "Depends". For
example, the "education" task (shortened):

```
Task: Education
Install: true
Description: Educational astronomy applications [...]

Recommends: celestia-gnome, gpredict, kstars
Suggests: sunclock, xtide
```

becomes in d/control:

```
Package: astro-education
Section: metapackages
Architecture: all
Depends: ${misc:Depends},
 astro-tasks (= ${source:Version}),
 gpredict,
 kstars
Recommends: celestia-gnome
Suggests: sunclock,
 xtide
Description: Educational astronomy applications [...]
```

celestia-gnome is a package that does not exist in unstable.
GENCONTROL_DEPENDS is set to TRUE.

In the moment, I would tend to rewrite blend-gen-control from scratch,
using Python 3 and the standard Debian Python packages (debian.deb822,
apt) in  a modular fashion. This would make the script much more
maintainable (given the knowledge of Python is a bit better than Perl),
and could also lead to create a "debian.blends" Python package that
could be re-used for the Web pages.

Any thoughts on that? I'd volunteer here.

Best regards

Ole

Bug#891188: blends-dev: created d/control recommends packages not in main

[Andreas Tille]

Hi Wolfgang,

thanks a lot for checking.

On Fri, Mar 16, 2018 at 12:07:28PM +0100, Wolfgang Schweer wrote:
> On Thu, Mar 15, 2018 at 07:41:30PM +0100, Andreas Tille wrote:
> > I've commited a fix to Git which for me creates now sensible Debian
> > Astro metapackages.
> 
> I've checked how this fix would concern Debian Edu:
> 
> (1) The Debian Edu Makefile has to be adjusted:
> s/GENCONTROL_DEPENDS = true/#GENCONTROL_DEPENDS = true/
> 
> (2) Packages not available (any more) in testing are then correctly 
> demoted from Recommends to Suggests due to the $missinglist fix. (It 
> seems those have been wrongly kept as Recommends since the August 
> 2017 changes.)
> 
> (3) The strong depends on gosa-plugin-netgroups needed due to Bug 
> #793667¹ (IMO cause for 'GENCONTROL_DEPENDS = true') are a non issue 
> since ages. I figure in a similar case adding information to the
> Debian Edu upgrade chapter seems to be sufficient (if a smarter
> solution isn't easy).

I would summarise your check with: "Works for Debian Edu"

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#891372: marked as done (kbuild: FTBFS with glibc 2.27: undefined reference to `__alloca')

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 12:05:02 +
with message-id 
and subject line Bug#891372: fixed in kbuild 1:0.1.9998svn3149+dfsg-1
has caused the Debian Bug report #891372,
regarding kbuild: FTBFS with glibc 2.27: undefined reference to `__alloca'
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.)


-- 
891372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kbuild
Version: 1:0.1.9998svn3127+dfsg-1
Severity: important
User: debian-gl...@lists.debian.org
Usertags: 2.27

kbuild 1:0.1.9998svn3127+dfsg-1 fails to build with glibc 2.27
(2.27-0experimental0 from experimental):

| gcc -DHAVE_CONFIG_H -I. 
-I/<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob -I..   -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>/kbuild-0.1.9998svn3127+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -MT glob.o -MD -MP 
-MF .deps/glob.Tpo -c -o glob.o 
/<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c
| /<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c: In function 
'glob':
| /<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c:577:23: 
warning: implicit declaration of function '__alloca'; did you mean 'alloca'? 
[-Wimplicit-function-declaration]
|newp = (char *) __alloca (dirlen + 1);
|^~~~
|alloca
| /<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c:577:14: 
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
|newp = (char *) __alloca (dirlen + 1);
|   ^
| /<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c:705:15: 
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
| newp = (char *) __alloca (home_len + dirlen);
|^
| /<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c:728:15: 
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
| newp = (char *) __alloca (end_name - dirname);
|^
| /<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c:779:15: 
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
| newp = (char *) __alloca (home_len + rest_len + 1);
|^
| /<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c:815:11: 
warning: implicit declaration of function '__stat'; did you mean '__xstat'? 
[-Wimplicit-function-declaration]
|  : __stat (dirname, )) == 0
|^~
|__xstat
| /<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c: In function 
'glob_in_dir':
| /<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c:1271:21: 
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
| char *fullname = (char *) __alloca (dirlen + 1 + patlen + 1);
|  ^
| /<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c:1302:12: 
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
| names = (struct globlink *) __alloca (sizeof (struct globlink));
| ^
| /<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c:1360:32: 
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
|  struct globlink *new = (struct globlink *)
| ^
| /<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/glob.c:1386:15: 
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
|names = (struct globlink *) __alloca (sizeof (struct globlink));
|^
| mv -f .deps/glob.Tpo .deps/glob.Po
| gcc -DHAVE_CONFIG_H -I. 
-I/<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob -I..   -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>/kbuild-0.1.9998svn3127+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -MT fnmatch.o -MD -MP 
-MF .deps/fnmatch.Tpo -c -o fnmatch.o 
/<>/kbuild-0.1.9998svn3127+dfsg/src/kmk/glob/fnmatch.c
| mv -f .deps/fnmatch.Tpo .deps/fnmatch.Po
| rm -f libglob.a
| ar cru libglob.a glob.o fnmatch.o 
| ar: `u' modifier ignored since `D' is the default (see `U')
| ranlib libglob.a
| make[5]: Leaving directory 
'/<>/kbuild-0.1.9998svn3127+dfsg/out/linux.amd64/release/bootstrap/kmk/glob'

[...]

| gcc -Wall -Wextra -Wdeclaration-after-statement -Wshadow -Wpointer-arith 
-Wbad-function-cast -g -O2 
-fdebug-prefix-map=/<>/kbuild-0.1.9998svn3127+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro 
-Wl,--as-needed -o kmk ar.o arscan.o commands.o default.o dir.o expand.o file.o 
function.o getopt.o getopt1.o implicit.o 

Bug#892960: marked as done (libdrm FTBFS on arm*: symbol differences)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 12:05:12 +
with message-id 
and subject line Bug#892960: fixed in libdrm 2.4.91-2
has caused the Debian Bug report #892960,
regarding libdrm FTBFS on arm*: symbol differences
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.)


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

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

...
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/<>'
dh_makeshlibs -plibdrm2 -V'libdrm2 (>= 2.4.89)' --add-udeb=libdrm2-udeb -- -c4
dh_makeshlibs -plibdrm-nouveau2 -V'libdrm-nouveau2 (>= 2.4.66)' -- -c4
dh_makeshlibs -plibdrm-radeon1 -V'libdrm-radeon1 (>= 2.4.39)' -- -c4
dh_makeshlibs -plibdrm-amdgpu1 -V'libdrm-amdgpu1 (>= 2.4.90)' -- -c4
dh_makeshlibs -plibdrm-tegra0 -V'libdrm-tegra0' -- -c4
dh_makeshlibs -plibdrm-freedreno1 -V'libdrm-freedreno1 (>= 2.4.89)' -- -c4
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: debian/libdrm-freedreno1/DEBIAN/symbols doesn't match 
completely debian/libdrm-freedreno1.symbols
--- debian/libdrm-freedreno1.symbols (libdrm-freedreno1_2.4.91-1_arm64)
+++ dpkg-gensymbolsaJO5I2   2018-03-14 07:53:26.403570801 +
@@ -7,10 +7,12 @@
  fd_bo_from_fbdev@Base 0
  fd_bo_from_handle@Base 0
  fd_bo_from_name@Base 0
+ fd_bo_get_iova@Base 2.4.91-1
  fd_bo_get_name@Base 0
  fd_bo_handle@Base 0
  fd_bo_map@Base 0
  fd_bo_new@Base 0
+ fd_bo_put_iova@Base 2.4.91-1
  fd_bo_ref@Base 0
  fd_bo_size@Base 0
  fd_device_del@Base 0
dh_makeshlibs: failing due to earlier errors
debian/rules:103: recipe for target 'override_dh_makeshlibs' failed
make[1]: *** [override_dh_makeshlibs] Error 2
--- End Message ---
--- Begin Message ---
Source: libdrm
Source-Version: 2.4.91-2

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

Debian distribution maintenance software
pp.
Sven Joachim  (supplier of updated libdrm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Mar 2018 22:23:03 +0100
Source: libdrm
Binary: libdrm-dev libdrm2 libdrm-common libdrm2-udeb libdrm-intel1 
libdrm-nouveau2 libdrm-radeon1 libdrm-omap1 libdrm-freedreno1 libdrm-exynos1 
libdrm-tegra0 libdrm-amdgpu1 libdrm-etnaviv1
Architecture: source
Version: 2.4.91-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Sven Joachim 
Description:
 libdrm-amdgpu1 - Userspace interface to amdgpu-specific kernel DRM services -- 
run
 libdrm-common - Userspace interface to kernel DRM services -- common files
 libdrm-dev - Userspace interface to kernel DRM services -- development files
 libdrm-etnaviv1 - Userspace interface to etnaviv-specific kernel DRM services 
-- ru
 libdrm-exynos1 - Userspace interface to exynos-specific kernel DRM services -- 
run
 libdrm-freedreno1 - Userspace interface to msm/kgsl kernel DRM services -- 
runtime
 libdrm-intel1 - Userspace interface to intel-specific kernel DRM services -- 
runt
 libdrm-nouveau2 - Userspace interface to nouveau-specific kernel DRM services 
-- ru
 libdrm-omap1 - Userspace interface to omap-specific kernel DRM services -- 
runti
 libdrm-radeon1 - Userspace interface to radeon-specific kernel DRM services -- 
run
 libdrm-tegra0 - Userspace interface to tegra-specific kernel DRM services -- 
runt
 libdrm2- Userspace interface to kernel DRM services -- runtime
 libdrm2-udeb - Userspace interface to kernel DRM services -- runtime (udeb)
Closes: 892960
Changes:
 libdrm (2.4.91-2) unstable; urgency=medium
 .
   * Update libdrm-freedreno1.symbols and shlibs (Closes: #892960).
Checksums-Sha1:
 339048a76a9113f150203bf6af1e0cf8041a0dca 3040 libdrm_2.4.91-2.dsc
 1f6dfc63d813ead05db783414a3772bb3fdcf99f 50222 libdrm_2.4.91-2.diff.gz
Checksums-Sha256:
 

Bug#892045: marked as done (usbguard-applet-qt: upgrading libqt5 to experimental's 5.10 breaks the applet)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 12:59:37 +0100
with message-id <47849fdb-f186-3e49-71f1-36e48810d...@debian.org>
and subject line Re: usbguard-applet-qt: upgrading libqt5 to experimental's 
5.10 breaks the applet
has caused the Debian Bug report #892045,
regarding usbguard-applet-qt: upgrading libqt5 to experimental's 5.10 breaks 
the applet
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.)


-- 
892045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: usbguard-applet-qt
Version: 0.7.0+ds1-2+b1
Severity: grave
Justification: renders package unusable

Nothing prevents the user from installing an incompatible Qt 5.10
libraries:

--8<---cut here---start->8---
$ usbguard-applet-qt 
Cannot mix incompatible Qt library (version 0x50a00) with this library (version 
0x50a01)
Aborted
--8<---cut here---end--->8---

Downgrading a number of libqt5* from experimental back to
testing/unstable's 5.9 fixes the issue.

Could it be prevented by requiring libqt5* < 5.10?

-- System Information:
Debian Release: 9.3
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'stable'), (70, 'unstable'), (60, 
'testing'), (50, 'experimental'), (40, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-3-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)
LSM: AppArmor: enabled

Versions of packages usbguard-applet-qt depends on:
ii  libc6   2.26-6
ii  libgcc1 1:8-20180218-1
ii  libqt5core5a5.9.2+dfsg-12
ii  libqt5gui5  5.9.2+dfsg-12
ii  libqt5svg5  5.9.2-3
ii  libqt5widgets5  5.9.2+dfsg-12
ii  libstdc++6  8-20180218-1
ii  libusbguard00.7.0+ds1-2+b1
ii  usbguard0.7.0+ds1-2+b1

usbguard-applet-qt recommends no packages.

usbguard-applet-qt suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,

On Sun, 04 Mar 2018 17:07:11 +0200 Mykola Nikishov  wrote:
> Package: usbguard-applet-qt
> Version: 0.7.0+ds1-2+b1
> Severity: grave
> Justification: renders package unusable
> 
> Nothing prevents the user from installing an incompatible Qt 5.10
> libraries:
> 
> --8<---cut here---start->8---
> $ usbguard-applet-qt 
> Cannot mix incompatible Qt library (version 0x50a00) with this library 
> (version 0x50a01)
> Aborted
> --8<---cut here---end--->8---
> 

sorry but we can't enforce such dependencies, specially with experimental 
versions of qt.

The stack needs to be still fully bootstrapped and built, this is why it is in 
experimental.

Stuff will and should self heal in a matter of days, if not, when the qt will 
go in unstable, if a rebuild
will be necessary, please open a bug against qtbase, for not providing a stable 
ABI, and then affect this package.

G.

> Downgrading a number of libqt5* from experimental back to
> testing/unstable's 5.9 fixes the issue.
> 
> Could it be prevented by requiring libqt5* < 5.10?
> 
> -- System Information:
> Debian Release: 9.3
>   APT prefers oldoldstable
>   APT policy: (500, 'oldoldstable'), (500, 'stable'), (70, 'unstable'), (60, 
> 'testing'), (50, 'experimental'), (40, 'oldstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.14.0-3-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)
> LSM: AppArmor: enabled
> 
> Versions of packages usbguard-applet-qt depends on:
> ii  libc6   2.26-6
> ii  libgcc1 1:8-20180218-1
> ii  libqt5core5a5.9.2+dfsg-12
> ii  libqt5gui5  5.9.2+dfsg-12
> ii  libqt5svg5  5.9.2-3
> ii  libqt5widgets5  5.9.2+dfsg-12
> ii  libstdc++6  8-20180218-1
> ii  libusbguard00.7.0+ds1-2+b1
> ii  usbguard0.7.0+ds1-2+b1
> 
> usbguard-applet-qt recommends no packages.
> 
> usbguard-applet-qt suggests no packages.
> 
> -- no debconf information
> 
> 



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