Bug#681263: Not sure

[G. Pablo Vanwoerkom]

Well, I did install compiz manually and since it didn't have "make
uninstall", I had to uninstall manually as well.

However, I think this behavior was my motivation to try to install compiz
manually. Anyways, I removed all mentions of compiz from my system, purged
compiz from synaptic, and installed again.

If there is more info you would need, let me know!
Thanks,-Pablo

Bug#681395: unblock smarty-gettext

[Adam D. Barratt]

On 13.07.2012 11:00, Mike Gabriel wrote:

On Do 12 Jul 2012 22:50:23 CEST "Adam D. Barratt" wrote:

What's this change about?

+  * debian/install, debian/links:
++ Install as /usr/bin/tsmarty2c (without extension) and drop 
the symlink
+  of the same name that used to refer to 
/usr/bin/tsmarty2c.php.


1.0b1-6 had three locations within /debian dir that played around
with  the file tsmarty2c.php (name that upstream gave the file):
debian/install, debian/links and debian/rules. The job done in
debian/links and the command in debian/rules obviously interfered 
with

each other.


Okay, but in that case the changelog is still wrong, as there have been 
absolutely

no changes to debian/install:

--- smarty-gettext-1.0b1/debian/install 2012-05-10 
18:59:25.0 +
+++ smarty-gettext-1.0b1/debian/install 2012-07-08 
13:07:48.0 +

@@ -1,2 +1,2 @@
 block.t.php usr/share/php/smarty3/plugins/
-tsmarty2c.php usr/bin/
+tsmarty2c.php usr/bin/
 No newline at end of file


This file only has lost an EOL (sorry for causing confusion).


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#681290: unblock: spice-gtk/0.12-4

[Liang Guo]

Hi, 
On Thu, Jul 12, 2012 at 05:51:08PM +0100, Adam D. Barratt wrote:
> >The difference between 0.12-3 and 0.12-4 is slight, just
> >copy .version and .tarball-version to build directory.
> >for the build script use the version information in
> >.tarball-version to determine the version it is building.
> 
> Testing currently has 0.12-1, so the changes which are relevant are
> everything after that, not just those in -4.
> 
> Regards,
> 
> Adam
Hi, 

This is the debdiff result of 0.12-1 and 0.12-4, I'll add
my comment start with "//"
liang@guoliangc:~/opt/src/spice$ debdiff spice-gtk_0.12-1.dsc 
spice-gtk_0.12-4.dsc
diff -Nru spice-gtk-0.12/debian/changelog spice-gtk-0.12/debian/changelog
--- spice-gtk-0.12/debian/changelog 2012-05-14 12:53:12.0 +0800
+++ spice-gtk-0.12/debian/changelog 2012-07-09 01:20:26.0 +0800
@@ -1,3 +1,27 @@
+spice-gtk (0.12-4) unstable; urgency=low
+
+  * Correct version problem in *.pc (Closes: #680290)
+
+ -- Liang Guo   Mon, 09 Jul 2012 00:36:14 +0800
+
+spice-gtk (0.12-3) unstable; urgency=low
+
+  * Add patch make-celt-to-be-optional.patch
+  * Disable celt
+
+ -- Liang Guo   Fri, 29 Jun 2012 01:37:37 +0800
+
+spice-gtk (0.12-2) unstable; urgency=low
+
+  * Enable usb redirect (Closes: #677662)
+  * Switch to vala 0.16 (Closes: #675665)
+  * Enable multiarch for libspice-client-glib-2.0-1, 
+libspice-client-gtk-2.0-1, libspice-client-gtk-3.0-1
+  * Build with hardening flags
+  * Use dpkg-statoverride to handle setuid bits
+
+ -- Liang Guo   Fri, 25 May 2012 21:52:45 +0800
+
 spice-gtk (0.12-1) unstable; urgency=low
 
   * New upstream release
//The primary change since 0.12-1 are: 
//1) Enable usb redirect support. Usb redirect is used to
//   redirect usb attached to the spice client to the 
//   spice server(normally a virtual machine). When the 
//   user want to connect his usb device to the virtual 
//   machine, he can just pulg his usb device, then he
//   can see his usb device in the virtual machine. This 
//   option significantly improve the user experience
//2) Disable celt codec support. Celt version 0.5.1 is 
//   the audio codec used by spice, but is not maintained
//   long long ago. To avoid potential security problem,
//   we decide to remove celt 0.5.1 from debian. 
//   libspice-server1 embedded celt before 0.10.1-3~nocelt
//   but libspice-server1 don't ship celt since 
//   0.10.1-3~nocelt, this breaks spice-gtk(<= 0.12-2)
//   which cause spice cannot migerate to testing. 

diff -Nru spice-gtk-0.12/debian/compat spice-gtk-0.12/debian/compat
--- spice-gtk-0.12/debian/compat2012-05-03 09:13:48.0 +0800
+++ spice-gtk-0.12/debian/compat2012-06-09 12:39:51.0 +0800
@@ -1 +1 @@
-8
+9
//Introduce by adding multi-arch support
diff -Nru spice-gtk-0.12/debian/control spice-gtk-0.12/debian/control
--- spice-gtk-0.12/debian/control   2012-05-03 09:13:48.0 +0800
+++ spice-gtk-0.12/debian/control   2012-06-23 09:54:33.0 +0800
@@ -1,9 +1,9 @@
 Source: spice-gtk
 Section: misc
 Priority: optional
-Maintainer: Liang Guo 
+Maintainer: Liang Guo 
 Build-Depends: 
- debhelper (>= 8.0.0), 
+ debhelper (>= 9), 
//Introduce by adding multi-arch support
  libspice-protocol-dev (>= 0.10.1), 
  libspice-server-dev,
  libpixman-1-dev (>= 0.17.7),
@@ -14,8 +14,8 @@
  libcairo2-dev (>= 1.2.0),
  libpulse-dev,
  libusb-1.0-0-dev,
- valac-0.14,
- libvala-0.14-dev,
+ valac-0.16,
+ libvala-0.16-dev,
//Switch to vala 0.16, this closes bug 675665
  python-all,
  python-gtk2-dev (>= 2.0.0),
  python-pyparsing,
@@ -26,6 +26,11 @@
  libgirepository1.0-dev,
  gir1.2-gtk-2.0,
  libtext-csv-perl,
+ libusbredirhost-dev,
+ libacl1-dev,
+ libpolkit-agent-1-dev,
+ libpolkit-gobject-1-dev,
//Introduced by adding usb redirect support, 
//usb redirect use acl and policy kit to control
//the access to usb devices. 
+ dpkg-dev (>= 1.16.1~),
 Standards-Version: 3.9.3
 X-Python-Version: >= 2.5
 Homepage: http://www.spice-space.org/
@@ -46,6 +51,8 @@
 Package: libspice-client-glib-2.0-1
 Section: libs
 Architecture: i386 amd64
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
//Introduce by adding multi-arch support
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Replaces: libspice-client-glib-2.0-4
 Conflicts: libspice-client-glib-2.0-4
@@ -58,6 +65,7 @@
 Package: gir1.2-spice-client-glib-2.0
 Section: introspection
 Architecture: i386 amd64
+Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends}, ${gir:Depends}
 Description: GObject for communicating with Spice servers 
(GObject-Introspection)
  libspice-glib4 provides glib objects for spice protocol
@@ -84,6 +92,8 @@
 Package: libspice-client-gtk-2.0-1
 Section: libs
 Architecture: i386 amd64
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
//Introduce by adding multi-arch support
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: GTK2 widget for SPICE clients (runtime library)
  libspice-gtk2 provides gtk2 widget to show spice display 
@@ -118,6 +128,8 @@
 P

Bug#679536: wine-bin: fails to install, trying to overwrite other packages files

[Michael Gilbert]

severity 679536 important
thanks

Hi, I'm setting this to important since it only affects experimental,
which doesn't actually get released.

Best wishes,
Mike



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

Bug#681496: unblock: gunicorn/0.14.5-1

[Chris Lamb]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock gunicorn/0.14.5. It fixes a grave security bug (#681471)
as well as a number of smaller issues.

It's been in unstable for 10 or 11 days now and I've been using it
production for that time without issue.

Many thanks.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org
   `-


signature.asc
Description: PGP signature

Bug#681455: openbox: Does not exit on Exit in pop-up menu.

[Nico Golde]

Hi,
* Sthu  [2012-07-13 12:31]:
> When I do press Exit on pop-up menu (the one I get w/ right-click on a 
> desktop),
> openbox does not exit. I have to click logout in its main menu - then from 
> KDM logout
> menu I logout.
> 
> Please fix it.

What do you mean? There is no logout button in openbox' main menu and the exit 
button works just fine.

Cheers
Nico
-- 
Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0
For security reasons, all text in this mail is double-rot13 encrypted.


pgplrKh3LB7hN.pgp
Description: PGP signature

Bug#681394: wget -O-: bogus "write error"

[Noël Köthe]

tags 681394 + experimental confirmed upstream
forwarded 681394 https://savannah.gnu.org/bugs/index.php?36843
thanks

Hello Jakub,

Am Donnerstag, den 12.07.2012, 22:04 +0200 schrieb Jakub Wilk:

> I'm getting bogus "write error"s with -O-:
> 
> $ wget -q -O- http://debian.org/ >/dev/null
> wget: write error: Inappropriate ioctl for device

Yes, I can reproduce the problem with the experimental version of wget.
With the one in wheezy, sid (1.13.4-3) I don't get the error.

I forwarded it to the upstream bug tracking system.

Thx for the report.

-- 
Noël Köthe 
Debian GNU/Linux, www.debian.org


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

Bug#675758: Another correction in this file

[Christian PERRIER]

The translation was not properly using braces around a variable name.

Fixed file attached.


-- 




ca.po
Description: application/gettext


signature.asc
Description: Digital signature

Bug#681495: printer-driver-ptouch: rastertoptch installed in directory that's not in cups' PATH

[Till Kamppeter]

We have fixed this in Ubuntu already. See:

https://launchpad.net/ubuntu/+source/ptouch-driver/+changelog
http://launchpadlibrarian.net/106473938/ptouch-driver_1.3-3_1.3-3ubuntu0.1.diff.gz

Please back-sync this package to Debian.

   Till




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

Bug#681394: [bug #36843] 1.13.4.59-2b1dd: -O - gives error wget: write error: Inappropriate ioctl for device

[NoëlKöthe]

URL:
  

 Summary: 1.13.4.59-2b1dd: -O - gives error wget: write error:
Inappropriate ioctl for device
 Project: GNU Wget
Submitted by: nok
Submitted on: Fr 13 Jul 2012 18:21:22 CEST
Category: Testing
Severity: 3 - Normal
Priority: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
 Originator Name: 
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
 Release: trunk
Operating System: GNU/Linux
 Reproducibility: Every Time
   Fixed Release: None
 Planned Release: None
  Regression: Yes
   Work Required: None
  Patch Included: No

___

Details:

Hello,

with the alpha/beta version 1.13.4.59-2b1dd of the comming wget release the
following error message is always reproducible for me:

$ wget -q -O - http://www.debian.org/ >/dev/null
wget: write error: Inappropriate ioctl for device


With 1.13.4 it is not reproducible.

Regards

Noel




___

Reply to this item at:

  

___
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/




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

Bug#681364: [regression] does not maintain focus when switching tags

[Yaroslav Halchenko]

On Fri, 13 Jul 2012, Julien Danjou wrote:
> This is not the fix. The fix is:
> http://git.naquadah.org/?p=awesome.git;a=commit;h=c084eb5b085287e4fb2661e834197cf8cf233215

Thanks -- this one worked.
any chance to squeeze this one into wheezy? ;)

-- 
Yaroslav O. Halchenko
Postdoctoral Fellow,   Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik



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

Bug#671673: dvipsk-ja: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2)

[Taku YASUI]

Hi,

I create a patch fixing this bug. Please apply attached patch.
Please apply it.

Thanks,

-- 
Taku YASUI 


dvipsk-ja.diff
Description: Binary data

Bug#672030: Attaching the patch so far

[Neil Williams]

The patch tag was added but the patch only exists in git, so I'm
attaching the raw patch to make it easier for others to debug the
segmentation fault which occurs after this patch is applied.

This patch is not sufficient to fix the bug itself.

Also, note that prior to the segmentation fault, the build log contains
70 CRITICAL warnings from GLib, GLib-GObject or BSE.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/

Description: Fix #includes to avoid FTBFS with GCC 4.7.
Author: Alessio Treglia 
Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672030
Forwarded: no
---
 birnet/birnetutils.cc   |1 +
 birnet/tests/threads.cc |1 +
 sfi/sfidl-parser.hh |2 +-
 3 files changed, 3 insertions(+), 1 deletion(-)

--- beast.orig/birnet/birnetutils.cc
+++ beast/birnet/birnetutils.cc
@@ -21,6 +21,7 @@
 #include "birnetmsg.hh"
 #include "birnetcpu.hh"
 #include 
+#include 
 #include 
 #include 
 #include 
--- beast.orig/birnet/tests/threads.cc
+++ beast/birnet/tests/threads.cc
@@ -17,6 +17,7 @@
 //#define TEST_VERBOSE
 #include 
 #include 
+#include 
 
 namespace {
 using namespace Birnet;
--- beast.orig/sfi/sfidl-parser.hh
+++ beast/sfi/sfidl-parser.hh
@@ -31,7 +31,7 @@ private:
 
 public:
   const Value& get(const Key& k) const {
-typename std::map::const_iterator i = find(k);
+typename std::map::const_iterator i = this->find(k);
 if (i != this->end())
   return i->second;
 else


pgpa77DutLHjO.pgp
Description: PGP signature

Bug#634930: gpa: GPA unusable due to "General Assuan error"

[Daniel Leidert]

Am Freitag, den 13.07.2012, 15:30 +0200 schrieb Werner Koch:

> I tried to replicate the problem with the current stable versions of GPA
> 0.9.2 and GPGME (well, my working copy).  I was not able to do that.  I
> don't have a clean squeeze installation right now available thus I can't
> check 0.9.0 easily.
> 
> Lionel, would you mind to run another test with GPA 0.9.2, GPGME 1.3.2,
> and GnuPG 2.0.19 (or 2.1-beta).

NOTE: The following packages are unofficial packaging work. We have an
outdated gpgme in Debian. I've built packages for the latest gpgme
release. However, if you install them, you probably need to downgrade
these packages after you've tested, how gpa behaves!

GPGME 1.3.2 packages built for unstable are here:
http://debian.wgdd.de/debian/incoming/packages/

Regards, Daniel




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

Bug#681495: printer-driver-ptouch: rastertoptch installed in directory that's not in cups' PATH

[Matthias Urlichs]

Package: printer-driver-ptouch
Version: 1.3-3
Severity: grave
Justification: renders package unusable

This package installs:

/usr/lib/i386-linux-gnu/cups/filter/rastertoptch

'strace -f -p $CUPS_PID' reveals that cups only looks in these locations:

6629  stat64("/usr/lib/cups/filter/rastertoptch", 0xbfa001d0)  = -1 ENOENT (No 
such file or directory)
6629  stat64("/usr/bin/rastertoptch", 0xbfa001d0) = -1 ENOENT (No such file or 
directory)
6629  stat64("/usr/sbin/rastertoptch", 0xbfa001d0) = -1 ENOENT (No such file or 
directory)
6629  stat64("/bin/rastertoptch", 0xbfa001d0) = -1 ENOENT (No such file or 
directory)
6629  stat64("/usr/bin/rastertoptch", 0xbfa001d0) = -1 ENOENT (No such file or 
directory)

Needless to say, this means that the driver does not work for anybody.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'unstable'), (600, 'stable'), (550, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-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 printer-driver-ptouch depends on:
ii  ghostscript9.05~dfsg-6
ii  libc6  2.13-33
ii  libcups2   1.5.3-1
ii  libcupsimage2  1.5.3-1
ii  python 2.7.3~rc2-1
ii  xz-utils   5.1.1alpha+20120614-1

printer-driver-ptouch recommends no packages.

printer-driver-ptouch 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#681494: offlineimap: needs option to disable starttls

[Kapil Hari Paranjape]

Package: offlineimap
Version: 6.3.4-1
Severity: wishlist
Tags: patch

Dear Maintainer,

I need to connect to a badly configured server that advertises STARTTLS
but is not properly configured for it :(

So I created an option 'tls' which allows me to disable the use of
STARTTLS for this server.

A patch against the above version of offlineimap is enclosed. It may
also work with minor changes against the more recent version.

Regards,

Kapil.

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


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

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

Versions of packages offlineimap depends on:
ii  python  2.7.3~rc2-1
ii  python-support  1.0.14

offlineimap recommends no packages.

Versions of packages offlineimap suggests:
ii  doc-base 0.10.4
pn  python-kerberos  

-- no debconf information
diff -ur ./imapserver.py /usr/share/pyshared/offlineimap/./imapserver.py
--- ./imapserver.py	2012-07-13 20:22:52.568204625 +0530
+++ /usr/share/pyshared/offlineimap/./imapserver.py	2011-08-11 01:14:58.0 +0530
@@ -46,7 +46,7 @@
 GSS_STATE_WRAP = 1
 def __init__(self, config, reposname,
  username = None, password = None, hostname = None,
- port = None, ssl = 1, tls = 1, maxconnections = 1, tunnel = None,
+ port = None, ssl = 1, maxconnections = 1, tunnel = None,
  reference = '""', sslclientcert = None, sslclientkey = None,
  sslcacertfile = None, idlefolders = []):
 self.ui = getglobalui()
@@ -60,7 +60,6 @@
 self.tunnel = tunnel
 self.port = port
 self.usessl = ssl
-self.usetls = tls
 self.sslclientcert = sslclientcert
 self.sslclientkey = sslclientkey
 self.sslcacertfile = sslcacertfile
@@ -240,7 +239,7 @@
 
 if not self.gssapi:
 if 'STARTTLS' in imapobj.capabilities and not\
-self.usessl and self.usetls:
+self.usessl:
 self.ui.debug('imap',
   'Using STARTTLS connection')
 imapobj.starttls()
@@ -502,7 +501,6 @@
 user = self.repos.getuser()
 port = self.repos.getport()
 ssl = self.repos.getssl()
-tls = self.repos.gettls()
 sslclientcert = self.repos.getsslclientcert()
 sslclientkey = self.repos.getsslclientkey()
 sslcacertfile = self.repos.getsslcacertfile()
@@ -525,7 +523,7 @@
 if not password:
 password = self.repos.getpassword()
 IMAPServer.__init__(self, self.config, self.repos.getname(),
-user, password, host, port, ssl, tls,
+user, password, host, port, ssl,
 self.repos.getmaxconnections(),
 reference = reference,
 idlefolders = idlefolders,
diff -ur ./repository/Gmail.py /usr/share/pyshared/offlineimap/./repository/Gmail.py
--- ./repository/Gmail.py	2012-07-13 20:24:24.516208876 +0530
+++ /usr/share/pyshared/offlineimap/./repository/Gmail.py	2011-08-11 01:14:58.0 +0530
@@ -54,9 +54,6 @@
 def getssl(self):
 return 1
 
-def gettls(self):
-return 1
-
 def getpreauthtunnel(self):
 return None
 
diff -ur ./repository/IMAP.py /usr/share/pyshared/offlineimap/./repository/IMAP.py
--- ./repository/IMAP.py	2012-07-13 20:09:32.384167653 +0530
+++ /usr/share/pyshared/offlineimap/./repository/IMAP.py	2011-08-11 01:14:58.0 +0530
@@ -162,9 +162,6 @@
 def getssl(self):
 return self.getconfboolean('ssl', 0)
 
-def gettls(self):
-return self.getconfboolean('tls', 0)
-
 def getsslclientcert(self):
 return self.getconf('sslclientcert', None)
 

Bug#681493: pet.debian.net pseudopackage

[Daniel Kahn Gillmor]

Package: bugs.debian.org
Priority: wishlist

We've just moved pet.debian.net on alioth (wagner.debian.org), and are
trying to get more effective collaborative development going on it.
We'd like a pseudopackage named pet.debian.net in the debian BTS.

Description:

pet.debian.net is a web installation of the Package Entropy Tracker
(PET).  PET is a collection of scripts that gather information about
your (or your group's) packages. It allows you to see in a bird's eye
view the health of hundreds of packages, instantly realizing where work
is needed.

The maintainer of the pseudopackage should be set to:

 PET developers 

please reassign #681401 to the pseudopackage (it was mistakenly initially set
to pet.debian.org, which will not exist -- PET will remain at
pet.debian.net).

Thanks for maintaining the BTS!  Please let us know if you need more
information.

Regards,

   --dkg


pgpBSSqIeB6JK.pgp
Description: PGP signature

Bug#571980: /boot/vmlinuz-2.6.33-2-amd64: impi oops on intel motherboard

[Ian Crowther]

On 12/07/12 21:21, Jonathan Nieder wrote:

Ian Crowther wrote:

   

I'm not sure what 2.6.32.y means. I've installed 2.6.32-5-686, which
seems to be recent.
 

Am I correct in assuming you mean version 2.6.32-45?  You can check
with

dpkg-query -W linux-image-$(uname -r)

to see the version number of the installed kernel, or

cat /proc/version

to see the version number of the running one in parentheses.

2.6.32-45 is close to 2.6.32.59 from kernel.org.

   

 That has the same problem (errors after loading
ipmi modules), though.
 

Thanks for checking.
   
Sorry, yes, 2.6.32-45 retains the problem ('modprobe ipmi_si' generates 
a bunch of messages and results in an unusable system).


3.2.0-3-686-pae (debian 3.2.21-3) works for at least an hour with all 
the ipmi modules loaded.


Thanks,

Ian



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

Bug#680037:

[shawn]

https://buildd.debian.org/status/logs.php?pkg=kyotocabinet&arch=sparc

its now failed twice on UltraSPARC III and passed once on Sun Fire T2000

It didn't make it to the tests in 1.2.76-1




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

Bug#681290: unblock: spice-gtk/0.12-4

[Michael Tokarev]

On 12.07.2012 20:51, Adam D. Barratt wrote:
> On 12.07.2012 07:47, Liang Guo wrote:
>> Please unblock spice-gtk.
>>
>> I upload 0.12-3 to unstable at 29th Jun, and
>> find a bug[1] which forbit other package to
>> compile. Then I uploaded 0.12-4 at 9th July,
>> and this cause 0.12-3 cannot automatically
>> migrate to testing
>>
>> The difference between 0.12-3 and 0.12-4 is slight, just
>> copy .version and .tarball-version to build directory.
>> for the build script use the version information in
>> .tarball-version to determine the version it is building.
> 
> Testing currently has 0.12-1, so the changes which are relevant are 
> everything after that, not just those in -4.

The original unblock request included SEVERAL diffstats,
one, the smallest, is between -3 and -4, but there are
also diffstats between other revisions too, starting
with -1 currently in wheezy.

Note that version of spice-gtk which is currently in
testing can not be shipped in wheezy, due to long
story with the celt audio codec.  We should either
let the -4 (celt-less) version go to wheezy, or we
should remove spice and spice-gtk (and all related
packages) and modify dependent packages (qemu-kvm)
to stop using spice.

Version of spice currently in unstable (which is
celt-less) can not enter testing even if it is ready
to go, because it breaks spice-gtk currently in
testing, exactly because this: spice-gtk currently
in testing (-1) requires celt from spice, and spice
in unstable does not contain celt anymore.


For what it is worth, I reviewed the changes made
by Liang, both between 3..4 and between 1..4 revisions.
In particular, I reviewed the only big part of these
changes, which is the patch removing celt usage from
spice-gtk.

The patch itself looks sane.  There are a few places
which might be made shorter, but the logic is right.

I verified the resulting binary (spicy) which uses the
spice-gtk libs, it works as expected.  It even works
with celt-enabled spice server (negotiating raw audio
"codec" correctly), so there's no big issues to expect
from this (biggest and most important) patch.

The changes in the debian packaging also look sane.

They reveal a few places in context which may want
some more love, in particular, the package (neither
sid's -4 release nor testing's -1) build process
can't be stopped and resumed, `clean' target and
rebuilt from scratch is needed in case of any error.
But this is exactly the same in wheezy too.

The packaging changes in -2 (the largest) is the
introduction of multiarch for the libraries.  Enabling
multiarch migth be tricky, but apparently this is done
correctly here - the resulting packages _looks_ okay.
Maybe I should fire up puiparts to verify various up/-
downgrades to see more.

The same revision (-2) included bumping versions of
several dependent libraries, I dunno why it is needed,
but these versions are in -testing now.

I'm not sure of the rules for the unblocking, but this
thing definitely looks sane to me, and testing of the
_code_ changes shows good results too.

Thank you for your time!

/mjt



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

Bug#672809: need the latest version for 2012 tax declaration

[Toni Mueller]

Hi Jonathan,

On Fri, Jul 13, 2012 at 10:16:38AM -0500, Jonathan Nieder wrote:
> Toni Mueller wrote:
> > I only discovered today that closing the bug was premature, and the
> > wrong way to go.
> I don't follow.  Does 0.18-1 not fix the bug?

it does. I have probably made a mistake, though, but I wanted to have
this package flow into Wheezy, when it appeared to be stuck in
unstable. That's why I thought that the bug should be open, instead of
closed.

Can you please make it go into Wheezy?


Kind regards,
--Toni++




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

Bug#666744: ITP: fbcmd -- command line interface (CLI) for facebook

[Jing-Cian Lin (Francine Lin)]

* Package name: fbcmd
  Version : 1.1
  Upstream Author : Dave Tompkins 
* URL : http://fbcmd.dtompkins.com/
* License : GPL-3+
  Programming Lang: php
  Description : Command Line Interface (CLI) for Facebook
 fbcmd is a command line interface (CLI) for facebook. It is open source, and
 works in Windows, Mac and Linux. You can update status fast and simply in your
 terminal. No more need to open a browser to do this!
 .
 It has not only fast status updates and posting items to your news feed, but
 also lots of additional commands to be more convenient to use.
 Do you love the command line as same as Facebook? That's fbcmd!

-- 
Regards,
Jing-Cian Lin ( Francine Lin )



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

Bug#681472: tuxonice-userui: how to select fpsplash mode with new unique ui program ?

[Andrey Rahmatullin]

On Fri, Jul 13, 2012 at 02:00:30PM +0200, Frédéric Boiteux wrote:
>   I've updated my TuxOnIce'd featured Debian system with latest 
> tuxonice-userui package, thanks for the update !
>   I saw in NEWS.Debian that scripts should be updated as the new
>   tuxonice-userui program is unique, using option -t or -f for selecting
>   text or fbsplash interfaces. As I previously select the fbsplash
>   interface using the tuxoniceuserui_fbsplash filename (in kernel
>   configuration or hibernate script), how can I now select fbsplash, as
>   neither kernel nor hibernate scripts offer options to userui program ?
I've succesfully uses the fbsplash interface by writing 
"/usr/lib/tuxonice-userui/tuxoniceui -f" to
/sys/power/tuxonice/user_interface/program. I didn't try to set
CONFIG_TOI_USERUI_DEFAULT_PATH but I can try that too. What did you do and
what didn't work?

-- 
WBR, wRAR


signature.asc
Description: Digital signature

Bug#634930: gpa: GPA unusable due to "General Assuan error"

[Werner Koch]

On Fri, 13 Jul 2012 15:30, w...@gnupg.org said:

> Lionel, would you mind to run another test with GPA 0.9.2, GPGME 1.3.2,
> and GnuPG 2.0.19 (or 2.1-beta).

Sorry, Lionel, it was meant to be sent the other Lionel.


-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.




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

Bug#681492: refcard: no license info at mentioned URL

[Holger Wansing]

Package: refcard
Severity: minor

The footer of the refcard reads:

"This document may be used under the terms of the GNU General
Public License version 3 or higher.
Conditions for copying and translations can be found at
http://www.debian.org/doc/manuals/refcard, ... "

But this URL does only contain all the pdfs, no license.


Also, this is probably not the perfect URL to mention there.

As I already proposed on
https://lists.debian.org/debian-doc/2012/04/msg00022.html
we should eventually use 
http://www.debian.org/doc/user-manuals.html#refcard
which looks more user-friendly and also provides a link to 
the svn repo, which has a COPYING file.



Holger

-- 

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 2.5.0
under DEBIAN GNU/LINUX 5.0.0 - L e n n y
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =




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

Bug#681491: libav-tools: long description should mention qt-faststart

[Jonas Smedegaard]

Package: libav-tools
Version: 6:0.8.3-4
Severity: normal

libav-tools lists in its long description the tools it provides.  Good!

...But one of the provided tools is missing: qt-faststart.

Please mention in long description all tools provided, to ease searching
for them - or at least mention qt-faststart as it does not start with
"ff" or "av" hinting at the relationship to this package or the ffmpeg
package.


 - Jonas



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

Bug#680519: lxde: please depend on gdm3

[Bob Bib]

Christian Perrier,
> #tasksel (3.12) UNRELEASED; urgency=low
> #
> #  * Really depending on gdm3 in task-lxde-desktop (Closes: #680519).

to reduce the probability of user complaints, wouldn't it be better to make it 
like this:

Depends: gdm3 | lightdm

(BTW, because of previous versions' dependency on 'xdm', 'gdm3 | 
x-display-manager' isn't a very good option).

Bug#675758: Another encoding problem...

[Christian PERRIER]

Here's a properly encoded file.

-- 




ca.po
Description: application/gettext


signature.asc
Description: Digital signature

Bug#681404: [Pkg-running-devel] Bug#681404: ITP: garmin-plugin -- browser plugin for communication with the Garmin Connect service

[Ralf Treinen]

On Thu, Jul 12, 2012 at 08:33:23PM -0600, Christian PERRIER wrote:
> Quoting Ralf Treinen (trei...@debian.org):

> >  It can be used to transfer GPX files (Geocache Descriptions) to your garmin
> >  device using the official Garmin Javascript API. Its functionality depends 
> > on
> >  the device you use. 
> >   - Edge305/Forerunner305: ReadFitnessData, ReadGpsData, No write support
> >   - Edge705/Oregon/Dakota: ReadFitnessData, ReadGpsData, Write Gpx files
> >   - Edge800: ReadFitnessData, Write Gpx/Tcx Files
> >   - Other devices: Executes external command to write Gpx to device 
> 
> May I suggest to replace "to your garmin device" by "to Garmin
> devices"?
> Rationale:
> - avoids personnalization
> - capitalize Garmin
> 
> Also:
> Other devices: executes an external command to write a GPX file to the
> device
> 
> Probably standardize on "GPX", also

I will do that, thanks for your suggestions !

> > - possibly has to go into contrib since it is made for interaction with a
> >   non-free service.
> 
> There could exist another service using the same protocol, so I think
> it probably can still go to main.

Yes, in fact I talked yesterday to Ansgar Burchardt (FTP assistant) who told 
me not to worry about this and just upload to main. Twitter stuff is also
in main, for instance.

Cheers -Ralf
-- 
Ralf Treinen
Laboratoire Preuves, Programmes et Systèmes
Université Paris Diderot, Paris, France.
http://www.pps.univ-paris-diderot.fr/~treinen/
=> New email address: trei...@pps.univ-paris-diderot.fr <=



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

Bug#675609: Corrected encoding for Danish translation

[Christian PERRIER]

The file sent in this bug report was encoded in ISO-8859-1 while
claiming to be UTF-8.

here's a properly encoded file.

-- 




da.po
Description: application/gettext


signature.asc
Description: Digital signature

Bug#595112: /usr/bin/dpkg-maintscript-helper: Please provide helper for moving a conffile between packages

[Raphael Hertzog]

retitle 595112 dpkg-maintscript-helper: new helper for moving a conffile 
between packages
thanks

On Tue, 31 Aug 2010, Josh Triplett wrote:
> Moving a conffile from one package to another seems to prove even more
> difficult than renaming it or removing it.  Please consider providing
> support for this case in dpkg-maintscript-helper.

What kind of problems are you referring to?

Michael Biebl reported in the thread at
http://lists.debian.org/4f31c323.9090...@debian.org
that the difficulty was to handle the case where the target
package has no guaranty to be installed. In that case, we
might keep the old conffile around when we don't really
want.

In http://lists.debian.org/20120209095814.ga3...@rivendell.home.ouaza.com
I suggested to create a rm_conffile_if_owner helper
function to deal with this case.

Would this fit your needs too?

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Get the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/



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

Bug#681350: reassigning to smbldap-tools

[Salvatore Bonaccorso]

reassign 681350 smbldap-tools
merge 680939 681350
thanks

I'm reassigning this bugreport to smbldap-tools and merging with
681350.

Regards,
Salvatore


signature.asc
Description: Digital signature

Bug#681490: nasm: CPPFLAGS hardening flags missing

[Simon Ruderich]

Package: nasm
Version: 2.10.01-1
Severity: normal
Tags: patch

Dear Maintainer,

The CPPFLAGS hardening flags are missing because they are ignored
by the build system. For more hardening information please have a
look at [1], [2] and [3].

The following patch fixes the issue.

dpkg-buildflags (used by buildflags.mk) automatically takes care
of debug in DEB_BUILD_OPTIONS and passes -O2 by default.
Therefore I removed it in the patch.

diff -Nru nasm-2.10.01/debian/rules nasm-2.10.01/debian/rules
--- nasm-2.10.01/debian/rules   2012-06-14 03:11:20.0 +0200
+++ nasm-2.10.01/debian/rules   2012-07-13 17:22:10.0 +0200
@@ -4,10 +4,8 @@
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
 
-CFLAGS += -O2
-ifneq ($(findstring debug,$(DEB_BUILD_OPTIONS)),)
-CFLAGS += -g
-endif
+# The build system ignores CPPFLAGS, pass them through CFLAGS instead.
+CFLAGS += $(CPPFLAGS)
 
 clean:
dh_testdir

To check if all flags were correctly enabled you can use
`hardening-check` from the hardening-includes package and check
the build log with `blhc` (hardening-check doesn't catch
everything):

$ hardening-check /usr/bin/rdf2bin /usr/bin/rdflib /usr/bin/rdx 
/usr/bin/ldrdf ...
/usr/bin/rdf2bin:
 Position Independent Executable: no, normal executable!
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: no not found!
/usr/bin/rdflib:
 Position Independent Executable: no, normal executable!
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: no not found!
/usr/bin/rdx:
 Position Independent Executable: no, normal executable!
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: no not found!
/usr/bin/ldrdf:
 Position Independent Executable: no, normal executable!
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: no not found!
...

(Position Independent Executable and Immediate binding is not
enabled by default.)

Use find -type f \( -executable -o -name \*.so\* \) -exec
hardening-check {} + on the build result to check all files.

Regards,
Simon

[1]: https://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags
[2]: https://wiki.debian.org/HardeningWalkthrough
[3]: https://wiki.debian.org/Hardening
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


signature.asc
Description: Digital signature

Bug#680939: Bug#681350: libconvert-asn1-perl: "use strict" breaks smbldap-tools

[Salvatore Bonaccorso]

Hi Saulo

btw, what smbldap-tools can do, is to workaround this is to use 'eval'.

so in a example something like:

cut-cut-cut-cut-cut-cut-
#!/usr/bin/perl

use strict 'refs';

my $attrs = "[ 'foo', 'bar', ]";
$attrs = eval "$attrs";

push @{$attrs}, 'foobar';

use Data::Dumper 'Dumper';
warn Dumper [$attrs];
cut-cut-cut-cut-cut-cut-

But again, this is more a hack.

Regards,
Salvatore


signature.asc
Description: Digital signature

Bug#672809: need the latest version for 2012 tax declaration

[Jonathan Nieder]

Hi Toni,

Toni Mueller wrote:

> I only discovered today that closing the bug was premature, and the
> wrong way to go.

I don't follow.  Does 0.18-1 not fix the bug?

Puzzled,
Jonathan



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

Bug#681489: base-files: Add /etc/os-release.d/debian and make it easy to provide supplementary /etc/os-release.d/* files

[Raphaël Hertzog]

Package: base-files
Version: 6.11
Severity: wishlist

/etc/os-release can now provide everything that /etc/dpkg/origins/default
does and thus I would like to deprecate /etc/dpkg/origins/* (I filed
#681474 against libdpkg-perl to track this).

However /etc/dpkg/origins/* has the benefit of keeping the information
of the parent distributions which /etc/os-release alone can't do.

After discussion with the systemd upstream maintainers, we came to the
conclusion that the best approach would be to store those files
in /etc/os-release.d/ and /etc/os-release itself could be a symlink
to the right file in /etc/os-release.d/ (hence /etc/os-release.d/debian)
for Debian.

The upstream documentation of /etc/os-release explicitly allows
/etc/os-release to be a symlink, see
http://www.freedesktop.org/software/systemd/man/os-release.html

Thus I would like base-files:
- to ship /etc/os-release.d/debian
- to ship /etc/os-release as a symlink to the former
- to make it easy to add supplementary files in /etc/os-release.d/
  and to update the symlink (i.e. reuse the VENDORFILE variable that you
  already have) for derivatives

Cheers,

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

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

Versions of packages base-files depends on:
ii  gawk [awk]  1:4.0.1+dfsg-2
ii  mawk [awk]  1.3.3-17

base-files recommends no packages.

base-files 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#680514: Reproduced

[John Goerzen]

Julien,

I reproduced this bug on current wheezy without the troublesome boot 
parameters.


Linux minerva 3.2.0-3-amd64 #1 SMP Thu Jun 28 09:07:26 UTC 2012 x86_64 
GNU/Linux



jgoerzen@minerva:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-amd64 root=/dev/mapper/minerva-root ro 
quiet pcie_aspm=force i915.lvds_downclock=1


Does this meet your requirements?

thanks,

-- John



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

Bug#681488: scheme9: CFLAGS hardening flags missing

[Simon Ruderich]

Package: scheme9
Version: 2012.07.10-1
Severity: normal
Tags: patch

Dear Maintainer,

The CFLAGS hardening flags are missing because they are
ovewrriten in Makefile. For more hardening information please
have a look at [1], [2] and [3].

The attached patch fixes the issue.

To check if all flags were correctly enabled you can use
`hardening-check` from the hardening-includes package and check
the build log with `blhc` (hardening-check doesn't catch
everything):

$ hardening-check /usr/bin/s9
/usr/bin/s9:
 Position Independent Executable: no, normal executable!
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: no not found!

(Position Independent Executable and Immediate binding is not
enabled by default.)

Use find -type f \( -executable -o -name \*.so\* \) -exec
hardening-check {} + on the build result to check all files.

Regards,
Simon

[1]: https://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags
[2]: https://wiki.debian.org/HardeningWalkthrough
[3]: https://wiki.debian.org/Hardening
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
Description: Use CFLAGS from environment (dpkg-buildflags).
 Necessary for hardening flags.
.
 Don't specify -O2 and -g (on by default) so they can be overwritten by
 dpkg-buildflags.
Author: Simon Ruderich 
Last-Update: 2012-07-13

--- scheme9-2012.07.10.orig/Makefile
+++ scheme9-2012.07.10/Makefile
@@ -27,7 +27,7 @@ BUILD_ENV=	env S9FES_LIBRARY_PATH=.:lib:
 
 # Override default compiler and flags
 CC=	gcc
-CFLAGS=	-g -Wall -ansi -pedantic -O2
+CFLAGS+=	-Wall -ansi -pedantic
 
 prefix=/usr/local
 exec_prefix=$(prefix)


signature.asc
Description: Digital signature

Bug#681487: bugs.debian.org: Bug against debian-maintainers not showing up in debian-maintainers page

[Andrea Colangelo]

Package: bugs.debian.org
Severity: normal

I reported a bug[1] to ask adding my GPG key to the DM keyring, as per
instructions on becoming a Debian Maintainer. BTS correctly opened the bug and
assigned it an id (#681445). Despite that, the bug is not listed in the
debian-maintainers pseudo-package page[2], altough several hours passed since
the bug was reported.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681445
[2] http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=debian-maintainers


-- System Information:
Debian Release: wheezy/sid
  APT prefers quantal-security
  APT policy: (500, 'quantal-security'), (500, 'precise-updates'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-26-generic (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



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

Bug#646367: krb5: MITKRB5-SA-2011-006 (multiple denial-of-service issues)

[Sam Hartman]

Honestly, the conditions involved are rare enough I don't think this is
worth fixing for squeeze.  If you want to prepare a fix it's a fairly
easy patch linked from the MIT advisory.  However I'd suggest that we
wait until a single user running squeeze comes forward and confirms they
are running into this issue. At that point I'll be happy to prepare  a
stable patch.



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

Bug#681486: unblock: cweb-latex/1.1.1.debian.1

[Julian Gilbey]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package cweb-latex

It was just reported to me via email that cweb-latex is now included in
the current texlive packages.  So I have uploaded a dummy transitional
package which simply depends upon the appropriate texlive package
instead, to avoid code duplication.  My intention is to request the
removal of this transitional package post-wheezy.

unblock cweb-latex/1.1.1.debian.1

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

Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.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#681485: unblock: rcs-latex/3.1.debian.1

[Julian Gilbey]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package rcs-latex

It was just reported to me via email that rcs-latex is now included in
the current texlive packages.  So I have uploaded a dummy transitional
package which simply depends upon the appropriate texlive package
instead, to avoid code duplication.  My intention is to request the
removal of this transitional package post-wheezy.

unblock rcs-latex/3.1.debian.1

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

Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.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#681484: override: rcs-latex:oldlibs/extra

[Julian Gilbey]

Package: ftp.debian.org
Version: 20120713

This package has just become a transitional package, hence the change
in section/priority.  (I will also ask for its removal post-wheezy.)

   Julian



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

Bug#681483: override: cweb-latex:oldlibs/extra

[Julian Gilbey]

Package: ftp.debian.org
Version: 20120713

This package has just become a transitional package, hence the change
in section/priority.  (I will also ask for its removal post-wheezy.)

(P.S. The automated email is unclear: it says:

Please make sure that the subject of the bug you file follows the
following format:

Subject: override: BINARY1:section/priority, [...], BINARYX:section/priority

but it does not specify whether the section/priority lists should be
the desired or current override sections/priorities.)

   Julian



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

Bug#681482: ecryptfs-utils: Hardening flags missing

[Simon Ruderich]

Package: ecryptfs-utils
Version: 98-2
Severity: normal
Tags: patch

Dear Maintainer,

The hardening flags are missing because they are disabled in
debian/rules. For more hardening information please have a look
at [1], [2] and [3].

Please don't disable all hardening flags just because a single
one doesn't work. See man dpkg-buildflags for ways to disable
them separately (e.g. -format in this case).

The attached patches enable all hardening flags.

- $CPPFLAGS are lost in ./configure because ac_python_devel.m4
  overwrites it, configure-fix-missing-cppflags.patch fixes this
  issue.
- The -Werror=format-security issues is fixed in
  wformat-security.patch.

These patches should be sent to upstream if possible.

To check if all flags were correctly enabled you can use
`hardening-check` from the hardening-includes package and check
the build log with `blhc` (hardening-check doesn't catch
everything):

$ hardening-check 
/usr/lib/python2.7/dist-packages/ecryptfs-utils/_libecryptfs.so 
/usr/lib/x86_64-linux-gnu/libecryptfs.so.0.0.0 /usr/bin/ecryptfs-manager 
/usr/bin/ecryptfs-wrap-passphrase ...
/usr/lib/python2.7/dist-packages/ecryptfs-utils/_libecryptfs.so:
 Position Independent Executable: no, regular shared library (ignored)
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: yes
/usr/lib/x86_64-linux-gnu/libecryptfs.so.0.0.0:
 Position Independent Executable: no, regular shared library (ignored)
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: yes
/usr/bin/ecryptfs-manager:
 Position Independent Executable: yes
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: yes
/usr/bin/ecryptfs-wrap-passphrase:
 Position Independent Executable: yes
 Stack protected: yes
 Fortify Source functions: yes
 Read-only relocations: yes
 Immediate binding: yes
...

(Position Independent Executable and Immediate binding is not
enabled by default.)

Use find -type f \( -executable -o -name \*.so\* \) -exec
hardening-check {} + on the build result to check all files.

Regards,
Simon

[1]: https://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags
[2]: https://wiki.debian.org/HardeningWalkthrough
[3]: https://wiki.debian.org/Hardening
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
Description: Don't overwrite CPPFLAGS in configure.
 Necessary for (hardening) flags from dpkg-buildflags.
Author: Simon Ruderich 
Last-Update: 2012-07-11

--- ecryptfs-utils-98.orig/configure
+++ ecryptfs-utils-98/configure
@@ -14258,6 +14258,8 @@ ac_link='$CC -o conftest$ac_exeext $CFLA
 ac_compiler_gnu=$ac_cv_c_compiler_gnu
 
 # save current global flags
+ac_save_CPPFLAGS="$CPPFLAGS"
+ac_save_LIBS="$LIBS"
 LIBS="$ac_save_LIBS $PYTHON_LDFLAGS"
 CPPFLAGS="$ac_save_CPPFLAGS $PYTHON_CPPFLAGS"
 cat confdefs.h - <<_ACEOF >conftest.$ac_ext
--- ecryptfs-utils-98.orig/m4/ac_python_devel.m4
+++ ecryptfs-utils-98/m4/ac_python_devel.m4
@@ -158,6 +158,8 @@ $ac_distutils_result])
 AC_MSG_CHECKING([consistency of all components of python development environment])
 AC_LANG_PUSH([C])
 # save current global flags
+ac_save_CPPFLAGS="$CPPFLAGS"
+ac_save_LIBS="$LIBS"
 LIBS="$ac_save_LIBS $PYTHON_LDFLAGS"
 CPPFLAGS="$ac_save_CPPFLAGS $PYTHON_CPPFLAGS"
 AC_TRY_LINK([
Description: Fix compiling with -Werror=format-security.
Author: Simon Ruderich 
Last-Update: 2012-07-11

--- ecryptfs-utils-98.orig/src/libecryptfs/module_mgr.c
+++ ecryptfs-utils-98/src/libecryptfs/module_mgr.c
@@ -813,7 +813,7 @@ int ecryptfs_process_decision_graph(stru
 	}
 	ad_cursor = ad_cursor->next;
 	ad_cursor->next = NULL;
-	if ((rc = asprintf(&ad_cursor->name,
+	if ((rc = asprintf(&ad_cursor->name, "%s",
 			   key_module_select_node.mnt_opt_names[0])) == -1) {
 		rc = -ENOMEM;
 		goto out_free_allowed_duplicates;
diff -Nru ecryptfs-utils-98/debian/ecryptfs-utils.lintian-overrides ecryptfs-utils-98/debian/ecryptfs-utils.lintian-overrides
--- ecryptfs-utils-98/debian/ecryptfs-utils.lintian-overrides	2012-06-29 13:22:29.0 +0200
+++ ecryptfs-utils-98/debian/ecryptfs-utils.lintian-overrides	2012-07-11 03:05:41.0 +0200
@@ -1,8 +1,3 @@
-# ecryptfs-utils does not (yet) build with hardening build flags
-ecryptfs-utils: hardening-no-stackprotector
-ecryptfs-utils: hardening-no-fortify-functions
-ecryptfs-utils: hardening-no-relro
-
 # false positives
 ecryptfs-utils: setuid-binary sbin/mount.ecryptfs_private 4755 root/root
 ecryptfs-utils: executable-not-elf-or-script usr/share/ecryptfs-utils/ecryptfs-record-passphrase
diff -Nru ecryptfs-utils-98/debian/libecryptfs0.lintian-override

Bug#681481: auctex: need to update triggers for new texlive?

[Julian Gilbey]

Package: auctex
Version: 11.86-10

/var/lib/dpkg/info/auctex.triggers currently lists:

interest /usr/share/texmf
interest /usr/share/texmf-texlive

But with texlive 2012, the latter should presumably be
/usr/share/texlive or perhaps /usr/share/texlive/texmf and
/usr/share/texlive/texmf-dist -- you could perhaps even get away with
/usr/share/texlive/texmf-dist.

   Julian



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

Bug#675731: base-files: Please add VERSION entry to /etc/os-release for unstable/testing too

[Raphael Hertzog]

On Sun, 03 Jun 2012, Santiago Vila wrote:
> If you want "wheezy", why can't you do this if VERSION is empty?
> 
> echo $PRETTY_NAME | awk '{ print $3 }' | sed -e 's#/.*##'

To avoid such hackery, you could export a DEBIAN_CODENAME variable.
/etc/os-release allows for vendor-specific fields.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Get the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/



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

Bug#681480: base-files: Provide HOME_URL, SUPPORT_URL and BUG_REPORT_URL in /etc/os-release

[Raphaël Hertzog]

Package: base-files
Version: 6.11
Severity: wishlist

http://www.freedesktop.org/software/systemd/man/os-release.html mentions
HOME_URL, SUPPORT_URL and BUG_REPORT_URL. It would be nice to provide
a value for those in /etc/os-release.

HOME_URL="http://www.debian.org";
SUPPORT_URL="http://www.debian.org/support";
BUG_REPORT_URL="http://bugs.debian.org";

Or maybe BUG_REPORT_URL="http://www.debian.org/Bugs/Reporting";.

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

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

Versions of packages base-files depends on:
ii  gawk [awk]  1:4.0.1+dfsg-2
ii  mawk [awk]  1.3.3-17

base-files recommends no packages.

base-files 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#676106: gonzui: FTBFS: configure: error: langscan for ruby not found

[Nobuhiro Iwamatsu]

Hi,

I sent a patch which revise FTBFS of langscan.
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676113

The problem in which a langscan library is not found is revised
with that patch.
However, since ruby-bdb offers only the library turned 1.8, gonzui
cannot be built yet.

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#681479: unblock: libconfig-model-perl/2.021-3

[Dominique Dumont]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package libconfig-model-perl

this package has a bug where data is not saved in the configuration file 
if hash key names are changed. For more details on what trigger the bug, see

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681353

I've cherry picked commits from upstream (aka me) to fix this issue (note that
the patches are more readble there than in the attached debdiff):

http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libconfig-model-perl.git;a=blob_plain;f=debian/patches/fix-unsaved-changes;hb=HEAD

This change uses a mechanism which is already provided to make sure that changed
data is saved.

The second patch test the fix:

 
http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libconfig-model-perl.git;a=blob_plain;f=debian/patches/test-fix-unsaved-changes;hb=HEAD

All the best

unblock libconfig-model-perl/2.021-3

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

Kernel: Linux 3.2.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
diff -Nru libconfig-model-perl-2.021/debian/changelog libconfig-model-perl-2.021/debian/changelog
--- libconfig-model-perl-2.021/debian/changelog	2012-06-29 14:14:48.0 +0200
+++ libconfig-model-perl-2.021/debian/changelog	2012-07-13 14:46:28.0 +0200
@@ -1,3 +1,15 @@
+libconfig-model-perl (2.021-3) unstable; urgency=low
+
+  * use patch from upstream to fix unsaved changes (Closes: #681353)
+Config::Model saves back data only when they are changed. To keep
+track of the changes, the notify_changes method must be called
+whenever a data is changed, otherwise the modifications will be
+lost. The patch fix-unsaved-change add calls to the notify_change
+method where it was forgotten. The second patch
+(test-fix-unsaved-changes) add the relevant test cases.
+
+ -- Dominique Dumont   Fri, 13 Jul 2012 14:22:05 +0200
+
 libconfig-model-perl (2.021-2) unstable; urgency=low
 
   * added a patch to fix a race condition between async calls to rmadison
diff -Nru libconfig-model-perl-2.021/debian/patches/fix-unsaved-changes libconfig-model-perl-2.021/debian/patches/fix-unsaved-changes
--- libconfig-model-perl-2.021/debian/patches/fix-unsaved-changes	1970-01-01 01:00:00.0 +0100
+++ libconfig-model-perl-2.021/debian/patches/fix-unsaved-changes	2012-07-13 14:46:28.0 +0200
@@ -0,0 +1,90 @@
+Description: Fix unsaved changes when changing hash keys
+ See description in debian bug. 
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681353
+Forwarded: yes
+Origin: upstream
+Applied-Upstream: yes
+--- a/lib/Config/Model/ListId.pm
 b/lib/Config/Model/ListId.pm
+@@ -234,6 +234,7 @@
+ if ($ok or $check eq 'no') {
+ $self->_store($to, $moved) ;
+ $moved->index_value($to) ;
++$self->notify_change(note => "moved from index $from to $to") ;
+ my $imode = $self->instance->get_data_mode ;
+ $self->set_data_mode( $to, $imode ) ;
+ }
+@@ -304,8 +305,7 @@
+ $self->{data}[$ida] = $objb ;
+ $self->{data}[$idb] = $obja ;
+ 
+-$self->notify_change(index => $ida) ;
+-$self->notify_change(index => $idb) ;
++$self->notify_change(note => "swapped index $ida and $idb") ;
+ }
+ 
+ #die "check index number after wap";
+--- a/lib/Config/Model/HashId.pm
 b/lib/Config/Model/HashId.pm
+@@ -280,6 +280,8 @@
+ delete $self->{warning_hash}{$from} ;
+ # update index_value attribute in moved objects
+ $self->{data}{$to}->index_value($to) ;
++
++$self->notify_change(note => "rename key from $from to $to");
+ 
+ # data_mode is preset or layered or user. Actually only user
+ # mode makes sense here
+@@ -333,6 +335,7 @@
+ 
+ my $list = $self->{list} ;
+ 
++my $msg ;
+ if (defined $ref_key) {
+ for (my $idx = 0; $idx <= $#$list; $idx ++ ) {
+ if ($list->[$idx] eq $ref_key) {
+@@ -340,9 +343,16 @@
+ last;
+ }
+ }
++
++$msg = "moved key $key_to_move after $ref_key" ;
+ } else {
+ unshift @$list , $key_to_move ;
++$msg = "moved key $key_to_move at beginning" ;
+ }
++
++
++$self->notify_change( note => $msg ) ;
++
+ }
+ 
+ 
+@@ -363,9 +373,13 @@
+ if ($list->[$idx] eq $key) {
+ $list->[$idx]   = $list->[$idx-1];
+ $list->[$idx-1] = $key ;
++$self->notify_change(note => "moved up key $key") ;
+ last ;
+ }
+ }
++
++# notify_change is placed in the loop so the notification
++# is not sent if the user tries to move up idx 0
+ }
+ 
+ 
+@@ -386,9 +400,13 @@
+ if ($list->[$idx] eq $key) {

Bug#680740:

[Zooko Wilcox-O'Hearn]

Folks:

I'm an upstream maintainer of Tahoe-LAFS and wanted to post to this
bug just to emphasize that Tahoe-LAFS 1.9.2 is strictly a bugfix
release over Tahoe-LAFS 1.9.1, and it is unlikely to introduce any
regressions or disruptions if you include 1.9.2 in Wheezy. As the
NEWS.rst file ¹ that Bert Agaz referenced describes, we fixed 14 bugs
in Tahoe-LAFS v1.9.2 and we did not introduce any features or change
any behavior that is likely to cause problems for people upgrading
from Tahoe-LAFS v1.9.1.

Some of the bugs that were fixed in this release were causing
widespread problems for users -- we've had several reports from users
that their repair jobs were failing with Tahoe-LAFS v1.9.1 and that
once they upgraded to 1.9.2 everything began working correctly.

So, please include Tahoe-LAFS v1.9.2 in the stable release of Debian
so that Debian users will not have that problem.

Thank you!

Regards,

Zooko

¹ https://tahoe-lafs.org/trac/tahoe-lafs/browser/NEWS.rst



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

Bug#676113: langscan: FTBFS: /usr/bin/install: cannot stat `./c.': No such file or directory

[Nobuhiro Iwamatsu]

tags 676113 + patch
thanks

Hi,

I created a patch which revise this problem.
I attched a patch. But this patch for covert to ruby1.9 and other are
not included.

Best regards,
  Nobuhiro

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


langscan-1.2+cvs20070125.debdiff
Description: Binary data

Bug#681478: wireshark-common: mergecap generates unusable file if interface index 0 has no packets

[Philipp Marek]

Package: wireshark-common
Version: 1.8.0-1
Tags: upstream

mergecap: Error reading : The file appears to be damaged or corrupt.
(pcapng: interface index 1024 is not less than interface count 1.)


Upstream report: 
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7381

Perhaps the previous version package should be made available again, until 
this is fixed in upstream.


Regards,

Phil




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

Bug#681477: dpkg-vendor: implement --select-closest command versions

[Raphael Hertzog]

Package: dpkg-dev
Version: 1.16.7
Severity: wishlist
User: d...@packages.debian.org
Usertags: dpkg-vendor

The --derives-from command works but when you have multiple levels of
derivatives, it imposes you to order your checks in the correct order 
to have the expected behaviour. It's also not reliable in the case
where the derivative relationships are symmetric (i.e. like RedHat and Fedora
which are evolving in parallel but building on each another). This
symmetric relationship is explicitely allowed in the ID_LIKE field
of /etc/os-release.

Therefore I suggest to implement a "dpkg-vendor --select-closest 
 ..." command that would compare all the listed distributions and
that would return the distribution which is closest to the current
distribution. This enables us to do:

TARGET_VENDOR := $(shell dpkg-vendor --select-closest debian ubuntu mint)

ifeq($(TARGET_VENDOR),mint)
# Mint specific options
else ifeq($(TARGET_VENDOR),ubuntu)
# Ubuntu specific options
else ifeq($(TARGET_VENDOR),debian)
# Debian specific options
endif

This command can be reliably implemented with /etc/dpkg/origin/* and with
/etc/os-release since the latter orders the derivatives listed in ID_LIKE
from the closest to the furthest.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Get the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/



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

Bug#654851: unattended-upgrades: email notifications don't have "Content-Type:" header

[Teodor MICU]

2012/7/13 Teodor MICU :
> What if «mail» is not available either?

I've just tested and no message is send. This is indeed mentioned in
the configuration file (from apt.conf.d) but it should be updated to
mention «sendmail» or «mailx» due to these changes. Probably a note in
README would not hurt anyone. :-)

While you are at this, the example [E.g. "u...@example.com"] should be
moved on a new line.

Cheers



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

Bug#681476: libqtcore4: use after free in src/corelib/tools/qlocale_unix.cpp

[Julien Cristau]

Subject: libqtcore4: use after free in src/corelib/tools/qlocale_unix.cpp
Package: libqtcore4
Version: 4:4.8.2-1
Severity: normal
Tags: patch

Valgrind complains about a use after free in the QSystemLocale code:

==15546== Invalid read of size 1
==15546==at 0xCEA4A76: QByteArray::QByteArray(char const*) (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCEF924E: QSystemLocale::query(QSystemLocale::QueryType, 
QVariant) const (in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCEC24D8: QLocalePrivate::updateSystemPrivate() (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCEC2E3A: systemPrivate() (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCEC2E68: defaultPrivate() (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCEC2F99: QLocale::QLocale() (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCF4B139: QResourceFileEngine::QResourceFileEngine(QString 
const&) (in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCF730FF: 
_q_resolveEntryAndCreateLegacyEngine_recursive(QFileSystemEntry&, 
QFileSystemMetaData&, QAbstractFileEngine*&, bool) (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCF7335D: 
QFileSystemEngine::resolveEntryAndCreateLegacyEngine(QFileSystemEntry&, 
QFileSystemMetaData&) (in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCF2EC11: QFileInfo::QFileInfo(QString const&) (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCF2A551: QFile::exists(QString const&) (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCE99FD2: QLibraryInfoPrivate::findConfiguration() (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==  Address 0x2a301798 is 24 bytes inside a block of size 37 free'd
==15546==at 0x4C27D4E: free (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==15546==by 0xCEF8F9E: getSystemLocale() (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCEF9236: QSystemLocale::query(QSystemLocale::QueryType, 
QVariant) const (in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCEC24D8: QLocalePrivate::updateSystemPrivate() (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCEC2E3A: systemPrivate() (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCEC2E68: defaultPrivate() (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCEC2F99: QLocale::QLocale() (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCF4B139: QResourceFileEngine::QResourceFileEngine(QString 
const&) (in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCF730FF: 
_q_resolveEntryAndCreateLegacyEngine_recursive(QFileSystemEntry&, 
QFileSystemMetaData&, QAbstractFileEngine*&, bool) (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCF7335D: 
QFileSystemEngine::resolveEntryAndCreateLegacyEngine(QFileSystemEntry&, 
QFileSystemMetaData&) (in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCF2EC11: QFileInfo::QFileInfo(QString const&) (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==15546==by 0xCF2A551: QFile::exists(QString const&) (in 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)

indeed disassembling getSystemLocale() shows a call to qFree(), from the
QByteArray destructor, apparently because it returns const char *
instead of QByteArray.  Changing the return type as below makes the use
after free disappear.

--- qt4-x11-4.8.2.orig/src/corelib/tools/qlocale_unix.cpp
+++ qt4-x11-4.8.2/src/corelib/tools/qlocale_unix.cpp
@@ -52,7 +52,7 @@
 
 QT_BEGIN_NAMESPACE
 
-static const char *getSystemLocale()
+static QByteArray getSystemLocale()
 {
 #if defined(Q_OS_QNX)
 static char buff[257];

Cheers,
Julien
-- 
Julien Cristau  
Logilab http://www.logilab.fr/
Informatique scientifique & gestion de connaissances



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

Bug#681471: gunicorn < 0.14.4 does not properly limit requests size

[Djoume Salvetti]

+1 for migrating 0.14.5 from sid to wheezy.

On 12-07-13 09:47 AM, Chris Lamb wrote:

Hi Djoume,


Package: gunicorn
Version: 0.14.3-1
Severity: grave

[..]

This has been fixed upstream in 0.14.4:


We could cherry-pick this commit and upload the result to wheezy-p-u
but I suggest that we just request an unblock for the current sid
version.

Just looks like bugfixes since 0.14.3 and 0.14.5 has been sitting in sid
for at least 10 days now.

(Or maybe it will migrate automatically; can't remember how we are doing
the borderline exemptions for this freeze.)


Regards,






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

Bug#634930: gpa: GPA unusable due to "General Assuan error"

[Werner Koch]

Hi,

I tried to replicate the problem with the current stable versions of GPA
0.9.2 and GPGME (well, my working copy).  I was not able to do that.  I
don't have a clean squeeze installation right now available thus I can't
check 0.9.0 easily.

Lionel, would you mind to run another test with GPA 0.9.2, GPGME 1.3.2,
and GnuPG 2.0.19 (or 2.1-beta).


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.




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

Bug#681281: tcc sometimes fails to read a long long correctly on i386

[Thomas Preud'homme]

Le jeudi 12 juillet 2012 00:19:41, vous avez écrit :
> 
> On i386 tcc can fails to read a long long value. A simple test case
> showing the problem:

[SNIP]

Since arm also needs 2 registers to store a long long, this bugs also affect 
armel. Note however that this precise testcase doesn't exhibit the bug for 
armel since arm has much more registers than i386.


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

Bug#681364: [regression] does not maintain focus when switching tags

[Julien Danjou]

On Fri, Jul 13 2012, Yaroslav Halchenko wrote:

> https://awesome.naquadah.org/bugs/index.php?getfile=512
>
> does not fix the issue for me.  Is there any other fix to try in
> conjunction/instead?

This is not the fix. The fix is:

http://git.naquadah.org/?p=awesome.git;a=commit;h=c084eb5b085287e4fb2661e834197cf8cf233215

-- 
Julien Danjou
/* Free Software hacker & freelance
   http://julien.danjou.info */



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

Bug#681471: gunicorn < 0.14.4 does not properly limit requests size

[Chris Lamb]

Hi Djoume,

> Package: gunicorn
> Version: 0.14.3-1
> Severity: grave
[..]
> This has been fixed upstream in 0.14.4:

We could cherry-pick this commit and upload the result to wheezy-p-u
but I suggest that we just request an unblock for the current sid
version.

Just looks like bugfixes since 0.14.3 and 0.14.5 has been sitting in sid
for at least 10 days now.

(Or maybe it will migrate automatically; can't remember how we are doing
the borderline exemptions for this freeze.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org
   `-


signature.asc
Description: PGP signature

Bug#681364: [regression] does not maintain focus when switching tags

[Yaroslav Halchenko]

unfortunately that patch

https://awesome.naquadah.org/bugs/index.php?getfile=512

does not fix the issue for me.  Is there any other fix to try in
conjunction/instead?

On Fri, 13 Jul 2012, Julien Danjou wrote:

> tag 681364 fixed-upstream
> forwarded 681364 
> https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1011
> thanks

> On Thu, Jul 12 2012, Yaroslav Halchenko wrote:

> > When I switch the tags, either with Mod4+ or Mod4+Esc, awesome
> > now focuses either on KDE's menu or (after I set focus=false for Plasma 
> > class)
> > on gkrellm ( I use awesome as KDEWM='--windowmanager awesome )

> > I believe this is a chance of beahvior and happened after recent upgrade
> > (finally I got to wheezy state): 2012-07-11 14:11:29 upgrade awesome:amd64
> > 3.4.11-2 3.4.12-2.  I think that awesome previously maintained the focus --
> > i.e. focused on the window in the tag it was previously focused on before
> > switching to a different tag. ... downgraded to 3.4.11-2 from snapshot.d.o 
> > --
> > yes, it works.  upgraded back to 3.4.12-2, restarted -- yes, bug is back
> > here

> > I marked it as important because it does have major usability effect given 
> > that
> > switching between tags is one of the most common operations.

> Yes, this is
> https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1011&project=1&order=id&sort=desc
-- 
Yaroslav O. Halchenko
Postdoctoral Fellow,   Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik



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

Bug#681475: std::pair C++03/11 incompat

[James Y Knight]

Package: gcc-4.7
Version: 4.7.1-2

In the current version of GCC 4.7 in Debian, std::pair isn't
ABI-compatible when used as a return value between C++03 and C++11 modes.
This was recently fixed in:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53657

It'd be really nice to get the fixed version of gcc accepted into wheezy,
so that users (or packages) compiling with -std=c++11 don't get mysterious
crashes from it. This particular incompatibility bites many boost::python
programs compiled in C++11 mode (against the c++03 debian
libboost-python), and surely there are other real cases where it shows up
as well.




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

Bug#681474: Dpkg::Vendor: should support /etc/os-release and /etc/os-release.d/*

[Raphael Hertzog]

Package: libdpkg-perl
Version: 1.16.7
Severity: wishlist

Debian is now shipping an /etc/os-release file and this file can provide
all the information that /etc/dpkg/origins/* files can provide. See
http://www.freedesktop.org/software/systemd/man/os-release.html
for the various fields that are supported and in particular ID_LIKE,
HOME_URL and BUG_REPORT_URL.

To be able to retrieve information from all the parents, the various
os-release files can be stored in /etc/os-release.d/ and /etc/os-release
could become a symlink.

Dpkg::Vendor should thus be updated to be able to use those (cross-distro
standardized) files when they exist so that we can deprecate the
debian-specific /etc/dpkg/origins/*.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Get the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/



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

Bug#681418: debugfs is a big security hole

[Henrique de Moraes Holschuh]

On Fri, 13 Jul 2012, Ben Hutchings wrote:
> I certainly consider mounting of debugfs to be significant security
> liability.  I'm not at all happy that people use it as the basis for

Seconded.  I know of at least three ways to hardcrash boxes through
debugfs (system specific, not a kernel bug), and the unfortunate naming
DOES help kernel maintainers take an even more irresponsible instance
regarding security than what is already [unfortunately] normal.  e.g.
missing calls to capable() in debugfs handlers.

It really should be called "advcfgfs".  Either that, or it should taint
the kernel when mounted, and any production stuff would be forced to
"graduate" to a proper peer-reviewed interface.

> I would like to address this by backporting this feature:
> 
> commit d6e486868cde585842d55ba3b6ec57af090fc343
> Author: Ludwig Nussel 
> Date:   Wed Jan 25 11:52:28 2012 +0100
> 
> debugfs: add mode, uid and gid options
> 
> and then changing the default mode (mask) to be 0700.  This should
> leave debugfs functional (most such applications will require root
> anyway) and allow users to relax permissions if they really don't
> care about the security problems.

Actually, it would be best if we could set mode, uid and gid per
inode/dentry, with defaults to the ones in the mount command (or
root:root 700).  Just like tmpfs does.

> However, currently there is not a single place for the user options.
> I think that either (1) debugfs should be mounted by default in a
> similar way to other pseudo-filesystems, or (2) debugfs should have a
> noauto entry in /etc/fstab where users can set options, and packages
> may use 'mount /sys/kernel/debug' to mount debugfs with those options
> (not 'mount -t debugfs debugfs /sys/kernel/debug', as now).

Both ideas would work.  Can you provide a patch for the relevant
initscripts?

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh



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

Bug#681051: xpra: menus pop up off-screen

[Michal Suchanek]

Excerpts from Antoine Martin's message of Thu Jul 12 16:00:48 +0200 2012:
> >>> Perhaps some sample script in documentation, or perhaps even a
> >>> xorg.conf.dummy and a script in /usr/bin using it could be installed
> >>> with xpra so that everyone does not have to figure out how the hell is
> >>> that thing supposed to work.
> >>>
> >
> >>> A sample script using xorg.conf.dummy could look like this:
> >>>
> >>> xpra --xvfb="Xorg -nolisten tcp -config xorg.conf.dummy -noreset 
> >>> +extension GLX +extension RANDR +extension RENDER -logfile 
> >>> ~/.xpra/xserver-$DISPLAY.log" --start-child="/etc/X11/Xsession true" 
> >>> start :$DISPLAY
> >>>
> >>> It is sad that you can't know what display xpra picks when starting it
> >>> but without actually patching xpra you can't do more than that.
> >> I think the config file option above is the easiest way to improve
> >> things quickly?
> >
> > It requires that the xorg.conf linked on the wiki is installed at
> > /etc/X11/xorg.conf.dummy
> > Otherwise full path to the file is required.
> Sure, I was thinking of putting it in:
> /etc/xpra/xorg.conf.dummy
> Next to xpra's config. Saves potential clashes with Xorg paths/packages 
> and keeps it more self-contained. But your suggested location also 
> works. Are there any guidelines on things like this?

I guess it would be better to get the file into xserver-xorg-video-dummy
package in this case.

Thanks

Michal



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

Bug#681473: CVE-2012-3404 CVE-2012-3405 CVE-2012-3406

[Moritz Muehlenhoff]

Package: eglibc
Severity: important
Tags: security

Hi,
please see http://www.openwall.com/lists/oss-security/2012/07/11/17 for details
and references to upstream patches.

The security impact is rather low IMO; if the format strings are under control
of a attacker, this opens a whole can of worms anyway.

Still, it would be nice to get these fixed for Wheezy and for Squeeze in a point
update.

Cheers,
Moritz



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

Bug#681472: tuxonice-userui: how to select fpsplash mode with new unique ui program ?

[Frédéric Boiteux]

Package: tuxonice-userui
Version: 1.1-1
Severity: minor


Hello,

  I've updated my TuxOnIce'd featured Debian system with latest tuxonice-userui 
package, thanks for the update !
  I saw in NEWS.Debian that scripts should be updated as the new 
tuxonice-userui program is unique, using option -t or -f for selecting text or 
fbsplash interfaces. As I previously select the fbsplash interface using the 
tuxoniceuserui_fbsplash filename (in kernel configuration or hibernate script), 
how can I now select fbsplash, as neither kernel nor hibernate scripts offer 
options to userui program ?

   Thanks for any tip !

Fred.


-- System Information:
Debian Release: 6.0.5
  APT prefers stable
  APT policy: (990, 'stable'), (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-hp-toi (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tuxonice-userui depends on:
ii  initramfs-tools   0.98.8 tools for generating an initramfs
ii  libc6 2.11.3-3   Embedded GNU C Library: Shared lib
ii  libfreetype6  2.4.2-2.1+squeeze4 FreeType 2 font engine, shared lib
ii  libjpeg8  8d-1   Independent JPEG Group's JPEG runt
ii  libmng1   1.0.10-1+b1Multiple-image Network Graphics li
ii  libpng12-01.2.44-1+squeeze4  PNG library - runtime

Versions of packages tuxonice-userui recommends:
ii  hibernate  2.0+15+g88d54a8-1 smartly puts your computer to slee

tuxonice-userui 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#668824: doxygen: newer upstream version available

[Thibaut Paumard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

package doxygen
retitle 668824 Please package doxygen 1.8.1.2
thanks

For the record, Debian now has 1.8.1.1, upstream has 1.8.1.2 (since...
yesterday).

Clearly, this will have to wait for after the freeze (or be done in
experimental/backports).

Regards, Thibaut.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAAJIkACgkQ+37NkUuUiPH1+ACfdvcIoFrFYBt6UA6K0SuOJ1In
7iUAmQGVJc2nviUeJ9IHUk+1Kc2N4v4e
=gxjh
-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#681471: gunicorn < 0.14.4 does not properly limit requests size

[Djoume Salvetti]

Package: gunicorn
Version: 0.14.3-1
Severity: grave
Tags: security fixed-upstream


gunicorn 0.14 introduced the ability to check if a request line is too 
large to protect against DoS, however the implementation had the 
following flaws:


* Gunicorn does not limit the size of a request header (the 
limit_request_field_size configuration parameter is not used)


* When the configured request limit is lower than its maximum value, the 
maximum value is used instead. For instance if limit_request_line is set 
to 1024, gunicorn will only limit the request line to 4096 chars (this 
issue also affects limit_request_fields)


* Request limits are not limited to their maximum authorized values. For 
instance it is possible to set limit_request_line to 64K (this issue 
also affects limit_request_fields)


This has been fixed upstream in 0.14.4:

https://github.com/benoitc/gunicorn/commit/d79ff999ce895e2ed0ea02aa8729e6da736dfc27



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

Bug#654851: unattended-upgrades: email notifications don't have "Content-Type:" header

[Teodor MICU]

2012/7/13 Michael Vogt :
> Indeed, sorry for that, should be fixed in bzr trunk, if testing goes
> well I will upload today. It will use sendmail if available to set the
> header and if not mail but without the header as there is no portable way
> apparently to do that with mailx.

Maybe a Suggests: or Recommends: mail-transport-agent would be
appropriate for having «sendmail» available? It's nice that it handles
the case that «sendmail» is not available. What if «mail» is not
available either?

Cheers



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

Bug#681462: Bugs not showing up on the debian bugtracker

[Jérémy Lal]

Hi Jérémy,

Passenger:

winvirtdebian:~# dpkg -l | grep passenger
ii  libapache2-mod-passenger   3.0.13debian-1Rails 
and Rack support for Apache2
ii  ruby-passenger 3.0.13debian-1Rails 
and Rack support for Apache2 and Nginx

Apache:

winvirtdebian:~# dpkg -l | grep apache
ii  apache22.2.22-9  Apache 
HTTP Server metapackage
ii  apache2-mpm-prefork2.2.22-9  Apache 
HTTP Server - traditional non-threaded model
ii  apache2-utils  2.2.22-9  utility 
programs for webservers
ii  apache2.2-bin  2.2.22-9  Apache 
HTTP Server common binary files
ii  apache2.2-common   2.2.22-9  Apache 
HTTP Server common files
ii  libapache2-mod-fcgid   1:2.3.6-1.1   an 
alternative module compat with mod_fastcgi
ii  libapache2-mod-passenger   3.0.13debian-1Rails 
and Rack support for Apache2
ii  libapache2-mod-php55.4.4-2 
server-side, HTML-embedded scripting language (Apache 2 module)
ii  libapache2-svn 1.6.17dfsg-4 
Subversion server modules for Apache

Config apache:

redmine.conf

# These modules must be enabled : rewrite, fcgid
# (mod_fastcgi is much harder to configure)
# Configuration for http://localhost:8080

 ServerName redmine.elodom.elovis.de

 # DefaultInitEnv for module mod_fcgid
 DefaultInitEnv RAILS_RELATIVE_URL_ROOT ""
 DefaultInitEnv X_DEBIAN_SITEID "default"

 # the mod_fcgid socket path
#   SocketPath "/var/run/redmine/sockets/default"

 DocumentRoot /usr/share/redmine/public
 
 Options +FollowSymLinks +ExecCGI
 Order allow,deny
 Allow from all
 RewriteEngine On
 RewriteRule ^$ index.html [QSA]
 RewriteRule ^([^.]+)$ $1.html [QSA]
 RewriteCond %{REQUEST_FILENAME} !-f [OR]
 RewriteCond %{REQUEST_FILENAME} dispatch.fcgi$
 RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
 

 CustomLog /var/log/apache2/redmine_access.log combined

Config passenger:

passenger.conf


   PassengerRoot /usr
   PassengerRuby /usr/bin/ruby
   PassengerDefaultUser www-data


What else?

PS: The error startet after some updates of many ruby and/or passenger 
packages just around a week ago. See attached aptitude log for this 
month. The problem started in between, i cannot specify in detail.

PS: reportbug sends the mail via CC to me, but it doesnt show up on 
debian BTS. Any ideas?

Thanks for your help.

Am 13.07.2012 13:50, schrieb Jérémy Lal:
> On 13/07/2012 13:38, Holger Rusch wrote:
>> Hi,
>>
>> see attached two bugs in redmine which i have send via reportbug
>> yesterday and which are still not showing up in the tracker.
>
> I need to know more about your setup, especially passenger:
> which package, version, how it is run (by apache ?) and what's
> the config.
>
> Jérémy.
>





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

Bug#681470: dpkg-shlibdeps: should also scan Build-Depends-Arch for minimal versions

[Raphael Hertzog]

Package: dpkg-dev
Version: 1.16.4
Severity: normal
User: d...@packages.debian.org
Usertags: dpkg-shlibdeps

dpkg 1.16.4 introduced the Build-Depends-Arch field but dpkg-shlibdeps has
not been updated to deal with this field.

Build dependencies are sometimes scanned to find out minimal versions to
inject in binary package dependencies. Build-Depends-Indep are not scanned
because by definition a library dependency required to build an executable
can not be put there.

However Build-Depends-Arch can perfectly host such build dependencies and
thus dpkg-shlibdeps should be updated to scan them too.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Get the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/



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

Bug#680837: weboob: FTBFS: Unknown Qt widget: Phonon.VideoPlayer

[Cyril Brulebois]

reassign 680837 python-qt4 4.9.3-2
affects  680837 weboob
thanks

Lucas Nussbaum  (08/07/2012):
> Source: weboob
> Version: 0.c-4
> Severity: serious
> Tags: wheezy sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20120708 qa-ftbfs
> Justification: FTBFS on amd64
> 
> > make[2]: Entering directory 
> > `/«PKGBUILDDIR»/weboob/applications/qvideoob/ui'
> > pyuic4 -o main_window_ui.py main_window.ui
> > pyuic4 -o minivideo_ui.py minivideo.ui
> > pyuic4 -o video_ui.py video.ui
> > Unknown Qt widget: Phonon.VideoPlayer
> > make[2]: *** [video_ui.py] Error 1

Many thanks to Scott for the analysis, bug in python-qt4 instead,
reassigning/affecting accordingly.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#681097: CVE-2012-3386: Information disclosure

[Moritz Mühlenhoff]

On Freitag, 13. Juli 2012 04:45:25 Eric Dorland wrote:
> * Moritz Muehlenhoff (muehlenh...@univention.de) wrote:
> > Package: automake
> > Version: 1:1.11-1.2.201001121001
> > Severity: important
> > Tags: security
> > 
> > Hi,
> > a security issue has been found in automake. It's not earth-shattering,
> > but we should still get it into Wheezy.
> > 
> > http://thread.gmane.org/gmane.comp.sysutils.automake.patches/8572
> > 
> > This also affects the source packages automake, automake1.7, automake1.9
> > and automake1.10...
> 
> It looks like it doesn't affect automake1.4, but I'm awaiting
> confirmation. Should I prepare a stable update as well or is it not
> worth it?

It doesn't warrant a DSA, but such issues can be fixed in a Squeeze point 
update. I'm adding Jonathan Wiltshire to CC, who's coordinating this process.

Cheers,
Moritz
-- 
Moritz Mühlenhoff muehlenh...@univention.de
Open Source Software Engineer
Univention GmbH  be open.fon: +49 421 22 232- 0
Mary-Somerville-Str.1  28359 Bremen  fax: +49 421 22 232-99
http://www.univention.de



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

Bug#681469: unblock: sbjson/2.3.2-2

[Jeroen Dekkers]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package sbjson

The new version builds with hardening enabled and links correctly with
the libraries it depends on, resulting in correct Depends.


unblock sbjson/2.3.2-2

-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-26-generic (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

diff -Nru sbjson-2.3.2/debian/changelog sbjson-2.3.2/debian/changelog
--- sbjson-2.3.2/debian/changelog   2012-05-09 23:11:11.0 +0200
+++ sbjson-2.3.2/debian/changelog   2012-06-29 19:11:14.0 +0200
@@ -1,3 +1,10 @@
+sbjson (2.3.2-2) unstable; urgency=low
+
+  * Build with hardening enabled.
+  * Correctly link with libobjc and libgnustep-base.
+
+ -- Jeroen Dekkers   Fri, 29 Jun 2012 19:09:28 +0200
+
 sbjson (2.3.2-1) unstable; urgency=low
 
   * Initial release. (Closes: #672134)
diff -Nru sbjson-2.3.2/debian/control sbjson-2.3.2/debian/control
--- sbjson-2.3.2/debian/control 2012-05-09 23:11:11.0 +0200
+++ sbjson-2.3.2/debian/control 2012-06-29 18:23:32.0 +0200
@@ -2,7 +2,7 @@
 Section: libs
 Priority: optional
 Maintainer: Jeroen Dekkers 
-Build-Depends: debhelper (>= 9), cdbs, gobjc, gnustep-make, libgnustep-base-dev
+Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1~), cdbs, gobjc, 
gnustep-make, libgnustep-base-dev
 Standards-Version: 3.9.3
 Homepage: http://stig.github.com/json-framework
 Vcs-Browser: https://github.com/dekkers/sbjson
diff -Nru sbjson-2.3.2/debian/patches/0001-add-makefiles.patch 
sbjson-2.3.2/debian/patches/0001-add-makefiles.patch
--- sbjson-2.3.2/debian/patches/0001-add-makefiles.patch2012-05-09 
23:11:11.0 +0200
+++ sbjson-2.3.2/debian/patches/0001-add-makefiles.patch2012-06-29 
19:11:09.0 +0200
@@ -3,18 +3,18 @@
 Subject: add-makefiles
 
 ---
- Classes/GNUmakefile |   27 +++
+ Classes/GNUmakefile |   29 +
  GNUmakefile |9 +
- 2 files changed, 36 insertions(+), 0 deletions(-)
+ 2 files changed, 38 insertions(+)
  create mode 100644 Classes/GNUmakefile
  create mode 100644 GNUmakefile
 
 diff --git a/Classes/GNUmakefile b/Classes/GNUmakefile
 new file mode 100644
-index 000..2249e72
+index 000..625d963
 --- /dev/null
 +++ b/Classes/GNUmakefile
-@@ -0,0 +1,27 @@
+@@ -0,0 +1,29 @@
 +# GNUstep makefile
 +include $(GNUSTEP_MAKEFILES)/common.make
 +
@@ -39,6 +39,8 @@
 +SBJsonParser.m \
 +SBJsonWriter.m
 +
++SBJson_LIBRARIES_DEPEND_UPON += -lgnustep-base -lobjc
++
 +-include GNUmakefile.preamble
 +include $(GNUSTEP_MAKEFILES)/library.make
 +-include GNUmakefile.postamble
diff -Nru sbjson-2.3.2/debian/rules sbjson-2.3.2/debian/rules
--- sbjson-2.3.2/debian/rules   2012-05-09 23:11:11.0 +0200
+++ sbjson-2.3.2/debian/rules   2012-06-29 17:57:11.0 +0200
@@ -3,6 +3,11 @@
 # Uncomment this to turn on verbose mode.
 export DH_VERBOSE=1
 
+export DEB_BUILD_MAINT_OPTIONS=hardening=+bindnow
+include /usr/share/dpkg/buildflags.mk
+# FIXME: dpkg-buildflags / cdbs should support OBJCFLAGS
+DEB_MAKE_BUILD_TARGET = all messages=yes OBJCFLAGS="$(CFLAGS)"
+
 include /usr/share/cdbs/1/rules/gnustep.mk
 include /usr/share/cdbs/1/class/gnumakefile.mk
 



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

Bug#681468: redmine: Adding of watchers to a ticket impossible

[Holger Rusch]

Package: redmine
Version: 1.4.4+dfsg1-1
Severity: normal

Dear Maintainer,

First:
I am also biten by #678515 and have switched ruby to 1.8 per
update-alternatives.
Redmine is runnig under passenger. I am running an actual fully updated
testing.

Problem:
If i want to add a watcher to a ticked nothing happens.
The URL changes from ".../issue/395" to ".../issue/395#".
No log entry is created in production.log.

Thanks for help.

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

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

Versions of packages redmine depends on:
ii  bundler   1.1.4-4
ii  dbconfig-common   1.8.47+nmu1
ii  debconf [debconf-2.0] 1.5.44
ii  rails 2:2.3.14.2
ii  redmine-mysql 1.4.4+dfsg1-1
ii  ruby  4.9
ii  ruby-coderay  1.0.6-2
ii  ruby-fastercsv1.5.5-1
ii  ruby-net-ldap 0.3.1-2
ii  ruby-rack 1.4.1-2
ii  ruby-rails-2.32.3.14-3
ii  ruby1.8 [ruby-interpreter]1.8.7.358-4
ii  ruby1.9.1 [ruby-interpreter]  1.9.3.194-1

redmine recommends no packages.

Versions of packages redmine suggests:
pn  bzr   
pn  cvs   
pn  darcs 
ii  git   1:1.7.10.4-1
pn  mercurial 
pn  ruby-openid   
pn  ruby-rmagick  
ii  subversion1.6.17dfsg-4

-- debconf information:
  redmine/instances/default/passwords-do-not-match:
  redmine/instances/default/remote/newhost:
  redmine/instances/default/db/basepath:
  redmine/instances/default/pgsql/changeconf: false
  redmine/instances/default/missing-db-package-error: abort
  redmine/default-language: ${defaultLocale}
  redmine/instances/default/pgsql/no-empty-passwords:
  redmine/instances/default/pgsql/method: unix socket
* redmine/instances/default/database-type: mysql
  redmine/instances/default/pgsql/manualconf:
  redmine/instances/default/pgsql/authmethod-admin: ident
  redmine/instances/default/pgsql/admin-user: postgres
  redmine/missing-redmine-package:
  redmine/instances/default/pgsql/authmethod-user: password
  redmine/instances/default/dbconfig-reinstall: false
* redmine/instances/default/db/app-user: redmine
* redmine/instances/default/default-language: de
  redmine/notify-migration:
  redmine/old-instances:
  redmine/instances/default/upgrade-error: abort
* redmine/instances/default/db/dbname: redmine_default
  redmine/instances/default/purge: false
* redmine/current-instances: default
  redmine/instances/default/remote/host:
  redmine/instances/default/dbconfig-upgrade: true
  redmine/instances/default/internal/reconfiguring: false
  redmine/instances/default/upgrade-backup: true
  redmine/instances/default/install-error: abort
* redmine/instances/default/mysql/admin-user: root
* redmine/instances/default/mysql/method: unix socket
  redmine/instances/default/internal/skip-preseed: false
  redmine/instances/default/remove-error: abort
  redmine/instances/default/dbconfig-remove:
  redmine/instances/default/remote/port:
* redmine/instances/default/dbconfig-install: true



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

Bug#681003: On tar.gz

[SM Baby Siabef]

I don't know why that file has encoding problems [it has the charset 
UTF-8, 8-bit...]


But I send [again, on tar.gz] the file.

If there's any problems, tell me.


es.po.tar.gz
Description: GNU Zip compressed data

Bug#680988: scim: Scim stops working properly in Sid with latest version

[Physicman]

Hi Tz-Huan,

On Fri, 13 Jul 2012 18:06:25 +0800
Tz-Huan Huang  wrote:

> Hi Chris,
[snip]
> Could you please give the version 1.2.7-4tz1 a  try?
> (http://www.csie.ntu.edu.tw/~tzhuan/debian)
> 
> It is based on 1.2.7-4 but contains the UI fixes.
> 

I'll try to give it a go tomorrow. I'll let you know the result.


> Thanks,
> Tz-Huan

Thanks for your help.

Best regards,

Chris

-- 
 ,''`.  Christopher `Physicman' Bodenstein 
 : :' :  Physicman.Net :   http://www.physicman.net/ 
 `. `'   Debian GNU/Linux  :   http://www.debian.org/
   `-Lisez le JIM  :   http://www.lejim.info/


pgp8rPWeo8lQZ.pgp
Description: PGP signature

Bug#681467: unattended-upgrades: broken on kfreebsd without ionice

[Steven Chamberlain]

Package: unattended-upgrades
Version: 0.79
Severity: grave
Tags: wheezy sid
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org

Hi,

Having upgraded unattended-upgrades from 0.76.3 -> 0.79 to follow
Wheezy, the following error occurs now on GNU/kFreeBSD:

> # unattended-upgrade -d
> Traceback (most recent call last):
>   File "/usr/bin/unattended-upgrade", line 964, in 
> stderr=fstderr)
>   File "/usr/lib/python2.7/subprocess.py", line 493, in call
> return Popen(*popenargs, **kwargs).wait()
>   File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
> errread, errwrite)
>   File "/usr/lib/python2.7/subprocess.py", line 1249, in _execute_child
> raise child_exception
> OSError: [Errno 2] No such file or directory

This is due to there being no ionice executable.  With a dummy
placeholder it seems functional again:

> # ln -s /bin/true /usr/bin/ionice
> # unattended-upgrade -d
> Initial blacklisted packages: 
> Starting unattended upgrades script
> ...

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org



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

Bug#681314: unblock: yp-svipc/0.14-2

[Thibaut Paumard]

> 3- the yorick-full meta-package (src:yorick), already unblocked, is
> waiting for yorick-svipc to build on kfreebsd-* before it can migrate.
>http://release.debian.org/migration/testing.pl?package=yorick
> Fixing the above-mentioned FTBFS takes us halfway through to letting
> yorick migrate (Yorick is also waiting for yorick-gyoto, I'm working
> on it).

For the record, the unblock request for gyoto is at:
   http://bugs.debian.org/681463

Regards, Thibaut.



smime.p7s
Description: Signature cryptographique S/MIME

Bug#681466: tasksel: update input method support and Chinese tasks

[Aron Xu]

Package: src:tasksel
Tags: patch

Hi,


I've prepared a patch for improving the input method support status in
Wheezy, together with some updates to Chinese tasks.

1. Input method:

a) scim-tables was removed from the archive because it was not
maintained. There are people uploaded it to NEW again, but I'm not
sure about its current quality and whether it will enter testing. So
all referenced places are replaced with Fcitx, which has added those
support before freeze aimed at being able to replace SCIM when needed.

b) im-config is replacing im-switch, and tasks where have input
methods is recommending im-config even if it wasn't recommend
im-switch before. im-switch is due to be removed from Wheezy +1, and
we want the transition be as smooth as possible from Wheezy.

c) IM Modules are explicitly added to Recommends, so that users can
take advantage of improved experience.

c) Fcitx has changed a lot so that chinese-s tasks need some updates
to enable those features

d) Japanese task adds uim-mozc, which is a good candidate in the
phrase of user experience. But there are people arguing that even
though mozc is open sourced, the community isn't that open. If there
are disagreement from Japanese community we can remove it later.

2. Chinese taks:

a) jfbterm has been replaced by zhcon, even though it is also
deprecated, it's still the best solution comparing with fbterm.

b) Varies deprecated packages are removed, downgraded or replaced by
modern equivalent.

c) Traditional Chinese community is still discussing about what
default input method they want to have in the task, so this part may
change later. Currently it's the defaults used in Ubuntu. (See: Bug #680668)


--
Regards,
Aron Xu


0001-Update-input-method-support-and-Chinese-tasks.patch
Description: Binary data

Bug#681450: t-prot: package description review

[Jochen Striepe]

Hello,

On Fri, Jul 13, 2012 at 09:45:34AM +0100, Justin B Rye wrote:
> The package description for t-prot has a couple of typos and language
> issues.  While fixing them I've reshuffled it quite a bit.

Thanks for reviewing. Since the package description is a Debian issue,
I will leave any comments to Gerfried, except:


> >  message run through a filter before it's displayed. If you use such a 
> > program
> >  we'd be interested if you could send in your setup.
> 
> (Did anybody ever do this?)

Yes, we got setups for Heirloom mailx and metamail from users ...


> |  It offers hints on how to apply it within Mutt, slrn, or INN 2.

... for which example configurations are provided in the package. The
DESCRIPTION part of the man page points at those, perhaps the package
description should be updated accordingly.


Greetings from Germany,
Jochen.



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

Bug#681442: mailx just does not support this....

[Bjørn Mork]

Michael Vogt  writes:

> I consider the above comments as rather rude. 

I apologize for that.  Yes, I see that the tone of that comment can be
considered rude.  That was really not the intention.

> The tests where run and
> don't fail on my system(s). This maybe locale dependant thought which
> indicates that they are not good enough. But claiming they are not run
> at all and that they are useless is a bit over the top. Plus they test
> that the mail is send (or not) and that it contains the elements
> needed.

This may be just me misunderstanding something, but the "test_mail.py"
script seems to redirect the mail to a file by replacing the mailx binary
with "mock-mail", which just redirects it's input to a file.  And I failed
to see how it could succeed as long as "utf-8" != "utf8"

bjorn@canardo:/usr/local/mydebs/tmp/unattended-upgrades-0.79.1$ egrep 'utf-?8' 
unattended-upgrade test/test_mail.py 
unattended-upgrade:# ensure that the message a utf8 encoded string
unattended-upgrade:s = s.encode("utf-8", "replace")
unattended-upgrade:msg.set_charset("utf8")
test/test_mail.py:# -*- coding: utf-8 -*-
test/test_mail.py:self.assertTrue('Content-Type: text/plain; 
charset="utf-8"' in mail_txt)

unless of course, your Message.set_charset does some magic processing of
the input.  Which it indeed does in wheezy.  That explains it.  I did a
(too) quick test on a system running squeeze.  My fault.

Sorry about that.  And once again my apoligies for the tone.  It was
completely unwarranted, and not appropriate at all in any case.


Bjørn



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

Bug#681418: debugfs is a big security hole

[Bjørn Mork]

Ben Hutchings  writes:

> I would like to address this by backporting this feature:
>
> commit d6e486868cde585842d55ba3b6ec57af090fc343
> Author: Ludwig Nussel 
> Date:   Wed Jan 25 11:52:28 2012 +0100
>
> debugfs: add mode, uid and gid options
>
> and then changing the default mode (mask) to be 0700. 

I like the proposal, but the feature does not seem mature yet.  Played a
bit with it and noticed a couple of confusing bugs which IMHO should be
fixed first:

 1) mode and owner is not propagated to files below the mount point:

nemi:/tmp# mount /sys/kernel/debug -o uid=42,mode=0700
nemi:/tmp# ls -la /sys/kernel/debug/
total 0
drwx-- 16   42 root 0 Jul  2 00:07 .
drwxr-xr-x  6 root root 0 Jul  2 00:07 ..
drwxr-xr-x  2 root root 0 Jul  2 00:07 acpi
drwxr-xr-x 32 root root 0 Jul 11 14:36 bdi
drwxr-xr-x  2 root root 0 Jul 13 11:51 bluetooth
drwxr-xr-x  4 root root 0 Jul  2 00:07 dri
drwxr-xr-x  2 root root 0 Jul  2 00:07 dynamic_debug
drwxr-xr-x  2 root root 0 Jul  2 00:07 extfrag
-r--r--r--  1 root root 0 Jul  2 00:07 gpio
drwxr-xr-x  3 root root 0 Jul  2 00:07 ieee80211
drwxr-xr-x  2 root root 0 Jul  2 00:07 kprobes
drwxr-xr-x  2 root root 0 Jul  2 00:07 kvm
drwxr-xr-x  2 root root 0 Jul  2 00:07 mce
drwxr-xr-x  2 root root 0 Jul  2 00:07 regmap
-rw-r--r--  1 root root 0 Jul  2 00:07 sched_features
-r--r--r--  1 root root 0 Jul  2 00:07 suspend_stats
drwxr-xr-x  5 root root 0 Jul  2 00:07 tracing
drwxr-xr-x  2 root root 0 Jul  2 00:07 usb
-r--r--r--  1 root root 0 Jul  2 00:07 wakeup_sources
drwxr-xr-x  2 root root 0 Jul  2 00:07 x86


 2) ownership and mode seems to be shared amoung all mount points,
resulting in the following unexpected behaviour:

nemi:/tmp# mount /sys/kernel/debug -o uid=42,mode=0700
nemi:/tmp# ls -ld /sys/kernel/debug
drwx-- 16 42 root 0 Jul  2 00:07 /sys/kernel/debug
nemi:/tmp# mount -t debugfs none /mnt/temp -o uid=0,mode=0755
nemi:/tmp# ls -ld /sys/kernel/debug
drwxr-xr-x 16 root root 0 Jul  2 00:07 /sys/kernel/debug


 3) ownership (but not mode?!) seems to be cached between mounts,
resulting in the following unexpected behaviour:

nemi:/tmp# mount /sys/kernel/debug -o uid=42,mode=0700
nemi:/tmp# ls -ld /sys/kernel/debug
drwx-- 16 42 root 0 Jul  2 00:07 /sys/kernel/debug
nemi:/tmp# umount /sys/kernel/debug
nemi:/tmp# grep debugfs /proc/mounts 
nemi:/tmp# grep debugfs /etc/fstab
debug   /sys/kernel/debug   debugfs defaults
nemi:/tmp# mount /sys/kernel/debug
nemi:/tmp# ls -ld /sys/kernel/debug
drwxr-xr-x 16 42 root 0 Jul  2 00:07 /sys/kernel/debug



These can all be considered minor glitches, but they sure confused me
the first time I hit them.



Bjørn



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

Bug#681465: CVE-2012-2845

[Moritz Muehlenhoff]

Package: exif
Severity: grave
Tags: security

CVE-2012-2845 (please see #681454 for the initial report) needs to be fixed
in exif rather than libexif.

This doesn't warrant a DSA, but you could still fix it through a stable point
update.

Cheers,
Moritz



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

Bug#681464: nemiver on powerpc : segfaults on startup

[Erik de Castro Lopo]

Package: nemiver
Version: 0.9.2-1
Severity: normal


Segfaults on startup on PowerPC.

Backtrace from GDB below:



Script started on Fri Jul 13 22:08:28 2012
$ gdb --args nemiver /bin/ls
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/bin/nemiver...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/nemiver /bin/ls
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
[New Thread 0xf7f30310 (LWP 1453)]
[New Thread 0xf3211310 (LWP 1455)]

Program received signal SIGSEGV, Segmentation fault.
_cairo_xlib_surface_add_glyph (pscaled_glyph=0xa318, font=0x10367d30, 
display=0xf7602800)
at 
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-xlib-render-compositor.c:1065
1065
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-xlib-render-compositor.c:
 No such file or directory.
(gdb) bt
#0  _cairo_xlib_surface_add_glyph (pscaled_glyph=0xa318, font=0x10367d30, 
display=0xf7602800)
at 
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-xlib-render-compositor.c:1065
#1  composite_glyphs (surface=0x10365378, op=CAIRO_OPERATOR_IN, 
_src=0x1036a6e0, src_x=0, src_y=0, dst_x=0, dst_y=0, info=)
at 
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-xlib-render-compositor.c:1357
#2  0x0e893c18 in composite_glyphs (compositor=, dst=, closure=, op=, src=,
src_x=, src_y=, dst_x=, 
dst_y=0, extents=0xa4b0, clip=0x10367b88)
at 
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-traps-compositor.c:2256
#3  0x0e895be0 in clip_and_composite (compositor=0xe914fb0, extents=0xa478, 
draw_func=0xe893bd4 , mask_func=0, draw_closure=0xa420, 
need_clip=1)
at 
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-traps-compositor.c:1038
#4  0x0e895e34 in _cairo_traps_compositor_glyphs (_compositor=0xe914fb0, 
extents=0xa478, scaled_font=0x10367d30, glyphs=, 
num_glyphs=15,
overlap=) at 
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-traps-compositor.c:2299
#5  0x0e83c1e8 in _cairo_compositor_glyphs (compositor=0xe914fb0, 
surface=0x10365378, op=, source=, 
glyphs=0x10365c08, num_glyphs=15,
scaled_font=0x10367d30, clip=) at 
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-compositor.c:246
#6  0x0e882d90 in _cairo_surface_show_text_glyphs (surface=0x10365378, 
op=CAIRO_OPERATOR_OVER, source=0xa858, utf8=0x0, utf8_len=0, 
glyphs=0x10365c08, num_glyphs=15,
clusters=, num_clusters=0, cluster_flags=0, 
scaled_font=0x10367d30, clip=0x103679b0)
at 
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-surface.c:2341
#7  0x0e888484 in _cairo_surface_offset_glyphs (surface=0x10365378, x=0, 
y=-418, op=CAIRO_OPERATOR_OVER, source=0xa858, scaled_font=0x10367d30, 
glyphs=,
num_glyphs=15, clip=0x10367b50) at 
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-surface-offset.c:296
#8  0x0e88907c in _cairo_surface_subsurface_glyphs (abstract_surface=, op=CAIRO_OPERATOR_OVER, source=0xbb20, glyphs=0xb328, 
num_glyphs=15,
scaled_font=, clip=) at 
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-surface-subsurface.c:223
#9  0x0e882d90 in _cairo_surface_show_text_glyphs (surface=0x1036a400, 
op=CAIRO_OPERATOR_OVER, source=0xbb20, utf8=0x0, utf8_len=0, 
glyphs=0xb328, num_glyphs=15,
clusters=, num_clusters=0, cluster_flags=0, 
scaled_font=0x10367d30, clip=0x10240e70)
at 
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-surface.c:2341
#10 0x0e8467ac in _cairo_gstate_show_text_glyphs (gstate=0x10365110, 
glyphs=, num_glyphs=15, info=)
at 
/build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo-gstate.c:1994
#11 0x0e835e60 in cairo_show_glyphs (cr=0x1008d768, glyphs=, 
num_glyphs=)
at /build/buildd-cairo_1.12.2-2-powerpc-TiPR0y/cairo-1.12.2/src/cairo.c:3315
#12 0x0ea04d0c in ?? () from /usr/lib/powerpc-linux-gnu/libpangocairo-1.0.so.0
#13 0x0ea05044 in ?? () from /usr/lib/powerpc-linux-gnu/libpangocairo-1.0.so.0
#14 0x0e9540b0 in pango_renderer_draw_glyphs () from 
/usr/lib/powerpc-linux-gnu/libpango-1.0.so.0
#15 0x0e954190 in pango_renderer_draw_glyph_item () from 
/usr/lib/powerpc-linux-gnu/libpango-1.0.so.0
#16 0x0e954ea8 in pango_renderer_draw_layout_line () from 
/usr/lib/powerpc-linux-gnu/libpango-1.0.so.0
#17 0x0e9550a4 in pango_renderer_draw_layout () from 
/usr/lib/powerpc-linux-gnu/libpango-1.0.so.0
#18 0x0ea05224

Bug#679235: animals! hey!

[Philipp Schafft]

reflum,

(CC to the bug so everybody stay informed.)

On Thu, 2012-07-12 at 19:55 +0200, Patrick Matthäi wrote:
> Am 12.07.2012 14:10, schrieb Philipp Schafft:
> > My next move is that I will release a new version within the next
> weeks
> > (I don't see a rush here as Debian is in freeze currently).

Ok, found a major legal bug so speeded this up.
There was wrong/missing license infos. I don't think it affects the
Debian package.

I just did a new release. You can find it on the homepage[0].

From the ChangeLog:
v. 201207131226 - Fri Jul 13 2012 14:26 CEST
* Changed ChangeLog format to RoarAudio Changelog Format.
* Allow answering "sure" to "Want to play again?".
* Updated legal infrastructure.
* Updated manpage.
* Updated Makefile.

[0] http://software.keep-cool.org/animals.html

-- 
Philipp.
 (Rah of PH2)


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

Bug#654851: unattended-upgrades: email notifications don't have "Content-Type:" header

[Michael Vogt]

On Fri, Jul 13, 2012 at 10:13:37AM +0300, Teodor MICU wrote:
> Hi,
> 
> There is an empty line between the headers that causes some headers
> (including Subject:) to be considered part of the message body.
> 
> | From: "root" 
> | Date: Fri, 13 Jul 2012 09:48:04 +0300
> | To: root@DOMAIN
> | Message-Id: <20120713064805.003CC179A9@mail.DOMAIN>
> |
> | MIME-Version: 1.0
> | Content-Type: text/plain; charset="utf-8"
> | Content-Transfer-Encoding: base64
> | Subject: unattended-upgrades result for 'frost.DOMAIN'

Indeed, sorry for that, should be fixed in bzr trunk, if testing goes
well I will upload today. It will use sendmail if available to set the
header and if not mail but without the header as there is no portable way
apparently to do that with mailx.

Cheers,
 Michael



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

Bug#680990: Diff does not show BOM difference.

[Santiago Vila]

On Mon, 9 Jul 2012, jmg wrote:

> Package: diff
> Version: 1:3.0-1

Please note that when reporting bugs, you should try the latest
version if possible. In this case, wheezy has version 3.2.

> Severity: normal
>
> When diff is used to compare two files which are identical line by
> line and a unique difference which is wether BOM is present or not
> to indicates UTF-8 encoding, diff does not indicate the good
> difference.

Please explain what do you mean by "does not indicate the good difference".

I have used this

#include 
int main() {
  printf("%c%c%c", 0xef,0xbb,0xbf);
  return 0;
}

to create a UTF8 BOM and then I've created two text files, one with
the BOM at the beginning and another one without it. This is what I
*see* when I make the diff:

1c1
< Hello.
---
> Hello.

but if I redirect the output to a file and use patch, the first file
becomes identical to the second file, so the diff is correct.

Are you reporting that BOM is invisible like spaces?
Why should we consider that as a bug in the "diff" program?
If it's invisible, blame the terminal, not diff!



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

Bug#681463: unblock: gyoto/0.0.3-5

[Thibaut Paumard]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package gyoto.

I attach a debdiff and explain the changes below.

1- Security Hardening Buld Flags Release Goal
   http://bugs.debian.org/680242

Fix: pass build flags explicitly to make. I had to reshuffle some
symbolic targets in debian/rules to make it work reliably. Could be made
cleaner, but I tried to keep changes to a minimum.

2- test suite failed on kfreebsd-any
   http://bugs.debian.org/679923

After checking, it appears that the "gyoto" executable from the gyoto
binary package fails to run on kfreebsd. However, the same functionality
is exposed to the Yorick interpreter by the yorick-gyoto package and
this binary package runs fine.

Fix:
 - disable building the gyoto binary package on kfreebsd;
 - don't let gyoto-dbg (or anything else) depend on it on kfreebsd;
 - disable the test suite on kfreebsd, which requires the gyoto
   executable to run.

3- test suite failed on some mips buildds
   http://bugs.debian.org/681452

After checking, it appears that this failure does not affect all the
machines. It may just be that the test suite is too expensive to run on
some smaller/slower buildds.

Fix: disable test suite on mips. I then tested manually the autobuilt
binaries, which run fine (although slowwwly) in my qemu installation.

4- yorick is waiting for yorick-gyoto
The yorick-full meta-package (src:yorick), already unblocked, is waiting
for yorick-gyoto to build on kfreebsd-* before it can migrate.
   http://release.debian.org/migration/testing.pl?package=yorick
Fixing the above-mentioned FTBFSes takes us halfway through to letting
yorick migrate. The other half is unblocking yp-svipc, already requested
here:
   http://bugs.debian.org/681314

Kind regards, Thibaut.

unblock gyoto/0.0.3-5
diff -Nru gyoto-0.0.3/debian/changelog gyoto-0.0.3/debian/changelog
--- gyoto-0.0.3/debian/changelog2012-06-25 20:03:10.0 +0200
+++ gyoto-0.0.3/debian/changelog2012-07-13 11:36:16.0 +0200
@@ -1,5 +1,44 @@
+gyoto (0.0.3-5) unstable; urgency=low
+
+  * skip test suite on mips as lucatelli fails on it (but it runs fine on
+other boxes). (Closes: 681452)
+
+ -- Thibaut Paumard   Fri, 13 Jul 2012 11:36:16 
+0200
+
+gyoto (0.0.3-4) unstable; urgency=low
+
+  * gyoto-dbg must not depend on gyoto on kfreebsd-*, else it is
+uninstallable on these archs.
+
+ -- Thibaut Paumard   Wed, 11 Jul 2012 14:30:02 
+0200
+
+gyoto (0.0.3-3) unstable; urgency=low
+
+  * debian/control Architectures fields should not be folded: previous
+upload led to missing binary packages for some archs.
+
+ -- Thibaut Paumard   Wed, 11 Jul 2012 13:02:34 
+0200
+
+gyoto (0.0.3-2) unstable; urgency=low
+
+  * Bug fix: "FTBFS on kfreebsd-i386 and kfreebsd-amd64 (test suite)",
+(Closes: #679923). The previous "fix" did not work at all. The library
+and the Yorick interface work fine, but not the stand-alone application.
+Disable the "gyoto" binary package and the test suite on kfreebsd-*.
+
+ -- Thibaut Paumard   Wed, 11 Jul 2012 11:20:09 
+0200
+
+gyoto (0.0.3-1+exp1) experimental; urgency=low
+
+  * Bug fix: "FTBFS on kfreebsd-i386 and kfreebsd-amd64 (test suite)"
+(Closes: #679923).
+  * Tentative bug fix: "don't rely on yorick to pass the fortified build
+flags" using patch fix_679923_kfreebsd_FTBFS (Closes: #680242).
+
+ -- Thibaut Paumard   Tue, 10 Jul 2012 10:50:50 
+0200
+
 gyoto (0.0.3-1) unstable; urgency=low
 
   * Initial release (Closes: #640809)
 
- -- Thibaut Paumard   Mon, 25 Jun 2012 20:03:10 
+0200
+ -- Thibaut Paumard   Fri, 22 Jun 2012 14:22:40 
+0200
diff -Nru gyoto-0.0.3/debian/control gyoto-0.0.3/debian/control
--- gyoto-0.0.3/debian/control  2012-06-22 14:21:54.0 +0200
+++ gyoto-0.0.3/debian/control  2012-07-11 14:29:51.0 +0200
@@ -12,7 +12,7 @@
 Homepage: http://gyoto.obspm.fr
 
 Package: gyoto
-Architecture: any
+Architecture: linux-any hurd-any
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: General relativistic ray-tracing
  Gyoto is a framework for computing geodesics in curved
@@ -41,7 +41,7 @@
 Architecture: any
 Section: debug
 Depends: libgyoto0 (= ${binary:Version}),
-gyoto (= ${binary:Version}),
+gyoto (= ${binary:Version}) [!kfreebsd-any],
 yorick-gyoto (= ${binary:Version}),
 ${misc:Depends}
 Description: debugging symbols for gyoto, libgyoto0 and yorick-gyoto
diff -Nru gyoto-0.0.3/debian/rules gyoto-0.0.3/debian/rules
--- gyoto-0.0.3/debian/rules2012-06-25 19:49:54.0 +0200
+++ gyoto-0.0.3/debian/rules2012-07-13 10:56:48.0 +0200
@@ -5,6 +5,8 @@
 # This has to be exported to make some magic below work.
 export DH_OPTIONS
 
+DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH)
+
 # Hardened flags
 DPKG_EXPORT_BUILDFLAGS = 1
 -include /usr/share/dpkg/buildflags.mk
@@ -33,17 +35,29 @@
dh_compress -i
dh_fixperms -i
 
-build-arch bu

Bug#681353: Pending fixes for bugs in the libconfig-model-perl package

[pkg-perl-maintainers]

tag 681353 + pending
thanks

Some bugs in the libconfig-model-perl package are closed in revision
49040e74d1272385c7735f08139722dd76cca9bf in branch 'master' by
Dominique Dumont

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libconfig-model-perl.git;a=commitdiff;h=49040e7

Commit message:

use patch from upstream to fix unsaved changes (Closes: #681353)




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

Bug#681462: redmine: Changeing of user/group role impossible

[Holger Rusch]

Package: redmine
Version: 1.4.4+dfsg1-1
Severity: normal

Dear Maintainer,

First:
I am also biten by #678515 and have switched ruby to 1.8 per
update-alternatives.
Redmine is runnig under passenger. I am running an actual fully updated
testing.

Problem:
If i want to change the role of a user/group for a project in
"../settings/members" after i press "Change" i get back a blank page.

production.log:
  Parameters: 
{"authenticity_token"=>"oFdFizI7jY0sK74MczCo0YK9ktKLdLt+mleRZMTgz/8=", 
"commit"=>"Change", "membership"=>{"role_ids"=>["3", "4", ""]}}

ActionController::MethodNotAllowed (Only get, put, and delete requests are 
allowed.):
  
/usr/lib/ruby/vendor_ruby/action_controller/routing/recognition_optimisation.rb:64:in
 `recognize_path'
  /usr/lib/ruby/vendor_ruby/action_controller/routing/route_set.rb:442:in 
`recognize'
  /usr/lib/ruby/vendor_ruby/action_controller/routing/route_set.rb:437:in `call'
  /usr/lib/ruby/vendor_ruby/action_controller/dispatcher.rb:87:in `dispatch'
  /usr/lib/ruby/vendor_ruby/action_controller/dispatcher.rb:121:in `_call'
  /usr/lib/ruby/vendor_ruby/action_controller/dispatcher.rb:130:in 
`build_middleware_stack'
  /usr/lib/ruby/vendor_ruby/active_record/query_cache.rb:29:in `call'
  /usr/lib/ruby/vendor_ruby/active_record/query_cache.rb:29:in `call'
  
/usr/lib/ruby/vendor_ruby/active_record/connection_adapters/abstract/query_cache.rb:34:in
 `cache'
  /usr/lib/ruby/vendor_ruby/active_record/query_cache.rb:9:in `cache'
  /usr/lib/ruby/vendor_ruby/active_record/query_cache.rb:28:in `call'
  
/usr/lib/ruby/vendor_ruby/active_record/connection_adapters/abstract/connection_pool.rb:361:in
 `call'
  /usr/lib/ruby/vendor_ruby/action_controller/string_coercion.rb:25:in `call'
  /usr/lib/ruby/vendor_ruby/rack/head.rb:9:in `call'
  /usr/lib/ruby/vendor_ruby/rack/methodoverride.rb:21:in `call'
  /usr/lib/ruby/vendor_ruby/action_controller/params_parser.rb:15:in `call'
  /usr/lib/ruby/vendor_ruby/action_controller/session/cookie_store.rb:99:in 
`call'
  /usr/lib/ruby/vendor_ruby/action_controller/failsafe.rb:26:in `call'
  /usr/lib/ruby/vendor_ruby/rack/lock.rb:15:in `call'
  /usr/lib/ruby/vendor_ruby/action_controller/dispatcher.rb:106:in `call'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/rack/request_handler.rb:96:in 
`process_request'
  
/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_request_handler.rb:516:in 
`accept_and_process_next_request'
  
/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_request_handler.rb:274:in 
`main_loop'
  
/usr/lib/ruby/vendor_ruby/phusion_passenger/classic_rails/application_spawner.rb:321:in
 `start_request_handler'
  
/usr/lib/ruby/vendor_ruby/phusion_passenger/classic_rails/application_spawner.rb:275:in
 `send'
  
/usr/lib/ruby/vendor_ruby/phusion_passenger/classic_rails/application_spawner.rb:275:in
 `handle_spawn_application'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/utils.rb:479:in `safe_fork'
  
/usr/lib/ruby/vendor_ruby/phusion_passenger/classic_rails/application_spawner.rb:270:in
 `handle_spawn_application'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server.rb:357:in 
`__send__'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server.rb:357:in 
`server_main_loop'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server.rb:206:in 
`start_synchronously'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server.rb:180:in `start'
  
/usr/lib/ruby/vendor_ruby/phusion_passenger/classic_rails/application_spawner.rb:149:in
 `start'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/spawn_manager.rb:219:in 
`spawn_rails_application'
  
/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server_collection.rb:132:in
 `lookup_or_add'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/spawn_manager.rb:214:in 
`spawn_rails_application'
  
/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server_collection.rb:82:in 
`synchronize'
  
/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server_collection.rb:79:in 
`synchronize'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/spawn_manager.rb:213:in 
`spawn_rails_application'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/spawn_manager.rb:132:in 
`spawn_application'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/spawn_manager.rb:275:in 
`handle_spawn_application'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server.rb:357:in 
`__send__'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server.rb:357:in 
`server_main_loop'
  /usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server.rb:206:in 
`start_synchronously'
  /usr/share/phusion-passenger/helper-scripts/passenger-spawn-server:99

Thanks.

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

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

Versions of packages redmine depends on:
ii  bu

Bug#555168: [Traduc] Bug#555168: Unclear license situation for (e)glibc locales provided by you

[Keld Simonsen]

I hereby grant all my locales to be licensed under GPL v2.

Best regards
Keld Simonsen

On Thu, Jun 14, 2012 at 02:29:23PM +0200, "Jean-Philippe Guérard" wrote:
> Le Mer 13 juin 2012 06:53, Christian PERRIER a écrit :
> > Quoting Helge Kreutzmann (deb...@helgefjell.de):
> >> Hello,
> >> you are listed as contact person/author of the following locale: fr_FR
> > I think Keld Simonsen's name is mentioned as the locale was based on one
> he wrote.
> > tra...@traduc.org is a collective address (see
> > http://traduc.org). Adding the internal organisational list to the CC
> field so that representatives of the traduc.org can give a stance in
> name of the organization.
> > PS: coucou, traduc.org..:-)...Bon, en gros, vous avez sûrement compris
> mais c'est vrai qu'il y a une action en cours actuellement, dans Debian,
> pour clarifier la licence des locales où celle-ci n'est pas claire. Je
> n'ai évidemment aucun doute sur les intentions de
> > traduc.org par rapport à la locale fr_FR (utiliser une licence libre),
> mais il faut que quelqu'un confirme cela, évidemment.
> > Ce serait quand même un peu ballot que Debian retire la locale
> > française de la libc. Je serais largement au chomage..:-)
> 
> The fr_FR was taken over by traduc.org in March 2008, and the update of
> this file have been discussed on the traduc mail list from
> January to March 2008 (http://listes.traduc.org/pipermail/traduc/).
> 
> At that time, the license was not discussed, as we were under the
> impression this file was part of the glibc and distributed under the same
> license.
> 
> The original author of this file is Keld Jørn Simonsen.
> 
> Provided that Keld Jørn Simonsen agree with this, we would be very happy
> to see this file officially put under a Free license. Using the same
> license as the glibc would be fine for us.
> 
> Hope that helps.
> 
> Best Regards.
> 
> -- 
> Jean-Philippe Guérard
> http://tigreraye.org
> 



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

Bug#681461: octave: Creation of packages directory will become obsolete, eventually

[Rafael Laboissiere]

Package: octave
Version: 3.6.2-3
Severity: normal

The problem underlying Bug#681064 has been fixed upstream:

http://hg.savannah.gnu.org/hgweb/octave/rev/a82fcd612c8f

This means that, once a new upstream version of Octave will be
released, that includes this patch, then the following line in
debian.octave-postinst will become obsolete: 

mkdir -p /usr/share/octave/packages

This bug report is just a reminder for us in the DOG.



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

Bug#681418: debugfs is a big security hole

[Ludwig Nussel]

Bjørn Mork wrote:
>  1) mode and owner is not propagated to files below the mount point:

That's intentional to keep things simple. If you can control the x bit
on the mount point then you can control who can reach files beneath.

>  2) ownership and mode seems to be shared amoung all mount points,
> resulting in the following unexpected behaviour:
>  3) ownership (but not mode?!) seems to be cached between mounts,
> resulting in the following unexpected behaviour:
> [...]
> These can all be considered minor glitches, but they sure confused me
> the first time I hit them.

Me too :-) debugfs is a special beast. It's a singleton filesystem. The
kernel itself mounts it at boot. When you mount it in userspace you
actually only expose what the kernel already has. Modifying the mount
options actually modifies the options of that single, already mounted
instance.

cu
Ludwig
-- 
 (o_   Ludwig Nussel
 //\
 V_/_  http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 
16746 (AG Nürnberg) 





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

Bug#681453: Split screen error comes back in 304.17

[Andreas Beckmann]

Hi Pjotr,

On 2012-07-13 11:33, Piotr Majkrzak wrote:
> I'm writig to You, because I'm affected with split screen error, which comes 
> back after pgrading from 295.33-2 to current 304.17-3. In cause of it my 
> 1366x768 screen is divided into 6 800x600 subscreens. As I remember few years 
> ago there was same error, which was casued by wrong monitor detection. My 
> monitor is internal LCD of Acer extensa 5635 painted with nvidia g105m 
> graphics card. Please do something with it

Please check the Nvidia forum and report this problem directly to
Nvidia. Their bug reporting instructions are at
http://www.nvnews.net/vbulletin/showthread.php?t=46678

Also try to find and add pointers to the "old" problem there.

Thanks.


Andreas



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

Bug#681460: xbrlapi: Modifier keys (alt,shift,control) don't work in X11

[Samuel Thibault]

Package: xbrlapi
Version: 4.4-4
Severity: important, upstream, fixed-upstream

This is just to document an issue being fixed in next upload.

With brltty 4.4, shortcuts typed from the braille keyboard (alt-f1,
alt-tab, etc.) do not work any more: all modifiers are actually not
working any more. This is because brltty 4.4 now transmits them another
way, which xbrlapi doesn't support yet. Upstream revision 6592 adds
support in xbrlapi.

Samuel

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

Kernel: Linux 3.0.4 (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

Versions of packages brltty depends on:
ii  libbrlapi0.5  4.4-4
ii  libc6 2.13-33
ii  libgpm2   1.20.4-6
ii  libicu48  4.8.1.1-8
ii  libncursesw5  5.9-9
ii  libtinfo5 5.9-9
ii  lsb-base  4.1+Debian7

Versions of packages brltty recommends:
ii  python  2.7.3~rc2-1

Versions of packages brltty suggests:
pn  brltty-speechd   
ii  brltty-x11   4.4-4
ii  console-braille  1.3

-- Configuration Files:
/etc/brltty/brl-sk-all.ktb changed:
title Seika
note The round keys to the left/right of the braille cells are named K1 and K8.
note The left/right ends of the left rocker are named K2 and K3.
note The long keys to the left/right of the center are named K4 and K5.
note The left/right ends of the right rocker are named K6 and K7.
bind !RoutingKey ROUTE
bind K1 FWINLT
bind K8 FWINRT
bind K2 LNUP
bind K3 LNDN
bind K2+K3 LNBEG
bind K6 FWINLTSKIP
bind K7 FWINRTSKIP
bind K6+K7 PASTE
bind K4 CSRTRK
bind K5 RETURN
bind K4+K5 CSRJMP_VERT
bind K6+K2 TOP_LEFT
bind K6+K3 BOT_LEFT
bind K7+K2 TOP
bind K7+K3 BOT
bind K4+K2 ATTRUP
bind K4+K3 ATTRDN
bind K5+K2 PRDIFLN
bind K5+K3 NXDIFLN
bind K4+K6 PRPROMPT
bind K4+K7 NXPROMPT
bind K5+K6 PRPGRPH
bind K5+K7 NXPGRPH
bind K1+K8+K2 CONTEXT+7 # RoutingKey -> PRINDENT
bind K1+K8+K3 CONTEXT+8 # RoutingKey -> NXINDENT
bind K1+K8+K4 CONTEXT+5 # RoutingKey -> SETLEFT
bind K1+K8+K5 CONTEXT+6 # RoutingKey -> DESCCHAR
bind K1+K8+K6 CONTEXT+9 # RoutingKey -> PRDIFCHAR
bind K1+K8+K7 CONTEXT+10 # RoutingKey -> NXDIFCHAR
bind K1+K8+K2+K6 CONTEXT+1 # RoutingKey -> CLIP_NEW
bind K1+K8+K2+K7 CONTEXT+2 # RoutingKey -> CLIP_ADD
bind K1+K8+K3+K6 CONTEXT+3 # RoutingKey -> COPY_LINE
bind K1+K8+K3+K7 CONTEXT+4 # RoutingKey -> COPY_RECT
bind K1+K2 HELP
bind K1+K3 LEARN
bind K1+K4 PREFLOAD
bind K1+K5 PREFSAVE
bind K1+K6 PREFMENU
bind K1+K7 INFO
bind K8+K2 DISPMD
bind K8+K3 FREEZE
bind K8+K6 SIXDOTS
bind K8+K7 SKPIDLNS
context menu
bind K1 FWINLT
bind K8 FWINRT
bind K2 MENU_PREV_ITEM
bind K3 MENU_NEXT_ITEM
bind K6 MENU_PREV_SETTING
bind K7 MENU_NEXT_SETTING
bind K4 MENU_FIRST_ITEM
bind K5 MENU_LAST_ITEM
context 1
bind !RoutingKey CLIP_NEW
context 2
bind !RoutingKey CLIP_ADD
context 3
bind !RoutingKey COPY_LINE
context 4
bind !RoutingKey COPY_RECT
context 5
bind !RoutingKey SETLEFT
context 6
bind !RoutingKey DESCCHAR
context 7
bind !RoutingKey PRINDENT
context 8
bind !RoutingKey NXINDENT
context 9
bind !RoutingKey PRDIFCHar
context 10
bind !RoutingKey NXDIFCHar


-- debconf information:
* brltty/braille-driver: VisioBraille [20/40]
* brltty/override: true
* brltty/speech-driver: No Speech
* brltty/device: /dev/ttyS0
* brltty/text-table: text.de

-- 
Samuel Thibault 
* c is away : cuisine; bouffe
 oh, moi je fais plutôt cuisine & bouffe en fait :)
 oui c'est vrai, certains font cuisine && bouffe (juste au cas où... ;-))
 ( cuisine && bouffe ) || restau
 voire ((cuisine && bouffe) || restau) & apéritif
 -+- #ens-mim -+-



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

Bug#669376: Please enable perl regex support

[David Schmitt]

Hi,

for the more complex spelunking expeditions, PCRE support would be very 
welcome!



Best Regards, David



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

Bug#681459: libopenjpeg2: SEGVs with broken files

[Jonas Smedegaard]

Package: libopenjpeg2
Version: 1.3+dfsg-4.4
Severity: important
Tags: security patch

I just noticed the following security-related bugfix getting applied to
the convenience copy of openjpeg in ghostscript, which might be relevant
to Debian:

http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=29a16f

More info here:

http://bugs.ghostscript.com/show_bug.cgi?id=693171

 - Jonas



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