Bug#752376: systemd-cron: does not meet requirements for cron-daemon

[Ansgar Burchardt]

Package: systemd-cron
Version: 1.1.1-1

The cron-daemon virtual package is defined as
+---
|  cron-daemon Any cron daemon that correctly follows policy
|  requirements
+---[ file:///usr/share/doc/debian-policy/virtual-package-names-list.txt.gz ]

The policy requirements are documented in 9.5 and also include
+---
| Any cron daemon must provide /usr/bin/crontab and support normal
| crontab entries as specified in POSIX. The daemon must also support
| names for days and months, ranges, and step values. It has to support
| /etc/crontab, and correctly execute the scripts in /etc/cron.d.
+---[ https://www.debian.org/doc/debian-policy/ch-opersys.html#s-cron-jobs ]

According to the package description, systemd-cron does not fulfill
these requirement and thus should not have Provides: cron-daemon.

I think it provides similar features as "anacron". So maybe it should
have a Provides: anacron instead?

Ansgar


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

Bug#752354: perl: trivial test C program fails to compile

[Damyan Ivanov]

-=| Niko Tyni, 22.06.2014 23:50:56 +0300 |=-
> Package: perl
> Version: 5.20.0-1
> Severity: important
> User: debian-p...@lists.debian.org
> Usertags: perl-5.20-transition
> 
> This is a regression from 5.18 and makes xchat-gnome drop
> its libperl linkage because its autoconf probe fails.
> 
>   % cat perltest.c 
>   #include 
>   #include 
>   #include 
>   int main() { return 0; }
>   % gcc $(perl -MExtUtils::Embed -e ccopts) perltest.c
>   /tmp/ccN3C0Sz.o: In function `S_croak_memory_wrap':
>   perltest.c:(.text+0x5): undefined reference to `PL_memory_wrap'
>   perltest.c:(.text+0x14): undefined reference to `Perl_croak_nocontext'
>   collect2: error: ld returned 1 exit status

I see this too. The compilation succeeds with 5.18.

> The severity should arguably be 'serious'.

Perhaps. But I think the fix is not in perl but in xchat-gnome.

It seems PL_memory_wrap and Perl_croak_nocontext were moved to libperl 
in 5.20, so the test library needs to link with that. Adding
 $(perl -MExtUtils::Embed -e ldopts)
to the compiler flags makes it pass. And xchat-gnome configuration 
looks like this:

 checking for perl... /usr/bin/perl
 checking for Perl header files... found
 checking for Perl library... found
 …
 checking for perl... /usr/bin/perl
 checking for perl >= 5.8.1... 5.20.0
 checking for XML::Parser... ok
 …
 checking which plugins to build...  autoaway notification url_scraper 
 sound-notification net-monitor notify-osd perl python tcl
 …
 config.status: creating plugins/perl/Makefile

Attached is the patch to xchat-gnome.

Not yet reassigning to allow a sanity check on my conclusions :)

Cheers,
dam

Description: configure.ac: fix perl header test for perl 5.20
 The PL_memory_wrap and Perl_croak_nocontext symbols are now in libperl so a
 test program needs to link with it.
 Adding $($PERL -MExtUtils::Embed -e ldopts) to the compiler command line does
 just that.
Author: Damyan Ivanov 
Bug-Debian: http://bugs.debian.org/752354

--- a/configure.ac
+++ b/configure.ac
@@ -164,7 +164,7 @@ fi
 
 if test "x$have_perl" != "xno"; then
 	AC_MSG_CHECKING(for Perl header files)
-	PERL_HEADER_TEST=`PT=perltest.c ; echo "#include " > $PT;  echo "#include " >> $PT;  echo "#include " >> $PT ;  echo "int main() { return 0; }" >> $PT ; $CC -Wall $PT -o $PT.out $($PERL -MExtUtils::Embed -e ccopts) 1>/dev/null 2>&1; echo $?; rm -f $PT $PT.out 1>/dev/null 2>&1`
+	PERL_HEADER_TEST=`PT=perltest.c ; echo "#include " > $PT;  echo "#include " >> $PT;  echo "#include " >> $PT ;  echo "int main() { return 0; }" >> $PT ; $CC -Wall $PT -o $PT.out $($PERL -MExtUtils::Embed -e ccopts) $($PERL -MExtUtils::Embed -e ldopts) 1>/dev/null 2>&1; echo $?; rm -f $PT $PT.out 1>/dev/null 2>&1`
 
 	if test "x$PERL_HEADER_TEST" = "x0" ; then
 		PERL_CFLAGS=`$PERL -MExtUtils::Embed -e ccopts`


signature.asc
Description: Digital signature

Bug#752283: downgrade to acpi-support* 0.141-2 fixed suspend

[Gijs Hillenius]

Temp fix:

apt-get purge acpi-fakekey acpi-support acpi-support-base

and

dpkg -i acpi-support_0.141-2_all.deb \\
acpi-fakekey_0.141-2_i386.deb \\
acpi-support-base_0.141-2_all.deb

and

editing /etc/default/acpi-support to re-enable lid

restores the suspend at LID close.



I had previously purged only acpi-fakekey acpi-support so, perhaps the
issue is in acpi-support-base


Looking at the difference between 
acpi-support-base 0.141-2 and 0.141-3

I noticed that something changed in power-funcs
( /usr/share/acpi-support/power-funcs)

0.141.2:
{ print unix_user; exit (0); } /x11-display = '\'$display.0\''/ { print 
unix_user; exit (0);}')

0.141.3:
{ print unix_user; exit (0); }')




-- 
BOFH excuse #239:

CPU needs bearings repacked


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

Bug#734523: dhelp: Error while building the HTML tree

[Arvind R.]

Package: dhelp
Version: 0.6.21+nmu4
Followup-For: Bug #734523

Dear Maintainer,

   * What led up to the situation?
 - system upgrade (jessie) prior to new devel requirement
   * What was the outcome of this action?
 - /usr/share/doc/HTML contains only README file, so
~# dpkg-reconfigure dhelp
Disabling dhelp
Run /etc/init.d/lighttpd force-reload to enable changes
[ ok ] Reloading web server configuration: lighttpd.
Building HTML tree...ArgumentError: invalid byte sequence in US-ASCII 
(/usr/lib/ruby/vendor_ruby/dhelp.rb:185:in `==='
/usr/lib/ruby/vendor_ruby/dhelp.rb:185:in `block in initialize'
/usr/lib/ruby/vendor_ruby/dhelp.rb:183:in `each'
/usr/lib/ruby/vendor_ruby/dhelp.rb:183:in `initialize'
/usr/lib/ruby/vendor_ruby/dhelp.rb:309:in `new'
/usr/lib/ruby/vendor_ruby/dhelp.rb:309:in `block (2 levels) in each'
/usr/lib/ruby/vendor_ruby/dhelp.rb:306:in `each'
/usr/lib/ruby/vendor_ruby/dhelp.rb:306:in `block in each'
/usr/lib/ruby/vendor_ruby/dhelp.rb:305:in `each'
/usr/lib/ruby/vendor_ruby/dhelp.rb:305:in `each'
/usr/lib/ruby/vendor_ruby/dhelp.rb:456:in `_register_docs'
/usr/lib/ruby/vendor_ruby/dhelp.rb:387:in `rebuild'
/usr/sbin/dhelp_parse:204:in `main'
/usr/sbin/dhelp_parse:216:in `')
 done.
Enabling dhelp: ok
Run /etc/init.d/lighttpd force-reload to enable changes
[ ok ] Reloading web server configuration: lighttpd.
Reindexing documentation in the background
~#
 - /usr/share/doc/HTML contains only README file

   * What outcome did you expect instead?
 - that /usr/share/doc/HTML/index.html to be created by reconfiguration

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

Kernel: Linux 3.15.1 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages dhelp depends on:
ii  doc-base0.10.5
ii  libdata-page-perl   2.02-1
ii  libhtml-parser-perl 3.71-1+b1
ii  liblocale-gettext-perl  1.05-8
ii  libtemplate-perl2.24-1.1+b1
ii  liburi-perl 1.60-1
ii  perl-modules5.18.2-4
ii  poppler-utils   0.24.5-4
ii  pstotext1.9-6
ii  ruby1:2.1.0.1
ii  ruby-bdb0.6.6-1+b1
ii  ruby-debian 0.3.8+b4
ii  ruby-gettext3.1.2-1
ii  ruby2.0 [ruby-interpreter]  2.0.0.484+really457-3
ii  ruby2.1 [ruby-interpreter]  2.1.2-2
ii  swish++ 6.1.5-2.2
ii  ucf 3.0030

Versions of packages dhelp recommends:
ii  html2text1.3.2a-17
ii  iceweasel [www-browser]  29.0.1-2
ii  links2 [www-browser] 2.8-2
ii  w3m [www-browser]0.5.3-15

Versions of packages dhelp suggests:
ii  catdvi0.14-12.1
ii  info2www  1.2.2.9-24
ii  lighttpd [httpd-cgi]  1.4.35-2
ii  man2html  1.6g-7

-- no debconf information


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

Bug#752354: perl: trivial test C program fails to compile

[Russ Allbery]

Damyan Ivanov  writes:

> Perhaps. But I think the fix is not in perl but in xchat-gnome.

> It seems PL_memory_wrap and Perl_croak_nocontext were moved to libperl 
> in 5.20, so the test library needs to link with that. Adding
>  $(perl -MExtUtils::Embed -e ldopts)
> to the compiler flags makes it pass. And xchat-gnome configuration 
> looks like this:

>  checking for perl... /usr/bin/perl
>  checking for Perl header files... found
>  checking for Perl library... found
>  …
>  checking for perl... /usr/bin/perl
>  checking for perl >= 5.8.1... 5.20.0
>  checking for XML::Parser... ok
>  …
>  checking which plugins to build...  autoaway notification url_scraper 
>  sound-notification net-monitor notify-osd perl python tcl
>  …
>  config.status: creating plugins/perl/Makefile

> Attached is the patch to xchat-gnome.

> Not yet reassigning to allow a sanity check on my conclusions :)

Your patch looks correct to me.  It looks like this Autoconf probe was
relying on those functions being implemented as macros?  I'm not sure how
the probe program could otherwise be successfully linked without including
the linker options.

-- 
Russ Allbery (r...@debian.org)   


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

Bug#752276: /usr/bin/dose-distcheck: support arch and version comparison with --checkonly

[Ralf Treinen]

Hi Vagrant,

On Sat, Jun 21, 2014 at 07:11:17PM -0700, Vagrant Cascadian wrote:
> Package: dose-distcheck
> Version: 3.2.2-1
> Severity: wishlist
> File: /usr/bin/dose-distcheck
> 
> It would be nice if --checkonly supported the full syntax you're likely to
> find in a Build-Depends line in a .dsc file, including things such as
> architecture [arch], or version comparisons (>= x.y.z):

AFAIK, only (=x.y.z) version comparisons are supported in the --check-only
option.

[arch] specifiers would be misleading here, as one would it expect to mean
"check that package in that version on that arch", which is not the meaning
of [arch] in a dsc file. Rather, if package p1 has a build-dependency on
package p2[arch], this means that when you compile package p1 on [arch]
then you need p2. It does, a priori, not mean that p2 has to be of
architecture arch. Furthermore, build-depencies may contain alternatives
(even though they are rarely used in build-dependencies), and they do not
make sense in the context of the --check-only option.

>   dose-debcheck --failures --explain --checkonly "debhelper, cpio, kmod, 
> gcc-4.8 (>= 4.8.2-21)" /var/lib/apt/lists/*amd64*Packages
>   (W)Debcudf: Package (gcc-4.8,4.8.2-21) does not have an associated cudf 
> version
>   The applications raised this exception : Not_found

It is not normal that an exception is raised, this seems to be a bug.

If you wish to check build-dependencies you should rather use
dose-builddebcheck. You can "almost" run it on the .dsc file itself -
you just have to change in the dsc file the "Source: p" into "Package: p".
We probably should allow dose-debbuildcheck to support this syntax.

Does dose-builddebcheck the job? If not, could you please explain your
usecase?

Cheers -Ralf.


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

Bug#752354: perl: trivial test C program fails to compile

[Niko Tyni]

On Mon, Jun 23, 2014 at 12:42:59AM -0700, Russ Allbery wrote:
> Damyan Ivanov  writes:
> 
> > Perhaps. But I think the fix is not in perl but in xchat-gnome.
> 
> > It seems PL_memory_wrap and Perl_croak_nocontext were moved to libperl 
> > in 5.20, so the test library needs to link with that. Adding
> >  $(perl -MExtUtils::Embed -e ldopts)
> > to the compiler flags makes it pass. And xchat-gnome configuration 
> > looks like this:
> 
> >  checking for perl... /usr/bin/perl
> >  checking for Perl header files... found
> >  checking for Perl library... found
> >  …
> >  checking for perl... /usr/bin/perl
> >  checking for perl >= 5.8.1... 5.20.0
> >  checking for XML::Parser... ok
> >  …
> >  checking which plugins to build...  autoaway notification url_scraper 
> >  sound-notification net-monitor notify-osd perl python tcl
> >  …
> >  config.status: creating plugins/perl/Makefile
> 
> > Attached is the patch to xchat-gnome.
> 
> > Not yet reassigning to allow a sanity check on my conclusions :)
> 
> Your patch looks correct to me.  It looks like this Autoconf probe was
> relying on those functions being implemented as macros?  I'm not sure how
> the probe program could otherwise be successfully linked without including
> the linker options.

Thanks for looking at this.

The probe doesn't actually use anything from the headers, it just
includes them:

#include 
#include 
#include 
int main() { return 0; }

It's not clear to me that this should require libperl linkage?
-- 
Niko Tyni   nt...@debian.org


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

Bug#752377: Typo in Description

[Barak A. Pearlmutter]

Package: libpam-fprintd
Version: 0.4.1-5-g73edad0-3
Severity: minor

The description

  $ apt show libpam-fprintd | grep -A100 Description:

  Description: PAM module for fingerprint authentication trough fprintd
   fprintd is a D-Bus daemon that offers libfprint functionality over the
   D-Bus interprocess communication bus. By adding this daemon layer above
   libfprint, various problems related to multiple applications simulatenously
   competing for fingerprint readers get solved.
   .
   This package provides a PAM module for fingerprint-based authentication
   via fprintd.

has two spelling errors:

  "trough" should be "through"

  "simulatenously" should be "simultaneously"

Some of its debian/control siblings share the second of these.

Cheers,

--Barak.
--
Barak A. Pearlmutter
 Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
 http://www.bcl.hamilton.ie/~barak/


pgpWnejPuOXdP.pgp
Description: PGP signature

Bug#752378: FTBFS: Missing python libraries in B-D-I

[Angel Abad]

Package: awscli
Severity: serious
Tags: patch

Hi, the pacakge FTBFS in a Debian Sid clean chroot, please take
a look to the patch. There is a missing python libraries in package
build depends.

==
ERROR: awscli.testutils (unittest.loader.ModuleImportFailure)
--
Traceback (most recent call last):
  File "/usr/lib/python3.4/unittest/case.py", line 58, in testPartExecutor
yield
  File "/usr/lib/python3.4/unittest/case.py", line 577, in run
testMethod()
  File "/usr/lib/python3.4/unittest/loader.py", line 32, in testFailure
raise exception
ImportError: Failed to import test module: awscli.testutils
Traceback (most recent call last):
  File "/usr/lib/python3.4/unittest/loader.py", line 312, in _find_tests
module = self._get_module_from_name(name)
  File "/usr/lib/python3.4/unittest/loader.py", line 290, in 
_get_module_from_name
__import__(name)
  File 
"/build/buildd/awscli-1.3.18/.pybuild/pythonX.Y_3.4/build/awscli/testutils.py", 
line 44, in 
import six
ImportError: No module named 'six'

Cheers,

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

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru awscli-1.3.18/debian/changelog awscli-1.3.18/debian/changelog
--- awscli-1.3.18/debian/changelog	2014-06-22 16:53:48.0 +0200
+++ awscli-1.3.18/debian/changelog	2014-06-23 09:51:16.0 +0200
@@ -1,3 +1,15 @@
+awscli (1.3.18-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing Build-Depends-Indep, fix FTBFS:
+- python3-six
+- python3-botocore
+- python3-colorama
+- python3-docutils
+- python3-bcdoc
+
+ -- Angel Abad   Mon, 23 Jun 2014 09:50:18 +0200
+
 awscli (1.3.18-1) unstable; urgency=medium
 
   * New upstream release (Closes: #744890)
diff -Nru awscli-1.3.18/debian/control awscli-1.3.18/debian/control
--- awscli-1.3.18/debian/control	2014-01-04 09:19:47.0 +0100
+++ awscli-1.3.18/debian/control	2014-06-23 09:52:01.0 +0200
@@ -6,6 +6,11 @@
 Build-Depends: debhelper (>= 9)
 	, python3
 	, python3-setuptools
+Build-Depends-Indep: python3-six
+, python3-botocore
+, python3-colorama
+, python3-docutils
+, python3-bcdoc
 Standards-Version: 3.9.5
 Homepage: http://aws.amazon.com/cli/
 Vcs-Svn: svn://anonscm.debian.org/python-apps/packages/awscli/trunk/

Bug#752379: x2goclient: Starting a virtualbox machine on the server while in an x2go session freezes x2go

[John Wyzer]

Package: x2goclient
Version: 4.0.2.0-2
Severity: important

When I start a virtualbox machine while in an x2go session (virtualbox is 
running
on the machine I've connected to with x2go), the moment the window of the 
virtual machine opens the x2go session freezes. I can however suspend it and
after resuming the session, everything is fine.



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

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

Versions of packages x2goclient depends on:
ii  libc6   2.19-3
ii  libcups21.7.3-3
ii  libgcc1 1:4.9.0-7
ii  libldap-2.4-2   2.4.39-1
ii  libqt4-network  4:4.8.6+dfsg-2
ii  libqt4-svg  4:4.8.6+dfsg-2
ii  libqtcore4  4:4.8.6+dfsg-2
ii  libqtgui4   4:4.8.6+dfsg-2
ii  libssh-40.6.3-2
ii  libstdc++6  4.9.0-7
ii  libx11-62:1.6.2-2
ii  libxpm4 1:3.5.10-1
ii  nxproxy 2:3.5.0.24-0x2go1+git20140508.472+wheezy.main.1
ii  openssh-client  1:6.5p1-4

Versions of packages x2goclient recommends:
ii  freerdp-x11 1.0.2-4+b1
ii  openssh-server  1:6.5p1-4
ii  rdesktop1.7.1-1

Versions of packages x2goclient suggests:
pn  pinentry-x2go  

-- no debconf information


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

Bug#752380: fvwm: FvwmPager is permanently crashing

[Ďoďo]

Package: fvwm
Version: 1:2.6.5.ds-3
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
1. Clicking on Pager.
2. Restarting Fvwm
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
1. I clicked on Page to switch to another Virtual desktop
2. Or I restarted Fvwm because pager was not there. Sometimes
I need to restart 3-4 times till
the pager stays running.
   * What was the outcome of this action?
Pager disapears. And I do not see it among the running
processes. I observe this problem
already longer time. Sometimes it is frequent and sometimes
just once a month.
   * What outcome did you expect instead?

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


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

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

Versions of packages fvwm depends on:
ii  libc6   2.19-1
ii  libcairo2   1.12.16-2
ii  libfontconfig1  2.11.0-5
ii  libfreetype62.5.2-1
ii  libfribidi0 0.19.6-1
ii  libgdk-pixbuf2.0-0  2.30.7-1
ii  libglib2.0-02.40.0-3
ii  libice6 2:1.0.8-2
ii  libperl4-corelibs-perl  0.003-1
ii  libpng12-0  1.2.50-1
ii  libreadline66.3-6
ii  librplay3   3.3.2-14
ii  librsvg2-2  2.40.2-1
ii  libsm6  2:1.2.1-2
ii  libstroke0  0.5.1-6
ii  libtinfo5   5.9+20140118-1
ii  libx11-62:1.6.2-2
ii  libxcursor1 1:1.1.14-1
ii  libxext62:1.3.2-1
ii  libxft2 2.3.1-2
ii  libxinerama12:1.1.3-1
ii  libxpm4 1:3.5.10-1
ii  libxrender1 1:0.9.8-1
ii  perl5.18.2-4
ii  zlib1g  1:1.2.8.dfsg-1

Versions of packages fvwm recommends:
ii  fvwm-icons20070101-2
ii  libx11-protocol-perl  0.56-6
ii  perl-tk   1:804.032-2

Versions of packages fvwm suggests:
ii  cpp  4:4.8.2-4
pn  fvwm-themes  
ii  m4   1.4.17-4
ii  menu 2.1.46
pn  wm-icons 

-- no debconf information


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

Bug#752366: [php-maint] Bug#752366: php5: Memory leak in FTPS functions results in denial of service

[Ondřej Surý]

Hi Ryan,

thanks for reporting the issue. We have an update queue in
stable-proposed-updates
right now with a bunch of upstream fixes that needs to be processed
first, so we don't
pile updates over updates.

But I will merge fix for your issue into next s-p-u update, ok?

Thanks,
Ondrej

On Mon, Jun 23, 2014, at 04:56, Ryan Underwood wrote:
> Package: php5
> Version: 5.4.4-14+deb7u11
> Severity: important
> 
> php5 stable version has a gaping memory leak in SSL handling which was
> fixed
> upstream.
> 
> http://git.php.net/?p=php-src.git;a=commitdiff;h=0863a0d6a0f740874b4ef8dc732a4ec94949470c
> 
> Without this patch, a process which makes repeated FTP-SSL connections
> will
> eventually consume all resources of the server, not limited by PHP's own
> memory_limit.
> 
> -- System Information:
> Debian Release: 7.5
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 3.14-0.bpo.1-686-pae (SMP w/1 CPU core)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> 
> Versions of packages php5 depends on:
> ii  libapache2-mod-php5  5.4.4-14+deb7u11
> ii  php5-common  5.4.4-14+deb7u11
> 
> php5 recommends no packages.
> 
> php5 suggests no packages.
> 
> -- no debconf information
> 
> ___
> pkg-php-maint mailing list
> pkg-php-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint


-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


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

Bug#752381: initramfs-tools: does not activate logical volume before trying to mount root filesystem on LVM

[Martin Steigerwald]

Package: initramfs-tools
Version: 0.115~bpo70+1
Severity: important

What did I do:

Today I installed backports version of open-vm-dkms and upgraded to most
recent 3.14 backport kernel from a previous version of it I installed due
to using BTRFS with skinny meta data on one partition.


Current results:

After this the machine failed to boot. It didn´t find the root filesystem
by its UUID. I typed "vgchange -ay" in initramfs and then Ctrl-D and then
it booted. This used to work without manual interaction before.

To make it boot consistently I added as a work-around:

mondschein:~> cat /etc/initramfs-tools/scripts/local-top/lvm-manual 
#!/bin/sh

PREREQ="lvm"
prereqs()
{
echo $PREREQ
}

case $1 in
prereqs)
prereqs
exit 0;
esac

. /scripts/functions

log_begin_msg "Activitating logical volumes (as it does not seem to be done 
automatically at the moment)."

vgchange -ay

log_end_msg


which I had handy as I use a similar workaround for enabling BTRFS RAID 1
boot on my laptop, which does not work as default.

This worked after actually chmod'ing +x it :)


Expected results:

Machine boots without manual adaptions to InitRD.


Additional information:

The machine still boots from an Ext4 filesystem. The BTRFS filesystem is
mounted later on by fstab.

There is a lvm and a BTRFS script in InitRD already, but the lvm script did
not seem to work properly:

mondschein:~> lsinitramfs /boot/initrd.img-3.14-0.bpo.1-686-pae | grep script
scripts
scripts/functions
scripts/nfs
scripts/init-bottom
scripts/init-bottom/udev
scripts/init-bottom/ORDER
scripts/local-premount
scripts/local-premount/btrfs
scripts/local-premount/resume
scripts/local-premount/ORDER
scripts/local
scripts/local-top
scripts/local-top/lvm-manual
scripts/local-top/lvm2
scripts/local-top/ORDER
scripts/init-top
scripts/init-top/blacklist
scripts/init-top/keymap
scripts/init-top/udev
scripts/init-top/ORDER
scripts/init-top/all_generic_ide


I thought it was an update to initramfs-tools causing this, but these have
been upgraded last week already:

Start-Date: 2014-06-12  11:46:49
Commandline: apt-get install -t wheezy-backports 
linux-image-3.14-0.bpo.1-686-pae linux-headers-3.14-0.bpo.1-686-pae btrfs-tools
Install: linux-headers-3.14-0.bpo.1-686-pae:i386 (3.14.5-1~bpo70+1), 
linux-image-3.14-0.bpo.1-686-pae:i386 (3.14.5-1~bpo70+1), 
linux-compiler-gcc-4.6-x
86:i386 (3.14.5-1~bpo70+1, automatic), btrfs-tools:i386 (3.14.1-1~bpo70+1), 
liblzo2-2:i386 (2.06-1, automatic), linux-kbuild-3.14:i386 (3.14-1~bpo70+1,
 automatic), linux-headers-3.14-0.bpo.1-common:i386 (3.14.5-1~bpo70+1, 
automatic)
Upgrade: initramfs-tools:i386 (0.109.1, 0.115~bpo70+1)
End-Date: 2014-06-12  11:48:06


And there rebooting the machine worked out of the box.

So maybe something in open-vm-tools or open-vm-dkms from wheezy-backports
interacts with InitRD script stuff in a way that breaks boot. But OTOH
I see no open-vm related scripts in above lsinitramfs output.

Thanks,
Martin

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 13M Jun 23 09:58 /boot/initrd.img-3.14-0.bpo.1-686-pae
-rw-r--r-- 1 root root 11M Jun 23 09:58 /boot/initrd.img-3.2.0-4-686-pae
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.14-0.bpo.1-686-pae 
root=UUID=a8e69cdf-f016-4f07-8d2d-d975881d2095 ro

-- resume
RESUME=/dev/sda2
-- /proc/filesystems
btrfs
ext3
ext2
ext4

-- lsmod
Module  Size  Used by
coretemp   12734  0 
crc32_pclmul   12809  0 
crc32c_intel   12624  0 
vmw_balloon12502  0 
irda   90367  0 
parport_pc 25991  0 
crc_ccitt  12331  1 irda
parport35207  1 parport_pc
aesni_intel17934  0 
vmwgfx142296  0 
ttm59829  1 vmwgfx
aes_i586   16647  1 aesni_intel
xts12583  1 aesni_intel
lrw12686  1 aesni_intel
gf128mul   12834  2 lrw,xts
ablk_helper12508  1 aesni_intel
cryptd 14125  1 ablk_helper
psmouse85040  0 
drm   198349  2 ttm,vmwgfx
evdev  17172  0 
serio_raw  12737  0 
pcspkr 12531  0 
i2c_piix4  12592  0 
i2c_core   23454  2 drm,i2c_piix4
battery12949  0 
processor  27575  0 
button 12824  0 
thermal_sys22946  1 processor
ac 12588  0 
shpchp 30673  0 
ext4  454558  4 
crc16  12327  1 ext4
mbcache12938  1 ext4
jbd2   77040  1 ext4
crc32c 12576  1 
btrfs 852360  1 
xor25716  1 btrfs
raid6_pq   95207  1 btrfs
dm_mod 78695  20 
sg 25573  0 
sd_mod 43628  5 
sr_mod 21563  0 
crc_t10dif 12399  1 sd_mod
c

Bug#752354: perl: trivial test C program fails to compile

[Russ Allbery]

Niko Tyni  writes:

> Thanks for looking at this.

> The probe doesn't actually use anything from the headers, it just
> includes them:

> #include 
> #include 
> #include 
> int main() { return 0; }

> It's not clear to me that this should require libperl linkage?

It's from a static inline function defined in the headers.  See perl.h:

#ifndef PERL_NO_INLINE_FUNCTIONS
/* Static inline funcs that depend on includes and declarations above.
   Some of these reference functions in the perl object files, and some
   compilers aren't smart enough to eliminate unused static inline
   functions, so including this file in source code can cause link errors
   even if the source code uses none of the functions. Hence including these
   can be be suppressed by setting PERL_NO_INLINE_FUNCTIONS. Doing this will
   (obviously) result in unworkable XS code, but allows simple probing code
   to continue to work, because it permits tests to include the perl headers
   for definitions without creating a link dependency on the perl library
   (which may not exist yet).
*/

#  include "inline.h"
#endif

So the solution is to either always link with the Perl flags, not just
compile, or to define that macro in probes.

-- 
Russ Allbery (r...@debian.org)   


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

Bug#752381: initramfs-tools: does not activate logical volume - two obversations

[Martin Steigerwald]

Hi!

I bzr diff on /boot/grub/grub.cfg revealed – but already from last week as I 
upgraded to the newer backport initramfs-tools, where booting still worked
okay:

 menuentry 'Debian GNU/Linux, mit Linux 3.2.0-4-686-pae' --class debian --
class gnu-linux --class gnu --class os {
load_video
insmod gzio
@@ -67,7 +90,7 @@
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root [UUID]
echo'Linux 3.2.0-4-686-pae wird geladen …'
-   linux   /vmlinuz-3.2.0-4-686-pae root=/dev/mapper/mondschein-debian ro  
+   linux   /vmlinuz-3.2.0-4-686-pae root=UUID=[UUID ro  
echo'Initiale Ramdisk wird geladen …'
initrd  /initrd.img-3.2.0-4-686-pae
 }
@@ -79,7 +102,7 @@
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root [UUID]
echo'Linux 3.2.0-4-686-pae wird geladen …'
-   linux   /vmlinuz-3.2.0-4-686-pae root=/dev/mapper/mondschein-debian ro 
single 
+   linux   /vmlinuz-3.2.0-4-686-pae root=UUID=[UUID] ro single 
echo'Initiale Ramdisk wird geladen …'
initrd  /initrd.img-3.2.0-4-686-pae
 }


And:

Booting today also failed with 3.2.0 kernel so the issue seems to have
nothing to do with the newer version of the 3.14 backport kernel.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

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

Bug#752382: /usr/bin/namecheck: namecheck should drop http://developer.berlios.de/

[Neil Muller]

Package: devscripts
Version: 2.14.5
Severity: normal
File: /usr/bin/namecheck
Tags: patch

Dear Maintainer,

developer.berlios.de no longer works as a way for querying project
names, and simply redirects to www.berlios.de. Consequently,
namecheck reports any project name as existing there.

Since berlios.de no longer does code hosting, the site should simply
be dropped.


-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
Not present

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages devscripts depends on:
ii  dpkg-dev 1.17.10
ii  libc62.19-3
ii  perl 5.18.2-4
ii  python3  3.4.1-1
pn  python3:any  

Versions of packages devscripts recommends:
ii  at  3.1.14-1
ii  dctrl-tools 2.23
ii  debian-keyring  2014.04.25
ii  dput0.9.6.4
ii  equivs  2.0.9
ii  fakeroot1.20-3
ii  file1:5.19-1
ii  gnupg   1.4.16-1.1
ii  libdistro-info-perl 0.13
ii  libencode-locale-perl   1.03-1
ii  libjson-perl2.61-1
ii  liblwp-protocol-https-perl  6.04-3
ii  libparse-debcontrol-perl2.005-4
ii  libsoap-lite-perl   1.11-1
ii  liburi-perl 1.60-1
ii  libwww-perl 6.06-1
ii  lintian 2.5.23.1
ii  man-db  2.6.7.1-1
ii  patch   2.7.1-5
ii  patchutils  0.3.3-1
ii  python3-debian  0.1.22
ii  python3-magic   1:5.19-1
ii  sensible-utils  0.0.9
ii  strace  4.5.20-2.3
ii  unzip   6.0-12
ii  wdiff   1.2.2-1
ii  wget1.15-1+b1
ii  xz-utils5.1.1alpha+20120614-2

Versions of packages devscripts suggests:
ii  build-essential  11.6
pn  cvs-buildpackage 
pn  devscripts-el
pn  gnuplot  
ii  gpgv 1.4.16-1.1
ii  heirloom-mailx [mailx]   12.5-2
ii  libauthen-sasl-perl  2.1600-1
pn  libfile-desktopentry-perl
ii  libnet-smtp-ssl-perl 1.01-3
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
pn  libyaml-syck-perl
pn  mutt 
ii  openssh-client [ssh-client]  1:6.6p1-5
ii  svn-buildpackage 0.8.5
pn  w3m  

-- no debconf information


namecheck.patch
Description: Binary data

Bug#752383: ia32-libs: Install silently does not overwrite old /usr/lib32/libGL.so.1 symbolic link

[Clinton Mead]

Package: ia32-libs
Version: 1:0.4
Severity: important

Dear Maintainer,

I have previously installed the nVidia drivers directly from nVidia. I believe
(but am not certain) that they created /usr/lib32/libGL.so.1 as a symbolic link
to /usr/lib32/libGL.so.173.14.09. This seems to link to libGLcore.so.1, which
does not exist on the 304 series of drivers.

The ia32-libs file should probably overwrite this symbolic link, or perhaps
alert the user that it exists and error, instead it just silently doesn't
overwrite and instead leaves the old driver.

Removing the symbolic link and reinstalling ia32-libs fixed the problem, but
only after many hours of debugging.



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

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

Versions of packages ia32-libs depends on:
ii  ia32-libs-i386 1:0.4
ii  multiarch-support  2.13-38+deb7u1

ia32-libs recommends no packages.

Versions of packages ia32-libs suggests:
ii  ia32-libs-gtk  1:0.1

-- no debconf information


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

Bug#750739: apache2-mpm-worker: Can't start with >= 5000 VirtualHosts with 'SSLEngine On' - "AH00016: Configuration Failed". sysctl fs.file-max=512000

[INTEN - Damian S. Kołodziejczyk]

> On Monday 16 June 2014 14:20:27, INTEN - Damian S. Kołodziejczyk
> wrote:
>> error log shows only "AH00016: Configuration Failed"
>
> If you have separate error logs for ssl virtualhosts, please also
> check those for additional error messages.
>

Additional error messages was empty - nothig more.

>> i increased max openfiles (sysctl fs.file-max=512000) becouse
>> i also increased FD_SETSIZE in httpd.
>
> Did you do this to try to fix this issue or was this an unrelated
> change to fix something else? httpd should not use FD_SETSIZE
> internally (though some library used by httpd may).
>

Yes - all libs with httpd required.

>> Normal virtualhosts = 40 000 and working,
>> SSL virtualhosts < 5000 and "AH00016: Configuration Failed"
>
> You could try to start it under "strace -f" and try to see if there is
> some system call that fails shortly before this message is printed.
>
> BTW, you original report said "version 2.2.22-13+deb7u1", but the
> AH00016 tag was only introduced in 2.4. Which version do you use
> exactly?
>

Strace shows only info about too many open files - so i increase it.
Nothing more points.

I checked also on version 2.4 - error also occurs and apparently
this is the version pasted. Today, I went back to 2.2.


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

Bug#752354: perl: trivial test C program fails to compile

[Niko Tyni]

On Mon, Jun 23, 2014 at 01:19:28AM -0700, Russ Allbery wrote:
> Niko Tyni  writes:
> 
> > Thanks for looking at this.
> 
> > The probe doesn't actually use anything from the headers, it just
> > includes them:

> It's from a static inline function defined in the headers.  See perl.h:
> 
> #ifndef PERL_NO_INLINE_FUNCTIONS
> /* Static inline funcs that depend on includes and declarations above.
>Some of these reference functions in the perl object files, and some
>compilers aren't smart enough to eliminate unused static inline
>functions, so including this file in source code can cause link errors
>even if the source code uses none of the functions. Hence including these
>can be be suppressed by setting PERL_NO_INLINE_FUNCTIONS. Doing this will
>(obviously) result in unworkable XS code, but allows simple probing code
>to continue to work, because it permits tests to include the perl headers
>for definitions without creating a link dependency on the perl library
>(which may not exist yet).
> */
> 
> #  include "inline.h"
> #endif
> 
> So the solution is to either always link with the Perl flags, not just
> compile, or to define that macro in probes.

Ah, that makes sense. Thanks for educating me! (and apologies for not taking
the time to dig this up myself.)

So it's indeed xchat-gnome that needs to be fixed. Will file a proper
report tonight (but anybody is naturally free to beat me to it.)
-- 
Niko


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

Bug#727296: exempi: diff for NMU version 2.2.1-1.1

[Michael Biebl]

Am 23.06.2014 02:31, schrieb Wookey:
> tags 727296 + pending
> thanks
> 
> Dear maintainer,
> 
> This bug has been pending for several months, and needs fixing for new
> ports such as arm64 
> (http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid),
> so I've prepared an NMU (versioned as 2.2.1-1.1) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.
> 
> Discussion on debian-devel revealed consensus that the right way to
> ensure successful builds on all new architectures was to autoreconf
> packages, so that method has been used to fix this bug. This works for
> all arches, even those that need libtool changes, and will continue to
> work into the future without an update as each new arch comes along.
> (Discussion at
> https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
> starting at
> https://lists.debian.org/debian-devel/2014/04/msg00342.html )
> 
> As you can see this works fine on your package, and is a very simple
> patch.
> 

Thanks for the patch, looks fine. Sorry for not getting to it earlier.

Feel free to upload directly without delay.

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

Bug#749577: Dolphin: unable tio create files on cifs mount - dsik full

[Jim Scadden]

tags 749577 + upstream
forwarded 749577 https://bugs.kde.org/show_bug.cgi?id=334776
thanks

On Wed, May 28, 2014 at 11:38:34AM +0200, rollopack wrote:
> Package: libkio5
> Version: 4:4.13.1-1
> Severity: important
> 
> Dear Maintainer,
> 
> The version 4.13.1-1 of the package introduce the KDE bug 334776 wich cause
> dolphin to report the error "disk full" error on file create.
> 
> Coping and old version of libkio.so.5 (libkio.so.5.13.0 from ubuntu) resolve
> the bug

Pending 4.13.2+ as per upstream bug:

Git commit 9a8426ae2ed35ac900b89a623618fc158d24ee6a by Tomáš Trnka. 
Committed on 25/05/2014 at 14:12.
Pushed by ttrnka into branch 'KDE/4.13'.

Revert "Avoid unnecessary automounting in KDiskFreeSpaceInfo::freeSpaceInfo"

This reverts commit 6246e99b43f3d1a9e15d563fbb5e173ed50ba5e5.

It breaks KIO on CIFS mounts as the check for automounts copied over 
from frameworks/kfileitem.cpp isDirectoryMounted() apparently matches 
CIFS as well (and for some weird reason KIO checks for available space 
before trying to copy files).

We'll probably have to return to v1 of the abovementioned commit, i.e. 
checking for "autofs" explicitly. However, more testing is apparently 
necessary to avoid further nasty surprises.

REVIEW: 117044
FIXED-IN: 4.13.2

-- 

Jim Scadden


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

Bug#752384: qa.debian.org: sourceforge.net redirector doesn't detect new upstream versions

[Gabriele Giacone]

Package: qa.debian.org
Severity: normal

http://qa.debian.org/cgi-bin/watch?pkg=sweethome3d

package: sweethome3d
debian-uversion: 4.3+dfsg
debian-mangled-uversion: 4.3
upstream-version: 4.3
upstream-url: 
http://qa.debian.org/watch/sf.php/sweethome3d/SweetHome3D-4.3-src.zip
status: up to date
checked at: Sun Jun 22 06:03:02 2014

4.4 is out and tarball available on sf site since 10 days.


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

Bug#748547: input-utils: FTBFS caused by make 4.0

[Paul Wise]

forcemerge 750264 748547
reassign 750264 make 4.0-1
affects 750264 + input-utils
thanks

#750264 and #748547 are the same bug but 748547 has the wrong title.

The same version of input-utils builds fine on wheezy, it looks like
this bug is caused by Debian switching to make 4.0.

The problematic file:

$ cat Make.config 
-e LIB  := lib
$ grep -C2 Make.config GNUmakefile
# config
-include Make.config
include mk/Variables.mk

On jessie (make 4.0-8):

$ make -j1 distclean
Make.config:1: *** empty variable name.  Stop.

On wheezy (make 3.81-8.2):

$ make -j1 distclean
checking for libdir name ... lib
rm -f *.o mk/*.dep
rm -f Make.config
rm -f lsinput input-events input-kbd lircd.conf EV.h REL.h ABS.h MSC.h LED.h 
SND.h REP.h KEY.h BTN.h BUS.h SW.h *~ xpm/*~ *.bak

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


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

Bug#752283: [Pkg-acpi-devel] Bug#752283: downgrade to acpi-support* 0.141-2 fixed suspend

[Michael Meskes]

On Mon, Jun 23, 2014 at 09:33:44AM +0200, Gijs Hillenius wrote:
> I had previously purged only acpi-fakekey acpi-support so, perhaps the
> issue is in acpi-support-base
> 
> 
> Looking at the difference between 
> acpi-support-base 0.141-2 and 0.141-3
> 
> I noticed that something changed in power-funcs
> ( /usr/share/acpi-support/power-funcs)

You coild try just using the old power-funcs file with the new acpi-support 
package.

> 0.141.2:
> { print unix_user; exit (0); } /x11-display = '\'$display.0\''/ { print 
> unix_user; exit (0);}')
> 
> 0.141.3:
> { print unix_user; exit (0); }')

This is misleading as you don't show the other x11-display pattern recognition
that was changed to, hopefully, catch both cases. However, that might fail, any
debugging of this function would be greatly appreciated. It did work correctly
in my tests, though.

Michael

-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at gmail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL


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

Bug#752171: pcp: Build depends on autoconf

[Xilin Sun]

Control: tag -1 patch

Dear maintainer,

Please consider applying attached patch to resolve "Build depends on autoconf".

Regards,
Xilin
diff -Nru pcp-3.9.6/debian/changelog pcp-3.9.6+nmu1/debian/changelog
--- pcp-3.9.6/debian/changelog	2014-06-19 00:34:07.0 +
+++ pcp-3.9.6+nmu1/debian/changelog	2014-06-23 07:49:08.0 +
@@ -1,3 +1,10 @@
+pcp (3.9.6+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix pcp FTBFS due to dependency on autoconf 
+
+ -- Xilin Sun   Mon, 23 Jun 2014 07:48:28 +
+
 pcp (3.9.6) unstable; urgency=low
 
   * Resolve FTBFS on build systems using systemd (closes: #746994)
diff -Nru pcp-3.9.6/debian/control pcp-3.9.6+nmu1/debian/control
--- pcp-3.9.6/debian/control	2014-06-19 00:35:33.0 +
+++ pcp-3.9.6+nmu1/debian/control	2014-06-23 07:49:37.0 +
@@ -4,7 +4,7 @@
 Homepage: http://www.performancecopilot.org
 Maintainer: PCP Development Team 
 Uploaders: Nathan Scott , Anibal Monsalve Salazar 
-Build-Depends: bison, flex, gawk, procps, pkg-config, debhelper (>= 5), perl (>= 5.6), libreadline-dev | libreadline5-dev | libreadline-gplv2-dev, chrpath, libbsd-dev [kfreebsd-any], libkvm-dev [kfreebsd-any], python-all, python-all-dev, libnspr4-dev, libnss3-dev, libsasl2-dev, libmicrohttpd-dev, libavahi-common-dev, libqt4-dev, autotools-dev
+Build-Depends: bison, flex, gawk, procps, pkg-config, debhelper (>= 6), perl (>= 5.6), libreadline-dev | libreadline5-dev | libreadline-gplv2-dev, chrpath, libbsd-dev [kfreebsd-any], libkvm-dev [kfreebsd-any], python-all, python-all-dev, libnspr4-dev, libnss3-dev, libsasl2-dev, libmicrohttpd-dev, libavahi-common-dev, libqt4-dev, autotools-dev, autoconf
 #Architecture-dependent -- Build-Depends: libibumad-dev, libibmad-dev
 Standards-Version: 3.9.3
 X-Python-Version: >= 2.6

Bug#752384: qa.debian.org: sourceforge.net redirector doesn't detect new upstream versions

[Paul Wise]

On Mon, Jun 23, 2014 at 4:56 PM, Gabriele Giacone <1o5g4...@gmail.com> wrote:

> upstream-url: 
> http://qa.debian.org/watch/sf.php/sweethome3d/SweetHome3D-4.3-src.zip
...
> 4.4 is out and tarball available on sf site since 10 days.

The sf.net redirector is based on the ftp.heanet.ie sourceforge
mirror, which appears to be out of date. The HEAnet mirror is used
because it provides rsync access that we need to easily get a full
list of all files on SourceForge.

ftp://ftp.heanet.ie/mirrors/sourceforge/s/sw/sweethome3d/SweetHome3D-source/

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


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

Bug#609378: Incorrect use of memset count/value

[Fabian Greffrath]

# actually fixed in 1.0+dfsg-3 which was left UNRELEASED
fixed 609378 1.1-1
thanks


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

Bug#750739: apache2-mpm-worker: Can't start with >= 5000 VirtualHosts with 'SSLEngine On' - "AH00016: Configuration Failed". sysctl fs.file-max=512000

[Stefan Fritsch]

On Mon, 23 Jun 2014, INTEN - Damian S. Kołodziejczyk wrote:
> Strace shows only info about too many open files - so i increase it.
> Nothing more points.

Have you looked at APACHE_ULIMIT_MAX_FILES in /etc/apache2/envvars? Maybe 
you just need to set a higher value there?

Bug#752384: HEAnet sourceforge mirror is outdated

[Paul Wise]

Hi HEAnet mirror operators,

The Debian project[1] QA group[2] is currently relying[3] on this
command to detect new versions of software that is packaged in Debian:

rsync -Pvan --log-file=/dev/null --list-only ftp.heanet.ie::sourceforge

We received a report that the HEAnet mirror of SourceForge files is at
least 10 days out of date. For example, compare these two URLs,
version 4.4 is missing from the HEAnet mirror:

ftp://ftp.heanet.ie/mirrors/sourceforge/s/sw/sweethome3d/SweetHome3D-source/
https://sourceforge.net/projects/sweethome3d/files/SweetHome3D-source/
https://bugs.debian.org/752384

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


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

Bug#751417: linux-image-3.2.0-4-5kc-malta: no SIGKILL after prctl(PR_SET_SECCOMP, 1, ...) on MIPS

[Luis Henriques]

On Thu, Jun 12, 2014 at 09:21:41PM +0100, Ben Hutchings wrote:
> On Thu, 2014-06-12 at 20:36 +0100, Ben Hutchings wrote:
> > Control: tag -1 security upstream patch moreinfo
> > Control: severity -1 grave
> > Control: found -1 3.14.5-1
> 
> Aurelien Jarno pointed out this appears to be fixed upstream in 3.15:
> 
> commit 137f7df8cead00688524c82360930845396b8a21
> Author: Markos Chandras 
> Date:   Wed Jan 22 14:40:00 2014 +
> 
> MIPS: asm: thread_info: Add _TIF_SECCOMP flag
> 
> It looks like this can be cherry-picked cleanly onto stable branches for
> 3.13 and 3.14.  For 3.11 and 3.12, it will need trivial adjustment.
> 
> For branches older than 3.11, this needs to be cherry-picked first:
> 
> commit e7f3b48af7be9f8007a224663a5b91340626fed5
> Author: Ralf Baechle 
> Date:   Wed May 29 01:02:18 2013 +0200
> 
> MIPS: Cleanup flags in syscall flags handlers.
> 
> Ben.
>

Thank you, I'm queuing this for the 3.11 kernel.

Cheers,
--
Luís

> > On Thu, 2014-06-12 at 16:19 +, Plamen Alexandrov wrote:
> > > Package: src:linux
> > > Version: 3.2.51-1
> > > Severity: normal
> > > 
> > > Under MIPS the system call prctl(PR_SET_SECCOMP, 1, ...) does not behave 
> > > as expected.
> > > According to the manual page, after calling it with 1 as a second 
> > > argument, any consecutive system calls other than read(), write(), 
> > > _exit() and sigreturn() should result in the delivery of SIGKILL. 
> > > However, under MIPS any consecutive system call behaves as if 
> > > prctl(PR_SET_SECCOMP, 1, ...) was never called.
> > > 
> > > Here is a simple example that can be used to reproduce the bug:
> > > 
> > > plamen@debian-mips:/tmp$ id
> > > uid=1000(plamen) gid=1000(user) groups=1000(user)
> > > plamen@debian-mips:/tmp$ cat prctl.c 
> > > #include 
> > > #include 
> > > #include 
> > > 
> > > int main(void)
> > > {
> > >   if (prctl(PR_SET_SECCOMP, 1, 0, 0, 0) != 0)
> > >   return 0;
> > >   uid_t uid = getuid();
> > >   printf("%u\n", (unsigned)uid);
> > >   return 0;
> > > }
> > > plamen@debian-mips:/tmp$ gcc prctl.c -o prctl
> > > plamen@debian-mips:/tmp$ ./prctl 
> > > 1000
> > > 
> > > There is no change if I replace
> > >   if (prctl(PR_SET_SECCOMP, 1, 0, 0, 0) != 0)
> > > with
> > >   if (prctl(PR_SET_SECCOMP, SECCOMP_MODE_STRICT, 0, 0, 0) != 0)
> > > and I add #include 
> > 
> > Indeed, I see no check for seccomp on the MIPS syscall 'fast path'.  The
> > seccomp check appears to be done on the 'slow path' which is used only
> > if tracing or audit is also enabled for the task.  If I run the above
> > program under strace, it is killed as expected.
> > 
> > Could you test whether the attached patches fix this?  (Instructions for
> > rebuilding the Debian kernel package with patches can be found at
> > .
> >   These patches apply to 'wheezy'.)
> > 
> > Ben.
> > 
> 
> -- 
> Ben Hutchings
> The program is absolutely right; therefore, the computer must be wrong.


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

Bug#751021: dpkg: Same error on 1.17.10 (i386)

[Guillaume Seren]

Package: dpkg
Version: 1.17.10
Followup-For: Bug #751021

Dear Maintener,
got the same behavior here, this is when I install a new kernel :

$ sudo dpkg -i 
../linux-image-3.16.0-rc2-201406230951_3.16.0-rc2-201406230951-10.00.Custom_i386.deb
 
../linux-headers-3.16.0-rc2-201406230951_3.16.0-rc2-201406230951-10.00.Custom_i386.deb
Sélection du paquet linux-image-3.16.0-rc2-201406230951 précédemment 
désélectionné.
(Lecture de la base de données... 195578 fichiers et répertoires déjà 
installés.)
Preparing to unpack 
.../linux-image-3.16.0-rc2-201406230951_3.16.0-rc2-201406230951-10.00.Custom_i386.deb
 ...
Examining /etc/kernel/preinst.d/
Done.
Unpacking linux-image-3.16.0-rc2-201406230951 
(3.16.0-rc2-201406230951-10.00.Custom) ...
Sélection du paquet linux-headers-3.16.0-rc2-201406230951 précédemment 
désélectionné.
Preparing to unpack 
.../linux-headers-3.16.0-rc2-201406230951_3.16.0-rc2-201406230951-10.00.Custom_i386.deb
 ...
Unpacking linux-headers-3.16.0-rc2-201406230951 
(3.16.0-rc2-201406230951-10.00.Custom) ...
Paramétrage de linux-image-3.16.0-rc2-201406230951 
(3.16.0-rc2-201406230951-10.00.Custom) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.16.0-rc2-201406230951 /boot/vmlinuz-3.16.0-rc2-201406230951
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
3.16.0-rc2-201406230951 /boot/vmlinuz-3.16.0-rc2-201406230951
update-initramfs: Generating /boot/initrd.img-3.16.0-rc2-201406230951
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.16.0-rc2-201406230951 
/boot/vmlinuz-3.16.0-rc2-201406230951
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 
3.16.0-rc2-201406230951 /boot/vmlinuz-3.16.0-rc2-201406230951
Création du fichier de configuration GRUB…
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29519: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29519: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29527: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29527: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29535: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29535: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29543: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29543: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29587: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29587: /usr/sbin/grub-probe
Image Linux trouvée : /boot/vmlinuz-3.16.0-rc2-201406230951
Image mémoire initiale trouvée : /boot/initrd.img-3.16.0-rc2-201406230951
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29687: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29687: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29696: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29696: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29704: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29704: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29712: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 29712: /usr/sbin/grub-probe
Image Linux trouvée : /boot/vmlinuz-3.16.0-rc2-201406230927
Image mémoire initiale trouvée : /boot/initrd.img-3.16.0-rc2-201406230927
Image Linux trouvée : /boot/vmlinuz-3.16.0-rc1-201406201740+
Image mémoire initiale trouvée : /boot/initrd.img-3.16.0-rc1-201406201740+
Image Linux trouvée : /boot/vmlinuz-3.16.0-rc1-2014061610
Image mémoire initiale trouvée : /boot/initrd.img-3.16.0-rc1-2014061610
Image Linux trouvée : /boot/vmlinuz-3.14-1-686-pae
Image mémoire initiale trouvée : /boot/initrd.img-3.14-1-686-pae
Image Linux trouvée : /boot/vmlinuz-3.2.0-4-686-pae
Image mémoire initiale trouvée : /boot/initrd.img-3.2.0-4-686-pae
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 30409: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on vgs invocation. 
Parent PID 30409: /usr/sbin/grub-probe
File descriptor 6 (/var/lib/dpkg/triggers/Unincorp) leaked on lvs invocation. 
Parent PID 30528

Bug#752385: DDPO: should display the sauerbraten package in non-free not contrib

[Markus Koschany]

Package: qa.debian.org
Severity: normal

Hi,

in order to complete the sauerbraten transition this source package had
to be moved from section contrib to non-free. The version in unstable
and testing is now available in section "non-free" while the versions
in oldstable and stable are in contrib. DDPO does not seem to take
this change into account and still displays the sauerbraten package
under section "contrib". It would be nice if DDPO would track
unstable/testing in this regard.

Regards,

Markus


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

Bug#752386: bzr: commit to sftp repo is broken

[Tim Marston]

Package: bzr
Version: 2.6.0+bzr6595-1
Severity: important

Dear Maintainer,

Committing to a bzr repository over sftp appears to now be broken.  (It
wasn't broken a month ago, or so.)

This is quite reproducable:

  ~$ bzr init foo
  ~$ bzr co sftp://localhost/~/foo bar
  ~$ cd bar
  bar$ touch a
  bar$ bzr add a
  bar$ bzr ci -m ""
  **BOOM!**

It seems that bzr+ssh:// URLs still work, though.

Here's the Python dump:


bzr: ERROR: exceptions.TypeError: Expected unicode or bytes, got


Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line 930,
  in exception_to_return_code
return the_callable(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line
  1121, in run_bzr
ret = run(*run_argv)
  File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line 673,
  in run_argv_aliases
return self.run(**all_cmd_args)
  File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line 697,
  in run
return self._operation.run_simple(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/cleanup.py", line 136,
  in run_simple
self.cleanups, self.func, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/cleanup.py", line 166,
  in _do_with_cleanups
result = func(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/builtins.py", line
  3687, in run
lossy=lossy)
  File "/usr/lib/python2.7/dist-packages/bzrlib/decorators.py", line
  218, in write_locked
result = unbound(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/workingtree_4.py", line
  218, in commit
result = WorkingTree.commit(self, message, revprops, *args,
  **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/decorators.py", line
  218, in write_locked
result = unbound(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/mutabletree.py", line
  211, in commit
*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/commit.py", line 290,
  in commit
lossy=lossy)
  File "/usr/lib/python2.7/dist-packages/bzrlib/cleanup.py", line 132,
  in run
self.cleanups, self.func, self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/cleanup.py", line 166,
  in _do_with_cleanups
result = func(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/commit.py", line 455,
  in _commit
self._update_branches(old_revno, old_revid, new_revno)
  File "/usr/lib/python2.7/dist-packages/bzrlib/commit.py", line 489,
  in _update_branches
self.branch, new_revno, self.rev_id, lossy=self._lossy)
  File "/usr/lib/python2.7/dist-packages/bzrlib/branch.py", line 1072,
  in import_last_revision_info_and_tags
self.fetch(source, revid)
  File "/usr/lib/python2.7/dist-packages/bzrlib/decorators.py", line
  218, in write_locked
result = unbound(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/branch.py", line 716,
  in fetch
return InterBranch.get(from_branch, self).fetch(last_revision,
  limit=limit)
  File "/usr/lib/python2.7/dist-packages/bzrlib/decorators.py", line
  218, in write_locked
result = unbound(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/branch.py", line 3226,
  in fetch
fetch_spec=fetch_spec)
  File "/usr/lib/python2.7/dist-packages/bzrlib/vf_repository.py", line
  1268, in fetch
find_ghosts=find_ghosts, fetch_spec=fetch_spec)
  File "/usr/lib/python2.7/dist-packages/bzrlib/decorators.py", line
  218, in write_locked
result = unbound(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/vf_repository.py", line
  2585, in fetch
find_ghosts=find_ghosts)
  File "/usr/lib/python2.7/dist-packages/bzrlib/fetch.py", line 77, in
  __init__
self.__fetch()
  File "/usr/lib/python2.7/dist-packages/bzrlib/fetch.py", line 104, in
  __fetch
self._fetch_everything_for_search(search_result)
  File "/usr/lib/python2.7/dist-packages/bzrlib/fetch.py", line 132, in
  _fetch_everything_for_search
stream, from_format, [])
  File "/usr/lib/python2.7/dist-packages/bzrlib/vf_repository.py", line
  2038, in insert_stream
self.target_repo.start_write_group()
  File "/usr/lib/python2.7/dist-packages/bzrlib/repository.py", line
  782, in start_write_group
self._start_write_group()
  File "/usr/lib/python2.7/dist-packages/bzrlib/repofmt/pack_repo.py",
  line 1724, in _start_write_group
self._pack_collection._start_write_group()
  File "/usr/lib/python2.7/dist-packages/bzrlib/repofmt/pack_repo.py",
  line 1531, in _start_write_group
file_mode=self.repo.bzrdir._get_file_mode())
  File
  "/usr/lib/python2.7/dist-packages/bzrlib/repofmt/groupcompress_repo.py",
  line 160, in __init__
self._writer.begin()
  File "/usr/lib/python2.7/dist-packages/bzrlib/pack.py", line 132, in
  begin
self.write_func(self._serialiser.begin())
  File "/usr/lib/python2.7/dist-packages/bzrlib/pack.py", line 135, in
  write_func
self._write_func(bytes)
 

Bug#752387: ITP: r-cran-gsl -- GNU R wrapper for the GNU Scientific Library

[Andreas Tille]

Package: wnpp
Severity: wishlist
Owner: Andreas Tille 

* Package name: r-cran-gsl
  Version : 1.9-10
  Upstream Author : Robin K. S. Hankin 
* URL : http://cran.r-project.org/web/packages/gsl/
* License : GPL
  Programming Lang: R
  Description : GNU R wrapper for the GNU Scientific Library
 An R wrapper for the special functions and quasi random number
 generators of the GNU Scientific Library
 (http://www.gnu.org/software/gsl/).


Remark: Since this GNU R package is used in the test suite of package
r-cran-spatstat and can enhance the spead of some specific functions
in this package drastically it will be packaged for Debian as well.
The packaging is done by the Debian Science team at

   
svn://anonscm.debian.org/debian-science/packages/R/trunk/packages/r-cran-gsl/trunk/


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

Bug#727521: xmlrpc-epi: diff for NMU version 0.54.2-1.1

[Wookey]

tags 727521 + patch
tags 727521 + pending
thanks

This bug has been pending for some time, and needs fixing for new
ports including arm64, which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

I've prepared an NMU for xmlrpc-epi (versioned as 0.54.2-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

As you can see this works fine on your package, and is a very simple
patch. 

diff -u xmlrpc-epi-0.54.2/debian/rules xmlrpc-epi-0.54.2/debian/rules
--- xmlrpc-epi-0.54.2/debian/rules
+++ xmlrpc-epi-0.54.2/debian/rules
@@ -20,6 +20,7 @@
 
 config.status:
 	dh_testdir
+	dh_autoreconf
 	./configure --build=$(DEB_BUILD_GNU_TYPE) --includedir=/usr/include/xmlrpc-epi \
 		--prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info \
 		CFLAGS="$(CFLAGS)" LDFLAGS="-Wl,-z,defs" $(DEB_CONFIGURE_EXTRA_FLAGS)
@@ -36,6 +37,7 @@
 	dh_testdir
 	dh_testroot
 	[ ! -f Makefile ] || $(MAKE) distclean
+	dh_autoreconf_clean
 	dh_clean build_stamp
 
 install: build
diff -u xmlrpc-epi-0.54.2/debian/changelog xmlrpc-epi-0.54.2/debian/changelog
--- xmlrpc-epi-0.54.2/debian/changelog
+++ xmlrpc-epi-0.54.2/debian/changelog
@@ -1,3 +1,10 @@
+xmlrpc-epi (0.54.2-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (Closes: #727521)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 20:52:18 +0800
+
 xmlrpc-epi (0.54.2-1) unstable; urgency=low
 
   * New upstream release (Closes:#620437)
diff -u xmlrpc-epi-0.54.2/debian/control xmlrpc-epi-0.54.2/debian/control
--- xmlrpc-epi-0.54.2/debian/control
+++ xmlrpc-epi-0.54.2/debian/control
@@ -3,7 +3,7 @@
 Maintainer: Robin Cornelius 
 Uploaders: Paul TBBle Hampson 
 Homepage: http://xmlrpc-epi.sourceforge.net/
-Build-Depends: debhelper (>= 8.1.3~), autotools-dev, libexpat1-dev, pkg-config
+Build-Depends: debhelper (>= 8.1.3~), autotools-dev, libexpat1-dev, pkg-config, dh-autoreconf
 Standards-Version: 3.9.2
 Section: libs
 Vcs-GIT: git://github.com/robincornelius/xmlrpc-epi-debian.git

Bug#727394: libbind: diff for NMU version 6.0-1.1

[Wookey]

tags 727394 + patch
tags 727394 + pending
thanks

Dear maintainer,

This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for libbind (versioned as 6.0-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.


diff -u libbind-6.0/debian/rules libbind-6.0/debian/rules
--- libbind-6.0/debian/rules
+++ libbind-6.0/debian/rules
@@ -8,6 +8,7 @@
 	touch $@
 
 clean:
+	dh_autotools-dev_restoreconfig
 	dh clean 
 	find . -name '*.o' -delete
 
@@ -18,6 +19,7 @@
 	dh binary-arch
 
 override_dh_auto_configure:
+	dh_autotools-dev_updateconfig
 	dh_auto_configure -- -with-libtool
 
 binary: binary-arch binary-indep
diff -u libbind-6.0/debian/changelog libbind-6.0/debian/changelog
--- libbind-6.0/debian/changelog
+++ libbind-6.0/debian/changelog
@@ -1,3 +1,10 @@
+libbind (6.0-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (closes: #727394)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 17:00:32 +0800
+
 libbind (6.0-1) unstable; urgency=low
 
   * Initial release; closes: #527985.
diff -u libbind-6.0/debian/control libbind-6.0/debian/control
--- libbind-6.0/debian/control
+++ libbind-6.0/debian/control
@@ -1,7 +1,7 @@
 Source: libbind
 Priority: extra
 Maintainer: Robert S. Edmonds 
-Build-Depends: debhelper (>= 7.0.50)
+Build-Depends: debhelper (>= 7.0.50), autotools-dev
 Standards-Version: 3.8.1
 Section: libs
 Homepage: http://www.isc.org/software/libbind

Bug#752389: dpkg-query: error: --listfiles needs a valid package name but 'libc6' is not: ambiguous package name 'libc6' with more than one installed instance

[Peter Gervai]

Package: libc6
Version: 2.19-3
Severity: normal

If irrelevant feel free to close.

Preparing to unpack .../libc6_2.19-3_amd64.deb ...
De-configuring libc6:i386 (2.18-7) ...
Checking for services that may need to be restarted...
Checking init scripts...
Unpacking libc6:amd64 (2.19-3) over (2.18-7) ...
Preparing to unpack .../archives/libc6_2.19-3_i386.deb ...
Checking for services that may need to be restarted...
Checking init scripts...
dpkg-query: error: --listfiles needs a valid package name but 'libc6' is not: 
ambiguous package name 'libc6' with more than one installed instance

Use --help for help about querying packages.
Unpacking libc6:i386 (2.19-3) over (2.18-7) ...


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

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash


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

Bug#752390: /usr/include/sys/_callout.h:56:2: error: unknown type name 'sbintime_t'

[Hector Oron]

Package: kfreebsd-kernel-headers
Version: 10.0~5
Severity: serious

Hello,

  sbintime_t is not defined at /usr/include/sys/_callout.h causing build error, 
at least for GNU GDB package, as found at:
  < 
https://buildd.debian.org/status/fetch.php?pkg=gdb&arch=kfreebsd-amd64&ver=7.7.1-2&stamp=1403257387
 >

  This error is preventing GNU GDB from entering testing/jessie release.

  Apparently /usr/include/sys/_callout.h is out dated, when looking to:
  < http://code.metager.de/source/xref/freebsd/sys/sys/_callout.h >

  Could you please update package?

Regards

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

Kernel: Linux 3.13-1-686-pae (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


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

Bug#728004: xblast-tnt: diff for NMU version 2.10.4-3.1

[Wookey]

tags 728004 + patch
tags 728004 + pending
thanks

Dear maintainer,

This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

I've prepared an NMU for xblast-tnt (versioned as 2.10.4-3.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

As you can see this works fine on your package, and is a very simple
patch. 

Regards.
diff -u xblast-tnt-2.10.4/debian/changelog xblast-tnt-2.10.4/debian/changelog
--- xblast-tnt-2.10.4/debian/changelog
+++ xblast-tnt-2.10.4/debian/changelog
@@ -1,3 +1,10 @@
+xblast-tnt (2.10.4-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (closes: #728004)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 17:24:50 +0800
+
 xblast-tnt (2.10.4-3) unstable; urgency=low
 
   * debian/menu: Adapt to new menu policy: s/Arcade/Action/.
diff -u xblast-tnt-2.10.4/debian/rules xblast-tnt-2.10.4/debian/rules
--- xblast-tnt-2.10.4/debian/rules
+++ xblast-tnt-2.10.4/debian/rules
@@ -42,6 +42,8 @@
 build: build-stamp
 build-stamp:
 	# mini binaries
+	cp -f /usr/share/misc/config.sub .
+	cp -f /usr/share/misc/config.guess .
 	./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
 		--prefix=/usr --mandir=\$${prefix}/share/man --with-x --disable-nls \
 		--enable-sound --with-otherdatadir=/usr/share/games/xblast-tnt \
diff -u xblast-tnt-2.10.4/debian/control xblast-tnt-2.10.4/debian/control
--- xblast-tnt-2.10.4/debian/control
+++ xblast-tnt-2.10.4/debian/control
@@ -2,7 +2,7 @@
 Section: games
 Priority: optional
 Maintainer: Gerfried Fuchs 
-Build-Depends: libxt-dev
+Build-Depends: libxt-dev, autotools-dev
 Standards-Version: 3.7.2
 
 Package: xblast-tnt

Bug#752391: enigmail: icedove crashes with SIGSEGV when sending emails unencrypted while for one recpient a key is present

[Michael Strobel]

Package: enigmail
Version: 2:1.6+git0.20140323-2
Severity: important

Dear Maintainer,

after upgrading to icedove 31 it crashed when sending an email to a person who
has a gpg key and one who has not. The dialog about key management pops up and
after some time icedove crashed. I tried disabling all extensions and ran
icedove only with enigmail. I'll add a gdb trackeback.

Best
Michael


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

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

Versions of packages enigmail depends on:
ii  gnupg1.4.16-1.1
ii  icedove  31.0~b1-2
ii  libc62.19-3

Versions of packages enigmail recommends:
ii  gnupg-agent  2.0.23-1

enigmail suggests no packages.

-- no debconf information

*** /home/michael/icedove.log
michael@debian ~ $ /usr/lib/icedove/run-mozilla.sh -g /usr/lib/icedove/icedove-
bin
MOZILLA_FIVE_HOME=/usr/lib/icedove
  LD_LIBRARY_PATH=/usr/lib/icedove:/usr/lib/icedove/plugins:/usr/lib/icedove
DISPLAY=:0
DYLD_LIBRARY_PATH=/usr/lib/icedove:/usr/lib/icedove
 LIBRARY_PATH=
   SHLIB_PATH=/usr/lib/icedove:/usr/lib/icedove
  LIBPATH=/usr/lib/icedove:/usr/lib/icedove
   ADDON_PATH=
  MOZ_PROGRAM=/usr/lib/icedove/icedove-bin
  MOZ_TOOLKIT=
moz_debug=1
 moz_debugger=
moz_debugger_args=
/usr/bin/gdb  --args /usr/lib/icedove/icedove-bin
GNU gdb (Debian 7.7.1-2) 7.7.1
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.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/icedove/icedove-bin...Reading symbols from
/usr/lib/debug//usr/lib/icedove/icedove-bin...done.
done.
(gdb) run
Starting program: /usr/lib/icedove/icedove-bin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

(process:9929): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size
== 0' failed

(icedove:9929): GLib-GObject-WARNING **: Attempt to add property GnomeProgram
::sm-connect after class was initialised

(icedove:9929): GLib-GObject-WARNING **: Attempt to add property GnomeProgram
::show-crash-dialog after class was initialised

(icedove:9929): GLib-GObject-WARNING **: Attempt to add property
GnomeProgram::display after class was initialised

(icedove:9929): GLib-GObject-WARNING **: Attempt to add property GnomeProgram
::default-icon after class was initialised
warning: Corrupted shared library list: 0x7fffe5a21000 != 0x7fffe5a15000
[New Thread 0x7fffe2d8c700 (LWP 9935)]
[New Thread 0x7fffe16ff700 (LWP 9936)]
[New Thread 0x7fffe07f2700 (LWP 9937)]
[New Thread 0x7fffdfff1700 (LWP 9938)]
[New Thread 0x7fffdf133700 (LWP 9939)]
[New Thread 0x7fffddf32700 (LWP 9942)]
[New Thread 0x7fffdd731700 (LWP 9943)]
[New Thread 0x76da6700 (LWP 9944)]
[New Thread 0x7fffdccff700 (LWP 9945)]
[New Thread 0x7fffdbbff700 (LWP 9946)]
[calBackendLoader] Using libical backend at
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-
a41df1933103}/components/libical.manifest
enigmail.js: Registered components
[New Thread 0x7fffb49ff700 (LWP 9947)]
[New Thread 0x7fffb43ff700 (LWP 9948)]
[New Thread 0x7fffb3bfe700 (LWP 9949)]
[New Thread 0x7fffb33fd700 (LWP 9950)]
[New Thread 0x7fffb22ff700 (LWP 9951)]
[New Thread 0x7fffe0e9e700 (LWP 9952)]
[New Thread 0x7fffdf7f0700 (LWP 9953)]
[New Thread 0x7fffdc4fe700 (LWP 9954)]
[New Thread 0x7fffdb3fe700 (LWP 9955)]
[Thread 0x7fffdbbff700 (LWP 9946) exited]
[Thread 0x7fffb33fd700 (LWP 9950) exited]
[New Thread 0x7fffb13ff700 (LWP 9956)]
[New Thread 0x7fffdbbff700 (LWP 9957)]
[New Thread 0x7fffb33fd700 (LWP 9958)]
[Thread 0x7fffb3bfe700 (LWP 9949) exited]
[Thread 0x7fffdbbff700 (LWP 9957) exited]
[New Thread 0x7fffb3bfe700 (LWP 9959)]
[New Thread 0x7fffdbbff700 (LWP 9960)]
[Thread 0x7fffdbbff700 (LWP 9960) exited]
[Thread 0x7fffb33fd700 (LWP 9958) exited]
[New Thread 0x7fffdbbff700 (LWP 9961)]
[New Thread 0x7fffb33fd700 (LWP 9962)]
[Thread 0x7fffb3bfe700 (LWP 9959) exited]
[Thread 0x7fffdbbff700 (LWP 9961) exited]
[New Thread 0x7fffb3bfe700 (LWP 9963)]
[Thread 0x7fffb33fd700 (LWP 9962) exited]
[New Thread 0x7fffb33fd700 (LWP 9964)]
[Thread 0x7fffb3bfe700 (LWP 9963) exited]
mimeVerify.jsm: module initialized
[New Thread 0x7fffb3bfe700 (LWP 9965)]
[Thread 0x7fff

Bug#534508: daemontools: setuidgid should initialize the supplementary groups

[Gerrit Pape]

On Thu, May 29, 2014 at 01:14:12PM +0200, Carlos Alberto Lopez Perez wrote:
> Hi,
> 
> This bite me recently.
> 
> I'm attaching a debdiff with the patch from Huaqing, which I tested and
> verified to work as expected. I also updated the manpage.
> 
> 
> Could you upload this please? If you don't have time I can do an NMU (if
> you think the attached debdiff is OK)

Hi,

I don't agree with this change, as I actually want to keep daemontools
in Debian as close to upstream as possible.  There are alternatives you
can use, like runit, perp, s6, ...

HTH, Gerrit.


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

Bug#752392: O: fpm2 -- password manager with GTK+ 2.x GUI

[Tobias Quathamer]

Package: wnpp
Severity: normal

I don't use fpm2 anymore, and upstream seems to be inactive. Therefore,
I'm orphaning the package.

If nobody adopts this package in the next months, I'll request the
removal before our next release.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#749978: #749978: guayadeque: Please update to use wxwidgets3.0

[Olly Betts]

On Mon, Jun 23, 2014 at 12:50:11PM +0300, Damyan Ivanov wrote:
> /tmp/buildd/guayadeque-0.3.7~ds0/src/ListView.h:160:5: error: 'wxImageList' 
> does not name a type
>  wxImageList *   m_ImageList;
>  ^

For this (and the similar errors for other missing classes) you probably
just need to explicitly include the appropriate wx/.h header which
declares the missing class.

Not sure about the other issues off the top of my head.

Cheers,
Olly


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

Bug#752295: gdb: FTBFS on kfreebsd

[Hector Oron]

Hello,

On Sun, Jun 22, 2014 at 11:59:59AM +0200, Ivo De Decker wrote:
> package: gdb
> version: 7.7.1-1
> severity: serious
> 
> Hi,
> 
> The gdb uploads of version 7.7.1 FTBFS on kfreebsd, blocking migration to
> testing.
> 
> https://buildd.debian.org/status/logs.php?pkg=gdb&ver=7.7.1-2&suite=sid

  This is caused by kfreebsd kernel headers being out dated, nothing to do with 
GNU GDB itself. I have opened #752390 to fix the current situation. Once that 
bug is fixed, GNU GDB will need to be rescheduled for a build.

Regards,
-- 
  Hector Oron


signature.asc
Description: Digital signature

Bug#726495: sendfile: diff for NMU version 2.1b.20080616-5.3

[Wookey]

tags 726495 + pending
thanks

Dear maintainer,

This bug has been pending for several months, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for sendfile (versioned as 2.1b.20080616-5.3)
and uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

As this package does not use debhelper and requests minimal NMU
changes the fix just copies in updated config.{sub,guess} rather than
the more generic re-autoconfing. (Discussion on thread starting at
https://lists.debian.org/debian-devel/2014/04/msg00342.html )

diff -u sendfile-2.1b.20080616/debian/rules sendfile-2.1b.20080616/debian/rules
--- sendfile-2.1b.20080616/debian/rules
+++ sendfile-2.1b.20080616/debian/rules
@@ -32,6 +32,8 @@
 endif
 
 build:
+	cp -f /usr/share/misc/config.sub  develop/
+	cp -f /usr/share/misc/config.guess develop/
 	test -f develop/config.cache || ./makeconfig CONFIG=/etc BINDIR=/usr/bin MANDIR=/usr/share/man SERVERDIR=/usr/bin
 	perl -i -pe 's/undef\s+ENABLE_MULTIPROTOCOL/define ENABLE_MULTIPROTOCOL/' src/globals.h
 	$(MAKE) all
diff -u sendfile-2.1b.20080616/debian/changelog sendfile-2.1b.20080616/debian/changelog
--- sendfile-2.1b.20080616/debian/changelog
+++ sendfile-2.1b.20080616/debian/changelog
@@ -1,3 +1,10 @@
+sendfile (2.1b.20080616-5.3) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (Closes: #726495)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 16:46:19 +0800
+
 sendfile (2.1b.20080616-5.2) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u sendfile-2.1b.20080616/debian/control sendfile-2.1b.20080616/debian/control
--- sendfile-2.1b.20080616/debian/control
+++ sendfile-2.1b.20080616/debian/control
@@ -2,7 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: Martin Schulze 
-Build-Depends: libreadline-dev
+Build-Depends: libreadline-dev, autotools-dev
 Standards-Version: 3.5.2.0
 
 Package: sendfile

Bug#727409: libharu: diff for NMU version 2.2.1-1.1

[Wookey]

tags 727409 + patch
tags 727409 + pending
thanks

Dear maintainer,

This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for libharu (versioned as 2.2.1-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

As you can see this works fine on this package, and is a very simple
patch.

Cheers
diff -Nru libharu-2.2.1/debian/changelog libharu-2.2.1/debian/changelog
--- libharu-2.2.1/debian/changelog	2011-08-31 13:52:03.0 +0100
+++ libharu-2.2.1/debian/changelog	2014-06-23 00:11:53.0 +0100
@@ -1,3 +1,10 @@
+libharu (2.2.1-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (closes: #727409)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 20:03:51 +0800
+
 libharu (2.2.1-1) unstable; urgency=low
 
   * update to upstream 2.2.1
diff -Nru libharu-2.2.1/debian/control libharu-2.2.1/debian/control
--- libharu-2.2.1/debian/control	2011-08-31 13:51:31.0 +0100
+++ libharu-2.2.1/debian/control	2014-06-05 13:03:44.0 +0100
@@ -1,7 +1,7 @@
 Source: libharu
 Priority: optional
 Maintainer: Johan Van de Wauw 
-Build-Depends: debhelper (>= 7.0.50~), libpng-dev, libz-dev
+Build-Depends: debhelper (>= 7.0.50~), libpng-dev, libz-dev, dh-autoreconf
 Standards-Version: 3.9.2
 Section: libs
 Homepage: http://www.libharu.org
diff -Nru libharu-2.2.1/debian/rules libharu-2.2.1/debian/rules
--- libharu-2.2.1/debian/rules	2011-08-31 13:51:31.0 +0100
+++ libharu-2.2.1/debian/rules	2014-06-05 13:03:31.0 +0100
@@ -1,4 +1,4 @@
 #!/usr/bin/make -f
 %:
-	dh  $@
+	dh  $@ --with autoreconf
 

Bug#529462: libsidplay: diff for NMU version 1.36.59-5.1

[Wookey]

tags 529462 + patch
tags 529462 + pending
thanks

Dear maintainer,

This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for libsidplay (versioned as 1.36.59-5.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

As you can see this works fine on this package, and is a very simple
patch. 

Cheers
diff -u libsidplay-1.36.59/debian/changelog libsidplay-1.36.59/debian/changelog
--- libsidplay-1.36.59/debian/changelog
+++ libsidplay-1.36.59/debian/changelog
@@ -1,3 +1,10 @@
+libsidplay (1.36.59-5.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (Closes: #529462)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 20:30:23 +0800
+
 libsidplay (1.36.59-5) unstable; urgency=low
 
   * Fix SID_CHECK_IOS_BIN in acinclude.m4 and configure (closes: #454870).
diff -u libsidplay-1.36.59/debian/control libsidplay-1.36.59/debian/control
--- libsidplay-1.36.59/debian/control
+++ libsidplay-1.36.59/debian/control
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Laszlo Boszormenyi (GCS) 
 Standards-Version: 3.7.3
-Build-Depends: debhelper (>> 4.0.0), patch
+Build-Depends: debhelper (>> 4.0.0), patch, dh-autoreconf
 
 Package: libsidplay1
 Section: libs
diff -u libsidplay-1.36.59/debian/rules libsidplay-1.36.59/debian/rules
--- libsidplay-1.36.59/debian/rules
+++ libsidplay-1.36.59/debian/rules
@@ -10,6 +10,7 @@
 build: build-stamp
 build-stamp:
 	dh_testdir debian/rules src
+	dh_autoreconf
 # well, ./configure isn't interactive here and doesn't take long, so it's
 # carried out in order to assist building the package for people with other
 # architectures and compiler environments
@@ -41,6 +42,7 @@
 	[ ! -f Makefile ] || $(MAKE) distclean
 	rm -f config.log
 	rm -f conftest*
+	dh_autoreconf_clean
 	dh_clean
 
 # Build architecture-independent files here.

Bug#727287: libesmtp: diff for NMU version 1.0.6-1.1

[Wookey]

tags 727287 + pending
thanks

Dear maintainer,

This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for libesmtp (versioned as 1.0.6-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

As you can see this works fine on this package, and is a very simple
patch. 

Cheers.
diff -Nru libesmtp-1.0.6/debian/changelog libesmtp-1.0.6/debian/changelog
--- libesmtp-1.0.6/debian/changelog	2010-08-16 00:07:50.0 +0100
+++ libesmtp-1.0.6/debian/changelog	2014-06-21 16:37:23.0 +0100
@@ -1,3 +1,10 @@
+libesmtp (1.0.6-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add dh-autoreconf in build to support new architectures (Closes: #727287)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 19:47:37 +0800
+
 libesmtp (1.0.6-1) unstable; urgency=low
 
   * New upstream release
diff -Nru libesmtp-1.0.6/debian/control libesmtp-1.0.6/debian/control
--- libesmtp-1.0.6/debian/control	2010-08-15 23:19:43.0 +0100
+++ libesmtp-1.0.6/debian/control	2014-06-05 12:47:27.0 +0100
@@ -6,7 +6,8 @@
 	quilt (>= 0.46-7~),
 	libltdl3-dev,
 	libssl-dev,
-	autotools-dev
+	autotools-dev,
+	dh-autoreconf
 Standards-Version: 3.9.1
 Homepage: http://www.stafford.uklinux.net/libesmtp/
 Vcs-Git: git://git.debian.org/collab-maint/libesmtp.git
diff -Nru libesmtp-1.0.6/debian/rules libesmtp-1.0.6/debian/rules
--- libesmtp-1.0.6/debian/rules	2010-08-15 23:53:38.0 +0100
+++ libesmtp-1.0.6/debian/rules	2014-06-05 12:46:53.0 +0100
@@ -3,7 +3,7 @@
 export DH_VERBOSE=1
 
 %:
-	dh --with quilt $@
+	dh --with quilt $@ --with autoreconf
 
 override_dh_auto_configure:
 	dh_auto_configure -- --with-auth-plugin-dir="/usr/lib/esmtp" --enable-etrn

Bug#727499: rudecgi: diff for NMU version 5.0.0-1.1

[Wookey]

tags 727499 + patch
tags 727499 + pending
thanks

Dear maintainer,

This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for rudecgi (versioned as 5.0.0-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

As you can see this works fine on this package, and is a very simple
patch. 

Cheers
diff -Nru rudecgi-5.0.0/debian/changelog rudecgi-5.0.0/debian/changelog
--- rudecgi-5.0.0/debian/changelog	2012-03-13 17:42:49.0 +
+++ rudecgi-5.0.0/debian/changelog	2014-06-23 00:18:05.0 +0100
@@ -1,5 +1,12 @@
+rudecgi (5.0.0-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (Closes: #727499)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 20:41:52 +0800
+
 rudecgi (5.0.0-1) unstable; urgency=low
 
-  * Initial release (Closes: #658347)  
+  * Initial release (Closes: #658347)
 
  -- Medhamsh V   Wed, 01 Feb 2012 14:36:50 +0530
diff -Nru rudecgi-5.0.0/debian/control rudecgi-5.0.0/debian/control
--- rudecgi-5.0.0/debian/control	2012-03-15 06:46:25.0 +
+++ rudecgi-5.0.0/debian/control	2014-06-05 13:41:18.0 +0100
@@ -1,7 +1,7 @@
 Source: rudecgi
 Priority: optional
 Maintainer: Medhamsh V 
-Build-Depends: debhelper (>= 9), autotools-dev
+Build-Depends: debhelper (>= 9), autotools-dev, dh-autoreconf
 Standards-Version: 3.9.2
 Section: libs
 Homepage: http://www.rudeserver.com/cgiparser/index.html
diff -Nru rudecgi-5.0.0/debian/rules rudecgi-5.0.0/debian/rules
--- rudecgi-5.0.0/debian/rules	2012-03-16 20:44:29.0 +
+++ rudecgi-5.0.0/debian/rules	2014-06-05 13:41:08.0 +0100
@@ -5,7 +5,7 @@
 #export DH_VERBOSE=1
 
 %:
-	dh $@
+	dh $@ --with autoreconf
 
 override_dh_installchangelogs:
 	dh_installchangelogs ChangeLog

Bug#727339: ccze: diff for NMU version 0.2.1-2.1

[Wookey]

tags 727339 + patch
tags 727339 + pending
thanks

Dear maintainer,

This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for ccze (versioned as 0.2.1-2.1) and uploaded
it to DELAYED/7. Please feel free to tell me if I should delay it
longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

However this package does not use debhelper so re-autoconfing is not
such a clean change as just updating config.{sub,guess}, thus I have
only done the simple fix on this package. I'm happy to change it to a
more future-proof reautoconf if you prefer.

Cheers.
diff -u ccze-0.2.1/debian/changelog ccze-0.2.1/debian/changelog
--- ccze-0.2.1/debian/changelog
+++ ccze-0.2.1/debian/changelog
@@ -1,3 +1,10 @@
+ccze (0.2.1-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (closes: #727339)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 16:28:32 +0800
+
 ccze (0.2.1-2) unstable; urgency=low
 
   * Add myself as Maintainer, as Gergely seems to be MIA
diff -u ccze-0.2.1/debian/rules ccze-0.2.1/debian/rules
--- ccze-0.2.1/debian/rules
+++ ccze-0.2.1/debian/rules
@@ -17,6 +17,8 @@
 
 config.status: configure
 	test -e debian/control
+	cp -f /usr/share/misc/config.sub .
+	cp -f /usr/share/misc/config.guess .
 	./configure --prefix=/usr --sysconfdir=/etc \
   --mandir=/usr/share/man \
   --build=${BGT} --host=${HGT} \
diff -u ccze-0.2.1/debian/control ccze-0.2.1/debian/control
--- ccze-0.2.1/debian/control
+++ ccze-0.2.1/debian/control
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Stephen Gran 
 Standards-Version: 3.7.2
-Build-Depends: libpcre3-dev, libncurses5-dev
+Build-Depends: libpcre3-dev, libncurses5-dev, autotools-dev
 
 Package: ccze
 Architecture: any

Bug#528810: libdjconsole: diff for NMU version 0.1.3-1.1

[Wookey]

tags 528810 + patch
tags 528810 + pending
thanks

Dear maintainer,

This bug has been pending for 5 years, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for libdjconsole (versioned as 0.1.3-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

As you can see this works fine on this package, and is a very simple
patch. 

Regards.
diff -u libdjconsole-0.1.3/debian/changelog libdjconsole-0.1.3/debian/changelog
--- libdjconsole-0.1.3/debian/changelog
+++ libdjconsole-0.1.3/debian/changelog
@@ -1,3 +1,10 @@
+libdjconsole (0.1.3-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Using dh-autoreconf during the build to support new arches (Closes: #528810)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 19:44:08 +0800
+
 libdjconsole (0.1.3-1) unstable; urgency=low
 
   * New upstream release
diff -u libdjconsole-0.1.3/debian/rules libdjconsole-0.1.3/debian/rules
--- libdjconsole-0.1.3/debian/rules
+++ libdjconsole-0.1.3/debian/rules
@@ -13,6 +13,7 @@
 
 config.status: configure
 	dh_testdir
+	dh_autoreconf
 	./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info --sysconfdir=/etc
 
 build: build-stamp
@@ -28,6 +29,7 @@
 	rm -f build-stamp
 	[ ! -f Makefile ] || $(MAKE) distclean
 	rm -f stamp-h2
+	dh_autoreconf_clean
 	dh_clean
 
 install: build
diff -u libdjconsole-0.1.3/debian/control libdjconsole-0.1.3/debian/control
--- libdjconsole-0.1.3/debian/control
+++ libdjconsole-0.1.3/debian/control
@@ -1,7 +1,7 @@
 Source: libdjconsole
 Priority: optional
 Maintainer: Adrien Cunin 
-Build-Depends: debhelper (>= 7), autotools-dev, pkg-config, libusb-dev
+Build-Depends: debhelper (>= 7), autotools-dev, pkg-config, libusb-dev, dh-autoreconf
 Standards-Version: 3.7.3
 Section: libs
 

Bug#727419: libnova: diff for NMU version 0.14.0-2.1

[Wookey]

tags 727419 + patch
tags 727419 + pending
thanks

Dear maintainer,

This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for libnova (versioned as 0.14.0-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

As you can see this works fine on this package, and is a very simple
patch. 

Cheers.
diff -Nru libnova-0.14.0/debian/changelog libnova-0.14.0/debian/changelog
--- libnova-0.14.0/debian/changelog	2012-03-25 13:51:48.0 +0100
+++ libnova-0.14.0/debian/changelog	2014-06-23 00:12:48.0 +0100
@@ -1,3 +1,10 @@
+libnova (0.14.0-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (closes: #727419)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 20:27:12 +0800
+
 libnova (0.14.0-2) unstable; urgency=low
 
   * Team upload. Upload to unstable.
diff -Nru libnova-0.14.0/debian/control libnova-0.14.0/debian/control
--- libnova-0.14.0/debian/control	2012-03-18 09:29:59.0 +
+++ libnova-0.14.0/debian/control	2014-06-05 13:26:58.0 +0100
@@ -2,7 +2,7 @@
 Section: libs
 Priority: optional
 Maintainer: Debian Krap Maintainers 
-Build-Depends: debhelper (>= 9), autotools-dev
+Build-Depends: debhelper (>= 9), autotools-dev, dh-autoreconf
 Standards-Version: 3.9.3
 Uploaders: Sune Vuorela 
 Homepage: http://libnova.sourceforge.net/
diff -Nru libnova-0.14.0/debian/rules libnova-0.14.0/debian/rules
--- libnova-0.14.0/debian/rules	2012-03-18 09:46:28.0 +
+++ libnova-0.14.0/debian/rules	2014-06-05 13:26:45.0 +0100
@@ -1,7 +1,7 @@
 #!/usr/bin/make -f
 
 %:
-	dh $@
+	dh $@ --with autoreconf
 
 override_dh_auto_test:
 	dh_auto_test

Bug#727322: argtable2: diff for NMU version 12-1.1

[Wookey]

tags 727322 + patch
tags 727322 + pending
thanks

Dear maintainer,

This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for argtable2 (versioned as 12-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

As you can see this works fine on this package, and is a very simple
patch. 

Cheers.
diff -Nru argtable2-12/debian/changelog argtable2-12/debian/changelog
--- argtable2-12/debian/changelog	2010-08-22 14:34:10.0 +0100
+++ argtable2-12/debian/changelog	2014-06-23 00:08:15.0 +0100
@@ -1,3 +1,10 @@
+argtable2 (12-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (Closes: #727322)
+
+ -- Chen Baozi   Tue, 03 Jun 2014 14:48:59 +0800
+
 argtable2 (12-1) unstable; urgency=low
 
   * New upstream version
diff -Nru argtable2-12/debian/control argtable2-12/debian/control
--- argtable2-12/debian/control	2010-08-22 14:38:05.0 +0100
+++ argtable2-12/debian/control	2014-06-03 07:48:47.0 +0100
@@ -1,7 +1,7 @@
 Source: argtable2
 Priority: optional
 Maintainer: Shachar Shemesh 
-Build-Depends: debhelper (>= 8), autotools-dev
+Build-Depends: debhelper (>= 8), autotools-dev, dh-autoreconf
 Standards-Version: 3.9.1.0
 Homepage: http://argtable.sourceforge.net
 Section: libs
diff -Nru argtable2-12/debian/rules argtable2-12/debian/rules
--- argtable2-12/debian/rules	2010-08-22 14:32:27.0 +0100
+++ argtable2-12/debian/rules	2014-06-03 07:48:10.0 +0100
@@ -8,7 +8,7 @@
 major=0
 
 %:
-	dh $@
+	dh $@ --with autoreconf
 
 clean:
 	[ ! -f Makefile ] || $(MAKE) distclean

Bug#727404: libee: diff for NMU version 0.4.1-1.1

[Wookey]

tags 727404 + patch
tags 727404 + pending
thanks

Dear maintainer,

This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for libee (versioned as 0.4.1-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

As you can see this works fine on this package, and is a very simple
patch. 

Cheers.
diff -Nru libee-0.4.1/debian/changelog libee-0.4.1/debian/changelog
--- libee-0.4.1/debian/changelog	2012-06-18 20:55:53.0 +0100
+++ libee-0.4.1/debian/changelog	2014-06-23 00:11:19.0 +0100
@@ -1,3 +1,10 @@
+libee (0.4.1-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (closes: #727404)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 20:59:37 +0800
+
 libee (0.4.1-1) unstable; urgency=low
 
   * Imported Upstream version 0.4.1
diff -Nru libee-0.4.1/debian/control libee-0.4.1/debian/control
--- libee-0.4.1/debian/control	2012-06-18 20:54:02.0 +0100
+++ libee-0.4.1/debian/control	2014-06-05 13:59:17.0 +0100
@@ -5,7 +5,8 @@
 autotools-dev,
 pkg-config,
 libxml2-dev,
-libestr-dev
+libestr-dev,
+dh-autoreconf
 Standards-Version: 3.9.3
 Section: libs
 Homepage: http://libee.sourceforge.net/
diff -Nru libee-0.4.1/debian/rules libee-0.4.1/debian/rules
--- libee-0.4.1/debian/rules	2012-06-18 20:47:02.0 +0100
+++ libee-0.4.1/debian/rules	2014-06-05 13:59:30.0 +0100
@@ -12,4 +12,4 @@
 export DEB_BUILD_HARDENING=1
 
 %:
-	dh $@ 
+	dh $@ --with autoreconf

Bug#732824: judy: diff for NMU version 1.0.5-1.1

[Wookey]

tags 732824 + pending
thanks

Dear maintainer,

This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for judy (versioned as 1.0.5-1.1) and uploaded
it to DELAYED/7. Please feel free to tell me if I should delay it
longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

As you can see this works fine on this package, and is a very simple
patch. 

Cheers.
diff -u judy-1.0.5/debian/changelog judy-1.0.5/debian/changelog
--- judy-1.0.5/debian/changelog
+++ judy-1.0.5/debian/changelog
@@ -1,3 +1,10 @@
+judy (1.0.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (Closes: #732824)
+
+ -- Chen Baozi   Tue, 03 Jun 2014 15:14:54 +0800
+
 judy (1.0.5-1) unstable; urgency=low
 
   * Fixed alignment issue, (Closes: #401124)
diff -u judy-1.0.5/debian/control judy-1.0.5/debian/control
--- judy-1.0.5/debian/control
+++ judy-1.0.5/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Troy Heber 
 Uploaders:
-Build-Depends: debhelper (>> 4.0.0)
+Build-Depends: debhelper (>> 4.0.0), dh-autoreconf
 Standards-Version: 3.7.2.2
 
 Package: libjudy-dev
diff -u judy-1.0.5/debian/rules judy-1.0.5/debian/rules
--- judy-1.0.5/debian/rules
+++ judy-1.0.5/debian/rules
@@ -21,6 +21,7 @@
 configure-stamp:
 	dh_testdir
 	# Add here commands to configure the package.
+	dh_autoreconf
 	./configure --prefix=/usr --mandir=/usr/share/man
 
 	touch configure-stamp
@@ -44,6 +45,7 @@
 	# Add here commands to clean up after the build process.
 	-$(MAKE) distclean
 
+	dh_autoreconf_clean
 	dh_clean
 
 install: build

Bug#752393: smokeping: fails to build docs with pod2man due to unquoted slash

[Rowan Thorpe]

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


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

Bug#752045: [ITR] templates://dictionaries-common/{dictionaries-common.templates}

[Agustin Martin]

On Mon, Jun 23, 2014 at 07:07:07AM +0200, Christian PERRIER wrote:
> Dear Debian maintainer,
> 
> The Debian internationalisation team and the Debian English
> localisation team will soon begin the review of the debconf
> templates used in dictionaries-common.
> 
> This review takes place for all packages that use debconf to interact with
> users and its aims are:
> - to improve the use of English in all debconf templates;
> - to make the wording of debconf templates more consistent;
> - to encourage more translations of templates.
...
> The first step of the process is to review the debconf source
> template file(s) of dictionaries-common. This review will start on Thursday, 
> June 26, 2014, or
> as soon as you acknowledge this mail with an agreement for us to
> carry out this process.
... 
> If you approve this process, please let us know by replying to this
> mail. If some work in progress on your side would conflict with such a
> rewrite (such as adding or removing debconf templates), please say so,
> and we will defer the review to later in the development cycle.

Hi,

Please proceed with the process, thanks.

Note that a newer templates file was uploaded (attached to this message),
with all previous changes reverted and new stuff put in a new template
"dictionaries-common/debconf_database_corruption". It is temporarily tagged
as non-translatable to not interfer with this review and to inhibit
possible translations outside this process.

I do not remember if old stuff was ever reviewed, feel free to have a look
at it.

Please find newer templates file attached.

Thank you for your help to improve package quality.

Regards,

-- 
Agustin
Template: dictionaries-common/debconf_database_corruption
Type: note
Description: Possible debconf database corruption
 Empty value for debconf question "${question}" but elements installed
 for class "${class}":
 .
  Choices_dictcom: "${installed_elements}"
  Choices_debconf: "${choices_value}"
  Owners/error: "${shared_owners}"
 .
 This can be related to debconf database corruption.
 See "/usr/share/doc/dictionaries-common/README.problems", section
 "Debconf database corruption".
 .
 In this case, running "/usr/share/debconf/fix_db.pl" can help to put
 debconf database in a consistent state.
 .
 Question may be asked after this message to try leaving the
 dictionaries system in a (provisionally) working state.

Template: dictionaries-common/invalid_debconf_value
Type: note
_Description: An invalid debconf value [${value}] has been found
 It does not correspond to any installed package in the system.
 .
 That is usually caused by problems at some time during packages
 installation, where the package providing [${value}] was selected for
 installation but finally not installed because of errors in other
 packages.
 .
 To fix this error, reinstall (or install) the package that provides
 the missing value.  Then, if you don't want this package on
 your system, remove it, which will also remove its debconf entries.
 Menu to be shown after this message will try to leave the system in a
 working state until then.
 .
 This error message can also appear during ispell dictionary or wordlist
 renaming (e.g., wenglish-> wamerican). In this case it is harmless and
 everything will be fixed after you select your default in the menu(s)
 shown after this message.

Template: dictionaries-common/default-ispell
Type: select
Choices-C: ${choices}, Manual symlink setting
__Choices: ${echoices}, Manual symlink setting
_Description: System default ispell dictionary:
 Please indicate which dictionary ispell should use as system-wide
 default when no other spell-checking dictionary is specified.
 .
 This sets up the /usr/lib/ispell/default.aff and
 /usr/lib/ispell/default.hash symlinks, as well as ispell's global
 ispell-wrapper and Emacs defaults.
 .
 Use "Manual symlink setting" if you want to handle the symlinks
 yourself. In this case ispell will have no global ispell-wrapper or
 Emacs defaults.
 .
 The default ispell dictionary can be changed at any time by running
 "select-default-ispell".

Template: dictionaries-common/default-wordlist
Type: select
Choices-C: ${choices}, Manual symlink setting
__Choices: ${echoices}, Manual symlink setting
_Description: System default wordlist:
 Please indicate which wordlist the "/usr/share/dict/words" symlink
 should point to. This will provide a simple list of dictionary words
 for basic spell-checking and word searches. Use "Manual symlink
 setting" if you want to handle this symlink yourself.
 .
 The default wordlist can be changed at any time by running
 "select-default-wordlist".

Template: dictionaries-common/move_old_usr_dict
Type: boolean
Default: true
_Description: Move non-FHS stuff under /usr/dict to /usr/dict-pre-FHS?
 Some stuff under /usr/dict that is not a symlink to /usr/share/dict has
 been detected in your system. /usr/share/dict is now the FHS location for
 those files. Everything under /usr/dict can be moved to /usr/dict-pre-FHS

Bug#727448: libxcrypt: diff for NMU version 1:2.4-3.1

[Wookey]

tags 727448 + patch
tags 727448 + pending
thanks

Dear maintainer,

This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for libxcrypt (versioned as 1:2.4-3.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

As you can see this works fine on this package, and is a very simple
patch. 


Regards.
diff -u libxcrypt-2.4/debian/changelog libxcrypt-2.4/debian/changelog
--- libxcrypt-2.4/debian/changelog
+++ libxcrypt-2.4/debian/changelog
@@ -1,3 +1,10 @@
+libxcrypt (1:2.4-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh-autoreconf in build to support new architectures (closes: #727448)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 20:38:32 +0800
+
 libxcrypt (1:2.4-3) unstable; urgency=low
 
   * QA upload (see #679703).  Skipping 1:2.4-2 to avoid archive filename
diff -u libxcrypt-2.4/debian/rules libxcrypt-2.4/debian/rules
--- libxcrypt-2.4/debian/rules
+++ libxcrypt-2.4/debian/rules
@@ -35,6 +35,7 @@
 
 config.status: configure
 	dh_testdir
+	dh_autoreconf
 	# Add here commands to configure the package.
 	CFLAGS="$(CFLAGS)" ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info
 
@@ -64,7 +65,7 @@
 	#cp -f /usr/share/misc/config.guess config.guess
 endif
 
-
+	dh_autoreconf_clean
 	dh_clean 
 
 install: build
diff -u libxcrypt-2.4/debian/control libxcrypt-2.4/debian/control
--- libxcrypt-2.4/debian/control
+++ libxcrypt-2.4/debian/control
@@ -2,7 +2,7 @@
 Section: libs
 Priority: optional
 Maintainer: Debian QA Group 
-Build-Depends: debhelper (>= 4.0.0), quilt
+Build-Depends: debhelper (>= 4.0.0), quilt, dh-autoreconf
 Standards-Version: 3.6.0
 
 Package: libxcrypt-dev

Bug#534817: liblip: diff for NMU version 2.0.0-1.2

[Wookey]

tags 534817 + patch
tags 534817 + pending
thanks

Dear maintainer,

This bug has been pending for some years, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).

So I've prepared an NMU for liblip (versioned as 2.0.0-1.2) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html

However this package does not use debhelper, so adding autoreconf
support could be quite intrusive for an NMU, so I have just done the
simple update of config.{sub,guess} and autotools-dev build-dep. 

Regards.
diff -u liblip-2.0.0/debian/rules liblip-2.0.0/debian/rules
--- liblip-2.0.0/debian/rules
+++ liblip-2.0.0/debian/rules
@@ -6,6 +6,8 @@
 
 build:
 	$(checkdir)
+	cp -f /usr/share/misc/config.sub .
+	cp -f /usr/share/misc/config.guess .
 	./configure --prefix=/usr --enable-shared
 	$(MAKE) install prefix=$(CURDIR)/shared
 	[ ! -f Makefile ] || $(MAKE) distclean
@@ -21,7 +23,7 @@
 	-rm -f config.log config.cache
 	-rm -f `find . -name "*~"`
 	-rm -rf tnt shared static
-	-rm -rf debian/tmp debian/files* core debian/substvars
+	-rm -rf debian/tmp debian/files* core debian/substvars debian/debhelper.log
 	-rm -rf debian/liblip2 debian/liblip-dev
 
 binary-indep: checkroot build
diff -u liblip-2.0.0/debian/control liblip-2.0.0/debian/control
--- liblip-2.0.0/debian/control
+++ liblip-2.0.0/debian/control
@@ -2,7 +2,7 @@
 Section: math
 Priority: optional
 Maintainer: Juan Esteban Monsalve Tobon 
-Build-Depends: libtnt-dev (>= 1.2.5-3)
+Build-Depends: libtnt-dev (>= 1.2.5-3), autotools-dev
 Homepage: http://www.deakin.edu.au/~gleb/lip.html
 Standards-Version: 3.7.2
 
diff -u liblip-2.0.0/debian/changelog liblip-2.0.0/debian/changelog
--- liblip-2.0.0/debian/changelog
+++ liblip-2.0.0/debian/changelog
@@ -1,3 +1,10 @@
+liblip (2.0.0-1.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add autotools-dev for updated config.{sub,guess} (Closes: #534817)
+
+ -- Chen Baozi   Thu, 05 Jun 2014 16:22:13 +0800
+
 liblip (2.0.0-1.1) unstable; urgency=low
 
   * Non-maintainer upload.

Bug#749890: fixed in 0.18.1~rc0-1 ?

[David Bremner]

Hi Jakub;

If you have a chance, could you check if this bug is fixed by
0.18.1~rc0-1 (in experimental)? The support for single message mboxes
is re-enabled there.

d


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

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

[Rowan Thorpe]

Tags: patch

Attached is a debdiff for several smokeping bugs.

--
Rowan Thorpe
PGP fingerprint:
 BB0A 0787 C0EE BDD8 7F97  3D30 49F2 13A5 265D CCBD

"There is a great difference between worry and concern. A worried person sees
a problem, and a concerned person solves a problem."
 - Harold Stephens
diff -Nru smokeping-2.6.9/debian/changelog smokeping-2.6.9/debian/changelog
--- smokeping-2.6.9/debian/changelog2013-03-16 18:07:00.0 +0200
+++ smokeping-2.6.9/debian/changelog2014-06-23 13:25:34.0 +0300
@@ -1,3 +1,20 @@
+smokeping (2.6.9-1~exp0.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use dh_autoreconf to avoid errors about "missing xx" and to allow
+rebuilding after first build (Closes: #724471)
+  * use dh_auto_configure rather than ./configure in rules, to only
+override specified flags, not all
+  * add patches:
+* fix-paths-inside-executables - hardcode paths inside executables
+  (Closes: #707225)
+* fix-pod-escaping - quote-protect a slash in a pod-link
+  (Closes: #752393)
+
+  * bump Standards-Version to 3.9.5
+
+ -- Rowan Thorpe   Fri, 20 Jun 2014 13:13:26 +0300
+
 smokeping (2.6.9-1~exp0) experimental; urgency=high
 
   * New upstream release to properly fix CVE-2012-0790 (Closes: #659899)
diff -Nru smokeping-2.6.9/debian/control smokeping-2.6.9/debian/control
--- smokeping-2.6.9/debian/control  2013-03-16 18:07:00.0 +0200
+++ smokeping-2.6.9/debian/control  2014-06-23 12:29:14.0 +0300
@@ -3,10 +3,10 @@
 Priority: extra
 Maintainer: Antoine Beaupré 
 Uploaders: Jose Carlos Garcia Sogo 
-Build-Depends: debhelper (>= 7.0.50~), autoconf, automake
+Build-Depends: debhelper (>= 7.0.50~), autoconf, automake, dh-autoreconf
 Build-Depends-Indep: librrds-perl, groff-base, libhtml-parser-perl,
  libdigest-hmac-perl, libwww-perl, liburi-perl, libcgi-fast-perl, 
libconfig-grammar-perl
-Standards-Version: 3.9.2
+Standards-Version: 3.9.5
 Homepage: http://smokeping.org/
 Vcs-Browser: http://git.debian.org/?p=collab-maint/smokeping.git
 Vcs-Git: git://git.debian.org/git/collab-maint/smokeping.git
diff -Nru smokeping-2.6.9/debian/patches/fix-paths-inside-executables 
smokeping-2.6.9/debian/patches/fix-paths-inside-executables
--- smokeping-2.6.9/debian/patches/fix-paths-inside-executables 1970-01-01 
02:00:00.0 +0200
+++ smokeping-2.6.9/debian/patches/fix-paths-inside-executables 2014-06-20 
18:06:14.0 +0300
@@ -0,0 +1,141 @@
+Index: smokeping-2.6.9/bin/smokeinfo
+===
+--- smokeping-2.6.9.orig/bin/smokeinfo
 smokeping-2.6.9/bin/smokeinfo
+@@ -4,8 +4,8 @@ use warnings;
+ 
+ use FindBin;
+ # PERL5LIB
+-use lib "$FindBin::Bin/../thirdparty/lib/perl5";
+-use lib "$FindBin::Bin/../lib";
++use lib "/usr/lib/perl5";
++use lib "/usr/lib";
+ 
+ use Smokeping::Info;
+ use Getopt::Long 2.25 qw(:config no_ignore_case);
+@@ -84,19 +84,19 @@ they work on the same syntax.
+ 
+ Get all data all nodes
+ 
+- smokeinfo etc/config 
++ smokeinfo /etc/smokeping/config
+ 
+ Only show nodes directly under /Customers
+ 
+- smokeinfo --filter=/Customers/ etc/config
++ smokeinfo --filter=/Customers/ /etc/smokeping/config
+ 
+ Show all nodes under /Customers
+ 
+- smokeinfo --mode=recursive --filter=/Customers/ etc/config
++ smokeinfo --mode=recursive --filter=/Customers/ /etc/smokeping/config
+ 
+ Show all nodes with '_wlan_' in the name
+ 
+- smokeinfo --mode=regexp --filter=_wlan_ etc/config
++ smokeinfo --mode=regexp --filter=_wlan_ /etc/smokeping/config
+ 
+ =head1 COPYRIGHT
+ 
+Index: smokeping-2.6.9/bin/smokeping
+===
+--- smokeping-2.6.9.orig/bin/smokeping
 smokeping-2.6.9/bin/smokeping
+@@ -6,12 +6,12 @@ use warnings;
+ 
+ use FindBin;
+ # PERL5LIB
+-use lib "$FindBin::Bin/../thirdparty/lib/perl5";
+-use lib "$FindBin::Bin/../lib";
++use lib "/usr/lib/perl5";
++use lib "/usr/lib";
+ 
+ use Smokeping;
+  
+-Smokeping::main("$FindBin::Bin/../etc/config");
++Smokeping::main("/etc/smokeping/config");
+ 
+ =head1 NAME
+ 
+@@ -136,7 +136,7 @@ local system. Three paths have to be ent
+ 
+ One pointing to your B installation
+ 
+- use lib qw(/usr/pack/rrdtool-1.0.33-to/lib/perl);
++ use lib qw(/usr/lib/perl);
+ 
+ One pointing to the place where you have installed the SmokePing libraries
+ 
+Index: smokeping-2.6.9/bin/smokeping_cgi
+===
+--- smokeping-2.6.9.orig/bin/smokeping_cgi
 smokeping-2.6.9/bin/smokeping_cgi
+@@ -6,8 +6,8 @@ use warnings;
+ 
+ use FindBin;
+ # PERL5LIB
+-use lib "$FindBin::Bin/../thirdparty/lib/perl5";
+-use lib "$FindBin::Bin/../lib";
++use lib "/usr/lib/perl5";
++use lib "/usr/lib";
+ 
+ # don't bother with zombies
+ $SIG{CHLD} = 'IGNORE';
+Index: smokeping-2.6.9/bin/tSmoke
+===
+--- smokeping-2.6.9.orig/bin/tSmoke
 smokeping-2.6.9/bin/t

Bug#750952: netselect-apt: netselect choose inexistant mirrors - (dash)

[Axel Beckert]

Control: severity -1 important
Control: tag -1 + unreproducible

doekia wrote:
> Severity: critical
> Justification: breaks the whole system

I'm sorry, but that's not really true:

1. It only breaks apt and packages dependent on it.
2. netselect-apt creates a backup copy so you just need to copy it
   back.

Additionally I can't reproduce the issue here. So maybe there's a
glitch in the downloaded mirror list which caused this?

Thanks for the patch, though!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


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

Bug#742483: zeitgeist: diff for NMU version 0.9.14-2.1

[Iain Lane]

Hi Sigfried,

I've prepared an NMU for zeitgeist (versioned as 0.9.14-2.1) and I'm
going to upload it to unstable now, since it blocks building folks. The
diff is attached to this message.

Thanks for maintaining zeitgeist,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]
diff -Nru zeitgeist-0.9.14/debian/changelog zeitgeist-0.9.14/debian/changelog
--- zeitgeist-0.9.14/debian/changelog	2013-10-25 22:33:59.0 +0100
+++ zeitgeist-0.9.14/debian/changelog	2014-06-23 11:49:26.0 +0100
@@ -1,3 +1,12 @@
+zeitgeist (0.9.14-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * 0001-libzeitgeist-Add-a-missing-dependency-on-gio-2.0.patch: Cherry-pick
+commit from to fix a missing dependency on gio-2.0 in the vapi file.
+(Closes: #742483)
+
+ -- Iain Lane   Mon, 23 Jun 2014 11:46:22 +0100
+
 zeitgeist (0.9.14-2) unstable; urgency=low
 
   * Fix installation of bash completion (Closes: #727089, #727151).
diff -Nru zeitgeist-0.9.14/debian/patches/0001-libzeitgeist-Add-a-missing-dependency-on-gio-2.0.patch zeitgeist-0.9.14/debian/patches/0001-libzeitgeist-Add-a-missing-dependency-on-gio-2.0.patch
--- zeitgeist-0.9.14/debian/patches/0001-libzeitgeist-Add-a-missing-dependency-on-gio-2.0.patch	1970-01-01 01:00:00.0 +0100
+++ zeitgeist-0.9.14/debian/patches/0001-libzeitgeist-Add-a-missing-dependency-on-gio-2.0.patch	2014-06-23 11:46:00.0 +0100
@@ -0,0 +1,22 @@
+From b1e82de434a7b63fe1290d0051de58350b069991 Mon Sep 17 00:00:00 2001
+From: Philip Withnall 
+Date: Sun, 16 Feb 2014 15:08:49 +
+Subject: [PATCH] libzeitgeist: Add a missing dependency on gio-2.0
+
+This actually makes the zeitgeist vapi file usable.
+
+Signed-off-by: Seif Lotfy 
+---
+ libzeitgeist/zeitgeist-2.0.deps | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/libzeitgeist/zeitgeist-2.0.deps b/libzeitgeist/zeitgeist-2.0.deps
+index ff8d39b..59eec5d 100644
+--- a/libzeitgeist/zeitgeist-2.0.deps
 b/libzeitgeist/zeitgeist-2.0.deps
+@@ -1 +1,2 @@
+ zeitgeist-datamodel-2.0
++gio-2.0
+-- 
+2.0.0
+
diff -Nru zeitgeist-0.9.14/debian/patches/series zeitgeist-0.9.14/debian/patches/series
--- zeitgeist-0.9.14/debian/patches/series	2013-10-25 22:16:07.0 +0100
+++ zeitgeist-0.9.14/debian/patches/series	2014-06-23 11:46:00.0 +0100
@@ -1 +1,2 @@
 fix_autocomplete.diff
+0001-libzeitgeist-Add-a-missing-dependency-on-gio-2.0.patch

Bug#724471: smokeping: FTBFS: configure.ac:24 error: required file 'conftools/compile' not found

[Rowan Thorpe]

I just sent a debdiff which updates several bugs including this one, and only
afterwards noticed Hideki Yamane had already sent a diff for this one (and for
a "related" bug which I since opened as a separate bug). For some strange
reason #724471 only appeared for me in reportbug and not by browsing the bts
for experimental. Both fixes I just sent are different though (and in one case
an actual fix rather than a workaround, and in the other case a more robust fix
too ...I believe?), but if I had seen his patch earlier I would have titled two
of the three patches more along the lines of "improved" patches rather than
"new" ones. Feel free to adapt the changelog to reflect that if you deem it
appropriate.
--
Rowan Thorpe
PGP fingerprint:
 BB0A 0787 C0EE BDD8 7F97  3D30 49F2 13A5 265D CCBD

"There is a great difference between worry and concern. A worried person sees
a problem, and a concerned person solves a problem."
 - Harold Stephens


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

Bug#752394: cups installation hangs in triggers

[Vincent Lefevre]

Package: cups
Version: 1.7.3-3
Severity: grave
Justification: renders package unusable

During an upgrade, I got:

[...]
Processing triggers for cups (1.7.3-3) ...

Then, nothing for 3 minutes. A ps output showed:

UIDPID  PPID  C STIME TTY  TIME CMD
root 20661 20645  0 13:03 pts/100:00:00 lpstat -h 
/var/run/cups/cups.sock -r

(thus started 3 minutes ago). I couldn't kill it from the terminal
with Ctrl-C or Ctrl-\. I had to start another terminal and do a
kill -9 on it.

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

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

Versions of packages cups depends on:
ii  cups-client1.7.3-3
ii  cups-common1.7.3-3
ii  cups-core-drivers  1.7.3-3
ii  cups-daemon1.7.3-3
ii  cups-filters   1.0.54-2
ii  cups-ppdc  1.7.3-3
ii  cups-server-common 1.7.3-3
ii  debconf [debconf-2.0]  1.5.53
ii  ghostscript9.05~dfsg-8.1
ii  libavahi-client3   0.6.31-4
ii  libavahi-common3   0.6.31-4
ii  libc-bin   2.19-3
ii  libc6  2.19-3
ii  libcups2   1.7.3-3
ii  libcupscgi11.7.3-3
ii  libcupsimage2  1.7.3-3
ii  libcupsmime1   1.7.3-3
ii  libcupsppdc1   1.7.3-3
ii  libgcc11:4.9.0-7
ii  libstdc++6 4.9.0-7
ii  libusb-1.0-0   2:1.0.19-1
ii  lsb-base   4.1+Debian13
ii  poppler-utils  0.24.5-4
ii  procps 1:3.3.9-5

Versions of packages cups recommends:
ii  avahi-daemon 0.6.31-4
ii  colord   1.2.1-1
ii  cups-filters [ghostscript-cups]  1.0.54-2
ii  printer-driver-gutenprint5.2.10-2

Versions of packages cups suggests:
ii  cups-bsd   1.7.3-3
pn  cups-pdf   
ii  foomatic-db20140325-1
ii  hplip  3.14.6-1
ii  printer-driver-hpcups  3.14.6-1
pn  smbclient  
ii  udev   204-10

-- debconf information:
  cupsys/backend: lpd, socket, usb, snmp, dnssd
  cupsys/raw-print: true


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

Bug#430684: Wheezy still confirmed bug

[Dirk Teurlings - SIGNET B.V.]

This is still confirmed on debian wheezy.

System:
RAM 64 GB
CPU Dual AMD Opteron(TM) Processor 6212 (16 cores in total)
2x SSD in RAID 1 256GB
2x HDD in RAID 1 1TB

With the innodb_buffer_pool_size on 50G the timeout is way too short.

We've fixed it with the same proposed fix by the original bugposter.

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

[Niko Tyni]

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.

> + use FindBin;
> + # PERL5LIB
> +-use lib "$FindBin::Bin/../thirdparty/lib/perl5";
> +-use lib "$FindBin::Bin/../lib";
> ++use lib "/usr/lib/perl5";
> ++use lib "/usr/lib";

Please don't hardcode /usr/lib/perl5. See #748380.

/usr/lib makes no sense at all, that's not for perl modules.

Just relying on the default perl search path without FindBin
or any "use lib" statements should work fine AFAICS.

> +- use lib "/usr/local/smokeping/lib";
> +- use lib "/usr/local/rrdtool-1.0.39/lib/perl";
> ++ use lib "/usr/lib";
> ++ use lib "/usr/lib/perl";

/usr/lib/perl is nonsense too (presumably a typo?)
-- 
Niko Tyni   nt...@debian.org


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

Bug#749978: #749978: guayadeque: Please update to use wxwidgets3.0

[Damyan Ivanov]

-=| Olly Betts, 23.06.2014 11:00:14 +0100 |=-
> On Mon, Jun 23, 2014 at 12:50:11PM +0300, Damyan Ivanov wrote:
> > /tmp/buildd/guayadeque-0.3.7~ds0/src/ListView.h:160:5: error: 'wxImageList' 
> > does not name a type
> >  wxImageList *   m_ImageList;
> >  ^
> 
> For this (and the similar errors for other missing classes) you probably
> just need to explicitly include the appropriate wx/.h header which
> declares the missing class.

Thanks. Attached is a patch that fixes these (until the build fails 
with other errors).

> Not sure about the other issues off the top of my head.

Sure. I guess the rest needs somebody deeper in C++ than me then.

-- dam
--- a/src/ListView.h
+++ b/src/ListView.h
@@ -28,6 +28,7 @@
 #include 
 #include 
 #include 
+#include 
 
 class guListViewClient;
 class guListViewHeader;
--- a/src/FileBrowser.cpp
+++ b/src/FileBrowser.cpp
@@ -36,6 +36,7 @@
 #include 
 #include 
 #include 
+#include 
 
 WX_DEFINE_OBJARRAY(guFileItemArray);
 
@@ -221,7 +222,7 @@ guFileBrowserDirCtrl::guFileBrowserDirCt
 
 	DirBtnSizer->Add( 0, 0, 1, wxEXPAND, 5 );
 
-	m_ShowLibPathsBtn = new wxToggleBitmapButton( this, wxID_ANY, guImage( guIMAGE_INDEX_tiny_library ), wxDefaultPosition, wxDefaultSize, wxBU_AUTODRAW );
+	m_ShowLibPathsBtn = new wxBitmapToggleButton( this, wxID_ANY, guImage( guIMAGE_INDEX_tiny_library ), wxDefaultPosition, wxDefaultSize, wxBU_AUTODRAW );
 m_ShowLibPathsBtn->SetToolTip( ShowPaths == guFILEBROWSER_SHOWPATH_SYSTEM ?
   _( "See used locations" ) :
   _( "See system files" ) );
--- a/src/FileBrowser.h
+++ b/src/FileBrowser.h
@@ -36,6 +36,7 @@
 #include 
 #include 
 #include 
+#include 
 
 
 #define guPANEL_FILEBROWSER_DIRCTRL ( 1 << 0 )
@@ -122,7 +123,7 @@ class guFileBrowserDirCtrl : public wxPa
 guMediaViewer * m_MediaViewer;
 guGenericDirCtrl *  m_DirCtrl;
 boolm_AddingFolder;
-wxToggleBitmapButton *  m_ShowLibPathsBtn;
+wxBitmapToggleButton *  m_ShowLibPathsBtn;
 
 voidOnShowLibPathsClick( wxCommandEvent& event );
 
--- a/src/AuiNotebook.cpp
+++ b/src/AuiNotebook.cpp
@@ -389,6 +389,8 @@ void guAuiNotebook::UpdateTabCtrlHeight(
 tabctrl->SetArtProvider(art->Clone());
 tab_frame->DoSizing();
 }
+
+return true;
 }
 
 //  //
--- a/src/AuiNotebook.h
+++ b/src/AuiNotebook.h
@@ -205,7 +205,7 @@ class guAuiNotebook : public wxAuiNotebo
 
 virtual ~guAuiNotebook();
 
-virtual void UpdateTabCtrlHeight();
+virtual bool UpdateTabCtrlHeight();
 
 wxString SavePerspective( void );
  	bool LoadPerspective( const wxString &layout );

Bug#752395: python2.7: JSON module: reading arbitrary process memory

[Gert van Dijk]

Package: python2.7
Version: 2.7.3-6+deb7u2
Severity: normal
Tags: security,patch

Dear Maintainer,

As reported upstream, the JSON module of Python is vulnerable for reading
arbitrary process memory. Please apply the patch as included in the bug report
http://bugs.python.org/issue21529

I'm not aware of any CVE assigned to this bug.

Patch is applied upstream in 2.7.7, so this only applies to wheezy and
squeeze-lts.

--- python2.7-2.7.3/Modules/_json.c 2012-04-10 01:07:33.0 +0200
+++ python2.7-2.7.3-withpatch/Modules/_json.c   2014-06-23
13:40:15.647298884 +0200
@@ -1491,7 +1491,7 @@
 PyObject *res;
 char *str = PyString_AS_STRING(pystr);
 Py_ssize_t length = PyString_GET_SIZE(pystr);
-if (idx >= length) {
+if ( idx < 0 || idx >= length) {
 PyErr_SetNone(PyExc_StopIteration);
 return NULL;
 }
@@ -1578,7 +1578,7 @@
 PyObject *res;
 Py_UNICODE *str = PyUnicode_AS_UNICODE(pystr);
 Py_ssize_t length = PyUnicode_GET_SIZE(pystr);
-if (idx >= length) {
+if ( idx < 0 || idx >= length) {
 PyErr_SetNone(PyExc_StopIteration);
 return NULL;
 }

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

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

Versions of packages python2.7 depends on:
ii  libbz2-1.0 1.0.6-4
ii  libc6  2.13-38+deb7u1
ii  libdb5.1   5.1.29-5
ii  libexpat1  2.1.0-1+deb7u1
ii  libgcc11:4.7.2-5
ii  libncursesw5   5.9-10
ii  libreadline6   6.2+dfsg-0.1
ii  libsqlite3-0   3.7.13-1+deb7u1
ii  libtinfo5  5.9-10
ii  mime-support   3.52-1
ii  python2.7-minimal  2.7.3-6+deb7u2

python2.7 recommends no packages.

Versions of packages python2.7 suggests:
ii  binutils   2.22-8
pn  python2.7-doc  

-- no debconf information


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

Bug#752396: ITP: r-cran-randomfields -- GNU R simulation and analysis of random fields

[Andreas Tille]

Package: wnpp
Severity: wishlist
Owner: Andreas Tille 

* Package name: r-cran-randomfields
  Version : 3.0.10
  Upstream Author : Martin Schlather 
* URL : http://cran.r-project.org/web/packages/RandomFields/
* License : GPL
  Programming Lang: R
  Description : GNU R simulation and analysis of random fields
 This GNU R package can be used for simulation of Gaussian and extreme
 value random fields; conditional simulation; kriging; maximum likelihood
 estimation.


Remark: This package is used in unit tests of r-cran-spatstat and thus
it will be provided as Debian package as well to enable running the full
test suite.  The package is maintained by the Debian Science team at


svn://anonscm.debian.org/debian-science/packages/R/trunk/packages/r-cran-randomfields/trunk/


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

Bug#751271: usb-modeswitch: doesn't switch Huawei E3131s-2 on boot

[Matt Li]

Scrap that, false alarm from rebooting and so the modem was already 
switched.


Replacing the wrapper script with a simple logging script just like 
Jakub also showed that the wrapper wasn't being run.
Interestingly, downgrading back to 2.1.1+repack0-1 and 20140327-1 
resulted in the same issue so maybe another dependency is at play.


My interim solution is to manually call the wrapper in rc.local as the 
modem will always be in the same USB port:


if [ ! -L /dev/3gmodem ];
then
/lib/udev/usb_modeswitch '/1-1.3.3:1.0' &
sleep 10
fi
pon 3g &


Where `sleep 10` is to give another time for the device to switch, which 
I notice can take up to ~8 seconds and /dev/3gmodem is a symlink set by 
another udev rule I have in /etc/udev/rules.d/99-usb.rules:


SUBSYSTEMS=="usb", DRIVERS=="option", ATTRS{bInterfaceNumber}=="01", 
SYMLINK+="3gmodem"



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

Bug#750623: [Pkg-ime-devel] Bug#750623: Bug#750623: What is the hold-up of uploadin new package

[Osamu Aoki]

Hi,

On Sun, Jun 22, 2014 at 12:01:49PM -0400, GUO Yixuan wrote:
> On Sun, Jun 22, 2014 at 08:27:12PM +0900, Osamu Aoki wrote:
> > 
> > On Sun, Jun 22, 2014 at 01:45:32AM +0800, Aron Xu wrote:
> > > On Sun, Jun 22, 2014 at 1:33 AM, GUO Yixuan  wrote:
> > > > I'm just waiting for a confirmation on the librime-dev => librime1-dev
> > > > renaming, from Aron, as we discussed in a previous thread. [1]
> > > >
> > > 
> > > As said before, I don't have strong opinion on either way.
> > 
> > My popsition is that you have not presented enough reason to do this.
> > So do not do this.
> 
> I remember one possible reason: librime 1.0 breaks some ABI and API
> compatibility, 

Yes.  Thus you need to change librime0 to librime1 etc.

> so we should change the -dev package name. [1][2]

No.  Your reference does not say so.

This is only needed if you are having massive dependency and transition
library in complicated arrangement which you seem not to chase.

KISS (Keep it simple and S***) is the reason why I said no.  (I am not
saying your method break things)

As long as all dependency packages are binNMUed using the standard
procedure, the same librime-dev is sufficient and simple.

Let's review what your reference say:

> [1] https://wiki.debian.org/TransitionBestPractices

The first reminder is:

If there's a backward-incompatible ABI change (binary incompatibility)
which prevents old programs from working with the new library: you need
to change the library soname, and you need to change the library package
name, but you usually should not change the -dev package name.
  ^

> [2] 
> http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#sonameapiabi
Hmmm... not therer but look at:
http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#id249952

1. -DEV package names

Package maintainer has two options when naming a shared library -DEV
package. 
...  This document is neutral on which method to deploy.

You did not present rationale to do extrastep with the second option.

I see 
librime1 (>= ${source:Version}), librime1 (<< ${source:Version}+1~)

This seems binNMU unsafe.  Please drop max version limitation.

Regards,

Osamu


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

Bug#746920: wfmath: ftbfs with GCC-4.9

[Xilin Sun]

Control: tag -1 patch

Dear maintainer,

Please consider applying the attached patch to resolve ftbfs with GCC-4.9.

Regards,
Xilin
diff -Nru wfmath-0.3.12/debian/changelog wfmath-0.3.12/debian/changelog
--- wfmath-0.3.12/debian/changelog	2012-06-02 17:34:40.0 +0800
+++ wfmath-0.3.12/debian/changelog	2014-06-23 19:52:31.0 +0800
@@ -1,3 +1,10 @@
+wfmath (0.3.12-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-4.9
+
+ -- Xilin Sun   Mon, 23 Jun 2014 19:52:02 +0800
+
 wfmath (0.3.12-3) unstable; urgency=low
 
   * added more symbols (closes: #671956)
diff -Nru wfmath-0.3.12/debian/libwfmath-0.3-6.symbols wfmath-0.3.12/debian/libwfmath-0.3-6.symbols
--- wfmath-0.3.12/debian/libwfmath-0.3-6.symbols	2012-06-01 16:08:27.0 +0800
+++ wfmath-0.3.12/debian/libwfmath-0.3-6.symbols	2014-06-23 19:53:08.0 +0800
@@ -46,7 +46,6 @@
  _ZN6WFMath12_Poly2OrientILi3EEaSERKS1_@Base 0.3.11
  _ZN6WFMath13_ScaleEpsilonEPKfS1_id@Base 0.3.11
  _ZN6WFMath13_ScaleEpsilonEddd@Base 0.3.11
- (optional)_ZN6WFMath14SloppyDistanceILi2EEEfRKNS_5PointIXT_EEES4_@Base 0.3.12
  _ZN6WFMath14BoundingSphereILi2ESt6vectorEENS_4BallIXT_EEERKT0_INS_5PointIXT_EEESaIS6_EE@Base 0.3.11
  _ZN6WFMath14SloppyDistanceILi3EEEfRKNS_5PointIXT_EEES4_@Base 0.3.11
  _ZN6WFMath14_ReadCoordListERSiPfi@Base 0.3.11
@@ -311,7 +310,6 @@
  _ZN6WFMath7PoissonEdj@Base 0.3.11
  _ZN6WFMath7PolygonILi2EE11rotatePointERKNS_9RotMatrixILi2EEERKNS_5PointILi2EEE@Base 0.3.11
  _ZN6WFMath7PolygonILi2EE5shiftERKNS_6VectorILi2EEE@Base 0.3.11
- (c++|optional=inline)WFMath::Polygon<2>::~Polygon()@Base 0.3.11
  _ZN6WFMath7PolygonILi3EE10moveCornerEiRKNS_5PointILi3EEEd@Base 0.3.11
  _ZN6WFMath7PolygonILi3EE11rotatePointERKNS_10QuaternionERKNS_5PointILi3EEE@Base 0.3.11
  _ZN6WFMath7PolygonILi3EE11rotatePointERKNS_9RotMatrixILi3EEERKNS_5PointILi3EEE@Base 0.3.11
@@ -963,11 +961,7 @@
  _ZNK6WFMath9RotMatrixILi3EE9isEqualToERKS1_d@Base 0.3.11
  _ZNK6WFMath9RotMatrixILi3EEeqERKS1_@Base 0.3.11
  _ZNK6WFMath9RotMatrixILi3EEneERKS1_@Base 0.3.11
- (regex|optional=inline)_ZNSsC[12]IPcEET_S1_RKSaIcE@Base 0.3.11
  (optional=inline)_ZNSs12_S_constructIPcEES0_T_S1_RKSaIcESt20forward_iterator_tag@Base 0.3.12
- (optional=inline)_ZNSt10_List_baseI13LinePointDataSaIS0_EE8_M_clearEv@Base 0.3.12
- (optional=inline)_ZNSt10_List_baseIN6WFMath11_PolyReaderILi3EEESaIS2_EE8_M_clearEv@Base 0.3.12
- (optional=inline)_ZNSt10_List_baseIN6WFMath9_miniball13Wrapped_arrayILi2EEESaIS3_EE8_M_clearEv@Base 0.3.12
  _ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 0.3.11
  _ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 0.3.11
  _ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 0.3.11
@@ -977,12 +971,6 @@
  _ZNSt6vectorIfSaIfEE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPfS1_EERKf@Base 0.3.11
  (regex)_ZNSt6vectorIfSaIfEE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPfS1_EE[mj]RKf@Base 0.3.11
  _ZNSt6vectorIfSaIfEE6insertEN9__gnu_cxx17__normal_iteratorIPfS1_EERKf@Base 0.3.11
- (regex|optional=inline)_ZNSt6vectorIfSaIfEED[12]Ev@Base 0.3.12
- (regex)_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIf[il]fEvT_T0_S8_T1_@Base 0.3.11
- (optional=inline)_ZSt13__heap_selectIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIfEvT_S7_S7_@Base 0.3.11
- _ZSt16__insertion_sortIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIfEvT_S7_@Base 0.3.11
- (regex)_ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIf[li]EvT_S7_T0_@Base 0.3.11
- (optional=inline)_ZSt19__move_median_firstIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIfEvT_S7_S7_@Base 0.3.11
  _ZTIN6WFMath10ParseErrorE@Base 0.3.11
  _ZTIN6WFMath15ColinearVectorsILi2EEE@Base 0.3.11
  _ZTIN6WFMath15ColinearVectorsILi3EEE@Base 0.3.11

Bug#752397: javahelper doesn't add libswt-cairo-gtk-3-jni when {java:Depends} is specified

[Praveen Arimbrathodiyil]

package: javahelper, libswt-gtk-3-java
severity: important

It is likely that libswt-gtk-3-java is missing a runtime dependency on . 
To test this gnukhata package can be installed from 
packages.debian.org/~praveen/gnukhata


$ gnukhata
getorgnames
result is[Ljava.lang.Object;@69cd468c
Exception in thread "main" java.lang.UnsatisfiedLinkError: Could not 
load SWT library. Reasons:

no swt-cairo-gtk-3836 in java.library.path
no swt-cairo-gtk in java.library.path
Can't load library: /usr/lib/jni/libswt-cairo-gtk-3836.so
Can't load library: /usr/lib/jni/libswt-cairo-gtk.so
	Can't load library: 
/home/inu/.swt/lib/linux/x86_64/libswt-cairo-gtk-3836.so

Can't load library: /home/inu/.swt/lib/linux/x86_64/libswt-cairo-gtk.so

at org.eclipse.swt.internal.Library.loadLibrary(Library.java:335)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:240)
at org.eclipse.swt.internal.cairo.Cairo.(Cairo.java:27)
at org.eclipse.swt.graphics.Image.createFromPixbuf(Image.java:725)
at org.eclipse.swt.graphics.Image.initNative(Image.java:677)
at org.eclipse.swt.graphics.Image.(Image.java:663)
at gnukhata.views.startupForm.(startupForm.java:119)
at gnukhata.views.startupForm.main(startupForm.java:1708)


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

Bug#752398: ITP: python-spyne -- Python RPC library for HttpRpc, SOAP, Json and more

[Russell Stuart]

Package: wnpp
Severity: wishlist
Owner: Russell Stuart 

* Package name: python-spyne
  Version : 2.10.10
  Upstream Author : Burak Arslan 
* URL : http://spyne.io/
* License : LGPL
  Programming Lang: Python
  Description : Python RPC library for HttpRpc, SOAP, Json and more

Spyne is a Python library for implementing RPC servers over HTTP and
ZeroMQ using a multitude of serialisation formats, such as HttpRpc,
SOAP, Json, XML.  The signatures of the published functions and the
data types passed as parameters and returned as results are obtained
by introspecting the python code.

Originally called soaplib, it was later renamed to rpclib, and then
to spyne.


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

Bug#752206: Option -a/--archive with full path to upstream source doesn't work

[Osamu Aoki]

Hi,

On Sun, Jun 22, 2014 at 10:49:09PM +0530, Vasudev Kamath wrote:
> > debug lines are long to make it easy to scan source to check such lines
> > by grep.  Others, you can call me lazy.  I keep terminal width
> > relatively large like 100.  I will happy to fold 80 if they are not
> > debug lines.  
> 
> I see, I normally keep everything under pep8 in my python project as its
> the standard accepted by python community (ofcourse now screen supports
> more than 80 column but we still carry baggage from past happily) 

I like to keep code within 80 ch/line if it does not interfare with
readability of code. 

I made exception to use up to 100 char/line for regex data.  For
debug.debug(...) like line, I made exception to keep it in one line.  I
hope to keep them so.  The trankated lines of these parts do not affect
program readability.

But Some variables like LMAX in upprecase may be changed to __line_max__
etc.  I am open for cleaning up such and reformatting in more readable
style if I get patch :-) 

FYI pep-8 has:
| Some teams strongly prefer a longer line length. For code maintained
| exclusively or primarily by a team that can reach agreement on this
| issue, it is okay to increase the nominal line length from 80 to 100
| characters (effectively increasing the maximum length to 99 characters),
| provided that comments and docstrings are still wrapped at 72
| characters.

Osamu


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

Bug#752399: ITP: python-fdb -- Python DB-API driver for Firebird

[Russell Stuart]

Package: wnpp
Severity: wishlist
Owner: Russell Stuart 

* Package name: python-fdb
  Version : 1.4
  Upstream Author : Pavel Cisar 
* URL : https://pypi.python.org/pypi/fdb/
* License : BSD
  Programming Lang: C, Python
  Description : Python DB-API driver for Firebird

FDB is a Python library package that implements Python Database API
2.0-compliant support for the open source relational database Firebird®.
In addition to the minimal feature set of the standard Python DB API,
FDB also exposes nearly the entire native client API of the database
engine.


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

Bug#749405: [Resolvconf-devel] Bug#749405: Current Status + Moving Forward?

[Thomas Hood]

On 23 June 2014 05:45, Nick Daly  wrote:

> What still needs to be done on this bug to resolve it?



I think it just needs to be tested.  Have you tested the proposed fix at
all?

-- 
Thomas

Bug#752400: tech-ctte: Please advice on util-linux situation

[Andreas Henriksson]

Package: tech-ctte
Severity: normal

Hello!

Over the past year I've followed a bit of the discussion on the
technical committee mailing list and it seems like people on the
committee are much more willing to turn to it for advice then other
people. Maybe I should not be so shy and try to ask for your guidance
more often myself? Lets try it...

According to Debian constitution chapter 6.1 §3 I'm seeking your
advice on how to best handle the util-linux situation.

In a very brief background statement, my impression is that the
current util-linux maintenance leaves alot to be desired. Bugs are not
being dealt with, patches are ignored, upstream releases are not
incorporated.

I've tried both giving the current maintainers time (as the little
public communication that exists has included repeated promises that
work is being done on the package), and more recently to actively help
out and offer a solution (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678446#62 and the
followup). Communications have not been very successful as it seems
like current maintainers do not like to communicate publicly. The
little information I have is from what has been leaked from private
discussions. The advice I've received from other Debian Developers is
that I should not expect any replies from current maintainers and
general support for just going ahead and uploading an updated version
of the package without maintainer concent. (If you're interested in
my work on the package itself see
http://people.debian.org/~ah/util-linux-2.24/ where I've aimed for
creating an updated and more easily maintainable package which
functionality wise is "on par" with current package -- paving the way
for actually fixing reported packaging bugs while being able to easily
update to new upstream releases when they appear.)

Basically, informed users are frustrated that they do not get to enjoy
the bugfixes and new features of upstream releases and Debian
Developers working on related packages are frustrated that they can
not get even the most trivial integration fixes included in the
util-linux package.

I've recently done some basic bug triaging and (amond other things)
added the "fixed-upstream" tag to more bugs which I could easily
identified as being resolved by newer upstream releases.  I think the
list of bugs speaks pretty much for itself that having a newer
upstream release in debian would be a welcome improvement:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=util-linux;include=tags:fixed-upstream

Apart from that, the package is basically always release critically
buggy and since the last maintainer upload (over 2 years ago) there
has been 8 NMUs. The current situation is that there are still 3 open
RC-bugs. Of these 1 would be resolved by a newer upstream release, the
other 2 are pure packaging bugs which upstream can not do anything
about but an active maintainer should be able to deal with quickly.

Hopefully my bug triaging has been helpful and just identifying which
bugs can be closed with a new upstream release in the archive
should save someone alot of time, but I'd like to go further and
actually see bugs *fixed*. I hope I've shown that I'm willing and
capable to do the work myself, but I'm unsure on how to best proceed
given that my help is not accepted in addition to Debians strong
ownership principles. So what is your advice? How do I best proceed?
If someone has secret back channels to maintainers, could you please
use them to see if we can find a way forward? Should I continue to
respect the wishes of the people listed as maintainer/uploaders of the
package despite they haven't produced any improvements in over 2 years
time and the package still needs attention to be in a shape acceptable
for release? Should I give up on trying to integrate my improvements
and instead continue to maintain my package outside of the archive and
ask people to use my version instead of the official package?


Regards,
Andreas Henriksson

PS. While forwarding a few patches upstream I was happy to see we already
have hurd porters working actively with upstream on their new releases! :)


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

Bug#752394: cups installation hangs in triggers

[Didier 'OdyX' Raboud]

Control: tags -1 +moreinfo

Le lundi, 23 juin 2014, 13.13:12 Vincent Lefevre a écrit :
> During an upgrade, I got:
> 
> [...]
> Processing triggers for cups (1.7.3-3) ...
> 
> Then, nothing for 3 minutes. A ps output showed:
> 
> UIDPID  PPID  C STIME TTY  TIME CMD
> root 20661 20645  0 13:03 pts/100:00:00 lpstat -h
> /var/run/cups/cups.sock -r
> 
> (thus started 3 minutes ago). I couldn't kill it from the terminal
> with Ctrl-C or Ctrl-\. I had to start another terminal and do a
> kill -9 on it.

Apparently it waits on this line:

http://anonscm.debian.org/gitweb/?p=printing/cups.git;a=blob;f=debian/cups.postinst;hb=debian/1.7.3-3#l131

What does the "lpstat -h /var/run/cups/cups.sock -r" command give to 
you?

TIA, cheers,

OdyX

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

Bug#752401: net-dns-fingerprint: fpdns doesn't work with recent Net::DNS (libnet-dns-perl 0.69+)

[Ondřej Surý]

Package: net-dns-fingerprint
Version: 0.9.3-5
Severity: grave
Tags: upstream
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

fpdns as packaged from Google Code is using some internal APIs from
Net::DNS and thus it ceased to work with recent upload of
libnet-dns-perl 0.77 to unstable.

Please update fpdns to the new upstream located at:

https://github.com/kirei/fpdns

Ondrej

- -- System Information:
Debian Release: 7.5
  APT prefers stable
  APT policy: (900, 'stable'), (800, 'testing')
Architecture: amd64 (x86_64)

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

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

iQIcBAEBCAAGBQJTqBzsAAoJEAyZtw70/LsHP4wQAMvKyRkPv2cvXjdJyF3XJXKH
TnEmTBEyGu6svqax6wEu49w7M8TlIOpafb35XV6ZR37tAhu3A9K4vhgjz4zPItYq
2U2grZKIkoPdfCob9DHzd6qro3ByPw1m3i7FpUiMPnoApsziXNbt9ThmUNxm4KdP
+h5Kc0A5s4n4ZtxP3w3o5Yv3AguYKIPdayPyDBhyVOD0tjexaMO9AyyoPJVF38iY
eXv/TyNMPmPhkIVNg+7fKS8xGUoS1rhXo+xCWp1UtgzK3S8Ael4jFmaCiUVpiTMH
9+GH1tJVPo73rIQcNVJwEXjONvwW5C/UYkrscpJrvYe2LqFNxLA3NiCbPVHy6+SJ
UDyhics3//Q41Vuocmyv2FNsH4zdoin2EYqVvV7y1T2aAnyk89fAv7NxYBP9zXQ4
Sy6shHJgiL8MgCmgzfDZ3TnPOHj6LsI2l1P0UEyd+RiFpd1socC0+kftP1KUMkFU
Rh/jYh3+XTvkf/TIM1WAzhwN3JoEJpkvgfsnQkXU8zuC3P0aRxVujCf1l85cX0UJ
vyUQI57wJJQeaKYrDtdHnjo7MZ2uEUZSj30zqVl7L3fOmPcfpHqkofc2pX97/E0L
fyBJKKIpejo+StabME6lvoZgFqTFNkUm9MzSDXhJ6LBnR1NZlNYgGPfZaanyJepQ
UIT5sArPOGo+3NlS27Fp
=ej6M
-END PGP SIGNATURE-


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

Bug#745556: Closing dialog for allowing invalid SSL certificate causes default to be accepted

[Jim Scadden]

On Mon, Jun 09, 2014 at 11:43:46AM +0100, Jim Scadden wrote:
> Attached is a proposed patch which I have forwarded upstream which 
> modifies the behaviour of the dialog box in question so that closing it 
> will return the user back to the previous dialog

After testing my patch for a while I do not believe that it is the best 
approach. With the patch applied the default option of 'Current Session 
only' is located on the left and the 'Forever' option is in the middle. 
Since the 'Continue' button on the previous dialog is in the middle
this means that a user who neglects to fully read the 2nd dialog box and 
just clicks will have chosen to accept the certificate forever.

Additionally the same logic for invalid SSL certificates is used in 
other parts of KDE, so any change would further require changes across 
multiple packages to keep the UI consistent across the DE.

Rémi, please could you advise if you would still like the behaviour to 
be modified? If so, given that the user has already stated on the first 
dialog box that they wish to connect to the server, and closing the 2nd 
dialog causes the certificate to only be accepted for the current 
session, would you be happy for this bug to be tagged as 'wishlist' 
since this is something could potentially require a substantial change 
upstream?

-- 

Jim Scadden


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

Bug#752402: missing license in debian/copyright

[Thorsten Alteholz]

Package: autogen
Version: 1:5.18.3-4
Severity: serious
User: alteh...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

Dear Maintainer,

please add the missing licenses of:
 autogen-5.18.3\autoopts\gettext.h
 autogen-5.18.3\autoopts\parse-*
 autogen-5.18.3\snprintfv\* 
to debian/copyright.


The name of the GPL-2.1+ license block should be LGPL-2.1+, shouldn't it?

Thanks!
  Thorsten


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

Bug#752368: [pkg-db-devel] Bug#752368: src:db5.3: FTCBFS on any architecture: installs build_signature_$DEB_HOST_ARCH.txt which is not built

[Ondřej Surý]

Control: tags -1 +pending

Thanks, Helmut, I have merged your patch and I am building new version
right now.

Somehow I didn't upload the last two fixes I did for db5.3 so this
update will have more fixes.

O.

On Mon, Jun 23, 2014, at 06:06, Helmut Grohne wrote:
> Package: src:db5.3
> Version: 5.3.28-3.1
> Severity: important
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> Dear db5.3 maintainers,
> 
> Currently db5.3 fails to cross-build from source for any architecture,
> because override_dh_installdocs tries to install a file never built:
> 
> | # Install build_signature_x32.txt to docs
> | install -m 644 debian/build_signature_x32.txt
> /tmp/buildd/db5.3/db5.3-5.3.28/debian/libdb5.3/usr/share/doc/libdb5.3/
> | install: cannot stat 'debian/build_signature_x32.txt': No such file or
> directory
> | debian/rules:211: recipe for target 'override_dh_installdocs' failed
> | make[1]: *** [override_dh_installdocs] Error 1
> | make[1]: Leaving directory '/tmp/buildd/db5.3/db5.3-5.3.28'
> | debian/rules:127: recipe for target 'binary-arch' failed
> | make: *** [binary-arch] Error 2
> | dpkg-buildpackage: error: debian/rules binary-arch gave error exit
> status 2
> 
> I suggest only installing this file when building it. Please consider my
> patch attached.
> 
> Helmut
> ___
> pkg-db-devel mailing list
> pkg-db-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-db-devel
> Email had 1 attachment:
> + db5.3_missing_build_signature.debdiff
>   1k (text/plain)


-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


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

Bug#742483: zeitgeist: diff for NMU version 0.9.14-2.1

[Siegfried Gevatter]

Great, thanks Iain :)

2014-06-23 12:55 GMT+02:00 Iain Lane :
> Hi Sigfried,
>
> I've prepared an NMU for zeitgeist (versioned as 0.9.14-2.1) and I'm
> going to upload it to unstable now, since it blocks building folks. The
> diff is attached to this message.
>
> Thanks for maintaining zeitgeist,
>
> --
> Iain Lane  [ i...@orangesquash.org.uk ]
> Debian Developer   [ la...@debian.org ]
> Ubuntu Developer   [ la...@ubuntu.com ]



-- 
Siegfried


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

Bug#749716: scons: Bibtex bibliography isn't created unless \bibliography is at the end of the document, but not if it's inside a section

[Alvaro G. M.]

Package: scons
Version: 2.3.1-1
Followup-For: Bug #749716

Dear Maintainer,

I've managed to get to the core of the error and I'm providing a patch that
solves this issue.

The problem lies on InternalLaTeXAuxAction function, which decides what to
do with .aux files generated by previous latex invocation.

For some reason, it decides to call bibtex over .aux files if and only if
they contain the word 'bibdata' inside them.

This may be enough for those cases where \bibliography is one of the last
commands on the main file. However, in some cases such as what I describe,
(I have a bibliography under the first subfile included by main file, and
after this file there come lots of sections, subsections, more included
files, etc) this command must be executed over all .aux files, for any of
this can contain a \bibliography command, \cite commands, etc.

This patch omits this test (if content.find("bibdata") != -1:) and simply
invokes bibtex (or biber) over all auxiliary files.

I think this should also be indeed faster, for file reading is performed by
SCons, although bibtex (or biber) must still process all the files.



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

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

Versions of packages scons depends on:
pn  python:any  

scons recommends no packages.

scons suggests no packages.

-- no debconf information

*** fix-bibtex-call.patch
diff -urNp scons-2.3.1.orig/engine/SCons/Tool/tex.py 
scons-2.3.1/engine/SCons/Tool/tex.py
--- scons-2.3.1.orig/engine/SCons/Tool/tex.py   2014-03-02 20:19:50.0 
+0100
+++ scons-2.3.1/engine/SCons/Tool/tex.py2014-06-23 15:12:51.100738449 
+0200
@@ -336,15 +336,13 @@ def InternalLaTeXAuxAction(XXXLaTeXActio
 already_bibtexed.append(auxfilename)
 target_aux = os.path.join(targetdir, auxfilename)
 if os.path.isfile(target_aux):
-content = open(target_aux, "rb").read()
-if content.find("bibdata") != -1:
-if Verbose:
-print "Need to run bibtex on ",auxfilename
-bibfile = 
env.fs.File(SCons.Util.splitext(target_aux)[0])
-result = BibTeXAction(bibfile, bibfile, env)
-if result != 0:
-check_file_error_message(env['BIBTEX'], 'blg')
-must_rerun_latex = True
+if Verbose:
+print "Need to run bibtex on ",auxfilename
+bibfile = env.fs.File(SCons.Util.splitext(target_aux)[0])
+result = BibTeXAction(bibfile, bibfile, env)
+if result != 0:
+check_file_error_message(env['BIBTEX'], 'blg')
+must_rerun_latex = True
 
 # Now decide if biber will need to be run.
 # When the backend for biblatex is biber (by choice or default) the
@@ -359,15 +357,13 @@ def InternalLaTeXAuxAction(XXXLaTeXActio
 already_bibtexed.append(bcffilename)
 target_bcf = os.path.join(targetdir, bcffilename)
 if os.path.isfile(target_bcf):
-content = open(target_bcf, "rb").read()
-if content.find("bibdata") != -1:
-if Verbose:
-print "Need to run biber on ",bcffilename
-bibfile = 
env.fs.File(SCons.Util.splitext(target_bcf)[0])
-result = BiberAction(bibfile, bibfile, env)
-if result != 0:
-check_file_error_message(env['BIBER'], 'blg')
-must_rerun_latex = True
+if Verbose:
+print "Need to run biber on ",bcffilename
+bibfile = env.fs.File(SCons.Util.splitext(target_bcf)[0])
+result = BiberAction(bibfile, bibfile, env)
+if result != 0:
+check_file_error_message(env['BIBER'], 'blg')
+must_rerun_latex = True
 
 # Now decide if latex will need to be run again due to index.
 if check_MD5(suffix_nodes['.idx'],'.idx') or (count == 1 and 
run_makeindex):


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

Bug#752403: linux-image-3.12-0.bpo.1-amd64: gre fragmentation broken

[Anton Ivanov]

Package: src:linux
Version: 3.12.9-1~bpo70+1
Severity: important

Dear Maintainer,

The following should setup a gre tunnel which has MTU 1500 and 
fragments gre correctly as needed. 

ip link add gt0 type gretap remote 10.0.48.1 local 192.168.128.1
ip link set gt0 up
ifconfig gt0 mtu 1500

This works fine on 3.2 from wheezy.

Well, on 3.12 (and also tested on 3.10 from OpenWRT Barrier Breaker)
it does not. For some reason the kernel transmits _ONLY_ the second
frag, not the first (big) one. As aresult anything relying on 1500
mtu GRE breaks outright.

I have noticed that backports is now @ 3.14, I will retest with that
shortly.


-- Package-specific info:
** Version:
Linux version 3.12-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.12.9-1~bpo70+1 (2014-02-07)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.12-0.bpo.1-amd64 
root=UUID=49a2baa4-c4fb-4b25-a847-da38aabf6eb4 ro quiet rootdelay=10

** Not tainted

** Kernel log:
[  121.018798] ppdev: user-space parallel port driver
[  126.617541] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery 
directory
[  126.683548] NFSD: starting 90-second grace period (net 81883dc0)
[  153.542230] usb 4-3: USB disconnect, device number 2
[  153.576943] lenovo_tpkbd 0003:17EF:6009.0002: usb_submit_urb(ctrl) failed: 
-19
[  153.577006] lenovo_tpkbd 0003:17EF:6009.0002: usb_submit_urb(ctrl) failed: 
-19
[  180.619815] ip_tables: (C) 2000-2006 Netfilter Core Team
[  180.652075] ip6_tables: (C) 2000-2006 Netfilter Core Team
[  180.692646] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[  181.426186] tg3 :04:00.0 eth0: Link is down
[  184.867657] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[  184.870369] device eth2 entered promiscuous mode
[  185.310452] IPv6: ADDRCONF(NETDEV_CHANGE): tap1: link becomes ready
[  185.310517] br0: port 2(tap1) entered forwarding state
[  185.310540] br0: port 2(tap1) entered forwarding state
[  185.340931] IPv6: ADDRCONF(NETDEV_CHANGE): tap0: link becomes ready
[  185.341022] br0: port 1(tap0) entered forwarding state
[  185.341053] br0: port 1(tap0) entered forwarding state
[  186.308096] br0: port 2(tap1) entered disabled state
[  186.969420] tg3 :04:00.0 eth0: Link is up at 1000 Mbps, full duplex
[  186.969449] tg3 :04:00.0 eth0: Flow control is off for TX and off for RX
[  187.945130] e1000e: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[  187.945457] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[  200.392550] br0: port 1(tap0) entered forwarding state
[  251.635353] Key type dns_resolver registered
[  251.665092] NFS: Registering the id_resolver key type
[  251.665138] Key type id_resolver registered
[  251.665143] Key type id_legacy registered
[  499.831589] br0: port 1(tap0) entered disabled state
[  526.554515] device l2tp0 entered promiscuous mode
[  526.554713] br0: port 3(l2tp0) entered forwarding state
[  526.554730] br0: port 3(l2tp0) entered forwarding state
[  541.589078] br0: port 3(l2tp0) entered forwarding state
[  906.452815] device l2tp1 entered promiscuous mode
[  906.452948] br0: port 4(l2tp1) entered forwarding state
[  906.452964] br0: port 4(l2tp1) entered forwarding state
[  921.507056] br0: port 4(l2tp1) entered forwarding state
[22276.366266] perf samples too long (2505 > 2500), lowering 
kernel.perf_event_max_sample_rate to 5
[25678.723114] ICMPv6 checksum failed [2a01:348:6:4c4::1 > 2a01:348:6:4c4::2]
[33901.361167] nr_pdflush_threads exported in /proc is scheduled for removal
[33901.361441] sysctl: The scan_unevictable_pages sysctl/node-interface has 
been disabled for lack of a legitimate use case.  If you have one, please send 
an email to linux...@kvack.org.
[34047.286645] device br0 entered promiscuous mode
[34054.745393] device br0 left promiscuous mode
[34509.021723] device lo entered promiscuous mode
[34523.995709] device lo left promiscuous mode
[34565.706977] device lo entered promiscuous mode
[34574.849005] device lo left promiscuous mode
[94270.499549] ICMPv6 checksum failed [2a01:348:6:4c4::1 > 2a01:348:6:4c4::2]
[100331.491781] ICMPv6 checksum failed [2a01:348:6:4c4::1 > 2a01:348:6:4c4::2]
[106812.568949] ICMPv6 checksum failed [2a01:348:6:4c4::1 > 2a01:348:6:4c4::2]
[126549.143683] CE: hpet increased min_delta_ns to 20115 nsec
[126549.143785] CE: hpet increased min_delta_ns to 30172 nsec
[126549.143893] CE: hpet increased min_delta_ns to 45258 nsec
[156243.297918] br0: port 4(l2tp1) entered disabled state
[156243.297967] br0: port 3(l2tp0) entered disabled state
[156260.892403] device l2tp1 left promiscuous mode
[156260.892419] br0: port 4(l2tp1) entered disabled state
[156260.892763] device l2tp0 left promiscuous mode
[156260.892769] br0: port 3(l2tp0) entered disabled state
[156260.893006] device tap1 left promiscuous mode
[156260.893012] br0: port 2(tap1) entered disabled state
[156260.893230] device tap0 left promiscuous mode
[156260.893235] br0: port 1(tap0) enter

Bug#742917: tiff: CVE-2013-4243

[Jay Berkenbilt]

Michael Gilbert  wrote:

>>> The diff looks ok to me. Other distros did security announcements for
>>> this, so it would be ok to do a DSA also.  If you want, upload to
>>> security-master and I'll handle the DSA, otherwise you should discuss
>>> as a proposed update with the release team.
>>
>> Okay, I've uploaded to security-master.
>
> I should have clarified, squeeze no longer gets security support, so
> I'll have to reject that.  You'll need to do an lts upload for
> squeeze.

Yeah, I knew that squeeze's security support was over, but I wasn't sure
who/what had responsibility for the long-term support for squeeze. I
remember the announcement about LTS but hadn't realized/remembered that
there was a separate upload path. I found the information about how to
do it. Thanks!

-- 
Jay Berkenbilt 


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

Bug#751077: icedove: segfaults on startup outside of gdb

[Arthur Marsh]

Package: icedove
Version: 31.0~b1-2
Followup-For: Bug #751077

Dear Maintainer,

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

   * What led up to the situation?

With the 31.0~b1-2 version of icedove on i386, if starting up outside of gdb
get an illegal instruction message then a segfault.

If starting inside of gdb, program locks up when opening an attachment.
gdb is unable to obtain a stack trace.

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

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


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

Kernel: Linux 3.16.0-rc2 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages icedove depends on:
ii  debianutils   4.4
ii  fontconfig2.11.0-5
ii  libasound21.0.27.2-4
ii  libatk1.0-0   2.12.0-1
ii  libc6 2.19-3
ii  libcairo2 1.12.16-2
ii  libdbus-1-3   1.8.4-1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-1
ii  libffi6   3.1-2
ii  libfontconfig12.11.0-5
ii  libfreetype6  2.5.2-1
ii  libgcc1   1:4.9.0-7
ii  libgdk-pixbuf2.0-02.30.7-1
ii  libglib2.0-0  2.40.0-3
ii  libgtk2.0-0   2.24.23-1
ii  libhunspell-1.3-0 1.3.3-1
ii  libnspr4  2:4.10.6-1
ii  libnss3   2:3.16.1-1
ii  libpango-1.0-01.36.3-1
ii  libpangocairo-1.0-0   1.36.3-1
ii  libpangoft2-1.0-0 1.36.3-1
ii  libpixman-1-0 0.32.4-1
ii  libsqlite3-0  3.8.5-2
ii  libstartup-notification0  0.12-3
ii  libstdc++64.9.0-7
ii  libvpx1   1.3.0-2
ii  libx11-6  2:1.6.2-2
ii  libxext6  2:1.3.2-1
ii  libxrender1   1:0.9.8-1
ii  libxt61:1.1.4-1
ii  psmisc22.21-2
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages icedove recommends:
ii  myspell-en-au [myspell-dictionary]  2.1-5.4
ii  myspell-en-gb [myspell-dictionary]  1:3.3.0-4

Versions of packages icedove suggests:
ii  fonts-lyx 2.0.6-1
ii  libgssapi-krb5-2  1.12.1+dfsg-3

-- debconf-show failed


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

Bug#745556: Closing dialog for allowing invalid SSL certificate causes default to be accepted

[Rémi Denis-Courmont]

Le 2014-06-23 20:38, Jim Scadden a écrit :
Rémi, please could you advise if you would still like the behaviour 
to
be modified? If so, given that the user has already stated on the 
first
dialog box that they wish to connect to the server, and closing the 
2nd

dialog causes the certificate to only be accepted for the current
session, would you be happy for this bug to be tagged as 'wishlist'
since this is something could potentially require a substantial 
change

upstream?


I am not sure I see the wisdom in tagging a security problem as 
wishlist. "Current session" is more than enough for a MITM to the steal 
the IMAP or POP credentials and hijack the account. And in this case, it 
seems there is hardly any way out for the user: Except for xkill, I 
cannot think of any way to reject an untrusted connection here.


I'd argue the security team is in a better position than me to 
determine what to do though.


--
Rémi Denis-Courmont


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

Bug#752404: libc6: Does not account for two packages from different archs being present

[Ralf G. R. Bergs]

Package: libc6
Version: 2.19-3_i386
Severity: normal

Dear Maintainer,

I have both amd64 and i386 enabled on my system. When I upgraded the
system today I spotted the following error:

--- 8x --
Preparing to unpack .../archives/libc6_2.19-3_i386.deb ...
De-configuring libc6:amd64 (2.19-1) ...
dpkg-query: error: --listfiles needs a valid package name but 'libc6'
is not: ambiguous package name 'libc6' with more than one installed
instance

Use --help for help about querying packages.
Unpacking libc6:i386 (2.19-3) over (2.19-1) ...
Preparing to unpack .../libc6_2.19-3_amd64.deb ...
Unpacking libc6:amd64 (2.19-3) over (2.19-1) ...
--- 8x --

It seems that the deconfigure script does not account for multiple
versions of the package potentially being present on a system.

Thank you!

KR,

Ralf

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

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


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

Bug#749405: [Resolvconf-devel] Bug#749405: Bug#749405: Current Status + Moving Forward?

[Edward Allcutt]

Hi Thomas,

On Mon, 23 Jun 2014, Thomas Hood wrote:

I think it just needs to be tested.  Have you tested the proposed fix at
all?


I've been using the below minimal patch locally for a few weeks now. It 
works for me in the just-plain-ifupdown configuration use-case.


==
$ diff -u /lib/systemd/system/resolvconf.service /etc/systemd/system/resolvconf.service 
--- /lib/systemd/system/resolvconf.service	2014-06-23 14:24:03.306557959 +0100

+++ /etc/systemd/system/resolvconf.service  2014-06-23 14:17:55.006474686 
+0100
@@ -2,6 +2,7 @@
 Description=Nameserver information manager
 Documentation=man:resolvconf(8)
 DefaultDependencies=no
+Before=networking.service

 [Service]
 RemainAfterExit=yes
@@ -11,4 +12,4 @@
 ExecStop=/sbin/resolvconf --disable-updates

 [Install]
-WantedBy=network.target
+WantedBy=sysinit.target
==

nb. WantedBy=sysinit.target matches the "Default-Start: S" from the old 
init script and Before=networking.service corresponds to

"X-Start-Before:networking".

My earlier waffling about hotplugging is about a potential problem (which 
I'm not sure really exists). It shouldn't block this bug from being 
resolved.


--
Edward Allcutt


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

Bug#752405: "fatal: ambiguous argument ..." when checkout specific tarball

[陳昌倬]

Package: pristine-tar
Version: 1.32
Severity: normal

Hi,

I cannot use pristine-tar to generate gcin_2.8.2+dfsg1.orig.tar.xz in
debian repository. The following error messages are showed:


fatal: ambiguous argument 
'830849db2cb02811856ebe77cebf4daee9e60d27^{tree}': unknown revision or path not 
in the working tree.
Use '--' to separate paths from revisions, like this:
'git  [...] -- [...]'
pristine-tar: git archive --format=tar 
830849db2cb02811856ebe77cebf4daee9e60d27\^\{tree\} | (cd 
'/tmp/pristine-tar._KiJdm36ZU' && tar x)
fatal: Not a valid object name
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
pristine-tar: command failed: git archive --format=tar 
830849db2cb02811856ebe77cebf4daee9e60d27\^\{tree\} | (cd 
'/tmp/pristine-tar._KiJdm36ZU' && tar x)


The following is reprocedure steps:

- debcheckout gcin
- cd gcin
- git checkout pristine-tar
- pristine-tar checkout gcin_2.8.2+dfsg1.orig.tar.xz


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

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

Versions of packages pristine-tar depends on:
ii  libbz2-1.01.0.6-5
ii  libc6 2.19-1
ii  perl-modules  5.18.2-4
ii  tar   1.27.1-2
ii  xdelta1.1.3-9.1
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages pristine-tar recommends:
ii  bzip2 1.0.6-5
ii  pbzip21.1.8-1
ii  xz-utils  5.1.1alpha+20120614-2

pristine-tar suggests no packages.

-- no debconf information

-- 
ChangZhuo Chen (陳昌倬) 
http://czchen.info/
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D


signature.asc
Description: Digital signature

Bug#751077: Info received (icedove: segfaults on startup outside of gdb)

[Arthur Marsh]

Debian Bug Tracking System wrote on 23/06/14 22:57:

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  Christoph Goehre 

If you wish to submit further information on this problem, please
send it to 751...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.



Correction, with teh new version of icedove, I had a segfault 
immediately when starting normally, but not when starting in safe mode 
until I opened an attachment.


I did obtain a backtrace:

Program received signal SIGSEGV, Segmentation fault.
0xad14b008 in ?? ()
(gdb) bt
#0  0xad14b008 in ?? ()
#1  0xad0fb148 in ?? ()
#2  0xad738f99 in ?? ()
#3  0xacf17210 in ?? ()
#4  0xb40cc8ca in ?? ()
#5  0xb622e117 in EnterBaseline (data=..., cx=0x1)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jit/BaselineJIT.cpp:124

#6  js::jit::EnterBaselineMethod (cx=0xb7d25ba0, state=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jit/BaselineJIT.cpp:155

#7  0xb64523d4 in Interpret (cx=0xbfff6550, cx@entry=0xb7d25ba0, state=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:2658

#8  0xb64536da in js::RunScript (cx=0xb7d25ba0, state=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:422

#9  0xb6453930 in js::Invoke (cx=0xb7d25ba0, args=...,
construct=js::NO_CONSTRUCT)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:494

#10 0xb6453e57 in js::Invoke (cx=0xb7d25ba0, thisv=..., fval=..., argc=3,
argv=0xbfff6e1c, rval=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:5---Type 
 to continue, or q  to quit---

31
#11 0xb633e81c in JS_CallFunctionValue (cx=0xb7d25ba0, obj=..., fval=...,
args=..., rval=...)
at /build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jsapi.cpp:5049
#12 0xb54c8c8b in nsXPCWrappedJSClass::CallMethod (this=0xad496f10,
wrapper=0xbfff6cdb, methodIndex=4, info_=0xb1fd587c,
nativeParams=0xbfff6ee0)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/xpconnect/src/XPCWrappedJSClass.cpp:1272
#13 0xb54c5621 in nsXPCWrappedJS::CallMethod (this=0xad4ac580, 
methodIndex=4,

info=0xb1fd587c, params=0xbfff6ee0)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/xpconnect/src/XPCWrappedJS.cpp:517

#14 0xb4c19c68 in PrepareAndDispatch (methodIndex=, self=
0xad47e770, args=)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/xpcom/reflect/xptcall/src/md/unix/xptcstubs_gcc_x86_unix.cpp:60

#15 0xb4c191c4 in NS_InvokeByIndex () from /usr/lib/icedove/libxul.so
#16 0xb54cc05e in Invoke (this=)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/xpconnect/src/XPCWrappedNative.cpp:2391

#17 Call (this=)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/xpconnect/src/XPCWrappedNative.cpp:1732

---Type  to continue, or q  to quit---
#18 XPCWrappedNative::CallMethod (ccx=..., 
mode=XPCWrappedNative::CALL_METHOD)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/xpconnect/src/XPCWrappedNative.cpp:1699

#19 0xb54d1b92 in XPC_WN_CallMethod (cx=0xb7d25ba0, argc=1, vp=0xb1e82c78)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/xpconnect/src/XPCWrappedNativeJSOps.cpp:1284

#20 0xb6453a2e in CallJSNative (args=...,
native=0xb54d19f7 JS::Value*)>, cx=0xb7d25ba0)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jscntxtinlines.h:239

#21 js::Invoke (cx=0xb7d25ba0, args=..., construct=js::NO_CONSTRUCT)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:475

#22 0xb644871d in Interpret (cx=0xbfff6550, cx@entry=0xb7d25ba0, state=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:2620

#23 0xb64536da in js::RunScript (cx=0xb7d25ba0, state=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:422

#24 0xb6453930 in js::Invoke (cx=0xb7d25ba0, args=...,
construct=js::NO_CONSTRUCT)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:494

---Type  to continue, or q  to quit---
#25 0xb6453e57 in js::Invoke (cx=0xb7d25ba0, thisv=..., fval=..., argc=0,
argv=0x0, rval=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:531

#26 0xb6453ffe in js::InvokeGetterOrSetter (cx=0xb7d25ba0, obj=0xad3605b0,
fval=..., argc=0, argv=0x0, rval=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:603

#27 0xb639d65f in js::Shape::get (this=0xb0cd8868, cx=0xb7d25ba0,
receiver=..., obj=0xad3605b0, pobj=0xb0cd49d0, vp=...)
at 
/build/icedove-CFQaeN/iced

Bug#666525: pbuilder: NMU diff for upload 0.215+nmu1

[Thorsten Glaser]

Dear maintainer,

as announced, I have NMUd pbuilder with the precise debdiff attached.
I have uploaded this to DELAYED/10.

bye,
//mirabilos
-- 
“ah that reminds me, thanks for the stellar entertainment that you and certain
other people provide on the Debian mailing lists │ sole reason I subscribed to
them (I'm not using Debian anywhere) is the entertainment factor │ Debian does
not strike me as a place for good humour, much less German admin-style humour”diff -Nru pbuilder-0.215/debian/changelog pbuilder-0.215+nmu1/debian/changelog
--- pbuilder-0.215/debian/changelog 2013-03-30 03:06:05.0 +0100
+++ pbuilder-0.215+nmu1/debian/changelog2014-06-23 15:38:36.0 
+0200
@@ -1,3 +1,15 @@
+pbuilder (0.215+nmu1) unstable; urgency=low
+
+  [ Ivo De Decker ]
+  * Only set CCACHE_DIR when running as build user. (closes: #666525)
+
+  [ Thorsten Glaser ]
+  * Non-maintainer upload.
+  * Disable network access during build by default on Linux (Closes: #748967)
+  * Replace use of su as requested by Helmut Grohne (Closes: #747946)
+
+ -- Thorsten Glaser   Thu, 22 May 2014 20:37:51 +0200
+
 pbuilder (0.215) unstable; urgency=low
 
   * Do not try to use /dev/shm if /run/shm is not present. (closes: #702811, 
#702102)
diff -Nru pbuilder-0.215/pbuilder-buildpackage 
pbuilder-0.215+nmu1/pbuilder-buildpackage
--- pbuilder-0.215/pbuilder-buildpackage2012-03-13 09:25:15.0 
+0100
+++ pbuilder-0.215+nmu1/pbuilder-buildpackage   2014-06-23 15:37:33.0 
+0200
@@ -37,18 +37,39 @@
 # environment, so cowdancer shouldn't have to run, and fakeroot
 # should be running later, so it shouldn't matter.
 # LOGNAME: set this to shut up some tools.
-# su -p : switch to user preserving env vars, we need most of them. 
-SUTOUSER="env LD_PRELOAD= LOGNAME=$BUILDUSERNAME su -p $BUILDUSERNAME"
+SUTOUSER=" env LD_PRELOAD= LOGNAME=$BUILDUSERNAME /sbin/start-stop-daemon 
--start --pidfile /dev/null --chuid $BUILDUSERNAME --startas /bin/sh"
 DEBBUILDOPTS="${DEBBUILDOPTS:+$DEBBUILDOPTS }-rfakeroot"
 EXTRAPACKAGES="${EXTRAPACKAGES} fakeroot"
 log "I: using fakeroot in build."
 else
 # run the build in root
-SUTOUSER="su -p "
 BUILDUSERID=0
 BUILDUSERNAME=root
+SUTOUSER=" env LOGNAME=$BUILDUSERNAME /bin/sh"
 fi
 
+case $USENETWORK in
+yes)
+   if [ "$DEB_BUILD_ARCH_OS" = "linux" ]; then
+   # omit the warning when running on kFreeBSD or Hurd
+   log "W: pbuilder: network will not be disabled during build!"
+   fi
+   ;;
+*)
+   if $CHROOTEXEC /usr/bin/unshare -n true; then
+   USENETWORK=no
+   SUTOUSER="/usr/bin/unshare -n -- $SUTOUSER"
+   log "I: pbuilder: network access will be disabled during build"
+   else
+   USENETWORK=yes
+   if [ "$DEB_BUILD_ARCH_OS" = "linux" ]; then
+   log "W: pbuilder: unshare CLONE_NEWNET not available"
+   fi
+   log "I: pbuilder: network access is available during build!"
+   fi
+   ;;
+esac
+
 
 # created files should have these UID/GIDs outside of chroot.
 BUILDRESULTUID="${BUILDRESULTUID:-${SUDO_UID:-0}}"
@@ -92,7 +113,9 @@
 
 recover_aptcache
 createbuilduser
+CCACHE_ENV=
 setup_ccache
+SUTOUSER=${SUTOUSER/ env / env $CCACHE_ENV}
 log "I: Installing the build-deps"
 executehooks "D"
 trap saveaptcache_umountproc_cleanbuildplace_trap exit sighup sigpipe
diff -Nru pbuilder-0.215/pbuilder-buildpackage-funcs 
pbuilder-0.215+nmu1/pbuilder-buildpackage-funcs
--- pbuilder-0.215/pbuilder-buildpackage-funcs  2012-03-31 06:51:11.0 
+0200
+++ pbuilder-0.215+nmu1/pbuilder-buildpackage-funcs 2014-06-23 
15:38:09.0 +0200
@@ -107,8 +107,7 @@
 mkdir -p "$BUILDPLACE/$CCACHEDIR"
 fi
 chown -R $BUILDUSERID:$BUILDUSERID "$BUILDPLACE/$CCACHEDIR"
-# Unfortunate difference between pbuilder-style and ccache-style config
-# env vars   :-/
-export CCACHE_DIR="$CCACHEDIR"
+   CCACHE_ENV="CCACHE_DIR=$CCACHEDIR"
+   unset CCACHE_DIR
 fi
 }
diff -Nru pbuilder-0.215/pbuilderrc pbuilder-0.215+nmu1/pbuilderrc
--- pbuilder-0.215/pbuilderrc   2013-03-26 09:49:45.0 +0100
+++ pbuilder-0.215+nmu1/pbuilderrc  2014-06-23 15:29:47.0 +0200
@@ -10,6 +10,7 @@
 #export http_proxy=http://your-proxy:8080/
 USEPROC=yes
 USEDEVPTS=yes
+USENETWORK=no
 USERUNSHM=yes
 USEDEVFS=no
 BUILDRESULT=/var/cache/pbuilder/result/
diff -Nru pbuilder-0.215/pbuilderrc.5 pbuilder-0.215+nmu1/pbuilderrc.5
--- pbuilder-0.215/pbuilderrc.5 2013-03-26 10:04:06.0 +0100
+++ pbuilder-0.215+nmu1/pbuilderrc.52014-06-23 15:29:47.0 +0200
@@ -380,6 +380,14 @@
 .B /dev/pts
 being mounted.
 .TP
+.BI "USENETWORK=" "no"
+Specify
+.B yes
+when you do not want to disable network access during build.
+Network is not available on a Debian buildd, so you might
+want to keep the default.
+Disabling network access currently onl

Bug#752406: RFP: lilyterm -- LilyTerm is a terminal emulator based off of libvte that aims to be fast and lightweight.

[Alex Rozenshteyn]

Package: wnpp
Severity: wishlist

* Package name: lilyterm
  Version : 0.9.9.2
  Upstream Author : Chao-Ming Lu 
* URL : http://lilyterm.luna.com.tw/
* License : GPLv3
  Programming Lang: C
  Description : LilyTerm is a terminal emulator based off of libvte that 
aims to be fast and lightweight.

LilyTerm is a lightweight terminal emulator with unicode support that
is not associated with any desktop environment and more user-friendly
than urxvt. I believe it fills a niche.

There is a debian package already provided.


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

Bug#750811: Bug#751532: Bug#750811: brltty: FTBFS on kfreebsd*

[Matthias Klose]

Control: severity 751532 important

Am 15.06.2014 20:43, schrieb Paul Gevers:
> On 15-06-14 17:31, Samuel Thibault wrote:
>> This is most probably similar to #714559 which had the same issue.
> 
> Yes, I agree. But interestingly enough, building liblouisutdml already 
> failed in gcc-4.8 while brltty (and libbluray) only now start to fail with
> gcc-4.9, so something must have changed.

on kfreebsd, gcj is used again as the default jdk.  I think at some time I
provided s symlink pointing to linux/jni_md.h in openjdk so you don't see this
on architectures where java points to openjdk.

> Shouldn't the package for kfreebsd* have the files in a different 
> sub-directory? linux just feels wrong on kfreebsd. I expect (but don't know
> for sure) that the resolver is smart enough to look in a sub-directory
> matching the os, but as I would expect not look in the directory named by a
> different os.

Both gcj and openjdk use the linux subdirectory on all posix architectures
upstream.  I don't see why this should be changed just locally without
addressing this upstream.

so for now packages building jni bindings should have both /include
and /include/linux on the include path.  brltty having kfreebsd-gnu
seems to be wrong in any case.

As a long term solution try to get this directory name defined upstream,
however I see this ending up as a wontfix issue ... so it seems to be better
to make sure that all packages use both include paths, and hardcoding the
second one as `linux' on all architectures.


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

Bug#752395: CVE request: python: _json module is vulnerable to arbitrary process memory read

[Vasyl Kaigorodov]

Hello,

It was reported [1] that Python built-in _json module have a flaw
(insufficient bounds checking), which allows a local user to read
current process' arbitrary memory.
From initial bug report [1]:
...
The sole prerequisites of this attack are that the attacker is able to
control or influence the two parameters of the default scanstring
function: the string to be decoded and the index.

The bug is caused by allowing the user to supply a negative index
value. The index value is then used directly as an index to an array
in the C code; internally the address of the array and its index are
added to each other in order to yield the address of the value that is
desired. However, by supplying a negative index value and adding this
to the address of the array, the processor's register value wraps
around and the calculated value will point to a position in memory
which isn't within the bounds of the supplied string, causing the
function to access other parts of the process memory.
...

Can a CVE ID be assigned to this issue please?
Also CC'ing the Debian bugreport here.


References:
[1] Upstream bug report with additional technical details: 
http://bugs.python.org/issue21529
[2] Debian bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752395
[3] RedHat bug tracker: https://bugzilla.redhat.com/show_bug.cgi?id=1112285

Thanks.
-- 
Vasyl Kaigorodov | Red Hat Product Security Team
PGP:  0xABB6E828 A7E0 87FF 5AB5 48EB 47D0 2868 217B F9FC ABB6 E828


pgpXHMfkq0QtO.pgp
Description: PGP signature

Bug#751077: Info received (Bug#751077: Info received (icedove: segfaults on startup outside of gdb))

[Arthur Marsh]

Debian Bug Tracking System wrote on 23/06/14 23:15:

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  Christoph Goehre 

If you wish to submit further information on this problem, please
send it to 751...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.



I disabled all plug-ins and tried gdb icedove, and still had a segfault:

Program received signal SIGSEGV, Segmentation fault.
0xa5c37008 in ?? ()
(gdb) bt
#0  0xa5c37008 in ?? ()
#1  0xb6239f34 in EnterIon (data=..., cx=0x243)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jit/Ion.cpp:2376

#2  js::jit::IonCannon (cx=0xa5b710c0, state=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jit/Ion.cpp:2456

#3  0xb6453845 in js::RunScript (cx=0xa5b710c0, state=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:401

#4  0xb6453930 in js::Invoke (cx=0xa5b710c0, args=...,
construct=js::NO_CONSTRUCT)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:494

#5  0xb644871d in Interpret (cx=0x1, cx@entry=0xa5b710c0, state=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:2620

#6  0xb64536da in js::RunScript (cx=0xa5b710c0, state=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:422

#7  0xb6453930 in js::Invoke (cx=0xa5b710c0, args=...,
construct=js::NO_CONSTRUCT)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:494

#8  0xb6453e57 in js::Invoke (cx=0xa5b710c0, thisv=..., fval=..., argc=1,
argv=0xb1e82620, rval=...)
---Type  to continue, or q  to quit---
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:531

#9  0xb63c3058 in js::DirectProxyHandler::call (
this=0xb7c54810 , 
cx=0xa5b710c0,

proxy=..., args=...)
at /build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jsproxy.cpp:448
#10 0xb640c021 in js::CrossCompartmentWrapper::call (
this=0xb7c54810 , 
cx=0xa5b710c0,

wrapper=..., args=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jswrapper.cpp:464

#11 0xb63c6a6f in call (args=..., proxy=..., cx=0xa5b710c0)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jsproxy.cpp:2659

#12 js::proxy_Call (cx=0xa5b710c0, argc=1, vp=0xb1e82610)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jsproxy.cpp:3062

#13 0xb6453b0d in CallJSNative (args=...,
native=0xb63c69d0 JS::Value*)>,

cx=0xa5b710c0)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jscntxtinlines.h:239

#14 js::Invoke (cx=0xa5b710c0, args=..., construct=js::NO_CONSTRUCT)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:468

#15 0xb644871d in Interpret (cx=0x1, cx@entry=0xa5b710c0, state=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:2---Type 
 to continue, or q  to quit---

620
#16 0xb64536da in js::RunScript (cx=0xa5b710c0, state=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:422

#17 0xb6453930 in js::Invoke (cx=0xa5b710c0, args=...,
construct=js::NO_CONSTRUCT)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:494

#18 0xb6453e57 in js::Invoke (cx=0xa5b710c0, thisv=..., fval=..., argc=1,
argv=0xbfffb8f0, rval=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:531

#19 0xb6453ffe in js::InvokeGetterOrSetter (cx=0xa5b710c0, obj=0xa0824100,
fval=..., argc=1, argv=0xbfffb8f0, rval=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:603

#20 0xb639d748 in js::Shape::set (this=0xa2fd71c0, cx=0xa5b710c0, obj=...,
receiver=..., strict=false, vp=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Shape-inl.h:95

#21 0xb63a7905 in js::baseops::SetPropertyHelper<(js::ExecutionMode)0> (
cxArg=0xa5b710c0, obj=..., receiver=..., id=...,
qualified=js::baseops::Qualified, vp=..., strict=false)
at /build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jsobj.cpp:4948
#22 0xb6449616 in setGeneric (strict=, vp=..., id=...,
---Type  to continue, or q  to quit---
receiver=..., obj=..., cx=)
at /build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/jsobj.h:1024
#23 SetPropertyOperation (rval=..., lval=..., pc=, 
script=...,

cx=)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:340

#24 Interpret (cx=0x1, cx@entry=0xa5b710c0, state=...)
at 
/build/icedove-CFQaeN/icedove-31.0~b1/mozilla/js/src/vm/Interpreter.cpp:2456

#25 0xb645

Bug#752408: finish-install: ppc64el support

[Frederic Bonnard]

Package: finish-install
Version: 2.46
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el


Dear Maintainer,

here is a patch from Ubuntu so that console is handled properly on the ppc64le 
architecture
in a guest or in the host.


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

Kernel: Linux 3.14-1-powerpc64le (SMP w/1 CPU core)
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/dash
diff -Nru finish-install-2.46/finish-install.d/90console finish-install-2.46/finish-install.d/90console
--- finish-install-2.46/finish-install.d/90console	2011-08-01 01:00:32.0 +
+++ finish-install-2.46/finish-install.d/90console	2014-06-06 10:11:36.0 +
@@ -93,7 +93,7 @@
 if [ -e $DT_ROOT/chosen/linux,stdout-path ]; then
 	chosen_dev=$(cat $DT_ROOT/chosen/linux,stdout-path)
 	case $chosen_dev in
-	/vdevice/vty@3000)
+	/vdevice/vty@3000|/vdevice/vty@7100)
 		case $(cat ${DT_ROOT}${chosen_dev}/compatible) in
 		hvterm-protocol)
 			console=hvsi0 ;;
@@ -109,6 +109,12 @@
 		console=hvsi1 ;;
 	/spider/serial)
 		console=hvc0 ;;
+	/ibm,opal/consoles/serial@0)
+		console=hvc0 ;;
+	/ibm,opal/consoles/serial@1)
+		console=hvc1 ;;
+	/ibm,opal/consoles/serial@2)
+		console=hvc2 ;;
 	*)
 		exit 0 ;;
 	esac