Bug#776456: kdesvn: Opening of files in kdiff3 for conflict resolution fails because of duplicated paths

[Vincas Dargis]

Package: kdesvn
Version: 1.5.5-4.1
Severity: normal

Dear Maintainer,

I have tree conflict in my repository, and to fix that I've:
* opened checkout directory using kdesvn
* right-clicked on conflicted file, selected "Resolve conflcit"
* KDiff3 opened, but with error message like this:

Opening of these files failed:

 -
/home/vincas/code/cpp/branches/debuggui/GPTServerTemp/home/vincas/code/cpp/branches/debuggui/GPTServerTemp/server.cpp
..merge-left.r2511
 -
/home/vincas/code/cpp/branches/debuggui/GPTServerTemp/home/vincas/code/cpp/branches/debuggui/GPTServerTemp/server.cpp
..merge-right.r2536
 -
/home/vincas/code/cpp/branches/debuggui/GPTServerTemp/home/vincas/code/cpp/branches/debuggui/GPTServerTemp/server.cpp.working


"cat /proc/$(pgrep kdiff3)/cmdline" gives me this (formatted for better
readibility):

kdiff3
/home/vincas/code/cpp/branches/debuggui/GPTServerTemp//home/vincas/code/cpp/branches/debuggui/GPTServerTemp/server.cpp
..merge-left.r2511
/home/vincas/code/cpp/branches/debuggui/GPTServerTemp//home/vincas/code/cpp/branches/debuggui/GPTServerTemp/server.cpp
..merge-right.r2536
/home/vincas/code/cpp/branches/debuggui/GPTServerTemp//home/vincas/code/cpp/branches/debuggui/GPTServerTemp/server.cpp.working
-o/home/vincas/code/cpp/branches/debuggui/GPTServerTemp/server.cpp

>From this I assume that it's kdesvn bug, not kdiff3 - provided paths are
duplicated, "/home/vincas..." part mentioned twice per path.

Side note - I'm using subversion from backports:

apt-cache policy subversion
subversion:
  Installed: 1.8.10-1~bpo70+1
  Candidate: 1.8.10-1~bpo70+1
  Version table:
 *** 1.8.10-1~bpo70+1 0
100 http://ftp.litnet.lt/debian/ wheezy-backports/main amd64 Packages
100 /var/lib/dpkg/status
 1.6.17dfsg-4+deb7u8 0
500 http://ftp.litnet.lt/debian/ wheezy/main amd64 Packages
500 http://security.debian.org/ wheezy/updates/main amd64 Packages




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

Kernel: Linux 3.2.0-4-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 kdesvn depends on:
ii  kde-runtime 4:4.8.4-2
ii  kdesvn-kio-plugins  1.5.5-4.1
ii  libapr1 1.4.6-3+deb7u1
ii  libaprutil1 1.4.1-3
ii  libc6   2.13-38+deb7u7
ii  libgcc1 1:4.7.2-5
ii  libkdecore5 4:4.8.4-4+deb7u1
ii  libkdeui5   4:4.8.4-4+deb7u1
ii  libkio5 4:4.8.4-4+deb7u1
ii  libkparts4  4:4.8.4-4+deb7u1
ii  libnepomuk4 4:4.8.4-4+deb7u1
ii  libnepomukutils44:4.8.4-4+deb7u1
ii  libqt4-dbus 4:4.8.2+dfsg-11
ii  libqt4-network  4:4.8.2+dfsg-11
ii  libqt4-sql  4:4.8.2+dfsg-11
ii  libqt4-svg  4:4.8.2+dfsg-11
ii  libqt4-xml  4:4.8.2+dfsg-11
ii  libqtcore4  4:4.8.2+dfsg-11
ii  libqtgui4   4:4.8.2+dfsg-11
ii  libsoprano4 2.7.6+dfsg.1-2wheezy1
ii  libstdc++6  4.7.2-5
ii  libsvn1 1.8.10-1~bpo70+1
ii  libsvnqt6   1.5.5-4.1

Versions of packages kdesvn recommends:
ii  graphviz  2.26.3-14+deb7u2
ii  kompare   4:4.8.4+dfsg-1

Versions of packages kdesvn suggests:
ii  kdiff3   0.9.96-4
pn  khelpcenter  

-- 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#776455: libencode-eucjpms-perl: problem in package description formatting of table-like text

[Beatrice Torracca]

Package: libencode-eucjpms-perl
Severity: minor

Hi,

the package description now includes a table-like section. Since (by Debian 
Policy) the lines that do not start with a space can be reformatted (wrapped) 
the current table is rendered in a terrible form right now, as you can see in 
the Debian page of the package:

https://packages.debian.org/sid/libencode-eucjpms-perl

the solution is simply to prefix each line of the table with a space like so:

 Canonical Alias  Description
 
 eucJP-ms  qr/\beuc-?jp-?ms$/i   eucJP-ms
   qr/\beuc-?jp-?win$/i
 cp51932   qr/\bcp51932$/i Windows Codepage 51932
 cp50220   Windows Codepage 50220
 cp50221   Windows Codepage 50221
 

the lines will be then treated as not to be wrapped and shown correctly 
everywhere.

I have also another suggestion. The last paragraph states "To find out how to 
use this module in detail, see Encode.". I would suggest to specify where 
"Encode" is cause it is not clear in this context (man page, web documentation, 
some doc file installed...).

Thanks,

beatrice


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

Bug#770009: Backtrace for the hang

[Bastien ROUCARIES]

Le 28 janv. 2015 08:00, "roucaries bastien" <
roucaries.bastien+deb...@gmail.com> a écrit :
>
>
> Le 27 janv. 2015 22:15, "Vincent Fourmond"  a écrit :
>
> >
> >   I've run the build on the MIPS portebox. It hangs on the first SVG
> > to PNG conversion. Here is a full backtrace. The process is for now
> > stopped on the porterbox; I think I can leave it for some hours more
> > at least, if other information could be useful.
>
> Smell like an openmp bug ny memory they are a enviroment variable to
disable openmp. We could try

OMP_thread_limit=1
> >
> >   Hope it helps,
> >
> >   Vincent
> >

Bug#776277: Solution

[Vincas Dargis]

I have recreated self-signed certificate with propper CN inside VisualSVN
(by default it was computer hostname), and now --non-interactive
--trust-server-cert is working as expected (accepts without prompting or
error).

Self-signed is also untrusted as one with non matching hostname, but maybe
it's SVN policy to ignore "--trust-server-cert" for hostname missmatch
specificlally as for "more dangerous" case?

Bug#776257: Fails to apply patch with dangling symlink

[Martin Pitt]

Michael Biebl [2015-01-26  1:55 +0100]:
> the latest update of patch broke the systemd package and causes it to
> FTBFS:

BTW, at least glibc is also affected, and judging by the recent slew
of autopkgtest failures in Ubuntu there's some more. We really need to
get this fixed fast.

Thanks,

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


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

Bug#770009: Backtrace for the hang

[roucaries bastien]

Le 27 janv. 2015 22:15, "Vincent Fourmond"  a écrit :
>
>   I've run the build on the MIPS portebox. It hangs on the first SVG
> to PNG conversion. Here is a full backtrace. The process is for now
> stopped on the porterbox; I think I can leave it for some hours more
> at least, if other information could be useful.

Smell like an openmp bug ny memory they are a enviroment variable to
disable openmp. We could try
>
>   Hope it helps,
>
>   Vincent
>

Bug#776454: tor-resolve should better handle .onion addresses

[Russell Coker]

Package: tor
Version: 0.2.5.10-1
Severity: normal

$ tor-resolve zp7zwyd5t3aju57m.onion
Jan 28 17:38:42.055 [warn] Got SOCKS5 status response '4': host is unreachable
Jan 28 17:38:42.055 [warn] zp7zwyd5t3aju57m.onion is a hidden service; those 
don't have IP addresses. To connect to a hidden service, you need to send the 
hostname to Tor; we suggest an application that uses SOCKS 4a.

The above output is informative, but not particularly useful for the case of
scripts.

https://www.howtoforge.com/anonymous-ssh-sessions-with-tor

The above web site gives an example of how to use tor which btraks when used
with .onion addresses.  One way to solve this would be for tor-resolve to
give "zp7zwyd5t3aju57m.onion" on stdout and the warning message on stderr,
that would inform users but work in the desired manner with scripts.

A small change to tor-resolve will make it work better with existing documented
practice and make it work with future use for .onion addresses in cases where
admins only care about non-onion addresses now.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages tor depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.19-13
ii  libevent-2.0-5  2.0.21-stable-2
ii  libseccomp2 2.1.1-1
ii  libssl1.0.0 1.0.1k-1
ii  lsb-base4.1+Debian13+nmu1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages tor recommends:
ii  logrotate3.8.7-1+b1
pn  tor-geoipdb  
pn  torsocks 

Versions of packages tor suggests:
pn  apparmor-utils 
pn  mixmaster  
pn  obfsproxy  
pn  polipo | privoxy   
pn  socat  
pn  tor-arm
pn  xul-ext-torbutton  

-- 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#776349: grass-gui: wx gui tries to load images from wrong location

[Ambrose Andrews]

That workaround works for me,

Many thanks Bas.

  -AA.


On 28 January 2015 at 08:04, Sebastiaan Couwenberg  wrote:
> Control: tags -1 pending
>
> On 01/27/2015 07:55 PM, Sebastiaan Couwenberg wrote:
>> For some reason the symlinks from the images under /usr/share to
>> /usr/lib are missing.
>
>> The symlinks are included in the package, but not on the filesystem
>> after installation:
>
>> This problem is limited to the directory symlinks, the symlinks for
>> individual files are working fine.
>
> The problem is the switch to symlinks in 6.4.4-1, when upgrading from an
> earlier version the existing directories are not replaced by the symlinks.
>
> I've commited a fix using dpkg-maintscript-helper to replace the
> directories with symlinks on upgrade. And aim to get it included in the
> first stable update of jessie.
>
> As a workaround in the mean time you can purge the grass-gui package and
> install it (and the dependencies removed along with grass-gui) again.
>
> Kind Regards,
>
> Bas
>
> --
>  GPG Key ID: 4096R/E88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
>



-- 
Ambrose Andrews
LPO box 8274 ANU Acton ACT 0200 Australia
http://www.vrvl.net/~ambrose/
mailto:ambr...@vrvl.net
voip:+61_261112936
mobile:+61_415544621
irc:{swiftirc|freenode|oftc}:znalo
skype:znalo7
xmpp:ambr...@jabber.fsfe.org|ambro...@member.fsf.org
diaspora:zn...@diasp.eu
99D8 6FF6 190D BF09 BA55 1E5F DF42 552D 9A90 14D7


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

Bug#775788: Build-Attempted of icedove on powerpc-unicamp-01

[Carsten Schoenert]

Hello Wouter,

the build of icedove 31.4.0-2 is broken again on powerpc-unicamp-01 (as
expected). Could you please reschedule the build on another powerpc
buildd again?
Christoph has fixed a RC bug [6] with this version of icedove and by
this it is important for us to get this version of icedove into testing.

Thanks!

(I don't have cut up the old mail because I added the RC bug about FTBFS
on powerpc [7] to the CC list of this mail.)

Am 22.01.2015 um 21:20 schrieb Carsten Schoenert:
> Hello Wouter,
> 
> Am 20.01.2015 um 00:58 schrieb Wouter Verhelst:
>>> Could this problem depends on the autobuilder powerpc-unicamp-01?
>>
>> Possibly, but I don't think it's a configuration issue on the buildd or
>> some such. All buildd hosts these days use throwaway chroots; that means
>> that if the issue occurs, it *should* also occur in a clean chroot.
>>
>> Looking at the buildd log, we see:
>>
>> Compile-time page size does not divide the runtime one.
>>
>> which to me smells like an incorrect assumption either in jemalloc or in
>> the code that uses jemalloc. But I'm not sure; I don't know what the
>> message means.
> 
> In the past from time to time we had build issues related to jemalloc
> [1], but Mozilla has worked on the code, probably initiated by Mike
> Hommey [3-5].
> This message is produced by a simple check if the pagesize is different
> to internal result check. On powerpc (and other platforms as well) the
> source is setting a definition of MALLOC_STATIC_SIZES to 1 because the
> code should be compiled as compile-time constants for performance
> reasons. This means later that some things are hardcoded and hasn't to
> detect by the CPU and the system, but the jemalloc compiler is proofing
> later the environment [2] before it will translate the code. But exactly
> here on this on the buildd this check was failing.
> 
> But how the jemalloc thing is exactly working ... I also don't know. :)
> 
>>> And finally could you schedule a rebuild of icedove on another
>>> autobuilder?
>>
>> We could randomly disable icedove on some buildd hosts and not on others
>> if it really FTBFS due to hardware, but I'd prefer to see the root cause
>> found and (hopefully) fixed.
>>
>> We don't currently know what the problem is, though.
> 
> I don't know if you have done some buildd's disabled for the icedove
> packages, but last night a build on host 'parry' was successful!
> That's because Christoph was meaning that there could be something
> different to the porter box. It would be interesting to found out what
> the differences are to the other buildd.
> 
> [1] 
> https://sources.debian.net/src/icedove/31.4.0-1/mozilla/memory/mozjemalloc/jemalloc.c/
> [2] 
> https://sources.debian.net/src/icedove/31.4.0-1/mozilla/memory/mozjemalloc/jemalloc.c/#L1085
> [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708331
> [4] https://bugzilla.mozilla.org/show_bug.cgi?id=825165
> [5] https://bugzilla.mozilla.org/show_bug.cgi?id=840242

[6] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770008
[7] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775788

-- 
Regards
Carsten Schoenert



signature.asc
Description: OpenPGP digital signature

Bug#776453: unblock: jasper/1.900.1-debian1-2.4

[Salvatore Bonaccorso]

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

Hi Release Team,

Could you please unblock the package jasper, the changelog reads as

> jasper (1.900.1-debian1-2.4) unstable; urgency=high
> 
>   * Non-maintainer upload.
>   * Add 07-CVE-2014-8157.patch patch.
> CVE-2014-8157: dec->numtiles off-by-one check in jpc_dec_process_sot().
> (Closes: #775970)
>   * Add 08-CVE-2014-8158.patch patch.
> CVE-2014-8158: unrestricted stack memory use in jpc_qmfb.c (Closes: 
> #775970)
> 
>  -- Salvatore Bonaccorso   Thu, 22 Jan 2015 17:09:24 +0100

and fixes two CVEs which were already addressed in DSA-3138-1:

 https://www.debian.org/security/2015/dsa-3138

unblock jasper/1.900.1-debian1-2.4

Attached is also the full debdiff for the version in unstable.

Thanks in advance!

Regards,
Salvatore
diff -Nru jasper-1.900.1-debian1/debian/changelog jasper-1.900.1-debian1/debian/changelog
--- jasper-1.900.1-debian1/debian/changelog	2014-12-21 10:31:44.0 +0100
+++ jasper-1.900.1-debian1/debian/changelog	2015-01-22 18:35:26.0 +0100
@@ -1,3 +1,14 @@
+jasper (1.900.1-debian1-2.4) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Add 07-CVE-2014-8157.patch patch.
+CVE-2014-8157: dec->numtiles off-by-one check in jpc_dec_process_sot().
+(Closes: #775970)
+  * Add 08-CVE-2014-8158.patch patch.
+CVE-2014-8158: unrestricted stack memory use in jpc_qmfb.c (Closes: #775970)
+
+ -- Salvatore Bonaccorso   Thu, 22 Jan 2015 17:09:24 +0100
+
 jasper (1.900.1-debian1-2.3) unstable; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff -Nru jasper-1.900.1-debian1/debian/patches/07-CVE-2014-8157.patch jasper-1.900.1-debian1/debian/patches/07-CVE-2014-8157.patch
--- jasper-1.900.1-debian1/debian/patches/07-CVE-2014-8157.patch	1970-01-01 01:00:00.0 +0100
+++ jasper-1.900.1-debian1/debian/patches/07-CVE-2014-8157.patch	2015-01-22 18:35:26.0 +0100
@@ -0,0 +1,19 @@
+Description: CVE-2014-8157: dec->numtiles off-by-one check in jpc_dec_process_sot()
+Origin: vendor, http://pkgs.fedoraproject.org/cgit/jasper.git/tree/jasper-CVE-2014-8157.patch
+Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1179282
+Bug-Debian: https://bugs.debian.org/775970
+Forwarded: not-needed
+Author: Salvatore Bonaccorso 
+Last-Update: 2015-01-22
+
+--- a/src/libjasper/jpc/jpc_dec.c
 b/src/libjasper/jpc/jpc_dec.c
+@@ -489,7 +489,7 @@ static int jpc_dec_process_sot(jpc_dec_t
+ 		dec->curtileendoff = 0;
+ 	}
+ 
+-	if (JAS_CAST(int, sot->tileno) > dec->numtiles) {
++	if (JAS_CAST(int, sot->tileno) >= dec->numtiles) {
+ 		jas_eprintf("invalid tile number in SOT marker segment\n");
+ 		return -1;
+ 	}
diff -Nru jasper-1.900.1-debian1/debian/patches/08-CVE-2014-8158.patch jasper-1.900.1-debian1/debian/patches/08-CVE-2014-8158.patch
--- jasper-1.900.1-debian1/debian/patches/08-CVE-2014-8158.patch	1970-01-01 01:00:00.0 +0100
+++ jasper-1.900.1-debian1/debian/patches/08-CVE-2014-8158.patch	2015-01-22 18:35:26.0 +0100
@@ -0,0 +1,336 @@
+Description: CVE-2014-8158: unrestricted stack memory use in jpc_qmfb.c
+Origin: vendor, http://pkgs.fedoraproject.org/cgit/jasper.git/tree/jasper-CVE-2014-8158.patch
+Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1179298
+Bug-Debian: https://bugs.debian.org/775970
+Forwarded: not-needed
+Author: Salvatore Bonaccorso 
+Last-Update: 2015-01-22
+
+--- a/src/libjasper/jpc/jpc_qmfb.c
 b/src/libjasper/jpc/jpc_qmfb.c
+@@ -306,11 +306,7 @@ void jpc_qmfb_split_row(jpc_fix_t *a, in
+ {
+ 
+ 	int bufsize = JPC_CEILDIVPOW2(numcols, 1);
+-#if !defined(HAVE_VLA)
+ 	jpc_fix_t splitbuf[QMFB_SPLITBUFSIZE];
+-#else
+-	jpc_fix_t splitbuf[bufsize];
+-#endif
+ 	jpc_fix_t *buf = splitbuf;
+ 	register jpc_fix_t *srcptr;
+ 	register jpc_fix_t *dstptr;
+@@ -318,7 +314,6 @@ void jpc_qmfb_split_row(jpc_fix_t *a, in
+ 	register int m;
+ 	int hstartcol;
+ 
+-#if !defined(HAVE_VLA)
+ 	/* Get a buffer. */
+ 	if (bufsize > QMFB_SPLITBUFSIZE) {
+ 		if (!(buf = jas_alloc2(bufsize, sizeof(jpc_fix_t {
+@@ -326,7 +321,6 @@ void jpc_qmfb_split_row(jpc_fix_t *a, in
+ 			abort();
+ 		}
+ 	}
+-#endif
+ 
+ 	if (numcols >= 2) {
+ 		hstartcol = (numcols + 1 - parity) >> 1;
+@@ -360,12 +354,10 @@ void jpc_qmfb_split_row(jpc_fix_t *a, in
+ 		}
+ 	}
+ 
+-#if !defined(HAVE_VLA)
+ 	/* If the split buffer was allocated on the heap, free this memory. */
+ 	if (buf != splitbuf) {
+ 		jas_free(buf);
+ 	}
+-#endif
+ 
+ }
+ 
+@@ -374,11 +366,7 @@ void jpc_qmfb_split_col(jpc_fix_t *a, in
+ {
+ 
+ 	int bufsize = JPC_CEILDIVPOW2(numrows, 1);
+-#if !defined(HAVE_VLA)
+ 	jpc_fix_t splitbuf[QMFB_SPLITBUFSIZE];
+-#else
+-	jpc_fix_t splitbuf[bufsize];
+-#endif
+ 	jpc_fix_t *buf = splitbuf;
+ 	register jpc_fix_t *srcptr;
+ 	register jpc_fix_t *dstptr;
+@@ -386,7 +374,6 @@ void jpc_qmfb_split_col(jpc_fix_t *a, in
+ 	register int m;
+ 	int hstartcol;
+ 
+-#if !defined(HAVE_VLA)
+ 	/* Get a buffer. */
+ 	if (bufsize > QMFB_SPLITBUFSIZE)

Bug#776452: ITP: python-nacl -- Python bindings to libsodium

[Tristan Seligmann]

Package: wnpp
Severity: wishlist
Owner: Tristan Seligmann 

* Package name: python-nacl
  Version : 0.2.3
  Upstream Author : Python Cryptography Authority
* URL : https://github.com/pyca/pynacl
* License : Apache License 2.0
  Programming Lang: Python
  Description : Python bindings to libsodium

PyNaCl is a Python binding to the Networking and Cryptography library (in the
form of libsodium), a crypto library with the stated goal of improving
usability, security and speed.


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

Bug#776450: grub-xen-host: does not work with PVH

[Gedalya]

Package: grub-xen-host
Version: 2.02~beta2-20
Severity: wishlist

Dear Maintainer,

When trying to create a domU with pvgrub2 and pvh=1, I get:

Parsing config from dnsmaster.cfg
xc: error: panic: xc_dom_core.c:877: xc_dom_parse_image: unsupported
feature requested: Invalid configuration
libxl: error: libxl_dom.c:407:libxl__build_pv: xc_dom_parse_image
failed: No such file or directory
libxl: error: libxl_create.c:1022:domcreate_rebuild_done: cannot
(re-)build domain: -3

This works fine without pvh=1.
Most probably pvgrub2 just doesn't support PVH, but it would be so nice
if this was added.

Thanks,

Gedalya


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

Bug#776449: ITP: 3270font -- monospaced font based on IBM 3270 terminals

[Adam Borowski]

Package: wnpp
Severity: wishlist
Owner: Adam Borowski 

* Package name: 3270font (fonts-3270)
  Version : 1.1
  Upstream Author : Ricardo Bánffy 
* URL : https://github.com/rbanffy/3270font
* License : BSD3
  Programming Lang: fontforge .sfd
  Description : monospaced font based on IBM 3270 terminals

 This font is derived from the x3270 font, which, in turn, was translated
 from the one in Georgia Tech's 3270tool, which was itself hand-copied
 from a 3270 terminal.
 .
 While looking reasonably close to its bitmap ancestors, this is a vector
 font that looks good at any size.  Its recommended use is, obviously, a
 text terminal, same as nearly half a century ago.

There's a bitmap version in the archive already: (xfonts-x3270-misc,
non-free), although PCF fonts are not configured by default for use with any
toolkits from this millenium.  Ricardo Bánffy's version is free, works with
modern technology, and has a number of improvements.

The conversion from bitmap used an eight-direction algorithm rather than the
usual squares, fitting the font's design (lots of diagonals).  There's also
a number of manual tweaks after that.

This package is a dependency of cool-retro-term, although a terminal font
has no lack of usefullness on its own.


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

Bug#776050: Bug#776237: xen-hypervisor-4.4-amd64: kernel panic on dom0 boot

[Gedalya]

On 01/27/2015 03:17 AM, Ian Campbell wrote:
>> Could #776237 be related to #776050?
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776050
> It's quite possible and the coincidence of the issue arising in ckt4
> makes me think it most likely is.
>
> Lets assume it is for now, I've merged the two bugs. If the issue
> persists after the fix for #776050 is uploaded we can always unmerge.
>
> Ian.
>

Yup, looks OK with 3.16.7-ckt4-2.


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

Bug#776448: xen dom0: "xen:balloon: reserve_additional_memory: add_memory() failed: -17"

[Gedalya]

Package: src:linux
Version: 3.16.7-ckt4-2
Severity: normal

Dear Maintainer,

After a clean boot everything is OK, but as soon as I reboot a domU for
the first time, I start getting these lines in dmesg:

xen:balloon: reserve_additional_memory: add_memory() failed: -17

And they keep repeating forever, quite frequently.

This seems to have been fixed in ubuntu:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3dcf63677d4eb7fdfc13290c8558c301d2588fe8


# xl dmesg
(XEN) Xen version 4.4.1 (Debian 4.4.1-6) (wa...@debian.org) (gcc (Debian
4.9.2-5) 4.9.2) debug=n Thu Dec 11 14:57:34 UTC 2014
(XEN) Bootloader: GRUB 2.02~beta2-20
(XEN) Command line: placeholder dom0_mem=768M,max:768M ucode=scan

And I have autoballoon="off" in /etc/xen/xl.conf



-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc
version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt4-2 (2015-01-27)

** Command line:
placeholder root=/dev/mapper/rvg0-dom0_80_rootfs ro quiet

** Not tainted

** Kernel log:
[   46.806552] device vif4.1 entered promiscuous mode
[   46.806719] device vif4.0 entered promiscuous mode
[   46.808018] IPv6: ADDRCONF(NETDEV_UP): vif4.1: link is not ready
[   46.808201] IPv6: ADDRCONF(NETDEV_UP): vif4.0: link is not ready
[   48.080581] xen-blkback:ring-ref 8, event-channel 15, protocol 1
(x86_64-abi) persistent grants
[   48.096044] xen-blkback:ring-ref 9, event-channel 16, protocol 1
(x86_64-abi) persistent grants
[   48.104120] xen-blkback:ring-ref 10, event-channel 17, protocol 1
(x86_64-abi) persistent grants
[   48.111257] xen-blkback:ring-ref 11, event-channel 18, protocol 1
(x86_64-abi) persistent grants
[   48.131462] vif vif-4-0 vif4.0: Guest Rx ready
[   48.131495] IPv6: ADDRCONF(NETDEV_CHANGE): vif4.0: link becomes ready
[   48.131532] breth1: port 4(vif4.0) entered forwarding state
[   48.131535] breth1: port 4(vif4.0) entered forwarding state
[   48.136706] vif vif-4-1 vif4.1: Guest Rx ready
[   48.136734] IPv6: ADDRCONF(NETDEV_CHANGE): vif4.1: link becomes ready
[   48.136753] breth0: port 5(vif4.1) entered forwarding state
[   48.136756] breth0: port 5(vif4.1) entered forwarding state
[   52.524439] device vif5.0 entered promiscuous mode
[   52.526017] IPv6: ADDRCONF(NETDEV_UP): vif5.0: link is not ready
[   52.810327] xen-blkback:ring-ref 8, event-channel 8, protocol 2
(x86_32-abi)
[   52.820391] xen-blkback:ring-ref 9, event-channel 9, protocol 2
(x86_32-abi)
[   52.832214] vif vif-5-0 vif5.0: Guest Rx ready
[   52.832257] IPv6: ADDRCONF(NETDEV_CHANGE): vif5.0: link becomes ready
[   52.832304] breth0: port 6(vif5.0) entered forwarding state
[   52.832308] breth0: port 6(vif5.0) entered forwarding state
[   58.840587] device vif6.0 entered promiscuous mode
[   58.842141] IPv6: ADDRCONF(NETDEV_UP): vif6.0: link is not ready
[   58.842798] device vif6.1 entered promiscuous mode
[   58.844263] IPv6: ADDRCONF(NETDEV_UP): vif6.1: link is not ready
[   60.145988] vif vif-6-0 vif6.0: Guest Rx ready
[   60.146026] IPv6: ADDRCONF(NETDEV_CHANGE): vif6.0: link becomes ready
[   60.146070] breth1: port 5(vif6.0) entered forwarding state
[   60.146074] breth1: port 5(vif6.0) entered forwarding state
[   60.147731] xen-blkback:ring-ref 8, event-channel 15, protocol 1
(x86_64-abi) persistent grants
[   60.158149] vif vif-6-1 vif6.1: Guest Rx ready
[   60.158178] IPv6: ADDRCONF(NETDEV_CHANGE): vif6.1: link becomes ready
[   60.158199] breth0: port 7(vif6.1) entered forwarding state
[   60.158202] breth0: port 7(vif6.1) entered forwarding state
[   60.160099] xen-blkback:ring-ref 2308, event-channel 24, protocol 1
(x86_64-abi) persistent grants
[   60.173611] xen-blkback:ring-ref 2309, event-channel 25, protocol 1
(x86_64-abi) persistent grants
[   60.181874] xen-blkback:ring-ref 2310, event-channel 26, protocol 1
(x86_64-abi) persistent grants
[   65.525950] device vif7.1 entered promiscuous mode
[   65.527393] IPv6: ADDRCONF(NETDEV_UP): vif7.1: link is not ready
[   65.528520] device vif7.0 entered promiscuous mode
[   65.529955] IPv6: ADDRCONF(NETDEV_UP): vif7.0: link is not ready
[   66.770492] xen-blkback:ring-ref 8, event-channel 9, protocol 1
(x86_64-abi) persistent grants
[   66.783509] xen-blkback:ring-ref 9, event-channel 10, protocol 1
(x86_64-abi) persistent grants
[   66.869486] vif vif-7-0 vif7.0: Guest Rx ready
[   66.869528] IPv6: ADDRCONF(NETDEV_CHANGE): vif7.0: link becomes ready
[   66.869567] breth0: port 8(vif7.0) entered forwarding state
[   66.869571] breth0: port 8(vif7.0) entered forwarding state
[   66.872315] vif vif-7-1 vif7.1: Guest Rx ready
[   66.872341] IPv6: ADDRCONF(NETDEV_CHANGE): vif7.1: link becomes ready
[   66.872363] breth1: port 6(vif7.1) entered forwarding state
[   66.872366] breth1: port 6(vif7.1) entered forwarding state
[   71.443566] device vif8.0 entered promiscuous mode
[   71.444965] IPv6: ADDRCONF(NETDEV_UP): vif8.0: link is not re

Bug#776233: openclipart: Some images, particularly PNGs, are far too large

[Martin Kelly]

Hi,

Thank you for the bug report; I quite agree with you. I am no longer the
openclipart maintainer (openclipart is currently orphaned), but whoever
becomes maintainer next should definitely look at this.

Thanks,
Martin

On 01/25/2015 10:47 AM, David Wright wrote:
> Package: openclipart
> Version: 1:0.18+dfsg-14
> Severity: normal
> 
> Dear Maintainer,
> 
> Some of the images in this package are far too large. For example
> -rw-r--r-- 1 3769493 Jun  4  2012 microchip_v.2_havok_redh_01.png
> -rw-r--r-- 1 3055767 Jun  4  2012 salad_mateya_01.png
> -rw-r--r-- 1 2829335 Jun  6  2012 stop_sign_right_font_mig_.png
> -rw-r--r-- 1 2819817 Jun  5  2012 stop_sign_miguel_s_nchez_.png
> -rw-r--r-- 1 1831764 Jun  4  2012 apple_mateya_01.png
> -rw-r--r-- 1 1639377 Jun  4  2012 paprika_mateya_01.png
> -rw-r--r-- 1 1593583 Jun  4  2012 cake_mateya_01.png
> -rw-r--r-- 1 1564746 Jun  4  2012 bread_mateya_01.png
> -rw-r--r-- 1 1535656 Jun  4  2012 pasta_mateya_01.png
> -rw-r--r-- 1 1481671 Jun  4  2012 egg_mateya_01.png
> -rw-r--r-- 1 1237372 Jun  4  2012 cheese_mateya_01.png
> -rw-r--r-- 1 1198050 Jun  4  2012 salami_mateya_01.png
> -rw-r--r-- 1 1086920 Jun  4  2012 banana_mateya_01.png
> -rw-r--r-- 1 1035599 Jun  4  2012 milk_mateya_01.png
> 
> Looking inside:
> /usr/share/openclipart/png/computer/microchip_v.2_havok_redh_01.png PNG 
> 16000x14464
> /usr/share/openclipart/png/signs_and_symbols/stop_sign_miguel_s_nchez_.png 
> PNG 20990x29700
> 
> At 100dpi, a stop sign that large would completely block the alley behind my 
> house!
> 
> I have visited the site https://openclipart.org/ and found some of these 
> images.
> Downloading the largest of the three sizes available there for the microchip 
> gives
> -rw-r--r-- 1 442072 Jan 25 10:22 Anonymous-microchip-v.2.png
> (2381x2112 pixels).
> 
> The effect on a laptop with a 1.8GHz twin processor and 2GB memory running
> X and the fvwm window manager is that everything stops for several minutes,
> including the clock display and, worse, the mouse, which means you have to
> be careful not to click anywhere because when the click action happens, the
> mouse might be anywhere on the screen after it has played catch-up.
> 
> Please replace the large images with smaller versions. If large PNGs are
> required, they can be generated from the svg files.
> 
> Cheers,
> David.
> 
> -- System Information:
> Debian Release: 7.8
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 3.2.0-4-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 openclipart depends on:
> ii  openclipart-libreoffice  1:0.18+dfsg-14
> ii  openclipart-png  1:0.18+dfsg-14
> ii  openclipart-svg  1:0.18+dfsg-14
> 
> openclipart recommends no packages.
> 
> openclipart 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#404163: Granule documentation license

[Riley Baird]

Hi Vlad,

That's great! Thanks for getting back so quickly! I've bumped up the
version and added the :
http://libertybsd.net/granule/granule-manual-en-1.1.1.tar.gz

Debian is using the 1.4.0-7 release. Most of the bugs which I am fixing
are specific to Debian. However, there are some which may be of interest
to upstream:

- A Swedish translation has been made
  https://bugs.debian.org/361081

- Building with gcc4.8 and -fpermissive has been fixed

http://sources.debian.net/src/granule/1.4.0-7-2/debian/patches/01-fix-template-with-permissive.diff/

- A menu file and an xpm icon have been created
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737922

- configure.in is being depreciated. It should be renamed to configure.ac
  https://lintian.debian.org/tags/deprecated-configure-filename.html

- You don't need to specify the encoding key in .desktop entries anymore
  https://lintian.debian.org/tags/desktop-entry-contains-encoding-key.html

- Some keywords could be added to the .desktop entry
  https://lintian.debian.org/tags/desktop-entry-lacks-keywords-entry.html

- To comply with policy, I'm going to make a basic manpage for granule.
I haven't done this yet, though.

- Someone has reported a bug with Debian in which they have made granule
segfault. I'm not sure how to fix this, though.
  https://bugs.debian.org/402210

- While not mandatory, for security reasons Debian recommends that
upstreams use GPG signatures to verify releases.
  https://lintian.debian.org/tags/debian-watch-may-check-gpg-signature.html

Thanks!

Riley

On 28/01/15 09:31, vlg wrote:
> Hi Riley,
> 
> The license is GNU Free Documentation License, Version 1.2 or any later
> version.
> 
> If you can add it yourself to the documentation, that would be very
> helpful as I have not touched it in 10 years.
> Here is the license text:
> 
> Copyright (c) 2005 Vladislav Grinchenko
> 
> Permission is granted to copy, distribute and/or modify this document
> under the terms of the GNU Free Documentation License, Version 1.2 or
> any later version published by the Free Software Foundation; with no
> Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You
> may obtain a copy of the GNU Free Documentation License from the Free
> Software Foundation by visiting their Web site or by writing to: Free
> Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
> 02111-1307, USA.
> 
> BTW, which version of granule are you fixing for debian?  The last
> public release was back in Sep 1 2008 Rel 1.4.0.
> Is that the one?
> 
> Please, let me know what you have fixed so that I make a maintenance
> release.
> 
> thanks,
> --Vlad Grinchenko
> 
> On Wed, 2015-01-28 at 07:14 +1100, Riley Baird wrote:
> 
>> Hi!
>>
>> I'm fixing some bugs for your "granule" program in Debian. Someone
>> requested that I add your documentation to the package. However, I can't
>> seem to find the license of the documentation, and Debian requires a
>> license before I can package it.
>>
>> Can you please provide a free license for the documentation?
>>
>> Yours thankfully,
>>
>> Riley Baird
> 
> 
> 


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

Bug#775319:

[lachlan-00]

This behaviour is also present on the kernel in experimental

user@lachp:~$ uname -a
Linux lachp 3.18.0-trunk-amd64 #1 SMP Debian 3.18.3-1~exp1 (2015-01-18) x86_64 
GNU/Linux

Bug#776447: browser-plugin-gnash: Gnash doesn't work and doesn't consider dependency at control file

[Mohsen Pahlevanzadeh]

Package: browser-plugin-gnash
Version: 0.8.11~git20140708-3+b2
Severity: important

Dear Maintainer,

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

Unfortunately, My gnash doesn't work and can't play I read in Arch wiki to 
have to install gstreamer0.10-ffmpeg, I try to install it, and Its dependency 
doesn't exist on sid repo, i download from stable repo and one of them can't 
install. 
I reported bug at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776189
By the way , The given depency of gstreamer0.10-ffmpeg which has not been 
installed completely, is libavcodec-extra-53 .
So, my gnash plugin doesn't work on my iceweasel doesn't play any flash.

--Regards
Mohsen  

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


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages browser-plugin-gnash depends on:
ii  gnash 0.8.11~git20140708-3+b2
ii  libboost-iostreams1.55.0  1.55.0+dfsg-3
ii  libc6 2.19-13
ii  libgcc1   1:4.9.2-10
ii  libglib2.0-0  2.42.1-1
ii  libstdc++64.9.2-10

browser-plugin-gnash recommends no packages.

Versions of packages browser-plugin-gnash suggests:
pn  browser-plugin-lightspark  

-- 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#776446: ITP: liblinux-fd-perl -- Linux specific special filehandles

[Christopher Hoskin]

Package: wnpp
Owner: Christopher Hoskin 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org

* Package name: liblinux-fd-perl
  Version : 0.011
  Upstream Author : Leon Timmermans 
* URL : https://metacpan.org/release/Linux-FD
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Linux specific special filehandles

Linux::FD provides you Linux specific special file handles. These are

* Event filehandles
* Signal filehandles
* Timer filehandles

These allow you to use conventional polling mechanisms to wait a large variety 
of events.


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

Bug#775536: [Secure-testing-team] Bug#775536: CVE-2014-9447

[Michael Gilbert]

On Mon, Jan 26, 2015 at 3:24 AM, Kurt Roeckx wrote:
> On Sun, Jan 25, 2015 at 09:00:59PM -0500, Michael Gilbert wrote:
>> control: tag -1 patch, pending
>>
>> Hi,
>>
>> I've uploaded an nmu fixing this issue to delayed/5.  Let me know if I
>> should delay longer.  Please see attached.
>
> There is no reason to delay it.

Have you done manual binary uploads to work around the failing buildd
architectures in the past?
https://buildd.debian.org/status/package.php?p=elfutils&suite=unstable

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#776388: chromium does not start at all

[Michael Gilbert]

control: severity -1 normal
control: retitle -1 chromium: should conflict with libgl1-mesa-swx11

On Tue, Jan 27, 2015 at 10:13 AM, Santiago Vila wrote:
> The only "special" thing about my system is that 3D acceletarion does
> not work properly and I have to use libgl1-mesa-swx11 instead of
> libgl1-mesa-glx (see Bug#763890).

Do any opengl applications actually work as expected with swx11?  I
tried minetest and it too didn't start.

I'm happy to add a conflicts post-jessie, but there are an incredible
number of other opengl applications just as likely to be incompatible
with swx11, so each cannot possibly be release critical.

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#776445: mbuffer -P# frequently hangs with very short input

[jepler]

Package: mbuffer
Version: 20140310-3
Severity: important
Tags: upstream

Dear Maintainer,

I traced a failure in my homebrewed backup system to a bug in mbuffer.
Intermittely, a backup would hang; strace showed that mbuffer was
waiting forever printing the statistic
in @  0.0 KiB/s, out @  0.0 KiB/s,  0.0 KiB total, buffer   0% full

I eventually determined that the following command would reproduce the
problem almost every time:
$ echo | taskset -c 1 mbuffer -P50

In this case, mbuffer should exit essentally immediately.

I believe that the problem has something to do with the way mbuffer uses
threads.  By not using "taskset -c 1", the problem manifests more
rarely, though still more than 1 in 50 times.

The bug seems to exist in unmodified upstream mbuffer-20141227 as well.

Curiously, the bug does not exist or does not manifest nearly as readily
on FreeBSD 9.2 with unmodified upstream mbuffer-20141227.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mbuffer depends on:
ii  libc6  2.19-13
ii  libmhash2  0.9.9.9-7

mbuffer recommends no packages.

mbuffer 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#776443: sphinx: please make output reproducible

[Chris Lamb]

Source: sphinx
Version: 1.2.3+dfsg-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain randomness
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that sphinx is generating documentation that is not repoducible.

For example, its output includes non-deterministic memory references
such as:

   <__main__.A at 0x7f68cb685710>

In addition, various generated (objects.inv, searchindex.js,
translations) do not output their keys in a determinstic order,
resulting in further randomness.

The attached patch attempts to remedy these issues. Once applied, many
packages that use sphinx--but alas not sphinx itself yet!--can be built
reproducibly in our current experimental
framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/sphinx/builders/html.py b/sphinx/builders/html.py
index 9c039e3..f489a35 100644
--- a/sphinx/builders/html.py
+++ b/sphinx/builders/html.py
@@ -269,7 +269,7 @@ class StandaloneHTMLBuilder(Builder):
 # html_domain_indices can be False/True or a list of index names
 indices_config = self.config.html_domain_indices
 if indices_config:
-for domain in self.env.domains.itervalues():
+for domain in sorted(self.env.domains.itervalues()):
 for indexcls in domain.indices:
 indexname = '%s-%s' % (domain.name, indexcls.name)
 if isinstance(indices_config, list):
@@ -808,7 +808,7 @@ class StandaloneHTMLBuilder(Builder):
 compressor = zlib.compressobj(9)
 for domainname, domain in self.env.domains.iteritems():
 for name, dispname, type, docname, anchor, prio in \
-domain.get_objects():
+sorted(domain.get_objects()):
 if anchor.endswith(name):
 # this can shorten the inventory by as much as 25%
 anchor = anchor[:-len(name)] + '$'
diff --git a/sphinx/ext/autodoc.py b/sphinx/ext/autodoc.py
index 423f921..721fbb4 100644
--- a/sphinx/ext/autodoc.py
+++ b/sphinx/ext/autodoc.py
@@ -60,7 +60,6 @@ class DefDict(dict):
 
 identity = lambda x: x
 
-
 class Options(dict):
 """A dict/attribute hybrid that returns None on nonexisting keys."""
 def __getattr__(self, name):
@@ -975,7 +974,8 @@ class FunctionDocumenter(DocstringSignatureMixin, 
ModuleLevelDocumenter):
 argspec = getargspec(self.object.__init__)
 if argspec[0]:
 del argspec[0][0]
-args = inspect.formatargspec(*argspec)
+args = inspect.formatargspec(*argspec,
+ formatvalue=lambda x: '=' + safe_repr(x))
 # escape backslashes for reST
 args = args.replace('\\', '')
 return args
@@ -1030,7 +1030,8 @@ class ClassDocumenter(ModuleLevelDocumenter):
 return None
 if argspec[0] and argspec[0][0] in ('cls', 'self'):
 del argspec[0][0]
-return inspect.formatargspec(*argspec)
+return inspect.formatargspec(*argspec,
+ formatvalue=lambda x: '=' + safe_repr(x))
 
 def format_signature(self):
 if self.doc_as_attr:
@@ -1229,7 +1230,8 @@ class MethodDocumenter(DocstringSignatureMixin, 
ClassLevelDocumenter):
 argspec = getargspec(self.object)
 if argspec[0] and argspec[0][0] in ('cls', 'self'):
 del argspec[0][0]
-args = inspect.formatargspec(*argspec)
+args = inspect.formatargspec(*argspec,
+ formatvalue=lambda x: '=' + safe_repr(x))
 # escape backslashes for reST
 args = args.replace('\\', '')
 return args
diff --git a/sphinx/search/__init__.py b/sphinx/search/__init__.py
index bd95ecc..760b137 100644
--- a/sphinx/search/__init__.py
+++ b/sphinx/search/__init__.py
@@ -268,13 +268,13 @@ class IndexBuilder(object):
 if fn in fn2index:
 rv[k] = fn2index[fn]
 else:
-rv[k] = [fn2index[fn] for fn in v if fn in fn2index]
+rv[k] = sorted([fn2index[fn] for fn in v if fn in 
fn2index])
 return rvs
 
 def freeze(self):
 """Create a usable data structure for serializing."""
-filenames = self._titles.keys()
-titles = self._titles.values()
+filenames = sorted(self._titles.keys())
+titles = sorted(self._titles.values())
 fn2index = dict((f, i) for (i, f) in enumerate(filenames))
 terms, title_terms = self.get_terms(fn2index)
 
diff --git a/sphinx/util/inspect.py b/sphinx/util/inspect.py
index cdbfea7..e04f1fa 100644
--- a/sphinx/util/inspect.py
+++ b/sphinx/util/i

Bug#776444: ITP: libdata-serializer-sereal-perl -- Creates bridge between Data::Serializer and Sereal

[Christopher Hoskin]

Package: wnpp
Owner: Christopher Hoskin 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org

* Package name: libdata-serializer-sereal-perl
  Version : 1.05
  Upstream Author : James Rouzier 
* URL : https://metacpan.org/release/Data-Serializer-Sereal
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Creates bridge between Data::Serializer and Sereal

Data::Serializer::Sereal is a bridge between Data::Serializer and Sereal


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

Bug#773319: pre-approval: unblock: sudo/1.8.10p3-1.1; possibly sudo/1.8.11p2-1.1?

[Michael Gilbert]

On Tue, Jan 27, 2015 at 4:24 AM, Christian Kastner wrote:
> Control: tags -1 - moreinfo
>
> Hi,
>
> On 2015-01-17 20:38, Ivo De Decker wrote:
>> Don't remove the moreinfo tag from this bug when the upload enters t-p-u
>> (unless you have other info to add to the discussion). Leave it there for at
>> least 5 days. After that, remove the moreinfo tag from this bug and let us
>> know whether you had any reports about the upload (good or bad). We will
>> review the situation at that point.
>
> sudo 1.8.10p3-1+deb8u1 was uploaded to t-p-u on 2015-01-19. In the week
> since then, no new bugs were reported, nor have I become aware of any
> other issues.

There is a new sudo RC bug #776137 (not related to this issue).  That
also needs fixing before an unblock will likely be granted.

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#762330: Is libjsoncpp still active maintained?

[Peter Spiess-Knafl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I am currently in discussion with the upstream author:

https://github.com/open-source-parsers/jsoncpp/issues/147

ABI compatibility looks terrible.

On 01/27/2015 12:57 PM, Martin Quinson wrote:
> On Tue, Jan 27, 2015 at 11:41:49AM +, Peter Spiess-Knafl
> wrote:
>> The actual maintainer seems unresponsive. I contacted him 2
>> months ago and pinged again now, no luck so far.
>> 
>> Can I adopt it, if there is no RFA? What if the current
>> maintainer does not answer at all?
>> 
>> Anyway I will start packaging current 0.7.x. And maybe the latest
>> 1.3 for experimental.
>> 
>> Would you be able to review/sponsor it, if it is done?
> 
> I'm affraid I'm really overloaded right now. But if you come up
> with a repackaging of libjsoncpp, we'll find a solution. There is
> quite a few reverse dependencies (afaik), so we will find someone
> to review and sponsor your packaging. I will have a very bad time
> helping you packaging the stuff, though.
> 
> If the maintainer is MIA, then we can upload the new versions as
> NMU or even move to a team maintenance, don't stress. 2 months is
> already something, but I'd prefer to not hijack the package before
> another 2 months period, to give enough time to the maintainer to
> react.
> 
> I'm not really aware of what are the good practices in this domain
> for debian. You should ask to some QA mailing list, maybe.
> 
> Bye, Mt.
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJUyEUYAAoJEAwiV48qkHlkytUH/iY9Q0HPFfXny7gUX3O3MB6b
fvNKpRQkw++vaup3Dw61npvSbkHvDZuJGxpALAYx1k2vmW6et1iCTKfvFgdgZNan
yxPOGaliIoMFA08tda9c54pI2+cNw6eQAD0wC1g1bub3pvkOhV5ea/SL6YlCLJyI
irEDu2b2MhcMJ5CRtaDfS4ZfsK38KVKBmRIDuZ6Tn5zvOwRmlWddWqInVyMjFTdW
sRQ2SAytXZLQrZ7AYHjRemve5Lpe/vtoTtJ0bsNMK1TnGpKGssEXow3HwCbCIj5B
RTsrfLS5k3cAXCuRh1yUC7zlVFdQLbIMImCG7nY/H6CLc8bb7U3aZq4rV+u8fe0=
=Mzdt
-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#776095: wheezy-pu: package sudo/1.8.5p2-1+nmu2

[Andreas Beckmann]

Followup-For: Bug #776095
Control: tag -1 - confirmed

Hi,

further testing revealed that the fix in 1.8.7-1 (that I backported)
was insufficient for sudo-ldap since in lenny sudo and sudo-ldap
created different /etc/sudoers, but only the one from sudo/lenny was
covered so far.
An updated diff is attached, adding more md5sums.
It also contains some git adjustments.

There is not much point in fixing this in jessie, since that would only
help on this unsupported upgrade path:

  lenny -> squeeze -> jessie

i.e. skipping over wheezy.
(But since there are other issues with sudo and the patch is pretty
straightforward, the fix may end up in jessie anyway.)

Regarding the version number, the following would probably work,too:

  1.8.5p2-1.2+deb7u2


Andreas
diff -Nru sudo-1.8.5p2/debian/changelog sudo-1.8.5p2/debian/changelog
--- sudo-1.8.5p2/debian/changelog	2013-03-01 06:18:08.0 +0100
+++ sudo-1.8.5p2/debian/changelog	2015-01-28 02:10:56.0 +0100
@@ -1,3 +1,12 @@
+sudo (1.8.5p2-1+nmu2) wheezy; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport from 1.8.7-1: "recognize lenny and squeeze unmodified sudoers" to
+avoid dpkg questions about modified conffiles on upgrades to wheezy.
+(Closes: #660594)
+
+ -- Andreas Beckmann   Wed, 28 Jan 2015 02:07:46 +0100
+
 sudo (1.8.5p2-1+nmu1) unstable; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff -Nru sudo-1.8.5p2/debian/control sudo-1.8.5p2/debian/control
--- sudo-1.8.5p2/debian/control	2012-06-28 20:06:35.0 +0200
+++ sudo-1.8.5p2/debian/control	2015-01-28 02:10:56.0 +0100
@@ -4,8 +4,8 @@
 Maintainer: Bdale Garbee 
 Build-Depends: debhelper (>= 7), libpam0g-dev, libldap2-dev, libsasl2-dev, libselinux1-dev [linux-any], autoconf, autotools-dev, bison, flex
 Standards-Version: 3.9.3
-Vcs-Git: git://git.gag.com/debian/sudo
-Vcs-Browser: http://git.gag.com/?p=debian/sudo
+Vcs-Git: git://anonscm.debian.org/collab-maint/sudo.git -b wheezy
+Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/sudo.git
 
 Package: sudo
 Architecture: any
diff -Nru sudo-1.8.5p2/debian/gbp.conf sudo-1.8.5p2/debian/gbp.conf
--- sudo-1.8.5p2/debian/gbp.conf	2012-06-28 20:06:35.0 +0200
+++ sudo-1.8.5p2/debian/gbp.conf	2015-01-28 02:10:56.0 +0100
@@ -8,7 +8,7 @@
 # the default branch for upstream sources:
 upstream-branch = upstream
 # the default branch for the debian patch:
-debian-branch = master
+debian-branch = wheezy
 # the default tag formats used:
 #upstream-tag = upstream/%(version)s
 #debian-tag = debian/%(version)s
diff -Nru sudo-1.8.5p2/debian/sudo-ldap.preinst sudo-1.8.5p2/debian/sudo-ldap.preinst
--- sudo-1.8.5p2/debian/sudo-ldap.preinst	2012-06-28 20:06:35.0 +0200
+++ sudo-1.8.5p2/debian/sudo-ldap.preinst	2015-01-28 02:10:56.0 +0100
@@ -8,7 +8,9 @@
 
   if [ -e "$SUDOERS" ]; then
 md5sum="$(md5sum $SUDOERS | sed -e 's/ .*//')"
-if [ "$md5sum" = "c5dab0f2771411ed7e67d6dab60a311f" ]; then
+if [ "$md5sum" = "c310ef4892a00cca8134f6e4fcd64b6d" ] ||  #lenny/sudo
+   [ "$md5sum" = "4f29c034a4229544ffdd9168a14f6cde" ] ||  #lenny/sudo-ldap
+   [ "$md5sum" = "c5dab0f2771411ed7e67d6dab60a311f" ]; then   #squeeze
 	# move unchanged sudoers file to avoid conffile question
 mv "$SUDOERS" "$SUDOERS.pre-conffile"
 fi
diff -Nru sudo-1.8.5p2/debian/sudo.preinst sudo-1.8.5p2/debian/sudo.preinst
--- sudo-1.8.5p2/debian/sudo.preinst	2012-06-28 20:06:35.0 +0200
+++ sudo-1.8.5p2/debian/sudo.preinst	2015-01-28 02:10:56.0 +0100
@@ -8,7 +8,9 @@
 
   if [ -e "$SUDOERS" ]; then
 md5sum="$(md5sum $SUDOERS | sed -e 's/ .*//')"
-if [ "$md5sum" = "c5dab0f2771411ed7e67d6dab60a311f" ]; then
+if [ "$md5sum" = "c310ef4892a00cca8134f6e4fcd64b6d" ] ||  #lenny/sudo
+   [ "$md5sum" = "4f29c034a4229544ffdd9168a14f6cde" ] ||  #lenny/sudo-ldap
+   [ "$md5sum" = "c5dab0f2771411ed7e67d6dab60a311f" ]; then   #squeeze
 	# move unchanged sudoers file to avoid conffile question
 mv "$SUDOERS" "$SUDOERS.pre-conffile"
 fi

Bug#776442: backportpackage: doesn't follow conventions on Debian

[Samuel Bronson]

Package: ubuntu-dev-tools
Version: 0.143
Severity: normal

Dear Maintainer,

The "backportpackage" doesn't appear to follow the
backports.debian.org conventions properly: it uses a strange version
numbering scheme, rather than doing what it says on
, namely:

  * Append "~bpo${debian_release}+${build_int}" to the version number,
e.g. "1.2.3-4" now becomes "1.2.3-4~bpo60+1", or for native
packages, "1.2.3" becomes "1.2.3~bpo60+1".

Also, it seems that it should ideally check what version's in the
target distro/backports already and pass it to dpkg-builpackage after
"-v":

  * Include all changelog entries since the last version on
debian-backports or since stable if it's the first version. You
should do this by passing "-v" to dpkg-buildpackage. Eg: "debuild
-v0.7.5-2", where "0.7.5-2" is the version in stable. If the
package wasn't in stable or backports before you don't have
include the changelog entrys (but you are free to do so).

Though, honestly, that would not have helped me much because I had to
unpack the package anyway in order to build it with debuild -- I don't
really feel the need to use a chroot for a private build targetting
the release I'm on ...

-- Thanks,
Samuel Bronson

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

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

Versions of packages ubuntu-dev-tools depends on:
ii  binutils   2.22-8+deb7u2
ii  dctrl-tools2.22.2
ii  devscripts 2.12.6+deb7u2
ii  diffstat   1.55-3
ii  distro-info0.10
ii  dpkg-dev   1.16.15
ii  lsb-release4.1+Debian8+deb7u1
ii  perl   5.14.2-21+deb7u2
ii  python 2.7.3-4+deb7u1
ii  python-apt 0.8.8.2
ii  python-debian  0.1.21
ii  python-distro-info 0.10
ii  python-httplib20.7.4-2+deb7u1
ii  python-launchpadlib1.9.12-2
ii  python-lazr.restfulclient  0.12.0-2+deb7u1
ii  python2.6  2.6.8-1.1
ii  python2.7  2.7.3-6+deb7u2
ii  sudo   1.8.5p2-1+nmu1

Versions of packages ubuntu-dev-tools recommends:
ii  bzr 2.6.0~bzr6526-1
ii  bzr-builddeb2.8.4
ii  ca-certificates 20130119+deb7u1
ii  cowdancer   0.70
ii  debian-archive-keyring  2014.3~deb7u1
ii  debian-keyring  2013.04.21
ii  debootstrap 1.0.48+deb7u2
ii  dput0.9.6.3+nmu2
ii  genisoimage 9:1.1.11-2
ii  libwww-perl 6.04-1
ii  lintian 2.5.30+deb8u2~bpo70+1
ii  patch   2.6.1-3
ii  pbuilder0.213
ii  perl-modules5.14.2-21+deb7u2
ii  python-dns  2.3.6-1+deb7u1
ii  python-gnupginterface   0.3.2-9.1
ii  python-soappy   0.12.0-4
ii  quilt   0.60-2
ii  reportbug   6.4.4+deb7u1

Versions of packages ubuntu-dev-tools suggests:
pn  ipython
ii  python 2.7.3-4+deb7u1
ii  python-simplejson  2.5.2-1
pn  qemu-user-static   

-- 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#776005: general: After finished the installation, I rebooted and the initialization has been stopped

[Riley Baird]

I'm not sure - sorry. I have noticed, however, that you forgot to CC the
bug. I've just done that now, so hopefully someone else will know.

On 24/01/15 23:54, Fco. Javier Fdez. Serrador wrote:
> No, I cannot it because the keyboard does not start. I started with
> Advanced Options --> Debian GNU/Linux (recovery mode).
> Then, as root, I do a exit, and then it start the rest OK greeen, and
> then start LXDE.
> 
> 
> 2015-01-22 21:04 GMT+01:00 Riley Baird
> :
>>> The initialization is stoped and the system does not do anything. I have to 
>>> do
>>> a hard reboot, and select the emergency bootup.
>>
>> Does it work when you use the "sysvinit" option?
> 
> 
> 


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

Bug#775661: [775661] additional info to "odd completion candidates"

[lumin]

I extracted the lines of python code below,
 which contribute to this issue.

:)
Thanks.

foo.py
---
|#!/usr/bin/python3.4
|# -*- Coding: UTF-8 -*-
|
|for i in range (3):
|   with open ("linux" + "\n." + str(i), "w+") as f:
|   f.write(" ")


-- 
 .''`.
: :' :
`. `' 
  `-  


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

Bug#775661: [775661] additional info to "odd completion candidates"

[lumin]

I'm sorry to reply so late.

In fact, these 3 files were generated from one of my python scripts.

-rw-r--r-- 1 x x 201K Jan 18 10:13 linux?.0
-rw-r--r-- 1 x x 113K Jan 18 10:13 linux?.1
-rw-r--r-- 1 x x 151K Jan 18 10:13 linux?.2

And I then found that, the "?" displayed in filename field denotes '\n'.
at the beginning I tried to fix the issue in my script:

f = open (filename.replace('?', ''), 'w+') [0]

but it doesn't work. however another replace action

f = open (filename.replace('\n', ''), 'w+') [1]

really kills that odd character.

thank you,
Ville Skyttä
Peter Cordes
for looking into this issue.

[0] where "filename" is a string object, the method "replace" does
replacement in the string.
[1] means delete all the newline character.
-- 
 .''`.
: :' :
`. `' 
  `-  


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

Bug#776428: tracker.debian.org: Add a link to the Security Bug Tracker

[Paul Wise]

On Wed, Jan 28, 2015 at 6:30 AM, Frederic MASSOT wrote:

> Can you add a link to the Security Bug Tracker ?

Packages with security issues already have action items that link to
the security tracker. Is there anything more you would like to see
added? Please give an example package and explanation of what is
missing from the tracker page.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#776441: harden-nids: Alternative to snort is not NIDS software

[Javier Fernández-Sanguino Peña]

Source: harden
Version: 0.1.38+nmu1
Severity: important
Tags: patch

The harden-nids package claims to provide a network intrusion detection upon
installation but depends on: 'snort | ntop'

Snort is a network intrusion detection program, but ntop is not. Ntop is a
network traffic probe that makes it possible to do traffic analysis but it 
does not have any capabilities to detect malicious network traffic either
through behavioural or signature-based mechanisms (an upstream does not claim
it to).

Ntop does not comply with the package description definition either: " A
network intrusion detection system is a tool that analyzes network packets and
logs anomalies or known crack attempts. "

I would suggest the package to remove ntop and include 'suricata' instead which
*is* a network intrusion system. Attached is a patch that does just that.

I'm setting the severity to 'important' since currently, in testing, Snort is
not available (due to a removal from the Release Managers in December) and
users installing this package currently in testing (and possibly in the
'jessie' release) would be just installing 'ntop' and not really an NIDS.

In that way, the package description would be completely misleading.


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

Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- control.orig	2015-01-28 02:06:09.0 +0100
+++ control	2015-01-28 02:06:36.0 +0100
@@ -111,7 +111,7 @@
 
 Package: harden-nids
 Architecture: all
-Depends: snort | ntop
+Depends: snort | suricata
 Recommends: logcheck
 Description: Harden a system by using a network intrusion detection system
  This package helps you to install a network intrusion detection system.

Bug#776343: tecnoballz: Lack of a --no-verbose option

[Celelibi]

2015-01-27 17:36 UTC+01:00, Markus Koschany :
> On Tue, 27 Jan 2015 03:13:16 +0100 Celelibi  wrote:
>> Package: tecnoballz
>> Version: 0.93.1-2
>> Severity: wishlist
>>
>> Hello again :),
>>
>> When tecnoballz has been launched with --verbose option, it is recorded
>> and every subsequent run will be verbose. The only way I found to
>> disable the verbose option is by editing by hand the config file.
>>
>> Actually, I'd even question the relevance of saving this option. It's
>> not a user preference like the language or the user names. It's more
>> like a one-time usage to debug something.
>>
>> Regards,
>> Celelibi
>
> Hello,
>
> I agree with you that saving the verbose option is not really useful.
> Indeed the only way to revert --verbose is by editing the config file.
> Nevertheless this looks like an intended design decision. I will ask the
> developer about this when he responds to your other bug reports, but
> don't expect a resolution for your problem. It might be "wontfix".
>
> Regards,
>
> Markus

If saving the setting is a design choice for whatever reason,
implenting a --no-verbose should be reasonable.


Regards,
Celelibi


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

Bug#677222: log_slow_queries deprecated

[Ivan Baldo]

Arrgg!!!
This bug hit me in Jessie with MariaDB 10.
If you change it as Steven said, then MariaDB 10 and MySQL 5.5 will 
start correctly if the user decides to uncomment it.
I can't believe this was reported in june 2012 and nothing has been 
done about it since, now users upgrading will hit this and if not fixed 
readily users installing Jessie will be hit too, loosing time 
unnecessarily for everyone

Thanks in advance.
Have a nice day.

--
Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: iba...@codigolibre.net - http://go.to/ibaldo


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

Bug#776400: grub-ieee1275: ppc64el-disable-vsx.patch applied to 32-bit kernel.img causes exception at 0x20000008 (mtmsrd 0)

[Mark Wiprud]

On Jan 27, 2015, at 2:40 PM, Colin Watson cjwat...@debian.org wrote:
> On Tue, Jan 27, 2015 at 11:17:04AM -0600, Mark wrote:
>> On a powerpc g4 (mac) system I am trying to switch from yaboot to grub.
>> The provided image always faults 8 bytes in. Looking at the patches for
>> grub I see "ppc64el-disable-vsx.patch" 
>> http://anonscm.debian.org/cgit/pkg-grub/grub.git/tree/debian/patches/ppc64el-disable-vsx.patch?id=debian/2.02.beta2-20
>> is causing the problem with the "mtmsrd" instruction.
>> 
>> I think the solution is to not apply this patch for 32-bit builds.
> 
> Thanks.  I prefer not to apply patches conditionally.  However, it
> should be sufficient to use the mtmsr instruction rather than mtmsrd;
> the bit we're trying to change is in the bottom 32 bits of the MSR in
> any case.
> 
> Please could you test version 2.02~beta2-21 when it becomes available in
> unstable (I'm preparing the upload now), and report how it behaves for
> you?
> 
> Thanks,
> 
> -- 
> Colin Watson   [cjwat...@debian.org]
> 

I have confirmed that the updated build fixes this problem.

Thanks!


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

Bug#774328: [Pkg-samba-maint] Bug#774328: ctdb: Failed to start ctdb.service: Unit ctdb.service failed to load: No such file or directory.

[Martin Schwenke]

Hi Mathieu,

This has stopped failing.  While that's obviously excellent, I wish I
could explain it.  :-(

Perhaps a systemd update did something magic?  I've only just seen
Cameron Norman's suggestion from 2015-01-02 to try "systemctl
daemon-reload".  That would have been a nice idea.  Not sure why I
didn't get an email from the bug system for Cameron's comment.  :-(
This was happening on my laptop where reboots are uncommon... so I
suppose a reboot could have fixed it too.

Do packages that provide systemd init need to set some sort of trigger
that causes a "systemctl daemon-reload"?  I just tried installing
proftpd-basic (random choice of daemon that I've never had installed
before), it starts and stops fine and I can't find any evidence of a
trigger like that, so that theory seems bogus.  :-(

Answers to questions below...

On Tue, 27 Jan 2015 14:51:46 +0100, Mathieu Parent
 wrote:

> 2015-01-16 9:20 GMT+01:00 Martin Schwenke :

> >> Anything relevant in /var/log/{syslog,ctdb/log.ctdb}? journalctl -u
> >> ctdb.service?
> >
> > No, nothing at all.  It looks like it is failing somewhere in systemd.
> 
> It's /var/log/ctdb/log.ctdb. Have you checked it too?

Yes, I had checked it and it was always empty, unless I ran
ctdbd_wrapper directly.  That's why I assumed a systemd problem.

Now it logs the expected failure due to broken configuration.  I'm
happy with that because I know enough if I want to configure CTDB from
this point...  :-)

> What "journalctl --unit ctdb.service" says ?
> 
> Is there any red line in "systemctl list-units"?

Yeah, given that it now works I see the CTDB-specific failure.

Sorry that this was a waste of time and we couldn't work out why it was
happening.  :-(

peace & happiness,
martin


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

Bug#775990: bug 775990

[Sandro Knauß]

tags 775990 +patch
severity 775990 grave
thanks

* The link has a patch mentioned:

http://quickgit.kde.org/?p=akonadi.git&a=commit&h=4ef5e13b047b73de1c9dee1ee4705fdb93c1fbe4

* Deadlock makes the package not usable, so set severity to grave.

regards,

sandro


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

Bug#776440: nmu: pcp_3.10.1

[Andreas Beckmann]

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

nmu pcp_3.10.1 . i386 . -m "Rebuild against perl 5.20"

maintainer upload was build on an outdated perl installation ...

this will close  #771789 libpcp-pmda-perl: uninstallable on i386: depends on 
perlapi-5.18.2

andreas


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

Bug#774737: unblock: libjpeg9/1:9a-2

[Bill Allombert]

On Fri, Jan 23, 2015 at 08:02:38AM +0100, Niels Thykier wrote:
> Hi,
> 
> Could you list the features that the turbo-variant is missing, which are
> present in the current version of libjpeg-progs from Wheezy?  Are there
> any lacking features beyond the "SmartScale" feature?

Yes, there are a number of missing features, most importantly,
libjpeg8 libjpeg-progs produces more accurate colors by using a higher quality
sampling. cjpeg and djpeg also provide options for better quality control.

The "SmartScale" extension is essentially a way to store the scaling parameter 
in
the JPEG image so that you do not to specify it when uncompressing the file.
But you can use the scaling code without ever creating an actual JFIF file with 
the
SmartScale extension (e.g. when converting to a raster format).

Cheers,
-- 
Bill. 

Imagine a large red swirl here.


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

Bug#776439: iceweasel: site identity spoofing

[Jakub Wilk]

Package: iceweasel
Version: 35.0-1
Tags: security

Iceweasel gets confused with the jwilk.net certificate, displaying 
incorrect information in the site identity popup, making the connection 
appear more secure than in actually is. To reproduce:


1) Go to https://jwilk.net/software/ and accept the self-signed 
certificate.


2) Click on the site identity button. The popup says says "This website 
does not supply identity information".


3) Open https://www.debian.org/ in another tab.

4) Go back to the original tab.

5) Click on the site button identity. Now the popup says "Verified by: 
Gandi", which is incorrect.



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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages iceweasel depends on:
ii  debianutils   4.4+b1
ii  fontconfig2.11.0-6.3
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-13
ii  libcairo2 1.14.0-2.1
ii  libdbus-1-3   1.8.14-1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.1-2+b2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-2
ii  libgcc1   1:4.9.2-10
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libglib2.0-0  2.42.1-1
ii  libgtk2.0-0   2.24.25-1
ii  libhunspell-1.3-0 1.3.3-3
ii  libnspr4  2:4.10.7-1
ii  libnss3   2:3.17.2-1.1
ii  libpango-1.0-01.36.8-3
ii  libsqlite3-0  3.8.7.4-1
ii  libstartup-notification0  0.12-4
ii  libstdc++64.9.2-10
ii  libvpx1   1.3.0-3
ii  libx11-6  2:1.6.2-3
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  procps2:3.3.9-8
ii  zlib1g1:1.2.8.dfsg-2+b1

--
Jakub Wilk


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

Bug#776438: example script for cron-driven sbuild-update

[Christian Kastner]

Source: sbuild
Version: 0.65.0-1
Severity: wishlist
Tags: patch

Hi,

I have attached the script I use to periodically update my various
sbuild chroots. It slightly facilitates chroot selection, logging, and
concurrency issues.

If you find this useful, please feel free to include it in examples/.

Regards,
Christian
#!/bin/sh
# Example script for automatically updating sbuild chroots
#
# Simply create a crontab /etc/cron.d/sbuild-update-all and specify the
# schedule that you want to use. The behaviour of this script can be influenced
# by the following evironment variables:
#
#   PATTERN glob pattern to match the chroot config name against, in
#   directory /etc/schroot/chroot.d/.
#
#   Default: *-sbuild
#
#   UPDATEARGS  The arguments with which sbuild-update will be invoked.
#
#   Default: --update --dist-upgrade --autoclean --autoremove
#
#   LOGFILE Log file to write to. These files are not rotated, you must set
#   this up yourself. See logrotate(8)
#
#   Default: /var/log/sbuild-update-all.log
#
# This script will refuse to run if another instance of it is running. In fact,
# it will refuse to run if there is an active chroot session (regardless of
# whether it is related to the matched patterns or not). Care for this must be
# taken when scheduling cron jobs, as crontabs are processed sequentially (with
# regards to variable assignment), but jobs are executed in parallel. 
#
# Examples
# 
#
# 1. Update all sbuild chroots four times a day (at 00:15/06:15/12:15/18:15):
#
# 15 */6 * * * root /usr/share/doc/sbuild/examples/sbuild-update-all
#
# 2. Update all sid sbuild chroots daily, and all jessie sbuild chroots weekly,
#and log the latter to a separate file:
#
# PATTERN = sid-*-sbuild
# @dailyroot /usr/share/doc/sbuild/examples/sbuild-update-all
#
# PATTERN = jessie-*-sbuild
# LOGFILE = /var/log/wheezy-chroot-update.log
# @weekly   root /usr/share/doc/sbuild/examples/sbuild-update-all
#
# The following will NOT work. Both of these jobs are executed at 00:15, so
# the second one will refuse to run:
#
# PATTERN = foo-*
# 15 0  * * * root /usr/share/doc/sbuild/examples/sbuild-update-all
#
# PATTERN = bar-*
# 15 0  * * * root /usr/share/doc/sbuild/examples/sbuild-update-all


# Output of sbuild-update invocations will be written to this file
LOGFILE=${LOGFILE:-/var/log/sbuild-update-all.log}

# Arguments passed to sbuild-update
UPDATEARGS=${UPDATEARGS:-"--update --dist-upgrade --autoclean --autoremove"}

# chroot config names are identified by this pattern
PATTERN=${PATTERN:-*-sbuild}


# Open logfile for output, make sure we're the only instance active
exec 8>>$LOGFILE
if ! flock -x -n 8
then
echo "$0: another instance is already running"
exit 1
fi
# Redirect stdout to logfile
exec 9>&1
exec 1>&8

if ! ls /etc/schroot/chroot.d/$PATTERN >/dev/null 2>&1
then
echo "No chroots defined"
break
fi

for fullname in /etc/schroot/chroot.d/$PATTERN
do
confname=`basename $fullname`

# Check for *any* active session and skip if there is one.
# chroots can share common factors, for example an LVM volume, so it's
# better to be safe than sorry.
if  [ -n "`schroot -l --all-sessions`" ]
then
echo "Active schroot session, will not continue"
break
fi

echo "** `date` **"
echo "Action: sbuild-update $UPDATEARGS $confname"

if ! sbuild-update $UPDATEARGS $confname
then
echo "ERROR: failed to update $confname"
continue
fi
done

# Release lock and undo redirections
exec 8>&- 1>&9 9>&-

Bug#776437: network-manager: After suspend the routing table is sometimes wrong

[Cesar Enrique Garcia]

Package: network-manager
Version: 0.9.10.0-5
Severity: important

 After I suspending my laptop and waking it up again, the routing table is
 no longer a valid one:

 # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.0.0 0.0.0.0 255.255.255.0   U 0  00 eth1

 whereas the routing table before suspending is:
  # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG1024   00 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 eth1
192.168.0.0 0.0.0.0 255.255.255.0   U 0  00 eth1

 nm-applet shows that the eth1 is connected to the Wi-Fi.

 The error cannot be reproduced all the time. Since it is a quite old and 
 slow laptop, there might be some race condition.

 I see no error messages in /var/log/daemon.log.

 The IPv6 routing table also changed. Before:
Kernel IPv6 routing table
DestinationNext Hop   Flag Met Ref Use If
::/0   :: !n   -1  1 11760 lo
::1/128:: U256 0 0 lo
2001:4c50:2ce:1600:216:6fff:fe4a:3fc2/128 :: Ue   256 0 
0 eth1
2001:4c50:2ce:1600::/64:: U10  0 0 eth1
2001:4c50:2ce:1600::/56fe80::c627:95ff:feb0:f03   UG   10  0 0 eth1
fe80::/64  :: U256 0 0 eth1
::/0   fe80::c627:95ff:feb0:f03   UG   1024 0 0 eth1
::/0   :: !n   -1  1 11760 lo
::1/128:: Un   0   167 lo
2001:4c50:2ce:1600:216:6fff:fe4a:3fc2/128 :: Un   0   1 
6 lo
fe80::216:6fff:fe4a:3fc2/128   :: Un   0   1   169 lo
ff00::/8   :: U256 2 0 eth1
::/0   :: !n   -1  1 11760 lo


After:

Kernel IPv6 routing table
DestinationNext Hop   Flag Met Ref Use If
::/0   :: !n   -1  1  4552 lo
::1/128:: U256 0 0 lo
2001:4c50:2ce:1600:216:6fff:fe4a:3fc2/128 :: Ue   256 0 
0 eth1
2001:4c50:2ce:1600::/64:: U10  0 0 eth1
2001:4c50:2ce:1600::/56fe80::c627:95ff:feb0:f03   UG   10  0 0 eth1
fe80::/64  :: U256 0 0 eth1
::/0   fe80::c627:95ff:feb0:f03   UG   1024 0 0 eth1
::/0   :: !n   -1  1  4552 lo
::1/128:: Un   0   123 lo
2001:4c50:2ce:1600:216:6fff:fe4a:3fc2/128 :: Un   0   5 
  979 lo
fe80::216:6fff:fe4a:3fc2/128   :: Un   0   1   218 lo
ff00::/8   :: U256 2 0 eth1
::/0   :: !n   -1  1  4552 lo

Regards

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.8.12-3
ii  init-system-helpers1.22
ii  isc-dhcp-client4.3.1-5
ii  libc6  2.19-13
ii  libdbus-1-31.8.12-3
ii  libdbus-glib-1-2   0.102-1
ii  libgcrypt201.6.2-4+b1
ii  libglib2.0-0   2.42.1-1
ii  libgnutls-deb0-28  3.3.8-5
ii  libgudev-1.0-0 215-8
ii  libmm-glib01.4.0-1
ii  libndp01.4-2
ii  libnewt0.520.52.17-1+b1
ii  libnl-3-2003.2.24-2
ii  libnl-genl-3-200   3.2.24-2
ii  libnl-route-3-200  3.2.24-2
ii  libnm-glib40.9.10.0-5
ii  libnm-util20.9.10.0-5
ii  libpam-systemd 215-8
ii  libpolkit-gobject-1-0  0.105-8
ii  libreadline6   6.3-8+b3
ii  libsoup2.4-1   2.48.0-1
ii  libsystemd0215-8
ii  libteamdctl0   1.12-1
ii  libuuid1   2.25.2-4
ii  lsb-base   4.1+Debian13+nmu1
ii  policykit-10.105-8
ii  udev   215-8
ii  wpasupplicant  2.3-1

Versions of packages network-manager recommends:
ii  crda3.13-1
ii  dnsmasq-base2.72-2
ii  iptables1.4.21-2+b1
ii  iputils-arping  3:20121221-5+b2
ii  modemmanager1.4.0-1
ii 

Bug#776436: fonts-vlgothic: wrong metrics for several symbols (full- instead of half-width)

[paulownia]

Package: fonts-vlgothic
Version: 20141206-1

The character widths of several (latin1) symbols in VL Gothic seem to
be incorrect, they are full-width when they should be half-width. The
following characters are affected, there may be more:

¤ U+00a4 CURRENCY SIGN
§ U+00a7 SECTION SIGN
¨ U+00a8 DIAERESIS
© U+00a9 COPYRIGHT SIGN
® U+00ae REGISTERED SIGN
° U+00b0 DEGREE SIGN
± U+00b1 PLUS-MINUS SIGN
² U+00b2 SUPERSCRIPT TWO
³ U+00b3 SUPERSCRIPT THREE
´ U+00b4 ACUTE ACCENT
¶ U+00b6 PILCROW SIGN
· U+00b7 MIDDLE DOT
¹ U+00b9 SUPERSCRIPT ONE
º U+00ba MASCULINE ORDINAL INDICATOR
¼ U+00bc VULGAR FRACTION ONE QUARTER
½ U+00bd VULGAR FRACTION ONE HALF
¾ U+00be VULGAR FRACTION THREE QUARTERS
¿ U+00bf INVERTED QUESTION MARK
× U+00d7 MULTIPLICATION SIGN
÷ U+00f7 DIVISION SIGN


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

Bug#776435: apt: Package install with apt preferences won't follow dependencies for release

[Dan Urist]

Package: apt
Version: 0.9.7.9+deb7u6
Severity: wishlist

Dear Maintainer,

With "apt-get install -t", a package and all its dependencies are
installed from the given release. There seems to be no way to achieve
the same behavior with apt preferences. While it's possible to specify
a glob or regexp for package names in apt preferences, any dependent
packages that don't match won't be installed from the given
release. The use case for this functionality is in systems managed by
configuration management software (e.g. puppet), where it's much more
straightforward to specify behavior in a configuration file than via
flags to a specific command.

For example, I need the newer functionality of the version of
syslog-ng in wheezy backports. With the following apt_preferences file:

> Package: syslog-ng*
> Pin: release n=wheezy-backports
> Pin-Priority: 990
> 

"apt-get install syslog-ng" gives this error:

> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  syslog-ng : Depends: syslog-ng-mod-mongodb but it is not going to be
>  installed
> E: Unable to correct problems, you have held broken packages.

>From "apt-get install syslog-ng-mod-mongodb", the issue is this:

> The following packages have unmet dependencies:
>  syslog-ng-mod-mongodb : Depends: libmongo-client0 (>= 0.1.6) but
>  0.1.5-1+deb7u1 is to be installed

This is because libmongo-client0 doesn't match the glob "syslog-ng*"
in the preferences file.

However, "apt-get -t wheezy-backports install syslog-ng" correctly
installs all the dependencies from backports.


-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (no /etc/apt/sources.list present) --


-- System Information:
Debian Release: 7.8
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.65-vs2.3.2.17-beng (SMP w/16 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages apt depends on:
ii  debian-archive-keyring  2014.3~deb7u1
ii  gnupg   1.4.12-7+deb7u6
ii  libapt-pkg4.12  0.9.7.9+deb7u6
ii  libc6   2.13-38+deb7u6
ii  libgcc1 1:4.7.2-5
ii  libstdc++6  4.7.2-5

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc 
ii  aptitude0.6.8.2-1
ii  dpkg-dev1.16.15
ii  python-apt  0.8.8.2
ii  xz-utils5.1.1alpha+20120614-2

-- Configuration Files:
/etc/cron.daily/apt [Errno 2] No such file or directory: u'/etc/cron.daily/apt'

-- 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#776395: java-package: Does not use the system's keystore

[Emmanuel Bourg]

Hi Francesc,

Thank you for the patch, this is an interesting suggestion. I wonder if
we should really go that far with the system integration of the
generated package though. I can imagine that someone may want to install
a stock Oracle JRE with no Debian interferences. So maybe this
integration could be enabled optionally with a
--with-system-certificates parameter on the command line.

Emmanuel Bourg


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

Bug#776434: gnuplot: Installing both gnuplot and gnuplot5 breaks gnuplot4 help

[Antonio Ospite]

Package: gnuplot
Version: 4.6.6-1
Severity: important

Dear Maintainer,

when installing both gnuplot and gnuplot5 the gnuplot4 help is broken
with this error:


$ gnuplot4

G N U P L O T
Version 4.6 patchlevel 6last modified September 2014
Build System: Linux x86_64

Copyright (C) 1986-1993, 1998, 2004, 2007-2014
Thomas Williams, Colin Kelley and many others

gnuplot home: http://www.gnuplot.info
faq, bugs, etc:   type "help FAQ"
immediate help:   type "help"  (plot window: hit 'h')

Terminal type set to 'qt'
gnuplot> help
/usr/share/gnuplot/gnuplot.gih: No such file or directory
gnuplot>


To reproduce that just install gnuplot, then install gnuplot5 and then
try using the 'help' command from gnuplot4.

I am not sure if this is a bug in gnuplot or gnuplot5 but I am filing it
here because gnuplot4 is the broken package.

Thanks,
   Antonio

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-rc5-ao2 (SMP w/1 CPU core)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages gnuplot depends on:
ii  gnuplot-qt [gnuplot-x11]  4.6.6-1

gnuplot recommends no packages.

Versions of packages gnuplot suggests:
ii  feedgnuplot  1.34-2
pn  gnuplot-doc  
pn  libgnuplot-iostream-dev  
pn  python-gnuplot   

-- no debconf information
-- 
Antonio Ospite
http://ao2.it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?


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

Bug#776072: dpkg-maintscript-helper dir_to_symlink explodes on subtree in cups-pdf package

[Andreas Beckmann]

On 2015-01-26 17:34, Guillem Jover wrote:
> Sorry, actually for non-M-A:same packages the best thing to do is to
> just pass the non-arch-qualified package name which will support all
> the above cases correctly. I'll try to make that clear in the man
> page.

So it's better to explicitly specify the unqualified package name in the
dpkg-maintscript-helper call than to have it taken from
DPKG_MAINTSCRIPT_PACKAGE (which may be qualified).

(in the underlying bug there was no, i.e. the default, package argument)

Andreas


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

Bug#775202: Add support for running a 64-bit Linux kernel on a 32-bit EFI

[Steve McIntyre]

On Tue, Jan 27, 2015 at 08:12:51PM +, Colin Watson wrote:
>On Mon, Jan 12, 2015 at 04:24:24PM +, Steve McIntyre wrote:
>> On Mon, Jan 12, 2015 at 03:17:39PM +, Colin Watson wrote:
>> >This all looks reasonable enough, but why not "return is_64_kernel () ?
>> >64 : 32;" here?  Then you could simplify
>> >grub_install_get_default_x86_platform to just conditionalise on "if
>> >(read_platform_size () == 64)" and avoid duplication.
>> 
>> Could do, yes. I personally tend to shy away from ternary usage like
>> that, but meh. :-)
>
>I meant this as a rough sketch rather than literal code ...

Yeah, OK...

>> OK, how about:
>
>Looks good, thanks!  Sorry for the delay in reviewing this.  I've pushed
>it to the Debian master branch.

Lovely, ta. I've also been remiss in taking it upstream so far.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Further comment on how I feel about IBM will appear once I've worked out
 whether they're being malicious or incompetent. Capital letters are forecast."
 Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html


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

Bug#776433: dict-devil: please make the build reproducible

[Chris Lamb]

Source: dict-devil
Version: 1.0-12
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that dict-devil could not be built reproducibly.

The attached patch removes timestamps from the build system. Once
applied, dict-devil can be built reproducibly in our current
experimental
framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds



Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad dict-devil.orig/dict-devil-1.0/debian/devil2dict 
dict-devil/dict-devil-1.0/debian/devil2dict
--- dict-devil.orig/dict-devil-1.0/debian/devil2dict2015-01-27 
22:53:44.754004688 +
+++ dict-devil/dict-devil-1.0/debian/devil2dict 2015-01-27 22:55:53.159685075 
+
@@ -28,7 +28,7 @@
 '--without-headword', # Necessary for multiple headwords.
 '--headword-separator', ', ',
 '-u', 'http://wiretap.area.com/Gopher/Library/Classic/devils.txt',
-'-s', 'The Devil\'s Dictionary (1881-1906)',
+'-s', 'The Devil\'s Dictionary (1881-1906)', '--without-time',
 $fmt_base
 or die "$0: can't open pipe to dictfmt: $!\n"
 if defined $fmt_base;
diff -urNad dict-devil.orig/dict-devil-1.0/debian/rules 
dict-devil/dict-devil-1.0/debian/rules
--- dict-devil.orig/dict-devil-1.0/debian/rules 2015-01-27 22:53:44.754004688 
+
+++ dict-devil/dict-devil-1.0/debian/rules  2015-01-27 22:55:27.298540948 
+
@@ -1,9 +1,13 @@
 #! /usr/bin/make -f
 
+BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date)
+
 %:
dh $@
 
 override_dh_auto_build:
chmod a+x debian/devil2dict
debian/devil2dict devils.txt devil
+   # Ensure deterministic mtime for dictzip to inherit
+   touch --date='$(BUILD_DATE)' devil.dict
dictzip devil.dict

Bug#776432: dict-stardic: please make the build reproducible

[Chris Lamb]

Source: dict-stardic
Version: 1.3.1-4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that dict-stardic could not be built reproducibly.

The attached patch removes timestamps from the build system. Once
applied, dict-stardic can be built reproducibly in our current
experimental
framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad dict-stardic.orig/dict-stardic-1.3.1/debian/rules 
dict-stardic/dict-stardic-1.3.1/debian/rules
--- dict-stardic.orig/dict-stardic-1.3.1/debian/rules   2015-01-27 
22:51:14.699367508 +
+++ dict-stardic/dict-stardic-1.3.1/debian/rules2015-01-27 
22:52:14.426009212 +
@@ -9,7 +9,7 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-
+BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date)
 
 CFLAGS = -Wall -g
 
@@ -25,7 +25,9 @@
dh_testdir
 
./convert.sh
-   cat stardic | /usr/bin/dictfmt -t -s "Stardic English-Chinese 
Dictionary" stardic
+   cat stardic | /usr/bin/dictfmt -t -s "Stardic English-Chinese 
Dictionary" --without-time stardic
+   # Ensure deterministic mtime for dictzip to inherit
+   touch --date='$(BUILD_DATE)' stardic.dict
/usr/bin/dictzip -v stardic.dict
 
touch build-stamp

Bug#776430: dictd: add --no-name flag to help reproducible builds

[Chris Lamb]

Source: dictd
Version: 1.12.1+dfsg-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that dictzip adds the filename and timestamp to the generated .dz files.

The attached patch adds a --no-name flag (like gzip) that disables this.
This will make it easier and cleaner for maintainers to make their
builds reproducible.

 [1]: https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/data.h b/data.h
index 2fa54f2..ca0f564 100644
--- a/data.h
+++ b/data.h
@@ -33,7 +33,8 @@ extern void dict_data_close (
 extern void dict_data_print_header( FILE *str, dictData *data );
 extern int  dict_data_zip(
const char *inFilename, const char *outFilename,
-   const char *preFilter, const char *postFilter );
+   const char *preFilter, const char *postFilter,
+   int nonameFlag );
 
 extern char *dict_data_obtain (
const dictDatabase *db,
diff --git a/dictzip.1.in b/dictzip.1.in
index 7b2c6e2..5b51173 100644
--- a/dictzip.1.in
+++ b/dictzip.1.in
@@ -172,6 +172,9 @@ license and quit.
 Check the compressed file integrity.  This option is not implemented.
 Instead, it will list the header information.
 .TP
+.BR \-n " or " \-\-no-name
+Don't save the original filename and timestamp.
+.TP
 .BR \-v " or " \-\-verbose
 Verbose. Display extra information during compression.
 .TP
diff --git a/dictzip.c b/dictzip.c
index 3e8000d..f917407 100644
--- a/dictzip.c
+++ b/dictzip.c
@@ -127,7 +127,8 @@ void dict_data_print_header( FILE *str, dictData *header )
 }
 
 int dict_data_zip( const char *inFilename, const char *outFilename,
-  const char *preFilter, const char *postFilter )
+  const char *preFilter, const char *postFilter,
+  int nonameFlag )
 {
char  inBuffer[IN_BUFFER_SIZE];
char  outBuffer[OUT_BUFFER_SIZE];
@@ -162,11 +163,16 @@ int dict_data_zip( const char *inFilename, const char 
*outFilename,
   err_fatal_errno( __func__,
   "Cannot open \"%s\"for write\n", outFilename );
 
-   origFilename = xmalloc( strlen( inFilename ) + 1 );
-   if ((pt = strrchr( inFilename, '/' )))
-  strcpy( origFilename, pt + 1 );
-   else
-  strcpy( origFilename, inFilename );
+   if (nonameFlag) {
+  origFilename = xmalloc( 1 );
+  origFilename[0] = '\0';
+   } else {
+  origFilename = xmalloc( strlen( inFilename ) + 1 );
+  if ((pt = strrchr( inFilename, '/' )))
+ strcpy( origFilename, pt + 1 );
+  else
+ strcpy( origFilename, inFilename );
+   }
 
/* Initialize compression engine */
zStream.zalloc= NULL;
@@ -210,10 +216,12 @@ int dict_data_zip( const char *inFilename, const char 
*outFilename,
 #if HEADER_CRC
header[GZ_FLG]|= GZ_FHCRC;
 #endif
-   header[GZ_MTIME+3]= (st.st_mtime & 0xff00) >> 24;
-   header[GZ_MTIME+2]= (st.st_mtime & 0x00ff) >> 16;
-   header[GZ_MTIME+1]= (st.st_mtime & 0xff00) >>  8;
-   header[GZ_MTIME+0]= (st.st_mtime & 0x00ff) >>  0;
+   if (!nonameFlag) {
+  header[GZ_MTIME+3]= (st.st_mtime & 0xff00) >> 24;
+  header[GZ_MTIME+2]= (st.st_mtime & 0x00ff) >> 16;
+  header[GZ_MTIME+1]= (st.st_mtime & 0xff00) >>  8;
+  header[GZ_MTIME+0]= (st.st_mtime & 0x00ff) >>  0;
+   }
header[GZ_XFL]= GZ_MAX;
header[GZ_OS] = GZ_OS_UNIX;
header[GZ_XLEN+1] = (extraLength & 0xff00) >> 8;
@@ -376,6 +384,7 @@ static void help( void )
   "",
   "-d --decompress  decompress",
   "-f --force   force overwrite of output file",
+  "-n --no-name don't save the original filename and timestamp",
   "-h --helpgive this help",
   "-k --keepdo not delete original file",
   "-l --listlist compressed file contents",
@@ -409,6 +418,7 @@ int main( int argc, char **argv )
int   listFlag   = 0;
int   stdoutFlag = 0;
int   testFlag   = 0;
+   int   nonameFlag = 0;
char  buffer[BUFFERSIZE];
char  *buf;
char  *pre   = NULL;
@@ -426,6 +436,7 @@ int main( int argc, char **argv )
   { "stdout",   0, 0, 'c' },
   { "decompress",   0, 0, 'd' },
   { "force",0, 0, 'f' },
+  { "no-name",  0, 0, 'n' },
   { "help", 0, 0, 'h' },
   { "keep", 0, 0, 'k' },
   { "list", 0, 0, 'l' },
@@ -463,11 +474,12 @@ int main( int argc, char **argv )
 #endif
 
while ((c = getopt_long( argc, argv,
-   "cdfhklLe:E:s:S:tvVD:p:P:",
+   "cdfnhklLe:E:s:S:tvVD:p:P:",
longopts, NULL

Bug#776431: Rebooting with intel-microcode 3.20150107.1~bpo70+1 causing CPU lockups

[Ashish SHUKLA]

Package: intel-microcode
Version: 3.20150107.1~bpo70+1

Hi,

After installing this microcode update and rebooting host (Dell PowerEdge
R430), we get:

--8<---cut here---start->8---
[   20.224624] [ cut here ] 

 
[   20.229882] WARNING: CPU: 0 PID: 1 at 
/build/linux-ax4Uh1/linux-3.16.7-ckt2/kernel/watchdog.c:265 
watchdog_overflow_callback+0x9a/0xc0()  

[   20.243701] Watchdog detected hard LOCKUP on cpu 0   

 
[   20.248931] Modules linked in:   

 
[   20.252809] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G  D   
3.16.0-0.bpo.4-amd64 #1 Debian 3.16.7-ckt2-1~bpo70+1

[   20.264878] Hardware name: Dell Inc. PowerEdge R430/0DYFC8, BIOS 1.0.2 
11/17/2014  
   
[   20.273355]   8171bac8 81541f8f 
88047f406c58
  
[   20.282045]  8106cecc 88046eec0c00  
88047f406d48
  
[   20.290924]   88047f406ef8 8106cfba 
8171baa0
  
[   20.299617] Call Trace:  

 
[   20.302440][] ? dump_stack+0x41/0x51
[   20.309307]  [] ? warn_slowpath_common+0x8c/0xc0
[   20.316306]  [] ? warn_slowpath_fmt+0x4a/0x50
[   20.323014]  [] ? watchdog_overflow_callback+0x9a/0xc0
[   20.330596]  [] ? __perf_event_overflow+0x98/0x230
[   20.337789]  [] ? x86_perf_event_set_period+0xd8/0x150
[   20.345371]  [] ? intel_pmu_handle_irq+0x1f8/0x3d0
[   20.352564]  [] ? perf_event_nmi_handler+0x32/0x60
[   20.359757]  [] ? nmi_handle+0x8d/0x140
[   20.365882]  [] ? 
default_send_IPI_mask_allbutself_phys+0xf0/0xf0
[   20.374553]  [] ? default_do_nmi+0xdd/0x130
[   20.381066]  [] ? do_nmi+0x88/0xc0
[   20.386704]  [] ? end_repeat_nmi+0x1e/0x2e
[   20.393121]  [] ? qi_submit_sync+0x197/0x430
[   20.399732]  [] ? qi_submit_sync+0x197/0x430
[   20.406342]  [] ? qi_submit_sync+0x197/0x430
[   20.412952]  <>  [] ? modify_irte+0xa1/0xf0
[   20.420110]  [] ? intel_ioapic_set_affinity+0x144/0x1e0
[   20.427790]  [] ? setup_ioapic_dest+0x70/0x97
[   20.434489]  [] ? native_smp_cpus_done+0xff/0x108
[   20.441586]  [] ? kernel_init_freeable+0xdc/0x1e7
[   20.448681]  [] ? rest_init+0x80/0x80
[   20.454612]  [] ? kernel_init+0xe/0xf0
[   20.460640]  [] ? ret_from_fork+0x7c/0xb0
[   20.466960]  [] ? rest_init+0x80/0x80
[   20.472890] ---[ end trace a5d8cfb932b02cf3 ]---
--8<---cut here---end--->8---

Kernel: linux-image-3.16.0-0.bpo.4-amd64 3.16.7-ckt2-1~bpo70

Output from "/proc/cpuinfo" from the host with "intel-microcode" package
purged:

--8<---cut here---start->8---
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 63
model name  : Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
stepping: 2
microcode   : 0x2a
cpu MHz : 1200.000
cache size  : 15360 KB
physical id : 0
siblings: 12
core id : 0
cpu cores   : 6
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 15
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt 
pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 
avx2 smep bmi2 erms invpcid
bogomips: 4794.61
clflush size: 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

proce

Bug#770009: Backtrace for the hang

[Vincent Fourmond]

With the backtrace...

On Tue, Jan 27, 2015 at 10:13 PM, Vincent Fourmond  wrote:
>   I've run the build on the MIPS portebox. It hangs on the first SVG
> to PNG conversion. Here is a full backtrace. The process is for now
> stopped on the porterbox; I think I can leave it for some hours more
> at least, if other information could be useful.
>
>   Hope it helps,
>
>   Vincent
>

Thread 2 (Thread 0x762ca460 (LWP 14695)):
#0  GetOpacityPixel (stroke_opacity=, y=590, x=139, 
fill_rule=EvenOddRule, 
fill=MagickTrue, mid=0.62537187436756381, polygon_info=0x840ed8) at 
../../magick/draw.c:3806
beta = 
subpath_opacity = 
p = 0x852198
q = 
j = 1
winding_number = -1
alpha = 
distance = 
i = 
#1  DrawPolygonPrimitive._omp_fn.3 () at ../../magick/draw.c:4027
q = 
id = 
fill_opacity = 
stroke_color = {blue = 65535, green = 65535, red = 65535, opacity = 
65535}
x = 139
stroke_opacity = 
fill_color = {blue = 65535, green = 65535, red = 65535, opacity = 0}
start = 
stop = 683
y = 590
draw_info = 0x8508a0
image_view = 0x841240
mid = 0.62537187436756381
exception = 0x873788
fill = MagickTrue
polygon_info = 0x832e10
bounds = {x1 = 0, y1 = 0, x2 = 683, y2 = 707}
start = 0
stop = 707
status = MagickTrue
warning: GDB can't find the start of the function at 0x7724e63e.

GDB is unable to find the start of the function at 0x7724e63e
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
stack pointer.
However, if you think GDB should simply search farther back
from 0x7724e63e for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
#2  0x7724e640 in ?? () from /usr/lib/mips-linux-gnu/libgomp.so.1
No symbol table info available.

Thread 1 (Thread 0x76f7f000 (LWP 14680)):
#0  0x77b29230 in GetOpacityPixel (stroke_opacity=, y=584, 
x=589, fill_rule=EvenOddRule, 
fill=MagickTrue, mid=0.62537187436756381, polygon_info=0x840588) at 
../../magick/draw.c:3714
beta = 
subpath_opacity = 0
p = 0x851d50
q = 
j = 0
winding_number = 
alpha = 
distance = 
i = 1
#1  DrawPolygonPrimitive._omp_fn.3 () at ../../magick/draw.c:4027
q = 0x765d85a8
id = 
fill_opacity = 
stroke_color = {blue = 65535, green = 65535, red = 65535, opacity = 
65535}
x = 589
stroke_opacity = 0
fill_color = {blue = 65535, green = 65535, red = 65535, opacity = 0}
start = 
stop = 683
y = 584
draw_info = 0x8508a0
image_view = 0x841240
mid = 0.62537187436756381
exception = 0x873788
fill = MagickTrue
polygon_info = 0x832e10
bounds = {x1 = 0, y1 = 0, x2 = 683, y2 = 707}
start = 0
stop = 707
status = MagickTrue
#2  0x772499c8 in GOMP_parallel () from /usr/lib/mips-linux-gnu/libgomp.so.1
No symbol table info available.
#3  0x77b2776c in DrawPolygonPrimitive (image=0x8705b8, draw_info=0x8508a0, 
primitive_info=0x884b18)
at ../../magick/draw.c:3985
image_view = 0x841240
mid = 0.62537187436756381
exception = 0x873788
fill = MagickTrue
status = MagickTrue
polygon_info = 
p = 
i = 
bounds = {x1 = 0, y1 = 0, x2 = 683, y2 = 707}
start = 0
stop = 707
__PRETTY_FUNCTION__ = "DrawPolygonPrimitive"
__func__ = "DrawPolygonPrimitive"
#4  0x77b30bf0 in DrawPrimitive (image=0x8705b8, draw_info=0x8508a0, 
primitive_info=0x884b18)
at ../../magick/draw.c:4619
mid = 
scale = 
clone_info = 
image_view = 0x840f00
exception = 0x873788
status = 1
i = 
x = 
y = 
__func__ = "DrawPrimitive"
#5  0x77b33c78 in DrawImage (image=0x8705b8, draw_info=0x882c20) at 
../../magick/draw.c:3156
affine = {sx = 1, rx = 0, ry = 0, sy = 1, tx = 0, ty = 0}
current = {sx = 1.25068752, rx = 0, ry = 0, sy = 
-1.2507, tx = -38.9392, 
  ty = 838.7894819207}
key = '\000' ...
keyword = "path", '\000' ...
geometry = '\000' ...
name = '\000' ...
pattern = '\000' 
primitive = 0x84d7e0 "push graphic-context\npath 'M 0,792 612,792 612,0 
0,0 0,792 z'\npop graphic-context\n"
token = 
q = 0x84d81e "pop graphic-context\n"
angle = 
factor = 
primitive_extent = 82
graphic_context = 0x8408d8
status = 1
point = 
start_color = {blue = 0, green = 0, red = 0, opacity 

Bug#776429: unblock: fs-uae/2.4.1+ds-3

[John Paul Adrian Glaubitz]

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

fs-uae has a bug which results in segmentation faults when using
newer versions of the proprietary nVidia driver [1,2]. Initially,
this was blamed on the nVidia driver but it turned out to be a
bug in fs-uae after nVidia investigated the problem [3].

The actual patch to fix the issue just removes an fs-uae-internal
implementation of the glibc function mprotect() which is the
only change in fs-uae_2.4.1+ds-3.

Since this issue affects multiple users and many of them have
directly complained to me in form of bug reports, I would kindly
ask the release team to unblock fs-uae_2.4.1+ds-3 for Jessie.

I have already uploaded fs-uae_2.4.1+ds-3 to unstable and should
pop up on the buildds quickly. I am attaching its debdiff.

Cheers,
Adrian

unblock fs-uae/2.4.1+ds-3

> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757164
> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767109
> [3] http://fs-uae.net/2015/01/27/fs-uae-2-4-3-released
diff -Nru fs-uae-2.4.1+ds/debian/changelog fs-uae-2.4.1+ds/debian/changelog
--- fs-uae-2.4.1+ds/debian/changelog	2014-05-03 19:22:05.0 +0200
+++ fs-uae-2.4.1+ds/debian/changelog	2015-01-27 23:19:17.0 +0100
@@ -1,3 +1,11 @@
+fs-uae (2.4.1+ds-3) unstable; urgency=medium
+
+  * Add debian/patches/0003-remove-custom-mprotect-function.patch
+to fix a segmentation fault when running fs-uae with recent
+versions of the proprietary nVidia driver (Closes: #757164).
+
+ -- John Paul Adrian Glaubitz   Tue, 27 Jan 2015 22:38:53 +0100
+
 fs-uae (2.4.1+ds-2) unstable; urgency=medium
 
   * Add missing dependency on python-pil for fs-uae-arcade in debian/control.
diff -Nru fs-uae-2.4.1+ds/debian/patches/0003-remove-custom-mprotect-function.patch fs-uae-2.4.1+ds/debian/patches/0003-remove-custom-mprotect-function.patch
--- fs-uae-2.4.1+ds/debian/patches/0003-remove-custom-mprotect-function.patch	1970-01-01 01:00:00.0 +0100
+++ fs-uae-2.4.1+ds/debian/patches/0003-remove-custom-mprotect-function.patch	2015-01-27 23:09:40.0 +0100
@@ -0,0 +1,26 @@
+Description: 0003-remove-custom-mprotect-function.patch
+ This patch removes an fs-uae-internal implementation of the glibc function
+ mprotect(). This implementation causes fa-uae to segfault when using
+ recent versions of the proprietary nVidia driver. nVidia has investigated
+ into the issue and identified the problem. Simply removing mprotect()
+ from the fs-uae code base results in the code using glibc's implementation
+ of mprotect() and fixes the segfault.
+
+--- fs-uae-2.4.1+ds.orig/src/od-fs/mman.cpp
 fs-uae-2.4.1+ds/src/od-fs/mman.cpp
+@@ -881,15 +881,6 @@ STATIC_INLINE uae_key_t find_shmkey (uae
+ return result;
+ }
+ 
+-int mprotect (void *addr, size_t len, int prot)
+-#ifdef PANDORA
+-__THROW
+-#endif
+-{
+-int result = 0;
+-return result;
+-}
+-
+ void *uae_shmat (int shmid, void *shmaddr, int shmflg)
+ {
+ write_log("uae_shmat shmid %d shmaddr %p, shmflg %d natmem_offset = %p\n",
diff -Nru fs-uae-2.4.1+ds/debian/patches/series fs-uae-2.4.1+ds/debian/patches/series
--- fs-uae-2.4.1+ds/debian/patches/series	2014-04-06 21:24:15.0 +0200
+++ fs-uae-2.4.1+ds/debian/patches/series	2015-01-27 23:05:45.0 +0100
@@ -1,2 +1,3 @@
 0001-use-external-libglee.patch
 0002-dont-copy-upstream-copying-file.patch
+0003-remove-custom-mprotect-function.patch

Bug#776428: tracker.debian.org: Add a link to the Security Bug Tracker

[Frederic MASSOT]

Package: tracker.debian.org
Severity: wishlist

Dear Maintainer,

Can you add a link to the Security Bug Tracker ?

https://security-tracker.debian.org/tracker/

Regards.

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500, 
'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


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

Bug#774233: systemd shell

[Antoine Beaupré]

On 2015-01-27 15:30:24, Niels Thykier wrote:
> Control: tags -1 patch
>
> On 2014-12-30 17:10, Antoine Beaupré wrote:
>> And actually, maybe it should be a subsection like 4.1.4.1 that would be
>> refered to by 5.5...
>> 
>
> Hi,
>
> Thanks for reporting this.
>
> The attached patch attempts to cover a basic 4.1.4.2 section for
> describing how to obtain a shell under systemd if booting fails.
> Admittedly, it lacks a reference from 5.5, but that should be fairly
> trivial once the contents of 4.1.4.2 is in place.
>
> A review would be greatly appreciated.

I am not familiar with the XML syntax, but the text looks fine.

Thanks!

A.

-- 
Code is law.
 - Lawrence Lessig


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

Bug#776427: fglrx 14.9 required linux kernel 2.6 or above (up to 3.15) and not 3.16

[dario]

Package: fglrx-driver
Version: 14.9
Severity: important

Dear Maintainer,

fglrx-driver 14.9 required linux kernel 2.6 or above (up to 3.15) and not 3.16
present in testing jessie.

Kind Regars.
Dario Allella




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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


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

Bug#775395: partman-zfs in d-i jessie image does not create grub-compatible /boot ZFS mirror

[Michael Milligan]

On 01/27/2015 02:02 PM, Steven Chamberlain wrote:
> Hi,
> 
> Michael Milligan wrote:
>> But installing Grub failed with "unknown filesystem".  In
>> troubleshooting the issue, it seems grub2 (version currently is
>> 2.02~beta2-19) does not recognize the "feature@lz4_compress" option (and
>> had been previously reported) of the ZFS pools that kFreeBSD kernel 10.1
>> creates.
> 
> Thanks for the report.
> 
> It is actually expected that grub2 since 2.02 should understand these
> feature flags, including LZ4 compression.  I thought it was working for
> me when I last tested.
> 
> Hopefully this can be figured out without having to default to using
> "-d" (disabling new features including LZ4 metadata compression).

Yeah, failed for me using 10.1 kfreebsd image...   I did not have time
to retry it with each individual feature flag turned on/off to find the
exact combination it was choking on, but at least one of them is still
not recognized by grub-probe, not necessarily lz4_compress.

Regards,
Mike

-- 
Michael Milligan   -> mi...@acmeps.com
Acme Professional Services LLC


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

Bug#768397: fglrx-modules-dkms 1:14.9+ga14.201-2 don't build against kernel 3.16.0

[dario]

Package: fglrx-driver
Version: 14.9
Followup-For: Bug #768397

Dear Maintainer,

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

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

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


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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


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

Bug#776426: RFP: openvsp -- Parametric 3D Modeler

[Rob McDonald]

Package: wnpp
Severity: wishlist

  Package name: openvsp
  Version : 3.0.3
  Upstream Author : Rob McDonald 
  URL : http://www.openvsp.org/
  License : NOSA 1.3
  Programming Lang: C++
  Description : Parametric 3D Modeler

OpenVSP is a parametric 3D geometry modeler originally developed by NASA.
Under development from the early '90s, it was released as open source
in January 2012.  Milestone version 3.0 has recently been released and
represents a near total re-write of OpenVSP with lots of great additions.

OpenVSP is decidely not CAD.  It presents an alternative approach to 3D
modeling in the spirit of SketchUp, Blender, OpenCSG, and others (though it
is unlike all of those).  Originally intended for aircraft modeling, the
addition of suport for custom components makes OpenVSP suitable for users in
any problem domain.

OpenVSP should be of interest to anyone looking to build models to 3D print.

I am the primary maintainer of OpenVSP and will be willing to help maintain
this package -- however, I have never packaged anything before and don't know
where to start.  OpenVSP does have some obscure dependencies that will
also need to be addressed in some way.

Rob


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

Bug#776425: ebview: dpkg-buildflags-missing warning when building ebview-client

[paulownia]

Package: ebview
Version: 0.3.6.2-1.3
Tags: patch

CPPFLAGS and LDFLAGS are currently not passed to the compiler when
building ebview-client; I think this is the cause of the
dpkg-buildflags-missing warning reported by the build log scanner
 (cdbs handles the
buildflags automatically for everything else).

The following patch fixes this:

--- a/debian/rules
+++ b/debian/rules
@@ -10,7 +10,7 @@ DEB_CONFIGURE_EXTRA_FLAGS := --sysconfdir=/etc
 DEB_MAKE_INSTALL_TARGET := install prefix=$(CURDIR)/debian/ebview/usr
 
 build/ebview::
-   $(CC) $(CFLAGS) -o $(CURDIR)/src/ebview-client 
$(CURDIR)/src/ebview-client.c
+   $(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) -o $(CURDIR)/src/ebview-client 
$(CURDIR)/src/ebview-client.c
 
 install/ebview::
install -m 755 $(CURDIR)/src/ebview-client 
$(CURDIR)/debian/ebview/usr/bin


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

Bug#776422: [systemd] power button does poweroff instead of STR after each upgrade of systemd

[Michael Biebl]

control: severity -1 normal
control: tags -1 moreinfo unreproducible

Am 27.01.2015 um 22:40 schrieb Timo Weingärtner:
> Package: systemd
> Version: 215-10
> Severity: grave
> Justification: causes data loss
> 
> I configured the power button to do STR in KDE. After each upgrade of systemd 
> the power button does poweroff instead causing loss of unsaved work.
> 
> This did not happen before the introduction of systemd as a replacement for 
> $everything, so I have to guess systemd is the problem; please reassign if 
> you 
> know better.

Please provide more information why you think there is a bug in systemd.

The current information you provided is not sufficient to make an
analysis of the problem. My uneducated guess would be, that KDE does not
deal with logind being restarted as part of the upgrade.


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



signature.asc
Description: OpenPGP digital signature

Bug#776423: iceweasel: OOM on OGG file

[Jakub Wilk]

Package: iceweasel
Version: 35.0-1
Usertags: afl

Iceweasel runs out of memory and crashes on the attached OGG file:

$ ulimit -v 100
$ iceweasel oom.ogg 


(process:4029): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
out of memory: 0x4B139378 bytes requested
Segmentation fault (core dumped)


This bug was found using American fuzzy lop:
https://packages.debian.org/experimental/afl

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages iceweasel depends on:
ii  debianutils   4.4+b1
ii  fontconfig2.11.0-6.3
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-13
ii  libcairo2 1.14.0-2.1
ii  libdbus-1-3   1.8.14-1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.1-2+b2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-2
ii  libgcc1   1:4.9.2-10
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libglib2.0-0  2.42.1-1
ii  libgtk2.0-0   2.24.25-1
ii  libhunspell-1.3-0 1.3.3-3
ii  libnspr4  2:4.10.7-1
ii  libnss3   2:3.17.2-1.1
ii  libpango-1.0-01.36.8-3
ii  libsqlite3-0  3.8.7.4-1
ii  libstartup-notification0  0.12-4
ii  libstdc++64.9.2-10
ii  libvpx1   1.3.0-3
ii  libx11-6  2:1.6.2-3
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  procps2:3.3.9-8
ii  zlib1g1:1.2.8.dfsg-2+b1

--
Jakub Wilk


oom.ogg
Description: audio/ogg

Bug#776424: can be crashed by some network traffic

[Joey Hess]

Source: kgb-bot
Version: 1.33-2
Severity: important
Tags: security

2015.01.19 18:08:39: Listening on http://0.0.0.0:?session=KGB
2015.01.19 18:08:43: Connected to freenode (holmes.freenode.net)
2015.01.19 18:08:43: Joining #commits...
2015.01.19 18:08:43: Connected to oftc (graviton.oftc.net)
2015.01.19 18:08:43: Joining #ikiwiki #vcs-home #git-annex...
Did not get DONE/CLOSE event for Wheel ID 73 from IP 222.186.34.155 at
/usr/share/perl5/POE/Component/Server/SimpleHTTP.pm line 221.
I had a problem posting to event Got_Request of session SOAPServer for
DIR handler '.*'. As reported by Kernel: 'No such file or directory',
perhaps the session name is spelled incorrectly for this handler? at
/usr/share/perl5/POE/Session.pm line 483.

This has happened to me twice now, and it takes the bot down.

root@elephant:/home/joey>systemctl  status kgb-bot.service 
● kgb-bot.service - LSB: Collaborative IRC helper
   Loaded: loaded (/etc/init.d/kgb-bot)
   Active: active (exited) since Mon 2015-01-19 14:08:39 JEST; 1 weeks 1 days 
ago
  Process: 26584 ExecReload=/etc/init.d/kgb-bot reload (code=exited, 
status=0/SUCCESS)

Jan 26 03:57:27 elephant kgb-bot[26584]: Reloading Collaborative IRC helper: 
kgb-bot.

systemd thinks the service is running ok, but the daemon has in fact crashed or
exited because of the event logged above. Both "service kbg-bot start" and
"systemctl start kgb-bot" do nothing. I have to "service kgb-bot stop" to get
out of this state. (It seems that this could stand to be improved, by eg,
writing a systemd service file that doesn't let the daemon fork, so systemd
can handle logging and know when the process has exited.)

Here's the log from the previous time it happened:

2015.01.15 23:05:33: Connected to freenode (wolfe.freenode.net)
2015.01.15 23:05:33: Joining #commits...
Did not get DONE/CLOSE event for Wheel ID 1089 from IP 222.186.34.155 at 
/usr/share/perl5/POE/Component/Server/SimpleHTTP.pm line 221.
I had a problem posting to event Got_Request of session SOAPServer for DIR 
handler '.*'. As reported by Kernel: 'No such file or directory', perhaps the 
session name is spelled incorrectly for this handler? at 
/usr/share/perl5/POE/Session.pm line 483.

I don't know the IP 222.186.34.155. I assume it is trying to exploit my
server with its DIR .*

Since this appears to be at least a DOS, I've tagged the bug as a minor
security issue.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#776422: [systemd] power button does poweroff instead of STR after each upgrade of systemd

[Timo Weingärtner]

Package: systemd
Version: 215-10
Severity: grave
Justification: causes data loss

I configured the power button to do STR in KDE. After each upgrade of systemd 
the power button does poweroff instead causing loss of unsaved work.

This did not happen before the introduction of systemd as a replacement for 
$everything, so I have to guess systemd is the problem; please reassign if you 
know better.


Regards
Timo

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16.0-4-amd64

Debian Release: 8.0
  900 testing http.debian.net 
  800 unstablehttp.debian.net 

--- Package information. ---
Depends (Version) | Installed
=-+-==
libacl1 (>= 2.2.51-8) | 2.2.52-2
libaudit1(>= 1:2.2.1) | 1:2.4-1+b1
libblkid1 (>= 2.17.2) | 2.25.2-4.1
libcap2   (>= 1:2.10) | 1:2.24-6
libcryptsetup4   (>= 2:1.4.3) | 2:1.6.6-4
libdbus-1-3(>= 1.1.1) | 1.8.12-3
libkmod2  (>= 5~) | 18-3
libpam0g(>= 0.99.7.1) | 1.1.8-3.1
libselinux1(>= 2.1.9) | 2.3-2
libsystemd-journal0 (= 208-8) | 
libudev1 (>= 189) | 215-10
libwrap0  (>= 7.6-4~) | 7.6.q-25
libsystemd-login0   (= 208-8) | 
util-linux  (>= 2.19.1-2) | 2.25.2-4.1
initscripts (>= 2.88dsf-53.2) | 2.88dsf-58
sysv-rc   | 2.88dsf-58
udev  | 215-10
acl   | 2.2.52-2
adduser   | 3.113+nmu3
libcap2-bin   | 1:2.24-6


Recommends  (Version) | Installed
=-+-===
libpam-systemd| 215-10


Suggests(Version) | Installed
=-+-===
systemd-ui| 



--- Output from package bug script ---


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

Bug#776421: parted: Segfault on align-check

[Lucio Crusca]

Package: parted
Version: 3.2-6
Severity: normal

While using parted I got the following SIGSEGV report:

(parted) align-check min 1

You found a bug in GNU Parted! Here's what you have to do:

Don't panic! The bug has most likely not affected any of your data.
[...]

# parted /dev/vda unit co print unit s print

Model: Virtio Block Device (virtblk)
Disk /dev/vda: 1136GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End SizeType File system  Flags
 1  1049kB  1136GB  1136GB  primary   boot, lvm

Model: Virtio Block Device (virtblk)
Disk /dev/vda: 2218786816s
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start  End  Size Type File system  Flags
 1  2048s  221875s  2218747953s  primary   boot, lvm


and the following history of commands I entered:

help
select /dev/vda
resize
resizepart
1
max
print devices
resizepart
1
1136GB
align-check min 1

Error: SEGV_MAPERR (Address not mapped to object)
Backtrace has 11 calls on stack:
  11: /lib/x86_64-linux-gnu/libparted.so.2(ped_assert+0x44) [0x7f64ba92d644]
  10: parted() [0x40a934]
  9: /lib/x86_64-linux-gnu/libc.so.6(+0x35180) [0x7f64ba125180]
  8: /lib/x86_64-linux-gnu/libparted.so.2(+0x157a8) [0x7f64ba9357a8]
  7: 
/lib/x86_64-linux-gnu/libparted.so.2(ped_device_get_minimum_alignment+0x1d) 
[0x7f64ba92e11d]
  6: parted() [0x4083d5]
  5: parted() [0x4084e4]
  4: parted(interactive_mode+0xff) [0x40ca2f]
  3: parted(main+0x119f) [0x405f6f]
  2: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f64ba111b45]
  1: parted() [0x405fc7]


Assertion (0) at ../../parted/ui.c:356 in function sa_sigsegv_handler() failed.
  
-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages parted depends on:
ii  libc6 2.19-13
ii  libparted23.2-6
ii  libreadline6  6.3-8+b3
ii  libtinfo5 5.9+20140913-1+b1

parted recommends no packages.

Versions of packages parted suggests:
pn  parted-doc  

-- no debconf information


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

Bug#775395: partman-zfs in d-i jessie image does not create grub-compatible /boot ZFS mirror

[Steven Chamberlain]

Control: severity -1 important

Michael Milligan wrote:
> Package: partman-zfs
> Version: 42
> Severity: grave
> Tags: d-i
> Justification: renders package unusable for ZFS-based install
> 
> (which is probably the reason someone is trying Debian/kFreeBSD .. to
> use ZFS)

Since this is a kfreebsd-any package, and we're not part of the
official stable release, I have to lower this to non-RC severity.

We should still fix it for the GNU/kFreeBSD release though.

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#776420: libreoffice-calc terminates unexpectedly when deleting a row in a spreadsheet

[Hubert]

Package: libreoffice-calc
Version: 1:4.3.3-2
Severity: important
Tags: upstream

Dear Maintainer,

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

   * What led up to the situation?
 I got an Excel file from a friend and edited it with libreoffice.
 As soon as I delete a row, calc crashes

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 delete any row on the first tab of the spredsheet

   * What was the outcome of this action?
 libreoffice closes

   * What outcome did you expect instead?
 one row less in the spreadsheet

   * gdb output:

Starting program: /usr/lib/libreoffice/program/soffice.bin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe7aaa700 (LWP 29932)]
[New Thread 0x7fffe159d700 (LWP 29933)]
[New Thread 0x7fffe0d9c700 (LWP 29934)]
[New Thread 0x7fffda2ed700 (LWP 29935)]
[Thread 0x7fffe159d700 (LWP 29933) exited]
[New Thread 0x7fffe159d700 (LWP 29936)]
[New Thread 0x7fffc700 (LWP 29937)]
[New Thread 0x7fffcf7fe700 (LWP 29938)]
[New Thread 0x7fffcd32c700 (LWP 29939)]
[Thread 0x7fffcd32c700 (LWP 29939) exited]
[Thread 0x7fffcf7fe700 (LWP 29938) exited]
[New Thread 0x7fffcf7fe700 (LWP 29941)]
[New Thread 0x7fffcd32c700 (LWP 29942)]
[New Thread 0x7fffbfba2700 (LWP 29943)]
[New Thread 0x7fffbf3a1700 (LWP 29944)]
[New Thread 0x7fffbe2d0700 (LWP 29945)]
[New Thread 0x7fffbdacf700 (LWP 29946)]
[New Thread 0x7fffbd2ce700 (LWP 29947)]
[New Thread 0x7fffbcacd700 (LWP 29948)]
[New Thread 0x7fffb7fff700 (LWP 29949)]
[New Thread 0x7fffb77fe700 (LWP 29950)]
[New Thread 0x7fffb6ffd700 (LWP 29951)]
[Thread 0x7fffbdacf700 (LWP 29946) exited]
[Thread 0x7fffbd2ce700 (LWP 29947) exited]
[Thread 0x7fffbcacd700 (LWP 29948) exited]
[Thread 0x7fffb7fff700 (LWP 29949) exited]
[Thread 0x7fffb77fe700 (LWP 29950) exited]
[Thread 0x7fffb6ffd700 (LWP 29951) exited]
[Thread 0x7fffbfba2700 (LWP 29943) exited]
[Thread 0x7fffbf3a1700 (LWP 29944) exited]
[Thread 0x7fffcd32c700 (LWP 29942) exited]
[New Thread 0x7fffcd32c700 (LWP 29952)]
[New Thread 0x7fffbf3a1700 (LWP 29953)]
[New Thread 0x7fffbfba2700 (LWP 29954)]
[New Thread 0x7fffb6ffd700 (LWP 29955)]
[New Thread 0x7fffbdacf700 (LWP 29956)]
[New Thread 0x7fffbd2ce700 (LWP 29957)]
[Thread 0x7fffbf3a1700 (LWP 29953) exited]
[Thread 0x7fffbdacf700 (LWP 29956) exited]
[Thread 0x7fffbe2d0700 (LWP 29945) exited]
[Thread 0x7fffb6ffd700 (LWP 29955) exited]
[Thread 0x7fffbfba2700 (LWP 29954) exited]
[Thread 0x7fffcd32c700 (LWP 29952) exited]
[New Thread 0x7fffcd32c700 (LWP 29958)]
[Thread 0x7fffcd32c700 (LWP 29958) exited]
[New Thread 0x7fffcd32c700 (LWP 29959)]
[Thread 0x7fffbd2ce700 (LWP 29957) exited]
[New Thread 0x7fffbd2ce700 (LWP 29960)]
[Thread 0x7fffbd2ce700 (LWP 29960) exited]
[New Thread 0x7fffbd2ce700 (LWP 29961)]
[Thread 0x7fffbd2ce700 (LWP 29961) exited]
[New Thread 0x7fffbd2ce700 (LWP 29962)]
[Thread 0x7fffbd2ce700 (LWP 29962) exited]
[New Thread 0x7fffbd2ce700 (LWP 29963)]
[Thread 0x7fffbd2ce700 (LWP 29963) exited]
[New Thread 0x7fffbd2ce700 (LWP 29964)]
[Thread 0x7fffbd2ce700 (LWP 29964) exited]
[New Thread 0x7fffbd2ce700 (LWP 29965)]
[Thread 0x7fffbd2ce700 (LWP 29965) exited]
[New Thread 0x7fffbd2ce700 (LWP 29966)]
[Thread 0x7fffcd32c700 (LWP 29959) exited]
[New Thread 0x7fffcd32c700 (LWP 29967)]
[New Thread 0x7fffbfba2700 (LWP 29968)]
[Thread 0x7fffbfba2700 (LWP 29968) exited]
[Thread 0x7fffcd32c700 (LWP 29967) exited]
[New Thread 0x7fffbfba2700 (LWP 29970)]
[New Thread 0x7fffcd32c700 (LWP 29971)]
[Thread 0x7fffcd32c700 (LWP 29971) exited]
[Thread 0x7fffbfba2700 (LWP 29970) exited]

Program received signal SIGSEGV, Segmentation fault.
0x7fff92f70634 in ScRangeList::operator[] (this=this@entry=0x2bcf3e8,
idx=idx@entry=0)
at /build/libreoffice-
9dBYD4/libreoffice-4.3.3/sc/source/core/tool/rangelst.cxx:1122
1122/build/libreoffice-
9dBYD4/libreoffice-4.3.3/sc/source/core/tool/rangelst.cxx: No such file or
directory.


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



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

Kernel: Linux 3.19.0-rc6 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libreoffice-calc depends on:
ii  coinor-libcbc32.8.12-1
ii  coinor-libcoinmp1 1.7.6+dfsg1-1
ii  libboost-iostreams1.55.0  1.55.0+dfsg-3
ii  libc6 2.19-13
ii  libgcc1   1:4.9.1-19
ii  libicu52  52.1-7
ii  liblcms2-22.6-3+b3
ii  libmwaw-0.3-3 0.3.1-2
ii  libodfgen-0.1-1   0.1.1-2
ii  liborcus-0.8-00.7.0+dfsg-9
ii  libreoffice-base-core 1:4.3.3-2
ii  libreoffice-core  1:4.3.3-2
ii  librevenge-0.0-0  0.0.1-3
ii 

Bug#770009: Backtrace for the hang

[Vincent Fourmond]

  I've run the build on the MIPS portebox. It hangs on the first SVG
to PNG conversion. Here is a full backtrace. The process is for now
stopped on the porterbox; I think I can leave it for some hours more
at least, if other information could be useful.

  Hope it helps,

  Vincent


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

Bug#776349: grass-gui: wx gui tries to load images from wrong location

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 01/27/2015 07:55 PM, Sebastiaan Couwenberg wrote:
> For some reason the symlinks from the images under /usr/share to
> /usr/lib are missing.

> The symlinks are included in the package, but not on the filesystem
> after installation:

> This problem is limited to the directory symlinks, the symlinks for
> individual files are working fine.

The problem is the switch to symlinks in 6.4.4-1, when upgrading from an
earlier version the existing directories are not replaced by the symlinks.

I've commited a fix using dpkg-maintscript-helper to replace the
directories with symlinks on upgrade. And aim to get it included in the
first stable update of jessie.

As a workaround in the mean time you can purge the grass-gui package and
install it (and the dependencies removed along with grass-gui) again.

Kind Regards,

Bas

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


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

Bug#774266: Wide gamut display not necessary

[Michael Below]

At the start, I thought this was about wide gamut displays. This is
not true, the effect is also visible on normal sRGB displays. It's just
more noticeable if the display has a good quality and you trust the
colors.


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

Bug#775395: partman-zfs in d-i jessie image does not create grub-compatible /boot ZFS mirror

[Steven Chamberlain]

Hi,

Michael Milligan wrote:
> But installing Grub failed with "unknown filesystem".  In
> troubleshooting the issue, it seems grub2 (version currently is
> 2.02~beta2-19) does not recognize the "feature@lz4_compress" option (and
> had been previously reported) of the ZFS pools that kFreeBSD kernel 10.1
> creates.

Thanks for the report.

It is actually expected that grub2 since 2.02 should understand these
feature flags, including LZ4 compression.  I thought it was working for
me when I last tested.

Hopefully this can be figured out without having to default to using
"-d" (disabling new features including LZ4 metadata compression).

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#776418: According to ubuntu reports, this appears to be a regression.

[Olliver Schinagl]

Searching a bit more,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1384297

Ubuntu users notice this as being a regression with the later 3.16 
series of kernels.



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

Bug#536775: granule: Granule closes down whenever I enter "to " as the start of my answer for checking.

[Riley Baird]

> Granule closes itself down whenever I enter "to " as the start of my answer 
> for checking (i.e. 
> the word "to" followed by a space.) It doesn't matter what, if anything, 
> follows "to ".
> 
> I've created a Deck with a single card to test and it doesn't seem to care 
> what words are on the front
>  and back of the card. Entering answers, I've gone through the two letter 
> combinations with "o" as
>  the second letter followed by a space like "ao ", "bo ", etc., and "to " is 
> the only one that crashes
>  Granule. It also happens with the example decks provided on SourceForge.
> 
> As the infinitives of English verbs all begin with "to " you'll understand me 
> doubting myself here when 
> trying a package widely used for language learning.

I've tried to reproduce this bug on the latest version, but I was unable
to. If you still find this issue in the latest version, then let me know.


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

Bug#776419: xdg-utils: xdg-open incorrectly parses .desktop files with Desktop Action sections

[Vladimir Kudrya]

Package: xdg-utils
Version: 1.1.0~rc1+git20111210-7.3
Severity: important
Tags: patch

Dear Maintainer, xdg-open garbles exec arguments when opening files with
something that has [Desktop Action...] sections.
(open_generic funcion)
i.e. 'xdg-open somefile.pdf' will launch:
/usr/bin/qpdfview --unique somefile.pdf qpdfview --unique 
--choose-instance somefile.pdf qpdfview somefile.pdf
instead of 
/usr/bin/qpdfview --unique somefile.pdf

This happens because open_generic_xdg_mime funcion grabs all Exec values from
entire .desktop file regardless of sections.

To correct this, section filter should be added with this patch:
8<---
550c550
< set -- $(sed -n 's/^Exec\(\[[^]]*\]\)\{0,1\}=//p' "$file")
---
> set -- $(sed -n '/^[[:space:]]*\[[Dd]esktop 
> [Ee]ntry\]/,/^[[:space:]]*\[/p' "$file" | sed 
> 's/^Exec\(\[[^]]*\]\)\{0,1\}=//p')
8<---
This way xdg-open will only use Exec from Desktop Entry section.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (900, 'testing'), (400, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8@ISO, LC_CTYPE=ru_RU.UTF-8@ISO (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

xdg-utils depends on no packages.

Versions of packages xdg-utils recommends:
ii  libfile-mimeinfo-perl  0.26-1
ii  libnet-dbus-perl   1.0.0-2+b2
ii  libx11-protocol-perl   0.56-6
ii  x11-utils  7.7+2
ii  x11-xserver-utils  7.7+3+b1

Versions of packages xdg-utils suggests:
pn  gvfs-bin  

-- 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#677456: awesome: status bar vanishes when started with startx and the process gets input on console

[Roland Hieber]

On Mon, Jul 02, 2012 at 06:07:38PM +0200, Roland Hieber wrote:
> I could isolate the issue further, it only happens when I give the
> option --exit-with-session to dbus-launch in my .xinitrc. It also
> happens with other window managers (I tried fluxbox). Without
> --exit-with-session, the issue is gone.

With current behaviour of startx, the issue is no longer relevant. Xorg takes
over the tty anyways and vlock is no longer needed. dbus-launch
--exit-session works fine now.

 - Roland


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

Bug#776400: grub-ieee1275: ppc64el-disable-vsx.patch applied to 32-bit kernel.img causes exception at 0x20000008 (mtmsrd 0)

[Colin Watson]

On Tue, Jan 27, 2015 at 11:17:04AM -0600, Mark wrote:
>  On a powerpc g4 (mac) system I am trying to switch from yaboot to grub.
> The provided image always faults 8 bytes in. Looking at the patches for
> grub I see "ppc64el-disable-vsx.patch" 
> http://anonscm.debian.org/cgit/pkg-grub/grub.git/tree/debian/patches/ppc64el-disable-vsx.patch?id=debian/2.02.beta2-20
> is causing the problem with the "mtmsrd" instruction.
> 
> I think the solution is to not apply this patch for 32-bit builds.

Thanks.  I prefer not to apply patches conditionally.  However, it
should be sufficient to use the mtmsr instruction rather than mtmsrd;
the bit we're trying to change is in the bottom 32 bits of the MSR in
any case.

Please could you test version 2.02~beta2-21 when it becomes available in
unstable (I'm preparing the upload now), and report how it behaves for
you?

Thanks,

-- 
Colin Watson   [cjwat...@debian.org]


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

Bug#776418: linux-base: i915 fails occasionally to suspend

[Olliver Schinagl]

Package: linux-base
Version: 3.5
Severity: important

Dear Maintainer,

The 3.16-series have some kernel bugs with the i915 video driver causing
suspend to occasionally fail. When it fails, it keeps failing and only a reboot
fixes it. This has been noticed on 2013 macbook airs, but I'll keep this report
to my own macbook pro mid 2013.

The kernel trace:
[44652.015163] ---[ end trace 97db4adad9ce9344 ]---
[44652.015182] [ cut here ]
[44652.015201] WARNING: CPU: 0 PID: 735 at /build/linux-
CMiYW9/linux-3.16.7-ckt2/drivers/gpu/drm/i915/intel_pm.c:5997
intel_display_power_put+0x127/0x150 [i915]()
[44652.015204] Modules linked in: bnep ecb btusb bluetooth 6lowpan_iphc pl2303
usbserial cdc_acm binfmt_misc snd_hda_codec_cirrus snd_hda_codec_hdmi
snd_hda_codec_generic iTCO_wdt iTCO_vendor_support hid_generic hid_apple joydev
usbhid bcm5974 hid nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache
sunrpc nls_utf8 nls_cp437 vfat fat evdev applesmc input_polldev
x86_pkg_temp_thermal intel_powerclamp intel_rapl coretemp efi_pstore kvm_intel
kvm crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul
glue_helper ablk_helper cryptd wl(PO) pcspkr efivars cfg80211 rfkill
thunderbolt lpc_ich i2c_i801 mfd_core snd_hda_intel snd_hda_controller
snd_hda_codec i915 sbs sbshc snd_hwdep drm_kms_helper snd_pcm drm ac video
i2c_algo_bit snd_timer battery apple_bl button snd mei_me soundcore i2c_core
[44652.015292]  shpchp mei processor thermal_sys fuse parport_pc ppdev lp
parport autofs4 ext4 crc16 mbcache jbd2 dm_mod sg sd_mod crc_t10dif
crct10dif_generic usb_storage ahci libahci crct10dif_pclmul libata
crct10dif_common crc32c_intel scsi_mod tg3 ptp pps_core libphy xhci_hcd usbcore
usb_common
[44652.015332] CPU: 0 PID: 735 Comm: Xorg Tainted: PW  O
3.16.0-4-amd64 #1 Debian 3.16.7-ckt2-1
[44652.015336] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC,
BIOS MBP111.88Z.0138.B03.1310291227 10/29/2013
[44652.015338]  0009 81507263 
81065847
[44652.015345]  88026544002c 8802631ab000 88026544
000b
[44652.015351]  880265448520 a03af167 8802631ab000
8802631ab000
[44652.015358] Call Trace:
[44652.015364]  [] ? dump_stack+0x41/0x51
[44652.015371]  [] ? warn_slowpath_common+0x77/0x90
[44652.015390]  [] ? intel_display_power_put+0x127/0x150
[i915]
[44652.015415]  [] ? intel_dp_get_modes+0x6c/0x100 [i915]
[44652.015429]  [] ?
drm_helper_probe_single_connector_modes_merge_bits+0x286/0x370 [drm_kms_helper]
[44652.015446]  [] ? drm_mode_getconnector+0x3dd/0x450 [drm]
[44652.015453]  [] ? poll_select_copy_remaining+0x140/0x140
[44652.015468]  [] ? drm_ioctl+0x1c7/0x5b0 [drm]
[44652.015478]  [] ? __hrtimer_start_range_ns+0x1cd/0x390
[44652.015484]  [] ? do_vfs_ioctl+0x2cf/0x4b0
[44652.015490]  [] ? __sys_recvmsg+0x3e/0x80
[44652.015496]  [] ? SyS_ioctl+0x81/0xa0
[44652.015503]  [] ? system_call_fast_compare_end+0x10/0x15
[44652.015506] ---[ end trace 97db4adad9ce9345 ]---

and upstream is some noice about this aswell.
https://freedesktop.org/patch/30470/

00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09)
[2.598451] fbcon: inteldrmfb (fb0) is primary device
[3.996610] i915 :00:02.0: fb0: inteldrmfb frame buffer device
model name: Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz

Thanks,

Olliver



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-base depends on:
ii  debconf [debconf-2.0]  1.5.55
ii  libuuid-perl   0.05-1+b1
ii  udev   215-10
ii  util-linux 2.25.2-4.1

linux-base recommends no packages.

linux-base suggests no packages.

-- debconf information:
  linux-base/disk-id-manual:
  linux-base/disk-id-convert-plan-no-relabel: true
  linux-base/disk-id-convert-plan: true
  linux-base/disk-id-convert-auto: true
  linux-base/disk-id-manual-boot-loader:
  linux-base/do-bootloader-default-changed:
  linux-base/disk-id-update-failed:

-- debsums errors found:
debsums: missing file /usr/share/doc/linux-base/NEWS.Debian.gz (from linux-base 
package)
debsums: missing file /usr/share/doc/linux-base/changelog.gz (from linux-base 
package)
debsums: missing file /usr/share/doc/linux-base/copyright (from linux-base 
package)


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

Bug#773386: release-notes: Systemd related updates to "before reboot" and Recovery proceedures

[Niels Thykier]

Control: tags -1 help

On 2014-12-17 20:37, Niels Thykier wrote:
> Package: release-notes
> Severity: normal
> Tags: jessie
> 
> (X-CC to systemd maintainers for input)
> 
> The release notes have a "Prepare for recovery"[1] and "Things
> to do before rebooting" section[2].  They currently does not cover any
> systemd related preparation.
> 
> I believe we should consider covering some/all of:
> 
>  * My system does not boot after upgrading to systemd.  How do I figure out
>what the problem is and how do I get a shell/some method to fix it?
> 

This seems to have partly forked into #774233, so please follow up with
relevant information to that.

>  * Is there someone I can do to check for issues after upgrading but before
>rebooting?  Like do we have a tool to report:
>- There are cycles in your init configuration between the following
>  services / init.d scripts.
>- You have an old init.d script laying around that is likely to break
>  stuff because of reason X
>- etc.
> 

Still hoping for more information here.  I would strongly prefer that we
could have users test their box before hitting reboot.

> 
> So far, I got following for recovery:
> 
>   * (When boot fails) Reboot and alter kernel command line to include
> "systemd.unit=rescue.target".

Covered in #774233

>   * (Before reboot or from rescue shell) Run systemctl enable
> debug-shell.service to get a (passwordless) root shell on TTY9
> "just in case"

Should possibly be included in #774233 as well, but I forgot it in my draft.

>   * (Before upgrade) Back up /sbin/init and use it on the kernel cmd line
>  as last resort [Presumably Jessie-only]
> 

As Andrei pointed out, the sysvinit package handles this.

> 
> On the "before reboot", I got nothing so far.  I am hoping you do.
> 
> If you got known issues to be documented in the Release Notes (or
> other suggestions for improvements), please file additional bugs.
> We got some items covered in [3], but I would not be surprised if I
> had missed one or some of the existing ones could be improved.
> 
> Thanks,
> ~Niels
> 
> [...]

Such extra bugs are still welcome!

~Niels


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

Bug#776263: tecnoballz: Right click cause game over

[Bruno Ethvignot]

Hi,

Le 27/01/2015 02:34, Celelibi a écrit :

2015-01-26 16:22 UTC+01:00, Markus Koschany :

Apparently, right clicking when loosing the last ball cause a game
over instead of simply loosing a life. It seems that this bug is easier
to reproduce when the ball is falling vertically. At least I could get
to reproduce it fairly easily by repeteadly right clicking while missing
the ball falling straight.

Hello and thanks for your reports,
I'm CCing Bruno because he is the upstream developer for tecnoballz and
might be interested in your bug reports too. I'm replying to all of them
separately.
@bug 776263
I can confirm that repeatedly right-clicking sometimes triggers "game
over" instead of just losing a life when the player misses the ball.
However this behaviour is rather random. It doesn't always have to be
the last ball.

FWIW: this bug can be reliably triggered by holding the right click
pressed and losing the last ball. I cannot reproduce the bug when it's
not the last ball that is lost.


I was able to reproduce the bug. I confirm.

--
Bruno


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

Bug#475728: spell error for a surname in the description file and adding a link

[Riley Baird]

> The file talks about Leither instead of Leitner (according to the
> homepage of the granule program):
> http://granule.sourceforge.net/grapp_about.html

Good pickup. This will be fixed in the next version.

> It could be a good idea to add a reference to the page of the project
> too at the end of the file. A lot of description files do it:
> Homepage: http://granule.sourceforge.net/

It seems like this part has already been fixed.


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

Bug#776417: fai-cd Not Using /boot/grub/i386-pc when $NFSROOT is jessie+ and FAI server is not

[Kevin Newman]

Package: fai-server
Version: 4.3.1
Severity: normal

Hi,

So, my NFSROOT is now higher than the server on which I'm running fai-server. 
My NFSROOT is Ubuntu Trusty and my fai-server is Ubuntu precise. The fai-cd 
script seems to be checking the kernel.img for the GRUB modules path in my FAI 
server rather than the kernel.img inside the $NFSROOT.

Current version of /usr/sbin/fai-cd:
100 # check for jessie path
101 if strings /usr/lib/grub/i386-pc/kernel.img | grep -q i386-pc/%s.mod; 
then
102 grubtarget=$tmp/boot/grub/i386-pc
103 else
104 # wheezy
105 grubtarget=$tmp/boot/grub
106 fi


Change to this?
100 # check for jessie path
101 if strings $NFSROOT/usr/lib/grub/i386-pc/kernel.img | grep -q 
i386-pc/%s.mod; then
102 grubtarget=$tmp/boot/grub/i386-pc
103 else
104 # wheezy
105 grubtarget=$tmp/boot/grub
106 fi


Without this change, booting off the resultant FAI CD results in GRUB stopping 
with an error of "error: file '/grub/i386-pc/normal.mod' not found". A simple 
ls of (cd0)/boot/grub shows that the modules are indeed present, just not in 
the i386-pc directory that Trusty/jessie expects them.

Also, I apologize for the previous bug reports - it does look like those paths 
are valid even with the two slashes in the middle of the filesystem path.

Thanks,

-Kevin

__

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to 
this email

Bug#774233: systemd shell

[Niels Thykier]

Control: tags -1 patch

On 2014-12-30 17:10, Antoine Beaupré wrote:
> And actually, maybe it should be a subsection like 4.1.4.1 that would be
> refered to by 5.5...
> 

Hi,

Thanks for reporting this.

The attached patch attempts to cover a basic 4.1.4.2 section for
describing how to obtain a shell under systemd if booting fails.
Admittedly, it lacks a reference from 5.5, but that should be fairly
trivial once the contents of 4.1.4.2 is in place.

A review would be greatly appreciated.

Thanks,
~Niels


diff --git a/en/upgrading.dbk b/en/upgrading.dbk
index 4bbc849..394b60f 100644
--- a/en/upgrading.dbk
+++ b/en/upgrading.dbk
@@ -189,7 +189,32 @@ course you will also need to fix the underlying problem and regenerate the
 initrd so the next boot won't fail again.
 
 
-
+
+  Debug shell during boot using systemd
+  
+In case the boot fails under systemd, it is possible to obtain a
+debug root shell by changing the kernel command line.  If the
+basic boot succeeds, but some of the services fails to start, it
+may be useful to add systemd.unit=rescue.target
+to the kernel parameters.
+  
+  
+Otherwise, the kernel parameter
+systemd.unit=emergency.target will provide you
+with an root shell at the earliest possible point.  However, this
+is done before mounting the root file system with read-write
+permissions.  You will have to do that manually with:
+  
+  
+mount -o remount,rw /
+  
+  
+For more information on debugging a broken boot under systemd
+can be found in the http://freedesktop.org/wiki/Software/systemd/Debugging/";>
+Diagnosing Boot Problems article.
+  
+
 
 
 

Bug#669785: websvn attempts to install its configuration file in /etc/apache2/conf.d/

[Nye Liu]

Package: websvn
Version: 2.3.3-1.2
Followup-For: Bug #669785

On post install:

"failed to create symbolic link ‘/etc/apache2/conf.d/websvn’: No such file or 
directory"

Why is websvn still trying to install files to /etc/apache2/conf.d/?

That has been gone for years.

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

Kernel: Linux 3.13.7-x86_64-linode38 (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 websvn depends on:
ii  apache2 [httpd]2.4.10-9
ii  debconf [debconf-2.0]  1.5.52
ii  libapache2-mod-php55.6.4+dfsg-2
ii  php-geshi  1.0.8.11-2
ii  php5   5.6.4+dfsg-2
ii  po-debconf 1.0.16+nmu2
ii  subversion 1.8.10-5
ii  ucf3.0027+nmu1

Versions of packages websvn recommends:
ii  enscript  1.6.5.90-2

websvn suggests no packages.

-- debconf information:
* websvn/repositories: /var/lib/svn
* websvn/permissions:
* websvn/configuration: true
* websvn/parentpath: /var/lib/svn
* websvn/webservers: apache2


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

Bug#776416: kfreebsd-10: CVE-2014-8613: SCTP stream reset vulnerability

[Steven Chamberlain]

Package: kfreebsd-10
Version: 10.1~svn274115-1
Severity: grave
Tags: security patch

Hi,

A unprivileged local DoS was reported in the FreeBSD kernel
implementation of SCTP:
https://security.freebsd.org/advisories/FreeBSD-SA-15:03.sctp.asc

This only affects systems serving SCTP connections.  A patch from
upstream should be uploaded soon fixing this in kfreebsd-10.

kfreebsd-9 in stable is not affected, since the last security upload
9.0-10+deb70.8 disabled this protocol.

kfreebsd-8 does not receive regular security updates, but we may decide
to disable SCTP there too.  (It's expected nobody would be using SCTP in
GNU/kFreeBSD squeeze or prior, because no userland tools had been ported
yet).

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


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

Bug#776415: kfreebsd-10: CVE-2014-8612: SCTP kernel mem disclosure/corruption

[Steven Chamberlain]

Package: kfreebsd-10
Version: 10.1~svn274115-1
Severity: grave
Tags: security patch

Hi,

A kernel memory disclosure/corruption vulnerability was announced,
in the FreeBSD kernel's implementation of SCTP:
https://security.FreeBSD.org/advisories/FreeBSD-SA-15:02.kmem.asc

This could affect the kfreebsd-10 package if SCTP is used.  A patch
from upstream should be uploaded soon fixing this.

kfreebsd-9 in stable is not affected, since the last security upload
9.0-10+deb70.8 already disabled this protocol.

kfreebsd-8 does not receive regular security updates, but we may decide
to disable SCTP there too.

kfreebsd-11 experimental will be affected until updated to a newer
snapshot.

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


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

Bug#775202: Add support for running a 64-bit Linux kernel on a 32-bit EFI

[Colin Watson]

On Mon, Jan 12, 2015 at 04:24:24PM +, Steve McIntyre wrote:
> On Mon, Jan 12, 2015 at 03:17:39PM +, Colin Watson wrote:
> >This all looks reasonable enough, but why not "return is_64_kernel () ?
> >64 : 32;" here?  Then you could simplify
> >grub_install_get_default_x86_platform to just conditionalise on "if
> >(read_platform_size () == 64)" and avoid duplication.
> 
> Could do, yes. I personally tend to shy away from ternary usage like
> that, but meh. :-)

I meant this as a rough sketch rather than literal code ...

> OK, how about:

Looks good, thanks!  Sorry for the delay in reviewing this.  I've pushed
it to the Debian master branch.

-- 
Colin Watson   [cjwat...@debian.org]


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

Bug#404163: Granule documentation

[Riley Baird]

Hi,

As much as I'd like to include the documentation, I've checked and it
doesn't seem to have license information associated with it. I'll write
to upstream so that we can hopefully work out what license it was
intended to be under.

Yours sincerely,

Riley Baird


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

Bug#639984: please reconsider clearing DISPLAY in lightdm startup script

[chrysn]

hello yves-alexis,

i'd like to ask you to reconsider your stance on clearing the DISPLAY
variable in the lightdm startup script.

granted, calling `/etc/init.d/lightdm restart` may not be the preferred
way of starting and stopping services any more, but as long as those
scripts don't actively resist invocation, they will be used.

while it's probably even a good idea that the lightdm binary does
something reasonable in the presence of DISPLAY, i'm pretty sure that
the lightdm instance started by the init script is never supposed to be
used in connection with a pre-set environment variable -- as you noted,
the more modern invocations of init scripts would clean that out anyway.

the situation i've ended up is similar to those situations described
earlier -- display went blank, trying to get the box up and running from
remote again, and DISPAY being set. the altered behavior of lightdm in
that situation is subtle to debug. the way Xephyr fails ("Unrecognized
option: -novtswitch / use: X [:] [option]") doesn't help
either. i ended up grepping through the lightdm source code when i
discovered the Xephyr thing until i unset the DISPLAY variable and later
found this bug report. a warning along the lines of `env |grep
'^DISPLAY=' >/dev/null && echo 'Warning: DISPLAY set, lightdm will
misbehave. Use invoke-rc.d instead.'` would have helped a lot.

i'm not saying that the lightdm init script is wrong in not clearing
DISPLAY if init scripts may rely on having a cleaned environment. but as
long as this is not enforced, lightdm failing to be started from the
init script under the described conditions is a very harsh way of
educating users.

best regards
chrysn

-- 
Most people would leave. Not us. We're Vikings. We have stubbornness issues.
  -- Hiccup, son of Stoic


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

Bug#404163: Granule documentation license

[Riley Baird]

Hi!

I'm fixing some bugs for your "granule" program in Debian. Someone
requested that I add your documentation to the package. However, I can't
seem to find the license of the documentation, and Debian requires a
license before I can package it.

Can you please provide a free license for the documentation?

Yours thankfully,

Riley Baird


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

Bug#774899: libdrm-intel1: 855GM: Failed to submit batch buffer, expect rendering corruption: No space left on device

[Matthias Großmann]

Update on this bug: My first assumption that
drm_intel_gem_check_aperture_space() causes this problem is probably
wrong. As it turned out, this function fails a lot more often than I
see the "failed to submit batch buffer" message in Xorg.0.log - in
general without any noticeable impact.

After enabling some more debug output, I am now seeing the error
message

Execbuffer fails to pin. Estimate: 234897408. Actual: 67125248. Available: 
130940928

so I guess that the DRM_IOCTL_I915_GEM_EXECBUFFER2 ioctl in do_exec2()
causes the failure.

LibreOffice's print dialog can (sometimes) also trigger this bug.


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

Bug#776414: Blurry EFI splash

[jnqnfe]

Package: debian-cd

When an official Debian disc image is loaded on a system with EFI, the
bootloader is displayed at at size of 800x600, larger than that used on
BIOS systems (640x480). The disc images include a bootloader splash
image (found in the syslinux directory) which has dimensions of 640x480
however, which is displayed sharp and clear on BIOS systems, but on EFI
systems, this splash image is stretched up to 800x600 making it blurry.

Please either swap the 640x480 image with an 800x600 one (presuming
syslinux will scale it down correctly), or include an additional 800x600
sized one for the grub (EFI) bootloader to use.

I have attached a copy of an updated/alternative 'Lines' theme svg,
which I also sent to the debian-cd team recently for consideration. This
uses the latest 'Lines' theme assets (I noticed tiny differences in the
logo compared to the current png that is available in the debian-cd_info
archive available on the mirrors), and I made an attempt to clean up the
'GNU/Linux' text (which someone other than the theme author has added on
top and imo looked messy).

CC-ing the debian-installer team, since the debian-cd_info archive is
held under the installer directories on the mirrors.

Bug#775921: unblock: torbrowser-launcher/0.1.8-1 (pre-approval)

[Holger Levsen]

Hi,

On Dienstag, 27. Januar 2015, Niels Thykier wrote:
> Ack, please go ahead and remove the moreinfo tag once it has been
> uploaded to unstable.

thanks! but sadly 0.1.8-1 is not suitable and probably I dont want 0.1.9-1 
neither, the changes due to github tickets #155 and 157 might be too 
invasive/unsafe...

So maybe the diff will be even smaller than 0.1.8-1 in which case i'll just 
upload to sid as 0.1.7+debian-1. If we decide to go with 0.1.9-1 instead, I'll 
come back to you first though.

de13483 (from 0.1.8) and 3f1146e (from 0.1.9, fixing de13483) are the 
problematic upstream commits I'm talking about...


cheers,
Holger




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

Bug#767067: Retitling

[Lisandro Damián Nicanor Pérez Meyer]

On Tuesday 27 January 2015 15:57:00 you wrote:
> Hello Lisandro,
> 
> Am Montag, den 26.01.2015, 18:50 -0300 schrieb Lisandro Damián Nicanor
> Pérez Meyer:
> [...]
> 
> > Hi! I have just uploaded Choqok 1.5 to experimental untill the freeze is
> > over. If you use sid it should be quite straightforward to test, you can
> > also wait until it gets into unstable/testing.
> 
> If have tested Choqok 1.4-1:
> 
> First with kwallet with the result that Choqok lost the auth data many
> times in a day.
> 
> The I tested it with the gnome-keyring. With them it work very well,
> since weeks no data lose :-)
> 
> For verifying I test it again with kwallet -->> lost data.

Interesting, because I was also suspecting a problem with kwallet.

> Now I have Choqok 1.5-1 installed and I test it again.

I'll wait for your tests then :)

-- 
15: Que es el "Correo Electronico"
* El correo que te llega por la corriente
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

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


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

Bug#770533: release-notes: [jessie]: add note about removal of lire (once Bug#770532 has been dealt with)

[Niels Thykier]

On Sat, 22 Nov 2014 06:14:41 +0100 Joost van =?utf-8?Q?Baal-Ili=C4=87?=
 wrote:
> Package: release-notes
> Severity: wishlist
> 
> Hi,
> 
> Once Bug#770532: (RM: lire) has been closed, we should probably add a note
> about why lire is not shipped with Debian jessie and mention alternatives
> (webalizer and friends).
> 
> Bye,
> 
> Joost
> 
> PS: I'll likely fix this bug myself.  Don't let that stop you from fixing it
> earlier, though!
> [...]

Hi Joost,

Any news on this? :)

~Niels


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

Bug#776413: Policy violation: ed priority "optional", should be "important"

[Pigeon]

Package: ed
Version: any

The priority of the ed package has been changed to "optional".
According to the changelog this is apparently for no reason other than
a response to bug #416585, the content of which is simply one person's
suggestion which he makes without providing any justification beyond
his personal whim.

The Debian policy manual
http://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities
says: "If the expectation is that an experienced Unix person who found
it missing would say "What on earth is going on, where is foo?", it
must be an important package." Surely it is beyond question that this
applies to ed. Anyone needing to edit a file via a simple
line-oriented interface on a Unix-like system will automatically reach
for ed and will be most disconcerted to find it missing. And certainly
ed used to have priority "important" as this suggests it should.

The assertion in bug #416585 that "anyone who wants it can easily
install it" is not true. The principal value of ed is that it is an
editor which works when nothing else does. If the system is broken, or
incompletely installed, or only accessible via the most primitive of
interfaces, or in other situations of a like kind, which are the sort
of situations in which ed or an equivalent is likely to be the only
editor that is usable at all, it is also highly likely that installing
ed (or anything else for that matter) will be impossible. And the lack
of a functional editor makes it many times harder to fix whatever
problem has given rise to the need for it.

I have recently been caught this way a couple of times myself. In one
case I was able to copy /bin/ed from another system onto a USB stick
and use that. In another I had to use yucky workarounds like
sed -i -e 'editing commands' 'filename'.

Another virtue of ed is that it is possible to use it to patch
binaries without the risk that arises with less primitive editors of
some automatic formatting function messing the whole thing up. For
instance if a hard-coded pathname is causing problems then ed is
capable of changing it to something else of the same or shorter length
with no collateral damage. The kind of situation in which such a problem
is likely to arise is also the kind of situation in which editing the
source and recompiling is likely to be impossible.

In short, not only is it a policy violation for ed to have priority
"optional", it also means that an important repair and rescue tool is
likely to be unavailable when it is most needed. Therefore I strongly
suggest that the priority for ed be reset to "important".

-- 
Pigeon

Be kind to pigeons- -Pigeon's Nest: http://pigeonsnest.co.uk/
GPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F


signature.asc
Description: Digital signature

Bug#775882: [debian-mysql] Bug#775882: mariadb-10.0: affected by CVEs of the Oracle Patch Update for January 2015?

[Salvatore Bonaccorso]

Hi Otto,

On Tue, Jan 27, 2015 at 09:20:51PM +0200, Otto Kekäläinen wrote:
> 2015-01-27 8:09 GMT+02:00 Salvatore Bonaccorso :
> > Thanks for the update and checking with upstream regarding the two
> > other CVEs. 10.0.16 seems now avaiable[1] (even though not yet
> > announced on the webpage itself).
> >
> >  [1]  https://downloads.mariadb.com/files/MariaDB/mariadb-10.0.16/source
> 
> 
> 10.0.16 has now been officially announced and I've updated both the
> master and jessie branches of the Debian packaging repo:
> http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/
> 
> Local builds pass OK. Currently I am running with the full test suite
> etc and if they pass I'll upload master to experimental, and if it is
> fully OK, I'll update jessie branch to unstable. As Jessie is not
> released, there is no jessie-security upload target yet, right?

Yes right, so release team needs to ack it and give an unblock for it.
I hope this will be not problem, so that we can have alreayd
mariadb-10.0/10.0.16-1 in jessie.

Thanks for your work and keeping us up-to-date,

Regards,
Salvatore


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

Bug#745195: status

[Willi Mann]

Control: tag -1 + pending

I've upgraded this bug to RC status because it is a regression from
wheezy. It is especially bad because it may bite some reverse
dependencies that use unrtf as part of a processing chain.

Salvatore Bonaccorso has already proposed a fix for this bug, based on
the upstream fix in newer versions.

WM


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