date:20141009

On Thu, 19 Jun 2014 15:37:19 +0800 Sphinx Jiang  wrote:
> Index: ctfutils-9.2/sys/cddl/contrib/opensolaris/uts/common/sys/isa_defs.h
> ===
> --- ctfutils-9.2.orig/sys/cddl/contrib/opensolaris/uts/common/sys/isa_defs.h  
>   2011-02-28 03:41:40.0 +0800
> +++ ctfutils-9.2/sys/cddl/contrib/opensolaris/uts/common/sys/isa_defs.h 
> 2014-06-19 15:22:27.320825153 +0800
> @@ -403,7 +403,7 @@
>  #define_INT_ALIGNMENT  4
>  #define_FLOAT_ALIGNMENT4
>  #define_FLOAT_COMPLEX_ALIGNMENT4
> -#if defined(__mips_n64)
> +#if defined(__mips64)

Ohh, on N32 project __mips64 is also defined, it means that 64bit
registers are available.
So for N64, we should use

#if defined(__mips64) && defined(__LP64__)

>  #define_LONG_ALIGNMENT 8
>  #define_LONG_LONG_ALIGNMENT8
>  #define_DOUBLE_ALIGNMENT   8

I NMUed it with the attached patch.


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

Bug#758165: gcc-4.9 devirtualisation bug affecting wxwidgets3.0 now fixed

Control: tags 758165 +fixed pending

[Dropped CC to #755361 as it is archived and mail bounces]

On Fri, Oct 10, 2014 at 08:10:16AM +0300, Niko Tyni wrote:
> On Wed, Oct 08, 2014 at 10:43:30PM +0100, Olly Betts wrote:
> > Even if the issue is header-only, it would definitely be good to retest
> > with 3.0.2-1 (in unstable only currently) in case there are changes in
> > the new upstream version which have solved this issue, especially as
> > Johan reports sage now builds OK.
> 
> It seems to be fixed with 3.0.2-1 on armel at least. I was able
> to build libwx-perl without the workarounds and the tests passed
> fine. So I guess #758165 can be closed (!)

Awesome, thanks for checking.

> I'll do a sourceful upload of libwx-perl removing the workarounds soonish.
> Not sure if I should wait for wxwidgets 3.0.2-1 to transition first.

I think it's reasonable to just upload libwx-perl now - I believe
3.0.2-1 is a pretty safe update, and we can always make a new upload
restoring the workaround to libwx-perl in the highly unlikely event
there's an RC issue with 3.0.2-1 which can't be fixed for jessie.

And if #758165 isn't full addressed, knowing sooner would improve the
chances of being able to do something about it, and having it auto-built
on all architectures is the best way to find any remaining issue.

Cheers,
Olly

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

Bug#764620: rxvt-unicode: borderLess incorrectly sets Override Redirect making window unusable.

2014-10-09 Thread Ryan Kavanagh

tags 764620 +moreinfo
thanks

Hi,

On Thu, Oct 09, 2014 at 06:31:30PM +0200, Micke Karls wrote:
> Trying to launch a terminal without window decorations using the borderLess
> option in rxvt-unicode I noticed that it not only removes window decorations
> but also sets "Override Redirect" which renders the window useless. 

Which window manager(s) are you using? This bug is very reminiscent of
https://bugs.kde.org/show_bug.cgi?id=172028 .

Best wishes,
Ryan


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

Bug#764532: guile-2.0: please build with the default gcc on armhf

2014-10-09 Thread Aurelien Jarno

On Thu, Oct 09, 2014 at 02:28:24PM -0500, Rob Browning wrote:
> tags 764532 pending
> thanks
> 
> Aurelien Jarno  writes:
> 
> > guile-2.0 is using gcc-4.8 on armel and armhf to workaround some bugs.
> > I have just done some test builds with gcc-4.9, the recently backported
> > from upstream fix the issues on armhf.
> 
> OK, this should be handled in the next upload.  Any idea if that fix (or
> something similar) might help armel?

No unfortunately, so far I have no idea how to fix armel.

Aurelien

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


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

Bug#761935: shine: ftbfs on mips64el

I nmued this package to delay-5 with the attached patch.

On Fri, Oct 10, 2014 at 9:50 AM, Aníbal Monsalve Salazar
 wrote:
> Control: severity -1 important
>
> On Wed, 2014-09-17 10:44:47 +0800, YunQiang Su wrote:
>> Package: shine
>> Version: 3.1.0-2
>>
>>
>> In debian/rules, there are lines:
>>
>> ifneq (,$(findstrings mips,$(DEB_HOST_ARCH)))
>> CFLAGS+= -mips32r2
>> export CFLAGS
>> endif
>>
>> It will make all mips* ports use mips32r2.
>>
>> change it to
>>
>> ifneq (,$(filter mips mipsel,$(DEB_HOST_ARCH)))
>>
>> can fix this problem.
>>
>> --
>> YunQiang Su
>
> Hello Romain,
>
> YunQiang forgot to set the severity of this bug report.
>
> Port bugs are at least important. ;-)
>
> Cheers,
>
> Aníbal


shine.debdiff
Description: Binary data

Bug#758165: gcc-4.9 devirtualisation bug affecting wxwidgets3.0 now fixed

2014-10-09 Thread Niko Tyni

On Wed, Oct 08, 2014 at 10:43:30PM +0100, Olly Betts wrote:
> On Wed, Oct 08, 2014 at 11:22:20PM +0300, Niko Tyni wrote:

> > I've filed #764525 to fix the uninstallability in sid and can re-test
> > when the binNMUs are built. The porter box setup doesn't really allow for
> > manually built binaries or mixing distributions AFAICS.
> 
> Even if the issue is header-only, it would definitely be good to retest
> with 3.0.2-1 (in unstable only currently) in case there are changes in
> the new upstream version which have solved this issue, especially as
> Johan reports sage now builds OK.

It seems to be fixed with 3.0.2-1 on armel at least. I was able
to build libwx-perl without the workarounds and the tests passed
fine. So I guess #758165 can be closed (!)

I'll do a sourceful upload of libwx-perl removing the workarounds soonish.
Not sure if I should wait for wxwidgets 3.0.2-1 to transition first.
-- 
Niko Tyni   nt...@debian.org


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

Bug#764540: wheezy-pu: package glibc/2.13-38+deb7u5

2014-10-09 Thread Aurelien Jarno

On Thu, Oct 09, 2014 at 10:29:25PM +0100, Adam D. Barratt wrote:
> On Thu, 2014-10-09 at 01:16 +0200, Aurelien Jarno wrote:
> > On Wed, Oct 08, 2014 at 11:27:30PM +0100, Adam D. Barratt wrote:
> > > Control: tags -1 + confirmed
> > > 
> > > On Wed, 2014-10-08 at 23:49 +0200, Aurelien Jarno wrote:
> > > > I would like to do an update of eglibc in wheezy, with the patches we
> > > > have accumulated in the SVN over the last months. I understand that
> > > > it's a bit late with the stable release schedule, that said all this
> > > > patches have been upstream and in jessie/sid for months.
> [...]
> > > Please go ahead; thanks.
> > > 
> > 
> > Thanks! I have just uploaded it.
> 
> A few other changes appear to have been included:
> 
>  debian/TODO |   33 
>  debian/debhelper.in/glibc-doc.install   |4 
>  debian/debhelper.in/glibc-doc.links |   17 
>  debian/debhelper.in/glibc-doc.manpages  |8 
> 
> were those intentional?

Oh I prepared my diff using the SVN and didn't notice that. It wasn't
intentional to add them, but on the other hand they have been removed by
mistake in the security team uploads deb7u3 and deb7u4. This means the
current glibc-doc is missing most of the documentation compared to
deb7u2, strange that we haven't got any bug report for that.

So we should keep these files to restore the documentation as it was
before. Should I do another upload mentioning in the changelog these
files have been added back?

Regards,
Aurelien

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


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

Bug#764672: chromium: GTK theme error: Unable to locate theme engine in module_path: "pixmap"

2014-10-09 Thread Federico Bruni

Package: chromium
Version: 37.0.2062.120-3
Severity: minor

Dear Maintainer,

The error mentioned in the subject disappears when I install 
gtk2-engines-pixbuf.
Perhaps it should be added as a dependency?

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

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

Versions of packages chromium depends on:
ii  gconf-service3.2.6-3
ii  libasound2   1.0.28-1
ii  libc62.19-11
ii  libcairo21.12.16-5
ii  libcap2  1:2.24-6
ii  libcups2 1.7.5-4
ii  libdbus-1-3  1.8.8-2
ii  libexpat12.1.0-6
ii  libfontconfig1   2.11.0-6.1
ii  libfreetype6 2.5.2-2
ii  libgcc1  1:4.9.1-16
ii  libgconf-2-4 3.2.6-3
ii  libgdk-pixbuf2.0-0   2.31.1-2
ii  libglib2.0-0 2.42.0-2
ii  libgnome-keyring03.12.0-1
ii  libgtk2.0-0  2.24.24-1
ii  libharfbuzz0b0.9.35-1
ii  libjpeg621:1.3.1-6
ii  libnspr4 2:4.10.7-1
ii  libnspr4-0d  2:4.10.7-1
ii  libnss3  2:3.17.1-1
ii  libpango-1.0-0   1.36.8-2
ii  libpangocairo-1.0-0  1.36.8-2
ii  libspeechd2  0.8-6
ii  libspeex11.2~rc1.2-1
ii  libstdc++6   4.9.1-16
ii  libudev1 215-5+b1
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1
ii  libxdamage1  1:1.1.4-2
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2
ii  libxi6   2:1.7.4-1
ii  libxml2  2.9.1+dfsg1-4
ii  libxrandr2   2:1.4.2-1
ii  libxrender1  1:0.9.8-1
ii  libxslt1.1   1.1.28-2+b1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1
ii  xdg-utils1.1.0~rc1+git20111210-7.1

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-inspector  
ii  chromium-l10n   37.0.2062.120-3

-- Configuration Files:
/etc/chromium/default [Errno 2] File o directory non esistente: 
u'/etc/chromium/default'
/etc/chromium/initial_bookmarks.html [Errno 2] File o directory non esistente: 
u'/etc/chromium/initial_bookmarks.html'
/etc/chromium/master_preferences [Errno 2] File o directory non esistente: 
u'/etc/chromium/master_preferences'

-- 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#764647: `mdadm_env.sh`, referenced in systemd service file, not provided

2014-10-09 Thread Michael Tokarev

10.10.2014 01:25, Paul Menzel wrote:
> Package: mdadm
> Version: 3.3.2-2
> Severity: normal
> 
> Dear Debian folks,
> 
> 
> looking through `journalctl -b -a` I noticed the line below.
> 
>   Failed at step EXEC spawning /usr/lib/systemd/scripts/mdadm_env.sh: No 
> such file or directory
> 
> But I am unable to find that script in the package. Could you please add
> it or first check for its existence before trying to execute it?

As far as I understand, it is exactly how it supposed to be used, from
systemd/mdmonitor.service:

[Service]
Environment=  MDADM_MONITOR_ARGS=--scan
EnvironmentFile=-/run/sysconfig/mdadm
ExecStartPre=-/usr/lib/systemd/scripts/mdadm_env.sh
ExecStart=/sbin/mdadm --monitor $MDADM_MONITOR_ARGS

Why systemd ignores the leading minus sign?


> PS: The following was printed to the terminal while running `reportbug
> mdadm`.

That should be revisited, it does lots of stuff, mostly assuming a problem
is in array assemble.  Please note however that your arrays are degraded,
which probably should be fixed.

> --- /proc/mdstat:
> Personalities : [raid1] 
> md0 : active raid1 sda1[0]
>   497856 blocks [2/1] [U_]
>   
> md1 : active raid1 sda2[0]
>   1953013952 blocks [2/1] [U_]

Thanks,

/mjt


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

Bug#748911: src:opal: FTBFS on 64 bits arch

NUMed with this patch.

On Thu, Oct 9, 2014 at 8:31 PM, Mauricio Faria de Oliveira
 wrote:
> Hi YunQiang,
>
> On 09/27/2014 01:12 AM, YunQiang Su wrote:
>> Can any ppc64el and arm64 guys help to test this patch?
>
> On 10/07/2014 11:58 PM, YunQiang Su wrote:> I will NMU ptlib with the
> attached debdiff.
>> If you don't agree with it, please cancel it or ask me to do it.
>
> Sorry for missing this one for a few days.
>
> For ppc64el, there's a small change required, because the machine
> name is powerpc64le (suffix 'le' vs. 'el'):
>
> $ sed 's,ppc64el | powerpc64el,powerpc64le,' -i ptlib.debdiff
>
> With that change, the ptlib package built successfully, and configure
> messages changed:
>
> from:
> configure: WARNING: "CPU powerpc64le not recognized - proceed with
> caution!"
> configure: OSTYPE set to linux
> configure: OSRELEASE set to "3.16-trunk-powerpc64le"
> configure: MACHTYPE set to powerpc64le
>
> to:
> configure: OSTYPE set to linux
> configure: OSRELEASE set to "3.16-trunk-powerpc64le"
> configure: MACHTYPE set to ppc64
>
>
> Thanks!
>
> --
> Mauricio Faria de Oliveira
> IBM Linux Technology Center
>



-- 
YunQiang Su


ptlib.debdiff
Description: Binary data

Bug#763278: gcc 4.9 wheezy-pu?

2014-10-09 Thread Adam D. Barratt

On Thu, 2014-10-09 at 23:01 -0400, Michael Gilbert wrote:
> Note that the window for the next stable update is closing in about a
> week, so there isn't a lot of time.

Actually, the /point release/ is in about a week. The advertised window
for getting updates in to it closes this weekend.

Regards,

Adam


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

Bug#764669: kinit without username, behaviour changes betweek wheezy and jessie

2014-10-09 Thread Benjamin Kaduk

On Thu, 9 Oct 2014, Mike Gabriel wrote:

> the behaviour of kinit changed after an upgrade from Debian wheezy to Debian 
> jessie (around 2014-10-10).
>
> Previously it was possible to simply say
>
>  $ kinit
>
> on the command line and kinit then would assume my current user as username 
> for obtaining a ticket for the default Kerberos realm.
>
> Since my upgrade, I have to always specify the Kerberos username when 
> executing kinit:
>
>  $ kinit mike
>
> This alone is only a bit inconvenient. However, this change of behaviour
> breaks the krb5-auth-dialog applet.
>
> Maybe you have an idea why this change occurred and maybe this bug needs
> to be reassigned to krb5-auth-dialog and maybe other tools that depend
> on kinit.

So, what is the observed behavior of just 'kinit' in the failing case?
I.e., how does it fail?

The selection of what client principal to use has some number of
fallbacks, if I remember correctly.

-Ben Kaduk


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

Bug#764671: No longer works with Subversion

2014-10-09 Thread Ben Hutchings

Package: meld
Version: 3.12.0-1
Severity: important

Since upgrading from 1.8, Meld does not show any changes in a
Subversion working copy.  It does appear to recognise it as
version-controlled, in that it can compare a single file or directory.
But it shows the parent version as being the same as the working
version.

Ben.

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

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

Versions of packages meld depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  gir1.2-gtksource-3.0 3.14.0-1
ii  libcanberra-gtk3-module  0.30-2.1
ii  libgtk-3-0   3.14.1-1
ii  libgtksourceview-3.0-1   3.14.0-1
ii  patch2.7.1-6
ii  python   2.7.8-1
ii  python-gi3.14.0-1
ii  python-gi-cairo  3.14.0-1
pn  python:any   

Versions of packages meld recommends:
ii  yelp  3.14.0-1

meld 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#764670: [libturbojpeg1] Please clarify description

2014-10-09 Thread Filipus Klutiero

Package: libturbojpeg1
Version: 1:1.3.1-6
Severity: wishlist

The short description reads: TurboJPEG runtime library - SIMD optimized
The extended description reads:

The libjpeg-turbo JPEG library is a library for handling JPEG files.

libjpeg-turbo is a JPEG image codec that uses SIMD instructions (MMX, SSE2,
NEON) to accelerate baseline JPEG compression and decompression on x86, x86-64,
and ARM systems.

This package contains the TurboJPEG shared runtime library.

There are a couple of issues here. The first sentence is probably the shortest sentence to contain both
"JPEG" and "library" 3 times. Some of these mentions are "indirect", but this could
easily be brought down to 2: "libjpeg-turbo is a library for handling JPEG files."

More problematic is the fact that libjpeg-turbo is defined, but never referred
to, while TurboJPEG is referred to, but never defined. One would think these
are equivalent, but http://www.libjpeg-turbo.org/About/TurboJPEG explains that
is not the case.

I would like to offer a solution, but there's a reason why I was reading these
descriptions, and the situation appears non-trivial. The page above suggests "the
TurboJPEG shared runtime library" would be wrong, since it defines TurboJPEG as an
API. However, if libjpeg-turbo builds 2 libraries, that's not clear from upstream's
explanation. This looks like clarification with upstream might be warranted.

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

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

Bug#764669: kinit without username, behaviour changes betweek wheezy and jessie

2014-10-09 Thread Mike Gabriel

Package: krb5-user
Version: 1.12.1+dfsg-10
Severity: normal


Dear maintainer,

the behaviour of kinit changed after an upgrade from Debian wheezy to Debian 
jessie (around 2014-10-10).

Previously it was possible to simply say

 $ kinit

on the command line and kinit then would assume my current user as username for 
obtaining a ticket for the default Kerberos realm.

Since my upgrade, I have to always specify the Kerberos username when executing 
kinit:

 $ kinit mike

This alone is only a bit inconvenient. However, this change of behaviour breaks 
the krb5-auth-dialog applet.

Maybe you have an idea why this change occurred and maybe this bug needs to be 
reassigned to krb5-auth-dialog and maybe other tools that depend on kinit.

Greets,
Mike


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

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

Versions of packages krb5-user depends on:
ii  krb5-config2.3
ii  libc6  2.19-11
ii  libcomerr2 1.42.12-1
ii  libgssapi-krb5-2   1.12.1+dfsg-10
ii  libgssrpc4 1.12.1+dfsg-10
ii  libk5crypto3   1.12.1+dfsg-10
ii  libkadm5clnt-mit9  1.12.1+dfsg-10
ii  libkadm5srv-mit9   1.12.1+dfsg-10
ii  libkdb5-7  1.12.1+dfsg-10
ii  libkeyutils1   1.5.9-5
ii  libkrb5-3  1.12.1+dfsg-10
ii  libkrb5support01.12.1+dfsg-10
ii  libss2 1.42.12-1

krb5-user recommends no packages.

krb5-user 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#764668: lgeneral: segfault when loading scenarios

2014-10-09 Thread Roland Hieber

Package: lgeneral
Version: 1.2.3+dfsg-2
Severity: important

Dear Maintainer,

I tried lgeneral for the first time, but every time I try to load a scenario,
the program segfaults. Apparently it does not matter which scenario I load.

GDB output:

$ gdb /usr/games/lgeneral 
Reading symbols from /usr/games/lgeneral...(no debugging symbols 
found)...done.
(gdb) r
Starting program: /usr/games/lgeneral 
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/x86_64-linux-gnu/libthread_db.so.1".
LGeneral 1.2.3
Copyright 2001-2011 Michael Speck
Published under GNU GPL
---
Looking up data in: /usr/share/games/lgeneral
[New Thread 0x7fffeefa3700 (LWP 19966)]
[New Thread 0x7fffea186700 (LWP 19968)]
[Thread 0x7fffea186700 (LWP 19968) exited]
[New Thread 0x7fffea186700 (LWP 19969)]
Mix_LoadWAV_RW with NULL src

Program received signal SIGSEGV, Segmentation fault.
0x55567435 in ?? ()
(gdb) bt
#0  0x55567435 in ?? ()
#1  0x5556a2a5 in ?? ()
#2  0xfe35 in ?? ()
#3  0x555869c4 in ?? ()
#4  0x555870b7 in ?? ()
#5  0x7811 in ?? ()
#6  0x77267b45 in __libc_start_main (main=0x74c0, 
argc=1, argv=0x7fffe008, 
init=, fini=, 
rtld_fini=, stack_end=0x7fffdff8)
at libc-start.c:287
#7  0x7b00 in ?? ()
(gdb) 


It would also be helpful if there were debugging symbols available.


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

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

Versions of packages lgeneral depends on:
ii  lgeneral-data1.0-1
ii  libc62.19-11
ii  libsdl-mixer1.2  1.2.12-11+b1
ii  libsdl1.2debian  1.2.15-10

Versions of packages lgeneral recommends:
pn  lgc-pg  

Versions of packages lgeneral suggests:
ii  game-data-packager  37

-- 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#749016: linux-image-3.14-1-amd64: initrd generated under 3.14-1 v3.14.4-1 does not load sd_mod, boot fails

2014-10-09 Thread Ben Hutchings

Control: tag -1 moreinfo

You all reported this as a regression in 3.14.  Has it been fixed in a
later kernel version?

If not:

1. Martin reported this as a regression when moving from 3.10 to 3.14;
did any of you use a later version (betwen 3.10 and 3.14) successfully?

2. Can someone provide a kernel log for a failed boot, before explicitly
loading sd_mod?

3. Can someone provide the output of this command when sd_mod is not
loaded:

for target in /sys/class/scsi_host/host*/device/target*/*:*; do
if target="$(readlink -f "$target")"; then
echo "[$target]"; cat "$target/uevent"; udevadm info -p "$target"
fi
done > /run/scsi-target-info

(Files created under /run in the initramfs are preserved in the fully
booted system, so you'll be able to copy the file later.)

Ben.

-- 
Ben Hutchings
Editing code like this is akin to sticking plasters on the bleeding stump
of a severed limb. - me, 29 June 1999


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

Bug#764597: u-boot: FTBFS on SH4 due to unsupported compiler option

2014-10-09 Thread Nobuhiro Iwamatsu

Hi,

I checked lastet gcc of Debian.
Current GCC of sh4 does not support  -m4-nopfu option.
Because function for using multilib of SH4 does not enable.
I started debugging about this.

Nobuhiro

2014-10-10 8:13 GMT+09:00 Nobuhiro Iwamatsu :
> Hi,
>
>> On SH4, we can't currently update the kernel to the latest version since
>> u-boot, which is a dependency of the kernel package, fails to build
>> from source.
>>
>> According to the build log [1], the reason for the failure is a compiler
>> option which is not supported in the current build configuration on
>> SH4.
>>
>> Checking the source code, it seems the option in question, "-m4-nofpu",
>> is used on SH4 only. Thus, it would therefore not hurt to just remove
>> this option.
>
> The -m4-nopfu option is required when user builds linux kernel and U-boot.
> Because these do not use the FPU. We need to build with this option to not
> use the instruction to use the FPU.
> Thus, developers of the SH (sh4) uses the GCC nofpu option is enabled.
> I do not check GCC of debian for SH4 the latest, I think it is not a problem 
> of
> U-Boot, that this option is not available in the Debian GCC is problem.
>
> Best regards,
>   Nobuhiro
>
>
> 2014-10-10 2:05 GMT+09:00 John Paul Adrian Glaubitz
> :
>> On 10/09/2014 06:54 PM, Vagrant Cascadian wrote:
>>>
>>> Your patch looks fine to me, largely because it'll only affect
>>> sh4. Would you be able to submit it upstream as well?
>>
>>
>> Yes, I would.
>>
>>> Have you tested that it will build with recent versions? We recently
>>> shifted the packaging to use "make all", but I'm not sure that will
>>> generate the u-boot.img used in the r2dplus target (just u-boot.bin).
>>
>>
>> I haven't tested it yet, I will be able to in the upcoming days when
>> the machine has finished building gcc-4.9. I would also like to hear
>> additional input from Nobuhiro Iwamatsu, the author of that file.
>>
>> Adrian
>>
>> --
>>  .''`.  John Paul Adrian Glaubitz
>> : :' :  Debian Developer - glaub...@debian.org
>> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>
>
>
> --
> Nobuhiro Iwamatsu
>iwamatsu at {nigauri.org / debian.org}
>GPG ID: 40AD1FA6



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


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

Bug#764667: distcc: Trigger cycle causes dpkg to fail processing

2014-10-09 Thread Guillem Jover

Package: distcc
Version: 3.1-6
Severity: serious

Hi!

This package introduces a trigger cycle, that while it might currently
not be visible in most cases it will suddenly make dpkg abort (as per
the spec) once #671711 is fixed in dpkg 1.17.17 to be uploaded later
today.

The problem is that distcc installs interests on /usr/lib/gcc which
is provided by (say) gcc-4.9.

Then distcc depends on libc6, depends on libgcc1, depends on libc6 and
gcc-4.9-base.

And gcc-4.9 depends on gcc-4.9-base and libc6 among others.

When several of those are unpacked on the same run, and the trigger gets
activated dpkg cannot proceed due to the trigger cycle and needs to
bail out, which is not a very nice upgrade path.


The solution to the above is to simply switch the triggers to their
noawait variants. In this case from «interest» to «interest-noawait».

Thanks,
Guillem


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

Bug#764666: ccache: Trigger cycle causes dpkg to fail processing

2014-10-09 Thread Guillem Jover

Package: ccache
Version: 3.1.9-1
Severity: serious

Hi!

This package introduces a trigger cycle, that while it might currently
not be visible in most cases it will suddenly make dpkg abort (as per
the spec) once #671711 is fixed in dpkg 1.17.17 to be uploaded later
today.

The problem is that ccache, installs interests on /usr/lib/gcc which
is provided by (say) gcc-4.9.

Then ccache depends on libc6, depends on libgcc1, depends on libc6 and
gcc-4.9-base.

And gcc-4.9 depends on gcc-4.9-base and libc6 among others.

When several of those are unpacked on the same run, and the trigger gets
activated dpkg cannot proceed due to the trigger cycle and needs to
bail out, which is not a very nice upgrade path.


The solution to the above is to simply switch the triggers to their
noawait variants. In this case from «interest» to «interest-noawait».

Thanks,
Guillem


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

Bug#762211: lightdm crashes on startup, system falls back to console

2014-10-09 Thread Pat Parson

Package: lightdm
Version: 1.10.2-2
Followup-For: Bug #762211

Dear Maintainer,

I am having this problem again, this time liblightdm-gobject is not the 
apparent cause.
After updating lightdm to latest testing version I am having the same results 
but an error appears in the logs.
segfault at * error 4 in libc-2.19.so

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (993, 'testing'), (993, 'stable'), (992, 'proposed-updates'), 
(991, 'stable-updates'), (550, 'testing'), (550, 'stable')
Architecture: i386 (i686)

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

Versions of packages lightdm depends on:
ii  adduser3.113+nmu3
ii  consolekit 0.4.6-5
ii  dbus   1.6.8-1+deb7u4
ii  debconf [debconf-2.0]  1.5.53
ii  libc6  2.19-11
ii  libgcrypt201.6.2-3
ii  libglib2.0-0   2.42.0-2
ii  libpam0g   1.1.8-3.1
ii  libxcb11.10-3
ii  libxdmcp6  1:1.1.1-1
ii  lightdm-gtk-greeter [lightdm-greeter]  1.1.6-2

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+7

Versions of packages lightdm suggests:
pn  accountsservice  
pn  upower   

-- Configuration Files:
/etc/apparmor.d/abstractions/lightdm [Errno 2] No such file or directory: 
u'/etc/apparmor.d/abstractions/lightdm'
/etc/apparmor.d/abstractions/lightdm_chromium-browser [Errno 2] No such file or 
directory: u'/etc/apparmor.d/abstractions/lightdm_chromium-browser'
/etc/apparmor.d/lightdm-guest-session changed:
/usr/lib/i386-linux-gnu/lightdm/lightdm-guest-session-wrapper {
  #include 
  #include 
  #include 
  
  /etc/compizconfig/config rw, # bug in compiz https://launchpad.net/bugs/697678
 
  / r,
  /bin/ rmix,
  /bin/fusermount Px,
  /bin/** rmix,
  /cdrom/ rmix,
  /cdrom/** rmix,
  /dev/ r,
  /dev/** rmw, # audio devices etc.
  owner /dev/shm/** rmw,
  /etc/ r,
  /etc/** rmk,
  /etc/gdm/Xsession ix,
  /lib/ r,
  /lib/** rmixk,
  /lib32/ r,
  /lib32/** rmixk,
  /lib64/ r,
  /lib64/** rmixk,
  owner /media/ r,
  owner /media/** rmwlixk,  # we want access to USB sticks and the like
  /opt/ r,
  /opt/** rmixk,
  @{PROC}/ r,
  @{PROC}/* rm,
  @{PROC}/asound rm,
  @{PROC}/asound/** rm,
  @{PROC}/ati rm,
  @{PROC}/ati/** rm,
  owner @{PROC}/** rm,
  # needed for gnome-keyring-daemon
  @{PROC}/*/status r,
  /sbin/ r,
  /sbin/** rmixk,
  /sys/ r,
  /sys/** rm,
  /tmp/ rw,
  owner /tmp/** rwlkmix,
  /usr/ r,
  /usr/** rmixk,
  /var/ r,
  /var/** rmixk,
  /var/guest-data/** rw, # allow to store files permanently
  /var/tmp/ rw,
  owner /var/tmp/** rwlkm,
  /{,var/}run/ r,
  # necessary for writing to sockets, etc.
  /{,var/}run/** rmkix,
  /{,var/}run/shm/** wl,
  capability ipc_lock,
  # silence warnings for stuff that we really don't want to grant
  deny capability dac_override,
  deny capability dac_read_search,
  #deny /etc/** w, # re-enable once LP#697678 is fixed
  deny /usr/** w,
  deny /var/crash/ w,
}

/etc/lightdm/lightdm.conf changed:
[LightDM]
[SeatDefaults]
xserver-allow-tcp=false
greeter-session=lightdm-greeter
greeter-hide-users=true
greeter-allow-guest=false
greeter-show-remote-login=false
allow-guest=false
greeter-setup-script=/etc/lightdm/greeter_res_setup
[XDMCPServer]
[VNCServer]

/etc/pam.d/lightdm changed:
auth  requisite pam_nologin.so
auth  required pam_env.so envfile=/etc/default/locale
@include common-auth
@include common-account
session  [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
session  requiredpam_limits.so
session  requiredpam_loginuid.so
@include common-session
session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
@include common-password

/etc/pam.d/lightdm-greeter changed:
auth  required pam_env.so envfile=/etc/default/locale
auth  required pam_permit.so
account   required pam_permit.so
password  required pam_deny.so
session   required pam_unix.so


-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm

-- debsums errors found:
sh: 1: /usr/sbin/dpkg-divert: not found


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

Bug#749659: audacity: Systematic check for Printf/Format mismatches

On Thu, Oct 09, 2014 at 01:11:56AM +0200, Benjamin Drung wrote:
> PS: I was reluctant to upload the debdiff because I liked to see the
> patch for 2.0.6 (which has autoreconf fixed). Upstream want to get wx3.0
> support in for 2.0.7 and is actively working on getting it in the svn
> repository. So you could provide the missing bits and we will get
> upstream to test your proposed changes (when I commit them to the
> upstream repository).

I'm assuming here that by "you" you mean Martin (just to make sure we
avoid misunderstandings, as I was the direct recipient of your message).

Cheers,
Olly


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

Bug#749243: lightdm: Could not create user data directory /var/lib/lightdm-data/lightdm

2014-10-09 Thread Pat Parson

Package: lightdm
Version: 1.10.2-2
Followup-For: Bug #749243

Dear Maintainer,

I am receiving the same message in the log files after updating.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (993, 'testing'), (993, 'stable'), (992, 'proposed-updates'), 
(991, 'stable-updates'), (550, 'testing'), (550, 'stable')
Architecture: i386 (i686)

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

Versions of packages lightdm depends on:
ii  adduser3.113+nmu3
ii  consolekit 0.4.6-5
ii  dbus   1.6.8-1+deb7u4
ii  debconf [debconf-2.0]  1.5.53
ii  libc6  2.19-11
ii  libgcrypt201.6.2-3
ii  libglib2.0-0   2.42.0-2
ii  libpam0g   1.1.8-3.1
ii  libxcb11.10-3
ii  libxdmcp6  1:1.1.1-1
ii  lightdm-gtk-greeter [lightdm-greeter]  1.1.6-2

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+7

Versions of packages lightdm suggests:
pn  accountsservice  
pn  upower   

-- Configuration Files:
/etc/apparmor.d/abstractions/lightdm [Errno 2] No such file or directory: 
u'/etc/apparmor.d/abstractions/lightdm'
/etc/apparmor.d/abstractions/lightdm_chromium-browser [Errno 2] No such file or 
directory: u'/etc/apparmor.d/abstractions/lightdm_chromium-browser'
/etc/apparmor.d/lightdm-guest-session [Errno 13] Permission denied: 
u'/etc/apparmor.d/lightdm-guest-session'
/etc/dbus-1/system.d/org.freedesktop.DisplayManager.conf [Errno 13] Permission 
denied: u'/etc/dbus-1/system.d/org.freedesktop.DisplayManager.conf'
/etc/init.d/lightdm [Errno 13] Permission denied: u'/etc/init.d/lightdm'
/etc/lightdm/keys.conf [Errno 13] Permission denied: u'/etc/lightdm/keys.conf'
/etc/lightdm/lightdm.conf [Errno 13] Permission denied: 
u'/etc/lightdm/lightdm.conf'
/etc/lightdm/users.conf [Errno 13] Permission denied: u'/etc/lightdm/users.conf'
/etc/pam.d/lightdm [Errno 13] Permission denied: u'/etc/pam.d/lightdm'
/etc/pam.d/lightdm-autologin [Errno 13] Permission denied: 
u'/etc/pam.d/lightdm-autologin'
/etc/pam.d/lightdm-greeter [Errno 13] Permission denied: 
u'/etc/pam.d/lightdm-greeter'

-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm

-- debsums errors found:
sh: 1: /usr/sbin/dpkg-divert: not found


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

Bug#763405: base-files: inclusion of /mnt in package can result in failures for systems where /mnt is ESTALE

2014-10-09 Thread Guillem Jover

Hi!

On Thu, 2014-10-09 at 20:55:33 +0200, Santiago Vila wrote:
> On Mon, 29 Sep 2014, Stephen Dowdy wrote:
> > Package: base-files
> > Version: 7.1wheezy6
> > Severity: normal

> > Since sysadmins tend to (and are often told to) use /mnt for
> > temporary mounts, and sometimes forget those mounts and they go
> > stale (nfs), a package (in this case 'base-files') that includes
> > /mnt in the files section will result in a complete failure to
> > install.

[…]
> > Preparing to replace base-files 7.1wheezy2 (using 
> > .../base-files_7.1wheezy6_amd64.deb) ...
> > --> Unpacking replacement base-files ...
> > dpkg: error processing 
> > /var/cache/apt/archives/base-files_7.1wheezy6_amd64.deb (--unpack):
> > -->  unable to stat `./mnt' (which I was about to install): Stale NFS file 
> > handle
> > Errors were encountered while processing:
> >  /var/cache/apt/archives/base-files_7.1wheezy6_amd64.deb
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > A package failed to install.  Trying to recover:
> >  
> > SERVER:~# ls /mnt
> > ls: cannot access /mnt: Stale NFS file handle
> > (d'oh sysadmin mounted other server months ago, which is now ESTALE,
> > but should not result in a fatal install failure in base-files)
> > 
> > SERVER:X# dpkg --fsys-tarfile - 
> > /var/cache/apt/archives/base-files_7.1wheezy6_amd64.deb | tar tvf - | grep 
> > /mnt
> > --> drwxr-xr-x root/root 0 2014-06-11 21:07 ./mnt/
> > 
> 
> I see the problem, and I see how dropping /mnt from base-files.deb
> (and creating it in the postinst) would make the problem to disappear.

I'm not sure it would, if this fails for dpkg, I'm expecting this
would fail for mkdir or stat or any other programs run from the
maintainer script as well.

> But I'm not sure that this is a bug in base-files.

I don't think it is, neither in dpkg.

> Could this be fixed in dpkg, or maybe dpkg has good reasons
> to fail in cases like this one?

dpkg needs to know what type of object a pathname is, to be able to
decide if it needs to replace it or update its metadata, etc.

The ESTALE pathname might be just up in the hierarchy, and dpkg might
be trying to access somehting lower, say /usr (ESTALE), and dpkg wants
to update «/usr/share/doc/pkg/copyright». dpkg cannot know which paths
might be mouned on NFS, because any could be.

In the end, this is a just a system administration issue. In the
same way that a setup might have RO filesystems, that need to be
remounted RW before upgrades, this is something that would need to
be checked by the sysadmin, or extending the upgrade script elided
above.

I'm afraid I don't think there's much else to do than close the report.

Thanks,
Guillem

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

Bug#763278: gcc 4.9 wheezy-pu?

2014-10-09 Thread Michael Gilbert

Hi,

I would like to ask for your opinion about uploading a newer gcc
version to wheezy?

This is to be able to continue building chromium security updates,
which has been discussed with the release team [0].  They've requested
that I discuss it with gcc maintainers, which is the reason for this
message.

I would be responsible for building and maintaining it.

Anyway, any thoughts?

Note that the window for the next stable update is closing in about a
week, so there isn't a lot of time.

Best wishes,
Mike

[0] http://bugs.debian.org/763278


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

Bug#764665: numactl: Please support hppa

2014-10-09 Thread John David Anglin

Package: numactl
Version: 2.0.10~rc2-3
Severity: normal

numactl builds successfully on hppa when enabled in control.

See log:
http://buildd.debian-ports.org/status/fetch.php?pkg=numactl&ver=2.0.10%7Erc2-3%2Bb2&arch=hppa&stamp=1412907629

-- System Information:
Debian Release: jessie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 3.16.3+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_CA.utf8)
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#764664: asciidoctor: new upstream version

2014-10-09 Thread brian m. carlson

Package: asciidoctor
Version: 0.1.4-3
Severity: wishlist

Asciidoctor 1.5.1 is now available.  It contains numerous improvements,
including fixes necessary to build the Git documentation correctly.

Please consider updating the package.

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

Kernel: Linux 3.17-rc5-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 asciidoctor depends on:
ii  ruby  1:2.1.0.4
ii  ruby1.9.1 [ruby-interpreter]  1.9.3.484-2
ii  ruby2.0 [ruby-interpreter]2.0.0.484+really457-3
ii  ruby2.1 [ruby-interpreter]2.1.3-1

asciidoctor recommends no packages.

Versions of packages asciidoctor suggests:
ii  asciidoc 8.6.9-3
ii  asciidoctor-doc  0.1.4-3

-- no debconf information

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#749729: [sadt] please skip non-executable tests

2014-10-09 Thread James McCoy

Hi Jakub,

On Sat, Jun 07, 2014 at 08:54:10PM +0200, Jakub Wilk wrote:
> * Nicolas Boulenguez , 2014-05-30, 23:05:
> >I suggest that sadt skips non executable tests with a warning and
> >documents this behaviour (as it does with missing dependencies), or
> >displays a warning when modifying the permissions. It took me some time to
> >find who was interfering with my version control system.
> 
> Thanks, that's a pretty strong argument that chmod'ing tests is not a good
> idea, at least not by default.

Do you intend to make some changes for this soon?

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


signature.asc
Description: Digital signature

Bug#757847: mate-notification-daemon: Partially fixed

2014-10-09 Thread Jean-Philippe MENGUAL

Package: mate-notification-daemon
Followup-For: Bug #757847

Dear Maintainer,

Hi,

Only the second part of the bug remains.  Indeed, actually, notifications work
patching orca. But the browsing in panel is still a problem.

Regards,

*** 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: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages mate-notification-daemon depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-11
ii  libcairo21.12.16-5
ii  libcanberra-gtk0 0.30-2.1
ii  libcanberra0 0.30-2.1
ii  libdbus-1-3  1.8.8-1+b1
ii  libdbus-glib-1-2 0.102-1
ii  libfontconfig1   2.11.0-6.1
ii  libfreetype6 2.5.2-2
ii  libgdk-pixbuf2.0-0   2.30.8-1+b1
ii  libglib2.0-0 2.42.0-2
ii  libgtk2.0-0  2.24.24-1
ii  libnotify4   0.7.6-2
ii  libpango-1.0-0   1.36.8-2
ii  libpangocairo-1.0-0  1.36.8-2
ii  libpangoft2-1.0-01.36.8-2
ii  libwnck222.30.7-2
ii  libx11-6 2:1.6.2-3

mate-notification-daemon recommends no packages.

mate-notification-daemon 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#757852: gnome-orca: Restriction of the bug

2014-10-09 Thread Jean-Philippe MENGUAL

Package: gnome-orca
Followup-For: Bug #757852

Dear Maintainer,

Hi,

The only part of the bug which remains is with alt-f1. Otherwise, the bug nearly
could be closed.

Regards,

*** 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: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.42.0-2
ii  gir1.2-gtk-3.0 3.12.2-3+b1
ii  gir1.2-pango-1.0   1.36.8-2
ii  gir1.2-wnck-3.03.4.9-2
ii  gsettings-desktop-schemas  3.14.0-1
ii  python33.4.1-1
ii  python3-brlapi 5.0-3
ii  python3-cairo  1.10.0+dfsg-4+b1
ii  python3-gi 3.14.0-1
ii  python3-louis  2.5.3-3
ii  python3-pyatspi2.12.0+dfsg-3
ii  python3-speechd0.8-6
pn  python3:any
ii  speech-dispatcher  0.8-6

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.24-1
ii  xbrlapi 5.0-3

gnome-orca 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#761935: shine: ftbfs on mips64el

2014-10-09 Thread Aníbal Monsalve Salazar

Control: severity -1 important 

On Wed, 2014-09-17 10:44:47 +0800, YunQiang Su wrote:
> Package: shine
> Version: 3.1.0-2
> 
> 
> In debian/rules, there are lines:
> 
> ifneq (,$(findstrings mips,$(DEB_HOST_ARCH)))
> CFLAGS+= -mips32r2
> export CFLAGS
> endif
> 
> It will make all mips* ports use mips32r2.
> 
> change it to
> 
> ifneq (,$(filter mips mipsel,$(DEB_HOST_ARCH)))
> 
> can fix this problem.
> 
> -- 
> YunQiang Su

Hello Romain,

YunQiang forgot to set the severity of this bug report.

Port bugs are at least important. ;-)

Cheers,

Aníbal


signature.asc
Description: Digital signature

Bug#763219: zeitgeist needs valadoc with vala 0.26 support.

2014-10-09 Thread Sebastian Reichel

Hi Andreas,

On Thu, Oct 09, 2014 at 09:55:14PM +0200, Andreas Henriksson wrote:
> For the record I just verified that this build failure goes away
> if using a (locally built) valadoc with support for vala 0.26.
> 
> (The problem here is that zeitgeist uses (the default) vala 0.26 to
> build itself and then tries to use valadoc on top of that, which still
> only supports vala 0.24. Changing this on the valadoc side is trivial
> and preferred. Just s/0.24/0.26/ in debian/control.)

I just uploaded valadoc 0.23.2~git20140902-2, which should include
support for vala 0.26.

-- Sebastian


signature.asc
Description: Digital signature

Bug#762211: Info received (lightdm crashes on startup, system falls back to console)

2014-10-09 Thread parspes

 In addition, immediately after the upgrade of the
liblightdm-gobject-1-0 library lightdm-gtk-greeter request access to
/dev/tty, something it did not need previously. The older version
still does not need this access to function.


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

Bug#761805: gammaray fix mips64el support

On Tue, 16 Sep 2014 14:54:30 +0800 YunQiang Su  wrote:
> Package: gammaray
> Version: 2.1.0-3
>
>
> In debian/patches/debian-archs-fix-build.patch, there is a line:
>
>elseif(CMAKE_SYSTEM_PROCESSOR STREQUAL "mips64" AND
> CMAKE_SIZEOF_VOID_P EQUAL 4)
>
> It works for mipsel/mips ports and mipsn32(el) ports, while not for 
> mips64(el),
> as the e_machine is the same for o32, n32, and n64.
>
> So for all mips ports, use the same may be an option, aka
> elseif(CMAKE_SYSTEM_PROCESSOR STREQUAL "mips64")

I nmued this package to delay 5 with the attached patch.

>
>
> --
> YunQiang Su
>
>


gammaray.debdiff
Description: Binary data

Bug#762211: lightdm crashes on startup, system falls back to console

2014-10-09 Thread Pat Parson

Package: liblightdm-gobject-1-0
Version: 1.10.2-2
Followup-For: Bug #762211

Dear Maintainer,

Updating liblightdm-gobject-1-0 to testing version produces this problem on my 
machine. 
Downgrading the library to stable corrects the problem.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (993, 'testing'), (993, 'stable'), (992, 'proposed-updates'), 
(991, 'stable-updates'), (550, 'testing'), (550, 'stable')
Architecture: i386 (i686)

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

Versions of packages liblightdm-gobject-1-0 depends on:
ii  libc6  2.19-11
ii  libglib2.0-0   2.42.0-2
ii  libx11-6   2:1.6.2-3
ii  libxklavier16  5.2.1-1
ii  multiarch-support  2.13-38+deb7u4

liblightdm-gobject-1-0 recommends no packages.

liblightdm-gobject-1-0 suggests no packages.

-- no debconf information

-- debsums errors found:
sh: 1: /usr/sbin/dpkg-divert: not found


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

Bug#764663: mikutter requires ruby-gettext >=3

2014-10-09 Thread NOKUBI Takatsugu

Package: mikutter
Severity: wishlist

mikutter package depends on ruby-gettext.
I backported it into wheezy, but wheezy has old ruby-gettext 2.2.1,
and 3.0.2 in wheezy backports.
Could you add depends field with ruby-gettext (>= 3) versioning?

-- System Information:
Debian Release: 7.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (x86_64)

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


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

Bug#763755: blender: SIGILL on startup

2014-10-09 Thread Johann Klammer

On 10/09/2014 03:01 PM, Matteo F. Vescovi wrote:
> Hi again!
> 
> On 2014-10-09 at 14:39 (CEST), Matteo F. Vescovi wrote:
>> Re-applying it with next upcoming revision. Sorry for the mess.
> 
> FTR, test build on i386 with your patch applied on top of
> 2.72 now fails [1].
> 
> I hope to find a solution soon.
> 
> Cheers.
> 
> 
> [1] 
> http://debomatic-i386.debian.net/distribution#unstable/blender/2.72+dfsg1-2/buildlog
> 
perhaps they need a

`include /usr/share/dpkg/architecture.mk`

in debian/rules now?

There was something about that in `man dpkg-architecture`.

The .71 in testing seems to build OK with it...
The menus look fishy, but that's probably this ancient NVIDIA VANTA
here(no shader progs)..


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

Bug#757847: mate-notification-daemon: Browsing on the panel is hard with keyboard

2014-10-09 Thread Jean-Philippe MENGUAL

Package: mate-notification-daemon
Version: 1.8.0-2
Followup-For: Bug #757847

Dear Maintainer,

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

   * What led up to the situation?

I installed mate-panel, mate-notification-daemon and orca 3.14.

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

When dropbox or pidgin changes status, no notification. But 9e can see the
status going to the panel via meta-ctrl-tab.

   * What was the outcome of this action?

First, alt-ctrl-tab doesn't move the focus on the panel sometimes. The behavior
is random. Sometimes it stays on the bottom panel, sometimes on caja, sometimes
it has success. alt-maj-tab has always success to reach the top panel.
Once here, maj-tab, after f10, can, randomly, render the applets. But it 
involves
a random twick, with f10 (twcce), arrow keys, maj-tab, etc. It's really not
convinient.

   * What outcome did you expect instead?

After alt-ctrl-tab, tab or arrow keys should move the focus on this top panel
and I should be able to hear the applet regularly and without all keyboard
twicks.

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

Thanks


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

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

Versions of packages mate-notification-daemon depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-11
ii  libcairo21.12.16-5
ii  libcanberra-gtk0 0.30-2.1
ii  libcanberra0 0.30-2.1
ii  libdbus-1-3  1.8.8-1+b1
ii  libdbus-glib-1-2 0.102-1
ii  libfontconfig1   2.11.0-6.1
ii  libfreetype6 2.5.2-2
ii  libgdk-pixbuf2.0-0   2.30.8-1+b1
ii  libglib2.0-0 2.42.0-2
ii  libgtk2.0-0  2.24.24-1
ii  libnotify4   0.7.6-2
ii  libpango-1.0-0   1.36.8-2
ii  libpangocairo-1.0-0  1.36.8-2
ii  libpangoft2-1.0-01.36.8-2
ii  libwnck222.30.7-2
ii  libx11-6 2:1.6.2-3

mate-notification-daemon recommends no packages.

mate-notification-daemon 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#681501: I found the thread taffit is referring to.

2014-10-09 Thread Brian Gupta

I found the thread taffit is referring to here (18 months ago):

http://lists.debconf.org/lurker/message/20130330.130910.2a600f87.en.html

He was questioning the fees collected by Paypal. (Which are just under
3%). In the thread people did express a dislike for Paypal, but
acknowledged that their fees are competitive with other fees we pay
for online payment processing. It was also expressed that people
didn't like that Paypal was the primary option, with an allowance only
given for people who couldn't use Paypal. IE: To take advantage of the
match one needed to use Paypal. Please note that an option option was
added shortly thereafter for European Interbank transfers but, if
memory serves, nobody take advantage of it.

The use of Paypal in that particular case was for a matching drive for
DC13, with a targeted dynamic progress bar, where if we didn't use
Paypal, it would be practically improbable to do using another service
in the timeframe with human resources we had available. It was very
easy for Debian.ch, to implement and maintain, and no one volunteered
to help with the harder work of integrating other options.

In the current case, we are NOT talking about ONLY allowing Paypal, we
are talking about adding an easy to use option, for those people who
do use Paypal. For Paypal users, it will greatly streamline the
donations process and increase follow through.

I will also add that currently both Debian.ch and Debian.fr accept
Paypal, and SPI passed a resolution to accept Paypal. [1] This is
still to be implemented, but we should see some progress within a
month or so. ffis also accepts paypal as well. [2] So basically all of
Debian's Trusted Orgs either accept or plan to accept Paypal payments.

Using SPI's Paypal account, in the future, will have one additional
advantage beyond US tax deductibility. Because SPI is a 501c3
non-profit, paypal provides a discounted rate of 2.2%. This is really
a great rate and the only way to get significantly lower, is to use
european wire transfers, which isn't really an option in the US, or to
use paper checks which are quite the opposite of easy.

I and many of the other people who are working on fundraising
understand that some people don't like Paypal. Some of us also don't
like Paypal, but view it as a useful and necessary tool for our jobs
of raising money for Debian. At the end of the day ALL these banking
services are proprietary services that we need to integrate with to
accept donations. Paypal, like all the services we use, does not
require us to use proprietary libraries or protocols to interface with
them.

I'll close on one note, for the donations page we are working on we
want ALL options listed. We also want to make to make the process as
painless as possible for our benefactors, so would prioritize those
options that are the simplest. If people don't like Paypal they don't
have to use it, as it won't even be the first option listed.

-Brian

[1] - http://www.spi-inc.org/corporate/resolutions/2013/2013-12-12.mcs.1/
[2] - http://www.ffis.de/News/Spenden-jetzt-auch-mit-PayPal-m-glich-5.html


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

Bug#764425: [INTL:es] Spanish translation of the debconf template apt-listbugs

2014-10-09 Thread jathanblackred

Hi Francesco. I send you some final modifications adding a final point 
that was missing in the next line after "%s":


#: ../lib/apt-listbugs/logic.rb:551
msgid ""
"All selected packages are already pinned or on hold. Ignoring %s 
command."

msgstr ""
"Todos los paquetes seleccionados ya se han anclado o marcado para 
mantener. "

"Ignorando la orden %s."

and a better translation for:

#: ../lib/apt-listbugs/logic.rb:73
msgid "See the manual page for the long options.\n"
msgstr "Consulte la página del manual para ver las opciones 
extendidas.\n"


I hope that these slight changes can still be implemented. Regards.
# apt-listbugs po translation to Spanish
# Copyright (C) 2014 Software in the Public Interest
# This file is distributed under the same license as the apt-listbugs package.
#
# Changes:
#   - Initial translation
#   Omar Campagne , 2012.
#
#   - Updates
#   MatÃas Bellone , 2014.
#   Jonathan Bustillos , 2014.
#
# Traductores, si no conocen el formato PO, merece la pena leer la
# documentaciÃ³n de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
#   info -n '(gettext)PO Files'
#   info -n '(gettext)Header Entry'
#
# Equipo de traducciÃ³n al espaÃ±ol, por favor lean antes de traducir
# los siguientes documentos:
#
#   - El proyecto de traducciÃ³n de Debian al espaÃ±ol
# http://www.debian.org/intl/spanish/
# especialmente las notas y normas de traducciÃ³n en
# http://www.debian.org/intl/spanish/notas
#
#   - La guÃa de traducciÃ³n de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
msgid ""
msgstr ""
"Project-Id-Version: apt-listbugs 0.1.8\n"
"Report-Msgid-Bugs-To: invernom...@paranoici.org\n"
"POT-Creation-Date: 2014-08-11 16:22+0200\n"
"PO-Revision-Date: 2014-10-06 20:54+\n"
"Last-Translator: Jonathan Bustillos \n"
"Language-Team: Debian Spanish \n"
"Language: es\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. TRANSLATORS: "E: " is a label for error messages; you may translate it with a suitable abbreviation of the word "error"
#: ../apt-listbugs:330 ../apt-listbugs:368 ../apt-listbugs:373
#: ../apt-listbugs:379 ../apt-listbugs:393 ../apt-listbugs:423
#: ../apt-listbugs:454 ../apt-listbugs:503 ../apt-listbugs:516
#: ../aptcleanup:54 ../aptcleanup:57 ../lib/apt-listbugs/logic.rb:268
#: ../lib/apt-listbugs/logic.rb:278 ../lib/apt-listbugs/logic.rb:900
#: ../lib/apt-listbugs/logic.rb:911 ../lib/apt-listbugs/logic.rb:923
#: ../migratepins:54 ../migratepins:57
msgid "E: "
msgstr "E: "

#: ../apt-listbugs:331
msgid ""
"This may be caused by a package lacking support for the ruby interpreter in "
"use. Try to fix the situation with the following commands:"
msgstr ""
"Es posible que esto suceda porque un paquete no es compatible con el "
"intÃ©rprete ruby utilizado. Intente corregir esta situaciÃ³n ejecutando lo "
"siguiente:"

#: ../apt-listbugs:368
msgid "APT_HOOK_INFO_FD is undefined.\n"
msgstr "No estÃ¡ definido APT_HOOK_INFO_FD.\n"

#: ../apt-listbugs:373
msgid "APT_HOOK_INFO_FD is not correctly defined.\n"
msgstr "No estÃ¡ definido correctamente APT_HOOK_INFO_FD.\n"

#: ../apt-listbugs:379
msgid "Cannot read from file descriptor %d"
msgstr "No se puede leer desde el descriptor de archivo %d"

#: ../apt-listbugs:393
msgid "APT Pre-Install-Pkgs is not giving me expected 'VERSION 3' string.\n"
msgstr "APT Pre-Install-Pkgs no devuelve la cadena esperada Â«VERSION 3Â».\n"

#: ../apt-listbugs:423
msgid "APT Pre-Install-Pkgs is giving me fewer fields than expected.\n"
msgstr "APT Pre-Install-Pkgs devuelve menos campos de los esperados.\n"

#: ../apt-listbugs:454
msgid ""
"APT Pre-Install-Pkgs is giving me an invalid direction of version change.\n"
msgstr ""
"APT Pre-Install-Pkgs devuelve una direcciÃ³n no vÃ¡lida de cambio de versiÃ³n.\n"

#: ../apt-listbugs:533
msgid "** Exiting with an error in order to stop the installation. **"
msgstr "** Saliendo con error para detener la instalaciÃ³n. **"

#: ../aptcleanup:54 ../lib/apt-listbugs/logic.rb:338 ../migratepins:54
msgid "Cannot read from %s"
msgstr "No se puede leer desde %s"

#: ../aptcleanup:125
msgid "Fixed packages : "
msgstr "Paquetes corregidos : "

#: ../lib/apt-listbugs/logic.rb:47
msgid "Usage: "
msgstr "Uso: "

#: ../lib/apt-listbugs/logic.rb:48
msgid " [options]  [arguments]"
msgstr " [opciones]  [argumentos]"

#: ../lib/apt-listbugs/logic.rb:50
msgid "Options:\n"
msgstr "Opciones:\n"

#. TRANSLATORS: the colons (:) in the following strings are vertically aligned, please keep their alignment consistent
#: ../lib/apt-listbugs/logic.rb:52
msgid " -h   : Display this help and exit.\n"
msgstr " -h: Mostrar esta ayuda y salir.\n"

#: ../lib/apt-listbugs/logic.rb:53
msgid " -v   : Show version number and exit.\n"
msgstr " -v

Bug#761418: freebsd-net-tools: netstat issues on 9.0 kernel

2014-10-09 Thread Steven Chamberlain

retitle 761418 freebsd-net-tools: netstat issues on 9.0 kernel
user debian-...@lists.debian.org
usertags kfreebsd
thanks

If netstat cannot read from /dev/mem, it is supposed to work anyway by
falling back to using sysctls.

The problem affecting the virtuoso-opensource testsuite is that when
recent versions of netstat run on a 9.0 kernel (such as on the buildds),
the word 'LISTEN' is not being shown in the output (the 'state' column).
 However, the listening sockets are still shown.

This is probably related to #740509, syscall ABI changes.

It may actually not have this problem running on a 10.1 kernel.  But the
buildds won't have that until after release.

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#681501: Debian France on Debian's new donations page?

2014-10-09 Thread Paul Wise

On Fri, Oct 10, 2014 at 2:45 AM, David Prévot wrote:

> let me at least cite a few ones.

Thanks, also I've read through the thread.

FTR, I share the concerns about PayPal but I acknowledge they are easy
for many people. As long as there other options for donating and we
don't store money in PayPal accounts I would not object to using them
as a donations processor via our TOs.

> thanks in advance if someone is able to provide an URL).

A few different web interfaces to the thread:

http://lists.debconf.org/lurker/message/20130330.130910.2a600f87.en.html
http://thread.gmane.org/gmane.linux.debian.conference.team/9545/focus=9546
https://www.mail-archive.com/debconf-team@lists.debconf.org/msg09491.html

> Anyway, if we were to endorse such service, I believe
> debian-project@l.d.o would be the right place to have this conversation,
> not a two-year long wishlist bug report log against www.debian.org.

I agree.

Brian, could you start the discussion on debian-project about PayPal?
To inform the discussion properly, please include factual information
about these topics and anything else you can think of:

How PayPal fees compare to other methods.

How our TOs treat money from PayPal; do they move it
manually/automatically to other accounts or keep it in PayPal?

How quickly we can be notified if TOs' PayPal accounts are frozen/locked/closed?

> On Thu, Oct 9, 2014 at 11:37 PM, Paul Wise wrote:
>
>> BTW, the page already mentions it is possible to donate to SPI via
>> PayPal.
>
> Maybe should that be fixed in the mean time.

I replaced PayPal with "other methods" on the page, hope that is OK.
Apologies to our translators for the noise.

-- 
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#764662: initscripts: bootclean: please except .sujournal

2014-10-09 Thread Steven Chamberlain

Package: sysvinit
Version: 2.88dsf-53.4
Severity: important
Tags: patch

Hi,

On GNU/kFreeBSD a UFS filesystem may contain a special .sujournal file
(soft-updates journal) with uid=0.  If /tmp is the mountpoint for such
a filesystem, bootclean will try and fail to delete this file on boot.

Please add .sujournal to the EXCEPT list in bootclean.sh to avoid this
error (patch attached).

Thank you.

-- 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
--- debian/src/initscripts/lib/init/bootclean.sh.orig	2014-01-27 21:21:13.0 +
+++ debian/src/initscripts/lib/init/bootclean.sh	2014-10-10 00:29:00.240698324 +0100
@@ -117,6 +117,7 @@
 		! ( -path ./quota.group -uid 0 )
 		! ( -path ./aquota.group -uid 0 )
 		! ( -path ./.journal -uid 0 )
+		! ( -path ./.sujournal -uid 0 )
 		! ( -path ./.clean -uid 0 )
 		! ( -path './...security*' -uid 0 )'

Bug#764608: patch for X11 forwarding when pam_namespace.so is used on SSH client

2014-10-09 Thread Colin Watson

Control: found -1 1:6.7p1-1
Control: forwarded -1 https://bugzilla.mindrot.org/show_bug.cgi?id=1789

On Thu, Oct 09, 2014 at 04:56:48PM +0200, Mike Gabriel wrote:
> I just checked debian/changelog and the 6.7 release announcement. The
> following issue hasn't been addressed yet in Debian, nor by upstream.
> 
> If on the SSH client side a session is running with pam_namespace.so
> in use, it is impossible to do X11 port forwarding. The ssh client
> tries to connect to /tmp/.X11-unix/X which is out of
> reach with pam_namespace sessions.
> 
> Instead, ssh client should connect the X11 forwarding end point to the
> X11 socket in kernel namespace (@/tmp/.X11-unix/X).
> 
> A patch is available in the Fedora OpenSSH package [1].
[...]
> [1] 
> http://pkgs.fedoraproject.org/cgit/openssh.git/tree/openssh-5.5p1-x11.patch

It appears (after a bit of trawling through git history plus some
guesswork; I wish Fedora had better conventions for patch headers the
way that Debian does ...) that this is
https://bugzilla.redhat.com/show_bug.cgi?id=598671, and the upstream bug
is https://bugzilla.mindrot.org/show_bug.cgi?id=1789.  By the way the
patch in Fedora's git repository does not match the latest one attached
to the upstream bug.

I'm a bit wary given upstream's fairly strenuous objections.  In cases
where I feel I know something better than upstream I do sometimes decide
to carry a patch anyway of course, but in this case I'm far from a
relevant expert.  Do you think that perhaps somebody could re-engage
with that upstream bug and see if they can work through the objections?

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#764661: reportbug: python-vte is required for the GUI, but is not included in the Debian installation

2014-10-09 Thread Nathan2055

Package: reportbug
Version: 6.4.4+deb7u1
Severity: normal

reportbug is included by default in Debian, however it requires python-vte to
run it's GUI, which is not included by default, causing it to start in text
mode unless it's installed.



-- Package-specific info:
** Environment settings:
INTERFACE="gtk2"

** /home/nathan2055/.reportbugrc:
reportbug_version "6.4.4"
mode standard
ui text
realname "Nathan2055"
email "spychicken2055+deb...@gmail.com"
no-cc
header "X-Debbugs-CC: spychicken2055+deb...@gmail.com"
smtphost reportbug.debian.org

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

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

Versions of packages reportbug depends on:
ii  apt   0.9.7.9+deb7u6
ii  python2.7.3-4+deb7u1
ii  python-reportbug  6.4.4+deb7u1

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
pn  emacs22-bin-common | emacs23-bin-common
ii  exim4  4.80-7
ii  exim4-daemon-light [mail-transport-agent]  4.80-7
ii  file   5.11-2+deb7u5
ii  gnupg  1.4.12-7+deb7u6
ii  python-gtk22.24.0-3+b1
pn  python-gtkspell
pn  python-urwid   
ii  python-vte 1:0.28.2-5
ii  xdg-utils  1.1.0~rc1+git20111210-6

Versions of packages python-reportbug depends on:
ii  apt   0.9.7.9+deb7u6
ii  python2.7.3-4+deb7u1
ii  python-debian 0.1.21
ii  python-debianbts  1.11
ii  python-support1.0.15

python-reportbug 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#764553: base-files: Does neither state which version nor which variant of the Artistic License is in /usr/share/common-licenses/Artistic

2014-10-09 Thread Santiago Vila

> Santiago Vila wrote:
> > > Another thing which I think would solve this issue easily, but which
> > > may have some side effects I'm not yet aware of, would be to rename
> > > the file to "Artistic-1.0-Perl" (or whatever) and make "Artistic" a
> > > symlink to it, analogous how it's done for the different GPL versions.
> > 
> > That would be a possibility to which I'm not opposed in principle,
> 
> Happy to hear.
> 
> Do we need a minor/wishlist bug to track this?

Against debian-policy. See the base-files FAQ.


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

Bug#764660: util-linux: flock -w 0 no longer allowed

2014-10-09 Thread Jeff King

Package: util-linux
Version: 2.25.1-3
Severity: normal
Tags: patch

Using a timeout of "0" with flock used to be allowed as a synonym for
"-n", but is now disallowed:

  $ flock -w 0 foo
  flock: timeout cannot be zero

Switching back to 2.20.1-5.11 from testing makes it work again. The bug
is old but just recently hit unstable. Upstream has a fix already:

  
https://github.com/karelzak/util-linux/commit/c4604c38b503c8c46e50fc2048ebbcbcfcad3802

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

Kernel: Linux 3.16-2-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

Versions of packages util-linux depends on:
ii  initscripts2.88dsf-53.4
ii  libblkid1  2.25.1-3
ii  libc6  2.19-11
ii  libmount1  2.25.1-3
ii  libncurses55.9+20140913-1
ii  libpam0g   1.1.8-3.1
ii  libselinux12.3-2
ii  libslang2  2.3.0-1
ii  libsmartcols1  2.25.1-3
ii  libtinfo5  5.9+20140913-1
ii  libuuid1   2.25.1-3
ii  lsb-base   4.1+Debian13
ii  tzdata 2014h-2
ii  zlib1g 1:1.2.8.dfsg-2

util-linux recommends no packages.

Versions of packages util-linux suggests:
pn  dosfstools   
pn  kbd | console-tools  
pn  util-linux-locales   

-- debconf information:
  util-linux/noauto-with-nonzero-passnum:


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

Bug#684399: emacs : dbus problem at start

tags unreproducible moreinfo
thanks

Erwan David  writes:

> Package: emacs24
> Version: 24.1+1-4
> Severity: normal
>
> When starting emacs24 (from a ssh connection and remote display), I
> get :

[...]

> (emacs:19860): GConf-WARNING **: Client failed to connect to the D-BUS
> daemon:
> /usr/bin/dbus-launch terminated abnormally without any error message

If you get a chance, could you see if this still happens with a more
recent version of Debian.  I just tested the current unstable emacs24,
via ssh -X, and didn't have any trouble.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4


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

Bug#758121: [Pkg-crosswire-devel] Bug#758121: bibletime: Bibletime is unusable in testing and unstable

2014-10-09 Thread Dimitri John Ledkov

On 9 October 2014 18:21, David Sanders  wrote:
> On Thursday, October 09, 2014 10:27:48 AM David Sanders wrote:
>> On Thursday, October 09, 2014 10:55:59 AM Dimitri John Ledkov wrote:
>> > On 8 October 2014 15:54,   wrote:
>> > > retitle 758121 bibletime: New upstream release fixes display problem in
>> > > jessie severity 758121 grave
>> > > thanks
>> > >
>> > > On Monday, October 06, 2014 10:26:56 PM you wrote:
>> > >> Bibletime is unusable in jessie and sid.  When you open any Bible or
>> > >> commentary all you see is jibberish.  This needs to be fixed prior to
>> > >> the release of jessie.
>> > >
>> > > I just built the new upstream release (2.10.1) from source.  It does not
>> > > have this problem.  Please update the bibletime package in jessie to the
>> > > latest upstream release available on sourceforge.
>> >
>> > Debdiff would be appreciated. I don't use, nor typically updated
>> > bibletime.
>>
>> Dimitri,
>>
>> I don't have a deb of version 2.10.1 to create a debdiff with.  I think the
>> package can be built from source without any patches and with minimum
>> trouble. I may try to create a deb but I'm not a debian developer so I may
>> be unsuccessful.  Any help would be appreciated.
>>
>> David
>
> Alright I built a deb package for version 2.10.1-1.  I've attached your 
> debdiff
> and the debian directory I used.  Let me know if you need anything else.

Heya. When I said debdiff, i meant debdiff between the two .dsc files,
which is essentially source changes to debian/* directory to build new
release.
The attached tarball is sufficient to derive the diff and for me to
review/apply it. I'll poke it tomorrow and comment/upload and or fix
up as needed. Unless roberto beats me to it.

-- 
Regards,

Dimitri.


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

Bug#764570: taskcoach: fail to start: wx._core.PyAssertionError

On Thu, Oct 09, 2014 at 08:04:48AM +0200, Peter Gervai wrote:
> wx._core.PyAssertionError: C++ assertion "m_window" failed at 
> ../src/gtk/dcclient.cpp(2043) in DoGetSize(): GetSize() doesn't work without 
> window

The quick fix (which might be useful, given the approaching freeze) is
to tell wxPython to quietly handle such cases, as happens by default in
2.8 - for details see:

http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README#n30

Cheers,
Olly


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

Bug#764597: u-boot: FTBFS on SH4 due to unsupported compiler option

2014-10-09 Thread Nobuhiro Iwamatsu

Hi,

> On SH4, we can't currently update the kernel to the latest version since
> u-boot, which is a dependency of the kernel package, fails to build
> from source.
>
> According to the build log [1], the reason for the failure is a compiler
> option which is not supported in the current build configuration on
> SH4.
>
> Checking the source code, it seems the option in question, "-m4-nofpu",
> is used on SH4 only. Thus, it would therefore not hurt to just remove
> this option.

The -m4-nopfu option is required when user builds linux kernel and U-boot.
Because these do not use the FPU. We need to build with this option to not
use the instruction to use the FPU.
Thus, developers of the SH (sh4) uses the GCC nofpu option is enabled.
I do not check GCC of debian for SH4 the latest, I think it is not a problem of
U-Boot, that this option is not available in the Debian GCC is problem.

Best regards,
  Nobuhiro


2014-10-10 2:05 GMT+09:00 John Paul Adrian Glaubitz
:
> On 10/09/2014 06:54 PM, Vagrant Cascadian wrote:
>>
>> Your patch looks fine to me, largely because it'll only affect
>> sh4. Would you be able to submit it upstream as well?
>
>
> Yes, I would.
>
>> Have you tested that it will build with recent versions? We recently
>> shifted the packaging to use "make all", but I'm not sure that will
>> generate the u-boot.img used in the r2dplus target (just u-boot.bin).
>
>
> I haven't tested it yet, I will be able to in the upcoming days when
> the machine has finished building gcc-4.9. I would also like to hear
> additional input from Nobuhiro Iwamatsu, the author of that file.
>
> Adrian
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



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


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

Bug#764606: dgit and upstream git repos [and 1 more messages]

2014-10-09 Thread Dimitri John Ledkov

On 9 October 2014 17:24, Ian Jackson  wrote:
> Dimitri John Ledkov writes ("Re: dgit and upstream git repos"):
>> On 9 October 2014 15:38, Ian Jackson  wrote:
>> > If I can feed a .pc-less source tree to dpkg-source -b and get
>> > roughtly the right output then that would obviously be a big
>> > improvement.
>>
>> $ apt-get source sword
>> $ cd sword-*
>> $ rm -rf .pc
>> # a tree with up-to-date debian/patches, all patches are applied (as
>> e.g. git-dpm does), .pc directory is gone
>> $ dpkg-source -b .
>> $ echo $?
>> 0
>
> However,
>
>$ apt-get source sword
>$ cd sword-*
>$ rm -rf .pc
>$ echo 'some stupid change' >>AUTHORS

Invalid transition. dgit/git-dpm would error out that tree does not
match HEAD commit.
but none the less

>$ dpkg-source -b .
>  [error message about uncommitted changes]
>$ dpkg-source --commit
>  [add commit message]
>  [hideous pile of crap from attempting to reapply all patches]
>$8
>
> The question is this, then: given the result of the first four steps2
> above, how to produce a correct source package ?
>

I believe/assert:
(a) dpkg-source --commit should work in this case
(b) may or may not need extra help with --no-preparation,
--unapply-patches, --auto-commit, --abort-on-upstream-changes

I'll experiment more when i have more time to dig into this. Not gonna
burn the midnight oil over this.

-- 
Regards,

Dimitri.


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

Bug#754988: Bug#763360 closed by Ondřej Surý

2014-10-09 Thread Julien Cristau

On Fri, Oct 10, 2014 at 00:46:42 +0200, Bill Allombert wrote:

> On Tue, Oct 07, 2014 at 10:31:45AM +0200, Ondřej Surý wrote:
> > On Mon, Oct 6, 2014, at 21:14, Bill Allombert wrote:
> > > > Version: 1:1.3.1-4
> > > >
> > > > My understanding is that this bug can be now closed as
> > > > the libjpeg-progs are not built from src:libjpeg-progs and
> > > > libjpeg62* binary package names has been accepted now.
> > > 
> > > Excellent news! When do you plan to upload a version libjpeg-turbo that
> > > does not hijack libjpeg62 anymore ?
> > 
> > JFTR I will list the consequences of any renaming that would happen:
> > 
> > 1. libjpeg-turbo62 (as an example) would still contain shared library
> > libjpeg.so.62, thus it needs to "Conflicts/Provides: libjpeg62", same
> > applies for the libjpeg62-dev package vs libjpeg-turbo62-dev
> > ("Conflicts/Provides: libjpeg62-dev)
> 
> You are painting a bleaker picture than what is really required.
> Since the package are fully compatible, the conflict is easily avoided by
> moving some files a bit and then using the alternative system. 
> 
They're not fully compatible, as libjpeg-turbo's libjpeg.so.62 provides
additional entry points.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#764122: [tex-live] Bug#764122: MnSymbol and new[tp]x shouldn't be in the texlive-fonts-extra ghetto

2014-10-09 Thread Norbert Preining

On Thu, 09 Oct 2014, Karl Berry wrote:
> Do what you want in Debian, of course.  (Do you exactly 100% follow the
> TL collection constituents now?)

Yes, we follow it 100% (besides leaving out a few packages that
are packaged separately).

> I don't want to just randomly add things to c-fontsrecommended.

I agree. Only if there is good reason.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13



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

Bug#681501: Debian France on Debian's new donations page?

2014-10-09 Thread Paul Wise

On Thu, Oct 9, 2014 at 9:32 PM, Neil McGovern wrote:

> Done, and removed "tax-exempt" - I'm not sure it is, is it?

 is Debian France "tax-exempt"?
 pabs: yes, but the receipt we deliver likely only have value in France?

-- 
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#764578: [pkg-wine-party] Bug#764578: Bug#764578: [wine-development] add option to debian/rules to build without stack protection

2014-10-09 Thread Michael Gilbert

On Thu, Oct 9, 2014 at 10:02 AM, Konstantin Demin wrote:
> Firstly, this change makes it possible to compile wine with support
> for applications that rely on the implicit stack operations that are
> not possible when stack smash protection (SSP) is on. However, as you
> may have already seen in the patch, wine is compiled by default with
> SSP enabled.

Can you provide some examples of applications that are actually affected?

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#764380: Came with 0.1.23

2014-10-09 Thread Stuart Prescott

Dear Stephan,

> fwiw, this behaviour was introduced with 0.1.23. Versions <0.1.23 work
> fine (i.e., it's not a python update that introduced this).
> 
> Hth!

It does indeed help. Thanks for providing a succinct reproduce script and some 
bounds for investigation. A git bisect points at this commit as being the 
problem:

28530e3c1af3aab92f5860c5825ab7fb09e46182 is the first bad commit
commit 28530e3c1af3aab92f5860c5825ab7fb09e46182
Author: John Wright 
Date:   Thu Aug 28 20:57:56 2014 -0700

Drop support for python2.5.

This allows us to do fewer import hacks in deb822.  (Probably other
modules as well, but I've only touched deb822.)

:04 04 f1a7782f9b7e44c6a8d093e3eb226b1d3170c279 
ec23b2a36ec7426e45e1f83b1907c6b6dc3b6052 M  debian
:04 04 9fd436000e900cb6096793d62f4651e3afd9f18e 
615391b466fcb203c4ad80dcd4e4b4dbdc0bca6a M  lib

http://anonscm.debian.org/cgit/pkg-python-debian/python-
debian.git/commit/?id=28530e3c1af3aab92f5860c5825ab7fb09e46182


I have to say that nothing in that commit jumps out to me as being the 
problem. 

cheers
Stuart


-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7


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

Bug#730593: emacs24: fails to set fullscreen frame parameter on gnome 3

tags 730593 confirmed
thanks
[When possible, please preserve the -forward address in any replies.]

I can reproduce this with current Debian Gnome 3, while in XFCE, Emacs
does shift to full screen.

Pedro Ângelo  writes:

> Package: emacs24
> Version: 24.3+1-2
> Severity: normal
>
> Dear Maintainer,
>
> On my .emacs I use the following command to set the emacs window to fullscreen
> on startup:
>
> (set-frame-parameter nil 'fullscreen 'fullboth)
>
> This has stopped working in the Emacs24 package in debian testing since the
> recent gnome updates. From the alternatives at
> http://www.emacswiki.org/emacs/FullScreen, the following don't work:
>
>  * Starting Emacs with the -fs parameter
>
>  * Sending the fullscreen message directly to the window manager with
>
> (defun fullscreen ()
>(interactive)
>(x-send-client-message nil 0 nil "_NET_WM_STATE" 32
>  '(2 "_NET_WM_STATE_FULLSCREEN" 0)))
>
> What *does* work:
>
>  * Setting the window to fullscreen via the *wmctrl* external program
>
>   * Setting the window to fullscreen using the gnome key binding to toggle
> fullscreen
>
> This looks like some change in gnome made emacs not able to request fullscreen
> as a frame property

Further info: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730593

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4


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

Bug#764658: gdm3: cannot see all session choices on smaller screens


Package: gdm3
Version: 3.13.92-1

On a 1280x800 laptop display, the pop-up "bubble" for the session
chooser in gdm3 cuts off the lower sessions (and offers no scrollbar) so
that I can only select XFCE (for example) by guesswork now.

  $ ls /usr/share/xsessions/
  gnome-bluetile.desktop  gnome.desktop twm.desktop
  gnome-classic.desktop   kde-plasma.desktopxfce.desktop
  gnome-fallback.desktop  lightdm-xsession.desktop  xmonad.desktop
  gnome-flashback-compiz.desktop  sawfish.desktop

Perhaps gdm3 should be smarter about the placement of the bubble, add a
scrollbar, or use a more flexible widget.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4


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

Bug#754988: Bug#763360 closed by Ondřej Surý

2014-10-09 Thread Bill Allombert

On Tue, Oct 07, 2014 at 10:31:45AM +0200, Ondřej Surý wrote:
> On Mon, Oct 6, 2014, at 21:14, Bill Allombert wrote:
> > > Version: 1:1.3.1-4
> > >
> > > My understanding is that this bug can be now closed as
> > > the libjpeg-progs are not built from src:libjpeg-progs and
> > > libjpeg62* binary package names has been accepted now.
> > 
> > Excellent news! When do you plan to upload a version libjpeg-turbo that
> > does not hijack libjpeg62 anymore ?
> 
> JFTR I will list the consequences of any renaming that would happen:
> 
> 1. libjpeg-turbo62 (as an example) would still contain shared library
> libjpeg.so.62, thus it needs to "Conflicts/Provides: libjpeg62", same
> applies for the libjpeg62-dev package vs libjpeg-turbo62-dev
> ("Conflicts/Provides: libjpeg62-dev)

You are painting a bleaker picture than what is really required.
Since the package are fully compatible, the conflict is easily avoided by
moving some files a bit and then using the alternative system. 

When do you plan to operate the renaming ?

I need to reupload libjpeg62 with a bumped epoch before the freeze.

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#764650: zsh: FTBFS with noatime mounts

2014-10-09 Thread Frank Terbeck

Thorsten Glaser wrote:
> Frank Terbeck dixit:
[...]
>>  elif test -f /etc/mtab && { grep $(df . 2>/dev/null| tail -n1 | awk '{print 
>> $1}') /etc/mtab | grep -q noatime; }; then
[...]
> Hm, I think this rings a bell. Didn’t we have this on another buildd
> already, years ago, because something like mtab wasn’t available or
> something? Will need to dig through mail/bts archives…

Axel hinted at that on IRC, as well. He thought that /proc/mounts should
be available, which I think has the same syntax. We could just double up
the test, once against /etc/mtab and then against /proc/mounts.

Would that help?


Regards, Frank


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

Bug#559969: jslint can now be used for evil

2014-10-09 Thread Ben Finney

On 09-Oct-2014, Daniel Pocock wrote:

> Mr Crockford has apparently given the Eclipse Foundation permission
> to distribute jslint without the "no evil" clause.

Great news! Thank you for seeking reliable documentation of this
permission; and for carefully letting us know.

-- 
 \“… Nature … is seen to do all things Herself and through |
  `\ herself of own accord, rid of all gods.” —Titus Lucretius |
_o__) Carus, c. 40 BCE |
Ben Finney 


signature.asc
Description: Digital signature

Bug#764657: dcfldd FTBFS on arm64, outdated config.sub/guess

2014-10-09 Thread peter green


Package: dcfldd
Version: 1.3.4.1-4
Severity: important
Tags: patch

Your package is failing to build on arm64 due to outdated 
config.sub/guess. You already have autotools-dev in your build-depends 
but don't appear to be actually using it. Given that -2.1 succeeded and 
reading the changelog I presume this is a result of the debian/rules 
restructuring in -3 (no build of -3 was attempted on arm64, presumablly 
due to lack of buildd time).


A debdiff adding --with autotools-dev is attatched.

If there is no response to this bug a NMU may well follow, if you have 
any objections please raise them now.
diff -Nru dcfldd-1.3.4.1/debian/changelog dcfldd-1.3.4.1/debian/changelog
--- dcfldd-1.3.4.1/debian/changelog 2014-10-08 20:57:02.0 +
+++ dcfldd-1.3.4.1/debian/changelog 2014-10-09 19:53:47.0 +
@@ -1,3 +1,10 @@
+dcfldd (1.3.4.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use --with autotools-dev to update config.sub/guess
+
+ -- Peter Michael Green   Thu, 09 Oct 2014 19:53:05 +
+
 dcfldd (1.3.4.1-4) unstable; urgency=medium
 
   * Fixed the author name in these patches:
diff -Nru dcfldd-1.3.4.1/debian/rules dcfldd-1.3.4.1/debian/rules
--- dcfldd-1.3.4.1/debian/rules 2014-10-05 18:16:36.0 +
+++ dcfldd-1.3.4.1/debian/rules 2014-10-09 19:52:36.0 +
@@ -4,4 +4,4 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 %:
-   dh $@ --parallel
+   dh $@ --parallel --with autotools-dev

Bug#764650: zsh: FTBFS with noatime mounts

2014-10-09 Thread Thorsten Glaser

Frank Terbeck dixit:

>In particular for noatime:
>
>  elif test -f /etc/mtab && { grep $(df . 2>/dev/null| tail -n1 | awk '{print 
> $1}') /etc/mtab | grep -q noatime; }; then
>
>...which doesn't catch the problem in the buildd, it would seem.
>
>It does work on my laptop, but then, I have no clue about buildds. :)

Hm, I think this rings a bell. Didn’t we have this on another buildd
already, years ago, because something like mtab wasn’t available or
something? Will need to dig through mail/bts archives…

bye,
//mirabilos
-- 
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh


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

Bug#707760: zsh: Alternatives broken for long time during upgrade from zsh4 to zsh5

2014-10-09 Thread Axel Beckert

Hi,

Frank Terbeck wrote:
> Axel Beckert wrote:
> > Sven Joachim wrote:
> [...]
> >> How about adding a symlink /bin/zsh4 -> zsh5 in the zsh package?  Not
> >> extremely pretty, but it should work.
> >
> > What about putting a shell script at /bin/zsh4 which more or less
> > looks this?
> >
> >   #!/bin/sh
> >   
> >   echo "$0 is deprecated, please switch to /bin/zsh or /usr/bin/zsh" 1>&2
> >   exec /bin/zsh5 "$@"
> 
> I think this is the way to go. Maybe even like this:
> 
> #!/bin/zsh -f
> 
> if [[ -o interactive ]]; then
> echo "$0 is deprecated, please switch to /bin/zsh or /usr/bin/zsh" 1>&2
> echo "Use: chsh -s /bin/zsh" 1>&2
> echo "This command ($0) will disappear eventually!" 1>&2
> fi
> exec /bin/zsh "$@"

Good idea!

I have one more refinement: Since during the upgrade /bin/zsh will be
symlinked to this script (i.e. the reason for this bug report), it
should also check if $0 contains zsh4. So I'll likely later add a
script like this one:

#!/bin/zsh -f

if [[ -o interactive && $0 == *zsh4* ]]; then
echo "$0 is deprecated, please switch to /bin/zsh or /usr/bin/zsh" 1>&2
echo "Use: chsh -s /bin/zsh" 1>&2
echo "This command ($0) will disappear eventually!" 1>&2
fi
exec /bin/zsh "$@"

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


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

Bug#763164: bash: Shellshock fix breaks bash function exporting

2014-10-09 Thread TrueY

Package: bash
Version: 4.2+dfsg-0.1+deb7u3
Followup-For: Bug #763164



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

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 bash depends on:
ii  base-files   7.1wheezy6
ii  dash 0.5.7-3
ii  debianutils  4.3.2
ii  libc62.13-38+deb7u4
ii  libtinfo55.9-10

Versions of packages bash recommends:
ii  bash-completion  1:2.0-1

Versions of packages bash suggests:
pn  bash-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#764656: fheroes2-pkg: [INTL:pt] Portuguese translation for debconf messages

2014-10-09 Thread Américo Monteiro

Package: fheroes2-pkg
version: 0+svn20131009r3181-1-2
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for fheroes2-pkg's debconf messages.
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .

-- 
Melhores cumprimentos/Best regards,

Américo Monteiro


fheroes2-pkg_0+svn20131009r3181-1-2_pt.po.gz
Description: GNU Zip compressed data

Bug#762435: emacs24: Warning message from GLib-GObject

[When possible, please preserve the -forwarded address in any replies.]

Recently reported to Debian.

Santiago Vila  writes:

> Package: emacs24
> Version: 24.3+1-5+b1
>
> Hello Rob. I got this today under unstable:
>
> (emacs:29258): GLib-GObject-WARNING **: The property GtkMisc:xalign is
> deprecated and shouldn't be used anymore. It will be removed in a
> future version.
>
> which apparently means emacs is using some obsolete feature of Gtk.

cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762435

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4


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

Bug#764122: [tex-live] Bug#764122: MnSymbol and new[tp]x shouldn't be in the texlive-fonts-extra ghetto

2014-10-09 Thread Karl Berry

Do what you want in Debian, of course.  (Do you exactly 100% follow the
TL collection constituents now?)

For TL, I see that c-fontsrecommended has txfonts and pxfonts.  Perhaps
I should exchange those with the newtx and newpx in extra, but I'm not
sure.  I have a feeling that an awful lot of documents use the original
*xfonts and it would just create needless churn.  Michael (Sharpe), do
you have an opinion here?

I don't want to just randomly add things to c-fontsrecommended.

karl


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

Bug#764553: base-files: Does neither state which version nor which variant of the Artistic License is in /usr/share/common-licenses/Artistic

2014-10-09 Thread Axel Beckert

Hi again,

thanks for fixing this so quickly.

Santiago Vila wrote:
> > Another thing which I think would solve this issue easily, but which
> > may have some side effects I'm not yet aware of, would be to rename
> > the file to "Artistic-1.0-Perl" (or whatever) and make "Artistic" a
> > symlink to it, analogous how it's done for the different GPL versions.
> 
> That would be a possibility to which I'm not opposed in principle,

Happy to hear.

Do we need a minor/wishlist bug to track this?

> but for now I'm just going to clarify what we currently have without
> doing any major changes.

Yeah, bad time for opening pandora's box. Needed to be done, though.
:-)

> This is really a more complex problem

Definitely.

> and it should ideally be solved by the policy group, as they are who
> really decide about the contents of common-licenses (there is a
> question in the base-files FAQ about this).

*nod*

Niko Tyni wrote:
> For the record, I intend to scan at least the 3000 pkg-perl packages
> to see how common the Artistic license variants are and how they are
> reflected in debian/copyright files.

Thanks! So I can remove that from my TODO list again. :-)

If you don't intent to post the results on debian-perl@ldo, I'd be
happy if you could keep me in the line as I intent to write a lintian
test for the Artistic license differences after having had a look at
the results of this/your check.

> There's quite some possibility for errors in debian/copyright
> declarations due to confusion between the variants.

Yep. I think, we're lucky that /u/s/c-l/Artistic is the Perl one as
most perl modules are licensed "under the same terms as Perl".

> This should also help us estimate whether the variants might warrant
> addition in base-files.

Indeed. Good point.

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


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

Bug#707760: zsh: Alternatives broken for long time during upgrade from zsh4 to zsh5

2014-10-09 Thread Frank Terbeck

Axel Beckert wrote:
> Sven Joachim wrote:
[...]
>> How about adding a symlink /bin/zsh4 -> zsh5 in the zsh package?  Not
>> extremely pretty, but it should work.
>
> What about putting a shell script at /bin/zsh4 which more or less
> looks this?
>
>   #!/bin/sh
>   
>   echo "$0 is deprecated, please switch to /bin/zsh or /usr/bin/zsh" 1>&2
>   exec /bin/zsh5 "$@"

I think this is the way to go. Maybe even like this:

#!/bin/zsh -f

if [[ -o interactive ]]; then
echo "$0 is deprecated, please switch to /bin/zsh or /usr/bin/zsh" 1>&2
echo "Use: chsh -s /bin/zsh" 1>&2
echo "This command ($0) will disappear eventually!" 1>&2
fi
exec /bin/zsh "$@"

> Or maybe even
>
>   #!/bin/sh
>   set -e
>   
>   echo "$0 is deprecated, please switch to /bin/zsh or /usr/bin/zsh" 1>&2
>   /bin/zsh5 "$@"
>   exit 1

Too intrusive, IMHO.


Regards, Frank


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

Bug#733623: wxgeometrie: ImportError: No module named pyparsing