Bug#918000: openmpi postinst failure due to missing space in script

[Mo Zhou]

Package: libopenmpi3
Version: 3.1.3-7
Severity: serious

Dear maintainer,

You missed a space in the script, which resulted in


The following packages will be upgraded:
  libopenmpi3 openmpi-common
2 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
210 not fully installed or removed.
Need to get 0 B/2338 kB of archives.
After this operation, 16.4 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 168982 files and directories currently installed.)
Preparing to unpack .../libopenmpi3_3.1.3-7_amd64.deb ...
Unpacking libopenmpi3:amd64 (3.1.3-7) over (3.1.3-5) ...
rm: cannot remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-8#': No such file 
or directory
rm: cannot remove 'End': No such file or directory
rm: cannot remove 'automatically': No such file or directory
rm: cannot remove 'added': No such file or directory
rm: cannot remove 'section': No such file or directory
dpkg: warning: old libopenmpi3:amd64 package post-removal script subprocess 
returned error exit status 1
dpkg: trying script from the new package instead ...
dpkg: error processing archive 
/var/cache/apt/archives/libopenmpi3_3.1.3-7_amd64.deb (--unpack):
 there is no script in the new version of the package - giving up
Preparing to unpack .../openmpi-common_3.1.3-7_all.deb ...
Unpacking openmpi-common (3.1.3-7) over (3.1.3-5) ...
rm: cannot remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-8#': No such file 
or directory
rm: cannot remove 'End': No such file or directory
rm: cannot remove 'automatically': No such file or directory
rm: cannot remove 'added': No such file or directory
rm: cannot remove 'section': No such file or directory
dpkg: warning: old openmpi-common package post-removal script subprocess 
returned error exit status 1
dpkg: trying script from the new package instead ...
dpkg: error processing archive 
/var/cache/apt/archives/openmpi-common_3.1.3-7_all.deb (--unpack):


 cat /var/lib/dpkg/info/libopenmpi3:amd64.postrm | tail -n1
[ -d /usr/lib/$multiarch/fortran/$base ] && rm 
/usr/lib/$multiarch/fortran/$cmplr# End automatically added section

 ^missing space here

Processed: tagging 917982

[Debian Bug Tracking System]

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

> tags 917982 + buster sid
Bug #917982 [src:fenix] fenix FTBFS with glibc 2.28
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: REally reassign

[Debian Bug Tracking System]

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

> reassign 917961 node-gyp
Bug #917961 {Done: Jérémy Lal } [nodejs] nodejs: missing 
shlibs prevents build-dependencies on libnode-dev from working correctly
Bug reassigned from package 'nodejs' to 'node-gyp'.
No longer marked as found in versions nodejs/10.15.0~dfsg-5.
Ignoring request to alter fixed versions of bug #917961 to the same values 
previously set
> found 917961 3.8.0-1
Bug #917961 {Done: Jérémy Lal } [node-gyp] nodejs: missing 
shlibs prevents build-dependencies on libnode-dev from working correctly
Marked as found in versions node-gyp/3.8.0-1 and reopened.
> fixed 917961 3.8.0-2
Bug #917961 [node-gyp] nodejs: missing shlibs prevents build-dependencies on 
libnode-dev from working correctly
Marked as fixed in versions node-gyp/3.8.0-2.
> thanks
Stopping processing here.

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

Bug#916738: nvidia-alternative: Depends on a non-existent version of glx-alternative which breaks upgrade path.

[ewe2]

Thanks Joerg, I've upgraded successfully and everything seems to be
working fine, I'm happy for the bug to be closed now.

On Wed, 26 Dec 2018 at 19:54, Joerg Schuetter  wrote:
>
> Version 0.9.0 of glx-alternative-{nvidia,mesa} are available since a few 
> days. Installation of nvidia packages 410.78-2 went smooth.
>
>
> --
> Best Regards
>   Joerg Schuetter
> ___
> pkg-nvidia-devel mailing list
> pkg-nvidia-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nvidia-devel



-- 

I love deadlines. I love the whooshing noise they make as they go by.

Bug#906831: marked as done (xul-ext-iceweasel-branding no longer works with firefox-esr 60)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 06:25:06 +
with message-id 
and subject line Bug#917966: Removed package(s) from unstable
has caused the Debian Bug report #906831,
regarding xul-ext-iceweasel-branding no longer works with firefox-esr 60
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.)


-- 
906831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-iceweasel-branding
Version: 0.4.0
Severity: serious

XUL addons are no longer supported.
--- End Message ---
--- Begin Message ---
Version: 0.4.0+rm

Dear submitter,

as the package firefox-branding-iceweasel has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/917966

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#790591: marked as done (gnome-python-desktop: depends on python-gnome2 which is deprecated)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 06:17:20 +
with message-id 
and subject line Bug#917891: Removed package(s) from unstable
has caused the Debian Bug report #790591,
regarding gnome-python-desktop: depends on python-gnome2 which is deprecated
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.)


-- 
790591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-python-desktop
Severity: important
Tags: sid stretch
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-gnome2 gnome-python

Hi,

gnome-python-desktop depends on python-gnome2, which is long
deprecated and going to be removed from the archive.
gnome-python-desktop should be ported away from it.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Stretch release as we're going to
try to remove python-gnome2 this cycle.

If you have any question don't hesitate to ask.

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 2.32.0+dfsg-4+rm

Dear submitter,

as the package gnome-python-desktop has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/917891

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#874751: marked as done (blktap-dkms: module FTBFS for Linux 4.12)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 06:18:36 +
with message-id 
and subject line Bug#917908: Removed package(s) from unstable
has caused the Debian Bug report #874751,
regarding blktap-dkms: module FTBFS for Linux 4.12
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.)


-- 
874751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: blktap-dkms
Version: 2.0.93-0.10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

blktap-dkms fails to build a module for Linux 4.12:

Selecting previously unselected package blktap-dkms.
(Reading database ... 34976 files and directories currently installed.)
Preparing to unpack .../blktap-dkms_2.0.93-0.10_amd64.deb ...
Unpacking blktap-dkms (2.0.93-0.10) ...
Setting up blktap-dkms (2.0.93-0.10) ...
Loading new blktap-2.0.93 DKMS files...
It is likely that 4.6.0-1-amd64 belongs to a chroot's host
Building for 4.12.0-1-amd64
Building initial module for 4.12.0-1-amd64
Error! Bad return status for module build on kernel: 4.12.0-1-amd64 (x86_64)
Consult /var/lib/dkms/blktap/2.0.93/build/make.log for more information.


DKMS make.log for blktap-2.0.93 for kernel 4.12.0-1-amd64 (x86_64)
Sat Sep  9 13:04:28 UTC 2017
make: Entering directory '/usr/src/linux-headers-4.12.0-1-amd64'
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/control.o
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/ring.o
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/device.o
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/request.o
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/sysfs.o
In file included from /var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:66:0,
 from /var/lib/dkms/blktap/2.0.93/build/blktap.h:33,
 from /var/lib/dkms/blktap/2.0.93/build/request.c:31:
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:119:24: warning: variably 
modified 'pending' at file scope
sizeof(((struct blktap_sring *)0)->ring[0])))
^
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:15:59: 
note: in definition of macro '__RD2'
 #define __RD2(_x)  (((_x) & 0x0002) ? 0x2 : ((_x) & 0x1))
   ^~
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:17:66: 
note: in expansion of macro '__RD4'
 #define __RD8(_x)  (((_x) & 0x00f0) ? __RD4((_x)>>4)<<4: __RD4(_x))
  ^
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:18:66: 
note: in expansion of macro '__RD8'
 #define __RD16(_x) (((_x) & 0xff00) ? __RD8((_x)>>8)<<8: __RD8(_x))
  ^
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:19:66: 
note: in expansion of macro '__RD16'
 #define __RD32(_x) (((_x) & 0x) ? __RD16((_x)>>16)<<16 : __RD16(_x))
  ^~
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:117:8: note: in expansion of 
macro '__RD32'
  ((int)__RD32((BLKTAP_PAGE_SIZE -\
^~
/var/lib/dkms/blktap/2.0.93/build/blktap.h:77:41: note: in expansion of macro 
'BLKTAP_RING_SIZE'
  struct blktap_request *pending[BLKTAP_RING_SIZE];
 ^~~~
/var/lib/dkms/blktap/2.0.93/build/request.c: In function 'blktap_request_alloc':
/var/lib/dkms/blktap/2.0.93/build/request.c:138:2: warning: this 'if' clause 
does not guard... [-Wmisleading-indentation]
  if (request)
  ^~
/var/lib/dkms/blktap/2.0.93/build/request.c:140:6: note: ...this statement, but 
the latter is misleadingly indented as if it is guarded by the 'if'
  sg_init_table(request->sg_table, ARRAY_SIZE(request->sg_table));
  ^
In file included from /var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:66:0,
 from /var/lib/dkms/blktap/2.0.93/build/blktap.h:33,
 from /var/lib/dkms/blktap/2.0.93/build/control.c:30:
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:119:24: warning: variably 
modified 'pending' at file scope
sizeof(((struct blktap_sring *)0)->ring[0])))
^
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:15:59: 
note: in definition of macro '__RD2'
 #define __RD2(_x)  (((_x) & 0x0002) ? 0x2 : ((_x) & 0x1))
   ^~

Bug#883212: marked as done (blktap FTBFS with glibc 2.25)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 06:18:01 +
with message-id 
and subject line Bug#917907: Removed package(s) from unstable
has caused the Debian Bug report #883212,
regarding blktap FTBFS with glibc 2.25
to be marked as done.

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

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


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

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

...
tap-ctl-allocate.c: In function 'tap_ctl_make_device':
tap-ctl-allocate.c:114:13: error: In the GNU C Library, "makedev" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "makedev", include 
 directly. If you did not intend to use a system-defined macro
 "makedev", you should undefine it after including . [-Werror]
  err = mknod(devname, perm, makedev(major, minor));
 ^~~ 
--- End Message ---
--- Begin Message ---
Version: 2.0.90-4+rm

Dear submitter,

as the package blktap has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/917907

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#916034: marked as done (sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64)

[أحمد المحمودي]

Hello Andreas,

On Wed, Jan 02, 2019 at 05:21:03AM +, Debian Bug Tracking System wrote:
> and subject line Bug#916034: fixed in sl-modem 2.9.11~20110321-14
> Changes:
>  sl-modem (2.9.11~20110321-14) unstable; urgency=medium
>  .
>[ Ondřej Nový ]
>* d/copyright: Change Format URL to correct one
>* d/changelog: Remove trailing whitespaces
>  .
>[ أحمد المحمودي (Ahmed El-Mahmoudy) ]
>* Remove old transitional sl-modem-source target
>* Modify support_linux3.diff patch to support linux >3.
>  Thanks to Ben Hutchings  (Closes: #916034)
>* Update standards version to 4.3.0, no changes needed
>* debian/control, debian/changelog: Remove empty lines
>* Bumped compat level to 12
---end quoted text---

Please build this package for i386 and upload.

Thanks.


-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#914607: Re-adding python-dfwinreg

[林上智]

Hi Hilko,

Hilko Bengen  於 2018年12月23日 週日 上午6:22寫道：
>
> Control: tag -1 pending
>
> I have just uploaded dfwinreg/20181214-2 to DELAYED/10 -- it will have
> to wait for python-dtfabric and python3-dtfabric to reach unstable.
>
> Cheers,
> -Hilko

Please feel free to add your name into the package maintainer if you want :)

SZ

Bug#916123: marked as done (grcompiler: Please use pkg-config to detect icu)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 05:49:12 +
with message-id 
and subject line Bug#916123: fixed in grcompiler 4.2-7
has caused the Debian Bug report #916123,
regarding grcompiler: Please use pkg-config to detect icu
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.)


-- 
916123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grcompiler
Version: 4.2-6+b3
Severity: normal

Dear Maintainer,

icu-config has been deprecated by its upstream developers for some years now.
In icu 63.1, icu-config is optional to install, but installed by default. In
the next version, icu-config will no longer be installed by default.

The developers recommend downstream packages use pkg-config to detect the icu
libraries.

Debian will remove icu-config from libicu-dev shortly. Hence, the need to patch
grcompiler to use pkg-config to detect icu.

Please let me know if you need any help with this change.



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

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

Versions of packages grcompiler depends on:
ii  libc6   2.28-2
ii  libgcc1 1:8.2.0-11
ii  libicu6363.1-5
ii  libstdc++6  8.2.0-11

grcompiler recommends no packages.

Versions of packages grcompiler suggests:
ii  firefox 63.0.3-1
ii  libgraphite2-3  1.3.12-1
pn  libreoffice 
pn  pango-graphite  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: grcompiler
Source-Version: 4.2-7

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated grcompiler package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Jan 2019 14:28:41 +0900
Source: grcompiler
Binary: grcompiler
Architecture: source
Version: 4.2-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Hideki Yamane 
Description:
 grcompiler - Compiler of smart (graphite) fonts
Closes: 916123
Changes:
 grcompiler (4.2-7) unstable; urgency=medium
 .
   * Team upload
 .
   [ Daniel Glassey ]
   * d/control:
 - update Vcs-* for salsa
 - build dep on debhelper 11
 - update team maintainer to debian-fo...@lists.debian.org
   * compat level 11
   * d/watch: grcompiler is now on gihub
   thanks to bgermann for the PR
 .
   [ Hideki Yamane ]
   * debian/patches
 - add icu_pkg-config.patch (Closes: #916123)
   * debian/control
 - set Standards-Version: 4.3.0
 - Suggests: drop iceweasel and add "gnome-www-browser | firefox-esr"
 - drop unnecessary "Build-depends: dh-autoreconf"
 - use dh12, set "Build-Depends: debhelper (>= 12), debhelper-compat (= 12)"
 - fix wrong Vcs-Git url
 - Add Homepage: field
   * debian/copyright
 - use https for copyright format URL
Checksums-Sha1:
 23c6678f168ff296f919ff748fa0ca870b75551e 2068 grcompiler_4.2-7.dsc
 d9086bc7a220c1d89e6fecd3e9fb9b42396113cf 11468 grcompiler_4.2-7.debian.tar.xz
 4aa47bc8215b1ea7a47d7bbab5f8415605385aed 7080 grcompiler_4.2-7_amd64.buildinfo
Checksums-Sha256:
 0577e783328ca92a4e97936a210a1aad19a68c920b945ee341d4f7ed5ef5f0ad 2068 
grcompiler_4.2-7.dsc
 22e64a8d43a30145664b270cffc564f1fc90844de53e5f1bcfa135077fae9cbe 11468 
grcompiler_4.2-7.debian.tar.xz
 dbb164b88fdac53d32f3dbc33cd4c39f6e6415ecf8fa719faa323667f8ada709 7080 
grcompiler_4.2-7_amd64.buildinfo
Files:
 2baba1d64ab62f4ca695646438eefe7c 2068 devel optional grcompiler_4.2-7.dsc
 21ddc906b88992b28eb04baf24c2c42b 11468 devel optional 
grcompiler_4.2-7.debian.tar.xz
 fe1f196e891f4622ce8f107d6bae98be 7080 devel optional 
grcompiler_4.2-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#916123: Bug #916123 in grcompiler marked as pending

[Hideki Yamane]

Control: tag -1 pending

Hello,

Bug #916123 in grcompiler 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/fonts-team/grcompiler/commit/3b501679d8e032ee8bc26197e748787c4afa31ce


add icu_pkg-config.patch (Closes: #916123)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916123

Processed: Bug #916123 in grcompiler marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #916123 [src:grcompiler] grcompiler: Please use pkg-config to detect icu
Added tag(s) pending.

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

Bug#916034: marked as done (sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 05:19:28 +
with message-id 
and subject line Bug#916034: fixed in sl-modem 2.9.11~20110321-14
has caused the Debian Bug report #916034,
regarding sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64
to be marked as done.

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

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


-- 
916034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sl-modem-dkms
Version: 2.9.11~20110321-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 2.9.11~20110321-12

Hi,

sl-modem-dkms fails to build a module for 4.18.0-3-amd64 and 4.9.0-8-amd64

Selecting previously unselected package sl-modem-dkms.
(Reading database ... 33401 files and directories currently installed.)
Preparing to unpack .../sl-modem-dkms_2.9.11~20110321-13_amd64.deb ...
Unpacking sl-modem-dkms (2.9.11~20110321-13) ...
Setting up sl-modem-dkms (2.9.11~20110321-13) ...
Loading new sl-modem-2.9.11~20110321 DKMS files...
grep: /lib/modules/4.9.0-6-amd64/build/.config: No such file or directory
It is likely that 4.9.0-6-amd64 belongs to a chroot's host
Building for 4.18.0-3-amd64
Building initial module for 4.18.0-3-amd64
Error!  Build of slusb.ko failed for: 4.18.0-3-amd64 (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ for more information.
dpkg: error processing package sl-modem-dkms (--configure):
 installed sl-modem-dkms package post-installation script subprocess returned 
error exit status 7
Errors were encountered while processing:
 sl-modem-dkms

# cat /var/lib/dkms/sl-modem/2.9.11~20110321/build/make.log 
DKMS make.log for sl-modem-2.9.11~20110321 for kernel 4.18.0-3-amd64 (x86_64)
Sun Dec  9 13:53:21 UTC 2018
make: Entering directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
doing %.o: %.c
cc -Wall -pipe -O3 -fomit-frame-pointer -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB 
`test -f /lib/modules/4.18.0-3-amd64/build/include/linux/modversions.h && echo 
-DMODVERSIONS --include 
/lib/modules/4.18.0-3-amd64/build/include/linux/modversions.h 
-I/lib/modules/4.18.0-3-amd64/build/include`  -I. -I./../modem   -o 
old_st7554.o -c old_st7554.c
old_st7554.c:49:10: fatal error: linux/init.h: No such file or directory
 #include 
  ^~
compilation terminated.
make: *** [Makefile:129: old_st7554.o] Error 1
make: Leaving directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
make: Entering directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'
make modules -C /lib/modules/4.18.0-3-amd64/build 
SUBDIRS=/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem
make[1]: Entering directory '/usr/src/linux-headers-4.18.0-3-amd64'
  CC [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.mod.o
  LD [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.18.0-3-amd64'
make: Leaving directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'

# cat /var/lib/dkms/sl-modem/2.9.11~20110321/build/make.log 
DKMS make.log for sl-modem-2.9.11~20110321 for kernel 4.9.0-8-amd64 (x86_64)
Sun Dec  9 14:02:25 UTC 2018
make: Entering directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
doing %.o: %.c
cc -Wall -pipe -O3 -fomit-frame-pointer -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB 
`test -f /lib/modules/4.9.0-8-amd64/build/include/linux/modversions.h && echo 
-DMODVERSIONS --include 
/lib/modules/4.9.0-8-amd64/build/include/linux/modversions.h 
-I/lib/modules/4.9.0-8-amd64/build/include`  -I. -I./../modem   -o old_st7554.o 
-c old_st7554.c
old_st7554.c:48:26: fatal error: linux/module.h: No such file or directory
 #include 
  ^
compilation terminated.
Makefile:128: recipe for target 'old_st7554.o' failed
make: *** [old_st7554.o] Error 1
make: Leaving directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
make: Entering directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'
make modules -C /lib/modules/4.9.0-8-amd64/build 
SUBDIRS=/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem
make[1]: Entering directory '/usr/src/linux-headers-4.9.0-8-amd64'
  CC [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC  

Processed: Re: Bug#889125: comidi-clojure FTBFS: test failure

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #889125 [src:comidi-clojure] comidi-clojure FTBFS: test failure
Added tag(s) patch.

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

Bug#889125: comidi-clojure FTBFS: test failure

[Cyril Brulebois]

Control: tag -1 patch

Cyril Brulebois  (2018-12-31):
> Control: forwarded -1 https://github.com/puppetlabs/comidi/issues/36

Upstream patch available (attached), and MR opened upstream:
  https://github.com/puppetlabs/comidi/pull/37

I think I'll wait a few days until upstream has had a chance to comment,
then I'll consider adding the patch to the debian packaging, and submit
an MR against the debian packaging repository.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
From feed07ec54e9d68e3bf52dd1f1a56138d8fd0eab Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Wed, 2 Jan 2019 04:34:31 +0100
Subject: [PATCH] Fix test failure with Clojure 1.9+
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Quoting the Clojure documentation:

Use :require in the ns macro in preference to calling this directly.

As kindly pointed out by Alex Miller (@puredanger), the “require” syntax
happened to work accidentally in Clojure 1.8, but that's now rejected by
Clojure 1.9+ with:

Call to clojure.core/ns did not conform to spec: […] Extra input

Debian bug report: https://bugs.debian.org/889125
---
 test/puppetlabs/comidi_test.clj | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/puppetlabs/comidi_test.clj b/test/puppetlabs/comidi_test.clj
index 0b3a53a..4d0e064 100644
--- a/test/puppetlabs/comidi_test.clj
+++ b/test/puppetlabs/comidi_test.clj
@@ -1,5 +1,5 @@
 (ns puppetlabs.comidi-test
-  (require [clojure.test :refer :all]
+  (:require [clojure.test :refer :all]
[puppetlabs.comidi :as comidi :refer :all]
[schema.test :as schema-test]
[schema.core :as schema]
-- 
2.11.0



signature.asc
Description: PGP signature

Bug#917036: libswagger2-perl: dead upstream

[intrigeri]

gregor herrmann:
> Sounds like a removal candidate?

Agreed ⇒ usertagged as such :)

Bug#917710: marked as done (bolt: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 04:49:02 +
with message-id 
and subject line Bug#917710: fixed in bolt 0.7-1
has caused the Debian Bug report #917710,
regarding bolt: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=2 ninja test returned exit code 1
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.)


-- 
917710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bolt
Version: 0.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- \
>   --libexecdir=/usr/lib/bolt \
>   -Dman=true \
>   -Dprivileged-group=sudo
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu 
> --libexecdir=lib/x86_64-linux-gnu --libexecdir=/usr/lib/bolt -Dman=true 
> -Dprivileged-group=sudo
> The Meson build system
> Version: 0.49.0
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: bolt
> Project version: 0.5
> Appending CFLAGS from environment: '-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security'
> Appending LDFLAGS from environment: '-Wl,-z,relro -Wl,-z,now -Wl,-z,defs 
> -Wl,--as-needed'
> Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2'
> Native C compiler: cc (gcc 8.2.0 "cc (Debian 8.2.0-13) 8.2.0")
> Build machine cpu family: x86_64
> Build machine cpu: x86_64
> Compiler for C supports arguments -fstack-protector-strong: YES
> Compiler for C supports arguments -Waggregate-return: YES
> Compiler for C supports arguments -Wunused: YES
> Compiler for C supports arguments -Warray-bounds: YES
> Compiler for C supports arguments -Wcast-align: YES
> Compiler for C supports arguments -Wclobbered: YES
> Compiler for C supports arguments -Wdeclaration-after-statement: YES
> Compiler for C supports arguments -Wempty-body: YES
> Compiler for C supports arguments -Wformat=2: YES
> Compiler for C supports arguments -Wformat-nonliteral: YES
> Compiler for C supports arguments -Wformat-security: YES
> Compiler for C supports arguments -Wformat-signedness: YES
> Compiler for C supports arguments -Wignored-qualifiers: YES
> Compiler for C supports arguments -Wimplicit-function-declaration: YES
> Compiler for C supports arguments -Winit-self: YES
> Compiler for C supports arguments -Wmissing-declarations: YES
> Compiler for C supports arguments -Wmissing-format-attribute: YES
> Compiler for C supports arguments -Wmissing-include-dirs: YES
> Compiler for C supports arguments -Wmissing-noreturn: YES
> Compiler for C supports arguments -Wmissing-parameter-type: YES
> Compiler for C supports arguments -Wmissing-prototypes: YES
> Compiler for C supports arguments -Wnested-externs: YES
> Compiler for C supports arguments -Wno-discarded-qualifiers 
> -Wdiscarded-qualifiers: YES
> Compiler for C supports arguments -Wno-missing-field-initializers 
> -Wmissing-field-initializers: YES
> Compiler for C supports arguments -Wno-strict-aliasing -Wstrict-aliasing: YES
> Compiler for C supports arguments -Wno-suggest-attribute=format 
> -Wsuggest-attribute=format: YES
> Compiler for C supports arguments -Wno-unused-parameter -Wunused-parameter: 
> YES
> Compiler for C supports arguments -Wold-style-definition: YES
> Compiler for C supports arguments -Woverride-init: YES
> Compiler for C supports arguments -Wpointer-arith: YES
> Compiler for C supports arguments -Wredundant-decls: YES
> Compiler for C supports arguments -Wreturn-type: YES
> Compiler for C supports arguments -Wshadow: YES
> Compiler for C supports arguments -Wsign-compare: YES
> Compiler for C supports arguments -Wstrict-aliasing: YES
> Compiler for C supports arguments -Wstrict-prototypes: YES
> Compiler for C supports arguments -Wtype-limits: YES
> Compiler for C supports arguments -Wundef: YES
> Compiler for C supports arguments -Wuninitialized: YES
> Compiler for C supports arguments -Wunused-but-set-variable: YES
> Compiler for C supports arguments -Wwrite-strings: YES
> Found pkg-config: /usr/bin/pkg-config (0.29)
> Dependency glib-2.0 found: YES 2.58.1
> Dependency gio-2.0 found: YES 2.58.1
> Dependency libudev found: YES 240
> Dependency gio-unix-2.0 found: YES 2.58.1
> Dependency udev found: YES 

Bug#917680: marked as done (nibabel: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 03:49:24 +
with message-id 
and subject line Bug#917680: fixed in nibabel 2.3.1+git51-g1ea7c30f-1
has caused the Debian Bug report #917680,
regarding nibabel: FTBFS: tests failed
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.)


-- 
917680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nibabel
Version: 2.3.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> /bin/sh: 1: git: not found
> python2.7 setup.py config --noisy
> Missing optional package "dicom" provided by package "pydicom"; you may get 
> run-time errors
> running config
> python2.7 setup.py build
> Missing optional package "dicom" provided by package "pydicom"; you may get 
> run-time errors
> running build
> running build_py
> running build_scripts
> /<>/nibabel/checkwarns.py:19: FutureWarning: The checkwarns 
> module is deprecated and will be removed in nibabel v3.0
>   'in nibabel v3.0', FutureWarning)
> /usr/lib/python2.7/dist-packages/nose/importer.py:94: FutureWarning: We no 
> longer carry a copy of the 'six' package in nibabel; Please import the 'six' 
> package directly
>   mod = load_module(part_fqname, fh, filename, desc)
> /usr/lib/python2.7/dist-packages/nose/importer.py:94: FutureWarning: We will 
> remove this module from nibabel soon; Please use the 'minc1' module instead
>   mod = load_module(part_fqname, fh, filename, desc)
> /usr/lib/python2.7/dist-packages/nose/importer.py:94: UserWarning: The DICOM 
> readers are highly experimental, unstable, and only work for Siemens 
> time-series at the moment
> Please use with caution.  We would be grateful for your help in improving them
>   mod = load_module(part_fqname, fh, filename, desc)
> ../<>/nibabel/nifti1.py:1590:
>  UserWarning: Multiple slice orders satisfy: sequential increasing, 
> alternating increasing, alternating decreasing 2. Choosing the first one
>   % ', '.join(matching_labels)
> SSS...SSS.S...S...S....S../<>/nibabel/streamlines/array_sequence.py:23:
>  FutureWarning: Conversion of the second argument of issubdtype from `bool` 
> to `np.generic` is deprecated. In future, it will be treated as `np.bool_ == 
> np.dtype(bool).type`.
>   np.issubdtype(obj.dtype, np.bool)))
> ./<>/nibabel/streamlines/tractogram.py:776: Warning: 
> Number of streamlines will be determined manually by looping through the 
> streamlines. If you know the actual number of streamlines, you might want to 
> set it beforehand via `self.header.nb_streamlines`.
>   " `self.header.nb_streamlines`.", Warning)
> 

Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

[Joseph Herlant]

Note that I'm having trouble with the latest release right now (see
https://github.com/PyCQA/pylint-django/issues/215) so I won't upload
it today.
But I should be able to get that fixed shortly.

Bug#917992: python3-ryu: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/bin/ryu

[Andreas Beckmann]

Package: python3-ryu
Version: 4.26+dfsg1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../python3-ryu_4.26+dfsg1-4_all.deb ...
  Unpacking python3-ryu (4.26+dfsg1-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-ryu_4.26+dfsg1-4_all.deb (--unpack):
   trying to overwrite '/usr/bin/ryu', which is also in package ryu-bin 
4.4+dfsg1-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-ryu_4.26+dfsg1-4_all.deb


cheers,

Andreas


ryu-bin=4.4+dfsg1-2_python3-ryu=4.26+dfsg1-4.log.gz
Description: application/gzip

Bug#917990: libplplotada1-dev: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/ada/adalib/plplotada/plplot_auxiliary.ali

[Andreas Beckmann]

Package: libplplotada1-dev
Version: 5.14.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libplplotada1-dev_5.14.0+dfsg-1_amd64.deb ...
  Unpacking libplplotada1-dev (5.14.0+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libplplotada1-dev_5.14.0+dfsg-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/ada/adalib/plplotada/plplot_auxiliary.ali', which is 
also in package libplplot-ada-dev:amd64 5.13.0+dfsg-9
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libplplotada1-dev_5.14.0+dfsg-1_amd64.deb


cheers,

Andreas


libplplot-ada-dev=5.13.0+dfsg-9_libplplotada1-dev=5.14.0+dfsg-1.log.gz
Description: application/gzip

Bug#917988: libodb-api-dev: file conflict with libodb-dev: /usr/lib/x86_64-linux-gnu/libodb.so

[Andreas Beckmann]

Package: libodb-api-dev
Version: 0.18.1-1
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 libodb-api-dev:amd64.
  Preparing to unpack .../48-libodb-api-dev_0.18.1-1_amd64.deb ...
  Unpacking libodb-api-dev:amd64 (0.18.1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-uOE0lB/48-libodb-api-dev_0.18.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libodb.so', which is also in 
package libodb-dev 2.4.0-1+b1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-uOE0lB/48-libodb-api-dev_0.18.1-1_amd64.deb


cheers,

Andreas


libodb-dev=2.4.0-1+b1_libodb-api-dev=0.18.1-1.log.gz
Description: application/gzip

Processed: Re: Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream
Bug #917717 [src:pylint-django] pylint-django: FTBFS: dh_auto_test: pybuild 
--test --test-pytest -i python{version} -p 3.7 returned exit code 13
Added tag(s) fixed-upstream.

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

Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

[Joseph Herlant]

Control: tags -1 + fixed-upstream

Reading through the changes of 2.0.1 to 2.0.5 of pylint-django, it
seems that this change has already been dealt with in the latest
version.
See: 
https://github.com/PyCQA/pylint-django/commit/c0408d7b844f46cf675986576ea2acaf4fd234cc#diff-caeb1acca0adc7ada7d03b9e07452774
So please don't get mad if I drop your patch. ;)

Thanks
Joseph

Bug#917987: libpillowfight: FTBFS (missing build-depends on cmake)

[Santiago Vila]

Package: src:libpillowfight
Version: 0.2.4-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-arch
dh build-arch -p python3-pypillowfight --with python3
   dh_testdir -a -O-ppython3-pypillowfight
   dh_update_autotools_config -a -O-ppython3-pypillowfight
   dh_autoreconf -a -O-ppython3-pypillowfight
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
sed 's,@DEB_VERSION_UPSTREAM@,0.2.4,g' debian/_version.h.in > 
src/pillowfight/_version.h
dh_auto_configure -p libpillowfight -p libpillowfight-dev -O--buildsystem=cmake 
-- -DLIBDIR=lib/x86_64-linux-gnu
install -d obj-x86_64-linux-gnu
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-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 -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DLIBDIR=lib/x86_64-linux-gnu ..
Can't exec "cmake": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 475.
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-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 -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DLIBDIR=lib/x86_64-linux-gnu .. 
failed to execute: No child processes
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-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 -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DLIBDIR=lib/x86_64-linux-gnu .. 
returned exit code 2
make[1]: *** [debian/rules:29: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -B" on amd64
but it also fails here on other architectures:

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

[ Based on the error message, it seems there is a missing build-depends on 
cmake,
  but I'm not 100% sure ].

Thanks.

Bug#917904: tightvncserver does not ask for password set by vncpasswd

[Ola Lundqvist]

Hi Jan

Thank you for the report.
I have now tested this myself. I purged all vnc software installed,
installed tightvncserver, run tightvncserver and then run vncpasswd to set
a password.
I failed to reproduce the problem. I'm asked for a password.

So the question is what you did differently. Can it be so that you have
some other vncpasswd software as an alternative and that happen to not be
updating the same things?

Best regards

// Ola

On Mon, 31 Dec 2018 at 15:33, Jan Christoph Terasa 
wrote:

> Package: tightvncserver
> Version: 1:1.3.9-9
> Severity: grave
> Tags: security
> Justification: user security hole
>
> Dear Maintainer,
>
> I installed tightvncserver on my VPS machine via apt. This did set up
> tightvncserver as an alternative for vncserver. Using a normal user
> account and
> starting vncserver for the first time asks for a 8-letter password. My
> assumption
> is this password will be used to authenticate users when connecting to the
> vnc
> server.
>
> After starting the vnc server via vncserver script, it is served on port
> 5901.
> On the client machine I use vinagre to connect to the server on port 5901.
> When
> connecting, I am not asked for a password, but rather directly taken to
> the X
> session. I would have expected the server to ask for the password I
> specified
> earlier.
>
> As a workaround, to ensure the integrity of the system, I set up iptable
> rules to
> not allow direct WAN connections to this port, but only allow local
> connections
> and use an SSH tunnel for connecting to the vnc server.
>
>
> kind regards,
> Christoph
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers oldstable-updates
>   APT policy: (500, 'oldstable-updates'), (500, 'testing'), (500,
> 'oldstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.14.17--std-ipv6-64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages tightvncserver depends on:
> ii  libc62.27-8
> ii  libjpeg62-turbo  1:1.5.2-2+b1
> ii  libx11-6 2:1.6.7-1
> ii  libxext6 2:1.3.3-1+b2
> ii  perl 5.28.0-3
> ii  x11-common   1:7.7+19
> ii  x11-utils7.7+4
> ii  xauth1:1.0.10-1
> ii  xserver-common   2:1.20.3-1
> ii  zlib1g   1:1.2.11.dfsg-1
>
> Versions of packages tightvncserver recommends:
> ii  x11-xserver-utils  7.7+8
> ii  xfonts-base1:1.0.4+nmu1
>
> Versions of packages tightvncserver suggests:
> pn  tightvnc-java  
>
> -- no debconf information
>


-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comFolkebogatan 26\
|  o...@debian.org   654 68 KARLSTAD|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---

Processed: Re: Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - fixed
Bug #917717 [src:pylint-django] pylint-django: FTBFS: dh_auto_test: pybuild 
--test --test-pytest -i python{version} -p 3.7 returned exit code 13
Removed tag(s) fixed.
> tags -1 + patch
Bug #917717 [src:pylint-django] pylint-django: FTBFS: dh_auto_test: pybuild 
--test --test-pytest -i python{version} -p 3.7 returned exit code 13
Added tag(s) patch.

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

Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

[Joseph Herlant]

Control: tags -1 - fixed
Control: tags -1 + patch
Hi guys,

Thanks Lucas for the report. Sorry for the late reply, I was out of
the country with very limited internet access.

Thanks Emmanuel for the quick patch.
Notes for next time:
 * Please use meaningful commit messages, especially when committing
to the master branch of a package you don't maintain. Using commit
messages like "fix issue 917717" makes the commit history harder to
read and the use of tools like gbp dch impossible as well as rendering
the gitlab hooks in place for tagging the bugs as pending unusable.
(If you're not sure about your patches, please just create a MR and
the maintainer can help getting the patch to a better standard)
 * Please conform to the DEP-3 headers when you are writing a quilt
patch header. See https://dep-team.pages.debian.net/deps/dep3/
 * If you have a patch that you thing is good enough for Debian, it's
generally a good practice to propose it upstream as upstream is
generally aware of the potential negative impacts and this would avoid
having to maintain diverging patch hell, especially on packages you
don't maintain.
 * Please don't tag bugs as "fixed" as long as there's no NMU uploaded
(as long as the package is not in the archive). In your case the tag
"patch" seems more appropriate.

There is an upstream upgrade I need to do so I'll clean the previous
points and do the upload today or tomorrow.

Thanks,
Joseph

Bug#917961: marked as done (nodejs: missing shlibs prevents build-dependencies on libnode-dev from working correctly)

[Debian Bug Tracking System]

Your message dated Wed, 2 Jan 2019 01:17:04 +0100
with message-id 

and subject line Re: [Pkg-javascript-devel] Bug#917961: nodejs: missing shlibs 
prevents build-dependencies on libnode-dev from working correctly
has caused the Debian Bug report #917961,
regarding nodejs: missing shlibs prevents build-dependencies on libnode-dev 
from working correctly
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.)


-- 
917961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nodejs
Version: 10.15.0~dfsg-5
Severity: serious
Justification: Policy 8.6

This is a reminder.

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

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

Versions of packages nodejs depends on:
ii  libc-ares2 1.14.0-1
ii  libc6  2.28-4
ii  libgcc11:8.2.0-13
ii  libicu63   63.1-5
ii  libnghttp2-14  1.35.1-1
ii  libnode64  10.15.0~dfsg-5
ii  libssl1.1  1.1.1a-1
ii  libstdc++6 8.2.0-13
ii  libuv1 1.24.0-1
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages nodejs recommends:
ii  ca-certificates  20180409
ii  nodejs-doc   10.15.0~dfsg-4

nodejs suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
reassign -1 node-gyp
fixed -1 3.8.0-2

Le mar. 1 janv. 2019 à 19:03, Jérémy Lal  a écrit :

> Package: nodejs
> Version: 10.15.0~dfsg-5
> Severity: serious
> Justification: Policy 8.6
>
> This is a reminder.



That was a bug in node-gyp not linking to "libnode" by default.

Jérémy
--- End Message ---

Bug#917975: marked as done (libeclipse-jdt-debug-ui-java: Depends: libeclipse-debug-core-java (>= 3.15) but 3.13.100+eclipse4.10-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Wed, 02 Jan 2019 00:05:26 +
with message-id 
and subject line Bug#917975: fixed in eclipse-jdt-debug 4.10-2
has caused the Debian Bug report #917975,
regarding libeclipse-jdt-debug-ui-java: Depends: libeclipse-debug-core-java (>= 
3.15) but 3.13.100+eclipse4.10-1 is to be installed
to be marked as done.

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

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


-- 
917975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libeclipse-jdt-debug-ui-java
Version: 3.10.100+eclipse4.10-1
Severity: serious

The following packages have unmet dependencies:
 libeclipse-jdt-debug-ui-java : Depends: libeclipse-debug-core-java (>= 3.15) 
but 3.13.100+eclipse4.10-1 is to be installed
--- End Message ---
--- Begin Message ---
Source: eclipse-jdt-debug
Source-Version: 4.10-2

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated eclipse-jdt-debug 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Jan 2019 00:33:09 +0100
Source: eclipse-jdt-debug
Binary: libeclipse-jdt-debug-java libeclipse-jdt-debug-ui-java 
libeclipse-jdt-launching-java
Architecture: source
Version: 4.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libeclipse-jdt-debug-java - Eclipse JDI Debug Model
 libeclipse-jdt-debug-ui-java - Eclipse JDI Debug UI
 libeclipse-jdt-launching-java - Eclipse Java Development Tools Launching 
Support
Closes: 917975
Changes:
 eclipse-jdt-debug (4.10-2) unstable; urgency=medium
 .
   * Fixed the dependencies of libeclipse-jdt-debug-ui-java (Closes: #917975)
Checksums-Sha1:
 ad7885d74d2df1be8231dfea684508e9a481d819 3114 eclipse-jdt-debug_4.10-2.dsc
 3426898d4ab78ec3939e5250c225bfe296bb80fd 7488 
eclipse-jdt-debug_4.10-2.debian.tar.xz
 f0949dd28ff63fcc0e023764fa864fe76becc1bb 15430 
eclipse-jdt-debug_4.10-2_source.buildinfo
Checksums-Sha256:
 da3a640648369cdab7a3bd61533ba27f2bf001279b263ecc4a7fe7502c380106 3114 
eclipse-jdt-debug_4.10-2.dsc
 dc425910d9ed864f8809d91cea0d231c8b440050d824fda9e2c3009eebf4d6a1 7488 
eclipse-jdt-debug_4.10-2.debian.tar.xz
 51b1c4249dc867e9712a423ee91c2c46305704e4c620b9ac197d590f148bcc52 15430 
eclipse-jdt-debug_4.10-2_source.buildinfo
Files:
 48c63aac8de88d27b50fa4bc9613859f 3114 java optional 
eclipse-jdt-debug_4.10-2.dsc
 ac12f6c1cc46f1fc556aab15e714fc73 7488 java optional 
eclipse-jdt-debug_4.10-2.debian.tar.xz
 4be6feddf81f2e48c1dbbb08981d504a 15430 java optional 
eclipse-jdt-debug_4.10-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlwr+q4SHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCshboQAJvAUISw7pAxIIAmhvOf73wzuM0AIPiA
QYdWjw7XXxN1DaxXG6W7CKJFE6VVaeOoAaA7oyNFRsXv78RsgG4Hum1Y4feC+4yi
S7q7bL7Mts8M16bhqzhBL80IS8xz/sWmDMNVScyVlQlxwPhT/W67qfn6OszA2RCw
9oRYy50lsAhDFDSdPwDbmxc3100DHp5ur/GbU2s9hCJPA82rSRdVh7fKSvBx7hyU
Bf9M/pwTP9zE2iNql+TV3Xr4osk4sbZVaXyzkGeR6fYEil3X51g7WIEFjmKUjX5H
ICSEOfVEQUmcnG87xizWYOP0Ch4k6qvF2quMhQetfCfylEqBLPBNMTmT45xd9++Q
4aozD7JJ51DQI9eNz8DmBbTPB/k5h4rbA9IgEdG80DH7TJBhmGzWosZ9r9W2lI1C
Y8BR+xECCHw5SIasKjBV/cEJe5KWeuma01FUZ85m7VrgmkcSFT8HsapAY1q/Lfmx
wbg0AU1WoWCpMhsGioYBPARLFOiBySbI/SZP5wAlsaVE0ZW4MPQmP4eZxICALktI
DyBr1sqyb2rhj7yCVfWMg8TA8SIGB3VeqtqG8E70CGA2rYX8G9QWJJQD6hHTRnbb
/ZxPhcElQW7IXgls23HpAWaOvaH+blProjXAXp/rKkP+mG9h6sHzPg7LAE8y3gQh
dlMVc8VW11/f
=i0rM
-END PGP SIGNATURE End Message ---

Processed: fixed 913106 in 0.11.0-1

[Debian Bug Tracking System]

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

> fixed 913106 0.11.0-1
Bug #913106 {Done: "A. Maitland Bottoms" } [comedilib] 
comedilib: FTBFS with glibc 2.28, upstream cherrypick fix attached
There is no source info for the package 'comedilib' at version '0.11.0-1' with 
architecture ''
Unable to make a source version for version '0.11.0-1'
Marked as fixed in versions 0.11.0-1.
> thanks
Stopping processing here.

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

Bug#917869: python-escript FTBFS on armhf, mips, mipsel and mips64el

[Adrian Bunk]

On Mon, Dec 31, 2018 at 06:51:12AM +, peter green wrote:
>... while the mips and mipsel builds ran out of virtual memory.
> 
> It may be worth playing with the settings, the first thing to try is probably 
> -Wl,-no-keep-memory , if that fails it may be worth trying optimising for 
> size ( -Os instead of -O2 )

I'd be surprised if -Os would help.

Most of the time the mips/mipsel build can be fixed by appending -g1 to 
the CXXFLAGS, overwriting the default -g (which is -g2).

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#917788: libmedc11: Overwrites a file from libmedc1v5

[Andreas Beckmann]

On Sun, 30 Dec 2018 09:21:03 -0600 Kurt Kremitzki  wrote:
> I was just about to open a bug on this same issue. It's actually present
> in both libmed11 and libmedc11. Instead of Conflicts, they both need
> Breaks + Replaces, see Policy 7.6 [1] or #906110 [2] for a similar

In this special case, you probably need to add
  Breaks+Replaces: libmed1v5 (>= 4)
respectively
  Breaks+Replaces: libmedc1v5 (>= 4)
since the versions before 4 should not have any file conflicts.


Andreas

Processed: Bug #917975 in eclipse-jdt-debug marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #917975 [libeclipse-jdt-debug-ui-java] libeclipse-jdt-debug-ui-java: 
Depends: libeclipse-debug-core-java (>= 3.15) but 3.13.100+eclipse4.10-1 is to 
be installed
Added tag(s) pending.

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

Bug#917975: Bug #917975 in eclipse-jdt-debug marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #917975 in eclipse-jdt-debug reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/java-team/eclipse-jdt-debug/commit/764f7e91346878fa2d6d25163b7fe52383d9a54b


Fixed the dependencies of libeclipse-jdt-debug-ui-java (Closes: #917975)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/917975

Bug#917945: marked as done (rust-rand-0.5: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Tue, 01 Jan 2019 23:35:34 +
with message-id 
and subject line Bug#917945: fixed in rust-rand-0.5 0.5.5-2
has caused the Debian Bug report #917945,
regarding rust-rand-0.5: Incomplete debian/copyright?
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.)


-- 
917945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-rand-0.5
Version: 0.5.5-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Wolfgang Silbermayr , 
ftpmas...@debian.org

Hi,

I just ACCEPTed rust-rand-0.5 from NEW but noticed it was missing 
attribution in debian/copyright for at least src/rngs/jitter.rs.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: rust-rand-0.5
Source-Version: 0.5.5-2

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

Debian distribution maintenance software
pp.
Wolfgang Silbermayr  (supplier of updated rust-rand-0.5 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed,  2 Jan 2019 00:11:53 CET
Source: rust-rand-0.5
Binary: librust-rand-0.5-dev librust-rand-0.5+alloc-dev 
librust-rand-0.5+cloudabi-dev librust-rand-0.5+fuchsia-zircon-dev 
librust-rand-0.5+libc-dev librust-rand-0.5+log-dev librust-rand-0.5+serde-dev 
librust-rand-0.5+serde1-dev librust-rand-0.5+serde-derive-dev 
librust-rand-0.5+std-dev librust-rand-0.5+stdweb-dev librust-rand-0.5+winapi-dev
Architecture: amd64 source
Version: 0.5.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Wolfgang Silbermayr 
Description: 
 librust-rand-0.5-dev - Randomness functionality and number generators - Rust 
source code
 librust-rand-0.5+alloc-dev - Randomness functionality and number generators - 
feature "alloc"
 librust-rand-0.5+cloudabi-dev - Randomness functionality and number generators 
- feature "cloudab
 librust-rand-0.5+fuchsia-zircon-dev - Randomness functionality and number 
generators - feature "fuchsia
 librust-rand-0.5+libc-dev - Randomness functionality and number generators - 
feature "libc"
 librust-rand-0.5+log-dev - Randomness functionality and number generators - 
feature "log"
 librust-rand-0.5+serde-dev - Randomness functionality and number generators - 
feature "serde"
 librust-rand-0.5+serde1-dev - Randomness functionality and number generators - 
feature "serde1"
 librust-rand-0.5+serde-derive-dev - Randomness functionality and number 
generators - feature "serde_d
 librust-rand-0.5+std-dev - Randomness functionality and number generators - 
feature "std"
 librust-rand-0.5+stdweb-dev - Randomness functionality and number generators - 
feature "stdweb"
 librust-rand-0.5+winapi-dev - Randomness functionality and number generators - 
feature "winapi"
Closes: 917945
Changes:
 rust-rand-0.5 (0.5.5-2) unstable; urgency=medium
 .
   * Package rand 0.5.5 from crates.io using debcargo 2.2.9
   * Add missing licensing information (Closes: #917945)
Checksums-Sha256: 
 67b35a69d33b7ecd02c3438088814e4c820f0738bfc7844739fe15dd09bf941d 1048 
librust-rand-0.5+alloc-dev_0.5.5-2_amd64.deb
 8d06ccac3f74e2211231746c596ad48d4a88e63da1213619f596e95498d35236 1056 
librust-rand-0.5+cloudabi-dev_0.5.5-2_amd64.deb
 33faf90a422d54ac3b46392cb56ba520957ffa00789b22c5279113f49b7e4d39 1076 
librust-rand-0.5+fuchsia-zircon-dev_0.5.5-2_amd64.deb
 45a25e34e629e9a41fa5d8160da405d9b82c86beefb3bec864a5413e3eea91f1 1048 
librust-rand-0.5+libc-dev_0.5.5-2_amd64.deb
 592d50a263a5a107eeb3211f303f00b45f05dcb88c0250a3fdcaa5ea473a57b4 1048 
librust-rand-0.5+log-dev_0.5.5-2_amd64.deb
 f5585c50361c89f2ae09311f32a0198a47fa7b879d066ed5c48d7fcddbd8a051 1056 
librust-rand-0.5+serde-derive-dev_0.5.5-2_amd64.deb
 dbf046b036394548787e9763b630e0834086b94a4b759ac8678112d9fa9f4f76 1048 
librust-rand-0.5+serde-dev_0.5.5-2_amd64.deb
 

Processed: tagging 916123

[Debian Bug Tracking System]

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

> tags 916123 + buster sid
Bug #916123 [src:grcompiler] grcompiler: Please use pkg-config to detect icu
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: reassign 916123 to src:grcompiler

[Debian Bug Tracking System]

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

> reassign 916123 src:grcompiler 4.2-6
Bug #916123 [grcompiler] grcompiler: Please use pkg-config to detect icu
Bug reassigned from package 'grcompiler' to 'src:grcompiler'.
No longer marked as found in versions grcompiler/4.2-6.
Ignoring request to alter fixed versions of bug #916123 to the same values 
previously set
Bug #916123 [src:grcompiler] grcompiler: Please use pkg-config to detect icu
Marked as found in versions grcompiler/4.2-6.
> thanks
Stopping processing here.

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

Processed: chai 4is now in unstable

[Debian Bug Tracking System]

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

> reassign 884155 src:node-object-path 0.11.3-1
Bug #884155 {Done: Pirate Praveen } [node-object-path] 
FTBFS with chai 4.1.2 in experimental
Bug reassigned from package 'node-object-path' to 'src:node-object-path'.
No longer marked as found in versions node-object-path/0.11.3-1.
No longer marked as fixed in versions node-object-path/0.11.4-1.
Bug #884155 {Done: Pirate Praveen } [src:node-object-path] 
FTBFS with chai 4.1.2 in experimental
Marked as found in versions node-object-path/0.11.3-1.
> fixed 884155 0.11.4-1
Bug #884155 {Done: Pirate Praveen } [src:node-object-path] 
FTBFS with chai 4.1.2 in experimental
Marked as fixed in versions node-object-path/0.11.4-1.
> severity 884155 serious
Bug #884155 {Done: Pirate Praveen } [src:node-object-path] 
FTBFS with chai 4.1.2 in experimental
Severity set to 'serious' from 'important'
> tags 884155 buster sid
Bug #884155 {Done: Pirate Praveen } [src:node-object-path] 
FTBFS with chai 4.1.2 in experimental
Added tag(s) buster and sid.
> forcemerge 884155 917757
Bug #884155 {Done: Pirate Praveen } [src:node-object-path] 
FTBFS with chai 4.1.2 in experimental
Bug #917757 [src:node-object-path] node-object-path: FTBFS: tests failed
Set Bug forwarded-to-address to 
'https://github.com/mariocasciaro/object-path/issues/91'.
Marked Bug as done
Marked as fixed in versions node-object-path/0.11.4-1.
Merged 884155 917757
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 917511 src:harvest-tools
Bug #917511 [harvest-tools] harvest-tools FTBFS, "This code requires C++14. 
Either your compiler does not support it or it is not enabled."
Bug reassigned from package 'harvest-tools' to 'src:harvest-tools'.
No longer marked as found in versions harvest-tools/1.3-3.
Ignoring request to alter fixed versions of bug #917511 to the same values 
previously set
> forcemerge 917689 917511
Bug #917689 [src:harvest-tools] harvest-tools: FTBFS: configure: error: Cap'n 
Proto headers not found.
Bug #917511 [src:harvest-tools] harvest-tools FTBFS, "This code requires C++14. 
Either your compiler does not support it or it is not enabled."
Severity set to 'serious' from 'normal'
Marked as found in versions harvest-tools/1.3-3.
Bug #917689 [src:harvest-tools] harvest-tools: FTBFS: configure: error: Cap'n 
Proto headers not found.
Added tag(s) patch.
Merged 917511 917689
> thanks
Stopping processing here.

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

Bug#914607: marked as done (plaso depends on cruft package python-dfwinreg)

[Debian Bug Tracking System]

Your message dated Tue, 01 Jan 2019 23:04:09 +
with message-id 
and subject line Bug#914607: fixed in dfwinreg 20181214-2
has caused the Debian Bug report #914607,
regarding plaso depends on cruft package python-dfwinreg
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.)


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

Package: plaso
Version: 1.5.1+dfsg-4
Severity: serious

plaso depends on python-dfwinreg which is no longer built by the dfwinreg 
source package.
--- End Message ---
--- Begin Message ---
Source: dfwinreg
Source-Version: 20181214-2

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated dfwinreg 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, 21 Dec 2018 22:58:24 +0100
Source: dfwinreg
Binary: python-dfwinreg python3-dfwinreg
Architecture: source all
Version: 20181214-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Hilko Bengen 
Description:
 python-dfwinreg - Digital Forensics Windows Registry library for Python 2
 python3-dfwinreg - Digital Forensics Windows Registry library for Python 3
Closes: 914607
Changes:
 dfwinreg (20181214-2) unstable; urgency=medium
 .
   * watch: Mangle download filename
   * Re-add python2 package (Closes: #914607)
Checksums-Sha1:
 6474b9bf58c4cafce1da596a2335df2ed2943691 2376 dfwinreg_20181214-2.dsc
 239b61e2fffba7b65f4ab1a2cbc1437871ad2908 2848 dfwinreg_20181214-2.debian.tar.xz
 bb685251827191ce4da8c7bba7828b5026ff77d9 6979 
dfwinreg_20181214-2_amd64.buildinfo
 9231e2ab837f9953012fdad5c40858230cb9 15652 
python-dfwinreg_20181214-2_all.deb
 ff0f943b8bbee5679a17035a7b2c87d31d52089e 15756 
python3-dfwinreg_20181214-2_all.deb
Checksums-Sha256:
 2eb2711fb8959474e8ff779a4caa36ec98478a3973579e575d515f863b8ce4a2 2376 
dfwinreg_20181214-2.dsc
 cd271b20c76c0f197f4a33265263c650af9e0992bc611e9875c16b74555de829 2848 
dfwinreg_20181214-2.debian.tar.xz
 fa0bbd40c362d2e0a568c6f33088c957a7aecfd52eafd4848b3fc59ad837 6979 
dfwinreg_20181214-2_amd64.buildinfo
 d5536e8ae6d9e2e73a0eb018b6524e209eedb64a80886c3034510db7a0772a4d 15652 
python-dfwinreg_20181214-2_all.deb
 c2642613c15a61da0fedb5b667fcf24fd849b05da7a3ba2ae2d33bf2374dd448 15756 
python3-dfwinreg_20181214-2_all.deb
Files:
 a7e1ff23306075947d73b4231d356542 2376 python optional dfwinreg_20181214-2.dsc
 65f2b056a0314f74bd9897217d65b3f0 2848 python optional 
dfwinreg_20181214-2.debian.tar.xz
 4c72ff5ab6def71ee11686460cf08af8 6979 python optional 
dfwinreg_20181214-2_amd64.buildinfo
 fa7a5bb8d36f900d7a1de416b1455508 15652 python optional 
python-dfwinreg_20181214-2_all.deb
 612e7a58b85d84d646f9c3b4f4316f88 15756 python optional 
python3-dfwinreg_20181214-2_all.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlwet9ESHGJlbmdlbkBk
ZWJpYW4ub3JnAAoJEHW3EGNcITp+0J8QAIs/OTYx8GmZZdLoKO3y62qV3Yly/Zxf
Jg7yx/h6X+xeeiwyCRCf3RVvwvPIWSt2t7xQe8t+PdIttMZ4SoPenqK9cS5+LLpP
nPPpDJkn/dAvVjLqB4ZGehxWpWmyR4ImLuHtgAXvX/gNx2NAmocZZgh9yfqMcsC4
1rSmUkIsOSL4OsC6NgkPbQSojgat1tRRz+1P5Ga3DrnKnYPIfSRTXRjPfC8MDjMC
S6kHUgyiDbE0KB8S7rCbHZeEskPPwHgtGHANq/g0fQMYzSuXpxlRxRK3tN7h1hUV
3YsmV8MADcErqCqtOE6a0VlI3G3Diq2dh1jb+7jhBH6rg29hy6E3cxvHV4sTyTCS
Y/gWOzvuH102/rUlBsJeJAOCr0AYrW9xvcpuh9GofZl9VuEQUv+pHHzU9RWVcGzH
LF598kJspzgsf/pHEhaCPDmGYlWHD63D1bs0F+ikb+IqGqxdAAWQQGC5nwBefgSF
JnfOb+dcanOaEuADSVaaDB2k5DL9Iz1Ge/dKgAy9+xf1vdku5q79w1qyef2mgnFG
QkwkYQ5wEa8QvBJ1XH5kj6WUy6kOd0sTCPNMV83w95HssUpDHrYEMdfk9XjkZuiA
79MyRhQUGE6+5e5GdfKGTDFHgA1WeR/Wv9JVi7zJwioJUS2uCNaQZWtwPp9jsAes
dRwHddtTtSxK
=dubP
-END PGP SIGNATURE End Message ---

Processed: severity of 917143 is serious

[Debian Bug Tracking System]

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

> severity 917143 serious
Bug #917143 [src:t-coffee] t-coffee breaks 
libbio-tools-run-alignment-tcoffee-perl autopkgtest: COREDUMP
Bug #917719 [src:t-coffee] libbio-tools-run-alignment-tcoffee-perl: FTBFS: 
dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 917699 src:mlton
Bug #917699 [src:urweb] urweb: FTBFS: build-dependency not installable: mlton
Bug reassigned from package 'src:urweb' to 'src:mlton'.
No longer marked as found in versions urweb/20170720+dfsg-2.
Ignoring request to alter fixed versions of bug #917699 to the same values 
previously set
> forcemerge 904475 917699
Bug #904475 [src:mlton] mlton: build-depends on the version of itself that is 
going to be built
Bug #917699 [src:mlton] urweb: FTBFS: build-dependency not installable: mlton
Added indication that 917699 affects 
mlton-runtime-x86-64-linux-gnu,mlton-compiler
Marked as found in versions mlton/20180207-1.
Bug #904475 [src:mlton] mlton: build-depends on the version of itself that is 
going to be built
Added tag(s) sid and buster.
Merged 904475 917699
> affects 904475 src:urweb
Bug #904475 [src:mlton] mlton: build-depends on the version of itself that is 
going to be built
Bug #917699 [src:mlton] urweb: FTBFS: build-dependency not installable: mlton
Added indication that 904475 affects src:urweb
Added indication that 917699 affects src:urweb
> thanks
Stopping processing here.

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

Bug#917687: [3dprinter-general] Bug#917687: cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pth

[Adrian Bunk]

Control: reassign -1 libpolyclipping-dev
Control: forcemerge 917057 -1

On Sun, Dec 30, 2018 at 10:12:34AM +0100, Gregor Riepl wrote:
> Thanks for the bug report.
> 
> Building the package used to work fine, so I'm suspecting the pthread
> detection scripts have started failing with glibc 2.28, which was updated
> recently.

There is no pthread detection issue, the problem is that blind pasting 
of the tail of the build log often only contains unrelated noise.

> I will look into the issue.
> If you have any idea why it might be occurring, please share.

The actual error is in #917057, which was already correctly marked as 
affecting src:cura-engine.

cu
Adrian

-- 

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

Processed: Re: Bug#917687: [3dprinter-general] Bug#917687: cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined re

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libpolyclipping-dev
Bug #917687 [src:cura-engine] cura-engine: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
 undefined reference to `pthread_create'
Bug reassigned from package 'src:cura-engine' to 'libpolyclipping-dev'.
No longer marked as found in versions cura-engine/1:3.3.0-2.1.
Ignoring request to alter fixed versions of bug #917687 to the same values 
previously set
> forcemerge 917057 -1
Bug #917057 [libpolyclipping-dev] libpolyclipping-dev: pkg-config file contains 
bogus includedir
Bug #917057 [libpolyclipping-dev] libpolyclipping-dev: pkg-config file contains 
bogus includedir
Added tag(s) buster and sid.
Bug #917687 [libpolyclipping-dev] cura-engine: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
 undefined reference to `pthread_create'
Added indication that 917687 affects src:cura-engine
Marked as found in versions libpolyclipping/6.4.2-4.
Added tag(s) patch.
Merged 917057 917687

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

Processed: affects 917660

[Debian Bug Tracking System]

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

> affects 917660 src:vim-youcompleteme
Bug #917660 [python3-hamcrest] vim-youcompleteme: FTBFS (failing tests)
Bug #917682 [python3-hamcrest] vim-youcompleteme: FTBFS: tests failed
Added indication that 917660 affects src:vim-youcompleteme
Added indication that 917682 affects src:vim-youcompleteme
> thanks
Stopping processing here.

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

Processed: forcibly merging 917657 917714

[Debian Bug Tracking System]

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

> forcemerge 917657 917714
Bug #917657 [src:lizzie] lizzie: FTBFS (autobuilder hangs)
Bug #917657 [src:lizzie] lizzie: FTBFS (autobuilder hangs)
Added tag(s) buster and sid.
Bug #917714 [src:lizzie] lizzie: FTBFS: dh_auto_test: 
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<>/lizzie-0.6\+dfsg1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/<>/lizzie-0.6\+dfsg1/debian 
-Dmaven.repo.local=/<>/lizzie-0.6\+dfsg1/debian/maven-repo 
--batch-mode test returned exit code 1
Added tag(s) ftbfs.
Merged 917657 917714
> thanks
Stopping processing here.

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

Processed: forcibly merging 917655 917667

[Debian Bug Tracking System]

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

> forcemerge 917655 917667
Bug #917655 [src:biojava4-live] biojava4-live: FTBFS (cannot find symbol 
JAXBContext)
Bug #917655 [src:biojava4-live] biojava4-live: FTBFS (cannot find symbol 
JAXBContext)
Added tag(s) buster and sid.
Bug #917667 [src:biojava4-live] biojava4-live: FTBFS: error: package 
javax.xml.bind.annotation does not exist
Added tag(s) ftbfs.
Merged 917655 917667
> thanks
Stopping processing here.

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

Processed: block 915069 with 917605

[Debian Bug Tracking System]

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

> block 915069 with 917605
Bug #915069 [libphp-predis] libphp-predis: Useless in Debian, superseded by 
php-nrk-predis
915069 was not blocked by any bugs.
915069 was not blocking any bugs.
Added blocking bug(s) of 915069: 917605
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 917593 src:roaraudio
Bug #917593 [src:mpd] mpd: FTBFS ('_IO_off64_t' has not been declared)
Bug reassigned from package 'src:mpd' to 'src:roaraudio'.
No longer marked as found in versions mpd/0.20.23-1.
Ignoring request to alter fixed versions of bug #917593 to the same values 
previously set
> forcemerge 915345 917593
Bug #915345 [src:roaraudio] roaraudio FTBFS with glibc 2.28
Bug #917593 [src:roaraudio] mpd: FTBFS ('_IO_off64_t' has not been declared)
Added indication that 917593 affects src:roarplaylistd,src:cmus
Marked as found in versions roaraudio/1.0~beta11-11.
Merged 915345 917593
> affects 915345 libroar-dev src:mpd
Bug #915345 [src:roaraudio] roaraudio FTBFS with glibc 2.28
Bug #917593 [src:roaraudio] mpd: FTBFS ('_IO_off64_t' has not been declared)
Added indication that 915345 affects libroar-dev and src:mpd
Added indication that 917593 affects libroar-dev and src:mpd
> thanks
Stopping processing here.

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

Bug#917545: marked as done (haskell-termonad: FTBFS in sid (Could not find module `Build_doctests'))

[Debian Bug Tracking System]

Your message dated Wed, 2 Jan 2019 00:11:34 +0200
with message-id <20190101221134.GM29139@localhost>
and subject line Fixed in 0.2.1.0-2
has caused the Debian Bug report #917545,
regarding haskell-termonad: FTBFS in sid (Could not find module 
`Build_doctests')
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.)


-- 
917545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-termonad
Version: 0.1.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
Linking dist-ghc/build/termonad-test/termonad-test ...
Preprocessing executable 'termonad' for termonad-0.1.0.0..
Building executable 'termonad' for termonad-0.1.0.0..
[1 of 1] Compiling Main ( app/Main.hs, 
dist-ghc/build/termonad/termonad-tmp/Main.o )
Linking dist-ghc/build/termonad/termonad ...
Preprocessing test suite 'doctests' for termonad-0.1.0.0..
Building test suite 'doctests' for termonad-0.1.0.0..
[1 of 1] Compiling Main ( test/DocTest.hs, 
dist-ghc/build/doctests/doctests-tmp/Main.o )

test/DocTest.hs:4:1: error:
Could not find module `Build_doctests'
Use -v to see a list of the files searched for.
  |
4 | import Build_doctests (flags, pkgs, module_sources)
  | ^^^
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

where you can get a full build log if you need it.

The error message suggests a missing build-depends, but if this is really
a bug in one of the build-depends, please use reassign and affects, so
that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Version: 0.2.1.0-2

Fixed in 0.2.1.0-2:
https://buildd.debian.org/status/package.php?p=haskell-termonad

cu
Adrian

-- 

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

Processed: fixed 917509 in 0.7.5-1

[Debian Bug Tracking System]

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

> fixed 917509 0.7.5-1
Bug #917509 {Done: Tommi Höynälänmaa } 
[src:theme-d-gnome] theme-d-gnome: FTBFS (dh_auto_configure fails)
Marked as fixed in versions theme-d-gnome/0.7.5-1.
> thanks
Stopping processing here.

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

Bug#916279: qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement

[Laurent Bigonville]

Le 1/01/19 à 21:35, Michael Tokarev a écrit :

01.01.2019 23:14, Laurent Bigonville wrote:
On Mon, 24 Dec 2018 09:34:16 +0300 Michael Tokarev  
wrote:



 > it doesn't really break the package in question. All these
 > packages will be of the same version anwyway, upgraded in
 > one go, at the very max there will be some docs missing
 > for a (short) while, until the next apt run.
 >
 > More, it's just one version which were like that during the
 > buster development cycle.
 >
 > Besides, *this* bug is fixed, it does declare a replacement :)

The usual way is to declare a Breaks/Replace when a file is moved 
between packages to prevent the file to be overwritten in case an 
older version of the package is installed.


I know the usual way, I just didn't think this is needed in this
particular case, as I explained before. At the very least, it is
a very minor issue, definitely not release critical.


 > I don't think this bug needs to be acted upon more. At least
 > I don't plan a new upload at least before it is migrated to
 > testing, as time is already too short and this very bug, a
 > stupid mistake, already took more time than necessary.

Well this bug has been reopened that mean that the package will never 
migrate


That's sort of unfortunate...


Indeed, it would be unfortunate to not have 3.1 in buster.

You could either close the bug if you are sure it will not cause an 
issue on upgrade, or maybe ask the release team?

Processed: tagging 917506

[Debian Bug Tracking System]

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

> tags 917506 + buster sid
Bug #917506 [src:python-crank] python-crank: FTBFS (failing tests)
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#917983: glib2.0: [experimental] FTBFS on arm64: tests/refcount/closures.c:298:main: assertion failed: (seen_thread2 != FALSE)

[Simon McVittie]

Source: glib2.0
Version: 2.58.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

A test fails on arm64:

START: /<>/debian/build/deb/tests/refcount/closures
init 0xfde2c210
.
.
.
.
c.
.
.
.
c.
.

stopping
stopped
**
GLib:ERROR:../../../tests/refcount/closures.c:298:main: assertion failed: 
(seen_thread2 != FALSE)

I've seen this before, in 2.54.2-3. If we run too many iterations, the
test times out; but if we run too few, the main thread starves the other
threads and the test gets through its intended number of iterations in
the main thread before the other threads have been scheduled at all, by
starving the other threads.

I'm very tempted to just knock out this particular test on arm*, at
least as a build-time test (it can stay as an autopkgtest, optionally
marked as flaky, if we want that).

smcv

Processed: Re: Bug#917493: fenix: FTBFS when built with dpkg-buildpackage -A

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #917493 [src:fenix] fenix: FTBFS when built with dpkg-buildpackage -A
Bug 917493 cloned as bug 917982
> retitle -2 fenix FTBFS with glibc 2.28
Bug #917982 [src:fenix] fenix: FTBFS when built with dpkg-buildpackage -A
Changed Bug title to 'fenix FTBFS with glibc 2.28' from 'fenix: FTBFS when 
built with dpkg-buildpackage -A'.

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

Bug#903448: closed by Josue Ortega (Bug#903448: fixed in asciinema 2.0.1-2)

[Andreas Beckmann]

Control: reopen -1

On 2018-12-29 17:21, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the ruby-websocket-parser,ruby-websocket package:
> 
> #903448: ruby-websocket-parser,ruby-websocket: error when trying to install 
> together

>  asciinema (2.0.1-2) unstable; urgency=medium>  .>* New maintainer 
> (Closes: #903448)
Wrong bug.


Andreas

Processed: Re: Bug#903448 closed by Josue Ortega (Bug#903448: fixed in asciinema 2.0.1-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #903448 [ruby-websocket-parser,ruby-websocket] 
ruby-websocket-parser,ruby-websocket: error when trying to install together
Bug 903448 is not marked as done; doing nothing.

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

Bug#917493: fenix: FTBFS when built with dpkg-buildpackage -A

[Adrian Bunk]

Control: clone -1 -2
Control: retitle -2 fenix FTBFS with glibc 2.28

On Fri, Dec 28, 2018 at 03:36:08PM +0100, Santiago Vila wrote:
> I wrote:
> 
> > but it also fails here:
> > 
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fenix.html
> 
> Please disregard this part of my report.
> 
> Reproducible builds always do "dpkg-buildpackage", so whatever
> happens in reproducible-builds is irrelevant in this case, because we
> know no amd64 .deb will be generated.
> 
> This report is only about "dpkg-buildpackage -A", which in theory must
> still work and in practice should not be very difficult to achieve
> (well, I hope so).

The fmul issue is an unrelated second issue, I'm cloning a bug for that one.

> Tbanks.

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#917980: glib2.0: [experimental] FTBFS on s390x: glib/gvariant-serialiser.c:174:g_variant_serialised_check: assertion failed (alignment & (gsize) serialised.data == 0): (4 == 0)

[Simon McVittie]

Source: glib2.0
Version: 2.58.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

A test fails on s390x. I think this is probably to do with either the
post-2.58.2 patches that I applied, or the GVariant fuzzing fixes in
2.58.2; it might be correlated with s390x being the only 64-bit big-endian
release architecture, or might be a quirk of s390x malloc, or might be
coincidence. (I'm glad I uploaded this to experimental first.)

It's reproducible on zelenka:

#0  0x03fffda3e66e in raise () from /lib/s390x-linux-gnu/libc.so.6
#1  0x03fffda23cec in abort () from /lib/s390x-linux-gnu/libc.so.6
#2  0x03fffde7da46 in g_assertion_message 
(domain=domain@entry=0x3fffdea47d6 "GLib",
file=file@entry=0x3fffdf063f6 "../../../glib/gvariant-serialiser.c", 
line=line@entry=174,
func=func@entry=0x3fffdf0674c <__FUNCTION__.6010> 
"g_variant_serialised_check",
message=message@entry=0x10054f190 "assertion failed (alignment & (gsize) 
serialised.data == 0): (4 == 0)")
at ../../../glib/gtestutils.c:2596
#3  0x03fffde7de20 in g_assertion_message_cmpnum (domain=0x3fffdea47d6 
"GLib",
file=0x3fffdf063f6 "../../../glib/gvariant-serialiser.c", line=,
func=0x3fffdf0674c <__FUNCTION__.6010> "g_variant_serialised_check", 
expr=,
arg1=, cmp=0x3fffdea9954 "==", arg2=, 
numtype=105 'i')
at ../../../glib/gtestutils.c:2652
#4  0x03fffde9ad4e in g_variant_serialised_check (serialised=...) at 
../../../glib/gvariant-serialiser.c:174
#5  0x03fffde9b12c in g_variant_serialised_n_children (serialised=...)
at ../../../glib/gvariant-serialiser.c:1359
#6  0x03fffde96090 in g_variant_n_children (value=value@entry=0x1009a32d0) 
at ../../../glib/gvariant-core.c:950
#7  0x03fffde916f4 in g_variant_iter_init (iter=iter@entry=0x3ffeca0, 
value=value@entry=0x1009a32d0)
at ../../../glib/gvariant.c:2976
#8  0x03fffde92a84 in g_variant_deep_copy (value=value@entry=0x1009a32d0) 
at ../../../glib/gvariant.c:5797
#9  0x03fffde95356 in g_variant_get_normal_form (value=0x1009a32d0) at 
../../../glib/gvariant.c:5891
#10 0x00018696 in test_normal_checking_tuple_offsets () at 
../../../glib/tests/gvariant.c:4941
#11 0x03fffde7d4ea in test_case_run (tc=0x10002b0d0) at 
../../../glib/gtestutils.c:2318
#12 g_test_run_suite_internal (suite=suite@entry=0x100028580, 
path=path@entry=0x0)
at ../../../glib/gtestutils.c:2403
#13 0x03fffde7d370 in g_test_run_suite_internal 
(suite=suite@entry=0x100028440, path=path@entry=0x0)
at ../../../glib/gtestutils.c:2415
#14 0x03fffde7d370 in g_test_run_suite_internal 
(suite=suite@entry=0x100028420, path=0x0)
at ../../../glib/gtestutils.c:2415
#15 0x03fffde7d7aa in g_test_run_suite (suite=0x100028420) at 
../../../glib/gtestutils.c:2490
#16 0x03fffde7d7e0 in g_test_run () at ../../../glib/gtestutils.c:1755
#17 0x00017f5c in main (argc=, argv=) at 
../../../glib/tests/gvariant.c:5055

(gdb) p *variant
$1 = {type_info = 0x3fffdf06b30 , size = 
20, contents = {serialised = {
  bytes = 0x1009a2a90, data = 0x3ffee74}, tree = {children = 
0x1009a2a90, n_children = 4398046506612}},
  state = 11, ref_count = 1, depth = 0}

smcv

Processed: tagging 917492

[Debian Bug Tracking System]

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

> tags 917492 + buster sid
Bug #917492 [src:fam] fam: FTBFS ('minor' was not declared in this scope)
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: forcibly merging 916922 917489

[Debian Bug Tracking System]

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

> forcemerge 916922 917489
Bug #916922 {Done: Mattia Rizzolo } [src:migrate] migrate: 
invalid SQLite 3.26+ patch from Ubuntu
Bug #917502 {Done: Thomas Goirand } [src:migrate] nova: 
FTBFS (name 'sqlite3' is not defined)
Bug #916922 {Done: Mattia Rizzolo } [src:migrate] migrate: 
invalid SQLite 3.26+ patch from Ubuntu
The source src:migrate and version 0.11.0-5 do not appear to match any binary 
packages
Marked as fixed in versions src:migrate/0.11.0-5.
Marked as fixed in versions src:migrate/0.11.0-5.
Bug #917489 {Done: Robin Jarry } [src:migrate] buildbot: FTBFS 
(name 'sqlite3' is not defined)
Removed indication that 917489 affects src:buildbot
Added indication that 917489 affects src:buildbot,python3-buildbot,src:nova
The source src:migrate and version 0.11.0-5 do not appear to match any binary 
packages
Marked as fixed in versions migrate/0.11.0-5.
Bug #917502 {Done: Thomas Goirand } [src:migrate] nova: 
FTBFS (name 'sqlite3' is not defined)
Merged 916922 917489 917502
> thanks
Stopping processing here.

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

Processed: tagging 917490

[Debian Bug Tracking System]

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

> tags 917490 + buster sid experimental
Bug #917490 [src:coccinelle] coccinelle: FTBFS (LaTeX Error: Option clash for 
package color)
Added tag(s) buster, sid, and experimental.
> thanks
Stopping processing here.

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

Processed: Re: Bug#917656: libnet-server-mail-perl: FTBFS (failing tests)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 perl-modules-5.28
Bug #917656 [src:libnet-server-mail-perl] libnet-server-mail-perl: FTBFS 
(failing tests)
Bug reassigned from package 'src:libnet-server-mail-perl' to 
'perl-modules-5.28'.
No longer marked as found in versions libnet-server-mail-perl/0.25-4.
Ignoring request to alter fixed versions of bug #917656 to the same values 
previously set
> severity -1 normal
Bug #917656 [perl-modules-5.28] libnet-server-mail-perl: FTBFS (failing tests)
Severity set to 'normal' from 'serious'

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

Bug#917656: libnet-server-mail-perl: FTBFS (failing tests)

[Xavier]

Control: reassign -1 perl-modules-5.28
Control: severity -1 normal

Hi all,

it seems that Net::SMTP->new() fails randomly when launched during
Net::server::Mail tests: $s is sometimes undefined after this:

  my $s = Net::SMTP->new( $host, Port => $port, Hello => 'localhost' );

http://matrix.cpantesters.org/?dist=Net-Server-Mail+0.26 also shows that
this rarely happens since the release of 5.28.0 (1/22), never before.

I added a workaround for now in libnet-server-mail-perl tests (warn and
return when $s is undefined).

Cheers,
Xavier

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 917394 src:gitlint
Bug #917394 [gitlint] gitlint: FTBFS -- test suite fails
Bug reassigned from package 'gitlint' to 'src:gitlint'.
No longer marked as found in versions gitlint/0.9.0-2.
Ignoring request to alter fixed versions of bug #917394 to the same values 
previously set
> forcemerge 896070 917394
Bug #896070 [src:gitlint] gitlint FTBFS: FAIL: test_target
Bug #917394 [src:gitlint] gitlint: FTBFS -- test suite fails
Marked as found in versions gitlint/0.9.0-2.
Added tag(s) ftbfs.
Merged 896070 917394
> thanks
Stopping processing here.

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

Processed: tagging 917382

[Debian Bug Tracking System]

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

> tags 917382 + buster sid
Bug #917382 [src:stunserver] Should stunserver be removed?
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: tagging 917216

[Debian Bug Tracking System]

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

> tags 917216 + buster
Bug #917216 [python-apt] python-apt FTBFS against apt/1.8.0~alpha3
Added tag(s) buster.
> thanks
Stopping processing here.

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

Processed: notfound 917216 in 1.8.0~alpha0~ubuntu2

[Debian Bug Tracking System]

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

> notfound 917216 1.8.0~alpha0~ubuntu2
Bug #917216 [python-apt] python-apt FTBFS against apt/1.8.0~alpha3
There is no source info for the package 'python-apt' at version 
'1.8.0~alpha0~ubuntu2' with architecture ''
Unable to make a source version for version '1.8.0~alpha0~ubuntu2'
No longer marked as found in versions 1.8.0~alpha0~ubuntu2.
> thanks
Stopping processing here.

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

Processed: tagging 857298

[Debian Bug Tracking System]

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

> tags 857298 - fixed
Bug #857298 [python-cassandra-dbg] python-cassandra-dbg is an empty package on 
hppa, m68k, mips, powerpc, powerpcspe, ppc64, s390x, and sparc64
Removed tag(s) fixed.
> thanks
Stopping processing here.

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

Processed: tagging 917203

[Debian Bug Tracking System]

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

> tags 917203 + buster sid
Bug #917203 [src:libmcrypt] FTBFS on at least two architectures: test failure 
in the enigma algorithm
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: block 917200 with 821435

[Debian Bug Tracking System]

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

> block 917200 with 821435
Bug #917200 [pyside2] pyside2: build-dependencies no longer satisfiable on 
mips64el.
917200 was not blocked by any bugs.
917200 was not blocking any bugs.
Added blocking bug(s) of 917200: 821435
> thanks
Stopping processing here.

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

Bug#917977: freefem++ build depends on the no longer built libpetsc-{complex,real}3.9-dev

[Adrian Bunk]

Source: freefem++
Version: 3.61.1+dfsg1-3
Severity: serious
Tags: ftbfs

 libpetsc-{complex,real}3.9-dev have been replaced by
 libpetsc-{complex,real}3.10-dev.

Processed: notfixed 916846 in 1:6.1.4-2, fixed 916846 in 1:6.1.4-2, notfound 917927 in 1:6.1.4-2 ...

[Debian Bug Tracking System]

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

> notfixed 916846 1:6.1.4-2
Bug #916846 [libreoffice-ogltrans] [libreoffice-ogltrans] Blank screen with 
OpenGL transitions
There is no source info for the package 'libreoffice-ogltrans' at version 
'1:6.1.4-2' with architecture ''
Unable to make a source version for version '1:6.1.4-2'
No longer marked as fixed in versions 1:6.1.4-2.
> fixed 916846 1:6.1.4-2
Bug #916846 [libreoffice-ogltrans] [libreoffice-ogltrans] Blank screen with 
OpenGL transitions
There is no source info for the package 'libreoffice-ogltrans' at version 
'1:6.1.4-2' with architecture ''
Unable to make a source version for version '1:6.1.4-2'
Marked as fixed in versions 1:6.1.4-2.
> notfound 917927 1:6.1.4-2
Bug #917927 [libreoffice-impress] [libreoffice-impress] Blank screen with 
OpenGL transitions
There is no source info for the package 'libreoffice-impress' at version 
'1:6.1.4-2' with architecture ''
Unable to make a source version for version '1:6.1.4-2'
No longer marked as found in versions 1:6.1.4-2.
> found 917927 1:6.1.4-2
Bug #917927 [libreoffice-impress] [libreoffice-impress] Blank screen with 
OpenGL transitions
There is no source info for the package 'libreoffice-impress' at version 
'1:6.1.4-2' with architecture ''
Unable to make a source version for version '1:6.1.4-2'
Marked as found in versions 1:6.1.4-2.
> notfixed 917795 1:6.1.4-3
Bug #917795 {Done: Rene Engelhard } [libreoffice-l10n-be] 
libreoffice-l10n-be: typo in the name: Belarussian → Belarusian
No longer marked as fixed in versions 1:6.1.4-3.
> close 917795 1:6.1.4-3
Bug #917795 {Done: Rene Engelhard } [libreoffice-l10n-be] 
libreoffice-l10n-be: typo in the name: Belarussian → Belarusian
Marked as fixed in versions libreoffice/1:6.1.4-3.
Bug #917795 {Done: Rene Engelhard } [libreoffice-l10n-be] 
libreoffice-l10n-be: typo in the name: Belarussian → Belarusian
Bug 917795 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#917975: libeclipse-jdt-debug-ui-java: Depends: libeclipse-debug-core-java (>= 3.15) but 3.13.100+eclipse4.10-1 is to be installed

[Adrian Bunk]

Package: libeclipse-jdt-debug-ui-java
Version: 3.10.100+eclipse4.10-1
Severity: serious

The following packages have unmet dependencies:
 libeclipse-jdt-debug-ui-java : Depends: libeclipse-debug-core-java (>= 3.15) 
but 3.13.100+eclipse4.10-1 is to be installed

Bug#917973: openmsx-catapult: Depends: openmsx (< 0.14.1~) but 0.15.0-2+b1 is to be installed

[Adrian Bunk]

Package: openmsx-catapult
Version: 0.14.0-1
Severity: serious

The following packages have unmet dependencies:
 openmsx-catapult : Depends: openmsx (< 0.14.1~) but 0.15.0-2+b1 is to be 
installed

Bug#915831: [Pkg-zfsonlinux-devel] Bug#915831: Bug#915831: Fwd: zfsutils-linux: Upgrading to 0.7.12 breaks during dpkg --configure

[Petter Reinholdtsen]

[Richard Laager]
> I don't think that's desirable. If this is actually required, then
> wouldn't every package trying to support systemd and sysvinit need to
> do that same?

I doubt it.  It would most likely only affect packages starting very
eary in the boot, (think rcS.d scripts), which are involved in file
system setup and file system initialization.  When I tracked this, it
was around 100 of around 100 packages with init.d scripts.

-- 
Happy hacking
Petter Reinholdtsen

Bug#916279: qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement

[Michael Tokarev]

01.01.2019 23:14, Laurent Bigonville wrote:

On Mon, 24 Dec 2018 09:34:16 +0300 Michael Tokarev  wrote:



 > it doesn't really break the package in question. All these
 > packages will be of the same version anwyway, upgraded in
 > one go, at the very max there will be some docs missing
 > for a (short) while, until the next apt run.
 >
 > More, it's just one version which were like that during the
 > buster development cycle.
 >
 > Besides, *this* bug is fixed, it does declare a replacement :)

The usual way is to declare a Breaks/Replace when a file is moved between 
packages to prevent the file to be overwritten in case an older version of the 
package is installed.


I know the usual way, I just didn't think this is needed in this
particular case, as I explained before. At the very least, it is
a very minor issue, definitely not release critical.


 > I don't think this bug needs to be acted upon more. At least
 > I don't plan a new upload at least before it is migrated to
 > testing, as time is already too short and this very bug, a
 > stupid mistake, already took more time than necessary.

Well this bug has been reopened that mean that the package will never migrate


That's sort of unfortunate...

Thanks,

/mjt

Bug#917638: infnoise: Job dev-infnoise.device/start failed with result 'timeout'

[Stephen Kitt]

Hi Alexander,

On Sun, 30 Dec 2018 18:01:53 +0100, "Alexander Mader"  wrote:
> > Does the device itself work? With the package installed,
> > 
> > sudo infnoise --debug --no-output
> > 
> > should produce output similar to  
> 
> unfortunately, it just produces "Error:" like this:
> 
> 8< - >8 
>root@:~# infnoise --debug --no-output
>Error: 
>root@:~# 
> 8< - >8 

That suggests something wrong with the device :-(. Does it show up when you
run lsusb? Mine shows

Bus 001 Device 039: ID 0403:6015 Future Technology Devices International, Ltd 
Bridge(I2C/SPI/UART/FIFO)

dmesg might show more useful information; look around the time you plugged
the TRNG in.

Regards,

Stephen


pgp58LYXXgmub.pgp
Description: OpenPGP digital signature

Bug#916279: qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement

[Laurent Bigonville]

On Mon, 24 Dec 2018 09:34:16 +0300 Michael Tokarev  wrote:
> 24.12.2018 6:00, Andreas Beckmann wrote:
> > Followup-For: Bug #916279
> > Control: found -1 1:3.1+dfsg-2
> >
> > Hi,
> >
> > you are missing a
> > Breaks: qemu-system-data (<< 1:3.1+dfsg-1~)
> > to match the Replaces, otherwise you are permitting partial
> > upgrade/downgrade paths where files are disappearing whil
> > dpkg considers everything correctly installed.
>
> it doesn't really break the package in question. All these
> packages will be of the same version anwyway, upgraded in
> one go, at the very max there will be some docs missing
> for a (short) while, until the next apt run.
>
> More, it's just one version which were like that during the
> buster development cycle.
>
> Besides, *this* bug is fixed, it does declare a replacement :)

The usual way is to declare a Breaks/Replace when a file is moved 
between packages to prevent the file to be overwritten in case an older 
version of the package is installed.


> I don't think this bug needs to be acted upon more. At least
> I don't plan a new upload at least before it is migrated to
> testing, as time is already too short and this very bug, a
> stupid mistake, already took more time than necessary.
>

Well this bug has been reopened that mean that the package will never 
migrate

Bug#915831: [Pkg-zfsonlinux-devel] Bug#915831: Fwd: zfsutils-linux: Upgrading to 0.7.12 breaks during dpkg --configure

[Rich]

TBH I personally think clever conditional logic in the package install for
  if (systemd installed) { systemd scripts, sysvinit scripts get
diverted to /dev/null }
  elsif (sysvinit for real) { install sysvinit scripts, divert systemd
scripts to /dev/null }
  else { print that you're doing neither of the above b/c the world is
confusing }
would be my default idea, but that seems like a lot of moving parts
where just breaking things out has many fewer things to go wrong, and
has precedent in fanning out into e.g. zfs-initramfs, zfs-test,
zfs-zed...

Also, while I support the idea of permitting sysvinit scripts to be
used for some users, I think "just" adding a Conflicts: systemd-sysv
anywhere but in an optional part of the packaging would be a drastic
user experience problem - they'd just get a sudden prompt to rip out
part of their system (a part that popcon suggests over 50% have
installed, and 42% have used parts of recently, in the case of
insserv) on trying to upgrade a minor version.

- Rich

On Tue, Jan 1, 2019 at 2:22 PM Richard Laager  wrote:
>
> On 12/31/18 6:34 PM, Rich wrote:
> > It seems like what we might want is an OR dependency on two child
> > zfs-{systemd,sysvinit} packages - and for those two packages to
> > conflict with each other (and require the appropriate respective init
> > packages)?
>
> I don't think that's desirable. If this is actually required, then
> wouldn't every package trying to support systemd and sysvinit need to do
> that same? That would be a lot of work. No other packages are doing
> this; there should be some other solution.
>
> If systemd-sysv and insserv are not co-installable, that conflict should
> be expressed in those packages.
>
> --
> Richard

Bug#787527: marked as done (Some sources are not included in your package)

[Debian Bug Tracking System]

Your message dated Tue, 1 Jan 2019 14:39:11 -0500
with message-id 

and subject line Re: Bug#787527: Some sources are not included in your package
has caused the Debian Bug report #787527,
regarding Some sources are not included in your package
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.)


-- 
787527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium-browser 
version: 43.0.2357.65-1
user: lintian-ma...@debian.org
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org

Hi,

Your package seems to include some files that lack sources
in prefered forms of modification:

* third_party/flot/excanvas.min.js
* third_party/bidichecker/bidichecker_packaged.js
* third_party/analytics/google-analytics-bundle.js
* third_party/swig/linux/swig
* tools/perf/page_sets/tough_scheduling_cases/second_batch_js_medium.min.js
* tools/perf/page_sets/tough_scheduling_cases/second_batch_js_light.min.js
* tools/perf/page_sets/tough_scheduling_cases/second_batch_js_heavy.min.js
* tools/perf/page_sets/tough_energy_cases/test.swf
* third_party/webgl/src/resources/jquery-1.3.2.min.js
* third_party/trace-viewer/third_party/jszip/jszip.min.js
* third_party/trace-viewer/third_party/d3/d3.min.js
* third_party/trace-viewer/third_party/chai/chai.js
* third_party/pycoverage/coverage/htmlfiles/jquery.tablesorter.min.js
* third_party/pycoverage/coverage/htmlfiles/jquery.min.js
* third_party/dom_distiller_js/dist/js/domdistiller_wrapped.js
* third_party/dom_distiller_js/dist/js/domdistiller.js
* third_party/WebKit/PerformanceTests/resources/jquery.tablesorter.min.js
* third_party/WebKit/PerformanceTests/resources/jquery.flot.min.js
* third_party/WebKit/ManualTests/resources/spinbox.swf
* 
third_party/WebKit/ManualTests/plugins/timeout-dialog-displayed-over-navigation.swf
* third_party/WebKit/ManualTests/plugins/test.swf
* third_party/trace-viewer/third_party/components/polymer/polymer.js
* third_party/trace-viewer/third_party/components/platform/platform.js
* third_party/webgl/src/other/get.webgl.org/tdl/tdl-minified.js
* third_party/skia/platform_tools/android/bin/linux/perfhost
* 
third_party/android_platform/bionic/tools/relocation_packer/test_data/elf_file_unittest_relocs_arm64_packed.so
* 
third_party/android_platform/bionic/tools/relocation_packer/test_data/elf_file_unittest_relocs_arm64.so
* 
third_party/android_platform/bionic/tools/relocation_packer/test_data/elf_file_unittest_relocs_arm32_packed.so
* 
third_party/android_platform/bionic/tools/relocation_packer/test_data/elf_file_unittest_relocs_arm32.so
* third_party/webgl/src/sdk/demos/mozilla/spore/sylvester.js
* third_party/webgl/src/sdk/demos/google/shiny-teapot/teapot-streams.js
* third_party/webgl/src/sdk/demos/google/high-dpi/teapot-streams.js
* third_party/webgl/src/sdk/demos/google/san-angeles/glut/SanOGLES
* third_party/webgl/src/sdk/demos/google/san-angeles/gles/bob/bob

Maybe:
* tools/relocation_packer/test_data/*.so

Please override:
* tools/trace/trace_data.js
* third_party/web-animations-js/sources/web-animations.min.js
* third_party/web-animations-js/sources/web-animations-next.min.js
* third_party/web-animations-js/sources/web-animations-next-lite.min.js
* ui/webui/resources/js/jstemplate_compiled.js



According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution 
  in source code as well as compiled form.".

This could also constitute a license violation for some copyleft licenses such 
as the GNU GPL.

In order to solve this problem, you could:
1. repack the origin tarball adding the missing source to it.
2  add the source files to "debian/missing-sources" directory

Both way satisfies the requirement that we ship the source. Second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them, thus full 
filling our social contract [3], see particularly §2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.

[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract


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

Bug#915831: [Pkg-zfsonlinux-devel] Bug#915831: Fwd: zfsutils-linux: Upgrading to 0.7.12 breaks during dpkg --configure

[Richard Laager]

On 12/31/18 6:34 PM, Rich wrote:
> It seems like what we might want is an OR dependency on two child
> zfs-{systemd,sysvinit} packages - and for those two packages to
> conflict with each other (and require the appropriate respective init
> packages)?

I don't think that's desirable. If this is actually required, then
wouldn't every package trying to support systemd and sysvinit need to do
that same? That would be a lot of work. No other packages are doing
this; there should be some other solution.

If systemd-sysv and insserv are not co-installable, that conflict should
be expressed in those packages.

-- 
Richard

Bug#870032: [Pkg-fedora-ds-maintainers] Bug#870032: closed by Timo Aaltonen (Bug#870032: fixed in 389-admin 1.1.46-1)

[Adrian Bunk]

On Mon, Dec 31, 2018 at 11:11:52AM +0200, Timo Aaltonen wrote:
> On 17.3.2018 19.47, Adrian Bunk wrote:
> > On Wed, Oct 04, 2017 at 06:21:05PM +, Debian Bug Tracking System wrote:
> >> ...
> >>  389-admin (1.1.46-1) unstable; urgency=medium
> >> ...
> >>* rules, postinst: Don't fail the install when the unconfigured
> >>  service doesn't start. (Closes: 870032) (LP: #1652476)
> >> ...
> > 
> > Thanks a lot for fixing this bug for unstable.
> > 
> > It is still present in stretch, could you also fix it there?
> > Alternatively, I can fix it for stretch if you don't object.
> > 
> > It might also be a good idea to include:
> > 
> >>* Fix systemd service to stop properly.
> >> ...
> 
> Hi, it's been a while, but I have this prepared now.

Thanks!

> Are you part of the
> stable team or should I ask for the ack elsewhere?

I am not part of the stable team, please ask for an ACK with
  reportbug release.debian.org
(stretch-pu, with a debdiff to the version in stretch attached).

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#917968: emms: relies on default-major-mode (replaced by major-mode in emacs 26)

[Rob Browning]

Package: emms
Version: 4.2-1.1
Severity: serious

It looks like emacs has removed the default-major-mode variable in favor
of major-mode.  I tried just replacing the reference, and emms appears
to build successfully.

I noticed this because it breaks emacsspeak.

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#917960: marked as done (beancount: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Tue, 01 Jan 2019 18:34:16 +
with message-id 
and subject line Bug#917960: fixed in beancount 2.1.3+hg20181225-2
has caused the Debian Bug report #917960,
regarding beancount: Incomplete debian/copyright?
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.)


-- 
917960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: beancount
Version: 2.1.3+hg20181225-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Stefano Zacchiroli , 
ftpmas...@debian.org

Hi,

I just ACCEPTed beancount from NEW but noticed it was missing 
attribution in debian/copyright for at least sorttable.js.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: beancount
Source-Version: 2.1.3+hg20181225-2

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

Debian distribution maintenance software
pp.
Stefano Zacchiroli  (supplier of updated beancount package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 01 Jan 2019 19:09:05 +0100
Source: beancount
Binary: beancount python3-beancount
Architecture: source all amd64
Version: 2.1.3+hg20181225-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Stefano Zacchiroli 
Description:
 beancount  - Double-entry accounting from text files
 python3-beancount - Double-entry accounting from text files - Python module
Closes: 917960
Changes:
 beancount (2.1.3+hg20181225-2) unstable; urgency=medium
 .
   * rules: simplify manpage dir creation
   * ship upstream examples
   * ship upstream info about where to find online documentation
   * copyright: release packaging files under GPL2 or later
   * copyright: document missing copyright and license for
 beancount/web/third_party/sorttable.js (Closes: #917960)
Checksums-Sha1:
 d77f5688cc385e2d8abba435c32cac707b349166 2435 beancount_2.1.3+hg20181225-2.dsc
 3962f5f2e06861cf53f97668af7f08755f2d87bd 4228 
beancount_2.1.3+hg20181225-2.debian.tar.xz
 a7b2aa2f3d564783998ac8c709fd483dcba653a3 197996 
beancount_2.1.3+hg20181225-2_all.deb
 2b04de79cad35bceb063a996487c444cb81112b6 11408 
beancount_2.1.3+hg20181225-2_amd64.buildinfo
 d25c06b68664d2fe0c37217fce32db1caba5dbe7 56220 
python3-beancount-dbgsym_2.1.3+hg20181225-2_amd64.deb
 39a338498bd3383c49c9a2e7ca5ec524fc4043de 486088 
python3-beancount_2.1.3+hg20181225-2_amd64.deb
Checksums-Sha256:
 e21b75f34f41d34dc6bd6a1f620b399d8424ba70503cf6d38aeaea61e505291b 2435 
beancount_2.1.3+hg20181225-2.dsc
 d4de6c2f0506dfc76692b66112799deb2aca31970ff7e7e4be8bfe3b274d3a43 4228 
beancount_2.1.3+hg20181225-2.debian.tar.xz
 31cb8e8e4d5752bd5c24bcb28ec996c5a020eb0c73a5fc89819bc1dc0d04510b 197996 
beancount_2.1.3+hg20181225-2_all.deb
 6a9ca3b76e11ddf4667464c44b7f8f9166f639b0591ee3e1563e8db6378bce78 11408 
beancount_2.1.3+hg20181225-2_amd64.buildinfo
 066182cb0f149d72c9884faee178ab5b970d1ee5fad69ffa51ddb80f0cdbf947 56220 
python3-beancount-dbgsym_2.1.3+hg20181225-2_amd64.deb
 f756a53f3e96fb991f1d6adaf489439982659c2dafe96a1607923b495de4f313 486088 
python3-beancount_2.1.3+hg20181225-2_amd64.deb
Files:
 fa7d897082062dc66b051cc03edbbf5a 2435 utils optional 
beancount_2.1.3+hg20181225-2.dsc
 f4145c22b5a3c40deed8f800ea73b78c 4228 utils optional 
beancount_2.1.3+hg20181225-2.debian.tar.xz
 ee151ab74c62e01d4ec74de60babf801 197996 utils optional 
beancount_2.1.3+hg20181225-2_all.deb
 225fad7e56c9857962b4c965d8ae8b2d 11408 utils optional 
beancount_2.1.3+hg20181225-2_amd64.buildinfo
 1ad4b62b1d75f988ee4399bd61babade 56220 debug optional 
python3-beancount-dbgsym_2.1.3+hg20181225-2_amd64.deb
 6529d4cda9b510cd03e5b32481507429 486088 python optional 
python3-beancount_2.1.3+hg20181225-2_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#917954: marked as done (fava: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Tue, 01 Jan 2019 18:34:24 +
with message-id 
and subject line Bug#917954: fixed in fava 1.9-2
has caused the Debian Bug report #917954,
regarding fava: Incomplete debian/copyright?
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.)


-- 
917954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fava
Version: 1.9-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Stefano Zacchiroli , 
ftpmas...@debian.org

Hi,

I just ACCEPTed fava from NEW but noticed it was missing attribution 
in debian/copyright for at least some code embedded in fava/static/gen/app.js.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: fava
Source-Version: 1.9-2

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

Debian distribution maintenance software
pp.
Stefano Zacchiroli  (supplier of updated fava package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 01 Jan 2019 19:15:00 +0100
Source: fava
Binary: python3-fava
Architecture: source all
Version: 1.9-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Stefano Zacchiroli 
Description:
 python3-fava - Web interface for the double-entry accounting tool Beancount
Closes: 917954
Changes:
 fava (1.9-2) unstable; urgency=medium
 .
   * debian/copyright: document additional copyright owners and licenses
 applicable to app.js (Closes: #917954)
Checksums-Sha1:
 964fdbce4b713b7cd6bca5d13e90a66fa5e4b553 2176 fava_1.9-2.dsc
 a394f85102d2dddb1f3aa3c97f929c52706e6130 2752 fava_1.9-2.debian.tar.xz
 0cbd86dba1cc5d1dfa1aa86130695b4287dab0a3 7622 fava_1.9-2_amd64.buildinfo
 acdd002e2c549171019a5a05826ee41f3b0bd45c 465056 python3-fava_1.9-2_all.deb
Checksums-Sha256:
 d6ef433797d3649668a6286f93295db1c1f29567c5c55a0587770bc376bf2874 2176 
fava_1.9-2.dsc
 c45757d2737e0dabecb6b9a369576c8ff8b11755d8c71bd40f3abd5979bfcc8e 2752 
fava_1.9-2.debian.tar.xz
 37ba5d85d519535264213963aa0928fa6c1096caeea6993dde63d6864836faf8 7622 
fava_1.9-2_amd64.buildinfo
 92f4446067c88dd0acee573601e795bdf0fbd1f9e71a8fd9027c05df7641686c 465056 
python3-fava_1.9-2_all.deb
Files:
 aa40ceefaa70d327f45c2671be5a2ad4 2176 python optional fava_1.9-2.dsc
 8061bbcc5d8ad1f92aca02c84ecdb4de 2752 python optional fava_1.9-2.debian.tar.xz
 5db5c59b68e17902823db028dfd787c4 7622 python optional 
fava_1.9-2_amd64.buildinfo
 e34bfb9e98f17da4a79f1a919d0d68cd 465056 python optional 
python3-fava_1.9-2_all.deb

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE8ZooXsFA+JEz681OfH5Cj5NBJ5kFAlwrsD8QHHphY2tAZGVi
aWFuLm9yZwAKCRB8fkKPk0EnmWMaEACOSg7cZ8pcblKa6Nb6hkkLJTLwGuemXNE6
d2iw4KeK6ryBlBFL8w5F1FTDyYE3qaRFUE6CpNd3fzWba2sGKyimhAqdjHiR4doX
v9C9VtncXy8hPCF2GGvAIlx4k+9xJDdntyE+PTKPMxwepY5AYvcpw3whSVGX19+M
hGn5Tci6T5eiM2jEtrvd95ckJtSlUK8yd4hUzCQsRN3WKqnyxMzJMoT5hH2OV75I
2Pbie6Szk3qgsPFPst+NqQGsH/hQg4TtJn5wsbVAPwG2+YTgou1buo9UsAqyA5Lt
DB5fxeAUuTXPzgz3saG5+lVGH9LvlH4V+c/U1PRzQfxd1EJlFGdEqm4NYRE3i45z
xCoMZS20Jr2YCZ1Zzk5L48BaVBLu0YsoCJP3otiGghPTY8QpgU9rGbuRgL73iS+7
dxreK59pBvlgFur0Z3OYuPvSXOnkXajX7PXggvH+pcFBLKlvB/MsBjlDHb8E54M7
i7jT7yZ08Eo+nkrES5aanzzKN3OjWDsnpFhGG9tiFkwCrUnL3j2PkT97Be3bU0je
yEGScOjrzzqIQNn6ADInAqXDLbxZ/TnllrkeV+8XQI68vTjp263EKCDjWCzjYtF+
SxxDPyo251yDGmy+wsV/DbuD0zcZFRNrQ18CW+3vZpLwOBQskNN0rBj3GEYCjy+Q
omIhEeoVOQ==
=h4m+
-END PGP SIGNATURE End Message ---

Bug#915344: openfoam: diff for NMU version 4.1+dfsg1-2.3

[Adrian Bunk]

On Tue, Jan 01, 2019 at 03:51:36PM +0100, Anton Gladky wrote:
> Could you please push your changes into the git? Thanks!

Done.

> Anton

cu
Adrian

-- 

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

Processed: limit source to beancount, tagging 917960

[Debian Bug Tracking System]

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

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

> tags 917960 + pending
Bug #917960 [src:beancount] beancount: Incomplete debian/copyright?
Warning: Unknown package 'src:beancount'
Added tag(s) pending.
Warning: Unknown package 'src:beancount'
> thanks
Stopping processing here.

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

Processed: Bug #917960 in beancount marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #917960 [src:beancount] beancount: Incomplete debian/copyright?
Warning: Unknown package 'src:beancount'
Ignoring request to alter tags of bug #917960 to the same tags previously set
Warning: Unknown package 'src:beancount'

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

Bug#917960: Bug #917960 in beancount marked as pending

[Stefano Zacchiroli]

Control: tag -1 pending

Hello,

Bug #917960 in beancount 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/python-team/applications/beancount/commit/f53ee91b7b269acbe75e8d5b5599d7eca9dbe762


copyright: document missing copyright and license for sorttable.js

Closes: #917960


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/917960

Bug#917961: nodejs: missing shlibs prevents build-dependencies on libnode-dev from working correctly

[Jérémy Lal]

Package: nodejs
Version: 10.15.0~dfsg-5
Severity: serious
Justification: Policy 8.6

This is a reminder.

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

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

Versions of packages nodejs depends on:
ii  libc-ares2 1.14.0-1
ii  libc6  2.28-4
ii  libgcc11:8.2.0-13
ii  libicu63   63.1-5
ii  libnghttp2-14  1.35.1-1
ii  libnode64  10.15.0~dfsg-5
ii  libssl1.1  1.1.1a-1
ii  libstdc++6 8.2.0-13
ii  libuv1 1.24.0-1
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages nodejs recommends:
ii  ca-certificates  20180409
ii  nodejs-doc   10.15.0~dfsg-4

nodejs suggests no packages.

-- no debconf information

Bug#917960: beancount: Incomplete debian/copyright?

[Chris Lamb]

Source: beancount
Version: 2.1.3+hg20181225-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Stefano Zacchiroli , 
ftpmas...@debian.org

Hi,

I just ACCEPTed beancount from NEW but noticed it was missing 
attribution in debian/copyright for at least sorttable.js.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

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

Bug#915402: esys-particle: diff for NMU version 2.3.5+dfsg1-2.1

[Adrian Bunk]

Control: tags 915402 + patch
Control: tags 915402 + pending

Dear maintainer,

I've prepared an NMU for esys-particle (versioned as 2.3.5+dfsg1-2.1) 
and uploaded it to DELAYED/14. 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 esys-particle-2.3.5+dfsg1/debian/changelog esys-particle-2.3.5+dfsg1/debian/changelog
--- esys-particle-2.3.5+dfsg1/debian/changelog	2017-08-07 23:05:00.0 +0300
+++ esys-particle-2.3.5+dfsg1/debian/changelog	2019-01-01 17:13:15.0 +0200
@@ -1,3 +1,11 @@
+esys-particle (2.3.5+dfsg1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with -g1 on mips/mipsel to work around address space
+limitations. (Closes: #915402)
+
+ -- Adrian Bunk   Tue, 01 Jan 2019 17:13:15 +0200
+
 esys-particle (2.3.5+dfsg1-2) unstable; urgency=medium
 
   [ gregor herrmann ]
diff -Nru esys-particle-2.3.5+dfsg1/debian/rules esys-particle-2.3.5+dfsg1/debian/rules
--- esys-particle-2.3.5+dfsg1/debian/rules	2017-08-07 23:04:32.0 +0300
+++ esys-particle-2.3.5+dfsg1/debian/rules	2019-01-01 17:13:15.0 +0200
@@ -1,5 +1,10 @@
 #!/usr/bin/make -f
 
+# less debug info to avoid running out of address space
+ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
+  export DEB_CXXFLAGS_MAINT_APPEND += -g1
+endif
+
 include /usr/share/dpkg/default.mk
 
 %:

Bug#917954: fava: Incomplete debian/copyright?

[Chris Lamb]

Hi Stefano,

> I'm postponing package upload, waiting for beancount (a fava dependency)
> to clear NEW too.

(I've gone ahead and processed this.)


Regards,

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

Processed: esys-particle: diff for NMU version 2.3.5+dfsg1-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 915402 + patch
Bug #915402 [src:esys-particle] esys-particle: FTBFS on mips/mipsel: OOM
Added tag(s) patch.
> tags 915402 + pending
Bug #915402 [src:esys-particle] esys-particle: FTBFS on mips/mipsel: OOM
Added tag(s) pending.

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

Bug#907974: perl-doc-html: Should be updated to 5.28 at the point of the transition

[Dominic Hargreaves]

On Mon, Nov 05, 2018 at 08:54:13PM +0200, Niko Tyni wrote:
> Control: severity -1 serious
> 
> On Tue, Sep 04, 2018 at 05:40:41PM +0100, Dominic Hargreaves wrote:
> > Source: perl-doc-html
> > Version: 5.26.0-4
> > Severity: wishlist
> > User: debian-p...@lists.debian.org
> > Usertags: perl-5.28-transition
> > X-Debbugs-Cc: p...@packages.debian.org
> > 
> > We should make this bug serious at the point of the 5.28 transition
> > so that we don't end up releasing with documentation for the wrong 
> > version of perl.
> > 
> > See #907273 and #154963 for additional context.
> 
> Perl 5.28 transition is done now, so raising the severity of this bug.

I'm not sure where the original tooling for perldoc.perl.org has gone,
but it seems like it might not be the best option these days.

Possible alternative source:

https://perldoc.pl/
https://github.com/Grinnz/perldoc-browser
https://metacpan.org/pod/Mojolicious::Command::export

Bug#917954: fava: Incomplete debian/copyright?

[Stefano Zacchiroli]

On Tue, Jan 01, 2019 at 03:07:02PM +, Chris Lamb wrote:
> I just ACCEPTed fava from NEW but noticed it was missing attribution 
> in debian/copyright for at least some code embedded in fava/static/gen/app.js.
> 
> This is in no way exhaustive so please check over the entire package 
> carefully and address these on your next upload.

Thanks, nice catch.

I've fixed this specific occurrence (in git) and looked for others,
without finding any.

I'm postponing package upload, waiting for beancount (a fava dependency)
to clear NEW too.

Cheers
-- 
Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »


signature.asc
Description: PGP signature

Processed: limit source to fava, tagging 917954

[Debian Bug Tracking System]

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

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

> tags 917954 + pending
Bug #917954 [src:fava] fava: Incomplete debian/copyright?
Warning: Unknown package 'src:fava'
Added tag(s) pending.
Warning: Unknown package 'src:fava'
> thanks
Stopping processing here.

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