Bug#764570: taskcoach: fail to start: wx._core.PyAssertionError
Package: taskcoach Version: 1.4.1-2 Severity: grave Justification: renders package unusable The last update wasn't that successful. :-( $ taskcoach (taskcoach:9934): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height = -1' failed Traceback (most recent call last): File /usr/bin/taskcoach, line 72, in module start() File /usr/bin/taskcoach, line 63, in start app = application.Application(options, args) File /usr/lib/python2.7/dist-packages/taskcoachlib/patterns/singleton.py, line 29, in __call__ class_.instance = super(Singleton, class_).__call__(*args, **kwargs) File /usr/lib/python2.7/dist-packages/taskcoachlib/application/application.py, line 117, in __init__ self.init(**kwargs) File /usr/lib/python2.7/dist-packages/taskcoachlib/application/application.py, line 226, in init self.settings, splash=splash) File /usr/lib/python2.7/dist-packages/taskcoachlib/gui/mainwindow.py, line 68, in __init__ self._create_window_components() # Not private for test purposes File /usr/lib/python2.7/dist-packages/taskcoachlib/gui/mainwindow.py, line 140, in _create_window_components viewer.addViewers(self.viewer, self.taskFile, self.settings) File /usr/lib/python2.7/dist-packages/taskcoachlib/gui/viewer/factory.py, line 45, in __init__ self.__add_all_viewers() File /usr/lib/python2.7/dist-packages/taskcoachlib/gui/viewer/factory.py, line 51, in __add_all_viewers self.__add_viewers(task.SquareTaskViewer) File /usr/lib/python2.7/dist-packages/taskcoachlib/gui/viewer/factory.py, line 66, in __add_viewers **self._viewer_kwargs(viewer_class)) File /usr/lib/python2.7/dist-packages/taskcoachlib/patterns/metaclass.py, line 39, in __call__ instance = super(NumberedInstances, cls).__call__(*args, **kwargs) File /usr/lib/python2.7/dist-packages/taskcoachlib/gui/viewer/task.py, line 464, in __init__ super(SquareTaskViewer, self).__init__(*args, **kwargs) File /usr/lib/python2.7/dist-packages/taskcoachlib/gui/viewer/task.py, line 136, in __init__ super(BaseTaskTreeViewer, self).__init__(*args, **kwargs) File /usr/lib/python2.7/dist-packages/taskcoachlib/gui/viewer/task.py, line 77, in __init__ super(BaseTaskViewer, self).__init__(*args, **kwargs) File /usr/lib/python2.7/dist-packages/taskcoachlib/gui/viewer/mixin.py, line 85, in __init__ super(FilterableViewerMixin, self).__init__(*args, **kwargs) File /usr/lib/python2.7/dist-packages/taskcoachlib/gui/viewer/base.py, line 583, in __init__ super(TreeViewer, self).__init__(*args, **kwargs) File /usr/lib/python2.7/dist-packages/taskcoachlib/gui/viewer/base.py, line 70, in __init__ pub.subscribe(self.onBeginIO, 'taskfile.aboutToRead') File /usr/lib/python2.7/dist-packages/taskcoachlib/thirdparty/pubsub/core/publisherbase.py, line 143, in subscribe topicObj = self.__topicMgr.getOrCreateTopic(topicName) File /usr/lib/python2.7/dist-packages/taskcoachlib/thirdparty/pubsub/core/topicmgr.py, line 206, in getOrCreateTopic if obj: wx._core.PyAssertionError: C++ assertion m_window failed at ../src/gtk/dcclient.cpp(2043) in DoGetSize(): GetSize() doesn't work without window -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages taskcoach depends on: ii fonts-dejavu 2.34-1 ii libxss1 1:1.2.2-1 ii python 2.7.8-1 ii python-chardet 2.2.1-2 ii python-dateutil 1.5+dfsg-1 ii python-keyring 3.7-1 ii python-lockfile 1:0.8-2 ii python-pyparsing 2.0.2+dfsg1-1 ii python-squaremap 1:1.0.4-2 ii python-twisted-core 14.0.2-2 ii python-wxgtk3.0 3.0.1.1+dfsg-1 ii python-wxversion 2.8.12.1+dfsg2-1 ii python-xdg 0.25-4 ii x11-utils7.7+1 Versions of packages taskcoach recommends: ii libavahi-compat-libdnssd1 0.6.31-4 ii libgnome-2-0 2.32.1-5 ii python-notify 0.1.1-3 Versions of packages taskcoach suggests: pn espeak none pn python-kde4 none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764571: libpoclu-dev and uthash-dev: error when trying to install together
Package: uthash-dev,libpoclu-dev Version: uthash-dev/1.9.7-1 Version: libpoclu-dev/0.10-3 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-10-09 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 ocl-icd-libopencl1:amd64. (Reading database ... 10872 files and directories currently installed.) Preparing to unpack .../ocl-icd-libopencl1_2.2.3-1_amd64.deb ... Unpacking ocl-icd-libopencl1:amd64 (2.2.3-1) ... Selecting previously unselected package libpoclu1:amd64. Preparing to unpack .../libpoclu1_0.10-3_amd64.deb ... Unpacking libpoclu1:amd64 (0.10-3) ... Selecting previously unselected package opencl-headers. Preparing to unpack .../opencl-headers_1.2-2014.04.13-1.1_all.deb ... Unpacking opencl-headers (1.2-2014.04.13-1.1) ... Selecting previously unselected package libpoclu-dev. Preparing to unpack .../libpoclu-dev_0.10-3_amd64.deb ... Unpacking libpoclu-dev (0.10-3) ... Selecting previously unselected package uthash-dev. Preparing to unpack .../uthash-dev_1.9.7-1_all.deb ... Unpacking uthash-dev (1.9.7-1) ... dpkg: error processing archive /var/cache/apt/archives/uthash-dev_1.9.7-1_all.deb (--unpack): trying to overwrite '/usr/include/utlist.h', which is also in package libpoclu-dev 0.10-3 Processing triggers for man-db (2.7.0.2-1) ... Errors were encountered while processing: /var/cache/apt/archives/uthash-dev_1.9.7-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) cow-shell unlink .ilist: No such file or directory 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/include/utlist.h 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#764547: bsdutils: script(1) is broken, hangs or crashes
Hello Thorsten Glaser! On Thu, Oct 09, 2014 at 12:52:29AM +0200, Thorsten Glaser wrote: Package: bsdutils Version: 1:2.25.1-3 Severity: serious Tags: upstream Justification: crashes Forwarded: http://thread.gmane.org/gmane.linux.utilities.util-linux-ng/1 Thanks for forwarding your issue upstream. Lets try to work it out ourselfs as well though... Hi, as I reported upstream in http://article.gmane.org/gmane.linux.utilities.util-linux-ng/1 the script(1) in util-linux 2.25.1 is broken, whereas the one in util-linux 2.20.1 as currently in jessie works fine. This applies to both my x32 regular machine as well as a clean, minimal amd64 and i386 cowbuilder sid chroot, as well as the OpenSuSE Buildservice setup. Since you seem to have a way to reproduce the problem, could you please also git bisect it? This bug opened in Debian to prevent a crashing script(1) from migrating to testing, and to track progress. (I don't see this as anything else then just yet another bug in script. I don't understand why your issue would be more important then getting 200 other issues fixed for other people.) Regards, Andreas Henriksson -- 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 09-10-14 02:17, Henrique de Moraes Holschuh wrote: On Wed, 08 Oct 2014, Paul Gevers wrote: Thanks for the careful response. And no, as mentioned above, I didn't mean to use dpkg-statoverride itself. dbconfig-common uses debconf and ufc to manage the configuration files. However, dbconfig-common checks with dpkg-statoverride if the configuration file is registered there and takes action if it is. However, currently it relies only on dpkg-statoverride to know if the ownership of the configuration file should be different, I want dbconfig-common to leave the ownership as it is if the file already exists. It looks like your problem is the situation where you have dpkg-statoverride information and it contradicts whatever is in debconf (or the filesystem, for that matter)? Actually, I was really thinking about the situation where dpkg-statoverride AND debconf were NOT used. dbconfig-common allows a package to specify the ownership and permissions of the configuration file. The package may or may not do this via debconf (cacti currently does not). If a local admin decides that the ownership and/or permissions need to be different dbconfig-common should honor that when updating the package. Until know (hence RC) dbconfig-common changed the ownership and permissions unconditionally to the ownership and permissions requested by the package (unless dpkg-statoverride was used by the admin), which may not be what the admin wants (and as you state below may not reflect the situation). In that case, it is an operator error: I suggest you inform him about it and refuse to continue. There's no other safe choice in the general case, AFAIK. But this indeed is a good idea. Lots more logic to add, but indeed. Annoying thing is that the script that actually does the file writing may be called manually as well. Let me ponder on this some time. Of course, it might happen that you have specific knowledge (such as you know the dpkg-statoverride information was added in error by a previous version of the package _and_ the information in the statoverride database exactly matches the one the bug would have caused) which allows you to automatically repair the problem, instead. Sure, but AFAICT that is not the case here. And if we're talking about an initial question (i.e. there is no conflict because there's nothing in the debconf database yet), then wouldn't using the dpkg-statoverride information as a pre-seed _and_ not allowing it to be overriden through debconf (i.e. don't ask the user about it at all) solve the issue? Not applicable for the bug at hand, because there never was a question to the user. Just hard-coding in the package, which I think is acceptable, as well as it should be acceptable that the package leaves it to dbconfig-common to just do-the-right-thing in this case. Paul signature.asc Description: OpenPGP digital signature
Bug#755207: marked as done (valadoc: Upcoming vala-0.16 removal)
Your message dated Thu, 09 Oct 2014 07:00:07 + with message-id e1xc7hn-0006j8...@franck.debian.org and subject line Bug#755207: fixed in valadoc 0.23.2~git20140902-1 has caused the Debian Bug report #755207, regarding valadoc: Upcoming vala-0.16 removal 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.) -- 755207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: valadoc Severity: important User: pkg-vala-maintain...@lists.alioth.debian.org Usertags: oldlibs vala-0.16-removal Hi, valadoc build-depends on vala-0.16, which is pretty old and we would like to remove. You should instead use the much newer valac-0.24, or preferably the unversioned 'valac' package. Emilio ---End Message--- ---BeginMessage--- Source: valadoc Source-Version: 0.23.2~git20140902-1 We believe that the bug you reported is fixed in the latest version of valadoc, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Reichel s...@debian.org (supplier of updated valadoc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 07 Sep 2014 22:29:40 +0200 Source: valadoc Binary: valadoc libvaladoc3 libvaladoc-data libvaladoc-dev Architecture: source amd64 all Version: 0.23.2~git20140902-1 Distribution: unstable Urgency: low Maintainer: Sebastian Reichel s...@debian.org Changed-By: Sebastian Reichel s...@debian.org Description: libvaladoc-data - API documentation generator for vala (data) libvaladoc-dev - API documentation generator for vala (devel files) libvaladoc3 - API documentation generator for vala (library) valadoc- API documentation generator for vala Closes: 755207 Changes: valadoc (0.23.2~git20140902-1) unstable; urgency=low . * new upstream snapshot - support for gtkdoc markdown parser * Drop support for vala 0.16 (Closes: #755207) Checksums-Sha1: 0c4e471d4b4002d1be93f178757f3e43b039198c 2245 valadoc_0.23.2~git20140902-1.dsc 713087e813167b57f9b1ce30b975f71cadfe9aa2 250435 valadoc_0.23.2~git20140902.orig.tar.gz 62bd22034315bbf8065062c1a2964b73caac3997 9052 valadoc_0.23.2~git20140902-1.debian.tar.xz 599cea1d34f77625893f93cff4c4dcbdd2a87694 97402 valadoc_0.23.2~git20140902-1_amd64.deb fe520d63a94747e1fcf8ad4b36db6f9ec4b0631e 271624 libvaladoc3_0.23.2~git20140902-1_amd64.deb 7a1e671c86000a6ab4b44a35519cc29a50a9bda5 24516 libvaladoc-data_0.23.2~git20140902-1_all.deb 64594e54243bf4443d217dd775e0f17fbf0d6895 35270 libvaladoc-dev_0.23.2~git20140902-1_amd64.deb Checksums-Sha256: db81bb17fb9acba22ddec6634879dedec9b6331dffd9020c30b176aa0e02d1ec 2245 valadoc_0.23.2~git20140902-1.dsc 3a2f0d1af1a4d08ea1628677781d7b6ca0261a4b82a24a50ecb02b98df2b0a58 250435 valadoc_0.23.2~git20140902.orig.tar.gz ffd359b01e7ceaa82d61c084a1e26f27c7a870343f2fb2b462f32f143ceef1d6 9052 valadoc_0.23.2~git20140902-1.debian.tar.xz 7ee326f6d1d658d201f02b5bbcd99a6df6b54f686e1bffdede41b35805fea3a6 97402 valadoc_0.23.2~git20140902-1_amd64.deb f536b74c3c8428813dc3876991895b7e54665aa506bf6fc0c00ca0c52cfc9467 271624 libvaladoc3_0.23.2~git20140902-1_amd64.deb a66b7c4e8d34a18c2a577a9529f96160327938ed74f81e3062c60a516ea73610 24516 libvaladoc-data_0.23.2~git20140902-1_all.deb bf97b6ab08e399b94ec6507a3a4c46aa21820ae83537706a584763384e9d25e8 35270 libvaladoc-dev_0.23.2~git20140902-1_amd64.deb Files: 14a347bcc1c6ebf3ea415b3dba510bf9 97402 devel extra valadoc_0.23.2~git20140902-1_amd64.deb ced310bc5188f41062e28d35e8f1f4d8 271624 libs extra libvaladoc3_0.23.2~git20140902-1_amd64.deb e08005c366ad490d817eedc5a26e732e 24516 misc extra libvaladoc-data_0.23.2~git20140902-1_all.deb ae1447d93d14b71918c83499af5c8998 35270 libdevel extra libvaladoc-dev_0.23.2~git20140902-1_amd64.deb addc003864abffadc4fbea7cd26c1c47 2245 devel extra valadoc_0.23.2~git20140902-1.dsc 334ddbf6323bcbba9b5c6e16d2d7cd41 250435 devel extra valadoc_0.23.2~git20140902.orig.tar.gz 6197e3c17fc949e5ee6b8f0743ce0846 9052 devel extra valadoc_0.23.2~git20140902-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12
Processed: Re: wagon2 fails to build in a non networked environment
Processing commands for cont...@bugs.debian.org: tags 761171 patch Bug #761171 [src:wagon2] wagon2 fails to build in a non networked environment Added tag(s) patch. End of message, stopping processing here. Please contact me if you need assistance. -- 761171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761171 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#764571: libpoclu-dev and uthash-dev: error when trying to install together
Hi, On 09/10/2014 08:28, Ralf Treinen wrote: Package: uthash-dev,libpoclu-dev Version: uthash-dev/1.9.7-1 Version: libpoclu-dev/0.10-3 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Thank for the report. I think (I will check) that this is the same file. I did not know that this header was already packaged. I will remove it from libpoclu-dev and add a dependency. Regards, Vincent Date: 2014-10-09 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 ocl-icd-libopencl1:amd64. (Reading database ... 10872 files and directories currently installed.) Preparing to unpack .../ocl-icd-libopencl1_2.2.3-1_amd64.deb ... Unpacking ocl-icd-libopencl1:amd64 (2.2.3-1) ... Selecting previously unselected package libpoclu1:amd64. Preparing to unpack .../libpoclu1_0.10-3_amd64.deb ... Unpacking libpoclu1:amd64 (0.10-3) ... Selecting previously unselected package opencl-headers. Preparing to unpack .../opencl-headers_1.2-2014.04.13-1.1_all.deb ... Unpacking opencl-headers (1.2-2014.04.13-1.1) ... Selecting previously unselected package libpoclu-dev. Preparing to unpack .../libpoclu-dev_0.10-3_amd64.deb ... Unpacking libpoclu-dev (0.10-3) ... Selecting previously unselected package uthash-dev. Preparing to unpack .../uthash-dev_1.9.7-1_all.deb ... Unpacking uthash-dev (1.9.7-1) ... dpkg: error processing archive /var/cache/apt/archives/uthash-dev_1.9.7-1_all.deb (--unpack): trying to overwrite '/usr/include/utlist.h', which is also in package libpoclu-dev 0.10-3 Processing triggers for man-db (2.7.0.2-1) ... Errors were encountered while processing: /var/cache/apt/archives/uthash-dev_1.9.7-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) cow-shell unlink .ilist: No such file or directory 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/include/utlist.h 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/. -- Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764561: Bug#764563: pocl: FTBFS: test suite errors and FTBFS on ppc64el
Hi, On 09/10/2014 04:57, Aaron M. Ucko wrote: Source: pocl Version: 0.10-3 Severity: serious Justification: fails to build from source The builds of pocl for i386 and (32-bit) powerpc both failed with test suite errors: three unexpected failures on i386 and 80 (!) on powerpc. Could you please take a look? You can find the full logs at https://buildd.debian.org/status/logs.php?pkg=poclver=0.10-3suite=sid (So far, most of the remaining failures were due to pocl's configure script rejecting the architecture as unsupported; you might want to tighten its architecture field in debian/control accordingly.) Thank for your report. As pocl is a new package, do you really think it deserve a serious bug (that block migration to testing?) Upstream is really interested on the results (they cannot test pocl on all Debian architecture before) but if bugs are filled with a serious severity I will immediately completely disable non standard architectures in order to allow pocl in jessie (and the work to try to support other architectures will be done after jessie release instead of before the freeze). Regards, Vincent Thanks! -- Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- 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
Hi sorry for my late reply - though being listed as a maintainer for the libcerf package I did not recieve a mail from the Debian bug tracker. I am quite new to the Debian packaging world - so most probably I did something wrong or forgot to regsiter somewher. Anyhow ... On Tue, 7 Oct 2014 22:51:50 +0200 Simon Paillard spaill...@debian.org wrote: Hi, On Tue, Oct 07, 2014 at 08:38:03AM +0200, Ralf Treinen wrote: 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 Thanks for the report ! Indeed - yes - thanks for the report. [...] Several facts: * both cerf.3 and cerfc.3 are already provided in manpages debian package since 10 years before libcerf upload in June 2014 * the function names are reserved for future use in C99. Options: * rename cerf functions and manpages of libcerf (avoid use of reserved names) or * manpages-dev to stop installing cerf.3 and cerfc.3 manpages * anyway, Michael, if you read me, I suggest you mention libcerf in the cerf* manpages. Just now I informed the upstream maintainers of libcerf about this. I am pretty sure they simply where not aware of the fact that these functions are already mentioned in the C99 standard. I am just not sure if they manage to change the upstream code in time to make it until the freeze of Jessie. I have not found cerf and cerfc in the documentation for glibc 2.20 so I assume that these functions would not be provided by the glibc version shipped with Jessie. Hence, I suggest to remove cerf.3 and cerfc.3 from manpages-dev as long as glibc does not provide this functionality. I am very well aware of the fact that this looks a bit like makeing this a sombody else's problem. However, in my opinion manpages of a package providing a particular functionality should have precedence. In any case this can only be an intermediate solution until upstream has renamed the functions. regards Eugen -- Simon Paillard signature.asc Description: This is a digitally signed message part
Processed: clone issue to track in binutils
Processing commands for cont...@bugs.debian.org: clone 763228 -1 Bug #763228 [src:cbmc] cbmc: FTBFS: ld: final link failed: Bad value Bug 763228 cloned as bug 764573 severity -1 important Bug #764573 [src:cbmc] cbmc: FTBFS: ld: final link failed: Bad value Severity set to 'important' from 'serious' reassign -1 src:binutils Bug #764573 [src:cbmc] cbmc: FTBFS: ld: final link failed: Bad value Bug reassigned from package 'src:cbmc' to 'src:binutils'. Ignoring request to alter found versions of bug #764573 to the same values previously set Ignoring request to alter fixed versions of bug #764573 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 763228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763228 764573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764573 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#764568: cheese: program dies with Attempt to unlock mutex that was not locked
Version: 3.14.0-1 Control: severity -1 grave On 08/10/14 19:20, Norbert Gruener wrote: Package: cheese Version: 3.12.2-1 Severity: critical Dear Maintainer, the program cheese dies with the following message norbert@norbert-tuxedo:~ $ cheese Attempt to unlock mutex that was not locked Aborted It is the same problem as in querybts, reportbug, and others ... I can reproduce it with 3.12.2-1 but not with cheese 3.14.0-1. So let's mark it as fixed in 3.14. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764568: marked as done (cheese: program dies with Attempt to unlock mutex that was not locked)
Your message dated Thu, 09 Oct 2014 10:08:32 +0200 with message-id 54364280.9010...@debian.org and subject line Re: Bug#764568: cheese: program dies with Attempt to unlock mutex that was not locked has caused the Debian Bug report #764568, regarding cheese: program dies with Attempt to unlock mutex that was not locked 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.) -- 764568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cheese Version: 3.12.2-1 Severity: critical Dear Maintainer, the program cheese dies with the following message norbert@norbert-tuxedo:~ $ cheese Attempt to unlock mutex that was not locked Aborted It is the same problem as in querybts, reportbug, and others ... -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cheese depends on: ii cheese-common 3.12.2-1 ii gnome-video-effects0.4.1-1 ii libc6 2.19-1 ii libcanberra-gtk3-0 0.30-2 ii libcheese-gtk233.12.2-1 ii libcheese7 3.12.2-1 ii libclutter-1.0-0 1.18.2-2 ii libclutter-gtk-1.0-0 1.5.2-2 ii libgdk-pixbuf2.0-0 2.30.8-1+b1 ii libglib2.0-0 2.42.0-2 ii libgnome-desktop-3-10 3.14.0-1 ii libgstreamer1.0-0 1.2.4-1 ii libgtk-3-0 3.12.2-3+b1 Versions of packages cheese recommends: ii gnome-icon-theme3.12.0-1 ii gvfs1.20.1-1 ii hicolor-icon-theme 0.13-1 ii nautilus-sendto 3.8.1-1+b1 ii yelp3.12.0-1 Versions of packages cheese suggests: pn gnome-video-effects-frei0r none -- no debconf information Cheers, Norbert -- Norbert Grüner ---End Message--- ---BeginMessage--- Version: 3.14.0-1 Control: severity -1 grave On 08/10/14 19:20, Norbert Gruener wrote: Package: cheese Version: 3.12.2-1 Severity: critical Dear Maintainer, the program cheese dies with the following message norbert@norbert-tuxedo:~ $ cheese Attempt to unlock mutex that was not locked Aborted It is the same problem as in querybts, reportbug, and others ... I can reproduce it with 3.12.2-1 but not with cheese 3.14.0-1. So let's mark it as fixed in 3.14. Emilio---End Message---
Processed: Re: Bug#764568: cheese: program dies with Attempt to unlock mutex that was not locked
Processing control commands: severity -1 grave Bug #764568 [cheese] cheese: program dies with Attempt to unlock mutex that was not locked Severity set to 'grave' from 'critical' -- 764568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764568 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#764441: sinfo and slurm-client: error when trying to install together
Hi Gaudenz, On Wed, Oct 08, 2014 at 10:34:45AM +0200, Gaudenz Steinlin gaud...@debian.org wrote: Ralf Treinen trei...@free.fr writes: 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/sinfo /usr/share/man/man1/sinfo.1.gz This happends because the sinfo binary in slurm moved from slurm-llnl to slurm-client and now the conflict specified in sinfo is wrong. To restore the previous state, sinfo should update it's conflict to slurm-client with appropriate versioning. Since your package had a Conflicts, can you please update it? If you agree on that, can you also reassign this bug to src:sinfo so that it is tracked properly? Cheers. -- Mehdi Dogguy -- 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
As upstream maintainer of libcerf, I would like to express a clear preference for solving the conflict by withdrawing cerf.3 and cerfc.3 from manpages-dev. I already proposed this solution to upstream, https://bugzilla.kernel.org/show_bug.cgi?id=80541 where it has been received favorably, but not yet definitively accepted. It might be helpful if somebody expressed in the name of Debian that the matter is somewhat urgent. I am opposed to the alternative solution of libcerf renaming the functions cerf and cerfc. Any other names would be less pertinent. There is no conflict with glibc. On the contrary, libcerf complements glibc in providing a missing implementation. Should glibc one day provide an official implementation, then the two functions will be immediately withdrawn from libcerf. - Joachim smime.p7s Description: S/MIME Cryptographic Signature
Bug#764569: systemd fails to reboot with nvidia on macpro
Control: tags -1 moreinfo Am 09.10.2014 um 07:51 schrieb Norbert Preining: Package: systemd Version: 215-5+b1 Severity: grave Justification: causes non-serious data loss Hi, since the switch to systemd my Mac Pro does not reboot anymore when I am rebooting from X with nvidia driver. What happens is that: - all connections are capped, I tried it via ssh, but couldn't see any logs - screen goes blank - there is rythmic HD activity forever hard reset necessary. It seems that systemd is trying to do whatever it tries to do, without success and without giving up, blocking reboot and any interaction. Nothing in the logs, absolutely nothing. - Unit samba.service: Description: LSB: ensure Samba daemons are started (nmbd and smbd) Instance: n/a Unit Load State: loaded Unit Active State: active Might be a duplicate of [1] Can you run update-rc.d samba remove systemctl stop samba.service and try again. If that doesn't help, follow the debugging hints at [2]. A first step would be, to enable persistent logging, and increase the verbosity via systemd.log_level=debug and/or enabling the debug-shell.service . [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740942 [2] http://freedesktop.org/wiki/Software/systemd/Debugging/ -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#764569: systemd fails to reboot with nvidia on macpro
Processing control commands: tags -1 moreinfo Bug #764569 [systemd] systemd fails to reboot with nvidia on macpro Added tag(s) moreinfo. -- 764569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764569 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#764547: bsdutils: script(1) is broken, hangs or crashes
Andreas Henriksson dixit: Since you seem to have a way to reproduce the problem, could you please also git bisect it? Not this week ☹ also, never worked with that before, I’d have to learn it first. Unless it can be automated? If the result of script contains “Total passed”, it worked, otherwise not. bye, //mirabilos -- 21:49⎜allamoox:#sendmail I have a question guys, ⎜Can I use my PC as SMTP server, I use Windows 7 . ⎜Already googled and Installed IIS ⎜but Still I can't send E-mail -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763237: ld problem tracked in #764573
Hi, This is just to let you know that this problem is now being tracked as #764573. Best, Michael pgpDOGut_NhjN.pgp Description: PGP signature
Bug#745969: guile-1.8: FTBFS: conflicting types for 'yyget_leng'
In case anyone still wants to build guile-1.8, a fix (remove declarations of 'yy*' functions in c-tokenize.lex) is described here: http://lists.gnu.org/archive/html/guile-devel/2010-03/msg00081.html It seems to work on arm64. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757168: marked as done (gamera: FTBFS on several architectures)
Your message dated Thu, 09 Oct 2014 09:20:30 + with message-id e1xc9te-0006gj...@franck.debian.org and subject line Bug#757168: fixed in gamera 3.4.1+svn1423-1 has caused the Debian Bug report #757168, regarding gamera: FTBFS on several architectures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 757168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gamera Version: 3.4.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) gamera failed to build on mips with: | == | FAIL: test_rle.test_rle1 | -- | Traceback (most recent call last): | File /usr/lib/python2.7/dist-packages/nose/case.py, line 197, in runTest | self.test(*self.arg) | File /«PKGBUILDDIR»/tests/test_rle.py, line 23, in test_rle1 | assert image1.color_ccs().to_string() == image2.color_ccs().to_string() | AssertionError | | -- | Ran 583 tests in 83.135s | | FAILED (failures=1) | [181272 refs] | make: *** [build/build-stamp] Error 123 The full build log is available from https://buildd.debian.org/status/fetch.php?pkg=gameraarch=powerpcver=3.4.1-1stamp=1406844483. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: gamera Source-Version: 3.4.1+svn1423-1 We believe that the bug you reported is fixed in the latest version of gamera, 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 757...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Stender deb...@danielstender.com (supplier of updated gamera 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: Wed, 08 Oct 2014 14:00:38 +0200 Source: gamera Binary: python-gamera python-gamera-dbg python-gamera-dev gamera-gui gamera-doc Architecture: source all Version: 3.4.1+svn1423-1 Distribution: unstable Urgency: medium Maintainer: Daniel Stender deb...@danielstender.com Changed-By: Daniel Stender deb...@danielstender.com Description: gamera-doc - documentation for the Gamera framework gamera-gui - GUI for the Gamera framework python-gamera - framework for building document analysis applications python-gamera-dbg - framework for document analysis applications (debug symbols) python-gamera-dev - framework for document analysis applications (header files) Closes: 692661 757168 Changes: gamera (3.4.1+svn1423-1) unstable; urgency=medium . * Updated source to SVN rev. 1423. * deb/rules: changed optimizations (Closes: #757168, thanks to Jakub Wilk). * deb/control: + bumped standards to 3.9.6 (no changes needed). + added XS-Testsuite (Closes: #692661, dropped override). + bumped dep of docs on main packages from Suggests to Recommends. * deb/copyright: + removed license for debian/dh_buildid (dropped in previous package). + updated some license short names. * deb/tests/control: removed no-build-needed (non-standard feature). * Corrected bug URL in suppress-wxdebug-assertion-messages.diff. * wrap-and-sort -a -s. Checksums-Sha1: 7f1f2b4330cbddacc91e6808bb2b47c108b03ada 2530 gamera_3.4.1+svn1423-1.dsc c02ea911395f278d609eb13464aa3945f776c4f7 5336995 gamera_3.4.1+svn1423.orig.tar.gz 6ad0de74613edea4e795d5bec8c4667288f70da7 31100 gamera_3.4.1+svn1423-1.debian.tar.xz eb0ceead00b8505087573a18d1b5932bc196ec6a 158108 python-gamera-dev_3.4.1+svn1423-1_all.deb 62ec502d3e1a8f3f3b77a1db333cc45a8026ca8e 371888 gamera-gui_3.4.1+svn1423-1_all.deb 077870136eb31088180892dfd815ab19213af52a 2750478 gamera-doc_3.4.1+svn1423-1_all.deb Checksums-Sha256: a6c5526cabd481d1af6fceafb15ae0716463bcfb42cb5c4b3482733acc1197ec 2530 gamera_3.4.1+svn1423-1.dsc 3f8182840cd04b7a94ae849690d93dff4213775fccbabc94c42ecefe13946b64 5336995 gamera_3.4.1+svn1423.orig.tar.gz 0855b8c78758b1b5418ce43983c8ce2b3bf5b062fafcf86cd01ab0e05c73db00 31100
Bug#763840: marked as done (iagno: file conflict with gnome-accessibility-themes 3.14)
Your message dated Thu, 09 Oct 2014 09:20:56 +
with message-id e1xc9u4-0006ns...@franck.debian.org
and subject line Bug#763840: fixed in iagno 1:3.14.0-2
has caused the Debian Bug report #763840,
regarding iagno: file conflict with gnome-accessibility-themes 3.14
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.)
--
763840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: iagno
Version: 1:3.14.0-1
Severity: serious
Tags: patch
Justification: Policy 7.6.1, Policy 10.1
Hi,
when upgrading iagno to 1:3.14.0-1 (i.e. today's upgrade in
testing) while gnome-accessibility-themes is still at 3.12.0-1, a file
conflict is reported:
Preparing to unpack .../iagno_1%3a3.14.0-1_amd64.deb ...
Unpacking iagno (1:3.14.0-1) over (1:3.12.2-1) ...
dpkg: error processing archive
/var/cache/apt/archives/iagno_1%3a3.14.0-1_amd64.deb (--unpack):
trying to overwrite '/usr/share/icons/HighContrast/48x48/apps/iagno.png',
which is also in package gnome-accessibility-themes 3.12.0-1
It seems like the HighContrast icons of iagno moved in 3.14 from
gnome-accessibility-themes to iagno itself, so Breaks+Replaces is
missing here. Patch attached for it.
Thanks,
--
Pino
--- a/debian/control.in
+++ b/debian/control.in
@@ -25,6 +25,8 @@ Architecture: any
Depends: ${shlibs:Depends},
${misc:Depends}
Recommends: yelp
+Breaks: gnome-accessibility-themes ( 3.14.0)
+Replaces: gnome-accessibility-themes ( 3.14.0)
Description: popular Othello game for GNOME
Iagno is a computer version of the game Reversi, more popularly called
Othello. Iagno is a two player strategy game similar to Go. The board
---End Message---
---BeginMessage---
Source: iagno
Source-Version: 1:3.14.0-2
We believe that the bug you reported is fixed in the latest version of
iagno, 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.
Andreas Henriksson andr...@fatal.se (supplier of updated iagno 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: Thu, 09 Oct 2014 10:33:00 +0200
Source: iagno
Binary: iagno
Architecture: source amd64
Version: 1:3.14.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
pkg-gnome-maintain...@lists.alioth.debian.org
Changed-By: Andreas Henriksson andr...@fatal.se
Description:
iagno - popular Othello game for GNOME
Closes: 763840
Changes:
iagno (1:3.14.0-2) unstable; urgency=medium
.
[ Pedro Beja ]
* Update build-dependencies according to configure.ac changes:
+ Bump valac (= 0.24)
* Breaks+Replaces needed to gnome-accessibility-themes ( 3.14.0),
thanks to Pino Toscano (Closes: #763840)
Checksums-Sha1:
6d90eb73d198ba5d7c3e7f8d9f5ecb31bc32777e 1582 iagno_3.14.0-2.dsc
82625caf9e173bad6ab37f32944a30742b278499 20284 iagno_3.14.0-2.debian.tar.xz
41098ba619bada165c4d43129fafc8c2666d9836 1135642 iagno_3.14.0-2_amd64.deb
Checksums-Sha256:
a051503964d09dab0d06b8f87275ab977b8286f28c58c440a488791ead0f50ba 1582
iagno_3.14.0-2.dsc
04e155db719967feec911666cae749c02f3349276291eb1ada8bf8a3bba1a676 20284
iagno_3.14.0-2.debian.tar.xz
675cd1fc9fd879db40593f738fa30c467cb5a74e83a17ff7553c959daa9b0380 1135642
iagno_3.14.0-2_amd64.deb
Files:
1fc13517a94199312264e6f8d6ed4834 1582 games optional iagno_3.14.0-2.dsc
8c39e6773502e0f4b678fa259cde9448 20284 games optional
iagno_3.14.0-2.debian.tar.xz
144b8c0d812832750ff2db1edb8866a9 1135642 games optional
iagno_3.14.0-2_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlQ2S0oACgkQcgQ2cL3l8e7UuwCfUMzMTyXFndiK8WqhL0YdjYB9
OrkAni9SpsdwBjBH4amcfV4RVsm/I7ip
=VCbR
-END PGP SIGNATUREEnd Message---
Processed: jessie
Processing commands for cont...@bugs.debian.org:
tag 764571 + sid jessie
Bug #764571 [uthash-dev,libpoclu-dev] libpoclu-dev and uthash-dev: error when
trying to install together
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.
End of message, stopping processing here.
Please contact me if you need assistance.
--
764268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764268
764571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764571
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#758956: quisk still depends on python-wxgtk2.8
Control: reopen -1 Control: found -1 3.6.18-1 On Tue, Sep 23, 2014 at 03:51:11AM +, Debian Bug Tracking System wrote: We believe that the bug you reported is fixed in the latest version of quisk, which is due to be installed in the Debian FTP archive. Unfortunately not - the BD was updated from python-wxgtk2.8 to python-wxgtk3.0, but the run-time dependency is still on python-wxgtk2.8: $ apt-cache showsrc quisk|grep wx Build-Depends: debhelper (= 9.0.0~), python, portaudio19-dev, libpulse-dev, libusb-dev, libfftw3-dev, python-all-dev, libasound2-dev, python-wxgtk3.0, hardening-wrapper $ apt-cache show quisk|grep wx Depends: python (= 2.7), python ( 2.8), libasound2 (= 1.0.16), libc6 (= 2.15), libfftw3-double3, libportaudio2 (= 19+svn20101113), libpulse0 (= 0.99.1), libusb-0.1-4 (= 2:0.1.12), python-wxgtk2.8 Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764581: RM: webkitgtk [sparc] -- ROM; webkitgtk 2.2.5 contains non-DFSG files
Package: ftp.debian.org Severity: serious webkitgtk 2.2.5 contains some files that are not redistributable so all its packages should be removed from the archive. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763613 for details. All other architectures have already upgraded to a version of webkitgtk that does not have this problem. sparc however does not have all the necessary build dependencies. Berto -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: quisk still depends on python-wxgtk2.8
Processing control commands:
reopen -1
Bug #758956 {Done: bott...@debian.org (A. Maitland Bottoms)} [src:quisk] quisk:
Please update to use wxpython3.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 quisk/3.6.18-1.
found -1 3.6.18-1
Bug #758956 [src:quisk] quisk: Please update to use wxpython3.0
Marked as found in versions quisk/3.6.18-1.
--
758956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758956
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#764275: Additional Info (chromium: Segfaults on Startup)
Okay some further information regarding this bug. I was able to get chromium to startup without segfaulting by deleting '~/home/.config/chromium' directory. Now the issue is that the necessary Google API to log Chromium into the browser sync network, as it throws 'Service Unavailable Try Again Later'. HTH -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764547: bsdutils: script(1) is broken, hangs or crashes
On Thu, Oct 09, 2014 at 08:38:09AM +, Thorsten Glaser wrote: Andreas Henriksson dixit: Since you seem to have a way to reproduce the problem, could you please also git bisect it? Not this week ☹ also, never worked with that before, I’d have to learn it first. Unless it can be automated? If the result of script contains “Total passed”, it worked, otherwise not. git bisect is a way to automate manual tasks, so I'm not sure how to make it more automated (or what you question really is). See 'man git bisect' or http://git-scm.com/docs/git-bisect basically: git bisect start v2.25.1 v2.20.1 -- term-utils/script.c ./autogen.sh ./configure make reproduce using ./script (instead of /usr/bin/script) git bisect bad|good rinse and repeat step 2+3 until git tells you the bad commit Regards, Andreas Henriksson PS. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764580 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Processed: jessie
Processing commands for cont...@bugs.debian.org:
tag 764268 -sid -jessie
Bug #764268 {Done: Ludovic Brenta ludo...@ludovic-brenta.org} [src:libaws]
libaws: build-dependency not satisfiable in sid
Removed tag(s) sid.
Bug #764268 {Done: Ludovic Brenta ludo...@ludovic-brenta.org} [src:libaws]
libaws: build-dependency not satisfiable in sid
Removed tag(s) jessie.
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#757348: systemd: with SysV init, can no longer suspend and shutdown from lightdm
Package: systemd-shim Version: 8-2 Followup-For: Bug #757348 Hi, I'm hit by this bug and am not sure what the tag fixed-upstream here is referring to ? This issue is very well present and does not seem to have a fix yet. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-shim depends on: ii cgmanager 0.32-4 ii libc6 2.19-11 ii libglib2.0-0 2.42.0-2 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: pn pm-utils none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764268: Processed: jessie
Hi Ludovic, On Donnerstag, 9. Oktober 2014, Ludovic Brenta wrote: Holger, please stop tagging jessie packages that are not in testing. I wasn't aware that I'm doing this, thanks for notifying! Additionally, the version of libaws referenced in #764268 is neither in jessie nor in sid. This is explained in the bug. Please do not ignore these explanations anymore. ok This is the third time I've had to correct your mistake by hand and I'm getting tired of this. How about you'd tell me immediatly? I'm also quite tired of tagging 1-3 bugs so that they don't show up in the list of release critical bugs affecting stable, which is what people see, when they use apt-listchanges (so they dont get scary warnings about broken packages which dont affect them) or people wanting to fix RC bugs in stable also have a better overview, whats releveant. Thats why I do this, and a.) I could use help with that and b.) people could tag+file bugs correctly in the first place (that only applies to constant submitters who I understand are busy+overworked them selves.) According to my tool, 410 RC bugs affecting wheezy known to the BTS, 896 known to us. - IOW: I've look at 896 RC bugs affecting wheezy since its release. And probably 300-400 I've assigned away not to clutter the views. I'm sorry I make mistakes when doing so and have thus annoyed you... but I hope you understand better now, why I do this. Mistakes happen. Any idea what to do with 764268 then? Downgrade? Close? cheers, Holger signature.asc Description: This is a digitally signed message part.
Processed (with 2 errors): 764258 is duplicate of 764034
Processing commands for cont...@bugs.debian.org: package mandos-client Limiting to bugs with field 'package' containing at least one of 'mandos-client' Limit currently set to 'package':'mandos-client' reassign 764258 python-gnutls Bug #764258 [mandos-client] mandos-client loops forever waiting for server Bug reassigned from package 'mandos-client' to 'python-gnutls'. package: python-gnutls' does not match at least one of mandos-client Failed to clear fixed versions and reopen on 764258: limit failed for bugs: 764258. package python-gnutls Limiting to bugs with field 'package' containing at least one of 'python-gnutls' Limit currently set to 'package':'python-gnutls' severity 764258 normal Bug #764258 [python-gnutls] mandos-client loops forever waiting for server Severity set to 'normal' from 'grave' merge 764258 764034 Bug #764258 [python-gnutls] mandos-client loops forever waiting for server Unable to merge bugs because: affects of #764034 is 'mandos' not '' Failed to merge 764258: Did not alter merged bugs stop Stopping processing here. Please contact me if you need assistance. -- 764034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764034 764258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764258 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#758121: [Pkg-crosswire-devel] Bug#758121: bibletime: Bibletime is unusable in testing and unstable
On 8 October 2014 15:54, da...@sandersweb.net wrote: retitle 758121 bibletime: New upstream release fixes display problem in jessie severity 758121 grave thanks On Monday, October 06, 2014 10:26:56 PM you wrote: Bibletime is unusable in jessie and sid. When you open any Bible or commentary all you see is jibberish. This needs to be fixed prior to the release of jessie. I just built the new upstream release (2.10.1) from source. It does not have this problem. Please update the bibletime package in jessie to the latest upstream release available on sourceforge. Debdiff would be appreciated. I don't use, nor typically updated bibletime. -- Regards, Dimitri. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 764448 is serious
Processing commands for cont...@bugs.debian.org: severity 764448 serious Bug #764448 [mate-applets] mate-applets 1.8.1+dfsg1-1 tries to overwrite files in gnome-applets 3.8.1-1 Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 764448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764448 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#764448: mate-applets 1.8.1+dfsg1-1 tries to overwrite files in gnome-applets 3.8.1-1
Hi Giacomo, On Mi 08 Okt 2014 09:28:07 CEST, Giacomo Mulas wrote: Dear Maintainer, the new version 1.8.1+dfsg1-1 of mate-applets contains files with the same name as gnome-applets 3.8.1-1. As a consequence, it is uninstallable if one also installs gnome-applets. This means that on sid, at the moment, I cannot install on a machine a full gnome desktop and a full mate desktop at the same time, letting individual users choose which one they prefer to use. Suggested solutions: 1) quick and dirty (unsatisfactory for me, but can be a temporary band aid): add a conflicts with gnome-applets 2) optimal solution: change the names of the conflicting applets (possibly coordinating with the gnome-applets maintainer) 3) less work than 2) but also less good: use the debian alternatives system to make mate and gnome applets with the same name coexist (definitely coordinating with the gnome-applets maintainer) 4) something else that I did not think about Bye Giacomo Mulas Thanks for reporting this. This needs to be fixed upstream+downstream. What are the files that trouble you (and us all)? (Asking, because I can't check right now, because I am at a customer). Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpLrrZ57GcS9.pgp Description: Digitale PGP-Signatur
Bug#764448: mate-applets 1.8.1+dfsg1-1 tries to overwrite files in gnome-applets 3.8.1-1
Control: reassign -1 mate-applets,gnome-applets Control: found -1 mate-applets/1.8.1+dfsg1-1 Control: found -1 gnome-applets/3.8.1-1 Hi, Giacomo Mulas wrote: the new version 1.8.1+dfsg1-1 of mate-applets contains files with the same name as gnome-applets 3.8.1-1. As a consequence, it is uninstallable if one also installs gnome-applets. Thanks for the report. For the MATE maintainers: We also ran into that issue on Ubuntu 12.04 LTS Precise with the packages from MATE PPA, so after this is fixed in Debian Sid, it should be fixed in the MATE Precise PPA, too. Suggested solutions: There's a standard procedure for such cases: https://www.debian.org/doc/debian-policy/ch-files.html#s-binaries 1) quick and dirty (unsatisfactory for me, but can be a temporary band aid): add a conflicts with gnome-applets Yeah, that's usually discouraged. 2) optimal solution: change the names of the conflicting applets (possibly coordinating with the gnome-applets maintainer) That's the officially recommended way. 3) less work than 2) but also less good: use the debian alternatives system to make mate and gnome applets with the same name coexist (definitely coordinating with the gnome-applets maintainer) For that their API/ABI always needs to be same. Which likely isn't. And it's also likely much more work than 2). Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- 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#764448: mate-applets 1.8.1+dfsg1-1 tries to overwrite files in gnome-applets 3.8.1-1
Processing control commands: reassign -1 mate-applets,gnome-applets Bug #764448 [mate-applets] mate-applets 1.8.1+dfsg1-1 tries to overwrite files in gnome-applets 3.8.1-1 Bug reassigned from package 'mate-applets' to 'mate-applets,gnome-applets'. No longer marked as found in versions mate-applets/1.8.1+dfsg1-1. Ignoring request to alter fixed versions of bug #764448 to the same values previously set found -1 mate-applets/1.8.1+dfsg1-1 Bug #764448 [mate-applets,gnome-applets] mate-applets 1.8.1+dfsg1-1 tries to overwrite files in gnome-applets 3.8.1-1 Marked as found in versions mate-applets/1.8.1+dfsg1-1. found -1 gnome-applets/3.8.1-1 Bug #764448 [mate-applets,gnome-applets] mate-applets 1.8.1+dfsg1-1 tries to overwrite files in gnome-applets 3.8.1-1 Marked as found in versions gnome-applets/3.8.1-1. -- 764448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764448 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
from my original report i would guesstimate from: + d=/tmp/.X11-unix ^^ ... Ah, sorry, I was under the impression (no idea why) that you were seeing the problem in getXconsole. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at gmail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764448: mate-applets 1.8.1+dfsg1-1 tries to overwrite files in gnome-applets 3.8.1-1
Hi Mike, Mike Gabriel wrote: What are the files that trouble you (and us all)? Here you go: Preparing to unpack .../mate-applets_1.8.1+dfsg1-1_i386.deb ... Unpacking mate-applets (1.8.1+dfsg1-1) over (1.8.0+dfsg1-1+b2) ... dpkg: error processing archive /var/cache/apt/archives/mate-applets_1.8.1+dfsg1-1_i386.deb (--unpack): trying to overwrite '/usr/share/man/man1/whereami_applet.1.gz', which is also in package gnome-applets 3.8.1-1 Processing triggers for [...] Errors were encountered while processing: /var/cache/apt/archives/mate-applets_1.8.1+dfsg1-1_i386.deb Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755575: marked as done (anjuta-extras: uninstallable with anjuta 3.14)
Your message dated Thu, 09 Oct 2014 10:34:01 + with message-id e1xcb2n-0004bh...@franck.debian.org and subject line Bug#755575: fixed in anjuta-extras 3.10.0-3 has caused the Debian Bug report #755575, regarding anjuta-extras: uninstallable with anjuta 3.14 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.) -- 755575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu anjuta-extras_3.10.0-1 . ALL . -m rebuild against anjuta 2:3.12.0-1 anjuta-extras still depends on anjuta ( 2:3.11) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: anjuta-extras Source-Version: 3.10.0-3 We believe that the bug you reported is fixed in the latest version of anjuta-extras, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Henriksson andr...@fatal.se (supplier of updated anjuta-extras 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: Thu, 09 Oct 2014 12:26:11 +0200 Source: anjuta-extras Binary: anjuta-extras Architecture: source amd64 Version: 3.10.0-3 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Andreas Henriksson andr...@fatal.se Description: anjuta-extras - plugins and extras for anjuta Closes: 755575 Changes: anjuta-extras (3.10.0-3) unstable; urgency=medium . * Bump anjuta versioned dependency to 2:3.15 (Closes: #755575) Checksums-Sha1: ebf3271c17a8c7eebf4e10f2b9c6f109f9620670 1697 anjuta-extras_3.10.0-3.dsc 5ad869248b08a670c7f739f713a3d87185cd5fe2 6440 anjuta-extras_3.10.0-3.debian.tar.xz 421bcdc985c945e439d689b3f9506684547b5a24 1594430 anjuta-extras_3.10.0-3_amd64.deb Checksums-Sha256: fdc1f0b8d70a14189a17d09308647bcc310dd4f17fbb87e5f4345ea9b8320912 1697 anjuta-extras_3.10.0-3.dsc e17a961643362a3aa4d9903334f22437ce75dd67cbbc74ae8a2125237f77a0a1 6440 anjuta-extras_3.10.0-3.debian.tar.xz bd97fd653f4534116f81d03651ac39463c5dab2a305026a9b2e660abc3af52a9 1594430 anjuta-extras_3.10.0-3_amd64.deb Files: 59b7a527014799746093976ca5f8512e 1697 gnome optional anjuta-extras_3.10.0-3.dsc d7fb0f587de8a14f69f0ce85d1c00d41 6440 gnome optional anjuta-extras_3.10.0-3.debian.tar.xz 2ab49b133a42014e620dc1e4e503df2f 1594430 gnome optional anjuta-extras_3.10.0-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlQ2Y9sACgkQcgQ2cL3l8e5XLACg1jwKqlv8ZaMpsKYcoypdrBD8 nDwAniTdNB1hRf3X2G0MWV4BrRlJyjwl =ATaW -END PGP SIGNATUREEnd Message---
Bug#758121: [Pkg-crosswire-devel] Bug#758121: Bug#758121: bibletime: Bibletime is unusable in testing and unstable
I do use it. I was planning on trying to update the package this weekend. Regards, -Roberto On Thu, Oct 09, 2014 at 10:55:59AM +0100, Dimitri John Ledkov wrote: On 8 October 2014 15:54, da...@sandersweb.net wrote: retitle 758121 bibletime: New upstream release fixes display problem in jessie severity 758121 grave thanks On Monday, October 06, 2014 10:26:56 PM you wrote: Bibletime is unusable in jessie and sid. When you open any Bible or commentary all you see is jibberish. This needs to be fixed prior to the release of jessie. I just built the new upstream release (2.10.1) from source. It does not have this problem. Please update the bibletime package in jessie to the latest upstream release available on sourceforge. Debdiff would be appreciated. I don't use, nor typically updated bibletime. -- Regards, Dimitri. ___ Pkg-crosswire-devel mailing list pkg-crosswire-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Bug#764472: cups creates millions of temporary files when printing
Hello Brian, Thank you for your answer. Hello Antonio, Thank you for your report. The first thing to say is that this is very likely not to be a bug in cups. Please see https://bugs.launchpad.net/ubuntu/+source/cups/+bug/890705 and https://bugzilla.redhat.com/show_bug.cgi?id=581748 So - do you have acroread installed? I looked at the bug reports you mentioned, so probably it is a problem of another package. I have acroread installed, but acroread was closed - I was printing with evince. But I will try to reproduce the problem and find it out. On Wed 08 Oct 2014 at 14:04:46 +0200, Antonio Sartori wrote: When trying to print (tried twice from evince, not tested from other software), cups creates millions of symbolic links in /tmp to the ppd driver in /etc/cups/ppd. The names of the symbolic links are similar to 54351da228fae. Millions of links would imply lots of printing taking place and not just twice. Is that the case? Also, does it occur with other applications? We really need to track down under what circumstances the files are created and why they are not deleted by the application. No, I tried to print only three or four times. This causes the system to hang on the next reboot while systemd tries to empty the tmp folder, making the system unbootable. Do you mean it hangs indefinitely and the machine has to powered off to be restarted? Yes. The problem is that systemd wants to empty the tmp folder during the boot. I don't know how it does it, but the problem is that removing millions of files is slow, anyway (see http://unix.stackexchange.com/questions/96935/faster-way-to-delete-large-number-of-files). I was finally able to list some of the files using ls -Uf | head -n 100 (it seems the slow part is the sorting of ls). The files where actually a bit more than 100. For removing the files, I used ionice -c 2 -n 7 find . -type l -delete, but it took more than one hour to finish. Notice that deleting the files by hand is tricky, since they are too many (rm does not work, it is not even possible to list the files with ls), I don't know how to do this. For now, I rebooted the system using a live dist and I typed mv /tmp /tmp2. This enables the system to boot again. Help on how I can delete the folder tmp2 would also be appreciated. I'm surprised 'ls -l' doesn't work. Is there any error message? What about 'ls -l | head'. 'rm -r /tmp2' should delete /tmp2. rm -r /tmp2 seems also to be extremely slow. Probably it unlinks first each single file inside tmp2. For now, I mounted tmp as tmpfs so I can try againg without making the system unbootable. Regards, Antonio Regards, Brian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5436422c.3020...@gmail.com
Bug#764472: cups creates millions of temporary files when printing
Hello Brian, Some additional information: The links are created when printing with evince, but not when printing with lp. (Actually, printing with evince produces blank pages, but I don't know whether this is related - maybe it's a problem of my pdf file.) The links continue to be created after the print command from evince has been given (about 50 links per minute). During this, a process uses most of the cpu, and it is /usr/bin/python /usr/share/system-config-printer/scp-dbus-service.py Killing this process, the creation of symlinks stops. So I guess this is what creates this lot of symlinks. I am not quite sure now whether this is a bug of evince, or of system-config-printer or something else. Regards, Antonio Il 09/10/2014 01:00, Brian Potkin ha scritto: Hello Antonio, Thank you for your report. The first thing to say is that this is very likely not to be a bug in cups. Please see https://bugs.launchpad.net/ubuntu/+source/cups/+bug/890705 and https://bugzilla.redhat.com/show_bug.cgi?id=581748 So - do you have acroread installed? On Wed 08 Oct 2014 at 14:04:46 +0200, Antonio Sartori wrote: When trying to print (tried twice from evince, not tested from other software), cups creates millions of symbolic links in /tmp to the ppd driver in /etc/cups/ppd. The names of the symbolic links are similar to 54351da228fae. Millions of links would imply lots of printing taking place and not just twice. Is that the case? Also, does it occur with other applications? We really need to track down under what circumstances the files are created and why they are not deleted by the application. This causes the system to hang on the next reboot while systemd tries to empty the tmp folder, making the system unbootable. Do you mean it hangs indefinitely and the machine has to powered off to be restarted? Notice that deleting the files by hand is tricky, since they are too many (rm does not work, it is not even possible to list the files with ls), I don't know how to do this. For now, I rebooted the system using a live dist and I typed mv /tmp /tmp2. This enables the system to boot again. Help on how I can delete the folder tmp2 would also be appreciated. I'm surprised 'ls -l' doesn't work. Is there any error message? What about 'ls -l | head'. 'rm -r /tmp2' should delete /tmp2. Regards, Brian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54364fe8.2060...@gmail.com
Bug#764588: ffmpeg: fails to build from source in sid
package: ffmpeg severity: critical version: 2.4.1-1 Hi, ffmpeg fails to build from source in sid in pbuilder as per attached log. make[1]: Leaving directory '/tmp/buildd/ffmpeg-2.4.1' debian/rules override_dh_auto_build-arch make[1]: Entering directory '/tmp/buildd/ffmpeg-2.4.1' sem_open: Function not implemented # Build qt-faststart here, to make it possible to build with 'nocheck'. make tools/qt-faststart make[2]: Entering directory '/tmp/buildd/ffmpeg-2.4.1' touch .version gcc -I. -I./ -D_FORTIFY_SOURCE=2 -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 - D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC - DZLIB_CONST -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow - fstack-protector-all -std=c99 -fomit-frame-pointer -fPIC -pthread - I/usr/include/p11-kit-1 -I/usr/include/harfbuzz -I/usr/include/freetype2 - I/usr/include/fribidi -I/usr/include/freetype2 -I/usr/include/bs2b - I/usr/include/freetype2 -I/usr/include/freetype2 -I/usr/include/fribidi - I/usr/include/opencv -I/usr/include/opus -D_REENTRANT -I/usr/include/p11-kit-1 -I/usr/include/schroedinger-1.0 -I/usr/include/orc-0.4 -D_GNU_SOURCE=1 - D_REENTRANT -I/usr/include/SDL -g -Wdeclaration-after-statement -Wall - Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wwrite-strings - Wtype-limits -Wundef -Wmissing-prototypes -Wno-pointer-to-int-cast -Wstrict- prototypes -Wempty-body -Wno-parentheses -Wno-switch -Wno-format-zero-length - Wno-pointer-sign -O3 -fno-math-errno -fno-signed-zeros -fno-tree-vectorize - Werror=format-security -Werror=implicit-function-declaration -Werror=missing- prototypes -Werror=return-type -Werror=vla -Wformat -Wno-maybe-uninitialized -MMD -MF tools/qt-faststart.d -MT tools/qt-faststart.o -c -o tools/qt- faststart.o tools/qt-faststart.c gcc -Llibavcodec -Llibavdevice -Llibavfilter -Llibavformat -Llibavresample - Llibavutil -Llibpostproc -Llibswscale -Llibswresample -Wl,-z,relro -Wl,- z,relro -Wl,-z,now -Wl,--as-needed -Wl,--warn-common -Wl,-rpath- link=libpostproc:libswresample:libswscale:libavfilter:libavdevice:libavformat:libavcodec:libavutil:libavresample -o tools/qt-faststart tools/qt-faststart.o make[2]: Leaving directory '/tmp/buildd/ffmpeg-2.4.1' # Use faketime to make the build more binary reproducible. faketime -f -m dh_auto_build -a sem_open: Function not implemented debian/rules:195: recipe for target 'override_dh_auto_build-arch' failed make[1]: *** [override_dh_auto_build-arch] Error 1 make[1]: Leaving directory '/tmp/buildd/ffmpeg-2.4.1' debian/rules:164: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 E: Failed autobuilding of package cheers, Holger DIST=unstable ARCH=amd64 W: /root/.pbuilderrc does not exist I: using fakeroot in build. I: Current time: Thu Oct 9 12:40:22 CEST 2014 I: pbuilder-time-stamp: 1412851222 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-amd64-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc filesystem I: mounting /dev/pts filesystem I: policy-rc.d already exists I: Obtaining the cached apt archive contents I: Installing the build-deps - Attempting to satisfy build-dependencies - Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: bc, debhelper (= 9), flite1-dev, frei0r-plugins-dev, ladspa-sdk, libass-dev, libbluray-dev, libbs2b-dev, libbz2-dev, libcaca-dev, libcdio-paranoia-dev, libcrystalhd-dev, libfribidi-dev, libgme-dev, libgnutls28-dev | libgnutls-dev, libgsm1-dev, libiec61883-dev, libavc1394-dev, libjack-jackd2-dev, libmodplug-dev, libmp3lame-dev, libopenal-dev, libopencv-dev, libopenjpeg-dev, libopus-dev, librtmp-dev, libschroedinger-dev, libsctp-dev, libsdl-dev, libshine-dev (= 3.0.0), libsoxr-dev, libspeex-dev, libssh-dev, libtheora-dev, libtwolame-dev, libva-dev, libvdpau-dev, libvorbis-dev, libvpx-dev, libwavpack-dev, libwebp-dev, libx264-dev, libxvidcore-dev, libxvmc-dev, libzmq3-dev, libzvbi-dev, texinfo, yasm, faketime, cleancss, doxygen, node-less dpkg-deb: building package `pbuilder-satisfydepends-dummy' in `/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 11926 files and directories currently installed.) Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ... Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ... dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested: pbuilder-satisfydepends-dummy depends on bc;
Bug#764547: bsdutils: script(1) is broken, hangs or crashes
Control: tags -1 unreproducible moreinfo Control: severity -1 normal Hello! I'm not able to build the old version because of #764580 but since script has no external dependencies just reverting the changes in term-utils/script.c should be enough: git diff v2.20.1..v2.25.1 term-utils/script.c | patch -p1 -R Building this does not result in any behavioural change for me. I also tried installing bsdutils 2.20.1-5.11 and saw no change in behaviour there either. That there are bugs in script is no news (see other bug reports) and, partially because of that and partially because of being unreproducible and partially because script by itself doesn't make bsdutils unusable, I'm setting the severity to be in line with the rest. Additional information to help resolve or atleaste reproduce welcome. Regards, Andreas Henriksson -- 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#764547: bsdutils: script(1) is broken, hangs or crashes
Processing control commands: tags -1 unreproducible moreinfo Bug #764547 [bsdutils] bsdutils: script(1) is broken, hangs or crashes Added tag(s) unreproducible and moreinfo. severity -1 normal Bug #764547 [bsdutils] bsdutils: script(1) is broken, hangs or crashes Severity set to 'normal' from 'serious' -- 764547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764547 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#764590: procps: fails to build from source in sid on amd64
package: procps
version: 3.3.9-8
severity: critical
Hi,
procps fails to build from source in sid on amd64 in pbuilder as per attached
log.
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./w.test/w.exp ...
=== w Summary ===
# of expected passes7
/tmp/buildd/procps-3.3.9/w version 3.3.9
Makefile:515: recipe for target 'check-DEJAGNU' failed
make[4]: *** [check-DEJAGNU] Error 1
make[4]: Leaving directory '/tmp/buildd/procps-3.3.9/testsuite'
Makefile:587: recipe for target 'check-am' failed
make[3]: *** [check-am] Error 2
make[3]: Leaving directory '/tmp/buildd/procps-3.3.9/testsuite'
Makefile:1118: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/tmp/buildd/procps-3.3.9'
Makefile:1409: recipe for target 'check' failed
make[1]: *** [check] Error 2
make[1]: Leaving directory '/tmp/buildd/procps-3.3.9'
dh_auto_test: make -j1 check returned exit code 2
debian/rules:20: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package
cheers,
Holger
DIST=unstable
ARCH=amd64
W: /root/.pbuilderrc does not exist
I: using fakeroot in build.
I: Current time: Thu Oct 9 13:01:50 CEST 2014
I: pbuilder-time-stamp: 1412852510
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-amd64-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /dev/pts filesystem
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (= 9.20120115), libncurses5-dev, libncursesw5-dev, dejagnu, libnuma-dev, dh-autoreconf, pkg-config
dpkg-deb: building package `pbuilder-satisfydepends-dummy' in `/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 11926 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested:
pbuilder-satisfydepends-dummy depends on debhelper (= 9.20120115); however:
Package debhelper is not installed.
pbuilder-satisfydepends-dummy depends on libncurses5-dev; however:
Package libncurses5-dev is not installed.
pbuilder-satisfydepends-dummy depends on libncursesw5-dev; however:
Package libncursesw5-dev is not installed.
pbuilder-satisfydepends-dummy depends on dejagnu; however:
Package dejagnu is not installed.
pbuilder-satisfydepends-dummy depends on libnuma-dev; however:
Package libnuma-dev is not installed.
pbuilder-satisfydepends-dummy depends on dh-autoreconf; however:
Package dh-autoreconf is not installed.
pbuilder-satisfydepends-dummy depends on pkg-config; however:
Package pkg-config is not installed.
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
autoconf{a} automake{a} autopoint{a} autotools-dev{a} bsdmainutils{a}
debhelper{a} dejagnu{a} dh-autoreconf{a} expect{a} file{a} gettext{a}
gettext-base{a} groff-base{a} intltool-debian{a} libasprintf0c2{a}
libcroco3{a} libffi6{a} libglib2.0-0{a} libmagic1{a} libncurses5-dev{a}
libncursesw5-dev{a} libnuma-dev{a} libnuma1{a} libpipeline1{a}
libsigsegv2{a} libtcl8.6{a} libtinfo-dev{a} libtool{a} libtool-bin{a}
libunistring0{a} libxml2{a} m4{a} man-db{a} pkg-config{a} po-debconf{a}
tcl-expect{a}
0 packages upgraded, 36 newly installed, 0 to remove and 0 not upgraded.
Need to get 2791 kB/13.8 MB of archives. After unpacking 41.8 MB will be used.
Writing extended state information...
Get: 1 http://ftp.de.debian.org/debian/ unstable/main libnuma1 amd64 2.0.10~rc2-3 [31.7 kB]
Get: 2 http://ftp.de.debian.org/debian/ unstable/main libtcl8.6 amd64 8.6.2+dfsg-1 [979 kB]
Get: 3 http://ftp.de.debian.org/debian/ unstable/main tcl-expect amd64 5.45-6 [131 kB]
Get: 4
Processed: Re: #764268 never affected wheezy
Processing commands for cont...@bugs.debian.org:
fixed 764268 2.10.2-4
Bug #764268 {Done: Ludovic Brenta ludo...@ludovic-brenta.org} [src:libaws]
libaws: build-dependency not satisfiable in sid
Marked as fixed in versions libaws/2.10.2-4.
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#746038: marked as done (linux-headers-amd64: configure error in linux-headers)
Your message dated Thu, 09 Oct 2014 11:04:08 + with message-id e1xcbvw-00021s...@franck.debian.org and subject line Bug#714045: fixed in blcr 0.8.6~b3-1 has caused the Debian Bug report #714045, regarding linux-headers-amd64: configure error in linux-headers 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.) -- 714045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-headers-amd64 Version: 3.13+56 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-headers-amd64 depends on: ii linux-headers-3.13-1-amd64 3.13.10-1 linux-headers-amd64 recommends no packages. linux-headers-amd64 suggests no packages. -- no debconf information When configure linux headers after last update in Debian Sid: In file /var/lib/dkms/blcr/0.8.5/build/make.log When configure linux headers after last update in Debian Sid: In file /var/lib/dkms/blcr/0.8.5/build/make.log DKMS make.log for blcr-0.8.5 for kernel 3.13-1-amd64 (x86_64) Sun Apr 27 11:03:38 WEST 2014 make: Entering directory `/usr/src/linux-headers-3.13-1-amd64' /var/lib/dkms/blcr/0.8.5/build/Kbuild:19: /var/lib/dkms/blcr/0.8.5/build/module_files: No such file or directory cd /var/lib/dkms/blcr/0.8.5/build env -i PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/lib/dkms ./configure --disable-maintainer-mode --with-linux=3.13-1-amd64 --with-installed-libcr --with-installed-util --with-components=modules --prefix=/usr touch /var/lib/dkms/blcr/0.8.5/build/config-stamp checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for pwd... /bin/pwd checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for perl5... no checking for perl... /usr/bin/perl checking for gmake... no checking for make... /usr/bin/make checking if /usr/bin/make is GNU make... yes (3.81) checking for ranlib... ranlib checking whether ln -s works... yes checking for style of include used by /usr/bin/make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking size of void *... 8 checking whether CXX='g++' acts like a C++ compiler... yes checking whether CXX='g++' matches wordsize of CC... yes checking how to print strings... printf checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm
Bug#714045: marked as done (blcr-dkms: blcr module is not built on kernel 3.9.1)
Your message dated Thu, 09 Oct 2014 11:04:08 + with message-id e1xcbvw-00021s...@franck.debian.org and subject line Bug#714045: fixed in blcr 0.8.6~b3-1 has caused the Debian Bug report #714045, regarding blcr-dkms: blcr module is not built on kernel 3.9.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.) -- 714045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: blcr-dkms Version: 0.8.5-2 Severity: grave Justification: renders package unusable The blcr module is not built when installing the package blcr-dkms and using the latest 3.9 testing kernel. This is the error log: [...] Building module: cleaning build area make KERNELRELEASE=3.9-1-486 -C /lib/modules/3.9-1-486/build M=/var/lib/dkms/blcr/0.8.5/build.(bad exit status: 2) Error! Bad return status for module build on kernel: 3.9-1-486 (i686) Consult /var/lib/dkms/blcr/0.8.5/build/make.log for more information. Output from /var/lib/dkms/blcr/0.8.5/build/make.log: [...] checking compiler to build kernel modules... gcc (default) checking for BSD- or MS-compatible name lister (nm)... (cached) /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... (cached) BSD nm configure: error: --with-linux argument '3.9-1-486' is neither a kernel version string nor a full path make[3]: *** [/var/lib/dkms/blcr/0.8.5/build/config-stamp] Error 1 make[2]: *** [_module_/var/lib/dkms/blcr/0.8.5/build] Error 2 make[1]: *** [sub-make] Error 2 make: *** [all] Error 2 make: Leaving directory `/usr/src/linux-headers-3.9-1-486' Thanks, Daniele -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.9-1-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages blcr-dkms depends on: ii dkms 2.2.0.3-1.2 ii linux-headers-3.2.0-4-486 [linux-headers] 3.2.41-2 ii linux-headers-3.2.0-4-686-pae [linux-headers] 3.2.41-2 ii linux-headers-3.9-1-486 [linux-headers]3.9.6-1 ii linux-headers-3.9-1-686-pae [linux-headers]3.9.6-1 ii linux-headers-686-pae [linux-headers] 3.9+49 ii make 3.81-8.2 Versions of packages blcr-dkms recommends: ii blcr-util 0.8.5-2 blcr-dkms suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: blcr Source-Version: 0.8.6~b3-1 We believe that the bug you reported is fixed in the latest version of blcr, 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 714...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alan Woodland awoodl...@debian.org (supplier of updated blcr 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, 08 Oct 2014 11:05:01 +0100 Source: blcr Binary: blcr-util blcr-testsuite libcr0 libcr-dbg lib32cr0 libcr-dev blcr-dkms Architecture: source all amd64 Version: 0.8.6~b3-1 Distribution: experimental Urgency: low Maintainer: Alan Woodland awoodl...@debian.org Changed-By: Alan Woodland awoodl...@debian.org Description: blcr-dkms - DKMS support for BLCR kernel module blcr-testsuite - Userspace tools to Checkpoint and Restart Linux processes blcr-util - Userspace tools to Checkpoint and Restart Linux processes lib32cr0 - (32bit) Libraries to Checkpoint and Restart Linux processes libcr-dbg - Libraries to Checkpoint and Restart Linux processes libcr-dev - Development files for BLCR libcr0 - Libraries to Checkpoint and Restart Linux processes Closes: 704460 714045 731234 Changes: blcr (0.8.6~b3-1) experimental; urgency=low . * Updated to latest upstream beta for newer kernel support (Closes: #714045) * Fixed typo in libcr0 description (Closes: #704460) * Added powerpcspe (Closes: #731234) * Fix version matching for Jessie kernels * Rerun autoconf Checksums-Sha1: e6c9b75a7c3936ccf1659fe614624a2550aa1162 2397 blcr_0.8.6~b3-1.dsc 23fc5e9c5f5312c331492398ebe003b211274485 934339 blcr_0.8.6~b3.orig.tar.gz
Bug#764448: mate-applets 1.8.1+dfsg1-1 tries to overwrite files in gnome-applets 3.8.1-1
On Thu, 9 Oct 2014, Mike Gabriel wrote: Hi Giacomo, Hi Mike Thanks for reporting this. This needs to be fixed upstream+downstream. What are the files that trouble you (and us all)? (Asking, because I can't check right now, because I am at a customer). Manpages. I had a look at the contents of the package, apparently everything else has a unique (full) filename, meaning that at least some part of the path is unique, even if the final filename duplicates something in gnome, so this is ok. Instead, most manpages in man1 in the package have exactly the same name as their gnome counterparts, so these should be changed/fixed. E.g. cdplayer_applet.1.gz, charpick_applet.1.gz, cpufreq-selector.1.gz, drivemount_applet.1.gz, geyes_applet.1.gz, gkb_applet.1.gz, ... Perhaps they should all be prefixed with mate- or suffixed with -mate or something similar to make their names unique. This should be relatively painless, apart from having to do some script-fu to rename the manpages before building the deb binary package... Could be done by awk probably, or even with some pipeing of commands like cd $INSTALL/usr/share/man/man1 ; for i in `ls *.1.gz` ; mv $i mate-$i ; done or something along these lines. Cheers Giacomo -- _ Giacomo Mulas gmu...@oa-cagliari.inaf.it _ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180244 mob. : +39 329 6603810 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 764588 is serious, reassign 764588 to src:ffmpeg
Processing commands for cont...@bugs.debian.org: severity 764588 serious Bug #764588 [ffmpeg] ffmpeg: fails to build from source in sid Severity set to 'serious' from 'critical' reassign 764588 src:ffmpeg 2.4.1-1 Bug #764588 [ffmpeg] ffmpeg: fails to build from source in sid Bug reassigned from package 'ffmpeg' to 'src:ffmpeg'. No longer marked as found in versions 2.4.1-1. Ignoring request to alter fixed versions of bug #764588 to the same values previously set Bug #764588 [src:ffmpeg] ffmpeg: fails to build from source in sid The source 'ffmpeg' and version '2.4.1-1' do not appear to match any binary packages Marked as found in versions ffmpeg/2.4.1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 764588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764588 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#764472: cups creates millions of temporary files when printing
Antonio, Please don't forget to Cc the bug report. I'v bounced your previous two mails there so there is no need to do anything about those. On Thu 09 Oct 2014 at 11:05:44 +0200, Antonio Sartori wrote: Hello Brian, Some additional information: The links are created when printing with evince, but not when printing with lp. (Actually, printing with evince produces blank pages, but I don't know whether this is related - maybe it's a problem of my pdf file.) The links continue to be created after the print command from evince has been given (about 50 links per minute). During this, a process uses most of the cpu, and it is /usr/bin/python /usr/share/system-config-printer/scp-dbus-service.py Killing this process, the creation of symlinks stops. So I guess this is what creates this lot of symlinks. I am not quite sure now whether this is a bug of evince, or of system-config-printer or something else. Nice progress. I'm thinking that your report should be reassigned to system-config-printer and merged with #764253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764253 But before doing so let us see if we can give the maintainers there some help. Acroread is non-running but I'd be happier if it were not around. Please would you purge it from the system and try a print or two. From evince is one obvious application. Iceweasel uses the same GTK print dialog so it too would be suitable. Another couple of links to rather old bug reports: https://bugzilla.redhat.com/show_bug.cgi?id=582202 https://bugzilla.redhat.com/show_bug.cgi?id=498743 Regards, Brian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762087: samba: systemd and samba stop computer wait of 5 minute
Same problem here. Even with systemctl stop samba it takes much time, and in the meanwhile a systemctl list-jobs returns this: JOB UNITTYPE STATE 2581 samba.service stop running 2582 samba-ad-dc.service stop waiting 2 jobs listed. -- Massimo Maiurana Ragusa (RG) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758501: marked as done (gsmlib: FTBFS in unstable with gettext 0.19)
Your message dated Thu, 09 Oct 2014 11:34:02 + with message-id e1xcbys-0002sp...@franck.debian.org and subject line Bug#758501: fixed in gsmlib 1.10+20120414.gita5e5ae9a-0.2 has caused the Debian Bug report #758501, regarding gsmlib: FTBFS in unstable with gettext 0.19 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.) -- 758501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gsmlib Version: 1.10+20120414.gita5e5ae9a-0.1 Severity: serious Justification: FTBFS User: debian-...@lists.debian.org Usertag: arm64 gsmlib will FTBFS due to gettext upgrade in unstable. Blocks arm64 since gettext 0.18 was never built on arm64, but happens also on all other architectures: local reproduced build on i386: make[3]: Entering directory '/tmp/buildd/gsmlib-1.10+20120414.gita5e5ae9a/po' *** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.18 but the autoconf macros are from gettext version 0.19 arm64 build: https://buildd.debian.org/status/fetch.php?pkg=gsmlibarch=arm64ver=1.10%2B20120414.gita5e5ae9a-0.1stamp=1408319184 ---End Message--- ---BeginMessage--- Source: gsmlib Source-Version: 1.10+20120414.gita5e5ae9a-0.2 We believe that the bug you reported is fixed in the latest version of gsmlib, 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. Andrew Shadura andre...@debian.org (supplier of updated gsmlib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 09 Oct 2014 13:24:02 +0200 Source: gsmlib Binary: libgsmme-dev libgsmme1c2a gsm-utils Architecture: source i386 Version: 1.10+20120414.gita5e5ae9a-0.2 Distribution: unstable Urgency: medium Maintainer: Mark Purcell m...@debian.org Changed-By: Andrew Shadura andre...@debian.org Description: gsm-utils - GSM mobile phone access applications libgsmme-dev - Header files and static libraries for gsmlib libgsmme1c2a - GSM mobile phone access library Closes: 758501 Changes: gsmlib (1.10+20120414.gita5e5ae9a-0.2) unstable; urgency=medium . * Non-maintainer upload. * Fix build with newer gettext (Closes: #758501). * Update config.sub/config.guess. * Add an upstream patch to fix parseInt2. Checksums-Sha1: 4b9afa331c27d243a177fe70382efe2330506737 1980 gsmlib_1.10+20120414.gita5e5ae9a-0.2.dsc 1b35d0cc20830c0f8cfc4520ace396a467232f8b 24944 gsmlib_1.10+20120414.gita5e5ae9a-0.2.debian.tar.xz b110a6c4f5d163a6ce216e8d1afdc92376db7248 37114 libgsmme-dev_1.10+20120414.gita5e5ae9a-0.2_i386.deb 2beda1b4e5b23a45a0d6c43d2c08a415b5c4d918 182474 libgsmme1c2a_1.10+20120414.gita5e5ae9a-0.2_i386.deb 30f9221220219d3ebf25674fd306380d3023fb63 107558 gsm-utils_1.10+20120414.gita5e5ae9a-0.2_i386.deb Checksums-Sha256: 61b3baa90e16809b036cb41a6eb50e098a1aa200c994902b359107886f6345df 1980 gsmlib_1.10+20120414.gita5e5ae9a-0.2.dsc 3442b8004c12e362a5b1184af5a8f52047d3be8ee736de8f193f7ee4e764a4f6 24944 gsmlib_1.10+20120414.gita5e5ae9a-0.2.debian.tar.xz c2ee5d4114461901dd02c9b4892f26a276dc84f874f87175a83ef271063361b5 37114 libgsmme-dev_1.10+20120414.gita5e5ae9a-0.2_i386.deb d851756a77f05196d1c058af33dc952c6fb13a642caac12490704d9e53042736 182474 libgsmme1c2a_1.10+20120414.gita5e5ae9a-0.2_i386.deb 709a283d712720154ea344fe1d0e2e4260864f0a34d695b24f6c667c5f3b375d 107558 gsm-utils_1.10+20120414.gita5e5ae9a-0.2_i386.deb Files: a2a024b955023bd54a5a2639bfb41217 1980 comm extra gsmlib_1.10+20120414.gita5e5ae9a-0.2.dsc 242946d156a80108394060b7dd9c03a7 24944 comm extra gsmlib_1.10+20120414.gita5e5ae9a-0.2.debian.tar.xz b39aa56626e56ea6944a22ad940c9109 37114 libdevel extra libgsmme-dev_1.10+20120414.gita5e5ae9a-0.2_i386.deb 7447833ab0097ce4a830586bf7f7909b 182474 libs extra libgsmme1c2a_1.10+20120414.gita5e5ae9a-0.2_i386.deb 4453e6a332b8c6d2ad0316bc25632cd6 107558 comm extra gsm-utils_1.10+20120414.gita5e5ae9a-0.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iQIcBAEBCAAGBQJUNnGEAAoJEG6k0jEaLSaNdS8P/08AsMsMbWvDgQhomwC3QZdc
Bug#761171: marked as done (wagon2 fails to build in a non networked environment)
Your message dated Thu, 09 Oct 2014 11:49:12 + with message-id e1xccdy-0007d8...@franck.debian.org and subject line Bug#761171: fixed in wagon2 2.6-1.1 has caused the Debian Bug report #761171, regarding wagon2 fails to build in a non networked environment 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.) -- 761171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:wagon2 Version: 2.6-1 Severity: serious Tags: sid jessie the tests fail without network access: [...] T E S T S --- Running org.apache.maven.wagon.providers.http.HugeFileDownloadTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 51.61 sec Running org.apache.maven.wagon.providers.http.HttpClientWagonTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.maven.wagon.providers.http.AbstractHttpClientWagonTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.052 sec FAILURE! Results : Tests in error: test(org.apache.maven.wagon.providers.http.AbstractHttpClientWagonTest): repo.maven.apache.org: Name or service not known Tests run: 6, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [...] ---End Message--- ---BeginMessage--- Source: wagon2 Source-Version: 2.6-1.1 We believe that the bug you reported is fixed in the latest version of wagon2, 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 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated wagon2 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: Thu, 09 Oct 2014 13:27:03 +0200 Source: wagon2 Binary: libwagon2-java Architecture: source all Version: 2.6-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Matthias Klose d...@debian.org Description: libwagon2-java - resources' transport abstraction that is used in Maven Closes: 761171 Changes: wagon2 (2.6-1.1) unstable; urgency=medium . * Non-maintainer upload. * Disable test accessing the network (Eugene Zhukov). Closes: #761171. Checksums-Sha1: f7a05c917e1e478873c312fbe8be1bcc9f49ac01 2297 wagon2_2.6-1.1.dsc da82454487d39e4f9eb24e58017097a892cc938d 6988 wagon2_2.6-1.1.debian.tar.xz 67322db54eb7f80e80671b4ae9a2e9a3ef25db2a 1320494 libwagon2-java_2.6-1.1_all.deb Checksums-Sha256: f19ad18cf9e046e077f6effc9006bb756b42b74c9d73cc8ab7075a296669e54d 2297 wagon2_2.6-1.1.dsc e198e16560efd7d93e523c82c8c469a6dadb62e6cacc8c26c0fd6bb8714af622 6988 wagon2_2.6-1.1.debian.tar.xz 37fc867225ef210ce6d4c330c761bc3d79ac603641898130d70c71b6a466486d 1320494 libwagon2-java_2.6-1.1_all.deb Files: 90508a33b7caf23e867067744ec59175 2297 java optional wagon2_2.6-1.1.dsc 1167e88c264dd3b37a1d195b8ed25d67 6988 java optional wagon2_2.6-1.1.debian.tar.xz d1bcc85ec777be4389ca5c5884e1d8b1 1320494 java optional libwagon2-java_2.6-1.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlQ2cpEACgkQStlRaw+TLJyTzgCfQrEMJ0lYINIhsGfG/w4Ib/X4 HakAoKcT4q9ZIbq4kkzzOaxZOIY6cR33 =rXhb -END PGP SIGNATUREEnd Message---
Bug#764588: ffmpeg: fails to build from source in sid
Control: reassign -1 pbuilder Control: forcemerge 700591 -1 Control: affects 700591 ffmpeg Hi Holger, On 09.10.2014 12:57, Holger Levsen wrote: ffmpeg fails to build from source in sid in pbuilder as per attached log. It works fine in sid (and jessie), but ... make[1]: Leaving directory '/tmp/buildd/ffmpeg-2.4.1' debian/rules override_dh_auto_build-arch make[1]: Entering directory '/tmp/buildd/ffmpeg-2.4.1' sem_open: Function not implemented ... you use the pbuilder from stable, which doesn't work correctly, see bug #700591 [1]. Adding the following to your pbuilderrc should work around the problem: BINDMOUNTS=$BINDMOUNTS /run/shm Best regards, Andreas 1: https://bugs.debian.org/700591 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 2 errors): Re: Bug#764588: ffmpeg: fails to build from source in sid
Processing control commands: reassign -1 pbuilder Bug #764588 [src:ffmpeg] ffmpeg: fails to build from source in sid Bug reassigned from package 'src:ffmpeg' to 'pbuilder'. No longer marked as found in versions ffmpeg/2.4.1-1. Ignoring request to alter fixed versions of bug #764588 to the same values previously set forcemerge 700591 -1 Failed to forcibly merge 700591: Not altering archived bugs; see unarchive. affects 700591 ffmpeg Failed to mark 700591 as affecting package(s): Not altering archived bugs; see unarchive. -- 764588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764588 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#711629: marked as done (libjavascript-packer-perl: FTBFS with perl 5.18: test failure)
Your message dated Thu, 09 Oct 2014 12:04:14 + with message-id e1xccs6-0003ji...@franck.debian.org and subject line Bug#711629: fixed in libjavascript-packer-perl 1.006003-2 has caused the Debian Bug report #711629, regarding libjavascript-packer-perl: FTBFS with perl 5.18: test failure 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.) -- 711629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libjavascript-packer-perl Version: 1.006003-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.18-transition Tags: sid jessie This package FTBFS with perl 5.18 from experimental (in a clean sbuild session): # Failed test 'compression level shrink' # at t/02-io.t line 168. # Failed test 'compression level obfuscate' # at t/02-io.t line 168. # Failed test 'compression level best whith short javascript' # at t/02-io.t line 168. # Failed test 'compression level best whith long javascript' # at t/02-io.t line 168. # Failed test 'compression level shrink function as argument' # at t/02-io.t line 168. # Failed test 'compression level shrink with qouted args' # at t/02-io.t line 168. # Looks like you failed 6 tests of 30. t/02-io.t . Dubious, test returned 6 (wstat 1536, 0x600) Failed 6/30 subtests t/pod.t ... ok Test Summary Report --- t/02-io.t (Wstat: 1536 Tests: 30 Failed: 6) Failed tests: 2-5, 7, 9 Non-zero exit status: 6 Files=4, Tests=50, 1 wallclock secs ( 0.04 usr 0.02 sys + 0.35 cusr 0.02 csys = 0.43 CPU) Result: FAIL -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) ---End Message--- ---BeginMessage--- Source: libjavascript-packer-perl Source-Version: 1.006003-2 We believe that the bug you reported is fixed in the latest version of libjavascript-packer-perl, 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 711...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominique Dumont d...@debian.org (supplier of updated libjavascript-packer-perl 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: Thu, 09 Oct 2014 13:56:05 +0200 Source: libjavascript-packer-perl Binary: libjavascript-packer-perl Architecture: source all Version: 1.006003-2 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Dominique Dumont d...@debian.org Description: libjavascript-packer-perl - module to compact JavaScript code Closes: 711629 Changes: libjavascript-packer-perl (1.006003-2) unstable; urgency=low . * Team upload. . [ Salvatore Bonaccorso ] * Change Vcs-Git to canonical URI (git://anonscm.debian.org) * Change search.cpan.org based URIs to metacpan.org based URIs . [ gregor herrmann ] * debian/control: remove Nicholas Bamber from Uploaders on request of the MIA team. * Strip trailing slash from metacpan URLs. . [ Salvatore Bonaccorso ] * Update Vcs-Browser URL to cgit web frontend . [ Dominique Dumont ] * Fix FTBS due to random order of returned keys (Closes: #711629) * control: source Standards-Version: '3.9.3' - '3.9.6' Checksums-Sha1: 38b450e8b87357e5c457098a97d634494e60afd0 2344 libjavascript-packer-perl_1.006003-2.dsc 18b226b65778bb15f8645d74ba74c0c189901c20 5600 libjavascript-packer-perl_1.006003-2.debian.tar.xz e9dea0818010e4e526bbe1b15be438c3cae6f453 14282 libjavascript-packer-perl_1.006003-2_all.deb Checksums-Sha256: 63bf3ef8ceb4293ebe7529dcea6bdabb9908a22f81f79df7f7a6889de26c6fba 2344 libjavascript-packer-perl_1.006003-2.dsc bd4889de08bc203e5b79bdf97d27b2c2c532757d7b2e562402041cfe6be59b51 5600 libjavascript-packer-perl_1.006003-2.debian.tar.xz 6dafe94f3f2bcd3cd52019e2409fe044c52bfe2c69d0ef52ba048992f28864cd 14282 libjavascript-packer-perl_1.006003-2_all.deb Files: aff14aafc210901c1db64df35798fd23 14282 perl optional libjavascript-packer-perl_1.006003-2_all.deb a27de45d2bdcbd5bade925bc92a365bf 2344 perl optional libjavascript-packer-perl_1.006003-2.dsc
Processed: merge #764588 into #700591
Processing commands for cont...@bugs.debian.org:
unarchive 700591
Bug #700591 {Done: Junichi Uekawa dan...@debian.org} [pbuilder] [pbuilder]
Add support for shared memory mounting point
Unarchived Bug 700591
forcemerge 700591 764588
Bug #700591 {Done: Junichi Uekawa dan...@debian.org} [pbuilder] [pbuilder]
Add support for shared memory mounting point
Bug #764588 [pbuilder] ffmpeg: fails to build from source in sid
Severity set to 'normal' from 'serious'
Marked Bug as done
Marked as fixed in versions pbuilder/0.214.
Marked as found in versions pbuilder/0.213.
Added tag(s) patch.
Merged 700591 764588
affects 700591 ffmpeg
Bug #700591 {Done: Junichi Uekawa dan...@debian.org} [pbuilder] [pbuilder]
Add support for shared memory mounting point
Bug #764588 {Done: Junichi Uekawa dan...@debian.org} [pbuilder] ffmpeg: fails
to build from source in sid
Added indication that 700591 affects ffmpeg
Added indication that 764588 affects ffmpeg
archive 700591
Bug #700591 {Done: Junichi Uekawa dan...@debian.org} [pbuilder] [pbuilder]
Add support for shared memory mounting point
Bug #764588 {Done: Junichi Uekawa dan...@debian.org} [pbuilder] ffmpeg: fails
to build from source in sid
archived 700591 to archive/91 (from 700591)
archived 764588 to archive/88 (from 700591)
thanks
Stopping processing here.
Please contact me if you need assistance.
--
700591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700591
764588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764588
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#764552: hwclock-set misconfigures kernel for NTP when RTC holds local time
[CCing the new bug number] Am 09.10.2014 um 02:20 schrieb Ben Hutchings: On Thu, 2014-10-09 at 01:22 +0200, Michael Biebl wrote: Does ntp and hwclock --hctosys not play well together? Yes, that's it! If you use NTP and tell the kernel to adjust the system time, that causes the kernel to periodically write the system time to the RTC too, because the system time will be more accurate. For hysterical raisins, the first call to settimeofday() that specifies a 'time zone' (local time offset) implicitly sets whether the RTC is supposed to hold local time or UTC: if the time value is unspecified and the time offset is non-zero then the RTC holds local time, otherwise it holds UTC. There is no way to change this later! 'hwclock --hctosys' specifies both time value and time offset, and therefore implicitly configures the RTC to hold UTC (but only when NTP is used and it is written periodically by the kernel). So we absolutely have to run 'hwclock --systz' first. We could *also* run 'hwclock --hctosys' straight after that. Both variants seem to work here, i.e. systz only or hctosys *after* systz. Tested both, with and without ntp enabled, under systemd and sysvinit. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#761040: [libqtwebkit4] Browsers based on Webkit crash on loading pages
On Thursday 09 October 2014 13:04:12 Michel Dänzer wrote: [snip] Program terminated with signal SIGSEGV, Segmentation fault. Thanks a lot Michel! Upstream is now informed. -- Ud. está viendo a la persona que ven nuestros clientes. Leyenda pegada en el espejo de una empresa. 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#764595: mini-buildd: Can't GPG-verify changes files (since python-debian-0.1.23)
Package: mini-buildd
Version: 1.0.4
Severity: grave
Justification: renders package unusable
A reminder to myself, and for those wondering...
grave: As this basically prevents any package building.
Will be fixed asap, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764380
Workarounds:
(1)
Downgrade to python-debian 0.1.23
(2)
diff --git a/mini_buildd/ftpd.py b/mini_buildd/ftpd.py
index d763b32..46769a7 100644
--- a/mini_buildd/ftpd.py
+++ b/mini_buildd/ftpd.py
@@ -42,7 +42,7 @@ class Incoming(object):
if cls.is_changes(changes_file):
LOG.debug(Checking: {c}.format(c=changes_file))
try:
-for fd in
debian.deb822.Changes(mini_buildd.misc.open_utf8(changes_file)).get(Files,
[]):
+for fd in debian.deb822.Changes(open(changes_file,
r)).get(Files, []):
valid_files.append(fd[name])
LOG.debug(Valid: {c}.format(c=fd[name]))
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mini-buildd depends on:
ii adduser 3.113+nmu3
ii debconf [debconf-2.0] 1.5.53
ii debootstrap 1.0.63
ii devscripts 2.14.7
ii dpkg-dev1.17.16
ii gnupg 1.4.18-4
ii libjs-jquery1.7.2+dfsg-3.2
ii libjs-sphinxdoc 1.2.3+dfsg-1
ii lintian 2.5.28
ii mini-buildd-common 1.0.4
ii python-cherrypy33.5.0-1
ii python-daemon 1.5.5-1
ii python-django 1.7-2
ii python-django-extensions1.3.10-1
ii python-django-registration 1.0+dfsg-2
ii python-mini-buildd 1.0.4
ii python-pyftpdlib1.2.0-1
pn python:any none
ii reprepro4.16.0-1
ii sbuild 0.64.3-2
ii schroot 1.6.10-1+b1
ii sudo1.8.10p3-1
Versions of packages mini-buildd recommends:
ii python-apt 0.9.3.10
Versions of packages mini-buildd suggests:
pn binfmt-supportnone
ii debootstrap 1.0.63
pn haveged none
pn lvm2 none
pn qemu-user-static none
-- Configuration Files:
/etc/default/mini-buildd changed [not included]
/etc/sudoers.d/mini-buildd-sudoers [Errno 13] Permission denied:
u'/etc/sudoers.d/mini-buildd-sudoers'
-- debconf information excluded
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761650: llvm-toolchain-3.5: FTBFS on kfreebsd
Hi, On 08/10/14 01:35, Steven Chamberlain wrote: An updated lldb-kfreebsd-mi.diff is attached I just finished a test-build on kfreebsd-amd64 (this took 34 hours on my usual development machine... the VM I rented for this work before, could do this in about 2). Anyway, this patch fixes the build, *but* there are still problems with linker path and C++ includes. Probably the kfreebsd patches need updating from current clang-3.4 in sid, where these issues were solved already; I'll have a go at fixing that next. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Really adjusting bug severity for Bug#764212: [wine-development] Error in bash script, fi needed at line 28
Processing commands for cont...@bugs.debian.org: severity 764212 grave Bug #764212 [wine-development] [wine-development] Error in bash script, fi needed at line 28 Severity set to 'grave' from 'normal' found 764212 1.7.28-1 Bug #764212 [wine-development] [wine-development] Error in bash script, fi needed at line 28 There is no source info for the package 'wine-development' at version '1.7.28-1' with architecture '' Unable to make a source version for version '1.7.28-1' Marked as found in versions 1.7.28-1. thanks Stopping processing here. Please contact me if you need assistance. -- 764212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764212 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#759926: marked as done (ruby-database-cleaner: FTBFS: ERROR: Test ruby2.1 failed: Running tests for ruby2.1 using debian/ruby-tests.rake ...)
Your message dated Thu, 09 Oct 2014 13:50:43 + with message-id e1xce79-0001ar...@franck.debian.org and subject line Bug#759926: fixed in ruby-database-cleaner 1.3.0-1 has caused the Debian Bug report #759926, regarding ruby-database-cleaner: FTBFS: ERROR: Test ruby2.1 failed: Running tests for ruby2.1 using debian/ruby-tests.rake ... 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.) -- 759926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-database-cleaner Version: 1.2.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 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): Running tests for ruby2.1 using debian/ruby-tests.rake ... /usr/bin/ruby2.1 -S rspec ./spec/database_cleaner/active_record/base_spec.rb ./spec/database_cleaner/active_record/transaction_spec.rb ./spec/database_cleaner/active_record/truncation_spec.rb /usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find 'mysql' (~ 2.9) - did find: [mysql-2.8.2] (Gem::LoadError) from /usr/lib/ruby/2.1.0/rubygems/dependency.rb:309:in `to_spec' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_gem.rb:53:in `gem' from /usr/lib/ruby/vendor_ruby/active_record/connection_adapters/mysql_adapter.rb:5:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require' from /«PKGBUILDDIR»/spec/database_cleaner/active_record/truncation_spec.rb:3:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:22:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:80:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:17:in `block in autorun' /usr/bin/ruby2.1 -S rspec ./spec/database_cleaner/active_record/base_spec.rb ./spec/database_cleaner/active_record/transaction_spec.rb ./spec/database_cleaner/active_record/truncation_spec.rb failed ERROR: Test ruby2.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/08/30/ruby-database-cleaner_1.2.0-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. The build was done with DEB_BUILD_OPTIONS=parallel=4, so if your packaging tries to support this, it might be a good idea to explore whether this might be the cause of the failure. ---End Message--- ---BeginMessage--- Source: ruby-database-cleaner Source-Version: 1.3.0-1 We believe that the bug you reported is fixed in the latest version of ruby-database-cleaner, 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. Antonio Terceiro terce...@debian.org (supplier of updated ruby-database-cleaner 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, 08 Oct 2014 21:44:30 -0300 Source: ruby-database-cleaner Binary: ruby-database-cleaner Architecture: source all Version: 1.3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Antonio Terceiro terce...@debian.org
Bug#764212: Fwd: Bug#764212: [wine-development] Error in bash script, fi needed at line 28
2014-10-09 16:33 GMT+04:00, jre jre.wine...@gmail.com: Most parts of your patch aren't related to this bug but simply use another style (replacing spaces with tabs; using bash builtins [ ] instead of test (I would prefer that too); omitting (bad idea)). As already noted previously the patch for this bug is really just adding the missing fi (haven't tested it, but it seems obvious). Please search the web how to submit correct patches. Basically you should keep them minimal and adapt to the current style of the file that you want to patch. If you want other things changed in wine file another bug with your patch and describe what you did there for what purpose. Adding fi eliminates the symptoms but not the reason. The reason is code formatting. Compare original version: https://github.com/rockdrilla/debian-wine/blob/909e89b15464830946c36126b185de606ac2b446/debian/scripts/wine and rewritten version: https://github.com/rockdrilla/debian-wine/blob/1ba97892f23a5ae37dddb0ec89faea057959dbc9/debian/scripts/wine In my opinion, my script looks a little cleaner and clearer than the original. Besides, I have never encountered this bug - just saw your bug report and decided to help. -- SY, Konstantin Demin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764287: marked as done (GRUB before 2.02 doesn't support ZFS lz4 compression)
Your message dated Thu, 09 Oct 2014 13:50:29 + with message-id e1xce6v-00015t...@franck.debian.org and subject line Bug#764287: fixed in partman-zfs 39 has caused the Debian Bug report #764287, regarding GRUB before 2.02 doesn't support ZFS lz4 compression 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.) -- 764287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: partman-zfs Version: 39 Severity: critical Tags: pending User: debian-...@lists.debian.org Usertags: kfreebsd Hi, If d-i is running kfreebsd 10.1, lz4 will be active by default for newly-created ZFS pools. GRUB 2.02 (in sid) can boot from these, but GRUB 2.00 (in jessie) cannot. So, installing sid from sid d-i is fine. Installing jessie from sid d-i will fail to install a bootloader, if /boot or /lib/modules are in a newly-created ZFS pool. Installing jessie from jessie d-i Beta 2 is also fine, but new installs to ZFS could fail as above if kfreebsd 10.1 udebs migrate before GRUB 2.00 does. To avoid that happening, I'm changing the default to not enable lz4 in newly-created zpools. This change can be reverted as soon as GRUB migrates to jessie. Old zpools created by wheezy are not affected because lz4 is already disabled for them. Thanks. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: partman-zfs Source-Version: 39 We believe that the bug you reported is fixed in the latest version of partman-zfs, 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. Christian Perrier bubu...@debian.org (supplier of updated partman-zfs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 09 Oct 2014 14:16:40 +0200 Source: partman-zfs Binary: partman-zfs Architecture: source kfreebsd-i386 Version: 39 Distribution: unstable Urgency: high Maintainer: Debian Install System Team debian-b...@lists.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: partman-zfs - Add to partman support for ZFS (udeb) Closes: 764287 Changes: partman-zfs (39) unstable; urgency=high . [ Steven Chamberlain ] * Team upload. * When creating new zpools, disable optional features including lz4_compress, because that will require grub-pc 2.02~, which is in sid but not jessie yet. (Closes: #764287) Please revert this after grub-pc 2.02~ migrates. * Bump zfsutils dependency to upstream version 9.2 or later, with support for the zpool create -d flag required for the above Checksums-Sha1: 0f0b3f40db70e11923cf83ac516f25641a9dc4cd 1669 partman-zfs_39.dsc e562030e330f903cb0cbb2b4f3205fb75f2ae9b4 259420 partman-zfs_39.tar.xz 80929ab837b9efbbfe5b2add3f1bf180c1e2a062 331848 partman-zfs_39_kfreebsd-i386.udeb Checksums-Sha256: cc4f40d2024f0faa7c2a0b0440385eccbeeabd7ca522c1aa456805a6bc69765f 1669 partman-zfs_39.dsc e9d98dd7d2eb20c6bf1855e253cd7e35cd5c37f84f00d670ec0db9bd323e5b10 259420 partman-zfs_39.tar.xz 11b17324eaf5d79226e83b6b34f7d80b379b34b9f307e59166052bee7eb34460 331848 partman-zfs_39_kfreebsd-i386.udeb Files: 33576d3195457a9ff854de9f899feddd 1669 debian-installer standard partman-zfs_39.dsc c6209f2138c123e6e436e71ec5ca38a7 259420 debian-installer standard partman-zfs_39.tar.xz ce5f06b27edb387a438e80e8435b3364 331848 debian-installer standard partman-zfs_39_kfreebsd-i386.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJUNov2AAoJEIcvcCxNbiWoWKcP/RsVMjNZfcDWqFlAElRkwBun 9nbgUNdU5h5AVwhxGF1HSL0dt+21ALwc4uOliggKjX4sHevfJeXP0SRb1rwpsLD0 hqcoOXBEDrWQ3l7cmxjGfaFAxcpPnBCD9r/3EeqJYK7fn/rM52r7DgpS+fdBKS8s aAsG+VOECdp2+JI9vpB1JBdFqPu8c9IQpJIinH6+Zy+dCRp5Ypjl3y8+sm6MGyIQ yCJmEb1j/97UzIdEX4XK0D/dk5gpls1muzUZC6wJKxmsbr3M3blRNzna/mVsE9EC
Bug#764561: Bug#764563: pocl: FTBFS: test suite errors and FTBFS on ppc64el
severity 764561 important severity 764563 important thanks Vincent Danjean vdanjean...@free.fr writes: Thank for your report. As pocl is a new package, do you really think it deserve a serious bug (that block migration to testing?) Upstream No, I accidentally specified the wrong severity; fixed. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- 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#764563: pocl: FTBFS: test suite errors and FTBFS on ppc64el
Processing commands for cont...@bugs.debian.org:
severity 764561 important
Bug #764561 [src:pocl] pocl: FTBFS on ppc64el: trouble with {true,false}_type
Severity set to 'important' from 'serious'
severity 764563 important
Bug #764563 [src:pocl] pocl: FTBFS: test suite errors
Severity set to 'important' from 'serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
764561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764561
764563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764563
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#758121: [Pkg-crosswire-devel] Bug#758121: bibletime: Bibletime is unusable in testing and unstable
On Thursday, October 09, 2014 10:55:59 AM Dimitri John Ledkov wrote: On 8 October 2014 15:54, da...@sandersweb.net wrote: retitle 758121 bibletime: New upstream release fixes display problem in jessie severity 758121 grave thanks On Monday, October 06, 2014 10:26:56 PM you wrote: Bibletime is unusable in jessie and sid. When you open any Bible or commentary all you see is jibberish. This needs to be fixed prior to the release of jessie. I just built the new upstream release (2.10.1) from source. It does not have this problem. Please update the bibletime package in jessie to the latest upstream release available on sourceforge. Debdiff would be appreciated. I don't use, nor typically updated bibletime. Dimitri, I don't have a deb of version 2.10.1 to create a debdiff with. I think the package can be built from source without any patches and with minimum trouble. I may try to create a deb but I'm not a debian developer so I may be unsuccessful. Any help would be appreciated. David -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745969: guile-1.8: FTBFS: conflicting types for 'yyget_leng'
Edmund Grimley Evans edmund.grimley.ev...@gmail.com writes: In case anyone still wants to build guile-1.8, a fix (remove declarations of 'yy*' functions in c-tokenize.lex) is described here: http://lists.gnu.org/archive/html/guile-devel/2010-03/msg00081.html It seems to work on arm64. For what it's worth, early next week I'm planning to determine whether or not guile-1.8 is going to stay in jessie. I'm still hoping we can remove it, but we'll see. We're down to very few rdepends. 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
Processed: reassign 764571 to libpoclu-dev, affects 764571
Processing commands for cont...@bugs.debian.org: reassign 764571 libpoclu-dev 0.10-3 Bug #764571 [uthash-dev,libpoclu-dev] libpoclu-dev and uthash-dev: error when trying to install together Bug reassigned from package 'uthash-dev,libpoclu-dev' to 'libpoclu-dev'. Ignoring request to alter found versions of bug #764571 to the same values previously set Ignoring request to alter fixed versions of bug #764571 to the same values previously set Bug #764571 [libpoclu-dev] libpoclu-dev and uthash-dev: error when trying to install together Marked as found in versions pocl/0.10-3. affects 764571 uthash-dev Bug #764571 [libpoclu-dev] libpoclu-dev and uthash-dev: error when trying to install together Added indication that 764571 affects uthash-dev thanks Stopping processing here. Please contact me if you need assistance. -- 764571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 746493 important Bug #746493 [gluegen2] Wrong guess on the endianness of powerpc Severity set to 'important' from 'grave' End of message, stopping processing here. Please contact me if you need assistance. -- 746493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746493 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#762087: samba-ad-dc script doesn't check for running process in stop
I am not running an ad-dc samba server, the role is 'auto', so that process never gets started. At the top of the 'start' stanza we see: SERVER_ROLE=`samba-tool testparm --parameter-name=server role 2/dev/null | tail -1` if [ $SERVER_ROLE != active directory domain controller ]; then exit 0 - but no such check exists in the 'stop' case. I think that could be the root cause of samba not shutting down and would explain why samba-ad-dc is in 'waiting' state: waiting for 'start-stop-daemon' to complete on a non-existent process. When I manually kill the '/etc/init.d/samba-ad-dc stop' process the samba service ends quickly. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764611: sonata: fails to launch since GLib upgrade to 2.42
Package: sonata Version: 1.6.2.1-6 Severity: grave Justification: renders package unusable Since upgrade of libglib2.0-0 to version 2.42.0, sonata fails to launch with the following error: Attempt to unlock mutex that was not locked -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (900, 'stable-updates'), (900, 'oldstable-updates'), (900, 'unstable'), (900, 'testing'), (900, 'stable'), (900, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sonata depends on: ii python 2.7.8-1 ii python-dbus 1.2.0-2+b3 ii python-gtk2 2.24.0-4 ii python-mpd 0.3.0-4 Versions of packages sonata recommends: pn python-eggtrayicon none ii python-tagpy2013.1-4 Versions of packages sonata suggests: pn python-mmkeys none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758956: marked as done (quisk: Please update to use wxpython3.0)
Your message dated Thu, 09 Oct 2014 15:59:43 + with message-id e1xcg7z-0003mq...@franck.debian.org and subject line Bug#758956: fixed in quisk 3.6.18-2 has caused the Debian Bug report #758956, regarding quisk: 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.) -- 758956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: quisk Version: 3.6.16-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: quisk Source-Version: 3.6.18-2 We believe that the bug you reported is fixed in the latest version of quisk, 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. A. Maitland Bottoms bott...@debian.org (supplier of updated quisk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 09 Oct 2014 07:10:40 -0400 Source: quisk Binary: quisk Architecture: source amd64 Version: 3.6.18-2 Distribution: unstable Urgency: low Maintainer: A. Maitland Bottoms bott...@debian.org Changed-By: A. Maitland Bottoms bott...@debian.org Description: quisk - Software Defined Radio (SDR) Closes: 758956 Changes: quisk (3.6.18-2) unstable; urgency=low . * Update runtime dependency to python-wxgtk3.0 (Closes: #758956) Checksums-Sha1: 42b4e905915c71131cb3d5274eb9f09a1fb6f3b2 2111 quisk_3.6.18-2.dsc cdcbe350756f009bf594d98370950c3f3966add7 8816 quisk_3.6.18-2.debian.tar.xz 1a3961cc5ed397fb5ee7aab6c4f98fcbc39684cd 262048 quisk_3.6.18-2_amd64.deb Checksums-Sha256:
Bug#764617: mini-buildd: Chroot build setup broken (since sbuild-0.63.3)
Package: mini-buildd Version: 1.0.4 Severity: grave Justification: renders package unusable FTR: In sbuild-0.63.3 this bug has been fixed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607228 Unfortunately, the workaround in mini-buildd for that bug now actually breaks mini-buildd now the bug is fixed ;). Upcoming release will have the workaround removed, of course, and eventually close this. In the meantime, the workaround to make the obsoleted workaround work again is to install any sbuild 0.63.3. Hth, S -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mini-buildd depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.53 ii debootstrap 1.0.63 ii devscripts 2.14.7 ii dpkg-dev1.17.16 ii gnupg 1.4.18-4 ii libjs-jquery1.7.2+dfsg-3.2 ii libjs-sphinxdoc 1.2.3+dfsg-1 ii lintian 2.5.28 ii mini-buildd-common 1.0.4 ii python-cherrypy33.5.0-1 ii python-daemon 1.5.5-1 ii python-django 1.7-2 ii python-django-extensions1.3.10-1 ii python-django-registration 1.0+dfsg-2 ii python-mini-buildd 1.0.4 ii python-pyftpdlib1.2.0-1 pn python:any none ii reprepro4.16.0-1 ii sbuild 0.64.3-2 ii schroot 1.6.10-1+b1 ii sudo1.8.10p3-1 Versions of packages mini-buildd recommends: ii python-apt 0.9.3.10 Versions of packages mini-buildd suggests: pn binfmt-supportnone ii debootstrap 1.0.63 pn haveged none pn lvm2 none pn qemu-user-static none -- Configuration Files: /etc/default/mini-buildd changed [not included] /etc/sudoers.d/mini-buildd-sudoers [Errno 13] Permission denied: u'/etc/sudoers.d/mini-buildd-sudoers' -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764619: aptly: Depends on non-existent package gpg
Package: aptly Version: 0.8-2 Severity: serious Dear Maintainer, aptly 0.8-2 is uninstallable, because it depends on gpg which does not exist: Depends: bzip2, gpg, gpgv, libc6 (= 2.2.5) You likely meant gnupg: gnupg: Installed: 1.4.18-4 Candidate: 1.4.18-4 Version table: *** 1.4.18-4 0 990 http://ftp.ch.debian.org/debian/ sid/main amd64 Packages 600 http://ftp.ch.debian.org/debian/ testing/main amd64 Packages 100 /var/lib/dpkg/status gpg: Installed: (none) Candidate: (none) Version table: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (110, 'experimental'), (109, 'buildd-unstable'), (109, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages aptly depends on: ii libc6 2.19-11 aptly recommends no packages. aptly suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 764615 to samba, forcibly merging 740942 764615
Processing commands for cont...@bugs.debian.org: reassign 764615 samba Bug #764615 [systemd] systemd: The duration of the stop of certain services by Systemd achieves 5 minutes Bug reassigned from package 'systemd' to 'samba'. No longer marked as found in versions systemd/215-5. Ignoring request to alter fixed versions of bug #764615 to the same values previously set forcemerge 740942 764615 Bug #740942 [samba] [samba] /etc/init.d/samba forbit systemd shutdown system Bug #759358 [samba] samba: Samba did not clean rc(x).d files and this lef over cause systemd to hang for 5 min Bug #761953 [samba] systemd: Hangup in shutdown process Bug #762002 [samba] [systemd] shutdown waiting 5 minutes for samba Bug #762087 [samba] samba: systemd and samba stop computer wait of 5 minutes Bug #764615 [samba] systemd: The duration of the stop of certain services by Systemd achieves 5 minutes Severity set to 'grave' from 'important' Added indication that 764615 affects systemd Marked as found in versions samba/2:4.1.11+dfsg-1 and samba/2:4.1.5+dfsg-1. Bug #759358 [samba] samba: Samba did not clean rc(x).d files and this lef over cause systemd to hang for 5 min Bug #761953 [samba] systemd: Hangup in shutdown process Bug #762002 [samba] [systemd] shutdown waiting 5 minutes for samba Bug #762087 [samba] samba: systemd and samba stop computer wait of 5 minutes Merged 740942 759358 761953 762002 762087 764615 thanks Stopping processing here. Please contact me if you need assistance. -- 740942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740942 759358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759358 761953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761953 762002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762002 762087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762087 764615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764615 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#762087: samba-ad-dc script doesn't check for running process in stop
Dominique Brazziel ha scritto il 09/10/2014 alle 17:17: I am not running an ad-dc samba server, the role is 'auto', so that process never gets started. In my case the role is standalone server but the result is the same, the server is not started due to the check in the 'start' stanza and the stop job looks for a process that doesn't exist. -- Massimo Maiurana Ragusa (RG) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764619: marked as done (aptly: Depends on non-existent package gpg)
Your message dated Thu, 09 Oct 2014 16:48:46 + with message-id e1xcgts-0004oi...@franck.debian.org and subject line Bug#764619: fixed in aptly 0.8-3 has caused the Debian Bug report #764619, regarding aptly: Depends on non-existent package gpg 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.) -- 764619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: aptly Version: 0.8-2 Severity: serious Dear Maintainer, aptly 0.8-2 is uninstallable, because it depends on gpg which does not exist: Depends: bzip2, gpg, gpgv, libc6 (= 2.2.5) You likely meant gnupg: gnupg: Installed: 1.4.18-4 Candidate: 1.4.18-4 Version table: *** 1.4.18-4 0 990 http://ftp.ch.debian.org/debian/ sid/main amd64 Packages 600 http://ftp.ch.debian.org/debian/ testing/main amd64 Packages 100 /var/lib/dpkg/status gpg: Installed: (none) Candidate: (none) Version table: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (110, 'experimental'), (109, 'buildd-unstable'), (109, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages aptly depends on: ii libc6 2.19-11 aptly recommends no packages. aptly suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: aptly Source-Version: 0.8-3 We believe that the bug you reported is fixed in the latest version of aptly, 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 aptly 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: Thu, 09 Oct 2014 18:41:38 +0200 Source: aptly Binary: aptly Architecture: source amd64 Version: 0.8-3 Distribution: unstable Urgency: medium Maintainer: Sebastien Delafond s...@debian.org Changed-By: Sebastien Delafond s...@debian.org Description: aptly - Swiss army knife for Debian repository management Closes: 764619 764622 Changes: aptly (0.8-3) unstable; urgency=medium . * Correct Vcs-Browser entry (Closes: #764622) * Correct dependency from gpg to gnupg (Closes: #764619) Checksums-Sha1: f86174e4fbfdc8d6d01cfe43b5cb835117c80545 1184 aptly_0.8-3.dsc d9b498674fcb792089fefcf695250bad06c3886e 5908 aptly_0.8-3.debian.tar.xz b46a30723b9fba49ac41ae15a5ccf1d3716fe26a 1989656 aptly_0.8-3_amd64.deb Checksums-Sha256: 8c192c93ed2c21a0dcaff6e7d8962785d0f668a7abefe688d4a1a23a543ab746 1184 aptly_0.8-3.dsc c7dca508ff86d50dd6da6da32c611c0d0d46bec181f08b5af445d2c8480974d0 5908 aptly_0.8-3.debian.tar.xz 4b56da3572941e4dd4261ca4908b37d2b1a78f6a607d78bfff92719d998338d9 1989656 aptly_0.8-3_amd64.deb Files: 763f80722a269d5fd5b2e4aad65a285c 1989656 utils extra aptly_0.8-3_amd64.deb bead63e407f8aca04815fd97ff16598f 1184 utils extra aptly_0.8-3.dsc a6186090f357c61b4b0b4e53ea698b24 5908 utils extra aptly_0.8-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlQ2uwgACgkQiZgNKcDdyD+2jACgkSENlpJF5aT4WdcINZlIo4Jg l+4AoMfqx2FzT3NBPu6k1qhp69bLob9A =vKBz -END PGP SIGNATUREEnd Message---
Bug#758121: [Pkg-crosswire-devel] Bug#758121: bibletime: Bibletime is unusable in testing and unstable
On Thursday, October 09, 2014 10:27:48 AM David Sanders wrote:
On Thursday, October 09, 2014 10:55:59 AM Dimitri John Ledkov wrote:
On 8 October 2014 15:54, da...@sandersweb.net wrote:
retitle 758121 bibletime: New upstream release fixes display problem in
jessie severity 758121 grave
thanks
On Monday, October 06, 2014 10:26:56 PM you wrote:
Bibletime is unusable in jessie and sid. When you open any Bible or
commentary all you see is jibberish. This needs to be fixed prior to
the release of jessie.
I just built the new upstream release (2.10.1) from source. It does not
have this problem. Please update the bibletime package in jessie to the
latest upstream release available on sourceforge.
Debdiff would be appreciated. I don't use, nor typically updated
bibletime.
Dimitri,
I don't have a deb of version 2.10.1 to create a debdiff with. I think the
package can be built from source without any patches and with minimum
trouble. I may try to create a deb but I'm not a debian developer so I may
be unsuccessful. Any help would be appreciated.
David
Alright I built a deb package for version 2.10.1-1. I've attached your debdiff
and the debian directory I used. Let me know if you need anything else.
David
david@deb8vm:~/Downloads$ debdiff bibletime_2.9.2-1.1+b1_amd64.deb
bibletime/bibletime_2.10.1-1_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in first .deb but not in second
-
-rw-r--r-- root/root /usr/share/doc/bibletime/changelog.Debian.amd64.gz
Control files: lines which differ (wdiff format)
Depends: libc6 (= 2.14), libclucene-core1 (= 2.3.3.4), [-libcurl3-gnutls (=
7.16.2),-] libgcc1 (= 1:4.1.1), libqt4-dbus (= 4:4.5.3), libqt4-network (=
4:4.5.3), libqt4-xml (= 4:4.5.3), libqt4-xmlpatterns (= 4:4.5.3), libqtcore4
(= 4:4.8.0), libqtgui4 (= 4:4.8.0), libqtwebkit4 (= 2.1.0~2011week13),
libstdc++6 (= 4.6), libsword11 (= 1.7.3+dfsg), [-zlib1g (= 1:1.1.4),-]
libqt4-svg (= 4.4.0), bibletime-data (= [-2.9.2-1.1)-] {+2.10.1-1)+}
Installed-Size: [-2378-] {+2959+}
[-Source: bibletime (2.9.2-1.1)-]
Version: [-2.9.2-1.1+b1-] {+2.10.1-1+}
david@deb8vm:~/Downloads$ debdiff bibletime-data_2.9.2-1.1_all.deb
bibletime/bibletime-data_2.10.1-1_all.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in second .deb but not in first
-
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/hdbk-config.html
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/hdbk-intro.html
-rw-r--r-- root/root
/usr/share/bibletime/docs/handbook/fi/hdbk-op-bookshelfmanager.html
-rw-r--r-- root/root
/usr/share/bibletime/docs/handbook/fi/hdbk-op-output.html
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/hdbk-op-parts.html
-rw-r--r-- root/root
/usr/share/bibletime/docs/handbook/fi/hdbk-op-search.html
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/hdbk-op.html
-rw-r--r-- root/root
/usr/share/bibletime/docs/handbook/fi/hdbk-reference-shortcuts.html
-rw-r--r-- root/root
/usr/share/bibletime/docs/handbook/fi/hdbk-reference-works.html
-rw-r--r-- root/root
/usr/share/bibletime/docs/handbook/fi/hdbk-reference.html
-rw-r--r-- root/root
/usr/share/bibletime/docs/handbook/fi/hdbk-start-firstrun.html
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/hdbk-term.html
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_back.png
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_bible.png
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_bible_add.png
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_bibletime.png
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_book.png
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_book_add.png
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_bookmark.png
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_books.png
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_cascade.png
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_checkbox.png
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_commentary.png
-rw-r--r-- root/root
/usr/share/bibletime/docs/handbook/fi/i_commentary_add.png
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_configure.png
-rw-r--r-- root/root
/usr/share/bibletime/docs/handbook/fi/i_configuresword.png
-rw-r--r-- root/root /usr/share/bibletime/docs/handbook/fi/i_contents2.png
-rw-r--r-- root/root
/usr/share/bibletime/docs/handbook/fi/i_displayconfig.png
-rw-r--r-- root/root
/usr/share/bibletime/docs/handbook/fi/i_document_magnifier.png
-rw-r--r-- root/root
Bug#762417: [Pkg-libvirt-maintainers] Bug#762417: vinagre: cannot connect - libgrypt error?
On 2014-10-07 Guido Günther a...@sigxcpu.org wrote: On Tue, Oct 07, 2014 at 12:16:51PM +0900, Norbert Preining wrote: [...] Is there any progress with respect to this introduced bug? Especially introducing such a grave bug in an NMU was a bit a surprise for me. I did see this but didn't have time to look into it yet but maybe Andreas can shed some light on this? Hello, I am sorry but I have not had time to look at the issue either. Real life is currently taking its toll. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764611: Problem persists with 2.42.0-2
Hello, The issue persists with exactly the same symptoms in the patched version which recently made its way into testing. Same w/ deadbeef, albeit that is a deb-mm package. -KS
Bug#680804: marked as done (odin: FTBFS: checking for blitz/tinyvec-et.h... no (removed in blitz++ 1:0.10-1))
Your message dated Thu, 09 Oct 2014 18:04:08 +
with message-id e1xci4o-0004xa...@franck.debian.org
and subject line Bug#680804: fixed in odin 1.8.8-1
has caused the Debian Bug report #680804,
regarding odin: FTBFS: checking for blitz/tinyvec-et.h... no (removed in
blitz++ 1:0.10-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.)
--
680804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: odin
Version: 1.8.5-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120708 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not
for C [enabled by default]
configure:8829: $? = 0
configure:8842: result: no
configure:8862: checking for gcc option to produce PIC
configure:9134: result: -fPIC -DPIC
configure:9146: checking if gcc PIC flag -fPIC -DPIC works
configure:9164: gcc -c -g -O2 -fPIC -DPIC -DPIC conftest.c 5
configure:9168: $? = 0
configure:9181: result: yes
configure:9205: checking if gcc static flag -static works
configure:9233: result: yes
configure:9248: checking if gcc supports -c -o file.o
configure:9269: gcc -c -g -O2 -o out/conftest2.o conftest.c 5
configure:9273: $? = 0
configure:9295: result: yes
configure:9303: checking if gcc supports -c -o file.o
configure:9350: result: yes
configure:9383: checking whether the gcc linker (/usr/bin/ld -m elf_x86_64)
supports shared libraries
configure:10374: result: yes
configure:10411: checking whether -lc should be explicitly linked in
configure:10416: gcc -c -g -O2 conftest.c 5
configure:10419: $? = 0
configure:10434: gcc -shared conftest.o -v -Wl,-soname -Wl,conftest -o
conftest 2\\1 \| /bin/grep -lc \/dev/null 2\\1
configure:10437: $? = 0
configure:10449: result: no
configure:10613: checking dynamic linker characteristics
configure:11046: gcc -o conftest -g -O2 -Wl,-rpath -Wl,/foo conftest.c 5
configure:11046: $? = 0
configure:11276: result: GNU/Linux ld.so
configure:11378: checking how to hardcode library paths into programs
configure:11403: result: immediate
configure:11923: checking whether stripping libraries is possible
configure:11928: result: yes
configure:11963: checking if libtool supports shared libraries
configure:11965: result: yes
configure:11968: checking whether to build shared libraries
configure:11989: result: yes
configure:11992: checking whether to build static libraries
configure:11996: result: yes
configure:12146: checking for ld used by g++
configure:12213: result: /usr/bin/ld -m elf_x86_64
configure:12220: checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld
configure:12235: result: yes
configure:12290: checking whether the g++ linker (/usr/bin/ld -m elf_x86_64)
supports shared libraries
configure:13203: result: yes
configure:13231: g++ -c -O3 -fno-tree-vectorize conftest.cpp 5
configure:13234: $? = 0
configure:13416: checking for g++ option to produce PIC
configure:13733: result: -fPIC -DPIC
configure:13742: checking if g++ PIC flag -fPIC -DPIC works
configure:13760: g++ -c -O3 -fno-tree-vectorize -fPIC -DPIC -DPIC
conftest.cpp 5
configure:13764: $? = 0
configure:13777: result: yes
configure:13798: checking if g++ static flag -static works
configure:13826: result: yes
configure:13838: checking if g++ supports -c -o file.o
configure:13859: g++ -c -O3 -fno-tree-vectorize -o out/conftest2.o
conftest.cpp 5
configure:13863: $? = 0
configure:13885: result: yes
configure:13890: checking if g++ supports -c -o file.o
configure:13937: result: yes
configure:13967: checking whether the g++ linker (/usr/bin/ld -m elf_x86_64)
supports shared libraries
configure:13996: result: yes
configure:14133: checking dynamic linker characteristics
configure:14514: g++ -o conftest -O3 -fno-tree-vectorize-Wl,-rpath
-Wl,/foo conftest.cpp 5
configure:14514: $? = 0
configure:14744: result: GNU/Linux ld.so
configure:14795: checking how to hardcode library paths into programs
configure:14820: result: immediate
configure:14906: checking for sin in -lm
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=${prefix}/include --mandir=${prefix}/share/man
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--libexecdir=${prefix}/lib/odin --disable-maintainer-mode
--disable-dependency-tracking --with-qt-dir=/usr/share/qt4
Bug#707462: marked as done (odin: FTBFS: ld: cannot find -lg2c)
Your message dated Thu, 09 Oct 2014 18:04:08 + with message-id e1xci4o-0004xa...@franck.debian.org and subject line Bug#680804: fixed in odin 1.8.8-1 has caused the Debian Bug report #680804, regarding odin: FTBFS: ld: cannot find -lg2c 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.) -- 680804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: odin Version: 1.8.5-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C [enabled by default] configure:8829: $? = 0 configure:8842: result: no configure:8862: checking for gcc option to produce PIC configure:9134: result: -fPIC -DPIC configure:9146: checking if gcc PIC flag -fPIC -DPIC works configure:9164: gcc -c -g -O2 -fPIC -DPIC -DPIC conftest.c 5 configure:9168: $? = 0 configure:9181: result: yes configure:9205: checking if gcc static flag -static works configure:9233: result: yes configure:9248: checking if gcc supports -c -o file.o configure:9269: gcc -c -g -O2 -o out/conftest2.o conftest.c 5 configure:9273: $? = 0 configure:9295: result: yes configure:9303: checking if gcc supports -c -o file.o configure:9350: result: yes configure:9383: checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries configure:10374: result: yes configure:10411: checking whether -lc should be explicitly linked in configure:10416: gcc -c -g -O2 conftest.c 5 configure:10419: $? = 0 configure:10434: gcc -shared conftest.o -v -Wl,-soname -Wl,conftest -o conftest 2\\1 \| /bin/grep -lc \/dev/null 2\\1 configure:10437: $? = 0 configure:10449: result: no configure:10613: checking dynamic linker characteristics configure:11046: gcc -o conftest -g -O2 -Wl,-rpath -Wl,/foo conftest.c 5 configure:11046: $? = 0 configure:11276: result: GNU/Linux ld.so configure:11378: checking how to hardcode library paths into programs configure:11403: result: immediate configure:11923: checking whether stripping libraries is possible configure:11928: result: yes configure:11963: checking if libtool supports shared libraries configure:11965: result: yes configure:11968: checking whether to build shared libraries configure:11989: result: yes configure:11992: checking whether to build static libraries configure:11996: result: yes configure:12146: checking for ld used by g++ configure:12213: result: /usr/bin/ld -m elf_x86_64 configure:12220: checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld configure:12235: result: yes configure:12290: checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries configure:13203: result: yes configure:13231: g++ -c -O3 -fno-tree-vectorize conftest.cpp 5 configure:13234: $? = 0 configure:13416: checking for g++ option to produce PIC configure:13733: result: -fPIC -DPIC configure:13742: checking if g++ PIC flag -fPIC -DPIC works configure:13760: g++ -c -O3 -fno-tree-vectorize -fPIC -DPIC -DPIC conftest.cpp 5 configure:13764: $? = 0 configure:13777: result: yes configure:13798: checking if g++ static flag -static works configure:13826: result: yes configure:13838: checking if g++ supports -c -o file.o configure:13859: g++ -c -O3 -fno-tree-vectorize -o out/conftest2.o conftest.cpp 5 configure:13863: $? = 0 configure:13885: result: yes configure:13890: checking if g++ supports -c -o file.o configure:13937: result: yes configure:13967: checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries configure:13996: result: yes configure:14133: checking dynamic linker characteristics configure:14514: g++ -o conftest -O3 -fno-tree-vectorize-Wl,-rpath -Wl,/foo conftest.cpp 5 configure:14514: $? = 0 configure:14744: result: GNU/Linux ld.so configure:14795: checking how to hardcode library paths into programs configure:14820: result: immediate configure:14906: checking for sin in -lm configure:14931: g++ -o conftest -I/usr/include/vtk-5.4 -I/usr/include/vtk-5.6 -I/usr/include/vtk-5.8 -O3 -fno-tree-vectorize -I/usr/include/vtk-5.4 -I/usr/include/vtk-5.6 -I/usr/include/vtk-5.8 -lvtkGraphics -lvtkFiltering -lQtGui -lQtCore -lofstd -loflog -lpthread -lz conftest.cpp -lm 5 configure:14931: $? = 0 configure:14940: result: yes configure:14948:
Processed: josm-plugins update to fix RC bug
Processing control commands: tags -1 help Bug #764176 [josm-plugins] josm-plugins: not installable in sid Added tag(s) help. -- 764176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764176 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#764176: josm-plugins update to fix RC bug
Control: tags -1 help Hi, I have managed to successfully download and import the latest josm-plugin tarball (svn30708). After adjusting all the dependencies to suit the latest version of josm, I failed to get it building. One of the patches did not apply cleanly. It turns out that the target name=revision part of build-common.xml which was being removed in the previous patch, has now been split into 3 (revision-svn, revision-svn2git revision-git). I hoped that deleting all 3 in the same way would do the job - but no. My knowledge of ant and it's build system is zero, so it will take me some time to investigate further. Maybe someone else would see the answer faster! I would like to be able to git push what I have done so far, but I do not have permissions for pkg-osm. My plan (if I succeeded) was to ask if anyone had any objections switching this package to pkg-grass. Should I create a new respository and stick it there anyway so anyone able to help can jump in? Cheers, Ross PS: In case it helps, the build fails in this way: debian/rules override_dh_auto_clean make[1]: Entering directory `/home/ross/debian/build-area/josm-plugins-0.0.svn30708+ds1' dh_auto_clean -Sant -- -f /home/ross/debian/build-area/josm-plugins-0.0.svn30708+ds1/debian/master.xml Buildfile: /home/ross/debian/build-area/josm-plugins-0.0.svn30708+ds1/debian/master.xml clean: BUILD FAILED /home/ross/debian/build-area/josm-plugins-0.0.svn30708+ds1/debian/master.xml:60: The following error occurred while executing this line: Target revision does not exist in the project colorscheme. It is used from target dist. Total time: 1 second dh_auto_clean: ant clean -f /home/ross/debian/build-area/josm-plugins-0.0.svn30708+ds1/debian/master.xml returned exit code 1 make[1]: *** [override_dh_auto_clean] Error 1 make[1]: Leaving directory `/home/ross/debian/build-area/josm-plugins-0.0.svn30708+ds1' make: *** [clean] Error 2 dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 gbp:error: Couldn't run 'git-pbuilder': git-pbuilder returned 2 signature.asc Description: OpenPGP digital signature
Bug#764318: libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs
On Tue, Oct 07, 2014 at 10:39:20AM +0200, Ondřej Surý wrote: 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. This conflicts would be unwarranted and go against Debian policy interoperability principle. If you like to keep providing libjpeg-turbo-progs, I suggest you rename all the binaries in libjpeg-turbo-progs with -turbo postfix or similar. Then, we could set up the alternative system to allow the user to choose between the two set of binaries. Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764499: marked as done (Fix build failure with python2.7 and PEP 466)
Your message dated Thu, 09 Oct 2014 19:05:25 + with message-id e1xcj1h-0007fj...@franck.debian.org and subject line Bug#764499: fixed in python-gevent 1.0.1-1 has caused the Debian Bug report #764499, regarding Fix build failure with python2.7 and PEP 466 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.) -- 764499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:python-gevent Version: 1.0-2 Severity: serious Tags: sid jessie patch Fix build failure with python2.7 and PEP 466 patch at http://launchpadlibrarian.net/186834363/python-gevent_1.0-2_1.0-2ubuntu1.diff.gz ---End Message--- ---BeginMessage--- Source: python-gevent Source-Version: 1.0.1-1 We believe that the bug you reported is fixed in the latest version of python-gevent, 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. Laszlo Boszormenyi (GCS) g...@debian.org (supplier of updated python-gevent 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, 08 Oct 2014 16:20:29 + Source: python-gevent Binary: python-gevent-dbg python-gevent-doc python-gevent Architecture: source amd64 all Version: 1.0.1-1 Distribution: unstable Urgency: low Maintainer: Laszlo Boszormenyi (GCS) g...@debian.org Changed-By: Laszlo Boszormenyi (GCS) g...@debian.org Description: python-gevent - gevent is a coroutine-based Python networking library python-gevent-dbg - gevent is a coroutine-based Python networking library - debugging python-gevent-doc - gevent is a coroutine-based Python networking library - documenta Closes: 694750 700731 747283 764499 Changes: python-gevent (1.0.1-1) unstable; urgency=low . * New upstream release, fixes thread switch detection (closes: #694750). * Fix sphinx build problem (closes: #700731). * Tighten greenlet dependency (closes: #747283). * Update Standards-Version to 3.9.6 . * Sync with Ubuntu. . [ Matthias Klose d...@ubuntu.com ] * Fix build failure with python2.7 and PEP 466 (closes: #764499). Checksums-Sha1: 82df9013d5637ab617551d814bec29e86739ba58 2019 python-gevent_1.0.1-1.dsc 2cc1b6e1fa29b30ea881fa6a195e57faaf089ae8 1455636 python-gevent_1.0.1.orig.tar.gz dbbba27c4f7b115859216248b96991f83fa69219 72244 python-gevent_1.0.1-1.debian.tar.xz 61c4e6a0c4342ce850ebee54810db844a2e51947 1359328 python-gevent-dbg_1.0.1-1_amd64.deb a593535bbb1c77fe99229fbdf78d640bc11f0f29 140102 python-gevent-doc_1.0.1-1_all.deb efb76a7a6144fdfda535bae5dea99cf79d150cfb 231740 python-gevent_1.0.1-1_amd64.deb Checksums-Sha256: b0ea156fdde6ff92801281d8fe30fb7eee42a01a65632dd53840c5fc8a660f11 2019 python-gevent_1.0.1-1.dsc 4627e215d058f71d95e6b26d9e7be4c263788a4756bd2858a93775f6c072df43 1455636 python-gevent_1.0.1.orig.tar.gz 546eba9fa29187022a433f787250d3e71405b5391c0754cd0abbb646b33958f5 72244 python-gevent_1.0.1-1.debian.tar.xz e9f84d99842f42b138453c89fe16e380176cf8e54544a53ed81caca5a42f86d8 1359328 python-gevent-dbg_1.0.1-1_amd64.deb 24c0f9e2da9d3fd22a2ca2b6fbcba44adb7efbaf77f8d8c291e095116fd4eea6 140102 python-gevent-doc_1.0.1-1_all.deb 715cb51bd82fdeb2aa5cdcce62c789fcc44e41030245d9af444b2828a887f183 231740 python-gevent_1.0.1-1_amd64.deb Files: 1fc94d23076457dd5005b21c2852b23b 2019 python extra python-gevent_1.0.1-1.dsc 7b952591d1a0174d6eb6ac47bd975ab6 1455636 python extra python-gevent_1.0.1.orig.tar.gz 555ea830cd2a288ea832a2e9aed1d7a7 72244 python extra python-gevent_1.0.1-1.debian.tar.xz 788f98c23336019a87328817bdacbd71 1359328 debug extra python-gevent-dbg_1.0.1-1_amd64.deb a1a5429f74ba1348137233028343c55a 140102 doc optional python-gevent-doc_1.0.1-1_all.deb 6704fa9917553ca573dddb1f164b35ad 231740 python extra python-gevent_1.0.1-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUNtkwAAoJENzjEOeGTMi/LdoQALoN9D8rJWNqQu38tEHbJOp+ 4RtcWLejYPbFgTg92h/AJBYCt5bH+cJVHx2N3GQnsYPPa1Qbcl6TYkwZ3JBOWeiB G8XskSu5TD7o/uWYqy7Kj2WfxHd/okClnFhoEitTl03gap37xd+atdUdEPQYMbcl +uVI1jnAAS2JYDzM2IQABUfRJahXhSWJ3IQ1jPAHzuAD2xE22UwKo5OQwh4ikCVM
Bug#759208: marked as done (goplay: shows no results at all)
Your message dated Thu, 09 Oct 2014 19:33:35 + with message-id e1xcjsx-0002tc...@franck.debian.org and subject line Bug#759208: fixed in goplay 0.9 has caused the Debian Bug report #759208, regarding goplay: shows no results at all 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.) -- 759208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: goplay Version: 0.5-1.2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Running goplay opens the window but there's no games. Tried update-apt-xapian-index. No chance. Tried golearn and gooffice - they also don't work. - Jonas - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages goplay depends on: ii apt-xapian-index 0.47 ii debtags 1.12.1 ii libapt-pkg4.121.0.6 ii libc6 2.19-9 ii libept1.4.12 1.0.12 ii libfltk1.11.1.10-19 ii libgcc1 1:4.9.1-8 ii libstdc++64.9.1-8 ii libx11-6 2:1.6.2-3 ii libxapian22 1.2.18-1 ii zlib1g1:1.2.8.dfsg-2 Versions of packages goplay recommends: ii games-thumbnails 20120227 goplay suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJT+wlbXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWpQ4H+wZBb/R+24Yg5UWSKuvCW6hA rhF9VnoDQy2ADDUNtayVnTkniF4wSVUL7T+wUi24Tzdt80HItJigpudpSv3rUGpX HDecZzsxHyf+AtFZtgPKZenzYT9Ya3VzdkZK/xn7SbVMjZCtkd1Pk5/3GqcUgQhn zi0Tad2tnYRIPAqF1f/3kCCYCRHOziHfHxil9GR/gitQpizDgAfsl48Rw4G9jmnm D1eQX38aLejiC24oEExokhe9pXxoFM69r4pcwCuciqeb8fEh8frCi8WN7Oyp6u20 0K4TmBfjh23n3ANIAyWar1FSYDHb6jOkTdXloGJMm7A21AVPRhv2RTPguv5cAMo= =pEz8 -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: goplay Source-Version: 0.9 We believe that the bug you reported is fixed in the latest version of goplay, 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. Petter Reinholdtsen p...@debian.org (supplier of updated goplay 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: Thu, 09 Oct 2014 19:22:24 + Source: goplay Binary: goplay Architecture: source Version: 0.9 Distribution: unstable Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Petter Reinholdtsen p...@debian.org Description: goplay - games (and more) package browser using DebTags Closes: 759208 Changes: goplay (0.9) unstable; urgency=low . * Update Standards-Version from 3.9.4 to 3.9.6. * Change default build rules to not print compiler flags, to make it easier to spot warnings. Adjust debian/rules to reenable them when building the debian package, for the automatic build check to work. * Change package priority from optional to extra, to bring it in line with the Debian archive settings. * Add more compiler warning flags by default. * Depend on debtags (= 1.12.2) or (= 1.12) to make sure we get a version with properly populating the debtags database (Closes: #759208). Checksums-Sha1: bf8b31dca09ebef6dea4d0b04264ec29ecb2dc23 1103 goplay_0.9.dsc 6adbe293d711eaafebc55719c26d3a6a68b7e98a 159308 goplay_0.9.tar.xz Checksums-Sha256: ee52653343d1e74a65864ecdb9c90c3bf9dffd01aede78b5e029275c89551c23 1103 goplay_0.9.dsc 3e713fdd4a53aa4edad143a1c85c11fbbfbff373cb2b5649d81411c2c1177a30 159308 goplay_0.9.tar.xz Files: cb9e7d61cd602cf1d2685b39905bf50a 1103 admin extra goplay_0.9.dsc 2e46a66c9501ae68d5982a00df25a622 159308 admin extra goplay_0.9.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iD8DBQFUNuF420zMSyow1ykRAqfnAKDek0ba/IRyMMgqAiOfFHuw4RMnvACcDhxd 2YBLdNUk75gaZENqPYR4Rp4=
Bug#763219: zeitgeist needs valadoc with vala 0.26 support.
Hello! For the record I just verified that this build failure goes away if using a (locally built) valadoc with support for vala 0.26. (The problem here is that zeitgeist uses (the default) vala 0.26 to build itself and then tries to use valadoc on top of that, which still only supports vala 0.24. Changing this on the valadoc side is trivial and preferred. Just s/0.24/0.26/ in debian/control.) Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757348: [systemd-shim] Re: systemd: with SysV init, can no longer suspend and shutdown from lightdm
Package: systemd-shim Version: 8-2 Fixed-upstream is invalid as this bug has recently had a number of others merged into it. I have spent a few days looking into this problem, and have had to start from scratch to see what is going on. I have been seeing what happens when you run 'pkcheck --list-temp', which currently returns 'Error getting session: No session for pid PID'. It looks like polkit has a hard dependency on systemd as init currently - the 'session' being sought goes through src/polkit/polkit/polkitunixsession-systemd.c:polkit_unix_session_initable_init, which then calls into sd_pid_get_session from the libsystemd0 package. This uses the PID of the pkcheck-calling process to read the proc file '/proc/pid/cgroup' - it looks for a line containing 'systemd', and then extracts the 'path', the bit at the end, to get at the session. On my current session, every single process has '/' as this path - in libsystemd0/systemd-215/src/shared/cgroup-util.c:cg_path_get_session line 1320, this path is explicitly rejected - its checked for and '-ENOENT' is returned. Under a systemd-as-init system, a valid example of a path would be '/user.slice/user-1000.slice/session-1.scope'. So far I haven't seen logind factor in here. I can see that polkit used to use ConsoleKit (I was originally expecting to be investigating src/polkit/polkitunixsession.c rather than the systemd version), I hope next session to turn back time a bit and see how this process worked properly under ConsoleKit. I know nothing about cgmanager yet BTW, I've been told it might be a bug with this - will check into that later. -- Libre software on Github: https://github.com/OmegaPhil FSF member #9442 signature.asc Description: OpenPGP digital signature
Bug#764441: sinfo and slurm-client: error when trying to install together
Mehdi Dogguy me...@dogguy.org writes: Hi Gaudenz, On Wed, Oct 08, 2014 at 10:34:45AM +0200, Gaudenz Steinlin gaud...@debian.org wrote: Ralf Treinen trei...@free.fr writes: 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/sinfo /usr/share/man/man1/sinfo.1.gz This happends because the sinfo binary in slurm moved from slurm-llnl to slurm-client and now the conflict specified in sinfo is wrong. To restore the previous state, sinfo should update it's conflict to slurm-client with appropriate versioning. Since your package had a Conflicts, can you please update it? If you agree on that, can you also reassign this bug to src:sinfo so that it is tracked properly? I will certainly update the Conflict if we can't agree on a better solution in the next few days. But as the Conflict was a workaround from the begining I'd prefer a solution where we agree on different names for the commands instead. The conflict is especially bad as the packages are not just two completely unrelated pieces of software but a cluster monitoring software and a cluster resource manager and job scheduler. I can very well imagine that people want to install both on the same system. Gaudenz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764642: apophenia: FTBFS with automake 1.14.x
Source: apophenia Version: 0.999b+ds1-1 Severity: serious Justification: fails to build from source Builds of apophenia with automake 1.14.1, as currently found in both unstable and testing, have been failing: Makefile.am:24: error: HAVE_LD_VERSION_SCRIPT does not appear in AM_CONDITIONAL Automake also issues many warnings of the form automake: warning: source file '$(top_builddir)/eg/apop_map_row.c' is in a subdirectory, automake: but option 'subdir-objects' is disabled which you might also want to consider addressing, if only to cut down on noise. Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764448: mate-applets 1.8.1+dfsg1-1 tries to overwrite files in gnome-applets 3.8.1-1
Hi Giacomo, hi Axel, On Do 09 Okt 2014 12:49:18 CEST, Giacomo Mulas wrote: On Thu, 9 Oct 2014, Mike Gabriel wrote: Hi Giacomo, Hi Mike Thanks for reporting this. This needs to be fixed upstream+downstream. What are the files that trouble you (and us all)? (Asking, because I can't check right now, because I am at a customer). Manpages. I had a look at the contents of the package, apparently everything else has a unique (full) filename, meaning that at least some part of the path is unique, even if the final filename duplicates something in gnome, so this is ok. Instead, most manpages in man1 in the package have exactly the same name as their gnome counterparts, so these should be changed/fixed. E.g. cdplayer_applet.1.gz, charpick_applet.1.gz, cpufreq-selector.1.gz, drivemount_applet.1.gz, geyes_applet.1.gz, gkb_applet.1.gz, ... Perhaps they should all be prefixed with mate- or suffixed with -mate or something similar to make their names unique. This should be relatively painless, apart from having to do some script-fu to rename the manpages before building the deb binary package... Could be done by awk probably, or even with some pipeing of commands like cd $INSTALL/usr/share/man/man1 ; for i in `ls *.1.gz` ; mv $i mate-$i ; done or something along these lines. Cheers Giacomo I removed the man pages again from the bin:package... for now... I have pinged upstream to get this fixed [1]. Mike [1] https://github.com/mate-desktop/mate-applets/issues/103 -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgprhWAbbQcHW.pgp Description: Digitale PGP-Signatur
Bug#759390: marked as done (gpsshogi: please use default boost version)
Your message dated Thu, 09 Oct 2014 21:21:16 + with message-id e1xcl9a-0008nf...@franck.debian.org and subject line Bug#759390: fixed in gpsshogi 0.6.0-3+nmu1 has caused the Debian Bug report #759390, regarding gpsshogi: please use default boost version 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.) -- 759390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: gpsshogi version: 0.6.0-3 Hi, Your package build-depends on libboost1.54-all-dev, which is no longer the default version. Please switch to an unversioned build-dependency (libboost-all-dev). Cheers, Ivo ---End Message--- ---BeginMessage--- Source: gpsshogi Source-Version: 0.6.0-3+nmu1 We believe that the bug you reported is fixed in the latest version of gpsshogi, 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. Yann Dirson dir...@debian.org (supplier of updated gpsshogi 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: Thu, 09 Oct 2014 22:23:13 +0200 Source: gpsshogi Binary: gpsshogi gpsshogi-data gpsshogi-dbg Architecture: source all amd64 Version: 0.6.0-3+nmu1 Distribution: unstable Urgency: medium Maintainer: Daigo Moriwaki da...@debian.org Changed-By: Yann Dirson dir...@debian.org Description: gpsshogi - Shogi playing program based on OpenShogiLib gpsshogi-data - data files for gpsshogi gpsshogi-dbg - Shogi playing program based on OpenShogiLib Closes: 759390 Changes: gpsshogi (0.6.0-3+nmu1) unstable; urgency=medium . * Non-maintainer upload. * Change boost build-dep to be version-less (Closes: #759390). * Add hint Shogi to menu file. Checksums-Sha1: ab4c5a2e70e9add5855c2a5c2a6dfb6909257fbb 1556 gpsshogi_0.6.0-3+nmu1.dsc 8ece79ff2729f5d9b88531ce21ee86f154dba4f9 9700 gpsshogi_0.6.0-3+nmu1.debian.tar.xz 89f012bcbc1088ae134b8f6e2e1824a5e7c69dab 6903690 gpsshogi-data_0.6.0-3+nmu1_all.deb 05ab372fc61491207a6667de380becdc665f2c7f 675670 gpsshogi_0.6.0-3+nmu1_amd64.deb d9cf881df023687d7d58521dc7e6e351d2e841f0 3223964 gpsshogi-dbg_0.6.0-3+nmu1_amd64.deb Checksums-Sha256: e9eab68171421abcd2a8004634ef25631947cafe7241f68ee2d141bdfd0c5d3f 1556 gpsshogi_0.6.0-3+nmu1.dsc 27a83c2a47181b2055b09a48b17b7a2d0f532fe9f14060d0f5662fcf738b9962 9700 gpsshogi_0.6.0-3+nmu1.debian.tar.xz cb914ef5a64f6f7c3b70c7be15858a856ce4b88796cd3ddb3ea70785d9e10ec5 6903690 gpsshogi-data_0.6.0-3+nmu1_all.deb c83d3f6618588efdc58358831515ef3111089a503b822dfae916bb1f5bd8dc3a 675670 gpsshogi_0.6.0-3+nmu1_amd64.deb 8b066ed475b37e88f21418192001ddd1ee05e8e756c1615fb8824381ecd7d74d 3223964 gpsshogi-dbg_0.6.0-3+nmu1_amd64.deb Files: b0b2f06ea5cc2bae6b3eaf1de209cd98 1556 games optional gpsshogi_0.6.0-3+nmu1.dsc 0805ccf0229ef053a606a513a0716c22 9700 games optional gpsshogi_0.6.0-3+nmu1.debian.tar.xz 6e1e5d241bba8f254652dc48b1d103a8 6903690 games optional gpsshogi-data_0.6.0-3+nmu1_all.deb 9838ed0ca0daa6f2b6d030a3a53c4dba 675670 games optional gpsshogi_0.6.0-3+nmu1_amd64.deb 01dcc6432413a4f99dfd84bbd9f7f6d6 3223964 debug extra gpsshogi-dbg_0.6.0-3+nmu1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iD8DBQFUNvbsV1uVslwzwbgRAjtrAJ0THk3XncrUnmd6KxAymN7/F6H8cQCgigL8 Wcue5WSU0DJn8jbhnUmvibY= =sDos -END PGP SIGNATUREEnd Message---
Bug#764646: Should this package be removed?
Package: f-spot Severity: serious f-spot is the last package using lcms1 (blocking it's removal), hasn't seen a maintainer upload since 2.5 years and is dead upstream (last upstream release in 2010). Also, there's three RC bugs by now. If you agree with the removal, please assign to ftp.debian.org Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764448: marked as done (mate-applets 1.8.1+dfsg1-1 tries to overwrite files in gnome-applets 3.8.1-1)
Your message dated Thu, 09 Oct 2014 21:22:05 + with message-id e1xcl9x-0008vq...@franck.debian.org and subject line Bug#764448: fixed in mate-applets 1.8.1+dfsg1-2 has caused the Debian Bug report #764448, regarding mate-applets 1.8.1+dfsg1-1 tries to overwrite files in gnome-applets 3.8.1-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.) -- 764448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mate-applets Version: 1.8.1+dfsg1-1 Severity: normal Dear Maintainer, the new version 1.8.1+dfsg1-1 of mate-applets contains files with the same name as gnome-applets 3.8.1-1. As a consequence, it is uninstallable if one also installs gnome-applets. This means that on sid, at the moment, I cannot install on a machine a full gnome desktop and a full mate desktop at the same time, letting individual users choose which one they prefer to use. Suggested solutions: 1) quick and dirty (unsatisfactory for me, but can be a temporary band aid): add a conflicts with gnome-applets 2) optimal solution: change the names of the conflicting applets (possibly coordinating with the gnome-applets maintainer) 3) less work than 2) but also less good: use the debian alternatives system to make mate and gnome applets with the same name coexist (definitely coordinating with the gnome-applets maintainer) 4) something else that I did not think about Bye Giacomo Mulas -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (401, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.3-jak (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages mate-applets depends on: ii gir1.2-mate-panel 1.8.1+dfsg1-1 ii gsettings-desktop-schemas 3.14.0-1 ii gstreamer0.10-alsa 0.10.36-2 ii gstreamer0.10-plugins-good 0.10.31-3+nmu4 ii gvfs1.22.0-1+b1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-11 ii libcairo2 1.12.16-5 ii libcpufreq0 008-1 ii libdbus-1-3 1.8.8-2 ii libdbus-glib-1-20.102-1 ii libfontconfig1 2.11.0-6.1 ii libfreetype62.5.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2 ii libglib2.0-02.42.0-2 ii libgtk2.0-0 2.24.24-1 ii libgtop2-7 2.28.5-2 ii libice6 2:1.0.9-1 ii libmate-desktop-2-171.8.1+dfsg1-1 ii libmate-panel-applet-4-11.8.1+dfsg1-1 ii libmateweather1 1.8.0-2 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpangoft2-1.0-0 1.36.8-2 ii libpolkit-gobject-1-0 0.105-7 ii libsm6 2:1.2.2-1 ii libstartup-notification00.12-4 ii libupower-glib3 0.99.1-3 ii libx11-62:1.6.2-3 ii mate-applets-common 1.8.1+dfsg1-1 ii mate-icon-theme 1.8.0-1 ii mate-panel 1.8.1+dfsg1-1 ii python 2.7.8-1 ii python-dbus 1.2.0-2+b3 ii python-gi 3.14.0-1 ii python-gobject 3.14.0-1 ii python-gst0.10 0.10.22-3 ii python-notify 0.1.1-3 Versions of packages mate-applets recommends: ii cpufrequtils 008-1 ii mate-media 1.8.0+dfsg1-3 ii mate-polkit 1.8.0+dfsg1-4 ii mate-system-monitor 1.8.0+dfsg1-2 mate-applets suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: mate-applets Source-Version: 1.8.1+dfsg1-2 We believe that the bug you reported is fixed in the latest version of mate-applets, 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. Mike Gabriel sunwea...@debian.org (supplier of updated mate-applets 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
