Bug#811862: fixed in libqalculate 0.9.10-1

[Vincent Legout]

Hi Emilio,

On Sun, Nov 06, 2016 at 04:24:29PM +0100, Emilio Pozuelo Monfort wrote :
> Hi,
> 
> On Thu, 08 Sep 2016 07:00:09 + Vincent Legout  wrote:
> >  libqalculate (0.9.10-1) experimental; urgency=medium
> >  .
> >* Upload to experimental
> >* New upstream version
> >  - Fix FTBFS with gcc 6 (Closes: #811862)
> 
> This is still unfixed in unstable. Any plans for a fix there?

I apologize, I was planning to transition this new package to unstable but
didn't find the time to do so before the transition freeze. I guess it's now too
late for that, and Matthias uploaded a fix for this bug in the meantime (thanks
for that).

Thanks for your work,

Vincent

Processed: your mail

[Debian Bug Tracking System]

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

> notfound 842695 0.9.4c-4
Bug #842695 {Done: Gianfranco Costamagna } [src:lirc] 
lirc: block testing migration
No longer marked as found in versions lirc/0.9.4c-4.
> thanks
Stopping processing here.

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

Bug#833245: openssl-blacklist: Uses obsolete compressor for .deb data.tar member

[Moritz Muehlenhoff]

On Tue, Aug 02, 2016 at 04:05:45AM +0200, Guillem Jover wrote:
> Source: openssl-blacklist
> Source-Version: 0.5-3
> Severity: important
> User: debian-d...@lists.debian.org
> Usertags: dpkg-obsolete-deb-data-tar-compressor
> 
> Hi!
> 
> This source package builds one or more binary packages using the
> deprecated compressor bzip2. The default has been xz for a while now
> which should usually compress better than bzip2. If instead you'd like
> speed then switch to use gzip.
> 
> Using a deprecated compressor when building binary packages will
> become an error in the near future. Please update the packages.
> 
> See also .

Instead of fixing this, should we just remove the package? It's been almost
a decade since CVE-2008-0166 happened, I don't think it serves any purpose
any longer.

Cheers,
Moritz

Bug#842878: marked as done (Asterisk crashes with pjproject 2.5.5)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2016 08:29:31 +0100
with message-id <2016072931.ga32...@fliwatuet.svr02.mucip.net>
and subject line Re: Bug#842878: Asterisk crashes with pjproject 2.5.5
has caused the Debian Bug report #842878,
regarding Asterisk crashes with pjproject 2.5.5
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.)


-- 
842878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: asterisk
Version: 1:13.11.2~dfsg-1

Hi,

Not sure if this should be filed against asterisk or pjproject.

I've just tried upgrading the pjproject libraries to version 2.5.5~dfsg-1 from 
sid.

With this version, asterisk seems to just exit when trying to dial the inner 
leg of the call. No error shows up, nothing in dmesg either.

-- Executing [gedalya-all@internal:1] 
Set("PJSIP/trunk-vitelity-in-", "CDR(peername)=trunk-vitelity-in") in 
new stack
-- Executing [gedalya-all@internal:2] 
MixMonitor("PJSIP/trunk-vitelity-in-", 
"/var/local/callrec/2016-11/1478045348.0.wav") in new stack
-- Executing [gedalya-all@internal:3] 
Dial("PJSIP/trunk-vitelity-in-", 
"PJSIP/../.././../.,30") in new 
stack
  == Begin MixMonitor Recording PJSIP/trunk-vitelity-in-
asterisk*CLI>
Disconnected from Asterisk server
Asterisk cleanly ending (0).
Executing last minute cleanups

That's all. Nothing in the log either.

After going back to pjproject 2.5.1~dfsg-4 everything works again.

Maybe asterisk just needs to be rebuilt against 2.5.5? I could try this later 
perhaps.

Thanks,

Gedalya
--- End Message ---
--- Begin Message ---
Version: 2.5.5~dfsg-3

On Thu, Nov 10, 2016 at 01:44:33PM -0500, Gedalya wrote:

> On 11/10/2016 05:26 AM, Bernhard Schmidt wrote:
> > I have just uploaded 2.5.5~dfsg-3 with all patches bundled in Asterisk
> > applied. Please take a look, should be available shortly.
> 
> Installed, works just fine.

Closing the bug accordingly.

Thanks a lot for your valuable help in testing this. You certainly seem
to know your way around Asterisk, help packaging and supporting that
beast is always appreciated. Feel free to fling anything our way what
you think should be changed.

Best Regards,
Bernhard


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

Bug#837847: marked as done (libgsf: FTBFS due to undeclared build dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2016 07:19:18 +
with message-id 
and subject line Bug#837847: fixed in libgsf 1.14.40-2
has caused the Debian Bug report #837847,
regarding libgsf: FTBFS due to undeclared build dependencies
to be marked as done.

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

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


-- 
837847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgsf
Version: 1.14.40-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk-doc-tools

Hi,

your package libgsf declares a build dependency on gtk-doc-tools.
gtk-doc-tools in turn depends on gnome-common, which in turn pulls in packages
like gettext, intltool or pkg-config.

The dependency on gnome-common was originally added for the GNOME_GTKDOC_CHECK
macro which has been deprecated and replaced by GTK_DOC_CHECK a long time ago.

As gnome-common has been declared deprecated by GNOME upstream [1], we would
like to drop this dependency from gtk-doc-tools.

We did a test of all reverse build dependencies of gtk-doc-tools and libgsf
failed to build due to now missing build dependencies which are no longer
pulled in by gtk-doc-tools.

A complete build log is available at
https://people.debian.org/~biebl/gtk-doc-tools/libgsf.log

We have uploaded that gtk-doc-tools package as 1.25-4 to experimental as well,
so you can test your package against this version.

Common build-failures and their fixes:

a/ configure.ac:32: error: possibly undefined macro: AC_PROG_INTLTOOL

   make[1]: intltoolize: Command not found

   → Build-Depends: intltool

b/ ./configure: line 5461: syntax error near unexpected token `yes'
   ./configure: line 5461: `GNOME_COMPILE_WARNINGS(yes)'

   ./configure: line 14801: GNOME_CODE_COVERAGE: command not found

   → Build-Depends: gnome-common (for GNOME_* macros)

c/ ./configure: line 17439: syntax error near unexpected token 
`$WARN_CFLAGS_EXTRA,'
   ./configure: line 17439: `AX_APPEND_COMPILE_FLAGS($WARN_CFLAGS_EXTRA, 
WARN_CFLAGS)'

   ./configure: line 2629: syntax error near unexpected token `git-directory'
   ./configure: line 2629: `AX_IS_RELEASE(git-directory)'

   → Build-Depends: autoconf-archive (for AX_* macros)

d/ ./configure: line 12518: intltool-update: command not found
   checking for intltool >= 0.40.0...  found
   ./configure: error: Your intltool is too old.  You need intltool 0.40.0 or 
later.

   → Build-Depends: intltool

e/ make[1]: intltoolize: Command not found

   → Build-Depends: intltool

f/ ./autogen.sh calls gnome-autogen.sh

   → Build-Depends: gnome-common


Please add the required build-dependencies to your package so once we upload
gtk-doc-tools_1.25-4 to unstable your package doesn't FTBFS.

Regards,
Michael


[1] https://wiki.gnome.org/Projects/GnomeCommon/Migration
--- End Message ---
--- Begin Message ---
Source: libgsf
Source-Version: 1.14.40-2

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Nov 2016 17:49:47 +1100
Source: libgsf
Binary: gir1.2-gsf-1 libgsf-1-114 libgsf-1-dev libgsf-1-common libgsf-bin
Architecture: source amd64 all
Version: 1.14.40-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 gir1.2-gsf-1 - GObject introspection data for the Structured File Library
 libgsf-1-114 - Structured File Library - runtime version
 libgsf-1-common - Structured File Library - common files
 libgsf-1-dev - Structured File Library - development files
 libgsf-bin - Structured File Library - programs
Closes: 837847
Changes:
 libgsf (1.14.40-2) unstable; urgency=medium
 .
   * Build-Depends += "intltool" (Closes: #837847).
Checksums-Sha1:
 9f2ac5700697de0d563bab90acb61679c53eedbf 2256 libgsf_1.14.40-2.dsc
 

Bug#843853: marked as done (Uninstallable due to dependency on libgstreamer-plugins-bad1.0-0 (< 1.8.4))

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 23:17:00 -0800
with message-id 

Processed: lets close this one

[Debian Bug Tracking System]

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

> close 842695
Bug #842695 [src:lirc] lirc: block testing migration
Marked Bug as done
> fixed 842695 0.9.4c-4
Bug #842695 {Done: Gianfranco Costamagna } [src:lirc] 
lirc: block testing migration
Marked as fixed in versions lirc/0.9.4c-4.
> thanks
Stopping processing here.

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

Bug#840094: blends-dev: Does not recognize multiline dependencies

[Andreas Tille]

Hi,

On Thu, Nov 10, 2016 at 10:38:32PM +0100, Ole Streicher wrote:
> On 10.11.2016 21:07, Andreas Tille wrote:
> > So I confirm that the first problem we detected is solved but there is
> > another one breaking Debian Edu.  I have again no suspicion why the '\'
> > sign is not elimiunated from the list only in those few cases.
> 
> I can also just "poke in the fog" here. I thought that the multilines
> were already eaten up by lines 537-544, and should not appear again
> here. However, they do, as my "print" debugger shows. Perlists, please
> help!!!
> 
> The pragmatic solution here is to just remove the backslashes from the
> end of line. I can commit a patch that does this.
> 
> However, debian-edu keeps to be broken. Reason is that the tasks contain
> lines like (development)
> 
> Depends: fp-compiler, [...multiline... ], fp-units-fv
> Depends: lazarus
> 
> so, with two "Depends" in one section. Or (electronics):

That's definitely broken and not supported by other tools than
blends-dev and should be fixed.  Every Depends, Recommends and
Suggests should be in a separate paragraph.
 
> Depends: qucs, gpsim, oregano
> Recommends: education-menus, xoscope
> Suggests: kicad, kicad-doc-en, kicad-doc-de, kicad-doc-es, kicad-doc-fr
> Suggests: electric, pcb, xcircuit, freehdl, gtkwave
> Responsible: ?
> NeedConfig:  no
> 
> two "Suggests". This does not work anymore (no idea why), but is also
> IMO forbidden by RFC834.

The web sentinel code does not even allow one Depends and Suggests in a
common paragraph.
 
> I have no idea why this works without RFC834 continuation, but not with
> them.
> 
> On the other hand, we *win* one more dependency: in "common", the
> "firmware-ralink" dependency line was *not* preceded one with a
> backslash. This shows that the backslash is just a bad idea for
> continuation lines.

Meanwhile I'm fully convinced that you are right here and we should fix
this soon since also in Debian Science some missing backslashes caused
loss of Dependencies in the resulting metapackages.
 
> --> debian-edu tasks are just broken. They don't follow any rule, and
> depending from the parser one will get always different results. Maybe
> we should fix that? remove all backslash continuation lines and
> duplicated keywords from the tasks files?

I think it should be sufficient to add line breaks where needed.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: severity of 823822 is serious

[Debian Bug Tracking System]

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

> severity 823822 serious
Bug #823822 [qttools5-dev-tools] qttools5-dev-tools: lupdate is super slow
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#843519: marked as done (gitlab: CVE-2016-9086)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2016 06:48:41 +
with message-id 
and subject line Bug#843519: fixed in gitlab 8.13.3+dfsg1-2
has caused the Debian Bug report #843519,
regarding gitlab: CVE-2016-9086
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.)


-- 
843519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab
Version: 8.10.5+dfsg-3
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

the following vulnerability was published for gitlab.

CVE-2016-9086[0]:
| GitLab versions 8.9.x and above contain a critical security flaw in the
| "import/export project" feature of GitLab. Added in GitLab 8.9, this
| feature allows a user to export and then re-import their projects as
| tape archive files (tar). All GitLab versions prior to 8.13.0
| restricted this feature to administrators only. Starting with version
| 8.13.0 this feature was made available to all users. This feature did
| not properly check for symbolic links in user-provided archives and
| therefore it was possible for an authenticated user to retrieve the
| contents of any file accessible to the GitLab service account. This
| included sensitive files such as those that contain secret tokens used
| by the GitLab service to authenticate users. GitLab CE and EE versions
| 8.13.0 through 8.13.2, 8.12.0 through 8.12.7, 8.11.0 through 8.11.10,
| 8.10.0 through 8.10.12, and 8.9.0 through 8.9.11 are affected.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-9086
[1] https://hackerone.com/reports/178152
[2] https://about.gitlab.com/2016/11/02/cve-2016-9086-patches/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 8.13.3+dfsg1-2

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 843...@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: Fri, 11 Nov 2016 10:56:31 +0530
Source: gitlab
Binary: gitlab
Architecture: source
Version: 8.13.3+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 gitlab - git powered software platform to collaborate on code
Closes: 843519
Changes:
 gitlab (8.13.3+dfsg1-2) unstable; urgency=medium
 .
   * Reupload to unstable (Closes: #843519)
Checksums-Sha1:
 9857cbf76fc44b2917456b144fb2cd5befcfd92c 2063 gitlab_8.13.3+dfsg1-2.dsc
 a7341b53880eb81115ff5c3ad62e7f919e7cb800 43488 
gitlab_8.13.3+dfsg1-2.debian.tar.xz
Checksums-Sha256:
 ee1b5816a23cbb4b61a3a70d8de15b4da4c931dff6c73af2a2991a537826b4f6 2063 
gitlab_8.13.3+dfsg1-2.dsc
 459c8ecd668cbf5449cd0e3351b431456134e14b44c82cb7d61583ac8e14ed65 43488 
gitlab_8.13.3+dfsg1-2.debian.tar.xz
Files:
 0c89a5e98311e7e129fbab667ed71144 2063 ruby optional gitlab_8.13.3+dfsg1-2.dsc
 affdebd92a346d193ec52bf8e92ee2c0 43488 ruby optional 
gitlab_8.13.3+dfsg1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYJWVRAAoJEM4fnGdFEsIqh08QAIkWQV39J3pF08M4bEIcXBxX
C/gUaouC+ijVslpe0gkPrIVMiK0Q+xGtC/dmmqyoHmilv3LJQmU/Pgc02snDI7EH
u++vng02A/eNWFMNvI1ldL14YIibsy1ag/fS3b0RMEN9J5UfNobnUTn8i9gWFYHT
imB8mZcTP74I1Mz4qFsravKZ4zwoib9TYJYX/uiUjnmjs15aL9FHzlj3zvMVe/NL
4LF977665eUIpd9cSgdn6GDDzpXnwXl0E7mJSaikbYSsW9kjnGXCCfmZzl80yAUh
BuUfRFDYEYyq9+/kI6JTW34YSAxDTxhUMIVoOUcujuit8r2dTwss9fnpj01qltvz
81Hy3vcljpCimXEF+igc7FlCnAHW5Ew2zuRRs93kxLyuELfil+R63UXUuGygA53n
eXH64EN//kKVFrAtyEHSz2pmwF6rUVVCKcHII4CnFxLqqaocoCVO190YAnlswTuX
0qRjzUOznXjdz3af69mlszW3RfRBCoseqaTPbsuXIKFKlOwMc2VJQbwB8p/VIVCe
Eucgrn5PxCopQeW8cBIlQrNcCLEg41IrVWyEo76QdXdoalAXTgVQRtaLM+NW3G1D
1jtdG4Ukvhg/bmwxiUTpo12EVFQIjI+XPumaLIe1KSNT+RdPcUUMBwEuE6VbfCTP

Bug#837847: tagged as pending

[Dmitry Smirnov]

tag 837847 pending
--

We believe that the bug #837847 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:

http://anonscm.debian.org/cgit/collab-maint/libgsf.git/diff/?id=f731aff

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit f731aff (HEAD, master)
Author: Dmitry Smirnov 
Date:   Fri Nov 11 06:52:07 2016

Build-Depends += "intltool" (Closes: #837847).

Processed: Bug#837847 tagged as pending

[Debian Bug Tracking System]

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

> tag 837847 pending
Bug #837847 [src:libgsf] libgsf: FTBFS due to undeclared build dependencies
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#823330: its working for me

[gustavo panizzo (gfa)]

Control:
merge 472001 -1
notfound -1 1.8beta5+ds1-1
thanks

Hello 

works for me

$ tsocks wget -q -O - icanhazip.com 
XXX.XXX.95.55

$ wget -q -O - icanhazip.com 
XXX.XXX.43.177


$ grep ^server /etc/tsocks.conf 
server = localhost
server_type = 5
server_port = 1081

I'm using tsocks 1.8beta5+ds1-1 but that particular patch hasn't changed

if you confirm it works for you, i'll proceed to close this bug

thanks!

-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa

Bug#838734: fixed in plasma-discover 5.8.3-1

[Scott Kitterman]

This is currently blocked from migrating to Testing by the Qt5.7.1 transition.  
Eventually, we'll get there.

Scott K

Processed: tagging 836885

[Debian Bug Tracking System]

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

> tags 836885 + pending
Bug #836885 [src:openldap] please stop building against Heimdal
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#824475: marked as done (python-mne: FTBFS: TraitError: The 'input' trait of a QuadricDecimation instance is 'read only'.)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 22:36:16 -0500
with message-id <2016033616.f2k6edqmcchhk...@hopa.kiewit.dartmouth.edu>
and subject line Re: Two unanswered RC bugs in python-mne
has caused the Debian Bug report #824475,
regarding python-mne: FTBFS: TraitError: The 'input' trait of a 
QuadricDecimation instance is 'read only'.
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.)


-- 
824475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mne
Version: 0.11+dfsg-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,

python-mne fails to build from source in unstable/amd64:

  [..]

  copying mne/time_frequency/__init__.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/_stockwell.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/ar.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/tfr.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/psd.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/stft.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/csd.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/multitaper.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  creating build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_psd.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/__init__.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_stockwell.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_csd.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_multitaper.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_ar.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_stft.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_tfr.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  creating build/lib.linux-x86_64-2.7/mne/realtime
  copying mne/realtime/__init__.py -> build/lib.linux-x86_64-2.7/mne/realtime
  copying mne/realtime/mockclient.py -> build/lib.linux-x86_64-2.7/mne/realtime
  copying mne/realtime/epochs.py -> build/lib.linux-x86_64-2.7/mne/realtime
  copying mne/realtime/stim_server_client.py -> 
build/lib.linux-x86_64-2.7/mne/realtime
  copying mne/realtime/fieldtrip_client.py -> 
build/lib.linux-x86_64-2.7/mne/realtime
  copying mne/realtime/client.py -> build/lib.linux-x86_64-2.7/mne/realtime
  creating build/lib.linux-x86_64-2.7/mne/realtime/tests
  copying mne/realtime/tests/__init__.py -> 
build/lib.linux-x86_64-2.7/mne/realtime/tests
  copying mne/realtime/tests/test_fieldtrip_client.py -> 
build/lib.linux-x86_64-2.7/mne/realtime/tests
  copying mne/realtime/tests/test_stim_client_server.py -> 
build/lib.linux-x86_64-2.7/mne/realtime/tests
  copying mne/realtime/tests/test_mockclient.py -> 
build/lib.linux-x86_64-2.7/mne/realtime/tests
  creating build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/__init__.py -> build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/base.py -> build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/time_gen.py -> build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/mixin.py -> build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/transformer.py -> build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/ems.py -> build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/csp.py -> build/lib.linux-x86_64-2.7/mne/decoding
  creating build/lib.linux-x86_64-2.7/mne/decoding/tests
  copying mne/decoding/tests/__init__.py -> 
build/lib.linux-x86_64-2.7/mne/decoding/tests
  copying mne/decoding/tests/test_csp.py -> 
build/lib.linux-x86_64-2.7/mne/decoding/tests
  copying mne/decoding/tests/test_ems.py -> 
build/lib.linux-x86_64-2.7/mne/decoding/tests
  copying mne/decoding/tests/test_transformer.py -> 
build/lib.linux-x86_64-2.7/mne/decoding/tests
  copying mne/decoding/tests/test_time_gen.py -> 
build/lib.linux-x86_64-2.7/mne/decoding/tests
  copying mne/commands/utils.py -> 

Bug#843874: marked as done (dpkg: segfaults installing desktop-base 9.0.0~exp1 on amd64)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2016 03:03:50 +
with message-id 
and subject line Bug#843874: fixed in dpkg 1.18.14
has caused the Debian Bug report #843874,
regarding dpkg: segfaults installing desktop-base 9.0.0~exp1 on amd64
to be marked as done.

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

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


-- 
843874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.18.13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + desktop-base

Hi,

during a test with piuparts I noticed a reproducible dpkg segfault
when installing desktop-base/experimental in a sid+experimental amd64 chroot.

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

  Selecting previously unselected package desktop-base.
  (Reading database ... 
(Reading database ... 5376 files and directories currently installed.)
  Preparing to unpack .../desktop-base_9.0.0~exp1_all.deb ...
  Unpacking desktop-base (9.0.0~exp1) ...
  Processing triggers for libglib2.0-0:amd64 (2.50.2-1) ...
  No schema files found: doing nothing.
  Setting up desktop-base (9.0.0~exp1) ...
  update-alternatives: using /usr/share/desktop-base/softwaves-theme to provide 
/usr/share/desktop-base/active-theme (desktop-theme) in auto mode
  update-alternatives: using 
/usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg to 
provide /usr/share/images/desktop-base/desktop-background (desktop-background) 
in auto mode
  update-alternatives: using 
/usr/share/desktop-base/active-theme/wallpaper/gnome-background.xml to provide 
/usr/share/images/desktop-base/desktop-background.xml (desktop-background.xml) 
in auto mode
  update-alternatives: using 
/usr/share/desktop-base/active-theme/lockscreen/gnome-background.xml to provide 
/usr/share/images/desktop-base/desktop-lockscreen.xml (desktop-lockscreen.xml) 
in auto mode
  update-alternatives: using /usr/share/desktop-base/active-theme/wallpaper to 
provide /usr/share/wallpapers/DebianTheme (desktop-plasma5-wallpaper) in auto 
mode
  update-alternatives: using 
/usr/share/desktop-base/active-theme/login/background.svg to provide 
/usr/share/images/desktop-base/login-background.svg (desktop-login-background) 
in auto mode
  update-alternatives: using 
/usr/share/desktop-base/active-theme/grub/grub-4x3.png to provide 
/usr/share/images/desktop-base/desktop-grub.png (desktop-grub) in auto mode
  dpkg: error processing package desktop-base (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
  E: Sub-process /usr/bin/dpkg received a segmentation fault.


(gdb) bt 
#0  strlen () at ../sysdeps/x86_64/strlen.S:106
#1  0x7fa55ad14da3 in _IO_vfprintf_internal (s=0x7ffe707d3230, 
format=, ap=0x7ffe707d58d8) at vfprintf.c:1637
#2  0x7fa55ad15c23 in buffered_vfprintf (s=0x7fa55b065520 
<_IO_2_1_stderr_>, format=, args=) at 
vfprintf.c:2325
#3  0x7fa55ad12f15 in _IO_vfprintf_internal (s=s@entry=0x7fa55b065520 
<_IO_2_1_stderr_>, format=format@entry=0x55d7d0e90ad0 " %s\n", 
ap=ap@entry=0x7ffe707d58d8) at vfprintf.c:1293
#4  0x7fa55adc2cb9 in ___fprintf_chk (fp=0x7fa55b065520 <_IO_2_1_stderr_>, 
flag=flag@entry=1, format=format@entry=0x55d7d0e90ad0 " %s\n") at 
fprintf_chk.c:35
#5  0x55d7d0e66fba in fprintf (__fmt=0x55d7d0e90ad0 " %s\n", 
__stream=) at /usr/include/x86_64-linux-gnu/bits/stdio2.h:97
#6  reportbroken_retexitstatus (ret=0) at ../../src/errors.c:111
#7  0x55d7d0e5e6c2 in main (argc=, argv=) at 
../../src/main.c:927

(gdb) bt full
#0  strlen () at ../sysdeps/x86_64/strlen.S:106
No locals.
#1  0x7fa55ad14da3 in _IO_vfprintf_internal (s=0x7ffe707d3230, 
format=, ap=0x7ffe707d58d8) at vfprintf.c:1637
len = 
string_malloced = 0
step0_jumps = {0, -2199, -2392, -2299, -778, -685, 966, 644, 1362, 
1166, 1273, -1287, 547, 639, -2145, -2098, -1198, -1093, -1081, -1069, -2725, 
-577, 304, 393, 485, -3452, 63, -3541, -3541, 1073}
space = 
is_short = 
use_outdigits = 0
step1_jumps = {0, 0, 0, 0, 0, 0, 0, 0, 0, 1166, 1273, -1287, 547, 639, 
-2145, -2098, -1198, -1093, -1081, -1069, -2725, -577, 304, 393, 485, -3452, 
63, -3541, -3541, 0}
group = 0
prec = -1
step2_jumps = {0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1273, -1287, 547, 639, 
-2145, -2098, -1198, -1093, -1081, -1069, -2725, -577, 304, 393, 485, -3452, 
63, -3541, -3541, 0}
string = 0x55d7d2bd99b0 
left = 0

Bug#843916: debian-installer: fails to FTBFS when u-boot bits go missing

[Cyril Brulebois]

Control: tag -1 patch pending

Cyril Brulebois  (2016-11-10):
> That being said, there's still the issue of debian-installer's build
> system not detecting this issue, which is what this bug report is
> about.

Looking at while loops under build/, only a few arm* bits seemed
affected. Should be fixed with:
| commit 44a203535217322402ad1f10294c76bd99fc1f51
| Author: Cyril Brulebois 
| Date:   Fri Nov 11 03:10:53 2016 +0100
| 
| Make sure errors in while loops are reported (Closes: #843916).


KiBi.


signature.asc
Description: Digital signature

Processed: Re: Bug#843916: debian-installer: fails to FTBFS when u-boot bits go missing

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch pending
Bug #843916 [debian-installer] debian-installer: fails to FTBFS when u-boot 
bits go missing
Added tag(s) pending and patch.

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

Bug#843874: in package dpkg marked as pending

[Guillem Jover]

Control: tag 843874 pending

Hi!

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

https://anonscm.debian.org/cgit/dpkg/dpkg.git/diff/?id=89b80a3

---
commit 89b80a3da82ea5b10b1500d6c531432d0ce585a5
Author: Guillem Jover 
Date:   Thu Nov 10 16:42:13 2016 +0100

dpkg: Fix use after free issue on error summary

We are releasing the dpkg database now after running the commands, which
means that the postponed error reporting summary was trying to print
messages that had already been freed from the database memory pool.

Duplicate the passed strings so that we are impervious to the database
life-cycle.

Regression introduced in commit 3404fd24ef8020b4d6dc17adb82d7e6c035d90dc.

Closes: #843874

diff --git a/debian/changelog b/debian/changelog
index ff40966..3169791 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -7,6 +7,10 @@ dpkg (1.18.14) UNRELEASED; urgency=medium
 - Do not set PIE options if they have been negated, and do not reset
   them if they have been requested.
 Closes: #843791, #843826
+  * Fix use after free error in dpkg. It was trying to print messages that
+had already been freed as part of the database memory pool, causing in
+some cases segfaults when reporting the error summary at the end.
+Regression introduced in dpkg 1.18.11. Closes: #843874
   * Test suite:
 - Do not fail tests on missing fakeroot, just skip them.
   * Build system:

Processed: Bug#843874 in package dpkg marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 843874 pending
Bug #843874 [dpkg] dpkg: segfaults installing desktop-base 9.0.0~exp1 on amd64
Added tag(s) pending.

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

Bug#811825: FaCT++ Debian package removal

[Tobias Hansen]

Hi Roberto,

I noticed today that ppl was removed from Debian testing due to two RC
bugs. The problem is that ppl 1.2 has a new soname (14), that means it
requires a library transition. We are now already past the library
transition freeze for Debian stretch. Are you shure that the ABI of ppl
changed with version 1.2, i.e. that this soname bump is required?

It would now probably be best to patch version 1.1 of ppl to have at
least this version in the next Debian release. The previous mails from
this bug report suggest that the patch that was discussed was not enough
to fix the build with gcc 6. Could you provide a new patch for this?

Best,
Tobias

On Sat, 6 Aug 2016 14:34:14 +0200 Roberto Bagnara 
wrote:
> The new version upstream (PPL 1.2, released in February 2016) solves
> all problems wrt GCC 6.  If upgrading to the latest upstream release
> is not wanted (why?), then patches have been provided in this very issue.
> Kind regards,
> 
>Roberto
> 

Bug#843939: radare2: FTBFS on arm64: user_pt_regs and NT_PRSTATUS unknown

[Aaron M. Ucko]

Source: radare2
Version: 1.0+dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The latest arm64 build of radare2 failed, per the log excerpt below.
Could you please take a look, and ensure that linux_debug.h includes
all necessary headers?

Thanks!

  p/native/linux/linux_debug.c: In function 'linux_handle_signals':
  p/native/linux/linux_debug.c:67:2: warning: #warning DO MORE RDEBUGREASON 
HERE [-Wcpp]
   #warning DO MORE RDEBUGREASON HERE
^~~
  p/native/linux/linux_debug.c: In function 'print_fpu':
  p/native/linux/linux_debug.c:376:2: warning: #warning not implemented for 
this platform [-Wcpp]
   #warning not implemented for this platform
^~~
  p/native/linux/linux_debug.c: In function 'linux_reg_read':
  p/native/linux/linux_debug.c:466:3: warning: #warning not implemented for 
this platform [-Wcpp]
#warning not implemented for this platform
 ^~~
  p/native/linux/linux_debug.c:473:18: error: storage size of 'regs' isn't known
  R_DEBUG_REG_T regs;
^~~~
  p/native/linux/linux_debug.c:482:41: error: 'NT_PRSTATUS' undeclared (first 
use in this function)
  ret = ptrace (PTRACE_GETREGSET, pid, NT_PRSTATUS, io);
   ^~~
  p/native/linux/linux_debug.c:482:41: note: each undeclared identifier is 
reported only once for each function it appears in
  p/native/linux/linux_debug.c:473:18: warning: unused variable 'regs' 
[-Wunused-variable]
  R_DEBUG_REG_T regs;
^~~~
  p/native/linux/linux_debug.c:381:7: warning: variable 'showfpu' set but not 
used [-Wunused-but-set-variable]
bool showfpu = false;
 ^~~
  p/native/linux/linux_debug.c: In function 'linux_reg_write':
  p/native/linux/linux_debug.c:528:16: warning: initialization discards 'const' 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  .iov_base = buf,
  ^~~
  In file included from p/native/linux/linux_debug.c:14:0:
  p/native/linux/linux_debug.h:44:23: error: invalid application of 'sizeof' to 
incomplete type 'struct user_pt_regs'
   #define R_DEBUG_REG_T struct user_pt_regs
 ^
  p/native/linux/linux_debug.c:529:23: note: in expansion of macro 
'R_DEBUG_REG_T'
  .iov_len = sizeof (R_DEBUG_REG_T)
 ^
  p/native/linux/linux_debug.c:531:49: error: 'NT_PRSTATUS' undeclared (first 
use in this function)
 int ret = ptrace (PTRACE_SETREGSET, dbg-pid, NT_PRSTATUS, io);
   ^~~
  In file included from p/native/linux/linux_debug.c:14:0:
  p/native/linux/linux_debug.h:44:23: error: invalid application of 'sizeof' to 
incomplete type 'struct user_pt_regs'
   #define R_DEBUG_REG_T struct user_pt_regs
 ^

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Processed: bug 841784 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=774237

[Debian Bug Tracking System]

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

> forwarded 841784 https://bugzilla.gnome.org/show_bug.cgi?id=774237
Bug #841784 [src:gnucash] gnucash: FTBFS under some timezones (eg. GMT-14)
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=774237'.
> thanks
Stopping processing here.

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

Processed: tagging 841784

[Debian Bug Tracking System]

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

> tags 841784 + upstream
Bug #841784 [src:gnucash] gnucash: FTBFS under some timezones (eg. GMT-14)
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#837827: marked as done (goffice-0.8: FTBFS due to undeclared build dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2016 00:18:52 +
with message-id 
and subject line Bug#837827: fixed in goffice-0.8 0.8.17-7
has caused the Debian Bug report #837827,
regarding goffice-0.8: FTBFS due to undeclared build dependencies
to be marked as done.

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

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


-- 
837827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: goffice-0.8
Version: 0.8.17-6
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk-doc-tools

Hi,

your package goffice-0.8 declares a build dependency on gtk-doc-tools.
gtk-doc-tools in turn depends on gnome-common, which in turn pulls in packages
like gettext, intltool or pkg-config.

The dependency on gnome-common was originally added for the GNOME_GTKDOC_CHECK
macro which has been deprecated and replaced by GTK_DOC_CHECK a long time ago.

As gnome-common has been declared deprecated by GNOME upstream [1], we would
like to drop this dependency from gtk-doc-tools.

We did a test of all reverse build dependencies of gtk-doc-tools and goffice-0.8
failed to build due to now missing build dependencies which are no longer
pulled in by gtk-doc-tools.

A complete build log is available at
https://people.debian.org/~biebl/gtk-doc-tools/goffice-0.8.log

We have uploaded that gtk-doc-tools package as 1.25-4 to experimental as well,
so you can test your package against this version.

Common build-failures and their fixes:

a/ configure.ac:32: error: possibly undefined macro: AC_PROG_INTLTOOL

   make[1]: intltoolize: Command not found

   → Build-Depends: intltool

b/ ./configure: line 5461: syntax error near unexpected token `yes'
   ./configure: line 5461: `GNOME_COMPILE_WARNINGS(yes)'

   ./configure: line 14801: GNOME_CODE_COVERAGE: command not found

   → Build-Depends: gnome-common (for GNOME_* macros)

c/ ./configure: line 17439: syntax error near unexpected token 
`$WARN_CFLAGS_EXTRA,'
   ./configure: line 17439: `AX_APPEND_COMPILE_FLAGS($WARN_CFLAGS_EXTRA, 
WARN_CFLAGS)'

   ./configure: line 2629: syntax error near unexpected token `git-directory'
   ./configure: line 2629: `AX_IS_RELEASE(git-directory)'

   → Build-Depends: autoconf-archive (for AX_* macros)

d/ ./configure: line 12518: intltool-update: command not found
   checking for intltool >= 0.40.0...  found
   ./configure: error: Your intltool is too old.  You need intltool 0.40.0 or 
later.

   → Build-Depends: intltool

e/ make[1]: intltoolize: Command not found

   → Build-Depends: intltool

f/ ./autogen.sh calls gnome-autogen.sh

   → Build-Depends: gnome-common


Please add the required build-dependencies to your package so once we upload
gtk-doc-tools_1.25-4 to unstable your package doesn't FTBFS.

Regards,
Michael


[1] https://wiki.gnome.org/Projects/GnomeCommon/Migration
--- End Message ---
--- Begin Message ---
Source: goffice-0.8
Source-Version: 0.8.17-7

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated goffice-0.8 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Nov 2016 10:57:37 +1100
Source: goffice-0.8
Binary: libgoffice-0.8-dev libgoffice-0.8-dbg libgoffice-0.8-8 
libgoffice-0.8-8-common
Architecture: source all amd64
Version: 0.8.17-7
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 libgoffice-0.8-8 - Document centric objects library - runtime files
 libgoffice-0.8-8-common - Document centric objects library - common files
 libgoffice-0.8-dbg - Document centric objects library - debugging files
 libgoffice-0.8-dev - Document centric objects library - development files
Closes: 837827
Changes:
 goffice-0.8 (0.8.17-7) unstable; urgency=medium
 .
   * Build-Depends += "intltool (>= 0.35.0)" (Closes: #837827).
Checksums-Sha1:
 

Bug#828545: marked as done (simutrans: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2016 00:04:31 +
with message-id 
and subject line Bug#828545: fixed in simutrans 120.1.3+repack-2
has caused the Debian Bug report #828545,
regarding simutrans: FTBFS with openssl 1.1.0
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.)


-- 
828545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simutrans
Version: 120.1.3+repack-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/simutrans_120.1.3+repack-1_amd64-20160529-1536

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: simutrans
Source-Version: 120.1.3+repack-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated simutrans 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: Thu, 10 Nov 2016 23:28:04 +0100
Source: simutrans
Binary: simutrans simutrans-data simutrans-makeobj
Architecture: source
Version: 120.1.3+repack-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 simutrans  - transportation simulator
 simutrans-data - transportation simulator (base data)
 simutrans-makeobj - data file compiler for Simutrans
Closes: 828545
Changes:
 simutrans (120.1.3+repack-2) unstable; urgency=medium
 .
   * Team upload.
   * Declare compliance with Debian Policy 3.9.8.
   * Switch to compat level 10.
   * Drop 0110-sha1-replacement.diff.
 We don't need this patch because the original sha1 implementation from Paul
 E.Jones is free software.
 See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730758 for a
 clarification.
   * Add sha1.patch.
 This is the original upstream version. It is free software. Add a
 clarification to debian/copyright. This also fixes the FTBFS with OpenSSL
 1.1.0. (Closes: #828545)
   * Fix installation path of makeobj and sim binary file.
   * debian/clean: Ensure that the package can be built twice in a row.
Checksums-Sha1:
 cf8199dcda97fc22e7e6ad6848a8ae01180bac0c 2365 simutrans_120.1.3+repack-2.dsc
 0642b96d94bbadb81ebbad3347ac16db3d8aed42 274004 
simutrans_120.1.3+repack-2.debian.tar.xz
Checksums-Sha256:
 e8fc7df8501d5bbae89782782f0b557cf0318fc305dd0fb9313fb9e3f5392b60 2365 
simutrans_120.1.3+repack-2.dsc
 86b3deb47ed45106f78bc86620ba0baf79136c55aab75dea9093d5148a5b84e3 274004 
simutrans_120.1.3+repack-2.debian.tar.xz
Files:
 1781f701622caaef70623cb31e319f17 2365 games extra 
simutrans_120.1.3+repack-2.dsc
 0651b7db885be0afbcd7361291b7f7cd 274004 games extra 
simutrans_120.1.3+repack-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKMBAEBCgB2BQJYJQRrXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0DxxhcG9AZGViaWFuLm9yZwAKCRDZrRS5UTtR5Kb1D/9V
IkkMB1MzLBH5sVeok0LElAqKKg08ZXyfa1HzdylGebvkkVnnOUOsC8GbFad8jdGa
WUA5lG3W0gBtSEiyI2dGT1Qr8ZfaOo++s1IrjIt+bKL+qIHeC8t24Hho/Bukmh42
4AHkbwKq1mQZxtxRN35wurOepcd+aWj6GyPmFvVNBkgJbaCNNxJKR7M/iUtT1Ckb
AwRQxf/sWsORNNriiZ5F9zh5ANiKZMx4e01kniAfadDctK/lKpqjdzlHD/P1P0nv
4thhcT4BsOCAbDEFjsP81WhsuWBdKXfd3mywfx4zgy8bzMxVvLTEs/TDxc3Ih8sq

Bug#837827: tagged as pending

[Dmitry Smirnov]

tag 837827 pending
--

We believe that the bug #837827 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:

http://anonscm.debian.org/cgit/collab-maint/goffice.git/diff/?id=d3a5f66

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit d3a5f66 (goffice-0.8)
Author: Dmitry Smirnov 
Date:   Fri Nov 11 00:01:58 2016

Build-Depends += "intltool (>= 0.35.0)" (Closes: #837827).

Processed: Bug#837827 tagged as pending

[Debian Bug Tracking System]

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

> tag 837827 pending
Bug #837827 [src:goffice-0.8] goffice-0.8: FTBFS due to undeclared build 
dependencies
Added tag(s) pending.
> --
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 843569 4.6.1.3+dfsg-7
Bug #843569 [src:mono] mono: FTBFS on ppc64el (-pie -fPIE issue in __thread TLS)
Marked as fixed in versions mono/4.6.1.3+dfsg-7.
>
End of message, stopping processing here.

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

Bug#843569: marked as done (mono: FTBFS on ppc64el (-pie -fPIE issue in __thread TLS))

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 23:50:31 +
with message-id 
and subject line 
has caused the Debian Bug report #843569,
regarding mono: FTBFS on ppc64el (-pie -fPIE issue in __thread TLS)
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.)


-- 
843569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mono
Version: 4.6.1.3+dfsg-4
Severity: serious

Your package failed to build on mipsel:

chmod +x _tmpinst/bin/al
if test -w /«BUILDDIR»/mono-4.6.1.3+dfsg/mcs; then :; else chmod -R +w 
/«BUILDDIR»/mono-4.6.1.3+dfsg/mcs; fi
cd /«BUILDDIR»/mono-4.6.1.3+dfsg/mcs && /usr/bin/make --no-print-directory -s 
NO_DIR_CHECK=1 PROFILES='binary_reference_assemblies net_4_x xbuild_12 
xbuild_14  ' CC='gcc' all-profiles
mkdir -p -- build/deps
build/profiles/basic.make:93: recipe for target 
'build/deps/basic-profile-check.exe' failed
make[7]: *** [build/deps/basic-profile-check.exe] Error 1
*** The compiler 'false' doesn't appear to be usable.
*** Trying the 'monolite' directory.
 long_mul R91 <- R76 R88
* Assertion: should not be reached at mini-mips.c:2229

Stacktrace:

  at  <0x>
  at System.IO.StreamReader.Init 
(System.IO.Stream,System.Text.Encoding,bool,int,bool) <0x00104>
  at System.IO.StreamReader..ctor 
(System.IO.Stream,System.Text.Encoding,bool,int,bool) <0x00100>
  at System.IO.StreamReader..ctor (System.IO.Stream,System.Text.Encoding) 
<0x00044>
  at System.IO.UnexceptionalStreamReader..ctor 
(System.IO.Stream,System.Text.Encoding) <0x00028>
  at (wrapper remoting-invoke-with-check) 
System.IO.UnexceptionalStreamReader..ctor 
(System.IO.Stream,System.Text.Encoding) <0x00070>
  at System.Console.SetupStreams (System.Text.Encoding,System.Text.Encoding) 
<0x002a8>
  at System.Console..cctor () <0x00250>
  at (wrapper runtime-invoke) object.runtime_invoke_void 
(object,intptr,intptr,intptr) <0x0008c>
  at  <0x>
  at Mono.CSharp.Driver.Main (string[]) <0x000a0>
  at (wrapper runtime-invoke) .runtime_invoke_int_object 
(object,intptr,intptr,intptr) <0x0013c>

Native stacktrace:

/«BUILDDIR»/mono-4.6.1.3+dfsg/mono/mini/mono() [0x4c2c68]

Debug info from gdb:


=
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=

Aborted
build/profiles/basic.make:93: recipe for target 
'build/deps/basic-profile-check.exe' failed

Full logs at
https://buildd.debian.org/status/logs.php?pkg=mono=mipsel

Emilio
--- End Message ---
--- Begin Message ---
fixed 843569 4.6.1.3+dfsg-7--- End Message ---

Processed: bug 828616 is forwarded to https://github.com/Yubico/yubico-piv-tool/issues/104

[Debian Bug Tracking System]

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

> forwarded 828616 https://github.com/Yubico/yubico-piv-tool/issues/104
Bug #828616 [src:yubico-piv-tool] yubico-piv-tool: FTBFS with openssl 1.1.0
Ignoring request to change the forwarded-to-address of bug#828616 to the same 
value
> thanks
Stopping processing here.

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

Bug#843532: [Pkg-dns-devel] Bug#843532: dnssec-trigger: broken by OpenSSL 1.1.0

[Sebastian Andrzej Siewior]

On 2016-11-10 12:10:41 [+0100], Ondřej Surý wrote:
> Sebastian,

Hi Ondřej,

> thanks for the patch. The 0.13~svn685-7 version in unstable includes
> your patch,
> and I would really appreciate if someone could test whether
> dnssec-trigger now
> works.

I managed to get around to test it. So the initial error is gone - the
daemon can be started. Are going the forward the two patches upstream or
should I do it?

> Ondrej

Sebastian

Processed: Re: Bug#843511: libqt5widgets5: Some Qt applications segfault on startup

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #843512 [lxqt-qtplugin] lxqt-qtplugin: Needs dependency on qtbase-abi, 
needs rebuild for Qt 5.7
Severity set to 'normal' from 'grave'

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

Bug#843512: Bug#843511: libqt5widgets5: Some Qt applications segfault on startup

[Alf Gaida]

Control: severity -1 normal
> However, with no additional dependency being added, this means Qt 5.7
> will move to testing before the new lxqt-qtplugin does, breaking every
> LXQt out there -- correct?
May be, but both packages will migrate in the same cycle or a cycle 
later. So it will eventually break some systems - and these systems can 
be repaired a) with purging lxqt-plugins b) waiting c) take 
lxqt-qtplugins from sid for the time being.


We are aware of the possible breaks, but we will find a solution in Qt 
upstream or Qt packaging before the stable release to picking up the 
qt-abi dependency correctly.

Bug#828556: sslscan: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

On 2016-11-10 12:10:04 [+0200], Adrian Bunk wrote:
> On Thu, Sep 01, 2016 at 09:55:46PM +0200, Sebastian Andrzej Siewior wrote:
> > control: forwarded -1 https://github.com/rbsec/sslscan/issues/108
> 
> Sebastian, Marvin, what is the status regarding getting this patch that 
> was applied upstream included in Debian?

Adrian: which patch?
Marvin: unless Adrian pulls out a patch I suggest you prepare a package
to build against libssl1.0-dev. I have currently no better suggestion. I
can sponsor the upload if you want me to.

> Thanks
> Adrian

Sebastian

Processed: bug 828616 is forwarded to https://github.com/Yubico/yubico-piv-tool/issues/104

[Debian Bug Tracking System]

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

> forwarded 828616 https://github.com/Yubico/yubico-piv-tool/issues/104
Bug #828616 [src:yubico-piv-tool] yubico-piv-tool: FTBFS with openssl 1.1.0
Set Bug forwarded-to-address to 
'https://github.com/Yubico/yubico-piv-tool/issues/104'.
> thanks
Stopping processing here.

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

Bug#827445: marked as done (python3-proselint: Remove `shell=True` as they are a security hazard)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 22:05:21 +
with message-id 
and subject line Bug#827445: fixed in python3-proselint 0.7.0-1
has caused the Debian Bug report #827445,
regarding python3-proselint: Remove `shell=True` as they are a security hazard
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.)


-- 
827445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-proselint
Version: 0.5.3-2
Severity: serious
Tags: security
Justification: 

This a migration blocker bug, as this issue is already fixed
in upstream's unreleased master.


As said on Python's subprocess docs,
using shell=True can be a security hazard[1],
as they open the door to shell code injection.

`shell=True` could for example be removed from:

out = subprocess.check_output("proselint --version", shell=True)
subprocess.call("proselint --debug >/dev/null", shell=True)

These other examples are possibly vulnerable to shell code injection:

out = subprocess.check_output("proselint {}".format(fullpath),
shell=True)
subprocess.call("{} {}".format("open", fullpath), shell=True)
subprocess.call("proselint {} >/dev/null".format(filepath), shell=True)

These other examples could maybe use python equivalents instead?:


subprocess.call("find . -name '*.pyc' -delete", shell=True)
subprocess.call("rm -rfv proselint/cache > /dev/null && mkdir -p
{}".format(os.path.join(os.path.expanduser("~"), ".proselint")),
shell=True)


See also upstream's bug tracker [2].

[1]: https://docs.python.org/2/library/subprocess.html#frequently-used-
arguments
[2]: https://github.com/amperser/proselint/issues/395



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

Kernel: Linux 4.5.0-2-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)

Versions of packages python3-proselint depends on:
ii  python3-click   6.6-1
ii  python3-future  0.15.2-2
ii  python3-six 1.10.0-3
pn  python3:any 

python3-proselint recommends no packages.

python3-proselint suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python3-proselint
Source-Version: 0.7.0-1

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

Debian distribution maintenance software
pp.
Víctor Cuadrado Juan  (supplier of updated python3-proselint 
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: Thu, 10 Nov 2016 22:18:39 +0100
Source: python3-proselint
Binary: python3-proselint
Architecture: source
Version: 0.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Víctor Cuadrado Juan 
Description:
 python3-proselint - Library and command-line prose linter utility (Python 3)
Closes: 827445
Changes:
 python3-proselint (0.7.0-1) unstable; urgency=medium
 .
   [ Víctor Cuadrado Juan ]
   * New Upstream release
 - Remove `shell=True` as they are a security hazard (Closes: #827445)
   * Drop 0002-Make-proselint-work-on-read-only-files.patch as
 it has been upstreamed
   * Update d/proselint.1 manpage for v0.7.0
   * Add TODO.Debian
   * Run `wrap-and-sort -ast`
 .
   [ Mattia Rizzolo ]
   * Add git-dpm tag config
   * Bump debhelper compat level to 10
Checksums-Sha1:
 dbd0015e70cad287def68d901d92eed191e4485b 2130 python3-proselint_0.7.0-1.dsc
 3c504317f55255690c0f1bb78b6e07391c7e9452 78585 
python3-proselint_0.7.0.orig.tar.gz
 9da92e094df2feca0a4d9357ba4fe95b5b3e21c5 3724 
python3-proselint_0.7.0-1.debian.tar.xz
Checksums-Sha256:
 e46b184b871e8271c4a4099f0abb051f632651d0827ade808d6e586dff810a44 2130 
python3-proselint_0.7.0-1.dsc
 

Bug#842326: ncmpc: NMU uploaded in deferred/queue

[Sebastian Harl]

Hi,

On Thu, Nov 10, 2016 at 08:34:44AM +0100, Gianfranco Costamagna wrote:
> On Mon, 31 Oct 2016 14:26:57 +0100 Gianfranco Costamagna 
>  wrote:
> > I uploaded the following NMU in deferred/10, please let me know if I can 
> > speed it up or cancel it
> > 
> > Attaching the debdiff for the new release (mostly autoconf fixes), and the 
> > filtered debdiff for the debian directory.
> > 
> 
> attaching the new debdiffs, since I forgot to close this bug

Thank you very much for taking care of this.

Merged as https://git.tokkee.org/?p=pkg-ncmpc.git;h=ncmpc-0.25-0.1

Cheers,
Sebastian

-- 
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x2F1FFCC7 +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin



signature.asc
Description: Digital signature

Bug#840094: blends-dev: Does not recognize multiline dependencies

[Ole Streicher]

Hi Andreas, Petter and all,

On 10.11.2016 21:07, Andreas Tille wrote:
> So I confirm that the first problem we detected is solved but there is
> another one breaking Debian Edu.  I have again no suspicion why the '\'
> sign is not elimiunated from the list only in those few cases.

I can also just "poke in the fog" here. I thought that the multilines
were already eaten up by lines 537-544, and should not appear again
here. However, they do, as my "print" debugger shows. Perlists, please
help!!!

The pragmatic solution here is to just remove the backslashes from the
end of line. I can commit a patch that does this.

However, debian-edu keeps to be broken. Reason is that the tasks contain
lines like (development)

Depends: fp-compiler, [...multiline... ], fp-units-fv
Depends: lazarus

so, with two "Depends" in one section. Or (electronics):

Depends: qucs, gpsim, oregano
Recommends: education-menus, xoscope
Suggests: kicad, kicad-doc-en, kicad-doc-de, kicad-doc-es, kicad-doc-fr
Suggests: electric, pcb, xcircuit, freehdl, gtkwave
Responsible: ?
NeedConfig:  no

two "Suggests". This does not work anymore (no idea why), but is also
IMO forbidden by RFC834.

I have no idea why this works without RFC834 continuation, but not with
them.

On the other hand, we *win* one more dependency: in "common", the
"firmware-ralink" dependency line was *not* preceded one with a
backslash. This shows that the backslash is just a bad idea for
continuation lines.

--> debian-edu tasks are just broken. They don't follow any rule, and
depending from the parser one will get always different results. Maybe
we should fix that? remove all backslash continuation lines and
duplicated keywords from the tasks files?

Best regards

Ole

Bug#828306: marked as done (galera-3: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 23:30:18 +0200
with message-id 

and subject line ASIO updated
has caused the Debian Bug report #828306,
regarding galera-3: FTBFS with openssl 1.1.0
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.)


-- 
828306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: galera-3
Version: 25.3.15-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/galera-3_25.3.15-1_amd64-20160529-1418

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828239
libasio-dev in Debian has been updated and is compatible with OpenSSL
1.1.0.

I am about to upload a new version of galera-3, and the rebuild will
solve this issue by using latest libasio-dev.--- End Message ---

Bug#843922: stockfish: FTBFS: g++: error: unrecognized command line option '-m32'

[Milan Zamazal]

Thanks for the report.  I changed the default build architecture to
general-64, I guess that's a good default these days.  Let's see what
happens (I'm afraid this package will require a bit more experiments
before it builds on all architectures, sorry about that).

Regards,
Milan

-- 
http://www.zamazal.org

Bug#843922: stockfish: FTBFS: g++: error: unrecognized command line option '-m32'

[Sven Joachim]

On 2016-11-10 21:41 +0100, Milan Zamazal wrote:

> Thanks for the report.  I changed the default build architecture to
> general-64, I guess that's a good default these days.

I haven't looked at the stockfish source, but I can imagine that this is
not going to improve the situation on 32-bit arches.  If the config
machinery cannot find out the pointer size by itself, dpkg-architecture
provides DEB_HOST_ARCH_BITS for you.

Cheers,
   Sven

Bug#821642: Bumping severity of PHP 7.0 transition bugs to serious

[Sebastiaan Couwenberg]

On Thu, 5 May 2016 10:20:57 +0200 Ondřej Surý wrote:
> I am bumping the severity of this bug to serious, as we are going to
> remove src:php5 from Debian and your package is blocking the first
> step which is removal of php5 from testing.  Please either update your
> package to support PHP 7.0 or remove the package from Debian unstable
> alltogether.

Since upstream has no plans for PHP 7 support [0],
removing pnp4nagios from unstable is the best option.

[0] https://github.com/lingej/pnp4nagios/issues/125

Kind Regards,

Bas

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

Processed: bug 821642 is forwarded to https://github.com/lingej/pnp4nagios/issues/125

[Debian Bug Tracking System]

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

> forwarded 821642 https://github.com/lingej/pnp4nagios/issues/125
Bug #821642 [pnp4nagios-web] pnp4nagios-web: PHP 7.0 Transition
Set Bug forwarded-to-address to 
'https://github.com/lingej/pnp4nagios/issues/125'.
> thanks
Stopping processing here.

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

Bug#843931: libgtkdatabox-0.9.3-0-{, lib}glade: fails to upgrade from 'testing' - trying to overwrite /usr/lib/glade/modules/libgladedatabox.a, ...

[Andreas Beckmann]

Package: libgtkdatabox-0.9.3-0-glade,libgtkdatabox-0.9.3-0-libglade
Version: 1:0.9.3.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libgtkdatabox-0.9.3-0-glade.
  Preparing to unpack 
.../libgtkdatabox-0.9.3-0-glade_1%3a0.9.3.0+dfsg-1_amd64.deb ...
  Unpacking libgtkdatabox-0.9.3-0-glade (1:0.9.3.0+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgtkdatabox-0.9.3-0-glade_1%3a0.9.3.0+dfsg-1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/lib/glade/modules/libgladedatabox.a', which is 
also in package libgtkdatabox-0.9.2-0-glade 1:0.9.2.0+dfsg-1

  Selecting previously unselected package libgtkdatabox-0.9.3-0-libglade.
  Preparing to unpack 
.../libgtkdatabox-0.9.3-0-libglade_1%3a0.9.3.0+dfsg-1_amd64.deb ...
  Unpacking libgtkdatabox-0.9.3-0-libglade (1:0.9.3.0+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgtkdatabox-0.9.3-0-libglade_1%3a0.9.3.0+dfsg-1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libglade/2.0/libdatabox.a', 
which is also in package libgtkdatabox-0.9.2-0-libglade 1:0.9.2.0+dfsg-1


cheers,

Andreas


libgtkdatabox-0.9.2-0-glade=1%0.9.2.0+dfsg-1_libgtkdatabox-0.9.3-0-glade=1%0.9.3.0+dfsg-1.log.gz
Description: application/gzip

Bug#830984: Do you have resources to look after ball? [progress info]

[Andreas Tille]

Hi Danny,

thanks a lot for your quick response to analyse the problems in the ball
package.  I take the freedom to turn this discussion into a public one
and CC the relevant bugs to leave a record there that something is
happening.

On Thu, Nov 10, 2016 at 03:26:30PM +0100, Danny Edel wrote:
> On 11/09/2016 03:39 PM, Andreas Tille wrote:
> > Sure you can't give a time line.  I think when we start our Advent bug
> > squashing party we need to tackle it somehow - but having this sorted
> > out before to enable some testing would be great.
> 
> I have had some time to look into this, there are three failures, and
> all are perfectly reproducible.  Investigating (with core dumps) revealed:
> 
> 1. PoseClustering_Test depends on verbatim boost::serialisation output,
> which changes with every library version update.  Upstream has already
> fixed this by ignoring the actual file contents, and instead feeding the
> file to the de-serializer and check if the resulting object compares equal.

Sounds good.
 
> 2. DefaultProcessors_test segfaults after trying to use an optimized-out
> variable.  This looks like a legitimate upstream bug to me.
> 
> 3. XDRPersistenceManager_test segfaults after following a null pointer.
> Also looks like an upstream bug.
> 
> While backporting the fix for (1) is straightforward, the code paths
> responsible for (2) and (3) have seen quite some activity in the
> meantime, with the relevant commits changing lots of other files.

Hmmm, may be we should base the packaging on a later upstream commit?

> Among
> other things, upstream also migrated from Qt4 to Qt5, and incorporated a
> few fixes for recent boost.

We somehow should target to Qt5 anyway (see #784451) better sooner than
later.
 
> I tried building upstream master to see if it still contained the bugs.
> It did not, however one other test fails
> (AssignBondOrderProcessor_Test), which is related to upstream issue 576.
> 
> I will try to isolate and backport fixes for the three issues, and
> report back afterwards.

Again thanks a lot for your contribution

 Andreas.

-- 
http://fam-tille.de

Bug#840094: blends-dev: Does not recognize multiline dependencies

[Andreas Tille]

Hi,

On Thu, Nov 10, 2016 at 01:53:20PM +0100, Ole Streicher wrote:
> >
> > gbp clone ssh://git.debian.org/git/blends/projects/med.git
> > cd med
> > make dist
> > grep ^, debian/control

Debian Med and Debian Science are OK with the patch, however:

   gbp clone ssh://git.debian.org/git/debian-edu/debian-edu.git
   cd debian-edu
   make dist
   grep '\\' debian/control | head
Suggests: \ cpqarrayd,
 \ isag,
 \ lshw,
Suggests: \  gnome-accessibility-themes,
Suggests: \ kde-full,
 \ kdeaccessibility,
 \ kdegraphics-thumbnailers,
 \ kdf,
 \ kfloppy,
 \ kinfocenter,

So for some reason in the Debian Edu case '\' signs will not be
ignored but added to the d/control file.

> This is what I meant, and it is fixed by my last commit. Please try
> again ;-)

So I confirm that the first problem we detected is solved but there is
another one breaking Debian Edu.  I have again no suspicion why the '\'
sign is not elimiunated from the list only in those few cases.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#843838: marked as done (Fail to access config file)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 20:45:03 +0100
with message-id <871syjnmps.fsf...@arioch.leonhardt.eu>
and subject line Re: Bug#843838: Fail to access config file
has caused the Debian Bug report #843838,
regarding Fail to access config file
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.)


-- 
843838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bacula-director
Version: 7.4.4+dfsg-3
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

after upgrade baculu bacule-director don't start anymore.

Nov 10 07:39:29 merkur systemd[1]: Starting Bacula Director Daemon service...
Nov 10 07:39:29 merkur bacula-dir[24610]: bacula-dir: ERROR TERMINATION at
parse_conf.c:919
Nov 10 07:39:29 merkur bacula-dir[24610]: Config error: Cannot open config file
"/etc/bacula/bacula-dir.conf": Keine Berechtigung
Nov 10 07:39:29 merkur bacula-dir[24610]: 10-Nov 07:39 bacula-dir: ERROR
TERMINATION at parse_conf.c:919
Nov 10 07:39:29 merkur bacula-dir[24610]: Config error: Cannot open config file
"/etc/bacula/bacula-dir.conf": Keine Berechtigung
Nov 10 07:39:29 merkur systemd[1]: bacula-director.service: Control process
exited, code=exited status=1
Nov 10 07:39:29 merkur systemd[1]: Failed to start Bacula Director Daemon
service.
Nov 10 07:39:29 merkur systemd[1]: bacula-director.service: Unit entered failed
state.
Nov 10 07:39:29 merkur systemd[1]: bacula-director.service: Failed with result
'exit-code'.





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

Kernel: Linux 4.7.0-1-amd64 (SMP w/6 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 bacula-director depends on:
ii  bacula-common  7.4.4+dfsg-3
ii  bacula-director-mysql  7.4.4+dfsg-3
ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-3
ii  init-system-helpers1.45
ii  libc6  2.24-5
ii  libcap21:2.25-1
ii  libgcc11:6.2.0-10
ii  libssl1.0.21.0.2j-1
ii  libstdc++6 6.2.0-10
ii  libwrap0   7.6.q-25
ii  lsb-base   9.20161101
ii  ucf3.0036
ii  zlib1g 1:1.2.8.dfsg-2+b3

bacula-director recommends no packages.

Versions of packages bacula-director suggests:
pn  bacula-doc  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYJBd7AAoJEAn4nzyModJdEP4QAI9Sud21FefTt6l0SXzBmBsq
Fqu7EAF+0xgHUE0S+1JaVLV8DyjGtGNiQi06vKWC6AdExJG21MeoVmeQrs42pqYS
7kRfGNlUsvg/hYKQa+tO1pJcUW7Qw7uw9jbzUUA7s1jBecIBFi28V+s9W9ai0rtR
Og46QbQ81j/x6P4OnZ86MM6L4/RbRxWq+C9QRo0NjGju52JSvtCFTjKdEGguBYSZ
Wc0yCrI+L2Ncbh6WJqdp0xMA8B8vKQw12BrJxYur0E++ZBeXbNMGbAgnrfz3HvRJ
qWxOmqO0R2Zh+ZdgHvdd50+Zm/IqiZVORd8lEoNd9T5KHYWrxBSei3yyNN+b0oGK
nFgPm0YRpf3x6dKKkIuCov8Qg458rkbOWx45BJeU40BBkVovcBc7+wEvREfGLKgs
CtamdWJUQtmu3tPUYh/4rloZdnq3rvY89tShGa6tUIWFblw85gl9zeVssrZo5OSC
JorkJdn9HJ9KFunmqR4I0i+uaCdZOnLZD8YKBt1sK1GNxBP4XbIaEb7JnfZM2vrq
ap7dH84sdXPHoLkX9vG6UcNYzFASR/0X0EbXeNWdEYBsZBG8VDdizam3oOu+zV9w
7nki7PHvQxinkLX8QIMVr5ZKCTIPUTv3pl9netMAy75/FhL89wgYrjBmL6aBhWLx
RyqFIztZEZgYA344ldDc
=hKUx
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Hi Jörg,

Sven Hartge  writes:

> On 10.11.2016 18:51, Jörg Frings-Fürst wrote:

>> But also I have no idea from where the dirmngr comes.

> I also have no idea, but I find it very suspicious that every group that
> should be "bacula" is "dirmngr" on your system, as if someone/something
> changed /etc/group or replaced it with a one not belonging to the system.

I first thought you maybe deliberately changed the group ownership of
your config files, but if you don't know either, I agree with Sven that
you have a local error with file ownerships or a messed up /etc/groups.

As I wrote earlier, please fix group ownerships of your config files to
be "bacula" or otherwise make sure the daemons have access to them for
reading.

I'm closing this bug as it's not a problem with the debian packages. If
you want to discuss this issue further, please respect the
"Reply-To"-Header.

Thanks,

Carsten--- End Message ---

Bug#841373: (no subject)

[Marcos Mobley]

just adding this to the report to help those who find it and want a
working alternative. hope that's okay.

https://gist.github.com/ruario/215c365facfe8d3c5071




signature.asc
Description: OpenPGP digital signature

Bug#843874: dpkg: segfaults installing desktop-base 9.0.0~exp1 on amd64

[Andreas Beckmann]

On 2016-11-10 16:34, Guillem Jover wrote:
>> If you can still reproduce at will, I might like to provide a patch to
>> make sure the fix works for you? If you could test this, probably
>> later today, that'd be awesome!
> 
> Ok, it was too trivial to leave alone. :) Attached the proposed patch.

That seems to work:

# ./dpkg-buggy --configure --pending
Setting up desktop-base (9.0.0~exp1) ...
dpkg: error processing package desktop-base (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
Segmentation fault

# ./dpkg-fixed --configure --pending
Setting up desktop-base (9.0.0~exp1) ...
dpkg: error processing package desktop-base (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 desktop-base

and I can run an arbitrary sequence of these two commands and get
always the same output.


Andreas

Processed: severity of 843928 is grave

[Debian Bug Tracking System]

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

> severity 843928 grave
Bug #843928 [src:ming] ming: CVE-2016-9264 CVE-2016-9265 CVE-2016-9266
Bug #843929 [src:ming] ming: CVE-2016-9264 CVE-2016-9265 CVE-2016-9266
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: reassign 843929 to src:ming, forcibly merging 843928 843929

[Debian Bug Tracking System]

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

> reassign 843929 src:ming
Bug #843929 [ming] ming: CVE-2016-9264 CVE-2016-9265 CVE-2016-9266
Bug reassigned from package 'ming' to 'src:ming'.
Ignoring request to alter found versions of bug #843929 to the same values 
previously set
Ignoring request to alter fixed versions of bug #843929 to the same values 
previously set
> forcemerge 843928 843929
Bug #843928 [src:ming] ming: CVE-2016-9264 CVE-2016-9265 CVE-2016-9266
Bug #843929 [src:ming] ming: CVE-2016-9264 CVE-2016-9265 CVE-2016-9266
Severity set to 'important' from 'serious'
Marked as found in versions ming/1:0.4.4-1.1.
Added tag(s) upstream.
Merged 843928 843929
> thanks
Stopping processing here.

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

Processed: severity of 838634 is serious, tagging 829255, found 840832 in 0.5.1-3

[Debian Bug Tracking System]

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

> severity 838634 serious
Bug #838634 [flashcache] flashcache-dkms: Failure to build with 4.8 kernels
Severity set to 'serious' from 'normal'
> tags 829255 + patch
Bug #829255 [oss4-dkms] oss4-dkms: Fails to build for 4.6.0-1-amd64
Added tag(s) patch.
> found 840832 0.5.1-3
Bug #840832 [galileo-daemon] galileo-daemon: fails to purge: deluser options 
need perl-modules to be installed
Marked as found in versions galileo/0.5.1-3.
> thanks
Stopping processing here.

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

Bug#843929: ming: CVE-2016-9264 CVE-2016-9265 CVE-2016-9266

[Chris Lamb]

Package: ming
Severity: serious
Tags: security

Hi,

the following vulnerabilities were published for ming.

CVE-2016-9264[0]:
global-buffer-overflow in printMP3Headers (listmp3.c)

CVE-2016-9265[1]:
divide-by-zero in printMP3Headers (listmp3.c)

CVE-2016-9266[2]:
left shift in listmp3.c

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-9264
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9264
[1] https://security-tracker.debian.org/tracker/CVE-2016-9265
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9265
[2] https://security-tracker.debian.org/tracker/CVE-2016-9266
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9266
Please adjust the affected versions in the BTS as needed.


Regards,

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

Bug#838415: marked as done (Wrong package name, installs typelib file into wrong directory)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 19:00:12 +
with message-id 
and subject line Bug#838415: fixed in urfkill 0.5.0-5
has caused the Debian Bug report #838415,
regarding Wrong package name, installs typelib file into wrong directory
to be marked as done.

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

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


-- 
838415: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gir1.2-urfkill-glib0
Version: 0.5.0-4
Severity: serious

Hi,

please follow /usr/share/doc/gobject-introspection/policy.txt when
package typelib files.

In case of gir1.2-urfkill-glib0, debian/gir1.2-urfkill-glib0.install is
broken and installs the files as
/usr/lib/Urfkill-0.5.typelib

Since multiarch paths are allowed for typelib files, just use
usr/lib/*/girepository-1.0/Urfkill-*.typelib

Please also name the package accordingly, in your case, this would be
gir1.2-urfkill-0.5

Last but not least, you need to use the gir addon via

dh $@ --with gir




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

Kernel: Linux 4.7.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)
--- End Message ---
--- Begin Message ---
Source: urfkill
Source-Version: 0.5.0-5

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

Debian distribution maintenance software
pp.
Keng-Yu Lin  (supplier of updated urfkill 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: Thu, 20 Oct 2016 15:45:03 +0800
Source: urfkill
Binary: urfkill liburfkill-glib0 liburfkill-glib-dev liburfkill-glib0-dbg 
gir1.2-urfkill-0.5
Architecture: source amd64
Version: 0.5.0-5
Distribution: unstable
Urgency: low
Maintainer: Keng-Yu Lin 
Changed-By: Keng-Yu Lin 
Description:
 gir1.2-urfkill-0.5 - GObject introspection data for the urfkill library
 liburfkill-glib-dev - wireless killswitch management library (development 
files)
 liburfkill-glib0 - wireless killswitch management library
 liburfkill-glib0-dbg - wireless killswitch management library (debug symbols)
 urfkill- wireless killswitch management daemon for laptops
Closes: 838415
Changes:
 urfkill (0.5.0-5) unstable; urgency=low
 .
   [Michael Biebl]
   * Follow gobject introspection policy (Closes: #838415)
 .
   [Keng-Yu Lin]
   * Use dpkg-trigger to call ldconfig for liburfkill-glib0
 - Add debian/liburfkill-glib0.triggers; remove debian/postinst
   * Bump Standards-Version to 3.9.8
   * Library gir1.2-urfkill-glib0 is renamed to gir1.2-urfkill-0.5,
 added the Breaks and Replaces in debian/control
Checksums-Sha1:
 c83e4a79176fd5910a21bd60f97928150b721561 2328 urfkill_0.5.0-5.dsc
 688994215a26082b3de95e1d2e72cf46c8a3804a 4104 urfkill_0.5.0-5.debian.tar.xz
 66600765ff02532fcc541610432f71d1366143dc 4862 
gir1.2-urfkill-0.5_0.5.0-5_amd64.deb
 426916a300f6c51582c7f0dca33c81d19b3aaabc 18152 
liburfkill-glib-dev_0.5.0-5_amd64.deb
 90c8a760e6cacbe45777e82803946ae188f98694 113626 
liburfkill-glib0-dbg_0.5.0-5_amd64.deb
 ab0342fc6fa85124541d7795f5b043a93c25fd8c 12132 
liburfkill-glib0_0.5.0-5_amd64.deb
 eeb1a01b724161e8f53a4515ffceb767dbafea5e 11524 
urfkill_0.5.0-5_20161110T102219z-0a9f9c47.buildinfo
 c759eb96db830206720dbb761ae786d143a3e491 36764 urfkill_0.5.0-5_amd64.deb
Checksums-Sha256:
 f8857800d89c75a0d2ab4d153cc01d037ab4d6421848f03d18ad3aa4d738e241 2328 
urfkill_0.5.0-5.dsc
 55dcaee1603ec2c5a5cb0be17c93d34a5d55533ccac9a49d2009001c840c81aa 4104 
urfkill_0.5.0-5.debian.tar.xz
 25e4b4a163c7a1583a2f3cc7e2a5fd9488a20a2f662213bd4279e47cbe4ce7bb 4862 
gir1.2-urfkill-0.5_0.5.0-5_amd64.deb
 e1a1b705798d492dab42bb74f0f8199e0ac032fb583652daf15d90ae9f1ac8e6 18152 
liburfkill-glib-dev_0.5.0-5_amd64.deb
 

Processed: jemalloc: jemalloc uses a hard coded page size detected during build

[Debian Bug Tracking System]

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

> clone 832931 -1
Bug #832931 [src:mariadb-10.0] mariadb-10.0: FTBFS on powerpc
Bug 832931 cloned as bug 843926
> reassign -1 libjemalloc1
Bug #843926 [src:mariadb-10.0] mariadb-10.0: FTBFS on powerpc
Bug reassigned from package 'src:mariadb-10.0' to 'libjemalloc1'.
No longer marked as found in versions mariadb-10.0/10.0.26-0+deb8u1.
No longer marked as fixed in versions mariadb-10.0/10.0.27-1.
> retitle -1 jemalloc uses a hard coded page size detected during build
Bug #843926 [libjemalloc1] mariadb-10.0: FTBFS on powerpc
Changed Bug title to 'jemalloc uses a hard coded page size detected during 
build' from 'mariadb-10.0: FTBFS on powerpc'.
> thanks
Stopping processing here.

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

Bug#842878: Asterisk crashes with pjproject 2.5.5

[Gedalya]

On 11/10/2016 05:26 AM, Bernhard Schmidt wrote:
> I have just uploaded 2.5.5~dfsg-3 with all patches bundled in Asterisk
> applied. Please take a look, should be available shortly.

Installed, works just fine.

Bug#832931: jemalloc hard codes page size during build

[Thadeu Lima de Souza Cascardo]

clone -1 -2
reassign -2 libjemalloc1
retitle -2 jemalloc uses a hard coded page size detected during build
bye


So, I traced this to jemalloc using the incorrect page size during
runtime. In fact, it detects the page size during build and set it up.
This has a large potential for a mess. And what a mess!

So, jemalloc in jessie has been built on a 4KiB-page system, and, this,
has a hard-coded page size of 4KiB. While jemalloc in sid has a
64KiB-page size. When we try to build mariadb on jessie on a 4KiB-page
size system, everything goes well. When we build it on partch, with a
64-bit 64KiB-page size kernel, things break, if it's a jessie jemalloc.

Later upstream versions seem to support multiple page sizes during
build.

For MariaDB specifically, one option would be to build it without
jemalloc. Other users would still be likely affected, however.

Cascardo.

Bug#843922: stockfish: FTBFS: g++: error: unrecognized command line option '-m32'

[Sven Joachim]

Source: stockfish
Version: 8-1
Severity: serious

Your package fails to build on most architectures, because it calls g++
with the '-m32' option which is not generally supported.  Besides that,
the Config information looks very wrong on some architectures,
e.g. arm64[1], s390x[2] and mips64el[3] are apparently all wrongly
recognized as 32-bit architectures.

Could you please have a look?


1. 
https://buildd.debian.org/status/fetch.php?pkg=stockfish=arm64=8-1=1478719816
2. 
https://buildd.debian.org/status/fetch.php?pkg=stockfish=s390x=8-1=1478721845
3. 
https://buildd.debian.org/status/fetch.php?pkg=stockfish=mips64el=8-1=1478734250

Bug#843838: [pkg-bacula-devel] Bug#843838: Bug#843838: Bug#843838: Fail to access config file

[Sven Hartge]

On 10.11.2016 18:51, Jörg Frings-Fürst wrote:

> I guess that the error is the wrong group.

Of course, this is obvious.

> But the error comes not from use rsync without --numeric-ids.
> I don't use rsync, I have moved the hard disk with dd.
> 
> But also I have no idea from where the dirmngr comes.

I also have no idea, but I find it very suspicious that every group that
should be "bacula" is "dirmngr" on your system, as if someone/something
changed /etc/group or replaced it with a one not belonging to the system.

> A note:
> 
> If you change "the way the daemons are started" please check and change
> the required user/group.

I tested this change on several systems, some newly installed Sid, some
upgraded from Jessie, some even upgraded from Squeeze and older.

Every sane system had the correct groups and users for /etc/bacula/*.

The only change for permissions and owners was needed for
/etc/bacula/bacula-sd.conf and this is done in bacula-sd.postinst.

In my opinion this problem is not a bug in the bacula package but your
system was broken to begin with and this change just exposed it.

You need to find out who or what made the changes to /etc/group as more
problems may linger.

I personally also don't see an obligation for Debian packages to check
every possible angle an administrator could have manually broken their
system and try to work around this, but YMMV.

Just broadly changing and overwriting every permission in /etc/bacula/
is also wrong, as the administrator might have made working changes
which we don't want to destroy.

Grüße,
Sven.





signature.asc
Description: OpenPGP digital signature

Processed: Re: [deb-dpdk] Bug#843864: dpdk-*-dkms: module FTBFS for Linux 4.8: unconditionally tries to build for the running kernel

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #843864 [dpdk-igb-uio-dkms,dpdk-rte-kni-dkms] dpdk-*-dkms: module FTBFS for 
Linux 4.8: unconditionally tries to build for the running kernel
Added tag(s) pending.

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

Bug#843864: [deb-dpdk] Bug#843864: dpdk-*-dkms: module FTBFS for Linux 4.8: unconditionally tries to build for the running kernel

[Luca Boccassi]

Control: tags -1 pending

On Thu, 2016-11-10 at 11:39 +0100, Andreas Beckmann wrote:
> Package: dpdk-igb-uio-dkms,dpdk-rte-kni-dkms
> Version: 16.07-1
> Severity: serious
> 
> the host is running 4.6.0-1-amd64, testing the package in
> a sid chroot with 4.8.0-1-amd64 headers installed:
> 
> DKMS make.log for dpdk-igb-uio-16.07 for kernel 4.8.0-1-amd64 (x86_64)
> Thu Nov 10 10:34:32 UTC 2016
> make[1]: *** /lib/modules/4.6.0-1-amd64/build: No such file or directory.  
> Stop.
> /usr/share/dpdk//mk/rte.module.mk:79: recipe for target 'igb_uio.ko' failed
> make: *** [igb_uio.ko] Error 2
> 
> DKMS make.log for dpdk-rte-kni-16.07 for kernel 4.8.0-1-amd64 (x86_64)
> Thu Nov 10 10:36:52 UTC 2016
> make[1]: *** /lib/modules/4.6.0-1-amd64/build: No such file or directory.  
> Stop.
> /usr/share/dpdk//mk/rte.module.mk:79: recipe for target 'rte_kni.ko' failed
> make: *** [rte_kni.ko] Error 2
> 
> 
> Andreas

Thanks, fixed in git, pending next upload.

Kind regards,
Luca Boccassi


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

Bug#843838: [pkg-bacula-devel] Bug#843838: Bug#843838: Fail to access config file

[Jörg Frings-Fürst]

Am Donnerstag, den 10.11.2016, 17:04 +0100 schrieb Sven Hartge:
> On 10.11.2016 16:41, Jörg Frings-Fürst wrote:
> > Am Donnerstag, den 10.11.2016, 09:25 +0100 schrieb Sven Hartge:
> > > Was the system in question at some time in the past cloned/copied
> > > via
> > > rsync (without using --numeric-ids) or any other method while
> > > having
> > > been bootet from a rescue medium like GRML or Knoppix?
> > One year ago I have move the system 1:1 (tested) to a new
> > hardrive. 
> > And the error occurred after the last update.
> 
> The error is triggered by a change in the way the daemons are
> started,
> as indicated in the changelog, but the core error is the wrong group
> (dirmngr != bacula) on your system.
> 
> I really think this happened during your system move (it happened to
> me
> as well in the past, forgot to add --numeric-ids to rsync) but you
> did
> not notice it, because most users either matched or the programs
> don't
> care about them, because they are started as root.
> 
> I guess if you check other dynamic system users (meaning users
> created
> by packaging scripts and not hardcoded into base-passwd) and groups
> you
> will still find additional mismatches somewhere in /etc and other
> places.
> 

I guess that the error is the wrong group. But the error comes not from
use rsync without --numeric-ids. I don't use rsync, I have moved the
hard disk with dd.

But also I have no idea from where the dirmngr comes.

A note:

If you change "the way the daemons are started" please check and change
the required user/group.

> Grüße,
> Sven.
> 

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#843916: debian-installer: fails to FTBFS when u-boot bits go missing

[Cyril Brulebois]

Hi,

Martin Michlmayr  (2016-11-10):
> * Cyril Brulebois  [2016-11-10 18:27]:
> > Once a fix is implemented for this specific issue, it would be nice to
> > know what to do with the kirkwood/u-boot things for openrd. If they're
> > not going to work (again/at all), the relevant code should go away
> > from debian-installer.git; or am I missing anything?
> 
> Sorry, I learned about the removal recently but forgot to update d-i.
> I pinged the upstream maintainer recently and I hope the u-boot images
> will be back in time for stretch.

Thanks for updating master, and for the comment in the commit message.

Shared responsibility anyway, d-i daily builds should have detected the
removal. ;) I'll fix that once I've nothing else to do for the release
(and check through a local removal/revert of your patch).


KiBi.


signature.asc
Description: Digital signature

Processed: [bts-link] source package ghostscript

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package ghostscript
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #843324 (http://bugs.debian.org/843324)
> # Bug title: ghostscript crashes on some machines, much of the time
> #  * http://bugs.ghostscript.com/show_bug.cgi?id=695862
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 843324 + fixed-upstream
Bug #843324 [ghostscript] ghostscript crashes on some machines, much of the time
Added tag(s) fixed-upstream.
> usertags 843324 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:heimdal

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:heimdal
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #822749 (http://bugs.debian.org/822749)
> # Bug title: heimdal ftbfs on all 32bit architectures
> #  * https://github.com/heimdal/heimdal/issues/175
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 822749 + fixed-upstream
Bug #822749 [src:heimdal] heimdal ftbfs on all 32bit architectures
Added tag(s) fixed-upstream.
> usertags 822749 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 822749 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#843916: debian-installer: fails to FTBFS when u-boot bits go missing

[Martin Michlmayr]

* Cyril Brulebois  [2016-11-10 18:27]:
> Once a fix is implemented for this specific issue, it would be nice to
> know what to do with the kirkwood/u-boot things for openrd. If they're
> not going to work (again/at all), the relevant code should go away
> from debian-installer.git; or am I missing anything?

Sorry, I learned about the removal recently but forgot to update d-i.
I pinged the upstream maintainer recently and I hope the u-boot images
will be back in time for stretch.

-- 
Martin Michlmayr
http://www.cyrius.com/

Processed: [bts-link] source package node-cli

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package node-cli
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #809252 (http://bugs.debian.org/809252)
> # Bug title: node-cli: insecure use of temporary files
> #  * https://github.com/node-js-libs/cli/issues/81
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 809252 + fixed-upstream
Bug #809252 [node-cli] node-cli: insecure use of temporary files
Added tag(s) fixed-upstream.
> usertags 809252 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#843916: debian-installer: fails to FTBFS when u-boot bits go missing

[Cyril Brulebois]

Package: debian-installer
Version: 20161031
Severity: serious
Justification: FTBFS(ish)

(X-D-Cc: u-boot Maintainer & Uploaders; please keep them in the loop
when replying; also debian-arm@ for good measure.)

Hi,

Steve noted that the armel build fails on the cdimage side because
kirkwood/u-boot stuff is missing for openrd. This isn't entirely
surprising because the latest u-boot upload to unstable, which got
used to build debian-installer 20161031 had:
| u-boot (2016.09+dfsg1-2) unstable; urgency=medium
[…]
|   * Remove openrd targets, as they do not boot (Closes: #837629).
| 
|  -- Vagrant Cascadian   Sun, 23 Oct 2016 19:36:36 -0700

I might have missed messages on debian-boot@, but a quick search on
kirkwood or openrd doesn't get me any unread messages warning us about
their imminent removal. It really would be nice to make sure
debian-boot@ knows about such things in advance (even better if I get
explicitly cc'ed on this so as to make sure I don't miss something
affecting next d-i releases).


That being said, there's still the issue of debian-installer's build
system not detecting this issue, which is what this bug report is
about.

Once a fix is implemented for this specific issue, it would be nice to
know what to do with the kirkwood/u-boot things for openrd. If they're
not going to work (again/at all), the relevant code should go away
from debian-installer.git; or am I missing anything?

Input welcome.


KiBi.

Bug#841574: marked as done (atig: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: db.execute "VACUUM status")

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 17:18:31 +
with message-id 
and subject line Bug#841574: fixed in atig 0.6.1-2
has caused the Debian Bug report #841574,
regarding atig: FTBFS: ERROR: Test "ruby2.3" failed:  Failure/Error: 
db.execute "VACUUM status"
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.)


-- 
841574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: atig
Version: 0.6.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  Failure/Error: db.execute "VACUUM status"
> 
>  SQLite3::SQLException:
>unknown database status
>  # ./lib/atig/db/statuses.rb:126:in `block in cleanup'
>  # ./lib/atig/db/sql.rb:27:in `execute'
>  # ./lib/atig/db/statuses.rb:121:in `cleanup'
>  # ./spec/db/statuses_spec.rb:180:in `block (2 levels) in  (required)>'
> 
> Top 10 slowest examples (11.24 seconds, 90.5% of total time):
>   Atig::Db::Statuses should cleanup
> 10.39 seconds ./spec/db/statuses_spec.rb:174
>   Atig::Db::Statuses should call listeners
> 0.10167 seconds ./spec/db/statuses_spec.rb:41
>   Atig::Db::Statuses should have uniq tid/sid when removed
> 0.10135 seconds ./spec/db/statuses_spec.rb:164
>   Atig::Db::Statuses should have unique tid
> 0.09696 seconds ./spec/db/statuses_spec.rb:73
>   Atig::Db::Statuses should remove by id
> 0.09585 seconds ./spec/db/statuses_spec.rb:159
>   Atig::Db::Statuses should be found by tid
> 0.09113 seconds ./spec/db/statuses_spec.rb:104
>   Atig::Db::Statuses should be found by screen_name
> 0.09076 seconds ./spec/db/statuses_spec.rb:132
>   Atig::Db::Statuses should be re-openable
> 0.08963 seconds ./spec/db/statuses_spec.rb:37
>   Atig::Db::Statuses should be found by screen_name with limit
> 0.08954 seconds ./spec/db/statuses_spec.rb:148
>   Atig::Db::Statuses should not contain duplicate
> 0.08811 seconds ./spec/db/statuses_spec.rb:56
> 
> Top 10 slowest example groups:
>   Atig::Db::Statuses
> 0.77699 seconds average (11.65 seconds / 15 examples) 
> ./spec/db/statuses_spec.rb:6
>   Atig::Db::Lists
> 0.03209 seconds average (0.32088 seconds / 10 examples) 
> ./spec/db/lists_spec.rb:5
>   Atig::Db::Followings when it is empty
> 0.0305 seconds average (0.0305 seconds / 1 example) 
> ./spec/db/followings_spec.rb:5
>   Atig::Db::Followings when updated users
> 0.02754 seconds average (0.27539 seconds / 10 examples) 
> ./spec/db/followings_spec.rb:20
>   Atig::Command::Autofix
> 0.00496 seconds average (0.00991 seconds / 2 examples) 
> ./spec/command/autofix_spec.rb:5
>   Atig::Command::Whois
> 0.00195 seconds average (0.00586 seconds / 3 examples) 
> ./spec/command/whois_spec.rb:8
>   Atig::Command::Destroy when remove recently tweet
> 0.00188 seconds average (0.00565 seconds / 3 examples) 
> ./spec/command/destroy_spec.rb:21
>   Atig::Command::Favorite
> 0.00183 seconds average (0.00916 seconds / 5 examples) 
> ./spec/command/favorite_spec.rb:5
>   Atig::Command::Thread
> 0.00175 seconds average (0.01222 seconds / 7 examples) 
> ./spec/command/thread_spec.rb:5
>   Atig::Command::Option when have bool property
> 0.0015 seconds average (0.003 seconds / 2 examples) 
> ./spec/command/option_spec.rb:44
> 
> Finished in 12.41 seconds (files took 0.50439 seconds to load)
> 182 examples, 1 failure
> 
> Failed examples:
> 
> rspec ./spec/db/statuses_spec.rb:174 # Atig::Db::Statuses should cleanup
> 
> [Coveralls] Outside the Travis environment, not sending data.
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby2.3" failed: 

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/atig_0.6.1-1_unstable.log

A list of current common problems and possible solutions is available at

Bug#843838: [pkg-bacula-devel] Bug#843838: Bug#843838: Fail to access config file

[Sven Hartge]

On 10.11.2016 16:41, Jörg Frings-Fürst wrote:
> Am Donnerstag, den 10.11.2016, 09:25 +0100 schrieb Sven Hartge:

>> Was the system in question at some time in the past cloned/copied via
>> rsync (without using --numeric-ids) or any other method while having
>> been bootet from a rescue medium like GRML or Knoppix?

> One year ago I have move the system 1:1 (tested) to a new hardrive. 
> And the error occurred after the last update.

The error is triggered by a change in the way the daemons are started,
as indicated in the changelog, but the core error is the wrong group
(dirmngr != bacula) on your system.

I really think this happened during your system move (it happened to me
as well in the past, forgot to add --numeric-ids to rsync) but you did
not notice it, because most users either matched or the programs don't
care about them, because they are started as root.

I guess if you check other dynamic system users (meaning users created
by packaging scripts and not hardcoded into base-passwd) and groups you
will still find additional mismatches somewhere in /etc and other places.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#843888: marked as done (haskell-cabal-install: FTBFS: Couldn't match type `Distribution.Package.PackageIdentifier' with `Cabal-1.24.0.0:Distribution.Package.PackageIdentifier')

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 16:03:40 +
with message-id 
and subject line Bug#843888: fixed in haskell-cabal-install 1.24.0.1-2
has caused the Debian Bug report #843888,
regarding haskell-cabal-install: FTBFS: Couldn't match type 
`Distribution.Package.PackageIdentifier' with 
`Cabal-1.24.0.0:Distribution.Package.PackageIdentifier'
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.)


-- 
843888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-cabal-install
Version: 1.24.0.1-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-cabal-install fails to build from source in unstable/amd64:

  […]

  touch configure-ghc-stamp
  . /usr/share/haskell-devscripts/Dh_Haskell.sh && \
  build_recipe
  Running debian/hlibrary.setup build --builddir=dist-ghc
  Building cabal-install-1.24.0.1...
  Preprocessing executable 'cabal' for cabal-install-1.24.0.1...
  [  1 of 106] Compiling Distribution.Client.Glob ( 
Distribution/Client/Glob.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Glob.o )
  [  2 of 106] Compiling Distribution.Client.Utils.Json ( 
Distribution/Client/Utils/Json.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Utils/Json.o )
  [  3 of 106] Compiling Distribution.Client.Utils.LabeledGraph ( 
Distribution/Client/Utils/LabeledGraph.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Utils/LabeledGraph.o )
  [  4 of 106] Compiling Distribution.Client.Dependency.Modular.Version ( 
Distribution/Client/Dependency/Modular/Version.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Dependency/Modular/Version.o 
)
  [  5 of 106] Compiling Distribution.Client.Dependency.Modular.PSQ ( 
Distribution/Client/Dependency/Modular/PSQ.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Dependency/Modular/PSQ.o )
  [  6 of 106] Compiling Distribution.Client.Dependency.Modular.Package ( 
Distribution/Client/Dependency/Modular/Package.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Dependency/Modular/Package.o 
)
  [  7 of 106] Compiling Distribution.Client.PackageUtils ( 
Distribution/Client/PackageUtils.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/PackageUtils.o )
  [  8 of 106] Compiling Distribution.Client.Haddock ( 
Distribution/Client/Haddock.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Haddock.o )
  [  9 of 106] Compiling Distribution.Client.Compat.FilePerms ( 
Distribution/Client/Compat/FilePerms.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Compat/FilePerms.o )
  [ 10 of 106] Compiling Distribution.Client.ParseUtils ( 
Distribution/Client/ParseUtils.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/ParseUtils.o )
  [ 11 of 106] Compiling Distribution.Client.Compat.Semaphore ( 
Distribution/Client/Compat/Semaphore.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Compat/Semaphore.o )
  [ 12 of 106] Compiling Distribution.Client.Compat.ExecutablePath ( 
Distribution/Client/Compat/ExecutablePath.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Compat/ExecutablePath.o )
  [ 13 of 106] Compiling Distribution.Client.JobControl ( 
Distribution/Client/JobControl.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/JobControl.o )
  [ 14 of 106] Compiling Distribution.Client.Compat.Process ( 
Distribution/Client/Compat/Process.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Compat/Process.o )
  [ 15 of 106] Compiling Distribution.Client.Init.Licenses ( 
Distribution/Client/Init/Licenses.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Init/Licenses.o )
  [ 16 of 106] Compiling Distribution.Client.PkgConfigDb ( 
Distribution/Client/PkgConfigDb.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/PkgConfigDb.o )
  [ 17 of 106] Compiling Distribution.Client.GZipUtils ( 
Distribution/Client/GZipUtils.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/GZipUtils.o )
  [ 18 of 106] Compiling Distribution.Client.World ( 
Distribution/Client/World.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/World.o )
  [ 19 of 106] Compiling Distribution.Client.ComponentDeps ( 
Distribution/Client/ComponentDeps.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/ComponentDeps.o )
  [ 20 of 106] Compiling Distribution.Client.PackageIndex ( 
Distribution/Client/PackageIndex.hs, 

Bug#828234: marked as done (anon-proxy: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 15:50:49 +
with message-id 
and subject line Bug#843821: Removed package(s) from unstable
has caused the Debian Bug report #828234,
regarding anon-proxy: FTBFS with openssl 1.1.0
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.)


-- 
828234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: anon-proxy
Version: 00.05.38+20081230-3
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/anon-proxy_00.05.38+20081230-3_amd64-20160529-1404

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Version: 00.05.38+20081230-4+rm

Dear submitter,

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

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

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

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

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

Bug#839626: marked as done (anon-proxy: outdated and unmaintained upstream)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 15:50:49 +
with message-id 
and subject line Bug#843821: Removed package(s) from unstable
has caused the Debian Bug report #839626,
regarding anon-proxy: outdated and unmaintained upstream
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.)


-- 
839626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: anon-proxy
severity: serious
x-debbugs-cc: pkg-privacy-maintain...@lists.alioth.debian.org

On Sun, Oct 02, 2016 at 05:49:29PM +0200, intrigeri wrote:
> Holger Levsen:
> > I noticed src:anon-proxy was uploaded today (*) and I am wondering: does it
> > still work at all? Is it recommended to use it at all?
> 
> It seems that upstream development stopped in 2009. There have been
> quite some developments in this area since then (most of it being
> reflected in updates to the Tor design), and I have concerns that
> anon-proxy may not safe to use nowadays.
> 
> It seems that their set of free relays is very low:
> https://anon.inf.tu-dresden.de/status.php?lang=en
> 
> I guess that Lunar would know more than me about it, but with the
> limited info I have in hand, I would recommend _not_ including
> anon-proxy in any stable Debian release (and even more so an outdated
> release).

ok, thanks, for now just filing a bug to prevent it from reaching testing.

If this situation doesn't change it's probably proper to file an RM bug
to get the package removed from unstable too.


-- 
cheers,
Holger


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 00.05.38+20081230-4+rm

Dear submitter,

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

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

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

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

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

Bug#843894: marked as done (monit: FTBFS: missing dependency on zlib)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 15:50:48 +
with message-id 
and subject line Bug#843894: fixed in monit 1:5.20.0-2
has caused the Debian Bug report #843894,
regarding monit: FTBFS: missing dependency on zlib
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.)


-- 
843894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: monit
Version: 1:5.20.0-1
Severity: serious
Justification: fails to build from source
User: helm...@debian.org
Usertags: rebootstrap

monit FTBFS in sid. Excerpt from the build log:

| checking for zlibVersion in -lz... no
| configure: error: libz not found
|   "tail -v -n +0 config.log"

Let me propose a wild guess: libssl-dev formerly depended on zlib1g-dev
and no longer does that in sid. monit needs zlib1g-dev for building. Now
that the dependency is dropped, it fails to build.

=> I guess adding zlib1g-dev to Build-Depends fixes this FTBFS.

Helmut
--- End Message ---
--- Begin Message ---
Source: monit
Source-Version: 1:5.20.0-2

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

Debian distribution maintenance software
pp.
Sergey B Kirpichev  (supplier of updated monit 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: Thu, 10 Nov 2016 17:35:09 +0300
Source: monit
Binary: monit
Architecture: source amd64
Version: 1:5.20.0-2
Distribution: unstable
Urgency: medium
Maintainer: Sergey B Kirpichev 
Changed-By: Sergey B Kirpichev 
Description:
 monit  - utility for monitoring and managing daemons or similar programs
Closes: 843894
Changes:
 monit (1:5.20.0-2) unstable; urgency=medium
 .
   * Fix FTBFS, add deps on zlib1g-dev (Closes: #843894)
   * Bump up Standards-Version (to 3.9.8)
Checksums-Sha1:
 aba23b3e76d888df5d4f06a06267d160ff0c7595 1956 monit_5.20.0-2.dsc
 9c83124582f8e77f672a2f86e52e4b8da8afae99 28100 monit_5.20.0-2.debian.tar.xz
 382585d6568f52c80e5da2feb1fe0b5f161c9031 666932 monit-dbgsym_5.20.0-2_amd64.deb
 d706eda2caa6443d6efe9a6697542709d6949161 4967 
monit_5.20.0-2_20161110T150032z-448dca03.buildinfo
 db15a655023ae9565bff112ab9ed06d997bc915b 308792 monit_5.20.0-2_amd64.deb
Checksums-Sha256:
 9b6b151cc2d0501c78ceda9dff1f3eb292ae70aaf0127bdbea3d18b37451e717 1956 
monit_5.20.0-2.dsc
 a469c839552d77388c7acc1c345ac619f15583146969d31adf2590f34390cace 28100 
monit_5.20.0-2.debian.tar.xz
 16d6d11acaf8c5c1f959a99a55474b38d5777ab41e062480b3c359175a62ba64 666932 
monit-dbgsym_5.20.0-2_amd64.deb
 973ea8fe9b11a4b71681123dadea184b8739062cf21c29c578312d6d47b3d734 4967 
monit_5.20.0-2_20161110T150032z-448dca03.buildinfo
 e99ecba3447c6b1ff279a1da3152dbc96aaf6eda9b46dd71ead29049596fb622 308792 
monit_5.20.0-2_amd64.deb
Files:
 87c2fbc5e538d76a9aade9fece5b69a0 1956 admin optional monit_5.20.0-2.dsc
 cb7824cbd492e2e6740a670b9f75d70c 28100 admin optional 
monit_5.20.0-2.debian.tar.xz
 0675cab57eb355358c33e2b2865b3970 666932 debug extra 
monit-dbgsym_5.20.0-2_amd64.deb
 448dca032e37d45b5b202e58cf3c72c6 4967 admin optional 
monit_5.20.0-2_20161110T150032z-448dca03.buildinfo
 077925ebca41ec586392db3973458e09 308792 admin optional monit_5.20.0-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYJJDpAAoJEDnJoLZAJirw5gQP/2xbqOdWEGspHNICSc37tzo1
PedCGB6Vz2IuaSNK1Ti0mEdMzHEGXoo5v1Cy0I8W1ltVCw/7favIwjOm1gEYepA2
1q+JGceKXlefsQVqcAjJ8KgZhHIcbFqQfUZex+Zb/FiXyDPL+HXeoHE94tgfzRMg
P9ya7CnRyOuXdYdpkK7B9eGh220Hl/PMQrBdCQWqcjCIwDxs7A7oAEw+7QHIFaZQ
crBfob/QItOcrXeR137ztls6WgC00RgfotSdiaAY3allzLeu6YVHU9cSTdEP0nk2
ak8OyF71jpNxOgIRDnenU0R/M3UPTgoWOeezUVf6VAB8PvKhiuxoeB8N5W41ftpn
qJioUbmm+8NuKjaWVlcCEZuw3Uhl+pUDw7XXgl/bOxYQMyq4sWNt/Kij2rFfz1Dm
CX9uohZye3zFaA3s8r3/+X1uhn71tPjgLzFV7VDsGnGqSnB/9TjCLoEFiDZ5h7Rw
vp5u+O0EUvneYkjJTJ+kSVCLUQ4A/e1E4qEkkop2zW5HhS7P7jGGpYNBvwCueU+Y
Qhud/Kw3ek5iFqv15+bwOPwsR08/u02eQ6B+2MT3+BNgq8Ep3RVpiloPhgPNVuYi
2QAaFhpKdOm6jILJFmhGjYVUBi9GRnJBMEHAKGZvoDetQjV1ZAhbZijU9nVI//Ac
Q7eIDXDZusg4WIvm+Rhg
=PDXZ

Bug#836437: marked as done (FTBFS: Could not find 'gemojione' (>= 2.2.1, ~> 2.2) - did find: [gemojione-3.1.0])

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 15:54:45 +
with message-id 
and subject line Bug#843883: Removed package(s) from unstable
has caused the Debian Bug report #836437,
regarding FTBFS: Could not find 'gemojione' (>= 2.2.1, ~> 2.2) - did find: 
[gemojione-3.1.0]
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.)


-- 
836437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: ruby-gitlab-emoji
version: 0.3.1-2
severity: serious

gitlab 8.10.5 now depends on ruby-gemojione directly. Once gitlab 8.10.5
enters testing, ruby-gitlab-emoji can be removed.

GEM_PATH= ruby2.3 -e gem\ \"gitlab_emoji\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not
find 'gemojione' (>= 2.2.1, ~> 2.2) - did find: [gemojione-3.1.0]
(Gem::LoadError)
Checked in
'GEM_PATH=/home/debci/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
execute `gem env` for more information
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1438:in `block in
activate_dependencies'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in `each'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in
`activate_dependencies'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1409:in `activate'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block
in gem'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in
`synchronize'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
from -e:1:in `'
bigdecimal (1.2.8)
did_you_mean (1.0.0)
diff-lcs (1.2.5)
gemojione (3.1.0)
gitlab_emoji (0.3.1)
io-console (0.4.5)
json (2.0.1, 1.8.3)
minitest (5.9.0)
net-telnet (0.1.1)
power_assert (0.2.7)
psych (2.0.17)
rake (10.5.0)
rdoc (4.2.1)
rspec (3.4.0)
rspec-core (3.4.3)
rspec-expectations (3.4.0)
rspec-mocks (3.4.1)
rspec-support (3.4.1)
test-unit (3.1.7)
thread_order (1.1.0)
adt-run [17:14:47]: test command1: ---]
adt-run [17:14:47]: test command1:  - - - - - - - - - - results - - - -
- - - - - -
command1 FAIL non-zero exit status 1
adt-run [17:14:48]:  summary
command1 FAIL non-zero exit status 1



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.3.1-2+rm

Dear submitter,

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

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

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

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

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

Bug#837644: marked as done (ruby-devise-async is not compatible with devise >= 4.0)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 15:53:15 +
with message-id 
and subject line Bug#843880: Removed package(s) from unstable
has caused the Debian Bug report #837638,
regarding ruby-devise-async is not compatible with devise >= 4.0
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.)


-- 
837638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: ruby-devise-async
version: 0.9.0-1
severity: serious

This was introduced as a dependency for gitlab, but gitlab does not
depend on it anymore (removed from Gemfile). We can safely remove the
dependency in gitlab's debian/control. Once that version enters testing,
we can remove ruby-devise-async.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.9.0-1+rm

Dear submitter,

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

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

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

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

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

Bug#837638: marked as done (ruby-devise-async: Incompatible with ruby-devise 4)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 15:53:15 +
with message-id 
and subject line Bug#843880: Removed package(s) from unstable
has caused the Debian Bug report #837638,
regarding ruby-devise-async: Incompatible with ruby-devise 4
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.)


-- 
837638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-devise-async
Version: 0.9.0-1
Severity: serious

Ever since ruby-devise 4.1.1-2 was uploaded to Debian unstable,
ruby-devise-async has been failing its autopkgtests.

https://ci.debian.net/packages/r/ruby-devise-async/unstable/amd64/

I looked upstream and it's apparently a known issue:

https://github.com/mhfs/devise-async/issues/94

Thanks,
Jeremy
--- End Message ---
--- Begin Message ---
Version: 0.9.0-1+rm

Dear submitter,

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

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

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

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

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

Bug#833234: openvpn-blacklist: diff for NMU version 0.5+nmu1

[Jamie Strandboge]

On Thu, 2016-11-10 at 10:25 +, Jonathan Wiltshire wrote:
> Control: tags 833234 + patch
> Control: tags 833234 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for openvpn-blacklist (versioned as 0.5+nmu1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
> 
> Regards.

Thanks! This looks good to me.

-- 
Jamie Strandboge | http://www.canonical.com



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

Bug#843908: marked as done (API/ABI change without corresponding soname change)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 17:46:06 +0200
with message-id <1478792766.2285.242.ca...@debian.org>
and subject line Re: Bug#843908: Acknowledgement (API/ABI change without 
corresponding soname change)
has caused the Debian Bug report #843908,
regarding API/ABI change without corresponding soname change
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.)


-- 
843908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zeromq3
Version: 4.2.0-1
Severity: grave

Hi,

the symbol zpoller_ignore_interrupts was removed in 4.2.0 (as also
mentioned in the release notes), and replaced by zpoller_set_nonstop.

Unfortunately this didn't go together with a change of the soname, thus
breaking all existing packages that currently link against zmq and use
that symbol.


According to the release notes there are also more symbols that were
removed / replaced by something else, or even worse, signatures of
functions changed while keeping the old function name.


See https://github.com/zeromq/czmq/releases


Sebastian

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Hi again,

nevermind, this was a local problem on this system. The API changes
were already in previous versions, and are even in stable.

Sorry for the noise

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

Bug#843908: API/ABI change without corresponding soname change

[Sebastian Dröge]

Package: zeromq3
Version: 4.2.0-1
Severity: grave

Hi,

the symbol zpoller_ignore_interrupts was removed in 4.2.0 (as also
mentioned in the release notes), and replaced by zpoller_set_nonstop.

Unfortunately this didn't go together with a change of the soname, thus
breaking all existing packages that currently link against zmq and use
that symbol.


According to the release notes there are also more symbols that were
removed / replaced by something else, or even worse, signatures of
functions changed while keeping the old function name.


See https://github.com/zeromq/czmq/releases


Sebastian

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

Bug#843838: [pkg-bacula-devel] Bug#843838: Fail to access config file

[Jörg Frings-Fürst]

Hello Sven,


Am Donnerstag, den 10.11.2016, 09:25 +0100 schrieb Sven Hartge:
> On 10.11.2016 08:05, Jörg Frings-Fürst wrote:
> 
> > # ls -l /etc/bacula/
> > insgesamt 104
> > -rw-r- 1 root   dirmngr 9343 Feb 20  2016 bacula-dir.conf
> > -rw-r- 1 root   bacula  9156 Aug 18 14:12 bacula-dir.conf.dist
> > -rw-r- 1 root   dirmngr 1024 Sep 29  2013 bacula-fd.conf
> 
> This looks highly suspicious and reminds me of something that
> happened
> to me in the past:
> 
> Was the system in question at some time in the past cloned/copied via
> rsync (without using --numeric-ids) or any other method while having
> been bootet from a rescue medium like GRML or Knoppix?
> 

One year ago I have move the system 1:1 (tested) to a new hardrive. 
And the error occurred after the last update.

> It seems the numerical UID in the rootfs got messed up.
> 
> Could you also please provide the output of
> 
> ls -ln /etc/bacula
> getent group dirmngr
> getent group bacula
> 

$ ls -ln /etc/bacula
insgesamt 104
-rw-r- 1   0 129 9343 Feb 20  2016 bacula-dir.conf
-rw-r- 1   0 134 9156 Aug 18 14:12 bacula-dir.conf.dist
-rw-r- 1   0 129 1024 Sep 29  2013 bacula-fd.conf
-rw-r- 1   0   0 1127 Aug 18 14:12 bacula-fd.conf.dist
-rw-r- 1 129 129 3338 Sep 12  2014 bacula-sd.conf
-rw-r- 1 129 134 8070 Aug 18 14:12 bacula-sd.conf.dist
-rw-r- 1   0 129  175 Feb 24  2014 bat.conf
-rw-r- 1   0 134  180 Aug 18 14:12 bat.conf.dist
-rw-r- 1   0 129  172 Sep 29  2013 bconsole.conf
-rw-r- 1   0 134  266 Aug 18 14:12 bconsole.conf.dist
-rw--- 1   0   0  442 Feb 24  2014 common_default_passwords
-rw--- 1   0 129  442 Dez 12  2013 common_default_passwords.dist
-rw-r- 1   0 129  926 Okt 20  2014 filesets.conf
drwxr-xr-x 2   0   0 4096 Nov  9 06:13 scripts
-rw-r- 1   0 129 3396 Sep 12  2014 server-ixion.conf
-rw-r- 1   0 129 3433 Mai  1  2014 server-neptun.conf
-rw-r- 1   0 129  583 Apr 18  2014 tray-monitor.conf
-rw-r- 1   0 129  583 Dez 12  2013 tray-monitor.conf.dist
-rw-r- 1   0 129 3590 Feb 20  2016 ws-merkur.conf
-rw-r- 1   0 129 3436 Mai  2  2014 ws-triton.conf
-rw-r- 1   0 129 3127 Mai  1  2014 ws-zaubermaus.conf

$ getent group dirmngr
dirmngr:x:129:

$ getent group bacula
bacula:x:134:


> Grüße,
> Sven.
> 
> 

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#843874: dpkg: segfaults installing desktop-base 9.0.0~exp1 on amd64

[Guillem Jover]

Hi!

On Thu, 2016-11-10 at 16:24:13 +0100, Guillem Jover wrote:
> This appears to be a problem with reportbroken_retexitstatus() in
> src/error.c when printing out the packages affected by the errors, so
> not something dangerous, but still annoying and wrong.
> 
> From your backtrace it seems the function which has accumulated the
> package names cannot access those pointers anymore. And even though I
> cannot reproduce I think I know what's going on.
> 
> The latest releases started freeing the memory pool when releaseing
> the database journal. Which means that this invalidates those stored
> references. I'll copy those strings for the next release so that we
> can still free the db.
> 
> If you can still reproduce at will, I might like to provide a patch to
> make sure the fix works for you? If you could test this, probably
> later today, that'd be awesome!

Ok, it was too trivial to leave alone. :) Attached the proposed patch.

Thanks,
Guillem
diff --git i/src/errors.c w/src/errors.c
index 0869235..d580e35 100644
--- i/src/errors.c
+++ w/src/errors.c
@@ -47,7 +47,7 @@ static int nerrs = 0;
 
 struct error_report {
   struct error_report *next;
-  const char *what;
+  char *what;
 };
 
 static struct error_report *reports = NULL;
@@ -66,7 +66,7 @@ enqueue_error_report(const char *arg)
 abort_processing = true;
 nr= 
   }
-  nr->what= arg;
+  nr->what = strdup(arg);
   nr->next = NULL;
   *lastreport= nr;
   lastreport= >next;
@@ -109,6 +109,7 @@ reportbroken_retexitstatus(int ret)
 fputs(_("Errors were encountered while processing:\n"),stderr);
 while (reports) {
   fprintf(stderr," %s\n",reports->what);
+  free(reports->what);
   reports= reports->next;
 }
   }

Bug#843874: dpkg: segfaults installing desktop-base 9.0.0~exp1 on amd64

[Guillem Jover]

Hi!

On Thu, 2016-11-10 at 12:11:51 +0100, Andreas Beckmann wrote:
> Package: dpkg
> Version: 1.18.13
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: affects -1 + desktop-base

> during a test with piuparts I noticed a reproducible dpkg segfault
> when installing desktop-base/experimental in a sid+experimental amd64 chroot.

I cannot reproduce this, on a clean sid chroot by just installing
desktop-base from experimental. :(

> >From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package desktop-base.
>   (Reading database ... 5376 files and directories currently installed.)
>   Preparing to unpack .../desktop-base_9.0.0~exp1_all.deb ...
>   Unpacking desktop-base (9.0.0~exp1) ...
>   Processing triggers for libglib2.0-0:amd64 (2.50.2-1) ...
>   No schema files found: doing nothing.
>   Setting up desktop-base (9.0.0~exp1) ...
[…]
>   dpkg: error processing package desktop-base (--configure):
>subprocess installed post-installation script returned error exit status 1
>   Errors were encountered while processing:
>   E: Sub-process /usr/bin/dpkg received a segmentation fault.

This appears to be a problem with reportbroken_retexitstatus() in
src/error.c when printing out the packages affected by the errors, so
not something dangerous, but still annoying and wrong.

From your backtrace it seems the function which has accumulated the
package names cannot access those pointers anymore. And even though I
cannot reproduce I think I know what's going on.

The latest releases started freeing the memory pool when releaseing
the database journal. Which means that this invalidates those stored
references. I'll copy those strings for the next release so that we
can still free the db.

If you can still reproduce at will, I might like to provide a patch to
make sure the fix works for you? If you could test this, probably
later today, that'd be awesome!

Thanks,
Guillem

Processed: found 843861 in 1.10-1

[Debian Bug Tracking System]

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

> # according to LTS team triage
> found 843861 1.10-1
Bug #843861 [potrace] potrace: CVE-2016-8685 CVE-2016-8686
Marked as found in versions potrace/1.10-1.
> thanks
Stopping processing here.

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

Bug#828337: marked as done (haproxy: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 15:19:35 +
with message-id 
and subject line Bug#828337: fixed in haproxy 1.7~dev6-1
has caused the Debian Bug report #828337,
regarding haproxy: FTBFS with openssl 1.1.0
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.)


-- 
828337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haproxy
Version: 1.6.5-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/haproxy_1.6.5-1_amd64-20160529-1427

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: haproxy
Source-Version: 1.7~dev6-1

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated haproxy 
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: Thu, 10 Nov 2016 16:02:27 +0200
Source: haproxy
Binary: haproxy haproxy-doc vim-haproxy
Architecture: source
Version: 1.7~dev6-1
Distribution: experimental
Urgency: medium
Maintainer: Debian HAProxy Maintainers 

Changed-By: Apollon Oikonomopoulos 
Description:
 haproxy- fast and reliable load balancing reverse proxy
 haproxy-doc - fast and reliable load balancing reverse proxy (HTML documentatio
 vim-haproxy - syntax highlighting for HAProxy configuration files
Closes: 828337 840735
Changes:
 haproxy (1.7~dev6-1) experimental; urgency=medium
 .
   * New upstream development release (Closes: #828337)
   * Upload to experimental
   * d/watch: look for 1.7
   * B-D on zlib1g-dev
   * haproxy: Depend on lsb-base for the initscript
   * Ship additional plain-text documentation
   * haproxy-doc: ship HTML version of management.txt
   * Update the default SSL cipher list and add a link to Mozilla's SSL
 configuration generator (Closes: #840735)
   * d/rules: use SUBVERS to pass the Debian revision to HAPROXY_VERSION
Checksums-Sha1:
 82451dc980a1eddcbdae565464d21897237fc2e1 2317 haproxy_1.7~dev6-1.dsc
 05e1707ab37d328658065a26f3af9f5fdb391e8b 1721271 haproxy_1.7~dev6.orig.tar.gz
 8ade225e8d2fc1e399fb5ce5426cc49a3d56566c 61352 haproxy_1.7~dev6-1.debian.tar.xz
Checksums-Sha256:
 fed1ef778d8250b79b60dc2218f4d3fea256026c93542670287286e431657eae 2317 
haproxy_1.7~dev6-1.dsc
 b6aae0fef347ab213586d08f1f2fa60a41956ea5d4c6b0181a0dd9ae605229e3 1721271 
haproxy_1.7~dev6.orig.tar.gz
 cecb0154a1dc919cf9344164a20b9801985a5304bfe7655d67e3734a5eb26b3c 61352 
haproxy_1.7~dev6-1.debian.tar.xz
Files:
 d86ea3e0c429d37755c50ee7245c7359 2317 net optional haproxy_1.7~dev6-1.dsc
 e9f338c8b5731ba0827e5f280e8bafb2 1721271 net optional 
haproxy_1.7~dev6.orig.tar.gz
 8c39c703ff03ac87dc55f30b1b98db1c 61352 net optional 
haproxy_1.7~dev6-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIwBAEBCAAaBQJYJH6GExxhcG9pa29zQGRlYmlhbi5vcmcACgkQ263J6+6nxg40
6Q//UBBS7KFbnhH3Bdx058523ydh2m+xZ71vcxSbbqVK+8ShzfDZq6wU1DuxJ/an
9t7qxu+7eM9HamiO/r71kknOoyXjo/yskBCfsRnaRgG161isE3Oxo+IGSJHmoQmv
vYfRRcMM4ZC1MwX+Oic4zKpwkCt/nv5bQh9wasNhGfE1hsekc/Aa27tXlrc2zIXl
zYBQ9K19d9Ge58thgPMy0MWaeme2x2pModBz44J17zIlgzOI9VlEHPh6UPHf6R94
mtMEM3mVHDwJsnyQbgqf1AJ3BYjBdtktz6vg17PZMzV8xQwihS3JnDKjo5iPAqB6
R7gEfIi8OS4q7uKyboTdd4gokFRKe+tcJfsLaEY/Wr3hJt1ueEd1W3R7Gv79TTfK

Bug#840094: blends-dev: Does not recognize multiline dependencies

[Andreas Tille]

On Thu, Nov 10, 2016 at 01:53:20PM +0100, Ole Streicher wrote:
> 
> This is what I meant, and it is fixed by my last commit. Please try
> again ;-)

Quick note from bad connection.  Seems to work now.  I'll try later more
carefully.

Thanks for your contribution

 Andreas. 

-- 
http://fam-tille.de

Bug#843670: libgtkdatabox: Needs to be updated to use multiarch paths

[Aaron M. Ucko]

Source: libgtkdatabox
Version: 1:0.9.3.0+dfsg-1
Followup-For: Bug #843670

As the latest upload demonstrated, (automatic) builds against current
unstable are now failing:

  dh_install -plibgtkdatabox-0.9.3-0-glade 
usr/share/glade/catalogs/gtkdatabox.xml
   install -d 
debian/libgtkdatabox-0.9.3-0-glade//usr/share/glade/catalogs
   cp --reflink=auto -a 
debian/tmp/usr/share/glade/catalogs/gtkdatabox.xml 
debian/libgtkdatabox-0.9.3-0-glade//usr/share/glade/catalogs/
  dh_install -plibgtkdatabox-0.9.3-0-glade 
usr/lib/glade/modules/libgladedatabox.*
  dh_install: Cannot find (any matches for) 
"usr/lib/glade/modules/libgladedatabox.*" (tried in "." and "debian/tmp")
  dh_install: libgtkdatabox-0.9.3-0-glade missing files: 
usr/lib/glade/modules/libgladedatabox.*
  dh_install: missing files, aborting

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Processed: Re: monit FTBFS: missing dependency on zlib

[Debian Bug Tracking System]

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

> retitle 843894 monit: FTBFS: missing dependency on zlib
Bug #843894 [src:monit] monit FTBFS: missing dependency on zlib
Changed Bug title to 'monit: FTBFS: missing dependency on zlib' from 'monit 
FTBFS: missing dependency on zlib'.
> thanks
Stopping processing here.

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

Processed: Re: [ipython] IPython 2 launch fails with "No module named shutil_get_terminal_size"

[Debian Bug Tracking System]

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

> retitle 843898 IPython 2 launch fails with "No module named 
> shutil_get_terminal_size"
Bug #843898 [ipython] [ipython] IPython 2 launch fails with "No module named 
shutil_get_terminal_size"
Changed Bug title to 'IPython 2 launch fails with "No module named 
shutil_get_terminal_size"' from '[ipython] IPython 2 launch fails with "No 
module named shutil_get_terminal_size"'.
> thanks
Stopping processing here.

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

Bug#843898: [ipython] IPython 2 launch fails with "No module named shutil_get_terminal_size"

[Erbureth]

Package: ipython
Version: 5.1.0-2
Severity: grave

--- Please enter the report below this line. ---
Dear Maintainer,

launching `ipython` ends with following traceback:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/IPython/__init__.py", line 48, in 

from .core.application import Application
  File "/usr/lib/python2.7/dist-packages/IPython/core/application.py", line 25, 
in 
from IPython.core import release, crashhandler
  File "/usr/lib/python2.7/dist-packages/IPython/core/crashhandler.py", line 
28, in 
from IPython.core import ultratb
  File "/usr/lib/python2.7/dist-packages/IPython/core/ultratb.py", line 128, in 

from IPython.utils.terminal import get_terminal_size
  File "/usr/lib/python2.7/dist-packages/IPython/utils/terminal.py", line 22, 
in 
from backports.shutil_get_terminal_size import get_terminal_size as 
_get_terminal_size  

 
ImportError: No module named shutil_get_terminal_size

ipython3 works fine.

Regards,

Jan Kriho

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.7.0-1-amd64

Debian Release: stretch/sid
  950 testing ftp.cz.debian.org 
  900 unstableftp.cz.debian.org 
  850 experimentalftp.cz.debian.org 
  800 stable  security.debian.org 
  800 stable  ftp.cz.debian.org 
  800 stable  dl.google.com 
  500 stable-updates  ftp.cz.debian.org 

--- Package information. ---
Depends  (Version) | Installed
==-+-
python-ipython (= 5.1.0-2) | 5.1.0-2


Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#843895: disk-detect/multipath: run update-dev before probing for devices

[Allan Jacobsen]

Package: disk-detect
Version: 1.108
Severity: serious
Tags: d-i patch

This is a reminder to the install team to have a look at this patch
that has been on alioth since august last year.

It would be really nice to get debian stable install on multipath
disks to work :-)

The patch is here:
https://anonscm.debian.org/cgit/d-i/hw-detect.git/commit/?id=50b37c0d1677abea93e0de1436208cf0f10351e3

It is not my work, but I am hit by the bug, and would really like to
help in fixing this.

Best regards

Allan jacobsen

Bug#843894: monit FTBFS: missing dependency on zlib

[Helmut Grohne]

Source: monit
Version: 1:5.20.0-1
Severity: serious
Justification: fails to build from source
User: helm...@debian.org
Usertags: rebootstrap

monit FTBFS in sid. Excerpt from the build log:

| checking for zlibVersion in -lz... no
| configure: error: libz not found
|   "tail -v -n +0 config.log"

Let me propose a wild guess: libssl-dev formerly depended on zlib1g-dev
and no longer does that in sid. monit needs zlib1g-dev for building. Now
that the dependency is dropped, it fails to build.

=> I guess adding zlib1g-dev to Build-Depends fixes this FTBFS.

Helmut

Bug#841883: linux-image-4.7.0-1-686: cannot boot with 4.7.8-1, stuck at loading initrd

[Sharuzzaman Ahmat Raslan]

Hi Ben,

I'm using Testing, and the package is not in testing yet.

I have seen that the migration to testing was blocked by block-udeb..

Hopefully the package can be migrated to testing soon.

Thanks





On Tue, Nov 1, 2016 at 12:17 PM, Ben Hutchings  wrote:

> Control: tag -1 moreinfo
>
> I think this may be the same as bug #841850 which is fixed in version
> 4.8.5-1.  Please let us know whether that works for you.
>
> Ben.
>
> --
> Ben Hutchings
> Horngren's Observation:
>Among economists, the real world is often a special
> case.
>



-- 
Sharuzzaman Ahmat Raslan

Bug#843888: haskell-cabal-install: FTBFS: Couldn't match type `Distribution.Package.PackageIdentifier' with `Cabal-1.24.0.0:Distribution.Package.PackageIdentifier'

[Chris Lamb]

Source: haskell-cabal-install
Version: 1.24.0.1-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-cabal-install fails to build from source in unstable/amd64:

  […]

  touch configure-ghc-stamp
  . /usr/share/haskell-devscripts/Dh_Haskell.sh && \
  build_recipe
  Running debian/hlibrary.setup build --builddir=dist-ghc
  Building cabal-install-1.24.0.1...
  Preprocessing executable 'cabal' for cabal-install-1.24.0.1...
  [  1 of 106] Compiling Distribution.Client.Glob ( 
Distribution/Client/Glob.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Glob.o )
  [  2 of 106] Compiling Distribution.Client.Utils.Json ( 
Distribution/Client/Utils/Json.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Utils/Json.o )
  [  3 of 106] Compiling Distribution.Client.Utils.LabeledGraph ( 
Distribution/Client/Utils/LabeledGraph.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Utils/LabeledGraph.o )
  [  4 of 106] Compiling Distribution.Client.Dependency.Modular.Version ( 
Distribution/Client/Dependency/Modular/Version.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Dependency/Modular/Version.o 
)
  [  5 of 106] Compiling Distribution.Client.Dependency.Modular.PSQ ( 
Distribution/Client/Dependency/Modular/PSQ.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Dependency/Modular/PSQ.o )
  [  6 of 106] Compiling Distribution.Client.Dependency.Modular.Package ( 
Distribution/Client/Dependency/Modular/Package.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Dependency/Modular/Package.o 
)
  [  7 of 106] Compiling Distribution.Client.PackageUtils ( 
Distribution/Client/PackageUtils.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/PackageUtils.o )
  [  8 of 106] Compiling Distribution.Client.Haddock ( 
Distribution/Client/Haddock.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Haddock.o )
  [  9 of 106] Compiling Distribution.Client.Compat.FilePerms ( 
Distribution/Client/Compat/FilePerms.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Compat/FilePerms.o )
  [ 10 of 106] Compiling Distribution.Client.ParseUtils ( 
Distribution/Client/ParseUtils.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/ParseUtils.o )
  [ 11 of 106] Compiling Distribution.Client.Compat.Semaphore ( 
Distribution/Client/Compat/Semaphore.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Compat/Semaphore.o )
  [ 12 of 106] Compiling Distribution.Client.Compat.ExecutablePath ( 
Distribution/Client/Compat/ExecutablePath.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Compat/ExecutablePath.o )
  [ 13 of 106] Compiling Distribution.Client.JobControl ( 
Distribution/Client/JobControl.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/JobControl.o )
  [ 14 of 106] Compiling Distribution.Client.Compat.Process ( 
Distribution/Client/Compat/Process.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Compat/Process.o )
  [ 15 of 106] Compiling Distribution.Client.Init.Licenses ( 
Distribution/Client/Init/Licenses.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Init/Licenses.o )
  [ 16 of 106] Compiling Distribution.Client.PkgConfigDb ( 
Distribution/Client/PkgConfigDb.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/PkgConfigDb.o )
  [ 17 of 106] Compiling Distribution.Client.GZipUtils ( 
Distribution/Client/GZipUtils.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/GZipUtils.o )
  [ 18 of 106] Compiling Distribution.Client.World ( 
Distribution/Client/World.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/World.o )
  [ 19 of 106] Compiling Distribution.Client.ComponentDeps ( 
Distribution/Client/ComponentDeps.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/ComponentDeps.o )
  [ 20 of 106] Compiling Distribution.Client.PackageIndex ( 
Distribution/Client/PackageIndex.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/PackageIndex.o )
  [ 21 of 106] Compiling Distribution.Client.Init.Types ( 
Distribution/Client/Init/Types.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Init/Types.o )
  [ 22 of 106] Compiling Distribution.Client.BuildReports.Types ( 
Distribution/Client/BuildReports/Types.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/BuildReports/Types.o )
  [ 23 of 106] Compiling Distribution.Client.Compat.Time ( 
Distribution/Client/Compat/Time.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Compat/Time.o )
  [ 24 of 106] Compiling Paths_cabal_install ( 
dist-ghc/build/autogen/Paths_cabal_install.hs, 
dist-ghc/build/cabal/cabal-tmp/Paths_cabal_install.o )
  [ 25 of 106] Compiling Distribution.Client.Utils ( 
Distribution/Client/Utils.hs, 
dist-ghc/build/cabal/cabal-tmp/Distribution/Client/Utils.o )
  [ 26 of 106] Compiling Distribution.Client.FileMonitor ( 
Distribution/Client/FileMonitor.hs, 

Processed: Re: FTBFS depdnding on docs/apibuild.py timestamp (api docs not buildable)

[Debian Bug Tracking System]

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

> retitle 842452 FTBFS depending on docs/apibuild.py timestamp (api docs not 
> buildable)
Bug #842452 [libvirt] FTBFS depdnding on docs/apibuild.py timestamp (api docs 
not buildable)
Changed Bug title to 'FTBFS depending on docs/apibuild.py timestamp (api docs 
not buildable)' from 'FTBFS depdnding on docs/apibuild.py timestamp (api docs 
not buildable)'.
> thanks
Stopping processing here.

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

Bug#843797: marked as done (koji: FTBFS: help2man: can't get `--help' info from ./cli/koji)

[Debian Bug Tracking System]

Your message dated Thu, 10 Nov 2016 13:12:37 +
with message-id 
<1478783557.3755462.783487289.13561...@webmail.messagingengine.com>
and subject line Re: koji: FTBFS: help2man: can't get `--help' info from 
./cli/koji
has caused the Debian Bug report #843797,
regarding koji: FTBFS: help2man: can't get `--help' info from ./cli/koji
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.)


-- 
843797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: koji
Version: 1.10.0-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,

koji fails to build from source in unstable/amd64:

  […]

  dh_auto_build
make -j1
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20161109174748.li6xI7ndXh.db.koji/koji-1.10.0'
  read the makefile
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20161109174748.li6xI7ndXh.db.koji/koji-1.10.0'
  PYTHONPATH=. help2man --no-info --version-string=1.10.0 -n "Koji build 
client" ./cli/koji > debian/koji.1
  help2man: can't get `--help' info from ./cli/koji
  Try `--no-discard-stderr' if option outputs to stderr
  debian/rules:11: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161109174748.li6xI7ndXh.db.koji/koji-1.10.0'
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

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


koji.1.10.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Chris Lamb wrote:

> koji fails to build from source in unstable/amd64:

I can no longer reproduce this in today's sid so closing.


Regards,

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

Bug#843797: koji: FTBFS: help2man: can't get `--help' info from ./cli/koji

[Chris Lamb]

Chris Lamb wrote:

> koji fails to build from source in unstable/amd64:

I can no longer reproduce this in today's sid so closing.


Regards,

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

Bug#843865: keystone: FTBFS: ca: Can't parse "3650d" as a number

[Chris Lamb]

tags 843865 + patch
thanks

Patch attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/keystone/common/openssl.py b/keystone/common/openssl.py
index c581e8d..4ea2410 100644
--- a/keystone/common/openssl.py
+++ b/keystone/common/openssl.py
@@ -217,7 +217,7 @@ class BaseCertificateConfigure(object):
 self.exec_command(['openssl', 'ca', '-batch',
'-out', '%(signing_cert)s',
'-config', '%(ssl_config)s',
-   '-days', '%(valid_days)dd',
+   '-days', '%(valid_days)d',
'-cert', '%(ca_cert)s',
'-keyfile', '%(ca_private_key)s',
'-infiles', '%(request_file)s'])