Processed: Re: diaspora-installer package fails to install

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #919978 [diaspora-installer] diaspora-installer package fails to install
Severity set to 'important' from 'grave'

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

Bug#919978: diaspora-installer package fails to install

[Pirate Praveen]

Control: severity -1 important

On Mon, 21 Jan 2019 09:53:39 +0100 Karl Stenerud
 wrote:
> Package: disaspora-installer
> Version: 0.7.6.1
> Severity: grave
> 
> Attempting to install diaspora-installer via apt fails with an error.
> 
> Transcript:
> 
> $ lxc launch images:debian/sid tester && lxc exec tester bash

Can you try with lxc-attach?

> Installing gems with rubygems ...
> sh: 1: bundle: not found

It seems /usr/local/bin is not in your path when you just start bash. It
worked with lxc-attach.



signature.asc
Description: OpenPGP digital signature

Processed: Fwd: Bug#921704: tortoisehg: uninstallable with mercurial 4.9

[Debian Bug Tracking System]

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

> package src:tortoisehg
Limiting to bugs with field 'package' containing at least one of 
'src:tortoisehg'
Limit currently set to 'package':'src:tortoisehg'

> tags 921704 + sid experimental
Bug #921704 [src:tortoisehg] tortoisehg: uninstallable with mercurial 4.9
Added tag(s) sid and experimental.
> thanks
Stopping processing here.

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

Bug#921704: tortoisehg: uninstallable with mercurial 4.9

[Ludovico Cavedon]

package src:tortoisehg
tags 921704 + sid experimental
thanks

Thank you for the bug report. TortoiseHg 4.9 has not been released yet.

Ludovico

On Fri, Feb 8, 2019 at 12:09 AM Julien Cristau  wrote:

> Source: tortoisehg
> Version: 4.8.1-0.1
> Severity: serious
> X-Debbugs-Cc: James Cowgill 
>
> Hi,
>
> mercurial 4.9 is now in sid, so tortoisehg needs an update.
>
> Cheers,
> Julien
>

Bug#919463: marked as done (aac-tactics ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Mon, 18 Feb 2019 02:55:04 +
with message-id 
and subject line Bug#919463: fixed in aac-tactics 8.8.0+1.gbp069dc3b-1
has caused the Debian Bug report #919463,
regarding aac-tactics ftbfs in unstable
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.)


-- 
919463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aac-tactics
Version: 8.6.1-2
Severity: serious
Tags: sid buster

aac-tactics ftbfs in unstable:

[...]
dh build --with ocaml
   dh_update_autotools_config
   dh_ocamlinit
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/home/packages/tmp/aac-tactics-8.6.1'
/usr/bin/make Makefile.coq
make[2]: Entering directory '/home/packages/tmp/aac-tactics-8.6.1'
coq_makefile -f Make -o Makefile.coq
make -f Makefile.coq Makefile
make[3]: Entering directory '/home/packages/tmp/aac-tactics-8.6.1'
COQDEP VFILES
*** Warning: aac_rewrite.mli already found in . (discarding ./aac_rewrite.mli)
*** Warning: print.mli already found in . (discarding ./print.mli)
*** Warning: theory.mli already found in . (discarding ./theory.mli)
*** Warning: matcher.mli already found in . (discarding ./matcher.mli)
*** Warning: search_monad.mli already found in . (discarding ./search_monad.mli)
*** Warning: helper.mli already found in . (discarding ./helper.mli)
*** Warning: coq.mli already found in . (discarding ./coq.mli)
*** Warning: print.ml already found in . (discarding ./print.ml)
*** Warning: theory.ml already found in . (discarding ./theory.ml)
*** Warning: matcher.ml already found in . (discarding ./matcher.ml)
*** Warning: search_monad.ml already found in . (discarding ./search_monad.ml)
*** Warning: helper.ml already found in . (discarding ./helper.ml)
*** Warning: coq.ml already found in . (discarding ./coq.ml)
*** Warning: aac_rewrite.ml4 already found in . (discarding ./aac_rewrite.ml4)
CAMLDEP aac_rewrite.mli
CAMLDEP print.mli
CAMLDEP theory.mli
CAMLDEP matcher.mli
CAMLDEP search_monad.mli
CAMLDEP helper.mli
CAMLDEP coq.mli
COQDEP aac.mlpack
CAMLDEP print.ml
CAMLDEP theory.ml
CAMLDEP matcher.ml
CAMLDEP search_monad.ml
CAMLDEP helper.ml
CAMLDEP coq.ml
CAMLDEP -pp aac_rewrite.ml4
make[3]: Nothing to be done for 'Makefile'.
make[3]: Leaving directory '/home/packages/tmp/aac-tactics-8.6.1'
make[2]: 'Makefile.coq' is up to date.
make[2]: Leaving directory '/home/packages/tmp/aac-tactics-8.6.1'
/usr/bin/make -f Makefile.coq opt html
make[2]: Entering directory '/home/packages/tmp/aac-tactics-8.6.1'
make[3]: Entering directory '/home/packages/tmp/aac-tactics-8.6.1'
CAMLC -c coq.mli
File "coq.mli", line 26, characters 45-56:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 30, characters 35-48:
Warning 3: deprecated: Tacmach.sigma
alias of Evd.sigma
File "coq.mli", line 32, characters 44-57:
Warning 3: deprecated: Tacmach.sigma
alias of Evd.sigma
File "coq.mli", line 32, characters 61-71:
Warning 3: deprecated: Term.types
Alias for Constr.types
File "coq.mli", line 32, characters 75-86:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 33, characters 48-58:
Warning 3: deprecated: Term.types
Alias for Constr.types
File "coq.mli", line 33, characters 63-74:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 34, characters 28-39:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 34, characters 43-54:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 35, characters 30-40:
Warning 3: deprecated: Term.types
Alias for Constr.types
File "coq.mli", line 35, characters 45-56:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 36, characters 28-39:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 36, characters 44-55:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 37, characters 31-42:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 37, characters 46-57:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 38, characters 33-44:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 38, characters 48-59:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 39, characters 24-35:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 39, characters 40-51:
Warning 3: deprecated: Term.constr
Alias for Constr.t
File "coq.mli", line 41, characters 29-40:
Warning 3: deprecated: Term.constr
Alias for 

Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders many systems unbootable

[Vagrant Cascadian]

On 2019-02-17, Vagrant Cascadian  wrote:
> On 2019-02-17, Timo Sigurdsson wrote:
>> Cyril Brulebois schrieb am 17.02.2019 19:38:
>>> Jürgen Löb  (2019-02-16):
> FWIW, I also built a local package from 4.9.155-1~ from salsa/stretch
> git, and it worked on a wandboard quad.
>
> $ uname -a
> Linux wbq0 4.9.0-9-armmp #1 SMP Debian 4.9.155-1~20190217~1 (2019-02-17) 
> armv7l GNU/Linux

That seemed to work fine on several tested boards.

I also did a local build commenting out
"debian/arm-avoid-abi-change-in-4.9.139.patch" in debian/patches and
removing "debian/abi/4.9.0-8/armhf_none_armmp" so that the abi conflicts
didn't fail to build...

$ uname -a
Linux cbxi4b 4.9.0-8-armmp #1 SMP Debian 4.9.144-4~20190217~1 (2019-02-17) 
armv7l GNU/Linux

Sounds like there may be a less intrusive patch in the works...


live well,
  vagrant

Bug#921195: marked as done (libloudmouth1-0: does not support IPv6 (fails Squeeze release goal))

[Debian Bug Tracking System]

Your message dated Mon, 18 Feb 2019 00:34:32 +
with message-id 
and subject line Bug#921195: fixed in loudmouth 1.5.3-5
has caused the Debian Bug report #921195,
regarding libloudmouth1-0: does not support IPv6 (fails Squeeze release goal)
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.)


-- 
921195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mcabber
Version: 1.1.0-1.1
Severity: serious
Tags: ipv6
Justification: fails release goal

I’m currently in the FOSDEM WLAN (IPv6-only, not FOSDEM-legacy),
and I can neither connect to the Jabber server with SRV RRs nor
when hardcoding commu.teckids.org in mcabberrc.

A netcat on commu.teckids.org port 5223 works, so it’s the client.

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

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

Versions of packages mcabber depends on:
ii  libaspell15  0.60.7~20110707-5
ii  libassuan0   2.5.2-1
ii  libc62.28-5
ii  libglib2.0-0 2.58.2-4
ii  libgpg-error01.33-3
ii  libgpgme11   1.12.0-6
ii  libidn11 1.33-2.2
ii  libloudmouth1-0  1.5.3-4
ii  libncursesw6 6.1+20181013-1
ii  libotr5  4.1.1-3
ii  libtinfo66.1+20181013-1

mcabber recommends no packages.

mcabber suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: loudmouth
Source-Version: 1.5.3-5

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

Debian distribution maintenance software
pp.
W. Martin Borgert  (supplier of updated loudmouth package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Feb 2019 22:34:08 +
Source: loudmouth
Binary: libloudmouth1-0 libloudmouth1-0-dbgsym libloudmouth1-dev
Architecture: source amd64
Version: 1.5.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian XMPP Maintainers 
Changed-By: W. Martin Borgert 
Description:
 libloudmouth1-0 - Lightweight C Jabber library
 libloudmouth1-dev - Development files for Loudmouth Jabber library
Closes: 921195
Changes:
 loudmouth (1.5.3-5) unstable; urgency=medium
 .
   * Add support for IPv6 (Closes: #921195)
   * Move maintainership from Gnome team to XMPP team
Checksums-Sha1:
 39fef9914504bb46cb8f5dacc921ddad232e0b08 2094 loudmouth_1.5.3-5.dsc
 61d47ee611133289a4f660e728e95e4f5571f432 11396 loudmouth_1.5.3-5.debian.tar.xz
 c9f04fd602e80c3282a77cbb13ed7280b503954b 193672 
libloudmouth1-0-dbgsym_1.5.3-5_amd64.deb
 3d2dca68120bf3414a8383d8b8e9cf178f0eb5b0 53656 
libloudmouth1-0_1.5.3-5_amd64.deb
 225a7ce296864ae8088fe90f75315a1083ea48fe 91960 
libloudmouth1-dev_1.5.3-5_amd64.deb
 7b4cc98acf4ccdd49ae02c7c7c1913e822149899 8492 loudmouth_1.5.3-5_amd64.buildinfo
Checksums-Sha256:
 17f8a41718113a2d754dfe3e534d184ddaf988f9a9f61a3d7dc296aee9bf1976 2094 
loudmouth_1.5.3-5.dsc
 929e6f7adf3d96017ea88e2a92ec40f7ba20cb8486ee42b5dbe11eff752dee77 11396 
loudmouth_1.5.3-5.debian.tar.xz
 5dc639b03ef03a305240ec892882e73b0f15f09883dcf7804b7739ccf7953179 193672 
libloudmouth1-0-dbgsym_1.5.3-5_amd64.deb
 558dac4f796fe1caf7cc32d27aebaec2b5eefdaabb18bff2fcb0a9726d9b2820 53656 
libloudmouth1-0_1.5.3-5_amd64.deb
 527086c71e7ccbd1a9aaf91e35a96a6d446f773a23587d249b21ecab0c33db96 91960 
libloudmouth1-dev_1.5.3-5_amd64.deb
 59c6fe0ded1664072f99f739435d1888ca9ca0e9978ce661c26fb2dfe1df5106 8492 
loudmouth_1.5.3-5_amd64.buildinfo
Files:
 a575eb719bcffd2f287b5e007862def3 2094 libs optional loudmouth_1.5.3-5.dsc
 91d50fa8fe67c2b130d2a04a61af446e 11396 libs optional 
loudmouth_1.5.3-5.debian.tar.xz
 31c163765a7e9b26847a33f7af60a82f 193672 debug optional 
libloudmouth1-0-dbgsym_1.5.3-5_amd64.deb
 5aa62b85481d79bff506ce9021796883 53656 libs optional 

Bug#922552: diffutils: FTBFS in ppc64el (failing tests)

[Santiago Vila]

Package: src:diffutils
Version: 1:3.7-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=diffutils=ppc64el=1%3A3.7-1=1550448741=0

Have to look at this.

Processed: fixed 922497 in 410.93-2

[Debian Bug Tracking System]

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

> fixed 922497 410.93-2
Bug #922497 [nvidia-driver] BUG: unable to handle kernel paging request at 
9b30a7cb488
Marked as fixed in versions nvidia-graphics-drivers/410.93-2.
> thanks
Stopping processing here.

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

Bug#922532: linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders many systems unbootable

[M.Gergo]

Some additional info for the previous kernel_panic error:

Stop-log:
==


root@cubieboard2:~# powerpoff

 Stopping Session 1 of user root.
[  OK  ] Stopped target Sound Card.
 Stopping User Manager for UID 0...
 Stopping OpenBSD Secure Shell server...
 Stopping D-Bus System Message Bus...
 Stopping Regular background program processing daemon...
[  OK  ] Stopped System Logging Service.
[  OK  ] Stopped Internet superserver.
[  OK  ] Stopped Self Monitoring and Reporting Technology (SMART) Daemon.
[  OK  ] Stopped D-Bus System Message Bus.
[  OK  ] Stopped irqbalance daemon.
[  OK  ] Stopped Regular background program processing daemon.
[  OK  ] Stopped OpenBSD Secure Shell server.
[  OK  ] Stopped Serial Getty on ttyS0.
[  OK  ] Stopped Getty on tty1.
[  OK  ] Stopped Session 1 of user root.
[  OK  ] Stopped User Manager for UID 0.
[  OK  ] Removed slice User Slice of root.
 Stopping Login Service...
[  OK  ] Removed slice system-getty.slice.
[  OK  ] Removed slice system-serial\x2dgetty.slice.
 Stopping Permit User Sessions...
[  OK  ] Stopped /etc/rc.local Compatibility.
[  OK  ] Stopped Login Service.
[  OK  ] Stopped Permit User Sessions.
[  OK  ] Stopped LSB: Start NTP daemon.
[  OK  ] Stopped target Network is Online.
[  OK  ] Deactivated swap /var/swap_file.
[  OK  ] Stopped LSB: Autogenerate and use a swap file.
[  OK  ] Stopped The Apache HTTP Server.
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped target Host and Network Name Lookups.
[  OK  ] Stopped target Network.
 Stopping Raise network interfaces...
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped target Slices.
[  OK  ] Removed slice User and Session Slice.
[  OK  ] Stopped target Sockets.
[  OK  ] Closed D-Bus System Message Bus Socket.
[  OK  ] Closed Syslog Socket.
[  OK  ] Stopped target System Initialization.
 Stopping Update UTMP about System Boot/Shutdown...
[  OK  ] Stopped target Encrypted Volumes.
[  OK  ] Stopped Forward Password Requests to Wall Directory Watch.
[  OK  ] Stopped Dispatch Password Requests to Console Directory Watch.
 Stopping Load/Save Random Seed...
[  OK  ] Stopped target Swap.
[  OK  ] Stopped Load/Save Random Seed.
[  OK  ] Stopped Update UTMP about System Boot/Shutdown.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped Raise network interfaces.
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped target Local File Systems.
 Unmounting /run/user/0...
 Unmounting /boot...
[  OK  ] Stopped Load Kernel Modules.
[  OK  ] Unmounted /run/user/0.
 Unmounting /home...
[  OK  ] Unmounted /boot.
[  OK  ] Stopped File System Check on 
/dev/d56366-7578-4efd-ab3c-dc9fb422579f.

[  OK  ] Unmounted /home.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Stopped File System Check on 
/dev/d1f8a9-2935-4cb6-9305-27cecd3b43c4.

[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Removed slice system-systemd\x2dfsck.slice.
[  OK  ] Reached target Shutdown.
[  192.175162] reboot: Power down
[  194.239408] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[  194.763806] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x

[  194.763806]
[  194.772949] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 
4.9.0-7-armmp-lpae #1 Debian 4.9.110-3+deb9u2

[  194.782500] Hardware name: Allwinner sun7i (A20) Family
[  194.787758] [] (unwind_backtrace) from [] 
(show_stack+0x20/0x24)
[  194.795506] [] (show_stack) from [] 
(dump_stack+0x90/0xa4)
[  194.802729] [] (dump_stack) from [] 
(panic+0x100/0x28c)
[  194.809692] [] (panic) from [] 
(complete_and_exit+0x0/0x2c)
[  194.817001] [] (complete_and_exit) from [] 
(SyS_reboot+0x1c8/0x238)
[  194.825004] [] (SyS_reboot) from [] 
(ret_fast_syscall+0x0/0x40)
[  194.832670] ---[ end Kernel panic - not syncing: Attempted to kill 
init! exitcode=0x

[  194.832670]

Bug#922478: have yet to find an armhf board that works with 4.9.144-3

[Adrian Bunk]

On Sun, Feb 17, 2019 at 09:52:48AM -0800, Vagrant Cascadian wrote:
> After upgrading to the latest 4.9.x kernel in sid, all of the armhf
> boards running this kernel failed to boot.
> 
> Adding to the list:
> 
> imx6: Cubox-i4pro, Cubox-i4x4, Wandboard Quad
> exynos5: Odroid-XU4
> exynos4: Odroid-U3
> rk3328: firefly-rk3288
> sunxi A20: Cubietruck
> 
> 
> So it clearly impacts a wide variety of systems...

debian/patches/debian/arm-avoid-abi-change-in-4.9.139.patch changes
the order of struct processor but lacks a corresponding change to 
arch/arm/mm/proc-macros.S

> live well,
>   vagrant

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: Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders many systems unbootable

[Debian Bug Tracking System]

Processing control commands:

> retitle 922478 upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 
> 4.9.144-3 renders many systems unbootable
Bug #922478 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 
4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable
Bug #922532 [src:linux] Debian 9.8 does'nt starts on Cubieboard
Changed Bug title to 'upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 
4.9.130-2 to 4.9.144-3 renders many systems unbootable' from 'upgrade 
linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders 
Bananapi and Lamobo R1 unbootable'.
Changed Bug title to 'upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 
4.9.130-2 to 4.9.144-3 renders many systems unbootable' from 'Debian 9.8 
does'nt starts on Cubieboard'.

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

Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders many systems unbootable

[Vagrant Cascadian]

Control: retitle 922478 upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 
4.9.130-2 to 4.9.144-3 renders many systems unbootable

On 2019-02-17, Timo Sigurdsson wrote:
> Cyril Brulebois schrieb am 17.02.2019 19:38:
>> Jürgen Löb  (2019-02-16):
>>> Package: linux-image-4.9.0-8-armmp-lpae
>>> Version: 4.9.144-3
>>> Severity: serious

FWIW, I also built a local package from 4.9.155-1~ from salsa/stretch
git, and it worked on a wandboard quad.

$ uname -a
Linux wbq0 4.9.0-9-armmp #1 SMP Debian 4.9.155-1~20190217~1 (2019-02-17) armv7l 
GNU/Linux

live well,
  vagrant


signature.asc
Description: PGP signature

Processed: affects 922543

[Debian Bug Tracking System]

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

> affects 922543 + release.debian.org
Bug #922543 [src:python-certbot] python-certbot: FTBFS in stretch when built 
with sbuild (unmet build-depends)
Added indication that 922543 affects release.debian.org
> thanks
Stopping processing here.

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

Bug#922543: python-certbot: FTBFS in stretch when built with sbuild (unmet build-depends)

[Santiago Vila]

Package: src:python-certbot
Version: 0.28.0-1~deb9u1
Severity: serious
Tags: ftbfs patch

Dear maintainer:

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


Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 778 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 copy:/<>/resolver-imjM6a/apt_archive ./ 
sbuild-build-depends-core-dummy 0.invalid.0 [778 B]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 778 B in 0s (0 B/s)
Selecting previously unselected package sbuild-build-depends-core-dummy.
(Reading database ... 13595 files and directories currently installed.)
Preparing to unpack .../sbuild-build-depends-core-dummy_0.invalid.0_amd64.deb 
...
Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-core-dummy (0.invalid.0) ...

+--+
| Check architectures  |
+--+

Arch check ok (amd64 included in all)

+--+
| Install package build dependencies   |
+--+


Setup apt archive
-

Merged Build-Depends: debhelper (>= 10~), dh-python, python3, python3-acme (>= 
0.26.0~), python3-configargparse (>= 0.10.0), python3-configobj, 
python3-cryptography (>= 1.2), python3-distutils | python3 (<< 3.6.5~), 
python3-josepy, python3-mock, python3-parsedatetime (>= 1.3), 
python3-repoze.sphinx.autointerface, python3-requests (>= 2.4.3), 
python3-rfc3339, python3-setuptools (>= 1.0), python3-sphinx (>= 1.2), 
python3-sphinx-rtd-theme, python3-tz, python3-zope.component, 
python3-zope.interface
Filtered Build-Depends: debhelper (>= 10~), dh-python, python3, python3-acme 
(>= 0.26.0~), python3-configargparse (>= 0.10.0), python3-configobj, 
python3-cryptography (>= 1.2), python3-distutils, python3-josepy, python3-mock, 
python3-parsedatetime (>= 1.3), python3-repoze.sphinx.autointerface, 
python3-requests (>= 2.4.3), python3-rfc3339, python3-setuptools (>= 1.0), 
python3-sphinx (>= 1.2), python3-sphinx-rtd-theme, python3-tz, 
python3-zope.component, python3-zope.interface
dpkg-deb: building package 'sbuild-build-depends-python-certbot-dummy' in 
'/<>/resolver-imjM6a/apt_archive/sbuild-build-depends-python-certbot-dummy.deb'.
dpkg-scanpackages: warning: Packages in archive but missing from override file:
dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
sbuild-build-depends-python-certbot-dummy
dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
Ign:1 copy:/<>/resolver-imjM6a/apt_archive ./ InRelease
Get:2 copy:/<>/resolver-imjM6a/apt_archive ./ Release [963 B]
Ign:3 copy:/<>/resolver-imjM6a/apt_archive ./ Release.gpg
Get:4 copy:/<>/resolver-imjM6a/apt_archive ./ Sources [684 B]
Get:5 copy:/<>/resolver-imjM6a/apt_archive ./ Packages [750 B]
Fetched 2397 B in 0s (0 B/s)
Reading package lists...
Reading package lists...

Install python-certbot build dependencies (apt-based resolver)
--

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 sbuild-build-depends-python-certbot-dummy : Depends: python3-distutils but it 
is not installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
E: Package installation failed
Not removing build depends: cloned chroot in use
/usr/bin/du: cannot access '/<>': No such file or directory
E: read_command failed to execute du
E: Cannot determine space needed for /<> (du failed)

Setup apt archive
-

Merged Build-Depends: dose-distcheck
Filtered Build-Depends: dose-distcheck
dpkg-deb: building package 'sbuild-build-depends-dose3-dummy' in 
'/<>/resolver-imjM6a/apt_archive/sbuild-build-depends-dose3-dummy.deb'.
dpkg-scanpackages: warning: Packages in archive but missing from override file:
dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
sbuild-build-depends-dose3-dummy sbuild-build-depends-python-certbot-dummy
dpkg-scanpackages: info: Wrote 3 entries to 

Bug#917760: marked as done (php-zeta-console-tools: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /usr/share/php/ezc/UnitTest/test/case.php:33)

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 20:53:20 +
with message-id 
and subject line Bug#917760: fixed in php-zeta-console-tools 1.7-4
has caused the Debian Bug report #917760,
regarding php-zeta-console-tools: FTBFS: PHP Fatal error:  Uncaught Error: 
Class 'PHPUnit_Framework_TestCase' not found in 
/usr/share/php/ezc/UnitTest/test/case.php:33
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.)


-- 
917760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-zeta-console-tools
Version: 1.7-3
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 '/<>'
> phpunit --exclude-group interactive
> PHP Fatal error:  Uncaught Error: Class 'PHPUnit_Framework_TestCase' not 
> found in /usr/share/php/ezc/UnitTest/test/case.php:33
> Stack trace:
> #0 /usr/share/php/ezc/UnitTest/autoload.php(19): require()
> #1 [internal function]: PHPUnit\Util\FileLoader::{closure}('ezcTestCase')
> #2 /<>/tests/argument_test.php(34): 
> spl_autoload_call('ezcTestCase')
> #3 /usr/share/php/PHPUnit/Util/FileLoader.php(57): 
> include_once('/build/php-zeta...')
> #4 /usr/share/php/PHPUnit/Util/FileLoader.php(45): 
> PHPUnit\Util\FileLoader::load('/build/php-zeta...')
> #5 /usr/share/php/PHPUnit/Framework/TestSuite.php(540): 
> PHPUnit\Util\FileLoader::checkAndLoad('/build/php-zeta...')
> #6 /usr/share/php/PHPUnit/Framework/TestSuite.php(618): 
> PHPUnit\Framework\TestSuite->addTestFile('/build/php-zeta...')
> #7 /usr/share/php/PHPUnit/Util/Configuration.php(1137): 
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #8 /usr/share/php/PHPUnit/Util/Configuration.php(996): 
> PHPUnit\Util\Configuration->getTestSuite(Object(DOMEleme in 
> /usr/share/php/ezc/UnitTest/test/case.php on line 33
> make[1]: *** [debian/rules:20: override_dh_auto_test] Error 255

The full build log is available from:
   
http://aws-logs.debian.net/2018/12/29/php-zeta-console-tools_1.7-3_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
php-zeta-console-tools, 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.
David Prévot  (supplier of updated php-zeta-console-tools 
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: Thu, 14 Feb 2019 16:03:05 -1000
Source: php-zeta-console-tools
Architecture: source
Version: 1.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 827420 882920 917760
Changes:
 php-zeta-console-tools (1.7-4) unstable; urgency=medium
 .
   [ Nishanth Aravamudan ]
   * Add missing dependency on patch for CI (Closes: #827420)
 .
   [ David Prévot ]
   * Move repository to salsa.d.o
   * Use https in Format
   * Drop get-orig-source target
   * Simplify clean target
   * Use debhelper-compat 12
   * Update Standards-Version to 4.3.0
   * Install NOTICE
   * Update for recent version of PHPUnit (Closes: #882920, #917760)
   * Update versioned build-dependency
Checksums-Sha1:
 4fc18d587851c553ed527401943e4a7e2d67fd2c 1930 php-zeta-console-tools_1.7-4.dsc
 49721e305770317a507c65f28c552ab83d924d80 8056 
php-zeta-console-tools_1.7-4.debian.tar.xz
 b7c63c4663ce90714d88f6c57637f2cc0506a707 6902 
php-zeta-console-tools_1.7-4_amd64.buildinfo
Checksums-Sha256:
 d26eb49b1fbdd8d772c91791f3901e8f343a6ddd5e0e5b5b59df90c9d2871975 1930 
php-zeta-console-tools_1.7-4.dsc
 

Bug#882920: marked as done (php-zeta-console-tools FTBFS with phpunit 6.4.4-2)

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 20:53:20 +
with message-id 
and subject line Bug#882920: fixed in php-zeta-console-tools 1.7-4
has caused the Debian Bug report #882920,
regarding php-zeta-console-tools FTBFS with phpunit 6.4.4-2
to be marked as done.

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

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


-- 
882920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-zeta-console-tools
Version: 1.7-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-zeta-console-tools.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-zeta-console-tools-1.7'
phpunit --exclude-group interactive
PHP Fatal error:  Class 'PHPUnit_Framework_TestCase' not found in 
/usr/share/php/ezc/UnitTest/test/case.php on line 33
debian/rules:20: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Source: php-zeta-console-tools
Source-Version: 1.7-4

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated php-zeta-console-tools 
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: Thu, 14 Feb 2019 16:03:05 -1000
Source: php-zeta-console-tools
Architecture: source
Version: 1.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 827420 882920 917760
Changes:
 php-zeta-console-tools (1.7-4) unstable; urgency=medium
 .
   [ Nishanth Aravamudan ]
   * Add missing dependency on patch for CI (Closes: #827420)
 .
   [ David Prévot ]
   * Move repository to salsa.d.o
   * Use https in Format
   * Drop get-orig-source target
   * Simplify clean target
   * Use debhelper-compat 12
   * Update Standards-Version to 4.3.0
   * Install NOTICE
   * Update for recent version of PHPUnit (Closes: #882920, #917760)
   * Update versioned build-dependency
Checksums-Sha1:
 4fc18d587851c553ed527401943e4a7e2d67fd2c 1930 php-zeta-console-tools_1.7-4.dsc
 49721e305770317a507c65f28c552ab83d924d80 8056 
php-zeta-console-tools_1.7-4.debian.tar.xz
 b7c63c4663ce90714d88f6c57637f2cc0506a707 6902 
php-zeta-console-tools_1.7-4_amd64.buildinfo
Checksums-Sha256:
 d26eb49b1fbdd8d772c91791f3901e8f343a6ddd5e0e5b5b59df90c9d2871975 1930 
php-zeta-console-tools_1.7-4.dsc
 3dd95c229e6a0bf33ae8f282893b79667190e71e791e7d535068d87362b23a98 8056 
php-zeta-console-tools_1.7-4.debian.tar.xz
 c299cecdbf0640010d89b582344510d62f146d483f34f2ad732810aedc7deeca 6902 
php-zeta-console-tools_1.7-4_amd64.buildinfo
Files:
 9759c5fc6d93b0f2c97ef52980655359 1930 php optional 
php-zeta-console-tools_1.7-4.dsc
 61d075f30b9977f9a4be79599500424e 8056 php optional 
php-zeta-console-tools_1.7-4.debian.tar.xz
 9115e0676fc8e5e8048f1fc077a7fab2 6902 php optional 
php-zeta-console-tools_1.7-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAlxpphISHHRhZmZpdEBk
ZWJpYW4ub3JnAAoJEAWMHPlE9r08Jq4IAIfO6Uu7JN0SWMXSCAaCxPces2QUG2Ib
E7v5CaAjBSvP0HWYNPVB8ggBJ/efMOcvXcf5bfta+6fktxV9dYsLycNAV9dXG9zK
x8S8s2v6nNA2ixR6gSYmiQfblgeypssMQtKus1gdDf3im0E1Y1BqxKTaWOJfxlFz
7NU1AP016dQYXmAy2wIuCz7TJKOK36+SKTCPW4ovXnNnq3S95YrOyCz8NXRgTabn
qP891oJtd0arr0Jgq14APN9dqFKCpPG8EdhMpOdmDRBCFj3rmJYUdzqIuWEW3KR+
RmmqpEa0b/4tzaC0g828GWi8GjQzaRkcjGo7f1crX/LI+taCWpxJxsU=
=zrSZ
-END PGP SIGNATURE End Message ---

Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable

[Timo Sigurdsson]

Hi,

Cyril Brulebois schrieb am 17.02.2019 19:38:

> Hi folks,
> 
> Jürgen Löb  (2019-02-16):
>> Package: linux-image-4.9.0-8-armmp-lpae
>> Version: 4.9.144-3
>> Severity: serious
>> 
>> Updated my Lamobo R1 board with apt update;apt upgrade
>> 
>> After the update uboot is struck at "Starting kernel". There is no
>> further output after "Starting kernel". Same happens on Bananapi 1
>> board. Unfortunately there is no more useful information.
> […]
> 
> Summing up, it looks like everybody in cc is confirming the regression
> happens between 4.9.130-2 and 4.9.144-3, with and without lpae, on
> various boards. Any chance you could check what happens with the
> 4.9.135-1 intermediary version that can be found on snapshot.debian.org?
> 
>  https://snapshot.debian.org/package/linux/4.9.135-1/
> 
> This might help narrow it down when the regression happened.
> 
> (And please use reply-all so that everyone is kept in the loop.)

So, I also tested 4.9.135-1 on a Bananapi board and can confirm it works.

I would suspect the issue is caused by Debian's kernel configuration or 
changes. The Kernel CI project has ARM hardware, including the Bananapi board 
and does tests of stable kernel updates to verify that the kernel boots. At 
least with multi_v7_defconfig and sunxi_defconfig, upstream 4.9.144 does boot 
on Allwinner-based hardware, see: 
https://kernelci.org/soc/allwinner/job/stable-rc/kernel/v4.9.144/

On a sidenote: This issue makes me wonder if Debian's approach to kernel 
updates (i.e. not bumping the version number/ABI and overwriting the kernel 
image and modules) is really the best option. IMHO Ubuntu's handling of kernel 
updates is more robust. It would have made things much easier today if I could 
have simply selected an older kernel in the bootloader, rather than having to 
recover one from a backup.

Kind regards,

Timo

Bug#922537: ansible: CVE-2019-3828

[Salvatore Bonaccorso]

Source: ansible
Version: 2.7.6+dfsg-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/ansible/ansible/pull/52133

Hi,

The following vulnerability was published for ansible.

CVE-2019-3828[0]:
path traversal in the fetch module

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-3828
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3828
[1] https://github.com/ansible/ansible/pull/52133

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable

[Cyril Brulebois]

Hi,

Reco  (2019-02-17):
> 1) Install qemu-system-arm.
> 
> 2) Unpack kernel .deb, locate vmlinuz-4.9.0-8-armmp.
> Or search your just-built zImage.
> 
> 3) Run qemu (no root required):
> 
> qemu-system-arm -M virt -nographic -kernel vmlinuz-4.9.0-8-armmp
> 
> If you see a kernel panic - the outcome is positive, the kernel is OK.
> If it just stays there eating 100% CPU - the outcome is negative.

Perfect, checked with .135-1 and .144-3.

That's super useful, much appreciated!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: reassign 922532 to src:linux, forcibly merging 922478 922532

[Debian Bug Tracking System]

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

> reassign 922532 src:linux 4.9.144-3
Bug #922532 [src:linux] Debian 9.8 does'nt starts on Cubieboard
Bug #922478 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 
4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable
Ignoring request to reassign bug #922532 to the same package
Ignoring request to reassign bug #922478 to the same package
Bug #922532 [src:linux] Debian 9.8 does'nt starts on Cubieboard
Bug #922478 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 
4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable
Ignoring request to alter found versions of bug #922532 to the same values 
previously set
Ignoring request to alter found versions of bug #922478 to the same values 
previously set
> forcemerge 922478 922532
Bug #922478 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 
4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable
Bug #922532 [src:linux] Debian 9.8 does'nt starts on Cubieboard
Bug #922532 [src:linux] Debian 9.8 does'nt starts on Cubieboard
Merged 922478 922532
> thanks
Stopping processing here.

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

Processed: merge

[Debian Bug Tracking System]

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

> reassign 922532 src:linux
Bug #922532 [linux-base] Debian 9.8 does'nt starts on Cubieboard
Bug reassigned from package 'linux-base' to 'src:linux'.
No longer marked as found in versions linux-base/4.5.
Ignoring request to alter fixed versions of bug #922532 to the same values 
previously set
> forcemerge 922478 922532
Bug #922478 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 
4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable
Bug #922532 [src:linux] Debian 9.8 does'nt starts on Cubieboard
Severity set to 'serious' from 'normal'
Marked as found in versions linux/4.9.144-3.
Merged 922478 922532
> thanks
Stopping processing here.

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

Bug#921837: marked as done (mopidy: FTBFS (dh_installman: Could not determine section for ./docs/_build/man/_static))

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 19:49:55 +
with message-id 
and subject line Bug#921837: fixed in mopidy 2.2.2-1
has caused the Debian Bug report #921837,
regarding mopidy: FTBFS (dh_installman: Could not determine section for 
./docs/_build/man/_static)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,sphinxdoc,systemd --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
   dh_auto_test -i -O--buildsystem=pybuild
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --with python2,sphinxdoc,systemd --buildsystem=pybuild
   dh_testroot -i -O--buildsystem=pybuild
   dh_prep -i -O--buildsystem=pybuild
   dh_installdirs -i -O--buildsystem=pybuild

[... snipped ...]

WARNING: autodoc: failed to import attribute 
u'core.PlaybackController.current_track' from module u'mopidy'; the following 
exception was raised:
No module named pykka
WARNING: autodoc: failed to import attribute u'core.PlaybackController.state' 
from module u'mopidy'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import attribute 
u'core.PlaybackController.time_position' from module u'mopidy'; the following 
exception was raised:
No module named pykka
WARNING: autodoc: failed to import attribute u'core.PlaybackController.mute' 
from module u'mopidy'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import attribute u'core.PlaybackController.volume' 
from module u'mopidy'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import method u'core.LibraryController.find_exact' 
from module u'mopidy'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import method u'core.PlaylistsController.filter' 
from module u'mopidy'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import method 
u'core.PlaylistsController.get_playlists' from module u'mopidy'; the following 
exception was raised:
No module named pykka
WARNING: autodoc: failed to import attribute 
u'core.PlaylistsController.playlists' from module u'mopidy'; the following 
exception was raised:
No module named pykka
WARNING: autodoc: failed to import class u'mixer.Mixer' from module u'mopidy'; 
the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import class u'mixer.MixerListener' from module 
u'mopidy'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import module u'dispatcher' from module 
u'mopidy.mpd'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import module u'playback' from module 
u'mopidy.mpd.protocol'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import module u'status' from module 
u'mopidy.mpd.protocol'; the following exception was raised:
No module named pykka
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
writing... mopidy.1 { } 
build succeeded, 100 warnings.

The manual pages are in _build/man.

Build finished. The manual pages are in _build/man.
make[2]: Leaving directory '/<>/docs'
dh_installman
dh_installman: Could not determine section for ./docs/_build/man/_static
dh_installman: Aborting due to earlier error
make[1]: *** [debian/rules:40: override_dh_installman] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

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

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

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

If this is really a bug in 

Bug#922507: marked as done (wml: Missing depends on libgd-perl)

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 19:50:08 +
with message-id 
and subject line Bug#922507: fixed in wml 2.12.2~ds1-2
has caused the Debian Bug report #922507,
regarding wml: Missing depends on libgd-perl
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.)


-- 
922507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wml
Version: 2.12.2~ds1-1
Severity: serious

Hi,

I'm getting the following error:
Can't locate GD.pm in @INC (you may need to install the GD module) (@INC 
contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 
/usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl) at /tmp/wml.28518.tmp1 line 197.
BEGIN failed--compilation aborted at /tmp/wml.28518.tmp1 line 197.

It seems that this was part of wml in older versions, but not in
the current version.


Kurt
--- End Message ---
--- Begin Message ---
Source: wml
Source-Version: 2.12.2~ds1-2

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated wml package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 17 Feb 2019 18:39:38 +0100
Source: wml
Binary: wml
Architecture: source all
Version: 2.12.2~ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Axel Beckert 
Changed-By: Axel Beckert 
Description:
 wml- off-line HTML generation toolkit
Closes: 922507
Changes:
 wml (2.12.2~ds1-2) unstable; urgency=medium
 .
   * Recommend libgd-perl: wml::des::imgbg now uses GD.pm instead of the
 vanished WML::GD which used the C library libgd3 directly. Thanks to
 Kurt Roeckx for the bug report! (Closes: #922507)
   * Install all files except the .spec files from wml_contrib into
 /usr/share/wml/contrib/ instead of /usr/share/doc/wml/wml_contrib/.
 + Make tkwmd executable via override and suggest perl-tk for it.
 + Replace ancient workaround with proper shebang line in wml1to2.
 + Add lintian override for /usr/share/wml/contrib/README.
Checksums-Sha1:
 58e3f69b5d3341e63b06f39e66ac7e2dfb6ab767 2389 wml_2.12.2~ds1-2.dsc
 b0964ebe00e02ed41ce36f20ea860f23fff01e7c 27052 wml_2.12.2~ds1-2.debian.tar.xz
 f6aaf4fdbb16853706125f521a98dae4c1917de5 470996 wml_2.12.2~ds1-2_all.deb
 99e7e23d4198ab39a1723f69bfc232c1fccf2d40 10132 wml_2.12.2~ds1-2_amd64.buildinfo
Checksums-Sha256:
 c381f2148509e571b9ce924ed334440f09ad46df1a60a4fa584d2357fa477a6b 2389 
wml_2.12.2~ds1-2.dsc
 2b7eeafb7f903a1698eb0d8913151ea810543da73cbb050bccb5e1d92f98fd63 27052 
wml_2.12.2~ds1-2.debian.tar.xz
 a8eecc961a75bbddb6314a1827eefb2f8d1030465f11f8ef7983fc49bea30727 470996 
wml_2.12.2~ds1-2_all.deb
 3fb1664de81b356b54d5d2f363e5d2f7d44900767ec2ac54112c35c6b4a686b1 10132 
wml_2.12.2~ds1-2_amd64.buildinfo
Files:
 5cce19ceb149ad526eb5773c0d47bc61 2389 web optional wml_2.12.2~ds1-2.dsc
 e04d5e34a9dc6a6d691e61635050a2a5 27052 web optional 
wml_2.12.2~ds1-2.debian.tar.xz
 16d90ae69e562ad8972375c884095df7 470996 web optional wml_2.12.2~ds1-2_all.deb
 b52656aa267d3c95477a4b536ddf3762 10132 web optional 
wml_2.12.2~ds1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAlxpr5IACgkQa+Zjx1o1
yXXu5hAAvcwxtpwoBNf1XIw2guYtfMJbBWTZUWX910ziyUURFarXaDOi4A1jLaZO
n/fR1/5jAj3keUI7WlsuST/kD0z32zg7fQaL4W6GLfb/7vCrO901/qTeYl7c10uc
CFt9ZB5WqhL+H2hAYgveaMQ6uf97EjbbsYj3z/7NNyeNcO4TIAH4MuP8bTrZCGKS
y+8PgfwvsOs2I+BU3orR4c8E8TD0n2TScsj+Vp0KI5BpYuWW3UiV8YAHkeXYVXQQ
DnrC7anVEc+qtMPZEl/zobyHrkUVc3UsiNVHkypuHgq6InSUxhyiWa/BeGqx1ldP
oJdx0ejwQ8dMXcViy2RsYDE5s7afrX5JEgcYeIOAOFWpwnMWuP7NlJK/h9dNrdMS
C/N0aFssQDbGauF+nIVZX0XdR5lcdcI3Am+sfHOxa0uuGk9Rn9DRJVNnQTnskuqt
sCTDPXU3BdeAEOHNpVNKvtOcTJTp43X3M+/C+YZw6RawwD+FOzIZbsPJXSXtzzVJ
PFR7izix9Maa9wc12LSqwroiYXSus192JeOg7Z/TyM1NOK2gZ6sc9N1v0tySOjwd
xqStObRgub8BEpFAFf+YcGwk5Q5+E8lMmc8NwCXEB9RDdj0GbC2kKU8P/DvHWknV
uI9Oa1x38fnVj0APkWHI799cHLo2WPMGPhY0OUXjhWUuUIbgVMU=
=qfIZ

Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable

[Reco]

Hi.

On Sun, Feb 17, 2019 at 08:27:34PM +0100, Cyril Brulebois wrote:
> Hi,
> 
> Reco  (2019-02-17):
> > Did this already in QEMU (virt board).
> > 4.9.135-1 works.
> > 4.9.144-1 (next one) is broken.
> 
> Is there any chance you could share how to get such a VM set up in QEMU?
> 
> I'd be happy to try a few kernel builds, but having a quick way to check
> whether a given kernel build is OK/KO would be much appreciated.

1) Install qemu-system-arm.

2) Unpack kernel .deb, locate vmlinuz-4.9.0-8-armmp.
Or search your just-built zImage.

3) Run qemu (no root required):

qemu-system-arm -M virt -nographic -kernel vmlinuz-4.9.0-8-armmp

If you see a kernel panic - the outcome is positive, the kernel is OK.
If it just stays there eating 100% CPU - the outcome is negative.

Reco

Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable

[Cyril Brulebois]

Hi,

Reco  (2019-02-17):
> Did this already in QEMU (virt board).
> 4.9.135-1 works.
> 4.9.144-1 (next one) is broken.

Is there any chance you could share how to get such a VM set up in QEMU?

I'd be happy to try a few kernel builds, but having a quick way to check
whether a given kernel build is OK/KO would be much appreciated.
 

Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#915311: marked as done (dumb-init FTBFS on mips*: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 19:19:20 +
with message-id 
and subject line Bug#915311: fixed in dumb-init 1.2.2-1.1
has caused the Debian Bug report #915311,
regarding dumb-init FTBFS on mips*: test failures
to be marked as done.

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

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


-- 
915311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dumb-init
Version: 1.2.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=dumb-init

...
=== FAILURES ===
_ test_all_processes_receive_term_on_exit_if_setsid[1] _

@pytest.mark.usefixtures('both_debug_modes', 'setsid_enabled')
def test_all_processes_receive_term_on_exit_if_setsid():
"""If the child exits for some reason, dumb-init should send TERM to all
processes in its session if setsid mode is enabled."""
>   child_pid, child_stdout = spawn_process_which_dies_with_children()

tests/child_processes_test.py:109: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def spawn_process_which_dies_with_children():
"""Spawn a process which spawns some children and then dies without
signaling them, wrapped in dumb-init.

Returns a tuple (child pid, child stdout pipe), where the child is
print_signals. This is useful because you can signal the PID and see if
anything gets printed onto the stdout pipe.
"""
proc = Popen(
(
'dumb-init',
'sh', '-c',

# we need to sleep before the shell exits, or dumb-init might 
send
# TERM to print_signals before it has had time to register 
custom
# signal handlers
'{python} -m testing.print_signals & sleep 0.1'.format(
python=sys.executable,
),
),
stdout=PIPE,
)
proc.wait()
assert proc.returncode == 0

# read a line from print_signals, figure out its pid
line = proc.stdout.readline()
match = re.match(b'ready \(pid: ([0-9]+)\)\n', line)
>   assert match, line
E   AssertionError: 
E   assert None

tests/child_processes_test.py:95: AssertionError
- Captured stderr call -
[dumb-init] Running in debug mode.
[dumb-init] Unable to detach from controlling tty (errno=25 Inappropriate ioctl 
for device).
[dumb-init] Child spawned with PID 7035.
[dumb-init] Unable to attach to controlling tty (errno=25 Inappropriate ioctl 
for device).
[dumb-init] setsid complete.
[dumb-init] Received signal 18.
[dumb-init] A child with PID 7035 exited with exit status 0.
[dumb-init] Forwarded signal 15 to children.
[dumb-init] Child exited with status 0. Goodbye.
_ test_all_processes_receive_term_on_exit_if_setsid[0] _

@pytest.mark.usefixtures('both_debug_modes', 'setsid_enabled')
def test_all_processes_receive_term_on_exit_if_setsid():
"""If the child exits for some reason, dumb-init should send TERM to all
processes in its session if setsid mode is enabled."""
>   child_pid, child_stdout = spawn_process_which_dies_with_children()

tests/child_processes_test.py:109: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def spawn_process_which_dies_with_children():
"""Spawn a process which spawns some children and then dies without
signaling them, wrapped in dumb-init.

Returns a tuple (child pid, child stdout pipe), where the child is
print_signals. This is useful because you can signal the PID and see if
anything gets printed onto the stdout pipe.
"""
proc = Popen(
(
'dumb-init',
'sh', '-c',

# we need to sleep before the shell exits, or dumb-init might 
send
# TERM to print_signals before it has had time to register 
custom
# signal handlers
'{python} -m testing.print_signals & sleep 0.1'.format(
python=sys.executable,
),
),
stdout=PIPE,
)
proc.wait()
assert proc.returncode == 0

# read a line from print_signals, figure out its pid
line = proc.stdout.readline()
match = re.match(b'ready \(pid: ([0-9]+)\)\n', line)
>

Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable

[Reco]

Hi.

On Sun, Feb 17, 2019 at 07:38:18PM +0100, Cyril Brulebois wrote:
> Hi folks,
> 
> Jürgen Löb  (2019-02-16):
> > Package: linux-image-4.9.0-8-armmp-lpae
> > Version: 4.9.144-3
> > Severity: serious
> > 
> > Updated my Lamobo R1 board with apt update;apt upgrade
> > 
> > After the update uboot is struck at "Starting kernel". There is no
> > further output after "Starting kernel". Same happens on Bananapi 1
> > board. Unfortunately there is no more useful information.
> […]
> 
> Summing up, it looks like everybody in cc is confirming the regression
> happens between 4.9.130-2 and 4.9.144-3, with and without lpae, on
> various boards. Any chance you could check what happens with the
> 4.9.135-1 intermediary version that can be found on snapshot.debian.org?

Did this already in QEMU (virt board).
4.9.135-1 works.
4.9.144-1 (next one) is broken.

The problem is - 4.9.144-1 introduced large amount of changes, including
two Spectre mitigations.

My attempts to build a kernel with CONFIG_SPECTRE=n yielded unbootable
kernels, which may mean that:

a) Spectre mitigations are not related to the problem.
b) My kernel-rebuilding skill could use some improvement.

Reco

Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable

[Cyril Brulebois]

Hi folks,

Jürgen Löb  (2019-02-16):
> Package: linux-image-4.9.0-8-armmp-lpae
> Version: 4.9.144-3
> Severity: serious
> 
> Updated my Lamobo R1 board with apt update;apt upgrade
> 
> After the update uboot is struck at "Starting kernel". There is no
> further output after "Starting kernel". Same happens on Bananapi 1
> board. Unfortunately there is no more useful information.
[…]

Summing up, it looks like everybody in cc is confirming the regression
happens between 4.9.130-2 and 4.9.144-3, with and without lpae, on
various boards. Any chance you could check what happens with the
4.9.135-1 intermediary version that can be found on snapshot.debian.org?

  https://snapshot.debian.org/package/linux/4.9.135-1/

This might help narrow it down when the regression happened.

(And please use reply-all so that everyone is kept in the loop.)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#922478: have yet to find an armhf board that works with 4.9.144-3

[Vagrant Cascadian]

After upgrading to the latest 4.9.x kernel in sid, all of the armhf
boards running this kernel failed to boot.

Adding to the list:

imx6: Cubox-i4pro, Cubox-i4x4, Wandboard Quad
exynos5: Odroid-XU4
exynos4: Odroid-U3
rk3328: firefly-rk3288
sunxi A20: Cubietruck


So it clearly impacts a wide variety of systems...


live well,
  vagrant


signature.asc
Description: PGP signature

Processed: Bug#919917: yui-compressor: insufficient java dependency in jessie

[Debian Bug Tracking System]

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

> severity 919917 normal
Bug #919917 [yui-compressor] yui-compressor: insufficient java dependency in 
jessie
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#919917: yui-compressor: insufficient java dependency in jessie

[Markus Koschany]

Contol: severity -1 normal

On Mon, 21 Jan 2019 20:13:37 -0800 tony mancill  wrote:
> On Sun, Jan 20, 2019 at 06:14:31PM +0100, Andreas Beckmann wrote:
> > Package: yui-compressor
> > Version: 2.4.7-2
> > Severity: serious
> > Tags: jessie
> > User: debian...@lists.debian.org
> > Usertags: piuparts
> > Control: affects -1 + libjs-protoaculous
> > Control: found -1 libjs-protoaculous/5
> 
> Hi Andreas,
> 
> The version of the package in the bug is found in jessie (oldstable)
> and doesn't exist in stretch (stable) or buster (testing).  Also, I
> believe the problem is with the version of default-jre-headless in
> jessie, given that the Depends hasn't changed since 2012.
> 
> Are you requesting that the bug be addressed for jessie?  (Do we need to
> open a RC-severity bug for oldstable right before the buster freeze?)

Bugs in Jessie not affecting Buster are not release critical.





signature.asc
Description: OpenPGP digital signature

Processed: Reassign RC bugs of affected packages to maven-javadoc-plugin

[Debian Bug Tracking System]

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

> reassign 920747 src:maven-javadoc-plugin
Bug #920747 [src:dirgra] dirgra FTBFS with recent OpenJDK
Bug reassigned from package 'src:dirgra' to 'src:maven-javadoc-plugin'.
No longer marked as found in versions dirgra/0.3-1.
Ignoring request to alter fixed versions of bug #920747 to the same values 
previously set
> reassign 920748 src:maven-javadoc-plugin
Bug #920748 [src:jnr-posix] jnr-posix FTBFS with recent OpenJDK
Bug reassigned from package 'src:jnr-posix' to 'src:maven-javadoc-plugin'.
No longer marked as found in versions jnr-posix/3.0.45-2.
Ignoring request to alter fixed versions of bug #920748 to the same values 
previously set
> forcemerge 919798 920747 920748
Bug #919798 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919800 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919874 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919875 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919878 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #920750 [src:maven-javadoc-plugin] libparanamer-java FTBFS with recent 
OpenJDK
Bug #920794 [src:maven-javadoc-plugin] localizer FTBFS with recent OpenJDK
Bug #920795 [src:maven-javadoc-plugin] weupnp FTBFS with recent OpenJDK
Bug #922369 [src:maven-javadoc-plugin] javamail: FTBFS on Buster/Sid
Bug #920747 [src:maven-javadoc-plugin] dirgra FTBFS with recent OpenJDK
920331 was blocked by: 919875 919878 919798 919800 919895 920750 919883 920795 
920794 919874 919876 920020 922369 919831 919968 919801
920331 was not blocking any bugs.
Added blocking bug(s) of 920331: 920747
Added tag(s) patch, sid, and buster.
Bug #920748 [src:maven-javadoc-plugin] jnr-posix FTBFS with recent OpenJDK
920331 was blocked by: 919968 920794 920750 919798 919883 920795 922369 919801 
919874 919876 919895 920747 919831 919875 920020 919800 919878
920331 was not blocking any bugs.
Added blocking bug(s) of 920331: 920748
Added tag(s) buster, patch, and sid.
Bug #919800 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919874 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919875 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919878 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #920750 [src:maven-javadoc-plugin] libparanamer-java FTBFS with recent 
OpenJDK
Bug #920794 [src:maven-javadoc-plugin] localizer FTBFS with recent OpenJDK
Bug #920795 [src:maven-javadoc-plugin] weupnp FTBFS with recent OpenJDK
Bug #922369 [src:maven-javadoc-plugin] javamail: FTBFS on Buster/Sid
Merged 919798 919800 919874 919875 919878 920747 920748 920750 920794 920795 
922369
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
919798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919798
919800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919800
919874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919874
919875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919875
919878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919878
920331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920331
920747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920747
920748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920748
920750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920750
920794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920794
920795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920795
922369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Reassign RC bugs of affected packages to maven-javadoc-plugin

[Debian Bug Tracking System]

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

> reassign 922369 src:maven-javadoc-plugin
Bug #922369 [src:javamail] javamail: FTBFS on Buster/Sid
Bug reassigned from package 'src:javamail' to 'src:maven-javadoc-plugin'.
Ignoring request to alter found versions of bug #922369 to the same values 
previously set
Ignoring request to alter fixed versions of bug #922369 to the same values 
previously set
> forcemerge 919798 922369
Bug #919798 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919800 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919874 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919875 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919878 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #920750 [src:maven-javadoc-plugin] libparanamer-java FTBFS with recent 
OpenJDK
Bug #920794 [src:maven-javadoc-plugin] localizer FTBFS with recent OpenJDK
Bug #920795 [src:maven-javadoc-plugin] weupnp FTBFS with recent OpenJDK
Bug #922369 [src:maven-javadoc-plugin] javamail: FTBFS on Buster/Sid
920331 was blocked by: 919876 919883 920020 919968 919798 920750 920794 919874 
919831 919801 919800 919875 920795 919878 919895
920331 was not blocking any bugs.
Added blocking bug(s) of 920331: 922369
Added tag(s) sid, buster, and patch.
Bug #919800 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919874 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919875 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919878 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #920750 [src:maven-javadoc-plugin] libparanamer-java FTBFS with recent 
OpenJDK
Bug #920794 [src:maven-javadoc-plugin] localizer FTBFS with recent OpenJDK
Bug #920795 [src:maven-javadoc-plugin] weupnp FTBFS with recent OpenJDK
Merged 919798 919800 919874 919875 919878 920750 920794 920795 922369
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
919798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919798
919800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919800
919874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919874
919875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919875
919878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919878
920331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920331
920750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920750
920794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920794
920795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920795
922369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#921790: liquidsoap: FTBFS (ld: cannot find -lexif)

[Andrey Rahmatullin]

On Sun, Feb 17, 2019 at 04:58:58PM +0200, Kyle Robbertze wrote:
> This is because version 1.0.1 of Camomile is in unstable. I am busy
> packaging liquidsoap 1.3.4, which is compatible with newer versions of
> Camomile and will fix both these issues.
Please note the freeze policy.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Processed: Reassign RC bugs of affected packages to maven-javadoc-plugin

[Debian Bug Tracking System]

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

> reassign 919798 src:maven-javadoc-plugin
Bug #919798 [src:antlr4] javadoc: The code being documented uses modules but 
the packages defined in … are in the unnamed module
Bug reassigned from package 'src:antlr4' to 'src:maven-javadoc-plugin'.
Ignoring request to alter found versions of bug #919798 to the same values 
previously set
Ignoring request to alter fixed versions of bug #919798 to the same values 
previously set
> reassign 919800 src:maven-javadoc-plugin
Bug #919800 [src:jackson-databind] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug reassigned from package 'src:jackson-databind' to 
'src:maven-javadoc-plugin'.
Ignoring request to alter found versions of bug #919800 to the same values 
previously set
Ignoring request to alter fixed versions of bug #919800 to the same values 
previously set
> reassign 919874 src:maven-javadoc-plugin
Bug #919874 [src:bsaf] javadoc: The code being documented uses modules but the 
packages defined in … are in the unnamed module
Bug reassigned from package 'src:bsaf' to 'src:maven-javadoc-plugin'.
Ignoring request to alter found versions of bug #919874 to the same values 
previously set
Ignoring request to alter fixed versions of bug #919874 to the same values 
previously set
> reassign 919875 src:maven-javadoc-plugin
Bug #919875 [src:commons-csv] javadoc: The code being documented uses modules 
but the packages defined in … are in the unnamed module
Bug reassigned from package 'src:commons-csv' to 'src:maven-javadoc-plugin'.
Ignoring request to alter found versions of bug #919875 to the same values 
previously set
Ignoring request to alter fixed versions of bug #919875 to the same values 
previously set
> reassign 919878 src:maven-javadoc-plugin
Bug #919878 [src:servlet-api] javadoc: The code being documented uses modules 
but the packages defined in … are in the unnamed module
Bug reassigned from package 'src:servlet-api' to 'src:maven-javadoc-plugin'.
Ignoring request to alter found versions of bug #919878 to the same values 
previously set
Ignoring request to alter fixed versions of bug #919878 to the same values 
previously set
> reassign 920750 src:maven-javadoc-plugin
Bug #920750 [src:libparanamer-java] libparanamer-java FTBFS with recent OpenJDK
Bug reassigned from package 'src:libparanamer-java' to 
'src:maven-javadoc-plugin'.
No longer marked as found in versions libparanamer-java/2.8-4.
Ignoring request to alter fixed versions of bug #920750 to the same values 
previously set
> reassign 920794 src:maven-javadoc-plugin
Bug #920794 [src:localizer] localizer FTBFS with recent OpenJDK
Bug reassigned from package 'src:localizer' to 'src:maven-javadoc-plugin'.
No longer marked as found in versions localizer/1.13-3.
Ignoring request to alter fixed versions of bug #920794 to the same values 
previously set
> reassign 920795 src:maven-javadoc-plugin
Bug #920795 [src:weupnp] weupnp FTBFS with recent OpenJDK
Bug reassigned from package 'src:weupnp' to 'src:maven-javadoc-plugin'.
No longer marked as found in versions weupnp/0.1.4-1.
Ignoring request to alter fixed versions of bug #920795 to the same values 
previously set
> forcemerge 919798 919800 919874 919875 919878 920750 920794 920795
Bug #919798 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #920795 [src:maven-javadoc-plugin] weupnp FTBFS with recent OpenJDK
920331 was blocked by: 919831 919800 919801 919798 919874 920020 919876 919878 
919883 919875 919895 919968
920331 was not blocking any bugs.
Added blocking bug(s) of 920331: 920795
Added tag(s) patch.
Bug #920750 [src:maven-javadoc-plugin] libparanamer-java FTBFS with recent 
OpenJDK
920331 was blocked by: 919878 919895 920795 919875 919801 919800 919874 919831 
919798 919968 919883 920020 919876
920331 was not blocking any bugs.
Added blocking bug(s) of 920331: 920750
Added tag(s) patch, sid, and buster.
Bug #920794 [src:maven-javadoc-plugin] localizer FTBFS with recent OpenJDK
920331 was blocked by: 919798 919968 920750 920020 919876 919883 919801 919800 
919874 919831 920795 919875 919878 919895
920331 was not blocking any bugs.
Added blocking bug(s) of 920331: 920794
Added tag(s) buster, sid, and patch.
Bug #919800 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919874 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919875 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Bug #919878 [src:maven-javadoc-plugin] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Merged 919798 919800 919874 919875 919878 920750 920794 920795
> thanks
Stopping 

Bug#919831: Javadoc -link makes broken links if module name matches package name

[tony mancill]

On Fri, Feb 15, 2019 at 08:22:14PM +0100, Markus Koschany wrote:
> Am 15.02.19 um 15:42 schrieb tony mancill:
> [...]
> > Any thoughts on whether we should focus on fixing javadoc generation or
> > look at other ways to mitigate the FTBFS?
> 
> Like burning all those -doc packages? :)
> 
> In my opinion we could ask Robert Scholte for advice. He is chairman of
> Apache Maven and directly involved in fixing this bug. If he doesn't
> know
> 
> However I think I have found a workaround, and we all love workarounds,
> don't we.
> 
> In your initial post you pointed to a related bug report. [1] That made
> me think and also read the fine Maven Javadoc documentation. There is an
> option called detectJavaApiLink
> 
> https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink
> 
> If I add
> 
> detectJavaApiLink=false to debian/maven.properties in libparanamer-java,
> the package builds from source again.
> 
> Maybe we should patch our tools and set this property to false and move
> on for now? Hopefully in a few months this will just work again without
> changing this option, when maven-javadoc-plugin et al. have been
> catching up?

Hi Markus,

Very nice find about detectJavaApiLink!  I'll try patching the
default value in current maven-javadoc-plugin here [1] and kick off as
large of a ratt build as I can see about coverage.  Assuming that is
successful, we could then look into what it would take to schedule a
binary NMU all packages that depend on maven-javadoc-plugin.  (Or maybe
someone on the list has a better idea?)

Do we know if there is any downside to disabling this by default?

Thanks!
tony

[1] 
https://salsa.debian.org/java-team/maven-javadoc-plugin/blob/master/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L569


signature.asc
Description: PGP signature

Bug#921790: marked as done (liquidsoap: FTBFS (ld: cannot find -lexif))

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 16:04:22 +
with message-id 
and subject line Bug#921790: fixed in camlimages 1:4.2.6-4
has caused the Debian Bug report #921790,
regarding liquidsoap: FTBFS (ld: cannot find -lexif)
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.)


-- 
921790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:liquidsoap
Version: 1.3.3-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with elpa,ocaml
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
./bootstrap
make[1]: Leaving directory '/<>'
   dh_ocamlinit -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- 
--with-default-font=/usr/share/fonts/truetype/liberation/LiberationMono-Regular.ttf
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking 
--with-default-font=/usr/share/fonts/truetype/liberation/LiberationMono-Regular.ttf
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c

[... snipped ...]

OCAMLOPT -c decoder/image/ppm_decoder.ml
OCAMLOPT -c decoder/external_decoder.ml
OCAMLOPT -c decoder/raw_audio_decoder.ml
OCAMLOPT -c decoder/flac_decoder.ml
OCAMLOPT -c decoder/aac_decoder.ml
OCAMLOPT -c decoder/ogg_decoder.ml
OCAMLOPT -c decoder/mad_decoder.ml
OCAMLOPT -c decoder/vorbisduration.ml
OCAMLOPT -c decoder/flacduration.ml
OCAMLOPT -c decoder/ogg_flac_duration.ml
OCAMLOPT -c decoder/taglib_plug.ml
OCAMLOPT -c decoder/image/camlimages_decoder.ml
OCAMLOPT -c decoder/image/sdlimage_decoder.ml
OCAMLOPT -c decoder/gstreamer_decoder.ml
OCAMLOPT -c shebang.ml
OCAMLOPT -c lang/lang_builtins.ml
OCAMLOPT -c lang/builtins_json.ml
OCAMLOPT -c lang/builtins_harbor.ml
OCAMLOPT -c lang/builtins_dtools.ml
OCAMLOPT -c lang/builtins_time.ml
OCAMLOPT -c lang/builtins_callbacks.ml
OCAMLOPT -c lang/builtins_lo.mli
OCAMLOPT -c lang/builtins_lo.ml
OCAMLOPT -c lang/builtins_magic.ml
OCAMLOPT -c lang/builtins_cry.ml
OCAMLOPT -c lang/builtins_lastfm.ml
OCAMLOPT -c main.ml
OCAMLOPT -c runner.ml
CC -c tools/unix_c.c
CC -c io/oss_io_c.c
OCAMLOPT -o liquidsoap
/usr/bin/ld: cannot find -lexif
collect2: error: ld returned 1 exit status
File "caml_startup", line 1:
Error: Error during linking
make[4]: *** [../Makefile.rules:110: liquidsoap] Error 2
make[4]: Leaving directory '/<>/src'
make[3]: *** [../Makefile.rules:67: all-auto-ocaml-prog] Error 2
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile.rules:27: all-subdirs] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

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

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

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

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 ---
Source: camlimages
Source-Version: 1:4.2.6-4

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

Debian distribution maintenance software
pp.
Kyle Robbertze  (supplier of updated camlimages package)

(This message was 

Bug#921790: Bug #921790 in camlimages marked as pending

[Kyle Robbertze]

Control: tag -1 pending

Hello,

Bug #921790 in camlimages 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/ocaml-team/camlimages/commit/64a50967726d79d58984e3f69930e8d811e399d8


Depend on libexif-dev (Closes: #921790)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/921790

Processed: Bug #921790 in camlimages marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #921790 [libcamlimages-ocaml-dev] liquidsoap: FTBFS (ld: cannot find -lexif)
Added tag(s) pending.

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

Processed: -lexif

[Debian Bug Tracking System]

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

> affects 921790 + src:liquidsoap
Bug #921790 [libcamlimages-ocaml-dev] liquidsoap: FTBFS (ld: cannot find -lexif)
Added indication that 921790 affects src:liquidsoap
> thanks
Stopping processing here.

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

Processed: -lexif

[Debian Bug Tracking System]

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

> reassign 921790 libcamlimages-ocaml-dev
Bug #921790 [src:liquidsoap] liquidsoap: FTBFS (ld: cannot find -lexif)
Bug reassigned from package 'src:liquidsoap' to 'libcamlimages-ocaml-dev'.
No longer marked as found in versions liquidsoap/1.3.3-2.
Ignoring request to alter fixed versions of bug #921790 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#922500: tex-common: Fails to install with LC_TIME=en_DE.UTF-8

[Norbert Preining]

And by the way, quoting from your first message

> LANG=C sudo aptitude
> Warning: Invalid locale (please review locale settings, this might
> lead to problems later):

And it did.

Best wishes


On February 17, 2019 3:11:41 PM GMT+01:00, Norbert Preining  
wrote:
>You set the locale for root while installing, this has nothing to do
>with user settings what so ever. If you remove bash and a different
>program fails to install, do you think this is an error of the program
>bring installed?
>
>If locales are not properly set up, then luatex fails to build a
>format, this is independent from the Debian packaging.
>
>Anyway, you reopened the bug, so let's enjoy it.
>
>Best
>
>Norbert
>
>On February 17, 2019 1:06:08 PM GMT+01:00, Charlemagne Lasse
> wrote:
>>> On Sun, 17 Feb 2019, Charlemagne Lasse wrote:
>>> > perl: warning: Setting locale failed.
>>> > perl: warning: Please check that your locale settings:
>>> > LANGUAGE = "en_US:en",
>>> > LC_ALL = (unset),
>>> > LC_TIME = "en_DE.UTF-8",
>>> > LANG = "C"
>>> > are supported and installed on your system.
>>>
>>> > locale: Cannot set LC_ALL to default locale: No such file or
>>directory
>>>
>>> You have a broken locale setup, there is nothing we can do. luatex
>>needs
>>> correctly setup locales, but they are not.
>>
>>But the installation of tex-common should not fail because of this. It
>>works fine when LC_TIME is not set to C or en_US.UTF-8 and so on
>>(everything which locales-all provides).
>>
>>If the installation of a package fails because a user set locale is
>>wrong then something is terrible broken with your installation
>>process. I understand that it may fail when the user calls luatex
>>manually with some incorrect env but not when the installation process
>>is run.
>>
>>Setup/Installation happens in the system context. But now you are
>>telling me that something in the user context is allowed to break the
>>installation. Nothing in the users env should change the way how the
>>package installation process behaves. We have /etc for that - not the
>>user specific env.
>>
>>What would you say when you swedish system administrator installs
>>package xyz and suddenly all english-only speaking users of the system
>>have to deal with a swedish-only installation of xyz - even when the
>>swedish system admin never explicitly said that a swedish-only version
>>should be installed? Sounds wrong, correct?
>>
>>It is a little bit like farting in the face of the reproducible build
>>folks. Cool, we removed all the non-reproducible behavior in the build
>>process - lets move all the reproducibility problems in the
>>installation process.
>>
>>Maybe the package is assigned incorrectly in this ticket and
>>dpkg/aptitude/... should sanitize the env. But the ticket should not
>>be closed so easily.
>>
>>It is not like I sat down and broke the package on purpose. I just
>>selected some good looking regional settings in KDE plasma. And
>>suddenly my texlive installation doesn't work anymore. Not something
>>which you would expect.
>
>
>--
>PREINING Norbert http://www.preining.info
>Accelia Inc. + JAIST + TeX Live + Debian Developer
>GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13


--
PREINING Norbert http://www.preining.info
Accelia Inc. + JAIST + TeX Live + Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable

[Timo Sigurdsson]

Hi,

I've also been hit by this bug on two systems (both are Lemaker Bananapi). The 
first system upgraded the kernel via unattended-upgrades and failed to come up 
after reboot. I don't have a serial cable, but I did hook up the board to a 
HDMI display. U-Boot loads the kernel, dtb and initramfs and starts the kernel 
but that's the last message and nothing happens after that anymore. My first 
suspicion was that something went wrong during the upgrade and the reboot might 
have happened before everything was configured. But I also tried manual package 
upgrade with a second device via apt update && apt full-upgrade followed by a 
manual reboot. That system didn't boot either.

I recovered both systems by replacing the contents of the directories /boot/ 
and /lib/modules/ with those of a recent backup (taken 3 days ago). After 
logging into the systems again, I downgraded the package 
linux-image-4.9.0-8-armmp-lpae to 4.9.130-2 and rebooted again in order to make 
sure no other package upgrade caused the issue. Indeed, with all packages 
up-to-date except linux-image-4.9.0-8-armmp-lpae, the systems work just fine.

So, there must be a serious regression in 4.9.144-3 at least on armmp-lpae. My 
amd64 systems run fine, btw, even with the latest kernel.


Thanks,

Timo

Bug#913576: Update

[bkw+1542031175]

Hi Mattia,

Unfortunately, I haven't heard anything from the Debian developers 
regarding this error.  However, this morning, with adequate time and 
careful preparation, I decided to perform a reboot on this server.  I'm 
very happy to report that the server booted successfully.  So, it 
appears that the generated EFI images functioned successfully.


I don't know what this means, for the error I encountered which led to 
me reporting this bug.  But it appears that the error was either a false 
alarm, or it was not a critical error.


Regardless, a reboot was successful.

Thanks.

Processed: tagging 922507

[Debian Bug Tracking System]

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

> tags 922507 + pending
Bug #922507 [wml] wml: Missing depends on libgd-perl
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#921790: liquidsoap: FTBFS (ld: cannot find -lexif)

[Kyle Robbertze]

Hi,

On 2019/02/17 11:52, Andrey Rahmatullin wrote:
> On Sat, Feb 09, 2019 at 12:15:34AM +, Santiago Vila wrote:
>> OCAMLOPT -o liquidsoap
>> /usr/bin/ld: cannot find -lexif
> libexif-dev is indeed not installed but my build fails even earlier:
> 
> OCAMLOPT -c tools/file_watcher.ml
> OCAMLOPT -c tools/file_watcher_mtime.ml
> OCAMLOPT -c configure.mli
> OCAMLOPT -c configure.ml
> File "configure.ml", line 25, characters 11-32:
> Error: Unbound module Camomile
> make[4]: *** [../Makefile.rules:193: configure.cmx] Error 2
> make[4]: Leaving directory '/<>/src'

This is because version 1.0.1 of Camomile is in unstable. I am busy
packaging liquidsoap 1.3.4, which is compatible with newer versions of
Camomile and will fix both these issues.

Cheers
Kyle

Bug#919028: marked as done (chrome-gnome-shell: postinst fails on reconfigure or if json already exists)

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 14:45:29 +
with message-id 
and subject line Bug#919028: fixed in chrome-gnome-shell 10.1-5
has caused the Debian Bug report #919028,
regarding chrome-gnome-shell: postinst fails on reconfigure or if json already 
exists
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.)


-- 
919028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chrome-gnome-shell
Version: 10.1-4
Severity: normal
Tags: patch

Dear Maintainer,

The postinst script fails if

  /etc/opt/chrome/native-messaging-hosts/org.gnome.chrome_gnome_shell.json

already exists on the system at the time of install. I've been able to
reproduce this two different ways so far:

1. I manually copied the file before upgrading to 10.1-4. The postinst
   attempted to symlink on top of an existing regular file and failed.

2. I ran `dpkg-reconfigure chrome-gnome-shell` after successful install.
   The postinst attempted to symlink on top an an already existing
   symlink that it had created when it was first installed.

There are probably several different ways you could address this, I'm
attaching a suggestion that works for me. In general I would think if
the destination already exists as a file or a symlink, you should avoid
trying to overwrite it at all.

Thanks!


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

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

Versions of packages chrome-gnome-shell depends on:
ii  gnome-shell   3.30.1-2
ii  python3   3.7.1-3
ii  python3-gi3.30.4-1
ii  python3-requests  2.20.0-2

chrome-gnome-shell recommends no packages.

Versions of packages chrome-gnome-shell suggests:
ii  chromium  72.0.3626.7-4
pn  firefox   

-- no debconf information
>From d8be8ae955cf79d0835b40718476561e97d79a9f Mon Sep 17 00:00:00 2001
From: Mike Miller 
Date: Fri, 11 Jan 2019 15:53:55 -0800
Subject: [PATCH] Avoid failing install on link in /etc/opt/chrome

---
 debian/postinst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/debian/postinst b/debian/postinst
index 703dfacc44a7..af0cada8695a 100644
--- a/debian/postinst
+++ b/debian/postinst
@@ -5,6 +5,8 @@ set -e
 #DEBHELPER#
 
 mkdir -p /etc/opt/chrome/native-messaging-hosts
-ln -s /usr/share/chrome-gnome-shell/org.gnome.chrome_gnome_shell.json 
/etc/opt/chrome/native-messaging-hosts/
+if [ ! -e 
/etc/opt/chrome/native-messaging-hosts/org.gnome.chrome_gnome_shell.json ]; then
+  ln -sf /usr/share/chrome-gnome-shell/org.gnome.chrome_gnome_shell.json 
/etc/opt/chrome/native-messaging-hosts/
+fi
 
 exit 0
-- 
2.20.1

--- End Message ---
--- Begin Message ---
Source: chrome-gnome-shell
Source-Version: 10.1-5

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated chrome-gnome-shell 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 17 Feb 2019 13:48:08 +
Source: chrome-gnome-shell
Architecture: source
Version: 10.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 919028
Changes:
 chrome-gnome-shell (10.1-5) unstable; urgency=medium
 .
   * Team upload
   * Avoid failure to install or reconfigure when
 /etc/opt/chrome/native-messaging-hosts/org.gnome.chrome_gnome_shell.json
 already exists. Thanks to Mike Miller. (Closes: #919028)
   * Remove /etc/opt/chrome/native-messaging-hosts during purge, avoiding
 leftover directories during remove-then-purge (thanks, piuparts)
Checksums-Sha1:
 

Bug#922500: tex-common: Fails to install with LC_TIME=en_DE.UTF-8

[Norbert Preining]

You set the locale for root while installing, this has nothing to do with user 
settings what so ever. If you remove bash and a different program fails to 
install, do you think this is an error of the program bring installed?

If locales are not properly set up, then luatex fails to build a format, this 
is independent from the Debian packaging.

Anyway, you reopened the bug, so let's enjoy it.

Best

Norbert

On February 17, 2019 1:06:08 PM GMT+01:00, Charlemagne Lasse 
 wrote:
>> On Sun, 17 Feb 2019, Charlemagne Lasse wrote:
>> > perl: warning: Setting locale failed.
>> > perl: warning: Please check that your locale settings:
>> > LANGUAGE = "en_US:en",
>> > LC_ALL = (unset),
>> > LC_TIME = "en_DE.UTF-8",
>> > LANG = "C"
>> > are supported and installed on your system.
>>
>> > locale: Cannot set LC_ALL to default locale: No such file or
>directory
>>
>> You have a broken locale setup, there is nothing we can do. luatex
>needs
>> correctly setup locales, but they are not.
>
>But the installation of tex-common should not fail because of this. It
>works fine when LC_TIME is not set to C or en_US.UTF-8 and so on
>(everything which locales-all provides).
>
>If the installation of a package fails because a user set locale is
>wrong then something is terrible broken with your installation
>process. I understand that it may fail when the user calls luatex
>manually with some incorrect env but not when the installation process
>is run.
>
>Setup/Installation happens in the system context. But now you are
>telling me that something in the user context is allowed to break the
>installation. Nothing in the users env should change the way how the
>package installation process behaves. We have /etc for that - not the
>user specific env.
>
>What would you say when you swedish system administrator installs
>package xyz and suddenly all english-only speaking users of the system
>have to deal with a swedish-only installation of xyz - even when the
>swedish system admin never explicitly said that a swedish-only version
>should be installed? Sounds wrong, correct?
>
>It is a little bit like farting in the face of the reproducible build
>folks. Cool, we removed all the non-reproducible behavior in the build
>process - lets move all the reproducibility problems in the
>installation process.
>
>Maybe the package is assigned incorrectly in this ticket and
>dpkg/aptitude/... should sanitize the env. But the ticket should not
>be closed so easily.
>
>It is not like I sat down and broke the package on purpose. I just
>selected some good looking regional settings in KDE plasma. And
>suddenly my texlive installation doesn't work anymore. Not something
>which you would expect.


--
PREINING Norbert http://www.preining.info
Accelia Inc. + JAIST + TeX Live + Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Processed: Re: Bug#922507: wml: Missing depends on libgd-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed
Bug #922507 [wml] wml: Missing depends on libgd-perl
Added tag(s) confirmed.

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

Bug#922507: wml: Missing depends on libgd-perl

[Axel Beckert]

Control: tag -1 + confirmed

Hi Kurt,

thanks for the bug report!

Kurt Roeckx wrote:
> I'm getting the following error:
> Can't locate GD.pm in @INC (you may need to install the GD module) (@INC 
> contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 
> /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 
> /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
> /usr/local/lib/site_perl) at /tmp/wml.28518.tmp1 line 197.
> BEGIN failed--compilation aborted at /tmp/wml.28518.tmp1 line 197.

This seems to come from using wml::des::imgbg:

/usr/share/wml/include/des/imgbg.wml:use GD;
/usr/share/wml/include/des/imgbg.wml:$im = GD::Image->new($size, 
$pixels);
/usr/share/wml/include/des/imgbg.wml:$im = GD::Image->new($pixels, 
$size);
/usr/share/wml/include/des/imgdot.wml:use GD;
/usr/share/wml/include/des/imgdot.wml:$im = GD::Image->new($x, $y);

So, indeed, there's a missing package relation.

> It seems that this was part of wml in older versions, but not in
> the current version.

Indeed. Previously there (i.e. in Stretch), there was a dependency on
libgd3 directly, because wml::des::imgbg used WML::GD which was a very
thin XS wrapper around the C library GD. That wrapper is gone now and
I missed the fact that it didn't just vanish but has been replaced
with calls to the existing perl module GD.

Will upload a fix shortly.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#920997: marked as done (slurm-llnl: CVE-2019-6438)

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 13:05:28 +
with message-id 
and subject line Bug#920997: fixed in slurm-llnl 18.08.5.2-1
has caused the Debian Bug report #920997,
regarding slurm-llnl: CVE-2019-6438
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.)


-- 
920997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slurm-llnl
Version: 18.08.3-1
Severity: grave
Tags: security upstream
Control: found -1 16.05.9-1+deb9u2
Control: found -1 16.05.9-1

Hi,

The following vulnerability was published for slurm-llnl.

CVE-2019-6438[0]:
| SchedMD Slurm before 17.11.13 and 18.x before 18.08.5 mishandles 32-bit
| systems.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-6438
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6438
[1] https://lists.schedmd.com/pipermail/slurm-announce/2019/18.html
[2] https://lists.schedmd.com/pipermail/slurm-announce/2019/19.html
[3] https://www.schedmd.com/news.php?id=213

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: slurm-llnl
Source-Version: 18.08.5.2-1

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

Debian distribution maintenance software
pp.
Gennaro Oliva  (supplier of updated slurm-llnl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Feb 2019 13:32:52 +0100
Source: slurm-llnl
Binary: libpam-slurm libpmi0 libpmi0-dbgsym libpmi0-dev libpmi2-0 
libpmi2-0-dbgsym libpmi2-0-dev libslurm-dev libslurm-perl libslurm33 
libslurm33-dbgsym libslurmdb-dev libslurmdb-perl libslurmdb33 
libslurmdb33-dbgsym slurm-client slurm-client-dbgsym slurm-client-emulator 
slurm-wlm slurm-wlm-basic-plugins slurm-wlm-basic-plugins-dbgsym 
slurm-wlm-basic-plugins-dev slurm-wlm-doc slurm-wlm-emulator slurm-wlm-torque 
slurmctld slurmctld-dbgsym slurmd slurmd-dbgsym slurmdbd slurmdbd-dbgsym sview
Architecture: source amd64 all
Version: 18.08.5.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Gennaro Oliva 
Description:
 libpam-slurm - PAM module to authenticate using the SLURM resource manager
 libpmi0- SLURM PMI library implementation
 libpmi0-dev - SLURM PMI library implementation development files
 libpmi2-0  - SLURM PMI2 library implementation
 libpmi2-0-dev - SLURM PMI2 library implementation development files
 libslurm-dev - SLURM development files
 libslurm-perl - Perl API for SLURM
 libslurm33 - Runtime library files for SLURM
 libslurmdb-dev - SLURM DataBase Daemon development files
 libslurmdb-perl - Perl API for the SLURM database
 libslurmdb33 - Runtime library files for the SLURM DataBase Daemon
 slurm-client - SLURM client side commands
 slurm-client-emulator - SLURM client side commands for the emulator
 slurm-wlm  - Simple Linux Utility for Resource Management
 slurm-wlm-basic-plugins - SLURM basic plugins
 slurm-wlm-basic-plugins-dev - SLURM basic plugins development files
 slurm-wlm-doc - SLURM documentation
 slurm-wlm-emulator - SLURM emulator
 slurm-wlm-torque - Torque compatibility wrappers for SLURM
 slurmctld  - SLURM central management daemon
 slurmd - SLURM compute node daemon
 slurmdbd   - Secure enterprise-wide interface to a database for SLURM
 sview  - GUI to view and modify SLURM state
Closes: 850891 851103 885759 920997
Changes:
 slurm-llnl (18.08.5.2-1) unstable; urgency=medium
 .
   * New upstream release fixes CVE-2019-6438 (Closes: #920997)
   * debian/patches/man-pages-typos: removed, applied upstream
   * Add Build-Depends-Package field to symbol files
   * Handling slurm user inside the plugin package as suggested by
 Karl Kornel (Closes: #850891)
   * Allow using a slurm user with a different UID if created before
 installation (Closes: #851103)
   * Move pid files under 

Processed: severity of 922478 is serious

[Debian Bug Tracking System]

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

> severity 922478 serious
Bug #922478 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 
4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#877202: marked as done (pyxdg FTBFS and Debci failure: ERROR: test_validate_icon_theme (test-icon.IconThemeTest))

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 12:34:27 +
with message-id 
and subject line Bug#877202: fixed in pyxdg 0.25-5
has caused the Debian Bug report #877202,
regarding pyxdg FTBFS and Debci failure: ERROR: test_validate_icon_theme 
(test-icon.IconThemeTest)
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.)


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

Some recent change in unstable makes pyxdg FTBFS and Debci fail:

https://ci.debian.net/packages/p/pyxdg/unstable/amd64/
https://tests.reproducible-builds.org/debian/history/pyxdg.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyxdg.html

...
==
ERROR: test_validate_icon_theme (test-icon.IconThemeTest)
--
Traceback (most recent call last):
  File "/build/1st/pyxdg-0.25/test/test-icon.py", line 20, in 
test_validate_icon_theme
theme.validate()
  File "/build/1st/pyxdg-0.25/xdg/IniFile.py", line 243, in validate
raise ValidationError(msg, self.filename)
ValidationError: ValidationError in file 
'/usr/share/icons/hicolor/index.theme': 
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: Scale
- Invalid key: 

Processed: reopen 922500

[Debian Bug Tracking System]

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

> reopen 922500
Bug #922500 {Done: Norbert Preining } [tex-common] 
tex-common: Fails to install with LC_TIME=en_DE.UTF-8
Bug reopened
Ignoring request to alter fixed versions of bug #922500 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Bug #877202 in pyxdg marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #877202 [src:pyxdg] pyxdg FTBFS and Debci failure: ERROR: 
test_validate_icon_theme (test-icon.IconThemeTest)
Ignoring request to alter tags of bug #877202 to the same tags previously set

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

Bug#877202: Bug #877202 in pyxdg marked as pending

[Simon McVittie]

On Thu, 14 Feb 2019 at 11:02:33 +, Simon McVittie wrote:
> Alternatively, uploading a version closely resembling the one in Ubuntu
> would be a low-risk option with a minimal fix for this bug.

For now I've done this, on a new debian/buster branch, and merged that
branch into master.

smcv

Bug#877202: Bug #877202 in pyxdg marked as pending

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #877202 in pyxdg 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/modules/pyxdg/commit/c64dc17fe601cf515ac95897fd3937c1a59a7aac


Add patches from upstream to support Scale, ScaledDirectories in icon themes

Closes: #877202
LP: #1766793


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/877202

Processed: Bug #877202 in pyxdg marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #877202 [src:pyxdg] pyxdg FTBFS and Debci failure: ERROR: 
test_validate_icon_theme (test-icon.IconThemeTest)
Ignoring request to alter tags of bug #877202 to the same tags previously set

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

Bug#877202: Bug #877202 in pyxdg marked as pending

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #877202 in pyxdg 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/modules/pyxdg/commit/c64dc17fe601cf515ac95897fd3937c1a59a7aac


Add patches from upstream to support Scale, ScaledDirectories in icon themes

Closes: #877202
LP: #1766793


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/877202

Processed: reassign 922488 to src:linux

[Debian Bug Tracking System]

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

> reassign 922488 src:linux 4.9.144-3
Bug #922488 [linux-image-4.9.0-8-amd64] linux-image-4.9.0-8-amd64: Kernel panic 
in IPv6 stack after some hours of operation
Bug reassigned from package 'linux-image-4.9.0-8-amd64' to 'src:linux'.
No longer marked as found in versions linux/4.9.144-3.
Ignoring request to alter fixed versions of bug #922488 to the same values 
previously set
Bug #922488 [src:linux] linux-image-4.9.0-8-amd64: Kernel panic in IPv6 stack 
after some hours of operation
Marked as found in versions linux/4.9.144-3.
> thanks
Stopping processing here.

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

Bug#922513: capstone: Block from entering testing

[Hilko Bengen]

Source: capstone
Version: 3.0.5-4
Severity: grave

I recently uploaded the capstone4 as a separate source package, assuming
that this would not have consequences in testing. As I was told on
#debian-release, that is not the case because the capstone4 package
takes over python-capstone, python3-capstone, capstone-tool and a
subsequent capstone migration to testing would cause removal of those
binary packages from testing.

This bug is intended to prevent such a migration.

Bug#922500: tex-common: Fails to install with LC_TIME=en_DE.UTF-8

[Charlemagne Lasse]

> On Sun, 17 Feb 2019, Charlemagne Lasse wrote:
> > perl: warning: Setting locale failed.
> > perl: warning: Please check that your locale settings:
> > LANGUAGE = "en_US:en",
> > LC_ALL = (unset),
> > LC_TIME = "en_DE.UTF-8",
> > LANG = "C"
> > are supported and installed on your system.
>
> > locale: Cannot set LC_ALL to default locale: No such file or directory
>
> You have a broken locale setup, there is nothing we can do. luatex needs
> correctly setup locales, but they are not.

But the installation of tex-common should not fail because of this. It
works fine when LC_TIME is not set to C or en_US.UTF-8 and so on
(everything which locales-all provides).

If the installation of a package fails because a user set locale is
wrong then something is terrible broken with your installation
process. I understand that it may fail when the user calls luatex
manually with some incorrect env but not when the installation process
is run.

Setup/Installation happens in the system context. But now you are
telling me that something in the user context is allowed to break the
installation. Nothing in the users env should change the way how the
package installation process behaves. We have /etc for that - not the
user specific env.

What would you say when you swedish system administrator installs
package xyz and suddenly all english-only speaking users of the system
have to deal with a swedish-only installation of xyz - even when the
swedish system admin never explicitly said that a swedish-only version
should be installed? Sounds wrong, correct?

It is a little bit like farting in the face of the reproducible build
folks. Cool, we removed all the non-reproducible behavior in the build
process - lets move all the reproducibility problems in the
installation process.

Maybe the package is assigned incorrectly in this ticket and
dpkg/aptitude/... should sanitize the env. But the ticket should not
be closed so easily.

It is not like I sat down and broke the package on purpose. I just
selected some good looking regional settings in KDE plasma. And
suddenly my texlive installation doesn't work anymore. Not something
which you would expect.

Processed: closing 922509

[Debian Bug Tracking System]

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

> close 922509 1.4.2-1
Bug #922509 [src:slixmpp] security issue in PEP plugin (CVE-2019-121)
Marked as fixed in versions slixmpp/1.4.2-1.
Bug #922509 [src:slixmpp] security issue in PEP plugin (CVE-2019-121)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#922509: closing 922509

[Salvatore Bonaccorso]

close 922509 1.4.2-1
thanks

Bug#922502: plasma-desktop: regional settings allow do select system incompatible locales

[Charlemagne Lasse]

See also https://bugs.debian.org/922500

Processed: Forgot to Cc control

[Debian Bug Tracking System]

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

> retitle 921803 python-scrapy: FTBFS randomly (failing tests)
Bug #921803 [src:python-scrapy] python-scrapy: FTBFS (failing tests)
Changed Bug title to 'python-scrapy: FTBFS randomly (failing tests)' from 
'python-scrapy: FTBFS (failing tests)'.
> severity 921803 important
Bug #921803 [src:python-scrapy] python-scrapy: FTBFS randomly (failing tests)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#921803: python-scrapy: FTBFS randomly (failing tests)

[Santiago Vila]

retitle 921803 python-scrapy: FTBFS randomly (failing tests)
severity 921803 important
thanks

On Sun, Feb 17, 2019 at 02:37:42PM +0500, Andrey Rahmatullin wrote:
> I cannot reproduce this on the current sid chroot.
> Unfortunately the log excerpt in the bug is not helpful and I couldn't
> access the RB website.

Sorry, I initially believed this was an "always-FTBFS bug" but I was wrong.

The failure is really random, so to reproduce you will have to try
several times. I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/python-scrapy/

Please contact me privately and I will try to give you access
to a machine where this failure (randomly) happens, so that
you can reproduce it as well.

Thanks.

Bug#922509: security issue in PEP plugin (CVE-2019-1000021)

[W. Martin Borgert]

Source: slixmpp
Version: 1.2.2-1.1
Severity: grave
Tags: security patch upstream

See
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-121
for details. A fixed version for stretch-security is on its way.

Bug#922500: marked as done (tex-common: Fails to install with LC_TIME=en_DE.UTF-8)

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 20:04:44 +0900
with message-id <20190217110444.ga8...@burischnitzel.preining.info>
and subject line Re: Bug#922500: tex-common: Fails to install with 
LC_TIME=en_DE.UTF-8
has caused the Debian Bug report #922500,
regarding tex-common: Fails to install with LC_TIME=en_DE.UTF-8
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.)


-- 
922500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tex-common
Version: 6.10
Severity: serious
Justification: Fails to install on a normal KDE installation with
"Germany" setting as Time localization

The installation works fine with LC_TIME=C but not with the setting
generated by KDE LC_TIME=en_DE.UTF-8. The aptitude output follows and
at the end the log file content mentioned in the aptitude output

sudo LC_TIME=en_DE.UTF-8 aptitude reinstall tex-common
Warning: Invalid locale (please review locale settings, this might
lead to problems later):
  locale::facet::_S_create_c_locale name not valid
The following packages will be REINSTALLED:
  tex-common
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and
33 not upgraded.
Need to get 53.0 kB of archives. After unpacking 0 B will be used.
Get: 1 http://ftp.de.debian.org/debian buster/main amd64 tex-common
all 6.10 [53.0 kB]
Fetched 53.0 kB in 1s (105 kB/s)
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
apt-listchanges: Can't set locale; make sure $LC_* and $LANG are correct!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "de_DE.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("de_DE.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory
(Reading database ... 21 files and directories currently installed.)
Preparing to unpack .../tex-common_6.10_all.deb ...
Unpacking tex-common (6.10) over (6.10) ...
Setting up tex-common (6.10) ...
locale: Cannot set LC_ALL to default locale: No such file or directory
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.kwturaob
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess
returned error exit status 1
Processing triggers for man-db (2.8.5-1) ...
Errors were encountered while processing:
 tex-common
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
E: Sub-process /usr/bin/dpkg returned an 

Bug#922507: wml: Missing depends on libgd-perl

[Kurt Roeckx]

Package: wml
Version: 2.12.2~ds1-1
Severity: serious

Hi,

I'm getting the following error:
Can't locate GD.pm in @INC (you may need to install the GD module) (@INC 
contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 
/usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl) at /tmp/wml.28518.tmp1 line 197.
BEGIN failed--compilation aborted at /tmp/wml.28518.tmp1 line 197.

It seems that this was part of wml in older versions, but not in
the current version.


Kurt

Bug#922489: marked as done (qtkeychain: relies on existence of libsecret-1.so -dev symlink)

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 10:51:53 +
with message-id 
and subject line Bug#922489: fixed in qtkeychain 0.9.1-2
has caused the Debian Bug report #922489,
regarding qtkeychain: relies on existence of libsecret-1.so -dev symlink
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.)


-- 
922489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsecret-1-0
Version: 0.18.7-1
Severity: normal

Hey,

qtkeychain is using libsecret as a backend to request passwords. ldd is
showing me that it is linked against libsecret-1.so.0 (fine). But strace
shows one sucessfull read of libsecret-1.so.0 (fine) but afterwards, it
tries to load libsecret-1.so without success (as libsecret-1-dev is not
installed). If I create this symlink from libsecret-1.so ->
libsecret-1.so, qtkeychain can load/store successfully passwords.

For me this looks like an error in libsecret, as qtkeychain only imports
libsecret/secret.h in libsecret.cpp [0]. Or maybe the usage in that file
is wrong or cmake screws things up...

My testsystem is a vagrant with a VirtualBox with only task-xfce-desktop and
nextcloud-desktop installed. I enabled to load GNOME startup scripts for
the XFCE environment.

hefee

[0] https://sources.debian.org/src/qtkeychain/0.9.1-1/libsecret.cpp/

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

Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libsecret-1-0 depends on:
ii  libc6 2.28-7
ii  libgcrypt20   1.8.4-5
ii  libglib2.0-0  2.58.3-1
ii  libsecret-common  0.18.7-1

libsecret-1-0 recommends no packages.

libsecret-1-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qtkeychain
Source-Version: 0.9.1-2

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

Debian distribution maintenance software
pp.
Sandro Knauß  (supplier of updated qtkeychain package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Feb 2019 11:15:10 +0100
Source: qtkeychain
Architecture: source
Version: 0.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: ownCloud for Debian maintainers 

Changed-By: Sandro Knauß 
Closes: 920984 922489
Changes:
 qtkeychain (0.9.1-2) unstable; urgency=medium
 .
   * Add commit to load versioned libsecret (Closes: #920984, #922489)
Checksums-Sha1:
 b34e42b8d07e97a3a15b545ef96876501a45baad 2142 qtkeychain_0.9.1-2.dsc
 011e700dedd9f12c95b47d894c31134c3107e282 7892 qtkeychain_0.9.1-2.debian.tar.xz
 119885306afdabdff6410a7685242c7650fb30b9 13693 
qtkeychain_0.9.1-2_source.buildinfo
Checksums-Sha256:
 f0d87f3bc5154307a56307c954d1725f2dc8a15d94b22b01ff55127671615f7d 2142 
qtkeychain_0.9.1-2.dsc
 b1493d9e1c8db7612ea13fa50fa91f613e848eb6b0c8df5f3a329a02828b2203 7892 
qtkeychain_0.9.1-2.debian.tar.xz
 7518233590037272bfdd47bba6a2ce9116a47ad5335138e3eef0d854c69e2ef7 13693 
qtkeychain_0.9.1-2_source.buildinfo
Files:
 785d4bbfd957775cc78b25a7cd88b726 2142 libs optional qtkeychain_0.9.1-2.dsc
 8badb872a2fc5cfc44671e3b4767b49e 7892 libs optional 
qtkeychain_0.9.1-2.debian.tar.xz
 4256bb76b027b9f0a9774dac5765d58d 13693 libs optional 
qtkeychain_0.9.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEOewRoCAWtykmSRoG462wCFBgVjYFAlxpOYoRHGhlZmVlQGRl
Ymlhbi5vcmcACgkQ462wCFBgVjZF6w/9FaJlkTK4tDhvvK7CZfsLir0gupXDi/Zi
BI1UESZGP2qW8jlWKsE5C+AQY3qMZakC0XsvR6B6RNvoi16N8LHLTptshKFHnT/6
NBiaDGNnPmiLoz7vQaxySkTeY1FD+fX/FpCAEi4Q+MGDfYuT/HXEWVRmaisdBx1h

Bug#922503: closed by Samuel Thibault (Re: Bug#922503: espeakup 0.80+deb9u3 is damaged)

[Samuel Thibault]

Hello,

Fran Torres, le dim. 17 févr. 2019 11:15:43 +0100, a ecrit:
> on the espeakup package was disapear the error on log
> and apear other error.

I believe that's just a deprecation warning.

Samuel

Processed: Re: Bug#922489: qtkeychain: relies on existence of libsecret-1.so -dev symlink

[Debian Bug Tracking System]

Processing control commands:

> Forwarded -1 https://github.com/frankosterfeld/qtkeychain/pull/139
Bug #922489 [qtkeychain] qtkeychain: relies on existence of libsecret-1.so -dev 
symlink
Set Bug forwarded-to-address to 
'https://github.com/frankosterfeld/qtkeychain/pull/139'.

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

Bug#922489: qtkeychain: relies on existence of libsecret-1.so -dev symlink

[Sandro Knauß]

Control: Forwarded -1 https://github.com/frankosterfeld/qtkeychain/pull/139

Hey,

thanks for the fast reply, that gave me the right direction to search for the 
bugfix.

> I think this is a qtkeychain bug. This code that appears to be responsible
> for dlopen()ing libsecret:
> 
> LibSecretKeyring::LibSecretKeyring()
> 
> : QLibrary("secret-1")
> 
> doesn't mention the ABI version, so it could equally easily end up loading
> an incompatible future library libsecret-1.so.1 or libsecret-1.so.27,
> and then crashing when it calls a function by assuming that it has the
> same ABI as the corresponding function in libsecret-1.so.0.

This was the bug, that there is no version added to QLibrary. Actually all 
other libraries have a abiversion defined. I added a patch upstream to fix this.

> I haven't programmed against Qt for years, but the documentation
> suggest that it should probably inherit from QLibrary("secret-1", 0)
> as described at ,
> so that Qt will specifically load libsecret-1.so.0 on Unix platforms.

Interestingly that noone stumbled over this bug before...

hefee

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

Processed (with 1 error): merging 910056 920458

[Debian Bug Tracking System]

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

> merge 910056 920458
Bug #910056 {Done: Mattia Rizzolo } [src:twisted] twisted: 
Missing version constraint on python-attr dependencies
Unable to merge bugs because:
done of #920458 is '' not 'Mattia Rizzolo '
package of #920458 is 'python3-twisted' not 'src:twisted'
Failed to merge 910056: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#922503: closed by Samuel Thibault (Re: Bug#922503: espeakup 0.80+deb9u3 is damaged)

[Fran Torres]

Hello,

after add the /bin/ before sh -c, the dpkg was configured the rest of
packages but, on the espeakup package was disapear the error on log
and apear other error. In this case, i'm not capable found the
problem. I add you a log (syslog, espeakup.service and output of apt)
in a unique log for can solve

Fran.
PD: the log are atached in another message

2019-02-17 10:39 GMT+01:00, Debian Bug Tracking System :
> This is an automatic notification regarding your Bug report
> which was filed against the espeakup package:
>
> #922503: espeakup 0.80+deb9u3 is damaged
>
> It has been closed by Samuel Thibault .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Samuel Thibault
>  by
> replying to this email.
>
>
> --
> 922503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922503
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#919802: marked as done (libjstun-java: FTBFS (The code being documented uses packages in the unnamed module))

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 10:04:29 +
with message-id 
and subject line Bug#919802: fixed in libjstun-java 0.7.3+dfsg-2
has caused the Debian Bug report #919802,
regarding libjstun-java: FTBFS (The code being documented uses packages in the 
unnamed module)
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.)


-- 
919802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libjstun-java
Version: 0.7.3+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   jh_linkjars -i
   jh_build -i
find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
 -d debian/_jh_build.libjstun-java -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 7
Note: src/de/javawi/jstun/test/demo/ice/ICENegociator.java uses unchecked or 
unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 warning
find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
/usr/share/doc/default-jdk-doc/api -link 
/usr/share/doc/default-jre-headless/api -classpath 
/usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
 -d debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp 
-source 1.7
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
2 errors
make: *** [debian/rules:11: build-indep] Error 123
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the builds ends and not necessarily the most relevant 
part)

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

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

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

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 ---
Source: libjstun-java
Source-Version: 0.7.3+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated libjstun-java 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Feb 2019 15:42:02 +0800
Source: libjstun-java
Binary: libjstun-java libjstun-java-doc
Architecture: source
Version: 0.7.3+dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 libjstun-java - Java-based STUN implementation
 libjstun-java-doc - Java-based STUN implementation (documentation)
Closes: 919802
Changes:
 libjstun-java (0.7.3+dfsg-2) unstable; urgency=low
 .
   * Remove Build-Depends-Indep on default-jdk-doc. (Closes: #919802)
 - This bug is not caused by this package. However we need to fix this bug
   to avoid AUTORM. We should add default-jdk-doc back to
   Build-Depends-Indep later when the bug is properly fixed in other place.
Checksums-Sha1:
 

Bug#921790: liquidsoap: FTBFS (ld: cannot find -lexif)

[Andrey Rahmatullin]

On Sat, Feb 09, 2019 at 12:15:34AM +, Santiago Vila wrote:
> OCAMLOPT -o liquidsoap
> /usr/bin/ld: cannot find -lexif
libexif-dev is indeed not installed but my build fails even earlier:

OCAMLOPT -c tools/file_watcher.ml
OCAMLOPT -c tools/file_watcher_mtime.ml
OCAMLOPT -c configure.mli
OCAMLOPT -c configure.ml
File "configure.ml", line 25, characters 11-32:
Error: Unbound module Camomile
make[4]: *** [../Makefile.rules:193: configure.cmx] Error 2
make[4]: Leaving directory '/<>/src'


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#915298: gdebi FTBFS with pyflakes 2.0.0-1

[Andrey Rahmatullin]

Here is the actual pyflakes3 output:

./gdebi-kde:92: local variable 'e' is assigned to but never used
./gdebi-gtk:80: local variable 'e' is assigned to but never used
./GDebi/KDEAptDialogs.py:147: local variable 'e' is assigned to but never used
./GDebi/GDebiKDE.py:363: local variable 'msg' is assigned to but never used
./GDebi/GDebiGtk.py:69: local variable 'e' is assigned to but never used
gdebi-gtk:80: local variable 'e' is assigned to but never used
gdebi-kde:92: local variable 'e' is assigned to but never used

I don't think aborting on non-empty pyflakes output, just like compiling
with -Werror, should be a part of a Debian package build.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#922504: socket-activate: FTBFS in sid (failing tests)

[Santiago Vila]

Package: src:socket-activate
Version: 0.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
pandoc -s -t man -o socket-activate.1 socket-activate.md
make[1]: Leaving directory '/<>'
   dh_auto_test -i
make -j1 check
make[1]: Entering directory '/<>'
SOCKET_ACTIVATE=/<>/socket-activate ./tests/basic
env: '/<>/socket-activate': No such file or directory
2019/02/17 09:32:10 socat[13787] E connect(5, AF=1 
"/<>/tests/sock", 62): No such file or directory
make[1]: *** [Makefile:14: check] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check returned exit code 2
make: *** [debian/rules:4: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A" and it fails 
every time.

I'm using sbuild + schroot. If for whatever reason you could not reproduce 
this, please
contact me privately and I will gladly offer ssh access to a test machine where 
this
happens all the time.

Thanks.

Processed: unarchiving 910056

[Debian Bug Tracking System]

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

> unarchive 910056
Bug #910056 {Done: Mattia Rizzolo } [src:twisted] twisted: 
Missing version constraint on python-attr dependencies
Unarchived Bug 910056
> thanks
Stopping processing here.

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

Bug#921803: python-scrapy: FTBFS (failing tests)

[Andrey Rahmatullin]

I cannot reproduce this on the current sid chroot.
Unfortunately the log excerpt in the bug is not helpful and I couldn't
access the RB website.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Processed: tagging 912183

[Debian Bug Tracking System]

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

> tags 912183 - moreinfo
Bug #912183 [src:python-cookies] python-cookies FTBFS with python 3.7 as 
supported version
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#922383: marked as done (nbd: FTBFS in sid (docbook2man: command not found))

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 09:04:25 +
with message-id 
and subject line Bug#922383: fixed in nbd 1:3.19-3
has caused the Debian Bug report #922383,
regarding nbd: FTBFS in sid (docbook2man: command not found)
to be marked as done.

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

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


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

Hello Wouter.

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


[...]

Making all in man
make[3]: Entering directory '/<>/man'
sh nbd-server.1.sh > nbd-server.1
sh nbd-server.5.sh > nbd-server.5
sh nbd-client.8.sh > nbd-client.8
sh nbd-trdump.1.sh > nbd-trdump.1
LC_ALL=C docbook2man nbdtab.5.in.sgml
/bin/bash: docbook2man: command not found
make[3]: *** [Makefile:677: nbdtab.5.sh.in] Error 127
make[3]: Leaving directory '/<>/man'
make[2]: *** [Makefile:837: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:481: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:8: 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"
and it also fails here:

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

[ Please consider uploading in source-only form (dpkg-buildpackage -S). It 
should work
  as far as there is no NEW processing ].

Thanks.
--- End Message ---
--- Begin Message ---
Source: nbd
Source-Version: 1:3.19-3

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

Debian distribution maintenance software
pp.
Wouter Verhelst  (supplier of updated nbd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 17 Feb 2019 10:51:59 +0200
Source: nbd
Binary: nbd-client nbd-client-dbgsym nbd-client-udeb nbd-server 
nbd-server-dbgsym
Architecture: source amd64
Version: 1:3.19-3
Distribution: unstable
Urgency: medium
Maintainer: Wouter Verhelst 
Changed-By: Wouter Verhelst 
Description:
 nbd-client - Network Block Device protocol - client
 nbd-client-udeb - Network Block Device protocol - client for Debian Installer 
(udeb)
 nbd-server - Network Block Device protocol - server
Closes: 922383
Changes:
 nbd (1:3.19-3) unstable; urgency=medium
 .
   * debian/control: add docbook-utils to build-depends. This shouldn't
 strictly be necessary, but it's the quickest fix that allows the
 package to build again... Closes: #922383
Checksums-Sha1:
 cd99cd11fb93c278b5edf6169b03a1eca6ea473b 1972 nbd_3.19-3.dsc
 5a4af1a342d1c1ea1cd84e5e9813e3786ade04d1 92557 nbd_3.19-3.diff.gz
 dd7919240d34e64191f2d1cf569a42ce993a3058 50380 
nbd-client-dbgsym_3.19-3_amd64.deb
 d51dea8ff626893307d4ea0216a03a2896f34c51 19368 
nbd-client-udeb_3.19-3_amd64.udeb
 317c1138a36210666a3282d52c2e0d59f94d51c5 65208 nbd-client_3.19-3_amd64.deb
 aa100b016c7df6899011697c727499ef989d5d8c 93588 
nbd-server-dbgsym_3.19-3_amd64.deb
 81f5849397aa393893a2bd1a4b1266343abfe08d 77392 nbd-server_3.19-3_amd64.deb
 03919b8876248bfe98180fbd2a2b5c4913963141 12628 nbd_3.19-3_amd64.buildinfo
Checksums-Sha256:
 6250c62256b01f6f3e008065ff189e9bc19a21624d1c9c0fbe0fc7afe506b069 1972 
nbd_3.19-3.dsc
 b85d108e91c62e95db3354628f9c3998fbaa8e4ba6a634e4be848488bfa1190c 92557 
nbd_3.19-3.diff.gz
 ce9d5e2e9a1fdff411c99e3ff4150b55eb3eabd46122a1fc1bb2988fa230df3c 50380 
nbd-client-dbgsym_3.19-3_amd64.deb
 f34507dfcefc16bd067e0529736fb0eb7f8f8eb5d6dae91e3947cab1f38816ad 19368 
nbd-client-udeb_3.19-3_amd64.udeb
 0221ce77a29e0e0de036c5b169accea1567759021738cfa0c352719a3ebc99e4 65208 
nbd-client_3.19-3_amd64.deb
 939a09418c96bc70f3d95c92b7921cee65c69c4c3df4b60e1c398bb811e07ba0 93588 
nbd-server-dbgsym_3.19-3_amd64.deb
 d48bf7cbbb4cfec4fc25abc7182d7c11dd7a4392077503f94ad4048733387c0a 77392 

Bug#922502: plasma-desktop: regional settings allow do select system incompatible locales

[Charlemagne Lasse]

Package: plasma-desktop
Version: 4:5.14.5-1
Severity: critical
Justification: makes unrelated software break on the system

The "regional settings" allow to select various regions which are not
available on the system (even with locales-all). An example here is
en_DE (Germany) for "Time". This is then exported at the next login in
the env variable LC_TIME as "en_DE.UTF-8". This is not supported on
any Debian buster installation and is causing other software to break.

Here an example of me trying to install tex-common under the
environment created by the plasma desktop:

sudo aptitude reinstall tex-common
Warning: Invalid locale (please review locale settings, this might
lead to problems later):
  locale::facet::_S_create_c_locale name not valid
The following packages will be REINSTALLED:
  tex-common
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and
33 not upgraded.
Need to get 53.0 kB of archives. After unpacking 0 B will be used.
Get: 1 http://ftp.de.debian.org/debian buster/main amd64 tex-common
all 6.10 [53.0 kB]
Fetched 53.0 kB in 1s (105 kB/s)
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
apt-listchanges: Can't set locale; make sure $LC_* and $LANG are correct!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "de_DE.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("de_DE.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory
(Reading database ... 21 files and directories currently installed.)
Preparing to unpack .../tex-common_6.10_all.deb ...
Unpacking tex-common (6.10) over (6.10) ...
Setting up tex-common (6.10) ...
locale: Cannot set LC_ALL to default locale: No such file or directory
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.kwturaob
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess
returned error exit status 1
Processing triggers for man-db (2.8.5-1) ...
Errors were encountered while processing:
 tex-common
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up tex-common (6.10) ...
locale: Cannot set LC_ALL to default locale: No such file or directory
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.oXxMEBqv
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
 tex-common





sudo cat /tmp/fmtutil.oXxMEBqv
fmtutil: fmtutil is using the 

Bug#921366: marked as done (Not suitable for buster, package probably unmaintained)

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 09:04:44 +
with message-id 
and subject line Bug#921366: fixed in zeparser.js 0.0.7+dfsg-2
has caused the Debian Bug report #921366,
regarding Not suitable for buster, package probably unmaintained
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.)


-- 
921366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zeparser.js
Version: 0.0.7+dfsg-1
Severity: serious


Dear all,

In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.

Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked by someone with more involvement in
Javascript packaging than me. Thanks!

light+love,
Mike

-- System Information:
Debian Release: 9.7
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: zeparser.js
Source-Version: 0.0.7+dfsg-2

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

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated zeparser.js 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Feb 2019 04:26:53 +0530
Source: zeparser.js
Binary: libjs-zeparser node-zeparser
Architecture: source
Version: 0.0.7+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Utkarsh Gupta 
Closes: 921366
Description: 
 libjs-zeparser - Javascript library for parsing Javascript code
 node-zeparser - Javascript code parser module for Node.js
Changes:
 zeparser.js (0.0.7+dfsg-2) unstable; urgency=medium
 .
   [ Utkarsh Gupta ]
   * Add myself as an uploader (Closes: #921366)
   * Bump debhelper compatibility level to 11
   * Bump Standards-Version to 4.3.0 (no changes needed)
   * Add d/upstream/metadata
   * Switch test to pkg-js-tools
   * Re-write d/rules
   * Update d/copyright
 .
   [ Xavier Guimard ]
   * Hide some false positive lintian errors
Checksums-Sha1: 
 6d8a98f89ed0f6686051557b49ca888b4865bc19 2109 zeparser.js_0.0.7+dfsg-2.dsc
 f8b32e344eff31951ebfc8ae55c193708ee06156 2800 
zeparser.js_0.0.7+dfsg-2.debian.tar.xz
Checksums-Sha256: 
 10b67ffbda7a52318ecc6b02fbb9cc93e6556cdcf21b31b5244ae1c4909860dc 2109 
zeparser.js_0.0.7+dfsg-2.dsc
 59556d25384cc4090af3230ebdb12f05cccfc5576e2272a031a3dacb034fa185 2800 
zeparser.js_0.0.7+dfsg-2.debian.tar.xz
Files: 
 993684945f1815c5def02b3200851651 2109 javascript optional 
zeparser.js_0.0.7+dfsg-2.dsc
 da6bf28b90b9b42a1be217241cdabe98 2800 javascript optional 
zeparser.js_0.0.7+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxpH6MACgkQ9tdMp8mZ
7unaSxAAjPRjr96jjQAq00+sliNFnIkziuVwIoGat/ZpDWxWO/Nixk3b5cKgQDjh
6ioXjX3JsfTbwpHSV1LPFCyeIXJDYbGLaL0DboiUYbxAX/7kAtNJ6y4gDyyUBkw8
tCr6B+AZN11wlckluPFK1Szpgilwprf8TF9RRI2kLEmbL1kq9qtZUUf9srDzLwvp
r5gpMUL1P0ElQL0Zvb6JdNQhtSpaRN6QwAO9gt6oSpi/7VtmtiC8DutIrtBCjMoQ
WG0VZMk1trb24YoZ+EaIezNKKXeko3OymAsSSHuXHlvdoZwyEmKbwbeJ8R75G2bv
A5x05j6QfUyLTJYXmwP8b/QlUEbJjbBQ5dt06g87JKd4FU0xdenje6K0+zarAvQ1
0GE3+FR2Q6Gn9GJ2RZVmLdHofCMj47zcD1li5WgcwdckUVETiVBSi9apKBNN2n5c
IADIW6RiGXcJcGNsqZwH6z0+qRQr15SqfNvT8aKwk+Weaz2+B4PCLeUj+WqYxm5P
WUo5U3sUCarUdQ5+zy8uf5kby7uTmvFKriugTPBiPO0eOMwv7XG0a0l5MD5iBseM
xXIDQUokFpDle+ySnxiGPU9vZOI7j6Spe7R6rHqTsQyyMbIj3WNMuTKwkC5PxGzR
G1JMi5t5aZXl/+OlL3ISvXOftgalilho/PMWBhBI4A99TQ3CxfM=
=xoU+
-END PGP SIGNATURE End Message ---

Bug#905001: marked as done (ibus-wayland always fails on weston with "No input_method global")

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 08:46:49 +
with message-id 
and subject line Bug#905001: fixed in ibus 1.5.19-4
has caused the Debian Bug report #905001,
regarding ibus-wayland always fails on weston with "No input_method global"
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.)


-- 
905001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ibus-wayland
Version: 1.5.18-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Control: forwarded -1 https://github.com/ibus/ibus/issues/2030

Dear Maintainer,

ibus-wayland always 100% fails with the error message
"No input_method global" when used with the weston Debian package.
As such, the ibus-wayland Debian package
is COMPLETELY USELESS. I suggest removal of ibus-wayland package,
unless the upstream fixes this.

This is a bug in upstream. I already reported this to
https://github.com/ibus/ibus/issues/2030
See the upstream bug report for the root cause of this.


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

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

Versions of packages ibus-wayland depends on:
ii  libc6   2.27-5
ii  libglib2.0-02.56.1-2
ii  libibus-1.0-5   1.5.18-1
ii  libwayland-client0  1.15.0-2
ii  libxkbcommon0   0.8.0-2

ibus-wayland recommends no packages.

ibus-wayland suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ibus
Source-Version: 1.5.19-4

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

Debian distribution maintenance software
pp.
Osamu Aoki  (supplier of updated ibus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Feb 2019 15:19:20 +0900
Source: ibus
Binary: gir1.2-ibus-1.0 ibus ibus-dbgsym ibus-doc ibus-gtk ibus-gtk-dbgsym 
ibus-gtk3 ibus-gtk3-dbgsym ibus-wayland ibus-wayland-dbgsym libibus-1.0-5 
libibus-1.0-5-dbgsym libibus-1.0-dev
Architecture: source amd64 all
Version: 1.5.19-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Osamu Aoki 
Description:
 gir1.2-ibus-1.0 - Intelligent Input Bus - introspection data
 ibus   - Intelligent Input Bus - core
 ibus-doc   - Intelligent Input Bus - development documentation
 ibus-gtk   - Intelligent Input Bus - GTK+2 support
 ibus-gtk3  - Intelligent Input Bus - GTK+3 support
 ibus-wayland - Intelligent Input Bus - Wayland support
 libibus-1.0-5 - Intelligent Input Bus - shared library
 libibus-1.0-dev - Intelligent Input Bus - development file
Closes: 835913 905001
Changes:
 ibus (1.5.19-4) unstable; urgency=medium
 .
   [ Simon McVittie ]
   * d/p/dconf-Use-dbus-run-session-to-set-up-dconf-overrides.patch:
 Use dbus-run-session instead of dbus-launch to work with a temporary
 dconf. Build-depend on dbus (>= 1.8) for this, instead of dbus-x11.
 (Closes: #835913)
   * d/p/dconf-Create-a-temporary-XDG_RUNTIME_DIR.patch:
 Create a temporary XDG_RUNTIME_DIR while generating dconf overrides,
 instead of interacting with the user's real XDG_RUNTIME_DIR (if
 available) or issuing warnings (in sbuild).
 .
   [ Osamu Aoki ]
   * Update Wayland protocol from upstream branch. (Closes: #905001)
   * Update bug script.
Checksums-Sha1:
 3dc0722c82b26b1861cbfbe4cc77f3a32ab9cb2c 2770 ibus_1.5.19-4.dsc
 071b7f1b44b151234092b2545beb7aba46f013b8 30024 ibus_1.5.19-4.debian.tar.xz
 67d468ef8d99b3852e2ac2745a67d4b169da699b 293732 
gir1.2-ibus-1.0_1.5.19-4_amd64.deb
 3caffed59bf8cb4333892634e118de03d8edc794 1453492 ibus-dbgsym_1.5.19-4_amd64.deb
 79cccf796b13124c063a292e81a5727e9b7733e5 431764 ibus-doc_1.5.19-4_all.deb
 6f5760415c65c4951dca2a8e0253af02f3f8fe4d 40188 

Bug#922500: tex-common: Fails to install with LC_TIME=en_DE.UTF-8

[Charlemagne Lasse]

Package: tex-common
Version: 6.10
Severity: serious
Justification: Fails to install on a normal KDE installation with
"Germany" setting as Time localization

The installation works fine with LC_TIME=C but not with the setting
generated by KDE LC_TIME=en_DE.UTF-8. The aptitude output follows and
at the end the log file content mentioned in the aptitude output

sudo LC_TIME=en_DE.UTF-8 aptitude reinstall tex-common
Warning: Invalid locale (please review locale settings, this might
lead to problems later):
  locale::facet::_S_create_c_locale name not valid
The following packages will be REINSTALLED:
  tex-common
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and
33 not upgraded.
Need to get 53.0 kB of archives. After unpacking 0 B will be used.
Get: 1 http://ftp.de.debian.org/debian buster/main amd64 tex-common
all 6.10 [53.0 kB]
Fetched 53.0 kB in 1s (105 kB/s)
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
apt-listchanges: Can't set locale; make sure $LC_* and $LANG are correct!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "de_DE.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("de_DE.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory
(Reading database ... 21 files and directories currently installed.)
Preparing to unpack .../tex-common_6.10_all.deb ...
Unpacking tex-common (6.10) over (6.10) ...
Setting up tex-common (6.10) ...
locale: Cannot set LC_ALL to default locale: No such file or directory
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.kwturaob
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess
returned error exit status 1
Processing triggers for man-db (2.8.5-1) ...
Errors were encountered while processing:
 tex-common
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up tex-common (6.10) ...
locale: Cannot set LC_ALL to default locale: No such file or directory
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.oXxMEBqv
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
 tex-common














sudo cat /tmp/fmtutil.oXxMEBqv
fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order):
fmtutil:   /usr/share/texmf/web2c/fmtutil.cnf
fmtutil:   /usr/share/texlive/texmf-dist/web2c/fmtutil.cnf
fmtutil: fmtutil is using the