Bug#901293: closing 901293

[Salvatore Bonaccorso]

close 901293 0.31.1+dfsg-1
thanks

Processed: closing 901293

[Debian Bug Tracking System]

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

> close 901293 0.31.1+dfsg-1
Bug #901293 [src:matrix-synapse] matrix-synapse: Improper event filtering in 
get_missing_events handler
Ignoring request to alter fixed versions of bug #901293 to the same values 
previously set
Bug #901293 [src:matrix-synapse] matrix-synapse: Improper event filtering in 
get_missing_events handler
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: matrix-synapse: Improper event filtering in get_missing_events handler

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.31.1+dfsg-1
Bug #901293 [src:matrix-synapse] matrix-synapse: Improper event filtering in 
get_missing_events handler
Marked as fixed in versions matrix-synapse/0.31.1+dfsg-1.

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

Bug#901293: matrix-synapse: Improper event filtering in get_missing_events handler

[Salvatore Bonaccorso]

Source: matrix-synapse
Version: 0.30.0+dfsg-1
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/matrix-org/synapse/pull/3371
Control: fixed -1 0.31.1+dfsg-1

From

https://matrix.org/blog/2018/06/08/synapse-0-31-1-released/

> v0.31.1 fixes a security bug in the get_missing_events federation API
> where event visibility rules were not applied correctly.

Regards,
Salvatore

Processed: tagging 899478, tagging 899441, tagging 899447, tagging 899453, tagging 899479, tagging 899501 ...

[Debian Bug Tracking System]

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

> tags 899478 + sid buster
Bug #899478 [src:culmus-fancy] culmus-fancy: Invalid maintainer address 
debian-hebrew-pack...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899441 + sid buster
Bug #899441 [src:aspell-ar] aspell-ar: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899447 + sid buster
Bug #899447 [src:aspell-ku] aspell-ku: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899453 + sid buster
Bug #899453 [src:bluez-firmware] bluez-firmware: Invalid maintainer address 
pkg-bluetooth-maintain...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899479 + sid buster
Bug #899479 [src:combat] combat: Invalid maintainer address 
pkg-corba-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899501 + sid buster
Bug #899501 [src:fcitx-chewing] fcitx-chewing: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899505 + sid buster
Bug #899505 [src:fcitx-sayura] fcitx-sayura: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899516 + sid buster
Bug #899516 [src:fuse-umfuse-fat] fuse-umfuse-fat: Invalid maintainer address 
pkg-vsquare-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899527 + sid buster
Bug #899527 [src:google-apputils-python] google-apputils-python: Invalid 
maintainer address cloud-packa...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899530 + sid buster
Bug #899530 [src:gnome-phone-manager] gnome-phone-manager: Invalid maintainer 
address pkg-bluetooth-maintain...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899534 + sid buster
Bug #899534 [src:hdate-applet] hdate-applet: Invalid maintainer address 
debian-hebrew-pack...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899536 + sid buster
Bug #899536 [src:hippo-canvas] hippo-canvas: Invalid maintainer address 
online-desktop-maintain...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899539 + sid buster
Bug #899539 [src:hunspell-ar] hunspell-ar: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899545 + sid buster
Bug #899545 [src:ibus-rime] ibus-rime: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899547 + sid buster
Bug #899547 [src:ibus-sunpinyin] ibus-sunpinyin: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899557 + sid buster
Bug #899557 [src:kaa-base] kaa-base: Invalid maintainer address 
pkg-freevo-ma...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899560 + sid buster
Bug #899560 [src:kakasi] kakasi: Invalid maintainer address 
pkg-nlp-ja-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899562 + sid buster
Bug #899562 [src:kernel-patch-viewos] kernel-patch-viewos: Invalid maintainer 
address pkg-vsquare-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899580 + sid buster
Bug #899580 [src:libkkc-data] libkkc-data: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899583 + sid buster
Bug #899583 [src:libmozilla-ldap-perl] libmozilla-ldap-perl: Invalid maintainer 
address pkg-fedora-ds-maintain...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899616 + sid buster
Bug #899616 [src:myspell-fa] myspell-fa: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899627 + sid buster experimental
Bug #899627 [src:openambit] openambit: Invalid maintainer address 
pkg-running-de...@lists.alioth.debian.org
Added tag(s) sid, experimental, and buster.
> tags 899633 + sid buster
Bug #899633 [src:otcl] otcl: Invalid maintainer address 
pkg-netsim-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899659 + sid buster
Bug #899659 [src:purelibc] purelibc: Invalid maintainer address 
pkg-vsquare-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899663 + sid buster
Bug #899663 [src:pylirc] pylirc: Invalid maintainer address 
pkg-lirc-ma...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899676 + sid buster
Bug #899676 [src:python-omniorb] python-omniorb: Invalid maintainer address 
pkg-corba-de...@lists.alioth.debian.org
Added tag(s) buster and sid.
> tags 899690 + sid buster
Bug #899690 [src:scim-pinyin] scim-pinyin: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899707 + sid buster
Bug #899707 [src:tclcl] tclcl: Invalid maintainer address 
pkg-netsim-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 899711 + sid buster
Bug #899711 [src:thunar-vcs-plugin] thunar-vcs-plugin: Invalid maintainer 
address 

Bug#901290: chromium: version 68 arm build causes internal compiler error

[Michael Gilbert]

package: src:chromium-browser
severity: grave
version: 68.0.3440.7-1

The version just uploaded to experimental causes an internal compiler
error in gcc on arm [0].

Best wishes,
Mike

[0]https://buildd.debian.org/status/package.php?p=chromium-browser=experimental

Processed: Re: libviennacl-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libviennacl-dev/README.gz

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.7.1+dfsg1-4
Bug #901041 {Done: Anton Gladky } [libviennacl-doc] 
libviennacl-doc: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/doc/libviennacl-dev/README.gz
Marked as found in versions viennacl/1.7.1+dfsg1-4; no longer marked as fixed 
in versions viennacl/1.7.1+dfsg1-4 and reopened.

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

Bug#901041: libviennacl-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libviennacl-dev/README.gz

[Andreas Beckmann]

Followup-For: Bug #901041
Control: found -1 1.7.1+dfsg1-4

You fixed the wrong problem. The Breaks+Replaces may still be needed,
but the underlying problem is not fixed - both libviennacl-dev and
libviennacl-doc ship these files:

  usr/share/doc/libviennacl-dev/README.gz
  usr/share/doc/libviennacl-dev/changelog.gz

This is most likely caused by a behavioral change in dh_installdocs
in debhelper compat level 11.

(Due to upload+testing timing I saw the buster->sid failure before the
sid+sid failure).


Andreas

Bug#901048: gnat-*-x86-64-linux-gnu: missing Conflicts: gnat-5, gnat-6

[Andreas Beckmann]

On 2018-06-08 17:51, Matthias Klose wrote:
> you should not run piuparts against outdated binaries.

These tests take everything available in the Packages files ...

>  I filed #899045
> to remove these packages, but that didn't get yet processed.  Closing
> this issue now.

Interestingly these packages still don't show up in the ftp-master cruft
report ... (otherwise I might have spotted their cruftness).


Andreas

Bug#901220: libreoffice-dictionaries: FTBFS: can't cd to /<>/debian/hunspell-es/usr/share/hunspell

[Andreas Beckmann]

Hi Rene,

On 2018-06-10 11:10, Rene Engelhard wrote:
> On Sun, Jun 10, 2018 at 10:56:31AM +0200, Andreas Beckmann wrote:
>> libreoffice-dictionaries/experimental FTBFS:
> Yes, I have seen this. I *do* look at buildlogs after uploads.

Unfortunately not everone does ... Anyway, I just needed a bug number to
tag a failed rebuild test in experimental :-)

> Will be fixed with a subsequent upload, whenever this will happen.
> Probably with beta2.

No hurry needed, I don't need the package.


Andreas

Bug#901185: remove unlisted bash dependecy

[積丹尼 Dan Jacobson]

Why use bash at all if e.g.,

$ checkbashisms /usr/sbin/update-exim4.conf.template
could not find any possible bashisms in bash script 
/usr/sbin/update-exim4.conf.template

means one can just use #!/bin/sh ?

Processed: limit source to spip, tagging 899895, tagging 879954

[Debian Bug Tracking System]

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

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

> tags 899895 + pending
Bug #899895 [src:spip] spip: Invalid maintainer address 
spip-maintain...@lists.alioth.debian.org
Added tag(s) pending.
> tags 879954 + pending
Bug #879954 [src:spip] spip: CVE-2017-15736
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: severity of 900597 is important

[Debian Bug Tracking System]

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

> severity 900597 important
Bug #900597 [src:golang-github-prometheus-client-golang] 
golang-github-prometheus-client-golang/0.9.0~pre1+git20180417.82f5ff1-2 breaks 
golang-github-docker-go-metrics
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#898024: marked as done (trying to overwrite '/usr/include/nodejs/common.gypi', which is also in package nodejs-dev 10.0.0~dfsg-2)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 23:06:59 +
with message-id 
and subject line Bug#898024: fixed in nodejs 10.4.0~dfsg-1
has caused the Debian Bug report #898024,
regarding trying to overwrite '/usr/include/nodejs/common.gypi', which is also 
in package nodejs-dev 10.0.0~dfsg-2
to be marked as done.

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

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


-- 
898024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nodejs-dev

Unpacking libnode64-dev (10.0.0~dfsg1-3) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-NI7HKh/073-libnode64-dev_10.0.0~dfsg1-3_amd64.deb 
(--unpack):
 trying to overwrite '/usr/include/nodejs/common.gypi', which is also in 
package nodejs-dev 10.0.0~dfsg-2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)


dpkg: dependency problems prevent configuration of nodejs-dev:
 nodejs-dev depends on libnode-dev; however:
  Package libnode-dev is not installed.

dpkg: error processing package nodejs-dev (--configure):
 dependency problems - leaving unconfigured
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 10.4.0~dfsg-1

We believe that the bug you reported is fixed in the latest version of
nodejs, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 898...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated nodejs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Jun 2018 00:12:34 +0200
Source: nodejs
Binary: nodejs-dev libnode64-dev nodejs libnode64 nodejs-doc
Architecture: source
Version: 10.4.0~dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Description:
 libnode64  - evented I/O for V8 javascript - runtime library
 libnode64-dev - evented I/O for V8 javascript (development files)
 nodejs - evented I/O for V8 javascript - runtime executable
 nodejs-dev - evented I/O for V8 javascript (debhelper files)
 nodejs-doc - API documentation for Node.js, the javascript platform
Closes: 898024
Changes:
 nodejs (10.4.0~dfsg-1) experimental; urgency=medium
 .
   * New upstream version 10.4.0~dfsg
   * libnodeXX-dev Breaks+Replaces nodejs-dev << 10 (Closes: #898024)
   * Standards-Version 4.1.4
   * Copyright:
+ comment the unexpected change in this BSD-3-clause
 + remove duplicate paragraph
 + remove files
 + add antlr4 with a BSD-3-clause license
Checksums-Sha1:
 5709b8d7f2bb648234ce6d2248da61a262942ba6 3120 nodejs_10.4.0~dfsg-1.dsc
 a02808b56cf2a7bdef8db34d0bef3d6a9a861fc6 15123239 
nodejs_10.4.0~dfsg.orig.tar.gz
 6db596fca14074c6221713dcd75f56fd18633a4a 78192 
nodejs_10.4.0~dfsg-1.debian.tar.xz
 7112d409328327b6823c32fdff6c2decb7ebb983 8608 
nodejs_10.4.0~dfsg-1_source.buildinfo
Checksums-Sha256:
 79e5b1d27ed68fec9409aa0bfd645a4b066e2ba89677f3e3d1cb2dd6dab1ce3b 3120 
nodejs_10.4.0~dfsg-1.dsc
 722d93dd14473c5c9e92f0e0f0220d9e3cd8834cae7dbabafd34a60338826c40 15123239 
nodejs_10.4.0~dfsg.orig.tar.gz
 5a9312e7c846aa835eb76e2cb66a0385a868584d4870ec58f77b8d97e12e227c 78192 
nodejs_10.4.0~dfsg-1.debian.tar.xz
 98a95fa1853d8ee9ed4d20c204d31fd559aee7c63f77aa038dfbb26fb0ecdef3 8608 
nodejs_10.4.0~dfsg-1_source.buildinfo
Files:
 5da906d4a7abbea859365dfb69e9f299 3120 javascript optional 
nodejs_10.4.0~dfsg-1.dsc
 3c19adb40b7dcb24ae0d66ea585c03c5 15123239 javascript optional 
nodejs_10.4.0~dfsg.orig.tar.gz
 c9f0c4dfa65b39e44a97a3fb91b6ca3c 78192 javascript optional 
nodejs_10.4.0~dfsg-1.debian.tar.xz
 55a167341d737d239360d42223889792 8608 javascript optional 
nodejs_10.4.0~dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAlsdopESHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0K9YQAKzoqty5KGjfuv9hiL0muWaz5HYUe8Q0
ds+/15fK8C2htojKee5F/HSp3rG1V7qFhnsIJMzJ5r2Bs798Xi0boasuouoq3Qr6
aMLQoUwq3CUtnvAMeRt34rigfLfMyX+eees6SmmbTPX1CPyyApg/EG0j+fWW3iXS
KYMVO5F2bwh4qGON7ZT1kd+cYs6b90vRWkPNqzxDMKrXzZMLAjDxBjZdEYX+9IW/
XJwKkcnBiHtMky7wJqJ9DVJGPIkCy9mt3yuTIjJAynIsbJub/z+Y9mnMToVOl8zR
dcjAXfLlOvVr9HesBRTMm6Z/GZQ23Y4JzjnNLfyYgn22KBfzxUrI6w8tL3dclFQX

Bug#901185: [Debconf-devel] Bug#901185: me too

[Colin Watson]

On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
> On 2018-06-10 Colin Watson  wrote:
> > On Sun, Jun 10, 2018 at 03:03:28PM +0200, Andreas Metzler wrote:
> >> I have tried debugging the issue to get a minimal testcase. I have had
> >> some success. The issue is triggered by debconf.
> >> /usr/share/debconf/confmodule changes IFS to \n and with bash5 this
> >> change is persistent and breaks the maintainerscript.
> 
> > Does this patch help?
> 
> yes, resetting IFS to its default value in confmodule helps.

Thanks.  For completeness, could you try this variant patch?  If shells
are going to be unreliable about setting IFS in this way, then I'd
rather just separate out the assignments altogether.

diff --git a/confmodule b/confmodule
index 8347c0b0..3ef7a309 100644
--- a/confmodule
+++ b/confmodule
@@ -42,10 +42,11 @@ _db_cmd () {
_db_internal_IFS="$IFS"
IFS=' '
printf '%s\n' "$*" >&3
-   IFS="$_db_internal_IFS"
# Set to newline to get whole line.
IFS='
-' read -r _db_internal_line
+'
+   read -r _db_internal_line
+   IFS="$_db_internal_IFS"
# Disgusting, but it's the only good way to split the line,
# preserving all other whitespace.
RET="${_db_internal_line#[! ][  ]}"

(This does still seem like a bash bug though, unless there's some arcane
interpretation of the standards that I'm unaware of.)

Cheers,

-- 
Colin Watson   [cjwat...@debian.org]

Bug#901243: nm-applet

[Le Déchaîné]

I'm guessing it's the same for nm-applet. I got no network manager
applet and trash applet either. System/Preferences is kinda empty too.

It may be the reason why I have to login and "startx" now (well...
sudo ifconfig eth0 up, sudo dhclient, and then startx).

Some interesting logs/crash.

Syslog:
Jun 10 06:48:26 symphony systemd[1]: Reloading.
Jun 10 06:48:27 symphony systemd[1]: Stopping Light Display Manager...
Jun 10 06:48:27 symphony at-spi-bus-launcher[1407]: XIO:  fatal IO
error 11 (Resource temporarily unavailable) on X server ":0"
Jun 10 06:48:27 symphony at-spi-bus-launcher[1407]:   after 82277
requests (82277 known processed) with 0 events remaining.
Jun 10 06:48:27 symphony pulseaudio[1446]: ICE default IO error
handler doing an exit(), pid = 1446, errno = 11
Jun 10 06:48:27 symphony trashapplet[1468]: trashapplet: Fatal IO
error 11 (Ressource temporairement non disponible) on X server :0.
Jun 10 06:48:27 symphony systemd[1361]: pulseaudio.service: Main
process exited, code=exited, status=1/FAILURE
Jun 10 06:48:27 symphony systemd[1361]: pulseaudio.service: Failed
with result 'exit-code'.
Jun 10 06:48:27 symphony [1469]: wnck-applet: Fatal IO error 11
(Ressource temporairement non disponible) on X server :0.
Jun 10 06:48:27 symphony mate-multiload-[1559]: mate-multiload-applet:
Fatal IO error 11 (Ressource temporairement non disponible) on X
server :0.
Jun 10 06:48:27 symphony notification-ar[1560]:
notification-area-applet: Fatal IO error 11 (Ressource temporairement
non disponible) on X server :0.
Jun 10 06:48:27 symphony clock-applet[1561]: clock-applet: Fatal IO
error 11 (Ressource temporairement non disponible) on X server :0.
Jun 10 06:48:27 symphony systemd[1361]: pulseaudio.service: Service
hold-off time over, scheduling restart.
Jun 10 06:48:27 symphony systemd[1361]: pulseaudio.service: Scheduled
restart job, restart counter is at 1.
Jun 10 06:48:27 symphony systemd[1361]: Stopped Sound Service.
Jun 10 06:48:27 symphony systemd[1361]: Starting Sound Service...
Jun 10 06:48:27 symphony rtkit-daemon[745]: Successfully made thread
15179 of process 15179 (n/a) owned by '1000' high priority at nice
level -11.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 1 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony pulseaudio[15179]: W: [pulseaudio] pid.c:
Stale PID file, overwriting.
Jun 10 06:48:27 symphony systemd[1]: Stopped Light Display Manager.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 1 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Successfully made thread
15180 of process 15179 (n/a) owned by '1000' RT at priority 5.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 2 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 2 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Successfully made thread
15181 of process 15179 (n/a) owned by '1000' RT at priority 5.
Jun 10 06:48:27 symphony rtkit-daemon[745]: Supervising 3 threads of 1
processes of 1 users.
Jun 10 06:48:27 symphony pulseaudio[15179]: E: [pulseaudio]
bluez5-util.c: GetManagedObjects() failed:
org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2
matched rules; type="method_call", sender=":1.338" (uid=1000 pid=15179
comm="/usr/bin/pulseaudio --daemonize=no ")
interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" error name="(unset)" requested_reply="0"
destination="org.bluez" (bus)
Jun 10 06:48:27 symphony systemd[1361]: Started Sound Service.
(...)
Messages:
Jun 10 06:49:49 symphony NetworkManager[764]: 
[1528627789.7842] caught SIGTERM, shutting down normally.
Jun 10 06:49:49 symphony NetworkManager[764]: 
[1528627789.8243] exiting (success)

(Also in syslog...)
Jun 10 10:37:20 symphony dhclient[18150]: execve
(/usr/lib/NetworkManager/nm-dhcp-helper, ...): No such file or
directory
(...)
Jun 10 16:56:52 symphony kernel: [196727.991463] traps:
mate-settings-d[18477] trap int3 ip:7f4e5abb1c41 sp:7ffcaa1aa750
error:0 in libglib-2.0.so.0.5600.1[7f4e5ab6+113000]
Jun 10 16:56:53 symphony kernel: [196728.900334] traps:
mate-settings-d[18495] trap int3 ip:7f2a4f869c41 sp:7ffe5a9e7d00
error:0 in libglib-2.0.so.0.5600.1[7f2a4f818000+113000]
Jun 10 16:56:54 symphony wnck-applet[18502]: g_object_set: assertion
'G_IS_OBJECT (object)' failed
Jun 10 16:56:54 symphony clock-applet[18575]: Negative content width
-1 (allocation 1, extents 1x1) while allocating gadget (node button,
owner GtkToggleButton)
Jun 10 16:56:56 symphony notification-ar[18576]:
GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object
path '/NO_DBUSMENU'

Bug#898468: marked as done (debian-installer: black screen/long delay in graphical installer after switching from linux 4.15 to 4.16)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 22:04:54 +
with message-id 
and subject line Bug#898468: fixed in debian-installer 20180610
has caused the Debian Bug report #898468,
regarding debian-installer: black screen/long delay in graphical installer 
after switching from linux 4.15 to 4.16
to be marked as done.

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

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


-- 
898468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Severity: serious
Justification: graphical installer regression

Hi,

Ever since we switched from linux 4.15 to 4.16, the graphical installer
gets a black screen. Comparing Xorg logs, everything is exactly the same
except for the kernel version and timestamps. syslog has extra lines
about random stuff:

May 12 02:25:01 init: starting pid 169, tty '': '/sbin/reopen-console 
/sbin/debian-installer'
May 12 02:25:01 init: starting pid 172, tty '/dev/tty4': '/usr/bin/tail -f 
/var/log/syslog'
May 12 02:25:02 init: process '/sbin/reopen-console /sbin/debian-installer' 
(pid 169) exited. Scheduling for restart.
May 12 02:25:02 init: starting pid 201, tty '': '/sbin/reopen-console 
/sbin/debian-installer'
May 12 02:25:02 kernel: [3.302164] random: debconf: uninitialized 
urandom read (8 bytes read)
May 12 02:25:02 kernel: [3.302291] random: debconf: uninitialized 
urandom read (8 bytes read)
May 12 02:25:02 kernel: [3.302351] random: debconf: uninitialized 
urandom read (8 bytes read)
May 12 02:25:02 kernel: [3.302450] random: debconf: uninitialized 
urandom read (8 bytes read)
May 12 02:25:02 kernel: [3.302530] random: debconf: uninitialized 
urandom read (8 bytes read)
May 12 02:25:02 kernel: [3.302682] random: debconf: uninitialized 
urandom read (8 bytes read)
May 12 02:25:02 kernel: [3.302804] random: debconf: uninitialized 
urandom read (8 bytes read)
May 12 02:25:02 kernel: [3.302963] random: debconf: uninitialized 
urandom read (8 bytes read)
May 12 02:25:02 kernel: [3.303009] random: debconf: uninitialized 
urandom read (8 bytes read)
May 12 02:25:02 kernel: [3.303078] random: debconf: uninitialized 
urandom read (8 bytes read)

   
^^

May 12 02:25:19 init: starting pid 170, tty '/dev/tty2': '-/bin/sh'
May 12 02:25:21 debconf: Setting debconf/language to en
May 12 02:25:21 main-menu[229]: DEBUG: resolver (libgcc1): package doesn't 
exist (ignored)
May 12 02:25:21 main-menu[229]: INFO: Falling back to the package 
description for brltty-udeb
May 12 02:25:21 main-menu[229]: INFO: Menu item 'localechooser' selected
May 12 02:25:22 debconf: Setting debconf/language to en
May 12 02:25:22 gtk-set-font: Switching to font 'DejaVu Sans' for 'en'
May 12 02:25:24 kernel: [   25.303708] random: crng init done

After a while, this happens:   ^^

Once that has happened (so after 20+ seconds), the screen comes up
properly without any intervention. I think I've seen reports on
#debian-kernel about boot stuff like plymouth/cryptsetup having issues
gathering entropy at the early stages of the boot sequence, but I'm not
sure that's a regression in the kernel, and/or something that should be
dealt with from within cdebconf.

That's why I'm filing this bug report for the time being, feel free to
mention actual bug reports on the kernel side, and to suggest ways to go
from here (I haven't followed that quite closely).

I've X-D-Cc'd debian-kernel@ as their input is more than welcome.

Interestingly, the text installer is working just fine so I guess it's
something frontend-specific (some X11 fun?), but I won't dig into that
right away.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: debian-installer
Source-Version: 20180610

We believe that the bug you reported is fixed in the latest version of
debian-installer, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 898...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated 

Bug#898024: [Pkg-javascript-devel] Bug#898024: Bug#898024: trying to overwrite '/usr/include/nodejs/common.gypi', which is also in package nodejs-dev 10.0.0~dfsg-2

[Jonas Smedegaard]

Quoting Jérémy Lal (2018-06-10 22:04:43)
> 2018-06-10 20:14 GMT+02:00 Jonas Smedegaard :
> > Quoting Jérémy Lal (2018-06-10 16:51:14)
> > > 2018-06-10 10:26 GMT+02:00 Andreas Beckmann :
> > > > The 8 -> 10 upgrade path does not work either:
> > > >
> > > >   Selecting previously unselected package libnode64-dev.
> > > >   Preparing to unpack .../libnode64-dev_10.3.0~dfsg-1_amd64.deb ...
> > > >   Unpacking libnode64-dev (10.3.0~dfsg-1) ...
> > > >   dpkg: error processing archive 
> > > > /var/cache/apt/archives/libnode64-dev_10.3.0~dfsg-1_amd64.deb 
> > > > (--unpack):
> > > >trying to overwrite '/usr/include/nodejs/common.gypi', which is also 
> > > > in package nodejs-dev 8.11.2~dfsg-1
> > > >   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> > > >   Errors were encountered while processing:
> > > >/var/cache/apt/archives/libnode64-dev_10.3.0~dfsg-1_amd64.deb
> > > >
> > > > You probably need to add
> > > >   Breaks+Replaces: nodejs-dev (<< 10.0.0~dfsg1-3)
> > > > to libnode64-dev for properly taking over /usr/include/nodejs/*
> > > >
> > >
> > > Hi Jonas,
> > >
> > > to do it i'm trying
> > > CDBS_BREAKS_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
> > > CDBS_REPLACES_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
> > >
> > > but it does not generate the expected fields.
> > > Did i make some mistake here ?
> >
> > Sorry, I don't locate those strings - which branch of which git are 
> > you trying out the above?
> >
> > It looks correct - but works only in concert with corresponding 
> > hints in control{.in.in} file.  See e.g. git commit f31d94a (i.e. 
> > _reverse_ of that, and adding Replaces: ${cdbs:Replaces}).
> >
> 
> i did not push it because it's w.i.p.
> and yet you're right, i forgot those hints. Thanks !

Good.  Please do ping me if there are any other issues you want me to 
investigate!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#901185: Checkbashisms

[積丹尼 Dan Jacobson]

I also note /etc/exim4/update-exim4.conf.conf got overwritten without
asking the user Y/N.
I also note exim4-config contains #!/bin/bash scripts without Depends: bash.

D>  Be sure the package passes Checkbashisms!

JN> Which package? Is there a particular bashism you noticed?

All the shell scripts in the exim* packages.

Anyway please declare a Conflict with bash5, or better yet make the
package finally installable. Thank you.

Bug#897242: marked as done (chromium: FTBFS on armhf: linker runs out of memory)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 17:03:38 -0400
with message-id 

and subject line Re: Bug#897242: chromium: FTBFS on armhf: linker runs out of 
memory
has caused the Debian Bug report #897242,
regarding chromium: FTBFS on armhf: linker runs out of memory
to be marked as done.

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

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


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

Hi,

As you know, chromium has been failing to build on armhf for a while now.
That's specially bad as it's blocking testing migration, causing testing
users to run a pretty old version with several security vulnerabilities.

I see that you've tried to make it build there again (without much success).

I would suggest to try with -Wl,--no-keep-memory (which may not be very
effective with ld.gold though), -Wl,-O1 or -Wl,-O0 (rather than the current
-Wl,-O2).

You tried to disable debug symbols, but since the build logs are silent I
don't know if the code is still compiling with -g.

Thanks for looking at this,
Emilio
--- End Message ---
--- Begin Message ---
version: 67.0.3396.62-2--- End Message ---

Bug#897242:

[Michael Gilbert]

version: 67.0.3396.62-2

Bug#901252: marked as done (vlc: Fail to launch, QPainter not active)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 22:11:33 +0200
with message-id <20180610201133.ga9...@ramacher.at>
and subject line Re: Bug#901252: vlc: Fail to launch, QPainter not active
has caused the Debian Bug report #901252,
regarding vlc: Fail to launch, QPainter not active
to be marked as done.

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

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


-- 
901252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vlc
Version: 3
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

I upgraded to VLC3 from Synaptic's Mark All Updates option, the bug started
here.

I ran a complete purge of all VLC packages and reinstall via rebuild from
source.

No results, bug persisted



-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 2018-06-10 18:31:31, John Hendricks wrote:
>  This is a little more complicated than I had anticipated. So nevermind, 
> sorry to waste your time.

When you find the time to provide the data, we can still try to figure out the
problem. It appears that you also reported the issue upstream
(https://forum.videolan.org/viewtopic.php?t=144738). The log there suggests that
you have a git version of vlc installed somehow (VLC media player 4.0.0-dev Otto
Chriek (revision 4.0.0-dev-3262-g5a59782d45)). So this is nothing we can fix.

Cheers

> On Sunday, June 10, 2018, 2:15:25 PM EDT, Sebastian Ramacher 
>  wrote:  
>  
>  [Please keep the bug in CC]
> 
> On 2018-06-10 17:50:20, John Hendricks wrote:
> > I apologize, this is the first bug report I've ever filed. I'm not sure 
> > where VLC keeps the log file, so I will attach the output of vlc -vvv in a 
> > text file.
> > I am unable to produce output from the given reportbug -n command. Anything 
> > I can do to help just please let me know and please be patient with me, I 
> > will do whatever I can.
> 
> Please start a new bug report against vlc, copy the complete dependency
> information and send it to this report.
> 
> For the log, please run vlc as:
> 
> vlc -vv >log.txt 2>&1
> 
> and then attach log.txt.
> 
> Cheers
> 
> > 
> >    On Sunday, June 10, 2018, 12:39:33 PM EDT, Sebastian Ramacher 
> > wrote:  
> >  
> >  Control: tags -1 + moreinfo unpreoducible
> > 
> > Hi
> > 
> > On 2018-06-10 11:52:47, John Hendricks wrote:
> > > Source: vlc
> > > Version: 3
> > > Severity: grave
> > > Tags: upstream
> > > Justification: renders package unusable
> > > 
> > > Dear Maintainer,
> > > 
> > > I upgraded to VLC3 from Synaptic's Mark All Updates option, the bug 
> > > started
> > > here.
> > > 
> > > I ran a complete purge of all VLC packages and reinstall via rebuild from
> > > source.
> > > 
> > > No results, bug persisted
> > 
> > This bug lacks many details which make this report unactionable. Please, 
> > while
> > having vlc installed, run reportbug -N NN vlc (replace the bug number 
> > with
> > the number of this bug) and let us know all the data that reportbug 
> > generates
> > (dependencies and versions, correct vlc version and so on). Also, please
> > reproduce the problem using vlc -vvv and attach the log output to the bug
> > report.
> > 
> > Cheers
> > 
> > > 
> > > 
> > > 
> > > -- System Information:
> > > Debian Release: 9.4
> > >  APT prefers stable-updates
> > >  APT policy: (500, 'stable-updates'), (500, 'stable')
> > > Architecture: i386 (i686)
> > > 
> > > Kernel: Linux 4.9.0-3-686-pae (SMP w/4 CPU cores)
> > > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
> > > LANGUAGE=en_US.utf8 (charmap=UTF-8)
> > > Shell: /bin/sh linked to /bin/dash
> > > Init: systemd (via /run/systemd/system)
> > > 
> > > ___
> > > pkg-multimedia-maintainers mailing list
> > > pkg-multimedia-maintain...@alioth-lists.debian.net
> > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
> > 
> > -- 
> > Sebastian Ramacher  
> 
> 
> 
> -- 
> Sebastian Ramacher  

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---

Bug#898024: [Pkg-javascript-devel] Bug#898024: Bug#898024: trying to overwrite '/usr/include/nodejs/common.gypi', which is also in package nodejs-dev 10.0.0~dfsg-2

[Jérémy Lal]

2018-06-10 20:14 GMT+02:00 Jonas Smedegaard :

> Hi Jérémy,
>
> Quoting Jérémy Lal (2018-06-10 16:51:14)
> > 2018-06-10 10:26 GMT+02:00 Andreas Beckmann :
> > > The 8 -> 10 upgrade path does not work either:
> > >
> > >   Selecting previously unselected package libnode64-dev.
> > >   Preparing to unpack .../libnode64-dev_10.3.0~dfsg-1_amd64.deb ...
> > >   Unpacking libnode64-dev (10.3.0~dfsg-1) ...
> > >   dpkg: error processing archive /var/cache/apt/archives/
> libnode64-dev_10.3.0~dfsg-1_amd64.deb (--unpack):
> > >trying to overwrite '/usr/include/nodejs/common.gypi', which is
> also in package nodejs-dev 8.11.2~dfsg-1
> > >   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> > >   Errors were encountered while processing:
> > >/var/cache/apt/archives/libnode64-dev_10.3.0~dfsg-1_amd64.deb
> > >
> > > You probably need to add
> > >   Breaks+Replaces: nodejs-dev (<< 10.0.0~dfsg1-3)
> > > to libnode64-dev for properly taking over /usr/include/nodejs/*
> > >
> >
> > Hi Jonas,
> >
> > to do it i'm trying
> > CDBS_BREAKS_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
> > CDBS_REPLACES_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
> >
> > but it does not generate the expected fields.
> > Did i make some mistake here ?
>
> Sorry, I don't locate those strings - which branch of which git are you
> trying out the above?
>
> It looks correct - but works only in concert with corresponding hints in
> control{.in.in} file.  See e.g. git commit f31d94a (i.e. _reverse_ of
> that, and adding Replaces: ${cdbs:Replaces}).
>

i did not push it because it's w.i.p.
and yet you're right, i forgot those hints. Thanks !

Jérémy

Bug#901113: marked as done (pyro: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 19:53:24 +
with message-id 
and subject line Bug#901113: fixed in pyro 1:3.16-3
has caused the Debian Bug report #901113,
regarding pyro: FTBFS when built with dpkg-buildpackage -A
to be marked as done.

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

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


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
This makefile is only for cleaning stuff up. ('make clean')
You can also build the tarball dist with it ('make sdist')
You can also build the win32 binary dist with it ('make windist')
make[1]: Leaving directory '/<>'
   dh_auto_test -i
   create-stamp debian/debhelper-build-stamp

[... snipped ...]

copying build/scripts-2.7/pyro-ns -> /<>/debian/tmp/usr/local/bin
copying build/scripts-2.7/pyro-nsd -> /<>/debian/tmp/usr/local/bin
copying build/scripts-2.7/pyro-es -> /<>/debian/tmp/usr/local/bin
copying build/scripts-2.7/pyro-wxnsc -> 
/<>/debian/tmp/usr/local/bin
changing mode of /<>/debian/tmp/usr/local/bin/pyro-genguid to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-nsc to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-esd to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-xnsc to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-ns to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-nsd to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-es to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-wxnsc to 775
running install_egg_info
Writing 
/<>/debian/tmp/usr/local/lib/python2.7/dist-packages/Pyro-3.16.egg-info
mv debian/tmp/usr/local/lib debian/tmp/usr/lib
dh_install -ppyro -Xwxnsc.py -Xxnsc.py
dh_install: Cannot find (any matches for) "usr/bin/pyro-es" (tried in ., 
debian/tmp)

dh_install: pyro missing files: usr/bin/pyro-es
dh_install: Cannot find (any matches for) "usr/bin/pyro-genguid" (tried in ., 
debian/tmp)

dh_install: pyro missing files: usr/bin/pyro-genguid
dh_install: Cannot find (any matches for) "usr/bin/pyro-ns" (tried in ., 
debian/tmp)

dh_install: pyro missing files: usr/bin/pyro-ns
dh_install: Cannot find (any matches for) "usr/bin/pyro-nsc" (tried in ., 
debian/tmp)

dh_install: pyro missing files: usr/bin/pyro-nsc
dh_install: Cannot find (any matches for) "usr/bin/pyro-esd" (tried in ., 
debian/tmp)

dh_install: pyro missing files: usr/bin/pyro-esd
dh_install: Cannot find (any matches for) "usr/bin/pyro-nsd" (tried in ., 
debian/tmp)

dh_install: pyro missing files: usr/bin/pyro-nsd
dh_install: missing files, aborting
install -d debian/.debhelper/generated/pyro
install -d debian/.debhelper/generated/pyro-gui
install -d debian/.debhelper/generated/pyro-doc
install -d debian/.debhelper/generated/pyro-examples
debian/rules:27: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 25
make[1]: Leaving directory '/<>'
debian/rules:12: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_install into override_dh_install-indep and 
override_dh_install-arch.

Thanks.
--- End Message ---
--- Begin Message ---
Source: pyro
Source-Version: 1:3.16-3

We believe that the bug you reported is fixed in the latest version of
pyro, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated pyro package)

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


-BEGIN PGP SIGNED MESSAGE-

Bug#901119: marked as done (yodl: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 19:54:01 +
with message-id 
and subject line Bug#901119: fixed in yodl 4.02.00-3
has caused the Debian Bug report #901119,
regarding yodl: FTBFS when built with dpkg-buildpackage -A
to be marked as done.

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

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


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
./build manual
mkdir -p tmp/wip
mkdir -p tmp/install
mkdir -p tmp/install/usr/share/doc/yodl-doc
tmp/install/usr/bin/yodl -I.:tmp/wip:tmp/wip/macros:manual -otmp/wip/out html 
manual
sh: 1: tmp/install/usr/bin/yodl: not found
Fatal: system - failure of system call (status 32512)
debian/rules:39: recipe for target 'override_dh_auto_build-indep' failed
make[1]: *** [override_dh_auto_build-indep] Error 1
make[1]: Leaving directory '/<>'
debian/rules:25: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


To reproduce, please try "dpkg-buildpackage -A".
(The error does not happen with "dpkg-buildpackage").

Thanks.
--- End Message ---
--- Begin Message ---
Source: yodl
Source-Version: 4.02.00-3

We believe that the bug you reported is fixed in the latest version of
yodl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated yodl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Jun 2018 12:27:44 -0700
Source: yodl
Binary: yodl yodl-doc
Architecture: source amd64 all
Version: 4.02.00-3
Distribution: unstable
Urgency: medium
Maintainer: Frank B. Brokken 
Changed-By: tony mancill 
Description:
 yodl   - Your Own Document Language (Yodl) is a pre-document language
 yodl-doc   - Documentation for Your Own Document Language (Yodl)
Closes: 901119
Changes:
 yodl (4.02.00-3) unstable; urgency=medium
 .
   * Update Vcs fields for migration from Alioth -> Salsa
   * Update for upstream migration from github to gitlab
   * Bump Standards-Version to 4.1.4
   * Use debhelper 11
   * Address dpkg-buildpackage -A failure (Closes: #901119)
Checksums-Sha1:
 cac1b5950d3c185fb5c038fcf6f664615b5f838b 2146 yodl_4.02.00-3.dsc
 ac8c1a7d21b00d982c061dfc40c8d82a1e283c7d 11188 yodl_4.02.00-3.debian.tar.xz
 13a602a1f344126da05c506eb5a88cb5738e7a39 1026168 
yodl-dbgsym_4.02.00-3_amd64.deb
 792a9564f3c638d6e126ddabae6ebee84730b455 1570440 yodl-doc_4.02.00-3_all.deb
 0daa33cee860d90dbf3dcc4de7cd4bc5fbe49822 8893 yodl_4.02.00-3_amd64.buildinfo
 68ff2721365c26d797706f0c7b027d99947ef432 210652 yodl_4.02.00-3_amd64.deb
Checksums-Sha256:
 fa631acf42fd58c2639cd25816d33fa98a08d047b2abbc35e596cd828a3b4121 2146 
yodl_4.02.00-3.dsc
 3bd43967f040af2989d017f94d39929867de03ad814aa2847c4541aec2b95bb6 11188 
yodl_4.02.00-3.debian.tar.xz
 c2ffeb1d65d9c936eab4c936db960990ffaf424ce81d5582afd8828a5a68df91 1026168 
yodl-dbgsym_4.02.00-3_amd64.deb
 1928989eefdfd677cf06edb427ef9334caffbf1d400318351ee21272c37398ed 1570440 
yodl-doc_4.02.00-3_all.deb
 6854b9cf3edafeec08e3ae48fe2be743e531a43f95cc549b7136aa75f29a1e2d 8893 
yodl_4.02.00-3_amd64.buildinfo
 846367ccffb6fb9661487b78221c482b3fbe836d38421348bd4c7ad81509fb2a 210652 
yodl_4.02.00-3_amd64.deb
Files:
 b27ee023a3691e8b01fd305429dd4c9b 2146 text optional yodl_4.02.00-3.dsc
 31a06b9e0892cf344e76ef89dd14904b 11188 text optional 
yodl_4.02.00-3.debian.tar.xz
 04dc2953b63cfc0fd3c4b5e847776d37 1026168 debug optional 
yodl-dbgsym_4.02.00-3_amd64.deb
 6a3f210949fc17a3dd6526b74a0b942f 1570440 doc optional 
yodl-doc_4.02.00-3_all.deb
 

Bug#898024: [Pkg-javascript-devel] Bug#898024: Bug#898024: trying to overwrite '/usr/include/nodejs/common.gypi', which is also in package nodejs-dev 10.0.0~dfsg-2

[Jonas Smedegaard]

Hi Jérémy,

Quoting Jérémy Lal (2018-06-10 16:51:14)
> 2018-06-10 10:26 GMT+02:00 Andreas Beckmann :
> > The 8 -> 10 upgrade path does not work either:
> >
> >   Selecting previously unselected package libnode64-dev.
> >   Preparing to unpack .../libnode64-dev_10.3.0~dfsg-1_amd64.deb ...
> >   Unpacking libnode64-dev (10.3.0~dfsg-1) ...
> >   dpkg: error processing archive 
> > /var/cache/apt/archives/libnode64-dev_10.3.0~dfsg-1_amd64.deb (--unpack):
> >trying to overwrite '/usr/include/nodejs/common.gypi', which is also in 
> > package nodejs-dev 8.11.2~dfsg-1
> >   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> >   Errors were encountered while processing:
> >/var/cache/apt/archives/libnode64-dev_10.3.0~dfsg-1_amd64.deb
> >
> > You probably need to add
> >   Breaks+Replaces: nodejs-dev (<< 10.0.0~dfsg1-3)
> > to libnode64-dev for properly taking over /usr/include/nodejs/*
> >
> 
> Hi Jonas,
> 
> to do it i'm trying
> CDBS_BREAKS_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
> CDBS_REPLACES_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
> 
> but it does not generate the expected fields.
> Did i make some mistake here ?

Sorry, I don't locate those strings - which branch of which git are you 
trying out the above?

It looks correct - but works only in concert with corresponding hints in 
control{.in.in} file.  See e.g. git commit f31d94a (i.e. _reverse_ of 
that, and adding Replaces: ${cdbs:Replaces}).


Hope that helps,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#901252: vlc: Fail to launch, QPainter not active

[Sebastian Ramacher]

[Please keep the bug in CC]

On 2018-06-10 17:50:20, John Hendricks wrote:
> I apologize, this is the first bug report I've ever filed. I'm not sure where 
> VLC keeps the log file, so I will attach the output of vlc -vvv in a text 
> file.
> I am unable to produce output from the given reportbug -n command. Anything I 
> can do to help just please let me know and please be patient with me, I will 
> do whatever I can.

Please start a new bug report against vlc, copy the complete dependency
information and send it to this report.

For the log, please run vlc as:

vlc -vv >log.txt 2>&1

and then attach log.txt.

Cheers

> 
> On Sunday, June 10, 2018, 12:39:33 PM EDT, Sebastian Ramacher 
>  wrote:  
>  
>  Control: tags -1 + moreinfo unpreoducible
> 
> Hi
> 
> On 2018-06-10 11:52:47, John Hendricks wrote:
> > Source: vlc
> > Version: 3
> > Severity: grave
> > Tags: upstream
> > Justification: renders package unusable
> > 
> > Dear Maintainer,
> > 
> > I upgraded to VLC3 from Synaptic's Mark All Updates option, the bug started
> > here.
> > 
> > I ran a complete purge of all VLC packages and reinstall via rebuild from
> > source.
> > 
> > No results, bug persisted
> 
> This bug lacks many details which make this report unactionable. Please, while
> having vlc installed, run reportbug -N NN vlc (replace the bug number with
> the number of this bug) and let us know all the data that reportbug generates
> (dependencies and versions, correct vlc version and so on). Also, please
> reproduce the problem using vlc -vvv and attach the log output to the bug
> report.
> 
> Cheers
> 
> > 
> > 
> > 
> > -- System Information:
> > Debian Release: 9.4
> >  APT prefers stable-updates
> >  APT policy: (500, 'stable-updates'), (500, 'stable')
> > Architecture: i386 (i686)
> > 
> > Kernel: Linux 4.9.0-3-686-pae (SMP w/4 CPU cores)
> > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
> > LANGUAGE=en_US.utf8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> > 
> > ___
> > pkg-multimedia-maintainers mailing list
> > pkg-multimedia-maintain...@alioth-lists.debian.net
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
> 
> -- 
> Sebastian Ramacher  



-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#901185: Checkbashisms

[Jonathan Nieder]

Hi,

積丹尼 wrote:

Be sure the package passes Checkbashisms!
>

Which package? Is there a particular bashism you noticed?

Please keep in mind that these reports appear as emails in a crowded inbox,
where a little context in the subject line can go a long way.

Thanks,
Jonathan

>

Bug#899486: marked as done (electrum: Invalid maintainer address pkg-bitcoin-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 17:50:31 +
with message-id 
and subject line Bug#899486: fixed in electrum 3.1.3-1
has caused the Debian Bug report #899486,
regarding electrum: Invalid maintainer address 
pkg-bitcoin-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of electrum,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: electrum
Source-Version: 3.1.3-1

We believe that the bug you reported is fixed in the latest version of
electrum, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tristan Seligmann  (supplier of updated electrum package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Jun 2018 19:24:45 +0200
Source: electrum
Binary: python3-electrum electrum
Architecture: source
Version: 3.1.3-1
Distribution: unstable
Urgency: medium
Maintainer: Tristan Seligmann 
Changed-By: Tristan Seligmann 
Description:
 electrum   - Easy to use Bitcoin client
 python3-electrum - Easy to use Bitcoin client - Python module
Closes: 899486
Changes:
 electrum (3.1.3-1) unstable; urgency=medium
 .
   * Update maintainer address (I am effectively the sole maintainer);
 closes: #899486.
   * Move git repository to Salsa.
   * New upstream release.
 - Drop patches (applied upstream).
   * Bump Standards-Version to 4.1.4 (no changes).
Checksums-Sha1:
 616a4018f485a4cf788e4cd0fb8f2d354db59cd7 1963 electrum_3.1.3-1.dsc
 ae284c31053a4df1849eb56889ca041a5bf3a453 2806178 electrum_3.1.3.orig.tar.gz
 0498aeff68bebe49b71e2b2b133be6a934d65b1b 13312 electrum_3.1.3-1.debian.tar.xz
 582d26f51c1da5dcd30c2df834436bfa1ea5d6fc 10602 
electrum_3.1.3-1_source.buildinfo
Checksums-Sha256:
 51974a97acb47e19812a133d4ec8feb9b4935ffa9d6e2c04e01e83f9baee7cd3 1963 
electrum_3.1.3-1.dsc
 3e5aedb52184f2237eb81194539f27b148045e266e46aca0e42ae53f9a47a216 2806178 
electrum_3.1.3.orig.tar.gz
 d0e8300a5a65414ffa928fa68224409533f480d6de91c2066cf2c9501d6e64c8 

Bug#900652: marked as forwarded (guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets called)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 12:32:11 -0500
with message-id <874liar1ic@trouble.defaultvalue.org>
has caused the   report #900652,
regarding guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets 
called
to be marked as having been forwarded to the upstream software
author(s) bug-gu...@gnu.org

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


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

It looks like gc.test may be failing intermittently in Debian (see below).
Searching around I saw at least one other report of this in the #guile
logs from last year.

For now, I'm wondering if if would be plausible to mark the test as
unresolved to avoid guile-2.2's removal from Debian testing, or if the
failure is likely to indicate a problem serious enough to warrant that
removal.

Emilio Pozuelo Monfort  writes:

> Your package failed to build on armhf:
>
> Running gc.test
> FAIL: gc.test: gc: after-gc-hook gets called
> [...]
> Totals for this test run:
> passes: 40732
> failures:   1
> unexpected passes:  0
> expected failures:  10
> unresolved test cases:  578
> untested test cases:1
> unsupported test cases: 1
> errors: 0
>
> FAIL: check-guile
> ==
> 1 of 1 test failed
>
>
> Full log at https://buildd.debian.org/status/package.php?p=guile-2.2

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4--- End Message ---

Bug#900652: guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets called

[Rob Browning]

It looks like gc.test may be failing intermittently in Debian (see below).
Searching around I saw at least one other report of this in the #guile
logs from last year.

For now, I'm wondering if if would be plausible to mark the test as
unresolved to avoid guile-2.2's removal from Debian testing, or if the
failure is likely to indicate a problem serious enough to warrant that
removal.

Emilio Pozuelo Monfort  writes:

> Your package failed to build on armhf:
>
> Running gc.test
> FAIL: gc.test: gc: after-gc-hook gets called
> [...]
> Totals for this test run:
> passes: 40732
> failures:   1
> unexpected passes:  0
> expected failures:  10
> unresolved test cases:  578
> untested test cases:1
> unsupported test cases: 1
> errors: 0
>
> FAIL: check-guile
> ==
> 1 of 1 test failed
>
>
> Full log at https://buildd.debian.org/status/package.php?p=guile-2.2

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#895482: severity 895482 important

[Michael Shuler]

severity 895482 important
thanks

Dropped severity to allow testing migration.

--
Michael

Processed: severity 895482 important

[Debian Bug Tracking System]

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

> severity 895482 important
Bug #895482 [ca-certificates] Fails to upgrade: installed ca-certificates 
package post-installation script subprocess returned error exit status 4
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#901106: marked as done (eccodes: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 16:50:35 +
with message-id 
and subject line Bug#901106: fixed in eccodes 2.7.3-3
has caused the Debian Bug report #901106,
regarding eccodes: FTBFS when built with dpkg-buildpackage -A
to be marked as done.

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

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


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=cmake --with=python3,fortran_mod 
--builddirectory=/<>/debian/build --no-parallel
   dh_update_autotools_config -i -O--buildsystem=cmake 
-O--builddirectory=/<>/debian/build
   dh_autoreconf -i -O--buildsystem=cmake 
-O--builddirectory=/<>/debian/build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
F77=gfortran-8 dh_auto_configure -- \
-DCMAKE_BUILD_TYPE=Release -DDISABLE_OS_CHECK=ON 
-DENABLE_INSTALL_ECCODES_DEFINITIONS=ON -DENABLE_INSTALL_ECCODES_SAMPLES=ON 
-DENABLE_PNG=ON -DENABLE_AEC=ON -DENABLE_RPATHS=OFF 
-DENABLE_RELATIVE_RPATHS=OFF -DENABLE_MEMFS=ON -DHAVE_BIT_REPRODUCIBLE=ON 
-DCMAKE_C_CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wl,-z,relro" -DENABLE_ALIGN_MEMORY=ON 
-DENABLE_GRIB_TIMER=ON -DENABLE_ECCODES_OMP_THREADS=On -DENABLE_PYTHON=ON 
-DPYTHON_EXECUTABLE=/usr/bin/python3 
install -d debian/build
cd debian/build && cmake ../.. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_BUILD_TYPE=Release -DDISABLE_OS_CHECK=ON 
-DENABLE_INSTALL_ECCODES_DEFINITIONS=ON -DENABLE_INSTALL_ECCODES_SAMPLES=ON 
-DENABLE_PNG=ON -DENABLE_AEC=ON -DENABLE_RPATHS=OFF 
-DENABLE_RELATIVE_RPATHS=OFF -DENABLE_MEMFS=ON -DHAVE_BIT_REPRODUCIBLE=ON 
"-DCMAKE_C_CFLAGS=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wl,-z,relro" -DENABLE_ALIGN_MEMORY=ON 
-DENABLE_GRIB_TIMER=ON -DENABLE_ECCODES_OMP_THREADS=On -DENABLE_PYTHON=ON 
-DPYTHON_EXECUTABLE=/usr/bin/python3
-- The C compiler identification is GNU 7.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info

[... snipped ...]

(grep -a -s -v python3:Depends debian/libeccodes-data.substvars; echo 
python3:Depends=python3-numpy) > debian/libeccodes-data.substvars.new
mv debian/libeccodes-data.substvars.new debian/libeccodes-data.substvars
(grep -a -s -v python3:Depends debian/libeccodes-doc.substvars; echo 
python3:Depends=python3-numpy) > debian/libeccodes-doc.substvars.new
mv debian/libeccodes-doc.substvars.new debian/libeccodes-doc.substvars
dh_install
install -d debian/.debhelper/generated/libeccodes0
install -d debian/libeccodes-data//usr/share/eccodes
cp --reflink=auto -a debian/tmp/usr/share/eccodes/definitions 
debian/tmp/usr/share/eccodes/samples debian/libeccodes-data//usr/share/eccodes/
install -d debian/.debhelper/generated/libeccodes-data
install -d debian/.debhelper/generated/libeccodes-dev
install -d debian/.debhelper/generated/libeccodes-tools
install -d debian/.debhelper/generated/python3-eccodes
install -d debian/.debhelper/generated/libeccodes-doc
#
# Setup cmake files for magics++, metview, etc.
#
mkdir -p debian/libeccodes-dev//usr/lib/x86_64-linux-gnu/cmake/eccodes
cp debian/tmp/usr/share/eccodes/cmake/* 
debian/libeccodes-dev//usr/lib/x86_64-linux-gnu/cmake/eccodes
sed -e 's%${_IMPORT_PREFIX}%/usr%' \
   < debian/tmp/usr/share/eccodes/cmake/eccodes-targets-release.cmake | \
sed -e 's%-lpython3.6 %%g' | \
sed -e 's%/usr/lib/libeccodes%/usr/lib/x86_64-linux-gnu/libeccodes%' | \
sed -e 's%/usr/lib/x86_64-linux-gnu/libopenjpeg.so;%%' | sed -e 
's%;/usr/lib/x86_64-linux-gnu/libpng.so%%g' \
  > 
debian/libeccodes-dev//usr/lib/x86_64-linux-gnu/cmake/eccodes/eccodes-targets-release.cmake
sed -e 's%;/usr/lib/x86_64-linux-gnu/libopenjpeg.so%%g' \
< debian/tmp/usr/share/eccodes/cmake/eccodes-config.cmake | \
sed -e 's%-lpython3.6 %%g' | \
sed -s 

Bug#901252: vlc: Fail to launch, QPainter not active

[Sebastian Ramacher]

Control: tags -1 + moreinfo unpreoducible

Hi

On 2018-06-10 11:52:47, John Hendricks wrote:
> Source: vlc
> Version: 3
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> I upgraded to VLC3 from Synaptic's Mark All Updates option, the bug started
> here.
> 
> I ran a complete purge of all VLC packages and reinstall via rebuild from
> source.
> 
> No results, bug persisted

This bug lacks many details which make this report unactionable. Please, while
having vlc installed, run reportbug -N NN vlc (replace the bug number with
the number of this bug) and let us know all the data that reportbug generates
(dependencies and versions, correct vlc version and so on). Also, please
reproduce the problem using vlc -vvv and attach the log output to the bug
report.

Cheers

> 
> 
> 
> -- System Information:
> Debian Release: 9.4
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 4.9.0-3-686-pae (SMP w/4 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
> LANGUAGE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed (with 1 error): Re: Bug#901252: vlc: Fail to launch, QPainter not active

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo unpreoducible
Unknown tag/s: unpreoducible.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore.

Bug #901252 [src:vlc] vlc: Fail to launch, QPainter not active
Added tag(s) moreinfo.

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

Bug#901252: vlc: Fail to launch, QPainter not active

[John Hendricks]

Source: vlc
Version: 3
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

I upgraded to VLC3 from Synaptic's Mark All Updates option, the bug started
here.

I ran a complete purge of all VLC packages and reinstall via rebuild from
source.

No results, bug persisted



-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

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

Bug#898024: [Pkg-javascript-devel] Bug#898024: trying to overwrite '/usr/include/nodejs/common.gypi', which is also in package nodejs-dev 10.0.0~dfsg-2

[Jérémy Lal]

2018-06-10 10:26 GMT+02:00 Andreas Beckmann :

> Followup-For: Bug #898024
> Control: found -1 10.3.0~dfsg-1
> Control: severity -1 serious
>
> The 8 -> 10 upgrade path does not work either:
>
>   Selecting previously unselected package libnode64-dev.
>   Preparing to unpack .../libnode64-dev_10.3.0~dfsg-1_amd64.deb ...
>   Unpacking libnode64-dev (10.3.0~dfsg-1) ...
>   dpkg: error processing archive /var/cache/apt/archives/
> libnode64-dev_10.3.0~dfsg-1_amd64.deb (--unpack):
>trying to overwrite '/usr/include/nodejs/common.gypi', which is also
> in package nodejs-dev 8.11.2~dfsg-1
>   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
>   Errors were encountered while processing:
>/var/cache/apt/archives/libnode64-dev_10.3.0~dfsg-1_amd64.deb
>
> You probably need to add
>   Breaks+Replaces: nodejs-dev (<< 10.0.0~dfsg1-3)
> to libnode64-dev for properly taking over /usr/include/nodejs/*
>

Hi Jonas,

to do it i'm trying
CDBS_BREAKS_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)
CDBS_REPLACES_libnode$(ABI)-dev = nodejs-dev (<< 10.0.0~dfsg1-3)

but it does not generate the expected fields.
Did i make some mistake here ?

Jérémy

Processed: retitle 901243 to mate-indicator-applet got removed from buster due to ido build dependency

[Debian Bug Tracking System]

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

> retitle 901243 mate-indicator-applet got removed from buster due to ido build 
> dependency
Bug #901243 [src:mate-indicator-applet] mate-indicator-applet got removed from 
buster due to (spurious?) ido build dependency
Changed Bug title to 'mate-indicator-applet got removed from buster due to ido 
build dependency' from 'mate-indicator-applet got removed from buster due to 
(spurious?) ido build dependency'.
> thanks
Stopping processing here.

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

Processed: affects 901185

[Debian Bug Tracking System]

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

> affects 901185 exim4-config
Bug #901185 [bash] exim4-config: fails to install
Added indication that 901185 affects exim4-config
> thanks
Stopping processing here.

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

Bug#874261: ncftp cannot be rebuilt from source

[Adrian Bunk]

On Sat, May 26, 2018 at 07:28:23PM +0200, Helmut Grohne wrote:
> Control: tags -1 - moreinfo
> 
> On Sat, May 26, 2018 at 05:27:20PM +0300, Adrian Bunk wrote:
> > Where is the attachment?
> 
> Here you go.
> 
> Helmut

> From: Helmut Grohne 
> Subject: make sh/autoconfall.sh work somewhat
>...
> @@ -51,7 +42,7 @@
>   fi
>  
>   /bin/mv configure configure.orig 2>/dev/null
> - "$AUTOCONF_BIN"/autoconf 2>&1 | fgrep -v AC_TRY_RUN
> + autoconf2.13 2>&1 | fgrep -v AC_TRY_RUN
>...

  autoconf2.13 -l autoconf_local 2>&1 | fgrep -v AC_TRY_RUN

cu
Adrian

-- 

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

Bug#901185: [Debconf-devel] Bug#901185: me too

[Andreas Metzler]

On 2018-06-10 Colin Watson  wrote:
> On Sun, Jun 10, 2018 at 03:03:28PM +0200, Andreas Metzler wrote:
>> I have tried debugging the issue to get a minimal testcase. I have had
>> some success. The issue is triggered by debconf.
>> /usr/share/debconf/confmodule changes IFS to \n and with bash5 this
>> change is persistent and breaks the maintainerscript.

> Does this patch help?

> diff --git a/confmodule b/confmodule
> index 8347c0b0..e6157520 100644
> --- a/confmodule
> +++ b/confmodule
> @@ -46,6 +46,7 @@ _db_cmd () {
>   # Set to newline to get whole line.
>   IFS='
>  ' read -r _db_internal_line
> + IFS="$_db_internal_IFS"
>   # Disgusting, but it's the only good way to split the line,
>   # preserving all other whitespace.
>   RET="${_db_internal_line#[! ][  ]}"

> (If so, that would suggest that the problem might be specifically in
> variable assignments preceding builtins.)

Hello Colin,

yes, resetting IFS to its default value in confmodule helps.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#901107: marked as done (grib-api: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 13:50:31 +
with message-id 
and subject line Bug#901107: fixed in grib-api 1.26.1-3
has caused the Debian Bug report #901107,
regarding grib-api: FTBFS when built with dpkg-buildpackage -A
to be marked as done.

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

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


-- 
901107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:grib-api
Version: 1.26.1-2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=cmake --with=python2,python3,fortran_mod 
--no-parallel
   dh_update_autotools_config -i -O--buildsystem=cmake
install -d debian/.debhelper/bucket/files
cp -an --reflink=auto config/config.guess 
debian/.debhelper/bucket/files/4676029966e14b0a9bfc430963a97196ea50451e4aa3ff23c41256b0046f6efe.tmp
mv 
debian/.debhelper/bucket/files/4676029966e14b0a9bfc430963a97196ea50451e4aa3ff23c41256b0046f6efe.tmp
 
debian/.debhelper/bucket/files/4676029966e14b0a9bfc430963a97196ea50451e4aa3ff23c41256b0046f6efe
cp -f /usr/share/misc/config.guess ./config/config.guess
cp -an --reflink=auto config/config.sub 
debian/.debhelper/bucket/files/4add30a10b137a5a4667e12868fb4783e385dbf865cfb7017b205321bd1a2f39.tmp
mv 
debian/.debhelper/bucket/files/4add30a10b137a5a4667e12868fb4783e385dbf865cfb7017b205321bd1a2f39.tmp
 
debian/.debhelper/bucket/files/4add30a10b137a5a4667e12868fb4783e385dbf865cfb7017b205321bd1a2f39
cp -f /usr/share/misc/config.sub ./config/config.sub
   dh_autoreconf -i -O--buildsystem=cmake
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' 
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec 
md5sum {} + -o -type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac

[... snipped ...]

done
`debian/tmp/usr/bin/grib1to2' probably isn't an ELF file.
elf_open: Exec format error
Ignoring chrpath error for non-ELF 
dh_numpy
(grep -a -s -v python:Depends debian/libgrib-api-doc.substvars; echo 
python:Depends=python-numpy) > debian/libgrib-api-doc.substvars.new
mv debian/libgrib-api-doc.substvars.new debian/libgrib-api-doc.substvars
dh_numpy3
(grep -a -s -v python3:Depends debian/libgrib-api-doc.substvars; echo 
python3:Depends=python3-numpy) > debian/libgrib-api-doc.substvars.new
mv debian/libgrib-api-doc.substvars.new debian/libgrib-api-doc.substvars
dh_install
install -d debian/.debhelper/generated/libgrib-api0
install -d debian/.debhelper/generated/libgrib-api-dev
install -d debian/.debhelper/generated/libgrib-api-tools
install -d debian/.debhelper/generated/libgrib-api-doc
install -d debian/.debhelper/generated/python-gribapi
install -d debian/.debhelper/generated/python3-gribapi
#
# Setup cmake files for magics++, metview, etc.
#
mkdir -p debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api
cp debian/tmp/usr/share/grib_api/cmake/* 
debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api
cat debian/tmp/usr/share/grib_api//cmake/grib_api-targets-release.cmake | \
sed -e 's% *IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE.*%  
IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE ""%' \
-e 's%${_IMPORT_PREFIX}%/usr%g' \
> 
debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api/grib_api-targets-release.cmake
cat debian/tmp/usr/share/grib_api//cmake/grib_api-config.cmake | \
sed -e 's%^set( grib_api_BASE_DIR.*%set ( grib_api_BASE_DIR /build/grib-api )%' 
| \
sed -e 's%^set( GRIB_API_TPLS.*%set( GRIB_API_TPLS "")%' | \
sed -e 's%^set( GRIB_API_TPL_LIBRARIES.*%set( GRIB_API_TPL_LIBRARIES "" )%' \
> 
debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api/grib_api-config.cmake
# For bit-reproducibility, sanitize the build paths
for f in grib_api-import.cmake grib_api-config.cmake ; do \
sed -e 's%/<>%/build/grib_api%g' < 
debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api/$f \
> debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api/x; \
mv debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api/x  
debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api/$f ; \
done
sed -e 's%/<>%/build/grib_api%g' < 
debian/libgrib-api-dev/usr/include/grib_api_ecbuild_config.h > x
/bin/sh: 1: 

Processed: gedit-source-code-browser-plugin: diff for NMU version 3.0.3-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 896726 + patch
Bug #896726 [src:gedit-source-code-browser-plugin] 
gedit-source-code-browser-plugin: missing build dependency on dh-python
Added tag(s) patch.
> tags 896726 + pending
Bug #896726 [src:gedit-source-code-browser-plugin] 
gedit-source-code-browser-plugin: missing build dependency on dh-python
Added tag(s) pending.

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

Bug#896726: gedit-source-code-browser-plugin: diff for NMU version 3.0.3-5.1

[Adrian Bunk]

Control: tags 896726 + patch
Control: tags 896726 + pending

Dear maintainer,

I've prepared an NMU for gedit-source-code-browser-plugin (versioned as 
3.0.3-5.1) and uploaded it to DELAYED/15. Please feel free to tell me if 
I should cancel it.

cu
Adrian

-- 

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

diff -Nru gedit-source-code-browser-plugin-3.0.3/debian/changelog gedit-source-code-browser-plugin-3.0.3/debian/changelog
--- gedit-source-code-browser-plugin-3.0.3/debian/changelog	2014-07-07 23:25:38.0 +0300
+++ gedit-source-code-browser-plugin-3.0.3/debian/changelog	2018-06-10 16:42:35.0 +0300
@@ -1,3 +1,10 @@
+gedit-source-code-browser-plugin (3.0.3-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the missing build dependency on dh-python. (Closes: #896726)
+
+ -- Adrian Bunk   Sun, 10 Jun 2018 16:42:35 +0300
+
 gedit-source-code-browser-plugin (3.0.3-5) unstable; urgency=medium
 
   * Patch: fix opening of remote files (LP: #1313112)
diff -Nru gedit-source-code-browser-plugin-3.0.3/debian/control gedit-source-code-browser-plugin-3.0.3/debian/control
--- gedit-source-code-browser-plugin-3.0.3/debian/control	2014-07-07 23:25:38.0 +0300
+++ gedit-source-code-browser-plugin-3.0.3/debian/control	2018-06-10 16:42:35.0 +0300
@@ -2,7 +2,7 @@
 Section: gnome
 Priority: optional
 Maintainer: Pietro Battiston 
-Build-Depends: debhelper (>= 7.0.50), python3
+Build-Depends: debhelper (>= 7.0.50), python3, dh-python
 Standards-Version: 3.9.5
 Homepage: https://github.com/Quixotix/gedit-source-code-browser
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/gedit-source-code-browser.git

Processed: doxyqml: diff for NMU version 0.3.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 828866 + pending
Bug #828866 [doxyqml] doxyqml: Please mark doxyqml multi-arch: foreign
Ignoring request to alter tags of bug #828866 to the same tags previously set
> tags 896754 + patch
Bug #896754 [src:doxyqml] doxyqml: missing build dependency on python3-distutils
Ignoring request to alter tags of bug #896754 to the same tags previously set
> tags 896754 + pending
Bug #896754 [src:doxyqml] doxyqml: missing build dependency on python3-distutils
Ignoring request to alter tags of bug #896754 to the same tags previously set

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

Processed: doxyqml: diff for NMU version 0.3.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 828866 + pending
Bug #828866 [doxyqml] doxyqml: Please mark doxyqml multi-arch: foreign
Added tag(s) pending.
> tags 896754 + patch
Bug #896754 [src:doxyqml] doxyqml: missing build dependency on python3-distutils
Added tag(s) patch.
> tags 896754 + pending
Bug #896754 [src:doxyqml] doxyqml: missing build dependency on python3-distutils
Added tag(s) pending.

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

Bug#896754: doxyqml: diff for NMU version 0.3.0-1.1

[Adrian Bunk]

Control: tags 828866 + pending
Control: tags 896754 + patch
Control: tags 896754 + pending

Dear maintainer,

I've prepared an NMU for doxyqml (versioned as 0.3.0-1.1) and uploaded 
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru doxyqml-0.3.0/debian/changelog doxyqml-0.3.0/debian/changelog
--- doxyqml-0.3.0/debian/changelog	2017-07-10 14:46:58.0 +0300
+++ doxyqml-0.3.0/debian/changelog	2018-06-10 16:38:00.0 +0300
@@ -1,3 +1,12 @@
+doxyqml (0.3.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the now required build dependency on python3-distutils.
+(Closes: #896754)
+  * Mark doxyqml Multi-Arch: foreign. (Closes: #828866)
+
+ -- Adrian Bunk   Sun, 10 Jun 2018 16:38:00 +0300
+
 doxyqml (0.3.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru doxyqml-0.3.0/debian/control doxyqml-0.3.0/debian/control
--- doxyqml-0.3.0/debian/control	2017-07-10 14:46:58.0 +0300
+++ doxyqml-0.3.0/debian/control	2018-06-10 16:38:00.0 +0300
@@ -4,12 +4,14 @@
 Maintainer: Loïc Minier 
 Build-Depends: debhelper (>= 9),
python3 (>= 3.0),
-   dh-python
+   dh-python,
+   python3-distutils
 Standards-Version: 4.0.0
 Homepage: http://agateau.com/projects/doxyqml
 
 Package: doxyqml
 Architecture: all
+Multi-Arch: foreign
 Depends: ${misc:Depends}, ${python3:Depends}, doxygen
 Description: QML filter for Doxygen
  Doxyqml is an input filter for Doxygen, a documentation system for C++

Bug#901243: mate-indicator-applet got removed from buster due to (spurious?) ido build dependency

[Adrian Bunk]

Source: mate-indicator-applet
Version: 1.20.0-1
Severity: serious

mate-indicator-applet was removed from buster when
ido was removed due to #895039.

The changelog says:

mate-indicator-applet (1.18.1-2) unstable; urgency=medium
...
  * debian/control:
+ Alternatively B-D on libido3-0.1-dev (>= 13.10) or
  libayatana-ido3-0.4-dev.
  Alternatively B-D on libindicator3-dev (>= 16.10) or
  libayatana-indicator3-dev.
  This lets this package build against Ubuntu Indicators in Ubuntu and
  derivatives, while in Debian and derivatives (except Ubuntu) the new
  Ayatana Indicators implementation gets used.
...
 -- Mike Gabriel   Mon, 04 Dec 2017 15:29:57 +0100


But the build dependencies are actually:

Build-Depends: debhelper (>= 11~),
   dpkg-dev (>= 1.16.1.1),
   intltool,
   libgtk-3-dev,
   libido3-0.1-dev,
   libayatana-ido3-0.4-dev,
   libindicator3-dev,
   libayatana-indicator3-dev,
...


This is not an alternative build dependency,
and makes the build dependencies not fulfillable
without ido.

Bug#901185: [Debconf-devel] Bug#901185: me too

[Colin Watson]

On Sun, Jun 10, 2018 at 03:03:28PM +0200, Andreas Metzler wrote:
> I have tried debugging the issue to get a minimal testcase. I have had
> some success. The issue is triggered by debconf.
> /usr/share/debconf/confmodule changes IFS to \n and with bash5 this
> change is persistent and breaks the maintainerscript.

Does this patch help?

diff --git a/confmodule b/confmodule
index 8347c0b0..e6157520 100644
--- a/confmodule
+++ b/confmodule
@@ -46,6 +46,7 @@ _db_cmd () {
# Set to newline to get whole line.
IFS='
 ' read -r _db_internal_line
+   IFS="$_db_internal_IFS"
# Disgusting, but it's the only good way to split the line,
# preserving all other whitespace.
RET="${_db_internal_line#[! ][  ]}"

(If so, that would suggest that the problem might be specifically in
variable assignments preceding builtins.)

-- 
Colin Watson   [cjwat...@debian.org]

Bug#901185: me too

[Andreas Metzler]

Hello bash maintainers (debconf Cced),

I have tried debugging the issue to get a minimal testcase. I have had
some success. The issue is triggered by debconf.
/usr/share/debconf/confmodule changes IFS to \n and with bash5 this
change is persistent and breaks the maintainerscript. i.e. installing a
package using the following.postinst (simply invoking the script as
unprivildged user also works, no dummy-package necessary)


#!/bin/sh
set -e
. /usr/share/debconf/confmodule
db_version 2.0
list="item1 item2"
for i in $list ; do
echo $i 1>&2
done


will
a) print
item1 item2
with bash5 and
b) print
item1
item2
with bash4 and dash.

Unfortunately I have not been able to get a simpler testcase.

cu Andreas

Bug#896353: Bug fixed in Git

[Adrian Bunk]

On Tue, May 22, 2018 at 11:42:35AM +0200, Andreas Tille wrote:
> Control: tags -1 pending
> 
> Hi Ghislain,
> 
> I intended to fix this (low hanging fruit ;-) ) bug but when I noticed
> that you are carrying an explicit *-dbg package I was wondering whether
> this is needed.  I would remove it in favour of the automatically
> created one - but may be you have your reasons for doing this.
>...

python*-dbg packages are also built for the debug build of the Pyhton 
interpreter (python{,3}-dbg), and -dbgsym conversion is therefore 
usually NOT correct for Python module packages.

In this case the -dbg variant of the bug is that python3-ltfatpy-dbg
also requires a dependency on python3-tk-dbg.

> Kind regards
> 
>   Andreas.

cu
Adrian

-- 

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

Bug#900826: marked as done (sabnzbdplus does not start due to python cheetah version error)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 12:20:04 +
with message-id 
and subject line Bug#900826: fixed in sabnzbdplus 2.3.4+dfsg-1
has caused the Debian Bug report #900826,
regarding sabnzbdplus does not start due to python cheetah version error
to be marked as done.

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

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


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

Dear Maintainer,

sabnzbdplus has stopped running on my testing system. When running from CLI i
get the following error:
~$ sabnzbdplus
Sorry, requires Python module Cheetah 2.0rc7 or higher.

Cheetah module is installed it is version 3.1.0-1. Startup script checks
cheetah version in a silly way.

try:
import Cheetah
if Cheetah.Version[0] != '2':
raise ValueError
except ValueError:
print "Sorry, requires Python module Cheetah 2.0rc7 or higher."
sys.exit(1)
except:
print "The Python module Cheetah is required"
sys.exit(1)

As you can see version 3 will not work...



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

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

Versions of packages sabnzbdplus depends on:
ii  libjs-bootstrap   3.3.7+dfsg-2
ii  libjs-excanvas0.r3-4
ii  libjs-jquery  3.2.1-1
ii  libjs-jquery-tablesorter  1:2.30.4+dfsg1-1
ii  libjs-jquery-ui   1.12.1+dfsg-5
ii  libjs-mochikit1.4.2-4
ii  libjs-moment  2.22.1+ds-1
ii  lsb-base  9.20170808
ii  python2.7.15~rc1-1
ii  python-cheetah3.1.0-1
ii  python-configobj  5.0.6-2
ii  python-sabyenc3.3.5-1
ii  python-six1.11.0-2

Versions of packages sabnzbdplus recommends:
ii  libavahi-compat-libdnssd1  0.7-4
ii  p7zip-full 16.02+dfsg-6
ii  par2   0.8.0-1
ii  python-cryptography2.1.4-1
ii  python-dbus1.2.8-2
ii  unrar  1:5.5.8-1

Versions of packages sabnzbdplus suggests:
ii  python-gtk22.24.0-5.1+b1
ii  python-notify  0.1.1-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sabnzbdplus
Source-Version: 2.3.4+dfsg-1

We believe that the bug you reported is fixed in the latest version of
sabnzbdplus, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 900...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
JCF Ploemen (jcfp)  (supplier of updated sabnzbdplus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Jun 2018 20:42:24 +
Source: sabnzbdplus
Binary: sabnzbdplus
Architecture: source all
Version: 2.3.4+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: JCF Ploemen (jcfp) 
Changed-By: JCF Ploemen (jcfp) 
Description:
 sabnzbdplus - web-based binary newsreader with nzb support
Closes: 900826
Changes:
 sabnzbdplus (2.3.4+dfsg-1) unstable; urgency=medium
 .
   [ JCF Ploemen (jcfp) ]
   * New upstream release:
 + accepts Cheetah versions newer than 2. (Closes: #900826)
   * Desktop: append %F field code to Exec key.
   * Manpage:
 + document option to add nzb files via cli.
 + remove obsolete options, add new --disable-file-log.
   * Rules: exclude example scripts from compression.
   * Patches: refresh 04, 09.
   * Copyright: bump upstream year to 2018.
   * Compat: bump level to 11 (from 10).
   * Bump Standards-Version to 4.1.4 (from 4.1.3; no further changes).
   * Lintian: override debian-rules-contains-unnecessary-get-orig-source-
 target.
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python-Version field.
Checksums-Sha1:
 450ebe0c21a61b01057d6799da6874193a49d03e 2097 sabnzbdplus_2.3.4+dfsg-1.dsc
 

Bug#900974: r-cran-hmisc: Missing Depends: r-cran-foreign, r-cran-nnet

[Dirk Eddelbuettel]

This issue is long closed. I will not comment on that last email.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#901185: me too

[Andreas Metzler]

On 2018-06-10 Eric Valette  wrote:
> On 6/10/18 11:57 AM, Eric Valette wrote:
>> On 6/10/18 11:35 AM, Andreas Metzler wrote:
 
>>> exports both dc_directives and any variable listed in dc_directives,
>>> i.e. any external command will see both ${dc_directives} and
>>> ${dc_eximconfig_configtype} et al.

>> right but did you intent that? The rest of the script seems not to use
>> explicitly anything but dc_directives in to awk script. Remains that the
>> script is broken with bash and not sure only from experimental (but as
>> the config file was already broken cannot be tottaly sure).

> Why don't you reassign the bug to bash experimental if you are so sure?

Because as it is the bug report is less than helpful for the bash
maintainers.

> Will do until you tell me why not

Please be a little bit more cooperative. Discuss first, and act later
when there is a consensus.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Processed: python-cluster: diff for NMU version 1.3.3-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 896298 + patch
Bug #896298 [python-cluster] python-cluster: cluster fails to import
Added tag(s) patch.
> tags 896298 + pending
Bug #896298 [python-cluster] python-cluster: cluster fails to import
Added tag(s) pending.

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

Bug#896298: python-cluster: diff for NMU version 1.3.3-1.1

[Adrian Bunk]

Control: tags 896298 + patch
Control: tags 896298 + pending

Dear maintainer,

I've prepared an NMU for python-cluster (versioned as 1.3.3-1.1) and 
uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru python-cluster-1.3.3/debian/changelog python-cluster-1.3.3/debian/changelog
--- python-cluster-1.3.3/debian/changelog	2016-04-28 12:31:41.0 +0300
+++ python-cluster-1.3.3/debian/changelog	2018-06-10 14:01:42.0 +0300
@@ -1,3 +1,11 @@
+python-cluster (1.3.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the missing dependency on python-pkg-resources.
+(Closes: #896298)
+
+ -- Adrian Bunk   Sun, 10 Jun 2018 14:01:42 +0300
+
 python-cluster (1.3.3-1) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru python-cluster-1.3.3/debian/control python-cluster-1.3.3/debian/control
--- python-cluster-1.3.3/debian/control	2016-04-28 12:31:41.0 +0300
+++ python-cluster-1.3.3/debian/control	2018-06-10 14:01:42.0 +0300
@@ -12,7 +12,7 @@
 
 Package: python-cluster
 Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}
+Depends: ${python:Depends}, python-pkg-resources, ${misc:Depends}
 XB-Python-Version: ${python:Versions}
 Description: allows grouping a list of arbitrary objects into related groups (clusters)
  python-cluster is a "simple" package that allows users to create several groups

Bug#901185: me too

[Andreas Metzler]

On 2018-06-10 Eric Valette  wrote:
> On 6/10/18 11:35 AM, Andreas Metzler wrote:

> > exports both dc_directives and any variable listed in dc_directives,
> > i.e. any external command will see both ${dc_directives} and
> > ${dc_eximconfig_configtype} et al.

> right but did you intent that?

Yes I did,...

> The rest of the script seems not to use
> explicitly anything but dc_directives in to awk script.

... because the awk script references both each entry in dc_directives
and its value (directives[i] and ENVIRON[directives[i]).

> Remains that the
> script is broken with bash and not sure only from experimental (but as the
> config file was already broken cannot be tottaly sure).

I had checked that before closing the bug report, bash/sid works.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#901129: marked as done (timidity: removes conffile belonging to timidity-daemon)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 11:05:20 +
with message-id 
and subject line Bug#901129: fixed in timidity 2.14.0-3
has caused the Debian Bug report #901129,
regarding timidity: removes conffile belonging to timidity-daemon
to be marked as done.

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

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


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

When upgrading timidity and timidity-daemon from 2.13.2-41 the following
happened (sorry for the German):

,
| Vorbereitung zum Entpacken von .../timidity_2.14.0-2_i386.deb ...
| Entpacken von timidity (2.14.0-2) über (2.13.2-41+b1) ...
| Vorbereitung zum Entpacken von .../timidity-daemon_2.14.0-2_all.deb ...
| Entpacken von timidity-daemon (2.14.0-2) über (2.13.2-41) ...
| Trigger für mime-support (3.60) werden verarbeitet ...
| Trigger für desktop-file-utils (0.23-3) werden verarbeitet ...
| Trigger für menu (2.1.47+b1) werden verarbeitet ...
| Trigger für systemd (238-5) werden verarbeitet ...
| Trigger für man-db (2.8.3-2) werden verarbeitet ...
| timidity (2.14.0-2) wird eingerichtet ...
| Neue Version der Konfigurationsdatei /etc/X11/app-defaults/TiMidity wird 
installiert ...
| Neue Version der Konfigurationsdatei 
/etc/X11/ja_JP.eucJP/app-defaults/TiMidity wird installiert ...
| Neue Version der Konfigurationsdatei /etc/timidity/timidity.cfg wird 
installiert ...
| Removing obsolete conffile /etc/init.d/timidity ...
| timidity-daemon (2.14.0-2) wird eingerichtet ...
| 
| Konfigurationsdatei »/etc/init.d/timidity«
|  ==> Gelöscht (von Ihnen oder von einem Skript) seit der Installation.
|  ==> Paketverteiler hat eine aktualisierte Version herausgegeben.
|Wie möchten Sie vorgehen? Ihre Wahlmöglichkeiten sind:
| Y oder I : Die Version des Paket-Betreuers installieren
| N oder O : Die momentan installierte Version beibehalten
|D : Die Unterschiede zwischen den Versionen anzeigen
|Z : Eine Shell starten, um die Situation zu begutachten
|  Der Standardweg ist das Beibehalten der momentanen Version.
| Trigger für systemd (238-5) werden verarbeitet ...
`

And since I was not smart enough to type "Y" at the dpkg prompt I was
left with /etc/init.d/timidity.dpkg-dist which had to be renamed to
timidity again.  Hopefully this was enough to untangle the mess, but
getting asked about a conffile which I (TTBOMK) did not change looks
unacceptable to me in any case.


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

Kernel: Linux 4.17.0-nouveau (SMP w/2 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 timidity depends on:
ii  libasound21.1.6-1
ii  libaudio2 1.9.4-6
ii  libc6 2.27-3
ii  libflac8  1.3.2-3
ii  libice6   2:1.0.9-2
ii  libjack0 [libjack-0.125]  1:0.125.0-3
ii  libncurses6   6.1+20180602-1
ii  libogg0   1.3.2-1+b1
ii  libpng16-16   1.6.34-1
ii  libsm62:1.2.2-1+b3
ii  libspeex1 1.2~rc1.2-1+b2
ii  libtinfo6 6.1+20180602-1
ii  libvorbis0a   1.3.6-1
ii  libvorbisenc2 1.3.6-1
ii  libx11-6  2:1.6.5-1
ii  libxaw7   2:1.0.13-1+b2
ii  libxext6  2:1.3.3-1+b2
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  lsb-base  9.20170808
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages timidity recommends:
pn  fluid-soundfont-gm  
ii  timidity-daemon 2.14.0-2

Versions of packages timidity suggests:
pn  fluid-soundfont-gs  
ii  freepats20060219-1
pn  pmidi   

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: timidity
Source-Version: 2.14.0-3

We believe that the bug you reported is fixed in the latest version of
timidity, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian 

Bug#901189: marked as done (timidity,timidity-el: both packages ship the manpages)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 11:05:20 +
with message-id 
and subject line Bug#901141: fixed in timidity 2.14.0-3
has caused the Debian Bug report #901141,
regarding timidity,timidity-el: both packages ship the manpages
to be marked as done.

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

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


-- 
901141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: timidity,timidity-el
Version: 2.14.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package timidity-el.
  Preparing to unpack .../timidity-el_2.14.0-2_all.deb ...
  Unpacking timidity-el (2.14.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/timidity-el_2.14.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/ja/man1/timidity.1.gz', which is also in 
package timidity 2.14.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/timidity-el_2.14.0-2_all.deb

The following files are shipped by both packages:

usr/share/man/ja/man1/timidity.1.gz
usr/share/man/ja/man5/timidity.cfg.5.gz
usr/share/man/man1/timidity.1.gz
usr/share/man/man5/timidity.cfg.5.gz


cheers,

Andreas


timidity=2.14.0-2_timidity-el=2.14.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: timidity
Source-Version: 2.14.0-3

We believe that the bug you reported is fixed in the latest version of
timidity, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated timidity package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Jun 2018 11:10:53 +0200
Source: timidity
Binary: timidity timidity-interfaces-extra timidity-el timidity-daemon
Architecture: source
Version: 2.14.0-3
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Reiner Herrmann 
Description:
 timidity   - Software sound renderer (MIDI sequencer, MOD player)
 timidity-daemon - runs TiMidity++ as a system-wide MIDI sequencer
 timidity-el - Emacs front end to Timidity++
 timidity-interfaces-extra - TiMidity++ extra user interfaces
Closes: 901129 901141
Changes:
 timidity (2.14.0-3) unstable; urgency=low
 .
   * QA upload.
   * Install manpages only in timidity package. (Closes: #901141)
   * Don't remove init.d conffile if it already belongs to timidity-daemon.
 (Closes: #901129)
Checksums-Sha1:
 a55bf3ec75be0a4f4843f7924da91a090a92a1d6 2292 timidity_2.14.0-3.dsc
 0f5f8915ef75c681b94c8c2fdbf887e7c6a648d2 28312 timidity_2.14.0-3.debian.tar.xz
 8a063d1765e648dc38407ea2e1978b1e99ce3989 12753 
timidity_2.14.0-3_amd64.buildinfo
Checksums-Sha256:
 b2951bcefdf5966b4aa5b749cad920da55b6b687c1a595fb1a1043e3f9703b81 2292 
timidity_2.14.0-3.dsc
 ccc15934fc6b493b7020a4dba4dcbc9a5bd36e3111babf41bcf8c9cef21ca226 28312 
timidity_2.14.0-3.debian.tar.xz
 89f5e16ca5889cdf9c5a84a2e0a5b4a96dbbc81b82414dc0d12f8b736b7b54cc 12753 
timidity_2.14.0-3_amd64.buildinfo
Files:
 0dac6a7ba0eeb0e123e4c273613e2f53 2292 sound optional timidity_2.14.0-3.dsc
 236197d2a7d47cd2c57f06426cf91ef5 28312 sound optional 
timidity_2.14.0-3.debian.tar.xz
 d6cb5ebfe83bd6798cd4a8c02cac9b2a 12753 sound optional 
timidity_2.14.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlsdAvAACgkQCBa54Yx2
K63OYxAAj3jNnTRb8oLMdLUnxn5GpknrAeJZEqRis4AaOlF7k/P6WJHld1nZpD1c
CLj7bh32qrfNS2UdlOksOqb/Df3R6ZzxtmTq80ZeCPw+STVH9az0yRD6ML66d9k3
JqgolqG5+yKP/sClNQSICoC0sqSmxhpy/ihgj5qnThpd7/N9xFKgAoO64LZfT2pu
3dmePOoM00xl+FePAkAGU0fS4E5cCr90mpNVLLMU68qkgY1kV3ddpdadMiMAL8ep
/AQsPOE6T3GZPVI2CXDxGz9p3CvHq8HW9ouiEy6EN8osVAZdLHUtE3vjsla6rZHE
6N8bRmSYtyb31vxhOsXhjYMNBL7mO+21t8zd+yBHyW5qhesKViRB++lS7BM+Qe5q
kY6js990YUhtoLyRmcmEHookMKrJ1u2afe/yCJkBiBPBAhNq7WxubH3DFLfvecXc
/0lEYzECDN7dfE4bcFRuSov8u9+Agy91OCkGkIU3BnjE9MHSJ+u4iXw9EZt+O99v

Bug#901141: marked as done ('/usr/share/man/ja/man1/timidity.1.gz' is also in package timidity)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 11:05:20 +
with message-id 
and subject line Bug#901141: fixed in timidity 2.14.0-3
has caused the Debian Bug report #901141,
regarding '/usr/share/man/ja/man1/timidity.1.gz' is also in package timidity
to be marked as done.

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

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


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Preparing to unpack .../timidity-el_2.14.0-2_all.deb ...
ERROR: timidity-el is broken - called emacs-package-remove as a new-style 
add-on, but has no compat file.
Remove timidity-el for emacs
Unpacking timidity-el (2.14.0-2) over (2.13.2-41) ...
dpkg: error processing archive 
/var/cache/apt/archives/timidity-el_2.14.0-2_all.deb (--unpack):
 trying to overwrite '/usr/share/man/ja/man1/timidity.1.gz', which is also in 
package timidity 2.14.0-2
Errors were encountered while processing:
 /var/cache/apt/archives/timidity-el_2.14.0-2_all.deb


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

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

Versions of packages timidity-el depends on:
ii  emacsen-common  3.0.0
pn  timidity

timidity-el recommends no packages.

timidity-el suggests no packages.

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlsbtkkACgkQ8gKXHaSn
niyhzAv9FlaXmD/WjMPtu/HorpPzssOdcF4g1xp4mItfrf4dJaKtbqrjsD1szC89
AZVgQp0w9D+fhbwPEoilQ4MpYBbzxjp/BvWRWe4PEQMyzmXtqg0YLs3WC/mToIzo
mZBpOZfgKNzH7kBXXeoUskn+6u3ejglR92JuLNtOSc+nQrGqC/wqlU/M15r/OBII
kLIoY86MApR1nX5iOtwtXfG4MvhjCCHmcNdU7K3az5ObiByC8C+Z0rTWWsL2VnvF
iGZQ+FERhVVXCgwI/f1PdkDOfYp9ijNFpXro2TTTI/fwCyxZVTBZCe/rGKtYcnhX
0ozdquFYM/9GWrAgZiBRDubNBANBpd1SxgXKbIV2vJIJAIWGov17pwPThArgD/IZ
d97Rn57jS1OZ1Jj9VogXjM+2jcoZAPySSag3k/3zf/mBYCBbpRBpifG3wl3xf9Ih
F1M3PDoB922EK9IYIqg377Mtk/MC9lhuN1qify9viZvkC8rUZKbYkeUlx+tOaHop
uy0oHSv5
=tws/
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: timidity
Source-Version: 2.14.0-3

We believe that the bug you reported is fixed in the latest version of
timidity, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated timidity package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Jun 2018 11:10:53 +0200
Source: timidity
Binary: timidity timidity-interfaces-extra timidity-el timidity-daemon
Architecture: source
Version: 2.14.0-3
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Reiner Herrmann 
Description:
 timidity   - Software sound renderer (MIDI sequencer, MOD player)
 timidity-daemon - runs TiMidity++ as a system-wide MIDI sequencer
 timidity-el - Emacs front end to Timidity++
 timidity-interfaces-extra - TiMidity++ extra user interfaces
Closes: 901129 901141
Changes:
 timidity (2.14.0-3) unstable; urgency=low
 .
   * QA upload.
   * Install manpages only in timidity package. (Closes: #901141)
   * Don't remove init.d conffile if it already belongs to timidity-daemon.
 (Closes: #901129)
Checksums-Sha1:
 a55bf3ec75be0a4f4843f7924da91a090a92a1d6 2292 timidity_2.14.0-3.dsc
 0f5f8915ef75c681b94c8c2fdbf887e7c6a648d2 28312 timidity_2.14.0-3.debian.tar.xz
 8a063d1765e648dc38407ea2e1978b1e99ce3989 12753 
timidity_2.14.0-3_amd64.buildinfo
Checksums-Sha256:
 b2951bcefdf5966b4aa5b749cad920da55b6b687c1a595fb1a1043e3f9703b81 2292 
timidity_2.14.0-3.dsc
 ccc15934fc6b493b7020a4dba4dcbc9a5bd36e3111babf41bcf8c9cef21ca226 28312 
timidity_2.14.0-3.debian.tar.xz
 89f5e16ca5889cdf9c5a84a2e0a5b4a96dbbc81b82414dc0d12f8b736b7b54cc 12753 
timidity_2.14.0-3_amd64.buildinfo
Files:
 0dac6a7ba0eeb0e123e4c273613e2f53 2292 sound optional timidity_2.14.0-3.dsc
 

Bug#896208: pysurfer: diff for NMU version 0.7-2.1

[Adrian Bunk]

Control: tags 896208 + patch
Control: tags 896208 + pending

Dear maintainer,

I've prepared an NMU for pysurfer (versioned as 0.7-2.1) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru pysurfer-0.7/debian/changelog pysurfer-0.7/debian/changelog
--- pysurfer-0.7/debian/changelog	2017-03-28 00:09:17.0 +0300
+++ pysurfer-0.7/debian/changelog	2018-06-10 12:41:23.0 +0300
@@ -1,3 +1,10 @@
+pysurfer (0.7-2.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Add the missing dependency on python-matplotlib. (Closes: #896208)
+
+ -- Adrian Bunk   Sun, 10 Jun 2018 12:41:23 +0300
+
 pysurfer (0.7-2) unstable; urgency=medium
 
   * Run help2man under xvfb to avoid manpage containing just an error
diff -Nru pysurfer-0.7/debian/control pysurfer-0.7/debian/control
--- pysurfer-0.7/debian/control	2017-03-28 00:09:17.0 +0300
+++ pysurfer-0.7/debian/control	2018-06-10 12:41:23.0 +0300
@@ -23,7 +23,8 @@
 Package: python-surfer
 Architecture: all
 Depends: ${misc:Depends}, ${python:Depends}, python-numpy, python-scipy,
- python-nibabel, python-pil | python-imaging, mayavi2, python-argparse
+ python-nibabel, python-pil | python-imaging, mayavi2, python-argparse,
+ python-matplotlib
 XB-Python-Version: ${python:Versions}
 Recommends: mencoder
 Description: visualize Freesurfer's data in Python

Processed: pysurfer: diff for NMU version 0.7-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 896208 + patch
Bug #896208 [python-surfer] python-surfer: surfer fails to import
Added tag(s) patch.
> tags 896208 + pending
Bug #896208 [python-surfer] python-surfer: surfer fails to import
Added tag(s) pending.

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

Bug#873341: Any news for this issue?

[Andreas Tille]

Hi again,

On Mon, May 28, 2018 at 01:51:09PM +0200, Emmanuel Bourg wrote:
> 
> You undeniably have the best understanding of SBT among the Debian
> developers. Even if you don't have the time to tackle all of this by
> yourself, do you think you could sketch a plan we could follow to
> achieve the SBT packaging? I'm sure people will jump in and help if the
> steps are clearly identified and with someone coordinating the packaging
> effort.

Since this mail remained unanswered I take the freedom to nag again:
What can we do to get sbt finally packaged?  I had the feeling that we
were *very* close last year and may be some discussing with ftpmaster
would have been sufficient (may be I'm wrong here).  But currently there
is a deadlock which needs some solution.

For my target project[1] I currently see no other clue than dumping
the JAR created by upstream into a non-free package since I have no
idea how to deal with those 17 *.scala files of that project. :-(

Kind regards

  Andreas.

[1] https://salsa.debian.org/med-team/pilon

-- 
http://fam-tille.de

Bug#868617: marked as done (golang-github-dnephin-cobra FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 10:49:56 +
with message-id 
and subject line Bug#868617: fixed in golang-github-dnephin-cobra 
1.5.1+git20170113.0.0e9ca70-3
has caused the Debian Bug report #868617,
regarding golang-github-dnephin-cobra FTBFS: test failures
to be marked as done.

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

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


-- 
868617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-dnephin-cobra
Version: 1.5+git20161103.0.a3c0924-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-dnephin-cobra FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-dnephin-cobra.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-dnephin-cobra.html

...
--- FAIL: TestChildCommandFlags (0.00s)
cobra_test.go:646: Wrong error message displayed, 
 invalid argument "10E" for "-i, --intone" flag: 
strconv.ParseInt: parsing "10E": invalid syntax
...
--- FAIL: TestFlagsBeforeCommand (0.00s)
cobra_test.go:1066: Wrong error message displayed, 
 invalid argument "10E" for "-i, --intone" flag: 
strconv.ParseInt: parsing "10E": invalid syntax
...
FAIL
exit status 1
FAILgithub.com/spf13/cobra  0.054s
?   github.com/spf13/cobra/cobra[no test files]
...
--- End Message ---
--- Begin Message ---
Source: golang-github-dnephin-cobra
Source-Version: 1.5.1+git20170113.0.0e9ca70-3

We believe that the bug you reported is fixed in the latest version of
golang-github-dnephin-cobra, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 868...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated 
golang-github-dnephin-cobra package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 10 Jun 2018 20:24:16 +1000
Source: golang-github-dnephin-cobra
Binary: golang-github-dnephin-cobra-dev
Architecture: source all
Version: 1.5.1+git20170113.0.0e9ca70-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dmitry Smirnov 
Description:
 golang-github-dnephin-cobra-dev - Go library for creating powerful modern Go 
CLI applications
Closes: 868617
Changes:
 golang-github-dnephin-cobra (1.5.1+git20170113.0.0e9ca70-3) unstable; 
urgency=medium
 .
   [ Alexandre Viau ]
   * Point Vcs-* urls to salsa.debian.org.
 .
   [ Dmitry Smirnov ]
   * added watch file
   * New patch to fix failing tests (Closes: #868617).
   * Standards-Version: 4.1.4; Priority: optional.
   * control += "Testsuite: autopkgtest-pkg-go".
Checksums-Sha1:
 087c3d592991ed3bd01fd3abae65992a9bbe6b9c 2466 
golang-github-dnephin-cobra_1.5.1+git20170113.0.0e9ca70-3.dsc
 68ec441a7eb0573dfc70de3d724c32c66e69c6ec 3352 
golang-github-dnephin-cobra_1.5.1+git20170113.0.0e9ca70-3.debian.tar.xz
 8756bf807d3e78f8b3553c01b08234a4b424f534 50552 
golang-github-dnephin-cobra-dev_1.5.1+git20170113.0.0e9ca70-3_all.deb
 5a29a17190f95f2a5aadfbb64de577104f0e6322 11143 
golang-github-dnephin-cobra_1.5.1+git20170113.0.0e9ca70-3_amd64.buildinfo
Checksums-Sha256:
 4c9049fd4d171a177340dfc9e1c34ae1c1ce57d6c638b1f6752b1a5da07ceb86 2466 
golang-github-dnephin-cobra_1.5.1+git20170113.0.0e9ca70-3.dsc
 2d9a7e0c5309c1bedc95737f3996b17828889da5b99b9ad2f09d5121c1b08610 3352 
golang-github-dnephin-cobra_1.5.1+git20170113.0.0e9ca70-3.debian.tar.xz
 6b512cef20ef677cb4e41dccfe795853df5d0752ad7fe581c168b2b0d81b8d0f 50552 
golang-github-dnephin-cobra-dev_1.5.1+git20170113.0.0e9ca70-3_all.deb
 b7fe39aec126e87bb77c94a6590ef51adf13fbf52851f3f1148e2cfe82ec08cf 11143 
golang-github-dnephin-cobra_1.5.1+git20170113.0.0e9ca70-3_amd64.buildinfo
Files:
 78f8730d0cc483baa6d0d69c32a99a73 2466 devel optional 
golang-github-dnephin-cobra_1.5.1+git20170113.0.0e9ca70-3.dsc
 7702d58cd875b2b27b986ef76abac994 3352 devel optional 
golang-github-dnephin-cobra_1.5.1+git20170113.0.0e9ca70-3.debian.tar.xz
 492f752f1653f84ed1c1498c548676b7 50552 devel optional 
golang-github-dnephin-cobra-dev_1.5.1+git20170113.0.0e9ca70-3_all.deb
 032191fbb37981ab69f38a214d54d3bc 11143 devel 

Bug#899775: mc: Invalid maintainer address pkg-mc-de...@lists.alioth.debian.org

[Dmitry Smirnov]

On Sunday, 10 June 2018 8:12:53 PM AEST Yury V. Zaytsev wrote:
> FYI, released mc-4.8.21 about a week ago...

Thanks, I've already uploaded it:

 https://packages.qa.debian.org/m/mc.html

-- 
Cheers,
 Dmitry Smirnov.

---


Good luck happens when preparedness meets opportunity.



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

Bug#868617: Bug #868617 in golang-github-dnephin-cobra marked as pending

[onlyjob]

Control: tag -1 pending

Hello,

Bug #868617 in golang-github-dnephin-cobra reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-github-dnephin-cobra/commit/cd7a943cf64e93a7544ef5f63ea80bcdf1fc2ce3


New patch to fix failing tests (Closes: #868617).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/868617

Processed: Bug #868617 in golang-github-dnephin-cobra marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #868617 [src:golang-github-dnephin-cobra] golang-github-dnephin-cobra 
FTBFS: test failures
Added tag(s) pending.

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

Bug#901185: Checkbashisms

[積丹尼 Dan Jacobson]

Be sure the package passes Checkbashisms!

Processed: bug is still there if you use experimental bash

[Debian Bug Tracking System]

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

> reopen 901185
Bug #901185 {Done: Andreas Metzler } [bash] exim4-config: 
fails to install
Bug reopened
Ignoring request to alter fixed versions of bug #901185 to the same values 
previously set
>
End of message, stopping processing here.

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

Processed: exim4 maintainer thinks it is a bash bug

[Debian Bug Tracking System]

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

> reassign 901185 bash 5.0~alpha1-1
Bug #901185 {Done: Andreas Metzler } [exim4-config] 
exim4-config: fails to install
Bug reassigned from package 'exim4-config' to 'bash'.
No longer marked as found in versions exim4/4.91-5.
Ignoring request to alter fixed versions of bug #901185 to the same values 
previously set
Bug #901185 {Done: Andreas Metzler } [bash] exim4-config: 
fails to install
Marked as found in versions bash/5.0~alpha1-1.
>
End of message, stopping processing here.

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

Bug#899775: mc: Invalid maintainer address pkg-mc-de...@lists.alioth.debian.org

[Yury V. Zaytsev]

On Wed, 30 May 2018, Andreas Tille wrote:


On Sun, May 27, 2018 at 06:32:53PM +1000, Dmitry Smirnov wrote:

On Friday, 25 May 2018 9:44:46 PM AEST Andreas Tille wrote:

Uh, somebody did not answer the call to salvage this list

Should we try to ask alioth-lists admins?  Any other idea how to
communicate about mc


Wouldn't something like m...@packages.qa.debian.org work for us? We probably
won't even need a list...


I'm fine with this as well.  Will somebody mind to upload the package
with this maintainer address?


FYI, released mc-4.8.21 about a week ago...

--
Sincerely yours,
Yury V. Zaytsev

Processed: severity of 873027 is serious, tagging 898705, found 898705 in 7.0.0+r33-1, found 898468 in 20171204 ...

[Debian Bug Tracking System]

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

> severity 873027 serious
Bug #873027 [libclamunrar] libclamunrar: FTBFS with zlib 1.2.10 and newer
Severity set to 'serious' from 'normal'
> tags 898705 + sid buster
Bug #898705 [src:android-platform-libcore] android-platform-libcore FTBFS with 
debhelper v11
Added tag(s) sid and buster.
> found 898705 7.0.0+r33-1
Bug #898705 [src:android-platform-libcore] android-platform-libcore FTBFS with 
debhelper v11
Marked as found in versions android-platform-libcore/7.0.0+r33-1.
> found 898468 20171204
Bug #898468 [debian-installer] debian-installer: black screen/long delay in 
graphical installer after switching from linux 4.15 to 4.16
Marked as found in versions debian-installer/20171204.
> tags 895828 + sid buster
Bug #895828 {Done: Gianfranco Costamagna } 
[src:haskell-vector-space-points] haskell-vector-space-points: cannot be built 
in sid
Added tag(s) sid and buster.
> tags 895576 + sid buster
Bug #895576 {Done: Gianfranco Costamagna } 
[src:haskell-uulib] haskell-uulib: FTBFS with GHC 8.2
Added tag(s) buster and sid.
> tags 897281 + sid buster
Bug #897281 [doc-debian-fr] doc-debian-fr: Should this package be removed?
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#901185: me too

[Eric Valette]

On 6/10/18 11:57 AM, Eric Valette wrote:

On 6/10/18 11:35 AM, Andreas Metzler wrote:


exports both dc_directives and any variable listed in dc_directives,
i.e. any external command will see both ${dc_directives} and
${dc_eximconfig_configtype} et al.


right but did you intent that? The rest of the script seems not to use 
explicitly anything but dc_directives in to awk script. Remains that the 
script is broken with bash and not sure only from experimental (but as 
the config file was already broken cannot be tottaly sure).



Why don't you reassign the bug to bash experimental if you are so sure? 
Will do until you tell me why not


-- eric

Bug#901185: me too

[Eric Valette]

On 6/10/18 11:35 AM, Andreas Metzler wrote:


exports both dc_directives and any variable listed in dc_directives,
i.e. any external command will see both ${dc_directives} and
${dc_eximconfig_configtype} et al.


right but did you intent that? The rest of the script seems not to use 
explicitly anything but dc_directives in to awk script. Remains that the 
script is broken with bash and not sure only from experimental (but as 
the config file was already broken cannot be tottaly sure).


-- eric

Processed: limit source to nodejs, tagging 898024

[Debian Bug Tracking System]

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

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

> tags 898024 + pending
Bug #898024 [nodejs-dev] trying to overwrite '/usr/include/nodejs/common.gypi', 
which is also in package nodejs-dev 10.0.0~dfsg-2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#901191: marked as done (libfabric-bin: missing Breaks+Replaces: libfabric1 (<< 1.6))

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 09:49:40 +
with message-id 
and subject line Bug#901191: fixed in libfabric 1.6.1-3
has caused the Debian Bug report #901191,
regarding libfabric-bin: missing Breaks+Replaces: libfabric1 (<< 1.6)
to be marked as done.

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

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


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

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libfabric-bin.
  Preparing to unpack .../libfabric-bin_1.6.1-1_amd64.deb ...
  Unpacking libfabric-bin (1.6.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libfabric-bin_1.6.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/fi_info', which is also in package libfabric1 
1.5.3-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libfabric-bin_1.6.1-1_amd64.deb


cheers,

Andreas


libfabric1=1.5.3-1_libfabric-bin=1.6.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libfabric
Source-Version: 1.6.1-3

We believe that the bug you reported is fixed in the latest version of
libfabric, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mehdi Dogguy  (supplier of updated libfabric package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 10 Jun 2018 11:12:48 +0200
Source: libfabric
Binary: libfabric-bin libfabric1 libfabric-dev
Architecture: source amd64
Version: 1.6.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Mehdi Dogguy 
Description:
 libfabric-bin - Diagnosis programs for the libfabric communication library
 libfabric-dev - Development files for libfabric1
 libfabric1 - libfabric communication library
Closes: 901191
Changes:
 libfabric (1.6.1-3) unstable; urgency=medium
 .
   * libfabric-bin must Breaks+Replaces libfabric1 (<< 1.6) (Closes: #901191)
Checksums-Sha1:
 30424d74bcec49ccdc2308d4e72f2bfffce769df 2235 libfabric_1.6.1-3.dsc
 7f83910e2da3c86bc6212823bca76604f52f6070 7668 libfabric_1.6.1-3.debian.tar.xz
 4ef2aca83de203c9716ff438240c8f3c39685278 63340 
libfabric-bin-dbgsym_1.6.1-3_amd64.deb
 3fff50b8d8282a0723144142cef8fd71297ff43a 30720 libfabric-bin_1.6.1-3_amd64.deb
 1b0aeab3deced6e482ab87ccdbc56817b556a560 568636 libfabric-dev_1.6.1-3_amd64.deb
 77fc91cea58b88a9c2ed08ff347eb575df265645 2609224 
libfabric1-dbgsym_1.6.1-3_amd64.deb
 c5086a6d4499fcb317383b422d6d93637c856fd8 418632 libfabric1_1.6.1-3_amd64.deb
 ae6af01a56b3064b8c21b6f523d8fbcb4f0aae66 7012 libfabric_1.6.1-3_amd64.buildinfo
Checksums-Sha256:
 4ec27ba4474a9e8482e452ca055ac383be6628ce6fd84f54ef8d3f1c5b7028a5 2235 
libfabric_1.6.1-3.dsc
 07c1409d8904bd05d2449b49137515462837783225bfa3ab053eb1e9bf30bf18 7668 
libfabric_1.6.1-3.debian.tar.xz
 db59bd5fc38939230a66ea4c36afcc2ef154fdb6e31abcff368afee4e2a40545 63340 
libfabric-bin-dbgsym_1.6.1-3_amd64.deb
 04932c22422d0594d8360abef9abb0da83d0a2f3dd430681ae2b3169a1be0040 30720 
libfabric-bin_1.6.1-3_amd64.deb
 9ca76e3c6617bcaaadd1828f48ac8ca8c290e136d68e66b5a9870e5adb081cc3 568636 
libfabric-dev_1.6.1-3_amd64.deb
 f6cdf8e67e3eb7ad88a5974535e89293134ce5a4233759d274904a1db940786d 2609224 
libfabric1-dbgsym_1.6.1-3_amd64.deb
 208d699de1a5443cd53b857a93237fce8a3c9363a9c759c74396acf6be5d43c8 418632 
libfabric1_1.6.1-3_amd64.deb
 221ff9b47f610f9483212dfaa576afe2e8c8e9b322f8cf38126d366a87dd0bc2 7012 
libfabric_1.6.1-3_amd64.buildinfo
Files:
 f36050d12b54ccb80de55eb83189491b 2235 libs optional libfabric_1.6.1-3.dsc
 e0198b61c74b3cba15bd9455fa2b74f7 7668 libs optional 

Bug#901185: marked as done (exim4-config: fails to install)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 11:44:45 +0200
with message-id <20180610094445.gd4...@argenau.bebt.de>
and subject line Re: Bug#901185: closed by Andreas Metzler  
(Re: Bug#901185: me too)
has caused the Debian Bug report #901185,
regarding exim4-config: fails to install
to be marked as done.

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

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


-- 
901185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exim4-config
Version: 4.91-5
Severity: grave
Justification: renders package unusable

apt-get -f install
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 2 non mis à jour.
4 partiellement installés ou enlevés.
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Paramétrage de exim4-config (4.91-5) ...
/etc/exim4/update-exim4.conf.conf: ligne 32: dc_eximconfig_configtype : 
commande introuvable
/etc/exim4/update-exim4.conf.conf: ligne 32: dc_eximconfig_configtype : 
commande introuvable
dpkg: erreur de traitement du paquet exim4-config (--configure) :
 installed exim4-config package post-installation script subprocess returned 
error exit status 127
dpkg: des problèmes de dépendances empêchent la configuration de exim4-base 
:
 exim4-base dépend de exim4-config (>= 4.82) | exim4-config-2 ; cependant :
 Le paquet exim4-config n'est pas encore configuré.
  Le paquet exim4-config-2 n'est pas installé.
  Le paquet exim4-config qui fournit exim4-config-2 n'est pas encore configuré.

dpkg: erreur de traitement du paquet exim4-base (--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de exim4 :
 exim4 dépend de exim4-base (>= 4.91-5) ; cependant :
 Le paquet exim4-base n'est pas encore configuré.
 exim4 dépend de exim4-base (<< 4.91-5.1) ; cependant :
 Le paquet exim4-base n'est pas encore configuré.



-- Package-specific info:
Exim version 4.91 #4 built 09-Jun-2018 16:10:39
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC 
Event OCSP PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated

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

Kernel: Linux 4.14.48 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages exim4-config depends on:
ii  adduser3.117
ii  debconf [debconf-2.0]  1.5.66

exim4-config recommends no packages.

exim4-config suggests no packages.

-- Configuration Files:
/etc/exim4/passwd.client [Errno 13] Permission non accordée: 
'/etc/exim4/passwd.client'

-- debconf information excluded
--- End Message ---
--- Begin Message ---

On 2018-06-10 Eric Valette  wrote:
> On 6/10/18 10:33 AM, Debian Bug Tracking System wrote:
>> This is an automatic notification regarding your Bug report
>> which was filed against the exim4-config package:

> But now how do we fix the problem? I will reopen until I have a fix. Putting
> dash as /bin/sh does fix anything BTW.

Closing again, workaround documented, not an exim bug.--- End Message ---

Bug#901185: me too

[Andreas Metzler]

On 2018-06-10 Eric Valette  wrote:
> On 6/10/18 10:51 AM, Eric Valette wrote:
>> On 6/10/18 10:34 AM, Eric Valette wrote:
 
>>> line 330 :export dc_directives ${dc_directives}

>> Shodul be export dc_directives=${dc_directives} as far as I understand.
[...]
> and it worked. But I still think there is a non portable syntax line 330 of
> exim4-config.postins.

Hello,

That is not invalid syntax, export takes a list of shell-local variables
(and *optionally* value assignments like foo=bar) and exports the list
of local varaiables. dc_directives contains a list of variables
(dc_eximconfig_configtype et al.) and

export dc_directives ${dc_directives}

exports both dc_directives and any variable listed in dc_directives,
i.e. any external command will see both ${dc_directives} and
${dc_eximconfig_configtype} et al.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#901191: Bug #901191 in libfabric marked as pending

[mehdi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/hpc-team/libfabric/commit/1bd5e81a6e6d958ccffc208e0e0f86ca9039088e


libfabric-bin must Breaks+Replaces libfabric1 (<< 1.6) (Closes: #901191)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/901191

Processed: Bug #901191 in libfabric marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #901191 [libfabric-bin] libfabric-bin: missing Breaks+Replaces: libfabric1 
(<< 1.6)
Added tag(s) pending.

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

Bug#901185: me too

[Andreas Metzler]

On 2018-06-10 Eric Valette  wrote:
> On 6/10/18 10:59 AM, Eric Valette wrote:
> > On 6/10/18 10:51 AM, Eric Valette wrote:

> >  2) mv /etc/exim4/update-exim4.conf.conf 
> > /etc/exim4/update-exim4.conf.conf.old

exactly what I wrote ;-)
"installs/configures successfully once the broken
/etc/exim4/update-exim4.conf.conf has been removed."

Bug#901225: libell-dev: missing dependency on libell0

[Sven Joachim]

Package: libell-dev
Version: 0.4-1
Severity: serious

Your package is lacking a dependency on libell0 (= ${binary:Version}),
without it dynamic linking is not going to work:

,
| $ sudo aptitude install libell-dev
| [...]   
| $ file /usr/lib/i386-linux-gnu/libell.so
| /usr/lib/i386-linux-gnu/libell.so: broken symbolic link to libell.so.0.0.1
`


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

Kernel: Linux 4.17.0-nouveau (SMP w/2 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)

-- no debconf information

Bug#901220: libreoffice-dictionaries: FTBFS: can't cd to /<>/debian/hunspell-es/usr/share/hunspell

[Rene Engelhard]

Hi,

On Sun, Jun 10, 2018 at 10:56:31AM +0200, Andreas Beckmann wrote:
> libreoffice-dictionaries/experimental FTBFS:
> 
> https://buildd.debian.org/status/fetch.php?pkg=libreoffice-dictionaries=all=1%3A6.1.0%7Ebeta1-1=1527247064=0

Yes, I have seen this. I *do* look at buildlogs after uploads.

This is experimental and this is a pure data
package with contents which ideally shouldn't be there at all but built
from wherever they come from, so I didn't immediately fix it.

Will be fixed with a subsequent upload, whenever this will happen.
Probably with beta2.

Regards,

Rene

Processed: tagging 901220

[Debian Bug Tracking System]

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

> tags 901220 + pending
Bug #901220 [src:libreoffice-dictionaries] libreoffice-dictionaries: FTBFS: 
can't cd to /<>/debian/hunspell-es/usr/share/hunspell
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 901129

[Debian Bug Tracking System]

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

> tags 901129 + pending
Bug #901129 [timidity] timidity: removes conffile belonging to timidity-daemon
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#901223: gitaly: FTBFS: prometheus.Observer does not implement prometheus.Histogram

[Andreas Beckmann]

Source: gitaly
Version: 0.96.1+debian-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

gitaly/experimental FTBFS:

https://buildd.debian.org/status/fetch.php?pkg=gitaly=amd64=0.96.1%2Bdebian-4=1528128434=0

...
gitlab.com/gitlab-org/gitaly/internal/middleware/limithandler/testpb
gitlab.com/gitlab-org/gitaly/internal/middleware/limithandler
gitlab.com/gitlab-org/gitaly/internal/helper/housekeeping
# gitlab.com/gitlab-org/gitaly/internal/middleware/limithandler
src/gitlab.com/gitlab-org/gitaly/internal/middleware/limithandler/metrics.go:109:13:
 cannot use histogramVec.WithLabelValues(serviceName, methodName) (type 
prometheus.Observer) as type prometheus.Histogram in assignment:
prometheus.Observer does not implement prometheus.Histogram (missing 
Collect method)
gitlab.com/gitlab-org/gitaly/vendor/google.golang.org/grpc/reflection
github.com/stretchr/testify/require
gitlab.com/gitlab-org/gitaly/internal/helper/fieldextractors
gitlab.com/gitlab-org/gitaly/client
gitlab.com/gitlab-org/gitaly/cmd/gitaly-ssh
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/gitaly-0.96.1\+debian/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/gitaly-0.96.1\+debian/obj-x86_64-linux-gnu/src\"
 -v -p 4 -ldflags "-X 
gitlab.com/gitlab-org/gitaly/internal/version.version=0.96.1+debian" 
gitlab.com/gitlab-org/gitaly/auth gitlab.com/gitlab-org/gitaly/client 
gitlab.com/gitlab-org/gitaly/cmd/gitaly 
gitlab.com/gitlab-org/gitaly/cmd/gitaly-ssh 
gitlab.com/gitlab-org/gitaly/internal/archive 
gitlab.com/gitlab-org/gitaly/internal/command 
gitlab.com/gitlab-org/gitaly/internal/config 
gitlab.com/gitlab-org/gitaly/internal/connectioncounter 
gitlab.com/gitlab-org/gitaly/internal/diff 
gitlab.com/gitlab-org/gitaly/internal/git 
gitlab.com/gitlab-org/gitaly/internal/git/alternates 
gitlab.com/gitlab-org/gitaly/internal/git/catfile 
gitlab.com/gitlab-org/gitaly/internal/git/log 
gitlab.com/gitlab-org/gitaly/internal/helper 
gitlab.com/gitlab-org/gitaly/internal/helper/fieldextractors 
gitlab.com/gitlab-org/gitaly/internal/helper/housekeeping 
gitlab.com/gitlab-org/gitaly/internal/helper/lines 
gitlab.com/gitlab-org/gitaly/internal/linguist 
gitlab.com/gitlab-org/gitaly/internal/logsanitizer 
gitlab.com/gitlab-org/gitaly/internal/middleware/cancelhandler 
gitlab.com/gitlab-org/gitaly/internal/middleware/limithandler 
gitlab.com/gitlab-org/gitaly/internal/middleware/limithandler/testpb 
gitlab.com/gitlab-org/gitaly/internal/middleware/metadatahandler 
gitlab.com/gitlab-org/gitaly/internal/middleware/panichandler 
gitlab.com/gitlab-org/gitaly/internal/middleware/sentryhandler 
gitlab.com/gitlab-org/gitaly/internal/rubyserver 
gitlab.com/gitlab-org/gitaly/internal/rubyserver/balancer 
gitlab.com/gitlab-org/gitaly/internal/server 
gitlab.com/gitlab-org/gitaly/internal/server/auth 
gitlab.com/gitlab-org/gitaly/internal/service 
gitlab.com/gitlab-org/gitaly/internal/service/blob 
gitlab.com/gitlab-org/gitaly/internal/service/commit 
gitlab.com/gitlab-org/gitaly/internal/service/conflicts 
gitlab.com/gitlab-org/gitaly/internal/service/diff 
gitlab.com/gitlab-org/gitaly/internal/service/namespace 
gitlab.com/gitlab-org/gitaly/internal/service/notifications 
gitlab.com/gitlab-org/gitaly/internal/service/operations 
gitlab.com/gitlab-org/gitaly/internal/service/ref 
gitlab.com/gitlab-org/gitaly/internal/service/remote 
gitlab.com/gitlab-org/gitaly/internal/service/repository 
gitlab.com/gitlab-org/gitaly/internal/service/server 
gitlab.com/gitlab-org/gitaly/internal/service/smarthttp 
gitlab.com/gitlab-org/gitaly/internal/service/ssh 
gitlab.com/gitlab-org/gitaly/internal/service/wiki 
gitlab.com/gitlab-org/gitaly/internal/storage 
gitlab.com/gitlab-org/gitaly/internal/supervisor 
gitlab.com/gitlab-org/gitaly/internal/supervisor/test-scripts 
gitlab.com/gitlab-org/gitaly/internal/tempdir 
gitlab.com/gitlab-org/gitaly/internal/testhelper 
gitlab.com/gitlab-org/gitaly/internal/version 
gitlab.com/gitlab-org/gitaly/streamio returned exit code 2
make[1]: *** [debian/rules:23: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/gitaly-0.96.1+debian'
make: *** [debian/rules:14: build-arch] Error 2


Andreas

Bug#901185: me too

[Eric Valette]

On 6/10/18 10:59 AM, Eric Valette wrote:

On 6/10/18 10:51 AM, Eric Valette wrote:



 2) mv /etc/exim4/update-exim4.conf.conf 
/etc/exim4/update-exim4.conf.conf.old

Bug#901185: me too

[Eric Valette]

On 6/10/18 10:51 AM, Eric Valette wrote:

On 6/10/18 10:34 AM, Eric Valette wrote:


line 330 :export dc_directives ${dc_directives}


Shodul be export dc_directives=${dc_directives} as far as I understand.


To fix I did :
1) use dash temporarilly
2) /etc/exim4/update-exim4.conf.conf.old
3) rerun install

and it worked. But I still think there is a non portable syntax line 330 
of exim4-config.postins.


-- eric

Bug#901220: libreoffice-dictionaries: FTBFS: can't cd to /<>/debian/hunspell-es/usr/share/hunspell

[Andreas Beckmann]

Source: libreoffice-dictionaries
Version: 1:6.1.0~beta1-1
Severity: serious
Justification: fails to build from source

libreoffice-dictionaries/experimental FTBFS:

https://buildd.debian.org/status/fetch.php?pkg=libreoffice-dictionaries=all=1%3A6.1.0%7Ebeta1-1=1527247064=0

   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
cd /<>/debian/hunspell-es/usr/share/hunspell; mv -v es_ANY.aff 
es_ES.aff; mv es_ANY.dic es_ES.dic
/bin/sh: 1: cd: can't cd to 
/<>/debian/hunspell-es/usr/share/hunspell
mv: cannot stat 'es_ANY.aff': No such file or directory
mv: cannot stat 'es_ANY.dic': No such file or directory
make[1]: *** [debian/rules:32: override_dh_install] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:20: binary-indep] Error 2


Andreas

Bug#901185: me too

[Eric Valette]

On 6/10/18 10:34 AM, Eric Valette wrote:


line 330 :export dc_directives ${dc_directives}


Shodul be export dc_directives=${dc_directives} as far as I understand.

-- eric

Bug#901218: libgrpc-dev: libgpr.a, libgpr.so are already shipped by libgpr1-dev

[Andreas Beckmann]

Package: libgrpc-dev
Version: 1.12.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files.

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

  Selecting previously unselected package libgrpc-dev:amd64.
  Preparing to unpack .../7-libgrpc-dev_1.12.0-1_amd64.deb ...
  Unpacking libgrpc-dev:amd64 (1.12.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-wuGieo/7-libgrpc-dev_1.12.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libgpr.a', which is also in 
package libgpr1-dev 2017-6
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-wuGieo/7-libgrpc-dev_1.12.0-1_amd64.deb

Is this a typo in libgrpc to ship libgpr files?

Since these appear to be unrelated libraries,
Conflicts/Breaks/Replaces is *NOT* a solution for this conflict.


cheers,

Andreas


libgpr1-dev=2017-6_libgrpc-dev=1.12.0-1.log.gz
Description: application/gzip

Processed: forcibly merging 901141 901189

[Debian Bug Tracking System]

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

> forcemerge 901141 901189
Bug #901141 [timidity-el] '/usr/share/man/ja/man1/timidity.1.gz' is also in 
package timidity
Bug #901189 [timidity-el] timidity,timidity-el: both packages ship the manpages
Marked as found in versions timidity/2.14.0-2.
Added tag(s) pending.
Merged 901141 901189
> thanks
Stopping processing here.

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

Processed: reassign 901189 to timidity-el

[Debian Bug Tracking System]

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

> reassign 901189 timidity-el
Bug #901189 [timidity,timidity-el] timidity,timidity-el: both packages ship the 
manpages
Bug reassigned from package 'timidity,timidity-el' to 'timidity-el'.
No longer marked as found in versions 2.14.0-2.
Ignoring request to alter fixed versions of bug #901189 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Reopen : please provide a way to fix

[Debian Bug Tracking System]

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

> reopen 901185
Bug #901185 {Done: Andreas Metzler } [exim4-config] 
exim4-config: fails to install
Bug reopened
Ignoring request to alter fixed versions of bug #901185 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#901216: libosmocoding0: missing Breaks+Replaces: libosmocore9 (<< 0.11)

[Andreas Beckmann]

Package: libosmocoding0
Version: 0.11.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libosmocoding0:amd64.
  Preparing to unpack .../libosmocoding0_0.11.0-1_amd64.deb ...
  Unpacking libosmocoding0:amd64 (0.11.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libosmocoding0_0.11.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libosmocoding.so.0', which is 
also in package libosmocore9:amd64 0.10.2-6
  Errors were encountered while processing:
   /var/cache/apt/archives/libosmocoding0_0.11.0-1_amd64.deb


cheers,

Andreas


libosmocore9=0.10.2-6_libosmocoding0=0.11.0-1.log.gz
Description: application/gzip

Processed (with 1 error): forcibly merging 901141 901189

[Debian Bug Tracking System]

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

> forcemerge 901141 901189
Bug #901141 [timidity-el] '/usr/share/man/ja/man1/timidity.1.gz' is also in 
package timidity
Unable to merge bugs because:
package of #901189 is 'timidity,timidity-el' not 'timidity-el'
Failed to forcibly merge 901141: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#901185: closed by Andreas Metzler (Re: Bug#901185: me too)

[Eric Valette]

On 6/10/18 10:33 AM, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the exim4-config package:



But now how do we fix the problem? I will reopen until I have a fix. 
Putting dash as /bin/sh does fix anything BTW.


-- eric

Bug#901185: me too

[Eric Valette]

On 6/10/18 7:07 AM, Andreas Metzler wrote:

On 2018-06-10 積丹尼 Dan Jacobson  wrote:

Oops. I mean just:
Setting up exim4-config (4.91-5) ...
/etc/exim4/update-exim4.conf.conf: line 26: dc_eximconfig_configtype: command 
not found


Hello,

Are you running bash (or other stuff) from experimental? IIRC there is
some breakage there.



I was runnin experimental bash , reverted to unstable but it does not 
change anything (see below).


I'm just wondering with this line in exim4-config.postinst

line 330 :export dc_directives ${dc_directives}


apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 13 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up exim4-config (4.91-5) ...
/etc/exim4/update-exim4.conf.conf: line 32: dc_eximconfig_configtype: 
command not found
/etc/exim4/update-exim4.conf.conf: line 32: dc_eximconfig_configtype: 
command not found

dpkg: error processing package exim4-config (--configure):
 installed exim4-config package post-installation script subprocess 
returned error exit status 127

Setting up exim4-daemon-light (4.91-5) ...
Job for exim4.service failed because the control process exited with 
error code.

See "systemctl status exim4.service" and "journalctl -xe" for details.
invoke-rc.d: initscript exim4, action "start" failed.
● exim4.service - LSB: exim Mail Transport Agent
   Loaded: loaded (/etc/init.d/exim4; generated)
   Active: failed (Result: exit-code) since Sun 2018-06-10 10:28:22 
CEST; 12ms ago

 Docs: man:systemd-sysv-generator(8)
  Process: 5225 ExecStart=/etc/init.d/exim4 start (code=exited, status=127)

Jun 10 10:28:22 tri-yann4 systemd[1]: Starting LSB: exim Mail Transport 
Agent...
Jun 10 10:28:22 tri-yann4 exim4[5225]: Starting 
MTA:/etc/exim4/update-exim4.conf.conf: line 32: 
dc_eximconfig_configtype: command not found
Jun 10 10:28:22 tri-yann4 systemd[1]: exim4.service: Control process 
exited, code=exited status=127
Jun 10 10:28:22 tri-yann4 systemd[1]: exim4.service: Failed with result 
'exit-code'.
Jun 10 10:28:22 tri-yann4 systemd[1]: Failed to start LSB: exim Mail 
Transport Agent.

dpkg: error processing package exim4-daemon-light (--configure):
 installed exim4-daemon-light package post-installation script 
subprocess returned error exit status 1

dpkg: dependency problems prevent configuration of exim4:
 exim4 depends on exim4-daemon-light | exim4-daemon-heavy | 
exim4-daemon-custom; however:

  Package exim4-daemon-light is not configured yet.
  Package exim4-daemon-heavy is not installed.
  Package exim4-daemon-custom is not installed.

dpkg: error processing package exim4 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 exim4-config
 exim4-daemon-light
 exim4
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
tri-yann4:/home/valette#

# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to replace
# the DEBCONFsomethingDEBCONF strings in the configuration template files.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype=''
dc_other_hostnames=''
dc_local_interfaces=''
dc_readhost=''
dc_relay_domains=''
dc_minimaldns=''
dc_relay_nets=''
dc_smarthost=''
CFILEMODE=''
dc_use_split_config=''
dc_hide_mailname=''
dc_mailname_in_oh=''
dc_localdelivery=''
dc_eximconfig_configtype dc_other_hostnames dc_local_interfaces dc_readhost 
dc_relay_domains dc_minimaldns dc_relay_nets dc_smarthost CFILEMODE 
dc_use_split_config dc_hide_mailname dc_mailname_in_oh dc_localdelivery=''

Bug#898976: marked as done (openjdk-7: 2018 Q2 security update)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2018 08:35:58 +
with message-id 
and subject line Bug#898976: fixed in openjdk-7 7u181-2.6.14-1
has caused the Debian Bug report #898976,
regarding openjdk-7: 2018 Q2 security update
to be marked as done.

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

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


-- 
898976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-7
Version: 7u171-2.6.13-1
Severity: serious
Tags: security

Hi,

As usual, there are a few security issues from 2018 Q2. There's no update
yet, though it's in progress:

http://mail.openjdk.java.net/pipermail/jdk7u-dev/2018-May/010767.html

We can either backport those changes or wait for the release.

Cheers,
Emilio

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

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
LANGUAGE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: openjdk-7
Source-Version: 7u181-2.6.14-1

We believe that the bug you reported is fixed in the latest version of
openjdk-7, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 898...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated openjdk-7 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Jun 2018 12:23:38 +0200
Source: openjdk-7
Binary: openjdk-7-jdk openjdk-7-jre-headless openjdk-7-jre openjdk-7-jre-lib 
openjdk-7-demo openjdk-7-source openjdk-7-doc openjdk-7-dbg icedtea-7-jre-jamvm 
openjdk-7-jre-zero
Architecture: source
Version: 7u181-2.6.14-1
Distribution: experimental
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Emilio Pozuelo Monfort 
Description:
 icedtea-7-jre-jamvm - Alternative JVM for OpenJDK, using JamVM
 openjdk-7-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-7-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-7-doc - OpenJDK Development Kit (JDK) documentation
 openjdk-7-jdk - OpenJDK Development Kit (JDK)
 openjdk-7-jre - OpenJDK Java runtime, using
 openjdk-7-jre-headless - OpenJDK Java runtime, using  (headless)
 openjdk-7-jre-lib - OpenJDK Java runtime (architecture independent libraries)
 openjdk-7-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
 openjdk-7-source - OpenJDK Development Kit (JDK) source files
Closes: 898976
Changes:
 openjdk-7 (7u181-2.6.14-1) experimental; urgency=medium
 .
   * IcedTea release 2.6.14 (based on 7u181). Closes: #898976.
   * Security fixes:
 - S8162488: JDK should be updated to use LittleCMS 2.8
 - S8180881: Better packaging of deserialization
 - S8182362: Update CipherOutputStream Usage
 - S8183032: Upgrade to LittleCMS 2.9
 - S8189123: More consistent classloading
 - S8189969, CVE-2018-2790: Manifest better manifest entries
 - S8189977, CVE-2018-2795: Improve permission portability
 - S8189981, CVE-2018-2796: Improve queuing portability
 - S8189985, CVE-2018-2797: Improve tabular data portability
 - S8189989, CVE-2018-2798: Improve container portability
 - S8189993, CVE-2018-2799: Improve document portability
 - S8189997, CVE-2018-2794: Enhance keystore mechanisms
 - S8190478: Improved interface method selection
 - S8190877: Better handling of abstract classes
 - S8191696: Better mouse positioning
 - S8192025, CVE-2018-2814: Less referential references
 - S8192030: Better MTSchema support
 - S8192757, CVE-2018-2815: Improve stub classes implementation
 - S8193409: Improve AES supporting classes
 - S8193414: Improvements in MethodType lookups
 - S8193833, CVE-2018-2800: Better RMI connection support
   * debian/patches/it-patch-updates.diff:
 - Refreshed.
   * debian/patches/hotspot-powerpcspe.diff: