Bug#810737: pbuilderrc setting for --bin-nmu-maintainer

[Thorsten Glaser]

Andreas Beckmann dixit:

>something: --bin-nmu-maintainer "$DEBFULLNAME <$DEBEMAIL>" (using the

Do note that devscripts also supports (and, in some older versions,
required, due to bugs) setting DEBEMAIL to the entire stuff.

That means you likely need to do something like this:

if [[ $DEBEMAIL = *' <'*'>' ]]; then
binnmumntner=$DEBEMAIL
elif [[ -z $DEBEMAIL ]]; then
error 'DEBEMAIL not set'
elif [[ -z $DEBFULLNAME ]]; then
error 'DEBFULLNAME not set and DEBEMAIL does not contain it'
else
binnmumntner="$DEBFULLNAME <$DEBEMAIL>"
fi

bye,
//mirabilos
-- 
This space for rent.

Bug#810750: kdevelop-python: FTBFS with python3.5 and no python3.4 installed

[Scott Kitterman]

Package: kdevelop-python
Version: 1.7.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Here's the actual failure during configure:

-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.5.1", 
minimum required is "3.0") 
-- Found PythonLibs: /usr/lib/aarch64-linux-gnu/libpython3.5m.so (found 
suitable version "3.5.1+", minimum required is "3.4") 
CMake Error at parser/CMakeLists.txt:18 (message):
  Python 3.4 with --enable-shared is required to build kdev-python

Full build log can be found at [1].

Scott K

[1] 
https://buildd.debian.org/status/fetch.php?pkg=kdevelop-python=arm64=1.7.0-1%2Bb1=1452552042

Bug#810755: RM: aegean [mips] -- ROM; builds OK but binaries crash on mips

[Sascha Steinbiss]

Package: ftp.debian.org
Severity: normal

Recently introduced build time tests have revealed that the mips binaries
don't work even if they are compiled with no obvious error message. 
As the maintainer, I have removed mips from the list of supported
archs and I am kindly asking to remove previous old mips binaries in
order not to stall testing migration.

Thanks
Sascha

Bug#793900: FTCBFS: uses build arch compiler

[Olly Betts]

Control: tag -1 +pending

On Tue, Jul 28, 2015 at 08:11:40PM +0200, Helmut Grohne wrote:
> +   CC = $(DEB_HOST_GNU_TYPE)-cc

FYI, your patch FTBFS - I seem to need to use this instead:

   CC = $(DEB_HOST_GNU_TYPE)-gcc

Cheers,
Olly

Bug#810759: cwiid: BD-Uninstallable on kfreebsd-* and hurd-i386 due to libbluetooth-dev

[Steven Chamberlain]

Hi,

Sebastian Ramacher wrote:
> libbluetooth-dev is only available on linux-any. Hence cwiid is currently
> BD-Uninstallable on kfreebsd-* and hurd-i386. Could the B-D on 
> libbluetooth-dev
> be restricuted to linux-any?

I just tried:  ./configure absolutely requires -lbluetooth, which is
only provided on Linux.  I don't think there is any bug in cwiid here,
it has never built before on non-Linux.  If we ever get a compatible
libbluetooth on kfreebsd or hurd it will then build.

The Wii Remote seems to only have Bluetooth connectivity so this package
wouldn't seem useful anyway wiuthout it.

p.s. I'm checking right now to see if ardour can build without cwiid
instead.

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


signature.asc
Description: Digital signature

Bug#810763: python3-uno: Please add support for python3.5

[Diederik de Haas]

Package: python3-uno
Version: 1:5.0.4~rc2-2
Severity: wishlist

python3 version 3.5.1-1 just entered unstable, but if I want to upgrade
to that version, I'll have to remove python3-uno and because libreoffice
depends on python3-uno, I'd have to remove that too.
Which of course I don't want to. 
So it would be great if python3.5 support can be added.

Regards,
  Diederik

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

Kernel: Linux 4.3.0-1-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 python3-uno depends on:
ii  libc6 2.21-6
ii  libgcc1   1:5.3.1-5
ii  libpython3.4  3.4.4-2
ii  libreoffice-core  1:5.0.4~rc2-2
ii  libstdc++65.3.1-5
ii  python3   3.4.3-7
ii  python3.4 3.4.4-2
ii  uno-libs3 5.0.4~rc2-2
ii  ure   5.0.4~rc2-2

python3-uno recommends no packages.

python3-uno suggests no packages.

-- no debconf information

Bug#808873: cron-apt never runs

[Ola Lundqvist]

Hi

Please try to enable cron apt through cron.d/cron-apt again. It is
obviously disabled that way.
Also can you send me the contents of

ls -l /usr/sbin/anacron

If you execute /etc/cron.daily/cron-apt is it executed then? I´m asking as
some system do not allow execution on all directories.

What else can you find in the logs about cron?

/ ola

Sent from a phone
Den 11 jan 2016 22:09 skrev "Jürgen Bausa" :

> > Please send me the contents of:
> > /etc/cron.d/cron-apt (when enabled that way)
>
> root@lina:/home/jba# cat /etc/cron.d/cron-apt
> #
> # Regular cron jobs for the cron-apt package
> #
> # Every night at 4 o'clock.
> 0 4 * * *   roottest -x /usr/sbin/cron-apt && /usr/sbin/cron-apt
> # Every hour.
> # 0 *   * * *   roottest -x /usr/sbin/cron-apt && /usr/sbin/cron-apt
> /etc/cron-apt/config2
> # Every five minutes.
> # */5 * * * *   roottest -x /usr/sbin/cron-apt && /usr/sbin/cron-apt
> /etc/cron-apt/config2
>
>
> > /etc/crontab
> root@lina:/home/jba# cat /etc/crontab
> # /etc/crontab: system-wide crontab
> # Unlike any other crontab you don't have to run the `crontab'
> # command to install the new version when you edit this file
> # and files in /etc/cron.d. These files also have username fields,
> # that none of the other crontabs do.
>
> SHELL=/bin/sh
> PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
>
> # m h dom mon dow user  command
> 17 ** * *   rootcd / && run-parts --report /etc/cron.hourly
> 25 6* * *   roottest -x /usr/sbin/anacron || ( cd / && run-parts --
> report /etc/cron.daily )
> 47 6* * 7   roottest -x /usr/sbin/anacron || ( cd / && run-parts --
> report /etc/cron.weekly )
> 52 61 * *   roottest -x /usr/sbin/anacron || ( cd / && run-parts --
> report /etc/cron.monthly )
> #
>
> # m h dom mon dow user  command
> */10   * *   *   *   root  sync_share >/dev/null 2>&1
>
>
> > /etc/cron-apt (all files)
>
> root@lina:/etc/cron-apt# cat config
> # Configuration for cron-apt. For further information about the possible
> # configuration settings see /usr/share/doc/cron-apt/README.gz.
>
> root@lina:/etc/cron-apt# ll *.d*
> action.d:
> insgesamt 8
> -rw-r--r-- 1 root root  18 Mai 24  2013 0-update
> -rw-r--r-- 1 root root 141 Sep  5 14:02 3-download
>
> config.d:
> insgesamt 0
>
> errormsg.d:
> insgesamt 0
>
> logmsg.d:
> insgesamt 0
>
> mailmsg.d:
> insgesamt 0
>
> syslogmsg.d:
> insgesamt 0
> root@lina:/etc/cron-apt# cat action.d/0-update
> update -o quiet=2
> root@lina:/etc/cron-apt# cat action.d/3-download
> autoclean -y
> # jba 2013-05-26 do upgrade
> #dist-upgrade -d -y -o APT::Get::Show-Upgraded=true
> dist-upgrade -y -o APT::Get::Show-Upgraded=true
>
> >
> > And do a "ls -l /etc/cron.*" and send me the output of that.
>
> root@lina:/etc/cron-apt# ls -l /etc/cron.*
> /etc/cron.d:
> insgesamt 12
> -rw-r--r-- 1 root root 244 Dez 28  2014 anacron
> -rw-r--r-- 1 root root 355 Dez 26 19:12 cron-apt
> -rw-r--r-- 1 root root 102 Jan  9 22:34 testlog
>
> /etc/cron.daily:
> insgesamt 60
> -rwxr-xr-x 1 root root   311 Dez 28  2014 0anacron
> -rwxr-xr-x 1 root root 15000 Apr 13  2015 apt
> -rwxr-xr-x 1 root root   314 Nov  8  2014 aptitude
> -rwxr-xr-x 1 root root   355 Okt 17  2014 bsdmainutils
> lrwxrwxrwx 1 root root18 Dez 22 21:24 cron-apt -> /usr/sbin/cron-apt
> -rwxr-xr-x 1 root root  1597 Apr 10  2015 dpkg
> -rwxr-xr-x 1 root root  4125 Feb 17  2015 exim4-base
> lrwxrwxrwx 1 root root37 Dez 11 02:59 google-chrome ->
> /opt/google/chrome/cron/google-chrome
> -rwxr-xr-x 1 root root   580 Dez 30  2011 htdig
> -rwxr-xr-x 1 root root89 Nov  8  2014 logrotate
> -rwxr-xr-x 1 root root  1293 Dez 31  2014 man-db
> -rwxr-xr-x 1 root root   435 Jun 13  2013 mlocate
> -rwxr-xr-x 1 root root   249 Nov 19  2014 passwd
>
> /etc/cron.hourly:
> insgesamt 0
>
> /etc/cron.monthly:
> insgesamt 4
> -rwxr-xr-x 1 root root 313 Dez 28  2014 0anacron
>
> /etc/cron.weekly:
> insgesamt 12
> -rwxr-xr-x 1 root root 312 Dez 28  2014 0anacron
> -rwxr-xr-x 1 root root 120 Sep  5 23:37 flashplugin
> -rwxr-xr-x 1 root root 771 Dez 31  2014 man-db
>
>
> >
> > Your log files is probably useful too. At least check that cron is
> running
> > something else. You mention that it is not running one of the other
> scripts
> > you have. But is it running any cron job at all?
>
> I checked by putting a file in /etc/cron.d that outputs every minute. That
> worked. It seems to me, that files maybe only run by cron, if the system is
> running at that time. As anacron is installed, it should also if the
> system is
> turned on later. Or am I wrong?
>
> Juergen
>
> >
> > Cheers,
> >
> > // Ola
>

Bug#810759: cwiid: BD-Uninstallable on kfreebsd-* and hurd-i386 due to libbluetooth-dev

[Sebastian Ramacher]

Source: cwiid
Version: 0.6.00+svn201-3.2
Severity: important

libbluetooth-dev is only available on linux-any. Hence cwiid is currently
BD-Uninstallable on kfreebsd-* and hurd-i386. Could the B-D on libbluetooth-dev
be restricuted to linux-any?

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#809184: "aptitude changelog" aborts with "Illegal instruction"

[Manuel A. Fernandez Montecelo]

Control: tags -1 - unreproducible + wontfix
Control: close -1


Hi Bjarni,

2015-12-29 23:11 To Bjarni Ingi Gislason:

2015-12-29 17:48 Bjarni Ingi Gislason:

On Mon, Dec 28, 2015 at 10:25:07AM +0800, Paul Wise wrote:

On Mon, 28 Dec 2015 01:57:25 + Bjarni Ingi Gislason wrote:


   aptitude changelog apt ...


Does this always produce the same outcome?



Yes, at least three times.


   Output was "Illegal instruction" with a return value of 132.

...

Architecture: i386 (i586)


There are some things that would help the aptitude maintainers figure
out what the problem is:

Send the output of this command:

cat /proc/cpuinfo



processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 5
model   : 8
model name  : AMD-K6(tm) 3D processor
stepping: 12
cpu MHz : 331.579
cache size  : 64 KB
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr cx8 pge mmx syscall 3dnow k6_mtrr 
vmmcall
bogomips: 663.15
clflush size: 32
cache_alignment : 32
address sizes   : 32 bits physical, 32 bits virtual
power management:
[...]


Thanks for the info.

Looks like a problem with Boost, and I've been checking in its BTS and:

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

The AMD K6 is an i585, or at least not a fully compatible i686, if I
recall correctly.


I've pinged the maintainers of the x32 port to see if they go ahead with
the NMU (pushing a release with that patch included).  I am not sure if
we can do much more about it from aptitude's side.


So it was officially announced that these processors will not be
supported and it seems that there will not be a reversal of this
decision:

 https://lists.debian.org/debian-devel-announce/2016/01/msg1.html

 https://lists.debian.org/debian-devel/2015/09/msg00589.html


It seems that the only solution for you is to use older releases only.

So at this point, I think that we cannot do anything about this from
aptitude's side, sorry.  I am closing the bug report.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#810681: heimdal-clients: installing package forces krb5-user to be removed

[Brian May]

Russ Allbery  writes:

> My recollection is that it doesn't actually do encryption of the data
> transfers, which is obviously something of a problem.  I think it only
> encrypts the control channel, if that.

>From memory: You can have the control channel signed or encrypted or
plain text. I suspect plain text might be the default.
-- 
Brian May 

Bug#810754: ardour: libs/pbd/dmalloc.cc is non-free

[David Bremner]

Source: ardour
Version: 2.8.16+git20131003-4
Severity: serious
Justification: Policy 2.1.5

Control: tag -1 jessie

As documented in debian/control, the license of libs/pbd/dmalloc.c is

 * Permission to use, copy, modify, and distribute this software for any
 * NON-COMMERCIAL purpose and without fee is hereby granted, provided
 * that the above copyright notice and this permission notice appear
 * in all copies, and that the name of Gray Watson not be used in
 * advertising or publicity pertaining to distribution of the document
 * or software without specific, written prior permission.


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

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

Bug#810766: regression: git-sh-prompt: incorrectly determines the upstream for repos produced by recent git svn clone --stdlayout

[Paul Wise]

Package: git
Version: 1:2.6.4-1
Severity: normal
File: /usr/lib/git-core/git-sh-prompt

I recently did a git svn clone of the Planet Debian SVN and I noticed
that the normal upstream indicator in the git part of my $PS1 was not
working properly. The issue appears to be that the code decides that
the upstream is trunk instead of origin/trunk. trunk gives an error
from git rev-list but origin/trunk does not. It works for normal git
svn clone because there the remote branch is just named git-svn with
no origin/ prefix. I'm using the below settings for my bash git PS1.
In case you need a small repo to reproduce this with, try neomis.
It still works with some of my old repos because the remote branch is
just trunk instead of origin/trunk, so I think git-svn changed this.

http://neomis.googlecode.com/svn

pabs@chianamo ~ $ git svn clone --stdlayout 
svn+ssh://svn.debian.org/svn/planet-debian
...
pabs@chianamo ~ $ cd planet-debian
pabs@chianamo ~/planet-debian (master) $ cd ..
pabs@chianamo ~ $ git svn clone svn+ssh://svn.debian.org/svn/secure-testing
...
pabs@chianamo ~ $ cd secure-testing
pabs@chianamo ~/secure-testing (master=) $ cd ..
pabs@chianamo ~ $ grep GIT_PS1 ~/.bash.d/git
export GIT_PS1_SHOWDIRTYSTATE=true
export GIT_PS1_SHOWSTASHSTATE=true
export GIT_PS1_SHOWUNTRACKEDFILES=true
export GIT_PS1_SHOWUPSTREAM=auto
export GIT_PS1_SHOWUPSTREAM=name
export GIT_PS1_SHOWCOLORHINTS=true
export GIT_PS1_DESCRIBE_STYLE=branch

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (860, 'testing-proposed-updates'), (850, 
'buildd-testing-proposed-updates'), (800, 'unstable'), (790, 
'buildd-unstable'), (700, 'experimental'), (690, 'buildd-experimental'), (500, 
'unstable-debug'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)

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

Versions of packages git depends on:
ii  git-man   1:2.6.4-1
ii  libc6 2.21-6
ii  libcurl3-gnutls   7.46.0-1
ii  liberror-perl 0.17-1.2
ii  libexpat1 2.1.0-7
ii  libpcre3  2:8.38-1
ii  perl-modules-5.22 [perl-modules]  5.22.1-3
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages git recommends:
ii  less 458-3+b1
ii  openssh-client [ssh-client]  1:7.1p1-6
ii  patch2.7.5-1
ii  rsync3.1.1-3

Versions of packages git suggests:
ii  gettext-base  0.19.7-2
pn  git-arch  
pn  git-cvs   
pn  git-daemon-run | git-daemon-sysvinit  
pn  git-doc   
pn  git-el
ii  git-email 1:2.6.4-1
ii  git-gui   1:2.6.4-1
ii  git-mediawiki 1:2.6.4-1
ii  git-svn   1:2.6.4-1
ii  gitk  1:2.6.4-1
pn  gitweb

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#810767: linux-image-3.16.0-4-amd64: kernel crashes with skb_under_panic when trying to use tc_mirred

[Jasper Wallace]

Package: src:linux
Version: 3.16.7-ckt20-1+deb8u2
Severity: important

Dear Maintainer,

I wanted to use traffic management and fq_codel with my solos adsl pci card and
after pokeing around online i found this guide:

https://wiki.gentoo.org/wiki/Traffic_shaping

Trying it with the 3.16.0-4-amd64 kernel panics the kernel when the:

$tc filter add dev $ext parent : protocol all u32 match u32 0 0 action 
mirred egress redirect dev $ext_ingress

line is run, see images here:

https://pointless.net/photos/id/1452475965/
https://pointless.net/photos/id/1452476173/
https://pointless.net/photos/id/1452476160/

It's possible it's the same bug as here:

http://www.spinics.net/lists/netdev/msg283931.html

but i'm not sure.

I've "fixed" this by upgrading to the 4.2 kernel from jessie-backports
(4.2.0-0.bpo.1-amd64), so it's fixed upstream, but not sure about what
would need to be patched to make it work with 3.16


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: 
product_name: 
product_version: 
chassis_vendor: 
chassis_version: 
bios_vendor: Intel Corp.
bios_version: MWPNT10N.86A.0083.2011.0524.1600
board_vendor: Intel Corporation
board_name: D525MW
board_version: AAE93082-401

** Network interface configuration:

auto lo
iface lo inet loopback

auto eth0
allow-hotplug eth0

iface eth0 inet static
address 192.168.1.1
netmask 255.255.255.0
up   ip addr add 192.168.1.3/24 dev eth0 label eth0:0
down ip addr del 192.168.1.3/24 dev eth0 label eth0:0
up   ip addr add 192.168.2.10/24 dev eth0 label eth0:0
down ip addr del 192.168.2.10/24 dev eth0 label eth0:0

iface eth0 inet6 static
address 2a01:348:82::1
netmask 64
up ip -6 route add 2a01:348:82::/48 dev lo

auto ppp0
iface ppp0 inet ppp
provider goscomb


** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a000] (rev 02)
Subsystem: Intel Corporation Device [8086:574d]
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: agpgart-intel

00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a001] (rev 02) 
(prog-if 00 [VGA controller])
Subsystem: Intel Corporation Device [8086:574d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: 
Kernel driver in use: i915

00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller [8086:27d8] (rev 01)
Subsystem: Intel Corporation Device [8086:d625]
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: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
1 [8086:27d0] (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
2 [8086:27d2] (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.2 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
3 [8086:27d4] (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
4 [8086:27d6] (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
 

Bug#810681: heimdal-clients: installing package forces krb5-user to be removed

[Russ Allbery]

Brian May  writes:

> Also note that IIRC Kereros protocol used by kftp in heimdal-clients is
> a kludge, and likely to have security issues.

My recollection is that it doesn't actually do encryption of the data
transfers, which is obviously something of a problem.  I think it only
encrypts the control channel, if that.

-- 
Russ Allbery (r...@debian.org)   

Bug#810757: how-can-i-help: sort bugs list in removals output

[Paul Wise]

Package: how-can-i-help
Version: 11
Severity: minor
Tags: newcomer

I'm diffing the daily output of `how-can-i-help --old` and I noticed
that for packages with multiple RC bugs, the output flips around, with
one bug being first on one day and then the other bug the next.
This should be easy to fix with a sort, so is suitable for a newcomer.

For example:

Today:

- - zzuf - https://tracker.debian.org/pkg/zzuf - removal on 2016-01-22 (bugs: 
#808696, #790297)
+ - zzuf - https://tracker.debian.org/pkg/zzuf - removal on 2016-01-22 (bugs: 
#790297, #808696)

Yesterday:

- - zzuf - https://tracker.debian.org/pkg/zzuf - removal on 2016-01-22 (bugs: 
#790297, #808696)
+ - zzuf - https://tracker.debian.org/pkg/zzuf - removal on 2016-01-22 (bugs: 
#808696, #790297)

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (860, 'testing-proposed-updates'), (850, 
'buildd-testing-proposed-updates'), (800, 'unstable'), (790, 
'buildd-unstable'), (700, 'experimental'), (690, 'buildd-experimental'), (500, 
'unstable-debug'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)

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

Versions of packages how-can-i-help depends on:
ii  ruby 1:2.2.4
ii  ruby-debian  0.3.9+b4
ii  ruby-json1.8.3-1+b1

how-can-i-help recommends no packages.

how-can-i-help suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#810763: python3-uno: Please add support for python3.5

[Diederik de Haas]

On Tuesday 12 January 2016 01:02:36 Mattia Rizzolo wrote:
> with that upload of python 3.5 as a default (python 3.5 is in unstable
> since a long time, actually, what changed a few hours ago is
> python-defaults) the python3.5 (part 2) transition just started.  with
> that a few packages will uninstallable, like this.
> 
> This is not a bug.  Will be fixed by a simple rebuild, probably even
> tomorrow (but most probably the day after).

Are you sure? 
This is the Depends line from 'aptitude show python3-uno':
Depends: libreoffice-core (= 1:5.0.4~rc2-2), python3 (>= 3.4~), python3 (< 
3.5), 
python3.4, libc6 (>= 2.14), libgcc1 (>= 1:3.0), libpython3.4 (>= 3.4.2), 
libstdc++6 (>= 4.8), uno-libs3 (>= 4.4.0~alpha), ure

Which to me looks like a hard dependency on python 3.4 and an explicit reject 
for python 3.5 ( python3 (< 3.5) )

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

Bug#810697: fwupdate: unowned files after purge (policy 6.8, 10.8): /var/cache/fwupdate/done

[Mario Limonciello]

Thanks, Sure thing.  I've staged something in git to clean these up.

The directory in /boot/efi isn't owned because it's possible that the
/boot/efi partition isn't mounted for some reason.  The contents of
/boot/efi/EFI/fw are written only by fwupdate as far as I'm aware.  I'll
clean up that directory during purge too.  If there ends up being a
reason this is a bad idea, please report it.

Thanks,

On 01/11/2016 05:26 AM, Andreas Beckmann wrote:
> Package: fwupdate
> Version: 0.5-1
> Severity: important
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package left unowned files on
> the system after purge, which is a violation of policy 6.8 (or 10.8):
>
> https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails
>
> Filing this as important as having a piuparts clean archive is a release
> goal since lenny.
>
> >From the attached log (scroll to the bottom...):
>
> 0m40.1s ERROR: FAIL: Package purging left files on system:
>   /boot/efi/   not owned
>   /boot/efi/EFI/   not owned
>   /boot/efi/EFI/fw/not owned
>   /var/cache/fwupdate/ owned by: fwupdate
>   /var/cache/fwupdate/done not owned
>
> I'm not exactly sure how the hierarchy under /boot/efi/
> should be handled, but the stamp file has to be cleaned up.
>
>
> cheers,
>
> Andreas



signature.asc
Description: OpenPGP digital signature

Bug#810550: grammar and indentation of unmet dependencies message

[Manuel A. Fernandez Montecelo]

2016-01-11 00:09 積丹尼 Dan Jacobson:

"MAFM" == Manuel A Fernandez Montecelo  writes:


MAFM> Adding "which" would make it longer, contradictory with the previous
MAFM> request.

But reducing those 34 blanks to just 2 would more than pay for...


Except that there are cases like (to grab some random example from
internet searches):

https://reproducible.debian.net/rb-pkg/unstable/armhf/haskell-cipher-des.html

libghc-crypto-cipher-tests-dev : Depends: libghc-hunit-dev-1.2.5.2-0c3b7 which 
is a virtual package and is not provided by any available package.

Depends: libghc-quickcheck-dev-2.7.6-8f38a 
which is a virtual package and is not provided by any available package.

Depends: libghc-base-dev-4.7.0.2-94ad8 which is 
a virtual package and is not provided by any available package.

Depends: libghc-byteable-dev-0.1.1-f5b1c which 
is a virtual package and is not provided by any available package.

Depends: libghc-bytestring-dev-0.10.4.0-788c9 
which is a virtual package and is not provided by any available package.

Depends: libghc-mtl-dev-2.1.3.1-28369 which is 
a virtual package and is not provided by any available package.

Depends: 
libghc-test-framework-dev-0.8.1.1-a3fad which is a virtual package and is not 
provided by any available package.

Depends: 
libghc-test-framework-hunit-dev-0.3.0.1-b6cf6 which is a virtual package and is 
not provided by any available package.

Depends: 
libghc-test-framework-quickcheck2-dev-0.3.0.3-30548 which is a virtual package 
and is not provided by any available package.
  



...and similar in the case of "OR" dependencies.

Ultimately, using package names as long as
"libghc-test-framework-quickcheck2-dev-0.3.0.3-30548" doesn't help at
all, and no matter what aptitude does in some cases, it is impossible to
make it nicely formatted in a vast number of cases.

In this example, it's not a problem with the versions of the provider
packages, so the alternatives ("provided by") are not shown as in your
original bug report.  But if they were, your proposal with the
alternatives indented with 2 spaces and "Depends: ..." again at 30-40
spaces would look horrible and, more importantly, *confusing*, in this
case.

If you really think about it, you proposal would also not improve
legibility and wrapping in not-very-wide terminals in the example above,
because your proposal didn't suggest any modification to this line at
all, so your suggestion would only address a relatively small subset of
cases that would go be made more readable, while making the problem
worse for other cases.

There are maybe other reasons why modifying the indentation might be
inappropriate, I didn't go in depth with this, but this simple example
of the real world just shows why a simple suggestion does not always
work and things are not so straightforward as you make them look in your
bug reports.


I simply think that these cases are unfrequent enough as to not warrant
to spend a lot of time trying to make them look nicer, when aptitude
still has so many open issues and some of much more severity or higher
occurrence.  And having >400 open bug reports doesn't help to focus at
all, that's why closing with +wontfix rather than have the bug gathering
dust for several years and ignored.

... More in general.  I think that it would be useful if you trusted the
judgement of the people maintaining the software when they say that your
suggestion is not a good idea.  We might not be right the 100% of the
time, but more often than not we are, and discussing everything to the
last detail gets a bit tiresome.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#503958: goplay: Please add functionality to search for multiplayer games

[Markus Koschany]

Hi,

Am 11.01.2016 um 22:30 schrieb Petter Reinholdtsen:
> 
> [Alexander Schmehl 2008]
>> It would be cool, if you could somehow search for multiplayer games.
> 
> I agree.  Some times I would like to look for multiplayer games to play
> with my friends, and it is hard to locate them in Debian.
> 
> I do not believe there is a debtag useful for flagging multiplayer games
> at the moment.  Perhaps such tag should be added?


Alexander has retired from Debian and I think he isn't really interested
in this bug report anymore. A "multiplayer" tag would be useful. Quite a
lot of games also mention "multiplayer" or "multi-player" capabilities
in their package descriptions. Something like that has worked for me in
the past:

aptitude search '~sgames ~dmultiplayer'
aptitude search '~sgames ~dmulti-player'

Regards,

Markus





signature.asc
Description: OpenPGP digital signature

Bug#810752: openssl s_server -www does not send a Content-Length header

[Vincent Lefevre]

Package: openssl
Version: 1.0.2e-1
Severity: normal

openssl s_server -www does not send a Content-Length header.
This can be reproduced from the test/certs directory of the
openssl source package with:

  openssl s_server -CAfile rootCA.pem -key rootCA.key -cert rootCA.pem -www

and with

  wget -S --no-check-certificate https://localhost:4433

which gives errors "The TLS connection was non-properly terminated."

According to https://savannah.gnu.org/bugs/?45792 this is not a bug
in wget (same problem with curl). A Content-Length header must be
provided.

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, 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 openssl depends on:
ii  libc62.21-6
ii  libssl1.0.2  1.0.2e-1

openssl recommends no packages.

Versions of packages openssl suggests:
ii  ca-certificates  20160104

-- no debconf information

Bug#810750: Acknowledgement (kdevelop-python: FTBFS with python3.5 and no python3.4 installed)

[Scott Kitterman]

The relevant test has been updated in git, so it may take a git snapshot to 
work with python3.5:

https://projects.kde.org/projects/extragear/kdevelop/plugins/kdev-python/repository/revisions/master/entry/parser/CMakeLists.txt

Bug#810753: override: genometools:science/optional

[Sascha Steinbiss]

Package: ftp.debian.org
Severity: normal

For some reason the genometools package has been accepted with priority extra.
I'd like to request to change the priority to optional because AFAICS it does
not depend on a package with priority extra (except faketime as a build time
dependency, which according to Policy 2.5 is acceptable). This change would
bring genometools (and the packages depending on it) in line with the general
Debian Med Policy, which prefers optional.

Bug#809459: mwparserfromhell: Please build for all supported python3 versions

[Yuvi Panda]

I can do this in 2d, but feel free to nmu too! I would appreciate it :)
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#810756: postgresql-multicorn: FTBFS due to update needed for postgresql 9.5

[Scott Kitterman]

Package: postgresql-multicorn
Version: 1.2.4-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

See the build log [1].  Seems easy enough to fix.

Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.

Scott K

[1] 
https://buildd.debian.org/status/fetch.php?pkg=postgresql-multicorn=amd64=1.2.4-1%2Bb1=1452554715

Bug#765180: python3-argcomplete: Add binary helpers

[Paul Wise]

On Mon, 13 Oct 2014 21:45:09 +0200 Tshepang Lekhonkhobe wrote:

> I'm referring to stuff like:
> 
> - /usr/bin/activate-global-python-argcomplete
> - /usr/bin/register-python-argcomplete
> 
> These things are available in the Python 2 version of the package.

I'd like to second this request. I'm writing Python 3 code and want to
avoid having to use Python 2 to generate completions.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#810758: RM: ardour [kfreebsd-amd64 kfreebsd-i386] -- ROM; commercial restriction

[Sebastian Ramacher]

Package: ftp.debian.org
Severity: normal

Please remove the out-of-date binary package ardour on kfreebsd-amd64 and
kfreebsd-i386. They contain code that with a commercial restriction (see
#810754) for details.

dak rm -Rn -b ardour -a kfreebsd-amd64,kfreebsd-i386 complained about broken
reverse dependencies from the same source package which are all transitional
arch: all packages.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#810762: debuild: shouldn't call dpkg-architecture for source-only builds

[Neil Mayhew]

Package: devscripts
Version: 2.15.9
Severity: normal
Tags: patch

I'm using debuild -S to create a source package. debuild calls
dpkg-architecture, which in turn tries to call gcc and shows an error.
I shouldn't need gcc to build a source package.

The variables set by dpkg-architecture aren't used in a sourceonly build, so
the call to dpkg-architecture should be inside the block that uses its
results.

See attached patch.

-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
DSCVERIFY_KEYRINGS=~/.gnupg/pubring.gpg
DEBSIGN_KEYID=$DEBEMAIL
DEBUILD_LINTIAN_OPTS="-I --show-overrides"
DEBUILD_PRESERVE_ENVVARS=http_proxy,no_proxy
DEBCHANGE_PRESERVE=yes

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

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

Versions of packages devscripts depends on:
ii  dpkg-dev 1.18.4
ii  libc62.21-6
ii  perl 5.22.1-3
ii  python3  3.4.3-7
pn  python3:any  

Versions of packages devscripts recommends:
ii  at  3.1.18-2
ii  curl7.46.0-1
ii  dctrl-tools 2.24-1
ii  debian-keyring  2015.11.30
ii  dput0.9.6.4
ii  equivs  2.0.9+nmu1
ii  fakeroot1.20.2-1
ii  file1:5.25-2
ii  gnupg   1.4.20-1
ii  libdistro-info-perl 0.14
ii  libencode-locale-perl   1.05-1
ii  libjson-perl2.90-1
ii  liblwp-protocol-https-perl  6.06-2
ii  libsoap-lite-perl   1.19-1
ii  liburi-perl 1.69-1
ii  libwww-perl 6.15-1
ii  lintian 2.5.39.1
ii  man-db  2.7.5-1
ii  patch   2.7.5-1
ii  patchutils  0.3.4-1
ii  python3-debian  0.1.27
ii  python3-magic   1:5.25-2
ii  sensible-utils  0.0.9
ii  strace  4.10-3
ii  unzip   6.0-20
ii  wdiff   1.2.2-1+b1
ii  wget1.17.1-1
ii  xz-utils5.1.1alpha+20120614-2.1

Versions of packages devscripts suggests:
ii  bsd-mailx [mailx]8.1.2-0.20150408cvs-1
ii  build-essential  11.7
pn  cvs-buildpackage 
pn  debbindiff   
pn  devscripts-el
pn  gnuplot  
ii  gpgv 1.4.20-1
ii  libauthen-sasl-perl  2.1600-1
ii  libfile-desktopentry-perl0.22-1
ii  libnet-smtp-ssl-perl 1.03-1
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
pn  libyaml-syck-perl
ii  mutt 1.5.24-1
ii  openssh-client [ssh-client]  1:7.1p1-5
ii  svn-buildpackage 0.8.5+nmu1
ii  w3m  0.5.3-26

-- no debconf information
>From 30c8bf741fe0eee1309ff74463314a00e4b0846a Mon Sep 17 00:00:00 2001
From: Neil Mayhew 
Date: Mon, 11 Jan 2016 17:15:41 -0700
Subject: [PATCH] Don't call dpkg-architecture unless it's necessary

---
 scripts/debuild.pl | 37 +++--
 1 file changed, 19 insertions(+), 18 deletions(-)

diff --git a/scripts/debuild.pl b/scripts/debuild.pl
index 5776198..bacc39e 100755
--- a/scripts/debuild.pl
+++ b/scripts/debuild.pl
@@ -957,24 +957,7 @@ if ($command_version eq 'dpkg') {
 # results $pkg and $version
 # mustsetvar maintainer is only needed for signing, so we leave that
 # to debsign or dpkg-sig
-# Call to dpkg-architecture to set DEB_{BUILD,HOST}_* environment
-# variables
-my @dpkgarch = 'dpkg-architecture';
-if ($targetarch) {
-	push @dpkgarch, "-a${targetarch}";
-}
-if ($targetgnusystem) {
-	push @dpkgarch, "-t${targetgnusystem}";
-}
-push @dpkgarch, '-f';
-
-my $archinfo;
-spawn(exec => [@dpkgarch],
-	  to_string => \$archinfo,
-	  wait_child => 1);
-foreach (split /\n/, $archinfo) {
-	/^(.*)=(.*)$/ and $ENV{$1} = $2;
-}
+# Set architecture
 
 # We need to do the arch, pv, pva stuff to figure out
 # what the changes file will be called,
@@ -984,6 +967,24 @@ if ($command_version eq 'dpkg') {
 } elsif ($binarytarget eq 'binary-indep') {
 	$arch = 'all';
 } else {
+	# Call dpkg-architecture to set DEB_{BUILD,HOST}_* environment
+	# variables
+	my @dpkgarch = 'dpkg-architecture';
+	if ($targetarch) {
+	push @dpkgarch, "-a${targetarch}";
+	}
+	if ($targetgnusystem) {
+	push @dpkgarch, "-t${targetgnusystem}";
+	}
+	push @dpkgarch, '-f';
+
+	my $archinfo;
+	spawn(exec => [@dpkgarch],
+	  to_string => \$archinfo,
+	  wait_child => 1);

Bug#810748: dracut: jessie version does not mount /usr

[Nis Martensen]

Package: dracut
Version: 040+1-1
Severity: important

In split-/usr configurations, when dracut switches root from the initrd
to /sysroot, it must already have mounted sysroot/usr before. Otherwise
systemd will be unable to read /etc/os-release (which is a symlink to
.../usr/lib/os-release) and refuse to boot.

If I read the documentation correctly, dracut is supposed to
automatically mount sysroot/usr before switching root. However, this
does not happen on my system. To be able to boot, I had to drop a copy
of /usr/lib/os-release into /etc. Do I need to tell dracut explicitly
that it should mount /usr? If so, how?

Thanks!

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

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

Versions of packages dracut depends on:
ii  console-setup  1.123
ii  cpio   2.11+dfsg-4.1
ii  kmod   18-3
ii  kpartx 0.5.0-6+deb8u1
ii  libc6  2.19-18+deb8u1
ii  pkg-config 0.28-1
ii  udev   215-17+deb8u2
ii  util-linux 2.25.2-6

Versions of packages dracut recommends:
ii  cryptsetup  2:1.6.6-5
pn  dmraid  
ii  dmsetup 2:1.02.90-2.2
pn  lvm2
pn  mdadm   

Versions of packages dracut suggests:
pn  dracut-network  

-- no debconf information
+ cat /lib/dracut/dracut-040-207-g7252cde
dracut-040-207-g7252cde
+ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=a1d788f9-e4ed-4fa5-9512-cf820455e9be ro quiet
+ '[' -f /etc/cmdline ']'
+ for _i in '/etc/cmdline.d/*.conf'
+ '[' -f '/etc/cmdline.d/*.conf' ']'
+ break
+ cat /proc/self/mountinfo
0 0 0:1 / / rw shared:1 - rootfs rootfs rw
14 0 0:14 / /sys rw,nosuid,nodev,noexec,relatime shared:2 - sysfs sysfs rw
15 0 0:3 / /proc rw,nosuid,nodev,noexec,relatime shared:7 - proc proc rw
16 0 0:5 / /dev rw,nosuid shared:8 - devtmpfs devtmpfs 
rw,size=1012840k,nr_inodes=253210,mode=755
17 14 0:15 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:3 - 
securityfs securityfs rw
18 16 0:16 / /dev/shm rw,nosuid,nodev shared:9 - tmpfs tmpfs rw
19 16 0:11 / /dev/pts rw,nosuid,noexec,relatime shared:10 - devpts devpts 
rw,gid=5,mode=620,ptmxmode=000
20 0 0:17 / /run rw,nosuid,nodev shared:11 - tmpfs tmpfs rw,mode=755
21 20 0:18 / /run/lock rw,nosuid,nodev,noexec,relatime shared:12 - tmpfs tmpfs 
rw,size=5120k
22 14 0:19 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:4 - tmpfs tmpfs 
ro,mode=755
23 22 0:20 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:5 - 
cgroup cgroup 
rw,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd
24 14 0:21 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:6 - pstore 
pstore rw
25 22 0:22 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:13 - 
cgroup cgroup rw,cpuset
26 22 0:23 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime 
shared:14 - cgroup cgroup rw,cpu,cpuacct
27 22 0:24 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:15 - 
cgroup cgroup rw,devices
28 22 0:25 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:16 - 
cgroup cgroup rw,freezer
29 22 0:26 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime 
shared:17 - cgroup cgroup rw,net_cls,net_prio
30 22 0:27 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:18 - 
cgroup cgroup rw,blkio
31 22 0:28 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime 
shared:19 - cgroup cgroup rw,perf_event
32 0 8:3 / /sysroot ro,relatime shared:20 - ext3 /dev/sda3 ro,data=ordered
+ cat /proc/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,nosuid,size=1012840k,nr_inodes=253210,mode=755 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup 
rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd
 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup 
rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup 
rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 

Bug#797702: ITP: grafana -- feature rich metrics dashboard and graph editor

[Dmitry Smirnov]

Hi Richard,

Whenever possible please maintain meaningful subject. :)


On Mon, 11 Jan 2016 02:55:19 PM you wrote:
> it seems all dependencies have been packaged.

Actually we need to take care of go-macaron packages:

http://whiteboard.debian.net/grafana.wb


It is a little bit tricky due to namespace problems but I already have 
unfinished draft of the packaging.


> Is there still a blocking issue anywhere?

Mostly lack of time, funding and other priorities on my side...


> FWIW, I can sponsor packages.

That's very nice but Alexandre have been accepted as DD recently so we should 
be fine. :)

-- 
Regards,
 Dmitry Smirnov.

---

Moral courage is the most valuable and usually the most absent
characteristic in men.
-- George S. Patton


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

Bug#810591: imagemagick:i386 not configured because /usr/bin/compare-im6 doesn't exist

[Vincent Fourmond]

[don't forget to keep 810...@bugs.debian.org in CC when you reply, we want
the information to be public]


On Mon, Jan 11, 2016 at 11:27 PM, Guy Durrieu 
wrote:

> Le 11/01/2016 22:52, Vincent Fourmond a écrit :
>
>> tag 810591 +moreinfo
>> thanks
>>
>>   Hello,
>>
>>   I'm very puzzled by this bug, since, clearly, compare-im6 exists in the
>> package:
>>
>> dpkg-deb -c imagemagick_6.8.9.9-6+b1_i386.deb | grep compare
>> -rw-r--r-- root/root  1745 2015-12-18 11:40
>> ./usr/share/man/man1/compare-im6.1.gz
>> lrwxrwxrwx root/root 0 2015-12-18 11:40 ./usr/bin/compare-im6 ->
>> ../lib/i386-linux-gnu/ImageMagick-6.8.9/bin-Q16/compare
>>
>>   And it points to a valid symlink (as long as the imagemagick-6.q16
>> package is installed, but as the former depends on the latter, it should
>> always be)...
>>
>>  dpkg-deb -c imagemagick-6.q16_6.8.9.9-6+b1_i386.deb | grep compare
>> -rwxr-xr-x root/root  5636 2015-12-18 11:40
>> ./usr/lib/i386-linux-gnu/ImageMagick-6.8.9/bin-Q16/compare
>>
>>   Can you describe what did you do more precisely ? Can you reinstall
>> imagemagick-6.q16 ? What does
>>
>> ls -l /usr/bin/compare-im6
>>
>> say ?
>>
>>   Cheers,
>>
>>   Vincent
>>
>>
> Hello,
>
> Thanks for your answer.
>
> The error appeared while performing aptitude full-upgrade (thus upgrading
> ImageMagick).
>
>
>
>  ls -l /usr/bin/compare-im6 gives
>
> lrwxrwxrwx 1 root root 55 déc.  18 11:40 /usr/bin/compare-im6 ->
> ../lib/i386-linux-gnu/ImageMagick-6.8.9/bin-Q16/compare
>
> but ImageMagick-6.8.9/bin-Q16/compare doesn't exist within
> /usr/lib/i386-linux-gnu...
>
> and I get the same error messages after reinstalling imagemagick-6.q16:
>
> (Sorry, the script is in french)
>
> ---
> (Lecture de la base de données... 363500 fichiers et répertoires déjà
> installés.)
> Préparation du dépaquetage de
> .../imagemagick-6.q16_8%3a6.8.9.9-6+b1_amd64.deb ...
> Dépaquetage de imagemagick-6.q16 (8:6.8.9.9-6+b1) sur (8:6.8.9.9-6+b1) ...
> Traitement des actions différées (« triggers ») pour mime-support (3.59)
> ...
> Traitement des actions différées (« triggers ») pour gnome-menus
> (3.13.3-6) ...
> Traitement des actions différées (« triggers ») pour desktop-file-utils
> (0.22-1) ...
> Traitement des actions différées (« triggers ») pour hicolor-icon-theme
> (0.13-1) ...
> Paramétrage de imagemagick-6.q16 (8:6.8.9.9-6+b1) ...
> Paramétrage de imagemagick:i386 (8:6.8.9.9-6+b1) ...
> update-alternatives: erreur: le chemin alternatif /usr/bin/compare-im6
> n'existe pas
> dpkg: erreur de traitement du paquet imagemagick:i386 (--configure) :
>  le sous-processus script post-installation installé a retourné une erreur
> de sortie d'état 2
> ---
>

  I'm getting more and more confused, this really shouldn't happen, since
imagemagick-6.q16 should be properly unpacked when it reaches the
configuration step...

  Before anything else, what does this tell you ?

dpkg -L imagemagick-6.q16

  Can you try using apt upgrade instead of aptitude ? (maybe aptitude is
getting confused at some point).

  Cheers,

  Vincent

Bug#810751: luarocks uses unzip but doesn't depend on it

[Neil Mayhew]

Package: luarocks
Version: 2.2.0+dfsg-2
Severity: normal

1. Install luarocks in a minimal system (eg a basic docker container)
   with --no-install-recommends

2. Try to install a rock

It fails with:

> sh: 1: unzip: not found
>
> Error: Failed unpacking rock file: /tmp/luarocks_luarocks-rock-...

The package depends specify zip but not unzip. However, unzip is an indirect
dependency of the recommended packages, so it usually gets installed and this
is presumably why the problem hasn't been noticed before.

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

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

Versions of packages luarocks depends on:
ii  liblua5.1-0-dev [liblua5.1-dev]  5.1.5-8
ii  lua5.1   5.1.5-8
ii  wget 1.17.1-1
ii  zip  3.0-11

luarocks recommends no packages.

luarocks suggests no packages.

-- no debconf information

Bug#809287: python-websockets: FTBFS: AssertionError: 1006 != 1005

[Piotr Ożarowski]

Source: python-websockets
Source-Version: 3.0-1

I forgot to close it in the changelog

Bug#744170: Bug in openssl

[Vincent Lefevre]

According to upstream, it actually seems to be a bug in openssl,
which doesn't send a Content-Length header. I've reported it:

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

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#809561: jessie-pu: package perl/5.20.2-3+deb8u2

[Dominic Hargreaves]

Control: retitle -1 jessie-pu: package perl/5.20.2-3+deb8u3

On Fri, Jan 01, 2016 at 04:16:32PM +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Fri, 2016-01-01 at 14:03 +, Dominic Hargreaves wrote:
> > Please find attached a proposed patch for #798727 in perl, which I would
> > like to include in an upload to stable. The same issues has already
> > been fixed for libencode-perl in s-p-u (see #807828).
> 
> Please go ahead.

Thanks, uploaded (with a delay for 5.20.2-3+deb8u2 to be released
as a security update).

Cheers,
Dominic.

Bug#697088: ebtables plugin for netfilter-persistent

[Ricardo Manriquez]

I just tried your script and it works well, it has a small typo at line 61,
should be ebtables instead of ebtable, also if you use it don't forget to
"chmod +x" it!

Have attached the corrected version for the lazy bunch.

Thank you very much Rik, best regards!

Ricardo Manriquez

On Sun, 10 Jan 2016 20:01:38 +0100 Rik Snel  wrote:
> Dear all,
>
> I have attached a simple ebtables plugin for
> netfilter-persistent. Just put it in
> /usr/share/netfilter-persistent/plugins.d
> and create /etc/ebtables/
>
> Greetings,
>
> Rik.
>
> --
> Nothing is ever a total loss; it can always serve as a bad example.


35-ebtables
Description: Binary data

Bug#810763: python3-uno: Please add support for python3.5

[Mattia Rizzolo]

On Tue, Jan 12, 2016 at 02:11:44AM +0100, Diederik de Haas wrote:
> Are you sure?

yes

> This is the Depends line from 'aptitude show python3-uno':
> Depends: libreoffice-core (= 1:5.0.4~rc2-2), python3 (>= 3.4~), python3 (< 
> 3.5), 
> python3.4, libc6 (>= 2.14), libgcc1 (>= 1:3.0), libpython3.4 (>= 3.4.2), 
> libstdc++6 (>= 4.8), uno-libs3 (>= 4.4.0~alpha), ure
> 
> Which to me looks like a hard dependency on python 3.4 and an explicit reject 
> for python 3.5 ( python3 (< 3.5) )

that dependecy is genereted automatically at build time.
Actually only libroffice-core is the manually instated dependency, as
you can see from the source control file:

Depends: libreoffice-core (= ${binary:Version}),
 ${misc:Depends},
 ${python3:Depends},
 ${shlibs:Depends}


A rebuild will be scheduled soon.  It's the normal process of
transitions.  You can check on the status on
https://release.debian.org/transitions/html/python3.5.html (updated
twice a day, IIRC).
Looking at it I find weird it has not been scheduled already, actually,
but I'm pretty sure sure it'll be soon.

-- 
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#810763: python3-uno: Please add support for python3.5

[Diederik de Haas]

On Tuesday 12 January 2016 01:19:16 Mattia Rizzolo wrote:
> > Are you sure?
> yes

Ok, thanks :-)

> that dependecy is genereted automatically at build time.
> Actually only libroffice-core is the manually instated dependency, as
> you can see from the source control file:

Will (try to) check that too next time.

> Depends: libreoffice-core (= ${binary:Version}),
>  ${misc:Depends},
>  ${python3:Depends},
>  ${shlibs:Depends}

I don't really understand what that translate into, but indeed there is no 
versioned dependency.

Thanks for the quick response :-)

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

Bug#810749: grive: Crash at first synchronisation: runtime exception

[Damien Couroussé]

Package: grive
Version: 0.2.0-1.1+b2
Severity: normal

hello,

the first synchronisation crashes as follows:

$ grive -a
---
Please go to this URL and get an authentication code:

[hidden]

---
Please input the authentication code here:
[hidden]
Reading local directories
Synchronizing folders
exception: /build/grive-7dwD69/grive-0.2.0/libgrive/src/http/CurlAgent.cc(149):
Throw in function long int gr::http::CurlAgent::ExecCurl(const string&,
gr::http::Receivable*, const gr::http::Header&)
Dynamic exception type: N5boost16exception_detail10clone_implIN2gr4http5ErrorEEE
std::exception::what: std::exception
[PN2gr4expt6MsgTagE] =
[PN2gr4http11CurlCodeTagE] = 0
[PN2gr4http15HttpResponseTagE] = 400
[PN2gr4http6UrlTagE] =
https://docs.google.com/feeds/default/private/full/-/folder?max-results=50=true
[PN2gr4http9HeaderTagE] = Authorization: Bearer
GData-Version: 3.0




-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'stable-updates'), (480, 'testing'), (200, 
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-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)

Versions of packages grive depends on:
ii  libboost-filesystem1.55.0   1.55.0+dfsg-3
ii  libboost-program-options1.55.0  1.55.0+dfsg-3
ii  libboost-system1.55.0   1.55.0+dfsg-3
ii  libc6   2.19-18+deb8u1
ii  libcurl3-gnutls 7.38.0-4+deb8u2
ii  libexpat1   2.1.0-6+deb8u1
ii  libgcc1 1:4.9.2-10
ii  libgcrypt20 1.6.3-2
ii  libjson-c2  0.11-4
ii  libstdc++6  4.9.2-10

grive recommends no packages.

grive suggests no packages.

-- no debconf information

Bug#809225: Nice way to solve bugs and segfaults

[Mehdi Dogguy]

Bonjour,

On 11/01/2016 08:39, Nathael Pajani wrote:
> Hi !
> 
> What a nice way to resolve a bug or segfault. None of my students
> ever tried this one yet.
> 
> Should remember it next time someone requests tech support for one of
> my products.
> 

I am not sure this message helps anything in any way. I can certainly
understand your frustration. I am not convinced this reaction can make
things moving forward. Instead, let's focus on the core issue.

AFAIK, older versions of Unison cannot work with OCaml 4.02. The latter
has been uploaded last October and we've transitioned all the OCaml stack
to 4.02.3. Since we don't support multiple version of OCaml in the same
archive, older versions of Unison had to be removed since they became
useless. Stéphane could have invested some time to backport necessary
changes to make them work with OCaml 4.02.3. Unfortunately, this requires
quite some work and was not worth trying.

The remaining issue is the situation of users of mixed machines stable/testing.
We are working on a solution for them and we are quite confident to get this
sorted out. The solution will probably land debian-backports and will be
announced on this list. So stay tuned!

In the meantime, he are the few working solutions that have been mentioned
by some users:
1) Copy needed binaries on systems you want to synchronize with.
2) Install Unison's packages from Jessie, and not use Stretch's ones.

If you encountering an issue that is not covered by what I've described, please
do share it with us so that we can try to help you.

> 
> Have fun.
> 

Likewise.

Kind regards,

-- 
Mehdi

Bug#810760: jessie-pu: package stk/4.4.4-5

[Felipe Sateler]

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

This fixes bug 805549 in jessie. This bug makes the dev package useless
in certain conditions.

Package is already uploaded to p-u, diff is attached.

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

Kernel: Linux 4.3.0-1-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)
diff --git a/debian/changelog b/debian/changelog
index 258ec0c..2a73017 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+stk (4.4.4-5+deb8u1) jessie; urgency=medium
+
+  [ Hanno Zulla ]
+  * Install missing SKINI.{msg,tbl} include files
+
+ -- Felipe Sateler   Fri, 18 Dec 2015 16:33:16 -0300
+
 stk (4.4.4-5) unstable; urgency=medium
 
   * Prepare for new rtaudio and rtmidi
diff --git a/debian/gbp.conf b/debian/gbp.conf
index cec628c..0e268a7 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,2 +1,3 @@
 [DEFAULT]
 pristine-tar = True
+debian-branch = debian/jessie
diff --git a/debian/patches/01-makefile.patch b/debian/patches/01-makefile.patch
index 3452268..7fb1106 100644
--- a/debian/patches/01-makefile.patch
+++ b/debian/patches/01-makefile.patch
@@ -64,7 +64,7 @@ Forwarded: no
  
 +install-headers:
 +	install -d $(DESTDIR)/usr/include/stk
-+	cp -r ../include/*.h $(DESTDIR)/usr/include/stk
++	cp -r ../include/* $(DESTDIR)/usr/include/stk
 +
 +install: $(SHAREDLIB) install-headers
 +	install -d  $(DESTDIR)/usr/share/stk
diff --git a/debian/rules b/debian/rules
index 4096934..b309804 100755
--- a/debian/rules
+++ b/debian/rules
@@ -34,6 +34,9 @@ override_dh_auto_configure:
 	mkdir -p src/Release
 	mkdir -p projects/demo/Release
 
+override_dh_auto_install:
+	dh_auto_install
+	rm -f debian/tmp/usr/include/stk/*.bak
 
 override_dh_link:
 	dh_link

Bug#809225: Nice way to solve bugs and segfaults

[Nathael Pajani]

Hi,

On 11/01/2016 23:41, Mehdi Dogguy wrote:
> let's focus on the core issue.
You're right, thanks for putting us back on tracks.


> AFAIK, older versions of Unison cannot work with OCaml 4.02. The latter
> has been uploaded last October and we've transitioned all the OCaml stack
> to 4.02.3. Since we don't support multiple version of OCaml in the same
> archive, older versions of Unison had to be removed since they became
> useless. Stéphane could have invested some time to backport necessary
> changes to make them work with OCaml 4.02.3. Unfortunately, this requires
> quite some work and was not worth trying.

I think that it should be nice to get a unison2.32.52 update which displays a 
message to
the user during upgrade, so that he knows that there is a known problem, and 
that the
solution is a migration to a newer version, with a few choices like "do nothing 
yet",
"migrate my repos to the new version", "install new unison but do not touch the 
repos".

Unison craches, removing the package from Debian servers does not solve the 
crash : the
old package will be kept, and Unison still crashes.
Using a new version does not work, as the data format for the repos are not 
compatible, so
not a solution either.


> The remaining issue is the situation of users of mixed machines 
> stable/testing.
> We are working on a solution for them and we are quite confident to get this
> sorted out. The solution will probably land debian-backports and will be
> announced on this list. So stay tuned!

Nice. A script to migrate the repo data to the new format might be good too, to 
prevent
having to backport things forever.

Anyway, due to the reply I got when I tried to contribute, I choosed a solution 
on my own,
which does not imply using Debian packaging system, and is not reproductible to 
others.
This results in time lost for everyone, as I have a working solution now, and 
will not
help working on a solution for this problem anymore.


> In the meantime, he are the few working solutions that have been mentioned
> by some users:
> 1) Copy needed binaries on systems you want to synchronize with.

I tried this, it did not work.

> 2) Install Unison's packages from Jessie, and not use Stretch's ones.
I think I tried to use the binary from the server on both side, but it was not 
linked to
the right libs, so not a solution either.
And as for the package themselves, I encountered dependency problems.


> If you encountering an issue that is not covered by what I've described, 
> please
> do share it with us so that we can try to help you.
I had to solve the problem on my own, which means I do not have a test system 
anymore. you
are on your own too on this problem now.
Sorry.


+++


-- 
Nathaël PAJANI - ED3L - Techno-Innov
Internet : http://www.ed3l.fr - http://www.techno-innov.fr

Bug#810761: wheezy-pu: package stk/4.4.3-2

[Felipe Sateler]

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

This update fixes bug 805549 on wheezy. This bug makes the dev package
useless for certain uses. Package is uploaded to p-u, diff is attached.


Saludos

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

Kernel: Linux 4.3.0-1-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)
diff --git a/debian/changelog b/debian/changelog
index 1b2036a..820f37b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+stk (4.4.3-2+deb7u1) wheezy; urgency=medium
+
+  [ Hanno Zulla ]
+  * Install missing SKINI.{msg,tbl} include files
+
+ -- Felipe Sateler   Fri, 18 Dec 2015 16:41:38 -0300
 stk (4.4.3-2) unstable; urgency=low
 
   [ Felipe Sateler ]
diff --git a/debian/gbp.conf b/debian/gbp.conf
index cec628c..d3f1da8 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,2 +1,4 @@
 [DEFAULT]
 pristine-tar = True
+debian-branch = debian/wheezy
+
diff --git a/debian/patches/01-makefile.patch b/debian/patches/01-makefile.patch
index 26fa351..db34483 100644
--- a/debian/patches/01-makefile.patch
+++ b/debian/patches/01-makefile.patch
@@ -64,7 +64,7 @@ Forwarded: no
  
 +install-headers:
 +	install -d $(DESTDIR)/usr/include/stk
-+	cp -r ../include/*.h $(DESTDIR)/usr/include/stk
++	cp -r ../include/* $(DESTDIR)/usr/include/stk
 +
 +install: $(SHAREDLIB) install-headers
 +	install -d  $(DESTDIR)/usr/share/stk
diff --git a/debian/rules b/debian/rules
index f6a9bb8..809929b 100755
--- a/debian/rules
+++ b/debian/rules
@@ -21,6 +21,10 @@ override_dh_auto_configure:
 	dh_auto_configure -- $(CONFIGURE_FLAGS)
 	mkdir -p src/Release
 
+override_dh_auto_install:
+	dh_auto_install
+	rm -f debian/tmp/usr/include/stk/*.bak
+
 override_dh_installchangelogs:
 	dh_installchangelogs doc/ReleaseNotes.txt
 

Bug#810765: ardour: FTBFS[!linux]: depends on cwiid, alsa

[Steven Chamberlain]

Package: ardour
Version: 1:4.4~dfsg-1
Severity: normal
Tags: patch

Hi,

ardour has become BD-Uninstallable on kfreebsd and hurd due to
Build-Depends:
  - cwiid, which is linux-specific;
  - libasound2-dev, which is linux-specific (although kfreebsd has
a compatibility wrapper around OSS, I think it will be inadequate
for ardour's purposes;  better to use JACK instead).

Please find attached patch adjusting the build-dependencies, and also
to only enable the ALSA backend on Linux.

(p.s. `BACKENDS+=,alsa` might have looked neater, but doesn't work)

Thanks!

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

Kernel: kFreeBSD 10.1-0-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru a/debian/control b/debian/control
--- a/debian/control	2015-10-20 12:44:27.0 +0100
+++ b/debian/control	2016-01-12 00:29:26.813611864 +
@@ -26,12 +26,12 @@
  libsigc++-2.0-dev (>= 2.2.10),
  uuid-dev,
  libxml2-dev (>= 2.5.7),
- libcwiid-dev,
+ libcwiid-dev [linux-any],
  libcairomm-1.0-dev (>= 1.10.0),
  libgtkmm-2.4-dev (>= 2.24.2),
  libpangomm-1.4-dev (>= 2.28.4),
  ladspa-sdk (>= 1.1-2),
- libasound2-dev (>= 0.9.4),
+ libasound2-dev (>= 0.9.4) [linux-any],
  libaubio-dev (>= 0.3.2),
  libjack-dev,
  liblo-dev (>= 0.26~),
diff -Nru a/debian/rules b/debian/rules
--- a/debian/rules	2015-10-20 12:44:27.0 +0100
+++ b/debian/rules	2016-01-12 00:29:13.954613461 +
@@ -44,6 +44,12 @@
 	DIST_TARGET = x86_64
 endif
 
+BACKENDS = jack
+ifneq (,$(findstring linux,$(DEB_HOST_ARCH_OS)))
+	# ALSA Backend is only available on Linux
+	BACKENDS = jack,alsa
+endif
+
 LD_LIBRARY_PATH += :$(DEB_DESTDIR)/usr/lib/ardour4/
 
 waf-configure-options = --lv2 \
@@ -52,7 +58,7 @@
 	--configdir=/etc/ \
 	--noconfirm \
 	--prefix=/usr/ \
-	--with-backends=jack,alsa \
+	--with-backends=$(BACKENDS) \
 	--no-phone-home \
 	--use-external-libs \
 	--dist-target=$(DIST_TARGET) \

Bug#810764: RFP: libclassindex-java -- a run-time annotation scanning library for Java

[Gioele Barabucci]

Package: wnpp
Severity: wishlist
Control: block 742119 by -1

* Package name: libclassindex-java
  Version : 3.4
  Upstream Author : Sławek Piotrowski
* URL : https://github.com/atteo/classindex
* License : Apache License 2
  Programming Lang: Java
  Description : a run-time annotation scanning library for Java

>From the homepage:

> ClassIndex is a much quicker alternative to every run-time annotation
> scanning library like Reflections or Scannotations.
>
> ClassIndex consist of two parts:
>
> 1. An annotation processor which at compile-time generates an index of
>classes implementing given interface, classes annotated by given
>annotation or placed in a common package. Thanks to automatic
>discovery the processor will be automatically executed when
>classindex.jar is added to the classpath.
>
> 2. Run-time API to read the content of generated indexes.

ClassIndex is a required dependency of XML Calabash (ITP:
)

Bug#810591: imagemagick:i386 not configured because /usr/bin/compare-im6 doesn't exist

[Vincent Fourmond]

tag 810591 +moreinfo
thanks

  Hello,

  I'm very puzzled by this bug, since, clearly, compare-im6 exists in the
package:

dpkg-deb -c imagemagick_6.8.9.9-6+b1_i386.deb | grep compare
-rw-r--r-- root/root  1745 2015-12-18 11:40
./usr/share/man/man1/compare-im6.1.gz
lrwxrwxrwx root/root 0 2015-12-18 11:40 ./usr/bin/compare-im6 ->
../lib/i386-linux-gnu/ImageMagick-6.8.9/bin-Q16/compare

  And it points to a valid symlink (as long as the imagemagick-6.q16
package is installed, but as the former depends on the latter, it should
always be)...

 dpkg-deb -c imagemagick-6.q16_6.8.9.9-6+b1_i386.deb | grep compare
-rwxr-xr-x root/root  5636 2015-12-18 11:40
./usr/lib/i386-linux-gnu/ImageMagick-6.8.9/bin-Q16/compare

  Can you describe what did you do more precisely ? Can you reinstall
imagemagick-6.q16 ? What does

ls -l /usr/bin/compare-im6

say ?

  Cheers,

  Vincent



On Sun, Jan 10, 2016 at 9:47 AM, Guy Durrieu 
wrote:

> Package: imagemagick:i386
> Version: 8:6.8.9.9-6+b1
>
> Dear Maintainer,
>
> Since a while now, a get the following error when running aptitude:
>
> Setting up imagemagick:i386 (8:6.8.9.9-6+b1) ...
> update-alternatives: error: alternative path /usr/bin/compare-im6 doesn't
> exist
> dpkg: error processing package imagemagick:i386 (--configure):
>  subprocess installed post-installation script returned error exit status 2
>
> Additionnally:
>  cups-filters
>  cups
>  printer-driver-hpcups
>  hplip
>  printer-driver-postscript-hp
>
> which apparently depend on imagemagick:i386 cannot be correctly configured
>
> Thanks in advance for your help
>
>
>
> -- Package-specific info:
> ImageMagick program version
> ---
> animate: compare: convert: composite: conjure: display: identify: import:
> mogrify: montage: stream:
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers proposed-updates
>   APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.3.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)
>
> Versions of packages imagemagick depends on:
> ii  imagemagick-6.q16  8:6.8.9.9-6+b1
>
> imagemagick recommends no packages.
>
> imagemagick suggests no packages.
>
> -- no debconf information
>
>

Bug#807463: RFS: pnmixer/0.6.1-1 [ITP] -- Simple mixer application for system tray

[Gianfranco Costamagna]

control: owner -1 !
control: tags -1 moreinfo


little review:
please use autoreconf instead of autotools-dev
(dh-autoreconf and call dh --with autoreconf)

please remove all the comments from rules file
and also the two lines below
DPKG_EXPORT_BUILDFLAGS = 1
include /usr/share/dpkg/default.mk


"
* This is my first Debian package

"

this isn't so much useful in the user experience, please remove :)

remove debian/rules.dh7

please enable VCS fields


pnmixer is designed to work on systems that use ALSA for sound management.
Any other sound driver like IOSS or FFADO, or sound server like PulseAudio
or Jackd, are currently not supported (patches welcome).


seems kind of a blocker, many users are left out...


check-all-the-things review:
flawfinder -Q -c .


(lots of security issues)

cheers,

Gianfranco





Il Mercoledì 9 Dicembre 2015 5:48, Arnaud Rébillout  ha 
scritto:
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pnmixer".

Package name: pnmixer
Version : 0.6.1-1
Upstream Author : Nick Lanham, Julian Ospald, Arnaud Rébillout
URL : https://github.com/nicklan/pnmixer
License : GPL-3
Section : sound

This is my first package.

I built it carefully using `dh_make`, checked and fixed errors with
`lintian`. It took me almost two days, given the huge amount of
documentation out there :)

PNMixer is a simple mixer application for the system tray, for those
who use ALSA for sound management. It may be people who like to keep
their system simple and lightweight, or people who do MAO, therefore
using Jackd when working on their music, and simple ALSA when they're
not. I'm part of both use cases.

PNMixer integrates nicely into desktop environments that don't have
a panel that supports applets and therefore can't run a mixer applet.
In particular it's been used quite a lot with fbpanel and tint2, but
should run fine in any system tray.

PNMixer comes with plenty of options, which make it quite a complete
system tray mixer: hotkeys support, notifications, plenty of config...
This is described in details in the README.

How does it compare with other system tray ALSA mixers in Debian ?
- qasmixer is C++/Qt4, no translation
- volumeicon-alsa is C/GTk2, no translation
- volti is Python/GTk2, translated in 5 languages

PNMixer is C/GTk3, translated in 4 languages.

It has been around for almost 5 years now, and is actively maintained.
It is packaged in several distributions:

- ArchLinux: https://aur.archlinux.org/packages/pnmixer/
- Gentoo: https://packages.gentoo.org/packages/media-sound/pnmixer
- Fedora: https://apps.fedoraproject.org/packages/pnmixer

It was also the default sound mixer in Crunchbang, a Debian-derived
distribution that is known as BunsenLabs now. There's also an unofficial
package for Ubuntu.

I'm one of the maintainers of PNMixer, so yes, I'm advertising a little
bit here :)

However, before being a maintainer, I was a PNMixer user, because it was
definitely the best system tray ALSA mixer around. I sincerely believe
that it's a valuable piece of software, and that Debian users can
benefit from it.

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

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

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

dget -x 
http://mentors.debian.net/debian/pool/main/p/pnmixer/pnmixer_0.6.1-1.dsc

Best regards,

Arnaud Rébillout



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

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

Bug#700045: linphone: account wizard rejects user names starting with a digit (required by sipgate)

[Michael Stapelberg]

Hi Helmut,

Helmut Grohne  writes:
> Start linphone. Click "Options", select "Preferences". Select tab
> "Manage SIP Accounts". Click the "Wizard" button. Click "Forward".
> Select "I have already a sip account ...". Click "Forward". Enter
> arbitray 6 digits into the username field. Enter an arbitrary non-empty
> character sequence into the password field. Enter a valid domain (such
> as "sipgate.com") into the domain field.
>
> Expected behaviour: The "Apply" button would be clickable.
> Observed behaviour: The "Apply" button is not clickable.
>
> Further details. The acceptance of the input data seems to depend on the
> value in the username field to start with a letter. This precludes
> sipgate users from using linphone.

I also ran into this bug.

A workaround is to prefix your sipgate username (e.g. 1234) with a
letter (e.g. a1234). Login will fail, but linphone will allow you to add
the account. Afterwards, choose Options → Preferences → Manage SIP
Accounts, select the account in question, click the Edit button, remove
the letter.

Upstream says this was fixed in 3.7.0:
https://lists.gnu.org/archive/html/linphone-users/2015-01/msg5.html

-- 
Best regards,
Michael

Bug#498067: dh_install wildcard exception mechanism request

[Gergely Nagy]

Hi!

This wishlist was recently brought to my attention, as something that
could be added via dh-exec. I have a couple of ideas for the syntax:

1) usr/bin/djview3 => usr/bin/djview3

This is the existing syntax for dh-exec-install-rename, which does a
copy behind the scenes. For this feature, it would need to do a rename.
I do not want to break existing functionality, so if I go with this
syntax, we will need a flag to tell dh-exec to do a move instead of
copy.

Something like -Oinstall-rename=move or --move-files. Or, following
existing syntax: --with-scripts=install-movefiles. I am leaning towards
this last one.

2) => usr/bin/djview3

Kind of like the rename syntax, but only with the second part of it.
This is shorter, and does not need additional flags on the #! line. But
it does not allow renaming with a move. I suppose that is not
particularly important, seeing that I know of no such request.

3) A combination of both.

By default, install-movefiles would come after install-rename, thus the
latter would rewrite the src => dest form before install-move gets
there. With a --with-scripts argument, movefiles would win the race
instead.

Having dumped this here, I will go with the third option. Thank you for
listening.

-- 
|8]

Bug#634073: Svn launches kwallet

[Brainslug]

It's two years later now, but subversion 1.9.2 on Debian/stretch still
launches stupid kwallet.

+1 on setting "password-stores=" to an empty string by default.


Cheers!

Bug#810677: nmu: tarantool_1.6.7.551.ga5bafc5-1

[Andreas Beckmann]

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

nmu tarantool_1.6.7.551.ga5bafc5-1 . ANY . unstable . -m "Rebuild against 
binutils 2.25.90.20160101"

Isn't there a way to automate these binNMUs on new binutils snapshots?


Andreas

Bug#810656: ifupdown: deadlocks: A start job is running for LSB: Raise network interfaces

[Guus Sliepen]

tags 810656 + pending
thanks

On Sun, Jan 10, 2016 at 05:50:05PM -0800, Alan W. Irwin wrote:

> I was going to add this additional report to
> , but that one
> has been closed so apparently I have to start a new bug report for this
> on-going issue.

You can reopen bugs that were closed, but it's OK to open a new one.

> This fairly modest recent update made the other computer unbootable.  The
> last message in the boot sequence is
> 
> "A start job is running for LSB: Raise network interfaces. (HHh MMmin SSsec / 
> no limit)
> 
> where HH is now up to 3 (hours).  Ctrl-C doesn't break the deadlock
> and if I type ctrl-alt-del, then the boot sequence is gone through
> again until this same deadlock is reached.
[...]
> So can we have an immediate Jessie fix for that unlimited timeout at
> least? A slowly booting machine is far preferable to one that won't
> boot at all.  :-)

That's indeed a problem. The upcoming version of ifupdown will have a
timeout of 5 minutes.

> Also, could someone here give clear directions about how to get out of
> the current deadlock so I can use that other computer or is a rescue
> distro like RIP necessary to get that computer working again? Note
> again, ctrl-C has no effect and ctrl-alt-del just reboots into the
> same deadlock again.

That I actually don't know, I suspect you have to ask some systemd gurus
about how to do that.

> >From previous experience with this deadlock on my current computer, I
> suspect this deadlock was caused because of the following stanza in
> /etc/network/interfaces on the currently deadlocked system (with the
> pre-up commands commented out on my current computer to avoid the
> deadlock).
> 
> auto eth0
> iface eth0 inet dhcp
> pre-up [ -f /etc/init.d/ferm ]
> pre-up /etc/init.d/ferm start >| /tmp/ferm.out 2>&1
> 
> The point of those two pre-up commands (which I have used on Debian
> for a very long time) was to work around a slight ferm issue where the
> configured firewall is put into place by ferm after networking is up,
> and I prefer to do that before (on at least non-NFS systems like this
> one where /etc/init.d/ferm is available regardless of networking) to
> avoid that small gap in firewall coverage.
> 
> Up to today's modest update the above pre-up commands were not causing
> any trouble on that system (which has a USB stick drive rather than
> a normal HD) so I did not comment them out.
> 
> Could you advise me how to get the above ferm workaround to work on
> non-NFS systems like this one (and also my present one) without generating a 
> deadlock?

If it's ferm itself that is stuck, then you can apply a timeout to that
one, like this:

auto eth0
iface eth0 inet dhcp
pre-up timeout 1m service ferm start

The timeout command should always be installed on a Debian system, in
/usr/bin. I hope this helps.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: Digital signature

Bug#797623: opensaml2: transition needed for g++-5 ABIs

[Andreas Beckmann]

Control: block 797770 with -1

On Tue, 01 Sep 2015 10:48:28 +0200 Ferenc Wagner  wrote:
> Hi,
> 
> Thanks for the detailed report.  Right now I'm doing urgent work on HA
> packages, but once that's done, I'll package new upstream versions of
> the whole Shibboleth stack to fix the outstanding OpenSAML security bug
> in unstable.  This will change the SO version of xml-security-c and
> probably all other library packages in the stack.  Does this change the
> big picture somehow?  I don't understand the interdependencies of this
> transition.  Anyway, feel free to NMU these packages if that helps
> unblocking other stuff, just don't be too concerned about the fate of
> the current versions in unstable, expect new upstream versions after a
> couple of weeks.

A couple of months later: What's the status?


Andreas

Bug#810684: audacity: Freeze during playback

[Jerry Quinn]

Package: audacity
Version: 2.0.6-2+b3
Severity: normal

Dear Maintainer,

I have a 45 minute mp3 loaded.  I was playing bits, moving around near the
beginning and playing again.  After several times, audacity locked up hard.

I attached gdb and dumped the backtrace for each of the active threads.

jlquinn@cerberus:~/fast$ gdb -p 27627
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 27627
Reading symbols from /usr/bin/audacity...(no debugging symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libexpat.so.1...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libportaudio.so.2...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libsndfile.so.1...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_html-3.0.so.0...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libavformat-ffmpeg.so.56...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libavutil-ffmpeg.so.54...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libmp3lame.so.0...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libFLAC++.so.6...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libFLAC.so.8...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/libid3tag.so.0...(no debugging symbols
found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libmad.so.0...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libSoundTouch.so.1...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libsoxr.so.0...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libtwolame.so.0...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libvorbisenc.so.2...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libvorbisfile.so.3...(no
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libvorbis.so.0...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libogg.so.0...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libportSMF.so.0...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libsbsms.so.10...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libvamp-hostsdk.so.3...(no
debugging symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libdl.so.2...Reading symbols from
/usr/lib/debug/.build-id/4e/f0d5906cc076c075416d683c32960cca5597f5.debug...done.
done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0...Reading
symbols from
/usr/lib/debug/.build-id/b2/2926c9347c837b223a930fa8047344d0412d27.debug...done.
done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libasound.so.2...(no debugging
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libpthread.so.0...Reading symbols
from
/usr/lib/debug/.build-id/75/d11a3ee55319e6cebcf33286de8df9a39bcaea.debug...done.
done.
[New LWP 28047]
[New LWP 28046]
[New LWP 27809]
[New LWP 27808]
[New LWP 27637]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Reading symbols from /usr/lib/x86_64-linux-gnu/libstdc++.so.6...(no debugging
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libm.so.6...Reading symbols from
/usr/lib/debug/.build-id/32/cf2a6213282743ee4531d19850652c3fc0a143.debug...done.
done.
Reading symbols from /lib/x86_64-linux-gnu/libgcc_s.so.1...(no debugging
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...Reading symbols from

Bug#810683: nmu: openblas_0.2.15-1 atlas_3.10.2-9

[Sébastien Villemot]

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

Dear Release Team,

Please schedule a binNMU of openblas and atlas. The libraries build by these
packages contain some binary objects that are taken from lapack (via the
liblapack-pic package), as reflected by their Built-Using field. They need to
be rebuild against the newly uploaded lapack 3.6.0-2.

nmu openblas_0.2.15-1 atlas_3.10.2-9 . ANY . unstable . -m "Rebuild against 
LAPACK 3.6.0"

Cheers,

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594


signature.asc
Description: PGP signature

Bug#741935: Bug#803800: avbin: FTBFS with FFmpeg 2.9

[Jonathan Peirce]

Thanks for the note Andreas. I think for the psychopy package we now 
have sufficient alternatives that we can live without avbin.

best wishes
Jon

On 07/01/16 22:31, Andreas Cadhalpun wrote:

Hi,

the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).

As this package is currently broken (#750577), not in testing
due to #741935, and still orphaned, I think it should be removed
from sid.

Therefore I'll request it's removal soon, unless someone fixes
the outstanding issues of this package.

Best regards,
Andreas


--
Dr Jonathan Peirce
School of Psychology
University of Nottingham





This message and any attachment are intended solely for the addressee
and may contain confidential information. If you have received this
message in error, please send it back to me, and immediately delete it. 


Please do not use, copy or disclose the information contained in this
message or in any attachment.  Any views or opinions expressed by the
author of this email do not necessarily reflect the views of the
University of Nottingham.

This message has been checked for viruses but the contents of an
attachment may still contain software viruses which could damage your
computer system, you are advised to perform your own checks. Email
communications with the University of Nottingham may be monitored as
permitted by UK legislation.

Bug#741223: Simplifying the patch

[Sunil Mohan Adapa]

I believe, the patch can and must be simplified.

*Current state*: The current patch creates a subvol called "@" and then
makes a lot of code changes to various activities to make sure that all
the activities happen on that subvol. The main brtfs volume is mounted
and then root directory path (the subvolume to work on) argument is
passed to all the necessary functions. This technique is based on
conventions specified in https://help.ubuntu.com/community/btrfs. On
this page, the only reason specified for not using default subvolume
feature of btrfs is that it does not work with rootfsflags recommended
in the page. I find that this convention makes it easy to examine
subvolumes and organize them but makes it hard to actually use a
subvolume. Typical process of reverting to a snapshot (which is a
subvolume) involves switching the default subvolume and rebooting.
However, in this convention, switching to a subvolume involves changing
boot arguments and modifying the fstab. From a reliability point of
view, this is troubling because we have to reliably update the uboot
environment, grub configuration and fstab.

*Proposal*: We should use the default volume feature of the btrfs
filesytem and we should not pass "subvol=@" etc. in fstab and kernel
boot arguments. In fact we should not even create a default subvolume
called "@". Then the patch will become very simple. No need to create
subvolume, no need to pass rootfsdir to all methods, no need for extra
/btrfs directory, no need to have special grub arguments and no need to
have special fstab options. The patch should simply create filesystem
with type 'btrfs' then treat it like any other filesystem by mounting,
debootstrapping, running grub-install etc. This mostly means that the
patch is not necessary. We just need to create some test cases (based on
existing cases for ext4) to make sure btrfs is building/running fine.

Snapshotting tools will then deal with complexity of
snapshots/subvolumes. A good example is how Snapper (snapper.io) works.
It creates snapshots underneath /.snapshots. When someone reverts to a
snapshot, it will set the default subvolume of the btrfs filesystem and
recommend a reboot. All of this can be done without the "@" subvolume. I
will post a separate proposal for snapshotting in FreedomBox in more
detail based on this plan.

-- 
Sunil



signature.asc
Description: OpenPGP digital signature

Bug#810672: firmware-free should include the ath9k_htc firmware binaries

[Paul Fertser]

Package: firmware-free
Version: 3.4
Severity: wishlist

Hello,

According to the upstream commit[1] ath9k_htc version 1.4.0 is free
software (and the future versions will be free software as well,
obviously).

Please add it to this package (and remove from firmware-atheros).

There's one important thing to consider though: location of the
firmware files.

If you add the binaries just as they're located in linux-firmware they
will be seen and used only by the kernel versions that include [2]. If
you copy them to the old place then the older kernels will work with
1.4.0 too (it's backwards-compatible to 1.3.0). Please see [2] for
more rationale and details regarding this.

The maintainer of the open ath9k_htc firmware is in Cc.

[1] 
https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=3f3aa3a12d5e5d34bda87a691cf7176baef95bf3
[2] 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e904cf6fe23022cde4e0ea9d41601411a315a3dc

Bug#810678: dia2code segfaults

[Ophir LOJKINE]

Package: dia2code

Hello,
  I've recently started to use dia2code. Apparently, the code is very old and 
is not maintained anymore.
  I've found the program to segfaults on several cases, and have corrected 
these.
  I've also added the ability to import database diagrams (useful for the SQL 
export).
  There are several different patches for the different problems.
  I've forked the code on github, and you can see the commits here:
https://github.com/lovasoa/dia2code/commits/master

Thanks,
lovasoa

Bug#790762: src:hplip: Many PPD files for postscript drivers are missing in printer-driver-postscript-hp

[John Paul Adrian Glaubitz]

Hi!

On 07/01/2015 05:22 PM, John Paul Adrian Glaubitz wrote:
> While setting up a new print server on the network, we noticed that the binary
> package printer-driver-postscript-hp is missing the PPDs for many postscript
> printers actually supported by hplip.

Just saw that hplip was finally updated again in Debian. Looking at the
package in question, the problem is still prevalent:

glaubitz@z6:/tmp> wget
ftp://ftp.debian.org/debian/pool/main/h/hplip/printer-driver-postscript-hp_3.15.11+repack0-1_all.deb
--2016-01-11 09:53:15--
ftp://ftp.debian.org/debian/pool/main/h/hplip/printer-driver-postscript-hp_3.15.11+repack0-1_all.deb
   => ‘printer-driver-postscript-hp_3.15.11+repack0-1_all.deb’
Resolving ftp.debian.org (ftp.debian.org)... 130.89.148.12,
2001:610:1908:b000::148:12
Connecting to ftp.debian.org (ftp.debian.org)|130.89.148.12|:21...
connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /debian/pool/main/h/hplip ... done.
==> SIZE printer-driver-postscript-hp_3.15.11+repack0-1_all.deb ... 843884
==> PASV ... done.==> RETR
printer-driver-postscript-hp_3.15.11+repack0-1_all.deb ... done.
Length: 843884 (824K) (unauthoritative)

printer-driver-postscript-hp_3.15.
100%[>]
824.11K  --.-KB/sin 0.1s

2016-01-11 09:53:16 (6.42 MB/s) -
‘printer-driver-postscript-hp_3.15.11+repack0-1_all.deb’ saved [843884]

glaubitz@z6:/tmp> dpkg-deb -c
printer-driver-postscript-hp_3.15.11+repack0-1_all.deb
drwxr-xr-x root/root 0 2016-01-10 02:00 ./
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/lib/
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/lib/cups/
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/lib/cups/driver/
-rwxr-xr-x root/root998446 2016-01-10 02:00
./usr/lib/cups/driver/postscript-hp
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/share/
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/share/doc/
drwxr-xr-x root/root 0 2016-01-10 02:00
./usr/share/doc/printer-driver-postscript-hp/
-rw-r--r-- root/root 75864 2016-01-09 22:42
./usr/share/doc/printer-driver-postscript-hp/changelog.Debian.gz
-rw-r--r-- root/root  4830 2016-01-09 22:42
./usr/share/doc/printer-driver-postscript-hp/copyright
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/share/cups/
drwxr-xr-x root/root 0 2016-01-10 02:00
./usr/share/cups/ppd-updaters/
-rw-r--r-- root/root   110 2016-01-10 02:00
./usr/share/cups/ppd-updaters/printer-driver-postscript-hp.ppd-updater
glaubitz@z6:/tmp>

The PPD files are not to be found in the PPD package either:

glaubitz@z6:/tmp> wget
ftp://ftp.debian.org/debian/pool/main/h/hplip/hpijs-ppds_3.15.11+repack0-1_all.deb
--2016-01-11 09:57:14--
ftp://ftp.debian.org/debian/pool/main/h/hplip/hpijs-ppds_3.15.11+repack0-1_all.deb
   => ‘hpijs-ppds_3.15.11+repack0-1_all.deb’
Resolving ftp.debian.org (ftp.debian.org)... 130.89.148.12,
2001:610:1908:b000::148:12
Connecting to ftp.debian.org (ftp.debian.org)|130.89.148.12|:21...
connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /debian/pool/main/h/hplip ... done.
==> SIZE hpijs-ppds_3.15.11+repack0-1_all.deb ... 160598
==> PASV ... done.==> RETR hpijs-ppds_3.15.11+repack0-1_all.deb ...
done.
Length: 160598 (157K) (unauthoritative)

hpijs-ppds_3.15.11+repack0-1_all.d
100%[>]
156.83K  --.-KB/sin 0.07s

2016-01-11 09:57:15 (2.09 MB/s) - ‘hpijs-ppds_3.15.11+repack0-1_all.deb’
saved [160598]

glaubitz@z6:/tmp> dpkg-deb -c hpijs-ppds_3.15.11+repack0-1_all.deb |grep
postscript
glaubitz@z6:/tmp>

Could you please add the missing postscript PPDs.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#810666: install of version 0.8.6 remove systemd

[Guus Sliepen]

severity 810666 normal
thanks

On Mon, Jan 11, 2016 at 07:12:28AM +0100, Jörg Frings-Fürst wrote:

> Package: ifupdown
> Version: 0.7.54
> Severity: critical
> 
> ~# apt-get dist-upgrade
> Paketlisten werden gelesen... Fertig
> Abhängigkeitsbaum wird aufgebaut.   
> Statusinformationen werden eingelesen Fertig
> Paketaktualisierung (Upgrade) wird berechnet... Fertig
> Die folgenden Pakete sind zurückgehalten worden:
>   ifupdown
> 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.

dist-upgrade detects that there is a transition going on and that
upgrading ifupdown now would cause other packages to be removed, that is
why it keeps it back.

> ~# apt-get install ifupdown

Now you are telling apt-get to explicitly upgrade the ifupdown package:

> Paketlisten werden gelesen... Fertig
> Abhängigkeitsbaum wird aufgebaut.   
> Statusinformationen werden eingelesen Fertig
> The following additional packages will be installed:
>   sysvinit-core
> Vorgeschlagene Pakete:
>   ppp rdnssd
> Die folgenden Pakete werden ENTFERNT:
>   systemd systemd-sysv
> Die folgenden NEUEN Pakete werden installiert:
>   sysvinit-core

And it tells you here what will happen if you continue.

> Die folgenden Pakete werden aktualisiert (Upgrade):
>   ifupdown
> 1 aktualisiert, 1 neu installiert, 2 zu entfernen und 0 nicht aktualisiert.
> Es müssen 204 kB an Archiven heruntergeladen werden.
> Nach dieser Operation werden 17,9 MB Plattenplatz freigegeben.
> Möchten Sie fortfahren? [J/n] n

It asks you if you really want to do this or not. Note that your system
would still be perfectly working when it installs sysvinit. So nothing
is broken by the ifupdown package, therefore I'm reducing the severity.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: Digital signature

Bug#810687: mdadm: eats all cpu time on all cores

[Michal Suchanek]

Package: mdadm
Version: 3.3.4-1.1+b1
Severity: normal

hello,

mdadm eats all CPU time of all cores.

This ShouldNotHappen(tm)

I had a lvm volume on a disk which failed while I was trying to upgrade
the volume to raid1 so my raid configureation is very broken.

killing mdadm only helps temporarily. it restarts itself.

Is there any debug information I can provide before I trash the disks?

Thanks

Michal


-- Package-specific info:
--- mdadm.conf
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST 
MAILADDR root
ARRAY metadata=ddf UUID=587baab3:c41402e5:c334b912:99c2ce3f
ARRAY container=587baab3:c41402e5:c334b912:99c2ce3f member=0 
UUID=363fa001:b5660ad0:24715b0d:afaecdb2

--- /etc/default/mdadm
INITRDSTART='none'
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false

--- /proc/mdstat:
Personalities : [linear] [raid1] 
md126 : inactive sdg[0]
  975585280 blocks super external:/md127/0
   
md127 : inactive sdg[0](S)
  1177304 blocks super external:ddf
   
unused devices: 

--- /proc/partitions:
major minor  #blocks  name

   8   80   31266648 sdf
   8   814193280 sdf1
   8   82   27070464 sdf2
   8   96  976762584 sdg
   8  112  244198584 sdh
   8  113  244197376 sdh1
   8  128  244198584 sdi
   8  129   20481024 sdi1
   8  1303148740 sdi2
   8  132  220564417 sdi4
   70   55562240 loop0
   80   30310400 sda
   81   30310384 sda1

--- LVM physical volumes:
  PV VG   Fmt  Attr PSize   PFree
  /dev/sdg   scratchg lvm2 a--  931.51g 8.00m
--- mount output
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=1005252,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,relatime,size=1612848k,mode=755)
/dev/sdf2 on / type ext3 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
/dev/sdh1 on /srv/rhev type ext4 (rw,relatime,data=ordered)
/dev/sdi1 on /home type ext3 (rw,relatime,errors=remount-ro,data=ordered)
/dev/sdi4 on /scratch type ext3 (rw,relatime,data=ordered)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=806424k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
usmb on /home/hramrach/mnt type fuse.usmb 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,max_read=32768)
servo:/srv/samba/au on /home/hramrach/au type fuse.sshfs 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
servo:/srv/scratch/Incoming on /home/hramrach/inc type fuse.sshfs 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
usmb on /home/hramrach/win type fuse.usmb 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,max_read=32768)
/dev/sda1 on /srv/flash type ext4 (rw,relatime,data=ordered)
usmb on /home/hramrach/data type fuse.usmb 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,max_read=32768)
usmb on /home/hramrach/inst type fuse.usmb 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,max_read=32768)
heretic:/media/sdg1 on /home/hramrach/test type fuse.sshfs 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

--- initrd.img-3.16.0-4-amd64:

gzip: /boot/initrd.img-3.16.0-4-amd64: 

Bug#810688: shadowsocks: man page references texinfo documents which don't exist

[Michal Suchanek]

Package: shadowsocks
Version: 2.1.0-1
Severity: normal

Hello,

when reading shadowsocks(1) man page I get this at the bottom:

SEE ALSO
   The  programs  are  documented fully by Shell Xu
    and Clowwindy ,
   available via the
  Info system.

However, both info shadowsocks and info ssserver return the stub
manpages and no actual texinfo documentation.

Please add the texinfo documentation or remove the reference.

Thanks

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages shadowsocks depends on:
ii  dpkg  1.18.3
ii  python2.7.11-1
ii  python-m2crypto   0.22.6~rc4-1
ii  python-pkg-resources  18.8-1

shadowsocks recommends no packages.

shadowsocks suggests no packages.

-- no debconf information

Bug#810679: [PATCH] IPv6 broken due with exosip 4

[Michael Stapelberg]

Package: linphone
Version: 3.6.1-2.4
Severity: normal
Tags: ipv6 patch

exosip 4 deprecated eXosip_enable_ipv6() in such a way that it fails
silently: https://sources.debian.net/src/libexosip2/4.1.0-2/src/eXconf.c/#L55

As a consequence, when enabling IPv6 in linphone, it tries to bind to an
IPv6 address (“::0”) while specifying IPv4 as address family, which
fails.

We need to switch to eXosip_set_option:

  eXosip_set_option(ctx->excontext, EXOSIP_OPT_ENABLE_IPV6, );

I’ve attached a patch which updates debian/patches/port-to-exosip-4.patch
Unfortunately, it seems I’m using a different quilt version than you
are, so quilt touched all hunks, making the patch bigger than it needs
to be. The important hunk of my patch is:

@@ -704,7 +722,14 @@
sal_set_dscp(ctx,ctx->dscp);
sal_use_dates(ctx,ctx->add_dates);
  
-@@ -429,7 +482,11 @@ int sal_listen_port(Sal *ctx, const char
+   ipv6=strchr(addr,':')!=NULL;
++#ifdef HAVE_STRUCT_EXOSIP_T
++  eXosip_set_option(ctx->excontext, EXOSIP_OPT_ENABLE_IPV6, );
++#else
+   eXosip_enable_ipv6(ipv6);
++#endif
+ 
+   if (is_secure && tr == SalTransportUDP){
ms_fatal("SIP over DTLS is not supported yet.");
return -1;
}

Feel free to re-do my patch if that makes merging easier.

Thanks for your work on linphone!

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

Kernel: Linux 4.3.0 (SMP w/8 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 linphone depends on:
ii  libasound21.0.29-1
ii  libatk1.0-0   2.18.0-1
ii  libavcodec-ffmpeg56   7:2.8.1-1
ii  libavutil-ffmpeg547:2.8.1-1
ii  libc6 2.19-22
ii  libcairo2 1.14.2-2
ii  libexosip2-11 4.1.0-2+b1
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6-2
ii  libgdk-pixbuf2.0-02.32.1-1
ii  libgl1-mesa-glx [libgl1]  11.0.5-1
ii  libglew1.13   1.13.0-2
ii  libglib2.0-0  2.46.2-3
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgtk2.0-0   2.24.28-1
ii  liblinphone5  3.6.1-2.4
ii  libmediastreamer-base33.6.1-2.4+b4
ii  libnotify40.7.6-2
ii  libogg0   1.3.2-1
ii  libopus0  1.1-2
ii  libortp9  3.6.1-2.4+b4
ii  libosip2-11   4.1.0-2
ii  libpango-1.0-01.38.1-1
ii  libpangocairo-1.0-0   1.38.1-1
ii  libpangoft2-1.0-0 1.38.1-1
ii  libpulse0 7.1-2
ii  libsoup2.4-1  2.52.1-1
ii  libspandsp2   0.0.6-2.1
ii  libspeex1 1.2~rc1.2-1
ii  libspeexdsp1  1.2~rc1.2-1
ii  libsqlite3-0  3.8.11.1-1
ii  libswscale-ffmpeg37:2.8.1-1
ii  libtheora01.1.1+dfsg.1-7
ii  libudev1  227-2
ii  libupnp6  1:1.6.19+git20141001-1
ii  libv4l-0  1.8.0-1
ii  libvpx3   1.5.0-2
ii  libx11-6  2:1.6.3-1
ii  libxv12:1.0.10-1+b1
ii  linphone-nogtk3.6.1-2.4

linphone recommends no packages.

Versions of packages linphone suggests:
pn  yelp  

-- no debconf information
--- linphone-3.6.1/debian/patches/port-to-exosip-4.patch	2013-07-30 22:45:13.0 +0200
+++ /tmp/linphone-3.6.1/debian/patches/port-to-exosip-4.patch	2016-01-11 09:45:22.990338912 +0100
@@ -10,8 +10,10 @@
 Only in linphone-3.6.1: config.sub
 Only in linphone-3.6.1: configure
 Only in linphone-3.6.1/console: Makefile.in
 a/coreapi/authentication.c
-+++ b/coreapi/authentication.c
+Index: linphone-3.6.1/coreapi/authentication.c
+===
+--- linphone-3.6.1.orig/coreapi/authentication.c
 linphone-3.6.1/coreapi/authentication.c
 @@ -308,7 +308,7 @@ void linphone_core_add_auth_info(Linphon
  			sai.userid=ai->userid;
  			sai.realm=ai->realm;
@@ -21,8 +23,10 @@
  			ai->usecount++;
  		}
  	}
 a/coreapi/callbacks.c
-+++ b/coreapi/callbacks.c
+Index: linphone-3.6.1/coreapi/callbacks.c
+===
+--- linphone-3.6.1.orig/coreapi/callbacks.c
 linphone-3.6.1/coreapi/callbacks.c
 @@ -224,19 +224,19 @@ static void call_received(SalOp *h){
  	lc->presence_mode==LinphoneStatusDoNotDisturb ||
  	lc->presence_mode==LinphoneStatusMoved){
@@ -96,8 +100,10 @@
  	}
  }
  
 a/coreapi/chat.c
-+++ b/coreapi/chat.c
+Index: linphone-3.6.1/coreapi/chat.c
+===
+--- linphone-3.6.1.orig/coreapi/chat.c
 linphone-3.6.1/coreapi/chat.c
 @@ -98,10 +98,10 @@ static void _linphone_chat_room_send_mes
  	}
  	if (msg->external_body_url) {
@@ 

Bug#810689: php5.6-cli: unowned symlink after purge (policy 6.8, 10.8): /etc/php/5.6/cli/conf.d/20-opcache.ini -> /etc/php/mods-available/opcache.ini

[Andreas Beckmann]

Package: php5.6-cli
Version: 5.6.17+dfsg-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

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

0m59.8s ERROR: FAIL: Package purging left files on system:
  /etc/php/5.6/cli/  owned by: php5.6-cli
  /etc/php/5.6/cli/conf.d/   owned by: php5.6-cli
  /etc/php/5.6/cli/conf.d/20-opcache.ini -> /etc/php/mods-available/opcache.ini 
 not owned


cheers,

Andreas


php5.6-cli_5.6.17+dfsg-1.log.gz
Description: application/gzip

Bug#799237:

[Michael D]

#810675 - upgrading to the latest upstream version fixes this.

Bug#810670: Acknowledgement (mlocate: Using grub-mount dir (/var/lib/os-prober/mount) blocks execution of update-grub)

[Andrey Nikitin]

I think that to solve this problem will be enough
to append "fuse.grub-mount"
to PRUNEFS variable (/etc/updatedb.conf).

Bug#810676: python-keyring: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

[Neil Williams]

Package: python-keyring
Version: 6.1-1
Severity: grave
Justification: renders package unusable

Processes using python-keyring 6.1 can no longer run as a daemon - a regression
from previous support, causing lava-server to halt all daemon operations.

dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: Unable 
to autolaunch a dbus-daemon without a $DISPLAY for X11

Traceback (most recent call last):
  File "/usr/bin/lava-server", line 9, in 
load_entry_point('lava-server==2015.12+5459.74d110f', 'console_scripts', 
'lava-server')()
  File "/usr/lib/python2.7/dist-packages/lava_server/manage.py", line 125, in 
main
run_with_dispatcher_class(LAVAServerDispatcher)
  File "/usr/lib/python2.7/dist-packages/lava_tool/dispatcher.py", line 45, in 
run_with_dispatcher_class
raise cls.run()
  File "/usr/lib/python2.7/dist-packages/lava/tool/dispatcher.py", line 153, in 
run
raise SystemExit(cls().dispatch(args))
  File "/usr/lib/python2.7/dist-packages/lava/tool/dispatcher.py", line 143, in 
dispatch
return command.invoke()
  File "/usr/lib/python2.7/dist-packages/lava_server/manage.py", line 114, in 
invoke
execute_from_command_line(['lava-server'] + self.args.command)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 353, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 345, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
348, in run_from_argv
self.execute(*args, **cmd_options)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
399, in execute
output = self.handle(*args, **options)
  File 
"/usr/lib/python2.7/dist-packages/lava_scheduler_app/management/commands/scheduler.py",
 line 46, in handle
from lava_scheduler_daemon.service import JobQueue
  File "/usr/lib/python2.7/dist-packages/lava_scheduler_daemon/service.py", 
line 28, in 
from lava_scheduler_daemon.worker import WorkerData
  File "/usr/lib/python2.7/dist-packages/lava_scheduler_daemon/worker.py", line 
31, in 
from lava_tool.authtoken import AuthenticatingServerProxy, MemoryAuthBackend
  File "/usr/lib/python2.7/dist-packages/lava_tool/authtoken.py", line 25, in 

import keyring.core
  File "/usr/lib/python2.7/dist-packages/keyring/__init__.py", line 12, in 

from .core import (set_keyring, get_keyring, set_password, get_password,
  File "/usr/lib/python2.7/dist-packages/keyring/core.py", line 158, in 
init_backend()
  File "/usr/lib/python2.7/dist-packages/keyring/core.py", line 58, in 
init_backend
set_keyring(load_config() or _get_best_keyring())
  File "/usr/lib/python2.7/dist-packages/keyring/core.py", line 66, in 
_get_best_keyring
keyrings = backend.get_all_keyring()
  File "/usr/lib/python2.7/dist-packages/keyring/util/__init__.py", line 20, in 
wrapper
func.always_returns = func(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/keyring/backend.py", line 180, in 
get_all_keyring
exceptions=TypeError))
  File "/usr/lib/python2.7/dist-packages/keyring/util/__init__.py", line 29, in 
suppress_exceptions
for callable in callables:
  File "/usr/lib/python2.7/dist-packages/keyring/backend.py", line 172, in 
is_class_viable
keyring_cls.priority
  File "/usr/lib/python2.7/dist-packages/keyring/util/properties.py", line 22, 
in __get__
return self.fget.__get__(None, owner)()
  File "/usr/lib/python2.7/dist-packages/keyring/util/XDG.py", line 18, in 
wrapper
return func(*args, **kwargs) * self.multiplier
  File "/usr/lib/python2.7/dist-packages/keyring/backends/kwallet.py", line 
134, in priority
bus = dbus.SessionBus()
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 211, in __new__
mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 100, in __new__
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 122, in __new__
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: Unable 
to autolaunch a dbus-daemon without a $DISPLAY for X11

python-keyring must NOT require X11 to operate.

Downgrading to 5.7.1-1 in testing fixes the problem.

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

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

Bug#810674: ITP: golang-github-kolo-xmlrpc -- Implementation of the XMLRPC client protocol in Go

[Martín Ferrari]

Package: wnpp
Severity: wishlist
Owner: "Martín Ferrari" 

* Package name: golang-github-kolo-xmlrpc
  Version : 0+git20150413.0826b98
  Upstream Author : Dmitry Maksimov 
* URL : https://github.com/kolo/xmlrpc
* License : MIT
  Programming Lang: Go
  Description : Implementation of the XMLRPC client protocol in Go

 The github.com/kolo/xmlrpc package is an implementation of client side part of
 XMLRPC protocol in the Go language.

Bug#810675: New Upstream Version - v0.7.06

[Michael D]

Package: duplicity
Version: 0.7.05-2

Upstream version v0.7.06 was released 2015/12/07 - would be great to please
get an update for it. Would also resolve #799237 and maybe others.

Thanks

Bug#810663: Include Device Tree model in reportbug script

[Uwe Kleine-König]

Hello,

On Sun, Jan 10, 2016 at 09:23:40PM -0800, Martin Michlmayr wrote:
> Please note that the strange "echo ... $(cat ..)" construct is
> intentional.  'cat /proc/device-tree/model' leads to a strange
> character at the end because there's no newline and using echo
> gets rid of it.

Maybe put this info also (or instead) in a source comment?

> diff --git a/debian/templates/image.plain.bug/include-model 
> b/debian/templates/image.plain.bug/include-model
> index 60a7112..9c6aedd 100644
> --- a/debian/templates/image.plain.bug/include-model
> +++ b/debian/templates/image.plain.bug/include-model
> @@ -39,6 +39,11 @@ grep_model() {
>  false
>  ;;
>esac
> +
> +  # Device Tree model
> +  if [ -r /proc/device-tree/model ]; then
> +echo "Device Tree model:" $(cat /proc/device-tree/model)

In recent kernels[1] /proc/device-tree is a symlink to
/sys/firmware/devicetree/base. I expect that it stays there for quite a
while, but I wonder if it would be cleaner to use /sys/firmware...
directly. Hmm, probably not, because using proc also covers
2.6.36..3.15.

Best regards
Uwe

[1] since 75b57ecf9d1d ("of: Make device nodes kobjects so they show up
in sysfs") which appeared in 3.15. 

-- 
Pengutronix e.K.   | Uwe Kleine-König|
Industrial Linux Solutions | http://www.pengutronix.de/  |

Bug#789931: tag this as wontfix/severity normal

[Gert Wollny]

tags 789931 wontfix 
severity 789931 severity
thanks

The bug was reported against version 2.2.0 which is outdated, version
3.2.0 now builds find on all architectures that are supported by the
insighttoolkit4. 

On the other hand,  the bug reports build failure on arm64 - this is an
arch that is not (yet) supported by insighttoolkit4 and the arch
support depends on upstream. Hence the downgrade and tag.

Bast, 
Gert 

Bug#810691: backuppc: unowned files after purge (policy 6.8, 10.8): /etc/backuppc/{htpasswd, pc}

[Andreas Beckmann]

Package: backuppc
Version: 3.3.1-2
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

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

1m20.0s ERROR: FAIL: Package purging left files on system:
  /etc/backuppc/ owned by: backuppc
  /etc/backuppc/htpasswd not owned
  /etc/backuppc/pc -> /etc/backuppc  not owned


cheers,

Andreas


backuppc_3.3.1-2.log.gz
Description: application/gzip

Bug#810655: libembperl-perl: post-installation script returned error

[Dominic Hargreaves]

On Mon, Jan 11, 2016 at 02:32:36AM +0100, Rosario Maddox wrote:
> Package: libembperl-perl
> Version: 2.5.0-4
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> Tried to install it:
> 
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> libembperl-perl is already the newest version.
> 0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
> 1 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> Do you want to continue? [Y/n] 
> Setting up libembperl-perl (2.5.0-4) ...
> dpkg: error processing package libembperl-perl (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Errors were encountered while processing:
>  libembperl-perl
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> This should not happen.

Could you try editing /var/lib/dpkg/info/libembperl-perl.postinst to
add ' -x' to the first shebang line, and then rerun this configuration
(dpkg --configure -a)? This should give a bit more information about
where it's failing.

Thanks,
Dominic.

Bug#810686: Creepy: Add Youtube plugin?

[Petter Reinholdtsen]

Package: creepy
Version: 1.3-1
Severity: wishlist

According to
https://code.google.com/p/gdata-issues/issues/detail?id=4234 >,
there is a API on Youtube to find videos by location.

The URL
https://gdata.youtube.com/feeds/api/videos?v=2=json=51.7248487,-1.2328819!=1km
 >
is supposed to be working, but when I tested it I got this reply:

  

  GData
  NoLongerAvailableException
  No longer available

  

I have not been able to find out if the API is replaced or simply
removed.

-- 
Happy hacking
Petter Reinholdtsen

Bug#808581: chromium: reactivate NPAPI option

[Pierre Crescenzo]

Hello,

I have gnome-shell-extensions package. But this is not an alternative of
the web functionalities.

Regards,


Pierre Crescenzo
  mailto:pie...@crescenzo.nom.fr
  http://www.crescenzo.nom.fr/

Bug#810602: ITP: argon2 -- memory-hard hashing function

[Luca BRUNO]

On Monday, January 11, 2016 08:57:23 AM Paul Wise wrote:
> On Sun, Jan 10, 2016 at 8:03 PM, Luca Bruno wrote:
> >  Argon2 is a password-hashing function that can be used to hash passwords
> >  for credential storage, key derivation, or other applications.
> 
> It might be better to move to client-side SSL certificates than keep
> using passwords :)

The description should probably be reworded a bit to stress that this is the 
outcome of the https://password-hashing.net/ competition.

Cheers, Luca

-- 
 .''`.  ** Debian GNU/Linux **  | Luca Bruno (kaeso)
: :'  :   The Universal O.S.| lucab (AT) debian.org
`. `'`  | GPG: 0xBB1A3A854F3BBEBF
  `- http://www.debian.org  | Debian GNU/Linux Developer


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

Bug#810673: proposed RM: mountall -- RoQA; only used by upstart which was removed

[Ansgar Burchardt]

Package: mountall
Version: 2.54
Severity: serious
Tags: sid

upstart was removed from Debian and Michael Biebl pointed out that the
"mountall" tool was only packaged for use with it.  So it should
probably be removed as well.

Besides upstart, apt-cache rdepends shows only cgroupfs-mount, but the
current version only suggests mountall.

If there are no objections, I'll reassign the removal request to ftp.d.o
later.

Ansgar

Bug#806844: unattended-upgrades: needs to be rebuilt with fixed debhelper

[Andreas Beckmann]

Followup-For: Bug #806844
Control: tag -1 pending

no-change rebuild NMU uploaded to DELAYED/2


Andreas

Bug#810131: RM: python-pygithub [all] -- NBS; renamed to python-github

[Gianfranco Costamagna]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi ftpmasters!

>> 
> This is already on the cruft report.  Once the rdepends are fixed,
> this will be taken care of automatically.
> 

well, actually it used to be automatically handled, but something is
preventing it to disappear.

I have the same issue with src:python-udiskie, that has been included
into a new src:udiskie package, but I still see the old source around

(and I confirm before it was correctly deleted).

Can it be a regression in some script?

(BTW my udiskie shouldn't have any rdep, being an application)

thanks,
Gianfranco

> Scott K
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWk3i8AAoJEPNPCXROn13ZLSQQAM0TNtWRuRjt+a21gXacePa4
+zoQ4cm4WGvNDSJazzl1fJTNna8xtoM1+fhOaxPuwx8vMDsRxCAoBdowqnxZiP7m
cN8SlZrgBnc+2fX5SxmHwg0xGc5CSnWCTfrTDrAPQiggdOlXIwiCaadqfFRAXpGw
4UfPka8bV3ahjtzC4AOMQTAEMTsW7qUue1NN+G8BZ5PEdMucnIPR3pZX9QsiCaSF
IyBqBOw79kxKHDTrsNzRzk2cNq1Entqe173+hbsVymqGCX0GvmvtVlf/ta9ngQ3P
G3YTAR+K8AiCcXsG2MUC4zCXQXx1v4zflYULFphyJFWx5D90Jr4fHVdnqK9NdOUC
TdaSGVLXws3KwTeyrxf4HOJrwT2YIbN/Zf+l2tcf/ggKUMn7qOiQ2PKC3TpVLwvw
Rv6Lx1JLpDoQ29kUagm7AZM0fqcdQ5m4AwThlDSjqLJxOJxcbuEnDlcBx/trXh74
6ZogDrqQ4uAA76cTPbbFOrlLM4YVEiBsU6AkmIys00+1h6MSFXjbMScoG20Jwdp1
E93xMILcOZvOEYQtcXJQyoiTmGUkdu6tKU3Iejk6l5zq2yr8CkfWf5tNQv0jOVyp
c0srNqktocI9x6fij4cAFp2d/yzMkIaHKNs8AhGRkytzNR1iv8lCIk/C1LH/EMG6
7x7UIusI9eZxocOpJwF7
=eo2s
-END PGP SIGNATURE-

Bug#810680: Poweroff not working on QNAP: POWER_RESET=y missing

[Martin Michlmayr]

Package: linux
Version: 4.3.3-5
Tags: patch

I finally figured out why poweroff is not working on QNAP devices
despite the fix I mentioned in #807696 recently.  POWER_RESET is not
enabled, so POWER_RESET_QNAP is not built in.

I also enabled POWER_RESET_GPIO since that's needed by some Kirkwood
devices we support.

diff --git a/debian/config/armel/config.kirkwood 
b/debian/config/armel/config.kirkwood
index 8ab415d..ad11867 100644
--- a/debian/config/armel/config.kirkwood
+++ b/debian/config/armel/config.kirkwood
@@ -438,6 +438,8 @@ CONFIG_PCI_MVEBU=y
 ##
 ## file: drivers/power/reset/Kconfig
 ##
+CONFIG_POWER_RESET=y
+CONFIG_POWER_RESET_GPIO=y
 CONFIG_POWER_RESET_QNAP=y
 CONFIG_POWER_RESET_RESTART=y
 

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#810131: RM: python-pygithub [all] -- NBS; renamed to python-github

[Mattia Rizzolo]

On Mon, Jan 11, 2016 at 10:41:16AM +0100, Gianfranco Costamagna wrote:
> > This is already on the cruft report.  Once the rdepends are fixed,
> > this will be taken care of automatically.
> > 
> 
> well, actually it used to be automatically handled, but something is
> preventing it to disappear.
> 
> I have the same issue with src:python-udiskie, that has been included
> into a new src:udiskie package, but I still see the old source around

the problem is actually different:

in your case it's an old source, which afaik needs a manual removal,
mine is an old binary, which will be dealt automatically once the rdep
is done, but I'd love it to be taken care of before that will happen
(because waiting s not really needed, and because otherwise britney
won't migrate it).

-- 
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#810681: heimdal-clients: installing package forces krb5-user to be removed

[Paul Millar]

Package: heimdal-clients
Version: 1.6~rc2+dfsg-9
Severity: important

Dear Maintainer,

I am trying to install the heimdal-clients package because it contains some
"kerberised" applications that do not exist in the MIT equivalent package:
krb5-user.

However, installing heimdal-clients would force krb5-user to be remove:


paul@celebrimbor:~$ sudo apt-get --dry-run install heimdal-clients
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libhdb9-heimdal libkadm5clnt7-heimdal libkadm5srv8-heimdal libkafs0-heimdal
libotp0-heimdal libsl0-heimdal
Suggested packages:
  heimdal-docs heimdal-kcm
The following packages will be REMOVED:
  krb5-user
The following NEW packages will be installed:
  heimdal-clients libhdb9-heimdal libkadm5clnt7-heimdal libkadm5srv8-heimdal
libkafs0-heimdal libotp0-heimdal libsl0-heimdal
0 upgraded, 7 newly installed, 1 to remove and 0 not upgraded.
Remv krb5-user [1.12.1+dfsg-19+deb8u1]
Inst libhdb9-heimdal (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Inst libkadm5clnt7-heimdal (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Inst libkadm5srv8-heimdal (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Inst libkafs0-heimdal (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Inst libotp0-heimdal (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Inst libsl0-heimdal (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Inst heimdal-clients (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Conf libhdb9-heimdal (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Conf libkadm5clnt7-heimdal (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Conf libkadm5srv8-heimdal (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Conf libkafs0-heimdal (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Conf libotp0-heimdal (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Conf libsl0-heimdal (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
Conf heimdal-clients (1.6~rc2+dfsg-9 Debian:8.2/stable [amd64])
paul@celebrimbor:~$


>From manual dry-run installing each of the dependencies, I see that only the
heimdal-clients package requires the removal of the krb5-user package.

I don't understand the reason for requiring krb5-user package to be removed: in
case of conflicting names, alternatives (as provided by dpkg) allows multiple
instances to exist concurrently.

I've classified this bug as IMPORTANT, but it could also be classified as
WISHLIST, depending on one's point-of-view.

Cheers,

Paul.



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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)

Bug#810685: [apt] apt has no bash-completion

[Bogdan Vatra]

Package: apt
Version: 1.1.10
Severity: wishlist

--- Please enter the report below this line. ---
apt-get has full bash completion, but sadly, apt has none.
It will be great if apt command will gain bash completion.

Thanks.

BogDan.

Bug#790762: src:hplip: Many PPD files for postscript drivers are missing in printer-driver-postscript-hp

[John Paul Adrian Glaubitz]

On 01/11/2016 11:23 AM, Didier 'OdyX' Raboud wrote:
>> While setting up a new print server on the network, we noticed 
>> that the binary package printer-driver-postscript-hp is missing 
>> the PPDs for many postscript printers actually supported by 
>> hplip.
> 
> It's not. These are now compressed using pyppd, since version 
> 3.10.9-1: They are in the /usr/lib/cups/driver/postscript-hp python
> script.
> 
> CUPS uses these "PPD-compressed scripts" in /usr/lib/cups/driver 
> itself to extract the needed PPDs, and there should be little need 
> for you to need the PPD files directly.

Ok, strange concept. On the other hand, the hpijs-ppds package contains
the PPDs uncompressed:

glaubitz@z6:/tmp> dpkg-deb -c hpijs-ppds_3.15.11+repack0-1_all.deb |
head -n 20
drwxr-xr-x root/root 0 2016-01-10 02:00 ./
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/share/
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/share/doc/
drwxr-xr-x root/root 0 2016-01-10 02:00
./usr/share/doc/hpijs-ppds/
-rw-r--r-- root/root 75864 2016-01-09 22:42
./usr/share/doc/hpijs-ppds/changelog.Debian.gz
-rw-r--r-- root/root  4830 2016-01-09 22:42
./usr/share/doc/hpijs-ppds/copyright
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/share/ppd/
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/share/ppd/hplip/
drwxr-xr-x root/root 0 2016-01-10 02:00 ./usr/share/ppd/hplip/HP/
-rw-r--r-- root/root 19199 2016-01-10 02:00
./usr/share/ppd/hplip/HP/hp-scanjet_pro_3500_f1-hpijs.ppd
-rw-r--r-- root/root 19417 2016-01-10 02:00
./usr/share/ppd/hplip/HP/hp-psc_950xi-hpijs.ppd
-rw-r--r-- root/root 19417 2016-01-10 02:00
./usr/share/ppd/hplip/HP/hp-psc_950vr-hpijs.ppd
-rw-r--r-- root/root 19399 2016-01-10 02:00
./usr/share/ppd/hplip/HP/hp-psc_950-hpijs.ppd
-rw-r--r-- root/root 19399 2016-01-10 02:00
./usr/share/ppd/hplip/HP/hp-psc_920-hpijs.ppd
-rw-r--r-- root/root 19455 2016-01-10 02:00
./usr/share/ppd/hplip/HP/hp-psc_900_series-hpijs.ppd
-rw-r--r-- root/root 19417 2016-01-10 02:00
./usr/share/ppd/hplip/HP/hp-psc_780xi-hpijs.ppd
-rw-r--r-- root/root 19399 2016-01-10 02:00
./usr/share/ppd/hplip/HP/hp-psc_780-hpijs.ppd
-rw-r--r-- root/root 19399 2016-01-10 02:00
./usr/share/ppd/hplip/HP/hp-psc_760-hpijs.ppd
-rw-r--r-- root/root 19417 2016-01-10 02:00
./usr/share/ppd/hplip/HP/hp-psc_750xi-hpijs.ppd
dpkg-deb: error: subprocess tar was killed by signal (Broken pipe)
glaubitz@z6:/tmp>

So the packaging is somewhat inconsistent. I also really don't see the
advantage in obfuscating and compressing a few text files like that,
but ok.

> You can always get the PPD file with calling the archive as 
> follows:
> 
> $ /usr/lib/cups/driver/postscript-hp cat 
> "postscript-hp:0/ppd/hplip/HP/hp-designjet_t2300_postscript-ps.ppd"

Ok, good to know. Thanks for the heads-up!

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#810682: libncarg-dev: unsatisfiable Depends: ncl-narg

[Andreas Beckmann]

Package: libncarg-dev
Version: 6.3.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

unsatisfiable Depends: ncl-narg

Did you mean ncl-ncarg?


Cheers,

Andreas

Bug#777791: ball: ftbfs with GCC-5

[Danny Edel]

Hello Andreas, hello list(s),

I tried to reproduce this build failure on a current sid and investigate
a bit.  On my machine it outputs the same basic error messages (although
the line numbers in the basic_string template file are a bit different).

I try to quote the error message partially so it becomes a bit clearer
what is really going on:

On 01/07/2016 01:12 PM, Andreas Tille wrote:
> /build/ball-1.4.3~beta1/include/BALL/DATATYPE/string.iC: In member function 
> 'BALL::String& BALL::String::insert(BALL::String::const_iterator, 
> std::initializer_list)':
> /build/ball-1.4.3~beta1/include/BALL/DATATYPE/string.iC:1379:19: error: no 
> matching function for call to 
> 'std::__cxx11::basic_string::insert(BALL::String::const_iterator&, 
> std::initializer_list&)'
>   str_.insert(p, li);
>^

(...)

Info:
BALL::String::const_iterator is a typedef for std::string::const_iterator


> /usr/include/c++/5/bits/basic_string.h:1308:7: note: candidate: void 
> std::__cxx11::basic_string<_CharT, _Traits, 
> _Alloc>::insert(std::__cxx11::basic_string<_CharT, _Traits, 
> _Alloc>::iterator, std::   initializer_list<_Tp>) [with _CharT = 
> char; _Traits = std::char_traits; _Alloc = std::allocator; 
> std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::iterator = 
> __gnu_cxx::__normal_iterator; 
> typename __gnu_cxx::__alloc_traits __gnu_cxx::__alloc_traits<_Alloc>::rebind<_CharT>::other>::pointer = char*]
>insert(iterator __p, initializer_list<_CharT> __l)
>^
> /usr/include/c++/5/bits/basic_string.h:1308:7: note:   no known conversion 
> for argument 1 from 'BALL::String::const_iterator {aka 
> __gnu_cxx::__normal_iterator 
> >}' to 'std::__cxx11::basic_string::iterator {aka 
> __gnu_cxx::__normal_iterator}'


In essence this says:

(1) No matching function for
string::insert(string::const_iterator, initializer_list),

because (when trying the correct overload),
(2) Cannot convert from string::const_iterator to string::iterator


Which raises the question: Why does the compiler try to convert to a
non-const-iterator in the first place?

According to both cplusplus.com[1] and cppreference.com[2] the insert
function with an initializer_list as second parameter should take a
*const_*iterator directly.

I have condensed this into a simple test case (see attached string.cc)
and for me, this testcase fails in the same way as ball when called with
GCC.

Try it like this:

g++ -std=c++11 string.cc -o string && ./string
(long error message)

Now, with clang++ this fails too:

clang++ -std=c++11 string.cc -o string && ./string
(a bit shorter error message, but essentially the same)

However, if I try the example using clang's STL implementation (from
debian package libc++-dev) it builds *and runs* as expected:

clang++ -std=c++11 -stdlib=libc++ string.cc -o string && ./string
(outputs "Some new string")


I am not sure how to continue from here - this might be a bug in clang's
or gcc's std::string implementation, unportable usage from upstream, or
any number of other things.  If you have access to other compilers, it
may help to test the snippet on them too and report the results.

For reference:

$ g++ -dumpversion
5.3.1

-> Does not compile, cannot convert const_iterator->iterator
-> libstdc++-5-dev 5.3.1-5

$ clang++ -dumpversion
4.2.1

-> Does not compile with default/gcc STL implementation
-> Compiles and runs with libc++-dev 3.7.0-1


I hope this helps in resolving this, or at least in figuring out *where*
the issue actually is located.

- Danny


[1]: http://www.cplusplus.com/reference/string/string/insert/
[2]: http://en.cppreference.com/w/cpp/string/basic_string/insert
#include 
#include 

using namespace std;

int main(){
	string s = "Somestring";
	string::const_iterator ci = s.cbegin()+4;
	initializer_list il = { ' ', 'n', 'e', 'w' , ' ' };
	s.insert(ci, il);
	cout << s << endl;
	return 0;
}

Bug#810690: php7.0-cli: unowned symlinks after purge (policy 6.8, 10.8): /etc/php/7.0/cli/conf.d/20-{json, opcache}.ini -> /etc/php/mods-available/*.ini

[Andreas Beckmann]

Package: php7.0-cli
Version: 7.0.2-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

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

0m47.4s ERROR: FAIL: Package purging left files on system:
  /etc/php/7.0/cli/  owned by: php7.0-cli
  /etc/php/7.0/cli/conf.d/   owned by: php7.0-cli
  /etc/php/7.0/cli/conf.d/20-json.ini -> /etc/php/mods-available/json.ini   
 not owned
  /etc/php/7.0/cli/conf.d/20-opcache.ini -> /etc/php/mods-available/opcache.ini 
 not owned


cheers,

Andreas


php7.0-cli_7.0.2-1.log.gz
Description: application/gzip

Bug#810758: RM: ardour [kfreebsd-amd64 kfreebsd-i386] -- ROM; commercial restriction

[Steven Chamberlain]

Hi,

Sebastian Ramacher wrote:
> Please remove the out-of-date binary package ardour on kfreebsd-amd64 and
> kfreebsd-i386. They contain code that with a commercial restriction (see
> #810754) for details.

I've created a patch to fix the FTBFS:  https://bugs.debian.org/810765

Feel free to RM the out-of-date binary package though in the meantime,
if there are really no reverse-deps.

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


signature.asc
Description: Digital signature

Bug#810579: nss: FTCBFS: defines LINUX based on uname

[Steven Chamberlain]

Helmut Grohne wrote:
> [...] However specifying that macro still makes "#if
> defined(LINUX)" succeed despite __linux__ not being defined. Given that
> the present patch does not work, I am removing the patch tag. Please add
> it back if you add another patch.

Thanks Helmut, sorry about that!  I didn't have the patch applied
properly when I tested on kfreebsd, or this would have been obvious.

> I very much like your approach of using __linux__ as it makes the build
> more robust, but I fear that this will require textually replacing LINUX
> with __linux__ in the source rather than using a macro indirection.

This is my preference too.  If nss would use the standard (since <=
2001?) __linux__ macro, it would not need to define its own via CFLAGS.
I've created a patch for this, which I hope could be accepted upstream.
Then I refreshed 38_kbsd.patch on top of it (attached also).

I've checked that this change is a no-op for native builds - diffoscope
confirms the compiled code on linux-amd64 and kfreebsd-amd64 is
unchanged by this.  And I reviewed the build logs to double-check I
really had the patches applied this time.

I don't have a linux->kfreebsd cross-build environment to confirm it has
fixed the FTCBFS, but perhaps Helmut could test that?

Thank you,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org
From: Steven Chamberlain 

Bug#810550: grammar and indentation of unmet dependencies message

[積丹尼 Dan Jacobson]

All I know is I would write that as
libghc-crypto-cipher-tests-dev:
  Depends: libghc-hunit-dev-1.2.5.2-0c3b7 which is a virtual package and is not 
provided by any available package.
  Depends: libghc-quickcheck-dev-2.7.6-8f38a which is a virtual package and is 
not provided by any available package.
  Depends: libghc-base-dev-4.7.0.2-94ad8 which is a virtual package and is not 
provided by any available package.

Bug#809324: severity?

[alberto fuentes]

I think the serverity of this bug should be raised, although im not sure
the package upgraded at all from what im reading

Had I read this bug, I would had not upgraded :(

Do we have to open another bug against the kernel or something?

The workaround is to keep the kernel 4.2.0-1 around for a while, i guess :P

Bug#810774: ftp.debian.org: RM: vidalia -- RoM; unmaintained upstream, buggy, Qt4

[intrigeri]

Package: ftp.debian.org
Severity: normal

Hi,

it seems that I forgot to explicitly request the removal from
experimental back when I asked for the package removal in #796299.

So, please also remove vidalia from experimental.

Thanks in advance!

Cheers,
--
intrigeri

Bug#810779: ifquery segfaults when interface cannot be locked

[Martin Pitt]

Package: ifupdown
Version: 0.8.6
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch xenial

Hello,

In https://launchpad.net/bugs/1532722 it was reported that since
per-interface locking was introduced, ifquery sometimes crashes here:

|  #1 0x00013032 in strncpy (__len=80, __src=, __dest=0xbe86aa70 
"lo") at /usr/include/arm-linux-gnueabihf/bits/string3.h:126
|  No locals.
|  #2 do_interface (target_iface=) at main.c:846
|  iface = "lo", '\000' 
|  liface = "lo", '\000' 
|  pch = 
|  envname = 
"IFUPDOWN_lo\000\000\000\000\000\070\000\000\000[\000\000\000n\000\000\000\005\000\000\000\000\320\362\266\003\000\000\000\000\000\000\000\344\240\002\000\000\000\000\000\204\t\001\000\220S\366\266PX\366\266\001\000\000\000\000\000\000\000\267\277\364\266\000\320\362\266\001\000\000\000\001\000\000\000\000\000\000\000\003\000\000\000\f\240\344\266
 
\242\002\000\220~\001\000\t\000\000\000\000\000\000\000\220\240\311\000`\240\311\000h\247\002\000\t\000\000\000\b\240\311\000\220\240\311\000ﺀ\002\000\210\242\311\000\004\000\000\000\337S\001\000\000\000\000"
|  siface = 
|  envval = 
|  piface = "lo", '\000' 
|  plock = 0x0
|  success = false
|  lock = 0x0
|  current_state = 0x1 
|  __PRETTY_FUNCTION__ = "do_interface"
|  have_mapping = 
|  okay = 
|  failed = 
|  #3 0x00011994 in main (argc=, argv=0xbe86ade8) at main.c:1146
|  i = 0
|  success = true


The full analysis is on the Launchpad bug, but I give a summary: The
problem starts in do_interface():

char *current_state;
lock = lock_interface(iface, _state);

current_state is a stack variable and thus could have a random value.
It seems to be NULL on my amd64 build, but the crashes were reported
on ARM where it just happened to be 0x01 (see above stack trace).

Calling lock_interface() failed because /run/network/ifstate.lo does
not exist (yet), and thus lock == NULL (see stack trace), and
current_state does not get written to as that's an early exit path in
lock_interface(). Then do_interface progresses into the "else if (cmds
== iface_query)" branch, current_state != NULL is satisfied, and
strncpy() gets called on the uninitialized value.

This is reproducible by explicitly initializing it to a bogus value:

char *current_state = (char*) 1;

then

 $ sudo rm /run/network/ifstate.lo
 $ ./ifquery lo

crashes in this manner.

The fix is trivial, I'll send it in a followup once I get the bug
number from this report.

Martin

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


signature.asc
Description: Digital signature

Bug#810780: lintian: license-problem-php-license is wrong when source comes from pecl.php.net

[Ondřej Surý]

Package: lintian
Version: 2.5.39.1
Severity: normal

Dear Maintainer,

license-problem-php-license is mostly wrong as it is.  The last
agreement with FTP Masters was that PHP license is OK when the sources
some from PECL repository.

Could you please modify the check to look for:

Source: http://pecl.php.net/package/.*

in d/copyright and not trigger the error in such case?  The PHP
License still should not be used from sources distributed from
elsewhere, but pecl.php.net is OK.


Cheers,
Ondrej

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

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

Versions of packages lintian depends on:
ii  binutils  2.25.90.20160101-1
ii  bzip2 1.0.6-8
ii  diffstat  1.60-1
ii  file  1:5.25-2
ii  gettext   0.19.7-2
ii  hardening-includes2.8+nmu2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.29+b5
ii  libarchive-zip-perl   1.56-2
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-1+b1
ii  libdpkg-perl  1.18.4
ii  libemail-valid-perl   1.198-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.413-1+b1
ii  libparse-debianchangelog-perl 1.2.0-8
ii  libperl5.22 [libdigest-sha-perl]  5.22.1-3
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.69-1
ii  man-db2.7.5-1
ii  patchutils0.3.4-1
ii  perl  5.22.1-3
ii  t1utils   1.39-2
ii  xz-utils  5.1.1alpha+20120614-2.1

Versions of packages lintian recommends:
ii  dpkg 1.18.4
ii  libperlio-gzip-perl  0.19-1+b1
ii  perl 5.22.1-3
ii  perl-modules-5.22 [libautodie-perl]  5.22.1-3

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.4
ii  libhtml-parser-perl3.71-2+b1
ii  libtext-template-perl  1.46-1
ii  libyaml-perl   1.15-1

-- no debconf information

Bug#805824: Team maintenance in Debian Science for pdl? (Was: pdl: Fails to build with GSL 2)

[Andreas Tille]

Hi Henning,

since it would be great to fix #805824 soon which seems pretty easy
considering the patch I would like to offer an NMU.  However, it would
be even more sensible to move the package under Debian Science team
maintenance and maintain it in Debian Science Git since it is part of
several Debian Science tasks (astronomy, numericalcomputation and
viewing).  If I do not hear anything from you until end of this week
I would go on to move pdl in Debian Science Git, add you as Uploader
and do a team upload (rather than an NMU).

What do you think?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#802284: closed by Guido Günther <a...@sigxcpu.org> (Re: [PATCH] gbp rpm: mock chroot builder)

[Guido Günther]

On Tue, Jan 12, 2016 at 05:38:47PM +1100, Ben Finney wrote:
> Control: reopen -1
> Control: found -1  git-buildpackage/0.7.1
> 
> On 08-Jan-2016, Debian Bug Tracking System wrote:
> > This is an automatic notification regarding your Bug report
> > which was filed against the git-buildpackage package:
> > 
> > #802284: git-buildpackage: should assemble overlay before issuing 
> > 'debian/rules' commands
> > 
> > It has been closed by Guido Günther .
> 
> I think this bug report was closed in error; the message that closes
> this report does not seem to address the bug.

Yept, the bug I meant to close was 796198, sorry and thanks for spotting this.

Cheers,
 -- Guido

Bug#807190: please upload cnrun2-2.0.2 (fixes #807190)

[andrei zavada]

Yaroslav et al,

There was indeed a bug in 2.0.2. I used to think that modern C++ is so
strict that once you get your stuff to compile with -Werror, it will
fly.  I might have to reconsider this assumption, though..

That said and fixed, here's
http://johnhommer.com/academic/code/cnrun/source/deb/cnrun_2.0.3-1.dsc,
which also depends on libgsl-dev | libgsl0-dev as you suggested.

Humbly asking to retry upload,
Andrei

On Mon, 4 Jan 2016 09:12:58 -0500
Yaroslav Halchenko  wrote:

> On Sun, 03 Jan 2016, andrei zavada wrote:
> 
> > Here's a new version of cnrun2 which builds with the new libgsl-dev:
> > http://johnhommer.com/academic/code/cnrun/source/deb/cnrun_2.0.2-1.dsc.  
> 
> as I have recommended before I think there should be both old and new
> versions of libgsl listed so we could build backports make it
> 
> libgsl2-dev | libgsl0-dev | libgsl-dev
> 
> since we have to list real package(s) first and then virtual one...
> actually that libgsl-dev is not virtual so may be
> 
> libgsl-dev | libgsl0-dev
> 
> would suffice
> 
> nevertheless build fails for me with
> 
> -63.30183855115; 0.020799230593354; 0.99375010742719;
> 0.049435076669742
> 
> Putout:
>  (put out unit "LN/bin/bash: line 6: 31501 Segmentation fault
> (core dumped) LUA_CPATH="./?.so;$LUA_CPATH"
> LD_PRELOAD=../../../src/libcnrun/.libs/libcnrun.so.2.0.0:$LD_PRELOAD
> lua ../example1.lua Makefile:990: recipe for target 'test' failed
> make[1]: *** [test] Error 139 make[1]: Leaving directory
> '/build/cnrun-2.0.2' dh_auto_test: make -j1 test returned exit code 2
> debian/rules:9: recipe for target 'build' failed make: *** [build]
> Error 2
> 



pgp1E_2LYfe3V.pgp
Description: OpenPGP digital signature

Bug#741223: Simplifying the patch

[Sunil Mohan Adapa]

On Tuesday 12 January 2016 01:04 AM, Petter Reinholdtsen wrote:
> [Sunil Mohan Adapa]
>> With the proposed approach, we will have both the ways to mount and use,
>> that is, revert to an older snapshot.
>>
>> 1) Use 'btrfs set-default' to set the default subvolume and reboot.
>>
>> 2) Change the arguments to mount in fstab and kernel boot parmeters like
>> before using 'subvol=' and 'subvolid='.
>>
>> Both methods will have the same result of mounting the desired
>> subvolume.  The latter appoarch is harder for automated tools to handle.
>>  Snapper (possibly most other tools) use the first method.
> 
> My point was that the root snapshot changing should be possible to do
> from grub, in case the default root is broken.  I suspect that is only
> possible with metod 2) mentioned above.

I misunderstood.

Mount arguments take precedence over default subvolume.  So, manual
overriding using method 2) should still be possible.

-- 
Sunil



signature.asc
Description: OpenPGP digital signature

Bug#810776: Please update golang-x-text to latest upstream version

[Potter, Tim (Converged Cloud)]

Package: golang-x-text
Owner: Tim Potter 
X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org
Severity: wishlist

In updating golang-google-grpc-dev, it turns out that one of the dependencies, 
golang-x-text
also needs to be updated to the latest upstream version.


Thanks,

Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#810778: fancontrol: sensor detection order can change and invalidate /etc/fancontrol

[Neal Murphy]

Package: fancontrol
Version: 1:3.3.5-2
Severity: normal
Tags: patch

Now and again, Jessie detects the sensors on my mainboard (Asus M5A99FX-Pro
R2.0) in a different order. This change in order requires that /etc/fancontrol
be editted to account for the change before the fans can be controlled.

To fix it, I added var DEVMAP to the config in the form "DEVMAP=CPU=k10temp
MBOARD=it8721", and changed all instances of 'hwmon0' to MBOARD and all
instances of hwmon1 to CPU. Then I hacked /usr/sbin/fancontrol to add edit the
config vars to remove this layer of abstraction. The mapping is not performed
if DEVMAP is not defined in--or is commented out of--the config file. DEVMAP
need contain only those sensors that need to be dynamically mapped.

The result is that fancontrol now dynamically determines which hwmonN goes with
which sensor; detection order no longer matters. It also removes a lot of the
confusion from the config file, provided good pseudonames are used.

Note that this depends on the existence of /sys/class/hwmon/hwmon*/device/name;
thus it may not be a universal solution. I assumed that the .../device/name
files always exist for the CPU and the mainboard.

I did not address /usr/sbin/pwmconfig.

Aside, I think--but am not certain--that the failure of fancontrol to start is
not detected/reported at startup; the failure doesn't seem to be reported
anywhere in /var/log/.



-- 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/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages fancontrol depends on:
ii  init-system-helpers  1.22
ii  lsb-base 4.1+Debian13+nmu1

fancontrol recommends no packages.

fancontrol suggests no packages.

-- no debconf information
# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=.2
DEVMAP=CPU=k10temp MBOARD=it8721
DEVNAME=CPU=k10temp MBOARD=it8721
DEVPATH=CPU=devices/pci:00/:00:18.3 MBOARD=devices/platform/it87.656
FCTEMPS=MBOARD/device/pwm3=MBOARD/device/temp1_input 
MBOARD/device/pwm1=CPU/device/temp1_input
FCFANS=MBOARD/device/pwm3=MBOARD/device/fan2_input 
MBOARD/device/pwm1=MBOARD/device/fan1_input
MINTEMP=MBOARD/device/pwm3=35 MBOARD/device/pwm1=30
MAXTEMP=MBOARD/device/pwm3=55 MBOARD/device/pwm1=55
MINSTART=MBOARD/device/pwm3=90 MBOARD/device/pwm1=0
MINSTOP=MBOARD/device/pwm3=50 MBOARD/device/pwm1=0
MINPWM=MBOARD/device/pwm3=0 MBOARD/device/pwm1=0
MAXPWM=MBOARD/device/pwm3=255 MBOARD/device/pwm1=255
--- /usr/sbin/fancontrol-	2015-12-17 02:44:00.0 -0500
+++ /usr/sbin/fancontrol	2016-01-12 00:43:44.0 -0500
@@ -55,6 +55,7 @@
 	fi
 
 	# grep configuration from file
+	DEVMAP=`egrep '^DEVMAP=.*$' $1 | sed -e 's/DEVMAP= *//g'`
 	INTERVAL=`egrep '^INTERVAL=.*$' $1 | sed -e 's/INTERVAL=//g'`
 	DEVPATH=`egrep '^DEVPATH=.*$' $1 | sed -e 's/DEVPATH= *//g'`
 	DEVNAME=`egrep '^DEVNAME=.*$' $1 | sed -e 's/DEVNAME= *//g'`
@@ -68,6 +69,39 @@
 	MINPWM=`egrep '^MINPWM=.*$' $1 | sed -e 's/MINPWM=//g'`
 	MAXPWM=`egrep '^MAXPWM=.*$' $1 | sed -e 's/MAXPWM=//g'`
 
+	# if DEVMAP is non-null, map the pseudonames in DEVMAP to the real names
+	if [ ! -z "$DEVMAP" ]; then
+		declare -A MONMAP
+		pushd /sys/class/hwmon
+		for mondev in *; do
+			if [ -e "$mondev/device/name" ]; then
+for monnam in $DEVMAP; do
+	OIFS=$IFS; IFS="="
+	set $monnam
+	IFS=$OIFS
+	if [ "$2" == `cat "$mondev/device/name"` ]; then
+		MONMAP[$1]=$mondev
+		break;
+	fi
+done
+			fi
+		done
+		# edit the config VARs
+		for pname in ${!MONMAP[@]}; do
+			DEVNAME=${DEVNAME//$pname/${MONMAP[$pname]}}
+			DEVPATH=${DEVPATH//$pname/${MONMAP[$pname]}}
+			FCTEMPS=${FCTEMPS//$pname/${MONMAP[$pname]}}
+			FCFANS=${FCFANS//$pname/${MONMAP[$pname]}}
+			MINTEMP=${MINTEMP//$pname/${MONMAP[$pname]}}
+			MAXTEMP=${MAXTEMP//$pname/${MONMAP[$pname]}}
+			MINSTART=${MINSTART//$pname/${MONMAP[$pname]}}
+			MINSTOP=${MINSTOP//$pname/${MONMAP[$pname]}}
+			MINPWM=${MINPWM//$pname/${MONMAP[$pname]}}
+			MAXPWM=${MAXPWM//$pname/${MONMAP[$pname]}}
+		done
+		popd
+	fi
+
 	# Check whether all mandatory settings are set
 	if [[ -z ${INTERVAL} || -z ${FCTEMPS} || -z ${MINTEMP} || -z ${MAXTEMP} || -z ${MINSTART} || -z ${MINSTOP} ]]
 	then