Bug#874017: UDD: please import data on debug packages

[Paul Wise]

On Sat, Sep 2, 2017 at 9:42 AM, Stuart Prescott wrote:

> As a future extension, importing the data out of the "Build-Ids" field might
> also be useful, providing a service to figure out the package name that has
> the debug symbols based on build-id. (The space-separated format of Build-Ids
> doesn't appear to be documented in deb-control(5) just yet.)

I think a better option for Build-Ids would be to import data from
snapshot.d.o, so that you can get Build-Ids for any core dump, even
one that was generated from a process running on sid 3 weeks ago.
There is a service in development using this approach, running on
lw08.d.o and website available here:

http://build-id.debian.net/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?))

[Ben Caradoc-Davies]

I can confirm that udisks2 2.7.2-2 fixes the thunar problems that I 
reported above: I see only the "usual" filesystems and can mount and 
unmount removable devices as expected.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#833012: OpenPGP signature mangling rule for auto/default

[Sean Whitton]

Hello Osamu,

Thank you for working on this bug!

In the case there is a query string you have:

> + $options{'pgpsigurlmangle'} = [ 's/\?/.' . $suffix . 
> '?/', ];

And in the case with no query string, you use the old code:

> + $options{'pgpsigurlmangle'} = [ 's/$/.' . $suffix . 
> '/', ];

Shouldn't there be a '$' in the first one, too?

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#874020: lists.debian.org: Consider disabling/removing the "debian-research" mailing list

[Gunnar Wolf]

Package: lists.debian.org
Severity: normal

Hi listadmins,

I was unaware of the existence of the debian-research mailing list
before today. And that's quite odd, as I have followed activities
regarding "Debian from an academic perspective" for several years!

When I got to the list archives, it all became obvious: It is a
non-list. The last non-spam mail is from 2014. The last mail that got
a reply is from 2011. There are several interesting mails between 2005
and 2010, but we don't seem to be able even to reply to mails there
anymore.

My request, thus, is to remove this list. Having it listed might lead
externals into believing that's the place to invite people to
participate in studies, or to send CfPs, or to solve non-technical
questions (all of those cases have happened). It is a non-service, as
those people are likely just wasting their time waiting for an answer;
they might try some better places instead, or just give up on Debian
and go elsewhere.

Thanks for considering this request!

Bug#870069: orig-tarball-missing-upstream-signature error breaks rebuilding existing packages and more

[Paul Hardy]

Chris,

On Fri, Sep 1, 2017 at 8:11 AM, Chris Lamb  wrote:
>
> Can you think of another way your particular versions could be
> detected?

Sorry, I don't understand what you mean by "versions".  I do use a
watch file for Unifont; here is the heart of it:

opts=pgpsigurlmangle=s/$/.sig/ \
 ftp://ftp.gnu.org/gnu/unifont/unifont-([\d\.]+)/unifont-([\d\.]+)\.tar\.gz

The upstream signature file will always be a ".sig" binary file
generated with "gpg -b", because that is what is required to upload
the tarball to the GNU Project's server.

With my latest Debian Unifont package though, I re-encoded the
original ".sig" file to an ASCII-armored ".asc"  file.  I used a
method that Guillem Jover posted in the debian-policy thread that I
started, cited in my previous message for this bug report.  It was
either that or have lintian generate an error--or override the error,
which I did not want to do.

Thanks,


Paul Hardy

Bug#874019: Note that the '-e' argument to x-terminal-emulator works like '--'

[Sean Whitton]

Package: debian-policy
Version: 4.1.0.0
User: debian-pol...@packages.debian.org
Usertags: informative proposal
X-debbugs-cc: Thorsten Glaser 

A suggestion from mirabilos:

On Thu, Aug 24 2017, Thorsten Glaser wrote:

> OK, enough yak shaving and back to your original question. Yes, this
> is correct, although the wording could probably be improved to deal
> with arguments after -e that begin with a hyphen-minus.
>
> “xterm -e foo bar -T baz blah” will call “foo bar -T baz blah”, so
> the -e works like an implicit -- there.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#873929: gcc7: Enable libgo tests and rebuilds with make -C

[Matthias Klose]

On 01.09.2017 23:11, Svante Signell wrote:
> On Fri, 2017-09-01 at 13:32 +0200, Matthias Klose wrote:
>> On 01.09.2017 11:55, Svante Signell wrote:
>>> Source: gcc-7
>>> Version: 7.2.0-2
>>> Severity: important
>>> Tags: patch
>>>
>>> Hello,
>>>
>>> Currently the libgo tests are not run due to a bug in
>>> libgo/Makefile.am
>>> (and Makefile.in). This error is found on all architectures where
>>> the
>>> testsuite is enabled. The attached patch fixes this bug as well as
>>> enables rebuilds with
>>> make -C build//libgo clean;
>>> ;
>>> make -C build//libgo;
>>> by adding more entries to the CLEANFILES target.
>>>
>>> (The GOBENCH = entry is due to a trailing white space in the
>>> original
>>> file)
>>
>> ok, this is the libgo-testsuite.diff patch.  Why do you test
>> USE_DEJAGNU twice then?
> 
> I just found out that the test suite does not run properly, and created
> the patch making that Makefile snippet being the same as for gcc-6. The
> if then else fi logic is broken:
> See e.g. https://buildd.debian.org/status/fetch.php?pkg=gcc-7=amd6
> 4=7.2.0-2=1504127698=0
> 
> /usr/bin/make  check-DEJAGNU
> make[9]: Entering directory '/<>/build/x86_64-linux-
> gnu/32/libgo/testsuite'
> srcdir='../../../../../src/libgo/testsuite'; export srcdir; \
> EXPECT=`if [ -f ../../expect/expect ] ; then echo ../../expect/expect ;
> else echo expect ; fi`; export EXPECT; \
> runtest=`if [ -f ../../../../../src/libgo/../dejagnu/runtest ] ; then
> echo ../../../../../src/libgo/../dejagnu/runtest ; else echo runtest;
> fi`; \
> if /bin/bash -c "$runtest --version" > /dev/null 2>&1; then \
>   exit_status=0; l='libgo'; for tool in $l; do \
> if $runtest "TEST_GCC_EXEC_PREFIX=/usr/lib/gcc" --tool $tool --
> srcdir $srcdir --target_board=unix\{,-fstack-protector\}
> GOTEST_TMPDIR=gotest21736/test; \
> then :; else exit_status=1; fi; \
>   done; \
> else echo "WARNING: could not find \`runtest'" 1>&2; :;\
> fi; \
> exit $exit_status
> 
> for failed build logs.
> 
>> The go testsuite is special, because it's normally run from every
>> multilib directory instead of the top libdir only.
> 
> Sorry, I don't (yet) know what you mean, but will in due time. Perhaps
> with your help?

if you look at the check target for all other target libraries, then you'll see
that it doesn't descend into the multilib directories, e.g. 32 and x32 on amd64,
which it does for all target libs besides libgo.  Instead the target libraries
are iterated what you specifiy in RUNTESTFLAGS.  libgo doesn't do that, and
descends into the non-default multilib dirs itself.  This can be a problem if
you don't have a kernel running which understands all multilib variants, e.g.
x32. I'm happy to drop any of these patches, but a test run shouldn't try to
execute multilib variants when current running kernel doesn't support it.

Matthias

Bug#874018: compiz: FTBFS on x32 (time_t vs long confusion)

[Adam Borowski]

Package: compiz
Version: 1:0.9.13.0+16.10.20160818.2-5.1
Severity: normal
Tags: patch

Hi!
Here's a patch that fixes FTBFS on x32.  Compiz's code provides *time_t
while libstartup-notification wants *long.

This will happen a lot more in the future as the y2038 team wants to
redefine time_t as 64-bit on old 32-bit archs too.


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

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

Versions of packages compiz depends on:
ii  compiz-core 1:0.9.13.0+16.10.20160818.2-5.1+x32
ii  compiz-gnome1:0.9.13.0+16.10.20160818.2-5.1+x32
ii  compiz-plugins-default  1:0.9.13.0+16.10.20160818.2-5.1+x32

compiz recommends no packages.

compiz suggests no packages.

-- no debconf information
--- compiz-0.9.13.0+16.10.20160818.2.orig/src/screen.cpp
+++ compiz-0.9.13.0+16.10.20160818.2/src/screen.cpp
@@ -2163,19 +2163,20 @@
 bool
 cps::StartupSequence::handleStartupSequenceTimeout ()
 {
-struct timeval now, active;
+struct timeval now;
 double elapsed;
 
 gettimeofday (, NULL);
 
 foreach (CompStartupSequence *s, startupSequences)
 {
+   long active_sec, active_usec;
sn_startup_sequence_get_last_active_time (s->sequence,
- _sec,
- _usec);
+ _sec,
+ _usec);
 
-   elapsed = double) now.tv_sec - active.tv_sec) * 100.0 +
-   (now.tv_usec - active.tv_usec))) / 1000.0;
+   elapsed = double) now.tv_sec - active_sec) * 100.0 +
+   (now.tv_usec - active_usec))) / 1000.0;
 
if (elapsed > STARTUP_TIMEOUT_DELAY)
sn_startup_sequence_complete (s->sequence);

Bug#862875: RFS: libzc/0.3.1-1 [ITP] -- fast zip cracking library

[Marc Ferland]

On Mon, Jul 24, 2017 at 3:24 PM, Andrey Rahmatullin  wrote:
>
> Control: tags -1 + moreinfo
>
> Please either add check to B-D to enable tests or explicitly disable them
> in debian/rules.
> I don't think yazc should be in the libs section.
> Explicit Depends: libzc3 in yazc is not needed.
> Please switch to the debhelper compat level 10.
> Please update Standards-Version to the current version.
> lib/qsort.h is not described in debian/copyright as having a different
> license.
>

All done. Thanks for the review.

Please use:

   dget -x 
https://mentors.debian.net/debian/pool/main/libz/libzc/libzc_0.3.3-1.dsc

to get the new version.

Marc

Bug#874017: UDD: please import data on debug packages

[Stuart Prescott]

Package: qa.debian.org
Severity: wishlist
User: qa.debian@packages.debian.org
Usertags: udd

As noted in https://bugs.debian.org/873729 UDD could also import dbgsym
packages into the database. As a first implementation, they can just be
imported as another location for Sources and Packages information. The
following config snippet is what Judd's UDD is using to import these
packages.

debian-debug-sid:
  type: src-pkg
  archs: 
[amd64,arm64,armel,armhf,hurd-i386,i386,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,mips64el,powerpc,ppc64el,s390x]
  directory: /srv/mirrors/debian-debug/dists/sid-debug/
  components: [main, contrib, non-free]
  distribution: debian
  packages-table: packages
  sources-table: sources
  uploaders-table: uploaders
  packages-schema: packages
  sources-schema: sources
  release: sid-debug

As a future extension, importing the data out of the "Build-Ids" field might
also be useful, providing a service to figure out the package name that has
the debug symbols based on build-id. (The space-separated format of Build-Ids
doesn't appear to be documented in deb-control(5) just yet.)

cheers
Stuart

Bug#381040: There is no excuse for this not being fixed

[Nye Liu]

the upstream has had the fix for this for a long time.

Bug#872299: gnome-orca: Orca segfaults on startup

[Tim Smith]

I don't have braille that I know of.

Output of "make check -k" is below.

Regards,

Tim

-

./check gtk2
got :1.0 at /org/a11y/atspi/accessible/root
  end of list
got :1.2 at /org/a11y/atspi/accessible/root
  end of list
got :1.3 at /org/a11y/atspi/accessible/root
  end of list
got :1.4 at /org/a11y/atspi/accessible/root
  got :1.4 at /org/a11y/atspi/accessible/1
Got name 'Top Expanded Edge Panel'
  got :1.4 at /org/a11y/atspi/accessible/2
Got name 'Bottom Expanded Edge Panel'
  end of list
got :1.5 at /org/a11y/atspi/accessible/root
  got :1.5 at /org/a11y/atspi/accessible/1
Got name 'Desktop'
  got :1.5 at /org/a11y/atspi/accessible/2
Got name 'check-a11y'
Success
./check gtk3
got :1.0 at /org/a11y/atspi/accessible/root
  end of list
got :1.2 at /org/a11y/atspi/accessible/root
  end of list
got :1.3 at /org/a11y/atspi/accessible/root
  end of list
got :1.4 at /org/a11y/atspi/accessible/root
  got :1.4 at /org/a11y/atspi/accessible/1
Got name 'Top Expanded Edge Panel'
  got :1.4 at /org/a11y/atspi/accessible/2
Got name 'Bottom Expanded Edge Panel'
  end of list
got :1.5 at /org/a11y/atspi/accessible/root
  got :1.5 at /org/a11y/atspi/accessible/1
Got name 'Desktop'
  got :1.5 at /org/a11y/atspi/accessible/2
Got name 'check-a11y'
Success
./check qt4
got :1.0 at /org/a11y/atspi/accessible/root
  end of list
got :1.2 at /org/a11y/atspi/accessible/root
  end of list
got :1.3 at /org/a11y/atspi/accessible/root
  end of list
got :1.4 at /org/a11y/atspi/accessible/root
  got :1.4 at /org/a11y/atspi/accessible/1
Got name 'Top Expanded Edge Panel'
  got :1.4 at /org/a11y/atspi/accessible/2
Got name 'Bottom Expanded Edge Panel'
  end of list
got :1.5 at /org/a11y/atspi/accessible/root
  got :1.5 at /org/a11y/atspi/accessible/1
Got name 'Desktop'
  got :1.5 at /org/a11y/atspi/accessible/2
Got name 'check-a11y'
Success
./check qt5
got :1.0 at /org/a11y/atspi/accessible/root
  end of list
got :1.2 at /org/a11y/atspi/accessible/root
  end of list
got :1.3 at /org/a11y/atspi/accessible/root
  end of list
got :1.4 at /org/a11y/atspi/accessible/root
  got :1.4 at /org/a11y/atspi/accessible/1
Got name 'Top Expanded Edge Panel'
  got :1.4 at /org/a11y/atspi/accessible/2
Got name 'Bottom Expanded Edge Panel'
  end of list
got :1.5 at /org/a11y/atspi/accessible/root
  got :1.5 at /org/a11y/atspi/accessible/1
Got name 'Desktop'
  got :1.5 at /org/a11y/atspi/accessible/2
Got name 'check-a11y'
Success
./check java
got :1.0 at /org/a11y/atspi/accessible/root
  end of list
got :1.2 at /org/a11y/atspi/accessible/root
  end of list
got :1.3 at /org/a11y/atspi/accessible/root
  end of list
got :1.4 at /org/a11y/atspi/accessible/root
  got :1.4 at /org/a11y/atspi/accessible/1
Got name 'Top Expanded Edge Panel'
  got :1.4 at /org/a11y/atspi/accessible/2
Got name 'Bottom Expanded Edge Panel'
  end of list
got :1.5 at /org/a11y/atspi/accessible/root
  got :1.5 at /org/a11y/atspi/accessible/1
Got name 'Desktop'
  got :1.5 at /org/a11y/atspi/accessible/2
Got name 'check-a11y'
Success
./check java7
./check: 34: ./check: /usr/lib/jvm/java-7-openjdk-amd64/bin/java: not found
got :1.0 at /org/a11y/atspi/accessible/root
  end of list
got :1.2 at /org/a11y/atspi/accessible/root
  end of list
got :1.3 at /org/a11y/atspi/accessible/root
  end of list
got :1.4 at /org/a11y/atspi/accessible/root
  got :1.4 at /org/a11y/atspi/accessible/1
Got name 'Top Expanded Edge Panel'
  got :1.4 at /org/a11y/atspi/accessible/2
Got name 'Bottom Expanded Edge Panel'
  end of list
got :1.5 at /org/a11y/atspi/accessible/root
  got :1.5 at /org/a11y/atspi/accessible/1
Got name 'Desktop'
  got :1.5 at /org/a11y/atspi/accessible/2
Got name 'check-a11y'
Success
./check: 42: kill: No such process

./check java8
got :1.0 at /org/a11y/atspi/accessible/root
  end of list
got :1.2 at /org/a11y/atspi/accessible/root
  end of list
got :1.3 at /org/a11y/atspi/accessible/root
  end of list
got :1.4 at /org/a11y/atspi/accessible/root
  got :1.4 at /org/a11y/atspi/accessible/1
Got name 'Top Expanded Edge Panel'
  got :1.4 at /org/a11y/atspi/accessible/2
Got name 'Bottom Expanded Edge Panel'
  end of list
got :1.5 at /org/a11y/atspi/accessible/root
  got :1.5 at /org/a11y/atspi/accessible/1
Got name 'Desktop'
  got :1.5 at /org/a11y/atspi/accessible/2
Got name 'check-a11y'
Success
./check java9
./check: 36: ./check: /usr/lib/jvm/java-9-openjdk-amd64/bin/java: not found
got :1.0 at /org/a11y/atspi/accessible/root
  end of list
got :1.2 at /org/a11y/atspi/accessible/root
  end of list
got :1.3 at /org/a11y/atspi/accessible/root
  end of list
got :1.4 at /org/a11y/atspi/accessible/root
  got :1.4 at /org/a11y/atspi/accessible/1
Got name 'Top Expanded Edge Panel'
  got :1.4 at /org/a11y/atspi/accessible/2
Got name 'Bottom Expanded Edge Panel'
  end of list
got :1.5 at /org/a11y/atspi/accessible/root
  got :1.5 at /org/a11y/atspi/accessible/1
Got name 

Bug#871348: Pending fixes for bugs in the robocode package

[pkg-java-maintainers]

tag 871348 + pending
thanks

Some bugs in the robocode package are closed in revision
c2f125d7105546b5d3dde983a3bc6721d48fc4c3 in branch 'master' by Markus
Koschany

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

Commit message:

Ignore robocode.distribution module to work around a FTBFS related to Maven

and the maven-assembly-plugin.

Closes: #871348

Bug#873807: ssh-askpass FTCBFS: xmkmf is unfixable

[Philip Hands]

Helmut Grohne  writes:

> Source: ssh-askpass
> Version: 1:1.2.4.1-9
> Tags: patch upstream
> User: helm...@debian.org
> Usertags: rebootstrap
> Control: block 873764 by -1
>
> ssh-askpass fails to cross build from source, because ... it uses xmkmf.
> I looked at xmkmf hard and there seems to be no way to make this work at
> all. I talked to vorlon, and we agreed that xmkmf should just die
> (#873764). As such I am asking you to migrate away from xmkmf. I am
> attaching a patch moves to autoconf in a minimal way that makes the
> binary package look mostly equal to the original package (according to
> diffoscope). Oh and the patch makes cross building work. Can you apply
> it? Or at least, can you remove xmkmf usage?

Done, and thanks very much for the patch, and the nudge.

I've been neglecting this package for way too long, so that gave me a
reason to fix some old bugs too.  :-)

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#794692: pulseaudio: please build pulseaudio-module-dev

[Jonathan Lane]

Package: pulseaudio
Version: 10.0-1+deb9u1
Followup-For: Bug #794692

Why does the API being unstable matter?  Debian isn't going to move to the next
integer version of PulseAudio within a release.  Please consider packaging this
or at the very least making the xrdp module a separate package for 
stretch-backports if not buster.  By that same inane logic you'd never ship 
kernel headers, since the kernel APIs and ABIs change all the time.

Jon
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; enable-remixing = yes
; enable-lfe-remixing = no
; lfe-crossover-freq = 0

; flat-volumes = yes

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 20

; default-sample-format = s16le
; default-sample-rate = 44100
; alternate-sample-rate = 48000
; default-sample-channels = 2
; default-channel-map = front-left,front-right

; default-fragments = 4
; default-fragment-size-msec = 25

; enable-deferred-volume = yes
; deferred-volume-safety-margin-usec = 8000
; deferred-volume-extra-delay-usec = 0
#!/usr/bin/pulseaudio -nF
#
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

# This startup script is used only if PulseAudio is started per-user
# (i.e. not in system mode)

.fail

### Automatically restore the volume of streams and devices
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore

### Automatically augment property information from .desktop files

Bug#871956: lintian: false positive: binary-file-built-without-LFS-support on x32

[Adam Borowski]

On Sat, Sep 02, 2017 at 12:18:59AM +0200, Boud Roukema wrote:
> On Fri, 1 Sep 2017, Adam Borowski wrote:
> > And what AC_SYS_LARGEFILE does, at least on Linux, is to return a hardcoded
> > setting so programs switch from off_t to off64_t whether they need to or
> > not.  This does the right thing on old 32-bit archs and is harmless on
> > 64-bit and new 32-bit.
> 
> AC_SYS_LARGEFILE on i386 (linux) for mpgrafic-0.3.15-1 apparently does *not*
> always do the right thing:

You call it but don't actually use what it returns: 

mpicc -DHAVE_CONFIG_H -I.  -I..  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2
-fdebug-prefix-map=/<>=.  -fstack-protector-strong -Wformat
-Werror=format-security -c -o parallel_io.o parallel_io.c

#define _XOPEN_SOURCE 500
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

You don't include "config.h" anywhere.

> > N: Processing source package mpgrafic (version 0.3.15-1, arch source) ...
> > C: mpgrafic source (0.3.15-1) [source]: debian-build-system dh
> > C: mpgrafic source (0.3.15-1) [source]: source-format 3.0 (quilt)
> > P: mpgrafic source (0.3.15-1) [source]: debian-watch-may-check-gpg-signature
> > N: 
> > N: Processing binary package mpgrafic (version 0.3.15-1, arch i386) ...
> > X: mpgrafic binary (0.3.15-1) [i386]: binary-file-built-without-LFS-support 
> > usr/bin/mpgrafic
> > C: mpgrafic binary (0.3.15-1) [i386]: no-ctrl-scripts
> > N: 
> > N: Processing binary package mpgrafic (version 0.3.15-1, arch amd64) ...
> > C: mpgrafic binary (0.3.15-1) [amd64]: no-ctrl-scripts
> > N: 
> > N: Processing binary package mpgrafic-dbgsym (version 0.3.15-1, arch i386) 
> > ...
> > C: mpgrafic-dbgsym binary (0.3.15-1) [i386]: no-ctrl-scripts
> > N: 
> > N: Processing binary package mpgrafic-dbgsym (version 0.3.15-1, arch amd64) 
> > ...
> 
> https://anonscm.debian.org/git/debian-astro/packages/mpgrafic.git/tree/configure.ac
> 
> https://anonscm.debian.org/git/debian-astro/packages/mpgrafic.git/tree/configure
> 
> This is a lintian false positive with AC_SYS_LARGEFILE.

Nope, you use pwrite() not pwrite64() -- on i386 you need the latter to get
LFS; they're aliases only on amd64, x32 and so on.


But in any case, even if it had been indeed a false positive, it'd be a
different bug.

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
⠈⠳⣄ 

Bug#860268: .desktop files can hide malware in Nautilus

[Phil Wyett]

On Fri, 2017-09-01 at 21:53 +0200, intrigeri wrote:
> Hi!
> 
> Micah Lee:
> > The upstream nautilus issue [1] has already been resolved, and will be
> > released in nautilus 3.24. But since this is an important security
> > issue, I think this patch should be backported so that it's fixed in
> > older versions of Debian.
> 
> Thanks for raising this issue in Debian!
> 
> Is there any plan upstream to backport this fix to their 3.22.x
> branch, and/or to request a CVE?
> 
> Did you personally check whether it's straightforward to backport the
> fix to 3.22?
> 
> Cheers,

Hi,

Seeing this bug. I have backported from the upstream patch (hash issue with
upstream diff) for testing purposes and all looks good. If anyone wishes to
test, a debdiff is attached.

The debdiff is prepared with a 'stretch-pu' in mind.

If any edits are required, please do not hesitate to let me know.

Regards

Phil

-- 
*** If this is a mailing list, I am subscribed, no need to CC me.***

Playing the game for the games sake.

Web: https://kathenas.org

Twitter: kathenasorg

Instagram: kathenasorgdiff -Nru nautilus-3.22.3/debian/changelog nautilus-3.22.3/debian/changelog
--- nautilus-3.22.3/debian/changelog	2017-03-09 01:39:58.0 +
+++ nautilus-3.22.3/debian/changelog	2017-09-01 23:43:51.0 +0100
@@ -1,3 +1,10 @@
+nautilus (3.22.3-1.1) stretch; urgency=high
+
+  * Non-maintainer upload.
+  * Backport desktop file trust patch from upstream. (Closes: #860268).
+
+ -- Phil Wyett   Fri, 01 Sep 2017 23:43:51 +0100
+
 nautilus (3.22.3-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru nautilus-3.22.3/debian/patches/desktop_file_trust.patch nautilus-3.22.3/debian/patches/desktop_file_trust.patch
--- nautilus-3.22.3/debian/patches/desktop_file_trust.patch	1970-01-01 01:00:00.0 +0100
+++ nautilus-3.22.3/debian/patches/desktop_file_trust.patch	2017-09-01 23:43:51.0 +0100
@@ -0,0 +1,408 @@
+From 1630f53481f445ada0a455e9979236d31a8d3bb0 Mon Sep 17 00:00:00 2001
+From: Carlos Soriano 
+Date: Mon, 6 Feb 2017 18:47:54 +0100
+Subject: mime-actions: use file metadata for trusting desktop files
+
+Currently we only trust desktop files that have the executable bit
+set, and don't replace the displayed icon or the displayed name until
+it's trusted, which prevents for running random programs by a malicious
+desktop file.
+
+However, the executable permission is preserved if the desktop file
+comes from a compressed file.
+
+To prevent this, add a metadata::trusted metadata to the file once the
+user acknowledges the file as trusted. This adds metadata to the file,
+which cannot be added unless it has access to the computer.
+
+Also remove the SHEBANG "trusted" content we were putting inside the
+desktop file, since that doesn't add more security since it can come
+with the file itself.
+
+https://bugzilla.gnome.org/show_bug.cgi?id=777991
+
+https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860268
+ .
+ nautilus (3.22.3-1.1) stretch; urgency=high
+ .
+   * Non-maintainer upload.
+   * Backport desktop file trust patch from upstream. (Closes: #860268)
+Author: Phil Wyett 
+---
+
+--- nautilus-3.22.3.orig/src/nautilus-directory-async.c
 nautilus-3.22.3/src/nautilus-directory-async.c
+@@ -30,6 +30,7 @@
+ #include "nautilus-global-preferences.h"
+ #include "nautilus-link.h"
+ #include "nautilus-profile.h"
++#include "nautilus-metadata.h"
+ #include 
+ #include 
+ #include 
+@@ -3580,13 +3581,17 @@ is_link_trusted (NautilusFile *file,
+ {
+ GFile *location;
+ gboolean res;
++g_autofree gchar* trusted = NULL;
+ 
+ if (!is_launcher)
+ {
+ return TRUE;
+ }
+ 
+-if (nautilus_file_can_execute (file))
++trusted = nautilus_file_get_metadata (file,
++  NAUTILUS_METADATA_KEY_DESKTOP_FILE_TRUSTED,
++  NULL);
++if (nautilus_file_can_execute (file) && trusted != NULL)
+ {
+ return TRUE;
+ }
+--- nautilus-3.22.3.orig/src/nautilus-file-operations.c
 nautilus-3.22.3/src/nautilus-file-operations.c
+@@ -235,10 +235,10 @@ typedef struct
+ #define COPY_FORCE _("Copy _Anyway")
+ 
+ static void
+-mark_desktop_file_trusted (CommonJob*common,
+-   GCancellable *cancellable,
+-   GFile*file,
+-   gboolean  interactive);
++mark_desktop_file_executable (CommonJob*common,
++  GCancellable *cancellable,
++  GFile*file,
++  gboolean  interactive);
+ 
+ static gboolean
+ is_all_button_text (const char *button_text)
+@@ -5290,10 +5290,10 @@ retry:
+ g_file_equal (copy_job->desktop_location, dest_dir) &&
+ is_trusted_desktop_file (src, job->cancellable))
+ {
+-mark_desktop_file_trusted (job,
+-   

Bug#874016: synaptic: can't launch synaptic from non-root user

[Sebastian Llanes]

Package: synaptic
Version: 0.84.2
Severity: important

Dear Maintainer,

   * Installed Debian and synaptic was working fine at first, but when I
installed Xfce instead of Gnome it stopped working.
   * Tried reinstalling synaptic, nothing happened.



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

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.15-1
ii  libapt-inst2.0   1.4.7
ii  libapt-pkg5.01.4.7
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u1
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:6.3.0-18
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgnutls30  3.5.8-5+deb9u2
ii  libgtk-3-0   3.22.11-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpcre2-8-0 10.22-3
ii  libstdc++6   6.3.0-18
ii  libvte-2.91-00.46.1-1
ii  libx11-6 2:1.6.4-3
ii  libxapian30  1.4.3-2
ii  policykit-1  0.105-18
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages synaptic recommends:
ii  libgtk2-perl   2:1.2499-1
ii  rarian-compat  0.8.1-6+b1
ii  xdg-utils  1.1.1-1

Versions of packages synaptic suggests:
pn  apt-xapian-index 
pn  deborphan
pn  dwww 
pn  menu 
ii  software-properties-gtk  0.96.20.2-1
ii  tasksel  3.39

-- no debconf information

Bug#853831: libqt5gui5: font rendering broken

[Ed Peguillan III]

Package: libqt5gui5
Version: 5.9.1+dfsg-9
Followup-For: Bug #853831

Dear Maintainer,

I think my problem is related. I initially thought the problem was with
qjackctl specifically, but I realized that many qt5 applications would
not start that depended on libqt5gui5, such as virtualbox.

This error is given when starting qjackctl or virtualbox:

$ virtualbox 
/usr/lib/virtualbox/VirtualBox: symbol lookup error:
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: undefined symbol:
FT_Property_Set

$ qjackctl 
qjackctl: symbol lookup error:
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: undefined symbol:
FT_Property_Set

See #873792 @
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873792

After I deleted the file I mentioned in that bug report, virtualbox and
qjackctl started, until I rebooted my machine. Now it is back to the
same error.

I had infinality fonts installed from this git repo
https://github.com/cmpitg/infinality-debian-package
This may be the cause of the conflict. Unfortunately, I don't know enough about 
this to figure out what is wrong. Uninstalling infinality did not fix the 
problem.

# apt install --reinstall libqt5gui5

did not work.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (1000, 'testing'), (1000, 'stable'), (750, 'stable'), (50, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libqt5gui5 depends on:
ii  fontconfig   2.12.3-0.2
ii  libc62.24-14
ii  libdrm2  2.4.82-1
ii  libegl1-mesa [libegl1-x11]   13.0.6-1+b2
ii  libfontconfig1   2.12.3-0.2
ii  libfreetype6 2.8-0.2
ii  libgbm1  13.0.6-1+b2
ii  libgcc1  1:7.2.0-1
ii  libgl1-mesa-glx [libgl1] 13.0.6-1+b2
ii  libglib2.0-0 2.53.4-3
ii  libharfbuzz0b1.4.2-1
ii  libice6  2:1.0.9-2
ii  libinput10   1.8.0-1
ii  libjpeg62-turbo  1:1.5.2-2
ii  libmtdev11.1.5-1+b1
ii  libpng16-16  1.6.31-1
ii  libqt5core5a [qtbase-abi-5-9-0]  5.9.1+dfsg-9
ii  libqt5dbus5  5.9.1+dfsg-9
ii  libqt5network5   5.9.1+dfsg-9
ii  libsm6   2:1.2.2-1+b3
ii  libstdc++6   7.2.0-1
ii  libudev1 234-2.3
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb-glx0  1.12-1
ii  libxcb-icccm40.4.1-1+b1
ii  libxcb-image00.4.0-1+b2
ii  libxcb-keysyms1  0.4.0-1+b2
ii  libxcb-randr01.12-1
ii  libxcb-render-util0  0.3.9-1+b1
ii  libxcb-render0   1.12-1
ii  libxcb-shape01.12-1
ii  libxcb-shm0  1.12-1
ii  libxcb-sync1 1.12-1
ii  libxcb-xfixes0   1.12-1
ii  libxcb-xinerama0 1.12-1
ii  libxcb-xkb1  1.12-1
ii  libxcb1  1.12-1
ii  libxi6   2:1.7.9-1
ii  libxkbcommon-x11-0   0.7.1-1
ii  libxkbcommon00.7.1-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages libqt5gui5 recommends:
ii  libqt5svg5 5.9.1-2+b1
ii  qt5-gtk-platformtheme  5.9.1+dfsg-9

Versions of packages libqt5gui5 suggests:
pn  qt5-image-formats-plugins  
pn  qtwayland5 

-- no debconf information

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Josh Triplett]

On Fri, Sep 01, 2017 at 09:57:09AM +0200, Uwe Kleine-König wrote:
> On Fri, Sep 01, 2017 at 12:02:12AM -0700, Josh Triplett wrote:
> > On Thu, Aug 31, 2017 at 08:47:55PM -0400, Christopher Li wrote:
> > > On Thu, Aug 31, 2017 at 4:55 PM, Uwe Kleine-König  Yes
> > > that works. So to address the Debian bug I can do:
> > > >
> > > >  - move sparse to /usr/lib
> > > >  - teach cgcc about the move of sparse
> > > >  - make /usr/bin/sparse call cgcc -no-compile "$@"
> > > 
> > > I don't like that. It means the user can't invoke sparse directly.
> > > 
> > > >
> > > > or is it easier to teach sparse about the architecture stuff?
> > > 
> > > First of all. It is not very trivial to teach sparse about the 
> > > architecture
> > > stuff. To my mind, we need to move all the cgcc logic into sparse.
> > 
> > Related to that: while it would mean we couldn't necessarily just rely
> > entirely on GCC's definitions for a target platform, I think in an ideal
> > world we could have a sparse binary that understood *all* target
> > platforms at once, such that you could ask Sparse on x86_64 to "compile"
> > as though targeting any arbitrary architecture. That would also have the
> > major advantage of making it easy to run the Sparse testsuite for
> > *every* target architecture without needing compilers for every such
> > architecture.
> 
> You'd need the target arch's system headers though.

Only for building userspace code, not for building standalone/kernel
code, or the Sparse testsuite.

- Josh Triplett

Bug#873822: RFS: achilles/2-9 [QA]

[David William Richmond Davies-Jones]

It was with compat level 10.

On 01/09/17 23:28, Tobias Frost wrote:
> Am Freitag, den 01.09.2017, 23:01 +0100 schrieb David William Richmond
> Davies-Jones:
>> I did do an upload here I dropped the build-dep, but it threw up a
>> warning about outdated config.{sub|guess}. Should I ignore this?
> 
> This was probably before setting compat level 10?
> (As said, d/compat == 10 does the magic, see https://lists.debian.org/d
> ebian-devel/2016/04/msg00018.html)
> 
> 
> 
>> On 01/09/17 22:59, Tobias Frost wrote:
>>> Am Freitag, den 01.09.2017, 21:14 +0100 schrieb David William
>>> Richmond
>>> Davies-Jones:
 Hello

 I have fixed the problems with the copyright file, deleted the
 stray
 file, and fixed the lintian warnings about encoding in desktop
 file
 and
 description started with synopsis.
>>>
>>> OK
>>>
 I also *think* that I've got everything sorted with autoreconf
 etc,
 but
 to be honest I always seem to have trouble and get confused with
 them.
>>>
>>> With compat level 10 dh-autoreconf is default -> you do not need B-
>>> D on
>>> it or autotools-dev anymore. That should fix the warning :)
>>>
>>> Fix this and reupload... Then we're ready, I guess!
>>>
>>> Thanks for the package!
>>>
>>> --
>>> tobi
>>>
>>>
 David

 On 31/08/17 22:17, Tobias Frost wrote:
> Control: owner -1 !
> Control: tags -1 moreinfo
>
> Hallo David,
>
> The package is already in a nice state; many thanks for
> updating
> it!
>
> However some fixes are required:
>
> - d/copyright needs fixing:
>   - as it says "Copyright: ?"... I think it must be 
> Copyright: 2000 Matthew Danish 
>   - Also the License is GPL-2+
>   - The license grant is not copied verbatimly 
>
> - d/manpage is a stray file.
>
> - Please (try to) fix those linitan warnings or evaluate if
> they
> are
> valid:
>
> W: achilles source: useless-autoreconf-build-depends autotools-
> dev
> I: achilles source: debian-watch-file-is-missing
> I: achilles: hardening-no-bindnow usr/bin/achilles
> W: achilles: description-synopsis-starts-with-article
> I: achilles: desktop-entry-contains-encoding-key
> usr/share/applications/achilles.desktop:3 Encoding
> I: achilles: desktop-entry-lacks-keywords-entry
> usr/share/applications/achilles.desktop
>
>
> --
> tobi
>
>>
>>

Bug#832176: Ping

[Bastien ROUCARIES]

Ping ?

Any progress ?

Bug#873822: RFS: achilles/2-9 [QA]

[Tobias Frost]

Am Freitag, den 01.09.2017, 23:01 +0100 schrieb David William Richmond
Davies-Jones:
> I did do an upload here I dropped the build-dep, but it threw up a
> warning about outdated config.{sub|guess}. Should I ignore this?

This was probably before setting compat level 10?
(As said, d/compat == 10 does the magic, see https://lists.debian.org/d
ebian-devel/2016/04/msg00018.html)



> On 01/09/17 22:59, Tobias Frost wrote:
> > Am Freitag, den 01.09.2017, 21:14 +0100 schrieb David William
> > Richmond
> > Davies-Jones:
> > > Hello
> > > 
> > > I have fixed the problems with the copyright file, deleted the
> > > stray
> > > file, and fixed the lintian warnings about encoding in desktop
> > > file
> > > and
> > > description started with synopsis.
> > 
> > OK
> > 
> > > I also *think* that I've got everything sorted with autoreconf
> > > etc,
> > > but
> > > to be honest I always seem to have trouble and get confused with
> > > them.
> > 
> > With compat level 10 dh-autoreconf is default -> you do not need B-
> > D on
> > it or autotools-dev anymore. That should fix the warning :)
> > 
> > Fix this and reupload... Then we're ready, I guess!
> > 
> > Thanks for the package!
> > 
> > --
> > tobi
> > 
> > 
> > > David
> > > 
> > > On 31/08/17 22:17, Tobias Frost wrote:
> > > > Control: owner -1 !
> > > > Control: tags -1 moreinfo
> > > > 
> > > > Hallo David,
> > > > 
> > > > The package is already in a nice state; many thanks for
> > > > updating
> > > > it!
> > > > 
> > > > However some fixes are required:
> > > > 
> > > > - d/copyright needs fixing:
> > > >   - as it says "Copyright: ?"... I think it must be 
> > > > Copyright: 2000 Matthew Danish 
> > > >   - Also the License is GPL-2+
> > > >   - The license grant is not copied verbatimly 
> > > > 
> > > > - d/manpage is a stray file.
> > > > 
> > > > - Please (try to) fix those linitan warnings or evaluate if
> > > > they
> > > > are
> > > > valid:
> > > > 
> > > > W: achilles source: useless-autoreconf-build-depends autotools-
> > > > dev
> > > > I: achilles source: debian-watch-file-is-missing
> > > > I: achilles: hardening-no-bindnow usr/bin/achilles
> > > > W: achilles: description-synopsis-starts-with-article
> > > > I: achilles: desktop-entry-contains-encoding-key
> > > > usr/share/applications/achilles.desktop:3 Encoding
> > > > I: achilles: desktop-entry-lacks-keywords-entry
> > > > usr/share/applications/achilles.desktop
> > > > 
> > > > 
> > > > --
> > > > tobi
> > > > 
> 
> 

Bug#872544: dbusada: Please update for gnat-7

[Gianfranco Costamagna]

hello!

welcome back :)


dcut ssh-upload cancel -f dbusada_0.4.0-0.1_amd64.changes
Uploading commands file to ssh.upload.debian.org (incoming: 
/srv/upload.debian.org/UploadQueue/)
SCP is deprecated. Please consider upgrading to SFTP.
Uploading locutus-1504304589.commands to ssh-upload


please don't make the patches on the BTS useless/lost if possible :D

G.


Il Venerdì 1 Settembre 2017 16:30, Reto Buerki  ha scritto:



Hi,


On 09/01/2017 01:41 PM, Gianfranco Costamagna wrote:

> since we got no answer, and this is blocking the gnat transition (one of the 
> last blockers), I think

> we should bump severity and go ahead even without a maintainer answer (please 
> followup, there is still

> time to address the issue without having to NMU the package).

> 

> the following attached tarballs are part of the package uploaded in unstable.

> 

> I'm also attaching the debdiff and the filtered debdiff for "debian" 
> directory.

> 

> Changes since the patch queue above are:

> - one patch from Ubuntu, fixing the wl-asneeded linking order

> - std-version is 4.1.0

> - changelog updated.

> 

> Feel free to reschedule, defer, cancel if you think the packaging has issues.


Please cancel this upload, the updated dbusada package is almost ready

for upload. Sorry for the delay, but I was on holidays last week.


Regards,

- reto

Bug#874015: aptitude: forgets selection state for package downgrade

[Yann Dirson]

Package: aptitude
Version: 0.8.7-1
Severity: normal

Let's choose a package tha is a candidate for upgrade (previous testing
version is installed, and more recent than current stable version).

If I select it for upgrade to testing and quit aptitude, the selected
version is still selected when I launch aptitude again.

Now if I select it for downgrade and quit, then on next launch
not only the downgrading choice is lost, but the package is now selected
for *upgrade*.

Combine this with a bug like #874012, where for some reason it seems to reset
selections as if user had quit and relaunched, and a time-consuming
selection of packages while attempting to restore a broken situation
just gets frustratingly lost.

-- Package-specific info:
Terminal: screen
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.7
Compiler: g++ 6.3.0 20170406
Compiled against:
  apt version 5.0.1
  NCurses version 6.0
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20161126
  cwidget version: 0.5.17
  Apt version: 5.0.1

aptitude linkage:
linux-vdso.so.1 (0x7fff74bd9000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7f5ba304c000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7f5ba2e1c000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7f5ba2bf2000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f5ba29eb000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7f5ba26f)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f5ba23e3000)
libboost_iostreams.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7f5ba21cb000)
libboost_filesystem.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7f5ba1fb2000)
libboost_system.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7f5ba1dae000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f5ba199a000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f5ba177d000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f5ba13fa000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f5ba10f6000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f5ba0edf000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f5ba0b4)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f5ba093c000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f5ba0725000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f5ba0509000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f5ba02f9000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f5ba00d3000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f5b9fec1000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f5b9fcb9000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f5b9fab2000)
/lib64/ld-linux-x86-64.so.2 (0x55b6671f1000)

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

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

Versions of packages aptitude depends on:
ii  aptitude-common0.8.7-1
ii  libapt-pkg5.0  1.4.7
ii  libboost-filesystem1.62.0  1.62.0+dfsg-4
ii  libboost-iostreams1.62.0   1.62.0+dfsg-4
ii  libboost-system1.62.0  1.62.0+dfsg-4
ii  libc6  2.24-11+deb9u1
ii  libcwidget3v5  0.5.17-6
ii  libgcc11:7.1.0-10
ii  libncursesw5   6.0+20161126-1
ii  libsigc++-2.0-0v5  2.10.0-1
ii  libsqlite3-0   3.19.3-3
ii  libstdc++6 7.1.0-10
ii  libtinfo5  6.0+20161126-1
ii  libxapian301.4.4-2

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-12
ii  sensible-utils 0.0.9

Versions of packages aptitude suggests:
ii  apt-xapian-index0.49
pn  aptitude-doc-en | aptitude-doc  
ii  debtags 2.1.2
ii  tasksel 3.39

-- no debconf information

Bug#874014: base-installer: Please use common kernel for all subarchitectures on m68k

[John Paul Adrian Glaubitz]

Source: base-installer
Version: 1.171
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: m68k

Hello!

base-installer currently fails to find a suitable kernel on any
m68k system during install because it tries to install different
kernels depending on the subarchitecture.

Since we have just a common kernel for m68k these days, this
mechanism no longer works and the kernel installation fails.

With the attached patch, the kernel/m68k.sh script has been modified
to use a common kernel on m68k. The corresponding test in kernel/tests/
m68k has been updated as well.

Please consider applying the patch for the next upload.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>From 1e8a67960b0a64f75a13a91159c8483fcc8dd144 Mon Sep 17 00:00:00 2001
From: John Paul Adrian Glaubitz 
Date: Sat, 2 Sep 2017 00:13:40 +0200
Subject: [PATCH] m68k: Use common kernel for all subarchitectures

Signed-off-by: John Paul Adrian Glaubitz 
---
 kernel/m68k.sh   | 29 +++--
 kernel/tests/m68k/crest.test | 17 +
 2 files changed, 16 insertions(+), 30 deletions(-)

diff --git a/kernel/m68k.sh b/kernel/m68k.sh
index f9403612..c42eafa3 100644
--- a/kernel/m68k.sh
+++ b/kernel/m68k.sh
@@ -1,29 +1,22 @@
 arch_get_kernel_flavour () {
-   case "$SUBARCH" in
-   amiga|atari|mac|bvme6000|mvme147|mvme16x|q40|sun3|sun3x)
-   echo "$SUBARCH"
+   echo m68k
+}
+
+arch_check_usable_kernel () {
+   case "$1" in
+   *-dbg)
+   return 1
+   ;;
+   *-m68k | *-m68k-*)
+   # Allow any other hyphenated suffix
return 0
;;
*)
-   warning "Unknown $ARCH subarchitecture '$SUBARCH'."
return 1
;;
esac
 }
 
-arch_check_usable_kernel () {
-   # Subarchitecture must match exactly
-   if echo "$1" | grep -Eq -- "-$2(-.*)?$"; then return 0; fi
-   return 1
-}
-
 arch_get_kernel () {
-   case "$KERNEL_MAJOR" in
-   2.6|3.*|4.*)
-   echo "linux-image-$1"
-   ;;
-   *)
-   warning "Unsupported kernel major '$KERNEL_MAJOR'."
-   ;;
-   esac
+   echo "linux-image-m68k"
 }
diff --git a/kernel/tests/m68k/crest.test b/kernel/tests/m68k/crest.test
index ad4dfd0b..1383e497 100644
--- a/kernel/tests/m68k/crest.test
+++ b/kernel/tests/m68k/crest.test
@@ -1,16 +1,9 @@
-subarch amiga
 cpuinfo crest.cpuinfo
 majors 2.6
-flavour amiga
-kernel-2.6 linux-image-amiga
+flavour m68k
+kernel-2.6 \
+  linux-image-m68k
 usable \
-  linux-image-amiga
+  linux-image-m68k
 unusable \
-  linux-image-atari \
-  linux-image-bvme6000 \
-  linux-image-hp \
-  linux-image-mac \
-  linux-image-mvme147 \
-  linux-image-mvme16x \
-  linux-image-q40 \
-  linux-image-sun3
+  linux-image-m68k-dbg
-- 
2.14.1

Bug#871956: lintian: false positive: binary-file-built-without-LFS-support on x32

[Boud Roukema]

On Fri, 1 Sep 2017, Adam Borowski wrote:


And what AC_SYS_LARGEFILE does, at least on Linux, is to return a hardcoded
setting so programs switch from off_t to off64_t whether they need to or
not.  This does the right thing on old 32-bit archs and is harmless on
64-bit and new 32-bit.


AC_SYS_LARGEFILE on i386 (linux) for mpgrafic-0.3.15-1 apparently does *not*
always do the right thing:

https://lintian.debian.org/resources/e617c1e7ba35e94b411994e8320643594559faf6920ef535c71c911eb32657fd.gz


N: Processing source package mpgrafic (version 0.3.15-1, arch source) ...
C: mpgrafic source (0.3.15-1) [source]: debian-build-system dh
C: mpgrafic source (0.3.15-1) [source]: source-format 3.0 (quilt)
P: mpgrafic source (0.3.15-1) [source]: debian-watch-may-check-gpg-signature
N: 
N: Processing binary package mpgrafic (version 0.3.15-1, arch i386) ...
X: mpgrafic binary (0.3.15-1) [i386]: binary-file-built-without-LFS-support 
usr/bin/mpgrafic
C: mpgrafic binary (0.3.15-1) [i386]: no-ctrl-scripts
N: 
N: Processing binary package mpgrafic (version 0.3.15-1, arch amd64) ...
C: mpgrafic binary (0.3.15-1) [amd64]: no-ctrl-scripts
N: 
N: Processing binary package mpgrafic-dbgsym (version 0.3.15-1, arch i386) ...
C: mpgrafic-dbgsym binary (0.3.15-1) [i386]: no-ctrl-scripts
N: 
N: Processing binary package mpgrafic-dbgsym (version 0.3.15-1, arch amd64) ...


https://anonscm.debian.org/git/debian-astro/packages/mpgrafic.git/tree/configure.ac

https://anonscm.debian.org/git/debian-astro/packages/mpgrafic.git/tree/configure

This is a lintian false positive with AC_SYS_LARGEFILE.

Bug#874013: libgl1-mesa-glx: transitional library package should not be Arch: all

[Simon McVittie]

Package: libgl1-mesa-glx
Version: 17.2.0~rc6-1
Severity: important

The libgl1-mesa-glx transitional package that exists after the libglvnd
transition is Architecture: all, but this is not appropriate when a
foreign-architecture package like Steam might depend on it. On an
amd64 system:

* steam:i386 Depends libgl1-mesa-glx (interpreted as :i386)
* Desired result: installing steam:i386 pulls libgl1-mesa-glx:i386
* Actual result: libgl1-mesa-glx (Arch: all) is considered to be
  part of the primary architecture amd64 and cannot satisfy
  steam's dependency, because it is not Multi-Arch: foreign

It would not be a correct solution to mark libgl1-mesa-glx:all as
M-A: foreign, because if it was, this dependency chain would be
considered to be valid:

steam:i386 -> libgl1-mesa-glx:all -> libgl1:amd64 -> libglx0:amd64 -> 
libglx-mesa0:amd64

and that is clearly not useful, because the i386 binaries in Steam cannot
load an amd64 libGL. The "i386ness" needs to be propagated all the way
through the dependency chain.

I think libgl1-mesa-glx needs to go back to being Architecture: any.
In general, transitional packages for shared libraries and other
architecture-dependent bits should themselves be architecture-dependent -
the wasted space on mirrors for having a copy of the same content per
architecture is small, because transitional packages are small.

libgl1-mesa-glx should perhaps also get a Depends on libglx-mesa0?
At the moment there is no guarantee that a system with the transitional
libgl1-mesa-glx will actually have Mesa's libglx - if the proprietary
drivers follow what Mesa has done, then the dependency chain could equally
well be satisfied by

libgl1-mesa-glx -> libgl1 -> libglx0 -> libglx-nvidia0

which seems rather unexpected! It would seem more reasonable for
installing libgl1-mesa-glx to pull in a complete Mesa stack equivalent
to what used to be in libgl1-mesa-glx.

All the same reasoning probably applies to libegl1-mesa, although I
don't really know how EGL works.

Regards,
S

Bug#873822: RFS: achilles/2-9 [QA]

[Tobias Frost]

Am Freitag, den 01.09.2017, 21:14 +0100 schrieb David William Richmond
Davies-Jones:
> Hello
> 
> I have fixed the problems with the copyright file, deleted the stray
> file, and fixed the lintian warnings about encoding in desktop file
> and
> description started with synopsis.

OK

> I also *think* that I've got everything sorted with autoreconf etc,
> but
> to be honest I always seem to have trouble and get confused with
> them.

With compat level 10 dh-autoreconf is default -> you do not need B-D on
it or autotools-dev anymore. That should fix the warning :)

Fix this and reupload... Then we're ready, I guess!

Thanks for the package!

--
tobi


> David
> 
> On 31/08/17 22:17, Tobias Frost wrote:
> > Control: owner -1 !
> > Control: tags -1 moreinfo
> > 
> > Hallo David,
> > 
> > The package is already in a nice state; many thanks for updating
> > it!
> > 
> > However some fixes are required:
> > 
> > - d/copyright needs fixing:
> >   - as it says "Copyright: ?"... I think it must be 
> > Copyright: 2000 Matthew Danish 
> >   - Also the License is GPL-2+
> >   - The license grant is not copied verbatimly 
> > 
> > - d/manpage is a stray file.
> > 
> > - Please (try to) fix those linitan warnings or evaluate if they
> > are
> > valid:
> > 
> > W: achilles source: useless-autoreconf-build-depends autotools-dev
> > I: achilles source: debian-watch-file-is-missing
> > I: achilles: hardening-no-bindnow usr/bin/achilles
> > W: achilles: description-synopsis-starts-with-article
> > I: achilles: desktop-entry-contains-encoding-key
> > usr/share/applications/achilles.desktop:3 Encoding
> > I: achilles: desktop-entry-lacks-keywords-entry
> > usr/share/applications/achilles.desktop
> > 
> > 
> > --
> > tobi
> > 

Bug#873822: RFS: achilles/2-9 [QA]

[David William Richmond Davies-Jones]

I did do an upload where I dropped the build-dep, but it threw up a
warning about outdated config.{sub|guess}. Should I ignore this?

On 01/09/17 22:59, Tobias Frost wrote:
> Am Freitag, den 01.09.2017, 21:14 +0100 schrieb David William Richmond
> Davies-Jones:
>> Hello
>>
>> I have fixed the problems with the copyright file, deleted the stray
>> file, and fixed the lintian warnings about encoding in desktop file
>> and
>> description started with synopsis.
> 
> OK
> 
>> I also *think* that I've got everything sorted with autoreconf etc,
>> but
>> to be honest I always seem to have trouble and get confused with
>> them.
> 
> With compat level 10 dh-autoreconf is default -> you do not need B-D on
> it or autotools-dev anymore. That should fix the warning :)
> 
> Fix this and reupload... Then we're ready, I guess!
> 
> Thanks for the package!
> 
> --
> tobi
> 
> 
>> David
>>
>> On 31/08/17 22:17, Tobias Frost wrote:
>>> Control: owner -1 !
>>> Control: tags -1 moreinfo
>>>
>>> Hallo David,
>>>
>>> The package is already in a nice state; many thanks for updating
>>> it!
>>>
>>> However some fixes are required:
>>>
>>> - d/copyright needs fixing:
>>>   - as it says "Copyright: ?"... I think it must be 
>>> Copyright: 2000 Matthew Danish 
>>>   - Also the License is GPL-2+
>>>   - The license grant is not copied verbatimly 
>>>
>>> - d/manpage is a stray file.
>>>
>>> - Please (try to) fix those linitan warnings or evaluate if they
>>> are
>>> valid:
>>>
>>> W: achilles source: useless-autoreconf-build-depends autotools-dev
>>> I: achilles source: debian-watch-file-is-missing
>>> I: achilles: hardening-no-bindnow usr/bin/achilles
>>> W: achilles: description-synopsis-starts-with-article
>>> I: achilles: desktop-entry-contains-encoding-key
>>> usr/share/applications/achilles.desktop:3 Encoding
>>> I: achilles: desktop-entry-lacks-keywords-entry
>>> usr/share/applications/achilles.desktop
>>>
>>>
>>> --
>>> tobi
>>>

Bug#874012: aptitude: "Internal Error, No file name" on reinstall request

[Yann Dirson]

Package: aptitude
Version: 0.8.7-1
Severity: normal

texlive-htmlxml is in unconfigured state and postinst will not complete
without a reinstall (files got missing after downgrade due to Replaces
issue).  But aptitude would not reinstall it:

root@home:~# aptitude reinstall texlive-htmlxml
The following packages will be REINSTALLED:
  texlive-htmlxml
The following packages will be REMOVED:
  cpp-7{u} gnustep-base-common{u} gnustep-common{u} libasan4{u}
  libboost-test1.62.0{u} libboost-timer1.62.0{u}
The following partially installed packages will be configured:
  tex-common texlive texlive-extra-utils texlive-font-utils
  texlive-fonts-recommended texlive-games
  texlive-generic-recommended texlive-lang-french texlive-latex-base
  texlive-latex-extra
texlive-latex-recommended texlive-luatex texlive-metapost
texlive-pictures texlive-xetex
0 packages upgraded, 0 newly installed, 1 reinstalled, 6 to remove and 396 not 
upgraded.
Need to get 0 B of archives. After unpacking 158 MB will be freed.
Do you want to continue? [Y/n/?]
E: Internal Error, No file name for texlive-htmlxml:amd64

bundle file available if needed


-- Package-specific info:
Terminal: screen
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.7
Compiler: g++ 6.3.0 20170406
Compiled against:
  apt version 5.0.1
  NCurses version 6.0
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20161126
  cwidget version: 0.5.17
  Apt version: 5.0.1

aptitude linkage:
linux-vdso.so.1 (0x7ffde3bc6000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7f51b48c2000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7f51b4692000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7f51b4468000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f51b4261000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7f51b3f66000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f51b3c59000)
libboost_iostreams.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7f51b3a41000)
libboost_filesystem.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7f51b3828000)
libboost_system.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7f51b3624000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f51b321)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f51b2ff3000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f51b2c7)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f51b296c000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f51b2755000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f51b23b6000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f51b21b2000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f51b1f9b000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f51b1d7f000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f51b1b6f000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f51b1949000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f51b1737000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f51b152f000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f51b1328000)
/lib64/ld-linux-x86-64.so.2 (0x55ba2253f000)

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

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

Versions of packages aptitude depends on:
ii  aptitude-common0.8.7-1
ii  libapt-pkg5.0  1.4.7
ii  libboost-filesystem1.62.0  1.62.0+dfsg-4
ii  libboost-iostreams1.62.0   1.62.0+dfsg-4
ii  libboost-system1.62.0  1.62.0+dfsg-4
ii  libc6  2.24-11+deb9u1
ii  libcwidget3v5  0.5.17-6
ii  libgcc11:7.1.0-10
ii  libncursesw5   6.0+20161126-1
ii  libsigc++-2.0-0v5  2.10.0-1
ii  libsqlite3-0   3.19.3-3
ii  libstdc++6 7.1.0-10
ii  libtinfo5  6.0+20161126-1
ii  libxapian301.4.4-2

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-12
ii  

Bug#861937: preload fails due to missing preload.state file

[Chris Lamb]

severity 861937 serious
thanks

  $ sudo apt install preload
  […]

  $ sudo tail -f /var/log/preload.log
  [Fri Sep  1 22:41:49 2017] loading conf from /etc/preload.conf
  [Fri Sep  1 22:41:49 2017] loading state from /var/lib/preload/preload.state
  [Fri Sep  1 22:41:49 2017] cannot open /var/lib/preload/preload.state for 
reading, ignoring: No such file or directory

.. makes the package pretty much unusable so raising severity :)


Regards,

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

Bug#874011: ITP: core-moos -- Mission Oriented Operating Suite

[Kyle Fazzari]

Package: wnpp
Severity: wishlist
Owner: Kyle Fazzari 

* Package name: core-moos
  Version : 10.0.2.a
  Upstream Author : Paul Michael Newman 
* URL : 
http://www.robots.ox.ac.uk/~mobile/MOOS/wiki/pmwiki.php/Main/HomePage
* License : GPL-2+
  Programming Lang: C++
  Description : Mission Oriented Operating Suite

Light, fast, cross-platform middleware for robotics. CoreMOOS is the most
fundamental layer, providing a very robust network based communications
architecture (two libraries and a lightweight communications hub called
MOOSDB) which for very little effort lets you build applications which
communicate with each other.

This software is often used in marine robotics, but users typically run
from source. This is an attempt to rectify that situation, at least for
Debian-based distributions. I'm planning on maintaining it, although
co-maintainers would not be turned down. I have a sponsor.

Bug#874000: Acknowledgement (sudo -A does not run the command)

[Samuel Hym]

I forgot to mention that reverting to the version in testing, 
1.8.20p2-1, solves the problem.

Bug#820904: ssh-askpass: cannot control position of ssh-askpass window

[Philip Hands]

Tony Finch  writes:

> Package: ssh-askpass
> Version: 1:1.2.4.1-9
> Severity: wishlist
> Tags: upstream patch
>
> Dear Philip,
>
> I am using i3-wm with two monitors and Xrandr.
>
> In this setup, ssh-askpass plonks itself over the crack between the screens.
> It doesn't have any facility to control where it places itself.

Sorry for the tardy response -- dealing with ssh-askpass bugs has been
bobbing just below the point where I get round to it on my TODO list for
far too long.

Anyway, since I'm now preparing a release, I looked at this, and it
occurs to me that it might be more useful to be able to specify the
position on the screen as e.g. a percentage of the width/height.

Currently it goes for the middle of the X axis, and one third from the
top on the Y.  We could therefore have resources xPercent and yPercent
that default to 50 and 33 respectively to attain the same effect (bar
rounding) and for your 2 screen setup you could set yPercent to 25, say,
to get it in the middle of one screen.

Would that work for you?

That strikes me as better than using an absolute position, but perhaps
there is something I'm not considering.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#869926: RFS: oprofile/1.2.0-1 [ITP]

[Roberto Oliveira]

Hi Andrey,


On Thu, 31 Aug 2017 22:52:12 +0500 Andrey Rahmatullin  wrote:
> Please upgrade to the current Standards-Version.
Fixed.

> Why do you use "rm `find . -name "*.la"`" instead of "find . -name "*.la" 
> -delete"?
Fixed

> Why do you ship static versions of the plugins?
Fixed. Don't need them, just need the .so files

> README_PACKAGERS says "It is recommended to run ldconfig in %post and
> %postun to add/remove the /oprofile path from the standard library
> search paths.", have you checked the plugins work without adding that to
> the search paths?
Fixed. I created a file in /etc/ld.so.conf.d/ so operf with JITed code
works doing
something like:
$ operf java -Xcomp -agentlib:jvmti_oprofile Hello

I also did the changes in packages, as we talked in IRC, providing 4 packages:
oprofile, oprofile-jit, libopagent1 and libopagent-dev

> include/sstream should be documented in debian/copyright.
Fixed

> doc/*.html should ideally be rebuilt during the build process, you can
> probably achieve that by adding them to debian/clean and checking that
> they are built properly.
Fixed. I added debian/clean file

>
> --
> WBR, wRAR

Bug#873929: gcc7: Enable libgo tests and rebuilds with make -C

[Svante Signell]

On Fri, 2017-09-01 at 13:32 +0200, Matthias Klose wrote:
> On 01.09.2017 11:55, Svante Signell wrote:
> > Source: gcc-7
> > Version: 7.2.0-2
> > Severity: important
> > Tags: patch
> > 
> > Hello,
> > 
> > Currently the libgo tests are not run due to a bug in
> > libgo/Makefile.am
> > (and Makefile.in). This error is found on all architectures where
> > the
> > testsuite is enabled. The attached patch fixes this bug as well as
> > enables rebuilds with
> > make -C build//libgo clean;
> > ;
> > make -C build//libgo;
> > by adding more entries to the CLEANFILES target.
> > 
> > (The GOBENCH = entry is due to a trailing white space in the
> > original
> > file)
> 
> ok, this is the libgo-testsuite.diff patch.  Why do you test
> USE_DEJAGNU twice then?

I just found out that the test suite does not run properly, and created
the patch making that Makefile snippet being the same as for gcc-6. The
if then else fi logic is broken:
See e.g. https://buildd.debian.org/status/fetch.php?pkg=gcc-7=amd6
4=7.2.0-2=1504127698=0

/usr/bin/make  check-DEJAGNU
make[9]: Entering directory '/<>/build/x86_64-linux-
gnu/32/libgo/testsuite'
srcdir='../../../../../src/libgo/testsuite'; export srcdir; \
EXPECT=`if [ -f ../../expect/expect ] ; then echo ../../expect/expect ;
else echo expect ; fi`; export EXPECT; \
runtest=`if [ -f ../../../../../src/libgo/../dejagnu/runtest ] ; then
echo ../../../../../src/libgo/../dejagnu/runtest ; else echo runtest;
fi`; \
if /bin/bash -c "$runtest --version" > /dev/null 2>&1; then \
  exit_status=0; l='libgo'; for tool in $l; do \
if $runtest "TEST_GCC_EXEC_PREFIX=/usr/lib/gcc" --tool $tool --
srcdir $srcdir --target_board=unix\{,-fstack-protector\}
GOTEST_TMPDIR=gotest21736/test; \
then :; else exit_status=1; fi; \
  done; \
else echo "WARNING: could not find \`runtest'" 1>&2; :;\
fi; \
exit $exit_status

for failed build logs.

> The go testsuite is special, because it's normally run from every
> multilib directory instead of the top libdir only.

Sorry, I don't (yet) know what you mean, but will in due time. Perhaps
with your help?

Bug#874010: libzip: CVE-2017-14107: memory allocation failure in _zip_cdir_grow (zip_dirent.c)

[Salvatore Bonaccorso]

Source: libzip
Version: 0.11.2-1.2
Severity: important
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for libzip.

CVE-2017-14107[0]:
| The _zip_read_eocd64 function in zip_open.c in libzip before 1.3.0
| mishandles EOCD records, which allows remote attackers to cause a
| denial of service (memory allocation failure in _zip_cdir_grow in
| zip_dirent.c) via a crafted ZIP archive.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14107
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14107
[1] 
https://blogs.gentoo.org/ago/2017/09/01/libzip-memory-allocation-failure-in-_zip_cdir_grow-zip_dirent-c/
[2] 
https://github.com/nih-at/libzip/commit/9b46957ec98d85a572e9ef98301247f39338a3b5

Regards,
Salvatore

Bug#874008: firejail: Steam doesn't start using upstream config

[Reiner Herrmann]

Hi Martin,

On Fri, Sep 01, 2017 at 10:43:59PM +0200, Martin Dosch wrote:
> Version: 0.9.48-2

[...]

> when I tried starting steam using the upstream profile I got following error:
> 
> > Error: line 32 in /home/martin/.config/firejail/steam.profile is invalid
> 
> After commenting the line 32 I got this:
> 
> > Error: line 36 in /home/martin/.config/firejail/steam.profile is invalid
> 
> So i also had to comment this. So for me steam started after commenting the
> following lines:
> 
> nodvd
> notv

nodvd and notv are new options in firejail 0.9.50-rc1 (which is
currently only available in experimental).

So unfortunately you can't use the current upstream steam profile
without upgrading firejail to at least .50-rc1.

Regards,
  Reiner


signature.asc
Description: PGP signature

Bug#873890: ansible: enabling systemd service fails in chroot

[Harlan Lieberman-Berg]

tag 873890 +pending +upstream +fixed-upstream
forwarded 873890 https://github.com/ansible/ansible/issues/21026
thanks

Thanks for the report!  I'll cherry pick this patch in tonight.

Bug#874009: rkt FTBFS: cannot find package "github.com/aws/aws-sdk-go/private/signer/v4"

[Adrian Bunk]

Source: rkt
Version: 1.21.0+dfsg-1
Severity: serious

Some recent change in unstable makes rkt FTBFS:

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

...
/usr/bin/make -C _build/src/github.com/coreos/rkt manpages 
GOPATH="/build/1st/rkt-1.21.0+dfsg"/_build/src2
make[2]: Entering directory 
'/build/1st/rkt-1.21.0+dfsg/_build/src/github.com/coreos/rkt'
mkdir -p dist/manpages/
ls 
/build/1st/rkt-1.21.0+dfsg/_build/src/github.com/coreos/rkt/build-rkt-1.21.0/gopath/src/github.com/coreos/rkt/rkt/*.go
 | \
grep -vE '_test.go|main.go|_gen.go|_stub.go' | \
GO15VENDOREXPERIMENT=1 GOARCH="amd64" CGO_ENABLED=1 CC="gcc" CXX="g++" 
GOPATH="/build/1st/rkt-1.21.0+dfsg/_build/src2" GOARCH=amd64 CC= xargs "go" run 
/build/1st/rkt-1.21.0+dfsg/_build/src/github.com/coreos/rkt/build-rkt-1.21.0/gopath/src/github.com/coreos/rkt/rkt/manpages_gen.go
../../../../src2/src/github.com/coreos/rkt/rkt/config/auth.go:25:2: cannot find 
package "github.com/aws/aws-sdk-go/private/signer/v4" in any of:

/build/1st/rkt-1.21.0+dfsg/_build/src2/src/github.com/coreos/rkt/vendor/github.com/aws/aws-sdk-go/private/signer/v4
 (vendor tree)
/usr/lib/go-1.8/src/github.com/aws/aws-sdk-go/private/signer/v4 (from 
$GOROOT)

/build/1st/rkt-1.21.0+dfsg/_build/src2/src/github.com/aws/aws-sdk-go/private/signer/v4
 (from $GOPATH)
rkt/rkt.mk:37: recipe for target 'manpages' failed
make[2]: *** [manpages] Error 123
make[2]: Leaving directory 
'/build/1st/rkt-1.21.0+dfsg/_build/src/github.com/coreos/rkt'
debian/rules:45: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2

Bug#779675: lintian: Add flag --list-tags that will list all tags Lintian knows about

[Chris Lamb]

tags 779675 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=63f08a23a545b54f75e3687413012b3c9806aa55


Stuart Prescott wrote:

> perhaps lintian-info -t could take a glob or regex

I tried this but I felt it made the argument too "magic" especially
as you can pass multiple tags. Also, escaping '*' etc. on the command-
line is always a little bit of a pain...


Regards,

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

Bug#873822: RFS: achilles/2-9 [QA]

[David William Richmond Davies-Jones]

Hello

I have fixed the problems with the copyright file, deleted the stray
file, and fixed the lintian warnings about encoding in desktop file and
description started with synopsis.

I also *think* that I've got everything sorted with autoreconf etc, but
to be honest I always seem to have trouble and get confused with them.

David

On 31/08/17 22:17, Tobias Frost wrote:
> Control: owner -1 !
> Control: tags -1 moreinfo
> 
> Hallo David,
> 
> The package is already in a nice state; many thanks for updating it!
> 
> However some fixes are required:
> 
> - d/copyright needs fixing:
>   - as it says "Copyright: ?"... I think it must be 
> Copyright: 2000 Matthew Danish 
>   - Also the License is GPL-2+
>   - The license grant is not copied verbatimly 
> 
> - d/manpage is a stray file.
> 
> - Please (try to) fix those linitan warnings or evaluate if they are
> valid:
> 
> W: achilles source: useless-autoreconf-build-depends autotools-dev
> I: achilles source: debian-watch-file-is-missing
> I: achilles: hardening-no-bindnow usr/bin/achilles
> W: achilles: description-synopsis-starts-with-article
> I: achilles: desktop-entry-contains-encoding-key
> usr/share/applications/achilles.desktop:3 Encoding
> I: achilles: desktop-entry-lacks-keywords-entry
> usr/share/applications/achilles.desktop
> 
> 
> --
> tobi
> 

Bug#874007: FTBFS with Java 9 due to -source/-target only (weird)

[Chris West]

Source: uima-addons
Version: 2.3.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.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

*** WEIRD ***

This is the only Maven-based package that hits this problem. I didn't
look why.

Build log sample:

[INFO] 
[INFO] Building UIMA Annotator: ConceptMapper 2.3.1
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
ConceptMapper ---
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
resources, i.e. build is platform dependent!
[INFO] Copying 0 resource
[INFO] 
[INFO] --- maven-dependency-plugin:2.8:copy-dependencies (copy dependencies to 
base-bin/lib) @ ConceptMapper ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:copy-resources (copy standard dirs and 
files to base-bin) @ ConceptMapper ---
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
resources, i.e. build is platform dependent!
[INFO] Copying 9 resources
[INFO] skip non existing resourceDirectory 
/build/uima-addons-2.3.1/ConceptMapper/src/main/readme
[INFO] 
[INFO] --- maven-compiler-plugin:3.6.1:compile (default-compile) @ 
ConceptMapper ---
[WARNING] The POM for org.codehaus.plexus:plexus-compiler-api:jar:2.x is 
invalid, transitive dependencies (if any) will not be available, enable debug 
logging for more details
[WARNING] The POM for org.codehaus.plexus:plexus-compiler-javac:jar:2.x is 
invalid, transitive dependencies (if any) will not be available, enable debug 
logging for more details
[INFO] Changes detected - recompiling the module!
[WARNING] File encoding has not been set, using platform encoding 
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] Compiling 23 source files to 
/build/uima-addons-2.3.1/ConceptMapper/target/classes
Use of target 1.5 is no longer supported, switching to 1.7
Use of source 1.5 is no longer supported, switching to 1.7
[INFO] 
/build/uima-addons-2.3.1/ConceptMapper/src/main/java/org/apache/uima/conceptMapper/support/tokens/TokenNormalizer.java:
 Some input files use or override a deprecated API.
[INFO] 
/build/uima-addons-2.3.1/ConceptMapper/src/main/java/org/apache/uima/conceptMapper/support/tokens/TokenNormalizer.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) @ 
ConceptMapper ---
[INFO] Not copying test resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.6.1:testCompile (default-testCompile) @ 
ConceptMapper ---
[INFO] Not compiling test sources
[INFO] 
[INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ ConceptMapper ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:3.0.2:jar (default-jar) @ ConceptMapper ---
[INFO] Building jar: 
/build/uima-addons-2.3.1/ConceptMapper/target/uima-an-conceptMapper.jar
[INFO] 
[INFO] 
[INFO] Building UIMA Annotator: DictionaryAnnotator 2.3.1
[INFO] 
[INFO] 
[INFO] --- xmlbeans-maven-plugin:2.3.3:xmlbeans (default) @ DictionaryAnnotator 
---
warning: [options] bootstrap class path not set in conjunction with -source 1.4
error: Source option 1.4 is no longer supported. Use 1.6 or later.
error: Target option 1.4 is no longer supported. Use 1.6 or later.

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] UIMA-AddOns: uima-addons-parent  SUCCESS [  0.002 s]
[INFO] UIMA Annotator: ConceptMapper .. SUCCESS [  5.152 s]
[INFO] UIMA Annotator: DictionaryAnnotator  FAILURE [  1.637 s]
[INFO] UIMA Addon: FsVariables  SKIPPED
[INFO] UIMA Addon: PearPackagingAntTask ... SKIPPED
[INFO] UIMA Annotator: RegularExpressionAnnotator . SKIPPED
[INFO] UIMA Addon: SimpleServer ... SKIPPED
[INFO] UIMA Annotator: SnowballAnnotator .. SKIPPED
[INFO] UIMA Annotator: WhitespaceTokenizer  SKIPPED
[INFO] UIMA Annotator: Tagger . SKIPPED
[INFO] UIMA Aggregate: uima-addons  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 

Bug#874008: firejail: Steam doesn't start using upstream config

[Martin Dosch]

Package: firejail
Version: 0.9.48-2
Severity: normal

Dear Reiner,

when I tried starting steam using the upstream profile I got following error:

> Error: line 32 in /home/martin/.config/firejail/steam.profile is invalid

After commenting the line 32 I got this:

> Error: line 36 in /home/martin/.config/firejail/steam.profile is invalid

So i also had to comment this. So for me steam started after commenting the
following lines:

nodvd
notv


There was a steam update recently but I don't think this is changed behavior by
steam as it seems firejail is reporting an syntax error.
Also I'm not aware of any update of firejail in steam recently.

Feel free to ask if I might provide any useful information.

Best regards,
Martin



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages firejail depends on:
ii  libapparmor1  2.11.0-10
ii  libc6 2.24-14

Versions of packages firejail recommends:
ii  firejail-profiles  0.9.48-2
ii  iptables   1.6.1-2
ii  xauth  1:1.0.9-1+b2
ii  xserver-xephyr 2:1.19.3-2

firejail suggests no packages.

-- debconf-show failed

Bug#874006: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: salliere
Version: 0.10
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

echo "Implementation-Version: 0.10" >> SalliereManifest.txt
mkdir -p classes
/usr/lib/jvm/default-java/bin/javac -source 1.5 -Xlint:all -cp 
/usr/share/java/csv.jar:/usr/share/java/debug-disable.jar:/usr/share/java/itext.jar:/usr/share/java/commons-net.jar:classes
 -d classes cx/ath/matthew/salliere/AsciiTablePrinter.java 
cx/ath/matthew/sall...
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.
make[2]: *** [.classes] Error 2
Makefile:38: recipe for target '.classes' failed
make[2]: Leaving directory '/build/salliere-0.10'

Cheers,
Chris.

Bug#874005: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: pescetti
Version: 0.5
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

sed 's/\(.*\)/msgid "\1"\nmsgstr "\1"/' >> translations/en_GB.po
mkdir -p classes
/usr/lib/jvm/default-java/bin/javac -encoding utf8 -source 1.5 -Xlint:all -cp 
classes:/usr/share/java/debug-disable.jar:/usr/share/java/itext.jar:classes -d 
classes cx/ath/matthew/pescetti/Constants.java cx/ath/matthew/pesc...
...
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.
Makefile:33: recipe for target '.classes' failed
make[2]: *** [.classes] Error 2

Cheers,
Chris.

Bug#874003: nautilus: Nautilus does not launch applications

[Joe Rowan]

Package: nautilus
Version: 3.25.90-1
Severity: important

Dear Maintainer,

Nautilus is not launching applications when document files double-clicked or 
right-clicked and 'Open with ' selected. Other right-click actions work. 
When launching is attempted, either the window redraws with the double-clicked 
file as the top item, or a new window is opened, again with the target file at 
the top of the list.

I recall seeing Nautilus updated late last night, this problem has occurred 
since then. Nemo is behaving normally.

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

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

Versions of packages nautilus depends on:
ii  desktop-file-utils 0.23-2
ii  gsettings-desktop-schemas  3.24.0-2
ii  gvfs   1.30.4-1+b1
ii  libatk1.0-02.24.0-1
ii  libc6  2.24-17
ii  libcairo-gobject2  1.14.10-1
ii  libcairo2  1.14.10-1
ii  libexempi3 2.4.3-1
ii  libexif12  0.6.21-2+b2
ii  libgail-3-03.22.19-1
ii  libgdk-pixbuf2.0-0 2.36.5-4
ii  libglib2.0-0   2.53.6-1
ii  libglib2.0-data2.53.6-1
ii  libgnome-autoar-0-00.2.2-1
ii  libgnome-desktop-3-12  3.25.91.1-1
ii  libgtk-3-0 3.22.19-1
ii  libnautilus-extension1a3.25.90-1
ii  libpango-1.0-0 1.40.11-1
ii  libpangocairo-1.0-01.40.11-1
ii  libselinux12.6-3+b2
ii  libtracker-sparql-1.0-01.12.1-1
ii  libx11-6   2:1.6.4-3
ii  nautilus-data  3.25.90-1
ii  shared-mime-info   1.8-1

Versions of packages nautilus recommends:
pn  gnome-sushi  
ii  gvfs-backends1.30.4-1+b1
ii  librsvg2-common  2.40.18-1

Versions of packages nautilus suggests:
ii  brasero   3.12.1-4
ii  eog   3.25.90-1
ii  evince [pdf-viewer]   3.24.1-1
ii  mpg321 [mp3-decoder]  0.3.2-1.1
ii  nautilus-sendto   3.8.6-1
ii  okular [pdf-viewer]   4:16.08.2-1+b1
pn  tracker   
ii  vlc [mp3-decoder] 1:2.2.6-dmo6
ii  xdg-user-dirs 0.15-3
ii  xpdf [pdf-viewer] 3.04-4+b1

-- no debconf information

Bug#874004: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: ssvnc
Version: 1.0.29
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[2]: Entering directory '/build/ssvnc-1.0.29/ultraftp'
javac -target 1.4 -source 1.4 AuthPanel.java ButtonPanel.java 
ClipboardFrame.java DH.java DesCipher.java FTPFrame.java OptionsFrame.java 
RecordingFrame.java RfbProto.java SSLSocketToMe.java SessionRecorder.java 
VncCanvas.java VncViewer.java
warning: [options] bootstrap class path not set in conjunction with -source 1.4
error: Source option 1.4 is no longer supported. Use 1.6 or later.
error: Target option 1.4 is no longer supported. Use 1.6 or later.
Makefile:11: recipe for target 'AuthPanel.class' failed
make[2]: *** [AuthPanel.class] Error 2
make[2]: Leaving directory '/build/ssvnc-1.0.29/ultraftp'

Cheers,
Chris.

Bug#874001: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: sonic
Version: 0.2.0
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/sonic-0.2.0'
[ -L sonic ] || ln -s . sonic
javac -source 1.5 -target 1.5 Sonic.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.
debian/rules:17: recipe for target 'sonic/Sonic.class' failed
make[1]: Leaving directory '/build/sonic-0.2.0'


Cheers,
Chris.

Bug#874000: sudo -A does not run the command

[Samuel Hym]

Package: sudo
Version: 1.8.21-1
Severity: normal

Dear Maintainer,

When using the option -A, sudo does not run the command after 
prompting for the password.

I tried the following:

$ export SUDO_ASKPASS=/usr/bin/ssh-askpass
$ sudo -A echo a
$

where I get the last prompt after correctly entering the password in 
ssh-askpass.
If I enter a wrong password, it correctly displays an error message 
and asks again for the password.

Weirder, I get:

$ export SUDO_ASKPASS=/usr/bin/ssh-askpass
$ sudo -A echo a
$ sudo -A echo a
a

where the second run doesn’t need the password, since it was entered 
the first time… So I can work-around the bug adding a dummy
sudo -A echo > /dev/null
before the useful sudo.

Best regards,
Samuel


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

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

Versions of packages sudo depends on:
ii  libaudit1   1:2.7.7-1+b2
ii  libc6   2.24-17
ii  libpam-modules  1.1.8-3.6
ii  libpam0g1.1.8-3.6
ii  libselinux1 2.6-3+b2
ii  lsb-base9.20170808

sudo recommends no packages.

sudo suggests no packages.

-- Configuration Files:
/etc/sudoers [Errno 13] Permiso denegado: '/etc/sudoers'
/etc/sudoers.d/README [Errno 13] Permiso denegado: '/etc/sudoers.d/README'

-- no debconf information

Bug#874002: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: sacjava
Version: 1.3+dfsg
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/sacjava-1.3+dfsg'
/usr/lib/jvm/default-java/bin/javac -source 1.5 -target 1.5 `find org -name 
"*.java" | xargs`
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.
debian/rules:9: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2

Cheers,
Chris.

Bug#873998: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: plplot
Version: 5.10.0+dfsg2
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

cmake /build/plplot-5.10.0+dfsg2 -DBUILD_TE ...  -DJAVACFLAGS="-source 1.5 
-target 1.5" )

...

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]: *** [bindings/java/plplot/core/config.class] Error 2

Cheers,
Chris.

Bug#873996: [Pkg-octave-devel] Bug#873996: FTBFS with Java 9 due to -source/-target only

[Mike Miller]

On Fri, Sep 01, 2017 at 21:05:45 +0100, Chris West wrote:
> This package fails to build with default-jdk pointing to openjdk-9-jdk.

If/when this needs to be patched in unstable, here is the upstream fix
that can be cherry-picked:

https://hg.savannah.gnu.org/hgweb/octave/rev/20c83f619102

-- 
mike


signature.asc
Description: PGP signature

Bug#873999: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: rxtx
Version: 2.2pre2
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[2]: Entering directory '/build/rxtx-2.2pre2'
/usr/lib/jvm/java-9-openjdk-amd64/bin/javac -classpath 
.:/build/rxtx-2.2pre2:/build/rxtx-2.2pre2/src: -d /build/rxtx-2.2pre2/ -O 
-source 1.3 -target 1.3 
/build/rxtx-2.2pre2/./src/gnu/io/UnsupportedCommOperationException.java 
/build/r...
warning: [options] bootstrap class path not set in conjunction with -source 1.3
error: Source option 1.3 is no longer supported. Use 1.6 or later.
error: Target option 1.3 is no longer supported. Use 1.6 or later.
Makefile:832: recipe for target 
'/build/rxtx-2.2pre2/gnu/io/UnsupportedCommOperationException.class' failed
make[2]: Leaving directory '/build/rxtx-2.2pre2'

Cheers,
Chris.

Bug#873997: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: openjpeg2
Version: 2.1.2
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample (messed up due to make -j):

make[3]: Entering directory '/build/openjpeg2-2.1.2/obj-x86_64-linux-gnu'
[  1%] javac *.java; jar cvf -> opj_viewer_xerces.jar
cd /build/openjpeg2-2.1.2/obj-x86_64-linux-gnu/src/bin/jpip && /usr/bin/javac 
-source 1.5 -target 1.5 -classpath /usr/share/java/xercesImpl.jar 
/build/openjpeg2-2.1.2/src/bin/jpip/opj_viewer_xerces/src/ImageViewer.java 
/bui...

...

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]: *** [bin/[...].jar] Error 2

Cheers,
Chris.

Bug#873996: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: octave
Version: 4.2.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.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample, a bit messed up due to parallel:

( cd ./scripts/java; "javac" -source 1.3 -target 1.3 -Xlint:-options -d 
/build/octave-4.2.1/scripts/java org/octave/OctaveReference.java )
error: Source option 1.3 is no longer supported. Use 1.6 or later.
error: Target option 1.3 is no longer supported. Use 1.6 or later.

...

Makefile:27394: recipe for target 
'scripts/java/org/octave/OctaveReference.class' failed
make[3]: *** [scripts/java/org/octave/OctaveReference.class] Error 2

...

make[3]: Leaving directory '/build/octave-4.2.1'
Makefile:26173: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1


Cheers,
Chris.

Bug#873995: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: nescc
Version: 1.3.5
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[7]: Entering directory 
'/build/nescc-1.3.5/tools/java/net/tinyos/nesc/wiring'
CLASSPATH=`cygpath -w ../../../.. 2>/dev/null || echo ../../../..` javac 
-source 1.5 -target 1.5 WiringCheck.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[7]: *** [WiringCheck.class] Error 2
Makefile:464: recipe for target 'WiringCheck.class' failed
make[7]: Leaving directory 
'/build/nescc-1.3.5/tools/java/net/tinyos/nesc/wiring'

Cheers,
Chris.

Bug#873994: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: neobio
Version: 0.0.20030929
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[1]: Entering directory '/build/neobio-0.0.20030929'
mkdir -p classes
javac -cp src -source 1.5 -target 1.5 -d  classes   src/neobio/gui/NeoBio.java 
src/neobio...
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.
debian/rules:15: recipe for target 'override_dh_auto_build' failed
make[1]: Leaving directory '/build/neobio-0.0.20030929'


Cheers,
Chris.

Bug#873993: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: munin
Version: 2.0.33
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

touch build-java-stamp
/usr/lib/jvm/default-java/bin/javac -sourcepath plugins/javalib -d 
build/plugins/javalib -g -source 1.5 -target 1.5 -Xlint 
plugins/javalib/org/munin/plugin/jmx/AbstractAnnotationGraphsProvider.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.
Makefile:50: recipe for target 
'plugins/javalib/org/munin/plugin/jmx/AbstractAnnotationGraphsProvider.class' 
failed
make[2]: *** 
[plugins/javalib/org/munin/plugin/jmx/AbstractAnnotationGraphsProvider.class] 
Error 2

Cheers,
Chris.

Bug#873992: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: libusb-java
Version: 0.8+ztex20090101
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[2]: Entering directory '/build/libusb-java-0.8+ztex20090101'
javac -source 1.5 -target 1.5 -encoding ISO-8859-1 ch/ntb/usb/Device.java 
ch/ntb/usb/LibLoader.java ch/ntb/usb/LibusbJava.java ch/ntb/usb/USB.java 
ch/ntb/usb/USBException.java ch/ntb/usb/USBTimeoutException.java 
ch/ntb/usb/Usb_Bus.java ch/ntb/usb/Usb_Config_Descriptor.java 
ch/ntb/usb/Usb_Descriptor.java ch/ntb/usb/Usb_Device.java 
ch/ntb/usb/Usb_Device_Descriptor.java ch/ntb/usb/Usb_Endpoint_Descriptor.java 
ch/ntb/usb/Usb_Interface.java ch/ntb/usb/Usb_Interface_Descriptor.java 
ch/ntb/usb/Utils.java ch/ntb/usb/logger/LogUtil.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.
Makefile:91: recipe for target 'classes.made' failed
make[2]: Leaving directory '/build/libusb-java-0.8+ztex20090101'
make[2]: *** [classes.made] Error 2

Cheers,
Chris.

Bug#873990: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: libmecab-java
Version: 0.99.6
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[1]: Entering directory '/build/libmecab-java-0.99.6'
dh_auto_build -- JAVAC="javac -source 1.5 -target 1.5 -encoding UTF-8" \
 INCLUDE=/usr/lib/jvm/default-java/include
make -j64 "JAVAC=javac -source 1.5 -target 1.5 -encoding UTF-8" 
INCLUDE=/usr/lib/jvm/default-java/include
make[2]: Entering directory '/build/libmecab-java-0.99.6'
c++ -O3 -c -fpic MeCab_wrap.cxx  `mecab-config --cflags` 
-I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux
c++ -shared  MeCab_wrap.o -o libMeCab.so `mecab-config --libs`
javac -source 1.5 -target 1.5 -encoding UTF-8 org/chasen/mecab/*.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.
Makefile:14: recipe for target 'all' failed
make[2]: *** [all] Error 2

Cheers,
Chris.

Bug#873989: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: libmatthew-java
Version: 0.8
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[3]: Entering directory '/build/libmatthew-java-0.8'
mkdir -p classes
cpp  -C -P -DDEBUGSETTING=false < cx/ath/matthew/debug/Debug.jpp > 
cx/ath/matthew/debug/Debug.java
/usr/lib/jvm/default-java/bin/javac -source 1.5  -cp classes -d classes 
cx/ath/matthew/debug/Debug.java cx/ath/matthew/utils/Hexdump.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.
make[3]: *** [.disabledebug] Error 2
make[2]: *** [.classes] Error 2
Makefile:107: recipe for target '.disabledebug' failed

Cheers,
Chris.

Bug#873991: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: libreadline-java
Version: 0.8.0.1+dfsg
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

mkdir ./build
cd src ; /usr/bin/make JAVAC="/usr/lib/jvm/default-java/bin/javac" 
JC_FLAGS="-source 1.4 -target 1.4" java
make[3]: Entering directory '/build/libreadline-java-0.8.0.1+dfsg/src'
/usr/lib/jvm/default-java/bin/javac -source 1.4 -target 1.4 -d ../build `find . 
-name "*.java"`
warning: [options] bootstrap class path not set in conjunction with -source 1.4
error: Source option 1.4 is no longer supported. Use 1.6 or later.
error: Target option 1.4 is no longer supported. Use 1.6 or later.
Makefile:9: recipe for target 'java' failed
make[3]: *** [java] Error 2


Cheers,
Chris.

Bug#873987: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: libisrt-java
Version: 4.8.20100629
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
   debian/rules override_jh_build
make[1]: Entering directory '/build/libisrt-java-4.8.20100629'
jh_build --javacopts="-source 1.5 -target 1.5" --javadoc-opts="-source 1.5"
find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.isrt -d 
debian/_jh_build.isrt -encoding ISO8859-1 -source 1.5 -target 1.5
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.
debian/rules:14: recipe for target 'override_jh_build' failed
make[1]: Leaving directory '/build/libisrt-java-4.8.20100629'

Cheers,
Chris.

Bug#873988: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: libjaxp1.3-java
Version: 1.3.05
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[1]: Entering directory '/build/libjaxp1.3-java-1.3.05'
mkdir -p build/license
/usr/lib/jvm/default-java/bin/javac -source 1.4 -d build `find javax org -name 
\*.java`
warning: [options] bootstrap class path not set in conjunction with -source 1.4
error: Source option 1.4 is no longer supported. Use 1.6 or later.
debian/rules:11: recipe for target 'override_dh_auto_build' failed
make[1]: Leaving directory '/build/libjaxp1.3-java-1.3.05'
make[1]: *** [override_dh_auto_build] Error 2

Cheers,
Chris.

Bug#860268: .desktop files can hide malware in Nautilus

[intrigeri]

Hi!

Micah Lee:
> The upstream nautilus issue [1] has already been resolved, and will be
> released in nautilus 3.24. But since this is an important security
> issue, I think this patch should be backported so that it's fixed in
> older versions of Debian.

Thanks for raising this issue in Debian!

Is there any plan upstream to backport this fix to their 3.22.x
branch, and/or to request a CVE?

Did you personally check whether it's straightforward to backport the
fix to 3.22?

Cheers,
-- 
intrigeri

Bug#873986: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: junit
Version: 3.8.2
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[1]: Entering directory '/build/junit-3.8.2'
mkdir -p classes
(cd src;/usr/lib/jvm/default-java/bin/javac -source 1.4 -target 1.4 -classpath 
. -d ../classes junit/*/*.java)
warning: [options] bootstrap class path not set in conjunction with -source 1.4
error: Source option 1.4 is no longer supported. Use 1.6 or later.
error: Target option 1.4 is no longer supported. Use 1.6 or later.
debian/rules:23: recipe for target 'override_dh_auto_build' failed
make[1]: Leaving directory '/build/junit-3.8.2'
make[1]: *** [override_dh_auto_build] Error 2

Cheers,
Chris.

Bug#873985: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: jtb
Version: 1.4.4
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
   debian/rules override_jh_build
make[1]: Entering directory '/build/jtb-1.4.4'
jh_build --javacopts="-source 1.5 -target 1.5" --javadoc-opts="-source 1.5"
find EDU -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.jtb -d 
debian/_jh_build.jtb -encoding ISO8859-1 -source 1.5 -target 1.5
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.
debian/rules:12: recipe for target 'override_jh_build' failed
make[1]: *** [override_jh_build] Error 123
make[1]: Leaving directory '/build/jtb-1.4.4'

Cheers,
Chris.

Bug#873983: ITP: nanook -- pre- and post-alignment analysis of nanopore sequencing data

[Andreas Tille]

Package: wnpp
Severity: wishlist
Owner: Andreas Tille 

* Package name: nanook
  Version : 1.26+dfsg-1
  Upstream Author : Richard M. Leggett 
* URL : https://documentation.tgac.ac.uk/display/NANOOK/NanoOK
* License : GPL
  Programming Lang: Java
  Description : pre- and post-alignment analysis of nanopore sequencing data
 NanoOK is a flexible, multi-reference software for pre- and post-
 alignment analysis of nanopore sequencing data, quality and error
 profiles.
 .
 NanoOK (pronounced na-nook) is a tool for extraction, alignment and
 analysis of Nanopore reads. NanoOK will extract reads as FASTA or FASTQ
 files, align them (with a choice of alignment tools), then generate a
 comprehensive multi-page PDF report containing yield, accuracy and
 quality analysis. Along the way, it generates plain text files which can
 be used for further analysis, as well as graphs suitable for inclusion
 in presentations and papers.


Remark: This package will be maintained by the Debian Med team at
   https://anonscm.debian.org/git/debian-med/nanook.git

Bug#873984: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: jnlp-servlet
Version: 20120126
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[1]: Entering directory '/build/jnlp-servlet-20120126'
rm -rf classes
rm -rf lib  
mkdir -p classes
mkdir -p lib
/usr/lib/jvm/default-java/bin/javac -source 1.5 -target 1.5 -classpath 
"/usr/lib/jvm/default-java/lib/javaws.jar:/usr/share/java/servlet-api-3.1.jar:src/classes"
 -d classes src/classes/jnlp/sample/jardiff/JarDiffConstants.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.
GNUmakefile:50: recipe for target 
'classes/jnlp/sample/jardiff/JarDiffConstants.class' failed
make[1]: *** [classes/jnlp/sample/jardiff/JarDiffConstants.class] Error 2
make[1]: Leaving directory '/build/jnlp-servlet-20120126'

Cheers,
Chris.

Bug#873981: [xpad] ** (xpad:776): WARNING **: There is a problem in the program Xpad. In function 'xpad_pad_toolbar_size_allocate' the variable 'event->height' is not a positive number.

[P. van Loo]

Package: xpad
Version: 4.8.0-1
Severity: normal

--- Please enter the report below this line. ---


--- System information. ---
Architecture: 
Kernel:   Linux 4.9.0-3-686-pae

Debian Release: 9.1
  500 stable  security.debian.org 
  500 stable  ftp.us.debian.org 
  500 oldstable   ftp.us.debian.org 
  100 stretch-backports ftp.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-=
libatk1.0-0 (>= 1.12.4) | 2.22.0-1
libc6 (>= 2.15) | 2.24-11+deb9u1
libcairo-gobject2   (>= 1.10.0) | 1.14.8-1
libcairo2(>= 1.2.4) | 1.14.8-1
libgdk-pixbuf2.0-0  (>= 2.22.0) | 2.36.5-2
libglib2.0-0(>= 2.41.1) | 2.50.3-2
libgtk-3-0  (>= 3.11.5) | 3.22.11-1
libgtksourceview-3.0-1(>= 3.10) | 3.22.2-1
libice6(>= 1:1.0.0) | 2:1.0.9-2
libpango-1.0-0  (>= 1.14.0) | 1.40.5-1
libpangocairo-1.0-0 (>= 1.14.0) | 1.40.5-1
libsm6  | 2:1.2.2-1+b3


Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#873982: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: jlapack
Version: 0.8~dfsg
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

javac -source 1.4 -target 1.4 -classpath 
.:blas.jar:simple:../../src/util/f2jutil.jar:../../src/error_reporting/xerbla.jar
 simple/org/netlib/blas/*.java
warning: [options] bootstrap class path not set in conjunction with -source 1.4
error: Source option 1.4 is no longer supported. Use 1.6 or later.
error: Target option 1.4 is no longer supported. Use 1.6 or later.
Makefile:9: recipe for target 'blas.jar' failed
make[4]: [blas.jar] Error 2 (ignored)

Cheers,
Chris.

Bug#873980: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: isorelax
Version: 2004
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/isorelax-2004'
javac -classpath /usr/share/java/ant.jar -source 1.5 -target 1.5 `find jp org 
-name \*.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.
debian/rules:24: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/isorelax-2004'

Cheers,
Chris.

Bug#873979: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: f2j
Version: 0.8.1+dfsg
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[2]: Entering directory '/build/f2j-0.8.1+dfsg/util'
mkdir -p obj
/usr/bin/javac -source 1.5 -target 1.5 -d obj org/j_paine/formatter/*.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.
Makefile:11: recipe for target 'f2jutil.jar' failed
make[2]: Leaving directory '/build/f2j-0.8.1+dfsg/util'

Cheers,
Chris.

Bug#873978: sendmail-base: Please check for /usr/share/sendmail/dynamic before sourcing it

[Sebastian Andrzej Siewior]

Package: sendmail-base
Version: 8.15.2-8
Severity: serious

I had sendmail installed. Then I removed it including sendmail-base. I
used "apt-get remove" instead of "purge" and this did not end well. The
log was quickly filled with this:

|Sep  1 21:28:02 debbuildd dhclient[3221]: DHCPREQUEST of 172.123.10.83 on eth0 
to 255.255.255.255 port 67
|Sep  1 21:28:02 debbuildd dhclient[3221]: DHCPOFFER of 172.123.10.83 from 
172.123.10.1
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPACK of 172.123.10.83 from 
172.123.10.1
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPDECLINE on eth0 to 
255.255.255.255 port 67
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 5
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPREQUEST of 172.123.10.83 on eth0 
to 255.255.255.255 port 67
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPOFFER of 172.123.10.83 from 
172.123.10.1
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPACK of 172.123.10.83 from 
172.123.10.1
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPDECLINE on eth0 to 
255.255.255.255 port 67
 
The reason for the DHCPCELINE was:
|/sbin/dhclient-script: 28: . :Can't open /usr/share/sendmail/dynamic

Which could have been caused by
|/etc/network/if-up.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/network/if-post-down.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/network/if-down.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/dhcp/dhclient-exit-hooks.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/ppp/ip-up.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/ppp/ip-down.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/resolvconf/update-libc.d/sendmail:. /usr/share/sendmail/dynamic;

but in my case it was /etc/dhcp/dhclient-exit-hooks.d/sendmail.

Please either remove those files on remove or test for
"/usr/share/sendmail/dynamic" before the script sources the file.

This was a headless box so it took while to notice…

Sebastian

Bug#873977: Please override

[Chris West]

Package: ant
Version: 1.9.9-4
Severity: wishlist
User: debian-j...@lists.debian.org
Usertags: default-java9

ant is upgrading the -source and -target options passed to javac, such
that they are a minimum of 1.6, to fix projects compiling with Java 9.

However, as we still have this crazy notion that we should ship javadoc,
many packages are immediately trying to build javadoc after the code has
compiled, and are passing "-source 1.4" along to their javadoc
invocation too.

Please also fix the source version, to a minimum of 1.6, in this case.



A good, small, fast example package for this is docbook-xsl-saxon. It
even builds with a different JAVA_HOME if you delete the JAVA_HOME
declaration from debian/rules:

-do-compile:
[javac] Use of a source 1.4 is no longer supported, switching to 1.6
[javac] Use of a target 1.4 is no longer supported, switching to 1.6
[javac] Compiling 21 source files to 
/var/tmp/faux170901.pimiento/docbook-xsl-saxon-1.00.dfsg.1/classes

...

jar:

-javadoc-build:
[mkdir] Created dir: 
/var/tmp/faux170901.pimiento/docbook-xsl-saxon-1.00.dfsg.1/api
  [javadoc] Warning: Leaving out empty argument '-windowtitle'
  [javadoc] Generating Javadoc
  [javadoc] Javadoc execution
  [javadoc] 1 error
  [javadoc] error: Source option 1.4 is no longer supported. Use 1.6 or later.

BUILD FAILED


The -source argument comes from the nbproject, via.
https://sources.debian.net/src/docbook-xsl-saxon/1.00.dfsg.1-7/nbproject/build-impl.xml/#L425
https://sources.debian.net/src/docbook-xsl-saxon/1.00.dfsg.1-7/nbproject/project.properties/#L26


Cheers,
Chris.

Bug#873975: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: cvc3
Version: 2.4.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.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[2]: Entering directory '/build/cvc3-2.4.1/java'
if [ ! -d obj ]; then mkdir -p obj; fi
/usr/lib/jvm/default-java/bin/javac  -Xlint -g -source 1.4 -sourcepath src \
-d obj src/cvc3/JniUtils.java
warning: [options] bootstrap class path not set in conjunction with -source 1.4
error: Source option 1.4 is no longer supported. Use 1.6 or later.
make[2]: *** [JniUtils.class] Error 2
Makefile:166: recipe for target 'JniUtils.class' failed
make[2]: Leaving directory '/build/cvc3-2.4.1/java'

Cheers,
Chris.

Bug#873976: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: db5.3
Version: 5.3.28
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

configure:18523: checking for javac
configure:18539: found /usr/bin/javac
configure:18550: result: javac
configure:18608: checking if javac works
configure:18622: javac -source 1.5 -target 1.5 Test.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.
configure:18625: $? = 2
configure:18629: error: The Java compiler javac failed (see config.log, check 
the CLASSPATH?)


Cheers,
Chris.

Bug#873974: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: colorpicker
Version: 1.0.0
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[1]: Entering directory '/build/colorpicker-1.0.0'
jh_build --javacopts="-source 1.5 -target 1.5" --javadoc-opts="-source 1.5"
grep-dctrl: debian/control:21: expected a colon.
find com -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.ColorPicker -d 
debian/_jh_build.ColorPicker -encoding ISO8859-1 -source 1.5 -target 1.5
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[1]: *** [override_jh_build] Error 123
debian/rules:18: recipe for target 'override_jh_build' failed
make[1]: Leaving directory '/build/colorpicker-1.0.0'

Cheers,
Chris.

Bug#873973: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: coco-java
Version: 20110419
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[1]: Entering directory '/build/coco-java-20110419'
javac -d . -source 1.4 -target 1.4 Trace.java Scanner.java Tab.java DFA.java 
ParserGen.java Parser.java Coco.java
warning: [options] bootstrap class path not set in conjunction with -source 1.4
error: Source option 1.4 is no longer supported. Use 1.6 or later.

Cheers,
Chris.

Bug#873972: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: cadencii
Version: 3.3.9+svn20110818.r1732
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

./build/java/org/kbinani/windows/forms/*.java 
./build/java/org/kbinani/xml/*.java -encoding UTF8 -target 1.5 -source 1.5
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.
Makefile:1081: recipe for target 'jcadencii' failed

Cheers,
Chris.

Bug#871956: lintian: false positive: binary-file-built-without-LFS-support on x32

[Adam Borowski]

On Fri, Sep 01, 2017 at 08:50:05PM +0200, Boud Roukema wrote:
> On Fri, 1 Sep 2017, Adam Borowski wrote:
> > Also, the vast majority of packages don't trigger this warning as they
> > request LFS unconditionally instead of trying to autodetect it.
> 
> The lintian warning here:
> https://lintian.debian.org/tags/binary-file-built-without-LFS-support.html
> says "This can be done by using the AC_SYS_LARGEFILE macro with autoconf, 
> or... "
> 
> This is what I've done in mpgrafic, since (in principle) autoconf
> makes things less hardwired.
> 
> Isn't it cleaner to use the AC_SYS_LARGEFILE autoconf macro rather
> than hardwire something such as -D_FILE_OFFSET_BITS=64 as a
> non-optional compile option?

That assumes your project uses autotools -- they seem to have rapidly
regressed recently, and projects are fleeing them left and right.

And what AC_SYS_LARGEFILE does, at least on Linux, is to return a hardcoded
setting so programs switch from off_t to off64_t whether they need to or
not.  This does the right thing on old 32-bit archs and is harmless on
64-bit and new 32-bit.

The problem is in snowflake packages that do things their own way and enable
LFS only when it's actually needed.  Here's where the lintian false positive
triggers.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
⠈⠳⣄ 

Bug#873971: FTBFS with Java 9 due to -source/-target only

[Chris West]

Source: antlr
Version: 2.7.7+dfsg-7
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

/usr/lib/jvm/default-java/bin/javac -source 1.4 `find antlr -name '*.java'`
warning: [options] bootstrap class path not set in conjunction with -source 1.4
error: Source option 1.4 is no longer supported. Use 1.6 or later.

Cheers,
Chris.

Bug#873969: -source upgrade to 1.6 breaks if ant.build.javac.source is set

[Chris West]

Source: ant
Version: 1.9.9-4
Severity: wishlist
User: debian-j...@lists.debian.org
Usertags: default-java9

ant has been taught to upgrade the -source and -target versions to 1.6,
to support Java 9. However, if a package specifies:

-Dant.build.javac.source=1.5

... then this override is skipped. Example package: airport-utils
(Can you tell I read lists in alphabetical order?)

https://sources.debian.net/src/airport-utils/2-6/debian/rules/#L7

jar-compile:
[javac] 
/var/tmp/faux170901.breezy/airport-utils-2/airport2config-build/build.xml:50: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 46 source files to 
/var/tmp/faux170901.breezy/airport-utils-2/airport2config-build/build
[javac] error: Source option 1.5 is no longer supported. Use 1.6 or later.
[javac] error: Target option 1.5 is no longer supported. Use 1.6 or later.

I believe the issue is that Javac#getSource() ignores the "source" field
if this property is set:

https://sources.debian.net/src/ant/1.9.9-4/src/main/org/apache/tools/ant/taskdefs/Javac.java/#L208

..and the patch only affects setting the field. Maybe move the fix to
getSource()?

https://sources.debian.net/src/ant/1.9.9-4/debian/patches/0013-auto-adjust-target.patch/


Cheers,
Chris.

Bug#873970: ITP: gtksourceview4: GTK+ syntax highlighting widget

[Jeremy Bicha]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org
Owner: jbi...@ubuntu.com

Package Name: gtksourceview4
Version: 3.99.4
Upstream Author : Ignacio Casal Quinteiro,
  Jesse van den Kieboom, Paolo Borelli, Sébastien Wilmet and others
License : LGPL-2.1+ except for a few GPL-2+ files
Programming Lang: C

Description: shared libraries for the GTK+ syntax highlighting widget
 GtkSourceView is a text widget that extends the standard GTK+ 3.x text widget
 GtkTextView. It improves GtkTextView by implementing syntax highlighting and
 other features typical of a source editor.

Other Info
--
Somewhat confusingly, gtksourceview4 is a new API for GTK+ 3.
gtksourceview5 is planned for release in a few years for GTK+ 4.

For more information, see
https://wiki.gnome.org/Projects/GtkSourceView/TransitionToGtkSourceView4
https://developer.gnome.org/gtksourceview/unstable/

The Debian GNOME team intends to maintain this package.

I'm uploading to experimental for now.

Packaging is currently at
https://anonscm.debian.org/viewvc/pkg-gnome/desktop/experimental/gtksourceview4/

Thanks,
Jeremy Bicha

Bug#841796: Orphaning Package (Was: Re: Updating the ibus-table-extraphrase Uploaders list)

[Tobias Frost]

Control: reassign -1 wnpp
Control: retitle -1 O: ibus-table-extraphrase -- Extra phrase for table engine 
of ibus

The only uploader of this package has asked to be removed from this package.
This makes the package technially orphaned, as it requires at least one human
uploader. This had not been considered when filing the "Remove from Uploader" 
bug.

This mail corrects this.

The IME Packaging Team is CC'ed so that they are aware and can adopt the package
accordingly.

--
tobi (for the MIA team)


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

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

Bug#856277: partially solved

[Carsten Schoenert]

Hello Dtux,

On Wed, Mar 01, 2017 at 12:25:31AM +0100, Dtux wrote:
> partially solved => no more crash, but same debug message (and more)
> 
> issue= remove all personal libraries added in config/kicad/fp-lib-table
> and re-add this personal libraries with "libraries wizard"
> 
> new error message at the pcbnew startup(#840287
> )=
> "Mismatch between the program and library build versions detected.
> The library used 3.0 (wchar_t,compiler with C++ ABI 1010,wx
> containers,compatible with 2.8),and wxPython used 3.0 (wchar_t,compiler with
> C++ ABI 1009,wx containers,compatible with 2.8)."

this (and also a crash) shouldn't happen with the version 4.0.6 in
testing. Still issues or is version 4.0.6 working?

Regards
Carsten

Bug#873968: openvas-scanner: previous changelog history of package not provided

[Javier Fernandez-Sanguino]

Package: openvas-scanner
Version:5.1.1-2
Priority: wishlist

Dear colleagues,

Many years ago  I maintained first openvas-server (from 2009 to 2010)
and then openvas-scanner package (and other related openvas-xxx packages) in
Debian. IIRC, Openvas-scanner was provided in experimental for 2 years (IIRC
from 2010 to 2012), as reflected in the PTS.

However, upon looking at the openvas-scanner package changelog [0]
there is not any reference to any of this past history.

I would appreciate if this past history is retained in, at least, the
packages debian/changelog . Please let me know if you would be open to
a patch to include this information in the current package

Best regards
Javier

[0] 
http://metadata.ftp-master.debian.org/changelogs/main/o/openvas-scanner/unstable_changelog

Bug#873746: crash backtrace

[Sven Joachim]

For the reference, this bug has been reported originally at
https://bugzilla.redhat.com/show_bug.cgi?id=1484290.  Thomas said he
could not reproduce it, but the crash happens with the current version
in unstable.

Here is a backtrace from "infotocap POC12" after rebuilding tic with
-O0, so that the variables are not all optimized out:

,
| Reading symbols from infotocap...done.
| (gdb) set args POC12
| (gdb) run
| Starting program: /usr/local/src/deb-src/ncurses/ncurses/obj/progs/infotocap 
POC12 
| 
| Program received signal SIGSEGV, Segmentation fault.
| __strcmp_ssse3 () at ../sysdeps/i386/i686/multiarch/strcmp-ssse3.S:241
| 241   ../sysdeps/i386/i686/multiarch/strcmp-ssse3.S: Datei oder Verzeichnis 
nicht gefunden.
| (gdb) bt full
| #0  __strcmp_ssse3 () at ../sysdeps/i386/i686/multiarch/strcmp-ssse3.S:241
| No locals.
| #1  0x565602cd in fmt_entry (tterm=0x56577c40, pred=0x5655e9e9 
, content_only=0, suppress_untranslatable=0, infodump=0, 
numbers=0) at ../../progs/dump_entry.c:996
| i = 7
| j = 39
| buffer = '\000' ...
| capability = 0x0
| name = 0xf7fb0627 "ws"
| predval = -1
| len = 14
| num_bools = 0
| num_values = 0
| num_strings = 0
| outcount = false
| #2  0x5656188d in dump_entry (tterm=0x56577c40, suppress_untranslatable=0, 
limited=1, numbers=0, pred=0x0) at ../../progs/dump_entry.c:1513
| save_tterm = {term_names = 0x0, str_table = 0x0, Booleans = 0x0, 
Numbers = 0x0, Strings = 0x0, ext_str_table = 0x0, ext_Names = 0x0, 
num_Booleans = 0, num_Numbers = 0, num_Strings = 0, ext_Booleans = 0, 
ext_Numbers = 0, ext_Strings = 0}
| len = 0
| critlen = 1023
| legend = 0x56567862 "older termcap"
| infodump = false
| #3  0x56558ceb in main (argc=2, argv=0xd324) at ../../progs/tic.c:1037
| j = -1
| len = 0
| my_tmpname = '\000' 
| my_altfile = '\000' ...
| v_opt = -1
| debug_level = 0
| smart_defaults = 1
| termcap = 0x0
| qp = 0x56577c40
| this_opt = -1
| last_opt = 63
| outform = 2
| sortmode = 4
| width = 60
| height = 65535
| formatted = false
| literal = false
| numbers = 0
| forceresolve = false
| limited = true
| tversion = 0x0
| source_file = 0xd509 "POC12"
| outdir = 0x0
| check_only = false
| suppress_untranslatable = false
| quickdump = 0
| quiet = false
| wrap_strings = false
| (gdb)
`

The POC12 file is attached.



POC12
Description: Binary data

Bug#841793: Orphaning Package (Was: Re: Updating the zinnia Uploaders list)

[Tobias Frost]

Control: reassign -1 wnpp
Control: retitle -1 O: zinnia -- online handwriting recognition system with 
machine learning

The only uploader of this package has asked to be removed from this package.
This makes the package technially orphaned, as it requires at least one human
uploader. This had not been considered when filing the "Remove from Uploader" 
bug.

This mail corrects this.

The IME Packaging Team is CC'ed so that they are aware.

--
tobi (for the MIA team)

Bug#873966: config-package-dev: transform operation error

[Geoffrey Thomas]

On Fri, 1 Sep 2017, Bruno Maitre wrote:


Dear Maintainer,

When using the transform operation dh_configpackage will output that kind
of error:

Can't use string ("/ARRAY(0x55f37e2c3080)") as an ARRAY ref while "strict refs" 
in use at /usr/bin/dh_configpackage line 394.

This error has been introduced by the correction of: 
#803962 : config-package-dev: Requires leading slashes un debian/*.displace


For this correction we iterrate through the differents operation arrays to
add a leading slash if needed.
The problem is that @transformfiles is an array of array since it's created
with filedoublearray function and not the filearray function like the others
operation arrays (which are simples arrays).
This lead to an add of a slash in front of the reference array ARRAY(0xXXX...) 
as can be seen in the error message.

Subsequent processing of transformfiles results in an error.

I've attached a patch with a way to fix this issue by removing transformfiles 
from the leading slashes verification loop and by checking leading slashes in 
the treatment of transformfiles itself as it was done before.


Note that I've triggered the error in a Debian testing environment and
the stable version is not affected.


Oops - thank you! I've applied the patch and I'll aim to do an upload that 
fixes this tonight.


Also, I could have sworn I did a test run of building all the examples in 
examples/, but indeed `apt-get source config-package-dev; cd 
examples/debhelper/debathena-transform-example-1.0; dpkg-buildpackage` 
fails. (And also fails in unstable because the example config file has 
changed location.) We should really add a test suite to make sure the 
examples build and produce the .debs we expect.


--
Geoffrey Thomas
https://ldpreload.com
geo...@ldpreload.com

Bug#841807: Orphaning Package (Was: Re: Updating the debian-zh-faq Uploaders list)

[Tobias Frost]

Package: src:debian-zh-faq
Followup-For: Bug #841807
Control: reassign -1 wnpp
Control: retitle -1 O: debian-zh-faq -- Debian Chinese FAQ (Chinese GB)
Control: severity -1 normal

The only uploader of this package has asked to be removed from this package.
This makes the package technially orphaned, as it requires at least one human
uploader. This had not been considered when filing the "Remove from Uploader" 
bug.

This mail corrects this.

The Debian Chinese Team is CC'ed so that they are aware and can adopt the 
package
accordingly.

--
tobi (for the MIA team)


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

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

Bug#871956: lintian: false positive: binary-file-built-without-LFS-support on x32

[Boud Roukema]

On Fri, 1 Sep 2017, Adam Borowski wrote:


Also, the vast majority of packages don't trigger this warning as they
request LFS unconditionally instead of trying to autodetect it.


The lintian warning here:
https://lintian.debian.org/tags/binary-file-built-without-LFS-support.html
says "This can be done by using the AC_SYS_LARGEFILE macro with autoconf, or... 
"

This is what I've done in mpgrafic, since (in principle) autoconf
makes things less hardwired.

Isn't it cleaner to use the AC_SYS_LARGEFILE autoconf macro rather
than hardwire something such as -D_FILE_OFFSET_BITS=64 as a
non-optional compile option?

Also, a rather important question seems to me to be: are there some
architectures (e.g. especially 32-bit) where there is no point trying
to ensure LFS support, since it won't work anyway? Or conversely:
can gcc implement a software solution for LFS support no matter what
the architecture is (among debian official + unofficial ports)?

Bug#873967: openvas-manager: No record of previous changelog history of Debian package

[Javier Fernandez-Sanguino]

Package: openvas-manager
Version: 4.0.0
Priority: wishlist

Dear colleagues,

Many years ago I maintained openvas-manager in experimental, as
reflected in the PTS. However, upon review of the latest's package
changelog [0] I do not see any reference to this. There are, however,
many references to versions of the package which where generated
automatically by OpenSUSE but never distributed in Debian.

I would appreciate if this past history is retained in, at least, the
packages debian/changelog . Please let me know if you would be open to
a patch to include this information in the current package

Best regards
Javier

[0] https://packages.qa.debian.org/o/openvas-manager.html

Bug#873919: make dpkg-buildpackage default locale UTF-8

[Ivan Shmakov]

> Hans-Christoph Steiner  writes:

 > Package: dpkg-dev

 > More and more packages are adding unicode files

I assume you mean “UTF-8 filenames” here (per below), right?

 > as unicode support has become more reliable and available.

What are the use cases for such filenames?

FWIW, I more than just occasionally use Debian in environments
with fonts lacking good (as in: ≥ 90%) Unicode, or even BMP,
coverage.  (Specifically, I’m for the most part interested in
Latin-1, -3, and Cyrillic characters only.)

Do you suggest that there’re filenames in Debian packages that
cannot be rendered in such environments?  If so, that’d
certainly be a nuisance for me.

 > The package building process is not guaranteed to happen in a unicode
 > locale since the Debian default locale is LC_ALL=C, which is ASCII
 > not UTF-8.  Reading UTF-8 filenames when the system is using ASCII
 > causes errors (Python makes them very visible, for example).

[…]

-- 
FSF associate member #7257  np. Fear of the Dark — Iron Maiden  B6A0 230E 334A

Bug#873962: sweethome3d: Random crash when opening/manipulating a file

[Markus Koschany]

Control: severity -1 important

Am 01.09.2017 um 17:19 schrieb Ludovic Lebègue:
> Package: sweethome3d
> Version: 5.4+dfsg-2
> Severity: grave
> Tags: upstream
> Justification: causes non-serious data loss
> 
> Hi,
> 
> On Debian testing sweethome3D now crashes randomly when opening or 
> manipulating
> a file

Hello,

thanks for reporting. We have to narrow down the issue first before we
assume severity grave which basically means that the program is
unusable. Your stacktrace also indicates that sweethome3d is only
affected by the bug and the real issue is in OpenJDK 8 or the underlying
graphics stack.

Could you provide more information how you trigger the crash please?
What file do you use? Please install openjdk-8-dbg so that we can get a
meaningful backtrace of the crash.

When I just search for the string
"Java_sun_java2d_opengl_OGLRenderQueue_flushBuffer" I can also find
numerous bug reports related to OpenJDK.

Markus




signature.asc
Description: OpenPGP digital signature

Bug#872482: why the further fixup is not needed

[Luca Boccassi]

On Wed, 30 Aug 2017 15:05:30 +0100 Luca Boccassi 
wrote:
> On Fri, 18 Aug 2017 07:35:20 +0200 Christian Ehrhardt
 d...@canonical.com> wrote:
> > For a grain of confidence and background - Upstream there is also a
> follow
> > up fix [1], but that is not needed for your package.
> > 
> > The reason is, that this follow up is only needed if dpdk has no
> > pkg-config, which the 16.11 based package that is in Debian right
now
> > already have.
> > 
> > [1]: https://github.com/collectd/collectd/pull/2405
> 
> The patch I sent actually already has that fix included as well :-)
> 
> Maintainers, gentle ping - I would like to upload a new version of
DPDK
> to sid (16.11.3) which will include the breaking change for !amd64.
> 
> It would be really appreciated if this patch could be looked at. I am
> more than willing to do the extra work and provide an NMU if time is
> short on your hands - just let me know if it's acceptable.
> 
> Thank you!

In case it's more convenient, I've sent a pull request on Github:

https://github.com/collectd/pkg-debian/pull/14

-- 
Kind regards,
Luca Boccassi

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

Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium

[Tollef Fog Heen]

]] Didier 'OdyX' Raboud 

> There are _plenty_ of changes that one needs to care about in a stable 
> upgrade: things like mandatory postfixing of Apache configuration files, 
> removal 
> of specific Python3 versions, removal of upstart, etc. Having to change a 
> shebang isn't a big deal given the amount of things one has to check accross 
> a 
> stable release upgrade.

You might quite reasonably write scripts in node and either store them
in a shared directory across multiple Debian versions or have ~/bin in
version control shared across multiple Debian installations (and
corresponding versions).

#! lines are a bit special in this regard.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Bug#873722: mirror.upb.edu.co permission issues

[Peter Palfrader]

Control: reopen -1
Control: retitle -1 mirror submission for mirror.upb.edu.co [permission issues]
Control: tag -1 +moreinfo

On Wed, 30 Aug 2017, Peter Palfrader wrote:

> > o we recommend mirrors not sync directly from service aliases such as
> >   ftp..debian.org (only http is guaranteed to be available at
> >   ftp..d.o sites).  Maybe change your config to sync from
> >   the site currently backing the ftp..debian.org service you sync
> >   from?
> 
> Also
> http://mirror.upb.edu.co/debian/project/trace/master
> is forbidden.
> 
> Please fix.

I am removing the mirror from the list again until this is fixed.
Please let us know when this happens.

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/