Processed: libarchive: CVE-2016-1541

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 3.2.0-1
Bug #823893 [src:libarchive] libarchive: CVE-2016-1541
Marked as fixed in versions libarchive/3.2.0-1.

-- 
823893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#823893: libarchive: CVE-2016-1541

[Salvatore Bonaccorso]

Source: libarchive
Version: 3.1.2-11
Severity: grave
Tags: security upstream fixed-upstream
Justification: user security hole
Control: fixed -1 3.2.0-1

Hi,

the following vulnerability was published for libarchive.

CVE-2016-1541[0]:
| Heap-based buffer overflow in the zip_read_mac_metadata function in
| archive_read_support_format_zip.c in libarchive before 3.2.0 allows
| remote attackers to execute arbitrary code via crafted entry-size
| values in a ZIP archive.

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-1541
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1541
[1] https://www.kb.cert.org/vuls/id/862384

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: tagging 823863

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 823863 + pending
Bug #823863 [src:xerces-c] xerces-c: CVE-2016-2099: use-after-free
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#760695: marked as done (tinc-gui: Please update to use wxpython3.0)

[Debian Bug Tracking System]

Your message dated Tue, 10 May 2016 15:45:56 +1200
with message-id <20160510034556.ga26...@survex.com>
and subject line Re: Bug#760695: tinc-gui: Please update to use wxpython3.0
has caused the Debian Bug report #760695,
regarding tinc-gui: Please update to use wxpython3.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
760695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tinc-gui
Version: 1.1~pre9-1
Severity: wishlist
User: freewx-ma...@lists.alioth.debian.org
Usertags: wxpy3.0

We're aiming to migrate the archive to using wxpython3.0 instead of
wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released.
This transition is already underway, and is being tracked by the release
team here:

https://release.debian.org/transitions/html/wxpython3.0.html

I noticed that there's a newer version of tinc in experimental, with a
new tinc-gui binary package which depends on python-wxgtk2.8.  I thought
it was useful to file a wishlist bug about this, mostly to give you a heads
up in case the plan is to get this into jessie.

The wxPython 3.0 API mostly adds to the wxPython2.8 API.  Many packages
work with wxPython 3.0 without any changes, but there are a few
incompatibilities.  For example, wx.Color is no longer supported as
an alias for wx.Colour, and some constants which were deprecated in 2.8
have been removed.  All the removed constants I'm aware of were set to 0
in wxPython 2.8, so removing them is still compatible with 2.8.

To assist updating to wxPython 3.0, I've put together a script which
will help make the mechanical changes required.  This is in a git repo
on collab-maint along with a README about using it and updating packages
for wxPython 3.0 in general:

http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git

The script has some options to control the sorts of changes it makes -
see the README and --help output for more information - you can view
the latest version of the README online here:

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

I've developed this script by trying to convert 20+ packages.  Please
try it out on your package - in many cases, it should be enough to get
your package working (if it doesn't already) - if it does, please upload
(and close this bug).

If the script doesn't do the job, please let me know (or improve the
script if you can figure out what it needs to do to get your package
working).

Another issue you may hit is that wxWidgets 3.0 now defaults to enabling
its "WXDEBUG" checks for incorrect API usage, so some applications will
emit scary sounding "assertion failures".  These are unlikely to
actually be new, just in a default build of 2.8, such incorrect uses
were handled quietly behind the scenes.  Sometimes these are easy to
fix, but if not you can easily patch the application to tell wx 3.0 to
handle them in the same way wx 2.8 does - details of how to do so are in
the README:

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

Cheers,
Olly
--- End Message ---
--- Begin Message ---
Control: fixed -1 1.1~pre12-1

This was fixed by the most recent upload to experimental:

Changes:
 tinc (1.1~pre12-1) experimental; urgency=medium
 .
   * New upstream release.
   * Bump Standards-Version.
   * Depend on python-wxgtk3.0 for the GUI.
   * Use dh --with python2.
   * Add Build-Depends for dh-python.
   * Update links in debian/control and debian/copyright.

Cheers,
Olly--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 821484 patch
Bug #821484 [freedombox-setup] freedombox-setup: PHP 7.0 Transition
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
821484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#822467: marked as done (supercollider: FTBFS: error: 'random_device' is not a member of 'std')

[Debian Bug Tracking System]

Your message dated Tue, 10 May 2016 00:34:12 +
with message-id 
and subject line Bug#822467: fixed in supercollider 1:3.7.0~repack-1
has caused the Debian Bug report #822467,
regarding supercollider: FTBFS: error: 'random_device' is not a member of 'std'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
822467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: supercollider
Version: 1:3.6.6~repack-2-2
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> [ 34%] Building CXX object 
> server/supernova/CMakeFiles/libsupernova.dir/sc/sc_plugin_interface.cpp.o
> cd "/<>/obj-x86_64-linux-gnu/server/supernova" && /usr/bin/g++   
> -DDLOPEN -DJACK_BACKEND -DNOVA_SIMD 
> -DSC_DATA_DIR=\"/usr/share/SuperCollider\" -DSC_FFT_FFTW 
> -DSC_PLUGIN_EXT=\".so\" -DSUPERNOVA 
> -I"/<>/obj-x86_64-linux-gnu/common" 
> -I"/<>/external_libraries" 
> -I"/<>/external_libraries/nova-simd" 
> -I"/<>/external_libraries/nova-tt" 
> -I"/<>/external_libraries/boost_endian" 
> -I"/<>/external_libraries/oscpack" 
> -I"/<>/external_libraries/TLSF-2.4.6/src" 
> -I"/<>/include/plugin_interface" 
> -I"/<>/include/server" -I"/<>/include/common" 
> -I"/<>/server/supernova/."  -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
> -ftemplate-depth-4096 -std=c++0x -O2 -g -DNDEBUG   -fschedule-insns2 
> -fomit-frame-pointer -Wreturn-type -fvisibility=hidden -pthread -o 
> CMakeFiles/libsupernova.dir/sc/sc_plugin_i
> nterface.cpp.o -c 
> "/<>/server/supernova/sc/sc_plugin_interface.cpp"
> In file included from 
> /<>/server/supernova/./utilities/named_hash_entry.hpp:27:0,
>  from 
> /<>/server/supernova/sc/../server/synth_definition.hpp:29,
>  from 
> /<>/server/supernova/sc/../server/node_types.hpp:28,
>  from 
> /<>/server/supernova/sc/sc_plugin_interface.hpp:26,
>  from 
> /<>/server/supernova/sc/sc_plugin_interface.cpp:23:
> /<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp: In 
> constructor 'nova::nova_tt::nonrecursive_rw_mutex::nonrecursive_rw_mutex()':
> /<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp:50:13: 
> warning: unused variable 'status' [-Wunused-variable]
>  int status = pthread_rwlock_init(, NULL);
>  ^
> /<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp: In 
> destructor 'nova::nova_tt::nonrecursive_rw_mutex::~nonrecursive_rw_mutex()':
> /<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp:56:13: 
> warning: unused variable 'status' [-Wunused-variable]
>  int status = pthread_rwlock_destroy();
>  ^
> /<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp: In member 
> function 'void nova::nova_tt::nonrecursive_rw_mutex::lock()':
> /<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp:62:13: 
> warning: unused variable 'status' [-Wunused-variable]
>  int status = pthread_rwlock_wrlock();
>  ^
> /<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp: In member 
> function 'void nova::nova_tt::nonrecursive_rw_mutex::unlock()':
> /<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp:90:13: 
> warning: unused variable 'status' [-Wunused-variable]
>  int status = pthread_rwlock_unlock();
>  ^
> /<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp: In member 
> function 'void nova::nova_tt::nonrecursive_rw_mutex::lock_shared()':
> /<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp:96:13: 
> warning: unused variable 'status' [-Wunused-variable]
>  int status = pthread_rwlock_rdlock();
>  ^
> /<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp: In member 
> function 'void nova::nova_tt::rw_mutex::unlock_shared()':
> /<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp:238:13: 
> warning: unused variable 'status' [-Wunused-variable]
>  int status = pthread_rwlock_unlock();
>  ^
> In file included from 
> /<>/server/supernova/sc/../server/node_types.hpp:28:0,
>  from 
> /<>/server/supernova/sc/sc_plugin_interface.hpp:26,
>  from 
> /<>/server/supernova/sc/sc_plugin_interface.cpp:23:
> /<>/server/supernova/sc/../server/synth_definition.hpp: In 
> member function 'void nova::detail::slot_resolver::register_slot(const 
> nova::c_string&, nova::slot_index_t)':
> /<>/server/supernova/sc/../server/synth_definition.hpp:87:14: 
> warning: unused variable 'success' [-Wunused-variable]

Bug#822467: marked as pending

[Felipe Sateler]

tag 822467 pending
thanks

Hello,

Bug #822467 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=pkg-multimedia/supercollider.git;a=commitdiff;h=18d3ef6

---
commit 18d3ef669bafd533476fe4c7a960a8b1ec51ca8f
Author: Felipe Sateler 
Date:   Mon May 9 21:14:23 2016 -0300

Release to unstable

diff --git a/debian/changelog b/debian/changelog
index fe96283..611e5d3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,14 +1,18 @@
-supercollider (1:3.7.0~repack-1) UNRELEASED; urgency=medium
+supercollider (1:3.7.0~repack-1) unstable; urgency=medium
 
   [ Dan Stowell ]
-  * Update watch file (github now not sourceforge)
-  * Update upstream url (github now not sourceforge)
-  * Prepare rules for importing supercollider 3.7.0
-  * Imported Upstream version 3.7.0~repack
-  * Update dependencies for new version
-  * Remove mathjax dependency management, dropped upstream
-  * Remove boost-lockfree from copyright, dropped upstream
-  * Refresh patches, and drop outdated ones
+  * Update upstream url references (github now not sourceforge)
+  * New Upstream version
+- Closes: #822467
+- Update dependencies for new version
+- Remove mathjax dependency management, dropped upstream
+- Remove boost-lockfree from copyright, dropped upstream
+- Refresh patches, and drop outdated ones
+- Update copyright information
+- Add patch to fix FTBFS when using system boost
+- Update install rules for changed readme filenames
+- Add patch to fix FTBFS, add -fPIC flag to tlsf build
+  * Ignore lintian error about (unused) portaudio config files
 
   [ IOhannes m zmölnig ]
   * Use https:// in Vcs-Browser stanza
@@ -16,7 +20,15 @@ supercollider (1:3.7.0~repack-1) UNRELEASED; urgency=medium
   [ Hanno Zulla ]
   * Update upstream homepage URL, fix vcs-field-uses-insecure-uri
 
- -- Dan Stowell   Sun, 13 Mar 2016 21:40:42 
+
+  [ Felipe Sateler ]
+  * Ship mime info in -common package, not -gedit package
+  * Bump Standards-Version to 3.9.8
+- Drop menu files in favor of the desktop entries
+
+  [ Jonas Smedegaard ]
+  * Remove myself as uploader.
+
+ -- Felipe Sateler   Mon, 09 May 2016 20:59:52 -0300
 
 supercollider (1:3.6.6~repack-2-2) unstable; urgency=medium
 

Processed: Bug#822467 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 822467 pending
Bug #822467 [supercollider] supercollider: FTBFS: error: 'random_device' is not 
a member of 'std'
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
822467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#823881: dosfstools: mmd fails right after mkfs.msdos (sectors/tracks mismatch)

[Cyril Brulebois]

Package: dosfstools
Version: 4.0-1
Severity: serious
Tags: d-i
Justification: d-i build failure/regression, without blatant misusage from 
d-i's side

Control: affects -1 src:debian-installer

(Please keep debian-b...@lists.debian.org and debian-...@lists.debian.org
in the loop when replying.)

Hi,

The version bump from 3.0.28-2 to 4.0-1 led to a new FTBFS on all EFI
archs for debian-installer (amd64, arm64, i386), where the following
operations are happening:
| + mkfs.msdos -C ./tmp/netboot-gtk/grub_efi/efi.img 416
| mkfs.fat 4.0 (2016-05-06)
| + mmd -i ./tmp/netboot-gtk/grub_efi/efi.img ::efi
| Total number of sectors (832) not a multiple of sectors per track (63)!
| Add mtools_skip_check=1 to your .mtoolsrc file to skip this test
| + cleanup
| + [ -z efi-image.7vXUPq ]
| + rm -f efi-image.7vXUPq
| + [ -z efi-image.u4utfz ]
| + rm -rf efi-image.u4utfz
| config/x86.cfg:38: recipe for target 'x86_grub_efi' failed

This can be reproduced with:
| make -C build build_netboot-gtk USE_UDEBS_FROM=sid

after having added "set -x" at the top of build/util/efi-image in
src:debian-installer.

After a quick look, it seems the d-i build system is only passing a
number of blocks to mkfs.{msdos,fat}, without specifying strange
parameters for sectors or trackers, so it looks to me that mkfs's
or mmd's behaviour is buggy.

Incidently, 832 isn't a multiple of 63, but is a multiple of 64. Could
there be some off-by-one somewhere?

Switching on verbose mode (adding -v):
| + mkfs.msdos -v -C ./tmp/netboot-gtk/grub_efi/efi.img 416
| mkfs.fat 4.0 (2016-05-06)
| ./tmp/netboot-gtk/grub_efi/efi.img has 255 heads and 63 sectors per track,

| hidden sectors 0x;
| logical sector size is 512,
| using 0xf8 media descriptor, with 832 sectors;
| drive number 0x80;
| filesystem has 2 12-bit FATs and 4 sectors per cluster.
| FAT size is 1 sector, and provides 199 clusters.
| There is 1 reserved sector.
| Root directory contains 512 slots and uses 32 sectors.
| Volume ID is 0da76041, no volume label.
| + mmd -i ./tmp/netboot-gtk/grub_efi/efi.img ::efi
| Total number of sectors (832) not a multiple of sectors per track (63)!
| Add mtools_skip_check=1 to your .mtoolsrc file to skip this test
| + cleanup
| + [ -z efi-image.AQOJ9R ]
| + rm -f efi-image.AQOJ9R
| + [ -z efi-image.dShhUx ]
| + rm -rf efi-image.dShhUx
| config/x86.cfg:38: recipe for target 'x86_grub_efi' failed

Comparing with the previous version (downgrading to 3.0.28-2):
| + mkfs.msdos -v -C ./tmp/netboot-gtk/grub_efi/efi.img 416
| mkfs.fat 3.0.28 (2015-05-16)
| ./tmp/netboot-gtk/grub_efi/efi.img has 64 heads and 32 sectors per track,
^^^
| hidden sectors 0x;
| logical sector size is 512,
| using 0xf8 media descriptor, with 832 sectors;
| drive number 0x80;
| filesystem has 2 12-bit FATs and 4 sectors per cluster.
| FAT size is 1 sector, and provides 199 clusters.
| There is 1 reserved sector.
| Root directory contains 512 slots and uses 32 sectors.
| Volume ID is 1666ec2f, no volume label.
| + mmd -i ./tmp/netboot-gtk/grub_efi/efi.img ::efi
| + mmd -i ./tmp/netboot-gtk/grub_efi/efi.img ::efi/boot
| + mcopy -i ./tmp/netboot-gtk/grub_efi/efi.img efi-image.qksN5Q/bootx64.efi 
::efi/boot/bootx64.efi
| + grub-cpmodules ./tmp/netboot-gtk/grub_efi x86_64-efi
| + exit 0

It would be great if this could be investigated shortly, as I'd like to
prepare a new d-i release soon:
  https://lists.debian.org/debian-boot/2016/05/msg00055.html


KiBi.

Bug#823880: libsvm : binary files in source package

[Dominique Belhachemi]

Package: libsvm
Version: 3.12-1.1
Severity: serious

The source package contains binary files, see

https://sources.debian.net/src/libsvm/3.12-1.1/windows/
https://sources.debian.net/src/libsvm/3.12-1.1/java/


v3.12 is from 2012, please consider an update to a recent version (
https://github.com/cjlin1/libsvm/releases )

Processed: severity of 823871 is important, notfound 823871 in 4.5.1-1, found 823871 in 4.5.3-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 823871 important
Bug #823871 [src:linux] linux-image-4.5.0-2-amd64: Cannot access TV-ATSC 
Digital Card
Severity set to 'important' from 'grave'
> notfound 823871 4.5.1-1
Bug #823871 [src:linux] linux-image-4.5.0-2-amd64: Cannot access TV-ATSC 
Digital Card
No longer marked as found in versions linux/4.5.1-1.
> found 823871 4.5.3-2
Bug #823871 [src:linux] linux-image-4.5.0-2-amd64: Cannot access TV-ATSC 
Digital Card
Marked as found in versions linux/4.5.3-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Merge duplicate

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 821126 udisks2
Bug #821126 [gparted] gparted: mount is unsupported.
Bug reassigned from package 'gparted' to 'udisks2'.
No longer marked as found in versions gparted/0.19.0-2.
Ignoring request to alter fixed versions of bug #821126 to the same values 
previously set
> forcemerge 782838 821126
Bug #782838 {Done: Michael Gilbert } [udisks2] 
udisks2-inhibit mount move fails
Bug #821126 [udisks2] gparted: mount is unsupported.
Severity set to 'critical' from 'serious'
Marked Bug as done
Added indication that 821126 affects gparted
Marked as fixed in versions udisks2/2.1.5-1.
Marked as found in versions udisks2/2.1.3-5.
Added tag(s) confirmed.
Merged 782838 821126
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
782838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782838
821126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#822477: marked as done (qgis: FTBFS: error: request for member 'insert' in 'qm', which is of pointer type 'QMap)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 23:02:55 +
with message-id 
and subject line Bug#822477: fixed in qgis 2.14.2+dfsg-1~exp1
has caused the Debian Bug report #822477,
regarding qgis: FTBFS: error: request for member 'insert' in 'qm', which is of 
pointer type 'QMap
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
822477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qgis
Version: 2.14.1+dfsg-2
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> cd /<>/qgis-2.14.1+dfsg/debian/build/src/gui && /usr/bin/c++   
> -DPYTHON2 -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII 
> -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_SQL_LIB -DQT_SVG_LIB -DQT_WEBKIT_LIB 
> -DQT_XML_LIB -DWITH_QTWEBKIT -Dqgis_gui_EXPORTS -isystem /usr/include/qt4 
> -isystem /usr/include/qt4/QtOpenGL -isystem /usr/include/qt4/QtSvg -isystem 
> /usr/include/qt4/QtWebKit -isystem /usr/include/qt4/QtGui -isystem 
> /usr/include/qt4/QtXml -isystem /usr/include/qt4/QtSql -isystem 
> /usr/include/qt4/QtNetwork -isystem /usr/include/qt4/QtCore 
> -I/<>/qgis-2.14.1+dfsg/debian/build -isystem 
> /usr/include/qt4/QtUiTools -I/<>/qgis-2.14.1+dfsg/src/gui 
> -I/<>/qgis-2.14.1+dfsg/src/gui/symbology-ng 
> -I/<>/qgis-2.14.1+dfsg/src/gui/attributetable 
> -I/<>/qgis-2.14.1+dfsg/src/gui/auth 
> -I/<>/qgis-2.14.1+dfsg/src/gui/editorwidgets 
> -I/<>/qgis-2.14.1+dfsg/src/gui/editorwidgets/core 
> -I/<>/qgis-2.14.1+dfsg/s
> rc/gui/layertree -I/<>/qgis-2.14.1+dfsg/src/gui/effects 
> -I/<>/qgis-2.14.1+dfsg/src/gui/../core 
> -I/<>/qgis-2.14.1+dfsg/src/gui/../core/auth 
> -I/<>/qgis-2.14.1+dfsg/src/gui/../core/composer 
> -I/<>/qgis-2.14.1+dfsg/src/gui/../core/geometry 
> -I/<>/qgis-2.14.1+dfsg/src/gui/../core/layertree 
> -I/<>/qgis-2.14.1+dfsg/src/gui/../core/raster 
> -I/<>/qgis-2.14.1+dfsg/src/gui/../core/symbology-ng 
> -I/<>/qgis-2.14.1+dfsg/src/gui/../core/effects 
> -I/<>/qgis-2.14.1+dfsg/debian/build/src/gui 
> -I/<>/qgis-2.14.1+dfsg/debian/build/src/gui/../ui -isystem 
> /usr/include/QtCrypto -isystem /usr/include/qwt -isystem /usr/include/gdal  
> -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security 
> -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -Wdate-time -D_FORTIFY_SOURCE=2  
> -DSPATIALITE_VERSION_GE_4_0_0 -DSPATIALITE_VERSION_G_4_1_1 
> -DSPATIALITE_HAS_INIT_EX -std=c++11 -Wall -Wextra -Wno-long-long 
> -Wformat-security -Wno-strict-aliasing -fvisibility=hidden 
> -fvisibility-inlines-hidden -fPIC   -DCORE_EXPORT= -DGUI_EXPORT= 
> -DPYTHON_EXPORT= -DANALYSIS_EXPORT= -DAPP_EXPORT= -DCUSTOMWIDGETS_EXPORT= 
> -DSERVER_EXPORT= -UGUI_EXPORT "-DGUI_EXPORT=__attribute__ ((visibility 
> (\"default\")))" -o CMakeFiles/qgis_gui.dir/qgssvgannotationitem.cpp.o -c 
> /<>/qgis-2.14.1+dfsg/src/gui/qgssvgannotationitem.cpp
> /<>/qgis-2.14.1+dfsg/python/core/conversions.sip: In function 'int 
> convertTo_QMap_3800_0600QMap_1800_0100QVariant(PyObject*, void**, int*, 
> PyObject*)':
> /<>/qgis-2.14.1+dfsg/python/core/conversions.sip:735:8: error: 
> request for member 'insert' in 'qm', which is of pointer type 'QMap int, QMap >*' (maybe you meant to use '->' ?)
>  qm.insert(k, *t);
> ^

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: qgis
Source-Version: 2.14.2+dfsg-1~exp1

We believe that the bug you reported is fixed in the latest version of
qgis, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated qgis package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 29 Apr 2016 21:07:07 +0200
Source: qgis
Binary: qgis qgis-common libqgis-app2.14.2 libqgis-core2.14.2 libqgis-gui2.14.2 
libqgis-analysis2.14.2 libqgis-networkanalysis2.14.2 libqgisgrass7-2.14.2 
libqgispython2.14.2 libqgis-customwidgets libqgis-server2.14.2 libqgis-dev 
qgis-dbg 

Bug#823164: (no subject)

[Roland Hieber]

Inspired by [0] I tried to build gobject-introspection with the
following patch:

Index: gobject-introspection-1.48.0/gir/gobject-2.0.c
===
--- gobject-introspection-1.48.0.orig/gir/gobject-2.0.c
+++ gobject-introspection-1.48.0/gir/gobject-2.0.c
@@ -1947,7 +1947,7 @@
 /**
  * g_closure_invoke:
  * @closure: a #GClosure
- * @return_value: (optional) (out): a #GValue to store the return
+ * @return_value: (optional) (in): a #GValue to store the return
  *value. May be %NULL if the callback of @closure
  *doesn't return a value.
  * @n_param_values: the length of the @param_values array


... but this doesn't fix the problem with lua-lgi. So there must be
something else here.

[0]: https://github.com/pavouk/lgi/issues/132#issuecomment-202408015


 - Roland

Processed (with 1 error): Merge duplicate

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 782838 821126
Bug #782838 {Done: Michael Gilbert } [udisks2] 
udisks2-inhibit mount move fails
Unable to merge bugs because:
package of #821126 is 'gparted' not 'udisks2'
Failed to forcibly merge 782838: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
782838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782838
821126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#794933: Info received ()

[Sami Abbessi]

Le 9 mai 2016 23:27, "Debian Bug Tracking System"  a
écrit :

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Apache Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 794...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 794933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794933
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#794933:

[Sami Abbessi]

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 820249 by 812838
Bug #820249 [src:golang-github-miekg-pkcs11] Please switch from softhsm to 
softhsm2
820249 was not blocked by any bugs.
820249 was blocking: 820235
Added blocking bug(s) of 820249: 812838
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
820249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#820149: [#820149] Fixed by uploading newer upstream version

[Potter, Tim (HPE Linux Support)]

This FTBFS should be fixed by the upload of the newer version in #812838.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#804531: eagle: cannot be rebuilt against libssl1.0.2

[Sebastian Andrzej Siewior]

On 2016-04-22 00:19:58 [+0200], Andreas Beckmann wrote:
> Since the only API/ABI difference between libssl1.0.0 and libssl1.0.2 is
> the removal of some symbols, you could try the following:
…

| $ readelf -a bin/eagle|grep -i SSLv3
|09aa3640  00019607 R_386_JUMP_SLOT      SSLv3_client_method
|09aa36ec  0001c207 R_386_JUMP_SLOT      SSLv3_server_method
|   406:  0 FUNCGLOBAL DEFAULT  UND SSLv3_client_method
|   450:  0 FUNCGLOBAL DEFAULT  UND SSLv3_server_method

Haven't tried it but it seems that the binary uses the removed symbols.

Besides I looked at the license [0]:
- 2.1.b says "not to … vary or modify the Software" so I think the
  change of libssl1.0.0 -> .2 is not permitted.
- 2.1.c says "… nor permit the Software or any part of it to be  combined
  with, or become incorporated in, any other programs;" which sounds
  like redistribution is not allowed
- 2.1.i puts it this way: "not to provide or otherwise make available
  the Software in whole or in part … in any form to any person … without
  prior written consent from the Licensor.".

Redistributing may be allowed due to the chapter in debian/copyright. It
is not the latest [1] available document which might be "recent" and the
license seems to have change a little, too.

[0] https://sources.debian.net/src/eagle/7.5.0-1/doc/license_en.txt/
[1] 
http://www.cadsoftusa.com/fileadmin/journalist/Documents/redistribute-eagle-freeware-letter.odt

> Andreas

Sebastian

Bug#823711: marked as done (cpputest: non-free files)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 21:50:33 +
with message-id 
and subject line Bug#823711: fixed in cpputest 3.7.2+dfsg-1
has caused the Debian Bug report #823711,
regarding cpputest: non-free files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
823711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpputest
Version: 3.7.2-1
Severity: serious
Usertags: dfsg

Files:  

 
platforms_startup/armcc/AT91SAM7A3/Retarget.c
platforms_startup/armcc/AT91SAM7A3/SAM7A3.asm
platforms_startup/armcc/LPC1768/Retarget.c
platforms_startup/armcc/LPC1768/Serial.h
Copyright:
2004-2012 Keil - An ARM Company
2005-2008 Keil Software
License: Keil
 This software may only be used under the terms of a valid, current,
 end user licence from KEIL for a compatible version of KEIL software
 development tools. Nothing else gives you the right to use this software.

---

Files:  

 
platforms_examples/armcc/AT91SAM7A3/tests/main.cpp
platforms_examples/armcc/LPC1768/tests/main.cpp
Copyright: James W. Grenning
License: RSCC-training
 For use by owners of Test-Driven Development for Embedded C,
 and attendees of Renaissance Software Consulting, Co. training
 classes.
 Authorized users may use this source code in your own projects, however
 the source code may not be used to create training material, courses,
 books, articles, and the like. We make no guarantees that this source code
 is fit for any purpose.

---

Files:
platforms_startup/armcc/LPC1833/cmsis_18xx.h
platforms_startup/armcc/LPC1833/retarget.c
platforms_startup/armcc/LPC1833/startup_LPC18xx.asm
platforms_startup/armcc/LPC1768/lpc17xx_clkpwr.c
platforms_startup/armcc/LPC1768/lpc17xx_clkpwr.h
platforms_startup/armcc/LPC1768/lpc17xx_libcfg_default.c
platforms_startup/armcc/LPC1768/lpc17xx_libcfg_default.h
platforms_startup/armcc/LPC1768/lpc17xx_pinsel.h
platforms_startup/armcc/LPC1768/lpc17xx_timer.c
platforms_startup/armcc/LPC1768/lpc17xx_timer.h
platforms_startup/armcc/LPC1768/lpc_types.h
Copyright:
2012-2013 NXP Semiconductors
2008,2010-2011 NXP Semiconductor
License: Custom-NXP-S
 Permission to use, copy, modify, and distribute this software and its
 documentation is hereby granted, under NXP Semiconductors' and its
 licensor's relevant copyrights in the software, without fee, provided that
 it is used in conjunction with NXP Semiconductors microcontrollers. This
 copyright, permission, and disclaimer notice must appear in all copies of
 this code.
Comment:
 Comparing to other two, this license is less extreme but clause
 "provided that it is used in conjunction with NXP Semiconductors
 microcontrollers" looks like use restriction to me.

Please investigate.

-- 
Regards,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

Sometimes the first duty of intelligent men is the restatement of the
obvious.
-- George Orwell



signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: cpputest
Source-Version: 3.7.2+dfsg-1

We believe that the bug you reported is fixed in the latest version of
cpputest, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 823...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated cpputest package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 May 2016 22:15:27 +0200
Source: cpputest
Binary: cpputest libcpputest-dev
Architecture: source
Version: 3.7.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Raphaël Hertzog 
Changed-By: Raphaël Hertzog 

Bug#822755: Tested on two more computers with identical pkg selection criteria : bug is everywhere

[Eric Valette]

So I hardly think this is not widely reproducible provided you have 
unstable + experimental up-to-date combination.


-- eric

Bug#823812: netbeans: non-free files

[Markus Koschany]

Hi,

Am 09.05.2016 um 12:11 schrieb Dmitry Smirnov:
> Source: netbeans
> Version: 8.1+dfsg2-3
> Severity: serious
> Usertags: dfsg
> 
> Files:
> cnd/javahelp/org/netbeans/modules/cnd/help/legal_notice.htm
> 
> javacard.project/javahelp/org/netbeans/modules/javacard/project/docs/help/docinfo.html
> 
> Contain fairly restrictive license:
> 
> 
> Except as expressly permitted in your
> license agreement or allowed by law, you may not use, copy, reproduce,
> translate, broadcast, modify, license, transmit, distribute, exhibit,
> perform, publish, or display any part, in any form, or by any means.
> Reverse engineering, disassembly, or decompilation of this software, unless
> required by law for interoperability, is prohibited.

It sounds scary but the first part of the sentence is important:

"Except as expressly permitted in your license agreement..."

The license agreement is GPL-2+-with-classpath-exception or CDDL-1

> 
> Those terms seems to apply to other files in respective directories.
> 
> File:
> 
> java.sourceui/test/unit/src/org/netbeans/api/java/source/ui/FileChooser.html
> 
> is explicitly licensed under those terms.

FileChooser.html does not contain a specific license grant. There are
more files under ui but those contain the standard license headers,
GPL-2+-with-classpath-exception or CDDL-1

> 
> 
> 
> File:
> 
> javascript2.extjs/test/unit/data/testfiles/completion/applyMethod/ClassManager.js
> 
> contains the following:
> 
> 
> Licensees holding valid commercial licenses may use this file in accordance 
> with the Commercial
> Software License Agreement provided with the Software or, alternatively, in 
> accordance with the
> terms contained in a written agreement between you and Sencha.
> 
> 
> However no other license is mentioned.

That's true and I wished upstream would be more careful about this.
However this file is part of the ExtJS framework from Sencha and is also
licensed under the GPL-3. I will update debian/copyright accordingly.



> 
> 
> 
> Files:
> j2ee.dd/src/org/netbeans/modules/j2ee/dd/impl/resources/web-app_2_3.dtd
> 
> j2ee.ddloaders/src/org/netbeans/modules/j2ee/ddloaders/catalog/resources/web-app_2_3.dtd
> 
> j2ee.sun.dd/src/org/netbeans/modules/j2ee/sun/dd/impl/resources/static-verification_1_4.dtd
> 
> j2ee.weblogic9/src/org/netbeans/modules/j2ee/weblogic9/resources/ejb-jar_2_1.xsd
> 
> j2ee.weblogic9/src/org/netbeans/modules/j2ee/weblogic9/resources/j2ee_1_4.xsd
> 
> j2ee.weblogic9/src/org/netbeans/modules/j2ee/weblogic9/resources/j2ee_web_services_client_1_1.xsd
> 
> j2ee.weblogic9/src/org/netbeans/modules/j2ee/weblogic9/resources/jsp_2_0.xsd
> 
> j2ee.weblogic9/src/org/netbeans/modules/j2ee/weblogic9/resources/web-app_2_4.xsd
> schema2beans/test/unit/data/TestApplication1_4.xsd
> schema2beans/test/unit/data/TestFinalWebApp.xsd
> schema2beans/test/unit/data/TestWebApp.xsd
> schema2beans/test/unit/data/TestWebAppDelegator.xsd
> schema2beans/test/unit/data/TestWebAppDelegatorBaseBean.xsd
> schema2beans/test/unit/data/final_j2ee_1_4.xsd
> schema2beans/test/unit/data/final_jsp_2_0.xsd
> schema2beans/test/unit/data/j2ee_1_4.xsd
> schema2beans/test/unit/data/j2ee_web_services_client_1_1.xsd
> schema2beans/test/unit/data/jsp_2_0.xsd
> web.core/src/org/netbeans/modules/web/taglib/resources/j2ee_1_4.xsd
> 
> web.core/src/org/netbeans/modules/web/taglib/resources/j2ee_web_services_client_1_1.xsd
> 
> web.core/src/org/netbeans/modules/web/taglib/resources/web-jsptaglibrary_2_0.xsd
> 
> 
>  This document and the technology which it describes are
>  distributed under licenses restricting their use, copying,
>  distribution, and decompilation. No part of this document
>  may be reproduced in any form by any means without prior
>  written authorization of Sun and its licensors, if any.
> 

Sun Microsystems was bought by Oracle a few years ago. The schema
resources / specifications are licensed under the standard license now. See

http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html

and download some of the files to verify this statement.


> 
> Same terms are also present in the following files, under
> "CDDL or GPL-2 and exception-GPL-Classpath" header:
> 
> Files:
> web.jsf/src/org/netbeans/modules/web/jsf/resources/javaee_5.xsd
> 
> web.jsf/src/org/netbeans/modules/web/jsf/resources/javaee_web_services_client_1_2.xsd
> web.jsf/src/org/netbeans/modules/web/jsf/resources/web-facesconfig_1_2.xsd
> web.jsf/src/org/netbeans/modules/web/jsf/resources/web-facesconfig_2_0.xsd
> 
> 

See above

> 
> File:
> php.editor/test/unit/data/testfiles/parser/performance/performance.php
> 
> is from "SMF 1.1" which is non-free according to
> 
> http://www.simplemachines.org/about/opensource.php
> 
> 
>  The license used for SMF 1.0 and SMF 1.1 is more restrictive than OSI
>  approved licenses. That 

Bug#806377: debirf : libfakechroot version 2.18-1 from sid is needed - even on jessie

[Daniel Kahn Gillmor]

On Thu 2016-01-21 17:59:45 -0500, Daniel Kahn Gillmor  
wrote:
> On Thu 2016-01-21 16:14:30 -0500, jhcha54008 wrote:
>> The current version 2.17.2-1 of libfakechroot in jessie is unusable with 
>> debootstrap
>> (#745082). This may be one of the causes of #809410 too.
>>
>> You may try debirf with fakechroot and libfakechroot version 2.18-1 from 
>> stretch or
>> sid installed.
>
> I've tried this in the past and it worked for me.  I've been meaning to
> set up the debirf autobuilder to work that way.
>
>> Would it make sense to have version 2.18-1 backported to jessie - or
>> included in a coming jessie point release ?
>
> I think getting it in backports at least would be nice, but i dunno
> about the getting into a point release.  That might not be something
> that the release team would be OK with.  If you wanted to start with a
> backport, that would be a good demonstration, i think.

I've just gone ahead with a fakechroot upload to debian-backports
(2.18-1~bpo8+1), which is about as simple as a backport can be.  It also
works for me on amd64, i'm hoping it will work as well on other
architectures.

I've published the debian packaging for the fakechroot jessie-backports
branch over in my personal vcs space on alioth:
 
 git://anonscm.debian.org/git/users/dkg/fakechroot.git
 
   (and should be visible in an hour or so at:)
 https://anonscm.debian.org/git/users/dkg/fakechroot.git

i'm happy to use a branch on the main alioth repo if you like, but
that'd mean i'd need permissions in scm_fakechroot, which i don't have
yet (i've just requested membership in case you want me to do that,
Piotr).

Regards,

--dkg


signature.asc
Description: PGP signature

Bug#821485: Bumping severity of PHP 7.0 transition bugs to serious

[Benoit Mortier]

On Thu, 5 May 2016 10:20:55 +0200 =?utf-8?B?T25kxZllaiBTdXLDvQ==?=
 wrote:
> Dear maintainer(s),

Hello,

> I am bumping the severity of this bug to serious, as we are going to
> remove src:php5 from Debian and your package is blocking the first
> step which is removal of php5 from testing.  Please either update your
> package to support PHP 7.0 or remove the package from Debian unstable
> alltogether.

Yes it should be removed from debian as the actual version in debian is
not compatible with php7.

The future version 1.0.13 will be fully compatible php5 and php7 and
should be uploaded to debian after this release

Cheers
-- 
Benoit Mortier
CEO
OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
Promouvoir et défendre le Logiciel Libre http://www.april.org/
Main developper in FusionDirectory : http://www.fusiondirectory.org/
Official French representative for OPSI : http://opsi.org/



signature.asc
Description: OpenPGP digital signature

Bug#823788: [buildd-tools-devel] Bug#823788: sbuild: non-error on stderr: "There are no foreign architectures configured"

[Adam Borowski]

On Mon, May 09, 2016 at 08:37:13AM +0200, Johannes Schauer wrote:
> Quoting Adam Borowski (2016-05-09 04:19:23)
> > I'm afraid that today's update introduced a spurious message, emitted both
> > on package build and on chroot update:
> > "There are no foreign architectures configured".

Correction: turns out this happens with sbuild-update but _not_ sbuild
itself.  I have no idea how I got the impression it's the case, sorry for
wasting your time with this part.

> > Putting aside the question whether this message fits places it's emitted, it
> > definitely shouldn't be written to stderr.  This breaks scripts that assume
> > stderr output means errors.  This includes for example cronjobs to update
> > chroots.
> 
> I want to better understand what scripts using sbuild expect from it.
>
> I don't think it has been the case before that sbuild only writes error
> messages to stderr. I see lots of output done to stderr which is merely status
> display. For example:
> 
>  | Checking available source versions...
> 
> or
> 
>  | Not removing foreign architectures: cloned chroot in use

Nope, nothing of these goes to stderr:

Good package:
[/tmp]$ sbuild tran >/dev/null;echo $?
0

Unknown package:
[/tmp]$ sbuild kjdgndfkjgh >/dev/null;echo $?
E: Failed to fetch source files
3

Invalid version:
[/tmp]$ sbuild tran_2 >/dev/null;echo $?
E: Failed to fetch source files
3

FTBFS ("failed"):
[/tmp]$ sbuild proll >/dev/null;echo $?
E: Package build dependencies not satisfied; skipping
3

FTBFS ("attempted"):
[/tmp]$ sbuild debdry >/dev/null; echo $?
2

In the last case sbuild is even too unchatty.

> As far as I understand the codebase, errors are differentiated by warnings and
> informational messages by their prefix. Errors start with "E: ". So it is true
> that many informational messages (see above) are not prefixed with a "I: " as
> they should.

It'd be nice if you could prefix "There are no foreign architectures configured"
with an "I: ", it currently sounds like a warning of some kind.

> But I do not see that this situation is actually a regression because as I
> showed above, sbuild already outputs lots of information of merely
> informational value on stderr.

Neither sbuild nor sbuild-update put information to stderr, except for this
new message in sbuild-update.

> So I need to understand:
> 
>  - which scripts break?
>  - what to scripts expect?
>  - how was the situation before any different than the one now?

In my case, crontab with:

5 3,15 * * *sbuild-update -udcar jessie stretch unstable >/dev/null

I'd think a good part of sbuild users run sbuild-update from cron like this,
at least this seems a natural thing to do.
 
> It would also be helpful if you could write me a command for me to try out 
> such
> that I see what exactly what breaks.

sbuild-update -udcar unstable >/dev/null
which should say nothing unless there's an error, but currently emits this
line.


Meow!
-- 
How to exploit the Bible for weight loss:
Pr28:25: he that putteth his trust in the ʟᴏʀᴅ shall be made fat.

Bug#823871: linux-image-4.5.0-2-amd64: Cannot access TV-ATSC Digital Card

[Stephen]

Package: src:linux
Version: 4.5.1-1
Severity: grave
Justification: renders package affected(TV Card) unusable

Dear Maintainer,


This bug applies to 'linux-image-4.5.0-2-amd64' I'm presently booted
into the ...01 version which works OK.

Anyway my Hauppauge internal ATSC card doesn't function with kernel
4.5.0.2, it's OK with 4.5.0.1 hence maybe a kernel driver regression?
I'll leave it in your teams capable hands. Any further information
needed, please shoot me an email.

Regards.

-- Package-specific info:
** 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)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.5.0-1-amd64 
root=UUID=7351ef5d-fc61-4e47-8d8a-e1c5b697aa91 ro quiet

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[   69.905084] tveeprom 5-0050: decoder processor is CX23888 (idx 34)
[   69.905086] tveeprom 5-0050: has no radio, has IR receiver, has no IR 
transmitter
[   69.905087] cx23885[0]: hauppauge eeprom: model=22111
[   69.908463] cx25840 7-0044: cx23888 A/V decoder found @ 0x88 (cx23885[0])
[   69.915338] cx25840 7-0044: firmware: direct-loading firmware 
v4l-cx23885-avcore-01.fw
[   70.007180] [drm] ring test on 5 succeeded in 1 usecs
[   70.007188] [drm] UVD initialized successfully.
[   70.007391] [drm] ib test on ring 0 succeeded in 0 usecs
[   70.007430] [drm] ib test on ring 3 succeeded in 0 usecs
[   70.177409] [drm] ib test on ring 5 succeeded
[   70.178772] [drm] Radeon Display Connectors
[   70.178777] [drm] Connector 0:
[   70.178780] [drm]   DP-1
[   70.178782] [drm]   HPD4
[   70.178787] [drm]   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 
0x644c
[   70.178789] [drm]   Encoders:
[   70.178791] [drm] DFP1: INTERNAL_UNIPHY2
[   70.178793] [drm] Connector 1:
[   70.178795] [drm]   HDMI-A-1
[   70.178797] [drm]   HPD5
[   70.178801] [drm]   DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 
0x643c
[   70.178802] [drm]   Encoders:
[   70.178804] [drm] DFP2: INTERNAL_UNIPHY2
[   70.178806] [drm] Connector 2:
[   70.178808] [drm]   DVI-I-1
[   70.178810] [drm]   HPD1
[   70.178813] [drm]   DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 
0x646c
[   70.178815] [drm]   Encoders:
[   70.178817] [drm] DFP3: INTERNAL_UNIPHY1
[   70.178819] [drm] CRT2: INTERNAL_KLDSCP_DAC2
[   70.178821] [drm] Connector 3:
[   70.178823] [drm]   DVI-I-2
[   70.178824] [drm]   HPD6
[   70.178827] [drm]   DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 
0x645c
[   70.178829] [drm]   Encoders:
[   70.178831] [drm] DFP4: INTERNAL_UNIPHY
[   70.178833] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[   70.190001] Adding 9920508k swap on /dev/sdb5.  Priority:-1 extents:1 
across:9920508k SSFS
[   70.261914] [drm] fb mappable at 0xC045F000
[   70.261917] [drm] vram apper at 0xC000
[   70.261918] [drm] size 8294400
[   70.261920] [drm] fb depth is 24
[   70.261921] [drm]pitch is 7680
[   70.262240] fbcon: radeondrmfb (fb0) is primary device
[   70.295787] Console: switching to colour frame buffer device 240x67
[   70.23] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   70.23] Bluetooth: BNEP filters: protocol multicast
[   70.28] Bluetooth: BNEP socket layer initialized
[   70.312299] radeon :06:00.0: fb0: radeondrmfb frame buffer device
[   70.339588] [drm] Initialized radeon 2.43.0 20080528 for :06:00.0 on 
minor 0
[   70.541016] vboxdrv: Found 6 processor cores
[   70.551711] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[   70.552517] r8169 :02:00.0: firmware: direct-loading firmware 
rtl_nic/rtl8168f-1.fw
[   70.559552] vboxdrv: TSC mode is Invariant, tentative frequency 3311099466 Hz
[   70.559556] vboxdrv: Successfully loaded version 5.0.20_Debian (interface 
0x0024)
[   70.567516] VBoxNetFlt: Successfully started.
[   70.569740] cx25840 7-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 
bytes)
[   70.573842] VBoxNetAdp: Successfully started.
[   70.580112] VBoxPciLinuxInit
[   70.581621] vboxpci: IOMMU not found (not registered)
[   70.647702] cx23885[0]: registered device video0 [v4l2]
[   70.647741] cx23885[0]: registered device vbi0
[   70.647850] cx23885[0]: registered ALSA audio device
[   70.647852] cx23885_dvb_register() allocating 1 frontend(s)
[   70.647854] cx23885[0]: cx23885 based dvb card
[   70.654160] r8169 :02:00.0 enp2s0: link down
[   70.654229] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[   70.697267] tda18271 6-0060: creating new instance
[   70.699298] TDA18271HD/C2 detected @ 6-0060
[   70.936310] tda18271 6-0060: attaching existing instance
[   70.936326] DVB: registering new adapter (cx23885[0])
[   70.936335] cx23885 :04:00.0: DVB: registering adapter 0 frontend 0 
(Samsung S5H1411 QAM/8VSB Frontend)...
[   70.936841] cx23885_dev_checkrevision() Hardware revision = 0xd0
[   70.936847] 

Bug#823069: RE: Bug#823069: live-boot-initramfs-tools: Kernel panic while booting live with Debian stretch busybox/live packages

[Arjen Balfoort]

That did not change a thing: output the same as in OP.

Arjen


On Mon, 9 May 2016 20:24:12 +0200 Kristian Klausen 
 wrote:

> Arjen could you try removing:
> 
PATH="/root/usr/bin:/root/usr/sbin:/root/bin:/root/sbin:/usr/bin:/usr/sbin:/bin:/sbin"

> export PATH
>
> from /lib/live/boot/9990-aaa-fixme.sh and see if it works?
>
> - Kristian
>
> 
> > Subject: Bug#823069: live-boot-initramfs-tools: Kernel panic while 
booting live with Debian stretch busybox/live packages

> > From: b...@decadent.org.uk
> > To: 823...@bugs.debian.org
> > CC: util-li...@packages.debian.org
> > Date: Mon, 9 May 2016 17:55:55 +0100
> >
> > Control: clone -1 -2
> > Control: reassign -2 util-linux
> > Control: severity -2 important
> > Control: affects -2 live-boot-initramfs-tools
> > Control: retitle -1 live-boot-initramfs-tools: wrongly adds 
directories in /root to the PATH
> > Control: retitle -2 util-linux: 'mount -o move' does not work with 
virtual filesystems

> >
> > On Sat, 30 Apr 2016 16:07:25 +0200 Arjen Balfoort 
 wrote:

> > [...]
> >> mount: /dev is write-protected, mounting read-only
> >> mount: /dev is not a block device
> >>
> >> The error is caused in 
/usr/share/initramfs-tools/scripts/init-bottom/udev

> >> Line: mount -n -o move /dev ${rootmnt}/dev
> > [...]
> >
> > This is a side-effect of my change in busybox 1.22.0-19, but I don't
> > think that change was wrong.
> >
> > live-boot-initramfs-tools adds directories under /root to $PATH, which
> > was formerly harmelss but now actually does result in some commands
> > being loaded from there. You must stop doing this; it is not
> > supportable and I will not support it.
> >
> > In particular, this mount command now invokes util-linux's mount. That
> > refuses to perform a move if the source filesystem was not mounted from
> > a block device. There is no good reason for this and obviously it
> > works with busybox and klibc's implementations of mount.
> >
> > Ben.
> >
> > --
> > Ben Hutchings
> > If you seem to know what you are doing, you'll be given more to do.
>
>

Bug#821665: Bumping severity of PHP 7.0 transition bugs to serious

[Antonio Ospite]

On Thu, 5 May 2016 10:20:58 +0200
Ondřej Surý  wrote:

> Dear maintainer(s),
> 
> I am bumping the severity of this bug to serious, as we are going to
> remove src:php5 from Debian and your package is blocking the first
> step which is removal of php5 from testing.  Please either update your
> package to support PHP 7.0 or remove the package from Debian unstable
> alltogether.
> 

Hi Ondřej,

I will update the package this week.

However my package depends on php-xml-serializer which is going to be
removed from Debian:
https://packages.qa.debian.org/p/php-xml-serializer/news/20160502T014739Z.html

So I think I will have to explore other serializers, like
php-symfony-serializer.

Also, is there any news about bug #818962? My package is going to give
the error as per the bug report.

Thanks,
   Antonio

-- 
Antonio Ospite
http://ao2.it

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

Bug#823813: netbeans: non-DFSG .xsd files (no modification?)

[Markus Koschany]

Am 09.05.2016 um 12:11 schrieb Dmitry Smirnov:
> Source: netbeans
> Version: 8.1+dfsg2-3
> Severity: serious
> Usertags: dfsg
> 
> Files:
> 
> websvc.wsitmodelext/src/org/netbeans/modules/websvc/wsitmodelext/catalog/resources/wsrm-policy-200502.xsd
> 
> websvc.wsitmodelext/src/org/netbeans/modules/websvc/wsitmodelext/catalog/resources/WS-Trust.xsd
> 
> websvc.wsitmodelext/src/org/netbeans/modules/websvc/wsitmodelext/catalog/resources/metadata-exchange.xsd
> 
> websvc.wsitmodelext/src/org/netbeans/modules/websvc/wsitmodelext/catalog/resources/optimizedmimeserialization-policy.xsd
> 
> websvc.wsitmodelext/src/org/netbeans/modules/websvc/wsitmodelext/catalog/resources/ws-policy-10.xsd
> 
> websvc.wsitmodelext/src/org/netbeans/modules/websvc/wsitmodelext/catalog/resources/wsat.xsd
> 
> are licensed under terms allowing only distribution (i.e. "copy and display")
> while explicitly prohibiting everything else:
> 
>"No other rights are granted by implication, estoppel or otherwise."
> 
> I'm particularly concerned about modification rights that appears to be 
> prohibited.
> 
> Please investigate.

Hi,

these are W3C specifications like
https://en.wikipedia.org/wiki/WS-Policy and
https://www.w3.org/TR/ws-metadata-exchange/. Nowadays they are either
licensed under the W3C document license
https://www.w3.org/Consortium/Legal/2015/doc-license or W3C software
license
https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document. The
latter is dfsg-free but the former does not allow modifications of W3C
documents except under the following conditions:

"No right to create modifications or derivatives of W3C documents is
granted pursuant to this license, except as follows: To facilitate
implementation of the technical specifications set forth in this
document, anyone may prepare and distribute derivative works and
portions of this document in software, in supporting materials
accompanying software, and in documentation of software, PROVIDED that
all such works include the notice below. HOWEVER, the publication of
derivative works of this document for use as a technical specification
is expressly prohibited.

In addition, "Code Components" —Web IDL in sections clearly marked as
Web IDL; and W3C-defined markup (HTML, CSS, etc.) and computer
programming language code clearly marked as code examples— are licensed
under the W3C Software License."

I think most people will agree that it makes no sense to modify a
specification because it would be extremely confusing and harmful for
the internet if there was more than one HTML 5 spec for example.

However I don't intend to argue about this matter because the websvc
module is not used by us. I will just remove it from the tarball.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#741204: marked as done (getdp is GPL-licensed, but links with both GPL-licensed and GPL-incompatible libraries)

[Debian Bug Tracking System]

Your message dated Mon, 9 May 2016 22:23:31 +0200
with message-id 

and subject line getdp is GPL-licensed, but links with both GPL-licensed and 
GPL-incompatible libraries
has caused the Debian Bug report #741204,
regarding getdp is GPL-licensed, but links with both GPL-licensed and 
GPL-incompatible libraries
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
741204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: getdp
Version: 2.4.2-1
Severity: serious
Justification: Policy 2.3
User: debian-science-maintain...@lists.alioth.debian.org
Usertags: scotch-license-issues

Hello,
the program /usr/bin/getdp is under the GNU GPL v2 (only? or later?
the debian/copyright is not too clear on this aspect) and links with:

  => libumfpack.so.5.6.2, which is under the GNU GPL v2 or later

  => libcholmod.so.2.1.2, which has parts under the GNU GPL v2 or later

  => libptscotch-5.1.so and libptscotcherr-5.1.so, which are released
 under the GPL-incompatible terms of the CeCILL-C v1.0 license

  => libpetsc.so.3.4.2 and libslepc.so.3.4.2, which, though not being
 under strong copyleft or under copyleft at all, link, in their
 turn, with the above three libraries...

This seems to mean that package getdp includes a file which is
GPL-licensed and links with both GPL-licensed and GPL-incompatible
libraries.

Please refer to the similar bug #740463 for some further details about
the SCOTCH licensing issues.

I think the possible solutions to the issue for getdp are, in
descending order of desirability:

 (A) SCOTCH copyright holders should be contacted and persuaded to
re-license (or dual-license) it under GPLv2-or-later-compatible terms

 (B) SCOTCH should be substituted with a GPLv2-or-later-compatible
replacement, if any is available (METIS seems to be at least
GPLv3-or-later-compatible, see https://bugs.debian.org/740463#15 )

 (C) GPL-licensed library (such as UMFPACK and CHOLMOD) copyright
holders, as well as GetDP copyright holders, should be asked to relax
the copyleft (for instance by switching to the LGPL v2.1) or add
license exceptions that give permission to link their works with
code released under CeCILL-C v1.0


As mentioned in previous bug reports, the best solution is (A):
I therefore renew my call for help to push in the direction of
{re|dual}-licensing SCOTCH under the GNU LGPL v2.1:
please see https://bugs.debian.org/740463#5 for the details.

Thanks for your time!
--- End Message ---
--- Begin Message ---
Package: getdp
Version: 2.7.0-1

It seems this bug should have been closed in getdp 2.7.0-1 when
lib[scotch]metis was removed from build dependencies.

  [ Christophe Trophime ]
  * debian/control:
+ remove lib[scotch]metis, gmsh[-tetgen], libgmsh[-tetgen]-dev,
  libhdf5-mpi-dev from Build-Depends.  Closes: #755973--- End Message ---

Bug#823711: cpputest: non-free files

[Raphael Hertzog]

Control: forwarded -1 https://github.com/cpputest/cpputest/issues/961

On Sun, 08 May 2016, Dmitry Smirnov wrote:
>  This software may only be used under the terms of a valid, current,
>  end user licence from KEIL for a compatible version of KEIL software
>  development tools. Nothing else gives you the right to use this software.

Thanks for this report. I forwarded this to the upstream developers.

I think that I will just exclude all the platforms_* directories
in my next upload.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Processed: Re: Bug#823711: cpputest: non-free files

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/cpputest/cpputest/issues/961
Bug #823711 [src:cpputest] cpputest: non-free files
Set Bug forwarded-to-address to 
'https://github.com/cpputest/cpputest/issues/961'.

-- 
823711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fixed 823830 in 1:2.1+dfsg-12+deb8u6

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 823830 1:2.1+dfsg-12+deb8u6
Bug #823830 [src:qemu] qemu: CVE-2016-3710 CVE-2016-3712
The source 'qemu' and version '1:2.1+dfsg-12+deb8u6' do not appear to match any 
binary packages
Marked as fixed in versions qemu/1:2.1+dfsg-12+deb8u6.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 808004

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 808004 libdiet-admin2.8 libdiet-sed2.8
Bug #808004 [libdiet-client2.8] libdiet-client2.8: not installable on sid
Added indication that 808004 affects libdiet-admin2.8 and libdiet-sed2.8
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
808004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#823748: tar: illegal hardware instruction breaks apt-get upgrade

[Diego Gomez]

Like Lee, me neither can reproduce it on my AMD Athlon(tm) II X4 640 processor.
I think it is safe to upgrade.

Regards.

--
Diego.-

Bug#820824: libapache2-mod-perl2: FTBFS: t/protocol/pseudo_http.t failure

[Niko Tyni]

On Thu, Apr 14, 2016 at 07:48:47AM +0200, Stefan Fritsch wrote:
> reassign 820824 apache2

> On Tuesday 12 April 2016 23:04:42, Niko Tyni wrote:
> > Looking at the CI results at
> >  
> > https://ci.debian.net/packages/liba/libapache2-mod-perl2/unstable/a
> > md64/ this started happening between 2016-04-09 and 2016-04-10,
> > probably with the apache2 2.4.18 -> 2.4.20 upgrade.
> > 
> > I can get this to happen with just
> > # ./t/TEST -verbose -httpd_conf $(pwd)/debian/apache2.conf
> > t/protocol/pseudo_http.t
> > 
> > and I see the Apache server process dies with SIGSEGV. Backtrace
> > below.
> > 
> > Cc'ing the Apache maintainers, seems to be a regression there?
> 
> Seems likely. Reassigning to keep 2.4.20-1 from migrating to testing 
> for now.

This is also

 
https://mail-archives.apache.org/mod_mbox/httpd-dev/201604.mbox/%3CCACsi250G0azcA-XyJHGLxacpDEg_ezJ=taus31pyb7g_8-x...@mail.gmail.com%3E

which says that while apache2 shouldn't crash, the mod_perl2 test is
buggy and should be fixed. Unfortunately mod_perl2 upstream is very
quiet these days, so nothing has happened so far on this front.

I intend to disable the test in libapache2-mod-perl2 for now until
a better solution is found.  Do you want to track the apache2 crash
with this bug, or should we reassign it back?

Thanks,
-- 
Niko Tyni   nt...@debian.org

Processed: tagging 821469

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 821469 + pending
Bug #821469 [acidbase] acidbase: PHP 7.0 Transition
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
821469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#823865: d/copyright is missing licenses for many files

[Ondřej Surý]

Package: phpsysinfo
Version: 3.2.1-1
Severity: serious

Dear maintainer,

d/copyright doesn't list all license holders and has wrong copyright
for at least some files:

Please convert to machine-readable copyright file and add missing copyrights:
 + Files: * is GPLv2+, e.g. any later version and not just GPL-2
 + Files: debian/* copyright is missing (is that also GPL-2), could you try 
contacting previous maintainers and make this clear?
 + Files: js/jQuery/* licenses are missing
 + Files: js/vendor/* licenses are missing
 + Files: templates/plugin/* licenses are missing, see the originals 
https://github.com/ludo/jquery-treetable/tree/master/css
 + Files: templates/vendor/* licenses are missing

Then there's a lot of pictures in gfx/, could you please contact
upstream and clarify the licenses for the images there?  At least
gfx/images/ looks suspicious, but there are lot of other images all
around.

The rest look okay(ish), but double check it anyway please.

Cheers,
Ondrej

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

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

Bug#821674: marked as done (src:drush: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 18:21:46 +
with message-id 
and subject line Bug#823767: Removed package(s) from unstable
has caused the Debian Bug report #821674,
regarding src:drush: PHP 7.0 Transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
821674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:drush
Version: 5.10.0-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 drush 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: drush -- 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

iQJ8BAEBCgBmBQJXFUtbXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHtekP/3gJjQOZUtvjNuqlv9/qfd3Z
fdcPSezsoeeHJXsmye0oxI9fNA+1n8/6in7STCglwp/hE/M0IXtOSb02PW33KQuv
cylZYoYTurt4KHrMKWgbUzuL/JIOJSRIYlICeFW2gFHBb9XKg5TqFtCwC1clz/8d
v7Vy+Gh6xHxQSc/LsEW+O3dDPiC8IX6F3XHQ+FyDlzRp2esW+elDCEZ8QlwIe1l6
CgWxvPX2s7bhLHhurZOxS8XVM8KSYbRtCQOWzRQsXy7NXpsuOC7rxkY/UX+bfUz3

Bug#821611: marked as done (phpreports: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 18:24:21 +
with message-id 
and subject line Bug#823836: Removed package(s) from unstable
has caused the Debian Bug report #821611,
regarding phpreports: PHP 7.0 Transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
821611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpreports
Version: 0.5.0-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 phpreports package currently depends on php5 php5-xsl .

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: phpreports -- 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

iQJ8BAEBCgBmBQJXFUq9XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHkiEQAJz1Ik/+/pOqDSGDnJVzbqrc
WVsIl7qqKtONf1Y5orq/3AQWbHV1ME5v38bMdsyVarqhN5Wp+B2RVTmjDntBU//y
jcgY8KU+kQLHMCnhV8jW684hPPKYvX1gpGGO6dCwFfoIp1f/XUGpS3NMlDsiA+lW
Ukpf6EGqifyZWGCo7AN5iuJb7Gj4mkRw2bVgEaBJNo/1gh9qN7LnsXrjZo1uOZ2Z
OMuozVhz4u88c8EHrmgaNnvwIwfCB5uSTQPEm3tMuAA/J6nq1NcP/W4zWXMGN3At

Bug#821483: marked as done (drush: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 18:21:46 +
with message-id 
and subject line Bug#823767: Removed package(s) from unstable
has caused the Debian Bug report #821483,
regarding drush: PHP 7.0 Transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
821483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drush
Version: 5.10.0-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 drush package currently 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: drush -- 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

iQJ8BAEBCgBmBQJXFUpeXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHeaEP/R0fQsNEUw3KV8wIf3EIaPAG
+CxdHwYwlCqtKZTl+G5+geBb5MRoqN2eYncg8HzPV4hOWdZCbnrraWL+syUoyqWG
a+tx8nsitLASTLTtv8A1iyAUAIoo0lK9eAG3RW1ueYZr65jhqYVwV+7moWePcRYy
LbkY1j92G5+l7U5fKA8hnxljEj+b9oHhe7jjvfvkAmL/YMkODPktw8Fmj3wAQtnf
YkHPQ+4EhHlxyoLu1Yw/z9kpCyfxNTnZCjBq3AbInBb07Hf8GGR2sn56s1iY4AA9

Bug#823069: live-boot-initramfs-tools: Kernel panic while booting live with Debian stretch busybox/live packages

[Kristian Klausen]

Arjen could you try removing:
PATH="/root/usr/bin:/root/usr/sbin:/root/bin:/root/sbin:/usr/bin:/usr/sbin:/bin:/sbin"
export PATH

from /lib/live/boot/9990-aaa-fixme.sh and see if it works?

- Kristian


> Subject: Bug#823069: live-boot-initramfs-tools: Kernel panic while booting 
> live with Debian stretch busybox/live packages
> From: b...@decadent.org.uk
> To: 823...@bugs.debian.org
> CC: util-li...@packages.debian.org
> Date: Mon, 9 May 2016 17:55:55 +0100
>
> Control: clone -1 -2
> Control: reassign -2 util-linux
> Control: severity -2 important
> Control: affects -2 live-boot-initramfs-tools
> Control: retitle -1 live-boot-initramfs-tools: wrongly adds directories in 
> /root to the PATH
> Control: retitle -2 util-linux: 'mount -o move' does not work with virtual 
> filesystems
>
> On Sat, 30 Apr 2016 16:07:25 +0200 Arjen Balfoort  
> wrote:
> [...]
>>  mount: /dev is write-protected, mounting read-only
>>  mount: /dev is not a block device
>>
>>  The error is caused in 
>> /usr/share/initramfs-tools/scripts/init-bottom/udev
>>  Line: mount -n -o move /dev ${rootmnt}/dev
> [...]
>
> This is a side-effect of my change in busybox 1.22.0-19, but I don't
> think that change was wrong.
>
> live-boot-initramfs-tools adds directories under /root to $PATH, which
> was formerly harmelss but now actually does result in some commands
> being loaded from there.  You must stop doing this; it is not
> supportable and I will not support it.
>
> In particular, this mount command now invokes util-linux's mount.  That
> refuses to perform a move if the source filesystem was not mounted from
> a block device.  There is no good reason for this and obviously it
> works with busybox and klibc's implementations of mount.
>
> Ben.
>
> --
> Ben Hutchings
> If you seem to know what you are doing, you'll be given more to do.
  

Bug#823495: marked as done (RM: php5-vtkgdcm -- ROM;doesn't support PHP7.0)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 14:15:10 -0400
with message-id <1607370.QtYsOmeHzU@kitterma-e6430>
and subject line Already removed from unstable
has caused the Debian Bug report #823495,
regarding RM: php5-vtkgdcm -- ROM;doesn't support PHP7.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
823495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gdcm
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 gdcm 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: gdcm -- 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

iQJ8BAEBCgBmBQJXFUtcXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHhD8QAJT85YMyKeUenoVIHm1uVLNS
Ry2TGhgfVpsKl259LZRayiCTnrgEqoMjhwEJjKdxjLFBltuUpynalUSEaaylJnd1
Si7C801pzoM6miJ//N76P3Ef19/92CXi8MWD1aFro3DczXIItOnA/oIDeHREzSkc
khlq+DPIbFTB6HlB1b/wCQqYtk2B/2atGhKBjh9XNnh12h3bnCriRC5f+UEFKEP3
/qQZR9KG1WNTzo0sKewpzljdj6LSa5EjQr0ggSypRh/xvYgAu71UDSh5oFWwZYWm

Bug#823103: marked as done (dsbltesters: (Build-)Depends: firestring which has been requested to be removed)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 18:12:49 +
with message-id 
and subject line Bug#823363: Removed package(s) from unstable
has caused the Debian Bug report #823103,
regarding dsbltesters: (Build-)Depends: firestring which has been requested to 
be removed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
823103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dsbltesters
Version: 0.9.5-4
Severity: serious
Tags: sid
Control: block 811358 with -1

Hi,

dsbltesters Build-Depends and Depends on firedns which has been
requested to be removed. (#811358)
Should dsbltesters be removed as well?


Andreas
--- End Message ---
--- Begin Message ---
Version: 0.9.5-4+rm

Dear submitter,

as the package dsbltesters has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/823363

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#776250: marked as done (Should not be part of jessie)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 18:11:37 +
with message-id 
and subject line Bug#823361: Removed package(s) from unstable
has caused the Debian Bug report #776250,
regarding Should not be part of jessie
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
776250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: compiz-fusion-bcop
Version: 0.8.4-1.1
Severity: serious

compiz has been removed from the Debian archive a while ago.
Releasing this package with jessie is therefor rather pointless.

Eventually, compiz-fusion-bcop should be removed completely from the
archive, for now, let's just remove it from testing and make sure it
doesn't migrate again.


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

Kernel: Linux 3.16.0-4-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)
--- End Message ---
--- Begin Message ---
Version: 0.8.4-1.1+rm

Dear submitter,

as the package compiz-fusion-bcop has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/823361

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#771503: marked as done (Remove package web2ldap)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 18:07:06 +
with message-id 
and subject line Bug#823181: Removed package(s) from unstable
has caused the Debian Bug report #771503,
regarding Remove package web2ldap
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
771503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: web2ldap
Version: 1.1.43~dfsg-1

https://tracker.debian.org/pkg/web2ldap

I understand that it's much work to maintain such a package and that Debian
maintainers sometimes cannot keep up with development.

But for me as upstream author it seems better not to have a Debian package at
all than having to deal with an outdated package which contains bugs already
fixed long ago.

=> Please remove package web2ldap because it's outdated and seems unmaintained.

Ciao, Michael.




smime.p7s
Description: S/MIME Cryptographic Signature
--- End Message ---
--- Begin Message ---
Version: 1.1.43~dfsg-1+rm

Dear submitter,

as the package web2ldap has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/823181

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: retitle 823863 to xerces-c: CVE-2016-2099: use-after-free

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 823863 xerces-c: CVE-2016-2099: use-after-free
Bug #823863 [src:xerces-c] xerces-c: CVE-2016-2099: upse-after-free
Changed Bug title to 'xerces-c: CVE-2016-2099: use-after-free' from 'xerces-c: 
CVE-2016-2099: upse-after-free'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#799195: marked as done (python-scientific: FTBFS during rebuild against netcdf 4.4.0)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 18:00:00 +
with message-id 
and subject line Bug#821221: Removed package(s) from unstable
has caused the Debian Bug report #799195,
regarding python-scientific: FTBFS during rebuild against netcdf 4.4.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
799195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-scientific
Version: 2.9.4-3
Severity: serious

Hi

The python-scientific package FTBFS during a rebuild against netcdf
4.4.0 (a transition).  Though I cannot tell if the issue is directly
related to netcdf or some other change in unstable since the upload.

The relevant part of the log appears to be:

"""
changing mode of build/scripts-2.7/task_manager from 664 to 775
changing mode of build/scripts-2.7/bsp_virtual from 664 to 775
rm -f Src/MPI/*.o
cd Src/MPI && PYTHONPATH=$(echo /«PKGBUILDDIR»/build/lib.*-2.7) USE_MPICH=yes   
/usr/bin/python  compile.py
Traceback (most recent call last):
  File "compile.py", line 8, in 
from Scientific import N
  File "/«PKGBUILDDIR»/build/lib.linux-x86_64-2.7/Scientific/N.py", line 6, in 

from numpy.oldnumeric import *
ImportError: No module named oldnumeric
make[1]: *** [override_dh_auto_build] Error 1
debian/rules:27: recipe for target 'override_dh_auto_build' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
"""

The issue affected all builds of the package except powerpc (no clue
why powerpc got free of it).  Anyway, a timely fix would be
appreciated so we can finish the netcdf transition without having to
remove python-scientific from testing.

Thanks,
~Niels
--- End Message ---
--- Begin Message ---
Version: 2.9.4-3+rm

Dear submitter,

as the package python-scientific has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/821221

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#823863: xerces-c: CVE-2016-2099: upse-after-free

[Salvatore Bonaccorso]

Source: xerces-c
Version: 3.1.1-1
Severity: grave
Tags: security upstream patch
Forwarded: https://issues.apache.org/jira/browse/XERCESC-2066

Hi,

the following vulnerability was published for xerces-c.

CVE-2016-2099[0]:
use-after-free

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-2099
[1] https://issues.apache.org/jira/browse/XERCESC-2066

Regards,
Salvatore

Bug#823563: marked as done (debian-security-support: fails to remove: update-alternatives: error: no alternatives for security-support-ended)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 17:34:37 +
with message-id 
and subject line Bug#823563: fixed in debian-security-support 2016.05.09+nmu1
has caused the Debian Bug report #823563,
regarding debian-security-support: fails to remove: update-alternatives: error: 
no alternatives for security-support-ended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
823563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-security-support
Version: 2016.05.04+nmu1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to remove.

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

0m29.7s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpxDZO77', 
'apt-get', 'remove', 'gettext-base', 'debian-security-support']
0m31.1s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages will be REMOVED:
debian-security-support gettext-base
  0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
  After this operation, 854 kB disk space will be freed.
  (Reading database ... 
(Reading database ... 7462 files and directories currently installed.)
  Removing debian-security-support (2016.05.04+nmu1) ...
  update-alternatives: error: no alternatives for security-support-ended
  dpkg: error processing package debian-security-support (--remove):
   subprocess installed pre-removal script returned error exit status 2
  dpkg: gettext-base: dependency problems, but removing anyway as you requested:
   debian-security-support depends on gettext-base.
  
  Removing gettext-base (0.19.7-2) ...
  /usr/bin/check-support-status: 8: .: gettext.sh: not found
  dpkg: error: error executing hook 'if [ -x 
/usr/share/debian-security-support/check-support-status.hook ] ; then 
/usr/share/debian-security-support/check-support-status.hook ; fi', exit code 
512
  E: Sub-process /usr/bin/dpkg returned an error code (2)
0m31.1s DEBUG: Command failed (status=100), but ignoring error: ['chroot', 
'/tmp/piupartss/tmpxDZO77', 'apt-get', 'remove', 'gettext-base', 
'debian-security-support']

cheers,

Andreas


debian-security-support_2016.05.04+nmu1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: debian-security-support
Source-Version: 2016.05.09+nmu1

We believe that the bug you reported is fixed in the latest version of
debian-security-support, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 823...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Ruano Rincón  (supplier of updated 
debian-security-support package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 May 2016 11:24:37 +0200
Source: debian-security-support
Binary: debian-security-support
Architecture: source
Version: 2016.05.09+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl 
Changed-By: Santiago Ruano Rincón 
Description:
 debian-security-support - Debian security support coverage checker
Closes: 823563
Changes:
 debian-security-support (2016.05.09+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove postrm file, accidentally included in the previous release
 (Closes: #823563)
Checksums-Sha1:
 bccb69fc340e42537780a7ed34c54472fd5b05d2 1865 
debian-security-support_2016.05.09+nmu1.dsc
 46a58e4e9b86a6256f59d9c40311af1f766a026e 23512 
debian-security-support_2016.05.09+nmu1.tar.xz
Checksums-Sha256:
 273ac591f6c0e9ab744ef364fb662a2872f0db9d03584ddbe7f13441abf2fd4a 1865 
debian-security-support_2016.05.09+nmu1.dsc
 8f1d76e06459ed077378828184ff59007abba570810ac467bde62059d212c982 23512 
debian-security-support_2016.05.09+nmu1.tar.xz
Files:
 fff80fec2300ff38edcb94b06788b2a5 1865 admin optional 
debian-security-support_2016.05.09+nmu1.dsc
 8159cce9918c9b9bfe8bdd194d0a9947 23512 admin optional 
debian-security-support_2016.05.09+nmu1.tar.xz

-BEGIN PGP 

Bug#822071: maildrop: Upgrade from courier-maildrop: Default delivery location changed from Maildirs $/HOME/Maildir to /var/mail/$USER

[Marcus Wolschon]

a)
0.75.0-20 doesn't fix ANYTHING.
It just adds a cryptic note to a NEWS file burried in /usr/share/doc .
The existing /etc/courier/maildroprc rule file is not moved (is
conversion needed?)
to /etc/maildroprc .


b)
How shall admins affected by this handle the tons of email that ended up
in /var/spool/mail/
to get it delivered using the fixed maildrop rules?
courier has no command do read mailspool files and pipe them through the
delivery
pipeline.

Processed: Re: Bug#821234: twinkle: FTBFS: error: 'ucommon::Digest::Digest(const ucommon::Digest&)' is private

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 821234 fixed-upstream pending
Bug #821234 [src:twinkle] twinkle: FTBFS: error: 'ucommon::Digest::Digest(const 
ucommon::Digest&)' is private
Added tag(s) fixed-upstream and pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
821234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Reassigning for removal

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #823848 [btrfs-progs] remove btrfs-tools-udev from archive
Bug reassigned from package 'btrfs-progs' to 'ftp.debian.org'.
No longer marked as found in versions btrfs-progs/4.4.1-1.1.
Ignoring request to alter fixed versions of bug #823848 to the same values 
previously set
> retitle -1 RM: btrfs-tools-udeb: ROQA, NBS, replaced by btrfs-progs-udeb
Bug #823848 [ftp.debian.org] remove btrfs-tools-udev from archive
Changed Bug title to 'RM: btrfs-tools-udeb: ROQA, NBS, replaced by 
btrfs-progs-udeb' from 'remove btrfs-tools-udev from archive'.
> severity -1 normal
Bug #823848 [ftp.debian.org] RM: btrfs-tools-udeb: ROQA, NBS, replaced by 
btrfs-progs-udeb
Severity set to 'normal' from 'serious'

-- 
823848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: live-boot-initramfs-tools: Kernel panic while booting live with Debian stretch busybox/live packages

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #823069 [live-boot-initramfs-tools] live-boot-initramfs-tools: Kernel panic 
while booting live with Debian stretch busybox/live packages
Bug 823069 cloned as bug 823856
> reassign -2 util-linux
Bug #823856 [live-boot-initramfs-tools] live-boot-initramfs-tools: Kernel panic 
while booting live with Debian stretch busybox/live packages
Bug reassigned from package 'live-boot-initramfs-tools' to 'util-linux'.
No longer marked as found in versions live-boot/1:20151213.
Ignoring request to alter fixed versions of bug #823856 to the same values 
previously set
> severity -2 important
Bug #823856 [util-linux] live-boot-initramfs-tools: Kernel panic while booting 
live with Debian stretch busybox/live packages
Severity set to 'important' from 'critical'
> affects -2 live-boot-initramfs-tools
Bug #823856 [util-linux] live-boot-initramfs-tools: Kernel panic while booting 
live with Debian stretch busybox/live packages
Added indication that 823856 affects live-boot-initramfs-tools
> retitle -1 live-boot-initramfs-tools: wrongly adds directories in /root to 
> the PATH
Bug #823069 [live-boot-initramfs-tools] live-boot-initramfs-tools: Kernel panic 
while booting live with Debian stretch busybox/live packages
Changed Bug title to 'live-boot-initramfs-tools: wrongly adds directories in 
/root to the PATH' from 'live-boot-initramfs-tools: Kernel panic while booting 
live with Debian stretch busybox/live packages'.
> retitle -2 util-linux: 'mount -o move' does not work with virtual filesystems
Bug #823856 [util-linux] live-boot-initramfs-tools: Kernel panic while booting 
live with Debian stretch busybox/live packages
Changed Bug title to 'util-linux: 'mount -o move' does not work with virtual 
filesystems' from 'live-boot-initramfs-tools: Kernel panic while booting live 
with Debian stretch busybox/live packages'.

-- 
823069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823069
823856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#823848: Reassigning for removal

[Gianfranco Costamagna]

control: reassign -1 ftp.debian.org
control: retitle -1 RM: btrfs-tools-udeb: ROQA, NBS, replaced by 
btrfs-progs-udeb
control: severity -1 normal


Hi, reassignign this bug to ftpmasters, that btrfs-tools-udeb can considered an 
old cruft.
There shouldn't be reverse-dependencies in unstable anymore for that udeb.

thanks,
Gianfranco
(please note: this is my first udeb removal request, sorry in advance if I 
didn't follow
the right procedure)

Processed (with 2 errors): Re: python3-gear: depends on python3.4

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 nmu: python-gear_0.5.8-2
Bug #822098 [python3-gear] python3-gear: depends on python3.4
Changed Bug title to 'nmu: python-gear_0.5.8-2' from 'python3-gear: depends on 
python3.4'.
> reassign -1 release.debian.org
Bug #822098 [python3-gear] nmu: python-gear_0.5.8-2
Bug reassigned from package 'python3-gear' to 'release.debian.org'.
No longer marked as found in versions python-gear/0.5.8-2.
Ignoring request to alter fixed versions of bug #822098 to the same values 
previously set
> severity -1 normal
Bug #822098 [release.debian.org] nmu: python-gear_0.5.8-2
Severity set to 'normal' from 'serious'
> user release.debian@packages.debian.org
Unknown command or malformed arguments to command.

> usertag -1 binnmu
Unknown command or malformed arguments to command.


-- 
822098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#821234: twinkle: FTBFS: error: 'ucommon::Digest::Digest(const ucommon::Digest&)' is private

[Peter Colberg]

Hi Chris, Logan,

On Sat, Apr 16, 2016 at 11:24:16PM +0100, Chris Lamb wrote:
> twinkle fails to build from source in unstable/amd64:

Thank you for reporting the FTBFS and pointing to the upstream fix.

I am still hoping that the upstream maintainer of twinkle will tag
a new release soon, which further fixes compatibility with Qt 5.6:

https://github.com/LubosD/twinkle/issues/64

Regards,
Peter

Bug#823069: live-boot-initramfs-tools: Kernel panic while booting live with Debian stretch busybox/live packages

[Ben Hutchings]

Control: clone -1 -2
Control: reassign -2 util-linux
Control: severity -2 important
Control: affects -2 live-boot-initramfs-tools
Control: retitle -1 live-boot-initramfs-tools: wrongly adds directories in 
/root to the PATH
Control: retitle -2 util-linux: 'mount -o move' does not work with virtual 
filesystems

On Sat, 30 Apr 2016 16:07:25 +0200 Arjen Balfoort  
wrote:
[...]
>  mount: /dev is write-protected, mounting read-only
>  mount: /dev is not a block device
> 
>  The error is caused in 
>/usr/share/initramfs-tools/scripts/init-bottom/udev
>  Line: mount -n -o move /dev ${rootmnt}/dev
[...]

This is a side-effect of my change in busybox 1.22.0-19, but I don't
think that change was wrong.

live-boot-initramfs-tools adds directories under /root to $PATH, which
was formerly harmelss but now actually does result in some commands
being loaded from there.  You must stop doing this; it is not
supportable and I will not support it.

In particular, this mount command now invokes util-linux's mount.  That
refuses to perform a move if the source filesystem was not mounted from
a block device.  There is no good reason for this and obviously it
works with busybox and klibc's implementations of mount.

Ben.
 
-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.

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

Bug#821482: marked as done (drupal7: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 16:52:27 +
with message-id 
and subject line Bug#821482: fixed in drupal7 7.43-2
has caused the Debian Bug report #821482,
regarding drupal7: PHP 7.0 Transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
821482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drupal7
Version: 7.43-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 drupal7 package currently depends on php5 php5-gd php5-mysql
php5-pgsql php5-sqlite .

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: drupal7 -- 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

iQJ8BAEBCgBmBQJXFUpeXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHu/wP/32/P34rNpVE4Ogj2YszeWbm
ZayGbAmR7wvqEJlXa0ZaPoWG0YgyF1d6Yb55d/wwaJD7789xkBoGF0G9fb+xdToi
sY3wNMmk/xIVw8rwxSI3bcxu+MsTdJeWd9mxN+V9pNhuk8ca6MDpX0gL68rnI5SG
4c/lUunCJxpd6MOOpcp//va/WgTYRiAJwzKmMlp0DuVzF2RtlWZXp/bkqsFc2aKV
XN9TdjUtpBBfMDdebGYLWpJixPHK5XXGHK6uxjJqjCCFu3V5yTluo58WX6WGjPTZ

Bug#822098: python3-gear: depends on python3.4

[Jean-Michel Vourgère]

Control: retitle -1 nmu: python-gear_0.5.8-2
Control: reassign -1 release.debian.org
Control: severity -1 normal
Control: user release.debian@packages.debian.org
Control: usertag -1 binnmu

On April 21st, Julien Cristau wrote:
> python3-gear depends on python3.4 which is replaced by python3.5.
> Your package needs to be rebuilt to lose that dependency.

I build tested on sid and saw no issue. This is a simple binnmu matter,
as far as I can tell. Reassigning to release team.

nmu python-gear_0.5.8-2 . ALL . -m "rebuild with python3.4 gone"

Bug#823572: marked as done (sympow: copyright file missing after upgrade (policy 12.5))

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 16:33:19 +
with message-id 
and subject line Bug#823572: fixed in sympow 1.023-7
has caused the Debian Bug report #823572,
regarding sympow: copyright file missing after upgrade (policy 12.5)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
823572: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sympow
Version: 1.023-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  stretch -> sid

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

0m53.0s ERROR: WARN: Inadequate results from running adequate!
  sympow: missing-copyright-file /usr/share/doc/sympow/copyright
  
  MISSING COPYRIGHT FILE: /usr/share/doc/sympow/copyright
  # ls -lad /usr/share/doc/sympow
  drwxr-xr-x 2 root root 40 May  3 11:18 /usr/share/doc/sympow
  # ls -la /usr/share/doc/sympow/
  total 0
  drwxr-xr-x   2 root root   40 May  3 11:18 .
  drwxr-xr-x 108 root root 2280 May  3 11:18 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


sympow_1.023-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sympow
Source-Version: 1.023-7

We believe that the bug you reported is fixed in the latest version of
sympow, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 823...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated sympow package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 May 2016 23:48:21 +
Source: sympow
Binary: sympow sympow-data
Architecture: source
Version: 1.023-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jerome Benoit 
Description:
 sympow - mathematical program for SYMmetric POWer elliptic curve L-functio
 sympow-data - mathematical program for SYMmetric POWer elliptic curve L-functio
Closes: 823572
Changes:
 sympow (1.023-7) unstable; urgency=medium
 .
   * Serious bug fix version (Closes: #823572), thanks to Andreas Beckmann
  for reporting the installation issue.
   * Debianization:
 - debian/control:
   - missing 'Pre-Depends: ${misc:Pre-Depends}', fix;
 - reproducible build, re-attempt.
Checksums-Sha1:
 8d3eea32454c9ed47578ea6141b688a751cc 2072 sympow_1.023-7.dsc
 86d574a3818020dd3fa1521133b3ad0f7ff02efa 27288 sympow_1.023-7.debian.tar.xz
Checksums-Sha256:
 26783eac97b83f090c181992fbf18c88a857e3c3243e43c742e0900fb65c8944 2072 
sympow_1.023-7.dsc
 79a69ad46a6d6463baa69223cc16dcb5e667802a91233ea278de0054e38e6da0 27288 
sympow_1.023-7.debian.tar.xz
Files:
 08801105ea32a09cbd15198213bb5154 2072 math optional sympow_1.023-7.dsc
 fae55f422b6e752ed0e8f1652fe3ec4f 27288 math optional 
sympow_1.023-7.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXMJWXAAoJEPNPCXROn13ZWeMQAJfG9I+6lG+4im/gnHq6ibzk
sTd2Fb7ljgNqEqQtTEOqH2hmkdbcT1+/FBJTy9CmVtDQ9DWSXD3ixje55s9gITni

Processed: Issue is known upstream

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 823164 https://github.com/pavouk/lgi/issues/132
Bug #823164 [src:lua-lgi] lua-lgi: FTBFS: Segmentation fault (core dumped)
Set Bug forwarded-to-address to 'https://github.com/pavouk/lgi/issues/132'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[Bernard Normier]

Ondřej, Chris,

Thank you for reaching out to us. We would indeed like to maintain or help
maintain the zeroc-ice packages in Debian; Jose (j...@zeroc.com, cc'ed)
could become co-maintainer.

We had a long discussion with Cleto in 2014 about Ice 3.6 packaging in
Debian, as we hoped to synchronize our packaging. This resulted in various
changes to our deb packages... but this was not incorporated into Debian
jessie or stretch yet, which still uses Ice 3.5. I think both Cleto and Paco
are now busy with other projects and can't devote much time to Ice
packaging.

For this immediate issue - PHP 7 support in stretch - I suggest we do the
following:
(a) add PHP 7 support to our 3.6 branch
(b) add Ice 3.6.2+ (and later 3.6.3) packages to stretch with PHP 7 support

We'll need some help/reviewing for (b), since our packaging is quite
different (and I'd argue much better) than the Debian Ice 3.5 packaging.

Cheers,
Bernard
-- 
Bernard Normier
ZeroC, Inc.
https://zeroc.com

-Original Message-
From: supp...@zeroc.com [mailto:supp...@zeroc.com] On Behalf Of Ondrej Surý
Sent: Monday, May 09, 2016 7:53 AM
To: Chris Knadle 
Cc: 821...@bugs.debian.org; 821...@bugs.debian.org; supp...@zeroc.com; Cleto
Martín ; p...@debian.org
Subject: Re: src:zeroc-ice: PHP 7.0 Transition

Chris,

I would say go ahead unless Cleto (who was the last person who cared about
zeroc-ice in 2014) or Francisco (who is still listed as maintainer even
though he last touched the package in 2012) violenty object.

I am also Ccing ZeroC, Inc. folks, as they might be interested in properly
maintaining zeroc-ice in Debian. I am quite sure that there will be always
somebody (me, you...) willing to review the packaging and sponsor the upload
to Debian if they do the heavy lifting.

Cheers,
--
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

On Mon, May 9, 2016, at 13:36, Chris Knadle wrote:
> Ondřej Surý:
> > Hi Chris,
> >
> > thanks for taking care of this.
> >
> > You can either try to backport PHP portion of 3.7.0-alpha0 to
> > 3.6.2[*], or check with upstream if they can finish 3.7.0 before
> > stretch freeze and if they can make it package 3.7.0-alpha0 right away.
> >
> > * - or ask upstream to include this update in 3.6.X
>
> The reason I'm involved here is that mumble depends on zeroc-ice and
> is going to removed with it if this bug isn't handled.
>
> I looked at a 'diff -U 1' (1 line of context) of the PHP code between
> 3.5.1
> and 3.7.0-alpha0 and it's ~10k lines; this is not something that would
> be reasonable as a patch in an NMU.  I don't think uploading a new
> version of the software as an NMU is in this case either -- someone
> would have to be familiar with using the software before they'd be
> comfortable sponsoring an NMU upload and this is a package with niche
> use.
>
> Instead the best plan I know of at the moment is removing any PHP
> dependencies from the package for now -- meaning commenting out
> php5-dev
> +
> php-zeroc-ice dependencies and the entire php-zeroc-ice section in
> debian/control and not shipping the php-zeroc-ice binary package for now.
> There are no packages that depend on php-zeroc-ice in Debian, so this
> shouldn't cause any known breakage.  It's not normally what I'd do but
> I don't see a better option.
>
> A debdiff of this is attached.
>
>-- Chris
>
> --
> Chris Knadle
> chris.kna...@coredump.us
> Email had 2 attachments:
> + zeroc-ice_3.5.1-6.5.debdiff
>   8k (text/plain)
> + signature.asc
>   1k (application/pgp-signature)

Bug#823069: Bug#823323: busybox: Side effect after disabling CONFIG_FEATURE_PREFER_APPLETS

[Arjen Balfoort]

On Sun, 08 May 2016 22:13:13 +0100 Ben Hutchings  
wrote:

> On Sun, 2016-05-08 at 14:27 +0800, Steven Shiau wrote:
> > On 2016年05月05日 08:47, Ben Hutchings wrote:
> > >
> > > >
> > > > Since initramfs-tools only allows hook A to declare a 
dependency on >

> > (must run after) hook B, not to declare that it must run before hook B,
> > >
> > > this has to be solved in klibc. > > Ben.
> > [...]
> >
> > Thanks, and this bug report seems to be related:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823069
>
> I don't think so. Â The error messages exist in busybox mount, but not
> klibc mount. Â It looks more like ${rootmnt} is not being set.


I can confirm that upgrading libklibc (and klibc-utils) to version 
2.0.4-9 did not solve this issue.



>
> Ben.
>
> --
> Ben Hutchings
> I haven't lost my mind; it's backed up on tape somewhere.

Bug#823848: remove btrfs-tools-udev from archive

[Nicholas D Steeves]

Package: btrfs-progs
Version: 4.4.1-1.1
Severity: serious

To conclude the btrfs-tools to btrfs-progs rename, ftpmasters need to
be contacted to remove btrfs-tools-udev from the archive for unstable
and testing.  When I discussed the rename with the D-I team, they said
a btrfs-tools-udev dummy package was not useful.  Debian-cd and
partman-btrfs in testing and unstable will not break when
btrfs-tools-udev is removed, because they've been patched to use
btrfs-progs-udev.

I've tagged this bug as serious, because
https://wiki.debian.org/ftpmaster_Removals states "file the bug as an
RC bug on the package first, indicating why you think the package
should be removed, and asking the maintainer if he/she agrees with
reassigning the bug to ftp.debian.org".

Thank you,
Nicholas

Bug#734688: Logs are not rotated for a month

[Tim Connors]

On Wed, 16 Dec 2015, Michael Gebetsroither wrote:

> Package: logrotate
> Version: 3.8.7-1+b1
> Followup-For: Bug #734688
>
> Dear Maintainer,
>
> Seconded, the problem still persists in jessie.
> Logrotate was practically broken after /var/log got full a month ago.
>
> There where various .log.1.gz files, most of which where 0 bytes which
> stopped logrotate to act on those files completely.
>
> # grep 'error creating output file' logrotate_force_20151216.log
> error: error creating output file /var/log/dpkg.log.1.gz: File exists
> error: error creating output file /var/log/alternatives.log.1.gz: File exists
> error: error creating output file /var/log/nginx/error.log.1.gz: File exists
> error: error creating output file /var/log/nginx/access.log.1.gz: File exists
> error: error creating output file /var/log/php5-fpm.log.1.gz: File exists
> error: error creating output file /var/log/syslog.1.gz: File exists
> error: error creating output file /var/log/daemon.log.1.gz: File exists
> error: error creating output file /var/log/auth.log.1.gz: File exists
> error: error creating output file /var/log/messages.1.gz: File exists

And in my case, it wasn't a 0 byte file - there was syslog.1 and
syslog.1.gz, both largish.  It is possible gzip simply failed the first
time because I ran out of space.

2 observations:

1) logrotate didn't output any diagnostics, or exit non zero.
Consequently, I noticed nothing in my cron.daily email for a month.  I
only noticed when a usb failure meant the syslog file grew enormously, and
I saw the top of the messages were from a month prior.

2) All these suggestions of heuristics about deleting a file if 0 sized
and created immediately before etc.  Why not just, when logrotate finds a
base file whose .gz already exists, recursively call itself again to start
rotating down to the current file, which can then be compressed and resume
where we were?

Sorry no patches, already after my bedtime, and this has already been
languishing in my todo list for a couple of weeks.


-- 
Tim Connors

Bug#823839: oce: please rebuild against freeimage 3.17.0

[Graham Inggs]

Source: oce
Version: 0.17.1-1
Severity: serious


Hi Maintainer

OCE needs to be rebuilt against the current version of freeimage in 
order to pick up the correct library paths in shipped CMake files.
For example, 
/usr/lib/x86_64-linux-gnu/oce-0.16/OCE04_VisualizationTargets-relwithdebinfo.cmake 
contains /usr/lib/libfreeimage.s instead of 
/usr/lib/x86_64-linux-gnu/libfreeimage.so.  Please refer to Ubuntu bug 
LP: #1556680 [1].  This causes at least FreeCAD to FTBFS.


In addition, the Build-Depends on libfreeimage-dev needs to be changed 
to libfreeimageplus-dev, otherwise OCE builds without freeimage 
support.  This can be confirmed by searching for '-DHAVE_FREEIMAGE' in 
the build logs.  If it is not present, freeimage support is missing.


Lastly, some files are shipped in /usr/lib/*/oce-0.16 and some in 
/usr/lib/*/oce-0.17.

Is this correct?  Please refer to Ubuntu bug LP: #1556685 [2].

Regards
Graham


[1] https://bugs.launchpad.net/bugs/1556680
[2] https://bugs.launchpad.net/bugs/1556685

Bug#823821: marked as done (RFS: sympow/1.023-7 [SeriousBugFix] mathematical program for SYMmetric POWer elliptic curve L-func)

[Debian Bug Tracking System]

Your message dated Mon, 9 May 2016 14:01:17 + (UTC)
with message-id <1243935506.1871315.1462802477370.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#823821: RFS: sympow/1.023-7 [SeriousBugFix] 
mathematical program for SYMmetric POWer elliptic curve L-func
has caused the Debian Bug report #823821,
regarding RFS: sympow/1.023-7 [SeriousBugFix] mathematical program for 
SYMmetric POWer elliptic curve L-func
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
823821: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: serious
Justification: Policy 12.5

Dear Sponsors,

I am looking for a Sponsor for the package sympow, this is a 
mathematical
package needed by Sage, a kind of Computer Algebra System (CAS) bunch.
This very package fixes a Serious bug and (persistant) reproducible 
issue.

Thanks in advaance,
Jerome

[1] https://anonscm.debian.org/cgit/debian-science/packages/sympow.git

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

Kernel: Linux 3.16.7-ckt20-0001-mbp62 (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: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Hi, sponsored!

cheers,

G.



Il Lunedì 9 Maggio 2016 12:57, Jerome Benoit  ha scritto:



Package: sponsorship-requests
Severity: serious
Justification: Policy 12.5

Dear Sponsors,

I am looking for a Sponsor for the package sympow, this is a mathematical
package needed by Sage, a kind of Computer Algebra System (CAS) bunch.
This very package fixes a Serious bug and (persistant) reproducible issue.

Thanks in advaance,
Jerome

[1] https://anonscm.debian.org/cgit/debian-science/packages/sympow.git

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

Kernel: Linux 3.16.7-ckt20-0001-mbp62 (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: sysvinit (via /sbin/init)--- End Message ---

Bug#821009: marked as done (simple-image-reducer: EXIF reading results in crash (wrong import))

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 13:50:02 +
with message-id 
and subject line Bug#821009: fixed in simple-image-reducer 1.0.2-4
has caused the Debian Bug report #821009,
regarding simple-image-reducer: EXIF reading results in crash (wrong import)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
821009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: simple-image-reducer
Version: 1.0.2-3
Severity: grave
Tags: patch
Justification: renders package unusable

The upstream repository for this package imports the python `EXIF` library,
which seems to have been changed to `exifread` by Debian maintainers.
Unfortunately the place where the `EXIF` library was actually used in the
source code has not been changed to use the new name.


Patch:

--- ./simple-image-reducer  2016-04-14 16:45:21.295397481 +0200
+++ /usr/bin/simple-image-reducer   2016-04-14 16:45:47.860312235 +0200
@@ -457,7 +457,7 @@
 transpose_methods = [Image.ROTATE_270]
 elif rotate_method == 'exif':
 if 'exif' in img.info:
-tags = EXIF.process_file(open(input), details=False)
+tags = exifread.process_file(open(input), details=False)
 if 'Image Orientation' in tags:
 transpose_methods = exif_to_transpose[
 tags['Image Orientation'].values[0] - 1]



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

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

Versions of packages simple-image-reducer depends on:
ii  python  2.7.9-1tanglu1
ii  python-exif 2.1.2-1
ii  python-gtk2 2.24.0-4
ii  python-imaging  3.1.1-1

simple-image-reducer recommends no packages.

simple-image-reducer suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: simple-image-reducer
Source-Version: 1.0.2-4

We believe that the bug you reported is fixed in the latest version of
simple-image-reducer, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 821...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
TANIGUCHI Takaki  (supplier of updated simple-image-reducer 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 May 2016 22:23:54 +0900
Source: simple-image-reducer
Binary: simple-image-reducer
Architecture: source all
Version: 1.0.2-4
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: TANIGUCHI Takaki 
Description:
 simple-image-reducer - GTK application to easily reduce and rotate images
Closes: 821009
Changes:
 simple-image-reducer (1.0.2-4) unstable; urgency=medium
 .
   * debian/patcher/fix_exif_module_name: Fix wrong module name.
 (Closes: #821009)
   * debian/control: Bump Standards-Version to 3.9.8.
Checksums-Sha1:
 880ba213dba2092e7e6404acf7a244cca739e631 2106 simple-image-reducer_1.0.2-4.dsc
 d0866d6f50fa5943ece7cc1fde31b08d10d80013 2292 
simple-image-reducer_1.0.2-4.debian.tar.xz
 60e936591c6b87efb81568717a998c11d449247b 15198 
simple-image-reducer_1.0.2-4_all.deb
Checksums-Sha256:
 f35c9fbb3c09f6bb861946d250933a3941184f1d50334cafbe5e99bbfe3fd181 2106 
simple-image-reducer_1.0.2-4.dsc
 bbf3efbd6b9cbc06318bc638571c51204726a5e6f6ee64772b8ca7d22e5ecae0 2292 
simple-image-reducer_1.0.2-4.debian.tar.xz
 35a3eafb0e9d632c979bd39954ed46b8618820f2eb381f33a1b339c3dac62dc3 15198 
simple-image-reducer_1.0.2-4_all.deb
Files:
 fdcd8fcdad6cc90d69d30ea5529a323d 2106 graphics extra 
simple-image-reducer_1.0.2-4.dsc
 0387bfa1fa7ee04a742ef290aa9f2c59 2292 graphics extra 
simple-image-reducer_1.0.2-4.debian.tar.xz
 

Bug#818552: nodejs on armel (v5l) fails with "illegal instruction"

[Jérémy Lal]

2016-05-09 15:41 GMT+02:00 Jérémy Lal :

> Hi,
>
> sorry for the delay,
>

Update: v8 has dropped armv5 support, see
https://github.com/nodejs/node/issues/5810
https://groups.google.com/forum/#!topic/v8-users/aSOFbaAQvMk

I'm going to remove "armel" from the list of Architectures.

Jérémy

Bug#818552: nodejs on armel (v5l) fails with "illegal instruction"

[Jérémy Lal]

Hi,

sorry for the delay,
somehow i did not receive this bug report.

Could you give me the output of
`cat /proc/cpuinfo` ?

Could you tell me if you get the same error with versions
4.3.1 or 4.4.3

If it does crash on version 4.3.1, and since this bug prevents migration to
testing,
i might lower its importance, but that doesn't mean i won't try to fix it.

Jérémy

Bug#821593: marked as done (php-net-ftp: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 13:34:37 +
with message-id 
and subject line Bug#821593: fixed in php-net-ftp 1:1.4.0-2
has caused the Debian Bug report #821593,
regarding php-net-ftp: PHP 7.0 Transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
821593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-net-ftp
Version: 1:1.4.0-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 php-net-ftp package currently depends on php5 php5-common .

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: php-net-ftp -- 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

iQJ8BAEBCgBmBQJXFUqwXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHnasP/jaZhnGxYyjSh8SjUhCx5lWm
BNz8/lZCdN7FQ3YY0H6QtIECoLXiP06qmMrn98+RnsNhyBkCAT5089Q/sTCqaUIB
Lxi3/p2LIfT8CHQLGy2peOOSSu1o4uBWprPEuKV8M2eIc9IBY3aguzamTCu33rml
yU/q2JhXKg/fbMUkre7zGLv87wOoZKa27o2qAR+WM/Ag7CHsXowvx5B8CdQQNWCg
paRmw7tr7/r6bvBItRLDPTFPAAHcYqd2o7Yz73SCsD5flgMha1SfWaVlVjy1gZ5F

Bug#821503: marked as done (hoteldruid: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 13:34:00 +
with message-id 
and subject line Bug#821503: fixed in hoteldruid 2.1.4-2
has caused the Debian Bug report #821503,
regarding hoteldruid: PHP 7.0 Transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
821503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hoteldruid
Version: 2.1.4-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 hoteldruid package currently depends on libapache2-mod-php5 php5
php5-cgi php5-sqlite .

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: hoteldruid -- 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

iQJ8BAEBCgBmBQJXFUptXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH7AYP/0thbgrGKv2LNVLweW1vsxQL
optQZiV3F34ImuQZH0VL/OJVqQBhBOQWLlyhwCvW7X3wJWh6Pwz/Gn7eumB9hJJ1
PflnLKamnY1KQrUR4WAxi3LT7vjdD7ImvDTmSN2w8iTcyKsppKqvbhlkCrxbNWDI
jzKCFHMYOnVJL55ROmnNPkRRu1ZJuzGriKxH9vXBbimUL3QN48i8o0If1OGc4gss

Bug#821534: marked as done (moodle: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 13:21:42 +
with message-id 
and subject line Bug#821534: fixed in moodle 2.7.14+dfsg-1
has caused the Debian Bug report #821534,
regarding moodle: PHP 7.0 Transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
821534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: moodle
Version: 2.7.13+dfsg-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 moodle package currently depends on libapache2-mod-php5 php5 php5-cgi
php5-cli php5-curl php5-fpm php5-gd php5-mysql php5-pgsql .

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: moodle -- 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

iQJ8BAEBCgBmBQJXFUqEXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHKc0QANXt3IKtvYLGtiz6WN0Xe6bw
Ll+pEnQEmBhLZ8S4QHoAmlSdBlNopAPPrQXvSXB6yw7D7umbTaGo+/M+464idRcp
GDtarovofQmcIUXyvj/Vkkr/udq4UunSBM3o0cBIBpf1h6vxa2yPl+qyhCKwy/hM
vDO7Iey5qX0WAIHhfD34aQrVwVJt94eOS7LPH2r20moWK4RqqIYrh1sFaiNo1g0r

Bug#823830: qemu: CVE-2016-3710 CVE-2016-3712

[Salvatore Bonaccorso]

Source: qemu
Version: 2.1+dfsg-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerabilities were published for qemu.

CVE-2016-3710[0]:
incorrect banked access bounds checking in vga module

CVE-2016-3712[1]:
Out-of-bounds read when creating weird vga screen surface

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-3710
[1] https://security-tracker.debian.org/tracker/CVE-2016-3712
[2] http://xenbits.xen.org/xsa/advisory-179.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#823515: marked as done (php7.0-cli: missing Depends: php-common (>= 1:37))

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 12:08:07 +
with message-id 
and subject line Bug#823515: fixed in php-defaults 40
has caused the Debian Bug report #823515,
regarding php7.0-cli: missing Depends: php-common (>= 1:37)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
823515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php7.0-cli
Version: 7.0.6-1

Saw:
update-alternatives: warning: forcing reinstallation of alternative 
/usr/bin/phar7.0 because link group phar is broken

 Additional PHP 7.0 information 

 PHP 7.0 SAPI (php7.0query -S): 

 PHP 7.0 Extensions (php7.0query -M -v): 

 Configuration files: 
[PHP]
engine = On
short_open_tag = Off
precision = 14
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = 17
disable_functions =
disable_classes =
zend.enable_gc = On
expose_php = On
max_execution_time = 30
max_input_time = 60
memory_limit = -1
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
track_errors = Off
html_errors = On
variables_order = "GPCS"
request_order = "GP"
register_argc_argv = Off
auto_globals_jit = On
post_max_size = 8M
auto_prepend_file =
auto_append_file =
default_mimetype = "text/html"
default_charset = "UTF-8"
doc_root =
user_dir =
enable_dl = Off
file_uploads = On
upload_max_filesize = 2M
max_file_uploads = 20
allow_url_fopen = On
allow_url_include = Off
default_socket_timeout = 60
[CLI Server]
cli_server.color = On
[Date]
[filter]
[iconv]
[intl]
[sqlite3]
[Pcre]
[Pdo]
[Pdo_mysql]
pdo_mysql.cache_size = 2000
pdo_mysql.default_socket=
[Phar]
[mail function]
SMTP = localhost
smtp_port = 25
mail.add_x_header = On
[SQL]
sql.safe_mode = Off
[ODBC]
odbc.allow_persistent = On
odbc.check_persistent = On
odbc.max_persistent = -1
odbc.max_links = -1
odbc.defaultlrl = 4096
odbc.defaultbinmode = 1
[Interbase]
ibase.allow_persistent = 1
ibase.max_persistent = -1
ibase.max_links = -1
ibase.timestampformat = "%Y-%m-%d %H:%M:%S"
ibase.dateformat = "%Y-%m-%d"
ibase.timeformat = "%H:%M:%S"
[MySQLi]
mysqli.max_persistent = -1
mysqli.allow_persistent = On
mysqli.max_links = -1
mysqli.cache_size = 2000
mysqli.default_port = 3306
mysqli.default_socket =
mysqli.default_host =
mysqli.default_user =
mysqli.default_pw =
mysqli.reconnect = Off
[mysqlnd]
mysqlnd.collect_statistics = On
mysqlnd.collect_memory_statistics = Off
[OCI8]
[PostgreSQL]
pgsql.allow_persistent = On
pgsql.auto_reset_persistent = Off
pgsql.max_persistent = -1
pgsql.max_links = -1
pgsql.ignore_notice = 0
pgsql.log_notice = 0
[bcmath]
bcmath.scale = 0
[browscap]
[Session]
session.save_handler = files
session.use_strict_mode = 0
session.use_cookies = 1
session.use_only_cookies = 1
session.name = PHPSESSID
session.auto_start = 0
session.cookie_lifetime = 0
session.cookie_path = /
session.cookie_domain =
session.cookie_httponly =
session.serialize_handler = php
session.gc_probability = 0
session.gc_divisor = 1000
session.gc_maxlifetime = 1440
session.referer_check =
session.cache_limiter = nocache
session.cache_expire = 180
session.use_trans_sid = 0
session.hash_function = 0
session.hash_bits_per_character = 5
url_rewriter.tags = "a=href,area=href,frame=src,input=src,form=fakeentry"
[Assertion]
zend.assertions = -1
[COM]
[mbstring]
[gd]
[exif]
[Tidy]
tidy.clean_output = Off
[soap]
soap.wsdl_cache_enabled=1
soap.wsdl_cache_dir="/tmp"
soap.wsdl_cache_ttl=86400
soap.wsdl_cache_limit = 5
[sysvshm]
[ldap]
ldap.max_links = -1
[mcrypt]
[dba]
[opcache]
[curl]
[openssl]

 /etc/php/7.0/cli/conf.d/10-pdo.ini 
extension=pdo.so

 /etc/php/7.0/cli/conf.d/20-gettext.ini 
extension=gettext.so

 /etc/php/7.0/cli/conf.d/20-mysqli.ini 
extension=mysqli.so

 /etc/php/7.0/cli/conf.d/10-mysqlnd.ini 
extension=mysqlnd.so

 /etc/php/7.0/cli/conf.d/20-sysvsem.ini 
extension=sysvsem.so

 /etc/php/7.0/cli/conf.d/20-xsl.ini 
extension=xsl.so

 /etc/php/7.0/cli/conf.d/20-calendar.ini 
extension=calendar.so

 /etc/php/7.0/cli/conf.d/20-iconv.ini 
extension=iconv.so

 /etc/php/7.0/cli/conf.d/20-posix.ini 
extension=posix.so

 /etc/php/7.0/cli/conf.d/20-simplexml.ini 
extension=simplexml.so

 /etc/php/7.0/cli/conf.d/20-dom.ini 
extension=dom.so

 /etc/php/7.0/cli/conf.d/20-ftp.ini 

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

[Ondřej Surý]

Chris,

I would say go ahead unless Cleto (who was the last person who cared
about zeroc-ice in 2014) or Francisco (who is still listed as maintainer
even though he last touched the package in 2012) violenty object.

I am also Ccing ZeroC, Inc. folks, as they might be interested in
properly maintaining zeroc-ice in Debian. I am quite sure that there
will be always somebody (me, you...) willing to review the packaging and
sponsor the upload to Debian if they do the heavy lifting.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

On Mon, May 9, 2016, at 13:36, Chris Knadle wrote:
> Ondřej Surý:
> > Hi Chris,
> > 
> > thanks for taking care of this.
> > 
> > You can either try to backport PHP portion of 3.7.0-alpha0 to 3.6.2[*],
> > or check with upstream if they can finish 3.7.0 before stretch freeze
> > and if they can make it package 3.7.0-alpha0 right away.
> > 
> > * - or ask upstream to include this update in 3.6.X
> 
> The reason I'm involved here is that mumble depends on zeroc-ice and is
> going to removed with it if this bug isn't handled.
> 
> I looked at a 'diff -U 1' (1 line of context) of the PHP code between
> 3.5.1
> and 3.7.0-alpha0 and it's ~10k lines; this is not something that would be
> reasonable as a patch in an NMU.  I don't think uploading a new version
> of
> the software as an NMU is in this case either -- someone would have to be
> familiar with using the software before they'd be comfortable sponsoring
> an
> NMU upload and this is a package with niche use.
> 
> Instead the best plan I know of at the moment is removing any PHP
> dependencies from the package for now -- meaning commenting out php5-dev
> +
> php-zeroc-ice dependencies and the entire php-zeroc-ice section in
> debian/control and not shipping the php-zeroc-ice binary package for now.
> There are no packages that depend on php-zeroc-ice in Debian, so this
> shouldn't cause any known breakage.  It's not normally what I'd do but I
> don't see a better option.
> 
> A debdiff of this is attached.
> 
>-- Chris
> 
> -- 
> Chris Knadle
> chris.kna...@coredump.us
> Email had 2 attachments:
> + zeroc-ice_3.5.1-6.5.debdiff
>   8k (text/plain)
> + signature.asc
>   1k (application/pgp-signature)

Bug#821482: drupal7: PHP 7.0 Transition ← Help requested!

[Ondřej Surý]

Hi Gunnar,

to my (limited[1]) knowledge the differences between 5.6 and 7.0 aren't
that big from users' perspective, so short patch doesn't have to be
wrong for a well-maintained code. See this list of incompatibilites from
PHP 7.0 upgrade guide:
https://secure.php.net/manual/en/migration70.incompatible.php

The patch is question is a bit confusing, because it obviously mixes
fixes for PHP 5.4, PHP 5.5 GD bug and PHP 7.0 updates, but overall it
looks good. That said there might be more some changes that wouldn't
trigger immediate parse errors, but might change some behavior in more
subtle way. However as drupal7 is well-maintained project with good
coding standards (am I right?), I would guess the chances are low for
this to happen.

Anyway I would suggest to update drupal7 with this patch and progress
with new updates as we go. You don't have any other options right now
anyway, right? :)

1. Fortunately it's been ages since I coded in PHP.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

On Thu, May 5, 2016, at 21:20, Gunnar Wolf wrote:
> tag 821482 + confirmed upstream patch pending
> thanks
> 
> Hi,
> 
> I'm contacting pkg-php-maint as recommendad by Ondřej's original mass
> bug filing, hopefully avoiding the removal of Drupal7 from Debian.
> 
> As it is now, at version 7.43, Drupal7 is *not* PHP7-clean, and it is
> documented with bugs in the upstream tracker:
> 
> https://www.drupal.org/node/2656548 — Drupal 7 PHP 7 testing issue
> https://www.drupal.org/node/2454439 — [META] Support PHP 7
> 
> Following the first link to the bottom, it *seems* that, three days
> ago, Mike Carper achieved a clean test run on PHP7:
> 
> https://dispatcher.drupalci.org/job/default/124946/testReport/
> 
> The patch in question:
> 
> https://www.drupal.org/files/issues/drupal-2656548-21-php7.patch
> 
> Now, the reason to contact pkg-php-maint... Even though I maintain
> Drupal7 for a long time, I do consider myself a PHP newbie. Could you
> help me ascertain iv the patch makes linguistic sense in PHP7? Help me
> check if this looks like enough, and without changing the logic?
> 
> I gave a *very* quick look at it, and the patch looks much shorter
> than what I expected. I don't know the extent of the language
> incompatibilities between 5.6 and 7, but if this works, I will be a
> very happy maintainer.
> 
> I have created a "php7" branch in the packaging repository; I have not
> built the package yet, but it should be doable trivially:
> 
> https://anonscm.debian.org/cgit/collab-maint/drupal7.git/commit/?h=php7
> 
> I intend to do as much testing as I can, but any help is welcome. I am
> quite time-stressed, and don't want to delay this until I got time to
> dig into it.
> 
> Thanks a lot!
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

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

[Chris Knadle]

Ondřej Surý:
> Hi Chris,
> 
> thanks for taking care of this.
> 
> You can either try to backport PHP portion of 3.7.0-alpha0 to 3.6.2[*],
> or check with upstream if they can finish 3.7.0 before stretch freeze
> and if they can make it package 3.7.0-alpha0 right away.
> 
> * - or ask upstream to include this update in 3.6.X

The reason I'm involved here is that mumble depends on zeroc-ice and is
going to removed with it if this bug isn't handled.

I looked at a 'diff -U 1' (1 line of context) of the PHP code between 3.5.1
and 3.7.0-alpha0 and it's ~10k lines; this is not something that would be
reasonable as a patch in an NMU.  I don't think uploading a new version of
the software as an NMU is in this case either -- someone would have to be
familiar with using the software before they'd be comfortable sponsoring an
NMU upload and this is a package with niche use.

Instead the best plan I know of at the moment is removing any PHP
dependencies from the package for now -- meaning commenting out php5-dev +
php-zeroc-ice dependencies and the entire php-zeroc-ice section in
debian/control and not shipping the php-zeroc-ice binary package for now.
There are no packages that depend on php-zeroc-ice in Debian, so this
shouldn't cause any known breakage.  It's not normally what I'd do but I
don't see a better option.

A debdiff of this is attached.

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us
diff -Nru zeroc-ice-3.5.1/debian/changelog zeroc-ice-3.5.1/debian/changelog
--- zeroc-ice-3.5.1/debian/changelog2016-03-04 23:17:37.0 -0500
+++ zeroc-ice-3.5.1/debian/changelog2016-05-09 07:28:11.0 -0400
@@ -1,3 +1,26 @@
+zeroc-ice (3.5.1-6.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+- Temporarily remove PHP support and the php-zeroc-ice package, as
+  PHP 5 is being removed from Debian and the current zeroc-ice package
+  as well as the available upstream zeroc-ice release tarballs are
+  not compatible with PHP 7.  Upstream git tag v3.7.0-alpha0 seems
+  to be the first version that supports PHP 7.
+  (Closes: #821723, #821639)
+
+  [ Christopher Knadle ]
+  * debian/changelog summary
+  * debian/NEWS:
+- Add entry explaining the necessity of removing PHP support
+
+  [ Gregor Herrmann ]
+  * debian/control:
+- Comment out php-dev dependency and php-zeroc-ice package
+  * debian/rules:
+- Comment out PHP references to keep PHP code from being built
+
+ -- Christopher Knadle   Sun, 08 May 2016 04:53:21 
-0400
+
 zeroc-ice (3.5.1-6.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru zeroc-ice-3.5.1/debian/control zeroc-ice-3.5.1/debian/control
--- zeroc-ice-3.5.1/debian/control  2016-03-04 21:59:26.0 -0500
+++ zeroc-ice-3.5.1/debian/control  2016-05-08 21:50:18.0 -0400
@@ -13,7 +13,7 @@
   zlib1g-dev | libz-dev,
   python-all-dev (>= 2.3.5-11),
   python3-all-dev,
-  php5-dev (>= 5.4.0~rc6),
+# php5-dev (>= 5.4.0~rc6),
   ruby-dev,
   ruby,
   libqt4-dev,
@@ -44,7 +44,7 @@
 libzeroc-ice3.5-cil (>= ${binary:Version}),
 python-zeroc-ice (>= ${binary:Version}),
 python3-zeroc-ice (>= ${binary:Version}),
-php-zeroc-ice (>= ${binary:Version}),
+#   php-zeroc-ice (>= ${binary:Version}),
 libzeroc-ice3.5-java (>= ${binary:Version}),
 ${misc:Depends}
 Recommends: libzeroc-ice35-dbg (>= ${binary:Version})
@@ -492,7 +492,7 @@
 ice35-translators (= ${binary:Version}),
 python-zeroc-ice (= ${binary:Version}),
 python3-zeroc-ice (= ${binary:Version}),
-php-zeroc-ice (= ${binary:Version}),
+#   php-zeroc-ice (= ${binary:Version}),
 ruby-zeroc-ice (= ${binary:Version}),
 icebox (= ${binary:Version}),
 ${misc:Depends}
@@ -554,26 +554,26 @@
  information in the ZeroC home page (http://www.zeroc.com/ice.html)
  and in the non-free package zeroc-ice-manual.
 
-Package: php-zeroc-ice
-Architecture: any
-Section: php
-Depends: php5-cli (>= 5.4.0~rc6-1) | php5 (>= 5.4.0~rc6-1),
-${shlibs:Depends}, ${misc:Depends}, ${php:Depends}
-Recommends: ice35-slice | ice-slice
-Description: Ice for PHP extension
- Ice, the Internet Communications Engine, is a middleware for the
- practical programmer developed by ZeroC Inc. A high-performance
- Internet communications platform, Ice includes a wealth of layered
- services and plug-ins.
- .
- Ice is built on concepts which will be familiar to CORBA programmers,
- and supports a wide variety of programming languages and runtime
- platforms.
- .
- This package contains the PHP extension module required to
- run/develop applications with Ice for PHP.  You will find further
- information in the ZeroC home page (http://www.zeroc.com/ice.html)
- and in the non-free package zeroc-ice-manual.
+#Package: php-zeroc-ice
+#Architecture: any
+#Section: php

Bug#823673: marked as done (samtools: FTBFS in testing)

[Debian Bug Tracking System]

Your message dated Mon, 9 May 2016 20:32:56 +0900
with message-id <20160509113256.GE16724@bubu.igloo>
and subject line Re: [Debian-med-packaging] Bug#823673: samtools: FTBFS in 
testing
has caused the Debian Bug report #823673,
regarding samtools: FTBFS in testing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
823673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samtools
Version: 1.3.1-1
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch.


=== Testing mpileup.reg regressions ===

UNEXPECTED FAIL: Output mismatch for $samtools mpileup -x -d 8500 -B -f 
mpileup.ref.fa deep.sam|awk '{print $4}'
See FAIL-47.out.1 vs expected/47.out


The full build log is attached.

I see that this package required a change recently for htslib 1.3.1.
However, if this only builds now with libhts >= 1.3.1, then the
Build-Depends field should be updated accordingly.

Thanks.

samtools_1.3.1-1_amd64-20160507-1455.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1.3.1-2

Le Sun, May 08, 2016 at 09:45:35PM +0900, Charles Plessy a écrit :
> Version: 1.3.1-2
 
> Thanks for the report; the issue was already reported in #822701, which I just
> fixed by updating Build-Depends.

Oops, forgot to close... done.

-- 
Charles--- End Message ---

Bug#823297: libbotan: security update breaks monotone

[Tim Weippert]

HI, 

On Mon, May 09, 2016 at 11:18:42AM +0200, Tim Weippert wrote:
> On Wed, May 04, 2016 at 06:19:25PM +0200, Markus Koschany wrote:
 
[ ... ]
 
> I try to rebuild monotone on the system against the updated lib and get back 
> to you. 

Rebuild of monotone fixed the issue. For more informations ldd/informations of 
mtn pull:

Before Security Update:

root@lab-server01:~/XXX# mtn pull
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to 'mtn://XXX/'
mtn:   include pattern  'XXX.*'
mtn:   exclude pattern  ''
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
mtn:   51,019 |  118 |16,837
mtn:  bytes in | bytes out | certs in | revs in
mtn: 1.4 k | 1.5 k |  0/0 | 0/0
mtn: successful exchange with 'XXX'

root@lab-server01:~/XXX# ldd `which mtn`
linux-vdso.so.1 (0x7ffdac731000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fee7d5d3000)
libbotan-1.10.so.0 => /usr/lib/libbotan-1.10.so.0 (0x7fee7d0d5000)
liblua5.1.so.0 => /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 
(0x7fee7cea8000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fee7cbdf000)
libidn.so.11 => /usr/lib/x86_64-linux-gnu/libidn.so.11 
(0x7fee7c9ab000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fee7c79)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fee7c485000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fee7c184000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fee7bf6e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fee7bbc3000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fee7b9a6000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fee7b796000)
libcrypto.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 
(0x7fee7b39b000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fee7b197000)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
(0x7fee7af14000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fee7ad0c000)
/lib64/ld-linux-x86-64.so.2 (0x7fee7d841000)


After Security Update:

root@lab-server01:~/XXX# mtn pull
mtn: Symbol `_ZTVN5Botan17DataSource_MemoryE' has different size in shared 
object, consider re-linking
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to 'mtn://XXX/'
mtn:   include pattern  'XXX'
mtn:   exclude pattern  ''
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
mtn:   51,019 |  118 |16,837
mtn: fatal signal: Segmentation fault
this is almost certainly a bug in monotone.
please send this error message, the output of 'mtn version --full',
and a description of what you were doing to 

do not send a core dump, but if you have one, 
please preserve it in case we ask you for information from it.
Segmentation fault

root@lab-server01:~/XXX# ldd `which mtn`
linux-vdso.so.1 (0x7fff3d39)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fb7a19f3000)
libbotan-1.10.so.0 => /usr/lib/libbotan-1.10.so.0 (0x7fb7a14f2000)
liblua5.1.so.0 => /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 
(0x7fb7a12c5000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fb7a0ffc000)
libidn.so.11 => /usr/lib/x86_64-linux-gnu/libidn.so.11 
(0x7fb7a0dc8000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fb7a0bad000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fb7a08a2000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fb7a05a1000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fb7a038b000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb79ffe)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fb79fdc3000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fb79fbb3000)
libcrypto.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 
(0x7fb79f7b7000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fb79f5b3000)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
(0x7fb79f33)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fb79f128000)
/lib64/ld-linux-x86-64.so.2 (0x7fb7a1c61000)

After Rebuild of monotone:

root@lab-server01:~/XXX# mtn pull
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to 'mtn://XXX/'
mtn:   include pattern  'XXX.*'
mtn:   exclude pattern  ''
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
mtn:   51,019 |  118 |16,837
mtn:  bytes in | bytes out | certs in | revs in
mtn: 8.8 k | 6.5 k |  4/4 | 1/1
mtn: successful exchange with 'mtn://XXX/'

Bug#823821: RFS: sympow/1.023-7 [SeriousBugFix] mathematical program for SYMmetric POWer elliptic curve L-func

[Jerome Benoit]

Package: sponsorship-requests
Severity: serious
Justification: Policy 12.5

Dear Sponsors,

I am looking for a Sponsor for the package sympow, this is a 
mathematical
package needed by Sage, a kind of Computer Algebra System (CAS) bunch.
This very package fixes a Serious bug and (persistant) reproducible 
issue.

Thanks in advaance,
Jerome

[1] https://anonscm.debian.org/cgit/debian-science/packages/sympow.git

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

Kernel: Linux 3.16.7-ckt20-0001-mbp62 (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: sysvinit (via /sbin/init)

Bug#821478: marked as done (dokuwiki: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 10:35:40 +
with message-id 
and subject line Bug#821478: fixed in dokuwiki 0.0.20150810.a-2
has caused the Debian Bug report #821478,
regarding dokuwiki: PHP 7.0 Transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
821478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dokuwiki
Version: 0.0.20150810.a-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 dokuwiki package currently depends on php5 .

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: dokuwiki -- 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

iQJ8BAEBCgBmBQJXFUpbXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH41MP+wZtgDEh29C+tyjiOmwnhQPc
qT77kU34Xyf8DXU8BLh2nuDbo7EvR7uH6Ur0AJaMQl+saAdahropzmZLO4P+mk8c
Cfqv4DGdXubZRJR3HL05n3+IdilV8PWBVZh2ug4C+leqMAauiJi90mR6vfvFnD5g
RnCzHVdBwLAp+Q1VE1p9TE+6GylUR8uLQIHglx2TdnIiEPJBh1pPC/69I6uVSian
RBiPg+Uh3S0KTFjxAe0I7KnY15ezZwZsOfr14kidCn5+FF+IuORbB/WjEWSPOmDx

Bug#818873: gcc-5-cross: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Andreas Beckmann]

Control: tag -1 - help + pending

On 2016-05-09 11:54, Matthias Klose wrote:
> On 09.05.2016 10:17, Andreas Beckmann wrote:
>> Followup-For: Bug #818873
> 
> that's already fixed in the VCS.

Good, so let's fix the tags :-)

Andreas

Processed: Re: Bug#818873: gcc-5-cross: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - help + pending
Bug #818873 [src:gcc-5-cross] gcc-5-cross: FTBFS when built with 
dpkg-buildpackage -A (No such file or directory)
Removed tag(s) help.
Bug #818873 [src:gcc-5-cross] gcc-5-cross: FTBFS when built with 
dpkg-buildpackage -A (No such file or directory)
Added tag(s) pending.

-- 
818873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#823813: netbeans: non-DFSG .xsd files (no modification?)

[Dmitry Smirnov]

Source: netbeans
Version: 8.1+dfsg2-3
Severity: serious
Usertags: dfsg

Files:

websvc.wsitmodelext/src/org/netbeans/modules/websvc/wsitmodelext/catalog/resources/wsrm-policy-200502.xsd

websvc.wsitmodelext/src/org/netbeans/modules/websvc/wsitmodelext/catalog/resources/WS-Trust.xsd

websvc.wsitmodelext/src/org/netbeans/modules/websvc/wsitmodelext/catalog/resources/metadata-exchange.xsd

websvc.wsitmodelext/src/org/netbeans/modules/websvc/wsitmodelext/catalog/resources/optimizedmimeserialization-policy.xsd

websvc.wsitmodelext/src/org/netbeans/modules/websvc/wsitmodelext/catalog/resources/ws-policy-10.xsd

websvc.wsitmodelext/src/org/netbeans/modules/websvc/wsitmodelext/catalog/resources/wsat.xsd

are licensed under terms allowing only distribution (i.e. "copy and display")
while explicitly prohibiting everything else:

   "No other rights are granted by implication, estoppel or otherwise."

I'm particularly concerned about modification rights that appears to be 
prohibited.

Please investigate.

-- 
Regards,
 Dmitry Smirnov.

---

Truth — Something somehow discreditable to someone.
-- H. L. Mencken, 1949



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

Bug#823812: netbeans: non-free files

[Dmitry Smirnov]

Source: netbeans
Version: 8.1+dfsg2-3
Severity: serious
Usertags: dfsg

Files:
cnd/javahelp/org/netbeans/modules/cnd/help/legal_notice.htm

javacard.project/javahelp/org/netbeans/modules/javacard/project/docs/help/docinfo.html

Contain fairly restrictive license:


Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce,
translate, broadcast, modify, license, transmit, distribute, exhibit,
perform, publish, or display any part, in any form, or by any means.
Reverse engineering, disassembly, or decompilation of this software, unless
required by law for interoperability, is prohibited.


Those terms seems to apply to other files in respective directories.

File:
java.sourceui/test/unit/src/org/netbeans/api/java/source/ui/FileChooser.html

is explicitly licensed under those terms.



File:

javascript2.extjs/test/unit/data/testfiles/completion/applyMethod/ClassManager.js

contains the following:


Licensees holding valid commercial licenses may use this file in accordance 
with the Commercial
Software License Agreement provided with the Software or, alternatively, in 
accordance with the
terms contained in a written agreement between you and Sencha.


However no other license is mentioned.



Files:
j2ee.dd/src/org/netbeans/modules/j2ee/dd/impl/resources/web-app_2_3.dtd

j2ee.ddloaders/src/org/netbeans/modules/j2ee/ddloaders/catalog/resources/web-app_2_3.dtd

j2ee.sun.dd/src/org/netbeans/modules/j2ee/sun/dd/impl/resources/static-verification_1_4.dtd

j2ee.weblogic9/src/org/netbeans/modules/j2ee/weblogic9/resources/ejb-jar_2_1.xsd

j2ee.weblogic9/src/org/netbeans/modules/j2ee/weblogic9/resources/j2ee_1_4.xsd

j2ee.weblogic9/src/org/netbeans/modules/j2ee/weblogic9/resources/j2ee_web_services_client_1_1.xsd
j2ee.weblogic9/src/org/netbeans/modules/j2ee/weblogic9/resources/jsp_2_0.xsd

j2ee.weblogic9/src/org/netbeans/modules/j2ee/weblogic9/resources/web-app_2_4.xsd
schema2beans/test/unit/data/TestApplication1_4.xsd
schema2beans/test/unit/data/TestFinalWebApp.xsd
schema2beans/test/unit/data/TestWebApp.xsd
schema2beans/test/unit/data/TestWebAppDelegator.xsd
schema2beans/test/unit/data/TestWebAppDelegatorBaseBean.xsd
schema2beans/test/unit/data/final_j2ee_1_4.xsd
schema2beans/test/unit/data/final_jsp_2_0.xsd
schema2beans/test/unit/data/j2ee_1_4.xsd
schema2beans/test/unit/data/j2ee_web_services_client_1_1.xsd
schema2beans/test/unit/data/jsp_2_0.xsd
web.core/src/org/netbeans/modules/web/taglib/resources/j2ee_1_4.xsd

web.core/src/org/netbeans/modules/web/taglib/resources/j2ee_web_services_client_1_1.xsd

web.core/src/org/netbeans/modules/web/taglib/resources/web-jsptaglibrary_2_0.xsd


 This document and the technology which it describes are
 distributed under licenses restricting their use, copying,
 distribution, and decompilation. No part of this document
 may be reproduced in any form by any means without prior
 written authorization of Sun and its licensors, if any.


Same terms are also present in the following files, under
"CDDL or GPL-2 and exception-GPL-Classpath" header:

Files:
web.jsf/src/org/netbeans/modules/web/jsf/resources/javaee_5.xsd

web.jsf/src/org/netbeans/modules/web/jsf/resources/javaee_web_services_client_1_2.xsd
web.jsf/src/org/netbeans/modules/web/jsf/resources/web-facesconfig_1_2.xsd
web.jsf/src/org/netbeans/modules/web/jsf/resources/web-facesconfig_2_0.xsd



File:
php.editor/test/unit/data/testfiles/parser/performance/performance.php

is from "SMF 1.1" which is non-free according to

http://www.simplemachines.org/about/opensource.php


 The license used for SMF 1.0 and SMF 1.1 is more restrictive than OSI
 approved licenses. That license allows users to modify the source, but does
 not allow them to redistribute or re-release the software without the
 express, written consent of Simple Machines.




Files:

cnd.makeproject/src/org/netbeans/modules/cnd/makeproject/ui/resources/samples/fractal.html

cnd.makeproject/src/org/netbeans/modules/cnd/makeproject/ui/resources/samples/hello.html

cnd.makeproject/src/org/netbeans/modules/cnd/makeproject/ui/resources/samples/lexyacc.html

cnd.makeproject/src/org/netbeans/modules/cnd/makeproject/ui/resources/samples/pi.html

editor.lib2/test/unit/src/org/netbeans/spi/editor/highlighting/performance/data/*

editor/test/qa-functional/data/org/netbeans/test/editor/data/OTA_TravelItinerary.xsd
java.lexer/test/unit/data/testfiles/JComponent.java.txt
web.jsf/src/org/netbeans/modules/web/jsf/resources/web-facesconfig_1_0.dtd
web.jsf/src/org/netbeans/modules/web/jsf/resources/web-facesconfig_1_1.dtd

xml.axi/test/unit/src/org/netbeans/modules/xml/axi/resources/OTA_TravelItinerary.xsd
xml.axi/test/unit/src/org/netbeans/modules/xml/axi/resources/address.xsd

Bug#823809: yosys: FTBFS in testing

[Santiago Vila]

Package: yosys
Version: 0.6-5
Severity: serious

Dear maintainer:

This package fails to build from source in stretch:


frontends/ast/ast.cc: In member function 'Yosys::RTLIL::Const 
Yosys::AST::AstNode::realAsConst(int)':
frontends/ast/ast.cc:860:17: error: 'isfinite' was not declared in this scope
  if (!isfinite(v)) {
 ^
frontends/ast/ast.cc:860:17: note: suggested alternative:
In file included from /usr/include/c++/5/random:38:0,
 from /usr/include/c++/5/bits/stl_algo.h:66,
 from /usr/include/c++/5/algorithm:62,
 from ./kernel/yosys.h:47,
 from frontends/ast/ast.cc:29:
/usr/include/c++/5/cmath:601:5: note:   'std::isfinite'
 isfinite(_Tp __x)
 ^
Makefile:340: recipe for target 'frontends/ast/ast.o' failed


The error seems related to #822408.

Note: If you need some -dev package which is only available in
unstable for now, consider using a versioned build-depends.
This will not prevent the package from propagating to testing
but at least everybody will know why it does not build.

The full build log is attached.

Thanks.

yosys_0.6-5_amd64-20160509-1144.gz
Description: application/gzip

Bug#823515: [php-maint] Bug#823515: php7.0-cli: missing Depends: php-common (>= 1:37)

[Ondřej Surý]

Hi Andreas,

thanks for detailed analysis. As the dpkg-divert is there only because
of Ubuntu 15.10 backports, I think the best path would be just to drop
(or wrap) the dpkg-divert altogether as it's only an ugly hack anyway
;).

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

On Fri, May 6, 2016, at 07:42, Andreas Beckmann wrote:
> Followup-For: Bug #823515
> 
> Hi,
> 
> during a test with piuparts I noticed some strange behavior w.r.t. the
> /usr/bin/phar alternative. After an upgrade from stretch to sid (which
> both have the same version of php7.0-cli), the /usr/bin/phar alternative
> is not cleaned up. This is not reproducible by just installing the
> package in either sid or stretch. An indication from the logfile is
> php-common diverting /usr/bin/phar on the upgrade from stretch to sid
> *after* php7.0-cli had set up an alternative there in stretch already.
> This most likely seems to clash in some way, so there should be a
> Depends on php-common (>= 1:37) to ensure the diversion is in place
> before the alternative is set up.
> 
> 
> Andreas
> 
> ___
> pkg-php-maint mailing list
> pkg-php-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint

Bug#818873: gcc-5-cross: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Matthias Klose]

On 09.05.2016 10:17, Andreas Beckmann wrote:

Followup-For: Bug #818873


that's already fixed in the VCS.

Bug#821534: [moodle-packaging] Bug#821534: Bumping severity of PHP 7.0 transition bugs to serious

[Ondřej Surý]

Joost,

thanks for letting me know. If moodle supports PHP 7 right away, it's
just a matter of replacing:

libapache2-mod-php5 | php5-cgi | php5-fpm, php5-mysql | php5-pgsql,
php5-gd, php5-curl, php5-cli,

with

php, php-mysql | php-pgsql, php-gd, php-curl, php-cli

(php is a virtual package that provides one of the web SAPIs, so you
don't have to list them all)

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

On Mon, May 9, 2016, at 09:41, Joost van Baal-Ilić wrote:
> Hi,
> 
> Op Thu, May 05, 2016 at 10:20:56AM +0200 schreef Ondřej Surý:
> > 
> > I am bumping the severity of this bug to serious, as we are going to
> > remove src:php5 from Debian and your package is blocking the first
> > step which is removal of php5 from testing.  Please either update your
> > package to support PHP 7.0 or remove the package from Debian unstable
> > alltogether.
> 
> Thanks, will upload a fixed moodle this month.  Dan Poltawski: thanks for
> your
> comment; appreciated.
> 
> Bye,
> 
> Joost
> 
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

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

[Ondřej Surý]

Hi Chris,

thanks for taking care of this.

You can either try to backport PHP portion of 3.7.0-alpha0 to 3.6.2[*],
or check with upstream if they can finish 3.7.0 before stretch freeze
and if they can make it package 3.7.0-alpha0 right away.

* - or ask upstream to include this update in 3.6.X

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

On Sun, May 8, 2016, at 00:20, Chris Knadle wrote:
> Update: none of the zeroc-ice release tarballs (including the current
> 3.6.2
> tarball) seem to support PHP 7 as best I can tell.  The v3.7.0-alpha0 tag
> in
> the upstream git repository does.
> 
> https://github.com/zeroc-ice/ice/tree/v3.7.0-alpha0
> 
> In the v3.7.0-alpha0 tag, php/src has separate "php5" and "php7"
> directories
> and code to choose which of these to use during the compile based on
> what's
> available on the system it's built with.  None of the 3.6 series seems to
> have this.
> 
>-- Chris
> 
> -- 
> Chris Knadle
> chris.kna...@coredump.us
> 
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

Bug#823297: libbotan: security update breaks monotone

[Tim Weippert]

On Wed, May 04, 2016 at 06:19:25PM +0200, Markus Koschany wrote:

[ ... ]

> I can't reproduce the segmentation fault on my system. Could you share
> some information about your setup? What exactly did you do before the
> segfault happened? Did you restart the monotone-server after the
> upgrade? Can you confirm that a rebuild fixes the issue?

It is not the monotone-server i running, it is an mtn update/pull/sync action 
from an
monotone-server. The System is an basic jessie vm on an kvm environment located 
by an hoster.

> I haven't seen other issues with the security update of libbotan1.10 so
> far but if monotone needs a rebuild, this bug should be reassigned to
> monotone.

I try to rebuild monotone on the system against the updated lib and get back to 
you. 

cheers, 
tim

-- 
Tim Weippert
http://weiti.org - we...@weiti.org
GPG Fingerprint - E704 7303 6FF0 8393 ADB1  398E 67F2 94AE 5995 7DD8

Processed: dpkg-dev: dpkg-shlibdeps searches paths given with -l in reverse order

[Debian Bug Tracking System]

Processing control commands:

> block 818873 with -1
Bug #818873 [src:gcc-5-cross] gcc-5-cross: FTBFS when built with 
dpkg-buildpackage -A (No such file or directory)
818873 was not blocked by any bugs.
818873 was not blocking any bugs.
Added blocking bug(s) of 818873: 823805

-- 
818873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818873
823805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#823803: libint2: FTBFS: build_libint.cc:34:34: fatal error: boost/preprocessor.hpp: No such file or directory

[Chris Lamb]

Source: libint2
Version: 2.1.0-1
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,

libint2 fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'libint2-build-deps' in 
'../libint2-build-deps_2.1.0-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package libint2-build-deps.
  (Reading database ... 23072 files and directories currently installed.)
  Preparing to unpack libint2-build-deps_2.1.0-1_all.deb ...
  Unpacking libint2-build-deps (2.1.0-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up libint2-build-deps (2.1.0-1) ...
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package libint2
  dpkg-buildpackage: info: source version 2.1.0-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Michael Banck 
   dpkg-source --before-build libint2-2.1.0
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean
 dh_testdir
 debian/rules override_dh_auto_clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0'
  dh_auto_clean
make -j1 distclean
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0'
  for dir in src tests/eri tests/hartree-fock doc tests/eri tests/hartree-fock; 
\
do \
  (cd ${dir} && make "DODEPEND=no" distclean) || exit 1; \
done
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src'
  for dir in bin lib; \
do \
  (cd ${dir} && make  distclean) || exit 1; \
done
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin'
  for dir in libint test_eri profile; \
do \
  (cd ${dir} && make  distclean) || exit 1; \
done
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin/libint'
  rm -f *.o
  rm -f libINT.a test build_libint
  rm -f *.d
  rm -f *.dot
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin/libint'
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin/test_eri'
  rm -rf generate_eri_code test_eri time_eri test_eri_rys *.o *.d *.dot *.log
  rm -rf Make.compute_eri libint2_init.cc libint2_static_init.cc 
libint2_static_cleanup.cc  libint2_init.o libint2_static_init.o 
libint2_static_cleanup.o test_eri_conf.h libint2_types.h libint2_params.h 
libint2_iface.h libint2_iface_internal.h libint2_init.h libint2_static_init.h 
libint2_static_cleanup.h 
  rm -rf run_time_eri.pl run_timing_suite.pl stdtests.pl test_eri.pl time_eri.pl
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin/test_eri'
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin/profile'
  rm -rf generate_t0g12_code profile_Gm *.o *.d
  rm -rf *.dot *.log
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin/profile'
  rm -rf MakeVars
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin'
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/lib'
  for dir in libint; \
do \
  (cd ${dir} && make  distclean) || exit 1; \
done
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/lib/libint'
  make[5]: Nothing to be done for 'distclean'.
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/lib/libint'
  rm -rf MakeRules MakeVars
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/lib'
  rm -rf libintdirlist.h
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src'
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/tests/eri'
  rm -rf test *.o *.d
  make[3]: Leaving directory 

Bug#823542: [Pkg-gmagick-im-team] Bug#823542: imagemagick-common: please mitigate CVE-2016-3714, remote arbitrary code execution during handling of delegates

[Simon McVittie]

On Mon, 09 May 2016 at 07:17:33 +, Bastien Roucaries wrote:
> Could you Walt about nmu. I have more patches...

Don't worry, I don't intend to NMU imagemagick, certainly not without
getting some sort of review from its maintainers and/or the security team.

Here is what I have so far (entirely untested). Unfortunately, it fails
to build from source, because imagemagick's own build process converts
SVG to PNG for the icons. Without Inkscape installed, that goes via
MVG format, which I've just disabled... so that won't work. You might
have to build-depend on inkscape if you go this route :-(

S
From: Simon McVittie 
Date: Mon, 9 May 2016 08:29:09 +0100
Subject: policy.xml: disable various coders to mitigate CVE-2016-3714 etc.

Bug: https://www.imagemagick.org/discourse-server/viewtopic.php?f=4=29588
Bug-CVE: CVE-2016-3714, CVE-2016-3715, CVE-2016-3717, CVE-2016-3718
Bug-Debian: https://bugs.debian.org/823542
---
 config/policy.xml | 20 
 1 file changed, 20 insertions(+)

diff --git a/config/policy.xml b/config/policy.xml
index e4908b1..36ae4ef 100644
--- a/config/policy.xml
+++ b/config/policy.xml
@@ -56,4 +56,24 @@
   
   
   
+
+  
+  
+  
+
+  
+  
+
+  
+  
+
+  
+  
+
+  
+  
+  
+  
+  
 
From: Cristy 
Date: Fri, 2 Oct 2015 18:58:28 -0400
Subject: The -caption option no longer fails for filenames with @ prefix

(cherry picked from commit 89ce096de81428c1b15b44ec97eb5a7c7d4e0f8b to be
able to apply the CVE-2016-3714 patch)

Bug-Debian: https://bugs.debian.org/823542
---
 magick/property.c | 25 +++--
 1 file changed, 11 insertions(+), 14 deletions(-)

diff --git a/magick/property.c b/magick/property.c
index 545cb6f..36c3aab 100644
--- a/magick/property.c
+++ b/magick/property.c
@@ -3254,13 +3254,13 @@ MagickExport char *InterpretImageProperties(const ImageInfo *image_info,
 *interpret_text;
 
   register char
-*q; /* current position in interpret_text */
+*q;  /* current position in interpret_text */
 
   register const char
-*p; /* position in embed_text string being expanded */
+*p;  /* position in embed_text string being expanded */
 
   size_t
-extent; /* allocated length of interpret_text */
+extent;  /* allocated length of interpret_text */
 
   MagickBooleanType
 number;
@@ -3271,22 +3271,19 @@ MagickExport char *InterpretImageProperties(const ImageInfo *image_info,
 (void) LogMagickEvent(TraceEvent,GetMagickModule(),"%s",image->filename);
 
   if (embed_text == (const char *) NULL)
-return((char *) NULL);
+return(ConstantString(""));
   p=embed_text;
 
   if (*p == '\0')
 return(ConstantString(""));
 
-  /* handle a '@' replace string from file */
-  if (*p == '@') {
- p++;
- if (*p != '-' && (IsPathAccessible(p) == MagickFalse) ) {
-   (void) ThrowMagickException(>exception,GetMagickModule(),
-   OptionError,"UnableToAccessPath","%s",p);
-   return((char *) NULL);
- }
- return(FileToString(p,~0UL,>exception));
-  }
+  if ((*p == '@') && (IsPathAccessible(p+1) != MagickFalse))
+{ 
+  /* handle a '@' replace string from file */
+  interpret_text=FileToString(p+1,~0UL,>exception);
+  if (interpret_text != (char *) NULL)
+return(interpret_text);
+}
 
   /*
 Translate any embedded format characters.
From: Cristy 
Date: Sat, 30 Apr 2016 14:56:34 -0400
Subject: Indirect filename must be authorized by policy

(cherry picked from commit 25040d1c8e48c0586297159bf9756a21e857a549)

Bug: https://www.imagemagick.org/discourse-server/viewtopic.php?f=4=29588
Bug-CVE: CVE-2016-3714
Bug-Debian: https://bugs.debian.org/823542
---
 magick/property.c | 15 +++
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/magick/property.c b/magick/property.c
index 36c3aab..bd28b98 100644
--- a/magick/property.c
+++ b/magick/property.c
@@ -67,6 +67,7 @@
 #include "magick/monitor.h"
 #include "magick/montage.h"
 #include "magick/option.h"
+#include "magick/policy.h"
 #include "magick/profile.h"
 #include "magick/property.h"
 #include "magick/quantum.h"
@@ -3273,18 +3274,24 @@ MagickExport char *InterpretImageProperties(const ImageInfo *image_info,
   if (embed_text == (const char *) NULL)
 return(ConstantString(""));
   p=embed_text;
-
+  while ((isspace((int) ((unsigned char) *p)) != 0) && (*p != '\0'))
+p++;
   if (*p == '\0')
 return(ConstantString(""));
-
   if ((*p == '@') && (IsPathAccessible(p+1) != MagickFalse))
-{ 
+{
   /* handle a '@' replace string from file */
+  if (IsRightsAuthorized(PathPolicyDomain,ReadPolicyRights,p) == MagickFalse)
+{
+  errno=EPERM;
+  (void) ThrowMagickException(>exception,GetMagickModule(),
+PolicyError,"NotAuthorized","`%s'",p);
+  return(ConstantString(""));
+}
   interpret_text=FileToString(p+1,~0UL,>exception);
   if (interpret_text 

Bug#785923: marked as done (sugar-pippy-activity: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Mon, 09 May 2016 10:35:37 +0200
with message-id <146278293764.13240.7472026547146884...@auryn.jones.dk>
and subject line Re: [Debian-olpc-devel] Bug#785923: sugar-pippy-activity: 
Please update to GStreamer 1.x
has caused the Debian Bug report #785923,
regarding sugar-pippy-activity: Please update to GStreamer 1.x
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
785923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sugar-pippy-activity
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package sugar-pippy-activity currently still depends on
GStreamer 0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
Version: 66-4

Quoting sl...@debian.org (2015-05-20 15:03:06)
> your package sugar-pippy-activity currently still depends on GStreamer 
> 0.10.

This was fixed in release 66-4.

Thanks for reporting!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature
--- End Message ---

Bug#818873: gcc-5-cross: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Andreas Beckmann]

Followup-For: Bug #818873

Hi,

in 
https://buildd.debian.org/status/fetch.php?pkg=gcc-5-cross=all=21=1462410260
 the failing command is 

DEB_HOST_ARCH=s390x ARCH=s390x MAKEFLAGS="CC=something" dh_shlibdeps 
-plibgnat-5-s390x-cross \

-l/lib/s390x-linux-gnu:/usr/lib/s390x-linux-gnu:/s390x-linux-gnu/lib:/usr/s390x-linux-gnu/lib:/«PKGBUILDDIR»/gcc/debian/tmp/usr/s390x-linux-gnu/lib:/«PKGBUILDDIR»/gcc/debian/tmp/usr/s390x-linux-gnu/lib
dpkg-shlibdeps: error: no dependency information found for 
/«PKGBUILDDIR»/gcc/debian/tmp/usr/s390x-linux-gnu/lib/libgcc_s.so.1 (used by 
debian/libgnat-5-s390x-cross/usr/s390x-linux-gnu/lib/libgnarl-5.so.1)
Hint: check if the library actually comes from a package.
dh_shlibdeps: dpkg-shlibdeps -Tdebian/libgnat-5-s390x-cross.substvars 
-l/lib/s390x-linux-gnu -l/usr/lib/s390x-linux-gnu -l/s390x-linux-gnu/lib 
-l/usr/s390x-linux-gnu/lib 
-l/«PKGBUILDDIR»/gcc/debian/tmp/usr/s390x-linux-gnu/lib 
-l/«PKGBUILDDIR»/gcc/debian/tmp/usr/s390x-linux-gnu/lib 
debian/libgnat-5-s390x-cross/usr/s390x-linux-gnu/lib/libgnat-5.so.1 
debian/libgnat-5-s390x-cross/usr/s390x-linux-gnu/lib/libgnarl-5.so.1 returned 
exit code 2

That's actually in the gcc source code being built by gcc-5-cross.
This call looks correct and there is also a
/usr/s390x-linux-gnu/lib/libgcc_s.so.1 available.
But if you dig into dpkg-shlibdeps source code, you see that the -l option
works rather counterintuitive. The -l paths get prepended to the list of
(default) search paths one-by-one, so that the last -l option gets actually
searched first.

I'm not sure who should be blamed here: dpkg, debhelper or gcc.
Neither dpkg-shlibdeps nor dh_shlibdeps document anything about the order
in their manpages.
Why is /«PKGBUILDDIR»/gcc/debian/tmp/usr/s390x-linux-gnu/lib included in
the search path anyway? AIUI if some library can (only) be satisfied from
there, dpkg-shlibdeps will always fail.

I could reproduce this in a sid/amd64 for an arch-indep build. (didn't verify
what is different in a full arch+indep build since this seems to take extremely
long). Changing the search path order lets this command succeed.


Andreas

Bug#823748: tar: illegal hardware instruction breaks apt-get upgrade

[Lee Garrett]

Hi Dirk,

which type of processor do you have on that machine? As ydirson pointed out,
older CPU types (80586 and below on the i386 architecture) are not supported
anymore in stretch.

For everyone else: I can't reproduce this bug on my Intel i5, so it's safe to
upgrade.

Regards,
Lee