Bug#818335: Cookie-Monster only works with the first opened page in new firefox

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: xul-ext-cookie-monster
Version: 1.3.0.0-1
Severity: grave

With new firefox-esr, nearly everything is broken. But as firefox guys
claim that this is not their problem then the problem of the addon,
there is no way than to report it to the addon, sorry.

With the new firefox, cookie monster only recognise the first ever open
page after start of firefox. While already configured cookies for other
websites work, it is not possible anymore to configure new cookie
policies for new pages.

Only workaround would be to restart firefox with every single new page
loaded.

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (500, 'testing'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.8 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages xul-ext-cookie-monster depends on:
ii  iceweasel  45.0esr-2

xul-ext-cookie-monster recommends no packages.

xul-ext-cookie-monster suggests no packages.

- -- no debconf information

- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQGcBAEBCgAGBQJW6OWHAAoJEKZ8CrGAGfasZZYL/0uAWwsi9h8rcT+OemqoL9y/
t6I1hpW5vw2u+q0oyIcqNuzPTBDOQwy12h7r+9nMjjH31ZPWwBzXZnUtghkhDMLw
Z6Ff80vDnmlBwHQrC9rQCuyjy1k2V+9kKNbqH7mhIn3j0lkLpw0vvLrx+/GuDAzV
9pk97uxSUzSBgOzIAYaXIn1z5GY3GSfiUJqWu7zZkbFl6OGHAzBBGkJCeSeji0jI
lTkrLsKlLwq2u/e0HK7UmTaJTb2trP3kVpyb+SAPDxce2O+8KzmstJim0XBDd+OZ
/ppBEWlm7jXuzAUNqmmZluw4QV6Q9iq5alX9zt8juyN726crCNULuSZ29JlAdVOk
aZfkcCSRKvJz2rNjs9lUfNNzAAz+uPTc8hsbhgIBcx1AYxAV9t0SufAMmTlUrX0s
BN8WiL9T1FMFOyMyK4Dw8IjYM7ZX1gJSuT6kBu7ds2TBrhKa1vypPJ3j3thSXgbn
2tF0BsNYDzlv+nCvQCzDJ1A3MxHB8pVhsRZD8asC4w==
=sYLm
-END PGP SIGNATURE-

Bug#818143: marked as done (haskell-http2: FTBFS: EncodeSpec.hs:18: uncaught exception: DecodeError (TooLongEos))

[Debian Bug Tracking System]

Your message dated Wed, 16 Mar 2016 04:41:09 +
with message-id 
and subject line Bug#818143: fixed in haskell-http2 1.5.3-2
has caused the Debian Bug report #818143,
regarding haskell-http2: FTBFS: EncodeSpec.hs:18: uncaught exception: 
DecodeError (TooLongEos)
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.)


-- 
818143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-http2
Version: 1.5.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

haskell-http2 fails to build from source in unstable/amd64:

  [..]
  
  Failures:
  
test/HPACK/EncodeSpec.hs:18: 
1) HPACK.Encode, encodeHeader and decodeHeader, works for NaiveH
 uncaught exception: DecodeError (TooLongEos)
  
test/HPACK/EncodeSpec.hs:34: 
2) HPACK.Encode, encodeHeader and decodeHeader, works for StaticH
 expected: True
  but got: False
  
test/HPACK/EncodeSpec.hs:34: 
3) HPACK.Encode, encodeHeader and decodeHeader, works for LinearH
 expected: True
  but got: False
  
  Randomized with seed 1264195451
  
  Finished in 2.7010 seconds
  27 examples, 3 failures
  Test suite spec: FAIL
  Test suite logged to: dist-ghc/test/http2-1.5.2-spec.log
  1 of 2 test suites (1 of 2 test cases) passed.
  /usr/share/cdbs/1/class/hlibrary.mk:154: recipe for target 'check-ghc-stamp' 
failed
  make: *** [check-ghc-stamp] Error 1

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


haskell-http2.1.5.2-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: haskell-http2
Source-Version: 1.5.3-2

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

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated haskell-http2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Mar 2016 00:13:10 -0400
Source: haskell-http2
Binary: libghc-http2-dev libghc-http2-prof libghc-http2-doc
Architecture: source
Version: 1.5.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Clint Adams 
Description:
 libghc-http2-dev - ${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-http2-doc - ${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-http2-prof - ${haskell:ShortDescription}${haskell:ShortBlurb}
Closes: 818143
Changes:
 haskell-http2 (1.5.3-2) unstable; urgency=medium
 .
   * Upstream patch to stop using memcpy.  closes: #818143.
Checksums-Sha1:
 86015beeb9b21395b7fdd29104ec5ce25cd9296d 2711 haskell-http2_1.5.3-2.dsc
 446bf063d6e0a4fc206f4642c94f28d4477ac521 5141896 
haskell-http2_1.5.3.orig.tar.gz
 d56ddb94d5e937009e067e9ee7188333163fa76d 3764 
haskell-http2_1.5.3-2.debian.tar.xz
Checksums-Sha256:
 e7a26c9e94996faac6f9d781bc1ac124faeec38ad23e0e3882d1ca4a0b66c669 2711 
haskell-http2_1.5.3-2.dsc
 78012045a1c149310843cd97e2d6df4ba61391e132caefee6153328bf7643bbd 5141896 
haskell-http2_1.5.3.orig.tar.gz
 fb61cb3da0ea804b41061cf7167c5b903ca6180719c38b43640dc03ba0d05759 3764 
haskell-http2_1.5.3-2.debian.tar.xz
Files:
 ad18780a2f7a13dc38ff6a21b6102571 2711 haskell extra haskell-http2_1.5.3-2.dsc
 211c1375247dc6cd577a069473d1b0a8 5141896 haskell extra 
haskell-http2_1.5.3.orig.tar.gz
 164fb396082903839c711724bf9493ce 3764 haskell extra 
haskell-http2_1.5.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Debian!

iQJ8BAEBCgBmBQJW6N5wXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NTgxRUM4NzQwNTNFNkM4MDc3OTFCOUI1
NTkyMzMxRTE5OUQzOEE4AAoJEFWSMx4ZnTioAZ4QAKtyJptHiexaulbPkuRxT070

Processed: Re: Bug#796226: cat: truncates long lines when input is terminal

[Debian Bug Tracking System]

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

> unarchive 796226
Bug #796226 {Done: Michael Stone } [coreutils] cat: 
truncates long lines when input is terminal
Unarchived Bug 796226
> forwarded 796226 https://bugs.debian.org/797479
Bug #796226 {Done: Michael Stone } [coreutils] cat: 
truncates long lines when input is terminal
Set Bug forwarded-to-address to 'https://bugs.debian.org/797479'.
> archive 796226
Bug #796226 {Done: Michael Stone } [coreutils] cat: 
truncates long lines when input is terminal
archived 796226 to archive/26 (from 796226)
> thanks
Stopping processing here.

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

Bug#818331: aac-tactics: FTBFS: constructor vcons (in type vT) expects 2 arguments

[Martin Michlmayr]

Package: aac-tactics
Version: 0.4-5
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> make[4]: Entering directory '/<>'
> "coqc"  -q -opt -R "." AAC_tactics   AAC
> File "./AAC.v", line 497, characters 8-20:
> Error: The constructor vcons (in type vT) expects 2 arguments.
> Makefile.coq:424: recipe for target 'AAC.vo' failed
> make[4]: *** [AAC.vo] Error 1
> make[4]: Leaving directory '/<>'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#790457: marked as done (FTBFS in unstable due to build-depends on libmysqlclient15-dev)

[Debian Bug Tracking System]

Your message dated Wed, 16 Mar 2016 01:20:16 +
with message-id 
and subject line Bug#790457: fixed in qsf 1.2.7-1.1
has caused the Debian Bug report #790457,
regarding FTBFS in unstable due to build-depends on libmysqlclient15-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.)


-- 
790457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qsf
Version: 1.2.7-1
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient15-dev

This package fails to build in unstable because the build-dependency on
libmysqlclient15-dev cannot be met.  libmysqlclient15-dev used to be
provided by mysql-5.5, but this is no longer the case in version 5.6
(see #790257).

Please update your Build-Depends to libmysqlclient-dev

-- 
Martin Michlmayr
Linux for HP Helion OpenStack, Hewlett-Packard
--- End Message ---
--- Begin Message ---
Source: qsf
Source-Version: 1.2.7-1.1

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

Debian distribution maintenance software
pp.
Lucas Kanashiro  (supplier of updated qsf 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, 13 Mar 2016 12:41:29 -0300
Source: qsf
Binary: qsf
Architecture: source
Version: 1.2.7-1.1
Distribution: unstable
Urgency: medium
Maintainer: Nelson A. de Oliveira 
Changed-By: Lucas Kanashiro 
Description:
 qsf- small and fast Bayesian spam filter
Closes: 790457
Changes:
 qsf (1.2.7-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build dependency on libmysqlclient-dev (Closes: #790457)
   * Update build dependencies
   * Bump debhelper compatibility level to 9
   * Declare compliance with Debian policy 3.9.7
   * Remove Homepage url from long description and put it in your own field
   * Wrap and sort dependencies
   * Update debian/copyright, now it is machine-readable
   * Update Section in debian/doc-base
   * Simplify debian/rules
   * Rewrite debian/watch
   * Rename debian/{doc-base,docs,install,lintian-overrides} to
 debian/qsf.{doc-base,docs,install,lintian-overrides}
Checksums-Sha1:
 1836c106daba9c419ad65e7065adf5b99432adf8 1754 qsf_1.2.7-1.1.dsc
 2b1f82b1e430d20bc4b8724ecffebda32395f5aa 6110 qsf_1.2.7-1.1.diff.gz
Checksums-Sha256:
 803aa4eeac2d62c7e1d63f91c00b11761739baf95ca48c3430faa42b4a460f22 1754 
qsf_1.2.7-1.1.dsc
 8c2111b9453a66f3239ffad06e99ee0e0b1816a532af63e7b473b0cfe5b397dc 6110 
qsf_1.2.7-1.1.diff.gz
Files:
 bef6b16ae1f32feaccc40787312537c7 1754 mail optional qsf_1.2.7-1.1.dsc
 b04795ebc384529c5e7aa001f59afe86 6110 mail optional qsf_1.2.7-1.1.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW6LAkAAoJEFwT1tuTBS4DXEgP/AhbIqSI0NLdlCcNkGOugiYd
B4F33BGuKo9Qbyy1CFB8YYTrZFe8hoc0XunO6hmTqq1fBHqTH2h32fdc83Fky6N7
rpEJbIdMYDL7wXkwAo60L2yfToOlhIknVrKLFS/o0jiWil4KsOIEYQBx/dxCjHMJ
pOHBH8UqOHc+KG/pEtCB3bbRHOg5QUiOAAdPDAbBZ6CAcpsnSlNAJ+cOqvkgpex4
SipXrsqJICBvqEz3Ai5uFS3ymAMlCPXEP9zOWBXJvuAihgX/71pdFQ+3Owzebf9+
kOf+IcRRkIxml7qoQJbKge+tNcwr/HBhpr8+skQjP1g8DRkYfWOonun5vI6olSB1
bssqKNRChTOkpsU3ADsEMFaidbA72pHGMSxGdzaoJx2Mr/Zjc3Y42nBu69Hb8LwD
8TDGR5n4KtUIWd3L6+C7E1mQn2gt9MVdoQJWiNhMhU0jFu1Yei+fOlC4EROJJEyb
S+WjlgcxkBBr32MyVm2VwodbOlF5oHObQ5o9dAB1MC0WKyFq2nxZAOIeXevgd5GP
MefVmxTC3mHvDCii18D5Vd4wQlv0037F3zSHC5tx4i0M4qeBVfblBej18uRqYYkr
xYCPJiMqKALynXD6XXsUU+NfwDxnAf8xay0x6Hz07kA0Hx9cfaDQnUpQstNXk7SF
US8iKeyXjB0Wa9Mkr8Is
=AVcj
-END PGP SIGNATURE End Message ---

Processed: reassign 818330 to src:linux, severity of 818330 is important

[Debian Bug Tracking System]

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

> reassign 818330 src:linux 4.2~rc6-1~exp1
Bug #818330 [linux-source] Kernels since 4.2-rc1 cause hang on Baytrail systems
Bug reassigned from package 'linux-source' to 'src:linux'.
No longer marked as found in versions 4.2rc1+.
Ignoring request to alter fixed versions of bug #818330 to the same values 
previously set
Bug #818330 [src:linux] Kernels since 4.2-rc1 cause hang on Baytrail systems
Marked as found in versions linux/4.2~rc6-1~exp1.
> severity 818330 important
Bug #818330 [src:linux] Kernels since 4.2-rc1 cause hang on Baytrail systems
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#818330: Kernels since 4.2-rc1 cause hang on Baytrail systems

[Justin Parker]

Package: linux-source
Version: 4.2rc1+
Severity: serious
Tags: upstream

Kernels since 4.2-rc1 contain:

[8fb55197e64d5988ec57b54e973daeea72c3f2ff] drm/i915: Agressive downclocking on
Baytrail

which causes hangs on my Bay Trail based Dell 3531.

Launchpad recorded the bug @
https://bugs.launchpad.net/debian/+source/linux/+bug/1531865

A patch was included there but it seems to only be a partial fix. As this bug
affects all non-stable Debian versions I am reporting it here. Please see
https://bugs.launchpad.net/debian/+source/linux/+bug/1531865  for more
information on the problem and the fix.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#818327: missing protoc plugin

[Steinar H. Gunderson]

Package: libgrpc-dev
Version: 0.12.0-1
Severity: grave

Hi,

libgrpc-dev does not include the protoc compiler plugin, and it is not
shipped in any other binary package. This makes it (as far as I can tell)
impossible to actually compile a project in any useful way; even the hello
world projects 
(https://github.com/grpc/grpc/tree/release-0_13/examples/cpp/helloworld)
depend on this, thus the RC severity.

After looking around a bit, it looks like this (and the C++ version of the
shared library) depends on protobuf 3.0.0 (beta) entering Debian, but I cannot
find a bug for that to block this one with.

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

Kernel: Linux 4.4.0 (SMP w/40 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done

[GCS]

On Tue, Mar 15, 2016 at 11:24 PM, Julian Taylor
 wrote:
> On 15.03.2016 22:48, László Böszörményi (GCS) wrote:
>>  This is known to pyzmq upstream[1] for about three years. It happens
>> on Ubuntu, Red Hat, CentOS and with ZeroMQ 4.0.x as well. While
>> timer_create() [4] is in librt, the standard GNU C library, it seems
>> pyzmq miss to link with it on the failing architectures.
[...]
> Are you saying linking against -lrt will fix the tests deadlocking?
>
> I don't quite see the relation between the hanging tests and the linked
> issues.
> The implicit declaration errors have always been there I think but only
> in a configure check so harmless (until now?).
 While I was checking the failing build logs, I see:
build/temp.linux-armv7l-2.7/scratch/tmp/timer_createOfMQXG.o: In
function `main':
timer_createOfMQXG.c:(.text+0x14): undefined reference to `timer_create'
collect2: error: ld returned 1 exit status

It's not just the implicit declaration, but a linker error later. I
can be wrong, but it seems it _may_ cause the test hang as there's no
timer to look for / to wait its expiration. Sorry if it happens in
normal logs as well; will check it tomorrow morning as it's almost
midnight here. :(

Laszlo/GCS

Bug#818318: git: CVE-2016-2324 and CVE-2016-2315 (currently unpublished) server and client RCE, fixed in 2.7.1

[GCS]

On Tue, Mar 15, 2016 at 10:13 PM, Ximin Luo  wrote:
> http://seclists.org/oss-sec/2016/q1/645
>
> Please upload 2.7.1 ASAP.
 Just for the record, it should be 2.7.3 due to an integer overflow
fix[1] (no CVE). On the other hand, CVE-2016-2315 is already fixed in
Stretch and Sid[2] with the 2.7.0 version.

Laszlo/GCS
[1] https://github.com/git/git/commit/13e0b0d3dc76353632dcb0bc63cdf03426154317
[2] https://security-tracker.debian.org/tracker/CVE-2016-2315

Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done

[Julian Taylor]

On 15.03.2016 22:48, László Böszörményi (GCS) wrote:
> On Tue, Mar 15, 2016 at 10:26 AM, Emilio Pozuelo Monfort
>  wrote:
>> On 14/03/16 22:03, Emilio Pozuelo Monfort wrote:
>>> Looks good. No problem and thanks for reacting that fast!
>>
>> I scheduled the binNMUs last night and things are going well. The only issue
>> seems to be pyzmq, see #818265.
>  This is known to pyzmq upstream[1] for about three years. It happens
> on Ubuntu, Red Hat, CentOS and with ZeroMQ 4.0.x as well. While
> timer_create() [4] is in librt, the standard GNU C library, it seems
> pyzmq miss to link with it on the failing architectures. User reports
> says that 'pip install pyzmq --install-option="--zmq=/usr/lib"' forces
> the linking. I don't know how pass it to setup.py (not using pip
> directly) and the path should be multiarch aware for us.
> 
> Hope this helps,
> Laszlo/GCS
> [1] https://github.com/zeromq/pyzmq/issues/391
> [2] https://github.com/zeromq/pyzmq/issues/468
> [3] https://github.com/zeromq/pyzmq/issues/658
> [4] http://man7.org/linux/man-pages/man2/timer_create.2.html
> 

Are you saying linking against -lrt will fix the tests deadlocking?

I don't quite see the relation between the hanging tests and the linked
issues.
The implicit declaration errors have always been there I think but only
in a configure check so harmless (until now?).

Processed: Bug#818295 marked as pending

[Debian Bug Tracking System]

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

> tag 818295 pending
Bug #818295 [src:guitarix] guitarix: Please replace build dependency on 
libwebkit-dev with libwebkitgtk-dev
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#818320: [pkg-go] Bug#818320: golang-golang-x-tools: FTBFS with go 1.6

[Tianon Gravi]

On 15 March 2016 at 15:06, Michael Hudson-Doyle
 wrote:
> (or you can approve my
> request to join pkg-go on alioth :-p)

You're long since approved by now! ;)


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#818320: golang-golang-x-tools: FTBFS with go 1.6

[Michael Hudson-Doyle]

There's a debdiff at
http://people.canonical.com/~mwh/golang-golang-x-tools_0.0~git20151026.0.0f9d71c-2_0.0~git20160315.0.f42ec61-1.diff
which is rather large, or you can grab the new stuff from
https://github.com/mwhudson/golang-go.tools (or you can approve my
request to join pkg-go on alioth :-p)

Cheers,
mwh

On 16 March 2016 at 10:51, Michael Hudson-Doyle
 wrote:
> Source: golang-golang-x-tools
> Version: 1:0.0~git20151026.0.0f9d71c-2
> Severity: serious
> Tags: patch
> Justification: Policy 4.9
>
> Dear Maintainer,
>
> The version of golang/x/tools in the archive currently fails tests with Go 
> 1.6 and fails to build.
>
> Updating to a new upstream snapshot should fix this.
>
> Cheers,
> mwh
>
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers wily-updates
>   APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
> (100, 'wily-backports')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.2.0-30-generic (SMP w/4 CPU cores)
> Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)

Bug#800229: dict-gazetteer2k: Please migrate a supported debhelper compat level

[Logan Rosen]

Package: dict-gazetteer2k
Version: 1.0.0-5.2
Followup-For: Bug #800229
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/rules:
- Remove legacy DH_COMPAT export.
- Use dh_prep instead of dh_clean -k.
- Add recommended build-arch and build-indep targets.
  * debian/compat: Specify compatibility level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Move debhelper build dependency to Build-Depends, as it's used in clean.
- Depend on ${misc:Depends}.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-7-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u dict-gazetteer2k-1.0.0/debian/control dict-gazetteer2k-1.0.0/debian/control
--- dict-gazetteer2k-1.0.0/debian/control
+++ dict-gazetteer2k-1.0.0/debian/control
@@ -2,12 +2,13 @@
 Section: text
 Priority: optional
 Maintainer: John Goerzen 
-Build-Depends-Indep: debhelper (>> 3.0.0), python, miscfiles, python-dictdlib, python-dictclient, dictzip
+Build-Depends: debhelper (>= 9)
+Build-Depends-Indep: python, miscfiles, python-dictdlib, python-dictclient, dictzip
 Standards-Version: 3.5.2
 
 Package: dict-gazetteer2k
 Architecture: all
-Depends: dict-gazetteer2k-places, dict-gazetteer2k-counties, dict-gazetteer2k-zips
+Depends: ${misc:Depends}, dict-gazetteer2k-places, dict-gazetteer2k-counties, dict-gazetteer2k-zips
 Description: Placeholder package to install entire Gazetteer 2000
  This package can be used to ensure that you always have the entire
  set of files comprising the 2000 Gazetteer installed.  You might
@@ -17,6 +18,7 @@
 
 Package: dict-gazetteer2k-places
 Architecture: all
+Depends: ${misc:Depends}
 Suggests: dict, dictd
 Description: Places Database for the 2000 US Gazetteer
  This is a database of (primarily) United States cities using
@@ -33,6 +35,7 @@
 
 Package: dict-gazetteer2k-counties
 Architecture: all
+Depends: ${misc:Depends}
 Suggests: dict, dictd
 Description: Counties Database for the 2000 US Gazetteer
  This is a database of (primarily) United States counties using
@@ -46,6 +49,7 @@
 
 Package: dict-gazetteer2k-zips
 Architecture: all
+Depends: ${misc:Depends}
 Suggests: dict, dictd
 Description: ZIP and ZCTA database for the 2000 US Gazetteer
  This is a database of United States ZIP code information.  It
diff -u dict-gazetteer2k-1.0.0/debian/rules dict-gazetteer2k-1.0.0/debian/rules
--- dict-gazetteer2k-1.0.0/debian/rules
+++ dict-gazetteer2k-1.0.0/debian/rules
@@ -5,9 +5,6 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-# This is the debhelper compatibility version to use.
-export DH_COMPAT=3
-
 PYTHON=python
 BASENAMES=places counties zips
 
@@ -26,7 +23,9 @@
 	touch configure-stamp
 
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 
 build-stamp: configure-stamp 
 	dh_testdir
@@ -56,7 +55,7 @@
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 
 	for FILE in $(BASENAMES); do \
 		cp debian/dirs.tmpl debian/dict-gazetteer2k-$$FILE.dirs; \
only in patch2:
unchanged:
--- dict-gazetteer2k-1.0.0.orig/debian/compat
+++ dict-gazetteer2k-1.0.0/debian/compat
@@ -0,0 +1 @@
+9

Bug#818320: golang-golang-x-tools: FTBFS with go 1.6

[Michael Hudson-Doyle]

Source: golang-golang-x-tools
Version: 1:0.0~git20151026.0.0f9d71c-2
Severity: serious
Tags: patch
Justification: Policy 4.9

Dear Maintainer,

The version of golang/x/tools in the archive currently fails tests with Go 1.6 
and fails to build.

Updating to a new upstream snapshot should fix this.

Cheers,
mwh

-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#818187: zeromq3 migrated without any transition being done

[GCS]

On Tue, Mar 15, 2016 at 10:26 AM, Emilio Pozuelo Monfort
 wrote:
> On 14/03/16 22:03, Emilio Pozuelo Monfort wrote:
>> Looks good. No problem and thanks for reacting that fast!
>
> I scheduled the binNMUs last night and things are going well. The only issue
> seems to be pyzmq, see #818265.
 This is known to pyzmq upstream[1] for about three years. It happens
on Ubuntu, Red Hat, CentOS and with ZeroMQ 4.0.x as well. While
timer_create() [4] is in librt, the standard GNU C library, it seems
pyzmq miss to link with it on the failing architectures. User reports
says that 'pip install pyzmq --install-option="--zmq=/usr/lib"' forces
the linking. I don't know how pass it to setup.py (not using pip
directly) and the path should be multiarch aware for us.

Hope this helps,
Laszlo/GCS
[1] https://github.com/zeromq/pyzmq/issues/391
[2] https://github.com/zeromq/pyzmq/issues/468
[3] https://github.com/zeromq/pyzmq/issues/658
[4] http://man7.org/linux/man-pages/man2/timer_create.2.html

Bug#805195: debdry: FTBFS: ImportError: No module named 'apt_pkg'

[Logan Rosen]

Package: debdry
Version: 0.2.1-1
Followup-For: Bug #805195
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * Build-depend on python3-apt to fix FTBFS with Python 3.5.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-7-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru debdry-0.2.1/debian/control debdry-0.2.1/debian/control
--- debdry-0.2.1/debian/control	2015-07-22 01:33:39.0 -0500
+++ debdry-0.2.1/debian/control	2016-03-15 16:29:04.0 -0500
@@ -1,9 +1,8 @@
 Source: debdry
 Priority: optional
 Section: devel
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Enrico Zini 
-Build-Depends: python3-setuptools, python3-all, debhelper (>= 9), dh-python
+Maintainer: Enrico Zini 
+Build-Depends: python3-setuptools, python3-all, debhelper (>= 9), dh-python, python3-apt
 Standards-Version: 3.9.1
 Vcs-Git: git://anonscm.debian.org/collab-maint/debdry.git
 Vcs-Browser: http://anonscm.debian.org/gitweb?p=collab-maint/debdry.git;a=summary

Bug#818318: git: CVE-2016-2324 and CVE-2016-2315 (currently unpublished) server and client RCE, fixed in 2.7.1

[Ximin Luo]

Package: git
Version: 1:2.7.0-1
Severity: grave
Tags: upstream security
Justification: user security hole

Dear Maintainer,

This was just posted:

http://seclists.org/oss-sec/2016/q1/645

Please upload 2.7.1 ASAP.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (300, 'unstable'), (200, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages git depends on:
ii  git-man   1:2.7.0-1
ii  libc6 2.21-9
ii  libcurl3-gnutls   7.47.0-1
ii  liberror-perl 0.17-1.2
ii  libexpat1 2.1.0-7
ii  libpcre3  2:8.38-3
ii  perl-modules-5.22 [perl-modules]  5.22.1-8
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages git recommends:
ii  less 481-2.1
ii  openssh-client [ssh-client]  1:7.1p2-2
ii  patch2.7.5-1
ii  rsync3.1.1-3

Versions of packages git suggests:
ii  gettext-base 0.19.7-2
ii  git-arch 1:2.7.0-1
ii  git-cvs  1:2.7.0-1
ii  git-daemon-sysvinit  1:2.7.0-1
ii  git-doc  1:2.7.0-1
ii  git-el   1:2.7.0-1
ii  git-email1:2.7.0-1
ii  git-gui  1:2.7.0-1
ii  git-mediawiki1:2.7.0-1
ii  git-svn  1:2.7.0-1
ii  gitk 1:2.7.0-1
ii  gitweb   1:2.7.0-1

-- no debconf information

Bug#817929: mosh and libutempter

[Goffredo Baroncelli]

I am not sure that libutempter0 is the real culprit, however I find a very 
strange behavior:

If I preload libutempter mosh-server didn't crashes. Instead if I run 
mosh-server alone, it crashes:


$ ldd /usr/bin/mosh-server 
linux-vdso.so.1 (0x7ffce553b000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7f8966678000)
libprotobuf.so.9 => /usr/lib/x86_64-linux-gnu/libprotobuf.so.9 
(0x7f896634e000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f896613)
libssl.so.1.0.2 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2 
(0x7f8965ec7000)
libcrypto.so.1.0.2 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2 
(0x7f8965a64000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7f896586)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f8965645000)
--> libutempter.so.0 => /usr/lib/x86_64-linux-gnu/libutempter.so.0 
(0x7f8965442000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f89650be000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f8964dc)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f8964baa000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f8964805000)
/lib64/ld-linux-x86-64.so.2 (0x561792d06000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f8964601000)


$ /usr/bin/mosh-server 

In dmesg I got "mosh-server[8320]: segfault at 0 ip"


Instead if I do

$ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libutempter.so.0 /usr/bin/mosh-server

mosh-server didn't crash...

I am inclined to think that preloading the library I change the library 
arrangement in memory; this could hide/show some wrong memory access.

Any idea how debug this ?

G.Baroncelli

Processed: Re: Bug#818222: libzeromq-perl: uses old libzmq1, should switch to libzmq5

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + upstream
Bug #818222 [libzeromq-perl] libzeromq-perl: uses old libzmq1, should switch to 
libzmq5
Added tag(s) upstream.

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

Bug#818222: libzeromq-perl: uses old libzmq1, should switch to libzmq5

[gregor herrmann]

Control: tag -1 + upstream

On Tue, 15 Mar 2016 11:56:04 +0100, László Böszörményi (GCS) wrote:

> On Mon, Mar 14, 2016 at 10:17 PM, gregor herrmann  wrote:
> > On Mon, 14 Mar 2016 20:46:06 +0100, Emilio Pozuelo Monfort wrote:
> >> Yes. Bumping this to RC so we don't release stretch with it, and opening
> >> bugs for the rdeps.
> >
> > Changing the build dep from libzmq-dev to libzmq5-dev is not enough
> > it seems:
> [...]
>  This is expected. Please note that zeromq is 2.x, while zeromq3 went
> through 3.x -> 4.0.x -> 4.1.x evolution.
> Please ask your upstream to port the code to the latest (4.1) zeromq version.

Thanks for confirming my hunch.
Will forward upstream (who hasn't been very active lately.)


Cheers,
gregor


-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Die Schmetterlinge: Matuska spricht


signature.asc
Description: Digital Signature

Processed: bug 818222 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=113059

[Debian Bug Tracking System]

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

> forwarded 818222 https://rt.cpan.org/Ticket/Display.html?id=113059
Bug #818222 [libzeromq-perl] libzeromq-perl: uses old libzmq1, should switch to 
libzmq5
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=113059'.
> thanks
Stopping processing here.

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

Bug#818000: Configuration files stored in /lib/ufw; FHS violation

[Ben Hutchings]

On Tue, 2016-03-15 at 11:03 -0500, Jamie Strandboge wrote:
> On Sat, 2016-03-12 at 15:30 +, Ben Hutchings wrote:
> > 
> > Package: ufw
> > Version: 0.34-2
> > Severity: serious
> > 
> > Configuration files written by the ufw command (user.rules,
> > user6.rules) must be stored in either /etc (if they are also intended
> > to be directly editable) or /var.
> > 
> > I spent quite some time trying to understand how to transfer my ufw
> > configuration to a new installation; following the FHS would have
> > saved me that.
> > 
> Sorry about that. Actually this has been discussed at great length in the
> upstream bug. Here has been my historical take:
> https://bugs.launchpad.net/ufw/+bug/728128/comments/1

I did understand that using /var potentially introduces a dependency
loop, though I would have thought you could start the daemon with only
statically defined rules and have it load user-defined rules when /var
becomes available.

> That said with 0.35 I finally yielded:
> 
> ufw (0.35) RELEASED; urgency=medium
>  ...
>   * move user[6].rules to /etc/ufw (LP: #728128)
> 
> In other words, this will be fixed in 0.35-1.

Thank you.

Ben.

-- 
Ben Hutchings
Hoare's Law of Large Problems:
Inside every large problem is a small problem struggling to get out.

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

Bug#818308: Bug#818304: tzdata-java: Removal of tzdata-java in tzdata 2016b-1 makes openjdk-7 uninstallable

[Ben Caradoc-Davies]

On 16/03/16 08:46, Aurelien Jarno wrote:

On 2016-03-16 08:02, Ben Caradoc-Davies wrote:

Please restore tzdata-java so that openjdk-7 can be installed on unstable.


We can't do that. The support to build tzdata-java seems to have been
removed from openjdk, that's why we had to stop building it. Anyway it
seems that openjdk-7 will be removed soon given the bugs that have been
opened:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814157
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814159
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814165
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814167
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814174

Now it would be could if openjdk people can actually comment on that.

Aurelien


Thanks, Aurelien. If the OpenJDK team intends the immediate removal of 
openjdk-7 from unstable, that would resolve both #818304 and #818308. I 
did not see anything in transitions. I am not sure how this change is 
announced.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#818308: Bug#818304: tzdata-java: Removal of tzdata-java in tzdata 2016b-1 makes openjdk-7 uninstallable

[Ben Caradoc-Davies]

Also reported for openjdk-7 as #818308 where this bug is grave. I do not 
know how else to use bts to report a normal bug in one package that is 
grave in another. I do not think bugs with different severity can be merged.


--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Processed: reassign and merge with 811368

[Debian Bug Tracking System]

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

> reassign 818301 src:linux 3.16.7-ckt20-1+deb8u2
Bug #818301 [src:python-astropy] python-astropy: FTBFS on mips: test suite 
errors
Bug reassigned from package 'src:python-astropy' to 'src:linux'.
No longer marked as found in versions python-astropy/1.1.2-1.
Ignoring request to alter fixed versions of bug #818301 to the same values 
previously set
Bug #818301 [src:linux] python-astropy: FTBFS on mips: test suite errors
Marked as found in versions linux/3.16.7-ckt20-1+deb8u2.
> affects 818301 + python-astropy
Bug #818301 [src:linux] python-astropy: FTBFS on mips: test suite errors
Ignoring request to set affects of bug 818301 to the same value previously set
> forcemerge 811368 818301
Bug #811368 [src:linux] Illegal instruction on MIPS
Bug #818301 [src:linux] python-astropy: FTBFS on mips: test suite errors
Removed indication that 818301 affects python-astropy
Added indication that 818301 affects python-scipy,src:python-astropy
Added tag(s) pending.
Merged 811368 818301
> thanks
Stopping processing here.

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

Bug#818308: openjdk-7-jre-headless: openjdk-7 uninstallable because tzdata-java removed

[Ben Caradoc-Davies]

Package: openjdk-7-jre-headless
Version: 7u95-2.6.4-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

As reported in #818304, openjdk-7 cannot be installed on unstable because, in
tzdata 2016b, tzdata-java was removed.

Apologies for the duplicate bug report. This is only a normal bug for tzdata
but it needs to be grave for openjdk-7.

Kind regards,
Ben.




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

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

Versions of packages openjdk-7-jre-headless depends on:
ii  ca-certificates-java  20140324
ii  java-common   0.57
ii  libc6 2.22-3
ii  libcups2  2.1.3-3
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6.3-3
ii  libgcc1   1:5.3.1-11
ii  libglib2.0-0  2.46.2-3
ii  libjpeg62-turbo   1:1.4.2-2
ii  libkrb5-3 1.13.2+dfsg-5
ii  liblcms2-22.6-3+b3
ii  libnss3   2:3.23-1
ii  libpcsclite1  1.8.15-1
ii  libpulse0 8.0-1
ii  libsctp1  1.0.16+dfsg-3
ii  libstdc++65.3.1-11
ii  multiarch-support 2.22-3
ii  tzdata-java   2016a-1
ii  util-linux2.27.1-6
ii  zlib1g1:1.2.8.dfsg-2+b1

openjdk-7-jre-headless recommends no packages.

Versions of packages openjdk-7-jre-headless suggests:
ii  fonts-dejavu-extra 2.35-1
pn  fonts-indic
pn  fonts-ipafont-gothic   
pn  fonts-ipafont-mincho   
pn  icedtea-7-jre-jamvm
ii  libnss-mdns0.10-7
pn  sun-java6-fonts
pn  ttf-wqy-microhei | ttf-wqy-zenhei  

-- debconf-show failed

Processed (with 2 errors): reassign and merge with 811368

[Debian Bug Tracking System]

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

> reassign818301 src:linux 3.16.7-ckt20-1+deb8u2
Unknown command or malformed arguments to command.
> affects 818301 + python-astropy
Bug #818301 [src:python-astropy] python-astropy: FTBFS on mips: test suite 
errors
Ignoring request to set affects of bug 818301 to the same value previously set
> forcemerge 811368 818301
Bug #811368 [src:linux] Illegal instruction on MIPS
Unable to merge bugs because:
package of #818301 is 'src:python-astropy' not 'src:linux'
Failed to forcibly merge 811368: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed (with 3 errors): reassign and merge with 811368

[Debian Bug Tracking System]

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

> reassign818301 src:linux *3.16.7-ckt20-1+deb8u2*
Unknown command or malformed arguments to command.
> 
Unknown command or malformed arguments to command.
> affects 818301 + python-astropy
Bug #818301 [src:python-astropy] python-astropy: FTBFS on mips: test suite 
errors
Added indication that 818301 affects python-astropy
> forcemerge 811368 818301
Bug #811368 [src:linux] Illegal instruction on MIPS
Unable to merge bugs because:
package of #818301 is 'src:python-astropy' not 'src:linux'
Failed to forcibly merge 811368: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#814994: marked as done (haskell-stack: FTBFS - build-dep libghc-aeson-dev (<< 0.10) unsatisfiable as 0.10.0.0-3 is current)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2016 18:50:01 +
with message-id 
and subject line Bug#814994: fixed in haskell-stack 1.0.0-1
has caused the Debian Bug report #814994,
regarding haskell-stack: FTBFS - build-dep libghc-aeson-dev (<< 0.10) 
unsatisfiable as 0.10.0.0-3 is current
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.)


-- 
814994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: haskell-stack
Version: 0.1.10.0-1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
 -> Attempting to parse the build-deps
 -> Considering build-dep debhelper (>= 9)
   -> Trying debhelper
 -> Considering build-dep haskell-devscripts (>= 0.9)
   -> Trying haskell-devscripts
 -> Considering build-dep cdbs
   -> Trying cdbs
 -> Considering build-dep ghc
   -> Trying ghc
 -> Considering build-dep ghc-prof
   -> Trying ghc-prof
 -> Considering build-dep libghc-aeson-dev (>= 0.8.0.2)
   -> Trying libghc-aeson-dev
 -> Considering build-dep libghc-aeson-dev (<< 0.10)
  Tried versions: 0.10.0.0-3
   -> Does not satisfy version, not trying
E: Could not satisfy build-dependency.


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


haskell-stack-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: haskell-stack
Source-Version: 1.0.0-1

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

Debian distribution maintenance software
pp.
Sven Bartscher  (supplier of updated 
haskell-stack 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, 15 Mar 2016 17:55:48 +0100
Source: haskell-stack
Binary: haskell-stack
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Sven Bartscher 
Description:
 haskell-stack - ${haskell:ShortDescription}${haskell:ShortBlurb}
Closes: 800067 800068 813844 814994
Changes:
 haskell-stack (1.0.0-1) unstable; urgency=medium
 .
   [ Dmitry Bogatov ]
   * New upstream release
 - Build-Depends on newer version of libghc-aeson-dev (Closes: #814994)
 .
   [ Joachim Breitner ]
   * Install gcc and xz-utils, as suggested by Joey, multiple times
 (Closes: 813844, 800067, 800068)
Checksums-Sha1:
 0c7605f9bc98fc4c4bdb61c6f5319cf8ccc702c4 7130 haskell-stack_1.0.0-1.dsc
 f500f9290e1387c86810837088ed0bd039cbfdee 312194 haskell-stack_1.0.0.orig.tar.gz
 fcafbc7c49ff81ee4e1f08b7d0cbc54ceadd916f 3776 
haskell-stack_1.0.0-1.debian.tar.xz
Checksums-Sha256:
 3bdb079cf17f0ef6bcf46e495ffbe4e5d062e24e71f3b2d116decbe8934382c9 7130 
haskell-stack_1.0.0-1.dsc
 cd2f606d390fe521b6ba0794de87edcba64c4af66856af09594907c2b4f4751d 312194 
haskell-stack_1.0.0.orig.tar.gz
 0f9299129cf15886b6c931f4be8fba04fbe1f698639c431ece252e9083d7883a 3776 
haskell-stack_1.0.0-1.debian.tar.xz
Files:
 aa9a37ba78544fcb6c6090622e57b01d 7130 haskell extra haskell-stack_1.0.0-1.dsc
 7a52e4b935a80c48ddc4d773645cc9fe 312194 haskell extra 
haskell-stack_1.0.0.orig.tar.gz
 a3efdaf30a2652c668eae78c636dd3e5 3776 haskell extra 
haskell-stack_1.0.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Debian!

iQJ7BAEBCgBmBQJW6FhLXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NTgxRUM4NzQwNTNFNkM4MDc3OTFCOUI1
NTkyMzMxRTE5OUQzOEE4AAoJEFWSMx4ZnTiorOMP92B/Jc27Ej4N7+2S0c4TjJ0o
X/Gs3Keg1cq8mUN6MbK8GwS3Nr9/kwRrYPKKFvBdsEtUkAUM9dah65TG7By8Q4E3
TDVxNKr2cnv+Ok6NFgNgfWGO44QfIfOUA9I/8kEGN5/JkVyAF17wAHPegF62+ThB
Rmef6QD47d5ftyabv6qBkTH51Xy8GgBeLfcJg2dWMtp77210aKpao8JykEWOHF0k

Bug#818301: python-astropy: FTBFS on mips: test suite errors

[Emilio Pozuelo Monfort]

Source: python-astropy
Version: 1.1.2-1
Severity: serious

Your package failed to build on mips, see:

https://buildd.debian.org/status/logs.php?pkg=python-astropy=1.1.2-1=mips

Bug#818298: package gpstrans FTBFS on variuos architectures

[Jurica Stanojkovic]

Package: gpstrans
Version: 0.41-5 
Severity: serious
Tags: sid + patch
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch

Hello,
Package gpstrans FTBFS on apha, mips, mips64el, mipsel, powerpc, ppc64, and 
ppc64el
with following error:
getline.c:191:13: error: 'TIOCGETC' undeclared (first use in this function)
   ioctl (0, TIOCGETC, );

Previous version 0.41-4 was successfully built on all previously listed 
architectures.

build logs:
https://buildd.debian.org/status/logs.php?pkg=gpstrans=0.41-5=sid
https://buildd.debian.org/status/logs.php?pkg=gpstrans=0.41-4=sid

Patch 04-fix-makefile.diff has not included POSIX macro for libgetline.a 
library.

I have created and attached a patch resolving this issue.

Patch was tested on MIPS. 
With this patch package was build successfully.

Please include this patch.

Thank you!

Regards,
JuricaDescription: re-enable POSIX macro for libgetline build
 Changes to Makefile's in patch 04-fix-makefile.diff did not include POSIX macro.
 Before gpstrans version 0.41-5 macro was defined in src/getline/Makefile.

Author: Jurica Stanojkovic 

--- gpstrans-0.41.orig/src/Makefile
+++ gpstrans-0.41/src/Makefile
@@ -37,7 +37,7 @@ XFILES	= gps/sendgpsinfo.o gps/dms.o gps
 
 all:	$(OFILES) $(HFILES)
 	@echo "Making all in ./getline"
-	@(cd getline ; make CFLAGS="$(CFLAGS)" libgetline.a)
+	@(cd getline ; make CFLAGS="$(CFLAGS) -DPOSIX" libgetline.a)
 	@echo "Making all in ./gps"
 	@(cd gps  ; make all CC="$(CC)" CFLAGS="$(CFLAGS)")
 	@echo "Making all in ./grid"

Bug#818297: ucommon: FTBFS on release architectures

[Emilio Pozuelo Monfort]

Source: ucommon
Version: 6.6.2-3
Severity: serious

Your package failed to build on mips, powerpc and s390x with failed tests:

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

There's also a kfreebsd-amd64 failure with outdated symbols file.

Cheers,
Emilio

Bug#812087: [pcscd] takes 100 % cpu

[Ludovic Rousseau]

On Mon, 7 Mar 2016 21:14:48 +0100 Philippe Teuwen  wrote:
>
>
> On 03/07/2016 07:34 PM, Ludovic Rousseau wrote:
> > printf("fds: %d %d\n", fds[0].revents, fds[1].revents);
>
> fds: 0 1
> always
>
> I also printed udev_dev from udev_monitor_receive_device()
> it's always null
>
> So we get fds[1].revents but don't get anything from
> udev_monitor_receive_device() so it's looping forever.
>
>
> You may try to trigger the bug from your side:
> It probably requires the same versions as me.
> kernel 4.3.0-1-amd64
> libusb-1.0-0 2:1.0.20-1
> libudev1 229-2
> I've a Yubikey neo-n plugged in.
> I start pcscd.
> I plug a usb hub (or anything else)
> => CPU at 100%

I am using:
$ uname -a
Linux debian 4.3.0-1-amd64 #1 SMP Debian 4.3.5-1 (2016-02-06) x86_64 
GNU/Linux


$ apt-cache policy libusb-1.0-0
libusb-1.0-0:
  Installé : 2:1.0.20-1
  Candidat : 2:1.0.20-1
 Table de version :
 *** 2:1.0.20-1 500
500 http://httpredir.debian.org/debian stretch/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy libudev1
libudev1:
  Installé : 229-2
  Candidat : 229-2
 Table de version :
 *** 229-2 500
500 http://httpredir.debian.org/debian stretch/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy pcscd
pcscd:
  Installé : 1.8.15-1
  Candidat : 1.8.15-1
 Table de version :
 *** 1.8.15-1 500
500 http://httpredir.debian.org/debian stretch/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy libccid
libccid:
  Installé : 1.4.22-1
  Candidat : 1.4.22-1
 Table de version :
 *** 1.4.22-1 500
500 http://httpredir.debian.org/debian stretch/main amd64 Packages
100 /var/lib/dpkg/status

And I can't reproduce the problem :-(

I tried connecting a USB memory, my Android phone, a USB hub but it all 
worked as expected.


That bug is even more strange now.

Maybe enabling libusb debug would help. I will try to document how to do 
that easily.


Bye

--
Dr. Ludovic Rousseau

Bug#818036: "kpartx does not ship multipathd.service but tries to start/stop that service" not fixed in 0.5.0+git1.656f8865-7

[Ritesh Raj Sarraf]

On Tue, 2016-03-15 at 18:18 +0100, Sven Hartge wrote:
> On 15.03.2016 18:16, Ritesh Raj Sarraf wrote:
> 
> > I am not walking away. The failure is 2 folds. If you got hit by
> -6, on
> > your machine the (broken) maintainer script gets installed, which
> you'll
> > have to manually remove.
> 
> No, I do not. It is your job as package maintainer to clean this up.
> You
> broke it, you fix it.

Okay! I'd agree on the last statement. :-)
I'll fix it soon.

For others who get hit, Sven has mentioned the workaround in this bug
report.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Processed (with 1 error): severity of 818293 is serious

[Debian Bug Tracking System]

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

> severity 818293 serious
Bug #818293 [kpartx] kpartx: cannot be installed
Severity set to 'serious' from 'grave'
> merge 818036 818293
Bug #818036 {Done: Ritesh Raj Sarraf } [kpartx] kpartx does 
not ship multipathd.service but tries to start/stop that service
Unable to merge bugs because:
done of #818293 is '' not 'Ritesh Raj Sarraf '
Failed to merge 818036: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed (with 1 error): merging 818036 818293

[Debian Bug Tracking System]

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

> merge 818036 818293
Bug #818036 {Done: Ritesh Raj Sarraf } [kpartx] kpartx does 
not ship multipathd.service but tries to start/stop that service
Unable to merge bugs because:
severity of #818293 is 'grave' not 'serious'
done of #818293 is '' not 'Ritesh Raj Sarraf '
Failed to merge 818036: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#818295: guitarix: Please replace build dependency on libwebkit-dev with libwebkitgtk-dev

[Alberto Garcia]

Source: guitarix
Version: 0.34.0-0.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The libwebkit-dev package has been marked as transitional for a few
years now, and I would like to get rid of it soon.

Please replace the build dependency with libwebkitgtk-dev.

Thanks,

Berto

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

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

Bug#818036: "kpartx does not ship multipathd.service but tries to start/stop that service" not fixed in 0.5.0+git1.656f8865-7

[Sven Hartge]

On Tue, 15 Mar 2016 22:28:49 +0530 Ritesh Raj Sarraf  wrote:

> If you upgrade from -5 to -7, you shouldn't be hitting this problem. I
> thought about handling the breakage, but that would touch files outside
> , which I'm not keen on. 
> 
> And Unstable is supposed to have breakages.

Sorry, but I find this unacceptable. Sure, Unstable can have breakages,
but is not supposed to have one. You cannot just ignore one upgrade path
because it is inconvenient for you.

The -6 package has been release to mirrors and has been installed on
systems, so you have to provide a clean upgrade path to the next package
and not just walk away saying "upgrade from -6 to -7 are not supported"
and leave the user to manually put the package into a working state again.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#818036: "kpartx does not ship multipathd.service but tries to start/stop that service" not fixed in 0.5.0+git1.656f8865-7

[Sven-Haegar Koch]

On Tue, 15 Mar 2016, Ritesh Raj Sarraf wrote:

So the "official" workaround is

rm /var/lib/dpkg/info/kpartx.prerm

before upgrading from -6?

(That works)

Greetings
Haegar


> If you upgrade from -5 to -7, you shouldn't be hitting this problem. I
> thought about handling the breakage, but that would touch files outside
> , which I'm not keen on. 
> 
> And Unstable is supposed to have breakages.
> 
> 
> 2016-03-15 13:46:48 upgrade kpartx:amd64 0.5.0+git1.656f8865-5
> 0.5.0+git1.656f8865-7
> 2016-03-15 13:46:48 status half-configured kpartx:amd64
> 0.5.0+git1.656f8865-5
> 2016-03-15 13:46:48 status unpacked kpartx:amd64 0.5.0+git1.656f8865-5
> 2016-03-15 13:46:48 status half-installed kpartx:amd64
> 0.5.0+git1.656f8865-5
> 2016-03-15 13:46:48 status triggers-pending man-db:amd64 2.7.5-1
> 2016-03-15 13:46:48 status half-installed kpartx:amd64
> 0.5.0+git1.656f8865-5
> 2016-03-15 13:46:49 status unpacked kpartx:amd64 0.5.0+git1.656f8865-7
> 2016-03-15 13:46:49 status unpacked kpartx:amd64 0.5.0+git1.656f8865-7
> 2016-03-15 13:46:49 configure kpartx:amd64 0.5.0+git1.656f8865-7
> 0.5.0+git1.656f8865-7
> 2016-03-15 13:46:49 status unpacked kpartx:amd64 0.5.0+git1.656f8865-7
> 2016-03-15 13:46:49 status half-configured kpartx:amd64
> 0.5.0+git1.656f8865-7
> 2016-03-15 13:46:49 status installed kpartx:amd64 0.5.0+git1.656f8865-7
> 
> On Tue, 2016-03-15 at 17:30 +0100, Sven-Haegar Koch wrote:
> > Hallo,
> > 
> > This bug is not fixed yet - maybe just an empty pre-removal script
> > will 
> > help?
> > 
> > Preparing to unpack .../kpartx_0.5.0+git1.656f8865-7_amd64.deb ...
> > Failed to stop multipathd.service: Unit multipathd.service not
> > loaded.
> > dpkg: warning: subprocess old pre-removal script returned error exit 
> > status 5
> > dpkg: trying script from the new package instead ...
> > dpkg: error processing archive 
> > /var/cache/apt/archives/kpartx_0.5.0+git1.656f8865-7_amd64--unpack):
> >  there is no script in the new version of the package - giving up
> > Failed to get unit file state for multipathd.service: No such file
> > or 
> > directory
> > multipathd.service is a disabled or a static unit, not starting it.
> > Processing triggers for man-db (2.7.5-1) ...
> > Errors were encountered while processing:
> >  /var/cache/apt/archives/kpartx_0.5.0+git1.656f8865-7_amd64.deb
> 

c'ya
sven-haegar

-- 
Three may keep a secret, if two of them are dead.
- Ben F.

Bug#818036: "kpartx does not ship multipathd.service but tries to start/stop that service" not fixed in 0.5.0+git1.656f8865-7

[Ritesh Raj Sarraf]

I am not walking away. The failure is 2 folds. If you got hit by -6, on
your machine the (broken) maintainer script gets installed, which you'll
have to manually remove.
That's something I do not want to handle in the package. Otherwise, the fix
to not break the maintainer script is done.

On Tue, Mar 15, 2016 at 10:40 PM, Sven Hartge  wrote:

> On Tue, 15 Mar 2016 22:28:49 +0530 Ritesh Raj Sarraf 
> wrote:
>
> > If you upgrade from -5 to -7, you shouldn't be hitting this problem. I
> > thought about handling the breakage, but that would touch files outside
> > , which I'm not keen on.Â
> >
> > And Unstable is supposed to have breakages.
>
> Sorry, but I find this unacceptable. Sure, Unstable can have breakages,
> but is not supposed to have one. You cannot just ignore one upgrade path
> because it is inconvenient for you.
>
> The -6 package has been release to mirrors and has been installed on
> systems, so you have to provide a clean upgrade path to the next package
> and not just walk away saying "upgrade from -6 to -7 are not supported"
> and leave the user to manually put the package into a working state again.
>
> Grüße,
> Sven.
>
>


-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

Bug#818036: "kpartx does not ship multipathd.service but tries to start/stop that service" not fixed in 0.5.0+git1.656f8865-7

[Sven Hartge]

On 15.03.2016 18:16, Ritesh Raj Sarraf wrote:

> I am not walking away. The failure is 2 folds. If you got hit by -6, on
> your machine the (broken) maintainer script gets installed, which you'll
> have to manually remove.

No, I do not. It is your job as package maintainer to clean this up. You
broke it, you fix it.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#818294: balsa: Please replace build dependency on libwebkit-dev with libwebkitgtk-dev

[Alberto Garcia]

Source: balsa
Version: 2.4.12-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The libwebkit-dev package has been marked as transitional for a few
years now, and I would like to get rid of it soon.

Please replace the build dependency with libwebkitgtk-dev.

Thanks,

Berto

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

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

Bug#818293: kpartx: cannot be installed

[Eric Valette]

Package: kpartx
Version: 0.5.0+git1.656f8865-7
Severity: grave
Justification: renders package unusable

LANG=C; apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libavformat57
The following packages will be upgraded:
  kpartx
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/32.2 kB of archives.
After this operation, 2048 B disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 387658 files and directories currently installed.)
Preparing to unpack .../kpartx_0.5.0+git1.656f8865-7_amd64.deb ...
Failed to stop multipathd.service: Unit multipathd.service not loaded.
dpkg: warning: subprocess old pre-removal script returned error exit status 5
dpkg: trying script from the new package instead ...
dpkg: error processing archive 
/var/cache/apt/archives/kpartx_0.5.0+git1.656f8865-7_amd64.deb (--unpack):
 there is no script in the new version of the package - giving up
Failed to get unit file state for multipathd.service: No such file or directory
multipathd.service is a disabled or a static unit, not starting it.
Errors were encountered while processing:
 /var/cache/apt/archives/kpartx_0.5.0+git1.656f8865-7_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



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

Kernel: Linux 4.4.5 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kpartx depends on:
ii  dmsetup 2:1.02.116-1+b1
ii  libc6   2.23-0experimental0
ii  libdevmapper1.02.1  2:1.02.116-1+b1
ii  udev229-2

kpartx recommends no packages.

kpartx suggests no packages.

-- no debconf information

Processed: notfixed 813982 in 0.10.2

[Debian Bug Tracking System]

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

> notfixed 813982 0.10.2
Bug #813982 {Done: Yaroslav Halchenko } [src:python-mne] 
python-mne: FTBFS: IndexError: an index can only have a single ellipsis ('...')
The source 'python-mne' and version '0.10.2' do not appear to match any binary 
packages
No longer marked as fixed in versions 0.10.2.
> thanks
Stopping processing here.

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

Processed: tagging 814994

[Debian Bug Tracking System]

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

> tags 814994 + pending
Bug #814994 [haskell-stack] haskell-stack: FTBFS - build-dep libghc-aeson-dev 
(<< 0.10) unsatisfiable as 0.10.0.0-3 is current
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#818036: "kpartx does not ship multipathd.service but tries to start/stop that service" not fixed in 0.5.0+git1.656f8865-7

[Ritesh Raj Sarraf]

If you upgrade from -5 to -7, you shouldn't be hitting this problem. I
thought about handling the breakage, but that would touch files outside
, which I'm not keen on. 

And Unstable is supposed to have breakages.


2016-03-15 13:46:48 upgrade kpartx:amd64 0.5.0+git1.656f8865-5
0.5.0+git1.656f8865-7
2016-03-15 13:46:48 status half-configured kpartx:amd64
0.5.0+git1.656f8865-5
2016-03-15 13:46:48 status unpacked kpartx:amd64 0.5.0+git1.656f8865-5
2016-03-15 13:46:48 status half-installed kpartx:amd64
0.5.0+git1.656f8865-5
2016-03-15 13:46:48 status triggers-pending man-db:amd64 2.7.5-1
2016-03-15 13:46:48 status half-installed kpartx:amd64
0.5.0+git1.656f8865-5
2016-03-15 13:46:49 status unpacked kpartx:amd64 0.5.0+git1.656f8865-7
2016-03-15 13:46:49 status unpacked kpartx:amd64 0.5.0+git1.656f8865-7
2016-03-15 13:46:49 configure kpartx:amd64 0.5.0+git1.656f8865-7
0.5.0+git1.656f8865-7
2016-03-15 13:46:49 status unpacked kpartx:amd64 0.5.0+git1.656f8865-7
2016-03-15 13:46:49 status half-configured kpartx:amd64
0.5.0+git1.656f8865-7
2016-03-15 13:46:49 status installed kpartx:amd64 0.5.0+git1.656f8865-7

On Tue, 2016-03-15 at 17:30 +0100, Sven-Haegar Koch wrote:
> Hallo,
> 
> This bug is not fixed yet - maybe just an empty pre-removal script
> will 
> help?
> 
> Preparing to unpack .../kpartx_0.5.0+git1.656f8865-7_amd64.deb ...
> Failed to stop multipathd.service: Unit multipathd.service not
> loaded.
> dpkg: warning: subprocess old pre-removal script returned error exit 
> status 5
> dpkg: trying script from the new package instead ...
> dpkg: error processing archive 
> /var/cache/apt/archives/kpartx_0.5.0+git1.656f8865-7_amd64--unpack):
>  there is no script in the new version of the package - giving up
> Failed to get unit file state for multipathd.service: No such file
> or 
> directory
> multipathd.service is a disabled or a static unit, not starting it.
> Processing triggers for man-db (2.7.5-1) ...
> Errors were encountered while processing:
>  /var/cache/apt/archives/kpartx_0.5.0+git1.656f8865-7_amd64.deb
-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Processed: tagging 814993

[Debian Bug Tracking System]

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

> tags 814993 + pending
Bug #814993 [haskell-cabal-install] haskell-cabal-install: FTBFS - build-dep 
libghc-zlib-dev (<< 0.6) unsatisfiable as 0.6.1.1-1 is current
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#815205: sbcl: FTBFS due to TeX error

[Christoph Egger]

Hi texinfo folks!

Christoph Egger  writes:
> Logan Rosen  writes:
>> I just merged sbcl 2:1.3.1-1 into Ubuntu (we have a simple chmod change in
>> debian/rules), and it failed to build on all architectures [1]. I verified
>> that this issue affects Debian unstable as well by building it in a chroot.
>>
>> It appears to be due to a TeX issue during the build.
>
> Seems to be related to texinfo 6.0.0 -> 6.1.0
>
> | .texinfo:3: TeX capacity exceeded, sorry [text input levels=15].

Upstream has decided this is a problem in texinfo .. can I have your
input on this issue?

  Christoph

https://bugs.launchpad.net/sbcl/+bug/1549892

Bug#818036: "kpartx does not ship multipathd.service but tries to start/stop that service" not fixed in 0.5.0+git1.656f8865-7

[Sven-Haegar Koch]

Hallo,

This bug is not fixed yet - maybe just an empty pre-removal script will 
help?

Preparing to unpack .../kpartx_0.5.0+git1.656f8865-7_amd64.deb ...
Failed to stop multipathd.service: Unit multipathd.service not loaded.
dpkg: warning: subprocess old pre-removal script returned error exit 
status 5
dpkg: trying script from the new package instead ...
dpkg: error processing archive 
/var/cache/apt/archives/kpartx_0.5.0+git1.656f8865-7_amd64--unpack):
 there is no script in the new version of the package - giving up
Failed to get unit file state for multipathd.service: No such file or 
directory
multipathd.service is a disabled or a static unit, not starting it.
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/kpartx_0.5.0+git1.656f8865-7_amd64.deb


c'ya
sven-haegar

-- 
Three may keep a secret, if two of them are dead.
- Ben F.

Bug#818000: Configuration files stored in /lib/ufw; FHS violation

[Jamie Strandboge]

On Sat, 2016-03-12 at 15:30 +, Ben Hutchings wrote:
> Package: ufw
> Version: 0.34-2
> Severity: serious
> 
> Configuration files written by the ufw command (user.rules,
> user6.rules) must be stored in either /etc (if they are also intended
> to be directly editable) or /var.
> 
> I spent quite some time trying to understand how to transfer my ufw
> configuration to a new installation; following the FHS would have
> saved me that.
> 
Sorry about that. Actually this has been discussed at great length in the
upstream bug. Here has been my historical take:
https://bugs.launchpad.net/ufw/+bug/728128/comments/1

That said with 0.35 I finally yielded:

ufw (0.35) RELEASED; urgency=medium
 ...
  * move user[6].rules to /etc/ufw (LP: #728128)

In other words, this will be fixed in 0.35-1.

> Ben.
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages ufw depends on:
> ii  debconf [debconf-2.0]  1.5.59
> ii  init-system-helpers1.29
> ii  iptables   1.6.0-2
> ii  python33.5.1-2
> pn  python3:any
> ii  ucf3.0035
> 
> ufw recommends no packages.
> 
> Versions of packages ufw suggests:
> ii  rsyslog  8.16.0-1
> 
> -- debconf information excluded
-- 
Jamie Strandboge | http://www.canonical.com



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

Bug#815798: marked as done (gitlab: not installable because of locale issue)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2016 15:50:31 +
with message-id 
and subject line Bug#815798: fixed in gitlab 8.4.3+dfsg-10
has caused the Debian Bug report #815798,
regarding gitlab: not installable because of locale issue
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.)


-- 
815798: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: gitlab uninstallabe on plain Debian "stretch"
Package: gitlab
Version: 8.4.3+dfsg-9
Severity: serious

Hi,

trying to install gitlab package on a palin stretch-system where postgis and
nginx have already been installed will currently not work.

In case it is of relevance, the system uses sysv-init.

Here is what I get (irrelevant parts have been skipped).

The "gitlab_production database is not empty" message can not be true.  I
did check it manually and it is empty.

..

gitlab_production database is not empty, skipping gitlab setup
Precompiling assets...
fatal: Not a git repository (or any of the parent directories): .git
I, [2016-02-24T13:50:04.590534 #18160]  INFO -- : 


...


Starting GitLab Unicorn
Starting GitLab Sidekiq
Starting gitlab-workhorse
.
The GitLab Unicorn web server with pid 20641 is running.
The GitLab Sidekiq job dispatcher with pid 20706 is running.
The gitlab-workhorse with pid 20683 is running.
GitLab and all its components are up and running.
fatal: Not a git repository (or any of the parent directories): .git
Checking GitLab Shell ...

GitLab Shell version >= 2.6.10 ? ... OK (2.6.10)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by gitlab:gitlab? ... yes
Repo base access is drwxrws---? ... yes
hooks directories in repos are links: ... rake aborted!
ActiveRecord::StatementInvalid: PG::UndefinedTable: ERROR:  relation "projects" 
does not exist
LINE 5:WHERE a.attrelid = '"projects"'::regclass
  ^
:   SELECT a.attname, format_type(a.atttypid, a.atttypmod),
 pg_get_expr(d.adbin, d.adrelid), a.attnotnull,
a.atttypid, a.atttypmod
FROM pg_attribute a LEFT JOIN pg_attrdef d
  ON a.attrelid = d.adrelid AND a.attnum = d.adnum
   WHERE a.attrelid = '"projects"'::regclass
 AND a.attnum > 0 AND NOT a.attisdropped
   ORDER BY a.attnum
/usr/share/gitlab/lib/tasks/gitlab/check.rake:476:in 
`check_repos_hooks_directory_is_link'
/usr/share/gitlab/lib/tasks/gitlab/check.rake:366:in `block (3 levels) in '
PG::UndefinedTable: ERROR:  relation "projects" does not exist
LINE 5:WHERE a.attrelid = '"projects"'::regclass
  ^
/usr/share/gitlab/lib/tasks/gitlab/check.rake:476:in 
`check_repos_hooks_directory_is_link'
/usr/share/gitlab/lib/tasks/gitlab/check.rake:366:in `block (3 levels) in '
Tasks: TOP => gitlab:check => gitlab:gitlab_shell:check
(See full trace by running task with --trace)
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 8.4.3+dfsg-10

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated gitlab package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Mar 2016 19:42:59 +0530
Source: gitlab
Binary: gitlab
Architecture: source
Version: 8.4.3+dfsg-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 gitlab - git powered software platform to collaborate on code
Closes: 815798 817150
Changes:
 gitlab (8.4.3+dfsg-10) unstable; urgency=medium
 .
   [ Balasankar C ]
   * Team upload.
   * Bump Standards Version (No Changes).
   * Fix typo in debian/README.Debian.
   * 0038-relax-net-ssh.patch : Add dep3 header.
 .
   [ Pirate Praveen ]
   * 

Bug#817150: marked as done (gitlab expects rails 4.2.5.1 which is not (anymore) in stretch)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2016 15:50:31 +
with message-id 
and subject line Bug#817150: fixed in gitlab 8.4.3+dfsg-10
has caused the Debian Bug report #817150,
regarding gitlab expects rails 4.2.5.1 which is not (anymore) in stretch
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.)


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

Package: gitlab
Version: 8.4.3+dfsg-9
Severity: normal

Dear Maintainer,

gitlab fails to install/configure because it expects to find rails 
4.2.5.1 installed on the system.

however, debian stretch comes with rails 4.2.5.2-2

adjusting the rails version in /usr/share/gitlab/Gemfile corrects the 
issue.


Best,
Hp

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages gitlab depends on:
ii  adduser3.113+nmu3
ii  asciidoctor1.5.4-1
ii  bc 1.06.95-9+b1
ii  bundler1.11.2-1
ii  debconf [debconf-2.0]  1.5.58
ii  git1:2.7.0-1
ii  gitlab-shell   2.6.10-1
ii  gitlab-workhorse   0.6.3-1
ii  init-system-helpers1.29
ii  libjs-chartjs  1.0.2-1
ii  libjs-clipboard1.4.2-1
ii  libjs-fuzzaldrin-plus  0.3.1-1
ii  libjs-graphael 0.5+dfsg-1
ii  libjs-jquery-cookie10-2
ii  libjs-jquery-history   10-2
ii  libjs-jquery-nicescroll3.6.6-1
ii  nginx  1.9.10-1
ii  nginx-full [nginx] 1.9.10-1
ii  nodejs 4.3.1~dfsg-3
ii  postgresql 9.5+172
ii  postgresql-client  9.5+172
ii  postgresql-client-9.5 [postgresql-client]  9.5.1-1
ii  rake   10.5.0-2
ii  redis-server   2:3.0.6-1
ii  ruby   1:2.3.0+1
ii  ruby-ace-rails-ap  3.0.3-2
ii  ruby-activerecord-deprecated-finders   1.0.4-1
ii  ruby-activerecord-session-store0.1.1-3
ii  ruby-acts-as-taggable-on   3.5.0-2
ii  ruby-addressable   2.3.8-1
ii  ruby-after-commit-queue1.3.0-1
ii  ruby-allocations   1.0.3-1+b1
ii  ruby-asana 0.4.0-1
ii  ruby-attr-encrypted1.3.4-1
ii  ruby-babosa1.0.2-1
ii  ruby-bootstrap-sass3.3.5.1-3
ii  ruby-browser   1.0.1-1
ii  ruby-cal-heatmap-rails 3.5.1+dfsg-1
ii  ruby-carrierwave   0.10.0+gh-2
ii  ruby-charlock-holmes   0.7.3+dfsg-2+b1
ii  ruby-coffee-rails  4.1.0-2
ii  ruby-colorize  0.7.7-1
ii  ruby-connection-pool   2.2.0-1
ii  ruby-creole0.5.0-2
ii  ruby-d3-rails  3.5.6+dfsg-1
ii  ruby-default-value-for 3.0.1-1
ii  ruby-devise3.5.2-3
ii  ruby-devise-async  0.9.0-1
ii  ruby-devise-two-factor 2.0.0-1
ii  ruby-diffy 3.0.6-1
ii  ruby-doorkeeper2.2.1-1
ii  ruby-dropzonejs-rails  0.7.1-1
ii  ruby-email-reply-parser0.5.8-1
ii  ruby-fog   1.34.0-2
ii  ruby-fogbugz   0.2.1-2
ii  ruby-font-awesome-rails4.3.0.0-1
ii  ruby-gemnasium-gitlab-service  0.2.6-1
ii  ruby-github-linguist   4.7.2-2
ii  ruby-github-markup 1.3.3+dfsg-1
ii  ruby-gitlab-emoji  0.2.1-1
ii  ruby-gitlab-flowdock-git-hook  1.0.1-1
ii  

Processed: found 818288

[Debian Bug Tracking System]

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

> found 818288 afl/2.08b-1
Bug #818288 [afl] afl: FTBFS on s390x
Marked as found in versions afl/2.08b-1.
> thanks
Stopping processing here.

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

Bug#818288: afl: FTBFS on s390x

[Daniel Stender]

Package: afl
Version: 2.08b-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

afl currently FTBFS on s390x:
https://buildd.debian.org/status/fetch.php?pkg=afl=s390x=2.08b-2=1458049587


clang-3.6 -g -O2 -fPIE -Wformat -Werror=format-security -Wall 
-D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/usr/lib/afl\" 
-DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.08b\"  -fPIC -c afl-llvm-rt.o.c -o 
../afl-llvm-rt.o
0  libLLVM-3.6.so.1 0x03fffc2ade02 llvm::sys::PrintStackTrace(_IO_FILE*) + 
42
1  libLLVM-3.6.so.1 0x03fffc2ac2c2
2  libLLVM-3.6.so.1 0x03eab16c
3  libLLVM-3.6.so.1 0x03fffca603c4 
llvm::SystemZTargetLowering::LowerOperation(llvm::SDValue, llvm::SelectionDAG&) 
const + 68
4  libLLVM-3.6.so.1 0x03fffbeddef0
5  libLLVM-3.6.so.1 0x03fffbee03ea llvm::SelectionDAG::Legalize() + 418
6  libLLVM-3.6.so.1 0x03fffbfe0410 
llvm::SelectionDAGISel::CodeGenAndEmitDAG() + 616
7  libLLVM-3.6.so.1 0x03fffbfe4a22 
llvm::SelectionDAGISel::SelectAllBasicBlocks(llvm::Function const&) + 2138
8  libLLVM-3.6.so.1 0x03fffbfe602c 
llvm::SelectionDAGISel::runOnMachineFunction(llvm::MachineFunction&) + 876
9  libLLVM-3.6.so.1 0x03fffba871f8 
llvm::FPPassManager::runOnFunction(llvm::Function&) + 584
10 libLLVM-3.6.so.1 0x03fffba874f6 
llvm::FPPassManager::runOnModule(llvm::Module&) + 54
11 libLLVM-3.6.so.1 0x03fffba86da0 
llvm::legacy::PassManagerImpl::run(llvm::Module&) + 984
12 clang0x804e855e 
clang::EmitBackendOutput(clang::DiagnosticsEngine&, clang::CodeGenOptions 
const&, clang::TargetOptions const&, clang::LangOptions const&, 
llvm::StringRef, llvm::Module*, clang::BackendAction, llvm::raw_ostream*) + 2622
13 clang0x804d6b90
14 clang0x806d94a4 clang::ParseAST(clang::Sema&, bool, 
bool) + 892
15 clang0x80315846 clang::FrontendAction::Execute() + 190
16 clang0x802eaafe 
clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) + 406
17 clang0x802ce43a 
clang::ExecuteCompilerInvocation(clang::CompilerInstance*) + 2338
18 clang0x802c9088 cc1_main(llvm::ArrayRef, 
char const*, void*) + 1472
19 clang0x802c5b74 main + 1436
20 libc.so.60x03fffaeb74c0 __libc_start_main + 272
21 clang0x802c8526
Stack dump:
0.  Program arguments: /usr/lib/llvm-3.6/bin/clang -cc1 -triple 
s390x-ibm-linux-gnu -emit-obj -disable-free -disable-llvm-verifier 
-main-file-name afl-llvm-rt.o.c -mrelocation-model pic -pic-level 2 
-mthread-model posix -fmath-errno -masm-verbose -mconstructor-aliases 
-fuse-init-array -target-cpu z10 -target-linker-version 2.25.1 
-momit-leaf-frame-pointer -g -dwarf-column-info -coverage-file 
/«PKGBUILDDIR»/llvm_mode/../afl-llvm-rt.o -resource-dir 
/usr/lib/llvm-3.6/bin/../lib/clang/3.6.2 -D _FORTIFY_SOURCE=2 -D 
AFL_PATH="/usr/lib/afl" -D BIN_PATH="/usr/bin" -D VERSION="2.08b" 
-internal-isystem /usr/local/include -internal-isystem 
/usr/lib/llvm-3.6/bin/../lib/clang/3.6.2/include -internal-externc-isystem 
/usr/include/s390x-linux-gnu -internal-externc-isystem /include 
-internal-externc-isystem /usr/include -O2 -Wformat -Werror=format-security 
-Wall -Wno-pointer-sign -fdebug-compilation-dir /«PKGBUILDDIR»/llvm_mode 
-ferror-limit 19 -fmessage-length 0 -mstackrealign -fno-signed
 -char -fobjc-runtime=gcc -fdiagnostics-show-option -vectorize-loops 
-vectorize-slp -o ../afl-llvm-rt.o -x c afl-llvm-rt.o.c 
1.   parser at end of file
2.  Code generation
3.  Running pass 'Function Pass Manager' on module 'afl-llvm-rt.o.c'.
4.  Running pass 'SystemZ DAG->DAG Pattern Instruction Selection' on 
function '@__sanitizer_cov_trace_pc'
clang: error: unable to execute command: Segmentation fault


DS

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

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

Versions of packages afl depends on:
ii  libc6  2.21-9

Versions of packages afl recommends:
ii  afl-clang  2.08b-1
ii  afl-doc2.08b-1
ii  g++4:5.3.1-1
ii  gcc4:5.3.1-1
ii  gnuplot4.6.6-3

afl suggests no packages.

-- no debconf information

Bug#818148: bullet: Out of memory errors do not make the build to stop

[Markus Koschany]

Control: severity -1 wishlist

Am 15.03.2016 um 16:01 schrieb Santiago Vila:
> severity 818148 serious
> thanks
> 
> Per Policy 4.6, "Error trapping in makefiles", I'm setting the
> severity to what it should be.
> 
> Policy 4.6 says:
> 
>   Every time you put more than one shell command (this includes using
>   a loop) in a makefile command you must make sure that errors are
>   trapped.
> 
> Note that it says "must", so the serious severity is completely appropriate.
> 
> Feel free to keep the "unreproducible" tag if you like, but this
> is a serious bug according to Debian policy.
> 
> Lack of memory is not the problem, it's just the way we discovered
> that this package does not trap for errors during the build.
> 
> The errors may be produced by any other reason other than lack of
> memory, but the fact that the makefiles do not trap errors remains the
> same.

I suggest that you calm down a little. It is obvious that you disagree
with my assessment but that does not justify your aggressiveness and
your actions.

For the record: As the main uploader of this package I strongly disagree
with your bug severity. The package is not affected and the
documentation is complete, all images are present as expected. Just
because the images are not generated with graphviz on a low memory
system does not make this a release critical issue. The build system
clearly told you that your memory is insufficient and that you should
rerun graphviz. If you ignore those error messages and my advice, then I
am unable to help you.

Please avoid changing the bug severity again but feel free to forward
this issue to Debian's Technical Committee after having slept over it.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#818148: bullet: Out of memory errors do not make the build to stop

[Santiago Vila]

On Tue, Mar 15, 2016 at 04:06:24PM +0100, Markus Koschany wrote:
> Am 15.03.2016 um 15:50 schrieb Santiago Vila:
> > Excuse me, how is this unreproducible at all?
> 
> It is neither reproducible on Debian's build servers nor on my system.

So if I report that "ls -l" segfaults would you tag the bug as
unreproducible after checking that "ls --color" or "ls" alone do not
segfault?

You would have a very narrow definition of "unreproducible" then.

For something to be considered unreproducible you should at least try
the conditions under which the problem is *reported* to happen.

If the report says "ls -l", you would try "ls -l". If the report
says "400 MB of RAM", you would try "400 MB of RAM".

Otherwise an unreproducible tag just means "I don't want to reproduce it",
and not "We followed *all* the steps in the bug report one by one and
the problem did not happen".

Thanks.

Processed: Re: Bug#818148: bullet: Out of memory errors do not make the build to stop

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #818148 [src:bullet] bullet: Out of memory errors do not make the build to 
stop
Severity set to 'wishlist' from 'serious'

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

Bug#818148: bullet: Out of memory errors do not make the build to stop

[Santiago Vila]

On Tue, Mar 15, 2016 at 04:06:24PM +0100, Markus Koschany wrote:

> It is also not serious because it does not violate the Debian Policy
> in any way

That's simply not true.

Please (Re)read Policy 4.6. I've quoted it in a previous email.

Thanks.

Bug#818148: bullet: Out of memory errors do not make the build to stop

[Markus Koschany]

Am 15.03.2016 um 15:50 schrieb Santiago Vila:
> On Tue, Mar 15, 2016 at 03:37:17PM +0100, Markus Koschany wrote:
>> Control: severity -1 wishlist
>> Control: tags -1 - moreinfo + unreproducible
> 
> Excuse me, how is this unreproducible at all?

It is neither reproducible on Debian's build servers nor on my system.

> 
> I've told you the way to reproduce it: Try on a machine with only 400 MB
> of RAM.
> 
> Your unwillingness to try the build with only 400 MB of RAM
> (i.e. "I don't want to reproduce it") does not make this problem
> unreproducible at all.

I have told you how you can fix this issue for your system.
Unfortunately you are the one who is unwilling to take this advice.

>> I am going to downgrade the severity to wishlist because I think this is
>> an improvement suggestion but not an important bug for Debian as long as
>> Bullet builds fine on Debian's build servers and also on my own system.
> 
> This is not wishlist. This is Debian policy. When something fails,
> we take the exit status and act accordingly.
> 
> Please read my previous email where I tell you how the generated
> package is completely different than what it should be.

This is not a RC bug because it does not affect the actual package in
Debian. It cannot be grave because it does not make the documentation
package unusable. It is also not serious because it does not violate the
Debian Policy in any way and I do not consider this issue release
critical either.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#818148: bullet: Out of memory errors do not make the build to stop

[Debian Bug Tracking System]

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

> severity 818148 serious
Bug #818148 [src:bullet] bullet: Out of memory errors do not make the build to 
stop
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Bug#817837: l2tpns: *** buffer overflow detected ***: l2tpns terminated

[Jonathan McDowell]

On Thu, Mar 10, 2016 at 07:50:22PM +, Dave Reeve wrote:
> Running l2tpns causes an instance crash as follows:
> 
> # l2tpns -v
> *** buffer overflow detected ***: l2tpns terminated
> (full trace removed as it doesn't help)
> 
> The problem exists in the ring buffer logging code.  Specially the vsprintf
> is called with a length of 4095 when the size of the buffer is MAX_LOG_LENGTH
> (defined as 512 in l2tpns.h).  The result is that as soon as the program is
> executed it crashes as soon as a few log messages are printed.  The following
> patch resolves the problem.
>
> I also have some more minor fixes, which resolve compiler warnings.  I
> am happy to share these if you let me know where to send them!

Upstream these days is at http://git.sameswireless.fr/l2tpns.git and I
note Fernando has been maintaining Debian packaging. As I haven't been
using l2tpns for some time I have emailed him asking if he would like to
take over maintenance of the package in Debian. It's probably best to
send fixes directly upstream.

J.

-- 
/-\ |  Do I BELIEVE in the Bible?! Hell,
|@/  Debian GNU/Linux Developer |man I've SEEN one!!!
\-  |

Bug#818123: marked as done (doublecmd: FTBFS in stretch)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2016 12:19:39 +
with message-id 
and subject line Bug#818123: fixed in doublecmd 0.7.0-1
has caused the Debian Bug report #818123,
regarding doublecmd: FTBFS in stretch
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.)


-- 
818123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:doublecmd
Version: 0.6.6-1
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


/<>/src/./platform/unix/umyunix.pas(523,83) Error: (3069)
Call by var for arg no. 3 has to match exactly: Go t "UTF8String"
expected "AnsiString"


The full build log is attached.

Thanks.

doublecmd_0.6.6-1_amd64-20160313-2250.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: doublecmd
Source-Version: 0.7.0-1

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated doublecmd 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, 15 Mar 2016 13:48:55 +0200
Source: doublecmd
Binary: doublecmd-gtk doublecmd-gtk-dbg doublecmd-qt doublecmd-qt-dbg 
doublecmd-plugins doublecmd-common
Architecture: source all amd64
Version: 0.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Graham Inggs 
Description:
 doublecmd-common - twin-panel (commander-style) file manager
 doublecmd-gtk - twin-panel (commander-style) file manager (GTK2)
 doublecmd-gtk-dbg - twin-panel (commander-style) file manager (GTK2 - debug)
 doublecmd-plugins - twin-panel (commander-style) file manager (plugins)
 doublecmd-qt - twin-panel (commander-style) file manager (Qt4)
 doublecmd-qt-dbg - twin-panel (commander-style) file manager (Qt4 - debug)
Closes: 803984 807257 807570 818123
Changes:
 doublecmd (0.7.0-1) unstable; urgency=medium
 .
   * New upstream release:
 - add inode/directory MimeType to doublecmd.desktop (Closes: #807570)
 - fix scrolling through files with long names is slow (Closes: #807257)
 - fix FTBFS with FPC 3.0 and Lazarus 1.6 (Closes: #818123)
   * Fix FTBFS on arm64, thanks Edmund Grimley Evans
 and Alexander Koblov (Closes: #803984)
   * Remove doublecmd-common.menu, as per #741573.
   * Use secure URIs for VCS fields.
   * Update d/copyright.
   * Update Lintian overrides for doublecmd-plugins.
   * Bump Standards-Version to 3.9.7, no further changes.
Checksums-Sha1:
 e3a9a1c11f51532d2790a640cc5e1460e3fa2ba4 2402 doublecmd_0.7.0-1.dsc
 ecc60e6ab44a91d6fd7d3bd56b14d3daf7357a35 6635488 doublecmd_0.7.0.orig.tar.gz
 dcecd5468139187eb3099431eac65f9902057ed5 11060 doublecmd_0.7.0-1.debian.tar.xz
 81b2f33c16f9ec8b5706d5bbf3f5f9053b3e7c56 1670894 
doublecmd-common_0.7.0-1_all.deb
 05e43cbaa3c1ebe6cabf9f410dd57939c47b6a53 771536 
doublecmd-gtk-dbg_0.7.0-1_amd64.deb
 1a21f1775bddd5de816dab60784fe61c321eb200 3151592 
doublecmd-gtk_0.7.0-1_amd64.deb
 90008a4cbbd0558e778b7e72e5b33805200447d0 1251840 
doublecmd-plugins_0.7.0-1_amd64.deb
 685b3c664ecdf8ce0fbfa63de7a2992612f68baf 763302 
doublecmd-qt-dbg_0.7.0-1_amd64.deb
 0fae70b9b62488345356c0683d42fa01eb7cb3d2 3080292 doublecmd-qt_0.7.0-1_amd64.deb
Checksums-Sha256:
 284c0517dca9cf7abb9c7fa3c62da42d03c714fef13e5d4ec51f51e9ebf8fc98 2402 
doublecmd_0.7.0-1.dsc
 4c0bb537268f44c6571da20a68650ee0164d1db9a300666012a72e8e3d7d6d20 6635488 
doublecmd_0.7.0.orig.tar.gz
 60b631c2aed1034bbfffacdd5fcf07f0741f879455dd359f67fe2e4c7b05bc98 11060 
doublecmd_0.7.0-1.debian.tar.xz
 a1aa7daaa590110e12bff329b73ab30a72ac8eeb953135b248948bfb730f7852 1670894 
doublecmd-common_0.7.0-1_all.deb
 198f22f924f07e2961921da4d9e52b8903439d572902eef241d3713cafcba7f6 771536 
doublecmd-gtk-dbg_0.7.0-1_amd64.deb
 bbbc451ca6c07ec3d8e854eae1957d435c6af01e659a684815b4a2975a080e06 3151592 
doublecmd-gtk_0.7.0-1_amd64.deb
 

Bug#811031: fglrx-driver: missing support for xserver 1.18

[Jonas Andradas]

On Fri, 15 Jan 2016 00:02:23 +0100 Andreas Beckmann

 wrote:

> Package: fglrx-driver

> Version: 1:15.9-4

> Severity: normal

> Tags: upstream

> Control: block 808735 with -1

>

> fglrx lacks support for xserver 1.18 (xorg-video-abi-20) in

> experimental.

>

>

> Andreas

>

>


Hi,


I am experiencing the same issue. When I try to install fglrx-driver, I get:


# apt-get install fglrx-driver

Reading package lists... Done

Building dependency tree

Reading state information... Done

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:


The following packages have unmet dependencies:

fglrx-driver : Depends: xorg-video-abi-19 but it is not installable or

xorg-video-abi-18 but it is not installable or

xorg-video-abi-15 but it is not installable or

xorg-video-abi-14 but it is not installable or

xorg-video-abi-13 but it is not installable or

xorg-video-abi-12 but it is not installable or

xorg-video-abi-11 but it is not installable or

xorg-video-abi-10 but it is not installable or

xorg-video-abi-8 but it is not installable or

xorg-video-abi-6.0 but it is not installable

Recommends: libgl1-fglrx-glx-i386

E: Unable to correct problems, you have held broken packages.



The xserver-xorg-core package does not provide xorg-video-abi-19 or

xorg-video-abi-18 anymore:


$ apt-cache show xserver-xorg-core

Package: xserver-xorg-core

Source: xorg-server

Version: 2:1.18.2-1

Installed-Size: 5637

Maintainer: Debian X Strike Force 

Architecture: amd64

Replaces: xserver-xorg (<< 1:7.7+10~), xserver-xorg-video-

modesetting

Provides: xorg-input-abi-22, xorg-video-abi-20, xserver-xorg-video-

modesetting

Depends: (...)

-- 
Jonás Andradas

Bug#818280: upgrade-reports: System is unusable after "aptitute safe-upgrade"

[Gilles Sadowski]

Package: upgrade-reports
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?

I first ran
 # aptitude safe-upgrade
which completed successfully.

["aptitude" automatically selected packages related to "console".]

I then installed the linux kernel 4.4 (using the available deb package from 
"unstable"),
followed by an upgrade of "firmware-linux" and "firmware-linux-nonfree".

Note: the "initramfs" operation was performed by "dracut" due to the package 
"initramfs"
crashing when called by grub (broken behaviour started about two weeks ago 
IIRC).

I then issued the command
 # reboot

The reboot/halt message appeared on the conseole, but the system did not reboot.
It was possible login and reissue the same command, to the same (non-)effect.

I powered off the machine and restarted it.

The boot sequence seemed normal until file system checks, with a message from 
systemd:
"a job is running" (or something like that).

After the 1min30s timeout I was then presented with the maintenance prompt.
Trying to continue (^D) led to this error message:

---CUT---
Error setting authority: Error initializing authority: Could not connect: No 
such file or directory (g-io-error-quark, 1)
---CUT---

With
 # journalctl -xb

I could spot problems being reported (lines prefixed with a string containing 
"systemd"):
Failed to start Conseole System Startup Logging
console-kit-log-system-start.service: Unit entered failed state
[...]
Failed to start Create Volatile Files and Directories
[...]
emergency.service: Failed at step EXEC spawning /bin/plymouth: No such file or 
directory

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

Upon rebooting, I chose the option "sysinit" (rather than the default grub 
entry).
This led to a flood of "Failed" during the boot sequence, seemingly caused by a 
read-only root filesystem.

Rebooted again, trying other entries (older kernels: 4.3 and 4.2).
All to no avail: same behaviour (either dropping to maintenance, or RO root).

   * What outcome did you expect instead?

I certainly did not expect to get an unusable system.

All this is on an installation where I *tried* to avoid "systemd": package 
"systemd-shim"
was installed.
But it seems that "systemd" is still forcefully installed (at least partially, 
since I
never asked that grub creates entries for "systemd" but they exist 
nevertheless).

I never had so many problems with Debian until this package was suddenly 
present on my
machine, without any warning that the init system was going to be completely 
different
and no way to opt out before the damage (as I would see later) was done.


Is there any option to get out of this situation, short of reinstalling the 
system?


Regards,
Gilles


-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)

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

Bug#816308: marked as done (topmenu-gtk: FTBFS: configure: error: --enable-lxpanel-plugin was given, but test for lxpanel failed)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2016 11:25:28 +
with message-id 
and subject line Bug#816308: fixed in topmenu-gtk 0.2.1+git20151210.8c6108f-3
has caused the Debian Bug report #816308,
regarding topmenu-gtk: FTBFS: configure: error: --enable-lxpanel-plugin was 
given, but test for lxpanel failed
to be marked as done.

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

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


-- 
816308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: topmenu-gtk
Version: 0.2.1+git20151210.8c6108f-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

topmenu-gtk fails to build from source in unstable/amd64:

  checking for ar... ar
  checking for archiver @FILE support... @
  checking for strip... strip
  checking for ranlib... ranlib
  checking command to parse /usr/bin/nm -B output from gcc object... ok
  checking for sysroot... no
  checking for a working dd... /bin/dd
  checking how to truncate binary pipes... /bin/dd bs=4096 count=1
  checking for mt... no
  checking if : is a manifest tool... no
  checking how to run the C preprocessor... gcc -E
  checking for ANSI C header files... yes
  checking for sys/types.h... yes
  checking for sys/stat.h... yes
  checking for stdlib.h... yes
  checking for string.h... yes
  checking for memory.h... yes
  checking for strings.h... yes
  checking for inttypes.h... yes
  checking for stdint.h... yes
  checking for unistd.h... yes
  checking for dlfcn.h... yes
  checking for objdir... .libs
  checking if gcc supports -fno-rtti -fno-exceptions... no
  checking for gcc option to produce PIC... -fPIC -DPIC
  checking if gcc PIC flag -fPIC -DPIC works... yes
  checking if gcc static flag -static works... no
  checking if gcc supports -c -o file.o... yes
  checking if gcc supports -c -o file.o... (cached) yes
  checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
  checking whether -lc should be explicitly linked in... no
  checking dynamic linker characteristics... GNU/Linux ld.so
  checking how to hardcode library paths into programs... immediate
  checking whether stripping libraries is possible... yes
  checking if libtool supports shared libraries... yes
  checking whether to build shared libraries... yes
  checking whether to build static libraries... no
  checking for pkg-config... /usr/bin/pkg-config
  checking pkg-config is at least version 0.9.0... yes
  checking for GTK... yes
  checking for X11... yes
  checking for WNCK1... yes
  checking for MATEPANELAPPLET... yes
  checking for XFCEPANELAPPLET... yes
  checking for LXPANELPLUGIN... no
  configure: error: in 
`/home/lamby/temp/cdt.20160229181627.YPdCZjB83S/topmenu-gtk-0.2.1+git20151210.8c6108f':
  configure: error: --enable-lxpanel-plugin was given, but test for lxpanel 
failed
  See `config.log' for more details
  /usr/share/cdbs/1/class/autotools.mk:42: recipe for target 
'debian/stamp-autotools' failed
  make: *** [debian/stamp-autotools] Error 1

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


topmenu-gtk.0.2.1+git20151210.8c6108f-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: topmenu-gtk
Source-Version: 0.2.1+git20151210.8c6108f-3

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated topmenu-gtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Mar 2016 11:48:21 +0100
Source: topmenu-gtk
Binary: topmenu-gtk3 topmenu-gtk3-dbg libtopmenu-client-gtk3-0 
libtopmenu-client-gtk3-dev libtopmenu-client-gtk3-dbg libtopmenu-server-gtk3-0 
libtopmenu-server-gtk3-dev libtopmenu-server-gtk3-dbg 

Bug#818278: pyzmq: binNMUs using zeromq3 4.1.x are timing out in the tests

[Matthias Klose]

Package: src:pyzmq
Version: 15.1.0-1
Severity: serious
Tags: sid stretch

According to
https://buildd.debian.org/status/package.php?p=pyzmq
tests are timing out or fail on most architectures.

Bug#817751: php-google-a* maybe not so useless (Was: Useless in Debian)

[David Prévot]

Hi Benoit,

Le 15/03/2016 04:54, Benoit Mortier a écrit :
> Le 09/03/16 21:38, David Prévot a écrit :
>> Package: php-google-api-php-client
[…]
>> Package: php-google-auth

>> [ Filled as an RC-bug by the maintainer to see the package auto-removed
>>   from testing, and not let it block the PHP 7.0 transition. ]
>>
>> I packaged php-google-api-php-client as used by owncloud
[…]
>> I intend to follow up with an RM request in a few months if nobody
>> objects (but feel free to beat me to it).

> we are the developper of FusionDirectory and we will soon have a
> google-apps plugin that will use this library
> 
> could we keep it inside debian

Let’s hold on the RM request then. Please ping us back when your plugin
is in the archive. You may wish to step up for the maintenance
(including dependencies) then: not sure I’ll stay around the PHP PEAR
(and Composer) Maintainers much longer once the ownCloud mess is done.

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#818222: libzeromq-perl: uses old libzmq1, should switch to libzmq5

[GCS]

On Mon, Mar 14, 2016 at 10:17 PM, gregor herrmann  wrote:
> On Mon, 14 Mar 2016 20:46:06 +0100, Emilio Pozuelo Monfort wrote:
>> Yes. Bumping this to RC so we don't release stretch with it, and opening
>> bugs for the rdeps.
>
> Changing the build dep from libzmq-dev to libzmq5-dev is not enough
> it seems:
[...]
 This is expected. Please note that zeromq is 2.x, while zeromq3 went
through 3.x -> 4.0.x -> 4.1.x evolution.
Please ask your upstream to port the code to the latest (4.1) zeromq version.

Regards,
Laszlo/GCS

Bug#808593: [Help]: Bug#808593: htsjdk: FTBFS: [testng] FAILED: testHTTPNotExist

[Eugene Zhukov]

On Mon, Mar 14, 2016 at 10:25 PM, Vincent Danjean  wrote:
> Le 14/03/2016 21:20, Vincent Danjean a écrit :
>> Is it the correct way to build a package that requires java 8?
>
>   I just saw that default-jre/jdk is 1.8 now, so I'm sure this
> package need to be fixed. If someone can tell me how to do it
> (or just point me to a package correctly written).

I suggest you put default-jdk (>=2:1.8) into Build-Depends instead of
openjdk-8-jre-headless and openjdk-8-jdk, and remove Build-Conflicts.

Eugene

Bug#818036: marked as done (kpartx does not ship multipathd.service but tries to start/stop that service)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2016 09:36:35 +
with message-id 
and subject line Bug#818036: fixed in multipath-tools 0.5.0+git1.656f8865-7
has caused the Debian Bug report #818036,
regarding kpartx does not ship multipathd.service but tries to start/stop that 
service
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.)


-- 
818036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kpartx
Version: 0.5.0+git1.656f8865-6
Severity: important

The maintainers scripts of kpartx try to start/stop multipathd.service
That service unit is shipped in the multipath-tools package though.
So this looks like an error in debian/rules.
Combining -a and -p doesn't really make sense.


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

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

Versions of packages kpartx depends on:
ii  dmsetup 2:1.02.116-1+b1
ii  libc6   2.22-2
ii  libdevmapper1.02.1  2:1.02.116-1+b1
ii  udev229-2

kpartx recommends no packages.

kpartx suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: multipath-tools
Source-Version: 0.5.0+git1.656f8865-7

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

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

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated multipath-tools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 Mar 2016 13:35:08 +0530
Source: multipath-tools
Binary: multipath-tools multipath-tools-dbg kpartx multipath-tools-boot 
multipath-udeb kpartx-udeb
Architecture: source amd64 all
Version: 0.5.0+git1.656f8865-7
Distribution: unstable
Urgency: medium
Maintainer: Debian LVM Team 
Changed-By: Ritesh Raj Sarraf 
Description:
 kpartx - create device mappings for partitions
 kpartx-udeb - create device mappings for partitions - udeb package (udeb)
 multipath-tools - maintain multipath block device access
 multipath-tools-boot - Support booting from multipath devices
 multipath-tools-dbg - maintain multipath block device access - debugging 
symbols
 multipath-udeb - maintain multipath block device access - udeb package (udeb)
Closes: 818036
Changes:
 multipath-tools (0.5.0+git1.656f8865-7) unstable; urgency=medium
 .
   * [72c07f4] Fix kpartx depending of non-existent service.
 Thanks to Michael Biebl (Closes: 818036)
Checksums-Sha1:
 5b6c863dde6b080b56c7d56e08ebc27e95a640a4 2587 
multipath-tools_0.5.0+git1.656f8865-7.dsc
 9605195d7d2459048b38d4a4824b50ef9640646d 26592 
multipath-tools_0.5.0+git1.656f8865-7.debian.tar.xz
 592e49102df066229fe8b00d0ed00102c9603dfb 15546 
kpartx-udeb_0.5.0+git1.656f8865-7_amd64.udeb
 bf2bba19a7d7cc43e8d880113aaca8079fd47416 32224 
kpartx_0.5.0+git1.656f8865-7_amd64.deb
 ca14e0ef155a583c3ae87136e492af5ef702a4d2 19906 
multipath-tools-boot_0.5.0+git1.656f8865-7_all.deb
 170f07d55dbac5a8376892712344f2e399e6047d 387994 
multipath-tools-dbg_0.5.0+git1.656f8865-7_amd64.deb
 6465413a50d24d42b38f7667e4142d35d0ce0735 198350 
multipath-tools_0.5.0+git1.656f8865-7_amd64.deb
 9771a19ed455f6b8eaa27fa2dfc2e2dc1a958670 126502 
multipath-udeb_0.5.0+git1.656f8865-7_amd64.udeb
Checksums-Sha256:
 dc5c8706feeb550c8a89dc7c63b2531d2a1393adb8ae97b4e856993c8e86c3f5 2587 
multipath-tools_0.5.0+git1.656f8865-7.dsc
 ff9de32fa0fc367d31d29fbd9774ccf3954b6b8bcce09618ce1df428f59aa10f 26592 
multipath-tools_0.5.0+git1.656f8865-7.debian.tar.xz
 dce0578dd5787b31fbd5d4aaba31d05a018db5506261f4e234c4a2ecd7f6da78 15546 
kpartx-udeb_0.5.0+git1.656f8865-7_amd64.udeb
 8a53437c488103d7eb82b7ba6e9ac04712f5a6a24b9f1d518e70ddf9be9c3db1 

Bug#817884: Don't try to dlopen(libm.so)

[Alastair McKinstry]

Following the discussion in #817988, I tested a one-line patch for
test_dl.py
changing 'libm.so' to 'libm.so.6' which solves this issue.

regards
Alastair

-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 




signature.asc
Description: OpenPGP digital signature

Bug#818187: zeromq3 migrated without any transition being done

[Emilio Pozuelo Monfort]

On 14/03/16 22:03, Emilio Pozuelo Monfort wrote:

On 14/03/16 21:55, László Böszörményi (GCS) wrote:

On Mon, Mar 14, 2016 at 8:58 PM, Emilio Pozuelo Monfort
 wrote:

Renaming a -dev package because the soname changed is bad. The only reason
to do it in this case is so that things don't look "odd".

  The main reason the soname is in the -dev package name is that the
simple 'libzmq-dev' is part of the zeromq package. But yes, it could
have remain as libzmq3-dev even if it looks inconsistent with libzm5.

 >

What I think should happen here is:

The package is renamed back to libzmq3-dev, so rdeps can be binNMUed.

A provides can be added for the packages that changed, since their
build-deps are not versioned. After libzmq5-dev is decrufted, they will be
fine.

Then the transition can complete.

How does that sound?

  I see and agree. Attached the next upload just to be sure. Please ACK
it and I'll upload it.

Sorry for the extra round,


Looks good. No problem and thanks for reacting that fast!


I scheduled the binNMUs last night and things are going well. The only issue 
seems to be pyzmq, see #818265.


Emilio

Bug#818265: pyzmq: FTBFS with newest zeromq3

[Emilio Pozuelo Monfort]

Source: pyzmq
Version: 15.1.0-1
Severity: serious

Your package failed to build on several architectures on a rebuild
against libzmq5:

https://buildd.debian.org/status/logs.php?pkg=pyzmq=15.1.0-1%2Bb2

Emilio

Bug#817754: [pkg-php-pear] Bug#817754: Useless in Debian

[Benoit Mortier]

Le 09/03/16 22:38, David Prévot a écrit :
> Package: php-google-auth
> Version: 0.6-1
> Severity: serious
> 
> [ Filled as an RC-bug by the maintainer to see the package auto-removed
>   from testing, and not let it block the PHP 7.0 transition. ]
> 
> I recently packaged php-google-auth as used by
> php-google-api-php-client, as used by owncloud, but owncloud is going
> away, see #816376 (so is php-google-api-php-client, see #817750). There
> is a priori little point to ship php-google-auth in a Debian stable
> release.
> 
> I intend to follow up with an RM request in a few months if nobody
> objects (but feel free to beat me to it).

Hello,

we are the developper of FusionDirectory and we will soon have a
google-apps plugin that will use this library

could we keep it inside debian

Cheers
-- 
Benoit Mortier
CEO
OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
Promouvoir et défendre le Logiciel Libre http://www.april.org/
Main developper in FusionDirectory : http://www.fusiondirectory.org/
Official French representative for OPSI : http://opsi.org/



signature.asc
Description: OpenPGP digital signature

Bug#817751: [pkg-php-pear] Bug#817751: Useless in Debian

[Benoit Mortier]

Le 09/03/16 21:38, David Prévot a écrit :
> Package: php-google-api-php-client
> Version: 0.6.7-2
> Severity: serious
> Tags: sid stretch
> 
> [ Filled as an RC-bug by the maintainer to see the package auto-removed
>   from testing, and not let it block the PHP 7.0 transition. ]
> 
> I packaged php-google-api-php-client as used by owncloud, but owncloud
> is going away, see #816376. There is a priori little point to ship
> php-google-api-php-client in the next Debian stable release.
> 
> I intend to follow up with an RM request in a few months if nobody
> objects (but feel free to beat me to it).

Hello,

we are the developper of FusionDirectory and we will soon have a
google-apps plugin that will use this library

could we keep it inside debian

Cheers
-- 
Benoit Mortier
CEO
OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
Promouvoir et défendre le Logiciel Libre http://www.april.org/
Main developper in FusionDirectory : http://www.fusiondirectory.org/
Official French representative for OPSI : http://opsi.org/



signature.asc
Description: OpenPGP digital signature

Bug#818257: marked as done (xtables-addons-source: Build fails with two errors)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2016 19:54:07 +1100
with message-id <47180814.5aZSn4DiRg@deblab>
and subject line Re: Bug#818257: xtables-addons-source: Build fails with two 
errors
has caused the Debian Bug report #818257,
regarding xtables-addons-source: Build fails with two errors
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.)


-- 
818257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xtables-addons-source
Version: 2.6-1
Severity: serious
Justification: fails to build from source

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 4.4.0-kirkwood-tld-1 (PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages xtables-addons-source depends on:
ii  bzip2 1.0.6-7+b3
ii  debhelper 9.20150101
ii  iptables-dev  1.4.21-2+b1
ii  make  4.0-8.1
ii  pkg-config0.28-1

Versions of packages xtables-addons-source recommends:
ii  module-assistant  0.11.7

xtables-addons-source suggests no packages.

-- no debconf information
Build of xtables-addons-source fails.  Build log attached below


cat xtables-addons-source.buildlog.4.4.0-kirkwood-tld-1.1456486168
/usr/bin/make -C /usr/src/linux M=/usr/src/modules/xtables-addons/extensions 
XA_ABSTOPSRCDIR=/usr/src/modules/xtables-addons 
XA_TOPSRCDIR=/usr/src/modules/xtables-addons DEPMOD=/bin/true clean
make[1]: Entering directory '/usr/src/linux-headers-4.4.0-kirkwood-tld-1'
make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-kirkwood-tld-1'
dh_auto_clean
make[1]: Entering directory '/usr/src/modules/xtables-addons'
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash 
/tmp/buildd/xtables-addons-2.6/build-aux/missing autoconf
Makefile:402: recipe for target 'configure' failed
make[1]: Leaving directory '/usr/src/modules/xtables-addons'
debian/rules:59: recipe for target 'override_dh_auto_clean' failed
hostname: Name or service not known
/usr/bin/make  -f debian/rules kdist_clean kdist_config binary-modules
make[1]: Entering directory '/usr/src/modules/xtables-addons'
hostname: Name or service not known
/usr/bin/make -C /usr/src/linux M=/usr/src/modules/xtables-addons/extensions 
XA_ABSTOPSRCDIR=/usr/src/modules/xtables-addons 
XA_TOPSRCDIR=/usr/src/modules/xtables-addons DEPMOD=/bin/true clean
make[2]: Entering directory '/usr/src/linux-headers-4.4.0-kirkwood-tld-1'
make[2]: Leaving directory '/usr/src/linux-headers-4.4.0-kirkwood-tld-1'
dh_auto_clean
make[2]: Entering directory '/usr/src/modules/xtables-addons'
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash 
/tmp/buildd/xtables-addons-2.6/build-aux/missing autoconf
/bin/bash: /tmp/buildd/xtables-addons-2.6/build-aux/missing: No such file or 
directory
Makefile:402: recipe for target 'configure' failed
make[2]: *** [configure] Error 127
make[2]: Leaving directory '/usr/src/modules/xtables-addons'
dh_auto_clean: make -j1 distclean returned exit code 2
debian/rules:59: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 2
make[1]: Leaving directory '/usr/src/modules/xtables-addons'
/usr/share/modass/include/common-rules.make:56: recipe for target 'kdist_build' 
failed
make: *** [kdist_build] Error 2
--- End Message ---
--- Begin Message ---
Package: xtables-addons-source
Version: 2.10-1

On Tuesday, 15 March 2016 7:48:06 AM AEDT root wrote:
> Package: xtables-addons-source
> Version: 2.6-1
> Severity: serious
> Justification: fails to build from source
> 
> [...]
> 
> Debian Release: 8.3
> 
> Kernel: Linux 4.4.0-kirkwood-tld-1 (PREEMPT)

Please do not complain that package in "stable" fails to build with 
unsupported kernel. Support for kernel 4.4 was introduced in xtables-addons 
2.10 that you can find in "testing" suite.
Therefore I'm closing this bug as "invalid".

Besides "xtables-addons-dkms" probably will work better for you than 
"xtables-addons-source".

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

Processed: fixed 818257 in 2.10-1

[Debian Bug Tracking System]

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

> fixed 818257 2.10-1
Bug #818257 [xtables-addons-source] xtables-addons-source: Build fails with two 
errors
Marked as fixed in versions xtables-addons/2.10-1.
> thanks
Stopping processing here.

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

Bug#818261: git usage in gemspec

[Matthias Klose]

Package: src:ruby-github-markdown
Version: 1.3.3+dfsg-1
Severity: serious
Tags: sid stretch
Justification: Breaks rdeps when binary-rebuilt

When rebuiling ruby-github-markdown in unstable, the .gemspec is missing in
the built binaries. This causes rdeps to fail to resolve their
dependencies.

It's unclear how this package ever managed to get a .gemspec into
the binary.

see buildlog at
https://launchpadlibrarian.net/228973061/buildlog_ubuntu-xenial-amd64.ruby-github-markup_1.3.3+dfsg-1_BUILDING.txt.gz

Bug#818260: sup-mail: crashes on start: "cannot load such file -- _xapian (LoadError)"

[Antonio Sartori]

Package: sup-mail
Version: 0.22.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

sup-mail crashes on start with the following output:

/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot 
load such file -- _xapian (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/vendor_ruby/xapian.rb:42:in `'
from /usr/lib/ruby/vendor_ruby/xapian.rb:40:in `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/vendor_ruby/sup/index.rb:4:in `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/vendor_ruby/sup.rb:428:in `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/bin/sup-mail:20:in `'


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

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

Versions of packages sup-mail depends on:
ii  ruby1:2.3.0+1
ii  ruby-chronic0.10.2-3
ii  ruby-highline   1.7.2-1
ii  ruby-locale 2.1.2-1
ii  ruby-lockfile   2.1.3-1
ii  ruby-mime-types 2.6.1-1
ii  ruby-ncurses1.4.9-1
ii  ruby-rubymail   1.1.0-2
ii  ruby-trollop2.0-2
ii  ruby-unicode0.4.4-2+b6
ii  ruby-xapian 1.2.22-2
ii  ruby2.1 [ruby-interpreter]  2.1.5-4
ii  ruby2.2 [ruby-interpreter]  2.2.4-1
ii  ruby2.3 [ruby-interpreter]  2.3.0-4

Versions of packages sup-mail recommends:
ii  ruby-gpgme  2.0.12-1

sup-mail suggests no packages.

-- no debconf information

Bug#818259: git usage in gemspec

[Matthias Klose]

Package: src:ruby-fog-atmos
Version: 0.1.0-2
Severity: serious
Tags: sid stretch
Justification: Breaks rdeps when binary-rebuilt

When rebuiling ruby-fog-atmos in unstable, the .gemspec is missing in
the built binaries. This causes rdeps to fail to resolve their
dependencies.

It's unclear how this package ever managed to get a .gemspec into
the binary.

see
https://launchpadlibrarian.net/216782808/buildlog_ubuntu-wily-amd64.ruby-fog-atmos_0.1.0-2build1_BUILDING.txt.gz

Bug#818258: ruby-em-synchrony: FTBFS: undefined method `client=' for AMQP:Module (NoMethodError)

[Chris Lamb]

Source: ruby-em-synchrony
Version: 1.0.4-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-em-synchrony fails to build from source in unstable/amd64:

  [..]

  2016-03-15 07:47:10 5587 [Note] InnoDB: The InnoDB memory heap is disabled
  2016-03-15 07:47:10 5587 [Note] InnoDB: Mutexes and rw_locks use GCC atomic 
builtins
  2016-03-15 07:47:10 5587 [Note] InnoDB: Memory barrier is not used
  2016-03-15 07:47:10 5587 [Note] InnoDB: Compressed tables use zlib 1.2.8
  2016-03-15 07:47:10 5587 [Note] InnoDB: Using Linux native AIO
  2016-03-15 07:47:10 5587 [Note] InnoDB: Using CPU crc32 instructions
  2016-03-15 07:47:10 5587 [Note] InnoDB: Initializing buffer pool, size = 
128.0M
  2016-03-15 07:47:10 5587 [Note] InnoDB: Completed initialization of buffer 
pool
  2016-03-15 07:47:10 5587 [Note] InnoDB: Highest supported file format is 
Barracuda.
  2016-03-15 07:47:10 5587 [Note] InnoDB: 128 rollback segment(s) are active.
  2016-03-15 07:47:10 5587 [Note] InnoDB: Waiting for purge to start
  2016-03-15 07:47:10 5587 [Note] InnoDB: 5.6.28 started; log sequence number 
1625987
  2016-03-15 07:47:10 5587 [Warning] No existing UUID has been found, so we 
assume that this is the first time that this server has been started. 
Generating a new UUID: 1ffb7e6c-ea82-11e5-86b7-0242ac110402.
  2016-03-15 07:47:10 5587 [Note] Event Scheduler: Loaded 0 events
  2016-03-15 07:47:10 5587 [Note] /usr/sbin/mysqld: ready for connections.
  Version: '5.6.28-1'  socket: '/tmp/tmp.jOwet2Dam4/mysql.sock'  port: 0  
(Debian)
  mysqld is alive
  /usr/lib/ruby/vendor_ruby/em-redis/redis_protocol.rb:72: warning: key 
"list_range" is duplicated and overwritten on line 121
  /usr/lib/ruby/vendor_ruby/em-redis/redis_protocol.rb:104: warning: key 
"members" is duplicated and overwritten on line 135
  
/home/lamby/temp/cdt.20160315074619.13UnpA3q1f/ruby-em-synchrony-1.0.4/lib/em-synchrony/amqp.rb:189:in
 `': undefined method `client=' for AMQP:Module (NoMethodError)
from 
/home/lamby/temp/cdt.20160315074619.13UnpA3q1f/ruby-em-synchrony-1.0.4/lib/em-synchrony/amqp.rb:10:in
 `'
from 
/home/lamby/temp/cdt.20160315074619.13UnpA3q1f/ruby-em-synchrony-1.0.4/lib/em-synchrony/amqp.rb:9:in
 `'
from 
/home/lamby/temp/cdt.20160315074619.13UnpA3q1f/ruby-em-synchrony-1.0.4/lib/em-synchrony/amqp.rb:8:in
 `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160315074619.13UnpA3q1f/ruby-em-synchrony-1.0.4/spec/helper/all.rb:8:in
 `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160315074619.13UnpA3q1f/ruby-em-synchrony-1.0.4/spec/activerecord_spec.rb:1:in
 `'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1361:in 
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1361:in 
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1359:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1359:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:106:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:92:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:78:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
from /usr/bin/rspec:4:in `'
  rake aborted!
  Command failed with status (1): [./debian/start_services_and_run.sh 
ruby2.3...]
  
/home/lamby/temp/cdt.20160315074619.13UnpA3q1f/ruby-em-synchrony-1.0.4/debian/ruby-tests.rake:5:in
 `block in '
  Tasks: TOP => default
  (See full trace by running task with --trace)
  ERROR: Test "ruby2.3" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160315074619.13UnpA3q1f/ruby-em-synchrony-1.0.4/debian/ruby-em-synchrony
 returned exit code 1
  debian/rules:15: recipe for target 'binary' failed
  make: *** [binary] Error 1

The build then hangs. The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


ruby-em-synchrony.1.0.4-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808593: [Help]: Bug#808593: htsjdk: FTBFS: [testng] FAILED: testHTTPNotExist

[Olivier Sallou]

- Mail original -
> De: "Vincent Danjean" 
> À: "Emmanuel Bourg" , "Andreas Tille" , 
> "Debian Java List"
> , 808...@bugs.debian.org
> Envoyé: Lundi 14 Mars 2016 21:20:11
> Objet: Re: [Help]: Bug#808593: htsjdk: FTBFS: [testng] FAILED: 
> testHTTPNotExist
> 
> Le 11/02/2016 21:50, Emmanuel Bourg a écrit :
> > Le 11/02/2016 21:01, Andreas Tille a écrit :
> > 
> >> any hint why this test that worked before might fail since end of
> >> December?
> > 
> > I got a quick look and I can't explain this test failure. It doesn't
> > seem very important though, you could just disable this test.
> 
> I just upgraded htsjdk (required for picard-tools). It does not seem to
> FTBFS anymore (pushed in git).

yeap, I checked this with Andreas some time ago, and could not reproduce either.

>   I plan to upload it when picard-tools will be ready but if someone
> can take a look at it before, I would be pleased. In particular,
> there is in debian/control:
> ===
> Build-Depends: openjdk-8-jre-headless, openjdk-8-jdk, ...
> Build-Conflicts: openjdk-7-jre-headless
> ===
> 
> And, in debian/rules:
> ===
>   dh_auto_build -- -Dant.build.javac.source=1.8 -Dant.build.javac.target=1.8
>   ...
> ===
> 
> Is it the correct way to build a package that requires java 8?

as long as target is not specifically set in build.xml that's the way.

Olivie

> 
> I do not change this part myself and did not check the requirement,
> but I just saw with picard-tools (same upstream authors) that java 8
> is also required ( <> operator (>=7) and lambda expressions (>=8) )
> so I would like to be sure to do the correct thing.
> 
>   Regards,
> Vincent
> 
> > Emmanuel Bourg
> > 
> 
> 
> --
> Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
> GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
> Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
> APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main
> 
> 

Bug#816041: marked as done (ldap-account-manager depends on php5-imagick which is no longer built)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2016 06:19:29 +
with message-id 
and subject line Bug#816041: fixed in ldap-account-manager 5.2-2
has caused the Debian Bug report #816041,
regarding ldap-account-manager depends on php5-imagick which is no longer built
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.)


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

Package: ldap-account-manager
Severity: serious
Version: 5.2-1

ldap-account-manager depends on php5-imagick which is no longer built by 
the source package php-imagick.


I'm not sure if you can just change the dependency to php-imagick or if 
more work is needed.
--- End Message ---
--- Begin Message ---
Source: ldap-account-manager
Source-Version: 5.2-2

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

Debian distribution maintenance software
pp.
Roland Gruber  (supplier of updated ldap-account-manager 
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, 06 Mar 2016 09:31:23 +0100
Source: ldap-account-manager
Binary: ldap-account-manager ldap-account-manager-lamdaemon
Architecture: source all
Version: 5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Roland Gruber 
Changed-By: Roland Gruber 
Description:
 ldap-account-manager - webfrontend for managing accounts in an LDAP directory
 ldap-account-manager-lamdaemon - Quota and home directory management for LDAP 
Account Manager
Closes: 816041
Changes:
 ldap-account-manager (5.2-2) unstable; urgency=medium
 .
   * Fix "ldap-account-manager depends on php5-imagick which is no longer
 built" by changing dependencies (Closes: #816041)
Checksums-Sha1:
 fb10acde990d847770e9d1eff9b172bbf6eb7ee1 1932 ldap-account-manager_5.2-2.dsc
 34dd1efeb3647fcf30525023c1cd6fb88f2bb28f 21204 
ldap-account-manager_5.2-2.debian.tar.xz
 5d3c3d57ba7fafa7cf503fcf1bd9a7731459d2cc 22546 
ldap-account-manager-lamdaemon_5.2-2_all.deb
 50171a624ad378136762e20333011432e14ce3c1 12149104 
ldap-account-manager_5.2-2_all.deb
Checksums-Sha256:
 e412d66f23a4838d7ee03ada7a302d0854b0334359f2e60dbbf9f15feb254ea3 1932 
ldap-account-manager_5.2-2.dsc
 fd5620e374ffdbb4320b97fac035c5df154825e83a4ff88919fc352396c3c4c3 21204 
ldap-account-manager_5.2-2.debian.tar.xz
 afb6035fa53913001a09929064151ada87d4aaafef1f1b1aaef89bf4a134eabe 22546 
ldap-account-manager-lamdaemon_5.2-2_all.deb
 cc273fb4d1470158e76637151a7f3a8f8ae0ea21a6506a3e572d99c110baae3d 12149104 
ldap-account-manager_5.2-2_all.deb
Files:
 4ef300c6f23f7908dbe662c2fc842748 1932 web extra ldap-account-manager_5.2-2.dsc
 32f843c252bdcb969fc580457c79bf16 21204 web extra 
ldap-account-manager_5.2-2.debian.tar.xz
 e1febfdc1629b48cc1abfb7678a97c36 22546 web extra 
ldap-account-manager-lamdaemon_5.2-2_all.deb
 f4ed883a730e51863e0664d6eea568d1 12149104 web extra 
ldap-account-manager_5.2-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJW56bNAAoJEIRzBit88JS6zE4QAJNdOLoPLUbcxjtodB8d1xBI
DW+/vd8+l4FgNhivAYr9hkamFECVk2/maJGn59XNFUWQufVoySI+qoOg+va5HgbF
CVQGxn3D/IGbd0Ui2Sdw9kTFW3CIpD2HqSsO1kuNIONDewhGa1v7T+YRuTexE+GZ
ULtUQ0BJPgO65Kvty+pQrWVMy49HwtjG3fELi0BULGq1HOiQGjBQ1MceBIOp47PO
kyeHTXTXNwGn5tnH1ed7bUKHVYQXDkWYQrqllcpesmxxE6TfZuUNGUpoDO+NHlCZ
AvIkjF8PeXKw1Wcu0Uu1F94plGRA5+SUR3XWZqGeaIZmqpJO9Thh9FwndrTEiKq4
pzi3IafaBnHd7YpuTjk7Z29egqr/rfPiC1XESeMOgMO6HUB+RukT3IjXOOJL/AE4
t4XLDCURenxYtyrQCGZDgH87kdYTFRmCQy38vVQJ7mNC2ULCxif0Ac8Pd9fOQMQa
UDUyXkmCaLaSC9Ou0QJ+iCKyoe9ksu8nR75WK/hEnAYtrR+Bse9GFkPX0nuss+Gv
ZRJ05PEu6y8bgLwOUc4Jcc3Rt24NdIafoWmu6wYDJas9UdKdngJMf1jD1w7wjyo9
5BgLkS2TDP7uMnajUBYR7l8ZZIyi7d3Jb3V0tpUvhTS5ZLTQhL4GLOG7+uX9IcIk
Fmw7/uQa5KjKAh3oCkmJ
=WCdv
-END PGP SIGNATURE End Message ---

Bug#815004: marked as done (Engine is installed at wrong location)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2016 06:19:09 +
with message-id 
and subject line Bug#815004: fixed in engine-pkcs11 0.2.1-2
has caused the Debian Bug report #815004,
regarding Engine is installed at wrong location
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.)


-- 
815004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libengine-pkcs11-openssl
Version: 0.2.1-1
Severity: grave
Justification: makes the package in question unusable

Hi,

After installing libengine-pkcs11-openssl, the following happens:

wouter@gangtai:~$ openssl engine pkcs11 -t
139772252497552:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
the shared 
library:dso_dlfcn.c:187:filename(/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libpkcs11.so):
 /usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libpkcs11.so: cannot open 
shared object file: No such file or directory
139772252497552:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:232:
139772252497552:error:260B6084:engine routines:DYNAMIC_LOAD:dso not 
found:eng_dyn.c:465:
139772252497552:error:2606A074:engine routines:ENGINE_by_id:no such 
engine:eng_list.c:390:id=pkcs11

This is because libengine-pkcs11-openssl writes its engine files to
/usr/lib/ssl/engines rather than the location where current OpenSSL
looks for engines.

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

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

Versions of packages libengine-pkcs11-openssl depends on:
ii  libc62.21-8
ii  libp11-2 0.3.1-1
ii  libssl1.0.2  1.0.2f-2

libengine-pkcs11-openssl recommends no packages.

libengine-pkcs11-openssl suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: engine-pkcs11
Source-Version: 0.2.1-2

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

Debian distribution maintenance software
pp.
Eric Dorland  (supplier of updated engine-pkcs11 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Mar 2016 01:23:30 -0400
Source: engine-pkcs11
Binary: libengine-pkcs11-openssl
Architecture: source amd64
Version: 0.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSC Maintainers 
Changed-By: Eric Dorland 
Description:
 libengine-pkcs11-openssl - OpenSSL engine for PKCS#11 modules
Closes: 815004
Changes:
 engine-pkcs11 (0.2.1-2) unstable; urgency=medium
 .
   * debian/control, debian/rules, debian/libengine-pkcs11-openssl.install:
 Install engine into the current openssl engine directory. (Closes:
 #815004)
   * debian/libengine-pkcs11-openssl.links: Drop compatibility symlink.
   * debian/control: Standards-Version to 3.9.7.
   * debian/control: Mark as Multi-Arch: same.
Checksums-Sha1:
 ac195e9fea748388abbe1b18d7a5d567f51a8323 2062 engine-pkcs11_0.2.1-2.dsc
 377e32c661a944daf67fdb5a73bea6b0e067f476 6596 
engine-pkcs11_0.2.1-2.debian.tar.xz
 2d9600215516825269d1da1636bc5d1dd0ffcd67 25254 
libengine-pkcs11-openssl-dbgsym_0.2.1-2_amd64.deb
 fdde2486c2e34cc1b9abb89cab82f973661f4106 14752 
libengine-pkcs11-openssl_0.2.1-2_amd64.deb
Checksums-Sha256:
 98212adcede7230b439dfe856002493ced267ffe602bbf50ad8820ffd3f3b313 2062 
engine-pkcs11_0.2.1-2.dsc
 44c0ac6c660a185788aeacce5023cfe2e75b906e37703096916b9b1fcfc06eb9 6596 
engine-pkcs11_0.2.1-2.debian.tar.xz
 679484a34fb432b5fdcd377a4ce54b4565dabb0435d6b62044e736b6d136 25254 
libengine-pkcs11-openssl-dbgsym_0.2.1-2_amd64.deb
 d7d92211320a72eb43ca8e131772cea5b37a81aaae2a6b67d86f36ec18c9a613 14752 

Bug#810360: marked as done (ugene: switch B-D to libprocps-dev)

[Debian Bug Tracking System]

Your message dated Tue, 15 Mar 2016 06:20:22 +
with message-id 
and subject line Bug#810360: fixed in ugene 1.21.0+dfsg-1
has caused the Debian Bug report #810360,
regarding ugene: switch B-D to libprocps-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.)


-- 
810360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ugene
Version: 1.19.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

libprocps4-dev is history, please switch to libprocps-dev.


Andreas
--- End Message ---
--- Begin Message ---
Source: ugene
Source-Version: 1.21.0+dfsg-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated ugene 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, 14 Mar 2016 19:19:42 +0100
Source: ugene
Binary: ugene ugene-data
Architecture: source all amd64
Version: 1.21.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 ugene  - integrated bioinformatics toolkit
 ugene-data - required data for UGENE - integrated bioinformatics toolkit
Closes: 810360
Changes:
 ugene (1.21.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream version
 Closes: #810360
   * Use xz compression in d/watch
Checksums-Sha1:
 0ffd67a368bdf729d8e9c405de18ddd118137eb1 2311 ugene_1.21.0+dfsg-1.dsc
 273f53caaa3dd079abaa339595ca230d05585f61 15760468 ugene_1.21.0+dfsg.orig.tar.xz
 dcef70469c725d13f8828ef77eb8cec9140395f9 11076 
ugene_1.21.0+dfsg-1.debian.tar.xz
 1285344527d636125fb026612b161d22f9780a42 6445248 
ugene-data_1.21.0+dfsg-1_all.deb
 a52a3431a3fd5036d4ada252282631b55d0092f9 326816182 
ugene-dbgsym_1.21.0+dfsg-1_amd64.deb
 200cf2e13b5b4282c2e0167c60bbc757d04a42c6 18132006 ugene_1.21.0+dfsg-1_amd64.deb
Checksums-Sha256:
 cc2724df2df4071f8bb965ff2b0aef5874768a6375926d20c49193c013136720 2311 
ugene_1.21.0+dfsg-1.dsc
 92159a988e922a6d9abc587d1ae57636d6431763c0600fb553102048863e3a07 15760468 
ugene_1.21.0+dfsg.orig.tar.xz
 c5ee00fea889e8d8a61f5fb59b54e9d89e45acd5fe4ef4a30b83c89ee753797e 11076 
ugene_1.21.0+dfsg-1.debian.tar.xz
 bad6596108c98f43ddde2314ede6ccfe5366b786c7c52c94ba83dfe9b89c62eb 6445248 
ugene-data_1.21.0+dfsg-1_all.deb
 8d415efda8173ab0d337733b8294e9ce443bbe4c1abb80ad3a58344c7b315372 326816182 
ugene-dbgsym_1.21.0+dfsg-1_amd64.deb
 da48287b0da68676687d4450bb73814a8d273472c8c9150b70a1da99de9e67ff 18132006 
ugene_1.21.0+dfsg-1_amd64.deb
Files:
 c888927212196d184eb95ea85c529723 2311 non-free/science optional 
ugene_1.21.0+dfsg-1.dsc
 ee46f3bd6ade7dd16c8d8dfb55048f41 15760468 non-free/science optional 
ugene_1.21.0+dfsg.orig.tar.xz
 8a42553c36d27bf654b34ae1da80edca 11076 non-free/science optional 
ugene_1.21.0+dfsg-1.debian.tar.xz
 0cb445100b76a74ce1a95e64cd39b878 6445248 non-free/science optional 
ugene-data_1.21.0+dfsg-1_all.deb
 d2e6f1e73a732a3ce6d49a2292ab2202 326816182 non-free/debug extra 
ugene-dbgsym_1.21.0+dfsg-1_amd64.deb
 39d523faea4babdbc405206960f15664 18132006 non-free/science optional 
ugene_1.21.0+dfsg-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJW5xldAAoJEFeKBJTRxkbR+cwP/1JutLe3aEwEso65b5IIHBqw
lxRcWyuk9Tvvg33bLkDlThBqhXsMG50Y3LQ9Fpz4Xj++zOQFIKCwSnqquVFZsR39
NHzb7VyMfwWPNH7rNL/VhzcMurr5QTXJG53kW3yGfLkW4MOuL9Inho8ivc0vaEP0
/ba2IjgkjawQocpoQWA7q19a7gIlYvGHL1DynHVlRSeGHsBv6DZyksvy/R3zOXD6
BqYQelWJpbAwnNxQoXPI+Wn2iUJUaD4PAa9tUGQgFTq5cre+kxj9OPrvched2qGa
RKIjuLvyyiNm7x0ZJ4wJwZs5a4ww3mhzvpIuyvyCUvxeDQ94WnSFRm7vhVjM/8rC
w93f2nIUxBINb+xlUc5dNKhpIkQy7cdQ76gAU/O1aAIupywDuZInxUFRaypNOp7M
qecjz8IK1PDArCrIDU7LEimVFXlYAEOglLylDa0oJSQvJx0K7fVhyvRj1UoGSSdH
aA7hcDqw5FYU5Ow/RqWVUOKxxKARYlmuM1iTawWjP47XxCLaGvBcg79fp3ohcMeh
6FXY+EhOFDEoQ0am50p9n5TrvrNCnne2iKpg4/s2/QbGFXoWhzK4SpkvxdpiSAFo

Bug#815004: marked as pending

[Eric Dorland]

tag 815004 pending
thanks

Hello,

Bug #815004 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:

http://git.debian.org/?p=pkg-opensc/engine-pkcs11.git;a=commitdiff;h=0f9adff

---
commit 0f9adff289380caf2887276d6e979871dbe174ba
Author: Eric Dorland 
Date:   Tue Mar 15 01:15:40 2016 -0400

Install engine into the current openssl engine directory

Closes: 815004

diff --git a/debian/changelog b/debian/changelog
index 1996eb6..b22ae83 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+engine-pkcs11 (0.2.1-2) unstable; urgency=medium
+
+  * debian/control, debian/rules, debian/libengine-pkcs11-openssl.install:
+Install engine into the current openssl engine directory. (Closes:
+#815004)
+
+ --
+
 engine-pkcs11 (0.2.1-1) unstable; urgency=medium
 
   * New upstream release.

Processed: Bug#815004 marked as pending

[Debian Bug Tracking System]

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

> tag 815004 pending
Bug #815004 [libengine-pkcs11-openssl] Engine is installed at wrong location
Added tag(s) pending.
> thanks
Stopping processing here.

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