Bug#754889: marked as done (whichwayisup: Wrong font name included)
Your message dated Thu, 17 Jul 2014 06:04:05 +
with message-id e1x7env-0007h3...@franck.debian.org
and subject line Bug#754889: fixed in whichwayisup 0.7.9-4
has caused the Debian Bug report #754889,
regarding whichwayisup: Wrong font name included
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.)
--
754889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: whichwayisup
Version: 0.7.9-3
Severity: grave
Tags: patch
Justification: renders package unusable
When not having installed ttf-dejavu-core the Symlink from
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf to
/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf is missing and the game does
not start.
I corrected the Path in lib/util.py
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14.9 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages whichwayisup depends on:
ii fonts-dejavu-core 2.34-1
ii python 2.7.6-2
ii python-ogg 1.3+repack-6
ii python-pygame 1.9.1release+dfsg-10
whichwayisup recommends no packages.
whichwayisup suggests no packages.
--- a/lib/util.py
+++ b/lib/util.py
@@ -29,7 +29,7 @@
class Util:
pygame.font.init()
- smallfont = pygame.font.Font(data.filepath(os.path.join(/usr/share/fonts/truetype/ttf-dejavu, DejaVuSans.ttf)), FONT_SIZE)
+ smallfont = pygame.font.Font(data.filepath(os.path.join(/usr/share/fonts/truetype/dejavu, DejaVuSans.ttf)), FONT_SIZE)
cached_text_images = {}
cached_images = {}
cached_images[key_z] = pygame.image.load(data.picpath(key, z))
@@ -302,4 +302,4 @@
tmp.blit(screen,(0,0))
screen = pygame.display.set_mode((SCREEN_WIDTH,SCREEN_HEIGHT),mode)
screen.blit(tmp,(0,0))
- pygame.display.flip()
\ No newline at end of file
+ pygame.display.flip()
---End Message---
---BeginMessage---
Source: whichwayisup
Source-Version: 0.7.9-4
We believe that the bug you reported is fixed in the latest version of
whichwayisup, 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 754...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Markus Koschany a...@gambaru.de (supplier of updated whichwayisup package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 15 Jul 2014 23:37:22 +0200
Source: whichwayisup
Binary: whichwayisup
Architecture: source all
Version: 0.7.9-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org
Changed-By: Markus Koschany a...@gambaru.de
Description:
whichwayisup - 2D platform game with a slight rotational twist
Closes: 754889
Changes:
whichwayisup (0.7.9-4) unstable; urgency=medium
.
* Update font_path.patch. Fix path to DejaVuSans.ttf.
- Thanks to Stefan Arnold for the report. (Closes: #754889)
* Declare compliance with Debian Policy 3.9.5.
* Remove build-dependency and dependency on python-ogg.
- python-pygame provides all necessary features.
* Install whichwayisup.png to usr/share/icons/hicolor/64x64/apps.
Checksums-Sha1:
d98d192ad844e7e2ec1cec651950835f7f4016ab 2080 whichwayisup_0.7.9-4.dsc
10196597fb0573d49d1dce7e5314f4b9497442b3 13552
whichwayisup_0.7.9-4.debian.tar.xz
8470e0cf7825deaaaddf31477a0d8fe45d82008b 888650 whichwayisup_0.7.9-4_all.deb
Checksums-Sha256:
68124bff40a2ae1d1883c9e4494c094860b7b0da553f966a270a81a85250498f 2080
whichwayisup_0.7.9-4.dsc
0583eec35a37cad199b1beb7850f7a3dbd186139c4f09f22cae3a5e2c930565f 13552
whichwayisup_0.7.9-4.debian.tar.xz
128dc05958d8fa6cab43b7b61c3690e6043681b73dba1f2f682c9778eb55a496 888650
whichwayisup_0.7.9-4_all.deb
Files:
cb8f9be3ba8be77730400c924d5d099f 888650 games extra
whichwayisup_0.7.9-4_all.deb
964465652ba2bc8f8145f452e58e3486 2080 games extra whichwayisup_0.7.9-4.dsc
eb11e2ef32fbc5be9050d45e76000981 13552 games extra
whichwayisup_0.7.9-4.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Bug#754982: FTBFS on kfreebsd with new miniupnpc
On 07/17/2014 02:38 AM, Petr Salinger wrote: Package: transmission Your package failed to build on kfreebsd: In fact, the problem is sligthly different. The transmission package does not support newly supplied libminiupnpc-dev under both Linux and kFreeBSD: checking supported miniupnp library... none As a result, it tries to use embedded version from transmission-2.82/third-party/miniupnp/ On kFreeBSD, the build fails. On Linux, the build succeeds, but the resulting binary does not Depend: libminiupnpc10, as it have been expected. The transmission package should be ported to use newer miniupnpc everywhere. The problem is not kfreebsd specific at all. Petr Oh, that explains it then! Thanks for the details. Do you know why it's not finding the libminiupnpc-dev bindings in the configure script? I'll try to find the time investigate later on. Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707268: [NMU] Bug#740085: package plplot 5.10.0
Le 24/06/2014 11:09, Thibaut Paumard a écrit : Dear Andrew, The freeze is approaching. We need plplot for gnudatalanguage. Do you plan on uploading plplot 5.10.0 so it can be part of jessie? Kind regards, Thibaut. Hi Andrew, I'd rather sponsor a package you would have prepared, but failing that I will try to make a non-maintainer upload next week. Please feel free to get back to me if I shouldn't, or if you prepare the upload. Kind regards, Thibaut. signature.asc Description: OpenPGP digital signature
Bug#754982: FTBFS on kfreebsd with new miniupnpc
On 07/17/2014 02:38 AM, Petr Salinger wrote: Package: transmission Your package failed to build on kfreebsd: In fact, the problem is sligthly different. The transmission package does not support newly supplied libminiupnpc-dev under both Linux and kFreeBSD: checking supported miniupnp library... none As a result, it tries to use embedded version from transmission-2.82/third-party/miniupnp/ On kFreeBSD, the build fails. On Linux, the build succeeds, but the resulting binary does not Depend: libminiupnpc10, as it have been expected. The transmission package should be ported to use newer miniupnpc everywhere. The problem is not kfreebsd specific at all. Petr Oh, that explains it then! Thanks for the details. Do you know why it's not finding the libminiupnpc-dev bindings in the configure script? I'll try to find the time investigate later on. Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754982: FTBFS on kfreebsd with new miniupnpc
As a result, it tries to use embedded version from transmission-2.82/third-party/miniupnp/ Oh, that explains it then! Thanks for the details. Do you know why it's not finding the libminiupnpc-dev bindings in the configure script? I'll try to find the time investigate later on. I looked into config.log, the signature of some library call in miniupnpc have been changed (addeded argument), I do not remeber name. The easiest solution might be to upload current Transmission 2.84, as upstream changelog for 2.83 says: Updated third party libraries: DHT updated to v0.22; miniupnpc updated to v1.9 Autoconf script fixes: better detection of ccache, minupnpc Cheers Petr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735991: marked as done (please build-depend on libtiff-dev, not libtiff4-dev)
Your message dated Thu, 17 Jul 2014 06:33:31 +
with message-id e1x7ffz-0002ob...@franck.debian.org
and subject line Bug#735991: fixed in adanaxisgpl 1.2.5.dfsg.1-6
has caused the Debian Bug report #735991,
regarding please build-depend on libtiff-dev, not libtiff4-dev
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
735991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: adanaxisgpl
Version: 1.2.5.dfsg.1-5
User: q...@debian.org
Usertags: libtiff4-dev
The libtiff4-dev package is a transitional package that is going to
disappear soon. Please update your build dependency from libtiff4-dev
to libtiff-dev.
---End Message---
---BeginMessage---
Source: adanaxisgpl
Source-Version: 1.2.5.dfsg.1-6
We believe that the bug you reported is fixed in the latest version of
adanaxisgpl, 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 735...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Markus Koschany a...@gambaru.de (supplier of updated adanaxisgpl 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: Sat, 12 Jul 2014 01:08:30 +0200
Source: adanaxisgpl
Binary: adanaxisgpl adanaxisgpl-data
Architecture: source amd64 all
Version: 1.2.5.dfsg.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org
Changed-By: Markus Koschany a...@gambaru.de
Description:
adanaxisgpl - Action game in four spatial dimensions
adanaxisgpl-data - Action game in four spatial dimensions
Closes: 726199 735991
Changes:
adanaxisgpl (1.2.5.dfsg.1-6) unstable; urgency=medium
.
* Team upload.
.
[ Markus Koschany ]
* wrap-and-sort -sa.
* Build-depend on libtiff-dev instead of libtiff4-dev. (Closes: #735991)
* Switch to compat level 9 and require debhelper =9.
* Declare compliance with Debian Policy 3.9.5.
* Build only with dh-autoreconf because it is a superset of autotools_dev.
* Add keywords and a comment in German to desktop file.
* Install 48x48 icon and use it for the desktop file. (Closes: #726199)
* Do not install NEWS file anymore since it contains the same information as
ChangeLog.
* debian/rules: Export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed to avoid
useless dependencies.
* Remove superfluous ${shlibs:Depends} substvar from -data package.
.
[ Evgeni Golov ]
* Correct Vcs-* URLs to point to anonscm.debian.org.
Checksums-Sha1:
ce2ada0027bbc11713e072ebe93c6ae018df1d1f 2251 adanaxisgpl_1.2.5.dfsg.1-6.dsc
ab10c95face7354fa01dd8138f2cf78a33c4bc1e 15588
adanaxisgpl_1.2.5.dfsg.1-6.debian.tar.xz
f38529948fd715c849037402533ba42334f2a7fc 1231358
adanaxisgpl_1.2.5.dfsg.1-6_amd64.deb
f86739b9527cea4413c79f8001ca1c537d250806 16841620
adanaxisgpl-data_1.2.5.dfsg.1-6_all.deb
Checksums-Sha256:
1e8e8b1183230ecf2aacac2f757a39acedb5617fd16b4bcb3ed00b13dd980bfb 2251
adanaxisgpl_1.2.5.dfsg.1-6.dsc
5251d02b15e7dab7482c39930d6ae987175b4ede02847e11d789baf302e5287a 15588
adanaxisgpl_1.2.5.dfsg.1-6.debian.tar.xz
08b3ae75ba8404b8b338ea0ffd0758df6e65a8b9cb078587a4d3f510e61d3a03 1231358
adanaxisgpl_1.2.5.dfsg.1-6_amd64.deb
503188567ea38826de205fe9b9147f64aa8c75e2651bff8565f461d9d3573189 16841620
adanaxisgpl-data_1.2.5.dfsg.1-6_all.deb
Files:
c8f6901efb32425e61e83898e61f1fc9 1231358 games optional
adanaxisgpl_1.2.5.dfsg.1-6_amd64.deb
83c52af56b4f0e26e283077fabe8573f 16841620 games optional
adanaxisgpl-data_1.2.5.dfsg.1-6_all.deb
d4604eb774acb1e6f9ff211d67c7100c 2251 games optional
adanaxisgpl_1.2.5.dfsg.1-6.dsc
a4ca4181a53840e2198dde0ce048d380 15588 games optional
adanaxisgpl_1.2.5.dfsg.1-6.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCAAGBQJTx2psAAoJEI7tzBuqHzL/rdAQAIFXZezDoSDHtSmO3a68SFvk
DhuOFOwi4PpmpFghE+5hT55P9PSBRpq4ofjZbIqbasdKhF2N7wwYZmoagkdlHnGc
BASdyb03vAhROCcV8ep1rlFzxT3haGceFK5gG1NFR3jRWetMyj9YHjeYRGOVIKPB
SC2SvUQCpeSOclkdQJ5HgL3gjhF85SHs/Zab2q/rq25DBRIAiWhTwdljMZ75Z0NW
EU4bBKYKL2vWhqasTFcQfsFx0Nb2PEPPFZBbd+BiS3qexv9fBcYi7zlvfIKo7TGv
p3VjYn091MHtG6oka/t5RKVIJCTE0FVRmPxx5sduyEB9+0ujyyc0FPKIDAYjG/D0
Bug#755017: FTBFS against cgsi-gsoap 1.3.6-1+b1
ons 2014-07-16 klockan 22:41 +0200 skrev Emilio Pozuelo Monfort: Source: gfal2 Version: 2.3.0-4 Severity: serious Doing rebuilds for the libgsoap5 transition, your package failed to build everywhere except on amd64, i386 and hurd-i386. That seems to be because in those builds, the version of libcgsi-gsoap1 was 1.3.6-1 (i.e. before the binNMU for libgsoap5) while on the builds that failed libcgsi-gsoap1 was at 1.3.6-1+b1. The error was: /usr/bin/c++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2-Wl,-z,relro CMakeFiles/unit_test_srm_plugin.dir/tests_srm.cpp.o -o unit_test_srm_plugin -L/«PKGBUILDDIR»/obj-arm-linux-gnueabihf/src -L/«PKGBUILDDIR»/obj-arm-linux-gnueabihf/plugins -rdynamic ../../../../src/libgfal2.so.2.3.0 -lgfal_srm_ifce -lgfal_transfer -lgfal_plugin_srm -lm ../../../../src/libgfal2.so.2.3.0 ../../../gtest/libgtest.a ../../../gtest/libgtest_main.a -luuid -lstdc++ -lglib-2.0 -lgthread-2.0 -lglib-2.0 -lgthread-2.0 -ldl ../../../gtest/libgtest.a -lpthread -Wl,-rpath,/«PKGBUILDDIR»/obj-arm-linux-gnueabihf/src:/«PKGBUILDDIR»/obj-arm-linux-gnueabihf/plugins //usr/lib/libcgsi_plugin.so.1: undefined reference to `soap_init_LIBRARY_VERSION_REQUIRED_20817' collect2: error: ld returned 1 exit status make[4]: *** [test/unit/common/srm/unit_test_srm_plugin] Error 1 I'm filing this against gfal2, although it bothers me that the libraries shipped by libcgsi-gsoap1 have undefined references. But that's been happening for a long time, so filing here. Please reassign if necessary. Emilio The failure is not caused by that the binnmu for cgsi-gsoap had happened, but because the binnmu for srm-ifce had not happened. Now that the binnmus for srm-ifce has completed the builds of gfal2 shouldn't have any problems. If you try to build against a cgsi-gsoap that has been rebuilt and an srm-ifce that has not you are using an incompatible set of dependencies and your build is expected to fail. That it fails instead of creating a broken binary is a good thing. That the libraries in libcgsi-gsoap1 have undefined references is by construction, they are deliberately left unresolved in order to make it possible for different users of the library to choose different implementations of these functions. Explicitly linking these libraries to one implementation will introduce breakage. The binnmu of lcgdm is similar. Only amd64 was tried so far and failed because it was using a cgsi-gsoap that had not been recompiled (and therefore expects gsoap4) together with the new gsoap5. After the cgsi-gsoap has been rebuilt the lcgdm rebuild will work just fine. I think you have unreasonable expectations if you expect interdependent packages to be able to binnmu in random order. This is not a permanent FTBFS. It is a transient state that exist during the transition when some packages have been rebuilt and some not. (The virtuabox package needs fixing for unrelated reasons, it bails out if the gcc version detected in greater than 4.8.) Mattias smime.p7s Description: S/MIME cryptographic signature
Bug#751082: Siduction
I made a temporary workaround for the problem I mentioned above in this comment: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755020#15 Or use the long-lived branch release (340.24 version) from Siduction floris -- 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#754257: [kdm] Workaround: Started with Empty Home Directory
Processing control commands: priority -1 normal Bug #754257 [kdm] [kdm] Cannot Log In -- Cannot Access Dbus Session Severity set to 'normal' from 'grave' tag -1 + moreinfo Bug #754257 [kdm] [kdm] Cannot Log In -- Cannot Access Dbus Session Added tag(s) moreinfo. -- 754257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754257 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#754257: [kdm] Workaround: Started with Empty Home Directory
Control: priority -1 normal Control: tag -1 + moreinfo ¡Hola David! El 2014-07-16 a las 14:50 +0300, David Baron escribió: Yes, empty home directory for user and it logs in. Any data, of course, can be brought in from the saved copy. Let's make a summary so far: * You have at least one user in your system that fails to log in using kdm. * In the same system you have other users that do work correctly. * With a new user the session starts correctly. I couldn't find in the reports what kind of session you are trying to start with the users that can't login, I'm assuming you are trying to start kde plasma. With this information, I would suspect of a composite/opengl related issue, and of some corrupted data in the home user directory that causes the session to fail completely. Please respond as clearly as possible the questions bellow: You mentioned that the bug doesn't happend with your user, which makes me wonder if you are loging in your user in the first graphical session and the failling users are trying to log in in the secondary graphical sessions (Change users/ New Login in kde). Can you confirm me if you log the failling user in the first graphical session if it works or not? Does the session of the failling users start correctly using another display manager (lightdm, gdm, etc)? Does the session starts correctly if you use another type of session/desktop environment/window manager (like openbox, for example)? After replying these questions, a good way to find the culprit would be to do a binary search with the data in the home user. It would be particularly useful if you could reproduce the issue copying a failling user ~/.kde and ~/.config to a newly created user home. -- The sooner you start to code, the longer the program will take. -- Roy Carlson Saludos /\/\ /\ `/ signature.asc Description: Digital signature
Bug#751828: pcre3: FTBFS [ppc64el]: Test failure in common with amd64
tags 751828 + patch
retitle 751828 pcre3: FTBFS: test failure: no longer produces number too big
in {} quantifier
found 751828 1:8.35-2
thanks
On Wed, 18 Jun 2014 at 11:38:11 -0300, Mauricio Faria de Oliveira wrote:
/a{}/I
-Failed: number too big in {} quantifier at offset 22
+Capturing subpattern count = 0
+No options
+First char = 'a'
+No need char
/(){64294967295}/I
-Failed: number too big in {} quantifier at offset 14
+Failed: regular expression is too large at offset 15
/(){2,4294967295}/I
-Failed: number too big in {} quantifier at offset 15
+Failed: numbers out of order in {} quantifier at offset 15
[...]
I can reproduce this on amd64 in 1:8.35-2, and it seems likely that the FTBFS
on every architecture except amd64 has the same cause.
These numbers are parsed using this loop, or matching code to parse max:
while (IS_DIGIT(*p)) min = min * 10 + (int)(*p++ - CHAR_0);
if (min 0 || min 65535)
{
*errorcodeptr = ERR5;
return p;
If min gets larger than 214748365 (slightly more than 2^31 / 10) in any
given iteration, then the next multiplication by 10 is a signed integer
overflow, which is formally undefined behaviour in C.
Older versions of gcc effectively guaranteed that signed integer overflow
wraps around in the way you might expect for twos-complement, e.g.
214748365 * 10 == (int) 2147483650U == -2147483646, but more recent gcc
(when -fwrapv is not given) optimizes on the assumption that undefined
behaviour will not be reached, so this overflow leads to unpredictable results.
In the current implementation, even with older gcc or -fwrapv, it is
probably also possible to construct invalid regexes that are incorrectly
parsed because a large limit wraps all the way round into the valid range
[0,65535] and is interpreted as a smaller limit.
One solution that seems reasonable is to check for out-of-range after each
digit is added. This should be portable to every platform with at least
32-bit int (strictly speaking, every platform where 655359 fits in an int).
The attached patch 0002 fixes this. I also attach patch 0001 to fix
#755052, which is non-essential but would help a lot with debugging
any future pcre3 test failures.
I might NMU this if it isn't fixed for a while, but I'll give the
maintainer a chance to sanity-check the patch first.
Regards,
S
From d0a1e185e351cde74b7fc0c072087d8d234e85b5 Mon Sep 17 00:00:00 2001
From: Simon McVittie s...@debian.org
Date: Thu, 17 Jul 2014 10:21:06 +0100
Subject: [PATCH 1/2] Run tests with VERBOSE=1 so we can see the logs for
failing tests
---
debian/changelog | 8
debian/rules | 2 +-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index 0467f9c..5e10cfc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+pcre3 (1:8.35-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Run tests with VERBOSE=1 so we can see the logs for failing tests
+(Closes: #755052)
+
+ -- Simon McVittie s...@debian.org Thu, 17 Jul 2014 09:27:30 +0100
+
pcre3 (1:8.35-2) unstable; urgency=medium
* Build-depends on auto-reconf (Closes: 754540)
diff --git a/debian/rules b/debian/rules
index 108a738..41ef1a3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -50,7 +50,7 @@ build-stamp: configure-stamp
# Add here commands to compile the package.
$(MAKE)
ifeq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE))
- $(MAKE) check
+ $(MAKE) check VERBOSE=1
endif
touch build-stamp
--
2.0.1
From 536eda8ebff29c0bb08817da0b45298ac312b6b7 Mon Sep 17 00:00:00 2001
From: Simon McVittie s...@debian.org
Date: Thu, 17 Jul 2014 10:21:25 +0100
Subject: [PATCH 2/2] Alter checks for too-large repeat count so they do not
rely on integer overflow behaviour (closes: #751828)
---
debian/changelog | 2 +
...g-repeat-count-check-for-overflow-after-e.patch | 93 ++
debian/patches/series | 1 +
3 files changed, 96 insertions(+)
create mode 100644 debian/patches/0001-When-parsing-repeat-count-check-for-overflow-after-e.patch
diff --git a/debian/changelog b/debian/changelog
index 5e10cfc..f6880a2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,8 @@ pcre3 (1:8.35-2.1) UNRELEASED; urgency=medium
* Non-maintainer upload.
* Run tests with VERBOSE=1 so we can see the logs for failing tests
(Closes: #755052)
+ * Alter checks for too-large repeat count so they do not rely on
+integer overflow behaviour (closes: #751828)
-- Simon McVittie s...@debian.org Thu, 17 Jul 2014 09:27:30 +0100
diff --git a/debian/patches/0001-When-parsing-repeat-count-check-for-overflow-after-e.patch b/debian/patches/0001-When-parsing-repeat-count-check-for-overflow-after-e.patch
new file mode 100644
index 000..a909502
--- /dev/null
+++
Processed: Re: Bug#751828: pcre3: FTBFS [ppc64el]: Test failure in common with amd64
Processing commands for cont...@bugs.debian.org:
tags 751828 + patch
Bug #751828 [src:pcre3] pcre3: FTBFS [amd64]: Test failures
Added tag(s) patch.
retitle 751828 pcre3: FTBFS: test failure: no longer produces number too big
in {} quantifier
Bug #751828 [src:pcre3] pcre3: FTBFS [amd64]: Test failures
Changed Bug title to 'pcre3: FTBFS: test failure: no longer produces number
too big in {} quantifier' from 'pcre3: FTBFS [amd64]: Test failures'
found 751828 1:8.35-2
Bug #751828 [src:pcre3] pcre3: FTBFS: test failure: no longer produces number
too big in {} quantifier
Marked as found in versions pcre3/1:8.35-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
751828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751828
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#752465: marked as done (Multi-Arch:same file conflict for any pair of architectures)
Your message dated Thu, 17 Jul 2014 10:03:59 + with message-id e1x7ixf-0001ok...@franck.debian.org and subject line Bug#752465: fixed in gdbm 1.8.3-13 has caused the Debian Bug report #752465, regarding Multi-Arch:same file conflict for any pair of 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.) -- 752465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libgdbm3 Version: 1.8.3-12 Severity: wishlist User: helm...@debian.org Usertags: rebootstrap Dear gdbm maintainer, gdbm is currently built against texinfo 5.1. When rebuilding it (for new architectures) against (current) texinfo 5.2, M-A:same conflicts occur for /usr/share/info/gdbm.info.gz: First line: -This is gdbm.info, produced by makeinfo version 5.1 from gdbm.texinfo. +This is gdbm.info, produced by makeinfo version 5.2 from gdbm.texinfo. This bug is fixed by uploading a new version of gdbm or binNMUing it for all architectures. Helmut ---End Message--- ---BeginMessage--- Source: gdbm Source-Version: 1.8.3-13 We believe that the bug you reported is fixed in the latest version of gdbm, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anibal Monsalve Salazar ani...@debian.org (supplier of updated gdbm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jul 2014 10:29:02 +0100 Source: gdbm Binary: libgdbm3 libgdbm-dev Architecture: source mips Version: 1.8.3-13 Distribution: unstable Urgency: high Maintainer: Anibal Monsalve Salazar ani...@debian.org Changed-By: Anibal Monsalve Salazar ani...@debian.org Description: libgdbm-dev - GNU dbm database routines (development files) libgdbm3 - GNU dbm database routines (runtime version) Closes: 737943 752465 752830 Changes: gdbm (1.8.3-13) unstable; urgency=high . [ Helmut Grohne ] * Source upload. Closes: #752465 * Move documentation from libgdbm3 to libgdbm-dev to comply with policy 8.2. Closes: #752830 . [ Anibal Monsalve Salazar ] * Bootstrap without texinfo. Patch by Daniel Schepler. Closes: #737943. * Standards Version is 3.9.5. * Remove debian/source/options. * Refresh patches. Checksums-Sha1: ddd80474cd73ebb0c4d5221d24c7af4ccab759e1 1804 gdbm_1.8.3-13.dsc de8ca65d7501e1bf5fa1fc81f6716be7c70fc102 14708 gdbm_1.8.3-13.debian.tar.xz da85d1d5cbe8ed7c0673e8da5642469170824788 28364 libgdbm3_1.8.3-13_mips.deb 043d51afd582e0ab1b941836c3890637590a739a 48810 libgdbm-dev_1.8.3-13_mips.deb Checksums-Sha256: 540d62c3fa66967a68ee11d5fd5ad6d0d0ec7d557cb2422cd3e6bf9f2263a028 1804 gdbm_1.8.3-13.dsc 8cd3f45f64cc8a134c434f3f0c234c5319b6510d83fdd901ec979b38a184425e 14708 gdbm_1.8.3-13.debian.tar.xz 7f33f05db5683a41a09715c93cc033d8e72656012c9a3be93275c8c70b023f9a 28364 libgdbm3_1.8.3-13_mips.deb 59db398cf2a038265a724a33b9340c9a825244afef944d0e97733bba397907f3 48810 libgdbm-dev_1.8.3-13_mips.deb Files: 6ecc306495abd0c647c3744fcc87b11f 28364 libs important libgdbm3_1.8.3-13_mips.deb 845c9e7779350d7d8dcc0aa61c2e8d71 48810 libdevel optional libgdbm-dev_1.8.3-13_mips.deb f1cdf8227909ef727b1d310fc09438f7 1804 libs important gdbm_1.8.3-13.dsc 3c1ba767067a98699a7bacccd2d53f9f 14708 libs important gdbm_1.8.3-13.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTx5xYAAoJEHxWrP6UeJfYBB8P/0YfWAHytib6JFqrA7iRniqV TGhSlrrsIh8jUn8iamw6a6Pw+L2itAF7iP30dD9wBioovq7sM5Z8tpgyQFwWXD4v AMJB/sy5ki/gkVhEfxZjmUZwja8tWUttpbmHOFwiOvRxZMWU7xgwtNv9qpsoeMwZ +Uzzz2+Twjunb0A53u/UT1tbXCt97amoOXdfX41KdV08s+Ums86ciZtXJibzpPqX LGQrG90Potg2kfbLBIExrNqtdlQ784C9mZXqx3Q1r1Al/hQlFjGf8eeKy9Wlt++l bIDgyo6/EqQF6VsWSa5exYkSn3OHiyGY52mQDmr7Ndlv2lbJdkRcEna68EFB9PfC RSAWSnzJbjZl0BvxKXHDmaOxcDpR4NZVugUz7ddu/lmdDzK3Lm13y45M4X9YPXeb p3c/bGmYayOfqBfBtklnuetNOkJWO0p9fM+EO3hHe7W/u95sivk2rmEwE43QRxqL m0Ni4gz4NWHZ+M8ADFhOGv/+XwEj4x7dOTtm8czXcp5LHpPH8gxUB1jzL3ASD0va auQtYh7C6vSztn8/qkJpZJKNge9+wphgGu8RxV2zEqCIGvpsHXyvC9lDCmM9vjCO qhKv8QQ+KuuMz8iuIFxRVRPDyC7PsdNODLJummGTp9ob5043blTdum4c5nztVb2x HhOZ9epTpIDttWmnMzJU =tOnC -END PGP
Bug#753098: marked as done (libgdbm3: Unpacking libgdbm3:amd64 (1.8.3-12+b1) over (1.8.3-12) ...)
Your message dated Thu, 17 Jul 2014 10:03:59 + with message-id e1x7ixf-0001ok...@franck.debian.org and subject line Bug#752465: fixed in gdbm 1.8.3-13 has caused the Debian Bug report #752465, regarding libgdbm3: Unpacking libgdbm3:amd64 (1.8.3-12+b1) over (1.8.3-12) ... 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.) -- 752465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libgdbm3 Version: 1.8.3-12+b1_amd64 Severity: normal 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, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-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 Screen output: # apt-get update Hit http://ftp.ch.debian.org jessie InRelease Hit http://ftp.ch.debian.org jessie-updates InRelease Hit http://security.debian.org jessie/updates InRelease Hit http://ftp.ch.debian.org jessie-backports InRelease Hit http://ftp.ch.debian.org jessie/main Sources/DiffIndex Hit http://deb.torproject.org jessie InRelease Get:1 ftp://ftp.debian.org stable InRelease Hit http://ftp.ch.debian.org jessie/main amd64 Packages/DiffIndex Hit http://ftp.ch.debian.org jessie/main i386 Packages/DiffIndex Hit http://ftp.ch.debian.org jessie/main Translation-en/DiffIndex Ign ftp://ftp.debian.org stable InRelease Hit http://ftp.ch.debian.org jessie-updates/main Sources Hit http://ftp.ch.debian.org jessie-updates/main amd64 Packages Hit http://security.debian.org jessie/updates/main Sources Hit http://ftp.ch.debian.org jessie-updates/main i386 Packages Hit http://ftp.ch.debian.org jessie-updates/main Translation-en Hit http://security.debian.org jessie/updates/main amd64 Packages Hit ftp://ftp.debian.org stable Release.gpg Hit http://ftp.ch.debian.org jessie-backports/main Sources Hit http://deb.torproject.org jessie/main amd64 Packages Hit http://security.debian.org jessie/updates/main i386 Packages Hit http://ftp.ch.debian.org jessie-backports/main amd64 Packages Hit http://security.debian.org jessie/updates/main Translation-en Hit ftp://ftp.debian.org stable Release Hit http://ftp.ch.debian.org jessie-backports/main i386 Packages Hit http://ftp.ch.debian.org jessie-backports/main Translation-en Hit http://deb.torproject.org jessie/main i386 Packages Hit ftp://ftp.debian.org stable/main amd64 Packages Hit ftp://ftp.debian.org stable/contrib amd64 Packages Hit ftp://ftp.debian.org stable/non-free amd64 Packages Hit ftp://ftp.debian.org stable/main i386 Packages Hit ftp://ftp.debian.org stable/contrib i386 Packages Hit ftp://ftp.debian.org stable/non-free i386 Packages Hit ftp://ftp.debian.org stable/contrib Translation-en Hit ftp://ftp.debian.org stable/main Translation-en Hit ftp://ftp.debian.org stable/non-free Translation-en Ign http://deb.torproject.org jessie/main Translation-en_US Ign http://deb.torproject.org jessie/main Translation-en Reading package lists... Done # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: libgdbm3 : Breaks: libgdbm3:i386 (!= 1.8.3-12) but 1.8.3-12+b1 is installed libgdbm3:i386 : Breaks: libgdbm3 (!= 1.8.3-12+b1) but 1.8.3-12 is installed E: Unmet dependencies. Try using -f. # apt-get -f upgrade Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done Calculating upgrade... Done The following package was automatically installed and is no longer required: xulrunner-29 Use 'apt-get autoremove' to remove it. The following packages will be
Bug#753011: marked as done (libgdbm3: Upgrade from 1.8.3-12 to 1.8.3-12+b1 has multiarch file conflict)
Your message dated Thu, 17 Jul 2014 10:03:59 +
with message-id e1x7ixf-0001ok...@franck.debian.org
and subject line Bug#752465: fixed in gdbm 1.8.3-13
has caused the Debian Bug report #752465,
regarding libgdbm3: Upgrade from 1.8.3-12 to 1.8.3-12+b1 has multiarch file
conflict
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.)
--
752465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libgdbm3
Version: 1.8.3-12+b1
Severity: important
Dear Maintainer,
When trying to upgrade libgdbm, I receive the following errors:
[walsterm@darjeeling:apt/sources.list.d]$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
libgdbm3 : Breaks: libgdbm3:i386 (!= 1.8.3-12) but 1.8.3-12+b1 is installed
libgdbm3:i386 : Breaks: libgdbm3 (!= 1.8.3-12+b1) but 1.8.3-12 is installed
E: Unmet dependencies. Try using -f.
[walsterm@darjeeling:apt/sources.list.d]$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
libdirac-decoder0 liblivemedia23 libproxy-tools xulrunner-29
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
libgdbm3
The following packages will be upgraded:
libgdbm3
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
66 not fully installed or removed.
Need to get 0 B/44.1 kB of archives.
After this operation, 4,096 B disk space will be freed.
Do you want to continue? [Y/n]
Reading changelogs... Done
(Reading database ... 364426 files and directories currently installed.)
Preparing to unpack .../libgdbm3_1.8.3-12+b1_amd64.deb ...
Unpacking libgdbm3:amd64 (1.8.3-12+b1) over (1.8.3-12) ...
dpkg: error processing archive
/var/cache/apt/archives/libgdbm3_1.8.3-12+b1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libgdbm3/changelog.Debian.gz',
which is different from other instances of package libgdbm3:amd64
Processing triggers for install-info (5.2.0.dfsg.1-4) ...
Errors were encountered while processing:
/var/cache/apt/archives/libgdbm3_1.8.3-12+b1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
[walsterm@darjeeling:apt/sources.list.d]$ apt-cache show libgdbm3
Package: libgdbm3
Source: gdbm (1.8.3-12)
Version: 1.8.3-12+b1
Installed-Size: 107
Maintainer: Anibal Monsalve Salazar ani...@debian.org
Architecture: amd64
Depends: libc6 (= 2.14), dpkg (= 1.15.4) | install-info
Pre-Depends: multiarch-support
Description-en: GNU dbm database routines (runtime version)
GNU dbm ('gdbm') is a library of database functions that use extendible
hashing and works similarly to the standard UNIX 'dbm' functions.
.
The basic use of 'gdbm' is to store key/data pairs in a data file, thus
providing a persistent version of the 'dictionary' Abstract Data Type
('hash' to perl programmers).
Description-md5: 900375b4641d82391c1c951c3b8647f6
Multi-Arch: same
Homepage: http://directory.fsf.org/project/gdbm/
Tag: implemented-in::c, role::shared-lib
Section: libs
Priority: important
Filename: pool/main/g/gdbm/libgdbm3_1.8.3-12+b1_amd64.deb
Size: 44064
MD5sum: ed33d34c893ef9aa9b5a6e2f7c12c11d
SHA1: b9ed80a52ebfd221bee670dbbb5111c812b337bd
SHA256: b3285b00037e35cb2d3b28fdd2fa2be9a843d8f872c59647e34d76b35478d4ec
Package: libgdbm3
Status: install ok installed
Priority: important
Section: libs
Installed-Size: 111
Maintainer: Anibal Monsalve Salazar ani...@debian.org
Architecture: amd64
Multi-Arch: same
Source: gdbm
Version: 1.8.3-12
Depends: libc6 (= 2.2.5), dpkg (= 1.15.4) | install-info
Pre-Depends: multiarch-support
Description-en: GNU dbm database routines (runtime version)
GNU dbm ('gdbm') is a library of database functions that use extendible
hashing and works similarly to the standard UNIX 'dbm' functions.
.
The basic use of 'gdbm' is to store key/data pairs in a data file, thus
providing a persistent version of the 'dictionary' Abstract Data Type
('hash' to perl programmers).
Description-md5: 900375b4641d82391c1c951c3b8647f6
Homepage: http://directory.fsf.org/project/gdbm/
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8,
Bug#752830: marked as done (libgdbm3: ships /usr/share/info/gdbm.info.gz which isn't versioned)
Your message dated Thu, 17 Jul 2014 10:03:59 + with message-id e1x7ixf-0001oq...@franck.debian.org and subject line Bug#752830: fixed in gdbm 1.8.3-13 has caused the Debian Bug report #752830, regarding libgdbm3: ships /usr/share/info/gdbm.info.gz which isn't versioned 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.) -- 752830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libgdbm3 Version: 1.8.3-12 Severity: serious libgdbm3 ships /usr/share/info/gdbm.info.gz, which isn't versioned (e.g. libgdbm3.info.gz or a versioned folder would be ok). This violates Policy 8.2.: If your package contains files whose names do not change with each change in the library shared object version, you must not put them in the shared library package. I noticed this because gdbm.info.gz contains the texinfo version in the beginning (as is normal for info files) and thus the file may differ in different architectures if it gets built against different texinfo versions, causing problems with multiarch as we have seen on #752465. Since gdbm.info.gz is a manual for developers, it could be moved to libgdbm-dev, solving this. The manpages are there already so that seems like an appropriate place. Thanks, Emilio ---End Message--- ---BeginMessage--- Source: gdbm Source-Version: 1.8.3-13 We believe that the bug you reported is fixed in the latest version of gdbm, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anibal Monsalve Salazar ani...@debian.org (supplier of updated gdbm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jul 2014 10:29:02 +0100 Source: gdbm Binary: libgdbm3 libgdbm-dev Architecture: source mips Version: 1.8.3-13 Distribution: unstable Urgency: high Maintainer: Anibal Monsalve Salazar ani...@debian.org Changed-By: Anibal Monsalve Salazar ani...@debian.org Description: libgdbm-dev - GNU dbm database routines (development files) libgdbm3 - GNU dbm database routines (runtime version) Closes: 737943 752465 752830 Changes: gdbm (1.8.3-13) unstable; urgency=high . [ Helmut Grohne ] * Source upload. Closes: #752465 * Move documentation from libgdbm3 to libgdbm-dev to comply with policy 8.2. Closes: #752830 . [ Anibal Monsalve Salazar ] * Bootstrap without texinfo. Patch by Daniel Schepler. Closes: #737943. * Standards Version is 3.9.5. * Remove debian/source/options. * Refresh patches. Checksums-Sha1: ddd80474cd73ebb0c4d5221d24c7af4ccab759e1 1804 gdbm_1.8.3-13.dsc de8ca65d7501e1bf5fa1fc81f6716be7c70fc102 14708 gdbm_1.8.3-13.debian.tar.xz da85d1d5cbe8ed7c0673e8da5642469170824788 28364 libgdbm3_1.8.3-13_mips.deb 043d51afd582e0ab1b941836c3890637590a739a 48810 libgdbm-dev_1.8.3-13_mips.deb Checksums-Sha256: 540d62c3fa66967a68ee11d5fd5ad6d0d0ec7d557cb2422cd3e6bf9f2263a028 1804 gdbm_1.8.3-13.dsc 8cd3f45f64cc8a134c434f3f0c234c5319b6510d83fdd901ec979b38a184425e 14708 gdbm_1.8.3-13.debian.tar.xz 7f33f05db5683a41a09715c93cc033d8e72656012c9a3be93275c8c70b023f9a 28364 libgdbm3_1.8.3-13_mips.deb 59db398cf2a038265a724a33b9340c9a825244afef944d0e97733bba397907f3 48810 libgdbm-dev_1.8.3-13_mips.deb Files: 6ecc306495abd0c647c3744fcc87b11f 28364 libs important libgdbm3_1.8.3-13_mips.deb 845c9e7779350d7d8dcc0aa61c2e8d71 48810 libdevel optional libgdbm-dev_1.8.3-13_mips.deb f1cdf8227909ef727b1d310fc09438f7 1804 libs important gdbm_1.8.3-13.dsc 3c1ba767067a98699a7bacccd2d53f9f 14708 libs important gdbm_1.8.3-13.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTx5xYAAoJEHxWrP6UeJfYBB8P/0YfWAHytib6JFqrA7iRniqV TGhSlrrsIh8jUn8iamw6a6Pw+L2itAF7iP30dD9wBioovq7sM5Z8tpgyQFwWXD4v AMJB/sy5ki/gkVhEfxZjmUZwja8tWUttpbmHOFwiOvRxZMWU7xgwtNv9qpsoeMwZ +Uzzz2+Twjunb0A53u/UT1tbXCt97amoOXdfX41KdV08s+Ums86ciZtXJibzpPqX LGQrG90Potg2kfbLBIExrNqtdlQ784C9mZXqx3Q1r1Al/hQlFjGf8eeKy9Wlt++l bIDgyo6/EqQF6VsWSa5exYkSn3OHiyGY52mQDmr7Ndlv2lbJdkRcEna68EFB9PfC RSAWSnzJbjZl0BvxKXHDmaOxcDpR4NZVugUz7ddu/lmdDzK3Lm13y45M4X9YPXeb
Bug#753291: marked as done (libgdbm3: fails to upgrade: trying to overwrite changelog.Debian.gz which is different)
Your message dated Thu, 17 Jul 2014 10:03:59 + with message-id e1x7ixf-0001ok...@franck.debian.org and subject line Bug#752465: fixed in gdbm 1.8.3-13 has caused the Debian Bug report #752465, regarding libgdbm3: fails to upgrade: trying to overwrite changelog.Debian.gz which is different 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.) -- 752465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libgdbm3 Version: 1.8.3-12+b1 Severity: serious Justification: uninstallable in M-A scenarios Unpacking libgdbm3:amd64 (1.8.3-12+b1) over (1.8.3-12) ... dpkg: error processing archive /var/cache/apt/archives/libgdbm3_1.8.3-12+b1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgdbm3/changelog.Debian.gz', which is different from other instances of package libgdbm3:amd64 My system now looks like this, after APT aborted: root@tglase-dev:~ # apt-cache policy libgdbm3:i386 libgdbm3:i386: Installed: 1.8.3-12+b1 Candidate: 1.8.3-12+b1 Version table: *** 1.8.3-12+b1 0 500 http://mirror.lan.tarent.de/debian/ jessie/main i386 Packages 500 http://ftp.de.debian.org/debian/ jessie/main i386 Packages 100 /var/lib/dpkg/status 1.8.3-11 0 500 http://mirror.lan.tarent.de/debian/ wheezy/main i386 Packages root@tglase-dev:~ # apt-cache policy libgdbm3:amd64 libgdbm3: Installed: 1.8.3-12 Candidate: 1.8.3-12+b1 Version table: 1.8.3-12+b1 0 500 http://mirror.lan.tarent.de/debian/ jessie/main amd64 Packages 500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages *** 1.8.3-12 0 100 /var/lib/dpkg/status 1.8.3-11 0 500 http://mirror.lan.tarent.de/debian/ wheezy/main amd64 Packages -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh ---End Message--- ---BeginMessage--- Source: gdbm Source-Version: 1.8.3-13 We believe that the bug you reported is fixed in the latest version of gdbm, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anibal Monsalve Salazar ani...@debian.org (supplier of updated gdbm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jul 2014 10:29:02 +0100 Source: gdbm Binary: libgdbm3 libgdbm-dev Architecture: source mips Version: 1.8.3-13 Distribution: unstable Urgency: high Maintainer: Anibal Monsalve Salazar ani...@debian.org Changed-By: Anibal Monsalve Salazar ani...@debian.org Description: libgdbm-dev - GNU dbm database routines (development files) libgdbm3 - GNU dbm database routines (runtime version) Closes: 737943 752465 752830 Changes: gdbm (1.8.3-13) unstable; urgency=high . [ Helmut Grohne ] * Source upload. Closes: #752465 * Move documentation from libgdbm3 to libgdbm-dev to comply with policy 8.2. Closes: #752830 . [ Anibal Monsalve Salazar ] * Bootstrap without texinfo. Patch by Daniel Schepler. Closes: #737943. * Standards Version is 3.9.5. * Remove debian/source/options. * Refresh patches. Checksums-Sha1: ddd80474cd73ebb0c4d5221d24c7af4ccab759e1 1804 gdbm_1.8.3-13.dsc de8ca65d7501e1bf5fa1fc81f6716be7c70fc102 14708 gdbm_1.8.3-13.debian.tar.xz da85d1d5cbe8ed7c0673e8da5642469170824788 28364 libgdbm3_1.8.3-13_mips.deb 043d51afd582e0ab1b941836c3890637590a739a 48810 libgdbm-dev_1.8.3-13_mips.deb Checksums-Sha256: 540d62c3fa66967a68ee11d5fd5ad6d0d0ec7d557cb2422cd3e6bf9f2263a028 1804 gdbm_1.8.3-13.dsc 8cd3f45f64cc8a134c434f3f0c234c5319b6510d83fdd901ec979b38a184425e 14708 gdbm_1.8.3-13.debian.tar.xz 7f33f05db5683a41a09715c93cc033d8e72656012c9a3be93275c8c70b023f9a 28364 libgdbm3_1.8.3-13_mips.deb 59db398cf2a038265a724a33b9340c9a825244afef944d0e97733bba397907f3
Bug#753253: marked as done (libgdbm3: Cannot overwrite shared file on upgrade)
Your message dated Thu, 17 Jul 2014 10:03:59 + with message-id e1x7ixf-0001ok...@franck.debian.org and subject line Bug#752465: fixed in gdbm 1.8.3-13 has caused the Debian Bug report #752465, regarding libgdbm3: Cannot overwrite shared file on upgrade 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.) -- 752465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libgdbm3 Severity: normal Dear Maintainer, I have both the amd64 and i386 version of this package installed. When trying to update to the latest version I encountered the following error: Preparing to unpack .../libgdbm3_1.8.3-12+b1_amd64.deb ... Unpacking libgdbm3:amd64 (1.8.3-12+b1) over (1.8.3-12) ... dpkg: error processing archive /var/cache/apt/archives/libgdbm3_1.8.3-12+b1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgdbm3/changelog.Debian.gz', which is different from other instances of package libgdbm3:amd64 Errors were encountered while processing: /var/cache/apt/archives/libgdbm3_1.8.3-12+b1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: dpkg: error processing package libgdbm3:i386 (--configure): package libgdbm3:i386 1.8.3-12+b1 cannot be configured because libgdbm3:amd64 is at a different version (1.8.3-12) Errors were encountered while processing: libgdbm3:i386 This prevents me from upgrading the package. Thanks in advance for looking into this. KR, Ralf -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: gdbm Source-Version: 1.8.3-13 We believe that the bug you reported is fixed in the latest version of gdbm, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anibal Monsalve Salazar ani...@debian.org (supplier of updated gdbm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jul 2014 10:29:02 +0100 Source: gdbm Binary: libgdbm3 libgdbm-dev Architecture: source mips Version: 1.8.3-13 Distribution: unstable Urgency: high Maintainer: Anibal Monsalve Salazar ani...@debian.org Changed-By: Anibal Monsalve Salazar ani...@debian.org Description: libgdbm-dev - GNU dbm database routines (development files) libgdbm3 - GNU dbm database routines (runtime version) Closes: 737943 752465 752830 Changes: gdbm (1.8.3-13) unstable; urgency=high . [ Helmut Grohne ] * Source upload. Closes: #752465 * Move documentation from libgdbm3 to libgdbm-dev to comply with policy 8.2. Closes: #752830 . [ Anibal Monsalve Salazar ] * Bootstrap without texinfo. Patch by Daniel Schepler. Closes: #737943. * Standards Version is 3.9.5. * Remove debian/source/options. * Refresh patches. Checksums-Sha1: ddd80474cd73ebb0c4d5221d24c7af4ccab759e1 1804 gdbm_1.8.3-13.dsc de8ca65d7501e1bf5fa1fc81f6716be7c70fc102 14708 gdbm_1.8.3-13.debian.tar.xz da85d1d5cbe8ed7c0673e8da5642469170824788 28364 libgdbm3_1.8.3-13_mips.deb 043d51afd582e0ab1b941836c3890637590a739a 48810 libgdbm-dev_1.8.3-13_mips.deb Checksums-Sha256: 540d62c3fa66967a68ee11d5fd5ad6d0d0ec7d557cb2422cd3e6bf9f2263a028 1804 gdbm_1.8.3-13.dsc 8cd3f45f64cc8a134c434f3f0c234c5319b6510d83fdd901ec979b38a184425e 14708 gdbm_1.8.3-13.debian.tar.xz 7f33f05db5683a41a09715c93cc033d8e72656012c9a3be93275c8c70b023f9a 28364 libgdbm3_1.8.3-13_mips.deb 59db398cf2a038265a724a33b9340c9a825244afef944d0e97733bba397907f3 48810 libgdbm-dev_1.8.3-13_mips.deb Files: 6ecc306495abd0c647c3744fcc87b11f 28364 libs important libgdbm3_1.8.3-13_mips.deb 845c9e7779350d7d8dcc0aa61c2e8d71 48810 libdevel optional libgdbm-dev_1.8.3-13_mips.deb f1cdf8227909ef727b1d310fc09438f7 1804 libs important gdbm_1.8.3-13.dsc
Bug#754676: marked as done (openttd: FTBFS on mips powerpc s390x (sparc))
Your message dated Thu, 17 Jul 2014 10:07:28 + with message-id e1x7ib2-0002rh...@franck.debian.org and subject line Bug#754676: fixed in openttd 1.4.1-1 has caused the Debian Bug report #754676, regarding openttd: FTBFS on mips powerpc s390x (sparc) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 754676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: openttd Version: 1.4.0-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on various architectures due to unexpected failures in the test suite. Full build logs: https://buildd.debian.org/status/fetch.php?pkg=openttdarch=mipsver=1.4.0-1stamp=1399986141 https://buildd.debian.org/status/fetch.php?pkg=openttdarch=powerpcver=1.4.0-1stamp=1404609365 https://buildd.debian.org/status/fetch.php?pkg=openttdarch=s390xver=1.4.0-1stamp=1403694878 (https://buildd.debian.org/status/fetch.php?pkg=openttdarch=sparcver=1.4.0-1stamp=1400165127) Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: openttd Source-Version: 1.4.1-1 We believe that the bug you reported is fixed in the latest version of openttd, 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 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthijs Kooijman matth...@stdin.nl (supplier of updated openttd 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, 17 Jul 2014 09:31:51 +0200 Source: openttd Binary: openttd openttd-dbg openttd-data Architecture: source amd64 all Version: 1.4.1-1 Distribution: unstable Urgency: medium Maintainer: Matthijs Kooijman matth...@stdin.nl Changed-By: Matthijs Kooijman matth...@stdin.nl Description: openttd- reimplementation of Transport Tycoon Deluxe with enhancements openttd-data - common data files for the OpenTTD game openttd-dbg - debugging symbols for openttd Closes: 754676 Changes: openttd (1.4.1-1) unstable; urgency=medium . * [7ddef46] New upstream release 1.4.1. - Fixed segfault during load on big endian machines. (Closes: #754676) * [54bf392] Remove build-with-libpng16.patch, which is included upstream. Checksums-Sha1: 74a5b9985056582549341ed56e24670da07c4231 1530 openttd_1.4.1-1.dsc 3e4c88cd68a878ffcd723813c809fc42f24935c2 10052089 openttd_1.4.1.orig.tar.gz d06c799fdf86b4148e241b21ed8d9efda3304ae5 10932 openttd_1.4.1-1.debian.tar.xz 4eda94b483073757a45f53600172081134c5e8ed 2096822 openttd_1.4.1-1_amd64.deb 7e5b6789a4b938ea36554308ddd6bfd62f83772c 10239246 openttd-dbg_1.4.1-1_amd64.deb 58336ba1529029ec22435c62af6be2393218fbc6 2623756 openttd-data_1.4.1-1_all.deb Checksums-Sha256: b015f394a1de8503542973433c863428e8187a6f9e7bc62fb06adb8379a6264f 1530 openttd_1.4.1-1.dsc 60ec7c1b6962eea36a84d70ec289fb1c900ca8d2b5da414f7330204d20b948ac 10052089 openttd_1.4.1.orig.tar.gz 28e344b63fdc255af83706c01cfb9da85473af7c8cef6f45e707eb8e5e9ecb32 10932 openttd_1.4.1-1.debian.tar.xz b89ab34a925e3aa2c0a9732d3ae4234b91385412a5710f0f64220be65c1c3773 2096822 openttd_1.4.1-1_amd64.deb a39bc7797403cd8717530183778decd13a2071bde7ca706273ad9a44d4b5680b 10239246 openttd-dbg_1.4.1-1_amd64.deb e9b96dfff0e5659730389bbe6988fc432f4b8a72b5329577f7c80764e4ba829d 2623756 openttd-data_1.4.1-1_all.deb Files: 5de96ee22f7449d425342147fb8c86b1 2096822 games optional openttd_1.4.1-1_amd64.deb c236d9aeaeb7cdd688b77dd7ef91eead 10239246 debug extra openttd-dbg_1.4.1-1_amd64.deb b61ff10fd7959ac8076add89ab4d5dd7 2623756 games optional openttd-data_1.4.1-1_all.deb 7b7b555a95beba61f12ab098e492785e 1530 games optional openttd_1.4.1-1.dsc 63c8d3cc09030200a12122d41ae2dd49 10052089 games optional openttd_1.4.1.orig.tar.gz bc46958ec6da6736deecb308f8276f43 10932 games optional openttd_1.4.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlPHmEYACgkQz0nQ5oovr7wSXACfSFeHo5aJYIh8TppwJxAW6xcw dOAAn3bQYJf0EiDNrykZm7gvsF/00H/j =E0FO -END PGP SIGNATUREEnd Message---
Bug#752425: marked as done (xfce4-session: upower-1.0 transition)
Your message dated Thu, 17 Jul 2014 10:07:46 + with message-id e1x7ibk-0003fq...@franck.debian.org and subject line Bug#752425: fixed in xfce4-session 4.10.1-7 has caused the Debian Bug report #752425, regarding xfce4-session: upower-1.0 transition to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 752425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xfce4-session Version: 4.10.1-6 Severity: normal User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: upower-1.0 upower 0.99.0 (currently available in experimental) has dropped many deprecated APIs and some important functionality. Among them is the removal of suspend / hibernate support, which is now handled by systemd/logind [1], or the removal of the D-Bus notify_sleep/notify_resume signals. For a full list of changes please see [2]. In preparation for the upower 1.0 transition [3] I'm filing this bug because your package declares a relationship with upower (suggests/recommends/depends). Please check your package carefully, if it uses / requires some of that functionality and make sure it's still working with the new upower version. [1] http://www.freedesktop.org/wiki/Software/systemd/inhibit/ [2] http://lists.freedesktop.org/archives/devkit-devel/2013-October/001519.html [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751953 ---End Message--- ---BeginMessage--- Source: xfce4-session Source-Version: 4.10.1-7 We believe that the bug you reported is fixed in the latest version of xfce4-session, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jackson Doak nosk...@ubuntu.com (supplier of updated xfce4-session 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, 17 Jul 2014 06:37:50 +1000 Source: xfce4-session Binary: xfce4-session xfce4-session-dbg Architecture: source amd64 Version: 4.10.1-7 Distribution: unstable Urgency: medium Maintainer: Debian Xfce Maintainers pkg-xfce-de...@lists.alioth.debian.org Changed-By: Jackson Doak nosk...@ubuntu.com Description: xfce4-session - Xfce4 Session Manager xfce4-session-dbg - Xfce4 Session Manager (debug symbols) Closes: 752425 Changes: xfce4-session (4.10.1-7) unstable; urgency=medium . * Check for logind support at runtime: - debian/patches/03_runtime-logind-support.patch: added. + Allows upower 0.99 support. closes: #752425 - debian/rules: + call xdt-autogen after patching + clean up autogenerated files modified by xdt-autogen. - debian/control: + add build-dep on libpolkit-gobject-1-dev. + add build-dep on xfce4-dev-tools and libtool in order to run xdt-autogen after patching. Checksums-Sha1: 8f10cb6f294ad6f06215c7386fe32cb46a0afdd9 1732 xfce4-session_4.10.1-7.dsc 614af3ff508dc97b21cbb6b53ca13ad998271023 14880 xfce4-session_4.10.1-7.debian.tar.xz 4a5db5754044eef38fd69b67d559e4a25128e31d 727866 xfce4-session_4.10.1-7_amd64.deb 68b037cabd2510d67ac0e7a2171636a9be929971 535382 xfce4-session-dbg_4.10.1-7_amd64.deb Checksums-Sha256: c7dc6bc781910339ff614c8d53e3375b32c27f0f5a99ac2812f48cb7fd1eabc2 1732 xfce4-session_4.10.1-7.dsc f69159719427e98de12655ce681eac5dbbda8defc6fd7df9c940ed8e33202916 14880 xfce4-session_4.10.1-7.debian.tar.xz d28a7098537162d36750dd0e98caa31a25474fbb014be40c3db94c4d735e823d 727866 xfce4-session_4.10.1-7_amd64.deb 511a1d21328e74b94517c44c4dd33013b28da469518059e80cfefc695d6f2294 535382 xfce4-session-dbg_4.10.1-7_amd64.deb Files: 78f462f99e4152161796115d7ee6846c 727866 xfce optional xfce4-session_4.10.1-7_amd64.deb fd794a92f1c2a7b37c6a45e9e8ad12c5 535382 debug extra xfce4-session-dbg_4.10.1-7_amd64.deb effad84a87a893c041f6b6123613f9a0 1732 xfce optional xfce4-session_4.10.1-7.dsc e19bcdbc63f86493e31fc592d3365cd4 14880 xfce optional xfce4-session_4.10.1-7.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlPHmhkACgkQcgQ2cL3l8e5LzACZAXp+W53Fo475MbDrzadzYA5T mWEAn3HiKHYRQ0gVyDJeSllWXi/zTmKu =Zv9+ -END PGP
Bug#754846: marked as done (upower upgrade breaks xfce4-power-manager suspend)
Your message dated Thu, 17 Jul 2014 10:07:37 + with message-id e1x7ibb-0002y1...@franck.debian.org and subject line Bug#752428: fixed in xfce4-power-manager 1.2.0-5 has caused the Debian Bug report #752428, regarding upower upgrade breaks xfce4-power-manager suspend 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.) -- 752428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: upower Version: 0.99.0-3 Severity: important Dear Maintainer, after upgrading upower:amd64 (0.9.23-2+b2, 0.99.0-3), xfce4-power-manager can no longer suspend the system in response to a hardware power button press. Notification dialog screenshot attached. In /etc/systemd/logind.conf I am using HandlePowerKey=ignore so xfce4-power-manager can handle the button press and lock the screen before suspend. Now suspend fails. Using: xfce4-power-manager 1.2.0-4 amd64 Kind regards, Ben. -- System Information: Debian Release: jessie/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=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages upower depends on: ii dbus 1.8.6-1 ii libc6 2.19-7 ii libdbus-1-31.8.6-1 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.40.0-3 ii libgudev-1.0-0 204-14 ii libimobiledevice4 1.1.6+dfsg-2 ii libplist2 1.11-3 ii libpolkit-gobject-1-0 0.105-6 ii libupower-glib20.99.0-3 ii libusb-1.0-0 2:1.0.19-1 ii pm-utils 1.4.1-15 ii systemd204-14 ii udev 204-14 Versions of packages upower recommends: ii policykit-1 0.105-6 upower suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: xfce4-power-manager Source-Version: 1.2.0-5 We believe that the bug you reported is fixed in the latest version of xfce4-power-manager, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jackson Doak nosk...@ubuntu.com (supplier of updated xfce4-power-manager 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, 17 Jul 2014 06:20:22 +1000 Source: xfce4-power-manager Binary: xfce4-power-manager xfce4-power-manager-data xfce4-power-manager-plugins Architecture: source amd64 all Version: 1.2.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Xfce Maintainers pkg-xfce-de...@lists.alioth.debian.org Changed-By: Jackson Doak nosk...@ubuntu.com Description: xfce4-power-manager - power manager for Xfce desktop xfce4-power-manager-data - power manager for Xfce desktop, arch-indep files xfce4-power-manager-plugins - power manager plugins for Xfce panel Closes: 752428 Changes: xfce4-power-manager (1.2.0-5) unstable; urgency=medium . * Add patch to support upower 0.99. Closes: #752428 * Bump upower depend to = 0.99 Checksums-Sha1: 9763648f040bed7a6373bfd6288c9a479c039638 1933 xfce4-power-manager_1.2.0-5.dsc 8e217eb48d4bbd7f7690f4f12c9c71f38ed504eb 16812 xfce4-power-manager_1.2.0-5.debian.tar.xz 376425492ce8360e557232b94bec7a718a2eee48 141848 xfce4-power-manager_1.2.0-5_amd64.deb 19c029aea150b7f0ab621a4077d547a643cd344c 530488 xfce4-power-manager-data_1.2.0-5_all.deb 142630475d581809df690fee17142752638e4516 84102 xfce4-power-manager-plugins_1.2.0-5_amd64.deb Checksums-Sha256: 7693da3806a28d06632ba6c0288b7255f1db8266ae33312d990961709082bdcd 1933 xfce4-power-manager_1.2.0-5.dsc d336fbbf61eb10610ba8b7e61b24fcf28ea3365a096424e7bef300e7255fc28c 16812 xfce4-power-manager_1.2.0-5.debian.tar.xz 32c2cb0c2079017b9463b9e15818d35d0758def0b44c9bb26bd5693e7f1a469a 141848 xfce4-power-manager_1.2.0-5_amd64.deb 575b5c664c9cfa4a1346c0c4b78b76503519d70536d3a7f847f9d9187163122f 530488 xfce4-power-manager-data_1.2.0-5_all.deb 8482ad4d05d09502a457d163949046c4bdf12fa3414486441cf7ac82101186bd 84102
Bug#754850: marked as done (upower: no suspend/hibernate on non-systemd systems)
Your message dated Thu, 17 Jul 2014 10:07:46 + with message-id e1x7ibk-0003fq...@franck.debian.org and subject line Bug#752425: fixed in xfce4-session 4.10.1-7 has caused the Debian Bug report #752425, regarding upower: no suspend/hibernate on non-systemd systems 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.) -- 752425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: upower Version: 0.99.0-3 Severity: important The newest update of upower (0.99.0-3) doesn't appear to be functional anymore. As I'm on a desktop, this means suspend and hibernate (obviously, there's no battery I could test). These functions don't even show up in XFCE's logout menu. On the other hand, pm-utils (pm-suspend from the command line) are fully functional. Unlike #718493 which is caused by interactions with logind, my system is free of any systemd components, so this is an unrelated regression. upower 0.9.23-2+b2 worked fine. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.15.3-x32 (SMP w/6 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 upower depends on: ii dbus 1.8.6-1 ii libc6 2.19-5 ii libdbus-1-31.8.6-1 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.40.0-3 ii libgudev-1.0-0 204-14 ii libimobiledevice4 1.1.6+dfsg-2 ii libplist2 1.11-3 pn libpolkit-gobject-1-0 none ii libupower-glib10.9.23-2+b2 ii libusb-1.0-0 2:1.0.19-1 ii pm-utils 1.4.1-15 ii udev 204-14 Versions of packages upower recommends: ii policykit-1 0.105-4 upower suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: xfce4-session Source-Version: 4.10.1-7 We believe that the bug you reported is fixed in the latest version of xfce4-session, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jackson Doak nosk...@ubuntu.com (supplier of updated xfce4-session 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, 17 Jul 2014 06:37:50 +1000 Source: xfce4-session Binary: xfce4-session xfce4-session-dbg Architecture: source amd64 Version: 4.10.1-7 Distribution: unstable Urgency: medium Maintainer: Debian Xfce Maintainers pkg-xfce-de...@lists.alioth.debian.org Changed-By: Jackson Doak nosk...@ubuntu.com Description: xfce4-session - Xfce4 Session Manager xfce4-session-dbg - Xfce4 Session Manager (debug symbols) Closes: 752425 Changes: xfce4-session (4.10.1-7) unstable; urgency=medium . * Check for logind support at runtime: - debian/patches/03_runtime-logind-support.patch: added. + Allows upower 0.99 support. closes: #752425 - debian/rules: + call xdt-autogen after patching + clean up autogenerated files modified by xdt-autogen. - debian/control: + add build-dep on libpolkit-gobject-1-dev. + add build-dep on xfce4-dev-tools and libtool in order to run xdt-autogen after patching. Checksums-Sha1: 8f10cb6f294ad6f06215c7386fe32cb46a0afdd9 1732 xfce4-session_4.10.1-7.dsc 614af3ff508dc97b21cbb6b53ca13ad998271023 14880 xfce4-session_4.10.1-7.debian.tar.xz 4a5db5754044eef38fd69b67d559e4a25128e31d 727866 xfce4-session_4.10.1-7_amd64.deb 68b037cabd2510d67ac0e7a2171636a9be929971 535382 xfce4-session-dbg_4.10.1-7_amd64.deb Checksums-Sha256: c7dc6bc781910339ff614c8d53e3375b32c27f0f5a99ac2812f48cb7fd1eabc2 1732 xfce4-session_4.10.1-7.dsc f69159719427e98de12655ce681eac5dbbda8defc6fd7df9c940ed8e33202916 14880 xfce4-session_4.10.1-7.debian.tar.xz d28a7098537162d36750dd0e98caa31a25474fbb014be40c3db94c4d735e823d 727866 xfce4-session_4.10.1-7_amd64.deb 511a1d21328e74b94517c44c4dd33013b28da469518059e80cfefc695d6f2294 535382
Bug#752428: marked as done (xfce4-power-manager: upower-1.0 transition)
Your message dated Thu, 17 Jul 2014 10:07:37 + with message-id e1x7ibb-0002y1...@franck.debian.org and subject line Bug#752428: fixed in xfce4-power-manager 1.2.0-5 has caused the Debian Bug report #752428, regarding xfce4-power-manager: upower-1.0 transition to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 752428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xfce4-power-manager Version: 1.2.0-4 Severity: normal User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: upower-1.0 upower 0.99.0 (currently available in experimental) has dropped many deprecated APIs and some important functionality. Among them is the removal of suspend / hibernate support, which is now handled by systemd/logind [1], or the removal of the D-Bus notify_sleep/notify_resume signals. For a full list of changes please see [2]. In preparation for the upower 1.0 transition [3] I'm filing this bug because your package declares a relationship with upower (suggests/recommends/depends). Please check your package carefully, if it uses / requires some of that functionality and make sure it's still working with the new upower version. [1] http://www.freedesktop.org/wiki/Software/systemd/inhibit/ [2] http://lists.freedesktop.org/archives/devkit-devel/2013-October/001519.html [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751953 ---End Message--- ---BeginMessage--- Source: xfce4-power-manager Source-Version: 1.2.0-5 We believe that the bug you reported is fixed in the latest version of xfce4-power-manager, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jackson Doak nosk...@ubuntu.com (supplier of updated xfce4-power-manager 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, 17 Jul 2014 06:20:22 +1000 Source: xfce4-power-manager Binary: xfce4-power-manager xfce4-power-manager-data xfce4-power-manager-plugins Architecture: source amd64 all Version: 1.2.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Xfce Maintainers pkg-xfce-de...@lists.alioth.debian.org Changed-By: Jackson Doak nosk...@ubuntu.com Description: xfce4-power-manager - power manager for Xfce desktop xfce4-power-manager-data - power manager for Xfce desktop, arch-indep files xfce4-power-manager-plugins - power manager plugins for Xfce panel Closes: 752428 Changes: xfce4-power-manager (1.2.0-5) unstable; urgency=medium . * Add patch to support upower 0.99. Closes: #752428 * Bump upower depend to = 0.99 Checksums-Sha1: 9763648f040bed7a6373bfd6288c9a479c039638 1933 xfce4-power-manager_1.2.0-5.dsc 8e217eb48d4bbd7f7690f4f12c9c71f38ed504eb 16812 xfce4-power-manager_1.2.0-5.debian.tar.xz 376425492ce8360e557232b94bec7a718a2eee48 141848 xfce4-power-manager_1.2.0-5_amd64.deb 19c029aea150b7f0ab621a4077d547a643cd344c 530488 xfce4-power-manager-data_1.2.0-5_all.deb 142630475d581809df690fee17142752638e4516 84102 xfce4-power-manager-plugins_1.2.0-5_amd64.deb Checksums-Sha256: 7693da3806a28d06632ba6c0288b7255f1db8266ae33312d990961709082bdcd 1933 xfce4-power-manager_1.2.0-5.dsc d336fbbf61eb10610ba8b7e61b24fcf28ea3365a096424e7bef300e7255fc28c 16812 xfce4-power-manager_1.2.0-5.debian.tar.xz 32c2cb0c2079017b9463b9e15818d35d0758def0b44c9bb26bd5693e7f1a469a 141848 xfce4-power-manager_1.2.0-5_amd64.deb 575b5c664c9cfa4a1346c0c4b78b76503519d70536d3a7f847f9d9187163122f 530488 xfce4-power-manager-data_1.2.0-5_all.deb 8482ad4d05d09502a457d163949046c4bdf12fa3414486441cf7ac82101186bd 84102 xfce4-power-manager-plugins_1.2.0-5_amd64.deb Files: 279f2fd88926245747c3ac6d49f691fc 141848 xfce optional xfce4-power-manager_1.2.0-5_amd64.deb f4b45cca87ea7b755dbb9adfbec2edd8 530488 xfce optional xfce4-power-manager-data_1.2.0-5_all.deb fc7659507af4575f271eb434554ba854 84102 xfce optional xfce4-power-manager-plugins_1.2.0-5_amd64.deb 0d8d3a6ec6f99bd4e1c1c860f9569183 1933 xfce optional xfce4-power-manager_1.2.0-5.dsc e94b81f81d6e2f0e054e71f30f19cf1d 16812 xfce optional xfce4-power-manager_1.2.0-5.debian.tar.xz
Bug#752430: marked as done (xfce4-systemload-plugin: upower-1.0 transition)
Your message dated Thu, 17 Jul 2014 10:07:53 + with message-id e1x7ibr-0003m7...@franck.debian.org and subject line Bug#752430: fixed in xfce4-systemload-plugin 1.1.1-3 has caused the Debian Bug report #752430, regarding xfce4-systemload-plugin: upower-1.0 transition to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 752430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xfce4-systemload-plugin Version: 1.1.1-2 Severity: normal User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: upower-1.0 upower 0.99.0 (currently available in experimental) has dropped many deprecated APIs and some important functionality. Among them is the removal of suspend / hibernate support, which is now handled by systemd/logind [1], or the removal of the D-Bus notify_sleep/notify_resume signals. For a full list of changes please see [2]. In preparation for the upower 1.0 transition [3] I'm filing this bug because your package declares a relationship with upower (suggests/recommends/depends). Please check your package carefully, if it uses / requires some of that functionality and make sure it's still working with the new upower version. [1] http://www.freedesktop.org/wiki/Software/systemd/inhibit/ [2] http://lists.freedesktop.org/archives/devkit-devel/2013-October/001519.html [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751953 ---End Message--- ---BeginMessage--- Source: xfce4-systemload-plugin Source-Version: 1.1.1-3 We believe that the bug you reported is fixed in the latest version of xfce4-systemload-plugin, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jackson Doak nosk...@ubuntu.com (supplier of updated xfce4-systemload-plugin 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, 16 Jul 2014 07:06:52 +1000 Source: xfce4-systemload-plugin Binary: xfce4-systemload-plugin Architecture: source amd64 Version: 1.1.1-3 Distribution: unstable Urgency: low Maintainer: Debian Xfce Maintainers pkg-xfce-de...@lists.alioth.debian.org Changed-By: Jackson Doak nosk...@ubuntu.com Description: xfce4-systemload-plugin - system load monitor plugin for the Xfce4 panel Closes: 752430 Changes: xfce4-systemload-plugin (1.1.1-3) unstable; urgency=low . [ Evgeni Golov ] * Correct Vcs-* URLs to point to anonscm.debian.org . [ Jackson Doak ] * Support upower 0.99 closes: #752430 - Add 01_upower-0.99.patch - Bump upower depend to = 0.99 Checksums-Sha1: 9ca5ef85f87bcf0360b40ad8662f61f9bc3de5e4 1630 xfce4-systemload-plugin_1.1.1-3.dsc 193ef85ff26d4e2f803aa7404177458a8fbe6274 4496 xfce4-systemload-plugin_1.1.1-3.debian.tar.xz aeb39fd239a64b662cb61265ddcf80ca460a8cf2 51308 xfce4-systemload-plugin_1.1.1-3_amd64.deb Checksums-Sha256: b36a9bda105f12adf09d1cc9bd9f65f88c0fbf07f07ce6fd94d3e6106e8549ee 1630 xfce4-systemload-plugin_1.1.1-3.dsc c7ef350a5cebabb061633d5b2cc3e0ae654d1fed04bc9386a60b9b5e443f2dc1 4496 xfce4-systemload-plugin_1.1.1-3.debian.tar.xz 318ccb1b297af40ebe5ee3681a43dd082ff3e1dcfc3a55ea08d739a36eff3370 51308 xfce4-systemload-plugin_1.1.1-3_amd64.deb Files: 7027dc41e1c10a01cd8eab28de9f25b1 51308 xfce optional xfce4-systemload-plugin_1.1.1-3_amd64.deb 04e64772ce4ea4662470dceb4c13b965 1630 xfce optional xfce4-systemload-plugin_1.1.1-3.dsc 0d3a5e04ce18e37b03e3e4bb2c6cf522 4496 xfce optional xfce4-systemload-plugin_1.1.1-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlPHmhkACgkQcgQ2cL3l8e4mJQCdH2hzmItgm4vQoDbe1GJ0uZ3H qEgAoLyEst+ne/oWqluGohdXRaI8XW5y =sDi0 -END PGP SIGNATUREEnd Message---
Bug#741415: say goodbye to network-manager-strongswan?
On 07/16/14 17:56, Thomas Goirand wrote: To try to kill your frustration, I have sponsored the upload of your fix to the delayed/10 queue. If everything goes well, then in 15 days, network-manager-strongswan will be back in Jessie. Thanx very much for your help Regards Harri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755059: redmine: Unable to install backported version of Redmine (2.5.1-2~bpo70+1) due to missing deps
Package: redmine Version: 2.5.1-2~bpo70+1 Severity: grave Justification: renders package unusable Package: redmine Version: 2.5.1-2~bpo70+1 Severity: grave Justification: renders package unusable Dear Maintainer, I cannot install the wheezy-backport version of Redmine since today due to the new uploaded debian version of redmine. Some dependencies are unavailable in backport but only in jessie/sid/exp. I'm not sure but I guess that dependencies for Redmine should be at least in backport too. Here are the apt error: # apt-get install redmine Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: redmine : Depends: ruby-railties-3.2 (= 3.2.16-1~) but it is not going to be installed Depends: ruby-rack (= 1.4.5~) but 1.4.1-2.1 is to be installed or ruby-rack1.4 but it is not installable Depends: ruby-awesome-nested-set but it is not installable E: Unable to correct problems, you have held broken packages. $ cat /etc/apt/sources.list.d/* deb http://pkg.jenkins-ci.org/debian binary/ deb http://security.debian.org/ wheezy/updates main deb http://http.debian.net/debian wheezy-updates main deb http://http.debian.net/debian wheezy-backports main $ cat /etc/apt/sources.list deb http://http.debian.net/debian wheezy main Cheers, Fabien -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise') Architecture: amd64 (x86_64) Kernel: Linux 3.2.54-fbo (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718068: csh: FTBFS: Makefile:24: *** missing separator. Stop.
I am consider NMU it. Any objection? -- YunQiang Su -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755062: systemd: Syslog (contents that journalctl shows) stopped working after upgrading from 204-14 to 208-6
Package: systemd Version: 208-6 Severity: grave Justification: causes data loss Hi, I upgraded from 204-14 to 208-6 last night and today in the morning, I noticed that journalctl doesn't show any entries from after the upgrade. Neither the at that time running journalctl -f nor a freshly called journalctl show anything new. Just calling journalctl, it shows all messages from boot up to when the upgrade happened. There is no syslog daemon like e.g. rsyslog installed. I have not yet rebooted, but I do expect that syslog must work after upgrading systemd without having rebooted. Otherwise it would be a severe data loss. And even if that would be the case: Either the running jpurnalctl -f from 204 or the just called journalctl from 208 should show something in this case. If I can provide more information to investigate this issue, feel free to ask. I'm though currently travelling (actually I noticed it because I wanted to check for ppp messages in syslog) so I may lag a little bit with regards to responses. -- Package-specific info: -- BEGIN ATTACHMENTS -- /tmp/tmp.R3QmnrfIV3/systemd-delta.txt /tmp/tmp.R3QmnrfIV3/systemd-analyze-dump.txt /tmp/tmp.R3QmnrfIV3/dsh-enabled.txt -- END ATTACHMENTS -- -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.15-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 systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.2 ii libacl1 2.2.52-1 ii libaudit11:2.3.7-1 ii libblkid12.20.1-5.8 ii libc62.19-7 ii libcap2 1:2.22-2 ii libcap2-bin 1:2.22-2 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.6-1 ii libgcrypt11 1.5.3-4 ii libkmod2 18-1 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.3-1 ii libsystemd-daemon0 208-6 ii libsystemd-journal0 208-6 ii libsystemd-login0208-6 ii libudev1 208-6 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.2 ii udev 208-6 ii util-linux 2.20.1-5.8 Versions of packages systemd recommends: ii libpam-systemd 208-6 Versions of packages systemd suggests: ii systemd-ui 3-2 -- Configuration Files: /etc/systemd/logind.conf changed: [Login] HandleLidSwitch=suspend -- no debconf information
Processed: Re: [php-maint] Bug#755057: Empty /usr/share/php5/php.ini-production in package php5-common on jessie/sid
Processing control commands: severity -1 serious Bug #755057 [php5-common] Empty /usr/share/php5/php.ini-production in package php5-common on jessie/sid Severity set to 'serious' from 'normal' -- 755057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755057 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#707268: Bug#725957: [NMU] Bug#740085: package plplot 5.10.0
Hi Thibaut, Thibaut Paumard wrote: I'd rather sponsor a package you would have prepared, but failing that How did you fail that? I reviewed his package at https://mentors.debian.net/package/plplot and IIRC the only main issues left were the upstream inclusion of prebuilt javascript files (jquery et al). There are multiple ways to mitigate this. At least the jquery issue is seen very differently under Debian developers. I'm though likely not able to sponsor the (fixed or workarounded) package the next few days as I'm currently travelling. So feel free to sponsor it, if you have time. I'd be happy about it. I can forward you my findings this evening, if preferred. I'd take care of the next GDL upload then in a few days. 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 signature.asc Description: Digital signature
Bug#754963: clang-3.4: /usr/bin/ld: cannot find crtbegin.o: No such file or directory
Hello, If you install libgcc-4.7-dev or libgcc-4.8-dev, the problem goes away. The dependency exists (on gcc 4.9) : Depends: libc6 (= 2.15), libclang1-3.4 (= 1:3.4.2-4), libffi6 (= 3.0.4), libgcc1 (= 1:4.1.1), libllvm3.4, libstdc++6 (= 4.9), libtinfo5, libstdc++-4.9-dev, libgcc-4.9-dev, libobjc-4.9-dev, libclang-common-3.4-dev (= 1:3.4.2-4), libc6-dev Confirmed by: https://packages.debian.org/sid/clang-3.4 I guess that clang search of gcc needs to be updated Cheers, Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755062: systemd: Syslog (contents that journalctl shows) stopped working after upgrading from 204-14 to 208-6
Am 17.07.2014 13:00, schrieb Axel Beckert: I upgraded from 204-14 to 208-6 last night and today in the morning, I noticed that journalctl doesn't show any entries from after the upgrade. Neither the at that time running journalctl -f nor a freshly called journalctl show anything new. Just calling journalctl, it shows all messages from boot up to when the upgrade happened. There is no syslog daemon like e.g. rsyslog installed. I have not yet rebooted, but I do expect that syslog must work after upgrading systemd without having rebooted. Otherwise it would be a severe data loss. And even if that would be the case: Either the running jpurnalctl -f from 204 or the just called journalctl from 208 should show something in this case. If I can provide more information to investigate this issue, feel free to ask. I'm though currently travelling (actually I noticed it because I wanted to check for ppp messages in syslog) so I may lag a little bit with regards to responses. Do you use persistent logging (i.e. do you have a /var/log/journal directory) or do you use volatile logging? What are the permissions of of the journal directory and the files therein (either /var/log/journal or /run/log/journal)? What is the output of systemctl status systemd-journald.service systemd-journald.socket Is the systemd-journald process still running? Can you strace it and trigger a log message via logger. -- 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#754963: clang-3.4: /usr/bin/ld: cannot find crtbegin.o: No such file or directory
On 17/07/2014 13:38, Sylvestre Ledru wrote: Hello, If you install libgcc-4.7-dev or libgcc-4.8-dev, the problem goes away. The dependency exists (on gcc 4.9) : Depends: libc6 (= 2.15), libclang1-3.4 (= 1:3.4.2-4), libffi6 (= 3.0.4), libgcc1 (= 1:4.1.1), libllvm3.4, libstdc++6 (= 4.9), libtinfo5, libstdc++-4.9-dev, libgcc-4.9-dev, libobjc-4.9-dev, libclang-common-3.4-dev (= 1:3.4.2-4), libc6-dev Confirmed by: https://packages.debian.org/sid/clang-3.4 I guess that clang search of gcc needs to be updated Jakub, what is the result of clang -v ? Thanks, Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754963: clang-3.4: /usr/bin/ld: cannot find crtbegin.o: No such file or directory
* Sylvestre Ledru sylves...@debian.org, 2014-07-17, 13:50: what is the result of clang -v ? $ clang -v echo EOF Debian clang version 3.4.2-4 (tags/RELEASE_34/dot2-final) (based on LLVM 3.4.2) Target: i386-pc-linux-gnu Thread model: posix Selected GCC installation: EOF Perhaps it's because gcc-4.9 uses i586-linux-gnu as triplet (unlike previous versions, which use i486-linux-gnu)? -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747012: marked as done (libtrio: FTBFS on powerpc, s390x and sparc)
Your message dated Thu, 17 Jul 2014 12:00:07 + with message-id e1x7km3-0008p8...@franck.debian.org and subject line Bug#747012: fixed in libtrio 1.16+dfsg1-1 has caused the Debian Bug report #747012, regarding libtrio: FTBFS on powerpc, s390x and sparc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 747012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libtrio Version: 1.14+dfsg-2 Severity: serious Justification: fails to build from source Hi Balint, I dare say you've noticed, I just wanted to make sure this is tracked: libtrio fails to build from source on powerpc, s390x and sparc. See https://buildd.debian.org/status/package.php?p=libtrio for details... Regards, Stephen -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: libtrio Source-Version: 1.16+dfsg1-1 We believe that the bug you reported is fixed in the latest version of libtrio, 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 747...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Balint Reczey bal...@balintreczey.hu (supplier of updated libtrio 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, 16 Jul 2014 16:42:37 +0200 Source: libtrio Binary: libtrio-dev libtrio2 Architecture: source i386 Version: 1.16+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Balint Reczey bal...@balintreczey.hu Changed-By: Balint Reczey bal...@balintreczey.hu Description: libtrio-dev - portable and extendable printf and string functions development f libtrio2 - portable and extendable printf and string functions Closes: 747012 Changes: libtrio (1.16+dfsg1-1) unstable; urgency=medium . * New upstream release - Fixed accuracy problems on platforms with double-double support. (Closes: #747012) * Exclude generated documentation from .orig tarball using debian/copyright * Drop 0001-build-shared-lib.patch since it has been integrated upstream * Update mangling in debian/watch * Bump .so version and library package name * Migrate to symbols file from shlibs file * Bump standards version, no changes needed Checksums-Sha1: c7b187f9c0d34b556e6e13eafb918827467d725b 1949 libtrio_1.16+dfsg1-1.dsc 3c9f3d962c429843067047e5d75b497b676644dd 110688 libtrio_1.16+dfsg1.orig.tar.xz 81aa94ea27122a0437dc1666ff08948a3e0b739d 4264 libtrio_1.16+dfsg1-1.debian.tar.xz eff4bcaeea91459912e6cf7bc58489a56e42a325 88064 libtrio-dev_1.16+dfsg1-1_i386.deb 9c5d28d43d416b3d780b8a2926a4931cee865271 43892 libtrio2_1.16+dfsg1-1_i386.deb Checksums-Sha256: eba94b94f21e07f715d1a989cf1da7f9755bda6702a9d7a2018b217cdc3cbffc 1949 libtrio_1.16+dfsg1-1.dsc b429c6f2d16f3044fc38fc9f7f8bfdf771bddb3394a526d2a3e6b871b4179568 110688 libtrio_1.16+dfsg1.orig.tar.xz b19dc5aff014ce707836432a63721eb992a73977a917540b6bb9ff57ef6925c4 4264 libtrio_1.16+dfsg1-1.debian.tar.xz 742c7cd1a93ea4e4bd02d9ed79b339c28670f086bc3f8d4c43012e6eb388b73b 88064 libtrio-dev_1.16+dfsg1-1_i386.deb c9f710d48fe0c2d6c3689a7fb37b76e2564c5da4c16dc7893cefb7ab727db721 43892 libtrio2_1.16+dfsg1-1_i386.deb Files: c8902c6a9a03b163a74ea38957b09f4f 88064 libdevel extra libtrio-dev_1.16+dfsg1-1_i386.deb 94e47bafca986b5de64254b2c09591a2 43892 libs extra libtrio2_1.16+dfsg1-1_i386.deb 0ab6619a4b2fee11d067b88772cd2e04 1949 libs extra libtrio_1.16+dfsg1-1.dsc 20aaf2a0c65148bf2e0a1cf9e1de59ef 110688 libs extra libtrio_1.16+dfsg1.orig.tar.xz e82d9598079cb658c9c69ee695ff5169 4264 libs extra libtrio_1.16+dfsg1-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJTxq36AAoJEPZk0la0aRp9YXQQAKc39Alz3lbbC147/Jwdz+Un 2R3VzsBgtJWpVT9QwmzgRascoATmOvCaFvAoNM0BuqHIuAeZVsEU83mQmb2tjUOE
Bug#754963: clang-3.4: /usr/bin/ld: cannot find crtbegin.o: No such file or directory
On 17/07/2014 13:59, Jakub Wilk wrote: * Sylvestre Ledru sylves...@debian.org, 2014-07-17, 13:50: what is the result of clang -v ? $ clang -v echo EOF Debian clang version 3.4.2-4 (tags/RELEASE_34/dot2-final) (based on LLVM 3.4.2) Target: i386-pc-linux-gnu Thread model: posix Selected GCC installation: EOF Sorry, I meant the command that you previously run: clang -v test.c Perhaps it's because gcc-4.9 uses i586-linux-gnu as triplet (unlike previous versions, which use i486-linux-gnu)? Maybe :) Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752617: Reopening
On Wed, Jul 16, 2014 at 2:40 PM, Ondřej Surý ond...@sury.org wrote: Please don't do anything harsh now, just leave the bugs open for now. Duly noted, thanks. -- ,''`. : :' : Cyril Bouthors `. `' Debian.org `-
Bug#707268: Bug#725957: [NMU] Bug#740085: package plplot 5.10.0
Hi Axel, Le 17/07/2014 13:09, Axel Beckert a écrit : Hi Thibaut, Thibaut Paumard wrote: I'd rather sponsor a package you would have prepared, but failing that How did you fail that? I reviewed his package at https://mentors.debian.net/package/plplot Thanks for pointing this out. I missed it because - plplot does not appear on the front-page of mentors, - there is no bug againsts the sponsorship-request pseudo package, - and no mention of this upload in this bug report (740085). I figured that was enough places to look for an information that should have been directed to me directly, who explicitly offered help and asked whether there was a plan. [...] I'm though likely not able to sponsor the (fixed or workarounded) package the next few days as I'm currently travelling. So feel free to sponsor it, if you have time. I'd be happy about it. I can forward you my findings this evening, if preferred. I should have some spare time next week. I'll be glad to read your findings, and we can keep each other informed on whether we get to it. Kind regards, Thibaut. I'd take care of the next GDL upload then in a few days. Regards, Axel signature.asc Description: OpenPGP digital signature
Bug#754963: clang-3.4: /usr/bin/ld: cannot find crtbegin.o: No such file or directory
$ clang -v test.c Debian clang version 3.4.2-4 (tags/RELEASE_34/dot2-final) (based on LLVM 3.4.2) Target: i386-pc-linux-gnu Thread model: posix Selected GCC installation: /usr/lib/llvm-3.4/bin/clang -cc1 -triple i386-pc-linux-gnu -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -main-file-name test.c -mrelocation-model static -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -target-cpu pentium4 -target-linker-version 2.24.51.20140617 -v -resource-dir /usr/lib/llvm-3.4/bin/../lib/clang/3.4.2 -internal-isystem /usr/include/clang/3.4.2/include/ -internal-isystem /usr/local/include -internal-isystem /usr/lib/llvm-3.4/bin/../lib/clang/3.4.2/include -internal-externc-isystem /usr/include/i386-linux-gnu -internal-externc-isystem /include -internal-externc-isystem /usr/include -fdebug-compilation-dir /home/jwilk -ferror-limit 19 -fmessage-length 180 -mstackrealign -fobjc-runtime=gcc -fdiagnostics-show-option -vectorize-slp -o /tmp/test-734030.o -x c test.c clang -cc1 version 3.4.2 based upon LLVM 3.4.2 default target i386-pc-linux-gnu ignoring nonexistent directory /usr/local/include ignoring nonexistent directory /include ignoring duplicate directory /usr/include/clang/3.4.2/include #include ... search starts here: #include ... search starts here: /usr/include/clang/3.4.2/include /usr/include/i386-linux-gnu /usr/include End of search list. /usr/bin/ld --hash-style=both --build-id --eh-frame-hdr -m elf_i386 -dynamic-linker /lib/ld-linux.so.2 -o a.out /usr/lib/i386-linux-gnu/crt1.o /usr/lib/i386-linux-gnu/crti.o crtbegin.o -L/lib/i386-linux-gnu -L/usr/lib/i386-linux-gnu -L/lib -L/usr/lib /tmp/test-734030.o -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed crtend.o /usr/lib/i386-linux-gnu/crtn.o /usr/bin/ld: cannot find crtbegin.o: No such file or directory /usr/bin/ld: cannot find -lgcc /usr/bin/ld: cannot find -lgcc_s clang: error: linker command failed with exit code 1 (use -v to see invocation) -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755067: xserver-xorg-core upgrade wants to remove virtualbox-guest-x11 due to incompatible ABI version
Package: virtualbox-guest-x11 Version: 4.3.12-dfsg-1 Severity: serious I'm running Debian Testing in Virtualbox. With the recent updates, virtualbox-guest-x11 is removed if you upgrade xserver-xorg-core to version 2:1.15.99.904-1, because virtualbox-guest-x11 needs xorg-video-abi-15 - but xserver-xorg-core now provides xorg-video-abi-18. Please upgrade or rebuild the Guest Additions to reflect these ABI changes.
Bug#753144: net-snmp: FTBFS on kfreebsd-amd64 - 'struct kinfo_proc' has no member named 'kp_eproc'
On Thu, Jul 17, 2014 at 01:45:38AM +0300, Niko Tyni wrote: make[2]: *** No rule to make target 'snmpinform.1', needed by 'maninstall'. Stop. Ah, that's probably just because I used 'git clean -dfx' between test builds. The upstream .gitignore has man/*.[1358] but there's no rule to remake man/snmpinform.1. Oh well. I guess I shouldn't hack so late. CC'ing the debian-bsd list. Maybe somebody can pick this up and/or at least eyeball the patch. In case someone ends up doing an NMU, please include the patch in #751918 too. I'd appreciate if somebody more knowledgeable could check the patch. Due to the large number of reverse dependencies, net-snmp is one of the more important packages for the upcoming Perl 5.20 transition, which makes this FTBFS bug a transition blocker. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754604: marked as done (plasma-nm: not binNMU-safe)
Your message dated Thu, 17 Jul 2014 13:19:02 +
with message-id e1x7laq-0004u2...@franck.debian.org
and subject line Bug#754604: fixed in plasma-nm 0.9.3.3-4
has caused the Debian Bug report #754604,
regarding plasma-nm: not binNMU-safe
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.)
--
754604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: plasma-nm
Version: 0.9.3.3-3
Severity: serious
plasma-nm has:
Replaces: knm-runtime, plasma-widget-networkmanagement ( ${binary:Version})
Breaks: knm-runtime, plasma-widget-networkmanagement ( ${binary:Version})
The version here is wrong. First because
plasma-widget-networkmanagement is arch:all so its version is the
plasma-nm version when binNMUed (as right now in sid). And second
because as plasma-widget-networkmanagement is a transitional package the
version in Breaks/Replaces should be the first version where plasma-nm
replaced it, not the current version, so it should be fixed, not a
substvar.
Cheers,
Julien
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: plasma-nm
Source-Version: 0.9.3.3-4
We believe that the bug you reported is fixed in the latest version of
plasma-nm, 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 754...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Maximiliano Curia m...@debian.org (supplier of updated plasma-nm 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, 17 Jul 2014 13:33:49 +0200
Source: plasma-nm
Binary: plasma-nm plasma-widget-networkmanagement plasma-nm-dbg
plasma-widget-networkmanagement-dbg
Architecture: source amd64 all
Version: 0.9.3.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian.org
Changed-By: Maximiliano Curia m...@debian.org
Description:
plasma-nm - Network Management widget for KDE Plasma workspaces
plasma-nm-dbg - debugging symbols for KDE Network Management widget
plasma-widget-networkmanagement - Transitional package for plasma-nm
plasma-widget-networkmanagement-dbg - Transitional package for plasma-nm-dbg
Closes: 753279 754604 754979
Changes:
plasma-nm (0.9.3.3-4) unstable; urgency=medium
.
* Update Homepage field. (Closes: #753279)
* Fix wrong replaces breaks versions. (Closes: #754604, #754979)
* New patch: disable_teamwidget
Checksums-Sha1:
72dd0e6c9ed5f0ae09345eab35ba36ded80b1fa2 2655 plasma-nm_0.9.3.3-4.dsc
3d9b0c872a5dc879e829f25291e1867d064eb059 7252 plasma-nm_0.9.3.3-4.debian.tar.xz
7b34e93ec99c4f240ab9d52810218ebf9a8660b8 737520 plasma-nm_0.9.3.3-4_amd64.deb
a042d106a04da23b85f17e22f1122a38736a5f3c 4576
plasma-widget-networkmanagement_0.9.3.3-4_all.deb
02bf254b6c2a41237b4349b30fef0675a4a4b0a8 10284458
plasma-nm-dbg_0.9.3.3-4_amd64.deb
14bdc6b94a8e92349405f64659d9a05b2a92199b 3794
plasma-widget-networkmanagement-dbg_0.9.3.3-4_all.deb
Checksums-Sha256:
d0066c919f05455293fb356a5a29d94648316f9ad666bd5836997d6d3bc3908f 2655
plasma-nm_0.9.3.3-4.dsc
daf17fa5b4a7b9c25e2c3c6e52b8b0c0cdbe3df47640ed4cc703674401b02130 7252
plasma-nm_0.9.3.3-4.debian.tar.xz
b7d7fe0be650ba3716a2a32088172497ec0e8c33f4d472664053755d0c08bf48 737520
plasma-nm_0.9.3.3-4_amd64.deb
88925e1071c7caa6455f775bfd8e39d881ecbbdaa590dbd5a3d942ed33006973 4576
plasma-widget-networkmanagement_0.9.3.3-4_all.deb
66abf330c4cf5b08691a7f688b9b97fd8e8864e30f23dff5aabdd9b3fbf52719 10284458
plasma-nm-dbg_0.9.3.3-4_amd64.deb
2a55716d4752fb9e3e9b67c97d96093dd346da0a01926d7fb84ad40fcc6ae217 3794
plasma-widget-networkmanagement-dbg_0.9.3.3-4_all.deb
Files:
deff627dcb7ff4b81efa67247bd3a480 737520 kde optional
plasma-nm_0.9.3.3-4_amd64.deb
0963559f7e4828492f5410daa350abcc 4576 oldlibs extra
plasma-widget-networkmanagement_0.9.3.3-4_all.deb
0ff18cf8a10fb51230304fd7f01b951d 10284458 debug extra
plasma-nm-dbg_0.9.3.3-4_amd64.deb
c29174bd852c7291007e8dc3bec5bf11 3794 oldlibs extra
plasma-widget-networkmanagement-dbg_0.9.3.3-4_all.deb
8b6aeb587a5e1acfebef5e2f47271554 2655 kde optional plasma-nm_0.9.3.3-4.dsc
Bug#755062: systemd: Syslog (contents that journalctl shows) stopped working after upgrading from 204-14 to 208-6
severity 755062 important tags 755062 + moreinfo unreproducible thanks Am 17.07.2014 13:00, schrieb Axel Beckert: Package: systemd Version: 208-6 Severity: grave Justification: causes data loss Hi, I upgraded from 204-14 to 208-6 last night and today in the morning, I noticed that journalctl doesn't show any entries from after the upgrade. Neither the at that time running journalctl -f nor a freshly called journalctl show anything new. Just calling journalctl, it shows all messages from boot up to when the upgrade happened. There is no syslog daemon like e.g. rsyslog installed. I have not yet rebooted, but I do expect that syslog must work after upgrading systemd without having rebooted. Otherwise it would be a severe data loss. And even if that would be the case: Either the running jpurnalctl -f from 204 or the just called journalctl from 208 should show something in this case. I just tested various upgrades from 204-14 (with and without persistent journal, VM and real hardware) and was not able to reproduce the problem. Also considering, that we still install rsyslog by default, I'm going to lower the severity to important. -- 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#755062: systemd: Syslog (contents that journalctl shows) stopped working after upgrading from 204-14 to 208-6
Processing commands for cont...@bugs.debian.org: severity 755062 important Bug #755062 [systemd] systemd: Syslog (contents that journalctl shows) stopped working after upgrading from 204-14 to 208-6 Severity set to 'important' from 'grave' tags 755062 + moreinfo unreproducible Bug #755062 [systemd] systemd: Syslog (contents that journalctl shows) stopped working after upgrading from 204-14 to 208-6 Added tag(s) unreproducible and moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 755062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#754984: libpam-systemd 208-6 conflicts with sysvinit-core
Processing commands for cont...@bugs.debian.org:
reopen 754984
Bug #754984 {Done: Michael Biebl bi...@debian.org} [libpam-systemd]
libpam-systemd 208-6 conflicts with sysvinit-core
Bug reopened
Ignoring request to alter fixed versions of bug #754984 to the same values
previously set
severity 754984 critical
Bug #754984 [libpam-systemd] libpam-systemd 208-6 conflicts with sysvinit-core
Severity set to 'critical' from 'normal'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
754984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754984
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#752939: Bug#754984: libpam-systemd 208-6 conflicts with sysvinit-core
reopen 754984 severity 754984 critical thanks * Michael Biebl bi...@debian.org [2014-07-16 17:20 +0200]: severity 754984 normal thanks Am 16.07.2014 17:00, schrieb Ben Caradoc-Davies: Package: libpam-systemd Version: 204-14 Severity: critical Justification: breaks the whole system Dear Maintainer, libpam-systemd 204-14 lived in peaceful coexistence with sysvinit-core by depending on systemd-sysv | systemd-shim. libpam-systemd 208-6 amd64 now depends on systemd-sysv alone, and thus conflicts with sysvinit-core. This change is intentional and caused by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939 I don't see the intention? Steve [0] confirmed that systemd-shim can coexist with sysvinit-core. I've build an alternate dependency on sysvinit-core for libpam-systemd and didn't recognized any missbehavior yet. So bug reopend as critical. Elimar [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939#24 -- The path to source is always uphill! -unknown- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718134: freetalk: FTBFS: manuals build fails against textinfo5 because some incompatibles changes wrt 4.13 and below (some warnings have turned into errors)
I noticed the 4.0rc5 released. Maybe we should consider package this version. On Thu, Jul 10, 2014 at 10:02 AM, YunQiang Su s...@debian.org wrote: Any progress of this bug? Forgot to upload? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754984: libpam-systemd 208-6 conflicts with sysvinit-core
Am 17.07.2014 16:20, schrieb Elimar Riesebieter: reopen 754984 severity 754984 critical thanks * Michael Biebl bi...@debian.org [2014-07-16 17:20 +0200]: severity 754984 normal thanks Am 16.07.2014 17:00, schrieb Ben Caradoc-Davies: Package: libpam-systemd Version: 204-14 Severity: critical Justification: breaks the whole system Dear Maintainer, libpam-systemd 204-14 lived in peaceful coexistence with sysvinit-core by depending on systemd-sysv | systemd-shim. libpam-systemd 208-6 amd64 now depends on systemd-sysv alone, and thus conflicts with sysvinit-core. This change is intentional and caused by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939 I don't see the intention? You should read the changelog then. Not understanding the intentions is not a justification for reopening a bug report which has been closed by its maintainer. I pointed you to the relevant bug report against systemd-shim and there is also [1]. Besides, the bug title is misleading: libpam-systemd is not conflicting with sysvinit-core. The combination sysvinit-core+systemd-shim simply doesn't provide the necessary environment anymore to run logind standalone, that's why systemd-shim was dropped as alternative dependency from libpam-systemd. Once systemd-shim fixed, the alternative depends in libpam-systemd can be re-added. I've been talking to Serge, who is already working on systemd-shim. Anyway, reassigned this bug report to systemd-shim. [1] http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=2d0f5c2d7609291733f893065f1acdf8f8796bc4 -- 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: reassign 754984 to systemd-shim, forcibly merging 752939 754984
Processing commands for cont...@bugs.debian.org: reassign 754984 systemd-shim Bug #754984 [libpam-systemd] libpam-systemd 208-6 conflicts with sysvinit-core Bug reassigned from package 'libpam-systemd' to 'systemd-shim'. No longer marked as found in versions systemd/204-14. Ignoring request to alter fixed versions of bug #754984 to the same values previously set forcemerge 752939 754984 Bug #752939 [systemd-shim] Needs to be updated for the single cgroup manager changes in systemd v205 Bug #754984 [systemd-shim] libpam-systemd 208-6 conflicts with sysvinit-core Severity set to 'grave' from 'critical' Marked as found in versions systemd-shim/6-3. Added tag(s) confirmed. Merged 752939 754984 thanks Stopping processing here. Please contact me if you need assistance. -- 752939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939 754984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754984 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#755038: marked as done (drupal7: SA-CORE-2014-003 - Drupal core - Multiple vulnerabilities)
Your message dated Thu, 17 Jul 2014 15:49:38 + with message-id e1x7nwa-0003ec...@franck.debian.org and subject line Bug#755038: fixed in drupal7 7.29-1 has caused the Debian Bug report #755038, regarding drupal7: SA-CORE-2014-003 - Drupal core - Multiple vulnerabilities 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.) -- 755038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: drupal7 Severity: grave Tags: security upstream fixed-upstream Hi See [1] for details, multiple vulnerabilities were fixed in drupal7 7.29 (there are no CVEs assigned yet). [1] https://www.drupal.org/SA-CORE-2014-003 Regards, Salvatore ---End Message--- ---BeginMessage--- Source: drupal7 Source-Version: 7.29-1 We believe that the bug you reported is fixed in the latest version of drupal7, 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. Gunnar Wolf gw...@debian.org (supplier of updated drupal7 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, 17 Jul 2014 07:42:19 -0500 Source: drupal7 Binary: drupal7 Architecture: source all Version: 7.29-1 Distribution: unstable Urgency: high Maintainer: Luigi Gangitano lu...@debian.org Changed-By: Gunnar Wolf gw...@debian.org Description: drupal7- fully-featured content management framework Closes: 750666 755038 Changes: drupal7 (7.29-1) unstable; urgency=high . * New upstream release * Fixes SA-CORE-2014-003 (Denial of service; access bypass; 2×cross- site scripting) (Closes: #755038) * Setting urgency as high due to the security issues this release closes. * Add a build-dependency on yui-compressor and actually build the minified JS files excluded from the package. (Closes: #750666) * Added lintian overrides for shipped sources, specific JS version Checksums-Sha1: 2935e62cd62c164a90b579e924c223fb9373de8d 1871 drupal7_7.29-1.dsc 8d48563f9af4cb414c352256cb97accb2764d7c5 3204971 drupal7_7.29.orig.tar.gz 990d43b5dcf5249471ac9003e32dda91ce2a93d4 173328 drupal7_7.29-1.debian.tar.xz 32f2ef2277e4836ce9db22b775bf738d372a923c 2473042 drupal7_7.29-1_all.deb Checksums-Sha256: a224c11d7325e6c5bc902fa11b564a5f10f56729bf4f9bc985e5c857c99f4da4 1871 drupal7_7.29-1.dsc 631ab9864e48cf467dc7b2ca4c300d53e3f73b7f86757be517e7ab89f09d3884 3204971 drupal7_7.29.orig.tar.gz e5d31fcd0d334e854d41176a69ba3cd6b017e5d6c7c8fae54bcc566178bcecd1 173328 drupal7_7.29-1.debian.tar.xz 4a950e65c39ffa4afaadf936120fcd9e44aecbc74459060a00f243aef4d5b278 2473042 drupal7_7.29-1_all.deb Files: 7b40d755a3176b597780377407888096 2473042 web extra drupal7_7.29-1_all.deb 89927ab37b23f7974f828c19f08e4302 1871 web extra drupal7_7.29-1.dsc 4d2fce09cef015e42a198b1517ec6554 3204971 web extra drupal7_7.29.orig.tar.gz 8a1a25a3977af5794adfda7758404d04 173328 web extra drupal7_7.29-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTx+F2AAoJEGc6A+TB25IfXC4P/A987wg+de0hh4HwM38xBQRw 16B0DPqFYwK/Iek8cQNo4c3lDvuk6ddghEGBoZhply7KCjKMeGMj74e7uDQzyHTi b0782fv3enqQpdfImCp3/eYTm8Rn5Bzd4t03B0ExINAixitZyYFlJe0DCANyXmyR HAD5QJ96ImDj4Ncs80G39JwyvlsmxCGsJZl6UJCxUsVF+DWHf5EjmI37njD8oPGt zFrl1PAcDljdt0xEA/QDXqgoc5paI+h9rhZmm/bR3JmUFvZEk1OkDp1SW/2yDDzU 29O7NWUJ9JYjGUhVh+pc922GJ3GZUMyCAXtqgTwYAYQcyJ35K63EjcpUZ1ctMaAC FYgfBjPZaSrqUKDBkugA2YlLe7LPw2/sTRU1aIJXnTxclxk9/zltzbybbcBtjzDB kZEdQcH2KnTlwT4+NoIDlAmg9d/dtnepIhVLJC+oiWfTPm9fj0H85O5nvNJRP8rL YKkYv2lsOgJrRaj3yFI3FLNuX1IJSuL6KBGZUZotkLSzorv/oNHj3qca1Q4Fj/vt dzC8y5TlS/qDjuErUud2pOtL7Whga7eXI0Qcb9B5UlPNFfaiC3pGkrmwdODtZ4bu kNosjS2xb4uJ3PD0IohIzh8O5dTdISDFMbjrAJmBd1iykpRxam7JuPGCSjBUGK5O Cb4XzNYmmfS2sWAkLhwn =JBlV -END PGP SIGNATUREEnd Message---
Bug#755057: marked as done (Empty /usr/share/php5/php.ini-production in package php5-common on jessie/sid)
Your message dated Thu, 17 Jul 2014 15:56:27 + with message-id e1x7o2l-0004vm...@franck.debian.org and subject line Bug#755057: fixed in php5 5.6.0~rc2+dfsg-4 has caused the Debian Bug report #755057, regarding Empty /usr/share/php5/php.ini-production in package php5-common on jessie/sid 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.) -- 755057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: php5-common Version: 5.6.0~rc2+dfsg-3 $ ls -l /usr/share/php5/php.ini-production -rw-r--r-- 1 root root 0 Jul 11 12:38 /usr/share/php5/php.ini-production This may also cause /var/lib/dpkg/info/libapache2-mod-php5.postinst to fail: Setting up libapache2-mod-php5 (5.6.0~rc2+dfsg-3) ... usage: fail($reason, $retval) at /usr/sbin/a2query line 168. usage: fail($reason, $retval) at /usr/sbin/a2query line 168. usage: fail($reason, $retval) at /usr/sbin/a2query line 168. /var/lib/dpkg/info/libapache2-mod-php5.postinst: 284: [: !=: unexpected operator ---End Message--- ---BeginMessage--- Source: php5 Source-Version: 5.6.0~rc2+dfsg-4 We believe that the bug you reported is fixed in the latest version of php5, 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. Ondřej Surý ond...@debian.org (supplier of updated php5 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, 17 Jul 2014 12:46:05 +0200 Source: php5 Binary: php5 php5-common libapache2-mod-php5 libapache2-mod-php5filter php5-cgi php5-cli php5-phpdbg php5-fpm libphp5-embed php5-dev php5-dbg php-pear php5-curl php5-enchant php5-gd php5-gmp php5-imap php5-interbase php5-intl php5-ldap php5-mcrypt php5-readline php5-mysql php5-mysqlnd php5-odbc php5-pgsql php5-pspell php5-recode php5-snmp php5-sqlite php5-sybase php5-tidy php5-xmlrpc php5-xsl Architecture: source all amd64 Version: 5.6.0~rc2+dfsg-4 Distribution: unstable Urgency: high Maintainer: Debian PHP Maintainers pkg-php-ma...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: libapache2-mod-php5 - server-side, HTML-embedded scripting language (Apache 2 module) libapache2-mod-php5filter - server-side, HTML-embedded scripting language (apache 2 filter mo libphp5-embed - HTML-embedded scripting language (Embedded SAPI library) php-pear - PEAR - PHP Extension and Application Repository php5 - server-side, HTML-embedded scripting language (metapackage) php5-cgi - server-side, HTML-embedded scripting language (CGI binary) php5-cli - command-line interpreter for the php5 scripting language php5-common - Common files for packages built from the php5 source php5-curl - CURL module for php5 php5-dbg - Debug symbols for PHP5 php5-dev - Files for PHP5 module development php5-enchant - Enchant module for php5 php5-fpm - server-side, HTML-embedded scripting language (FPM-CGI binary) php5-gd- GD module for php5 php5-gmp - GMP module for php5 php5-imap - IMAP module for php5 php5-interbase - interbase/firebird module for php5 php5-intl - internationalisation module for php5 php5-ldap - LDAP module for php5 php5-mcrypt - MCrypt module for php5 php5-mysql - MySQL module for php5 php5-mysqlnd - MySQL module for php5 (Native Driver) php5-odbc - ODBC module for php5 php5-pgsql - PostgreSQL module for php5 php5-phpdbg - server-side, HTML-embedded scripting language (PHPDBG binary) php5-pspell - pspell module for php5 php5-readline - Readline module for php5 php5-recode - recode module for php5 php5-snmp - SNMP module for php5 php5-sqlite - SQLite module for php5 php5-sybase - Sybase / MS SQL Server module for php5 php5-tidy - tidy module for php5 php5-xmlrpc - XML-RPC module for php5 php5-xsl - XSL module for php5 Closes: 714041 754775 755057 Changes: php5 (5.6.0~rc2+dfsg-4) unstable; urgency=medium . [ Ondřej Surý ] * Fix invalid reportbug script directory in the php5 package (Closes: #754775) * Fix missing backslash that made php.ini-production empty (Closes: #755057) . [ Andreas Schwab ]
Bug#754984: libpam-systemd 208-6 conflicts with sysvinit-core
unmerge 754984 reassign 754984 libpam-systemd found 754984 208-4 retitle libpam-systemd: re-add alternative dependency on systemd-shim block 754984 by 752939 severity 754984 normal thanks Am 17.07.2014 17:25, schrieb Michael Biebl: Besides, the bug title is misleading: libpam-systemd is not conflicting with sysvinit-core. The combination sysvinit-core+systemd-shim simply doesn't provide the necessary environment anymore to run logind standalone, that's why systemd-shim was dropped as alternative dependency from libpam-systemd. Once systemd-shim fixed, the alternative depends in libpam-systemd can be re-added. I've been talking to Serge, who is already working on systemd-shim. Anyway, reassigned this bug report to systemd-shim. Let's do something actually useful with this bug report and use it as a tracker bug with the proper title and severity. Michael -- 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 (with 1 errors): Re: Bug#754984: libpam-systemd 208-6 conflicts with sysvinit-core
Processing commands for cont...@bugs.debian.org: unmerge 754984 Bug #754984 [systemd-shim] libpam-systemd 208-6 conflicts with sysvinit-core Bug #752939 [systemd-shim] Needs to be updated for the single cgroup manager changes in systemd v205 Disconnected #754984 from all other report(s). reassign 754984 libpam-systemd Bug #754984 [systemd-shim] libpam-systemd 208-6 conflicts with sysvinit-core Bug reassigned from package 'systemd-shim' to 'libpam-systemd'. No longer marked as found in versions systemd-shim/6-3. Ignoring request to alter fixed versions of bug #754984 to the same values previously set found 754984 208-4 Bug #754984 [libpam-systemd] libpam-systemd 208-6 conflicts with sysvinit-core Marked as found in versions systemd/208-4. retitle libpam-systemd: re-add alternative dependency on systemd-shim Unknown command or malformed arguments to command. block 754984 by 752939 Bug #754984 [libpam-systemd] libpam-systemd 208-6 conflicts with sysvinit-core 754984 was not blocked by any bugs. 754984 was not blocking any bugs. Added blocking bug(s) of 754984: 752939 severity 754984 normal Bug #754984 [libpam-systemd] libpam-systemd 208-6 conflicts with sysvinit-core Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 752939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939 754984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754984 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#753748: marked as done (Mail to maintainer address bounces)
Your message dated Thu, 17 Jul 2014 15:55:22 + with message-id e1x7o1i-00048s...@franck.debian.org and subject line Bug#753748: fixed in percona-xtradb-cluster-5.5 5.5.37-25.10+dfsg-2 has caused the Debian Bug report #753748, regarding Mail to maintainer address bounces to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 753748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: percona-xtradb-cluster-server-5.5 Severity: serious Justification: policy 3.3 - Forwarded message from ubuntu-devel-discuss-boun...@lists.ubuntu.com - Date: Fri, 04 Jul 2014 15:21:48 + From: ubuntu-devel-discuss-boun...@lists.ubuntu.com To: andr...@fatal.se Subject: Your message to Ubuntu-devel-discuss awaits moderator approval Your mail to 'Ubuntu-devel-discuss' with the subject Bug#753743: percona-xtradb-cluster-server-5.5: please depend on iproute2 instead of iproute transitional package Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: [---censored-url---] - End forwarded message - ---End Message--- ---BeginMessage--- Source: percona-xtradb-cluster-5.5 Source-Version: 5.5.37-25.10+dfsg-2 We believe that the bug you reported is fixed in the latest version of percona-xtradb-cluster-5.5, 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 753...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James Page james.p...@ubuntu.com (supplier of updated percona-xtradb-cluster-5.5 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, 17 Jul 2014 12:21:18 +0100 Source: percona-xtradb-cluster-5.5 Binary: percona-xtradb-cluster-common-5.5 percona-xtradb-cluster-client-5.5 percona-xtradb-cluster-client percona-xtradb-cluster-server-5.5 percona-xtradb-cluster-server Architecture: source all amd64 Version: 5.5.37-25.10+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org Changed-By: James Page james.p...@ubuntu.com Description: percona-xtradb-cluster-client - Percona XtraDB Cluster database client percona-xtradb-cluster-client-5.5 - Percona Server database client binaries percona-xtradb-cluster-common-5.5 - Percona Server database common files percona-xtradb-cluster-server - Percona XtraDB Cluster database server percona-xtradb-cluster-server-5.5 - Percona Server database server binaries Closes: 748812 748884 749792 750073 750769 751573 753743 753748 754489 Changes: percona-xtradb-cluster-5.5 (5.5.37-25.10+dfsg-2) unstable; urgency=medium . [ Américo Monteiro ] * Portuguese translation for debconf messages (Closes: #748812). . [ Christian Perrier ] * French translation for debconf messages (Closes: #748884). . [ Victory ] * Japanese translation for debconf messages (Closes: #750769). . [ Helge Kreutzmann ] * German translation for debconf messages (Closes: #751573). . [ James Page ] * d/control: Update Maintainer to pkg-mysql-maint (Closes: #750073, #753748). * d/control: Use iproute2 instead of iproute transitional package (Closes: #753743). * d/control: Disable percona-xtradb-cluster-testsuite* packages as they are non-functional with wsrep and Galera (Closes: #749792). . [ Plamen Alexandrov ] * d/p/mips-ftbfs.patch: Resolve FTBFS on mips architecture (Closes: #754489). Checksums-Sha1: f48dddac04e6063997fca95539ae7a6871262a3d 2864 percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-2.dsc 255788cfe143e5fec291d17387d838025b197bf4 37228 percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-2.debian.tar.xz 30aa765361d0d0c6798f3fbc036de8d5aee6207a 10800 percona-xtradb-cluster-common-5.5_5.5.37-25.10+dfsg-2_all.deb dd6b8fba3ca902d1da0cc300acb9849007cd18d8 1408046 percona-xtradb-cluster-client-5.5_5.5.37-25.10+dfsg-2_amd64.deb
Bug#752762: load-module module-alsa-sink freezes display
Control: severity -1 important I'm downgrading the severity seems this seems to (a) not happen to other people, and (b) looks like it could be a bug in some client rather than pulse. -- Saludos, Felipe Sateler -- 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#752762: load-module module-alsa-sink freezes display
Processing control commands: severity -1 important Bug #752762 [pulseaudio] load-module module-alsa-sink freezes display Severity set to 'important' from 'grave' -- 752762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752762 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#754608: marked as done (git-annex: FTBFS on most buildds: git-annex: runInteractiveProcess: pipe: Too many open files)
Your message dated Thu, 17 Jul 2014 16:21:08 + with message-id e1x7oqe-0007zq...@franck.debian.org and subject line Bug#754608: fixed in git-annex 5.20140717 has caused the Debian Bug report #754608, regarding git-annex: FTBFS on most buildds: git-annex: runInteractiveProcess: pipe: Too many open files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 754608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: git-annex Version: 5.20140709 Severity: serious Justification: FTBFS Hi, your package no longer builds, apparently because of exhausted resources during the test suite: | git-annex: runInteractiveProcess: pipe: Too many open files | preferred content: FAIL | set group to standard failed | git-annex: runInteractiveProcess: pipe: Too many open files | git-annex: runInteractiveProcess: pipe: Too many open files | git-annex: git: createProcess: resource exhausted (Too many open files) | add subdirs:FAIL | git annex init failed | | 2 out of 132 tests failed | (This could be due to a bug in git-annex, or an incompatability |with utilities, such as git, installed on this system.) | make[1]: *** [test] Error 1 Full build logs linked from: https://buildd.debian.org/status/package.php?p=git-annexsuite=sid Direct build log for i386: https://buildd.debian.org/status/fetch.php?pkg=git-annexarch=i386ver=5.20140709stamp=1404943224 Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: git-annex Source-Version: 5.20140717 We believe that the bug you reported is fixed in the latest version of git-annex, 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 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joey Hess jo...@debian.org (supplier of updated git-annex 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, 17 Jul 2014 11:27:25 -0400 Source: git-annex Binary: git-annex Architecture: source amd64 Version: 5.20140717 Distribution: unstable Urgency: high Maintainer: Joey Hess jo...@debian.org Changed-By: Joey Hess jo...@debian.org Description: git-annex - manage files with git, without checking their contents into git Closes: 754608 Changes: git-annex (5.20140717) unstable; urgency=high . * Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). Checksums-Sha1: 94b7b22fbd338d9eb36b5ffc0e5d76e483433935 3869 git-annex_5.20140717.dsc 5102d38ce36c73b1b6078219ed4a6395dcd83691 5593605 git-annex_5.20140717.tar.gz e5ac80a6f386243ca95b0a28e768245771aeaa63 8312378 git-annex_5.20140717_amd64.deb Checksums-Sha256:
Bug#735994: Bug#736035: Bug#735994: upgrading to serious: libtiff4-dev is being removed
so when is this transition to use libtiff-dev to happen? cmtk just was removed from jessie for no good reason (I have not spotted that severity still was serious), so I wondered if I should just wait a bit and upload updated package or start whining process to bring current cmtk back into jessie (since currently technically there is nothing wrong with it!) On Tue, 01 Jul 2014, Yaroslav Halchenko wrote: On Tue, 01 Jul 2014, Yaroslav Halchenko wrote: No, it's not fine. Buildds only consider the first alternative, so if libtiff4-dev no longer exists, the package won't be able to build on the buildds. and with your argument reopening those just closed issues ;) but for now with normal severity since FTBFS is not factual yet (libtiff4-dev is still there). I will swap the order of those in build-depends -- pbuilder iirc is a bit smarter, so hopefully there would be no issues in building those backports we care about in neurodebian bleh -- but I just can't because then they will FTBFS now since there is no libtiff-dev yet in the archive... so I will just let the time get ripe I guess and do nothing meanwhile -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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#751059: pycurl: FTBFS - conflicting (transitive) build dependencies
Processing control commands: retitle -1 pycurl: FTBFS - missing b-d on libgnutls28-dev Bug #751059 [pycurl] pycurl: FTBFS - conflicting (transitive) build dependencies Changed Bug title to 'pycurl: FTBFS - missing b-d on libgnutls28-dev' from 'pycurl: FTBFS - conflicting (transitive) build dependencies' -- 751059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751059 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#751059: pycurl: FTBFS - conflicting (transitive) build dependencies
Control: retitle -1 pycurl: FTBFS - missing b-d on libgnutls28-dev On 2014-06-21 Andreas Metzler ametz...@bebt.de wrote: On 2014-06-09 Michael Tautschnig m...@debian.org wrote: Package: pycurl [...} The following packages have unmet dependencies: librtmp-dev : Depends: libgnutls-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. E: Could not satisfy build-dependency. A further investigation suggests that the problem is - librtmp-dev --depends-- libgnutls-dev --depends-- libgcrypt11-dev - libssh2-1-dev --depends-- libgcrypt20-dev --conflicts-- libgcrypt11-dev [...] Hello, Looking at the last successful buildlog the b-d on librtmp-dev seems to be superfluous, the only match on rtmp there is the installation of the b-ds. I got a successful (assuming the test suite does its job) build with the attached patch. Status update: librtmp-dev has dropped its unnecessary dependency on libgnutls-dev, which is why the pycurl build now fails with i486-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -DPYCURL_VERSION=7.19.3.1 -DHAVE_CURL_GNUTLS=1 -DHAVE_CURL_GNUTLS=1 -DHAVE_CURL_SSL=1 -I/usr/include/python2.7 -c src/pycurl.c -o build/temp.linux-x86_64-2.7/src/pycurl.o src/pycurl.c:113:30: fatal error: gnutls/gnutls.h: No such file or directory # include gnutls/gnutls.h Patch posted previously still works. 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
Processed: severity of 720535 is grave
Processing commands for cont...@bugs.debian.org: # fails to start sounds like a grave bug severity 720535 grave Bug #720535 [gdevilspie] gdevilspie can't start Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 720535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720535 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#735994: Bug#736035: Bug#735994: upgrading to serious: libtiff4-dev is being removed
Yaroslav Halchenko y...@debian.org wrote: so when is this transition to use libtiff-dev to happen? cmtk just was removed from jessie for no good reason (I have not spotted that severity still was serious), so I wondered if I should just wait a bit and upload updated package or start whining process to bring current cmtk back into jessie (since currently technically there is nothing wrong with it!) I'm sorry this is causing a problem for you. Hopefully my comments below will help a little. It is definitely not my intention to create a headache for anyone, but I would point out that this has been in the works for a long time. I'm not sure I really see the problem with just uploading a new version to sid with a build dependency on libtiff-dev. This may work fine for backported versions since libtiff4-dev provided libtiff-dev for a long time (years), but if it doesn't, the backporting mechanism supports having different build dependencies for backporting. Yes, it creates a small headache for the backporter, but it's something that is pretty routine. I don't know anything about neurodebian, but it seems to me that it must support the ability to have different build dependencies or other differences in config for backported packages. The tiff transition has been in the works for something like two years. I believe debian was the first major distribution to start and the last one to finish making the switch. I don't want to keep a transitional package around, and removing it has always been part of the plan. I'm sorry that this is causing a hassle for you. I tried to organize this to minimize hassle and to provide loads of time for developers to make the switch. Let me know if I can be of any assistance in some way other than reintroducing libtiff4-dev. -- Jay Berkenbilt q...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755093: FTBFS on kfreebsd, s390x and sparc
Source: cjs Version: 2.2.1-2 Severity: serious Your package failed to build on kfreebsd, s390x and sparc. Although it hasn't built on those architectures in the past (and thus this bug shouldn't be RC), this is a cinnamon package and src:cinnamon is available on s390x and now requires cjs, making it unbuildable and thus out of date on that architecture. There are two options here: - Fix the cjs FTBFS - Request the removal of cinnamon on s390x. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735994: Bug#736035: Bug#735994: upgrading to serious: libtiff4-dev is being removed
On Thu, 17 Jul 2014, Jay Berkenbilt wrote: so when is this transition to use libtiff-dev to happen? cmtk just was removed from jessie for no good reason (I have not spotted that severity still was serious), so I wondered if I should just wait a bit and upload updated package or start whining process to bring current cmtk back into jessie (since currently technically there is nothing wrong with it!) I'm sorry this is causing a problem for you. Hopefully my comments below will help a little. It is definitely not my intention to create a headache for anyone, but I would point out that this has been in the works for a long time. I'm not sure I really see the problem with just uploading a new version to sid with a build dependency on libtiff-dev. This may work fine for backported versions since libtiff4-dev provided libtiff-dev for a long time (years), but if it doesn't, the backporting mechanism supports having different build dependencies for backporting. IIRC either it is in the policy or just in a mentality of buildds that first listed package must be non-virtual. Yes, it creates a small headache for the backporter, but it's something that is pretty routine. I don't know anything about neurodebian, but it seems to me that it must support the ability to have different build dependencies or other differences in config for backported packages. yeah -- there we should not have any problem, thanks for checking ;) The tiff transition has been in the works for something like two years. I believe debian was the first major distribution to start and the last one to finish making the switch. I don't want to keep a transitional package around, and removing it has always been part of the plan. I'm sorry that this is causing a hassle for you. I tried to organize this to minimize hassle and to provide loads of time for developers to make the switch. Let me know if I can be of any assistance in some way other than reintroducing libtiff4-dev. doh -- blind/silly/busy? me, there is already a libtiff5-dev and what I need is actually to adjust build-depends to bdepend on it -- I took it wrong and assumed that the entire transition is about introducing libtiff-dev physical package... ok, so I will just go ahead and adjust build-depends to be libtiff5-dev | libtiff4-dev | libtiff-dev, and that should resolve it ;) Cheers! -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735994: Bug#736035: Bug#735994: upgrading to serious: libtiff4-dev is being removed
On Thu, 17 Jul 2014, Yaroslav Halchenko wrote: Let me know if I can be of any assistance in some way other than reintroducing libtiff4-dev. doh -- blind/silly/busy? me, there is already a libtiff5-dev and what I need is actually to adjust build-depends to bdepend on it -- I took it wrong and assumed that the entire transition is about introducing libtiff-dev physical package... ok, so I will just go ahead and adjust build-depends to be libtiff5-dev | libtiff4-dev | libtiff-dev, and that should resolve it ;) double silly me -- I see no statement in the policy that first one must be non-virtual, also ants package I maintain just build-depends on libtiff-dev and buildds were as happy... so I guess I just had a bad dream. Sorry about all the noise -- I will fix it all up shortly -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754879: built on i386
Version: 4.9.1-1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755099: libjudydebian1: broken on amd64
Package: libjudydebian1
Version: 1.0.5-1.1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
gcc-4.8.3+ miscompile libjudy on AMD64. Workarounds:
* use -fno-aggressive-loop-optimizations
* compile witn gcc-4.7
* compile with clang :-)
Judy's quite obscure; I've not seen any obvious bug, but it's a challenge to
compilers... And -fno-aggressive-loop-optimizations works around the bug so
I hesitate to fill a PR on https://gcc.gnu.org/bugzilla/.
Oh yes, GCC upstream doesn't work either (tested w/pristine 4.8.3 and 4.9.1).
Here's a testcase:
--
// testj1.cc
#include cstdint
#include stdexcept
#include Judy.h
using namespace std;
namespace {
uint64_t Items[] =
{
39895168241613, 72383693324832, 395899889036069, 847472082254022,
946081064318053, 1037167590154045,
1633874457044695, 169355155793, 1699866756097333,
2297933432179674, 2340748542246111, 2490696201066604,
2928757784612027, 3419613478295142, 3477583438964521,
3487665594607298, 3714788097418699, 3721974488148864,
3758589574777127, 4156020789217938, 4459711081140573,
4682530741276476, 4731624807195863, 4846840683894723,
4857387254864689, 4873346723597917, 4966839149608974,
5631406002858271, 5722255428668219, 5820718729024077,
6209639118315956, 6406299749329887, 6454295835737737,
6503048444249319, 6520786252857121, 6906836761168795,
6926132865086029, 6954533820994232
};
}
int
main(int /*argc*/, char const * /*argv*/[])
{
intRc_int;// boolean values returned (0 or 1)
Pvoid_t PJ1Array = nullptr; // initialize Judy1 array
for (auto item: Items) {
// set item
J1S(Rc_int, PJ1Array, item);
// get last (with value = ii)
auto ii = item;
J1L(Rc_int, PJ1Array, ii);
if (ii != item)
throw runtime_error(J1L: ii != item);
}
return 0;
}
--
This program inserts increasing int64_t's into a Judy1 array. After each insert,
it checks whether the last item is what was just added.
$ g++ -O3 -g -W -Wall -pipe -std=c++11 testj1.cc -o testj1 -lJudy
Expected result:
$ ./testj1
$
Actual result:
$ ./testj1
terminate called after throwing an instance of 'std::runtime_error'
what(): J1L: ii != item
Aborted (core dumped)
$
Thanks!
Yves
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-3-generic (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages libjudydebian1 depends on:
ii libc6 2.19-7
libjudydebian1 recommends no packages.
libjudydebian1 suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735994: Bug#736035: Bug#735994: upgrading to serious: libtiff4-dev is being removed
Yaroslav Halchenko y...@debian.org wrote: double silly me -- I see no statement in the policy that first one must be non-virtual, also ants package I maintain just build-depends on libtiff-dev and buildds were as happy... so I guess I just had a bad dream. Sorry about all the noise -- I will fix it all up shortly Yup, just replacing the build dependency with libtiff-dev was the original suggestion and what almost everyone did with their packages. We all have bad dreams sometimes. :-) -- Jay Berkenbilt q...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753144: net-snmp: FTBFS on kfreebsd-amd64
I'd appreciate if somebody more knowledgeable could check the patch. Due to the large number of reverse dependencies, net-snmp is one of the more important packages for the upcoming Perl 5.20 transition, which makes this FTBFS bug a transition blocker. The patch seems be fine. Or kfreebsd.h with content: ** #include freebsd10.h #include osreldate.h #include sys/queue.h #include sys/_types.h *** Cheers Petr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754879: marked as done (FTBFS on i386)
Your message dated Thu, 17 Jul 2014 21:04:36 +0200 with message-id 53c81e44.5010...@ubuntu.com and subject line built on i386 has caused the Debian Bug report #754879, regarding FTBFS on i386 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.) -- 754879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gcc-4.9 Version: 4.9.0-11 Severity: serious The package FTBFS on i386 and hurd-i386 but successfully built in the past. Complete build log at [1] [1] https://buildd.debian.org/status/package.php?p=gcc-4.9suite=unstable -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information ---End Message--- ---BeginMessage--- Version: 4.9.1-1---End Message---
Bug#754709: marked as done (mednafen: no longer buildable on powerpc/s390x/sparc: libtrio-dev missing)
Your message dated Thu, 17 Jul 2014 19:18:36 + with message-id e1x7rco-0001sa...@franck.debian.org and subject line Bug#754709: fixed in mednafen 0.9.36.2-2 has caused the Debian Bug report #754709, regarding mednafen: no longer buildable on powerpc/s390x/sparc: libtrio-dev missing 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.) -- 754709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mednafen Version: 0.9.36.2-1 Severity: serious Justification: FTBFS Hi, your package can no longer be built on powerpc/s390x/sparc, presumably since the following bug was resolved: 1) #746817 Should build against and link with system's libtrio [RESOLVED] given that libtrio is still uncompiled on those three archs: https://buildd.debian.org/status/package.php?p=libtriosuite=sid This means you have out-of-date binaries and your package can't migrate to testing. Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: mednafen Source-Version: 0.9.36.2-2 We believe that the bug you reported is fixed in the latest version of mednafen, 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 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt sk...@debian.org (supplier of updated mednafen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jul 2014 21:00:53 +0200 Source: mednafen Binary: mednafen Architecture: source amd64 Version: 0.9.36.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Stephen Kitt sk...@debian.org Description: mednafen - multi-platform emulator, including NES, GB/A, Lynx, PC Engine Closes: 754709 Changes: mednafen (0.9.36.2-2) unstable; urgency=medium . * libvorbisidec and libtrio are priority extra, so mednafen must be priority extra. * Build-depend on libtrio-dev 1.16 or later since that's the first version to build on all architectures (closes: #754709). * Enable parallel builds. * Move trio source out of the way during the build, as done for mpcdec and tremor. Checksums-Sha1: 02bf4f7bbae9ec8c54be49c7d24586682fdaa633 2239 mednafen_0.9.36.2-2.dsc 36543e16bde231ba9d1690c14e7e2c75a3668508 13036 mednafen_0.9.36.2-2.debian.tar.xz d58d9ec4d48e8a0f61d442582a31c014be2ee84f 2467124 mednafen_0.9.36.2-2_amd64.deb Checksums-Sha256: 85d3656a521801a5542c251d3f33b49a016d222b778b68aa910768847fad4bc0 2239 mednafen_0.9.36.2-2.dsc 8d892be7e87a14130671a9239ba9aeff1d21f3e14ba13d6dbc95ccf278908c41 13036 mednafen_0.9.36.2-2.debian.tar.xz 6507afe1dd5319acac83789abf3b832131c3c64b00e91c106fb2b1fbc0c6c4fb 2467124 mednafen_0.9.36.2-2_amd64.deb Files: 7ac840100c33b2c85d7ee3e7217aa35f 2467124 games extra mednafen_0.9.36.2-2_amd64.deb b76b0eb4ea8ea8ca7a4286db96c7b504 2239 games extra mednafen_0.9.36.2-2.dsc 1973884dfdb9aa88f391e26bf5ce5d9f 13036 games extra mednafen_0.9.36.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTyB8IAAoJEHWXeKmja0lPAIEP/Ag+uvPfkIr0P84fygQzL1m2 b/l1R73N57eb++If136DMM9KEfjaDxV57AsrRDPyeUnRw/3/0PEgSbmz+yZZPgfR 2R9jKnSHKsxRsoQkY6I0/3O7JYSmOwTxTCYNdfzFOcLRl4qbOr2QU/wDyjLs3hDB zVqQEHv5ly5W76XgwGFHaL6Mdo4UCQ9Zl/jbPJ/q6ZlM5cQl0jbzmUP1EJ4kfka0 ZGrQCPt3MjvE/GdBqf0UhD7VNza/whsMaZFhjiH/cr5RNJ165TBKOQ1MUDKE0VEi hf9vBMujnQeNWAgjZTNEy7pvG9j89cKSBeNb+eenoiufWRYVjCLGmjM9lNUTs6Xq h4iT7yqF0PGyQDl5k/om0qg/b5i2UuK9FEbdvnKPGDeJPPi07//2MsI4O1Te0X/l yr71x8QnD/q4jmw2rKNHu85RsR/G2PfR6pRwXt7xCil2IxG1WjZu1YzLgoV+N5iw opv8M0KBqzwRqwxEoB6x5XgCwe+PzBa152r+WBNaiY0A5F6fx6e26jnEKSOONX9I 58oxX3NnrdCfqppmaPzhaZwSYmQc4G3EVRb4wvTHugu9W4UgWG/8FOrYd/fK8NBy bbcRP0YjZ6xSXtUwTUi6Gl+2Uh4w6bhOncsF+moGHQ0IWY+tLulWGHmMceNuRWEa TCh5P5yxU+B/hJYo6hrp =z/4h -END PGP SIGNATUREEnd Message---
Bug#754669: fixed in sash 3.8-2
Hello Tollef. Tollef Fog Heen tfh...@debian.org (2014-07-16): Format: 1.8 Date: Wed, 16 Jul 2014 20:48:59 +0200 Source: sash Binary: sash Architecture: source amd64 Version: 3.8-2 Distribution: unstable Urgency: medium Maintainer: Tollef Fog Heen tfh...@debian.org Changed-By: Tollef Fog Heen tfh...@debian.org Description: sash - Stand-alone shell Closes: 754669 Changes: sash (3.8-2) unstable; urgency=medium . * Use #if instead of #ifdef for HAVE_LINUX_* in sash.c to make this build on kfreebsd. Closes: #754669 It now fails with a missing include: | cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -DHAVE_GZIP=1 -DHAVE_LINUX_ATTR=0 -DHAVE_LINUX_CHROOT=0 -DHAVE_LINUX_LOSETUP=0 -DHAVE_LINUX_PIVOT=0 -DHAVE_LINUX_MOUNT=0 -DHAVE_BSD_MOUNT=1 -DMOUNT_TYPE='ufs' -c cmds.c | cmds.c:35:24: fatal error: linux/loop.h: No such file or directory | #include linux/loop.h | ^ | compilation terminated. Do you want a reopen or a new bug report? Build logs: https://buildd.debian.org/status/fetch.php?pkg=sasharch=kfreebsd-amd64ver=3.8-2stamp=1405539467 https://buildd.debian.org/status/fetch.php?pkg=sasharch=kfreebsd-i386ver=3.8-2stamp=1405539311 Mraw, KiBi. signature.asc Description: Digital signature
Bug#755102: libexpect-php5: please update build-depends, expect-dev is gone
Source: libexpect-php5 Version: 0.3.1-1 Severity: serious Justification: FTBFS Hi, expect-dev was dropped in the last expect upload: | Changes: | expect (5.45-6) unstable; urgency=low | . |* Split the expect package into expect and tcl-expect where the libexpect | library and the Tcl package are moved. Made the tcl-expect package | multiarch same. |* Renamed the expect-dev package into tcl-expect-dev and moved the included | scripts into the main expect package. |* Build expect with Tcl 8.6. |* Use CFLAGS from the dpkg build flags. Fixed potential security bug in | printf format handling. |* Bumped the debhelper compatibility version to 9. |* Bumped standards version to 3.9.5. so your package's build-deps need an update. Sergei (in cc): that package needs an update before the old binary can be removed, and so that your package can be a candidate for migration to testing. In the meanwhile, it's not because it has out-of-date binaries. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755104: faketime: BD-Uninstallable on !linux: libc6 (= 2.17)
Source: faketime Version: 0.9.6-2 Severity: serious Justification: FTBFS Hi, alpha and ia64 are gone, but libc fun remains with hurd (libc0.3) and kfreebsd (libc0.1), so a build-dep on “libc6 (= 2.17)” doesn't work there and your package is stuck in the BD-Uninstallable state: | faketime build-depends on missing: | - libc6 (= 2.17) Full summary: https://buildd.debian.org/status/package.php?p=faketimesuite=sid Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753144: net-snmp: FTBFS on kfreebsd-amd64
tag 75314 patch thanks On Thu, Jul 17, 2014 at 08:58:30PM +0200, Petr Salinger wrote: I'd appreciate if somebody more knowledgeable could check the patch. Due to the large number of reverse dependencies, net-snmp is one of the more important packages for the upcoming Perl 5.20 transition, which makes this FTBFS bug a transition blocker. The patch seems be fine. Thanks! Tagging accordingly. Not sure how soon I can prepare an NMU. I'd be happy if somebody else picked that up and fixed #751918 in the same go. (Even better if it's the maintainer, of course :) -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755105: kadu: no longer builds on kfreebsd-*
Source: kadu Version: 1.0~rc2.5-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on kfreebsd-*: | -- * Kadu is now successfully installed * | -- ** | -- | -- Thanks for choosing Kadu Communicator and ENJOY!!! | -- | -- Kadu Team | -- | make[1]: Leaving directory '/«PKGBUILDDIR»/build-dir' | cp /«PKGBUILDDIR»/debian/tmp/usr/share/kadu/ChangeLog debian/kadu/usr/share/doc/kadu/about-changes-tab.txt | rm -f /«PKGBUILDDIR»/debian/tmp/usr/share/kadu/modules/data/osd_hints/License | dh_install -s | cp: cannot stat 'debian/tmp/debian/tmp/usr/lib/kadu/plugins/libantistring.so': No such file or directory | dh_install: cp -a debian/tmp/debian/tmp/usr/lib/kadu/plugins/libantistring.so debian/kadu//usr/lib/kadu/plugins/ returned exit code 1 | make: *** [install-arch] Error 2 | debian/rules:73: recipe for target 'install-arch' failed Full build logs: https://buildd.debian.org/status/fetch.php?pkg=kaduarch=kfreebsd-amd64ver=1.0~rc2.5-1stamp=1405456260 https://buildd.debian.org/status/fetch.php?pkg=kaduarch=kfreebsd-i386ver=1.0~rc2.5-1stamp=1405459537 I suspect this might be a failure to enable shared libraries because of platform misdetection. Please get in touch with debian-bsd@ if you need help. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 753144
Processing commands for cont...@bugs.debian.org: # whoops tags 753144 + patch Bug #753144 [src:net-snmp] net-snmp: FTBFS on kfreebsd-amd64 - 'struct kinfo_proc' has no member named 'kp_eproc' Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 753144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753144 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#755102: libexpect-php5: please update build-depends, expect-dev is gone
Hi Cyril, On Thu, Jul 17, 2014 at 11:30 PM, Cyril Brulebois k...@debian.org wrote: Sergei (in cc): that package needs an update before the old binary can be removed, and so that your package can be a candidate for migration to testing. In the meanwhile, it's not because it has out-of-date binaries. I understand that, thank you for the clarification. Though libexpect-php5 has another two RC bugs, one of which was reported more than 2 years ago (see [1]). I can fix #755102 in NMU, but would this fix be reasonable given that I'm not going to fix #667767 and #752628 (especially the latter). [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667767 Cheers! -- Sergei Golovan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755102: libexpect-php5: please update build-depends, expect-dev is gone
Sergei Golovan sgolo...@nes.ru (2014-07-17): Hi Cyril, On Thu, Jul 17, 2014 at 11:30 PM, Cyril Brulebois k...@debian.org wrote: Sergei (in cc): that package needs an update before the old binary can be removed, and so that your package can be a candidate for migration to testing. In the meanwhile, it's not because it has out-of-date binaries. I understand that, thank you for the clarification. Though libexpect-php5 has another two RC bugs, one of which was reported more than 2 years ago (see [1]). I can fix #755102 in NMU, but would this fix be reasonable given that I'm not going to fix #667767 and #752628 (especially the latter). [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667767 Yeah, I saw that while filing the bug report. Another easy way out if breaking that package, which is a decision I'll leave to the release guy going to request the decruft on the FTP side. :) I just thought documenting the build-dep issue explicitly was a good idea. Mraw, KiBi. signature.asc Description: Digital signature
Bug#718068: csh: FTBFS: Makefile:24: *** missing separator. Stop.
On Thu, 17 Jul 2014 18:42:27 +0800, YunQiang Su wrote: I am consider NMU it. Any objection? No need to ask for explicit permission to perform an NMU, ie. to help others :) In other words: please go ahead, and thanks in advance. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Billie Holiday: Please Don't Talk About Me When I'm Gone signature.asc Description: Digital Signature
Processed: reassign 752199 to php-sabre-event
Processing commands for cont...@bugs.debian.org: # Reassigning to the end of the dependency chain reassign 752199 php-sabre-event Bug #752199 [php-sabre-event php-sabre-http] Useless in Jessie Bug reassigned from package 'php-sabre-event php-sabre-http' to 'php-sabre-event'. Ignoring request to alter found versions of bug #752199 to the same values previously set Ignoring request to alter fixed versions of bug #752199 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 752199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 754033
Processing commands for cont...@bugs.debian.org: tags 754033 + pending Bug #754033 [src:at-spi2-core] at-spi2-core: stray shlibs file makes udebs useless Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 754033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754033 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#754602: libnb-platform18-java: build-depends on virtual package java7-jdk
Control: severity -1 normal Control: retitle -1 libnb-platform18-java: build-depends on virtual package java7-jdk After some more investigation it looks like that it is not possible to build the package with git-buildpackage. The import with git-import-dsc works but something goes wrong when I try to build libnb-platform18-java with gbp. However when I simply use cowbuilder building the package succeeds thus I am using this bug report to report another bug. Having a build-dependency on a virtual package, java7-jdk, when the package already depends on default-jdk appears to be superfluous and also wrong. I believe this should be fixed. Markus signature.asc Description: OpenPGP digital signature
Processed: libnb-platform18-java: build-depends on virtual package java7-jdk
Processing control commands: severity -1 normal Bug #754602 [src:libnb-platform18-java] libnb-platform18-java: FTBFS due to unmet build-dependencies Severity set to 'normal' from 'serious' retitle -1 libnb-platform18-java: build-depends on virtual package java7-jdk Bug #754602 [src:libnb-platform18-java] libnb-platform18-java: FTBFS due to unmet build-dependencies Changed Bug title to 'libnb-platform18-java: build-depends on virtual package java7-jdk' from 'libnb-platform18-java: FTBFS due to unmet build-dependencies' -- 754602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754602 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#755116: [nvidia-xconfig] impossible execute startx
Package: nvidia-xconfig Version: 331.67-1 Severity: critical --- Please enter the report below this line. --- Description file attached. I have the same problem on two different computers with the following nvidia card: (this one refers to log file attached) Command 502 of 3 #nvidia-xconfig --query-gpu-info Number of GPUs: 1 GPU #0: Name : GeForce 8500 GT UUID : GPU-8b451ec2-ef7d-fe26-5c81-16ae92dfda2d PCI BusID : PCI:1:0:0 Number of Display Devices: 2 Display Device 0 (CRT-0): EDID Name : Ancor Communications Inc ASUS VH222 Minimum HorizSync : 30.000 kHz Maximum HorizSync : 85.000 kHz Minimum VertRefresh : 55 Hz Maximum VertRefresh : 75 Hz Maximum PixelClock: 160.000 MHz Maximum Width : 1920 pixels Maximum Height: 1080 pixels Preferred Width : 1920 pixels Preferred Height : 1080 pixels Preferred VertRefresh : 60 Hz Physical Width: 470 mm Physical Height : 260 mm Display Device 1 (CRT-1): EDID Name : Ancor Communications Inc ASUS VH222 Minimum HorizSync : 30.000 kHz Maximum HorizSync : 85.000 kHz Minimum VertRefresh : 55 Hz Maximum VertRefresh : 75 Hz Maximum PixelClock: 160.000 MHz Maximum Width : 1920 pixels Maximum Height: 1080 pixels Preferred Width : 1920 pixels Preferred Height : 1080 pixels Preferred VertRefresh : 60 Hz Physical Width: 470 mm Physical Height : 260 mm This on is of the other computer GPU #0: Name : GeForce GT 520 UUID : GPU-dc95c099-9b26-3273-d3b0-2e66bee1522a PCI BusID : PCI:1:0:0 Number of Display Devices: 2 Display Device 0 (CRT-1): EDID Name : Samsung SyncMaster Minimum HorizSync : 30.000 kHz Maximum HorizSync : 81.000 kHz Minimum VertRefresh : 56 Hz Maximum VertRefresh : 75 Hz Maximum PixelClock: 140.000 MHz Maximum Width : 1280 pixels Maximum Height: 1024 pixels Preferred Width : 1280 pixels Preferred Height : 1024 pixels Preferred VertRefresh : 60 Hz Physical Width: 380 mm Physical Height : 300 mm Display Device 1 (DFP-0): EDID Name : Ancor Communications Inc VE247 Minimum HorizSync : 30.000 kHz Maximum HorizSync : 83.000 kHz Minimum VertRefresh : 50 Hz Maximum VertRefresh : 76 Hz Maximum PixelClock: 170.000 MHz Maximum Width : 1920 pixels Maximum Height: 1080 pixels Preferred Width : 1920 pixels Preferred Height : 1080 pixels Preferred VertRefresh : 60 Hz Physical Width: 530 mm Physical Height : 300 mm Please contact me. I am glad to help you. thanks Marco Righi --- System information. --- Architecture: amd64 Kernel: Linux 3.14-1-amd64 Debian Release: jessie/sid 500 testing-updates ftp.it.debian.org 500 testing www.deb-multimedia.org 500 testing security.debian.org 500 testing ftp.it.debian.org 500 testing apt.jenslody.de 500 stable repo.wuala.com 500 stable apt.spideroak.com 500 sid linux.dropbox.com 500 debian packages.linuxmint.com 100 jessie-backports ftp.it.debian.org --- Package information. --- Depends (Version) | Installed =-+-=== pkg-config| 0.28-1 x11-common| 1:7.7+7 libc6 (= 2.14) | Recommends (Version) | Installed -+-=== libgl1-nvidia-glx-any| Package's Suggests field is empty. -- Think Marco, think different web site:http://www.di.unipi.it/~righi/ [ 468.851] X.Org X Server 1.15.99.904 (1.16.0 RC 4) Release Date: 2014-07-07 [ 468.852] X Protocol Version 11, Revision 0 [ 468.852] Build Operating System: Linux 3.14-1-amd64 x86_64 Debian [ 468.852] Current Operating System: Linux gaia 3.14-1-amd64 #1 SMP Debian 3.14.12-1 (2014-07-11) x86_64 [ 468.852] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14-1-amd64 root=UUID=f096ca70-1dd2-4529-a345-b348b0aae9cf ro quiet [ 468.852] Build Date: 08 July 2014 01:26:43PM [ 468.852] xorg-server 2:1.15.99.904-1 (http://www.debian.org/support) [ 468.852] Current version of pixman: 0.32.4 [ 468.853] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 468.853] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 468.853] (==) Log file: /var/log/Xorg.0.log, Time: Thu Jul 17 23:24:47 2014 [ 468.854] (==) Using config file:
Bug#754033: marked as done (at-spi2-core: stray shlibs file makes udebs useless)
Your message dated Thu, 17 Jul 2014 21:34:17 + with message-id e1x7tjh-hz...@franck.debian.org and subject line Bug#754033: fixed in at-spi2-core 2.12.0-2 has caused the Debian Bug report #754033, regarding at-spi2-core: stray shlibs file makes udebs useless 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.) -- 754033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: at-spi2-core Version: 2.10.2-3 Severity: serious Tags: d-i patch Justification: broken udebs [ -boot@ in X-D-Cc ] Hi maintainers, the following bugs should have been fixed thanks to various udeb additions: #723951, #723163. Unfortunately that isn't the case yet, because during the build the following instructions: | override_dh_makeshlibs: | dh_makeshlibs -a --add-udeb=libatspi0-udeb generate the following shlibs file: | $ cat debian/libatspi2.0-0/DEBIAN/shlibs | libatspi 0 libatspi2.0-0 | udeb: libatspi 0 libatspi0-udeb which looks like what we would like reverse dependencies to use to get a proper dependencies as far as udebs are concerned. But given there's still this file around, the generated shlibs file is later getting replaced by its contents, making all efforts moot: | $ cat debian/libatspi2.0-0.shlibs | libatspi 0 libatspi2.0-0 (= 2.9.90) (Note the missing udeb line.) I'm going to assume you might want to be keep the version around, you'll find attached a patch against master which implements that. Mraw, KiBi. From 01af06cd340cfd547f3f66f8b9af1cd8967c1132 Mon Sep 17 00:00:00 2001 From: Cyril Brulebois k...@debian.org Date: Sun, 6 Jul 2014 23:11:41 +0200 Subject: [PATCH] Fix generated shlibs file (broken for udebs). --- debian/changelog| 7 +++ debian/libatspi2.0-0.shlibs | 1 - debian/rules| 2 +- 3 files changed, 8 insertions(+), 2 deletions(-) delete mode 100644 debian/libatspi2.0-0.shlibs diff --git a/debian/changelog b/debian/changelog index 6445706..c8a4304 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,7 +1,14 @@ at-spi2-core (2.10.2-4) UNRELEASED; urgency=medium + [ Samuel Thibault ] * control: Fix typo in package description (Closes: Bug#745283) + [ Cyril Brulebois ] + * Fix generated shlibs file by removing stray, static copy +(debian/libatspi2.0-0.shlibs), and by moving the version to the +dh_makeshlibs call (-V flag). This will fix reverse-depending udeb +uninstallability as soon as at-spi2-atk is rebuilt. + -- Samuel Thibault sthiba...@debian.org Sun, 20 Apr 2014 10:38:29 +0200 at-spi2-core (2.10.2-3) unstable; urgency=low diff --git a/debian/libatspi2.0-0.shlibs b/debian/libatspi2.0-0.shlibs deleted file mode 100644 index 8035888..000 --- a/debian/libatspi2.0-0.shlibs +++ /dev/null @@ -1 +0,0 @@ -libatspi 0 libatspi2.0-0 (= 2.9.90) diff --git a/debian/rules b/debian/rules index 6b1afc7..de62d98 100755 --- a/debian/rules +++ b/debian/rules @@ -21,7 +21,7 @@ override_dh_auto_install: override_dh_auto_test: override_dh_makeshlibs: - dh_makeshlibs -a --add-udeb=libatspi0-udeb + dh_makeshlibs -a --add-udeb=libatspi0-udeb -V 'libatspi2.0-0 (= 2.9.90)' dh_girepository -pgir1.2-atspi-2.0 override_dh_strip: -- 2.0.1 ---End Message--- ---BeginMessage--- Source: at-spi2-core Source-Version: 2.12.0-2 We believe that the bug you reported is fixed in the latest version of at-spi2-core, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault sthiba...@debian.org (supplier of updated at-spi2-core package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jul 2014 22:29:27 +0200 Source: at-spi2-core Binary: at-spi2-core at-spi2-core-udeb at-spi2-core-dbg libatspi2.0-0 libatspi0-udeb libatspi2.0-dev libatspi2.0-0-dbg gir1.2-atspi-2.0 at-spi2-doc Architecture: source amd64 all Version: 2.12.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Accessibility Team debian-accessibil...@lists.debian.org Changed-By: Samuel Thibault sthiba...@debian.org Description: at-spi2-core - Assistive
Bug#752627: marked as done (zabbix: combines code released under GPL and GPL-incompatible licenses (PHP license))
Your message dated Thu, 17 Jul 2014 21:40:23 + with message-id e1x7tpb-0001zv...@franck.debian.org and subject line Bug#752627: fixed in zabbix 1:2.2.5+dfsg-1 has caused the Debian Bug report #752627, regarding zabbix: combines code released under GPL and GPL-incompatible licenses (PHP license) 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.) -- 752627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: zabbix Version: 1:2.2.3+dfsg-1 Severity: serious zabbix combines code released under the GPL with code released under the PHP license in src/libs/zbxsys/mutexs.c. (The PHP license is not included in the header, but somewhere below.) As the GPL and PHP license are incompatible[1], this makes the package not distributable. [1] https://www.gnu.org/licenses/license-list.html#PHP-3.01 Ansgar ---End Message--- ---BeginMessage--- Source: zabbix Source-Version: 1:2.2.5+dfsg-1 We believe that the bug you reported is fixed in the latest version of zabbix, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Smirnov only...@debian.org (supplier of updated zabbix package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 18 Jul 2014 03:16:47 +1000 Source: zabbix Binary: zabbix-agent zabbix-frontend-php zabbix-java-gateway zabbix-proxy-mysql zabbix-proxy-pgsql zabbix-proxy-sqlite3 zabbix-server-mysql zabbix-server-pgsql Architecture: source amd64 all Version: 1:2.2.5+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Christoph Haas h...@debian.org Changed-By: Dmitry Smirnov only...@debian.org Description: zabbix-agent - network monitoring solution - agent zabbix-frontend-php - network monitoring solution - PHP front-end zabbix-java-gateway - network monitoring solution - Java gateway zabbix-proxy-mysql - network monitoring solution - proxy (using MySQL) zabbix-proxy-pgsql - network monitoring solution - proxy (using PostgreSQL) zabbix-proxy-sqlite3 - network monitoring solution - proxy (using SQLite3) zabbix-server-mysql - network monitoring solution - server (using MySQL) zabbix-server-pgsql - network monitoring solution - server (using PostgreSQL) Closes: 744385 749707 751910 752627 754271 Changes: zabbix (1:2.2.5+dfsg-1) unstable; urgency=medium . * New upstream release [July 2014] (Closes: #754271). - fixed CVE-2014-3005: local file inclusion via XXE (Closes: #751910). - removed PHP-licensed code (Closes: #752627). - don't use deprecated function mbstring.internal_encoding (Closes: #749707). * zabbix-agent: Depends: +pciutils; Recommends: +usbutils (Closes: #744385). * Added debian/gbp.conf. * Build-Depends: + libgcrypt-dev -- libgcrypt20-dev | libgcrypt-dev. + pkg-config. * Replace source-less minified .js files on build-time; added source-is-missing lintian-overrides; updated debian/copyright. Checksums-Sha1: fb074adef42adfa6690c1f9129483957957ace6c 2752 zabbix_2.2.5+dfsg-1.dsc f35d5831563a51b8376a573e1729d44eeba1cd0e 5907528 zabbix_2.2.5+dfsg.orig.tar.xz c04d4ed2bc9165b73f8e043b3fd2fc59e6b010a9 187992 zabbix_2.2.5+dfsg-1.debian.tar.xz 552a538487ec461100642322f7b94cdecdd62524 315730 zabbix-agent_2.2.5+dfsg-1_amd64.deb 817abfc68610567b1a054b0246ca0d126b5b36d7 2909488 zabbix-frontend-php_2.2.5+dfsg-1_all.deb 1d5483ddc593ebe0db9fbcb4338b1924e75ba83b 182528 zabbix-java-gateway_2.2.5+dfsg-1_all.deb 07167f8f1902fe63680980ab81976d7cf9316ed3 555886 zabbix-proxy-mysql_2.2.5+dfsg-1_amd64.deb b153a4d2959855348027671ba176acecc31e3de3 559134 zabbix-proxy-pgsql_2.2.5+dfsg-1_amd64.deb 9a05a073f4f38b268bd847aba343bc3997e4fccf 542226 zabbix-proxy-sqlite3_2.2.5+dfsg-1_amd64.deb 91b9adc4c9b557681786e17863caffc17ec5188d 1732974 zabbix-server-mysql_2.2.5+dfsg-1_amd64.deb fdd42f71455248be99d4f02e7eb6c7e16676dc1c 1734762 zabbix-server-pgsql_2.2.5+dfsg-1_amd64.deb Checksums-Sha256: c3cc4bc4df0342601470b47496fa3a52fd2024bcdd5410098ed29bac9e41e25f 2752 zabbix_2.2.5+dfsg-1.dsc
Bug#751910: marked as done (zabbix: CVE-2014-3005: local file inclusion via XXE)
Your message dated Thu, 17 Jul 2014 21:40:23 +
with message-id e1x7tpb-0001zp...@franck.debian.org
and subject line Bug#751910: fixed in zabbix 1:2.2.5+dfsg-1
has caused the Debian Bug report #751910,
regarding zabbix: CVE-2014-3005: local file inclusion via XXE
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.)
--
751910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: zabbix
Version: 1:2.2.3+dfsg-1
Severity: grave
Tags: security
Advisory: http://seclists.org/fulldisclosure/2014/Jun/87
Below might be the fix, but please verify.
---
Henri Salo
svn diff -r46596:46600
Index: frontends/php/include/defines.inc.php
===
--- frontends/php/include/defines.inc.php (revision 46596)
+++ frontends/php/include/defines.inc.php (revision 46600)
@@ -835,6 +835,9 @@
define('ZBX_DEFAULT_IMPORT_HOST_GROUP', 'Imported hosts');
+// XML import flags
+define('LIBXML_IMPORT_FLAGS', LIBXML_NONET);
+
// API errors
define('ZBX_API_ERROR_INTERNAL', 111);
define('ZBX_API_ERROR_PARAMETERS', 100);
Index: frontends/php/include/classes/import/readers/CXmlImportReader.php
===
--- frontends/php/include/classes/import/readers/CXmlImportReader.php
(revision 46596)
+++ frontends/php/include/classes/import/readers/CXmlImportReader.php
(revision 46600)
@@ -32,7 +32,8 @@
*/
public function read($string) {
libxml_use_internal_errors(true);
- $result = simplexml_load_string($string);
+ libxml_disable_entity_loader(true);
+ $result = simplexml_load_string($string, null, LIBXML_IMPORT_FLAGS);
if (!$result) {
$errors = libxml_get_errors();
libxml_clear_errors();
Index: frontends/php/include/classes/import/CXmlImport18.php
===
--- frontends/php/include/classes/import/CXmlImport18.php (revision 46596)
+++ frontends/php/include/classes/import/CXmlImport18.php (revision 46600)
@@ -390,12 +390,13 @@
return $array;
}
- public static function import($file) {
+ public static function import($source) {
libxml_use_internal_errors(true);
+ libxml_disable_entity_loader(true);
$xml = new DOMDocument();
- if (!$xml-loadXML($file)) {
+ if (!$xml-loadXML($source, LIBXML_IMPORT_FLAGS)) {
$text = '';
foreach (libxml_get_errors() as $error) {
switch ($error-level) {
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: zabbix
Source-Version: 1:2.2.5+dfsg-1
We believe that the bug you reported is fixed in the latest version of
zabbix, 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 751...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Smirnov only...@debian.org (supplier of updated zabbix package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 18 Jul 2014 03:16:47 +1000
Source: zabbix
Binary: zabbix-agent zabbix-frontend-php zabbix-java-gateway zabbix-proxy-mysql
zabbix-proxy-pgsql zabbix-proxy-sqlite3 zabbix-server-mysql zabbix-server-pgsql
Architecture: source amd64 all
Version: 1:2.2.5+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Haas h...@debian.org
Changed-By: Dmitry Smirnov only...@debian.org
Description:
zabbix-agent - network monitoring solution - agent
zabbix-frontend-php - network monitoring solution - PHP front-end
zabbix-java-gateway - network monitoring solution - Java gateway
zabbix-proxy-mysql - network monitoring solution - proxy (using MySQL)
zabbix-proxy-pgsql - network monitoring solution - proxy (using PostgreSQL)
zabbix-proxy-sqlite3 - network monitoring solution - proxy (using SQLite3)
zabbix-server-mysql - network monitoring solution - server (using MySQL)
zabbix-server-pgsql - network monitoring solution - server (using PostgreSQL)
Closes: 744385 749707 751910 752627 754271
Changes:
zabbix (1:2.2.5+dfsg-1) unstable;
Processed: Re: Bug#750811: brltty: FTBFS on kfreebsd*
Processing control commands: severity -1 important Bug #750811 [brltty] brltty: FTBFS on kfreebsd* Severity set to 'important' from 'serious' -- 750811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750811 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#750811: brltty: FTBFS on kfreebsd*
Control: severity -1 important Hello, Matthias Klose, le Fri 11 Jul 2014 15:48:56 +0200, a écrit : Shouldn't the package for kfreebsd* have the files in a different sub-directory? linux just feels wrong on kfreebsd. I expect (but don't know for sure) that the resolver is smart enough to look in a sub-directory matching the os, but as I would expect not look in the directory named by a different os. you need to pass both -I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux Err, the latest gcj now happens to have jni_md.h next to jni.h, and thus brltty builds again... Samuel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755116: Acknowledgement ([nvidia-xconfig] impossible execute startx)
xorg.con attached Il 17/07/2014 23:33, Debian Bug Tracking System ha scritto: Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian NVIDIA Maintainers pkg-nvidia-de...@lists.alioth.debian.org If you wish to submit further information on this problem, please send it to 755...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- Think Marco, think different web site:http://www.di.unipi.it/~righi/ # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 331.67 (pbuilder@zam904) Tue Apr 22 12:31:11 UTC 2014 Section ServerLayout Identifier Layout0 Screen 0 Screen0 0 0 InputDeviceKeyboard0 CoreKeyboard InputDeviceMouse0 CorePointer EndSection Section Files EndSection Section InputDevice # generated from default Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/psaux Option Emulate3Buttons no Option ZAxisMapping 4 5 EndSection Section InputDevice # generated from default Identifier Keyboard0 Driver kbd EndSection Section Monitor Identifier Monitor0 VendorName Unknown ModelName Unknown HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option DPMS EndSection Section Device Identifier Device0 Driver nvidia VendorName NVIDIA Corporation EndSection Section Screen Identifier Screen0 Device Device0 MonitorMonitor0 DefaultDepth24 SubSection Display Depth 24 EndSubSection EndSection
Bug#752948: marked as done (swi-prolog: FTBFS - test_singleton.pl: Exported procedure is not defined)
Your message dated Fri, 18 Jul 2014 00:15:05 +0200 with message-id 20140717221505.GA2201@localhost.localdomain and subject line Re: Bug#752948: swi-prolog: FTBFS - test_singleton.pl: Exported procedure is not defined has caused the Debian Bug report #752948, regarding swi-prolog: FTBFS - test_singleton.pl: Exported procedure is not defined 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.) -- 752948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: swi-prolog Version: 6.6.6-1 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] Exported procedure memory_file:atom_to_memory_file/2 is not defined ERROR: /srv/jenkins-slave/workspace/sid-goto-cc-swi-prolog/swi-prolog-6.6.6/src/Tests/core/test_singleton.pl:10: Exported procedure memory_file:free_memory_file/1 is not defined ERROR: /srv/jenkins-slave/workspace/sid-goto-cc-swi-prolog/swi-prolog-6.6.6/src/Tests/core/test_singleton.pl:10: Exported procedure memory_file:memory_file_to_atom/2 is not defined ERROR: /srv/jenkins-slave/workspace/sid-goto-cc-swi-prolog/swi-prolog-6.6.6/src/Tests/core/test_singleton.pl:10: Exported procedure memory_file:open_memory_file/4 is not defined ERROR: /srv/jenkins-slave/workspace/sid-goto-cc-swi-prolog/swi-prolog-6.6.6/src/Tests/core/test_singleton.pl:10: Exported procedure memory_file:new_memory_file/1 is not defined Script /srv/jenkins-slave/workspace/sid-goto-cc-swi-prolog/swi-prolog-6.6.6/src/Tests/core/test_singleton.pl failed: test_singleton:copied_singletons/2: Undefined procedure: memory_file:new_memory_file/1 . done Running scripts from attvar .. done Running scripts from library done Running scripts from charset . done Running scripts from clp . done Running scripts from GC .. done Running scripts from thread done 22.875 seconds cpu time for 45,269,518 inferences 7,503 atoms, 4,919 functors, 5,805 predicates, 308 modules, 267,385 VM-codes LimitAllocated In use Local stack : 268,439,552 126,9761,488 Bytes Global stack : 268,443,648 126,960 144 Bytes Trail stack : 268,435,456 129,0168 Bytes 1,678 garbage collections gained 206,696,512 bytes in 2.071 seconds. 5,212 atom garbage collections gained 280,206 atoms in 6.930 seconds. Stack shifts: 742 local, 918 global, 443 trail in 0.151 seconds. 2 threads, 3,321 finished threads used 2.829 seconds. *** 1 tests failed *** Makefile:416: recipe for target 'check' failed make[2]: *** [check] Error 1 make[2]: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-swi-prolog/swi-prolog-6.6.6/src' debian/rules:125: recipe for target 'override_dh_auto_test' failed The full build log is attached; please do let me know if the problem is unreproducible, in which case I shall try to investigate further. Best, Michael swi-prolog-build-log.txt.gz Description: application/gunzip pgpgVJ1RuDrni.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Hi, This bug cannot be reproduced. I'm closing it now. Please reopen if you have more information. Regards, Eugeniy Meshcheryakov 28 червня 2014 о 01:05 +0100 Michael Tautschnig написав(-ла): Package: swi-prolog Version: 6.6.6-1 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] Exported procedure memory_file:atom_to_memory_file/2 is not defined ERROR: /srv/jenkins-slave/workspace/sid-goto-cc-swi-prolog/swi-prolog-6.6.6/src/Tests/core/test_singleton.pl:10: Exported procedure memory_file:free_memory_file/1 is not defined ERROR: /srv/jenkins-slave/workspace/sid-goto-cc-swi-prolog/swi-prolog-6.6.6/src/Tests/core/test_singleton.pl:10: Exported procedure memory_file:memory_file_to_atom/2 is not defined ERROR: /srv/jenkins-slave/workspace/sid-goto-cc-swi-prolog/swi-prolog-6.6.6/src/Tests/core/test_singleton.pl:10: Exported procedure memory_file:open_memory_file/4 is not defined ERROR:
Bug#755121: FTBFS: error: 'CLIENT' has not been declared
Source: xbmc Version: 2:13.1~rc1+dfsg1-1 Severity: serious Your package failed to build on all architectures. Excerpt from the logs: CPP xbmc/music/karaoke/karaokelyricsfactory.o In file included from NFSFile.cpp:35:0: /usr/include/nfsc/libnfs-raw-mount.h:150:38: error: 'CLIENT' has not been declared extern void * mount1_null_1(void *, CLIENT *); ^ See https://buildd.debian.org/status/logs.php?pkg=xbmcver=2%3A13.1~rc1%2Bdfsg1-1%2Bb1 Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755036: kxd: FTBFS: tests fail
On Wed, Jul 16, 2014 at 11:18:02PM -0400, Aaron M. Ucko wrote:
Source: kxd
Version: 0.12-1
Severity: serious
Justification: fails to build from source
Builds of kxd have been failing due to test suite errors. There are
two problems, each affecting multiple tests:
Thanks for opening this bug! I saw the failures this morning but I'm
only now at the computer.
* Many tests call os.getlogin, which has been throwing OSError, AFAICT
because stdin isn't a terminal:
Traceback (most recent call last):
File tests/run_tests, line 213, in setUp
self.server = ServerConfig()
File tests/run_tests, line 162, in __init__
self.gen_certs(self_sign)
File tests/run_tests, line 93, in gen_certs
self.name, os.getlogin(), platform.node())),
OSError: [Errno 25] Inappropriate ioctl for device
The patch at
https://blitiri.com.ar/git/r/kxd/c/2af6c0892cf34ca25e66cc7be328b75d6444970c/
should fix it.
It's in the next branch of the repository (git://blitiri.com.ar/kxd),
once you confirm this works, I'll move it to master and will include it
into the next release.
* In addition, test_{both,client,server}_delegated all fail with
Traceback (most recent call last):
File tests/run_tests, line 220, in tearDown
if self.daemon:
AttributeError: 'Delegation' object has no attribute 'daemon'
This one is just a consequence of the previous error.
Thanks again!
Alberto
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753764: marked as done (dmtcp: not installable in sid)
Your message dated Thu, 17 Jul 2014 23:03:31 + with message-id e1x7ui3-00058l...@franck.debian.org and subject line Bug#753764: fixed in dmtcp 2.3.1-1 has caused the Debian Bug report #753764, regarding dmtcp: not installable in sid 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.) -- 753764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dmtcp Version: 2.2-1 Severity: grave User: trei...@debian.org Usertags: edos-uninstallable Hello, dmtcp is not installable in sid on any architecture where it is available (amd64, i386). This is the case since at least 2014-04-05, possibly longer. The reason is that it depends on libmtcp1 which only exists in in an old version in wheezy. -Ralf. ---End Message--- ---BeginMessage--- Source: dmtcp Source-Version: 2.3.1-1 We believe that the bug you reported is fixed in the latest version of dmtcp, 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 753...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kapil Arya ka...@ccs.neu.edu (supplier of updated dmtcp 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: Mon, 14 Jul 2014 18:56:41 -0400 Source: dmtcp Binary: dmtcp dmtcp-dbg Architecture: source amd64 Version: 2.3.1-1 Distribution: unstable Urgency: low Maintainer: Kapil Arya ka...@ccs.neu.edu Changed-By: Kapil Arya ka...@ccs.neu.edu Description: dmtcp - Checkpoint/Restart functionality for Linux processes dmtcp-dbg - Debug package for dmtcp Closes: 662910 753764 Changes: dmtcp (2.3.1-1) unstable; urgency=low . * New upstream release 2.3.1 (closes: #662910). * Remove stale dependency on libmtcp1 (closes: #753764). * Upload sponsored by Yaroslav Halchenko deb...@onerussian.com Checksums-Sha1: 19ee7fc63c6fb3f69a167237cdc7e4e64fcf2631 1268 dmtcp_2.3.1-1.dsc 2ab286a7ff9a04e3e7017df33e712bc22bc52e5d 1318667 dmtcp_2.3.1.orig.tar.gz d1fe171dc9605d5d7228e2e643289792775374e1 6936 dmtcp_2.3.1-1.debian.tar.xz f8fd64f6df9a901ec08e9daaa3c783837cfad199 661414 dmtcp_2.3.1-1_amd64.deb 65f17eebc4fbb6f02acb16febcacce03780c4cd8 4359208 dmtcp-dbg_2.3.1-1_amd64.deb Checksums-Sha256: 2418f26f42029ad69f373586d7072cc4cc08d0aa55e1f33949da7cdd5fdecaaf 1268 dmtcp_2.3.1-1.dsc 1f83ae112e102d4fbf69dded0dfaa6daeb60c4c0c569297553785a876e95ba15 1318667 dmtcp_2.3.1.orig.tar.gz 86810fd0f9f7bd8e025ce04c9a48a8a59d2d581d1eae7062de4becad4bfabb1c 6936 dmtcp_2.3.1-1.debian.tar.xz d0f137b302b6a6f3dc3d42052f5996dd2ae43491f113e2ca8ac753f443dd3907 661414 dmtcp_2.3.1-1_amd64.deb b9b7d909fc3cf122a750b8d502c1807416eaa0bb01a674b83dc16e54f09592ef 4359208 dmtcp-dbg_2.3.1-1_amd64.deb Files: cfcb8fb8090a51aa68db52b5540fe9bc 661414 utils optional dmtcp_2.3.1-1_amd64.deb c9d6156d134518c7663f7d28fcfdbafc 4359208 debug extra dmtcp-dbg_2.3.1-1_amd64.deb edf9155d25bc72f9b39ba2730edc10e7 1268 utils optional dmtcp_2.3.1-1.dsc 129fad69c420630ffbc0870de9ba034e 1318667 utils optional dmtcp_2.3.1.orig.tar.gz b588b92b5178e92093832631f9e04c74 6936 utils optional dmtcp_2.3.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlPIU6sACgkQjRFFY3XAJMjlzQCdGudYlBMRged7COnCbyZlGEBO ZxEAoKulJh19QIxZelhxUN6/QP6yEfcd =uNox -END PGP SIGNATUREEnd Message---
Bug#755127: unnecessary conflict with libgcv5
Package: libgvc6 Version: 2.38.0-1 Severity: serious libgvc6 conflicts against libgvc5. Having different packages per ABI is also done to make them co-installable, which is kind of defeated by this conflict and makes library transitions unnecessary complex. There doesn't seem to be any file conflict, making this conflict arbitrary. -e System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752434: marked as done (wmbattery: upower-1.0 transition)
Your message dated Thu, 17 Jul 2014 23:34:31 + with message-id e1x7vc3-lc...@franck.debian.org and subject line Bug#748935: fixed in wmbattery 2.44 has caused the Debian Bug report #748935, regarding wmbattery: upower-1.0 transition to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 748935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wmbattery Version: 2.43 Severity: normal User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: upower-1.0 upower 0.99.0 (currently available in experimental) has dropped many deprecated APIs and some important functionality. Among them is the removal of suspend / hibernate support, which is now handled by systemd/logind [1], or the removal of the D-Bus notify_sleep/notify_resume signals. For a full list of changes please see [2]. In preparation for the upower 1.0 transition [3] I'm filing this bug because your package declares a relationship with upower (suggests/recommends/depends). Please check your package carefully, if it uses / requires some of that functionality and make sure it's still working with the new upower version. [1] http://www.freedesktop.org/wiki/Software/systemd/inhibit/ [2] http://lists.freedesktop.org/archives/devkit-devel/2013-October/001519.html [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751953 ---End Message--- ---BeginMessage--- Source: wmbattery Source-Version: 2.44 We believe that the bug you reported is fixed in the latest version of wmbattery, 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 748...@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 wmbattery package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 18 Jul 2014 01:14:49 +0200 Source: wmbattery Binary: wmbattery Architecture: source i386 Version: 2.44 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Andrew Shadura andre...@debian.org Description: wmbattery - display laptop battery info, dockable in WindowMaker Closes: 740885 748935 Changes: wmbattery (2.44) unstable; urgency=medium . * Better AC detection. * Support times with upower and acpi (Closes: #740885). * Use the latest upower API (Closes: #748935). * Fix upower detection. Checksums-Sha1: 182a309530ec21b2e1b3d9136c06e850eb93d4ee 1582 wmbattery_2.44.dsc 6a36e1c69dbbe4944145bfc51e279034dce14343 39278 wmbattery_2.44.tar.gz 78237cd5038eaa1158b9c32d2d5733cee6e2e064 23728 wmbattery_2.44_i386.deb Checksums-Sha256: f2451e55ba9e723e434a31a813e196b370e731dd3712e5909ed2e0aad9fa524d 1582 wmbattery_2.44.dsc aa0a1312922ba4f0abca5f2e8abbf285363bf4a1c8862d89fe2921e74c832cae 39278 wmbattery_2.44.tar.gz 3e0bf3e05cdaeb8dbef34e1ec43e0e3a6960eba0bc0431766dfcc57650c6f543 23728 wmbattery_2.44_i386.deb Files: ebe4f7ceaadc48fde1469f9d37667995 23728 x11 extra wmbattery_2.44_i386.deb 4214b59fab11dafaf75e5d6d49cc3831 1582 x11 extra wmbattery_2.44.dsc 9055cad65d1d9d00466c5f25b79cebbf 39278 x11 extra wmbattery_2.44.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iQIcBAEBCAAGBQJTyFu3AAoJEG6k0jEaLSaNGQQQAJzVnUaq6L2TsG3U1F2UmTGl pvFvFi2DASUYtM5TQ41RqFMFHODH2K9tqVPdrVwRp5UfuCIHqH4xbKQZCNJwaJ8c 3KZ6xQOK5uhAGfrMRg3taNSEYL0B6WM+DnCMMr/ZkBiGN5diiPoueJKc795ty9vI O7tMZmR69PTj8NRx5a0Zx6dDVoE2P9o5fr9B0BlVXJzGdpE5Eroe2N3l8TprDrsT 0P429IicBmNuQDpiXYyMPXVoLW+vwjCDHOp2gSz4T/coPpns+rvP++yFZrYHzT06 dFHppm82VHQDbfWt+SFl34OvN2Qr0YyWZq/BD4gAow8Tq/48MapN5rPhXXs+kVDy RoFyCcqNzA8TRIm9aLUk9XlP/8PqUpcIK009SmIDbKkEjayJ7nwrTn8LQzPoPBRx 0Y6j33TBN5Gt5F0X2CsxqVaZ2qsgAqJKdwIhjHF5AuDe9c4g+mgY1Dlmo38Fit+/ TgcQ2XX6AhD2+xyGMl27dHK/CpqGgircob1mCLnVWyHv9lWbL1TQYVFsg8dqxZIU oU1viMErhCwdt7Y2Se3st0nOTKmFpzIiI7jyOYgQAOUIuwhBEajG7zOVSnoGqu8s heinCoRH46yAQ7T3+nqVbpqWVNi7T9ZwNLtdRW4VFw/7ONfpgXD6UWFMUC+r8aUx 4hj5RehAEFzXJTxtGV9n =BMo/ -END PGP SIGNATUREEnd Message---
Bug#748935: marked as done (fails to build from source with upower 0.99)
Your message dated Thu, 17 Jul 2014 23:34:31 + with message-id e1x7vc3-lc...@franck.debian.org and subject line Bug#748935: fixed in wmbattery 2.44 has caused the Debian Bug report #748935, regarding fails to build from source with upower 0.99 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.) -- 748935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wmbattery Version: 2.42 User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: upower-1.0 We're preparing to transition the new upower release into unstable. The new version breaks the API/ABI and will in some cases require porting. Reverse dependencies has been build-tested and your package failed to build. Build log can be found at: http://people.debian.org/~biebl/upower-1.0/ For more information see: http://lists.freedesktop.org/archives/devkit-devel/2013-October/001519.html http://www.hadess.net/2013/10/more-power-management-changes.html ---End Message--- ---BeginMessage--- Source: wmbattery Source-Version: 2.44 We believe that the bug you reported is fixed in the latest version of wmbattery, 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 748...@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 wmbattery package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 18 Jul 2014 01:14:49 +0200 Source: wmbattery Binary: wmbattery Architecture: source i386 Version: 2.44 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Andrew Shadura andre...@debian.org Description: wmbattery - display laptop battery info, dockable in WindowMaker Closes: 740885 748935 Changes: wmbattery (2.44) unstable; urgency=medium . * Better AC detection. * Support times with upower and acpi (Closes: #740885). * Use the latest upower API (Closes: #748935). * Fix upower detection. Checksums-Sha1: 182a309530ec21b2e1b3d9136c06e850eb93d4ee 1582 wmbattery_2.44.dsc 6a36e1c69dbbe4944145bfc51e279034dce14343 39278 wmbattery_2.44.tar.gz 78237cd5038eaa1158b9c32d2d5733cee6e2e064 23728 wmbattery_2.44_i386.deb Checksums-Sha256: f2451e55ba9e723e434a31a813e196b370e731dd3712e5909ed2e0aad9fa524d 1582 wmbattery_2.44.dsc aa0a1312922ba4f0abca5f2e8abbf285363bf4a1c8862d89fe2921e74c832cae 39278 wmbattery_2.44.tar.gz 3e0bf3e05cdaeb8dbef34e1ec43e0e3a6960eba0bc0431766dfcc57650c6f543 23728 wmbattery_2.44_i386.deb Files: ebe4f7ceaadc48fde1469f9d37667995 23728 x11 extra wmbattery_2.44_i386.deb 4214b59fab11dafaf75e5d6d49cc3831 1582 x11 extra wmbattery_2.44.dsc 9055cad65d1d9d00466c5f25b79cebbf 39278 x11 extra wmbattery_2.44.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iQIcBAEBCAAGBQJTyFu3AAoJEG6k0jEaLSaNGQQQAJzVnUaq6L2TsG3U1F2UmTGl pvFvFi2DASUYtM5TQ41RqFMFHODH2K9tqVPdrVwRp5UfuCIHqH4xbKQZCNJwaJ8c 3KZ6xQOK5uhAGfrMRg3taNSEYL0B6WM+DnCMMr/ZkBiGN5diiPoueJKc795ty9vI O7tMZmR69PTj8NRx5a0Zx6dDVoE2P9o5fr9B0BlVXJzGdpE5Eroe2N3l8TprDrsT 0P429IicBmNuQDpiXYyMPXVoLW+vwjCDHOp2gSz4T/coPpns+rvP++yFZrYHzT06 dFHppm82VHQDbfWt+SFl34OvN2Qr0YyWZq/BD4gAow8Tq/48MapN5rPhXXs+kVDy RoFyCcqNzA8TRIm9aLUk9XlP/8PqUpcIK009SmIDbKkEjayJ7nwrTn8LQzPoPBRx 0Y6j33TBN5Gt5F0X2CsxqVaZ2qsgAqJKdwIhjHF5AuDe9c4g+mgY1Dlmo38Fit+/ TgcQ2XX6AhD2+xyGMl27dHK/CpqGgircob1mCLnVWyHv9lWbL1TQYVFsg8dqxZIU oU1viMErhCwdt7Y2Se3st0nOTKmFpzIiI7jyOYgQAOUIuwhBEajG7zOVSnoGqu8s heinCoRH46yAQ7T3+nqVbpqWVNi7T9ZwNLtdRW4VFw/7ONfpgXD6UWFMUC+r8aUx 4hj5RehAEFzXJTxtGV9n =BMo/ -END PGP SIGNATUREEnd Message---
Bug#740885: marked as done (wmbattery: no updates and no time estimation after kernel upgrade)
Your message dated Thu, 17 Jul 2014 23:34:31 + with message-id e1x7vc3-lw...@franck.debian.org and subject line Bug#740885: fixed in wmbattery 2.44 has caused the Debian Bug report #740885, regarding wmbattery: no updates and no time estimation after kernel upgrade 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.) -- 740885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wmbattery Version: 2.42 Severity: important It seems that after kernel upgrade to 3.12-1-amd64, wmbattery: 1. Stops updates. I.e. if I unplug power, nothing changes on wmbattery screen until i kill and restart wmbattery. I added -w 1 to command line and the charing status and accamulator status is displayed properly 2. Doesn't display charging/discharging time estimation anymore (now always 0:0) I have Lenovo x220 notebook. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-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 wmbattery depends on: ii libapm1 3.2.2-14 ii libc62.17-97 ii libglib2.0-0 2.38.2-5 ii libupower-glib1 0.9.23-2+b1 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxpm4 1:3.5.10-1 ii upower 0.9.23-2+b1 wmbattery recommends no packages. Versions of packages wmbattery suggests: ii wmaker 0.95.5-2 -- no debconf information ---End Message--- ---BeginMessage--- Source: wmbattery Source-Version: 2.44 We believe that the bug you reported is fixed in the latest version of wmbattery, 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 740...@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 wmbattery package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 18 Jul 2014 01:14:49 +0200 Source: wmbattery Binary: wmbattery Architecture: source i386 Version: 2.44 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Andrew Shadura andre...@debian.org Description: wmbattery - display laptop battery info, dockable in WindowMaker Closes: 740885 748935 Changes: wmbattery (2.44) unstable; urgency=medium . * Better AC detection. * Support times with upower and acpi (Closes: #740885). * Use the latest upower API (Closes: #748935). * Fix upower detection. Checksums-Sha1: 182a309530ec21b2e1b3d9136c06e850eb93d4ee 1582 wmbattery_2.44.dsc 6a36e1c69dbbe4944145bfc51e279034dce14343 39278 wmbattery_2.44.tar.gz 78237cd5038eaa1158b9c32d2d5733cee6e2e064 23728 wmbattery_2.44_i386.deb Checksums-Sha256: f2451e55ba9e723e434a31a813e196b370e731dd3712e5909ed2e0aad9fa524d 1582 wmbattery_2.44.dsc aa0a1312922ba4f0abca5f2e8abbf285363bf4a1c8862d89fe2921e74c832cae 39278 wmbattery_2.44.tar.gz 3e0bf3e05cdaeb8dbef34e1ec43e0e3a6960eba0bc0431766dfcc57650c6f543 23728 wmbattery_2.44_i386.deb Files: ebe4f7ceaadc48fde1469f9d37667995 23728 x11 extra wmbattery_2.44_i386.deb 4214b59fab11dafaf75e5d6d49cc3831 1582 x11 extra wmbattery_2.44.dsc 9055cad65d1d9d00466c5f25b79cebbf 39278 x11 extra wmbattery_2.44.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iQIcBAEBCAAGBQJTyFu3AAoJEG6k0jEaLSaNGQQQAJzVnUaq6L2TsG3U1F2UmTGl pvFvFi2DASUYtM5TQ41RqFMFHODH2K9tqVPdrVwRp5UfuCIHqH4xbKQZCNJwaJ8c 3KZ6xQOK5uhAGfrMRg3taNSEYL0B6WM+DnCMMr/ZkBiGN5diiPoueJKc795ty9vI O7tMZmR69PTj8NRx5a0Zx6dDVoE2P9o5fr9B0BlVXJzGdpE5Eroe2N3l8TprDrsT 0P429IicBmNuQDpiXYyMPXVoLW+vwjCDHOp2gSz4T/coPpns+rvP++yFZrYHzT06 dFHppm82VHQDbfWt+SFl34OvN2Qr0YyWZq/BD4gAow8Tq/48MapN5rPhXXs+kVDy RoFyCcqNzA8TRIm9aLUk9XlP/8PqUpcIK009SmIDbKkEjayJ7nwrTn8LQzPoPBRx 0Y6j33TBN5Gt5F0X2CsxqVaZ2qsgAqJKdwIhjHF5AuDe9c4g+mgY1Dlmo38Fit+/ TgcQ2XX6AhD2+xyGMl27dHK/CpqGgircob1mCLnVWyHv9lWbL1TQYVFsg8dqxZIU
Bug#754846: upower upgrade breaks xfce4-power-manager suspend
Confirmed fixed in xfce4-power-manager 1.2.0-5 and upower 0.99.0-3 on amd64. Thanks very much! Kind regards, -- Ben Caradoc-Davies b...@wintersun.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
