Bug#821767: fio: Crashes with alignment error on ARM

[Remy Oudompheng]

Package: fio
Version: 2.1.11-2
Severity: important
Tags: upstream

Dear Maintainer,

I am unable to use fio on a armhf system because it crashes with the
following error:

$ fio test.fio
rand-read: (groupid=1, jobs=1): err= 0: pid=23829: Tue Apr 19 07:37:07 2016
  read : io=32768KB, bw=3353.1KB/s, iops=838, runt=  9770msec
slat (usec): min=1, max=236, avg= 1.91, stdev= 2.61
clat (usec): min=1505, max=16993, avg=4762.37, stdev=408.08
 lat (usec): min=1741, max=16995, avg=4764.28, stdev=407.86
zsh: bus error  fio test.fio

In dmesg output I see:
[29512.892409] Alignment trap: not handling instruction ed937b00 at [<0001e2b0>]
[29512.894041] Unhandled fault: alignment exception (0x011) at 0x000e3526

It seems that the bug was fixed by the upstream developer in version 2.1.14:
see this commit and following ones:

commit 24081c9bea3dae81103f57b4ba897006886d24f9
Author: Jens Axboe 
Date:   Mon Oct 20 10:52:21 2014 -0600

stat: ensure that the fp fields are 64-bit aligned

Signed-off-by: Jens Axboe 

-- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)

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

Versions of packages fio depends on:
ii  libaio1  0.3.110-1
ii  libc62.19-18+deb8u4
ii  libibverbs1  1.1.8-1.1
ii  librados20.80.7-2+deb8u1
ii  librbd1  0.80.7-2+deb8u1
ii  librdmacm1   1.0.19.1-1
ii  python   2.7.9-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

fio recommends no packages.

Versions of packages fio suggests:
pn  gnuplot  

-- no debconf information

Bug#821763: xserver-xorg-video-radeon: LibreOffice Preferences UI font corruption on AMD A6-1450 APU/Radeon HD 8250

[Michel Dänzer]

On 19.04.2016 13:24, J Mo wrote:
> Package: xserver-xorg-video-radeon
> Version: 1:7.7.0-1
> Severity: normal
> 
> Example image:
> http://jmomo.net/files/snapshot_LibreOffice_fonts_broken-2.png
> 
> Notice the blocks under "Menu" in the middle-right where letters should be in 
> the UI.
> 
> The hardware is a Zotac ZBox CA320 which has a AMD A6-1450 APU (Radeon HD 
> 8250).

Looks like https://bugs.freedesktop.org/show_bug.cgi?id=63397 .


> I pulled the SSD from this system and ran it on other hardware with a 
> different
> (NVidia) GPU and the artifacts went away.

Which drivers were used on the Nvidia GPU? If it wasn't the nouveau
kernel driver and the Xorg modesetting driver, it would be interesting
if you could try that combination to see if it happens with that as
well. That could narrow down where the bug is.



-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

Bug#821592: phpmyadmin: PHP 7.0 Transition

[Michal Čihař]

Hi Ondřej

Dne 18.4.2016 v 22:59 Ondřej Surý napsal(a):
> Package: phpmyadmin
> Version: 4:4.6.0-1
> Severity: important
> User: pkg-php-ma...@lists.alioth.debian.org
> Usertags: php7.0-transition
> 
> Dear maintainer(s),
> 
> this bug is a part of ongoing php7.0 transition.  It is filled as
> important, but the severity will be bumped to serious within quite short
> (~month) timeframe as the transition was announced almost 3 months ago.
> 
> The phpmyadmin package currently depends on libapache2-mod-php5
> libapache2-mod-php5filter php5 php5-cgi php5-cli php5-common php5-fpm
> php5-mysql php5-mysqlnd .

The only reason for this is to allow building packages for older distros
from same sources. Indeed the current solution is not really working
well, but I haven't found better. For example it doesn't prevent user
installing php5-mysql together with php7.0-cgi, what really doesn't lead
to working setup in current sid where both PHP versions are available.

-- 
Michal Čihař | http://cihar.com/ | https://weblate.org/



signature.asc
Description: OpenPGP digital signature

Bug#821766: gle-graphics: FTBFS on hurd-i386, but previously did

[Tobias Frost]

Package: gle-graphics
Version: 4.2.5-4
Severity: normal

Your package FTBFS on hurd, but previously build. Would be great if you could 
take a look.

https://buildd.debian.org/status/fetch.php?pkg=gle-graphics=hurd-i386=4.2.5-4=1459285516

Snippet:

make[2]: Leaving directory '/«PKGBUILDDIR»'
echo 2016-03-29 > gle-refman/title/source_date.tex
faketime -f "2016-03-29 09:48:58" make doc
sem_open: Operation not supported
debian/rules:31: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/«PKGBUILDDIR»'


Did not check, but maybe the doc generation could be moved to Build-Indep?
(which would have other benefits, as it reduced Build-Depends and is 
porter-friendly)

Thanks!

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

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

Bug#821746: [Pkg-dns-devel] Bug#821746: dnsval: FTBFS on kFreeBSD: conflicting types for '__sym_ston' et al.

[Ondřej Surý]

Control: severity -1 normal
Control: found -1 dnsval/2.2-1

I will, just mind next time that FTBFS on non-release arch is not serious... 

-- 
Ondřej Surý 



On 19 Apr 2016 01:12, at 01:12, "Aaron M. Ucko"  wrote:
>Source: dnsval
>Version: 2.0-4
>Severity: serious
>Justification: fails to build from source (but built successfully in
>the past)
>
>Builds of dnsval on kFreeBSD have been failing:
>
>  res_debug.c:481:1: error: conflicting types for '__sym_ston'
>sym_ston(const struct RES_SYM_TYPE *syms, const char *name, int
>*success)
>   ^
>/usr/include/resolv.h:332:6: note: previous declaration of '__sym_ston'
>was here
>   int  sym_ston (const struct res_sym *, const char *, int *) __THROW;
>^
>  res_debug.c:502:1: error: conflicting types for '__sym_ntos'
>   sym_ntos(const struct RES_SYM_TYPE *syms, int number, int *success)
>   ^
>/usr/include/resolv.h:333:14: note: previous declaration of
>'__sym_ntos' was here
>   const char * sym_ntos (const struct res_sym *, int, int *) __THROW;
>^
>  res_debug.c:523:1: error: conflicting types for '__sym_ntop'
>   sym_ntop(const struct RES_SYM_TYPE *syms, int number, int *success)
>   ^
>/usr/include/resolv.h:334:14: note: previous declaration of
>'__sym_ntop' was here
>   const char * sym_ntop (const struct res_sym *, int, int *) __THROW;
>^
>
>Could you please take a look?
>
>Thanks!
>
>___
>pkg-dns-devel mailing list
>pkg-dns-de...@lists.alioth.debian.org
>https://lists.alioth.debian.org/mailman/listinfo/pkg-dns-devel

Bug#821765: fife: FTBS on kfreebsd-*, but previously built

[Tobias Frost]

Source: fife
Version: 0.3.5-1+b3
Severity: normal

The package built in the past, but now fails.
Please take a look.

https://buildd.debian.org/status/package.php?p=fife=sid

https://buildd.debian.org/status/fetch.php?pkg=fife=kfreebsd-amd64=0.3.5-1%2Bb3=1460107463
https://buildd.debian.org/status/fetch.php?pkg=fife=kfreebsd-i386=0.3.5-1%2Bb3=1460104530

snippet:

python2.7 /usr/bin/scons -C build-python2.7 fife-python -j2
scons: Entering directory `/«PKGBUILDDIR»/build-python2.7'
scons: Reading SConscript files ...
no platform-config found (searched build/gnukfreebsd10-config.py)
NameError: global name 'Exit' is not defined:
  File "/«PKGBUILDDIR»/build-python2.7/SConstruct", line 208:
platformConfig = utils.getPlatformConfig()
  File "/«PKGBUILDDIR»/build-python2.7/utils/scons/scons_utils.py", line 73:
Exit(1)
debian/rules:22: recipe for target 'debian/stamps/build-python2.7' failed


Maybe Scons related?

Thanks!

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

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

Bug#821764: aseprite: FTBFS on hurd-i386 but previously did

[Tobias Frost]

Package: aseprite
Version: 1.1.3+ds-3
Severity: normal

Buildllog:

https://buildd.debian.org/status/fetch.php?pkg=aseprite=hurd-i386=1.1.3%2Bds-3=1457974698

Seems to be a PATH_MAX issue,
See https://www.gnu.org/software/hurd/community/gsoc/project_ideas/maxpath.html
for hints fixing it..

Otherwise, please request removal from hurd...

Thanks!

--
tobi



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

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

Bug#821409: gtk+3.0: gtk3 apps seem to be graphically broken since the most recent updates

[Alan Baghumian]

Hi Michael,

See here:

https://www.bountysource.com/issues/28293692-selected-text-is-white-on-white-invisible-webkit1-gtk-3-19-7-adwaita

I had the same issue with Evolution in Parsix and upgrading webkitgtk to
2.4.10 fixed it.

Alan
On Apr 18, 2016 7:14 PM, "Michael Biebl"  wrote:

> Am 18.04.2016 um 18:09 schrieb Alan Baghumian:
> > Hi Guys,
> >
> > Regarding transparency of selected text in Evolution, the package needs
> > to be recompiled using webkitgtk 2.4.10+ and that will fix it.
>
> I thought webkit needed a rebuild against gtk 3.20, not evolution.
>
> Alan, can you clarify? Do you have any references?
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>

Bug#821730: samba: Cannot connect to Samba 4.2 server from OS X 10.11

[Tim Rogers]

Yes, I do. Is that incorrect?

[global]
workgroup = OHS
server string = File Server
netbios name = server-2

# security = user
map to guest = Bad User

...

Thank you.

On Mon, Apr 18, 2016 at 6:18 PM Andrew Bartlett  wrote:

> On Mon, 2016-04-18 at 21:41 +, Tim Rogers wrote:
> > Package: samba
> > Version: 2:4.2.10+dfsg-0+deb8u2
> > Severity: important
> >
> > Dear Maintainer,
> >
> > After upgrading from Samba 4.1 to Samba 4.2, I can no longer connect
> > to shares from OS X 10.11. Linux boxes (upgraded to Samba 4.2)
> > connect fine,
> > as does Windows 10.
> >
> > Samba logs show the following error for each connection attempt:
> >
> > [2016/04/15 12:40:07.087650,  1]
> > ../auth/ntlmssp/ntlmssp_server.c:908(ntlmssp_server_postauth)
> >   ntlmssp_server_postauth: invalid NTLMSSP_MIC for user=[GUEST]
> > domain=[] workstation=[ROGERS]
> > [2016/04/15 12:40:07.087709,  1] ../lib/util/util.c:559(dump_data)
> >   [] 67 7E 0E CB CE 77 2E 62   05 00 BD F6 E3 84 FB 27   g~...w.b
> > ...'
> > [2016/04/15 12:40:07.087747,  1] ../lib/util/util.c:559(dump_data)
> >   [] 43 AD 8C C7 E8 F7 0A 1C   06 A8 03 CB FC C8 17 38   C...
> > ...8
> >
> > I assume that there are configuration options for smb.conf which will
> > resolve this - but I can't find them. I can't find any clear
> > instructions in the
> > documentation, although it seems to suggest that such issues are
> > likely with this upgrade.
>
> Do you have 'map to guest = bad user' set in your smb.conf?
>
> Andrew Bartlett
>
> --
> Andrew Bartlett
> https://samba.org/~abartlet/
> Authentication Developer, Samba Team https://samba.org
> Samba Development and Support, Catalyst IT
> https://catalyst.net.nz/services/samba
>
>
>
>
>
>
>

Bug#821763: xserver-xorg-video-radeon: LibreOffice Preferences UI font corruption on AMD A6-1450 APU/Radeon HD 8250

[J Mo]

Package: xserver-xorg-video-radeon
Version: 1:7.7.0-1
Severity: normal

Example image:
http://jmomo.net/files/snapshot_LibreOffice_fonts_broken-2.png

Notice the blocks under "Menu" in the middle-right where letters should be in 
the UI.

The hardware is a Zotac ZBox CA320 which has a AMD A6-1450 APU (Radeon HD 8250).

I have been using the hardware for about two weeks now and this is the first 
graphical glitch I've seen, so this could be LibreOffice too. Let me know if 
yuo want me to refile on LibreOffice.

I pulled the SSD from this system and ran it on other hardware with a different 
(NVidia) GPU and the artifacts went away.




-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Temash [Radeon HD 8250/8280G] [1002:983d]

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.5.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160409 (Debian 5.3.1-14) ) #1 SMP Debian 4.5.1-1 (2016-04-14)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 21210 Apr 12 20:00 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 55352 Apr 18 17:15 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 4.920] (--) Log file renamed from "/var/log/Xorg.pid-652.log" to 
"/var/log/Xorg.0.log"
[ 4.922] 
X.Org X Server 1.18.3
Release Date: 2016-04-04
[ 4.922] X Protocol Version 11, Revision 0
[ 4.922] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[ 4.922] Current Operating System: Linux panic 4.5.0-1-amd64 #1 SMP Debian 
4.5.1-1 (2016-04-14) x86_64
[ 4.922] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.5.0-1-amd64 
root=UUID=bf908df3-15d5-4683-839e-2dbea668e58d ro ipv6.disable=1 quiet
[ 4.922] Build Date: 05 April 2016  07:00:43AM
[ 4.922] xorg-server 2:1.18.3-1 (http://www.debian.org/support) 
[ 4.922] Current version of pixman: 0.33.6
[ 4.922]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 4.922] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4.923] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 18 17:14:22 
2016
[ 4.924] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 4.925] (==) No Layout section.  Using the first Screen section.
[ 4.926] (==) No screen section available. Using defaults.
[ 4.926] (**) |-->Screen "Default Screen Section" (0)
[ 4.926] (**) |   |-->Monitor ""
[ 4.926] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 4.927] (==) Automatically adding devices
[ 4.927] (==) Automatically enabling devices
[ 4.927] (==) Automatically adding GPU devices
[ 4.927] (==) Max clients allowed: 256, resource mask: 0x1f
[ 4.930] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 4.930]Entry deleted from font path.
[ 4.933] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 4.933] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 4.933] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 4.933] (II) Loader magic: 0x55d0638cadc0
[ 4.933] (II) Module ABI versions:
[ 4.933]X.Org ANSI C Emulation: 0.4
[ 4.933]X.Org Video Driver: 20.0
[ 4.933]X.Org XInput driver : 22.1
[ 4.933]X.Org Server Extension : 9.0
[ 4.937] (++) using VT number 7

[ 4.937] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[ 4.938] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 5.597] (--) PCI:*(0:0:1:0) 1002:983d:19da:b208 rev 0, Mem @ 
0xc000/268435456, 0xd000/8388608, 0xfeb0/262144, I/O @ 
0xf000/256, BIOS @ 0x/131072
[ 5.597] (II) LoadModule: "glx"
[ 5.598] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 5.613] (II) Module glx: vendor="X.Org Foundation"
[ 5.613]compiled for 1.18.3, module version = 1.0.0
[ 5.616]ABI class: X.Org Server Extension, version 9.0
[ 5.616] (==) AIGLX 

Bug#821334: approx: 'apt-get update' yields 'Err http://approx wheezy-updates/main amd64 Packages'

[David Christensen]

On 04/18/2016 07:14 AM, Eric Cooper wrote:

I'm not sure, but due to the way mirrors work, it's often difficult to
reproduce some problems, and they often just "go away" when you retry.

For example, the ftp.us.debian.org mirror is actually round-robined
among multiple sites.  A longstanding problem with approx is that it
resolves the name on each transfer (because I'm lazy and just pass the
name to curl).  If it resolves to different sites between the Release
file and the Packages file, and those two sites are not in sync,
the update can fail with checksum errors.

Any way, I'm going to mark this closed as of version 5.5 unless you
object.  Sorry for the inconvenience.


Please leave the bug report open.


I typically run up to a half dozen machines for my SOHO LAN.  I've run 
Approx off and on for the past several years, and have experienced these 
kinds of insolvable problems.  When it works, great.  When it doesn't 
work, I shut it down and do redundant downloads (netinst and/or 
updates).  Recently, I started doing Debian Live builds.  So, now I need 
Approx even more.



Perhaps if Approx saved the IP address after the first name lookup and 
used that for all transfers, Approx would be more reliable (?).  Or, 
does round-robin make this impossible?



As a work-around, can I specify a host that is not round-robined in my 
approx.conf file?  How do I find such hosts?



Any other ideas?


David

Bug#821424: pulseaudio: Do not put normal users on group audio

[Christian PERRIER]

Control: reassign -1 user-setup

Quoting Felipe Sateler (fsate...@debian.org):
> Control: reassign -1 debian-installer
> 
> On 18 April 2016 at 13:06, Corcodel Marian  wrote:
> 
> > Any way pulseaudio is default sound server on debian and suggest to do not 
> > put
> > users on audio group because cross interference with alsa programs, now 
> > alsa is
> > for power users and pulseaudio is on default.
> 
> Pulseaudio does not add the user to the audio group. I'm guessing the
> installer does, so I reassign there.


Adding the *first created* user to so-called "useful" groups is done
by user-setup.

We'll need a detaailed explanantion abou twhy this shouldn't be done
anymore, including all possible use cases of the installer.




signature.asc
Description: PGP signature

Bug#821762: RFS: ublock-origin/1.6.8+dfsg-1 -- general-purpose lightweight ads, malware, trackers blocker

[Sean Whitton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for an update to ublock-origin.

* Package name: ublock-origin
  Version : 1.6.8+dfsg-1
  Upstream Author : Raymond Hill
* URL : https://github.com/gorhill/uBlock
* License : GPL-3+
  Section : web

Changes since the last upload:

  * Package new upstream release.
  * Explicitly include copyright for Raymond Hill.
  * Updates for upstream's repository reorganisation:
- Patch tools/make-assets.sh
- Update debian/clean-dfsg.sh
- Update debian/copyright
- Explain changes README.source.
  * Bump standards version to 3.9.8 (no changes required).

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/u/ublock-origin/ublock-origin_1.6.8+dfsg-1.dsc

Or build it with gbp:

gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-emacsen/pkg/ublock-origin.git
cd ublock-origin
gbp buildpackage

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#821260: RFS: python-adventure/1.4-1 [ITP], Bug#821260: RFS: python-adventure/1.4-1 [ITP]

[Ben Finney]

Howdy Markus,

(Limiting distribution just to the RFS bug report to discuss the
sponsorship.)

Markus Koschany  writes:

> Am 18.04.2016 um 02:15 schrieb Ben Finney:
> > Those are in end-line comments (“# foo”). My understanding is that
> > end-line comments with that syntax are permitted in any Debian
> > control files.
>
> cme check dpkg made me aware of this and it probably refers to:
> https://www.debian.org/doc/debian-policy/ch-controlfields#s-controlsyntax

That's right, thank you for showing it to me.

I don't think that restriction is justified, and have now filed
bug#821363 to effect a change in that policy.

Until then, the specification has the meaning as you described it. I
have removed those comment lines from ‘debian/copyright’.

> CC-BY-4.0 is a good choice and would help to avoid any confusion.

Done.

> I can live with the python3-adventure split off but as Bas already
> said I also find it unlikely that another program will ever make use
> of it.

Another reason was that Pybuild and dh_python make it much easier to
handle the package build when there is a ‘python3-libraryname’ package
containing the library.

However, you have convinced me that it is misleading to present a
‘python3-adventure’ when the package does not install a public module to
be imported.

I have merged the Python library back into the main application binary
package.

> Could you remove those ^L form feed characters please?

Done.


> desktop-file-validate is a useful tool to ensure compliance with the
> freedesktop specification. The written text can be found at
>
> https://specifications.freedesktop.org/menu-spec/latest/

Thank you. I have corrected the badly-formatted field in the desktop
entry.

> Another suggestion: The recommended location for hicolor icons is
> /usr/share/icons/hicolor.

These are deliberately low-colour icons (8 colours and 16 colours) to
reduce the file size; but there doesn't appear to be an XDG standard
place for low-colour icons.

> If you resize your icons to 256x256 you could install them to
> /usr/share/icons/hicolor/256x256/apps and replace the absolute icon
> path in your desktop file with the icon name.

Done.


The resulting updated source package is available:

$ dget -x 
http://mentors.debian.net/debian/pool/main/p/python-adventure/python-adventure_1.4-1.dsc

-- 
 \  “Every valuable human being must be a radical and a rebel, for |
  `\  what he must aim at is to make things better than they are.” |
_o__)  —Niels Bohr |
Ben Finney 

Bug#819826: #819826 was resolved incorrectly

[Michel Dänzer]

Hi Michael,


you resolved #819826 by replacing

 find $config -name libstdc++.so.6\* -execdir rm -f {} \;

with

 find $runtime -name libstdc++.so.6\* -execdir rm -f {} \;

Unfortunately, the latter isn't sufficient, because some Steam games
ship their own stale copies of libraries in their own directories,
outside of the Steam runtime. Come to think of it, maybe even the former
wasn't sufficient if the user chose to install games outside of the
Steam config directory?

For the same reason, I'm afraid that not using the Steam runtime isn't
sufficient to avoid the stale library problem after all. Looks like the
only effective solution may be to force the system versions of affected
libraries via LD_PRELOAD.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

Bug#821761: linux-image-4.5.0-1-amd64: [regression] switching from gdm Xorg vt to normal virtual console corrupts display until reboot

[Paul Wise]

Package: src:linux
Version: 4.5.1-1
Severity: normal

When I upgraded to linux 4.5.1 I found that switching from a gdm Xorg
vt to normal virtual console corrupts the display until I reboot. The
display corruption is not static and is mostly black with some fuzz
around the sides and sometimes pixels from the gdm vt are in the top of
the display. This happens both with and without an external display
plugged into the VGA port on the laptop. This does not happen with 4.4
but it does happen with 4.6 from experimental. I couldn't find any way
to work around this issue other than a reboot.

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

** Model information
sys_vendor: LENOVO
product_name: 0831CTO
product_version: ThinkPad X201 Tablet
chassis_vendor: LENOVO
chassis_version: Not Available
bios_vendor: LENOVO
bios_version: 6QET62WW (1.32 )
board_vendor: LENOVO
board_name: 0831CTO
board_version: Not Available

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller 
[8086:0044] (rev 02)
Subsystem: Lenovo Core Processor DRAM Controller [17aa:2193]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor 
Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA 
controller])
Subsystem: Lenovo Core Processor Integrated Graphics Controller 
[17aa:215a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 10.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range BC, TimeoutDis+, LTR-, OBFF 
Not Supported ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [90] Subsystem: Lenovo 5 Series/3400 Series Chipset PCI 
Express Root Port 1 [17aa:2164]
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 5 [8086:3b4a] (rev 06) (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#821760: Please pull in xserver-xorg-input-libinput

[Michael Biebl]

Package: xserver-xorg-input-all
Version: 1:7.7+14
Severity: normal

Hi,

GNOME 3.20 has dropped support for non-libinput mouse configurations [1]
So any configuration changes you make in gnome-control-center won't have
any effect unless xserver-xorg-input-libinput is installed, e.g. my
tap-to-click touchpad settings had no effect otherwise [2]

We quickly discussed this issue on #debian-gnome IRC where I suggested
that we let one of the GNOME packages pull in
xserver-xorg-input-libinput.

pochu mentioned that doing this via xserver-xorg-input-all might be
nicer. What's the state of xserver-xorg-input-libinput, Timo? Do you
consider it ready for the masses and do we want to have it installed
(and enabled) by default?

Regards,
Michael


[1] 
https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=66c211ff24bec6a938d6a6a0dd8730f4689ef383
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821354
-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages xserver-xorg-input-all depends on:
ii  xserver-xorg-input-evdev  1:2.10.1-1+b1
ii  xserver-xorg-input-synaptics  1.8.3-1+b1
ii  xserver-xorg-input-vmmouse1:13.1.0-1+b1

Versions of packages xserver-xorg-input-all recommends:
ii  xserver-xorg-input-wacom  0.30.0-1+b1

xserver-xorg-input-all suggests no packages.

-- no debconf information

Bug#821270: Review of firefox-branding-iceweasel

[Sean Whitton]

Hello,

I just took a closer look at your debian/rules file.  You don't need the
boilerplate.  This is enough:

,
| #!/usr/bin/make -f
| 
| %:
|   dh $@ --with xul-ext --parallel
| 
| override_dh_auto_install:
|   xpi-pack ./xpi-build ./build.xpi
|   install-xpi ./build.xpi
`

However, since this is a native package, would you consider editing your
Makefile so that dh_xul-ext can do your whole build for you?  Take a
look at the source package y-u-no-validate.  It uses this main Makefile
target:

,
| %:
|   dh $@ --with xul-ext --buildsystem=xul_ext --sourcedirectory=src
`

There is an override, but it's just something minor.  This works because
the source code is organised in a standard way, but your code seems to
be organised in a non-standard way which is why you need a complex
Makefile and dh overrides.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#821409: gtk+3.0: gtk3 apps seem to be graphically broken since the most recent updates

[Michael Biebl]

Am 18.04.2016 um 18:09 schrieb Alan Baghumian:
> Hi Guys,
> 
> Regarding transparency of selected text in Evolution, the package needs
> to be recompiled using webkitgtk 2.4.10+ and that will fix it.

I thought webkit needed a rebuild against gtk 3.20, not evolution.

Alan, can you clarify? Do you have any references?

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



signature.asc
Description: OpenPGP digital signature

Bug#821759: Iceweasel does not warn about website asking to store data for offline use

[Alef Farah]

Package: iceweasel
Version: 44.0.2-1

There is an option in iceweasel, under "about:preferences#advanced",
which says "Tell me when a website asks to store data for offline use",
which consists of a checkbox. It is expected that, when the box is
checked, a dialog would appear when a website wishes to store data for offline
use. What seems to happen is nothing: No dialog and no warning.

Steps to reproduce: Check the box as aforementioned, then visit a
website that stores data for offline use. Some examples that are present
in my browser:

http://www.thesun.co.uk
https://web.whatsapp.com
https://web.telegram.org

I am using Debian stretch/sid.

Bug#821758: Transmission "Move to top" has no effect on the download queue

[Alef Farah]

Package: transmission-gtk
Version: 2.84-3

Opening the context menu of an item in transmission's GUI, then
selecting "Queue", then "Move to top", seems to have no effect on the
actual ordering of the downloads. Steps to reproduce:

Limit the number of downloads by using the menu bar: "Edit > Preferences
> Downloading > Maximum active downloads", add at least N + 1
torrents, where N is the download limit, then try to move the queued
item to the top as aforementioned.

The expected result is that the item starts downloading. The actual
result is no change at all.

I am using Debian stretch/sid.

Bug#821442: schroot: operation not permitted (only with 4.5 kernel)

[Barry Warsaw]

On Apr 18, 2016, at 09:40 PM, James McCoy wrote:

>I've been seeing something similar.  Am I right to assume that these are
>union-type=overlay?  If so, this seems to be a change in the kernel.

Yep, union-type=overlay.


pgpyRCcXhRcjK.pgp
Description: OpenPGP digital signature

Bug#821757: wheezy-pu: package xapian-core/1.2.12-2

[Olly Betts]

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

I'd like to update xapian-core in wheezy to fix a bug which can cause
database corruption.  This is triggered by certain usage patterns, and
the recoll package is known to be affected:

https://bugs.debian.org/808610

I've attached a debdiff for the proposed upload.  The patch added is
from the upstream git repo - it's been on git master since 2015-04-28,
and in upstream stable releases since 2015-05-20.

There's already a pending request to address this in jessie:

https://bugs.debian.org/820059

The patch for wheezy is exactly the same as that for jessie, except with
a "quilt refresh" to adjust the line numbers of some of the hunks.

Cheers,
Olly
diff -Nru xapian-core-1.2.12/debian/changelog 
xapian-core-1.2.12/debian/changelog
--- xapian-core-1.2.12/debian/changelog 2012-12-11 17:22:23.0 +1300
+++ xapian-core-1.2.12/debian/changelog 2016-04-19 13:14:15.0 +1200
@@ -1,3 +1,10 @@
+xapian-core (1.2.12-2+deb7u1) oldstable; urgency=medium
+
+  * New patch increment-cursor-version-on-cancel-or-reopen.patch fixing
+possible database corruption, especially with recoll.  (Closes: #808610)
+
+ -- Olly Betts   Tue, 19 Apr 2016 13:13:31 +1200
+
 xapian-core (1.2.12-2) unstable; urgency=low
 
   * New patch fix-db-write-lock.patch which fixes database write locking to
diff -Nru 
xapian-core-1.2.12/debian/patches/increment-cursor-version-on-cancel-or-reopen.patch
 
xapian-core-1.2.12/debian/patches/increment-cursor-version-on-cancel-or-reopen.patch
--- 
xapian-core-1.2.12/debian/patches/increment-cursor-version-on-cancel-or-reopen.patch
1970-01-01 12:00:00.0 +1200
+++ 
xapian-core-1.2.12/debian/patches/increment-cursor-version-on-cancel-or-reopen.patch
2016-04-19 13:13:25.0 +1200
@@ -0,0 +1,197 @@
+Description: Increment cursor version of cancel or reopen
+ Potentially increment the cursor version on cancel() or when the database is
+ reopened, and flag the current cursor version as used when a cursor is
+ rebuilt.
+ .
+ Fixes database corruption issues with certain usage patterns, which recoll
+ can trigger.
+Author: Olly Betts 
+Origin: upstream, 
https://trac.xapian.org/changeset/826d1a19cc356e7bf66c1681626e70af32967447/git 
and 
https://trac.xapian.org/changeset/d784290ce015958474f965817f7a41f1483c3e03/git
+Bug: https://trac.xapian.org/ticket/675
+Bug-Debian: https://bugs.debian.org/808610
+Forwarded: https://trac.xapian.org/ticket/675
+Last-Update: 2016-04-19
+
+--- a/backends/brass/brass_cursor.cc
 b/backends/brass/brass_cursor.cc
+@@ -1,7 +1,7 @@
+ /* brass_cursor.cc: Btree cursor implementation
+  *
+  * Copyright 1999,2000,2001 BrightStation PLC
+- * Copyright 2002,2003,2004,2005,2006,2007,2008,2009,2010,2012 Olly Betts
++ * Copyright 2002,2003,2004,2005,2006,2007,2008,2009,2010,2012,2015 Olly Betts
+  *
+  * This program is free software; you can redistribute it and/or
+  * modify it under the terms of the GNU General Public License as
+@@ -99,6 +99,7 @@
+ C[level].n = B->C[level].n;
+ C[level].p = B->C[level].p;
+ version = B->cursor_version;
++B->cursor_created_since_last_modification = true;
+ }
+ 
+ BrassCursor::~BrassCursor()
+--- a/backends/brass/brass_table.cc
 b/backends/brass/brass_table.cc
+@@ -1435,6 +1435,11 @@
+ 
+ base_letter = ch;
+ 
++if (cursor_created_since_last_modification) {
++  cursor_created_since_last_modification = false;
++  ++cursor_version;
++}
++
+ /* ready to open the main file */
+ 
+ RETURN(true);
+@@ -1975,6 +1980,11 @@
+ changed_n = 0;
+ changed_c = DIR_START;
+ seq_count = SEQ_START_POINT;
++
++if (cursor_created_since_last_modification) {
++  cursor_created_since_last_modification = false;
++  ++cursor_version;
++}
+ }
+ 
+ / B-tree reading /
+--- a/backends/chert/chert_cursor.cc
 b/backends/chert/chert_cursor.cc
+@@ -1,7 +1,7 @@
+ /* chert_cursor.cc: Btree cursor implementation
+  *
+  * Copyright 1999,2000,2001 BrightStation PLC
+- * Copyright 2002,2003,2004,2005,2006,2007,2008,2009,2010,2012 Olly Betts
++ * Copyright 2002,2003,2004,2005,2006,2007,2008,2009,2010,2012,2015 Olly Betts
+  *
+  * This program is free software; you can redistribute it and/or
+  * modify it under the terms of the GNU General Public License as
+@@ -97,6 +97,7 @@
+ C[level].n = B->C[level].n;
+ C[level].p = B->C[level].p;
+ version = B->cursor_version;
++B->cursor_created_since_last_modification = true;
+ }
+ 
+ ChertCursor::~ChertCursor()
+--- a/backends/chert/chert_table.cc
 b/backends/chert/chert_table.cc
+@@ -1438,6 +1438,11 @@
+ 
+ base_letter = ch;
+ 
++if (cursor_created_since_last_modification) {
++  cursor_created_since_last_modification = false;
++  ++cursor_version;
++}
++
+ /* ready to open the main file */
+ 
+ RETURN(true);

Bug#821312: RFS: classic-theme-restorer/1.5.0-1 -- customize the new Iceweasel look

[Sean Whitton]

Hello,

On Mon, Apr 18, 2016 at 05:30:37PM +0800, Paul Wise wrote:
> I suspect this should be s/Iceweasel/Firefox/ now?

Thanks.  Fixed in git ready for the next upload.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#812395: u-boot-tools: sheevaplug /etc/fw_env.config - explain how env address depends on your version of u-boot.

[Rick Thomas]

>> If you could please provide a patch detailing exactly what you would
>> like changed, that would be appreciated.

It look like the latest u-boot-tools has exactly what I would have said.  Very 
sorry for taking so long to get back.

I think this bug can be closed now.

Thanks!
Rick

Bug#821442: schroot: operation not permitted (only with 4.5 kernel)

[James McCoy]

On Mon, Apr 18, 2016 at 02:14:58PM -0400, Barry Warsaw wrote:
> With today's dist-upgrade, I am unable to enter an existing or newly
> created chroot, nor am I able to sbuild or adt-run with the chroot.
> 
> I had an existing sid-amd64 chroot which I could not enter.  I then
> removed the chroot and recreated it with mk-sbuild.  Now I get:
> 
> % schroot -u root -c sid-amd64
> E: 15binfmt: update-binfmts: unable to open
> /var/run/schroot/mount/sid-amd64-98db94f4-3bc6-4948-95a6-57a8e986bba9/bin/sh:
> Operation not permitted
> E: 20copyfiles: cp: cannot create regular file
> '/var/run/schroot/mount/sid-amd64-98db94f4-3bc6-4948-95a6-57a8e986bba9/etc/resolv.conf':
> Operation not permitted
> E: 15binfmt: update-binfmts: unable to open
> /var/run/schroot/mount/sid-amd64-98db94f4-3bc6-4948-95a6-57a8e986bba9/bin/sh:
> Operation not permitted
> E: sid-amd64-98db94f4-3bc6-4948-95a6-57a8e986bba9: Chroot setup
> failed: stage=setup-start

I've been seeing something similar.  Am I right to assume that these are
union-type=overlay?  If so, this seems to be a change in the kernel.

Running linux-image-4.5.0-1-amd64, I see various failures using overlay
but rebooting into linux-image-4.4.0-1-amd64 I am again able to use
schroot/sbuild.

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

Bug#821730: samba: Cannot connect to Samba 4.2 server from OS X 10.11

[Andrew Bartlett]

On Mon, 2016-04-18 at 21:41 +, Tim Rogers wrote:
> Package: samba
> Version: 2:4.2.10+dfsg-0+deb8u2
> Severity: important
> 
> Dear Maintainer,
> 
> After upgrading from Samba 4.1 to Samba 4.2, I can no longer connect
> to shares from OS X 10.11. Linux boxes (upgraded to Samba 4.2)
> connect fine, 
> as does Windows 10. 
> 
> Samba logs show the following error for each connection attempt:
> 
> [2016/04/15 12:40:07.087650,  1]
> ../auth/ntlmssp/ntlmssp_server.c:908(ntlmssp_server_postauth)
>   ntlmssp_server_postauth: invalid NTLMSSP_MIC for user=[GUEST]
> domain=[] workstation=[ROGERS]
> [2016/04/15 12:40:07.087709,  1] ../lib/util/util.c:559(dump_data)
>   [] 67 7E 0E CB CE 77 2E 62   05 00 BD F6 E3 84 FB 27   g~...w.b
> ...'
> [2016/04/15 12:40:07.087747,  1] ../lib/util/util.c:559(dump_data)
>   [] 43 AD 8C C7 E8 F7 0A 1C   06 A8 03 CB FC C8 17 38   C...
> ...8
> 
> I assume that there are configuration options for smb.conf which will
> resolve this - but I can't find them. I can't find any clear
> instructions in the 
> documentation, although it seems to suggest that such issues are
> likely with this upgrade.

Do you have 'map to guest = bad user' set in your smb.conf?

Andrew Bartlett

-- 
Andrew Bartlett
https://samba.org/~abartlet/
Authentication Developer, Samba Team https://samba.org
Samba Development and Support, Catalyst IT   
https://catalyst.net.nz/services/samba

Bug#821756: plasma-desktop: System Settings crashes often after being closed

[J Mo]

Package: plasma-desktop
Version: 4:5.4.3-1
Severity: minor

System Settings crashes very often, but not always, after being closed. As far 
as I can tell, this does not affect the saving of settings.

Note that I am using the Classic Tree view.

The bug reporter says it's a segfault(11) and provides the following 
probably-useless debug info:


Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f41df05a8c0 (LWP 2728))]

Thread 6 (Thread 0x7f41bfbe1700 (LWP 2730)):
#0  0x7f41d8c2904f in pthread_cond_wait@@GLIBC_2.3.2 () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f41c34b3af3 in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x7f41c34b3247 in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#3  0x7f41d8c23454 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#4  0x7f41db7a2ecd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 5 (Thread 0x7f41a0aef700 (LWP 3207)):
#0  0x7f41db799e4d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f41d870232c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f41d870243c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f41d8702479 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f41d8728b75 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f41d8c23454 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#6  0x7f41db7a2ecd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7f4197ffe700 (LWP 3208)):
#0  0x7f41d8746a90 in g_mutex_unlock () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f41d8701cea in g_main_context_check () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f41d87022d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f41d87026b2 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f41bb7ac906 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x7f41d8728b75 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f41d8c23454 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#7  0x7f41db7a2ecd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f41957d3700 (LWP 3402)):
#0  0x7f41db799e4d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f41d870232c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f41d870243c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f41dc0b5a5b in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f41dc05cd6a in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f41dbe79854 in QThread::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f41dbe7e7fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f41d8c23454 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x7f41db7a2ecd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7f41b4054700 (LWP 4181)):
#0  0x7f41c72b4a27 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#1  0x7f41c72b4da9 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#2  0x7f41c72b563a in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#3  0x7f41c7926337 in pa_mainloop_dispatch () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f41c792673c in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f41c79267e0 in pa_mainloop_run () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f41c7934a29 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7f41c72c5648 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#8  0x7f41d8c23454 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#9  0x7f41db7a2ecd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f41df05a8c0 (LWP 2728)):
[KCrash Handler]
#6  0x022619b0 in ?? ()
#7  0x7f41dc0921a9 in QObject::disconnect(QObject const*, char const*, 
QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f41bde7c976 in KParts::PartManager::~PartManager() () from 
/usr/lib/x86_64-linux-gnu/libKF5Parts.so.5
#9  0x7f41bde7cb29 in KParts::PartManager::~PartManager() () from 
/usr/lib/x86_64-linux-gnu/libKF5Parts.so.5
#10 0x7f41dc08c4eb in QObjectPrivate::deleteChildren() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f41dc095d60 in QObject::~QObject() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f41be5cac9b in KHTMLPart::~KHTMLPart() () from 
/usr/lib/x86_64-linux-gnu/libKF5KHtml.so.5
#13 0x7f41be5cadb9 in KHTMLPart::~KHTMLPart() () from 

Bug#820059: jessie-pu: package xapian-core/1.2.19-1

[Olly Betts]

Control: tags -1 + patch
Control: tags -1 - moreinfo
 
On Wed, Apr 06, 2016 at 09:35:46PM +0100, Adam D. Barratt wrote:
> On Tue, 2016-04-05 at 17:06 +1200, Olly Betts wrote:
> > The attached patch is from the upstream git repo - it's been on git
> > master since 2015-04-28, and in upstream stable releases since
> > 2015-05-20.
> 
> In isolation the patch looks okay, but in order to confirm a upload
> please can we have a debdiff of the proposed source package, as built
> and tested on Jessie?

Attached.

Cheers,
Olly
diff -Nru xapian-core-1.2.19/debian/changelog 
xapian-core-1.2.19/debian/changelog
--- xapian-core-1.2.19/debian/changelog 2014-10-22 00:52:12.0 +1300
+++ xapian-core-1.2.19/debian/changelog 2016-04-19 12:09:08.0 +1200
@@ -1,3 +1,10 @@
+xapian-core (1.2.19-1+deb8u1) stable; urgency=medium
+
+  * New patch increment-cursor-version-on-cancel-or-reopen.patch fixing
+possible database corruption, especially with recoll.  (Closes: #808610)
+
+ -- Olly Betts   Tue, 19 Apr 2016 11:49:06 +1200
+
 xapian-core (1.2.19-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru 
xapian-core-1.2.19/debian/patches/increment-cursor-version-on-cancel-or-reopen.patch
 
xapian-core-1.2.19/debian/patches/increment-cursor-version-on-cancel-or-reopen.patch
--- 
xapian-core-1.2.19/debian/patches/increment-cursor-version-on-cancel-or-reopen.patch
1970-01-01 12:00:00.0 +1200
+++ 
xapian-core-1.2.19/debian/patches/increment-cursor-version-on-cancel-or-reopen.patch
2016-04-05 16:53:19.0 +1200
@@ -0,0 +1,197 @@
+Description: Increment cursor version of cancel or reopen
+ Potentially increment the cursor version on cancel() or when the database is
+ reopened, and flag the current cursor version as used when a cursor is
+ rebuilt.
+ .
+ Fixes database corruption issues with certain usage patterns, which recoll
+ can trigger.
+Author: Olly Betts 
+Origin: upstream, 
https://trac.xapian.org/changeset/826d1a19cc356e7bf66c1681626e70af32967447/git 
and 
https://trac.xapian.org/changeset/d784290ce015958474f965817f7a41f1483c3e03/git
+Bug: https://trac.xapian.org/ticket/675
+Bug-Debian: https://bugs.debian.org/808610
+Forwarded: https://trac.xapian.org/ticket/675
+Last-Update: 2016-04-05
+
+--- a/backends/brass/brass_cursor.cc
 b/backends/brass/brass_cursor.cc
+@@ -1,7 +1,7 @@
+ /* brass_cursor.cc: Btree cursor implementation
+  *
+  * Copyright 1999,2000,2001 BrightStation PLC
+- * Copyright 2002,2003,2004,2005,2006,2007,2008,2009,2010,2012 Olly Betts
++ * Copyright 2002,2003,2004,2005,2006,2007,2008,2009,2010,2012,2015 Olly Betts
+  *
+  * This program is free software; you can redistribute it and/or
+  * modify it under the terms of the GNU General Public License as
+@@ -99,6 +99,7 @@
+ C[level].n = B->C[level].n;
+ C[level].p = B->C[level].p;
+ version = B->cursor_version;
++B->cursor_created_since_last_modification = true;
+ }
+ 
+ BrassCursor::~BrassCursor()
+--- a/backends/brass/brass_table.cc
 b/backends/brass/brass_table.cc
+@@ -1446,6 +1446,11 @@
+ 
+ base_letter = ch;
+ 
++if (cursor_created_since_last_modification) {
++  cursor_created_since_last_modification = false;
++  ++cursor_version;
++}
++
+ /* ready to open the main file */
+ 
+ RETURN(true);
+@@ -1985,6 +1990,11 @@
+ changed_n = 0;
+ changed_c = DIR_START;
+ seq_count = SEQ_START_POINT;
++
++if (cursor_created_since_last_modification) {
++  cursor_created_since_last_modification = false;
++  ++cursor_version;
++}
+ }
+ 
+ / B-tree reading /
+--- a/backends/chert/chert_cursor.cc
 b/backends/chert/chert_cursor.cc
+@@ -1,7 +1,7 @@
+ /* chert_cursor.cc: Btree cursor implementation
+  *
+  * Copyright 1999,2000,2001 BrightStation PLC
+- * Copyright 2002,2003,2004,2005,2006,2007,2008,2009,2010,2012 Olly Betts
++ * Copyright 2002,2003,2004,2005,2006,2007,2008,2009,2010,2012,2015 Olly Betts
+  *
+  * This program is free software; you can redistribute it and/or
+  * modify it under the terms of the GNU General Public License as
+@@ -97,6 +97,7 @@
+ C[level].n = B->C[level].n;
+ C[level].p = B->C[level].p;
+ version = B->cursor_version;
++B->cursor_created_since_last_modification = true;
+ }
+ 
+ ChertCursor::~ChertCursor()
+--- a/backends/chert/chert_table.cc
 b/backends/chert/chert_table.cc
+@@ -1449,6 +1449,11 @@
+ 
+ base_letter = ch;
+ 
++if (cursor_created_since_last_modification) {
++  cursor_created_since_last_modification = false;
++  ++cursor_version;
++}
++
+ /* ready to open the main file */
+ 
+ RETURN(true);
+@@ -2007,6 +2012,11 @@
+ changed_n = 0;
+ changed_c = DIR_START;
+ seq_count = SEQ_START_POINT;
++
++if (cursor_created_since_last_modification) {
++  cursor_created_since_last_modification = false;
++  ++cursor_version;
++}
+ }
+ 
+ / B-tree reading 

Bug#821755: plasma-desktop: Task Switchers are broken: "The Window Switcher installation is broken, resources are missing"

[J Mo]

Package: plasma-desktop
Version: 4:5.4.3-1
Severity: normal

In System Settings > Workspace > Window Management > Task Switcher.

All non-default Task Switchers installed via the star (Get Hot New Stuff) seem 
to be broken and most result in an error message:

"The Window Switcher installation is broken, resources are missing. Contact 
your distribution about this."

I suspect all of these task switchers are not compatible with KDE 5. I'm not 
sure why they are being presented as valid options when they don't work.



Also the default task switcher (Breeze) is terrible, which is why I wanted to 
change it in the first place, but that's not relevant.



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

Kernel: Linux 4.5.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 plasma-desktop depends on:
ii  breeze  4:5.4.3-1
ii  kactivities 5.16.0-1
ii  kde-cli-tools   4:5.4.3-1
ii  kded5   5.16.0-1
ii  kio 5.16.0-1
ii  libc6   2.22-6
ii  libcanberra00.30-3
ii  libfontconfig1  2.11.0-6.4
ii  libgcc1 1:5.3.1-14
ii  libkf5activities5   5.16.0-1
ii  libkf5activitiesexperimentalstats1  4:5.4.3-1
ii  libkf5archive5  5.16.0-1
ii  libkf5auth5 5.16.0-1
ii  libkf5baloo55.16.0-1
ii  libkf5bookmarks55.16.0-1
ii  libkf5codecs5   5.16.0-1
ii  libkf5completion5   5.16.0-1
ii  libkf5configcore5   5.16.0-1
ii  libkf5configgui55.16.0-1
ii  libkf5configwidgets55.16.0-1
ii  libkf5coreaddons5   5.16.0-1
ii  libkf5dbusaddons5   5.16.0-1
ii  libkf5emoticons55.16.0-2
ii  libkf5globalaccel5  5.16.0-1
ii  libkf5guiaddons55.16.0-1
ii  libkf5i18n5 5.16.0-1
ii  libkf5iconthemes5   5.16.0-1
ii  libkf5itemviews55.16.0-1
ii  libkf5jobwidgets5   5.16.0-1
ii  libkf5kcmutils5 5.16.0-1
ii  libkf5kdelibs4support5  5.16.0-1
ii  libkf5kiocore5  5.16.0-1
ii  libkf5kiofilewidgets5   5.16.0-1
ii  libkf5kiowidgets5   5.16.0-1
ii  libkf5newstuff5 5.16.0-1
ii  libkf5notifications55.16.0-1
ii  libkf5notifyconfig5 5.16.0-1
ii  libkf5parts55.16.0-1
ii  libkf5people5   5.16.0-1
ii  libkf5peoplewidgets55.16.0-1
ii  libkf5plasma5   5.16.0-1
ii  libkf5plasmaquick5  5.16.0-1
ii  libkf5quickaddons5  5.16.0-1
ii  libkf5runner5   5.16.0-1
ii  libkf5service-bin   5.16.0-1
ii  libkf5service5  5.16.0-1
ii  libkf5solid55.16.0-1
ii  libkf5sonnetui5 5.16.0-1
ii  libkf5wallet-bin5.16.0-1
ii  libkf5wallet5   5.16.0-1
ii  libkf5widgetsaddons55.16.0-1
ii  libkf5windowsystem5 5.16.0-1
ii  libkf5xmlgui5   5.16.0-1
ii  libkfontinst5   4:5.4.3-1
ii  libkfontinstui5 4:5.4.3-1
ii  libkworkspace5-54:5.4.3-2
ii  libphonon4qt5-4 4:4.8.3-2
ii  libpulse-mainloop-glib0 8.0-2
ii  libpulse0   8.0-2
ii  libqt5concurrent5   5.5.1+dfsg-16+b1
ii  libqt5core5a5.5.1+dfsg-16+b1
ii  libqt5dbus5 5.5.1+dfsg-16+b1
ii  libqt5gui5  5.5.1+dfsg-16+b1
ii  libqt5network5  5.5.1+dfsg-16+b1
ii  libqt5printsupport5 5.5.1+dfsg-16+b1
ii  libqt5qml5  5.5.1-3
ii  libqt5quick55.5.1-3
ii  libqt5svg5  5.5.1-2
ii  libqt5widgets5  5.5.1+dfsg-16+b1
ii  libqt5x11extras55.5.1-3
ii  libqt5xml5  5.5.1+dfsg-16+b1
ii  libstdc++6  5.3.1-14
ii  libtaskmanager5 4:5.4.3-2
ii  libx11-62:1.6.3-1
ii  libx11-xcb1 2:1.6.3-1
ii  libxcb-record0  1.11.1-1
ii  libxcb-xkb1 1.11.1-1
ii  libxcb1 1.11.1-1
ii  libxcursor1   

Bug#809524: ITP: golang-github-hpcloud-tail -- Go package for reading from continously updated files (tail -f)

[Alexandre Viau]

Hello Daniel,

Sorry I couldn't reply to your messages lately.

Go ahead and take over the ITP! :)
--
Alexandre Viau
av...@debian.org


On Mon, Apr 18, 2016 at 3:11 PM, Daniel Stender  wrote:
> I've begun to work on that package and pushed into a new group repo:
> https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-hpcloud-tail.git
>
> I would complete the Packer dependencies with this package, however I can't
> hijack the ITP without confirmation.
>
> Share maintenance?
>
> Best,
> Daniel
>
> --
> 4096R/DF5182C8
> http://www.danielstender.com/blog/

Bug#821754: plasma-desktop: Window shadows not being cleaned up when the windows move/disappear

[J Mo]

Package: plasma-desktop
Version: 4:5.4.3-1
Severity: minor

Sometimes window shadows are not being cleaned up properly.

Here is an example screenshot of the Application Launcher leaving a shadow 
behind which doesn't go away until something covers it:

http://jmomo.net/files/snapshot_KDE_shadows_left_behind1.png

The gray line is from the bottom of the menu.



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

Kernel: Linux 4.5.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 plasma-desktop depends on:
ii  breeze  4:5.4.3-1
ii  kactivities 5.16.0-1
ii  kde-cli-tools   4:5.4.3-1
ii  kded5   5.16.0-1
ii  kio 5.16.0-1
ii  libc6   2.22-6
ii  libcanberra00.30-3
ii  libfontconfig1  2.11.0-6.4
ii  libgcc1 1:5.3.1-14
ii  libkf5activities5   5.16.0-1
ii  libkf5activitiesexperimentalstats1  4:5.4.3-1
ii  libkf5archive5  5.16.0-1
ii  libkf5auth5 5.16.0-1
ii  libkf5baloo55.16.0-1
ii  libkf5bookmarks55.16.0-1
ii  libkf5codecs5   5.16.0-1
ii  libkf5completion5   5.16.0-1
ii  libkf5configcore5   5.16.0-1
ii  libkf5configgui55.16.0-1
ii  libkf5configwidgets55.16.0-1
ii  libkf5coreaddons5   5.16.0-1
ii  libkf5dbusaddons5   5.16.0-1
ii  libkf5emoticons55.16.0-2
ii  libkf5globalaccel5  5.16.0-1
ii  libkf5guiaddons55.16.0-1
ii  libkf5i18n5 5.16.0-1
ii  libkf5iconthemes5   5.16.0-1
ii  libkf5itemviews55.16.0-1
ii  libkf5jobwidgets5   5.16.0-1
ii  libkf5kcmutils5 5.16.0-1
ii  libkf5kdelibs4support5  5.16.0-1
ii  libkf5kiocore5  5.16.0-1
ii  libkf5kiofilewidgets5   5.16.0-1
ii  libkf5kiowidgets5   5.16.0-1
ii  libkf5newstuff5 5.16.0-1
ii  libkf5notifications55.16.0-1
ii  libkf5notifyconfig5 5.16.0-1
ii  libkf5parts55.16.0-1
ii  libkf5people5   5.16.0-1
ii  libkf5peoplewidgets55.16.0-1
ii  libkf5plasma5   5.16.0-1
ii  libkf5plasmaquick5  5.16.0-1
ii  libkf5quickaddons5  5.16.0-1
ii  libkf5runner5   5.16.0-1
ii  libkf5service-bin   5.16.0-1
ii  libkf5service5  5.16.0-1
ii  libkf5solid55.16.0-1
ii  libkf5sonnetui5 5.16.0-1
ii  libkf5wallet-bin5.16.0-1
ii  libkf5wallet5   5.16.0-1
ii  libkf5widgetsaddons55.16.0-1
ii  libkf5windowsystem5 5.16.0-1
ii  libkf5xmlgui5   5.16.0-1
ii  libkfontinst5   4:5.4.3-1
ii  libkfontinstui5 4:5.4.3-1
ii  libkworkspace5-54:5.4.3-2
ii  libphonon4qt5-4 4:4.8.3-2
ii  libpulse-mainloop-glib0 8.0-2
ii  libpulse0   8.0-2
ii  libqt5concurrent5   5.5.1+dfsg-16+b1
ii  libqt5core5a5.5.1+dfsg-16+b1
ii  libqt5dbus5 5.5.1+dfsg-16+b1
ii  libqt5gui5  5.5.1+dfsg-16+b1
ii  libqt5network5  5.5.1+dfsg-16+b1
ii  libqt5printsupport5 5.5.1+dfsg-16+b1
ii  libqt5qml5  5.5.1-3
ii  libqt5quick55.5.1-3
ii  libqt5svg5  5.5.1-2
ii  libqt5widgets5  5.5.1+dfsg-16+b1
ii  libqt5x11extras55.5.1-3
ii  libqt5xml5  5.5.1+dfsg-16+b1
ii  libstdc++6  5.3.1-14
ii  libtaskmanager5 4:5.4.3-2
ii  libx11-62:1.6.3-1
ii  libx11-xcb1 2:1.6.3-1
ii  libxcb-record0  1.11.1-1
ii  libxcb-xkb1 1.11.1-1
ii  libxcb1 1.11.1-1
ii  libxcursor1 1:1.1.14-1+b1
ii  libxfixes3  1:5.0.1-2+b2
ii  libxi6  2:1.7.6-1
ii  libxkbfile1 1:1.0.9-2
ii  oxygen-sounds   4:5.4.3-1
ii  phonon4qt5  4:4.8.3-2
ii  

Bug#818050: /usr/bin/colormgr: cannot profile monitor with gretag i1-display2

[Christopher James Halse Rogers]

Hm. I see that you don't have colord-sensor-argyll installed. I think 
that might be required to drive your calibration device.


Can you please try installing it and see if calibration works?

It's a Suggests: rather than a Recommends: because it depends on 
argyll, which is almost 100MB on-disc and is not necessary for quite a 
lot of users, but we could certainly fix the error reported.

Bug#821753: plasma-desktop: System Settings: Login Screen (SDDM) item weird/broken

[J Mo]

Package: plasma-desktop
Version: 4:5.4.3-1
Severity: normal

I am getting weird problems when trying to configure Login Screen (SDDM) 
options under System Settings.  Many times the entire UI will freeze up when 
switching between the "Theme" and "Advanced" tabs, and switching between other 
configuration options.

Sometimes it works, sometimes it doesn't. It's very intermittent and usually 
selecting a different System Settings option will clear it up. Just keep 
clicking around back and forth. Between tabs and options and the UI will start 
freezing up.

Also would be nice if there were some alternative login screens or I could 
change that obnoxious colorful background.  =)


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

Kernel: Linux 4.5.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 plasma-desktop depends on:
ii  breeze  4:5.4.3-1
ii  kactivities 5.16.0-1
ii  kde-cli-tools   4:5.4.3-1
ii  kded5   5.16.0-1
ii  kio 5.16.0-1
ii  libc6   2.22-6
ii  libcanberra00.30-3
ii  libfontconfig1  2.11.0-6.4
ii  libgcc1 1:5.3.1-14
ii  libkf5activities5   5.16.0-1
ii  libkf5activitiesexperimentalstats1  4:5.4.3-1
ii  libkf5archive5  5.16.0-1
ii  libkf5auth5 5.16.0-1
ii  libkf5baloo55.16.0-1
ii  libkf5bookmarks55.16.0-1
ii  libkf5codecs5   5.16.0-1
ii  libkf5completion5   5.16.0-1
ii  libkf5configcore5   5.16.0-1
ii  libkf5configgui55.16.0-1
ii  libkf5configwidgets55.16.0-1
ii  libkf5coreaddons5   5.16.0-1
ii  libkf5dbusaddons5   5.16.0-1
ii  libkf5emoticons55.16.0-2
ii  libkf5globalaccel5  5.16.0-1
ii  libkf5guiaddons55.16.0-1
ii  libkf5i18n5 5.16.0-1
ii  libkf5iconthemes5   5.16.0-1
ii  libkf5itemviews55.16.0-1
ii  libkf5jobwidgets5   5.16.0-1
ii  libkf5kcmutils5 5.16.0-1
ii  libkf5kdelibs4support5  5.16.0-1
ii  libkf5kiocore5  5.16.0-1
ii  libkf5kiofilewidgets5   5.16.0-1
ii  libkf5kiowidgets5   5.16.0-1
ii  libkf5newstuff5 5.16.0-1
ii  libkf5notifications55.16.0-1
ii  libkf5notifyconfig5 5.16.0-1
ii  libkf5parts55.16.0-1
ii  libkf5people5   5.16.0-1
ii  libkf5peoplewidgets55.16.0-1
ii  libkf5plasma5   5.16.0-1
ii  libkf5plasmaquick5  5.16.0-1
ii  libkf5quickaddons5  5.16.0-1
ii  libkf5runner5   5.16.0-1
ii  libkf5service-bin   5.16.0-1
ii  libkf5service5  5.16.0-1
ii  libkf5solid55.16.0-1
ii  libkf5sonnetui5 5.16.0-1
ii  libkf5wallet-bin5.16.0-1
ii  libkf5wallet5   5.16.0-1
ii  libkf5widgetsaddons55.16.0-1
ii  libkf5windowsystem5 5.16.0-1
ii  libkf5xmlgui5   5.16.0-1
ii  libkfontinst5   4:5.4.3-1
ii  libkfontinstui5 4:5.4.3-1
ii  libkworkspace5-54:5.4.3-2
ii  libphonon4qt5-4 4:4.8.3-2
ii  libpulse-mainloop-glib0 8.0-2
ii  libpulse0   8.0-2
ii  libqt5concurrent5   5.5.1+dfsg-16+b1
ii  libqt5core5a5.5.1+dfsg-16+b1
ii  libqt5dbus5 5.5.1+dfsg-16+b1
ii  libqt5gui5  5.5.1+dfsg-16+b1
ii  libqt5network5  5.5.1+dfsg-16+b1
ii  libqt5printsupport5 5.5.1+dfsg-16+b1
ii  libqt5qml5  5.5.1-3
ii  libqt5quick55.5.1-3
ii  libqt5svg5  5.5.1-2
ii  libqt5widgets5  5.5.1+dfsg-16+b1
ii  libqt5x11extras55.5.1-3
ii  libqt5xml5  5.5.1+dfsg-16+b1
ii  libstdc++6  5.3.1-14
ii  libtaskmanager5 4:5.4.3-2
ii  libx11-62:1.6.3-1
ii  libx11-xcb1 2:1.6.3-1
ii  libxcb-record0  1.11.1-1
ii  libxcb-xkb1 1.11.1-1
ii  libxcb1 

Bug#821752: Failure to build shared libraries

[Philippe Grégoire]

Package: bmake
Version: 20160220-2

bmake fails to build shared libraries, due to bsd.lib.mk. The
attached patch adds the appropriate -Wl flag.

Thanks,

P. Grégoire
diff --git a/mk/lib.mk b/mk/lib.mk
index c76fd9b..c1f4045 100644
--- a/mk/lib.mk
+++ b/mk/lib.mk
@@ -118,7 +118,7 @@ APICFLAGS?= -k
 # Platform-independent linker flags for ELF shared libraries
 .if ${OBJECT_FMT} == "ELF"
 SHLIB_SOVERSION=	${SHLIB_MAJOR}
-SHLIB_SHFLAGS=		-soname lib${LIB}.so.${SHLIB_SOVERSION}
+SHLIB_SHFLAGS=		-Wl,-soname=lib${LIB}.so.${SHLIB_SOVERSION}
 SHLIB_LDSTARTFILE?=	/usr/lib/crtbeginS.o
 SHLIB_LDENDFILE?=	/usr/lib/crtendS.o
 .endif

Bug#821751: plasma-desktop: Font Management: Unable to delete/disable fonts

[J Mo]

Package: plasma-desktop
Version: 4:5.4.3-1
Severity: normal

I am not able to delete or disable fonts.

System Settings > Appearance > Font > Font Management
Select multiple fonts
Delete them
"Error" "Backend died, but has been restarted. Please try again."
Somtetimes /usr/lib/x86_64-linux-gnu/libexec/kauth/fontinst starts 
eating 100% CPU on a core.
It is noteworthy that sometimes the action succeeds, especially if 
doing them one-by-one, but I didn't see a pattern.

Verified on a 2nd system with different hardware too.



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

Kernel: Linux 4.5.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 plasma-desktop depends on:
ii  breeze  4:5.4.3-1
ii  kactivities 5.16.0-1
ii  kde-cli-tools   4:5.4.3-1
ii  kded5   5.16.0-1
ii  kio 5.16.0-1
ii  libc6   2.22-6
ii  libcanberra00.30-3
ii  libfontconfig1  2.11.0-6.4
ii  libgcc1 1:5.3.1-14
ii  libkf5activities5   5.16.0-1
ii  libkf5activitiesexperimentalstats1  4:5.4.3-1
ii  libkf5archive5  5.16.0-1
ii  libkf5auth5 5.16.0-1
ii  libkf5baloo55.16.0-1
ii  libkf5bookmarks55.16.0-1
ii  libkf5codecs5   5.16.0-1
ii  libkf5completion5   5.16.0-1
ii  libkf5configcore5   5.16.0-1
ii  libkf5configgui55.16.0-1
ii  libkf5configwidgets55.16.0-1
ii  libkf5coreaddons5   5.16.0-1
ii  libkf5dbusaddons5   5.16.0-1
ii  libkf5emoticons55.16.0-2
ii  libkf5globalaccel5  5.16.0-1
ii  libkf5guiaddons55.16.0-1
ii  libkf5i18n5 5.16.0-1
ii  libkf5iconthemes5   5.16.0-1
ii  libkf5itemviews55.16.0-1
ii  libkf5jobwidgets5   5.16.0-1
ii  libkf5kcmutils5 5.16.0-1
ii  libkf5kdelibs4support5  5.16.0-1
ii  libkf5kiocore5  5.16.0-1
ii  libkf5kiofilewidgets5   5.16.0-1
ii  libkf5kiowidgets5   5.16.0-1
ii  libkf5newstuff5 5.16.0-1
ii  libkf5notifications55.16.0-1
ii  libkf5notifyconfig5 5.16.0-1
ii  libkf5parts55.16.0-1
ii  libkf5people5   5.16.0-1
ii  libkf5peoplewidgets55.16.0-1
ii  libkf5plasma5   5.16.0-1
ii  libkf5plasmaquick5  5.16.0-1
ii  libkf5quickaddons5  5.16.0-1
ii  libkf5runner5   5.16.0-1
ii  libkf5service-bin   5.16.0-1
ii  libkf5service5  5.16.0-1
ii  libkf5solid55.16.0-1
ii  libkf5sonnetui5 5.16.0-1
ii  libkf5wallet-bin5.16.0-1
ii  libkf5wallet5   5.16.0-1
ii  libkf5widgetsaddons55.16.0-1
ii  libkf5windowsystem5 5.16.0-1
ii  libkf5xmlgui5   5.16.0-1
ii  libkfontinst5   4:5.4.3-1
ii  libkfontinstui5 4:5.4.3-1
ii  libkworkspace5-54:5.4.3-2
ii  libphonon4qt5-4 4:4.8.3-2
ii  libpulse-mainloop-glib0 8.0-2
ii  libpulse0   8.0-2
ii  libqt5concurrent5   5.5.1+dfsg-16+b1
ii  libqt5core5a5.5.1+dfsg-16+b1
ii  libqt5dbus5 5.5.1+dfsg-16+b1
ii  libqt5gui5  5.5.1+dfsg-16+b1
ii  libqt5network5  5.5.1+dfsg-16+b1
ii  libqt5printsupport5 5.5.1+dfsg-16+b1
ii  libqt5qml5  5.5.1-3
ii  libqt5quick55.5.1-3
ii  libqt5svg5  5.5.1-2
ii  libqt5widgets5  5.5.1+dfsg-16+b1
ii  libqt5x11extras55.5.1-3
ii  libqt5xml5  5.5.1+dfsg-16+b1
ii  libstdc++6  5.3.1-14
ii  libtaskmanager5 4:5.4.3-2
ii  libx11-62:1.6.3-1
ii  libx11-xcb1 2:1.6.3-1
ii  libxcb-record0  1.11.1-1
ii  libxcb-xkb1 1.11.1-1
ii  libxcb1 1.11.1-1
ii  libxcursor1 1:1.1.14-1+b1
ii  libxfixes3  1:5.0.1-2+b2

Bug#821750: option to follow symlinks

[Antoine Beaupré]

Package: ncdu
Version: 1.10-1
Severity: wishlist

I understand why ncdu doesn't count symlinks by default, but in some
cases, it would be very useful to do so. My use case is specifically
about git-annex repositories, which make heavy use of symlinks.

There is a patch in the upstream bugtracker, but the thread has been
inactive for a few years now:

https://dev.yorhel.nl/ncdu/bug/16
https://p.blicky.net/j3py5

A copy of the patch is attached.

-- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable'), (1, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages ncdu depends on:
ii  libc6 2.19-18+deb8u4
ii  libncursesw5  5.9+20140913-1+b1
ii  libtinfo5 5.9+20140913-1+b1

ncdu recommends no packages.

ncdu suggests no packages.

-- no debconf information
diff --git a/src/dir_scan.c b/src/dir_scan.c
index 6c38eeb..0b9d679 100644
--- a/src/dir_scan.c
+++ b/src/dir_scan.c
@@ -188,7 +188,7 @@ static int dir_scan_item(struct dir *d) {
   if(exclude_match(dir_curpath))
 d->flags |= FF_EXL;
 
-  if(!(d->flags & (FF_ERR|FF_EXL)) && lstat(d->name, )) {
+  if(!(d->flags & (FF_ERR|FF_EXL)) && (follow_symlinks ? stat : lstat)(d->name, )) {
 d->flags |= FF_ERR;
 dir_setlasterr(dir_curpath);
   }
diff --git a/src/global.h b/src/global.h
index e298f1e..4ef8bc6 100644
--- a/src/global.h
+++ b/src/global.h
@@ -84,6 +84,8 @@ struct dir {
 extern int pstate;
 /* read-only flag */
 extern int read_only;
+/* Whether to follow symlinks */
+extern int follow_symlinks;
 /* minimum screen update interval when calculating, in ms */
 extern long update_delay;
 /* filter directories with CACHEDIR.TAG */
diff --git a/src/main.c b/src/main.c
index 2e30d25..5b5e5f1 100644
--- a/src/main.c
+++ b/src/main.c
@@ -39,6 +39,7 @@
 
 int pstate;
 int read_only = 0;
+int follow_symlinks = 0;
 long update_delay = 100;
 int cachedir_tags = 0;
 
@@ -119,6 +120,7 @@ static void argv_parse(int argc, char **argv) {
 { 'v', 0, "-v" },
 { 'x', 0, "-x" },
 { 'r', 0, "-r" },
+{ 'L', 0, "-L" },
 { 'o', 1, "-o" },
 { 'f', 1, "-f" },
 { '0', 0, "-0" },
@@ -159,6 +161,7 @@ static void argv_parse(int argc, char **argv) {
   exit(0);
 case 'x': dir_scan_smfs = 1; break;
 case 'r': read_only = 1; break;
+case 'L': follow_symlinks = 1; break;
 case 's': si = 1; break;
 case 'o': export = val; break;
 case 'f': import = val; break;

Bug#821231: Possible fix

[Dai]

I have been looking at the code using the gnome-packagekit-gnome-3.14 
source, and I inserted "ignore_updates_changed = TRUE;" at line 3009 of 
gpk-updateviewer.c just before the call to 
"gpk_update_viewer_get_new_update_array ();" recompiled and now the 
dialog box is not doubled up. I did not extensively test if this has any 
adverse affect to anything else, but it solved the issue for me.


Dai
*
***

Bug#821435: patchelf: FTBFS on mips*: tests fail: set-rpath.sh no-rpath.sh big-dynstr.sh set-rpath-library.sh

[Felipe Sateler]

Control: tags -1 upstream confirmed
Control: forwarded -1 https://github.com/NixOS/patchelf/issues/82
Control: retitle -1 patchelf: --set-rpath breaks binaries on mips*

Hi,

On 18 April 2016 at 14:40, Andreas Beckmann  wrote:
> Hi,
>
> patchelf FTBFS on mips* with some testsuite failures:

Thanks for the bug report. It appears patchelf never worked on mips.
I'm pondering asking for a removal there until this issue is fixed.

-- 

Saludos,
Felipe Sateler

Bug#821454: [pkg-go] Bug#821454: dh-golang: Position-independent executables (PIE)

[Michael Hudson-Doyle]

This is like the cross-compilation / CGO_ENABLED=0 situations:

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818651#10
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776401#27

I still don't really know of a good answer. I've been meaning to ask
upstream if they have any ideas about this, maybe I'll get around to
this today :-)

Cheers,
mwh

On 19 April 2016 at 07:06, Peter Colberg  wrote:
> Package: dh-golang
> Version: 1.15
> Severity: normal
>
> Dear Debian Go team,
>
> In response to the lintian warning hardening-no-pie, I am trying to
> build acmetool (#817091) as a position-independent executable (PIE).
>
> The Go compiler supports a -buildmode=pie since version 1.5.
>
> Building the package with this flag produces the following errror:
>
>   dpkg-buildpackage: source package acmetool
>   dpkg-buildpackage: source version 0.0.49-1
>   dpkg-buildpackage: source distribution unstable
>dpkg-source --before-build acmetool-0.0.49
>   dpkg-buildpackage: host architecture amd64
>fakeroot debian/rules clean
>   dh clean --buildsystem=golang --with=golang
>  dh_testdir -O--buildsystem=golang
>  dh_auto_clean -O--buildsystem=golang
>  dh_clean -O--buildsystem=golang
>dpkg-source -b acmetool-0.0.49
>   dpkg-source: info: using source format '3.0 (quilt)'
>   dpkg-source: info: building acmetool using existing 
> ./acmetool_0.0.49.orig.tar.gz
>   dpkg-source: info: building acmetool in acmetool_0.0.49-1.debian.tar.xz
>   dpkg-source: info: building acmetool in acmetool_0.0.49-1.dsc
>debian/rules build
>   dh build --buildsystem=golang --with=golang
>  dh_testdir -O--buildsystem=golang
>  dh_update_autotools_config -O--buildsystem=golang
>  dh_auto_configure -O--buildsystem=golang
>  debian/rules override_dh_auto_build
>   make[1]: Entering directory '/<>'
>   dh_auto_build -O--buildsystem=golang -- -buildmode=pie -ldflags "-X 
> github.com/hlandau/acme/hooks.DefaultPath=/etc/ac
> +me
>   go install -v -buildmode=pie -ldflags "-X 
> github.com/hlandau/acme/hooks.DefaultPath=/etc/acme/hooks -X github
> +.ci github.com/hlandau/acme/acmeapi/acmeendpoints 
> github.com/hlandau/acme/acmeapi/acmeutils
> +github.com/hlandau/acme/cmd/a/acme/redirector 
> github.com/hlandau/acme/responder github.com/hlandau/acme/solver
> +github.com/hlandau/acme/storage githu
>   runtime/internal/sys
>   go install runtime/internal/sys: mkdir /usr/lib/go/pkg/linux_amd64_shared: 
> permission denied
>   dh_auto_build: go install -v -buildmode=pie -ldflags -X 
> github.com/hlandau/acme/hooks.DefaultPath=/etc/acme/hooks -X
> +gicmeapi github.com/hlandau/acme/acmeapi/acmeendpoints 
> github.com/hlandau/acme/acmeapi/acmeutils
> +github.com/hlandau/acme/andau/acme/redirector 
> github.com/hlandau/acme/responder github.com/hlandau/acme/solver
> +github.com/hlandau/acme/storage
>   debian/rules:14: recipe for target 'override_dh_auto_build' failed
>   make[1]: *** [override_dh_auto_build] Error 1
>   make[1]: Leaving directory '/<>'
>   debian/rules:11: recipe for target 'build' failed
>   make: *** [build] Error 2
>   dpkg-buildpackage: error: debian/rules build gave error exit status 2
>
> Any ideas what is going wrong?
>
> It works fine if I compile from upstream:
>
>   git clone https://github.com/hlandau/acme github.com/hlandau/acme
>   cd github.com/hlandau/acme/cmd/acmetool
>   export GOPATH=$PWD
>   go get -v
>   go build -v -buildmode=pie
>
> Regards,
> Peter
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Bug#821321: libvorbisfile: ov_pcm_seek wrongly returns OV_EOF or segfaults sometimes

[Frank Heckenbach]

Hi Martin,

> Thank you for your bug report!
> 
> Judging from the code that reproduces the bug (two subsequent seeks to 
> 0) and from the related vorbis code you are mentioning, this sounds a 
> lot like #782831, which was fixed in 1.3.4-3. Could you confirm or 
> refute that theory by testing your code (I guess you have further 
> examples apart from the one you posted) with 1.3.4-3?

1.3.4-3 isn't on the main server anymore, but luckily I recently
learned about snapshot.debian.org. It may be old news for you, but
for anyone else who may be reading this report and doesn't know
about it, I fetched the following two files and rebuilt them
(together with the origial libvorbis_1.3.4.orig.tar.gz from jessie).
I didn't try 1.3.5 yet as I want to change as little as possible in
the system.

http://snapshot.debian.org/archive/debian/20151001T033412Z/pool/main/libv/libvorbis/libvorbis_1.3.4-3.dsc
http://snapshot.debian.org/archive/debian/20151001T033412Z/pool/main/libv/libvorbis/libvorbis_1.3.4-3.debian.tar.xz

It did indeed fix the test case, and also my real case where I found
the problem. I'll do some more tests soon and report if I find more
problems, but I hope not.

Thanks,
Frank

Bug#820708: [Pkg-pascal-devel] Bug#820708: Bug#820708: castle-game-engine: hardcoded libpng12 dependency

[Michalis Kamburelis]

  

  

>  For Debian packaging, it may make sense to just simplify and say  
 "let castle-game-engine recommend libpng". I'm just saying that it's  
 not a strict dependency for upstream.

>

> Not sure if I fully agree. If I understand correctly the packages that  
have a Build-Depends on cge need the Depends/Recommends on libpng (like  
view3dscene).  

  

Sure, it's correct that view3dscene "Recommends" the libpng. Because opening a
VRML/X3D file that uses a texture encoded in png is a very common case, it's
reasonable for a user to assume that "just installing view3dscene" will make
this possible.

  

And most games use png for textures/images, so they will want to "Depend" on
libpng. Otherwise they could not read png textures. (Which doesn't need to
cause a crash, a particular game may choose to turn it into a mere warning.)

What I meant to say, in my earlier mail, is that: if you somehow make a game
that doesn't use png (maybe it has no textures/images, or only in other
formats like jpg or ppm or dds), then it does not need to depend on libpng. It
will happily work on a system without libpng. So merely using CGE does not
*always* imply that you also need to have libpng at runtime.

Regards,

Michalis

Bug#821749: kgb-client: Support only notifying for "new to repo" commits in Git

[James McCoy]

Package: kgb-client
Version: 1.33-2
Severity: wishlist

The typical workflow I use for packaging in git is to work directly with
upstream sources and merge upstream tags into a Debian-specific branch
(c.f., https://anonscm.debian.org/cgit/pkg-vim/neovim.git).

I already have the post-receive hook filtering out any lines that match
refs/heads/master (i.e., upstream's code), which avoids floods for the
commit emails.  However, KGB still notifies for all of the upstream
commits that get pulled in by the merge, even though they're not "new"
to the repo when the merge commit is processed.

In #748397, it was suggested to use the squash_* git-config variables to
avoid the flood, but that's not very useful.  It forces me to remember
to push the merge commit on its own (so the related upstream commits are
squashed) and then continue pushing normally so there are typical
notices for packaging related commits.

Ideally, I'd like to handle this like git_multimail.py does, where a
specific commit is only notified when it is new to the repository,
not for every branch which contains the commit.

As a simpler/short-term solution, being able to notify the content that
“git log --ancestry-path old..new” shows would likely be a decent
compromise.  At least in my limited testing, that seems to avoid
notifying about every upstream commit while still including a
notification of the merge commit and any other commits to the packaging
branch.

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

Kernel: Linux 4.5.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)

Bug#821350: dh-golang: generates rubbish in Built-Using; errors on invocation

[Michael Hudson-Doyle]

The attached should fix this. I get this for rkt's Built-Using now:

 Built-Using: docker-registry (= 2.3.1~ds1-1), golang (= 2:1.6.1-2),
golang-context (= 0.0~git20140604.1.14f550f-1), golang-github-appc-cni
(= 0.2.0~rc0+dfsg-1), golang-github-appc-docker2aci (= 0.9.3+dfsg-1),
golang-github-appc-spec (= 0.7.4+dfsg-1),
golang-github-coreos-go-systemd (= 5-1),
golang-github-coreos-ioprogress (= 0.0~git20151023.0.4637e49-1),
golang-github-cznic-b (= 0.0~git20151027.0.01b13d7-1),
golang-github-cznic-bufs (= 0.0~git20140818.0.3dcccbd-1),
golang-github-cznic-fileutil (= 0.0~git20150708.0.1c9c88f-1),
golang-github-cznic-mathutil (= 0.0~git20150605.0.a804f0f-1),
golang-github-cznic-ql (= 1.0.2-1), golang-github-cznic-sortutil (=
0.0~git20150617.0.4c73428-1), golang-github-cznic-strutil (=
0.0~git20150430.0.1eb03e3-1), golang-github-cznic-zappy (=
0.0~git20160305.0.4f5e6ef-1), golang-github-dustin-go-humanize (=
0.0~git20151125.0.8929fe9-1), golang-github-google-btree (=
0.0~git20150413.0.cc6329d-1), golang-github-gorilla-mux (=
0.0~git20150814.0.f7b6aaa-1), golang-github-hashicorp-errwrap (=
0.0~git20141028.0.7554cd9-1), golang-github-pborman-uuid (=
0.0+git20150824.0.cccd189-1), golang-github-peterbourgon-diskv (=
2.0.0-1), golang-github-spf13-cobra (= 0.0~git20160117.0.8e91712-1),
golang-github-spf13-pflag (= 0.0~git20151218.0.7f60f83-2),
golang-go-semver (= 0.0~git20150304-1), golang-go.crypto (=
1:0.0~git20151201.0.7b85b09-2), golang-gocapability-dev (=
0.0~git20150506.1.66ef2aa-1), golang-golang-x-net-dev (=
1:0.0+git20160110.4fd4a9f-1), golang-google-grpc (=
0.0~git20151002.0.3e7b7e5-1), golang-goprotobuf (= 0.0~git20160330-1),
golang-speter-go-exp-math-dec-inf (= 0.0~git20140417.0.42ca6cd-2)

which looks at least plausible.

On 19 April 2016 at 10:28, Dmitry Smirnov  wrote:
> On Tuesday, 19 April 2016 10:19:56 AM AEST Michael Hudson-Doyle wrote:
>> Wow, I'm not sure that package gets much from using dh-golang at all?
>> But I think the problem is the " --builddirectory=_build" in the
>> default target, somehow that needs to get funnelled into the right
>> place. Will have a look.
>
> Thanks. We actually have many Golang packages with "--builddirectory=_build"
> so fixing that is very important.

Are there any other packages you think would be particularly good to
try to build?

Cheers,
mwh
From 5877dffe5bcb36a4afd724c31530d4f747f887d5 Mon Sep 17 00:00:00 2001
From: Michael Hudson-Doyle 
Date: Tue, 19 Apr 2016 11:59:51 +1200
Subject: [PATCH] More dh_golang fixes

---
 debian/changelog | 13 +
 script/dh_golang | 30 --
 2 files changed, 29 insertions(+), 14 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index a4b3689..0dcca6c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+dh-golang (1.16) UNRELEASED; urgency=medium
+
+  * Make dh_golang more robust:
+- Initialize the buildsystem more correctly, so --builddirectory=_build
+  works (Closes: 821350)
+- Exit with an error if any of the 'go list' or 'dpkg-search' commands
+  fail.
+- Quote the current working directory in the regexp used to filter out
+  files from the build directory.
+  * Also trim dh_golang's use statements. 
+
+ -- Michael Hudson-Doyle   Tue, 19 Apr 2016 11:42:26 +1200
+
 dh-golang (1.15) unstable; urgency=medium
 
   [ Michael Hudson-Doyle ]
diff --git a/script/dh_golang b/script/dh_golang
index 5e1e71d..b2c6d99 100755
--- a/script/dh_golang
+++ b/script/dh_golang
@@ -9,14 +9,7 @@ dh_golang - Generates Built-Using substvar
 use strict;
 use Cwd qw(realpath);
 use Debian::Debhelper::Dh_Lib; # not in core
-use Dpkg; # not in core
-use Dpkg::Control; # not in core
-use Dpkg::Control::Info; # not in core
-use Dpkg::Deps; # not in core
-use Dpkg::Gettext; # not in core
-use Scalar::Util qw(blessed); # in core since v5.7.3
-use List::Util qw(first); # in core since v5.7.3
-use Debian::Debhelper::Buildsystem::golang;
+use Debian::Debhelper::Dh_Buildsystems; # not in core
 
 =head1 SYNOPSIS
 
@@ -35,34 +28,43 @@ The best way to invoke B is by using B.
 
 =cut
 
-init();
-
 
 # Generate misc:Built-Using substvar.
 
 
-my $bs = Debian::Debhelper::Buildsystem::golang->new();
+buildsystems_init();
+my $bs = load_buildsystem("golang");
 
-$bs->_set_dh_gopkg();
 $bs->_set_gopath();
 
 my @targets = $bs->get_targets();
 
 my $godeps = `go list -f '{{ range .Deps }}{{.}} {{ end }}' @targets`;
+if ($? != 0) {
+die "go list of targets failed";
+}
 $godeps =~ s/\n/ /g;
 my @godirs = split /\n/, `go list -f '{{ .Dir }}' $godeps`;
+if ($? != 0) {
+die "go list of dependencies failed";
+}
 my $realgodirs;
-my $cwd = $bs->{cwd};
 for my $godir (@godirs) {
 my $realpath = realpath($godir);
 # @godirs will include the 

Bug#821748: mutt-patched: sidebar duplicate folders

[Matt Taggart]

Package: mutt-patched
Version: 1.5.23-3
Severity: minor

When using the sidebar and the following in .muttrc

===
set mbox_type=Maildir
set folder=~/Maildir/
set spoolfile = =INBOX
set postponed = =Drafts
set record= =Sent

set sidebar_visible="yes"
set sidebar_width=15
set sidebar_sort="yes"
mailboxes =INBOX =Spam =Drafts =Sent
===

the sidebar lists each folder twice, one with a message count and one
without. I cannot enter the ones without a message count, "is not a
mailbox".

If I do this instead
===
unmailboxes *
mailboxes =INBOX =Spam =Drafts =Sent
===

then it only lists with ones with message counts that work to enter. So
something is automatically adding them incorrectly and cleaning the list
first works around it.

-- 
Matt Taggart
tagg...@debian.org

Bug#741853: mutt-patched: sidebar_shortpath is not recognized in mutt 1.5.22-2

[Matt Taggart]

RE: 741853...

The provided examples/sidebar.muttrc still lists sidebar_shortpath and
sidebar_folderindent which no longer work. It needs to be updated for
the changes (I guess removing those and adding "sidebar_delim_chars"?)

Thanks,

-- 
Matt Taggart
tagg...@debian.org

Bug#702255: efitools: changing back from ITP to RFP

[Ben Hutchings]

On Wed, 23 Sep 2015 13:43:24 +0200 Pierre Chifflier  wrote:
> retitle 702255 ITP: efitools -- Tools to manipulate EFI secure boot keys and 
> signatures
> owner 702255 !
> block 702255 by 702254
> thanks
> 
> Hi,
> 
> I've finally managed to get some time to work again on this ITP.
> 
> I've uploaded the sbsigntool package to NEW (See #702254), which is
> required to build efitools. If/when sbsigntool is accepted, upload for
> efitools will follow.

Go on then!

Ben.
 
-- 
Ben Hutchings
Usenet is essentially a HUGE group of people passing notes in class.
  - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette'

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

Bug#821744: icedove: Missing scrollbars

[Tony Houghton]

Package: icedove
Version: 1:45.0~b4-2
Severity: normal

This experimental version appears to be using its own theme instead of
the system theme, and the scrollbars aren't being drawn properly. Only
the grey background appears; the draggable bar is invisible, but it
appears to behave as if it is present if I click and drag etc.

FWIW I'm using a Macbook Retina (hidpi display with Intel Iris
graphics).

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

Kernel: Linux 4.4.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)

Versions of packages icedove depends on:
ii  debianutils   4.7
ii  fontconfig2.11.0-6.4
ii  libasound21.1.0-1
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.22-6
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.8-1
ii  libdbus-glib-1-2  0.106-1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libffi6   3.2.1-4
ii  libfontconfig12.11.0-6.4
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:5.3.1-14
ii  libgdk-pixbuf2.0-02.32.3-2
ii  libglib2.0-0  2.48.0-1
ii  libgtk-3-03.20.3-1
ii  libhunspell-1.3-0 1.3.3-4
ii  libicu55  55.1-7
ii  libnspr4  2:4.12-2
ii  libnss3   2:3.23-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  libpixman-1-0 0.33.6-1
ii  libsqlite3-0  3.11.1-1
ii  libstartup-notification0  0.12-4
ii  libstdc++65.3.1-14
ii  libvpx3   1.5.0-2
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.9-2
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages icedove recommends:
ii  hunspell-en-gb [hunspell-dictionary]  1:5.1.2-1
ii  hunspell-en-us [hunspell-dictionary]  20070829-6
ii  iceowl-extension  1:45.0~b4-2

Versions of packages icedove suggests:
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.13.2+dfsg-5

-- no debconf information

Bug#821747: No longer works on the Hurd

[James Clarke]

Package: htop
Version: 2.0.1-1
Severity: important
Tags: patch upstream
User: debian-h...@lists.debian.org
Usertags: hurd
Forwarded: https://github.com/hishamhm/htop/pull/472

Hi,
Since version 2, htop does not have suport for the Hurd, as it uses the
"unsupported" backend. I have submitted a patch upstream, so please
backport it.

Regards,
James

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unreleased'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.6+git20160311-486-dbg/Hurd-0.7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages htop depends on:
ii  libc0.3   2.22-5
ii  libhwloc5 1.11.2-3
ii  libncursesw5  6.0+20160319-1
ii  libtinfo5 6.0+20160319-1

htop recommends no packages.

Versions of packages htop suggests:
pn  lsof
pn  strace  

-- no debconf information

Bug#821409: gtk+3.0: gtk3 apps seem to be graphically broken since the most recent updates

[Christoph Anton Mitterer]

On Mon, 2016-04-18 at 18:37 +0200, Christoph Anton Mitterer wrote:
> one more:
> In libreoffice, with libreoffice-gtk3 installed, the scrollbars are
> no
> longer visible either and some other drawing errors seem to be there,
> like no border around the text fields below the menu (e.g. the
> forumal
> field in Calc)... and other text fields, like the one for font face
> and
> size are all gray (while they should probably be white).

There was a rebuild of libreoffice and now things changed a bit...
The scrollbar, which was before completely grey (even the part that one
can move around) is now visible again.
When I move it (i.e. click hold and move) it gets blue and every place
where I move it over gets blue as well (i.e. there is no clearing).
When I release, then the movable part of the bar gets dark grey again,
but all other locations that were blue because of the above issue
remain so.

That doesn't happen in at least gedit, so maybe it's a libreoffice
specific bug?


Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#821746: dnsval: FTBFS on kFreeBSD: conflicting types for '__sym_ston' et al.

[Aaron M. Ucko]

Source: dnsval
Version: 2.0-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of dnsval on kFreeBSD have been failing:

  res_debug.c:481:1: error: conflicting types for '__sym_ston'
   sym_ston(const struct RES_SYM_TYPE *syms, const char *name, int *success)
   ^
  /usr/include/resolv.h:332:6: note: previous declaration of '__sym_ston' was 
here
   int  sym_ston (const struct res_sym *, const char *, int *) __THROW;
^
  res_debug.c:502:1: error: conflicting types for '__sym_ntos'
   sym_ntos(const struct RES_SYM_TYPE *syms, int number, int *success)
   ^
  /usr/include/resolv.h:333:14: note: previous declaration of '__sym_ntos' was 
here
   const char * sym_ntos (const struct res_sym *, int, int *) __THROW;
^
  res_debug.c:523:1: error: conflicting types for '__sym_ntop'
   sym_ntop(const struct RES_SYM_TYPE *syms, int number, int *success)
   ^
  /usr/include/resolv.h:334:14: note: previous declaration of '__sym_ntop' was 
here
   const char * sym_ntop (const struct res_sym *, int, int *) __THROW;
^

Could you please take a look?

Thanks!

Bug#821745: luksipc: FTBFS: static assertion failed: "sizeof(off_t) == 8"

[Aaron M. Ucko]

Source: luksipc
Version: 0.04-1
Severity: serious
Justification: fails to build from source

Builds of luksipc for 32-bit architectures such as i386 failed:

  gcc -Wall -Wextra -Wshadow -Wpointer-arith -Wcast-qual -Wstrict-prototypes 
-Wmissing-prototypes -std=c11 -O2 -D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=500 -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -c -o luksipc.o luksipc.c
  luksipc.c:50:31: error: static assertion failed: "sizeof(off_t) == 8"
   #define staticassert(cond)_Static_assert(cond, #cond)
 ^
  luksipc.c:53:1: note: in expansion of macro 'staticassert'
   staticassert(sizeof(off_t) == 8);
   ^
  luksipc.c: In function 'askUserConfirmation':
  luksipc.c:795:19: warning: format '%lu' expects argument of type 'long 
unsigned int', but argument 4 has type 'uint64_t {aka long long unsigned int}' 
[-Wformat=]
 fprintf(stderr, "%s: %lu MiB = %.1f GiB\n", parameters->rawDevice, 
devSize / 1024 / 1024, (double)(devSize / 1024 / 1024) / 1024);
 ^
  Makefile:31: recipe for target 'luksipc.o' failed

Ideally, luksipc would properly support such architectures (and not,
e.g., try to use format strings that don't match argument widths);
however, if that's not feasible, please set its Architecture field
accordingly.

Speaking of the Architecture field, whichever approach you take
towards 32-bit Linux, please exclude non-Linux architectures, which
obviously won't work at all.

Thanks!

Bug#821743: cyrus-admin: fails to upgrade from 'sid' - trying to overwrite /usr/sbin/cyrus

[Andreas Beckmann]

Package: cyrus-admin
Version: 2.5.7-0+exp4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package cyrus-admin.
  Preparing to unpack .../cyrus-admin_2.5.7-0+exp4_all.deb ...
  Unpacking cyrus-admin (2.5.7-0+exp4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cyrus-admin_2.5.7-0+exp4_all.deb (--unpack):
   trying to overwrite '/usr/sbin/cyrus', which is also in package cyrus-common 
2.4.18-5
  Errors were encountered while processing:
   /var/cache/apt/archives/cyrus-admin_2.5.7-0+exp4_all.deb


cheers,

Andreas


cyrus-common=2.4.18-5_cyrus-admin=2.5.7-0+exp4.log.gz
Description: application/gzip

Bug#821742: deprecated features in Quesion.pm and Config.pm

[Jaakov]

Package: debconf
Version: 1.5.56

Looks like updating perl broke debconf:

# aptitude purge libmpcdec6:amd64
Die folgenden Pakete werden ENTFERNT:
  libmpcdec6{p}
0 Pakete aktualisiert, 0 zusätzlich installiert, 1 werden entfernt und 0 
nicht aktualisiert.
0 B an Archiven müssen heruntergeladen werden. Nach dem Entpacken werden 
0 B zusätzlich belegt sein.

Möchten Sie fortsetzen? [Y/n/?] Y
Unescaped left brace in regex is deprecated, passed through in regex; 
marked by <-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at 
/usr/share/perl5/Debconf/Question.pm line 72.
Unescaped left brace in regex is deprecated, passed through in regex; 
marked by <-- HERE in m/\${ <-- HERE ([^}]+)}/ at 
/usr/share/perl5/Debconf/Config.pm line 30.
(Lese Datenbank ... 316017 Dateien und Verzeichnisse sind derzeit 
installiert.)

Entfernen von libmpcdec6:amd64 (2:0.1~r459-4.1) ...
Löschen der Konfigurationsdateien von libmpcdec6:amd64 (2:0.1~r459-4.1) ...
#

I' not sure whether it applies to debconf or to perl, so feel free to 
redirect the bug appropriately if wrong here.

Bug#819579: abi-monitor: Short description continues into long description

[Peter Spiess-Knafl]

Hi Josh!

Thank you detecting this. I tried to improve the package description
(changes are pushed to git).

The fix will be included with the next upload (containing more critical
changes).

Greetings
Peter

Bug#821741: linux-perf-4.6: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/perf-tip/tips.txt

[Andreas Beckmann]

Package: linux-perf-4.6
Version: 4.6~rc3-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package linux-perf-4.6.
  Preparing to unpack .../linux-perf-4.6_4.6~rc3-1~exp1_amd64.deb ...
  Unpacking linux-perf-4.6 (4.6~rc3-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-perf-4.6_4.6~rc3-1~exp1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/doc/perf-tip/tips.txt', which is also in 
package linux-perf-4.5 4.5.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-perf-4.6_4.6~rc3-1~exp1_amd64.deb


cheers,

Andreas


linux-perf-4.5=4.5.1-1_linux-perf-4.6=4.6~rc3-1~exp1.log.gz
Description: application/gzip

Bug#821738: cyrus-clients,cyrus-murder: error when trying to install together

[Andreas Beckmann]

Package: cyrus-clients,cyrus-murder
Version: 2.5.7-0+exp4
User: trei...@debian.org
Usertags: edos-file-overwrite

Architecture: amd64
Distribution: experimental

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package cyrus-murder.
  Preparing to unpack .../cyrus-murder_2.5.7-0+exp4_amd64.deb ...
  Unpacking cyrus-murder (2.5.7-0+exp4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cyrus-murder_2.5.7-0+exp4_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/cyrus-mupdatetest.1.gz', which is 
also in package cyrus-clients 2.5.7-0+exp4
  Processing triggers for libc-bin (2.22-6) ...
  Processing triggers for systemd (229-4) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/cyrus-murder_2.5.7-0+exp4_amd64.deb
 
This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/lib/cyrus/bin/mupdatetest
  usr/share/man/man1/cyrus-mupdatetest.1.gz

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


cyrus-clients=2.5.7-0+exp4_cyrus-murder=2.5.7-0+exp4.log.gz
Description: application/gzip

Bug#821736: prewikka: New prewikka version 1.2.6

[Thomas ANDREJAK]

Package: prewikka
Severity: normal

Dear Maintainer,

Since the end of 2015, there is a new version of Prewikka (and all Prelude 
modules) : 1.2.6
You can find the tarball here : 
https://www.prelude-siem.org/projects/prelude/files

Please, upgrade from 1.0.0 (2010) to 1.2.6 (2015)

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_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#821409: gtk+3.0: gtk3 apps seem to be graphically broken since the most recent updates

[Christoph Anton Mitterer]

Another thing which I've noticed (so far in evolution only):

When I open a context menu somewhere in it and then open it again (i.e.
several times right click), only the first one it appears next to the
mouse pointer... in all further cases it appears close to where it was
opened first time, but in varying locations,... even if the mouse
pointer is somewhere completely else.


Not sure if it's a GTK3 issue, but at least I didn't notice it before
in evolution.


Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#821740: debian build system overwrites CFLAGS/CPPFLAGS/LDFLAGS

[Matthias Klose]

Package: src:lz4
Version: 0.0~r131-2
Severity: important
Tags: sid stretch

The lz4 upstream system uses the CFLAGS/CPPFLAGS/LDFLAGS macros, which are 
overridden by the debian build system.  These really should accumulate.  E.g. 
upstream CFLAGS sets -std=c99, which is likely to break with GCC 6 having c11 as 
the default.

Bug#821400: firmware-brcm80211: brcmfmac_sdio wants brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied

[Ben Hutchings]

On Mon, 2016-04-18 at 14:57 -0400, Daniel Kahn Gillmor wrote:
> Version: 20160110-1
> 
> Thanks for the quick response, Ben.
> 
> On Mon 2016-04-18 09:49:27 -0400, Ben Hutchings wrote:
> > 
> > > 
> > > It looks to me like the brcmfmac_sdio kernel module is expecting this
> > > .txt file is supposed to be shipped alongside the .bin, but it isn't
> > > present.
> > That's board-specific configuration, not really firmware.  I don't know
> > where you're supposed to get it from.
> hm, https://wiki.debian.org/InstallingDebianOn/Asus/X205TA#WiFi
> suggests:
> 
>    cp /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 
> /lib/firmware/brcm/brcmfmac43340-sdio.txt
> 
> and indeed, after doing that, and then removing and re-loading the
> kernel module with:
> 
>  modprobe -v -r brcmfmac
>  modprobe -v brcmfmac
> 
> then the device is found correctly.

Ah, I dimly remembered that this information could be stashed in the
system firmware somewhere.  It seems like the driver ought to look
there first if EFI support is enabled (there is an in-kernel API for
reading EFI variables).  That will have to be developed upstream
though.

Ben.

-- 
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.

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

Bug#821739: mrtg 'can not determine ifNumber'

[Richard Kettlewell]

Package: mrtg
Version: 2.17.4-2+b1

mrtg has started consistently producing the following error for one of
my interfaces:

2016-04-18 23:30:02: WARNING: Can not determine ifNumber for
public@sfere:
ref: 'Descr'key: 'tun0'

This looks very similar to #122273.

$ snmpwalk -v 1 -c public localhost 1.3.6.1.2.1.2
/usr/share/mibs/netsnmp/UCD-SNMP-MIB: No such file or directory
/usr/share/mibs/netsnmp/LM-SENSORS-MIB: No such file or directory
SNMPv2-SMI::mib-2.2.1.0 = INTEGER: 11
SNMPv2-SMI::mib-2.2.2.1.1.1 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.1.2 = INTEGER: 2
SNMPv2-SMI::mib-2.2.2.1.1.3 = INTEGER: 3
SNMPv2-SMI::mib-2.2.2.1.1.4 = INTEGER: 4
SNMPv2-SMI::mib-2.2.2.1.1.5 = INTEGER: 5
SNMPv2-SMI::mib-2.2.2.1.1.6 = INTEGER: 6
SNMPv2-SMI::mib-2.2.2.1.1.7 = INTEGER: 7
SNMPv2-SMI::mib-2.2.2.1.1.8 = INTEGER: 8
SNMPv2-SMI::mib-2.2.2.1.1.9 = INTEGER: 9
SNMPv2-SMI::mib-2.2.2.1.1.10 = INTEGER: 10
SNMPv2-SMI::mib-2.2.2.1.1.11 = INTEGER: 11
SNMPv2-SMI::mib-2.2.2.1.2.1 = STRING: "lo"
SNMPv2-SMI::mib-2.2.2.1.2.2 = STRING: "Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
SNMPv2-SMI::mib-2.2.2.1.2.3 = STRING: "Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
SNMPv2-SMI::mib-2.2.2.1.2.4 = STRING: "Realtek Semiconductor Co., Ltd.
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter"
SNMPv2-SMI::mib-2.2.2.1.2.5 = STRING: "Realtek Semiconductor Co., Ltd.
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter"
SNMPv2-SMI::mib-2.2.2.1.2.6 = STRING: "Realtek Semiconductor Co., Ltd.
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter"
SNMPv2-SMI::mib-2.2.2.1.2.7 = STRING: "Realtek Semiconductor Co., Ltd.
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter"
SNMPv2-SMI::mib-2.2.2.1.2.8 = STRING: "br0"
SNMPv2-SMI::mib-2.2.2.1.2.9 = STRING: "sit0"
SNMPv2-SMI::mib-2.2.2.1.2.10 = STRING: "6in4"
SNMPv2-SMI::mib-2.2.2.1.2.11 = STRING: "tun0"
SNMPv2-SMI::mib-2.2.2.1.3.1 = INTEGER: 24
SNMPv2-SMI::mib-2.2.2.1.3.2 = INTEGER: 6
SNMPv2-SMI::mib-2.2.2.1.3.3 = INTEGER: 6
SNMPv2-SMI::mib-2.2.2.1.3.4 = INTEGER: 6
SNMPv2-SMI::mib-2.2.2.1.3.5 = INTEGER: 6
SNMPv2-SMI::mib-2.2.2.1.3.6 = INTEGER: 6
SNMPv2-SMI::mib-2.2.2.1.3.7 = INTEGER: 6
SNMPv2-SMI::mib-2.2.2.1.3.8 = INTEGER: 6
SNMPv2-SMI::mib-2.2.2.1.3.9 = INTEGER: 131
SNMPv2-SMI::mib-2.2.2.1.3.10 = INTEGER: 131
SNMPv2-SMI::mib-2.2.2.1.3.11 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.4.1 = INTEGER: 65536
SNMPv2-SMI::mib-2.2.2.1.4.2 = INTEGER: 1500
SNMPv2-SMI::mib-2.2.2.1.4.3 = INTEGER: 1500
SNMPv2-SMI::mib-2.2.2.1.4.4 = INTEGER: 1500
SNMPv2-SMI::mib-2.2.2.1.4.5 = INTEGER: 1500
SNMPv2-SMI::mib-2.2.2.1.4.6 = INTEGER: 1500
SNMPv2-SMI::mib-2.2.2.1.4.7 = INTEGER: 1500
SNMPv2-SMI::mib-2.2.2.1.4.8 = INTEGER: 1500
SNMPv2-SMI::mib-2.2.2.1.4.9 = INTEGER: 1480
SNMPv2-SMI::mib-2.2.2.1.4.10 = INTEGER: 1280
SNMPv2-SMI::mib-2.2.2.1.4.11 = INTEGER: 1400
SNMPv2-SMI::mib-2.2.2.1.5.1 = Gauge32: 1000
SNMPv2-SMI::mib-2.2.2.1.5.2 = Gauge32: 10
SNMPv2-SMI::mib-2.2.2.1.5.3 = Gauge32: 10
SNMPv2-SMI::mib-2.2.2.1.5.4 = Gauge32: 1
SNMPv2-SMI::mib-2.2.2.1.5.5 = Gauge32: 1000
SNMPv2-SMI::mib-2.2.2.1.5.6 = Gauge32: 1
SNMPv2-SMI::mib-2.2.2.1.5.7 = Gauge32: 1
SNMPv2-SMI::mib-2.2.2.1.5.8 = Gauge32: 0
SNMPv2-SMI::mib-2.2.2.1.5.9 = Gauge32: 0
SNMPv2-SMI::mib-2.2.2.1.5.10 = Gauge32: 0
SNMPv2-SMI::mib-2.2.2.1.5.11 = Gauge32: 0
SNMPv2-SMI::mib-2.2.2.1.6.1 = ""
SNMPv2-SMI::mib-2.2.2.1.6.2 = Hex-STRING: 00 04 A7 05 AC 0B
SNMPv2-SMI::mib-2.2.2.1.6.3 = Hex-STRING: 00 04 A7 05 AC 0C
SNMPv2-SMI::mib-2.2.2.1.6.4 = Hex-STRING: 00 04 A7 08 AF B0
SNMPv2-SMI::mib-2.2.2.1.6.5 = Hex-STRING: 00 04 A7 08 AF AF
SNMPv2-SMI::mib-2.2.2.1.6.6 = Hex-STRING: 00 04 A7 08 AF AE
SNMPv2-SMI::mib-2.2.2.1.6.7 = Hex-STRING: 00 04 A7 08 AF AD
SNMPv2-SMI::mib-2.2.2.1.6.8 = Hex-STRING: 00 04 A7 05 AC 0B
SNMPv2-SMI::mib-2.2.2.1.6.9 = ""
SNMPv2-SMI::mib-2.2.2.1.6.10 = ""
SNMPv2-SMI::mib-2.2.2.1.6.11 = ""
SNMPv2-SMI::mib-2.2.2.1.7.1 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.7.2 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.7.3 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.7.4 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.7.5 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.7.6 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.7.7 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.7.8 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.7.9 = INTEGER: 2
SNMPv2-SMI::mib-2.2.2.1.7.10 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.7.11 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.8.1 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.8.2 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.8.3 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.8.4 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.8.5 = INTEGER: 2
SNMPv2-SMI::mib-2.2.2.1.8.6 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.8.7 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.8.8 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.8.9 = INTEGER: 2
SNMPv2-SMI::mib-2.2.2.1.8.10 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.8.11 = INTEGER: 1
SNMPv2-SMI::mib-2.2.2.1.9.1 = Timeticks: (0) 0:00:00.00
SNMPv2-SMI::mib-2.2.2.1.9.2 = Timeticks: (0) 0:00:00.00
SNMPv2-SMI::mib-2.2.2.1.9.3 = Timeticks: (0) 0:00:00.00

Bug#821737: roundcube-plugins-extra: wrong directory name for thunderbird_labels plugin

[Arnaud Duplessier]

Package: roundcube-plugins-extra
Version: 1.1.3-20151025
Severity: normal

Dear Maintainer,

When I tried to use the thunderbird_labels plugin it doesn't work out of
the box.

In /usr/share/doc/roundcube-plugins-extra/thunderbird-labels.README We
can read :
- add 'thunderbird_labels' to $rcmail_config['plugins'] in main.inc.php

But the plugin is in thunderbird-labels directory in /var/lib/roundcube/plugins.
It should be thunderbird_labels with "_" not "-"


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

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

Versions of packages roundcube-plugins-extra depends on:
ii  libjs-jquery-mousewheel  11-1
ii  roundcube-core   1.1.4+dfsg.1-3

roundcube-plugins-extra recommends no packages.

Versions of packages roundcube-plugins-extra suggests:
ii  fail2ban  0.9.3-1

-- no debconf information

Bug#734669: avahi: Add DEB_BUILD_PROFILES stage1 support for bootstraping

[John Paul Adrian Glaubitz]

Hi Wookey, hi Daniel!

Both these patches look very promising and I'm all for applying them,
I'm currently in the situation on powerpcspe.

However, it seems that debian/control still needs to be amended with
the necessary  statements if I'm not mistaken. At least I had
to add that to build avahi on powerpcspe.

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#803104: yelp: FTBFS: Segmentation fault

[Michael Biebl]

Control: severity -1 important
Control: yelp: FTBFS:  Segmentation fault in gtk-doc if no $DISPLAY

I've disabled the gtk-doc generation during build and we use the
pre-generated files shipped by upstream for now.
I'll keep this bug open as I want to switch on --enable-gtk-doc at some
point when the webkit2 issue has been fixed.

Downgrading the severity though, as the package now builds successfully
everywhere.

Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#819395: RFS: stormlib-listfiles/2015-04-20-1 [ITP]

[Gianfranco Costamagna]

Still a copyright issue

W missing-license-paragraph-in-dep5-copyright
public-domain (paragraph at line 17)


G.


Il Lunedì 18 Aprile 2016 21:33, Pali Rohár  ha scritto:
On Monday 18 April 2016 19:09:49 Gianfranco Costamagna wrote:

> Hi
> 
> >> 0.0.0~20150420
> >
> >Ok, I change it to that string.
> 
> as said by Jakub, 0~20150420 is already fine

I did not get any email from Jakub.

Anyway, now I updated stormlib-listfiles package on mentors.debian.net.

-- 
Pali Rohár
pali.ro...@gmail.com

Bug#821350: dh-golang: generates rubbish in Built-Using; errors on invocation

[Dmitry Smirnov]

On Tuesday, 19 April 2016 10:19:56 AM AEST Michael Hudson-Doyle wrote:
> Wow, I'm not sure that package gets much from using dh-golang at all?
> But I think the problem is the " --builddirectory=_build" in the
> default target, somehow that needs to get funnelled into the right
> place. Will have a look.

Thanks. We actually have many Golang packages with "--builddirectory=_build"
so fixing that is very important.

-- 
All the best,
 Dmitry Smirnov.

---

It has become almost a cliché to remark that nobody boasts of ignorance
of literature, but it is socially acceptable to boast ignorance of
science.
-- Richard Dawkins


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

Bug#821272: rkt: Can't run docker images

[Dmitry Smirnov]

On Sunday, 17 April 2016 10:12:01 AM AEST Nicolas LE CAM wrote:
> Version: 1.3.0+dfsg-1

Nicolas, please try rkt-1.4.0.

Did you find anything relevant in upstream bug tracker?

The following bug is not your case, right?

   https://github.com/coreos/rkt/issues/2392

Did you try converting image using "docker2aci"?

Thanks.

-- 
All the best,
 Dmitry Smirnov.

---

The surest way to corrupt a youth is to instruct him to hold in higher
esteem those who think alike than those who think differently.
-- Friedrich Nietzsche


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

Bug#819921: basket: please make the build reproducible (timestamps)

[Luigi Toscano]

Control: forwarded -1 https://github.com/basket-notepads/basket/pull/25

Alexis Bienvenüe ha scritto:
> While working on the “reproducible builds” effort [1], we have noticed
> that 'basket' could not be built reproducibly.
> 
> The attached patch removes build date from debug info. Once applied,
> basket can be built reproducibly in our current experimental framework.

Hi, thanks for the patch, I submitted it upstream for inclusion (patches are
going in).

-- 
Luigi

Bug#821350: dh-golang: generates rubbish in Built-Using; errors on invocation

[Michael Hudson-Doyle]

Wow, I'm not sure that package gets much from using dh-golang at all?
But I think the problem is the " --builddirectory=_build" in the
default target, somehow that needs to get funnelled into the right
place. Will have a look.

On 19 April 2016 at 09:05, Michael Stapelberg  wrote:
> Michael, can you take a look at this issue please?
>
> On Mon, Apr 18, 2016 at 12:45 AM, Dmitry Smirnov  wrote:
>>
>> Package: dh-golang
>> Version: 1.15
>> Severity: serious
>>
>> Recent upload of "rkt" was rejected
>>
>> rkt_1.4.0+dfsg-1_amd64.deb: Built-Using refers to non-existing source
>> package apt (= 1.0.9.10)
>>
>> due to rubbish in Built-Using field:
>>
>> apt (= 1.0.9.10), apt (= 1.0.10.2), apt (= 1.2.10)
>>
>> Also invocation of dh-golang logged the following:
>>
>> 
>>dh_golang -O--buildsystem=golang -O--builddirectory=_build
>> can't load package: package github.com/coreos/rkt/api/v1alpha: cannot find
>> package "github.com/coreos/rkt/api/v1alpha" in any of:
>> /usr/lib/go/src/github.com/coreos/rkt/api/v1alpha (from $GOROOT)
>>
>> /build/rkt-1.4.0+dfsg/obj-x86_64-linux-gnu/src/github.com/coreos/rkt/api/v1alpha
>> (from $GOPATH)
>> can't load package: package github.com/coreos/rkt/rkt: cannot find package
>> "github.com/coreos/rkt/rkt" in any of:
>> /usr/lib/go/src/github.com/coreos/rkt/rkt (from $GOROOT)
>>
>> /build/rkt-1.4.0+dfsg/obj-x86_64-linux-gnu/src/github.com/coreos/rkt/rkt
>> (from $GOPATH)
>> can't load package: package .: no buildable Go source files in
>> /build/rkt-1.4.0+dfsg
>> can't load package: package .: no buildable Go source files in
>> /build/rkt-1.4.0+dfsg
>> dpkg-query: error: --search needs at least one file name pattern argument
>>
>> Use --help for help about querying packages.
>> 
>>
>> This is regression from "dh-golang" v1.12.
>>
>> Please investigate.
>>
>> --
>> All the best,
>>  Dmitry Smirnov
>>  GPG key : 4096R/53968D1B
>>
>> ---
>>
>> Truth never damages a cause that is just.
>> -- Mahatma Gandhi
>
>
>
>
> --
> Best regards,
> Michael

Bug#821734: libvotca-csg3: fails to upgrade from 'jessie' - trying to overwrite /usr/share/man/man7/votca-csg.7.gz

[Andreas Beckmann]

Package: libvotca-csg3
Version: 1.3.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libvotca-csg3.
  Preparing to unpack .../libvotca-csg3_1.3.0-1_amd64.deb ...
  Unpacking libvotca-csg3 (1.3.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvotca-csg3_1.3.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man7/votca-csg.7.gz', which is also in 
package libvotca-csg2 1.2.4-2.1+b1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Processing triggers for libc-bin (2.22-6) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libvotca-csg3_1.3.0-1_amd64.deb


cheers,

Andreas


libvotca-csg2=1.2.4-2.1+b1_libvotca-csg3=1.3.0-1.log.gz
Description: application/gzip

Bug#821726: mandelbulber2: please build-depend on libpng-dev (=> libpng16 instead of libpng12)

[Giovanni Mascellani]

Hi.

Il 18/04/2016 23:16, Mattia Rizzolo ha scritto:
> looks like you missed the libpng16 transition :)

I definitely did. I'm uploading a new version in a few minutes.

Thanks, Giovanni.
-- 
Giovanni Mascellani 
PhD Student - Scuola Normale Superiore, Pisa, Italy

http://poisson.phc.unipi.it/~mascellani



signature.asc
Description: OpenPGP digital signature

Bug#821431: apt-listbugs gets confused in non-C-locales and break install or upgrade completely

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Francesco,

Am Mo den 18. Apr 2016 um 22:39 schrieb Francesco Poli:
> > > P.S.: I am closing your bug report, since the issue is in other
> > > packages and it has already been fixed (even though not in jessie).
> > 
> > Well, I posted that bug to stable release and it is not fixed in stable
> > release.
> > 
> > What is the stable release for if there are bugs that keeps apt from
> > updating the system (or only update it with some workarounds)?
> > 
> > I please you to also fix that bug in stable.
> 
> I don't think that the severity of this bug is high enough to justify
> an update in a stable point release, but anyway, even assuming it is,
> the issue is *not* in apt-listbugs.
> I am *not* the one who needs to be convinced.
> The bug [1] is in package ruby-gettext: if you feel like it, please try
> and persuade ruby-gettext Debian package maintainers to prepare an
> updated package for jessie with this bug fixed...

Ok, I reassigned that bug to ruby-gettext.

Even though, that I think the severity is much higher than "normal" (it
affects the whole system and even somehow security), I will not touch it
currently. I hope the maintainer of ruby-gettext will do so.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Charset: ISO-8859-1

iQGcBAEBCgAGBQJXFVciAAoJEKZ8CrGAGfasAF0L/jCzbRo47LIsOEOL1x1/gk5g
3WmWR0xnFvP/h5p+PGqqbKe5nGCC4K29hSwxNlBgLxI9rzMIhmcFezHtmqyKFbtm
/rCRTngKnHZVJzlcf/mN6wdti66c9FRRq26b7L6hbSm6I6Vi+8IZWyc8B/sbv13z
zoCasuyavXwAWb7iabYxlfRXoeyRT/urYXVbwgRmVBZ1J7mRoD8O4e1MS8mHud3D
gE1Mrhsb+X08gWlP5QHaSWy6IBn9VFfq1taQj8VJpjtxvGxAWpilx+JsgI5Ge3Ps
8aTsPNojt0aqskfGDl5gk20n9Ken/xPGRRr5bOiCFAQl12oZsCHrfvScgXhkRzmr
Z6QQyPu4yJdahyxJPHnWygg3bAfFUwN5NdNnJPLjM+Y/I/9jtkXy85FvChjxq1v7
8Muv3HgKE3ei1v2IxX/Lqebp4+gf0B/YOgk/Azf1veQtx6DeNSQKPtcEEPPeezXl
8VFBZsB6wLNcCI+4wb+cXI7UcMhjW/uux8alF1LtHA==
=9ZkG
-END PGP SIGNATURE-

Bug#525314:

[SamuelOPH]

Hi Axel,

It looks like efte is already packaged[1].

​I'm assuming that I should follow the procedure explained here[2] in order
to substitute fte with efte, am I right?

[1]https://tracker.debian.org/pkg/efte
[2]https://wiki.debian.org/Renaming_a_Package

Thanks

Samuel Henrique O. P. [samueloph]

Bug#821733: nmu: imagemagick_8:6.9.2.10+dfsg-2

[Andreas Beckmann]

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

nmu imagemagick_8:6.9.2.10+dfsg-2 . ANY . experimental . -m "Rebuild against 
libopenexr22"

openexr had a transition recently.


Andreas

Bug#821732: CVE-2016-4024: integer overflow resulting in insufficient heap allocation

[Matthias Geerdsen]

Source: imlib2
Severity: normal
Tags: security upstream

Hi,

the following vulnerability was published for imlib2.

CVE-2016-4024[0,1]:
integer overflow resulting in insufficient heap allocation

The upstream fix can be found at [2]

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-4024
[1] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4024
[2] 
https://git.enlightenment.org/legacy/imlib2.git/commit/?id=7eba2e4c8ac0e20838947f10f29d0efe1add8227

Please adjust the affected versions in the BTS as needed.

Bug#821731: ctk: FTBFS: ctkDICOMUtil.cpp:33:3: error: 'log4cplus' has not been declared

[Andreas Beckmann]

Package: ctk
Version: 0.1.0+git20131105~b8307961b6-2
Severity: serious
Justification: fails to build from source

I just tried to rebuild ctk against the new libdcmtk-dev, but it failed with

/build/ctk-0.1.0+git20131105~b8307961b6/Libs/DICOM/Core/ctkDICOMUtil.cpp: In 
function 'void ctk::setDICOMLogLevel(ctkErrorLogLevel::LogLevel)':
/build/ctk-0.1.0+git20131105~b8307961b6/Libs/DICOM/Core/ctkDICOMUtil.cpp:33:3: 
error: 'log4cplus' has not been declared
   log4cplus::Logger log = log4cplus::Logger::getRoot();
   ^
[ 33%] Building CXX object 
Libs/DICOM/Core/CMakeFiles/CTKDICOMCore.dir/moc_ctkDICOMIndexer.cxx.o
/build/ctk-0.1.0+git20131105~b8307961b6/Libs/DICOM/Core/ctkDICOMUtil.cpp:36:35: 
error: 'log' was not declared in this scope
 case ctkErrorLogLevel::Trace: log.setLogLevel(OFLogger::TRACE_LOG_LEVEL); 
break;
   ^
/build/ctk-0.1.0+git20131105~b8307961b6/Libs/DICOM/Core/ctkDICOMUtil.cpp: In 
function 'ctkErrorLogLevel::LogLevel ctk::dicomLogLevel()':
/build/ctk-0.1.0+git20131105~b8307961b6/Libs/DICOM/Core/ctkDICOMUtil.cpp:52:3: 
error: 'log4cplus' has not been declared
   log4cplus::Logger log = log4cplus::Logger::getRoot();
   ^
/build/ctk-0.1.0+git20131105~b8307961b6/Libs/DICOM/Core/ctkDICOMUtil.cpp:53:11: 
error: 'log' was not declared in this scope
   switch (log.getLogLevel())
   ^
/build/ctk-0.1.0+git20131105~b8307961b6/Libs/DICOM/Core/ctkDICOMUtil.cpp:63:1: 
warning: control reaches end of non-void function [-Wreturn-type]
 }
 ^


Andreas

Bug#821730: samba: Cannot connect to Samba 4.2 server from OS X 10.11

[Tim Rogers]

Package: samba
Version: 2:4.2.10+dfsg-0+deb8u2
Severity: important

Dear Maintainer,

After upgrading from Samba 4.1 to Samba 4.2, I can no longer connect to
shares from OS X 10.11. Linux boxes (upgraded to Samba 4.2) connect fine,
as does Windows 10.

Samba logs show the following error for each connection attempt:

[2016/04/15 12:40:07.087650,  1]
../auth/ntlmssp/ntlmssp_server.c:908(ntlmssp_server_postauth)
  ntlmssp_server_postauth: invalid NTLMSSP_MIC for user=[GUEST] domain=[]
workstation=[ROGERS]
[2016/04/15 12:40:07.087709,  1] ../lib/util/util.c:559(dump_data)
  [] 67 7E 0E CB CE 77 2E 62   05 00 BD F6 E3 84 FB 27   g~...w.b
...'
[2016/04/15 12:40:07.087747,  1] ../lib/util/util.c:559(dump_data)
  [] 43 AD 8C C7 E8 F7 0A 1C   06 A8 03 CB FC C8 17 38   C...
...8

I assume that there are configuration options for smb.conf which will
resolve this - but I can't find them. I can't find any clear instructions
in the
documentation, although it seems to suggest that such issues are likely
with this upgrade.

Thank you.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_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 samba depends on:
ii  adduser  3.113+nmu3
ii  dpkg 1.17.26
ii  libbsd0  0.7.0-2
ii  libc62.19-18+deb8u4
ii  libhdb9-heimdal [heimdal-hdb-api-8]  1.6~rc2+dfsg-9
ii  libldb1  2:1.1.20-0+deb8u1
ii  libpam-modules   1.1.8-3.1+deb8u1+b1
ii  libpam-runtime   1.1.8-3.1+deb8u1
ii  libpopt0 1.16-10
ii  libpython2.7 2.7.9-2
ii  libtalloc2   2.1.2-0+deb8u1
ii  libtdb1  1.3.6-0+deb8u1
ii  libtevent0   0.9.25-0+deb8u1
ii  lsb-base 4.1+Debian13+nmu1
ii  multiarch-support2.19-18+deb8u4
ii  procps   2:3.3.9-9
ii  python   2.7.9-1
ii  python-dnspython 1.12.0-1
ii  python-ntdb  1.0-5
ii  python-samba 2:4.2.10+dfsg-0+deb8u2
pn  python2.7:any
ii  samba-common 2:4.2.10+dfsg-0+deb8u2
ii  samba-common-bin 2:4.2.10+dfsg-0+deb8u2
ii  samba-dsdb-modules   2:4.2.10+dfsg-0+deb8u2
ii  samba-libs   2:4.2.10+dfsg-0+deb8u2
ii  tdb-tools1.3.6-0+deb8u1
ii  update-inetd 4.43

Versions of packages samba recommends:
ii  attr   1:2.4.47-2
ii  logrotate  3.8.7-1+b1
ii  samba-vfs-modules  2:4.2.10+dfsg-0+deb8u2

Versions of packages samba suggests:
pn  bind9  
pn  bind9utils 
pn  ctdb   
pn  ldb-tools  
pn  ntp
pn  smbldap-tools  
ii  winbind2:4.2.10+dfsg-0+deb8u2

-- no debconf information

Bug#798396: Still present in 2.1.0-2

[Thomas Klute]

Control: found -1 2.1.0-2

This bug is still present in 2.1.0-2 according to the logs from buildd
(https://buildd.debian.org/status/fetch.php?pkg=softhsm2=arm64=2.1.0-2=1459985395):

> configure:4560: checking if we can compile in 64-bit mode
> configure:4583: gcc -o conftest -m64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE 
> -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed conftest.c  >&5
> gcc: error: unrecognized command line option '-m64'

SoftHSM v1 is getting removed (see #820235), so having softhsm2
available is important (e.g. see #820248).

Bug#821431: apt-listbugs gets confused in non-C-locales and break install or upgrade completely

[Francesco Poli]

On Mon, 18 Apr 2016 22:14:56 +0100 Klaus Ethgen wrote:

[...]
> Am Mo den 18. Apr 2016 um 21:57 schrieb Francesco Poli:
[...]
> > Or to plain
> > run-time errors, with buggy ruby-gettext or ruby-locale packages, as
> > you already know!
> 
> Well, then it is a bug and needs to get fixed.

As I said, this bug [1] has indeed been fixed in package ruby-gettext,
after the release of jessie.

[1] https://bugs.debian.org/799194

> 
> > P.S.: I am closing your bug report, since the issue is in other
> > packages and it has already been fixed (even though not in jessie).
> 
> Well, I posted that bug to stable release and it is not fixed in stable
> release.
> 
> What is the stable release for if there are bugs that keeps apt from
> updating the system (or only update it with some workarounds)?
> 
> I please you to also fix that bug in stable.

I don't think that the severity of this bug is high enough to justify
an update in a stable point release, but anyway, even assuming it is,
the issue is *not* in apt-listbugs.
I am *not* the one who needs to be convinced.
The bug [1] is in package ruby-gettext: if you feel like it, please try
and persuade ruby-gettext Debian package maintainers to prepare an
updated package for jessie with this bug fixed...

Bye.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpwnR_gewa0T.pgp
Description: PGP signature

Bug#820309: webkit2gtk: rebuild needed

[Emilio Pozuelo Monfort]

On 18/04/16 23:25, Alberto Garcia wrote:
> On Mon, Apr 18, 2016 at 09:50:14PM +0200, Jiri Horner wrote:
> 
>> gtk 3.20 finally made it to sid. Exactly as described above, webkit
>> have issues, when built on gtk <3.20 but running on 3.20. Scrollbars
>> are not rendering for me at all under gtk 3.20 with default Adwaita.
>>
>> Could you force a rebuild of this package?
> 
> I'm mostly offline these days.
> 
> Emilio, Gustavo, could you take care of this?

We can handle this through a binNMU. I'll see what's the plan for the rest of
the broken packages and act accordingly.

Cheers,
Emilio

Bug#821729: O: polygraph -- performance testing tool for caching proxies and more

[Sebastian Andrzej Siewior]

Package: wnpp
Severity: normal

I hereby orphan the package. The package was maintained by an upstream
developer of Measurement Factory which passed away. Upstream is willing
to help with bug fixing of their code but don't have Debian expertise
for packaging [0].

[0] http://lists.web-polygraph.org/pipermail/users/2016-March/000313.html

Sebastian

Bug#820309: webkit2gtk: rebuild needed

[Alberto Garcia]

On Mon, Apr 18, 2016 at 09:50:14PM +0200, Jiri Horner wrote:

> gtk 3.20 finally made it to sid. Exactly as described above, webkit
> have issues, when built on gtk <3.20 but running on 3.20. Scrollbars
> are not rendering for me at all under gtk 3.20 with default Adwaita.
> 
> Could you force a rebuild of this package?

I'm mostly offline these days.

Emilio, Gustavo, could you take care of this?

Berto

Bug#821727: poker-engine: FTBFS: unknown test /bin/bash

[Chris Lamb]

Source: poker-engine
Version: 1.3.6-1.2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

poker-engine fails to build from source in unstable/amd64:

  [..]

  config.status: creating tests/history.py
  config.status: creating tests/muck.py
  config.status: creating tests/positions.py
  config.status: creating tests/sit.py
  config.status: creating tests/tournament.py
  config.status: creating tests/upgrades.py
  config.status: creating tests/libxml2leak.py
  config.status: creating tests/test-gamehistory.py
  config.status: creating tests/test-pokercards.py
  config.status: creating tests/test-pokerengineconfig.py
  config.status: creating tests/test-pokertournament.py
  config.status: creating tests/test-pokerprizes.py
  config.status: creating tests/test-game.py
  config.status: creating tests/test-pokerchips.py
  config.status: creating tests/test-pokerrake.py
  config.status: creating tests/test-pokerplayer.py
  config.status: creating tests/test-version.py
  config.status: creating tests/test-i18n.py
  config.status: creating tests/Makefile
  config.status: executing po-directories commands
  configure: WARNING: unrecognized options: --disable-dependency-tracking
  rm -f ./*cdbs-*
  rm -f debian/stamp-autotools-files
   debian/rules build
  test -x debian/rules
  mkdir -p "."
  touch debian/stamp-autotools-files
  chmod a+x 
/home/lamby/temp/cdt.20160418221818.cJgaLUO0pw.poker-engine/poker-engine-1.3.6/./configure
  mkdir -p .
  cd . &&   CFLAGS="-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall" CXXFLAGS="-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall" CPPFLAGS="-Wdate-time 
-D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" 
/home/lamby/temp/cdt.20160418221818.cJgaLUO0pw.poker-engine/poker-engine-1.3.6/./configure
 --build=x86_64-linux-gnu  --prefix=/usr --includedir="\${prefix}/include" 
--mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" 
--sysconfdir=/etc --localstatedir=/var 
--libexecdir="\${prefix}/lib/poker-engine" --srcdir=. --disable-maintainer-mode 
--disable-dependency-tracking --disable-silent-rules   --enable-maintainer-mode 
  configure: WARNING: unrecognized options: --disable-dependency-tracking
  checking for a BSD-compatible install... /usr/bin/install -c
  checking whether build environment is sane... yes
  checking for a thread-safe mkdir -p... /bin/mkdir -p
  checking for gawk... no
  checking for mawk... mawk
  checking whether make sets $(MAKE)... yes
  checking whether make supports nested variables... yes
  checking whether make sets $(MAKE)... (cached) yes
  checking for rsync... /usr/bin/rsync
  checking whether to enable maintainer-specific portions of Makefiles... yes
  checking for a Python interpreter with version >= 2.3... python
  checking for python... /usr/bin/python
  checking for python version... 2.7
  checking for python platform... linux2
  checking for python script directory... ${prefix}/lib/python2.7/dist-packages
  checking for python extension module directory... 
${exec_prefix}/lib/python2.7/dist-packages
  checking for pkg-config... /usr/bin/pkg-config
  checking pkg-config is at least version 0.9.0... yes
  checking for PYPOKER_EVAL... yes
  checking wether python module libxml2 is available... 
/usr/lib/python2.7/dist-packages/libxml2.py ... yes
  checking wether python module libxslt is available... 
/usr/lib/python2.7/dist-packages/libxslt.py ... yes
  checking wether python module pokereval is available... 
/usr/lib/python2.7/dist-packages/pokereval.py ... yes
  checking for a sed that does not truncate output... /bin/sed
  checking whether NLS is requested... yes
  checking for msgfmt... /usr/bin/msgfmt
  checking for gmsgfmt... /usr/bin/msgfmt
  checking for xgettext... /usr/bin/xgettext
  checking for msgmerge... /usr/bin/msgmerge
  checking that generated files are newer than configure... done
  configure: creating ./config.status
  config.status: creating tests/run
  config.status: creating pokerconfigupgrade
  config.status: creating po/Makefile
  config.status: creating Makefile
  config.status: creating poker-engine.pc
  config.status: creating pokerconfigupgrade.8
  config.status: creating pokerengine/Makefile
  config.status: creating tests/allin.py
  config.status: creating tests/blinds.py
  config.status: creating tests/buyin.py
  config.status: creating tests/bugs.py
  config.status: creating tests/chips.py
  config.status: creating tests/deal.py
  config.status: creating tests/eval.py
  config.status: creating tests/history.py
  config.status: creating tests/muck.py
  config.status: creating tests/positions.py
  config.status: creating tests/sit.py
  config.status: creating tests/tournament.py
  config.status: creating tests/upgrades.py
  config.status: creating tests/libxml2leak.py
  config.status: creating 

Bug#821728: git-buildpackage: gbp buildpackage does not seem to read debian/gbp.conf before checking the branch name

[Tim Dengel]

Package: git-buildpackage
Version: 0.7.3
Severity: minor

Dear Maintainer,

the package I'm building has its upstream branch on 'master' (the current 
release on tag v0.2.0) and the debian branch for sid on 'debian/sid'. I 
therefore have created a configuration file in 'debian/gbp.conf' with the 
following content, so that I can run 'gbp buildpackage' instead of the lengthy 
'gbp buildpackage --git-upstream-tree=v0.2.0 --git-debian-branch=debian/sid':

[buildpackage]
git-upstream-tree=v0.2.0
git-debian-branch=debian/sid

But when I run "gbp buildpackage --git-verbose" I get:

gbp:debug: ['git', 'rev-parse', '--show-cdup']
gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
gbp:debug: /bin/true [] []
gbp:debug: ['git', 'status', '--porcelain']
gbp:debug: ['git', 'symbolic-ref', 'HEAD']
gbp:debug: ['git', 'show-ref', 'refs/heads/debian/sid']
gbp:error: You are not on branch 'master' but on 'debian/sid'
gbp:error: Use --git-ignore-branch to ignore or --git-debian-branch to set the 
branch name.

So it seems that the contents of 'debian/gbp.conf' are not checked before the 
error message regarding the branch names is printed.
I would have expected that the package builds normally.

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

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

Versions of packages git-buildpackage depends on:
ii  devscripts2.16.2
ii  git   1:2.8.0~rc3-1
ii  man-db2.7.5-1
ii  python-dateutil   2.4.2-1
ii  python-pkg-resources  20.7.0-1
ii  python-six1.10.0-3
pn  python:any

Versions of packages git-buildpackage recommends:
ii  cowbuilder   0.79
ii  pbuilder 0.223
ii  pristine-tar 1.33
ii  python-requests  2.9.1-3

Versions of packages git-buildpackage suggests:
ii  python-notify  0.1.1-4
ii  sudo   1.8.15-1.1
ii  unzip  6.0-20

-- no debconf information

Bug#750834: closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#821336: Removed package(s) from unstable)

[Aurelien Jarno]

control: reopen -1
control: reassign -1 gcc-5
control: found -1 gcc-5/5.3.1-14
control: retitle -1 gcc-5: [arm64] float to double conversion does not silence 
sNaN 

On 2016-04-18 18:46, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the gcc-4.8 package:
> 
> #750834: gcc-4.8: [arm64] float to double conversion does not silence sNaN
> 
> It has been closed by Debian FTP Masters .
> 

This bug is still present in GCC 5, though it has been fixed in GCC 6. I
am therefore reopening the bug and reassigning.

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

Bug#821720: src:wikidiff2: PHP 7.0 Transition

[Ondřej Surý]

Package: src:wikidiff2
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The wikidiff2 package currently build-depends on php5 php5-cli php5-dev .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: wikidiff2 -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 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)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUt+XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHlbkP/0+11NgafGrxNxUrJ791AP3l
9YAI5AWSue9Tgm7xx8MiKloU2ZcQx053ayX8nqQXrpVNvxq9IOLM8lZlUszphWXz
Fq15gxkpzqsL+Ikb/bhs5nN5Do6d3zyxuzALoLl4nfGfLldIPHb5/N4og4Q8M03C
8Ck2c7lSff80wCJGIa2HIM5mCQPi0bCRa1QV+CLYKJVPmJ86fso+Fd5XU/JwtX8F
hi5M/F8yOnQzJhS2cmJXL2OJkmAMrrHV7NxmFH3F18XBppmynH1bpnyf86FT7PBM
jqfZ+p4dZeQ6PjNh4pFPyBMbHlaFsZI4L1Cta9Xapii0caLcQxMogdNoS1rvqae+
qxaAQe5kidkY68gf5eCYEMazQ6owxHrBOpewE4NX3Ox9ckFRU/cHUX2+qS/YrDkq
iMOFwsStkugU9ujBPXxBx6zG40dGO3wwAzcGYNihPChsOJ0MDFgGt5RAEbrpdzKd
gMUSwMVU+RERYA7KAUJpKGfwtZ4+6afc6j3oQ8bVoDU/8wEuvh9H/Bj2tDirFIHA
wRxOp53veAR3QhWRBclc4CPqmxkpgTWwAgmuXfgbNDjcol4oXPZpmj92BtN6YaGB
Et0ukk8NScm9pGX7fQZ2IkzOSeBzu3Gu6cJrqlcjl81ToqbbNpshcwcA7M7zbdnu
lk+VG5M049U/+/9l+r2w
=QpCV
-END PGP SIGNATURE-

Bug#821722: src:xhprof: PHP 7.0 Transition

[Ondřej Surý]

Package: src:xhprof
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The xhprof package currently build-depends on php5 php5-dev .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: xhprof -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 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)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUt/XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHsGUQALKSnzaphckxz3Gj48rMog8b
0CkNyIuWWtNXDX6X+MdNttJnk1X3nmzEC43aBEiU0oCz2xTcxtR7MSqjiG0TSeAk
QTjz6Tv65aAcypxeBrEedi8DwMaECWwGLBrt3nWl0ngKYTBE8QHNfTvmPQK8Gzdj
aPk0DMMVIrY8gw21Dd0kF4/lC7974xKYXKmKBOGZk8nK8kiHND86V11xOaoOv61k
L2b1l3mx8Try7++/x4PhaYvSEb/qFrqlplJWxXstvXHRNRX1N2AumJHMFyRJO1Z5
R1INbjz/GZDI3MeU2UnAMAQwXlH7anOhgGYiTE4TSL46dJbBMV8omQR6xmgoHi1v
Rtp7E+O2WcYnNvrOd0Q7frD5E7NC7w0U/GlMZlbeRsfxrdDrhiP8kLq4x+NAT4EW
VspnBQynN8dzTzL6OTk13OLbnOj+HAM5Q60JxMMlk6aYzb+zEc3MO8gZ+YrCQ6ew
1fimH+JQXvoTEvPc9f3xm5foBwLp6stPPcVIuGwQN/N2J5M7zLGq5xUQ2237SOFG
7EE8yIStiJ3lzc34V3Mu7vRXBsYFQIKKlmMMfOhNB1h8nudzuy7IJjo7xebUKu+O
xyn9jduXwtV/KcAJWd2oI7VUfhlwYsZ0MGgQLiH3qptoeLMmX44sBglTAYFdZTes
FHIATSpK6AvaF4yX/1Kl
=MeRE
-END PGP SIGNATURE-

Bug#821715: src:swig: PHP 7.0 Transition

[Ondřej Surý]

Package: src:swig
Version: 3.0.7-2
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The swig package currently build-depends on php5 php5-cgi php5-dev .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: swig -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 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)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUt5XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHfiQQALgG+Z7enkTOqKUNpVvbXQIV
tX5s0m2x7wkBTc+/IMQQOO/ahZxocw5GY0pCYDrieS5patnFksWj26hZYjQ65Lrl
0CHMW/oLY0Wk3ET4wQhcF3qMaCR1nRvnXKGqNriRPGI9kDifx7o9Veoqs7I+bGqg
MMbjMnMfiQaX/Lz1hbKUCHzop/QArAFCZ8w3hJro7U2Mrw/X/miCJhGMGthBT38p
gpp8CrJRjiqSo6BbNpadHn8J/oA4R6VL5Wr9zznMImnfk0NcsMZfH8u90EYdfFNv
M8QE+4za+jQKdB47Taa6kmMW9bNA+qPouqvZto/2lNGMqe+/svEJobihenUuFrGa
dGaPEK/9ecwsgJtdJOdMbsg7yvuD/3EWmwQhTsQsW9M2RaRbDRASomQ1pZotanL6
tjzug3bfxpnQOnOZ00qHjlFGvDkvMzg+C7vVOpBkCKCDamwPuwiHq8vnQx1hJfT2
HdGmy8PLRWwIDEzuItgT9zsY/ZMLlXH1wgf8hTk5BQkRF+VbjWqvUGlULuLuxqr+
rbi299cAhAp/fgzfYrkoRkLPV20PrUl43NjHidN87qHusiKt9OMAihWuAGClqXMO
gCe8WeStN/7s7JMz+pfVZIk4enGcKBaUeCtR0odJB4A8tIhVLPJ1JH6hhTC6Xwqp
9jU8I8ZbC9+htgDGaDDP
=byO0
-END PGP SIGNATURE-

Bug#748616: closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#821336: Removed package(s) from unstable)

[Aurelien Jarno]

control: reopen -1
control: reassign -1 gcc-5
control: found -1 gcc-5/5.3.1-14
control: retitle -1 gcc-5: [armel] float to double conversion does not silence 
sNaN

On 2016-04-18 18:46, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the gcc-4.8 package:
> 
> #748616: gcc-4.8: [armel] float to double conversion does not silence sNaN
> 
> It has been closed by Debian FTP Masters .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters 
>  by
> replying to this email.

The bug is still present in recent GCC version. Reopening and
reassigning.

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

Bug#821717: src:symfony: PHP 7.0 Transition

[Ondřej Surý]

Package: src:symfony
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The symfony package currently build-depends on php5 php5-dev .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: symfony -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 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)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUt7XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHVxYP/jDKCHx9K4fZBkHzsbzEnmJF
oKIwd6DjfBCO36kWI2k9oJ3DMu5/UxXArPbEVIpkQjLqsUy+0XKShIX49z5CcD2A
xl9Byqq51gKCDKMH2tAifAN+pcttjJgew5M3ypjeSPbK2x5TBSMwRCNAeY0bCwbj
CilaOZU+s5TcHjegJF5O+DDu9W7VkS8irbvKLSq77uoGR7jFGQMOQuPdE/3spZN9
MjStFxKumK0L490wiVC897oyrBk0R5XZmh5zF+DkmAJQ5Tssnu9EvPcrEXgBs1CY
7pr5QoQ6C/5MA9o+XmnZIq1mMkK4KaS8NifY4A3a8UfAs9wMh2gmb9QVZcYUMkNe
QhyH1cOb8bjeK4yCCkbumUC0TQt6/3C9+qbCf+BEQF8dJi12f/FWHiGXwAR0JbQ7
yFa5iqrvu/bQLtXvDkF7Y9peagf45xmWTsUNGNK7GP2Z3p/YrUQOtcBJhSPWBDvu
/YhOAjSyFOUfjVsR68Uh2APJyBXyam6/RlIVIblMrhCVGD8fhdSSxB+RQ8/N90/I
osr0GpZ8L+fLdwZv2226Pl2lmvBgHC1xPL6hpPwjFgnzVkhvGtKGmpQaWd2+ajIB
zToGHXkrMqsUBLGPn37vWbpperWQQAHgQdxl6xswGNJaooHf/aLzvuI0s8qrK1O8
AoSLeh+9Zye4T3X/v2Sb
=7QSN
-END PGP SIGNATURE-

Bug#821726: mandelbulber2: please build-depend on libpng-dev (=> libpng16 instead of libpng12)

[Mattia Rizzolo]

Source: mandelbulber2
Version: 2.07.1-1
Severity: serious
Tags: patch
User: lib...@packages.debian.org
Usertags: libpng16-transition
Control: block 650601 by -1

Dear maintainer,

looks like you missed the libpng16 transition :)
This is currently ongoing, and libpng12 is about to be removed *soon*
(for sure from testing in a couple of days).

Please stop build-depending on libpng12-dev and use libpng-dev, which
will pulls libpng16.

I tested it, and it builds with libpng16, patch attached.
If I hear nothing from you, I plan to NMU it.

-- 
regards,
Mattia Rizzolo

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

 changelog |8 
 control   |2 +-
 2 files changed, 9 insertions(+), 1 deletion(-)

diff -Nru mandelbulber2-2.07.1/debian/changelog 
mandelbulber2-2.07.1/debian/changelog
--- mandelbulber2-2.07.1/debian/changelog   2016-04-17 20:30:29.0 
+
+++ mandelbulber2-2.07.1/debian/changelog   2016-04-18 21:03:08.0 
+
@@ -1,3 +1,11 @@
+mandelbulber2 (2.07.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Build depend on libpng-dev instead of libpng12-dev for the libpng16
+transition.  Closes: #xx
+
+ -- Mattia Rizzolo   Mon, 18 Apr 2016 21:02:34 +
+
 mandelbulber2 (2.07.1-1) unstable; urgency=medium
 
   * Initial release (closes: #819431).
diff -Nru mandelbulber2-2.07.1/debian/control 
mandelbulber2-2.07.1/debian/control
--- mandelbulber2-2.07.1/debian/control 2016-04-17 20:30:29.0 +
+++ mandelbulber2-2.07.1/debian/control 2016-04-18 21:02:31.0 +
@@ -2,7 +2,7 @@
 Section: math
 Priority: extra
 Maintainer: Giovanni Mascellani 
-Build-Depends: debhelper (>= 9), qtbase5-dev, libpng12-dev, libgsl-dev,
+Build-Depends: debhelper (>= 9), qtbase5-dev, libpng-dev, libgsl-dev,
  qttools5-dev, qttools5-dev-tools, docbook-xsl, xsltproc
 Standards-Version: 3.9.8
 Homepage: https://github.com/buddhi1980/mandelbulber2


signature.asc
Description: PGP signature

Bug#821725: tuptime: fails to install: unable to open database file

[Andreas Beckmann]

Package: tuptime
Version: 3.3.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package tuptime.
  (Reading database ... 
(Reading database ... 8234 files and directories currently installed.)
  Preparing to unpack .../tuptime_3.3.0-1_amd64.deb ...
  Unpacking tuptime (3.3.0-1) ...
  Processing triggers for systemd (229-4) ...
  Setting up tuptime (3.3.0-1) ...
  adding tuptime user...
  Traceback (most recent call last):
File "/usr/bin/tuptime", line 1117, in 
  main()
File "/usr/bin/tuptime", line 996, in main
  assure_state_db(btime, uptime, kernel, arg)
File "/usr/bin/tuptime", line 283, in assure_state_db
  db_conn = sqlite3.connect(arg.db_file)
  sqlite3.OperationalError: unable to open database file
  dpkg: error processing package tuptime (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for systemd (229-4) ...
  Errors were encountered while processing:
   tuptime


cheers,

Andreas


tuptime_3.3.0-1.log.gz
Description: application/gzip

Bug#821723: src:zeroc-ice: PHP 7.0 Transition

[Ondřej Surý]

Package: src:zeroc-ice
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The zeroc-ice package currently build-depends on php5 php5-dev .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: zeroc-ice -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 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)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUt/XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH57cP/3OC//0U6ab44N0QoeYLSD2e
ug13xx2Tei0h8i6xg3CNHBgYB/eTInkXhLgKylMUFieesUtJKo/iWyb00OQ3Nyuh
Kzj5Vh8lBeShkds6sHmdzunPB2ZJutEHYGLyCc2b7XoEt8PlZGFEMGWHbQFC1nzY
Ae5IgmW33BoojrPLVeWV28lLLoIXwTpZ+IM7e1q8HZPYmpPPFtyYWq7Wlp5MInDW
L/fwwJRzTXRacPxqsa5cT69cRXEuiYouZgkuYQbfses8AEwzKeGaFPmxtVmUix4j
JyxOmA9nCqeUZ89RjO3YlDdOs7AsjJm5QB1+c9TZVMFPoYAc7Hkxbbg+cFrAWfTV
Zo1Kc2tvrr4LEFKADn/72dVfoRqcJtqLoYMRsB1ZeXLhgvKN9Yn17JclSBIeCXc2
mrwxTxfsfZ9rIH2QqrQoPeiYVmexroF4tP451CgNZbxYzZ8ubiDTNnnz1cfkjWUw
Aa1LH1FOOs34LWrZcvhYruA5FFEYL2FaEIO5z29Ij3pj2NQmsXFveTvvxkac5jMQ
ZeCAWLrGJqI2djzlcCKYw1gSVNdx7pZ/t+CKxUgIkdcCwNNBKyKisVyCp+uXk0/4
AvcA4dhrhkJpfRGSYX0GqTDnjwbIYeAotBarX5gBNOrRV2989XS79ecEkV6PYkkY
qzREZXOwEZpyJ5Ak7rP6
=uQ/U
-END PGP SIGNATURE-

Bug#821350: dh-golang: generates rubbish in Built-Using; errors on invocation

[Michael Stapelberg]

Michael, can you take a look at this issue please?

On Mon, Apr 18, 2016 at 12:45 AM, Dmitry Smirnov  wrote:

> Package: dh-golang
> Version: 1.15
> Severity: serious
>
> Recent upload of "rkt" was rejected
>
> rkt_1.4.0+dfsg-1_amd64.deb: Built-Using refers to non-existing source
> package apt (= 1.0.9.10)
>
> due to rubbish in Built-Using field:
>
> apt (= 1.0.9.10), apt (= 1.0.10.2), apt (= 1.2.10)
>
> Also invocation of dh-golang logged the following:
>
> 
>dh_golang -O--buildsystem=golang -O--builddirectory=_build
> can't load package: package github.com/coreos/rkt/api/v1alpha: cannot
> find package "github.com/coreos/rkt/api/v1alpha" in any of:
> /usr/lib/go/src/github.com/coreos/rkt/api/v1alpha (from $GOROOT)
> /build/rkt-1.4.0+dfsg/obj-x86_64-linux-gnu/src/
> github.com/coreos/rkt/api/v1alpha (from $GOPATH)
> can't load package: package github.com/coreos/rkt/rkt: cannot find
> package "github.com/coreos/rkt/rkt" in any of:
> /usr/lib/go/src/github.com/coreos/rkt/rkt (from $GOROOT)
> /build/rkt-1.4.0+dfsg/obj-x86_64-linux-gnu/src/
> github.com/coreos/rkt/rkt (from $GOPATH)
> can't load package: package .: no buildable Go source files in
> /build/rkt-1.4.0+dfsg
> can't load package: package .: no buildable Go source files in
> /build/rkt-1.4.0+dfsg
> dpkg-query: error: --search needs at least one file name pattern argument
>
> Use --help for help about querying packages.
> 
>
> This is regression from "dh-golang" v1.12.
>
> Please investigate.
>
> --
> All the best,
>  Dmitry Smirnov
>  GPG key : 4096R/53968D1B
>
> ---
>
> Truth never damages a cause that is just.
> -- Mahatma Gandhi
>



-- 
Best regards,
Michael

Bug#821724: nmh: fails to install: update-alternatives: error: no alternatives for mailx

[Andreas Beckmann]

Package: nmh
Version: 1.6-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package nmh.
  (Reading database ... 
(Reading database ... 7442 files and directories currently installed.)
  Preparing to unpack .../archives/nmh_1.6-10_amd64.deb ...
  Unpacking nmh (1.6-10) ...
  Setting up nmh (1.6-10) ...
  update-alternatives: error: no alternatives for mailx
  dpkg: error processing package nmh (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   nmh


cheers,

Andreas


nmh_1.6-10.log.gz
Description: application/gzip

Bug#821714: src:simplepie: PHP 7.0 Transition

[Ondřej Surý]

Package: src:simplepie
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The simplepie package currently build-depends on php5 php5-cli .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: simplepie -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 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)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUt5XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHVYIQAJiyPdlr4k5drOwtEe5LrNlp
t60JVQTH50ZdOZKMFELIVp+SfpuWYyyITE8j/WS0y0KgQNQ9ywuh3TjNhKl4UbIP
Qj0CQJtVvs6pWnPO0ZlBrrb9X8XS1PCb6VpAt5GGKAz76Wvf6XyFuP1kvza0jc8I
AX0xbYPQJKY5gvLt+t8wW8tPgb2zX3a4AoFCfmY99BRSDBrZvuwAwReYrTKmDt9U
gD6rCtL7YHgjRC72K2VLb54PVuMhi7Sc5d5SqIUlfwqU/A9kGpdaQVhhohaQFVE7
7aewz80+PCR2j48Q2u9QBjxJbloAg4OjDmx36iYcSDpkw7vt3O+5TyhGYxn7E7mP
RQt93Ju05Tt4WgcfhVIGL88SBCosBk0bYFEVXp6dA2Fmrq2HAItPqr6WWR5cw8DD
h/4BH6F9Mx5UNbgvLMdjn9DHr3GcqTR/wScI6qrTXZJDrY02ePb8OicTvcsnHq4u
az84/XWdo8kv638oJISJrRD48oTbVw6h1rb/JZjurrpA33DQmZjj61BhF57E+HFK
bDDh3s7OapHNKMJtgWQhXaPtwyOOuM5TKirjTJX3Lvfeig7IMml70Gjz7MmfmsM1
iTaooA2Py+xJf7SlvLbdsI/LtGL+MZV0/xFKR7sSZwCBkf89VQRFK25V732xU2vt
lUI+NJSm6tX9WsxWlFbk
=UJ5K
-END PGP SIGNATURE-

Bug#821719: src:twig: PHP 7.0 Transition

[Ondřej Surý]

Package: src:twig
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The twig package currently build-depends on php5 php5-cli php5-dev .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: twig -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 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)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUt8XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHn6AQAL1/uWIoLTVkYeFC8+1bYBQJ
6VFgy0td3kGKHp9sLcXFMNRQutKooywS+PtUMHMmQzA4w4c/AmhnNFo6XpR54xDD
Moq5P4ffYUNI6KCM4lxH/MSvNxoXzdy6CNPJMkzt8MnuNZrhATOzmfyo9i0A5lY0
U54sA3V0kPRXGYeoH0Dyi6k6vU70qkGPPvnGVsbXRBQDvknCAPWiODUf6F3fwgcb
+U1L36VhsG1j8/PInew/JU+WxYMox3bwJE2a65JuUd7Ld6atmpXKdYcnalUBPfwm
VNwcMSxDPmuKZK0rm9foYZQsykiKo07nDHgbBqcBLYypcwXoUUR/9W/5YCNf/+7C
psd8mFuxDk/U6Mi0eL33o95NFVzDHYG8GIC92lNwQHSQgMDnyEEnv037D2QRmNzL
wrXwUmeHY+D8MDThIi6OEkPBqdgIWOXmXtta7I2egWk0sEFabN1q7ZZV2lHA+2+R
K9dS0DsvWZQt2ZHj0WuEQ5ePCkP+dbQg1wepXsoTFuWH4NzJKCTGn3ShOPxxQceV
umx8IUrXeSN3mT5hKRbzJwnbWgaAewc4doP6t8gdx2IC0vy9RG/btIqXnXnnl9Tq
T+lZT45M2RtPyvXsrJoNZ3rTcdnbz4RWhyfCziPUFrKXQ5kh5IYdCoKTZ60ceovz
q+b9AJZf4K/hMwNTa/S2
=v9A2
-END PGP SIGNATURE-

Bug#821716: src:swig2.0: PHP 7.0 Transition

[Ondřej Surý]

Package: src:swig2.0
Version: 2.0.12-1
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The swig2.0 package currently build-depends on php5 php5-cgi php5-dev .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: swig2.0 -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 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)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUt6XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH49MP/A5yWiGccVHl2POlaL74FDVZ
ygkoOr4WJ/C5G3GhAsvTeVlEp7b76OE+D8E46sqEz7nu1vaHTsqDguQboNPp2vpF
rtdseQmg5q417dFZwBPJXV07YgO8D1V8Wd/BedOVZOHjnC9qoYYfq3daSWrB9iQz
6VZAuU38pwfY+TnnY8yAlIFdJjbVAXFCRYNIRd1IiFuQVgZg96zinqwhBPwM4grs
WjyKkxmQWChgDVNTb1lRWa0fXnwpK5WS7Vspr/X5+bMjtyf+TFg1FGoSBC1UEgI/
s3QnLU3cHdXG0UkLj6xccUaVJzRLmChmIfQfC1iVXUOtP7EMaxiL08f2OeUtSL38
C9KveuReahxUjEhVYgw5O7367oLnQwUZzewhquX2JE0xLh3D3RfucQD4esaWddZl
fhO7wTTGFk8kvFgWq70ENe0GoiCAsDH/B5tRSpy0bVlpTFDqUXBe+FTWO3gwQf/m
rZzFs0qIQbCz3mWjBwNMZwWHiKy7gHADLJxEsMbozgtaDp0qpMf2EwFPTZiuMsL6
WiZvrwOUoT9kPnUiujhmTNKKJQ3E7lDUuv4hrZYRZv6YuDX/8ruYIqZm7oYqwHht
QeVMkXk91zEKoC5otrCCb10n+OMej1qZXaa7QVMRxrKqgUuHPtqLqrIy1zyxuuIa
YI+m/T6Z64uHiCMb8NXe
=pimJ
-END PGP SIGNATURE-

Bug#821721: src:uwsgi: PHP 7.0 Transition

[Ondřej Surý]

Package: src:uwsgi
Version: 2.0.12-5
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The uwsgi package currently build-depends on libphp5-embed php5 php5-dev .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: uwsgi -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 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)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUt9XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHhVIQAJCIWVQ6F4MADhI/P1ln/f95
Ln9BBsSb3fRAaYoTS3FKYPGaiGuZdQodGTGBQlsPvraTN6q+2bYOqwe8SoWDuvlj
lvYvtUeLuxIis8ykvfQgy0F8+1AGb/+2ZR+JIz5kfkUK8z9O4NurxaQJqq/kAfDk
mqp3wDCDrbiijnglqsjBBm54v1RCIg59CyGqi7BRQN0Mp9FIno+nOS7cSpO1NB3A
iEd3cy/I82dhL7hMx+ktrzQE1d4oMeAGQo+505wHekAlHwjC8nRDRzoCorw/kOMt
Mkdle4Hu0S9Wj3me61s895gKaTSDrrY/vp2yFxGJ9+5D6FcMstF3fPW/nthoCLQ7
aYmqWPSn49Z34Q7VXJ5Mc+pQpBIBTOKGrtmWGqQW8zz/okdsiafNyzt+03s9v/sf
F2rUwDsMy6a1F6D6gCYi2agBoy7aAMaBdE2P8WVIYzKXonum4+8nLcaoilNYyz8M
IZ3jS8264KtaZZ28JFF5hzuE9cvBjXJevnpNGUlpQcaPooMoWt6JgUMlx+Mr1eiF
51mIuHa3RZzbSvK+6eaObmttcaQW0CeOr5nZxrd+N8q76XrWIy3ey9ydZW+B3k8I
nQPZqWBUEaVEHCxQaSwF+vTYukpdZXQGxruWffgB+MH4SoHhSeYMIw6oLdVit08f
WluX2u1pI8Au3Fh32ZZQ
=gvMd
-END PGP SIGNATURE-