Bug#796611: marked as done (ferm: Has init script in runlevel S but no matching service file)
Your message dated Sat, 23 Apr 2016 06:05:00 + with message-id and subject line Bug#796611: fixed in ferm 2.2-5 has caused the Debian Bug report #796611, regarding ferm: Has init script in runlevel S but no matching service file 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.) -- 796611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ferm Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: init-rcs-service Hi, Your package ferm has an initscript that is enabled in runlevel S, but it does not provide a corresponding systemd service unit. Systemd generates units for all sysv init scripts that do not have a corresponding systemd unit. By default, it sets DefaultDependencies=yes, which means they get ordered after early boot has finished. The problem is that to preserve the runlevel S semantics, systemd in debian is currently[1] ordering all S services Before=sysinit.target. This target is particularly early in the boot sequence, which means that it is most of the time too strict. In turn, this means it is fairly easy to end up with dependency cycles. For an example, see bug [763315]. Do note that the cycle still exists with sysvinit, it is just that systemd complains more loudly. Please add a systemd unit for the given service with the appropriate dependencies, which most of the time will be less strict than Before=sysinit.target. In other cases, the script is simply not applicable in systemd, in which case the package should ship a symlink to /dev/null as /lib/systemd/system/.service. We have prepared a transition wiki page[2] explaining the issue in more detail, and outlining some general guidance. Please refer to it as it will have useful information. If you have any other doubts, feel free to ask in pkg-systemd-maintain...@lists.alioth.debian.org -- [1] http://sources.debian.net/src/systemd/222-2/debian/patches/Add-support-for-rcS.d-init-scripts-to-the-sysv-gener.patch/ [763315] https://bugs.debian.org/763315 [2] https://wiki.debian.org/Teams/pkg-systemd/rcSMigration --- End Message --- --- Begin Message --- Source: ferm Source-Version: 2.2-5 We believe that the bug you reported is fixed in the latest version of ferm, 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 796...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander Wirt (supplier of updated ferm 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: SHA1 Format: 1.8 Date: Sat, 23 Apr 2016 07:54:53 +0200 Source: ferm Binary: ferm Architecture: source all Version: 2.2-5 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt Changed-By: Alexander Wirt Description: ferm - maintain and setup complicated firewall rules Closes: 796611 Changes: ferm (2.2-5) unstable; urgency=medium . * Reimport changes from 2.2-3.2 Closes: #796611 Checksums-Sha1: 500d9f90756e647173a20699f7c86bbe55e69847 1756 ferm_2.2-5.dsc 4de9c73cacc7c9a28e170f7284ed7a3fbb2db0de 15853 ferm_2.2-5.diff.gz 218ba493e840306ca1f9a1c1a72b6168df032681 105202 ferm_2.2-5_all.deb Checksums-Sha256: 29b68eb167e64844075dfc6ce65af93d202137e5dd4c5fa98f2b54edc9744b31 1756 ferm_2.2-5.dsc e69512a5cf049f4cbdacd7155d4958ac59c4864315ea15f09c483f75aa3646fc 15853 ferm_2.2-5.diff.gz 429790acb8b693e7689b121070a9e81f5a234def3780eb916e1092d21cf132da 105202 ferm_2.2-5_all.deb Files: edad9a20de6b4b14afb44f6b69d3894d 1756 net optional ferm_2.2-5.dsc fb8371b991ce7dcb176a6910b6d4b5a2 15853 net optional ferm_2.2-5.diff.gz 38e0e4143a76e1e86a51bac070b60987 105202 net optional ferm_2.2-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJXGw7kAAoJEB5F+Mqd4jsWeWwP/icapL/ZxCX5xR1c6mZ/TGVl k43Lx6Nv9XMZrHkt5PwDK8XyNST7U9ixRAw43jb5WfVkFwuLZ5emzCM6qnvKWdiJ LAun3VIZ4v8LmhAAFrUcUShlGq+IjAss4w3toK5K2ALGbpd29Rbk+LN3k73Fe9CP A7Mllrb7stcvnnQSObxfqhcOLUG6AyPs3RqUfT4yP7LUfppLxX6eFySTWWecajIQ Usj4jCbwH9gqcauAN3KqmlpQYFJKyctkU+vJJoG1m+NUMU4vrjT1+bzULf6W8oxn zRGigP6WarVWr08aszrhHxQN5d39mifABKkCy+0+F3onisMZBM/ub4h9cb2Rq/GW FYSHWAEkSIplpkUXJZDXQidOHP4DttXJjoGqRNNT/2s09gz6uTL9h+vbz2/
Bug#800309: gkrellm-radio: Please migrate a supported debhelper compat level
Package: gkrellm-radio
Version: 2.0.4-1.1
Followup-For: Bug #800309
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* debian/rules:
- Remove legacy DH_COMPAT export.
- Don't allow $(MAKE) clean to ignore errors.
- Replace dh_clean -k with dh_prep.
* debian/compat: Specify compatibility level of 9.
* debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.
Thanks for considering the patch.
Logan Rosen
-- System Information:
Debian Release: stretch/sid
APT prefers xenial-updates
APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500,
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.0-18-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u gkrellm-radio-2.0.4/debian/control gkrellm-radio-2.0.4/debian/control
--- gkrellm-radio-2.0.4/debian/control
+++ gkrellm-radio-2.0.4/debian/control
@@ -2,14 +2,14 @@
Section: sound
Priority: optional
Maintainer: Sjoerd Simons
-Build-Depends: debhelper (>> 3.0.0), liblircclient-dev, gkrellm (>= 2.0.0), libgtk2.0-dev
+Build-Depends: debhelper (>= 9), liblircclient-dev, gkrellm (>= 2.0.0), libgtk2.0-dev
Standards-Version: 3.5.7
Package: gkrellm-radio
Architecture: any
Replaces: gkrellm-radio2
Conflicts: gkrellm-radio2
-Depends: gkrellm (>> 2.0.0), ${shlibs:Depends}
+Depends: ${misc:Depends}, gkrellm (>> 2.0.0), ${shlibs:Depends}
Description: FM radio tuner for GKrellM
A gkrellm plugin to control radio tuners on linux. It allows you to define
and jump between a number of radio stations. With a mouse wheel you can dial
diff -u gkrellm-radio-2.0.4/debian/rules gkrellm-radio-2.0.4/debian/rules
--- gkrellm-radio-2.0.4/debian/rules
+++ gkrellm-radio-2.0.4/debian/rules
@@ -7,9 +7,6 @@
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
-# This is the debhelper compatability version to use.
-export DH_COMPAT=3
-
configure: configure-stamp
configure-stamp:
dh_testdir
@@ -31,14 +28,14 @@
rm -f build-stamp configure-stamp
# Add here commands to clean up after the build process.
- -enable_nls=1 WITH_LIRC=1 $(MAKE) clean
+ enable_nls=1 WITH_LIRC=1 $(MAKE) clean
dh_clean
install: build
dh_testdir
dh_testroot
- dh_clean -k
+ dh_prep
dh_installdirs
enable_nls=1 WITH_LIRC=1 $(MAKE) install \
only in patch2:
unchanged:
--- gkrellm-radio-2.0.4.orig/debian/compat
+++ gkrellm-radio-2.0.4/debian/compat
@@ -0,0 +1 @@
+9
Bug#800297: gkrellm-mailwatch: Please migrate a supported debhelper compat level
Package: gkrellm-mailwatch
Version: 2.4.3-1
Followup-For: Bug #800297
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* debian/rules:
- Remove legacy DH_COMPAT export.
- Don't allow $(MAKE) clean to ignore errors.
- Replace dh_clean -k with dh_prep.
* debian/compat: Specify compatibility level of 9.
* debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.
Thanks for considering the patch.
Logan Rosen
-- System Information:
Debian Release: stretch/sid
APT prefers xenial-updates
APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500,
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.0-18-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u gkrellm-mailwatch-2.4.3/debian/control gkrellm-mailwatch-2.4.3/debian/control
--- gkrellm-mailwatch-2.4.3/debian/control
+++ gkrellm-mailwatch-2.4.3/debian/control
@@ -1,7 +1,7 @@
Source: gkrellm-mailwatch
Section: mail
Priority: optional
-Build-Depends: debhelper, gkrellm (>= 2.0.0), libgtk2.0-dev
+Build-Depends: debhelper (>= 9), gkrellm (>= 2.0.0), libgtk2.0-dev
Maintainer: Sjoerd Simons
Standards-Version: 3.1.1
@@ -9,7 +9,7 @@
Architecture: any
Replaces: gkrellm-mailwatch2
Conflicts: gkrellm-mailwatch2
-Depends: gkrellm (>= 2.0.0), ${shlibs:Depends}
+Depends: ${misc:Depends}, gkrellm (>= 2.0.0), ${shlibs:Depends}
Description: GKrellM plugin to watch mailboxes in multiple panels
A GKrellM plugin to monitor mbox, maildir and MH style mailboxes in
multiple gkrellm panels.
diff -u gkrellm-mailwatch-2.4.3/debian/rules gkrellm-mailwatch-2.4.3/debian/rules
--- gkrellm-mailwatch-2.4.3/debian/rules
+++ gkrellm-mailwatch-2.4.3/debian/rules
@@ -5,8 +5,6 @@
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
-# This is the debhelper compatability version to use.
-export DH_COMPAT=3
ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
@@ -39,14 +37,14 @@
rm -f build-stamp configure-stamp
# Add here commands to clean up after the build process.
- -$(MAKE) clean
+ $(MAKE) clean
dh_clean
install: build
dh_testdir
dh_testroot
- dh_clean -k
+ dh_prep
dh_installdirs
# Add here commands to install the package into debian/tmp.
only in patch2:
unchanged:
--- gkrellm-mailwatch-2.4.3.orig/debian/compat
+++ gkrellm-mailwatch-2.4.3/debian/compat
@@ -0,0 +1 @@
+9
Bug#800215: gkrellkam: Please migrate a supported debhelper compat level
Package: gkrellkam
Version: 2.0.0-1.1
Followup-For: Bug #800215
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* debian/rules:
- Remove legacy DH_COMPAT export.
- Replace dh_clean -k with dh_prep.
- Don't allow $(MAKE) clean to ignore errors.
* debian/compat: Indicate compatibility level of 9.
* debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.
Thanks for considering the patch.
Logan Rosen
-- System Information:
Debian Release: stretch/sid
APT prefers xenial-updates
APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500,
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.0-18-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u gkrellkam-2.0.0/debian/rules gkrellkam-2.0.0/debian/rules
--- gkrellkam-2.0.0/debian/rules
+++ gkrellkam-2.0.0/debian/rules
@@ -5,9 +5,6 @@
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
-# This is the debhelper compatability version to use.
-export DH_COMPAT=3
-
configure: configure-stamp
configure-stamp:
dh_testdir
@@ -30,14 +27,14 @@
rm -f build-stamp configure-stamp
# Add here commands to clean up after the build process.
- -$(MAKE) clean
+ $(MAKE) clean
dh_clean
install: build
dh_testdir
dh_testroot
- dh_clean -k
+ dh_prep
dh_installdirs
# Add here commands to install the package into debian/gkrellkam.
diff -u gkrellkam-2.0.0/debian/control gkrellkam-2.0.0/debian/control
--- gkrellkam-2.0.0/debian/control
+++ gkrellkam-2.0.0/debian/control
@@ -2,12 +2,12 @@
Section: x11
Priority: optional
Maintainer: paul cannon
-Build-Depends: debhelper (>> 3.0.0), gkrellm (>= 2.0.0), libgtk2.0-dev, libglib2.0-dev
+Build-Depends: debhelper (>= 9), gkrellm (>= 2.0.0), libgtk2.0-dev, libglib2.0-dev
Standards-Version: 3.5.8
Package: gkrellkam
Architecture: any
-Depends: gkrellm (>= 2.0.0), ${shlibs:Depends}
+Depends: ${misc:Depends}, gkrellm (>= 2.0.0), ${shlibs:Depends}
Recommends: wget
Description: GKrellM plugin that displays a periodically updating image
GKrellKam is basically wmGrabImage in a GKrellM panel, except that it
only in patch2:
unchanged:
--- gkrellkam-2.0.0.orig/debian/compat
+++ gkrellkam-2.0.0/debian/compat
@@ -0,0 +1 @@
+9
Bug#800226: python-imaging-doc-handbook: Please migrate a supported debhelper compat level
Package: python-imaging-doc-handbook
Version: 1.1.2-1.1
Followup-For: Bug #800226
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* debian/rules: Remove legacy DH_COMPAT export.
* debian/compat: Indicate compatibility level of 9.
* debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.
Thanks for considering the patch.
Logan Rosen
-- System Information:
Debian Release: stretch/sid
APT prefers xenial-updates
APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500,
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.0-18-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u python-imaging-doc-handbook-1.1.2/debian/control python-imaging-doc-handbook-1.1.2/debian/control
--- python-imaging-doc-handbook-1.1.2/debian/control
+++ python-imaging-doc-handbook-1.1.2/debian/control
@@ -2,11 +2,12 @@
Section: doc
Priority: optional
Maintainer: Simon Richter
-Build-Depends: debhelper (>> 3.0.0)
+Build-Depends: debhelper (>= 9)
Standards-Version: 3.5.2
Package: python-imaging-doc-html
Architecture: all
+Depends: ${misc:Depends}
Description: Documentation for the Python Imaging Library.
The Python Imaging Library (PIL) adds an image object to your
Python interpreter. You can load image objects from a variety of file
@@ -16,6 +17,7 @@
Package: python-imaging-doc-pdf
Architecture: all
+Depends: ${misc:Depends}
Suggests: pdf-viewer
Description: Documentation for the Python Imaging Library.
The Python Imaging Library (PIL) adds an image object to your
diff -u python-imaging-doc-handbook-1.1.2/debian/rules python-imaging-doc-handbook-1.1.2/debian/rules
--- python-imaging-doc-handbook-1.1.2/debian/rules
+++ python-imaging-doc-handbook-1.1.2/debian/rules
@@ -5,9 +5,6 @@
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
-# This is the debhelper compatability version to use.
-export DH_COMPAT=3
-
configure:
# Nothing to do
@@ -23,7 +20,7 @@
install: build
dh_testdir
dh_testroot
- dh_clean -k
+ dh_prep
dh_installdirs
for i in *.htm *.css *.gif; do \
only in patch2:
unchanged:
--- python-imaging-doc-handbook-1.1.2.orig/debian/compat
+++ python-imaging-doc-handbook-1.1.2/debian/compat
@@ -0,0 +1 @@
+9
Bug#800308: gkrellmwireless: Please migrate a supported debhelper compat level
Package: gkrellmwireless
Version: 2.0.3-1
Followup-For: Bug #800308
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* debian/rules:
- Remove legacy DH_COMPAT export.
- Don't allow $(MAKE) clean to ignore errors.
- Replace dh_clean -k with dh_prep.
* debian/compat: Indicate compatibility level of 9.
* debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.
Thanks for considering the patch.
Logan Rosen
-- System Information:
Debian Release: stretch/sid
APT prefers xenial-updates
APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500,
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.0-18-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u gkrellmwireless-2.0.3/debian/control gkrellmwireless-2.0.3/debian/control
--- gkrellmwireless-2.0.3/debian/control
+++ gkrellmwireless-2.0.3/debian/control
@@ -1,7 +1,7 @@
Source: gkrellmwireless
Section: x11
Priority: optional
-Build-Depends: debhelper (>> 3.0.0), gkrellm (>= 2.0.0), libgtk2.0-dev
+Build-Depends: debhelper (>= 9), gkrellm (>= 2.0.0), libgtk2.0-dev
Maintainer: Sjoerd Simons
Standards-Version: 3.5.7
@@ -9,7 +9,7 @@
Conflicts: gkrellmwireless2
Replaces: gkrellmwireless2
Architecture: any
-Depends: gkrellm (>= 2.0.0), ${shlibs:Depends}
+Depends: ${misc:Depends}, gkrellm (>= 2.0.0), ${shlibs:Depends}
Description: 802.11 wireless link monitor plugin for GKrellM
This GKrellM plugin allows you to monitor the status of an 802.11 wireless
ethernet link.
diff -u gkrellmwireless-2.0.3/debian/rules gkrellmwireless-2.0.3/debian/rules
--- gkrellmwireless-2.0.3/debian/rules
+++ gkrellmwireless-2.0.3/debian/rules
@@ -5,9 +5,6 @@
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
-# This is the debhelper compatability version to use.
-export DH_COMPAT=3
-
ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
CFLAGS += -g
endif
@@ -33,13 +30,13 @@
rm -f build-stamp configure-stamp
# Add here commands to clean up after the build process.
- -$(MAKE) clean
+ $(MAKE) clean
dh_clean
install: build
dh_testdir
dh_testroot
- dh_clean -k
+ dh_prep
dh_installdirs
# Add here commands to install the package into debian/tmp.
only in patch2:
unchanged:
--- gkrellmwireless-2.0.3.orig/debian/compat
+++ gkrellmwireless-2.0.3/debian/compat
@@ -0,0 +1 @@
+9
Bug#821154: marked as done (chromium: crashes on video)
Your message dated Sat, 23 Apr 2016 04:02:57 +
with message-id
and subject line Bug#821154: fixed in chromium-browser 50.0.2661.75-2
has caused the Debian Bug report #821154,
regarding chromium: crashes on video
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.)
--
821154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 50.0.2661.75-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Upgraded chromium from 49.0.2623.108-1
* What exactly did you do (or not do) that was effective (or
ineffective)?
Opened up vimeo.com, or file:// {...}.m4v also does the trick
Tried this also with a blank user profile.
* What was the outcome of this action?
An "aw snap" page, and this:
[6272:6299:0416/013127:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust
OOM score of renderer with pid 6324: Permission denied
[6321:6321:0416/013127:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called
with multiple threads in process gpu-process
[6272:6299:0416/013134:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust
OOM score of renderer with pid 6356: Permission denied
Received signal 11 SEGV_MAPERR 002e6800
#0 0x555b3c305b2e
#1 0x555b3c305ee9
#2 0x7fed39df8d30
#3 0x555b3f66ff26
#4 0x555b3f670036
#5 0x555b4052b076
#6 0x555b40516cf1
#7 0x555b40516f41
#8 0x555b40512b4d
#9 0x555b3c36b0ad
#10 0x555b3c322f69
#11 0x555b3c323a7d
#12 0x555b3c323d48
#13 0x555b3c3257e9
#14 0x555b3c339878
#15 0x555b3c322205
#16 0x555b3c35179a
#17 0x555b3c34ddad
#18 0x7fed39def454 start_thread
#19 0x7fed39b2cecd clone
r8: 7fed04003750 r9: 555b3ccfbad0 r10: 7fed0400bfe0 r11:
r12: 7fed04003d58 r13: 555b41930702 r14: 7fed1cf2a320 r15:
555b41239d71
di: 002e6800 si: 555b41930702 bp: bx:
002e6800
dx: ax: cx: sp:
7fed1cf2a260
ip: 555b3f66ff26 efl: 00010246 cgf: 0033 erf:
0004
trp: 000e msk: cr2: 002e6800
[end of stack trace]
-- System Information:
Debian Release: stretch/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.5.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages chromium depends on:
ii libasound2 1.1.0-1
ii libatk1.0-0 2.20.0-1
ii libc62.22-6
ii libcairo21.14.6-1+b1
ii libcups2 2.1.3-5
ii libdbus-1-3 1.10.8-1
ii libexpat12.1.1-1
ii libfontconfig1 2.11.0-6.4
ii libfreetype6 2.6.3-3+b1
ii libgcc1 1:5.3.1-14
ii libgdk-pixbuf2.0-0 2.32.3-2
ii libglib2.0-0 2.48.0-1
ii libgnome-keyring03.12.0-1+b1
ii libgtk2.0-0 2.24.30-1.1
ii libjpeg62-turbo 1:1.4.2-2
ii libnspr4 2:4.12-2
ii libnss3 2:3.23-2
ii libnss3-1d 2:3.23-2
ii libpango-1.0-0 1.38.1-1
ii libpangocairo-1.0-0 1.38.1-1
ii libpci3 1:3.3.1-1.1
ii libspeechd2 0.8-7
ii libstdc++6 5.3.1-14
ii libx11-6 2:1.6.3-1
ii libxcomposite1 1:0.4.4-1
ii libxcursor1 1:1.1.14-1+b1
ii libxdamage1 1:1.1.4-2+b1
ii libxext6 2:1.3.3-1
ii libxfixes3 1:5.0.1-2+b2
ii libxi6 2:1.7.6-1
ii libxml2 2.9.3+dfsg1-1
ii libxrandr2 2:1.5.0-1
ii libxrender1 1:0.9.9-2
ii libxslt1.1 1.1.28-2.1
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.2-1+b1
ii x11-utils7.7+3
ii xdg-utils1.1.1-1
Versions of packages chromium recommends:
ii fonts-liberation 1.07.4-1
Versions of packages chromium suggests:
pn chromium-l10n
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 50.0.2661.75-2
We believe that the bug you reported is fixed in the latest version of
chromium-browser, 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 t
Bug#821931: marked as done (chromium: Hangout crash regullary)
Your message dated Sat, 23 Apr 2016 04:02:57 + with message-id and subject line Bug#821154: fixed in chromium-browser 50.0.2661.75-2 has caused the Debian Bug report #821154, regarding chromium: Hangout crash regullary 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.) -- 821154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 50.0.2661.75-1 Severity: normal Dear Maintainer, Hangout crash with the following output: Apr 20 16:55:41 k-c13 chromium.desktop[9296]: [9296:9331:0420/165541:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 12203: Permission denied Apr 20 16:55:47 k-c13 chromium.desktop[9296]: Received signal 11 SEGV_MAPERR 002e6800 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #0 0x55ef4c683b2e Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #1 0x55ef4c683ee9 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #2 0x7f60b8b9eec0 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #3 0x55ef4f9edf26 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #4 0x55ef4f9ee036 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #5 0x55ef508a9076 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #6 0x55ef50894cf1 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #7 0x55ef50894f41 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #8 0x55ef50890b4d Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #9 0x55ef4c6e90ad Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #10 0x55ef4c6a0f69 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #11 0x55ef4c6a1a7d Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #12 0x55ef4c6a1d48 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #13 0x55ef4c6a37e9 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #14 0x55ef4c6b7878 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #15 0x55ef4c6a0205 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #16 0x55ef4c6cf79a Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #17 0x55ef4c6cbdad Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #18 0x7f60b8b95454 start_thread Apr 20 16:55:47 k-c13 chromium.desktop[9296]: #19 0x7f60b88d478d clone Apr 20 16:55:47 k-c13 chromium.desktop[9296]: r8: 55ef5543c160 r9: 55ef4d079ad0 r10: 55ef55449920 r11: Apr 20 16:55:47 k-c13 chromium.desktop[9296]: r12: 55ef5544a7b8 r13: 55ef51cae702 r14: 7f6094bf7320 r15: 55ef515b7d71 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: di: 002e6800 si: 55ef51cae702 bp: bx: 002e6800 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: dx: ax: cx: sp: 7f6094bf7260 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: ip: 55ef4f9edf26 efl: 00010246 cgf: 0033 erf: 0004 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: trp: 000e msk: cr2: 002e6800 Apr 20 16:55:47 k-c13 chromium.desktop[9296]: [end of stack trace] I hope that it helps. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (700, 'unstable'), (650, 'testing'), (600, 'stable'), (500, 'stable-updates'), (500, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chromium depends on: ii libasound2 1.1.0-1 ii libatk1.0-0 2.20.0-1 ii libc62.23-0experimental2 ii libcairo21.14.6-1+b1 ii libcups2 2.1.3-5 ii libdbus-1-3 1.11.2-1 ii libexpat12.1.1-1 ii libfontconfig1 2.11.0-6.4 ii libfreetype6 2.6.3-3+b1 ii libgcc1 1:6.0.1-1 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libglib2.0-0 2.48.0-1 ii libgnome-keyring03.12.0-1+b1 ii libgtk2.0-0 2.24.30-1.1 ii libjpeg62-turbo 1:1.4.80-115-gfb907b2-1 ii libnspr4 2:4.12-2 ii libnss3 2:3.23-2 ii libpango-1.0-0 1.40.1-1 ii libpangocairo-1.0-0 1.40.1-1 ii libpci3 1:3.3.1-1.1 ii libspeechd2 0.8.3-1 ii libstdc++6 6.0.1-1 ii libx11-6 2:1.6.3-1 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1+b1 ii libxdamage1 1:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.1-2+b2 ii libxi6 2:1.7.6-1 ii libxml2 2.9.3+dfsg1-1 ii libxrandr2 2:1.5.0
Bug#821463: marked as done (chromium: frequent SEGV_MAPERR)
Your message dated Sat, 23 Apr 2016 04:02:57 + with message-id and subject line Bug#821154: fixed in chromium-browser 50.0.2661.75-2 has caused the Debian Bug report #821154, regarding chromium: frequent SEGV_MAPERR 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.) -- 821154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 50.0.2661.75-1 Severity: important Dear Maintainer, While surfing with chromium on gmail or youtube, after following a few links, chromium throw an "Aw Snap!" error. (the number of links followed is not always the same, but it happens rapidly, like ~5 clicks). I get the following trace in stderr: [4390:4420:0418/214831:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 4496: Permission denied [4390:4420:0418/214835:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 4527: Permission denied Received signal 11 SEGV_MAPERR 002e6800 #0 0x55a04ba10b2e #1 0x55a04ba10ee9 #2 0x7ff34b695d30 #3 0x55a04ed7af26 #4 0x55a04ed7b036 #5 0x55a04fc36076 #6 0x55a04fc21cf1 #7 0x55a04fc21f41 #8 0x55a04fc1db4d #9 0x55a04ba760ad #10 0x55a04ba2df69 #11 0x55a04ba2ea7d #12 0x55a04ba2ed48 #13 0x55a04ba307e9 #14 0x55a04ba44878 #15 0x55a04ba2d205 #16 0x55a04ba5c79a #17 0x55a04ba58dad #18 0x7ff34b68c454 start_thread #19 0x7ff34b3c9ecd clone r8: 7ff3200049e0 r9: 55a04c406ad0 r10: 7ff320004b20 r11: r12: 7ff320005ed8 r13: 55a05103b702 r14: 7ff31daf9320 r15: 55a050944d71 di: 002e6800 si: 55a05103b702 bp: bx: 002e6800 dx: ax: cx: sp: 7ff31daf9260 ip: 55a04ed7af26 efl: 00010246 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 002e6800 [end of stack trace] The issue seems related to: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821154 But it affects more than just video. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chromium depends on: ii libasound2 1.1.0-1 ii libatk1.0-0 2.20.0-1 ii libc62.22-6 ii libcairo21.14.6-1+b1 ii libcups2 2.1.3-5 ii libdbus-1-3 1.10.8-1 ii libexpat12.1.1-1 ii libfontconfig1 2.11.0-6.4 ii libfreetype6 2.6.3-3+b1 ii libgcc1 1:5.3.1-14 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libglib2.0-0 2.48.0-1 ii libgnome-keyring03.12.0-1+b1 ii libgtk2.0-0 2.24.30-1.1 ii libjpeg62-turbo 1:1.4.2-2 ii libnspr4 2:4.12-2 ii libnss3 2:3.23-2 ii libnss3-1d 2:3.23-2 ii libpango-1.0-0 1.40.1-1 ii libpangocairo-1.0-0 1.40.1-1 ii libpci3 1:3.3.1-1.1 ii libspeechd2 0.8-7 ii libstdc++6 5.3.1-14 ii libx11-6 2:1.6.3-1 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1+b1 ii libxdamage1 1:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.1-2+b2 ii libxi6 2:1.7.6-1 ii libxml2 2.9.3+dfsg1-1 ii libxrandr2 2:1.5.0-1 ii libxrender1 1:0.9.9-2 ii libxslt1.1 1.1.28-2.1 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.2-1+b1 ii x11-utils7.7+3 ii xdg-utils1.1.1-1 Versions of packages chromium recommends: ii fonts-liberation 1.07.4-1 Versions of packages chromium suggests: pn chromium-l10n -- no debconf information --- End Message --- --- Begin Message --- Source: chromium-browser Source-Version: 50.0.2661.75-2 We believe that the bug you reported is fixed in the latest version of chromium-browser, 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. M
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forcemerge 821154 821463 Bug #821154 [chromium] chromium: crashes on video Bug #821463 [chromium] chromium: frequent SEGV_MAPERR Severity set to 'grave' from 'important' Added tag(s) patch, confirmed, and help. Merged 821154 821463 > forcemerge 821154 821931 Bug #821154 [chromium] chromium: crashes on video Bug #821463 [chromium] chromium: frequent SEGV_MAPERR Bug #821931 [chromium] chromium: Hangout crash regullary Severity set to 'grave' from 'normal' Added tag(s) help, confirmed, and patch. Bug #821463 [chromium] chromium: frequent SEGV_MAPERR Merged 821154 821463 821931 > severity 822158 minor Bug #822158 [chromium] chromium: Display:table height issue breaks some web pages Severity set to 'minor' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 821154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821154 821463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821463 821931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821931 822158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#822293: password-gorilla: Cannot save new passwords
Package: password-gorilla
Version: 1.5.3.7-1
Severity: grave
I have recently been unable to save new entries in Password Gorilla. I
get an error about not being able to run ifconfig. This occurs because
Password Gorilla uses the Tcl package uuid which way deep inside calls
ifconfig (full stack below). On my Debian unstable system, the ifconfig
program is located in /sbin which is not in my PATH as a non-root user.
There are some workarounds:
* Add /sbin to your PATH (not a great idea)
* Create a symbolic link from /sbin/ifconfig to a directory in your PATH.
* Create a shell script in your PATH called ifconfig that does something
similar, like call "ip a" or "hostname -I". I don't really know what the
Tcl uuid package requires from ifconfig, so it is difficult to say what
is an appropriate substitute, but this worked for me.
Possible solutions:
* Change Password Gorilla to use some other method for generating UUIDs.
* Change the Tcl uuid package not to use ifconfig.
I set the severity to grave because this prevents saving password
entries which is the core function of Password Gorilla.
Error message stack:
couldn't execute "ifconfig": no such file or directory
couldn't execute "ifconfig": no such file or directory
while executing
"exec ifconfig"
(procedure "dump" line 2)
invoked from within
"dump"
(procedure "::nettool::mac_list" line 3)
invoked from within
"::nettool::mac_list"
(procedure "::nettool::hwid_list" line 3)
invoked from within
"::nettool::hwid_list"
(procedure "generate_tcl_machinfo" line 36)
invoked from within
"generate_tcl_machinfo"
(procedure "generate_tcl" line 7)
invoked from within
"generate_tcl"
(procedure "generate" line 6)
invoked from within
"generate"
(procedure "uuid::uuid" line 7)
invoked from within
"uuid::uuid generate"
(procedure "PopulateRecord" line 20)
invoked from within
"PopulateRecord [ set newrn [ $::gorilla::db createRecord ] ] "
(procedure "Ok" line 30)
invoked from within
"Ok"
(in namespace inscope "::gorilla::LoginDialog::0" script line 1)
invoked from within
"namespace inscope ::gorilla::LoginDialog::0 Ok"
invoked from within
".nmLoginDialog0.bf.top.ok invoke "
invoked from within
".nmLoginDialog0.bf.top.ok instate !disabled { .nmLoginDialog0.bf.top.ok
invoke } "
invoked from within
".nmLoginDialog0.bf.top.ok instate pressed { .nmLoginDialog0.bf.top.ok
state !pressed; .nmLoginDialog0.bf.top.ok instate !disabled {
.nmLoginDialog0.bf..."
(command bound to event)
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages password-gorilla depends on:
ii itcl3 3.4.3-1
ii tcl8.5 8.5.19-2
ii tcllib 1.18-dfsg-2
ii tk8.5 8.5.19-1
ii tklib 0.6-3
password-gorilla recommends no packages.
password-gorilla suggests no packages.
-- no debconf information
--
Neil Roeth
Bug#822274: marked as done (golang-github-hpcloud-tail: FTBFS in unstable: cannot find package "golang.org/x/sys/unix")
Your message dated Fri, 22 Apr 2016 23:25:26 + with message-id and subject line Bug#822274: fixed in golang-github-hpcloud-tail 1.0.0+git20160415.b294095-2 has caused the Debian Bug report #822274, regarding golang-github-hpcloud-tail: FTBFS in unstable: cannot find package "golang.org/x/sys/unix" 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.) -- 822274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: golang-github-hpcloud-tail Version: 1.0.0+git20160415.b294095-1 Severity: serious Dear maintainer: This package fails to build from source in unstable: -- go install -v github.com/hpcloud/tail github.com/hpcloud/tail/cmd/gotail github.com/hpcloud/tail/ratelimiter github.com/hpcloud/tail/util github.com/hpcloud/tail/watch src/gopkg.in/fsnotify.v1/inotify.go:19:2: cannot find package "golang.org/x/sys/unix" in any of: /usr/lib/go/src/golang.org/x/sys/unix (from $GOROOT) /<>/golang-github-hpcloud-tail-1.0.0+git20160415.b294095/obj-x86_64-linux-gnu/src/golang.org/x/sys/unix (from $GOPATH) dh_auto_build: go install -v github.com/hpcloud/tail github.com/hpcloud/tail/cmd/gotail github.com/hpcloud/tail/ratelimitr github.com/hpcloud/tail/util github.com/hpcloud/tail/watch returned exit code 1 -- The build was made on a virtual machine running stretch with sbuild and a sid chroot. The full build log is attached. Thanks. golang-github-hpcloud-tail_1.0.0+git20160415.b294095-1_amd64-20160422-2328.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: golang-github-hpcloud-tail Source-Version: 1.0.0+git20160415.b294095-2 We believe that the bug you reported is fixed in the latest version of golang-github-hpcloud-tail, 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. Daniel Stender (supplier of updated golang-github-hpcloud-tail 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: Sat, 23 Apr 2016 00:29:06 +0200 Source: golang-github-hpcloud-tail Binary: golang-github-hpcloud-tail-dev gotail Architecture: source all amd64 Version: 1.0.0+git20160415.b294095-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Daniel Stender Description: golang-github-hpcloud-tail-dev - Go library for reading from continuously updated files gotail - Go implementation of tail Closes: 822274 Changes: golang-github-hpcloud-tail (1.0.0+git20160415.b294095-2) unstable; urgency=medium . * deb/gbp.conf: added compression. * deb/control: + added golang-x-sys-dev to depends (Closes: #822274). + bumped standards to 3.9.8 (no changes needed). Checksums-Sha1: bda9b66a2f05f6da80637d527c1ad7e3c7549854 2454 golang-github-hpcloud-tail_1.0.0+git20160415.b294095-2.dsc 317d770c37c55210d90341ff4875826eb9da95a9 14016 golang-github-hpcloud-tail_1.0.0+git20160415.b294095.orig.tar.xz d383dbb4606a79658ed8bfe5860efdd226a73389 2324 golang-github-hpcloud-tail_1.0.0+git20160415.b294095-2.debian.tar.xz 9ae76d837ce5607b95cc6ddfa10270ae73004581 15382 golang-github-hpcloud-tail-dev_1.0.0+git20160415.b294095-2_all.deb 09ecf057df4acec83cb1e4eb31d011da8c08aa69 500400 gotail_1.0.0+git20160415.b294095-2_amd64.deb Checksums-Sha256: 2c51ab91f339ac3b162422ddb986bfae4a0c4b58f02fb06f290e4cb944c91f4e 2454 golang-github-hpcloud-tail_1.0.0+git20160415.b294095-2.dsc 4e27c123aa707037471246a9c7ec95243b05c9417fc163c86834134a77c54f59 14016 golang-github-hpcloud-tail_1.0.0+git20160415.b294095.orig.tar.xz 03e469c1d26e77a933104d2796919bdb1087a554905bc6803d945282d6f5ee17 2324 golang-github-hpcloud-tail_1.0.0+git20160415.b294095-2.debian.tar.xz 8aa56ce655d610cda026a30febffa9a2ba2d9c4d6886856eafa59a5139c8744e 15382 golang-github-hpcloud-tail-dev_1.0.0+git
Bug#822279: kdenlive: missing dependency
Package: kdenlive Version: 16.04.0-1 Severity: grave This kdenlive version depends on qml-module-qtquick-controls which leads to a segmentation fault at startup: $ kdenlive qrc:/qml/kdenliveclipmonitor.qml:2:1: module "QtQuick.Controls.Styles" is not installed qrc:/qml/kdenliveclipmonitor.qml:1:1: module "QtQuick.Controls" is not installed qrc:/qml/kdenliveclipmonitor.qml:2:1: module "QtQuick.Controls.Styles" is not installed qrc:/qml/kdenliveclipmonitor.qml:1:1: module "QtQuick.Controls" is not installed Erreur de segmentation Manually installing the package solves the issue. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kdenlive depends on: ii ffmpeg7:3.0.1-3 ii kded5 5.16.0-1 ii kdenlive-data 16.04.0-1 ii kinit 5.16.0-1 ii kio 5.16.0-1 ii libc6 2.22-7 ii libgcc1 1:5.3.1-14 ii libgl1-mesa-glx [libgl1] 11.1.3-1 ii libglu1-mesa [libglu1]9.0.0-2.1 ii libkf5archive55.16.0-1 ii libkf5attica5 5.16.0-1 ii libkf5auth5 5.16.0-1 ii libkf5bookmarks5 5.16.0-1 ii libkf5codecs5 5.16.0-1 ii libkf5completion5 5.16.0-1 ii libkf5configcore5 5.16.0-1 ii libkf5configgui5 5.16.0-1 ii libkf5configwidgets5 5.16.0-1 ii libkf5coreaddons5 5.16.0-1 ii libkf5crash5 5.16.0-1 ii libkf5dbusaddons5 5.16.0-1 ii libkf5filemetadata3 5.16.0-1+b1 ii libkf5guiaddons5 5.16.0-1 ii libkf5i18n5 5.16.0-1 ii libkf5iconthemes5 5.16.0-1 ii libkf5itemviews5 5.16.0-1 ii libkf5jobwidgets5 5.16.0-1 ii libkf5kiocore55.16.0-1 ii libkf5kiofilewidgets5 5.16.0-1 ii libkf5kiontlm55.16.0-1 ii libkf5kiowidgets5 5.16.0-1 ii libkf5newstuff5 5.16.0-1 ii libkf5notifications5 5.16.0-1 ii libkf5notifyconfig5 5.16.0-1 ii libkf5plotting5 5.16.0-1 ii libkf5service-bin 5.16.0-1 ii libkf5service55.16.0-1 ii libkf5solid5 5.16.0-1 ii libkf5sonnetui5 5.16.0-1 ii libkf5textwidgets55.16.0-1 ii libkf5widgetsaddons5 5.16.0-1 ii libkf5xmlgui5 5.16.0-1 ii libmlt++3 6.2.0-1 ii libmlt6 6.2.0-1 ii libqt5concurrent5 5.5.1+dfsg-16+b1 ii libqt5core5a 5.5.1+dfsg-16+b1 ii libqt5dbus5 5.5.1+dfsg-16+b1 ii libqt5gui55.5.1+dfsg-16+b1 ii libqt5network55.5.1+dfsg-16+b1 ii libqt5qml55.5.1-3 ii libqt5quick5 5.5.1-3 ii libqt5script5 5.5.1+dfsg-2 ii libqt5svg55.5.1-2 ii libqt5widgets55.5.1+dfsg-16+b1 ii libqt5xml55.5.1+dfsg-16+b1 ii libstdc++65.3.1-14 ii libv4l-0 1.10.0-2 ii melt 6.2.0-1 ii oxygen-icon-theme 4:4.14.0-1 ii qml-module-qtquick2 5.5.1-3 Versions of packages kdenlive recommends: ii dvdauthor0.7.0-1.4+b1 ii dvgrab 3.5-2+b3 ii frei0r-plugins 1.4-3+b1 ii genisoimage 9:1.1.11-3 ii recordmydesktop 0.3.8.1+svn602-1+b1 ii swh-plugins 0.4.15+1-8 Versions of packages kdenlive suggests: pn khelpcenter -- no debconf information
Bug#749354: marked as done (isakmpd: FTBFS - cannot open /../../Makefile)
Your message dated Fri, 22 Apr 2016 22:13:24 + with message-id and subject line Bug#749354: fixed in isakmpd 20041012-7.3 has caused the Debian Bug report #749354, regarding isakmpd: FTBFS - cannot open /../../Makefile 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.) -- 749354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: isakmpd Version: 20041012-7.2 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] cd /srv/jenkins-slave/workspace/sid-goto-cc-isakmpd/isakmpd-20041012/apps/certpatch; make ; make[2]: Entering directory '/srv/jenkins-slave/workspace/sid-goto-cc-isakmpd/isakmpd-20041012/apps/certpatch' awk: cannot open /../../Makefile (No such file or directory) GNUmakefile:40: *** multiple target patterns. Stop. make[2]: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-isakmpd/isakmpd-20041012/apps/certpatch' GNUmakefile:137: recipe for target 'mksubdirs' failed make[1]: *** [mksubdirs] Error 2 Looking at GNUmakefile suggests that .CURDIR might not be set or is set to an empty value. Be aware that this build uses the latest make in unstable, version 4.0-7. The full build log is attached. Best, Michael isakmpd-build-log.txt.gz Description: application/gunzip pgpyegvbPz4wS.pgp Description: PGP signature --- End Message --- --- Begin Message --- Source: isakmpd Source-Version: 20041012-7.3 We believe that the bug you reported is fixed in the latest version of isakmpd, 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 749...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Andrzej Siewior (supplier of updated isakmpd 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: Wed, 20 Apr 2016 21:40:11 +0200 Source: isakmpd Binary: isakmpd Architecture: source Version: 20041012-7.3 Distribution: unstable Urgency: medium Maintainer: Jochen Friedrich Changed-By: Sebastian Andrzej Siewior Description: isakmpd- The Internet Key Exchange protocol openbsd implementation Closes: 749354 Changes: isakmpd (20041012-7.3) unstable; urgency=medium . * Non-maintainer upload. * Fixup GNUmakefile for certpatch. Patch by Erwan Prioul (Closes: #749354). Checksums-Sha1: e9f8b627adbfc636a59b0d90ec590bfd00079869 1735 isakmpd_20041012-7.3.dsc a166d0039fcb310ec092463da56aee340eebbcaa 31572 isakmpd_20041012-7.3.debian.tar.xz Checksums-Sha256: 9486af8b59beac191bb879bfe2f90becefc03711aafe91c26f3706cae8e2d627 1735 isakmpd_20041012-7.3.dsc 77a312e079e859ad141108e66a5d9613be7c7fbb53f047ff633edbe629cff458 31572 isakmpd_20041012-7.3.debian.tar.xz Files: 2ced56db306b09c8881cffccdafeea09 1735 net optional isakmpd_20041012-7.3.dsc 0ecfbcddf5f7ea5e93596542e765b62f 31572 net optional isakmpd_20041012-7.3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJXF9w0AAoJEHuW6BYqjPXRaDkQALbAamrtjqY4wLsLk8kmj5lx fGTgYdo5mk1oCAwzBolIaSz3krMEn4Lym17HGx0xzi7tYkpN62iP9yzhBT7YUjCu ih5wColgYqu9PMKN7Ijz79fujmT12gR3H1Y/AI6aunyWf1yw2Ml8Dv7OU64KqlHW eCICnOAiNHnasaKabrYuyEVv1hl64VRnfThDDqmurvn/l0eCK0mV0EafL0b/z2Vd y/hMDwkv4mYCKegpFWWbkAFJA3M2ue0hmrxSFr8PyJMSuVSty4G2pYMs/hVmyhma RN5+M+JU/W7zV+p62SyvBX6xGIdXsKNnrWr0cVf44U/0vbpKS8VMat3xgx0/pNU1 8W6Y0XlPjZdqtAn0Y5tFBVJ9uEk5wpsQTB32I5djRaLFPtIwb9b8WvuurRlC30RH Mf0DW3v6ueATwzs2jtJAAd+ptBlh+J9/FyGSrS9LMI4SpBqSsYCK5RbYjFr1MTyZ dXtUsnPMRd/MQJA26L3lvKrepHqu4Wcub6uRdO+iJzrYf9KVp63gXCJSg4dgqw0C 65OKQ/DhcjESXGNh2iTdjVqlo4c023K+uY5SEYEqdgfm7hrc4nOEVS8UFDEMj0/+ jrjwSMCX9+x0t5YlcT826o9Cl3aQlkFB1NmznqWuLOdY8sLsV2aRE7zlDpIwhbaz g85E1W070SWvHrzDk0Zr =YN4G -END PGP SIGNATURE End Message ---
Bug#808610: marked as done (libxapian22: xapian database corruption causes recollindex loop)
Your message dated Fri, 22 Apr 2016 21:54:47 + with message-id and subject line Bug#808610: fixed in xapian-core 1.2.12-2+deb7u1 has caused the Debian Bug report #808610, regarding libxapian22: xapian database corruption causes recollindex loop 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.) -- 808610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxapian22 Version: 1.2.19-1 Severity: important Dear Maintainer, I run recollindex from a crontab every night against a corpus of pdf files. After upgrading to jessie, every few days this update would go into a cpu busy loop, requiring the process to be killed and the database to be deleted and remade. Rebuilding `xapian-core` using the 1.2.21_git68 version of xapian-core from the xapian project has fixed this. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/16 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libxapian22 depends on: ii libc6 2.19-18+deb8u1 ii libgcc1 1:4.9.2-10 ii libstdc++6 4.9.2-10 ii libuuid12.25.2-6 ii zlib1g 1:1.2.8.dfsg-2+b1 libxapian22 recommends no packages. Versions of packages libxapian22 suggests: pn xapian-tools -- no debconf information -- John --- End Message --- --- Begin Message --- Source: xapian-core Source-Version: 1.2.12-2+deb7u1 We believe that the bug you reported is fixed in the latest version of xapian-core, 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 808...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts (supplier of updated xapian-core 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: SHA1 Format: 1.8 Date: Tue, 19 Apr 2016 13:13:31 +1200 Source: xapian-core Binary: libxapian22 libxapian22-dbg libxapian-dev xapian-tools xapian-doc xapian-examples Architecture: source amd64 all Version: 1.2.12-2+deb7u1 Distribution: wheezy Urgency: medium Maintainer: Olly Betts Changed-By: Olly Betts Description: libxapian-dev - Development files for Xapian search engine library libxapian22 - Search engine library libxapian22-dbg - Debugging symbols for the Xapian Search engine library xapian-doc - Core Xapian documentation xapian-examples - Xapian simple example programs xapian-tools - Basic tools for Xapian search engine library Closes: 808610 Changes: xapian-core (1.2.12-2+deb7u1) oldstable; urgency=medium . * New patch increment-cursor-version-on-cancel-or-reopen.patch fixing possible database corruption, especially with recoll. (Closes: #808610) Checksums-Sha1: 73b3b040b9e13e6f2784d362df51370ef92c4329 2132 xapian-core_1.2.12-2+deb7u1.dsc fc4f492231c90c74794b171a0fdcb072fdaec142 31887 xapian-core_1.2.12-2+deb7u1.debian.tar.gz 22793f50510a31f21beac8358102e8bab0ef23ae 1184708 libxapian22_1.2.12-2+deb7u1_amd64.deb 870fa80c98427da60e02d5f976917899c659fea9 7574176 libxapian22-dbg_1.2.12-2+deb7u1_amd64.deb b91eaf92e377719b836cec5aa36b3241358c4602 1866408 libxapian-dev_1.2.12-2+deb7u1_amd64.deb 530145cea537e7c182cc6a80a2be4e2e6d11b2d2 473706 xapian-tools_1.2.12-2+deb7u1_amd64.deb 388b02bd3a67fb623024a4900d516d52661c3057 390468 xapian-examples_1.2.12-2+deb7u1_amd64.deb 619385e1dec2680399b78c9112e95583fe6180c0 2282942 xapian-doc_1.2.12-2+deb7u1_all.deb Checksums-Sha256: 268080d18d9d4f20826490bea2112e9a24ffac8a472a39d76b24c06b22017c6c 2132 xapian-core_1.2.12-2+deb7u1.dsc b8edc5b5f90eb86ceced861c88aa41cc0d927c33594c202afeada03b67052951 31887 xapian-core_1.2.12-2+deb7u1.debian.tar.gz 158cbbe80d4adf696427185a6b63b009ee77cd645a9d05da36c6d30e8c34481f 1184708 libxapian22_1.2.12-2+deb7u1_amd64.deb 92b6ef9cb9d635c33a61dae68732eb5f64a3cf9ddf096a8c1d943e6d6e3edfcd 7574176 libxapian22-dbg_1.2.12-2+deb7u1_amd64.deb 8b97689e8bb79fc66dd816d94a32c95a099ddc015f690068562d21fe4819bb80 1866408 libxapian-dev_1.2.12-
Bug#803275: yt: FTBFS: tests fail on several architectures
notfixed 803275 3.2.1-2.2 found 803275 3.2.1-2.2 thanks "Aaron M. Ucko" writes: > Thanks for fixing yt's Build-Depends setting! Automated builds are > doing better, but several have failed with test suite errors, and I > suspect more will follow. Could you please take a look? You can find > the logs at https://buildd.debian.org/status/logs.php?pkg=yt&ver=3.2.1-2 . Per https://buildd.debian.org/status/logs.php?pkg=yt&ver=3.2.1-2.2 , there are still test suite errors (except on architectures that were already okay, at least so far). Could you please take another look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#779047: marked as done (Two security issues)
Your message dated Fri, 22 Apr 2016 21:54:17 + with message-id and subject line Bug#779047: fixed in fuseiso 20070708-3+deb7u1 has caused the Debian Bug report #779047, regarding Two security issues 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.) -- 779047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fuseiso Severity: grave Tags: security Hi, two vulnerabilities have been found in fuseiso: https://bugzilla.redhat.com/show_bug.cgi?id=863102 https://bugzilla.redhat.com/show_bug.cgi?id=863091 CVE IDs have been requested, but are not yet assigned: http://www.openwall.com/lists/oss-security/2015/02/06/7 Cheers, Moritz --- End Message --- --- Begin Message --- Source: fuseiso Source-Version: 20070708-3+deb7u1 We believe that the bug you reported is fixed in the latest version of fuseiso, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated fuseiso 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: Thu, 24 Mar 2016 18:03:02 +0100 Source: fuseiso Binary: fuseiso Architecture: source i386 Version: 20070708-3+deb7u1 Distribution: wheezy-security Urgency: high Maintainer: David Paleino Changed-By: Thorsten Alteholz Description: fuseiso- FUSE module to mount ISO filesystem images Closes: 779047 Changes: fuseiso (20070708-3+deb7u1) wheezy-security; urgency=high . * Non-maintainer upload by the Wheezy LTS Team. * debian/patches (Closes: #779047): (patches copied from the Squeeze version) + CVE-2015-8837 Add 02-prevent-buffer-overflow.patch. Prevent stack-based buffer overflow when concatenating strings to an absolute path name. Prevention is done by checking that the result will stay under the maximum path length as given by the platforms PATH_MAX constant. + CVE-2015-8836 Add 03-prevent-integer-overflow.patch. Prevent integer overflow in ZISO code. Bail out if a ZF block size > 2^17 is to be read. Checksums-Sha1: 151f3bda79f1226f0fe019f3d51439c19224ef7f 2051 fuseiso_20070708-3+deb7u1.dsc 4b3069f535af53477172359eaaab90e5b827f8e9 339470 fuseiso_20070708.orig.tar.gz e5edbc80df95be06d50e0a24ffba6090db38e586 5178 fuseiso_20070708-3+deb7u1.debian.tar.gz 32d0ae73be7a5c78a08083bef222b476ff8a2251 22724 fuseiso_20070708-3+deb7u1_i386.deb Checksums-Sha256: a3088ae7e50389002823b4fd72a811735ffd23d5bb3e8a14326946203194780d 2051 fuseiso_20070708-3+deb7u1.dsc 9bc183a99f0025d01f30ac3f3622b2602b0ad58dfb5d3acce9063d144bf77193 339470 fuseiso_20070708.orig.tar.gz 668730b73d858179950e408d4cdb7c67aebc3981ef7035e5675639a5679a4636 5178 fuseiso_20070708-3+deb7u1.debian.tar.gz bdc581832d950a74f05e3ba80c3fcd35b1db4d52740dfd33e93f8067878f5b29 22724 fuseiso_20070708-3+deb7u1_i386.deb Files: b1ff3fefdf6a07ada1648a7f9be0d7a2 2051 admin optional fuseiso_20070708-3+deb7u1.dsc 30a0e7a3cf577664001e471ba12b6fb4 339470 admin optional fuseiso_20070708.orig.tar.gz e86de53189d8ec0c484e3282a2a7e2b6 5178 admin optional fuseiso_20070708-3+deb7u1.debian.tar.gz 0dc6671b43d9d6c02d669d76fe709279 22724 admin optional fuseiso_20070708-3+deb7u1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJXAqnmXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2MjAxRkJGRkRCQkRFMDc4MjJFQUJCOTY5 NkZDQUMwRDM4N0I1ODQ3AAoJEJb8rA04e1hHgn0P/ifEl8cC36kuUQ0TVIKV8amn NKxG4AKeMvG+fCHyvePxJd2uDOx837wpBFeuTYt5PAQBYAjBeLskpZrMu/mbkala zGAW4qTuGQ9HTmtcekkAVYuCVFwmaUBgV3UCTS4Dacd7CJlt/8DiNn0zyn8Jf2de 3oB+7vPQsRrDqKVoxzeE0M+e9pF3oAMTDDo0/9Zj5Evl+CKvTe4fC1y8bxPj2ZtB +t+V3rPXZpfnHE/wlwNbl5iMO7MkSp//PlEZWF1wgs65obKUaixZEfwmSYVA9Xby OdJA+w9mHIgW4qoLujWmzbhpyNHZpYYdtsL6AMh3xshJMEzNNDjTJyqPnhgdH3Iy P1gSZtZ0tGtRe05V2tq6VsHKDIHZI0o7tjigUhqaugKt/BIW38CGEBjwXSq93uoG ziczrZtoTl730W3HxKFp+lTOarAk7ok6uHXdZ/IdTQwl7BJobiN5VQmPYFx/xaI6 o8EQXANTUgfBOPdGH74k4xAtLET7J2O37sTw6C5/Zq5wTvzM+jpfmS439k8hA+zH fNKPDF97dp3AZQCYcisaU2tUDy0hbgHpCRTFNVwAdBxuBjxyaoOraHpuwZfCZpAY D18gGQkxlwbwqgapycIFBhL
Bug#819375: marked as done (libreoffice: FTBFS on ppc64el due to linking jawt from the wrong directory)
Your message dated Fri, 22 Apr 2016 21:52:37 + with message-id and subject line Bug#819375: fixed in libreoffice 1:4.3.3-2+deb8u4 has caused the Debian Bug report #819375, regarding libreoffice: FTBFS on ppc64el due to linking jawt from the wrong directory 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.) -- 819375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libreoffice Version: 1:4.3.3-2+deb8u3 Severity: serious Tags: upstream patch Justification: fails to build from source (but built successfully in the past) Dear Maintainer, java dir for power64 and power64le are now different for reasons listed in https://bugs.openjdk.java.net/browse/JDK-8073139 Because of this there is FTBFS on ppc64el when linking libjawt. Attached patches are cherry-picked from the LibreOffice git and solve this problem. I hope that the patches can be useful for solving the problem with building a security update for Jessie@ppc64el. Cheers -- Slavek -- System Information: Debian Release: 8.3 APT prefers stable APT policy: (500, 'stable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Init: unable to detect commit 7a66dbe982623be620ad6ac426fe689a434e5f51 Author: David Tardon Date: Tue May 12 10:37:53 2015 +0200 java dir for powepc64 and powepc64le can differ E.g., RHEL >= 7.1 uses ppc64le for reasons listed in https://bugs.openjdk.java.net/browse/JDK-8073139 . Change-Id: I982e65cdf9e8a5ed23cf444ccb2aee764c4c diff --git a/configure.ac b/configure.ac index 26071dc..55157a9 100644 --- a/configure.ac +++ b/configure.ac @@ -6997,9 +6997,12 @@ then powerpc) my_java_arch=ppc ;; -powerpc64*) +powerpc64) my_java_arch=ppc64 ;; +powerpc64le) +AS_IF([test -d "$JAVA_HOME/jre/lib/ppc64le"], [my_java_arch=ppc64le], [my_java_arch=ppc64]) +;; x86_64) my_java_arch=amd64 ;; commit d8eee8e4d1a303044bf34b28c2e95bd6da23fd79 Author: David Tardon Date: Tue May 12 12:10:16 2015 +0200 java dir for powepc64 and powepc64le can differ E.g., RHEL >= 7.1 uses ppc64le for reasons listed in https://bugs.openjdk.java.net/browse/JDK-8073139 . This is a follow-up to commit 7a66dbe982623be620ad6ac426fe689a434e5f51. Change-Id: I685f76d51e9775788a7fb225c6a5e2309a45ceb7 diff --git a/config_host/config_java.h.in b/config_host/config_java.h.in new file mode 100644 index 000..8b23de9 --- /dev/null +++ b/config_host/config_java.h.in @@ -0,0 +1,6 @@ +#ifndef CONFIG_JAVA_H +#define CONFIG_JAVA_H + +#undef JAVA_ARCH + +#endif diff --git a/configure.ac b/configure.ac index 55157a9..5414754 100644 --- a/configure.ac +++ b/configure.ac @@ -7002,6 +7002,7 @@ then ;; powerpc64le) AS_IF([test -d "$JAVA_HOME/jre/lib/ppc64le"], [my_java_arch=ppc64le], [my_java_arch=ppc64]) +JAVA_ARCH=$my_java_arch ;; x86_64) my_java_arch=amd64 @@ -7011,6 +7012,7 @@ then ;; esac JAWTLIB="-L$JAVA_HOME/jre/lib/$my_java_arch -ljawt" +AS_IF([test "$JAVA_ARCH" != ""], [AC_DEFINE_UNQUOTED([JAVA_ARCH], ["$JAVA_ARCH"])]) fi AC_MSG_RESULT([$JAWTLIB]) fi @@ -12988,6 +12990,7 @@ AC_CONFIG_HEADERS([config_host/config_folders.h]) AC_CONFIG_HEADERS([config_host/config_gcc.h]) AC_CONFIG_HEADERS([config_host/config_global.h]) AC_CONFIG_HEADERS([config_host/config_graphite.h]) +AC_CONFIG_HEADERS([config_host/config_java.h]) AC_CONFIG_HEADERS([config_host/config_lgpl.h]) AC_CONFIG_HEADERS([config_host/config_locales.h]) AC_CONFIG_HEADERS([config_host/config_mpl.h]) diff --git a/jvmfwk/inc/vendorbase.hxx b/jvmfwk/inc/vendorbase.hxx index 2ecd01f..a01db56 100644 --- a/jvmfwk/plugins/sunmajor/pluginlib/vendorbase.hxx +++ b/jvmfwk/plugins/sunmajor/pluginlib/vendorbase.hxx @@ -20,6 +20,8 @@ #ifndef INCLUDED_JVMFWK_PLUGINS_SUNMAJOR_PLUGINLIB_VENDORBASE_HXX #define INCLUDED_JVMFWK_PLUGINS_SUNMAJOR_PLUGINLIB_VENDORBASE_HXX +#include "config_java.h" + #include "rtl/ustring.hxx" #include "rtl/ref.hxx" #include "osl/endian.h" @@ -31,7 +33,9 @@ namespace jfw_plugin //Used by subclasses of VendorBase to build paths to Java runtime -#if defined(__sparcv9) +#if defined(JAVA_ARCH) +#define JFW_PLUGIN_ARCH JAVA_ARCH +#elif defin
Bug#808610: marked as done (libxapian22: xapian database corruption causes recollindex loop)
Your message dated Fri, 22 Apr 2016 21:52:42 + with message-id and subject line Bug#808610: fixed in xapian-core 1.2.19-1+deb8u1 has caused the Debian Bug report #808610, regarding libxapian22: xapian database corruption causes recollindex loop 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.) -- 808610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxapian22 Version: 1.2.19-1 Severity: important Dear Maintainer, I run recollindex from a crontab every night against a corpus of pdf files. After upgrading to jessie, every few days this update would go into a cpu busy loop, requiring the process to be killed and the database to be deleted and remade. Rebuilding `xapian-core` using the 1.2.21_git68 version of xapian-core from the xapian project has fixed this. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/16 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libxapian22 depends on: ii libc6 2.19-18+deb8u1 ii libgcc1 1:4.9.2-10 ii libstdc++6 4.9.2-10 ii libuuid12.25.2-6 ii zlib1g 1:1.2.8.dfsg-2+b1 libxapian22 recommends no packages. Versions of packages libxapian22 suggests: pn xapian-tools -- no debconf information -- John --- End Message --- --- Begin Message --- Source: xapian-core Source-Version: 1.2.19-1+deb8u1 We believe that the bug you reported is fixed in the latest version of xapian-core, 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 808...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts (supplier of updated xapian-core 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: SHA1 Format: 1.8 Date: Tue, 19 Apr 2016 11:49:06 +1200 Source: xapian-core Binary: libxapian22 libxapian22-dbg libxapian-dev xapian-tools xapian-doc xapian-examples Architecture: source amd64 all Version: 1.2.19-1+deb8u1 Distribution: jessie Urgency: medium Maintainer: Olly Betts Changed-By: Olly Betts Description: libxapian-dev - Development files for Xapian search engine library libxapian22 - Search engine library libxapian22-dbg - Debugging symbols for the Xapian Search engine library xapian-doc - Core Xapian documentation xapian-examples - Xapian simple example programs xapian-tools - Basic tools for Xapian search engine library Closes: 808610 Changes: xapian-core (1.2.19-1+deb8u1) stable; urgency=medium . * New patch increment-cursor-version-on-cancel-or-reopen.patch fixing possible database corruption, especially with recoll. (Closes: #808610) Checksums-Sha1: 0069a020877ca1674c9f32a43992f153e66fdf1e 2221 xapian-core_1.2.19-1+deb8u1.dsc 593486e67a9936971c6c47ffa0689c5b52824922 18184 xapian-core_1.2.19-1+deb8u1.debian.tar.xz 945d6d0330a8cca955bbccc596960609f1882495 982846 libxapian22_1.2.19-1+deb8u1_amd64.deb 809a5bcbccae0efeb06f9de4c092f142e9959486 5621020 libxapian22-dbg_1.2.19-1+deb8u1_amd64.deb 0dff07d5d8780c69475728fc2926bc6a2759088b 1186304 libxapian-dev_1.2.19-1+deb8u1_amd64.deb 32f63c1e9615b3e0d47f62b3e7a0078cc365cd4f 466706 xapian-tools_1.2.19-1+deb8u1_amd64.deb fb84bfa53b246ae4a5ed9759b82288be6c0e8575 403700 xapian-examples_1.2.19-1+deb8u1_amd64.deb 430843ad680efc9caf4c3065e80b6234c4777ad1 2041136 xapian-doc_1.2.19-1+deb8u1_all.deb Checksums-Sha256: de867c52c9cc9957dc996395a304d9a215bec9cf46f738dd5bb800994dd7a91c 2221 xapian-core_1.2.19-1+deb8u1.dsc 09c3b52613c45aa0b16b7df9508c5982f1f17db421300aa2eca496dab6ce2ab0 18184 xapian-core_1.2.19-1+deb8u1.debian.tar.xz 7389582e04be08f21f8a4f15a32a60686a284db75e6f43d825a8e9d6677037fc 982846 libxapian22_1.2.19-1+deb8u1_amd64.deb 40b5bb848811a878032c52301c71a549962bb11ecb7b219312fb994ef523e5a1 5621020 libxapian22-dbg_1.2.19-1+deb8u1_amd64.deb f9f70f96cc5854f4e2f3058569ae8c7e2bb4b5908787a5e29a6b22b9c9ba47ed 1186304 libxapian-dev_1.2.19-1+deb8u1_
Processed: Re: Bug#803275: yt: FTBFS: tests fail on several architectures
Processing commands for cont...@bugs.debian.org:
> notfixed 803275 3.2.1-2.2
Bug #803275 {Done: Tobias Frost } [src:yt] yt: FTBFS: tests
fail on several architectures
Ignoring request to alter fixed versions of bug #803275 to the same values
previously set
> found 803275 3.2.1-2.2
Bug #803275 {Done: Tobias Frost } [src:yt] yt: FTBFS: tests
fail on several architectures
Marked as found in versions yt/3.2.1-2.2 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
803275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#822274: golang-github-hpcloud-tail: FTBFS in unstable: cannot find package "golang.org/x/sys/unix"
Package: golang-github-hpcloud-tail Version: 1.0.0+git20160415.b294095-1 Severity: serious Dear maintainer: This package fails to build from source in unstable: -- go install -v github.com/hpcloud/tail github.com/hpcloud/tail/cmd/gotail github.com/hpcloud/tail/ratelimiter github.com/hpcloud/tail/util github.com/hpcloud/tail/watch src/gopkg.in/fsnotify.v1/inotify.go:19:2: cannot find package "golang.org/x/sys/unix" in any of: /usr/lib/go/src/golang.org/x/sys/unix (from $GOROOT) /<>/golang-github-hpcloud-tail-1.0.0+git20160415.b294095/obj-x86_64-linux-gnu/src/golang.org/x/sys/unix (from $GOPATH) dh_auto_build: go install -v github.com/hpcloud/tail github.com/hpcloud/tail/cmd/gotail github.com/hpcloud/tail/ratelimitr github.com/hpcloud/tail/util github.com/hpcloud/tail/watch returned exit code 1 -- The build was made on a virtual machine running stretch with sbuild and a sid chroot. The full build log is attached. Thanks. golang-github-hpcloud-tail_1.0.0+git20160415.b294095-1_amd64-20160422-2328.gz Description: application/gzip
Bug#816796: php-apigen: Useless in Debian
Hi Florian, Le 22/04/2016 à 16:09, Florian Schlichting a écrit : > On Wed, Apr 20, 2016 at 04:00:40PM -0400, David Prévot wrote: >> Le 20/04/2016 à 15:43, Florian Schlichting a écrit >>> So if it's not too difficult to maintain with PHP 7, I'd love for >>> php-apigen to be kept in Debian in the future! >> >> Feel free to take it over (with its dependency chain). > > OK, I'll have a look at php-apigen and dependencies, preparing updates > for PHP 7. Can I keep you in Uploaders, or would you rather be removed? Please, remove me (I’m still around the team, and willing to help for general or specific issues, but don’t wish to be part of the main contacts for packages I don’t use anymore). > I may need a hand or > helpful hint getting used to the pkg-php tools, though, so if you see me > doing something stupid please do tell! The should be the good place to ask for advice in doubt, I won’t the only one willing to help. > I have requested to join pkp-php on alioth. I’m not an admin, but those are usually dealt with in a timely manner, so welcome! Regards David signature.asc Description: OpenPGP digital signature
Bug#818528: madplay: diff for NMU version 0.15.2b-8.1
Control: tags 818528 + patch Control: tags 818528 + pending Dear maintainer, I've prepared an NMU for madplay (versioned as 0.15.2b-8.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards. diff -u madplay-0.15.2b/debian/rules madplay-0.15.2b/debian/rules --- madplay-0.15.2b/debian/rules +++ madplay-0.15.2b/debian/rules @@ -8,7 +8,7 @@ DEB_AUTO_UPDATE_AUTOHEADER:=1.11 DEB_AUTO_UPDATE_AUTOMAKE:=1.11 DEB_AUTO_UPDATE_AUTOCONF:=yes -DEB_AUTOMAKE_ARGS:=--foreign +DEB_AUTOMAKE_ARGS:=--foreign --add-missing include /usr/share/cdbs/1/rules/buildcore.mk include /usr/share/cdbs/1/rules/debhelper.mk diff -u madplay-0.15.2b/debian/changelog madplay-0.15.2b/debian/changelog --- madplay-0.15.2b/debian/changelog +++ madplay-0.15.2b/debian/changelog @@ -1,3 +1,10 @@ +madplay (0.15.2b-8.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS by --add-missing to automake call (Closes: #818528) + + -- Paul Gevers Fri, 22 Apr 2016 21:58:24 +0200 + madplay (0.15.2b-8) unstable; urgency=high * Fix buffer overflow in the alsa output code (Closes: #619341) signature.asc Description: OpenPGP digital signature
Processed: madplay: diff for NMU version 0.15.2b-8.1
Processing control commands: > tags 818528 + patch Bug #818528 [madplay] madplay: FTBFS: required file `./depcomp' not found Added tag(s) patch. > tags 818528 + pending Bug #818528 [madplay] madplay: FTBFS: required file `./depcomp' not found Added tag(s) pending. -- 818528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#822257: linux-image-4.5.0-1-amd64: Since the upgrade to kernel 4.5.0-1 i can't login at all!!!
Processing control commands: > severity -1 important Bug #822257 [src:linux] linux-image-4.5.0-1-amd64: Since the upgrade to kernel 4.5.0-1 i can't login at all!!! Severity set to 'important' from 'critical' > tag -1 moreinfo Bug #822257 [src:linux] linux-image-4.5.0-1-amd64: Since the upgrade to kernel 4.5.0-1 i can't login at all!!! Added tag(s) moreinfo. -- 822257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#822257: linux-image-4.5.0-1-amd64: Since the upgrade to kernel 4.5.0-1 i can't login at all!!!
Control: severity -1 important Control: tag -1 moreinfo At what does the boot or login process fail? Do you see any error messages? If you are using a graphical login screen, have you tried switching to a text terminal (Ctrl-Alt-F2) and logging in there? Does that still work? Ben. -- Ben Hutchings When in doubt, use brute force. - Ken Thompson signature.asc Description: This is a digitally signed message part
Bug#816796: php-apigen: Useless in Debian
Hi David, On Wed, Apr 20, 2016 at 04:00:40PM -0400, David Prévot wrote: > Le 20/04/2016 à 15:43, Florian Schlichting a écrit > > So if it's not too difficult to maintain with PHP 7, I'd love for > > php-apigen to be kept in Debian in the future! > > Feel free to take it over (with its dependency chain). OK, I'll have a look at php-apigen and dependencies, preparing updates for PHP 7. Can I keep you in Uploaders, or would you rather be removed? > My main concern is about security support during the stable lifetime: > it???s PHP, so there will be problems/stuff to fix. Relying on the > packaging team to take care of that on one???s behalf is not an option (it > won???t scale, and I don???t want to be the one doing the clean up during > the stable lifetime, hence those RC-bugs prior to the release). Thanks for clarifying. I will consider that when looking at the packages, but I think I can handle the workload. I may need a hand or helpful hint getting used to the pkg-php tools, though, so if you see me doing something stupid please do tell! I have requested to join pkp-php on alioth. Florian
Bug#821891: marked as done (libbde: FTBFS: FAIL: test_bdeinfo.sh)
Your message dated Fri, 22 Apr 2016 21:49:04 +0200
with message-id <8737qdzaof@msgid.hilluzination.de>
and subject line Re: Bug#821891: libbde: FTBFS: FAIL: test_bdeinfo.sh
has caused the Debian Bug report #821891,
regarding libbde: FTBFS: FAIL: test_bdeinfo.sh
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.)
--
821891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbde
Version: 20160418-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,
libbde fails to build from source in unstable/amd64:
[..]
--add-comments=TRANSLATORS: --keyword=_ --keyword=N_ \
--files-from=./POTFILES.in \
--copyright-holder='Joachim Metz' \
--package-name="${package_gnu}libbde" \
--package-version='20160418' \
--msgid-bugs-address="$msgid_bugs_address" \
;; \
esac
test ! -f libbde.po || { \
if test -f ./libbde.pot; then \
sed -f remove-potcdate.sed < ./libbde.pot > libbde.1po && \
sed -f remove-potcdate.sed < libbde.po > libbde.2po && \
if cmp libbde.1po libbde.2po >/dev/null 2>&1; then \
rm -f libbde.1po libbde.2po libbde.po; \
else \
rm -f libbde.1po libbde.2po ./libbde.pot && \
mv libbde.po ./libbde.pot; \
fi; \
else \
mv libbde.po ./libbde.pot; \
fi; \
}
make[3]: Leaving directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/po'
test ! -f ./libbde.pot || \
test -z "" || make
make[2]: Leaving directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/po'
Making all in manuals
make[2]: Entering directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/manuals'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/manuals'
Making all in tests
make[2]: Entering directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/tests'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/tests'
Making all in msvscpp
make[2]: Entering directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/msvscpp'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/msvscpp'
make[2]: Entering directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418'
make[2]: Nothing to be done for 'all-am'.
make[2]: Leaving directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418'
make[1]: Leaving directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418'
dh_auto_test -O--parallel
make -j9 check VERBOSE=1
make[1]: Entering directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418'
Making check in include
make[2]: Entering directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/include'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/include'
Making check in common
make[2]: Entering directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/common'
make[2]: Leaving directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/common'
Making check in libcstring
make[2]: Entering directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcstring'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcstring'
Making check in libcerror
make[2]: Entering directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcerror'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcerror'
Making check in libcthreads
make[2]: Entering directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcthreads'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcthreads
Bug#819586: debian-installer-netboot-images: unhelpful handling of GPG errors
(re-adding Adam.)
Didier 'OdyX' Raboud (2016-04-22):
> Le vendredi, 22 avril 2016, 19.57:55 Cyril Brulebois a écrit :
> > Didier, I see you have committed a fix in git master, so I'm tagging
> > this bug report accordingly. Did you test it (e.g. by faking a
> > Release file corruption)?
>
> Yes, right. I hacked on that bug, but forgot to update the buglog;
> sorry for that.
No worries.
> > This seems like something we should cherry-pick in stable branches,
> > but I don't want to do so without a confirmation first.
>
> The following patch makes the build fail indeed:
>
> diff --git a/get-images.sh b/get-images.sh
> index caea03d..31f25bf 100755
> --- a/get-images.sh
> +++ b/get-images.sh
> @@ -159,6 +159,9 @@ unpack_installer () {
> wget -c $MIRROR/dists/$DISTRIBUTION/Release.gpg -O $RELEASE_FILE.gpg
> wget -c $MIRROR/dists/$DISTRIBUTION/Release -O $RELEASE_FILE
>
> +# Corrupt the release file
> +echo "Break the signature" >> $RELEASE_FILE
> +
> gpgv --keyring /usr/share/keyrings/debian-archive-keyring.gpg
> $RELEASE_FILE.gpg $RELEASE_FILE
>
> get_di_built_using $1
Thanks!
I've therefore git cherry-picked your patch to both wheezy and jessie
branches, but I didn't do any build testing. Adam, if you end up being
the one preparing the next dini upload(s) [I hope to be around for good
by then but…], feel free to hunt me down if that doesn't work out as
planned.
KiBi.
signature.asc
Description: Digital signature
Processed: retitle 816101 to FTBFS on mipsel/powerpc - broken openmpi breaks petsc build
Processing commands for cont...@bugs.debian.org: > retitle 816101 FTBFS on mipsel/powerpc - broken openmpi breaks petsc build Bug #816101 [src:petsc] FTBFS on mipsel - broken openmpi breaks petsc build Changed Bug title to 'FTBFS on mipsel/powerpc - broken openmpi breaks petsc build' from 'FTBFS on mipsel - broken openmpi breaks petsc build'. > thanks Stopping processing here. Please contact me if you need assistance. -- 816101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#819586: debian-installer-netboot-images: unhelpful handling of GPG errors
Hoy KiBi,
Le vendredi, 22 avril 2016, 19.57:55 Cyril Brulebois a écrit :
> Adam D. Barratt (2016-03-30):
> > Whilst a failure to verify the Release signature does mean that we
> > don't attempt to build an image using untrusted inputs, the package
> > build continues with no sign of a problem having occurred until the
> > binary packages are examined.
>
> Thanks for the catch!
>
> Didier, I see you have committed a fix in git master, so I'm tagging
> this bug report accordingly. Did you test it (e.g. by faking a Release
> file corruption)?
Yes, right. I hacked on that bug, but forgot to update the buglog; sorry
for that.
> This seems like something we should cherry-pick in
> stable branches, but I don't want to do so without a confirmation
> first.
The following patch makes the build fail indeed:
diff --git a/get-images.sh b/get-images.sh
index caea03d..31f25bf 100755
--- a/get-images.sh
+++ b/get-images.sh
@@ -159,6 +159,9 @@ unpack_installer () {
wget -c $MIRROR/dists/$DISTRIBUTION/Release.gpg -O $RELEASE_FILE.gpg
wget -c $MIRROR/dists/$DISTRIBUTION/Release -O $RELEASE_FILE
+# Corrupt the release file
+echo "Break the signature" >> $RELEASE_FILE
+
gpgv --keyring /usr/share/keyrings/debian-archive-keyring.gpg
$RELEASE_FILE.gpg $RELEASE_FILE
get_di_built_using $1
--
Cheers,
OdyX
Bug#819586: debian-installer-netboot-images: unhelpful handling of GPG errors
Control: tag -1 patch pending Hi, Adam D. Barratt (2016-03-30): > Source: debian-installer-netboot-images > Version: 20120712 > Severity: serious > Justification: silently ignores failures, creating broken packages > > Hi, > > Whilst preparing the dini uploads for the upcoming point releases, on > debdiffing the binary packages against the previous versions I noticed > that one of them seemed to have lost all of its files and had an > Installed-Size of 32. > > Checking the build log, I found that this was due to one of the Release > file checks failing with: > > gpgv: BAD signature from "Debian Archive Automatic Signing Key > (7.0/wheezy) " > > (This appears to have been an issue with a particular mirror, fwiw.) > > The checks in get-images.sh do: > > if gpgv --keyring /usr/share/keyrings/debian-archive-keyring.gpg > $RELEASE_FILE.gpg $RELEASE_FILE ; then > get_di_built_using $1 > get_installer $1 > fi > > Whilst a failure to verify the Release signature does mean that we don't > attempt to build an image using untrusted inputs, the package build > continues with no sign of a problem having occurred until the binary > packages are examined. Thanks for the catch! Didier, I see you have committed a fix in git master, so I'm tagging this bug report accordingly. Did you test it (e.g. by faking a Release file corruption)? This seems like something we should cherry-pick in stable branches, but I don't want to do so without a confirmation first. KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#819586: debian-installer-netboot-images: unhelpful handling of GPG errors
Processing control commands: > tag -1 patch pending Bug #819586 [src:debian-installer-netboot-images] debian-installer-netboot-images: unhelpful handling of GPG errors Added tag(s) pending and patch. -- 819586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#822262: efitools: FTBFS: efi.h: No such file or directory
Source: efitools Version: 1.4.2-1 Severity: serious Justification: fails to build from source Build of efitools in minimal environments (notably, on the autobuilders) have been failing: simple_file.c:7:17: fatal error: efi.h: No such file or directory Please declare a build dependency on gnu-efi and confirm with pbuilder or the like that you haven't missed anything else. Thanks!
Bug#810209: marked as done (yt: Please update dependency on libpng-dev)
Your message dated Fri, 22 Apr 2016 17:37:12 + with message-id and subject line Bug#810209: fixed in yt 3.2.1-2.2 has caused the Debian Bug report #810209, regarding yt: Please update dependency on libpng-dev 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.) -- 810209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: yt Severity: important User: lib...@packages.debian.org Usertags: libpng16-transition Dear yt maintainers, Currently we are preparing the transition of libpng1.2 to libpng1.6. The transition bug is #650601. A rebuild of all packages depending on libpng-dev and libpng(3,12,12-0)-dev has been done. The result with buildlogs can be found here: https://libpng.sviech.de/ yt builds fine with libpng16, you can see the buildlog here: https://libpng.sviech.de/yt.build Howver, yt (build-)depends an versioned development package libpng12-dev. Please update your (build-)depends to libpng-dev to help in the transition. This bug will become RC as soon as the transition starts, as it is planned to remove libpng12. Thanks! -- tobi --- End Message --- --- Begin Message --- Source: yt Source-Version: 3.2.1-2.2 We believe that the bug you reported is fixed in the latest version of yt, 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 810...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated yt 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: Fri, 22 Apr 2016 19:30:14 +0200 Source: yt Binary: python-yt python3-yt Architecture: source Version: 3.2.1-2.2 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Tobias Frost Description: python-yt - Framework for analyzing and visualizing simulation data (Python 2 python3-yt - Framework for analyzing and visualizing simulation data (Python 3 Closes: 810209 Changes: yt (3.2.1-2.2) unstable; urgency=medium . * Non-maintainer upload. * Really removing the B-D on libpng-dev. (Closes: #810209) Checksums-Sha1: c5b5128ad27c17e5d8ca84e04ddabbc68d2d3b0c 2258 yt_3.2.1-2.2.dsc 9165ec19c25d0c7ef71439ae292957cf9a371004 9444 yt_3.2.1-2.2.debian.tar.xz Checksums-Sha256: c89e3948c20cd6a72af8079d0a7b173fe24872dfd12ff53447fd1166adb6eb47 2258 yt_3.2.1-2.2.dsc 3430dc2020b63b792cc175a6d604f5c5e5359521bf5fb3ac15a49d9d64b2fb06 9444 yt_3.2.1-2.2.debian.tar.xz Files: 2c25d4f4402e1bea1a1fdf7e07766076 2258 python optional yt_3.2.1-2.2.dsc cdcea65e4fb06dad8ee3e1f8e9b324a9 9444 python optional yt_3.2.1-2.2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXGl+0AAoJEJFk+h0XvV02JzIP/RFolWRbB7EVQ1Q2bbXvEVKw Qqt0lwW0vOLmKJE8bZBDtR3gjK2FIdeONwUfOJ8CWAawOOV9DvupbJmaE1ThfBys 402H9GLGk8YhmMA3uL56LE1D+Smw+gcFF/kc68VnnR/pw4zyAWnTcCOJ/mrccXiq oGZtvd7AiuSl5OHsvPEtHzrR980G0MzsoiTZ62h8Y/fK4Fk4oikAtMI8dmHw2Xu2 bKzOXUAkyqsCE6Wisjpn6CGoPHf3nN8tTgLIvXhlxINqN2ThT9uhr4CMxSCFM68m LoSnf0BkrNTqZRSrYv87MciDQYHPjuM5NKy85x1KFn9NzcYjVp6UTD3WZcyuhGLp ZNpUnveLpJM3FVQmul/D2hZKPPfbuYUjIjmlj9cLDNy2FHvqHXmJNpUKOMBQgyw1 acA82NNp1npXJvYyC1KtKH0eQ4T7EEmWV4CpFhC4gGZI0189yRZw/hQSVLDVE0Ta pMYwbLkykTMfxdpZr/3WL/ykBhukXcsIASK8f3VxomaJyZGsMZSIzLVF6CiZ4tJt sGs6PKYoT88eoODdur+z4oZ6pIO2pdvuQv2RTYvhZUIGxrPWAic/sIYzNSbcuy/C t0F6C8/T5ehRolm6cLHD6zMt33lyQaJVyj6ZPc2xWk6r7GwXYKmBy1e/nsPggJdm uZuv4lOzUGfWHv3PaFe+ =zwT9 -END PGP SIGNATURE End Message ---
Processed: reopening 810209
Processing commands for cont...@bugs.debian.org:
> reopen 810209
Bug #810209 {Done: Tobias Frost } [yt] yt: Please update
dependency on libpng-dev
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions yt/3.2.1-2.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
810209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#810209: yt: diff for NMU version 3.2.1-2.2
Control: tags 810209 + patch Dear maintainer, I've prepared an NMU for yt (versioned as 3.2.1-2.2). The diff is attached to this message. Regards. diff -Nru yt-3.2.1/debian/changelog yt-3.2.1/debian/changelog --- yt-3.2.1/debian/changelog 2016-04-22 19:02:34.0 +0200 +++ yt-3.2.1/debian/changelog 2016-04-22 19:30:14.0 +0200 @@ -1,3 +1,10 @@ +yt (3.2.1-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Really removing the B-D on libpng-dev. (Closes: #810209) + + -- Tobias Frost Fri, 22 Apr 2016 19:30:14 +0200 + yt (3.2.1-2.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru yt-3.2.1/debian/control yt-3.2.1/debian/control --- yt-3.2.1/debian/control 2015-10-28 12:17:17.0 +0100 +++ yt-3.2.1/debian/control 2016-04-22 19:30:09.0 +0200 @@ -7,7 +7,6 @@ cython3 (>= 0.22), debhelper (>= 9), dh-python, - libpng12-dev, libpython-dev, libpython3-dev, python-all-dev,
Processed: yt: diff for NMU version 3.2.1-2.2
Processing control commands:
> tags 810209 + patch
Bug #810209 {Done: Tobias Frost } [yt] yt: Please update
dependency on libpng-dev
Added tag(s) patch.
--
810209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#803275: marked as done (yt: FTBFS: tests fail on several architectures)
Your message dated Fri, 22 Apr 2016 17:25:45 + with message-id and subject line Bug#803275: fixed in yt 3.2.1-2.1 has caused the Debian Bug report #803275, regarding yt: FTBFS: tests fail on several architectures 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.) -- 803275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yt Version: 3.2.1-2 Severity: important Justification: fails to build from source Thanks for fixing yt's Build-Depends setting! Automated builds are doing better, but several have failed with test suite errors, and I suspect more will follow. Could you please take a look? You can find the logs at https://buildd.debian.org/status/logs.php?pkg=yt&ver=3.2.1-2 . Thanks! --- End Message --- --- Begin Message --- Source: yt Source-Version: 3.2.1-2.1 We believe that the bug you reported is fixed in the latest version of yt, 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 803...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated yt 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: Fri, 22 Apr 2016 19:02:34 +0200 Source: yt Binary: python-yt python3-yt Architecture: source Version: 3.2.1-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Tobias Frost Description: python-yt - Framework for analyzing and visualizing simulation data (Python 2 python3-yt - Framework for analyzing and visualizing simulation data (Python 3 Closes: 803275 810209 Changes: yt (3.2.1-2.1) unstable; urgency=medium . * Non-maintainer upload. * Fixing the test-suite failure which caused the FTBFS (Closes: #803275) * Remove B-D on libpng (Closes: #810209) Checksums-Sha1: fd3d27630467bf29ce5cdb17a265950192220430 2272 yt_3.2.1-2.1.dsc d172e79f3637d2f24fe77a37cf53cc3b56a1a522 9424 yt_3.2.1-2.1.debian.tar.xz Checksums-Sha256: 1bf14f40a7644b86dd95aa64b9235b48b41276d155f6a882e4462e19edf482e6 2272 yt_3.2.1-2.1.dsc 9ddc3f0024fa6b0326e6d5c6cbb7ffbfd3abd6179b7c1a67cc94821e91e8240e 9424 yt_3.2.1-2.1.debian.tar.xz Files: 24e3b8a681722b01c8c79606f4cd00c1 2272 python optional yt_3.2.1-2.1.dsc 0c13ab4816ecc0fe3a982c5a8c28824a 9424 python optional yt_3.2.1-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXGlpiAAoJEJFk+h0XvV02oEsQAL0+a2FPtjNLcdbjrGdypK17 lHx2tztq9wVY+mE/Rys35os3fBZ2lEiDNFPcfgg4d/r/Up6AQJXbRsrDL8CMfpz8 x5Sd4a8hicgjtdqm/ItU/cfW9wBHq810nv6yZT3dn4YZd5yPU8LUeB2efy3GPH2a zbD4MJv9k52eN+VsFPNdT0+4Rx7y8grwgk5N1XCWehwTDA+4W9PracslXdiGHWd6 Pi9T7vUdiuHwExSWY65+17HUxbec/qfbgAVGyntzcNSd0m9MwkCTDqq7E1Vg3/Rw /MoSabDkRmWoH06+9ZmN5MVj5+tDfaDnhGiSXNbqCZLEUKsA8XYm1NzxRGSOa+li PNlNoeGmO5WL+4ZofWJuzadP7JsdJ1YvzuDZJMleZD9jksXM8N7S52S8HcMUK6xP GGutyssyb5G74EpevlC0+BImCnQ5irImbLJaMMOssmUKPE6/HouGzzAPIdDGjlKO lq1RonEJKPNUC8k/xilxCBlSFTWeGwqvr5t4JcNGg7Dg/viJsliKv6fpua/3yX6x hOioJalwretKCFLO240ulpo05Rd6z0YmyNFx5Igk5/eqrUiZK7YtLTfho2YYHbw1 KFQO6cjsrVgtG/VTQKFH1M8AlQ5/V72x42EoOIjcKx/Qs0Onl/RimYhUI8cNu0SW 4fTjX4g6rrWABja0DYWP =BRBB -END PGP SIGNATURE End Message ---
Bug#810209: marked as done (yt: Please update dependency on libpng-dev)
Your message dated Fri, 22 Apr 2016 17:25:45 + with message-id and subject line Bug#810209: fixed in yt 3.2.1-2.1 has caused the Debian Bug report #810209, regarding yt: Please update dependency on libpng-dev 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.) -- 810209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: yt Severity: important User: lib...@packages.debian.org Usertags: libpng16-transition Dear yt maintainers, Currently we are preparing the transition of libpng1.2 to libpng1.6. The transition bug is #650601. A rebuild of all packages depending on libpng-dev and libpng(3,12,12-0)-dev has been done. The result with buildlogs can be found here: https://libpng.sviech.de/ yt builds fine with libpng16, you can see the buildlog here: https://libpng.sviech.de/yt.build Howver, yt (build-)depends an versioned development package libpng12-dev. Please update your (build-)depends to libpng-dev to help in the transition. This bug will become RC as soon as the transition starts, as it is planned to remove libpng12. Thanks! -- tobi --- End Message --- --- Begin Message --- Source: yt Source-Version: 3.2.1-2.1 We believe that the bug you reported is fixed in the latest version of yt, 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 810...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated yt 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: Fri, 22 Apr 2016 19:02:34 +0200 Source: yt Binary: python-yt python3-yt Architecture: source Version: 3.2.1-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Tobias Frost Description: python-yt - Framework for analyzing and visualizing simulation data (Python 2 python3-yt - Framework for analyzing and visualizing simulation data (Python 3 Closes: 803275 810209 Changes: yt (3.2.1-2.1) unstable; urgency=medium . * Non-maintainer upload. * Fixing the test-suite failure which caused the FTBFS (Closes: #803275) * Remove B-D on libpng (Closes: #810209) Checksums-Sha1: fd3d27630467bf29ce5cdb17a265950192220430 2272 yt_3.2.1-2.1.dsc d172e79f3637d2f24fe77a37cf53cc3b56a1a522 9424 yt_3.2.1-2.1.debian.tar.xz Checksums-Sha256: 1bf14f40a7644b86dd95aa64b9235b48b41276d155f6a882e4462e19edf482e6 2272 yt_3.2.1-2.1.dsc 9ddc3f0024fa6b0326e6d5c6cbb7ffbfd3abd6179b7c1a67cc94821e91e8240e 9424 yt_3.2.1-2.1.debian.tar.xz Files: 24e3b8a681722b01c8c79606f4cd00c1 2272 python optional yt_3.2.1-2.1.dsc 0c13ab4816ecc0fe3a982c5a8c28824a 9424 python optional yt_3.2.1-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXGlpiAAoJEJFk+h0XvV02oEsQAL0+a2FPtjNLcdbjrGdypK17 lHx2tztq9wVY+mE/Rys35os3fBZ2lEiDNFPcfgg4d/r/Up6AQJXbRsrDL8CMfpz8 x5Sd4a8hicgjtdqm/ItU/cfW9wBHq810nv6yZT3dn4YZd5yPU8LUeB2efy3GPH2a zbD4MJv9k52eN+VsFPNdT0+4Rx7y8grwgk5N1XCWehwTDA+4W9PracslXdiGHWd6 Pi9T7vUdiuHwExSWY65+17HUxbec/qfbgAVGyntzcNSd0m9MwkCTDqq7E1Vg3/Rw /MoSabDkRmWoH06+9ZmN5MVj5+tDfaDnhGiSXNbqCZLEUKsA8XYm1NzxRGSOa+li PNlNoeGmO5WL+4ZofWJuzadP7JsdJ1YvzuDZJMleZD9jksXM8N7S52S8HcMUK6xP GGutyssyb5G74EpevlC0+BImCnQ5irImbLJaMMOssmUKPE6/HouGzzAPIdDGjlKO lq1RonEJKPNUC8k/xilxCBlSFTWeGwqvr5t4JcNGg7Dg/viJsliKv6fpua/3yX6x hOioJalwretKCFLO240ulpo05Rd6z0YmyNFx5Igk5/eqrUiZK7YtLTfho2YYHbw1 KFQO6cjsrVgtG/VTQKFH1M8AlQ5/V72x42EoOIjcKx/Qs0Onl/RimYhUI8cNu0SW 4fTjX4g6rrWABja0DYWP =BRBB -END PGP SIGNATURE End Message ---
Processed: severity of 822243 is normal
Processing commands for cont...@bugs.debian.org: > severity 822243 normal Bug #822243 [ftp.debian.org] calligra: RM calligra [ANY] -- RC-buggy, FTBFS, blocks removal of no-longer-built packages Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 822243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 803275 is serious
Processing commands for cont...@bugs.debian.org: > severity 803275 serious Bug #803275 [src:yt] yt: FTBFS: tests fail on several architectures Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 803275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#817789: marked as done (FTBFS: pep8 module is now in python-pep8 package)
Your message dated Fri, 22 Apr 2016 16:19:52 + with message-id and subject line Bug#817789: fixed in blockdiag 1.4.7-2.1 has caused the Debian Bug report #817789, regarding FTBFS: pep8 module is now in python-pep8 package 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.) -- 817789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: blockdiag Version: 1.4.7-2 Severity: normal Tags: patch The pep8 module is now in python-pep8 package, so the Build-Depends for this package need to be updated. Here is a patch. --- debian/control.orig 2016-03-10 10:30:58.612028956 + +++ debian/control 2016-03-10 10:31:45.312231146 + @@ -7,7 +7,7 @@ python-all, python-setuptools, python-unittest2, - pep8 (>= 1.3), + python-pep8, python-nose, python-zc.buildout, python-funcparserlib (>= 0.3.4), --- End Message --- --- Begin Message --- Source: blockdiag Source-Version: 1.4.7-2.1 We believe that the bug you reported is fixed in the latest version of blockdiag, 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 817...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated blockdiag 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: Fri, 18 Mar 2016 18:17:54 +0100 Source: blockdiag Binary: python-blockdiag python3-blockdiag Architecture: source all Version: 1.4.7-2.1 Distribution: unstable Urgency: medium Maintainer: Kouhei Maeda Changed-By: Georges Khaznadar Description: python-blockdiag - generate block-diagram image file from spec-text file python3-blockdiag - generate block-diagram image file from spec-text file for Python Closes: 817789 Changes: blockdiag (1.4.7-2.1) unstable; urgency=medium . * Non-maintainer upload. * added a dependency on python-pep8. Closes: #817789 Checksums-Sha1: b25d4017d1faf1eb7cb9cf10e869c787e9d1d6da 2267 blockdiag_1.4.7-2.1.dsc b98e21f5a5881c1bad43f1f747d68c498808b9a0 6092 blockdiag_1.4.7-2.1.debian.tar.xz b293956de08dd141d94b8d28e1d68cb15b4db609 73636 python-blockdiag_1.4.7-2.1_all.deb b53889a91fbd0fa0ecd086280896223b1ecd91a6 73410 python3-blockdiag_1.4.7-2.1_all.deb Checksums-Sha256: 0ed391a6fe02861b90579e96591c5da2e47a49bf2d3c259f60679bab5d27362b 2267 blockdiag_1.4.7-2.1.dsc f26a41122121d1203cedc21b6ac53bb634da2d2d97162ac631f2a12488eb1009 6092 blockdiag_1.4.7-2.1.debian.tar.xz fb469ef81ea8a7b340c63ee15c6b2dffc9f4dd7c7fadaee9ef8a6b5184f67797 73636 python-blockdiag_1.4.7-2.1_all.deb 8ca668a47ccbf6aa1ea9ae9c660c8dcd559528edeef81728924c6fee3dcc17f2 73410 python3-blockdiag_1.4.7-2.1_all.deb Files: dc3604896ca175c4ded0b86783e2bbbd 2267 python optional blockdiag_1.4.7-2.1.dsc 7b0ae67c884075cf16c45a8654e6f246 6092 python optional blockdiag_1.4.7-2.1.debian.tar.xz f0555ac8dab0ec10edd6a17e7440523c 73636 python optional python-blockdiag_1.4.7-2.1_all.deb 0b41b8e28981bfa0dfdc9ff147aeb278 73410 python optional python3-blockdiag_1.4.7-2.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVuw73hwoFpBxNq45AQjH+xAAhpckZJNYZNWCtkG3QQEQRQF9AL5yPHBF JtVGAEi3f2bBq4BHoMEyVyRbs4x46QNta/2+OZ/fbd23W0qYcvn/7dDoro7ZfT58 qguehr+NQxPai1nUKRMCH7U0AfU94KGOi1JFB6doLbkwhmCflc7GPADmQ1gWWZJ+ Jip/e1NzPHqQmCw12F/xSr51TPKQ5G0Ktn94OvRJSmxUA+oV6YVDijdbXnemyaSb VvjLEeRr+capamim0hA+w1nn5VZMDse7gSY4vJSItnjJ/Vo8fewTaKs6qqCSHkHd LUNEU2uZvRVir59jMZsOoHfk5h3MUX2TgrQasSb/ndubCoMPVjSyfgYLIwdpbIQ2 URtn2GSNMMm87Svyk2cej9iVgJZDuREeBjemMRong3U0fIl6s7ivkzUZZgiWVTq7 sq8izd05E6hFQA8ZPZouedrtmVZ7MMEfXJe/wVzu32cVwJKlTRRxm8k3QgQkC8WB GhDIZrgolNl6DI+6ZoyuSrywGuUUC4cxTDhFZQOKaymTzAqOJAU7il4ExoPm8BJz kGTXDZEIhQ+AoTfvMpvQ9UPVUylRC0bvapsLZ3AcYtFHG/65SB87O4hEDonk3uPo 76LthEQbIEPqMjaYVM38eDIdPISDa+LNpDCffuqN9tokxKIdpsUdUyIgus4IMtxR baKQdDtAKFg= =DrCC -END PGP SIGNATURE End Message ---
Bug#822257: linux-image-4.5.0-1-amd64: Since the upgrade to kernel 4.5.0-1 i can't login at all!!!
Package: src:linux Version: 4.5.1-1 Severity: critical Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Sony Corporation product_name: SVEM1EW product_version: C60AXKWN chassis_vendor: Sony Corporation chassis_version: N/A bios_vendor: Insyde Corp. bios_version: R0150E8 board_vendor: Sony Corporation board_name: VAIO board_version: N/A ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 14h Processor Root Complex [1022:1510] Subsystem: Sony Corporation Family 14h Processor Root Complex [104d:90ad] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- [disabled] Capabilities: Kernel driver in use: radeon Kernel modules: radeon 00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler HDMI Audio [1002:1314] Subsystem: Sony Corporation Wrestler HDMI Audio [104d:90ad] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 14h Processor Root Port [1022:1512] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 14h Processor Root Port [1022:1513] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 14h Processor Root Port [1022:1514] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller [1022:7812] (rev 03) (prog-if 30 [XHCI]) Subsystem: Sony Corporation FCH USB XHCI Controller [104d:90ad] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7804] (prog-if 01 [AHCI 1.0]) Subsystem: Sony Corporation FCH SATA Controller [AHCI mode] [104d:90ad] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ahci Kernel modules: ahci 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller [1022:7807] (rev 11) (prog-if 10 [OHCI]) Subsystem: Sony Corporation FCH USB OHCI Controller [104d:90ad] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller [1022:7807] (rev 11) (prog-if 10 [OHCI]) Subsystem: Sony Corporation FCH USB OHCI Controller [104d:90ad] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepp
Bug#818533: marked as done (gpsim-dev: needs to rebuild due to GTK+ API change)
Your message dated Fri, 22 Apr 2016 16:25:11 + with message-id and subject line Bug#818533: fixed in gpsim 0.29.0-2 has caused the Debian Bug report #818533, regarding gpsim-dev: needs to rebuild due to GTK+ API change 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.) -- 818533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gpsim-dev Version: 0.29.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, due to changes in GTK+ API (gtk_sheet*) package needs to rebuild. Otherwise fail linking libgpsim in other applications. No other operational changes are required - just rebuild. Thanks, -- Slavek -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages gpsim-dev depends on: ii gpsim0.29.0-1 ii libpopt-dev 1.16-10 gpsim-dev recommends no packages. gpsim-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gpsim Source-Version: 0.29.0-2 We believe that the bug you reported is fixed in the latest version of gpsim, 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 818...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated gpsim 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: Fri, 18 Mar 2016 00:36:00 +0100 Source: gpsim Binary: gpsim gpsim-dev Architecture: source amd64 Version: 0.29.0-2 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Description: gpsim - Simulator for Microchip's PIC microcontrollers gpsim-dev - Libraries needed only for building gpsim components Closes: 818533 Changes: gpsim (0.29.0-2) unstable; urgency=medium . * rebuilf with new GTK libraries. Closes: #818533 Checksums-Sha1: 23393a4db211cca1d8b59a81bb425729dd3ae605 1868 gpsim_0.29.0-2.dsc 76fe9034867448b94a8fbed960497d10f0381b0a 10036 gpsim_0.29.0-2.debian.tar.xz b1672b320eedf06ae5f0ea34276e6e5c7c864272 7783546 gpsim-dbgsym_0.29.0-2_amd64.deb 0ea59cd8142c3f469abe7b90c9f034b6e0b34d34 224804 gpsim-dev_0.29.0-2_amd64.deb a317827c95585451b01b640c067851f20c1c9011 1226152 gpsim_0.29.0-2_amd64.deb Checksums-Sha256: 057c255e79b43af010a8a62780d58c76af0628afa4b0aba74df542adf50759ec 1868 gpsim_0.29.0-2.dsc 0b1acb7142a5b0ee7fa8332e7f7de3ec9553450502dcabc53ac91f8d3c29fdb7 10036 gpsim_0.29.0-2.debian.tar.xz 90f0784b2b4626a1a711b145ea848befb523f5d603d79f0778bbc7cab0a41cd1 7783546 gpsim-dbgsym_0.29.0-2_amd64.deb e5dfbc12b71bda6628dae6111e1d42ca7f03d95d0a3d0db505da43c1c77f111b 224804 gpsim-dev_0.29.0-2_amd64.deb bf27e80426cde9b40eb91c648fd2bea922c849bb6947696c9ffe4943aa3049a0 1226152 gpsim_0.29.0-2_amd64.deb Files: 8664a0ead4d0ba6ce641327d9d838934 1868 electronics optional gpsim_0.29.0-2.dsc 915bd940f21cfc4c880606874932b1a9 10036 electronics optional gpsim_0.29.0-2.debian.tar.xz 4cc744b20dd539e5048a1d8cac75eb92 7783546 debug extra gpsim-dbgsym_0.29.0-2_amd64.deb 897ce307e74354f3a758cbc1bd4593e6 224804 devel optional gpsim-dev_0.29.0-2_amd64.deb ff02d0791a6564553443a7e000d6630a 1226152 electronics optional gpsim_0.29.0-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVutCrxwoFpBxNq45AQiG+Q/9GJLaCbSTnc1BYUd7PKKQl8DFUVg69luH U3IzjC36HInU2fWP9K2+vuSt7PQXZjo3LquqYLWXd2jdo6XgOLU5oZ9JNMfkxSHz HByThHVjZ3AU+OMPx+zZp2hHvT/Ng9GQlZFOfM5eNRdL49StQi9p8Re+c+3pJAeL gGLXKOWGerR8lVx8BKuCyA/quKEkRJeNBdzHu4Teb52o5JeHDc/r1xagZ/l5C0La p/7cci4sg09MDl/3FHdLqiIvjFPtRU67rw4x58buPRmFI0uKDTairddCTY9EDukE Zri3LaxGR/hX9h+tjm0Ufrj3ck/bt0NmNbnE7JSHwpMpsadRKJqtjjid2BTsUNY1 Mfz1ScOig4V6LMNVWQC60IyCSlXwqN+ZhBXBIHNv4tI6NAZhEW+rs/j1mDjejfey 8HBuoFEs+Y3lU6zTkhjDRkikKlvBcEYZ7kksreZEI+/pUAfjuwwziKcDeMzg6ql7 yaChHoJ5ZODFbKYr5Oa6oDUmuGcs2sQ0CmFtGJkZK3ZqDchIvVBzoBP1uEUo8TOX spqO3dDFYD4I+i0j/Kx4BuHYw3KpNRihEy
Bug#816101: petsc: FTBFS on mipsel - broken openmpi breaks petsc build
On 21 April 2016 at 17:19, Graham Inggs wrote: > This sounds a lot like the problem we have with powerpc, see bug #814183. I > think you may just have been very lucky in which powerpc buildds petsc has > landed on lately. Your luck ran out, the build failed on powerpc [1]. It stopped responding just after: C/C++ example src/snes/examples/tutorials/ex19 run successfully with 1 MPI process ...and was terminated after 150 minutes of inactivity. [1] https://buildd.debian.org/status/fetch.php?pkg=petsc&arch=powerpc&ver=3.6.3.dfsg2-4.1&stamp=1461340655
Bug#821795: lttng-modules-dkms: module FTBFS in jessie against Linux 3.16: error: conflicting types for 'trace_mm_page_alloc_extfrag'
* Michael Jeanson wrote: > Hi, > > Here is a debdiff against the current package fixing the build > failure, I'll ask Jon to make a new upload. Thanks Michael, I'm traveling this week and next, I'll try to get to this as soon as I can but it may be a week or two before I have adequate time. NMUs are welcome if faster response time is necessary. Cheers, -- Jon
Processed: Re: Amarok should depend on virtual-mysql-server-core to support MariaDB
Processing control commands:
> reopen -1
Bug #815567 {Done: Samuel Henrique Oltramari Pinto (SamuelOPH)
} [amarok] Amarok should depend on
virtual-mysql-server-core to support MariaDB
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions amarok/2.8.0-4.1.
--
815567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#815567: Amarok should depend on virtual-mysql-server-core to support MariaDB
Control: reopen -1 On Mon, 22 Feb 2016 18:06:27 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= wrote: > Amarok defines as build dependency: > > Build-Depends-Indep: mysql-server-core-5.6 | mysql-server-core > > This should be changed to: > > Build-Depends-Indep: mysql-server-core-5.6 | virtual-mysql-server-core That has been implemented, but that's the wrong approach. The buildds only consider the first alternative. This will break once mysql-5.6 gets replaced by mysql-5.7 (or whatever else). This will break in stretch in case mysql-5.6 leaves stretch. And even if secondary alternatives would be considered by the buildds - which provider of virtual-mysql-server-core should be installed? There is probably more than one ... So in this case you would really want a generic real package as first alternative: Build-Depends(-Indep): default-mysql-server-core | virtual-mysql-server-core except that we currently don't have default-mysql-server-core ... Andreas
Processed: Re: Bug#822243: calligra: RM calligra [ANY] -- RC-buggy, FTBFS, blocks removal of no-longer-built packages
Processing commands for cont...@bugs.debian.org: > reassign 822243 ftp.debian.org Bug #822243 [src:calligra] calligra: RM calligra [ANY] -- RC-buggy, FTBFS, blocks removal of no-longer-built packages Bug reassigned from package 'src:calligra' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #822243 to the same values previously set Ignoring request to alter fixed versions of bug #822243 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 822243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#822243: calligra: RM calligra [ANY] -- RC-buggy, FTBFS, blocks removal of no-longer-built packages
reassign 822243 ftp.debian.org thanks On Friday 22 April 2016 14:34:22 Tobias Frost wrote: > Source: calligra > Severity: serious > Justification: blocks removal of cruft / completion of transitions > > Hi, > > I know, calligra is a very diffult package to maintain, but unfortunatly it > has 4 RC bugs which prevents it to be rebuilt and therefore blocks several > packages to be removed -- to complete transitions. > > At the moment, according to #806454 and #817945 is not even installable, and > according to [1] the current and a prospective new maintainer has currently > no time. > > Therefore please consider to remove the *binary* packages from sid to help > untangle things: > - glew > - gsl > - hdf5 > - and removal of libpng 1.2 > > Please resond to this bug or -- if you agree -- reassign it to > ftp.debian.org. If there is no respone within a week, I willl reassign it > accordingly. (The RM bug will remove only the binary packages, source > should be kept if not decided otherwise by the ftp-masters) > > Please note that latest when we file for libpng1.2 removal, this needs to be > resolved, otherwise we will ask ftp.debian.org to remove calligara together > with libpng1.2 > > Thanks! As long as there is no active maintainer I don't see why we should keep RC binaries around. Removing the binaries for now sounds like a good idea in case someone misses calligra and steps over to maintain it. Else we can remove the source later. Kinds regards, Lisandro. -- They are plenty, a whole hurd of gnus. * pinotree turns OdyX upside down ˙snuƃ ɟo pɹnɥ ǝloɥʍ ɐ 'ʎʇuǝld ǝɹɐ ʎǝɥʇ gh (-: ˙ǝsɐǝןd 'dn ʞɔɐq ǝɯ uɹnʇ ǝsɐǝןd ʍou * pinotree turns OdyX upside down again Thank you. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#808463: non-free code in boot.c
Please see http://tuxera.com/forum/viewtopic.php?f=2&t=31104&sid=26bd6fc5dd9dc86f0170051a4c8fffe8 Jean-Pierre
Bug#790259: marked as done (ltt-control: FTBFS with glibc 2.21 and gcc-5)
Your message dated Fri, 22 Apr 2016 10:14:11 -0400 with message-id <20160422141411.GA9196@angus> and subject line Re: Bug#790259: ltt-control: FTBFS with glibc 2.21 and gcc-5 has caused the Debian Bug report #790259, regarding ltt-control: FTBFS with glibc 2.21 and gcc-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.) -- 790259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ltt-control Version: 2.6.0-1 Severity: normal >From my pbuilder build log, using a setup preferring glibc and gcc-defaults from experimental: ... /bin/bash ../../../libtool --tag=CC --mode=link gcc -Wall -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -g -fno-strict-aliasing -fPIE -pie -Wl,-z,relro -Wl,-z,now -o lttng conf.o commands/start.o commands/list.o commands/create.o commands/destroy.o commands/stop.o commands/enable_events.o commands/disable_events.o commands/enable_channels.o commands/disable_channels.o commands/add_context.o commands/set_session.o commands/version.o commands/calibrate.o commands/view.o commands/snapshot.o commands/save.o commands/load.o utils.o lttng.o ../../../src/lib/lttng-ctl/liblttng-ctl.la ../../../src/common/libcommon.la ../../../src/common/config/libconfig.la -lpopt -lpthread libtool: link: gcc -Wall -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -g -fno-strict-aliasing -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/lttng conf.o commands/start.o commands/list.o commands/create.o commands/destroy.o commands/stop.o commands/enable_events.o commands/disable_events.o commands/enable_channels.o commands/disable_channels.o commands/add_context.o commands/set_session.o commands/version.o commands/calibrate.o commands/view.o commands/snapshot.o commands/save.o commands/load.o utils.o lttng.o ../../../src/lib/lttng-ctl/.libs/liblttng-ctl.so ../../../src/common/.libs/libcommon.a -luuid -lrt ../../../src/common/config/.libs/libconfig.a -lxml2 /usr/lib/x86_64-linux-gnu/libpopt.so -lpthread ../../../src/common/.libs/libcommon.a(mi-lttng.o):(.data.rel.ro.local+0x0): multiple definition of `mi_lttng_element_snapshots' commands/enable_events.o:(.bss+0x30): first defined here collect2: error: ld returned 1 exit status Makefile:504: recipe for target 'lttng' failed make[5]: *** [lttng] Error 1 make[5]: Leaving directory '/tmp/buildd/ltt-control-2.6.0/src/bin/lttng' Makefile:406: recipe for target 'all-recursive' failed make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory '/tmp/buildd/ltt-control-2.6.0/src/bin' Makefile:401: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/tmp/buildd/ltt-control-2.6.0/src' Makefile:499: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/tmp/buildd/ltt-control-2.6.0' dh_auto_build: make -j1 V=1 returned exit code 2 debian/rules:14: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory '/tmp/buildd/ltt-control-2.6.0' debian/rules:11: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Daniel Schepler --- End Message --- --- Begin Message --- * Daniel Schepler wrote: > Source: ltt-control > Version: 2.6.0-1 > Severity: normal > > From my pbuilder build log, using a setup preferring glibc and gcc-defaults > from experimental: > > ... > /bin/bash ../../../libtool --tag=CC --mode=link gcc -Wall -g -O2 -fPIE > -fstack-protector-strong -Wformat -Werror=format-security -g > -fno-strict-aliasing -fPIE -pie -Wl,-z,relro -Wl,-z,now -o lttng conf.o > commands/start.o commands/list.o commands/create.o commands/destroy.o > commands/stop.o commands/enable_events.o commands/disable_events.o > commands/enable_channels.o commands/disable_channels.o commands/add_context.o > commands/set_session.o commands/version.o commands/calibrate.o > commands/view.o commands/snapshot.o commands/save.o commands/load.o utils.o > lttng.o ../../../src/lib/lttng-ctl/liblttng-ctl.la > ../../../src/common/libcommon.la ../../../src/common/config/libconfig.la > -lpopt -lpthread > libtool: link: gcc -Wall -g -O2 -fPIE -fstack-protector-strong -Wformat > -Werror=format-security -g -fno-strict-aliasing -fPIE -pie -Wl,-z -Wl,relro > -Wl,-z -Wl,now -o .libs/lttng conf.o commands/start.o commands/list.o > commands/create.o commands/destroy.o commands/stop.o commands/enable_events.
Bug#820291: node-seq: uninstallable in sid: Depends: node-chainsaw (< 0.1) but 0.1.0-1 is to be installed
Hi, I am not to worried about node-seq being removed from testing at the moment, as there are many other dependencies requiring packaging for browserify first. It looks like it is is not a simple matter of updating the Depends: field in debian/control. Cloning the upstream repo, merging some fixes for the testsuite from a fork, npm install'ing the dependencies gives me a passing test (Expresso is required for the tests - I must file a bug about that). npm update'ing the chainsaw dependency to 0.1.0 gives me the following test failure when running "npm test": uncaught undefined: RangeError: Maximum call stack size exceeded at action (/home/ross/github/node-seq/index.js:76:11) at call (/home/ross/github/node-seq/index.js:236:17) at Array.forEach (native) at Object.parEach (/home/ross/github/node-seq/index.js:230:17) at EventEmitter.saw.next (/home/ross/github/node-seq/node_modules/chainsaw/index.js:62:18) at Object.extend (/home/ross/github/node-seq/index.js:491:13) at EventEmitter.saw.next (/home/ross/github/node-seq/node_modules/chainsaw/index.js:62:18) at EventEmitter.saw.jump (/home/ross/github/node-seq/node_modules/chainsaw/index.js:143:13) at Function.cb (/home/ross/github/node-seq/index.js:39:21) at next (/home/ross/github/node-seq/index.js:266:26) I will need to see what changed in chainsaw. But I will probably concentrate on all the other browserify dependencies first. Regards, Ross signature.asc Description: OpenPGP digital signature
Bug#822243: calligra: RM calligra [ANY] -- RC-buggy, FTBFS, blocks removal of no-longer-built packages
Source: calligra Severity: serious Justification: blocks removal of cruft / completion of transitions Hi, I know, calligra is a very diffult package to maintain, but unfortunatly it has 4 RC bugs which prevents it to be rebuilt and therefore blocks several packages to be removed -- to complete transitions. At the moment, according to #806454 and #817945 is not even installable, and according to [1] the current and a prospective new maintainer has currently no time. Therefore please consider to remove the *binary* packages from sid to help untangle things: - glew - gsl - hdf5 - and removal of libpng 1.2 Please resond to this bug or -- if you agree -- reassign it to ftp.debian.org. If there is no respone within a week, I willl reassign it accordingly. (The RM bug will remove only the binary packages, source should be kept if not decided otherwise by the ftp-masters) Please note that latest when we file for libpng1.2 removal, this needs to be resolved, otherwise we will ask ftp.debian.org to remove calligara together with libpng1.2 Thanks! -- tobi -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#822242: libgd2: CVE-2016-3074: Signedness vulnerability causing heap overflow
Source: libgd2 Version: 2.1.1-4 Severity: grave Tags: security upstream patch fixed-upstream Hi, the following vulnerability was published for libgd2. CVE-2016-3074[0]: Signedness vulnerability causing heap overflow 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-3074 [1] https://github.com/libgd/libgd/commit/2bb97f407c1145c850416a3bfbcc8cf124e68a19 Please adjust the affected versions in the BTS as needed. Salvatore
Bug#816440: marked as done (openjdk-9-jdk: file conflict jawt.h)
Your message dated Fri, 22 Apr 2016 11:01:31 +
with message-id
and subject line Bug#816440: fixed in openjdk-9 9~b115-1
has caused the Debian Bug report #816440,
regarding openjdk-9-jdk: file conflict jawt.h
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.)
--
816440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-9-jdk
Version: 9~b107-1
Running with a clean experimental chroot, openjdk-9-jdk has a file
conflict with openjdk-9-jdk-headless (9~b107-1).
Here is the truncated output of "apt-get install openjdk-9-jdk":
Unpacking openjdk-9-jdk:amd64 (9~b107-1) ...
dpkg: error processing archive
/var/cache/apt/archives/openjdk-9-jdk_9~b107-1_amd64.deb (--unpack):
trying to overwrite
'/usr/lib/jvm/java-9-openjdk-amd64/include/jawt.h', which is also in
package openjdk-9-jdk-headless:amd64 9~b107-1
https://piuparts.debian.org/experimental/fail/openjdk-9-jdk_9~b107-1.log
Thanks,
Joe Ferguson
--- End Message ---
--- Begin Message ---
Source: openjdk-9
Source-Version: 9~b115-1
We believe that the bug you reported is fixed in the latest version of
openjdk-9, 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 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose (supplier of updated openjdk-9 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: Thu, 21 Apr 2016 23:48:04 +0200
Source: openjdk-9
Binary: openjdk-9-jdk-headless openjdk-9-jre-headless openjdk-9-jdk
openjdk-9-jre openjdk-9-demo openjdk-9-source openjdk-9-doc openjdk-9-dbg
openjdk-9-jre-zero
Architecture: source amd64 all
Version: 9~b115-1
Distribution: experimental
Urgency: medium
Maintainer: OpenJDK Team
Changed-By: Matthias Klose
Description:
openjdk-9-dbg - Java runtime based on OpenJDK (debugging symbols)
openjdk-9-demo - Java runtime based on OpenJDK (demos and examples)
openjdk-9-doc - OpenJDK Development Kit (JDK) documentation
openjdk-9-jdk - OpenJDK Development Kit (JDK)
openjdk-9-jdk-headless - OpenJDK Development Kit (JDK) (headless)
openjdk-9-jre - OpenJDK Java runtime, using ${vm:Name}
openjdk-9-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
openjdk-9-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
openjdk-9-source - OpenJDK Development Kit (JDK) source files
Closes: 816440
Changes:
openjdk-9 (9~b115-1) experimental; urgency=medium
.
* OpenJDK 9, b115.
* Fix header file conflict. Closes: #816440. LP: #1550950.
Checksums-Sha1:
8b4299a104d2fdda67ba08f7592cd91d957402f7 4379 openjdk-9_9~b115-1.dsc
0f36a1695468e260f59197c5a44ed231227d9cef 69080126 openjdk-9_9~b115.orig.tar.gz
e7cff732204a8119cf9993de602927c5f78f034f 229169 openjdk-9_9~b115-1.diff.gz
86e0b9280d463c4fe68969e829e2fec811d4d97a 155022672
openjdk-9-dbg_9~b115-1_amd64.deb
201db429cad080891e0951dcfacecddb030a186c 1576674
openjdk-9-demo_9~b115-1_amd64.deb
6cdd580eea8a32868b2585be268d0f530097132a 13594302
openjdk-9-doc_9~b115-1_all.deb
326c7b4f58c160fd27a93434c726f3861184dcdc 328044
openjdk-9-jdk-headless_9~b115-1_amd64.deb
1b90c0be1b6acf18a75aa36a7e5e14b3b7e7c4e1 16538 openjdk-9-jdk_9~b115-1_amd64.deb
a639e7237269fcba9b05100d9c925d33b2b1606d 183614898
openjdk-9-jre-headless_9~b115-1_amd64.deb
ef40c8a197c2571e38016ac75acf962b6e70e671 2132830
openjdk-9-jre-zero_9~b115-1_amd64.deb
5b7ca7a925154b9bcd3da755011ec7333859c2a3 51270 openjdk-9-jre_9~b115-1_amd64.deb
6f6582600900e5559c218067b9fc29c8413083ca 48033552
openjdk-9-source_9~b115-1_all.deb
Checksums-Sha256:
263b55ca05241cf00d06777b03087d0e9de48d98770f9c01a3d64b43298dee7b 4379
openjdk-9_9~b115-1.dsc
c4152dcd943a3a8eb35d91e6592b1cf2896871f3bebd1c2445511993da8566b6 69080126
openjdk-9_9~b115.orig.tar.gz
fd8a1f8a80a32bdc390d6eb342116107f04d2b6ae77f6effc422476c223e0d50 229169
openjdk-9_9~b115-1.diff.gz
cc7bbf3cd436e4213f4b5ebb5e2c85b6df85059b2ef77c0e3b5b8fa209e789f4 155022672
openjdk-9-dbg_9~b115-1_amd64.deb
19967a420b8a596327dea9b57e6d52f2ee29a1a23bc622ae821f56a21096785c 1576674
openjdk-9-demo_9~b115-1_amd64.deb
70561d510021ad4040260f63bc7c8d4e69190c077212914573a8843c004f9
Bug#791094: marked as done (libbpp-phyl: library transition may be needed when GCC 5 is the default)
Your message dated Fri, 22 Apr 2016 11:00:30 + with message-id and subject line Bug#791094: fixed in libbpp-phyl 2.2.0-1 has caused the Debian Bug report #791094, regarding libbpp-phyl: library transition may be needed when GCC 5 is the default 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.) -- 791094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-phyl Version: 2.1.0-1 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for "BEGIN GCC CXX11" in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append "v5" to the name of the package (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag + transition block by 790756 reassign release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition --- End Message --- --- Begin Message --- Source: libbpp-phyl Source-Version: 2.2.0-1 We believe that the bug you reported is fixed in the latest version of libbpp-phyl, 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 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libbpp-phyl 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: Thu, 21 Apr 2016 14:16:41 +0200 Source: libbpp-phyl Binary: libbpp-phyl-dev libbpp-phyl9v5 Architecture: source amd64 Version: 2.2.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libbpp-phyl-dev - Bio++ Phylogenetic library development files libbpp-phyl9v5 - Bio++ Phylogenetic library Closes: 791094 Changes: libbpp-phyl (2.2.0-1) unstable; urgency=medium . * New upstream version * Moved packaging to Git * Better description * Team maintenance in Debian Med team * cme fix dpkg-control * Source package section: science * Add watch file * debhelper 9 * DEP5 * short dh rules file using d-shlib
Bug#791098: marked as done (libbpp-raa: library transition may be needed when GCC 5 is the default)
Your message dated Fri, 22 Apr 2016 11:00:31 + with message-id and subject line Bug#791098: fixed in libbpp-raa 2.2.0-1 has caused the Debian Bug report #791098, regarding libbpp-raa: library transition may be needed when GCC 5 is the default 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.) -- 791098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-raa Version: 2.1.0-1 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for "BEGIN GCC CXX11" in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append "v5" to the name of the package (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag + transition block by 790756 reassign release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition --- End Message --- --- Begin Message --- Source: libbpp-raa Source-Version: 2.2.0-1 We believe that the bug you reported is fixed in the latest version of libbpp-raa, 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 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libbpp-raa 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: Thu, 21 Apr 2016 17:52:34 +0200 Source: libbpp-raa Binary: libbpp-raa-dev libbpp-raa1v5 Architecture: source amd64 Version: 2.2.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libbpp-raa-dev - Bio++ Remote Acnuc Access library development files libbpp-raa1v5 - Bio++ Remote Acnuc Access library Closes: 791098 Changes: libbpp-raa (2.2.0-1) unstable; urgency=medium . * New upstream version * Moved packaging to Git * Add watch file * Add homepage * Team maintenance in Debian Med team * cme fix dpkg-control * debhelper 9 * Source package in Section: science * short dh rules file using d-shlibs * Libra
Bug#821100: [debian-mysql] Bug#821100: MySQL 5.5.49 for Oracle April 2016 CPU
Hi Robie, On Fri, Apr 22, 2016 at 09:52:44AM +0100, Robie Basak wrote: > On Thu, Apr 21, 2016 at 07:13:34PM +0200, Salvatore Bonaccorso wrote: > > Do you have any status-update for this for us? > > Struggling to find an available and willing sponsor, sorry. Lars has had > his tree ready for a while. > > I am DM for src:mysql-5.6, but not for src:mysql-5.5 (that's just a > technicality, I could be added I suppose) but I think you said that this > needs a DD? Yes thats (unfortunately) still the case. You need to be a DD for now, to upload to security-master. DM uploads are not yet implemented. > Unfortunately this means that Lars passes his work to me for review, and > then I pass it to a sponsor for upload, so it's a bit slow. > > My usual sponsoring DD for MySQL is also an Ubuntu dev and is busy this > week (it being Ubuntu release week) so hasn't been able to spare any > time for me on this. I'll continue to seek a sponsor. > > If anyone else can help please, the trees are at: > > http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/log/ > http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/log/?h=debian/wheezy > > In my judgement (as a DM for mysql-5.6), Lars' work here is correct and > ready to upload. Can you provide me the resulting (signed) source package? In that case I can build and upload it instead (but would like not to deal with the packaging git repository, in case it has some workflows to use). Regards, Salvatore
Processed: reassign 821942 to libnet-dns-perl, fixed 821942 in 1.05-2, affects 821942 ...
Processing commands for cont...@bugs.debian.org:
> reassign 821942 libnet-dns-perl 1.05-1
Bug #821942 {Done: Axel Beckert }
[libnet-dns-perl,libnet-dns-sec-perl] libnet-dns-sec-perl: Errors were
encountered while processing: libnet-dns-sec-perl
Bug #820332 {Done: Axel Beckert }
[libnet-dns-perl,libnet-dns-sec-perl] libnet-dns-perl: Conflict with
libnet-dns-sec-perl but not in Conflicts
Bug reassigned from package 'libnet-dns-perl,libnet-dns-sec-perl' to
'libnet-dns-perl'.
Bug reassigned from package 'libnet-dns-perl,libnet-dns-sec-perl' to
'libnet-dns-perl'.
No longer marked as found in versions libnet-dns-perl/1.05-1 and
libnet-dns-sec-perl/0.21-1.
No longer marked as found in versions libnet-dns-sec-perl/0.21-1 and
libnet-dns-perl/1.05-1.
No longer marked as fixed in versions libnet-dns-perl/1.05-2.
No longer marked as fixed in versions libnet-dns-perl/1.05-2.
Bug #821942 {Done: Axel Beckert } [libnet-dns-perl]
libnet-dns-sec-perl: Errors were encountered while processing:
libnet-dns-sec-perl
Bug #820332 {Done: Axel Beckert } [libnet-dns-perl]
libnet-dns-perl: Conflict with libnet-dns-sec-perl but not in Conflicts
Marked as found in versions libnet-dns-perl/1.05-1.
Marked as found in versions libnet-dns-perl/1.05-1.
> fixed 821942 1.05-2
Bug #821942 {Done: Axel Beckert } [libnet-dns-perl]
libnet-dns-sec-perl: Errors were encountered while processing:
libnet-dns-sec-perl
Bug #820332 {Done: Axel Beckert } [libnet-dns-perl]
libnet-dns-perl: Conflict with libnet-dns-sec-perl but not in Conflicts
Marked as fixed in versions libnet-dns-perl/1.05-2.
Marked as fixed in versions libnet-dns-perl/1.05-2.
> affects 821942 + libnet-dns-sec-perl
Bug #821942 {Done: Axel Beckert } [libnet-dns-perl]
libnet-dns-sec-perl: Errors were encountered while processing:
libnet-dns-sec-perl
Bug #820332 {Done: Axel Beckert } [libnet-dns-perl]
libnet-dns-perl: Conflict with libnet-dns-sec-perl but not in Conflicts
Added indication that 821942 affects libnet-dns-sec-perl
Added indication that 820332 affects libnet-dns-sec-perl
> notfound 822139 0.5.0-1~bpo8+1
Bug #822139 {Done: Harlan Lieberman-Berg } [letsencrypt]
Not installable on jessie-backports
No longer marked as found in versions python-letsencrypt/0.5.0-1~bpo8+1.
> found 821383 5.7.0-1
Bug #821383 {Done: Mike Gabriel } [mate-menu]
mate-menu: fail with maximize windows
Marked as found in versions mate-menu/5.7.0-1.
> notfound 821383 5.7.1-1
Bug #821383 {Done: Mike Gabriel } [mate-menu]
mate-menu: fail with maximize windows
No longer marked as found in versions mate-menu/5.7.1-1.
> notfound 812395 2016.01+dfsg1-1
Bug #812395 {Done: Vagrant Cascadian } [u-boot-tools]
u-boot-tools: sheevaplug /etc/fw_env.config - explain how env address depends
on your version of u-boot.
No longer marked as found in versions u-boot/2016.01+dfsg1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
812395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812395
820332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820332
821383: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821383
821942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821942
822139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 822085, found 822085 in 5.34.19+dfsg-1.2, severity of 822075 is normal, tagging 822104
Processing commands for cont...@bugs.debian.org: > tags 822085 + sid Bug #822085 [src:root-system] RM: root-system: RoQA unmaintained, RC-buggy, FTBFS, blocks removal of old packages Added tag(s) sid. > found 822085 5.34.19+dfsg-1.2 Bug #822085 [src:root-system] RM: root-system: RoQA unmaintained, RC-buggy, FTBFS, blocks removal of old packages Marked as found in versions root-system/5.34.19+dfsg-1.2. > severity 822075 normal Bug #822075 [apt-file] apt-file: Fails to install apt-file-2.5.4 due to requiring older perl-base-5.20 Severity set to 'normal' from 'grave' > tags 822104 + sid stretch Bug #822104 [src:guessnet] guessnet: FTBFS: *** libiw not found. Check 'config.log' for more details. Added tag(s) sid and stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 822075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822075 822085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822085 822104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#801321: marked as done (commons-javaflow: depends on obsolete libasm2-java library)
Your message dated Fri, 22 Apr 2016 09:49:24 + with message-id and subject line Bug#801321: fixed in commons-javaflow 0.0~svn20151101-1 has caused the Debian Bug report #801321, regarding commons-javaflow: depends on obsolete libasm2-java library 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.) -- 801321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: commons-javaflow Severity: important User: pkg-java-maintain...@lists.alioth.debian.org Usertags: oldlibs libasm2-java Hi, commons-javaflow depends on libasm2-java, which is obsolete and was replaced by libasm4-java. commons-javaflow should be ported to the new libasm4-java version, so that we can remove the old, unmaintained one. There are only four packages in Debian which depend on libasm2-java: - substance - liblaf-widget-java - jasperreports - commons-javaflow substance and liblaf-widget-java are both five years old and there is no indication of upstream development. substance is a build-dependency of jajuk which is still actively developed but the Debian package is outdated. jasperreports is also severely outdated. commons-javaflow has no reverse-dependencies and a very low popcon value. It would be great to "save" the first three packages, commons-javaflow should probably be removed. Regards, Markus --- End Message --- --- Begin Message --- Source: commons-javaflow Source-Version: 0.0~svn20151101-1 We believe that the bug you reported is fixed in the latest version of commons-javaflow, 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 801...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated commons-javaflow 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, 22 Apr 2016 10:05:13 +0200 Source: commons-javaflow Binary: libcommons-javaflow-java libcommons-javaflow-java-doc Architecture: source Version: 0.0~svn20151101-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Description: libcommons-javaflow-java - Apache Commons Javaflow (Sandbox) libcommons-javaflow-java-doc - Documentation for Apache Commons Javaflow (Sandbox) Closes: 801321 Changes: commons-javaflow (0.0~svn20151101-1) unstable; urgency=medium . * Team upload. * New upstream snapshot. * Declare compliance with Debian Policy 3.9.8. * Vcs-fields: Use https. * Switch from cdbs to dh sequencer. * New build system: Switch to Maven and use maven-debian-helper. * Use compat level 9 and require debhelper >= 9. * Switch to libasm-java. (Closes: #801321) * Add libcommons-io-java to Build-Depends. Remove libbcel-java. * Use Maven substvars instead of manually depending on packages. * Do not depend on default-jre-headless | java2-runtime-headless. * Update package description. * Remove debian/build.xml and debian/pom.xml. * Use debian/copyright format 1.0. Checksums-Sha1: 3830969c9ffe30b1ccdb90cf48147c72aad9d864 2626 commons-javaflow_0.0~svn20151101-1.dsc dd4833b53299f812c1a8584b182285b639b326cf 72164 commons-javaflow_0.0~svn20151101.orig.tar.gz 87be06debcfdc191dff1864329917fb6f85f438d 3996 commons-javaflow_0.0~svn20151101-1.debian.tar.xz Checksums-Sha256: 7d294d257f9a7d189030cb8f58bae02a3418484461e84e459f9f8b10161e9252 2626 commons-javaflow_0.0~svn20151101-1.dsc dd9e2013e09d07b9fe528c7a9a393792c39e48aa3846ef3ddb83588dc1a28daa 72164 commons-javaflow_0.0~svn20151101.orig.tar.gz 1219159ba79721c7ab2426e769a9737559840c668e8c60a88fbdbe95f04aebb1 3996 commons-javaflow_0.0~svn20151101-1.debian.tar.xz Files: 10df7a3f5281c2c2658f8dd5fa1c78b4 2626 java optional commons-javaflow_0.0~svn20151101-1.dsc 8133fb4ce2d52aee89cc4b326e28 72164 java optional commons-javaflow_0.0~svn20151101.orig.tar.gz 4ed24a28fb77e61b0bc59b835b84e2e8 3996 java optional commons-javaflow_0.0~svn20151101-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJXGeUCXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgz
Bug#822118: [Debian-med-packaging] Bug#822118: RM: fw4spl -- RoQA, unmaintained, RC-buggy, FTBFS, blocks removal of old packages
On Thu, Apr 21, 2016 at 08:42:58PM +0200, Corentin Desfarges wrote: > As I said to Andreas a few weeks ago, the FW4SPL team is currently > working on a new version of the framework using VTK6, ITK4, and the > new Boost version. > > We should be able to remove the dependences to the old versions of > these packages over the next week. I didn't notice it, but the binary RM was already processed, so currently there are no fw4spl binaries in debian. So this is not really a problem anymore for us, yet of course we would like to see this completely fixed. > About libpng, I'm not sure to understand. FW4SPL depends on > libpng-dev, and if I refers to the sid packages list, libpng-dev is > related to libpng1.6, not libpng1.2. The package couldn't be rebuild, so there was still the old binary that depended on libpng12. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#821100: [debian-mysql] Bug#821100: MySQL 5.5.49 for Oracle April 2016 CPU
On Thu, Apr 21, 2016 at 07:13:34PM +0200, Salvatore Bonaccorso wrote: > Do you have any status-update for this for us? Struggling to find an available and willing sponsor, sorry. Lars has had his tree ready for a while. I am DM for src:mysql-5.6, but not for src:mysql-5.5 (that's just a technicality, I could be added I suppose) but I think you said that this needs a DD? Unfortunately this means that Lars passes his work to me for review, and then I pass it to a sponsor for upload, so it's a bit slow. My usual sponsoring DD for MySQL is also an Ubuntu dev and is busy this week (it being Ubuntu release week) so hasn't been able to spare any time for me on this. I'll continue to seek a sponsor. If anyone else can help please, the trees are at: http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/log/ http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/log/?h=debian/wheezy In my judgement (as a DM for mysql-5.6), Lars' work here is correct and ready to upload. Robie
Bug#819235: closing 819235
close 819235 thanks Hi, xdg-app can now be installed. Closing Cheers, Laurent Bigonville
Processed: closing 819235
Processing commands for cont...@bugs.debian.org: > close 819235 Bug #819235 [xdg-app] xdg-app: unable to install, missing dependencies Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 819235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#810209: yt: Please update dependency on libpng-dev
Source: yt Followup-For: Bug #810209 Looking into it (with my limited pyhton knowledge), I think it is using matplot lib for its png need: File yt/utilities/png_writer.py: (...) import matplotlib._png as _png (...) if MPL_VERSION < MPL_API_2_VERSION: def call_png_write_png(buffer, width, height, filename, dpi): _png.write_png(buffer, width, height, filename, dpi) else: def call_png_write_png(buffer, width, height, filename, dpi): _png.write_png(buffer, filename, dpi) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
