Processed: tagging 595298
Processing commands for cont...@bugs.debian.org:
# squeeze has linux 2.6.32
tags 595298 + wheezy sid
Bug #595298 {Done: Romain Beauxis to...@rastageeks.org} [oss4-dkms]
oss4-dkms: linux 2.6.36 not supported
Added tag(s) sid and wheezy.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
595298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656943: engauge-digitizer FTBFS on armel and armhf due to not maintaining proper distinctions between double and qreal
package: engauge-digitizer
severity: serious
tags: patch
version: 5.0-1
The latest upload of engauge-digitizer failed on armel and armhf with
the following erors
src/digitview.cpp:293:61: error: no matching function for call to
'QMatrix::map(double, double, double*, double*) const'
src/digitview.cpp:293:61: note: candidates are:
/usr/include/qt4/QtGui/qmatrix.h:80:10: note: void QMatrix::map(int, int, int*,
int*) const
/usr/include/qt4/QtGui/qmatrix.h:80:10: note: no known conversion for
argument 3 from 'double*' to 'int*'
/usr/include/qt4/QtGui/qmatrix.h:81:10: note: void QMatrix::map(qreal, qreal,
qreal*, qreal*) const
/usr/include/qt4/QtGui/qmatrix.h:81:10: note: no known conversion for
argument 3 from 'double*' to 'qreal* {aka float*}'
/usr/include/qt4/QtGui/qmatrix.h:85:12: note: QPoint QMatrix::map(const
QPoint) const
/usr/include/qt4/QtGui/qmatrix.h:85:12: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:86:13: note: QPointF QMatrix::map(const
QPointF) const
/usr/include/qt4/QtGui/qmatrix.h:86:13: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:87:11: note: QLine QMatrix::map(const QLine)
const
/usr/include/qt4/QtGui/qmatrix.h:87:11: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:88:12: note: QLineF QMatrix::map(const
QLineF) const
/usr/include/qt4/QtGui/qmatrix.h:88:12: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:89:15: note: QPolygonF QMatrix::map(const
QPolygonF) const
/usr/include/qt4/QtGui/qmatrix.h:89:15: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:90:14: note: QPolygon QMatrix::map(const
QPolygon) const
/usr/include/qt4/QtGui/qmatrix.h:90:14: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:91:13: note: QRegion QMatrix::map(const
QRegion) const
/usr/include/qt4/QtGui/qmatrix.h:91:13: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:92:18: note: QPainterPath QMatrix::map(const
QPainterPath) const
/usr/include/qt4/QtGui/qmatrix.h:92:18: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:123:30: note: QRect QMatrix::map(const QRect)
const
/usr/include/qt4/QtGui/qmatrix.h:123:30: note: candidate expects 1 argument,
4 provided
src/digitview.cpp:295:68: error: no matching function for call to
'QMatrix::map(double, double, double*, double*) const'
src/digitview.cpp:295:68: note: candidates are:
/usr/include/qt4/QtGui/qmatrix.h:80:10: note: void QMatrix::map(int, int, int*,
int*) const
/usr/include/qt4/QtGui/qmatrix.h:80:10: note: no known conversion for
argument 3 from 'double*' to 'int*'
/usr/include/qt4/QtGui/qmatrix.h:81:10: note: void QMatrix::map(qreal, qreal,
qreal*, qreal*) const
/usr/include/qt4/QtGui/qmatrix.h:81:10: note: no known conversion for
argument 3 from 'double*' to 'qreal* {aka float*}'
/usr/include/qt4/QtGui/qmatrix.h:85:12: note: QPoint QMatrix::map(const
QPoint) const
/usr/include/qt4/QtGui/qmatrix.h:85:12: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:86:13: note: QPointF QMatrix::map(const
QPointF) const
/usr/include/qt4/QtGui/qmatrix.h:86:13: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:87:11: note: QLine QMatrix::map(const QLine)
const
/usr/include/qt4/QtGui/qmatrix.h:87:11: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:88:12: note: QLineF QMatrix::map(const
QLineF) const
/usr/include/qt4/QtGui/qmatrix.h:88:12: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:89:15: note: QPolygonF QMatrix::map(const
QPolygonF) const
/usr/include/qt4/QtGui/qmatrix.h:89:15: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:90:14: note: QPolygon QMatrix::map(const
QPolygon) const
/usr/include/qt4/QtGui/qmatrix.h:90:14: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:91:13: note: QRegion QMatrix::map(const
QRegion) const
/usr/include/qt4/QtGui/qmatrix.h:91:13: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:92:18: note: QPainterPath QMatrix::map(const
QPainterPath) const
/usr/include/qt4/QtGui/qmatrix.h:92:18: note: candidate expects 1 argument, 4
provided
/usr/include/qt4/QtGui/qmatrix.h:123:30: note: QRect QMatrix::map(const QRect)
const
/usr/include/qt4/QtGui/qmatrix.h:123:30: note: candidate expects 1 argument,
4 provided
src/digitview.cpp: In member function 'QRect DigitView::convertZoom(QRect,
bool)':
src/digitview.cpp:305:70: error: no matching function for call to
'QMatrix::map(double, double, double*, double*) const'
src/digitview.cpp:305:70: note: candidates are:
/usr/include/qt4/QtGui/qmatrix.h:80:10: note: void QMatrix::map(int, int, int*,
int*) const
/usr/include/qt4/QtGui/qmatrix.h:80:10: note: no
Bug#655842: mess seen if defoma is installed
I installed defoma in order to remove it. And got the following mess. At least it removed it. # aptitude full-upgrade The following packages will be upgraded: fonts-arphic-uming 1 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 0 B/10.6 MB of archives. After unpacking 56.3 kB will be freed. Do you want to continue? [Y/n/?] Selecting previously unselected package fonts-arphic-uming. (Reading database ... 11 files and directories currently installed.) Preparing to replace fonts-arphic-uming 0.2.20080216.2-1 (using .../fonts-arphic-uming_0.2.20080216.2-2_all.deb) ... /etc/defoma/hints/ttf-arphic-uming.hints: Unable to open, or empty. #!/bin/sh -xv set -e + set -e # Purge leftovers from the old package if present PACKAGE=ttf-arphic-uming + PACKAGE=ttf-arphic-uming ... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652795: ovito: diff for NMU version 0.9.2-1.1
tags 652795 + patch
tags 652795 + pending
thanks
Dear maintainer,
I've prepared an NMU for ovito (versioned as 0.9.2-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
Regards.
-Steve
diff -Nru ovito-0.9.2/debian/changelog ovito-0.9.2/debian/changelog
--- ovito-0.9.2/debian/changelog 2010-10-30 16:46:45.0 -0500
+++ ovito-0.9.2/debian/changelog 2012-01-22 20:11:46.0 -0600
@@ -1,3 +1,11 @@
+ovito (0.9.2-1.1) unstable; urgency=low
+
+ * Non-Maintainer Upload.
+
+ * patches/boost1.48: New. Work around moc limitation. Closes: #652795.
+
+ -- Steve M. Robbins s...@debian.org Sun, 22 Jan 2012 20:11:46 -0600
+
ovito (0.9.2-1) unstable; urgency=low
* Initial release (Closes: #600812)
diff -Nru ovito-0.9.2/debian/patches/boost1.48 ovito-0.9.2/debian/patches/boost1.48
--- ovito-0.9.2/debian/patches/boost1.48 1969-12-31 18:00:00.0 -0600
+++ ovito-0.9.2/debian/patches/boost1.48 2012-01-22 15:37:34.0 -0600
@@ -0,0 +1,98 @@
+Description: Work around moc limitations
+ Some parts of Boost, introduced in Boost 1.48 are not
+ understood by the limited C++ parser of moc. This
+ patch defines header guards that prevent the troublesome boost
+ headers from being processed.
+Bug-Debian: #652795
+Author: Tobias Frost t...@coldtobi.de
+Reviewed-By: Steve Robbins s...@debian.org
+
+
+--- a/src/atomviz/CMakeLists.txt
b/src/atomviz/CMakeLists.txt
+@@ -199,7 +199,7 @@
+ ENDIF(OVITO_BUILD_PLUGIN_SCRIPTING)
+
+ # Use the QT meta-object compiler to generate additional code.
+-QT4_WRAP_CPP(AtomViz_MOC_SRCS ${AtomViz_MOC_HDRS})
++QT4_WRAP_CPP(AtomViz_MOC_SRCS ${AtomViz_MOC_HDRS} OPTIONS -DBOOST_TT_HAS_OPERATOR_HPP_INCLUDED)
+
+ # Generate plugin module.
+ ADD_LIBRARY(AtomViz
+--- a/src/base/CMakeLists.txt
b/src/base/CMakeLists.txt
+@@ -58,7 +58,7 @@
+ )
+
+ # Use the QT meta-object compiler to generate additional code.
+-QT4_WRAP_CPP(Base_MOC_SRCS ${Base_MOC_HDRS})
++QT4_WRAP_CPP(Base_MOC_SRCS ${Base_MOC_HDRS} OPTIONS -DBOOST_TT_HAS_OPERATOR_HPP_INCLUDED)
+
+ # Create shared library.
+ ADD_LIBRARY(Base
+--- a/src/core/CMakeLists.txt
b/src/core/CMakeLists.txt
+@@ -354,7 +354,7 @@
+ )
+
+ # Use the QT meta-object compiler to generate additional code.
+-QT4_WRAP_CPP(Core_MOC_SRCS ${Core_MOC_HDRS})
++QT4_WRAP_CPP(Core_MOC_SRCS ${Core_MOC_HDRS} OPTIONS -DBOOST_TT_HAS_OPERATOR_HPP_INCLUDED)
+
+ # Include a resource file in the library.
+ QT4_ADD_RESOURCES(Core_RC_SRCS resources/core.qrc)
+--- a/src/crystalanalysis/CMakeLists.txt
b/src/crystalanalysis/CMakeLists.txt
+@@ -79,7 +79,7 @@
+ ENDIF(OVITO_BUILD_PLUGIN_SCRIPTING)
+
+ # Use the QT meta-object compiler to generate additional code.
+-QT4_WRAP_CPP(CrystalAnalysis_MOC_SRCS ${CrystalAnalysis_MOC_HDRS})
++QT4_WRAP_CPP(CrystalAnalysis_MOC_SRCS ${CrystalAnalysis_MOC_HDRS} OPTIONS -DBOOST_TT_HAS_OPERATOR_HPP_INCLUDED)
+
+ # Generate plugin module.
+ ADD_LIBRARY(CrystalAnalysis
+--- a/src/povray/CMakeLists.txt
b/src/povray/CMakeLists.txt
+@@ -60,7 +60,7 @@
+ ENDIF(OVITO_BUILD_PLUGIN_SCRIPTING)
+
+ # Use the QT meta-object compiler to generate additional code.
+-QT4_WRAP_CPP(POVRay_MOC_SRCS ${POVRay_MOC_HDRS})
++QT4_WRAP_CPP(POVRay_MOC_SRCS ${POVRay_MOC_HDRS} OPTIONS -DBOOST_TT_HAS_OPERATOR_HPP_INCLUDED)
+
+ # Create plugin library.
+ ADD_LIBRARY(POVRay
+--- a/src/scripting/CMakeLists.txt
b/src/scripting/CMakeLists.txt
+@@ -54,7 +54,7 @@
+ )
+
+ # Use the QT meta-object compiler to generate additional code.
+-QT4_WRAP_CPP(Scripting_MOC_SRCS ${Scripting_MOC_HDRS})
++QT4_WRAP_CPP(Scripting_MOC_SRCS ${Scripting_MOC_HDRS} OPTIONS -DBOOST_TT_HAS_OPERATOR_HPP_INCLUDED )
+
+ # Create plugin library.
+ ADD_LIBRARY(Scripting
+--- a/src/scripting_gui/CMakeLists.txt
b/src/scripting_gui/CMakeLists.txt
+@@ -53,7 +53,7 @@
+ )
+
+ # Use the QT meta-object compiler to generate additional code.
+-QT4_WRAP_CPP(Scripting_gui_MOC_SRCS ${Scripting_gui_MOC_HDRS})
++QT4_WRAP_CPP(Scripting_gui_MOC_SRCS ${Scripting_gui_MOC_HDRS} OPTIONS -DBOOST_TT_HAS_OPERATOR_HPP_INCLUDED)
+
+ # Create plugin library.
+ ADD_LIBRARY(ScriptingGUI
+--- a/src/stdobjects/CMakeLists.txt
b/src/stdobjects/CMakeLists.txt
+@@ -54,7 +54,7 @@
+ )
+
+ # Use the QT meta-object compiler to generate additional code.
+-QT4_WRAP_CPP(StdObjects_MOC_SRCS ${StdObjects_MOC_HDRS})
++QT4_WRAP_CPP(StdObjects_MOC_SRCS ${StdObjects_MOC_HDRS} OPTIONS -DBOOST_TT_HAS_OPERATOR_HPP_INCLUDED )
+
+ # Create plugin library.
+ ADD_LIBRARY(StdObjects
diff -Nru ovito-0.9.2/debian/patches/series ovito-0.9.2/debian/patches/series
--- ovito-0.9.2/debian/patches/series 2010-10-29 08:58:04.0 -0500
+++ ovito-0.9.2/debian/patches/series 2012-01-22 15:05:23.0 -0600
@@ -1 +1,2 @@
debian-changes-0.9.2-1~2
+boost1.48
signature.asc
Description: Digital signature
Processed: ovito: diff for NMU version 0.9.2-1.1
Processing commands for cont...@bugs.debian.org: tags 652795 + patch Bug #652795 [src:ovito] ovito: FTBFS: usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at BOOST_JOIN Added tag(s) patch. tags 652795 + pending Bug #652795 [src:ovito] ovito: FTBFS: usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at BOOST_JOIN Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 652795: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656377: CVE-2011-3919
Hi,
Attached is the patch I plan to apply as an nmu fixing an RC bug in
this package.
Best wishes,
Mike
diff -u libxml2-2.7.8.dfsg/parser.c libxml2-2.7.8.dfsg/parser.c
--- libxml2-2.7.8.dfsg/parser.c
+++ libxml2-2.7.8.dfsg/parser.c
@@ -2709,7 +2709,7 @@
buffer[nbchars++] = '';
if (nbchars buffer_size - i - XML_PARSER_BUFFER_SIZE) {
- growBuffer(buffer, XML_PARSER_BUFFER_SIZE);
+ growBuffer(buffer, i + XML_PARSER_BUFFER_SIZE);
}
for (;i 0;i--)
buffer[nbchars++] = *cur++;
diff -u libxml2-2.7.8.dfsg/debian/changelog libxml2-2.7.8.dfsg/debian/changelog
--- libxml2-2.7.8.dfsg/debian/changelog
+++ libxml2-2.7.8.dfsg/debian/changelog
@@ -1,3 +1,10 @@
+libxml2 (2.7.8.dfsg-6.1) unstable; urgency=high
+
+ * Non-maintainer upload by the Security Team.
+ * Fix CVE-2011-3919: buffer overflow in parser.c (closes: #656377).
+
+ -- Michael Gilbert michael.s.gilb...@gmail.com Sun, 22 Jan 2012 16:29:49 -0500
+
libxml2 (2.7.8.dfsg-6) unstable; urgency=low
* Team upload.
Bug#656950: scid-data fails to install during upgrade
Package: scid Version: 1:4.3.0.cvs20111216-1 Severity: serious scid fails to upgrade due to a conflict with scid-data: ... Selecting previously unselected package scid-data. Unpacking scid-data (from .../scid-data_1%3a4.3.0.cvs20111216-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/scid-data_1%3a4.3.0.cvs20111216-1_all.deb (--unpack): trying to overwrite '/usr/share/scid/data/scid.eco', which is also in package scid 1:4.3.0.cvs20110714-2 configured to not write apport reports dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to replace scid 1:4.3.0.cvs20110714-2 (using .../scid_1%3a4.3.0.cvs20111216-1_amd64.deb) ... Unpacking replacement scid ... ... Errors were encountered while processing: /var/cache/apt/archives/scid-data_1%3a4.3.0.cvs20111216-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: ... dpkg: dependency problems prevent configuration of scid: scid depends on scid-data (= 1:4.3.0.cvs20111216-1); however: Package scid-data is not installed. dpkg: error processing scid (--configure): dependency problems - leaving unconfigured ... Errors were encountered while processing: scid Current status: 1 broken [+1], 13 updates [-85]. -- System Information: Debian Release: wheezy/sid APT prefers experimental APT policy: (1900, 'experimental'), (1800, 'unstable'), (1700, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages scid-data recommends: iu scid 1:4.3.0.cvs20111216-1 -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: severity of 656951 is serious
Processing commands for cont...@bugs.debian.org: severity 656951 serious Bug #656951 [fonts-arphic-uming] fonts-arphic-uming: fails to upgrade on a system without defoma installed Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 656951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656377: marked as done (libxml2: [PATCH] fix for CVE-2011-3919)
Your message dated Mon, 23 Jan 2012 06:47:43 +
with message-id e1rpdgt-00046k...@franck.debian.org
and subject line Bug#656377: fixed in libxml2 2.7.8.dfsg-7
has caused the Debian Bug report #656377,
regarding libxml2: [PATCH] fix for CVE-2011-3919
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.)
--
656377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libxml2
Version: 2.7.8.dfsg-5.1
Severity: grave
Tags: patch security
Justification: user security hole
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu precise ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* SECURITY UPDATE: denial of service via buffer overflow
- parser.c: fix an allocation error when copying entities
- 5bd3c061823a8499b27422aee04ea20aae24f03e
- CVE-2011-3919
Thanks for considering the patch.
References:
http://git.gnome.org/browse/libxml2/commit/?id=5bd3c061823a8499b27422aee04ea20aae24f03e
http://src.chromium.org/svn/trunk/src/third_party/libxml/README.chromium
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-3919
http://googlechromereleases.blogspot.com/2012/01/stable-channel-update.html
-- System Information:
Debian Release: wheezy/sid
APT prefers precise-updates
APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500,
'precise')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-8-generic (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
diff -u libxml2-2.7.8.dfsg/parser.c libxml2-2.7.8.dfsg/parser.c
--- libxml2-2.7.8.dfsg/parser.c
+++ libxml2-2.7.8.dfsg/parser.c
@@ -2709,7 +2709,7 @@
buffer[nbchars++] = '';
if (nbchars buffer_size - i - XML_PARSER_BUFFER_SIZE) {
- growBuffer(buffer, XML_PARSER_BUFFER_SIZE);
+ growBuffer(buffer, i + XML_PARSER_BUFFER_SIZE);
}
for (;i 0;i--)
buffer[nbchars++] = *cur++;
diff -u libxml2-2.7.8.dfsg/debian/changelog libxml2-2.7.8.dfsg/debian/changelog
---End Message---
---BeginMessage---
Source: libxml2
Source-Version: 2.7.8.dfsg-7
We believe that the bug you reported is fixed in the latest version of
libxml2, which is due to be installed in the Debian FTP archive:
libxml2-dbg_2.7.8.dfsg-7_i386.deb
to main/libx/libxml2/libxml2-dbg_2.7.8.dfsg-7_i386.deb
libxml2-dev_2.7.8.dfsg-7_i386.deb
to main/libx/libxml2/libxml2-dev_2.7.8.dfsg-7_i386.deb
libxml2-doc_2.7.8.dfsg-7_all.deb
to main/libx/libxml2/libxml2-doc_2.7.8.dfsg-7_all.deb
libxml2-utils_2.7.8.dfsg-7_i386.deb
to main/libx/libxml2/libxml2-utils_2.7.8.dfsg-7_i386.deb
libxml2_2.7.8.dfsg-7.diff.gz
to main/libx/libxml2/libxml2_2.7.8.dfsg-7.diff.gz
libxml2_2.7.8.dfsg-7.dsc
to main/libx/libxml2/libxml2_2.7.8.dfsg-7.dsc
libxml2_2.7.8.dfsg-7_i386.deb
to main/libx/libxml2/libxml2_2.7.8.dfsg-7_i386.deb
python-libxml2-dbg_2.7.8.dfsg-7_i386.deb
to main/libx/libxml2/python-libxml2-dbg_2.7.8.dfsg-7_i386.deb
python-libxml2_2.7.8.dfsg-7_i386.deb
to main/libx/libxml2/python-libxml2_2.7.8.dfsg-7_i386.deb
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 656...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrew O. Shadura bugzi...@tut.by (supplier of updated libxml2 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...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 20 Jan 2012 12:54:41 +0300
Source: libxml2
Binary: libxml2 libxml2-utils libxml2-dev libxml2-dbg libxml2-doc
python-libxml2 python-libxml2-dbg
Architecture: source i386 all
Version: 2.7.8.dfsg-7
Distribution: unstable
Urgency: low
Maintainer: Debian XML/SGML Group debian-xml-sgml-p...@lists.alioth.debian.org
Changed-By: Andrew O. Shadura bugzi...@tut.by
Description:
libxml2- GNOME XML library
libxml2-dbg - Debugging symbols for the GNOME XML library
libxml2-dev - Development files for the GNOME XML library
libxml2-doc - Documentation for the GNOME XML library
libxml2-utils - XML utilities
python-libxml2 - Python bindings for the GNOME XML library
python-libxml2-dbg - Python bindings for the GNOME XML library (debug
extension)
Closes: 656377
Changes:
libxml2 (2.7.8.dfsg-7) unstable; urgency=high
.
* Team
Bug#656388: RM: tucan -- RoM
retitle 656388 RM: tucan -- RoM
severity 656388 normal
reassign 656388 ftp.debian.org
thanks
Hi,
The upstream is not active since May of 2011[0], furthermore the
update plugins process is not secure and many plugins don't work,
please remove tucan from the archive.
[0] http://code.google.com/p/tucan/source/list
In advance, thank you so much.
Kind regards,
--
Julián Moreno Patiño
.''`. Debian GNU/{Linux,KfreeBSD}
: :' : Free Operating Systems
`. `' http://debian.org/
`- PGP KEY ID 6168BF60
Registered GNU Linux User ID 488513
signature.asc
Description: Digital signature
Processed: RM: tucan -- RoM
Processing commands for cont...@bugs.debian.org: retitle 656388 RM: tucan -- RoM Bug #656388 [tucan] tucan: insecure update mechanism Changed Bug title to 'RM: tucan -- RoM' from 'tucan: insecure update mechanism' severity 656388 normal Bug #656388 [tucan] RM: tucan -- RoM Severity set to 'normal' from 'grave' reassign 656388 ftp.debian.org Bug #656388 [tucan] RM: tucan -- RoM Bug reassigned from package 'tucan' to 'ftp.debian.org'. Bug No longer marked as found in versions tucan/0.3.9-1. thanks Stopping processing here. Please contact me if you need assistance. -- 656388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656953: [openshot] Segmentation fault at startup, different to #643562
Package: openshot Version: 1.4.0-1 Severity: critical --- Please enter the report below this line. --- $ openshot - ERROR 1 -- Failed to import 'from openshot import main' Error Message: cannot import name main OpenShot (version 1.4.0) Process no longer exists: 14767. Creating new pid lock file. mlt_repository_init: failed to dlopen /usr/lib/mlt/libmltavformat.so (libmlt.so.2: cannot open shared object file: No such file or directory) No LADSPA plugins were found! Check your LADSPA_PATH environment variable. Detecting formats, codecs, and filters... Segmentation fault --- System information. --- Architecture: i386 Kernel: Linux 3.1.0-9.dmz.1-liquorix-686 Debian Release: wheezy/sid 500 unstablew3you.com 500 unstableliquorix.net 500 unstableftp.hr.debian.org 500 unstabledeb.opera.com 500 unstableaptosid.com 500 testing ftp.hr.debian.org 500 stable ftp.hr.debian.org 500 stable dl.google.com 500 experimentalmozilla.debian.net 100 experimental-snapshots qt-kde.debian.net 1 experimentalftp.hr.debian.org --- Package information. --- Depends (Version) | Installed ===-+- gtk2-engines-pixbuf | 2.24.8-3 fontconfig | 2.8.0-3 librsvg2-common | 2.34.2-2 melt| 0.7.6+git20111222-1 python-gtk2 | 2.24.0-2 python-httplib2 | 0.7.2-1 python-imaging | 1.1.7-4 python-mlt3 | 0.7.6+git20111222-1 OR python-mlt2 | python-pygoocanvas | 0.14.1-1+b3 python-xdg | 0.19-3 python (= 2.5) | 2.7.2-9 python-support (= 0.90.0) | 1.0.14 Recommends (Version) | Installed =-+-=== openshot-doc | frei0r-plugins| 1.1.22git20091109-1.1 Suggests (Version) | Installed ===-+-=== blender(= 2.5) | 2.61-1 inkscape| 0.49.0+bzr10609 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Add epoch to version found
Processing commands for cont...@bugs.debian.org: # Add the epoch to the version found so that version tracking will # handle it properly. found 656789 1:4.3.0.cvs20111216-1 Bug #656789 [src:scid] scid: FTBFS: fatal error: tcl.h: No such file or directory Bug Marked as found in versions scid/1:4.3.0.cvs20111216-1. notfound 656789 4.3.0.cvs20111216-1 Bug #656789 [src:scid] scid: FTBFS: fatal error: tcl.h: No such file or directory The source scid and version do not appear to match any binary packages Bug No longer marked as found in versions scid/4.3.0.cvs20111216-1. -- Stopping processing here. Please contact me if you need assistance. -- 656789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656717: marked as done (libzen FTBFS on most 32-bit architectures, overload error)
Your message dated Sun, 22 Jan 2012 09:02:39 + with message-id e1rotjv-0001nj...@franck.debian.org and subject line Bug#656717: fixed in libzen 0.4.23-4 has caused the Debian Bug report #656717, regarding libzen FTBFS on most 32-bit architectures, overload error 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.) -- 656717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: libzen severity: serious libzen failed to build on most* 32-bit architectures with the following error ../../../Source/ZenLib/Ztring.h:201:13: error: 'ZenLib::Ztring ZenLib::Ztring::From_Number(size_t, ZenLib::int8u)' cannot be overloaded ../../../Source/ZenLib/Ztring.h:186:13: error: with 'ZenLib::Ztring ZenLib::Ztring::From_Number(ZenLib::int32u, ZenLib::int8u)' ../../../Source/ZenLib/Ztring.h:318:19: error: 'static ZenLib::Ztring ZenLib::Ztring::ToZtring(size_t, ZenLib::int8u)' cannot be overloaded ../../../Source/ZenLib/Ztring.h:310:19: error: with 'static ZenLib::Ztring ZenLib::Ztring::ToZtring(ZenLib::int32u, ZenLib::int8u)' *Strangely s390 succeeded, I dunno why. ---End Message--- ---BeginMessage--- Source: libzen Source-Version: 0.4.23-4 We believe that the bug you reported is fixed in the latest version of libzen, which is due to be installed in the Debian FTP archive: libzen-dev_0.4.23-4_amd64.deb to main/libz/libzen/libzen-dev_0.4.23-4_amd64.deb libzen-doc_0.4.23-4_all.deb to main/libz/libzen/libzen-doc_0.4.23-4_all.deb libzen0_0.4.23-4_amd64.deb to main/libz/libzen/libzen0_0.4.23-4_amd64.deb libzen_0.4.23-4.debian.tar.gz to main/libz/libzen/libzen_0.4.23-4.debian.tar.gz libzen_0.4.23-4.dsc to main/libz/libzen/libzen_0.4.23-4.dsc 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 656...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chow Loong Jin hyper...@debian.org (supplier of updated libzen 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 22 Jan 2012 15:26:40 +0800 Source: libzen Binary: libzen-dev libzen0 libzen-doc Architecture: source amd64 all Version: 0.4.23-4 Distribution: unstable Urgency: low Maintainer: Chow Loong Jin hyper...@debian.org Changed-By: Chow Loong Jin hyper...@debian.org Description: libzen-dev - ZenLib C++ utility library -- development files libzen-doc - ZenLib C++ utility library -- documentation libzen0- ZenLib C++ utility library -- runtime Closes: 656717 Changes: libzen (0.4.23-4) unstable; urgency=low . * [75c6135] Fix NEED_SIZET patch to avoid 32-bit breakage. Thanks to Peter Green (Closes: #656717) * [1ae30af] Install arch-specific libzenconfig.h to libzen-dev Checksums-Sha1: dddefcecb456598e0bc852a6c5d2cfb2a4aac1d6 1950 libzen_0.4.23-4.dsc cfd5d112b609ded35b59c494c8d709e607d7fdc1 9253 libzen_0.4.23-4.debian.tar.gz 87b7604b835f73817911abce1c5ad779faa9c573 41118 libzen-dev_0.4.23-4_amd64.deb 2708712e041fd0c2a0f0a82fdff68eeb5973e971 121820 libzen0_0.4.23-4_amd64.deb 09361c69da9f4ca4c1dcbed3f94036097658cf66 578740 libzen-doc_0.4.23-4_all.deb Checksums-Sha256: 0a3cc3e422327e2ac811cef53bb32e5a17c68c3311001395494a2bb575a3fd10 1950 libzen_0.4.23-4.dsc ea180fe93c255ea9d26c4f38d29b8bd519becf97dc6b8bcec483f13853b851d6 9253 libzen_0.4.23-4.debian.tar.gz 45ebff307e1c17cdeee5bd8c5d7f2f78cd15b3eea66f8f3bcab78fb39137b468 41118 libzen-dev_0.4.23-4_amd64.deb 4a8efeaa74c886ed11edbf213b7ca3cc7e180e905f1daefa3dc1a34c7b87aa7c 121820 libzen0_0.4.23-4_amd64.deb 629fd81b80e83b4527b3d560d3719905790e1ad66ca049938991e2913ccefb45 578740 libzen-doc_0.4.23-4_all.deb Files: fe7af0b6adee911ec2bd739b612b2847 1950 libs optional libzen_0.4.23-4.dsc e45335571444ac10ce4817f03520d340 9253 libs optional libzen_0.4.23-4.debian.tar.gz 350e1b076d3175b141d3730d1132dc13 41118 libdevel optional libzen-dev_0.4.23-4_amd64.deb d842c61e885c2bdca0d7e0ea4cc14376 121820 libs optional libzen0_0.4.23-4_amd64.deb 53a92b02eb69890d87e29fb8a256c515 578740 doc optional libzen-doc_0.4.23-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJPG73LAAoJEPvVIltYh1Khe0QP+QGmiroiggX1nnq4GkP6BShN
Bug#656113: wims: fails to install - bin/mkindex: cannot create mkindex.log: Permission denied
Hello Andreas, thank you for the notification. I tried to reproduce the failure you described. I could reproduce it *once*: - pbuilder login == creates a directory /var/cache/pbuilder/build/foo - cp wims*_4.02-1_amd64.deb /var/cache/pbuilder/build/foo/tmp == copies of relevant packages - cd /var/cache/pbuilder/build/foo/; dpkg -i tmp/*deb == fails to install due to missing dependencies. By the way, i noticed a strange quirk: the package adduser was missing. - apt-get -f install == downloads dependencies, and installs them, then tries to install wims : then I could reproduce the failure you noticed! However my pbuilder archive (for ARCH=amd64, DIST=sid) was not refreshed. So I made another try: - pbuilder update - pbuilder login - cd /var/cache/pbuilder/build/foo; apt-get install wims And then the package wims was properly installed. Running this sequence again gave the same result, of course. So my opinion is that at some time the environment provided by Sid missed some feature, which is missing no longer, now. In my opinion, this bug report should closed, as the bug is not reproducible. What is your idea about it? Best regards, Georges. Andreas Beckmann a écrit : Package: wims Version: 4.02-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package wims. (Reading database ... 26747 files and directories currently installed.) Unpacking wims (from .../archives/wims_4.02-5_amd64.deb) ... Adding system user `wims' (UID 102) ... Adding new group `wims' (GID 105) ... Adding new user `wims' (UID 102) with group `wims' ... Not creating home directory `/var/lib/wims'. Adding system user `nowims' (UID 103) ... Adding new group `nowims' (GID 106) ... Adding new user `nowims' (UID 103) with group `nowims' ... Not creating home directory `/'. Processing triggers for wims-modules ... Indexed 21 modules. Indexed 0 cn sheets. Indexed 27 en sheets. Indexed 0 es sheets. Indexed 321 fr sheets. Indexed 19 it sheets. Indexed 48 nl sheets. bin/mkindex: 194: bin/mkindex: cannot create mkindex.log: Permission denied bin/mkindex: 199: bin/mkindex: cannot create index.log: Permission denied oefdoc.pl en peut pas créer public_html/scripts/js/editor/scripts_1/bd_js/en/iff_bd.js at bin/oefdoc.pl line 430. dpkg: error processing wims-modules (--unpack): subprocess installed post-installation script returned error exit status 13 configured to not write apport reports Errors were encountered while processing: wims-modules The installation performed by piuparts is done with DEBIAN_FRONTEND=noninteractive and stdin redirected from /dev/null. cheers, Andreas -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 signature.asc Description: Digital signature
Processed: tagging #656113
Processing commands for cont...@bugs.debian.org: tags 656113 unreproducible moreinfo Bug #656113 [wims] wims: fails to install - bin/mkindex: cannot create mkindex.log: Permission denied Added tag(s) unreproducible and moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 656113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656204: this is in fact not an RC bug
Rolf Leggewie debian-b...@rolf.leggewie.biz (22/01/2012): The current package is installable just fine. While no doubt resulting in a bit of an ugly state, the update from one particular unstable package to another breaks but also works at least to the point of not leaving the package unusable and according to Paul there is also an easy workaround to resolve the situation. Nothing qualifying for grave severity that I can see. Erm. Breaking the dpkg configuration phase means you can break alot of other packages. On mine that was “just” glib*, gtk*, so the whole X session was totally broken. I find it highly irritating that nobody wanted to properly maintain this package for years and now that I've taken on this difficult task of cleaning up this year-long neglect everybody and their uncle thinks they know better how to do that. [ more whining ] Heh, welcome to maintaining libraries. The policy has details, lintian helps one not to trivial errors, and fixing the package (be it about where to ship this or that part of the -dev/lib packages, or about fixing upgradability issues) is AFAICT trivial. Why don't you just fix the package and move to other things? Mistakes happen every day, it's not the end of the world to have a grave bug in ones package if one learns about it and tries to avoid doing the same mistakes again. This bug never affected testing, it's in fact not an RC bug even for unstable itself. Anybody who blocks the current package from going to testing is not doing Debian a favour. Wrong. Policy 7.6 says it's an RC bug. Mraw, KiBi. signature.asc Description: Digital signature
Bug#652146: hwinfo: diff for NMU version 16.0-2.2
Steffen Winterfeldt wrote... On Wed, 18 Jan 2012, Christoph Biedl wrote: Steffen Winterfeldt wrote... Thanks! But shouldn't it be 'mov %%rbx,%%rdi' etc, then? Hm, why? cpuid affects only the lower 32 Bits. Using %rbx instead shouldn't do harm, though. No, the result is zero-extended to 64 bits in 64bit-mode. I stand corrected. (Call me Thomas, I wanted to see that with my own eye, this took a while, sorry about that.) By the way, I am quite confused by the fact cpuid with %eax set to 0 returns the ID in %ebx,%edx,%ecx while cpuid with %eax set to 0x4000 appearently returns, if running under xen, the ID in %ebx,%ecx,%edx, read: With %ecx and %edx in swapped order. Mind of you double-check your code does the right thing unless you've already done so? I don't have a Xen installation at hand to do this, they crashed or did other nasty things every time I've tried in the past six years. Christoph -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 656629 is forwarded to https://www.mozdev.org/bugs/show_bug.cgi?id=24683
Processing commands for cont...@bugs.debian.org: forwarded 656629 https://www.mozdev.org/bugs/show_bug.cgi?id=24683 Bug #656629 [enigmail] enigmail: OpenPGP menu does not appear in Icedove 8.0.2 Set Bug forwarded-to-address to 'https://www.mozdev.org/bugs/show_bug.cgi?id=24683'. thanks Stopping processing here. Please contact me if you need assistance. -- 656629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 624464, tagging 632106, tagging 632108, tagging 632262, tagging 632264, tagging 632265 ...
Processing commands for cont...@bugs.debian.org:
# most stuff (BTS, PTS, ...) use maintainer information from unstable only
tags 624464 + squeeze-ignore
Bug #624464 {Done: Julien Valroff jul...@debian.org} [rsakeyfind] rsakeyfind:
invalid maintainer address
Added tag(s) squeeze-ignore.
tags 632106 + squeeze-ignore
Bug #632106 {Done: Roland Dreier rol...@digitalvampire.org} [libibverbs]
libibverbs: Mails to Maintainer address are bouncing
Added tag(s) squeeze-ignore.
tags 632108 + squeeze-ignore
Bug #632108 {Done: Roland Dreier rol...@digitalvampire.org} [libmlx4]
libmlx4: Mails to Maintainer address are bouncing
Added tag(s) squeeze-ignore.
tags 632262 + squeeze-ignore
Bug #632262 {Done: Leo Iannacone l...@ubuntu.com} [src:upse] Invalid
maintainer address
Added tag(s) squeeze-ignore.
tags 632264 + squeeze-ignore
Bug #632264 {Done: Regis Boudin re...@debian.org} [src:pidgin-mpris] Invalid
maintainer address
Added tag(s) squeeze-ignore.
tags 632265 + squeeze-ignore
Bug #632265 {Done: Frank Lichtenheld dj...@debian.org} [src:pidgin-audacious]
Invalid maintainer address
Added tag(s) squeeze-ignore.
tags 632266 + squeeze-ignore
Bug #632266 {Done: Bart Martens ba...@debian.org} [src:gtkglext] Invalid
maintainer address
Added tag(s) squeeze-ignore.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
632266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632266
632264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632264
632108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632108
632106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632106
632262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632262
632265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632265
624464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#655151: python-newt: ImportError: No module named _snack
Package: python-newt Version: 0.52.14-7 Followup-For: Bug #655151 The bug is still present in 0.52.14-7 on amd64: |% python -c 'import snack' |Traceback (most recent call last): | File string, line 1, in module | File /usr/lib/python2.7/dist-packages/snack.py, line 42, in module |import _snack |ImportError: No module named _snack From the build log: |install: cannot stat `python2.6/_snackmodule.so': No such file or directory |install: cannot stat `python2.7/_snackmodule.so': No such file or directory -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (150, 'unstable'), (99, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-newt depends on: ii libnewt0.52 0.52.14-7 ii python 2.7.2-9 ii python2.62.6.7-4 ii python2.72.7.2-8 python-newt recommends no packages. python-newt suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656204: this is in fact not an RC bug
Thank you for your comment, Cyril. I'm not convinced but willing to listen. I hope you are, too. On 22.01.2012 18:30, Cyril Brulebois wrote: Erm. Breaking the dpkg configuration phase means you can break alot of other packages. On mine that was “just” glib*, gtk*, so the whole X session was totally broken. Then grave is the wrong severity, it should be critical. Are you now saying this bug is critical? Heh, welcome to maintaining libraries. Yes, I know. Much of the pain cannot be avoided. My frustration is about people who don't really know what's going on with the package making my life even more difficult than it already is or needs to be - and insisting on it for the wrong reasons, as it seems to me. fixing the package [...] is AFAICT trivial. Why don't you just fix the package and move to other things? Mistakes happen every day, it's not the end of the world to have a grave bug in ones package if one learns about it and tries to avoid doing the same mistakes again. See, this is one of the things I'm talking about. People only understand half the story (at best) and refuse to read explanations even after they were given several times. You for example are apparently still ignoring the fact that the fix for my mistake had been up well before this bug even went to grave status. I've stressed this fact in almost every comment I made here and you still missed it. Just one example of how my life gets more complicated than it should be. Again, I guess a certain level of this cannot be avoided in a collaborative effort, but the amount of it I'm seeing is frustrating. This bug never affected testing, it's in fact not an RC bug even for unstable itself. Anybody who blocks the current package from going to testing is not doing Debian a favour. Wrong. Policy 7.6 says it's an RC bug. Even if this was indeed the case, why should the package be kept from migrating to testing if the problem never affected testing? That's my idea of course and only covered by common sense not by Policy. In any case, 7.6 tells me how to get out of the hole (D'uh!) I had dug for myself. Nowhere does it say that the hole I dug is RC. Furthermore, grave severity implies either of the following three * data loss - obviously not * security hole - obviously not * makes package unusable - that's why normally this would be RC but it does not apply to this particular ticket, 656204 is a bit special I've also looked into whether this ticket is critical or serious and came to the conclusion it isn't. You and Adam were the ones to set it to grave, so you must have had one of the three reasons above. If you really look at it (as I have done) you will find it hard to justify the initial reflex of RC bug and most definitely of grave status. This came a bit as a surprise to me as well. Apparently, the package already migrated to testing, so this is merely an opportunity for me to learn more about policy now. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656204: this is in fact not an RC bug
Rolf Leggewie debian-b...@rolf.leggewie.biz (22/01/2012): Then grave is the wrong severity, it should be critical. Are you now saying this bug is critical? There might have been no other packages co-upgraded, so grave as “the package is unusable” is enough. My frustration is about people who don't really know what's going on with the package making my life even more difficult than it already is or needs to be - and insisting on it for the wrong reasons, as it seems to me. I'm not sure if I qualify for this description, AFAICT I only set the appropriate severity based on what I saw on my system and policy. fixing the package [...] is AFAICT trivial. Why don't you just fix the package and move to other things? Mistakes happen every day, it's not the end of the world to have a grave bug in ones package if one learns about it and tries to avoid doing the same mistakes again. See, this is one of the things I'm talking about. People only understand half the story (at best) and refuse to read explanations even after they were given several times. You for example are apparently still ignoring the fact that the fix for my mistake had been up well before this bug even went to grave status. I've stressed this fact in almost every comment I made here and you still missed it. You said there's a fix in git, but there's no fix in the archive. So setting the appropriate severity, affected versions, etc. is what is expected. I'm sorry you don't seem to like that. Just one example of how my life gets more complicated than it should be. Again, I guess a certain level of this cannot be avoided in a collaborative effort, but the amount of it I'm seeing is frustrating. I could say the same about people whining. Wrong. Policy 7.6 says it's an RC bug. Even if this was indeed the case, why should the package be kept from migrating to testing if the problem never affected testing? That's my idea of course and only covered by common sense not by Policy. We have suite-specific tags, which might have been used to reflect that, but of course challenging the severity repeatedly was much more interesting. I'm not throwing Adam's hat at you, but he's been handling RC bugs for a long while now, you might have just trusted his judgement. In any case, 7.6 tells me how to get out of the hole (D'uh!) I had dug for myself. Nowhere does it say that the hole I dug is RC. Furthermore, grave severity implies either of the following three * data loss - obviously not * security hole - obviously not * makes package unusable - that's why normally this would be RC but it does not apply to this particular ticket, 656204 is a bit special No it is not special. You claim it is. I've also looked into whether this ticket is critical or serious and came to the conclusion it isn't. You and Adam were the ones to set it to grave, so you must have had one of the three reasons above. If you really look at it (as I have done) you will find it hard to justify the initial reflex of RC bug and most definitely of grave status. This came a bit as a surprise to me as well. Please look again. (Oh and if you want Adam to look at it again, maybe you should be Ccing him.) Apparently, the package already migrated to testing, so this is merely an opportunity for me to learn more about policy now. Thank you so much for playing bug severity ping pong. Mraw, KiBi. signature.asc Description: Digital signature
Processed: reassign 656808 to libglib2.0-0, forcibly merging 656564 656808, severity of 656564 is critical
Processing commands for cont...@bugs.debian.org: reassign 656808 libglib2.0-0 Bug #656808 [gnome-settings-daemon] gnome-settings-daemon: segmentation fault after some use Bug reassigned from package 'gnome-settings-daemon' to 'libglib2.0-0'. Bug No longer marked as found in versions gnome-settings-daemon/3.2.2-2. forcemerge 656564 656808 Bug#656564: libglib2.0-0: since upgrade to 2.30.2-5 programs start segfaulting at random Bug#656808: gnome-settings-daemon: segmentation fault after some use Forcibly Merged 656564 656808. severity 656564 critical Bug #656564 [libglib2.0-0] libglib2.0-0: since upgrade to 2.30.2-5 programs start segfaulting at random Bug #656808 [libglib2.0-0] gnome-settings-daemon: segmentation fault after some use Severity set to 'critical' from 'important' Severity set to 'critical' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 656564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656564 656808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656755: Help with architecture not supporting SSE (Was: Bug#656755: libhmsbeagle FTBFS on everything except amd64)
Hi, I have to admit that I do not have any experience with SSE issues. Any advise what to do in cases like this (see build logs linked below)? The error message starts with libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../libhmsbeagle -I/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0 -I/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0 -O3 -c BeagleCPUSSEPlugin.cpp -fPIC -DPIC -o .libs/libhmsbeagle_cpu_sse_la-BeagleCPUSSEPlugin.o In file included from /build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/SSEDefinitions.h:37:0, from /build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.hpp:44, from /build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.h:240, from BeagleCPUSSEPlugin.cpp:9: /usr/lib/gcc/i486-gnu/4.6/include/emmintrin.h:32:3: error: #error SSE2 instruction set not enabled In file included from /build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/SSEDefinitions.h:39:0, from /build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.hpp:44, from /build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.h:240, from BeagleCPUSSEPlugin.cpp:9: /usr/lib/gcc/i486-gnu/4.6/include/xmmintrin.h:32:3: error: #error SSE instruction set not enabled In file included from /build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.hpp:44:0, from /build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.h:240, from BeagleCPUSSEPlugin.cpp:9: /build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/SSEDefinitions.h:52:10: error: '__m128d' does not name a type /build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/SSEDefinitions.h:80:2: error: 'V_Real' does not name a type In file included from /build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.h:240:0, from BeagleCPUSSEPlugin.cpp:9: Any help is welcome Andreas. On Sat, Jan 21, 2012 at 09:50:16PM +, Adam D. Barratt wrote: On Sat, 2012-01-21 at 17:16 +0100, Andreas Tille wrote: On Sat, Jan 21, 2012 at 03:00:25PM +, peter green wrote: It seems things are a little more complex than they first appeared. In particular it seems libhmsbeagle has a specific sse2 plugin which can only be built with sse2 enabled and that is built even if --enable-sse=no is passed (which seems like a bug in the upstream build system to me). Therefore disabling -msse2 has caused the package to FTBFS everywhere except amd64. For non pc architectures I would think the sse2 plugin should simply be disabled. Do you have any hint how I could find this plugin which should be disabled. [...] A failed build log would probably be helpful. I also have included upstream whether they might be able to give any hint about this issue: Predictably, https://buildd.debian.org/status/package.php?p=libhmsbeagle has several - the hurd-i386, powerpc and s390x logs all look like they fail whilst building libhmsbeagle_cpu_sse_la-BeagleCPUSSEPlugin.lo. Regards, Adam -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: messing around with stuff in /etc is grounds for RC status
Processing commands for cont...@bugs.debian.org: severity 197254 serious Bug #197254 [isdnutils-base] isdnutils-base: /etc/isdn/isdn.conf overwritten without warning on upgrade Severity set to 'serious' from 'normal' severity 331116 serious Bug #331116 [isdnlog] isdnlog: fails to purge Severity set to 'serious' from 'normal' tags 197254 help Bug #197254 [isdnutils-base] isdnutils-base: /etc/isdn/isdn.conf overwritten without warning on upgrade Added tag(s) help. tags 331116 help Bug #331116 [isdnlog] isdnlog: fails to purge Added tag(s) help. thank you Stopping processing here. Please contact me if you need assistance. -- 331116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=331116 197254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=197254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653779: Intent to NMU exult to fix pending po-debconf l10n bugs (and one RC bug)
Dear Debian maintainer, The exult Debian package, which you are the maintainer of, has pending bug report(s) which include translation updates or fixes for po-debconf, namely bug number 595628 (and maybe other similar bugs). The i18n team is now hunting the very last bits of missing localization and your package went on our radar. You may have uploaded recently but, unfortunately for you, you then got *another* l10n bug report. So, sorry for this, but the radar beeped at your package and here am I with an NMU intent...:-) I have the intention, as part of a more general action of the Debian i18n Task Force to build and possibly upload a non-maintainer upload for exult in order to fix this as well as all pending translations for the debconf templates. Of course, an upload made by you would even be better...:-) Such changes are always harmless, which explains why I safely consider building NMU's for such issues even though they're obviously non critical. The schedule for the NMU (in case it happens, that is if you agree with it or if I don't receive any answer in 2 days) is roughly the following: Sunday, January 22, 2012 : send this notice Thursday, January 26, 2012 : post a NMU announcement to debian-i18n with you (maintainer) CC'ed this can happen earlier if the maintainer agrees In such case, the deadlines below will also happen earlier Friday, February 03, 2012 : (midnight) deadline for receiving translation updates Saturday, February 04, 2012 : build the package and upload it to DELAYED/7-day send the NMU patch to the BTS Saturday, February 11, 2012 : NMU reaches incoming If you intent to upload yourself, please notify me so that I interrupt the process on my side. Please also don't upload without a discussion with me. Some translators might send a few new translations and I can handle a round of translation updates for you. Really, don't upload silently...:-) In case I upload an NMU, I will subscribe to the Package Tracking System for exult and follow its life for 60 days after my NMU in order to fix any issue potentially introduced by my upload. Let me know, as soon as possible, if you have any kind of objection to this process. If you'd rather do the fix yourself, I will of course leave the package alone. Same if you have reasons not to do the update now. -- signature.asc Description: Digital signature
Bug#656564: libglib2.0-0: since upgrade to 2.30.2-5 programs start segfaulting at random
Hi Michael,
On Fr, 20 Jan 2012, Michael Biebl wrote:
- Revert this commit and recompile glib2.0 to see if it fixes the crashes
THis is what I did, I disabled
94-closure-fix-handling-of-ENUMs-and-integral-return-ty.patch
recompiled and installed, but g-s-d still has the tendency to
die on me.
Anything else?
- Install libglib2.0-0-dbg and libffi5-dbg and get a backtrace or a core
dump. For the latter you'll probably need to adjust ulimit.
Where should I do that in the gnome-session path? /etc/profile?
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
Far out in the uncharted backwaters of the unfashionable
end of the western spiral arm of the Galaxy lies a small
unregarded yellow sun.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656564: libglib2.0-0: since upgrade to 2.30.2-5 programs start segfaulting at random
On 22.01.2012 15:48, Norbert Preining wrote: Hi Michael, On Fr, 20 Jan 2012, Michael Biebl wrote: - Revert this commit and recompile glib2.0 to see if it fixes the crashes THis is what I did, I disabled 94-closure-fix-handling-of-ENUMs-and-integral-return-ty.patch recompiled and installed, but g-s-d still has the tendency to die on me. Anything else? The complete commit also added patch 93-*.patch and modified the symbols file. It might be easier to just downgrade to -4 from testing. - Install libglib2.0-0-dbg and libffi5-dbg and get a backtrace or a core dump. For the latter you'll probably need to adjust ulimit. Where should I do that in the gnome-session path? /etc/profile? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656808#15 You should then get a core file in ~ whenever g-s-d crashes. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#590822: marked as done (python-jaxml: cannot be bytecompiled with Python 2.7: SyntaxError: cannot assign to __debug__)
Your message dated Sun, 22 Jan 2012 15:04:25 +
with message-id e1royy1-sl...@franck.debian.org
and subject line Bug#590822: fixed in jaxml 3.01-6.1
has caused the Debian Bug report #590822,
regarding python-jaxml: cannot be bytecompiled with Python 2.7: SyntaxError:
cannot assign to __debug__
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.)
--
590822: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-jaxml
Version: 3.01-5
Severity: wishlist
User: debian-pyt...@lists.debian.org
Usertags: python2.7
Hello,
jaxml.py cannot be bytecompiled with Python 2.7:
$ python2.7 -m compileall -q /usr/share/python-support/
Compiling /usr/share/python-support/python-jaxml/jaxml.py ...
SyntaxError: ('cannot assign to __debug__',
('/usr/share/python-support/python-jaxml/jaxml.py', 990, None, 'self.__debug__
= file\n'))
While we are not close to make Python 2.7 a supported version, please
consider fixing this bug anyway.
--
Jakub Wilk
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: jaxml
Source-Version: 3.01-6.1
We believe that the bug you reported is fixed in the latest version of
jaxml, which is due to be installed in the Debian FTP archive:
jaxml_3.01-6.1.diff.gz
to main/j/jaxml/jaxml_3.01-6.1.diff.gz
jaxml_3.01-6.1.dsc
to main/j/jaxml/jaxml_3.01-6.1.dsc
python-jaxml_3.01-6.1_all.deb
to main/j/jaxml/python-jaxml_3.01-6.1_all.deb
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 590...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated jaxml 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...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 20 Jan 2012 14:50:48 +0100
Source: jaxml
Binary: python-jaxml
Architecture: source all
Version: 3.01-6.1
Distribution: unstable
Urgency: low
Maintainer: Vanessa Gutiérrez vane...@gmail.com
Changed-By: gregor herrmann gre...@debian.org
Description:
python-jaxml - Python module for generating XML documents
Closes: 590822
Changes:
jaxml (3.01-6.1) unstable; urgency=low
.
* Non-maintainer upload.
.
[ Migual Landeata ]
* Assignment to __debug__, even as an attribute, is not allowed in
Python 2.7. See upstream tracker issue http://bugs.python.org/issue9438.
(LP: #719188) (Closes: #590822). Thanks to Xavier Bassery for the patch.
Checksums-Sha1:
a56db99496a49a895f7a9fa0e3182ba4a8966613 1757 jaxml_3.01-6.1.dsc
070aadede21af4c6b171b5351bc4cc70f5c4a1af 3352 jaxml_3.01-6.1.diff.gz
07a586d3ae25e5ca1059f7c2576e2c231678a9f2 26304 python-jaxml_3.01-6.1_all.deb
Checksums-Sha256:
8f41ea57d1bb1d711fbdd3ab38f2230ee492b0ae48c48a54049de0cc4612666d 1757
jaxml_3.01-6.1.dsc
d270a2cdae7da718c73472850623963d9d28ae1fa0630ef764c7753b9fb2f188 3352
jaxml_3.01-6.1.diff.gz
3006cda3433c2d0d2b052668ca84b554c647a61c89d29d9329737389dc391b55 26304
python-jaxml_3.01-6.1_all.deb
Files:
e29da07e02cf820027dbfa3cd673902b 1757 python optional jaxml_3.01-6.1.dsc
439675d6e8c1567f35196e411b87aa94 3352 python optional jaxml_3.01-6.1.diff.gz
1300f8478bd7780b95deb8f1a62ec3d4 26304 python optional
python-jaxml_3.01-6.1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBCAAGBQJPGXGXAAoJELs6aAGGSaoGFOgQAI3ef9XENC1qEqTyoHVBnUua
xpZEKOKgm6BLZGc4XFN5kMeYX6LSvH9FD+J+0+EzwzYxhXwUusxMrF9rR72U/nqi
4G+fpMbzHdRAhFhozWHCDbRIm+ELonHBgwfkY2r6oKMHy/IZRakdRqCGWB1KHh9X
ypzBB3161NSHHPRHverLTrpvBoY3DX9f6ZYxjSwgUWhx/+QQn/nNWxZaQK4jkp0G
SkxtuTcJOaAKuLPCVkWvZFP14NHY5bfHB0WUqlTlb5x4lq64xGvMMG+EBm8zJa8+
eNuUKZMMmq6EMYHe36gnOrR702jtIoDJ+w7JYrtrodUm5SFdYcHt90+Y1UxgAJO7
eKK1wZz5EGuV4oja5kiwJvio2ma/rz6CY7DeGEYuFWFsSijALLd1euyj2uYBAkUy
JX+MJnDNnkuNxfVL2m6gdAYLiUv+3AawjbyOxysan/2+0pDkkM8tKvgwEXP1O5yQ
nrKHwqjL+JmHxOZotG+EEBH4O5h4JmSEDaAh68vpOcQ3csKpPYWr7nz83bwdN34a
2sGuLiypN9AFVjoq5ujPaMSYXDGFc/0wIZNXrI39BS6cWa4so4BKT0yl0kKOQPWD
Z7plH61g6tq7LIgRo7hDZjVWBmIh8rb4bXmWOLVPDt3GJ5THOyF9cSqFlnO7tuiX
rSYpjqJoDBO20xoaQ2or
=24FS
-END PGP SIGNATURE-
---End Message---
Bug#654257: newlib: FTBFS: cannot find the library `sys/linux/liblinux.la' or unhandled argument `sys/linux/liblinux.la'
tag 654257 + patch thanks On Mon, 02 Jan 2012 16:47:33 +0100, Jakub Wilk wrote: Source: newlib Version: 1.18.0-6.1 Severity: serious Justification: fails to build from source The attached patch (taken from Ubuntu) fixes the FTBFS, but then we run into: % lintian -F newlib_1.18.0-6.2_i386.changes E: newlib-m68hc1x: arch-independent-package-contains-binary-or-object usr/m68hc11/lib/libc.a Not sure if a lintian override is ok here ... Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Rod Steward: Tonight's The Night diff -u newlib-1.18.0/debian/control newlib-1.18.0/debian/control --- newlib-1.18.0/debian/control +++ newlib-1.18.0/debian/control @@ -2,7 +2,7 @@ Section: devel Priority: extra Maintainer: Arthur Loiret aloi...@debian.org -Build-Depends: debhelper (= 6), quilt (= 0.40), texinfo, binutils-spu [powerpc ppc64], gcc-spu [powerpc ppc64], lzma +Build-Depends: debhelper (= 6), quilt (= 0.40), texinfo, binutils-spu [powerpc ppc64], gcc-spu [powerpc ppc64], lzma, dpkg-dev (= 1.16.0), linux-libc-dev (= 3.0.0-2) Build-Depends-Indep: gcc-m68hc1x Standards-Version: 3.9.1 diff -u newlib-1.18.0/debian/changelog newlib-1.18.0/debian/changelog --- newlib-1.18.0/debian/changelog +++ newlib-1.18.0/debian/changelog @@ -1,3 +1,19 @@ +newlib (1.18.0-6.2) unstable; urgency=low + + * Non-maintainer upload. + * Fix FTBFS: cannot find the library `sys/linux/liblinux.la' or +unhandled argument `sys/linux/liblinux.la': add patch from Ubuntu: +[ Wookey ] +* Fix build to work with co-installable (multiarched) linux-libc-dev + headers. LP: #750585. +[ Steve Langasek ] +* add a versioned build-dependency on linux-libc-dev and dpkg-dev for the + hard-coded multiarch paths. +(And adjust versions for linux-libc-dev and dpkg-dev.) +(Closes: #654257) + + -- gregor herrmann gre...@debian.org Sun, 22 Jan 2012 15:37:13 +0100 + newlib (1.18.0-6.1) unstable; urgency=medium * Non-maintainer upload. diff -u newlib-1.18.0/debian/rules newlib-1.18.0/debian/rules --- newlib-1.18.0/debian/rules +++ newlib-1.18.0/debian/rules @@ -3,6 +3,7 @@ DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) +DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) version:= $(shell dpkg-parsechangelog | grep ^Version | sed -e 's/^Version: //') uversion := $(shell echo $(version) | cut -d '-' -f1) diff -u newlib-1.18.0/debian/patches/series newlib-1.18.0/debian/patches/series --- newlib-1.18.0/debian/patches/series +++ newlib-1.18.0/debian/patches/series @@ -3,0 +4 @@ +65_multiarch-headers.patch only in patch2: unchanged: --- newlib-1.18.0.orig/debian/patches/65_multiarch-headers.patch +++ newlib-1.18.0/debian/patches/65_multiarch-headers.patch @@ -0,0 +1,26 @@ +Index: newlib-1.18.0/newlib/libc/sys/linux/Makefile.am +=== +--- newlib-1.18.0.orig/newlib/libc/sys/linux/Makefile.am 2011-04-07 12:39:43.0 + newlib-1.18.0/newlib/libc/sys/linux/Makefile.am2011-04-07 12:39:47.0 + +@@ -169,7 +169,7 @@ + + # This will handle both /usr/src/linux-2.4/include/asm/signal.h (in Red Hat Linux 7.1) + # and also /usr/src/linux/include/asm/signal.h in older versions of Red Hat Linux +-SIGNAL_H = /usr/include/asm/signal.h ++SIGNAL_H = /usr/include/$(DEB_HOST_MULTIARCH)/asm/signal.h + + liblinux_la_LDFLAGS = -Xcompiler -nostdlib + +Index: newlib-1.18.0/newlib/libc/sys/linux/Makefile.in +=== +--- newlib-1.18.0.orig/newlib/libc/sys/linux/Makefile.in 2011-04-07 12:57:39.0 + newlib-1.18.0/newlib/libc/sys/linux/Makefile.in2011-04-07 12:57:07.0 + +@@ -484,7 +484,7 @@ + + # This will handle both /usr/src/linux-2.4/include/asm/signal.h (in Red Hat Linux 7.1) + # and also /usr/src/linux/include/asm/signal.h in older versions of Red Hat Linux +-SIGNAL_H = /usr/include/asm/signal.h ++SIGNAL_H = /usr/include/$(DEB_HOST_MULTIARCH)/asm/signal.h + liblinux_la_LDFLAGS = -Xcompiler -nostdlib + ADD_OBJS = \ + $(LINUX_MACH_LIB) signature.asc Description: Digital signature
Processed: Re: Bug#654257: newlib: FTBFS: cannot find the library `sys/linux/liblinux.la' or unhandled argument `sys/linux/liblinux.la'
Processing commands for cont...@bugs.debian.org: tag 654257 + patch Bug #654257 [src:newlib] newlib: FTBFS: cannot find the library `sys/linux/liblinux.la' or unhandled argument `sys/linux/liblinux.la' Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 654257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#655789: Re: Bug#655789: wv - NMU to fix FTBFS new upstream release
Hello Dmitry, I have to say this version isn't okay. Because this version of libwv has an ABI bump, its SONAME has changed from libwv-1.2.so.3 to libwv-1.2.so.4. This requires a rename of the binary package: from libwv-1.2-3 to libwv-1.2-4. So please change it. (And read on, there is another change required.) http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html This will make a library transition in the archive because there are packages directly/indirectly depend on libwv, namely: mimedefang lyx mew mew-beta w3m-el w3m-el-snapshot gwrite swish-e horde3 namazu2-index-tools hyperestraier Doing a transition needs to coordinate with Release Team, and it would be great if you can upload the new package to _experimental_ before uploading to unstable, and with the time frame report bugs to respective dependent packages (if there are issues need them to fix) and so they can react. Note: issues can be fixed by a rebuild without source change does not need to be reported to maintainers of those packages. http://release.debian.org/transitions/ e.g. http://bugs.debian.org/656758 -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555483: FTBFS with binutils-gold
tags 555483 pending thanks Hi, I've prepared an NMU for logjam (versioned as 4.5.3-5.1) and I've uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Thanks. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reopening 655151
Processing commands for cont...@bugs.debian.org:
reopen 655151
Bug #655151 {Done: Alastair McKinstry mckins...@debian.org} [python-newt]
python-newt: ImportError: No module named _snack
thanks
Stopping processing here.
Please contact me if you need assistance.
--
655151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#655789: Re: Bug#655789: wv - NMU to fix FTBFS new upstream release
Also please explain: On Sun, Jan 22, 2012 at 22:31, Dmitry Smirnov only...@member.fsf.org wrote: + support for parallel build This is a small library, I don't see the necessity of using parallel build because it adds extra complexity to debian/rules. - disable static build Can you explain why you disable the production of static linked binary for a library package? -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653953: magicmaze: diff for NMU version 1.4.3.2.dfsg-1.1
tags 653953 + patch tags 653953 + pending thanks Dear maintainer, I've prepared an NMU for magicmaze (versioned as 1.4.3.2.dfsg-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Leonard Cohen: Jazz Police diff -u magicmaze-1.4.3.2.dfsg/debian/control magicmaze-1.4.3.2.dfsg/debian/control --- magicmaze-1.4.3.2.dfsg/debian/control +++ magicmaze-1.4.3.2.dfsg/debian/control @@ -8,7 +8,7 @@ Package: magicmaze Architecture: all -Depends: ruby, libsdl-ruby, ttf-isabella +Depends: ruby, libsdl-ruby, ttf-isabella (= 1.2-2) Description: rescue the maiden while avoiding the monsters This is a simple game where you are a wizard searching the evil demon's tower to try and rescue the beautiful maiden. Inspired by Gauntlet II, diff -u magicmaze-1.4.3.2.dfsg/debian/changelog magicmaze-1.4.3.2.dfsg/debian/changelog --- magicmaze-1.4.3.2.dfsg/debian/changelog +++ magicmaze-1.4.3.2.dfsg/debian/changelog @@ -1,3 +1,15 @@ +magicmaze (1.4.3.2.dfsg-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Fix magicmaze searches for Isabella.ttf in wrong place, crashes.: +- add patch 20_isabella.dpatch: adjust fontfile variable to point to new + location of Isabella.ttf +- debian/control: make dependency on ttf-isabella versioned +Thanks to Raphael Wimmer for the bug report. +(Closes: #653953) + + -- gregor herrmann gre...@debian.org Sun, 22 Jan 2012 16:33:43 +0100 + magicmaze (1.4.3.2.dfsg-1) unstable; urgency=low * The Now with DFSG-free orig tarball! release diff -u magicmaze-1.4.3.2.dfsg/debian/patches/00list magicmaze-1.4.3.2.dfsg/debian/patches/00list --- magicmaze-1.4.3.2.dfsg/debian/patches/00list +++ magicmaze-1.4.3.2.dfsg/debian/patches/00list @@ -1,0 +2 @@ +20_isabella only in patch2: unchanged: --- magicmaze-1.4.3.2.dfsg.orig/debian/patches/20_isabella.dpatch +++ magicmaze-1.4.3.2.dfsg/debian/patches/20_isabella.dpatch @@ -0,0 +1,20 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 20_isabella.dpatch by gregor herrmann gre...@debian.org +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: Update path to Isabella.ttf +## DP: Bug-Debian: http://bugs.debian.org/653953 + +@DPATCH@ +diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' magicmaze-1.4.3.2.dfsg~/magicmaze/graphics.rb magicmaze-1.4.3.2.dfsg/magicmaze/graphics.rb +--- magicmaze-1.4.3.2.dfsg~/magicmaze/graphics.rb 2012-01-22 16:26:48.0 +0100 magicmaze-1.4.3.2.dfsg/magicmaze/graphics.rb 2012-01-22 16:27:14.0 +0100 +@@ -99,7 +99,7 @@ + @font32 = SDL::TTF.open( fontfile, fontsize.last * SCALE_FACTOR ) + rescue SDL::Error = err + # Debian font +- fontfile = /usr/share/fonts/truetype/Isabella.ttf ++ fontfile = /usr/share/fonts/truetype/ttf-isabella/Isabella.ttf + fontsize = [12, 28] + if tries 1 then + tries += 1 # to avoid loop. signature.asc Description: Digital signature
Processed: magicmaze: diff for NMU version 1.4.3.2.dfsg-1.1
Processing commands for cont...@bugs.debian.org: tags 653953 + patch Bug #653953 [magicmaze] magicmaze searches for Isabella.ttf in wrong place, crashes. Added tag(s) patch. tags 653953 + pending Bug #653953 [magicmaze] magicmaze searches for Isabella.ttf in wrong place, crashes. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 653953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649408: gnome-keyring: no socket to connect to
Package: gnome-keyring Version: 3.2.2-1 Followup-For: Bug #649408 I still have the same message on an up-to-date Sid system dist-upgraded today. I am on Xfce and it interferes with ncmpcpp when I connect to LastFM with it I can see the gnome-keyring message appearing on the screen. It happens only for the first time I open ncmpcpp. I guess I could remove the package gnome-keyring from my system, but am not sure for what I would need it. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-keyring depends on: ii dbus-x11 1.4.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3 ii libc62.13-24 ii libcap-ng0 0.6.6-1 ii libcap2-bin 1:2.22-1 ii libdbus-1-3 1.4.16-1 ii libgck-1-0 3.2.2-1 ii libgcr-3-1 3.2.2-1 ii libgcrypt11 1.5.0-3 ii libglib2.0-0 2.30.2-5 ii libgtk-3-0 3.2.3-1 Versions of packages gnome-keyring recommends: ii libpam-gnome-keyring 3.2.2-1 gnome-keyring suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656877: linux-image-2.6.32-5-kirkwood: Unable to modprobe sd_mod and thus to mount USB devices
Package: linux-2.6 Version: 2.6.32-39squeeze1 Severity: grave Justification: renders package unusable # modprobe sd_mod FATAL: Error inserting sd_mod (/lib/modules/2.6.32-5-kirkwood/kernel/drivers/scsi/sd_mod.ko): Unknown symbol in module, or unknown parameter (see dmesg) # dmesg|tail […] [ 1213.753328] sd_mod: Unknown symbol scsi_verify_blk_ioctl [ 1213.764231] sd_mod: Unknown symbol scsi_cmd_blk_ioctl -- Package-specific info: ** Version: Linux version 2.6.32-5-kirkwood (Debian 2.6.32-38) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Mon Oct 3 16:55:04 UTC 2011 ** Command line: console=ttyS0,115200 ** Not tainted ** Kernel log: [0.250978] TCP bind hash table entries: 16384 (order: 4, 65536 bytes) [0.251157] TCP: Hash tables configured (established 16384 bind 16384) [0.251167] TCP reno registered [0.251316] NET: Registered protocol family 1 [0.251488] Unpacking initramfs... [0.390735] Freeing initrd memory: 2284K [0.390844] NetWinder Floating Point Emulator V0.97 (double precision) [0.391091] audit: initializing netlink socket (disabled) [0.391124] type=2000 audit(0.380:1): initialized [0.397586] VFS: Disk quotas dquot_6.5.2 [0.397846] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [0.397962] JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [0.398624] msgmni has been set to 1006 [0.400343] alg: No test for stdrng (krng) [0.400463] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [0.400475] io scheduler noop registered [0.400482] io scheduler anticipatory registered [0.400490] io scheduler deadline registered [0.400676] io scheduler cfq registered (default) [0.406702] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [0.407174] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A [0.723343] console [ttyS0] enabled [0.727411] NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit) [0.736108] Scanning device for bad blocks [0.891983] Creating 3 MTD partitions on orion_nand: [0.897156] 0x-0x0010 : u-boot [0.902708] 0x0010-0x0050 : uImage [0.908185] 0x0050-0x2000 : root [0.914405] mice: PS/2 mouse device common for all mice [0.919923] rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0 [0.925872] i2c /dev entries driver [0.929572] cpuidle: using governor ladder [0.933800] cpuidle: using governor menu [0.937857] Registered led device: plug:green:health [0.942893] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver [0.949309] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver [0.995647] mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) [1.035645] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy ) [1.075645] mv_xor mv_xor.2: Marvell XOR: ( xor cpy ) [1.115645] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy ) [1.122313] TCP cubic registered [1.125554] NET: Registered protocol family 17 [1.130050] Gating clock of unused units [1.130058] before: 0x00dfc3fd [1.130065] after: 0x00c7c1d9 [1.130364] registered taskstats version 1 [1.135158] rtc-mv rtc-mv: setting system clock to 2012-01-22 14:51:58 UTC (1327243918) [1.143273] Initalizing network drop monitor service [1.148329] Freeing init memory: 124K [1.226056] udev[44]: starting version 164 [1.451840] mmc0: mvsdio driver initialized, using GPIO 47 for card detection [1.562507] mmc0: new high speed SDHC card at address e5bf [1.581543] mmcblk0: mmc0:e5bf SD08G 7.68 GiB [1.586216] mmcblk0: p1 p2 p3 p4 [1.942157] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode [2.567629] udev[150]: starting version 164 [3.010261] SCSI subsystem initialized [3.222025] libata version 3.00 loaded. [3.297493] usbcore: registered new interface driver usbfs [3.313053] usbcore: registered new interface driver hub [3.339601] usbcore: registered new device driver usb [3.367004] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [3.385160] MV-643xx 10/100/1000 ethernet driver version 1.4 [3.392179] mv643xx_eth smi: probed [3.396231] sata_mv sata_mv.0: version 1.28 [3.400553] sata_mv sata_mv.0: slots 32 ports 2 [3.406589] scsi0 : sata_mv [3.410032] scsi1 : sata_mv [3.413253] ata1: SATA max UDMA/133 irq 21 [3.417411] ata2: SATA max UDMA/133 irq 21 [3.421587] orion-ehci orion-ehci.0: Marvell Orion EHCI [3.427789] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 [3.455647] orion-ehci orion-ehci.0: irq 19, io mem 0xf105 [3.475611] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 [3.481616] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [3.488457] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [3.495724] usb usb1: Product: Marvell Orion EHCI [
Processed: found 656872 in javahelper/0.38, severity of 656872 is grave
Processing commands for cont...@bugs.debian.org: found 656872 javahelper/0.38 Bug #656872 [javahelper] javahelper: jh_build is unable to build jar files The source javahelper and version 0.38 do not appear to match any binary packages Bug Marked as found in versions javahelper/0.38. severity 656872 grave Bug #656872 [javahelper] javahelper: jh_build is unable to build jar files Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 656872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654395: additional patches for newer libav sources
Hi John, Le 19/01/2012 09:51, John Vogel a écrit : I had the same problem with blender 2.61-1 segfaulting on my wheezy/sid box. This bug has been fixed in git repository with the commit ed82a2a So I went about trying to build from git. Right away had problems with missing headers declarations for libavutil/mathematics.h. Then, had problems with avformat_alloc_open_context2() in intern/audaspace/ffmpeg/AUD_FFMPEGWriter.cpp. I found a fix in Gentoo's ebuild for blender-2.60a which negates most of the current debian/patches/0009-fix_FTBFS_ffmpeg_debian.patch. So I added the first patch below and replaced the 0009 patch with the second patch below (the one I found for the Gentoo ebuild). Builds fine and blender seems to running fine on my system, using up to date sid and strictly pure debian system other then my wacom driver (upstream kernel module and xorg driver). --- intern/ffmpeg/ffmpeg_compat.h |4 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/intern/ffmpeg/ffmpeg_compat.h b/intern/ffmpeg/ffmpeg_compat.h index dfdad22..bf6e4a9 100644 --- a/intern/ffmpeg/ffmpeg_compat.h +++ b/intern/ffmpeg/ffmpeg_compat.h @@ -74,6 +74,10 @@ #define FFMPEG_SWSCALE_COLOR_SPACE_SUPPORT #endif +#if (LIBAVUTIL_VERSION_MAJOR 51) || ((LIBAVUTIL_VERSION_MAJOR == 51) (LIBAVUTIL_VERSION_MINOR = 9)) +#include libavutil/mathematics.h +#endif + #ifndef FFMPEG_HAVE_AVIO #define AVIO_FLAG_WRITE URL_WRONLY #define avio_open url_fopen First, this patch does not have anything related to this bug report so next time, you are more than welcome to open another bug report. Next, I don't know how your patch managed to negates the patch 0009 but if it does, it's not the good way to solve this. Instead, an update to the ffmpeg_compat.h is only needed (cf patch attached to #656502). Thanks for your concern in blender package, Cheers -- Kevin 'Kiniou' Roy http://blog.knokorpo.fr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654395: marked as done ([blender] Segmentation fault on startup)
Your message dated Sun, 22 Jan 2012 17:54:39 +0100 with message-id 4f1c3f4f.7010...@gmail.com and subject line has caused the Debian Bug report #654395, regarding [blender] Segmentation fault on startup 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.) -- 654395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: blender Version: 2.61-1 Severity: normal --- Please enter the report below this line. --- I just updated Blender to the new version. When starting Blender, it crashes with a segmentation fault. Here is the backtrace: Program received signal SIGSEGV, Segmentation fault. 0x72159038 in _IO_vfprintf_internal (s=0x7fffdb30, format=0x11adc92 %s/blender/%s, ap=0x7fffdc98) at vfprintf.c:1620 1620vfprintf.c: No such file or directory. in vfprintf.c (gdb) bt #0 0x72159038 in _IO_vfprintf_internal (s=0x7fffdb30, format=0x11adc92 %s/blender/%s, ap=0x7fffdc98) at vfprintf.c:1620 #1 0x7217cf82 in _IO_vsnprintf (string=0x7fffdd80 /usr/lib/blender/\227\303\001, maxlen=optimized out, format=0x11adc92 %s/blender/%s, args=0x7fffdc98) at vsnprintf.c:120 #2 0x00c43e50 in BLI_snprintf () #3 0x00c3c5bb in get_path_system.isra.3 () #4 0x00c3c75f in BLI_get_folder () #5 0x01045382 in BLF_lang_init () #6 0x0073fa33 in WM_init () #7 0x0072fdb3 in main () --- System information. --- Architecture: amd64 Kernel: Linux 3.1.0-1-amd64 Debian Release: wheezy/sid 900 unstablewww.debian-multimedia.org 900 unstableftp.de.debian.org 580 experimental-snapshots qt-kde.debian.net 570 experimentalwww.debian-multimedia.org 570 experimentalftp.de.debian.org 560 testing www.debian-multimedia.org 560 testing security.debian.org 560 testing ftp.de.debian.org 550 stable www.debian-multimedia.org 550 stable security.debian.org 550 stable ftp.de.debian.org --- Package information. --- Depends(Version) | Installed -+- python3.2| 3.2.2-2 ttf-dejavu | 2.33-2 libavcodec53 (= 4:0.7.3-1) | 5:0.9-0.6 OR libavcodec-extra-53 (= 4:0.7.3-1) | libavdevice53(= 4:0.7.3-1) | 5:0.9-0.6 OR libavdevice-extra-53 (= 4:0.7.3-1) | libavformat53(= 4:0.7.3-1) | 5:0.9-0.6 OR libavformat-extra-53 (= 4:0.7.3-1) | libavutil51 (= 4:0.7.3-1) | 5:0.9-0.6 OR libavutil-extra-51(= 4:0.7.3-1) | libc6 (= 2.7) | 2.13-24 libfftw3-3 | 3.3-1 libfreetype6 (= 2.2.1) | 2.4.8-1 libgcc1 (= 1:4.1.1) | 1:4.6.2-9 libgl1-mesa-glx | 7.11.2-1 OR libgl1 | libglew1.6(= 1.6.0) | 1.6.0-4 libglu1-mesa | 7.11.2-1 OR libglu1 | libgomp1 (= 4.2.1) | 4.6.2-9 libilmbase6 (= 1.0.1) | 1.0.1-3 libjack-jackd2-0 (= 1.9.5~dfsg-14) | OR libjack-0.116| libjpeg8 (= 8c) | 8c-2 libopenal1 | 1:1.13-4 libopenexr6 (= 1.6.1) | 1.6.1-4.1 libopenjpeg2 | 1.3+dfsg-4 libpng12-0 (= 1.2.13-4) | 1.2.46-3 libpython3.2 (= 3.2~a4) | 3.2.2-2 libsdl1.2debian(= 1.2.10-1) | 1.2.14-6.4 libsndfile1 (= 1.0.20) | 1.0.25-3 libstdc++6 (= 4.6) | 4.6.2-9 libswscale2 (= 4:0.7.3-1) | 5:0.9-0.6 OR libswscale-extra-2(= 4:0.7.3-1) | libtiff4 | 3.9.5-2 libx11-6 | 2:1.4.4-4 libxi6 | 2:1.4.5-1 zlib1g (= 1:1.2.3.3.dfsg) | 1:1.2.3.4.dfsg-3 Package's Recommends field is empty. Suggests (Version) | Installed ===-+-=== yafaray | ---End Message--- ---BeginMessage--- Package:blender Version:2.61-2 -- Kevin 'Kiniou' Roy http://blog.knokorpo.fr ---End Message---
Bug#652235: Multiple new security issues
Apart from the security issues commented on this bug, there were discovered recently 10 more recent security issues that affect moodle on stable and testing/sid Adding them to this bug instead of creating a new one. Summary: CVE-2012-0792 Moodle MSA-12-0002: Personal information leak CVE-2012-0793 Moodle MSA-12-0004: Added profile image security CVE-2012-0794 Moodle MSA-12-0005: Encryption enhancement CVE-2012-0795 Moodle MSA-12-0006: Additional email address validation CVE-2012-0796 Moodle MSA-12-0007: Email injection prevention CVE-2012-0797 Moodle MSA-12-0008: Unsynchronised access via tokens CVE-2012-0798 Moodle MSA-12-0009: Role access issue CVE-2012-0799 Moodle MSA-12-0010: Unauthorised access to session key CVE-2012-0800 Moodle MSA-12-0011: Browser autofill password issue CVE-2012-0801 Moodle MSA-12-0012: Form validation issue Original Message Date: Fri, 20 Jan 2012 11:33:31 -0700 From: Vincent Danen vda...@redhat.com To: oss-secur...@lists.openwall.com Subject: [oss-security] CVE request: moodle 2.2.1, 2.1.4, 2.0.7, 1.9.16 vulnerabilities New moodle releases were made to fix a number of flaws (summarized below). Could CVEs be assigned to these? [1] http://docs.moodle.org/dev/Moodle_2.2.1_release_notes [2] http://docs.moodle.org/dev/Moodle_2.1.4_release_notes [3] http://docs.moodle.org/dev/Moodle_2.0.7_release_notes [4] http://docs.moodle.org/dev/Moodle_1.9.16_release_notes MSA-12-0001: Recaptcha transmission consistency issue Affects: 2.2, 2.1.x, 2.0.x, 1.9.x Fix: http://git.moodle.org/gw?p=moodle.git;a=commitdiff;h=b608b227bac4efba76da43dabe9bc2e32fb8fa32 Reference: http://moodle.org/mod/forum/discuss.php?d=194008 MSA-12-0002: Personal information leak Affects: 1.9.x Fix: http://git.moodle.org/gw?p=moodle.git;a=commitdiff;h=36b0ddeed45d0751508dcd9fa50f17fda43bae54 Reference: http://moodle.org/mod/forum/discuss.php?d=194009 MSA-12-0003: Added password protection Affects: 2.2, 2.1.x, 2.0.x, 1.9.x Fix: http://git.moodle.org/gw?p=moodle.git;a=commitdiff;h=aa30d3e8ce0dd41d3d0f7dae856beb180fed1f83 Reference: http://moodle.org/mod/forum/discuss.php?d=194011 MSA-12-0004: Added profile image security Affects: 2.2, 2.1.x, 2.0.x, 1.9.x Fix: http://git.moodle.org/gw?p=moodle.git;a=commit;h=90911c4ff98dc2078a3acef5ddf5a1a8f7e20ba5 Reference: http://moodle.org/mod/forum/discuss.php?d=194012 MSA-12-0005: Encryption enhancement Affects: 2.2, 2.1.x, 2.0.x, 1.9.x Fix: http://git.moodle.org/gw?p=moodle.git;a=commitdiff;h=98456628a24bba25d336860d38a45b5a4e3895da Reference: http://moodle.org/mod/forum/discuss.php?d=194013 MSA-12-0006: Additional email address validation Affects: 2.2, 2.1.x, 2.0.x, 1.9.x Fix: http://git.moodle.org/gw?p=moodle.gita=searchh=HEADst=commits=MDL-13572 Reference: http://moodle.org/mod/forum/discuss.php?d=194014 MSA-12-0007: Email injection prevention Affects: 2.2, 2.1.x, 2.0.x, 1.9.x Fix: http://git.moodle.org/gw?p=moodle.git;a=commit;h=62988bf0bbc73df655f51884aaf1f523928abff9 Reference: http://moodle.org/mod/forum/discuss.php?d=194015 MSA-12-0008: Unsynchronised access via tokens Affects: 2.2, 2.1.x, 2.0.x Fix: http://git.moodle.org/gw?p=moodle.gita=searchh=HEADst=commits=MDL-28126 Reference: http://moodle.org/mod/forum/discuss.php?d=194016 MSA-12-0009: Role access issue Affects: 2.2, 2.1.x Fix: http://git.moodle.org/gw?p=moodle.gita=searchh=HEADst=commits=MDL-29469 Reference: http://moodle.org/mod/forum/discuss.php?d=194017 MSA-12-0010: Unauthorised access to session key Affects: 2.1.x, 2.0.x Fix: http://git.moodle.org/gw?p=moodle.gita=searchh=HEADst=commits=MDL-27334 Reference: http://moodle.org/mod/forum/discuss.php?d=194018 MSA-12-0011: Browser autofill password issue Affects: 2.2, 2.1.x, 2.0.x Fix: http://git.moodle.org/gw?p=moodle.git;a=commitdiff;h=6e9989dbd3f261b2e1586ff77b0bf22fc7091485 Reference: http://moodle.org/mod/forum/discuss.php?d=194019 MSA-12-0012: Form validation issue Affects: 2.2, 2.1.x Fix: http://git.moodle.org/gw?p=moodle.git;a=commit;h=51070abc78b9e1db1db9a44855e8623b22bebd48 Reference: http://moodle.org/mod/forum/discuss.php?d=194020 -- Vincent Danen / Red Hat Security Response Team Original Message Date: Sat, 21 Jan 2012 17:15:29 -0700 From: Kurt Seifried kseifr...@redhat.com To: oss-secur...@lists.openwall.com Subject: Re: [oss-security] CVE request: moodle 2.2.1, 2.1.4, 2.0.7, 1.9.16 vulnerabilities On 01/20/2012 11:33 AM, Vincent Danen wrote: New moodle releases were made to fix a number of flaws (summarized below). Could CVEs be assigned to these? [1] http://docs.moodle.org/dev/Moodle_2.2.1_release_notes [2] http://docs.moodle.org/dev/Moodle_2.1.4_release_notes [3] http://docs.moodle.org/dev/Moodle_2.0.7_release_notes [4] http://docs.moodle.org/dev/Moodle_1.9.16_release_notes Summary: CVE-2012-0792 Moodle MSA-12-0002: Personal information leak CVE-2012-0793 Moodle MSA-12-0004: Added profile image security CVE-2012-0794 Moodle MSA-12-0005: Encryption
Bug#656877: [armel] Unable to modprobe sd_mod and thus to mount USB devices
severity 656877 important tags 656877 + moreinfo quit Hi, Goulven Guillard wrote: Version: 2.6.32-39squeeze1 [...] [ 37.737987] sd_mod: Unknown symbol scsi_verify_blk_ioctl [ 37.748886] sd_mod: Unknown symbol scsi_cmd_blk_ioctl [...] Linux version 2.6.32-5-kirkwood (Debian 2.6.32-38) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Mon Oct 3 16:55:04 UTC 2011 We don't currently guarantee that loading new modules after an upgrade will work until the next reboot. However, this looks like it is only 30 seconds or so after boot, so something else is probably at play. Did you flash the kernel correctly? Sorry for the trouble, Jonathan [...] Hardware: Marvell eSATA SheevaPlug Reference Board [...] ii uboot-mkimage 0.4generate kernel image for U-Boot -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [armel] Unable to modprobe sd_mod and thus to mount USB devices
Processing commands for cont...@bugs.debian.org: severity 656877 important Bug #656877 [linux-2.6] linux-image-2.6.32-5-kirkwood: Unable to modprobe sd_mod and thus to mount USB devices Severity set to 'important' from 'grave' tags 656877 + moreinfo Bug #656877 [linux-2.6] linux-image-2.6.32-5-kirkwood: Unable to modprobe sd_mod and thus to mount USB devices Added tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 656877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656247: marked as done (phpmyadmin: Local File Inclusion via XXE-injection (CVE-2011-4107))
Your message dated Sun, 22 Jan 2012 17:17:09 + with message-id e1rp12t-0006xf...@franck.debian.org and subject line Bug#656247: fixed in phpmyadmin 4:3.3.7-7 has caused the Debian Bug report #656247, regarding phpmyadmin: Local File Inclusion via XXE-injection (CVE-2011-4107) 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.) -- 656247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: phpmyadmin Version: 4:3.3.7-6 Severity: normal Vulnerability in phpmyadmin in squeeze has been exploited wildly in public. Spion from #debian-security asked this to be handled quickly. Tracker: http://security-tracker.debian.org/tracker/CVE-2011-4107 Exploit: http://www.exploit-db.com/exploits/18371/ OSVDB: http://osvdb.org/show/osvdb/76798 Please note that I have not validated this vulnerability and there is something strange going on as OSVDB has subject: libraries/import/xml.php XML Data Entity References Parsing Remote Information Disclosure and exploit-db is talking about LFI. Probably both are true. Contact me in case you need any help solving this issue. I can test and try to patch for example if needed. From MITRE's CVE-list: == Name: CVE-2011-4107 Status: Candidate URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4107 Phase: Assigned (20111018) Category: Reference: FULLDISC:2002 PhpMyAdmin Arbitrary File Reading Reference: URL:http://seclists.org/fulldisclosure/2011/Nov/21 Reference: MISC:http://packetstormsecurity.org/files/view/106511/phpmyadmin-fileread.txt Reference: MISC:http://www.wooyun.org/bugs/wooyun-2010-03185 Reference: MISC:https://bugzilla.redhat.com/show_bug.cgi?id=751112 Reference: CONFIRM:http://www.phpmyadmin.net/home_page/security/PMASA-2011-17.php Reference: FEDORA:FEDORA-2011-15831 Reference: URL:http://lists.fedoraproject.org/pipermail/package-announce/2011-November/069649.html Reference: FEDORA:FEDORA-2011-15841 Reference: URL:http://lists.fedoraproject.org/pipermail/package-announce/2011-November/069625.html Reference: FEDORA:FEDORA-2011-15846 Reference: URL:http://lists.fedoraproject.org/pipermail/package-announce/2011-November/069635.html Reference: BID:50497 Reference: URL:http://www.securityfocus.com/bid/50497 Reference: OSVDB:76798 Reference: URL:http://osvdb.org/76798 Reference: SECUNIA:46447 Reference: URL:http://secunia.com/advisories/46447 Reference: XF:phpmyadmin-xml-info-disclosure(71108) Reference: URL:http://xforce.iss.net/xforce/xfdb/71108 The simplexml_load_string function in the XML import plug-in (libraries/import/xml.php) in phpMyAdmin 3.4.x before 3.4.7.1 and 3.3.x before 3.3.10.5 allows remote authenticated users to read arbitrary files via XML data containing external entity references, aka an XML external entity (XXE) injection attack. Current Votes: None (candidate not yet proposed) == -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages phpmyadmin depends on: ii dbconfig-common1.8.46+squeeze.0 common framework for packaging dat ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii libapache2-mod-php55.3.3-7+squeeze3 server-side, HTML-embedded scripti ii libjs-mootools 1.2.4.0~debian1-1 compact JavaScript framework ii perl 5.10.1-17squeeze2 Larry Wall's Practical Extraction ii php5 5.3.3-7+squeeze3 server-side, HTML-embedded scripti ii php5-cgi 5.3.3-7+squeeze3 server-side, HTML-embedded scripti ii php5-mcrypt5.3.3-7+squeeze3 MCrypt module for php5 ii php5-mysql 5.3.3-7+squeeze3 MySQL module for php5 ii ucf3.0025+nmu1 Update Configuration File: preserv Versions of packages phpmyadmin recommends: ii apache22.2.16-6+squeeze4 Apache HTTP Server metapackage ii apache2-mpm-prefork [h 2.2.16-6+squeeze4 Apache HTTP Server - traditional n ii mysql-client 5.1.49-3 MySQL database client (metapackage ii mysql-client-5.1 [mysq 5.1.49-3 MySQL database client binaries ii php5-gd5.3.3-7+squeeze3 GD module for php5 Versions of packages phpmyadmin suggests: pn
Bug#500940: marked as done ([mlview] segfaults when saving in tree view)
Your message dated Sun, 22 Jan 2012 17:50:29 + with message-id e1rp1yj-0002ua...@franck.debian.org and subject line Bug#656714: Removed package(s) from unstable has caused the Debian Bug report #500940, regarding [mlview] segfaults when saving in tree view 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.) -- 500940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mlview Version: 0.9.0-2.1 Severity: grave Mlview segfaults when I save a file in the tree view. 1. create a new file with root 'test' 2. go to 'tools'-'new view'-'tree view' 3. save the file 4. segfault --- System information. --- Architecture: i386 Kernel: Linux 2.6.26-1-686 Debian Release: lenny/sid 900 testing security.debian.org 900 testing mirror.switch.ch 900 testing debian.netcologne.de 500 stable mirror.switch.ch 500 hardy wine.budgetdedicated.com --- Package information. --- Depends (Version) | Installed =-+- libart-2.0-2 (= 2.3.18) | 2.3.20-2 libatk1.0-0 (= 1.20.0) | 1.22.0-1 libbonobo2-0 (= 2.15.0) | 2.22.0-1 libbonoboui2-0 (= 2.15.1) | 2.22.0-1 libc6 (= 2.7-1) | 2.7-13 libcairo2 (= 1.4.0) | 1.6.4-6 libcairomm-1.0-1 (= 1.4.0) | 1.6.0-1 libfontconfig1 (= 2.4.0) | 2.6.0-1 libfreetype6 (= 2.3.5) | 2.3.7-2 libgcc1 (= 1:4.1.1-21) | 1:4.3.1-9 libgconf2-4 (= 2.13.5) | 2.22.0-1 libglade2-0 (= 1:2.6.1) | 1:2.6.2-1 libglademm-2.4-1c2a (= 2.6.0) | 2.6.6-1 libglib2.0-0 (= 2.16.0) | 2.16.5-1 libglibmm-2.4-1c2a (= 2.16.0) | 2.16.4-1 libgnome2-0 (= 2.17.3) | 2.20.1.1-1 libgnomecanvas2-0 (= 2.11.1) | 2.20.1.1-1 libgnomeprint2.2-0 (= 2.17.0) | 2.18.4-1 libgnomeui-0 (= 2.17.1) | 2.20.1.1-1 libgnomevfs2-0 (= 1:2.17.90) | 1:2.22.0-5 libgtk2.0-0 (= 2.12.0) | 2.12.11-3 libgtkmm-2.4-1c2a (= 1:2.12.0) | 1:2.12.7-1 libgtksourceview1.0-0 (= 1.7.2) | 1.8.5-1 libice6 (= 1:1.0.0) | 2:1.0.4-1 liborbit2 (= 1:2.14.10) | 1:2.14.13-0.1 libpango1.0-0 (= 1.20.1) | 1.20.5-2 libpng12-0 (= 1.2.13-4) | 1.2.27-1 libpopt0 (= 1.10) | 1.14-4 libsigc++-2.0-0c2a (= 2.0.2) | 2.0.18-2 libsm6 | 2:1.0.3-2 libstdc++6 (= 4.2.1-4) | 4.3.1-9 libvte9 (= 1:0.16.9) | 1:0.16.14-3 libx11-6 | 2:1.1.5-1 libxft2 ( 2.1.1) | 2.1.12-3 libxml2 (= 2.6.27) | 2.6.32.dfsg-4 libxrender1 | 1:0.9.4-2 libxslt1.1 (= 1.1.18) | 1.1.24-2 zlib1g (= 1:1.1.4) | 1:1.2.3.3.dfsg-12 gconf2 (= 2.10.1-2) | 2.22.0-1 GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu... (no debugging symbols found) (gdb) run Starting program: /usr/bin/mlview (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6623700 (LWP 6600)] mlview-debug: in void mlview::PluginPriv::load() : in file mlview-plugin.cc : line 72 : condition (module) failed; raising exception mlview-debug: in void mlview::PluginManager::load_all_plugins_from_default_plugins_dir() : in file mlview-plugin-manager.cc : line 106 : catched exception: Assertion failed mlview-debug: in MlViewStatus mlview::SourceView::set_default_language() : in file mlview-source-view.cc : line 539 : mime_type: text/xml mlview-debug: in MlViewStatus mlview::SourceView::set_language_from_mime_type(const mlview::UString) : in file mlview-source-view.cc : line 515 : language associated to 'text/xml'mime type: 0x8c95a10 [New Thread 0xb5c37b90 (LWP 6614)] [New Thread 0xb5436b90 (LWP 6615)]
Bug#565038: marked as done (mlview: ftbfs with gcc-4.5)
Your message dated Sun, 22 Jan 2012 17:50:29 + with message-id e1rp1yj-0002ua...@franck.debian.org and subject line Bug#656714: Removed package(s) from unstable has caused the Debian Bug report #565038, regarding mlview: ftbfs with gcc-4.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.) -- 565038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mlview Version: 0.9.0-2.2 Severity: normal Tags: sid User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.5 The package fails to build in a test rebuild on at least amd64 with gcc-4.5/g++-4.5, but succeeds to build with gcc-4.4/g++-4.4. For the compiler version used, see: http://lists.debian.org/debian-devel/2010/01/msg00230.html The full build log can be found at: http://people.debian.org/~lucas/logs/2010/01/08b/mlview_0.9.0-2.2_lsid64b.buildlog The last lines of the build log are cwat the end of this report. The reason of the build failure is likely in the package (compiler or linker message found in the build log), if this turns out as a gcc bug, please reassign to the gcc-4.5 package. If the build ends with a message confused by earlier errors, bailing out, please ignore it for now; these compiler errors are filed separately. [...] ranlib .libs/libeggrecent.a creating libeggrecent.la (cd .libs rm -f libeggrecent.la ln -s ../libeggrecent.la libeggrecent.la) make[4]: Leaving directory `/build/user-mlview_0.9.0-2.2-amd64-0xffIY/mlview-0.9.0/src/recent-files' make[4]: Entering directory `/build/user-mlview_0.9.0-2.2-amd64-0xffIY/mlview-0.9.0/src' /bin/bash ../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/libxml2 -I/usr/include/libxml2 -D_REENTRANT -I/usr/include/libglade-2.0 -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D_REENTRANT -I/usr/include/libglademm-2.4 -I/usr/lib/libglademm-2.4/include -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/libglade-2.0 -I/usr/include/giomm-2.4 -I/usr/lib/giomm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/lib/pangomm-1.4/include -I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/atkmm-1.6 -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sigc++- 2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/cairomm-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/libxml2 -D_REENTRANT -I/usr/include/gtksourceview-2.0 -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include-D_REENTRANT -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/giomm-2.4 -I/usr/lib/giomm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/lib/pangomm-1.4/include -I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/atkmm-1.6 -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/includ e -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/cairomm-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -D_REENTRANT -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -pthread -DORBIT2=1 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0
Bug#654263: marked as done (mlview: FTBFS on armhf, reproduced on amd64, error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Sun, 22 Jan 2012 17:50:29 + with message-id e1rp1yj-0002ua...@franck.debian.org and subject line Bug#656714: Removed package(s) from unstable has caused the Debian Bug report #654263, regarding mlview: FTBFS on armhf, reproduced on amd64, error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 654263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mlview Version: 0.9.0-2.2 Severity: serious https://buildd.debian.org/status/package.php?p=mlviewsuite=sid The build failure was seen on armhf, but I have reproduced it on a sid amd64 system, hence the security raise to serious. Konstantinos ---End Message--- ---BeginMessage--- Version: 0.9.0-2.2+rm Dear submitter, as the package mlview has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/656714 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain) ---End Message---
Bug#652253: marked as done (glame: FTBFS: libtool: link: `/usr/lib/libltdl.la' is not a valid libtool archive)
Your message dated Sun, 22 Jan 2012 17:57:21 + with message-id e1rp1fn-0003vn...@franck.debian.org and subject line Bug#656367: Removed package(s) from unstable has caused the Debian Bug report #652253, regarding glame: FTBFS: libtool: link: `/usr/lib/libltdl.la' is not a valid libtool archive 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.) -- 652253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: glame Version: 2.0.1-5 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20111210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ar cru .libs/normalize.a normalize.o ranlib .libs/normalize.a creating normalize.la /bin/sed: can't read /usr/lib/libltdl.la: No such file or directory libtool: link: `/usr/lib/libltdl.la' is not a valid libtool archive make[4]: *** [normalize.la] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/12/10/glame_2.0.1-5_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Version: 2.0.1-5+rm Dear submitter, as the package glame has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/656367 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain) ---End Message---
Processed: Try to fix 622384
Processing commands for cont...@bugs.debian.org:
unarchive 622384
Bug #622384 {Done: Luk Claes l...@debian.org} [src:dovecot] dovecot: FTBFS:
Build-Conflicts with linux-kernel-headers
Unarchived Bug 622384
fixed 622384 0.62.3-1
Bug #622384 {Done: Luk Claes l...@debian.org} [src:dovecot] dovecot: FTBFS:
Build-Conflicts with linux-kernel-headers
The source dovecot and version do not appear to match any binary packages
Bug Marked as fixed in versions dovecot/0.62.3-1.
close 622384 0.62.3-1
Bug#622384: dovecot: FTBFS: Build-Conflicts with linux-kernel-headers
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 0.62.3-1, send any further explanations to Kurt
Roeckx k...@roeckx.be
thanks
Stopping processing here.
Please contact me if you need assistance.
--
622384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656904: Gnash breaks flash-enabled websites (such as Google Finance)
Package: gnash Version: 0.8.10~git20111001-1 Severity: grave When using IceWeasel (or Chromium) and entering flash-enabled website, like Google Finance. To reproduce: Enter Google Finance: http://www.google.com/finance?q=EURUSD You see gray rectangle. Because this website has a fallback mechanism, removing gnash gives users static content of the web-site. Web-site detects whenever the browser is flash-enabled or not, and gives different content according to it. This package must be either: 1. fixed, or 2. gnash should be avoided on all new desktop installations, or 3. activate gnash only on supported websites, such as YouTube I'm not a developed, but willing to assist in testing. I am using Debian GNU/Linux wheezy/testing on AMD64 (also tried gnash 0.8.8-5 Debian GNU/Linux 6.0.3 on AMD64 and i386) Same problem applies to other Flash-enabled websites, such as: www.amd.com -- -Alexey Eromenko Technologov 22.Jan.2012. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656914: kdelibs5-dev: causes kaffeine to FTBFS with current xine-lib
Package: kdelibs5-dev Version: 4:4.6.5-2 Severity: serious Doing test-builds of various packages which depend on libxine-dev, I find that kaffeine isn't built due to failure to find xine-lib. There are two problems here, one of which causes FTBFS. 1. cmake doesn't seem to be ignoring what's output by xine-config on stderr, so it doesn't correctly pick up on the version number. (I've tested this by playing with xine-config, preventing it from outputting its deprecation warning on stderr.) 2. The FindXine.cmake script should really be using pkg-config to locate xine-lib... -- | _ | Darren Salt, using Debian GNU/Linux (and Android) | ( ) | | X | ASCII Ribbon campaign against HTML e-mail | / \ | http://www.asciiribbon.org/ Govt investigations contribute more to amusement than knowledge. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 654220 to FTBFS with libav 0.8
Processing commands for cont...@bugs.debian.org: retitle 654220 FTBFS with libav 0.8 Bug #654220 [opencv] FTBFS with libav in experimental Changed Bug title to 'FTBFS with libav 0.8' from 'FTBFS with libav in experimental' thanks Stopping processing here. Please contact me if you need assistance. -- 654220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 654183 to FTBFS with libav 0.8
Processing commands for cont...@bugs.debian.org: retitle 654183 FTBFS with libav 0.8 Bug #654183 [ffms2] FTBFS with libav in experimental Changed Bug title to 'FTBFS with libav 0.8' from 'FTBFS with libav in experimental' thanks Stopping processing here. Please contact me if you need assistance. -- 654183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 654212 to FTBFS with libav 0.8
Processing commands for cont...@bugs.debian.org:
retitle 654212 FTBFS with libav 0.8
Bug #654212 {Done: Benjamin Drung bdr...@debian.org} [audacity] FTBFS with
libav in experimental
Changed Bug title to 'FTBFS with libav 0.8' from 'FTBFS with libav in
experimental'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
654212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 654213 to FTBFS with libav 0.8
Processing commands for cont...@bugs.debian.org:
retitle 654213 FTBFS with libav 0.8
Bug #654213 {Done: Aron Xu a...@debian.org} [ktoon] FTBFS with libav in
experimental
Changed Bug title to 'FTBFS with libav 0.8' from 'FTBFS with libav in
experimental'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
654213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 654221 to FTBFS with libav 0.8
Processing commands for cont...@bugs.debian.org:
retitle 654221 FTBFS with libav 0.8
Bug #654221 {Done: Ansgar Burchardt ans...@debian.org} [performous] FTBFS
with libav in experimental
Changed Bug title to 'FTBFS with libav 0.8' from 'FTBFS with libav in
experimental'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
654221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 654215 to FTBFS with libav 0.8
Processing commands for cont...@bugs.debian.org: retitle 654215 FTBFS with libav 0.8 Bug #654215 [chromium-browser] FTBFS with libav in experimental Changed Bug title to 'FTBFS with libav 0.8' from 'FTBFS with libav in experimental' thanks Stopping processing here. Please contact me if you need assistance. -- 654215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 654222 to FTBFS with libav 0.8
Processing commands for cont...@bugs.debian.org:
retitle 654222 FTBFS with libav 0.8
Bug #654222 {Done: jac...@debian.org (Eugene V. Lyubimkin)} [qmmp] FTBFS with
libav in experimental
Changed Bug title to 'FTBFS with libav 0.8' from 'FTBFS with libav in
experimental'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
654222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 654229 to FTBFS with libav 0.8
Processing commands for cont...@bugs.debian.org: retitle 654229 FTBFS with libav 0.8 Bug #654229 [wxsvg] FTBFS with libav in experimental Changed Bug title to 'FTBFS with libav 0.8' from 'FTBFS with libav in experimental' thanks Stopping processing here. Please contact me if you need assistance. -- 654229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 653823 with 653625
Processing commands for cont...@bugs.debian.org: block 653823 with 653625 Bug #653823 [release.debian.org] transition: boost-defaults Was not blocked by any bugs. Added blocking bug(s) of 653823: 653625 thanks Stopping processing here. Please contact me if you need assistance. -- 653823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 653823 with 652775
Processing commands for cont...@bugs.debian.org: block 653823 with 652775 Bug #653823 [release.debian.org] transition: boost-defaults Was blocked by: 653625 Added blocking bug(s) of 653823: 652775 thanks Stopping processing here. Please contact me if you need assistance. -- 653823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 653823 with 652797
Processing commands for cont...@bugs.debian.org: block 653823 with 652797 Bug #653823 [release.debian.org] transition: boost-defaults Was blocked by: 653625 652775 Added blocking bug(s) of 653823: 652797 thanks Stopping processing here. Please contact me if you need assistance. -- 653823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 653823 with 653625 652775 652797 652790 652795 652786 652798 653796 652788 653805 653806 653807 652784
Processing commands for cont...@bugs.debian.org: block 653823 with 653625 652775 652797 652790 652795 652786 652798 653796 652788 653805 653806 653807 652784 Bug #653823 [release.debian.org] transition: boost-defaults Was blocked by: 653625 652775 652797 Added blocking bug(s) of 653823: 652784, 653805, 652795, 652788, 653806, 653796, 653807, 652798, 652786, and 652790 thanks Stopping processing here. Please contact me if you need assistance. -- 653823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#655788: [Debian-med-packaging] Bug#655788: Bug#655788: igstk: FTBFS: libITKIO.so: undefined reference to `gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const)'
On Sun, Jan 22, 2012 at 1:40 AM, Steve M. Robbins st...@sumost.ca wrote:
On Sat, Jan 21, 2012 at 11:12:45PM -0500, Dominique Belhachemi wrote:
Hi Steve,
It occurred in a clean pbuilder environment on amd64 and the build
used the latest itk package:
Setting up libvxl1.14 (1.14.0-14) ...
Setting up libinsighttoolkit3.20 (3.20.1-2) ...
OK, I'm preparing ITK 3.20.1-3 which adds dependency from
libinsighttoolkit3-dev to libvxl1-dev. This fixes the
immediate problem ...
CMake Warning at /usr/lib/InsightToolkit/UseITK.cmake:53 (FIND_PACKAGE):
Could not find module FindVXL.cmake or a configuration file for package
VXL.
... because FindVXL.cmake is part of libvxl1-dev.
Unfortunately, it exposes a different problem. The build now requires
file /usr/share/vxl/cmake/doxy_header.html which I cannot find.
The missing file is located in the vxl source package
./vxl-1.14.0/config/cmake/doxygen/doxy_header.html
but it is not part of the vxl binary packages.
igstk compiles fine after applying the following patch to vxl.
--- vxl-1.14.0.orig/config/cmake/Modules/UseVXL.cmake
+++ vxl-1.14.0/config/cmake/Modules/UseVXL.cmake
@@ -132,7 +132,7 @@ IF(VXL_CONFIG_CMAKE)
ENDIF(VXL_PROVIDE_OLD_CACHE_NAMES)
# Allow use of VXL's cmake/doxygen framework
- INCLUDE(${VXL_CMAKE_DOXYGEN_DIR}/doxygen.cmake)
+# INCLUDE(${VXL_CMAKE_DOXYGEN_DIR}/doxygen.cmake)
IF(VXL_PROVIDE_STANDARD_OPTIONS)
# Provide the standard set of VXL CMake options to the project.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656171: [Debian-Islamic-maintainers] Bug#656171: zekr: unowned files after purge (policy 6.8) violating FHS (policy 9.1) too
السلام عليكم، The zekr package runs: zekr -index all during installation, also the package runs: zekr -clean all, both of these commands result in creating of /root/.zekr folder. I tried running: zekr -index all -workspace /tmp/xyz , but that didn't change anything. Yet if I try running: zekr -workspace /tmp/xyz -index all, this results in launching the Zekr GUI, and not running the indexing command. On Tue, Jan 17, 2012 at 03:19:15AM +0100, Andreas Beckmann wrote: As putting files into /root/ is also a violation of http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 I'm setting the severity to serious. ---end quoted text--- Please note that this issue, if not fixed, can lead to removing zekr from next Debian release. -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: Digital signature
Bug#656171: marked as forwarded (zekr: unowned files after purge (policy 6.8) violating FHS (policy 9.1) too)
Your message dated Sun, 22 Jan 2012 22:25:32 +0200 with message-id 20120122202532.ga2...@ants.dhis.net has caused the report #656171, regarding zekr: unowned files after purge (policy 6.8) violating FHS (policy 9.1) too to be marked as having been forwarded to the upstream software author(s) Mohsen Saboorian mohs...@gmail.com (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.) -- 656171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- السلام عليكم، The zekr package runs: zekr -index all during installation, also the package runs: zekr -clean all, both of these commands result in creating of /root/.zekr folder. I tried running: zekr -index all -workspace /tmp/xyz , but that didn't change anything. Yet if I try running: zekr -workspace /tmp/xyz -index all, this results in launching the Zekr GUI, and not running the indexing command. On Tue, Jan 17, 2012 at 03:19:15AM +0100, Andreas Beckmann wrote: As putting files into /root/ is also a violation of http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 I'm setting the severity to serious. ---end quoted text--- Please note that this issue, if not fixed, can lead to removing zekr from next Debian release. -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: Digital signature ---End Message---
Bug#655838: marked as done (libaxis2c0 and libaxis2c-dev: error when trying to install together)
Your message dated Sun, 22 Jan 2012 22:04:38 +0100 with message-id 4f1c79e6.3010...@gmail.com and subject line axis2c -dev conflicts solved with 1.6.0-4 has caused the Debian Bug report #655838, regarding libaxis2c0 and libaxis2c-dev: error when trying to install together 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.) -- 655838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libaxis2c-dev,libaxis2c0 Version: libaxis2c-dev/1.6.0-2.2 Version: libaxis2c0/1.6.0-2.2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-01-14 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libxml2 libapr1 libc-dev-bin linux-libc-dev libc6-dev uuid-dev libapr1-dev libaxis2c0 libxml2-dev libaxis2c-dev Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libxml2. (Reading database ... 10520 files and directories currently installed.) Unpacking libxml2 (from .../libxml2_2.7.8.dfsg-5.1_amd64.deb) ... Selecting previously unselected package libapr1. Unpacking libapr1 (from .../libapr1_1.4.5-1.1_amd64.deb) ... Selecting previously unselected package libc-dev-bin. Unpacking libc-dev-bin (from .../libc-dev-bin_2.13-24_amd64.deb) ... Selecting previously unselected package linux-libc-dev. Unpacking linux-libc-dev (from .../linux-libc-dev_3.1.8-2_amd64.deb) ... Selecting previously unselected package libc6-dev. Unpacking libc6-dev (from .../libc6-dev_2.13-24_amd64.deb) ... Selecting previously unselected package uuid-dev. Unpacking uuid-dev (from .../uuid-dev_2.20.1-1.1_amd64.deb) ... Selecting previously unselected package libapr1-dev. Unpacking libapr1-dev (from .../libapr1-dev_1.4.5-1.1_amd64.deb) ... Selecting previously unselected package libaxis2c0. Unpacking libaxis2c0 (from .../libaxis2c0_1.6.0-2.2_amd64.deb) ... Selecting previously unselected package libxml2-dev. Unpacking libxml2-dev (from .../libxml2-dev_2.7.8.dfsg-5.1_amd64.deb) ... Selecting previously unselected package libaxis2c-dev. Unpacking libaxis2c-dev (from .../libaxis2c-dev_1.6.0-2.2_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libaxis2c-dev_1.6.0-2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/axis2/lib/libaxis2_xpath.so', which is also in package libaxis2c0 1.6.0-2.2 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libaxis2c-dev_1.6.0-2.2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/axis2/lib/libaxis2_axiom.so /usr/lib/axis2/lib/libaxis2_engine.so /usr/lib/axis2/lib/libaxis2_http_common.so /usr/lib/axis2/lib/libaxis2_http_receiver.so /usr/lib/axis2/lib/libaxis2_http_sender.so /usr/lib/axis2/lib/libaxis2_parser.so /usr/lib/axis2/lib/libaxis2_xpath.so -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- It was just accepted in unstable. Thanks Steffen ---End Message---
Bug#656690: marked as done (Rebuild for Mono transition)
Your message dated Sun, 22 Jan 2012 21:03:48 + with message-id e1rp4zo-00074y...@franck.debian.org and subject line Bug#656690: fixed in coco-cs 20110419-5 has caused the Debian Bug report #656690, regarding Rebuild for Mono transition to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 656690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:coco-cs Version: 20110419-4 Severity: serious Hi, A Mono transition is underway. Every source package needs to be rebuilt to compile against CLR 4.0 instead of CLR 2.0. Please upload coco-cs for this change. You can check it worked if, after rebuilding, coco-cs has a dependency on libmono-corlib4.0-cil instead of …corlib2.0-cil. http://wiki.debian.org/Teams/DebianMonoGroup/Mono210Transition http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648775 Cheers, -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] PhD student [ i...@cs.nott.ac.uk ] signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: coco-cs Source-Version: 20110419-5 We believe that the bug you reported is fixed in the latest version of coco-cs, which is due to be installed in the Debian FTP archive: coco-cs_20110419-5.diff.gz to main/c/coco-cs/coco-cs_20110419-5.diff.gz coco-cs_20110419-5.dsc to main/c/coco-cs/coco-cs_20110419-5.dsc coco-cs_20110419-5_all.deb to main/c/coco-cs/coco-cs_20110419-5_all.deb 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 656...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Loeberbauer loeberba...@ssw.jku.at (supplier of updated coco-cs 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 21 Jan 2012 17:58:30 +0100 Source: coco-cs Binary: coco-cs Architecture: source all Version: 20110419-5 Distribution: unstable Urgency: low Maintainer: Markus Loeberbauer loeberba...@ssw.jku.at Changed-By: Markus Loeberbauer loeberba...@ssw.jku.at Description: coco-cs- Coco/R Compiler Generator (C-Sharp Version) Closes: 656690 Changes: coco-cs (20110419-5) unstable; urgency=low . * Switched to CLR 4.0 (Closes: #656690) Checksums-Sha1: 64edd18028744dca3f9fbffa29c6b685c8984b68 1135 coco-cs_20110419-5.dsc 809886c18bfd05a9f4ae67863578dd3fc494185c 6551 coco-cs_20110419-5.diff.gz f3f18573457c5ca16e2dd968df4d24537860a30e 42702 coco-cs_20110419-5_all.deb Checksums-Sha256: 2ba5a18d6e5f4a53541179326bfa2fcd7fc68cb0d553a9bdc9ad3465dbc4df8e 1135 coco-cs_20110419-5.dsc 1941c57bf776b17def9974127d8f9730103513816b4549456a50236abd1665c4 6551 coco-cs_20110419-5.diff.gz 2d11554941b2b73328f06ba3dcf48cec0bba07d7d5d43e1b70d36e811f8ba301 42702 coco-cs_20110419-5_all.deb Files: 3db45decf40bc7076d450282d0eeb7ae 1135 devel optional coco-cs_20110419-5.dsc cb11601a314f0ead50ef2211316f90fc 6551 devel optional coco-cs_20110419-5.diff.gz 2d05eb2e8dd00437da8615b26f2c9571 42702 devel optional coco-cs_20110419-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk8cavEACgkQq7SPDcPCS94XfACgz9prIhflwRwZh3vjFQd2VzOf gMMAoKNqrWu4zS8CY2xUcnUclsu5aigc =aZKy -END PGP SIGNATURE- ---End Message---
Bug#653893: marked as done (ideviceinstaller: ftbfs against libzip-0.10)
Your message dated Sun, 22 Jan 2012 21:06:13 +
with message-id e1rp4c9-0007o6...@franck.debian.org
and subject line Bug#653893: fixed in ideviceinstaller 1.0.0-1.1
has caused the Debian Bug report #653893,
regarding ideviceinstaller: ftbfs against libzip-0.10
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.)
--
653893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: ideviceinstaller
Version: 1.0.0-1
Severity: serious
Tags: patch
Justification: ftbfs
Hi,
a rebuild against libzip-0.10 failed to build:
gcc -DHAVE_CONFIG_H -I. -I..-Wall -Wextra -Wmissing-declarations
-Wredundant-decls -Wshadow -Wpointer-arith -Wwrite-strings
-Wswitch-default -Wno-unused-parameter -Werror -g -pthread
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/p11-kit-1 -I/usr/include/libxml2 -I/usr/include/libxml2
-I/usr/lib/libzip/include -g -O2 -c -o
ideviceinstaller-ideviceinstaller.o `test -f 'ideviceinstaller.c' ||
echo './'`ideviceinstaller.c
ideviceinstaller.c: In function 'zip_f_get_contents':
ideviceinstaller.c:164:41: error: comparison between signed and unsigned
integer expressions [-Werror=sign-compare]
cc1: all warnings being treated as errors
make[3]: *** [ideviceinstaller-ideviceinstaller.o] Error 1
make[3]: Leaving directory `/tmp/buildd/ideviceinstaller-1.0.0/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/buildd/ideviceinstaller-1.0.0'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/buildd/ideviceinstaller-1.0.0'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Description: fix build failure with libzip 0.10
zip_fread returns signed int64 while zip_stat size is an unsigned int64.
---
src/ideviceinstaller.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/src/ideviceinstaller.c
+++ b/src/ideviceinstaller.c
@@ -161,7 +161,7 @@ static int zip_f_get_contents(struct zip
}
*buffer = malloc(zs.size);
- if (zip_fread(zfile, *buffer, zs.size) != zs.size) {
+ if (zs.sizeLLONG_MAX || zip_fread(zfile, *buffer, zs.size) != (zip_int64_t)zs.size) {
fprintf(stderr, ERROR: zip_fread %ld bytes from '%s'\n, zs.size, filename);
free(*buffer);
*buffer = NULL;
Description: fix build failure with libzip 0.10
zip_fread returns signed int64 while zip_stat size is an unsigned int64.
---
src/ideviceinstaller.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/src/ideviceinstaller.c
+++ b/src/ideviceinstaller.c
@@ -161,7 +161,7 @@ static int zip_f_get_contents(struct zip
}
*buffer = malloc(zs.size);
- if (zip_fread(zfile, *buffer, zs.size) != zs.size) {
+ if (zs.sizeLLONG_MAX || zip_fread(zfile, *buffer, zs.size) != (zip_int64_t)zs.size) {
fprintf(stderr, ERROR: zip_fread %ld bytes from '%s'\n, zs.size, filename);
free(*buffer);
*buffer = NULL;
Description: fix build failure with libzip 0.10
zip_fread returns signed int64 while zip_stat size is an unsigned int64.
---
src/ideviceinstaller.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/src/ideviceinstaller.c
+++ b/src/ideviceinstaller.c
@@ -161,7 +161,7 @@ static int zip_f_get_contents(struct zip
}
*buffer = malloc(zs.size);
- if (zip_fread(zfile, *buffer, zs.size) != zs.size) {
+ if (zs.sizeLLONG_MAX || zip_fread(zfile, *buffer, zs.size) != (zip_int64_t)zs.size) {
fprintf(stderr, ERROR: zip_fread %ld bytes from '%s'\n, zs.size, filename);
free(*buffer);
*buffer = NULL;
---End Message---
---BeginMessage---
Source: ideviceinstaller
Source-Version: 1.0.0-1.1
We believe that the bug you reported is fixed in the latest version of
ideviceinstaller, which is due to be installed in the Debian FTP archive:
ideviceinstaller-dbg_1.0.0-1.1_amd64.deb
to main/i/ideviceinstaller/ideviceinstaller-dbg_1.0.0-1.1_amd64.deb
ideviceinstaller_1.0.0-1.1.debian.tar.gz
to main/i/ideviceinstaller/ideviceinstaller_1.0.0-1.1.debian.tar.gz
ideviceinstaller_1.0.0-1.1.dsc
to main/i/ideviceinstaller/ideviceinstaller_1.0.0-1.1.dsc
ideviceinstaller_1.0.0-1.1_amd64.deb
to main/i/ideviceinstaller/ideviceinstaller_1.0.0-1.1_amd64.deb
A summary
Processed: Rise severity of usb-modeswitch 1.2.2 bugs
Processing commands for cont...@bugs.debian.org: severity 656688 serious Bug #656688 [usb-modeswitch] usb-modeswitch: no ttyHS* devices Severity set to 'serious' from 'normal' severity 656063 serious Bug #656063 [usb-modeswitch] usb_modeswitch_dispatcher: free(): invalid next size Severity set to 'serious' from 'normal' severity 656854 serious Bug #656854 [usb-modeswitch] usb-modeswitch throws general protection error and umts modem is unusable Severity set to 'serious' from 'important' merge 656688 656854 Bug#656688: usb-modeswitch: no ttyHS* devices Bug#656854: usb-modeswitch throws general protection error and umts modem is unusable Merged 656688 656854. thanks Stopping processing here. Please contact me if you need assistance. -- 656854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656854 656063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656063 656688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573793: marked as done (xine-lib-1.2: FTBFS on kfreebsd-*: missing vdpau plugin)
Your message dated Sun, 22 Jan 2012 21:11:44 + with message-id 525b27e8b0%li...@youmustbejoking.demon.co.uk and subject line xine-lib-1.2: VDPAU on kfreebsd-* has caused the Debian Bug report #573793, regarding xine-lib-1.2: FTBFS on kfreebsd-*: missing vdpau plugin 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.) -- 573793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xine-lib-1.2 Version: 1.1.90hg+20100309+8d16822f2be7-2 Severity: serious Tags: patch Justification: FTBFS User: debian-...@lists.debian.org Usertags: kfreebsd Hi, your package no longer builds on kfreebsd-*: it fails at the dh_install step since the vdpau plugin is missing. Please find attached an updated debian-changes patch which enables it on kfreebsd (rather than freebsd). Build logs: https://buildd.debian.org/status/package.php?p=xine-lib-1.2suite=experimental Thanks for considering. Mraw, KiBi. Origin: upstream, other, * Description: Applied patches. See Vcs-* headers in debian/control. --- a/configure +++ b/configure @@ -19268,7 +19268,7 @@ $as_echo #define ARCH_ARM /**/ confd sparc*-*-linux*) case `uname -m` in -sparc) cpuflags=-mcpu=supersparc -mtune=supersparc ;; +sparc) cpuflags=-mcpu=ultrasparc -mtune=ultrasparc ;; sparc64)cpuflags=-mcpu=ultrasparc -mtune=ultrasparc ;; esac test x$enable_vis != xno has_vis=yes @@ -22411,6 +22411,11 @@ fi default_enable_vidix=yes ;; +kfreebsd*) +default_enable_vidix=yes +default_enable_vdpau=yes +;; + linux*) default_enable_dxr3=yes default_enable_fb=yes --- a/m4/video_out.m4 +++ b/m4/video_out.m4 @@ -46,6 +46,11 @@ AC_DEFUN([XINE_VIDEO_OUT_PLUGINS], [ default_enable_vidix=yes ;; +kfreebsd*) +default_enable_vidix=yes +default_enable_vdpau=yes +;; + linux*) default_enable_dxr3=yes default_enable_fb=yes ---End Message--- ---BeginMessage--- Version: 1.1.90hg+20100309+8d16822f2be7-3 Just noticed that this one should have been closed a while ago... -- | _ | Darren Salt, using Debian GNU/Linux (and Android) | ( ) | | X | ASCII Ribbon campaign against HTML e-mail | / \ | http://www.asciiribbon.org/ I am. Therefore, I think. I think. ---End Message---
Bug#642267: downgrading to important
severity 642267 important retitle 642267 ruby-ffi: returning struct by value does not work on ia64 thanks Since this represents a single failing test, I am downgrading the severiry of this bug to important, and will ignore the test results on ia64. I will still appreciate a lot if any ia64 user can help with investigating this. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#654511: Doesn't contain source for waf binary code
3.1.5 release is imminent. Will be fixed part of that upload. Regards, Dmitrijs. signature.asc Description: OpenPGP digital signature
Bug#629952: subversion fails to build for stable(-security) on kfreebsd
On Thu, Jan 05, 2012 at 07:13:35PM +0100, Moritz Muehlenhoff wrote: On Thu, Jun 16, 2011 at 07:33:34PM +0200, Aurelien Jarno wrote: On Wed, Jun 15, 2011 at 12:45:22PM +0200, Thijs Kinkhorst wrote: On Thu, June 9, 2011 23:03, Peter Samuelson wrote: [Thijs Kinkhorst] The last two security updates for subversion, 1.6.12dfsg-6 and 1.6.12dfsg-7, have failed to build on kfreebsd-i386 and kfreebsd-amd64. Attached are two sample build logs. Can you investigate this? It is a problem we've seen on _some_ but not all kfreebsd buildd hosts for quite some time, and last we tried, Cyril could not reproduce it on his own system. One of the test suites starts up a server process on localhost, connects to it, does some tests, and eventually kills the server. Starting the server, or connecting to it, is what appears to be failing. It works on all our Linux platforms, and it _used_ to work on some of the kfreebsd buildds as well, though lately it seems to not work on any of them. Is it valid to create a TCP based server on 127.0.0.1, connect to it, then later kill it, in a build chroot? If not, I guess I can disable all those tests. I've just always assumed that was a valid thing to do in a package build. Thanks. I'm not a buildd expert, so I'm CC'ing some of those that are. If it builds at least on some buildds (which ones?), it would help me in the sort term if we could get those buildds to build 1.6.12dfsg-6. I think it builds fine on non-smp buildds, which at the time of the Squeeze release were fano and finzi. They have been switched to SMP a few weeks ago. Maybe we should switch them back to non-SMP? Alternatively I can build them manually to solve this situation, though it will only hide the problem. Can you upload manual builds? The archs need to be in sync for acceptance in the upcoming 6.0.4 point release of Squeeze. I have built both kfreebsd-amd64 and kfreebsd-i386 versions on non-SMP machines. I have just uploaded the resulting packages. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629952: subversion fails to build for stable(-security) on kfreebsd
Aurelien Jarno aurel...@aurel32.net (22/01/2012): I have built both kfreebsd-amd64 and kfreebsd-i386 versions on non-SMP machines. I have just uploaded the resulting packages. \o/ Mraw, KiBi. signature.asc Description: Digital signature
Bug#656918: debian/rules does not clean the source properly
Source: mediainfo Version: 0.7.52 Severity: serious The package does cannot be built twice. /var/tmp/libmediainfo-0.7.52 $ debuild dpkg-buildpackage -rfakeroot -D -us -uc dpkg-buildpackage: source package libmediainfo dpkg-buildpackage: source version 0.7.52-1 dpkg-buildpackage: source changed by Chow Loong Jin hyper...@debian.org dpkg-source --before-build libmediainfo-0.7.52 dpkg-buildpackage: host architecture amd64 fakeroot debian/rules clean dh clean --with=autoreconf dh_testdir debian/rules override_dh_auto_clean make[1]: Entering directory `/var/tmp/libmediainfo-0.7.52' dh_auto_clean -DProject/GNU/Library make[1]: Leaving directory `/var/tmp/libmediainfo-0.7.52' dh_autoreconf_clean dh_clean dpkg-source -b libmediainfo-0.7.52 dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building libmediainfo using existing ./libmediainfo_0.7.52.orig.tar.gz dpkg-source: warning: executable mode 0755 of 'Documentation.html' will not be represented in diff dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/tab_b.png: binary file contents changed dpkg-source: error: add Doc/tab_b.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/tab_h.png: binary file contents changed dpkg-source: error: add Doc/tab_h.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/nav_h.png: binary file contents changed dpkg-source: error: add Doc/nav_h.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/tab_a.png: binary file contents changed dpkg-source: error: add Doc/tab_a.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/open.png: binary file contents changed dpkg-source: error: add Doc/open.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/bc_s.png: binary file contents changed dpkg-source: error: add Doc/bc_s.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/nav_f.png: binary file contents changed dpkg-source: error: add Doc/nav_f.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/tab_s.png: binary file contents changed dpkg-source: error: add Doc/tab_s.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/closed.png: binary file contents changed dpkg-source: error: add Doc/closed.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: warning: executable mode 0755 of 'Doc/installdox' will not be represented in diff dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/doxygen.png: binary file contents changed dpkg-source: error: add Doc/doxygen.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/search/search_l.png: binary file contents changed dpkg-source: error: add Doc/search/search_l.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/search/search_r.png: binary file contents changed dpkg-source: error: add Doc/search/search_r.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/search/mag_sel.png: binary file contents changed dpkg-source: error: add Doc/search/mag_sel.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/search/close.png: binary file contents changed dpkg-source: error: add Doc/search/close.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to libmediainfo-0.7.52/Doc/search/search_m.png: binary file contents changed dpkg-source: error: add Doc/search/search_m.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: unrepresentable changes to source dpkg-buildpackage: error:
Bug#613589: /sbin/cfdisk: Bad Table error after fresh Squeeze install
Hi,
Timo Juhani Lindfors wrote:
thanks for the report. I can reproduce the problem with the attached
partition table image.
Thanks. When I try to reproduce this with cfdisk parttable1.img
(also with -g or overriding the C/H/S values), I get FATAL ERROR:
Cannot get disk size. I guess I should be testing using a vm, but
I'm lazy. :)
Anyway, how about this patch for squeeze? Possible changelog entry:
* From upstream: cfdisk: don't use size of device based on cylinders.
Closes: #613589
Patch is against commit 5e5f7dac (changelog: release, 2011-01-25) from
git://git.debian.org/~lamont/util-linux.git. Seems to build fine,
though that doesn't mean much.
-- 8 --
From: Karel Zak k...@redhat.com
Date: Mon, 6 Sep 2010 13:30:48 +0200
Subject: cfdisk: don't use size of device based on cylinders
commit 73356e0553bd9ac00f556891a4798064c0ee6849 upstream.
This patch is enough to make cfdisk usable on non-DOS disks where
partitioning is not based on CHS. cfdisk should not print error
messages for such disks.
Addresses: https://bugzilla.redhat.com/show_bug.cgi?id=630340
Signed-off-by: Karel Zak k...@redhat.com
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
fdisk/cfdisk.c | 17 +
1 files changed, 5 insertions(+), 12 deletions(-)
diff --git a/fdisk/cfdisk.c b/fdisk/cfdisk.c
index 4fb41529..5b9aaebe 100644
--- a/fdisk/cfdisk.c
+++ b/fdisk/cfdisk.c
@@ -177,7 +177,6 @@ int heads = 0;
int sectors = 0;
long long cylinders = 0;
int cylinder_size = 0; /* heads * sectors */
-long long total_size = 0; /* actual_size rounded down */
long long actual_size = 0; /* (in 512-byte sectors) - set using ioctl */
/* explicitly given user values */
int user_heads = 0, user_sectors = 0;
@@ -879,7 +878,7 @@ del_part(int i) {
if (i num_parts - 1)
p_info[i].last_sector = p_info[i+1].first_sector - 1;
else
- p_info[i].last_sector = total_size - 1;
+ p_info[i].last_sector = actual_size - 1;
p_info[i].offset = 0;
p_info[i].flags = 0;
@@ -928,7 +927,7 @@ add_part(int num, int id, int flags, long long first, long
long last,
return -1;
}
-if (first = total_size) {
+if (first = actual_size) {
*errmsg = _(Partition begins after end-of-disk);
return -1;
}
@@ -938,11 +937,6 @@ add_part(int num, int id, int flags, long long first, long
long last,
return -1;
}
-if (last = total_size) {
- *errmsg = _(Partition ends in the final partial cylinder);
- return -1;
-}
-
for (i = 0; i num_parts; i++) {
if (p_info[i].id 0 IS_PRIMARY(p_info[i].num))
pri++;
@@ -1637,8 +1631,7 @@ decide_on_geometry(void) {
if (user_cylinders 0)
cylinders = user_cylinders;
-total_size = cylinder_size*cylinders;
-if (total_size actual_size)
+if (cylinder_size * cylinders actual_size)
print_warning(_(You specified more cylinders than fit on disk));
}
@@ -1646,7 +1639,7 @@ static void
clear_p_info(void) {
num_parts = 1;
p_info[0].first_sector = 0;
-p_info[0].last_sector = total_size - 1;
+p_info[0].last_sector = actual_size - 1;
p_info[0].offset = 0;
p_info[0].flags = 0;
p_info[0].id = FREE_SPACE;
@@ -2429,7 +2422,7 @@ change_geometry(void) {
if (ret_val) {
long long disk_end;
- disk_end = total_size-1;
+ disk_end = actual_size-1;
if (p_info[num_parts-1].last_sector disk_end) {
while (p_info[num_parts-1].first_sector disk_end) {
--
1.7.9.rc2
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656854: Bug#656248: Rise severity of usb-modeswitch 1.2.2 bugs
Hi, Ralf: note that #656248 _is_ closed but that you are now affected by #656854 which is a different beast, sorry. That's okay, I just wanted to make sure this is tracked somewhere, so it does not hit testing. I am using the package you created for the other bug to have a working printer until this is resolved. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 656688 to usb_modeswitch throws general protection errors to syslog
Processing commands for cont...@bugs.debian.org: retitle 656688 usb_modeswitch throws general protection errors to syslog Bug #656688 [usb-modeswitch] usb-modeswitch: no ttyHS* devices Bug #656854 [usb-modeswitch] usb-modeswitch throws general protection error and umts modem is unusable Changed Bug title to 'usb_modeswitch throws general protection errors to syslog' from 'usb-modeswitch: no ttyHS* devices' Changed Bug title to 'usb_modeswitch throws general protection errors to syslog' from 'usb-modeswitch throws general protection error and umts modem is unusable' thanks Stopping processing here. Please contact me if you need assistance. -- 656688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636910: marked as done ([xine-lib-1.2] unable to load addon xine: Can't locate Debian/Debhelper/Sequence/xine.pm)
Your message dated Sun, 22 Jan 2012 21:53:21 + with message-id e1rp5ll-0003lf...@franck.debian.org and subject line Bug#636910: fixed in xine-lib-1.2 1.2.0-4 has caused the Debian Bug report #636910, regarding [xine-lib-1.2] unable to load addon xine: Can't locate Debian/Debhelper/Sequence/xine.pm 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.) -- 636910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libxine-dev Version: 1.1.90hg+20110516+847d4f89a4fb-1 Severity: serious Justification: kdebase-runtime ftbfs Tags: patch Hi, Typical amd64 experimental system. Trying to build kdebase-runtime, I get: $ debian/rules build /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.pl --with=kde,pkgkde-symbolshelper --with=xine error: unable to load addon xine: Can't locate Debian/Debhelper/Sequence/xine.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.12.4 /usr/local/share/perl/5.12.4 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.12 /usr/share/perl/5.12 /usr/local/lib/site_perl .) at (eval 8) line 2. BEGIN failed--compilation aborted at (eval 8) line 2. make: *** [debian/dhmk_rules.mk] Error 2 The cause: xine.pm in libxine-dev is not in the right place: $ dpkg-query -L libxine-dev | grep xine.pm /usr/share/perl5/Debian/Debhelper/Sequence/xine.pm /usr/share/perl5/Debian/Debhelper/Sequence/xine.pm/xine.pm The following fixes it (or cherry-picking the fix from sid should work, too). --- debian/changelog |6 ++ debian/libxine-dev.install |2 +- 2 files changed, 7 insertions(+), 1 deletions(-) diff --git a/debian/changelog b/debian/changelog index 992e0f62..36dcf229 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +xine-lib-1.2 (1.1.90hg+20110516+847d4f89a4fb-1.1) local; urgency=low + + * Fix dh 7 xine sequence file installation. + + -- Jonathan Nieder jrnie...@gmail.com Sat, 06 Aug 2011 16:08:37 -0500 + xine-lib-1.2 (1.1.90hg+20110516+847d4f89a4fb-1) experimental; urgency=low * 1.2.x development branch snapshot. diff --git a/debian/libxine-dev.install b/debian/libxine-dev.install index 9dcf5dfc..d2df685f 100644 --- a/debian/libxine-dev.install +++ b/debian/libxine-dev.install @@ -4,4 +4,4 @@ debian/tmp/usr/lib/libxine*.so debian/tmp/usr/lib/pkgconfig/libxine.pc debian/tmp/usr/share/aclocal/xine.m4 debian/dh_xine usr/bin -debian/xine.pm usr/share/perl5/Debian/Debhelper/Sequence/xine.pm +debian/xine.pm usr/share/perl5/Debian/Debhelper/Sequence -- 1.7.6 ---End Message--- ---BeginMessage--- Source: xine-lib-1.2 Source-Version: 1.2.0-4 We believe that the bug you reported is fixed in the latest version of xine-lib-1.2, which is due to be installed in the Debian FTP archive: libxine-dev_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine-dev_1.2.0-4_amd64.deb libxine2-all-plugins_1.2.0-4_all.deb to main/x/xine-lib-1.2/libxine2-all-plugins_1.2.0-4_all.deb libxine2-bin_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-bin_1.2.0-4_amd64.deb libxine2-console_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-console_1.2.0-4_amd64.deb libxine2-dbg_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-dbg_1.2.0-4_amd64.deb libxine2-doc_1.2.0-4_all.deb to main/x/xine-lib-1.2/libxine2-doc_1.2.0-4_all.deb libxine2-ffmpeg_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-ffmpeg_1.2.0-4_amd64.deb libxine2-gnome_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-gnome_1.2.0-4_amd64.deb libxine2-misc-plugins_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-misc-plugins_1.2.0-4_amd64.deb libxine2-plugins_1.2.0-4_all.deb to main/x/xine-lib-1.2/libxine2-plugins_1.2.0-4_all.deb libxine2-vdr_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-vdr_1.2.0-4_amd64.deb libxine2-x_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-x_1.2.0-4_amd64.deb libxine2_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2_1.2.0-4_amd64.deb xine-lib-1.2_1.2.0-4.debian.tar.bz2 to main/x/xine-lib-1.2/xine-lib-1.2_1.2.0-4.debian.tar.bz2 xine-lib-1.2_1.2.0-4.dsc to main/x/xine-lib-1.2/xine-lib-1.2_1.2.0-4.dsc 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 636...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp.
Bug#656501: marked as done (xine-ui: unowned files after purge (policy 6.8) violating FHS (policy 9.1) too)
Your message dated Sun, 22 Jan 2012 21:53:21 + with message-id e1rp5ll-0003ll...@franck.debian.org and subject line Bug#656501: fixed in xine-lib-1.2 1.2.0-4 has caused the Debian Bug report #656501, regarding xine-ui: unowned files after purge (policy 6.8) violating FHS (policy 9.1) too 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.) -- 656501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xine-ui Version: 0.99.6-1.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails From the attached log (scroll to the bottom...): 0m32.0s ERROR: FAIL: Package purging left files on system: /root/.xinenot owned /root/.xine/catalog.cache not owned As putting files into /root is also a violation of http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 I'm setting the severity to serious. cheers, Andreas xine-ui_0.99.6-1.1.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: xine-lib-1.2 Source-Version: 1.2.0-4 We believe that the bug you reported is fixed in the latest version of xine-lib-1.2, which is due to be installed in the Debian FTP archive: libxine-dev_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine-dev_1.2.0-4_amd64.deb libxine2-all-plugins_1.2.0-4_all.deb to main/x/xine-lib-1.2/libxine2-all-plugins_1.2.0-4_all.deb libxine2-bin_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-bin_1.2.0-4_amd64.deb libxine2-console_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-console_1.2.0-4_amd64.deb libxine2-dbg_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-dbg_1.2.0-4_amd64.deb libxine2-doc_1.2.0-4_all.deb to main/x/xine-lib-1.2/libxine2-doc_1.2.0-4_all.deb libxine2-ffmpeg_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-ffmpeg_1.2.0-4_amd64.deb libxine2-gnome_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-gnome_1.2.0-4_amd64.deb libxine2-misc-plugins_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-misc-plugins_1.2.0-4_amd64.deb libxine2-plugins_1.2.0-4_all.deb to main/x/xine-lib-1.2/libxine2-plugins_1.2.0-4_all.deb libxine2-vdr_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-vdr_1.2.0-4_amd64.deb libxine2-x_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2-x_1.2.0-4_amd64.deb libxine2_1.2.0-4_amd64.deb to main/x/xine-lib-1.2/libxine2_1.2.0-4_amd64.deb xine-lib-1.2_1.2.0-4.debian.tar.bz2 to main/x/xine-lib-1.2/xine-lib-1.2_1.2.0-4.debian.tar.bz2 xine-lib-1.2_1.2.0-4.dsc to main/x/xine-lib-1.2/xine-lib-1.2_1.2.0-4.dsc 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 656...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. li...@youmustbejoking.demon.co.uk (supplier of updated xine-lib-1.2 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 22 Jan 2012 21:03:47 + Source: xine-lib-1.2 Binary: libxine2-doc libxine2 libxine2-bin libxine-dev libxine2-ffmpeg libxine2-gnome libxine2-console libxine2-vdr libxine2-x libxine2-misc-plugins libxine2-dbg libxine2-plugins libxine2-all-plugins Architecture: source all amd64 Version: 1.2.0-4 Distribution: experimental Urgency: low Maintainer: Darren Salt li...@youmustbejoking.demon.co.uk Changed-By: li...@youmustbejoking.demon.co.uk Description: libxine-dev - the xine video player library, development packages libxine2 - the xine media player library, meta-package (development branch) libxine2-all-plugins - the xine video/media player library, meta package libxine2-bin - the xine video/media player library, binary files libxine2-console - libaa/libcaca/framebuffer/directfb related plugins for libxine2 libxine2-dbg - debug symbols for libxine2 libxine2-doc - the xine video player library, documentation files libxine2-ffmpeg - MPEG-related plugins for libxine2 libxine2-gnome - GNOME-related plugins for libxine2 libxine2-misc-plugins - Input, audio output and post plugins for libxine2 libxine2-plugins - the xine
Bug#642266: marked as done (ruby-ffi: FTBFS on sparc)
Your message dated Sun, 22 Jan 2012 22:03:29 + with message-id e1rp5vz-0005cz...@franck.debian.org and subject line Bug#642266: fixed in ruby-ffi 1.0.11debian-3 has caused the Debian Bug report #642266, regarding ruby-ffi: FTBFS on sparc 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.) -- 642266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby-ffi Severity: serious Relevant part of the build log: /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb make[1]: Entering directory `/build/buildd-ruby-ffi_1.0.9+git20110920debian-1-sparc-gQa_Ad/ruby-ffi-1.0.9+git20110920debian' cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/Benchmark.c -o build/libtest/Benchmark.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/BoolTest.c -o build/libtest/BoolTest.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/BufferTest.c -o build/libtest/BufferTest.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/ClosureTest.c -o build/libtest/ClosureTest.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/EnumTest.c -o build/libtest/EnumTest.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/FunctionTest.c -o build/libtest/FunctionTest.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/GlobalVariable.c -o build/libtest/GlobalVariable.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/LastErrorTest.c -o build/libtest/LastErrorTest.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/NumberTest.c -o build/libtest/NumberTest.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/PointerTest.c -o build/libtest/PointerTest.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/ReferenceTest.c -o build/libtest/ReferenceTest.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/StringTest.c -o build/libtest/StringTest.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/StructTest.c -o build/libtest/StructTest.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/UnionTest.c -o build/libtest/UnionTest.o cc -O2 -fno-omit-frame-pointer -fno-strict-aliasing -W -Werror -Wall -Wno-unused -Wno-parentheses -Ibuild -fPIC -D_REENTRANT -c libtest/VariadicTest.c -o build/libtest/VariadicTest.o cc -o build/libtest.so -shared -mimpure-text -Wl,-O1 -Wl,-soname,libtest.so build/libtest/Benchmark.o build/libtest/BoolTest.o build/libtest/BufferTest.o build/libtest/ClosureTest.o build/libtest/EnumTest.o build/libtest/FunctionTest.o build/libtest/GlobalVariable.o build/libtest/LastErrorTest.o build/libtest/NumberTest.o build/libtest/PointerTest.o build/libtest/ReferenceTest.o build/libtest/StringTest.o build/libtest/StructTest.o build/libtest/UnionTest.o build/libtest/VariadicTest.o -lm make[1]: Leaving directory `/build/buildd-ruby-ffi_1.0.9+git20110920debian-1-sparc-gQa_Ad/ruby-ffi-1.0.9+git20110920debian' ./spec/ffi/custom_type_spec.rb:24: warning: already initialized constant ToNativeMap ./spec/ffi/custom_type_spec.rb:25: warning: already initialized constant FromNativeMap ./spec/ffi/custom_type_spec.rb:22: warning: already initialized constant Custom_enum ./spec/ffi/custom_type_spec.rb:24: warning: already initialized constant ToNativeMap ./spec/ffi/custom_type_spec.rb:25: warning: already initialized constant FromNativeMap
Processed: downgrading to important
Processing commands for cont...@bugs.debian.org: severity 642267 important Bug #642267 [ruby-ffi] ruby-ffi: FTBFS on ia64 Severity set to 'important' from 'serious' retitle 642267 ruby-ffi: returning struct by value does not work on ia64 Bug #642267 [ruby-ffi] ruby-ffi: FTBFS on ia64 Changed Bug title to 'ruby-ffi: returning struct by value does not work on ia64' from 'ruby-ffi: FTBFS on ia64' thanks Stopping processing here. Please contact me if you need assistance. -- 642267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: block 655788 by 656922 Bug #655788 [src:igstk] igstk: FTBFS: libITKIO.so: undefined reference to `gdcm::PixmapToPixmapFilter::SetInput(gdcm::Pixmap const)' Was not blocked by any bugs. Added blocking bug(s) of 655788: 656922 End of message, stopping processing here. Please contact me if you need assistance. -- 655788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629952: subversion fails to build for stable(-security) on kfreebsd
On Sun, 2012-01-22 at 22:32 +0100, Aurelien Jarno wrote: On Thu, Jan 05, 2012 at 07:13:35PM +0100, Moritz Muehlenhoff wrote: On Thu, Jun 16, 2011 at 07:33:34PM +0200, Aurelien Jarno wrote: I think it builds fine on non-smp buildds, which at the time of the Squeeze release were fano and finzi. They have been switched to SMP a few weeks ago. Maybe we should switch them back to non-SMP? Alternatively I can build them manually to solve this situation, though it will only hide the problem. Can you upload manual builds? The archs need to be in sync for acceptance in the upcoming 6.0.4 point release of Squeeze. I have built both kfreebsd-amd64 and kfreebsd-i386 versions on non-SMP machines. I have just uploaded the resulting packages. Thanks. I can see the new packages on ftp-master, but they don't appear to be on security.d.o yet? Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656923: zfs-fuse: Please readd powerpc (built for 0.7.0-3)
Package: zfs-fuse Version: 0.7.0-4 Severity: serious Tags: sid As this built before on powerpc, I believe that serious is appropriate. Please change severity if I'm wrong. https://buildd.debian.org/status/logs.php?pkg=zfs-fusearch=powerpc -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric-proposed'), (500, 'oneiric'), (100, 'oneiric-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-15-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#238245: license choice - consensus on dual MIT/GPL-2 ?
On Tue, Jan 17, 2012 at 11:11:48PM +0100, Stefano Zacchiroli wrote: [ TL;DR: would you object re-licensing www.d.o content under dual MIT/Expat + GPL-2 ? ] What do you think? I am happy for all my contributions I have done for the Debian website (which admittedly have not been a lot recently) including any of the scripts or php dynamic pages (if any are left) to be re-licensed under the dual-license MIT/Expat and GPL-2+ I'm not sure if nm.d.o carries any of my code anymore but it covers that. I have no problems with the or later and actually consider it an essential part of the license for GPL. FWIW anything I contribute in future can also be licensed under this dual license too. Stefano, there's a bunch of stuff at SPI I did too, let me know if they want something similar. I cannot remember now what I said about their logo for example. - Craig -- Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 signature.asc Description: Digital signature
Bug#629952: subversion fails to build for stable(-security) on kfreebsd
On Sun, Jan 22, 2012 at 10:11:40PM +, Adam D. Barratt wrote: On Sun, 2012-01-22 at 22:32 +0100, Aurelien Jarno wrote: On Thu, Jan 05, 2012 at 07:13:35PM +0100, Moritz Muehlenhoff wrote: On Thu, Jun 16, 2011 at 07:33:34PM +0200, Aurelien Jarno wrote: I think it builds fine on non-smp buildds, which at the time of the Squeeze release were fano and finzi. They have been switched to SMP a few weeks ago. Maybe we should switch them back to non-SMP? Alternatively I can build them manually to solve this situation, though it will only hide the problem. Can you upload manual builds? The archs need to be in sync for acceptance in the upcoming 6.0.4 point release of Squeeze. I have built both kfreebsd-amd64 and kfreebsd-i386 versions on non-SMP machines. I have just uploaded the resulting packages. Thanks. I can see the new packages on ftp-master, but they don't appear to be on security.d.o yet? Yes, I first uploaded them to ftp-master until I realized I should have uploaded them to security-master. I have done that half an hour ago, they arrived in the embargoed queue, and they should be publicly available in the next minutes. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629952: subversion fails to build for stable(-security) on kfreebsd
On Sun, 2012-01-22 at 23:20 +0100, Aurelien Jarno wrote: On Sun, Jan 22, 2012 at 10:11:40PM +, Adam D. Barratt wrote: On Sun, 2012-01-22 at 22:32 +0100, Aurelien Jarno wrote: I have built both kfreebsd-amd64 and kfreebsd-i386 versions on non-SMP machines. I have just uploaded the resulting packages. Thanks. I can see the new packages on ftp-master, but they don't appear to be on security.d.o yet? Yes, I first uploaded them to ftp-master until I realized I should have uploaded them to security-master. I have done that half an hour ago, they arrived in the embargoed queue, and they should be publicly available in the next minutes. Looks like they're there now; thanks. Predictably the keys for most of the other architectures have expired in the meantime, but that's another issue (that most of the current recipients probably don't care about). Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: aboot FTBFS in unstable
Processing commands for cont...@bugs.debian.org: # peter green wrote: # # tags 652598 +wheezy sid # thanks # # Forwarding to the control server. #tags 652598 +notsqueeze tags 652598 + wheezy sid experimental Bug #652598 [src:aboot] aboot FTBFS in unstable Added tag(s) sid, wheezy, and experimental. End of message, stopping processing here. Please contact me if you need assistance. -- 652598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656581: usbmuxd: buffer overflow introduced in 1.0.7 (CVE-2012-0065)
Le 01/21/2012 09:14 AM, Yves-Alexis Perez a écrit : On ven., 2012-01-20 at 22:59 +0100, Julien Lavergne wrote: Thanks, revision 1.0.7-2 with the upstream patch is available on mentors. Does this mean you need one? Yes, my regular sponsor is not available, but I can do a proper RFS tomorrow. Regards, Julien Lavergne -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656929: char/wchar_t disparity, cannot link with libmediainfo.pc's settings
Package: libmediainfo-dev Version: 0.7.52-1 Severity: serious Hello, currently, if an application relies on the flags returned from pkgconfig for libmediainfo, the application cannot be linked! This happens because MediaInfo_Const.h makes use of the _UNICODE definition to create the type definition for the String class used in the library interfaces. This trick is ok for Win32 environment but not for Unix where there is no such convention. Another application doesn't know how libmediainfo was compiled, and cannot guess. OTOH that's what pkgconfig is for. libmediainfo.pc should export the required definition flags for the compiler. Or maybe create a custom def.var (like MEDIAINFO_UNICODE) in order to avoid interference with other flags, and MediaInfo_Const.h would contain something like #if defined(UNICODE) || defined (_UNICODE) || defined (MEDIAINFO_UNICODE) instead of #if defined(UNICODE) || defined (_UNICODE). Regards, Eduard. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.1 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libmediainfo-dev depends on: ii libmediainfo0 0.7.52-1 ii libzen-dev 0.4.23-3 libmediainfo-dev recommends no packages. libmediainfo-dev suggests no packages. -- no debconf information -- * alphascorpii kuckt Sex and the City und fühlt sich befremdet alphascorpii Dann doch lieber Angriff der Killerbienen alphascorpii ... ist ja auch irgendwie das selbe ;) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645112: marked as done (zsh: FTBFS: configure: error: No terminal handling library was found on your system.)
Your message dated Sun, 22 Jan 2012 23:04:13 +
with message-id e1rp6sl-0004vf...@franck.debian.org
and subject line Bug#645112: fixed in zsh 4.3.15-1
has caused the Debian Bug report #645112,
regarding zsh: FTBFS: configure: error: No terminal handling library was found
on your system.
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.)
--
645112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libncurses5-dev
Version: 5.9-2
Severity: serious
X-Debbugs-CC: Matthias Klose d...@debian.org
Static linking with -lncurses fails if you need symbols from libtinfo:
,
| $ cat foo.c
| #include term.h
| #include stdlib.h
|
| int main(void)
| {
| return tgetent(NULL, );
| }
| $ LANG=C gcc foo.c -lncurses -static
| /tmp/ccRe0RW2.o: In function `main':
| foo.c:(.text+0x19): undefined reference to `tgetent'
| collect2: ld returned 1 exit status
`
This makes zsh and possibly a few other packages FTBFS.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.1.0-rc9-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libncurses5-dev depends on:
ii libc6-dev [libc-dev] 2.13-21
ii libncurses5 5.9-2
ii libtinfo-dev 5.9-2
ii ncurses-bin 5.9-2
libncurses5-dev recommends no packages.
Versions of packages libncurses5-dev suggests:
ii ncurses-doc 5.9-2
-- no debconf information
---End Message---
---BeginMessage---
Source: zsh
Source-Version: 4.3.15-1
We believe that the bug you reported is fixed in the latest version of
zsh, which is due to be installed in the Debian FTP archive:
zsh-dbg_4.3.15-1_amd64.deb
to main/z/zsh/zsh-dbg_4.3.15-1_amd64.deb
zsh-dev_4.3.15-1_amd64.deb
to main/z/zsh/zsh-dev_4.3.15-1_amd64.deb
zsh-doc_4.3.15-1_all.deb
to main/z/zsh/zsh-doc_4.3.15-1_all.deb
zsh-static_4.3.15-1_amd64.deb
to main/z/zsh/zsh-static_4.3.15-1_amd64.deb
zsh_4.3.15-1.debian.tar.gz
to main/z/zsh/zsh_4.3.15-1.debian.tar.gz
zsh_4.3.15-1.dsc
to main/z/zsh/zsh_4.3.15-1.dsc
zsh_4.3.15-1_amd64.deb
to main/z/zsh/zsh_4.3.15-1_amd64.deb
zsh_4.3.15.orig.tar.bz2
to main/z/zsh/zsh_4.3.15.orig.tar.bz2
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 645...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Axel Beckert a...@debian.org (supplier of updated zsh 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...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 22 Jan 2012 20:51:58 +0100
Source: zsh
Binary: zsh zsh-doc zsh-static zsh-dev zsh-dbg
Architecture: source all amd64
Version: 4.3.15-1
Distribution: unstable
Urgency: low
Maintainer: Debian Zsh Maintainers pkg-zsh-de...@lists.alioth.debian.org
Changed-By: Axel Beckert a...@debian.org
Description:
zsh- shell with lots of features
zsh-dbg- shell with lots of features (debugging symbols)
zsh-dev- shell with lots of features (development files)
zsh-doc- zsh documentation - info/HTML format
zsh-static - shell with lots of features (static link)
Closes: 603503 624497 630906 631795 632140 634609 641162 644179 645112 646046
Changes:
zsh (4.3.15-1) unstable; urgency=low
.
* New upstream release
+ [45913f43] Allow closing of fd's not recorded by the shell
(Closes: #644179)
+ [2938c58c] replace overlapping strcpy with memmove (Closes: #624497)
+ Includes new _git implementation (Closes: #630906, #603503)
.
[ Frank Terbeck ]
* [c63c0d79] Adding support for (un)markauto in _apt (Closes: #631795)
* [fd222338] Support -F completion for aptitude (Closes: #632140)
* [fbaba904, 7c61c918] Use one positive arch-spec instead of several negated
ones (Closes: #634609)
* [af2bb4fd] Removing upstream patches due to new release
* [ea0e8c35] at2quilt: Updating autotools patches
.
[ Michael Prokop ]
* [21e7021b] provide debian/gbp.conf for git-buildpackage and friends
.
[ Mitsuya Shibata ]
* [1e111f71] Add tinfo to --with-term-lib flag (Closes: #645112)
.
[ Ansgar Burchardt ]
* [add75037]
Bug#656756: marked as done (shogun: Please use debians default csharp compiler)
Your message dated Sun, 22 Jan 2012 23:03:39 + with message-id e1rp6rn-0004aw...@franck.debian.org and subject line Bug#656756: fixed in shogun 1.1.0-2 has caused the Debian Bug report #656756, regarding shogun: Please use debians default csharp compiler 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.) -- 656756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: shogun Version: 1.1.0-1 Severity: serious Justification: fails to build from source User: debian-...@lists.debian.org Usertags: mono-2.10-transition mono-2.10-transition-gmcs The package shogun requires gmcs to build. In mono 2.10, uploaded to unstable a short while ago, the default csharp compiler has change from gmcs to dmcs. mono-gmcs will not be installed by mono-devel anymore. Please use the default compiler mono-csc or explicitly build depend on an appropriate version of mono-gmcs. For more information see [0,1] or visit #debian-cli [0] http://wiki.debian.org/Teams/DebianMonoGroup/Mono210Transition [1] http://www.mono-project.com/CSharp_Compiler signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: shogun Source-Version: 1.1.0-2 We believe that the bug you reported is fixed in the latest version of shogun, which is due to be installed in the Debian FTP archive: libshogun-dev_1.1.0-2_amd64.deb to main/s/shogun/libshogun-dev_1.1.0-2_amd64.deb libshogun11_1.1.0-2_amd64.deb to main/s/shogun/libshogun11_1.1.0-2_amd64.deb shogun-cmdline-static_1.1.0-2_amd64.deb to main/s/shogun/shogun-cmdline-static_1.1.0-2_amd64.deb shogun-csharp-modular_1.1.0-2_amd64.deb to main/s/shogun/shogun-csharp-modular_1.1.0-2_amd64.deb shogun-dbg_1.1.0-2_amd64.deb to main/s/shogun/shogun-dbg_1.1.0-2_amd64.deb shogun-doc-cn_1.1.0-2_all.deb to main/s/shogun/shogun-doc-cn_1.1.0-2_all.deb shogun-doc-en_1.1.0-2_all.deb to main/s/shogun/shogun-doc-en_1.1.0-2_all.deb shogun-elwms-static_1.1.0-2_amd64.deb to main/s/shogun/shogun-elwms-static_1.1.0-2_amd64.deb shogun-java-modular_1.1.0-2_amd64.deb to main/s/shogun/shogun-java-modular_1.1.0-2_amd64.deb shogun-lua-modular_1.1.0-2_amd64.deb to main/s/shogun/shogun-lua-modular_1.1.0-2_amd64.deb shogun-python-modular_1.1.0-2_amd64.deb to main/s/shogun/shogun-python-modular_1.1.0-2_amd64.deb shogun-python-static_1.1.0-2_amd64.deb to main/s/shogun/shogun-python-static_1.1.0-2_amd64.deb shogun-r-static_1.1.0-2_amd64.deb to main/s/shogun/shogun-r-static_1.1.0-2_amd64.deb shogun-ruby-modular_1.1.0-2_amd64.deb to main/s/shogun/shogun-ruby-modular_1.1.0-2_amd64.deb shogun_1.1.0-2.debian.tar.gz to main/s/shogun/shogun_1.1.0-2.debian.tar.gz shogun_1.1.0-2.dsc to main/s/shogun/shogun_1.1.0-2.dsc 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 656...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Soeren Sonnenburg so...@debian.org (supplier of updated shogun 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 22 Jan 2012 19:26:12 +0100 Source: shogun Binary: libshogun11 libshogun-dev shogun-doc-en shogun-doc-cn shogun-dbg shogun-python-modular shogun-lua-modular shogun-ruby-modular shogun-java-modular shogun-csharp-modular shogun-python-static shogun-cmdline-static shogun-r-static shogun-elwms-static Architecture: source all amd64 Version: 1.1.0-2 Distribution: unstable Urgency: low Maintainer: Soeren Sonnenburg so...@debian.org Changed-By: Soeren Sonnenburg so...@debian.org Description: libshogun-dev - Large Scale Machine Learning Toolbox libshogun11 - Large Scale Machine Learning Toolbox shogun-cmdline-static - Large Scale Machine Learning Toolbox shogun-csharp-modular - Large Scale Machine Learning Toolbox shogun-dbg - Large Scale Machine Learning Toolbox shogun-doc-cn - Large Scale Machine Learning Toolbox shogun-doc-en - Large Scale Machine Learning Toolbox shogun-elwms-static - Large Scale Machine Learning Toolbox shogun-java-modular - Large Scale Machine Learning Toolbox shogun-lua-modular - Large Scale Machine Learning Toolbox shogun-python-modular - Large Scale Machine Learning Toolbox shogun-python-static - Large Scale
Processed (with 1 errors): Re: irrlicht: Please Build-Depends on libjpeg-dev, not libjpeg62-dev
Processing commands for cont...@bugs.debian.org:
# Bill Allombert wrote:
#
# We are transitionning from libjpeg62 to libjpeg8.
[...]
Unknown command or malformed arguments to command.
# I am raising the severity to serious because irrlicht FTBFS due to
conflicting
# build-deps.
#
# Luckily not in squeeze.
#tags 634032 +notsqueeze
tags 634032 + wheezy sid experimental
Bug #634032 {Done: Didier Raboud o...@debian.org} [src:irrlicht] irrlicht:
Please Build-Depends on libjpeg-dev, not libjpeg62-dev
Added tag(s) sid, wheezy, and experimental.
End of message, stopping processing here.
Please contact me if you need assistance.
--
634032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654395: additional patches for newer libav sources
On 01/22/2012 11:48 AM, Kevin Roy wrote: Hi John, -- First, this patch does not have anything related to this bug report so next time, you are more than welcome to open another bug report. Next, I don't know how your patch managed to negates the patch 0009 but if it does, it's not the good way to solve this. Instead, an update to the ffmpeg_compat.h is only needed (cf patch attached to #656502). Thanks for your concern in blender package, Cheers I apologize for posting to this bug improperly. In my haste to get blender working on my system again, I jumped at a chance to help. I realize now that my method and actions have actually led to disrupting the people doing work that is over my head. In the future, I will think more carefully before I post and to be more thorough in checking that I'm posting to the correct bug. I certainly didn't intend to step on toes, but it's clear to me now that I did. Thank you for your patience and forbearance. Cordially, John -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656938: ideviceinstaller FTBFS on 32-bit architectures, format string errors.
package: ideviceinstaller
version: 1.0.0-1.1
severity: serious
tags: patch
gcc -DHAVE_CONFIG_H -I. -I..-Wall -Wextra -Wmissing-declarations
-Wredundant-decls -Wshadow -Wpointer-arith -Wwrite-strings -Wswitch-default
-Wno-unused-parameter -Werror -g -pthread -I/usr/include/glib-2.0
-I/usr/lib/arm-linux-gnueabi/glib-2.0/include -I/usr/include/p11-kit-1
-I/usr/include/libxml2 -I/usr/include/libxml2 -I/usr/lib/libzip/include
-g -O2 -c -o ideviceinstaller-ideviceinstaller.o `test -f 'ideviceinstaller.c'
|| echo './'`ideviceinstaller.c
ideviceinstaller.c: In function 'zip_f_get_contents':
ideviceinstaller.c:165:3: error: format '%ld' expects argument of type 'long
int', but argument 3 has type 'zip_uint64_t' [-Werror=format]
cc1: all warnings being treated as errors
I have attatched an updated verion of 653893-libzip-0.10.patch which typecasts the value
to type unsigned long long and changes the format specifier to %llu.
Description: fix build failure with libzip 0.10
zip_fread returns signed int64 while zip_stat size is an unsigned int64.
From: Fathi Boudra f...@debian.org
Bug-Debian: http://bugs.debian.org/653893
---
src/ideviceinstaller.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: ideviceinstaller-1.0.0/src/ideviceinstaller.c
===
--- ideviceinstaller-1.0.0.orig/src/ideviceinstaller.c 2011-03-19 15:56:32.0 +
+++ ideviceinstaller-1.0.0/src/ideviceinstaller.c 2012-01-22 23:50:01.0 +
@@ -161,8 +161,8 @@
}
*buffer = malloc(zs.size);
- if (zip_fread(zfile, *buffer, zs.size) != zs.size) {
- fprintf(stderr, ERROR: zip_fread %ld bytes from '%s'\n, zs.size, filename);
+ if (zs.sizeLLONG_MAX || zip_fread(zfile, *buffer, zs.size) != (zip_int64_t)zs.size) {
+ fprintf(stderr, ERROR: zip_fread %llu bytes from '%s'\n, (unsigned long long)(zs.size), filename);
free(*buffer);
*buffer = NULL;
zip_fclose(zfile);
