Bug#764196: maildir-utils: FTBFS on arm*
On Tue, Oct 7, 2014 at 10:02:53 +0900, Norbert Preining wrote: Hi Hector, On Mon, 06 Oct 2014, Hector Oron wrote: /usr/bin/guile-snarf: 54: /usr/bin/guile-snarf: gcc-4.8: not found Hmm, this is really strange. There was a bug in guile-2.0-dev that had the gcc hard-coded. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759096 That was fixed, so I bumped the build-dep onto the correct guile-2.0-dev version. Also, checking the actual content of guile-snarf in the current ARM package, I don't see any occurrence of gcc-4.8 Err. Not sure how you did that, but: $ dpkg --fsys-tarfile /srv/ftp-master.debian.org/ftp/pool/main/g/guile-2.0/guile-2.0-dev_2.0.11+1-7_armel.deb |tar xOf - ./usr/bin/guile-snarf | grep gcc-4.8 # C pre-processor determined at Guile configure-time: gcc-4.8 -E. if [ x$CPP = x ] ; then cpp=gcc-4.8 -E ; else cpp=$CPP ; fi (and same in 2.0.11+1-8) So I think guile-2.0-dev needs a dependency on gcc-4.8 on those archs. Cheers, Julien signature.asc Description: Digital signature
Bug#764196: maildir-utils: FTBFS on arm*
On Tue, 07 Oct 2014, Julien Cristau wrote: $ dpkg --fsys-tarfile /srv/ftp-master.debian.org/ftp/pool/main/g/guile-2.0/guile-2.0-dev_2.0.11+1-7_armel.deb |tar xOf - ./usr/bin/guile-snarf | grep gcc-4.8 # C pre-processor determined at Guile configure-time: gcc-4.8 -E. if [ x$CPP = x ] ; then cpp=gcc-4.8 -E ; else cpp=$CPP ; fi Ah, interesting ... I checked the arm64 (as it was the first listed and the bug reported said arm*) ... Indeed: arm64 is ok armel and armhf is bad, still has gcc-4.8 So I think guile-2.0-dev needs a dependency on gcc-4.8 on those archs. Indeed! Should I reopen the bug concerning this matter on guile-2.0-dev? All the best Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity
Processing commands for cont...@bugs.debian.org: severity 764291 grave Bug #764291 [chromium] chromium 37 for i386 is miscompiled - it crashes on CMOV and SSE instructions Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 764291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764291 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#720517: [PATCH] Bug#720517: dbconfig-common must not change ownership of files
Control: tags -1 -patch On 05-10-14 22:02, Paul Gevers wrote: Control: tags -1 patch For anybody reading this bug report before I upload the fix, I would really appreciate a review of my proposal, so please leave your comments here. So I let this issue ponder a bit and I concluded that my proposed fix is not good. The problem is that when a package that is already installed starts using dbconfig-common, the permissions won't be set appropriately. So the fix needs to be implemented otherwise. I have ideas, but I have to figure it out. Paul signature.asc Description: OpenPGP digital signature
Processed: Re: [PATCH] Bug#720517: dbconfig-common must not change ownership of files
Processing control commands: tags -1 -patch Bug #720517 [dbconfig-common] dbconfig-common must not change ownership of files Removed tag(s) patch. -- 720517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720517 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#764310: manpages-dev and libcerf-doc: error when trying to install together
Package: libcerf-doc,manpages-dev Version: libcerf-doc/1.3-1 Version: manpages-dev/3.71-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-10-07 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: Selecting previously unselected package libcerf-doc. (Reading database ... 10872 files and directories currently installed.) Preparing to unpack .../libcerf-doc_1.3-1_all.deb ... Unpacking libcerf-doc (1.3-1) ... Selecting previously unselected package manpages-dev. Preparing to unpack .../manpages-dev_3.71-1_all.deb ... Unpacking manpages-dev (3.71-1) ... dpkg: error processing archive /var/cache/apt/archives/manpages-dev_3.71-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/cerf.3.gz', which is also in package libcerf-doc 1.3-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db (2.7.0.2-1) ... Errors were encountered while processing: /var/cache/apt/archives/manpages-dev_3.71-1_all.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/share/man/man3/cerf.3.gz /usr/share/man/man3/cerfc.3.gz This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720517: configuration files, ownership and dpkg-statoverride
Hi, I am looking into dbconfig-common RC bug 720517 [1] and I was wondering what the general idea is of maintainer scripts changing the permissions and/or owners of configuration files and the use of dpkg-statoverride. I myself find it unacceptable that updating a package changes the permissions/owners of a configuration file without asking, even when I have not documented that fact with dpkg-statoverride. At least that is how I read policy 10.7.3 [2]. Do other people find it sensible that you need to document this fact with dpkg-statoverride? In other words, is it ok to change permissions and ownership as done by dbconfig-common if you didn't? Paul [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720517 [2] https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3 signature.asc Description: OpenPGP digital signature
Bug#758695: marked as done (python-traitsui: Please update to use wxpython3.0)
Your message dated Tue, 7 Oct 2014 19:42:41 +1300
with message-id 20141007064241.GA2337@debian
and subject line Re: Bug#758695: python-traitsui: Updated patch for wxPython 3.0
has caused the Debian Bug report #758695,
regarding python-traitsui: Please update to use wxpython3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
758695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-traitsui
Version: 4.4.0-1.1
Severity: important
Tags: patch sid jessie
User: freewx-ma...@lists.alioth.debian.org
Usertags: wxpy3.0
Control: block 755757 by -1
We're aiming to migrate the archive to using wxpython3.0 instead of
wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released.
I've rebuilt python-traitsui by simply updating the dependencies (see
the attached patch).
I tried to test it by running the tests it includes (using nose). I'm
not sure how useful these tests are, as they don't all pass before my
changes, but FWIW, I tested these two combinations:
python-wxgtk2.8 + python-traitsui 4.4.0-1.1 + python-pyface 4.4.0-1.1
python-wxgtk3.0 + patched python-traitsui + python-pyface 4.4.0-1.2 (see
The updated python-pyface also just updates the dependencies - see
#757313 for that patch.
Things actually look slightly better with the second one:
FAILED (SKIP=14, errors=1, failures=3)
---
FAILED (SKIP=14, failures=3)
I'm happy to NMU these changes.
Cheers,
Olly
diff -Nru python-traitsui-4.4.0/debian/changelog python-traitsui-4.4.0/debian/changelog
--- python-traitsui-4.4.0/debian/changelog 2014-07-07 08:06:33.0 +1200
+++ python-traitsui-4.4.0/debian/changelog 2014-08-18 02:57:06.0 +1200
@@ -1,3 +1,10 @@
+python-traitsui (4.4.0-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Update dependency on python-wxgtk2.8 to python-wxgtk3.0.
+
+ -- Olly Betts o...@survex.com Mon, 18 Aug 2014 02:56:21 +1200
+
python-traitsui (4.4.0-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru python-traitsui-4.4.0/debian/control python-traitsui-4.4.0/debian/control
--- python-traitsui-4.4.0/debian/control 2014-03-16 16:52:33.0 +1300
+++ python-traitsui-4.4.0/debian/control 2014-08-18 02:56:11.0 +1200
@@ -13,7 +13,7 @@
Package: python-traitsui
Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, python-traits, python-pyface, python-wxgtk2.8
+Depends: ${python:Depends}, ${misc:Depends}, python-traits, python-pyface, python-wxgtk3.0
Breaks: python-traitsgui, python-traitsbackendqt, python-traitsbackendwx
Replaces: python-traitsgui, python-traitsbackendqt, python-traitsbackendwx
Description: traits-capable user interfaces
---End Message---
---BeginMessage---
I NMUed this on 2014-09-28 but the changelog entry didn't close the bug:
python-traitsui (4.4.0-1.3) unstable; urgency=medium
* Non-maintainer upload.
* Improve wxpython3.0.patch so mayavi2 works.
-- Olly Betts o...@survex.com Sat, 20 Sep 2014 00:05:20 +
Cheers,
Olly---End Message---
Bug#758939: mayavi2: diff for NMU version 4.3.1-3.1
Control: tags 758939 + pending
Dear maintainer,
I've uploaded an NMU for mayavi2 (versioned as 4.3.1-3.1).
This is the same diff I sent before but with the changelog
entry tweaked.
Cheers,
Olly
diff -Nru mayavi2-4.3.1/debian/changelog mayavi2-4.3.1/debian/changelog
--- mayavi2-4.3.1/debian/changelog 2014-06-17 18:37:54.0 +1200
+++ mayavi2-4.3.1/debian/changelog 2014-10-07 19:41:05.0 +1300
@@ -1,3 +1,11 @@
+mayavi2 (4.3.1-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload with maintainer's permission.
+ * Update for wxpython3.0 (Closes: #758939):
++ New patch: wxpy3.0-compat.patch
+
+ -- Olly Betts o...@survex.com Tue, 07 Oct 2014 06:40:35 +
+
mayavi2 (4.3.1-3) unstable; urgency=medium
* d/rules: remove references to pyshared (Closes: #746762)
diff -Nru mayavi2-4.3.1/debian/control mayavi2-4.3.1/debian/control
--- mayavi2-4.3.1/debian/control 2014-03-16 17:06:34.0 +1300
+++ mayavi2-4.3.1/debian/control 2014-09-01 05:59:14.0 +1200
@@ -14,7 +14,7 @@
Package: mayavi2
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends},
- python-traits, python-traitsui, python-wxgtk2.8, python-numpy,
+ python-traits, python-traitsui, python-wxgtk3.0, python-numpy,
python-vtk (= 5.4.2-5), python-pkg-resources, python-envisage,
python-apptools (= 4.0.0-1), libjs-jquery, python-configobj
Suggests: python-scipy, ipython
diff -Nru mayavi2-4.3.1/debian/patches/ipython.diff mayavi2-4.3.1/debian/patches/ipython.diff
--- mayavi2-4.3.1/debian/patches/ipython.diff 2011-12-08 22:06:41.0 +1300
+++ mayavi2-4.3.1/debian/patches/ipython.diff 2014-09-20 12:49:41.0 +1200
@@ -1,8 +1,8 @@
-Index: mayavi2-4.0.0/mayavi/tests/README.txt
+Index: mayavi2-4.3.1/mayavi/tests/README.txt
===
mayavi2-4.0.0.orig/mayavi/tests/README.txt 2011-12-08 03:55:09.0 -0500
-+++ mayavi2-4.0.0/mayavi/tests/README.txt 2011-12-08 03:55:36.0 -0500
-@@ -47,7 +47,6 @@
+--- mayavi2-4.3.1.orig/mayavi/tests/README.txt
mayavi2-4.3.1/mayavi/tests/README.txt
+@@ -47,7 +47,6 @@ The IPython Shell can be embedded anywhe
You need to import the `IPython` module and then add the following
lines wherver you want to embed the shell::
diff -Nru mayavi2-4.3.1/debian/patches/series mayavi2-4.3.1/debian/patches/series
--- mayavi2-4.3.1/debian/patches/series 2011-12-09 17:32:05.0 +1300
+++ mayavi2-4.3.1/debian/patches/series 2014-09-01 06:01:52.0 +1200
@@ -1,2 +1,3 @@
help.diff
ipython.diff
+wxpy3.0-compat.patch
diff -Nru mayavi2-4.3.1/debian/patches/wxpy3.0-compat.patch mayavi2-4.3.1/debian/patches/wxpy3.0-compat.patch
--- mayavi2-4.3.1/debian/patches/wxpy3.0-compat.patch 1970-01-01 12:00:00.0 +1200
+++ mayavi2-4.3.1/debian/patches/wxpy3.0-compat.patch 2014-09-20 13:13:56.0 +1200
@@ -0,0 +1,127 @@
+Description: Fixes for wxPython 3.0
+ Retains compatibility with 2.8 - there wx.InitAllImageHandlers() is a no-op,
+ wx.HIDE_READONLY is 0, and wx.PySimpleApp() issues a deprecation warning.
+Author: Olly Betts o...@survex.com
+Bug-Debian: https://bugs.debian.org/758939
+Forwarded: no
+Last-Update: 2014-09-20
+
+Index: mayavi2-4.3.1/tvtk/pyface/ui/wx/init.py
+===
+--- mayavi2-4.3.1.orig/tvtk/pyface/ui/wx/init.py
mayavi2-4.3.1/tvtk/pyface/ui/wx/init.py
+@@ -22,10 +22,6 @@ if wx.VERSION (2, 6):
+ _app = wx.GetApp()
+
+ if _app is None:
+-_app = wx.PySimpleApp()
++_app = wx.App(False)
+-
+-# Before we can load any images we have to initialize wxPython's image
+-# handlers.
+-wx.InitAllImageHandlers()
+
+ EOF ##
+Index: mayavi2-4.3.1/tvtk/util/wx_gradient_editor.py
+===
+--- mayavi2-4.3.1.orig/tvtk/util/wx_gradient_editor.py
mayavi2-4.3.1/tvtk/util/wx_gradient_editor.py
+@@ -392,7 +392,7 @@ class wxGradientEditorWidget(wx.Panel, G
+ (lookuptable) ``*.grad`` (gradient table for use with this program),
+ and ``*.jpg`` (image of the gradient)
+
+-dlg = wx.FileDialog(self, Save LUT to..., style=wx.SAVE)
++dlg = wx.FileDialog(self, Save LUT to..., style=wx.FD_SAVE)
+ wildcard = Gradient Files (.grad)|*.grad| \
+All files (*.*)|*.*
+ dlg.SetWildcard(wildcard)
+@@ -405,7 +405,7 @@ class wxGradientEditorWidget(wx.Panel, G
+
+ Load a ``*.grad`` lookuptable file using wxpython dialog
+
+-style = wx.OPEN | wx.HIDE_READONLY
++style = wx.FD_OPEN
+ dlg = wx.FileDialog(self, Open a file, style=style)
+ wildcard = Gradient Files (.grad)|*.grad| \
+All files (*.*)|*.*
+@@ -510,7 +510,7 @@ def main():
+ If we had a vtk window running, update it here
+ print(Update Render
Processed: mayavi2: diff for NMU version 4.3.1-3.1
Processing control commands: tags 758939 + pending Bug #758939 [src:mayavi2] mayavi2: Please update to use wxpython3.0 Added tag(s) pending. -- 758939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758939 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#758939: marked as done (mayavi2: Please update to use wxpython3.0)
Your message dated Tue, 07 Oct 2014 07:04:05 + with message-id e1xboox-0002ns...@franck.debian.org and subject line Bug#758939: fixed in mayavi2 4.3.1-3.1 has caused the Debian Bug report #758939, regarding mayavi2: Please update to use wxpython3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 758939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mayavi2 Version: 4.3.1-3 Severity: important Tags: sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wxpy3.0 Control: block 755757 by -1 We're aiming to migrate the archive to using wxpython3.0 instead of wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released. This transition is already underway, and is being tracked by the release team here: https://release.debian.org/transitions/html/wxpython3.0.html The wxPython 3.0 API mostly adds to the wxPython2.8 API. Many packages work with wxPython 3.0 without any changes, but there are a few incompatibilities. For example, wx.Color is no longer supported as an alias for wx.Colour, and some constants which were deprecated in 2.8 have been removed. All the removed constants I'm aware of were set to 0 in wxPython 2.8, so removing them is still compatible with 2.8. To assist updating to wxPython 3.0, I've put together a script which will help make the mechanical changes required. This is in a git repo on collab-maint along with a README about using it and updating packages for wxPython 3.0 in general: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git The script has some options to control the sorts of changes it makes - see the README and --help output for more information - you can view the latest version of the README online here: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I've developed this script by trying to convert 20+ packages. Please try it out on your package - in many cases, it should be enough to get your package working (if it doesn't already) - if it does, please upload (and close this bug). If the script doesn't do the job, please let me know (or improve the script if you can figure out what it needs to do to get your package working). Another issue you may hit is that wxWidgets 3.0 now defaults to enabling its WXDEBUG checks for incorrect API usage, so some applications will emit scary sounding assertion failures. These are unlikely to actually be new, just in a default build of 2.8, such incorrect uses were handled quietly behind the scenes. Sometimes these are easy to fix, but if not you can easily patch the application to tell wx 3.0 to handle them in the same way wx 2.8 does - details of how to do so are in the README: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I'm happy to sponsor uploads for this transition, though if you have an active sponsor already check with them first - I don't want to tread on anyone's toes. Cheers, Olly ---End Message--- ---BeginMessage--- Source: mayavi2 Source-Version: 4.3.1-3.1 We believe that the bug you reported is fixed in the latest version of mayavi2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 758...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts o...@survex.com (supplier of updated mayavi2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Oct 2014 06:40:35 + Source: mayavi2 Binary: mayavi2 Architecture: source Version: 4.3.1-3.1 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org Changed-By: Olly Betts o...@survex.com Description: mayavi2- scientific visualization package for 2-D and 3-D data Closes: 758939 Changes: mayavi2 (4.3.1-3.1) unstable; urgency=medium . * Non-maintainer upload with maintainer's permission. * Update for wxpython3.0 (Closes: #758939): + New patch: wxpy3.0-compat.patch Checksums-Sha1: 5de8fd6143a9d27068f7e702d59386165618ae0c 2062 mayavi2_4.3.1-3.1.dsc 0bf29ef26c0022d98283774482838e05c55b2fa1 13836
Bug#758954: marked as done (drpython: Please update to use wxpython3.0)
Your message dated Tue, 07 Oct 2014 07:03:47 + with message-id e1xboof-0002k8...@franck.debian.org and subject line Bug#758954: fixed in drpython 1:3.11.4-1.1 has caused the Debian Bug report #758954, regarding drpython: Please update to use wxpython3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 758954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: drpython Version: 1:3.11.1-2 Severity: important Tags: sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wxpy3.0 Control: block 755757 by -1 We're aiming to migrate the archive to using wxpython3.0 instead of wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released. This transition is already underway, and is being tracked by the release team here: https://release.debian.org/transitions/html/wxpython3.0.html The wxPython 3.0 API mostly adds to the wxPython2.8 API. Many packages work with wxPython 3.0 without any changes, but there are a few incompatibilities. For example, wx.Color is no longer supported as an alias for wx.Colour, and some constants which were deprecated in 2.8 have been removed. All the removed constants I'm aware of were set to 0 in wxPython 2.8, so removing them is still compatible with 2.8. To assist updating to wxPython 3.0, I've put together a script which will help make the mechanical changes required. This is in a git repo on collab-maint along with a README about using it and updating packages for wxPython 3.0 in general: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git The script has some options to control the sorts of changes it makes - see the README and --help output for more information - you can view the latest version of the README online here: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I've developed this script by trying to convert 20+ packages. Please try it out on your package - in many cases, it should be enough to get your package working (if it doesn't already) - if it does, please upload (and close this bug). If the script doesn't do the job, please let me know (or improve the script if you can figure out what it needs to do to get your package working). Another issue you may hit is that wxWidgets 3.0 now defaults to enabling its WXDEBUG checks for incorrect API usage, so some applications will emit scary sounding assertion failures. These are unlikely to actually be new, just in a default build of 2.8, such incorrect uses were handled quietly behind the scenes. Sometimes these are easy to fix, but if not you can easily patch the application to tell wx 3.0 to handle them in the same way wx 2.8 does - details of how to do so are in the README: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I'm happy to sponsor uploads for this transition, though if you have an active sponsor already check with them first - I don't want to tread on anyone's toes. Cheers, Olly ---End Message--- ---BeginMessage--- Source: drpython Source-Version: 1:3.11.4-1.1 We believe that the bug you reported is fixed in the latest version of drpython, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 758...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts o...@survex.com (supplier of updated drpython package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 21 Sep 2014 11:46:02 + Source: drpython Binary: drpython Architecture: source all Version: 1:3.11.4-1.1 Distribution: unstable Urgency: medium Maintainer: William Vera bi...@billy.com.mx Changed-By: Olly Betts o...@survex.com Description: drpython - simple and customizable editor for the Python language Closes: 758954 Changes: drpython (1:3.11.4-1.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release: - Update and refresh patches. - Drop patch FileDialog, incorporated upstream. - Needs --buildsystem=python_distutils passing to dh because there's now a 'Makefile' in the top level of the source tree. - Needs
Bug#764260: marked as done (mlbviewer: FTBFS: dh_auto_clean: failed to run pyversions)
Your message dated Tue, 07 Oct 2014 07:34:27 + with message-id e1xbphv-0006lg...@franck.debian.org and subject line Bug#764260: fixed in mlbviewer 2014.sf.3-2 has caused the Debian Bug report #764260, regarding mlbviewer: FTBFS: dh_auto_clean: failed to run pyversions 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.) -- 764260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mlbviewer Version: 2014.sf.3-1 Severity: serious Justification: fails to build from source Builds of mlbviewer in minimal environments (such as on the autobuilders) have been failing: Can't exec pyversions: No such file or directory at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 120. dh_auto_clean: failed to run pyversions make: *** [clean] Error 2 debian/rules:8: recipe for target 'clean' failed Please declare a build dependency on python and confirm with pbuilder or the like that you haven't missed anything else. AFAICT, it should moreover be safe to switch the binary package's architecture from any to all, which would also reduce the practical impact of this bug. Could you please review both settings? Thanks! ---End Message--- ---BeginMessage--- Source: mlbviewer Source-Version: 2014.sf.3-2 We believe that the bug you reported is fixed in the latest version of mlbviewer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 764...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Delafond s...@debian.org (supplier of updated mlbviewer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Oct 2014 09:15:33 +0200 Source: mlbviewer Binary: mlbviewer Architecture: source all Version: 2014.sf.3-2 Distribution: unstable Urgency: medium Maintainer: Sebastien Delafond s...@debian.org Changed-By: Sebastien Delafond s...@debian.org Description: mlbviewer - Curses interface to the MLB.TV media offering Closes: 764260 Changes: mlbviewer (2014.sf.3-2) unstable; urgency=medium . * Build-depend on python to fix FTBFS (Closes: #764260) * Switch arch from any to all Checksums-Sha1: e5970170c2fe138b3bfb6e73d7ee56b29b166a75 1248 mlbviewer_2014.sf.3-2.dsc b79223c5da02da6f836b1dcbd35a5ee8f169af27 1928 mlbviewer_2014.sf.3-2.debian.tar.xz 26346868db3c3be6d4e175258e886f63fb2a98c7 81970 mlbviewer_2014.sf.3-2_all.deb Checksums-Sha256: 3d17e1b1008ab0c7889c6edb0579c770effa6bdbcaea1866ad1136cd92720d74 1248 mlbviewer_2014.sf.3-2.dsc 3d82b5a05cc4db281be307e321d88d0947c280b4d2b260ddb31d6ed6cf78a977 1928 mlbviewer_2014.sf.3-2.debian.tar.xz 14eec2fbffaf527ea1d537b77e18fd8fb084e1978aecda90f308ba3aa16bc167 81970 mlbviewer_2014.sf.3-2_all.deb Files: 841a7da7db665e78ee79a719bb6d2df2 81970 python optional mlbviewer_2014.sf.3-2_all.deb bc2fbaf270877615a5147a13fc76b370 1248 python optional mlbviewer_2014.sf.3-2.dsc 7e895b2324f1cbd6f8655c66a32d08ab 1928 python optional mlbviewer_2014.sf.3-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlQzk2YACgkQiZgNKcDdyD+EqgCgsoeatKtuCBLRkmvHpLWXvGsX MpUAoK2GPN9iFniisk42aI2K4r9Ho0nr =vsSR -END PGP SIGNATUREEnd Message---
Bug#761356: marked as done (openjpeg-tools and libopenjp2-tools: error when trying to install together)
Your message dated Tue, 7 Oct 2014 09:43:04 +0200 with message-id CA+7wUszEYxt9QBuSbynGrTOrVfW5CZzQqbgY28U=ky5dgmu...@mail.gmail.com and subject line has caused the Debian Bug report #761356, regarding openjpeg-tools and libopenjp2-tools: 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.) -- 761356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libopenjp2-tools,openjpeg-tools Version: libopenjp2-tools/2.1.0-1 Version: openjpeg-tools/2.0.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-09-13 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: Selecting previously unselected package libjpeg8:amd64. (Reading database ... 10869 files and directories currently installed.) Preparing to unpack .../libjpeg8_8d1-1_amd64.deb ... Unpacking libjpeg8:amd64 (8d1-1) ... Selecting previously unselected package liblcms2-2:amd64. Preparing to unpack .../liblcms2-2_2.6-3_amd64.deb ... Unpacking liblcms2-2:amd64 (2.6-3) ... Selecting previously unselected package libpng12-0:amd64. Preparing to unpack .../libpng12-0_1.2.50-2_amd64.deb ... Unpacking libpng12-0:amd64 (1.2.50-2) ... Selecting previously unselected package libjbig0:amd64. Preparing to unpack .../libjbig0_2.1-3_amd64.deb ... Unpacking libjbig0:amd64 (2.1-3) ... Selecting previously unselected package libtiff5:amd64. Preparing to unpack .../libtiff5_4.0.3-10_amd64.deb ... Unpacking libtiff5:amd64 (4.0.3-10) ... Selecting previously unselected package libopenjp2-7:amd64. Preparing to unpack .../libopenjp2-7_2.1.0-1_amd64.deb ... Unpacking libopenjp2-7:amd64 (2.1.0-1) ... Selecting previously unselected package libopenjpeg6:amd64. Preparing to unpack .../libopenjpeg6_2.0.0-1_amd64.deb ... Unpacking libopenjpeg6:amd64 (2.0.0-1) ... Selecting previously unselected package libopenjp2-tools. Preparing to unpack .../libopenjp2-tools_2.1.0-1_amd64.deb ... Unpacking libopenjp2-tools (2.1.0-1) ... Selecting previously unselected package openjpeg-tools. Preparing to unpack .../openjpeg-tools_2.0.0-1_amd64.deb ... Unpacking openjpeg-tools (2.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/openjpeg-tools_2.0.0-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/opj_decompress.1.gz', which is also in package libopenjp2-tools 2.1.0-1 Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: /var/cache/apt/archives/openjpeg-tools_2.0.0-1_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/bin/opj_compress /usr/bin/opj_decompress /usr/bin/opj_dump /usr/share/man/man1/opj_compress.1.gz /usr/share/man/man1/opj_decompress.1.gz /usr/share/man/man1/opj_dump.1.gz This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -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--- I believe this is time to fix this one now. Bug was in openjpeg-tools/2.0.0-1 only, it was neither in 1:1.5.2-3 nor in src:openjpeg2/2.1.0-1.---End Message---
Processed: your mail
Processing commands for cont...@bugs.debian.org: fixed 761356 1:1.5.2-3 Bug #761356 [openjpeg-tools] openjpeg-tools and libopenjp2-tools: error when trying to install together Marked as fixed in versions openjpeg/1:1.5.2-3. End of message, stopping processing here. Please contact me if you need assistance. -- 761356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761356 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#764162: linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network
On Mon, 2014-10-06 at 01:21 +0200, Svenska wrote: Package: src:linux Version: 3.16.3-2 Severity: serious Justification: may cause silent data corruption Hello, after upgrading the kernel of my NAS to 3.16-2-kirkwood, I noticed corrupt data on my files. The NAS works as a DHCP client on its single LAN port, the two hard drives run in a RAID1 configuration. Both drives are fine according to mdadm and smartctl. Kernel logs in both cases have not been eye-catching. Samba is configured with unix charset = ISO-8859-1. When copying data from the NAS to some other device using CIFS or Samba (the other devices run jessie/amd64 or wheezy/i686), the files are partly corrupt. The reported md5 checksums of files change every time the files are read. (And they differ from the checksums as stored on disk as well.) The files are not completely destroyed: ZIP archives show CRC errors only for some files in them, and video files remain generally playable, with lots of audio/video errors and crashing players. Shell access using SSH generally works. Trying to copy files with scp or sftp breaks the connection (invalid MAC packets or similar). File listing and mounting with sshfs work. Trying to copy files via sshfs results in a Socket not connected error, and the mount point is gone. As far as I can see, the on-disk data seems to be fine, as do files copied to the NAS while running the corrupt kernel. I am unable to check all new files, though - there might have been silent data corruption on new files. It's sounding like the issue might be corruption on the networking path rather than the disk path then? Data corruption on NAS devices is a serious issue for me. Reverting back to 3.14-2-kirkwood fixed the problems. Which exact version did you revert to? Looking at debian/changelog since the first 3.14 version I don't see much specific to kirkwood. At some point there were some changes with the network PHY but they predate 3.14 IIRC. The only thing which jumps out is [armel/kirkwood] mm: Enable HIGHMEM (Closes: #760786) in 3.16.2-1. If you were able to try 3.16-1~exp1[0] from snapshot.debian.org that might help rule that out. If 3.16-1~exp1 still has the issue then I think we are looking at an upstream regression. It might be worth bisecting a bit over the old kernels from experimental which can be found on snapshot.d.o e.g. to narrow down if the issue appeared in 3.15 or 3.16. After that please could you to take this up with the upstream developers[1], who are normally very responsive to kirkwood issues. Thanks, Ian. [0] Should be at http://snapshot.debian.org/package/linux/3.16-1~exp1/ [1] ARM/Marvell Dove/Kirkwood/MV78xx0/Orion SOC support M: Jason Cooper ja...@lakedaemon.net M: Andrew Lunn and...@lunn.ch M: Sebastian Hesselbarth sebastian.hesselba...@gmail.com L: linux-arm-ker...@lists.infradead.org (moderated for non-subscribers) S: Maintained Best Regards -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information Hardware : QNAP TS-119/TS-219 Revision : ** PCI devices: 00:00.0 Host bridge [0600]: Marvell Technology Group Ltd. Device [11ab:6282] (rev 01) Subsystem: Marvell Technology Group Ltd. Device [11ab:11ab] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 9 Region 0: Memory at ignored (64-bit, prefetchable) Capabilities: access denied 00:01.0 SATA controller [0106]: JMicron Technology Corp. JMB363 SATA/IDE Controller [197b:2363] (rev 03) (prog-if 01 [AHCI 1.0]) Subsystem: JMicron Technology Corp. JMB363 SATA/IDE Controller [197b:2363] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 9 Region 5: Memory at e001 (32-bit, non-prefetchable) [size=8K] [virtual] Expansion ROM at e000 [disabled] [size=64K] Capabilities: access denied Kernel driver in use: ahci 00:01.1 IDE interface [0101]: JMicron Technology Corp. JMB363 SATA/IDE Controller [197b:2363] (rev 03) (prog-if 85 [Master SecO PriO]) Subsystem: JMicron Technology Corp. JMB363 SATA/IDE Controller [197b:2363] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin B routed to IRQ 9 Region 0: I/O ports at 1010 [disabled] [size=8] Region 1: I/O ports at 1020
Bug#764318: libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs
Package: libjpeg-progs Version: 1:1.3.1-3 Severity: grave Justification: renders package unusable libjpeg-progs can't be upgraded: Unpacking libjpeg-progs (1:9a-2) over (1:1.3.1-3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1:1.3.1-3 Processing triggers for man-db (2.7.0.2-1) ... Errors were encountered while processing: /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libjpeg-progs depends on: ii libjpeg-turbo-progs 1:1.3.1-3 libjpeg-progs recommends no packages. libjpeg-progs suggests no packages. -- debconf-show failed -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763360: closed by Ondřej Surý ond...@sury.org
On Mon, Oct 6, 2014, at 21:14, Bill Allombert wrote: On Mon, Oct 06, 2014 at 11:54:06AM +, Debian Bug Tracking System wrote: Date: Mon, 06 Oct 2014 13:52:42 +0200 From: Ondřej Surý ond...@sury.org To: Bill Allombert ballo...@debian.org, Andreas Barth a...@ayous.org Cc: Emilio Pozuelo Monfort po...@debian.org, 763360-d...@bugs.debian.org Subject: Re: Bug#763360: libjpeg-turbo is hijacking binaries from other source packages X-Mailer: MessagingEngine.com Webmail Interface - ajax-257eafe9 Version: 1:1.3.1-4 My understanding is that this bug can be now closed as the libjpeg-progs are not built from src:libjpeg-progs and libjpeg62* binary package names has been accepted now. Excellent news! When do you plan to upload a version libjpeg-turbo that does not hijack libjpeg62 anymore ? JFTR I will list the consequences of any renaming that would happen: 1. libjpeg-turbo62 (as an example) would still contain shared library libjpeg.so.62, thus it needs to Conflicts/Provides: libjpeg62, same applies for the libjpeg62-dev package vs libjpeg-turbo62-dev (Conflicts/Provides: libjpeg62-dev) 2. Thus libjpeg62 and libjpeg62-dev from src:libjpeg6b will be uninstallable because libjpeg-turbo62 is a default JPEG library in Debian and therefore it will be almost always present in the system where JPEG library is needed. Well, even my stripped down KVM server box has libjpeg library since qemu-kvm depends on it[1]. Installation of libjpeg62 from src:libjpeg6b will be possible only in a very specialized scenarios where the system is stripped down to a bare minimum. 3. yet another transition will be started and buildd cycles spent Ondrej -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764318: libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs
Control: notfound -1 1:1.3.1-3 Control: found -1 1:9a-2 On 2014-10-07 10:11:30 +0200, Vincent Lefevre wrote: Unpacking libjpeg-progs (1:9a-2) over (1:1.3.1-3) ... [...] -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs
Processing control commands: notfound -1 1:1.3.1-3 Bug #764318 [libjpeg-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs No longer marked as found in versions libjpeg-turbo/1:1.3.1-3. found -1 1:9a-2 Bug #764318 [libjpeg-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Marked as found in versions libjpeg9/1:9a-2. -- 764318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764318 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#764318: libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs
Control: clone -1 -2 Control: reassign -2 libjpeg-turbo-progs Control: found -2 1:1.3.1-3 Vincent, in fact the libjpeg-turbo-progs also had incorrect Breaks: libjpeg-progs instead of proper Conflicts: libjpeg-progs, so the bug is also present in the libjpeg-turbo-progs. Cheers, Ondrej On Tue, Oct 7, 2014, at 10:32, Vincent Lefevre wrote: Control: notfound -1 1:1.3.1-3 Control: found -1 1:9a-2 On 2014-10-07 10:11:30 +0200, Vincent Lefevre wrote: Unpacking libjpeg-progs (1:9a-2) over (1:1.3.1-3) ... [...] -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#764318: libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs
Processing control commands: clone -1 -2 Bug #764318 [libjpeg-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Bug 764318 cloned as bug 764322 reassign -2 libjpeg-turbo-progs Bug #764322 [libjpeg-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Bug reassigned from package 'libjpeg-progs' to 'libjpeg-turbo-progs'. No longer marked as found in versions libjpeg9/1:9a-2. Ignoring request to alter fixed versions of bug #764322 to the same values previously set found -2 1:1.3.1-3 Bug #764322 [libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Marked as found in versions libjpeg-turbo/1:1.3.1-3. -- 764318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764318 764322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764322 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#746013: Investigating i386 issues with libmatheval
On Mon, 06 Oct 2014 23:41:16 +0200 Julian Taylor jtaylor.deb...@googlemail.com wrote: On 06.10.2014 23:34, Neil Williams wrote: Something odd with the *386 builds, i386, kfreebsd-i386 and hurd-i386: i386 chroot: -1.3130352854993315 +1.3130352854993312 Other 32bit architectures don't have a problem. thats very expected, i386 numerical precision depends on compiler optimizations as the fpu has 80 bit width while double has 64. You need to bump the error bounds or use special flags like -ffloat-store or -fpmath=sse to avoid it. OK, thanks. We're going to tweak the patch to use deterministic precision, based on the highest precision available on all current architectures. -- Neil Williams = http://www.linux.codehelp.co.uk/ signature.asc Description: PGP signature
Bug#760846: Upstream's got a patch
Upstream has got a patch: https://github.com/zmanda/amanda/commit/e810e1945909b5a55c3688d0b996a91f526ae1c6 It worked in my case. -- Michał Pokrywka -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: pyserial: diff for NMU version 2.6-1.1
Processing control commands: tags 759074 + pending Bug #759074 [src:pyserial] python-serial: Please update to use wxpython3.0 Added tag(s) pending. -- 759074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759074 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#759074: pyserial: diff for NMU version 2.6-1.1
Control: tags 759074 + pending
Dear maintainer,
I've prepared an NMU for pyserial (versioned as 2.6-1.1) and
uploaded it. This is the same diff I attached before, but
with the changelog entry date touched and the package rebuilt
with current unstable.
Cheers,
Olly
diff -u pyserial-2.6/debian/control pyserial-2.6/debian/control
--- pyserial-2.6/debian/control
+++ pyserial-2.6/debian/control
@@ -11,7 +11,7 @@
Package: python-serial
Architecture: all
Depends: ${python:Depends}, ${misc:Depends}
-Suggests: python-wxgtk2.8 | python-wxgtk
+Suggests: python-wxgtk3.0 | python-wxgtk
XB-Python-Version: ${python:Versions}
Description: pyserial - module encapsulating access for the serial port
This module encapsulates the access for the serial port. It provides
@@ -22,7 +22,7 @@
Package: python3-serial
Architecture: all
Depends: ${python3:Depends}, ${misc:Depends}
-Suggests: python3-wxgtk2.8 | python3-wxgtk
+Suggests: python3-wxgtk3.0 | python3-wxgtk
XB-Python-Version: ${python3:Versions}
Description: pyserial - module encapsulating access for the serial port
This module encapsulates the access for the serial port. It provides
diff -u pyserial-2.6/debian/changelog pyserial-2.6/debian/changelog
--- pyserial-2.6/debian/changelog
+++ pyserial-2.6/debian/changelog
@@ -1,3 +1,14 @@
+pyserial (2.6-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Update for wxPython 3.0, Closes: #759074:
+- debian/control: Update dependencies.
+- examples/wxSerialConfigDialog.py,examples/wxTerminal.py: Drop calls to
+ wx.InitAllImageHandlers() which is a no-op for 2.8 and gives a
+ deprecation warning with 3.0. Update deprecated wx.SAVE to wx.FD_SAVE.
+
+ -- Olly Betts o...@survex.com Tue, 07 Oct 2014 09:02:39 +
+
pyserial (2.6-1) unstable; urgency=low
* New upstream version. Closes: #664788.
only in patch2:
unchanged:
--- pyserial-2.6.orig/examples/wxSerialConfigDialog.py
+++ pyserial-2.6/examples/wxSerialConfigDialog.py
@@ -229,8 +229,6 @@
class MyApp(wx.App):
Test code
def OnInit(self):
-wx.InitAllImageHandlers()
-
ser = serial.Serial()
print ser
#loop until cancel is pressed, old values are used as start for the next run
only in patch2:
unchanged:
--- pyserial-2.6.orig/examples/wxTerminal.py
+++ pyserial-2.6/examples/wxTerminal.py
@@ -202,7 +202,7 @@
def OnSaveAs(self, event):
Save contents of output window.
filename = None
-dlg = wx.FileDialog(None, Save Text As..., ., , Text File|*.txt|All Files|*, wx.SAVE)
+dlg = wx.FileDialog(None, Save Text As..., ., , Text File|*.txt|All Files|*, wx.FD_SAVE)
if dlg.ShowModal() == wx.ID_OK:
filename = dlg.GetPath()
dlg.Destroy()
@@ -320,7 +320,6 @@
class MyApp(wx.App):
def OnInit(self):
-wx.InitAllImageHandlers()
frame_terminal = TerminalFrame(None, -1, )
self.SetTopWindow(frame_terminal)
frame_terminal.Show(1)
Bug#750275: marked as done (model-builder: FTBFS: chmod: cannot access '/«PKGBUILDDIR»/debian/model-builder//usr/share/pyshared/model_builder//Examples/*': No such file or directory)
Your message dated Tue, 07 Oct 2014 09:21:51 + with message-id e1xbqxr-0003sw...@franck.debian.org and subject line Bug#750275: fixed in model-builder 0.4.1-6.2 has caused the Debian Bug report #750275, regarding model-builder: FTBFS: chmod: cannot access '/«PKGBUILDDIR»/debian/model-builder//usr/share/pyshared/model_builder//Examples/*': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 750275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: model-builder Version: 0.4.1-6.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140601 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules binary pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions pyversions: missing debian/pyversions file, fall back to supported versions test -x debian/rules dh_testroot dh_prep dh_installdirs -A if [ -e model_builder/Docs/Quick-start.pdf ]; then \ echo Quick-start.pdf shouldn't be part of the tarball because of licensing issues!; \ exit 1; \ fi mkdir -p . mkdir -p debian/python-module-stampdir cd . \ python setup.py build \ --build-base=/«PKGBUILDDIR»/./build running build running build_py running egg_info writing Model_Builder.egg-info/PKG-INFO writing top-level names to Model_Builder.egg-info/top_level.txt writing dependency_links to Model_Builder.egg-info/dependency_links.txt writing entry points to Model_Builder.egg-info/entry_points.txt reading manifest file 'Model_Builder.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'model_builder/Docs/*.pdf' writing manifest file 'Model_Builder.egg-info/SOURCES.txt' touch debian/python-module-stampdir/model-builder Adding cdbs dependencies to debian/model-builder.substvars dh_installdirs -pmodel-builder cd . \ python setup.py install \ --root=/«PKGBUILDDIR»/debian/model-builder/ \ --install-purelib=/usr/lib/python2.7/site-packages/ \ --prefix=/usr --no-compile -O0 --install-layout=deb running install running build running build_py running egg_info writing Model_Builder.egg-info/PKG-INFO writing top-level names to Model_Builder.egg-info/top_level.txt writing dependency_links to Model_Builder.egg-info/dependency_links.txt writing entry points to Model_Builder.egg-info/entry_points.txt reading manifest file 'Model_Builder.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'model_builder/Docs/*.pdf' writing manifest file 'Model_Builder.egg-info/SOURCES.txt' running install_lib creating /«PKGBUILDDIR»/debian/model-builder/usr creating /«PKGBUILDDIR»/debian/model-builder/usr/lib creating /«PKGBUILDDIR»/debian/model-builder/usr/lib/python2.7 creating /«PKGBUILDDIR»/debian/model-builder/usr/lib/python2.7/site-packages creating /«PKGBUILDDIR»/debian/model-builder/usr/lib/python2.7/site-packages/model_builder creating /«PKGBUILDDIR»/debian/model-builder/usr/lib/python2.7/site-packages/model_builder/Examples copying build/lib.linux-x86_64-2.7/model_builder/Examples/verhulst.ode - /«PKGBUILDDIR»/debian/model-builder/usr/lib/python2.7/site-packages/model_builder/Examples copying build/lib.linux-x86_64-2.7/model_builder/Examples/sprucebudworm.ode - /«PKGBUILDDIR»/debian/model-builder/usr/lib/python2.7/site-packages/model_builder/Examples copying build/lib.linux-x86_64-2.7/model_builder/Examples/sirdemog.ode - /«PKGBUILDDIR»/debian/model-builder/usr/lib/python2.7/site-packages/model_builder/Examples copying build/lib.linux-x86_64-2.7/model_builder/Examples/sir_unc.spec - /«PKGBUILDDIR»/debian/model-builder/usr/lib/python2.7/site-packages/model_builder/Examples copying build/lib.linux-x86_64-2.7/model_builder/Examples/sir.ode - /«PKGBUILDDIR»/debian/model-builder/usr/lib/python2.7/site-packages/model_builder/Examples copying build/lib.linux-x86_64-2.7/model_builder/Examples/pk.ode - /«PKGBUILDDIR»/debian/model-builder/usr/lib/python2.7/site-packages/model_builder/Examples copying build/lib.linux-x86_64-2.7/model_builder/Examples/nagumo.ode - /«PKGBUILDDIR»/debian/model-builder/usr/lib/python2.7/site-packages/model_builder/Examples copying build/lib.linux-x86_64-2.7/model_builder/Examples/lotka-volterra2_unc.spec -
Bug#759066: marked as done (model-builder: Please update to use wxpython3.0)
Your message dated Tue, 07 Oct 2014 09:21:51 + with message-id e1xbqxr-0003se...@franck.debian.org and subject line Bug#759066: fixed in model-builder 0.4.1-6.2 has caused the Debian Bug report #759066, regarding model-builder: Please update to use wxpython3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 759066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: model-builder Version: 0.4.1-6.1 Severity: important Tags: sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wxpy3.0 Control: block 755757 by -1 We're aiming to migrate the archive to using wxpython3.0 instead of wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released. This transition is already underway, and is being tracked by the release team here: https://release.debian.org/transitions/html/wxpython3.0.html The wxPython 3.0 API mostly adds to the wxPython2.8 API. Many packages work with wxPython 3.0 without any changes, but there are a few incompatibilities. For example, wx.Color is no longer supported as an alias for wx.Colour, and some constants which were deprecated in 2.8 have been removed. All the removed constants I'm aware of were set to 0 in wxPython 2.8, so removing them is still compatible with 2.8. To assist updating to wxPython 3.0, I've put together a script which will help make the mechanical changes required. This is in a git repo on collab-maint along with a README about using it and updating packages for wxPython 3.0 in general: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git The script has some options to control the sorts of changes it makes - see the README and --help output for more information - you can view the latest version of the README online here: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I've developed this script by trying to convert 20+ packages. Please try it out on your package - in many cases, it should be enough to get your package working (if it doesn't already) - if it does, please upload (and close this bug). If the script doesn't do the job, please let me know (or improve the script if you can figure out what it needs to do to get your package working). Another issue you may hit is that wxWidgets 3.0 now defaults to enabling its WXDEBUG checks for incorrect API usage, so some applications will emit scary sounding assertion failures. These are unlikely to actually be new, just in a default build of 2.8, such incorrect uses were handled quietly behind the scenes. Sometimes these are easy to fix, but if not you can easily patch the application to tell wx 3.0 to handle them in the same way wx 2.8 does - details of how to do so are in the README: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I'm happy to sponsor uploads for this transition, though if you have an active sponsor already check with them first - I don't want to tread on anyone's toes. Cheers, Olly ---End Message--- ---BeginMessage--- Source: model-builder Source-Version: 0.4.1-6.2 We believe that the bug you reported is fixed in the latest version of model-builder, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts o...@survex.com (supplier of updated model-builder package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Oct 2014 08:11:43 + Source: model-builder Binary: model-builder Architecture: source all Version: 0.4.1-6.2 Distribution: unstable Urgency: medium Maintainer: Varun Hiremath va...@debian.org Changed-By: Olly Betts o...@survex.com Description: model-builder - graphical ODE simulator Closes: 750275 759066 Changes: model-builder (0.4.1-6.2) unstable; urgency=medium . * Non-maintainer upload with maintainer's permission. * Fix FTBFS due to python helper changes. (Closes: #750275) * Update for wxPython 3.0 (Closes: #759066): - New patch: wxpython3.0.patch Checksums-Sha1: 01946dcd2ea26f0cef8de6459ffa5d3b4cb71feb 1963
Bug#764005: targetcli: Upgrade issues from 2.1-1
Control: severity -1 important @Chris: Are you okay if I downgrade this? With severity grave it will be a candidate for removal. I understand the data loss situation during upgrades, but for users deploying it fresh, it is a non-issue. Please reset to grave if you disagree. My intent is to have LIO target for Jessie, available. On Sunday 05 October 2014 02:00 PM, Jerome Martin wrote: On 10/05/2014 09:37 AM, Ritesh Raj Sarraf wrote: Thanks for the bug report. Jerome: How can we ensure to have the old 2.x settings / targets in 3.x ? Manually, this is easy. But to automate package upgrade is bit of a brain-twister. I haven't found yet a good way to do it. Basically, the config format is completely different, so we need to start the new initscript and save the config (in the new version) while the target is running. But removing the previous package actually stops it... Is this save functionality available and ready to test, in the new 3.x series that in now in the archive ? Sorry, I ask this because I don't have the resources to test these myself. If that functionality is in, then yes, we could fix it the way you and Chris have proposed. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention.
Bug#764322: marked as done (libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs)
Your message dated Tue, 07 Oct 2014 09:21:29 + with message-id e1xbqxv-0003dl...@franck.debian.org and subject line Bug#764322: fixed in libjpeg-turbo 1:1.3.1-6 has caused the Debian Bug report #764322, regarding libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs 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.) -- 764322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libjpeg-progs Version: 1:1.3.1-3 Severity: grave Justification: renders package unusable libjpeg-progs can't be upgraded: Unpacking libjpeg-progs (1:9a-2) over (1:1.3.1-3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1:1.3.1-3 Processing triggers for man-db (2.7.0.2-1) ... Errors were encountered while processing: /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libjpeg-progs depends on: ii libjpeg-turbo-progs 1:1.3.1-3 libjpeg-progs recommends no packages. libjpeg-progs suggests no packages. -- debconf-show failed -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) ---End Message--- ---BeginMessage--- Source: libjpeg-turbo Source-Version: 1:1.3.1-6 We believe that the bug you reported is fixed in the latest version of libjpeg-turbo, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 764...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý ond...@debian.org (supplier of updated libjpeg-turbo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 07 Oct 2014 10:03:41 +0200 Source: libjpeg-turbo Binary: libjpeg-dev libjpeg62-dev libjpeg62 libjpeg62-dbg libturbojpeg1 libturbojpeg1-dbg libturbojpeg1-dev libjpeg-turbo-progs libjpeg-turbo-progs-dbg Architecture: source all Version: 1:1.3.1-6 Distribution: unstable Urgency: medium Maintainer: Debian TigerVNC Packaging Team pkg-tigervnc-de...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: libjpeg-dev - Development files for the JPEG library [dummy package] libjpeg-turbo-progs - Programs for manipulating JPEG files libjpeg-turbo-progs-dbg - Programs for manipulating JPEG files (debugging symbols) libjpeg62 - libjpeg-turbo JPEG runtime library libjpeg62-dbg - Debugging symbols for the libjpeg-turbo JPEG library libjpeg62-dev - Development files for the libjpeg-turbo JPEG library libturbojpeg1 - TurboJPEG runtime library - SIMD optimized libturbojpeg1-dbg - TurboJPEG runtime library - SIMD optimized (debugging symbols) libturbojpeg1-dev - Development files for the TurboJPEG library Closes: 764322 Changes: libjpeg-turbo (1:1.3.1-6) unstable; urgency=medium . * Changes Breaks: libjpeg-progs to Conflicts: libjpeg-progs and drop Replaces: libjpeg-progs (Closes: #764322) Checksums-Sha1: 8b5d3caa742ba6e4deae82d05e9fd74646217704 2783 libjpeg-turbo_1.3.1-6.dsc e6dc4daaad627d086ce78d94f6e153e90379289e 77252 libjpeg-turbo_1.3.1-6.debian.tar.xz 202a5511e92effe2b2c574e5435c6c43f7a03f47 48482 libjpeg-dev_1.3.1-6_all.deb Checksums-Sha256: 8c9a705513345c36023ad2972e2f79a2f935fc5082bf1fdd1277694b9d017ee4 2783 libjpeg-turbo_1.3.1-6.dsc 052cd05819be1b2dd5e691d0f1a3de01ee6ba463122ba5fd606a52edec5c4242 77252 libjpeg-turbo_1.3.1-6.debian.tar.xz 96bbdffcf1e76b382a99c1f24a64c39266d30c1123dc095e46ec41f2ccfe672a 48482 libjpeg-dev_1.3.1-6_all.deb Files: 6344c2b69ab0f20aac72e089dc315e3c 2783 graphics optional
Bug#759074: marked as done (python-serial: Please update to use wxpython3.0)
Your message dated Tue, 07 Oct 2014 09:23:53 + with message-id e1xbqzp-0005pp...@franck.debian.org and subject line Bug#759074: fixed in pyserial 2.6-1.1 has caused the Debian Bug report #759074, regarding python-serial: Please update to use wxpython3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 759074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-serial Version: 2.6-1 Severity: important Tags: sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wxpy3.0 Control: block 755757 by -1 We're aiming to migrate the archive to using wxpython3.0 instead of wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released. This transition is already underway, and is being tracked by the release team here: https://release.debian.org/transitions/html/wxpython3.0.html The wxPython 3.0 API mostly adds to the wxPython2.8 API. Many packages work with wxPython 3.0 without any changes, but there are a few incompatibilities. For example, wx.Color is no longer supported as an alias for wx.Colour, and some constants which were deprecated in 2.8 have been removed. All the removed constants I'm aware of were set to 0 in wxPython 2.8, so removing them is still compatible with 2.8. To assist updating to wxPython 3.0, I've put together a script which will help make the mechanical changes required. This is in a git repo on collab-maint along with a README about using it and updating packages for wxPython 3.0 in general: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git The script has some options to control the sorts of changes it makes - see the README and --help output for more information - you can view the latest version of the README online here: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I've developed this script by trying to convert 20+ packages. Please try it out on your package - in many cases, it should be enough to get your package working (if it doesn't already) - if it does, please upload (and close this bug). If the script doesn't do the job, please let me know (or improve the script if you can figure out what it needs to do to get your package working). Another issue you may hit is that wxWidgets 3.0 now defaults to enabling its WXDEBUG checks for incorrect API usage, so some applications will emit scary sounding assertion failures. These are unlikely to actually be new, just in a default build of 2.8, such incorrect uses were handled quietly behind the scenes. Sometimes these are easy to fix, but if not you can easily patch the application to tell wx 3.0 to handle them in the same way wx 2.8 does - details of how to do so are in the README: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I'm happy to sponsor uploads for this transition, though if you have an active sponsor already check with them first - I don't want to tread on anyone's toes. Cheers, Olly ---End Message--- ---BeginMessage--- Source: pyserial Source-Version: 2.6-1.1 We believe that the bug you reported is fixed in the latest version of pyserial, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts o...@survex.com (supplier of updated pyserial package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Oct 2014 09:02:39 + Source: pyserial Binary: python-serial python3-serial Architecture: source all Version: 2.6-1.1 Distribution: unstable Urgency: medium Maintainer: Matthias Klose d...@debian.org Changed-By: Olly Betts o...@survex.com Description: python-serial - pyserial - module encapsulating access for the serial port python3-serial - pyserial - module encapsulating access for the serial port Closes: 759074 Changes: pyserial (2.6-1.1) unstable; urgency=medium . * Non-maintainer upload. * Update for wxPython 3.0, Closes: #759074: - debian/control: Update dependencies. - examples/wxSerialConfigDialog.py,examples/wxTerminal.py: Drop calls to
Processed: Re: Bug#764005: targetcli: Upgrade issues from 2.1-1
Processing control commands: severity -1 important Bug #764005 [targetcli] targetcli: Upgrade issues from 2.1-1 Severity set to 'important' from 'grave' -- 764005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764005 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: Re-opening for alternative fix to cover all architectures
Processing commands for cont...@bugs.debian.org:
reopen 746013
Bug #746013 {Done: Neil Williams codeh...@debian.org} [libmatheval]
libmatheval: please migrate to guile-2.0
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libmatheval/1.1.11+dfsg-1.1.
found 746013 1.1.11+dfsg-1.1
Bug #746013 [libmatheval] libmatheval: please migrate to guile-2.0
There is no source info for the package 'libmatheval' at version
'1.1.11+dfsg-1.1' with architecture ''
Unable to make a source version for version '1.1.11+dfsg-1.1'
Marked as found in versions 1.1.11+dfsg-1.1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
746013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746013
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#746013: Re-opening for alternative fix to cover all architectures
reopen 746013 found 746013 1.1.11+dfsg-1.1 thanks Looking at a change in the evaluator to ensure that a deterministic precision is used for all calls. -- Neil Williams = http://www.linux.codehelp.co.uk/ signature.asc Description: PGP signature
Bug#764327: thinfan: Startup Fails On PostInstall
Package: thinkfan Version: Thinkfan Severity: grave Justification: renders package unusable Dear Maintainer, From the applicaiton log: # journalctl -xn -- Logs begin at Mon 2014-10-06 22:36:18 EDT, end at Tue 2014-10-07 05:35:40 EDT. -- Oct 07 05:35:40 Jessie systemd[1]: Starting simple and lightweight fan control program... -- Subject: Unit thinkfan.service has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit thinkfan.service has begun starting up. Oct 07 05:35:40 Jessie thinkfan[11964]: thinkfan 0.9.1 starting... Oct 07 05:35:40 Jessie thinkfan[11964]: WARNING: Using default fan control in /proc/acpi/ibm/fan. Oct 07 05:35:40 Jessie thinkfan[11964]: WARNING: Using default temperature inputs in /proc/acpi/ibm/thermal. Oct 07 05:35:40 Jessie thinkfan[11964]: WARNING: You're using simple temperature limits without correction values, and your fan will only star Oct 07 05:35:40 Jessie thinkfan[11964]: Module thinkpad_acpi doesn't seem to support fan_control Oct 07 05:35:40 Jessie thinkfan[11964]: Cleaning up and resetting fan control. Oct 07 05:35:40 Jessie systemd[1]: PID file /var/run/thinkfan.pid not readable (yet?) after start. Oct 07 05:35:40 Jessie systemd[1]: Failed to start simple and lightweight fan control program. -- Subject: Unit thinkfan.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit thinkfan.service has failed. -- -- The result is failed. Oct 07 05:35:40 Jessie systemd[1]: Unit thinkfan.service entered failed state. -- System Information: Debian Release: sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.16-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (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#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist
Package: initramfs-tools Version: 0.118 Followup-For: Bug #762984 i am hit by the same problem. as a temporary fix, i added the 'vgchange -ay' to /usr/share/initramfs-tools/scripts/local-top/lvm2 as adding it to /etc/initramfs-tools/scripts/local-top/vgscan somehow did not work (most likely due wrong order of execution, but i did not investigate further) -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 17M Oct 7 11:49 /boot/initrd.img-3.16-2-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.16-2-amd64 root=/dev/mapper/--vg-root ro quiet acpi_backlight=vendor pcie_aspm=force -- resume RESUME=/dev/mapper/--vg-swap_1 -- /proc/filesystems btrfs ext3 ext2 ext4 fuseblk -- lsmod Module Size Used by ctr12927 1 ccm17577 1 bnep 17431 2 binfmt_misc16949 1 pci_stub 12429 1 vboxpci23077 0 vboxnetadp 25443 0 vboxnetflt 23324 0 vboxdrv 340020 3 vboxnetadp,vboxnetflt,vboxpci nfsd 263053 2 auth_rpcgss51240 1 nfsd oid_registry 12419 1 auth_rpcgss nfs_acl12511 1 nfsd nfs 187961 0 lockd 83417 2 nfs,nfsd fscache45542 1 nfs sunrpc237445 6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl ecb12737 1 btusb 29721 0 uvcvideo 79005 0 bluetooth 374429 21 bnep,btusb videobuf2_vmalloc 12816 1 uvcvideo videobuf2_memops 12519 1 videobuf2_vmalloc videobuf2_core 47787 1 uvcvideo 6lowpan_iphc 16588 1 bluetooth v4l2_common12995 1 videobuf2_core videodev 126451 3 uvcvideo,v4l2_common,videobuf2_core media 18305 2 uvcvideo,videodev acpi_call 12552 0 x86_pkg_temp_thermal12951 0 intel_powerclamp 17159 0 joydev 17063 0 intel_rapl 17356 0 iTCO_wdt 12831 0 coretemp 12820 0 iTCO_vendor_support12649 1 iTCO_wdt kvm_intel 139077 0 kvm 388597 1 kvm_intel crc32_pclmul 12915 0 ghash_clmulni_intel12978 0 aesni_intel 151423 3 arc4 12536 2 aes_x86_64 16719 1 aesni_intel iwldvm135156 0 lrw12757 1 aesni_intel mac80211 474202 1 iwldvm gf128mul 12970 1 lrw glue_helper12695 1 aesni_intel ablk_helper12572 1 aesni_intel snd_hda_codec_hdmi 45118 1 iwlwifi92451 1 iwldvm cfg80211 405538 3 iwlwifi,mac80211,iwldvm cryptd 14516 3 ghash_clmulni_intel,aesni_intel,ablk_helper i915 836937 2 thinkpad_acpi 69119 1 drm_kms_helper 49210 1 i915 drm 249955 4 i915,drm_kms_helper snd_hda_codec_realtek63031 1 evdev 17445 5 psmouse98616 0 serio_raw 12849 0 pcspkr 12595 0 ac 12715 0 i2c_algo_bit 12751 1 i915 tpm_tis17182 0 nvram 13034 1 thinkpad_acpi snd_hda_codec_generic63107 1 snd_hda_codec_realtek i2c_i801 16965 0 mei_me 17941 0 tpm31511 1 tpm_tis i2c_core 46012 7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev wmi17339 0 mei74977 1 mei_me lpc_ich20768 0 snd_hda_intel 26327 0 snd_hda_controller 26727 1 snd_hda_intel snd_hda_codec 104463 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller snd_hwdep 13148 1 snd_hda_codec snd_pcm88662 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller snd_timer 26614 1 snd_pcm snd65244 9 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,thinkpad_acpi shpchp 31121 0 mfd_core 12601 1 lpc_ich battery13356 0 rfkill 18867 5 cfg80211,thinkpad_acpi,bluetooth button 12944 1 i915 video 18030 1 i915 soundcore 13026 2 snd,snd_hda_codec processor 28221 0 loop 26605 0 fuse 83350 1 parport_pc 26300 0 ppdev 16782 0 lp 17074 0 parport35749 3 lp,ppdev,parport_pc autofs435529 2 ext4 469572 6 crc16 12343 2 ext4,bluetooth mbcache17171 1 ext4 jbd2
Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist
On 10/07/2014 11:59 AM, IOhannes m zmoelnig wrote: i am hit by the same problem. as a temporary fix, i added the 'vgchange -ay' to /usr/share/initramfs-tools/scripts/local-top/lvm2 as adding it to /etc/initramfs-tools/scripts/local-top/vgscan somehow did not work (most likely due wrong order of execution, but i did not investigate further) i turned out that i had forgotten to set +x permissions for /etc/initramfs-tools/scripts/local-top/vgscan gfmrdsa IOhannes signature.asc Description: OpenPGP digital signature
Processed: found in original too
Processing commands for cont...@bugs.debian.org: found 746013 1.1.11+dfsg-1 Bug #746013 [libmatheval] libmatheval: please migrate to guile-2.0 There is no source info for the package 'libmatheval' at version '1.1.11+dfsg-1' with architecture '' Unable to make a source version for version '1.1.11+dfsg-1' Marked as found in versions 1.1.11+dfsg-1. thanks Stopping processing here. Please contact me if you need assistance. -- 746013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746013 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#758948: marked as done (pykaraoke: Please update to use wxpython3.0)
Your message dated Tue, 07 Oct 2014 10:19:19 + with message-id e1xbrrt-0001ha...@franck.debian.org and subject line Bug#758948: fixed in pykaraoke 0.7.5-1.1 has caused the Debian Bug report #758948, regarding pykaraoke: Please update to use wxpython3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 758948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: pykaraoke Version: 0.7.5-1 Severity: important Tags: sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wxpy3.0 Control: block 755757 by -1 We're aiming to migrate the archive to using wxpython3.0 instead of wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released. This transition is already underway, and is being tracked by the release team here: https://release.debian.org/transitions/html/wxpython3.0.html The wxPython 3.0 API mostly adds to the wxPython2.8 API. Many packages work with wxPython 3.0 without any changes, but there are a few incompatibilities. For example, wx.Color is no longer supported as an alias for wx.Colour, and some constants which were deprecated in 2.8 have been removed. All the removed constants I'm aware of were set to 0 in wxPython 2.8, so removing them is still compatible with 2.8. To assist updating to wxPython 3.0, I've put together a script which will help make the mechanical changes required. This is in a git repo on collab-maint along with a README about using it and updating packages for wxPython 3.0 in general: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git The script has some options to control the sorts of changes it makes - see the README and --help output for more information - you can view the latest version of the README online here: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I've developed this script by trying to convert 20+ packages. Please try it out on your package - in many cases, it should be enough to get your package working (if it doesn't already) - if it does, please upload (and close this bug). If the script doesn't do the job, please let me know (or improve the script if you can figure out what it needs to do to get your package working). Another issue you may hit is that wxWidgets 3.0 now defaults to enabling its WXDEBUG checks for incorrect API usage, so some applications will emit scary sounding assertion failures. These are unlikely to actually be new, just in a default build of 2.8, such incorrect uses were handled quietly behind the scenes. Sometimes these are easy to fix, but if not you can easily patch the application to tell wx 3.0 to handle them in the same way wx 2.8 does - details of how to do so are in the README: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I'm happy to sponsor uploads for this transition, though if you have an active sponsor already check with them first - I don't want to tread on anyone's toes. Cheers, Olly ---End Message--- ---BeginMessage--- Source: pykaraoke Source-Version: 0.7.5-1.1 We believe that the bug you reported is fixed in the latest version of pykaraoke, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 758...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts o...@survex.com (supplier of updated pykaraoke package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Oct 2014 09:42:38 + Source: pykaraoke Binary: pykaraoke pykaraoke-bin python-pykaraoke Architecture: source all Version: 0.7.5-1.1 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org Changed-By: Olly Betts o...@survex.com Description: pykaraoke - free CDG/MIDI/MPEG karaoke player pykaraoke-bin - free CDG/MIDI/MPEG karaoke player python-pykaraoke - free CDG/MIDI/MPEG karaoke player Closes: 645568 758948 Changes: pykaraoke (0.7.5-1.1) unstable; urgency=medium . * Non-maintainer upload. * Update to use wxPython 3.0 (Closes: #758948): + New patch: wxpython3.0.patch * Drop dependency on
Bug#763493: marked as done (simgear: Please change build dependency to libjpeg-dev (libjpeg-turbo transition))
Your message dated Tue, 07 Oct 2014 10:19:34 +
with message-id e1xbrri-0001qw...@franck.debian.org
and subject line Bug#763493: fixed in simgear 3.0.0-5
has caused the Debian Bug report #763493,
regarding simgear: Please change build dependency to libjpeg-dev (libjpeg-turbo
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.)
--
763493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: simgear
Version: 3.0.0-4
Severity: important
Tags: patch
User: ond...@debian.org
Usertags: libjpeg-turbo-transition
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer(s),
Debian is transitioning from IJG JPEG library (src:libjpeg8) to
libjpeg-turbo implementation (src:libjpeg-turbo)[1] of libjpeg62 API
with decode from memory buffer interface (jpeg_mem_{src,dest}).
Your package cannot be transitioned automatically as it explicitly
build depends on specific API/ABI (libjpeg8-dev) and this build
dependency needs to be changed to libjpeg-dev. In most if not all
cases this should be sufficient to build against libjpeg-turbo.
I am in process of testing each package in question to compile against
libjpeg-turbo and I will provide a suitable patch for each package
when I will succeed.
On the other hand please note that the winter^Wfreeze is coming and
if your package is not updated in due time it might be NMUed by the
release team (or by me with the full ack of release team).
That also means that if you are OK with NMU then please respond to
this bug report and I will prepare and upload the recompiled packages
for you.
Cheers,
Ondrej
1. The full Technical Committee decision can be found here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717076#235
- -- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (700, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQJ8BAEBCgBmBQJUKqrXXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHaasP/1sLKn7BxS1Hi31+pV31681l
43w2pexolcskDA8rPXZqFV56emw6sYi5UNJiikGzMu49VubkroapazKfGGJ9t0w3
qh5uQArrwpQVDVzkMN6hUbXJ7+3kB1Wi29OdZrxDirg2zitxO9ER45Ur65umIxQ6
WWpV0/izGXzvepNYtTAW/vCEKS0u/p1MX4byniTE5+/GIpnjXZ79hBJWKTsBF1lW
ut+0CvA2qqo3nFEhBbzNYrF9dnKlePfQ0k/+5XOrkuENr4wK12NNDBUSZmueJUna
GASqRku9W7FKnVDRYfzskPMz9M575m5ldfgkAtjUpyMYwzeZ0Tu5QSeABB2uFfj5
aPDYgtyQJ3ajNKBki2zRz0Heu90wSdcExgWqxj+AIzIOFvcxJC+T3Ker6fCgY/Qb
c6NisHsmIJVcBr9vVRYrC/CGZkTPv6WHlxles6a+F6Alo14MqoMcwnR4QMEJXMbS
XuSIusIFKViUB6Gg3e01Ih3vzuMc/887ve/JGbdWA9T2weGUQLbooLNmNfsEMNX+
JKo1kN+t3ubrjN/W2fKubomK8PyZwV4SNH8R6E4LgnhmUTolk5VVYzzurGT7shYs
W05bbUUgS5yZtlkl5cz4Baxd421vLLRE5OjWNa4B0aHaiXhS8Px1z6/AB9lcbUHt
rDgEAHa1mGUeC8P6DFJ6
=RfB4
-END PGP SIGNATURE-
---End Message---
---BeginMessage---
Source: simgear
Source-Version: 3.0.0-5
We believe that the bug you reported is fixed in the latest version of
simgear, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 763...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Markus Wanner mar...@bluegap.ch (supplier of updated simgear package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 07 Oct 2014 09:53:01 +0200
Source: simgear
Binary: libsimgearcore3.0.0 libsimgearcore3.0.0-dbg libsimgearscene3.0.0
libsimgearscene3.0.0-dbg libsimgear-dev simgear-dev
Architecture: source amd64 all
Version: 3.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian FlightGear Crew pkg-fgfs-c...@lists.alioth.debian.org
Changed-By: Markus Wanner mar...@bluegap.ch
Description:
libsimgear-dev - Simulator Construction Gear -- development files
libsimgearcore3.0.0 - Simulator Construction Gear -- core library
libsimgearcore3.0.0-dbg - debugging symbols for libsimgearcore
libsimgearscene3.0.0 - Simulator Construction Gear -- scene library
libsimgearscene3.0.0-dbg - debugging
Processed: jessie
Processing commands for cont...@bugs.debian.org:
tag 764287 + sid jessie
Bug #764287 [partman-zfs] GRUB before 2.02 doesn't support ZFS lz4 compression
Added tag(s) sid and jessie.
tag 764310 + sid jessie
Bug #764310 [libcerf-doc,manpages-dev] manpages-dev and libcerf-doc: error when
trying to install together
Added tag(s) sid and jessie.
tag 763476 + sid jessie
Bug #763476 [src:jpegjudge] jpegjudge: Please change build dependency to
libjpeg-dev (libjpeg-turbo transition)
Added tag(s) sid and jessie.
tag 764268 + sid jessie
Bug #764268 {Done: Ludovic Brenta ludo...@ludovic-brenta.org} [src:libaws]
libaws: build-dependency not satisfiable in sid
Added tag(s) sid and jessie.
tag 764327 + sid jessie
Bug #764327 [thinkfan] thinfan: Startup Fails On PostInstall
Added tag(s) sid and jessie.
End of message, stopping processing here.
Please contact me if you need assistance.
--
763476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763476
764268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764268
764287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764287
764310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764310
764327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764327
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#764330: libtasn1-doc_4.2-1: trying to overwrite..., which is also in package libtasn1-3-dev 2.13-2
package: libtasn1-doc version: 4.2-1 severity: serious Hi, from a test doing wheezy-jessie upgrades (running on jenkins.debian.net) I observed this: On Dienstag, 7. Oktober 2014, jenk...@jenkins.debian.net wrote: See https://jenkins.debian.net/job/chroot-installation_wheezy_install_developer_upgrade_to_jessie/480/ ... Selecting previously unselected package libtasn1-doc. Preparing to unpack .../libtasn1-doc_4.2-1_all.deb ... Unpacking libtasn1-doc (4.2-1) ... dpkg: error processing archive /var/cache/apt/archives/libtasn1-doc_4.2-1_all.deb (--unpack): trying to overwrite '/usr/share/info/libtasn1.info.gz', which is also in package libtasn1-3-dev 2.13-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) ... Errors were encountered while processing: /var/cache/apt/archives/libtasn1-doc_4.2-1_all.deb cheers, Holger signature.asc Description: This is a digitally signed message part.
Processed: Remove tags jessie and sid
Processing commands for cont...@bugs.debian.org:
tags 764268 -jessie -sid
Bug #764268 {Done: Ludovic Brenta ludo...@ludovic-brenta.org} [src:libaws]
libaws: build-dependency not satisfiable in sid
Removed tag(s) jessie.
Bug #764268 {Done: Ludovic Brenta ludo...@ludovic-brenta.org} [src:libaws]
libaws: build-dependency not satisfiable in sid
Removed tag(s) sid.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
764268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764268
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#730057: marked as done (This package should be removed)
Your message dated Tue, 07 Oct 2014 10:59:41 + with message-id e1xbsux-0004r8...@franck.debian.org and subject line Bug#764256: Removed package(s) from unstable has caused the Debian Bug report #730057, regarding This package should be removed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 730057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: freesci Severity: important freesci is more or less dead upstream and has already attracted two NMUs. The freesci code was the basis for the SCI support in ScummVM (and there were fixes on top of it). So I suggest we remove freesci in favour of ScummVM? Cheers, Moritz -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (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 ---End Message--- ---BeginMessage--- Version: 0.6.4-7.2+rm Dear submitter, as the package freesci has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/764256 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Processed (with 1 errors): [intent to NMU] Re: Bug#756243: spice-vdagent: Neither guest resizing nor clipboard sharing work
Processing control commands: found -1 + 0.15.0-1.1 Unknown command or malformed arguments to command. severity -1 serious Bug #756243 [spice-vdagent] spice-vdagent: Neither guest resizing nor clipboard sharing work Severity set to 'serious' from 'normal' tag -1 + patch Bug #756243 [spice-vdagent] spice-vdagent: Neither guest resizing nor clipboard sharing work Added tag(s) patch. -- 756243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756243 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: found 756243 in 0.15.0-1.1
Processing commands for cont...@bugs.debian.org: found 756243 0.15.0-1.1 Bug #756243 [spice-vdagent] spice-vdagent: Neither guest resizing nor clipboard sharing work Marked as found in versions spice-vdagent/0.15.0-1.1. thanks Stopping processing here. Please contact me if you need assistance. -- 756243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756243 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#764343: media-player-info: maintainer address bounces
Source: media-player-info Severity: serious Tags: sid X-Debbugs-Cc: Martin Pitt mp...@debian.org The maintainer address for media-player-info bounces, see below. (Also why does the upload to Debian have an Original-Maintainer field?) Ansgar On 10/07/2014 12:49, kubuntu-devel-ow...@lists.ubuntu.com wrote: You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at kubuntu-devel-ow...@lists.ubuntu.com. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763488: NMUs uploaded to DELAYED/5 (libjpeg-turbo transition)
Hi, to finish the libjpeg-turbo transition in time for next stable releases, the missing fixes for libjpeg8-dev to libjpeg-dev changes in build depends were built and uploaded to DELAYED/5 as NMUs. No other changes than those related to libjpeg8 to libjpeg-turbo were done in the packages. Cheers, -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763488: [Openjdk] Bug#763488: NMUs uploaded to DELAYED/5 (libjpeg-turbo transition)
Am 07.10.2014 um 14:01 schrieb Ondřej Surý: Hi, to finish the libjpeg-turbo transition in time for next stable releases, the missing fixes for libjpeg8-dev to libjpeg-dev changes in build depends were built and uploaded to DELAYED/5 as NMUs. No other changes than those related to libjpeg8 to libjpeg-turbo were done in the packages. please avoid these uploads. 6 and 8 are not part of the upcoming release, and we'll have another 7 upload soonish. thanks, Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762250: marked as done (cecilia: Please update to use wxpython3.0)
Your message dated Wed, 8 Oct 2014 01:16:31 +1300 with message-id 20141007121631.GA18342@debian and subject line Re: Bug#762250: cecilia: Patch for wxPython 3.0 has caused the Debian Bug report #762250, regarding cecilia: Please update to use wxpython3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 762250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cecilia Version: 5.0.9-1 Severity: serious Justification: blocks the on-going wxpython3.0 transition Tags: sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wxpy3.0 Control: block 755757 by -1 I missed this package in my previous checks, as while it uses the wx API, it doesn't seem to have any sort of dependency on python-wxgtk2.8 or indeed any wx package (it'd be useful for transitions, and I think also for users, to add at least a 'Suggests: python-wxgtk3.0'). Starting cecilia from unstable with python-wxgtk3.0 installed, I get the following output, and it doesn't seem to actually start up correctly: Preferences file not found. pyo version 0.7.0 (uses single precision) WxPython is not found for the current python version. Pyo will use a minimal GUI toolkit written with Tkinter. This toolkit has limited functionnalities and is no more maintained or updated. If you want to use all of pyo's GUI features, you should install WxPython, available here: http://www.wxpython.org/ ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/cecilia/Resources/splash.py, line 70, in OnPaint font.SetPixelSize((15,15)) File /usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_gdi.py, line 2313, in SetPixelSize return _gdi_.Font_SetPixelSize(*args, **kwargs) wx._core.PyAssertionError: C++ assertion IsOk() failed at ../src/gtk/font.cpp(337) in GetPointSize(): invalid font Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_misc.py, line 1367, in Notify self.notify() File /usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py, line 16866, in Notify self.result = self.callable(*self.args, **self.kwargs) File /usr/lib/python2.7/dist-packages/cecilia/Resources/splash.py, line 78, in OnClose self.callback() File /usr/bin/cecilia, line 68, in onStart ceciliaMainFrame.onOpen(os.path.join(MODULES_PATH, category, file), True) File /usr/lib/python2.7/dist-packages/cecilia/Resources/CeciliaMainFrame.py, line 236, in onOpen CeciliaLib.openCeciliaFile(self, event, builtin) File /usr/lib/python2.7/dist-packages/cecilia/Resources/CeciliaLib.py, line 584, in openCeciliaFile getVar(audioServer).openCecFile(cecFilePath) File /usr/lib/python2.7/dist-packages/cecilia/Resources/audio.py, line 1660, in openCecFile CeciliaLib.getVar(mainFrame).onUpdateInterface(None) File /usr/lib/python2.7/dist-packages/cecilia/Resources/CeciliaMainFrame.py, line 326, in onUpdateInterface ceciliaInterface = CeciliaInterface.CeciliaInterface(None, title='Interface - %s' % title, mainFrame=self) File /usr/lib/python2.7/dist-packages/cecilia/Resources/CeciliaInterface.py, line 52, in __init__ self.controlPanel = Control.CECControl(self, -1) File /usr/lib/python2.7/dist-packages/cecilia/Resources/Control.py, line 108, in __init__ self.sizerMain.Add(Separator(self, (230,2), colour=BORDER_COLOUR), 1, wx.EXPAND) File /usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py, line 14453, in Add return _core_.Sizer_Add(*args, **kwargs) wx._core.PyAssertionError: C++ assertion Assert failure failed at ../src/common/sizer.cpp(1401) in DoInsert(): too many items (4 1*3) in grid sizer (maybe you should omit the number of either rows or columns?) I've included the standard information from the other mails I filed earlier below: We're aiming to migrate the archive to using
Bug#718154: marked as done (psychopy: FTBFS: Tests failed)
Your message dated Tue, 07 Oct 2014 12:20:12 +
with message-id e1xbtks-0006qu...@franck.debian.org
and subject line Bug#718154: fixed in psychopy 1.79.00+git16-g30c9343.dfsg-1.1
has caused the Debian Bug report #718154,
regarding psychopy: FTBFS: Tests failed
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.)
--
718154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: psychopy
Version: 1.77.02.dfsg-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130726 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
echo I: Running tests using default Python
I: Running tests using default Python
cd build xvfb-run -s -screen 0 1024x768x24 -ac +extension GLX +render
-noreset \
python ../psychopy/tests/runPytest.py -v -s -m not
needs_sound || { echo TESTS FAILED; exit 1; }
= test session starts
==
platform linux2 -- Python 2.7.5 -- pytest-2.2.3 -- /usr/bin/python
collecting ... Xlib: extension RANDR missing on display :99.
collected 0 items / 1 errors
ERRORS
__ ERROR collecting .
__
_pytest.runner:120: in __init__
???
_pytest.main:299: in _memocollect
???
_pytest.main:223: in _memoizedcall
???
_pytest.main:299: in lambda
???
_pytest.main:440: in collect
???
_pytest.main:456: in _collect
???
py._path.common:312: in visit
???
py._path.common:358: in gen
???
py._path.common:358: in gen
???
py._path.common:358: in gen
???
py._path.common:348: in gen
???
_pytest.main:479: in _recurse
???
_pytest.main:135: in call_matching_hooks
???
_pytest.config:289: in _getmatchingplugins
???
_pytest.config:188: in getconftestmodules
???
_pytest.config:224: in importconftest
???
_pytest.config:229: in _postimport
???
_pytest.config:278: in _onimportconftest
???
_pytest.core:179: in consider_conftest
???
_pytest.core:89: in register
???
_pytest.core:419: in __call__
???
_pytest.core:430: in _docall
???
_pytest.core:348: in execute
???
_pytest.core:231: in pytest_plugin_registered
???
_pytest.core:317: in call_plugin
???
_pytest.core:348: in execute
???
lib.linux-x86_64-2.7/psychopy/tests/test_app/conftest.py:12: in
pytest_configure
psychopyApp._app = psychopyApp.PsychoPyApp(interactive=False,
showSplash=False)
lib.linux-x86_64-2.7/psychopy/app/psychopyApp.py:107: in __init__
self.onInit(**kwargs)
lib.linux-x86_64-2.7/psychopy/app/psychopyApp.py:138: in onInit
from psychopy import compatibility
lib.linux-x86_64-2.7/psychopy/compatibility.py:3: in module
import psychopy.data
lib.linux-x86_64-2.7/psychopy/data.py:7: in module
from psychopy import misc, gui, logging
lib.linux-x86_64-2.7/psychopy/misc.py:10: in module
import monitors
lib.linux-x86_64-2.7/psychopy/monitors/__init__.py:6: in module
import calibTools
lib.linux-x86_64-2.7/psychopy/monitors/calibTools.py:48: in module
os.makedirs(monitorFolder)
/usr/lib/python2.7/os.py:150: in makedirs
makedirs(head, mode)
/usr/lib/python2.7/os.py:150: in makedirs
makedirs(head, mode)
/usr/lib/python2.7/os.py:157: in makedirs
mkdir(name, mode)
E OSError: [Errno 13] Permission denied: '/sbuild-nonexistent'
=== 1 error in 1.11 seconds
Preferences.py failed to create folder /sbuild-nonexistent/.psychopy2.
Settings will be read-only
TESTS FAILED
make: *** [install/psychopy] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/07/26/psychopy_1.77.02.dfsg-1_unstable.log
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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Source: psychopy
Source-Version: 1.79.00+git16-g30c9343.dfsg-1.1
We believe that the bug you reported is fixed in the latest version of
psychopy, which is due to be installed in
Bug#764343: marked as done (media-player-info: maintainer address bounces)
Your message dated Tue, 07 Oct 2014 12:18:56 + with message-id e1xbtje-0005hm...@franck.debian.org and subject line Bug#764343: fixed in media-player-info 22-2 has caused the Debian Bug report #764343, regarding media-player-info: maintainer address bounces 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.) -- 764343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: media-player-info Severity: serious Tags: sid X-Debbugs-Cc: Martin Pitt mp...@debian.org The maintainer address for media-player-info bounces, see below. (Also why does the upload to Debian have an Original-Maintainer field?) Ansgar On 10/07/2014 12:49, kubuntu-devel-ow...@lists.ubuntu.com wrote: You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at kubuntu-devel-ow...@lists.ubuntu.com. ---End Message--- ---BeginMessage--- Source: media-player-info Source-Version: 22-2 We believe that the bug you reported is fixed in the latest version of media-player-info, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 764...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt mp...@debian.org (supplier of updated media-player-info package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 07 Oct 2014 14:14:11 +0200 Source: media-player-info Binary: media-player-info Architecture: source all Version: 22-2 Distribution: unstable Urgency: medium Maintainer: Martin Pitt mp...@debian.org Changed-By: Martin Pitt mp...@debian.org Description: media-player-info - Media player identification files Closes: 764343 Changes: media-player-info (22-2) unstable; urgency=medium . * Fix Maintainer: field again, crept in from basing the previous upload on the latest Ubuntu version. (Closes: #764343) Checksums-Sha1: 2b9510ca90676771fefed601e35acdf77de72516 1806 media-player-info_22-2.dsc 5b96992207fcd8f621f74912153baf2be8fb8673 3976 media-player-info_22-2.debian.tar.xz e06a3462377fc62dcdf30a2661553c0cf63438c1 33264 media-player-info_22-2_all.deb Checksums-Sha256: ddaafdd73b31a26129bcae3012cd9a9eac619a61e8990efc5f0742f333168450 1806 media-player-info_22-2.dsc 4bc1b5a2cb7dced9187c0d207e490c5ecea6da8720e5daf64bd275bab100112a 3976 media-player-info_22-2.debian.tar.xz 49ebcce5a1c4c450efad3b71e1581665ffaecf5ed0c334dfdb87d05e64d94024 33264 media-player-info_22-2_all.deb Files: dfee59ccf78dce3c8e31523020b71a7a 1806 admin optional media-player-info_22-2.dsc bc2cc5708bca66f0b68f161308f3de28 3976 admin optional media-player-info_22-2.debian.tar.xz 5c5a6bd11fcaa637b7130234bd9511ab 33264 admin optional media-player-info_22-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUM9lpAAoJENFO8V2v4RNH76AP/RX39L7A9vpg5oz/JdpB3+Zz wS7c3iY1YXnAszgN+nm+uzfUbjjXo0bqFgu1p2CxbD71hUJCyRiA2r0SZqLBoD0n +LHZGZUQ7zX8o40VRgSAp/Q2/6etEUL3s5bD9TGnpwlWlatf2cFr2Fmcl74mIil9 zSTu1qMNmvRepZui9OusWaIeQoJoNYKhrqQHoufLdZB2kHzcaOii+JWETy5nmbVL EHIVLxaO2We0L7mPKvElADxJcrAZDh/LfCQX3wLF5gSS2Ogk9mNXAIY1e+c65beX YqiTGMx7iKcLlvGXC5XNAi/9axnpYmPf7dLp2K9Lz2h0+kMUjsJHu+0nuxpO7ALG egT+YykQmiMNNCU6s+RWljoaoreJeSRV1Ls0tz+SIQzkgwBW/Ma3sRcUCaZaSUpt Pre+CH/0u4G+QCgf2WjSYDuf8TAiyg9T5n1CBdSAOKGvtKwBOnIdr5qIAa9szMAu ZT/mLKwFbMY0J7bx/YAFSeMRKkGa3YqNCXlX41dwWZ8gsUL75VbYAnhnPrUZq/XE bS2EnwTUO3ilpL78IN6igm+dOVz4vzGdytSRVQWv7X+TEWpsBqbdnG2KxQ+g5A4O 5oAryuZ8VD0FCFPggN/9k4XIyFWazNQDNL0axAUBvX2Sr5UYkjS8PoSWtL8nAwxF Z9ve9wd17ThvXcLWQ7RD =qa9A -END PGP SIGNATUREEnd Message---
Bug#759090: marked as done (psychopy: Please update to use wxpython3.0)
Your message dated Tue, 07 Oct 2014 12:20:12 + with message-id e1xbtks-0006qa...@franck.debian.org and subject line Bug#759090: fixed in psychopy 1.79.00+git16-g30c9343.dfsg-1.1 has caused the Debian Bug report #759090, regarding psychopy: Please update to use wxpython3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 759090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: psychopy Version: 1.79.00+git16-g30c9343.dfsg-1 Severity: important Tags: sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wxpy3.0 Control: block 755757 by -1 We're aiming to migrate the archive to using wxpython3.0 instead of wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released. This transition is already underway, and is being tracked by the release team here: https://release.debian.org/transitions/html/wxpython3.0.html The wxPython 3.0 API mostly adds to the wxPython2.8 API. Many packages work with wxPython 3.0 without any changes, but there are a few incompatibilities. For example, wx.Color is no longer supported as an alias for wx.Colour, and some constants which were deprecated in 2.8 have been removed. All the removed constants I'm aware of were set to 0 in wxPython 2.8, so removing them is still compatible with 2.8. To assist updating to wxPython 3.0, I've put together a script which will help make the mechanical changes required. This is in a git repo on collab-maint along with a README about using it and updating packages for wxPython 3.0 in general: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git The script has some options to control the sorts of changes it makes - see the README and --help output for more information - you can view the latest version of the README online here: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I've developed this script by trying to convert 20+ packages. Please try it out on your package - in many cases, it should be enough to get your package working (if it doesn't already) - if it does, please upload (and close this bug). If the script doesn't do the job, please let me know (or improve the script if you can figure out what it needs to do to get your package working). Another issue you may hit is that wxWidgets 3.0 now defaults to enabling its WXDEBUG checks for incorrect API usage, so some applications will emit scary sounding assertion failures. These are unlikely to actually be new, just in a default build of 2.8, such incorrect uses were handled quietly behind the scenes. Sometimes these are easy to fix, but if not you can easily patch the application to tell wx 3.0 to handle them in the same way wx 2.8 does - details of how to do so are in the README: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README I'm happy to sponsor uploads for this transition, though if you have an active sponsor already check with them first - I don't want to tread on anyone's toes. Cheers, Olly ---End Message--- ---BeginMessage--- Source: psychopy Source-Version: 1.79.00+git16-g30c9343.dfsg-1.1 We believe that the bug you reported is fixed in the latest version of psychopy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts o...@survex.com (supplier of updated psychopy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Oct 2014 10:59:58 + Source: psychopy Binary: psychopy Architecture: source all Version: 1.79.00+git16-g30c9343.dfsg-1.1 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team t...@neuro.debian.net Changed-By: Olly Betts o...@survex.com Description: psychopy - environment for creating psychology stimuli in Python Closes: 718154 759090 Changes: psychopy (1.79.00+git16-g30c9343.dfsg-1.1) unstable; urgency=medium . * Non-maintainer upload. * Update for wxPython 3.0 (Closes: #759090): - New patch: wxpython3.0.patch * Create temporary directory and point $HOME to it when running tests during
Bug#763488: [Openjdk] Bug#763488: NMUs uploaded to DELAYED/5 (libjpeg-turbo transition)
On Tue, Oct 7, 2014, at 14:14, Matthias Klose wrote: Am 07.10.2014 um 14:01 schrieb Ondřej Surý: Hi, to finish the libjpeg-turbo transition in time for next stable releases, the missing fixes for libjpeg8-dev to libjpeg-dev changes in build depends were built and uploaded to DELAYED/5 as NMUs. No other changes than those related to libjpeg8 to libjpeg-turbo were done in the packages. please avoid these uploads. 6 and 8 are not part of the upcoming release, I know, but for our sanity they should be updated as well, so we don't have to track the exceptions. and we'll have another 7 upload soonish. If soonish ~ 5 days then it shouldn't be a problem, since the new version will have higher version number than the one in DELAYED/5 and if soonish = 5 days than I see no problem with NMU to help finish the transition, right? But feel free to cancel the DELAYED/5 upload if you really feel strongly about this. (Or I can do that, although I would prefer not to.) Cheers, -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761040: [libqtwebkit4] Browsers based on Webkit crash on loading pages
On Monday 06 October 2014 12:28:46 Lennart Sorensen wrote: [snip] I tried running qupzilla and got this: Do you happen to see a SIGBUS or a SIGSERV when you reproduce the bug? I've been asked by upstream about this :-/ -- 8: Si un archivo ha pasado a la Papelera de Reciclaje * Ud tiene una carpeta llamada Papelera de Reciclaje Damian Nadales http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#761040: [libqtwebkit4] Browsers based on Webkit crash on loading pages
On Tuesday 07 October 2014 09:43:05 Lisandro Damián Nicanor Pérez Meyer wrote: On Monday 06 October 2014 12:28:46 Lennart Sorensen wrote: [snip] I tried running qupzilla and got this: Do you happen to see a SIGBUS or a SIGSERV when you reproduce the bug? I've been asked by upstream about this :-/ Sorry, I think the question is different. In powerpc: do you get a SIGBUS or SIGSERV for unaligned access? -- Programming is really just the mundane aspect of expressing a solution to a problem. There are talents that are specifically related to actually coding, but the real issue is being able to grasp problems and devise solutions that are detailed enough to actually be coded. John Carmack answers on Slashdot, http://slashdot.org/games/99/10/15/1012230.shtml Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#764353: libhdf4: FTBFS on s390x and ppc64el: test failures
Source: libhdf4 Severity: serious Version: 4.2.10-2 libhdf4 FTBFS in the (newly enabled) test suite on s390x and ppc64el. On s390x, the test setup program crashes: https://buildd.debian.org/status/fetch.php?pkg=libhdf4arch=s390xver=4.2.10-2stamp=1412545742 === HDF Library Fortran Interface Tests Setup === *** Error in `/«PKGBUILDDIR»/HDF4.2.10/hdf/test/.libs/lt-fortestF': free(): invalid next size (fast): 0xafeb3fd0 *** Program received signal SIGABRT: Process abort signal. Backtrace for this error: #0 0x3FFFD066C57 #1 0x3FFFD0673B5 #2 0x39721F3 #3 0x3FFFCE3340C #4 0x3FFFCE34A0D #5 0x3FFFCE7D491 #6 0x3FFFCE83EFD #7 0x3FFFCE84ED3 #8 0x3FFFD2A38B1 #9 0x3FFFD2A41FD #10 0x80007DB5 in MAIN__ at fortestF.f:? Aborted On ppc64el, The testsuite went in a loop, so the log is too big to be sent (12GB). Aurelien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764355: targetcli: Fails to load or save any config on Jessie
Package: targetcli Version: 3.0+git0.7e32595e-2 Severity: grave Justification: renders package unusable Having tried on two systems (one fresh install netboot system), and I really can't get this package to do anything at all: . Give useless error message if kernel modules aren't loaded: This RTSRoot does not exist in configFS. . Fails to save an empty config ( #FIXME ) . Fails to create any usable export config, even for a file backed I/O: / ls o- / . [...] o- backstores .. [...] | o- fileio [0 Storage Object] | o- iblock [0 Storage Object] | o- pscsi . [0 Storage Object] | o- rd_mcp [0 Storage Object] o- ib_srpt ... [0 Targets] o- iscsi . [0 Targets] o- loopback .. [0 Targets] o- qla2xxx ... [0 Targets] o- tcm_fc [0 Targets] o- vhost . [0 Targets] / /backstores/fileio /backstores/fileio create test /home/testfile 100m Generating a wwn serial. Using buffered mode. Created fileio test. /backstores/fileio cd / / saveconfig WARNING: Saving ermintrude current configuration to disk will overwrite your boot settings. The current target configuration will become the default boot config. Are you sure? Type 'yes': yes Saving new startup configuration Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/configshell/shell.py, line 990, in run_interactive self._cli_loop() File /usr/lib/python2.7/dist-packages/configshell/shell.py, line 820, in _cli_loop self.run_cmdline(cmdline) File /usr/lib/python2.7/dist-packages/configshell/shell.py, line 934, in run_cmdline self._execute_command(path, command, pparams, kparams) File /usr/lib/python2.7/dist-packages/configshell/shell.py, line 909, in _execute_command result = target.execute_command(command, pparams, kparams) File /usr/lib/python2.7/dist-packages/targetcli/ui_node.py, line 103, in execute_command pparams, kparams) File /usr/lib/python2.7/dist-packages/configshell/node.py, line 1416, in execute_command result = method(*pparams, **kparams) File /usr/lib/python2.7/dist-packages/targetcli/ui_root.py, line 68, in ui_command_saveconfig CliConfig.save_running_config() File /usr/lib/python2.7/dist-packages/targetcli/cli_config.py, line 65, in save_running_config config.load_live() File /usr/lib/python2.7/dist-packages/rtslib/config.py, line 562, in load_live source=source, allow_new_attrs=True) File /usr/lib/python2.7/dist-packages/rtslib/config.py, line 190, in _load_parse_tree token = self.validate_obj(token, cur) File /usr/lib/python2.7/dist-packages/rtslib/config.py, line 385, in validate_obj raise ConfigError(Unknown object type: %s % obj_type) ConfigError: Unknown object type: storage / Same problem on previous 3.14 kernel and on both machines. It seems strange that this managed to get through testing in this state, as it currently seems completely unusuable. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages targetcli depends on: ii python 2.7.8-1 ii python-configshell 1.5+git0.0827baa6-2 ii python-rtslib 3.0+git0.86e46bc6-2 targetcli recommends no packages. targetcli suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764357: non-free file in package
Package: ssdeep Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, according to the file header, the file edit_dist.c is copied from trn3.6. Due to restrictions in the license, trn3.6 is in non-free. So please replace this file in ssdeep by a free version. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720517: configuration files, ownership and dpkg-statoverride
Paul Gevers writes (configuration files, ownership and dpkg-statoverride): I am looking into dbconfig-common RC bug 720517 [1] and I was wondering what the general idea is of maintainer scripts changing the permissions and/or owners of configuration files and the use of dpkg-statoverride. The user should not be expected or required to use dpkg-statoverride on configuration files (whether they are dpkg-managed conffiles or maintainers-script-managed). chmod/chown should be sufficient. I myself find it unacceptable that updating a package changes the permissions/owners of a configuration file without asking, even when I have not documented that fact with dpkg-statoverride. At least that is how I read policy 10.7.3 [2]. I think you are right. But I don't see anyone disputing this. Also I don't see in your references an explanation from anyone as to why dbconfig-common does this. Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725714: Partial fix using hw-setup for the missing firmware problem in d-i?
Here is another draft patch for hw-detect. This one is tested, and
find the missing firmware on my X200 test laptop.
This approach keep the non-functioning code and add two new
approaches, one looking at the meta information for loadmed modules,
and one parsing the dmesg output. The union from all three methods
are then presented as the list of wanted firmware.
diff --git a/check-missing-firmware.sh b/check-missing-firmware.sh
index 60c6ff4..74db55b 100755
--- a/check-missing-firmware.sh
+++ b/check-missing-firmware.sh
@@ -61,6 +61,18 @@ nic_is_configured() {
return 1
}
+add_if_fw_missing() {
+fwfile=$1
+if [ ! -e /lib/firmware/$fwfile ] ; then
+if grep -q ^$fwfile$ $DENIED 2/dev/null; then
+ log listed in $DENIED
+continue
+fi
+files=${files:+$files }$fwfile
+modules=$module${modules:+ $modules}
+fi
+}
+
check_missing () {
upnics
@@ -117,11 +129,30 @@ check_missing () {
done
done
+# Workaround for bug #725714, the kernel and udev no longer
+# let us know via /dev/.udev/firmware-missing and
+# /run/udev/firmware-missing which firmware files the kernel
+# drivers look for. This approach will only find firmware for
+# the loaded kernel modules. Modules refusing to
+# register/load when the firmware is missing will be missed.
+for module in $(cut -d -f1 /proc/modules); do
+for fwfile in $(modinfo $module | grep ^firmware: | cut -d: -f2);
do
+log looking for firmware file $fwfile needed by $module
+add_if_fw_missing $fwfile
+done
+done
+for fwfile in $(dmesg | grep 'firmware: failed' | sed 's/.*firmware:
failed to load //' | cut -d -f1); do
+# Dummy make sure '-n $modules' test below find something
+module=kernel
+log looking for firmware file $fwfile requested by kernel
+add_if_fw_missing $fwfile
+done
+
if [ -n $modules ]; then
log missing firmware files ($files) for $modules
return 0
else
- log no missing firmware in $MISSING
+ log no missing firmware for any kernel module
return 1
fi
}
--
Happy hacking
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: libmatheval: diff for NMU version 1.1.11+dfsg-1.2
Processing control commands: tags 746013 + pending Bug #746013 [libmatheval] libmatheval: please migrate to guile-2.0 Added tag(s) pending. -- 746013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746013 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#746013: libmatheval: diff for NMU version 1.1.11+dfsg-1.2
Control: tags 746013 + pending
Dear maintainer,
I've prepared an NMU for libmatheval (versioned as 1.1.11+dfsg-1.2) and
uploaded it to unstable with a fix for the compiler optimisation effects.
This diff extends the previous diff for i386 support.
Regards.
diff -Nru libmatheval-1.1.11+dfsg/debian/changelog libmatheval-1.1.11+dfsg/debian/changelog
--- libmatheval-1.1.11+dfsg/debian/changelog 2014-10-06 15:38:39.0 +0100
+++ libmatheval-1.1.11+dfsg/debian/changelog 2014-10-07 15:16:41.0 +0100
@@ -1,3 +1,15 @@
+libmatheval (1.1.11+dfsg-1.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add a fix to lib/xmath.c to limit the precision to
+within the range compatible with the current compiler
+optimisations so that the uncertain process of comparing
+floating point numbers can be used in the test suite.
+Completes the migration to guile-2.0 (Closes: #746013)
+ * Update symbols for the patched function
+
+ -- Neil Williams codeh...@debian.org Tue, 07 Oct 2014 15:04:50 +0100
+
libmatheval (1.1.11+dfsg-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru libmatheval-1.1.11+dfsg/debian/libmatheval1.symbols libmatheval-1.1.11+dfsg/debian/libmatheval1.symbols
--- libmatheval-1.1.11+dfsg/debian/libmatheval1.symbols 2014-05-06 19:29:30.0 +0100
+++ libmatheval-1.1.11+dfsg/debian/libmatheval1.symbols 2014-10-07 15:15:38.0 +0100
@@ -48,6 +48,7 @@
math_sec@Base 1.1.3
math_sech@Base 1.1.3
math_step@Base 1.1.3
+ math_truncate15@Base 1.1.11
node_copy@Base 1.1.3
node_create@Base 1.1.3
node_derivative@Base 1.1.3
diff -Nru libmatheval-1.1.11+dfsg/debian/patches/004-arch-optimisation.patch libmatheval-1.1.11+dfsg/debian/patches/004-arch-optimisation.patch
--- libmatheval-1.1.11+dfsg/debian/patches/004-arch-optimisation.patch 1970-01-01 01:00:00.0 +0100
+++ libmatheval-1.1.11+dfsg/debian/patches/004-arch-optimisation.patch 2014-10-07 15:04:13.0 +0100
@@ -0,0 +1,73 @@
+Description: Compiler optimisation affects on floating point tests.
+ Truncate the precision of a returned double to 15 places.
+ This allows for compiler optimisations which may change the
+ comparison of floating point numbers on particular architectures.
+ .
+ libmatheval (1.1.11+dfsg-1.2) unstable; urgency=low
+ .
+ * Non-maintainer upload.
+ * Add a fix to lib/xmath.c to limit the precision to
+ within the range compatible with the current compiler
+ optimisations so that the uncertain process of comparing
+ floating point numbers can be used in the test suite.
+ Completes the migration to guile-2.0 (Closes: #746013)
+Author: Dave Pigott dave.pig...@linaro.org
+Bug-Debian: https://bugs.debian.org/746013
+
+---
+
+--- libmatheval-1.1.11+dfsg.orig/lib/xmath.c
libmatheval-1.1.11+dfsg/lib/xmath.c
+@@ -19,8 +19,32 @@
+ * http://www.gnu.org/licenses/.
+ */
+
++#include stdio.h
+ #include xmath.h
+
++
++double
++math_truncate15(double x)
++{
++ /*
++ * Truncate the precision of a returned double to 15 decimal places
++ * This is hacky, and as at the time of writing, is only required for
++ * the coth function, which due to optimisation and floating point
++ * width, gives a different result on i386 to all other platforms
++ * At the moment we're dealing with an explicit 15 significant digits.
++ * This could be generalised to a give me n digits of precision type
++ * solution
++ */
++ double d;
++ char s[128];
++
++ sprintf(s, %.15f, x);
++ sscanf(s, %lf, d);
++
++ return d;
++}
++
++
+ double
+ math_cot(double x)
+ {
+@@ -81,7 +105,7 @@ math_coth(double x)
+ /*
+ * Calculate hyperbolic cotangent value.
+ */
+- return 1 / tanh(x);
++ return math_truncate15(1 / tanh(x));
+ }
+
+ double
+--- libmatheval-1.1.11+dfsg.orig/tests/functions.at
libmatheval-1.1.11+dfsg/tests/functions.at
+@@ -335,7 +335,7 @@ AT_DATA([function.scm],
+ (display (evaluator-evaluate-x f 1))
+ ]])
+
+-AT_CHECK([matheval.sh function.scm], [ignore], [1.3130352854993315], [ignore])
++AT_CHECK([matheval.sh function.scm], [ignore], [1.313035285499331], [ignore])
+
+ AT_DATA([function.scm],
+ [[
diff -Nru libmatheval-1.1.11+dfsg/debian/patches/series libmatheval-1.1.11+dfsg/debian/patches/series
--- libmatheval-1.1.11+dfsg/debian/patches/series 2014-10-06 15:47:53.0 +0100
+++ libmatheval-1.1.11+dfsg/debian/patches/series 2014-10-07 14:58:25.0 +0100
@@ -1,2 +1,3 @@
002-skip-docs.patch
003-guile2.0.patch
+004-arch-optimisation.patch
Processed: severity of 763169 is serious
Processing commands for cont...@bugs.debian.org: severity 763169 serious Bug #763169 [apt] apt upgrade fails in postinst with adduser: not found Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 763169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763169 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#764360: kexec doesn't work with systemd
Package: kexec-tools Version: 1:2.0.4-1 Severity: serious Hi, the purpose of kexec is that it works 'out-of-the-box', this doesn't work anymore with a default jessie system (kexec 1:2.0.4-1, systemd 215-5+b1), a 'normal' reboot with kexec now behaves like a coldreboot, so kexec-tools is basically useless with systemd now. Regards, Daniel -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725714: Partial fix using hw-setup for the missing firmware problem in d-i?
On Tue, 2014-10-07 at 15:52 +0200, Petter Reinholdtsen wrote:
Here is another draft patch for hw-detect. This one is tested, and
find the missing firmware on my X200 test laptop.
This approach keep the non-functioning code
The firmware agent is never coming back, so please do remove the related
code.
and add two new
approaches, one looking at the meta information for loadmed modules,
and one parsing the dmesg output. The union from all three methods
are then presented as the list of wanted firmware.
diff --git a/check-missing-firmware.sh b/check-missing-firmware.sh
index 60c6ff4..74db55b 100755
--- a/check-missing-firmware.sh
+++ b/check-missing-firmware.sh
[...]
@@ -117,11 +129,30 @@ check_missing () {
done
done
+# Workaround for bug #725714, the kernel and udev no longer
+# let us know via /dev/.udev/firmware-missing and
+# /run/udev/firmware-missing which firmware files the kernel
+# drivers look for.
This belongs in the changelog not the code.
This approach will only find firmware for
+# the loaded kernel modules. Modules refusing to
+# register/load when the firmware is missing will be missed.
+for module in $(cut -d -f1 /proc/modules); do
+for fwfile in $(modinfo $module | grep ^firmware: | cut -d:
-f2); do
+log looking for firmware file $fwfile needed by $module
+add_if_fw_missing $fwfile
+done
+done
+for fwfile in $(dmesg | grep 'firmware: failed' | sed 's/.*firmware:
failed to load //' | cut -d -f1); do
Redundant use of grep; sed can do that (sed -n 's/.../.../p').
+# Dummy make sure '-n $modules' test below find something
+module=kernel
The driver name should appear at the start of the log line (after the
timestamp). Use that instead of 'kernel'.
+log looking for firmware file $fwfile requested by kernel
+add_if_fw_missing $fwfile
+done
+
Indentation of the above is inconsistent with the surrounding code (4
spaces vs hard tab).
Ben.
if [ -n $modules ]; then
log missing firmware files ($files) for $modules
return 0
else
- log no missing firmware in $MISSING
+ log no missing firmware for any kernel module
return 1
fi
}
--
Happy hacking
Petter Reinholdtsen
--
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky
signature.asc
Description: This is a digitally signed message part
Bug#746456: FTBFS as test does not terminate
Source: google-perftools Followup-For: Bug #746456 I've successfuly build 2.2.1-0.2 with my cowbuilder. It even passes all 46 tests: ... PASS: tcmalloc_and_profiler_unittest === All 46 tests passed === ... I think you can close this bug. Cheers, Santiago -- System Information: Debian Release: 7.2 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=es_CO.utf8, LC_CTYPE=es_CO.utf8 (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#616689: The bug now reaches the separate /usr on lvm case
Hello, This bug is now also a problem with the new version of initramfs-tools in the case of a separate /usr partition on a lvm, as /usr is also being mounting early in the boot sequence by initramfs (this problem wasn't hitting me beforehand as I did put a small root partition on a non-lvm partition for avoiding such problems ... :/) Actually, the solutions proposed there were not working for me, I still had to vgchange -ay on the initramfs prompt. My working solution ended up to add the scsi_mod.scan=sync option to be passed by grub, and forced the lvm scanning by adding to /usr/share/initramfs-tools/scripts/local-top/lvm2 the lines: lvm pvscan lvm vgscan lvm vgchange -ay before the activate_vg lines. Note that I added the lvm vgchange -ay line on top of the other one, as suggested previously. It seemed that the volume /groups/ were correctly scanned and identified during the initial boot-up, as I could read the following lines: PV /dev/sdb1 VG lv_data lvm2 [1.82 TiB / 0free] PV /dev/sda3 VG lv_system lvm2 [235.68 GiB / 0free] Total: 2 [2.05 TiB] / in use: 2 [2.05 TiB] / in no VG: 0 [0 ] Reading all physical volumes. This may take a while... Found volume group lv_data using metadata type lvm2 Found volume group lv_system using metadata type lvm2 But the lvm /volumes/ were not activated, as initramfs was waiting for the /usr partition, until complaing and falling back to the prompt were the vgchange command had to be performed... so that I ended up adding the vgchange command in a why not mood, that ended up to work for me. I do not know if this is a solution or a dirty hack, but at least it is working for me. I don't know neither if /all/ the modifications are indeed necessary, as I added them incrementally until it worked. I hope that I could help... -- Raphaël -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: unarchiving 694098, fixed 694098 in 10.0~svn252032-1
Processing commands for cont...@bugs.debian.org:
unarchive 694098
Bug #694098 {Done: Robert Millan r...@debian.org} [kfreebsd-10] kfreebsd-10:
CVE-2012-4576
Unarchived Bug 694098
fixed 694098 10.0~svn252032-1
Bug #694098 {Done: Robert Millan r...@debian.org} [kfreebsd-10] kfreebsd-10:
CVE-2012-4576
There is no source info for the package 'kfreebsd-10' at version
'10.0~svn252032-1' with architecture ''
Unable to make a source version for version '10.0~svn252032-1'
Marked as fixed in versions 10.0~svn252032-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
694098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694098
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#725714: Partial fix using hw-setup for the missing firmware problem in d-i?
Thank you for the code review. :) [Ben Hutchings] The firmware agent is never coming back, so please do remove the related code. I know and agree, but URL: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725714#163 asked for the non-working code to be kept to work with older kernels. I do not have any strong feelings, so I left it as it was. This belongs in the changelog not the code. Actually, as long as there are several blocks doing similar things, I believe an explanation should be close to the code to explain why. I will wonder when I return in a few years time. :) The driver name should appear at the start of the log line (after the timestamp). Use that instead of 'kernel'. Yeah, but did not find a simple way to do it, and it is not affecting the functionallity, only the user messages. Should probably be fixed in the final version. Redundant use of grep; sed can do that (sed -n 's/.../.../p'). Yeah. Indentation of the above is inconsistent with the surrounding code (4 spaces vs hard tab). It will happen before any commit is done. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725714: Partial fix using hw-setup for the missing firmware problem in d-i?
On Tue, 2014-10-07 at 17:09 +0200, Petter Reinholdtsen wrote: Thank you for the code review. :) [Ben Hutchings] The firmware agent is never coming back, so please do remove the related code. I know and agree, but URL: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725714#163 asked for the non-working code to be kept to work with older kernels. Actually it is udev that removed this feature originally. Anyway, I shan't argue this with KiBi. I do not have any strong feelings, so I left it as it was. This belongs in the changelog not the code. Actually, as long as there are several blocks doing similar things, I believe an explanation should be close to the code to explain why. I will wonder when I return in a few years time. :) Perhaps this would be better placed above the old code, as that is what should be cleaned up at some later date. The driver name should appear at the start of the log line (after the timestamp). Use that instead of 'kernel'. Yeah, but did not find a simple way to do it, and it is not affecting the functionallity, only the user messages. Should probably be fixed in the final version. Redundant use of grep; sed can do that (sed -n 's/.../.../p'). Yeah. Indentation of the above is inconsistent with the surrounding code (4 spaces vs hard tab). It will happen before any commit is done. Thanks. Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky signature.asc Description: This is a digitally signed message part
Bug#746012: closed by Matthias Klose d...@debian.org (Bug#746012: fixed in graphviz 2.38.0-1)
Control: severity -1 normal Am 02.10.2014 um 22:38 schrieb Rob Browning: reopen 746012 thanks Debian Bug Tracking System ow...@bugs.debian.org writes: This is an automatic notification regarding your Bug report which was filed against the graphviz package: #746012: graphviz: please migrate to guile-2.0 It has been closed by Matthias Klose d...@debian.org. It looks like there's one more vestigial bit, i.e. the libltdl-dev dependency in the control file. That's from guile-1.8, not 2.0, and should no longer be necessary. # Broken Build-Depends: ... graphviz: guile-1.8-dev ... this is hardly release critical. Please set severities correctly when reopening issues. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#746012 closed by Matthias Klose d...@debian.org (Bug#746012: fixed in graphviz 2.38.0-1)
Processing control commands: severity -1 normal Bug #746012 [graphviz] graphviz: please migrate to guile-2.0 Severity set to 'normal' from 'serious' -- 746012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746012 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 764162
Processing commands for cont...@bugs.debian.org: tags 764162 + moreinfo Bug #764162 [src:linux] linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 764162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764162 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 (with 1 errors): unarchiving 694098, fixed 694098 in 10.0~svn252032-1
Processing commands for cont...@bugs.debian.org:
unarchive 694098
fixed 694098 10.0~svn252032-1
Bug #694098 {Done: Robert Millan r...@debian.org} [kfreebsd-10] kfreebsd-10:
CVE-2012-4576
There is no source info for the package 'kfreebsd-10' at version
'10.0~svn252032-1' with architecture ''
Unable to make a source version for version '10.0~svn252032-1'
Ignoring request to alter fixed versions of bug #694098 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
694098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694098
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#746013: marked as done (libmatheval: please migrate to guile-2.0)
Your message dated Tue, 07 Oct 2014 15:51:15 + with message-id e1xbx2h-0008fj...@franck.debian.org and subject line Bug#746013: fixed in libmatheval 1.1.11+dfsg-1.2 has caused the Debian Bug report #746013, regarding libmatheval: please migrate to guile-2.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 746013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libmatheval I'm planning to have guile-1.8 removed from unstable before the freeze; please migrate to guile-2.0 as soon as possible. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 ---End Message--- ---BeginMessage--- Source: libmatheval Source-Version: 1.1.11+dfsg-1.2 We believe that the bug you reported is fixed in the latest version of libmatheval, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 746...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Neil Williams codeh...@debian.org (supplier of updated libmatheval package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 07 Oct 2014 15:04:50 +0100 Source: libmatheval Binary: libmatheval-dev libmatheval1 Architecture: source amd64 Version: 1.1.11+dfsg-1.2 Distribution: unstable Urgency: low Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Neil Williams codeh...@debian.org Description: libmatheval-dev - GNU library for evaluating symbolic mathematical expressions (dev libmatheval1 - GNU library for evaluating symbolic mathematical expressions (run Closes: 746013 Changes: libmatheval (1.1.11+dfsg-1.2) unstable; urgency=low . * Non-maintainer upload. * Add a fix to lib/xmath.c to limit the precision to within the range compatible with the current compiler optimisations so that the uncertain process of comparing floating point numbers can be used in the test suite. Completes the migration to guile-2.0 (Closes: #746013) * Update symbols for the patched function Checksums-Sha1: 5ca55edaa78c520ed4534358b0dcc6cf42bbe944 2180 libmatheval_1.1.11+dfsg-1.2.dsc f93317eeb83f98575e027bc7a1b8c54a44d4cf45 7116 libmatheval_1.1.11+dfsg-1.2.debian.tar.xz 5259744cc4d4992e6e40e61d2dd127616186e1a0 23778 libmatheval-dev_1.1.11+dfsg-1.2_amd64.deb d5569bfbaf9df8802f71584218283c20bfa67d69 22872 libmatheval1_1.1.11+dfsg-1.2_amd64.deb Checksums-Sha256: 22aea35dcd950b23f57a6e5b69e6fc9ed2e3afcd3396d2e9dd0144cf8049112c 2180 libmatheval_1.1.11+dfsg-1.2.dsc ed990bf6dffd28b7d2834d65cc9066e21f0c59544da2f1c0b39a1d5277daf672 7116 libmatheval_1.1.11+dfsg-1.2.debian.tar.xz 800a88dbb19a42f252439d2a189dbda9b2b8be686a4161f316b500cb9a02eb0f 23778 libmatheval-dev_1.1.11+dfsg-1.2_amd64.deb 4b742afe768da15dc5edf74f24ee69b108cb60546847ca3195879982cc0cc26d 22872 libmatheval1_1.1.11+dfsg-1.2_amd64.deb Files: 06c4c597cbc100d9a58d22363f6ad958 23778 libdevel optional libmatheval-dev_1.1.11+dfsg-1.2_amd64.deb 6eb15318160271c82d97186f1ee9f9ba 22872 libs optional libmatheval1_1.1.11+dfsg-1.2_amd64.deb 679f35ee083fc2d19e61a0ddaf07197c 2180 science optional libmatheval_1.1.11+dfsg-1.2.dsc 5a51fb0221cb00acf276dd2ba4a5e90c 7116 science optional libmatheval_1.1.11+dfsg-1.2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUM/Z6AAoJEPFn5DyBQ7aC1TQP/1ew/p2xMBfZ4pCznsTgWfbK qK/NAVEeOzTq02BhRTR9/roSKTouQht5PC6MjQVffplP+lSl6hrT+X1SemyBBO4K QE89zZOdyc0PFXw6RTFnZ0WR/4uk0quOBVSdgO7izcc4emUARpNO9p+M5jCP+Gq6 0mA1cnuG7ZysLVPxelVEnmvXGRZiXV1lZhOwvayRTmeBTB5dt5zx8szhJ67dlfEM NM4QZZyuUhE9pKoSuYnuxeVP+9mj2PzK2SHpEvegK6s+bcNP92a1Z/PJ1x0HP5YO tReQyeOaTQqBlPbM4+sh7f2CwUDsSCrCSznpFSjB1CPjI1W1Tztp+v/JC77EdyY0 SGGwlpjNnA6n7/DdhJ9vH4GuGylwHaOZSoCN4GEQCCyhJGJXyZB1sptcS+zwR1mK 3U1WsgISz9Ww3r+lxn9Zuc2bKdoF1n2UiUS8MH8ouyUgPj+eIr3XAe/6HVJg/h+v GcICoW3p9uQNdx5hRnXb48fo3ta8iJBXB31uodvrF5o++buFztf9e54cPXOqJoXy kHYS5CnJKwq01SfndFvpRppS0TZWwI5bOb/AY9prLP28LGcmU05S6/n04aFQ2GDK
Bug#756243: marked as done (spice-vdagent: Neither guest resizing nor clipboard sharing work)
Your message dated Tue, 07 Oct 2014 15:52:54 + with message-id e1xbx4i-gh...@franck.debian.org and subject line Bug#756243: fixed in spice-vdagent 0.15.0-1.2 has caused the Debian Bug report #756243, regarding spice-vdagent: Neither guest resizing nor clipboard sharing work 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.) -- 756243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: spice-vdagent Severity: normal Version: 0.15.0-1 Hi, I'm testing spice-vdagent in a sid (GNOME Shell) guest, on a sid (GNOME Shell, libvirt/qemu, QXL display, Spice channels enabled) host, in spicy. The guest display doesn't resize to match the window size. The clipboard sharing doesn't work either way. Any debugging info I could provide? Cheers, -- intrigeri ---End Message--- ---BeginMessage--- Source: spice-vdagent Source-Version: 0.15.0-1.2 We believe that the bug you reported is fixed in the latest version of spice-vdagent, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 756...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. intrigeri intrig...@debian.org (supplier of updated spice-vdagent package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 07 Oct 2014 16:47:46 +0200 Source: spice-vdagent Binary: spice-vdagent Architecture: source amd64 Version: 0.15.0-1.2 Distribution: unstable Urgency: medium Maintainer: Liang Guo guoli...@debian.org Changed-By: intrigeri intrig...@debian.org Description: spice-vdagent - Spice agent for Linux Closes: 732924 756243 Changes: spice-vdagent (0.15.0-1.2) unstable; urgency=medium . * Non-maintainer upload, with permission from maintainer. * Use systemd for session information (Closes: #756243). Accordingly build-depend on libsystemd-login-dev, which is needed for getting session information from logind. * Start spice-vdagent in the GDM3 greeter session (Closes: #732924). Checksums-Sha1: 02d2ebe62f2efa69ccb3afcdd73d36f83e0863ef 2115 spice-vdagent_0.15.0-1.2.dsc 028a3612a3d81c0caaed09b8b0b81ea9bbf33648 4292 spice-vdagent_0.15.0-1.2.debian.tar.xz d548252a7f0e30ce8cfe4929e92a544dbe7399bc 43316 spice-vdagent_0.15.0-1.2_amd64.deb Checksums-Sha256: b4fe585db0488210f772b5359c2b4ccd9bf4502b89a72ada62b95df55318b1b1 2115 spice-vdagent_0.15.0-1.2.dsc 24910170cf02e98bf62c5594c15cb42faf2edcd9ac8c45b589c7fd76b8f87e1d 4292 spice-vdagent_0.15.0-1.2.debian.tar.xz 98a071daf04267db0230ac6e98168fc9c4e44ce03c1f73b3ea19c17f25a59756 43316 spice-vdagent_0.15.0-1.2_amd64.deb Files: 7cb76c3abd548f9c2d5c57a22a6601d1 2115 x11 optional spice-vdagent_0.15.0-1.2.dsc c25b1ce2c25715d2e737cc47fc2d85b4 4292 x11 optional spice-vdagent_0.15.0-1.2.debian.tar.xz cd4c399acb4cc42971033000739b3b8d 43316 x11 optional spice-vdagent_0.15.0-1.2_amd64.deb -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJUM/2hAAoJELrOFdKldJj/VVAQAKI2frTUrhR8FdRo9AsnZ0DG HwZF5fSPpODxkdlXHThJtFBhn0XCQWZF2DIOuRg17W8Tp/iv+KF+9Ljwh+VTT8oV PrP4fmRcfKOKe0PRfFZPlzavcNm8NDFLxJ6ANlXyRUFaiQoW31IOF3dCY3rsiwdZ d4M+V9NvpMCGTjAD+kUgNMrtRYuq9Nw2R6/mQfGIUd5jTLL6OKCvG3r6OjHdWEKT 25+fXudN8/sG2EQwRVap0CNBl4DuhF/kU//r2G/TZtkbL2D3E9LWCZ75Udjt3duj ywjmZoJOU8TkC2/mIDb40t2urcwZkrGy7AnRt0Rgpi8JvoE1F90d91RH8WTPn9cM R0nzh1cG6s1CEV3R4b0gpJZ7G+2DXL2s+2mDcyIPIuAYzku2CLx3TT3djCI2DB+k /4bqPOjjvRHH/aUr92imLamlhXnefplrblj6km9TM63JxuzHsNXoy048qiq6Phm7 GvVzUl+eYD1mQ7pCgTIC/VgXje1XYhlimVGUEdVf2kbk6winq5QkojwbzmfTCwA+ zzEwS/AojgQFN/olAoiEupWemHeC0dNVBM3MlVKeqnXO5wO+JpAm2vVwGhzeBw7m DY8Gw1h8apEEaDZj8hEloRixjI+gQhb1ctWuiX0WQ60c4O+uXtYfsMJ+Qk0FGQGj EYrnYKINj+1/lq69jV/j =C9w4 -END PGP SIGNATUREEnd Message---
Bug#718315: Please reduce severity of bug
Dear Maintainer, I do not believe that this bug constitutes a security vulnerability or that it deserves grave severity. To be exploited remotely, you have to execute an untrusted XSLT stylesheet, which is similar to executing untrusted arbitrary code, and is a bad idea for reasons much more severe than this DoS. For example, using external entities and the document() function, an untrusted XSLT stylesheet can read arbitrary files from the filesystem and upload their contents to a Web server on the Internet. So in order to safely execute an untrusted XSLT stylesheet, you really need to run the XSLT processor in a sandbox with restricted filesystem and network access. At that point you might as well use ulimit or cgroups to prevent resource consumption such as from infinite recursion. As for exploiting locally, there are already a plethora of ways for a local user to DoS the system, such as by running a fork bomb in bash. In these ways, Xalan is similar to an interpreter like bash or perl. The fact that malicious programs can do great harm to a system if interpreted by bash or perl does not constitute a security vulnerability in bash or perl, and nor should it in Xalan. I therefore propose that the severity of this bug be reduced to important or normal so that Xalan can migrate to Testing. It would be a shame for Xalan to not make it into Jessie because of this. Regards, Andrew -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): unarchiving 694098, fixed 694098 in kfreebsd-10/10.0~svn252032-1
Processing commands for cont...@bugs.debian.org:
unarchive 694098
fixed 694098 kfreebsd-10/10.0~svn252032-1
Bug #694098 {Done: Robert Millan r...@debian.org} [kfreebsd-10] kfreebsd-10:
CVE-2012-4576
Marked as fixed in versions kfreebsd-10/10.0~svn252032-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
694098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694098
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#764196: maildir-utils: FTBFS on arm*
Julien Cristau jcris...@debian.org writes: So I think guile-2.0-dev needs a dependency on gcc-4.8 on those archs. Indeed. I'll fix it shortly. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761040: [libqtwebkit4] Browsers based on Webkit crash on loading pages
Can anyone check is arora suffers from the same bug on ppc? arora is currently using Qt5, but the same webkit codebase, so we would like to know if this is a shared bug or not. -- http://www.tiraecol.net/modules/comic/comic.php?content_id=162 Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#764281: dpkg-source: error: expected ^--- in line 34 of diff
Processing control commands:
forcemerge 764206 -1
Bug #764206 {Done: Guillem Jover guil...@debian.org} [dpkg-dev] dpkg-source:
Broken source unpacking when applying patches
Bug #764206 {Done: Guillem Jover guil...@debian.org} [dpkg-dev] dpkg-source:
Broken source unpacking when applying patches
Marked as found in versions dpkg/1.17.15.
Bug #764281 [dpkg-dev] dpkg-source: error: expected ^--- in line 34 of diff
Severity set to 'serious' from 'normal'
Marked Bug as done
Marked as fixed in versions dpkg/1.17.16.
Marked as found in versions dpkg/1.17.14.
Merged 764206 764281
--
764206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764206
764281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764281
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#763319: marked as done (Fails unless python-django-longerusername in installed)
Your message dated Tue, 07 Oct 2014 17:04:07 + with message-id e1xbybd-kf...@franck.debian.org and subject line Bug#763319: fixed in lava-server 2014.09-1 has caused the Debian Bug report #763319, regarding Fails unless python-django-longerusername in installed 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.) -- 763319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: lava-server Version: 2014.08.2-1 Severity: grave Hey, See errors below.. Looking at the lava-server.git it seems that the usage of longusername is already on its way out, but not there yet for this version of this package [Mon Sep 29 09:45:57.548969 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] mod_wsgi (pid=1930): Exception occurred processing WSGI script '/etc/lava-server/lava-server.wsgi'. [Mon Sep 29 09:45:57.549139 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] Traceback (most recent call last): [Mon Sep 29 09:45:57.549169 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] File /usr/lib/python2.7/dist-packages/django/core/handlers/wsgi.py, line 187, in __call__ [Mon Sep 29 09:45:57.549312 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] response = self.get_response(request) [Mon Sep 29 09:45:57.549336 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] File /usr/lib/python2.7/dist-packages/django/core/handlers/base.py, line 199, in get_response [Mon Sep 29 09:45:57.549367 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] response = self.handle_uncaught_exception(request, resolver, sys.exc_info()) [Mon Sep 29 09:45:57.549537 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] File /usr/lib/python2.7/dist-packages/django/core/handlers/base.py, line 239, in handle_uncaught_exception [Mon Sep 29 09:45:57.549571 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] if resolver.urlconf_module is None: [Mon Sep 29 09:45:57.549587 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] File /usr/lib/python2.7/dist-packages/django/core/urlresolvers.py, line 361, in urlconf_module [Mon Sep 29 09:45:57.549610 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] self._urlconf_module = import_module(self.urlconf_name) [Mon Sep 29 09:45:57.549637 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] File /usr/lib/python2.7/importlib/__init__.py, line 37, in import_module [Mon Sep 29 09:45:57.549660 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] __import__(name) [Mon Sep 29 09:45:57.549674 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] File /usr/lib/python2.7/dist-packages/lava_server/urls.py, line 23, in module [Mon Sep 29 09:45:57.549696 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] from longerusername.forms import AuthenticationForm [Mon Sep 29 09:45:57.549718 2014] [wsgi:error] [pid 1930] [remote 93.93.130.87:50348] ImportError: No module named longerusername.forms -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: lava-server Source-Version: 2014.09-1 We believe that the bug you reported is fixed in the latest version of lava-server, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 763...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Neil Williams codeh...@debian.org (supplier of updated lava-server package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 01 Oct 2014 14:13:30 +0100 Source: lava-server Binary: lava-server lava lava-dev lava-server-doc Architecture: source all Version: 2014.09-1 Distribution: unstable Urgency: medium Maintainer: Debian LAVA team pkg-linaro-lava-de...@lists.alioth.debian.org Changed-By: Neil Williams
Bug#763310: marked as done (Fails to upgrade from 2014.07.1-1 to 2014.08.2-1)
Your message dated Tue, 07 Oct 2014 17:04:07 +
with message-id e1xbybd-kz...@franck.debian.org
and subject line Bug#763310: fixed in lava-server 2014.09-1
has caused the Debian Bug report #763310,
regarding Fails to upgrade from 2014.07.1-1 to 2014.08.2-1
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.)
--
763310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: lava-server
Version: 2014.08.2-1
Severity: serious
Hey,
Upgrading our server from 2014.07.1-1 to 2014.08.2-1 seems to fail inside the
django migrations:
Preparing to unpack .../lava-server_2014.08.2-1_all.deb ...
[ ok ] Stopping lava-server manage scheduler: lava-daemon.
Unpacking lava-server (2014.08.2-1) over (2014.07.1-1) ...
snip
Setting up lava-server (2014.08.2-1) ...
lavaserver
lavaserver
devel
devel
Operations to perform:
Synchronize unmigrated apps: linaro_django_xmlrpc, django_openid_auth,
lava_projects, lava_scheduler_daemon, django_tables2, lava_markitup
Apply all migrations: sessions, admin, dashboard_app, auth, sites,
contenttypes, lava_scheduler_app, google_analytics
Synchronizing apps without migrations:
Creating tables...
Installing custom SQL...
Installing indexes...
Running migrations:
Applying contenttypes.0001_initial... FAKED
Applying auth.0001_initial... FAKED
Applying admin.0001_initial... FAKED
Applying dashboard_app.0001_initial...Traceback (most recent call last):
File /usr/bin/lava-server, line 9, in module
load_entry_point('lava-server==2014.08.2', 'console_scripts',
'lava-server')()
File /usr/lib/python2.7/dist-packages/lava_server/manage.py, line 125, in
main
run_with_dispatcher_class(LAVAServerDispatcher)
File /usr/lib/python2.7/dist-packages/lava_tool/dispatcher.py, line 45, in
run_with_dispatcher_class
raise cls.run()
File /usr/lib/python2.7/dist-packages/lava/tool/dispatcher.py, line 153, in
run
raise SystemExit(cls().dispatch(args))
File /usr/lib/python2.7/dist-packages/lava/tool/dispatcher.py, line 143, in
dispatch
return command.invoke()
File /usr/lib/python2.7/dist-packages/lava_server/manage.py, line 114, in
invoke
execute_from_command_line(['lava-server'] + self.args.command)
File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py,
line 385, in execute_from_command_line
utility.execute()
File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py,
line 377, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File /usr/lib/python2.7/dist-packages/django/core/management/base.py, line
288, in run_from_argv
self.execute(*args, **options.__dict__)
File /usr/lib/python2.7/dist-packages/django/core/management/base.py, line
338, in execute
output = self.handle(*args, **options)
File /usr/lib/python2.7/dist-packages/django/core/management/base.py, line
533, in handle
return self.handle_noargs(**options)
File
/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py,
line 27, in handle_noargs
call_command(migrate, **options)
File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py,
line 115, in call_command
return klass.execute(*args, **defaults)
File /usr/lib/python2.7/dist-packages/django/core/management/base.py, line
338, in execute
output = self.handle(*args, **options)
File
/usr/lib/python2.7/dist-packages/django/core/management/commands/migrate.py,
line 160, in handle
executor.migrate(targets, plan, fake=options.get(fake, False))
File /usr/lib/python2.7/dist-packages/django/db/migrations/executor.py,
line 63, in migrate
self.apply_migration(migration, fake=fake)
File /usr/lib/python2.7/dist-packages/django/db/migrations/executor.py,
line 97, in apply_migration
migration.apply(project_state, schema_editor)
File /usr/lib/python2.7/dist-packages/django/db/migrations/migration.py,
line 107, in apply
operation.database_forwards(self.app_label, schema_editor, project_state,
new_state)
File
/usr/lib/python2.7/dist-packages/django/db/migrations/operations/models.py,
line 36, in database_forwards
schema_editor.create_model(model)
File /usr/lib/python2.7/dist-packages/django/db/backends/schema.py, line
270, in create_model
self.execute(sql, params)
File /usr/lib/python2.7/dist-packages/django/db/backends/schema.py, line
98, in execute
cursor.execute(sql, params)
File /usr/lib/python2.7/dist-packages/django/db/backends/utils.py, line 65,
in execute
return
Bug#694098: unarchiving 694098, reopening 694098, closing 694098
unarchive 694098 reopen 694098 # trying to mark with fixing version in Debian to have graph showing correct information close 694098 10.0~svn252032-1 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): unarchiving 694098, reopening 694098, closing 694098
Processing commands for cont...@bugs.debian.org:
unarchive 694098
reopen 694098
Bug #694098 {Done: Robert Millan r...@debian.org} [kfreebsd-10] kfreebsd-10:
CVE-2012-4576
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 10.0~svn252032-1, 10.0~svn243419, and
kfreebsd-10/10.0~svn252032-1.
# trying to mark with fixing version in Debian to have graph showing correct
information
close 694098 10.0~svn252032-1
Bug #694098 [kfreebsd-10] kfreebsd-10: CVE-2012-4576
There is no source info for the package 'kfreebsd-10' at version
'10.0~svn252032-1' with architecture ''
Unable to make a source version for version '10.0~svn252032-1'
Marked as fixed in versions 10.0~svn252032-1.
Bug #694098 [kfreebsd-10] kfreebsd-10: CVE-2012-4576
Marked Bug as done
thanks
Stopping processing here.
Please contact me if you need assistance.
--
694098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694098
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#763134: acpi-support-base: /usr/share/acpi-support/power-funcs broken from line 24 if consolekit installed and no dbus running
Hi Michael, Not Thijs here, but I think can also comment on this: On Sun, Oct 05, 2014 at 10:09:51PM +0200, Michael Meskes wrote: On Sun, Oct 05, 2014 at 08:49:46PM +0200, Thijs Kinkhorst wrote: On its own, I would not consider failure to lock the screen in specific situations a high priority issue because of the other consequences of having physical access to a machine. Normally I would suggest to fix the bug through the regular stable update channel. Ok, thanks for the clarification. I absolutely agree, but didn't want to go ahead without asking. However, am I correct that this is a regression in the DSA for acpi-support (0.140-5+deb7u3)? If so, we can fix it through stable security since it's a regression introduced in that channel. Nope, I don't think this is a regression. I'm pretty sure the same problem applies to the original stable version. Given the above and that this was not introduced via a DSA, you can go ahead and ask for an update trough stable-proposed-update. Keep in mind that the window is closing this weekend IIRC. Regards, Salvatore signature.asc Description: Digital signature
Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked
Hello, I think there is a problem with keepnote configuration ($HOME/.config/keepnote/keepnote.xml). If I removed that file, keepnote started successfully. But when I have changed configuration settings (i.e. Edit- Preferences, option Default Notebook Use current notebook) and save it, next start of the application finished with known error (Attempt to unlock mutex that was not locked) -- Regards -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764330: marked as done (libtasn1-doc_4.2-1: trying to overwrite..., which is also in package libtasn1-3-dev 2.13-2)
Your message dated Tue, 07 Oct 2014 17:33:55 + with message-id e1xbye3-0004zi...@franck.debian.org and subject line Bug#764330: fixed in libtasn1-6 4.2-2 has caused the Debian Bug report #764330, regarding libtasn1-doc_4.2-1: trying to overwrite..., which is also in package libtasn1-3-dev 2.13-2 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.) -- 764330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: libtasn1-doc version: 4.2-1 severity: serious Hi, from a test doing wheezy-jessie upgrades (running on jenkins.debian.net) I observed this: On Dienstag, 7. Oktober 2014, jenk...@jenkins.debian.net wrote: See https://jenkins.debian.net/job/chroot-installation_wheezy_install_developer_upgrade_to_jessie/480/ ... Selecting previously unselected package libtasn1-doc. Preparing to unpack .../libtasn1-doc_4.2-1_all.deb ... Unpacking libtasn1-doc (4.2-1) ... dpkg: error processing archive /var/cache/apt/archives/libtasn1-doc_4.2-1_all.deb (--unpack): trying to overwrite '/usr/share/info/libtasn1.info.gz', which is also in package libtasn1-3-dev 2.13-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) ... Errors were encountered while processing: /var/cache/apt/archives/libtasn1-doc_4.2-1_all.deb cheers, Holger signature.asc Description: This is a digitally signed message part. ---End Message--- ---BeginMessage--- Source: libtasn1-6 Source-Version: 4.2-2 We believe that the bug you reported is fixed in the latest version of libtasn1-6, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 764...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler ametz...@debian.org (supplier of updated libtasn1-6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 07 Oct 2014 19:12:52 +0200 Source: libtasn1-6 Binary: libtasn1-6-dev libtasn1-doc libtasn1-6-dbg libtasn1-6 libtasn1-bin libtasn1-3-bin Architecture: source i386 all Version: 4.2-2 Distribution: unstable Urgency: medium Maintainer: Debian GnuTLS Maintainers pkg-gnutls-ma...@lists.alioth.debian.org Changed-By: Andreas Metzler ametz...@debian.org Description: libtasn1-3-bin - transitional libtasn1-3-bin package libtasn1-6 - Manage ASN.1 structures (runtime) libtasn1-6-dbg - Manage ASN.1 structures (debugging symbols) libtasn1-6-dev - Manage ASN.1 structures (development) libtasn1-bin - Manage ASN.1 structures (binaries) libtasn1-doc - Manage ASN.1 structures (documentation) Closes: 764330 Changes: libtasn1-6 (4.2-2) unstable; urgency=medium . * libtasn1-doc also needs to have a versioned Breaks/Replaces against libtasn1-3-dev, since that package also used to include the docs. Closes: #764330 * Build with --disable-silent-rules. Checksums-Sha1: b82841190bb985c3d120a1b0315f07815e656744 2406 libtasn1-6_4.2-2.dsc 40fc50b28ad249c1e8ecc4b30a0081e9630e9f02 56720 libtasn1-6_4.2-2.debian.tar.xz 4ab15c6df66715a8f7a6047ccffd566b217328f1 90934 libtasn1-6-dev_4.2-2_i386.deb 8d0b268724a111aaba106cf8e55cc503f46d49c7 305008 libtasn1-doc_4.2-2_all.deb 4612982e559ac4ebbcc2600151485fd210f54266 90420 libtasn1-6-dbg_4.2-2_i386.deb 5a0d37b0bfa8d0380dadbd11132f7b5e13f398d9 50542 libtasn1-6_4.2-2_i386.deb 1346b22010d61c44f11a3c4c51cf2e054a98a704 22634 libtasn1-bin_4.2-2_i386.deb cb400a5f20a7ad99afd941ef81ab462ba01a09a8 9688 libtasn1-3-bin_4.2-2_all.deb Checksums-Sha256: ba4217afd707f120a939e5ed36a1bed9a4aa025d7b2c51b24660089e6a3b749c 2406 libtasn1-6_4.2-2.dsc b8ef6d02492cf7cd1a20558222c9296afeae0ea15e4d643649e4d19e8ab8790d 56720 libtasn1-6_4.2-2.debian.tar.xz 83adc74c6687652063151c1c253530a707907a375f17ee879e0ff2402aa4ef9a 90934 libtasn1-6-dev_4.2-2_i386.deb d044391c780e20e5d9eb04347f4364cb6281a9831ecae18d88005731dde9b83b 305008 libtasn1-doc_4.2-2_all.deb 59f782a2a590646c43a0c354d9f8de4022afe11a7c665e05684e629adc2d9a46 90420 libtasn1-6-dbg_4.2-2_i386.deb 1d822dfa18851c21ec43bed56c6607839b5128213e62f89d59bbdfb0453ff583 50542 libtasn1-6_4.2-2_i386.deb b147118a2ba1d67399d50e123a8b90ac8f28a83768ee144e435d4b315aa9b95f 22634
Processed: tagging 759559
Processing commands for cont...@bugs.debian.org: tags 759559 + security Bug #759559 [libpam-script] libpam-script: (root) login without password Added tag(s) security. thanks Stopping processing here. Please contact me if you need assistance. -- 759559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759559 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#720517: configuration files, ownership and dpkg-statoverride
On 07-10-14 15:40, Ian Jackson wrote: Also I don't see in your references an explanation from anyone as to why dbconfig-common does this. I you mean with why: why is it implemented this way than that is exactly the question that I am asking myself looking at the code, if you mean why does dbconfig-common change the ownership of cactis configuration file than the answer is that you can tell dbconfig-common in your maintainer scripts what the (I expected initial) ownership should be. dbconfig-common than sets the ownership on every update of the package where it is called, except when dpkg-statoverride is set. I am trying to come up with a patch against dpkg-statoverride that sets the ownership and permissions upon creation, but not upon updates. Paul signature.asc Description: OpenPGP digital signature
Bug#759720: marked as done (initramfs boot fails after unlocking encrypted root lv)
Your message dated Tue, 07 Oct 2014 18:03:44 +
with message-id e1xbz6u-0007xv...@franck.debian.org
and subject line Bug#759720: fixed in cryptsetup 2:1.6.6-2
has caused the Debian Bug report #759720,
regarding initramfs boot fails after unlocking encrypted root lv
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.)
--
759720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: cryptsetup
Version: 2:1.4.3-4
Severity: serious
Tags: patch
[Rationale for severity serious: renders system unbootable]
I recently upgraded a Thecus n2100 from squeeze to wheezy [better late
than never!]. It's a headless system; the root filesystem is a logical
volume on LVM over an encrypted physical volume. I use dropbear to ssh
into the system at initramfs stage and unlock the encrypted PV, as
described in /usr/share/doc/cryptsetup/README.remote.gz.
After completing the upgrade and installing a new kernel version, I
rebooted the system. Although it was possible to log in remotely to
initramfs via ssh and successfully unlock encrypted root filesystem,
the system did not proceed to mount the root FS and boot.
Judging by the output of ps, a rescue shell is started after I unlock
the encrypted volume. There is no terminal connected to the system, so
I couldn't actually interact with the rescue shell, but grepping
through the rescue shell's environment gives:
REASON=ALERT! /dev/ram0 does not exist. Dropping to a shell!
Before unlocking encrypted device, /conf/param.conf contains
ROOT=/dev/mapper/name-of-root-lv line pointing to the correct root
device; after unlocking it contains *two* ROOT lines, the original,
correct line and a second, incorrect line (ROOT=/dev/ram0). I think
this second line is causing the subsequent boot process to fail.
It seems that the second line is put there by this part of
/usr/share/initramfs-tools/scripts/local-top/cryptroot after unlocking
the encrypted volume:
,[ /usr/share/initramfs-tools/scripts/local-top/cryptroot ]
| NEWROOT=${cmdline_root:-/dev/mapper/$cryptlvm}
| if [ $cryptrootdev = yes ]; then
| # required for lilo to find the root device
| echo ROOT=$NEWROOT /conf/param.conf
| fi
| eval $(fstype $NEWROOT)
`
The first, correct ROOT line is put there by flash-kernel: The n2100
uses redboot as a bootloader; redboot loads a kernel image and an
initramfs image from flash; in Debian, the flash-kernel package
automates the process of writing the kernel and the initramfs image to
flash; flash-kernel has explicit support for the n2100.
Because redboot passes the kernel bogus root parameter
[root=/dev/ram0], flash-kernel includes an initramfs-tools hook to
write the correct root device to /conf/param.conf when building the
initramfs image:
,[ /usr/share/initramfs-tools/hooks/flash_kernel_set_root ]
| # Should we override the root device or merely provide a default root
| # device?
| blsr=$(get_machine_field $machine Bootloader-sets-root)
|
| if [ $blsr = no ]; then
| # The boot loader doesn't pass root= on the command line, so
| # provide a default.
| install -d $DESTDIR/conf/conf.d
| echo ROOT=\$rootdev\ $DESTDIR/conf/conf.d/default_root
| else
| # The boot loader passes a bogus root= (e.g. root=/dev/ram), so
| # override the command line parameter.
| install -d $DESTDIR/conf
| echo ROOT=\$rootdev\ $DESTDIR/conf/param.conf
| fi
`
The quoted section of local-top/cryptoroot causes a bogus second
ROOT= entry (the bogus root=/dev/ram0 from the command line) to be
written to /conf/param.conf. This prevents boot process from
continuing correctly.
This problem is present both in the version of cryptsetup in wheezy,
and in the version in wheezy-backports (2:1.6.4-4~bpo70+1). I haven't
tested it, but I'm guessing the version in jessie is also affected.
I imagine that other system which use flash-kernel, with
Bootloader-sets-root=yes, would also be affected if they use root on a
LV over an encrypted device.
I attach a patch which fixes the issue for me, it could probably do
with further testing. The patch is against the version of cryptsetup in
wheezy-backports.
--- debian/initramfs/cryptroot-script.orig
+++ debian/initramfs/cryptroot-script
@@ -297,10 +297,15 @@
return 1
fi
- NEWROOT=${cmdline_root:-/dev/mapper/$cryptlvm}
- if [ $cryptrootdev = yes ]; then
-# required for lilo
Bug#764353: libhdf4: FTBFS on s390x and ppc64el: test failures
I'm aware of the issues. I've asked for porter access to see if I can fix these problems. Johan On Tue, Oct 7, 2014 at 2:54 PM, Rebecca Palmer rebecca_pal...@zoho.com wrote: Source: libhdf4 Severity: serious Version: 4.2.10-2 libhdf4 FTBFS in the (newly enabled) test suite on s390x and ppc64el. On s390x, the test setup program crashes: https://buildd.debian.org/status/fetch.php?pkg=libhdf4arch=s390xver=4.2.10-2stamp=1412545742 === HDF Library Fortran Interface Tests Setup === *** Error in `/«PKGBUILDDIR»/HDF4.2.10/hdf/test/.libs/lt-fortestF': free(): invalid next size (fast): 0xafeb3fd0 *** Program received signal SIGABRT: Process abort signal. Backtrace for this error: #0 0x3FFFD066C57 #1 0x3FFFD0673B5 #2 0x39721F3 #3 0x3FFFCE3340C #4 0x3FFFCE34A0D #5 0x3FFFCE7D491 #6 0x3FFFCE83EFD #7 0x3FFFCE84ED3 #8 0x3FFFD2A38B1 #9 0x3FFFD2A41FD #10 0x80007DB5 in MAIN__ at fortestF.f:? Aborted On ppc64el, The testsuite went in a loop, so the log is too big to be sent (12GB). Aurelien ___ Pkg-grass-devel mailing list pkg-grass-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764061: Totally uninstallable
On Mon, 06 Oct 2014, +00:04:01 EEST (UTC +0300), Hilmar Preuße hill...@web.de pressed some keys: Can you freshly install the package now (after removal)? Yes. I suspect I got corrupted file when I first time tried installation. -- Juhapekka naula Tolvanen * http colon slash slash iki dot fi slash juhtolv Quidquid Latine dictum sit altum videtur. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): unarchiving 694098, reassign 694098 to src:kfreebsd-10, found 694098 in 10.0~svn232747-1 ...
Processing commands for cont...@bugs.debian.org:
unarchive 694098
reassign 694098 src:kfreebsd-10
Bug #694098 {Done: Salvatore Bonaccorso car...@debian.org} [kfreebsd-10]
kfreebsd-10: CVE-2012-4576
Bug reassigned from package 'kfreebsd-10' to 'src:kfreebsd-10'.
No longer marked as found in versions 10.0~svn232747-1.
No longer marked as fixed in versions 10.0~svn252032-1.
found 694098 10.0~svn232747-1
Bug #694098 {Done: Salvatore Bonaccorso car...@debian.org} [src:kfreebsd-10]
kfreebsd-10: CVE-2012-4576
Marked as found in versions kfreebsd-10/10.0~svn232747-1 and reopened.
fixed 694098 10.0~svn252032-1
Bug #694098 [src:kfreebsd-10] kfreebsd-10: CVE-2012-4576
Marked as fixed in versions kfreebsd-10/10.0~svn252032-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
694098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694098
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#764386: libefivar0: Segmentation fault in vars_get_variable() (vars.c:165)
Package: libefivar0 Version: 0.12-1 Severity: critical Justification: breaks the whole system Upgrading libefivar0 from version 0.10-5 to 0.12-1 causes a segmentation fault when running efibootmgr without arguments (I tried it with both efibootmgr 0.7.0-2 and 0.9.0-1). I'm not quite sure if severity critical is justified, but I think a broken efibootmgr is at least potentially able to break the whole system. gdb pointed to libefivar.so.0 which has no debugging symbols, so I built my own and that one crashes in vars.c line 165 with var == NULL. The last two lines in an strace log before the crash are open(/sys/firmware/efi/vars/Boot0005-8be4[...]/raw_var, O_RDONLY) = 3 read(3, [...], 4096) = -1 EIO (Input/output error) (Sorry, no copypaste, just readtype; the system in question has only very limited network connectivity at the moment and I'm sending this report from a different system.) var is apparently returned from a call to read_file() a few lines above. The source code history shows that read_fd() has recently been replaced by read_file(), but they behave differently after read errors. In particular, read_file() resets the buffer to NULL whereas read_fd() didn't. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694098: marked as done (kfreebsd-10: CVE-2012-4576)
Your message dated Tue, 07 Oct 2014 19:55:58 +0100 with message-id 5434373e.4060...@pyro.eu.org and subject line Re: Bug#694098: kfreebsd-10: CVE-2012-4576 has caused the Debian Bug report #694098, regarding kfreebsd-10: CVE-2012-4576 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.) -- 694098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: kfreebsd-10 severity: serious version: 10.0~svn232747-1 Hi, a security advisory was issued for freebsd, and kfreebsd-10 is affected: http://lists.freebsd.org/pipermail/freebsd-announce/2012-November/001440.html ---End Message--- ---BeginMessage--- Source-Version: 10.0~svn252032-1---End Message---
Bug#746013: libmatheval: diff for NMU version 1.1.11+dfsg-1.2
On 07.10.2014 16:21, Neil Williams wrote: Control: tags 746013 + pending Dear maintainer, I've prepared an NMU for libmatheval (versioned as 1.1.11+dfsg-1.2) and uploaded it to unstable with a fix for the compiler optimisation effects. This diff extends the previous diff for i386 support. Regards. please upload such hacky patches to delayed so I can override it with something proper if I find the time... the rounding issue can be solved much simpler by using appropriate C types or putting an error on the tests. Also you shouldn't just add a new debian specific symbol to a library ... (or was this forwarded upstream?) but still thanks for handling the issue which I have been neglecting for too long. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763780: This is CVE-2014-7206.
This is CVE-2014-7206. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: user debian-secur...@lists.debian.org, usertagging 763780 ...
Processing commands for cont...@bugs.debian.org:
user debian-secur...@lists.debian.org
Setting user to debian-secur...@lists.debian.org (was car...@debian.org).
usertags 763780 + tracked
Usertags were: tracked.
Usertags are now: tracked.
retitle 763780 apt-get: CVE-2014-7206: Insecure temporary changelog handling
Bug #763780 {Done: Michael Vogt m...@debian.org} [apt] apt-get: Insecure
temporary changelog handling
Changed Bug title to 'apt-get: CVE-2014-7206: Insecure temporary changelog
handling' from 'apt-get: Insecure temporary changelog handling'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
763780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763780
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
