Processed: re: zoneminder: uses deprecated libavresample

[Debian Bug Tracking System]

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

> tags 971324 -bullseye
Bug #971324 [src:zoneminder] zoneminder: uses deprecated libavresample
Removed tag(s) bullseye.
> severity 971324 serious
Bug #971324 [src:zoneminder] zoneminder: uses deprecated libavresample
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: re: nageru: uses deprecated libavresample

[Debian Bug Tracking System]

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

> tags 971328 -bullseye
Bug #971328 [src:nageru] nageru: uses deprecated libavresample
Removed tag(s) bullseye.
> severity 971328 serious
Bug #971328 [src:nageru] nageru: uses deprecated libavresample
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#993421: sdl-kitchensink build-depends on removed package libavresample-dev

[peter green]

Source: sdl-kitchensink
Version: 1.0.9-2
Severity: serious
Tags: bookworm, sid

The ffmpeg package no longer builds libavresample-dev, it is completely gone
from testing and while it is present in unstable as a cruft package, it is
uninstallable there due to dependency versions. So this package's
build-dependencies can no longer be satisfied in testing.

Bug#971322: sdl-kitchensink build-depends on removed package libavresample-dev

[peter green]

Source: sdl-kitchensink
Version: 1.0.9-2
Severity: serious
Tags: bookworm, sid

The ffmpeg package no longer builds libavresample-dev, it is completely gone
from testing and while it is present in unstable as a cruft package, it is
uninstallable there due to dependency versions. So this package's
build-dependencies can no longer be satisfied in testing.

Processed: re: performous: uses deprecated libavresample

[Debian Bug Tracking System]

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

> tags 971322 -bullseye
Bug #971322 [src:performous] performous: uses deprecated libavresample
Removed tag(s) bullseye.
> severity 971322 serious
Bug #971322 [src:performous] performous: uses deprecated libavresample
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#993390: virtuoso-opensource: FTBFS: Dkmarshal.c:50:11: fatal error: rpc/types.h: No such file or directory

[Boyuan Yang]

X-Debbugs-CC: sramac...@debian.org

Hi,

On Tue, 31 Aug 2021 18:41:01 +0200 Sebastian Ramacher 
wrote:
> Source: virtuoso-opensource
> Version: 7.2.5.1+dfsg1-0.1
> Severity: serious
> Tags: ftbfs sid bullseye
> Justification: fails to build from source (but built successfully in the
past)
> X-Debbugs-Cc: sramac...@debian.org
> 
> | libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2
-fno-strict-aliasing -O2 -Wall -DNDEBUG -DPOINTER_64 -
I/<>/libsrc/Xml.new -DOPENSSL_NO_KRB5 -Dlinux -D_GNU_SOURCE -
DFILE64 -D_LARGEFILE64_SOURCE -I../../libsrc -g -O2 -ffile-prefix-
map=/<>=. -fstack-protector-strong -Wformat -Werror=format-
security -D_GNU_SOURCE -c Dkmem.c  -fPIC -DPIC -o .libs/libdksrv_la-Dkmem.o
> | Dkmarshal.c:50:11: fatal error: rpc/types.h: No such file or directory
> |    50 | # include 
> |   |   ^
> | compilation terminated.
> | make[5]: *** [Makefile:1169: libdksrv_la-Dkmarshal.lo] Error 1
> 
>
https://buildd.debian.org/status/fetch.php?pkg=virtuoso-opensource=arm64=7.2.5.1%2Bdfsg1-0.1%2Bb1=1630424102=0

Looks like a side effect of glibc/2.31-14 (Aug 17 2021):

  * debian/rules.d/build.mk: stop passing --enable-obsolete-rpc.

Also see
https://sources.debian.org/src/virtuoso-opensource/7.2.5.1+dfsg1-0.1/libsrc/Dk/Dkmarshal.c/#L49
:

##

#if defined (i386) || \
defined (_WIN64) || \
defined (_M_IX86) || \
defined (_M_ALPHA) || \
defined (mc68000) || \
defined (sparc) || \
defined (__x86_64) || \
defined (__alpha) || \
defined (__powerpc) || \
defined (mips) || \
defined (__OS2__) || \
defined (_IBMR2)
# define _IEEE_FLOATS
#elif defined (OPL_SOURCE)
# include 
#else
# include 
# include 
#endif

#

-- 
Thanks,
Boyuan Yang


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

Processed: re: aubio: uses deprecated libavresample

[Debian Bug Tracking System]

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

> tags 971319 -bullseye
Bug #971319 [src:aubio] aubio: uses deprecated libavresample
Removed tag(s) bullseye.
> severity 971319 serious
Bug #971319 [src:aubio] aubio: uses deprecated libavresample
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Re: kylin-burner: Please release 3.0.10 to unstable

[Debian Bug Tracking System]

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

> severity 993361 serious
Bug #993361 [src:kylin-burner] kylin-burner: Please release 3.0.10 to unstable
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#993336: libclass-trait-perl: arch:all but depends on perlapi-5.32.0

[Alexander Zangerl]

On Tue, 31 Aug 2021 00:53:09 +0300, Niko Tyni writes:
>Package: libclass-trait-perl

i've requested removal of that package (#993410).

regards
az


-- 
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/
In German, a young lady has no sex, while a turnip has. Think what 
overwrought reverence that shows for the turnip, and what callous 
disrespect for the girl. -- Mark Twain


signature.asc
Description: Digital Signature

Processed: netatalk: Switch to tracker 3

[Debian Bug Tracking System]

Processing control commands:

> block 993052 by -1
Bug #993052 [release.debian.org] transition: tracker
993052 was blocked by: 993361
993052 was not blocking any bugs.
Added blocking bug(s) of 993052: 993412

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

Bug#993412: netatalk: Switch to tracker 3

[Jeremy Bicha]

Source: netatalk
Version: 3.1.12~ds-8
Severity: serious
Control: block 993052 by -1

We have begun the transition from tracker 2 to tracker 3. Please
update your package for this transition.

Your salsa repo is not open for merge proposals, but you can grab the
top 3 commits from
https://salsa.debian.org/laney/netatalk/-/commits/wip/tracker3

Thanks,
Jeremy Bicha

Bug#993403: marked as done (libobject-remote-perl: missing dependency on libstrictures-perl)

[Debian Bug Tracking System]

Your message dated Tue, 31 Aug 2021 20:49:00 +
with message-id 
and subject line Bug#993403: fixed in libobject-remote-perl 0.004001-2
has caused the Debian Bug report #993403,
regarding libobject-remote-perl: missing dependency on libstrictures-perl
to be marked as done.

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

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


-- 
993403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libobject-remote-perl
Version: 0.004001-1
Severity: serious
Tags: ftbfs sid bookworm

This package is missing a dependency on libstrictures-perl.

  % perl -e 'use Object::Remote'
  Can't locate strictures.pm in @INC (you may need to install the strictures 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 
/usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 
/usr/local/lib/site_perl) at /usr/share/perl5/Object/Remote/Proxy.pm line 3.
 
Until recently this was masked by its dependency, libmoo-perl,
depending on libstrictures-perl, but that was removed in
libmoo-perl_2.005004-1.

The missing dependency causes test suite failures, making the package
fail to build from source and regress on ci.debian.net. The regressions
are blocking libmoo-perl_2.005004-1 from entering testing.

When this is fixed, libmoo-perl should declare a Breaks entry
on the old versions.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libobject-remote-perl
Source-Version: 0.004001-2
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libobject-remote-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 31 Aug 2021 22:34:21 +0200
Source: libobject-remote-perl
Architecture: source
Version: 0.004001-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 993403
Changes:
 libobject-remote-perl (0.004001-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Update standards version to 4.5.0, no changes needed.
 .
   [ gregor herrmann ]
   * Add a (build) dependency on libstrictures-perl. (Closes: #993403)
   * Declare compliance with Debian Policy 4.6.0.
   * Set Rules-Requires-Root: no.
   * Bump debhelper-compat to 13.
Checksums-Sha1:
 5414382e4ba7c48c824da18b9d95a7be05ccde24 2920 
libobject-remote-perl_0.004001-2.dsc
 fe84fc57cf806f2ad9978571f99b741c5a7687fe 4456 
libobject-remote-perl_0.004001-2.debian.tar.xz
Checksums-Sha256:
 d0d523546328a363737e5e749f158eccacfca942f9076f82255fb9410a8eb7ee 2920 
libobject-remote-perl_0.004001-2.dsc
 ecefb439c53fd8f15afcb5bb2a7c0fc5fe09f3386d80dd0972150693bcec02d2 4456 
libobject-remote-perl_0.004001-2.debian.tar.xz
Files:
 58f4ed731f1a51afe6f2fbe331b980ef 2920 perl optional 
libobject-remote-perl_0.004001-2.dsc
 a9d8b5341a4d485b0a830770c2291a9d 4456 perl optional 
libobject-remote-perl_0.004001-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmEukzBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZIww//ZdUXWYtOdYNRBX3fLBhQO+YRpR+6ip1QqtzeVmdsORTqVBT+Y8sEz3lt
fw35RjCkcHYSx0pn0EJ9uDZBZ4ILtwyP0PCaMy9LS7qAzZdyfssUj1xlPNHAe7Rw
ONunObUZvLaDRa1cjFYcU3TLPSku85hF7yPRv7q1BZal42nW6h1sSVAMOOccDd2G
N2aEEVGNKZszhF7qagzcg6VGTwP+XPLhUSVwwRSFeEzd1P8hPoZcE4LAXC+5vGop
eR0/0yR/UqfRk8k4HK2XZ+II0Fmd3Pz83rFz4x51ylWtrUiTrSNjEzztPETGBqFm
OQruDbh4S5M+peuocTYJXLlcE4mlvc1R+fTA1PevRXPGblI2sTIR11FTEyUIWhk3
0MqF22o8AHGhNHVgbNu9C/BRTdoHlWmLvIl+p4yhb4ebdYhffgNWH9QwJ7i2Pa7L
5ThWooIehYMBngfLxuJ6NSyfWBRipRuFa4y7xaU4mEwiVAR8HH8HJ9bgM15iqZ1/
sinfB9exhKMyz4uDpkuBql0AcZPNWjbWLY6VMg2g+SVrGMUYjQAHjDOaJVeaLcjc
vdDlFjfVfJGSH7WOPF8EiIv3Ej9PADskyuEOgHQ5twGD4UzH0Z+DNxULuK2hE/YM

Processed: Bug#993403 marked as pending in libobject-remote-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #993403 [libobject-remote-perl] libobject-remote-perl: missing dependency 
on libstrictures-perl
Added tag(s) pending.

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

Bug#993403: marked as pending in libobject-remote-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #993403 in libobject-remote-perl 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/perl-team/modules/packages/libobject-remote-perl/-/commit/184f6a327044bbec02bc6eae8feee08919682f11


Add a (build) dependency on libstrictures-perl.

Closes: #993403


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993403

Bug#993399: marked as done (libdatetimex-easy-perl: FTBFS: t/03-parse.t failure)

[Debian Bug Tracking System]

Your message dated Tue, 31 Aug 2021 20:34:05 +
with message-id 
and subject line Bug#993399: fixed in libdatetimex-easy-perl 0.089-3
has caused the Debian Bug report #993399,
regarding libdatetimex-easy-perl: FTBFS: t/03-parse.t failure
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.)


-- 
993399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdatetimex-easy-perl
Version: 0.089-2
Severity: serious
Tags: ftbfs sid bookworm patch
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=137397

This package fails its test suite on current sid.

It broke with libdatetime-format-flexible-perl_0.34-1.

Petr Písař says in the upstream ticket that the libdatetimex-easy-perl
tests need to adapt and provides a patch there.

This is currently blocking the testing migration of the new
libdatetime-format-flexible-perl version because of regressions
on ci.debian.net.

>From 
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libdatetimex-easy-perl.html

   #   Failed test at t/03-parse.t line 32.
   #  got: 'America/New_York'
   # expected: '-0500'
   # Looks like you failed 1 test of 18.
   
   [...]
   
   Test Summary Report
   ---
   t/01-basic.t   (Wstat: 0 Tests: 76 Failed: 0)
 TODO passed:   47-53
   t/03-parse.t   (Wstat: 256 Tests: 18 Failed: 1)
 Failed test:  6
 Non-zero exit status: 1
   Files=3, Tests=106,  3 wallclock secs ( 0.05 usr  0.02 sys +  2.17 cusr  
0.22 csys =  2.46 CPU)
   Result: FAIL
 
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libdatetimex-easy-perl
Source-Version: 0.089-3
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libdatetimex-easy-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 31 Aug 2021 21:51:07 +0200
Source: libdatetimex-easy-perl
Architecture: source
Version: 0.089-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 993399
Changes:
 libdatetimex-easy-perl (0.089-3) unstable; urgency=medium
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ gregor herrmann ]
   * debian/watch: use uscan version 4.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 10 to 12.
   * Set debhelper-compat version in Build-Depends.
 .
   [ gregor herrmann ]
   * Add patch from CPAN RT to adapt tests to DateTime-Format-
 Flexible-0.34. (Closes: #993399)
   * Update years of packaging copyright.
   * Declare compliance with Debian Policy 4.6.0.
   * Annotate test-only build dependencies with .
   * Bump debhelper-compat to 13.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
Checksums-Sha1:
 d2c4db0eed184fe5bef624251ba839ca0e762968 2633 
libdatetimex-easy-perl_0.089-3.dsc
 a9c25ad79068fbfa7c377b4fe669b90f3ae4fb57 4204 
libdatetimex-easy-perl_0.089-3.debian.tar.xz
Checksums-Sha256:
 81860f643c4f92ea584649038c6b89b663583fd2d5278505e1fb80568ed21edd 2633 
libdatetimex-easy-perl_0.089-3.dsc
 853378604943a266b62a516d3bec5161de713cdb5c78b9cc2bda62dfdb402231 4204 
libdatetimex-easy-perl_0.089-3.debian.tar.xz
Files:
 457f64166e350c122b49f37cfc8edf94 2633 perl optional 
libdatetimex-easy-perl_0.089-3.dsc
 72f618b429fa85421ea0bbbfb32552bf 4204 perl optional 
libdatetimex-easy-perl_0.089-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmEuiMtfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZ7xhAAlR7dwp3X4NYTbMYiTFq0u8kwJpTwwUyzsSC2gkYTsWOpzAMgi7VdqxUu
bnlovnfdLPN5vQ3e+OLbniLbASZwPAmbgzn2bh7O5/2+Mt3cN210YEqyHHYZvJ0J
FAoLvPI8yvwxS9WZsUSVuvlmDsvidXYCW7Su3LtUTIiQKk0RtFSDrZXTQ/SrdGpH

Bug#993399: marked as pending in libdatetimex-easy-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #993399 in libdatetimex-easy-perl 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/perl-team/modules/packages/libdatetimex-easy-perl/-/commit/a47a14d4bb6bc1619c9d8431be269c96c71d7e1a


Add patch from CPAN RT to adapt tests to DateTime-Format-Flexible-0.34.

Closes: #993399


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993399

Processed: Bug#993399 marked as pending in libdatetimex-easy-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #993399 [src:libdatetimex-easy-perl] libdatetimex-easy-perl: FTBFS: 
t/03-parse.t failure
Added tag(s) pending.

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

Bug#992867: marked as done (Stop flooding syslog! You will fill up the disk.)

[Debian Bug Tracking System]

Your message dated Tue, 31 Aug 2021 21:38:22 +0200
with message-id 
and subject line Re: Bug#992867: Stop flooding syslog! You will fill up the 
disk.
has caused the Debian Bug report #992867,
regarding Stop flooding syslog! You will fill up the disk.
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.)


-- 
992867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: x11-xkb-utils
Version: 7.7+5
Severity: grave

Did anybody take a look at syslog recently?

It is flooded with
Internal error:   Could not resolve keysym ...

So much so that the disk will fill up.
--- End Message ---
--- Begin Message ---
On 2021-08-24 21:36:59 +0800, 積丹尼 Dan Jacobson wrote:
> Package: x11-xkb-utils
> Version: 7.7+5
> Severity: grave
> 
> Did anybody take a look at syslog recently?
> 
> It is flooded with
> Internal error:   Could not resolve keysym ...
> 
> So much so that the disk will fill up.

You already filed #953032. We don't need two bug reports for the same
issue.

Cheers
-- 
Sebastian Ramacher


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

Processed: bug 993397 is forwarded to https://github.com/Aneurysm9/hostfile_manager/issues/8

[Debian Bug Tracking System]

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

> forwarded 993397 https://github.com/Aneurysm9/hostfile_manager/issues/8
Bug #993397 [src:libhostfile-manager-perl] libhostfile-manager-perl: FTBFS: You 
planned 65 tests but ran 64.
Set Bug forwarded-to-address to 
'https://github.com/Aneurysm9/hostfile_manager/issues/8'.
> thanks
Stopping processing here.

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

Bug#993403: libobject-remote-perl: missing dependency on libstrictures-perl

[Niko Tyni]

Package: libobject-remote-perl
Version: 0.004001-1
Severity: serious
Tags: ftbfs sid bookworm

This package is missing a dependency on libstrictures-perl.

  % perl -e 'use Object::Remote'
  Can't locate strictures.pm in @INC (you may need to install the strictures 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 
/usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 
/usr/local/lib/site_perl) at /usr/share/perl5/Object/Remote/Proxy.pm line 3.
 
Until recently this was masked by its dependency, libmoo-perl,
depending on libstrictures-perl, but that was removed in
libmoo-perl_2.005004-1.

The missing dependency causes test suite failures, making the package
fail to build from source and regress on ci.debian.net. The regressions
are blocking libmoo-perl_2.005004-1 from entering testing.

When this is fixed, libmoo-perl should declare a Breaks entry
on the old versions.
-- 
Niko Tyni   nt...@debian.org

Bug#993395: marked as done (libconfig-ini-perl: broken by libmixin-linewise-perl)

[Debian Bug Tracking System]

Your message dated Tue, 31 Aug 2021 19:33:33 +
with message-id 
and subject line Bug#993395: fixed in libconfig-ini-perl 1:0.027-1
has caused the Debian Bug report #993395,
regarding libconfig-ini-perl: broken by libmixin-linewise-perl
to be marked as done.

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

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


-- 
993395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libconfig-ini-perl
Version: 1:0.025-1.1
Severity: serious
Tags: ftbfs fixed-upstream sid bookworm

As seen on ci.debian.net, this package fails its test suite with
libmixin-linewise-perl/0.110-1. The regression is currently blocking
libmixin-linewise-perl testing migration.

The issue is presumably fixed upstream in Config-INI:

0.027 2021-06-22 22:27:53-04:00 America/New_York
- require Mixin::Linewise v0.110 to cope with new error message

I haven't checked if this is only build time breakage, or if run time
is affected too. In the latter case libmixin-linewise-perl probably needs
to add a Breaks entry.

>From 
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libconfig-ini-perl.html

   #   Failed test 'read_file on non-plain-file'
   #   at t/reader-err.t line 30.
   #   ''lib' is not readable at t/reader-err.t line 29.
   # '
   # doesn't match '(?^i:not a plain file)'
   
   #   Failed test 'can't read an unreadable file'
   #   at t/reader-err.t line 51.
   #   ''tempt6w8z' is not readable at t/reader-err.t line 50.
   # '
   # doesn't match '(?^:(?:couldn't|can't) read)'
   # Looks like you failed 2 tests of 9.
   t/reader-err.t . 
   1..9
   ok 1 - read_file without args
   ok 2 - read_file with non-existent file
   not ok 3 - read_file on non-plain-file
   not ok 4 - can't read an unreadable file
   ok 5 - read_string without args
   ok 6 - syntax error
   ok 7 - syntax error
   ok 8 - we can't read a UTF-8 file that starts with a BOM
   ok 9 - the error message mentions a BOM
   Dubious, test returned 2 (wstat 512, 0x200)
   Failed 2/9 subtests 

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libconfig-ini-perl
Source-Version: 1:0.027-1
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libconfig-ini-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 31 Aug 2021 21:22:12 +0200
Source: libconfig-ini-perl
Architecture: source
Version: 1:0.027-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 993395
Changes:
 libconfig-ini-perl (1:0.027-1) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Rename autopkgtest configuration file(s) as per new pkg-perl-
 autopkgtest schema.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Remove Fabrizio Regalli from Uploaders. Thanks for your work!
   * Remove Jonathan Yu from Uploaders. Thanks for your work!
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ Laurent Baillet ]
   * fix lintian file-contains-trailing-whitespace warning
 .
   [ gregor herrmann ]
   * debian/watch: use uscan version 4.
 .
   [ Debian Janitor ]
   * Bump debhelper from deprecated 8 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Submit.
   * Remove obsolete fields Contact, Name from debian/upstream/metadata
 (already present in machine-readable debian/copyright).
 .
   [ gregor herrmann ]
   * Import upstream version 0.027.
   * Bump versioned (build) dependency on libmixin-linewise-perl.
 (Closes: #993395)
   * Update upstream email address.
   * Update years of packaging copyright.
   * Declare compliance with Debian Policy 4.6.0.
   * Set 

Bug#993399: libdatetimex-easy-perl: FTBFS: t/03-parse.t failure

[Niko Tyni]

Source: libdatetimex-easy-perl
Version: 0.089-2
Severity: serious
Tags: ftbfs sid bookworm patch
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=137397

This package fails its test suite on current sid.

It broke with libdatetime-format-flexible-perl_0.34-1.

Petr Písař says in the upstream ticket that the libdatetimex-easy-perl
tests need to adapt and provides a patch there.

This is currently blocking the testing migration of the new
libdatetime-format-flexible-perl version because of regressions
on ci.debian.net.

>From 
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libdatetimex-easy-perl.html

   #   Failed test at t/03-parse.t line 32.
   #  got: 'America/New_York'
   # expected: '-0500'
   # Looks like you failed 1 test of 18.
   
   [...]
   
   Test Summary Report
   ---
   t/01-basic.t   (Wstat: 0 Tests: 76 Failed: 0)
 TODO passed:   47-53
   t/03-parse.t   (Wstat: 256 Tests: 18 Failed: 1)
 Failed test:  6
 Non-zero exit status: 1
   Files=3, Tests=106,  3 wallclock secs ( 0.05 usr  0.02 sys +  2.17 cusr  
0.22 csys =  2.46 CPU)
   Result: FAIL
 
-- 
Niko Tyni   nt...@debian.org

Processed: Bug#993395 marked as pending in libconfig-ini-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #993395 [libconfig-ini-perl] libconfig-ini-perl: broken by 
libmixin-linewise-perl
Added tag(s) pending.

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

Bug#975191: [Pkg-rust-maintainers] Bug#975191: re: rust-js-sys: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

[Wolfgang Silbermayr]

On 8/31/21 4:25 PM, Bastian Germann wrote:
> On Wed, 2 Dec 2020 02:46:36 + peter green  wrote:
>>  > This will impact quite some other modules.
>>
>> I agree that the current autoremoval list looks pretty scary, so I decided
>> to do some
>> dependency analysis. It seems there are 5 source packages with direct or
>> indirect hard
>> dependencies on rust-js-sys.
>>
>> rust-www-sys
>> rust-ring
>> rust-rustls
>> rust-sct
>> rust-webpki
> 
> Hey,
> 
> I would like to get rustls migrating to bookworm but this is a blocker for it.
> Can you please state if you want to fix this or would like help with it? I
> guess importing the current version will do it.

Hi Bastian,

I'd be happy to support getting rustls to migrate as well.

After taking a look, "just" updating rust-js-sys to the latest version also
requires an update of the wasm-bindgen related crates to the latest version
(which currently is 0.2.76 across all of them):

wasm-bindgen-shared
wasm-bindgen-backend
wasm-bindgen-macro-support
wasm-bindgen-macro
wasm-bindgen

I did a quick test run updating all of these, and it basically works, once
`syn` got updated. For `syn`, we have an RFS note indicating that autopkgtests
don't work yet with the updated version and need some other packages such as
`insta` uploaded before. I didn't dig too deeply into that part, but we might
need to invest some additional work here.

Within the wasm-bindgen* group, I also stumbled over a few autopkgtest problems:

wasm-bindgen-macro-support has a few features that fail their tests, but I
expect that these tests simply aren't intended to be run with only a single
feature enabled. Would require some investigation and either fixing or marking
them as broken. The rest of the tests succeeds.

wasm-bindgen-macro requires wasm-bindgen to be available for the autopkgtest,
but it should be possible to handle that. In addition, it requires
wasm-bindgen-futures 0.4, some more about that below.

wasm-bindgen requires js-sys 0.3 to be available for the autopkgtest, but
again that can be handled.

js-sys requires wasm-bindgen-futures 0.4 for the autopkgtest as well.

Regarding wasm-bindgen-futures, that one has a dev dependency on
futures-channel-preview in a 0.3 alpha version. We can basically handle that,
but that crate received its last update about two years ago. At a quick look,
it seems to be a bootstrapping crate that might be intended to be replaced by
futures-channel which is available by now, but that didn't happen yet for
whichever reason. Might be a topic to investigate upstream. That one pulls in
futures-core 0.3, and thus requires an update of the futures ecosystem from
0.1 to 0.3 which by itself is a topic that is much larger than the
wasm-bindgen topic that I describe here. There was already some preparation
done by another team member, but I'm not sure when it was the last time
somebody took a thorough look at what they prepared.

I'd love to work on untangling these issues, but once I start working on such
a group of problematic packages, I usually discover blockers which stop my
undertaking, and due to being a DM, I need a DD to either grant me upload
access for the affected crates, or sponsor the upload for me, so it's quite
tedious to finish such a group of packages, with all the inconveniences that
come from the delays, such as packages failing to migrate for some time or
autopkgtests failing until the required dependencies become available. If it
was for me, we could go forward and upload the updates, but in the past it
didn't take long until we collected many reports about failing or skipped
autopkgtests.

That's what I can tell upfront from my quick evaluation, but speaking from
experience, I'd expect some unforeseen roadblock to show up when working on it.

I hope this quick analysis gives you some insight into the overall state, and
some idea where and how you would like to proceed. In case you need some
support working on a specific crate, let me know.

Best regards,
Wolfgang.

Bug#993395: marked as pending in libconfig-ini-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #993395 in libconfig-ini-perl 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/perl-team/modules/packages/libconfig-ini-perl/-/commit/f2b9deb8bd918e8138a46843d51b3d37dfe27826


Bump versioned (build) dependency on libmixin-linewise-perl.

Closes: #993395


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993395

Processed: neutron: CVE-2021-40085: Arbitrary dnsmasq reconfiguration via extra_dhcp_opts

[Debian Bug Tracking System]

Processing control commands:

> found -1 2:17.1.1-6
Bug #993398 [src:neutron] neutron: CVE-2021-40085: Arbitrary dnsmasq 
reconfiguration via extra_dhcp_opts
Marked as found in versions neutron/2:17.1.1-6.

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

Bug#993398: neutron: CVE-2021-40085: Arbitrary dnsmasq reconfiguration via extra_dhcp_opts

[Salvatore Bonaccorso]

Source: neutron
Version: 2:18.1.0-2
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://launchpad.net/bugs/1939733
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2:17.1.1-6

Hi,

The following vulnerability was published for neutron.

CVE-2021-40085[0]:
| An issue was discovered in OpenStack Neutron before 16.4.1, 17.x
| before 17.2.1, and 18.x before 18.1.1. Authenticated attackers can
| reconfigure dnsmasq via a crafted extra_dhcp_opts value.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-40085
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40085
[1] https://launchpad.net/bugs/1939733
[2] https://www.openwall.com/lists/oss-security/2021/08/31/2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#993397: libhostfile-manager-perl: FTBFS: You planned 65 tests but ran 64.

[Niko Tyni]

Source: libhostfile-manager-perl
Version: 0.09-1.1
Severity: serious
Tags: ftbfs sid bookworm

This package fails its test suite on current sid.

It probably broke with libtest-nowarnings-perl_1.06-1 which is already
in testing (not sure why autopkgtest regression checks didn't catch this.)
>From the Test-NoWarnings changelog:

  Made had_no_warnings turn off the checking at END time for use with
  done_testing based tests with no test count. Also added docs.

>From 
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libhostfile-manager-perl.html

   # Looks like you planned 65 tests but ran 64.
   t/run.t .. 
   1..65
   ok 1 - use Hostfile::Manager;
   ok 2 - Hostfile::Manager->can('block')
   ok 3 - block
   ok 4 - Hostfile::Manager->can('new')
   ok 5 - ... and the constructor should succeed
   ok 6 - '... and the object it returns' isa 'Hostfile::Manager'
   ok 7 - Hostfile::Manager->can('disable_fragment')
   ok 8 - ... and fragment_enabled returns ok when fragment is indeed enabled
   ok 9 - ... and disable_fragment returns ok when fragment is newly disabled
   ok 10 - ... and fragment is indeed disabled
   ok 11 - Hostfile::Manager->can('enable_fragment')
   ok 12 - ... and enable_fragment returns ok when fragment is newly enabled
   ok 13 - ... and fragment is indeed enabled
   ok 14 - Hostfile::Manager->can('enable_fragment')
   ok 15 - ... and enable_fragment returns ok when fragment is newly enabled
   ok 16 - ... and fragment is indeed enabled
   ok 17 - ... and fragment only appears once
   ok 18 - ... and enable_fragment does not complain excessively when enabling 
missing fragment
   ok 19 - Hostfile::Manager->can('fragment_enabled')
   ok 20 - ... and fragment_enabled returns ok when fragment is indeed enabled
   ok 21 - ... and fragment_enabled returns not_ok when fragment is not enabled
   ok 22 - Hostfile::Manager->can('fragment_list')
   ok 23 - ... and fragment list matches expectation
   ok 24 - Hostfile::Manager->can('fragment_status_flag')
   ok 25 - ... and fragment_status_flag returns '+' when fragment is enabled 
and unmodified
   ok 26 - ... and fragment_status_flag returns '*' when fragment is enabled 
and modified
   ok 27 - ... and fragment_status_flag returns ' ' when fragment is disabled
   ok 28 - Hostfile::Manager->can('get_fragment')
   ok 29 - ... and get_fragment returns fragment content
   ok 30 - Hostfile::Manager->can('get_fragment')
   ok 31 - ... and get_fragment undef when fragment file missing
   ok 32 - Hostfile::Manager->can('hostfile')
   ok 33 - ... and hostfile should start out with content of file at 
hostfile_path
   ok 34 - ... and settings its value should NOT succeed
   ok 35 - ... and settings its value did not succeed
   ok 36 - hostfile should start out with content of file at hostfile_path
   ok 37 - Hostfile::Manager->can('hostfile')
   ok 38 - ... and hostfile should start out with content of file at 
hostfile_path, even when constructed with a different hostfile_path
   ok 39 - Hostfile::Manager->can('hostfile_path')
   ok 40 - ... and hostfile_path should start out with default value
   ok 41 - ... and setting its value should succeed
   ok 42 - Hostfile::Manager->can('load_hostfile')
   ok 43 - ... and load_hostfile indicates success
   ok 44 - ... and load_hostfile actually loaded the file
   ok 45 - Hostfile::Manager->can('load_hostfile')
   ok 46 - ... and load_hostfile chokes when hostfile missing
   ok 47 - Hostfile::Manager->can('load_hostfile')
   ok 48 - ... and load_hostfile indicates success
   ok 49 - ... and load_hostfile actually loaded the file
   ok 50 - Hostfile::Manager->can('path_prefix')
   ok 51 - ... and path_prefix should start out with default value
   ok 52 - ... and setting its value should succeed
   ok 53 - Hostfile::Manager->can('toggle_fragment')
   ok 54 - ... and fragment_enabled returns ok when fragment is enabled
   ok 55 - ... and toggle_fragment returns ok when fragment is newly toggled
   ok 56 - ... and fragment is disabled
   ok 57 - ... and toggle_fragment returns ok when fragment is newly toggled
   ok 58 - ... and fragment is enabled
   ok 59 - Hostfile::Manager->can('write_hostfile')
   ok 60 - ... and write_hostfile returns ok
   ok 61 - ... and hostfile written to t/fixtures/hosts/write_test
   ok 62 - Hostfile::Manager->can('write_hostfile')
   ok 63 - ... and write_hostfile chokes when trying to write to file without 
permissions
   ok 64 - ... and hostfile NOT written to t/fixtures/hosts/write_test
   Dubious, test returned 255 (wstat 65280, 0xff00)
   Failed 1/65 subtests 
   
   Test Summary Report
   ---
   t/run.t (Wstat: 65280 Tests: 64 Failed: 0)
 Non-zero exit status: 255
 Parse errors: Bad plan.  You planned 65 tests but ran 64.

-- 
Niko Tyni   nt...@debian.org

Bug#993395: libconfig-ini-perl: broken by libmixin-linewise-perl

[Niko Tyni]

Package: libconfig-ini-perl
Version: 1:0.025-1.1
Severity: serious
Tags: ftbfs fixed-upstream sid bookworm

As seen on ci.debian.net, this package fails its test suite with
libmixin-linewise-perl/0.110-1. The regression is currently blocking
libmixin-linewise-perl testing migration.

The issue is presumably fixed upstream in Config-INI:

0.027 2021-06-22 22:27:53-04:00 America/New_York
- require Mixin::Linewise v0.110 to cope with new error message

I haven't checked if this is only build time breakage, or if run time
is affected too. In the latter case libmixin-linewise-perl probably needs
to add a Breaks entry.

>From 
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libconfig-ini-perl.html

   #   Failed test 'read_file on non-plain-file'
   #   at t/reader-err.t line 30.
   #   ''lib' is not readable at t/reader-err.t line 29.
   # '
   # doesn't match '(?^i:not a plain file)'
   
   #   Failed test 'can't read an unreadable file'
   #   at t/reader-err.t line 51.
   #   ''tempt6w8z' is not readable at t/reader-err.t line 50.
   # '
   # doesn't match '(?^:(?:couldn't|can't) read)'
   # Looks like you failed 2 tests of 9.
   t/reader-err.t . 
   1..9
   ok 1 - read_file without args
   ok 2 - read_file with non-existent file
   not ok 3 - read_file on non-plain-file
   not ok 4 - can't read an unreadable file
   ok 5 - read_string without args
   ok 6 - syntax error
   ok 7 - syntax error
   ok 8 - we can't read a UTF-8 file that starts with a BOM
   ok 9 - the error message mentions a BOM
   Dubious, test returned 2 (wstat 512, 0x200)
   Failed 2/9 subtests 

-- 
Niko Tyni   nt...@debian.org

Processed: bookworm, not bullseye

[Debian Bug Tracking System]

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

> tags 993390 - bullseye
Bug #993390 [src:virtuoso-opensource] virtuoso-opensource: FTBFS: 
Dkmarshal.c:50:11: fatal error: rpc/types.h: No such file or directory
Ignoring request to alter tags of bug #993390 to the same tags previously set
> tags 993390 bookworm
Bug #993390 [src:virtuoso-opensource] virtuoso-opensource: FTBFS: 
Dkmarshal.c:50:11: fatal error: rpc/types.h: No such file or directory
Ignoring request to alter tags of bug #993390 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 993381

[Debian Bug Tracking System]

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

> tags 993381 + sid bookworm
Bug #993381 [src:conserver] conserver FTBFS: checking whether the C compiler 
works... no
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Processed: tagging 993390

[Debian Bug Tracking System]

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

> tags 993390 = ftbfs sid bookworm
Bug #993390 [src:virtuoso-opensource] virtuoso-opensource: FTBFS: 
Dkmarshal.c:50:11: fatal error: rpc/types.h: No such file or directory
Added tag(s) bookworm; removed tag(s) bullseye.
> thanks
Stopping processing here.

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

Bug#992696: [Pkg-freeipa-devel] Bug#992696: 389-ds: 389-DS no longer starts since bullseye due to libjemalloc.so.2 not found

[Adam Reece]

Hi Timo,

Thanks for your response.

I had spotted the Samba schema issue shortly after and took it out of the 
configuration already, but still had the same problem. Only by creating the 
symlink I mentioned this problem became resolved.

Does it matter that this system was an in-place upgrade from Buster? (Its 
original installation was Jessie and has been upgraded throughout releases.)


 * Adam Reece
 * Sven Co-op team

 * Email: a...@svencoop.com 
 * Web: www.svencoop.com 

On 31/08/2021 17:47, Timo Aaltonen wrote:

On 22.8.2021 15.15, Adam Reece wrote:


Aug 22 14:13:38 amun ns-slapd[14030]: [22/Aug/2021:14:13:38.279004946 +0200] - ERR - 
dse_read_one_file - The entry cn=schema in file 
/etc/dirsrv/slapd-amun.service/schema/60samba3.ldif (lineno: 1) is invalid, error code 20 
(Type or value exists) - object class sambaConfig: The name does not match the OID 
"1.3.6.1.4.1.7165.1.2.2.10". Another object class is already using the name or 
OID.
Aug 22 14:13:38 amun ns-slapd[14030]: [22/Aug/2021:14:13:38.280495362 +0200] - 
ERR - setup_internal_backends - Please edit the file to correct the reported 
problems and then restart the server.

That's your error.

The 389 packages didn't change since -2 and things work just fine on 
ci.debian.net and salsa (meaning the daemon starts), so I don't know how 389 
could be to blame here.

the libjemalloc thing is just noise, it's not a hard requirement AIUI.




OpenPGP_0x772BA858CF9CD88D.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#993316: systemd: missing /lib/systemd/system/rpcbind.service file

[Niels Thykier]

Michael Biebl:
> Hi Niels
> 
> Am 31.08.21 um 18:07 schrieb Niels Thykier:
> 
>> My thought is that this is not something I want in dh_link - dh_link has
>> no business second guessing the link values it gets.  Since dh_link runs
>> after dh_installsystemd, then we cannot even rely on dh_installsystemd
>> to perform a fix up either.
> 
> Nod.
> 
>> Which begins to smell like that either people have to update their
>> dh_links calls/configuration OR we roll back the dh_installsystemd
>> change to move to /usr.  I am not particular fan of either.  :-/
>>
>> Nevertheless, I am inclined to do a rollback and then punt on the "/ ->
>> /usr" migration track for now.
> 
> I'll see if I can compile a list of possibly affected packages.
> If the number is low enough, I think updating the symlink manually is
> probably ok.
> 
> Regards,
> Michael
> 
> 

I appreciate it, but I think we should be careful here with the manual
update.  If consensus on debian-devel is that debhelper should roll this
back, then we will break these packages again.

I do not think that would make us popular... :-/

~Niels

Bug#993338: octave: Setting up octave fails due to missing libGL.so.1

[Sébastien Villemot]

Le lundi 30 août 2021 à 22:32 +, Witold Baryluk a écrit :
> Package: octave
> Version: 6.2.0-1
> Severity: serious
> Justification: Policy 3.5
> X-Debbugs-Cc: witold.bary...@gmail.com
> 
> Dear Maintainer,
> 
> when debootstrapping using live-build:
> 
> Setting up octave (6.2.0-1) ...
> /usr/bin/octave-cli: error while loading shared libraries: libGL.so.1: cannot 
> open shared object file: No such file or directory
> dpkg: error processing package octave (--configure):
>  installed octave package post-installation script subprocess returned error 
> exit status 127
> 
> 
> Mesa is installed later by apt. Pre-Depends maybe required? Also weird a
> bit that octave-cli requires OpenGL.

Policy §6.5 is clear about the fact that, when the postinst script is
called, dependencies are unpacked and configured (unless there are
circular dependencies, which I don’t think is the case here).

So if libgl1 is really unpacked after octave is configured, the bug
probably lies in dpkg.

Do you have a way of reproducing the problem?

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Bug#993338: octave: Setting up octave fails due to missing libGL.so.1

[Witold Baryluk]

Package: octave
Version: 6.2.0-1
Followup-For: Bug #993338
X-Debbugs-Cc: witold.bary...@gmail.com

Actually not mesa itself strictly, but rather 'libgl1' package needs to
be in Pre-Depends afaik.

Regards,
Witold

Bug#993043: ensmallen: autopkgtest regression on arm64/i386/ppc64el

[Graham Inggs]

This appears to be fixed, at least on arm64 and ppc64el, by the upload
of armadillo/1:10.6.2+dfsg-1.

Bug#993316: systemd: missing /lib/systemd/system/rpcbind.service file

[Michael Biebl]

Hi Niels

Am 31.08.21 um 18:07 schrieb Niels Thykier:


My thought is that this is not something I want in dh_link - dh_link has
no business second guessing the link values it gets.  Since dh_link runs
after dh_installsystemd, then we cannot even rely on dh_installsystemd
to perform a fix up either.


Nod.


Which begins to smell like that either people have to update their
dh_links calls/configuration OR we roll back the dh_installsystemd
change to move to /usr.  I am not particular fan of either.  :-/

Nevertheless, I am inclined to do a rollback and then punt on the "/ ->
/usr" migration track for now.


I'll see if I can compile a list of possibly affected packages.
If the number is low enough, I think updating the symlink manually is 
probably ok.


Regards,
Michael




OpenPGP_signature
Description: OpenPGP digital signature

Bug#992696: [Pkg-freeipa-devel] Bug#992696: 389-ds: 389-DS no longer starts since bullseye due to libjemalloc.so.2 not found

[Timo Aaltonen]

On 22.8.2021 15.15, Adam Reece wrote:


Aug 22 14:13:38 amun ns-slapd[14030]: [22/Aug/2021:14:13:38.279004946 +0200] - ERR - 
dse_read_one_file - The entry cn=schema in file 
/etc/dirsrv/slapd-amun.service/schema/60samba3.ldif (lineno: 1) is invalid, error code 20 
(Type or value exists) - object class sambaConfig: The name does not match the OID 
"1.3.6.1.4.1.7165.1.2.2.10". Another object class is already using the name or 
OID.
Aug 22 14:13:38 amun ns-slapd[14030]: [22/Aug/2021:14:13:38.280495362 +0200] - 
ERR - setup_internal_backends - Please edit the file to correct the reported 
problems and then restart the server.

That's your error.

The 389 packages didn't change since -2 and things work just fine on 
ci.debian.net and salsa (meaning the daemon starts), so I don't know how 
389 could be to blame here.


the libjemalloc thing is just noise, it's not a hard requirement AIUI.


--
t

Bug#993390: virtuoso-opensource: FTBFS: Dkmarshal.c:50:11: fatal error: rpc/types.h: No such file or directory

[Sebastian Ramacher]

Source: virtuoso-opensource
Version: 7.2.5.1+dfsg1-0.1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

| libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-fno-strict-aliasing -O2 -Wall -DNDEBUG -DPOINTER_64 
-I/<>/libsrc/Xml.new -DOPENSSL_NO_KRB5 -Dlinux -D_GNU_SOURCE 
-DFILE64 -D_LARGEFILE64_SOURCE -I../../libsrc -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -D_GNU_SOURCE -c Dkmem.c  -fPIC -DPIC -o 
.libs/libdksrv_la-Dkmem.o
| Dkmarshal.c:50:11: fatal error: rpc/types.h: No such file or directory
|50 | # include 
|   |   ^
| compilation terminated.
| make[5]: *** [Makefile:1169: libdksrv_la-Dkmarshal.lo] Error 1

https://buildd.debian.org/status/fetch.php?pkg=virtuoso-opensource=arm64=7.2.5.1%2Bdfsg1-0.1%2Bb1=1630424102=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#993332: marked as done (gnumeric: FTBFS: Can't exec "gtkdocize": No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 31 Aug 2021 16:18:34 +
with message-id 
and subject line Bug#993332: fixed in gnumeric 1.12.50-1
has caused the Debian Bug report #993332,
regarding gnumeric: FTBFS: Can't exec "gtkdocize": No such file or directory
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.)


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

This package fails to build from source on current sid.

>From a build log:

  dh_autoreconf --as-needed
  libtoolize: putting auxiliary files in '.'.
  libtoolize: copying file './ltmain.sh'
  libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
  libtoolize: copying file 'm4/libtool.m4'
  libtoolize: copying file 'm4/ltoptions.m4'
  libtoolize: copying file 'm4/ltsugar.m4'
  libtoolize: copying file 'm4/ltversion.m4'
  libtoolize: copying file 'm4/lt~obsolete.m4'
  libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
  You should update your 'aclocal.m4' by running aclocal.
  Can't exec "gtkdocize": No such file or directory at 
/usr/share/autoconf/Autom4te/FileUtils.pm line 293.
  autoreconf: error: gtkdocize failed with exit status: 2
  dh_autoreconf: error: autoreconf -f -i returned exit code 2
  make[1]: *** [debian/rules:33: override_dh_autoreconf] Error 25
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:29: binary-arch] Error 2
  dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2
 
A full log is available for instance at

 
https://buildd.debian.org/status/fetch.php?pkg=gnumeric=mips64el=1.12.48-1%2Bb3=1630062552=0

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: gnumeric
Source-Version: 1.12.50-1
Done: Dmitry Smirnov 

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated gnumeric package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 31 Aug 2021 22:43:25 +1000
Source: gnumeric
Architecture: source
Version: 1.12.50-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Closes: 993332
Changes:
 gnumeric (1.12.50-1) unstable; urgency=medium
 .
   * New upstream release.
   * Build-Depends += "gtk-doc-tools" (Closes: #993332)
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Drop unnecessary dependency on dh-autoreconf.
   * Build-Depends:
 = libgoffice-0.10-dev (>= 0.10.49~)
Checksums-Sha1:
 0554abf89bb865e2f7658afca83d5320025e18c7 2516 gnumeric_1.12.50-1.dsc
 1274acd3178d3dadf3f6a7226562bc4f07bf927f 18062104 gnumeric_1.12.50.orig.tar.xz
 499ba632e0ba1669cb4c9f0b202e3d483faa27ad 43276 gnumeric_1.12.50-1.debian.tar.xz
 5c6f968fb23beeb8a4fdbe419554bd24d0bd6e69 17566 
gnumeric_1.12.50-1_amd64.buildinfo
Checksums-Sha256:
 6fea4d447743bde6a34663982d818c89210c4981239c9eef48a321cdddfe8732 2516 
gnumeric_1.12.50-1.dsc
 758819ba1bd6983829f9e7c6d71a7fa20cd75a3652a271e5bb003d5d8bcc14b8 18062104 
gnumeric_1.12.50.orig.tar.xz
 378e8556664f9bfe84fc9f2db0c9874fd583384322d4119e31feca2571025062 43276 
gnumeric_1.12.50-1.debian.tar.xz
 26830deb8cb261da9eabe1263266fbc693a600b0cde39ebf57fce785dfb33394 17566 
gnumeric_1.12.50-1_amd64.buildinfo
Files:
 41850200d3c82d072250600ed7635079 2516 math optional gnumeric_1.12.50-1.dsc
 06868b655c5a231a4e9c1009ed701cc1 18062104 math optional 
gnumeric_1.12.50.orig.tar.xz
 d81f76259c662c6f633fdc66ed4c43c7 43276 math optional 
gnumeric_1.12.50-1.debian.tar.xz
 d67e9cefcf899bc74851c40f59499129 17566 math optional 
gnumeric_1.12.50-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAmEuTMAACgkQUra72VOW
jRugARAAxtKVllEqoSvrM7DMPrfost8wD5P3DqRnK5UmiAU+z/hKgWXxdB9OXu73
JPcPtMiVB0hqayy6DIEGL6yzYSvAbj69wUGJWmzDoNaeobEl7BJCYR6/GjmaLXcN

Processed: Re: Bug#993128: libvpx6: Unable to use camera or share screen on WebRTC conferences

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #993128 [libvpx6] libvpx6: Unable to use camera or share screen on WebRTC 
conferences
Bug #993222 [libvpx6] ffmpeg: Having libvpx 1.10.0-1 installed gives "ABI 
version mismatch" error
Added tag(s) moreinfo.
Added tag(s) moreinfo.

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

Bug#993128: libvpx6: Unable to use camera or share screen on WebRTC conferences

[Sebastian Ramacher]

Control: tags -1 moreinfo

On 2021-08-27 12:10:14 -0300, Paulo Roberto Alves de Oliveira (aka kretcheu) 
wrote:
> Package: libvpx6
> Version: 1.10.0-1
> Severity: important
> Tags: a11y
> 
> Dear Maintainer,
> 
> When we try do use camera or share screen on WebRTC like, Jitsi, 
> GoogleMeeting, it's not working.
> 
> Running Chromium on terminal we can see many error messages:
> 
> ERROR:video_stream_encoder.cc(1729)] Failed to encode frame. Error code: -7
> 
> Downgrading to version 1.9.0-1 it's working again.

Could you please retry with 1.10.0-2 which is now available in unstable?

Cheers

> 
> Thank's
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
> Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages libvpx6 depends on:
> ii  libc6  2.31-17
> 
> libvpx6 recommends no packages.
> 
> libvpx6 suggests no packages.
> 
> -- no debconf information
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#993350: xsane: Scanimage detects scanner but Xsane won't start it

[Hans Georg Colle]

Scanimage fails starting the scan, too. The result of "scanimage -d
epson2:libusb:002:005 --format png -o /home/georg/unsinn.png" is
"scanimage: sane_start: Operation not supported".
Georg

Bug#993316: systemd: missing /lib/systemd/system/rpcbind.service file

[Niels Thykier]

Michael Biebl:
> Am 30.08.21 um 18:31 schrieb Vincent Lefevre:
>> Package: systemd
>> Version: 247.9-1
>> Severity: critical
>> Justification: breaks unrelated software
>>
>> systemd provides a dangling symlink:
>>
>> $ ls -l /lib/systemd/system/portmap.service
>> lrwxrwxrwx 1 root root 15 2021-08-17 17:31:36
>> /lib/systemd/system/portmap.service -> rpcbind.service
>> $ ls -L /lib/systemd/system/portmap.service
>> ls: cannot access '/lib/systemd/system/portmap.service': No such file
>> or directory
> 
> This symlink is created via
> 
> dh_link lib/systemd/system/rpcbind.service
> lib/systemd/system/portmap.service
> 
> I wonder if debhelper can do something about this or if this is one of
> the cases where the package is best updated manually.
> 
> I suspect we have a few packages which create such aliasing symlinks via
> *.links files or explicit calls to dh_link
> 
> 
> Niels, what's your thought on this?
> 
> 
>> This breaks checkrestart:
> 
> [...]
> 
> Regards,
> Michael
> 

My thought is that this is not something I want in dh_link - dh_link has
no business second guessing the link values it gets.  Since dh_link runs
after dh_installsystemd, then we cannot even rely on dh_installsystemd
to perform a fix up either.

Which begins to smell like that either people have to update their
dh_links calls/configuration OR we roll back the dh_installsystemd
change to move to /usr.  I am not particular fan of either.  :-/

Nevertheless, I am inclined to do a rollback and then punt on the "/ ->
/usr" migration track for now.

~Niels

Bug#955107: marked as done (python3-sphinxcontrib.spelling: Uses obsolete API ‘Sphinx.info’)

[Debian Bug Tracking System]

Your message dated Tue, 31 Aug 2021 17:11:14 +0200
with message-id <20210831151114.4vivl64f36tah5j7@mornie>
and subject line Re: Bug#955107: python3-sphinxcontrib.spelling: Uses obsolete 
API ‘Sphinx.info’
has caused the Debian Bug report #955107,
regarding python3-sphinxcontrib.spelling: Uses obsolete API ‘Sphinx.info’
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.)


-- 
955107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-coverage
Version: 4.5.2+dfsg.1-4
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

python-coverage fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f coverage/htmlfiles/jquery.isonscreen.js
> dh_auto_build --buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python2 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/python.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/execfile.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/env.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/plugin_support.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/__init__.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/parser.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/__main__.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/html.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/cmdline.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/debug.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/misc.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/results.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/annotate.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/plugin.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/backunittest.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/pytracer.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/data.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/version.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/config.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/multiproc.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/templite.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/phystokens.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/control.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/summary.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/report.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/bytecode.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/collector.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/xmlreport.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/backward.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/pickle2json.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> copying coverage/files.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage
> creating 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage/fullcoverage
> copying coverage/fullcoverage/encodings.py -> 
> /<>/.pybuild/cpython2_2.7_coverage/build/coverage/fullcoverage
> running build_ext
> building 'coverage.tracer' extension
> creating build
> creating build/temp.linux-x86_64-2.7
> creating build/temp.linux-x86_64-2.7/coverage
> creating build/temp.linux-x86_64-2.7/coverage/ctracer
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python2.7 -c coverage/ctracer/datastack.c -o 
> build/temp.linux-x86_64-2.7/coverage/ctracer/datastack.o
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> 

Bug#993128: Info received (libvpx6: Unable to use camera or share screen on WebRTC conferences)

[Jacob Byrd]

upgrading to version 1.10.0-2 has solved the problem on both chromium and
firefox for me.

On Sun, Aug 29, 2021 at 2:06 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Multimedia Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 993...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 993128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993128
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Processed: Re: Bug#993350: xsane: Scanimage detects scanner but Xsane won't start it

[Debian Bug Tracking System]

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

> severity 993350 grave
Bug #993350 [xsane] xsane: Scanimage detects scanner but Xsane won't start it
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#992689: dino crashing with new gnome 40

[John Scott]

On Sun, 2021-08-22 at 13:43 -0400, Taowa wrote:
> I'm planning on doing an upload this week to fix it- ideally today.

Do you still got this, Taowa?


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

Bug#991606: marked as pending in ruby-libxml

[Sergio Durigan Junior]

On Tuesday, August 31 2021, Mattia Rizzolo wrote:

> On Mon, Aug 30, 2021 at 09:54:29PM +, Sergio Durigan Junior wrote:
>> Bug #991606 in ruby-libxml 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/ruby-team/ruby-libxml/-/commit/93e491e68dfef33329834820e45e911d01e3d89c
>
> I haven't tried, but doesn't this cause the tests to fail with libxml2
> << 2.9.12, such as what's currently in unstable?

Yes, it would cause regressions with libxml2 2.9.10.  This should only
be uploaded when libxml2 2.9.12 is also uploaded to unstable.  I think I
should have made it clearer in the changelog; sorry about that.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#993381: conserver FTBFS: checking whether the C compiler works... no

[Helmut Grohne]

Source: conserver
Version: 8.2.6-2
Tags: ftbfs
Severity: serious

conserver fails to build from source in unstable. I think the following
pieces are the relevant bits from the build log:

| dh_auto_configure -- \
|   --verbose \
|   --sysconfdir=/etc/conserver \
|   --with-openssl \
|   --with-pam \
|   --with-port=782 \
|   --with-logfile=/var/log/conserver/server.log \
|   --with-pidfile=/run/conserver/conserver.pid \
|   --with-libwrap \
|   --with-ipv6 \
|   --with-gssapi
|   ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --verbose 
--sysconfdir=/etc/conserver --with-openssl --with-pam --with-port=782 
--with-logfile=/var/log/conserver/server.log 
--with-pidfile=/run/conserver/conserver.pid --with-libwrap --with-ipv6 
--with-gssapi
| checking for port number specification... port '782'
| checking for secondary channel base port... port '0'
| checking for master conserver hostname... 'console'
| checking for client configuration filename... '/etc/conserver/console.cf'
| checking for configuration filename... '/etc/conserver/conserver.cf'
| checking for password filename... '/etc/conserver/conserver.passwd'
| checking for log filename... '/var/log/conserver/server.log'
| checking for PID filename... '/run/conserver/conserver.pid'
| checking for MAXMEMB setting... 16
| checking for connect() timeout... 10
| checking whether to trust reverse DNS... no
| checking whether to display extended messages... no
| checking whether to use -R paths as well as -L... no
| checking whether we are building for a Cyclades TS... no
| checking for gcc... gcc
| checking whether the C compiler works... no
| configure: error: in `/<>':
| configure: error: C compiler cannot create executables
| See `config.log' for more details
|   tail -v -n \+0 config.log
| ==> config.log <==
| ...
| configure:3463: checking whether the C compiler works
| configure:3485: gcc -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c  >&5
| conftest.c:8:26: warning: missing terminating " character
| 8 | #define CONFIGINVOCATION "./configure --build=x86_64-linux-gnu
|   |  ^
| conftest.c:9:1: error: expected identifier or '(' before '--' token
| 9 | --prefix=/usr
|   | ^~
| conftest.c:10:23: error: expected identifier or '(' before '/' token
|10 | --includedir=${prefix}/include
|   |   ^
| conftest.c:11:19: error: expected identifier or '(' before '/' token
|11 | --mandir=${prefix}/share/man
|   |   ^
| conftest.c:12:20: error: expected identifier or '(' before '/' token
|12 | --infodir=${prefix}/share/info
|   |^
| conftest.c:17:19: error: expected identifier or '(' before '/' token
|17 | --libdir=${prefix}/lib/x86_64-linux-gnu
|   |   ^
| conftest.c:30:14: warning: missing terminating " character
|30 | --with-gssapi"
|   |  ^
| conftest.c:30:14: error: missing terminating " character
| configure:3489: $? = 1
| configure:3529: result: no
| configure: failed program was:
| | /* confdefs.h */
| | #define PACKAGE_NAME "conserver"
| | #define PACKAGE_TARNAME "conserver"
| | #define PACKAGE_VERSION "8.2.6"
| | #define PACKAGE_STRING "conserver 8.2.6"
| | #define PACKAGE_BUGREPORT ""
| | #define PACKAGE_URL ""
| | #define CONFIGINVOCATION "./configure --build=x86_64-linux-gnu
| | --prefix=/usr
| | --includedir=${prefix}/include
| | --mandir=${prefix}/share/man
| | --infodir=${prefix}/share/info
| | --sysconfdir=/etc
| | --localstatedir=/var
| | --disable-option-checking
| | --disable-silent-rules
| | --libdir=${prefix}/lib/x86_64-linux-gnu
| | --runstatedir=/run
| | --disable-maintainer-mode
| | --disable-dependency-tracking
| | --verbose
| | --sysconfdir=/etc/conserver
| | --with-openssl
| | --with-pam
| | --with-port=782
| | --with-logfile=/var/log/conserver/server.log
| | --with-pidfile=/run/conserver/conserver.pid
| | --with-libwrap
| | --with-ipv6
| | --with-gssapi"
| | #define DEFPORT "782"
| | #define DEFBASEPORT "0"
| | #define MASTERHOST "console"
| | #define CLIENTCONFIGFILE SYSCONFDIR "/console.cf"
| | #define CONFIGFILE SYSCONFDIR "/conserver.cf"
| | #define PASSWDFILE SYSCONFDIR "/conserver.passwd"
| | #define LOGFILEPATH "/var/log/conserver/server.log"
| | #define PIDFILE "/run/conserver/conserver.pid"
| | #define MAXMEMB 16
| | #define CONNECTTIMEOUT 10
| | /* end confdefs.h.  */
| | 
| | int
| | main (void)
| | {
| | 
| |   ;
| |   return 0;
| | }
| configure:3534: error: in `/<>':
| configure:3536: error: C compiler cannot create 

Bug#993379: libyami-utils FTBFS: error: ‘void av_init_packet(AVPacket*)’ is deprecated [-Werror=deprecated-declarations]

[Helmut Grohne]

Source: libyami-utils
Version: 1.3.0-3
Severity: serious
Tags: ftbfs

libyami-utils fails to build from source in unstable. A build ends as
follows:

| g++ -DHAVE_CONFIG_H -I. -I..  -I../tests -I/usr/include/libyami  -I..   
-D__STDC_CONSTANT_MACROS -I/usr/include/x86_64-linux-gnu -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -Wall -Wno-unused-function -Wno-cpp 
-Wno-missing-braces -Werror -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
../tests/decodeinputavformat.o ../tests/decodeinputavformat.cpp
| ../tests/decodeinputavformat.cpp: In constructor 
‘DecodeInputAvFormat::DecodeInputAvFormat()’:
| ../tests/decodeinputavformat.cpp:36:29: error: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Werror=deprecated-declarations]
|36 | av_init_packet(_packet);
|   | ^
| In file included from /usr/include/x86_64-linux-gnu/libavcodec/bsf.h:30,
|  from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:44,
|  from 
/usr/include/x86_64-linux-gnu/libavformat/avformat.h:312,
|  from ../tests/decodeinputavformat.h:22,
|  from ../tests/decodeinputavformat.cpp:20:
| /usr/include/x86_64-linux-gnu/libavcodec/packet.h:488:6: note: declared here
|   488 | void av_init_packet(AVPacket *pkt);
|   |  ^~
| cc1plus: all warnings being treated as errors
| make[3]: *** [Makefile:645: ../tests/decodeinputavformat.o] Error 1
| make[3]: *** Waiting for unfinished jobs
| make[3]: Leaving directory '/<>/examples'
| make[2]: *** [Makefile:465: all-recursive] Error 1
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:397: all] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j8 returned exit code 2
| make: *** [debian/rules:6: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Helmut

Bug#974199: marked as done (libnet-nis-perl: ftbfs with glibc 2.31-14: rpc/rpc.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 31 Aug 2021 14:48:57 +
with message-id 
and subject line Bug#974199: fixed in libnet-nis-perl 0.44-2
has caused the Debian Bug report #974199,
regarding libnet-nis-perl: ftbfs with glibc 2.31-14: rpc/rpc.h: No such file or 
directory
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.)


-- 
974199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnet-nis-perl
Version: 0.44-1
Severity: important
Tags: sid bullseye patch

patch at
http://launchpadlibrarian.net/506401684/libnet-nis-perl_0.44-1build7_0.44-1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: libnet-nis-perl
Source-Version: 0.44-2
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libnet-nis-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 31 Aug 2021 16:35:06 +0200
Source: libnet-nis-perl
Architecture: source
Version: 0.44-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 974199
Changes:
 libnet-nis-perl (0.44-2) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Strip trailing slash from metacpan URLs.
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-Browser URL to cgit web frontend
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Remove Hendrik Frenzel from Uploaders. Thanks for your work!
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ gregor herrmann ]
   * debian/control: update Build-Depends for cross builds.
   * debian/watch: use uscan version 4.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 9 to 12.
   * Set debhelper-compat version in Build-Depends.
 .
   [ gregor herrmann ]
   * Add patch from CPAN RT to use libnsl2 if possible. (Closes: #974199)
   * Add necessary build dependencies for the nsl2 patch.
 Thanks to Matthias Klose for the Ubuntu debdiff.
   * Update years of packaging copyright.
   * Declare compliance with Debian Policy 4.6.0.
   * Set Rules-Requires-Root: no.
   * Bump debhelper-compat to 13.
   * Add /me to Uploaders.
   * debian/rules: enable all hardening flags.
Checksums-Sha1:
 778995105e8ee24744e3c32f21d22fba239a449c 2356 libnet-nis-perl_0.44-2.dsc
 4216a31e5328a9622e1e9afea193d0d3def0793a 3300 
libnet-nis-perl_0.44-2.debian.tar.xz
Checksums-Sha256:
 bbf71c5cbdf605f20ee09455f1ceaa6dbf84bd33fb6dfe0d6582d425e68d77db 2356 
libnet-nis-perl_0.44-2.dsc
 330bbda2c8b2d1a055bb0c06624c799756eee2c45759ce2546eeddd08663adc1 3300 
libnet-nis-perl_0.44-2.debian.tar.xz
Files:
 74ffb5c5e40d24cb13bae6f7911a5455 2356 perl optional libnet-nis-perl_0.44-2.dsc
 8d61365b517f5f6a91f0433ffd904a3e 3300 perl optional 
libnet-nis-perl_0.44-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmEuPwhfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZ41BAAwDlDD/x4u6FubqqEiDB2ZLtnlXlhGuUNTugw9+kg281YYnZ8onY6TmVi
33LuiHZQfzPEmjWtxgoZAnn77QFWnE9GumV5R9ZGUZU1FoHMOIb8ksNAgsDn3ymS
8ZnpggvYIQKQcfIGfJ6trWe2YM36JMP4SYVo+gEGSqyfwbyn3Oxmjm3wo+8EgE2B
JvcYkztW2fcq91JIxkeKt4b+mGxCzPxs66VjLnqBYaGJlMaYUbVnuQaUeU5lSR8a
JpGR1nTsKvfSq0eNEl2R6k0i4kQ4dE7hHtC8AzgdAmEM5GrmSA4FCHcrSiI710kR
BTByq0aEpEB3dgNyA8BLAA6Se/cuiMcYyseNNzW+6n/v6yc2sX62CfvKy6tRMtQJ
hB3xXLCHRTvSBEe8wYHdIJK2QMR8KEEXnpdMG1rCMNKDUQKcc6wgbfV8LFzLjcXU
dpRewYki2anCc2Ljftw07r8B8u9vQHi+9qpvVWVFQbWOlZQqxyd5OjG79ZrP0nID
CWOFVbnDpgXBv8zCml9tID3e0RZsamN0KCEZ/rdWl8rKEyj5fUaPM9qkzBMbRMyW
cYaDqe/ELgDUsKY+L4ekmSx/+51/tUA0o+GD11pw27jMNEnz+7DokwgJuMCEPcmn
vbW6H0LU+x637ErBneq0jhaC6bPPFbFpZPHKS2RWYaDF/J8FEJk=
=1B8S
-END PGP SIGNATURE End Message ---

Processed: Bug#974199 marked as pending in libnet-nis-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #974199 [libnet-nis-perl] libnet-nis-perl: ftbfs with glibc 2.31-14: 
rpc/rpc.h: No such file or directory
Added tag(s) pending.

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

Bug#974199: marked as pending in libnet-nis-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #974199 in libnet-nis-perl 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/perl-team/modules/packages/libnet-nis-perl/-/commit/3d3b2f3fbfcf71b210d75e3046ffe6b578c66ee2


Add patch from CPAN RT to use libnsl2 if possible.

Closes: #974199


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974199

Bug#961359: remem: diff for NMU version 2.12-7.1

[Boyuan Yang]

Control: tags -1 +patch  +pending
X-Debbugs-CC: j...@debian.org

Dear maintainer,

I've prepared an NMU for remem (versioned as 2.12-7.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards,
Boyuan Yang

diff -u remem-2.12/debian/rules remem-2.12/debian/rules
--- remem-2.12/debian/rules
+++ remem-2.12/debian/rules
@@ -4,9 +4,9 @@
 
 build:
dh_testdir
-   ./configure --mandir='$${prefix}/share/man' --prefix='/usr' \
+   dh_auto_configure -- \
--with-lispdir='/usr/share/emacs/site-lisp'
-   make
+   $(MAKE)
touch build
 
 clean:
diff -u remem-2.12/debian/changelog remem-2.12/debian/changelog
--- remem-2.12/debian/changelog
+++ remem-2.12/debian/changelog
@@ -1,3 +1,19 @@
+remem (2.12-7.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  
+  [ Boyuan Yang ]
+  * debian/source/format: Explicitly use "1.0" source format.
+
+  [ Clint Adams ]
+  * debian/postinst: Use mktemp instead of tempfile. (Closes: #961359)
+
+  [ Helmut Grohne ]
+  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure.
+  (Closes: #929276)
+
+ -- Boyuan Yang   Tue, 31 Aug 2021 10:20:30 -0400
+
 remem (2.12-7) unstable; urgency=low
 
   * Po-debconf translation updates:
only in patch2:
unchanged:
--- remem-2.12.orig/debian/source/format
+++ remem-2.12/debian/source/format
@@ -0,0 +1 @@
+1.0


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

Processed: remem: diff for NMU version 2.12-7.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch  +pending
Bug #961359 [src:remem] src:remem: use mktemp instead of tempfile
Ignoring request to alter tags of bug #961359 to the same tags previously set
Bug #961359 [src:remem] src:remem: use mktemp instead of tempfile
Added tag(s) pending.

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

Processed: bug 974199 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=132492, tagging 974199

[Debian Bug Tracking System]

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

> forwarded 974199 https://rt.cpan.org/Public/Bug/Display.html?id=132492
Bug #974199 [libnet-nis-perl] libnet-nis-perl: ftbfs with glibc 2.31-14: 
rpc/rpc.h: No such file or directory
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=132492'.
> tags 974199 + patch
Bug #974199 [libnet-nis-perl] libnet-nis-perl: ftbfs with glibc 2.31-14: 
rpc/rpc.h: No such file or directory
Ignoring request to alter tags of bug #974199 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#975191: re: rust-js-sys: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

[Bastian Germann]

On Wed, 2 Dec 2020 02:46:36 + peter green  wrote:

 > This will impact quite some other modules.

I agree that the current autoremoval list looks pretty scary, so I decided to 
do some
dependency analysis. It seems there are 5 source packages with direct or 
indirect hard
dependencies on rust-js-sys.

rust-www-sys
rust-ring
rust-rustls
rust-sct
rust-webpki


Hey,

I would like to get rustls migrating to bookworm but this is a blocker for it.
Can you please state if you want to fix this or would like help with it? I guess importing the 
current version will do it.


Thanks,
Bastian

Bug#937269: peframe: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

Am Sun, Sep 13, 2020 at 05:44:44PM +0200 schrieb Sascha Steinbiss:
> Hi Moritz,
> 
> >> Just an update: Python 3 compatibility is indeed introduced in the latest 
> >> upstream version, however, that version also adds some new dependencies 
> >> that would need to be packaged and pass NEW. For example, 
> >> python-virustotal-api, which has been in NEW for quite some time. I have 
> >> also looked at adding python-oletools, but that will also need new 
> >> dependencies of its own.
> >> I’ll try work on this eventually, unless someone else is interested and 
> >> has some spare time.
> > 
> > Are you still actively working on this one or should we rather remove 
> > peframe for now?
> 
> I am sorry to say that I am not at the moment. The number of dependencies 
> (and some license issues) to package the new version is currently exceeding 
> my non-work Debian time :?
> 
> Please feel free to remove it for now, unless someone wants to take over.

Ack. Given that noone stepped up for about a year now, I'll go ahead and file
a removal request.

Cheers,
 Moritz

Bug#993332: marked as pending in gnumeric

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #993332 in gnumeric 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/debian/gnumeric/-/commit/5939d6c00f61abf67d1f9147fe7331872a868dec


Build-Depends += "gtk-doc-tools" (Closes: #993332)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993332

Processed: Bug#993332 marked as pending in gnumeric

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #993332 [src:gnumeric] gnumeric: FTBFS: Can't exec "gtkdocize": No such 
file or directory
Added tag(s) pending.

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

Processed: python-xarray: autopkgtest regression on several architectures

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #983758 {Done: Alastair McKinstry } 
[src:python-xarray] python-xarray: autopkgtest regression on several 
architectures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-xarray/0.19.0-3.

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

Bug#983758: python-xarray: autopkgtest regression on several architectures

[Graham Inggs]

Control: reopen -1

Hi Alastair

This same test also fails on i386 [1].

tests/test_dataarray.py::TestDataArray::test_pad_constant FAILED [ 56%]

Regards
Graham


[1] https://ci.debian.net/packages/p/python-xarray/testing/i386/

Bug#991606: marked as pending in ruby-libxml

[Mattia Rizzolo]

On Mon, Aug 30, 2021 at 09:54:29PM +, Sergio Durigan Junior wrote:
> Bug #991606 in ruby-libxml 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/ruby-team/ruby-libxml/-/commit/93e491e68dfef33329834820e45e911d01e3d89c

I haven't tried, but doesn't this cause the tests to fail with libxml2
<< 2.9.12, such as what's currently in unstable?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#991606: ruby-libxml: test failures with libxml2 2.9.12

[Mattia Rizzolo]

On Fri, Aug 20, 2021 at 11:20:38PM +0530, Pirate Praveen wrote:
> Control: forwarded -1 https://github.com/xml4r/libxml-ruby/issues/172
> 
> On Wed, 28 Jul 2021 15:35:58 +0200 Mattia Rizzolo  wrote:
> > Source: ruby-libxml
> > Version:  3.2.0-1
> > Severity: serious
> 
> Do we keep serious severity for failure only in experimental? Don't we wait
> till libxml2 2.9.12 hits unstable to raise severity?

mh no.
sev:serious is very appropriate for something that is just about to land
in unstable RSN :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#993164: proftpd-core: When upgrading from Buster to Bullseyes, the installation of ProFTPd fails

[Andreas Günther]

Am Montag, 30. August 2021, 18:42:01 CEST schrieb Hilmar Preuße:
> 
> I would not expect that this works. Your specific proftp configuration
> needs to crypto and the wrap modules so I'd expect that the setup fails,
> b/c they could not be found.
> 
> However I still don't understand why the setup fails if they are at
> least in unpacked state.

> > I am still convinced that there is something wrong with this package.

Hi,

but I realized that now. The whole time the installer was bothered by a line 
in "/etc/proftpd/proftpd.conf", namely "IdentLookups off". I commented on this 
line and thus everything could be reinstalled and started successfully.

Best regards and thank you very much 

Andreas 

Bug#993355: haskell-hgettext: autopkgtest regressed in August 2020

[Graham Inggs]

Source: haskell-hgettext
Version: 0.1.31.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-CC: debian...@lists.debian.org

Hi Maintainer

Some time in August 2020, haskell-hgettext's autopkgtests regressed in
testing [1].
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/h/haskell-hgettext/testing/amd64/


autopkgtest [20:40:01]: test cabal-install-compatibility:
[---
Warning: No remote package servers have been specified. Usually you would have
one specified in the config file.
Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: example-0.1.0 (user goal)
[__1] next goal: example:setup.Cabal (dependency of example)
[__1] rejecting: example:setup.Cabal-3.0.1.0/installed-3.0... (conflict:
example => example:setup.Cabal>=1.8 && <1.25)
[__1] fail (backjumping, conflict set: example, example:setup.Cabal)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: example, example:setup.Cabal

autopkgtest [20:40:03]: test cabal-install-compatibility:
---]
autopkgtest [20:40:03]: test cabal-install-compatibility:  - - - - - -
- - - - results - - - - - - - - - -
cabal-install-compatibility FAIL non-zero exit status 1

Bug#993016: libdap: Includes rpc/types.h which is no longer provided by libc6-dev

[Sebastiaan Couwenberg]

On 8/31/21 10:02 AM, Aurelien Jarno wrote:
> On 2021-08-30 23:07, Aurelien Jarno wrote:
>> On 2021-08-30 20:15, Sebastiaan Couwenberg wrote:
>>> On 8/27/21 12:14 PM, Aurelien Jarno wrote:
 On 2021-08-26 13:27, Bas Couwenberg wrote:
> The recent changes in glibc break libdap and its rdeps:
>
>  In file included from /usr/include/libdap/XDRUtils.h:37,
>   from /usr/include/libdap/Sequence.h:50,
>   from libdap_headers.h:52,
>   from ogr_dods.h:44,
>   from ogrdodsdriver.cpp:29:
>  /usr/include/libdap/xdr-datatypes.h:16:10: fatal error: rpc/types.h: No 
> such file or directory
> 16 | #include 
>|  ^
>
> /usr/include/rpc/types.h was provided by libc6-dev in bullseye, but it is 
> no longer included in libc6-dev (2.31-17).

 The problem is that libdap has proper TI RPC support, but it doesn't
 export that information properly to libdap.pc and dap-config, sorry
 about that.

 Please find a patch attached to fix that.
>>>
>>> Thanks for the patch, I've prepared an NMU with it applied.
>>>
>>> I can confirm that it fixes the libdap issue breaking the gdal build.
>>> Unfortunately ecs.h from ogdi-dfsg still includes rpc/rpc.h also
>>> breaking the gdal build.
>>
>> It's normal keeps including rpc/rpc.h, but it should get its cflags
>> updated. It has just been binNMUed today, and with libogdi-dev version
>> 4.1.0+ds-5+b1, I get:
>>
>> $ /usr/bin/ogdi-config --cflags
>> -I/usr/include/ogdi -I/usr/include/tirpc
>> $ pkg-config --cflags ogdi
>> -I/usr/include/ogdi -I/usr/include/tirpc
>>
>> So that should be fixed already.
> 
> In pratice it doesn't work due to an issue with the gdal packaging.  The
> patch debian/patches/ogdi should be dropped.

Thanks for looking into this, I came to the same conclusion this morning:

 https://github.com/OSGeo/gdal/pull/4394#issuecomment-908892817

That just leave this libdap issue as a blocker.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: Bug#993262: digikam-private-libs: depends on libkf5akonadicontact5-20.08 which is not available anymore in Sid

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 release.debian.org
Bug #993262 [digikam-private-libs] digikam-private-libs: depends on 
libkf5akonadicontact5-20.08 which is not available anymore in Sid
Bug reassigned from package 'digikam-private-libs' to 'release.debian.org'.
No longer marked as found in versions digikam/4:7.1.0-2.
Ignoring request to alter fixed versions of bug #993262 to the same values 
previously set
> forcemerge 992948 -1
Bug #992948 {Done: Sebastian Ramacher } 
[release.debian.org] nmu: digikam_4:7.1.0-2
Bug #993262 [release.debian.org] digikam-private-libs: depends on 
libkf5akonadicontact5-20.08 which is not available anymore in Sid
Severity set to 'normal' from 'grave'
Marked Bug as done
Bug #992948 {Done: Sebastian Ramacher } 
[release.debian.org] nmu: digikam_4:7.1.0-2
Added tag(s) sid and bookworm.
Merged 992948 993262

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

Bug#993262: digikam-private-libs: depends on libkf5akonadicontact5-20.08 which is not available anymore in Sid

[Adrian Bunk]

Control: reassign -1 release.debian.org
Control: forcemerge 992948 -1

On Sun, Aug 29, 2021 at 06:47:24PM +0200, Sébastien KALT wrote:
> Package: digikam-private-libs
> Version: 4:7.1.0-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> Since last update of libkf5akonadicontact5 to version 4:21.08.0-1, digikam is
> not installable because digikam-private-libs depends on libkf5akonadicontact5
> version 20.08 :
> 
> # apt install digikam
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  digikam-private-libs : Depends: libkf5akonadicontact5-20.08
> E: Unable to correct problems, you have held broken packages.
> 
> digikam and digikam-private-libs where uninstalled during the dist-upgrade
> which upgraded libkf5akonadicontact5.

Thanks for the report, this has been fixed with a rebuild of digikam in 
unstable.

> Regards,
> 
> Sébastien

cu
Adrian

Bug#993316: systemd: missing /lib/systemd/system/rpcbind.service file

[Michael Biebl]

Am 31.08.21 um 10:17 schrieb Vincent Lefevre:


/etc/systemd/system/multi-user.target.wants/rpcbind.service -> 
/lib/systemd/system/rpcbind.service

though /lib/systemd/system/rpcbind.service doesn't exist.


That's a separate issue



OpenPGP_signature
Description: OpenPGP digital signature

Bug#993316: systemd: missing /lib/systemd/system/rpcbind.service file

[Michael Biebl]

Am 30.08.21 um 18:31 schrieb Vincent Lefevre:

Package: systemd
Version: 247.9-1
Severity: critical
Justification: breaks unrelated software

systemd provides a dangling symlink:

$ ls -l /lib/systemd/system/portmap.service
lrwxrwxrwx 1 root root 15 2021-08-17 17:31:36 /lib/systemd/system/portmap.service 
-> rpcbind.service
$ ls -L /lib/systemd/system/portmap.service
ls: cannot access '/lib/systemd/system/portmap.service': No such file or 
directory


This symlink is created via

dh_link lib/systemd/system/rpcbind.service 
lib/systemd/system/portmap.service


I wonder if debhelper can do something about this or if this is one of 
the cases where the package is best updated manually.


I suspect we have a few packages which create such aliasing symlinks via 
*.links files or explicit calls to dh_link



Niels, what's your thought on this?



This breaks checkrestart:


[...]

Regards,
Michael



OpenPGP_signature
Description: OpenPGP digital signature

Bug#993333: weechat: FTBFS: Target "irc" links to item " use `command -v' in scripts instead

[Sébastien Helleu]

On Tue, Aug 31, 2021 at 12:18:52AM +0300, Niko Tyni wrote:
> Source: weechat
> Version: 3.0.1-1
> Severity: serious
> Tags: ftbfs sid bookworm
> 
> This package fails to build from source on current sid.
> 
> It looks like this regressed with the recent change in debianutils
> that made /usr/bin/which output a deprecation warning.
> 
> >From a build log:
> 
>-- Found GCRYPT: /usr/bin/which: this version of `which' is deprecated; 
> use `command -v' in scripts instead.
>-L/usr/lib/x86_64-linux-gnu -lgcrypt  
>
>[...]
>
>CMake Error at src/plugins/irc/CMakeLists.txt:20 (add_library):
>  Target "irc" links to item " use `command -v' in scripts instead.
>
>  -L/usr/lib/x86_64-linux-gnu -lgcrypt" which has leading or trailing
>  whitespace.  This is now an error according to policy CMP0004.
> 
> A full log is available at
> 
>   
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/weechat.html
> 
> -- 
> Niko Tyni   nt...@debian.org

Hi Niko,

Thanks for your report.

The problem is indirectly caused by the deprecation of the "which" command in
the package debianutils.  I opened the Debian bug #993244 two days ago (feel
free to merge bugs if needed).

The "which" command seems to be used inside CMake, not in WeeChat itself, but
this breaks compilation of WeeChat (I suppose like many other packages).

For now I have no fix available on WeeChat side.  If the warning on stderr in
"which" command stays as-is, I think CMake has to be fixed.

-- 
Sébastien Helleu

web: weechat.org / flashtux.org
irc: FlashCode @ irc.libera.chat

Bug#993316: systemd: missing /lib/systemd/system/rpcbind.service file

[Vincent Lefevre]

On 2021-08-31 02:30:00 +0200, Vincent Lefevre wrote:
> On 2021-08-30 20:59:21 +0200, Michael Biebl wrote:
> > Am 30.08.21 um 18:31 schrieb Vincent Lefevre:
> > > $ ls -l /lib/systemd/system/portmap.service
> > > lrwxrwxrwx 1 root root 15 2021-08-17 17:31:36 
> > > /lib/systemd/system/portmap.service -> rpcbind.service
> > > $ ls -L /lib/systemd/system/portmap.service
> > > ls: cannot access '/lib/systemd/system/portmap.service': No such file or 
> > > directory
> > > 
> > > This breaks checkrestart:
> > 
> > This sounds like a bug in checkrestart, fwiw. Does it really have the path
> > /lib/systemd/system/portmap.service hard-coded?
> 
> No, it seems to read all .service files under /lib/systemd/system,
> and failures seem to make the program abort. Perhaps it should
> detect dangling symlinks (though I suppose that they are unexpected).

I also note that /lib/systemd/system/portmap.service is not the only
issue. One has:

/etc/systemd/system/multi-user.target.wants/rpcbind.service -> 
/lib/systemd/system/rpcbind.service

though /lib/systemd/system/rpcbind.service doesn't exist.

rpcbind.service is only available as:
/usr/lib/systemd/system/rpcbind.service

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#993016: libdap: Includes rpc/types.h which is no longer provided by libc6-dev

[Aurelien Jarno]

On 2021-08-30 23:07, Aurelien Jarno wrote:
> On 2021-08-30 20:15, Sebastiaan Couwenberg wrote:
> > On 8/27/21 12:14 PM, Aurelien Jarno wrote:
> > > On 2021-08-26 13:27, Bas Couwenberg wrote:
> > >> The recent changes in glibc break libdap and its rdeps:
> > >>
> > >>  In file included from /usr/include/libdap/XDRUtils.h:37,
> > >>   from /usr/include/libdap/Sequence.h:50,
> > >>   from libdap_headers.h:52,
> > >>   from ogr_dods.h:44,
> > >>   from ogrdodsdriver.cpp:29:
> > >>  /usr/include/libdap/xdr-datatypes.h:16:10: fatal error: rpc/types.h: No 
> > >> such file or directory
> > >> 16 | #include 
> > >>|  ^
> > >>
> > >> /usr/include/rpc/types.h was provided by libc6-dev in bullseye, but it 
> > >> is no longer included in libc6-dev (2.31-17).
> > > 
> > > The problem is that libdap has proper TI RPC support, but it doesn't
> > > export that information properly to libdap.pc and dap-config, sorry
> > > about that.
> > > 
> > > Please find a patch attached to fix that.
> > 
> > Thanks for the patch, I've prepared an NMU with it applied.
> > 
> > I can confirm that it fixes the libdap issue breaking the gdal build.
> > Unfortunately ecs.h from ogdi-dfsg still includes rpc/rpc.h also
> > breaking the gdal build.
> 
> It's normal keeps including rpc/rpc.h, but it should get its cflags
> updated. It has just been binNMUed today, and with libogdi-dev version
> 4.1.0+ds-5+b1, I get:
> 
> $ /usr/bin/ogdi-config --cflags
> -I/usr/include/ogdi -I/usr/include/tirpc
> $ pkg-config --cflags ogdi
> -I/usr/include/ogdi -I/usr/include/tirpc
> 
> So that should be fixed already.

In pratice it doesn't work due to an issue with the gdal packaging.  The
patch debian/patches/ogdi should be dropped.

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: Re: Bug#993222: ffmpeg: Having libvpx 1.10.0-1 installed gives "ABI version mismatch" error

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libvpx6 1.10.0-1
Bug #993222 [ffmpeg] ffmpeg: Having libvpx 1.10.0-1 installed gives "ABI 
version mismatch" error
Bug reassigned from package 'ffmpeg' to 'libvpx6'.
No longer marked as found in versions ffmpeg/7:4.4-5.
Ignoring request to alter fixed versions of bug #993222 to the same values 
previously set
Bug #993222 [libvpx6] ffmpeg: Having libvpx 1.10.0-1 installed gives "ABI 
version mismatch" error
Marked as found in versions libvpx/1.10.0-1.
> forcemerge 993128 -1
Bug #993128 [libvpx6] libvpx6: Unable to use camera or share screen on WebRTC 
conferences
Bug #993222 [libvpx6] ffmpeg: Having libvpx 1.10.0-1 installed gives "ABI 
version mismatch" error
Severity set to 'serious' from 'normal'
Added tag(s) a11y.
Merged 993128 993222
> tags 993128 - a11y
Bug #993128 [libvpx6] libvpx6: Unable to use camera or share screen on WebRTC 
conferences
Bug #993222 [libvpx6] ffmpeg: Having libvpx 1.10.0-1 installed gives "ABI 
version mismatch" error
Removed tag(s) a11y.
Removed tag(s) a11y.

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

Processed: notfound 993172 in libgcc-s1/11.2.0-3

[Debian Bug Tracking System]

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

> notfound 993172 libgcc-s1/11.2.0-3
Bug #993172 [gcc-11-base] gcc-11-base: i386 (Geode LX): latest testing 
migration produces sig ILL (due to #993162 ?)
The source libgcc-s1 and version 11.2.0-3 do not appear to match any binary 
packages
Ignoring request to alter found versions of bug #993172 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: notfound 993172 in gcc-11-mipsen/11.2.0-3

[Debian Bug Tracking System]

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

> notfound 993172 gcc-11-mipsen/11.2.0-3
Bug #993172 [gcc-11-base] gcc-11-base: i386 (Geode LX): latest testing 
migration produces sig ILL (due to #993162 ?)
No longer marked as found in versions gcc-11-mipsen/11.2.0-3.
> thanks
Stopping processing here.

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

Bug#993345: marked as done (debhelper: Regression: Undefined subroutine ::Debhelper::Buildsystem::cmake::get_buildoption)

[Debian Bug Tracking System]

Your message dated Tue, 31 Aug 2021 06:03:27 +
with message-id 
and subject line Bug#993345: fixed in debhelper 13.5.1
has caused the Debian Bug report #993345,
regarding debhelper: Regression: Undefined subroutine 
::Debhelper::Buildsystem::cmake::get_buildoption
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.)


-- 
993345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 13.5
Severity: grave
X-Debbugs-CC: ni...@thykier.net

A regression appears when upgrading from debhelper/13.4.1 to debhelper/13.5:

% dh_auto_test --buildsystem=cmake
Undefined subroutine ::Debhelper::Buildsystem::cmake::get_buildoption
called at /usr/share/perl5/Debian/Debhelper/Buildsystem/cmake.pm line 175.

See https://buildd.debian.org/status/package.php?p=wbxml2 for real example.

-- 
Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 13.5.1
Done: Niels Thykier 

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 31 Aug 2021 05:43:35 +
Source: debhelper
Architecture: source
Version: 13.5.1
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Closes: 993345
Changes:
 debhelper (13.5.1) unstable; urgency=medium
 .
   [ Paul Wise ]
   * cmake.pm: make it possible to override dh provided ctest arguments
 .
   [ Niels Thykier ]
   * cmake.pm: Add missing import which broke cmake related builds.
 Thanks to Boyuan Yang for reporting the issue.
 (Closes: #993345)
Checksums-Sha1:
 ce9e63c55120f2b694c74a45bec6a302e85b463c 1789 debhelper_13.5.1.dsc
 f0fdb53b5615c6068d351bc2eea005280c16cb2d 563280 debhelper_13.5.1.tar.xz
 0d59fef27fd9eeca33595e813dd3d35627f65783 5014 debhelper_13.5.1_source.buildinfo
Checksums-Sha256:
 200498cdfa2460669eb154c1757739cfe0697004eadc4115053c478c07614e30 1789 
debhelper_13.5.1.dsc
 390c3c8fd008aa74b0de1e790bc1e157fd3ba1b1901146679ee9b43dce97f04b 563280 
debhelper_13.5.1.tar.xz
 91721bdeea752dd10aef377a6c21dc8df41d234accb8badba5d17261fc3840f1 5014 
debhelper_13.5.1_source.buildinfo
Files:
 b319e3cb31d92658f4bcde5218126266 1789 devel optional debhelper_13.5.1.dsc
 10a87e68f8c9822d9c78044ea2716ce8 563280 devel optional debhelper_13.5.1.tar.xz
 d0982965672fa7145719be9d8ac014b2 5014 devel optional 
debhelper_13.5.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE8f9dDX4ALfD+VfsMplt42+Z8eqwFAmEtwh4SHG5pZWxzQHRo
eWtpZXIubmV0AAoJEKZbeNvmfHqsaLQP+wTg1FXPrPYFynglYBU55nRBujJtL/QL
CBcANFJ8ljKlNCMX6wSOf5hDS1rcUTEFVG/BS967p6H25EiNcIMOIKfIGf5f77Xc
+rZXhG7Nx4oPrDRKDn99xyasN2wqaY4UCnqMZUxLfqCcjMWp6MJN/5aKCDodGllp
lxw4uPqXHUJDjN6rp852hnICrEqeLuV1fgS0x8gB7URkTuvnZ+pf0gUGJrn9jtJ8
1KyYj3vpu9O13XuxqwA6jDJ3MWCLhvHcQsf5lo/skXL8PzX5FCZeDNx7PJ5QQPKG
ti/vKm1/lHxOrTf31Y/vLd1ISrwW6EReqq4O3TX5wySp3bh7rPNUNapc8Xlh8ZCN
Yf9lqDiSuj38k3qQNJIaIO+BqD2aNQA5KlD8Amtwp1Z2mWDxuQRWKZ3Xq3jVg5yt
zPSOKyBJ0cPPRy+bVjRMR/Cs7qV3Olngg7Vo+9VXbNYZWWObYWoejjdecVTlKUjX
eKznW3w3vkLvehjB5SDpGEKY3WtDPmIp+efBkU1evRxPbuHtwxii/CW1AfEodIUA
7/SCac1sbgdGYUrdphHfMNh4dK4S4F9w42yoZQXRcM6qRubcX43oWO6yRGjQfFoa
s+6Qm2hxx7Qbn6JbweKPtf1PrZvKO+XyOYfdAZFni6u30gxiJjy+24+CBUwI/0pU
VpHJOCOmcGGH
=hy4s
-END PGP SIGNATURE End Message ---