Bug#964682: marked as done (icu: FTBFS: dh_auto_test: error: cd source && make -j4 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jul 2020 05:34:26 +
with message-id 
and subject line Bug#964682: fixed in icu 67.1-3
has caused the Debian Bug report #964682,
regarding icu: FTBFS: dh_auto_test: error: cd source && make -j4 check 
VERBOSE=1 returned exit code 2
to be marked as done.

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

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


-- 
964682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icu
Version: 67.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/source'
> make[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
> rule.
> verifying that icu-config --selfcheck can operate
> verifying that make -f Makefile.inc selfcheck can operate
> FAIL: Makefile.inc could not run properly.
> make[3]: *** [Makefile:243: xcheck-local] Error 1
> make[3]: Leaving directory '/<>/source'
> make[2]: *** [Makefile:153: check-recursive] Error 2
> make[2]: Leaving directory '/<>/source'
> dh_auto_test: error: cd source && make -j4 check VERBOSE=1 returned exit code 
> 2

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/icu_67.1-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: icu
Source-Version: 67.1-3
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated icu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Jul 2020 06:51:53 +0200
Source: icu
Architecture: source
Version: 67.1-3
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 964682
Changes:
 icu (67.1-3) unstable; urgency=medium
 .
   * Don't run self-tests parallel until make-dfsg is fixed (closes: #964682).
Checksums-Sha1:
 7c6ffc81c260dc9464e9ce6f3219f25f734d89ee 2219 icu_67.1-3.dsc
 b1f5fe81415c72b6f400e0df393e92c06e754dfc 24076 icu_67.1-3.debian.tar.xz
Checksums-Sha256:
 0a574a9a42191ebc8206cc34866691feeac288cce61dc9f986f4d5650ccfe293 2219 
icu_67.1-3.dsc
 afdaf67e22b0d09b7431a6879dc77cb489c721a459857f5ce4e0b86b4d3d2ac1 24076 
icu_67.1-3.debian.tar.xz
Files:
 250fdb3737f29a5dfc37890fcc5bc071 2219 libs optional icu_67.1-3.dsc
 b994dea780e5f463990169fe5d5fe7f7 24076 libs optional icu_67.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl8OkioACgkQ3OMQ54ZM
yL/0OhAAg2U883rR5rRCXMQ5cifAMSv/6ylbuTb9Yf7t+7yonfFJYAJxIPqxNRSm
QqavUoLxcgjRniH4LK/btMfCCJWrmWYvhELIJhqeloJaf6mZymzn+C6ECCOylBBW
7ZWYTvzMo8M9U5caOf8IOS+gU+/WX+s/bNIB0KQvEOtXzhiC7QmmnemiQavxDN0t
1bqJNqPKFXesVzoZ8uak+MmcCUVWPiyVePn+lCdAprjFk7c3CJkBvDXysXJPIgBx
TyCp10Fikz1AArCPP6Ynh1lqnKRvDp08DqgouGOv8eJlab/ydJVx4X5g2D+3uWDJ
W+W8H7zeLJnA4HqSu8laaTqq+9Jq3sVnnAY5exCtUYfYUkgTAWtr3Xu1qInOCulm
wfeu4W3GNlaeOgHQ6y9uJn2sLcYBlBfGBMam6y/QSFG2V0khb4LNup7eLRTWEX32
VknhRbhlM5fVIu6z6t8HlUFnnQPTs+6c+BMktQR/AcBcGja1vKYhgbqF07fS7z9n
o3pepqX2RcpVGBZrym0V0CY1A9wMNB5eWlB6w98Qrmz/8bzpg7t5PXsJ52bhU4sA
li+K3ZWx80I7NUcFHC5saXRauosrf8Zu8FdR/VjKtE5NisqWxDCCd2+yYhVhGFKw
tcweznRBGVo8/WZEI/bUPw3NoQRCELbhw/RspSO7hzhV77PGBzo=
=WJc8
-END PGP SIGNATURE End Message ---

Processed: severity of 941175 is grave

[Debian Bug Tracking System]

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

> severity 941175 grave
Bug #941175 [lptools] lp-shell: invalid syntax error on start
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#963862: marked as done (debug-me: FTBFS: bad base64 data)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jul 2020 03:03:46 +
with message-id 
and subject line Bug#963862: fixed in debug-me 1.20190926-2
has caused the Debian Bug report #963862,
regarding debug-me: FTBFS: bad base64 data
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.)


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

This package fails to build on current sid.

>From my build log:

  Configuring debug-me-1.20190926...
  Warning: Instead of 'ghc-options: -XNoMonadFailDesugaring' use 'extensions:
  NoMonadFailDesugaring'
  Preprocessing executable 'debug-me' for debug-me-1.20190926..
  Building executable 'debug-me' for debug-me-1.20190926..
  
  on the commandline: warning:
  -XNoMonadFailDesugaring is deprecated: MonadFailDesugaring is now the 
default behavior
  [ 1 of 32] Compiling DotDir   ( DotDir.hs, 
dist/build/debug-me/debug-me-tmp/DotDir.o )
  [ 2 of 32] Compiling JSON ( JSON.hs, 
dist/build/debug-me/debug-me-tmp/JSON.o )
  [ 3 of 32] Compiling Memory   ( Memory.hs, 
dist/build/debug-me/debug-me-tmp/Memory.o )
  [ 4 of 32] Compiling Output   ( Output.hs, 
dist/build/debug-me/debug-me-tmp/Output.o )
  [ 5 of 32] Compiling Pty  ( Pty.hs, 
dist/build/debug-me/debug-me-tmp/Pty.o )
  [ 6 of 32] Compiling ServerList   ( ServerList.hs, 
dist/build/debug-me/debug-me-tmp/ServerList.o )
  [ 7 of 32] Compiling Session  ( Session.hs, 
dist/build/debug-me/debug-me-tmp/Session.o )
  [ 8 of 32] Compiling SessionID( SessionID.hs, 
dist/build/debug-me/debug-me-tmp/SessionID.o )
  [ 9 of 32] Compiling Val  ( Val.hs, 
dist/build/debug-me/debug-me-tmp/Val.o )
  
  Val.hs:47:16: error:
  • Could not deduce (MonadFail m) arising from a use of ‘fail’
from the context: Monad m
  bound by the type signature for:
 unb64 :: forall (m :: * -> *). Monad m => T.Text -> m 
B.ByteString
  at Val.hs:45:1-44
Possible fix:
  add (MonadFail m) to the context of
the type signature for:
  unb64 :: forall (m :: * -> *). Monad m => T.Text -> m B.ByteString
  • In the expression: fail "bad base64 data"
In the first argument of ‘either’, namely
  ‘(\ _ -> fail "bad base64 data")’
In the expression:
  either
(\ _ -> fail "bad base64 data")
return
(B64.decode $ T.encodeUtf8 t)
 |
  47 | (\_ -> fail "bad base64 data")
 |^^
  make[2]: *** [Makefile:30: debug-me] Error 1
  make[2]: Leaving directory '/<>'
 
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: debug-me
Source-Version: 1.20190926-2
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated debug-me 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, 14 Jul 2020 19:44:25 -0700
Source: debug-me
Architecture: source
Version: 1.20190926-2
Distribution: unstable
Urgency: medium
Maintainer: Sean Whitton 
Changed-By: Sean Whitton 
Closes: 963862
Changes:
 debug-me (1.20190926-2) unstable; urgency=medium
 .
   * Fix build (Closes: #963862):
 - Patch Val.hs for recent ghc: replace type constraint Monad -> MonadFail
 - Patch Server.hs for recent Network.WebSockets: hide import of
   Network.WebSockets.serverPort.
Checksums-Sha1:
 f235523c6d0c899a5c2ec90b523052882dc053ab 2972 debug-me_1.20190926-2.dsc
 6dd959e041f7ad62b7c7207247cf9499350a251f 16612 
debug-me_1.20190926-2.debian.tar.xz
Checksums-Sha256:
 e338353fb0c2d7f2a344b6f21832e8e61c56e8a328f97cc8e249083f9b086f95 2972 
debug-me_1.20190926-2.dsc
 8df23d35287a53379599e7c9703fad9f5e3b8541713612c5b86c561ca00f9e38 16612 
debug-me_1.20190926-2.debian.tar.xz
Files:
 

Processed: tags 907496 unreproducible

[Debian Bug Tracking System]

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

> tags 907496 unreproducible
Bug #907496 {Done: Aloïs Micard } [libcurlpp0] libcurlpp0: 
Always fails with "No URL set!"
Ignoring request to alter tags of bug #907496 to the same tags previously set
> --
Stopping processing here.

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

Processed: add patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #961230 [src:guile-2.2] guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: 
alternatives priority expects min version < 1000.
Added tag(s) patch.

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

Processed: add patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #961280 [src:guile-3.0] guile-3.0 FTBFS with make-dfsg/4.3-1: ERROR: 
alternatives priority expects min version < 1000
Added tag(s) patch.

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

Processed: add patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #961295 [src:guile-2.0] guile-2.0 FTBFS with make-dfsg/4.3-1: ERROR: 
alternatives priority expects min version < 1000
Added tag(s) patch.

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

Bug#961230: add patch

[Matthias Klose]

Control: tags -1 + patch

patch at
http://launchpadlibrarian.net/488576218/guile-2.2_2.2.7+1-5build1_2.2.7+1-5ubuntu1.diff.gz

Bug#963446: marked as done (cross-toolchain-base-ports: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 22:18:35 +
with message-id 
and subject line Bug#963446: fixed in cross-toolchain-base-ports 38
has caused the Debian Bug report #963446,
regarding cross-toolchain-base-ports: FTBFS: dpkg-buildpackage: error: fakeroot 
debian/rules clean subprocess returned exit status 2
to be marked as done.

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

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


-- 
963446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cross-toolchain-base-ports
Version: 37
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> debian/kernelarch.make:5: *** empty variable name.  Stop.
> dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> exit status 2
> 
> Build finished at 2020-06-21T07:14:36Z

The full build log is available from:
   
http://qa-logs.debian.net/2020/06/20/cross-toolchain-base-ports_37_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: cross-toolchain-base-ports
Source-Version: 38
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated 
cross-toolchain-base-ports 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, 14 Jul 2020 23:53:21 +0200
Source: cross-toolchain-base-ports
Architecture: source
Version: 38
Distribution: unstable
Urgency: medium
Maintainer: Cross Toolchain Base Team 

Changed-By: Matthias Klose 
Closes: 963446
Changes:
 cross-toolchain-base-ports (38) unstable; urgency=medium
 .
   * Build using glibc 2.31-1.
   * Build using gcc 10.1.0-5.
   * Build using linux 5.7.
   * Use the linux source version for the Built-Using info.
   * Fix build with make 4.3. Closes: #963446.
Checksums-Sha1:
 f44a0b4e670964d9b9a63d5d4091477d90edad56 6206 cross-toolchain-base-ports_38.dsc
 28cbb60ad39207b4041d2d301d1bda30349a1769 42404 
cross-toolchain-base-ports_38.tar.xz
 5b48b328060012771e3fb19043a03adc4d060947 8211 
cross-toolchain-base-ports_38_source.buildinfo
Checksums-Sha256:
 40b591759cdbbcd4b9c295cc0c83fde5c4b3986f258995cb9f880c59060babb4 6206 
cross-toolchain-base-ports_38.dsc
 e03dcde6bf4cf665aad976a388361bb7a44e420a4342e46312620b1e4a00e521 42404 
cross-toolchain-base-ports_38.tar.xz
 9a4b818efd9571e71b9126b0b0571039152759079f7333c33d83fe9140103291 8211 
cross-toolchain-base-ports_38_source.buildinfo
Files:
 8d60e456bbc32f6cdd9977b2cfc7718f 6206 devel optional 
cross-toolchain-base-ports_38.dsc
 bae21a0f70b96e72b3ef68c2050c2dd0 42404 devel optional 
cross-toolchain-base-ports_38.tar.xz
 fbf55e93d506e98180b01cfc7f7b7ae0 8211 devel optional 
cross-toolchain-base-ports_38_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl8OKfAQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9QWLEAC5RQYOzJJwdm/+2d3gdoPXncrMnEGAZ+Ev
rWvLpchgQzswqpDYl+nWtEKsjfy3UkNvZ4klma8sjiW4J7wo3ly5jsnxJXZaFqRe
daWBVgDPux4FdAm3VVzIVbEE7FrQ60O5pLannTNU6SgrV5Z7+pf2s+fEjIQaTOXa
OozIeH1WgRw8OPbzXoaPSCBou41jGrfkSBvO5Gx7OLUrbBD4h/3hRLs2C08v4Wqt
TJvBvat4EJ1lvGoy6DiSiSVM8Oi89WIZYlgmAbMxiH48AcfAKOAP9TsQT97F9VPs
430tC+j494fof8p5sJhwDMn9FTNMQW6+OPzW+871mfS1yr8I8YotDGpX6it1j5Jm
0D34IX4Zfk8M+n/yJaqXe9h5vunYmLsiUboPjG45Tx3px/gRxSHrUWyEuOuXL6s/
CrsIa6PmkTRvgo363B+7TIHuR/YC8UhexWhL8YEdiMgnIWKP+qifs2hs3ZJm2pxS
vI38F3aDNlF3AEAsLpZtWN3NDZg5xt+y6CoWOYvmj7F47DoWoWClFe37Uh4VJR3c

Bug#960762: [Pkg-libvirt-maintainers] Bug#960762: libvirt: random (?) test hangs

[Andrea Bolognani]

On Fri, Jul 03, 2020 at 12:04:16AM +0200, Andrea Bolognani wrote:
> On Wed, Jul 01, 2020 at 09:24:00AM +0200, Guido Günther wrote:
> > On Tue, Jun 30, 2020 at 09:28:34PM +0200, Andrea Bolognani wrote:
> > > Has anyone managed to reproduce this? I've built 6.0.0-7 from source
> > > in a tight loop 100 times, both in a sid:i386 chroot via cowbuilder
> > > and in a sid:i386 VM, without encountering a single failure.
> > 
> > I tried to reproduce too when this came in and couldn't.
> 
> Okay, let's assume it was a temporary glitch then - at least until
> another build fails for the same reason.

We've made three uploads in a row now with zero issues on i386, so
at this point I would say it's fair to assume this one failure was
just a fluke. I vote for closing the bug and unblocking migrations
to testing.

-- 
Andrea Bolognani 
Resistance is futile, you will be garbage collected.


signature.asc
Description: PGP signature

Processed: tag 907496 unreproducible

[Debian Bug Tracking System]

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

> tag 907496 unreproducible
Bug #907496 {Done: Aloïs Micard } [libcurlpp0] libcurlpp0: 
Always fails with "No URL set!"
Added tag(s) unreproducible.
> --
Stopping processing here.

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

Bug#963628: [Pkg-javascript-devel] Bug#963628: Bug#963628: Node-jest fails with: Error: Cannot find module 'import-local'

[Xavier]

Le 14/07/2020 à 22:06, Xavier a écrit :
> Le 28/06/2020 à 09:32, Xavier a écrit :
>> Control: severity -1 grave
>>
>> Le 27/06/2020 à 23:31, Nilesh Patra a écrit :
>>>
>>>
>>> On Sun, 28 Jun 2020, 02:45 Xavier, >> > wrote:
>>>
>>> Control: severity -i grave
>>>
>>>
>>> Thanks.
>>>
>>>
>>> Le 24/06/2020 à 21:18, Nilesh Patra a écrit :
>>> > Package: node-jest
>>> > Severity: serious
>>> >
>>> > Dear Maintainer,
>>> >
>>> > Node-jest fails with the following on all the node-modules I've
>>> tried yet.
>>> > Sample examples on
>>>
>>> Work needed for node-jest:
>>>  * add babel-plugin-istanbul; proposition: add it in node-babel7
>>>
>>>
>>> It's good.
>>> Would you mind discussing this bit on the list?
>>
>> pkg-js list receives messages related to this bug
>>
>>>  * update and fix node-jsdom
>>>  * add missing components
>>>
>>>
>>> Noted.
>>>
>>>
>>> Here is the list of missing modules (mix of node-jest and node-jsdom):
>>
>> jsdom:
>>  * data-urls
>>  * domexception
>>  * html-encoding-sniffer
>>  * w3c-hr-time
>>  * whatwg-encoding
>>  * whatwg-mimetype
>>  * whatwg-url
>>  * xml-name-validator
> 
> Hi all,
> 
> after fixing node-jsdom, these modules are required for jest:
>  * astral-regex
>  * babel-plugin-istanbul
>  * babel-preset-current-node-syntax
>  * fast-json-stable-stringify
>  * is-generator-fn
>  * makeerror
>  * natural-compare
>  * p-each-series
>  * p-reduce
>  * sane
>  * string-length
>  * supports-hyperlinks
>  * terminal-link
>  * throat
>  * tmpl
>  * walker

+ import-local and realpath-native

> I suggests to embed babel* in node-babel7 and others in node-jest. What
> are your advises ?
> 

Bug#963628: [Pkg-javascript-devel] Bug#963628: Bug#963628: Node-jest fails with: Error: Cannot find module 'import-local'

[Xavier]

Le 28/06/2020 à 09:32, Xavier a écrit :
> Control: severity -1 grave
> 
> Le 27/06/2020 à 23:31, Nilesh Patra a écrit :
>>
>>
>> On Sun, 28 Jun 2020, 02:45 Xavier, > > wrote:
>>
>> Control: severity -i grave
>>
>>
>> Thanks.
>>
>>
>> Le 24/06/2020 à 21:18, Nilesh Patra a écrit :
>> > Package: node-jest
>> > Severity: serious
>> >
>> > Dear Maintainer,
>> >
>> > Node-jest fails with the following on all the node-modules I've
>> tried yet.
>> > Sample examples on
>>
>> Work needed for node-jest:
>>  * add babel-plugin-istanbul; proposition: add it in node-babel7
>>
>>
>> It's good.
>> Would you mind discussing this bit on the list?
> 
> pkg-js list receives messages related to this bug
> 
>>  * update and fix node-jsdom
>>  * add missing components
>>
>>
>> Noted.
>>
>>
>> Here is the list of missing modules (mix of node-jest and node-jsdom):
> 
> jsdom:
>  * data-urls
>  * domexception
>  * html-encoding-sniffer
>  * w3c-hr-time
>  * whatwg-encoding
>  * whatwg-mimetype
>  * whatwg-url
>  * xml-name-validator

Hi all,

after fixing node-jsdom, these modules are required for jest:
 * astral-regex
 * babel-plugin-istanbul
 * babel-preset-current-node-syntax
 * fast-json-stable-stringify
 * is-generator-fn
 * makeerror
 * natural-compare
 * p-each-series
 * p-reduce
 * sane
 * string-length
 * supports-hyperlinks
 * terminal-link
 * throat
 * tmpl
 * walker

I suggests to embed babel* in node-babel7 and others in node-jest. What
are your advises ?

Bug#965026: grub-emu is unusable with orca nor BRLTTY

[Patrick ZAJDA]

Package: grub-emu
Version: 2.02+dfsg1-20
Severity: critical
Tags: a11y
Justification: breaks the whole system

Dear Maintainer,

I use Debian with Orca and BRLTTY and executed grub-emu.
When ran on mate-terminal, it shows an interface where BRLTTY displays "Screen 
not in text mode" and Orca doesn't speak at all.
The only solution to stop it is to killall -9 grub-emu from another terminal.

The most critical situation is when I run grub-emu from a TTY session. In this 
case, BRLTTY displays again "Screen not in text mode" and my system locked, I 
was not able to close grub-emu nor to use another TTY to kill it.
The only solution I found to reboot correctly was use SSH.

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/nvme0n1p3 / ext4 rw,noatime,nodiratime,errors=remount-ro 0 0
/dev/nvme0n1p2 /boot ext2 rw,noatime,nodiratime 0 0
/dev/sda4 /var/vm ext4 rw,noatime,nodiratime,quota,usrquota,grpquota 0 0
/dev/nvme0n1p1 /boot/efi vfat 
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
 0 0
/dev/sdb1 /home ext4 rw,relatime,quota,usrquota,grpquota 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="${saved_entry}"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  c520d8e3-9caa-45e3-9dc0-664205763df9
else
  search --no-floppy --fs-uuid --set=root c520d8e3-9caa-45e3-9dc0-664205763df9
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=fr_FR
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=1
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=1
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-c520d8e3-9caa-45e3-9dc0-664205763df9' {
savedefault
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  
1891f72e-62a2-4314-98c7-79626e392794
else
  search --no-floppy --fs-uuid --set=root 
1891f72e-62a2-4314-98c7-79626e392794
fi
echo'Chargement de Linux 5.6.0-0.bpo.2-amd64…'
linux   /vmlinuz-5.6.0-0.bpo.2-amd64 
root=UUID=c520d8e3-9caa-45e3-9dc0-664205763df9 ro  splash splash
echo'Chargement du disque mémoire initial…'
initrd  /initrd.img-5.6.0-0.bpo.2-amd64
}
submenu 'Options avancées pour Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-c520d8e3-9caa-45e3-9dc0-664205763df9' {
menuentry 'Debian GNU/Linux, avec Linux 5.6.0-0.bpo.2-amd64' --class 
debian --class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-5.6.0-0.bpo.2-amd64-advanced-c520d8e3-9caa-45e3-9dc0-664205763df9' {
savedefault
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; 
fi
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  
1891f72e-62a2-4314-98c7-79626e392794
else
  search --no-floppy --fs-uuid --set=root 

Bug#965040: singularity-container: CVE-2020-13845 CVE-2020-13846 CVE-2020-13847

[Salvatore Bonaccorso]

Source: singularity-container
Version: 3.5.2+ds1-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 

Hi,

The following vulnerabilities were published for singularity-container.

CVE-2020-13845[0]:
| Sylabs Singularity 3.0 through 3.5 has Improper Validation of an
| Integrity Check Value. Image integrity is not validated when an ECL
| policy is enforced. The fingerprint required by the ECL is compared
| against the signature object descriptor(s) in the SIF file, rather
| than to a cryptographically validated signature.


CVE-2020-13846[1]:
| Sylabs Singularity 3.5.0 through 3.5.3 fails to report an error in a
| Status Code.


CVE-2020-13847[2]:
| Sylabs Singularity 3.0 through 3.5 lacks support for an Integrity
| Check. Singularity's sign and verify commands do not sign metadata
| found in the global header or data object descriptors of a SIF file.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-13845
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13845
[1] https://security-tracker.debian.org/tracker/CVE-2020-13846
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13846
[2] https://security-tracker.debian.org/tracker/CVE-2020-13847
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13847

Regards,
Salvatore

Bug#963808: ruby-sanitize: CVE-2020-4054: HTML sanitization bypass in Sanitize

[Salvatore Bonaccorso]

Hi Antonio,

On Tue, Jul 14, 2020 at 09:41:21AM -0300, terce...@debian.org wrote:
> On Mon, Jul 13, 2020 at 10:04:10PM +0200, Salvatore Bonaccorso wrote:
> > Hi Antonio,
> > 
> > On Mon, Jul 13, 2020 at 11:19:38AM -0300, terce...@debian.org wrote:
> > > On Sun, Jul 12, 2020 at 03:11:30PM +0200, Salvatore Bonaccorso wrote:
> > > > On Sat, Jun 27, 2020 at 09:10:01PM +0200, Salvatore Bonaccorso wrote:
> > > > > Source: ruby-sanitize
> > > > > Version: 4.6.6-2
> > > > > Severity: grave
> > > > > Tags: security upstream
> > > > > Justification: user security hole
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > The following vulnerability was published for ruby-sanitize.
> > > > > 
> > > > > CVE-2020-4054[0]:
> > > > > | In Sanitize (RubyGem sanitize) greater than or equal to 3.0.0 and 
> > > > > less
> > > > > | than 5.2.1, there is a cross-site scripting vulnerability. When HTML
> > > > > | is sanitized using Sanitize's "relaxed" config, or a custom config
> > > > > | that allows certain elements, some content in a math or svg element
> > > > > | may not be sanitized correctly even if math and svg are not in the
> > > > > | allowlist. You are likely to be vulnerable to this issue if you use
> > > > > | Sanitize's relaxed config or a custom config that allows one or more
> > > > > | of the following HTML elements: iframe, math, noembed, noframes,
> > > > > | noscript, plaintext, script, style, svg, xmp. Using carefully 
> > > > > crafted
> > > > > | input, an attacker may be able to sneak arbitrary HTML through
> > > > > | Sanitize, potentially resulting in XSS (cross-site scripting) or 
> > > > > other
> > > > > | undesired behavior when that HTML is rendered in a browser. This has
> > > > > | been fixed in 5.2.1.o
> > > > 
> > > > Attached ist a preliminary debdiff with the fix, but two prerequisites
> > > > before "fix: Don't treat :remove_contents as `true` when it's an
> > > > Array" and "feat: Remove useless filtered element content by default".
> > > > 
> > > > Antonio, would it be possible to let it go trough your second pair of
> > > > eyes, with the pre-knolege that I'm not familiar with the package but
> > > > trying to address the CVE-2020-4054.
> > > > 
> > > > If those look correct, the plan would be to do 4.6.6-2.1~deb10u1 based
> > > > on that for buster-security.
> > > 
> > > Yes, those patches look OK.
> > > 
> > > Thanks for your work.
> > 
> > Thanks for your review! So propsing to upload the NMU first, and then
> > later handle the DSA for it based on that version if no negative
> > reports come in.
> 
> Sure, just do it.

NMU done (in delayed queue). Will try to have later an eye on the
reports but if you notice something odd just let me know.

Regards,
Salvatore

Bug#963292: marked as done (libdata-messagepack-perl: FTBFS: pack_template.h:897:65: error: unknown type name ‘msgpack_timestamp’)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 19:18:39 +
with message-id 
and subject line Bug#963292: fixed in libdata-messagepack-perl 1.00-3
has caused the Debian Bug report #963292,
regarding libdata-messagepack-perl: FTBFS: pack_template.h:897:65: error: 
unknown type name ‘msgpack_timestamp’
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.)


-- 
963292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdata-messagepack-perl
Version: 1.00-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -c  "-I." "-I." -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
> -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -Wall -W -Wno-comment -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
> -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT 
> -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe 
> -I/usr/local/include   -DVERSION=\"1.00\" -DXS_VERSION=\"1.00\" -o 
> xs-src/pack.o -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.30/CORE"  
> -DUSE_PPPORT xs-src/pack.c
> In file included from xs-src/pack.c:45:
> /usr/include/msgpack/pack_template.h:897:65: error: unknown type name 
> ‘msgpack_timestamp’
>   897 | msgpack_pack_inline_func(_timestamp)(msgpack_pack_user x, const 
> msgpack_timestamp* d)
>   | 
> ^
> /usr/include/msgpack/pack_template.h: In function ‘msgpack_pack_timestamp’:
> /usr/include/msgpack/pack_template.h:899:21: error: request for member 
> ‘tv_sec’ in something not a structure or union
>   899 | if int64_t)d->tv_sec) >> 34) == 0) {
>   | ^~
> /usr/include/msgpack/pack_template.h:900:40: error: request for member 
> ‘tv_nsec’ in something not a structure or union
>   900 | uint64_t data64 = ((uint64_t) d->tv_nsec << 34) | 
> (uint64_t)d->tv_sec;
>   |^~
> /usr/include/msgpack/pack_template.h:900:70: error: request for member 
> ‘tv_sec’ in something not a structure or union
>   900 | uint64_t data64 = ((uint64_t) d->tv_nsec << 34) | 
> (uint64_t)d->tv_sec;
>   |  
> ^~
> In file included from /usr/lib/x86_64-linux-gnu/perl/5.30/CORE/perl.h:1159,
>  from ./xshelper.h:36,
>  from xs-src/pack.c:5:
> /usr/include/msgpack/pack_template.h:918:9: error: request for member 
> ‘tv_nsec’ in something not a structure or union
>   918 | _msgpack_store32([0], d->tv_nsec);
>   | ^~~~
> In file included from /usr/include/msgpack/sysdep.h:91,
>  from /usr/include/msgpack/pack_define.h:13,
>  from xs-src/pack.c:7:
> /usr/include/msgpack/pack_template.h:919:9: error: request for member 
> ‘tv_sec’ in something not a structure or union
>   919 | _msgpack_store64([4], d->tv_sec);
>   | ^~~~
> make[1]: *** [Makefile:357: xs-src/pack.o] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/06/20/libdata-messagepack-perl_1.00-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libdata-messagepack-perl
Source-Version: 1.00-3
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 

Bug#950460: marked as done (libdata-messagepack-perl: FTBFS with msgpack-c/3.2.1-1)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 19:18:39 +
with message-id 
and subject line Bug#963292: fixed in libdata-messagepack-perl 1.00-3
has caused the Debian Bug report #963292,
regarding libdata-messagepack-perl: FTBFS with msgpack-c/3.2.1-1
to be marked as done.

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

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


-- 
963292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdata-messagepack-perl
Version: 1.00-2
Severity: important

While testing reverse build-deps of msgpack-c against the latest version
(currently in experimental), your package failed to build:


x86_64-linux-gnu-gcc -c  "-I." "-I." -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -Wall -W -Wno-comment -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT 
-D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include  
 -DVERSION=\"1.00\" -DXS_VERSION=\"1.00\" -o xs-src/MessagePack.o -fPIC 
"-I/usr/lib/x86_64-linux-gnu/perl/5.30/CORE"  -DUSE_PPPORT xs-src/MessagePack.c
x86_64-linux-gnu-gcc -c  "-I." "-I." -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -Wall -W -Wno-comment -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT 
-D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include  
 -DVERSION=\"1.00\" -DXS_VERSION=\"1.00\" -o xs-src/pack.o -fPIC 
"-I/usr/lib/x86_64-linux-gnu/perl/5.30/CORE"  -DUSE_PPPORT xs-src/pack.c
In file included from xs-src/pack.c:45:
/usr/include/msgpack/pack_template.h:897:65: error: unknown type name 
‘msgpack_timestamp’
  897 | msgpack_pack_inline_func(_timestamp)(msgpack_pack_user x, const 
msgpack_timestamp* d)
  | 
^
/usr/include/msgpack/pack_template.h: In function ‘msgpack_pack_timestamp’:
/usr/include/msgpack/pack_template.h:899:21: error: request for member ‘tv_sec’ 
in something not a structure or union
  899 | if int64_t)d->tv_sec) >> 34) == 0) {
  | ^~
/usr/include/msgpack/pack_template.h:900:40: error: request for member 
‘tv_nsec’ in something not a structure or union
  900 | uint64_t data64 = ((uint64_t) d->tv_nsec << 34) | 
(uint64_t)d->tv_sec;
  |^~
/usr/include/msgpack/pack_template.h:900:70: error: request for member ‘tv_sec’ 
in something not a structure or union
  900 | uint64_t data64 = ((uint64_t) d->tv_nsec << 34) | 
(uint64_t)d->tv_sec;
  |  ^~
In file included from /usr/lib/x86_64-linux-gnu/perl/5.30/CORE/perl.h:1159,
 from ./xshelper.h:36,
 from xs-src/pack.c:5:
/usr/include/msgpack/pack_template.h:918:9: error: request for member ‘tv_nsec’ 
in something not a structure or union
  918 | _msgpack_store32([0], d->tv_nsec);
  | ^~~~
In file included from /usr/include/msgpack/sysdep.h:91,
 from /usr/include/msgpack/pack_define.h:13,
 from xs-src/pack.c:7:
/usr/include/msgpack/pack_template.h:919:9: error: request for member ‘tv_sec’ 
in something not a structure or union
  919 | _msgpack_store64([4], d->tv_sec);
  | ^~~~
make[1]: *** [Makefile:357: xs-src/pack.o] Error 1
make[1]: Leaving directory '/<>'
make: *** [/usr/share/cdbs/1/class/makefile.mk:77: debian/stamp-makefile-build] 
Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


It appears to be mis-handling the new timestamp related types added in
msgpack-c 3.1.0.

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

Kernel: Linux 5.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 

Processed: Bug#963292 marked as pending in libdata-messagepack-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #963292 [src:libdata-messagepack-perl] libdata-messagepack-perl: FTBFS: 
pack_template.h:897:65: error: unknown type name ‘msgpack_timestamp’
Bug #950460 [src:libdata-messagepack-perl] libdata-messagepack-perl: FTBFS with 
msgpack-c/3.2.1-1
Added tag(s) pending.
Added tag(s) pending.

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

Bug#963292: marked as pending in libdata-messagepack-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #963292 in libdata-messagepack-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/libdata-messagepack-perl/-/commit/4b3dbafdd064dd2cd9b627fa3297155bd045a8e6


Fix build with msgpack-c 3.0.

Closes: #963292


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963292

Processed: Bug#962550 marked as pending in gclib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #962550 [libgclib1] libgclib1: ABI break without soname change
Added tag(s) pending.

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

Bug#964039: marked as done (vg: FTBFS on mips64el)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 18:49:30 +
with message-id 
and subject line Bug#964039: fixed in vg 1.25.0+ds-2
has caused the Debian Bug report #964039,
regarding vg: FTBFS on mips64el
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.)


-- 
964039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vg
Version: 1.25.0+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

vg failed to build on mips64el:
| Test Summary Report
| ---
| t/34_vg_pack.t  (Wstat: 0 Tests: 18 Failed: 2)
|   Failed tests:  16-17
| t/48_vg_convert.t   (Wstat: 0 Tests: 26 Failed: 2)
|   Failed tests:  15, 19
| Files=50, Tests=672, 2446 wallclock secs ( 3.33 usr  0.48 sys + 3450.18 cusr 
398.58 csys = 3852.57 CPU)
| Result: FAIL
| make[1]: *** [debian/rules:70: override_dh_auto_test-arch] Error 1

See 
https://buildd.debian.org/status/fetch.php?pkg=vg=mips64el=1.25.0%2Bds-1=1593113654=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: vg
Source-Version: 1.25.0+ds-2
Done: cru...@debian.org (Michael R. Crusoe)

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated vg 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, 14 Jul 2020 15:15:28 +0200
Source: vg
Architecture: source
Version: 1.25.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 964039
Changes:
 vg (1.25.0+ds-2) unstable; urgency=medium
 .
   * Restrict architectures to build for. Closes: #964039.
Checksums-Sha1:
 b5d4d3d92ad7cf74e8c1e4a9dd5a8fdfc1767040 2952 vg_1.25.0+ds-2.dsc
 e4f59be3da4d84efb3328c75ef6a53433938470a 41796 vg_1.25.0+ds-2.debian.tar.xz
 2daf68aa3ec1692855bc7cafbed6a1aba74f88a2 10800 vg_1.25.0+ds-2_source.buildinfo
Checksums-Sha256:
 0835f4fea884311f2b92a93fd080e32ac5ae885d464f18f77784cf2933c2aee6 2952 
vg_1.25.0+ds-2.dsc
 ab76430c4089a5a9de32b6088f9794b0d09420b83561c7635b31f17a0fd9cc8a 41796 
vg_1.25.0+ds-2.debian.tar.xz
 3a6dedea88c0d32e7c2a02c3901d6861425ecfbe0c9a9bbfdc96f605cbe69583 10800 
vg_1.25.0+ds-2_source.buildinfo
Files:
 da3288ecae076d61ba65b4442a1e6d49 2952 science optional vg_1.25.0+ds-2.dsc
 b05091eab16696d0f19bd4d329a04414 41796 science optional 
vg_1.25.0+ds-2.debian.tar.xz
 3f5396a3d57e0bf1ad5713a5b12c6508 10800 science optional 
vg_1.25.0+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl8N+nwACgkQPCZ2P2xn
5uJLPA/9Hyl3N33sEMoFZFsKtHr03etPQIIqJCMzI5dPMuShKgY00NvAM4KkMQrp
baWG5AmayGGNvtXDxjGxJ2NCzDh+MwnVCJMRyCBw6SEMv2YE5kVjyzjfYmq63NdX
myfiAKW9J3sDcRI5Dj5fQFqjvCpZCHgwhlsI/LWuY7WDcoIPFfoQ5nzkA/H61kcW
Fblkqw9hI3VLk2NDTfwef7BnmuNQjezhexYJbF9Y+cNHO/ItVbc0oXX0GuVaZJjn
WewhR4a11mIazu8rAe+pj71tFk1O1imbUBtx6fP6CiZHe6nVcfenKD4ZW40jLoZL
iPgy2L0/jxVvWQBYyR1/IBRIu3UAQ2/AdpiGpwc+f8733gKBipyV4asVRk6rMwLS
cqRXlK87wHcs+Z154JG9TVbNKohuaahfAJQXfm4hY6AoemQSgBilOYUKsZREbvdv
jnI4fDWV8f986bGW2FY9gfwy4hTqyzLE4JJkYgKqPHKO1LkZslvAwwm9qGpS9aX0
8K4BjFegQz+0ozol1lSllGFfe0/dA/CfazCo/gDiI5E521WBoCMKGW+5GWSOlYlg
2k+rj4pHPopxn/E4CajoSzl1QR76ixPL7sODnua81lUNN+X1UhqZ1bIeEmiP80rn
DqcWwXcbey8ilc2y4VSiKwsG5P2x1DGhLPkqwpHK4Z4+DddxBN4=
=4pvz
-END PGP SIGNATURE End Message ---

Bug#962550: marked as pending in gclib

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #962550 in gclib 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/med-team/libgclib/-/commit/911e9f4f5bb73a328fade24e13894ef5083be686


Bump soname. Closes: #962550


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/962550

Processed: Bug#964039 marked as pending in vg

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964039 [src:vg] vg: FTBFS on mips64el
Added tag(s) pending.

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

Bug#954699: marked as done (cider: FTBFS: Spies can only be created in ‘before-each’)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 18:34:04 +
with message-id 
and subject line Bug#954699: fixed in cider 0.19.0+dfsg-2.1
has caused the Debian Bug report #954699,
regarding cider: FTBFS: Spies can only be created in ‘before-each’
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.)


-- 
954699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cider
Version: 0.19.0+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> LANG=C.UTF-8 LC_ALL=C.UTF-8 mkdocs build --clean
> WARNING -  Config value: 'site_favicon'. Warning: Unrecognised configuration 
> name: site_favicon 
> WARNING -  Config value: 'pages'. Warning: The 'pages' configuration option 
> has been deprecated and will be removed in a future release of MkDocs. Use 
> 'nav' instead. 
> INFO-  Cleaning site directory 
> INFO-  Building documentation to directory: /<>/html 
> WARNING -  Documentation file 'about/contributing.md' contains a link to 
> 'about/readthedocs.org' which is not found in the documentation files. 
> make[1]: Leaving directory '/<>'
>dh_elpa_test
>   buttercup -L . -L test/utils
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Spies can only be created in ‘before-each’
> dh_elpa_test: error: buttercup -L . -L test/utils returned exit code 255
> make: *** [debian/rules:4: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/03/22/cider_0.19.0+dfsg-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: cider
Source-Version: 0.19.0+dfsg-2.1
Done: =?utf-8?q?Lukas_M=C3=A4rdian?= 

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

Debian distribution maintenance software
pp.
Lukas Märdian  (supplier of updated cider package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Jul 2020 12:30:35 +0200
Source: cider
Architecture: source
Version: 0.19.0+dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacs addons team 

Changed-By: Lukas Märdian 
Closes: 954699
Changes:
 cider (0.19.0+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Lukas Märdian ]
   * Cherry pick upstream commit 50228d441efee8b5de92a0f34039ea6380352d92
 to fix "Spies can only be created in ‘before-each’" (Closes: #954699)
 .
   * Cherry pick upstream commit adeede55ebc8db26131a9f04bf596621574d742c
 - refreshed for current version
 - via upstream PR#2804 (together with commit 50228d)
 - https://github.com/clojure-emacs/cider/pull/2804
 .
   * Cherry pick one hunk of 92d2c3ed0416d8010bb74252b535fff80bbcbfd5
 - only before-all > before-each is needed to fix the tests
 .
   [ Dimitri John Ledkov ]
   * Drop debian/source/options, does not allow individual patches.
Checksums-Sha1:
 e378fdfd76b756f90a405a7a336cc3afcbc86d74 2161 cider_0.19.0+dfsg-2.1.dsc
 a62a30628ac918efb18b45c95536366bde9c030c 10052 
cider_0.19.0+dfsg-2.1.debian.tar.xz
 a635b3a8ae2f313c17be0af1e7476ca7c6a2a286 14741 
cider_0.19.0+dfsg-2.1_source.buildinfo
Checksums-Sha256:
 d89e51a7ef1ec0bccdc15409248fd85bace1c4fe31f1eb5c10b711e65fffb6b0 2161 
cider_0.19.0+dfsg-2.1.dsc
 380591ce32fa2fe92a47730c8fffbeb1b49e26ba08f19a457f92569ae1817718 10052 
cider_0.19.0+dfsg-2.1.debian.tar.xz
 2188dacfd39e6f2f6ac468e3551e76c624b6384828a286b528d1ab0303ee02a4 14741 
cider_0.19.0+dfsg-2.1_source.buildinfo
Files:
 

Bug#964039: marked as pending in vg

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #964039 in vg 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/med-team/vg/-/commit/c4d49face2fd06279f433a234ec0535377a4e5ad


Restrict architectures to build for. Closes: #964039.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964039

Bug#907496: marked as done (libcurlpp0: Always fails with "No URL set!")

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 17:45:45 +
with message-id <3bb87ad562184e0b896dfe4a44a4e...@micard.lu>
and subject line 
has caused the Debian Bug report #907496,
regarding libcurlpp0: Always fails with "No URL set!"
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.)


-- 
907496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcurlpp0
Version: 0.8.1-2+b1
Severity: grave
Justification: renders package unusable

libcurlpp0 appears to always fail with a "No URL set!" error message.
I only tested the "Easy" API.

For example even the first example in its repo

doesn't work:

$ g++ -Wall example00.cpp `curlpp-config --cflags --libs` `curl-config --cflags 
--libs`
$ ./a.out 
No URL set!

I recompiled libcurlpp using both 7 & 8[1] and when linking the example program 
to
the new build it works fine (both static & dynamic libs). So I'm not sure where
the problem lies but even after reinstalling the Debian package I could only get
it to work with my local libcurlpp.

[1] GCC package versions:
g++-7: 7.3.0-28
g++-8: 4:8.2.0-1

-- System Information:
Debian Release: 9.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libcurlpp0 depends on:
ii  libc6   2.27-5
ii  libcurl47.61.0-1
ii  libgcc1 1:8.2.0-4
ii  libstdc++6  8.2.0-4

libcurlpp0 recommends no packages.

libcurlpp0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hello everyone!

Since we were unable to reproduce this bug I'm tagging it unreproducible and 
closing it.
In the meantime if anyone have more intel feel free to re-open this bug with 
more details.

--
Aloïs Micard 

GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2--- End Message ---

Bug#965033: meson: Missing dependency on python3-pkg-resources

[Adrian Bunk]

Package: meson
Version: 0.55.0-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:systemd

$ meson
Traceback (most recent call last):
  File "/usr/bin/meson", line 17, in 
from mesonbuild import mesonmain
  File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line 25, in 

from . import mconf, mdist, minit, minstall, mintro, msetup, mtest, 
rewriter, msubprojects, munstable_coredata, mcompile
  File "/usr/lib/python3/dist-packages/mesonbuild/mconf.py", line 16, in 

from . import coredata, environment, mesonlib, build, mintro, mlog
  File "/usr/lib/python3/dist-packages/mesonbuild/build.py", line 26, in 

from . import dependencies
  File "/usr/lib/python3/dist-packages/mesonbuild/dependencies/__init__.py", 
line 15, in 
from .boost import BoostDependency
  File "/usr/lib/python3/dist-packages/mesonbuild/dependencies/boost.py", line 
25, in 
from .base import DependencyException, ExternalDependency, 
PkgConfigDependency
  File "/usr/lib/python3/dist-packages/mesonbuild/dependencies/base.py", line 
32, in 
import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'
$

Processed: meson: Missing dependency on python3-pkg-resources

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:systemd
Bug #965033 [meson] meson: Missing dependency on python3-pkg-resources
Added indication that 965033 affects src:systemd

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

Bug#961851: marked as done (make-dfsg breaks cross-toolchain-base autopkgtest: debian/kernelarch.make:5: *** empty variable name)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 17:48:47 +
with message-id 
and subject line Bug#961851: fixed in cross-toolchain-base 46
has caused the Debian Bug report #961851,
regarding make-dfsg breaks cross-toolchain-base autopkgtest: 
debian/kernelarch.make:5: *** empty variable name
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.)


-- 
961851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: make-dfsg, cross-toolchain-base
Control: found -1 make-dfsg/4.3-1
Control: found -1 cross-toolchain-base/45
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of make-dfsg the autopkgtest of
cross-toolchain-base fails in testing when that autopkgtest is run with
the binary packages of make-dfsg from unstable. It passes when run with
only packages from testing. In tabular form:

   passfail
make-dfsg  from testing4.3-1
cross-toolchain-base   from testing45
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of make-dfsg to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=make-dfsg

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cross-toolchain-base/5687474/log.gz

autopkgtest [18:08:29]: test build: [---
Testing cross builds on amd64 ...
+ CROSS_ARCHS=ppc64el DEB_BUILD_OPTIONS=parallel=2 nopgo nolto
dpkg-buildpackage -d -b --no-sign
dpkg-buildpackage: info: source package cross-toolchain-base
dpkg-buildpackage: info: source version 45
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Matthias Klose 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
debian/kernelarch.make:5: *** empty variable name.  Stop.
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess
returned exit status 2
autopkgtest [18:08:29]: test build: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cross-toolchain-base
Source-Version: 46
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated cross-toolchain-base 
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, 14 Jul 2020 19:33:22 +0200
Source: cross-toolchain-base
Architecture: source
Version: 46
Distribution: unstable
Urgency: medium
Maintainer: Cross Toolchain Base Team 

Changed-By: Matthias Klose 
Closes: 954663 961851
Changes:
 cross-toolchain-base (46) unstable; urgency=medium
 .
   * Build using glibc 2.31-1.
   * Build using gcc 10.1.0-5.
   * Build using linux 5.7.
   * Use the linux source version for the Built-Using info. Closes: #954663.
   * Fix build with make 4.3. Closes: #961851.
   * Bump standards version.
Checksums-Sha1:
 dad300ba09260b2c2bb754f74393a11ee3a54956 6144 cross-toolchain-base_46.dsc
 6e6d0f7cd42775dc534a39a36601c07867cd6b69 42720 cross-toolchain-base_46.tar.xz
 d0d408f8523a466c64ca7efc4b4b219b58cfe367 8187 
cross-toolchain-base_46_source.buildinfo
Checksums-Sha256:
 ef9cce4a1b232bf475305463f9ebc4925462fa4087f20102364dfe80400a63fe 6144 
cross-toolchain-base_46.dsc
 255d1bd9cd2ec37da5309a2f7e7cf13454d9005349c1d5a3b5a54a6c99b841b3 42720 
cross-toolchain-base_46.tar.xz
 455f343e039074011136c71659bb7a4f1c220a39cd7333e4d6b8bef9f5dfb7af 8187 

Bug#965005: marked as done (libdolfin-dev-common: missing Breaks+Replaces: libdolfin-dev (<< 2019.2.0~git20200218.027d9cc-7))

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 17:18:27 +
with message-id 
and subject line Bug#965005: fixed in dolfin 2019.2.0~git20200218.027d9cc-9
has caused the Debian Bug report #965005,
regarding libdolfin-dev-common: missing Breaks+Replaces: libdolfin-dev (<< 
2019.2.0~git20200218.027d9cc-7)
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.)


-- 
965005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdolfin-dev-common
Version: 2019.2.0~git20200218.027d9cc-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack 
.../libdolfin-dev-common_2019.2.0~git20200218.027d9cc-8_amd64.deb ...
  Unpacking libdolfin-dev-common (2019.2.0~git20200218.027d9cc-8) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libdolfin-dev-common_2019.2.0~git20200218.027d9cc-8_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/include/dolfin/adaptivity/AdaptiveLinearVariationalSolver.h', which is 
also in package libdolfin-dev 2019.2.0~git20200218.027d9cc-6+b2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/var/cache/apt/archives/libdolfin-dev-common_2019.2.0~git20200218.027d9cc-8_amd64.deb


cheers,

Andreas


libdolfin-dev=2019.2.0~git20200218.027d9cc-6+b2_libdolfin-dev-common=2019.2.0~git20200218.027d9cc-8.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dolfin
Source-Version: 2019.2.0~git20200218.027d9cc-9
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated dolfin 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, 14 Jul 2020 23:34:19 +0800
Source: dolfin
Architecture: source
Version: 2019.2.0~git20200218.027d9cc-9
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Drew Parsons 
Closes: 965005
Changes:
 dolfin (2019.2.0~git20200218.027d9cc-9) experimental; urgency=medium
 .
   * append 64-bit tests to skip on 32-bit arches, append to
 ARCH_SPECIFIC_SKIP_SERIAL_TEST_64
   * libdolfin-dev-common Replaces and Breaks:
 libdolfin-dev (<< 2019.2.0~git20200218.027d9cc-7)
 Add corresponding versioned depends for libdolfin-dev on
 libdolfin-dev-common (>= 2019.2.0~git20200218.027d9cc-7)
 Closes: #965005.
Checksums-Sha1:
 ed7ee92cdfbecedd9af643d3e5507a1d9583bf29 3718 
dolfin_2019.2.0~git20200218.027d9cc-9.dsc
 bdb13b4da81496a16c6ecf193d027f993240c7a1 2508104 
dolfin_2019.2.0~git20200218.027d9cc-9.debian.tar.xz
Checksums-Sha256:
 b3b50f4267c39074a847871080357dd41f2d8f99587ab983a4b770427f1c5158 3718 
dolfin_2019.2.0~git20200218.027d9cc-9.dsc
 7a2812e872037e1b53278fae9e12cc0a19acf0dcb0898dc1a71bb15f8fc70516 2508104 
dolfin_2019.2.0~git20200218.027d9cc-9.debian.tar.xz
Files:
 65580b06e7a7a8ed8fa214751c8cbffd 3718 math optional 
dolfin_2019.2.0~git20200218.027d9cc-9.dsc
 020ff92e819d6f1e5e09e4074d6a2e55 2508104 math optional 
dolfin_2019.2.0~git20200218.027d9cc-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl8N5AIACgkQVz7x5L1a
AfrvwQ/+PcLgnLAt7JQpJspm5TMGSni7MbC4y97qPMlmnHcDKvbzFTO5bAuA02v2
W9VeyAuhX7AtQPqXLwuAqUSU45cgHRg4xqmwMlMyqSEbp2Uom4tNh7bMEHntW3Cl
7x/PWMKtzhT+hd0Yrlro9+KxuATHkkBSPmGJOUJZTvFwKaacaRreWXECNeN4He52
eQ4N77XI/pGQWMZXup/L5eiV2Wna78x2uN+0OPddVI1bBaxm6bNZcmyDdq4x53aw
WgkoA62kGeMov80PhaMyLmcrtOblPJPGHAH9i3IA576GOdd/vjmecDyiyW00k8rq

Processed: Fixing found/fixed metadata of #955107 - try 2

[Debian Bug Tracking System]

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

> # I should have used source package name, not binary
> notfound 955107 python3-sphinxcontrib.spelling/4.2.0-2
Bug #955107 [python3-sphinxcontrib.spelling] python3-sphinxcontrib.spelling: 
Uses obsolete API ‘Sphinx.info’
The source python3-sphinxcontrib.spelling and version 4.2.0-2 do not appear to 
match any binary packages
No longer marked as found in versions python3-sphinxcontrib.spelling/4.2.0-2.
> found 955107 sphinxcontrib-spelling/4.2.0-2
Bug #955107 [python3-sphinxcontrib.spelling] python3-sphinxcontrib.spelling: 
Uses obsolete API ‘Sphinx.info’
Marked as found in versions sphinxcontrib-spelling/4.2.0-2.
> notfixed 955107 python3-sphinxcontrib.spelling/4.3.0-1
Bug #955107 [python3-sphinxcontrib.spelling] python3-sphinxcontrib.spelling: 
Uses obsolete API ‘Sphinx.info’
The source python3-sphinxcontrib.spelling and version 4.3.0-1 do not appear to 
match any binary packages
No longer marked as fixed in versions python3-sphinxcontrib.spelling/4.3.0-1.
> fixed 955107 sphinxcontrib-spelling/4.3.0-1
Bug #955107 [python3-sphinxcontrib.spelling] python3-sphinxcontrib.spelling: 
Uses obsolete API ‘Sphinx.info’
Marked as fixed in versions sphinxcontrib-spelling/4.3.0-1.
> thanks
Stopping processing here.

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

Processed: Fixing found/fixed metadata of #955107

[Debian Bug Tracking System]

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

> # the package name was wrong (control → contrib)
> notfound 955107 python3-sphinxcontrol.spelling/4.2.0-2
Bug #955107 [python3-sphinxcontrib.spelling] python3-sphinxcontrib.spelling: 
Uses obsolete API ‘Sphinx.info’
The source python3-sphinxcontrol.spelling and version 4.2.0-2 do not appear to 
match any binary packages
No longer marked as found in versions python3-sphinxcontrol.spelling/4.2.0-2.
> found 955107 python3-sphinxcontrib.spelling/4.2.0-2
Bug #955107 [python3-sphinxcontrib.spelling] python3-sphinxcontrib.spelling: 
Uses obsolete API ‘Sphinx.info’
The source python3-sphinxcontrib.spelling and version 4.2.0-2 do not appear to 
match any binary packages
Marked as found in versions python3-sphinxcontrib.spelling/4.2.0-2.
> notfixed 955107 python3-sphinxcontrol.spelling/4.3.0-1
Bug #955107 [python3-sphinxcontrib.spelling] python3-sphinxcontrib.spelling: 
Uses obsolete API ‘Sphinx.info’
The source python3-sphinxcontrol.spelling and version 4.3.0-1 do not appear to 
match any binary packages
No longer marked as fixed in versions python3-sphinxcontrol.spelling/4.3.0-1.
> fixed 955107 python3-sphinxcontrib.spelling/4.3.0-1
Bug #955107 [python3-sphinxcontrib.spelling] python3-sphinxcontrib.spelling: 
Uses obsolete API ‘Sphinx.info’
The source python3-sphinxcontrib.spelling and version 4.3.0-1 do not appear to 
match any binary packages
Marked as fixed in versions python3-sphinxcontrib.spelling/4.3.0-1.
> thanks
Stopping processing here.

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

Bug#963061: marked as done (nodejs breaks node-grunt-contrib-nodeunit autopkgtest: 1/24 assertions failed)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 16:34:38 +
with message-id 
and subject line Bug#963061: fixed in node-grunt-contrib-nodeunit 2.0.0-3
has caused the Debian Bug report #963061,
regarding nodejs breaks node-grunt-contrib-nodeunit autopkgtest: 1/24 
assertions failed
to be marked as done.

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

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


-- 
963061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs, node-grunt-contrib-nodeunit
Control: found -1 nodejs/12.18.0~dfsg-3
Control: found -1 node-grunt-contrib-nodeunit/2.0.0-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of nodejs the autopkgtest of
node-grunt-contrib-nodeunit fails in testing when that autopkgtest is
run with the binary packages of nodejs from unstable. It passes when run
with only packages from testing. In tabular form:

 passfail
nodejs   from testing12.18.0~dfsg-3
node-grunt-contrib-nodeunit  from testing2.0.0-2
all others   from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of nodejs to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=nodejs

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-grunt-contrib-nodeunit/5930269/log.gz

autopkgtest [00:27:30]: test pkg-js-autopkgtest: [---
Using package.json
Node module name is grunt-contrib-nodeunit
# Copy test files
Looking at /usr/lib/nodejs/grunt-contrib-nodeunit
Looking at /usr/lib/*/nodejs/grunt-contrib-nodeunit
Looking at /usr/share/nodejs/grunt-contrib-nodeunit
Found /usr/share/nodejs/grunt-contrib-nodeunit
Linking /usr/share/nodejs/grunt-contrib-nodeunit/package.json
Linking /usr/share/nodejs/grunt-contrib-nodeunit/tasks
Launch debian/tests/pkg-js/test with sh -ex
+ grunt nodeunit:tests
Running "nodeunit:tests" (nodeunit) task
Testing nodeunit_test.js.F
>> nodeunit - fail
>> Message: Operator should display for multiline.
>> Error: false == true
>> at Object.ok (/usr/lib/nodejs/nodeunit/lib/types.js:83:39)
>> at
/tmp/autopkgtest-lxc._0bjsk9r/downtmp/autopkgtest_tmp/smokek9UbcK/test/nodeunit_test.js:18:12
>> at callDone (/usr/share/nodejs/grunt-legacy-util/index.js:160:5)
>> at ChildProcess.
(/usr/share/nodejs/grunt-legacy-util/index.js:199:5)
>> at ChildProcess.emit (events.js:315:20)
>> at ChildProcess.EventEmitter.emit (domain.js:482:12)
>> at maybeClose (internal/child_process.js:1021:16)
>> at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)

Warning: 1/24 assertions failed (2605ms) Use --force to continue.

Aborted due to warnings.
autopkgtest [00:27:33]: test pkg-js-autopkgtest: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-grunt-contrib-nodeunit
Source-Version: 2.0.0-3
Done: Olivier Tilloy 

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

Debian distribution maintenance software
pp.
Olivier Tilloy  (supplier of updated 
node-grunt-contrib-nodeunit 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, 14 Jul 2020 17:21:50 +0200
Source: node-grunt-contrib-nodeunit
Binary: node-grunt-contrib-nodeunit
Architecture: source
Version: 2.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Olivier Tilloy 
Description:
 node-grunt-contrib-nodeunit - Grunt plugin to run Nodeunit unit 

Bug#963771: marked as done (nodejs breaks node-immutable-tuple autopkgtest: can handle a lot of strings: AssertionError)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 16:34:44 +
with message-id 
and subject line Bug#963771: fixed in node-immutable-tuple 0.4.10-8
has caused the Debian Bug report #963771,
regarding nodejs breaks node-immutable-tuple autopkgtest: can handle a lot of 
strings: AssertionError
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.)


-- 
963771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs, node-immutable-tuple
Control: found -1 nodejs/12.18.0~dfsg-3
Control: found -1 node-immutable-tuple/0.4.10-7
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of nodejs the autopkgtest of node-immutable-tuple
fails in testing when that autopkgtest is run with the binary packages
of nodejs from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
nodejs from testing12.18.0~dfsg-3
node-immutable-tuple   from testing0.4.10-7
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of nodejs to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=nodejs

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-immutable-tuple/6049318/log.gz

  1) performance
   can handle a lot of strings:
 AssertionError [ERR_ASSERTION]: Expected values to be loosely
deep-equal:

tuple {
  '0': 'ftchujom2yv',
  '1': 'vfs12z46td',
  '2': 'vnjsdgd5oie',
  '3': 'p975if8h16t',
  '4': 'us43v9frwga',
  '5': '4u158uqgnu3',
  '6': 'uxs8h8druu',
  '7': '0d6egk7shh76',
  '8': '8sbvrilamav',
  '9': 'db4jmngu56t'
}

should loosely deep-equal

[
  'ftchujom2yv',
  'vfs12z46td',
  'vnjsdgd5oie',
  'p975if8h16t',
  'us43v9frwga',
  '4u158uqgnu3',
  'uxs8h8druu',
  '0d6egk7shh76',
  '8sbvrilamav',
  'db4jmngu56t'
]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-immutable-tuple
Source-Version: 0.4.10-8
Done: Olivier Tilloy 

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

Debian distribution maintenance software
pp.
Olivier Tilloy  (supplier of updated 
node-immutable-tuple 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, 14 Jul 2020 18:09:02 +0200
Source: node-immutable-tuple
Binary: node-immutable-tuple
Architecture: source
Version: 0.4.10-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Olivier Tilloy 
Description:
 node-immutable-tuple - Immutable finite list objects
Closes: 963771
Changes:
 node-immutable-tuple (0.4.10-8) unstable; urgency=medium
 .
   [ Gianfranco Costamagna ]
   * Team upload.
 .
   [ Olivier Tilloy ]
   * Remove an obsolete test that fails with recent versions of Node.js
 (Closes: #963771)
Checksums-Sha1:
 812f83f61a8c31f9393ca9a89f22b80f8434d5a3 2327 node-immutable-tuple_0.4.10-8.dsc
 82dafc0061b74f3cd0bb6ef28cc52e6d52ed9823 41656 
node-immutable-tuple_0.4.10-8.debian.tar.xz
 7cd62ab9e0f128aba34470a9727fbe4130ad0ae8 10337 
node-immutable-tuple_0.4.10-8_source.buildinfo
Checksums-Sha256:
 9f3a214111ace7b0c1efb416a6e7f20c3eee279d2b369b3bbfda0138f5eff22c 2327 
node-immutable-tuple_0.4.10-8.dsc
 9028ea683e4d7cd4a86f348a76e62f43b8c78add564b608b56a31730e04f6e0c 41656 
node-immutable-tuple_0.4.10-8.debian.tar.xz
 50a19ba6b3c5bb385c4c28ba114a8fbbc02e87700aede00de3848d29c66886cc 10337 
node-immutable-tuple_0.4.10-8_source.buildinfo
Files:
 30674bb1fa3aa95841212e7ba456a50a 2327 

Bug#963771: nodejs breaks node-immutable-tuple autopkgtest: can handle a lot of strings: AssertionError

[Olivier Tilloy]

An upstream change in Node.js is causing this test failure:
https://github.com/nodejs/node/commit/a0f338ecc1

The solution is to remove the offending test:
https://salsa.debian.org/js-team/node-immutable-tuple/-/merge_requests/1

Bug#964837: marked as done (pandoc-citeproc-preamble: FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 16:04:07 +
with message-id 
and subject line Bug#964837: fixed in pandoc-citeproc-preamble 1.4-1
has caused the Debian Bug report #964837,
regarding pandoc-citeproc-preamble: FTBFS
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.)


-- 
964837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pandoc-citeproc-preamble
Version: 1.2.4-2
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: 

The package currently fails to build:
| src/pandoc-citeproc-preamble.hs:73:25: error:
| • Couldn't match type ‘text-1.2.4.0:Data.Text.Internal.Text’
|  with ‘[Char]’
|   Expected type: Maybe String
| Actual type: Maybe text-1.2.4.0:Data.Text.Internal.Text
| • In the expression: Just s
|   In an equation for ‘toPath’: toPath (MetaString s) = Just s
||
| 73 | toPath (MetaString s) = Just s
|| ^


See
https://buildd.debian.org/status/fetch.php?pkg=pandoc-citeproc-preamble=amd64=1.2.4-2%2Bb2=1592220029=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pandoc-citeproc-preamble
Source-Version: 1.4-1
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated 
pandoc-citeproc-preamble 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, 14 Jul 2020 08:49:58 -0700
Source: pandoc-citeproc-preamble
Architecture: source
Version: 1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Sean Whitton 
Changed-By: Sean Whitton 
Closes: 964837
Changes:
 pandoc-citeproc-preamble (1.4-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #964837).
 .
 pandoc-citeproc-preamble (1.4) unstable; urgency=medium
 .
   * Update copyright years in various places.
   * Add CONTRIBUTING.rst & DEVELOPER-CERTIFICATE.
   * Tweak GitHub pull request template.
   * Add debian/tests/control.
   * Add override_dh_auto_test to run the integration test.
 - Add  build-deps on pandoc & pandoc-citeproc.
   * Declare compliance with Debian Policy 4.4.1.
 - Use 'https' in the Format: field in d/copyright.
   * README.md: add apt-get installation instructions.
 .
 pandoc-citeproc-preamble (1.3) unstable; urgency=medium
 .
   * Select pandoc-citeproc's refs Div by its 'refs' identifier, rather
 than by its 'references' class (see definition of Attr type in
 Text.Pandoc.Definition).
 This fixes pandoc-citeproc-preamble with pandoc-citeproc >=0.16.3.
 From 0.16.3 onwards, pandoc-citeproc can add a 'hanging-indent' class
 to the refs Div, which broke pandoc-citeproc-preamble's old method of
 selecting the refs Div.
   * Update for pandoc-types >=1.20.
 - Add dependency on text-conversions library.
 .
   * Add a simple integration test.
   * README.md: Don't specify a --resolver argument in the sample `stack
 install` command.
 Users probably want to use the latest LTS, so that
 pandoc-citeproc-preamble will work with recent pandoc.
Checksums-Sha1:
 e5157994bc6f1fc3c9df764d6a47e5230aad71df 2362 
pandoc-citeproc-preamble_1.4-1.dsc
 6c1502167b95d760c97aa4cad5afd3a74efb490f 3248 
pandoc-citeproc-preamble_1.4-1.debian.tar.xz
 e6637403bf8c8c797eb9d512d7a5f440be049350 18656 
pandoc-citeproc-preamble_1.4.orig.tar.xz
Checksums-Sha256:
 3d652b2fc973438b104fbcc206e78ee6b30c9dcbe79321a1599c980b6be70c6e 2362 
pandoc-citeproc-preamble_1.4-1.dsc
 29c51289d7bc9f874f80b848856d1753882d0460a21683b170fdd06b3e36ee30 3248 
pandoc-citeproc-preamble_1.4-1.debian.tar.xz
 e1a7a43eb137c7cbbccb9ca1e93d992c3567450b64541c7e74c7d75f69c7e61f 18656 
pandoc-citeproc-preamble_1.4.orig.tar.xz
Files:
 81b2871a4c89a2f96226ffd86496fdd5 2362 haskell optional 
pandoc-citeproc-preamble_1.4-1.dsc
 

Bug#965025: gpsshogi-data: data does not seem to be provided in the preferred format for modification

[Yann Dirson]

Package: gpsshogi
Version: 0.7.0-2
Severity: serious

The .bin and .dat files in gpsshogi-data come as-is in SVN, with
no information as to what they are generated from.  This does not
look DFSG-compliant.

As to the impact on my work on resurrecting the package (#964730),
if this issue is not solve it looks to me like at the minimum the data
would have to be split into non-free, and gpsshogi itself move
to contrib.


-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (990, 'stable'), (900, 'testing'), (500, 'stable-debug'), (500, 
'unstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages gpsshogi depends on:
ii  gpsshogi-data   0.7.0-2
ii  libboost-date-time1.67.01.67.0-13+deb10u1
ii  libboost-filesystem1.67.0   1.67.0-13+deb10u1
ii  libboost-iostreams1.67.01.67.0-13+deb10u1
ii  libboost-program-options1.67.0  1.67.0-13+deb10u1
ii  libboost-serialization1.67.01.67.0-13+deb10u1
ii  libboost-system1.67.0   1.67.0-13+deb10u1
ii  libboost-thread1.67.0   1.67.0-13+deb10u1
ii  libc6   2.28-10
ii  libgcc1 1:8.3.0-6
ii  libgl1  1.1.0-1
ii  libgsl232.5+dfsg-6
ii  libosl1v5   0.8.0-2~deb10u0
ii  libpocofoundation60 1.9.0-5+b1
ii  libpoconet601.9.0-5+b1
ii  libqt5core5a5.11.3+dfsg1-1+deb10u3
ii  libqt5gui5  5.11.3+dfsg1-1+deb10u3
ii  libqt5network5  5.11.3+dfsg1-1+deb10u3
ii  libqt5widgets5  5.11.3+dfsg1-1+deb10u3
ii  libqt5xml5  5.11.3+dfsg1-1+deb10u3
ii  libreadline77.0-5
ii  libstdc++6  8.3.0-6
ii  libtcmalloc-minimal42.7-1

gpsshogi recommends no packages.

gpsshogi suggests no packages.

-- no debconf information

Bug#963061: nodejs breaks node-grunt-contrib-nodeunit autopkgtest: 1/24 assertions failed

[Olivier Tilloy]

This failure is caused by an unidentified change in upstream Node.js which
results in a test's output not being wrapped as expected. Simply modifying
that test to add some more data so that its output is wrapped does the
trick:

https://salsa.debian.org/js-team/node-grunt-contrib-nodeunit/-/merge_requests/1

Bug#965021: conntrackd: segfaults when not disabling internal cache

[Thomas Schneider]

Package: conntrackd
Version: 1:1.4.5-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I’m experiencing a problem with conntrackd.

* What led up to the situation?

I installed and configured conntrackd and simply started it.

* What exactly did you do (or not do) that was effective (or ineffective)?

I investigated the problem using gdb and valgrind.  As the segfault
happens in cache_ct_cmp(), by being passed a NULL pointer that it tries
to dereference, I tried to disable the caches.

Setting `DisableExternalCache on` led to the same behaviour.  Setting
`DisableInternalCache on` apparently fixed it, however this option is
only available in NOTRACK mode (and I want to use FTFW mode).

Since some hash related functions appear in the backtrace, I tried to
change the value of HashSize and HashLimit.  Based on more or less
similar reports I found online, I tried disabling TCPWindowTracking and
ExpectationSync.  Neither one fixed the problem.

* What was the outcome of this action?

It segfaulted right after starting.  Only with `DisableExternalCache
on`, it produced any output (see below), without that, no output was
produced.

* What outcome did you expect instead?

I expected it to work, or at least provide a sensible error message.


*** /tmp/gdb.log
# gdb -q --args conntrackd
Reading symbols from conntrackd...Reading symbols from 
/usr/lib/debug/.build-id/ce/01eee7370eaa2a78b30857a5478c1b7f600bfe.debug...done.
done.
(gdb) r
Starting program: /usr/sbin/conntrackd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Tue Jul 14 16:48:55 2020] (pid=13845) [notice] disabling external cache

Program received signal SIGSEGV, Segmentation fault.
0x55564ba1 in cache_ct_cmp (data1=0x0, data2=0x555afd60) at 
cache-ct.c:104
104 cache-ct.c: No such file or directory.
(gdb) bt
#0  0x55564ba1 in cache_ct_cmp (data1=0x0, data2=0x555afd60) at 
cache-ct.c:104
#1  0xf633 in hashtable_find (table=0x555a9810, 
data=data@entry=0x555afd60,
id=) at hash.c:74
#2  0x5556434c in cache_find (c=c@entry=0x555a9710, 
ptr=ptr@entry=0x555afd60,
id=id@entry=0x7fff9ec4) at cache.c:304
#3  0x55564378 in cache_update_force (c=0x555a9710, 
ptr=0x555afd60) at cache.c:279
#4  0x555663b8 in dump_handler (type=NFCT_T_UPDATE, data=, ct=0x555afd60)
at ctnl.c:266
#5  dump_handler (type=NFCT_T_UPDATE, ct=0x555afd60, data=) 
at ctnl.c:257
#6  0x77ba47db in __callback (nlh=0x7fffa090, nfa=0x7fff9f50, 
data=0x555afd40)
at callback.c:58
#7  0x7778805c in nfnl_step (h=h@entry=0x555afa20, 
nlh=nlh@entry=0x7fffa090)
at libnfnetlink.c:1340
#8  0x77788823 in nfnl_process (h=h@entry=0x555afa20,
buf=buf@entry=0x7fffa090 , 
len=len@entry=3604) at libnfnetlink.c:1385
#9  0x77788b8e in nfnl_catch (h=0x555afa20) at libnfnetlink.c:1539
#10 0x77ba562f in nfct_query (h=0x555afc00, qt=qt@entry=NFCT_Q_DUMP,
data=data@entry=0x555772e4 ) at api.c:970
#11 0x55561f71 in nl_dump_conntrack_table (h=) at 
netlink.c:153
#12 0x5556661f in ctnl_init () at ctnl.c:456
#13 0xf505 in init () at run.c:301
#14 0xdf72 in main (argc=1, argv=0x7fffe428) at main.c:367

*** /tmp/valgrind.log
# valgrind conntrackd
==13777== Memcheck, a memory error detector
==13777== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==13777== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==13777== Command: conntrackd
==13777==
[Tue Jul 14 16:44:45 2020] (pid=13777) [notice] disabling external cache
==13777== Invalid read of size 8
==13777==at 0x113608: hashtable_find (hash.c:72)
==13777==by 0x118377: cache_update_force (cache.c:279)
==13777==by 0x11A3B7: dump_handler (ctnl.c:266)
==13777==by 0x11A3B7: dump_handler (ctnl.c:257)
==13777==by 0x4A5A7DA: __callback (callback.c:58)
==13777==by 0x4E8A05B: nfnl_step (libnfnetlink.c:1340)
==13777==by 0x4E8A822: nfnl_process (libnfnetlink.c:1385)
==13777==by 0x4E8AB8D: nfnl_catch (libnfnetlink.c:1539)
==13777==by 0x4A5B62E: nfct_query (api.c:970)
==13777==by 0x11A61E: ctnl_init (ctnl.c:456)
==13777==by 0x113504: init (run.c:301)
==13777==by 0x111F71: main (main.c:367)
==13777==  Address 0x54af660 is 0 bytes after a block of size 32 alloc'd
==13777==at 0x4837B65: calloc (vg_replace_malloc.c:752)
==13777==by 0x113577: hashtable_create (hash.c:39)
==13777==by 0x117E8D: cache_create (cache.c:102)
==13777==by 0x121796: internal_cache_init (internal_cache.c:26)
==13777==by 0x11ADAC: init_sync (sync-mode.c:396)
==13777==by 0x11A52A: ctnl_init (ctnl.c:414)
==13777==by 0x113504: init (run.c:301)
==13777==by 0x111F71: main (main.c:367)
==13777==
==13777== Invalid read of size 8
==13777==at 0x118BA1: cache_ct_cmp 

Processed: fixed 871201 in 9.9.0-2, closing 871201

[Debian Bug Tracking System]

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

> fixed 871201 9.9.0-2
Bug #871201 [src:eclipse-cdt] eclipse-cdt: FTBFS: 
java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (No such file or directory)
Marked as fixed in versions eclipse-cdt/9.9.0-2.
> close 871201
Bug #871201 [src:eclipse-cdt] eclipse-cdt: FTBFS: 
java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (No such file or directory)
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: unarchiving 871201, reopening 871201, unarchiving 725452, reopening 725452, unarchiving 702059 ...

[Debian Bug Tracking System]

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

> # src:eclipse-cdt was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 871201
Bug #871201 {Done: Debian FTP Masters } 
[src:eclipse-cdt] eclipse-cdt: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (No such file or directory)
Unarchived Bug 871201
> reopen 871201
Bug #871201 {Done: Debian FTP Masters } 
[src:eclipse-cdt] eclipse-cdt: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (No such file or directory)
'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 8.6.0-2+rm.
> unarchive 725452
Bug #725452 {Done: Debian FTP Masters } 
[eclipse-cdt] eclipse: After project delete and import, eclipse doesn't 
re-import the gcc includes
Unarchived Bug 725452
> reopen 725452
Bug #725452 {Done: Debian FTP Masters } 
[eclipse-cdt] eclipse: After project delete and import, eclipse doesn't 
re-import the gcc includes
'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 8.6.0-2+rm.
> unarchive 702059
Bug #702059 {Done: Debian FTP Masters } 
[eclipse-cdt] eclipse-cdt is missing a dep: libglib2.0-bin, crashed after 
startup
Unarchived Bug 702059
> reopen 702059
Bug #702059 {Done: Debian FTP Masters } 
[eclipse-cdt] eclipse-cdt is missing a dep: libglib2.0-bin, crashed after 
startup
'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 8.6.0-2+rm.
> unarchive 758062
Bug #758062 {Done: Debian FTP Masters } 
[eclipse-cdt] [eclipse-cdt] New project wizard result in null pointer exception 
when populating project types
Unarchived Bug 758062
> reopen 758062
Bug #758062 {Done: Debian FTP Masters } 
[eclipse-cdt] [eclipse-cdt] New project wizard result in null pointer exception 
when populating project types
'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 8.6.0-2+rm.
> thanks
Stopping processing here.

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

Processed: fixed 964334 in 83.0.4103.116-1~deb10u3

[Debian Bug Tracking System]

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

> fixed 964334 83.0.4103.116-1~deb10u3
Bug #964334 {Done: Michael Gilbert } [chromium] segfault 
repeatedly
Bug #963548 {Done: Michael Gilbert } [chromium] Received 
signal 11 SEGV_MAPERR
Bug #964287 {Done: Michael Gilbert } [chromium] chromium: 
crashes after page interaction due to a double free
Bug #964362 {Done: Michael Gilbert } [chromium] chromium 
crash frequently, SEGV_MAPERR
Bug #964451 {Done: Michael Gilbert } [chromium] chromium 
(83.0.4103.116-1~deb10u2) constantly crashes and slow
Bug #964760 {Done: Michael Gilbert } [chromium] chromium: 
Chromium 83.0.4103.116-2 crash : SEGV_MAPERR
Bug #964817 {Done: Michael Gilbert } [chromium] chromium 
83.0.4103.116-1~deb10u2 crashes frequently
Marked as fixed in versions chromium/83.0.4103.116-1~deb10u3.
Marked as fixed in versions chromium/83.0.4103.116-1~deb10u3.
Marked as fixed in versions chromium/83.0.4103.116-1~deb10u3.
Marked as fixed in versions chromium/83.0.4103.116-1~deb10u3.
Marked as fixed in versions chromium/83.0.4103.116-1~deb10u3.
Marked as fixed in versions chromium/83.0.4103.116-1~deb10u3.
Marked as fixed in versions chromium/83.0.4103.116-1~deb10u3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
963548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963548
964287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964287
964334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964334
964362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964362
964451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964451
964760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964760
964817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#965019: mir FTBFS with protobuf 3.12.3

[Adrian Bunk]

Source: mir
Version: 1.7.0+dfsg1-1
Severity: serious
Tags: ftbfs

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

...
/<>/src/server/frontend/protobuf_responder.cpp: In member function 
‘virtual void 
mir::frontend::detail::ProtobufResponder::send_response(google::protobuf::uint32,
 google::protobuf::MessageLite*, const FdSets&)’:
/<>/src/server/frontend/protobuf_responder.cpp:42:69: error: ‘int 
google::protobuf::MessageLite::ByteSize() const’ is deprecated: Please use 
ByteSizeLong() instead [-Werror=deprecated-declarations]
   42 | send_response_buffer{static_cast(response->ByteSize())};
  | ^
In file included from /usr/include/google/protobuf/generated_enum_util.h:36,
 from /usr/include/google/protobuf/map.h:55,
 from 
/usr/include/google/protobuf/generated_message_table_driven.h:34,
 from 
/<>/build-arm64/src/protobuf/mir_protobuf_wire.pb.h:26,
 from 
/<>/src/server/frontend/protobuf_responder.h:23,
 from 
/<>/src/server/frontend/protobuf_responder.cpp:19:
/usr/include/google/protobuf/message_lite.h:420:7: note: declared here
  420 |   int ByteSize() const { return internal::ToIntSize(ByteSizeLong()); }
  |   ^~~~
...

Bug#965014: marked as done (bsdmainutils: binaries uploaded)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 14:39:20 +
with message-id 
and subject line Bug#965014: fixed in bsdmainutils 12.1.5
has caused the Debian Bug report #965014,
regarding bsdmainutils: binaries uploaded
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.)


-- 
965014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bsdmainutils
Version: 12.1.4
Severity: serious
Justification: can't migrate per Britney policy.

Hello, thanks for fixing the bsdmainutils RC bugs, but without a source-only 
upload, the package
won't ever migrate to testing.
In specific, the arch:all packages can't be binNMUed, so please reupload if you 
want the fix to go in testing.

thanks!

Gianfranco
--- End Message ---
--- Begin Message ---
Source: bsdmainutils
Source-Version: 12.1.5
Done: Michael Meskes 

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

Debian distribution maintenance software
pp.
Michael Meskes  (supplier of updated bsdmainutils 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, 14 Jul 2020 15:42:14 +0200
Source: bsdmainutils
Architecture: source
Version: 12.1.5
Distribution: unstable
Urgency: medium
Maintainer: Debian Bsdmainutils Team 
Changed-By: Michael Meskes 
Closes: 965014
Changes:
 bsdmainutils (12.1.5) unstable; urgency=medium
 .
   * Source only upload. (Closes: #965014)
Checksums-Sha1:
 45299204f6e818d29437a6e1e741ff447e7d97fe 1759 bsdmainutils_12.1.5.dsc
 3d5c9b75488cf314d4f6d7f1b5a1dc641743c884 172380 bsdmainutils_12.1.5.tar.xz
 7a10f711e93a078590f687edd859fa4e59dfb613 6693 
bsdmainutils_12.1.5_amd64.buildinfo
Checksums-Sha256:
 d0da2f4499a138170ac7265a93de32dd9062db9b401f6c9d7130e56e7b426137 1759 
bsdmainutils_12.1.5.dsc
 a91244129fdb1c0bd6be6d757b18d9c52600766312d1af927207118ca3be1ea4 172380 
bsdmainutils_12.1.5.tar.xz
 ce0c872815d866efc1235137c2210fa7cb85c042b5faf4855df484c5236972a2 6693 
bsdmainutils_12.1.5_amd64.buildinfo
Files:
 0129adb19eb17eb9441395d906b39330 1759 utils optional bsdmainutils_12.1.5.dsc
 5bd37cbabacaf11bee8c3bb3788edcce 172380 utils optional 
bsdmainutils_12.1.5.tar.xz
 263b8249171a4a977a53cd69a146ae03 6693 utils optional 
bsdmainutils_12.1.5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEZ/2RWVGI6sRsEOjtNdhXwLvLOyUFAl8NuHUACgkQNdhXwLvL
OyWa0w//fgCGz4srM4hGBHozAyMKU2kM48ABim1QlzMofyZdAm/vhezYJv52XKSN
HONhVwrF46hYVSBtI6ibrGSvh8i87GxPE4o/BQmXmgORl4CiFwQq7Y3KIefJLV1O
gYq3TgwrQheUDG3oePW+YgyXWcP/P8pfsKBfX4GiMHHFIYUd0Qa3Jxm+E+f53H/R
JPTcMIjJMf/E25FDpUPmfu/+KNfyXzy+JJwmgT473ZszcBUJ7lhrApFLlxtcQGIx
G4UmzTG9CWW1IRxx/pdoygrQ+F4g78bWDH1GobC2mqgX5rH8TkWsztVIwAfEXpiT
Uzh634lwFOl4ouSC9eQakqdmH3BgK7adHwiUviEcZDNnKe/qcixm8lDpxvmozUCB
74q2qqTjQI7iXpcjL9EKvJw1gSyOmOqyMTPJV0cj089TQUyACxTptzwxKXXKqMWp
RlQ4kd2zzORx8E00h2Xi/92lCpcwjzqb3cbu+KJvOVK5hCL2c2s2uE9QHXhKGi+x
fNGWLr+o/te2Q4uiK8mZ/So6kPIYsDO+KNFbaK8SbWUgtBOVTP+BnyMgkl7gQOqO
49TzNU5yUNui4GivQhDnums4O/Qoq4IgMbu/Pw4rxIo74KUw1EurIPtj305rmzCi
X0YP1LEIuB4sg8EioXf2n/k6lnnx4m2obiyo1iikW2TaAJ7Qk0M=
=9Q2o
-END PGP SIGNATURE End Message ---

Processed: Fix metadata by moving where it was fixed

[Debian Bug Tracking System]

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

> reassign 964242 util-linux 2.35.2-6
Bug #964242 {Done: Chris Hofstaedtler } [bsdmainutils] 
bsdmainutils: depends on non-existing version of bsdextrautils
Bug reassigned from package 'bsdmainutils' to 'util-linux'.
No longer marked as found in versions bsdmainutils/12.1.3.
No longer marked as fixed in versions util-linux/2.35.2-7 and 
bsdmainutils/12.1.3.
Bug #964242 {Done: Chris Hofstaedtler } [util-linux] 
bsdmainutils: depends on non-existing version of bsdextrautils
Marked as found in versions util-linux/2.35.2-6.
> fixed 964242 2.35.2-7
Bug #964242 {Done: Chris Hofstaedtler } [util-linux] 
bsdmainutils: depends on non-existing version of bsdextrautils
Marked as fixed in versions util-linux/2.35.2-7.
> affects 964242 bsdmainutils
Bug #964242 {Done: Chris Hofstaedtler } [util-linux] 
bsdmainutils: depends on non-existing version of bsdextrautils
Added indication that 964242 affects bsdmainutils
> thanks
Stopping processing here.

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

Processed: tagging 964084

[Debian Bug Tracking System]

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

> tags 964084 + ftbfs
Bug #964084 [src:haskell-derive] haskell-derive: Removal notice: broken and 
unmaintained
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#963325: marked as done (alot: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 15:34:22 +0200
with message-id <159473366251.924536.9632456319219985162@localhost>
and subject line Forgot to close bug in d/changelog
has caused the Debian Bug report #963325,
regarding alot: FTBFS: dh_auto_test: error: pybuild --test -i python{version} 
-p 3.8 returned exit code 13
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.)


-- 
963325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alot
Version: 0.9-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d build/doctrees  -D today="March 12, 2020" source 
> build/html
> Running Sphinx v2.4.3
> making output directory... done
> loading intersphinx inventory from 
> file:///usr/share/doc/python-doc/html/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'file:///usr/share/doc/python-doc/html/objects.inv' not 
> fetchable due to : No connection 
> adapters were found for 'file:///usr/share/doc/python-doc/html/objects.inv'
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 35 source files that are out of date
> updating environment: [new config] 35 added, 0 changed, 0 removed
> reading sources... [  2%] api/commands
> reading sources... [  5%] api/crypto
> reading sources... [  8%] api/database
> reading sources... [ 11%] api/index
> reading sources... [ 14%] api/interface
> reading sources... [ 17%] api/overview
> reading sources... [ 20%] api/settings
> reading sources... [ 22%] api/utils
> reading sources... [ 25%] configuration/accounts
> reading sources... [ 28%] configuration/config_options
> reading sources... [ 31%] configuration/contacts_completion
> reading sources... [ 34%] configuration/hooks
> reading sources... [ 37%] configuration/index
> reading sources... [ 40%] configuration/key_bindings
> reading sources... [ 42%] configuration/theming
> reading sources... [ 45%] description
> reading sources... [ 48%] faq
> reading sources... [ 51%] index
> reading sources... [ 54%] installation
> reading sources... [ 57%] manpage
> reading sources... [ 60%] usage/cli_commands
> reading sources... [ 62%] usage/cli_options
> reading sources... [ 65%] usage/commands
> reading sources... [ 68%] usage/crypto
> reading sources... [ 71%] usage/first_steps
> reading sources... [ 74%] usage/index
> reading sources... [ 77%] usage/modes/bufferlist
> reading sources... [ 80%] usage/modes/envelope
> reading sources... [ 82%] usage/modes/global
> reading sources... [ 85%] usage/modes/namedqueries
> reading sources... [ 88%] usage/modes/search
> reading sources... [ 91%] usage/modes/taglist
> reading sources... [ 94%] usage/modes/thread
> reading sources... [ 97%] usage/signals
> reading sources... [100%] usage/synopsis
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [  2%] api/commands
> writing output... [  5%] api/crypto
> writing output... [  8%] api/database
> writing output... [ 11%] api/index
> writing output... [ 14%] api/interface
> writing output... [ 17%] api/overview
> writing output... [ 20%] api/settings
> writing output... [ 22%] api/utils
> writing output... [ 25%] configuration/accounts
> writing output... [ 28%] configuration/config_options
> writing output... [ 31%] configuration/contacts_completion
> writing output... [ 34%] configuration/hooks
> writing output... [ 37%] configuration/index
> writing output... [ 40%] configuration/key_bindings
> writing output... [ 42%] configuration/theming
> writing output... [ 45%] description
> writing output... [ 48%] faq
> writing output... [ 51%] index
> writing output... [ 54%] installation
> writing output... [ 57%] manpage
> writing output... [ 60%] usage/cli_commands
> writing output... [ 62%] usage/cli_options
> writing output... [ 65%] usage/commands
> writing output... [ 68%] usage/crypto
> writing output... [ 71%] usage/first_steps
> writing output... [ 74%] usage/index
> writing output... [ 77%] usage/modes/bufferlist
> writing output... [ 80%] usage/modes/envelope
> writing output... [ 82%] usage/modes/global
> writing output... [ 85%] usage/modes/namedqueries
> writing output... [ 88%] usage/modes/search
> writing output... [ 

Bug#965016: Manuskript crashes when browsing scenes

[Víctor Bedoya Ponte]

Package: Manuskript
Version: 0.8.0-1
Severity: grave

   * I start Manuskript
   * I try it first with a saved project; then I also try without a saved 
project, and the outcome is the same. In both cases, I browse some scenes, I 
modify some settings, or I start full-screen mode.
   * What was the outcome of this action? The program crashes.
   * What outcome did you expect instead? Change scenes, modify settings, 
start full-screen mode

-- Terminal output:

qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 672, resource 
id: 0, major code: 19 (DeleteProperty), minor code: 0
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = python3.7 path = /usr/bin pid = 5111
KCrash: Arguments: /usr/bin/python3.7 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from 
kdeinit
sock_file=/run/user/1000/kdeinit5__0


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

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

Versions of packages manuskript depends on:
ii  libqt5svg5  5.11.3-2
ii  python3 3.7.3-1
ii  python3-enchant 2.0.0-1
ii  python3-lxml4.3.2-1
ii  python3-markdown3.0.1-3
ii  python3-pyqt5   5.11.3+dfsg-1+b3
ii  python3-pyqt5.qtwebkit  5.11.3+dfsg-1+b3
ii  zlib1g  1:1.2.11.dfsg-1


-- Python shows this message: 

Application: python3.7 (python3.7), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0a7ad4e740 (LWP 5111))]

Thread 6 (Thread 0x7f0a5e032700 (LWP 5117)):
#0  0x7f0a7b30a00c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-
linux-gnu/libpthread.so.0
#1  0x7f0a5e620e83 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#2  0x7f0a5e620bd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#3  0x7f0a7b303fa3 in start_thread () from /lib/x86_64-linux-gnu/
libpthread.so.0
#4  0x7f0a7ae4a4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 5 (Thread 0x7f0a6501f700 (LWP 5116)):
#0  0x7f0a75e6de69 in g_mutex_lock () from /lib/x86_64-linux-gnu/
libglib-2.0.so.0
#1  0x7f0a75e23ca6 in g_main_context_dispatch () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#2  0x7f0a75e241c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0a75e2425c in g_main_context_iteration () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#4  0x7f0a797dd743 in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0a7978b15b in 
QEventLoop::exec(QFlags) () from /lib/x86_64-
linux-gnu/libQt5Core.so.5
#6  0x7f0a795dae76 in QThread::exec() () from /lib/x86_64-linux-gnu/
libQt5Core.so.5
#7  0x7f0a795e4a67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f0a7b303fa3 in start_thread () from /lib/x86_64-linux-gnu/
libpthread.so.0
#9  0x7f0a7ae4a4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7f0a67fff700 (LWP 5114)):
#0  0x7f0a75e6de69 in g_mutex_lock () from /lib/x86_64-linux-gnu/
libglib-2.0.so.0
#1  0x7f0a75e23140 in g_main_context_acquire () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#2  0x7f0a75e23ff5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0a75e2425c in g_main_context_iteration () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#4  0x7f0a797dd743 in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0a7978b15b in 
QEventLoop::exec(QFlags) () from /lib/x86_64-
linux-gnu/libQt5Core.so.5
#6  0x7f0a795dae76 in QThread::exec() () from /lib/x86_64-linux-gnu/
libQt5Core.so.5
#7  0x7f0a6fbf4545 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f0a795e4a67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f0a7b303fa3 in start_thread () from /lib/x86_64-linux-gnu/
libpthread.so.0
#10 0x7f0a7ae4a4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f0a6eabd700 (LWP 5113)):
#0  0x7f0a7ae3f819 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f0a71f6ecf7 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f0a71f7091a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/
libxcb.so.1
#3  0x7f0a6fd01d79 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f0a795e4a67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0a7b303fa3 in start_thread () from /lib/x86_64-linux-gnu/
libpthread.so.0
#6  0x7f0a7ae4a4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 

Bug#885195: [Pkg-electronics-devel] Bug#885195: Bug#885195: geda-gaf: please migrate to guile-2.2

[Bdale Garbee]

I'm not interested in maintaining pcb any more.

Bdale

On July 13, 2020 7:04:01 PM MDT, Rob Browning  wrote:
>Bdale Garbee  writes:
>
>> So... while I'm sure gEDA could be "saved" in Debian with enough
>effort,
>> I just don't see the point, and won't put any time or attention on it
>> myself.   
>
>I'd suggest we should do something "soonish".  This is the last package
>holding guile-2.0 in testing, and I'd *really* like to be able to
>finish
>the guile-2.0 removal.
>
>For what it's worth, I thought I'd see how hard it might be to update
>to
>guile-3.0, and the attached (very primitive/incomplete) diff does get
>the current package to build and pass all but one of the tests here
>(assuming that wasn't a short-circuit and there are more tests after
>that).
>
>However, unless someone's interested in maintaining the package,
>pursuing guile-3.0 support, upgrading to 1.10, etc.  Perhaps it's best
>to file for removal now.  We can always reintroduce it later, if the
>situation improves.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#963808: ruby-sanitize: CVE-2020-4054: HTML sanitization bypass in Sanitize

[terceiro]

On Mon, Jul 13, 2020 at 10:04:10PM +0200, Salvatore Bonaccorso wrote:
> Hi Antonio,
> 
> On Mon, Jul 13, 2020 at 11:19:38AM -0300, terce...@debian.org wrote:
> > On Sun, Jul 12, 2020 at 03:11:30PM +0200, Salvatore Bonaccorso wrote:
> > > On Sat, Jun 27, 2020 at 09:10:01PM +0200, Salvatore Bonaccorso wrote:
> > > > Source: ruby-sanitize
> > > > Version: 4.6.6-2
> > > > Severity: grave
> > > > Tags: security upstream
> > > > Justification: user security hole
> > > > 
> > > > Hi,
> > > > 
> > > > The following vulnerability was published for ruby-sanitize.
> > > > 
> > > > CVE-2020-4054[0]:
> > > > | In Sanitize (RubyGem sanitize) greater than or equal to 3.0.0 and less
> > > > | than 5.2.1, there is a cross-site scripting vulnerability. When HTML
> > > > | is sanitized using Sanitize's "relaxed" config, or a custom config
> > > > | that allows certain elements, some content in a math or svg element
> > > > | may not be sanitized correctly even if math and svg are not in the
> > > > | allowlist. You are likely to be vulnerable to this issue if you use
> > > > | Sanitize's relaxed config or a custom config that allows one or more
> > > > | of the following HTML elements: iframe, math, noembed, noframes,
> > > > | noscript, plaintext, script, style, svg, xmp. Using carefully crafted
> > > > | input, an attacker may be able to sneak arbitrary HTML through
> > > > | Sanitize, potentially resulting in XSS (cross-site scripting) or other
> > > > | undesired behavior when that HTML is rendered in a browser. This has
> > > > | been fixed in 5.2.1.o
> > > 
> > > Attached ist a preliminary debdiff with the fix, but two prerequisites
> > > before "fix: Don't treat :remove_contents as `true` when it's an
> > > Array" and "feat: Remove useless filtered element content by default".
> > > 
> > > Antonio, would it be possible to let it go trough your second pair of
> > > eyes, with the pre-knolege that I'm not familiar with the package but
> > > trying to address the CVE-2020-4054.
> > > 
> > > If those look correct, the plan would be to do 4.6.6-2.1~deb10u1 based
> > > on that for buster-security.
> > 
> > Yes, those patches look OK.
> > 
> > Thanks for your work.
> 
> Thanks for your review! So propsing to upload the NMU first, and then
> later handle the DSA for it based on that version if no negative
> reports come in.

Sure, just do it.


signature.asc
Description: PGP signature

Bug#965014: bsdmainutils: binaries uploaded

[Gianfranco Costamagna]

Source: bsdmainutils
Version: 12.1.4
Severity: serious
Justification: can't migrate per Britney policy.

Hello, thanks for fixing the bsdmainutils RC bugs, but without a source-only 
upload, the package
won't ever migrate to testing.
In specific, the arch:all packages can't be binNMUed, so please reupload if you 
want the fix to go in testing.

thanks!

Gianfranco

Processed: tagging 963452

[Debian Bug Tracking System]

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

> tags 963452 + confirmed
Bug #963452 [src:varnish-modules] varnish-modules: FTBFS: dpkg-gencontrol: 
error: error occurred while parsing Depends field: libc6 (>= 2.14), 
libvarnishapi2 (>= 6.1.0),
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#965013: quart FTBFS: no theme named 'pydata_sphinx_theme' found

[Adrian Bunk]

Source: quart
Version: 0.12.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=quart=all=0.12.0-1=1594718034=0

...
/usr/bin/make -C docs clean html SPHINXBUILD=sphinx-build SPHINXOPTS="-N -D 
html_last_updated_fmt=\"14 July 2020\""
make[2]: Entering directory '/<>/docs'
Running Sphinx v2.4.3
making output directory... done

Theme error:
no theme named 'pydata_sphinx_theme' found (missing theme.conf?)
make[2]: *** [Makefile:20: html] Error 2

Processed: Bug metadata corrections

[Debian Bug Tracking System]

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

> reassign 964231 src:faketime 0.9.7-3
Bug #964231 [faketime] faketime: FTBFS with glibc 2.31 due to ftime deprecation
Bug reassigned from package 'faketime' to 'src:faketime'.
No longer marked as found in versions faketime/0.9.7-3.
Ignoring request to alter fixed versions of bug #964231 to the same values 
previously set
Bug #964231 [src:faketime] faketime: FTBFS with glibc 2.31 due to ftime 
deprecation
Marked as found in versions faketime/0.9.7-3.
> tags 964231 ftbfs bullseye sid
Bug #964231 [src:faketime] faketime: FTBFS with glibc 2.31 due to ftime 
deprecation
Added tag(s) ftbfs, sid, and bullseye.
> thanks
Stopping processing here.

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

Bug#963292: add patch

[Matthias Klose]

Control: tags -1 + patch

patch at
http://launchpadlibrarian.net/488517436/libdata-messagepack-perl_1.00-2build3_1.00-2ubuntu1.diff.gz

there's also a "new" upstream 1.01.

Processed: add patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #963292 [src:libdata-messagepack-perl] libdata-messagepack-perl: FTBFS: 
pack_template.h:897:65: error: unknown type name ‘msgpack_timestamp’
Bug #950460 [src:libdata-messagepack-perl] libdata-messagepack-perl: FTBFS with 
msgpack-c/3.2.1-1
Added tag(s) patch.
Added tag(s) patch.

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

Bug#964270: marked as done (salt: autopkgtest regression: [Errno 6] No such device or address)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 11:50:15 +
with message-id 
and subject line Bug#964270: fixed in salt 3001+dfsg1-2
has caused the Debian Bug report #964270,
regarding salt: autopkgtest regression: [Errno 6] No such device or address
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.)


-- 
964270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: salt
Version: 3001+dfsg1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of salt the autopkgtest of salt fails in testing
when that autopkgtest is run with the binary packages of salt from
unstable. It passes when run with only packages from testing. In tabular
form:

   passfail
salt   from testing3001+dfsg1-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=salt

https://ci.debian.net/data/autopkgtest/testing/amd64/s/salt/6135926/log.gz

==
ERROR: test_run_cwd_in_combination_with_runas
(unit.modules.test_cmdmod.CMDMODTestCase)
[CPU:0.0%|MEM:6.3%] cmd.run executes command in the cwd directory
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.vefy12bw/downtmp/autopkgtest_tmp/tests/unit/modules/test_cmdmod.py",
line 449, in test_run_cwd_in_combination_with_runas
runas = os.getlogin()
OSError: [Errno 6] No such device or address

--
Ran 9852 tests in 220.597s

FAILED (errors=1, skipped=2164, expected failures=1)
Exception ignored in: 
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/salt/transport/ipc.py", line 695,
in _read
TypeError: catching classes that do not inherit from BaseException is
not allowed
autopkgtest [15:28:11]: test unittest: ---]




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: salt
Source-Version: 3001+dfsg1-2
Done: Benjamin Drung 

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated salt 
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, 14 Jul 2020 12:57:17 +0200
Source: salt
Architecture: source
Version: 3001+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Salt Team 
Changed-By: Benjamin Drung 
Closes: 964270 964614
Changes:
 salt (3001+dfsg1-2) unstable; urgency=medium
 .
   * tests: Replace os.getlogin by getpass.getuser (Closes: #964270, #964614)
Checksums-Sha1:
 5f0fa4559746c4543807a6e35eb47dd00a23d2ef 4111 salt_3001+dfsg1-2.dsc
 7226a89446d2b1d33fd3f9e37910a3f6a24728a5 71796 salt_3001+dfsg1-2.debian.tar.xz
 4cdb3db6a5ae13ee3d6151c7407fc650f673fdd3 13944 
salt_3001+dfsg1-2_source.buildinfo
Checksums-Sha256:
 79b1b978ea127486bafb9d36adac6da71510ae51ae6f05e7dfac1b76e060579e 4111 
salt_3001+dfsg1-2.dsc
 f8559e364cd25cb109af503f6be5fbfce40f84a4c6f1e25d31effcab771047a8 71796 
salt_3001+dfsg1-2.debian.tar.xz
 c24e0c2bb56b4f84a892caef7c54f48e1f37d62ff9f167de16efdf5de3a7da60 13944 
salt_3001+dfsg1-2_source.buildinfo
Files:
 4569b1f1f9405040f2f33dccd03daea5 4111 admin optional salt_3001+dfsg1-2.dsc
 34b94e88a120bd2cd3d05a84329f9e9b 71796 admin optional 
salt_3001+dfsg1-2.debian.tar.xz
 f28e93a412eba8b858828f318e8267b2 13944 admin optional 
salt_3001+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#964309: marked as done (bsdmainutils: FTBFS because of missing libncurses-dev dependency)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 11:48:36 +
with message-id 
and subject line Bug#964309: fixed in bsdmainutils 12.1.4
has caused the Debian Bug report #964309,
regarding bsdmainutils: FTBFS because of missing libncurses-dev dependency
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.)


-- 
964309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bsdmainutils
Version: 12.1.3
Severity: serious
Justification: FTBFS

Hello,

bsdmainutils currently FTBFS because it is missing the libncurses-dev
dependency, leading to

ncal.c:46:10: fatal error: term.h: No such file or directory
   46 | #include 

Samuel

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

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

Versions of packages bsdmainutils depends on:
ii  bsdutils 1:2.35.2-4
ii  debianutils  4.9.1
ii  libbsd0  0.10.0-1
ii  libc62.30-8
ii  libtinfo66.2-1

Versions of packages bsdmainutils recommends:
ii  bsdextrautils  2.35.2-4

Versions of packages bsdmainutils suggests:
pn  calendar  
pn  vacation  
ii  wamerican [wordlist]  2019.10.06-1
ii  wfrench [wordlist]1.2.6-1
ii  whois 5.5.6

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: bsdmainutils
Source-Version: 12.1.4
Done: Michael Meskes 

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

Debian distribution maintenance software
pp.
Michael Meskes  (supplier of updated bsdmainutils 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, 14 Jul 2020 13:12:27 +0200
Source: bsdmainutils
Binary: bsdmainutils calendar calendar-dbgsym ncal ncal-dbgsym
Architecture: source all amd64
Version: 12.1.4
Distribution: unstable
Urgency: medium
Maintainer: Debian Bsdmainutils Team 
Changed-By: Michael Meskes 
Description:
 bsdmainutils - collection of more utilities from FreeBSD
 calendar   - display upcoming dates and provide reminders
 ncal   - display a calendar and the date of Easter
Closes: 946726 964309 964389
Changes:
 bsdmainutils (12.1.4) unstable; urgency=medium
 .
   * Re-added libncurses-dev built dependency that was lost during the
 transition.
 (Closes: #964309)
   * Fix config file handling. (Closes: #964389)
   * Add patch to calendar to cleanup after fork(). (Closes: #946726)
Checksums-Sha1:
 e457561c3ca60c161985e01b5d87d49aa5f2a010 1759 bsdmainutils_12.1.4.dsc
 06e8c3ced1fc68af2bb0d40ea1aa9bd3f680fe94 172340 bsdmainutils_12.1.4.tar.xz
 c19a1b8281992448a30e6aba42c5dcd164d87f48 15880 bsdmainutils_12.1.4_all.deb
 407eef973141bab78b7264ba02c6cdab804f3853 6590 
bsdmainutils_12.1.4_amd64.buildinfo
 28c95c2a9ca92c1930f5f513b2c1974b40a5ec94 25408 calendar-dbgsym_12.1.4_amd64.deb
 25e68b6d1c28889e71d5194b669ea66e2a92c0be 131384 calendar_12.1.4_amd64.deb
 9d557e34d7742263aa1e157eb9b359c80e4b7746 29384 ncal-dbgsym_12.1.4_amd64.deb
 f7d554266de15981b926fb8b0ed7502288f9d173 29336 ncal_12.1.4_amd64.deb
Checksums-Sha256:
 d50a87424dd60c3714eed2c4093a054ceea80b018c7ccc249b0a83b73005f000 1759 
bsdmainutils_12.1.4.dsc
 4148edeed6c8fa443bd6f8ad97e5aef6b5001fb31df5f6bf9e560f6e4b8248c2 172340 
bsdmainutils_12.1.4.tar.xz
 

Bug#964691: marked as done (omnidb: FTBFS: build-dependency not installable: fonts-glewlwyd)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 11:49:47 +
with message-id 
and subject line Bug#964691: fixed in omnidb 2.17.0+ds-2
has caused the Debian Bug report #964691,
regarding omnidb: FTBFS: build-dependency not installable: fonts-glewlwyd
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.)


-- 
964691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: omnidb
Version: 2.17.0+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 11), dh-python, fonts-glewlwyd, 
> fonts-roboto-unhinted, libjs-excanvas, libjs-jquery, libjs-jquery-ui, 
> postgresql-server-dev-all, python3:any | python3-all:any | python3-dev:any | 
> python3-all-dev:any, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 11), dh-python, fonts-glewlwyd, 
> fonts-roboto-unhinted, libjs-excanvas, libjs-jquery, libjs-jquery-ui, 
> postgresql-server-dev-all, python3:any, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [458 B]
> Get:5 copy:/<>/apt_archive ./ Packages [526 B]
> Fetched 1941 B in 0s (190 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: fonts-glewlwyd but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/omnidb_2.17.0+ds-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: omnidb
Source-Version: 2.17.0+ds-2
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated omnidb 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, 14 Jul 2020 13:14:54 +0200
Source: omnidb
Architecture: source
Version: 2.17.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
Changed-By: Christoph Berg 
Closes: 962878 964691
Changes:
 omnidb (2.17.0+ds-2) unstable; urgency=medium
 .
   * Add "shared files" to omnidb-common description.
   * B-D on fonts-glyphicons-halflings instead of fonts-glewlwyd.
 (Closes: #962878, #964691
   * DH 13.
Checksums-Sha1:
 bdc1e2b7ca284e277aaa889506bdd2400ab82f67 2353 omnidb_2.17.0+ds-2.dsc
 6121a55e60c9735e6317a36896d2bc3b8c6c387a 9728 

Bug#962878: marked as done (omnidb-common: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd))

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 11:49:47 +
with message-id 
and subject line Bug#962878: fixed in omnidb 2.17.0+ds-2
has caused the Debian Bug report #962878,
regarding omnidb-common: should depend on fonts-font-awesome and/or 
fonts-glyphicons-halflings (not fonts-glewlwyd)
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.)


-- 
962878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: omnidb-common
Version: 2.17.0+ds-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

omnidb-common depends on fonts-glewlwyd,
which contains the fonts font-awesome and glyphicons-halflings.

Please instead depend on fonts-font-awesome and/or
fonts-glyphicons-halflings as needed,
so that fonts-glewlwyd can be dropped from Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl7ndY4ACgkQLHwxRsGg
ASFHJBAAouLRkVI5ks4SpcL9VjanALoILa0vAUsGiClFXaL6daPTvSJ/tornlYtn
Jl0iMWvyODEerl+IlYCG63Y7Z/4zZ5+cVPIXu/NXOGeiy/j5Hk/CX7et8QvqIR3t
Bp+0n80T9KQVIxQ3AQSSBeYODSFq1hAwnNHKJjOwubJFsmqEY4MqPh3RpMEVGIym
ieeEBVpaUY84ekmBADYv/UaZVw0f29SJcLm7pABFbhr90VJm/oC2ZC6dTpOX8hqA
OJ7drfejSCpGvpDJ93VcR/lQoGDRqYrfBmFtFE2cy84Sc2EjAMS+Ahvl+kCI5PBP
xcPIzsGW35/NbQM03AWA5Yg3lSZsc/QSMKwJE+EvqYcnt4kVqrv3gUidWfjJ1ZtU
w+QwNK2KiX1Hd0Q6h95lnHySpIMAl5hjnt1wpsbv3k1cPhmCGzffJ/iXPSOjGO+X
sW8EU0OPJY8VM60Ejo1E67vJkXAjccYUOIXh4nIhtTC72OGBxe3ESAeji1sCDe1O
Ize8/QzhO1+4lbMD60H2+kazUcSqmi9nNiEdn1EqNREdBbiEMWl8dltZX4qas7g9
fsNCjGjFVT37uwGSo4yJmqm+QgvAUHPeefzvRBVRe2ygR27W+jQH3LyMsJ6nIOpF
rt9WA3QHsP+2l+an4pT8VD5ZL7HjlFxj2mPF+cWM933ClDyYKUg=
=nKg7
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: omnidb
Source-Version: 2.17.0+ds-2
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated omnidb 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, 14 Jul 2020 13:14:54 +0200
Source: omnidb
Architecture: source
Version: 2.17.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
Changed-By: Christoph Berg 
Closes: 962878 964691
Changes:
 omnidb (2.17.0+ds-2) unstable; urgency=medium
 .
   * Add "shared files" to omnidb-common description.
   * B-D on fonts-glyphicons-halflings instead of fonts-glewlwyd.
 (Closes: #962878, #964691
   * DH 13.
Checksums-Sha1:
 bdc1e2b7ca284e277aaa889506bdd2400ab82f67 2353 omnidb_2.17.0+ds-2.dsc
 6121a55e60c9735e6317a36896d2bc3b8c6c387a 9728 omnidb_2.17.0+ds-2.debian.tar.xz
Checksums-Sha256:
 59be5e4d4ca5796573f8e7dd9b375c0c545bbbf30ca43fe5fe9cbacd9e599ee0 2353 
omnidb_2.17.0+ds-2.dsc
 74b54160e73949cb085adfbff0a256e8b497c8b855818f51cf595401fe39f946 9728 
omnidb_2.17.0+ds-2.debian.tar.xz
Files:
 7d1601ff31f0f248e46960cc7d1a885e 2353 database optional omnidb_2.17.0+ds-2.dsc
 c0b3209f948a69e8aa1ea2fdf1a0bf25 9728 database optional 
omnidb_2.17.0+ds-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl8Nl9QACgkQTFprqxLS
p64k+w/6A+HGpUl3ZpKJf428C2bDcBgc7GnnxHNqj5cJvIQrJMYjO4cqJaRdiVye
tYHw8RK286UBEyS7AE6n3WahwqLpEJXodcX7ypdFrF8EwUDIzl/AWOVFRFT1fUqM
y1vOIiXGV4LrNi4QCNOjHxT1iVX9Zn2zF4hv6NslY3CJVh9GhA3pIi1N5xiRViOE
0KkG4oa1cn2/OtOBV3AyncVu0MJsrewy2l3BiH+wC5dT+bNg/jGGlFHf5YSM7PlJ
alipoFmk26RMSKVwn2tHgD8SW3xGCiuVKn+hRsGXlkr0t8fstdH/UAFZE5G2xQCl
1muuwrNloBZwDml7j8XT40SgaCYW+nOgl0+DsRKzua7vAHRcTRdZRIAvj0NLifcc
ml5s1lW8lPZH6ciFUNXALvWSz4NNhsYShqwj2Av+i095OYsPihQuHtbVJFut9Ty4
WhpOozm7ZOuyinEwU7oN0abrpjijBGhh8oVJhllRYF6NUaJp8PSjCb+4r3/TCPNw
rJTpWO2KezoYgPuAXAGR9LKLWcBHhBDlsxVB6eLFEBJobxZw+khtr5oS0K8XA4sZ
+agYZF6HK2hJuYb6Kps0uG8Tqlf88rVLQzJjJvRSsScob77f4V73aSiFdevtXlWg
BvlVkXEVRXisfwVqrhBQHs0C5t/avw41fCOlhvPqJPkrk2mqRTM=
=6vw0
-END PGP SIGNATURE End Message ---

Bug#965010: msgpack-c ftbfs on armhf (test failure)

[Matthias Klose]

Package: src:msgpack-c
Version: 3.3.0-1
Severity: serious
Tags: sid bullseye

msgpack-c ftbfs on armhf (test failure):

[...]
[ RUN  ] object_with_zone.system_clock_impl_min
../test/object_with_zone.cpp:1031: Failure
Value of: obj.as() == v
  Actual: false
Expected: true
[  FAILED  ] object_with_zone.system_clock_impl_min (0 ms)

Processed: Bug#962878 marked as pending in omnidb

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #962878 [omnidb-common] omnidb-common: should depend on fonts-font-awesome 
and/or fonts-glyphicons-halflings (not fonts-glewlwyd)
Added tag(s) pending.

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

Bug#962878: marked as pending in omnidb

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #962878 in omnidb 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/postgresql/omnidb/-/commit/0d71cd0b95722287d4fb1444bcc10bf1c451aaad


B-D on fonts-glyphicons-halflings instead of fonts-glewlwyd. (Closes: #962878, 
#964691


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/962878

Bug#964691: marked as pending in omnidb

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #964691 in omnidb 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/postgresql/omnidb/-/commit/0d71cd0b95722287d4fb1444bcc10bf1c451aaad


B-D on fonts-glyphicons-halflings instead of fonts-glewlwyd. (Closes: #962878, 
#964691


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964691

Processed: Bug#964691 marked as pending in omnidb

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964691 [src:omnidb] omnidb: FTBFS: build-dependency not installable: 
fonts-glewlwyd
Added tag(s) pending.

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

Bug#965007: pitivi: ships a copy of gstreamer libraries

[Andreas Beckmann]

Package: pitivi
Version: 0.999-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libunwind8:amd64.
  Preparing to unpack .../1-libunwind8_1.2.1-9_amd64.deb ...
  Unpacking libunwind8:amd64 (1.2.1-9) ...
  Preparing to unpack .../2-libgstreamer1.0-0_1.17.2-1_amd64.deb ...
  Unpacking libgstreamer1.0-0:amd64 (1.17.2-1) over (1.16.2-2) ...
  Preparing to unpack .../3-libgstreamer-plugins-base1.0-0_1.17.2-1_amd64.deb 
...
  Unpacking libgstreamer-plugins-base1.0-0:amd64 (1.17.2-1) over (1.16.2-4) ...
  Preparing to unpack .../4-libgstreamer-gl1.0-0_1.17.2-1_amd64.deb ...
  Unpacking libgstreamer-gl1.0-0:amd64 (1.17.2-1) over (1.16.2-4) ...
  Preparing to unpack .../5-gstreamer1.0-plugins-bad_1.17.2-1_amd64.deb ...
  Unpacking gstreamer1.0-plugins-bad:amd64 (1.17.2-1) over (1.16.2-2.1+b1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-GE87Dh/5-gstreamer1.0-plugins-bad_1.17.2-1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgsttranscode.so', which is also in 
package pitivi 0.999-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Preparing to unpack .../6-libgstreamer-plugins-bad1.0-0_1.17.2-1_amd64.deb ...
  Unpacking libgstreamer-plugins-bad1.0-0:amd64 (1.17.2-1) over (1.16.2-2.1+b1) 
...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-GE87Dh/6-libgstreamer-plugins-bad1.0-0_1.17.2-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libgsttranscoder-1.0.so.0', 
which is also in package pitivi 0.999-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Selecting previously unselected package libltc11:amd64.
  Preparing to unpack .../7-libltc11_1.3.1-1_amd64.deb ...
  Unpacking libltc11:amd64 (1.3.1-1) ...
  Selecting previously unselected package libopenni2-0.
  Preparing to unpack .../8-libopenni2-0_2.2.0.33+dfsg-13_amd64.deb ...
  Unpacking libopenni2-0 (2.2.0.33+dfsg-13) ...
  Selecting previously unselected package gstreamer1.0-plugins-bad-apps.
  Preparing to unpack .../9-gstreamer1.0-plugins-bad-apps_1.17.2-1_amd64.deb ...
  Unpacking gstreamer1.0-plugins-bad-apps (1.17.2-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-GE87Dh/9-gstreamer1.0-plugins-bad-apps_1.17.2-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/gst-transcoder-1.0', which is also in package 
pitivi 0.999-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-GE87Dh/5-gstreamer1.0-plugins-bad_1.17.2-1_amd64.deb
   
/tmp/apt-dpkg-install-GE87Dh/6-libgstreamer-plugins-bad1.0-0_1.17.2-1_amd64.deb
   
/tmp/apt-dpkg-install-GE87Dh/9-gstreamer1.0-plugins-bad-apps_1.17.2-1_amd64.deb

Once this has been solved in pitivi, gstreamer in experimental needs 
corresponding Breaks+Replaces to take back the files it owns.

cheers,

Andreas


pitivi=0.999-2_gstreamer1.0-plugins-bad-apps=1.17.2-1.log.gz
Description: application/gzip

Bug#963546: fixed in meson 0.55.0-1

[Gianfranco Costamagna]

control: reopen -1
control: notfixed -1 0.55.0-1
control: notfixed -1 0.55.0~rc2-1

Hello, looks like there is still one tweak needed?

+meson (0.55.0-2) unstable; urgency=medium
+
+  * Don't require armhf tools on s390x (Closes: #963546)
+
+ -- Gianfranco Costamagna   Tue, 14 Jul 2020 
13:06:33 +0200
+
 meson (0.55.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru meson-0.55.0/debian/tests/control meson-0.55.0/debian/tests/control
--- meson-0.55.0/debian/tests/control   2020-07-12 16:29:07.0 +0200
+++ meson-0.55.0/debian/tests/control   2020-07-14 13:06:32.0 +0200
@@ -12,4 +12,4 @@
 Depends: meson, @builddeps@, valac, rustc, ldc [!s390x !ppc64el]
 
 Tests: crossbuild
-Depends: meson, g++, g++-arm-linux-gnueabihf
+Depends: meson, g++, g++-arm-linux-gnueabihf [!s390x]


this is the failure:
Reading package lists...
Building dependency tree...
Reading state information...
Package g++-arm-linux-gnueabihf is not available, but is referred to by another 
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'g++-arm-linux-gnueabihf' has no installation candidate
crossbuild   FAIL badpkg
blame: meson
badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
autopkgtest [09:26:49]:  summary
basicmeson   PASS
clangmeson   PASS
exhaustive   PASS
crossbuild   FAIL badpkg


thanks for fixing everything else!

(I'm still testing the patch right now, but I presume it should be good)

Gianfranco

Processed: Re: Bug#963546: fixed in meson 0.55.0-1

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #963546 {Done: Jussi Pakkanen } [src:meson] meson: 
autopkgtest failures
'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 meson/0.55.0-1 and meson/0.55.0~rc2-1.
> notfixed -1 0.55.0-1
Bug #963546 [src:meson] meson: autopkgtest failures
Ignoring request to alter fixed versions of bug #963546 to the same values 
previously set
> notfixed -1 0.55.0~rc2-1
Bug #963546 [src:meson] meson: autopkgtest failures
Ignoring request to alter fixed versions of bug #963546 to the same values 
previously set

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

Bug#965006: libtomcat10{,-embed}-java: install files in 9.x paths

[Andreas Beckmann]

Package: libtomcat10-java,libtomcat10-embed-java
Version: 10.0.0~M6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Preparing to unpack .../libtomcat10-embed-java_10.0.0~M6-1_all.deb ...
  Unpacking libtomcat10-embed-java (10.0.0~M6-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libtomcat10-embed-java_10.0.0~M6-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/maven-repo/org/apache/tomcat/embed/tomcat-embed-core/9.x/tomcat-embed-core-9.x.pom',
 which is also in package libtomcat9-embed-java 9.0.37-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libtomcat10-embed-java_10.0.0~M6-1_all.deb

  Preparing to unpack .../libtomcat10-java_10.0.0~M6-1_all.deb ...
  Unpacking libtomcat10-java (10.0.0~M6-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libtomcat10-java_10.0.0~M6-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/maven-repo/org/apache/tomcat/tomcat-annotations-api/9.x/tomcat-annotations-api-9.x.pom',
 which is also in package libtomcat9-java 9.0.37-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libtomcat10-java_10.0.0~M6-1_all.deb


cheers,

Andreas


libtomcat9-embed-java=9.0.37-1_libtomcat10-embed-java=10.0.0~M6-1.log.gz
Description: application/gzip

Bug#965005: libdolfin-dev-common: missing Breaks+Replaces: libdolfin-dev (<< 2019.2.0~git20200218.027d9cc-7)

[Andreas Beckmann]

Package: libdolfin-dev-common
Version: 2019.2.0~git20200218.027d9cc-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack 
.../libdolfin-dev-common_2019.2.0~git20200218.027d9cc-8_amd64.deb ...
  Unpacking libdolfin-dev-common (2019.2.0~git20200218.027d9cc-8) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libdolfin-dev-common_2019.2.0~git20200218.027d9cc-8_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/include/dolfin/adaptivity/AdaptiveLinearVariationalSolver.h', which is 
also in package libdolfin-dev 2019.2.0~git20200218.027d9cc-6+b2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/var/cache/apt/archives/libdolfin-dev-common_2019.2.0~git20200218.027d9cc-8_amd64.deb


cheers,

Andreas


libdolfin-dev=2019.2.0~git20200218.027d9cc-6+b2_libdolfin-dev-common=2019.2.0~git20200218.027d9cc-8.log.gz
Description: application/gzip

Bug#953258: closed by Debian FTP Masters (reply to Federico Ceratto ) (Bug#953258: fixed in python-hug 2.6.0-2)

[Andreas Beckmann]

Control: reopen -1

https://salsa.debian.org/debian/python-hug/-/commit/2bebbaec1fb1b12b2de8e199fb3d27b37f2ba5c3

'Breaks+Replaces' is not a valid syntax, dpkg wants these separate ;-)

Breaks: python3-hug (<< 2.6.0)
Replaces: python3-hug (<< 2.6.0)


Andreas

Processed: Re: Bug#953258 closed by Debian FTP Masters (reply to Federico Ceratto ) (Bug#953258: fixed in python-hug 2.6.0-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #953258 {Done: Federico Ceratto } [python3-hug-doc] 
python3-hug-doc: missing Breaks+Replaces: python3-hug (<< 2.4.1)
'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-hug/2.6.0-2.

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

Bug#964227: marked as done (datefudge: FTBFS with glibc 2.31 (conflicting gettimeofday prototype))

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 10:03:27 +
with message-id 
and subject line Bug#964227: fixed in datefudge 1.24
has caused the Debian Bug report #964227,
regarding datefudge: FTBFS with glibc 2.31 (conflicting gettimeofday prototype)
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.)


-- 
964227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: datefudge
Version: 1.23
Severity: important
Tags: patch upstream

datefudge fails to build from source with glibc 2.31

| gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wextra -D_REENTRANT -fpic -c -o datefudge.o 
datefudge.c
| sed -e 's,@VERSION@,1.23,g; s,@MULTIARCH_PATTERN@,/*-*,g; 
s,@LIBDIR@,/usr/lib,g;' \
| < datefudge.man > datefudge.1
| datefudge.c:81:5: error: conflicting types for ‘gettimeofday’
|81 | int gettimeofday(struct timeval *x, struct timezone *y) {
|   | ^~~~
| In file included from datefudge.c:21:
| /usr/include/x86_64-linux-gnu/sys/time.h:66:12: note: previous declaration of 
‘gettimeofday’ was here
|66 | extern int gettimeofday (struct timeval *__restrict __tv,
|   |^~~~
| make[1]: *** [Makefile:40: datefudge.o] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j4 "INSTALL=install --strip-program=true" 
returned exit code 2
| make: *** [debian/rules:16: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

The full build log is available there:
http://qa-logs.debian.net/2020/06/24/datefudge_1.23_unstable_glibc-exp.log

The support for timezones in gettimeofday has been removed in glibc
2.31. As a result the second argument of the gettimeofday prototype has
been changed from struct timezone * to void *. The same change needs to
be done in datefudge.

You will find attached a patch fixing that. It would be nice if it can
be fixed relatively soon so that we can start the transition.

Regards,
Aurelien
diff -Nru datefudge-1.23/datefudge.c datefudge-1.23/datefudge.c
--- datefudge-1.23/datefudge.c  2019-08-02 18:09:51.0 +
+++ datefudge-1.23/datefudge.c  2020-07-03 20:49:48.0 +
@@ -66,8 +66,8 @@
 
 #endif
 
-int __gettimeofday(struct timeval *x, struct timezone *y) {
-static int (*libc_gettimeofday)(struct timeval *, struct timezone *) = 
NULL;
+int __gettimeofday(struct timeval *x, void *y) {
+static int (*libc_gettimeofday)(struct timeval *, void *) = NULL;
 int res;
 
 if(!libc_gettimeofday)
@@ -78,7 +78,7 @@
 return 0;
 }
 
-int gettimeofday(struct timeval *x, struct timezone *y) {
+int gettimeofday(struct timeval *x, void *y) {
 return __gettimeofday(x,y);
 }
 
--- End Message ---
--- Begin Message ---
Source: datefudge
Source-Version: 1.24
Done: Robert Luberda 

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

Debian distribution maintenance software
pp.
Robert Luberda  (supplier of updated datefudge 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, 14 Jul 2020 11:11:48 +0200
Source: datefudge
Architecture: source
Version: 1.24
Distribution: unstable
Urgency: medium
Maintainer: Robert Luberda 
Changed-By: Robert Luberda 
Closes: 945599 964227
Changes:
 datefudge (1.24) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Update standards version to 4.4.1, no changes needed.
   * Set debhelper-compat version in Build-Depends.
   * Fix day-of-week for changelog entries 1.12, 1.11, 1.10, 1.9, 1.8,
 1.7, 1.6, 1.5, 1.4, 1.3, 1.2, 1.1, 1.0.
 .
   [ Robert Luberda ]
   * Fix FTBFS on hurd-i386: Necessary functions disabled (closes: #945599).
 Thanks to Paul Sonnenschein for the patch.
   * Fix FTBFS with glibc 2.31 (conflicting gettimeofday prototype) (closes:
 #964227). Thanks to Aurelien Jarno for the patch.
   * Bump debhelper's compact level to 13.
   * Standards-Version: 4.5.0.
Checksums-Sha1:
 

Bug#965000: marked as done (lintian fails autopkg tests on all archs except for amd64)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 02:33:42 -0700
with message-id 

and subject line Re: Bug#965000: lintian fails autopkg tests on all archs 
except for amd64
has caused the Debian Bug report #965000,
regarding lintian fails autopkg tests on all archs except for amd64
to be marked as done.

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

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


-- 
965000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lintian
Version: 2.83.0
Severity: serious
Tags: sid bullseye

lintian fails autopkg tests on all archs except for amd64, the architecture
seems to be hard-coded.

# Literal output does not match
#
# --- ../../autopkgtest_tmp/testsuite/eval/lintian-features/html-output/literal
# +++
../../autopkgtest_tmp/testsuite/eval/lintian-features/html-output/literal.actual.parsed
# -  html-output_1.0+dsfg-1.1_amd64.buildinfo
# +  html-output_1.0+dsfg-1.1_arm64.buildinfo
# -  html-output_1.0+dsfg-1.1_amd64.changes
# +  html-output_1.0+dsfg-1.1_arm64.changes
#
#   Failed test 'Lintian passes for html-output'
#   at
/tmp/autopkgtest-lxc.72_dgd2a/downtmp/build.Z17/src/lib/Test/Lintian/Run.pm line
302.
# Looks like you failed 1 test of 1.
../../autopkgtest_tmp/testsuite/eval/lintian-features/html-output/generic.t

Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests
--- End Message ---
--- Begin Message ---
Hi Matthias,

On Tue, Jul 14, 2020 at 12:24 AM Matthias Klose  wrote:
>
> lintian fails autopkg tests on all archs except for amd64, the architecture
> seems to be hard-coded.
>
> # --- 
> ../../autopkgtest_tmp/testsuite/eval/lintian-features/html-output/literal

The bug you report was already addressed in our repo and is pending:


https://salsa.debian.org/lintian/lintian/-/commit/6dfec99bf7a41b0e373657d07d43655110ac172d

Also, another test fails on architectures whose ld does not by default
enable SHF_MERGE. It is addressed here:


https://salsa.debian.org/lintian/lintian/-/commit/a656ab8621be29b7a9deb28cd955ca077c322533

Thanks for bringing this issue to our attention!

Closing this bug.

Kind regards
Felix Lechner--- End Message ---

Bug#964950: marked as done (nginx: CVE-2020-11724)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 08:36:02 +
with message-id 
and subject line Bug#964950: fixed in nginx 1.18.0-5
has caused the Debian Bug report #964950,
regarding nginx: CVE-2020-11724
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.)


-- 
964950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nginx
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for ngx_lua.

CVE-2020-11724[0]:
| ngx_http_lua_subrequest.c allows HTTP request smuggling, as
| demonstrated by the ngx.location.capture API.


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-2020-11724
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11724

Cheers!
Sylvain Beucler
Debian LTS Team
--- End Message ---
--- Begin Message ---
Source: nginx
Source-Version: 1.18.0-5
Done: =?utf-8?b?T25kxZllaiBOb3bDvQ==?= 

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated nginx 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, 14 Jul 2020 10:08:15 +0200
Source: nginx
Architecture: source
Version: 1.18.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Nginx Maintainers 

Changed-By: Ondřej Nový 
Closes: 964950
Changes:
 nginx (1.18.0-5) unstable; urgency=medium
 .
   * Prevented request smuggling in LUA
 CVE-2020-11724
 Closes: #964950
Checksums-Sha1:
 6839c8e7a7e04731bf44f0afa02cb01b898ba101 4750 nginx_1.18.0-5.dsc
 a24f0355029ae09b67861677b9ceca223f4ff00e 1038760 nginx_1.18.0-5.debian.tar.xz
 4476fd788723f13faa0eb48df603bb80344b7945 25156 nginx_1.18.0-5_amd64.buildinfo
Checksums-Sha256:
 3aacd8d456e58aedc2730440e01cd7e4fa6135825b4ad9cfaeba3a46a806a5f7 4750 
nginx_1.18.0-5.dsc
 8d50608bcf8295d901eeda021af6684d43ac13ff2fb51c77f8a2d64f464c9b29 1038760 
nginx_1.18.0-5.debian.tar.xz
 1e1e324acb5d2f31ea39318659413c820edffd58adf398ba80f9ab1eb524076c 25156 
nginx_1.18.0-5_amd64.buildinfo
Files:
 a9b134d5bdd14b11240d93accbec37ec 4750 httpd optional nginx_1.18.0-5.dsc
 29c0cb790d95fd0b641cd2217152385f 1038760 httpd optional 
nginx_1.18.0-5.debian.tar.xz
 9e61b8b1f39fd8c1db71d483d7380ed5 25156 httpd optional 
nginx_1.18.0-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAl8NaY4ACgkQNXMSVZ0e
BkvRQA/9HJDawjgGYAZ1q/HtunVSloxoeXGwwJaSAz3lv88uNzPctqQw9KEGixBL
LtIEFl/S0rPPp0X4/jdqa9akKQfjvx6GGKqFPrSidjs+oHzDflyRR1SdeLm024cE
zrzK+7Bw7NlmC2ZzZMRxMmCvBWdMZvHpeVGGRC4XJozvEsaXkXdgj/iAM5+fUmX5
mBkeclfHXhrs3HGH3nRFGHO8oGdz12s1q9pCKwgdpAmgz2RmmF7WfGYNEe5P+8iC
1sKKMcuD0gHvRSjh83EIkNxQci/qQL3FVykgose5yQhH0ibsZIT0RRcg57dahrDk
wtkRHrL9vDH6AtfTRhnCWt5oO9HxdKViyaJeC5GvY2Obinf2OP3A6tEUeiYxje1z
F2CGtje5n6l7SfhqY3Tfm72tf4am6RX14yZF8mgWoche/burtf2M0/SKpz76oQai
eVMJf0fIo5CBdrR2uicNmbqTyfBypM1mb40RRa3CWh9z+28xZ5njBwGnQqPISIt0
CV2EN0pVdDqs5Cg/yLxGTmgVC8q9gNrbQzQl/jpVstPfJZq1eAh3uDHsPUKCWtWE
yY55qyPZbvQ+aHoXIWgEiBm+NBTggzNS49ckh4hRLOC28KBZujeSlUFYkcumtjBV
TTnmOxagizyvvgJnR57EU+UI9J3WQsBUGrwHWd13wYYwUzqYfVg=
=WEwf
-END PGP SIGNATURE End Message ---

Bug#964950: marked as done (nginx: CVE-2020-11724)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jul 2020 08:14:56 +
with message-id <5f0d698076552_57da2aaddd5425bc89...@godard.mail>
and subject line Bug#964950 fixed in nginx
has caused the Debian Bug report #964950,
regarding nginx: CVE-2020-11724
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.)


-- 
964950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nginx
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for ngx_lua.

CVE-2020-11724[0]:
| ngx_http_lua_subrequest.c allows HTTP request smuggling, as
| demonstrated by the ngx.location.capture API.


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-2020-11724
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11724

Cheers!
Sylvain Beucler
Debian LTS Team
--- End Message ---
--- Begin Message ---
Hello,

Bug #964950 in nginx reported by you has been fixed in the Git repository.
You can see the commit message below and you can check the diff of the fix at:

https://salsa.debian.org/nginx-team/nginx/-/commit/aa1f93ee247cd7d21473f35bcba4a95cdfb388ad


Prevented request smuggling in LUA CVE-2020-11724 Closes: #964950


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964950--- End Message ---

Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does

[Dmitry Smirnov]

On Tuesday, 14 July 2020 3:10:39 PM AEST Ross Vandegrift wrote:
> Hi Dmitry - systemctl is still breaking builds in experimental, any
> updates?

Not yet, unfortunately. Sorry for inconvenience. I'm going to seek CTTE 
advise on #959174...

-- 
All the best,
 Dmitry Smirnov.

---

Someone once said that a fool can put on his coat better than a wise man
can put it on for him. The implications of that undermine most of the
agenda of the political left.
-- Thomas Sowell


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

Bug#925691: gauche-c-wrapper: ftbfs with GCC-9

[Jens Thiele]

Hi,

Fabian Brosda fixed gauche-c-wrapper for Arch Linux:
https://aur.archlinux.org/packages/gauche-c-wrapper/

The new patches are 11 to 14:
https://aur.archlinux.org/cgit/aur.git/tree/11_fix_jp_encoding.patch?h=gauche-c-wrapper
https://aur.archlinux.org/cgit/aur.git/tree/12_float128.patch?h=gauche-c-wrapper
https://aur.archlinux.org/cgit/aur.git/tree/13_local_typedef.patch?h=gauche-c-wrapper
https://aur.archlinux.org/cgit/aur.git/tree/14_extend_parser.patch?h=gauche-c-wrapper

Greetings,
karme

Bug#965000: lintian fails autopkg tests on all archs except for amd64

[Matthias Klose]

Package: src:lintian
Version: 2.83.0
Severity: serious
Tags: sid bullseye

lintian fails autopkg tests on all archs except for amd64, the architecture
seems to be hard-coded.

# Literal output does not match
#
# --- ../../autopkgtest_tmp/testsuite/eval/lintian-features/html-output/literal
# +++
../../autopkgtest_tmp/testsuite/eval/lintian-features/html-output/literal.actual.parsed
# -  html-output_1.0+dsfg-1.1_amd64.buildinfo
# +  html-output_1.0+dsfg-1.1_arm64.buildinfo
# -  html-output_1.0+dsfg-1.1_amd64.changes
# +  html-output_1.0+dsfg-1.1_arm64.changes
#
#   Failed test 'Lintian passes for html-output'
#   at
/tmp/autopkgtest-lxc.72_dgd2a/downtmp/build.Z17/src/lib/Test/Lintian/Run.pm line
302.
# Looks like you failed 1 test of 1.
../../autopkgtest_tmp/testsuite/eval/lintian-features/html-output/generic.t

Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests

Bug#964682: icu: FTBFS: dh_auto_test: error: cd source && make -j4 check VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Hi,

On 11/07/20 at 16:08 +0200, László Böszörményi (GCS) wrote:
> I can workaround this by setting no parallel to the tests, which in
> turn will run slower on multicore processors but will pass. Then Manoj
> can revert the mentioned bad fix of make-dfsg while upstream will work
> on a better one. Another way is to report this misbehaviour to GNU to
> fix.
> Which way to go first?

My 2 cents: I did not notice any large scale breakage in many packages
due to this change. So it's not unlikely that it won't be fixed prompty
in make, and that it might be better to work around this in your
package.

Lucas