Bug#879662: apt: debian-installer FTBFS: E: Method copy has died unexpectedly!

[Cyril Brulebois]

Package: apt
Version: 1.4.8
Severity: serious
Tags: d-i
Justification: FTBFS

[ Please keep both debian-boot@ and me in copy. ]

It seems the “most secure file downloading on the planet” can no longer
copy files around:
| get-packages udeb  
| make[5]: 'sources.list.udeb' is up to date.
| Ign:1 copy:/home/kibi/debian-installer/installer/build localudebs/ InRelease
| Ign:2 copy:/home/kibi/debian-installer/installer/build localudebs/ Release
| Ign:3 copy:/home/kibi/debian-installer/installer/build localudebs/ Packages
| Ign:4 copy:/home/kibi/debian-installer/installer/build localudebs/ 
Translation-en
| Ign:5 copy:/home/kibi/debian-installer/installer/build localudebs/ Contents 
(deb)
| Ign:6 copy:/home/kibi/debian-installer/installer/build localudebs/ Contents 
(deb)
| Ign:7 copy:/home/kibi/debian-installer/installer/build localudebs/ Contents 
(udeb)
| Get:8 http://localhost/debian unstable InRelease [235 kB]
| Ign:9 copy:/home/kibi/debian-installer/installer/build localudebs/ Contents 
(udeb)
| Ign:3 copy:/home/kibi/debian-installer/installer/build localudebs/ Packages
| Ign:4 copy:/home/kibi/debian-installer/installer/build localudebs/ 
Translation-en
| Ign:5 copy:/home/kibi/debian-installer/installer/build localudebs/ Contents 
(deb)
| Ign:6 copy:/home/kibi/debian-installer/installer/build localudebs/ Contents 
(deb)
| Ign:7 copy:/home/kibi/debian-installer/installer/build localudebs/ Contents 
(udeb)
| Ign:9 copy:/home/kibi/debian-installer/installer/build localudebs/ Contents 
(udeb)
| Ign:3 copy:/home/kibi/debian-installer/installer/build localudebs/ Packages
| Ign:4 copy:/home/kibi/debian-installer/installer/build localudebs/ 
Translation-en
| Ign:5 copy:/home/kibi/debian-installer/installer/build localudebs/ Contents 
(deb)
| Ign:6 copy:/home/kibi/debian-installer/installer/build localudebs/ Contents 
(deb)
| Ign:7 copy:/home/kibi/debian-installer/installer/build localudebs/ Contents 
(udeb)
| Ign:9 copy:/home/kibi/debian-installer/installer/build localudebs/ Contents 
(udeb)
| Reading package lists...
| E: Method copy has died unexpectedly!
| E: Sub-process copy received signal 31.

Error reporting is a bit underwhelming. :(

This happens with this sources.list file:
| (sid-amd64-devel)kibi@wodi:~/debian-installer/installer/build$ cat 
sources.list.udeb 
| # This file is automatically generated, edit sources.list.udeb.local instead.
| deb [trusted=yes] copy:/home/kibi/debian-installer/installer/build/ 
localudebs/
| deb http://localhost/debian unstable main/debian-installer

This can be reproduced on all archs by triggering a daily build in the
debian-installer directory, in a sid chroot:
| cd build && ./daily-build build-only


KiBi.

Bug#868969: marked as done (adblock-plus: FTBFS: UnicodeDecodeError: 'utf8' codec can't decode byte 0xd1 in position 366: invalid continuation byte)

[Debian Bug Tracking System]

Your message dated Tue, 24 Oct 2017 01:48:42 +
with message-id 
and subject line Bug#868969: fixed in adblock-plus 2.9.1+dfsg-1
has caused the Debian Bug report #868969,
regarding adblock-plus: FTBFS: UnicodeDecodeError: 'utf8' codec can't decode 
byte 0xd1 in position 366: invalid continuation byte
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.)


-- 
868969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adblock-plus
Version: 2.7.3+dfsg-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/adblock-plus-2.7.3+dfsg'
> TZ=UTC python build.py build --release
> Warning: Mapped file adblockplusui/skin/fonts/CreteRound-Italic.otf doesn't 
> exist
> Warning: Mapped file adblockplusui/skin/fonts/CreteRound-Regular.otf doesn't 
> exist
> Traceback (most recent call last):
>   File "build.py", line 11, in 
> buildtools.build.processArgs(BASE_DIR, sys.argv)
>   File "/<>/adblock-plus-2.7.3+dfsg/buildtools/build.py", line 616, 
> in processArgs
> commands[command](baseDir, scriptName, opts, args, type)
>   File "/<>/adblock-plus-2.7.3+dfsg/buildtools/build.py", line 57, 
> in __call__
> return self._handler(baseDir, scriptName, opts, args, type)
>   File "/<>/adblock-plus-2.7.3+dfsg/buildtools/build.py", line 203, 
> in runBuild
> multicompartment=multicompartment)
>   File "/<>/adblock-plus-2.7.3+dfsg/buildtools/packagerGecko.py", 
> line 378, in createBuild
> fixupLocales(params, files)
>   File "/<>/adblock-plus-2.7.3+dfsg/buildtools/packagerGecko.py", 
> line 220, in fixupLocales
> data = localeTools.parseString(files[path].decode('utf-8'), path)
>   File "/<>/adblock-plus-2.7.3+dfsg/buildtools/localeTools.py", 
> line 187, in parseString
> for name, comment, value in it:
>   File "/<>/adblock-plus-2.7.3+dfsg/buildtools/localeTools.py", 
> line 150, in parseDTDString
> parser.Parse('', True)
>   File "/<>/adblock-plus-2.7.3+dfsg/buildtools/localeTools.py", 
> line 137, in ExternalEntityRefHandler
> subparser.Parse(data.encode('utf-8'), True)
> UnicodeDecodeError: 'utf8' codec can't decode byte 0xd1 in position 366: 
> invalid continuation byte
> debian/rules:7: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/adblock-plus_2.7.3+dfsg-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: adblock-plus
Source-Version: 2.9.1+dfsg-1

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated adblock-plus 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: Mon, 23 Oct 2017 13:15:12 -1000
Source: adblock-plus
Binary: xul-ext-adblock-plus
Architecture: source
Version: 2.9.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: David Prévot 
Description:
 xul-ext-adblock-plus - advertisement blocking extension for web browsers
Closes: 827965 868969
Changes:
 adblock-plus (2.9.1+dfsg-1) unstable; urgency=medium
 .
   [ Wladimir Palant ]
   * Releasing Adblock Plus 2.9.1
 .
   [ David Prévot ]
   * Use upstream source archive with dependencies included
   * Remove 

Processed: limit source to adblock-plus, tagging 827965, tagging 868969

[Debian Bug Tracking System]

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

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

> tags 827965 + pending
Bug #827965 [adblock-plus] Please remove me from Uploaders
Added tag(s) pending.
> tags 868969 + pending
Bug #868969 [src:adblock-plus] adblock-plus: FTBFS: UnicodeDecodeError: 'utf8' 
codec can't decode byte 0xd1 in position 366: invalid continuation byte
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#824229:

[Otto Kekäläinen]

I've reported this upstream at https://github.com/schani/metapixel/issues/10

Bug#876702: marked as done (haskell-language-python FTBFS: Couldn't match type `t146' with `[Either a30 [Statement SrcSpan]]')

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 22:04:14 +
with message-id 
and subject line Bug#876605: fixed in happy 1.19.8-1
has caused the Debian Bug report #876605,
regarding haskell-language-python FTBFS: Couldn't match type `t146' with 
`[Either a30 [Statement SrcSpan]]'
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.)


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

Some recent change in unstable makes haskell-language-python FTBFS:

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

...
[17 of 23] Compiling Language.Python.Version2.Parser.Parser ( 
dist-ghc/build/Language/Python/Version2/Parser/Parser.hs, 
dist-ghc/build/Language/Python/Version2/Parser/Parser.o )

dist-ghc/build/Language/Python/Version2/Parser/Parser.hs:2171:17: error:
* Couldn't match type `t146'
 with `[Either a30 [Statement SrcSpan]]'
  `t146' is a rigid type variable bound by
the type signature for:
  happyReduce_7 :: forall t127 t143 t144 t145 t146 t147 t148 t149 t150 
t151 t152 t153 t154 t155 t156 t157 t158 t159 t160 t161 t162 t163 t164 t165 t166 
t167 t168 t169 t170 t171 t172 t173 t174 t175 t176 t177 t178 t179 t180 t181 t182 
t183 t184 t185 t186 t187 t188 t189 t190 t191 t192 t193 t194 t195 t196 t197 t198 
t199 t200 t201 t202 t203 t204 t205 t206 t207 t208 t209 t210 t211 t212 t213 t214 
t215 t216 t217 t218 t219 t220 t221 t222 t223 t224 t225 t226 t227 t228 t229 t230 
t231 t232 t233 t234 t235 t236 t237 t238 t239 t240 t241 t242 t243 t244 t245 t246 
t247 t248 t249 t250 t251 t252 t253 t254 t255 t256 t257 t258 t259 t260 t261 t262 
t263 t264 t265 t266 t267 t268 t269 t270 t271 t272.
   Happy_GHC_Exts.Int#
   -> Token
   -> Happy_GHC_Exts.Int#
   -> Happy_IntList
   -> HappyStk
(HappyAbsSyn
   t127
   t143
   t144
...
--- End Message ---
--- Begin Message ---
Source: happy
Source-Version: 1.19.8-1

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

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

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated happy 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, 24 Oct 2017 00:46:34 +0300
Source: happy
Binary: happy
Architecture: source
Version: 1.19.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Description:
 happy  - Parser generator for Haskell
Closes: 876605
Changes:
 happy (1.19.8-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #876605)
Checksums-Sha1:
 da0cf3541bcb669bfa35d48c88c20415c9755232 2152 happy_1.19.8-1.dsc
 53a7c4e3d2e0ebacc9bb205f6fc041fc918bcbe3 179814 happy_1.19.8.orig.tar.gz
 a5ca1d438a44cd6fa6a0b488234c7db191fbf02e 8748 happy_1.19.8-1.debian.tar.xz
 c42c26918bf323cebf476864d206a5ffe90c6635 9560 happy_1.19.8-1_amd64.buildinfo
Checksums-Sha256:
 d5308276746cef39c66ccce1926a52afd81ae369701095644da5bd72c9e0f9e5 2152 
happy_1.19.8-1.dsc
 4df739965d559e48a9b0044fa6140241c07e8f3c794c6c0a6323024fd7f0d3a0 179814 
happy_1.19.8.orig.tar.gz
 cacc9fec341b920364becabe9a4891d465c7a292cab870604685b41efbcac74a 8748 
happy_1.19.8-1.debian.tar.xz
 db1e53c89f0c0a9f743e571c88011cf19964c759d4ed07993e8e861bb126ff32 9560 
happy_1.19.8-1_amd64.buildinfo
Files:
 eb6c12c470d7518043483c06307429b5 2152 haskell extra happy_1.19.8-1.dsc
 1a3d15f90bb20b3b00ebf55e55728dce 179814 haskell extra happy_1.19.8.orig.tar.gz
 a1ce1ed25d1224463a22e39c0e00600a 8748 haskell 

Bug#876605: marked as done (Monadic grammar, threaded lexer, -a enabled, but no type signature, fails to compile)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 22:04:14 +
with message-id 
and subject line Bug#876605: fixed in happy 1.19.8-1
has caused the Debian Bug report #876605,
regarding Monadic grammar, threaded lexer, -a enabled, but no type signature, 
fails to compile
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.)


-- 
876605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: agda
Version: 2.5.2-2
Severity: serious

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

...
dist-ghc/build/Agda/Syntax/Parser/Parser.hs:2441:19: error:
• Couldn't match type ‘t13’ with ‘()’
  ‘t13’ is a rigid type variable bound by
the type signature for:
  happyReduce_114 :: forall t13 t14 t15 t38 t41 t44 t45 t46 t54 t55 t84.
 Happy_GHC_Exts.Int#
 -> Token
 -> Happy_GHC_Exts.Int#
 -> Happy_IntList
 -> HappyStk
  (HappyAbsSyn t13 t14 t15 t38 t41 t44 t45 t46 
t54 t55 t84)
 -> Parser (HappyAbsSyn t13 t14 t15 t38 t41 t44 t45 
t46 t54 t55 t84)
at dist-ghc/build/Agda/Syntax/Parser/Parser.hs:2440:20
  Expected type: Happy_GHC_Exts.Int#
 -> Token
 -> Happy_GHC_Exts.Int#
 -> Happy_IntList
 -> HappyStk
  (HappyAbsSyn t13 t14 t15 t38 t41 t44 t45 t46 t54 t55 
t84)
 -> Parser (HappyAbsSyn t13 t14 t15 t38 t41 t44 t45 t46 t54 
t55 t84)
Actual type: Happy_GHC_Exts.Int#
 -> Token
 -> Happy_GHC_Exts.Int#
 -> Happy_IntList
 -> HappyStk
  (HappyAbsSyn () t14 t15 t38 t41 t44 t45 t46 t54 t55 
t84)
 -> Parser (HappyAbsSyn () t14 t15 t38 t41 t44 t45 t46 t54 
t55 t84)
...
--- End Message ---
--- Begin Message ---
Source: happy
Source-Version: 1.19.8-1

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

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

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated happy 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, 24 Oct 2017 00:46:34 +0300
Source: happy
Binary: happy
Architecture: source
Version: 1.19.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Description:
 happy  - Parser generator for Haskell
Closes: 876605
Changes:
 happy (1.19.8-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #876605)
Checksums-Sha1:
 da0cf3541bcb669bfa35d48c88c20415c9755232 2152 happy_1.19.8-1.dsc
 53a7c4e3d2e0ebacc9bb205f6fc041fc918bcbe3 179814 happy_1.19.8.orig.tar.gz
 a5ca1d438a44cd6fa6a0b488234c7db191fbf02e 8748 happy_1.19.8-1.debian.tar.xz
 c42c26918bf323cebf476864d206a5ffe90c6635 9560 happy_1.19.8-1_amd64.buildinfo
Checksums-Sha256:
 d5308276746cef39c66ccce1926a52afd81ae369701095644da5bd72c9e0f9e5 2152 
happy_1.19.8-1.dsc
 4df739965d559e48a9b0044fa6140241c07e8f3c794c6c0a6323024fd7f0d3a0 179814 
happy_1.19.8.orig.tar.gz
 cacc9fec341b920364becabe9a4891d465c7a292cab870604685b41efbcac74a 8748 
happy_1.19.8-1.debian.tar.xz
 db1e53c89f0c0a9f743e571c88011cf19964c759d4ed07993e8e861bb126ff32 9560 
happy_1.19.8-1_amd64.buildinfo
Files:
 eb6c12c470d7518043483c06307429b5 2152 haskell extra happy_1.19.8-1.dsc
 1a3d15f90bb20b3b00ebf55e55728dce 179814 haskell extra happy_1.19.8.orig.tar.gz
 a1ce1ed25d1224463a22e39c0e00600a 8748 haskell extra 
happy_1.19.8-1.debian.tar.xz
 aaa5d63d7c00cad47bd8fa752935c3aa 9560 haskell extra 
happy_1.19.8-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAlnuZdYUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDwn1RAAnwxnq/XFjIxEm2j7FHWhmn1RY8L/

Bug#876635: marked as done (haskell-cryptol FTBFS: Couldn't match type `t69' with `Pattern PName')

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 22:04:14 +
with message-id 
and subject line Bug#876605: fixed in happy 1.19.8-1
has caused the Debian Bug report #876605,
regarding haskell-cryptol FTBFS: Couldn't match type `t69' with `Pattern PName'
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.)


-- 
876605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-cryptol
Version: 2.4.0-2
Severity: serious
Tags: buster sid

https://buildd.debian.org/status/package.php?p=haskell-cryptol=sid

...
dist-ghc/build/Cryptol/Parser.hs:1329:18: error:
* Couldn't match type `t69' with `Pattern PName'
  `t69' is a rigid type variable bound by
the type signature for:
  happyReduce_60 :: forall t69.
Happy_GHC_Exts.Int#
-> Located Token
-> Happy_GHC_Exts.Int#
-> Happy_IntList
-> HappyStk (HappyAbsSyn t69)
-> ParseM (HappyAbsSyn t69)
at dist-ghc/build/Cryptol/Parser.hs:1328:19
  Expected type: Happy_GHC_Exts.Int#
 -> Located Token
 -> Happy_GHC_Exts.Int#
 -> Happy_IntList
 -> HappyStk (HappyAbsSyn t69)
 -> ParseM (HappyAbsSyn t69)
Actual type: Happy_GHC_Exts.Int#
 -> Located Token
 -> Happy_GHC_Exts.Int#
 -> Happy_IntList
 -> HappyStk (HappyAbsSyn (Pattern PName))
 -> ParseM (HappyAbsSyn (Pattern PName))
--- End Message ---
--- Begin Message ---
Source: happy
Source-Version: 1.19.8-1

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

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

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated happy 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, 24 Oct 2017 00:46:34 +0300
Source: happy
Binary: happy
Architecture: source
Version: 1.19.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Description:
 happy  - Parser generator for Haskell
Closes: 876605
Changes:
 happy (1.19.8-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #876605)
Checksums-Sha1:
 da0cf3541bcb669bfa35d48c88c20415c9755232 2152 happy_1.19.8-1.dsc
 53a7c4e3d2e0ebacc9bb205f6fc041fc918bcbe3 179814 happy_1.19.8.orig.tar.gz
 a5ca1d438a44cd6fa6a0b488234c7db191fbf02e 8748 happy_1.19.8-1.debian.tar.xz
 c42c26918bf323cebf476864d206a5ffe90c6635 9560 happy_1.19.8-1_amd64.buildinfo
Checksums-Sha256:
 d5308276746cef39c66ccce1926a52afd81ae369701095644da5bd72c9e0f9e5 2152 
happy_1.19.8-1.dsc
 4df739965d559e48a9b0044fa6140241c07e8f3c794c6c0a6323024fd7f0d3a0 179814 
happy_1.19.8.orig.tar.gz
 cacc9fec341b920364becabe9a4891d465c7a292cab870604685b41efbcac74a 8748 
happy_1.19.8-1.debian.tar.xz
 db1e53c89f0c0a9f743e571c88011cf19964c759d4ed07993e8e861bb126ff32 9560 
happy_1.19.8-1_amd64.buildinfo
Files:
 eb6c12c470d7518043483c06307429b5 2152 haskell extra happy_1.19.8-1.dsc
 1a3d15f90bb20b3b00ebf55e55728dce 179814 haskell extra happy_1.19.8.orig.tar.gz
 a1ce1ed25d1224463a22e39c0e00600a 8748 haskell extra 
happy_1.19.8-1.debian.tar.xz
 aaa5d63d7c00cad47bd8fa752935c3aa 9560 haskell extra 
happy_1.19.8-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAlnuZdYUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDwn1RAAnwxnq/XFjIxEm2j7FHWhmn1RY8L/
wh/+So8iUBYKnSLKgEPdtnkVqPWcLD5IhhDYvekZDc1zqHdaEumqQYVbbNefVi37
mLJs0iHNVBV90Hl8NYK0j1Bn5dSW+HDnEGAtDvCCJQkvzoQcPN8zwPZmBRc9SQm0
U97Gg+8kC2VVmgWvvq5USvKkrILU7cTWD1PgxWjw0EBvGNOi30yPeOZ61+eebfUs
D1eoOSYKCcB3XnacBo3f8oYPc+WlLdc/vvnaQfJYpEHG7RVXoM1qtEamAkrAD12G
qs9MUtiCbIBjxfUslcAgXH97VfM9UAkN01INZz/Xfv2wJADVaLh9tzrmC5K68ioj

Processed: reassign 876635 to happy, reassign 876702 to happy, forcibly merging 876605 876635 876702

[Debian Bug Tracking System]

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

> reassign 876635 happy
Bug #876635 [src:haskell-cryptol] haskell-cryptol FTBFS: Couldn't match type 
`t69' with `Pattern PName'
Bug reassigned from package 'src:haskell-cryptol' to 'happy'.
No longer marked as found in versions haskell-cryptol/2.4.0-2.
Ignoring request to alter fixed versions of bug #876635 to the same values 
previously set
> reassign 876702 happy
Bug #876702 [src:haskell-language-python] haskell-language-python FTBFS: 
Couldn't match type `t146' with `[Either a30 [Statement SrcSpan]]'
Bug reassigned from package 'src:haskell-language-python' to 'happy'.
No longer marked as found in versions haskell-language-python/0.5.4-4.
Ignoring request to alter fixed versions of bug #876702 to the same values 
previously set
> forcemerge 876605 876635 876702
Bug #876605 [happy] Monadic grammar, threaded lexer, -a enabled, but no type 
signature, fails to compile
Bug #876702 [happy] haskell-language-python FTBFS: Couldn't match type `t146' 
with `[Either a30 [Statement SrcSpan]]'
Set Bug forwarded-to-address to 'https://github.com/simonmar/happy/issues/94'.
Added indication that 876702 affects 
haskell-language-python,haskell-cryptol,agda
Marked as found in versions happy/1.19.6-1.
Added tag(s) fixed-upstream.
Bug #876605 [happy] Monadic grammar, threaded lexer, -a enabled, but no type 
signature, fails to compile
Added tag(s) buster and sid.
Bug #876635 [happy] haskell-cryptol FTBFS: Couldn't match type `t69' with 
`Pattern PName'
Set Bug forwarded-to-address to 'https://github.com/simonmar/happy/issues/94'.
Added indication that 876635 affects 
haskell-language-python,haskell-cryptol,agda
Marked as found in versions happy/1.19.6-1.
Added tag(s) fixed-upstream.
Merged 876605 876635 876702
> thanks
Stopping processing here.

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

Processed (with 1 error): reassign 876605 to happy, tagging 876605 ..., affects 876605, forcibly merging 876605 876635 876702

[Debian Bug Tracking System]

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

> reassign 876605 happy 1.19.6-1
Bug #876605 [src:agda] agda FTBFS: Couldn't match type ‘t13’ with ‘()’
Bug reassigned from package 'src:agda' to 'happy'.
No longer marked as found in versions agda/2.5.2-2.
Ignoring request to alter fixed versions of bug #876605 to the same values 
previously set
Bug #876605 [happy] agda FTBFS: Couldn't match type ‘t13’ with ‘()’
Marked as found in versions happy/1.19.6-1.
> tags 876605 + fixed-upstream
Bug #876605 [happy] agda FTBFS: Couldn't match type ‘t13’ with ‘()’
Added tag(s) fixed-upstream.
> forwarded 876605 https://github.com/simonmar/happy/issues/94
Bug #876605 [happy] agda FTBFS: Couldn't match type ‘t13’ with ‘()’
Set Bug forwarded-to-address to 'https://github.com/simonmar/happy/issues/94'.
> retitle 876605 Monadic grammar, threaded lexer, -a enabled, but no type 
> signature, fails to compile
Bug #876605 [happy] agda FTBFS: Couldn't match type ‘t13’ with ‘()’
Changed Bug title to 'Monadic grammar, threaded lexer, -a enabled, but no type 
signature, fails to compile' from 'agda FTBFS: Couldn't match type ‘t13’ with 
‘()’'.
> affects 876605 haskell-language-python agda haskell-cryptol
Bug #876605 [happy] Monadic grammar, threaded lexer, -a enabled, but no type 
signature, fails to compile
Added indication that 876605 affects haskell-language-python, agda, and 
haskell-cryptol
> forcemerge 876605 876635 876702
Bug #876605 [happy] Monadic grammar, threaded lexer, -a enabled, but no type 
signature, fails to compile
Unable to merge bugs because:
package of #876702 is 'src:haskell-language-python' not 'happy'
package of #876635 is 'src:haskell-cryptol' not 'happy'
Failed to forcibly merge 876605: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#879643: marked as done (debhelper: dh_usrlocal tries to chown to root:group which fails because group is not valid)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 21:34:02 +
with message-id 
and subject line Bug#879643: fixed in debhelper 10.10.3
has caused the Debian Bug report #879643,
regarding debhelper: dh_usrlocal tries to chown to root:group which fails 
because group is not valid
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

dh_usrlocal adds the following to my maintainerscript for cacti:
# Automatically added by dh_usrlocal/10.10.2
if [ "$1" = configure ]; then
(
while read line; do
set -- $line
dir="$1"; mode="$2"; user="$3"; group="$4"
if [ ! -e "$dir" ]; then
if mkdir "$dir" 2>/dev/null; then
chown "$user":"$group" "$dir"
chmod "$mode" "$dir"
fi
fi
done
) << DATA
/usr/local/share 02775 root group
/usr/local/share/cacti 02775 root group
/usr/local/share/cacti/resource 02775 root group
/usr/local/share/cacti/resource/script_queries 02775 root group
/usr/local/share/cacti/resource/script_server 02775 root group
/usr/local/share/cacti/resource/snmp_queries 02775 root group
/usr/local/share/cacti/scripts 02775 root group
DATA

which is wrong, because group doesn't exist on my system. As a result, the
generated package fails to install (hence the severity). The manual says it
should be saying staff instead. The directories are created by a debian/dirs
file, so they are not created by me with the wrong group during build time
(anyways, also in my build env, that group doesn't exist).

Paul

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlnuR+kACgkQnFyZ6wW9
dQpdEQf/WPcOalD1VZanGIqEYl0H+OaB0gzfmJqfbKcKM5ZOEBeMvtEG1GjlDaG4
PaXUKhlW+NGHwrzN44BrXT76KXkS64eaMYn/H8eZX8TQ+RBKvOmpHHoXTJazCPsY
MW51x+lc77BYANsrfk7Bjvsje69WP4S+rxRCL2NJR01rKJXeqnTfSTqClL8b6KQO
X1rwvYx1N1NYd7P6m/LD2PWniiiYBGKmKV8Ij95T99Hxtg3vyJPm4bWjwNTpSq4R
hkEpxJRH4zVqLBzx1bzACKYoag32uDCFR1lGHQ2qIg1ghHvayCYgyDSNNJjbtdp+
9YdKxJ58qdyRUcMGwlSM4kB7vBMoqg==
=UPbC
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 10.10.3

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Oct 2017 21:24:08 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 10.10.3
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 879643
Changes:
 debhelper (10.10.3) unstable; urgency=medium
 .
   * dh_strip: Skip the entire directory when an exclude rule
 parameter matches it.
   * dh_fixperms: Improve the documentation to assume less familarity
 with "Rules-Requires-Root" (R³).
   * dh_usrlocal: Ditto.
   * dh_builddeb: Ditto.
   * dh_usrlocal: Correct the group name when creating directories
 owned by "root:staff".  Thanks to Paul Gevers for reporting
 the bug.  (Closes: #879643)
   * dh_usrlocal: Fix inverted boolean logic that made dh_usrlocal
 ignore ownership of directories when it should have preserved
 them.
Checksums-Sha1:
 a5f79a2a2ad4a200bbf81d488a0402e59a6fe4eb 1795 debhelper_10.10.3.dsc
 8c30238c97973e70f7653a3330ae1685fe4cbf4a 428548 debhelper_10.10.3.tar.xz
 cbe7d1435917501a9061404513daeda71f695cfd 4506 
debhelper_10.10.3_source.buildinfo
Checksums-Sha256:
 

Processed: closing 872378

[Debian Bug Tracking System]

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

> close 872378 1.06-2
Bug #872378 [fenrir] fenrir.deb: No speech after enabling fenrir to start in 
concial.
There is no source info for the package 'fenrir' at version '1.06-2' with 
architecture ''
Unable to make a source version for version '1.06-2'
Marked as fixed in versions 1.06-2.
Bug #872378 [fenrir] fenrir.deb: No speech after enabling fenrir to start in 
concial.
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#872378: closing 872378

[Samuel Thibault]

close 872378 1.06-2
thanks

Things are now working on my testbox, other issues are probably
configuration issues.

Bug#872378: fenrir.deb: No speech after enabling fenrir to start inconcial.

[Samuel Thibault]

Hello,

Matthew Dyer, on mar. 29 août 2017 10:55:33 -0400, wrote:
> Downgrading still gives me no speech.  I have speech with orca how ever. 
> Espeakup also works though not at the same time.  I have espeakup disabled at
> the moment.

Ok.

I have found issues in upstream packages, could you try installing the
version I have uploaded? (1.06-2)

Alternatively, you can modify /lib/systemd/system/fenrir.service

ExecStart=/usr/bin/fenrir-daemon

should actually read as

ExecStart=/usr/bin/fenrir

and make sure that you have the python3-dbus package installed.

If it still doesn't work, please send us your /var/log/fenrir.log

Samuel

Processed: severity of 879643 is grave

[Debian Bug Tracking System]

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

> severity 879643 grave
Bug #879643 [debhelper] debhelper: dh_usrlocal tries to chown to root:group 
which fails because group is not valid
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#877029: marked as done (taskcoach: Program fails to start)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 21:17:38 +
with message-id 
and subject line Bug#877029: fixed in taskcoach 1.4.3-5
has caused the Debian Bug report #877029,
regarding taskcoach: Program fails to start
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.)


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

Dear Maintainer,

Taskcoach will no longer start on my system. When selecting the program from
the gui nothing happens. Launching from the command line gives this:

 Traceback (most recent call last):
  File "/usr/bin/taskcoach", line 72, in 
start()
  File "/usr/bin/taskcoach", line 63, in start
app = application.Application(options, args)
  File "/usr/lib/python2.7/dist-packages/taskcoachlib/patterns/singleton.py",
line 29, in __call__
class_.instance = super(Singleton, class_).__call__(*args, **kwargs)
  File "/usr/lib/python2.7/dist-
packages/taskcoachlib/application/application.py", line 117, in __init__
self.initTwisted()
  File "/usr/lib/python2.7/dist-
packages/taskcoachlib/application/application.py", line 164, in initTwisted
if map(int, twisted.__version__.split('.')) < (11,):
ValueError: invalid literal for int() with base 10: '0rc1'






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

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

Versions of packages taskcoach depends on:
ii  fonts-dejavu 2.37-1
ii  libxss1  1:1.2.2-1+b2
ii  python   2.7.13-2
ii  python-chardet   3.0.4-1
ii  python-dateutil  2.6.1-1
ii  python-keyring   10.4.0-1
ii  python-lockfile  1:0.12.2-2
ii  python-pyparsing 2.1.10+dfsg1-1
ii  python-squaremap 1:1.0.4-2
ii  python-twisted-core  17.9.0~rc1-1
ii  python-wxgtk3.0  3.0.2.0+dfsg-4
ii  python-wxversion 3.0.2.0+dfsg-4
ii  python-xdg   0.25-4
ii  x11-utils7.7+3+b1
ii  xdg-utils1.1.1-1

Versions of packages taskcoach recommends:
ii  libavahi-compat-libdnssd1  0.7-3
ii  libgnome-2-0   2.32.1-6
ii  python-notify  0.1.1-4

Versions of packages taskcoach suggests:
pn  espeak   
pn  python-kde4  

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: taskcoach
Source-Version: 1.4.3-5

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

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated taskcoach 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: Mon, 23 Oct 2017 21:05:34 +0200
Source: taskcoach
Binary: taskcoach
Architecture: source
Version: 1.4.3-5
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Boulenguez 
Changed-By: Nicolas Boulenguez 
Description:
 taskcoach  - friendly task manager
Closes: 789565 877029
Changes:
 taskcoach (1.4.3-5) unstable; urgency=medium
 .
   * twisted-version-compare.diff: allow string minor version. Closes: 877029.
   * Handle API change in python-lockfile 0.9. Closes: 789565.
   * Make build-dependency on dh-python explicit.
   * Standards-Version: 4.1.1.
Checksums-Sha1:
 db52a1617c40e4e3b826143f6ad746c624cc81a6 2301 taskcoach_1.4.3-5.dsc
 9107b239b1e79dc41b4c7c2b94ba29a9077a4ee9 21324 taskcoach_1.4.3-5.debian.tar.xz
Checksums-Sha256:
 ab7674004123e136e4ddabb7aad093f7f3d30ff91c1c1a75a4d52c0df514b74c 2301 
taskcoach_1.4.3-5.dsc
 be86bcc454a7611eb9a76c3910de876f066682946a84c3d9033f2ea28d7b748b 21324 
taskcoach_1.4.3-5.debian.tar.xz
Files:
 59685430c2cb49cf815ef19bf2d0ba89 2301 utils 

Bug#878911: avahi FTBFS with debhelper 10.9.2

[Felipe Sateler]

On Sat, Oct 21, 2017 at 3:44 AM, Niels Thykier  wrote:
> Control: reassign -1 debhelper 10.9.2
>
> Michael Biebl:
>> On Tue, 17 Oct 2017 19:45:11 +0300 Adrian Bunk  wrote:
>>> Source: avahi
>>> Version: 0.7-3
>>> Severity: serious
>>>
>>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/avahi.html
>>>
>>> ...
>>>dh_systemd_start
>>> dh_systemd_start: Could not find "avahi-daemon.socket" in the 
>>> /lib/systemd/system directory of avahi-dnsconfd. This could be a typo, or 
>>> using Also= with a service file from another package. Please check 
>>> carefully that this message is harmless.
>>> dh_systemd_start: Cannot open(avahi-daemon.socket) for extracting the Also= 
>>> line(s)
>>> debian/rules:4: recipe for target 'binary' failed
>>> make: *** [binary] Error 2
>>>
>>>
>>> 19:35 < nthykier> bunk: Ideally, avahi would fix this on their end.  
>>> Without the fail-on-error, debhelper will silently "not do things"
>>>   when the file is unreadable (even if only temporarily).  
>>> I.e. a "fail-to-fail"-case
>>>
>>
>
> Hi,
>
>> avahi-daemon.socket is provided by avahi-daemon, a binary package which
>> is built from the same source package and avahi-dnsconfd depends on
>> avahi-daemon.
>
> Ok, when I spoke with Adrian about this, I had a different understanding
> of what happened and why it broke.
>
>> Niels, can you be a bit more specific why this fails now and what you
>> think is the proper fix?
>
> I can explain why it fails; dh_systemd_start basically reads the Also=
> line and pretends it was a part of the services listed on the cmdline/in
> the package.  As it is now mandatory for us to be able to read the
> service files, this will fail as the service is not where we expect to
> find it.
>
> The comment related to that part of the code reads:
>
> """
> # Handle all unit files specified via Also= explicitly.
> # This is not necessary for enabling, but for disabling, as we
> # cannot read the unit file when disabling (it was already
> # deleted).
> """
>
> @biebl/@fsateler: when a unit has an Also= that points to a unit in a
> different package can we then just ignore the relation?  I assume that
> we should not disable/stop services from another package on removal.

I think that in this case, the correct fix is to drop the Also= line.

1. We don't want to stop avahi-daemon socket if dnsconfd is removed
2. It appears the Also line is being treated as some form of
dependency manager (ie, to ensure that the avahi-daemon is started
when dnsconfd is started), but it is not necessary, because
avahi-daemon.socket is already Required.

So, I think we have not yet found a compelling case for dropping the
debhelper error. The Also line is not needed, and can be safely
dropped from the avahi-dnsconfd unit.

-- 

Saludos,
Felipe Sateler

Bug#871125: marked as done (nuitka: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 21:14:25 +
with message-id 
and subject line Bug#871125: fixed in nuitka 0.5.28.1+ds-1
has caused the Debian Bug report #871125,
regarding nuitka: FTBFS: Test failures
to be marked as done.

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

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


-- 
871125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nuitka
Version: 0.5.27+ds-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +  File "/<>/nuitka-0.5.27+ds/nuitka/utils/AppDirs.py", line 59, in 
> getCacheDir
> +makePath(result)
> +  File "/<>/nuitka-0.5.27+ds/nuitka/utils/FileOperations.py", line 
> 65, in makePath
> +os.makedirs(path)
> +  File "/usr/lib/python2.7/os.py", line 150, in makedirs
> +makedirs(head, mode)
> +  File "/usr/lib/python2.7/os.py", line 150, in makedirs
> +makedirs(head, mode)
> +  File "/usr/lib/python2.7/os.py", line 157, in makedirs
> +mkdir(name, mode)
> +OSError: [Errno 13] Permission denied: '/sbuild-nonexistent'
>  
> Exit codes 0 (CPython) != 1 (Nuitka)
> Error, outputs differed.
> Error exit! 1
> debian/rules:16: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/nuitka_0.5.27+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: nuitka
Source-Version: 0.5.28.1+ds-1

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

Debian distribution maintenance software
pp.
Kay Hayen  (supplier of updated nuitka package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Oct 2017 10:44:31 +0200
Source: nuitka
Binary: nuitka
Architecture: source all
Version: 0.5.28.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Kay Hayen 
Changed-By: Kay Hayen 
Description:
 nuitka - Python compiler with full language support and CPython compatibil
Closes: 871125
Changes:
 nuitka (0.5.28.1+ds-1) unstable; urgency=medium
 .
   * New upstream hotfix release.
   * Also ignore sbuild non-existant directory (Closes: #871125).
Checksums-Sha1:
 824c43a2e0fdc6e84085c0c8ffaf73a74be536f6 2190 nuitka_0.5.28.1+ds-1.dsc
 a1cab7404511218087b69b6f6510163fa8add133 801277 nuitka_0.5.28.1+ds.orig.tar.gz
 e29260ae2421d39eab95d26dcf53ef5d1c683f26 10532 
nuitka_0.5.28.1+ds-1.debian.tar.xz
 9969f88c3f36df0d8c2a03987938a3954244f767 704152 nuitka_0.5.28.1+ds-1_all.deb
 21331bc174c01835611fea58199044dabf6e5f4a 7190 
nuitka_0.5.28.1+ds-1_amd64.buildinfo
Checksums-Sha256:
 8de88edcfbf36874fa1600a316cd2fc7c4955eae9aa296dead64bde68fd135a8 2190 
nuitka_0.5.28.1+ds-1.dsc
 0af1acdfae3310471a989868dbd4a1c2485a641ca8136068099cff7d8ac97edc 801277 
nuitka_0.5.28.1+ds.orig.tar.gz
 bfc8e30203b2e571c3183c8f96cff39bb0b45bb1a16c2a54544765b7c386ba58 10532 
nuitka_0.5.28.1+ds-1.debian.tar.xz
 c29b9ba53b832d8a712bebd3ccbd123ad5098adb2b1b7562fa4bd91abf19ee11 704152 
nuitka_0.5.28.1+ds-1_all.deb
 eea04c19ccba3c9c7fe4ef5526772d3f56eeea4c822f466c1aa1bb4557d6fabf 7190 
nuitka_0.5.28.1+ds-1_amd64.buildinfo
Files:
 1fa931a57e2116c109966fc1dd352d0c 2190 python optional nuitka_0.5.28.1+ds-1.dsc
 eebcb0e0f1b3d2f26bdf5366bd8c8af3 801277 python optional 
nuitka_0.5.28.1+ds.orig.tar.gz
 8c6fb894968c13bce5ce9c3d7b4beb31 10532 python optional 
nuitka_0.5.28.1+ds-1.debian.tar.xz
 a38380ee38540f53383200f9fc3c46c1 704152 python optional 
nuitka_0.5.28.1+ds-1_all.deb
 

Bug#879635: marked as done (gobby: build against libinfinity-0.7-dev)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 21:07:51 +
with message-id 
and subject line Bug#879635: fixed in gobby 0.6.0~20170204~e5c2d1-1
has caused the Debian Bug report #879635,
regarding gobby: build against libinfinity-0.7-dev
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.)


-- 
879635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gobby
Version: 0.5.0-8.1
Severity: serious

libinfinity bumped to 0.7. Please build against the new version.

Emilio
--- End Message ---
--- Begin Message ---
Source: gobby
Source-Version: 0.6.0~20170204~e5c2d1-1

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

Debian distribution maintenance software
pp.
Philipp Kern  (supplier of updated gobby 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, 23 Oct 2017 21:07:56 +0200
Source: gobby
Binary: gobby
Architecture: source amd64
Version: 0.6.0~20170204~e5c2d1-1
Distribution: unstable
Urgency: medium
Maintainer: Philipp Kern 
Changed-By: Philipp Kern 
Description:
 gobby  - infinote-based collaborative text editor
Closes: 879635
Changes:
 gobby (0.6.0~20170204~e5c2d1-1) unstable; urgency=medium
 .
   * New upstream git snapshot (Closes: #879635)
Checksums-Sha1:
 9cd08a9ba0234b94ecdbd96fd9e8d4e37d647f2b 1707 gobby_0.6.0~20170204~e5c2d1-1.dsc
 13cff6b3a235c0d0531f47ccb8a959292873315a 519079 
gobby_0.6.0~20170204~e5c2d1.orig.tar.gz
 abe1decc2e573d47f9a8013bfd86faabd0b400cd 10400 
gobby_0.6.0~20170204~e5c2d1-1.debian.tar.xz
 d4d3fd6af177e9d3abdd8b4113dd9c0575a5c6bd 5958360 
gobby-dbgsym_0.6.0~20170204~e5c2d1-1_amd64.deb
 9cf6754f241c1225d1abebcfd413ca07af2fa09d 16131 
gobby_0.6.0~20170204~e5c2d1-1_amd64.buildinfo
 c2f9d92692769ea7744075f42272056ab7cd7b9b 549340 
gobby_0.6.0~20170204~e5c2d1-1_amd64.deb
Checksums-Sha256:
 8903cf5ebe09d083376f5182711754af3eb404707593c5c9f9f15f378cce3189 1707 
gobby_0.6.0~20170204~e5c2d1-1.dsc
 da90b04fd18a8afae03a754affa4c5173f3ca172645184a77fc9aa9a352d4478 519079 
gobby_0.6.0~20170204~e5c2d1.orig.tar.gz
 e033b02b3e2709da43e3d25ea280e4570f9615f304ee41b6df9ef7f860c251ef 10400 
gobby_0.6.0~20170204~e5c2d1-1.debian.tar.xz
 517fd6bf278610b49bc37477897641df744c9a1d6764bb838e5815e646ffc96c 5958360 
gobby-dbgsym_0.6.0~20170204~e5c2d1-1_amd64.deb
 1428e2c3fb72dbeb4f1849e2be5e4329d2560cb6d39854d013c5bb34d677 16131 
gobby_0.6.0~20170204~e5c2d1-1_amd64.buildinfo
 e8c9cde47d8889119ec6c8238601b0813b8c1993872e64c0255d1afce45622f8 549340 
gobby_0.6.0~20170204~e5c2d1-1_amd64.deb
Files:
 aba55aec29af6e2cc8326e600a72eba0 1707 net optional 
gobby_0.6.0~20170204~e5c2d1-1.dsc
 80664133e23d99ce7064f413ed047b47 519079 net optional 
gobby_0.6.0~20170204~e5c2d1.orig.tar.gz
 78bbca065b92bd7dfb6f2cfd45deeb37 10400 net optional 
gobby_0.6.0~20170204~e5c2d1-1.debian.tar.xz
 08bfdc190ddea14e19db2ed63d575998 5958360 debug optional 
gobby-dbgsym_0.6.0~20170204~e5c2d1-1_amd64.deb
 6b27850257a75b8d83f9eea117c5dcd7 16131 net optional 
gobby_0.6.0~20170204~e5c2d1-1_amd64.buildinfo
 e5a95cdf231b0c30568ee1a7b4f0d6c6 549340 net optional 
gobby_0.6.0~20170204~e5c2d1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAlnuRycRHHBrZXJuQGRl
Ymlhbi5vcmcACgkQRG4lRTXQVuzeRAgAr43tCW9mPAMksG2dkvOBlr5dBSF0OiQs
f16VttL9FX8gJemlhP1KqciTD1syaN/FbYdrYDkaG0imcJcG90bMxwx1X14j3Ass
6UqraRNcK02ZW1B8l5xmbEx0EFCrTPYC81FqQ4gWDs4VrglOD+XMHjXTczc4cTSd
iWlfB5NVzSpJzu+vbmOUEi7Vbm67BTVXtB42bQO9/a8E8zO5gcYlinAfTPkhTvfA
yAPpvfJzRoJKQXbsK9d0MGjF+uJaQfOU1KWZWgoFZmf+uja3D4jZEofaPqMYHgwy
HYZbp8P5bXWqEnAotEIrYKrOEE99fj+3zTZleBguqkTaJAIl9j+4ag==
=HZd9
-END PGP SIGNATURE End Message ---

Bug#878948:

[Javi Legido]

I can confirm the issue and the fix, installing libglvnd0 package.

Cheers.

Javier

Bug#873088: git-annex CVE-2017-12976 wheezy backport

[Antoine Beaupré]

Hi all,

I've undertaken the work to backport the patch for CVE-2017-12976 to
wheezy, that is 3.20120629 (!). First off, the Ddar and Gcrypt remote
were missing, so that reduced the work. It also seems that the assistant
didn't need to be patched because it didn't use ssh host primitives as
much.

At least this is what I found. The debdiff is attached and I have
uploaded a test build on my usual repository:

https://people.debian.org/~anarcat/debian/wheezy-lts/

Test seems to pass, both at build time and during some basic smoke tests
in a wheezy VM. I also can't reproduce the issue with the new package,
so the fix seems to work. I am assuming Haskell's type checking take
care of the rest.

Any review would be greatly appreciated, I plan on uploading this to
wheezy by the end of the week.

Note that the stretch upload should be fairly trivial with the provided
patch: just apply, fix the change and upload. Jessie should be fairly
easy to patch with the two examples...

Thanks especially to Joeyh for his quick response!

A.

-- 
I would defend the liberty of consenting adult creationists to practice
whatever intellectual perversions they like in the privacy of their own
homes; but it is also necessary to protect the young and innocent.
- Arthur C. Clarke
>From 05903f52f614243421451836c4431e3b63de53ce Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= 
Date: Mon, 23 Oct 2017 16:50:56 -0400
Subject: [PATCH] (oldstable) fix dashed ssh hostname issue CVE-2017-12976
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Security fix: Disallow hostname starting with a dash, which would get
passed to ssh and be treated an option. This could be used by an attacker
who provides a crafted ssh url (for eg a git remote) to execute arbitrary
code via ssh -oProxyCommand.

The same class of security hole recently affected git itself,
CVE-2017-1000117.

Method: Identified all places where ssh is run, by git grep '"ssh"'
Converted them all to use a SshHost, if they did not already, for
specifying the hostname.

SshHost was made a data type with a smart constructor, which rejects
hostnames starting with '-'.

Note that git-annex already contains extensive use of Utility.SafeCommand,
which fixes a similar class of problem where a filename starting with a
dash gets passed to a program which treats it as an option.

This was backported by Antoine Beaupré, from the upstream stable patch
provided by Joey Hess.
---
 Annex/Ssh.hs | 22 --
 Remote/Helper/Ssh.hs |  7 ++-
 Utility/SshHost.hs   | 29 +
 debian/changelog | 10 ++
 4 files changed, 57 insertions(+), 11 deletions(-)
 create mode 100644 Utility/SshHost.hs

diff --git a/Annex/Ssh.hs b/Annex/Ssh.hs
index 8bd4fe33a..63c2324a3 100644
--- a/Annex/Ssh.hs
+++ b/Annex/Ssh.hs
@@ -18,10 +18,11 @@ import qualified Git.Config
 import Config
 import qualified Build.SysConfig as SysConfig
 import Annex.Perms
+import Utility.SshHost
 
 {- Generates parameters to ssh to a given host (or user@host) on a given
  - port, with connection caching. -}
-sshParams :: (String, Maybe Integer) -> [CommandParam] -> Annex [CommandParam]
+sshParams :: (SshHost, Maybe Integer) -> [CommandParam] -> Annex [CommandParam]
 sshParams (host, port) opts = go =<< sshInfo (host, port)
 	where
 		go (Nothing, params) = ret params
@@ -30,14 +31,14 @@ sshParams (host, port) opts = go =<< sshInfo (host, port)
 			liftIO $ createDirectoryIfMissing True $ parentDir socketfile
 			lockFile $ socket2lock socketfile
 			ret params
-		ret ps = return $ ps ++ opts ++ portParams port ++ [Param host]
+		ret ps = return $ ps ++ opts ++ portParams port ++ [Param (fromSshHost host)]
 		-- If the lock pool is empty, this is the first ssh of this
 		-- run. There could be stale ssh connections hanging around
 		-- from a previous git-annex run that was interrupted.
 		cleanstale = whenM (not . any isLock . M.keys <$> getPool) $
 			sshCleanup
 
-sshInfo :: (String, Maybe Integer) -> Annex (Maybe FilePath, [CommandParam])
+sshInfo :: (SshHost, Maybe Integer) -> Annex (Maybe FilePath, [CommandParam])
 sshInfo (host, port) = ifM caching
 	( do
 		dir <- fromRepo gitAnnexSshDir
@@ -91,7 +92,7 @@ sshCleanup = do
 -- "ssh -O stop" is noisy on stderr even with -q
 let cmd = unwords $ toCommand $
 	[ Params "-O stop"
-	] ++ params ++ [Param host]
+	] ++ params ++ [Param (fromSshHost host)]
 boolSystem "sh"
 	[ Param "-c"
 	, Param $ "ssh " ++ cmd ++ " >/dev/null 2>/dev/null"
@@ -99,16 +100,17 @@ sshCleanup = do
 -- Cannot remove the lock file; other processes may
 -- be waiting on our exclusive lock to use it.
 
-hostport2socket :: String -> Maybe Integer -> FilePath
-hostport2socket host Nothing = host
-hostport2socket host (Just port) = host ++ "!" ++ show port
+hostport2socket :: SshHost -> Maybe Integer -> FilePath
+hostport2socket 

Processed: notfound 849832 in 1:52.4.0-1

[Debian Bug Tracking System]

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

> notfound 849832 1:52.4.0-1
Bug #849832 [icedove] firefox: contains JSHint work under non-free licence
Ignoring request to alter found versions of bug #849832 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#879264: cannot enter the desktop environment

[Luca Boccassi]

On Sat, 21 Oct 2017 12:34:31 +0200 Michael Biebl 
wrote:
> Control: reassign -1 liglvnd0-nvidia
> Control: forcemerge 878851 -1
> 
> Hi Lu Wang
> 
> Am 21.10.2017 um 12:10 schrieb Lu Wang:
> > Oct 21 16:58:56 lenovo /usr/lib/gdm3/gdm-x-session[16569]: Couldn't
open libGL.so.1: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined
symbol: _glapi_tls_Current
> > 
> 
> While you see gdm3 failing to start, your underlying problem is a
> botched OpenGL installation coming from the NVIDIA driver. See
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878851
> 
> I'm reassigning the bug report accordingly.
> 
> Afaics, you should ge able to get back to a usable system by
installing
> liglvnd0 (which will replace libglvnd0-nvidia)
> 
> Regards,
> Michael

Andreas,

Shall we remove the provides? It looks like, for whatever reasons, not
all the symbols are exported by nvidia. Perhaps the bundled glvnd
libraries are too old?

libGLdispatch.so.0 in libglvnd0 exports that symbol.

Kind regards,
Luca Boccassi

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

Processed: mariadb-10.1: FTBFS on mips64el due to test failures

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:gdal
Bug #879637 [src:mariadb-10.1] mariadb-10.1: FTBFS on mips64el due to test 
failures
Added indication that 879637 affects src:gdal

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

Bug#879637: mariadb-10.1: FTBFS on mips64el due to test failures

[Bas Couwenberg]

Source: mariadb-10.1
Version: 10.1.28-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:gdal

Dear Maintainer,

mariadb-10.1 (10.1.28-1) FTBFS on mips64el, and the missing binaries are
blocking testing migration of mariadb-10.1 and its reverse dependencies.

For the full build logs, see:

 
https://buildd.debian.org/status/logs.php?arch=mips64el=mariadb-10.1=10.1.28-1

Please fix this ASAP or consider ignoring the test failure.

Kind Regards,

Bas

Bug#879635: gobby: build against libinfinity-0.7-dev

[Emilio Pozuelo Monfort]

Package: gobby
Version: 0.5.0-8.1
Severity: serious

libinfinity bumped to 0.7. Please build against the new version.

Emilio

Bug#879636: openvdb: FTBFS on mips(el): virtual memory exhausted: Cannot allocate memory

[Emilio Pozuelo Monfort]

Source: openvdb
Version: 4.0.2-1
Severity: serious

Your package failed to build on mips(el):

g++ -c -g -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fvisibility=hidden -fvisibility-inlines-hidden -O1 -std=c++11 -pthread -g -I . 
-I .. -I /usr/include -I /usr/include/OpenEXR -I /usr/include -I /usr/include 
-I /usr/include -DOPENVDB_USE_BLOSC -DOPENVDB_USE_LOG4CPLUS 
-DOPENVDB_USE_GLFW_3 -I /usr/include -fPIC -o unittest/TestUtil.o 
unittest/TestUtil.cc
virtual memory exhausted: Cannot allocate memory
Makefile:861: recipe for target 'unittest/TestTools.o' failed

sh4 also seems affected by this.

Full logs at https://buildd.debian.org/status/package.php?p=openvdb

Emilio

Processed: retitle 879516 to glm: Mailing list rejects mail from debian BTS

[Debian Bug Tracking System]

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

> retitle 879516 glm: Mailing list rejects mail from debian BTS
Bug #879516 [rrdtool] [Fwd: Bug#879511: Updating the rrdtool Uploaders list]
Changed Bug title to 'glm: Mailing list rejects mail from debian BTS' from 
'[Fwd: Bug#879511: Updating the rrdtool Uploaders list]'.
> thanks
Stopping processing here.

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

Bug#878666: marked as done (kopano-search depends on cruft package mktemp)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 18:19:08 +
with message-id 
and subject line Bug#877549: fixed in kopanocore 8.3.4-3
has caused the Debian Bug report #877549,
regarding kopano-search depends on cruft package mktemp
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.)


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

Package: kopano-search
Severity: serious
Tags: buster, sid

kopano-search depends on the package mktemp which is no longer built by the coreutils source 
package. Prior to being dropped this was a transitional package depending on "coreutils 
(>= 7.4-1)", please update your dependency so that the package can be decrufted.
--- End Message ---
--- Begin Message ---
Source: kopanocore
Source-Version: 8.3.4-3

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated kopanocore 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Oct 2017 18:27:15 +0200
Source: kopanocore
Binary: kopano-libs kopano-core kopano-archiver kopano-backup kopano-common 
kopano-contacts kopano-dev kopano-dagent kopano-gateway kopano-ical kopano-l10n 
kopano-monitor kopano-search kopano-server kopano-spooler kopano-utils 
python-mapi python-kopano php-mapi
Architecture: source
Version: 8.3.4-3
Distribution: unstable
Urgency: medium
Maintainer: Giraffe Maintainers 

Changed-By: Carsten Schoenert 
Description:
 kopano-archiver - Complete and feature rich groupware solution - archiver
 kopano-backup - Complete and feature rich groupware solution - backup
 kopano-common - Complete and feature rich groupware solution - common files
 kopano-contacts - Complete and feature rich groupware solution - contact mapi 
provi
 kopano-core - Metapackage to install the Kopano Core stack
 kopano-dagent - Complete and feature rich groupware solution - delivery agent
 kopano-dev - C++ Development files and libraries for Kopano Core
 kopano-gateway - Complete and feature rich groupware solution - POP3 and IMAP 
gate
 kopano-ical - Complete and feature rich groupware solution - CalDAV and CalDAV
 kopano-l10n - Complete and feature rich groupware solution - l10n files
 kopano-libs - Complete and feature rich groupware solution - Free/Busy library
 kopano-monitor - Complete and feature rich groupware solution - quota monitor
 kopano-search - Complete and feature rich groupware solution - indexer
 kopano-server - Complete and feature rich groupware solution - server component
 kopano-spooler - Complete and feature rich groupware solution - email spooler
 kopano-utils - Complete and feature rich groupware solution - admin tools
 php-mapi   - Complete and feature rich groupware solution - PHP MAPI bindings
 python-kopano - Complete and feature rich groupware solution - Python bindings
 python-mapi - Complete and feature rich groupware solution - Python MAPI bindin
Closes: 876480 877454 877549
Changes:
 kopanocore (8.3.4-3) unstable; urgency=medium
 .
   [ Guido Günther ]
   * [75a1b00] kopano-dev: Depend on kopano-libs (Closes: #877454)
 Obviously needs the -dev package needs a depending on the library package.
 Without those libraries no real development is possible.
   * [e2098a7] kopano-search: drop dependencies on essential packages
 The dependencies on various now partially essential packages aren't needed
 and can be dropped.
 (Closes: #877549)
   * [6d4dc9b] uscan: switch to https
   * [cf57093] uscan: Match on beta versions and ignore .90 "betas"
 Be more open for beta versions too, but ignore versions of *.90 which are
 like final pre versions for the next release.
 .
   [ Carsten Schoenert ]
   * [9414114] debian/control: increase Standards-Version to 4.1.1
 No further changes are needed.
   * [3e273da] debian/control: put 

Bug#877454: marked as done (kopano-dev: missing Depends: kopano-libs (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 18:19:08 +
with message-id 
and subject line Bug#877454: fixed in kopanocore 8.3.4-3
has caused the Debian Bug report #877454,
regarding kopano-dev: missing Depends: kopano-libs (= ${binary:Version})
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.)


-- 
877454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kopano-dev
Version: 8.3.4-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m17.9s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libmapi.so -> libmapi.so.1.0.0
  /usr/lib/x86_64-linux-gnu/libkcutil.so -> libkcutil.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkcsync.so -> libkcsync.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkcssl.so -> libkcssl.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkcsoap.so -> libkcsoap.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkcserver.so -> libkcserver.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkcpydirector.so -> libkcpydirector.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkcpyconv.so -> libkcpyconv.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkcmapi.so -> libkcmapi.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkcinetmapi.so -> libkcinetmapi.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkcicalmapi.so -> libkcicalmapi.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkchl.so -> libkchl.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkcfreebusy.so -> libkcfreebusy.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkcarchivercore.so -> libkcarchivercore.so.0.0.0
  /usr/lib/x86_64-linux-gnu/libkcarchiver.so -> libkcarchiver.so.0.0.0
  /usr/lib/x86_64-linux-gnu/kopano/ldapmsplugin.so -> ldapplugin.so


cheers,

Andreas


kopano-dev_8.3.4-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kopanocore
Source-Version: 8.3.4-3

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated kopanocore 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Oct 2017 18:27:15 +0200
Source: kopanocore
Binary: kopano-libs kopano-core kopano-archiver kopano-backup kopano-common 
kopano-contacts kopano-dev kopano-dagent kopano-gateway kopano-ical kopano-l10n 
kopano-monitor kopano-search kopano-server kopano-spooler kopano-utils 
python-mapi python-kopano php-mapi
Architecture: source
Version: 8.3.4-3
Distribution: unstable
Urgency: medium
Maintainer: Giraffe Maintainers 

Changed-By: Carsten Schoenert 
Description:
 kopano-archiver - Complete and feature rich groupware solution - archiver
 kopano-backup - Complete and feature rich groupware solution - backup
 kopano-common - Complete and feature rich groupware solution - common files
 kopano-contacts - Complete and feature rich groupware solution - contact mapi 
provi
 kopano-core - Metapackage to install the Kopano Core stack
 kopano-dagent - Complete and feature rich groupware solution - delivery agent
 kopano-dev - C++ Development files and libraries for Kopano Core
 kopano-gateway - Complete and feature rich groupware solution - POP3 and IMAP 
gate
 kopano-ical - Complete and feature rich groupware solution - CalDAV and CalDAV
 kopano-l10n - Complete and feature rich groupware solution - l10n files
 kopano-libs - Complete and feature rich groupware solution - Free/Busy library
 kopano-monitor - Complete and feature rich groupware solution - quota monitor
 kopano-search - Complete and feature rich groupware solution - indexer
 kopano-server - Complete and feature rich groupware solution - server component
 kopano-spooler - Complete and feature rich groupware solution - email spooler
 kopano-utils - Complete and feature rich groupware solution - admin tools
 php-mapi   - Complete and 

Bug#877549: marked as done (kopano-search has obsolete dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 18:19:08 +
with message-id 
and subject line Bug#877549: fixed in kopanocore 8.3.4-3
has caused the Debian Bug report #877549,
regarding kopano-search has obsolete dependencies
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.)


-- 
877549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kopano-search
Version: 8.3.4-2
Severity: normal

kopano-search should no longer require dependencies on coreutils >= 5.93 or
mktemp >= 1.5, as these have been Essential packages for several releases.
The dependency on bash >= 3.0 is similarly redundant.

Mike Stone
--- End Message ---
--- Begin Message ---
Source: kopanocore
Source-Version: 8.3.4-3

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated kopanocore 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Oct 2017 18:27:15 +0200
Source: kopanocore
Binary: kopano-libs kopano-core kopano-archiver kopano-backup kopano-common 
kopano-contacts kopano-dev kopano-dagent kopano-gateway kopano-ical kopano-l10n 
kopano-monitor kopano-search kopano-server kopano-spooler kopano-utils 
python-mapi python-kopano php-mapi
Architecture: source
Version: 8.3.4-3
Distribution: unstable
Urgency: medium
Maintainer: Giraffe Maintainers 

Changed-By: Carsten Schoenert 
Description:
 kopano-archiver - Complete and feature rich groupware solution - archiver
 kopano-backup - Complete and feature rich groupware solution - backup
 kopano-common - Complete and feature rich groupware solution - common files
 kopano-contacts - Complete and feature rich groupware solution - contact mapi 
provi
 kopano-core - Metapackage to install the Kopano Core stack
 kopano-dagent - Complete and feature rich groupware solution - delivery agent
 kopano-dev - C++ Development files and libraries for Kopano Core
 kopano-gateway - Complete and feature rich groupware solution - POP3 and IMAP 
gate
 kopano-ical - Complete and feature rich groupware solution - CalDAV and CalDAV
 kopano-l10n - Complete and feature rich groupware solution - l10n files
 kopano-libs - Complete and feature rich groupware solution - Free/Busy library
 kopano-monitor - Complete and feature rich groupware solution - quota monitor
 kopano-search - Complete and feature rich groupware solution - indexer
 kopano-server - Complete and feature rich groupware solution - server component
 kopano-spooler - Complete and feature rich groupware solution - email spooler
 kopano-utils - Complete and feature rich groupware solution - admin tools
 php-mapi   - Complete and feature rich groupware solution - PHP MAPI bindings
 python-kopano - Complete and feature rich groupware solution - Python bindings
 python-mapi - Complete and feature rich groupware solution - Python MAPI bindin
Closes: 876480 877454 877549
Changes:
 kopanocore (8.3.4-3) unstable; urgency=medium
 .
   [ Guido Günther ]
   * [75a1b00] kopano-dev: Depend on kopano-libs (Closes: #877454)
 Obviously needs the -dev package needs a depending on the library package.
 Without those libraries no real development is possible.
   * [e2098a7] kopano-search: drop dependencies on essential packages
 The dependencies on various now partially essential packages aren't needed
 and can be dropped.
 (Closes: #877549)
   * [6d4dc9b] uscan: switch to https
   * [cf57093] uscan: Match on beta versions and ignore .90 "betas"
 Be more open for beta versions too, but ignore versions of *.90 which are
 like final pre versions for the next release.
 .
   [ Carsten Schoenert ]
   * [9414114] debian/control: increase Standards-Version to 4.1.1
 No further changes are needed.
   * [3e273da] debian/control: put l10n package into section localization
   * [1e61e46] 

Bug#879631: python3-flask-socketio: missing dependency

[astian]

Package: python3-flask-socketio
Version: 2.9.0-1
Severity: serious

Dear Maintainer,

This package lacks a dependency on the upstream "python-socketio" [0],
which provides a "socketio" module.  Please do not confuse it with the
Debian package of the same name, which also provides a "socketio": that
package is actually "gevent-socketio" [1] and incompatible with
python3-flask-socketio [2].

  0: https://github.com/miguelgrinberg/python-socketio/
  1: https://github.com/abourget/gevent-socketio
  2: From flask_socketio/__init__.py:
   if gevent_socketio_found:
   print('The gevent-socketio package is incompatible with this version 
of '
 'the Flask-SocketIO extension. Please uninstall it, and then '
 'install the latest version of python-socketio in its place.')
   sys.exit(1)

It seems that the required package is not currently packaged in Debian,
unfortunately.  As is, python3-flask-socketio is useless.  Further
justification for "serious" severity: Debian policy manual section 3.5
[3].

  3: https://www.debian.org/doc/debian-policy/#dependencies

Cheers.

PS: The package tracker at  says:

  action needed
  Problems while searching for a new upstream version


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

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

Versions of packages python3-flask-socketio depends on:
ii  python3   3.6.3-1
ii  python3-engineio  1.6.1-1
ii  python3-flask 0.12.2-2

python3-flask-socketio recommends no packages.

python3-flask-socketio suggests no packages.

-- no debconf information

Bug#878935: marked as done (Unsatisfiable dependencies on !amd64)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 17:20:34 +
with message-id 
and subject line Bug#878935: fixed in bpfcc 0.3.0-4
has caused the Debian Bug report #878935,
regarding Unsatisfiable dependencies on !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.)


-- 
878935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbpfcc
Version: 0.3.0-3
Severity: serious
Justification: Makes the package uninstallable on most architectures

Hi!

As [0] shows, libbpfcc has unsatisfiable dependencies on everything but
amd64. This is because [1] is inherently wrong, "linux-headers-amd64"
is of course only available on amd64, the other architectures have
their own meta-packages [2]. Unfortunately there is (AFAIK) no good way
to properly solve the "this package needs the current kernel headers
installed" problem in Debian because

   1. There are no (real or virtual) "linux-{image,headers}-
  generic" packages (like in Ubuntu [3,4]) which have the same name on
  all architectures.
   2. Even if there were such packages, there's no guarantee that "linux-
  headers-generic" would point to the headers matching the *currently
  running* kernel (which is what libbcc needs). In fact, with partial
  upgrades, migrations from unstable to testing, upgraded-but-not-yet-
  rebooted machines, etc., it is quite likely that libbpfcc will be
  broken even if all its dependencies are fulfilled.

I therefore ask you to

   1. Revert [1].
   2. Reopen [5] and put a note regarding the requirements of the kernel
  headers in README.Debian and/or the package description.
   3. Talk to the Debian Linux maintainers to find a proper solution to
  this problem. It's probably not going to be easy, but these kinds of
  problems really deserve to be fixed properly.

Yes, this sucks. I have run into #877925 myself and also thought that
this should be simply solvable with a dependency. Oh, well, at least
you may take comfort in the fact that others [6] have also run into
this problem... ;-)

Best regards

Alexander Kurtz

[0] https://tracker.debian.org/pkg/bpfcc
[1] 
https://anonscm.debian.org/git/collab-maint/bpfcc.git/commit/?id=f73049e48fd98dd01d4475f88f6b490e6a1b34bb
[2] https://packages.debian.org/source/sid/linux
[3] https://packages.ubuntu.com/artful/linux-image-generic
[4] https://packages.ubuntu.com/artful/linux-headers-generic
[5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877925
[6] https://anonscm.debian.org/git/pkg-dkms/dkms.git/tree/debian/control#n24

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: bpfcc
Source-Version: 0.3.0-4

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated bpfcc 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, 23 Oct 2017 22:08:02 +0530
Source: bpfcc
Binary: libbpfcc libbpfcc-dev python-bpfcc bpfcc-tools bpfcc-lua
Architecture: source amd64 all
Version: 0.3.0-4
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf 
Changed-By: Ritesh Raj Sarraf 
Description:
 bpfcc-lua  - Standalone tool to run BCC tracers written in Lua
 bpfcc-tools - tools for BPF Compiler Collection (BCC)
 libbpfcc   - shared library for BPF Compiler Collection (BCC)
 libbpfcc-dev - shared library for BPF Compiler Collection (BCC)
 python-bpfcc - Python wrappers for BPF Compiler Collection (BCC)
Closes: 878922 878935
Changes:
 bpfcc (0.3.0-4) unstable; urgency=medium
 .
   * Add dependency on library for the development package.
 Thanks to Alexander Kurtz (Closes: #878922)
   * Revert "Add depends on linux headers package, which is a dependency
 for JIT"
   * Update README.Debian with details about dependency on running
 kernel development headers and debug package.
 

Bug#878922: marked as done (libbpfcc-dev does not depend on libbpfcc)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 17:20:34 +
with message-id 
and subject line Bug#878922: fixed in bpfcc 0.3.0-4
has caused the Debian Bug report #878922,
regarding libbpfcc-dev does not depend on libbpfcc
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.)


-- 
878922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbpfcc-dev
Version: 0.3.0-3
Severity: serious
Justification: Policy violation

Hi!

Debian Policy, section 8.4 ("Development files") [0] says:

Installing the development package must result in installation 
of all the development files necessary for compiling programs
against that shared library.

However, libbpfcc-dev does not depend on libbpfcc. This makes
compilation fail, for example like this:

root@riga:~/alfwrapper# make
cc -std=gnu11 -Iinclude -O2 -Wall -Wextra -Werror --output='alfwrapper' 
src/alfwrapper.c lib/bcc.c lib/die.c lib/env.c lib/pid.c lib/string.c 
lib/cleanup.c lib/path.c lib/fd.c lib/parse.c lib/argv.c lib/socket.c -lbcc
/usr/bin/ld: cannot find -lbcc
collect2: error: ld returned 1 exit status
Makefile:9: recipe for target 'alfwrapper' failed
make: *** [alfwrapper] Error 1
root@riga:~/alfwrapper# 

Please fix this by making libbpfcc-dev depend on libbpfcc.

Best regards

Alexander Kurtz

[0] https://www.debian.org/doc/debian-policy/#development-files

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: bpfcc
Source-Version: 0.3.0-4

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated bpfcc 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, 23 Oct 2017 22:08:02 +0530
Source: bpfcc
Binary: libbpfcc libbpfcc-dev python-bpfcc bpfcc-tools bpfcc-lua
Architecture: source amd64 all
Version: 0.3.0-4
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf 
Changed-By: Ritesh Raj Sarraf 
Description:
 bpfcc-lua  - Standalone tool to run BCC tracers written in Lua
 bpfcc-tools - tools for BPF Compiler Collection (BCC)
 libbpfcc   - shared library for BPF Compiler Collection (BCC)
 libbpfcc-dev - shared library for BPF Compiler Collection (BCC)
 python-bpfcc - Python wrappers for BPF Compiler Collection (BCC)
Closes: 878922 878935
Changes:
 bpfcc (0.3.0-4) unstable; urgency=medium
 .
   * Add dependency on library for the development package.
 Thanks to Alexander Kurtz (Closes: #878922)
   * Revert "Add depends on linux headers package, which is a dependency
 for JIT"
   * Update README.Debian with details about dependency on running
 kernel development headers and debug package.
 Thanks to Alexander Kurtz (Closes: #878935)
Checksums-Sha1:
 db6aee226acd02ddec877391c16970883322087b 2500 bpfcc_0.3.0-4.dsc
 bf4c3cc00b11c58f1b3ab5d7574b9eb972ba12e7 6376 bpfcc_0.3.0-4.debian.tar.xz
 2050b8cc4278f4daf5b93735118862b08fbab3ed 8598626 
bpfcc-lua-dbgsym_0.3.0-4_amd64.deb
 118e903940dd30bf66cf2851dfa377ff917ef21b 11486120 bpfcc-lua_0.3.0-4_amd64.deb
 09237718d7256963f669dd5f5ab46d9062d32f26 581796 bpfcc-tools_0.3.0-4_all.deb
 a804743770f9dbaf0dd53abc1b193942a1b70685 9860 bpfcc_0.3.0-4_amd64.buildinfo
 c7de5f5916f0fdd503786ce570c763e1e7574fb0 8637494 
libbpfcc-dbgsym_0.3.0-4_amd64.deb
 aa4f026b6ae6d1e95868e1134d0c013385f4bff8 15626 libbpfcc-dev_0.3.0-4_all.deb
 15f353190a78d86259055c40328ace7e112d5e2e 11028710 libbpfcc_0.3.0-4_amd64.deb
 7e20a02e7bfdb39c283833bc8197de87e87de8cb 22104 python-bpfcc_0.3.0-4_all.deb
Checksums-Sha256:
 0312a07c4b5c441e75ce33b7397f5f2300eafea1682908eb4da6e8fefb7e40a6 2500 
bpfcc_0.3.0-4.dsc
 75fbba3c53cd0693d0273db82102bc958dada20264da764a722ae089d0c7cc19 6376 
bpfcc_0.3.0-4.debian.tar.xz
 1c58f4e5c58620234233eee1042f6aeaec817944457dc5f8a2c8b27a42df7fc0 8598626 

Processed: CVE-2016-10504 / CVE-2017-14151

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 2.1.0-2+deb8u2
Bug #874430 {Done: Mathieu Malaterre } [src:openjpeg2] 
openjpeg2: CVE-2017-14151: heap-based buffer overflow in opj_mqc_flush
Ignoring request to alter found versions of bug #874430 to the same values 
previously set

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

Bug#874430: CVE-2016-10504 / CVE-2017-14151

[Mathieu Malaterre]

Control: notfound -1 2.1.0-2+deb8u2

I have been trying to track those related CVE and it appears that this
commit should avoid this kind of issue:

https://github.com/uclouvain/openjpeg/commit/3a80b72ac

(I had actually forgotten I authored this back then).

I think the issue was introducated later:

https://github.com/uclouvain/openjpeg/commit/e05d2901e

So I will not include the related patch.

Cheers

Bug#878312: marked as done (intel-gpu-tools FTBFS on i386: igt_x86.c:96:10: error: redefinition of 'igt_x86_features')

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 19:40:25 +0300
with message-id 
and subject line Re: Bug#878312: intel-gpu-tools FTBFS on i386: 
igt_x86.c:96:10: error: redefinition of 'igt_x86_features'
has caused the Debian Bug report #878312,
regarding intel-gpu-tools FTBFS on i386: igt_x86.c:96:10: error: redefinition 
of 'igt_x86_features'
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.)


-- 
878312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: intel-gpu-tools
Version: 1.20-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=intel-gpu-tools=i386=1.20-1=1507331187=0

...
../../lib/igt_x86.c:96:10: error: redefinition of 'igt_x86_features'
 unsigned igt_x86_features(void)
  ^~~~
In file included from ../../lib/igt_x86.c:38:0:
../../lib/igt_x86.h:47:24: note: previous definition of 'igt_x86_features' was 
here
 static inline unsigned igt_x86_features(void)
^~~~
../../lib/igt_x86.c:148:7: error: redefinition of 'igt_x86_features_to_string'
 char *igt_x86_features_to_string(unsigned features, char *line)
   ^~
In file included from ../../lib/igt_x86.c:38:0:
../../lib/igt_x86.h:51:21: note: previous definition of 
'igt_x86_features_to_string' was here
 static inline char *igt_x86_features_to_string(unsigned features, char *line)
 ^~
Makefile:718: recipe for target 'igt_x86.lo' failed
make[5]: *** [igt_x86.lo] Error 1
--- End Message ---
--- Begin Message ---
fixed 878312 1.20-2
thanks

-- 
t--- End Message ---

Processed: tagging 879471

[Debian Bug Tracking System]

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

> tags 879471 + confirmed
Bug #879471 [src:varnish] src:varnish: 5.2 needs a SONAME version bump
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#878408: marked as done (cdo FTBFS on 32bit: undefined references)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 15:33:53 +
with message-id 
and subject line Bug#878408: fixed in cdo 1.9.1+dfsg.1-4
has caused the Debian Bug report #878408,
regarding cdo FTBFS on 32bit: undefined references
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.)


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

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

...
libtool: link: g++ -g -O2 -fdebug-prefix-map=/<>/cdo-1.9.1+dfsg.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -fopenmp -Wl,-z 
-Wl,relro -Wl,-z -Wl,now -o .libs/cdo cdo-cdo.o cdo-Adisit.o cdo-Afterburner.o 
cdo-Arith.o cdo-Arithc.o cdo-Arithdays.o cdo-Arithlat.o cdo-CDItest.o 
cdo-CDIread.o cdo-CDIwrite.o cdo-Cat.o cdo-Change.o cdo-Change_e5slm.o 
cdo-Cloudlayer.o cdo-CMOR.o cdo-CMOR_lite.o cdo-CMOR_table.o cdo-Collgrid.o 
cdo-Command.o cdo-Comp.o cdo-Compc.o cdo-Complextorect.o cdo-Cond.o cdo-Cond2.o 
cdo-Condc.o cdo-Consecstat.o cdo-Copy.o cdo-Deltat.o cdo-Deltime.o 
cdo-Derivepar.o cdo-Detrend.o cdo-Diff.o cdo-Distgrid.o cdo-Duplicate.o 
cdo-EOFs.o cdo-Eof3d.o cdo-EcaIndices.o cdo-Echam5ini.o cdo-Enlarge.o 
cdo-Enlargegrid.o cdo-Ensstat.o cdo-Ensstat3.o cdo-Ensval.o cdo-Eofcoeff.o 
cdo-Eofcoeff3d.o cdo-EstFreq.o cdo-Exprf.o cdo-FC.o cdo-Filedes.o 
cdo-Fillmiss.o cdo-Filter.o cdo-Fldrms.o cdo-Fldstat.o cdo-Fldstat2.o 
cdo-Fourier.o cdo-Gengrid.o cdo-Gradsdes.o cdo-Gri
 dboxstat.o cdo-Gridcell.o cdo-Gridsearch.o cdo-Harmonic.o cdo-Hi.o 
cdo-Histogram.o cdo-Importamsr.o cdo-Importbinary.o cdo-Importcmsaf.o 
cdo-Importobs.o cdo-Info.o cdo-Input.o cdo-Intgrid.o cdo-Intgridtraj.o 
cdo-Intlevel.o cdo-Intlevel3d.o cdo-Intntime.o cdo-Inttime.o cdo-Intyear.o 
cdo-Invert.o cdo-Invertlev.o cdo-Isosurface.o cdo-Log.o cdo-MapReduce.o 
cdo-Maskbox.o cdo-Mastrfu.o cdo-Math.o cdo-Merge.o cdo-Mergegrid.o 
cdo-Mergetime.o cdo-Merstat.o cdo-Monarith.o cdo-Mrotuv.o cdo-Mrotuvb.o 
cdo-Ninfo.o cdo-Nmldump.o cdo-Output.o cdo-Outputgmt.o cdo-Pack.o cdo-Pardup.o 
cdo-Pinfo.o cdo-Pressure.o cdo-Regres.o cdo-Remap.o cdo-Remapeta.o 
cdo-Replace.o cdo-Replacevalues.o cdo-Rhopot.o cdo-Rotuv.o cdo-Runpctl.o 
cdo-Runstat.o cdo-Samplegrid.o cdo-Samplegridicon.o cdo-Seascount.o 
cdo-Seaspctl.o cdo-Seasstat.o cdo-Selbox.o cdo-Selgridcell.o cdo-Select.o 
cdo-Selmulti.o cdo-Seloperator.o cdo-Selrec.o cdo-Seltime.o cdo-Selvar.o 
cdo-Set.o cdo-Setattribute.o cdo-Setbox.o cdo-Setgatt.o cdo-Setgrid.o
  cdo-Sethalo.o cdo-Setmiss.o cdo-Setpartab.o cdo-Setrcaname.o cdo-Settime.o 
cdo-Setzaxis.o cdo-Shiftxy.o cdo-Showinfo.o cdo-Showattribute.o cdo-Sinfo.o 
cdo-Smooth.o cdo-Sort.o cdo-Sorttimestamp.o cdo-Specinfo.o cdo-Spectral.o 
cdo-Spectrum.o cdo-Split.o cdo-Splitrec.o cdo-Splitsel.o cdo-Splittime.o 
cdo-Splityear.o cdo-Subtrend.o cdo-Tee.o cdo-Templates.o cdo-Test.o cdo-Tests.o 
cdo-Timcount.o cdo-Timcumsum.o cdo-Timpctl.o cdo-Timselpctl.o cdo-Timselstat.o 
cdo-Timsort.o cdo-Timstat.o cdo-Timstat2.o cdo-Timstat3.o cdo-Tinfo.o 
cdo-Tocomplex.o cdo-Transpose.o cdo-Trend.o cdo-Trms.o cdo-Tstepcount.o 
cdo-Vargen.o cdo-Varrms.o cdo-Vertintml.o cdo-Vertintap.o cdo-Vertstat.o 
cdo-Vertcum.o cdo-Vertwind.o cdo-Verifygrid.o cdo-Wct.o cdo-Wind.o 
cdo-WindTrans.o cdo-Writegrid.o cdo-Writerandom.o cdo-XTimstat.o cdo-YAR.o 
cdo-Yearmonstat.o cdo-Ydayarith.o cdo-Ydaypctl.o cdo-Ydaystat.o cdo-Ydrunpctl.o 
cdo-Ydrunstat.o cdo-Yhourarith.o cdo-Yhourstat.o cdo-Ymonarith.o cdo-Ymonpctl.o 
cdo-Ymonstat.o cdo-Yse
 aspctl.o cdo-Yseasstat.o cdo-Zonstat.o cdo-Magplot.o cdo-Magvector.o 
cdo-Maggraph.o cdo-template_parser.o cdo-results_template_parser.o 
cdo-magics_template_parser.o cdo-StringUtilities.o cdo-CdoMagicsMapper.o  
-L/usr/lib -L/usr/lib/i386-linux-gnu/hdf5/serial/lib -Wl,--as-needed 
./.libs/libcdo.a ../libcdi/src/.libs/libcdi.so -lMagPlus 
/usr/lib/i386-linux-gnu/libproj.so -lfftw3 -leccodes -ludunits2 -lnetcdf 
-lhdf5_hl -lhdf5 -lsz -lm -ljpeg -lz /usr/lib/i386-linux-gnu/libcurl-gnutls.so 
-pthread -fopenmp
cdo-Gradsdes.o: In function `Gradsdes(void*)':
./src/Gradsdes.cc:1319: undefined reference to `pstreamInqGRIBinfo(int, int*, 
float*, long long*)'
./.libs/libcdo.a(libcdo_la-pstream.o): In function 
`pstreamCloseChildStream(pstream_t*)':
./src/pstream.cc:936: undefined reference to `processAddNvals(long)'
./.libs/libcdo.a(libcdo_la-pstream.o): In function `pstream_t::close()':
./src/pstream.cc:1002: undefined reference to `processAddNvals(long)'
collect2: error: ld returned 1 exit status

Bug#877341: marked as done (libapache2-mod-md: Doesn't work yet: "AH02572: Failed to configure at least one certificate and key" (require a patched version of apache2))

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 15:21:03 +
with message-id 
and subject line Bug#877341: fixed in libapache2-mod-md 1.0.1-1
has caused the Debian Bug report #877341,
regarding libapache2-mod-md: Doesn't work yet: "AH02572: Failed to configure at 
least one certificate and key" (require a patched version of apache2)
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.)


-- 
877341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-md
Version: 0.9.0-1
Severity: grave

Dear Ondřej,

I've installed libapache2-mod-md on a machine (Raspberry Pi) running
Debian Unstable where apache2 was already installed.

I've disabled all previous site configurations and wrote a new site
configuration from scratch and only enabled that site:

---8<---
ServerAdmin a...@deuxchevaux.org
ServerName ….deuxchevaux.org
ManagedDomain ….deuxchevaux.org

# Requires libapache2-mod-md ≥ 0.9.4
#MDRequireHttps temporary

DocumentRoot /var/www/html

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined


Protocols h2 h2c http/1.1




Protocols h2 http/1.1

SSLEngine on


--->8---

"apache2ctl configtest" said that everything is fine: "Syntax OK".

Upon "service apache2 restart" I though got the following lines in the
error.log:

---8<---
[Sat Sep 30 18:39:45.407137 2017] [ssl:emerg] [pid 4976:tid 1995292672] 
AH02572: Failed to configure at least one certificate and key for 
….deuxchevaux.org:443 
[Sat Sep 30 18:39:45.407356 2017] [ssl:emerg] [pid 4976:tid 1995292672] SSL 
Library Error: error:02001002:system library:fopen:No such file or directory 
(fopen('/etc/apache2/md/domains/….deuxchevaux.org/privkey.pem','r')) 
[Sat Sep 30 18:39:45.407449 2017] [ssl:emerg] [pid 4976:tid 1995292672] SSL 
Library Error: error:2006D080:BIO routines:BIO_new_file:no such file 
[Sat Sep 30 18:39:45.407621 2017] [ssl:emerg] [pid 4976:tid 1995292672] SSL 
Library Error: error:140A80B1:SSL routines:SSL_CTX_check_private_key:no 
certificate assigned 
[Sat Sep 30 18:39:45.407675 2017] [ssl:emerg] [pid 4976:tid 1995292672] 
AH02312: Fatal error initialising mod_ssl, exiting. 
AH00016: Configuration Failed 
--->8---

According to https://github.com/icing/mod_md/wiki/2.4.x-Installation,
this module needs either Apache 2.5/2.6 (not yet in Debian) or a patched
Apache 2.4, otherwise I'd get the AH02572 error message and an SSL
Library Error. Which I got, see above.

So I checked apache2's changelog.Debian.gz for inclusion of such a patch
but found none. I also checked https://bugs.debian.org/src:apache2 for
an according request to include such a patch, but haven't found any
either.

So I assume that libapache2-mod-md is currently not usable at all with
plain Debian unstable.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'buildd-unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 
'buildd-experimental'), (1, 'experimental')
Architecture: armhf (armv7l)

Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libapache2-mod-md depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.27-6
ii  libapr1 1.6.2-1
ii  libaprutil1 1.6.0-2
ii  libc6   2.24-17
ii  libcurl3-gnutls 7.55.1-1
ii  libjansson4 2.10-1
ii  libssl1.1   1.1.0f-5

libapache2-mod-md recommends no packages.

libapache2-mod-md suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libapache2-mod-md
Source-Version: 1.0.1-1

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated libapache2-mod-md 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 

Bug#879624: xorg: After upgrade to buster: system doesnt start x-server anymore but stop reacting

[olar_epbu]

Package: xorg
Version: 1:7.7+19
Severity: grave
Tags: d-i
Justification: renders package unusable

Dear Maintainer,

After i upgraded my software pacage and the system from stretch to buster I can 
not start the x-server anymore.
When booting in normal mode the system hangs after outputting a few lines about 
an achi operator problem and notifiing me that linux is clear. I can not input 
anything, but the cursor blinks.
When i boot in resque mode, my laptop( x1 carbon) behaves quite normal. I can 
login and connect to internet via cable. But once I enter startx or xinit, the 
computer hangs again. 

Thank you

-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 
[8086:1616] (rev 09)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.13.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
6.4.0 20171010 (Debian 6.4.0-8)) #1 SMP Debian 4.13.4-2 (2017-10-15)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 30821 Oct 11 13:26 /var/log/Xorg.2.log
-rw-r--r-- 1 root root 30824 Oct 20 14:15 /var/log/Xorg.1.log
-rw-r--r-- 1 root root  5765 Oct 20 19:05 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[   699.483] 
X.Org X Server 1.19.5
Release Date: 2017-10-12
[   699.484] X Protocol Version 11, Revision 0
[   699.484] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian
[   699.485] Current Operating System: Linux carbon 4.13.0-1-amd64 #1 SMP 
Debian 4.13.4-2 (2017-10-15) x86_64
[   699.485] Kernel command line: BOOT_IMAGE=/vmlinuz-4.13.0-1-amd64 
root=UUID=c4e5a1a2-ec30-47c7-ba73-ea995c5804fb ro single
[   699.485] Build Date: 16 October 2017  12:28:38PM
[   699.485] xorg-server 2:1.19.5-1 (https://www.debian.org/support) 
[   699.486] Current version of pixman: 0.34.0
[   699.486]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   699.486] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   699.488] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 20 19:05:31 
2017
[   699.489] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   699.491] (==) No Layout section.  Using the first Screen section.
[   699.491] (==) No screen section available. Using defaults.
[   699.491] (**) |-->Screen "Default Screen Section" (0)
[   699.491] (**) |   |-->Monitor ""
[   699.491] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   699.491] (==) Automatically adding devices
[   699.491] (==) Automatically enabling devices
[   699.491] (==) Automatically adding GPU devices
[   699.492] (==) Max clients allowed: 256, resource mask: 0x1f
[   699.494] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   699.494]Entry deleted from font path.
[   699.496] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   699.496] (==) ModulePath set to "/usr/lib/xorg/modules"
[   699.496] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   699.496] (II) Loader magic: 0x564182b02de0
[   699.496] (II) Module ABI versions:
[   699.496]X.Org ANSI C Emulation: 0.4
[   699.496]X.Org Video Driver: 23.0
[   699.496]X.Org XInput driver : 24.1
[   699.496]X.Org Server Extension : 10.0
[   699.497] (--) using VT number 2

[   699.497] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[   699.497] (II) xfree86: Adding drm device (/dev/dri/card0)
[   699.504] (--) PCI:*(0:0:2:0) 8086:1616:17aa:2227 rev 9, Mem @ 
0xf000/16777216, 0xe000/268435456, I/O @ 0x3000/64, BIOS @ 
0x/131072
[   699.504] (II) LoadModule: "glx"
[   699.506] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   699.515] (II) Module glx: vendor="X.Org Foundation"
[   699.515]compiled for 1.19.5, module version = 1.0.0
[   699.515]ABI class: X.Org Server Extension, version 10.0
[   699.515] (==) Matched modesetting as autoconfigured driver 0
[   699.515] (==) Matched fbdev as autoconfigured driver 1
[   

Bug#879231: security update: ruby2.3

[Antonio Terceiro]

Hi security team,

I have prepared a security update for ruby2.3.

It includes all the pending recent CVE's, plus a fix for a bug that
causes runaway child processes hogging the CPU, noticed at least in
puppet.

The test suite still passes both during build, and under autopkgtest. I
am running these packages on my workstation since yesterday. The patches
are targeted enough that I don't expect any regressions.

As I explained before, unfortunately the patch management for ruby2.3 is
not optimal, so I attach both the debdiff and the individual patches
that I applied to the git repository. The later will make your review
work easier.

You can also inspect the git repository:
https://anonscm.debian.org/cgit/collab-maint/ruby.git/log/?h=debian/stretch
diff --git a/debian/changelog b/debian/changelog
index 068662c7..bad775fd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,24 @@
+ruby2.3 (2.3.3-1+deb9u2) stretch-security; urgency=high
+
+  * asn1: fix out-of-bounds read in decoding constructed objects
+[CVE-2017-14033] (Closes: #875928)
+Original patch by Kazuki Yamaguchi; backported from the standalone openssl package
+  * lib/webrick/log.rb: sanitize any type of logs
+[CVE-2017-10784] (Closes: #875931)
+Original patch by Yusuke Endoh; backported to Ruby 2.3 by Usaku NAKAMURA
+  * fix Buffer underrun vulnerability in Kernel.sprintf
+[CVE-2017-0898] (Closes: #875936)
+Backported to Ruby 2.3 by Usaku NAKAMURA
+  * Whitelist classes and symbols that are in Gem spec YAML
+[CVE-2017-0903] (Closes: #879231)
+Original patch by Aaron Patterson; backported from the standalone Rubygems
+package
+  * thread_pthread.c: do not wakeup inside child processes
+Avoid child Ruby processed being stuck in a busy loop (Closes: #876377)
+Original patch by Eric Wong
+
+ -- Antonio Terceiro   Sun, 22 Oct 2017 12:45:48 -0200
+
 ruby2.3 (2.3.3-1+deb9u1) stretch-security; urgency=high
 
   * Fix arbitrary heap exposure problem in the JSON library (Closes: #873906)
diff --git a/ext/openssl/ossl_asn1.c b/ext/openssl/ossl_asn1.c
index 89da5949..4012 100644
--- a/ext/openssl/ossl_asn1.c
+++ b/ext/openssl/ossl_asn1.c
@@ -870,19 +870,18 @@ int_ossl_asn1_decode0_cons(unsigned char **pp, long max_len, long length,
 {
 VALUE value, asn1data, ary;
 int infinite;
-long off = *offset;
+long available_len, off = *offset;
 
 infinite = (j == 0x21);
 ary = rb_ary_new();
 
-while (length > 0 || infinite) {
+available_len = infinite ? max_len : length;
+while (available_len > 0) {
 	long inner_read = 0;
-	value = ossl_asn1_decode0(pp, max_len, , depth + 1, yield, _read);
+	value = ossl_asn1_decode0(pp, available_len, , depth + 1, yield, _read);
 	*num_read += inner_read;
-	max_len -= inner_read;
+	available_len -= inner_read;
 	rb_ary_push(ary, value);
-	if (length > 0)
-	length -= inner_read;
 
 	if (infinite &&
 	NUM2INT(ossl_asn1_get_tag(value)) == V_ASN1_EOC &&
@@ -973,7 +972,7 @@ ossl_asn1_decode0(unsigned char **pp, long length, long *offset, int depth,
 if(j & V_ASN1_CONSTRUCTED) {
 	*pp += hlen;
 	off += hlen;
-	asn1data = int_ossl_asn1_decode0_cons(pp, length, len, , depth, yield, j, tag, tag_class, _read);
+	asn1data = int_ossl_asn1_decode0_cons(pp, length - hlen, len, , depth, yield, j, tag, tag_class, _read);
 	inner_read += hlen;
 }
 else {
diff --git a/lib/rubygems.rb b/lib/rubygems.rb
index 9c0219ce..3528a15f 100644
--- a/lib/rubygems.rb
+++ b/lib/rubygems.rb
@@ -602,7 +602,7 @@ def self.load_yaml
 
 unless test_syck
   begin
-gem 'psych', '>= 1.2.1'
+gem 'psych', '>= 2.0.0'
   rescue Gem::LoadError
 # It's OK if the user does not have the psych gem installed.  We will
 # attempt to require the stdlib version
@@ -626,6 +626,7 @@ def self.load_yaml
 end
 
 require 'yaml'
+require 'rubygems/safe_yaml'
 
 # If we're supposed to be using syck, then we may have to force
 # activate it via the YAML::ENGINE API.
diff --git a/lib/rubygems/config_file.rb b/lib/rubygems/config_file.rb
index de90cbfd..2bcd830f 100644
--- a/lib/rubygems/config_file.rb
+++ b/lib/rubygems/config_file.rb
@@ -332,7 +332,7 @@ def load_file(filename)
 return {} unless filename and File.exist? filename
 
 begin
-  content = YAML.load(File.read(filename))
+  content = Gem::SafeYAML.load(File.read(filename))
   unless content.kind_of? Hash
 warn "Failed to load #{filename} because it doesn't contain valid YAML hash"
 return {}
diff --git a/lib/rubygems/package.rb b/lib/rubygems/package.rb
index 0d9adba2..ab49ea2d 100644
--- a/lib/rubygems/package.rb
+++ b/lib/rubygems/package.rb
@@ -466,7 +466,7 @@ def read_checksums gem
 
 @checksums = gem.seek 'checksums.yaml.gz' do |entry|
   Zlib::GzipReader.wrap entry do |gz_io|
-YAML.load gz_io.read
+Gem::SafeYAML.safe_load gz_io.read
   end
 end
   end
diff --git 

Bug#873088: git-annex security issue backports

[Antoine Beaupré]

On 2017-10-12 20:53:13, Moritz Mühlenhoff wrote:
> On Fri, Sep 29, 2017 at 06:56:32PM +0200, Salvatore Bonaccorso wrote:
>> Hi Antoine,
>> 
>> On Thu, Sep 28, 2017 at 01:53:06PM -0400, Antoine Beaupré wrote:
>> > Hi again,
>> > 
>> > I reached out to joeyh to see how we could backport git-annex security
>> > patches to wheezy. He responded by sharing the attached patch he sent to
>> > the git-annex maintainer that backports the fixes to stretch. I figured
>> > it would be useful for the core secteam to have visibilty on this...
>> > 
>> > He also validated the approach i suggested of "grep for ssh and backport
>> > the SshHost construct" to fix the issue in earlier version.
>> 
>> Thanks. Indeed we were already in contact with Richard.
>> 
>> Richard, friendly ping, did you had a chance to continue working on
>> the jessie- and stretch-security upload?
>
> What's the status?

I'm resuming work on this now, and I'll see how I can backport this to
wheezy, which should helpfully give some help/nudge to the jessie
version as well.

A.

-- 
It is a miracle that curiosity survives formal education
- Albert Einstein

Bug#879384: marked as done (artemis FTBFS with libbatik-java 1.9-3)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 11:33:46 +
with message-id 
and subject line Bug#879384: fixed in artemis 16.0.17+dfsg-3
has caused the Debian Bug report #879384,
regarding artemis FTBFS with libbatik-java 1.9-3
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.)


-- 
879384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: artemis
Version: 16.0.17+dfsg-2
Severity: serious

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

...
/build/1st/artemis-16.0.17+dfsg/uk/ac/sanger/artemis/components/PrintArtemis.java:597:
 error: cannot access Localizable
GenericDOMImplementation.getDOMImplementation();
^
  class file for org.apache.batik.i18n.Localizable not found
/build/1st/artemis-16.0.17+dfsg/uk/ac/sanger/artemis/components/PrintArtemis.java:604:
 error: cannot access XMLConstants
svgG.setFont(Options.getOptions().getFont());
^
  class file for org.apache.batik.util.XMLConstants not found
/build/1st/artemis-16.0.17+dfsg/uk/ac/sanger/artemis/components/ComparatorDialog.java:235:
 warning: '_' used as an identifier
  public void actionPerformed(ActionEvent _) 
  ^
  (use of '_' as an identifier might not be supported in releases after Java SE 
8)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
2 errors
59 warnings
Makefile:48: recipe for target 
'uk/ac/sanger/artemis/MegaBlastComparisonData.class' failed
make[2]: *** [uk/ac/sanger/artemis/MegaBlastComparisonData.class] Error 1
--- End Message ---
--- Begin Message ---
Source: artemis
Source-Version: 16.0.17+dfsg-3

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

Debian distribution maintenance software
pp.
Fabian Klötzl  (supplier of updated artemis 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: Mon, 23 Oct 2017 10:38:42 +0200
Source: artemis
Binary: artemis
Architecture: source all
Version: 16.0.17+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Fabian Klötzl 
Description:
 artemis- genome browser and annotation tool
Closes: 879384
Changes:
 artemis (16.0.17+dfsg-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Steffen Moeller ]
   * debian/upstream/metadata:
 - RRID -> SciCrunch
 - Added ref to OMICtools and bio.tools
 .
   [ Fabian Klötzl ]
   * add batik-all.jar to classpath (Closes: #879384)
 .
   [ Andreas Tille ]
   * Standards-Version: 4.1.1
Checksums-Sha1:
 9158e69f773f6871d8049e3d37b4e5ba0bb6d6ea 2278 artemis_16.0.17+dfsg-3.dsc
 36a3b645e3ff0b28f52553bada3701b51558f752 30056 
artemis_16.0.17+dfsg-3.debian.tar.xz
 fda41de6f3a302a0da95fb02aa7eb4486c323b40 2622352 artemis_16.0.17+dfsg-3_all.deb
 41a009dcf28004fa364dab0302e686fb83316130 13597 
artemis_16.0.17+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 ad35a0f39190e6ca1a984940b61398dd33b794a78c7ec7bbc75907df29c53659 2278 
artemis_16.0.17+dfsg-3.dsc
 30b721f3adb2aca3bb4551af4ee22cb4606c900b0dfff3f19caa2662e0bcf5be 30056 
artemis_16.0.17+dfsg-3.debian.tar.xz
 97e32c326cb44abfb83a275cd2e9bdd61bad91642043bf6bc2bc3e459de97d47 2622352 
artemis_16.0.17+dfsg-3_all.deb
 d7ae26fb9d1a966bfb62878438b79070d36c8b943e8ecbbb28b01f87fdd3ef96 13597 
artemis_16.0.17+dfsg-3_amd64.buildinfo
Files:
 02e3cc9081f4738d463584194164cd78 2278 science optional 
artemis_16.0.17+dfsg-3.dsc
 e479398772fd3ba8f3cd388b085cde31 30056 science optional 
artemis_16.0.17+dfsg-3.debian.tar.xz
 4e9992e6fac1b020cf1db63a7ca77519 2622352 science optional 
artemis_16.0.17+dfsg-3_all.deb
 5f66f78643f2b90fb6416be38a07ebc1 13597 science optional 
artemis_16.0.17+dfsg-3_amd64.buildinfo

-BEGIN 

Bug#879252: marked as done (figtree FTBFS with libbatik-java 1.9-3)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 11:19:17 +
with message-id 
and subject line Bug#879252: fixed in figtree 1.4.3+dfsg-2
has caused the Debian Bug report #879252,
regarding figtree FTBFS with libbatik-java 1.9-3
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.)


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

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

...
  dh_auto_build
ant -Duser.name debian
Buildfile: /build/1st/figtree-1.4.3+dfsg/build.xml

init:
[mkdir] Created dir: /build/1st/figtree-1.4.3+dfsg/dist

compile:
[javac] /build/1st/figtree-1.4.3+dfsg/build.xml:40: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 127 source files to /build/1st/figtree-1.4.3+dfsg/build
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] 
/build/1st/figtree-1.4.3+dfsg/src/figtree/application/FigTreeFrame.java:1279: 
error: cannot access Localizable
[javac] DOMImplementation domImpl = 
GenericDOMImplementation.getDOMImplementation();
[javac] ^
[javac]   class file for org.apache.batik.i18n.Localizable not found
[javac] 
/build/1st/figtree-1.4.3+dfsg/src/figtree/application/FigTreeFrame.java:1286: 
error: cannot access XMLConstants
[javac] Element svgRoot = svgGenerator.getRoot();
[javac]   ^
[javac]   class file for org.apache.batik.util.XMLConstants not found
[javac] Note: 
/build/1st/figtree-1.4.3+dfsg/src/figtree/application/FigTreeFrame.java uses or 
overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 2 errors

BUILD FAILED
/build/1st/figtree-1.4.3+dfsg/build.xml:40: Compile failed; see the compiler 
error output for details.

Total time: 22 seconds
dh_auto_build: ant -Duser.name debian returned exit code 1
debian/rules:12: recipe for target 'binary' failed
make: *** [binary] Error 2
--- End Message ---
--- Begin Message ---
Source: figtree
Source-Version: 1.4.3+dfsg-2

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

Debian distribution maintenance software
pp.
Fabian Klötzl  (supplier of updated figtree 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: Mon, 23 Oct 2017 09:57:37 +0200
Source: figtree
Binary: figtree
Architecture: source all
Version: 1.4.3+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Fabian Klötzl 
Description:
 figtree- graphical phylogenetic tree viewer
Closes: 879252
Changes:
 figtree (1.4.3+dfsg-2) unstable; urgency=medium
 .
   * Team upload
 .
   [ Fabian Klötzl ]
   * fixed my own mail address. ☺
   * added patch to include batik-all.jar in classpath (Closes: #879252)
   * bump policy to 4.1.1 (no changes needed)
 .
   [ Steffen Moeller ]
   * debian/upstream/metadata: Added references to registries
 .
   [ Andreas Tille ]
   * Exclude pre-releases from watch file
Checksums-Sha1:
 3db288425d2574b7c65d6770445095e9683c92ad 2363 figtree_1.4.3+dfsg-2.dsc
 d77cc61f1f8e1946d3e938f396e7b34dbea72638 13476 
figtree_1.4.3+dfsg-2.debian.tar.xz
 873dd99271a583b4c0fa06d642e7fb45aaa75962 953624 figtree_1.4.3+dfsg-2_all.deb
 f73596456fa553ceb9bea80aede5c82e158d83f5 12691 
figtree_1.4.3+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 1a7341ddbe4c9e8e544dd3c96978ee75fe7d251a74b640e01ce40cdf977af87c 2363 
figtree_1.4.3+dfsg-2.dsc
 583fa8e7f5c9d69b7e21dc5f5c6149e0ce0b4724e4771868ddc4659b89163416 

Bug#879487: marked as done (cgview FTBFS with libbatik-java 1.9-3)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 11:19:06 +
with message-id 
and subject line Bug#879487: fixed in cgview 0.0.20100111-3
has caused the Debian Bug report #879487,
regarding cgview FTBFS with libbatik-java 1.9-3
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.)


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

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

...
  debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/cgview-0.0.20100111'
cd src && \
cp -a ca/ualberta/stothard/cgview/includes . && \
javac -classpath 
/usr/share/java/batik-awt-util.jar:/usr/share/java/batik-dom.jar:/usr/share/java/batik-svggen.jar:/usr/share/java/batik-util.jar:/usr/share/java/batik-xml.jar:/usr/share/java/commons-lang.jar:/usr/share/java/jargs.jar:/usr/share/java/xercesImpl.jar
 ca/ualberta/stothard/cgview/*.java && \
jar -cmf ../manifestinfo cgview.jar ca/ualberta/stothard/cgview/*.class 
includes && \
rm -rf includes
ca/ualberta/stothard/cgview/CgviewIO.java:156: error: cannot access Localizable
DOMImplementation domImpl = 
GenericDOMImplementation.getDOMImplementation();
^
  class file for org.apache.batik.i18n.Localizable not found
ca/ualberta/stothard/cgview/CgviewIO.java:184: error: cannot access XMLConstants
Element root = graphics2D.getRoot();
 ^
  class file for org.apache.batik.util.XMLConstants not found
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
2 errors
debian/rules:21: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: cgview
Source-Version: 0.0.20100111-3

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

Debian distribution maintenance software
pp.
Fabian Klötzl  (supplier of updated cgview 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: Mon, 23 Oct 2017 10:38:42 +0200
Source: cgview
Binary: cgview
Architecture: source amd64
Version: 0.0.20100111-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Fabian Klötzl 
Description:
 cgview - Circular Genome Viewer
Closes: 879487
Changes:
 cgview (0.0.20100111-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Fabian Klötzl ]
   * add batik-all.jar to classpath (Closes: #879487)
   * bump policy version to 4.1.1 (no changes)
 .
   [ Andreas Tille ]
   * d/rules: do not parse d/changelog
Checksums-Sha1:
 d7cbc84afafe49eb1229332785e7e237f3c5c55a 2083 cgview_0.0.20100111-3.dsc
 9822dd87abaeab66492ca2926d3348bd6a994732 7708 
cgview_0.0.20100111-3.debian.tar.xz
 86eea15234d71bfaa8ec9c3123eb574a628d1319 11808 
cgview_0.0.20100111-3_amd64.buildinfo
 9ad267aa5aca2d48c2ef8d9e265c0595646c6b28 586380 cgview_0.0.20100111-3_amd64.deb
Checksums-Sha256:
 76fc403acfb1ad785e954d779534ff622e6191893deaae1961bc94c8624101d8 2083 
cgview_0.0.20100111-3.dsc
 855dc64e7f8ebba523f9313caae01bdcc7d58bf79fa910ed6da949d9ca40c87e 7708 
cgview_0.0.20100111-3.debian.tar.xz
 06edeb5e532a25286be4b1b5f9e025d8a001b663728a6ff111e7d6980f5a20ea 11808 
cgview_0.0.20100111-3_amd64.buildinfo
 ededaf12e16db183b28990d548a237543a5328adc1571e55c97b1514dbfa3566 586380 
cgview_0.0.20100111-3_amd64.deb
Files:
 1eb142da4afc2c1941ab58bf2fb5e6e2 2083 science optional 
cgview_0.0.20100111-3.dsc
 71c405b9c0a48ca44bb050c3d2385203 7708 science optional 
cgview_0.0.20100111-3.debian.tar.xz
 9064d7f62476836730f9f3185fef2d96 11808 science optional 

Processed: Re: bind9: CVE-2017-3142 CVE-2017-3143

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1:9.10.6+dfsg-1
Bug #866564 {Done: Salvatore Bonaccorso } [src:bind9] bind9: 
CVE-2017-3142 CVE-2017-3143
Marked as fixed in versions bind9/1:9.10.6+dfsg-1.

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

Bug#866564: bind9: CVE-2017-3142 CVE-2017-3143

[Bernhard Schmidt]

Control: fixed -1 1:9.10.6+dfsg-1

Fixed upstream

--- 9.10.6b1 released ---

4643.   [security]  An error in TSIG handling could permit
unauthorized
zone transfers or zone updates. (CVE-2017-3142)
(CVE-2017-3143) [RT #45383]


signature.asc
Description: PGP signature

Processed: Re: bind9: CVE-2017-3137: A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 bind9/1:9.10.6+dfsg-1
Bug #860225 {Done: Salvatore Bonaccorso } [src:bind9] bind9: 
CVE-2017-3137: A response packet can cause a resolver to terminate when 
processing an answer containing a CNAME or DNAME
Marked as fixed in versions bind9/1:9.10.6+dfsg-1.

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

Bug#860225: bind9: CVE-2017-3137: A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME

[Bernhard Schmidt]

Control: fixed -1 bind9/1:9.10.6+dfsg-1

Fixed upstream

--- 9.10.5rc2 released ---

4578.   [security]  Some chaining (CNAME or DNAME) responses to
upstream
queries could trigger assertion failures.
(CVE-2017-3137) [RT #44734]


signature.asc
Description: PGP signature

Bug#778720: bind9: hangs / crashes on mips after some time

[Bernhard Schmidt]

Control: fixed -1 1:9.10.6+dfsg-1

This has been fixed upstream

--- 9.10.5b1 released ---
[...]
4414.   [bug]   Corrected a bug in the MIPS implementation of
isc_atomic_xadd(). [RT #41965]


signature.asc
Description: PGP signature

Processed: Re: bind9: hangs / crashes on mips after some time

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1:9.10.6+dfsg-1
Bug #778720 {Done: James Cowgill } [bind9] bind9: hangs / 
crashes on mips after some time
Marked as fixed in versions bind9/1:9.10.6+dfsg-1.

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

Processed: severity of 879268 is serious

[Debian Bug Tracking System]

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

> severity 879268 serious
Bug #879268 [btrbk] btrbk: Failed to parse subvolume list
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#877035: Same here

[Mario Lang]

I am seeing these problems as well.
Basically, mpsyt is totally unusable to me, since it backtraces on more
or less every search and play attempt.  Trying to play crashes mpsyt
totally.

-- 
AR Mario Lang   Phone: +43 316 873 6897
Graz University of Technology  Mobile: +43 664 60 873 6897
IT-Services for research and teaching   Email: ml...@tugraz.at
Steyrergasse 30/1, 8010 Graz, Austriawww.zid.tugraz.at

Bug#878817: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#878817: luajit: Please drop mips64el again)

[James Cowgill]

Control: forwarded -1 https://github.com/LuaJIT/LuaJIT/pull/362
Control: tags -1 patch

Hi,

On Fri, 20 Oct 2017 16:23:18 +0300 Adrian Bunk  wrote:
> Control: reopen -1
> 
> 16:20 < jcowgill> bunk, LocutusOfBorg: i have a patch for luajit which fixes 
> neovim - i haven't tested it on any other lua code yet 
>   though
> 16:21 < bunk> jcowgill: so that's actually a luajit bug?
> 16:21 < jcowgill> bunk: yes it's a jit miscompile

I've submitted my fix in the above PR. It has some gory details of how
it causes the segfault in neovim.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#878817 closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#878817: luajit: Please drop mips64el again)

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/LuaJIT/LuaJIT/pull/362
Bug #878817 [src:luajit] luajit: jit miscompile on mips64el
Set Bug forwarded-to-address to 'https://github.com/LuaJIT/LuaJIT/pull/362'.
> tags -1 patch
Bug #878817 [src:luajit] luajit: jit miscompile on mips64el
Added tag(s) patch.

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

Processed: Re: Bug#877310: nbdkit FTBFS on armhf/i386: FAIL: test-socket-activation

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.1.16-1
Bug #877310 [src:nbdkit] nbdkit FTBFS on armhf/i386: FAIL: 
test-socket-activation
Marked as fixed in versions nbdkit/1.1.16-1.

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

Bug#877310: nbdkit FTBFS on armhf/i386: FAIL: test-socket-activation

[Hilko Bengen]

Control: fixed -1 1.1.16-1

Looks like the problem no longer occurs with the latest upload.

Cheers,
-Hilko

Bug#877314: marked as done (ruby-premailer FTBFS and Debci failure: test failure)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 08:49:40 +
with message-id 
and subject line Bug#877314: fixed in ruby-premailer 1.8.6-2
has caused the Debian Bug report #877314,
regarding ruby-premailer FTBFS and Debci failure: test failure
to be marked as done.

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

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


-- 
877314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-premailer
Version: 1.8.6-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes ruby-premailer FTBFS and Debci fail:

https://ci.debian.net/packages/r/ruby-premailer/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-premailer.html

...
Loaded suite /usr/lib/ruby/vendor_ruby/rake/rake_test_loader
Started
Premailer::TestCase: 
  default_test: .: (0.000564)
  TestAdapter: 
test_adapters_are_findable_by_class:
/build/1st/ruby-premailer-1.8.6/lib/premailer/adapter/hpricot.rb:40: warning: 
character class has duplicated range: /\A\#([\w_\-]+)\Z/
/build/1st/ruby-premailer-1.8.6/lib/premailer/adapter/hpricot.rb:71: warning: 
character class has duplicated range: /\[SPEC\=([\d]+)\[(.[^\]\]]*)\]\]/
/usr/lib/ruby/vendor_ruby/hpricot/traverse.rb:230: warning: assigned but unused 
variable - i
/usr/lib/ruby/vendor_ruby/hpricot/traverse.rb:297: warning: assigned but unused 
variable - oop
/usr/lib/ruby/vendor_ruby/hpricot/traverse.rb:615: warning: assigned but unused 
variable - links
/usr/lib/ruby/vendor_ruby/hpricot/elements.rb:490: warning: assigned but unused 
variable - idx
.: (0.092552)
test_adapters_are_findable_by_symbol:   .: (0.000405)
test_default_to_best_available: 
/build/1st/ruby-premailer-1.8.6/lib/premailer/adapter.rb:21: warning: instance 
variable @use not initialized
.: (0.001250)
test_raises_argument_error: .: (0.000381)
test_settable_via_symbol:   .: (0.001634)
  TestHtmlToPlainText: 
test_headings:  .: (0.008737)
test_img_alt_tags:  .: (0.003714)
test_line_breaks:   .: (0.001862)
test_links: .: (0.010979)
test_links_within_headings: .: (0.001138)
test_lists: .: (0.010320)
test_multiple_links_per_line:   .: (0.000961)
test_paragraphs_and_breaks: .: (0.003593)
test_specialchars:  .: (0.001002)
test_stripping_html:.: (0.000771)
test_stripping_ignored_blocks:  
/build/1st/ruby-premailer-1.8.6/lib/premailer/adapter/hpricot.rb:170: warning: 
instance variable @html_encoding not initialized
.: (0.009234)
test_stripping_whitespace:  .: (0.003730)
test_to_plain_text_with_body:   
/build/1st/ruby-premailer-1.8.6/lib/premailer/adapter/hpricot.rb:170: warning: 
instance variable @html_encoding not initialized
.: (0.008706)
test_to_plain_text_with_fragment:   
/build/1st/ruby-premailer-1.8.6/lib/premailer/adapter/hpricot.rb:170: warning: 
instance variable @html_encoding not initialized
.: (0.008723)
test_to_plain_text_with_malformed_body: 
/build/1st/ruby-premailer-1.8.6/lib/premailer/adapter/hpricot.rb:170: warning: 
instance variable @html_encoding not initialized
.: (0.008459)
test_wrapping_lines:.: (0.001104)
test_wrapping_spans:
/build/1st/ruby-premailer-1.8.6/lib/premailer/adapter/hpricot.rb:170: warning: 
instance variable @html_encoding not initialized
.: (0.008530)
  TestLinks: 
test_appending_link_query_string:   .: (0.052149)
test_convertable_inline_links:  .: (0.017419)
test_empty_query_string:.: (0.012961)
test_non_convertable_inline_links:  .: (0.020109)
test_preserving_links:  .: (0.023632)
test_resolving_urls_from_html_string:   .: (0.000492)
test_resolving_urls_from_string:.: (0.001513)
test_resolving_urls_from_uri:   .: (0.001278)
test_resolving_urls_in_doc: 

Bug#857148: marked as done (pki-tools: broken symlinks: /usr/bin/KRATool -> DRMTool, /usr/share/pki/java-tools/KRATool.cfg -> DRMTool.cfg)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 11:38:25 +0300
with message-id <605cbad7-40de-0e29-8dd6-f1212af40...@debian.org>
and subject line Re: [Pkg-freeipa-devel] Bug#857148: pki-tools: broken 
symlinks: /usr/bin/KRATool -> DRMTool, /usr/share/pki/java-tools/KRATool.cfg -> 
DRMTool.cfg
has caused the Debian Bug report #857148,
regarding pki-tools: broken symlinks: /usr/bin/KRATool -> DRMTool, 
/usr/share/pki/java-tools/KRATool.cfg -> DRMTool.cfg
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.)


-- 
857148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pki-tools
Version: 10.3.5-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m38.4s ERROR: FAIL: Broken symlinks:
  /usr/share/pki/java-tools/KRATool.cfg -> DRMTool.cfg
  /usr/bin/KRATool -> DRMTool

Files called DRMTool or DRMTool.cfg do not seem to exist in any
package in Debian unstable.


cheers,

Andreas


pki-tools_10.3.5-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
fixed 857148 10.3.5+12-4
thanks

On 08.03.2017 14:44, Andreas Beckmann wrote:
> Package: pki-tools
> Version: 10.3.5-6
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
> 
>>From the attached log (scroll to the bottom...):
> 
> 0m38.4s ERROR: FAIL: Broken symlinks:
>   /usr/share/pki/java-tools/KRATool.cfg -> DRMTool.cfg
>   /usr/bin/KRATool -> DRMTool
> 
> Files called DRMTool or DRMTool.cfg do not seem to exist in any
> package in Debian unstable.

This was actually fixed in 10.3.5+12-4 which still FTBFS'd and tried to
close the wrong bug


-- 
t--- End Message ---

Processed: Bug#877314 marked as pending

[Debian Bug Tracking System]

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

> tag 877314 pending
Bug #877314 [src:ruby-premailer] ruby-premailer FTBFS and Debci failure: test 
failure
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#877314: marked as pending

[Pirate Praveen]

tag 877314 pending
thanks

Hello,

Bug #877314 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-premailer.git/commit/?id=8956f61

---
commit 8956f61ac7bf00f93884c63c4b9e2a1c44744590
Author: Pirate Praveen 
Date:   Mon Oct 23 13:40:29 2017 +0530

update changelog

diff --git a/debian/changelog b/debian/changelog
index 8401145..268c0d0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+ruby-premailer (1.8.6-2) unstable; urgency=medium
+
+  * Team Upload
+  * Disable failing tests (they are unmaintained upstream) (Closes: #877314)
+  * Bump standards version to 4.1.1
+
+ -- Pirate Praveen   Mon, 23 Oct 2017 13:40:11 +0530
+
 ruby-premailer (1.8.6-1) unstable; urgency=medium
 
   * Initial release (Closes: #820924)

Processed: bug 877314 is forwarded to https://github.com/premailer/premailer/issues/352

[Debian Bug Tracking System]

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

> forwarded 877314 https://github.com/premailer/premailer/issues/352
Bug #877314 [src:ruby-premailer] ruby-premailer FTBFS and Debci failure: test 
failure
Set Bug forwarded-to-address to 
'https://github.com/premailer/premailer/issues/352'.
> thanks
Stopping processing here.

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

Bug#878498: snakemake is marked for autoremoval from testing

[Andreas Tille]

Hi folks,

does somebody care about this issue?

Kind regards

   Andreas.

- Forwarded message from Debian testing autoremoval watch 
 -

Date: Sun, 22 Oct 2017 04:39:05 +
From: Debian testing autoremoval watch 
To: snakem...@packages.debian.org
Subject: snakemake is marked for autoremoval from testing

snakemake 3.10.0-1 is marked for autoremoval from testing on 2017-11-12

It is affected by these RC bugs:
878498: snakemake: snakemake FTBFS with Python 3.6 as default


___
Debian-med-packaging mailing list
debian-med-packag...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging


- End forwarded message -

-- 
http://fam-tille.de

Processed: Re: [pkg-apparmor] Bug#878203: Bug#878203: AA breaks libvirt when running with kernel 4.13

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libvirt-daemon-system
Bug #878203 [apparmor] AA breaks libvirt when running with kernel 4.13
Bug reassigned from package 'apparmor' to 'libvirt-daemon-system'.
No longer marked as found in versions apparmor/2.11.0-11.
Ignoring request to alter fixed versions of bug #878203 to the same values 
previously set
> retitle -1 AppArmor blocks QEMU guests access to /proc/*/cmdline
Bug #878203 [libvirt-daemon-system] AA breaks libvirt when running with kernel 
4.13
Changed Bug title to 'AppArmor blocks QEMU guests access to /proc/*/cmdline' 
from 'AA breaks libvirt when running with kernel 4.13'.
> found -1 3.8.0-3
Bug #878203 [libvirt-daemon-system] AppArmor blocks QEMU guests access to 
/proc/*/cmdline
Marked as found in versions libvirt/3.8.0-3.
> severity -1 normal
Bug #878203 [libvirt-daemon-system] AppArmor blocks QEMU guests access to 
/proc/*/cmdline
Severity set to 'normal' from 'serious'
> tag -1 + upstream
Bug #878203 [libvirt-daemon-system] AppArmor blocks QEMU guests access to 
/proc/*/cmdline
Added tag(s) upstream.

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

Bug#878203: [pkg-apparmor] Bug#878203: Bug#878203: AA breaks libvirt when running with kernel 4.13

[intrigeri]

Control: reassign -1 libvirt-daemon-system
Control: retitle -1 AppArmor blocks QEMU guests access to /proc/*/cmdline
Control: found -1 3.8.0-3
Control: severity -1 normal
Control: tag -1 + upstream

Hi Michael, Guido & others,

first of all, thanks a lot for trying AppArmor and reporting bugs,
much appreciated :)

I'm sorry you've hit issues caused by new AppArmor features landing in
Linux mainline (which is very good news in itself but we've failed to
get ready for that in Debian). I have designed a plan to avoid such
situations in the future: #879584 and #879585.

Michael Biebl:
> Updating libvirt to 3.8.0-1 from experimental fixed the immediate issue
> for me, i.e. the libvirt instances start again.

… and this is now fixed in sid too. Kudos to Guido for being so
proactive both to fix such issues in libvirt upstream and to upload
them to Debian — you rock!

> I'm not sure whether to merge these two bug reports now, or we keep this
> one open and deal with the remaining denial(s) (the severity should
> probably be downgraded in this case as it doesn't seem to cause any
> noticeable issues).

> After updating to libvirt 3.8.0-1 I still the get following DENIAL when
> shutting down a libvirt/KVM instance:

>> 2017-10-11T14:43:54.683220+02:00 pluto kernel: [  355.112941] audit:
> type=1400 audit(1507725834.681:55): apparmor="DENIED" operation="open"
> profile="libvirt-4e5a8920-a2a1-4c6b-b7f1-528c20878cdd"
> name="/proc/684/cmdline" pid=3154 comm="qemu-system-x86"
> requested_mask="r" denied_mask="r" fsuid=114 ouid=0

I'm hereby doing the latter, i.e. re-purposing this duplicate bug
report into one that tracks this noisy denial.

@Guido: I've not noticed any breakage caused by AppArmor blocking QEMU
access to /proc/*/cmdline. Grepping the QEMU source code for "cmdline"
outputs too many hits for a non-C person like me to investigate, so
I am really clueless wrt. what the potential problems of this denial
could be. Shall we silence the denial or allow it (possibly prefixed
with "owner" to avoid increasing the attack surface too much)? Once we
reach a conclusion here I'm happy to send a patch upstream.

Cheers,
-- 
intrigeri

Bug#853585: marked as done (opal: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 23 Oct 2017 06:18:56 +
with message-id 
and subject line Bug#853585: fixed in opal 3.10.10~dfsg2-2.1
has caused the Debian Bug report #853585,
regarding opal: ftbfs with GCC-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.)


-- 
853585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:opal
Version: 3.10.10~dfsg2-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/opal_3.10.10~dfsg2-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
 from h263-1998.h:52,
 from h263-1998.cxx:50:
/usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:2808:9: note: declared here
 int rtp_payload_size;   /* The size of the RTP payload: the coder will  */
 ^~~~
h263-1998.cxx:596:14: warning: 'AVCodecContext::rtp_callback' is deprecated 
[-Wdeprecated-declarations]
   m_context->rtp_callback = _RFC2190_EncoderContext::RTPCallBack;
  ^~~~
In file included from ../common/ffmpeg.h:49:0,
 from h263-1998.h:52,
 from h263-1998.cxx:50:
/usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:2802:87: note: declared here
 void (*rtp_callback)(struct AVCodecContext *avctx, void *data, int size, 
int mb_nb);

   ^
h263-1998.cxx:596:14: warning: 'AVCodecContext::rtp_callback' is deprecated 
[-Wdeprecated-declarations]
   m_context->rtp_callback = _RFC2190_EncoderContext::RTPCallBack;
  ^~~~
In file included from ../common/ffmpeg.h:49:0,
 from h263-1998.h:52,
 from h263-1998.cxx:50:
/usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:2802:87: note: declared here
 void (*rtp_callback)(struct AVCodecContext *avctx, void *data, int size, 
int mb_nb);

   ^
h263-1998.cxx:596:14: warning: 'AVCodecContext::rtp_callback' is deprecated 
[-Wdeprecated-declarations]
   m_context->rtp_callback = _RFC2190_EncoderContext::RTPCallBack;
  ^~~~
In file included from ../common/ffmpeg.h:49:0,
 from h263-1998.h:52,
 from h263-1998.cxx:50:
/usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:2802:87: note: declared here
 void (*rtp_callback)(struct AVCodecContext *avctx, void *data, int size, 
int mb_nb);

   ^
make[5]: Leaving directory '/<>/plugins/video/H.263-1998'
Makefile:6: recipe for target 'all' failed
make[4]: *** [all] Error 2
make[4]: Leaving directory '/<>/plugins'
Makefile:578: recipe for target 'subdirs' failed
make[3]: *** [subdirs] Error 2
make[3]: *** Waiting for unfinished jobs
make[3]: Leaving directory '/<>'
Makefile:728: recipe for target 'opt' failed
make[2]: *** [opt] Error 2
make[2]: Leaving directory '/<>'
dh_auto_build: make -j64 PKG_CONFIG_PATH=/<>/samples VERBOSE=1 opt 
docs returned exit code 2
debian/rules:25: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:18: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin