Bug#918316: nocache: FTBFS in sid

[Sven Joachim]

On 2019-01-04 22:49 +, Santiago Vila wrote:

> Package: src:nocache
> Version: 1.1-1
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> I tried to build this package in sid but it failed:
>
> 
> [...]
>  debian/rules build-arch
> dh build-arch
>dh_update_autotools_config -a
>dh_autoreconf -a
>dh_auto_configure -a
>dh_auto_build -a
>   make -j1 "INSTALL=install --strip-program=true"
> make[1]: Entering directory '/<>'
> cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wl,-z,relro -Wl,-z,now -o cachedel cachedel.c
> cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wl,-z,relro -Wl,-z,now -o cachestats cachestats.c
> cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wl,-z,relro -Wl,-z,now -fPIC -c -o nocache.o nocache.c
> cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wl,-z,relro -Wl,-z,now -fPIC -c -o fcntl_helpers.o fcntl_helpers.c
> cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wl,-z,relro -Wl,-z,now -fPIC -c -o pageinfo.o pageinfo.c
> cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wl,-z,relro -Wl,-z,now -pthread -shared -Wl,-soname,nocache.so -o nocache.so 
> nocache.o fcntl_helpers.o pageinfo.o -ldl
> sed 's!##libdir##!$(dirname "$0")!' nocache
> chmod a+x nocache
> make[1]: Leaving directory '/<>'
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> ## #916415
> timeout 11 ./nocache apt show coreutils 1>>/dev/null
>
> WARNING: apt does not have a stable CLI interface. Use with caution in 
> scripts.
>
> make[1]: *** [debian/rules:21: override_dh_auto_test] Error 124

I get a different error here:

,
| ## #916415
| timeout 11 ./nocache apt show coreutils 1>>/dev/null
| apt: nocache.c:148: init_mutexes: Assertion `fds_lock != NULL' failed.
| Aborted
| make[1]: *** [debian/rules:21: override_dh_auto_test] Error 134
`

Increasing the timeout to 60 as you suggested does not help.

Cheers,
   Sven

Bug#918329: apriltag ftbfs on release architectures

[Matthias Klose]

Package: src:apriltag
Version: 0.10.0-1
Severity: serious
Tags: sid buster

apriltag ftbfs on release architectures, where it built before.  Looks like the
build system is exaggerating optimization flags, using -O4 nonsense.

Bug#896786: marked as done (rss2email: missing build dependency on python3-distutils)

[Debian Bug Tracking System]

Your message dated Sat, 05 Jan 2019 07:35:00 +
with message-id 
and subject line Bug#896786: fixed in rss2email 1:3.9-4.1
has caused the Debian Bug report #896786,
regarding rss2email: missing build dependency on python3-distutils
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.)


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

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

...
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 21, in 
from distutils.core import setup
ModuleNotFoundError: No module named 'distutils.core'
E: pybuild pybuild:336: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 3.6 returned exit code 13
make: *** [debian/rules:4: clean] Error 25


Due to

python3.6 (3.6.5~rc1-2) unstable; urgency=medium

  * python3.6: Drop dependency on python3-distutils.
...
 -- Matthias Klose   Tue, 20 Mar 2018 14:29:58 +0800
--- End Message ---
--- Begin Message ---
Source: rss2email
Source-Version: 1:3.9-4.1

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

Debian distribution maintenance software
pp.
gustavo panizzo  (supplier of updated rss2email 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: Sat, 05 Jan 2019 12:52:59 +0800
Source: rss2email
Binary: rss2email
Architecture: source all
Version: 1:3.9-4.1
Distribution: unstable
Urgency: medium
Maintainer: Etienne Millon 
Changed-By: gustavo panizzo 
Description:
 rss2email  - receive RSS feeds by email
Closes: 896786
Changes:
 rss2email (1:3.9-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add missing dependency on python3-distutils (Closes: #896786)
Checksums-Sha1:
 69f8b0cbfb1db559f108bbe9a7805ded9584d531 1981 rss2email_3.9-4.1.dsc
 108d2f978df6ea3d7fb4a6679e44074a6e0e3046 12288 rss2email_3.9-4.1.debian.tar.xz
 987ab4b2ee548844d5b6596e34d205d9e325bb2e 44160 rss2email_3.9-4.1_all.deb
 332153cf3d08c8187bd4334c20b889bd6e45a3b0 5710 rss2email_3.9-4.1_arm64.buildinfo
Checksums-Sha256:
 1a4e3f76dbefcd24499f032f91751a5d0668ca1d4f41375db6ec9d82bca96609 1981 
rss2email_3.9-4.1.dsc
 1ad9434a6ae6f20651155cdff26e008102702dd77fd758de03f8f33064215b0c 12288 
rss2email_3.9-4.1.debian.tar.xz
 8c12de114fa653bbed5e830ee52d2590a23cd7dda721b9ec1b342bc182dd9829 44160 
rss2email_3.9-4.1_all.deb
 3d6750d785245114d2522cedaab0119295f911058b1d8bae4d0951597cb7edce 5710 
rss2email_3.9-4.1_arm64.buildinfo
Files:
 084bbcb9bb4dfaf578938132aba460ff 1981 mail optional rss2email_3.9-4.1.dsc
 135d39428651b2c3120e31dd4f7b6def 12288 mail optional 
rss2email_3.9-4.1.debian.tar.xz
 aff842ce88a051c00cc1421826d07581 44160 mail optional rss2email_3.9-4.1_all.deb
 ad7bbacce883b0c9cc12d361dbc68ca0 5710 mail optional 
rss2email_3.9-4.1_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEDixTvDtPMx04S0bghpRR/E7siM4FAlwwUZ0RHGdmYUB6dW1i
aS5jb20uYXIACgkQhpRR/E7siM4Rpg//QKYxeUP6uyUO19b7weVU1g1iRMFZ2HQB
hhjWIQwHq3TZqstmeTZrWsJp9uDu0Cm0f/FLxPjuNktInQsvecRRNkx/ozt/vMLL
7aFDK3tRQh9dEpAfhXZfvg+20syaTYqgCH3kfYdS+kWF2T+FJRf7uaBu5Pn1uxix
8u/rfm6Ko0rFxRTd/lm5ZFnseYkIu25qzEvye6NnaKKYtODvcu2tTvm6LmqkGPhk
MMxcyXHv9wwI6dxzJB5rLpf49bNxyQX7iGp7EKP4CBAYk4yW9X0BTsf/5B7NKkAM
zTbiCG6Y1x0y8nkSrLFV8yoleQ7S6iF0Svl2cg1PvMc/kyRCIU1xzCsDosZiMbhT
CC9Lh9uK/oEmFLgJsVUTVebwF5uIco27NmjG0QL38/vdyo4u8pNGlgGzs1EWvWDh
FttOFELtbPj8HEkOKt0Kn00lxfgrcFQIZPyzZZgvZswZW/kaLGZUxhcGJjDX+HVl
SS5SM1D3S8Ex50lQxrh93/HlnzNFzdZm5gNBPc4muAOgsSKtkvYqIIaUhu0Wh/wm
tcV4xqKTasDeyqcxZrbe+XqJwq9KV7McypoFP9czXfGXpmMznR7cysZMAy8fxhVu
FRl4lU1usY8i05Y/YGOvql0OTrD96nzHjpiquCj1B2sH9ry8yxpZ6JGdRMetRKL6
PtJ7KDlYrbU=
=Jpt2
-END PGP SIGNATURE End Message ---

Bug#918259: idle-python3.6 is not installable in unstable

[Matthias Klose]

On 04.01.19 20:58, Adrian Bunk wrote:
> Package: idle-python3.6
> Severity: serious
> 
> The following packages have unmet dependencies:
>  idle-python3.6 : Depends: python3.6-tk but it is not installable

it doesn't make sense to file this issue, with the python3.6 removal pending.

Processed: re-closing bug

[Debian Bug Tracking System]

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

> close 914607 20181214-2
Bug #914607 [dfwinreg] plaso depends on cruft package python-dfwinreg
There is no source info for the package 'dfwinreg' at version '20181214-2' with 
architecture ''
Unable to make a source version for version '20181214-2'
Ignoring request to alter fixed versions of bug #914607 to the same values 
previously set
Bug #914607 [dfwinreg] plaso depends on cruft package python-dfwinreg
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#912685: marked as done (debian/rules is not binNMU safe)

[Debian Bug Tracking System]

Your message dated Sat, 05 Jan 2019 05:49:44 +
with message-id 
and subject line Bug#912685: fixed in net-snmp 5.7.3+dfsg-5
has caused the Debian Bug report #912685,
regarding debian/rules is not binNMU safe
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.)


-- 
912685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: net-snmp
Version: 5.7.3+dfsg-4
Severity: serious

Hi,

In debian/rules you have the following:

UPSTREAM_VERSION = $(shell dpkg-parsechangelog | egrep '^Version:' | cut -f 2 
-d ':' | sed 's/ //' | sed 's/~dfsg.*$$//')
COMPAT_VERSION = $(UPSTREAM_VERSION)~dfsg
[...]
override_dh_makeshlibs:
dh_makeshlibs -plibsnmp$(LIB_VERSION) -V"libsnmp$(LIB_VERSION) (>= 
$(COMPAT_VERSION))"

When a binNMU is scheduled, UPSTREAM_VERSION is set to 5.7.3+dfsg-4+b1
and then COMPAT_VERSION is set to 5.7.3+dfsg-4+b1~dfsg which is
completely boggus

All the reverse-dependency will have this boggus version in their
generated dependency list.

Why aren't you using "dh_makeshlibs -V" or the version macro that are
present in /usr/share/dpkg/pkg-info.mk ?

Kind regards,

Laurent Bigonville


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
--- End Message ---
--- Begin Message ---
Source: net-snmp
Source-Version: 5.7.3+dfsg-5

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated net-snmp 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: Sat, 05 Jan 2019 16:16:10 +1100
Source: net-snmp
Binary: snmpd snmptrapd snmp libsnmp-base libsnmp30 libsnmp30-dbg libsnmp-dev 
libsnmp-perl python-netsnmp tkmib
Architecture: source all amd64
Version: 5.7.3+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Net-SNMP Packaging Team 
Changed-By: Craig Small 
Description:
 libsnmp-base - SNMP configuration script, MIBs and documentation
 libsnmp-dev - SNMP (Simple Network Management Protocol) development files
 libsnmp-perl - SNMP (Simple Network Management Protocol) Perl5 support
 libsnmp30  - SNMP (Simple Network Management Protocol) library
 libsnmp30-dbg - SNMP (Simple Network Management Protocol) library debug
 python-netsnmp - SNMP (Simple Network Management Protocol) Python support
 snmp   - SNMP (Simple Network Management Protocol) applications
 snmpd  - SNMP (Simple Network Management Protocol) agents
 snmptrapd  - Net-SNMP notification receiver
 tkmib  - SNMP (Simple Network Management Protocol) MIB browser
Closes: 912685 914657
Changes:
 net-snmp (5.7.3+dfsg-5) unstable; urgency=medium
 .
   * Use debhelper macros for shlibs Closes: #912685
   * Relocate snmp.conf to libsnmp-base Closes: #914657
Checksums-Sha1:
 74f1d4557abab09e42195f26982f40a6ec626ceb 2968 net-snmp_5.7.3+dfsg-5.dsc
 280c0178fc901575f78b4746d8879170e296ac46 77572 
net-snmp_5.7.3+dfsg-5.debian.tar.xz
 97a571ebb6584194f45f0175392e241cfa82b582 1594640 
libsnmp-base_5.7.3+dfsg-5_all.deb
 ca8f8089ad99287b8a7a23fdb0fffee2ac3cfeff 1100432 
libsnmp-dev_5.7.3+dfsg-5_amd64.deb
 63d798703bfd73f82133c31e0acc7bcf1102cfc9 346208 
libsnmp-perl-dbgsym_5.7.3+dfsg-5_amd64.deb
 edcdc3ec4694ac34b1e8323774d87f4ce8a0efb6 1532596 
libsnmp-perl_5.7.3+dfsg-5_amd64.deb
 9250ee79500f06e7ad736492d6b2899faf7db1e6 2726376 
libsnmp30-dbg_5.7.3+dfsg-5_amd64.deb
 a37914f950fec4c799c71d5dfe09b53f403a0847 2324088 
libsnmp30_5.7.3+dfsg-5_amd64.deb
 f17825beeaf214ea211f8ee24f00dd231b4907f0 10912 
net-snmp_5.7.3+dfsg-5_amd64.buildinfo
 bf50b4d9d99baa7a4c37d8

Bug#914657: marked as done (missing snmp.conf triggers flood of error messages)

[Debian Bug Tracking System]

Your message dated Sat, 05 Jan 2019 05:49:44 +
with message-id 
and subject line Bug#914657: fixed in net-snmp 5.7.3+dfsg-5
has caused the Debian Bug report #914657,
regarding missing snmp.conf triggers flood of error messages
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.)


-- 
914657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsnmp30
Version: 5.7.3+dfsg-4+b1
Severity: important


Hi,

when I start an application like gscan2pdf or colord, I get flodded with
the following messages on stdout:

MIB search path: 
/home/michael/.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf:/usr/share/mibs/site:/usr/share/snmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp
Cannot find module (SNMPv2-MIB): At line 1 in (none)
Cannot find module (IF-MIB): At line 1 in (none)
Cannot find module (IP-MIB): At line 1 in (none)
Cannot find module (TCP-MIB): At line 1 in (none)
Cannot find module (UDP-MIB): At line 1 in (none)
Cannot find module (HOST-RESOURCES-MIB): At line 1 in (none)
Cannot find module (NOTIFICATION-LOG-MIB): At line 1 in (none)
Cannot find module (DISMAN-EVENT-MIB): At line 1 in (none)
Cannot find module (DISMAN-SCHEDULE-MIB): At line 1 in (none)
Cannot find module (HOST-RESOURCES-TYPES): At line 1 in (none)
Cannot find module (MTA-MIB): At line 1 in (none)
Cannot find module (NETWORK-SERVICES-MIB): At line 1 in (none)
Cannot find module (SNMPv2-TC): At line 15 in 
/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt
Cannot find module (SNMPv2-SMI): At line 34 in 
/usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Cannot find module (SNMPv2-TC): At line 37 in 
/usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Did not find 'enterprises' in module #-1 (/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Did not find 'TruthValue' in module #-1 (/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Unlinked OID in UCD-SNMP-MIB: ucdavis ::= { enterprises 2021 }
Undefined identifier: enterprises near line 39 of 
/usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt)
Did not find 'ucdExperimental' in module UCD-SNMP-MIB 
(/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt)
Unlinked OID in UCD-DISKIO-MIB: ucdDiskIOMIB ::= { ucdExperimental 15 }
Undefined identifier: ucdExperimental near line 19 of 
/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt
Cannot find module (SNMPv2-TC): At line 10 in 
/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt)
Did not find 'ucdExperimental' in module UCD-SNMP-MIB 
(/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt)
Unlinked OID in UCD-DLMOD-MIB: ucdDlmodMIB ::= { ucdExperimental 14 }
Undefined identifier: ucdExperimental near line 13 of 
/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt
Cannot find module (SNMPv2-TC): At line 15 in 
/usr/share/snmp/mibs/LM-SENSORS-MIB.txt
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/LM-SENSORS-MIB.txt)
Did not find 'ucdExperimental' in module UCD-SNMP-MIB 
(/usr/share/snmp/mibs/LM-SENSORS-MIB.txt)
Unlinked OID in LM-SENSORS-MIB: lmSensors ::= { ucdExperimental 16 }
Undefined identifier: ucdExperimental near line 32 of 
/usr/share/snmp/mibs/LM-SENSORS-MIB.txt
Did not find 'ucdavis' in module UCD-SNMP-MIB 
(/usr/share/snmp/mibs/UCD-DEMO-MIB.txt)
Unlinked OID in UCD-DEMO-MIB: ucdDemoMIB ::= { ucdavis 14 }
Undefined identifier: ucdavis near line 7 of 
/usr/share/snmp/mibs/UCD-DEMO-MIB.txt
Cannot find module (SNMP-TARGET-MIB): At line 1 in (none)
Cannot find module (SNMP-FRAMEWORK-MIB): At line 9 in 
/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Cannot find module (SNMPv2-SMI): At line 8 in 
/usr/share/snmp/mibs/NET-SNMP-MIB.txt
Did not find 'enterprises' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-MIB.txt)
Unlinked OID in NET-SNMP-MIB: netSnmp ::= { enterprises 8072 }
Undefined identifier: enterprises near line 10 of 
/usr/share/snmp/mibs/NET-SNMP-MIB.txt
Cannot find module (SNMPv2-TC): At line 21 in 
/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Did not find 'SnmpAdminString' in module #-1 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'netSnmpObjects' in module NET-SNMP-MIB 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'netSnmpModuleIDs' in module NET-SNMP-MIB 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'netSnmpNotifications' in module NET-SNMP-MIB 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'netSnmpGroups' in modu

Bug#918188: linux: FTBFS on arm64

[Noah Meyerhans]

On Fri, Jan 04, 2019 at 06:57:21AM +0100, Salvatore Bonaccorso wrote:
> >   LD  vmlinux.o
> >   MODPOST vmlinux.o
> >   GEN .version
> >   CHK include/generated/compile.h
> >   UPD include/generated/compile.h
> >   CC  init/version.o
> >   LD  init/built-in.o
> > ./drivers/firmware/efi/libstub/lib.a(arm64-stub.stub.o): In function 
> > `handle_kernel_image':
> > ./debian/build/build_arm64_none_arm64/./drivers/firmware/efi/libstub/arm64-stub.c:63:
> >  undefined reference to `__efistub__GLOBAL_OFFSET_TABLE_'
> > ld: ./drivers/firmware/efi/libstub/lib.a(arm64-stub.stub.o): relocation 
> > R_AARCH64_ADR_PREL_PG_HI21 against external symbol 
> > `__efistub__GLOBAL_OFFSET_TABLE_' can not be used when making a shared 
> > object; recompile with -fPIC
> > /<>/Makefile:1010: recipe for target 'vmlinux' failed
> > make[5]: *** [vmlinux] Error 1
> > Makefile:152: recipe for target 'sub-make' failed
> > make[4]: *** [sub-make] Error 2
> > Makefile:24: recipe for target '__sub-make' failed
> > make[3]: *** [__sub-make] Error 2
> > make[3]: Leaving directory 
> > '/<>/debian/build/build_arm64_none_arm64'
> > debian/rules.real:190: recipe for target 
> > 'debian/stamps/build_arm64_none_arm64' failed
> > make[2]: *** [debian/stamps/build_arm64_none_arm64] Error 2
> > make[2]: Leaving directory '/<>'
> > debian/rules.gen:400: recipe for target 'build-arch_arm64_none_arm64_real' 
> > failed
> > make[1]: *** [build-arch_arm64_none_arm64_real] Error 2
> > make[1]: Leaving directory '/<>'
> > debian/rules:41: recipe for target 'build-arch' failed
> > make: *** [build-arch] Error 2
> > dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
> 
> https://buildd.debian.org/status/fetch.php?pkg=linux&arch=arm64&ver=4.9.144-1&stamp=1546572157&raw=0

The problem was introduced with upstream commit
27b5ebf61818749b3568354c64a8ec2d9cd5ecca. Reverting that commit fixes
the build, but there may be a better option.



signature.asc
Description: PGP signature

Bug#918326: python-dfwinreg and python3-dfwinreg depend on cruft package dtfabric

[peter green]

package: python3-dfwinreg
version: 20180712-1
severity: serious

It seems that with the most recent upload the build-dependencies were fixed from "dtfabric" to 
"python-dtfabric" and "python3-dtfabric", but the binary dependencies for python-dfwinreg and 
python3-dtwinreg are still on "dtfabric", can you please fix them.

Bug#914607: closed by Hilko Bengen (Bug#914607: fixed in dfwinreg 20181214-2)

[peter green]

reassign 914607 dfwinreg
found 914607 20180712-1
fixed 914607 20181214-2
thanks

Britney gets confused when a bug is closed by a package other than the one it 
is filed against, so I am reassinging the bug to the package that closed it.

On 01/01/19 23:09, Debian Bug Tracking System wrote:

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

#914607: plaso depends on cruft package python-dfwinreg

It has been closed by Hilko Bengen .

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 Hilko Bengen 
 by
replying to this email.

Processed: Re: Bug#914607 closed by Hilko Bengen (Bug#914607: fixed in dfwinreg 20181214-2)

[Debian Bug Tracking System]

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

> reassign 914607 dfwinreg
Bug #914607 {Done: Hilko Bengen } [plaso] plaso depends on 
cruft package python-dfwinreg
Bug reassigned from package 'plaso' to 'dfwinreg'.
No longer marked as found in versions plaso/1.5.1+dfsg-4.
No longer marked as fixed in versions dfwinreg/20181214-2.
> found 914607 20180712-1
Bug #914607 {Done: Hilko Bengen } [dfwinreg] plaso depends 
on cruft package python-dfwinreg
There is no source info for the package 'dfwinreg' at version '20180712-1' with 
architecture ''
Unable to make a source version for version '20180712-1'
Marked as found in versions 20180712-1 and reopened.
> fixed 914607 20181214-2
Bug #914607 [dfwinreg] plaso depends on cruft package python-dfwinreg
There is no source info for the package 'dfwinreg' at version '20181214-2' with 
architecture ''
Unable to make a source version for version '20181214-2'
Marked as fixed in versions 20181214-2.
> thanks
Stopping processing here.

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

Bug#905877: regression in 1.4: upgrades random packages from testing to experimental (doesn't respect pinning?)

[Paul Wise]

Package: unattended-upgrades
Version: 1.9

On Sat, 11 Aug 2018 10:40:33 +0800 Paul Wise wrote:

> Recently I have had unattended-upgrades upgrade random packages from
> testing to experimental.

I thought this had been fixed but recently I got git upgraded to
experimental for some reason. I've included the full debug log below.

Unattended upgrade result: All upgrades installed 

Warning: A reboot is required to complete this upgrade, or a previous one.

Packages that were upgraded:
 git git-cvs git-doc git-email git-gui git-man git-mediawiki git-svn 
 gitk libqt5help5 libqt5multimediagsttools5 
 libqt5multimediagsttools5-dbgsym libqt5multimediaquick5 
 libqt5x11extras5 libqt5x11extras5-dbgsym python3-dbus.mainloop.pyqt5 
 python3-dbus.mainloop.pyqt5-dbg qml-module-qtmultimedia 
 qml-module-qtqml-models2 qml-module-qtquick-window2 
 qml-module-qtquick2 roodi 

Packages with upgradable origin but kept back:
 gimp gimp-data libgimp2.0 

Package installation log:
Log started: 2019-01-03  10:27:53
apt-listchanges: Reading changelogs...
apt-listchanges: Mailing root: apt-listchanges: changelogs for chianamo
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 460714 files and directories currently installed.)
Preparing to unpack .../00-git-cvs_1%3a2.20.1+next.20181228-1_all.deb ...
Unpacking git-cvs (1:2.20.1+next.20181228-1) over (1:2.19.2-1) ...
Preparing to unpack .../01-gitk_1%3a2.20.1+next.20181228-1_all.deb ...
Unpacking gitk (1:2.20.1+next.20181228-1) over (1:2.19.2-1) ...
Preparing to unpack .../02-git-svn_1%3a2.20.1+next.20181228-1_all.deb ...
Unpacking git-svn (1:2.20.1+next.20181228-1) over (1:2.19.2-1) ...
Preparing to unpack .../03-git-mediawiki_1%3a2.20.1+next.20181228-1_all.deb ...
Unpacking git-mediawiki (1:2.20.1+next.20181228-1) over (1:2.19.2-1) ...
Preparing to unpack .../04-git-gui_1%3a2.20.1+next.20181228-1_all.deb ...
Unpacking git-gui (1:2.20.1+next.20181228-1) over (1:2.19.2-1) ...
Preparing to unpack .../05-git-email_1%3a2.20.1+next.20181228-1_all.deb ...
Unpacking git-email (1:2.20.1+next.20181228-1) over (1:2.19.2-1) ...
Preparing to unpack .../06-git_1%3a2.20.1+next.20181228-1_amd64.deb ...
Unpacking git (1:2.20.1+next.20181228-1) over (1:2.19.2-1) ...
Preparing to unpack .../07-git-man_1%3a2.20.1+next.20181228-1_all.deb ...
Unpacking git-man (1:2.20.1+next.20181228-1) over (1:2.19.2-1) ...
Preparing to unpack .../08-git-doc_1%3a2.20.1+next.20181228-1_all.deb ...
Unpacking git-doc (1:2.20.1+next.20181228-1) over (1:2.19.2-1) ...
Preparing to unpack .../09-libqt5help5_5.11.3-2_amd64.deb ...
Unpacking libqt5help5:amd64 (5.11.3-2) over (5.11.2-5) ...
Preparing to unpack .../10-libqt5multimediagsttools5-dbgsym_5.11.3-2_amd64.deb 
...
Unpacking libqt5multimediagsttools5-dbgsym:amd64 (5.11.3-2) over (5.11.2-2) ...
Preparing to unpack .../11-libqt5multimediagsttools5_5.11.3-2_amd64.deb ...
Unpacking libqt5multimediagsttools5:amd64 (5.11.3-2) over (5.11.2-2) ...
Preparing to unpack .../12-libqt5multimediaquick5_5.11.3-2_amd64.deb ...
Unpacking libqt5multimediaquick5:amd64 (5.11.3-2) over (5.11.2-2) ...
Preparing to unpack .../13-libqt5x11extras5-dbgsym_5.11.3-2_amd64.deb ...
Unpacking libqt5x11extras5-dbgsym:amd64 (5.11.3-2) over (5.11.2-2) ...
Preparing to unpack .../14-libqt5x11extras5_5.11.3-2_amd64.deb ...
Unpacking libqt5x11extras5:amd64 (5.11.3-2) over (5.11.2-2) ...
Preparing to unpack 
.../15-python3-dbus.mainloop.pyqt5-dbg_5.11.3+dfsg-1+b3_amd64.deb ...
Unpacking python3-dbus.mainloop.pyqt5-dbg (5.11.3+dfsg-1+b3) over 
(5.11.3+dfsg-1+b2) ...
Preparing to unpack 
.../16-python3-dbus.mainloop.pyqt5_5.11.3+dfsg-1+b3_amd64.deb ...
Unpacking python3-dbus.mainloop.pyqt5 (5.11.3+dfsg-1+b3) over 
(5.11.3+dfsg-1+b2) ...
Preparing to unpack .../17-qml-module-qtquick2_5.11.3-2_amd64.deb ...
Unpacking qml-module-qtquick2:amd64 (5.11.3-2) over (5.11.2-3) ...
Preparing to unpack .../18-qml-module-qtmultimedia_5.11.3-2_amd64.deb ...
Unpacking qml-module-qtmultimedia:amd64 (5.11.3-2) over (5.11.2-2) ...
Preparing to unpack .../19-qml-module-qtqml-models2_5.11.3-2_amd64.deb ...
Unpacking qml-module-qtqml-models2:amd64 (5.11.3-2) over (5.11.2-3) ...
Preparing to unpack .../20-qml-module-qtquick-window2_5.11.3-2_amd64.deb ...
Unpacking qml-module-qtquick-window2:amd64 (5.11.3-2) over (5.11.2-3) ...
Preparing to unpack .../21-roodi_5.0.0-2_all.deb ...
Unpacking roodi (5.0.0-2) over (5.0.0-1) ...
Setting up git-man (1:2.20.1+next.20181228-1) ...
Setting up qml-module-qtquick2:amd64 (5.11.3-2) ...
Set

Bug#918323: unattended-upgrades: tried to upgrade package with conffile prompt

[Paul Wise]

Package: unattended-upgrades
Version: 1.9
Severity: serious

unattended-upgrades tried to upgrade a package (lvm2) with a conffile
prompt and failed because conffile prompts require user input. This
meant that the upgrade of lvm2 failed and was the system was left in a
partially broken state. Normally unattended-upgrades refuses to upgrade
packages that need conffile prompts, so this seems like a regression.

I've included the full log with debug info below:

Unattended upgrade result: All upgrades installed 

Warning: A reboot is required to complete this upgrade, or a previous one.

Packages that attempted to upgrade:
 antlr4 cppcheck dh-golang dmeventd dmsetup gir1.2-secret-1 
 gnome-shell-extension-suspend-button gnome-shell-extension-weather 
 hub kpartx libantlr4-runtime-java libcdr-0.1-1 
 libdevmapper-event1.02.1 libdevmapper1.02.1 
 libdevmapper1.02.1-dbgsym libetonyek-0.1-1 libqxp-0.0-0 
 libsecret-1-0 libsecret-1-0-dbgsym libsecret-common libsecret-tools 
 libwpd-0.10-10 lvm2 python-sqlalchemy 

Packages with upgradable origin but kept back:
 gimp gimp-data libgimp2.0 

Package installation log:
Log started: 2019-01-04  12:49:36
[master 31e4f0db] saving uncommitted changes in /etc prior to apt run
 1 file changed, 0 insertions(+), 0 deletions(-)
 rewrite debdelta/gnupg/random_seed (100%)
apt-listchanges: Reading changelogs...
apt-listchanges: Mailing root: apt-listchanges: changelogs for chianamo
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 460811 files and directories currently installed.)
Preparing to unpack .../libdevmapper1.02.1-dbgsym_2%3a1.02.155-1_amd64.deb ...
Unpacking libdevmapper1.02.1-dbgsym:amd64 (2:1.02.155-1) over (2:1.02.145-4.1) 
...
Preparing to unpack .../dmsetup_2%3a1.02.155-1_amd64.deb ...
Unpacking dmsetup (2:1.02.155-1) over (2:1.02.145-4.1) ...
Setting up dmsetup (2:1.02.155-1) ...
update-initramfs: deferring update (trigger activated)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 460811 files and directories currently installed.)
Preparing to unpack .../libdevmapper1.02.1_2%3a1.02.155-1_amd64.deb ...
Unpacking libdevmapper1.02.1:amd64 (2:1.02.155-1) over (2:1.02.145-4.1) ...
Setting up libdevmapper1.02.1:amd64 (2:1.02.155-1) ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 460811 files and directories currently installed.)
Preparing to unpack .../00-antlr4_4.7.1-1_all.deb ...
Unpacking antlr4 (4.7.1-1) over (4.6-2) ...
Preparing to unpack .../01-libantlr4-runtime-java_4.7.1-1_all.deb ...
Unpacking libantlr4-runtime-java (4.7.1-1) over (4.6-2) ...
Preparing to unpack .../02-cppcheck_1.86-1_amd64.deb ...
Unpacking cppcheck (1.86-1) over (1.85-2) ...
Preparing to unpack .../03-dh-golang_1.39_all.deb ...
Unpacking dh-golang (1.39) over (1.38) ...
Preparing to unpack .../04-libdevmapper-event1.02.1_2%3a1.02.155-1_amd64.deb ...
Unpacking libdevmapper-event1.02.1:amd64 (2:1.02.155-1) over (2:1.02.145-4.1) 
...
Selecting previously unselected package liblvm2cmd2.03:amd64.
Preparing to unpack .../05-liblvm2cmd2.03_2.03.02-1_amd64.deb ...
Unpacking liblvm2cmd2.03:amd64 (2.03.02-1) ...
Preparing to unpack .../06-dmeventd_2%3a1.02.155-1_amd64.deb ...
Unpacking dmeventd (2:1.02.155-1) over (2:1.02.145-4.1) ...
Preparing to unpack .../07-libsecret-1-0-dbgsym_0.18.7-1_amd64.deb ...
Unpacking libsecret-1-0-dbgsym:amd64 (0.18.7-1) over (0.18.6-3) ...
Preparing to unpack .../08-libsecret-common_0.18.7-1_all.deb ...
Unpacking libsecret-common (0.18.7-1) over (0

Bug#918322: More info

[Jakub Sokołowski]

Seems like I failed to add additional info:

Picture of error: 
https://mega.nz/#!LehDlKbB!x_pFGX3wlq-Kgo6v5jUC6ydbqTQ4R43bft7mAC6j_ms

This seems to be realted to initrd since when I ran update-initramfs on an 
older kernel that one started showing the same symptoms as the new one.

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

[Sam Hartman]

> "Adrian" == Adrian Bunk  writes:

latest upgrade of libkrb5-3 (1.16.1-1 -> 1.16.2-1)
>> automount starts but dies immediately after accessing a
>> automounter point.
>> 
>> Automount is configured to authenticate via GSSAPI using system
>> keytab.  After the GSSAPI authentication succeeded, any access to
>> a configure automount entry causes automount to die with an
>> assertion failure (followed by an abort()):

Adrian> Thanks for your report.

Adrian> I'm moving this bug report to libkrb5-3 since this is the
Adrian> change that triggered your regression for assessment whether
Adrian> the bug is there.

Adrian, I'm guessing you're looking at this with your QA hat on?
How well do you understand autofs?  Any chance you could help put
together a repo?  If you don't know autofs-ldap well, I can learn it
just as well as anyone, but if you do happen to know it well, help would
be appreciated.
In the latest krb5 package, the debian/tests directory contains a
slapd-gssapi test which happens to set up LDAP well enough that you can
SASL authenticate it.
So, my guess is that adapting that test to  set up an autofs-ldap that
uses gss auth to ldap probably isn't too incredibly hard.
I don't know autofs at all, and for example I don't know how to set up
the directory to have the right info.

If you or the submitter can easily help, it would be appreciated.
If not, I'll look into it.

--Sam

Bug#917782: [gimp] Missing symbol

[Paolo Redaelli]

First of all sorry for the late answer, Google tought your answer were
spam. :(

Il 30/12/18 15:51, Simon McVittie ha scritto:
> Control: tags -1 + moreinfo
>
> On Sun, 30 Dec 2018 at 11:45:12 +0100, Paolo Redaelli wrote:
>> gimp: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0:
>> undefined symbol: babl_format_with_space
> Do you have a version of libbabl-0.1-0 installed from some apt
> source outside Debian, for instance deb-multimedia.org, or a copy of
> libbabl-0.1.so.0 in a non-dpkg-managed directory like /usr/local/lib?
>
> We have had recurring problems with deb-multimedia.org providing its own
> libbabl-0.1-0 and libgegl-0.4-0 packages, which are marked with higher
> version numbers than any official Debian version, causing them to satisfy
> versioned dependencies even when they should not.

Indeed you're right. After I removed the libbabl-0.10 which came from
deb-multimedia the issue was solved.

That's taught me to stick to Debian repositories and not tainting a
system: I removed deb-multimedia from my sources long ago, I thought its
effects were "faded"

>> libbabl-0.1-0 (>= 0.1.10) |
>> libgegl-0.4-0 (>= 0.4.12) |
> Either you do not have libbabl and libgegl installed, or (probably
> more likely) whatever software you were using to report this bug
> is not reporting installed packages correctly. 
I used reportbug-ng
> Please report bugs
> using the reportbug(1) tool from the reportbug package whenever
> possible.  The reportbug-ng package is not recommended, due to
>  (it is also no longer maintained).

I wasn't aware of its status. I'll stick to plain reportbug


> You can provide the same information that reportbug would have done
> by running "reportbug --template gimp" and pasting its output into an
> email to the bug address.

Thanks. Sorry for the lame bug.

Bug#917727: openhft-lang: FTBFS: [ERROR] /<>/lang/src/main/java/net/openhft/lang/io/IOTools.java:[85, 13] cannot find symbol

[tony mancill]

On Wed, Jan 02, 2019 at 01:05:40PM +0100, Emmanuel Bourg wrote:
> Le 30/12/2018 à 17:29, tony mancill a écrit :
> 
> > Given that there aren't many (or any?) r-deps for the openhft libraries,
> > I'm tempted to pull the versions in experimental into unstable so we
> > have the libraries in buster.  It's either that, or not include these
> > packages in buster at all.
> > 
> > Thoughts?
> 
> The OpenHFT libraries are used by Spring (libspring-java), and if I
> remember well I had to pick very specific versions to have a consistent
> set of compatible libraries. I plan to upgrade Spring to the version 5.1
> before the freeze, I'll see at this moment what versions of the OpenHFT
> libraries are required.

Ah, I don't want to break libspring-java, so I'll wait to hear from you.
Let me know if there are bits I can help with.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#832355: ktap: module FTBFS for Linux 4.6: error: '__GFP_WAIT' undeclared

[Azat Khuzhin]

> But it looks like ktap is dead upstream now, so perhaps we should just
> remove it from the archive instead?

Sadly, but yes.
So agree, should be just removed from the archive.

Regards,
Azat.

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

[Greg Hudson]

On Fri, 04 Jan 2019 15:54:01 -0500 Sam Hartman  wrote:
> There are no thread support changes between 1.16.1 and 1.16.2.
> There is one ccache related change which I'll include below related to
> memory ccaches.
> Do you know what type of credential cache  is being used here?

krb5_mcc_start_seq_get() is in the traceback, so the memory cache change
is a clear candidate for the bug.  I can't find anything wrong with the
code, though.  From the stack trace, there appears to be a memory ccache
on the list with an invalid mutex, but I don't see any way of getting
into that state.

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

[Debian Bug Tracking System]

Your message dated Sat, 05 Jan 2019 00:19:34 +
with message-id 
and subject line Bug#918313: Removed package(s) from unstable
has caused the Debian Bug report #899449,
regarding bfgminer: Invalid maintainer address 
pkg-bitcoin-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of bfgminer,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 5.4.2+dfsg-1+rm

Dear submitter,

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

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

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

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

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

Bug#900930: marked as done (CVE-2018-10057 CVE-2018-10058)

[Debian Bug Tracking System]

Your message dated Sat, 05 Jan 2019 00:19:34 +
with message-id 
and subject line Bug#918313: Removed package(s) from unstable
has caused the Debian Bug report #900930,
regarding CVE-2018-10057 CVE-2018-10058
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.)


-- 
900930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bfgminer
Severity: grave
Tags: security

http://www.openwall.com/lists/oss-security/2018/06/03/1
 
--- End Message ---
--- Begin Message ---
Version: 5.4.2+dfsg-1+rm

Dear submitter,

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

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

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

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

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

Bug#899596: marked as done (libxfcegui4: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 05 Jan 2019 00:19:06 +
with message-id 
and subject line Bug#918199: Removed package(s) from unstable
has caused the Debian Bug report #899596,
regarding libxfcegui4: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of libxfcegui4,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 4.10.0-4+rm

Dear submitter,

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

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

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

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

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

Processed: Re: nocache: FTBFS in sid

[Debian Bug Tracking System]

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

> tags 918316 + patch
Bug #918316 [src:nocache] nocache: FTBFS in sid
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#918316: nocache: FTBFS in sid

[Santiago Vila]

tags 918316 + patch
thanks

The patch below works for me:

--- a/debian/rules
+++ b/debian/rules
@@ -18,5 +18,5 @@ override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
 #  -NOCACHE_NR_FADVISE=2 dh_auto_test -v
## #916415
-   timeout 11 ./nocache apt show coreutils 1>>/dev/null
+   timeout 60 ./nocache apt show coreutils 1>>/dev/null
 endif


Note: I don't quite understand the purpose of the timeout. Is it
really useful/required to set a timeout at all? Normally sbuild (the
autobuilder program used by the build daemons) has already a built-in
timeout mechanism which prevents the autobuilder to be stuck forever,
and by looking at build logs from reproducible builds, I believe
pbuilder has also a timeout by default.

Thanks.

Bug#894285: android-framework-23 FTBFS with openjdk-9

[Markus Koschany]

I had a go at this and it looks like the package simply is not ready for
Java 9+. The unmappable character error is bogus. Rather issues like
using an underscore character as a variable name (which is forbidden in
Java 9) or naming a package java.lang ... are the root cause of the FTBFS.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#876060: marked as done (vit's error messages makes its output blow up.)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 23:05:05 +
with message-id 
and subject line Bug#876060: fixed in vit 1.3~beta1-1
has caused the Debian Bug report #876060,
regarding vit's error messages makes its output blow up.
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.)


-- 
876060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vit
Version: 1.2-4
Severity: important

Dear Maintainer,

I start to use taskwarrior a week ago. That is good for me.
And, I tried to use vit on urxvt (rxvt-unicode 9.22-1+b1)


And, I use taskwarrior with Japanese(UTF8 encode)

When I use vit, vit reports 
"Negative repeat count does nothing at /usr/bin/vit line 775."

more than three times. It does not make me read tasks.

And, use "j","k" key, makes blow up messages on the terminal.

I would like to use vit on UTF8 environment(Japanese environment)

If you want to dummy data for reporducing. I will make that.

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

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

Versions of packages vit depends on:
ii  libcurses-perl  1.36-1+b1
ii  perl5.24.1-3+deb9u1
ii  taskwarrior 2.5.1+dfsg-3

vit recommends no packages.

vit suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: vit
Source-Version: 1.3~beta1-1

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

Debian distribution maintenance software
pp.
Iain R. Learmonth  (supplier of updated vit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Jan 2019 22:36:27 +
Source: vit
Binary: vit
Architecture: source all
Version: 1.3~beta1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Tasktools Packaging Team 
Changed-By: Iain R. Learmonth 
Description:
 vit- full-screen terminal interface for Taskwarrior
Closes: 876060
Changes:
 vit (1.3~beta1-1) unstable; urgency=medium
 .
   * New upstream version 1.3~beta1
- It is not clear exactly how the "Negative repeat count does nothing" were
  solved, but they no longer occur in this release. (Closes: #876060)
   * Removed patches as fixes are implemented upstream
   * The command file location is changed to /usr/share/vit/commands
Checksums-Sha1:
 19c01fe9e7893ab76151d7da730f3d3d49757987 1982 vit_1.3~beta1-1.dsc
 75b488d1618614b2d1fb42bb9464dd0a4e0131c9 56006 vit_1.3~beta1.orig.tar.gz
 b2a33d38a5297fecb26438e64387f1836fa33f09 3120 vit_1.3~beta1-1.debian.tar.xz
 46a30fcca81f9b8b3f0673ef0783d47d06c70bf1 23152 vit_1.3~beta1-1_all.deb
 4f36353ae8690c146779a1c83430b7d9e4b9 5603 vit_1.3~beta1-1_amd64.buildinfo
Checksums-Sha256:
 64134c43b46c6f38b4e5f160c73038e0cb012a9bf23a5a1b677ee96db4c53cda 1982 
vit_1.3~beta1-1.dsc
 0ce916c9aaa3be657bc5f9eaa5b6413d1214cb8b556e5c55534c4ca616a74dae 56006 
vit_1.3~beta1.orig.tar.gz
 8039dc30c3df5ea165d88e510e224d7f7e6d9174036037003aafc1a0d92c2586 3120 
vit_1.3~beta1-1.debian.tar.xz
 740add1aca9ab4ff4c8248bcb92e8ee270fdc2690c83e1ab2bf52ee5090c1d45 23152 
vit_1.3~beta1-1_all.deb
 0bb63c7c321e0c6284a1ed91214dbf7ab019e80abb913909da9ef1ad3ac5ad08 5603 
vit_1.3~beta1-1_amd64.buildinfo
Files:
 b07e27c15ce5ced54d263778bfce7ee3 1982 utils extra vit_1.3~beta1-1.dsc
 91db356c82bb53d8aff14fd61964b566 56006 utils extra vit_1.3~beta1.orig.tar.gz
 42507f69105b06da2f1939bc066e50b2 3120 utils extra vit_1.3~beta1-1.debian.tar.xz
 9f086c99758d740f119203eb2efd8a6d 23152 utils extra vit_1.3~beta1-1_all.deb
 d18c53089cee21b792b047ab7ffd9468 5603 utils extra 
vit_1.3~beta1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE/ps4MHN0fw3t6AudF4mIfdjVvF0FAlwv4WoACgkQF4mIfdjV
vF3tJxAAlae/isHlzVnNaOtYt5enugAg1j7NvrX/Zgb6SpBV9Zal8ZYDP12rhOQ+
Mz/4249sYZFqjRtZsV

Bug#907624: What ffindex do we want to package

[Steffen Möller]

Heya, I have replied, at least I had typed it :o/

So, yes, I had chosen that version of ffsort_index to get hhsuite to 
compile. I have no idea if there are other reverse dependencies on 
ffindex, my priority is on hhsuite.


Cheers,

Steffen

On 04.01.19 18:17, Michael Crusoe wrote:
I think 0.9.9.7+sog+git20160415.14274c9-1 is the source of the recent 
FTBFS of hhsuite: https://bugs.debian.org/917495 as our packaged 
version is missing the "ffsort_index" function.


The hh-suite github repo contains a submodule pointing at their fork 
of ffindex at ~ 2017-06-01:
https://github.com/soedinglab/hh-suite/tree/v3.0-beta.3/lib → 
https://github.com/soedinglab/ffindex_soedinglab/tree/360e4176ece531be34a94298c808349916d016ac


I suggest that we package it as part of hhsuite until another package 
needs it.


hhsuite does provide  "*-Source*" packages that include ffindex, so we 
wouldn't need a multi-source build.




În joi, 20 dec. 2018 la 11:59, Andreas Tille > a scris:


Ping?
Steffen, if you did not had a specific reason I assume it was by
mistake and will replace the Segfaulting code by the original one.
If I do not hear from you I assume you will agree.
Kind regards, Andreas.

On Wed, Dec 19, 2018 at 09:53:38AM +0100, Andreas Tille wrote:
> Hi,
>
> after reading
https://github.com/soedinglab/ffindex_soedinglab/issues/4
> I came to the conclusion that we somehow picked the wrong fork of
> ffindex.  For me it seems very probable that if we pick the old
codebase
> bug #907624 which was introduced when choosing this will vanish
if we
> revert to the previously packaged code base.  I have a local commit
> which is doing this:
>
>
> diff --git a/debian/changelog b/debian/changelog
> index 6a26115..c409f4f 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,12 @@
> +ffindex (0.9.9.7+sog+git20160415.14274c9-1) UNRELEASED;
urgency=medium
> +
> +  * The previous location on Github was an improperly choosen fork
> +    (see https://github.com/soedinglab/ffindex_soedinglab/issues/4)
> +    Here the version is now named "0.9.9.7+sog" (Saved On Github)
> +    to make it alphabethically later than the previous one.
> +
> + -- Andreas Tille mailto:ti...@debian.org>>
Wed, 19 Dec 2018 09:16:09 +0100
> +
>  ffindex (0.9.9.7+soedinglab+git20180802.74550c8-1) unstable;
urgency=medium
>
>    * Fix watch file (version should actually be
+git20171201.74550c8 but
> diff --git a/debian/watch b/debian/watch
> index 91b4f38..b47f123 100644
> --- a/debian/watch
> +++ b/debian/watch
> @@ -1,4 +1,4 @@
>  version=4
>
> -opts="mode=git,pretty=0.9.9.7+soedinglab+git%cd.%h" \
> - https://github.com/soedinglab/ffindex_soedinglab.git HEAD
> +opts="mode=git,pretty=0.9.9.7+sog+git%cd.%h" \
> + https://github.com/ahcm/ffindex.git HEAD
>
>
>
> Upstream at github.com/ahcm/ffindex
 was extremely quick to tag a
> release and so it is at least active.
>
> Steffen, was your pick intentional or did you just stumbled by
chance
> over the other fork?  Are you OK with reverting to the old code?
>
> Kind regards
>
>       Andreas.
>
> PS: I reported the segfault issue to the according fork anyway
> https://github.com/soedinglab/ffindex_soedinglab/issues/7
>
>
> --
> http://fam-tille.de
>
>

-- 
http://fam-tille.de




--
Michael R. Crusoe
Co-founder & Lead, Common Workflow Language project 


Direktorius, VšĮ "Darbo eigos", Vilnius, Lithuania
https://orcid.org/-0002-2961-9670 


m...@commonwl.org 
+1 480 627 9108 / +370 653 11125

Bug#918316: nocache: FTBFS in sid

[Santiago Vila]

Package: src:nocache
Version: 1.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
   dh_auto_build -a
make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -o cachedel cachedel.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -o cachestats cachestats.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -fPIC -c -o nocache.o nocache.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -fPIC -c -o fcntl_helpers.o fcntl_helpers.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -fPIC -c -o pageinfo.o pageinfo.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -pthread -shared -Wl,-soname,nocache.so -o nocache.so 
nocache.o fcntl_helpers.o pageinfo.o -ldl
sed 's!##libdir##!$(dirname "$0")!' nocache
chmod a+x nocache
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
## #916415
timeout 11 ./nocache apt show coreutils 1>>/dev/null

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

make[1]: *** [debian/rules:21: override_dh_auto_test] Error 124
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


To be sure, I have tried to build the package 151 times on 8 different machines
and it failed 151 times. Here are the full build logs:

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

A very similar failure happened here in mipsel, a release architecture:

https://buildd.debian.org/status/fetch.php?pkg=nocache&arch=mipsel&ver=1.1-1&stamp=1546582253&raw=0

If you need help to reproduce this, please say so, I would gladly offer access 
to a system
where this seems to happen all the time.

Thanks.

Bug#918249: marked as done (doc-rfc: please switch to ps2txt for testsuite)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 22:35:43 +
with message-id 
and subject line Bug#918249: fixed in doc-rfc 20181229-2
has caused the Debian Bug report #918249,
regarding doc-rfc: please switch to ps2txt for testsuite
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.)


-- 
918249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doc-rfc
Version: 20181229-1
Severity: serious
tags: patch

Hello, the following Ubuntu patch [1] does the switch from pstotext (really 
unmaintained, and out from testing),
to ps2txt, part of src:ghostscript.

I'm filing this bug as "serious", because it means that the autopkgtestsuite is 
not runnable with a "testing" codebase
(since pstotext is out from buster)

[1] 
https://launchpadlibrarian.net/364763538/doc-rfc_20170121-1_20170121-1ubuntu1.diff.gz

I'm also committing the fix for this bug on git, feel free to upload it (or ask 
me to do it)!

thanks for considering it

G.
--- End Message ---
--- Begin Message ---
Source: doc-rfc
Source-Version: 20181229-2

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

Debian distribution maintenance software
pp.
Iustin Pop  (supplier of updated doc-rfc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Jan 2019 22:56:31 +0100
Source: doc-rfc
Binary: doc-rfc doc-rfc-std doc-rfc-std-proposed doc-rfc-old-std 
doc-rfc-fyi-bcp doc-rfc-experimental doc-rfc-misc doc-rfc-informational 
doc-rfc-others
Architecture: source all
Version: 20181229-2
Distribution: unstable
Urgency: medium
Maintainer: Iustin Pop 
Changed-By: Iustin Pop 
Description:
 doc-rfc- RFC documents metapackage
 doc-rfc-experimental - Experimental RFCs
 doc-rfc-fyi-bcp - FYI and BCP RFCs
 doc-rfc-informational - Informational RFCs
 doc-rfc-misc - Historic and draft RFCs
 doc-rfc-old-std - Old Standard RFCs
 doc-rfc-others - Old experimental and unclassified RFCs
 doc-rfc-std - Standard RFCs
 doc-rfc-std-proposed - Proposed Standard RFCs
Closes: 895541 918249
Changes:
 doc-rfc (20181229-2) unstable; urgency=medium
 .
   [ Till Kamppeter  ]
   * In the autopkgtest replaced the call of pstotext by ps2txt
 as pstotext upstream is unmaintained for years and stopped
 working with Ghostscript whereas ps2txt is part of ghostscript
 (LP: #1762778, Closes: #918249, Closes: #895541).
 .
   [ Gianfranco Costamagna ]
   * Commit the Ubuntu delta on Debian git.
 .
   [ Iustin Pop ]
   * Acknowledge semi-NMU, thanks a lot Gianfranco!
   * Restore rfc5771.txt deleted by quilt (misbehaviour), to make future
 merges with upstream easier.
Checksums-Sha1:
 220ccaa9a593a5472a9ea9d53e17e05ea345ab39 2881 doc-rfc_20181229-2.dsc
 885a2f54d6dea6749b3e3ede920def5ba735c95f 20556 doc-rfc_20181229-2.debian.tar.xz
 48356b08bc35ca2a154c9af8f9f915cb42f76703 6999424 
doc-rfc-experimental_20181229-2_all.deb
 b4fe033d6dde6989e2f7ff66e6fd5ab935091c6b 4314220 
doc-rfc-fyi-bcp_20181229-2_all.deb
 3550fff96aa72d7dc28192797cf905944526d800 39128808 
doc-rfc-informational_20181229-2_all.deb
 e33f1a2cdaf0414924ed71eae1e7d263c727a7d7 8319876 
doc-rfc-misc_20181229-2_all.deb
 518c0a19844dc877cf9b97c133f1e76129aed09f 17075240 
doc-rfc-old-std_20181229-2_all.deb
 cfe9dcc56f445e146567e03a52bfbf821e2de39c 59903172 
doc-rfc-others_20181229-2_all.deb
 e2ee17decff953de8d16978a7d62f5ce801936ba 45075956 
doc-rfc-std-proposed_20181229-2_all.deb
 450c94df4e137c7484b37578daebb29fdd95800e 5160912 doc-rfc-std_20181229-2_all.deb
 76eb589ebc463587c807d92c02e8d007c87c8d1e 8904 doc-rfc_20181229-2_all.deb
 b9e57d31d1dc5ba617eb7101191bcd4d5090ca01 10248 
doc-rfc_20181229-2_amd64.buildinfo
Checksums-Sha256:
 ca21e7a75045510c30322d7c2672cea7fd2e09a474cd7421de6942a60bc3ddb2 2881 
doc-rfc_20181229-2.dsc
 81bfa99ecd88cbcff9a850c361a6cbe576157da101d4d256cdd635fed8be9c9f 20556 
doc-rfc_20181229-2.debian.tar.xz
 fb7e726d694055ae4fd45b62e5d4f8dc083c218d72c64299084053d137144a90 6999424 
doc-rfc-experimental_20181229-2_all.deb
 21cdf2f6b805fd764f57065dcd6110039c3f5494b4

Processed: severity of 917083 is serious

[Debian Bug Tracking System]

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

> severity 917083 serious
Bug #917083 [mysql-workbench] mysql-workbench: Cannot Connect to Database: 
Unsupported option provided to mysql_options()
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: thfvgf

[Debian Bug Tracking System]

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

> forcemerge 918090 918217
Bug #918090 [src:theano] theano: C-optimized ops fail with "module 
'numpy.core.multiarray' has no attribute '_get_ndarray_c_version'"
Bug #918217 [src:theano] theano: autopkgtest fails with python-numpy 
(1:1.16.0~rc1-3)
Severity set to 'serious' from 'normal'
917323 was blocked by: 918204 918209 918201 918206 918207 918128 918208 918217 
918202 918214 918121 918210 918212 918213 917465
917323 was not blocking any bugs.
Removed blocking bug(s) of 917323: 918217
Added tag(s) patch.
Merged 918090 918217
>
End of message, stopping processing here.

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

Processed: severity of 774527 is grave

[Debian Bug Tracking System]

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

> severity 774527 grave
Bug #774527 [arc] arc: directory traversal
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#918312: salt-{master,minion} fail to purge

[Adrian Bunk]

Source: salt
Version: 2018.3.3+dfsg1-1
Severity: serious
Control: affects -1 salt-master salt-minion

https://piuparts.debian.org/sid/source/s/salt.html

  Purging configuration files for salt-master (2018.3.3+dfsg1-1) ...
  rmdir: failed to remove '/var/lib/salt/pki': No such file or directory
  dpkg: error processing package salt-master (--purge):
   installed salt-master package post-removal script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   salt-master

  Purging configuration files for salt-minion (2018.3.3+dfsg1-1) ...
  rmdir: failed to remove '/var/lib/salt/pki': No such file or directory
  rmdir: failed to remove '/var/lib/salt': No such file or directory
  dpkg: error processing package salt-minion (--purge):
   installed salt-minion package post-removal script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   salt-minion

Processed: salt-{master,minion} fail to purge

[Debian Bug Tracking System]

Processing control commands:

> affects -1 salt-master salt-minion
Bug #918312 [src:salt] salt-{master,minion} fail to purge
Added indication that 918312 affects salt-master and salt-minion

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

Bug#907624: What ffindex do we want to package

[Andreas Tille]

On Fri, Jan 04, 2019 at 07:17:24PM +0200, Michael Crusoe wrote:
> I think 0.9.9.7+sog+git20160415.14274c9-1 is the source of the recent FTBFS
> of hhsuite: https://bugs.debian.org/917495 as our packaged version is
> missing the "ffsort_index" function.
> 
> The hh-suite github repo contains a submodule pointing at their fork of
> ffindex at ~ 2017-06-01:
> https://github.com/soedinglab/hh-suite/tree/v3.0-beta.3/lib  →
> https://github.com/soedinglab/ffindex_soedinglab/tree/360e4176ece531be34a94298c808349916d016ac
> 
> I suggest that we package it as part of hhsuite until another package needs
> it.
> 
> hhsuite does provide  "*-Source*" packages that include ffindex, so we
> wouldn't need a multi-source build.

By any means just do something sensible.  I'm way to less educated about
this software and just got my fingers dirty with it since nobody else
cared about the (other!) bugs.
 
Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#918249: doc-rfc: please switch to ps2txt for testsuite

[Iustin Pop]

On 2019-01-04 21:26:03, Iustin Pop wrote:
> On 2019-01-04 20:16:40, Gianfranco Costamagna wrote:
> >  thanks  for having a look! I was wondering about something more subtle and 
> > behind the scenes :)
> > btw for some reasons the ci is not running the testsuite on 
> > unstablehttps://ci.debian.net/packages/d/doc-rfc/probably because testing 
> > is sad?
> > I don't know, I tried the -2 I committed on git on debomatic and the 
> > autopkgtestsuite was good :)
> 
> Hrmm, I thought I'd get an email about this, but no, seems I have to
> look manually at ddpo. One more thing to add to my notes…
> 
> I'll try to sort this out soon, before the soft freeze. Not sure I can
> finish everything this weekend.

This is very weird. My procedure for uploading a new package includes
running an autopkgtest manually, and I see now that this fails (on the
version I uploaded), I don't know why I missed it before the most recent
upload. Unfortunately I don't have a fully automated
'build-check-upload' pipeline, so most likely human error/oversight.

In any case, I'll be more careful in the future. New version is
uploading right now.

thanks,
iustin

Processed: severity of 918149 is serious

[Debian Bug Tracking System]

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

> severity 918149 serious
Bug #918149 [terminator] terminator: Unstated Dependency On `dbus-x11`
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 918272

[Debian Bug Tracking System]

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

> tags 918272 + ftbfs
Bug #918272 [src:staden] staden build-dependencies unsatisfiable.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: severity of 918272 is serious

[Debian Bug Tracking System]

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

> severity 918272 serious
Bug #918272 [src:staden] staden build-dependencies unsatisfiable.
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#918247: marked as done (camlimages FTBFS on ocaml bytecode architectures)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 21:34:21 +
with message-id 
and subject line Bug#918247: fixed in camlimages 1:4.2.6-2
has caused the Debian Bug report #918247,
regarding camlimages FTBFS on ocaml bytecode architectures
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.)


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

https://buildd.debian.org/status/package.php?p=camlimages&suite=sid

...
--- Checking if ocamldep understands -modules... (yes)
*** omake: finished reading OMakefiles (2.56 sec)
*** omake: 36/516 targets are up to date
*** omake: failed (3.10 sec, 0/0 scans, 0/0 rules, 22/237 digests)
*** omake error:
   File /usr/lib/omake/build/OCaml.om: line 491, characters 12-24
   Uncaught Exception:
  You are trying to build OCaml native code file: region.cmx
  However, the NATIVE_ENABLED flag is not set.
  Include the following definition in your OMakefile
  if you really want to build this file.
 NATIVE_ENABLED = true
make[1]: *** [debian/rules:22: override_dh_auto_build] Error 123
--- End Message ---
--- Begin Message ---
Source: camlimages
Source-Version: 1:4.2.6-2

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 918...@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 generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 04 Jan 2019 22:37:37 +0200
Source: camlimages
Binary: libcamlimages-ocaml libcamlimages-ocaml-dev libcamlimages-ocaml-doc
Architecture: source amd64 all
Version: 1:4.2.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Kyle Robbertze 
Description:
 libcamlimages-ocaml - OCaml image processing library (Runtime library)
 libcamlimages-ocaml-dev - OCaml image processing library (Development package)
 libcamlimages-ocaml-doc - OCaml CamlImages library documentation
Closes: 918247
Changes:
 camlimages (1:4.2.6-2) unstable; urgency=medium
 .
   * Fix bytecode compilation (Closes: #918247)
Checksums-Sha1:
 cc7a7c726e5c34ca9e92cf82305060c0b8d4834d 2423 camlimages_4.2.6-2.dsc
 a2308f9f019f24f9f2ae5a252197c25e84571b03 8720 camlimages_4.2.6-2.debian.tar.xz
 e3c024a65c1fa3def14b417ed49f9b092c04be07 16057 
camlimages_4.2.6-2_amd64.buildinfo
 9c634e732be631eb1d5e93cc06eda3b6abe2574d 8428 
libcamlimages-ocaml-dbgsym_4.2.6-2_amd64.deb
 fa7b7272141ec837fbb54639fa12c556ed4e3aae 46104 
libcamlimages-ocaml-dev-dbgsym_4.2.6-2_amd64.deb
 e5855ec5d8078ce71d901432359d053658e242a7 857340 
libcamlimages-ocaml-dev_4.2.6-2_amd64.deb
 3b800d1554703113a6fd24fb18c7f160ce352f31 2428944 
libcamlimages-ocaml-doc_4.2.6-2_all.deb
 2c25e208ec0e95bba0adaeb1784b942fc1530a19 34996 
libcamlimages-ocaml_4.2.6-2_amd64.deb
Checksums-Sha256:
 3c82842ea0a0ff47abca87b237f02a24062ac63958bf63634c12da2f7932bccb 2423 
camlimages_4.2.6-2.dsc
 eb39566c485db985367f233a5648fda842da05f1a631f1256d553a5be3738b9f 8720 
camlimages_4.2.6-2.debian.tar.xz
 e4b1a00a15e4bdab7e4a6e6ae5f20c7783e99478313bff5ae7e66cc5eb4c6a8b 16057 
camlimages_4.2.6-2_amd64.buildinfo
 1ad083d5fd39de0a0bc11b18c08a7e7e30482da96d1b040bd6a2f577dc4dee14 8428 
libcamlimages-ocaml-dbgsym_4.2.6-2_amd64.deb
 35a46f506eece2a520a614ea093137b38b5fffdcab9e469acbc1b298e5aa78c7 46104 
libcamlimages-ocaml-dev-dbgsym_4.2.6-2_amd64.deb
 f0d460766151596feba266170cab47a73cebf865d6a4b2acc58e38b5e2703bd3 857340 
libcamlimages-ocaml-dev_4.2.6-2_amd64.deb
 4be0af2408c8e5dfcf0fb2397286cd072269da5b0fbabdaf58b67b272368fc0d 2428944 
libcamlimages-ocaml-doc_4.2.6-2_all.deb
 8b3e132754c893edf9daa64d01ace9ddf6cf3e25bc08180c4fe53d9d34a8e940 34996 
libcamlimages-ocaml_4.2.6-2_amd64.deb
Files:
 6ad57d6e5db48c905d877711dfb80439 2423 devel optional camlimages_4.2.6-2.dsc
 3b2910913cc4ff3d588f872b3e016240 8720 devel optional 
camlimages_4.2.6-2.debian.tar.xz
 60ce551c5e08b3cbec1e12638d2039f9 16057 devel optional 
camlimages_4.2.6-2_amd64.buildinfo
 0d3658fca1

Bug#918303: tmuxinator build depends on ruby-awesome-print that is currently not in buster

[Adrian Bunk]

Source: tmuxinator
Version: 0.12.0-3
Severity: serious
Tags: ftbfs
Control: block -1 by 888119

tmuxinator build depends on ruby-awesome-print
that is currently not in buster due to #888119.

Processed: tmuxinator build depends on ruby-awesome-print that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 888119
Bug #918303 [src:tmuxinator] tmuxinator build depends on ruby-awesome-print 
that is currently not in buster
918303 was not blocked by any bugs.
918303 was not blocking any bugs.
Added blocking bug(s) of 918303: 888119

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

Bug#918300: ruby-compat-resource build depends on ruby-cheffish that is currently not in buster

[Adrian Bunk]

Source: ruby-compat-resource
Version: 12.10.5-1
Severity: serious
Tags: ftbfs buster sid
Control: block -1 by 912246

ruby-compat-resource build depends on ruby-cheffish
that is currently not in buster due to #912246.

Processed: ruby-omniauth-cas3 build depends on ruby-awesome-print that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 888119
Bug #918302 [src:ruby-omniauth-cas3] ruby-omniauth-cas3 build depends on 
ruby-awesome-print that is currently not in buster
918302 was not blocked by any bugs.
918302 was not blocking any bugs.
Added blocking bug(s) of 918302: 888119

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

Processed: ruby-compat-resource build depends on ruby-cheffish that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 912246
Bug #918300 [src:ruby-compat-resource] ruby-compat-resource build depends on 
ruby-cheffish that is currently not in buster
918300 was not blocked by any bugs.
918300 was not blocking any bugs.
Added blocking bug(s) of 918300: 912246

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

Bug#918302: ruby-omniauth-cas3 build depends on ruby-awesome-print that is currently not in buster

[Adrian Bunk]

Source: ruby-omniauth-cas3
Version: 1.1.4-2
Severity: serious
Tags: ftbfs
Control: block -1 by 888119

ruby-omniauth-cas3 build depends on ruby-awesome-print
that is currently not in buster due to #888119.

Processed: python-oslo.messaging build depends on python-pyngus that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 896117 896507 897841
Bug #918299 [src:python-oslo.messaging] python-oslo.messaging build depends on 
python-pyngus that is currently not in buster
918299 was not blocked by any bugs.
918299 was not blocking any bugs.
Added blocking bug(s) of 918299: 897841, 896507, and 896117

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

Bug#918299: python-oslo.messaging build depends on python-pyngus that is currently not in buster

[Adrian Bunk]

Source: python-oslo.messaging
Version: 8.1.0-3
Severity: serious
Tags: ftbfs
Control: block -1 by 896117 896507 897841

python-oslo.messaging build depends on python-pyngus that is currently
not in buster due to #896117, #896507 and #897841.

Bug#918297: php-services-weather build depends on php-db that is currently not in buster

[Adrian Bunk]

Source: php-services-weather
Version: 1.4.7-4
Severity: serious
Tags: ftbfs buster sid
Control: block -1 by 889532

php-services-weather build depends on php-db that is currently
not in buster due to #889532.

Processed: php-services-weather build depends on php-db that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 889532
Bug #918297 [src:php-services-weather] php-services-weather build depends on 
php-db that is currently not in buster
918297 was not blocked by any bugs.
918297 was not blocking any bugs.
Added blocking bug(s) of 918297: 889532

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

Processed: php-log build depends on php-db that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 889532
Bug #918296 [src:php-log] php-log build depends on php-db that is currently not 
in buster
918296 was not blocked by any bugs.
918296 was not blocking any bugs.
Added blocking bug(s) of 918296: 889532

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

Bug#918296: php-log build depends on php-db that is currently not in buster

[Adrian Bunk]

Source: php-log
Version: 1.12.9-2
Severity: serious
Tags: ftbfs buster sid
Control: block -1 by 889532

php-log build depends on php-db that is currently
not in buster due to #889532.

Processed: openstreetmap-carto build depends on node-carto that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 872547
Bug #918294 [src:openstreetmap-carto] openstreetmap-carto build depends on 
node-carto that is currently not in buster
918294 was not blocked by any bugs.
918294 was not blocking any bugs.
Added blocking bug(s) of 918294: 872547

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

Bug#918294: openstreetmap-carto build depends on node-carto that is currently not in buster

[Adrian Bunk]

Source: openstreetmap-carto
Version: 2.45.1-1
Severity: serious
Tags: ftbfs buster sid
Control: block -1 by 872547

openstreetmap-carto build depends on node-carto that
is currently not in buster due to #872547.

Bug#918292: node-sshpk build depends on node-temp that is currently not in buster

[Adrian Bunk]

Source: node-sshpk
Version: 1.13.1+dfsg-1
Severity: serious
Tags: ftbfs
Control: block -1 by 834915

node-sshpk build depends on node-temp that is currently
not in buster due to #834915.

Processed: node-sshpk build depends on node-temp that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 834915
Bug #918292 [src:node-sshpk] node-sshpk build depends on node-temp that is 
currently not in buster
918292 was not blocked by any bugs.
918292 was not blocking any bugs.
Added blocking bug(s) of 918292: 834915

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

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

[Kyle Robbertze]

Control: tag -1 pending

Hello,

Bug #918247 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/a12bdc446c41611fe4fbcbee786f37bae9b78fed


Enable bytecode compilation (Closes: #918247)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918247

Processed: node-xmpp build depends on node-node-stringprep that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 895029
Bug #918293 [src:node-xmpp] node-xmpp build depends on node-node-stringprep 
that is currently not in buster
918293 was not blocked by any bugs.
918293 was not blocking any bugs.
Added blocking bug(s) of 918293: 895029

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

Processed: Bug #918247 in camlimages marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918247 [src:camlimages] camlimages FTBFS on ocaml bytecode architectures
Added tag(s) pending.

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

Bug#918293: node-xmpp build depends on node-node-stringprep that is currently not in buster

[Adrian Bunk]

Source: node-xmpp
Version: 0.3.2-3
Severity: serious
Tags: ftbfs buster sid
Control: block -1 by 895029

node-xmpp build depends on node-node-stringprep that is currently
not in buster due to #895029.

Processed: node-postcss build depends on node-js-beautify that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 60 888903
Bug #918290 [src:node-postcss] node-postcss build depends on node-js-beautify 
that is currently not in buster
918290 was not blocked by any bugs.
918290 was not blocking any bugs.
Added blocking bug(s) of 918290: 60 and 888903

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

Bug#918290: node-postcss build depends on node-js-beautify that is currently not in buster

[Adrian Bunk]

Source: node-postcss
Version: 6.0.23-1
Severity: serious
Tags: ftbfs
Control: block -1 by 60 888903

node-postcss build depends on node-js-beautify
that is currently not in buster due to #60 and #888903.

Processed: node-autoprefixer build depends on node-js-beautify that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 60 888903
Bug #918289 [src:node-autoprefixer] node-autoprefixer build depends on 
node-js-beautify that is currently not in buster
918289 was not blocked by any bugs.
918289 was not blocking any bugs.
Added blocking bug(s) of 918289: 60 and 888903

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

Bug#918289: node-autoprefixer build depends on node-js-beautify that is currently not in buster

[Adrian Bunk]

Source: node-autoprefixer
Version: 7.2.5-1
Severity: serious
Tags: ftbfs
Control: block -1 by 60 888903

node-autoprefixer build depends on node-js-beautify
that is currently not in buster due to #60 and #888903.

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

[Sam Hartman]

So what's happening here is  that a k5_mutex_lock is getting  an invalid
argument error calling  a series of wrappers that basically all boil
down to pthread_mutex_lock.
So, basically somehow pthread_mutex_lock is getting passed a bad mutex.
This appears to be happening in the credentials cache code.

There are no thread support changes between 1.16.1 and 1.16.2.
There is one ccache related change which I'll include below related to
memory ccaches.
Do you know what type of credential cache  is being used here?

>From 6d784809fe07c2d5f60c1a692bcac08b0d40f0a7 Mon Sep 17 00:00:00 2001
From: Greg Hudson 
Date: Sun, 1 Jul 2018 00:12:25 -0400
Subject: [PATCH] Fix bugs with concurrent use of MEMORY ccaches

A memory ccache iterator stores an alias into the cache object's
linked list of credentials.  If the cache is reinitialized while the
iterator is active, the alias becomes invalid.  Also, multiple handles
referencing the same memory ccache all use aliases to the same data
object; if one of the handles is destroyed, the other contains a
dangling pointer.

Fix the first issue by adding a generation counter to the cache and to
cursors, incremented each time the cache is initialized or destroyed.
Check the generation on each cursor step and end the iteration if the
list was invalidated.  Fix the second issue by adding a reference
count to the cache object, counting one reference for the table slot
and one for each open handle.  Empty the cache object on each destroy
operation, but only release the object when the last handle to it is
destroyed or closed.

Add regression tests for the two issues to t_cc.c.

The first issue was reported by Sorin Manolache.

(cherry picked from commit 146dadec8fe7ccc4149eb2e3f577cc320aee6efb)

ticket: 8202
version_fixed: 1.16.2
---
 src/lib/krb5/ccache/cc_memory.c | 164 +---
 src/lib/krb5/ccache/t_cc.c  |  51 +
 2 files changed, 154 insertions(+), 61 deletions(-)

diff --git a/src/lib/krb5/ccache/cc_memory.c b/src/lib/krb5/ccache/cc_memory.c
index c5425eb3ae..8cdaff7fb3 100644
--- a/src/lib/krb5/ccache/cc_memory.c
+++ b/src/lib/krb5/ccache/cc_memory.c
@@ -102,18 +102,20 @@ extern krb5_error_code krb5_change_cache (void);
 typedef struct _krb5_mcc_link {
 struct _krb5_mcc_link *next;
 krb5_creds *creds;
-} krb5_mcc_link, *krb5_mcc_cursor;
+} krb5_mcc_link;
 
 /* Per-cache data header.  */
 typedef struct _krb5_mcc_data {
 char *name;
 k5_cc_mutex lock;
 krb5_principal prin;
-krb5_mcc_cursor link;
+krb5_mcc_link *link;
 krb5_timestamp changetime;
 /* Time offsets for clock-skewed clients.  */
 krb5_int32 time_offset;
 krb5_int32 usec_offset;
+int refcount;   /* One for the table slot, one per handle */
+int generation; /* Incremented at each initialize */
 } krb5_mcc_data;
 
 /* List of memory caches.  */
@@ -122,6 +124,12 @@ typedef struct krb5_mcc_list_node {
 krb5_mcc_data *cache;
 } krb5_mcc_list_node;
 
+/* Iterator over credentials in a memory cache. */
+struct mcc_cursor {
+int generation;
+krb5_mcc_link *next_link;
+};
+
 /* Iterator over memory caches.  */
 struct krb5_mcc_ptcursor_data {
 struct krb5_mcc_list_node *cur;
@@ -132,7 +140,23 @@ static krb5_mcc_list_node *mcc_head = 0;
 
 static void update_mcc_change_time(krb5_mcc_data *);
 
-static void krb5_mcc_free (krb5_context context, krb5_ccache id);
+/* Remove creds from d, invalidate any existing cursors, and unset the client
+ * principal.  The caller is responsible for locking. */
+static void
+empty_mcc_cache(krb5_context context, krb5_mcc_data *d)
+{
+krb5_mcc_link *curr, *next;
+
+for (curr = d->link; curr != NULL; curr = next) {
+next = curr->next;
+krb5_free_creds(context, curr->creds);
+free(curr);
+}
+d->link = NULL;
+d->generation++;
+krb5_free_principal(context, d->prin);
+d->prin = NULL;
+}
 
 /*
  * Modifies:
@@ -150,16 +174,12 @@ krb5_mcc_initialize(krb5_context context, krb5_ccache id, 
krb5_principal princ)
 {
 krb5_os_context os_ctx = &context->os_context;
 krb5_error_code ret;
-krb5_mcc_data *d;
+krb5_mcc_data *d = id->data;
 
-d = (krb5_mcc_data *)id->data;
 k5_cc_mutex_lock(context, &d->lock);
+empty_mcc_cache(context, d);
 
-krb5_mcc_free(context, id);
-
-d = (krb5_mcc_data *)id->data;
-ret = krb5_copy_principal(context, princ,
-  &d->prin);
+ret = krb5_copy_principal(context, princ, &d->prin);
 update_mcc_change_time(d);
 
 if (os_ctx->os_flags & KRB5_OS_TOFFSET_VALID) {
@@ -185,61 +205,59 @@ krb5_mcc_initialize(krb5_context context, krb5_ccache id, 
krb5_principal princ)
 krb5_error_code KRB5_CALLCONV
 krb5_mcc_close(krb5_context context, krb5_ccache id)
 {
-free(id);
-return KRB5_OK;
-}
-
-static void
-krb5_mcc_free(krb5_context context, krb5_ccache id)
-{
-krb5_mcc_cursor curr,next;
-krb5_mcc_data *d;
+krb

Bug#918288: nipype build depends on python-nipy that is currently not in buster

[Adrian Bunk]

Source: nipype
Version: 1.1.3-1
Severity: serious
Tags: ftbfs
Control: block -1 by 906388

nipype build depends on python-nipy that is currently
not in buster due to #906388.

Processed: nipype build depends on python-nipy that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 906388
Bug #918288 [src:nipype] nipype build depends on python-nipy that is currently 
not in buster
918288 was not blocked by any bugs.
918288 was not blocking any bugs.
Added blocking bug(s) of 918288: 906388

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

Bug#918287: linux-patch-grsecurity2 build depends on dh-kpatches that is currently not in buster

[Adrian Bunk]

Source: linux-patch-grsecurity2
Version: 3.1+4.9.11-201702181444-1
Severity: serious
Tags: ftbfs
Control: block -1 by 876892

linux-patch-grsecurity2 build depends on dh-kpatches
that is currently not in buster due to #876892.

Processed: linux-patch-debianlogo build depends on dh-kpatches that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 876892
Bug #918286 [src:linux-patch-debianlogo] linux-patch-debianlogo build depends 
on dh-kpatches that is currently not in buster
918286 was not blocked by any bugs.
918286 was not blocking any bugs.
Added blocking bug(s) of 918286: 876892

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

Processed: linux-patch-grsecurity2 build depends on dh-kpatches that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 876892
Bug #918287 [src:linux-patch-grsecurity2] linux-patch-grsecurity2 build depends 
on dh-kpatches that is currently not in buster
918287 was not blocked by any bugs.
918287 was not blocking any bugs.
Added blocking bug(s) of 918287: 876892

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

Bug#918286: linux-patch-debianlogo build depends on dh-kpatches that is currently not in buster

[Adrian Bunk]

Source: linux-patch-debianlogo
Version: 1.16
Severity: serious
Tags: buster sid ftbfs
Control: block -1 by 876892

linux-patch-debianlogo build depends on dh-kpatches
that is currently not in buster due to #876892.

Processed: librdf-query-client-perl build depends on libhttp-lrdd-perl that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 750946
Bug #918283 [src:librdf-query-client-perl] librdf-query-client-perl build 
depends on libhttp-lrdd-perl that is currently not in buster
918283 was not blocked by any bugs.
918283 was not blocking any bugs.
Added blocking bug(s) of 918283: 750946

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

Processed: librdf-trine-serializer-rdfa-perl build depends on librdf-rdfa-parser-perl that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 750946
Bug #918284 [src:librdf-trine-serializer-rdfa-perl] 
librdf-trine-serializer-rdfa-perl build depends on librdf-rdfa-parser-perl that 
is currently not in buster
918284 was not blocked by any bugs.
918284 was not blocking any bugs.
Added blocking bug(s) of 918284: 750946

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

Bug#918284: librdf-trine-serializer-rdfa-perl build depends on librdf-rdfa-parser-perl that is currently not in buster

[Adrian Bunk]

Source: librdf-trine-serializer-rdfa-perl
Version: 0.100-1
Severity: serious
Tags: ftbfs
Control: block -1 by 750946

librdf-trine-serializer-rdfa-perl build depends on librdf-rdfa-parser-perl
that is currently not in buster due to #750946.

Bug#918283: librdf-query-client-perl build depends on libhttp-lrdd-perl that is currently not in buster

[Adrian Bunk]

Source: librdf-query-client-perl
Version: 0.114-1
Severity: serious
Tags: ftbfs buster sid
Control: block -1 by 750946

librdf-query-client-perl build depends on libhttp-lrdd-perl
that is currently not in buster due to #750946.

Bug#918282: libokhttp-java build depends on libandroid-23-java that is currently not in buster

[Adrian Bunk]

Source: libokhttp-java
Version: 3.12.1-1
Severity: serious
Tags: ftbfs
Control: block -1 by 894285

libokhttp-java build depends on libandroid-23-java that is
currently not in buster due to #894285.

Processed: libokhttp-java build depends on libandroid-23-java that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 894285
Bug #918282 [src:libokhttp-java] libokhttp-java build depends on 
libandroid-23-java that is currently not in buster
918282 was not blocked by any bugs.
918282 was not blocking any bugs.
Added blocking bug(s) of 918282: 894285

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

Bug#918281: openscenegraph-3.4 build depends on cruft package libcoin80-dev

[Adrian Bunk]

Source: openscenegraph-3.4
Version: 3.4.1+dfsg1-4
Severity: serious
Tags: ftbfs

openscenegraph-3.4 build depends on libcoin80-dev
that is no longer built by src:coin3.

Processed: khal build depends on vdirsyncer that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 909996
Bug #918279 [src:khal] khal build depends on vdirsyncer that is currently not 
in buster
918279 was not blocked by any bugs.
918279 was not blocking any bugs.
Added blocking bug(s) of 918279: 909996

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

Processed: koji build depends on python-qpid-proton that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 896117 896507 897841
Bug #918280 [src:koji] koji build depends on python-qpid-proton that is 
currently not in buster
918280 was not blocked by any bugs.
918280 was not blocking any bugs.
Added blocking bug(s) of 918280: 896117, 897841, and 896507

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

Bug#918276: vlc: When you open VLC 3.0.5-1 any .mp4 file a Debian 9.6 hangs

[Sebastian Ramacher]

Control: severity -1 important
Control: tags -1 = moreinfo

On 2019-01-04 23:35:34, Сергей Фёдоров wrote:
> Package: vlc
> Version: 3.0.5-1
> Severity: critical
> Tags: a11y
> Justification: breaks the whole system
>  
> When I install vlc 3.0.3-1-0+deb9u1 any .mp4 file is opening and showing
> normally. But when i install vlc 3.0.5-1 a any attempt open any .mp4 file
> a Debian 9.6 hangs. A Debian 9.6 hangs for all vlc version above
> 3.0.3-1-0+deb9u1.

Please provide a a log of vlc -vv when the it hangs. Please also let us know if
you use hardware decoding, if you have the corresponding drivers installed and
which type of GPU you use.

Cheers


>  
> --- vlc 3.0.5-1 -
>  
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>  
> Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), 
> LANGUAGE=ru_RU.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>  
> Versions of packages vlc depends on:
> ii  vlc-bin  3.0.5-1
> ii  vlc-plugin-base  3.0.5-1
> ii  vlc-plugin-qt3.0.5-1
> ii  vlc-plugin-video-output  3.0.5-1
>  
> Versions of packages vlc recommends:
> ii  vlc-l10n  3.0.5-1
> ii  vlc-plugin-notify  3.0.5-1
> ii  vlc-plugin-samba  3.0.5-1
> ii  vlc-plugin-skins2  3.0.5-1
> ii  vlc-plugin-video-splitter  3.0.5-1
> ii  vlc-plugin-visualization  3.0.5-1
>  
> vlc suggests no packages.
>  
> Versions of packages libvlc-bin depends on:
> ii  libc62.28-4
> ii  libvlc5  3.0.5-1
>  
> Versions of packages libvlc5 depends on:
> ii  libc62.28-4
> ii  libvlccore9  3.0.5-1
>  
> Versions of packages libvlc5 recommends:
> ii  libvlc-bin  3.0.5-1
>  
> Versions of packages vlc-bin depends on:
> ii  libc6  2.28-4
> ii  libvlc-bin  3.0.5-1
> ii  libvlc53.0.5-1
>  
> Versions of packages vlc-plugin-base depends on:
> ii  liba52-0.7.40.7.4-19
> ii  libaom0  1.0.0-3
> ii  libarchive133.3.3-2
> ii  libaribb24-01.0.3-2
> ii  libasound2  1.1.7-2
> ii  libass9  1:0.14.0-2
> ii  libavahi-client30.7-4+b1
> ii  libavahi-common30.7-4+b1
> ii  libavc1394-00.5.4-5
> ii  libavcodec587:4.1-1
> ii  libavformat587:4.1-1
> ii  libavutil56  7:4.1-1
> ii  libbasicusageenvironment12018.11.26-1
> ii  libbluray2  1:1.0.2-3
> ii  libc62.28-4
> ii  libcairo21.16.0-2
> ii  libcddb21.3.2-6
> ii  libchromaprint1  1.4.3-2+b1
> ii  libcrystalhd31:0.0~git20110715.fdd2f19-13
> ii  libdbus-1-3  1.12.12-1
> ii  libdc1394-222.2.5-1
> ii  libdca0  0.0.6-1
> ii  libdvbpsi10  1.3.2-1
> ii  libdvdnav4  6.0.0-1
> ii  libdvdread4  6.0.0-1
> ii  libebml4v5  1.3.6-2
> ii  libfaad22.8.8-1
> ii  libflac81.3.2-3
> ii  libfontconfig1  2.13.1-2
> ii  libfreetype62.9.1-3
> ii  libfribidi0  1.0.5-3
> ii  libgcc1  1:8.2.0-13
> ii  libgcrypt20  1.8.4-4
> ii  libglib2.0-02.58.2-3
> ii  libgnutls30  3.6.5-2
> ii  libgpg-error01.33-3
> ii  libgroupsock82018.11.26-1
> ii  libharfbuzz0b2.3.0-1
> ii  libixml101:1.8.4-2
> ii  libjpeg62-turbo  1:1.5.2-2+b1
> ii  libkate10.4.1-8
> ii  liblirc-client0  0.10.1-4
> ii  liblivemedia64  2018.11.26-1
> ii  liblua5.2-0  5.2.4-1.1+b2
> ii  libmad0  0.15.1b-9
> ii  libmatroska6v5  1.4.9-1
> ii  libmicrodns00.0.10-1
> ii  libmpcdec6  2:0.1~r495-1+b2
> ii  libmpeg2-4  0.5.1-8
> ii  libmpg123-0  1.25.10-2
> ii  libmtp9  1.1.13-1.1
> ii  libncursesw66.1+20181013-1
> ii  libnfs112.0.0-1~exp1
> ii  libogg0  1.3.2-1+b1
> ii  libopenmpt-modplug1  0.4.0-1
> ii  libopus0   

Bug#915502: marked as done (feedreader: Feedreader dies while updating feeds from a tt-rss instance)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 20:42:22 +
with message-id 
and subject line Bug#915502: fixed in feedreader 2.6.1-1
has caused the Debian Bug report #915502,
regarding feedreader: Feedreader dies while updating feeds from a tt-rss 
instance
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.)


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

Dear Maintainer,

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

Trying to update feeds from a tt-rss instance on a seerver feedreader dies with
this error in terminal:

(process:8852): GLib-DEBUG (recursed): posix_spawn avoided (fd close requested)
Error while executing 'addr2line -f -e /usr/bin/feedreader 0x7ffad2c392f1':
Troppi file aperti
Something went very wrong. Your stacktrace cannot be displayed
An error occurred (SIGABRT)
   The reason is likely a failed assertion (assert...).
   Note: no file path and line numbers can be retrieved. Are you sure you added
-g -X -rdynamic to valac command line?


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



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

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

Versions of packages feedreader depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-1
ii  libc62.27-8
ii  libcairo21.16.0-1
ii  libcurl4 7.62.0-1
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
ii  libgee-0.8-2 0.20.1-1
ii  libglib2.0-0 2.58.1-2
ii  libgoa-1.0-0b3.30.0-1
ii  libgstreamer-plugins-base1.0-0   1.14.4-1
ii  libgstreamer1.0-01.14.4-1
ii  libgtk-3-0   3.24.1-2
ii  libjson-glib-1.0-0   1.4.4-1
ii  libpango-1.0-0   1.42.4-4
ii  libpeas-1.0-01.22.0-2+b1
ii  librest-0.7-00.8.1-1
ii  libsecret-1-00.18.6-3
ii  libsoup2.4-1 2.64.1-3
ii  libsqlite3-0 3.25.3-2
ii  libwebkit2gtk-4.0-37 2.22.4-1
ii  libxml2  2.9.4+dfsg1-7+b2

feedreader recommends no packages.

feedreader suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: feedreader
Source-Version: 2.6.1-1

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

Debian distribution maintenance software
pp.
Ulises Vitulli  (supplier of updated feedreader package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Jan 2019 09:23:27 -0300
Source: feedreader
Binary: feedreader
Architecture: source amd64
Version: 2.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Ulises Vitulli 
Changed-By: Ulises Vitulli 
Description:
 feedreader - simple client for online RSS services like tt-rss and others
Closes: 915502
Changes:
 feedreader (2.6.1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #915502).
   * Updated copyright files to reflect redistribution changes.
   * Refreshed local patch on typos.
   * Bump up standard versions (no changes required).
   * Added debian watch file.
Checksums-Sha1:
 81c21274e51e2aa6c1c0b1e7d20dab1a82f2bf98  feedreader_2.6.1-1.dsc
 7be23e4f6e19bb6f73aa974e3732e8e00687e772 812613 feedreader_2.6.1.orig.tar.gz
 b404f48000b2dea6538c483df20

Bug#918280: koji build depends on python-qpid-proton that is currently not in buster

[Adrian Bunk]

Source: koji
Version: 1.16.0-2
Severity: serious
Tags: ftbfs
Control: block -1 by 896117 896507 897841

koji build depends on python-qpid-proton that is currently
not in buster due to #896117, #896507 and #897841.

Bug#918279: khal build depends on vdirsyncer that is currently not in buster

[Adrian Bunk]

Source: khal
Version: 1:0.9.10-0.1
Severity: serious
Tags: ftbfs
Control: block -1 by 909996

khal build depends on vdirsyncer that is currently
not in buster due to #909996.

Processed: Re: Bug#918276: vlc: When you open VLC 3.0.5-1 any .mp4 file a Debian 9.6 hangs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #918276 [vlc] vlc: When you open VLC 3.0.5-1 any .mp4 file a Debian 9.6 
hangs
Severity set to 'important' from 'critical'
> tags -1 = moreinfo
Bug #918276 [vlc] vlc: When you open VLC 3.0.5-1 any .mp4 file a Debian 9.6 
hangs
Added tag(s) moreinfo; removed tag(s) a11y.

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

Processed: i8c build depends on python3-libi8x that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 875373
Bug #918278 [src:i8c] i8c build depends on python3-libi8x that is currently not 
in buster
918278 was not blocked by any bugs.
918278 was not blocking any bugs.
Added blocking bug(s) of 918278: 875373

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

Bug#918278: i8c build depends on python3-libi8x that is currently not in buster

[Adrian Bunk]

Source: i8c
Version: 0.0.6-1
Severity: serious
Tags: ftbfs
Control: block -1 by 875373

i8c build depends on python3-libi8x that is currently
not in buster due to #875373.

Bug#918277: cairocffi build depends on python3-xcffib that is currently not in buster

[Adrian Bunk]

Source: cairocffi
Version: 0.7.2-2.1
Severity: serious
Tags: ftbfs
Control: block -1 by 860739 892648 903619 917171

cairocffi build depends on python3-xcffib that is currently not
in buster due to #860739, #892648, #903619 and #917171.

Processed: cairocffi build depends on python3-xcffib that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 860739 892648 903619 917171
Bug #918277 [src:cairocffi] cairocffi build depends on python3-xcffib that is 
currently not in buster
918277 was not blocked by any bugs.
918277 was not blocking any bugs.
Added blocking bug(s) of 918277: 917171, 860739, 892648, and 903619

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

Bug#918276: vlc: When you open VLC 3.0.5-1 any .mp4 file a Debian 9.6 hangs

[Сергей Фёдоров]

Package: vlc
Version: 3.0.5-1
Severity: critical
Tags: a11y
Justification: breaks the whole system
 
When I install vlc 3.0.3-1-0+deb9u1 any .mp4 file is opening and showing
normally. But when i install vlc 3.0.5-1 a any attempt open any .mp4 file
a Debian 9.6 hangs. A Debian 9.6 hangs for all vlc version above
3.0.3-1-0+deb9u1.
 
--- vlc 3.0.5-1 -
 
-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
 
Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), 
LANGUAGE=ru_RU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
 
Versions of packages vlc depends on:
ii  vlc-bin  3.0.5-1
ii  vlc-plugin-base  3.0.5-1
ii  vlc-plugin-qt3.0.5-1
ii  vlc-plugin-video-output  3.0.5-1
 
Versions of packages vlc recommends:
ii  vlc-l10n  3.0.5-1
ii  vlc-plugin-notify  3.0.5-1
ii  vlc-plugin-samba  3.0.5-1
ii  vlc-plugin-skins2  3.0.5-1
ii  vlc-plugin-video-splitter  3.0.5-1
ii  vlc-plugin-visualization  3.0.5-1
 
vlc suggests no packages.
 
Versions of packages libvlc-bin depends on:
ii  libc62.28-4
ii  libvlc5  3.0.5-1
 
Versions of packages libvlc5 depends on:
ii  libc62.28-4
ii  libvlccore9  3.0.5-1
 
Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.5-1
 
Versions of packages vlc-bin depends on:
ii  libc6  2.28-4
ii  libvlc-bin  3.0.5-1
ii  libvlc53.0.5-1
 
Versions of packages vlc-plugin-base depends on:
ii  liba52-0.7.40.7.4-19
ii  libaom0  1.0.0-3
ii  libarchive133.3.3-2
ii  libaribb24-01.0.3-2
ii  libasound2  1.1.7-2
ii  libass9  1:0.14.0-2
ii  libavahi-client30.7-4+b1
ii  libavahi-common30.7-4+b1
ii  libavc1394-00.5.4-5
ii  libavcodec587:4.1-1
ii  libavformat587:4.1-1
ii  libavutil56  7:4.1-1
ii  libbasicusageenvironment12018.11.26-1
ii  libbluray2  1:1.0.2-3
ii  libc62.28-4
ii  libcairo21.16.0-2
ii  libcddb21.3.2-6
ii  libchromaprint1  1.4.3-2+b1
ii  libcrystalhd31:0.0~git20110715.fdd2f19-13
ii  libdbus-1-3  1.12.12-1
ii  libdc1394-222.2.5-1
ii  libdca0  0.0.6-1
ii  libdvbpsi10  1.3.2-1
ii  libdvdnav4  6.0.0-1
ii  libdvdread4  6.0.0-1
ii  libebml4v5  1.3.6-2
ii  libfaad22.8.8-1
ii  libflac81.3.2-3
ii  libfontconfig1  2.13.1-2
ii  libfreetype62.9.1-3
ii  libfribidi0  1.0.5-3
ii  libgcc1  1:8.2.0-13
ii  libgcrypt20  1.8.4-4
ii  libglib2.0-02.58.2-3
ii  libgnutls30  3.6.5-2
ii  libgpg-error01.33-3
ii  libgroupsock82018.11.26-1
ii  libharfbuzz0b2.3.0-1
ii  libixml101:1.8.4-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libkate10.4.1-8
ii  liblirc-client0  0.10.1-4
ii  liblivemedia64  2018.11.26-1
ii  liblua5.2-0  5.2.4-1.1+b2
ii  libmad0  0.15.1b-9
ii  libmatroska6v5  1.4.9-1
ii  libmicrodns00.0.10-1
ii  libmpcdec6  2:0.1~r495-1+b2
ii  libmpeg2-4  0.5.1-8
ii  libmpg123-0  1.25.10-2
ii  libmtp9  1.1.13-1.1
ii  libncursesw66.1+20181013-1
ii  libnfs112.0.0-1~exp1
ii  libogg0  1.3.2-1+b1
ii  libopenmpt-modplug1  0.4.0-1
ii  libopus01.3-1
ii  libpng16-16  1.6.36-2
ii  libpostproc557:4.1-1
ii  libprotobuf-lite17  3.6.1.3-1
ii  libpulse012.2-2
ii  libraw1394-112.1.2-1+b1
ii  libresid-builder0c2a2.1.1-15
ii  librsvg2-2  2.44.10-1
ii  libsamplerate0  0.1.9-2
ii  libsdl-image1.2  1.2.12-10
ii  libsdl1.2debian  1.2.15+dfsg2-4
ii  libsecret-1-0  

Processed: graphite-api build depends on python3-xcffib that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 860739 892648 903619 917171
Bug #918275 [src:graphite-api] graphite-api build depends on python3-xcffib 
that is currently not in buster
918275 was not blocked by any bugs.
918275 was not blocking any bugs.
Added blocking bug(s) of 918275: 917171, 903619, 892648, and 860739

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

Bug#918275: graphite-api build depends on python3-xcffib that is currently not in buster

[Adrian Bunk]

Source: graphite-api
Version: 1.1.3-5
Severity: serious
Tags: ftbfs
Control: block -1 by 860739 892648 903619 917171

graphite-api build depends on python3-xcffib that is currently not in buster 
due to #860739, #892648, #903619 and #917171.

Processed: block 911271 with 911988

[Debian Bug Tracking System]

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

> block 911271 with 911988
Bug #911271 [foolscap] foolscap: (Build) Depends on non existing python-txtorcon
911271 was not blocked by any bugs.
911271 was not blocking any bugs.
Added blocking bug(s) of 911271: 911988
> thanks
Stopping processing here.

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

Bug#918274: foodcritic build depends on chef that is currently not in buster

[Adrian Bunk]

Source: foodcritic
Version: 13.1.1-2
Severity: serious
Tags: ftbfs
Control: block -1 by 909205

foodcritic build depends on chef that is currently
not in buster due to #909205.

Processed: foodcritic build depends on chef that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 909205
Bug #918274 [src:foodcritic] foodcritic build depends on chef that is currently 
not in buster
918274 was not blocked by any bugs.
918274 was not blocking any bugs.
Added blocking bug(s) of 918274: 909205

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

Bug#918273: eficas build depends on python-openturns that is currently not in buster

[Adrian Bunk]

Source: eficas
Version: 6.4.0-1-2
Severity: serious
Tags: ftbfs
Control: block -1 by 897768 902513

eficas build depends on python-openturns that is currently
not in buster due to #897768 and #902513.

Processed: eficas build depends on python-openturns that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 897768 902513
Bug #918273 [src:eficas] eficas build depends on python-openturns that is 
currently not in buster
918273 was not blocked by any bugs.
918273 was not blocking any bugs.
Added blocking bug(s) of 918273: 902513 and 897768

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

Bug#918249: doc-rfc: please switch to ps2txt for testsuite

[Iustin Pop]

On 2019-01-04 20:16:40, Gianfranco Costamagna wrote:
>  thanks  for having a look! I was wondering about something more subtle and 
> behind the scenes :)
> btw for some reasons the ci is not running the testsuite on 
> unstablehttps://ci.debian.net/packages/d/doc-rfc/probably because testing is 
> sad?
> I don't know, I tried the -2 I committed on git on debomatic and the 
> autopkgtestsuite was good :)

Hrmm, I thought I'd get an email about this, but no, seems I have to
look manually at ddpo. One more thing to add to my notes…

I'll try to sort this out soon, before the soft freeze. Not sure I can
finish everything this weekend.

iustin

Bug#918268: bugs-everywhere build depends on monotone that is currently not in buster

[Adrian Bunk]

Source: bugs-everywhere
Version: 1.1.1-4
Severity: serious
Tags: ftbfs
Control: block -1 by 888612 889556

bugs-everywhere build depends on monotone that is currently
not in buster due to #888612 and #889556.

Processed: bugs-everywhere build depends on monotone that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 888612 889556
Bug #918268 [src:bugs-everywhere] bugs-everywhere build depends on monotone 
that is currently not in buster
918268 was not blocked by any bugs.
918268 was not blocking any bugs.
Added blocking bug(s) of 918268: 889556 and 888612

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