Bug#800921: libphonenumber7-java: fails to upgrade from 'jessie' - trying to overwrite /usr/share/java/geocoder.jar

[Andreas Beckmann]

Package: libphonenumber7-java
Version: 7.0.11-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libphonenumber7-java.
  Preparing to unpack .../libphonenumber7-java_7.0.11-2_all.deb ...
  Unpacking libphonenumber7-java (7.0.11-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libphonenumber7-java_7.0.11-2_all.deb (--unpack):
   trying to overwrite '/usr/share/java/geocoder.jar', which is also in package 
libphonenumber6-java 6.3~svn698-3
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libphonenumber7-java_7.0.11-2_all.deb


cheers,

Andreas


libphonenumber6-java=6.3~svn698-3_libphonenumber7-java=7.0.11-2.log.gz
Description: application/gzip

Bug#800923: libcorosync-common-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/include/corosync/corodefs.h

[Andreas Beckmann]

Package: libcorosync-common-dev
Version: 2.3.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libcorosync-common-dev:amd64.
  Preparing to unpack .../libcorosync-common-dev_2.3.5-1_amd64.deb ...
  Unpacking libcorosync-common-dev:amd64 (2.3.5-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libcorosync-common-dev_2.3.5-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/corosync/corodefs.h', which is also in 
package corosync-dev 1.4.6-1.1
  Errors were encountered while processing:
   /var/cache/apt/archives/libcorosync-common-dev_2.3.5-1_amd64.deb


cheers,

Andreas


corosync-dev=1.4.6-1.1_libcorosync-common-dev=2.3.5-1.log.gz
Description: application/gzip

Bug#800924: uronode: fails to upgrade from 'jessie' - trying to overwrite /usr/share/man/man1/nodeusers.1.gz

[Andreas Beckmann]

Package: uronode
Version: 2.3.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package uronode.
  Preparing to unpack .../uronode_2.3.1-1_amd64.deb ...
  Unpacking uronode (2.3.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/uronode_2.3.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/nodeusers.1.gz', which is also in 
package ax25-node 0.3.2-7.4
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/uronode_2.3.1-1_amd64.deb


cheers,

Andreas


ax25-node=0.3.2-7.4_uronode=2.3.1-1.log.gz
Description: application/gzip

Bug#800925: libatlas-cpp-0.6-tools: fails to upgrade from 'jessie' - trying to overwrite /usr/bin/atlas_convert

[Andreas Beckmann]

Package: libatlas-cpp-0.6-tools
Version: 0.6.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libatlas-cpp-0.6-tools.
  Preparing to unpack .../libatlas-cpp-0.6-tools_0.6.3-1_amd64.deb ...
  Unpacking libatlas-cpp-0.6-tools (0.6.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libatlas-cpp-0.6-tools_0.6.3-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/atlas_convert', which is also in package 
libatlas-cpp-0.6-dev 0.6.2-4.1
  Errors were encountered while processing:
   /var/cache/apt/archives/libatlas-cpp-0.6-tools_0.6.3-1_amd64.deb


cheers,

Andreas


libatlas-cpp-0.6-dev=0.6.2-4.1_libatlas-cpp-0.6-tools=0.6.3-1.log.gz
Description: application/gzip

Bug#610087: ITP: corsix-th -- Open source clone of Theme Hospital

[Phil Morrell]

On 3 October 2015 at 21:39, Alexandre Detiste
 wrote:
> Please reply and CC 610...@bugs.debian.org
> and quote this in full if you're ok with this.
>
>
> Le samedi 3 octobre 2015 21:10:53, vous avez écrit :
>> Hi,
>>
>> Would it be possible for me to help with the packaging of corsix-th (I
>> own the GOG version of the data files)? I've been lurking on the
>> Debian mailing lists for a while scouting for something suitable to
>> start with while trying to follow the maintainer guides. It's been a
>> long time since I've actually created a deb and I haven't setup a
>> debsign key or anything yet.
>> --
>> Phil Morrell
>
> Hi, of course you're welcome to work on this !
> You can adopt the bug if you want.
>
> I own this game retail & the one that is from time to time free on Origin.
> And game-data-packager can download the demo too.
>
>
> The "Not Invented Here" syndrome doen't give any value;
> so I'd really suggest to re-use work provided by the GetDeb package.
>
> So there's what remain todo:
> *) write a man page, you can even propose it to upstream
>   before starting with the Debian packaging
>
> *) stomp debian/copyright with a new machinereadable one with:
>
> debian/*
>2015 Phil Morrell 
>2011-2015 Christoph Korn 
>
> + all the licenses from LICENSE.txt cut in DEP-5 paragraphs.
>
> [ https://github.com/CorsixTH/CorsixTH/blob/master/LICENSE.txt ]
>
> *) review the source code, see if that really match with LICENSE.txt
>
> *) find a sponsor
>
>
> lintian 
> /var/cache/apt-cacher-ng/archive.getdeb.net/ubuntu/pool/games/c/corsix-th/corsix-th_0.50-1~getdeb3_amd64.deb
> P: corsix-th: no-upstream-changelog
> W: corsix-th: binary-without-manpage usr/games/corsix-th
> I: corsix-th: desktop-entry-lacks-keywords-entry 
> usr/share/applications/corsix-th.desktop

(Hello Games Team)

Thank you for the support and initial pointers, I would indeed like to
attempt to bring the existing packaging up to Debian's standards. I've
downloaded hopefully all I need to get started, including the engine,
game data, getdeb package outputs and the playdeb packaging repo. I'm
just looking at getting initial Alioth access setup for uploading the
orig tarball and sharing the dsc etc.

Bug#800928: realmd: FTBFS with GLib 2.45.7

[Robert Ancell]

Package: realmd
Severity: normal

Dear Maintainer,

realmd FTBFS with GLib 2.45.7, see patch in:
https://bugs.freedesktop.org/show_bug.cgi?id=92282

Thanks,
--Robert

-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 
'wily-proposed'), (500, 'wily'), (500, 'trusty-updates'), (500, 'trusty'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#800925: libatlas-cpp-0.6-tools: fails to upgrade from 'jessie' - trying to overwrite /usr/bin/atlas_convert

[Olek Wojnar]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: tags -1 pending

Fix should be uploaded shortly, thanks!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWEe+lAAoJEH2D1AagncHkxfEQAJHEOU0rq0YJq52Q6J+GErdW
CryQ7ToRpM7KdER1qjBq310k/3GWWxWibSCfXeAhmSIoPsGLAJ/IOv5Mh4f4ODeF
reKMue3wrJOwXvbTmtIs1zZpZfnub1x3MQsNfxC0Tz3CrghPXSktD7uksLkVONXA
RN5pnlh0duPC0Sd4GMDALc78N7cUqM4Cs5nNQD+bVCH1CYwU+P2lGNwYpfe+6K6C
MpnsZK2gonNWOCPUSsLn9Iz72n9SzT91i8IUVbhZjsRnytlv/t6OZHF2h9fPHeUz
cxvORNLiGqcTVzaKHFgYCpSBSglgzQfXnbyu0MxrnUIYha/Ci2eTfixe5ERxFFwU
e5rlgMoAo+xCj91P5hSlnKYHsmhhmBZ8BmEZFxX7bIdrg7ZfBynBoZw3XZXzhThr
SguZAi/5bhJXLhSnF2JJd0l2/eH9Ke+Hv7TZxRN6nmZ4rAheP8vJiQCdiBpOaEii
+VTmC2/yD/YJ44iujXekayRmcqucbM1+0m2z7nBVn+bHoAOaRxGD7vikRBSfClds
OA0Tnx9iJwtx1dvegF5fmI7aYo5gHz3uPt0Q9DKM7+WkM/I9m41mI3xvPckcC7Fu
9IjNUbgLfIwk/aCNVHGuS5qY1N3/kJBWnXfxGpAca6RhceWZG5N+QD6AZpCDDNJd
Gms2YjSSPcuDp4Ruc9wz
=nInr
-END PGP SIGNATURE-

Bug#677915: FW:9/25/2015 4:02:31 AM

[jeanluke_cyprus]

 http://021ae.com/elhweo/mtifurkyonmkiqbtzegcghutkcxuxzny.ayufwugcryedwbwtrqpak
 
jeanluke_cyp...@yahoo.com

Sent from my iPhone   

Bug#800922: libmicrospdy-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/x86_64-linux-gnu/pkgconfig/libmicrospdy.pc

[Andreas Beckmann]

Package: libmicrospdy-dev
Version: 0.9.42+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libmicrospdy-dev.
  Preparing to unpack .../libmicrospdy-dev_0.9.42+dfsg-2_amd64.deb ...
  Unpacking libmicrospdy-dev (0.9.42+dfsg-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmicrospdy-dev_0.9.42+dfsg-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/libmicrospdy.pc', 
which is also in package libmicrohttpd-dev 0.9.37+dfsg-1+b1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libmicrospdy-dev_0.9.42+dfsg-2_amd64.deb


cheers,

Andreas


libmicrohttpd-dev=0.9.37+dfsg-1+b1_libmicrospdy-dev=0.9.42+dfsg-2.log.gz
Description: application/gzip

Bug#800926: RFP: python-compago -- framework for simple command-line parsing

[Ben Finney]

Package: wnpp
Severity: wishlist

* Package name: python-compago
  Version : 1.4
  Upstream Author : Justin Mohr 
* URL : https://pypi.python.org/pypi/compago/
* License : BSD-3-clause
  Programming Lang: Python
  Description : framework for simple command-line parsing

Write polished command line applications in a fraction of the
time. Guaranteed, or double your money back!

Compago is a framework for simple command-line parsing in Python.
Compago provides a simple framework and set of decorators to allow
you to quickly and easily define a set of commands within a
script. For those familiar with Ruby's Thor, Compago fills a
similar niche.

This project was inspired by the excellent Flask-Script extension
for Flask, but has been entirely rewritten to remove all Flask
dependencies.

-- 
 \“Considering the current sad state of our computer programs, |
  `\ software development is clearly still a black art, and cannot |
_o__)  yet be called an engineering discipline.” —Bill Clinton |
Ben Finney 


signature.asc
Description: PGP signature

Bug#800927: atlas-cpp: Symbols need to be updated for several architectures

[Olek Wojnar]

Source: atlas-cpp
Version: 0.6.3-1
Severity: important

Dear Me,

The latest version of atlas-cpp does not contain correct symbols for the
following architectures:
armel
armhf
i386
mips
mipsel
powerpc
hppa
hurd-i386
kfreebsd-i386
x32

The regex tags appear to have been removed unintentionally. Replacing them
should correct this problem.

Bug#800927: Acknowledgement (atlas-cpp: Symbols need to be updated for several architectures)

[Olek Wojnar]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: tags -1 pending
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWEeniAAoJEH2D1AagncHkbC0P+wQ/8YHtiZ/pHB7UHNL96oeR
z7Q+KUInQzAs0BtgflSyYm5f23CkXPR05s1tEcdUlEI9ZQLQB8xcKYMrTQAMWBTl
ktTptIBHSO51q16xZIxO1TPh7YMdvHXpSqTdPIn3d0uLQSTuOz/YYcONOlMI/BBV
7Gf1Bg1LyRe+GS8yXIIUDmM4AvHHSbjU7NYpvvJ/PT3iEj1Rh6cThzC5ujAIREOh
t3406og/vrmyXfuYJSZEd2CyhZLKKliLwlMQd3bcKMkHocheFcrKJUAGOiItQhSs
+BX4HSv21Cilw8NvDDbhQBHJCEIBqwPuAb1vSVozsFQVNDaSpY8Tk/wkhC/Hvep8
70HUZfT33jqbDx2P7K42ymRgtT4zyIy5wmk2XhX/aDp9EwYgF4OuCZCEbV8hVe+p
hc4JNNGg1392JRUN8rSxOrGiqLziYavYHUfmMdxkWUuizbhGo824F6BDJsi3jvl2
ke8qm2qiRv0RhGKTjj/BWwKwhNa5SeoTZ17wuTlxDeH2fx7KnAwQFNx4qR8mxV2j
ofmf4XvKJI4//g8jOXCupn/Al2DZhoMo4x/0Alazia1CSnKGNktHfNu4x7cmme26
6EmadSJBb6+D9LNWaf+HBm5mm3vlXzQq9dzDY/rqghHGSgdTRzoOGRq946687mY4
QemcB+pOsxd2jTasGI77
=fIIJ
-END PGP SIGNATURE-

Bug#783770: Request for CUDA 7

[lumin]

Package Caffe maintained by me now suffers FTBFS,
one way to solve this FTBFS is to bump CUDA from 6.5 to 7,
because CUDA 7 can work with GCC 5 (>> 4.9).

So I request for CUDA 7 too.


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

Bug#800929: linux_source-3.16: Scheduler prefers pinned tasks

[Paul Szabo]

Package: linux_source-3.16
Version: 3.16.7-ckt11-1+deb8u4
Severity: normal

The Linux CFS scheduler prefers pinned tasks and unfairly
gives more CPU time to tasks that have set CPU affinity.
This effect is observed with or without CGROUP controls.

To demonstrate: on an otherwise idle machine, as some user
run several processes pinned to each CPU, one for each CPU
(as many as CPUs present in the system) e.g. for a quad-core
non-HyperThreaded machine:

  taskset -c 0 perl -e 'while(1){1}' &
  taskset -c 1 perl -e 'while(1){1}' &
  taskset -c 2 perl -e 'while(1){1}' &
  taskset -c 3 perl -e 'while(1){1}' &

and (as that same or some other user) run some without
pinning:

  perl -e 'while(1){1}' &
  perl -e 'while(1){1}' &

and use e.g.   top   to observe that the pinned processes get
more CPU time than "fair".

Fairness is obtained when either:
 - there are as many un-pinned processes as CPUs; or
 - with CGROUP controls and the two kinds of processes run by
   different users, when there is just one un-pinned process; or
 - if the pinning is turned off for these processes (or they
   are started without).

Any insight is welcome!

Thanks, Paul

Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia


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

Kernel: Linux 3.16.7-ckt11-pk07.13.8-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.16.7-ckt11-pk07.13-amd64 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx 
-fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 
-fcall-saved-r11"
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y

#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
# CONFIG_KERNEL_GZIP is not set
CONFIG_KERNEL_BZIP2=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_FHANDLE=y
CONFIG_USELIB=y
# CONFIG_AUDIT is not set
CONFIG_HAVE_ARCH_AUDITSYSCALL=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_LEGACY_ALLOC_HWIRQ=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CMOS_UPDATE=y

#
# Timers subsystem
#
CONFIG_HZ_PERIODIC=y
# CONFIG_NO_HZ_IDLE is not set
# CONFIG_NO_HZ_FULL is not set
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set

#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_IRQ_TIME_ACCOUNTING is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y

#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_PREEMPT_RCU is not set
CONFIG_RCU_STALL_COMMON=y
# CONFIG_RCU_USER_QS is not set
CONFIG_RCU_FANOUT=32
CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_RCU_NOCB_CPU is 

Bug#714222: FW:Re: 9/25/2015 4:02:37 AM

[jeanluke_cyprus]

 http://conradsinclair.com/wv/pwkzgqlnhtefhq.gixonbagfmkpclhmlwlhqy
 
jeanluke_cyp...@yahoo.com

Sent from my iPhone   

Bug#800077: virtualbox: Cannot install 5.0.4-dfsg-3 with just modules

[candeb]

Hi again,

Sorry, I should have thought about it earlier but only realised it when I still 
couldn't upgrade without the sources : Debian does not allow versioned 
dependencies on virtual package names.  In other words, if you put any version 
requirement on virtualbox-modules it will only accept a package actually named 
virtualbox-modules with an appropriate version, a "provides" will not be 
accepted.

Will you find it acceptable to remove the version constraints from the 
"virtualbox-modules" dependency ?  I think this would not change much from your 
point of view - a user who is competent enough to compile and install separate 
module packages would know what to do if virtualbox complains the installed 
modules are for an older version, no ?

Cheers,
I.


- Mail original -
De: "Gianfranco Costamagna" 
À: can...@free.fr
Cc: 800...@bugs.debian.org, "Ritesh Raj Sarraf" 
Envoyé: Lundi 28 Septembre 2015 09:00:13
Objet: Re: Bug#800077: virtualbox: Cannot install 5.0.4-dfsg-3 with just modules

Hi


>Thanks, but I beg to disagree : you need
>
>virtualbox-dkms OR virtualbox-source  ** OR virtualbox-modules **
>
>I compile modules on one machine and use them on several others.  Why force 
>me to install the module sources, kernel headers, and all the rest if I
>already have the compiled modules ?


sure, this is a perfectly valid use-case :)
http://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/commit/?id=41a45bc76907ad2921e4ad50fc6c1b8fba45fad4

committed, on git, can you please tell me if it works for you?


I also changed the dependency to >= instead of =, because the kernel modules 
should work even if from
other virtualbox versions.

(I'm specially thinking about getting a new dkms and keep an old virtualbox, 
just because the kernel has been upgraded)

@Ritesh, how do you feel about that commit?

cheers,

Gianfranco

Bug#789092: dosbox: please improve interoperability with wine

[Graham Inggs]

Hi

> I had a short look on the upstream repository, seems upstream is alive.
> At the same time the last release is quite old. Do you know if there's a
> chance for a new release soon (in months maybe)?

I pinged Peter Veenstra (qbix79 on sourceforge) about a new release.

> Otherwise, can you either apply the patches mentioned by Graham Inggs,
> or package a snapshot from upstream?

Since dosbox's maintainer agrees with Low Threshold NMU, I intend to
NMU dosbox 0.74 including the above-mentioned in a few days.

Regards
Graham

Bug#800085: linux-image-4.1.0-2-armmp: The ethernet fails to come up on my Allwinner A10 device.

[Ian Campbell]

On Sun, 2015-09-27 at 02:55 +0200, Gianluca Renzi wrote:
> Sorry but I don't agree with you. Supposing the allwinner A10 device
> need some voltage regulator drivers to be enabled in the kernel to
> have some devices in a working state, this not hurts some other
> devices that have some other configuration setting different in
> hardware layout. They are defined in the device tree for this
> particular machine, vendor or somewhere else. So the drivers for the
> regulator can be safely inserted into the A10 Debian kernel and you
> will don't break down anything.

Ben said, and I agree, that nothing in the set of modules suggested in
the URL enables any kind of real regulator. So while everything you say
is true, it is of no relevance here I'm afraid.

If you know of a specific option for a _physical_ regulator device (or
other physical bit of h/w) which should be enabled and/or loaded to fix
this issue then please let us know what it is.

Thanks,
Ian.

Bug#800844: ITP: bhyve -- hypervisor/virtual machine manager for FreeBSD

[Christoph Egger]

Package: wnpp
Severity: wishlist
Owner: Christoph Egger 

* Package name: bhyve
  Version : 10.2
  Upstream Author : FreeBSD Foundation
* URL : http://bhyve.org/
* License : BSD
  Programming Lang: C / ASM
  Description : hypervisor/virtual machine manager for FreeBSD

Bug#800795: Bug#800798: gtk+3.0: Please add breaks for python(3)-gi << 3.18

[Simon McVittie]

Control: severity 800798 serious
Control: reassign 800795 gir1.2-gtk-3.0 3.18.0-1
Control: forcemerge 800798 800804 800795
Control: affects 800798 + quodlibet virt-manager

On Sat, 03 Oct 2015 at 20:17:29 +0200, Christoph Reiter wrote:
> I'm not sure if this is the right thing to do but maybe add a breaks << 3.18
> for the two packages in gir1.2-gtk-3.0?

Good idea, but we should probably have the new pygobject first.
I'm doing a test build now.

S

Bug#781607: [Pkg-freeipa-devel] Bug#781607: Bug#781607: FreeIPA 4.2

[Harald Dunkel]

Hi freeipa maintainers and everybody involved,

I just found the new version 4.1.4 in the repository. This
is amazing. Can't wait to try it out.

Please keep on you good work
Harri

Bug#800840: ecasound FTBFS on Alpha: use of infinities despite compilation with -ffast-math

[Michael Cree]

Source: ecasound
Version: 2.9.1-7
Severity: important
Justification: fails to build from source but built in the past
User: debian-al...@lists.debian.org
Usertags: ftbfs

Ecasound FTBFS on Alpha due to a test-suite failure [1]:

make  check-TESTS
make[5]: Entering directory '/«PKGBUILDDIR»/libecasound'
make[6]: Entering directory '/«PKGBUILDDIR»/libecasound'
../test-driver: line 107: 22820 Floating point exception"$@" > $log_file 2>&1
FAIL: libecasound_tester

Running the test suite under gdb reveals the place of the floating
point exception to be:

#0  0x000120114d30 in GENERIC_OSCILLATOR::set_parameter (this=0x12022ec10, 
param=, value=0) at osc-gen.cpp:208

which is on the line of code:

loop_length_rep = 1.0f / frequency();

i.e., a division by frequency() after setting frequency to zero, thus
a division by zero.  But ecasound is compiled with -ffast-math, which
according to the gcc manual in turn sets -ffinite-math-only which is
a guarantee to the compiler that all floating point calculations are
finite.  On Alpha abusing that guarantee results in a floating point
exception and program termination.

Assuming it is intended that frequencies can be zero I attach a patch
that protects against the division by zero.  With that ecasound builds
to completion on Alpha.

(In the patch I also assume that frequencies are non-negative thus
there is no possibility of -0.0 as a frequency.)

Cheers
Michael.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=ecasound=alpha=2.9.1-7=1440432975
Index: ecasound-2.9.1/libecasound/osc-gen.cpp
===
--- ecasound-2.9.1.orig/libecasound/osc-gen.cpp
+++ ecasound-2.9.1/libecasound/osc-gen.cpp
@@ -205,7 +205,10 @@ void GENERIC_OSCILLATOR::set_parameter(i
   switch (param) {
   case 1: 
 frequency(value);
-loop_length_rep = 1.0f / frequency(); // length of one wave in seconds
+if (frequency() == 0.0)
+  loop_length_rep = INFINITY;   // Protect against div by zero
+else
+  loop_length_rep = 1.0f / frequency(); // length of one wave in seconds
 break;
 
   case 2: 

Bug#789092: dosbox: please improve interoperability with wine

[Graham Inggs]

On 4 October 2015 at 11:59, Graham Inggs  wrote:
> Since dosbox's maintainer agrees with Low Threshold NMU, I intend to
> NMU dosbox 0.74 including the above-mentioned in a few days.

Reminder to myself to include fix for #792886 (dosbox: MOUNT uses stat
to check if directory exists, fails with inodes greater then 2^32) as
well.

Bug#673772: mips: ATC with syscalls not working

[Nicolas Boulenguez]

Package: gnat-4.9
Followup-For: Bug #673772
Control: retitle: ATC with syscalls not working
Control: reassign -1 gnat-5 5.2.1-19

As I understand the reference manual, the following program
  with Ada.Calendar; use Ada.Calendar;
  with Ada.Text_IO;  use Ada.Text_IO;
  with Interfaces.C; use Interfaces.C;
  procedure Main is
 function usleep (Secs : int) return int;
 pragma Import (C, usleep, "usleep");
 Res: int;
 Start_Time : Time := Clock;
  begin
 select
delay 1.0;
Put_Line ("OK:" & Integer'Image (Integer (Clock - Start_Time)));
 then abort
Res := usleep (10_000_000);
Put_Line ("KO:" & Integer'Image (Integer (Clock - Start_Time)));
 end select;
  end Main;
should produce
  OK: 1
Instead, on amd64 with gnat-5.2.1-17:
  KO: 1
  OK: 1
and on mips with gnat-5.2.1-19:
  KO: 10
  OK: 10

Bug#800085: linux-image-4.1.0-2-armmp: The ethernet fails to come up on my Allwinner A10 device.

[Ian Campbell]

On Sat, 2015-09-26 at 18:04 +0100, Ben Hutchings wrote:
> Control: tag -1 - newcomer
> Control: tag -1 moreinfo
> 
> On Sat, 2015-09-26 at 12:10 -0400, Matthew Schneider wrote:
> > Package: src:linux
> > Version: 4.1.6-1
> > Severity: important
> > Tags: newcomer
> > 
> > Dear Maintainer,
> > 
> >* What led up to the situation?
> > Attempted to install the mainline Debian kernel for the first time
> on
> > this system.
> >* What was the outcome of this action?
> > The ethernet did not come up. 
> > 
> > The problem seems to be outlined and solved here: 
> > 
> http://comments.gmane.org/gmane.comp.hardware.netbook.arm.sunxi/17147
> >  
> > It would seem that an additional module needs to be included for it
> > to work correctly.
> [...]
> 
> None of the extra modules that were enabled as a 'solution' have
> anything to do with this hardware (or any real hardware).  So I don't
> think we have a real solution.

I agree, the URL suggests:
> CONFIG_REGULATOR_DEBUG=y
> CONFIG_REGULATOR_VIRTUAL_CONSUMER=y
> CONFIG_REGULATOR_USERSPACE_CONSUMER=y
> CONFIG_PWM_SUN4I=y

Of which the first is a debug option, the second two are "virtual" (in
that they don't relate to any real hardware) and the final one, while
related to h/w it is not h/w which should have anything to do with
Ethernet.

My best guess is that one of these has some sort of knock-on dependency
which causes something else to be enabled. I'm going to investigate
that possibility now... In the meantime:

> Please send the boot log from Linux 4.1 (or 4.2, which just landed in
> unstable).

Yes, please.

It would also be useful/interesting to know which Allwinner A10 device
this was with.

Ian.

Bug#717014: on some archs, a library using Elementary_Functions needs -lm

[Nicolas Boulenguez]

Package: gnat-4.9
Followup-For: Bug #717014
Control: reassign -1 gnat-5 5.2.1-19

Confirmed on mips.

Bug#799853: linux-image-2.6.32-5-xen-amd64: Xen kernel BUG: unable to handle kernel paging request

[Ian Campbell]

On Wed, 2015-09-23 at 11:51 +0200, Zdeněk Bělehrádek wrote:
> Package: linux-2.6
> Version: 2.6.32-48squeeze10

I'm afraid that with Squeeze being old-old-stable at this point your
best bet is going to be to upgrade at least the kernel if not the whole
distro to something > Squeeze.

I'd suggest starting with 2.6.32-48squeeze14 from the lts effort, if
that doesn't help (which I think is most likely going to be the case)
then 3.2.68-1+deb7u3~bpo60+1 from the o-o-bpo might be a good bet.
That's assuming you cannot upgrade the entire system to Wheezy or even
Jessie, which would be best of course.

Ian.


> Severity: important
> 
> 
> We have several virtual servers running under Xen, and two of them
> crash every few hours to days. Crash times are quite random, we have
> seen two crashes just about 2 minutes apart, and also few days went
> without crashing.
> 
> The crashing servers are used as mailservers, and run several
> instances of Exim, each listenning on different loopback and public
> IP address. Our customer uses it to send bulk e-mails, so there are
> long intervals of inactivity. We do have more of these serevrs, only
> two of them are crashing.
> 
> I checked the core dump with the crash utility, and it always hits
> kernel BUG: unable to handle kernel paging request, always in the
> same function and with the same backtrace. The crash is always
> triggered by collectd process. We tried to update kernel to latest
> version, and it had no effect. 
> 
> The hypervisor is xen-hypervisor-4.4-amd64 from Debian Jessie, the
> Dom0 is also Jessie. There is enough RAM in physical HW to support
> all the guests and some more.
> 
> I censored hostnames and IP addresses to protect the innocent.
> 
> -- Dmesg from crashed guest:
> 
> [12694.749508] BUG: unable to handle kernel paging request at
> 880002c49500
> [12694.750086] IP: [] inet_diag_dump+0x39f/0x78f
> [inet_diag]
> [12694.750690] PGD 1002067 PUD 1006067 PMD 3a9f067 PTE 0
> [12694.751300] Oops:  [#1] SMP 
> [12694.751932] last sysfs file: /sys/devices/vbd
> -2049/block/xvda1/uevent
> [12694.752007] CPU 0 
> [12694.752007] Modules linked in: tcp_diag inet_diag loop snd_pcm
> snd_timer snd soundcore snd_page_alloc evdev pcspkr joydev ext3 jbd
> mbcache dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq
> async_xor xor async_memcpy async_tx raid1 raid0 multipath linear
> md_mod xen_blkfront xen_netfront
> [12694.752007] Pid: 892, comm: collectd Not tainted 2.6.32-5-xen
> -amd64 #1 
> [12694.752007] RIP: e030:[]  []
> inet_diag_dump+0x39f/0x78f [inet_diag]
> [12694.752007] RSP: e02b:8800fcc31a88  EFLAGS: 00010246
> [12694.752007] RAX: 880002c49500 RBX: 8800fc558c70 RCX:
> 
> [12694.752007] RDX: 8800fef1cdc0 RSI: 8800fc558c60 RDI:
> 8800fd848148
> [12694.752007] RBP: 880002c3ef00 R08: 8800fc558000 R09:
> 
> [12694.752007] R10: 7f08762daeb0 R11: 8127be52 R12:
> 8800fc558c60
> [12694.752007] R13: 8800fdd8ea20 R14: 8800fd848000 R15:
> 8800fc558c60
> [12694.752007] FS:  7f08762db700() GS:880003add000()
> knlGS:
> [12694.752007] CS:  e033 DS:  ES:  CR0: 8005003b
> [12694.752007] CR2: 880002c49500 CR3: fd023000 CR4:
> 2660
> [12694.752007] DR0:  DR1:  DR2:
> 
> [12694.752007] DR3:  DR6: 0ff0 DR7:
> 0400
> [12694.752007] Process collectd (pid: 892, threadinfo
> 8800fcc3, task 8800fc902350)
> [12694.752007] Stack:
> [12694.752007]  81255a22 8800fc558000 0004
> 880002b14f00
> [12694.752007] <0> 001c 816e1f80 001c00d0
> 
> [12694.752007] <0> 880002a5a810 816e1d80 00d0
> 0074
> [12694.752007] Call Trace:
> [12694.752007]  [] ? sock_rmalloc+0x29/0x86
> [12694.752007]  [] ? netlink_dump+0x54/0x16c
> [12694.752007]  [] ? netlink_recvmsg+0x1a6/0x2c0
> [12694.752007]  [] ?
> hrtimer_try_to_cancel+0x3a/0x43
> [12694.752007]  [] ? sock_recvmsg+0xa6/0xbe
> [12694.752007]  [] ?
> autoremove_wake_function+0x0/0x2e
> [12694.752007]  [] ?
> autoremove_wake_function+0x0/0x2e
> [12694.752007]  [] ? verify_iovec+0x52/0xa2
> [12694.752007]  [] ? verify_iovec+0x52/0xa2
> [12694.752007]  [] ? sys_recvmsg+0x1b7/0x2cc
> [12694.752007]  [] ? sk_prot_alloc+0x79/0x12f
> [12694.752007]  [] ? sock_attach_fd+0x91/0xbf
> [12694.752007]  [] ? fd_install+0x2e/0x5a
> [12694.752007]  [] ? sock_map_fd+0x57/0x64
> [12694.752007]  [] ? system_call_fastpath+0x16/0x1b
> [12694.752007] Code: 34 4c 89 f7 c7 43 3c 00 00 00 00 e8 88 b8 0d e1
> c7 43 44 00 00 00 00 89 43 40 41 80 7c 24 10 0a 75 35 0f b7 45 38 48
> 8d 44 05 00 <48> 8b 10 49 89 54 24 18 48 8b 40 08 49 89 44 24 20 0f
> b7 45 38 
> [12694.752007] RIP  [] inet_diag_dump+0x39f/0x78f
> [inet_diag]
> [12694.752007]  RSP 
> [12694.752007] CR2: 880002c49500
> 

Bug#800843: Please upload last upstream version

[Yvan Masson]

Package: fotowall
Version: 0.98~beta+git20150707-1

Dear maintainer,

Could you please update your package to last upstream version ?
Fortunately it is going to solve #795753...

Regards,
Yvan

Bug#760211: on some archs, a library using Task_Attributes needs -lpthread

[Nicolas Boulenguez]

Package: gnat-4.9
Followup-For: Bug #760211
Control: reassign -1 gnat-5 5.2.1-21

Confirmed on kfreebsd-amd64.

Bug#800085: linux-image-4.1.0-2-armmp: The ethernet fails to come up on my Allwinner A10 device.

[Ian Campbell]

On Sun, 2015-10-04 at 11:17 +0100, Ian Campbell wrote:

> I agree, the URL suggests:
> > CONFIG_REGULATOR_DEBUG=y
> > CONFIG_REGULATOR_VIRTUAL_CONSUMER=y
> > CONFIG_REGULATOR_USERSPACE_CONSUMER=y
> > CONFIG_PWM_SUN4I=y
> 
[...]
> My best guess is that one of these has some sort of knock-on dependency
> which causes something else to be enabled. I'm going to investigate
> that possibility now...

Nope, it turns out PWM_SUN4I is already on in our config and the other
three are independent and turn on nothing else, which was basically as
expected since they are all virtual.

SUN4I_PWM is a module, so it might be worth modprobing that (module
will be pwm-sun4i it seems) to ensure it is loaded and see if that
helps. I don't think it will though.

>  In the meantime:
> 
> > Please send the boot log from Linux 4.1 (or 4.2, which just landed in
> > unstable).
> 
> Yes, please.
> 
> It would also be useful/interesting to know which Allwinner A10 device
> this was with.

... and the .config for your working self-built kernel would be useful
for comparison too. As well as a dmesg from both the Debian kernel and
that one.

Given the self-built+working kernel was 3.16 based and the Debian one
was 4.1 it may just be that 4.1 has a bug with the Ethernet, so trying
4.2 would indeed be wise too.

Ian.

Bug#800870: pygobject: fails to interoperate with Gtk 3.18

[Simon McVittie]

Source: pygobject
Version: 3.16.2-1
Severity: serious
Tags: fixed-upstream
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=749625
Control: block 800798 by -1

pygobject < 3.18 doesn't work with the GIR from Gtk >= 3.18.
See:
https://bugzilla.gnome.org/show_bug.cgi?id=749625
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800798
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800804
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800795

The easiest way to address this is probably to update pygobject,
then add Breaks in the Gtk GIR as suggested in #800798.

Regards,
S

Bug#800871: udev: /dev/snd is only readable by root

[Sébastien Dailly]

Package: udev
Version: 226-3
Severity: normal

Hello,

after the system startup, /dev/snd is only readable by root :

> sudo ls -lah /dev/snd
> total 0
> drwxr-x---  3 root root  220 oct.   4 14:20 .
> drwxr-xr-x 15 root root 3,2K oct.   4 14:20 ..
> drwxr-xr-x  2 root root   60 oct.   4 14:20 by-path
> crw-rw  1 root audio 116,  2 oct.   4 14:20 controlC0
> crw-rw  1 root audio 116,  7 oct.   4 14:20 hwC0D0
> crw-rw  1 root audio 116,  4 oct.   4 14:20 pcmC0D0c
> crw-rw  1 root audio 116,  3 oct.   4 14:20 pcmC0D0p
> crw-rw  1 root audio 116,  5 oct.   4 14:20 pcmC0D1p
> crw-rw  1 root audio 116,  6 oct.   4 14:20 pcmC0D2c
> crw-rw  1 root audio 116,  1 oct.   4 14:20 seq
> crw-rw  1 root audio 116, 33 oct.   4 14:20 timer

This break pulseaudio to initialize correctly. I do not know the
permissions to other users have been dropped.

I do not know if the problem comes from udev or other, but I would like
to know how to restore the correct permissions on system startup.

Thanks.

-- Package-specific info:

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

Kernel: Linux 4.2.0-1-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
Init: sysvinit (via /sbin/init)
P: /devices/LNXSYSTM:00
E: DEVPATH=/devices/LNXSYSTM:00
E: MODALIAS=acpi:LNXSYSTM:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:01
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:02
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:02
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:03
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:03
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXPWRBN:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00
E: DRIVER=button
E: MODALIAS=acpi:LNXPWRBN:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
E: EV=3
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: KEY=10 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: NAME="Power Button"
E: PHYS="LNXPWRBN/button/input0"
E: PRODUCT=19/0/1/0
E: PROP=0
E: SUBSYSTEM=input
E: USEC_INITIALIZED=5451959

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event1
N: input/event1
E: DEVNAME=/dev/input/event1
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event1
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: MAJOR=13
E: MINOR=65
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=5701294

P: /devices/LNXSYSTM:00/LNXSYBUS:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00
E: MODALIAS=acpi:LNXSYBUS:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00
E: MODALIAS=acpi:PNP0A03:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0003:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0003:00
E: MODALIAS=acpi:PNP0003:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0103:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0103:00
E: MODALIAS=acpi:PNP0103:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C02:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C02:00
E: MODALIAS=acpi:PNP0C02:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP:00
E: MODALIAS=acpi:PNP:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0100:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0100:00
E: MODALIAS=acpi:PNP0100:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0200:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0200:00
E: MODALIAS=acpi:PNP0200:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0303:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0303:00
E: MODALIAS=acpi:PNP0303:PNP030B:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0400:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0400:00
E: MODALIAS=acpi:PNP0400:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0401:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0401:00
E: MODALIAS=acpi:PNP0401:
E: SUBSYSTEM=acpi

Bug#797878: QNAP TS-219P II bricked by linux-image-4.1.0-0.bpo.1-kirkwood (4.1.3-1~bpo8+1) from jessie-backports: missing dependency on updated flash-kernel package

[Ian Campbell]

On Thu, 2015-09-03 at 11:58 +0200, Robert Schlabbach wrote:
> Proposed fix: Add flash-kernel 3.45 to jessie-backports and add a
> dependency of any Linux kernels 3.17 or later on at least this
> package version.

Agreed. The important change was made in flash-kernel 3.37 so the
breaks in the kernel should be updated to at least that.

I'll do that and arrange for f-k 3.46 to go into bpo.

Thanks,
Ian.

Bug#800875: pm-utils: cannot resume from suspend after upgrade to jessie

[Bryan Jurish]

Package: pm-utils
Version: 1.4.1-15
Severity: normal

Dear Maintainer(s),

After upgrading from wheezy to jessie, I am unable to resume from
suspend.  pm-suspend appears to function as expected (drives spin down,
fans stop, screen blanks), but the keyboard spacebar, power button,
mouse, and wake-on-lan packets all fail to wake the machine.

Odd symptom: after issuing `pm-suspend` (or `s2ram --force` or
`echo mem >/sys/power/state`), the keyboard (Kinesis FreeStyle) "FN" led
is lit.  Pressing the spacebar immediately causes the LED to extinguish
and the display's "no signal" message to appear.

I was unable to boot with my previous kernel (3.2.0-4-686-pae) to test
whether this might be a kernel issue.

Boot options "nodemodeset" and "pnpbios=off" had no effect.  Option
"acpi=off" made pm-suspend a no-op (as is probably to be
expected). Mainboard is an Intel DP67BG, graphics card is a Radeon
HD5450 (using xorg "radeon" driver, not fglrx).  suspend/resume worked
great in wheezy under previous kernel.

Any help and/or advice would be appreciated.

marmosets,
  Bryan

-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)

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

Versions of packages pm-utils depends on:
ii  powermgmt-base  1.31+nmu1

Versions of packages pm-utils recommends:
ii  ethtool  1:3.16-1
ii  hdparm   9.43-2
ii  kbd  1.15.5-2
ii  procps   2:3.3.9-9
ii  vbetool  1.1-3

Versions of packages pm-utils suggests:
pn  cpufrequtils
ii  radeontool  1.6.3-1
pn  wireless-tools  

-- no debconf information


-- 
Bryan Jurish   "There is *always* one more bug."
moocow.bov...@gmail.com -Lubarsky's Law of Cybernetic Entomology


lspci-v.out
Description: Binary data


lsusb-v.out
Description: Binary data
Initial commandline parameters: 
Sun Oct  4 13:39:17 CEST 2015: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend:
/usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend: success.

Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux carrot 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt11-1+deb8u4 (2015-09-19) i686 GNU/Linux
Module  Size  Used by
snd_hrtimer12540  1 
snd_seq_midi   12744  0 
snd_seq_midi_event 13124  1 snd_seq_midi
snd_seq51555  3 snd_seq_midi_event,snd_seq_midi
cfg80211  350041  0 
rfkill 18387  1 cfg80211
binfmt_misc12733  1 
nfsd  236959  2 
auth_rpcgss45765  1 nfsd
oid_registry   12387  1 auth_rpcgss
nfs_acl12463  1 nfsd
nfs   168022  0 
lockd  73443  2 nfs,nfsd
fscache44782  1 nfs
sunrpc211341  6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
joydev 16847  0 
snd_hda_codec_realtek62023  1 
snd_ice171260506  0 
snd_cs8427 13144  1 snd_ice1712
x86_pkg_temp_thermal12839  0 
snd_hda_codec_hdmi 44414  1 
snd_hda_codec_generic58021  1 snd_hda_codec_realtek
snd_ice17xx_ak4xxx 12644  1 snd_ice1712
intel_powerclamp   17006  0 
snd_ak4xxx_adda17293  2 snd_ice1712,snd_ice17xx_ak4xxx
intel_rapl 17172  0 
snd_i2c12898  2 snd_ice1712,snd_cs8427
snd_hda_intel  25959  0 
kvm_intel 133491  0 
snd_mpu401_uart13299  1 snd_ice1712
snd_rawmidi22284  2 snd_mpu401_uart,snd_seq_midi
snd_hda_controller 26262  1 snd_hda_intel
snd_seq_device 12980  3 snd_seq,snd_rawmidi,snd_seq_midi
kvm   330286  1 kvm_intel
snd_hda_codec  93768  5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
snd_ac97_codec 96151  1 snd_ice1712
crc32_pclmul   12809  0 
aesni_intel17934  0 
snd_hwdep  12906  1 snd_hda_codec
aes_i586   16647  1 aesni_intel
snd_pcm_oss44124  0 
ac97_bus   12462  1 snd_ac97_codec
xts12583  1 aesni_intel
lrw12645  1 aesni_intel
mxm_wmi12467  0 
evdev  17136  2 
iTCO_wdt   12727  0 
iTCO_vendor_support12585  1 iTCO_wdt
gf128mul   12834  2 lrw,xts
snd_mixer_oss  21822  1 snd_pcm_oss
ablk_helper12508  1 aesni_intel
cryptd 14124  1 ablk_helper
snd_pcm78128  7 snd_ice1712,snd_pcm_oss,snd_ac97_codec,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
snd_timer  22010  3 snd_hrtimer,snd_pcm,snd_seq
snd55101  20 

Bug#797881: QNAP TS-219P II: qcontrol no longer works after upgrading to linux-image-4.1.0-0.bpo.1-kirkwood

[Ian Campbell]

On Thu, 2015-09-03 at 12:20 +0200, Robert Schlabbach wrote:
> Package: linux-image-4.1.0-0.bpo.1-kirkwood
> Version: 4.1.3-1~bpo8+1
>  
> After installing this Linux kernel on my QNAP TS-219P II, qcontrol no
> longer works:
>  
> 1. The status LED remains in red/green blink mode (as set by the boot
> loader). It should be set to solid green when the kernel is loaded.
> 2. The buzzer does not buzz. It should buzz when the kernel is loaded
> and when the kernel is shutting down.
>  
> Removing and reinstalling the qcontrol package did not help.

I suspect this is due to the device path for the input node changing
from /dev/input/by-path/platform-gpio_keys-event to /dev/input/by
-path/platform-gpio-keys-event. With the version of qcontrol in Jessie
it won't even start if it can't find the device, even though it can do
many of its core things without it (the node is for button input only).

This is fixed by qcontrol 0.5.4-4 in testing (both looking for old and
new names, as well as not treating failure to find either as a
catastrophe), but for Jessie you can just edit the path in
/etc/qcontrol.conf.

If that works for you then it might be worth uploading an updated
qcontrol to backports.

Thanks,
Ian.

Bug#800424: libdevel-cover-perl: FTBFS on i386 (Linux + Hurd, not kFreeBSD)

[Axel Beckert]

Control: tag -1 + upstream
Control: forwarded -1 https://github.com/pjcj/Devel--Cover/issues/143 
Control: retitle -1 libdevel-cover-perl: FTBFS occasionally due to 
non-deterministically failing tests (t/e2e/aeval_merge.t, t/e2e/eval_merge.t)

Hi,

Axel Beckert wrote:
> libdevel-cover-perl FTBFS on i386 and hurd-i386 (but not kfreebsd-i386)
> due to a test suite failure:
> https://buildd.debian.org/status/package.php?p=libdevel-cover-perl

This is a non-deterministic build failure. I wasn't able to reproduce
it on i386 out-of-the-box. Then I ran dh_auto_test in a loop until I
was able to reproduce the failure:

  while nice -n2 dh_auto_test; do sleep 1; done

It ran for 8 iterations and several minutes before it failed. I've
forwarded the issue to upstream publically now.

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

Bug#800701: pandoc: suppresses ~code~ when converting Org-mode to HTML(5)

[Karl Voit]

Hi!

John MacFarlane (j...@berkeley.edu) wrote:

> This bug was fixed in pandoc over a year ago:
> https://github.com/jgm/pandoc/issues/1345

Great to know. Thought so, that it is not hard to fix.

However, this being a Debian bug report and I got the most current
Pandoc package for Debian stable: Excuse me my naïve question: is it
supposed that this fix is going to hit Debian stable as an update
anytime soon?

And I do have a second question since I am writing very simple
parser on my own: what's the default policy of Pandoc when it comes
to unknown syntax? When can content be missing after conversion of
unknown syntax elements?

Thank you very much for your help!

> +++ Karl Voit [Oct 02 15 18:35 ]:
> >Package: pandoc
> >Version: 1.12.4.2~dfsg-1+b14
> >Severity: important
> >
> >Dear Maintainer,
> >
> >I ran unit-tests for (py)pandoc on my new Debian machine. In contrast to
> >oldstable, pandoc now deletes text when converting from Org-mode to HTML or
> >HTML5.
> >
> >  * What exactly did you do (or not do) that was effective (or
> >ineffective)?
> >
> >I am using this short example file:
> >
> >| vk@sherri ~2d % cat source.org
> >| foo ~bar~ *baz*
> >| vk@sherri ~2d %
> >
> >  * What was the outcome of this action?
> >
> >Converting via pandoc (or pypandoc) deletes the "bar" text from the content:
> >
> >| vk@sherri ~2d % pandoc -f org -t html source.org
> >| foo  baz
> >| vk@sherri ~2d % pandoc -f org -t html5 source.org
> >| foo  baz
> >| vk@sherri ~2d %
> >
> >  * What outcome did you expect instead?
> >
> >With a prior version of Debian oldstable, I got a different result (from my
> >memory, code-tags were used definitely according to my unit tests):
> >
> >| foo bar baz
> >
> >
> >
> >-- System Information:
> >Debian Release: 8.2
> > APT prefers stable
> > APT policy: (500, 'stable')
> >Architecture: amd64 (x86_64)
> >Foreign Architectures: i386
> >
> >Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> >Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: 
> >LC_ALL set to en_US.utf8)
> >Shell: /bin/sh linked to /bin/dash
> >Init: systemd (via /run/systemd/system)
> >
> >Versions of packages pandoc depends on:
> >ii  libc62.19-18+deb8u1
> >ii  libffi6  3.1-2+b2
> >ii  libgmp10 2:6.0.0+dfsg-6
> >ii  libicu52 52.1-8+deb8u3
> >ii  liblua5.1-0  5.1.5-7.1
> >ii  libpcre3 2:8.35-3.3
> >ii  libyaml-0-2  0.1.6-3
> >ii  pandoc-data  1.12.4.2~dfsg-1
> >ii  zlib1g   1:1.2.8.dfsg-2+b1
> >
> >pandoc recommends no packages.
> >
> >Versions of packages pandoc suggests:
> >pn  etoolbox   
> >pn  pandoc-citeproc
> >ii  texlive-latex-recommended  2014.20141024-2
> >pn  texlive-luatex 
> >ii  texlive-xetex  2014.20141024-2
> >
> >-- no debconf information
> >
> >-- 
> >Karl Voit
> >
> 

-- 
Karl Voit

Bug#800842: linux-image-4.2.0-1-amd64: Kernel Oops when irqbalance is enabled

[Peter Marschall]

Package: src:linux
Version: 4.2.1-2
Severity: important

Hi,

when irqblanace (installed version 1.0.6-3) is enabled,
linux-image-4.2.0-1-amd64 oopses ~15 seconds after boot)

This Oops is new with linux-image-4.2.0-1-amd64:
it did not happen with previous kernel versions.

It happens on both (independent) installations on this machine.

Disabling irqbalance seems to fix the issue.
Since rebooting with irqbalance disenabled, no Oops occurred.

The attached file give the dmesg information of the oops'ed kernel.

Thanks for maintaining the Linux kenel in Debian
Peter

PS: I reported the bug against linux, because I think a kernel should
never oops. Feeld free to re-assign as you think appropriate.


-- Package-specific info:
** Version:
Linux version 4.2.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.3 
(Debian 4.9.3-4) ) #1 SMP Debian 4.2.1-2 (2015-09-27)

** Command line:
BOOT_IMAGE=/vmlinuz-4.2.0-1-amd64 root=LABEL=root1 ro noapic quiet 3

** Not tainted

** Kernel log:
 see attached dmesg log

** Model information
sys_vendor: FUJITSU
product_name: ESPRIMO P920
product_version: 
chassis_vendor: FUJITSU
chassis_version: C$WX01
bios_vendor: FUJITSU // American Megatrends Inc.
bios_version: V4.6.5.4 R1.10.0 for D3222-A1x
board_vendor: FUJITSU
board_name: D3222-A1
board_version: S26361-D3222-A1

** Loaded modules:
ecb
rfcomm
ebtable_filter
ebtables
binfmt_misc
cpufreq_conservative
cpufreq_powersave
cpufreq_userspace
cpufreq_stats
bnep
nfsd
auth_rpcgss
oid_registry
nfs_acl
nfs
lockd
grace
fscache
sunrpc
nf_conntrack_ipv4
nf_defrag_ipv4
iptable_filter
ip_tables
xt_limit
nf_log_ipv6
nf_log_common
xt_LOG
xt_tcpudp
nf_conntrack_ipv6
nf_defrag_ipv6
xt_conntrack
nf_conntrack
ip6table_filter
ip6_tables
x_tables
ftdi_sio
pl2303
usbserial
uas
uvcvideo
videobuf2_vmalloc
videobuf2_memops
videobuf2_core
usb_storage
snd_usb_audio
v4l2_common
snd_usbmidi_lib
videodev
snd_rawmidi
snd_seq_device
media
btusb
btrtl
btbcm
btintel
bluetooth
rfkill
tpm_infineon
deflate
ctr
twofish_generic
twofish_avx_x86_64
twofish_x86_64_3way
twofish_x86_64
twofish_common
camellia_generic
camellia_aesni_avx2
camellia_aesni_avx_x86_64
camellia_x86_64
serpent_avx2
serpent_avx_x86_64
serpent_sse2_x86_64
xts
serpent_generic
blowfish_generic
blowfish_x86_64
blowfish_common
cast5_avx_x86_64
cast5_generic
cast_common
des_generic
cbc
cmac
xcbc
rmd160
sha512_ssse3
sha512_generic
crypto_null
af_key
xfrm_algo
x86_pkg_temp_thermal
intel_powerclamp
intel_rapl
iosf_mbi
kvm_intel
kvm
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
iTCO_wdt
iTCO_vendor_support
ppdev
snd_hda_codec_hdmi
sha256_ssse3
sha256_generic
hmac
drbg
ansi_cprng
aesni_intel
aes_x86_64
lrw
gf128mul
glue_helper
ablk_helper
cryptd
evdev
psmouse
snd_hda_codec_realtek
snd_hda_codec_generic
serio_raw
pcspkr
i2c_i801
sg
i915
lpc_ich
snd_hda_intel
mfd_core
snd_hda_codec
shpchp
snd_hda_core
snd_hwdep
drm_kms_helper
snd_pcm
drm
snd_timer
mei_me
snd
mei
soundcore
i2c_algo_bit
fujitsu_laptop
parport_pc
parport
8250_fintek
battery
tpm_tis
processor
video
tpm
button
hid_generic
usbhid
hid
sch5636
sch56xx_common
coretemp
loop
ecryptfs
autofs4
ext4
crc16
mbcache
jbd2
sr_mod
cdrom
sd_mod
ahci
libahci
crc32c_intel
libata
xhci_pci
ehci_pci
xhci_hcd
ehci_hcd
scsi_mod
e1000e
usbcore
ptp
pps_core
usb_common
fan
thermal
thermal_sys

** Network interface configuration:

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

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

Versions of packages linux-image-4.2.0-1-amd64 depends on:
ii  debconf [debconf-2.0]   1.5.57
ii  initramfs-tools [linux-initramfs-tool]  0.120
ii  kmod21-1
ii  linux-base  4.0

Versions of packages linux-image-4.2.0-1-amd64 recommends:
ii  firmware-linux-free  3.4
ii  irqbalance   1.0.6-3

Versions of packages linux-image-4.2.0-1-amd64 suggests:
ii  debian-kernel-handbook  1.0.16
ii  grub-pc 2.02~beta2-28
ii  linux-doc-4.2   4.2.1-2

Versions of packages linux-image-4.2.0-1-amd64 is related to:
pn  firmware-atheros
pn  firmware-bnx2   
pn  firmware-bnx2x  
pn  firmware-brcm80211  
pn  firmware-intelwimax 
pn  firmware-ipw2x00
pn  firmware-ivtv   
pn  firmware-iwlwifi
pn  firmware-libertas   
pn  firmware-linux  
ii  firmware-linux-nonfree  0.44
pn  firmware-myricom
pn  firmware-netxen 
pn  firmware-qlogic 
ii  firmware-ralink 0.44
ii  firmware-realtek0.44
pn  xen-hypervisor  

-- debconf information:
  linux-image-4.2.0-1-amd64/postinst/depmod-error-initrd-4.2.0-1-amd64: false
  

Bug#800811: fpc: FTBFS on i386,...

[Edmund Grimley Evans]

On armhf the solution may be to disable optimisations on the first
build, when running 2.6.4. See

http://lists.freepascal.org/pipermail/fpc-devel/2015-October/036017.html
http://lists.freepascal.org/pipermail/fpc-pascal/2015-June/044565.html

and the rest of those threads.

Bug#800811: fpc: FTBFS on i386,...

[Paul Gevers]

Hi Edmund,

On 03-10-15 23:04, Edmund Grimley Evans wrote:
> The new upload to experimental hasn't fared too well on the buildds:

We noticed.

> I was able to make it build on i386 with this patch, though I wouldn't
> be surprised if there's a better, more general solution:

Thanks a lot for your patch. I was already trying to reproduce, but it
seems there is no problem on amd64. I will let this sink in and see how
to implement that more generic solution. Probably something with a call
to dpkg-architecture.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#800693: Patch

[Axel Beckert]

Hi Salvo,

Salvo Tomaselli wrote:
> This is the patch to copy in
> debian/patches and add to debian/patches/series.

For some reason the DEP-3 headers are wrongly indented. But it's
correct in the package on mentors. Probably an editor issue while
pasting.

The patch works fine for me, too. So thanks again.

David: Will upload it as posted on mentors to DELAYED/2.

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

Bug#800874: kscreen: plasmoid missing from Debian package

[Ilia Kats]

Package: kscreen
Version: 4:5.4.1-1
Severity: important

Dear Maintainer,

the kscreen plasmoid is missing from the Debian package. I believe it would be 
sufficient to add /usr/share/plasma/* and /usr/share/kservices5/* to 
kscreen.install, but I have not yet tested this.

Kind regards, Ilia Kats

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

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

Versions of packages kscreen depends on:
ii  kde-cli-tools  4:5.4.1-1
ii  libc6  2.19-22
ii  libkf5configcore5  5.14.0-1
ii  libkf5configwidgets5   5.14.0-1
ii  libkf5coreaddons5  5.14.0-1
ii  libkf5dbusaddons5  5.14.0-1
ii  libkf5globalaccel5 5.14.0-1
ii  libkf5i18n55.14.0-1
ii  libkf5screen6  4:5.4.1-1
ii  libkf5widgetsaddons5   5.14.0-1
ii  libkf5xmlgui5  5.14.0-1
ii  libqt5core5a   5.4.2+dfsg-9
ii  libqt5dbus55.4.2+dfsg-9
ii  libqt5gui5 5.4.2+dfsg-9
ii  libqt5qml5 5.4.2-6
ii  libqt5quick5   5.4.2-6
ii  libqt5widgets5 5.4.2+dfsg-9
ii  libstdc++6 5.2.1-18
ii  plasma-framework   5.14.0-1
ii  qml-module-qtgraphicaleffects  5.4.2-2+b1

kscreen recommends no packages.

kscreen suggests no packages.

-- no debconf information

Bug#800327: Bug#799948: Permission issue with GDM and NVidia

[Luca Boccassi]

On Sep 30, 2015 17:26, "Andreas Beckmann"  wrote:
>
> On 2015-09-29 10:31, Luca Boccassi wrote:
> > Another solution would be having the DM packages themselves add their
users
> > to the video group on install as well, but I'd be wary of adding
> > workarounds in other packages, especially when it involves extending
> > privileges, and I suspect the respective mainteiners feel the same way.
> >
> > Andreas, Vincent, what are your thoughts on this?
>
> I don't have time to dig into this right now. IIRC some consolekit magic
> puts the local X user into to the video group, so GL works for the
> logged in user... but not for most *dm.
>
> Did someone check whether this behavior depends on systemd vs. sysvinit?
>
> Do the device permissions differ dependening on the way the nvidia
> module was loaded?

Ran a few tests, with glx-alternatives 0.6 and 340.93-2, and without gdm in
video group:

old modprobe, sysvinit: gdm works!
old modprobe, systemd: gdm oops

new modprobe, systemd: gdm oops
new modprobe, sysvinit: gdm oops

The first result is interesting I think, I'd expected it to work.

> We should get the maintainers of the affected *dm packages involved in
> this discussion.

There's a bug open against gdm, cc'ed.

Kind regards,
Luca Boccassi

Bug#800833: brasero: Brasero do not detect libdvdcss2 even when installed

[Jean Baptiste Favre]

Package: brasero
Version: 3.12.1-1
Severity: important
Tags: patch

Dear Maintainer,

When trying to perform a DVD copy, brasero complained libdvdcss2 wasn't found,
though installed via libdvd-pkg.

Problem is that Brasero looks for "dvdcss_interface_2" symbol which has been
removed from libdvdcss2 last versions.

Attached patch aims to remove dvdcss_interface_2 symbol check from Brasero.



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

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

Versions of packages brasero depends on:
ii  brasero-common  3.12.1-1
ii  gnome-icon-theme3.12.0-1
ii  gstreamer1.0-plugins-base   1.6.0-1
ii  gvfs1.26.0-2
ii  libatk1.0-0 2.18.0-1
ii  libbrasero-media3-1 3.12.1-1
ii  libc6   2.19-22
ii  libcairo-gobject2   1.14.2-2
ii  libcairo2   1.14.2-2
ii  libgdk-pixbuf2.0-0  2.32.0-1
ii  libglib2.0-02.46.0-2
ii  libgstreamer-plugins-base1.0-0  1.6.0-1
ii  libgstreamer1.0-0   1.6.0-1
ii  libgtk-3-0  3.18.0-3
ii  libice6 2:1.0.9-1+b1
ii  libnautilus-extension1a 3.14.2-1
ii  libpango-1.0-0  1.38.0-3
ii  libpangocairo-1.0-0 1.38.0-3
ii  libsm6  2:1.2.2-1+b1
ii  libtotem-plparser18 3.10.5-1
ii  libtracker-sparql-1.0-0 1.6.0-1
ii  libxml2 2.9.2+zdfsg1-4

Versions of packages brasero recommends:
ii  brasero-cdrkit  3.12.1-1
ii  yelp3.16.1-1

Versions of packages brasero suggests:
ii  libdvd-pkg [libdvdcss2]  1.3.99-1-1
ii  libdvdcss2   1.3.99-1~local
ii  tracker  1.6.0-1
ii  vcdimager0.7.24+dfsg-0.2

-- no debconf information
--- a/plugins/dvdcss/burn-dvdcss.c
+++ b/plugins/dvdcss/burn-dvdcss.c
@@ -95,9 +95,6 @@ brasero_dvdcss_library_init (BraseroPlug
 	if (!module)
 		goto error_doesnt_exist;
 
-	if (!g_module_symbol (module, "dvdcss_interface_2", ))
-		goto error_version;
-
 	if (!g_module_symbol (module, "dvdcss_open", ))
 		goto error_version;
 	dvdcss_open = address;

Bug#781607: [Pkg-freeipa-devel] Bug#781607: Bug#781607: Bug#781607: FreeIPA 4.2

[Timo Aaltonen]

On 04.10.2015 09:12, Harald Dunkel wrote:
> Hi freeipa maintainers and everybody involved,
> 
> I just found the new version 4.1.4 in the repository. This
> is amazing. Can't wait to try it out.

Yes, it wasn't too hard to finish after dogtag 10.2.6.

For 4.2 unstable now has SSSD 1.13.1, and I'm thinking of disabling
DNSSEC again but the patches for it need serious rework. Packaging BIND
9.10.x would probably need some collaboration, and preferably a shared
git-repo as a first step. Pinged Michael Gilbert about this some time
ago. Lamont, do you have any concerns about this?

4.3 will likely have "replica promotion" feature added, which will as a
by-product allow us to replicate servers with GSSAPI. And the new
prereq's python-jwcrypto and custodia are already in NEW.


-- 
t

Bug#784070: is it maybe possible to settle dislikings and fix this bug?

[Paul Muster]

Dear Michael,

thanks for clarifying the situation.

> serverfault solution isn't exactly wrong, it is incomplete, it
> does not cover a situation when you have slow-to-appear devices.
> This solution, however, fixes the problem in this bugreport,
> a problem which I introduced when I tried to address the problem
> with slow-to-appear devices.  Ofcourse it is better to be able
> to boot from a degraded raid than to be able to boot from slow
> devices, esp. since the latter had a workaround.  So in this
> sense, serverfault solution will fix _this_ bug.

so, couldn't you patch the package to fix the problem for all people
that do not have "slow-to-appear devices"?


> But I also dislike doing work which is being thrown away by others,
> since this is a pure waste of time/energy, and time is a very scarse
> resource.  I don't want to do any work if I know this work will be
> thrown away, and here, debian-installer people did throw my work
> a) without a good reason and b) without actual rights for that.

Of course what you describe is extremely disappointing for you. Since I
don't know what exactly happened: There should be a decision committee
which listens to both sides and decides _for Debian_.

> So I stopped maintaining all software which is related to debian-installer,
> because now I know it is just a waste of time.  As simple as that, and
> there's nothing like dislike of someone in there, there's nothing
> personal.

It's not obvious to me why a bug in mdadm can't be fixed because there
is a conflict with the d-i maintainers. Why can d-i maintainers decide
about mdadm?

> In short, I don't maintain mdadm anymore, so there's no reason to
> ask me about it.

That would be very sad because it's a really important package.


Thanks & Greetings,

Paul

Bug#800837: radicale: please provide a backport for radicale

[Félix Sipma]

Source: radicale
Version: please provide a backport for radicale
Severity: wishlist

It would be great to have a backport of radicale available, so that
users using stable do not have to enable testing to install radicale
1.0-1.

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

Kernel: Linux 4.1.0-2-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
Init: systemd (via /run/systemd/system)


signature.asc
Description: PGP signature

Bug#786611: Possible fix

[Ritesh Raj Sarraf]

On Sat, 2015-10-03 at 16:35 -0400, Philippe Grégoire wrote:
> 
> I have been genuinely interested in adopting a package, for a while.
> 
> Quite frankly, I only played with iscsitarget for a couple of minutes
> as 
> I am planning to replace my current NAS setup. Considering the
> integration of IPSec in the mix, I ruled out iSCSI as it couldn't be
> done meeting my requirements.
> 
>  From my benchmarks, however, IET has 25% more throughput than LIO
> and,
> although there's probably some deficiencies regarding complex setups
> (ACLs, for one), I am not convinced it should be ruled out by users.
> 

Being an out-of-tree kernel module has its challenges. For one, it
needs to catch-up with every kernel release. But more than that, it is
the integration and testing that gets missed. Any module that is in-
kernel gets to enjoy the wider testing from the kernel community.

>  From the upstream's page, it seems there has been no activity for a
> little more than a year. Are you in touch with them and, if so, do
> they
> have plans for the project?
> 

Not recently, no. Earlier, I was in contact with Ross and Arne, but
that's all.

> What kind of help do you need?

Bug reports, testing and packaging. If you are interested, and you have
no Debian upload rights, I can be your sponsor for this package. But
other than that, not much. 

I tend to only package/maintain things that I use, and iscsitarget has
moved away from that list. But I will sponsor it if you are willing to
maintain.

-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



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

Bug#798924: /usr/lib/x86_64-linux-gnu/jni/libatk-wrapper.so.6.0.0: SIGSEGV on Netbeans startup

[Samuel Thibault]

Mithat Konar, le Sat 03 Oct 2015 16:20:19 -0500, a écrit :
> When I use Samuel's fix,

Which fix? Commenting the line in /etc?  It's not a fix, it's a
workaround, which just completely disables libatk-wrapper-java.  Any bug
in that situation can thus not be due to it.

Samuel

Bug#800839: virtualbox-ext-pack: [INTL:pt] Portuguese translation for debconf messages

[Américo Monteiro]

Package: virtualbox-ext-pack
version: 5.0.2-3
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for virtualbox-ext-pack'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


virtualbox-ext-pack_5.0.2-3_pt.po.gz
Description: GNU Zip compressed data

Bug#666106: kfreebsd-i386: Exceptions with tracebacks in task rendezvous cause STORAGE_ERROR

[Nicolas Boulenguez]

Package: gnat-4.9
Followup-For: Bug #666106
Control: reassign -1 gnat-5 5.2.1-18

The message is "s-intman.adb:139 explicit raise" again.

Bug#795071: Acknowledgement (pulseaudio: Could not play a dvd over tcp protocol)

[Sébastien Dailly]

Le 10/08/2015 12:13, Chimrod a écrit :
> Package: pulseaudio
> Version: 6.0-5
> Severity: normal
>
> Dear Maintainer,
>
> This is a very strange problem, related to pulseaudio : I can't get
the sound
> when I play a dvd, and only in this situation, everything else works.
>
> I'm using pulseaudio over the network, with a sound server, with
module-native-
> protocol-tcp, and as soon as I start to play the movie, I've got
thoses traces
> in the syslog (without any sound of course) :
>

Hello,

I've update pulseaudio to 7.0-1 and everything works now.

You can close the bug.

Regards,

Sébastien

Bug#786980: heimdahl: german package translation misleading

[Holger Levsen]

Hi,

On Sonntag, 4. Oktober 2015, Andrei POPESCU wrote:
> > the package description reads
> > 
> >  Heimdal is a free implementation of Kerberos 5 that aims to be
> >  compatible with MIT Kerberos.
> > 
> > which is translated to German as
> > 
> >  Heimdal ist eine freie Implementierung von Kerberos 5, die mit MIT
> >  Kerberos kompatibel sein soll.
> > 
> > which means something else, roughly "that it should be compatible" (but
> > probably is not).
> > 
> > Better:
> >  Heimdal ist eine freie Implementierung von Kerberos 5, die
> >  Kompatibilität mit MIT Kerberos anstrebt.
> 
> Translations of the package description are not under control of the
> package maintainer, closing.

sigh. 

so there is no way to track bugs in translated package descriptions? That 
would be really sad.
 
> Andrei (just one of the people looking after bugs reported against
> unknown packages)

thanks for caring!


cheers,
Holger




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

Bug#784319: [Pkg-nagios-devel] Bug#784319: Segfault when running check_dhcp

[Jan Wagner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

tags 784319 + pending
thanks

Am 05.05.15 um 12:21 schrieb Andreas Heinlein:
> Since upgrading to jessie, I get this in my syslog: kernel:
> check_dhcp[20879]: segfault at 21 ip 2b508d08f21e sp 
> 7ffc9eee20b0 error 4 in libc-2.19.so[2b508cfc1000+19f000]
> 
> The problem seems to be already tracked and fixed here: 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198318

this was fixed by upstream in a more complete and reliable way:
https://github.com/monitoring-plugins/monitoring-plugins/commit/466cb79e
5224327c29fc6b84a1cec99c2b190c5a

I commited this patch into the VCS and it should be included into the
next upload.

Cheers, Jan.
- -- 
Never write mail to , you have been warned!
- -BEGIN GEEK CODE BLOCK-
Version: 3.12
GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V-
PS PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y
- --END GEEK CODE BLOCK--
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)

iQIcBAEBCgAGBQJWEQomAAoJEAxwVXtaBlE+240QAJ/y8sPVPB3MM8Wl6wpS5lwA
BdQ4RIdUoOHn4pxAt+YDAPujPpp/GWXaCb8HbRthW9DinQ9AIPjVSA/0fNyDbFT4
081MX14PJsx0SUBqhdsNS+wpLsFfw3t2ptIV6ms+V5vmnFbADEAp+ZJdneDzMBny
VP58xvZS0wNYOLUtjFMc7ywlrhQ6EFPp2YoYrqZm0IV5V0/DeggrZCxptxgnOkq7
vPQHbGSOLo/BzuHXbeADU4zY0xghiaOKwDXcbANOtILlztl8ugve1Rcr+64R7bpI
Cb5zMv9nUFK+y8jWODfwUw3ex5tqkQaVB2jN2durrfjMrt33E7U3ZagJkccCh4VM
L4E8eaQ0fuv+f7waq7c8jMlgcJNE6YdqWo8sW0Oajx+/TOIYM2d93zoverZIKzmU
jwbQjyz3m8mixHyMcLsAz5I3LjWN1Wo6VGu6hgrtcuamJwxmqLjTIN5Ag+Kfg3Za
LSn47gQkUQ3lFIPCVg9xkjTSNe39v6ZKR5KfTP73JRG5Q556ED8hsRWrQl5/d8nI
IJ9UYuMd5eSjh58nt2IpQnqBNJdpT+44Dwd7D+mesvISLDcpOJZW+bezdMSlREtY
gdDBmOoVbzluPcxRM1HtrXbLQVP9l6tIAlD+7HnX+J1eQ0R0Gu1Ha5jbtje0jEwi
gCNeuKWFuruHFImPV6Qf
=Cb7c
-END PGP SIGNATURE-

Bug#800845: autopkgtest: Add support for nested VMs

[Christian Seiler]

Package: autopkgtest
Version: 3.17.2
Severity: wishlist
Tags: patch

Hello Martin,

as per our discussion on the autopkgtest mailing list [1], I'd like to
be able to have autopkgtest support nested VMs for testing of network
clients in the kernel such as NFS, CIFS, iSCSI, NBD, etc.

The logic would be to

 - have the test environment run a simple server that the client may
   connect to
 - have a copy of the qcow2 base image in the test environment
 - create a QEMU/KVM VM in the test environment that then tests the
   client (this can again be done with adt-run inside the test env)

I've attached two patches that implement the necessary changes to
autopkgtest. They are quire minimal in fact:

 1. Have adt-virt-qemu add an additional drive to the VM that
maps (read-only) to the qcow2 base image (but without QEMU
interpreting the image, just passing it through via format=raw).

This allows the drive to be used as a base image, e.g.
qemu-img create -f qcow2 -b /dev/vdb overlay.img
(Running KVM on top of something like that works, btw., in case
you were wondering - you can easily try that by creating a loop
device, i.e. losetup --show -f base.img and then doing
adt-run ... --- adt-virt-qemu /dev/loopX.)

 2. Have adt-virt-qemu provide an environment variable to the tests
so that they may make use of it. (ADT_QCOW2_BASEIMAGE)

 3. Have adt-virt-qemu export the capability provides-qcow2-baseimage.

 4. Add new restriction needs-qcow2-baseimage that is checked against
that capability. (The base image logic is done unconditionally by
adt-virt-qemu, regardless of the restriction. In principle this
would allow people to just do vmdebootstrap inside the VM if the
base image were not to be exported.)

 5. If in KVM mode, add -cpu host option to the emulator command, since
that is required (but not sufficient) for nested KVM to work.

Note that nested KVM will also require a module option to be set.
(nested=1 for either the kvm_intel or kvm_amd module.) Setting
-cpu host has no negative side effects even if nested=0 is set on
the host - then the kvm_* modules will not load in the VM and KVM
will simply be not available - same as without -cpu host.

On the other hand, nested KVM is nice-to-have, but not required for
a nested VM - the VM inside could be a non-accelerated QEMU VM.

Once could in principle also add support for nested KVM to adt-virt-lxc
by simply allowing the administrator to specify an additional qcow2
base image on the command line. That could be done in an additional
step.

I've updated the documentation to reflect the base image changes.

It would be great if that could be added to autopkgtest.

Thanks!

Regards,
Christian
From d091f958e1a61cbf4d3296c4267d011ba3c6dbd4 Mon Sep 17 00:00:00 2001
From: Christian Seiler 
Date: Sun, 4 Oct 2015 12:25:39 +0200
Subject: [PATCH 1/2] Add 'needs-qcow2-baseimage' restriction

Add restrictions that allows tests to require a qcow2 base image be
present inside the test environment, so that e.g. nested VM tests are
possible.
---
 doc/README.package-tests.rst | 20 
 lib/testdesc.py  |  9 -
 virt-subproc/adt-virt-qemu   | 25 ++---
 virt-subproc/adt-virt-qemu.1 | 10 ++
 4 files changed, 60 insertions(+), 4 deletions(-)

diff --git a/doc/README.package-tests.rst b/doc/README.package-tests.rst
index e1127cb..5872617 100644
--- a/doc/README.package-tests.rst
+++ b/doc/README.package-tests.rst
@@ -202,6 +202,26 @@ needs-recommends
 Enable installation of recommended packages in apt for the test
 dependencies. This does not affect build dependencies.
 
+needs-qcow2-baseimage
+The test needs to have a read-only qcow2 base image available so it
+may create an overlay and start a qemu/KVM virtual machine inside
+the test environment.
+
+This is useful for testing network client packages that require
+kernel support (NFS, CIFS, iSCSI, NBD, etc.): the external testing
+environment sets up a minimalistic server environment and then
+starts a virtual machine that tests the client.
+
+While currently only adt-virt-qemu supports this, this options is
+independent of the isolation level. If the setup of the server also
+needs a specific isolation level, that should be specified
+additionally.
+
+The environment variable ADT_QCOW2_BASEIMAGE will be set to the
+absolute path of the qcow2 base image. If the test environment
+supports it, this variable will be available irrespective of
+whether this restriction was added to the test or not.
+
 Defined features
 
 
diff --git a/lib/testdesc.py b/lib/testdesc.py
index 260b2fa..33fdb7f 100644
--- a/lib/testdesc.py
+++ b/lib/testdesc.py
@@ -42,7 +42,8 @@ import adtlog
 
 known_restrictions = ['rw-build-tree', 'breaks-testbed', 'needs-root',
   'build-needed', 

Bug#796668: marked as done (transition: log4cplus)

[Emilio Pozuelo Monfort]

Control: reopen -1

This doesn't close the transition bug.

Cheers,
Emilio

Bug#800846: error message in preinst doesn't match test, checks for kernel 3.2 but tells the user it needs 2.6.32

[peter green]

Package: libc6
Version: 2.21-0experimental1

I had an expermimental chroot on a system that happened to be running an 
old kernel. I got an error message about needing a 2.6.32 kernel which 
was strange as I already had a 2.6.32 kernel.


Reading the preinst revealed

# The GNU libc requires a >= 3.2 kernel, found in wheezy
if linux_compare_versions "$kernel_ver" lt 3.2
then
echo WARNING: this version of the GNU libc requires kernel 
version
echo 2.6.32 or later.  Please upgrade your kernel before 
installing

echo glibc.
kernel26_help

exit 1
fi

So it's checking for 3.2 but telling the user they need 2.6.32.

Bug#800836: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash

[Nicolas Le Cam]

Sorry, my intention was to follow-up on bug #799948.
As I don't want to mess up the BTS again, I prefer to leave a note,
instead of playing with the control server, and forward the same info
on the bug #799948.

regards,
Nicolas

Bug#800872: smd-loop just exists with an error code and no explanation when /tmp is full

[Enrico Zini]

Package: syncmaildir
Version: 1.2.6.1-1
Severity: normal

Hello,

thank you for syncmaildir.

Fetching mail Worked Until Yesterday™, and now I get this:

  $ smd-loop -v
  smd-loop: /usr/bin/smd-pull -s default
  $ echo $?
  1

I noticed /tmp was full. After cleaning it up:

  $ smd-loop
  default: smd-client@localhost: TAGS: stats::new-mails(0), del-mails(0), 
bytes-received(0), xdelta-received(214)

I wish there was something like an error message in a case like this.


Thank you,

Enrico


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

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

Versions of packages syncmaildir depends on:
ii  libc6   2.19-22
ii  libglib2.0-02.46.0-2
ii  lua5.1  5.1.5-8
ii  openssh-client  1:6.9p1-2
ii  xdelta  1.1.3-9.1

syncmaildir recommends no packages.

syncmaildir suggests no packages.

-- no debconf information

Bug#770369: Eterm on Jessie, Stretch and Sid does not run shell

[Stamatis Mavrogeorgis]

Exact same problem here.

I did some investigation and I can confirm the following:

* Eterm (0.9.6-1) runs properly on AntiX-15 which is based on Jessie.

* I installed (with dpkg) on Jessie the Eterm deb package that runs
properly on AntiX-15 and Eterm still exhibits the same erratic behaviour
[on Jessie].

* I installed on AntiX-15 the Eterm deb package that behaves erratically on
Jessie, and it runs properly [on AntiX-15].

* I repeated the latter two above steps between AntiX-15 and Stretch
(testing) and AntiX-15 and Sid with identical results as with AntiX-15 and
Jessie: - AntiX-15 runs the Stretch and Sid Eterm packages properly,
whereas Stretch and Sid exhibit erratic behaviour on the Eterm package
brought over from Antix-15.

The above led me to speculate that there is nothing wrong with the Eterm
package per se, instead, the problem seems to lie with Jessie and
subsequent (Stretch, Sid) system implementations.

Bug#800385: tor: systemd .service granting too much capabilities?

[Peter Palfrader]

On Mon, 28 Sep 2015, Laurent Bigonville wrote:

> When looking at the capabilities that are granted by the .service file
> compared to the upstream one (in the contrib directory), I'm wondering
> if it couldn't be reduced.

Maybe.

> -CapabilityBoundingSet=CAP_SETUID CAP_SETGID CAP_NET_BIND_SERVICE
> +CapabilityBoundingSet=CAP_SETUID CAP_SETGID CAP_NET_BIND_SERVICE 
> CAP_DAC_OVERRIDE CAP_CHOWN CAP_FOWNER
> 
> The dac_override one could atleast be dropped if root also had access
> to the /var/log/tor /var/lib/tor directories (giving access to the root
> group?). Not too sure about the other ones.

But root doesn't.  And I think we need chown since we start as root and
then create sockets and give that to the target user.  Do you disagree?

> I'm also wondering about: ReadWriteDirectories=-/var/run, shouldn't this
> be removed and shouldn't /var/run/tor be created by tmpfiles mechanism
> (or the RuntimeDirectory= option) instead of using the install command?

>From reading the manpage I get the impression that this will not allow
us to create the directory in a way that the right user ends up owning
it.  Any ideas?

> Also, shouldn't "NoNewPrivileges=yes" be added like in the upstream one?

The manpage suggests that it disallows UID changes, but when I tested
it, tor should still transition from root to its target user.  I think
we should set this option.

weasel
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#800836: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash

[Nicolas Le Cam]

Package: nvidia-legacy-340xx-driver
Version: 340.93-1
Severity: normal

Dear Maintainer,

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

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

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

Subject: Re: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash

Package: nvidia-graphics-drivers-legacy-340xx
Version: 340.93-1
Followup-For: Bug #799948

Dear Maintainer,

Same problem here while upgrading from 340.76-6 to 340.93-1.
OTOH glx-diversions wasn't upgraded, but it really seems to be the same
problem.

Adding group video to the Debian-gdm user fixes the problem.

regards,
Nicolas

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

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

-- Package-specific info:
uname -a:
Linux misaki 4.2.0-1-amd64 #1 SMP Debian 4.2.1-2 (2015-09-27) x86_64 GNU/Linux

/proc/version:
Linux version 4.2.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.3 
(Debian 4.9.3-4) ) #1 SMP Debian 4.2.1-2 (2015-09-27)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.93  Wed Aug 19 16:49:15 PDT 
2015
GCC version:  gcc version 4.9.3 (Debian 4.9.3-4) 

lspci 'VGA compatible controller [0300]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G86M [Quadro NVS 
135M] [10de:042b] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:01f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia

dmesg:
[0.00] Console: colour VGA+ 80x25
[0.264448] vgaarb: setting as boot device: PCI::01:00.0
[0.264448] vgaarb: device added: 
PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none
[0.264448] vgaarb: loaded
[0.264448] vgaarb: bridge control possible :01:00.0
[0.489509] Linux agpgart interface v0.103
[1.586071] [Firmware Bug]: Duplicate ACPI video bus devices for the same 
VGA controller, please try module parameter "video.allow_duplicates=1"if the 
current driver doesn't work.
[2.444345] nvidia: module license 'NVIDIA' taints kernel.
[2.472232] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[2.472734] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[2.472746] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.93  Wed Aug 
19 16:49:15 PDT 2015

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Oct  4 09:35 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   44 Oct  4 09:35 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   41 Oct  4 09:35 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   41 Oct  4 09:35 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Oct  4 09:35 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Oct  4 09:35 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   57 Oct  4 09:35 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   57 Oct  4 09:35 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   54 Oct  4 09:35 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 Oct  4 09:35 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   49 Oct  4 09:35 
/etc/alternatives/glx--libnvidia-cfg.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   51 Oct  4 09:35 
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   25 Oct  4 09:35 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Oct  4 09:35 

Bug#182360: 182360 fixed in gnat-5

[Nicolas Boulenguez]

Package: gnat-4.9
Followup-For: Bug #182360
Control: retitle -1 [Fixed in 5.2] GNAT.OS_Lib.Close ignores return value

Adacore has found a way to preserve compatibility *and* allow the user
to raise an exception.
>From s-os_lib.ads:
   procedure Close (FD : File_Descriptor; Status : out Boolean);
   --  Close file referenced by FD. Status is False if the underlying service
   --  failed. Reasons for failure include: disk full, disk quotas exceeded
   --  and invalid file descriptor (the file may have been closed twice).

   procedure Close (FD : File_Descriptor);
   --  Close file referenced by FD. This form is used when the caller wants to
   --  ignore any possible error (see above for error cases).

Bug#784823: Regression - mdadm in jessie will not boot degraded raid1 array

[Paul Muster]

severity 784823 critical
merge 784070 784823
thanks


Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784070 for
new information about bug and package status.


Greetings,

Paul

Bug#800835: firmware-linux-free: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1.bin for module i915

[Olivier Berger]

Package: firmware-linux-free
Version: 3.4
Severity: normal

Hi.

After today's kernel update in testing, I'm getting the following :
W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1.bin for module i915

It doesn't seem to be shipped.

Thanks in advance.

Best regards,

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

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

firmware-linux-free depends on no packages.

firmware-linux-free recommends no packages.

Versions of packages firmware-linux-free suggests:
ii  initramfs-tools  0.120

-- debconf-show failed

Bug#800080: dolphin: servicemenus

[vampiru]

https://git.reviewboard.kde.org/r/125425/

i copied /usr/share/kde4/servicetypes/konqpopupmenuplugin.desktop  to
/usr/share/kservicetypes5/

and context menus in dolphin started working again


On Sat, Sep 26, 2015 at 4:45 PM, andrei  wrote:

> Package: dolphin
> Version: 4:15.08.1-1
> Severity: normal
>
> Dear Maintainer,
>
> context/service menus stopped working in dolphin (Version 15.08.1)
>
> it seems related to this error:
>
> KServiceTypeTrader: serviceType "KonqPopupMenu/Plugin" not found
>
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing-updates
>   APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'),
> (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.1.0-2-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
> Init: systemd (via /run/systemd/system)
>
> Versions of packages dolphin depends on:
> ii  libc6  2.19-22
> ii  libdolphinvcs5 4:15.08.1-1
> ii  libkf5baloo5   5.14.0-1
> ii  libkf5baloowidgets515.08.0-2
> ii  libkf5bookmarks5   5.14.0-1
> ii  libkf5codecs5  5.14.0-1
> ii  libkf5completion5  5.14.0-1
> ii  libkf5configcore5  5.14.0-1
> ii  libkf5configgui5   5.14.0-1
> ii  libkf5configwidgets5   5.14.0-1
> ii  libkf5coreaddons5  5.14.0-1
> ii  libkf5dbusaddons5  5.14.0-1
> ii  libkf5filemetadata35.14.0-1
> ii  libkf5i18n55.14.0-1
> ii  libkf5iconthemes5  5.14.0-1
> ii  libkf5itemviews5   5.14.0-1
> ii  libkf5jobwidgets5  5.14.0-1
> ii  libkf5kcmutils55.14.0-1
> ii  libkf5kiocore5 5.14.0-1
> ii  libkf5kiofilewidgets5  5.14.0-1
> ii  libkf5kiowidgets5  5.14.0-1
> ii  libkf5newstuff55.14.0-1
> ii  libkf5notifications5   5.14.0-1
> ii  libkf5parts5   5.14.0-1
> ii  libkf5service5 5.14.3-1
> ii  libkf5solid5   5.14.0-2
> ii  libkf5textwidgets5 5.14.0-1
> ii  libkf5widgetsaddons5   5.14.0-1
> ii  libkf5windowsystem55.14.0-1
> ii  libkf5xmlgui5  5.14.0-1
> ii  libphonon4qt5-44:4.8.3-2
> ii  libqt5core5a   5.4.2+dfsg-9
> ii  libqt5dbus55.4.2+dfsg-9
> ii  libqt5gui5 5.4.2+dfsg-9
> ii  libqt5widgets5 5.4.2+dfsg-9
> ii  libqt5xml5 5.4.2+dfsg-9
> ii  libstdc++6 5.2.1-17
> ii  phonon4qt5 4:4.8.3-2
>
> Versions of packages dolphin recommends:
> ii  ruby  1:2.1.5.1
>
> Versions of packages dolphin suggests:
> pn  dolphin-plugins  
>
> -- no debconf information
>

Bug#800338: wodim: cant write/read using internal DVD GT34N for spesific DVD disc

[Brianajie Waluyo]

Dear Sir,

I was tried with new disc and with different manufacture/brand, it's work
flawlessly...
Then my opionion was this a disc brand factor, my friend told me that some
brand have more thick than standard and my bad that i got that one.
I used V*rbatim disc for my last, and the bad disc was GTPr* disc.

Thanks.

Best regards,

Brianajie W.
Pada tanggal 30 Sep 2015 13.28, "Thomas Schmitt" 
menulis:

> Hi,
>
> results for now:
>
> - Write type "DAO" (option -sao) is not working. The attempt to write
>   spoils the DVD-R medium for further writing.
>
> - Write type "Incremental" (option -tao) for now failed only because
>   it got to see the spoiled media from the -sao attempts.
>
> Please try -tao with a fresh DVD-R medium.
>
> Do not make further experiments with -sao. It's futile.
>
>
> 
> Details from your report:
>
> > brianajie@heavenbox:~/tmp$ cdrskin -v dev=/dev/sr0 -sao dota1.iso
> > ...
> > cdrskin: FATAL : SCSI error on write(0,16): See MMC specs: Sense Key 3
> "Medium error", ASC 0C ASCQ 80.
>
> That's the same problem that can be seen in the Brasero log.
>
>
> > brianajie@heavenbox:~/tmp$ cdrskin -v dev=/dev/sr0 -tao dota1.iso
> > ...
> > cdrskin: status 3 BURN_DISC_APPENDABLE "There is an incomplete disc in
> the drive"
>
> The DVD-R is not blank any more. The "Incremental" write type
> would be able to write to this medium, but the free space on
> medium is much too small for taking the ISO image:
>
> > cdrskin: FATAL : predicted session size 2294244s does not fit on media
> (3616s)
>
> The burn preparations of the -sao run reserved most of
> the medium capacity but then failed to fill this by data.
> Now this capacity is not usable any more.
>
>
> The other failures happen out of similar reasons:
>
> > cdrskin: SORRY : Write job parameters are unsuitable
> > cdrskin: Reason: SAO: write type SAO works only on blank media,
>
> The write type on DVD-R is named "DAO", not "SAO", but elsewise
> the program is right. This write type cannot work with DVD-R which
> have already written data or a reserved track.
>
>
> > cdrskin: FATAL : predicted session size 487500s does not fit on media
> (3616s)
>
> There are only 7 MB remaining for writing on this DVD-R.
> You's need to make a very small ISO so that it could fit
> in there. (It would not work anyway, as we learn next.)
>
>
> Then you obviously tried a new DVD-R:
>
> The -sao run failed again with Medium Error.
>
> The -tao run saw enough free space.
> But the DVD-R is again in an unhealthy state from the previous
> failed -sao run:
>
> > Starting new track at sector: 487520
> > cdrskin: FATAL : SCSI error on write(487520,16): [5 21 02] Illegal
> request. Invalid address for write.
>
> The drive refused to write at the start of the unused area
> of the DVD-R. Probably because the first session on the medium
> is not completed.
>
>
> > I tried again with the CDRW disc and DVDRW disc to makes sure
> > that not drive failure and both disc works flawlessly.
>
> So the drive is quite selectively incapable of DVD-R "DAO".
>
> It is not clear yet whether it would do "Incremental".
>
>
> Have a nice day :)
>
> Thomas
>
>

Bug#800834: ardour: Freesound search stops work

[Massimo Barbieri]

Package: ardour
Version: 1:4.2~dfsg-5
Severity: minor

Dear Maintainer,
in the add media window the freesound search by tag doesn't show any results.
Thanks for your work!
Max-B



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

Kernel: Linux 4.2-2.dmz.1-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ardour depends on:
ii  ardour-data   1:4.2~dfsg-5
ii  jackd 5
ii  libasound21.0.29-1
ii  libatk1.0-0   2.16.0-2
ii  libatkmm-1.6-1v5  2.22.7-3
pn  libaubio4 
ii  libbluetooth3 5.33-1
ii  libc6 2.19-22
ii  libcairo2 1.14.2-2
ii  libcairomm-1.0-1v51.10.0-1.2
ii  libcurl3-gnutls   7.44.0-2
ii  libcwiid1 0.6.00+svn201-3.2
ii  libfftw3-single3  3.3.4-2
ii  libflac8  1.3.1-4
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6-2
ii  libgcc1   1:5.2.1-17
ii  libgdk-pixbuf2.0-02.32.0-1
ii  libglib2.0-0  2.44.1-1.1
ii  libglibmm-2.4-1v5 2.44.0-3
ii  libgtk2.0-0   2.24.28-1
ii  libgtkmm-2.4-1v5  1:2.24.4-2+b1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-1
ii  liblilv-0-0   0.20.0~dfsg0-1
ii  liblo70.28-5
ii  liblrdf0  0.4.0-5
pn  libltc11  
ii  libogg0   1.3.2-1
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libpangomm-1.4-1v52.36.0-2+b1
ii  librubberband21.8.1-6+b1
ii  libsamplerate00.1.8-8
ii  libserd-0-0   0.20.0~dfsg1-1
ii  libsigc++-2.0-0v5 2.6.1-1
ii  libsndfile1   1.0.25-9.1
ii  libsord-0-0   0.12.2~dfsg0-1
ii  libsratom-0-0 0.4.6~dfsg0-1
ii  libstdc++65.2.1-17
pn  libsuil-0-0   
ii  libtag1v5 1.9.1-2.4
ii  libvamp-hostsdk3v52.6~repack0-2
pn  libvamp-sdk2v5
ii  libx11-6  2:1.6.3-1
ii  libxml2   2.9.2+zdfsg1-4

Versions of packages ardour recommends:
ii  chromium [www-browser]   45.0.2454.101-1
ii  iceweasel [www-browser]  38.2.1esr-1~deb8u1
ii  w3m [www-browser]0.5.3-24

ardour suggests no packages.

-- no debconf information

Bug#800838: Makefile.am doesn't copy sv translation

[Josef Andersson]

Package: boinc*
Version: 7.6.6 and newer

Even though the translation to Swedish for boincmgr is complete since before 
version 7.4 (see boinc on transifex), the sv mo-file is nowhere to be found 
after installing.

Think I found the bug: Under folder locale in the source for the package, see 
file Makefile.am.
The locale dirs lists all langue dirs. For Swedish it's listed as sv_SE which 
was changed in boinc to sv a while ago. (see 
http://lists.ssl.berkeley.edu/pipermail/boinc_loc/2015-March/002435.html )
So Makefile.am wont ever copy it. It should be changed to sv, not sv_SE.

This bug was first reported downstream.

https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1502568

-- 
Vänligen / Best regards
Josef Andersson

Bug#800693: Patch

[Salvo Tomaselli]

tags 800693 patch
thanks

This is the patch to copy in
debian/patches and add to debian/patches/series.


-- 
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
-- Galileo Galilei

http://ltworf.github.io/ltworf/Description: Fix to accomodate changes in python-urwid
 Version 3 of the package is not backwards compatible.
 Origin: other https://bbs.archlinux.org/viewtopic.php?pid=1481016
 Bug-Debian: https://bugs.debian.org/#800693
 Forwarded: no
 Reviewed-By: Salvo 'LtWorf' Tomaselli 
 Last-Update: 2015-10-03

--- wicd-1.7.2.4.orig/curses/wicd-curses.py
+++ wicd-1.7.2.4/curses/wicd-curses.py
@@ -927,9 +927,10 @@ class appGUI():
 if not ui._started:
 return False
 
-input_data = ui.get_input_nonblocking()
+ui.set_input_timeouts(max_wait=0)
+input_data = ui.get_input()
 # Resolve any "alarms" in the waiting
-self.handle_keys(input_data[1])
+self.handle_keys(input_data)
 
 # Update the screen
 canvas = self.frame.render( (self.size),True )

Bug#800338: wodim: cant write/read using internal DVD GT34N for spesific DVD disc

[Thomas Schmitt]

Hi,

> I was tried with new disc and with different manufacture/brand, it's work
> flawlessly...

Good news for the software. Not a bug but a bad relationship
between drive and medium.

Therefore i will now mark this bug as "wontfix" and close it.

Thank you for discussing the problem. If new problems occur
around DVD writing, you are invited to start a new bug report.
If you need any advise, mail to
  pkg-libburnia-de...@lists.alioth.debian.org


Have a nice day :)

Thomas

Bug#800841: [libruby2.1] libruby-2.1.so.2.1.0 is missing a function

[Detlef Reichl]

Package: libruby2.1
Version: 2.1.5-4
Severity: normal


I tried to start a ruby-gtk program (self written, but that has no 
effect) with ruby-gnome2, which is directly compiled from the git 
sources from https://github.com/ruby-gnome2/ruby-gnome2.


It stopped with the error message:

ruby: symbol lookup error:
/home/det/.gem/ruby/2.1.0/extensions/x86_64-linux/2.1.0/glib2-3.0.6/glib2.so:
undefined symbol: ruby_eval_string_from_file

This function is implemented in the ruby sources of the ruby2.1 package 
in the file vm_eval.c, but it does not appear in the shared object file

/usr/lib/x86_64-linux-gnu/libruby-2.1.so.2.1.0

If I compile the original ruby2.1 sources from
http://http.debian.net/debian/pool/main/r/ruby2.1/ruby2.1_2.1.5.orig.tar.xz
without any debian patches, the libruby-2.1.so.2.1.0 contians the 
mentioned function.


I don't know, what the error causes, because I don't know the debian 
build system and how it modifies the original files.


detlef

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.2.0-1-amd64

Debian Release: stretch/sid
  500 testing security.debian.org
  500 testing ftp2.de.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#800561: RFS: classified-ads/0.08-1 - internet messaging system

[Tobias Frost]

Hi Antti,

Am Donnerstag, den 01.10.2015, 01:28 +0300 schrieb Antti Järvinen:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "classified-ads":
> 
>  * Package name: classified-ads
>Version : 0.08-1
>Upstream Author : Antti Järvinen 
>  * URL : http://katiska.org/classified-ads/
>  * License : LGPL-2.1
>Section : net
> 
> It builds those binary packages:
> 
>   classified-ads - Program for displaying classified advertisement
> items
> 
> To access further information about this package, please visit the 
> following URL:
> 
> https://mentors.debian.net/package/classified-ads
> 
> Alternatively, one can download the package with dget using this
> command:
> 
> dget -x http://mentors.debian.net/debian/pool/main/c/classified-ads/c
> lassified-ads_0.08-1.dsc
> 
> More information about classified-ads can be obtained from 
> http://katiska.org/classified-ads/.
> 
> Changes since the last upload:
>   * Qt version change (4->5)
>   * Translation system change from dm files of qt to gnu gettext
>   * Bitmap conversion produces same binary always. Closes: #794395
>   * Networking related bugfixes
> 
> Regards,

> Antti Järvinen
> 

small issues only, please fix those (or convince me that it is ok) and
ping me again.  I'll pull from git.

-> d/changelog 
 * It is convention when you package a new upstream to have that in the
   changelog. As you close upstream bugs, you would write:
  "New upstream release. Closes: #794395"

 * Because: d/changelog is for Debian changes, not to document 
   upstream changes. Let those lines go. 
   
 * But there are changes do the pacakaging which are not documented:
 o removal of B-Ds, adding of README.Source 
  
For practice sharing: When my package is under a repository I try to
have one commit per change topic. This helps to understand which
d/changelog entry correleates to which change.

-> d/README.source
  * the procedure you describe is quite standard, so maybe remove it?
  otherwise:
  * it has some trailing whitespaces.
  * you *SHOULD* *REALLY* sign tags, at least the final build
(add this to your gbp.conf) 
  * you should even consider signing every commit. 
http://mikegerwitz.com/papers/git-horror-story

-> your gbp.conf should be only related to the package, not your
(local) build enviorment. You local settings should go into your local
file. See gbp.conf(5).

(As you are upstream: Please also bump the copyright years when you add
or edit files to their header. Its odd to have new file (c) 2013...
NOTE: This is *NOT* something you need to fix for this upload, just a
suggestion to adapt this best practice in the future)

--
tobi

Bug#800795: quodlibet: does not start

[christophe.pauc_reportbug]

Hello,

 

Downgrading gir1.2-gtk-3.0 to 3.16  Quodlibet is working again.

Bug#799935: emacs24: double desktop entry in .desktop file does not work in cinnamon

[persmule]

This problem also appears on my GNOME environment.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500, 
'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages emacs24 depends on:
ii  emacs24-bin-common 24.5+1-2
ii  gconf-service  3.2.6-3
ii  libacl12.2.52-2
ii  libasound2 1.0.29-1
ii  libatk1.0-02.16.0-2
ii  libc6  2.19-22
ii  libcairo-gobject2  1.14.2-2
ii  libcairo2  1.14.2-2
ii  libdbus-1-31.10.0-3
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.6-2
ii  libgconf-2-4   3.2.6-3
ii  libgdk-pixbuf2.0-0 2.32.0-1
ii  libgif44.1.6-11
ii  libglib2.0-0   2.44.1-1.1
ii  libgnutls-deb0-28  3.3.17-1
ii  libgomp1   5.2.1-17
ii  libgpm21.20.4-6.1+b2
ii  libgtk-3-0 3.16.6-1
ii  libice62:1.0.9-1+b1
ii  libjpeg62-turbo1:1.4.1-2
ii  libm17n-0  1.7.0-1
ii  libmagickcore-6.q16-2  8:6.8.9.9-6
ii  libmagickwand-6.q16-2  8:6.8.9.9-6
ii  libotf00.9.13-2
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-01.36.8-3
ii  libpng12-0 1.2.50-2+b2
ii  librsvg2-2 2.40.10-1
ii  libselinux12.3-2+b1
ii  libsm6 2:1.2.2-1+b1
ii  libtiff5   4.0.5-1
ii  libtinfo5  6.0+20150810-1
ii  libx11-6   2:1.6.3-1
ii  libxft22.3.2-1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxml22.9.2+zdfsg1-4
ii  libxpm41:3.5.11-1+b1
ii  libxrandr2 2:1.5.0-1
ii  libxrender11:0.9.8-1+b1
ii  zlib1g 1:1.2.8.dfsg-2+b1

emacs24 recommends no packages.

Versions of packages emacs24 suggests:
ii  emacs24-common-non-dfsg  24.4+1-2


-- no debconf information


On Thu, 24 Sep 2015 22:20:20 +0900 Norbert Preining 
wrote:
> Package: emacs24
> Version: 24.5+1-2
> Severity: normal
>
> Hi,
>
> the recent update brought a new emacs24 .desktop file that contains
> two desktop entries. But unfortunately this seems to be not
> supported by cinnamon, or at least it offers me only the
> GNU Emacs 24 (Terminal)
> option.
>
> Could you please ship two different .desktop files if possible?
>
> Thanks a lot
>
> Norbert
>
>
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (300, 'testing'), (200, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.3.0-rc1 (SMP w/4 CPU cores; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages emacs24 depends on:
> ii emacs24-bin-common 24.5+1-2
> ii gconf-service 3.2.6-3
> ii libacl1 2.2.52-2
> ii libasound2 1.0.29-1
> ii libatk1.0-0 2.16.0-2
> ii libc6 2.19-22
> ii libcairo-gobject2 1.14.2-2
> ii libcairo2 1.14.2-2
> ii libdbus-1-3 1.10.0-3
> ii libfontconfig1 2.11.0-6.3
> ii libfreetype6 2.6-2
> ii libgconf-2-4 3.2.6-3
> ii libgdk-pixbuf2.0-0 2.32.0-1
> ii libgif4 4.1.6-11
> ii libglib2.0-0 2.44.1-1.1
> ii libgnutls-deb0-28 3.3.17-1
> ii libgomp1 5.2.1-17
> ii libgpm2 1.20.4-6.1+b2
> ii libgtk-3-0 3.16.6-1
> ii libice6 2:1.0.9-1+b1
> ii libjpeg62-turbo 1:1.4.1-2
> ii libm17n-0 1.7.0-1
> ii libmagickcore-6.q16-2 8:6.8.9.9-6
> ii libmagickwand-6.q16-2 8:6.8.9.9-6
> ii libotf0 0.9.13-2
> ii libpango-1.0-0 1.36.8-3
> ii libpangocairo-1.0-0 1.36.8-3
> ii libpng12-0 1.2.50-2+b2

Bug#776540: game-data-packager: please add support for games working with gemrbd engine

[Markus Koschany]

Am 03.10.2015 um 22:04 schrieb Simon McVittie:
[...]
> We don't currently have a good way to spell "the file with sha1sum
> 1234... should be installed as foo1.dat in the English data but foo2.dat
> in German". Is that what you're asking for?
> 
> If some files are identical, there's syntax for adding symlinks (see
> tyrian.yaml).

Hi,

I have pushed my latest revision to branch baldurs-gate. My problem is
that I have seven files with identical names but different sizes and
hashsums. e.g.

 # English Linux installer
  842   e5526c907bb56ec72f8e6cf4eb30fc2e Baldur.ini

 # German Linux installer
  905   2dc7b81c210ed13ea88f509c765d4b76 Baldur.ini

My first attempt was to list all files from both installers under
size_and_md5: and sha1sums: but obviously g-d-p doesn't like this scheme
and fails with an assertion error

AssertionError: ('trying to set size of "%s" to both %d and %d',
'Baldur.ini', 842, 905)


I would like to express:

If Baldur.ini in GameData with size 905 and md5sum
2dc7b81c210ed13ea88f509c765d4b76
is_valid: true
install_to baldurs-gate1-de package

If Baldur.ini in directory with size 905 and md5sum
2dc7b81c210ed13ea88f509c765d4b76 AND Baldur.ini in directory with size
842 e5526c907bb56ec72f8e6cf4eb30fc2e Baldur.ini
raise exception ("That doesn't look like a valid archive")

If Baldur.ini with size and hashsum as declared in baldurs-gate-1.yaml
NOT IN GameData then give up

The current workaround seems to be to rename those files and to append a
language specific suffix. Then one has to declare another stanza where
"file x" is installed as "file y". (e.g. dig.yaml) Baldur's Gate from
gog requires a manual repack, so this technique is quite annoying.

Another problem: the English version ships

data/AREA1700.BIF

the German version

Data/AREA1700.BIF

Both files are identical. My hope was that g-d-p would recognize the
hashsums for both of them when I declare

  25300442  496788a2ce730353acf26d2bebf0471c AREA1700.BIF

and accepts that I install the same file into the data directory
(English version) or the Data directory (German version). Unfortunately
this fails with another error message at build time.
For the last issue symlinking would be an option but this is rather
inconvenient when you have to process a lot of files like that.

Markus






signature.asc
Description: OpenPGP digital signature

Bug#799948: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash

[Nicolas Le Cam]

Package: nvidia-graphics-drivers-legacy-340xx
Version: 340.93-1
Followup-For: Bug #799948

Dear Maintainer,

Same problem here while upgrading from legacy-340xx version 340.76-6
to 340.93-1.
OTOH glx-diversions wasn't upgraded, but it really seems to be the same
problem.

Adding group video to the Debian-gdm user fixes the problem for me.

regards,
Nicolas

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

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

-- Package-specific info:
uname -a:
Linux misaki 4.2.0-1-amd64 #1 SMP Debian 4.2.1-2 (2015-09-27) x86_64 GNU/Linux

/proc/version:
Linux version 4.2.0-1-amd64 (debian-ker...@lists.debian.org) (gcc
version 4.9.3 (Debian 4.9.3-4) ) #1 SMP Debian 4.2.1-2 (2015-09-27)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.93  Wed Aug 19
16:49:15 PDT 2015
GCC version:  gcc version 4.9.3 (Debian 4.9.3-4)

lspci 'VGA compatible controller [0300]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G86M
[Quadro NVS 135M] [10de:042b] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:01f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- 
Kernel driver in use: nvidia

dmesg:
[0.00] Console: colour VGA+ 80x25
[0.264448] vgaarb: setting as boot device: PCI::01:00.0
[0.264448] vgaarb: device added:
PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none
[0.264448] vgaarb: loaded
[0.264448] vgaarb: bridge control possible :01:00.0
[0.489509] Linux agpgart interface v0.103
[1.586071] [Firmware Bug]: Duplicate ACPI video bus devices for
the same VGA controller, please try module parameter
"video.allow_duplicates=1"if the current driver doesn't work.
[2.444345] nvidia: module license 'NVIDIA' taints kernel.
[2.472232] vgaarb: device changed decodes:
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[2.472734] [drm] Initialized nvidia-drm 0.0.0 20150116 for
:01:00.0 on minor 0
[2.472746] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.93
Wed Aug 19 16:49:15 PDT 2015

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Oct  4 09:35 /etc/alternatives/glx ->
/usr/lib/nvidia
lrwxrwxrwx 1 root root   44 Oct  4 09:35
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   41 Oct  4 09:35
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu ->
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   41 Oct  4 09:35
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu ->
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Oct  4 09:35
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Oct  4 09:35
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   57 Oct  4 09:35
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   57 Oct  4 09:35
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   54 Oct  4 09:35
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 Oct  4 09:35
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   49 Oct  4 09:35
/etc/alternatives/glx--libnvidia-cfg.so.1-i386-linux-gnu ->
/usr/lib/i386-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   51 Oct  4 09:35
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   25 Oct  4 09:35
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Oct  4 09:35
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf ->
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Oct  4 09:35
/etc/alternatives/glx--nvidia-bug-report.sh ->
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   29 Oct  4 09:35
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   28 Oct  4 09:35 /etc/alternatives/nvidia
-> /usr/lib/nvidia/legacy-340xx
lrwxrwxrwx 1 root root   57 Oct  4 09:35

Bug#800874: (no subject)

[Ilia Kats]

Actually never mind, it appears the bug report was a bit premature, as 
the plasmoid was disabled upstream. Sorry about that.

Bug#800828: ITP: macs2 -- Model Based Analysis for ChIP-Seq data

[Michael Crusoe]

Whoops, totally missed that macs2 was already packaged as `macs` (I only
search for macs2 as that was the name in PyPI).

FYI: upstream has stopped updating the GitHub tags & releases and switched
to PyPI.

Differences between macs 2.0.9 and macs2 version 2.1.0 in my package
- Upstream's license is now BSD-3-clause
- Single binary with subcommands
- Has two spelling errors (I patched this)

Different packaging choices I made (mostly related to 2015 best practices
vs. 2012)
- pybuild
- upstream/metadata for their paper
- used Git instead of Subversion
- watch looks at PyPI (bonus, upstream signs their releases now!)

Shall I migrate the subversion repository to git and then apply my changes?

My git repo is at git+ssh://git.debian.org/git/debian-med/macs2.git

Bug#733860: Debian Pond Packages

[Ximin Luo]

On 11/01/15 19:25, intrigeri wrote:
> Ximin Luo wrote (11 Jan 2015 16:34:40 GMT) :
>> I spoke to upstream (agl) at 31c3 and explained to him what Debian 
>> experimental is, and he is happy for it to be packaged there for now.
> 
> Woohoo! \o/
> 

Preliminary package is here:

https://mentors.debian.net/package/pond

but with the GUI disabled because of that pending GTK issue.

I just need to write man pages for {client,editstate,server} then I will go 
upload it.

X

-- 
GPG: 4096R/1318EFAC5FBBDBCE
git://github.com/infinity0/pubkeys.git

Bug#599537: closed by Michael Gilbert <mgilb...@debian.org> ()

[Camaleón]

El 2015-10-03 a las 21:42 +, Debian Bug Tracking System escribió:

> Upstream states this in the dhclient.conf manpage now:
> 
> These  declarations  are  automatically set in leases acquired by the DHCP
> client, but must also be configured in predefined leases - a predefined lease
> whose expiry time has passed will not be used by the DHCP client.
> 
> Best wishes,
> Mike

Well, "dhclient.conf" man page has always (at least since Squeeze) 
stated so which basically means this inactive 5 years bug still remains
(and also bug #100886 that was closed in the same way) ;-)

Greetings,

-- 
Camaleón 

Bug#800800: [Pkg-virtualbox-devel] Bug#800800: vagrant: Running vagrant up to start a VM fails with error

[Ritesh Raj Sarraf]

On Sat, 2015-10-03 at 16:24 -0300, Antonio Terceiro wrote:
> > The guest machine entered an invalid state while waiting for it
> > to boot. Valid states are 'starting, running'. The machine is in
> the
> > 'poweroff' state. Please verify everything is configured
> > properly and try again.
> > 
> > If the provider you're using has a GUI that comes with it,
> > it is often helpful to open that and watch the machine, since the
> > GUI often has more helpful error messages than Vagrant can
> retrieve.
> > For example, if you're using VirtualBox, run `vagrant up` while the
> > VirtualBox GUI is open.
> > 
> > The primary issue for this error is that the provider you're using
> > is not properly configured. This is very rarely a Vagrant issue.
> > 


From this bug report, there is not enough information on what that
"invalid" state was. Please provide that information, as is mentioned
above. 

"For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open."


Other than that, do you have anything in your system logs ?


-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



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

Bug#800830: checkflac from flactag warns about cuesheets from mkcue

[Daniel Pocock]

Package: mkcue
Version: 1-4
Severity: important
X-Debbugs-CC: a...@gently.org.uk

I used mkcue as part of a workflow for some CDs which become FLAC files
with embedded cue sheets.

Later, I tried the checkflac script from flactag (it is discussed in the
flactag man page), it read the disc ID from the CD in the drive and also
calculated a disc ID from the cue sheet, it found a mismatch.

Bug#800831: missing pre-gap and index mark data

[Daniel Pocock]

Package: mkcue
Version: 1-4
Severity: important
X-Debbugs-CC: a...@gently.org.uk

mkcue is behaving like "cdrdao --fast-toc", it is not reading the
pre-gap and index mark details from the disk and it is not including
those details in the Cue sheet.

For some purposes, such as calculating a Musicbrainz disk ID, it may be
necessary to have all these details.

Bug#800832: mate-terminal: sets TERM to ‘xterm’ even though ‘xterm-256colors’ would be appropriate

[Axel]

Package: mate-terminal
Version: 1.8.1+dfsg1-4
Severity: minor

Dear Maintainer,

This results in programs like E Links and Midnight Commander only offering 16 
colour
interfaces, at least by default. Whereas some programs, like E Links, can just 
be set to
use 256 colours, others, like the Midnight Commander, will refuse to accept any 
such
setting.

A quick fix can be achieved by using the “Run a custom command instead of my 
shell”
setting (menu → Edit → Profile Preferences → Title and Command) and using this 
command:

env TERM=xterm-256color 

e.g.:

env TERM=xterm-256color /bin/bash

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

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

Versions of packages mate-terminal depends on:
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-18+deb8u1
ii  libcairo2 1.14.0-2.1
ii  libdconf1 0.22.0-1
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u2
ii  libglib2.0-0  2.42.1-1
ii  libgtk2.0-0   2.24.25-3
ii  libice6   2:1.0.9-1+b1
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libsm62:1.2.2-1+b1
ii  libvte9   1:0.28.2-5
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  mate-desktop-common   1.8.1+dfsg1-3+deb8u1
ii  mate-terminal-common  1.8.1+dfsg1-4
pn  python:any

mate-terminal recommends no packages.

mate-terminal suggests no packages.

-- no debconf information

Bug#599537: [pkg-dhcp-devel] Bug#599537: closed by Michael Gilbert <mgilb...@debian.org> ()

[Michael Gilbert]

control: reopen -1

On Sun, Oct 4, 2015 at 3:07 AM, Camaleón wrote:
> Well, "dhclient.conf" man page has always (at least since Squeeze)
> stated so which basically means this inactive 5 years bug still remains
> (and also bug #100886 that was closed in the same way) ;-)

If the current documentation isn't clear, which I'm not convinced of,
do you have a better wording suggestion?  Is better wording enough to
make people happy about this problem?

Best wishes,
Mike

Bug#800879: libmetacity-private3a: failes to install if libmetacity-private3 is installed

[James Cowgill]

Package: libmetacity-private3a
Version: 1:3.18.0-1
Severity: serious

Hi,

libmetacity-private3a does not install properly if libmetacity-private3
is already installed. When I retried this it suceeded because apt
decided to remove libmetacity-private3 first, but the first time I
upgraded the package and if is installed manually, it fails.

# dpkg -l libmetacity-private*
...
ii  libmetacity-private31:3.17.2-4

# dpkg -i /var/cache/apt/archives/libmetacity-private3a_1%3a3.18.0-1_amd64.deb 
Selecting previously unselected package libmetacity-private3a.
(Reading database ... 23001 files and directories currently installed.)
Preparing to unpack .../libmetacity-private3a_1%3a3.18.0-1_amd64.deb ...
Unpacking libmetacity-private3a (1:3.18.0-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libmetacity-private3a_1%3a3.18.0-1_amd64.deb 
(--install):
 trying to overwrite '/usr/lib/libmetacity-private.so.3.0.0', which is also in 
package libmetacity-private3 1:3.17.2-4
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libmetacity-private3a_1%3a3.18.0-1_amd64.deb

Thanks,
James

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

Bug#800878: inkscape: non-free file "gallardo.svgz"

[Dmitry Smirnov]

Source: inkscape
Version: 0.91-5
Severity: important

Dear maintainer,

According to its metadata, image "/usr/share/inkscape/examples/gallardo.svgz" 
appears to be non-free:

WorkLicense: http://creativecommons.org/licenses/by-nc-sa/2.5/
LicenseProhibits: http://web.resource.org/cc/CommercialUse
WorkDescription: A traced Lamborghini Gallardo.
The source image can be found at:
http://en.wikipedia.org/wiki/Image:Lamborghini_Gallardo_silver.jpg

-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B


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

Bug#599537: [pkg-dhcp-devel] Bug#599537: closed by Michael Gilbert <mgilb...@debian.org> ()

[Camaleón]

El 2015-10-04 a las 09:50 -0400, Michael Gilbert escribió:

> control: reopen -1
> 
> On Sun, Oct 4, 2015 at 3:07 AM, Camaleón wrote:
> > Well, "dhclient.conf" man page has always (at least since Squeeze)
> > stated so which basically means this inactive 5 years bug still remains
> > (and also bug #100886 that was closed in the same way) ;-)
> 
> If the current documentation isn't clear, which I'm not convinced of,
> do you have a better wording suggestion?  Is better wording enough to
> make people happy about this problem?
> 
> Best wishes,
> Mike

After 5 years I'm afraid I completely forgot about this problem but 
looks like bug #100886 provides some kind of patch for code and also 
improvement of the man page. But yet again the bug was opened 14 years 
ago so who knows... 

Maybe using a different "expire" value for the template to avoid this 
from happening or adding a simple comment ("#") on the top of the 
"expire" entry so the user can be better aware of this.

Greetings,

-- 
Camaleón 

Bug#800882: python-cairosvg: fails with 'module' object has no attribute 'ANTIALIAS_FAST'

[Jonas Smedegaard]

Package: python-cairosvg
Version: 1.0.16-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Any (or at least pdf and png that I tried) use of commandline toll
cairosvg-py2 results in this error:

Traceback (most recent call last):
  File "/usr/bin/cairosvg-py2", line 24, in 
import cairosvg
  File "/usr/lib/python2.7/dist-packages/cairosvg/__init__.py", line 27, in 

from . import surface
  File "/usr/lib/python2.7/dist-packages/cairosvg/surface/__init__.py", line 
47, in 
"optimizeSpeed": cairo.ANTIALIAS_FAST,
AttributeError: 'module' object has no attribute 'ANTIALIAS_FAST'


 - Jonas

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

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

Versions of packages python-cairosvg depends on:
ii  python2.7.9-1
ii  python-cairo  1.8.8-2

python-cairosvg recommends no packages.

python-cairosvg suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWET67AAoJECx8MUbBoAEhECcP/38N8qBHN2Ithuou0+BtR6rw
VqlNkMXSHgvSLN4tC4AoKxf9Q3JMf7l04HKXcQqccfcN6Ra8xlAwzSLooTve7oKP
Zw2S+uavx21DGqkcvyFgw/oAUrmyazOScJg6tfbJ0EenzyLbP4LvTs+dbDd6Cj8N
R4NLnl6Qc6aixLBtdQmZoXvyUceOAkgOvyEjOwHeFPPl/7btEtSj+XBVxgzX3lRj
FcKEYdwT2aqAzik6QRqr8sOgtQTzsEDtf5B7g0ZrRI3fn6nUB+lYL6me3sO1KZyP
oEpyfpuUPEOXZ7PDaF4u1g2LgJFjiMGydqheIQJlAviIIpPJML+m6bNcBRSOAMFG
vcKjFmmFwa2ygjENsRFvhPFDY1z599z7u/DzxhbktG9g7daoYx2Mm3jL/fAfugf2
1mNSj+RDqR/nQB8sVrZC98QamL81PkfiVeuzc1SqiNcWB3VYqT+IprtIDThVmtba
WGQLjTH+euoSFDghN3ETYVIxfLBzP8GxxhjP92yOIpMpJlD0FFCsf06QpsMnAgLS
GPUlKtB9d56EQFP/AimyCImef4yuLBs0fcYA0LLcs9NUcsWx4RmxnWcvMKkqkwox
EQRj/O4U++sAXdYavc95/TzKHab7w/vJxAFZUupknly3G2IfIuSkaCUV8zaqGN4m
Im0neT0XyiBz1lNlroNO
=JHwq
-END PGP SIGNATURE-

Bug#800878: inkscape: non-free file "gallardo.svgz"

[Mattia Rizzolo]

On Mon, Oct 05, 2015 at 12:52:49AM +1100, Dmitry Smirnov wrote:
> According to its metadata, image "/usr/share/inkscape/examples/gallardo.svgz" 
> appears to be non-free:
> 
> WorkLicense: http://creativecommons.org/licenses/by-nc-sa/2.5/
> LicenseProhibits: http://web.resource.org/cc/CommercialUse
> WorkDescription: A traced Lamborghini Gallardo.
> The source image can be found at:
> http://en.wikipedia.org/wiki/Image:Lamborghini_Gallardo_silver.jpg


It's funny because according to that wikipedia page the image under a
double license GFDL-1.2 / CC-BY-SA-3.0.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#759794: [Debian-med-packaging] Bug#759794: insighttoolkit4: FTBFS on amd64 with ENOSPC

[Steve M. Robbins]

Hello Gert,

I ran into this issue again today which prompted me to re-read this bug log.

On Sat, 30 Aug 2014 16:15:19 +0200 Gert Wollny  wrote:
> > insighttoolkit4 repeatedly FTBFS on amd64 [1] because of ENOSPC. A
> > manual build on porterbox barriere.debian.org reported a need of ~44GB
> > while it failed on buildd barber at approx 37GB of disk space.
> 
> There are two things that could probably help:
> 
>  - change the python-binding dimensions to use only 2 an 3. I enabled
>also 4 because in our lab we have to deal with 3D+t data, but in the
>end using 4D data with python is not such a good idea memory-wise. 
>(On Monday I will check how much this actually saves)

I can definitely make this change for the next upload.  
Did you ever quantify whether this saves on disk space?

>  - build with -g1 or even -g0 (have to look up if this is not against
>Debian Policy).  The python bindings creates a lots of debugging info
>that gets thrown away anyway. We would then also have to disable the
>lib*-dbg package.

I think in the coming months there will be an archive-wide automatic debug 
package generation [1] .  We can then drop the -dbg package.  I haven't 
checked, but I suspect it will still require building with -g.

[1]  https://lists.debian.org/debian-devel/2015/08/msg00443.html

Thanks,
-Steve


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

Bug#800824: DD

[Mathias Behrle]

* Raphael Hertzog: " Re: DD" (Sun, 4 Oct 2015 15:30:54 +0200):

Hi Raphael,

thanks for getting back.

> On Sat, 03 Oct 2015, Mathias Behrle wrote:
> > Will wait for tomorrow to see if something waits in the queue or otherwise
> > will try again to see it will be fixed.
> 
> If the error persists, then get in touch with Frontdesk... 

Did that already: 800...@bugs.debian.org

> Are you submitting this logged via a SSL client certificate generated on
> sso.debian.org?
> 
> If yes, try when you are not logged.
> If no, then try to get one (via your alioth account) and try again while
> being logged.

My first attempt was logged in via my alioth credentials for mathiasb-guest.
Indeed the provisional account was created, but the server error raises
whenever the email challenge is triggered.

I meanwhile tried also with a SSO certificate (I didn't have one before), but
the problem persists. So it seems I will have to wait until someone with
insight will have a look at the problem.

Cheers,
Mathias

-- 

Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6


pgpIaX1MhgJu6.pgp
Description: Digitale Signatur von OpenPGP

Bug#673772: asynchronous transfer of control with delay abort and syscalls not working

[Nicolas Boulenguez]

Package: gnat-5
Followup-For: Bug #673772
Control: tag -1 upstream wontfix

Quoting upstream:
Actually Ada does not make any guarantee when mixing ATC and system calls and
indeed, it is fundamentally unsafe if not impossible to properly abort from any
random system call, so this isn't supported.

Bug#800885: awesome: missing systray icons after number of screens changes

[Roland Hieber]

On Sun, 04 Oct 2015 17:00:21 +0200 Roland Hieber  wrote:
> However, it does not happen with all systray icons; so far I could reproduce 
> it
> with:
> 
> * xfce4-power-manager
> * shutter

* gmpc

 - Roland

Bug#800878: inkscape: non-free file "gallardo.svgz"

[Dmitry Smirnov]

On Sunday 04 October 2015 15:56:11 Mattia Rizzolo wrote:
> On Mon, Oct 05, 2015 at 12:52:49AM +1100, Dmitry Smirnov wrote:
> > According to its metadata, image
> > "/usr/share/inkscape/examples/gallardo.svgz"> 
> > appears to be non-free:
> > WorkLicense: http://creativecommons.org/licenses/by-nc-sa/2.5/
> > LicenseProhibits: http://web.resource.org/cc/CommercialUse
> > WorkDescription: A traced Lamborghini Gallardo.
> > The source image can be found at:
> > http://en.wikipedia.org/wiki/Image:Lamborghini_Gallardo_silver.jpg
> 
> It's funny because according to that wikipedia page the image under a
> double license GFDL-1.2 / CC-BY-SA-3.0.

Not really that funny because there are two different images - the original 
photo (CC-BY-SA-3.0) and its traced image (derivative) included to Inkscape 
under CC-BY-NC-SA-2.5... I reckon there is some irony...

Anyway I found another non-free image:

/usr/share/inkscape/examples/animated-clock.svg

LicenseProhibits: http://web.resource.org/cc/CommercialUse
WorkLicense: http://creativecommons.org/licenses/by-nc-nd/2.5/

Thanks.

-- 
Best wishes,
 Dmitry Smirnov.

---
Democracy is a pathetic belief in the collective wisdom of individual
ignorance.
-- H. L. Mencken


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

Bug#800898: skrooge-common: non-free images

[Dmitry Smirnov]

Package: skrooge-common
Version: 1.9.3-1
Severity: important

Dear maintainer,

The following images appears to be non-free:

/usr/share/icons/hicolor/scalable/actions/skrooge_less.svgz
/usr/share/icons/hicolor/scalable/actions/skrooge_more.svgz
/usr/share/icons/hicolor/scalable/actions/skrooge_much_less.svgz
/usr/share/icons/hicolor/scalable/actions/skrooge_much_more.svgz

According to their metadata:

LicenseProhibits: http://creativecommons.org/ns#CommercialUse
WorkLicense: http://creativecommons.org/licenses/by-nc-sa/3.0/

Please investigate.

-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B


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

Bug#800881: jessie-pu: package nvidia-graphics-drivers/340.93-0+deb8u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Second PU request for fixing CVE-2015-5950.

This requires a new upstream release, too, that is two or three releases
ahead of what is currently in jessie.

The proposed changes are all already included and tested in sid.
This includes changes from several uploads to sid (up to 340.76-4) that
are a new upstream release and several bugfixes and minor features that
I consider appropriate for jessie.
The big changes done in sid 340.76-5 onwards are excluded, instead the
changes needed for jessie were cherry-picked into 340.93-0+deb8u1.

Regarding the version number, 340.93-1 was uploaded to sid (before the
CVE was made public), so we need to use 340.93-0+deb8u1 this time (or
would 340.93-0 be ok?). (A shorter version number reduces version string
inflation when rebuilding nvidia-graphics-modules.)


Annotated, reordered and merged changelog:

+nvidia-graphics-drivers (340.93-0+deb8u1) jessie; urgency=medium
+
+  * New upstream legacy 340xx branch release 340.93 (2015-09-02).
+* Fixed CVE-2015-5950: Memory corruption due to an unsanitized pointer.
+  (Closes: #800566)
+  * New upstream legacy 340xx branch release 340.76 (2015-01-27).
+* Improved compatibility with recent Linux kernels.  (Closes: #778698)
+  * Update lintian overrides.

New upstream blob with security bugfix.

+  * nvidia-driver-bin, libnvidia-compiler, libnvidia-eglcore,
+libgl1-nvidia-glx: Add Provides+Conflicts: $pkg-${nvidia:Version} to
+forbid co-installation with the respective legacy packages from the same
+upstream version due to file conflicts on versioned files that are not
+handled via alternatives.

improve and simplify co-existence with legacy packages

+  * bug-script: Report file information in arm-linux-gnueabihf directories.
+  * bug-script: Collect information from /etc/modules{,-load.d/}.

get better information from reportbug

+  * README.source: Document my schroot setup for testing module compilation.
+  * README.source: Document armhf setup for testing module compilation.

maintainer documentation

+  * Add ignore_xen_on_arm.patch needed for dkms build on armhf: armmp
+kernel headers ship with CONFIG_XEN enabled, which breaks the build,
+so since running this driver on XEN is currently not supported,
+ignore the check for XEN in nv-linux.h as a workaround on arm, and
+also disable CONFIG_XEN and CONFIG_XEN_DOM0 if building on <= 3.16.
+(Closes: #794435)

Allow the kernel module to be compiled for the Debian armhf kernels.
The driver is packaged for armhf, but cannot be tested due to lack of hardware.

+  * nvidia-detect: Detect stretch as supported suite, and parse -h as --help.
+(Closes: #792801)

+  * Fix nvidia-modprobe.conf module unload ordering, to stop nvidia-uvm
+getting stuck until a second modprobe -r nvidia-current is issued.
+Fix provided by Jö Fahlke. Thanks! (Closes: #793386)

important bugfix for bumblebee users

+  * Add Luca Boccassi to Uploaders.

+  * nvidia-driver, nvidia-kernel-*: Report the latest tested Linux version
+that can build the kernel module in the package description.

Maybe that gives some hints to people complaining about the jessie
driver not supporting the latest kernels from jessie-backports ...

+  * Split some old UNRELEASED changelog entries to linearize the BTS history.

+  * nvidia-kernel-source: Use reproducible timestamps and file order inside
+/usr/src/nvidia-kernel.tar.xz.

+  * conftest.h:
+- Implement new conftest.sh function nvidia_grid_build (352.41).
+- Implement new conftest.sh functions backing_dev_info (346.82),
+  phys_to_dma, dma_ops, get_dma_ops, noncoherent_swiotlb_dma_ops (352.09).
+- Implement new conftest.sh function dma_map_ops (352.30).
+- Reorder conftest.h to match conftest.sh.
+- Implement check for linux/log2.h (346.16).
+- Implement check for xen/ioemu.h (346.59).
+- Implement new conftest.sh functions write_cr4, xen_ioemu_inject_msi
+  (346.59), list_cut_position (349.12).
+- Implement new conftest.sh functions file_inode, drm_pci_set_busid
+  (340.76).

We maintain only one conftest.h for all upstream release branches.
Most of the checks that were added in newer release branches are now
also needed for 340.93.


Andreas
Index: debian/libnvidia-eglcore.lintian-overrides.in
===
--- debian/libnvidia-eglcore.lintian-overrides.in	(.../tags/340.65-2)	(revision )
+++ debian/libnvidia-eglcore.lintian-overrides.in	(.../branches/340)	(revision )
@@ -1,6 +1,5 @@
 # The NVIDIA license does not allow any form of modification.
 [!amd64]: binary-file-built-without-LFS-support
-shlib-calls-exit
 [i386]: shlib-with-non-pic-code
 spelling-error-in-binary
 hardening-no-fortify-functions
Index: debian/nvidia-opencl-icd.lintian-overrides.in

Bug#800889: 3.18.0

[Philipp Klaus Krause]

I just tried 3.18.0 from current debian testing, and see the same
problem there.

Philipp

Bug#800534: jedit: Open dialog shows nonsense in the files list view

[tony mancill]

On 09/30/2015 07:47 AM, Victor Porton wrote:
> Subject: jedit: Open dialog shows nonsense in the files list view
> Package: jedit
> Version: 5.1.0+dfsg-2
> Severity: normal
> 
> Dear Maintainer,
> 
> File Open dialog sometimes shows some nonsense. See the attached
> screenshot for an example.

Hello Victor,

Thank you for the bug report.  I am in the process of packaging a new
upstream release of jedit and then will evaluate/fix this bug on jedit  5.2.

Cheers,
tony




signature.asc
Description: OpenPGP digital signature