Bug#751365: New upstream release and Python 3 support

[Thomas Goirand]

Package: pykerberos
Version: 1.1+svn10616-2
Severity: important
Tags: patch

Dear maintainers,

There's a new version of pykerberos available here:
https://pypi.python.org/pypi/pykerberos

This version (eg: 1.1.5) now includes support for Python 3. So it'd be nice
to package this version and to add support for Python 3.

To speed up this process, I've worked on the package, and added numerous
improvements. I have dropped my changes over here:

http://xen01.node0184.gplhost.com/pykerberos/

In there, you will also find a "patches" folder, with all the individual
patches against the Git of the project. You can also git pull from:

http://anonscm.debian.org/git/users/zigo/pykerberos.git

if you find this easier. The changelog which I propose is as follow:

pykerberos (1.1.5-0.1) unstable; urgency=medium

  * Non-maintainer upload.
  * New upstream release.
  * Added a debian/gbp.conf.
  * Added extend-diff-ignore = "^[^/]*[.]egg-info/" in debian/source/options.
  * Added python3 support.
  * Removed useless debian/pyversions and debian/pycompat.
  * Canonical VCS URLs.
  * Added a watch file.
  * debian/copyright using parseable format 1.0.
  * Added a homepage field.
  * Drops conflicts + replaces, as this is a very old version that had the
issue and even Wheezy should be unaffected now.
  * Also cleans the build folder to allow double builds.
  * Disabled some unused dh target to speed-up the build.
  * Added add-function-to-inquire-on-credentials.patch (Closes: #744049).

If you have no time to work on this, please allow me to NMU the package.
I indeed need this to be able to package python-requests-kerberos for
OpenStack, and best would be to have the above Python 3 support ASAP.

Cheers,

Thomas Goirand (zigo)


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

Bug#745427: Proposed debdiff for wheezy

[Salvatore Bonaccorso]

Hi

Attached is the proposed debdiff I would like to propose to the
release-team for an update trough pu. This would make the way free for
the removal of libplrpc-perl from stable.

Note the proxy modules are still installed, but get a security warning
in documentation as we did for unstable.

Regards,
Salvatore
diff -Nru libdbi-perl-1.622/debian/changelog libdbi-perl-1.622/debian/changelog
--- libdbi-perl-1.622/debian/changelog  2012-06-07 12:46:26.0 +0200
+++ libdbi-perl-1.622/debian/changelog  2014-06-11 22:26:24.0 +0200
@@ -1,3 +1,15 @@
+libdbi-perl (1.622-1+deb7u1) wheezy; urgency=low
+
+  * Team upload.
+  * Remove libplrpc-perl from Build-Depends and Depends (Closes: #745427)
+  * warn users of DBI::Proxy about its unsafe usage of Storable
+patch by Petr Písař from
+https://rt.cpan.org/Public/Bug/Display.html?id=90475
+  * Add dont-install-dbiproxy-script.patch patch.
+Don't install dbiproxy script into /usr/bin.
+
+ -- Salvatore Bonaccorso   Tue, 10 Jun 2014 09:05:28 +0200
+
 libdbi-perl (1.622-1) unstable; urgency=low
 
   * New upstream release
diff -Nru libdbi-perl-1.622/debian/control libdbi-perl-1.622/debian/control
--- libdbi-perl-1.622/debian/control2012-06-07 12:46:26.0 +0200
+++ libdbi-perl-1.622/debian/control2014-06-11 22:26:24.0 +0200
@@ -9,7 +9,6 @@
  Nicholas Bamber ,
  Alessandro Ghedini 
 Build-Depends: perl, debhelper (>= 9),
- libplrpc-perl,
  libtest-pod-coverage-perl,
  libtest-pod-perl,
  perl (>= 5.10.1) | libtest-simple-perl (>= 0.90)
@@ -20,7 +19,7 @@
 
 Package: libdbi-perl
 Architecture: any
-Depends: ${misc:Depends}, ${perl:Depends}, ${shlibs:Depends}, libplrpc-perl
+Depends: ${misc:Depends}, ${perl:Depends}, ${shlibs:Depends}
 Provides: perl-dbdabi-${perl-dbdabi-version}
 Breaks: libdbd-anydata-perl (<< 0.09+),
  libdbd-csv-perl (<< 0.3000),
diff -Nru libdbi-perl-1.622/debian/patches/Security-notice-for-Proxy.patch 
libdbi-perl-1.622/debian/patches/Security-notice-for-Proxy.patch
--- libdbi-perl-1.622/debian/patches/Security-notice-for-Proxy.patch
1970-01-01 01:00:00.0 +0100
+++ libdbi-perl-1.622/debian/patches/Security-notice-for-Proxy.patch
2014-06-11 22:26:24.0 +0200
@@ -0,0 +1,56 @@
+From cd8fcbbf402e1d70c9f325f8b0fcd99e02cf14be Mon Sep 17 00:00:00 2001
+From: Petr Písař 
+Date: Mon, 18 Nov 2013 12:52:09 +0100
+Subject: [PATCH] Security notice for Proxy
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+Bug: https://rt.cpan.org/Public/Bug/Display.html?id=90475
+
+PlRPC is not secure due to Storable. Warn Proxy users about it.
+
+Signed-off-by: Petr Písař 
+---
+ lib/DBD/Proxy.pm   | 7 +++
+ lib/DBI/ProxyServer.pm | 7 +++
+ 2 files changed, 14 insertions(+)
+
+diff --git a/lib/DBD/Proxy.pm b/lib/DBD/Proxy.pm
+index 287b2dc..5948255 100644
+--- a/lib/DBD/Proxy.pm
 b/lib/DBD/Proxy.pm
+@@ -974,6 +974,13 @@ The workaround is storing the modified local copy back to 
the server:
+   $dbh->{"csv_tables"} = $tables;
+ 
+ 
++=head1 SECURITY WARNING
++
++L used underneath is not secure due to serializing and
++deserializing data with L module. Use the proxy driver only in
++trusted environment.
++
++
+ =head1 AUTHOR AND COPYRIGHT
+ 
+ This module is Copyright (c) 1997, 1998
+diff --git a/lib/DBI/ProxyServer.pm b/lib/DBI/ProxyServer.pm
+index 68ad4af..78a0d78 100644
+--- a/lib/DBI/ProxyServer.pm
 b/lib/DBI/ProxyServer.pm
+@@ -867,6 +867,13 @@ Don't try to put parameters into the sql-query like this:
+ =back
+ 
+ 
++=head1 SECURITY WARNING
++
++L used underneath is not secure due to serializing and
++deserializing data with L module. Use the proxy driver only in
++trusted environment.
++
++
+ =head1 AUTHOR
+ 
+ Copyright (c) 1997Jochen Wiedmann
+-- 
+1.8.3.1
+
diff -Nru libdbi-perl-1.622/debian/patches/dont-install-dbiproxy-script.patch 
libdbi-perl-1.622/debian/patches/dont-install-dbiproxy-script.patch
--- libdbi-perl-1.622/debian/patches/dont-install-dbiproxy-script.patch 
1970-01-01 01:00:00.0 +0100
+++ libdbi-perl-1.622/debian/patches/dont-install-dbiproxy-script.patch 
2014-06-11 22:26:24.0 +0200
@@ -0,0 +1,17 @@
+Description: Don't install /usr/bin/dbiproxy
+Origin: vendor
+Forwarded: no
+Author: Salvatore Bonaccorso 
+Last-Update: 2014-06-10
+
+--- a/Makefile.PL
 b/Makefile.PL
+@@ -120,7 +120,7 @@ my %opts = (
+   'DBD::PO' => '2.10',
+ },
+ LICENSE => 'perl',
+-EXE_FILES => [ "dbiproxy$ext_pl", "dbiprof$ext_pl", "dbilogstrip$ext_pl" 
],
++EXE_FILES => [ "dbiprof$ext_pl", "dbilogstrip$ext_pl" ],
+ DIR => [ ],
+ dynamic_lib => { OTHERLDFLAGS => "$::opt_g" },
+ clean => { FILES=> "\$(DISTVNAME) Perl.xsi t/zv*_*.t dbi__null_test_tmp*"
diff -Nru libdbi-perl-1.622/debian/patches/series 
libdbi-perl-1.622/debian/patches/series
--- libdbi-perl-1.622/debian/patches/series 2012-06-07 12:46:26.0 
+0200
+++ libdbi-perl-1.622/debian/patches/series 2014-06-11 22:26:24.0

Bug#751363: dpkg: change gnu-triplet for i386 to i586-linux-gnu

[Guillem Jover]

On Thu, 2014-06-12 at 08:41:42 +0200, Guillem Jover wrote:
> On Thu, 2014-06-12 at 08:16:36 +0200, Helmut Grohne wrote:
> > Package: dpkg
> > Version: 1.17.10
> > Severity: normal
> > User: helm...@debian.org
> > Usertags: rebootstrap
> 
> > Packages built with gcc-4.9 on i386 no longer work with actual i386 or
> > i486 processors. Consequently, gcc has already moved on and changed the
> > triplet from i486-linux-gnu to i586-linux-gnu. Please apply this change
> > to dpkg as well. This change is important for tools, that compute cross
> > toolchain package names using dpkg-architecture such as rebootstrap[1].
> 
> Thanks for the patch. Although I'll not be applying it yet, until I've

Err, obviously there was no explicit patch, read that as applying this
change. :)

Thanks,
Guillem


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

Bug#751363: dpkg: change gnu-triplet for i386 to i586-linux-gnu

[Guillem Jover]

Hi!

On Thu, 2014-06-12 at 08:16:36 +0200, Helmut Grohne wrote:
> Package: dpkg
> Version: 1.17.10
> Severity: normal
> User: helm...@debian.org
> Usertags: rebootstrap

> Packages built with gcc-4.9 on i386 no longer work with actual i386 or
> i486 processors. Consequently, gcc has already moved on and changed the
> triplet from i486-linux-gnu to i586-linux-gnu. Please apply this change
> to dpkg as well. This change is important for tools, that compute cross
> toolchain package names using dpkg-architecture such as rebootstrap[1].

Thanks for the patch. Although I'll not be applying it yet, until I've
analyzed the current situation properly. I find it very unfortunate that
the triplet was not switched to use the generic i386-linux-gnu, as is
used by all of our other ports, so that we don't need to keep changing
this in dpkg to match or not what the gcc in use might be using. :/
(With the switch the triplet for cross-compilers will be wrong depending
on the gcc version being used…)

This does not seem to have been announced to the developers at large
either? There were some complains about the initial switch to making
gcc build with -march=i586 by default around 2011.

See also .

Thanks,
Guillem


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

Bug#750846: wheezy-pu: package clamav/0.98.1+dfsg-1+deb7u3

[Adam D. Barratt]

Control: tags -1 + pending

On 2014-06-09 23:17, Scott Kitterman wrote:

On Monday, June 09, 2014 23:05:21 Adam D. Barratt wrote:

On Sat, 2014-06-07 at 10:05 -0400, Scott Kitterman wrote:
> This is a small, low risk change cherry-picked from upstream that fixes a
> significant issue reported by a Debian Wheezy user.  We had intended to
> wait for the final 0.98.4 release and just fix this with the next package
> update, but that release has been unaccountably delayed, so I think it
> makes sense to go ahead and fix this issue while we wait for upstream to
> get 0.98.4 out the door.

Please go ahead; thanks.


clamav/0.98.1+dfsg-1+deb7u4 uploaded.


Flagged for acceptance; thanks.

Regards,

Adam


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

Bug#750860: xorg crashes randomly, floating point exception (synaptics' fault?)

[niky 45]

ok, something like 4 days later, I have had some other problems related to
the new kernel, but the xorg hasn't crashed. so, problem solved.

thanks for your help.

*note: I'm not sure if it was the new kernel OR the synaptics driver in
experimental... since I updated both things.


2014-06-07 21:38 GMT+02:00 niky 45 :

> oh. alright. It seems logical that random old packages from experimental
> are not supported.
>
> for now, I'm running the latest sid kernel (I installed the generic
> linux-image package to let it handle the kernel updates). the cpufreq
> config files are not there (they're part or the kernel), but if it behaves
> as expected, then I'll not miss them. (I mean, I can actually upgrade to a
> new kernel if cpufreq works as I'm expecting, even without those files)
>
> as for the synaptics in experimental, I already installed it, and I think
> the xserver has crashed after that, but I'm not sure. I mean, I have
> updated it today, and I have seen like three crashes today, but I'm not
> sure if the last crash was previous to the update or after it. Also, I
> didn't restarted the server after the update, so... It may well have been
> that the old driver was still loaded and crashed.
>
> as for mixing branches, I know, I know. not the best thing to do. but I
> have been using debian for a while, and well, I can manage that (as in,
> I know it's prone to break, but I don't mind fixing it every now and
> then).
>
> anyway, I'll test everything for a while and update you with the results.
>
> thanks.
>
>
> 2014-06-07 21:02 GMT+02:00 maximilian attems :
>
> staying on random old packages is not supported,
>> stable has lots of fixes on top of 3.2.0
>>
>>
>> On Sat, Jun 07, 2014 at 08:54:29PM +0200, niky 45 wrote:
>> > oh. I thought that since the kernel in stable is the 3.2.0, mine (3.6.9)
>> > wouldn't be too outdated...
>>
>> also randomly mixing stable and testing is no good,
>> please either switch to one distribution or the other.
>>
>> while you are it there is a new synpatics driver in experimental,
>> which goes with the xorg from testing.
>>
>> No idea about the cpufreq blurb.
>>
>> best,
>>
>> --
>> maks
>>
>
>
>
> --
> >> niky45 <<
>
>
>


-- 
>> niky45 <<

Bug#751364: php5: heap-based buffer overflow in DNS TXT record parsing

[Salvatore Bonaccorso]

Source: php5
Severity: grave
Tags: security upstream

Hi

A heap-based buffer overflow was commited in [1], Red Hat Bugzilla
reference at [2].

 [1] 
https://github.com/php/php-src/commit/b34d7849ed90ced9345f8ea1c59bc8d101c18468
 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1108447

A CVE assignment is pending. Could you also mark affected versions for
the BTS? From a quick(!) look it seems that all versions have the
vulnerable code present.

Regards,
Salvatore


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

Bug#751363: dpkg: change gnu-triplet for i386 to i586-linux-gnu

[Helmut Grohne]

Package: dpkg
Version: 1.17.10
Severity: normal
User: helm...@debian.org
Usertags: rebootstrap

Dear dpkg maintainers,

Packages built with gcc-4.9 on i386 no longer work with actual i386 or
i486 processors. Consequently, gcc has already moved on and changed the
triplet from i486-linux-gnu to i586-linux-gnu. Please apply this change
to dpkg as well. This change is important for tools, that compute cross
toolchain package names using dpkg-architecture such as rebootstrap[1].

For reference: The bug that changed i386 to i486 was #310394.

Helmut

[1] https://wiki.debian.org/HelmutGrohne/rebootstrap


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

Bug#747252: lightdm: AppArmor parser error in /etc/apparmor.d/abstractions/lightdm_chromium-browser

[Yves-Alexis Perez]

On jeu., 2014-06-12 at 00:49 -0400, Daniel Richard G. wrote:
> Yves, you removed /etc/apparmor.d/lightdm-guest-session from the
> package (via a debhelper exclusion directive), but you didn't exclude
> /etc/apparmor.d/abstractions/lightdm_chromium-browser, which is the
> profile that was generating the error in the first place  >_<


Well, I followed intrigeri remark: since guest session is not working
anyway, there's no point in having a broken AppArmor profile for that.
That's not the case for the lightdm_chromium-browser one, is it?

In any case, please provide a working patch against the current package.
I won't do anything more on this until someone actually test the
changes.
-- 
Yves-Alexis


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

Bug#750920: missing dependency, broken interpreter

[Scott Kitterman]

On Sunday, June 08, 2014 15:00:00 Stefan Bühler wrote:
> Package: attic
> Version: 0.10-1
> Severity: grave
> 
> Hi,
> 
> attic uses #!/usr/bin/python3 as interpreter, but has native (cython)
> modules that were compiled with a certain python3 version (3.3 in the
> archive, but depends on python3-dev version at build time).
...
> Rebuilding the package with python3-dev from current testing also fixes
> the problem.

Just rebuilding doesn't solve the entire problem.  The package depends are 
still wrong and it'll just break again the next time we change python3 
versions.  NMU debdiff attached.  I intend to upload this to delay/3.diff -Nru attic-0.10/debian/changelog attic-0.10/debian/changelog
--- attic-0.10/debian/changelog	2014-02-06 11:47:23.0 -0500
+++ attic-0.10/debian/changelog	2014-06-12 01:39:14.0 -0400
@@ -1,3 +1,16 @@
+attic (0.10-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Generate correct python interpreter dependencies with dh_python3
+(Closes: #750920)
+- Add dh-python to build-depends
+- Add python3:Depends
+- Add dh_python3 to debian/rules
+- Add additional dpkg-gencontrol call to expand python3:Depends generated
+  by dh_python3
+
+ -- Scott Kitterman   Wed, 11 Jun 2014 14:57:18 -0400
+
 attic (0.10-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru attic-0.10/debian/control attic-0.10/debian/control
--- attic-0.10/debian/control	2014-02-06 11:47:37.0 -0500
+++ attic-0.10/debian/control	2014-06-12 01:38:11.0 -0400
@@ -2,7 +2,7 @@
 Section: admin
 Priority: extra
 Maintainer: Clint Adams 
-Build-Depends: python3-dev, python3-openssl, python3-msgpack
+Build-Depends: dh-python, python3-dev, python3-openssl, python3-msgpack
 Standards-Version: 3.9.5
 Homepage: https://pythonhosted.org/Attic/
 Vcs-Git: git://git.debian.org/collab-maint/attic.git
@@ -10,7 +10,7 @@
 
 Package: attic
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, python3, python3-openssl, python3-msgpack
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, python3-openssl, python3-msgpack
 Recommends: python3-llfuse
 Description: deduplicating backup program
  Attic is a deduplicating backup program written in Python. The main
diff -Nru attic-0.10/debian/rules attic-0.10/debian/rules
--- attic-0.10/debian/rules	2013-11-25 09:15:01.0 -0500
+++ attic-0.10/debian/rules	2014-06-12 01:41:52.0 -0400
@@ -14,6 +14,7 @@
 	$(checkdir)
 	rm -f debian/substvars debian/files build-arch
 	rm -rf debian/attic debian/tmp attic/__pycache__ build __pycache__
+	rm -rf debian/attic.*
 
 build: build-arch build-indep
 build-indep:
@@ -26,6 +27,7 @@
 binary: binary-indep binary-arch
 binary-indep: checkroot
 binary-arch: checkroot install
+	dh_python3 -a
 	$(INSTALL_DIR) debian/$(package)/DEBIAN \
 		debian/$(package)/usr/share/doc/$(package)
 	$(INSTALL_FILE) debian/copyright debian/$(package)/usr/share/doc/$(package)
@@ -37,6 +39,7 @@
 	cd debian/$(package) && find * -type f ! -regex '^DEBIAN/.*' -print0 | xargs -r0 md5sum > DEBIAN/md5sums
 	dpkg-shlibdeps debian/$(package)/usr/lib/python3/dist-packages/$(package)/*.so
 	dpkg-gencontrol -Pdebian/$(package)
+	dpkg-gencontrol -Pdebian/$(package) -Tdebian/attic.substvars
 	dpkg --build debian/$(package) ..
 
 install: build

Bug#749903: wheezy-pu bug link

[Kees Cook]

Upload approved in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750699

-- 
Kees Cook@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#751355: $projectnumber expands . to contain spurious \+

[Helmut Grohne]

Control: reassign -1 src:ppl

On Thu, Jun 12, 2014 at 03:22:14AM +0100, Michael Tautschnig wrote:
> ~/ppl-1.1/doc# grep '^(version' 
> user-configured-c-interface.latex-dir/refman.tex
> (version 1.\+1)
> 
> 
> Unsurprisingly this doesn't compile:

This only fails to compile if your TeX sources fail to define \+. But
Doxygen introduced this define in its generated header:

\newcommand{\+}{\discretionary{\mbox{\scriptsize$\hookleftarrow$}}{}{}}

It appears not to be used, which most likely is due to ppl setting the
LATEX_HEADER Doxygen configuration option. This configuration option is
clearly declared as an unstable API, so unfortunately (by using this
option) this will have to be fixed in ppl.

Helmut


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

Bug#751362: springlobby: Please update to wxwidgets3.0

[Olly Betts]

Package: springlobby
Version: 0.194-1
Severity: serious
Justification: Blocks an on-going transition
Tags: sid jessie
User: freewx-ma...@lists.alioth.debian.org
Usertags: wx3.0

Dear maintainer,

We're aiming to migrate the archive to using wxwidgets3.0 instead of
wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released.

I had springlobby down on the list of packages that were already using
wxwidgets3.0, but I just spotted that in the latest upload you've switched
springlobby from back to wxwidgets2.8.  That's working against the
on-going wxwidgets3.0 transition:

https://release.debian.org/transitions/html/wxwidgets3.0.html

What were the problems that using wxwidgets3.0 was causing?  I don't see
anything about this in the BTS, and the changelog entry doesn't mention
anything specific.

At this point in the transition (and in the jessie release cycle), I'd
definitely recommend that packages stick with wxwidgets3.0 and we work
on resolving any issues.  That way there's a good chance to actually
resolve them before the jessie freeze.

Cheers,
Olly
diff -Nru freedink-dfarc-3.10/debian/changelog freedink-dfarc-3.10/debian/changelog
--- freedink-dfarc-3.10/debian/changelog	2012-09-28 01:55:08.0 +1200
+++ freedink-dfarc-3.10/debian/changelog	2014-06-01 01:05:13.0 +1200
@@ -1,3 +1,10 @@
+freedink-dfarc (3.10-1.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Update to use wxwidgets3.0.  New patch: wx3.0-compat.patch
+
+ -- Olly Betts   Sun, 01 Jun 2014 01:05:05 +1200
+
 freedink-dfarc (3.10-1.1) unstable; urgency=low
 
   * Non-maintainer upload
diff -Nru freedink-dfarc-3.10/debian/control freedink-dfarc-3.10/debian/control
--- freedink-dfarc-3.10/debian/control	2012-04-28 01:17:26.0 +1200
+++ freedink-dfarc-3.10/debian/control	2013-11-22 16:38:55.0 +1300
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Debian Games Team 
 Uploaders: Sylvain Beucler 
-Build-Depends: debhelper (>= 7.0.50~), autotools-dev, libbz2-dev, libwxgtk2.8-dev, intltool (>= 0.31)
+Build-Depends: debhelper (>= 7.0.50~), autotools-dev, libbz2-dev, libwxgtk3.0-dev, intltool (>= 0.31)
 Standards-Version: 3.9.3
 Homepage: http://www.gnu.org/software/freedink/
 Vcs-Git: git://git.debian.org/git/pkg-games/freedink-dfarc.git
diff -Nru freedink-dfarc-3.10/debian/.gitignore freedink-dfarc-3.10/debian/.gitignore
--- freedink-dfarc-3.10/debian/.gitignore	2008-08-26 08:13:37.0 +1200
+++ freedink-dfarc-3.10/debian/.gitignore	1970-01-01 12:00:00.0 +1200
@@ -1,9 +0,0 @@
-# rules:
-build-stamp
-build
-dfarc2
-# debhelper:
-files
-dfarc2.postinst.debhelper
-dfarc2.postrm.debhelper
-dfarc2.substvars
diff -Nru freedink-dfarc-3.10/debian/patches/series freedink-dfarc-3.10/debian/patches/series
--- freedink-dfarc-3.10/debian/patches/series	1970-01-01 12:00:00.0 +1200
+++ freedink-dfarc-3.10/debian/patches/series	2013-11-22 16:57:14.0 +1300
@@ -0,0 +1 @@
+wx3.0-compat.patch
diff -Nru freedink-dfarc-3.10/debian/patches/wx3.0-compat.patch freedink-dfarc-3.10/debian/patches/wx3.0-compat.patch
--- freedink-dfarc-3.10/debian/patches/wx3.0-compat.patch	1970-01-01 12:00:00.0 +1200
+++ freedink-dfarc-3.10/debian/patches/wx3.0-compat.patch	2014-06-01 01:22:43.0 +1200
@@ -0,0 +1,285 @@
+Description: fix to build with wxwidgets 3.0
+ wxLogError, etc are macros in wx 3.0.
+Author: Olly Betts 
+Forwarded: no
+Last-Update: 2013-11-22
+
+--- a/src/InstallVerifyFrame.cpp
 b/src/InstallVerifyFrame.cpp
+@@ -166,7 +166,7 @@
+ }
+   else
+ {
+-  ::wxLogError(_("An error occured while extracting the .dmod file."));
++  wxLogError(_("An error occured while extracting the .dmod file."));
+ }
+   ::wxRemoveFile(mTarFilePath);
+   // TODO: return error code instead of wxID_OK if something goes wrong
+--- a/src/DFArcFrame.cpp
 b/src/DFArcFrame.cpp
+@@ -343,7 +343,7 @@
+ {
+   wxString description = _("D-Mod files (*.dmod)");
+   wxFileDialog FileDlg(0, _("Select a .dmod file"), _T(""), _T(""), description + _T("|*.dmod"),
+-wxOPEN | wxFILE_MUST_EXIST);
++wxFD_OPEN | wxFD_FILE_MUST_EXIST);
+  
+   if (FileDlg.ShowModal() == wxID_OK)
+ {
+@@ -912,7 +912,7 @@
+ {
+ 		  if (::wxRmdir(mConfig->mSelectedDmod) == false)
+ {
+-		  ::wxLogError(_("Unable to remove D-Mod directory. All other files were removed."));
++		  wxLogError(_("Unable to remove D-Mod directory. All other files were removed."));
+ 		  lSuccess = false;
+ }
+ }
+--- a/src/RecursiveDelete.cpp
 b/src/RecursiveDelete.cpp
+@@ -52,7 +52,7 @@
+   {
+ if (::wxRemoveFile(aFilename) == false)
+ {
+-	  ::wxLogError(_("Could not remove %s"), aFilename.c_str());
++	  wxLogError(_("Could not remove %s"), aFilename.c_str());
+ 	  mError = true;
+ }
+ }
+@@ -70,7 +70,7 @@
+ {
+   if ( ::wxRmdir( aDirname ) == false )
+ 	{
+-	  ::wxLogError(_("Could not remove

Bug#750699: micro release from upstream!

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2014-06-11 at 16:40 -0700, Kees Cook wrote:
> Yay! I was able to convince upstream to do a micro release, so now the
> delta is tiny. I've attached the new debdiff, which shows just the cert
> chain and algo updates, with user agent reporting for their end. Much much
> better.

Much nicer indeed; thanks. :)

Please go ahead.

Regards,

Adam


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

Bug#742829: Bug #742829

[Daniel Richard G.]

On Sat, 2014 Jun  7 16:41+0200, intrigeri wrote:
> Hi,
>
> [Cc'ing Jamie, who authored this profile initially, according to the
> DEP-3 headers.]
>
> @Jamie: that's about Debian bug #742829, on how to handle differences
> in packaging chromium in Debian and Ubuntu, in the corresponding
> AppArmor profile.

Hi Jamie!

> In Trusty, Ubuntu is still shipping this profile as part of their own
> delta on top of upstream, and I guess everybody would be happy if a
> clean profile was merged upstream, in a way that distros can easily
> adapt paths to the way they're packaging chromium, without having to
> patch the main profile file. If this profile goes upstream, then
> Ubuntu can simply replace their own profile with the generic one, and
> add a tiny tunables file on top. I'm sure they'll be delighted to cut
> down their maintenance costs this way.
>
> Really, upstream is nice, happy to take patches, and the needed work
> is quite simple :)

It's not quite clear what the upstream for the Chromium profile is,
however. It doesn't exist in the Launchpad apparmor nor
apparmor-profiles repositories; the original source, it appears, is
debian/patches/add-chromium-browser.patch in the Ubuntu apparmor source
package (a patch against /dev/null containing the entirety of the file).
We know that Jamie authored the thing, and he's a Canonical guy, so why
doesn't this profile live with the others?

(The package even has another patch, debian/patches/update-chromium-
browser.patch, that *modifies* the file created by the aforementioned
patch. It's like they're studiously trying to avoid taking ownership of
the thing...)

> Personally, I've no strong interest in confining chromium, so I won't
> take the lead on it, but I'm happy to test and review patches before
> you submit it upstream, if it may help.

Web browsers are one of the biggest, if not *the* biggest entry vector
on most systems---confining them is a must. My concern is that AppArmor
in itself isn't enough, due to the lack of proper GUI isolation. If
someone hacks your browser, even if they can't read/write/execute their
way into anything, they can still keylog, screenscrape, and remote-
control your desktop. Not even going into the one-kernel-bug-and-all-
this-security-goes-poof thing...

> I'm glad you've been working on this. Thanks!

This is relevant to my interests ^_^

> However, I'm not overly enthusiastic at the idea of adding this kind
> of band-aid on top of a Ubuntu-specific patch we've pulled into our
> packaging, and that is not fit for Debian in its current state,
> especially when there's an easy and clean way to improve things for
> everybody.

Well, I first tried something along the lines of

#@{CHROMIUM}=chromium-browser
@{CHROMIUM}=chromium

/usr/lib/@{CHROMIUM}/@{CHROMIUM} ixr,
/usr/lib/@{CHROMIUM}/xdg-settings ixr,

but that was messy, and I don't think would have made a good case for
upstream inclusion. AppArmor aliases seem to be a better avenue for this
need. How else might one do it?


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

Bug#751361: apache2: SNI not working correctly when certificate is defined in global scope

[Martin Schwenke]

Package: apache2
Version: 2.4.9-1
Severity: normal

Dear Maintainer,

SSL certificates in virtual hosts are being ignored.  The certificate
configured in global scope is used for all virtual hosts.

Please see this Apache bug:

  https://issues.apache.org/bugzilla/show_bug.cgi?id=56353

It has a patch. :-)

-- Package-specific info:

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

Kernel: Linux 3.12-1-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/bash

Versions of packages apache2 depends on:
ii  apache2-bin   2.4.9-1
ii  apache2-data  2.4.9-1
ii  lsb-base  4.1+Debian12
ii  mime-support  3.56
ii  perl  5.18.2-4
ii  procps1:3.3.9-5

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.34

Versions of packages apache2 suggests:
ii  apache2-doc  2.4.9-1
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  apache2-utils2.4.9-1
ii  elinks [www-browser] 0.12~pre6-4
ii  links [www-browser]  2.8-2
ii  lynx-cur [www-browser]   2.8.8pre5-1
ii  w3m [www-browser]0.5.3-15

Versions of packages apache2-bin depends on:
ii  libapr1  1.5.1-2
ii  libaprutil1  1.5.3-2
ii  libaprutil1-dbd-sqlite3  1.5.3-2
ii  libaprutil1-ldap 1.5.3-2
ii  libc62.19-1
ii  libldap-2.4-22.4.39-1
ii  liblua5.1-0  5.1.5-5
ii  libpcre3 1:8.31-5
ii  libssl1.0.0  1.0.1g-4
ii  libxml2  2.9.1+dfsg1-3
ii  perl 5.18.2-4
ii  zlib1g   1:1.2.8.dfsg-1

Versions of packages apache2-bin suggests:
ii  apache2-doc  2.4.9-1
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  elinks [www-browser] 0.12~pre6-4
ii  links [www-browser]  2.8-2
ii  lynx-cur [www-browser]   2.8.8pre5-1
ii  w3m [www-browser]0.5.3-15

Versions of packages apache2 is related to:
ii  apache2  2.4.9-1
ii  apache2-bin  2.4.9-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#751360: libswe-dev: /usr/lib/i386-linux-gnu/pkgconfig/libswe-1.80.00.pc wrong value

[Paul Elliott]

Package: libswe-dev
Version: 1.80.00.0001-1
Severity: normal

Dear Maintainer,


the file /usr/lib/i386-linux-gnu/pkgconfig/libswe-1.80.00.pc
says includedir=${prefix}/include/libswe-1.80.00 where it
should say includedir=${prefix}/include


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

Kernel: Linux 3.14-1-686-pae (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 libswe-dev depends on:
ii  libc62.19-1
ii  libswe0  1.80.00.0001-1

libswe-dev recommends no packages.

libswe-dev suggests no packages.

-- no debconf information

-- 
Paul Elliott   1(512)837-1096
pelli...@blackpatchpanel.com   PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com/pme/   Austin TX 78758-3117


signature.asc
Description: Digital signature

Bug#747252: lightdm: AppArmor parser error in /etc/apparmor.d/abstractions/lightdm_chromium-browser

[Daniel Richard G.]

Yves, you removed /etc/apparmor.d/lightdm-guest-session from the
package (via a debhelper exclusion directive), but you didn't exclude
/etc/apparmor.d/abstractions/lightdm_chromium-browser, which is the
profile that was generating the error in the first place  >_<

https://packages.debian.org/sid/amd64/lightdm/filelist

On Sat, 2014 Jun  7 15:12+0200, intrigeri wrote:
>
> Good to know. That may be an error on my side, then. May you please
> share the exact patch you're applying to the relevant profile(s)?

Looks like the errant profiles are going away, but for what it's worth,
this is what I did (basically, comment out all "ptrace" and "signal"
directives):

--- /etc/apparmor.d/abstractions/lightdm_chromium-browser.orig  2014-06-12 
00:32:32.0 -0400
+++ /etc/apparmor.d/abstractions/lightdm_chromium-browser   2014-06-04 
21:03:07.663729440 -0400
@@ -18,10 +18,10 @@
   /opt/google/chrome-unstable/google-chrome-unstable Cx -> chromium,
 
   # Allow ptracing processes in the chromium child profile
-  ptrace peer=/usr/lib/lightdm/lightdm-guest-session//chromium,
+#  ptrace peer=/usr/lib/lightdm/lightdm-guest-session//chromium,
 
   # Allow receiving and sending signals to processes in the chromium child 
profile
-  signal (receive, send) peer=/usr/lib/lightdm/lightdm-guest-session//chromium,
+#  signal (receive, send) 
peer=/usr/lib/lightdm/lightdm-guest-session//chromium,
 
   profile chromium {
 # Allow all the same accesses as other applications in the guest session
@@ -39,14 +39,14 @@
 @{PROC}/sys/kernel/yama/ptrace_scope r,
 
 # Allow ptrace reads of processes in the lightdm-guest-session
-ptrace (read) peer=/usr/lib/lightdm/lightdm-guest-session,
+#ptrace (read) peer=/usr/lib/lightdm/lightdm-guest-session,
 # Allow other guest session processes to read and trace us
-ptrace (readby, tracedby) peer=/usr/lib/lightdm/lightdm-guest-session,
-ptrace (readby, tracedby) peer=@{profile_name},
+#ptrace (readby, tracedby) peer=/usr/lib/lightdm/lightdm-guest-session,
+#ptrace (readby, tracedby) peer=@{profile_name},
 
 # Allow us to receive and send signals from processes in the
 # lightdm-guest-session
-signal (receive, send) set=("exists") 
peer=/usr/lib/lightdm/lightdm-guest-session,
+#signal (receive, send) set=("exists") 
peer=/usr/lib/lightdm/lightdm-guest-session,
 
 @{PROC}/[0-9]*/ r, # sandbox wants these
 @{PROC}/[0-9]*/fd/ r,  # sandbox wants these


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

Bug#751359: /etc/chromium.d/README: line 1: Any: command not found

[積丹尼 Dan Jacobson]

Package: chromium
Version: 36.0.1985.49-1
Severity: grave

/etc/chromium.d/README: line 1: Any: command not found
/usr/bin/chromium: line 32: jessie/sid: No such file or directory

! ! ! !


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

Bug#751358: iceweasel: Immediate segfault visiting any page that uses WebGL

[Christopher Wellons]

Package: iceweasel
Version: 30.0-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

After updating to this latest release, visiting any page that creates
a WebGL context causes an immediate segmentation fault in Iceweasel.
Here's an example of such a website:

* http://nullprogram.com/fun-liquid/webgl/

Attached is the gdb backtrace. The segfault still occurs with all
plugins and addons disabled in a fresh profile.


- -- Package-specific info:

- -- 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/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 iceweasel 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-1
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-6
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  libsqlite3-0  3.8.4.3-3
ii  libstartup-notification0  0.12-3
ii  libstdc++64.9.0-6
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  procps1:3.3.9-5
ii  zlib1g1:1.2.8.dfsg-1

iceweasel recommends no packages.

Versions of packages iceweasel suggests:
ii  fonts-mathjax  2.3-1
ii  fonts-oflb-asana-math  000.907-6
ii  fonts-stix [otf-stix]  1.1.1-1
ii  libcanberra0   0.30-2
ii  libgnomeui-0   2.24.5-3
ii  libgssapi-krb5-2   1.12.1+dfsg-2
pn  mozplugger 

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJTmSYGAAoJEGEzgsVIsrhBlRgH/2L72ETZseY70nr51zd1H0Wa
RHcDpMXiE3M2KaEIm2greBSRA7Vk43k4qyW/alXXUFpBZF+6tmOWWlFAY8PN97YP
JAGGINSz2vevNYLAxIla0ySVTLOA+k2m7FsgcKD3XBjd/J0uZiuiSe0UYBO9+aVO
cO4wIle4g4OeaaN5e+qBALPQlqWtXf9sLgcBzxiwpF7L56tNwre1/yEanHfT9Jk2
8Zn9shSvHLDB2eWHQLbillbbBePrGh0twesFiyW+QaLSjCdEAHU/7yP5UgUQq8UV
trN/DDO6MJcGf23JdhZchhqEyiKPdD5wpS+IpSMhbus4ZbM3iP71X+5PM4T0VVo=
=pk06
-END PGP SIGNATURE-
Starting program: /usr/bin/iceweasel -P http://nullprogram.com/fun-liquid/webgl/
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe7190700 (LWP 6816)]
[Thread 0x7fffe7190700 (LWP 6816) exited]
[New Thread 0x7fffe7190700 (LWP 6819)]
[New Thread 0x7fffe07ff700 (LWP 6820)]
[New Thread 0x7fffdf7eb700 (LWP 6821)]
[New Thread 0x7fffdefea700 (LWP 6822)]
[New Thread 0x7fffde3ff700 (LWP 6823)]
[New Thread 0x7fffd5ced700 (LWP 6824)]
[New Thread 0x7fffd54ec700 (LWP 6825)]
[New Thread 0x7fffd4aff700 (LWP 6826)]
[New Thread 0x7fffd42fe700 (LWP 6827)]
[New Thread 0x7fffe09ad700 (LWP 6828)]
[New Thread 0x7fffdfffe700 (LWP 6829)]
[New Thread 0x7fffd34ff700 (LWP 6830)]
[New Thread 0x7fffd24ff700 (LWP 6834)]
[Thread 0x7fffe07ff700 (LWP 6820) exited]
[Thread 0x7fffd4aff700 (LWP 6826) exited]
[Thread 0x7fffd34ff700 (LWP 6830) exited]
[Thread 0x7fffd42fe700 (LWP 6827) exited]
[Thread 0x7fffd54ec700 (LWP 6825) exited]
[Thread 0x7fffd24ff700 (LWP 6834) exited]
[Thread 0x7fffe09ad700 (LWP 6828) exited]
[Thread 0x7fffdfffe700 (LWP 6829) exited]
[Thread 0x7fffe7190700 (LWP 6819) exited]
[Thread 0x7fffde3ff700 (LWP 6823) exited]
[Thread 0x7fffd5ced700 (LWP 6824) exited]
[Thread 0x7fffdefea700 (LWP 6822) exited]
[Thread 0x7fffdf7eb700 (LWP 6821) exited]
process 6807 is executing new program: /usr/lib/iceweasel/iceweasel
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe7190700 (LWP 6842)]
[Thread 0x7fffe7190700 (LWP 6842) exited]
[New Thread 0x7fffe7190700 (LWP 6844)]
[New Thread 0x7fffe07ff700 (LWP 6845)]
[New Thread 0x7fffdf7eb700 (LWP 6846)]
[New Thread 0x7fffdefea700 (LWP 6847)]
[New Thread 0x7fffde3ff700 (LWP 6848)]
[New Thread 0x76d76700 (LWP 6849)]
[New Thread 0x7fffdd4ff700 (LWP 6850)]
[New Thread 0x7fffdbf75700 (LWP 6852)]
[New Thread 0x7fffdb774700 (LWP 6853)]
[New Thread 0x7fffdadff700 (LWP 6854)]
[New Thread 0x7fffd2558700 (LWP 6855)]
[New Thread 0x7fffd1bff700 (LWP 6856)]
[New Thread 0x7fffd13fe700 (LWP 6857)]
[New Thread 0x7fffd0cff700 (LWP 6858)]
[New Thread 0x7fffd0

Bug#750913: xmlcopyeditor: Gdk-CRITICAL **: IA__gdk_window_process_updates: assertion 'GDK_IS_WINDOW (window)' failed

[Olly Betts]

On Sun, Jun 08, 2014 at 11:55:35PM +1200, Olly Betts wrote:
> On Sun, Jun 08, 2014 at 01:15:28PM +0200, Vincent Lefevre wrote:
> > When I start xmlcopyeditor, I get the following error:
> > 
> > (xmlcopyeditor:20706): Gdk-CRITICAL **: IA__gdk_window_process_updates: 
> > assertion 'GDK_IS_WINDOW (window)' failed
> 
> You're using my recent NMU to update xmlcopyeditor to use wxwidgets3.0, so I
> took a look.  However, I don't see this (or any other) message.

Trying on a different machine, I do see this, suggesting it's timing
dependent.

Thanks for the backtrace.  I suspect it's a wx issue, and I'll see if I
can track this down.

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#750911: xmlcopyeditor: shouldn't output debug messages

[Olly Betts]

On Sun, Jun 08, 2014 at 01:08:01PM +0200, Vincent Lefevre wrote:
> When I start xmlcopyeditor, it outputs:
> 
> 12:23:05: Debug: Failed to connect to session manager: SESSION_MANAGER 
> environment variable not defined
> 
> This is just a debug message, not an error (I don't use a session manager,
> so that it is normal that SESSION_MANAGER is not defined).

I had a look at this to see if it was due to changes in my NMU, but I
can't get this message from 1.2.0.12-1.1.  I do run a session manager,
but I unset SESSION_MANAGER in the shell before I started
xmlcopyeditor, and I don't get this message.  I tried unsetting every
environment variable with SESSION in its name, and that didn't help
either.

Can you check if this affect xmlcopyeditor 1.2.0.12-1 too?

And do you see this with any other apps you use which have already
migrated to wxwidgets3.0?

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#751294: chromium: Does not display any web page or settings ("Aw, Snap")

[Theppitak Karoonboonyanan]

Package: chromium
Followup-For: Bug #751294
Severity: important

This doesn't occur to me. It still works fine as usual.
So, lowering the severity.

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

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

Versions of packages chromium depends on:
ii  chromium-inspector   35.0.1916.153-1
ii  gconf-service3.2.6-2
ii  libasound2   1.0.27.2-4
ii  libc62.19-1
ii  libcairo21.12.16-2
ii  libcap2  1:2.22-1.2
ii  libcups2 1.7.3-3
ii  libdbus-1-3  1.8.4-1
ii  libexpat12.1.0-6
ii  libfontconfig1   2.11.0-5
ii  libfreetype6 2.5.2-1
ii  libgcc1  1:4.9.0-6
ii  libgconf-2-4 3.2.6-2
ii  libgcrypt11  1.5.3-4
ii  libgdk-pixbuf2.0-0   2.30.7-1
ii  libglib2.0-0 2.40.0-3
ii  libgnome-keyring03.8.0-2
ii  libgtk2.0-0  2.24.23-1
ii  libharfbuzz0b0.9.28-2
ii  libjpeg8 8d-2
ii  libnspr4 2:4.10.6-1
ii  libnss3  2:3.16.1-1
ii  libpango-1.0-0   1.36.3-1
ii  libpangocairo-1.0-0  1.36.3-1
ii  libspeechd2  0.8-6
ii  libspeex11.2~rc1.1-1
ii  libstdc++6   4.9.0-6
ii  libudev1 204-10
ii  libx11-6 2:1.6.2-2
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1
ii  libxdamage1  1:1.1.4-1
ii  libxext6 2:1.3.2-1
ii  libxfixes3   1:5.0.1-1
ii  libxi6   2:1.7.2-1
ii  libxml2  2.9.1+dfsg1-3
ii  libxrandr2   2:1.4.2-1
ii  libxrender1  1:0.9.8-1
ii  libxslt1.1   1.1.28-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1
ii  xdg-utils1.1.0~rc1+git20111210-7.1

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-l10n  
pn  mozplugger 

-- 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#750605: screen goes berserk, had to downgrade

[積丹尼 Dan Jacobson]

found 750605 2:2.99.912-1~exp1
thanks
> "ma" == maximilian attems  writes:

ma> Newer snapshat has sna fixes, please test 2:2.99.911+git20140607-1~exp1
ma> (without uxa fallback)

What package is that? Where can I get it? All I know is the installed

# apt-cache policy $@
xserver-xorg-video-intel:
  Installed: 2:2.99.912-1~exp1
  Candidate: 2:2.99.912-1~exp1
  Version table:
 *** 2:2.99.912-1~exp1 0
990 http://ftp.br.debian.org/debian/ experimental/main i386 Packages
100 /var/lib/dpkg/status
 2:2.21.15-2+b1 0
500 http://ftp.br.debian.org/debian/ unstable/main i386 Packages


one is busted.


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

Bug#749795: holes in secure apt

[Joey Hess]

Christoph Anton Mitterer wrote:
> reopen 749795
> I'm reopening this for now, even if the issue is solved from a technical
> point of view (see below why).

AAICS, #749795 talked about bringing this to the security team's
attention, but they never seem to have been CCed.

So the security team may not be aware that a security hole in apt was
recently fixed, that caused apt-get source to not give any indication
when the Release file was lacking a signature.

Whether it's closed in unstable or not, this bug is open still in
stable, and needs to get a CVE assigned, and a DSA issued.

-- 
see shy jo


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

Bug#700760: Bug#751285: systemtap-sdt-dev: should be "Arch: all" so gcc and libc can B-D on it

[Samuel Bronson]

Matthias Klose  writes:
[...]
> If you really are too lazy to have architecture specific build
> dependencies, then consider shipping an empty package for the
> unsupported architectures.

Um, that was actually meant as a convenience for *you* (and anyone else
who works on a package that wants to provide SDT probes) more than for
me: since  really is meant to work *EVERYWHERE* [1], the
proper way to handle architectures where systemtap's 
currently fails because of oddities in their assembly syntax is to
conditionalize the definitions of the macros that use the problematic
syntax, adding variants that *do* work with their assembly syntax.

[1]: https://sourceware.org/systemtap/wiki/UserSpaceProbeImplementation

If you're incredulous at the idea that this one header is supposed to
support probes on EVERY architecture, consider that a probe consists of

  * probe PC address (address size)

  * link-time sh_addr of .stapsdt.base section (address size)

  * link-time address of the semaphore variable (address size). This is
zero if the probe does not have an associated semaphore; in this
case no .stapsdt.base adjustment should be done

  * provider name (null-terminated string)

  * probe name (null-terminated string)

  * argument format (null-terminated string)

There's already one conditional for __powerpc__ & __powerpc64__ to deal
with the fact that register numbers there look exactly like constants,
and another for ISAs where nop takes an argument (namely, __ia64__,
__s390__, & __s390x__); it doesn't seem likely that it will be
particularly difficult to deal with any other oddities.

If worst came to worst, we could simply gut the whole thing on
architectures with really strange assembly syntax, so that it doesn't
emit so much as a NOP.


However, all of this depends on knowing which architectures
  don't work, so for the Nth time:
  which architectures is 
  buggy on?

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!

Bug#751357: xul-ext-adblock-plus: obsolete-conffile found by adequate

[shirish शिरीष]

Package: xul-ext-adblock-plus
Version: 2.6.3-1
Severity: important
Usertags: obsolete-conffile adequate

Dear Maintainer,
Adequate reported an obsolete-conffile for xul-ext-adblock-plus while
upgrading to the newer xul-ext-adblock-plus version.

$ adequate xul-ext-adblock-plus
xul-ext-adblock-plus: obsolete-conffile /etc/xul-ext/adblock-plus.js

>From https://wiki.debian.org/DpkgConffileHandling it seems that
xul-ext-adblock-plus has stopped shipping a conffile and that's why
adequate is complaining. Please fix it one way or the other.

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

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

Versions of packages xul-ext-adblock-plus depends on:
ii  iceweasel  29.0.1-2

xul-ext-adblock-plus recommends no packages.

xul-ext-adblock-plus suggests no packages.

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8


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

Bug#751260: devscripts: wrap-and-sort does not handle comments in Build-Depends properly

[James McCoy]

Control: reassign -1 python-debian 0.1.21+nmu2
Control: forcemerge 604093 -1

On Wed, Jun 11, 2014 at 04:03:06PM +0200, Rohan Garg wrote:
> Running wrap-and-sort on a control file of a package that had the first
> build dep commented out completely deletes the build-deps of the package.
> 
> Testcase :
> 
> Snippet from a control file -
> 
> 
> Build-Depends:
> # kde-sc-dev-latest (>= 4:4.10.2),
>  cmake, debhelper (>= 7.3.16), pkg-kde-tools (>= 0.12),
> 
> 
> Running wrap-and-sort on a control file with such a snippet will delete
> everything from the Build Depends

This is due to #604093 (in python-debian).  Reassigning and merging with
the other reports.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 


signature.asc
Description: Digital signature

Bug#751356: twidge: Segmentation Fault while querying for twits

[Josue Ortega]

Package: twidge
Version: 1.1.0
Severity: important
Tags: upstream

Dear Maintainer,

While running "twidge lsrecent" or "twidge lsreplies" returns a Segmentation
Fault.

I am sorry if I didn't bring more technical information but I have no experience
with Haskell.

Hope this report will be helpful.

Cheers 

-- 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=es_GT.UTF-8, LC_CTYPE=es_GT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages twidge depends on:
ii  curl 7.37.0-1
ii  libc62.19-1
ii  libcurl3-gnutls  7.37.0-1
ii  libffi6  3.1-2
ii  libgmp10 2:6.0.0+dfsg-4

twidge recommends no packages.

twidge suggests no packages.

-- 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#750026: transition: qtbase-opensource-src

[Lisandro Damián Nicanor Pérez Meyer]

On Wednesday 11 June 2014 22:01:05 Lisandro Damián Nicanor Pérez Meyer wrote:
> Doko has raised the severities to serius of the bugs in the qt5 stack
> that causes FTBFSs due to symbols changes. Should I start rebuilding or do
> you want to force the transition by ignoring the relevant bugs?

Just ignore me please. The bugs are also present in testing so they shouldn't 
be a problem.


-- 
8: Si un archivo ha pasado a la "Papelera de Reciclaje"
* Ud tiene una carpeta llamada "Papelera de Reciclaje"
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

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


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

Bug#751224: FTBFS with newer libminiupnpc10

[Vincent Cheng]

Control: forwarded -1 http://trac.wildfiregames.com/ticket/2552
Control: tag -1 + pending

On Wed, Jun 11, 2014 at 2:18 AM, Thomas Goirand  wrote:
> Package: 0ad
> Version: 0.0.16-2
> Severity: important
> Tags: patch
>
> Dear package maintainer,
>
> We would like to have a transition to the last version of libminiupnpc10
> which I uploaded to experimental. Unfortunately, 0ad FTBFS when building
> with that new version.
>
> I've attached to this bug report a patch for 0ad, which you can simply
> drop in debian/patches. Please upload a new version of 0ad including this
> patch ASAP, so we can start the miniupnpc transition.
>
> Note that I have tested the patch, and 0ad built fine with it. However,
> I didn't check/test for the UPnP functionality.

I'm going to use upstream's patch instead, but thanks anyways!

Regards,
Vincent


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

Bug#751355: $projectnumber expands . to contain spurious \+

[Michael Tautschnig]

Package: doxygen-latex
Version: 1.8.7-2

The following is a regression from 1.8.6-2, which built ppl (where this problem
occurs) just fine in the very same setup.

So we have:

~/ppl-1.1/doc# grep PROJECT_NUMBER Doxyfile.user-configured-c-interface-latex
PROJECT_NUMBER = 1.1

~/ppl-1.1/doc# grep '^(version' *.tex
devref-language-interface.tex:(version $projectnumber)
devref.tex:(version $projectnumber)
user-configured-c-interface.tex:(version $projectnumber)
user-configured-prolog-interface.tex:(version $projectnumber)
user-language-interface.tex:(version $projectnumber)
user.tex:(version $projectnumber)


Run doxygen:

~/ppl-1.1/doc# 
TEXINPUTS=/srv/jenkins-slave/workspace/sid-goto-cc-ppl/ppl-1.1/doc: doxygen 
Doxyfile.user-configured-c-interface-latex
Warning: Tag `XML_SCHEMA' at line 231 of file 
`Doxyfile.user-configured-c-interface-latex' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
Warning: Tag `XML_DTD' at line 232 of file 
`Doxyfile.user-configured-c-interface-latex' has become obsolete.
 To avoid this warning please remove this line from your configuration 
file or upgrade it using "doxygen -u"
Warning: doxygen no longer ships with the FreeSans font.
You may want to clear or change DOT_FONTNAME.
Otherwise you run the risk that the wrong font is being used for dot generated 
graphs.
GPL:-1: warning: multiple use of section label 'GPL', (first occurrence: 
/srv/jenkins-slave/workspace/sid-goto-cc-ppl/ppl-1.1/doc/gpl.dox, line 6)
GFDL:-1: warning: multiple use of section label 'GFDL', (first occurrence: 
/srv/jenkins-slave/workspace/sid-goto-cc-ppl/ppl-1.1/doc/fdl.dox, line 6)

~/ppl-1.1/doc# grep '^(version' user-configured-c-interface.latex-dir/refman.tex
(version 1.\+1)


Unsurprisingly this doesn't compile:

pdflatex refman
[...]
! Undefined control sequence.
\@title ...Program Analyzers''. } \\ (version 1.\+
  1)


Best,
Michael



pgpAAhvHzryDh.pgp
Description: PGP signature

Bug#751354: Override/fix Lintian tags

[djcj]

Package: pidgin
Version: 2.10.9-1

You should override this source package Lintian warning:
pidgin source: no-debian-copyright
The copyright file is generated at build time.

This warning should be fixed:
pidgin source: brace-expansion-in-debhelper-config-file 
debian/pidgin-dev.install
Don't use the braces in debian/pidgin-dev.install but instead use 
separate lines

to install .html, .gif and .png files.

And for the binary package libpurle0 you might consider an override for 
this:

libpurple0: embedded-library usr/lib/purple-2/libgg.so: libgadu
Unless it is possible and makes sense to link it dynamically against 
libgadu (which I doubt).



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

Bug#750772: Some more additional info: seems related to PHP 5.6

[Sebastian Lange]

Hi Roland,

doesn't work for me. I tried some 5.5 Snapshots and the 5.4.4-14+deb7u10 from 
wheezy. Which 5.5 Version fixed it for you?


#!bastla


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

Bug#577737: [pinentry-qt4] Re: gpg command won't use agent if the agent is configured to use pinentry-qt4

[Peter Eisentraut]

I can't reproduce this, and I can't explain it.

A couple of things to try:

Try running pinentry-qt4 independently of gpg.  Just start it and enter
GETPIN at the prompt, and see if a window appears.

Also check your login setup to make sure that the environment variables
GPG_TTY and/or GPG_AGENT_INFO are set correctly.  Although that wouldn't
explain why pinentry-gtk-2 works.  There could be other environment
variables or settings that affect Qt but not Gtk.  Testing the programs
separately, as described above, might clarify that.


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

Bug#715038: add mips64(el) mipsn32(el) support to eglibc

[Yunqiang Su]

On Thu, Jun 12, 2014 at 4:39 AM, Aurelien Jarno  wrote:
> Hi,
>
> On Tue, Jun 10, 2014 at 08:17:53PM +0800, Sphinx Jiang wrote:
>> Hi,
>>
>> In this patch, o32 libraries are moved from /lib to /libo32.
>
> I have applied this patch with some small changes fixing some issues and
> homogenizing all mips*.mk files, most importantly:
> - really install the o32 library in /libo32 for mipsn32el.mk
> - changed a end into endef
> - replace MIPS64 by MIPS in the o32 package description, as it doesn't
>   need a 64-bit CPU to run the o32 libc (contrary to the n32 and n64
>   ones).
>
> Don't hesitate to look at the SVN to check everything is ok.

Great, thank you so much.

>
> --
> Aurelien Jarno  GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net http://www.aurel32.net
>
> --
> To unsubscribe, send mail to 715038-unsubscr...@bugs.debian.org.



-- 
Yunqiang Su


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

Bug#750026: transition: qtbase-opensource-src

[Lisandro Damián Nicanor Pérez Meyer]

Doko has raised the severities to serius of the bugs in the qt5 stack
that causes FTBFSs due to symbols changes. Should I start rebuilding or do
you want to force the transition by ignoring the relevant bugs?

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
El jun 10, 2014 3:34 PM, "Lisandro Damián Nicanor Pérez" <
perezme...@gmail.com> escribió:

> gammaray and pyqt5 have built everywhere except sparc and hurd, so it
> should
> be ready. fcitx-qt5 seems ready.
>
> qtcreator is not a blocker.
>
> We can wait for packages to age or age them, but that's your call :)
>
> Thanks a lot! :-D
>
> --
>
> Lisandro Damián Nicanor Pérez Meyer
> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/
>

Bug#751353: flash-kernel: Add support for TI AM335x BeagleBone (black).

[Vagrant Cascadian]

Package: flash-kernel
Version: 3.20
Severity: wishlist
Tags: patch

The patch below adds support for the BeagleBone Black board.

It will require a patched u-boot, or using a uEnv.txt in order to load the boot
script on the first partition on the eMMC or microSD:

# Adjust values to taste:
device=mmc
mmcdev=0
mmcpart=2
script=/boot/boot.scr
uenvcmd=load ${device} ${mmcdev}:${mmcpart} ${loadaddr} ${script} && source 
${loadaddr}

I've tested this with the u-boot shipping on current BeagleBone Black boards,
though it may not work with previous u-boot versions that shipped with the
boards. I'll work on patching the u-boot in Debian to support it without
requiring uEnv.txt.


The Machine field will also likely apply to the BeagleBone White, which uses a
different .dtb and may require other changes for flash-kernel to support it.
Not sure what exactly to do about that.


commit 314ea22d1754c92f1249bd54bb01dc8a4e441dae
Author: Vagrant Cascadian 
Date:   Wed Jun 11 16:13:08 2014 -0700

Add support for TI AM335x BeagleBone (black).

diff --git a/bootscript/bootscr.beaglebone b/bootscript/bootscr.beaglebone
new file mode 100644
index 000..ab35a09
--- /dev/null
+++ b/bootscript/bootscr.beaglebone
@@ -0,0 +1,17 @@
+# boot script for BeagleBone
+
+setenv device mmc
+setenv partition ${mmcdev}:${mmcpart}
+setenv bootargs '@@LINUX_KERNEL_CMDLINE@@'
+
+image_locations='/boot/ /'
+kvers='@@KERNEL_VERSION@@'
+
+for pathprefix in ${image_locations}
+do
+  load ${device} ${partition} ${loadaddr} ${pathprefix}vmlinuz-${kvers} \
+  && load ${device} ${partition} ${fdtaddr} ${pathprefix}dtb-${kvers} \
+  && load ${device} ${partition} ${rdaddr} ${pathprefix}initrd.img-${kvers} \
+  && echo "Booting Debian ${kvers} from ${device} ${partition}..." \
+  && bootz ${loadaddr} ${rdaddr}:${filesize} ${fdtaddr}
+done
diff --git a/db/all.db b/db/all.db
index ec685c2..3298328 100644
--- a/db/all.db
+++ b/db/all.db
@@ -527,6 +527,13 @@ Mtd-Kernel: kernel
 Mtd-Initrd: ramdisk
 Bootloader-Sets-Incorrect-Root: yes
 
+Machine: TI AM335x BeagleBone
+Kernel-Flavors: armmp
+DTB-Id: am335x-boneblack.dtb
+Boot-Script-Path: /boot/boot.scr
+U-Boot-Script-Name: bootscr.beaglebone
+Required-Packages: u-boot-tools
+
 Machine: Toshiba AC100 / Dynabook AZ
 Method: android
 Android-Boot-Device: /dev/mmcblk0


signature.asc
Description: Digital signature

Bug#751352: RFS: syncterm/20140525-1

[Fernando Toledo]

Package: sponsorship-requests
Severity: wishlist

Package: sponsorship-requests
  Severity: whislist

  Dear mentors,

  I am looking for a sponsor for my package "syncterm"

 * Package name: syncterm
   Version : 20140525-1
   Upstream Author : Stephen Hurd 
 * URL : http://syncterm.bbsdev.net
 * License : GPL 2
   Section : comm

  It builds those binary packages:

syncterm   - BBS terminal program from Synchronet
 syncterm-dbg - BBS terminal program from Synchronet

  To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/syncterm

  Alternatively, one can download the package with dget using this command:

dget -x
http://mentors.debian.net/debian/pool/main/s/syncterm/syncterm_20140525-1.dsc


  Changes since the last upload:

  * new upstream release
  * debug packages depends
  * debug package should be extra priority (lintian)


  I want to get into debian because this terminal emulator is the best for
support ANSI-BBS console codes. You can see it, finding some screenshoots on
internet.
  It's part of Synchronet BBS, a free BBS system.

  Regards,
   Fernando Toledo




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

Kernel: Linux 3.14-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.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#751282: pbuilder overrides keyring

[Phillip Susi]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 06/11/2014 05:16 PM, Thorsten Glaser wrote:
| Phillip Susi dixit:
|
|> specified in the suite script.  This breaks the creation of a pbuilder
|> for ubuntu since the keyring is forced back to debian's.
|
| It doesn;t because you;re supposed to add --keyring to the command
| line calling cowbuilder --create by yourself.

This makes no sense.  First, if you are going to specify it anyway, then it 
doesn't need to be in pbuilderrc, and second, why should you specify it when 
debootstrap already defaults to the correct value?


-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTmPVOAAoJEI5FoCIzSKrwKZIH/2emI3J+N1BCUtdB3hA+5LCv
uSpPk8nTsVp9KQEBxfABbz/XybQcXhIkQuvmpnh7bxn8H5qs1R0qluqTAFQ6Cn3T
qOVaHkfaC0R5bGY0spI4X4FffJ5y4SnVAWD/avVzQJZrX7ibLr+mVVsXbZ5sxiHN
LE0GdEvK7qnL66nzzTY2B2TwvUuv9E3KAZi2nS5Hm2OqvoLPh1Dmis/5naC9JHy3
r2LWAbxZ85d/ol8159HqOm5UMf2xTNGx2y08/CfzRVeBmQdH8tc4PIkg5aJJFNJq
/nk9qXSAW2tuemaDTfX8Dm0AyH894kWQdfgQpehQ6CGqsZw5D8yHXXjJ8FJU+B4=
=EphF
-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#339838: nut-nutrition: Would like to record 'snacks' and change the number of meals

[Iain R. Learmonth]

tags 339838 + wontfix
thanks

The upstream author has indicated that he is no longer developing this
application, and it has previously been stated by the upstream author that
"this would be very a serious modification", I am tagging this as wontfix.

Iain.

-- 
urn:x-human:Iain R. Learmonth
http://iain.learmonth.me/ 
mailto:i...@fsfe.org   
xmpp:i...@jabber.fsfe.org  
tel:+447875886930 

GPG Fingerprint: 1F72 607C 5FF2 CCD5 3F01 600D 56FF 9EA4 E984 6C49
Please verify out-of-band before trusting with sensitive information.

This email was composed Thu 12 Jun 01:15:00 BST 2014.



pgpu8EsNIPOdt.pgp
Description: PGP signature

Bug#745628: [Pkg-bluetooth-maintainers] Bug#745628: bluez: please use dh-autoreconf to fix FTBFS on ppc64el

[Nobuhiro Iwamatsu]

Hi,

Thanks for your report.
We will have plan transition from bluez4 to bluez5.
I want to revice this problem on bluez5. Could you check bluez5 build
on  ppc64le, if you can?
Bluez5 already installed in experimental.

Best regards,
  Nobuhiro


2014-04-23 23:31 GMT+09:00 Fernando Seiti Furusato :
> Package: bluez
> Version: 4.101-4.1
> Severity: normal
> Tags: patch
> Control: usertags -1 ppc64el
>
> Dear Maintainer,
>
> While trying to enable this package on ppc64el, the build configuration files
> needed to be updated. That could be achieved by adding autoreconf to the 
> build.
>
>
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: ppc64el (ppc64le)
>
> Kernel: Linux 3.13-1-powerpc64le (SMP w/8 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> ___
> Pkg-bluetooth-maintainers mailing list
> pkg-bluetooth-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-bluetooth-maintainers



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


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

Bug#746078: [Pkg-bluetooth-maintainers] Bug#746078: Bug#746078: Please provide bluez 5 in unstable

[Nobuhiro Iwamatsu]

Hi, again.

# I added Jordi Mallach, Laurent Bigonville and Christopher Schramm
(blueman maintainer)  to CC.

I want to talk about bluez5 transition on this BTS. OK?

Although it is in the present situation,
 - bluez5 is already contained in expeirmental.
 - gnome-bluetooth by which bluez5 was supported is in experimental by
Laurent Bigonville. (Thanks!)
 - bluedevil by which bluez5 was supported is also in experimental.
 - blueman which bluez4 and bluez5 were both supported is in unstable.

We have an important package required since it already transition in
experimental.
We need to move them to unstable.

An order which I consider is as follows.
1. upload to bluez5 to unstable.
 NOTE: I think that we does not need binary transition, because
bluez5 ABI of library does not change
   from bluez4 to bluez5.
2. if accepted bluez5, upload gnome-bluetooth and bluedevil.
3. (or 2?) upload other package what depends bluez5.

Since I did not know the state of other packages yet, I wrote simply.
Would you give me an opinion?

Best regards,
  Nobuhiro

2014-06-12 8:27 GMT+09:00 Nobuhiro Iwamatsu :
> Hi,
>
> Sorry, reply was late.
>
> 2014-05-16 1:16 GMT+09:00 Didier 'OdyX' Raboud :
>> Dear Bluetooth maintainers,
>>
>> I would like to emphasize Sjoerd's point:
>>
>> Le dimanche, 27 avril 2014, 15.07:45 Sjoerd Simons a écrit :
>>> For jessie it would be good to at least have bluez 5 be available if
>>> not be used as the default for Debian. Which obviously as a first
>>> step need to have bluez 5 transition to unstable.
>>
>> For what is worth, as I mentioned on debian-devel [0], KDE can be made
>> ready for Bluez5 with two straightforward uploads of new upstream
>> versions of {lib,}bluedevil. I plan to upload these in coordination with
>> their respective maintainers to experimental in the next days.
>
> Thanks for upload!
>
>>
>> [0] https://lists.debian.org/debian-devel/2014/05/msg00076.html
>>
>>> Given it's a pretty massive transition (involving e.g. all the
>>> desktops), the thinking at the Debian gnome sprint was it would
>>> probably be best (as a temporary solution) to have both bluez 5 and
>>> bluez 4 in unstable and conflicting (so only one can be installed at
>>> any one time). In that way packages can transition at their own time
>>> instead of requiring the whole distribution in one go.
>>
>> I'm rather leaning towards deprecating Bluez4 as early as possible, but
>> that's really up to you to decide.
>
> Yes,  However, adjustment with big DE is difficult.
>
>>
>>> Would it be possible to do such a strategy in a reasonable timeframe
>>> so the transition and testing can happen with a good amount of time
>>> left before the Jessie freeze?
>>
>> Having Bluez5 in Jessie would be nice, to say the least.
>>
>
> Yes, I think too. I can already upload bluez5 to unstable as bluez part.
> Is bluedevil  2.0~rc1-1 working with bluez5? Can I upload bluze5 to
> unstable by KDE part?
> Of course, I will also ask Gnome team about this.
>
> Best regards,
>   Nobuhiro
>
> --
> Nobuhiro Iwamatsu
>iwamatsu at {nigauri.org / debian.org}
>GPG ID: 40AD1FA6
>
> ___
> Pkg-bluetooth-maintainers mailing list
> pkg-bluetooth-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-bluetooth-maintainers



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


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

Bug#750699: micro release from upstream!

[Kees Cook]

Yay! I was able to convince upstream to do a micro release, so now the
delta is tiny. I've attached the new debdiff, which shows just the cert
chain and algo updates, with user agent reporting for their end. Much much
better.

-Kees

-- 
Kees Cook@debian.org
diff -Nru duo-unix-1.8/CHANGES duo-unix-1.8.1/CHANGES
--- duo-unix-1.8/CHANGES2011-12-31 13:12:22.0 -0800
+++ duo-unix-1.8.1/CHANGES  2014-06-11 14:37:31.0 -0700
@@ -1,3 +1,10 @@
+duo_unix-1.8.1:
+
+- Update HTTPS CA certificates.
+
+- Improve support for SHA2 in HTTPS.
+
+- Send User-Agent header with each request.
 
 duo_unix-1.8:
 
diff -Nru duo-unix-1.8/configure.ac duo-unix-1.8.1/configure.ac
--- duo-unix-1.8/configure.ac   2011-12-31 13:12:46.0 -0800
+++ duo-unix-1.8.1/configure.ac 2014-06-11 14:37:31.0 -0700
@@ -7,7 +7,7 @@
 
 # Package, version, bug report address
 AC_INIT([duo_unix],
-   [1.8],
+   [1.8.1],
[duo_u...@duosecurity.com])
 
 # Tells autoconf where to find necessary build scripts and macros.
diff -Nru duo-unix-1.8/debian/changelog duo-unix-1.8.1/debian/changelog
--- duo-unix-1.8/debian/changelog   2012-06-16 11:08:56.0 -0700
+++ duo-unix-1.8.1/debian/changelog 2014-06-11 16:20:45.0 -0700
@@ -1,3 +1,10 @@
+duo-unix (1.8.1-1~deb7u1) stable-proposed-updates; urgency=medium
+
+  * New upstream micro release.
+- Fixes user-agent and certificate chain (Closes: 749903).
+
+ -- Kees Cook   Wed, 11 Jun 2014 16:15:34 -0700
+
 duo-unix (1.8-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru duo-unix-1.8/lib/cacert.h duo-unix-1.8.1/lib/cacert.h
--- duo-unix-1.8/lib/cacert.h   2011-12-31 10:38:27.0 -0800
+++ duo-unix-1.8.1/lib/cacert.h 2014-06-11 14:04:18.0 -0700
@@ -12,7 +12,7 @@
  * /C=US/O=Entrust.net/OU=www.entrust.net/CPS incorp. by ref. (limits 
liab.)/OU=(c) 1999 Entrust.net Limited/CN=Entrust.net Secure Server 
Certification Authority
  */
 
-#define CACERT_PEM \
+#define ENTRUST_PEM \
 "-BEGIN CERTIFICATE-\n"\
 "MIIE2DCCBEGgAwIBAgIEN0rSQzANBgkqhkiG9w0BAQUFADCBwzELMAkGA1UE\n"\
 "BhMCVVMxFDASBgNVBAoTC0VudHJ1c3QubmV0MTswOQYDVQQLEzJ3d3cuZW50\n"\
@@ -44,4 +44,148 @@
 "rQXvqzJ4h6BUcxm1XAX5Uj5tLUUL9wqT6u0G+bI=\n"\
 "-END CERTIFICATE-\n"
 
+/*
+ * /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Assured ID Root CA
+ */
+
+#define DIGICERT1_PEM \
+"-BEGIN CERTIFICATE-\n"\
+"MIIDtzCCAp+gAwIBAgIQDOfg5RfYRv6P5WD8G/AwOTANBgkqhkiG9w0BAQUFADBl\n"\
+"MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3\n"\
+"d3cuZGlnaWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBBc3N1cmVkIElEIFJv\n"\
+"b3QgQ0EwHhcNMDYxMTEwMDAwMDAwWhcNMzExMTEwMDAwMDAwWjBlMQswCQYDVQQG\n"\
+"EwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNl\n"\
+"cnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBBc3N1cmVkIElEIFJvb3QgQ0EwggEi\n"\
+"MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtDhXO5EOAXLGH87dg+XESpa7c\n"\
+"JpSIqvTO9SA5KFhgDPiA2qkVlTJhPLWxKISKityfCgyDF3qPkKyK53lTXDGEKvYP\n"\
+"mDI2dsze3Tyoou9q+yHyUmHfnyDXH+Kx2f4YZNISW1/5WBg1vEfNoTb5a3/UsDg+\n"\
+"wRvDjDPZ2C8Y/igPs6eD1sNuRMBhNZYW/lmci3Zt1/GiSw0r/wty2p5g0I6QNcZ4\n"\
+"VYcgoc/lbQrISXwxmDNsIumH0DJaoroTghHtORedmTpyoeb6pNnVFzF1roV9Iq4/\n"\
+"AUaG9ih5yLHa5FcXxH4cDrC0kqZWs72yl+2qp/C3xag/lRbQ/6GW6whfGHdPAgMB\n"\
+"AAGjYzBhMA4GA1UdDwEB/wQEAwIBhjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdDgQW\n"\
+"BBRF66Kv9JLLgjEtUYunpyGd823IDzAfBgNVHSMEGDAWgBRF66Kv9JLLgjEtUYun\n"\
+"pyGd823IDzANBgkqhkiG9w0BAQUFAAOCAQEAog683+Lt8ONyc3pklL/3cmbYMuRC\n"\
+"dWKuh+vy1dneVrOfzM4UKLkNl2BcEkxY5NM9g0lFWJc1aRqoR+pWxnmrEthngYTf\n"\
+"fwk8lOa4JiwgvT2zKIn3X/8i4peEH+ll74fg38FnSbNd67IJKusm7Xi+fT8r87cm\n"\
+"NW1fiQG2SVufAQWbqz0lwcy2f8Lxb4bG+mRo64EtlOtCt/qMHt1i8b5QZ7dsvfPx\n"\
+"H2sMNgcWfzd8qVttevESRmCD1ycEvkvOl77DZypoEd+A5wwzZr8TDRRu838fYxAe\n"\
+"+o0bJW1sj6W3YQGx0qMmoRBxna3iw/nDmVG3KwcIzi7mULKn+gpFL6Lw8g==\n"\
+"-END CERTIFICATE-\n"
+
+/*
+ * /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root CA
+ */
+
+#define DIGICERT2_PEM \
+"-BEGIN CERTIFICATE-\n"\
+"MIIDrzCCApegAwIBAgIQCDvgVpBCRrGhdWrJWZHHSjANBgkqhkiG9w0BAQUFADBh\n"\
+"MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3\n"\
+"d3cuZGlnaWNlcnQuY29tMSAwHgYDVQQDExdEaWdpQ2VydCBHbG9iYWwgUm9vdCBD\n"\
+"QTAeFw0wNjExMTAwMDAwMDBaFw0zMTExMTAwMDAwMDBaMGExCzAJBgNVBAYTAlVT\n"\
+"MRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5j\n"\
+"b20xIDAeBgNVBAMTF0RpZ2lDZXJ0IEdsb2JhbCBSb290IENBMIIBIjANBgkqhkiG\n"\
+"9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4jvhEXLeqKTTo1eqUKKPC3eQyaKl7hLOllsB\n"\
+"CSDMAZOnTjC3U/dDxGkAV53ijSLdhwZAAIEJzs4bg7/fzTtxRuLWZscFs3YnFo97\n"\
+"nh6Vfe63SKMI2tavegw5BmV/Sl0fvBf4q77uKNd0f3p4mVmFaG5cIzJLv07A6Fpt\n"\
+"43C/dxC//AH2hdmoRBBYMql1GNXRor5H4idq9Joz+EkIYIvUX7Q6hL+hqkpMfT7P\n"\
+"T19sdl6gSzeRntwi5m3OFBqOasv+zbMUZBfHWymeMr/y7vrTC0LUq7dBMtoM1O/4\n"\
+"gdW7jVg/tRvoSSiicNoxBN33shbyTApOB6jtSj1etX+jkMOvJwIDAQABo2MwYTAO\n"\
+"BgNVHQ8BAf8EBAMCAYYwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4EFgQUA95QNVbR\n"\
+"TLtm8KPiGxvDl7I90VUw

Bug#640604: debsigs: installation fails: Verification on package /var/cache/apt/archives/debsigs_0.1.17_all.deb failed!

[Guillem Jover]

Hi!

On Mon, 2011-09-05 at 21:53:59 +0200, Lucas Nussbaum wrote:
> Package: debsigs
> Version: 0.1.17
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: instest-20110825 instest

> > The following NEW packages will be installed:
> > debsigs
> > 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> > 11 not fully installed or removed.
> > Need to get 52.9 kB of archives.
> > After this operation, 184 kB of additional disk space will be used.
> > Get:1 http://localhost/debian/ sid/main debsigs all 0.1.17 [52.9 kB]
> > Fetched 52.9 kB in 0s (969 kB/s)
> > Authenticating /var/cache/apt/archives/debsigs_0.1.17_all.deb ...
> > debsig: Origin Signature check failed. This deb might not be signed.
> > 
> > dpkg: error processing /var/cache/apt/archives/debsigs_0.1.17_all.deb 
> > (--unpack):
> > Verification on package /var/cache/apt/archives/debsigs_0.1.17_all.deb 
> > failed!
> > configured to not write apport reports
> > Errors were encountered while processing:
> > /var/cache/apt/archives/debsigs_0.1.17_all.deb
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> The full build log is available from:
>  http://people.debian.org/~lucas/logs/2011/08/25/debsigs.log

> It is reproducible by installing your package in a clean chroot, using
> the debconf Noninteractive frontend, and priority: critical.

No, It's not, this bug report seems bogus to me. In the log from the
URL the packages start to fail to install just after debsig-verify gets
unpacked, so this cannot really be a bug in debsigs, it could be at
most a bug in either debsig-verify or dpkg. But as mentioned in the
subsequent replies dpkg has shipped with no-debsig in its default
dpkg.cfg file for a while. So my assumption is that the chroot used
had an empty or custom dpkg.cfg w/o that option enabled, i.e. a
problem in the setup. And no, there's no need for any signing of the
debsigs package at all, because those would get rejected at this point
in time anyway.

As such this bug should be closed,  but I'll leave that to the
maintainer. It's a pitty though that the package got removed from
stable due to a bogus bug report. :(

Thanks,
Guillem


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

Bug#495881: #495881 fixed in upstream commit 0dde19974

[Andreas Henriksson]

Control: tag -1 fixed-upstream

A modified version of the proposed patch was merged upstream in commit
https://github.com/karelzak/util-linux/commit/0dde19974bcbb07ce977992ab04b7dfa752d99b3

Regards,
Andreas Henriksson


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

Bug#751291: libnet: [ftbfs] use dh-autoreconf in order to build on new architectures

[Stefanos Harhalakis]

Hi Fernando,

Thanks for the patch.

The new version should find its way to unstable in the near future.

Thanks,
Stefanos

On Wednesday 11 June 2014 16:09:52 Fernando Seiti Furusato wrote:
> Package: src:libnet
> Severity: normal
> Tags: patch
> User: debian-powe...@lists.debian.org
> Usertags: ppc64el
> User: debian-de...@lists.debian.org
> Usertags: autoreconf
> 
> 
> Dear Maintainer,
> 
> Package libnet fails to build from source on ppc64el, due to 
configuration
> files being out of date.
> Running autoreconf will update them accordingly and the package will 
build
> successfully.
> The patch attached includes dh-autoreconf to the build.
> 
> Thank you.
> Fernando
> 
> 
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: ppc64el (ppc64le)
> 
> Kernel: Linux 3.13-1-powerpc64le (SMP w/4 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash

Bug#751351: xterm: pointerMode reset ignores resource setting

[Pete Wyckoff]

Package: xterm
Version: 306-1
Severity: normal

Starting with xterm-306-1, when I run /usr/bin/reset in an xterm,
the pointerMode goes back to default, ignoring my resource
setting of "never":

arf$ xrdb -query | grep pointerMode
xterm*pointerMode:  0

It looks like this is due to a change in version 305 to ReallyReset,
in charproc.c, where the mode is put back to default:

+   screen->pointer_mode = DEF_POINTER_MODE;

Is there a way to have it honor the resource setting, even
after a reset?  Thanks,

-- Pete

-- 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/2 CPU cores)
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 xterm depends on:
ii  libc6   2.19-1
ii  libfontconfig1  2.11.0-5
ii  libice6 2:1.0.8-2
ii  libtinfo5   5.9+20140118-1
ii  libutempter01.1.5-4
ii  libx11-62:1.6.2-2
ii  libxaw7 2:1.0.12-1
ii  libxft2 2.3.1-2
ii  libxmu6 2:1.1.2-1
ii  libxpm4 1:3.5.10-1
ii  libxt6  1:1.1.4-1
ii  xbitmaps1.1.1-2

Versions of packages xterm recommends:
ii  x11-utils  7.7+1

Versions of packages xterm suggests:
pn  xfonts-cyrillic  

-- 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#746078: [Pkg-bluetooth-maintainers] Bug#746078: Please provide bluez 5 in unstable

[Nobuhiro Iwamatsu]

Hi,

Sorry, reply was late.

2014-05-16 1:16 GMT+09:00 Didier 'OdyX' Raboud :
> Dear Bluetooth maintainers,
>
> I would like to emphasize Sjoerd's point:
>
> Le dimanche, 27 avril 2014, 15.07:45 Sjoerd Simons a écrit :
>> For jessie it would be good to at least have bluez 5 be available if
>> not be used as the default for Debian. Which obviously as a first
>> step need to have bluez 5 transition to unstable.
>
> For what is worth, as I mentioned on debian-devel [0], KDE can be made
> ready for Bluez5 with two straightforward uploads of new upstream
> versions of {lib,}bluedevil. I plan to upload these in coordination with
> their respective maintainers to experimental in the next days.

Thanks for upload!

>
> [0] https://lists.debian.org/debian-devel/2014/05/msg00076.html
>
>> Given it's a pretty massive transition (involving e.g. all the
>> desktops), the thinking at the Debian gnome sprint was it would
>> probably be best (as a temporary solution) to have both bluez 5 and
>> bluez 4 in unstable and conflicting (so only one can be installed at
>> any one time). In that way packages can transition at their own time
>> instead of requiring the whole distribution in one go.
>
> I'm rather leaning towards deprecating Bluez4 as early as possible, but
> that's really up to you to decide.

Yes,  However, adjustment with big DE is difficult.

>
>> Would it be possible to do such a strategy in a reasonable timeframe
>> so the transition and testing can happen with a good amount of time
>> left before the Jessie freeze?
>
> Having Bluez5 in Jessie would be nice, to say the least.
>

Yes, I think too. I can already upload bluez5 to unstable as bluez part.
Is bluedevil  2.0~rc1-1 working with bluez5? Can I upload bluze5 to
unstable by KDE part?
Of course, I will also ask Gnome team about this.

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


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

Bug#751345: linux: Sound modules list update for 3.15

[Ben Hutchings]

Control: tag -1 moreinfo

On Thu, 2014-06-12 at 00:01 +0200, Samuel Thibault wrote:
> Source: linux
> Version: 3.14-1~exp1
> Severity: normal
> Tags: patch
> 
> Hello,
> 
> Here is the sound module list update for linux 3.15.
> 
> Thanks,
> Samuel
[...]
> Index: debian/installer/modules/sound-modules
> ===
> --- debian/installer/modules/sound-modules  (révision 21419)
> +++ debian/installer/modules/sound-modules  (copie de travail)
> @@ -77,6 +77,7 @@
>  snd-hda-codec-si3054 ?
>  snd-hda-codec-via ?
>  snd-hda-codec ?
> +snd-hda-controller ?
>  snd-hda-intel ?
>  snd-hdsp ?
>  snd-hdspm ?

This is a library, not a driver, and is automatically included as a
dependency of the drivers that use it.  So unless you have a particular
reason to list it explicitly, I would rather not do so.

Ben.

-- 
Ben Hutchings
The program is absolutely right; therefore, the computer must be wrong.


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

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

[Alexander Alemayhu]

On Thu, Jun 12, 2014 at 12:22:25AM +0200, Yoann Gauthier wrote:
> Hei,
> 

Hei,

> I created the new patch to fix license error reported by lintian. With this
> new patch, I have an error during package-building : (sorry, it's in french)
> 
> dpkg-source: info: construction de postr à partir de
> ./postr_0.13.orig.tar.gz
> patching file debian/copyright
> Reversed (or previously applied) patch detected!  Skipping patch.
> 1 out of 1 hunk ignored
> dpkg-source: info: les décalages (« fuzz ») ne sont pas autorisés lors de
> l'application des correctifs
> dpkg-source: info: si le correctif
> « 05-fix_missing_license_paragraph.patch » est correctement appliqué par
> quilt, utiliser « quilt refresh » pour le mettre à jour
> dpkg-source: erreur: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B
> .pc/05-fix_missing_license_paragraph.patch/ --reject-file=- <
> postr.orig.oMZtof/debian/patches/05-fix_missing_license_paragraph.patch a
> produit une erreur de sortie de type 1
> 
> 

Taking a quick look at your changes it looks like you have fuzz in the patches
and according to dpkg fuzz is not allowed. Try updating the patch file.

Please do not push changes which are obviosly broken to the repository! It is
much better if you do things locally and only push when you see it works as
expected.

> 
> I don't understand why ? Do you have an idea ?
> 
> Regards,
> 
> Yoann
> 
> 
> 2014-06-11 14:55 GMT+02:00 Alexander Alemayhu :
> 
> > On Wed, Jun 11, 2014 at 01:56:59PM +0200, Yoann Gauthier wrote:
> > > Hello,
> > >
> >
> > Hei,
> >
> > > Okay, I will fix missing-license-paragraph-in-dep5-copyright gpl-3 during
> > > this week.
> > >
> > > To generate debian package you use : git-buildpackage ? And what is the
> > > complete lintian command ?
> > >
> >
> > Yes. git-buildpackage makes it easy to build a package. It also has some
> > nice
> > features like re-creating the upstream tarballs and much more. For lintian
> > i run 'lintian -EvIL +pedantic'. I am not sure how mentors.debian.net does
> > it.
> >
> > > Thanks,
> > >
> > > Yoann
> > >
> > >
> > >
> > > 2014-06-10 23:04 GMT+02:00 Alexander Alemayhu :
> > >
> > > > On Tue, Jun 10, 2014 at 09:15:49PM +0200, Yoann Gauthier wrote:
> > > > > Hello,
> > > > >
> > > >
> > > > Hei,
> > > >
> > > > > I updated the changelog file as asked. Thanks for the push access,
> > it's
> > > > > easier for me to make changes now :).
> > > > >
> > > > > My changelog needs a review I think, because I am not familiar with
> > > > > changeLog conventions.
> > > > >
> > > >
> > > > It looks good IMO :)
> > > >
> > > > > If you have new task to delegate, I am available.
> > > > >
> > > >
> > > > After running lintian today a new warning appears:
> > > > W: postr source: missing-license-paragraph-in-dep5-copyright gpl-3
> > > > (paragraph at line 3)
> > > >
> > > > The warning does appear on earlier commits aswell. Maybe something has
> > > > changed
> > > > in lintian, could you look into it?
> > > >
> > > > I talked with a DD and was recommended to fix the autotools warnings
> > > > reported by
> > > > lintian. He also proposed to handle the python bytecode generation in a
> > > > more
> > > > correct way. I will be looking at using dh-autoreconf to make the
> > package
> > > > free
> > > > of the autools warnings. It might take a couple of days...
> > > >
> > > > >
> > > > > Regards,
> > > > >
> > > > > Yoann
> > > > >
> > > > >
> > > > > 2014-06-10 7:57 GMT+02:00 Alexander Alemayhu :
> > > > >
> > > > > > On Mon, Jun 09, 2014 at 08:29:51PM +0200, Yoann Gauthier wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > >
> > > > > > Hei.
> > > > > >
> > > > > > > I fixed the desktop-entry-lacks-keywords-entry as asked.
> > > > > > > Find attached the patch. I used quilt to create my patch :
> > > > > > > 04-fix_desktop_keywords.patch and then git format to create patch
> > > > file.
> > > > > > >
> > > > > >
> > > > > > Good. You should also update the debian/changelog to include an
> > entry
> > > > which
> > > > > > mentions the patch. Please take a close look at the existing lines
> > to
> > > > get
> > > > > > an
> > > > > > idea of what to write.
> > > > > >
> > > > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > PS : have access (push request) to your repository will be easier
> > > > for me.
> > > > > > >
> > > > > >
> > > > > > Full access granted. You should now be able to push directly.
> > > > > >
> > > > > > > Yoann
> > > > > > >
> > > > > > >
> > > > > > > 2014-06-03 22:50 GMT+02:00 Alexander Alemayhu <
> > alexan...@bitraf.no>:
> > > > > > >
> > > > > > > > On Tue, Jun 03, 2014 at 11:45:27AM +0200, Yoann Gauthier wrote:
> > > > > > > > > Hi Alexander,
> > > > > > > > >
> > > > > > > > > What are the next tasks I can do to help for the packaging ?
> > > > > > > > >
> > > > > > > >
> > > > > > > > You could look at the desktop-entry-lacks-keywords-entry[0]
> > > > lintian tag
> > > > > > > > and try
> > > > > > > > to fix it. I was planning on fixing it but wanted to
>

Bug#751350: RFP: knowthelist -- Knowthelist - the awesome party music player

[Mario Stephan]

Package: wnpp
Severity: wishlist

* Package name: knowthelist
  Version : 2.1.2
  Upstream Author : Mario Stephan 
* URL : https://github.com/knowthelist/knowthelist
* License : LGPL
  Programming Lang: C++
  Description : Knowthelist - the awesome party music player

Easy to use for all party guests
Quick search for tracks in collection
Two players with separate playlists
Mixer with fader, 3 channel EQ and gain
FadeNow to smoothly jump to the next song
Auto fader and auto gain
Trackanalyser search for song start/end and gain setting
Auto DJ function with multiple filters for random play
Monitor player for pre listen tracks (via 2nd sound card e.g. USB)


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

Bug#751349: airspy: inappropriate archive section?

[Christoph Anton Mitterer]

Source: airspy
Version: 0.2.13.9350af1-1
Severity: minor


Hi.

Shouldn't the command line tools package airspy go to some other section
i.e. != libs ?

Cheers,
Chris.


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

Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_DE.utf8, LC_CTYPE=en_DE.utf8 (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#749795: holes in secure apt

[Christoph Anton Mitterer]

reopen 749795
stop

Hi.

I'm reopening this for now, even if the issue is solved from a technical
point of view (see below why).


In my opinion this is really some horrible bug... probably it could have
been very easily found by others, and we have no idea whether it was
exploited already or not.

Anyone who believed in getting trusted sources might have been attacked
with forged packages, and even the plain build of such package might
have undermined users' security integrity.

The same is the case with all debian build systems which probably rely
on secure APT.


So IMHO this bug definitely deserves a CVE and a DSA,... so that people
are informed that there systems might have been compromised (i.e. if an
attacker tricked them into using forged sources)... which is also why I
reopen it.

And do we need an investigation whether Debian an the Debian archives
themselves might have been intruded that way?


It's really saddening to see that such an issue could slip through,
especially when I've personally started already a few threads on
debian-devel about the security of secure APT.
The most recent one was IIRC:
https://lists.debian.org/debian-devel/2012/03/msg00549.html
but I've had one before, I think.


I think such bug shows that we can't just move on as we did till now...

From the APT perspective:

- Do we have unit checks now in APT, which basically test all commands
with unsigned repos, repos with invalid signature, packages where the
sums don't match the valid repo signatures, etc.?
We really should have this,.. and also check for things like expiry
dates.

- I also think that there should be one place of code that handles all
downloads of packages, so that we have some rock solid functions, which
do all the checks and verifications.

- I think per default APT should refuse to work with unsigned
repos/packages. One should really need some configuration switch or
option that allows this.
I don't think it's a big issue, since all the major repos are signed and
even the "end-user" tools to make own repos (like debarchiver) support
signing.
People should simply be taught to not use unsigned repos...

- That being said,... APT should always delete all cached files (repo
lists, signature files, Package and Source lists as well as downloaded
packages) as soon as a single verification error occurred at some place.
And since 3rd party programs or users may manually take stuff from
places like /var/lib/apt/lists or /var/cache/apt/archives... these
directories should contain a subdir like "unsecured/" where APT
downloads stuff to and only moves it out from there once all checks have
been passed.

- In case any even just remotely possible security issue occurs... apt
should exit with a non-zero status and not just a warning wich shell
scripts from users usually won't check for.


What about 3rd party programs and Debian in general:
There are still probably many programs which download stuff without any
verification,... or just warn which may be easily overseen:
- [c]debootstrap
I think they both default now to verify signatures (which is a good
thing)... but IIRC, debootstrap also defaults to not verify anything...
if the keyrings aren't installed - admittedly this is unlikely... but
possible... I've already had a discussion at the respective bug with
upstream, but nothing happened... I think such choices make it easily
happen for security critical situations to occur... completely
unnecessary.

- not really secure APT related: apt-listbugs
Not sure whether it uses https for getting bug infos... but since Debian
nowadays uses certs from GANDI, which we generally cannot trust,... this
is probably moot anyway.
Securely showing bugs, may be important for users, since they want to
now about bugs like "big security hole in package XYZ - don't install"

- apt-listchanges
Guess that uses local files an is therefore secure.

- apt-file
Last time I checked, the bug about not verifying the sums of the
Contents-* files was still open


- what about our build daemons and building tools like piuparts,
pbuilder, pbuilder-uml, debian-builder or qemubuilder
Do they use secure APT in ALL places? Is this constantly checked by some
unit tests?
Or are they easily tricked into using possibly insecure files, by
depending on exit statuses which are perhaps not != 0 in case of
security problems ... or by using files which were downloaded but not
removed when it was found out that they're insecure.

I think a package like e.g. pbuilder might easily operate insecurely...
it depends on [c]debootstrap for building... if debootstrap is used, but
debian-archive-keyring is not installed, then (IIRC) no signature
checking is done... in that case forged stuff may be downloaded,
chrooted into... and *bam* - already lost the game... and you don't even
need a hole like APT not checking files it gets with apt-get source.



Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Bug#684568: 684568 fixed in upstream commit 38d663a6b3

[Andreas Henriksson]

Hello!

For reference, that the bug in question is fixed in:
https://github.com/karelzak/util-linux/commit/38d663a6b30781609a8fdc0e02c0b4b76a2ed240

Regards,
Andreas Henriksson


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

Bug#751255: [Debian-med-packaging] Bug#751255: treeviewx: Please update to use wxwidgets3.0

[Charles Plessy]

Le Thu, Jun 12, 2014 at 01:20:56AM +1200, Olly Betts a écrit :
> 
> I've rebuilt your package using the attached patch.  I haven't tried
> to run it though - a specialist package like this is much better tested
> by someone who actually uses it (I don't have any suitable data, and
> I'd have little idea what to do with it even if I did!)

Hi Olly,

thanks for the patch !  I have split it up and committed it in the
source package's subversion repository.

Vcs-Browser: 
http://anonscm.debian.org/viewvc/debian-med/trunk/packages/treeviewx/trunk/
Vcs-Svn: svn://anonscm.debian.org/debian-med/trunk/packages/treeviewx/trunk/

I tried to run the patched program and I see the following error on startup.

07:21:04: can't open file 'bitmaps/treeview.xbm' (error 2: Aucun fichier ou 
dossier de ce type)
07:21:04: Failed to load image from file "bitmaps/treeview.xbm".

The strange thing is that bitmaps/treeview.xbm is not visible in the source
directory after building.  Could you have a look if the problem was caused by
the switch to wxwidgets3.0 ?

Have a nice day,

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan


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

Bug#740944: bug reports get sent to non-existing sub...@trac.transmissionbt.com

[Bob Bib]

control: found -1 2.81-1

> transmission (2.81-1) unstable; urgency=low
>
> ...
>   * [1d5de1c0] debian/control: add Bugs field

Unfortunately, I can't find any reference
to the "Bugs" field of debian/control
in the Debian Policy 3.9.5.0:
https://www.debian.org/doc/debian-policy/


Best wishes, Bob


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

Bug#751348: qutecom: Inconsistent definition of ORTP_INET6 to cause conflicting types

[Michael Tautschnig]

Package: qutecom
Version: 2.2.1+dfsg1-5
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error. Please note that we
use our research compiler tool-chain (using tools from the cbmc package), which
permits extended reporting on type inconsistencies at link time.

[...]
/usr/bin/g++  -fPIC -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -lpthread 
-Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 -lgthread-2.0 -pthread 
-lglib-2.0 -Wl,-z,relro -shared -Wl,-soname,libphapi.so -o libphapi.so 
CMakeFiles/phapi.dir/aec2.o CMakeFiles/phapi.dir/nortel.o 
CMakeFiles/phapi.dir/owpl_adapter.o CMakeFiles/phapi.dir/owpl_plugin.o 
CMakeFiles/phapi.dir/owpl_log.o CMakeFiles/phapi.dir/phapi-old.o 
CMakeFiles/phapi.dir/phapi.o CMakeFiles/phapi.dir/phaudiodriver.o 
CMakeFiles/phapi.dir/phcodec.o CMakeFiles/phapi.dir/phevents.o 
CMakeFiles/phapi.dir/phlog.o CMakeFiles/phapi.dir/phmbuf.o 
CMakeFiles/phapi.dir/phmedia-audio-file.o CMakeFiles/phapi.dir/phmedia-audio.o 
CMakeFiles/phapi.dir/phmedia.o CMakeFiles/phapi.dir/phrecorder.o 
CMakeFiles/phapi.dir/phresample.o CMakeFiles/phapi.dir/phvline.o 
CMakeFiles/phapi.dir/tonegen.o CMakeFiles/phapi.dir/wav.o 
CMakeFiles/phapi.dir/wlm.o CMakeFiles/phapi.dir/phcodec-h263.o 
CMakeFiles/phapi.dir/phcodec-h263plus.o CMakeFiles/phapi.dir/phcodec-h263flv1.o 
CMakeFiles/phapi.dir/phcodec-h264.o CMakeFiles/phapi.dir/phcodec-mpeg4.o 
CMakeFiles/phapi.dir/phmedia-video.o 
CMakeFiles/phapi.dir/phmedia-video-control.o 
CMakeFiles/phapi.dir/phmedia-video-bwcontrol.o 
CMakeFiles/phapi.dir/phcodec-avcodec-wrapper.o 
CMakeFiles/phapi.dir/phmedia-alsa.o CMakeFiles/phapi.dir/phmedia-oss.o  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/libosip2
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/owbase
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/owsl
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/eXosip/transport_manager
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/sVoIP
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/eXosip
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/ortp
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/phapi/stun
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/phapi/gsm
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/libs/owutil/cutil
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/phapi-util
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/phapi/fidlib
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/phapi/speexec
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/libs/timer
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/phapi/g722
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/phapi/g726
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/libs/owutil/util
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/libs/pixertool
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/libs/owutil/thread
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/libs/webcam
  
-L/srv/jenkins-slave/workspace/sid-goto-cc-qutecom/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/srtp
 ../libosip2/libosip2.a ../owbase/libowbase.so ../owsl/libowsl.so 
../eXosip/transport_manager/libtransport_manager.a ../sVoIP/libsvoip.a 
../eXosip/libexosip.a ../ortp/libortp.a stun/libstun.a gsm/libgsm.a 
../../libs/owutil/cutil/libowcutil.a ../phapi-util/libphapiutil.so 
fidlib/libfidlib.a speexec/libspeexec.a ../../libs/timer/libwtimer.a 
g722/libg722.a g726/libg726.a -lboost_program_options -lboost_serialization 
-lboost_signals -lboost_thread -lboost_system -luuid 
../../libs/owutil/util/libowutil.so -lavcodec -lavutil -lswscale 
../../libs/pixertool/libpixertool.a ../../libs/owutil/thread/libowthread.a 
../../libs/webcam/libwebcam.so -lglib-2.0 -lgmodule-2.0 -lgthread-2.0 
-lgobject-2.0 -lpthread -lrt -ldl -lsamplerate -lasound 
../eXosip/transport_manager/libtransport_manager.a ../owsl/libowsl.so 
../owbase/libowbase.so -lcurl ../sVoIP/libsvoip.a ../libosip2/li

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

[Yoann Gauthier]

Hei,

I created the new patch to fix license error reported by lintian. With this
new patch, I have an error during package-building : (sorry, it's in french)

dpkg-source: info: construction de postr à partir de
./postr_0.13.orig.tar.gz
patching file debian/copyright
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored
dpkg-source: info: les décalages (« fuzz ») ne sont pas autorisés lors de
l'application des correctifs
dpkg-source: info: si le correctif
« 05-fix_missing_license_paragraph.patch » est correctement appliqué par
quilt, utiliser « quilt refresh » pour le mettre à jour
dpkg-source: erreur: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B
.pc/05-fix_missing_license_paragraph.patch/ --reject-file=- <
postr.orig.oMZtof/debian/patches/05-fix_missing_license_paragraph.patch a
produit une erreur de sortie de type 1



I don't understand why ? Do you have an idea ?

Regards,

Yoann


2014-06-11 14:55 GMT+02:00 Alexander Alemayhu :

> On Wed, Jun 11, 2014 at 01:56:59PM +0200, Yoann Gauthier wrote:
> > Hello,
> >
>
> Hei,
>
> > Okay, I will fix missing-license-paragraph-in-dep5-copyright gpl-3 during
> > this week.
> >
> > To generate debian package you use : git-buildpackage ? And what is the
> > complete lintian command ?
> >
>
> Yes. git-buildpackage makes it easy to build a package. It also has some
> nice
> features like re-creating the upstream tarballs and much more. For lintian
> i run 'lintian -EvIL +pedantic'. I am not sure how mentors.debian.net does
> it.
>
> > Thanks,
> >
> > Yoann
> >
> >
> >
> > 2014-06-10 23:04 GMT+02:00 Alexander Alemayhu :
> >
> > > On Tue, Jun 10, 2014 at 09:15:49PM +0200, Yoann Gauthier wrote:
> > > > Hello,
> > > >
> > >
> > > Hei,
> > >
> > > > I updated the changelog file as asked. Thanks for the push access,
> it's
> > > > easier for me to make changes now :).
> > > >
> > > > My changelog needs a review I think, because I am not familiar with
> > > > changeLog conventions.
> > > >
> > >
> > > It looks good IMO :)
> > >
> > > > If you have new task to delegate, I am available.
> > > >
> > >
> > > After running lintian today a new warning appears:
> > > W: postr source: missing-license-paragraph-in-dep5-copyright gpl-3
> > > (paragraph at line 3)
> > >
> > > The warning does appear on earlier commits aswell. Maybe something has
> > > changed
> > > in lintian, could you look into it?
> > >
> > > I talked with a DD and was recommended to fix the autotools warnings
> > > reported by
> > > lintian. He also proposed to handle the python bytecode generation in a
> > > more
> > > correct way. I will be looking at using dh-autoreconf to make the
> package
> > > free
> > > of the autools warnings. It might take a couple of days...
> > >
> > > >
> > > > Regards,
> > > >
> > > > Yoann
> > > >
> > > >
> > > > 2014-06-10 7:57 GMT+02:00 Alexander Alemayhu :
> > > >
> > > > > On Mon, Jun 09, 2014 at 08:29:51PM +0200, Yoann Gauthier wrote:
> > > > > > Hello,
> > > > > >
> > > > >
> > > > > Hei.
> > > > >
> > > > > > I fixed the desktop-entry-lacks-keywords-entry as asked.
> > > > > > Find attached the patch. I used quilt to create my patch :
> > > > > > 04-fix_desktop_keywords.patch and then git format to create patch
> > > file.
> > > > > >
> > > > >
> > > > > Good. You should also update the debian/changelog to include an
> entry
> > > which
> > > > > mentions the patch. Please take a close look at the existing lines
> to
> > > get
> > > > > an
> > > > > idea of what to write.
> > > > >
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > PS : have access (push request) to your repository will be easier
> > > for me.
> > > > > >
> > > > >
> > > > > Full access granted. You should now be able to push directly.
> > > > >
> > > > > > Yoann
> > > > > >
> > > > > >
> > > > > > 2014-06-03 22:50 GMT+02:00 Alexander Alemayhu <
> alexan...@bitraf.no>:
> > > > > >
> > > > > > > On Tue, Jun 03, 2014 at 11:45:27AM +0200, Yoann Gauthier wrote:
> > > > > > > > Hi Alexander,
> > > > > > > >
> > > > > > > > What are the next tasks I can do to help for the packaging ?
> > > > > > > >
> > > > > > >
> > > > > > > You could look at the desktop-entry-lacks-keywords-entry[0]
> > > lintian tag
> > > > > > > and try
> > > > > > > to fix it. I was planning on fixing it but wanted to
> prioritize the
> > > > > > > autotools
> > > > > > > warnings. Hopefully we can get some advice from David.
> > > > > > >
> > > > > > > It looks like you would need to create a debian patch file to
> > > modify
> > > > > > > data/postr.desktop.in.in. If you are unfamiliar with quilt,
> take a
> > > > > look
> > > > > > > at this
> > > > > > > introduction[1].
> > > > > > >
> > > > > > > PS: Remember to fetch the latest changes, before making new
> > > changes. It
> > > > > > > might
> > > > > > > help in avoiding merge conflicts.
> > > > > > >
> > > > > > > PPS: desktop-entry-lacks-keywords-entry only occurs when using
> > > `lintian
> > > > > > > -EvIL
> > > > > > > +pedanti

Bug#709335: libvirt memory leakage on connected clients

[Jan Čapek]

I would like report this problem as well with exactly the same
symptoms. If a virt-manager stays connected to the host via qemu+ssh://
interface, the memory usage grows everyday until all system memory is
exhausted.

Is there any other workaround except for regular restarts? 

Best regards,

Jan Capek

-- 
Braiins Systems


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

Bug#751347: /etc/cron.daily/rkhunter: grep: write error

[Francois Marier]

Package: rkhunter
Version: 1.4.0-3
Severity: normal

I couldn't easily see where that error is coming from, but the daily cron job 
emits
the following message every day:

  /etc/cron.daily/rkhunter:
  grep: write error

Francois

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

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

Versions of packages rkhunter depends on:
ii  binutils   2.24.51.20140604-2
ii  debconf [debconf-2.0]  1.5.53
ii  file   1:5.18-1
ii  net-tools  1.60-26
ii  perl   5.18.2-4
ii  ucf3.0030

Versions of packages rkhunter recommends:
ii  curl7.37.0-1+b1
ii  iproute 1:3.14.0-2
ii  lsof4.86+dfsg-1
ii  postfix [mail-transport-agent]  2.11.0-1
pn  unhide.rb | unhide  
ii  wget1.15-1+b1

Versions of packages rkhunter suggests:
ii  bsd-mailx [mailx] 8.1.2-0.20131005cvs-1
pn  libdigest-whirlpool-perl  
ii  liburi-perl   1.60-1
ii  libwww-perl   6.06-1
ii  powermgmt-base1.31+nmu1
pn  tripwire  

-- debconf information:
* rkhunter/apt_autogen: true
* rkhunter/cron_daily_run: true
* rkhunter/cron_db_update: true


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

Bug#751345: linux: Sound modules list update for 3.15

[Samuel Thibault]

Source: linux
Version: 3.14-1~exp1
Severity: normal
Tags: patch

Hello,

Here is the sound module list update for linux 3.15.

Thanks,
Samuel

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

Kernel: Linux 3.14.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Index: debian/installer/modules/sound-modules
===
--- debian/installer/modules/sound-modules  (révision 21419)
+++ debian/installer/modules/sound-modules  (copie de travail)
@@ -77,6 +77,7 @@
 snd-hda-codec-si3054 ?
 snd-hda-codec-via ?
 snd-hda-codec ?
+snd-hda-controller ?
 snd-hda-intel ?
 snd-hdsp ?
 snd-hdspm ?

Bug#751346: man page for totem-audio-preview

[Milan Kupcevic]

Package: totem
Tags: patch

A patch adding totem-audio-preview man page is attached.

Milan

diff -Nru ./data/Makefile.am ../totem-3.12.1/data/Makefile.am
--- ./data/Makefile.am	2014-03-23 09:13:08.0 -0400
+++ ../totem-3.12.1/data/Makefile.am	2014-06-11 17:18:07.239050365 -0400
@@ -9,7 +9,7 @@
 EXTRA_DIST += $(bugreport_SCRIPTS)
 
 # Man pages
-man_MANS = totem.1 totem-video-thumbnailer.1
+man_MANS = totem.1 totem-video-thumbnailer.1 totem-audio-preview.1
 totem-video-thumbnailer.1: totem-video-thumbnailer.pod
 	$(AM_V_GEN) pod2man -c "" -s 1 -q none -n totem-video-thumbnailer -r GNOME $< > $@
 EXTRA_DIST += \
diff -Nru ./data/Makefile.in ../totem-3.12.1/data/Makefile.in
--- ./data/Makefile.in	2014-04-30 05:41:21.0 -0400
+++ ../totem-3.12.1/data/Makefile.in	2014-06-11 17:18:22.475050195 -0400
@@ -488,7 +488,7 @@
 bugreport_SCRIPTS = totem-bugreport.py
 
 # Man pages
-man_MANS = totem.1 totem-video-thumbnailer.1
+man_MANS = totem.1 totem-video-thumbnailer.1 totem-audio-preview.1
 
 # UI files and images
 stuffdir = $(pkgdatadir)
diff -Nru ./data/totem-audio-preview.1 ../totem-3.12.1/data/totem-audio-preview.1
--- ./data/totem-audio-preview.1	1969-12-31 19:00:00.0 -0500
+++ ../totem-3.12.1/data/totem-audio-preview.1	2014-06-10 21:31:04.220334100 -0400
@@ -0,0 +1,49 @@
+.\" Copyright (C) 2014 Milan Kupcevic 
+.\"
+.\" This file is free software; you may redistribute it and/or modify
+.\" it under the terms of the GNU General Public License as
+.\" published by the Free Software Foundation; either version 2,
+.\" or (at your option) any later version.
+.\"
+.\" This file is distributed in the hope that it will be useful, but
+.\" WITHOUT ANY WARRANTY; without even the implied warranty of
+.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+.\" GNU General Public License for more details.
+.\"
+.\" You should have received a copy of the GNU General Public License 
+.\" along with this; if not write to the Free Software Foundation, Inc.
+.\" 59 Temple Place, Suite 330, Boston, MA 02111-1307  USA
+.TH totem\-audio\-preview 1 "2014\-06\-08" "GNOME" "User Commands"
+.SH NAME
+totem\-audio\-preview \- play audio files
+.SH SYNOPSIS
+.B totem\-audio\-preview
+.RI [ OPTION ]... " " [ FILE ]...
+.SH DESCRIPTION
+.B totem\-audio\-preview 
+is primarily used by GNOME applications for audio preview purposes.
+.SH OPTIONS
+.TP
+.B \-h, \-\-help
+Display help.
+.TP
+.B \-\-help-gst
+Display GStreamer options.
+.TP
+.B \-m, \-\-mimetype
+Display supported mime\-types.
+.TP
+.B \-\-g\-fatal\-warnings
+Make all warnings fatal.
+.PP
+When no FILE is specified, read standard input.
+.SH AUTHOR
+.B totem\-audio\-preview 
+was written by Bastien Nocera .
+.PP 
+This manual page was written by Milan Kupcevic for the Debian Project.
+.SH SEE ALSO
+.PP
+.BR \%totem\-video\-thumbnailer (1),
+.BR \%totem (1), 
+.BR \%nautilus (1)

Bug#751344: netgen: please re-enable the linking with libav libraries

[Francesco Poli (wintermute)]

Package: netgen
Version: 4.9.13.dfsg-8
Severity: wishlist

Hello Debian Science Maintainers,
could you please re-enable the linking of netgen with libav libraries?

As noted on bug #618968 [1], an up-to-date netgen package depending on oce
packages version 0.15-x (currently in unstable and testing) is allowed
to link with libav.

[1] https://bugs.debian.org/618968#194

Having netgen with libav functionality enabled in jessie would be great.
Thanks for your time!


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

Bug#751334: nvidia-kernel-dkms: after kernel upgrade from 3.2 to 3.14, root ops fail once X is started

[JS]

I'm attaching a copy of /var/log/Xorg.0.log with nvidia and X running on the 
3.2 kernel, which works fine.

One of the odd things in the Xorg log file when this ran on the 3.14 kernel 
were lines like these (they are
not present when running the 3.2 kernel):

/var/log/Xorg.1.log:[ 48327.144] drmOpenDevice: node name is /dev/dri/card0
/var/log/Xorg.1.log:[ 48327.148] drmOpenByBusid: drmOpenMinor returns -1
/var/log/Xorg.1.log:[ 48327.148] drmOpenDevice: node name is /dev/dri/card1
/var/log/Xorg.1.log:[ 48327.152] drmOpenByBusid: drmOpenMinor returns -1
/var/log/Xorg.1.log:[ 48327.152] drmOpenDevice: node name is /dev/dri/card2


All the libdrm libraries in my system were up to date.


thanks,
-jack

Xorg.0.log
Description: Binary data

Bug#680738: salome-gui: links with both GPL-licensed and GPL-incompatible libraries

[Francesco Poli]

On Sun, 23 Feb 2014 12:49:21 +0100 Francesco Poli wrote:

> On Wed, 18 Dec 2013 22:06:48 +0100 Francesco Poli wrote:
[...]
> Now, the remaining steps are:
> 
> > 
> >  3a) a new version of package salome-gui depending on this new version
> > of package oce will close bug #680738
[...]

Hello Debian Science Maintainers,
is there any progress on bug #680738?

As previously said, an updated salome-gui package depending on oce
packages version 0.15-x (currently in unstable and testing) would
suffice to close the bug report.

Having salome-gui ready to be released in jessie would be great.
Thanks for your time!


-- 
 http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
 New GnuPG key, see the transition document!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpmf1DW6mlMX.pgp
Description: PGP signature

Bug#698527: Bug#680738: salome-gui: links with both GPL-licensed and GPL-incompatible libraries

[Francesco Poli]

On Sun, 23 Feb 2014 12:49:21 +0100 Francesco Poli wrote:

> On Wed, 18 Dec 2013 22:06:48 +0100 Francesco Poli wrote:
[...]
> Now, the remaining steps are:
[...]
> >  3b) a new version of package elmer depending on this new version of
> > package oce will close bug #698527, re-enabling the building of
> > ElmerGUI, *as long as* the OpenSSL linking issue has been solved in the
> > meanwhile
[...]

Hello Debian Science Maintainers,
is there any progress on bug #698527?

Has the OpenSSL linking issue been addressed?
As previously said, once the OpenSSL issue is solved, an updated elmer
package depending on oce packages version 0.15-x (currently in unstable
and testing) may re-enable the building of ElmerGUI and close the bug
report.

Having elmer ready to be released in jessie would be great (please
remember that there's also bug #740463 to be addressed...).
Thanks for your time!


-- 
 http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
 New GnuPG key, see the transition document!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpqmm8AMHjT8.pgp
Description: PGP signature

Bug#751343: python-tornado: FTBFS on mips due to test failure

[Scott Kitterman]

Source: python-tornado
Version: 3.2.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

While rebuilding your package on mips as part of the python3.3 removal
transition, the following test failure (and FTBFS) ocurred:

# python3 tests only in autopkgtest because I'm lazy
set -e && for pyvers in 2.7; do \
PYTHONPATH=/«PKGBUILDDIR» python$pyvers ./tornado/test/runtests.py; \
done
...sss..s.Fsss...sssss...s.s...ssss...s.s...
==
FAIL: test_multi_performance (tornado.test.gen_test.GenEngineTest)
--
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/tornado/testing.py", line 427, in wrapper
functools.partial(f, self), timeout=timeout)
  File "/«PKGBUILDDIR»/tornado/ioloop.py", line 389, in run_sync
return future_cell[0].result()
  File "/«PKGBUILDDIR»/tornado/concurrent.py", line 129, in result
raise_exc_info(self.__exc_info)
  File "/«PKGBUILDDIR»/tornado/stack_context.py", line 302, in wrapped
ret = fn(*args, **kwargs)
  File "/«PKGBUILDDIR»/tornado/gen.py", line 574, in inner
self.set_result(key, result)
  File "/«PKGBUILDDIR»/tornado/gen.py", line 500, in set_result
self.run()
  File "/«PKGBUILDDIR»/tornado/gen.py", line 531, in run
yielded = self.gen.send(next)
  File "/«PKGBUILDDIR»/tornado/test/gen_test.py", line 327, in 
test_multi_performance
self.assertLess(end - start, 1.0)
AssertionError: 1.4046919345855713 not less than 1.0

--
Ran 739 tests in 42.257s

FAILED (failures=1, skipped=76)
Some tests were skipped because: PEP 380 not available, futures module
not present, mock package not present, needs fix, pycares module not
present, pycurl module not present, ssl.SSLContext not present,
tornado.speedups module not present, twisted module not present
[E 140611 20:26:50 testing:611] FAIL
make[1]: *** [override_dh_auto_test] Error 1
debian/rules:31: recipe for target 'override_dh_auto_test' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
debian/rules:9: recipe for target 'build-arch' failed
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


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

Bug#751342: bison: enable verbose build logs

[Helmut Grohne]

Package: bison
Version: 2:3.0.2.dfsg-2
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

Dear Maintainer,

bison fails to build here. I did not yet figure whether this is caused
by my build environment, because the logs reveal too little detail.
Please make the log more verbose. For rationale see:
https://wiki.debian.org/ReleaseGoals/VerboseBuildLogs

Please consider the attached patch.

Helmut
diff -Nru bison-3.0.2.dfsg/debian/changelog bison-3.0.2.dfsg/debian/changelog
--- bison-3.0.2.dfsg/debian/changelog
+++ bison-3.0.2.dfsg/debian/changelog
@@ -1,3 +1,10 @@
+bison (2:3.0.2.dfsg-2.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * Enable verbose build logs. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 10 Jun 2014 19:29:18 +0200
+
 bison (2:3.0.2.dfsg-2) unstable; urgency=low
 
   * Fix parallel builds by inhibiting example code extraction in Makefiles
diff -Nru bison-3.0.2.dfsg/debian/rules bison-3.0.2.dfsg/debian/rules
--- bison-3.0.2.dfsg/debian/rules
+++ bison-3.0.2.dfsg/debian/rules
@@ -12,6 +12,9 @@
 override_dh_auto_clean:
[ ! -f $(SRCDIR)/Makefile ] || dh_auto_clean
 
+override_dh_auto_configure:
+   dh_auto_configure -- --disable-silent-rules
+
 override_dh_auto_build:
# Touch all files in the dependency tree of bison.info to
# inhibit makeinfo invocation in the build process.

Bug#746994: Same bug on my box

[Nathan Scott]

- Original Message -
> Hi,
> 
> I see this ps error too on my box, version 3.9.4. Can it be overcome to
> try building until 3.9.5 is out? I suspect there are issues with make
> 4.0 too.

The fix is in git://git.performancecopilot.org/pcp dev branch - it would
be great if you could use that and confirm the fix?

pcp-3.9.5 will be released and uploaded next week, so the wait shouldn't
be too long now.

cheers.

--
Nathan


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

Bug#751341: Acknowledgement (debian/control missing VCS tags)

[Hans-Christoph Steiner]

Tags: patch

Attached is a patch made with `git format-patch -n1` that can be applied using
`git am`.  It adds the missing VCS tags.
From 8f8455e3889d7fe9138f38c78b757d8049463f2b Mon Sep 17 00:00:00 2001
From: Hans-Christoph Steiner 
Date: Wed, 11 Jun 2014 17:36:27 -0400
Subject: [PATCH 1/1] add Vcs tags (Closes: #751341)

---
 debian/control | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debian/control b/debian/control
index 60be58a..11c718a 100644
--- a/debian/control
+++ b/debian/control
@@ -4,6 +4,8 @@ Priority: optional
 Maintainer: Bastian Blank 
 Build-Depends: debhelper (>> 7), libdebian-installer4-dev (>= 0.81~), libdebconfclient0-dev (>= 0.40), autotools-dev, libbz2-dev, liblzma-dev, zlib1g-dev
 Standards-Version: 3.9.0
+Vcs-Git: git://git.debian.org/users/waldi/cdebootstrap.git
+Vcs-Browser: http://anonscm.debian.org/gitweb/?p=users/waldi/cdebootstrap.git
 
 Package: cdebootstrap
 Architecture: any
-- 
1.9.1



signature.asc
Description: OpenPGP digital signature

Bug#751048: Sponsorship of newer Fizsh package

[Axel Beckert]

Hi Guido,

Guido van Steen wrote:
> Regarding the upstream signature file I (as upstream) have produced a file
> called ./fizsh-1.0.6.tar.gz.asc:
> 
> > gpg --armor --detach-sig ./fizsh-1.0.6.tar.gz
> 
> I uploaded it to:
> 
> http://sourceforge.net/projects/fizsh/files/fizsh-1.0.6.tar.gz.asc
> 
> After this I amended the watch file:
> 
> """version=3
> 
> options=pgpsigurlmangle=s/$/.asc/ \
> http://sf.net/fizsh/fizsh-([0-9]\.[0-9]\.[0-9]+)\.tar\.gz"""
> 
> and issued:
> 
> > uscan --verbose --debug --force-download
> 
> This seems to work OK. Both the source file and the signature file are
> downloaded, and the signature is checked.

Without having tested it myself, this looks fine. Thanks for your effort!

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#751341: debian/control missing VCS tags

[Hans-Christoph Steiner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: cdebootstrap
Version: 0.5.10
Severity: normal

debian/control is missing Vcs-Git and Vcs-Browser, making it difficult to
find the original source repo.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: GPG for Android - https://guardianproject.info/code/gnupg/
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJTmMogAAoJEJ8P5Yc3S76BVXIQAKUvTj5MGad2AcB+lo6IdWcJ
IiMOIdNaWjvoBm9yWzg4Ct/joqrmTHn3iNbzNi1IcihRis73YbWSr5tKfhd7pZDq
80uTUKo9FHNNsU4Z9GudRboE9bVvqmRv7xdSQKPxoulAtVyYQR3Q+Q4SUgtKxEzJ
zJ8ppH0Lw60ZAHsUSlSY4s2p7w8po7Zdys2EXyhVWq9ULXqgP0Ot2msta6qtBM6K
IEk3PDv8fOxQ3xDHfPs/6/ufl6gr5QTcoG78iRIuA3vEU9KCBJu9XON/f+9T/FWv
Q6XPjNn2SWXk3iOekyHroIVyBYYr1aLXrA9rKD8yXUvnxto5LrSIwLrDoJ54syMQ
Lf11ZYOara17tI9SY7lsxtFVZqUMrYV5j3In5jdSo0CThawxCh14pe9J3r2JxwNh
FLq+qhWxf8aVrpGum/jRxLBGLyOKVWCR1Amnhej5AY0EQRrBh+TcoFskw91ZAlV0
zqPZ99Y1tchFVgWwduxphg7di/tx23snwJ/S7LpFcEQcUXxZEdiSpNa/+ZXt6eZk
oUmutdzSWXQISUzdKzjd7xn65AxjjMXiuWxEZLOmNWm/GyMxSf/9By5d+1XTDJ/8
4qyahPETh44wcOve6Jj45vgW4MDmx98SDsHcJFnnyoF5ppsd5SOWEgSE04joMIHz
ItCd+XA5Q4S8RTIVZzBe
=qxEx
-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#746994: Same bug on my box

[Svante Signell]

Hi,

I see this ps error too on my box, version 3.9.4. Can it be overcome to
try building until 3.9.5 is out? I suspect there are issues with make
4.0 too.


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

Bug#751340: flash-kernel: Add support for Wandboard i.MX6 Quad Board.

[Vagrant Cascadian]

Package: flash-kernel
Version: 3.20
Severity: wishlist
Tags: patch

The following patch adds support for "Wandboard i.MX6 Quad Board.", and lays
the groundwork for supporting other Wandboard models.

Unfortunately, it does not work out of the box with the u-boot in Debian, as
bootscript support was removed from the default bootcmd, but I will be fixing
that soon...

Two options to work around this, the first is setting bootcmd and saving the
environment:

  bootcmd=load mmc 0:1 ${loadaddr} /boot.scr || load mmc 0:1 ${loadaddr} 
/boot/boot.scr && source ${loadaddr}

Alternately, placing a uEnv.txt on the first partition, fat formatted, to load
the bootscript:

  uenvcmd=load mmc 0:1 ${loadaddr} /boot.scr || load mmc 0:1 ${loadaddr} 
/boot/boot.scr && source ${loadaddr}


commit b0bc3b63b3cf54d371f6c7aadb94684b4362bb99
Author: Vagrant Cascadian 
Date:   Tue Jun 10 23:10:31 2014 -0700

Add support for Wandboard i.MX6 Quad Board.

diff --git a/bootscript/bootscr.wandboard b/bootscript/bootscr.wandboard
new file mode 100644
index 000..6e1a5c3
--- /dev/null
+++ b/bootscript/bootscr.wandboard
@@ -0,0 +1,20 @@
+# boot script for Wandboard
+
+setenv device mmc
+setenv partition ${mmcdev}:${mmcpart}
+if test -z "${ramdiskaddr}" ; then
+   setenv ramdiskaddr 0x1300
+fi
+setenv bootargs '@@LINUX_KERNEL_CMDLINE@@'
+
+image_locations='/boot/ /'
+kvers='@@KERNEL_VERSION@@'
+
+for pathprefix in ${image_locations}
+do
+  load ${device} ${partition} ${loadaddr} ${pathprefix}vmlinuz-${kvers} \
+  && load ${device} ${partition} ${fdt_addr} ${pathprefix}dtb-${kvers} \
+  && load ${device} ${partition} ${ramdiskaddr} 
${pathprefix}initrd.img-${kvers} \
+  && echo "Booting Debian ${kvers} from ${device} ${partition}..." \
+  && bootz ${loadaddr} ${ramdiskaddr}:${filesize} ${fdt_addr}
+done
diff --git a/db/all.db b/db/all.db
index ec685c2..6c31fec 100644
--- a/db/all.db
+++ b/db/all.db
@@ -532,6 +532,13 @@ Method: android
 Android-Boot-Device: /dev/mmcblk0
 Required-Packages: abootimg
 
+Machine: Wandboard i.MX6 Quad Board
+Kernel-Flavors: armmp
+DTB-Id: imx6q-wandboard.dtb
+Boot-Script-Path: /boot/boot.scr
+U-Boot-Script-Name: bootscr.wandboard
+Required-Packages: u-boot-tools
+
 Machine: WITS A31 Colombus Evaluation Board
 Kernel-Flavors: armmp armmp-lpae
 Boot-Script-Path: /boot/boot.scr


Thanks!

live well,
  vagrant


signature.asc
Description: Digital signature

Bug#751339: RFP: ath9k-htc-firmware -- free firmware for Atheros AR7010/AR9271 wireless adapters

[Daniel Kahn Gillmor]

Package: wnpp
Severity: wishlist

* Package name: ath9k-htc-firmware
  Version : 1.3.2
  Upstream Author : Qualcomm Atheros
* URL : http://jxself.org/ath9k-htc/
* License : ClearBSD
  Programming Lang: C, assembly
  Description : free firmware for Atheros AR7010/AR9271 wireless adapters

ath9k-ftc-firmware provides a free implementation of firmware for two
available wireless chipsets.

the GNU project has endorsed this hardware as "respects your freedom"
due to the freeness of the licensing:

 
https://www.fsf.org/news/tehnoetic-wireless-usb-adapter-now-fsf-certified-to-respect-your-freedom

It would be great to ship these firmware modules in debian now that we
have the source.  If we can make it easier for people to improve them,
that would be great.

Unfortunately, the build process appears to be a little bit involved:

https://trisquel.info/en/forum/how-install-ath9k-htc-firmware-atheros-communications-inc-ar9271

while it's just "make toolchain && make firmware", the "make
toolchain" step fetches several free software libraries and packages
(and specific versions of those packages: libgmp 5.0.5, libmpfr 3.1.1,
libmpc 1.0.1, binutils 2.23.1, and gcc 4.7.2), patches a few of them
(gcc and binutils in particular), and then uses the fetched/patched
software to build the firmware statically.

This presents some packaging challenges because it doesn't model the
usual debian workflow.  Maybe someone with more experience packaging
firmware can pick this up so that we can fully-support this hardware
in debian?

   --dkg


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

Bug#751338: pkg-kde-tools: mark binary pkg-kde-tools with M-A:foreign

[Helmut Grohne]

Package: pkg-kde-tools
Version: 0.15.13
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

Dear Maintainer,

pkg-kde-tools currently causes a number of packages to have
unsatisfiable cross-Build-Depends, because it is Arch:all without
M-A:foreign. Affected source packages include:

attica phonon grantlee qca2 libgc qtbase-opensource-src polkit-qt-1
phonon-backend-gstreamer qt4-x11 soprano qjson qt-assistant-compat
strigi libiodbc2 qtbase-opensource-src mozjs qtwebkit

It seems that the scripts contained in pkg-kde-tools do already support
multiarch and cross-compilation. In addition Ubuntu treats all Arch:all
packages as M-A:foreign in Build-Depends and has not reported on
problems. It appears that adding M-A:foreign is safe here.

Thanks for considering

Helmut
diff -Nru pkg-kde-tools-0.15.13/debian/changelog 
pkg-kde-tools-0.15.13+nmu1/debian/changelog
--- pkg-kde-tools-0.15.13/debian/changelog  2014-02-23 13:09:30.0 
+0100
+++ pkg-kde-tools-0.15.13+nmu1/debian/changelog 2014-06-11 23:13:20.0 
+0200
@@ -1,3 +1,10 @@
+pkg-kde-tools (0.15.13+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark binary pkg-kde-tools as M-A:foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 11 Jun 2014 23:12:58 +0200
+
 pkg-kde-tools (0.15.13) unstable; urgency=medium
 
   [ Maximiliano Curia ]
diff -Nru pkg-kde-tools-0.15.13/debian/control 
pkg-kde-tools-0.15.13+nmu1/debian/control
--- pkg-kde-tools-0.15.13/debian/control2014-02-23 13:09:30.0 
+0100
+++ pkg-kde-tools-0.15.13+nmu1/debian/control   2014-06-11 23:13:32.0 
+0200
@@ -17,6 +17,7 @@
 Recommends: dpkg-dev (>= 1.15.6~), libwww-perl
 Suggests: debhelper (>= 7.3.16), cdbs
 Breaks: kdelibs5-dev (<< 4:4.2.2), dpkg-dev (<< 1.15.6~)
+Multi-Arch: foreign
 Description: various packaging tools and scripts for KDE Applications
  This package contains a variety of packaging tools and build scripts that may
  be very useful when packaging KDE applications. Even if you are a maintainer

Bug#751282: pbuilder overrides keyring

[Thorsten Glaser]

Phillip Susi dixit:

>specified in the suite script.  This breaks the creation of a pbuilder
>for ubuntu since the keyring is forced back to debian's.

It doesn;t because you;re supposed to add --keyring to the command
line calling cowbuilder --create by yourself.

bye,
//mira“BTDT”bilos
-- 
“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”


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

Bug#751237: claws-mail: SEGV when trying to get IMAP mail

[Shane Kerr]

Ricardo,

On Wed, 11 Jun 2014 16:06:24 +0200
Ricardo Mones  wrote:

>   You can install claws-mail-dbg package to have debug symbols. That
> way backtraces are more meaningful. Can you reproduce it that way and
> post the new backtrace?
>
>   Be sure to use ‘thread apply all bt’ within gdb (claws-mail is
> multi-threaded).

Sure, here is the pertinent output:


Core was generated by `claws-mail'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __GI___pthread_mutex_lock (mutex=0x3) at ../nptl/pthread_mutex_lock.c:66
66  ../nptl/pthread_mutex_lock.c: No such file or directory.
(gdb) thread apply all bt

Thread 3 (Thread 0x7fc9c20b2a00 (LWP 16309)):
#0  0x7fc9bbe76d5d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fc9bd6a8fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc9bd6a90ec in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc9c117f341 in gtk_main_iteration ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#4  0x005bd075 in threaded_run (folder=0x1449220, 
param=param@entry=0x7fffd7ca4370, result=result@entry=0x7fffd7ca4340, 
func=func@entry=0x5bd130 ) at imap-thread.c:445
#5  0x005bf671 in imap_threaded_connect_ssl (
folder=folder@entry=0x1449220, 
server=0x140de70 "imap.time-travellers.nl.eu.org", port=port@entry=993)
at imap-thread.c:577
#6  0x004a0780 in imap_session_new (account=0x140da00, 
folder=0x1449220) at imap.c:1148
#7  imap_session_get (folder=folder@entry=0x1449220) at imap.c:1034
#8  0x004a2183 in imap_scan_required (folder=0x1449220, 
_item=0x14874e0) at imap.c:4722
#9  0x0048e9c0 in folder_item_process_open (before_proc_func=0x0, 
after_proc_func=0x0, data=0x0, item=0x14874e0) at folder.c:2002
#10 folder_item_open (item=item@entry=0x14874e0) at folder.c:2038
---Type  to continue, or q  to quit---
#11 0x00498ec3 in folderview_selected (ctree=0x10fe400, row=0x1586520, 
column=-1, folderview=0x12b37c0) at folderview.c:2111
#12 0x7fc9bd9783b8 in g_closure_invoke ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x7fc9bd989d3d in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x7fc9bd991a29 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x7fc9bd991ce2 in g_signal_emit ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x005fb84c in gtk_cmctree_select (ctree=ctree@entry=0x10fe400, 
node=0x1586520) at gtkcmctree.c:3904
#17 0x005fbd6d in real_unselect_all (clist=0x10fe400)
at gtkcmctree.c:2882
#18 0x006186a8 in gtk_sctree_real_unselect_all (clist=0x10fe400)
at gtksctree.c:792
#19 0x006172e7 in select_row (sctree=0x10fe400, row=1, col=0, 
state=, _node=0x0) at gtksctree.c:383
#20 0x00618f36 in gtk_sctree_button_press (widget=, 
event=0x1300d20) at gtksctree.c:554
#21 0x7fc9c11814f5 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#22 0x7fc9bd9783b8 in g_closure_invoke ()
---Type  to continue, or q  to quit---
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#23 0x7fc9bd989afb in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x7fc9bd9916f9 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 0x7fc9bd991ce2 in g_signal_emit ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#26 0x7fc9c1291114 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#27 0x7fc9c117fca4 in gtk_propagate_event ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#28 0x7fc9c118005b in gtk_main_do_event ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#29 0x7fc9c0dfb1fc in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#30 0x7fc9bd6a8e04 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x7fc9bd6a9048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x7fc9bd6a930a in g_main_loop_run ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x7fc9c117f147 in gtk_main ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#34 0x00449ca7 in main (argc=1, argv=0x7fffd7ca7358) at main.c:1559
---Type  to continue, or q  to quit---

Thread 2 (Thread 0x7fc9a26b5700 (LWP 16310)):
#0  0x7fc9bbe76d5d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fc9bd6a8fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc9bd6a930a in g_main_loop_run ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc9c0193e16 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7fc9bd6cdf15 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fc9be4500ca in start_thread (arg=0x7fc9a26b5700)
at pthread_create.c:312
#6  0x7fc9bbe81ffd in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fc9942c6700 (LWP 16321)):
#0  __GI_

Bug#751048: Sponsorship of newer Fizsh package

[Guido van Steen]

Hi Axel,

Thank you for your review.

Regarding the upstream signature file I (as upstream) have produced a file
called ./fizsh-1.0.6.tar.gz.asc:

> gpg --armor --detach-sig ./fizsh-1.0.6.tar.gz

I uploaded it to:

http://sourceforge.net/projects/fizsh/files/fizsh-1.0.6.tar.gz.asc

After this I amended the watch file:

"""version=3

options=pgpsigurlmangle=s/$/.asc/ \
http://sf.net/fizsh/fizsh-([0-9]\.[0-9]\.[0-9]+)\.tar\.gz"""

and issued:

> uscan --verbose --debug --force-download

This seems to work OK. Both the source file and the signature file are
downloaded, and the signature is checked.

Is this how it can be done?

Thank for your help!

Guido

P.S. I will finish the remaining issues within a few days.



On Tue, Jun 10, 2014 at 1:06 AM, Axel Beckert  wrote:

> Hi Guido,
>
> TL;DR: Most stuff is fine, but for an upload, I'd like to have at least
> debian/copright to be streamlined. Fixes for the remaining remarks are
> of course appreciated, too. Details see below.
>
> (And if you don't mind that it there will be a slightly different
> package in Debian than on SourceForge, I'd prefer that package to have
> the version 1.0.6-1, too.)
>
> On Sun, Jun 08, 2014 at 11:21:03AM +0200, Guido van Steen wrote:
> > I have just uploaded a new version of Fizsh to Sourceforge. This is
> version
> > 1.0.6. I have also uploaded the corresponding Debian source package to
> > Debian Mentors. This package is availabe at
> > http://mentors.debian.net/debian/pool/main/f/fizsh
> >
> > Could you please review the package? I looking forward to reading your
> > review.
>
> So far I noticed the following things:
>
>
> debian/copyright:
>
> * The licenses "BSD-3-clause~zsh-history-substring-search-contributors",
>   "BSD-3-clause~fizsh" and
>   "BSD-3-clause~zsh-syntax-highlighting-contributors" seem to be
>   identical word-wise. In that case the license only needs to be
>   spelled out respectively defined once.
>
>   Of course they differ in the copyright holders, but those are
>   already listed in the "Files:" starting paragraphs and should only
>   be listed there.
>
> * The "License:" starting paragraphs only define the license text and
>   do not need verbatim formatting. They should be word-wrapped if
>   lines are longer than 80 columns. Comments signs from licenses
>   copied from source code headers can and should be dropped.
>
>
> debian/README: This file should be probably better named
> debian/README.source.
>
>
> debian/rules:
>
> * lintian warning script-not-executable
>
>   # the scripts in the "./scripts/" directory of the source package are
>   # copied to both "./debian/usr/bin/" and "./debian/etc/fizsh/". they
>   # are also copied to "./debian/fizsh/usr/share/fizsh/", but they are
>   # not meant to be copied there. moreover they end up there without the
>   # executable bit, which causes lintian to complain about
>   # "script-not-executable". therefore they are explicitly removed after
>   # dh_install.
>
>   While it is good to not have the files in the package twice, this
>   maybe a case where it may have been better to override the lintian
>   warning as the files are meant to be sourced (if it works without
>   them being executables). This not seldom with shell-related
>   packages.
>
>   So just decided if you want them user-modifiable or not and put them
>   in either /etc/fizsh or /usr/share/fizsh and override the above
>   mentioned lintian warning.
>
>   Another way to get rid of that lintian warning would be to remove the
>   shebang lines from those scripts. They're not needed anyway if the
>   scripts are just sourced.
>
> * A general remark on lines like the following:
>
>   [ -d foo ] && rm -rf foo || true
>
>   Just using "rm -rf foo" should suffice and is easier to read:
>
>   * If the directory doesn't exist, it does nothing
>   * It does exit with return code 0 even if the file does not exist.
>
> * Warnings from configure:
>
>   # without the following override the ./configure script would be called
> with two
>   # unrecognized options: --disable-maintainer-mode,
> --disable-dependency-tracking
>   override_dh_auto_configure:
> ./configure \
> --prefix=/usr \
> --includedir=\${prefix}/include \
> --mandir=\${prefix}/share/man \
> --infodir=\${prefix}/share/info \
> --sysconfdir=/etc \
> --localstatedir=/var
>
>   I think those warnings can be safely ignored and hence the override
>   could be dropped. I'm though fine if you are annoyed by the warnings
>   and prefer to keep the override. (I'd be rather annoyed by such a
>   long override. :-)
>
> debian/changelog:
>
> * While it is acceptable, I find the style with a blank line between
>   each item hard to read.
>
> * I'd also indent any line not starting wit "*" by two blanks.
>
>
> debian/watch and .sig files:
>
> * The .sig files mentioned in the context of pgpsigurlmangle are meant
>   to be signature files, not public key files as on [1]. See the
>   documentation f

Bug#751114: radiusd-livingston: Conflicting declarations of function req2str

[Paul Martin]

On Tue, Jun 10, 2014 at 01:58:22PM +0100, Michael Tautschnig wrote:

> As, however, the return value appears to be redundant, this should not cause
> actual problems at present.

Indeed! It's really really old Livingston code.

-- 
Paul Martin 


signature.asc
Description: Digital signature

Bug#678446: Updated util-linux to 2.24.2, ok to upload to experimental?

[Andreas Henriksson]

Hello again Adam Conrad!

Thanks for your initial quick followup.

I'm writing another followup to your mail as I probably was a little
too quick to answer and send. I ofcourse have many questions about
your plans and work which I should have included in my last mail...

Have you posted any information on what you're working on
anywhere already?

Is your current work available anywhere?

What plans do you have that you have not yet had time to implement?

Is there anything I can help you out with?

When do you expect to upload anything to the Debian archive?

What, if any, of your plans do you consider blockers before
uploading a new version to the archive?

Are you aiming for getting your new changes into Jessie or are
do you think it's too late in the process to introduce big changes
in util-linux now?

You seemed quite interesting in avoiding duplicate work in your
initial mail. Do you have any plans on how we can improve
collaboration around util-linux packaging? 
If we've already duplicated work that is unfortunate but sometimes
unavoidable. What in my opinion would be much worse is if we
can't find a way to avoid duplicating further work.
(As of right now I see no other option but to continue working
on my branches.. Hopefully you can fill me in on some
of the above information so I can help you out instead!)

Regards,
Andreas Henriksson


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

Bug#722611: mutt: segfaults when sending with SMTP

[Matteo Cypriani]

retitle 722611 libsasl2-2: double free with DIGEST-MD5
reassign 722611 libsasl2-2 2.1.25.dfsg1-14
tag 722611 patch
thanks

On Wed, 11 Jun 2014 10:36:04 -0400, Matteo Cypriani  wrote:
> I hadn't really used it since last time, but I just had mutt crash again
> after sending a mail:
> 
> Envoi du message... 0K/9,6K (0%)
> *** Error in `mutt': double free or corruption (!prev): 0x02868280
> *** zsh: abort  mutt
> 
> Package versions:
>   mutt1.5.23-1
>   libsasl2-2  2.1.26.dfsg1-9

After all it *looks* indeed like it's a bug in libsasl. The bug occurs when
trying to send an email with mutt via SMTP and the DIGEST-MD5 authentication,
because free_rc4() (from plugins/digestmd5.c) is called twice: once when mutt
calls sasl_client_step(), and once when it calls sasl_dispose(). I'm
attaching a file with the most important steps of my gdb session (this time I
rebuilt mutt and libsasl with nostrip to have all the symbols).

I'm also attaching a patch that fixes the problem for me, but please don't
blindly apply it: I really don't know what I'm doing! Maybe the pointers
should be set to NULL elsewhere, or maybe free_rc4() shouldn't be called
twice in the first place, I'm not familiar enough with the code to tell.

Cheers,
  Matteo


gdb_session
Description: Binary data
Subject: Avoids double free in case free_rc4() is called multiple times
Author: Matteo Cypriani 
--- a/plugins/digestmd5.c
+++ b/plugins/digestmd5.c
@@ -1226,8 +1226,15 @@
 {
 /* free rc4 context structures */
 
-if(text->cipher_enc_context) text->utils->free(text->cipher_enc_context);
-if(text->cipher_dec_context) text->utils->free(text->cipher_dec_context);
+if(text->cipher_enc_context) {
+text->utils->free(text->cipher_enc_context);
+text->cipher_enc_context = NULL;
+}
+
+if(text->cipher_dec_context) {
+text->utils->free(text->cipher_dec_context);
+text->cipher_dec_context = NULL;
+}
 }
 
 static int init_rc4(context_t *text, 


pgpz41bM2VvjE.pgp
Description: PGP signature

Bug#700760: libc6: GDB 7.5 would benefit from a SystemTap SDT probe

[Aurelien Jarno]

tag 700760 - moreinfo
close 700760 2.19-0experimental0
thanks

On Mon, Jun 09, 2014 at 06:02:06PM +0200, Aurelien Jarno wrote:
> reopen 700760
> tag 700760 + moreinfo
> clone 750996
> reassign -1 750996 systemtap-sdt-dev
> retitle 750996 systemtap-sdt-dev: breaks eglibc build on alpha
> block 700760 by 750996
> thanks
> 
> On Mon, Jun 09, 2014 at 10:13:05PM +1200, Michael Cree wrote:
> > Source: eglibc
> > Version: 2.19-1
> > Severity: important
> > User: debian-al...@lists.debian.org
> > Usertags: alpha
> > Justification: fails to build from source but built in the past
> > X-Debbugs-CC: debian-al...@lists.debian.org
> > 
> > eglibc FTBFS on alpha for two reasons, firstly, due to the inclusion of
> > systemtap headers and, secondly, because of what might be broken
> > FUTEX_CLOCK_REALTIME support in the kernel.
> > 
> > The systemtap header inclusion introduces an invalid unsplit symbol
> > reference to global_max_fast in inline asm leading to a failure to compile
> > malloc/malloc.c, which is the reason for the compiler ICE seen in the build
> > log at:
> > 
> > http://buildd.debian-ports.org/status/fetch.php?pkg=eglibc&arch=alpha&ver=2.19-1&stamp=1401942698
> > 
> > The compiler ICE is now fixed in gcc upstream (PR target/61336) to a
> > graceful error exit which won't help us in getting eglibc built on alpha.
> > 
> > So my question: can we have the systemtap-sdt-dev build-dep removed from
> > eglibc for a build on Alpha?  (And what are the implications of that?
> > Presumably nothing since even a number of official arches are not supported
> > by systemtap?)
> 
> systemtap-sdt-dev was supposed to be something transparent for the
> glibc, but in practice it causes build failure on at least on alpha (see
> above). Looking at the BTS, I see it also causes problems with GCC, so I
> am a bit concerned on other side effects we might haven't seen yet.
> 
> systemtap-sdt-dev was supposed to be arch:all to be able to be used on
> all architecture, but in practice it doesn't seems to be the case. Could
> you please to switch it back to a specific architecture list where it
> actually works? In the meantime we are going to revert SDT support in
> eglibc, thus reopening the bug.

As the problem has been solved at the GCC level, we are not going to
revert the SDT changes in the next glibc upload. I am therefore closing
bug#700760 again.


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


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

Bug#474608: [Logcheck-devel] Bug#474608: logcheck: SMTP vs sendmail

[Juliusz Chroboczek]

> Would it be possible to have loccheck using SMTP to send email reports
> instead of local /usr/bin/sendmail.

That would break systems running dma instead of a full-fledged SMTP daemon.

-- Juliusz


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

Bug#715038: add mips64(el) mipsn32(el) support to eglibc

[Aurelien Jarno]

Hi,

On Tue, Jun 10, 2014 at 08:17:53PM +0800, Sphinx Jiang wrote:
> Hi,
> 
> In this patch, o32 libraries are moved from /lib to /libo32.

I have applied this patch with some small changes fixing some issues and
homogenizing all mips*.mk files, most importantly:
- really install the o32 library in /libo32 for mipsn32el.mk
- changed a end into endef
- replace MIPS64 by MIPS in the o32 package description, as it doesn't
  need a 64-bit CPU to run the o32 libc (contrary to the n32 and n64
  ones).

Don't hesitate to look at the SVN to check everything is ok.

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


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

Bug#751283: Segmentation fault on startup

[Serghei Mihai]

Package: claws-mail
Version: 3.10.1-1
Followup-For: Bug #751283

Hi,

Just to complete your report with the traceback I get when launching claws-
mail:

main.c:1380:Claws Mail crashed, checking for new messages in local folders
folderview.c:1078:called inc_lock (lock count 1)
folderview.c:1151:called inc_unlock (lock count 0)
folder.c:2569:Total cache memory usage: 0
hooks.c:71:registed new hook for 'avatar_image_render' as id 1
prefs.c:297:Found [Plugins_GTK2]
plugin.c:451:trying to load `/usr/lib/x86_64-linux-gnu/claws-
mail/plugins/pgpcore.so'
plugin.c:370:plugin licence check passed: GPL3+ found
sgpgme.c:616:setting gpgme CTYPE locale
sgpgme.c:623:setting gpgme CTYPE locale to: en_GB.utf8
sgpgme.c:630:setting gpgme locale to UTF8: en_GB.UTF-8
sgpgme.c:633:done
sgpgme.c:641:setting gpgme MESSAGES locale
sgpgme.c:648:setting gpgme MESSAGES locale to: en_GB.utf8
sgpgme.c:654:setting gpgme locale to UTF8: en_GB.UTF-8
sgpgme.c:658:done
sgpgme.c:667:GpgME Protocol: OpenPGP
Version: 2.0.23 (req 1.4.0)
Executable: /usr/bin/gpg2
sgpgme.c:667:GpgME Protocol: CMS
Version: ??? (req 1.9.6)
Executable: /usr/bin/gpgsm
sgpgme.c:667:GpgME Protocol: GPGCONF
Version: 2.0.23 (req 2.0.4)
Executable: /usr/bin/gpgconf
sgpgme.c:667:GpgME Protocol: Assuan
Version: 1.0 (req 1.0)
Executable: /tmp/gpg-5Cyf58/S.gpg-agent
prefs_gtk.c:86:Reading configuration...
prefs_gpg.c:542:set GPG_AGENT_INFO=/tmp/gpg-5Cyf58/S.gpg-agent:1106:1
prefs_gpg.c:450:Saving GPG config
prefs.c:310:Found [GPG]
hooks.c:71:registed new hook for
'address_completion_build_address_list_hooklist' as id 1
autocompletion.c:128:PGP address autocompletion hook registered
plugin.c:525:Plugin PGP/Core (from file /usr/lib/x86_64-linux-gnu/claws-
mail/plugins/pgpcore.so) loaded
plugin.c:526:TIMING plugin_load /usr/lib/x86_64-linux-gnu/claws-
mail/plugins/pgpcore.so: 0s031ms
plugin.c:273:adding /usr/lib/x86_64-linux-gnu/claws-mail/plugins/pgpmime.so to
/usr/lib/x86_64-linux-gnu/claws-mail/plugins/pgpcore.so rdeps
plugin.c:451:trying to load `/usr/lib/x86_64-linux-gnu/claws-
mail/plugins/pgpmime.so'
plugin.c:370:plugin licence check passed: GPL3+ found
plugin.c:525:Plugin PGP/MIME (from file /usr/lib/x86_64-linux-gnu/claws-
mail/plugins/pgpmime.so) loaded
plugin.c:526:TIMING plugin_load /usr/lib/x86_64-linux-gnu/claws-
mail/plugins/pgpmime.so: 0s000ms
plugin.c:451:trying to load `/usr/lib/x86_64-linux-gnu/claws-
mail/plugins/fancy.so'
plugin.c:370:plugin licence check passed: GPL3 found
prefs_gtk.c:86:Reading configuration...
plugin.c:525:Plugin Fancy HTML Viewer (from file /usr/lib/x86_64-linux-gnu
/claws-mail/plugins/fancy.so) loaded
plugin.c:526:TIMING plugin_load /usr/lib/x86_64-linux-gnu/claws-
mail/plugins/fancy.so: 0s038ms
plugin.c:451:trying to load `/usr/lib/x86_64-linux-gnu/claws-
mail/plugins/notification.so'
plugin.c:370:plugin licence check passed: GPL3+ found
hooks.c:71:registed new hook for 'folder_item_update' as id 4
hooks.c:71:registed new hook for 'folder_update' as id 4
hooks.c:71:registed new hook for 'msginfo_update' as id 3
hooks.c:71:registed new hook for 'offline_switch' as id 1
hooks.c:71:registed new hook for 'mainwindow_close' as id 1
hooks.c:71:registed new hook for 'mainwindow_iconified' as id 1
hooks.c:71:registed new hook for 'account_list_changed' as id 1
hooks.c:71:registed new hook for 'theme_changed' as id 1
prefs_gtk.c:86:Reading configuration...
notification_core.c:332:Notification Plugin: Hash table created
mainwindow.c:2857:main window position: 0, 22
notification_hotkeys.c:105:Notification plugin: Updating keybindings..
notification_hotkeys.c:115:Notification plugin: Unbinding all keybindings..
notification_hotkeys.c:105:Notification plugin: Updating keybindings..
notification_hotkeys.c:115:Notification plugin: Unbinding all keybindings..
notification_plugin.c:357:Notification plugin loaded
plugin.c:525:Plugin Notification (from file /usr/lib/x86_64-linux-gnu/claws-
mail/plugins/notification.so) loaded
plugin.c:526:TIMING plugin_load /usr/lib/x86_64-linux-gnu/claws-
mail/plugins/notification.so: 0s014ms
prefs_gtk.c:1074:destroying cache
main.c:1557:TIMING main startup: 0s277ms
main.c:2912:Failed to get state info from NetworkManager: The name
org.freedesktop.NetworkManager was not provided by any .service files
alertpanel.c:254:Creating alert panel dialog...
alertpanel.c:213:called inc_lock (lock count 1)
alertpanel.c:223:called inc_unlock (lock count 0)
alertpanel.c:107:return value = 1
folderview.c:1078:called inc_lock (lock count 1)
imap.c:4721:getting session...
main.c:2912:Failed to get state info from NetworkManager: The name
org.freedesktop.NetworkManager was not provided by any .service files
** Message: Account 'entrouvert': Connecting to IMAP4 server:
imap.***.:993...

imap-thread.c:393:found imap 0x1427750
Segmentation fault



-- 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-amd

Bug#751337: babeltrace: FTBFS on kfreebsd (error: 'HOST_NAME_MAX' undeclared)

[Julien Cristau]

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

Your package fails to build on kfreebsd:

> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2 -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-kfreebsd-gnu/glib-2.0/include   
> -Wall -Wformat -include config.h -I../../include -I../../tests/utils -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -c -o test_ctf_writer.o test_ctf_writer.c
> test_ctf_writer.c: In function 'main':
> test_ctf_writer.c:718:16: error: 'HOST_NAME_MAX' undeclared (first use in 
> this function)
>   char hostname[HOST_NAME_MAX];
> ^
> test_ctf_writer.c:718:16: note: each undeclared identifier is reported only 
> once for each function it appears in
> test_ctf_writer.c:718:7: warning: unused variable 'hostname' 
> [-Wunused-variable]
>   char hostname[HOST_NAME_MAX];
>^
> make[5]: *** [test_ctf_writer.o] Error 1

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=babeltrace&arch=kfreebsd-amd64&ver=1.2.1-2&stamp=1395842529

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#741878: #741878

[Andrew Wilkinson]

Hi,

I'm seeing the same issue on Buffy The Vampire Slayer S1D3 and S2D3. I've
modified the code to print out the offending data structures, but I'm not
sure what to do about them.

I added...

--- a/dvdvideo/volume.py
+++ b/dvdvideo/volume.py
@@ -156,6 +156,9 @@ class FileSetUdf:

 i = input[0]
 j = input[1]
+print(i, i.entry)
+print(j, j.entry)
+
 ad_i = i.entry.ad[0]
 ad_j = j.entry.ad[0]


and got...

 ; ad: (
 ; ad: (
 ; ad: (
 ; ad: (
 ; ad: (
 ; ad: ()>

Hope that helps,
Andrew

Bug#751336: babeltrace: FTBFS on armel (test failure)

[Julien Cristau]

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

See the build log at
https://buildd.debian.org/status/fetch.php?pkg=babeltrace&arch=armel&ver=1.2.1-2&stamp=1395846913

There's also a build failure on sparc which may or may not be related:
https://buildd.debian.org/status/fetch.php?pkg=babeltrace&arch=sparc&ver=1.2.1-2&stamp=1395859546

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#751335: gnome-main-menu: unbuildable on !linux archs

[Pino Toscano]

Source: gnome-main-menu
Version: 1.8.0-1
Severity: important
Tags: patch

Hi,

currently gnome-main-menu cannot be built on non-Linux architectures,
because of few Linux-specific build dependencies.

Since the features they enable are optional, those build dependencies
can be safely restricted as linux-only. Patch attached for it.

Thanks,
-- 
Pino
--- a/debian/control
+++ b/debian/control
@@ -19,10 +19,10 @@ Build-Depends: debhelper (>= 9),
libxml2-dev,
libcairo2-dev,
libx11-dev,
-   network-manager-dev,
-   libnm-glib-dev,
-   libnm-util-dev,
-   libiw-dev,
+   network-manager-dev [linux-any],
+   libnm-glib-dev [linux-any],
+   libnm-util-dev [linux-any],
+   libiw-dev [linux-any],
libmate-slab-dev,
mate-common,
libdconf-dev,

Bug#482528: closed by Jelmer Vernooij (Bug#482528: fixed in heimdal 1.6~rc2+dfsg-7)

[Jelmer Vernooij]

On Wed, Jun 11, 2014 at 09:50:51PM +0200, Bastian Blank wrote:
> Control: reopen -1
> Control: severity -1 serious
> 
> On Wed, Jun 11, 2014 at 03:51:25AM +, Debian Bug Tracking System wrote:
> >* Use alternatives for kpasswd, ksu, kdestroy, kswitch, kadmin and 
> > ktutil.
> >  + Allows installation together with krb5-user. Closes: #482528
> 
> kadmin is _not_ compatible, neither in the command-line interface nor in
> the protocol.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=213316 for the
discussion leading up to this change.

These binaries do provide similar functionality, even if their
interface isn't compatible. What is the justification for severity
serious?

Cheers,

Jelmer

-- 
Jelmer Vernooij 
Debian Developer   http://samba.org/~jelmer/


signature.asc
Description: Digital signature

Bug#751280: arbtt: improve time categorization directives

[Felipe Sateler]

Control: forwarded -1 
https://bitbucket.org/nomeata/arbtt/issue/14/improve-time-categorization-directives

On Wed, Jun 11, 2014 at 3:05 PM, Joachim Breitner  wrote:
> Control: forwarded -1 
> https://bitbucket.org/nomeata/arbtt/issue/13/include-command-to-split-rotate-logs

Copy paste error? ;)

>
> Thanks again, also forwarded upstream, where I’ll comment on these
> issues.

OK, will answer there.

-- 

Saludos,
Felipe Sateler


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

Bug#741596: mkgmap crashes: java.lang.NoClassDefFoundError: it/unimi/dsi/fastutil/longs/Long2ObjectOpenHashMap

[Manfred Stock]

Package: mkgmap
Version: 0.0.0+svn2981-1
Followup-For: Bug #741596

Hi,

I experienced the same problem when trying the mkgmap package from sid, and
took a closer look at it. On one hand, I noticed that
it.unimi.dsi.fastutil.longs.Long2ObjectOpenHashMap is contained in
libfastutil-java, however, that is not marked as a dependency in the mkgmap
package. Installing libfastutil-java did not immediately help though, I also
had to apply the following change to the mkgmap script:

-exec $JAVACMD -jar /usr/share/mkgmap/mkgmap.jar "$@"
+exec $JAVACMD -cp 
/usr/share/java/fastutil.jar:/usr/share/mkgmap/mkgmap.jar 
uk.me.parabola.mkgmap.main.Main "$@"

After that, the mkgmap command from the bug report ran successfully. I also
noticed that META-INF/MANIFEST.MF in the mkgmap.jar file declares a Class-Path
which is fairly long and most likely contains (nearly?) exclusively files that
cannot be found at the given location. For most files, this probably is no
problem, but I suspect that when using a pbf export of OSM data, the same
problem will occur for classes provided by libprotobuf-java and libosmpbf-java.

So it seems that ${java:Depends} in the control file does not add all necessary
dependencies (I've got no idea if it should/could, but I guess it adds ant,
which is probably *not* needed at runtime...), and that META-INF/MANIFEST.MF or
the mkgmap script should be changed such that they point to the required .jar
files.

Best regards
Manfred

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

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

Versions of packages mkgmap depends on:
ii  ant1.9.4-1
ii  default-jre2:1.7-52
ii  openjdk-7-jre  7u55-2.4.7-2

mkgmap recommends no packages.

Versions of packages mkgmap suggests:
pn  josm
pn  qlandkarte  

-- 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#747341: Info received (Confirmation)

[josh]

On Wed, Jun 11, 2014 at 09:51:52AM -0700, Ben Wong wrote:
> Okay, I ran bash under gdb and got a backtrace which perhaps points to
> readline. While it's hard to lay blame with a malloc error, this fits
> with my experience as bash would often crash immediately after exiting
> a command and returning to the prompt.

While I can't easily distinguish the two cases (since my terminal tabs close
when the shell does, and I don't usually run the shell under gdb or under
another shell), the crash always occurs for me when I press enter on a newly
typed command line.  The memory corruption may linger from some previous
command, but the crash doesn't happen until I type in a new command and hit
enter.

> Josh: Do you have a specialized ~/.inputrc? I do and I wonder if that
> could be what's triggering the bug for us. A lesser possibility could
> be a customized prompt. Have you changed your PS1 from Debian's
> default?
> 
> My PS1='\h:\W\$ '
> 
> My .inputrc follows
[...]

Yes, I have a custom PS1 and .inputrc.  You can git clone all of my
relevant configuration files from git://joshtriplett.org/git/home .

Here's my PS1:

\[\e]0;\w\a\]$(e="$?";[ "$e" -ne 0 ] && echo -n "\[\e[01;31m\]($e) 
")${debian_chroot:+\[\e[01;37m\]($debian_chroot) 
}${prompt_remote:+\[\e[01;32m\]\u@\h\[\e[00m\]:}\[\e[01;34m\]\w\[\e[00m\]\$ 
\[$(__vte_osc7)\]

Here's my .inputrc:

$include /etc/inputrc

set editing-mode emacs

set bell-style none

"\e[1~": beginning-of-line
"\e[4~": end-of-line
"\e[1;5C": forward-word
"\e[1;5D": backward-word
"\e[5C": forward-word
"\e[5D": backward-word
"\e\e[C": forward-word
"\e\e[D": backward-word

$if term=rxvt
"\e[8~": end-of-line
"\eOc": forward-word
"\eOd": backward-word
$endif


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

Bug#751299: homebank: Add "account adjustment" feature

[Riccardo Boninsegna]

Package: homebank
Version: 4.5.5-2
Severity: wishlist
Tags: upstream

This software could benefit from a feature called "account adjustment" in some
of its competitors e.g. Microsoft Money 2003: as HomeBank is right now you can
only set a starting balance and transactions are incrementally applied over
that.

In certain scenarios (like keeping track of your paper money), the ability to
record the value of an account at any arbitrary moment would greatly enhance
the usability of this program.



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

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

Versions of packages homebank depends on:
ii  homebank-data4.5.5-2
ii  libatk1.0-0  2.12.0-1
ii  libc62.18-7
ii  libcairo21.12.16-2
ii  libfontconfig1   2.11.0-5
ii  libfreetype6 2.5.2-1
ii  libgdk-pixbuf2.0-0   2.30.7-1
ii  libglib2.0-0 2.40.0-3
ii  libgtk2.0-0  2.24.23-1
ii  libofx4  1:0.9.4-2.1
ii  libpango-1.0-0   1.36.3-1
ii  libpangocairo-1.0-0  1.36.3-1
ii  libpangoft2-1.0-01.36.3-1

Versions of packages homebank recommends:
ii  librsvg2-common  2.40.2-1

homebank suggests no packages.

-- 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#571120: RFS: pisa/python-pisa

[wjdoekes]

There has been some
upstream changes, that should be reflected in the package.
Mainly the name "pisa" is not used anymore, it seems, only
"xhtml2pdf". The latest version is "0.0.4" at github [1]. But
there was a release "0.0.6" at PyPI [2]. Is it based on the
github code? Anyway, we should probably use the new version
numbers with a new epoch and providing pisa. What do you think?


I did a quick test substituting:

  from ho.pisa import CreatePDF
  (python-pisa 3.0.32-1build1)

with this:

  from xhtml2pdf.pisa import CreatePDF
  (chrisglass gitrev 5987c9c9b3b04f55abb74fb2c4a82f023dc4268a
   Fri Jun 6 17:12:13 2014 +0800)

in a tiny example [1]. And the first thing I noticed is that
the xhtml2pdf version does not handle  values like
expected [2].

I'd say patching sx.pisa3 with a tiny patch [3] is the quickest
fix to this bug. And that you cannot reasonably expect xhtml2pdf
to replace pisa without breaking things for a lot of people.


[1] Example code, comparing xhtml2pdf to ho/sx-pisa:

  from xhtml2pdf.pisa import CreatePDF as CreatePDF_xhtml2pdf, VERSION
  from ho.pisa import CreatePDF as CreatePDF_pisa, VERSION as VERSION2
  from io import BytesIO as S
  s = S('''
  
  
  
  th, td { border:1pt solid black; border-collapse:collapse; }
  th { background: #ccc; }
  
  
  
  75%25%
  valuevalue
  
  
  
  ''')
  s.seek(0)
  with open('xhtml2pdf.pdf', 'w') as d:
  print 'xhtml2pdf', VERSION
  CreatePDF_xhtml2pdf(src=s, dest=d)
  s.seek(0)
  with open('pisa.pdf', 'w') as d:
  print 'pisa', VERSION2
  CreatePDF_pisa(src=s, dest=d)


[2] The above script outputs this:

  xhtml2pdf 3.0.33
  pisa 3.0.32

And it writes two files:

  - xhtml2pdf.pdf
  - pisa.pdf

If you compare them, you see that the pisa.pdf renders the table like
expected with the first column taking up ~3/4 of the width. The
xhtml2pdf version makes the first column take up *less* than half
the width.


[3] Suggested fix: an improved version of [4]

  --- sx/pisa3/pisa_util.py.orig2014-06-11 16:11:15.0 +0200
  +++ sx/pisa3/pisa_util.py 2014-06-11 20:57:19.557501000 +0200
  @@ -51,10 +51,11 @@ import shutil

   rgb_re = re.compile("^.*?rgb[(]([0-9]+).*?([0-9]+).*?([0-9]+)[)].*?[ 
]*$")


  -if not(reportlab.Version[0] == "2" and reportlab.Version[2] >= "1"):
  +_reportlab_version = tuple(map(int, reportlab.Version.split('.')))
  +if _reportlab_version < (2, 1):
   raise ImportError("Reportlab Version 2.1+ is needed!")

  -REPORTLAB22 = (reportlab.Version[0] == "2" and reportlab.Version[2] 
>= "2")

  +REPORTLAB22 = _reportlab_version >= (2, 2)
   # print "***", reportlab.Version, REPORTLAB22, reportlab.__file__

   import logging


[4] http://anonscm.debian.org/viewvc/python-modules/packages/pisa/\
  trunk/debian/patches/0002-Fix-reportlab-version-detection-for-\
  versions-greater.patch?view=markup


Cheers,
Walter Doekes
OSSO B.V.


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

Bug#751298: localepurge: reinstall command does not work: flag --fix-mising is not correct

[chambertux]

Package: localepurge
Version: 0.6.3+deb7u1

To reinstall all the packages which localepurge has been taking care of 
before, you can use the following command:


apt-get -u --reinstall --fix-mising install $(dpkg -S LC_MESSAGES | cut 
-d: -f1 | tr ', ' '\n' | sort -u)


I have --fix-mising and the correct way is --fix-missing.


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

Bug#751297: procps: sysinfo.c is_disk does not guard against /sys being unavailable

[Michael Tautschnig]

Package: procps
Version: 1:3.3.9-5
Usertags: goto-cc

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

[...]
=== vmstat tests ===

Schedule of variations:
unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for 
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./vmstat.test/vmstat.exp ...
FAIL: vmstat partition (using sda1)


So what is going on here:

~/procps-3.3.9/testsuite# ../vmstat -p sda1
Segmentation fault

~/procps-3.3.9/testsuite# LD_LIBRARY_PATH=../proc/.libs/ gdb --args 
../.libs/vmstat -p sda1
[...]
(gdb) r
Starting program: 
/srv/jenkins-slave/workspace/sid-goto-cc-procps/procps-3.3.9/.libs/vmstat -p 
sda1

Program received signal SIGSEGV, Segmentation fault.
0x777bec8a in getdiskstat (disks=0x7fffe6b8, 
partitions=0x7fffe6c0) at sysinfo.c:942
942   (*disks)[cDisk-1].partitions++;
(gdb) bt
#0  0x777bec8a in getdiskstat (disks=0x7fffe6b8, 
partitions=0x7fffe6c0)
at sysinfo.c:942
#1  0x00401823 in diskpartition_format (partition_name=0x7fffeaed 
"sda1") at vmstat.c:405
#2  main (argc=, argv=0x7fffe828) at vmstat.c:860
(gdb) print cDisk
$1 = 
(gdb) print disks
$2 = (struct disk_stat **) 0x7fffe6b8
(gdb) print *disks
$3 = (struct disk_stat *) 0x0


Looking at the code of getdiskstat this must meant that either parsing
/proc/diskstats fails or partitions are otherwise seen before memory for a disk
has been allocated. And indeed this is the case here as the call to is_disk does
not produce an appropriate result in my case, because:

~/procps-3.3.9/testsuite# ls /sys
~/procps-3.3.9/testsuite#


So it would be nice if is_disk failed in some sensible way if /sys/block wasn't
available at all.

Best,
Michael



pgpo41z9C6FkJ.pgp
Description: PGP signature

Bug#482528: closed by Jelmer Vernooij (Bug#482528: fixed in heimdal 1.6~rc2+dfsg-7)

[Bastian Blank]

Control: reopen -1
Control: severity -1 serious

On Wed, Jun 11, 2014 at 03:51:25AM +, Debian Bug Tracking System wrote:
>* Use alternatives for kpasswd, ksu, kdestroy, kswitch, kadmin and ktutil.
>  + Allows installation together with krb5-user. Closes: #482528

kadmin is _not_ compatible, neither in the command-line interface nor in
the protocol.

Bastian

-- 
It is more rational to sacrifice one life than six.
-- Spock, "The Galileo Seven", stardate 2822.3


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