Bug#753699: marked as done (lynx: Alert!: This client does not contain support for HTTPS URLs.)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 06:18:54 +
with message-id 
and subject line Bug#753699: fixed in lynx-cur 2.8.9dev1-2
has caused the Debian Bug report #753699,
regarding lynx: Alert!: This client does not contain support for HTTPS URLs.
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.)


-- 
753699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lynx-cur
Version: 2.8.9dev1-1
Severity: grave
Justification: renders package unusable

Just updated:

Unpacking lynx-cur (2.8.9dev1-1) over (2.8.8pre5-1) ...

After updating:

Alert!: This client does not contain support for HTTPS URLs.

lynx: Can't access startfile 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601683


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh

Versions of packages lynx-cur depends on:
ii  libbsd0   0.6.0-2
ii  libbz2-1.01.0.6-5
ii  libc6 2.19-4
ii  libidn11  1.28-2
ii  libncursesw5  5.9+20140118-1
ii  libtinfo5 5.9+20140118-1
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages lynx-cur recommends:
ii  mime-support  3.56

lynx-cur suggests no packages.

-- Configuration Files:
/etc/lynx-cur/lynx.cfg changed [not included]
/etc/lynx-cur/lynx.lss changed [not included]

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: lynx-cur
Source-Version: 2.8.9dev1-2

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

Debian distribution maintenance software
pp.
Atsuhito KOHDA  (supplier of updated lynx-cur 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: SHA1

Format: 1.8
Date: Tue, 08 Jul 2014 14:19:54 +0900
Source: lynx-cur
Binary: lynx-cur lynx-cur-wrapper lynx
Architecture: source all amd64
Version: 2.8.9dev1-2
Distribution: unstable
Urgency: medium
Maintainer: Atsuhito KOHDA 
Changed-By: Atsuhito KOHDA 
Description:
 lynx   - Text-mode WWW Browser (transitional package)
 lynx-cur   - Text-mode WWW Browser with NLS support (development version)
 lynx-cur-wrapper - Wrapper for lynx-cur (transitional package)
Closes: 753699
Changes:
 lynx-cur (2.8.9dev1-2) unstable; urgency=medium
 .
   * Fixed B-D by adding libgcrypt20-dev.  libgnutls-dev installs automatically
 libgcrypt11-dev but libgnutls28-dev doesn't install libgcrypt20-dev
 automatically.  Thanks to Thorsten Glaser  and Andreas
 Metzler   (Closes: #753699)
Checksums-Sha1:
 baffd4776f3fb689c336d2a5beb421f21cee5855 1316 lynx-cur_2.8.9dev1-2.dsc
 04c790b057a380d6f395246850e4481ced21 33272 lynx-cur_2.8.9dev1-2.diff.gz
 fc919aad324c6414568cf0aa2f0e5cdd4bdc3c88 230976 
lynx-cur-wrapper_2.8.9dev1-2_all.deb
 48872592841500756ce47ce7754041bea594de69 231372 lynx_2.8.9dev1-2_all.deb
 c5d464d32ade1df8206d514bb3066d4a5c26129a 1620870 lynx-cur_2.8.9dev1-2_amd64.deb
Checksums-Sha256:
 ff1960960abaf5d67273666f8c3222af94c4b0e8fc2b8bbfe6d627aeff851912 1316 
lynx-cur_2.8.9dev1-2.dsc
 04e38dcf16a5b56a70fab69fc7f1b1a983ad773bf7bf8c9435221365bee3a152 33272 
lynx-cur_2.8.9dev1-2.diff.gz
 0809576702e3aca561394b7ff8872fa4e5216e949732741f1fbc65268824dbb1 230976 
lynx-cur-wrapper_2.8.9dev1-2_all.deb
 d3fd3fc1383b2271a6e04db7d321110974f9c0aacda3ce605a89442941ca 231372 
lynx_2.8.9dev1-2_all.deb
 3c1a68ef309e1c49fd89c02081519530c4f09d5b8587a65d8a388bfbbf83949a 1620870 
lynx-cur_2.8.9dev1-2_amd64.deb
Files:
 47550f8a1920eb5161486f7df85aa484 230976 oldlibs extra 
lynx-cur-wrapper_2.8.9dev1-2_all.deb
 2741ddbb246207a1fbb4be660018f2ab 231372 oldlibs extra lynx_2.8.9dev1-2_all.deb
 9ea51b959b90bd3cc1626ae97f520acf 1620870 web extra 
lynx-cur_2.8.9dev1-2_amd64.deb
 dbf915654d6a5d9ddc679170f34492ee 1316 web extra lynx-cur_2.8.9dev1-2.dsc
 fd5bf7476488f3ecdebdc207d502bc6a 33272 web extra lynx-cur_2.8.9dev1-2.diff.gz

-BEGIN PGP SIGNATURE-
Version: Gn

Bug#752393: marked as done (smokeping: fails to build docs with pod2man due to unquoted slash)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 03:35:38 +
with message-id 
and subject line Bug#752393: fixed in smokeping 2.6.9-1
has caused the Debian Bug report #752393,
regarding smokeping: fails to build docs with pod2man due to unquoted slash
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.)


-- 
752393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: smokeping
Version: 2.6.9-1~exp0
Justification: fails to build from source
Severity: serious
Tags: upstream

Dear Maintainer,

   * What led up to the situation?

 Normal building of package.

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

 Tried to build package from source.

   * What was the outcome of this action?

 Failure to build man page from smokeping_config.pod file, which was in
 turn created from lib/Smokeping.pm

   * What outcome did you expect instead?

 Build docs correctly.

 NB: I have created a patch which fixes this but will send it separately
 shortly, as it affects several bugs in addition to this one.

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

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

Versions of packages smokeping depends on:
ii  adduser 3.113+nmu3
ii  debianutils 4.4
ii  fping   3.10-1
ii  libcgi-fast-perl5.18.2-4
ii  libconfig-grammar-perl  1.10-2
ii  libdigest-hmac-perl 1.03+dfsg-1
ii  libjs-cropper   1.2.2-1
ii  libjs-prototype 1.7.1-3
ii  libjs-scriptaculous 1.9.0-2
ii  librrds-perl1.4.8-1+b1
ii  libsnmp-session-perl1.13-1.1
ii  liburi-perl 1.60-1
ii  libwww-perl 6.06-1
ii  lsb-base4.1+Debian13
ii  perl5.18.2-4
ii  ucf 3.0030

Versions of packages smokeping recommends:
ii  apache2-bin [httpd-cgi]  2.4.9-2
ii  dnsutils 1:9.9.5.dfsg-4
ii  echoping 6.0.2-7
ii  libsocket6-perl  0.25-1

Versions of packages smokeping suggests:
ii  curl   7.37.0-1+b1
ii  exim4  4.82.1-1
ii  exim4-daemon-light [mail-transport-agent]  4.82.1-1+b1
pn  libauthen-radius-perl  
ii  libio-socket-ssl-perl  1.992-1
ii  libnet-dns-perl0.77-2
ii  libnet-ldap-perl   1:0.6400+dfsg-1
ii  libnet-telnet-perl 3.04-1
ii  openssh-client 1:6.6p1-5

-- Configuration Files:
/etc/smokeping/smokeping_secrets [Errno 13] Permission denied: 
u'/etc/smokeping/smokeping_secrets'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: smokeping
Source-Version: 2.6.9-1

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated smokeping package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Jul 2014 22:03:59 -0400
Source: smokeping
Binary: smokeping
Architecture: source all
Version: 2.6.9-1
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Description:
 smokeping  - latency logging and graphing system
Closes: 685811 699799 707225 724471 752393
Changes:
 smokeping (2.6.9-1) unstable; urgency=medium
 .
   * Upload to unstable
   * remove jsogo as uploader, as I haven't heard from him in years
   * Bug fix: missing "#MODE=slave" in /etc/default/smokeping, thanks to
 xavier renaut for reporting and Rowan Thorpe for confirmation (Closes:
 #685811).
   * follow anonscm.d.o rename
   * fix status doesn't use the pidfile (Closes: #699799)
   * use dh_autoreconf 

Bug#724471: marked as done (smokeping: FTBFS: configure.ac:24: error: required file 'conftools/compile' not found)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 03:35:38 +
with message-id 
and subject line Bug#724471: fixed in smokeping 2.6.9-1
has caused the Debian Bug report #724471,
regarding smokeping: FTBFS: configure.ac:24: error: required file 
'conftools/compile' not found
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.)


-- 
724471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:smokeping
Version: 2.6.8-2
Severity: serious
Justification: FTBFS

smokeping fails to build in a clean current sid pbuilder chroot:

make[1]: Entering directory `/tmp/buildd/smokeping-2.6.9'
aclocal
autoconf
automake
configure.ac:24: error: required file 'conftools/compile' not found
configure.ac:24:   'automake --add-missing' can install 'compile'
make[1]: *** [override_dh_auto_configure] Error 1
make[1]: Leaving directory `/tmp/buildd/smokeping-2.6.9'
make: *** [build] Error 2


Full log attached.
I: using fakeroot in build.
I: Current time: Wed Sep 18 21:31:17 EEST 2013
I: pbuilder-time-stamp: 1379529077
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/base+dh.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /dev/pts filesystem
I: Mounting /var/cache/pbuilder/ccache
I: policy-rc.d already exists
I: Setting up ccache
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 7.0.50~), autoconf, automake, librrds-perl, groff-base, 
libhtml-parser-perl, libdigest-hmac-perl, libwww-perl, liburi-perl, 
libcgi-fast-perl, libconfig-grammar-perl
dpkg-deb: building package `pbuilder-satisfydepends-dummy' in 
`/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 14836 files and directories currently installed.)
Unpacking pbuilder-satisfydepends-dummy (from 
.../pbuilder-satisfydepends-dummy.deb) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on autoconf; however:
  Package autoconf is not installed.
 pbuilder-satisfydepends-dummy depends on automake; however:
  Package automake is not installed.
 pbuilder-satisfydepends-dummy depends on librrds-perl; however:
  Package librrds-perl is not installed.
 pbuilder-satisfydepends-dummy depends on libhtml-parser-perl; however:
  Package libhtml-parser-perl is not installed.
 pbuilder-satisfydepends-dummy depends on libdigest-hmac-perl; however:
  Package libdigest-hmac-perl is not installed.
 pbuilder-satisfydepends-dummy depends on libwww-perl; however:
  Package libwww-perl is not installed.
 pbuilder-satisfydepends-dummy depends on liburi-perl; however:
  Package liburi-perl is not installed.
 pbuilder-satisfydepends-dummy depends on libcgi-fast-perl; however:
  Package libcgi-fast-perl is not installed.
 pbuilder-satisfydepends-dummy depends on libconfig-grammar-perl; 
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...
Initializing package states...
Writing extended state information...
The following NEW packages will be installed:
  autoconf{a} automake{a} autotools-dev{a} ca-certificates{a} fontconfig{a} 
  fontconfig-config{a} fonts-dejavu-core{a} libcairo2{a} 
  libcgi-fast-perl{a} libconfig-grammar-perl{a} libdatrie1{a} libdbi1{a} 
  libdigest-hmac-perl{a} libdrm2{a} libegl1-mesa{a} 
  libencode-locale-perl{a} libexpat1{a} libfcgi-perl{a} 
  libfile-listing-perl{a} libfontconfig1{a} libfreetype6{a} libgbm1{a} 
  libgl1-mesa-glx{a} libglapi-mesa{a} libgraphite2-3{a} libharfbuzz0a{a} 
  libhtml-parser-perl{a} libhtml-tagset-perl{a} libhtml-tree-perl{a} 
  libhttp-cookies-perl{a} libhttp-date-perl{a} libhttp-message-perl{a} 
  libhttp-negotiate-perl{a} libio-html-perl{a} libio-socket-ssl-perl{a} 
  libllvm3.2{a} liblwp-mediatypes-perl{a} liblwp-protocol-https-perl{a} 
  libnet-http-perl{a} libnet-ssleay-perl{a} libpango-1.0-0{a} 
  libpangocairo-1.0-0{a} libpangoft2-1.0-0{a} libpixman-1-0{a} 
 

Bug#724471: Bug#707225: smokeping: patch for bugs #707225, #724471 and #752393

[Antoine Beaupré]

On 2014-06-23 10:11:20, Rowan Thorpe wrote:
> I've attached an updated diff based on the below feedback. Because the changes
> only affect this bug I won't update the diff on the other two bugs until this
> version is confirmed good.
>
> On 14:20 Mon 23 Jun 2014, Niko Tyni wrote:
>> On Mon, Jun 23, 2014 at 01:44:17PM +0300, Rowan Thorpe wrote:
>>
>> > Attached is a debdiff for several smokeping bugs.
>>
>> Thanks for your work. I'm not the maintainer (anymore), so just
>> a couple of comments.

Thanks Rowan for those patches, and Niko for the review!

I have factored in what I think are the latest patches from Rowan, and
uploaded 2.6.9 to sid, so hopefully we'll have something to test in
jessie soon enough before the freeze that we can get some more testing.

Unfortunately, I mostly run Smokeping on production systems, which makes
this quite difficult to test for me - I'm working a little bit in the
blind here.

I have nevertheless reviewed the patches, and they seem good. I'm a
little hesitant about the documentation changes, because we're diverging
From upstream - Rowan, could you look at submitting those patches
upstream in a way that would work for both Debian and upstream?

Ideally we'd cut down on the number of patches in debian/patches, not
add to them. :) But of course, better to fix bugs than avoid patching...

Finally, Rowan, if you are interested, you could join me in maintaining
that package. Even if you are not a Debian maintainer, you can still
work on the git repository through the Alioth service. See this page to
get more information on how it works and getting an account:

https://wiki.debian.org/Alioth/PackagingProject

The workflow would basically be that you could commit the changes into
git, and then I could review them and upload the changes in the Debian
archive.

Smokeping packaging definitely needs help. I did some work in getting it
up to speed in the last 5 years, but the work is far from done, as can
be seen in the debian/TODO file and the numerous bugs found in the
Debian BTS.

Sorry if I've been a little slow with the patches, I'll try to be
swifter next time! :)

A.

-- 
Le péché est né avant la vertu, comme le moteur avant le frein.
 - Jean-Paul Sartre


pgpfmhj8rtIMh.pgp
Description: PGP signature

Processed: tagging 724471

[Debian Bug Tracking System]

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

> tags 724471 + pending
Bug #724471 [src:smokeping] smokeping: FTBFS: configure.ac:24: error: required 
file 'conftools/compile' not found
Added tag(s) pending.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#754059: [systemd-sysv] Conflicts with sysvinit-core

[Filipus Klutiero]

On 2014-07-07 13:04, Michael Biebl wrote:

Am 07.07.2014 18:50, schrieb Filipus Klutiero:

I suppose there's a reason why a conflict was declared. I didn't mean
declaring a conflict with sysvinit-core is a bug *per se*. The bug is to
conflict with a package of required priority, namely sysvinit-core. If
it's necessary to conflict with a required package, then something's
very wrong with the package.

Nope, it's not.
See also other init systems, like the upstart package, which declare the
same Conflicts/Replaces.





I did specify "If it's necessary to conflict with a required package". I assume 
you're implying that's not the case for systemd-sysv and will report a bug regarding 
sysvinit-core's priority.

--
Filipus Klutiero
http://www.philippecloutier.com


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Bug#751201: emacs-goodies-el: site-start files don't work

[Debian Bug Tracking System]

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

> severity 751201 normal
Bug #751201 [emacs-goodies-el] emacs-goodies-el: site-start files don't work
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#751201: emacs-goodies-el: site-start files don't work

[Peter S Galbraith]

severity 751201 normal
thanks

I can't reproduce this on up-to-date sid.  Waiting for further input but
let's not remove thispackage from testing just yet.  ;-)

Peter


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#736036: marked as done (please build-depend on libtiff-dev, not libtiff4-dev)

[Debian Bug Tracking System]

Your message dated Mon, 7 Jul 2014 17:07:47 -0700
with message-id 

and subject line Re: Bug#736036: upgrading to serious: libtiff4-dev is being 
removed
has caused the Debian Bug report #736036,
regarding please build-depend on libtiff-dev, not libtiff4-dev
to be marked as done.

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

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


-- 
736036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: perceptualdiff
Version: 1.1.1-1
User: q...@debian.org
Usertags: libtiff4-dev

The libtiff4-dev package is a transitional package that is going to
disappear soon.  Please update your build dependency from libtiff4-dev
to libtiff-dev.
--- End Message ---
--- Begin Message ---
The control file says this depends on libtiff-dev. My changelog says I fixed
this bug in the last upload, back in January. I think this bug is already fixed
and will mark it closed. Speak up and re-open if you disagree.

http://sources.debian.net/src/perceptualdiff/1.1.1-2/debian/control--- End Message ---

Bug#753820: marked as done (atril build-depends on obsolete transiionall package)

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 23:33:44 +
with message-id 
and subject line Bug#753820: fixed in atril 1.8.0+dfsg1-4
has caused the Debian Bug report #753820,
regarding atril build-depends on obsolete transiionall package
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.)


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

Package: atril
Severity: serious
Tags: patch

atril depends on the obsolete transitional package libtiff4-dev which 
has been removed in the latest version of the tiff source package.


The fix is trivial and obvious, change the build-dependency to libtiff-dev
--- End Message ---
--- Begin Message ---
Source: atril
Source-Version: 1.8.0+dfsg1-4

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated atril package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Jul 2014 01:15:47 +0200
Source: atril
Binary: atril atril-dbg atril-common libatrilview3 libatrilview-dev 
libatrilview3-dbg libatrildocument3 libatrildocument-dev libatrildocument3-dbg
Architecture: source all amd64
Version: 1.8.0+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: MATE Packaging Team 
Changed-By: Mike Gabriel 
Description:
 atril  - MATE document viewer
 atril-common - MATE document viewer (common files)
 atril-dbg  - MATE document viewer (debugging symbols)
 libatrildocument-dev - MATE document rendering library (development files)
 libatrildocument3 - MATE document rendering library
 libatrildocument3-dbg - MATE document rendering library (debugging symbols)
 libatrilview-dev - MATE document viewing library (development files)
 libatrilview3 - MATE document viewing library
 libatrilview3-dbg - MATE document viewing library (debugging symbols)
Closes: 753820
Changes:
 atril (1.8.0+dfsg1-4) unstable; urgency=medium
 .
   * debian/control:
 + Modify B-D: libtiff4-dev -> libtiff-dev. (Closes: #753820).
Checksums-Sha1:
 aa03b4c8d2ca5fc8d6e572e17ebdf05784a39768 2953 atril_1.8.0+dfsg1-4.dsc
 4d93a476ab7863b66a135477d06dba98fb154fea 11308 
atril_1.8.0+dfsg1-4.debian.tar.xz
 1588d755f2e08fb2782fa008fc145f3e8afad7fe 390920 
atril-common_1.8.0+dfsg1-4_all.deb
 3464ae3c26edddba44a5fcf1f54a98d52761eca4 150262 atril_1.8.0+dfsg1-4_amd64.deb
 b4e029b4b1427afedccf913703a01cdc10da8084 706872 
atril-dbg_1.8.0+dfsg1-4_amd64.deb
 8895035b7605f5a89fc32748dcf4d97f87b86827 92068 
libatrilview3_1.8.0+dfsg1-4_amd64.deb
 63ce57a46af8c707e2d4d857ba2f6994b8c44600 13326 
libatrilview-dev_1.8.0+dfsg1-4_amd64.deb
 8a55e367f1ce48bc45ef22c5628594ae875a3647 308164 
libatrilview3-dbg_1.8.0+dfsg1-4_amd64.deb
 a9aee923041ee2c29b4936dda91a008c4860e6bf 181478 
libatrildocument3_1.8.0+dfsg1-4_amd64.deb
 54292ec965124f28015c5865ac4af37549745168 23416 
libatrildocument-dev_1.8.0+dfsg1-4_amd64.deb
 f1a79ed73ff691ebefbaed5ea76fcffaaaeaee54 547238 
libatrildocument3-dbg_1.8.0+dfsg1-4_amd64.deb
Checksums-Sha256:
 fbb0fc209456df2c5c600e1b815eabe571d52070b62a25774a230cf2efb6e448 2953 
atril_1.8.0+dfsg1-4.dsc
 62764d569fe2e32784afd765ec235070b34d72e39eccdb531c3ab965e1f88773 11308 
atril_1.8.0+dfsg1-4.debian.tar.xz
 8c90ed360c8fdbb62e3ce926264547981e382d3cd4a15b56742953833f35fffe 390920 
atril-common_1.8.0+dfsg1-4_all.deb
 ae1665ced3d8472e30a2e20c01ed8f4ff981db14aabc1147fa203fc1c9f9d8de 150262 
atril_1.8.0+dfsg1-4_amd64.deb
 ca01ebe132444972c51c68928b8dc18509382e0204636c21b1e1eb1081cc8de4 706872 
atril-dbg_1.8.0+dfsg1-4_amd64.deb
 2851f86ed4560a4bc514a89c642364ebee7f1d3754b2d233d3f8e28f54d17b0f 92068 
libatrilview3_1.8.0+dfsg1-4_amd64.deb
 70c479e65cf2af454839bfc69c33e46a09aacfc74571176f2af9b5711094c480 13326 
libatrilview-dev_1.8.0+dfsg1-4_amd64.deb
 384e50b731e8bcfd8232e5d87600d70e397278f832c7eef3b571d09ae99101d1 308164 
libatrilview3-dbg_1.8.0+dfsg1-4_amd64.deb
 215a48052114fe9b8350ecde8694ea25f7564295549b89d820b53d9db1c239d4 181478 
libatrildocument3_1.8.0+dfsg1-4_amd64.deb
 eb4c97fae7a899fec5d46dd5c6aaec

Bug#738411: Re: libtext-kakasi-perl: FTBFS: Tests failures

[NOKUBI Takatsugu]

At Mon, 07 Jul 2014 19:57:40 +0200,
Emilio Pozuelo Monfort wrote:
> > This probrem is come from libkakasi. It is already fixed in
> > upstream CVS HEAD.
> > 
> > I'll release newer version of KAKASI in few week.
> 
> Any updates on this?

Some bugs are discovered, almost things were already fixed. I hope to
release in this week.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#738411: Re: libtext-kakasi-perl: FTBFS: Tests failures

[NOKUBI Takatsugu]

Ah, sorry. I misunderstood.

At Mon, 07 Jul 2014 19:57:40 +0200,
Emilio Pozuelo Monfort wrote:
> > This probrem is come from libkakasi. It is already fixed in
p> > upstream CVS HEAD.
> > 
> > I'll release newer version of KAKASI in few week.
> 
> Any updates on this?

The latest libkakasi (2.3.6-1) resolve the issue.

   dh_auto_test
make[1]: Entering directory 
'/home/knok/draft/debian/tmp/libtext-kakasi-perl-2.04'
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 
'blib/lib', 'blib/arch')" t/*.t
t/01-func.t  ok
t/02-obj.t . ok
t/03-encode.t .. ok
All tests successful.
Files=3, Tests=164,  1 wallclock secs ( 0.06 usr  0.02 sys +  0.20 cusr  0.04 
csys =  0.32 CPU)
Result: PASS


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#753964: partman-basicfilesystems: uninstallable on non-linux: dosfstools-udeb missing

[Cyril Brulebois]

Cyril Brulebois  (2014-07-06):
> This contributed to the following:
> | Date: Sun, 6 Jul 2014 05:01:15 +
> | From: udeb uninstallability watcher 
> | To: k...@debian.org
> | Subject: udeb uninstallability trend: worse (+43/-0)

And back to the previous situation after:
  udeb uninstallability trend: better (+0/-30) [kfreebsd-*]
  udeb uninstallability trend: better (+0/-13) [hurd-i386]

Thanks, Colin.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#723168: libmount1-udeb: uninstallable, depends on libselinux1

[Laurent Bigonville]

Le Sun, 6 Jul 2014 22:38:19 +0200,
Cyril Brulebois  a écrit :

> Hello Laurent and d-i people,

Hello Cyril,

> Laurent Bigonville  (2014-04-17):
> > Package: libmount1-udeb
> > Followup-For: Bug #723168
> > 
> > Hi,
> > 
> > I could start building a libselinux1-udeb package if you want.
> > 
> > I think that all the dependencies should be already present for
> > libselinux:
> > 
> >  Depends: libc6 (>= 2.14), libpcre3 (>= 8.10)
> > 
> > But this doesn't mean that we'll be able to do anything related to
> > selinux in the installer, there are other packages that would be
> > needed to do anything useful, but this would be a first step to
> > have SELinux related functions in d-i
> 
> maybe I'm missing something obvious but I fail to see how SELinux
> could be useful in the installer context.

Well my initial idea was to try to see if we could provide an installer
that was able to install a SELinux enabled machine on the first reboot
with all the files properly labeled on disk.

But as said this would require some changes in different components
(udpkg, add a refpolicy udeb,...), so this is maybe a bit premature to
start providing a udeb for libselinux.

> 
> I'm adding -boot@ to the loop to have more eyes on this.
> 

This was actually a wild idea and I didn't really checked in depth. So
if somebody is really interested in this, I could have a look otherwise
I'll put this in my longterm TODO list I guess.

Cheers,

Laurent Bigonville


> Mraw,
> KiBi.


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#753945: marked as done (FTBFS on kfreebsd-i386 (test segfaulting))

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 19:15:53 -0300
with message-id <2652935.7Eo6a9XRGg@luna>
and subject line Re: Bug#753945: FTBFS on kfreebsd-i386 (test segfaulting)
has caused the Debian Bug report #753945,
regarding FTBFS on kfreebsd-i386 (test segfaulting)
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.)


-- 
753945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gammaray
Version: 2.0.2-1
Severity: serious

Gammaray if FTBFS in kfreebsd-i386 due to a test failing.

This is stopping Qt 5 from migratin to testing.

The build log is



Kinds regards, Lisandro.

-- System Information:
Debian Release: jessie/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Sunday 06 July 2014 11:20:39 Lisandro Damián Nicanor Pérez Meyer wrote:
> Source: gammaray
> Version: 2.0.2-1
> Severity: serious
> 
> Gammaray if FTBFS in kfreebsd-i386 due to a test failing.

pochu gave it back and it worked this time, so closing.

-- 
"Los pibes no piden que levantemos un muro para que tengan un límite,
sino que los ayudemos a crecer en libertad."
  Padre Bergoglio - http://www.lanacion.com.ar/1153060

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#731415: marked as done (unrar-free is dead upstream and completely useless)

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 21:40:25 +
with message-id 
and subject line Bug#731415: fixed in unrar-free 1:0.0.1+cvs20140707-1
has caused the Debian Bug report #731415,
regarding unrar-free is dead upstream and completely useless
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.)


-- 
731415: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unrar-free
Version: 1:0.0.1+cvs20071127-2
Severity: serious

unrar-free is dead upstream.

unrar-free is completely useless, since the new format produced by all
RAR versions since 2001 (sic) is not supported.
It is already a tough task trying to find any rar archive at all that
unrar-free can unpack, and for any file you actually want to unpack
the chances that unrar-free can handle it are nil.

As Timo already pointed out in #312552, unar (sic) is an open source
software already in Debian that can actually unpack non-historic rar
archives.
--- End Message ---
--- Begin Message ---
Source: unrar-free
Source-Version: 1:0.0.1+cvs20140707-1

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated unrar-free 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Jul 2014 04:29:29 +0800
Source: unrar-free
Binary: unrar-free
Architecture: source i386
Version: 1:0.0.1+cvs20140707-1
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 unrar-free - Unarchiver for .rar files
Closes: 731415
Changes:
 unrar-free (1:0.0.1+cvs20140707-1) unstable; urgency=low
 .
   * New upstream release
 - Use unar to handle RAR3 format when it is installed (Closes: #731415)
   * Bump Standards-Version to 3.9.5: Nothing needs to be changed
Checksums-Sha1:
 bcadd785debccb144aea688224e413fa321d78eb 1879 
unrar-free_0.0.1+cvs20140707-1.dsc
 8bf14b9ca954bd2d5360443034efbaf9be9f81b7 129890 
unrar-free_0.0.1+cvs20140707.orig.tar.gz
 bd7267ae78661ffa732bd877410bc655f9cefdc5 5784 
unrar-free_0.0.1+cvs20140707-1.debian.tar.xz
 a8c9d4d8f260430be876227ab6820077b7ecca48 24042 
unrar-free_0.0.1+cvs20140707-1_i386.deb
Checksums-Sha256:
 1c0e1c5e533709200d78c4eb5ffd7d31b467a853cf0b45e005a3485f38ee7a65 1879 
unrar-free_0.0.1+cvs20140707-1.dsc
 30ba9f9f62abf7f14b7d516864d60fca43d48a93090179685780dd318dd2dba3 129890 
unrar-free_0.0.1+cvs20140707.orig.tar.gz
 4f1a234bd775ef537f4077bb2e5193ac3e9d43cb61fe83c9859a54af04582b7d 5784 
unrar-free_0.0.1+cvs20140707-1.debian.tar.xz
 6db9b622f0b90bdacb26b48d7c3d930aa06580167e3cb41b2eb27754975f35d3 24042 
unrar-free_0.0.1+cvs20140707-1_i386.deb
Files:
 191bab95eaa3670fb74f71adf45b0fdf 24042 utils optional 
unrar-free_0.0.1+cvs20140707-1_i386.deb
 6b1d82334917288cbe60b7861aa60505 1879 utils optional 
unrar-free_0.0.1+cvs20140707-1.dsc
 92755b66a3fe40eb325aa2a41b17d02e 129890 utils optional 
unrar-free_0.0.1+cvs20140707.orig.tar.gz
 60f127dacad273924ef85a59e4a4c273 5784 utils optional 
unrar-free_0.0.1+cvs20140707-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJTuwv3AAoJEPgLgUbQQog2XGYQAIRde7oEIJLTrarrqzSCrvRl
ezJfVE8+nB5+2qOcpRBi3eKdlUu5JBxL1vq/6yAZeqs7JzqMu44iIjf0pPLB/QDl
RyTBiO97rAgh8LxF2Yk/VYBwwihg+R38ii51x/0uKXjCWyI5eX3laFvfH7w3GUOu
h+zndofO4Hlex7wSSZ0jDzbbPXXRbLbFGWvH0aTKUONyuDvPlBi4Lev4ODCG7Ecx
wYdIIq+fTQf/8vKcpX+e0jhbup9fuVK016xnfNyo/96FDRJ8Q3Oh2kAf0eMXoWV6
YBz8ch0i91z+MuE+KLDzmbTeq0WENPrC3AYU/OFYp63IJCZQj/OmLEEZrkXTG30Y
huWR9pMw8NoTnZ2vCueXFCpGaLDrNOvuSE7Xf0X2OCNRs9eKN6+6JKWIxynYLkVt
XosbfGLzBqqqtrXVtLeQxAzt/g+g7hK0Jdh4if/FSa15Z8gyQ5Wn2AMFbWhlSEn9
rl3NIX+7AiWgqvm18J7s+oYicdQa+95ENdJdnQpy1FNk6rloEORFnfiwKWZcSmag
q7LWx6XTXNDXJBSAFRT6rvqScoh5DIACXX2bBHGla6M40dEatvoRUpqSxLBJ+WG+
6NGS1iNnNBzwiC65FEXo1a/9JiRiv+EAUVb6OhUl5RlHKfzqL4KmzFn/4sPo8Hc3
a2Haeab6vrZDwLqkUQyf
=mrwk
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#753941: libapt-pkg4.12: segfaults at debListParser::NewVersion

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #753941 [libapt-pkg4.12] libapt-pkg4.12: segfaults at 
debListParser::NewVersion
Severity set to 'important' from 'grave'

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#753941: libapt-pkg4.12: segfaults at debListParser::NewVersion

[David Kalnischkies]

Control: severity -1 important

Hi,

On Sun, Jul 06, 2014 at 04:00:29PM +0200, Zakaria ElQotbi wrote:
> Package: libapt-pkg4.12
> Version: 1.0.5
> Severity: grave
> Justification: renders package unusable

Thanks for the report!

These bugs are traditionally hard to tackle as they are hard to
reproduce (if at all possible). They depend on the order of sources.list
entries and the contents of the files downloaded as a result of that.
I am therefore downgrading a bit as this will resolve itself very very
likely with the next 'apt-get update'. Alternatively the posted
workaround works just as well. (and because you can hit it with any
version of apt from the last four years – so an RC-bugs would at the
most discourage people from upgrading to a security fix we had
recently…)


That said, I happen to know what is wrong this time as I saw it while
rewriting this codearea for a (still unfinished… damn) experimental
branch, which should have been public weeks ago… anyway, the simple fix
is in our debian/sid branch now waiting for the next upload.

As a (very) small reward for reporting this issue: The workaround will
actually make apt's cache generation slightly faster and is totally
harmless (if you don't happen to use insane high values, the equivalent
of 100MB should be enough, the current default is ~25MB). It is "very
small" though as it is probably not measurable…


Technical background:
In the dark ages (=before squeeze) if the cache was too small apt would
just error out ("mmap ran out of room"). In many many iterations
I worked on making the cache generation relocatable at runtime, so that
we can grow the underlying mmap by moving to a different address (as
growing but keeping the address is unlikely to work). We can't just
increase the cache size by default as on embedded devices we would eat
a good part of the available RAM this way… really bad if the kernel
OOM-killer is triggered…

The offender here is the line:
Ver->Section = UniqFindTagWrite("Section");

So the compiler figures out the storage location (Ver->Section), then
it calculates the value (return value of the function call) and stores
the value at the storage location – just that this is the old location
as the function call could potentially move the mmap… segfault.

So the solution is something like:
tempvalue = UniqFindTagWrite("Section");
Ver->Section = tempvalue;

Seems trivial, right? It is also the reason why regardless of how hard
you try to find all these instances, one or two are always slipping
through (but after 4 years, there can't be that many left, right? ;) )


Best regards

David Kalnischkies


signature.asc
Description: Digital signature

Bug#748694: sys/sdt.h is architecture specific, and causing issues on unsupported architectures

[Matthias Klose]

Am 07.07.2014 22:55, schrieb Sergio Durigan Junior:
>> Which architectures don't need it? Any architecture that support glibc
>> and gdb for example benefits from having sdt markers available.
> 
> Mark is right.
> 
> It seems it is never enough to repeat this, but  should not
> be related to SystemTap.  GDB makes a strong use of this header file,
> and as a matter of fact, GDB even implemented the support for userspace
> SDT probes on ARM *before* SystemTap did.  And I did not have to change
> anything on .
> 
> By reading the backlog of this bug, I see that the main problem seems to
> be the use of "arch:all" for this package (I am not considering the
> initial "bug" that was not a bug after all).  I am not a Debian
> maintainer, so I will not try to convince people (or doko, in this case)
> of the contrary.  However, making  available only on the
> architectures supported by SystemTap is bad for GDB, and I can provide a
> list of reasons if you want.
> 
> My request, then, is that you make this package available to the
> architectures where GDB is available.
> on 
> I hope you find this reasonable.

thanks, talking with mjw I think this is reasonable. however for debian
multiarch cross builds this header is seen on any cross build, even if it
shouldn't. I think the correct solution will be to keep system-tap-sdt-dev
architecture dependant and to ship the sdt.h headers on any arch.

  Matthias


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#731415: unrar-free is dead upstream and completely useless

[Ying-Chun Liu (PaulLiu)]

Hi,

What we really need is another script that mimic the unrar interface.
unar provides "lsar" and "unar" command for listing and extracting.
lsar can also outputs json format for programs to parse.
Someone whould really work on this.

BTW, I'm about to upload a new version of unrar-free to use unar to
extract RAR 3.0 format. But it is merely an workaround.
New programs should use "lsar" and "unar", or a script that uses these
commands.

Yours,
Paul

-- 
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) 



signature.asc
Description: OpenPGP digital signature

Bug#748694: sys/sdt.h is architecture specific, and causing issues on unsupported architectures

[Sergio Durigan Junior]

> Which architectures don't need it? Any architecture that support glibc
> and gdb for example benefits from having sdt markers available.

Mark is right.

It seems it is never enough to repeat this, but  should not
be related to SystemTap.  GDB makes a strong use of this header file,
and as a matter of fact, GDB even implemented the support for userspace
SDT probes on ARM *before* SystemTap did.  And I did not have to change
anything on .

By reading the backlog of this bug, I see that the main problem seems to
be the use of "arch:all" for this package (I am not considering the
initial "bug" that was not a bug after all).  I am not a Debian
maintainer, so I will not try to convince people (or doko, in this case)
of the contrary.  However, making  available only on the
architectures supported by SystemTap is bad for GDB, and I can provide a
list of reasons if you want.

My request, then, is that you make this package available to the
architectures where GDB is available.

I hope you find this reasonable.

Thanks,

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

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

[Debian Bug Tracking System]

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

> forwarded 754125 https://rt.cpan.org/Ticket/Display.html?id=97035
Bug #754125 [libimager-perl] libimager-perl: FTBFS on s390x
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=97035'.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#750351: New packages uploaded to mentors, sponsor needed

[Benedict Verhegghe]

New packages pyformex-0.9.1-1 are available here:
http://mentors.debian.net/package/pyformex

These sohuld fix the bug and provide much more functionality (new
upstream release).

Need a sponsor to upload them. Anyone wants to help?


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#736007: marked as done (please build-depend on libtiff-dev, not libtiff4-dev)

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 22:01:08 +0200
with message-id <53bafc84.9020...@bzed.de>
and subject line already fixed
has caused the Debian Bug report #736007,
regarding please build-depend on libtiff-dev, not libtiff4-dev
to be marked as done.

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

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


-- 
736007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gimp-plugin-registry
Version: 5.20120621
User: q...@debian.org
Usertags: libtiff4-dev

The libtiff4-dev package is a transitional package that is going to
disappear soon.  Please update your build dependency from libtiff4-dev
to libtiff-dev.
--- End Message ---
--- Begin Message ---
Version: 7.20140602
-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F--- End Message ---

Processed: reassign 752991 to python-matplotlib, forcibly merging 750630 752991

[Debian Bug Tracking System]

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

> reassign 752991 python-matplotlib 1.3.1-1+b1
Bug #752991 [python3-matplotlib] python3-matplotlib: pylab fails to be imported
Bug reassigned from package 'python3-matplotlib' to 'python-matplotlib'.
No longer marked as found in versions matplotlib/1.3.1-1.
Ignoring request to alter fixed versions of bug #752991 to the same values 
previously set
Bug #752991 [python-matplotlib] python3-matplotlib: pylab fails to be imported
Marked as found in versions matplotlib/1.3.1-1.
> forcemerge 750630 752991
Bug #750630 [python-matplotlib] python-matplotlib: Default backend 'tkagg' 
broken
Bug #751385 [python-matplotlib] newer python interfers with matplotlib
Bug #751692 [python-matplotlib] cannot import matplotlib.backends.tkagg 
(missing _tkagg.so)
Bug #752057 [python-matplotlib] python-tk: importing matplotlib does not work 
anymore
Bug #753243 [python-matplotlib] mypaint: FTBFS: ImportError: cannot import name 
_tkagg
Bug #752991 [python-matplotlib] python3-matplotlib: pylab fails to be imported
751055 was blocked by: 753243 751385 752057 751692 750630
751055 was not blocking any bugs.
Added blocking bug(s) of 751055: 752991
Added tag(s) sid, jessie, and patch.
Bug #751385 [python-matplotlib] newer python interfers with matplotlib
Bug #751692 [python-matplotlib] cannot import matplotlib.backends.tkagg 
(missing _tkagg.so)
Bug #752057 [python-matplotlib] python-tk: importing matplotlib does not work 
anymore
Bug #753243 [python-matplotlib] mypaint: FTBFS: ImportError: cannot import name 
_tkagg
Merged 750630 751385 751692 752057 752991 753243
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
750630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750630
751055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751055
751385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751385
751692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751692
752057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752057
752991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752991
753243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#754063: [Pkg-sysvinit-devel] Bug#754063: initscripts: no longer depends on ifupdown

[Steve Langasek]

Control: tags -1 moreinfo unreproducible
Control: severity -1 important

On Mon, Jul 07, 2014 at 10:07:10AM +0200, Michal Suchanek wrote:
> Package: initscripts
> Version: 2.88dsf-53.2
> Severity: grave
> Justification: renders package unusable

> I upgraded initscripts which no llonger depend on ifupdown.

> Hence I have no networking on next boot.

> IMHO this renders the initscripts unusable for 90% of users.

The git history shows that ifupdown has never been a dependency of the
initscripts package.  And there's no reason that initscripts should be
responsible for pulling this package onto the system; and upgrading
initscripts should not cause ifupdown to be *removed* from the system
either.

So why do you think this is an initscripts bug?

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature

Bug#749553: marked as done (cenon.app: FTBFS with gnustep-gui/0.24: TileScrollView.m:94:9: error: pointer value used where a floating point value was expected)

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 18:03:36 +
with message-id 
and subject line Bug#749553: fixed in cenon.app 4.0.2-1
has caused the Debian Bug report #749553,
regarding cenon.app: FTBFS with gnustep-gui/0.24: TileScrollView.m:94:9: error: 
pointer value used where a floating point value was expected
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.)


-- 
749553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cenon.app
Version: 3.93-1.2
Severity: important
Tags: sid jessie
User: pkg-gnustep-maintain...@lists.alioth.debian.org
Usertags: gnustep-gui0.24-transition gnustep-transition

This package fails to build on i386/amd64 with gnustep-gui/0.24.0-1
with the following error:

 Compiling file TileScrollView.m ...
TileScrollView.m: In function '-[TileScrollView zoomIn:]':
TileScrollView.m:94:9: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
 if (Diff((float)[[resPopupListButton itemAtIndex:row] tag] / 100.0, 
oldScaleFactor) < 0.001)
 ^
TileScrollView.m:94:9: warning: (Messages without a matching method signature 
[enabled by default]
TileScrollView.m:94:9: warning: will be assumed to return 'id' and accept 
[enabled by default]
TileScrollView.m:94:9: warning: '...' as arguments.) [enabled by default]
TileScrollView.m:94:9: error: pointer value used where a floating point value 
was expected
TileScrollView.m:94:9: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
TileScrollView.m:94:9: error: pointer value used where a floating point value 
was expected
TileScrollView.m:94:9: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
TileScrollView.m:94:9: error: pointer value used where a floating point value 
was expected
TileScrollView.m:101:5: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
 scaleFactor = [[resPopupListButton itemAtIndex:row] tag] / 100.0;
 ^
TileScrollView.m:101:62: error: invalid operands to binary / (have 'id' and 
'double')
 scaleFactor = [[resPopupListButton itemAtIndex:row] tag] / 100.0;
  ^
TileScrollView.m: In function '-[TileScrollView zoomOut:]':
TileScrollView.m:120:9: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
 if (Diff((float)[[resPopupListButton itemAtIndex:row] tag] / 100.0, 
oldScaleFactor) < 0.001)
 ^
TileScrollView.m:120:9: error: pointer value used where a floating point value 
was expected
TileScrollView.m:120:9: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
TileScrollView.m:120:9: error: pointer value used where a floating point value 
was expected
TileScrollView.m:120:9: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
TileScrollView.m:120:9: error: pointer value used where a floating point value 
was expected
TileScrollView.m:126:5: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
 scaleFactor = (float)[[resPopupListButton itemAtIndex:row] tag] / 100.0;
 ^
TileScrollView.m:126:5: error: pointer value used where a floating point value 
was expected
TileScrollView.m: In function '-[TileScrollView magnifyRegion:]':
TileScrollView.m:172:9: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
 if (Diff((float)[[resPopupListButton itemAtIndex:row] tag] / 100.0, 
oldScaleFactor) < 0.001)
 ^
TileScrollView.m:172:9: error: pointer value used where a floating point value 
was expected
TileScrollView.m:172:9: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
TileScrollView.m:172:9: error: pointer value used where a floating point value 
was expected
TileScrollView.m:172:9: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
TileScrollView.m:172:9: error: pointer value used where a floating point value 
was expected
TileScrollView.m:181:9: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
 scaleFactor = [[resPopupListButton itemAtIndex:row] tag] / 100.0;
 ^
TileScrollView.m:181:66: error: invalid operands to binary / (have 'id' and 
'double')
 scaleFactor = [[resPopupListButton itemAtIndex:row] tag] / 100.0;
  ^
TileScrollView.m:187:5: warning: 'NSCollectionViewItem' may not respond to 
'-tag' [enabled by default]
 scaleFa

Bug#753985: marked as done (gpgv-udeb: fails to validate Release files (missing sha256 support))

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 18:48:41 +
with message-id 
and subject line Bug#753985: fixed in gnupg 1.4.18-2
has caused the Debian Bug report #753985,
regarding gpgv-udeb: fails to validate Release files (missing sha256 support)
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.)


-- 
753985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpgv-udeb
Version: 1.4.18-1
Severity: grave
Tags: patch
Justification: renders package unusable

Hi folks,

I'm really sorry for:
 - having failed to reply to your request in time[1];
 - having failed to deliver any testing, which led to lost user time[2]
   and is going to cost another gnupg upload.

 1. https://lists.debian.org/debian-boot/2014/01/msg00129.html
 2. https://lists.debian.org/debian-boot/2014/07/msg7.html

I've finally spent some time on this, and checked the following things:

 a) A trivial removal of the --enable-minimal flag would need to go
together with disabling bzip2 support; resulting udebs would be
uninstallable due to a libbz2 dependency. d-i would then be bigger
but functional again.

 b) Thankfully we don't need to consider the backup plan mentioned in a)
since all we need is enabling sha256 support. Currently, Release
files include MD5+SHA1+SHA256. You'll find a tested patch attached.
(This means a whole installation using a netboot-gtk image.)

I also noticed "make check" isn't run for the udeb build; I don't think
it would hurt to do so (the testsuite is smart enough to notice support
for some bits wasn't enabled, see output below my signature), that's why
I'm including an extra patch adding that.

Sorry again…

Mraw,
KiBi.


Testsuite output for the udeb check:
| make[2]: Entering directory '/home/kibi/hack/gnupg.git/build-udeb/checks'
| gpg (GnuPG) 1.4.18
| Copyright (C) 2014 Free Software Foundation, Inc.
| License GPLv3+: GNU GPL version 3 or later 
| This is free software: you are free to change and redistribute it.
| There is NO WARRANTY, to the extent permitted by law.
| 
| Home: .
| Supported algorithms:
| Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
| Cipher: 3DES
| Hash: MD5, SHA1, RIPEMD160, SHA256, SHA224
| Compression: Uncompressed, ZIP, ZLIB
| PASS: version.test
| Hash algorithm SHA-384 is not installed (not an error)
| Hash algorithm SHA-512 is not installed (not an error)
| PASS: mds.test
| PASS: decrypt.test
| PASS: decrypt-dsa.test
| MD5 SHA1 RIPEMD160 SHA256 SHA224 | PASS: sigs.test
| PASS: sigs-dsa.test
| 3DES | PASS: encrypt.test
| 3DES | PASS: encrypt-dsa.test
| PASS: seat.test
| PASS: clearsig.test
| PASS: encryptp.test
| PASS: detach.test
| PASS: armsigs.test
| PASS: armencrypt.test
| PASS: armencryptp.test
| PASS: signencrypt.test
| PASS: signencrypt-dsa.test
| PASS: armsignencrypt.test
| PASS: armdetach.test
| PASS: armdetachm.test
| PASS: detachm.test
| PASS: genkey1024.test
| 3DES | PASS: conventional.test
| 3DES | PASS: conventional-mdc.test
| PASS: multisig.test
| PASS: verify.test
| PASS: armor.test
| ===
| All 27 tests passed
| ===
| make[2]: Leaving directory '/home/kibi/hack/gnupg.git/build-udeb/checks'
>From 716ad8686c8dc274d62399042cd89a1549ce817e Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Sun, 6 Jul 2014 21:25:45 +0200
Subject: [PATCH 1/2] Fix gpgv-udeb by adding --enable-sha256, which is needed
 to validate Release files.

---
 debian/changelog | 7 +++
 debian/rules | 2 +-
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 4987723..db5868a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+gnupg (1.4.18-2) UNRELEASED; urgency=medium
+
+  * Fix gpgv-udeb by adding --enable-sha256, which is needed to validate
+Release files.
+
+ -- Cyril Brulebois   Sun, 06 Jul 2014 21:10:24 +0200
+
 gnupg (1.4.18-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/rules b/debian/rules
index 683b8b2..6878842 100755
--- a/debian/rules
+++ b/debian/rules
@@ -22,7 +22,7 @@ CONFARGS  = --prefix=/usr --libexecdir=/usr/lib/ \
 --enable-noexecstack
 
 CONFARGS_FULL= --enable-mailto --with-mailprog=/usr/sbin/sendmail
-CONFARGS_MINIMAL = --enable-minimal --enable-rsa --disable-nls --disable-regex --disable-gnupg-iconv --disable-gettext --without-iconv --without-readline --without-zlib
+CONFARGS_MINIMAL = --enable-minimal --enable-rsa --disable-nls --disable-regex --disable-gnupg-iconv --disable-gettext --without-iconv --wi

Bug#750270: marked as done (readahead-fedora: FTBFS: Makefile:533: *** missing separator (did you mean TAB instead of 8 spaces?))

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 19:33:40 +
with message-id 
and subject line Bug#750270: fixed in readahead-fedora 2:1.5.6-5.1
has caused the Debian Bug report #750270,
regarding readahead-fedora: FTBFS: Makefile:533: *** missing separator (did you 
mean TAB instead of 8 spaces?)
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.)


-- 
750270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: readahead-fedora
Version: 2:1.5.6-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140601 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»/scripts'
> Makefile:533: *** missing separator (did you mean TAB instead of 8 spaces?).  
> Stop.
> make[3]: Leaving directory '/«PKGBUILDDIR»/scripts'
> Makefile:444: recipe for target 'all-recursive' failed
> make[2]: *** [all-recursive] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/01/readahead-fedora_1.5.6-5_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: readahead-fedora
Source-Version: 2:1.5.6-5.1

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated readahead-fedora 
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: SHA1

Format: 1.8
Date: Wed, 02 Jul 2014 20:50:57 +0200
Source: readahead-fedora
Binary: readahead-fedora
Architecture: source amd64
Version: 2:1.5.6-5.1
Distribution: unstable
Urgency: low
Maintainer: Raphael Geissert 
Changed-By: Petter Reinholdtsen 
Description:
 readahead-fedora - Fedora's implementation of readahead to preload boot 
process file
Closes: 750270
Changes:
 readahead-fedora (2:1.5.6-5.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix build problem caused by new automake (Closes: #750270).
Checksums-Sha1:
 63eeed2f11901a19e54f3b2d2645e193db6bf392 1231 readahead-fedora_1.5.6-5.1.dsc
 26da531e523d143fb5392cb2e6077d30624a0f94 21912 
readahead-fedora_1.5.6-5.1.diff.gz
 5d78e476e3abcab76e59ed70fdf14a98218c65c8 33766 
readahead-fedora_1.5.6-5.1_amd64.deb
Checksums-Sha256:
 5d22b6147c387f9b6986b9b56ea0051dbce78ce14bc3307dec8e8dbfb765e666 1231 
readahead-fedora_1.5.6-5.1.dsc
 0ffa332be5a3a9f4f6a79b18b2755f6f915d66867fe36fcc9963df77dee922bd 21912 
readahead-fedora_1.5.6-5.1.diff.gz
 c8a2f43c43771fd58b52db0e565e1593adb13c04357fed83dba1df52b384c9e8 33766 
readahead-fedora_1.5.6-5.1_amd64.deb
Files:
 65c74607ad2d38589b99c79a27c90ecf 33766 admin optional 
readahead-fedora_1.5.6-5.1_amd64.deb
 a1e1db6281ed546c87f41a8afb9067f1 1231 admin optional 
readahead-fedora_1.5.6-5.1.dsc
 146119da559f0d429d59f94323fe09b0 21912 admin optional 
readahead-fedora_1.5.6-5.1.diff.gz

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

iD8DBQFTtFX/20zMSyow1ykRAvMNAKCKfBAZHojzeVlIXzeY3ZVFiBy3CgCeJi/F
HeWQRgfTmwYu3Rg7etRtnEI=
=bIm8
-END PGP SIGNATURE End Message ---

Processed (with 1 errors): forcibly merging 750630 752991

[Debian Bug Tracking System]

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

> forcemerge 750630 752991
Bug #750630 [python-matplotlib] python-matplotlib: Default backend 'tkagg' 
broken
Bug #751385 [python-matplotlib] newer python interfers with matplotlib
Bug #751692 [python-matplotlib] cannot import matplotlib.backends.tkagg 
(missing _tkagg.so)
Bug #752057 [python-matplotlib] python-tk: importing matplotlib does not work 
anymore
Bug #753243 [python-matplotlib] mypaint: FTBFS: ImportError: cannot import name 
_tkagg
Unable to merge bugs because:
package of #752991 is 'python3-matplotlib' not 'python-matplotlib'
Failed to forcibly merge 750630: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x1c81650)', 
'requester', 'Julian Taylor ', 'request_addr', 
'cont...@bugs.debian.org', 'request_msgid', 
'<1404755631-3641-bts-jtay...@ubuntu.com>', 'request_subject', ...) called at 
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 552
eval {...} called at 
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 551
Debbugs::Control::Service::control_line('line', undef, 'clonebugs', 
'HASH(0x1bbf0b8)', 'limit', 'HASH(0x1bbeaa0)', 'common_control_options', 
'ARRAY(0x1bbeae8)', 'errors', ...) called at /usr/lib/debbugs/service line 474

> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#754125: libimager-perl: FTBFS on s390x

[Emilio Pozuelo Monfort]

Package: libimager-perl
Version: 0.98+dfsg-2
Severity: serious

Your package has failed to build on s390x:

https://buildd.debian.org/status/logs.php?pkg=libimager-perl&arch=s390x

Excerpt from the log:

Failed 215/251 subtests 

Test Summary Report
---
t/10png.t (Wstat: 11 Tests: 36 Failed: 0)
  Non-zero wait status: 11
  Parse errors: Bad plan.  You planned 251 tests but ran 36.
Files=2, Tests=37,  1 wallclock secs ( 0.02 usr  0.00 sys +  0.16 cusr  0.02 
csys =  0.20 CPU)
Result: FAIL
make[2]: *** [test_dynamic] Error 255

Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: reassign 752171 to src:pcp, forcibly merging 752171 753209

[Debian Bug Tracking System]

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

> reassign 752171 src:pcp pcp/3.9.4
Bug #752171 [pcp] pcp: Build depends on autoconf
Bug reassigned from package 'pcp' to 'src:pcp'.
No longer marked as found in versions pcp/3.9.4.
Ignoring request to alter fixed versions of bug #752171 to the same values 
previously set
Bug #752171 [src:pcp] pcp: Build depends on autoconf
Marked as found in versions pcp/3.9.4.
> forcemerge 752171 753209
Bug #752171 [src:pcp] pcp: Build depends on autoconf
Bug #752171 [src:pcp] pcp: Build depends on autoconf
Marked as found in versions pcp/3.9.6.
Added tag(s) sid and jessie.
Bug #753209 [src:pcp] pcp: FTBFS: make: autoconf: Command not found
Marked as found in versions pcp/3.9.4.
Added tag(s) patch.
Merged 752171 753209
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#663388: marked as done (gnustep-back-common: unowned files after purge (policy 6.8, 10.8) violating FHS (policy 9.1) too)

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 17:48:37 +
with message-id 
and subject line Bug#663388: fixed in gnustep-back 0.24.0-2
has caused the Debian Bug report #663388,
regarding gnustep-back-common: unowned files after purge (policy 6.8, 10.8) 
violating FHS (policy 9.1) too
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.)


-- 
663388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnustep-back-common
Version: 0.20.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):

http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

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

0m32.0s ERROR: FAIL: Package purging left files on system:
  /root/GNUstep  not owned
  /root/GNUstep/Library  not owned
  /var/lib/GNUstep   not owned
  /var/lib/GNUstep/Fonts not owned
  /var/log/gnustep-back-common.log   not owned


As putting files into /root is also a violation of
http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2
I'm setting the severity to serious.


cheers,

Andreas


gnustep-back-common_0.20.1-2.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: gnustep-back
Source-Version: 0.24.0-2

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

Debian distribution maintenance software
pp.
Yavor Doganov  (supplier of updated gnustep-back 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: SHA1

Format: 1.8
Date: Mon, 07 Jul 2014 16:00:20 +0300
Source: gnustep-back
Binary: gnustep-back0.24 gnustep-back0.24-art gnustep-back0.24-cairo 
gnustep-back-common gnustep-back-dbg
Architecture: source all amd64
Version: 0.24.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Yavor Doganov 
Description:
 gnustep-back-common - GNUstep GUI Backend - common files
 gnustep-back-dbg - GNUstep GUI Backend - debugging symbols
 gnustep-back0.24 - GNUstep GUI Backend
 gnustep-back0.24-art - GNUstep GUI Backend (art)
 gnustep-back0.24-cairo - GNUstep GUI Backend (cairo)
Closes: 663388
Changes:
 gnustep-back (0.24.0-2) unstable; urgency=medium
 .
   * Upload to unstable; should finally fix the piuparts issue once
 mknfonts.tool is binNMUed (Closes: #663388).
   * debian/compat: Bump to 9 to get .build-id debugging symbols.
   * debian/control.m4 (Build-Depends): Require debhlper >= 9.
 (Description): Mention that the art backend is deprecated.
 (Suggests): Remove fonts-freefont-ttf as -common depends on it.
   * debian/control: Regenerate.
   * debian/rules (confflags): Define conditionally and pass --host to
 configure only if cross-compiling.
Checksums-Sha1:
 925ce80db8d7179b0ebb3c49010c44acd2d3f3fd 2152 gnustep-back_0.24.0-2.dsc
 f7f7ba9930e0b51712659f46c18c641b99a0d635 18260 
gnustep-back_0.24.0-2.debian.tar.xz
 0fc078a293b51fd1df60c58632f84c84520a1da7 79122 
gnustep-back0.24_0.24.0-2_all.deb
 b5a048d1b0773c4bad854ef9903556ad25f764f6 281308 
gnustep-back0.24-art_0.24.0-2_amd64.deb
 595d1143e91423e1cf68685653bbda051317b1a0 242020 
gnustep-back0.24-cairo_0.24.0-2_amd64.deb
 e0fbc87312b32eae52795b227eb33d3ea029d20d 102160 
gnustep-back-common_0.24.0-2_amd64.deb
 20432267f71e39d5802392d9dcfcb7c871d2d42d 1031036 
gnustep-back-dbg_0.24.0-2_amd64.deb
Checksums-Sha256:
 7ea7501966ee82991b2843dc8d68a5f0b565f6e9796ce1a5ebacb6cc04db483c 2152 
gnustep-back_0.24.0-2.dsc
 c370d9ca9911c6b3fa176132a85944cf93ab6b719ce66da465589e19333c 18260 
gnustep-back_0.24.0-2.debian.tar.xz
 7450c1538a47cc7e29a26fcbe07133e8841b5dfebbcfd3a550afc84826190c40 79122 
gnustep-back0.24_0.24.0-2_all.deb
 f1c1d2f9543376b658d2818811e5dcbfe5cf9c50997b0e224a148e477edb353a 281308 
gnustep-back0.24-art_0.24.0-2_amd64.deb
 81b19e77d54abd8cc1e4743ec4c730adb958732671e230eae63c99e8e0504f36 242020 
gnustep-back0.24-cairo_0.24.0-2_

Bug#750623: marked as done (librime-dev: not installable on sid)

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 16:00:15 +
with message-id 
and subject line Bug#750623: fixed in librime 1.1+dfsg-1
has caused the Debian Bug report #750623,
regarding librime-dev: not installable on sid
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.)


-- 
750623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librime-dev
Version: 0.9.9-1
Severity: grave
User: trei...@debian.org
Usertags: edos-outdated

Hi,

librime-dev can no longer be installed in sid since it depends on
librime0 < 0.9.9-1+1~. However, the version of librim0 in sid is
0.9.9-1+b1.

Since librime-dev is architecture=all it needs a sourceful upload.

-Ralf.
--- End Message ---
--- Begin Message ---
Source: librime
Source-Version: 1.1+dfsg-1

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

Debian distribution maintenance software
pp.
Osamu Aoki  (supplier of updated librime 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: SHA1

Format: 1.8
Date: Sun, 29 Jun 2014 21:54:11 +0900
Source: librime
Binary: librime1 librime-bin librime1-dev librime1-dbg
Architecture: source amd64 all
Version: 1.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: IME Packaging Team 
Changed-By: Osamu Aoki 
Description:
 librime-bin - Rime Input Method Engine - utilities
 librime1   - Rime Input Method Engine - core library
 librime1-dbg - Rime Input Method Engine, the core library - debugging symbols
 librime1-dev - Rime Input Method Engine, the core library - development files
Closes: 746152 750623
Changes:
 librime (1.1+dfsg-1) unstable; urgency=medium
 .
   [ Guo Yixuan (郭溢譞) ]
   * New upstream release. (Closes: #746152)
   * librime1-dev: conflicts and replaces librime-dev, for
 renaming.
   * librime1-dev: dropped max version dependency on librime1.
 (Closes: #750623)
   * Bumped standard version to 3.9.5, no changes needed.
 .
   [ Osamu Aoki (青木 修) ]
   * Removed binary blobs in thirdparty/{bin,src/opencc-windows}/ .
   * Updated copyright file.
   * Re-add max version dependency using Upstream-Version.
Checksums-Sha1:
 188afc05c247be9428f391b3a3ee57528510fbdf 1754 librime_1.1+dfsg-1.dsc
 5d16fd4d57ac1987f41caf77a8e83e4b0281b220 2349569 librime_1.1+dfsg.orig.tar.gz
 dbab44ebc935ebfadfe94015abb1cd360f00f36b 5128 librime_1.1+dfsg-1.debian.tar.xz
 14cc6c388ab183ef32290e55099a6b80837ebe81 668700 librime1_1.1+dfsg-1_amd64.deb
 42ab8608e7e6035ec588ad592a54ec175ed9117d 22112 librime-bin_1.1+dfsg-1_amd64.deb
 6e8f9297fcb5c53d7cb2c57cc0d21658b519cca9 12514 librime1-dev_1.1+dfsg-1_all.deb
 326f49cd474e9ec527323fedea5ef669649c4de4 12296930 
librime1-dbg_1.1+dfsg-1_amd64.deb
Checksums-Sha256:
 aed01193145a1034ca07d9c0eca2eae904ea977ec13cbaa0b3b57eb3a56c1b62 1754 
librime_1.1+dfsg-1.dsc
 2df14ed85afcdfc8126130774e98d4f4f6f3b8d14370a86439411d7215972bdc 2349569 
librime_1.1+dfsg.orig.tar.gz
 84d2c46ee12f990f136665328085f8a184a29febaeca320ac969dbdc904fd0d0 5128 
librime_1.1+dfsg-1.debian.tar.xz
 2de8e2446a6676a314fcf720d10efd5b2a5a7a1057496cfbe36c3efb5d5cda5b 668700 
librime1_1.1+dfsg-1_amd64.deb
 212afd8da55065fc9c9ae7327cdd8328473bd58417cf02a838e0cf9c94f1789d 22112 
librime-bin_1.1+dfsg-1_amd64.deb
 ed7dd187441ceb858a01ea57d4996b376ba042191b893cdff17918ccd040c5a7 12514 
librime1-dev_1.1+dfsg-1_all.deb
 7b4f8681a155b00e68d1a0188109c8e57c28452eea26e8a05891852101ae87f2 12296930 
librime1-dbg_1.1+dfsg-1_amd64.deb
Files:
 e9d255de25d2e417a11e4966f611ebbb 668700 libs extra 
librime1_1.1+dfsg-1_amd64.deb
 d9276d6f6a881ca9c07a993c709b89cc 22112 utils extra 
librime-bin_1.1+dfsg-1_amd64.deb
 cd84e7009b8190f31a1f47e90b554d5e 12514 libdevel extra 
librime1-dev_1.1+dfsg-1_all.deb
 910322d8c2dc717dbcdd1a413a59ab90 12296930 debug extra 
librime1-dbg_1.1+dfsg-1_amd64.deb
 321a87115c6182316cb179ba619214dc 1754 libs extra librime_1.1+dfsg-1.dsc
 aee53c5910d4592f3d4514c9a18bdbdd 2349569 libs extra 
librime_1.1+dfsg.orig.tar.gz
 001b6f0496abdde81d4a6d3d25b243d2 5128 libs extra 
librime_1.1+dfsg-1.debian.tar.xz

-BEGIN PGP SIGN

Bug#738411: Re: libtext-kakasi-perl: FTBFS: Tests failures

[Emilio Pozuelo Monfort]

On 19/02/14 09:02, NOKUBI Takatsugu wrote:
> Package: libtext-kakasi-perl
> Tags: upstream, fixed-upstream
> Followup-For: Bug #738411
> 
> This probrem is come from libkakasi. It is already fixed in
> upstream CVS HEAD.
> 
> I'll release newer version of KAKASI in few week.

Any updates on this?

Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: [Pkg-sysvinit-devel] Bug#754063: initscripts: no longer depends on ifupdown

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo unreproducible
Bug #754063 [initscripts] initscripts: no longer depends on ifupdown
Added tag(s) unreproducible and moreinfo.
> severity -1 important
Bug #754063 [initscripts] initscripts: no longer depends on ifupdown
Severity set to 'important' from 'grave'

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#753184: marked as done (foremost: FTBFS: dpkg-source: error: expected ^--- in line 3 of diff `foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch')

[Raúl Benencia]

reopen 753184
thanks

On Mon, Jul 07, 2014 at 03:54:08PM +, Debian Bug Tracking System wrote:
> 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.

Guillem, the package has been uploaded to unstable by my usual sponsor. I
asked him to upload it a couple of day before you offer yourself to do
it. Nevertheless, I'll like to handle the upload to stable with you.

I will reopen the bug until the problem is fixed in stable.

Cheers,
Rul



signature.asc
Description: Digital signature

Processed: Re: Bug#753184: marked as done (foremost: FTBFS: dpkg-source: error: expected ^--- in line 3 of diff `foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch')

[Debian Bug Tracking System]

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

> reopen 753184
Bug #753184 {Done: Raúl Benencia } [src:foremost] foremost: 
FTBFS: dpkg-source: error: expected ^--- in line 3 of diff 
`foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions foremost/1.5.7-5.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#748694: marked as done (sys/sdt.h is architecture specific, and causing issues on unsupported architectures)

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 16:07:04 +
with message-id 
and subject line Bug#748694: fixed in systemtap 2.3-2.1
has caused the Debian Bug report #748694,
regarding sys/sdt.h is architecture specific, and causing issues on unsupported 
architectures
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.)


-- 
748694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemtap
Version: 2.3-2
Severity: serious
Tags: sid jessie

The sys/sdt.h header file is shipped in an architecture independent package, and
installed into /usr/include where it is found on the include path for every
architecture.  Seen that the mere inclusion of this header causes build failures
on some architectures. Reported in

  https://gcc.gnu.org/PR61231

and before in

  https://gcc.gnu.org/ml/gcc-patches/2012-12/msg01122.html

This just seems to be the visible fall-out, what about issues on architectures
not supported by systemtap?

In bug #423934 you mention that systemtap should be only available on
architectures where it is supported.  The systemtap-sdt-dev package violates
this assurance.  So the correct solution for this seems to be an architecture
dependent systemtap-sdt-dev package shipping the header file in
/usr/include/
--- End Message ---
--- Begin Message ---
Source: systemtap
Source-Version: 2.3-2.1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated systemtap 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: SHA1

Format: 1.8
Date: Sat, 05 Jul 2014 17:08:01 +0200
Source: systemtap
Binary: systemtap systemtap-common systemtap-runtime systemtap-doc 
systemtap-server systemtap-client systemtap-sdt-dev
Architecture: source amd64 all
Version: 2.3-2.1
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf 
Changed-By: Matthias Klose 
Description:
 systemtap  - instrumentation system for Linux
 systemtap-client - instrumentation system for Linux (client for compile server)
 systemtap-common - instrumentation system for Linux (common component)
 systemtap-doc - documentation and examples for SystemTap
 systemtap-runtime - instrumentation system for Linux (runtime component)
 systemtap-sdt-dev - statically defined probes development files
 systemtap-server - instrumentation system for Linux (compile server)
Closes: 748694 749035
Changes:
 systemtap (2.3-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Make systemtap-sdt-dev architecture dependent again, build it on every
 architecture, move the sys/sdt.h to the multiarch include path, and don't
 ship the sdt headers on architectures where systemtap is not built.
 Closes: #748694.
 Doesn't need to be M-A: foreign. Closes: #749035.
Checksums-Sha1:
 8e340cb6425a34009ebc153ed499dafb6651d922 2114 systemtap_2.3-2.1.dsc
 72944488f7dac5f26a764d8c4344c5a5947f83ed 20076 systemtap_2.3-2.1.debian.tar.xz
 b21b0770d539eb5644893d20bcb17d96eae8763c 803204 systemtap_2.3-2.1_amd64.deb
 9edcc3399a3792f252461b6100763543d2bd8d99 394430 
systemtap-common_2.3-2.1_all.deb
 d070d7761712bc780f76a738d76ee8edad352643 109696 
systemtap-runtime_2.3-2.1_amd64.deb
 f928967b488b0c4f48801fcd9a04a549af761a69 1674916 systemtap-doc_2.3-2.1_all.deb
 52d4ff784a66ad905db5a2d6c618fe6b73bd5c98 116000 
systemtap-server_2.3-2.1_amd64.deb
 e889a0f2e9d71e3c926b4457f565d46b856555c4 17522 
systemtap-client_2.3-2.1_amd64.deb
 c2f4ebf858f96ab8125763dba09246d818a3fe64 24480 
systemtap-sdt-dev_2.3-2.1_amd64.deb
Checksums-Sha256:
 881eacb2c8b14ba76a604c2408dbfb447de9154413a8c8234c8627baed6781b8 2114 
systemtap_2.3-2.1.dsc
 0dbb4ea41c71627956a74e7a9813dc5a24a7dcc59f95912395a97aaf5af38e3a 20076 
systemtap_2.3-2.1.debian.tar.xz
 38347b81b530669410bcb859eb31ae210dd9d7f5b18e69067f5b0c2c7bfa0284 803204 
systemtap_2.3-2.1_amd64.deb
 f8223c6846c3184a6345256bb16799592f1ce919cfee90bc7a7dd0225383924e 394430 
systemtap-common_2.3-2.1_all.deb
 fdd4e76aab4dacf05dd5b6d1b71789ac81fdc5941

Bug#751228: marked as done (libffado: does not compile on mips)

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 17:05:40 +
with message-id 
and subject line Bug#751228: fixed in libffado 2.2.1-2
has caused the Debian Bug report #751228,
regarding libffado: does not compile on mips
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.)


-- 
751228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libffado
Version: 2.2.1-1
Severity: normal

I have a patch for this


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: mips (mips64)

Kernel: Linux 3.2.0-4-5kc-malta
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: libffado
Source-Version: 2.2.1-2

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated libffado package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Jul 2014 18:38:48 +0200
Source: libffado
Binary: libffado-dev libffado2 ffado-tools ffado-dbus-server ffado-mixer-qt4
Architecture: source all amd64
Version: 2.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Sebastian Ramacher 
Description:
 ffado-dbus-server - FFADO D-Bus server
 ffado-mixer-qt4 - FFADO D-Bus mixer applets (QT4)
 ffado-tools - FFADO debugging and firmware tools
 libffado-dev - FFADO API - development files
 libffado2  - FFADO API
Closes: 751228
Changes:
 libffado (2.2.1-2) unstable; urgency=medium
 .
   * Team upload.
   * debian/patches/cpuinfo-parsing.patch: Fix /proc/cpuinfo parsing. Thanks to
 Plamen Aleksandrov. (Closes: #751228)
Checksums-Sha1:
 d0d63d41e69b80006713d21abf340187a64b85d2 2583 libffado_2.2.1-2.dsc
 6c1997bffa89a71e40a80ef9690ff42832d67785 7800 libffado_2.2.1-2.debian.tar.xz
 8e3d83c349d46a5a60767dc21236c98be71df561 93046 ffado-mixer-qt4_2.2.1-2_all.deb
 fa877fb53a5f50be073bef91954f219a62d24c97 19758 libffado-dev_2.2.1-2_amd64.deb
 3c398fe01040390a7e14ff4db5d91f5f1d3b06fb 1328416 libffado2_2.2.1-2_amd64.deb
 cef888f1e3e4b8fff197c19d6672d569782edf8c 50620 ffado-tools_2.2.1-2_amd64.deb
 a4ab50182e07042c765f5c985f7354e8e22b2c58 61350 
ffado-dbus-server_2.2.1-2_amd64.deb
Checksums-Sha256:
 0fbb80e219568b91922935303145ed0f4c1fdcf735cbd04b08ffeeb1d6b972e4 2583 
libffado_2.2.1-2.dsc
 d278744dd7a6a011156fd668a5321e1105220df2f0bb0cac342a3093e83f0e44 7800 
libffado_2.2.1-2.debian.tar.xz
 b1ee8548c06c3550418a1b8a66261ae57b3afe4037eb1eb2838caed902f77ca6 93046 
ffado-mixer-qt4_2.2.1-2_all.deb
 143e599c773c54fec4c53f069a95b917f985f23f77fc2dcc1d1cef242f4321ff 19758 
libffado-dev_2.2.1-2_amd64.deb
 1af519cba18ab0139284bbe26eeada841ffb06b58bda1dd217e429a85b278bbf 1328416 
libffado2_2.2.1-2_amd64.deb
 0b0c208c0f89543495727a6d5617837ee1445eb9a0a208e6cf1a8b04b9fbaf5f 50620 
ffado-tools_2.2.1-2_amd64.deb
 08e4fb35c33037d323f543e43693a5bf76c54d900cccab9003e419771b6c 61350 
ffado-dbus-server_2.2.1-2_amd64.deb
Files:
 815527528fda182934d4fb011805f8f4 93046 sound optional 
ffado-mixer-qt4_2.2.1-2_all.deb
 eeb2054822990c99500826722b54953c 19758 libdevel optional 
libffado-dev_2.2.1-2_amd64.deb
 a2f706515b2c896790da24f59f209533 1328416 libs optional 
libffado2_2.2.1-2_amd64.deb
 a101c8970a7ef325a51f9ad8b969446a 50620 sound optional 
ffado-tools_2.2.1-2_amd64.deb
 8d0fde61c81c0beda3962033ec112edf 61350 sound optional 
ffado-dbus-server_2.2.1-2_amd64.deb
 1ed740e5cb2f6edf42f2b9e11fd26cde 2583 libs optional libffado_2.2.1-2.dsc
 5d708e1b83c021662bea43b25a8e64c1 7800 libs optional 
libffado_2.2.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJTus96AAoJEGny/FFupxmTjggP/A7n89ciNwmCW3X1U8EQhSKZ
IKp6sdNf+Xk1kjo1LMzs/4V6us6VRh5I/1gMA/JVeeK/CTPNEWGxX7hKt3WjR21N
LC3/Ojud4uyVzxOkUCFn8RWvmEAeDoUIh9t+jC8miYhbJgmNIxAiyu4JSWrhB9+Z
zcekEp64dhyoeOWJiePHh3vsBVYVwZlLu1H0n7OlwDaUX/sg+iFxA/jLe0mefuQB
iFa6Yx0CjAAUwTDiJ4CJHhNaK8K0ACglpc95fgTR6eFMf4

Bug#753985: [Pkg-gnupg-maint] Bug#753985: gpgv-udeb: fails to validate Release files (missing sha256 support)

[Thijs Kinkhorst]

Op maandag 7 juli 2014 11:36:49 schreef Didier 'OdyX' Raboud:
> >  b) Thankfully we don't need to consider the backup plan mentioned in
> >
> > a) since all we need is enabling sha256 support. Currently, Release
> > files include MD5+SHA1+SHA256. You'll find a tested patch attached.
> > (This means a whole installation using a netboot-gtk image.)
> 
> I can confirm that Cyril's patch fixes gpgv.exe usage within win32-
> loader.

Merci beaucoup a vous deux pour votre aide excellente dans ce cas! J'ai a 
l'heure téĺéchargé un nouveau version du gnupg.


Cordialement,
Thijs


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

Processed: building uwsgi against the default ruby

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #743994 [src:uwsgi] uwsgi: (Build-)Depends on obsolete version of Ruby (1.9)
Added tag(s) patch.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#743994: building uwsgi against the default ruby

[Antonio Terceiro]

Control: tag -1 + patch

Hello,

I have built uwsgi locally with the attached patch and tested the rack
plugin with a minimal application (following the instructions on
http://uwsgi-docs.readthedocs.org/en/latest/Ruby.html) and it seems to
just work.

Given that code that works with 1.9 generally works with 2.0+ (and with
2.1 which is the current version in jessie), I think these changes
should be good enough to get uwsgi back in jessie. However, pleae note
that I didn't test uwsgi-plugin-rbthreads and uwsgi-plugin-fiber as I
couldn't figure out how to do it within the time I had.

Regarding the attached patch: note that I am dropping the '1.9.1' prefix
from rack plugin package name, but you could as well drop the '-ruby'
suffix: just uwsgi-plugin-rack should be meaningfull enough and
consistent with the other Ruby-related plugins that don't have an
explicit mention to ruby in their names.

-- 
Antonio Terceiro 
diff -Nru uwsgi-2.0.3/debian/changelog uwsgi-2.0.3/debian/changelog
--- uwsgi-2.0.3/debian/changelog	2014-04-07 10:09:34.0 -0300
+++ uwsgi-2.0.3/debian/changelog	2014-07-07 14:39:21.0 -0300
@@ -1,3 +1,10 @@
+uwsgi (2.0.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * 
+
+ -- Antonio Terceiro   Mon, 07 Jul 2014 14:39:19 -0300
+
 uwsgi (2.0.3-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru uwsgi-2.0.3/debian/control uwsgi-2.0.3/debian/control
--- uwsgi-2.0.3/debian/control	2014-04-07 10:07:14.0 -0300
+++ uwsgi-2.0.3/debian/control	2014-07-07 14:43:53.0 -0300
@@ -47,8 +47,8 @@
  python-greenlet-dev [amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390x sparc],
  python3-all-dev,
  openjdk-7-jdk [amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390x sparc],
- ruby1.9.1,
- ruby1.9.1-dev,
+ ruby,
+ ruby-dev,
  uuid-dev
 Standards-Version: 3.9.5
 Homepage: http://projects.unbit.it/uwsgi/
@@ -253,7 +253,7 @@
 - PSGI, Rack, WSGI, etc.
   * coroutines
 - Coro::AnyEvent
-- Fiber (Ruby 1.9.1)
+- Fiber (Ruby)
 - greenlet (Python 2)
 
 Package: uwsgi-infrastructure-plugins
@@ -299,7 +299,7 @@
  uwsgi-plugin-psgi (= ${binary:Version}),
  uwsgi-plugin-python (= ${binary:Version}),
  uwsgi-plugin-python3 (= ${binary:Version}),
- uwsgi-plugin-rack-ruby1.9.1 (= ${binary:Version}),
+ uwsgi-plugin-rack-ruby (= ${binary:Version}),
  uwsgi-plugin-v8 (= ${binary:Version}) [amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mipsel]
 Description: plugins for integration of uWSGI and application
  uWSGI presents a complete stack for networked/clustered web applications,
@@ -316,7 +316,7 @@
   * PHP
   * Perl PSGI
   * Python WSGI (Python 2 and 3)
-  * Rack (Ruby 1.9.1)
+  * Rack (Ruby)
   * V8
 
 Package: uwsgi-plugin-alarm-curl
@@ -370,7 +370,7 @@
 Package: uwsgi-plugin-rbthreads
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, uwsgi-core (= ${binary:Version}),
- uwsgi-plugin-rack-ruby1.9.1 (= ${binary:Version})
+ uwsgi-plugin-rack-ruby (= ${binary:Version})
 Description: Ruby native threads plugin for uWSGI
  uWSGI presents a complete stack for networked/clustered web applications,
  implementing message/object passing, caching, RPC and process management.
@@ -378,12 +378,12 @@
  used in order to add compatibility with tons of different technology on top of
  the same core.
  .
- This package provides Ruby 1.9 native threads plugin for uWSGI.
+ This package provides Ruby native threads plugin for uWSGI.
 
 Package: uwsgi-plugin-fiber
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, uwsgi-core (= ${binary:Version}),
- uwsgi-plugin-rack-ruby1.9.1 (= ${binary:Version})
+ uwsgi-plugin-rack-ruby (= ${binary:Version})
 Description: Fiber plugin for uWSGI
  uWSGI presents a complete stack for networked/clustered web applications,
  implementing message/object passing, caching, RPC and process management.
@@ -391,8 +391,7 @@
  used in order to add compatibility with tons of different technology on top of
  the same core.
  .
- This package provides Fiber plugin for uWSGI
- with Ruby 1.9.1.
+ This package provides Fiber plugin for uWSGI with Ruby.
  .
  Fibers are a form of coroutine, useful for implementing cooperative
  multitasking.
@@ -544,18 +543,17 @@
  This package provides Python 3 WSGI plugin for uWSGI
  (linked with Python 3 runtime).
 
-Package: uwsgi-plugin-rack-ruby1.9.1
+Package: uwsgi-plugin-rack-ruby
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, uwsgi-core (= ${binary:Version})
-Description: Rack plugin for uWSGI (Ruby 1.9.1)
+Description: Rack plugin for uWSGI (Ruby)
  uWSGI presents a complete stack for networked/clustered web applications,
  implementing message/object passing, caching, RPC and process management.
  It is designed to be fully modular. This means that different plugins can be
  used in order to add compatibility with tons of different technology on top of
  the same core.
  .
- This package provides Rack plugin

Bug#753684: ifupdown: Dead symlinks in /etc/network/if-pre-up.d block networking

[Andrew Shadura]

Hello,

On Fri, 04 Jul 2014 12:37:43 +0200
Matthias Urlichs  wrote:

> Package: ifupdown
> Version: 0.7.48.1
> Severity: serious
> Justification: Policy 10.7 (?)

> # ln -s /not/an/existing/file /etc/network/if-pre-up.d/buggy
> # ifup eth0
> [ one error message and no networking ]

> … which is fun if you remote-admin something.

Um. Don't do that then. Or get it fixed in run-parts. Commands for
pre-up *must* succeed, otherwise the precondition for getting an
interface up wouldn't be met. So it doesn't precisely sound like a bug
in ifupdown.

Meanwhile, I don't see how this violates Policy 10.7.

-- 
Cheers,
  Andrew


signature.asc
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

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

> tag 729590 + pending
Bug #729590 [python-matplotlib] nitime: FTBFS: RuntimeError: maximum recursion 
depth exceeded
Added tag(s) pending.
> tag 750630 + pending
Bug #750630 [python-matplotlib] python-matplotlib: Default backend 'tkagg' 
broken
Bug #751385 [python-matplotlib] newer python interfers with matplotlib
Bug #751692 [python-matplotlib] cannot import matplotlib.backends.tkagg 
(missing _tkagg.so)
Bug #752057 [python-matplotlib] python-tk: importing matplotlib does not work 
anymore
Bug #752991 [python-matplotlib] python3-matplotlib: pylab fails to be imported
Bug #753243 [python-matplotlib] mypaint: FTBFS: ImportError: cannot import name 
_tkagg
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> tag 752548 + pending
Bug #752548 [python-matplotlib] python-matplotlib: Segmentation fault in show()
Added tag(s) pending.
> tag 714948 + pending
Bug #714948 [python-matplotlib-dbg] python-matplotlib-dbg: Importing 
matplotlib.pyplot fails (for dbg version)
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
714948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714948
729590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729590
750630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750630
751385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751385
751692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751692
752057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752057
752548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752548
752991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752991
753243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: your mail

[Debian Bug Tracking System]

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

> tag 737438 + pending
Bug #737438 [src:matplotlib] [src:matplotlib] Sourceless file (minified) 
(jquery)
Added tag(s) pending.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#754122: cutter-testing-framework: Depends: gstreamer0.10-plugins-cutter (= 1.2.4-1) but it is not going to be installed

[Sebastian Ramacher]

Package: cutter-testing-framework
Version: 1.2.4-1
Severity: grave
Justification: renders package unusable

cutter-testing-framework can no longer be installed:

apt install cutter-testing-framework
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 cutter-testing-framework : Depends: gstreamer0.10-plugins-cutter (= 1.2.4-1) 
but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Processed: severity of 754105 is minor

[Debian Bug Tracking System]

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

> severity 754105 minor
Bug #754105 [virt-manager] virt-manager does not support waking up domains in 
state pmsuspended
Severity set to 'minor' from 'grave'
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#754119: libmagic1: arch-specific symlink in /usr/share

[Jakub Wilk]

Package: file
Version: 1:5.19-1+exp1
Severity: serious
Justification: Policy §9.1.1

FHS says that the /usr/share/ hierarchy “is intended to be shareable 
among all architecture platforms of a given OS”. But my /usr/share/file/ 
looks like this:


lrwxrwxrwx 1 root root 38 Jul  7 18:41 magic.mgc -> 
/usr/lib/i386-linux-gnu/file/magic.mgc

This is not sharable with anything except i386.


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

Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libmagic1 depends on:
ii  libc6  2.19-5
ii  multiarch-support  2.19-5
ii  zlib1g 1:1.2.8.dfsg-1

Versions of packages libmagic1 suggests:
ii  file  1:5.19-1+exp1

Versions of packages file depends on:
ii  libc6   2.19-5
ii  zlib1g  1:1.2.8.dfsg-1

--
Jakub Wilk


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#754059: [systemd-sysv] Conflicts with sysvinit-core

[Michael Biebl]

Am 07.07.2014 18:50, schrieb Filipus Klutiero:
> I suppose there's a reason why a conflict was declared. I didn't mean
> declaring a conflict with sysvinit-core is a bug *per se*. The bug is to
> conflict with a package of required priority, namely sysvinit-core. If
> it's necessary to conflict with a required package, then something's
> very wrong with the package.

Nope, it's not.
See also other init systems, like the upstart package, which declare the
same Conflicts/Replaces.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: your mail

[Debian Bug Tracking System]

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

> tags 753483 + pending
Bug #753483 [gnustep-dl2] libgnustep-dl2-0d: Programs using EOControl die with 
NSInvalidArgumentException, reason: Can not determine type information for 
+[GDL2CDNSObject (null)]
Bug #705602 [gnustep-dl2] gnustep-dl2: DBModeler dies with 
NSInvalidArgumentException
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#754059: [systemd-sysv] Conflicts with sysvinit-core

[Filipus Klutiero]

reopen 754059
thanks

On 2014-07-07 07:09, Michael Biebl wrote:

Am 07.07.2014 08:56, schrieb Filipus Klutiero:

Package: systemd-sysv
Version: 204-14
Severity: serious

systemd-sysv conflicts with sysvinit-core, which is required.

Correct, systemd-sysv has a Conflicts/Replaces against sysvinit-core so
it is actually possible to switch between different init systems.

This is not a bug but intentional and necessary. Thus closing the bug
report.


Michael




I suppose there's a reason why a conflict was declared. I didn't mean declaring 
a conflict with sysvinit-core is a bug *per se*. The bug is to conflict with a 
package of required priority, namely sysvinit-core. If it's necessary to 
conflict with a required package, then something's very wrong with the package.

--
Filipus Klutiero
http://www.philippecloutier.com


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#752075: daemontools-run: Add systemd support

[Michael Biebl]

Am 07.07.2014 16:36, schrieb Gerrit Pape:
> Hi Michael, thanks for your help.
> 
> On Mon, Jul 07, 2014 at 02:59:05PM +0200, Michael Biebl wrote:
>> [CCing the bug report]
>>
>> Am 07.07.2014 14:39, schrieb Jonathan de Boyne Pollard:
>>> I did systemd units for this ages ago.  It's better to do this as two
>>> units: a "path" unit that watches the service directory and a
>>> "service" unit that is started when the service directory is found to
>>> be non-empty.
> 
> Hi Jonathan, good to see you're still around.  Thanks for your
> contribution.
> 
>>   And you don't need svscanboot at all, since systemd's
>>> journal logs the output of svscan and does it better than
>>> readproctitle does.
>>
>> Ansgar suggested using the journal for that as well [1], which sounds
>> reasonable.
> 
> Is this journal an in-memory-log, or does it write to disk?

Depends on the configuration. The default in jessie will be to not log
to disk. We might change that in the future though.

>>   And don't forget to run "systemctl
>>> preset svscan.path" as part of your package installation process.
>>> (I've heard rumours that "update-rc.d svscan.path defaults" runs
>>> "systemctl preset svscan.path" in some testing versions somewhere; but
>>> I've not witnessed this myself.)
>>
>> As Ansgar already mentioned, probably the best way to handle that in
>> Debian is to use the dh-systemd helper.
>> Unfortuantely the daemontools package doesn't use debhelper, which
>> complicates that a bit it.
> 
> To me, that's not unfortunate. To me, debhelper complicates things.  It
> can't be that difficult to enable a service, configure it to be enabled
> by default, and vice-versa.

The problem here is, that you can't rely on systemd being installed, as
it is not mandatory. Therefore we re-implemented the relevant bits in
the init-system-helpers package.

> To see what snippets debhelper puts into maintainer scripts, can you
> point me to an example package in Debian that installs simple systemd
> services, Michael?  I search for files containing systemd in the debian
> package directory, but with no applicable result.

There are many packages which use dh-systemd (basically all packages
depending on init-system-helpers. You can have a look at those.

Also, Ansgar already more or less answered that question at [1]:

> As far as I know, this still misses the maintainer script logic that is
> needed to start the service on installation and stop it again when the
> package is removed.
> 
> There is a debhelper addon to add them, but the daemontools doesn't use
> debhelper so they have to be added manually. The snippets can be found
> in autoscripts/* in the init-system-helpers source package (it also
> needs a runtime dependency on init-system-helpers).

You can copy the relevant bits to your maintainer scripts, but it has
the unfortunate effect that updates of dh-systemd will not automatically
be applied to your package and you'll have to do that manually.




[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752075#60
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#751969: gir1.2-goocanvas-2.0: Introspection file installed in the wrong directory

[Alberto Garcia]

Here's the debdiff, there's still room for improvement in the package
but this fixes the really important problems.

Berto
diff -Nru goocanvas-2.0.2/debian/changelog goocanvas-2.0.2/debian/changelog
--- goocanvas-2.0.2/debian/changelog2014-02-28 17:04:57.0 +0200
+++ goocanvas-2.0.2/debian/changelog2014-07-07 17:53:25.0 +0300
@@ -1,3 +1,22 @@
+goocanvas (2.0.2-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/fix-g-i-path.patch:
+- Install .typelib files in its proper directory (Closes: #751969).
+  * debian/gir1.2-goocanvas-2.0.install:
+- Update path for .typelib files.
+  * debian/libgoocanvas-2.0-dev.install
+- Install .gir file.
+  * debian/rules:
+- Build with autoreconf.
+- Run dh_girepository after dh_shlibdeps.
+- Enable parallel builds.
+  * debian/control:
+- Add build dependencies on dh-autoreconf and gobject-introspection.
+- Delete trailing whitespaces from the description.
+
+ -- Alberto Garcia   Mon, 07 Jul 2014 17:31:33 +0300
+
 goocanvas (2.0.2-1) experimental; urgency=medium
 
   * New upstream release (Closes: #588177)
diff -Nru goocanvas-2.0.2/debian/control goocanvas-2.0.2/debian/control
--- goocanvas-2.0.2/debian/control  2014-02-28 17:04:15.0 +0200
+++ goocanvas-2.0.2/debian/control  2014-07-07 17:30:24.0 +0300
@@ -3,9 +3,9 @@
 Maintainer: Debian Ruby Extras Maintainers 

 Uploaders: Jose Carlos Garcia Sogo ,
Hideki Yamane 
-Build-Depends: debhelper (>= 9), libglib2.0-dev (>= 2.28), 
+Build-Depends: debhelper (>= 9), libglib2.0-dev (>= 2.28), dh-autoreconf,
  autotools-dev, gtk-doc-tools, libgtk-3-dev, libcairo2-dev (>= 1.10),
- libgirepository1.0-dev
+ libgirepository1.0-dev, gobject-introspection
 Standards-Version: 3.9.5
 Section: libs
 Vcs-Git: git://anonscm.debian.org/collabmaint/goocanvas.git
@@ -18,11 +18,11 @@
 Multi-Arch: same
 Depends: libgoocanvas-2.0-9 (= ${binary:Version}), ${misc:Depends}, 
libgtk-3-dev
 Description: development libraries, include files and documentation for 
goocanvas
- GooCanvas is a canvas widget for GTK+ that uses the cairo 2D library for 
- drawing. It has a model/view split, and uses interfaces for canvas items and 
+ GooCanvas is a canvas widget for GTK+ that uses the cairo 2D library for
+ drawing. It has a model/view split, and uses interfaces for canvas items and
  views, so you can easily turn any application object into canvas items.
  .
- This package contains the development libraries, include files 
+ This package contains the development libraries, include files
  and documentation
 
 Package: libgoocanvas-2.0-common
@@ -30,8 +30,8 @@
 Multi-Arch: foreign
 Depends: ${misc:Depends}
 Description: translations for goocanvas
- GooCanvas is a canvas widget for GTK+ that uses the cairo 2D library for 
- drawing. It has a model/view split, and uses interfaces for canvas items and 
+ GooCanvas is a canvas widget for GTK+ that uses the cairo 2D library for
+ drawing. It has a model/view split, and uses interfaces for canvas items and
  views, so you can easily turn any application object into canvas items.
  .
  This package contains the translations
@@ -42,8 +42,8 @@
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}, libgoocanvas-2.0-common (= 
${source:Version})
 Description: canvas widget for GTK+ that uses the cairo 2D library
- GooCanvas is a canvas widget for GTK+ that uses the cairo 2D library for 
- drawing. It has a model/view split, and uses interfaces for canvas items and 
+ GooCanvas is a canvas widget for GTK+ that uses the cairo 2D library for
+ drawing. It has a model/view split, and uses interfaces for canvas items and
  views, so you can easily turn any application object into canvas items.
  .
  This package contains the shared library
@@ -63,4 +63,3 @@
  .
  It can be used by packages using the GIRepository format to generate
  dynamic bindings.
-
diff -Nru goocanvas-2.0.2/debian/gir1.2-goocanvas-2.0.install 
goocanvas-2.0.2/debian/gir1.2-goocanvas-2.0.install
--- goocanvas-2.0.2/debian/gir1.2-goocanvas-2.0.install 2014-02-02 
05:36:21.0 +0200
+++ goocanvas-2.0.2/debian/gir1.2-goocanvas-2.0.install 2014-07-07 
17:34:01.0 +0300
@@ -1 +1 @@
-usr/lib/*/girepository-*/GooCanvas-*.typelib
+usr/lib/girepository-*/GooCanvas-*.typelib
diff -Nru goocanvas-2.0.2/debian/libgoocanvas-2.0-dev.install 
goocanvas-2.0.2/debian/libgoocanvas-2.0-dev.install
--- goocanvas-2.0.2/debian/libgoocanvas-2.0-dev.install 2014-02-02 
05:36:26.0 +0200
+++ goocanvas-2.0.2/debian/libgoocanvas-2.0-dev.install 2014-07-07 
17:52:57.0 +0300
@@ -2,3 +2,4 @@
 usr/lib/*/libgoocanvas-2.0.so
 usr/lib/*/pkgconfig
 usr/include
+usr/share/gir-1.0
diff -Nru goocanvas-2.0.2/debian/patches/fix-g-i-path.patch 
goocanvas-2.0.2/debian/patches/fix-g-i-path.patch
--- goocanvas-2.0.2/debian/patches/fix-g-i-path.patch   1970-01-01 
02:00:00.0 +0200
+++ goocanvas-2.0.2/debian/patches/fix-g-i-path.patch   

Bug#753184: marked as done (foremost: FTBFS: dpkg-source: error: expected ^--- in line 3 of diff `foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch')

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 15:50:52 +
with message-id 
and subject line Bug#753184: fixed in foremost 1.5.7-5
has caused the Debian Bug report #753184,
regarding foremost: FTBFS: dpkg-source: error: expected ^--- in line 3 of diff 
`foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch'
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.)


-- 
753184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: foremost
Version: 1.5.7-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140628 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):
> Unpack source
> ─
> 
> gpgv: keyblock resource `/sbuild-nonexistent/.gnupg/trustedkeys.gpg': file 
> open error
> gpgv: Signature made Fri Jul 20 14:05:33 2012 UTC using RSA key ID EED3BC0D
> gpgv: Can't check signature: public key not found
> dpkg-source: warning: failed to verify signature on ./foremost_1.5.7-4.dsc
> dpkg-source: info: extracting foremost in foremost-1.5.7
> dpkg-source: info: unpacking foremost_1.5.7.orig.tar.gz
> dpkg-source: info: unpacking foremost_1.5.7-4.debian.tar.gz
> dpkg-source: info: applying fix-config-file-path.patch
> dpkg-source: error: expected ^--- in line 3 of diff 
> `foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch'
> dpkg-source: info: applying fix-lintian-hardening-warnings.patch
> dpkg-source: info: fuzz is not allowed when applying patches
> dpkg-source: info: if patch 'fix-lintian-hardening-warnings.patch' is 
> correctly applied by quilt, use 'quilt refresh' to update it
> FAILED [dpkg-source died]

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/28/foremost_1.5.7-4_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: foremost
Source-Version: 1.5.7-5

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

Debian distribution maintenance software
pp.
Raúl Benencia  (supplier of updated foremost 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, 03 Jul 2014 14:03:02 -0300
Source: foremost
Binary: foremost
Architecture: source amd64
Version: 1.5.7-5
Distribution: unstable
Urgency: medium
Maintainer: Raúl Benencia 
Changed-By: Raúl Benencia 
Description:
 foremost   - forensic program to recover lost files
Closes: 753184
Changes:
 foremost (1.5.7-5) unstable; urgency=medium
 .
   * Update maintainer email address.
   * Include new VCS control fields.
   * Fix FTBFS caused by dpkg update. Thanks Juhani Numminen. (Closes: #753184)
   * Bump standards version to 3.9.5, no changes.
Checksums-Sha1:
 7283381dc58ded419ddf1faeae2f9cac673cdf98 1799 foremost_1.5.7-5.dsc
 2bbd857a9dc39dcbbb4858655c0bca94b3107c05 6808 foremost_1.5.7-5.debian.tar.xz
 a3baa1b1ae63b2f8a7c8f12f7e3c258250313340 41088 foremost_1.5.7-5_amd64.deb
Checksums-Sha256:
 a0ee7d957057dfec63ca113e5e847eeeb68750f4f214c8febc629a1f2fe70e59 1799 
foremost_1.5.7-5.dsc
 c0fb1829253645aff25b721b48da7f985644c2c395bf2a49d18bdbf98b798ebb 6808 
foremost_1.5.7-5.debian.tar.xz
 21c5c8dc83f6c7f6c19a91784807a28b82e5498c399d3ef39db70224ac6ea605 41088 
foremost_1.5.7-5_amd64.deb
Files:
 adaae6d8932d889a0b2ae95cdcd9ec6d 41088 admin optional 
foremost_1.5.7-5_amd64.deb
 7def851ca19e1fd2753368f13d590174 1799 admin optional foremost_1.5.7-5.dsc
 d4dc376bbd0eff1f41e3ad0f767ea1b8 6808 admin optional 
foremost_1.5.7-5.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJTur+XAAoJEKtkX0BihqfQeqQQAIlJlcE249U9TwB6Fo9lQFBE
tBFRqNm5/qbe0wfl2qj

Processed: severity of 749553 is serious

[Debian Bug Tracking System]

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

> severity 749553 serious
Bug #749553 [src:cenon.app] cenon.app: FTBFS with gnustep-gui/0.24: 
TileScrollView.m:94:9: error: pointer value used where a floating point value 
was expected
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#754105: virt-manager does not support waking up domains in state pmsuspended

[Johan Kröckel]

Package: virt-manager
Version: 0.9.5-1
Severity: grave
Justification: causes non-serious data loss

When the vm goes into pmsuspended state the only way to wake it up is running
# virsh  dompmwakeup domain

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

Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages virt-manager depends on:
ii  gconf2 3.2.6-2
ii  librsvg2-common2.40.2-1
ii  python 2.7.6-2
ii  python-dbus1.2.0-2+b3
ii  python-glade2  2.24.0-3+b1
ii  python-gnome2  2.28.1+dfsg-1
ii  python-gtk-vnc 0.5.3-1
ii  python-gtk22.24.0-3+b1
ii  python-ipy 1:0.81-1
ii  python-libvirt 1.2.1-2
ii  python-support 1.0.15
ii  python-urlgrabber  3.9.1-4
ii  python-vte 1:0.28.2-5
ii  virtinst   0.600.4-3

Versions of packages virt-manager recommends:
ii  gnome-icon-theme 3.12.0-1
ii  libvirt-bin  1.2.4-3
ii  python-spice-client-gtk  0.23-1

Versions of packages virt-manager suggests:
ii  gnome-keyring3.8.2-2+b1
pn  python-gnomekeyring  
pn  python-guestfs   
pn  ssh-askpass  
pn  virt-viewer  

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#752075: daemontools-run: Add systemd support

[Gerrit Pape]

Hi Michael, thanks for your help.

On Mon, Jul 07, 2014 at 02:59:05PM +0200, Michael Biebl wrote:
> [CCing the bug report]
> 
> Am 07.07.2014 14:39, schrieb Jonathan de Boyne Pollard:
> > I did systemd units for this ages ago.  It's better to do this as two
> > units: a "path" unit that watches the service directory and a
> > "service" unit that is started when the service directory is found to
> > be non-empty.

Hi Jonathan, good to see you're still around.  Thanks for your
contribution.

>   And you don't need svscanboot at all, since systemd's
> > journal logs the output of svscan and does it better than
> > readproctitle does.
> 
> Ansgar suggested using the journal for that as well [1], which sounds
> reasonable.

Is this journal an in-memory-log, or does it write to disk?

>   And don't forget to run "systemctl
> > preset svscan.path" as part of your package installation process.
> > (I've heard rumours that "update-rc.d svscan.path defaults" runs
> > "systemctl preset svscan.path" in some testing versions somewhere; but
> > I've not witnessed this myself.)
> 
> As Ansgar already mentioned, probably the best way to handle that in
> Debian is to use the dh-systemd helper.
> Unfortuantely the daemontools package doesn't use debhelper, which
> complicates that a bit it.

To me, that's not unfortunate. To me, debhelper complicates things.  It
can't be that difficult to enable a service, configure it to be enabled
by default, and vice-versa.

To see what snippets debhelper puts into maintainer scripts, can you
point me to an example package in Debian that installs simple systemd
services, Michael?  I search for files containing systemd in the debian
package directory, but with no applicable result.

Regards, Gerrit.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#753184: foremost: FTBFS: dpkg-source: error: expected ^--- in line 3 of diff `foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch'

[Raúl Benencia]

Hello again,

On Sun, Jul 06, 2014 at 10:25:09PM +0200, Guillem Jover wrote:
> The changes look good. There's a missing mention of the
> Standards-Version bump though, and some of the changelog items could
> do with some slight verbosity. :)

I've updated the changelog with your suggestions. The .dsc URL is the
same. What do you think of it now?

Thanks in advance, Guillem. =)

Cheers, 
--
Raúl Benencia


signature.asc
Description: Digital signature

Bug#738460: macchanger: Random mac feature fails in all of the random mac assigning options

[Theodore Ts'o]

On Mon, Jul 07, 2014 at 08:25:25AM +0200, David Paleino wrote:
> On Sun, 6 Jul 2014 21:23:25 -0400, Theodore Ts'o wrote:
> 
> > Do you have any objections if I upload this as a NMU?  Or would you
> > prefer to update the package?
> 
> Please Ted, go ahead. :)

Ok, thanks.  I'll do that this evening.  Since I got your ack, I won't
bother using a delayed queue.

BTW, I was looking at the local Debian patches, and with the exception
of the OUI list changes patch, I'm not convinced any of the other ones
make sense for us to be carrying.

In particular, 02-fix_usage_message.patch seems especially pointless,
since calling out that both "--mac=XX:XX:XX:XX:XX:XX" and "--mac
XX:XX:XX:XX:XX:XX" work is spectacularly pointless.  That's a
fundamental feature of how getopt_long works, and if we really felt
the need to explicitly mention this fact for every single option that
takes an argument, the usage message for pretty much all of GNU shell
utils would grow by a huge amount.

Similarly, the chances that we might pick the same random mac address
is *possible*, but (a) it's so unlikely that it's not worth bothering
about, and (b) having the same MAC address get used once in a very
long while is actually a good thing.

In fact, growing the number of addresses in the OUI list is actually,
paradoxically, more likely to cause people to make MAC address stand
out as being more likely to be a spoofed address.  Using a smaller
number of OUI's, but ones which are known to be commonly used by
modern systems, especially ones of the same type as the user (i.e., if
you are using a Thinkpad, you might want to use MAC addresses that are
used byThinkpads and Dell and HP laptops but if you use a MAC address
used by a medical device that would only be found in a hospital or
clinic, or research sensor, it might cause comment for that address to
show up at a Starbucks cafe).

Bottom line, keeping patches that are out of sync from upstream is
much more likely to cause harm than good.

Cheers,

- Ted

P.S.  In fact, it looks like macchiato[1] is more advanced in terms of
actually providing security and privacy to its users, as opposed to
something that only *appears* to provide security.

[1] https://github.com/EtiennePerot/macchiato

So I'm wondering if it's better to package macchiato and then
encourage people to switch ot it, or to try to add macchiato's
features into macchanger.  The advantage of the former is that it's
much less work.  The advantage of the latter is that it's more likely
Debian users will benefit, since they won't have to switch their boot
scripts to use macchiato.

And of course, probably the best thing to do is that this
functionality should be built into network-manager.  Where
network-manager really should be using random MAC addresses while it
is scanning for AP's, and depending on whether an AP (by MAC address)
is a "known" friendly one (i.e., when you are at your home router) or
one which is unknown (i.e., at a Starbucks cafe) it should
automatically randomize the MAC address before doing the DHCP dance


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#752075: daemontools-run: Add systemd support

[Michael Biebl]

[CCing the bug report]

Am 07.07.2014 14:39, schrieb Jonathan de Boyne Pollard:
> I did systemd units for this ages ago.  It's better to do this as two
> units: a "path" unit that watches the service directory and a
> "service" unit that is started when the service directory is found to
> be non-empty.

Makes sense I guess.

  And you don't need svscanboot at all, since systemd's
> journal logs the output of svscan and does it better than
> readproctitle does.

Ansgar suggested using the journal for that as well [1], which sounds
reasonable.

> There are minor variants on these in the nosh-systemd-services
> package, which runs the nosh daemontools-compatibility scanner under
> systemd in a similar (but not quite the same, since nosh has a
> separate socket-activated service manager and a choice of service
> scanners) manner.  For more documentation, install the nosh-guide
> package and read /usr/local/share/doc/nosh/svscan-startup.html .
> 
> For the packages themselves, go to
> http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
> .  I notice that I've missed off a link to the nosh-systemd-services
> package.  I'll try to fix that as soon as I have the right computer
> accessible.  It's not hard to guess the URL from the other hyperlinks
> there, though.  nosh-systemd-services_1.6_amd64.deb is the package
> name.
> 
> Do systemd units the systemd way, of course.  My unit files here are
> in /etc because they are my local administrator modifications.  Yours
> will have to be in /usr/lib .

In Debian that would be /lib/systemd/system/

  And don't forget to run "systemctl
> preset svscan.path" as part of your package installation process.
> (I've heard rumours that "update-rc.d svscan.path defaults" runs
> "systemctl preset svscan.path" in some testing versions somewhere; but
> I've not witnessed this myself.)

As Ansgar already mentioned, probably the best way to handle that in
Debian is to use the dh-systemd helper.
Unfortuantely the daemontools package doesn't use debhelper, which
complicates that a bit it.

>  jdebp /etc/systemd/system %cat svscan.path
>  [Unit]
>  Description=Daemontools service monitor
> 
>  [Path]
>  DirectoryNotEmpty=/service/
>  Unit=svscan.service

Is that a typo? Is that really a /service top-level directory?
Shouldn't that rather be something like /etc/service?

>  [Install]
>  WantedBy=multi-user.target
>  jdebp /etc/systemd/system %cat svscan.service
>  [Unit]
>  Description=Daemontools service scanner
> 
>  [Service]
>  ExecStart=/usr/bin/svscan /service/
>  Restart=always
> 
>  [Install]
> 

I guess we have enough options now how this can be addressed in
daemontools. A quite literal translation of the inittab entry or a
deeper integration into systemd utilizing the journal and mechanisms
like .path units.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752075#60

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#746838: marked as done (diagnostics: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 12:19:35 +
with message-id 
and subject line Bug#746838: fixed in diagnostics 0.3.3-10
has caused the Debian Bug report #746838,
regarding diagnostics: ftbfs with GCC-4.9
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.)


-- 
746838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:diagnostics
Version: 0.3.3-9
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

The package fails to build in a test rebuild on at least amd64 with
gcc-4.9/g++-4.9, but succeeds to build with gcc-4.8/g++-4.8. The
severity of this report may be raised before the jessie release.

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/diagnostics_0.3.3-9_unstable_gcc49.log
The last lines of the build log are at the end of this report.

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

  apt-get -t experimental install g++ 

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

[...]
/bin/bash ../../../libtool --tag=CXX   --mode=link x86_64-linux-gnu-g++  -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-Wall -Werror -pedantic  -Wl,-z,relro -lACE -lpthread -o libinstrumentation.la  
load_symbol.lo  -ldl 
libtool: link: x86_64-linux-gnu-ar cru .libs/libinstrumentation.a 
.libs/load_symbol.o 
libtool: link: x86_64-linux-gnu-ranlib .libs/libinstrumentation.a
libtool: link: ( cd ".libs" && rm -f "libinstrumentation.la" && ln -s 
"../libinstrumentation.la" "libinstrumentation.la" )
make[9]: Leaving directory 
`/«PKGBUILDDIR»/diagnostics/extensions/instrumentation'
make[8]: Leaving directory 
`/«PKGBUILDDIR»/diagnostics/extensions/instrumentation'
make[7]: Leaving directory 
`/«PKGBUILDDIR»/diagnostics/extensions/instrumentation'
Making all in memory
make[7]: Entering directory `/«PKGBUILDDIR»/diagnostics/extensions/memory'
rm -f *.o *.lo *.la
rm -f diag_stamp_*
touch diag_stamp_2
make  all-recursive
make[8]: Entering directory `/«PKGBUILDDIR»/diagnostics/extensions/memory'
make[9]: Entering directory `/«PKGBUILDDIR»/diagnostics/extensions/memory'
/bin/bash ../../../libtool --tag=CXX   --mode=compile x86_64-linux-gnu-g++ 
-DHAVE_CONFIG_H   -I../../.. -DDEBUG__LEVEL__=2 -D_FORTIFY_SOURCE=2  -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-Wall -Werror -pedantic -MT allocation_database.lo -MD -MP -MF 
.deps/allocation_database.Tpo -c -o allocation_database.lo 
allocation_database.cpp
libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I../../.. 
-DDEBUG__LEVEL__=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Werror 
-pedantic -MT allocation_database.lo -MD -MP -MF .deps/allocation_database.Tpo 
-c allocation_database.cpp  -fPIC -DPIC -o .libs/allocation_database.o
libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I../../.. 
-DDEBUG__LEVEL__=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Werror 
-pedantic -MT allocation_database.lo -MD -MP -MF .deps/allocation_database.Tpo 
-c allocation_database.cpp -o allocation_database.o >/dev/null 2>&1
mv -f .deps/allocation_database.Tpo .deps/allocation_database.Plo
/bin/bash ../../../libtool --tag=CXX   --mode=compile x86_64-linux-gnu-g++ 
-DHAVE_CONFIG_H   -I../../.. -DDEBUG__LEVEL__=2 -D_FORTIFY_SOURCE=2  -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-Wall -Werror -pedantic -MT annotations.lo -MD -MP -MF .deps/annotations.Tpo -c 
-o annotations.lo annotations.cpp
libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I../../.. 
-DDEBUG__LEVEL__=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Werror 
-pedantic -MT annotations.lo -MD -MP -MF .deps/annotations.Tpo -c 
annotations.cpp  -fPIC -DPIC -o .libs/annotations.o
In file included from ../../../diagnostics/frame/platform_config.hpp:51:0,
 from ../../../diagnostics/extensions/memory/annotations.hpp:30,
 from annotations.cpp:28:
../../../diagnostics/frame/namespace.hpp:53:52: error: 'void 
{anonymous}::dummy_for_se

Bug#733352: marked as done (tophat: FTBFS: string_base.h:1465:53: error: no matching function for call to 'seqan::Gaps >, seqan::Tag >::Gaps(const

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 12:55:55 +
with message-id 
and subject line Bug#733352: fixed in tophat 2.0.12+dfsg-1
has caused the Debian Bug report #733352,
regarding tophat: FTBFS: string_base.h:1465:53: error: no matching function for 
call to 'seqan::Gaps >, 
seqan::Tag >::Gaps(const seqan::String 
>&)'
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.)


-- 
733352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tophat
Version: 2.0.10-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131226 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):
> g++ -DHAVE_CONFIG_H -I. -I..   -D_FORTIFY_SOURCE=2  -Wall 
> -Wno-strict-aliasing -g -gdwarf-2 -Wuninitialized  -O3 -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -DNDEBUG -pthread -I/usr/include  -I./SeqAn-1.3 -c -o segment_juncs.o 
> segment_juncs.cpp
> In file included from segment_juncs.cpp:37:0:
> common.h: In member function 'void GBamWriter::write(bam1_t*, int64_t)':
> common.h:578:14: warning: variable 'pre_block_offs' set but not used 
> [-Wunused-but-set-variable]
>   int pre_block_offs=0; //but before this write()
>   ^
> segment_juncs.cpp: In member function 'void 
> SegmentSearchWorker::operator()()':
> segment_juncs.cpp:4720:27: warning: variable 'last_read_id' set but not used 
> [-Wunused-but-set-variable]
>  uint64_t read_id = 0, last_read_id = 0;
>^
> In file included from /usr/include/seqan/sequence.h:82:0,
>  from segment_juncs.cpp:27:
> /usr/include/seqan/sequence/string_base.h: In instantiation of 'static void 
> seqan::AppendValueToString_::appendValue_(T&, TValue&) [with T = 
> seqan::String >, 
> seqan::Tag >, seqan::Alloc<> >; TValue = const 
> seqan::String >; TExpand = 
> seqan::Tag]':
> /usr/include/seqan/sequence/string_base.h:1490:65:   required from 'void 
> seqan::appendValue(seqan::String&, const TValue&, 
> seqan::Tag) [with TTargetValue = seqan::Gaps seqan::Alloc<> >, seqan::Tag >; TTargetSpec = 
> seqan::Alloc<>; TValue = seqan::String >; TExpand = 
> seqan::TagGenerous_]'
> /usr/include/seqan/sequence/sequence_interface.h:1241:72:   required from 
> 'void seqan::appendValue(T&, const TValue&) [with T = 
> seqan::String >, 
> seqan::Tag >, seqan::Alloc<> >; TValue = 
> seqan::String >]'
> segment_juncs.cpp:2605:32:   required from here
> /usr/include/seqan/sequence/string_base.h:1465:53: error: no matching 
> function for call to 'seqan::Gaps >, 
> seqan::Tag >::Gaps(const seqan::String seqan::Alloc<> >&)'
>  typename Value::Type temp_copy(_value); //temp copy because 
> resize could invalidate _value
>  ^
> /usr/include/seqan/sequence/string_base.h:1465:53: note: candidates are:
> In file included from /usr/include/seqan/align.h:76:0,
>  from segment_juncs.cpp:31:
> /usr/include/seqan/align/gaps_array.h:156:5: note: seqan::Gaps seqan::Tag >::Gaps(const seqan::Gaps seqan::Tag >&) [with TSequence = seqan::String seqan::Alloc<> >]
>  Gaps(Gaps const & other) :
>  ^
> /usr/include/seqan/align/gaps_array.h:156:5: note:   no known conversion for 
> argument 1 from 'const seqan::String >' to 'const 
> seqan::Gaps >, 
> seqan::Tag >&'
> /usr/include/seqan/align/gaps_array.h:146:5: note: seqan::Gaps seqan::Tag >::Gaps(TSequence&) [with TSequence = 
> seqan::String >]
>  Gaps(TSequence & seq) :
>  ^
> /usr/include/seqan/align/gaps_array.h:146:5: note:   no known conversion for 
> argument 1 from 'const seqan::String >' to 
> 'seqan::String >&'
> /usr/include/seqan/align/gaps_array.h:141:5: note: seqan::Gaps seqan::Tag >::Gaps() [with TSequence = seqan::String seqan::Alloc<> >]
>  Gaps() : _sourceBeginPos(0), _sourceEndPos(0), _clippingBeginPos(0), 
> _clippingEndPos(0)//,
>  ^
> /usr/include/seqan/align/gaps_array.h:141:5: note:   candidate expects 0 
> arguments, 1 provided
> In file included from /usr/include/seqan/modifier.h:67:0,
>  from /usr/include/seqan/find.h:44,
>  from segment_juncs.cpp:28:
> /usr/include/seqan/modifier/modifier_view.h: In instantiation of 
> 'seqan::ModifiedString 
> >::ModifiedString(const THost_&, typename 
> seqan::EnableIf >::Type*) [with THost_ = 
> seqan::String, seqan::Alloc<> 
> >; THost = seqan::String, 
> seqan::Alloc<> >; TFunct

Bug#733352: [Debian-med-packaging] Bug#733352: Bowtie and tophat fail to build with seqan >= 1.4

[Alex Mestiashvili]

Patch provided by Manuel Holtgrewe solves the build issues with 
seqan-1.4 and tophat.


https://lists.fu-berlin.de/pipermail/seqan-dev/2014-July/msg1.html

Alex


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#751888: [Gluster-devel] Bug#751888: glusterfs-server: creating symlinks generates errors

[Patrick Matthäi]

thanks :)

Am 02.07.2014 17:01, schrieb Thomas Goirand:

Hi,

I'm uploading a bugfix version in Debian with the patch available from
here: http://review.gluster.org/#/c/8153/

I would usually do this kind of NMU using the delayed queue, but since
Patrick Matthäi wrote he's on vacation, I don't see the point in
delaying more. My upload is by the way very minimalistic, and only
including the upstream patch. I wont send a debdiff, since that's really
only the stripe.c patch added to the package (I'm not adding the new
tests, I'll leave this work/decision to the maintainers of glusterfs).

I hope this helps.

Cheers,

Thomas Goirand (zigo)


--
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#754059: marked as done ([systemd-sysv] Conflicts with sysvinit-core)

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 13:09:35 +0200
with message-id <53ba7fef.1010...@debian.org>
and subject line Re: Bug#754059: [systemd-sysv] Conflicts with sysvinit-core
has caused the Debian Bug report #754059,
regarding [systemd-sysv] Conflicts with sysvinit-core
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.)


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

Package: systemd-sysv
Version: 204-14
Severity: serious

systemd-sysv conflicts with sysvinit-core, which is required.

This is particularly problematic since libpam-systemd alternatively depends on 
systemd-sysv. On my testing install, APT's solution when asked to upgrade 
systemd is to remove sysvinit-core:

# LANG=C apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... The following packages were automatically installed and 
are no longer required:
  libcolamd2.8.0 lp-solve xulrunner-29
Use 'apt-get autoremove' to remove them.
Done
The following packages will be REMOVED:
  sysvinit-core
The following NEW packages will be installed:
  systemd-sysv
The following packages will be upgraded:
  libpam-systemd libsystemd-daemon0 libsystemd-id128-0 libsystemd-journal0 
libsystemd-login0 systemd
6 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.


Removing libpam-systemd isn't too tempting neither:

# LANG=C apt-get remove libpam-systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libcolamd2.8.0 libmodemmanagerqt1 libnetworkmanagerqt1 lp-solve xulrunner-29
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  colord hplip kde-plasma-desktop libpam-systemd network-manager plasma-nm 
plasma-widget-networkmanagement policykit-1 policykit-1-gnome 
printer-driver-postscript-hp udisks2
0 upgraded, 0 newly installed, 11 to remove and 5 not upgraded.


I managed to solve this safely by installing systemd-shim.

I was surprised to see APT propose the removal of a required package. I didn't 
test how that would go, but if that's not a problem, something must be wrong 
with its priority field. I'll save my system from such an experimentation and 
let others decide if this needs to be reassigned.

--
Filipus Klutiero
http://www.philippecloutier.com
--- End Message ---
--- Begin Message ---
Am 07.07.2014 08:56, schrieb Filipus Klutiero:
> Package: systemd-sysv
> Version: 204-14
> Severity: serious
> 
> systemd-sysv conflicts with sysvinit-core, which is required.

Correct, systemd-sysv has a Conflicts/Replaces against sysvinit-core so
it is actually possible to switch between different init systems.

This is not a bug but intentional and necessary. Thus closing the bug
report.


Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#753954: [deejayd] Some sources are not included in your package

[Bastien ROUCARIES]

On Mon, Jul 7, 2014 at 12:39 PM, Alexandre Rossi
 wrote:
> tag 753954 pending
> thanks
>
> Hi,
>
>> Your package seems to include some files that lack sources
>> in prefered forms of modification:
>>
>> data/htdocs/js/lib/jquery.js
>
> Fixed package is awaiting sponsorship.
>
> http://mentors.debian.net/debian/pool/main/d/deejayd/deejayd_0.10.0-7.dsc
>
> I added debian/patches/jssouce which adds
> data/htdocs/js/lib/jquery.src.js alongside
> data/htdocs/js/lib/jquery.js .
>
> However lintian is not happy with this, source-is-missing is still
> triggered, but at least this bug is fixed. Please advice as to report
> this as a lintian bug.

No it is perfect but you could add it under debian/missing-source .
Lintian found it automatically

Bastien
>
> Thanks for reporting,
>
> Alex


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#754073: fetchmailconf: Fetchmail does not start -- libBLT.2.4.so.8.6

[Jonás Andradas]

Package: fetchmailconf
Version: 6.3.26-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

when trying to start fetchmailconf, the following error is found:

~$ fetchmailconf
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/fetchmailconf.py", line 8, in 
from Tkinter import *
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 42, in 
raise ImportError, str(msg) + ', please install the python-tk package'
ImportError: libBLT.2.4.so.8.6: cannot open shared object file: No such file or
directory, please install the python-tk package

Package python-tk is installed, and blt too.  However the libBLT library
present in the system is 2.5 instead of 2.4:

ls: cannot access /usr/lib/libBLT.2.4.so.8.6: No such file or directory

blt: /usr/lib/libBLT.2.5.so.8.6

If this bug should not be associated with fetchmailconf but with python-tk,
please, change it accordingly (if possible), or I will re-open it there.

Thank you very much in advance,

Best Regards,

Jonás.



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.12-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages fetchmailconf depends on:
ii  fetchmail  6.3.26-1
ii  python 2.7.6-2
ii  python-tk  2.7.7-2

fetchmailconf recommends no packages.

fetchmailconf suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#753954: [deejayd] Some sources are not included in your package

[Alexandre Rossi]

tag 753954 pending
thanks

Hi,

> Your package seems to include some files that lack sources
> in prefered forms of modification:
>
> data/htdocs/js/lib/jquery.js

Fixed package is awaiting sponsorship.

http://mentors.debian.net/debian/pool/main/d/deejayd/deejayd_0.10.0-7.dsc

I added debian/patches/jssouce which adds
data/htdocs/js/lib/jquery.src.js alongside
data/htdocs/js/lib/jquery.js .

However lintian is not happy with this, source-is-missing is still
triggered, but at least this bug is fixed. Please advice as to report
this as a lintian bug.

Thanks for reporting,

Alex


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#753954: [deejayd] Some sources are not included in your package

[Debian Bug Tracking System]

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

> tag 753954 pending
Bug #753954 [deejayd] [deejayd] Some sources are not included in your package
Added tag(s) pending.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#753985: gpgv-udeb: fails to validate Release files (missing sha256 support)

[Didier 'OdyX' Raboud]

Control: affects -1 +win32-loader

Folks,

Le dimanche, 6 juillet 2014 21.47:29, vous avez écrit :
> I'm really sorry for:
>  - having failed to reply to your request in time[1];
>  - having failed to deliver any testing, which led to lost user
> time[2] and is going to cost another gnupg upload.

Same here, btw.

This bug hits gpgv-win32 (which is functional per se, but not sufficient 
for checking the Release files) and therefore win32-loader.

>  b) Thankfully we don't need to consider the backup plan mentioned in
> a) since all we need is enabling sha256 support. Currently, Release
> files include MD5+SHA1+SHA256. You'll find a tested patch attached.
> (This means a whole installation using a netboot-gtk image.)

I can confirm that Cyril's patch fixes gpgv.exe usage within win32-
loader.

Cheers,

OdyX


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#753225: marked as done (manderlbot: FTBFS: Latex errors)

[Debian Bug Tracking System]

Your message dated Mon, 07 Jul 2014 09:36:59 +
with message-id 
and subject line Bug#753225: fixed in manderlbot 0.9.2-19
has caused the Debian Bug report #753225,
regarding manderlbot: FTBFS: Latex errors
to be marked as done.

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

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


-- 
753225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: manderlbot
Version: 0.9.2-18
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140628 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»/doc'
> docbook2man manderlbot.1.sgml
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
> Working on: /«PKGBUILDDIR»/doc/manderlbot.1.sgml
> nsgmls:/«PKGBUILDDIR»/doc/manderlbot.1.sgml:36:13:E: document type does not 
> allow element "OPTION" here; missing one of "COMMAND", "ARG", "GROUP" 
> start-tag
> 
> DimitriFontaine2003Dimitri FontaineDone.
> lyx -e latex manderlbot.lyx
> hevea -fix url-fix.hva manderlbot.tex
> ./url-fix.hva:6: Parsing of argument failed
> ./url-fix.hva:6: Giving up command: \renewcommand
> ./url-fix.hva:50: Error while reading LaTeX macros arguments:
>   End of file in argument
> Adios
> make[3]: *** [manderlbot.html] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/28/manderlbot_0.9.2-18_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: manderlbot
Source-Version: 0.9.2-19

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

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated manderlbot 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: SHA1

Format: 1.8
Date: Mon, 07 Jul 2014 12:38:21 +0400
Source: manderlbot
Binary: manderlbot
Architecture: source all
Version: 0.9.2-19
Distribution: unstable
Urgency: low
Maintainer: Debian Erlang Packagers 
Changed-By: Sergei Golovan 
Description:
 manderlbot - IRC bot, written in Erlang
Closes: 753225
Changes:
 manderlbot (0.9.2-19) unstable; urgency=low
 .
   * Fixed options in manpage.
   * Removed % from additional CSS to please hevea (closes: #753225).
   * Bumped standards version to 3.9.5.
Checksums-Sha1:
 e4bdbbd1042a4b24d5aa5acc829d6683f9083f12 1204 manderlbot_0.9.2-19.dsc
 b9df27a64f4a47914642a60001012343197c754f 10032 
manderlbot_0.9.2-19.debian.tar.xz
 7fe3a8d0ba4227a219220f3929bfc16f11d173ae 120716 manderlbot_0.9.2-19_all.deb
Checksums-Sha256:
 b2e91148b3ef50caacc76bc9bf05ec695cbd9e4b4b9c2f5dfd40b927c088d1e2 1204 
manderlbot_0.9.2-19.dsc
 8342134ec95badfac2ca9626ab2833a991307c551ca45d8e855a711c0dc02545 10032 
manderlbot_0.9.2-19.debian.tar.xz
 6e2bf089d6e945d0e79c1b12eb3eeda5d3cb8bfab3ffcb52e5c76a05b44e56b4 120716 
manderlbot_0.9.2-19_all.deb
Files:
 0f58f880db8bdb74e257df9ae1acd948 120716 net optional 
manderlbot_0.9.2-19_all.deb
 d20df5823e9fddde8009007aa568546b 1204 net optional manderlbot_0.9.2-19.dsc
 26f1b1a40c0c6896c7d4bb5ddfc06e37 10032 net optional 
manderlbot_0.9.2-19.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iD8DBQFTul2vIcdH02pGEFIRAoeYAJ9mhsyrcwtdbanAj3N4CwQKynOeMACfYF6u
UALDBVXcI8+puW2o8trrhf0=
=9s+s
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#753985: gpgv-udeb: fails to validate Release files (missing sha256 support)

[Debian Bug Tracking System]

Processing control commands:

> affects -1 +win32-loader
Bug #753985 [gpgv-udeb] gpgv-udeb: fails to validate Release files (missing 
sha256 support)
Added indication that 753985 affects win32-loader

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#751228: libffado: does not compile on mips

[Sebastian Ramacher]

Hi

On 2014-07-07 10:56:45, Adrian Knoth wrote:
> > repository. Could you please push your changes?
> 
> That's pushed now.

Thank you!
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#746589: More on this bug

[d_baron]

I have it too, rendering a new 64-bit wheezy 7.5 install unusable!


I doubt that kdm itself is the problem though I tried to file a bug for this a 
well. The 4.8 version with all the 4.8 packages worked flawlessly. It was some 
other upgraded package, most likely not part of KDE that killed it. I upgraded 
the kdm and a lot of kde stuff as well to 4.11+ in desperation to get it 
working again, to no avail.


There is a similar 2011 bug still around against dbus #649362‭‮

Bug#751228: libffado: does not compile on mips

[Adrian Knoth]

On Sun, Jul 06, 2014 at 01:09:08PM +0200, Sebastian Ramacher wrote:

> Hi Adrian,

Hi!

> repository. Could you please push your changes?

That's pushed now.


HTH

-- 
mail: a...@thur.de  http://adi.thur.de  PGP/GPG: key via keyserver


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: your mail

[Debian Bug Tracking System]

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

> severity 740885 grave
Bug #740885 [wmbattery] wmbattery: no updates and no time estimation after 
kernel upgrade
Severity set to 'grave' from 'important'
>
End of message, stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#753442: why do you blame systemd?

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #753442 [debootstrap] debootstrap: host's /run/shm gets unmounted after 
debootstrap run
Removed tag(s) moreinfo.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#753444: Bug#753542: Bug#753444: Bug#753542: perl-base - Segfaults in libperl.so.5.18

[Emilio Pozuelo Monfort]

On 07/07/14 09:31, Aurelien Jarno wrote:
> On Sat, Jul 05, 2014 at 07:15:56PM +0200, Emilio Pozuelo Monfort wrote:
>> That said, feel free to upload perl now.
> 
> It has been uploaded, and is now installed on all s390x buildds.

Thanks. I have scheduled a bunch of binNMUs.

Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#753442: why do you blame systemd?

[Holger Levsen]

control: tags -1 - moreinfo

Hi Daniel, 

thanks for providing more information!


cheers,
Holger


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

Bug#754063: initscripts: no longer depends on ifupdown

[Michal Suchanek]

Package: initscripts
Version: 2.88dsf-53.2
Severity: grave
Justification: renders package unusable

Hello,

I upgraded initscripts which no llonger depend on ifupdown.

Hence I have no networking on next boot.

IMHO this renders the initscripts unusable for 90% of users.

Please fix.

Thanks

Michal

-- System Information:
Debian Release: 7.5
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (500, 'testing'), (410, 
'unstable'), (400, 'experimental'), (300, 'saucy-updates'), (300, 
'saucy-security'), (300, 'saucy-proposed'), (300, 'saucy-backports'), (300, 
'saucy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.15-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages initscripts depends on:
ii  coreutils   8.13-3.5
ii  debianutils 4.3.2
ii  libc6   2.19-4
ii  lsb-base4.1+Debian8+deb7u1
ii  mount   2.22-1~test1
ii  sysv-rc 2.88dsf-53.2
ii  sysvinit-utils  2.88dsf-53.2

Versions of packages initscripts recommends:
ii  e2fsprogs  1.42.5-1.1
ii  psmisc 22.19-1+deb7u1

initscripts suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: jessie

[Debian Bug Tracking System]

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

> tags 753516 + sid jessie
Bug #753516 [xscorch] xscorch: fails to parse its data file
Added tag(s) sid and jessie.
> tags 753955 + sid jessie
Bug #753955 [adacgi1] adacgi1: not installable in sid
Added tag(s) sid and jessie.
> tags 753957 + sid jessie
Bug #753957 [libahven3-dev] ahven-dbg: not installable in sid
Added tag(s) sid and jessie.
> tags 753978 + sid jessie
Bug #753978 [golang-go.tools,easygit] easygit and golang-go.tools: error when 
trying to install together
Added tag(s) sid and jessie.
> tags 753833 + wheezy-ignore
Bug #753833 [uriparser] Source package contains non-free IETF RFC/I-D
Added tag(s) wheezy-ignore.
> tags 753760 + wheezy-ignore
Bug #753760 [uncrustify] Non free logo
Added tag(s) wheezy-ignore.
> tags 752644 + wheezy-ignore
Bug #752644 [php-net-smtp] php-net-smtp is licensed under the PHP license and 
is not PHP
Added tag(s) wheezy-ignore.
> tags 752223 + wheezy-ignore
Bug #752223 {Done: Olivier Sallou } [src:biomaj-watcher] 
[biomaj-watcher] Some sources are not included in your package
Added tag(s) wheezy-ignore.
> tags 752215 + wheezy-ignore
Bug #752215 [src:advene] [src:advene]  Some sources are not included in your 
package
Added tag(s) wheezy-ignore.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
752215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752215
752223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752223
752644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752644
753516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753516
753760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753760
753833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753833
753955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753955
753957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753957
753978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#753444: Bug#753542: Bug#753444: Bug#753542: perl-base - Segfaults in libperl.so.5.18

[Aurelien Jarno]

On Sat, Jul 05, 2014 at 07:15:56PM +0200, Emilio Pozuelo Monfort wrote:
> That said, feel free to upload perl now.

It has been uploaded, and is now installed on all s390x buildds.

Aurelien

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org