Bug#794309: python-ironic: Not installable due to depends python-sqlalchemy ( 0.10)
Package: python-ironic Version: 2015.1.0-4 Severity: grave Justification: renders package unusable All this package needs is an upload to rebuild it with the current sqlalchemy. This is blocking sqlalchemy transition to testing. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794264: systemd: System will no longer boot
On Fri, Jul 31, 2015 at 11:15:06PM +0200, Michael Biebl wrote: Control: tags -1 moreinfo Am 31.07.2015 um 20:57 schrieb ael: Package: systemd Version: 221-1 Severity: critical Justification: breaks the whole system I had to select the sysvinit option from the grub menu in order to achieve a boot. The standard menu entry got as far as (probably) trying to spawn X, and then hung. But it had no business doing that because the default target was set to default.target - /lib/systemd/system/multi-user.target in /etc/systemd/systemd/ If X hangs, what makes you sure systemd is at fault? X runs when booted via sysvinit. I have subsequently discovered that I cannot shutdown that machine. It reports something like the shutdown.service did not complete (with timeout). I think I know why that happened, *but* to refuse to umount the filesystem and stop all processes to allow a safe manual power off is a major flaw. I had to just cut power after manually unmounting the few mounts that it would permit. That whole machine is now is a complete mess, and I am not sure that I will be able to recover to try to provide the reports you request without a lot of time and effort. I will be away from the machine for about 1 month in a day or so, so such a report may be delayed. Another (amd64) machine has also stopped booting properly after the latest updates. At least it gets as far as emergency mode. That too seems to be a systemd problem. Back to the i386 machine, the target in this report: when I tried to apt-get upgrade in case the bug had been fixed, it hung on systemd because udev could not be upgraded. The udev refusal to upgrade came with a message from dpkg about a group 'Input' already existing. This from memory: so the details may not be correct. As I say that system is messed up so I can't easily check those details for now. Thanks for the reply. Please provide a verbose debug log of systemd. Add systemd.log_level=debug systemd.debug-shell to the kernel command line. You should get a debug shell on tty9, which you can use to inspect the system. Please attach the output of journalctl -alb systemd-analyze dump systemctl status [1] http://freedesktop.org/wiki/Software/systemd/Debugging/#index1h1 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794329: gdc-multilib: uninstallable in sid: Depends: gdc (= 4:5.2.1-2), but sid has gdc (5.2.1-2)
Package: gdc-multilib Version: 4:5.2.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is not installable in sid: gdc-multilib/amd64 unsatisfiable Depends: gdc (= 4:5.2.1-2) gdc-multilib/i386 unsatisfiable Depends: gdc (= 4:5.2.1-2) since gdc | 5.1.1-1 | stretch | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x gdc | 5.1.1-1 | sid | arm64, armel gdc | 5.2.1-2 | sid | amd64, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x Cheers, Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794320: main option prdr_enable unknown
On Sat, Aug 01, 2015 at 12:47:19PM +0200, Andreas Metzler wrote: Package: exim4-config Version: 4.86-1 Severity: serious After updating an old testing system I get this: Setting up exim4-config (4.86-1) ... 2015-08-01 15:04:52 Exim configuration error in line 140 of /var/lib/exim4/config.autogenerated.tmp: main option prdr_enable unknown [...] exim4-daemon-* on thissystem was older than 4.83, wasn't it? 4.82.1-2 -- WBR, wRAR signature.asc Description: Digital signature
Bug#794320: main option prdr_enable unknown
On 2015-08-01 Andrey Rahmatullin w...@wrar.name wrote: Package: exim4-config Version: 4.86-1 Severity: serious After updating an old testing system I get this: Setting up exim4-config (4.86-1) ... 2015-08-01 15:04:52 Exim configuration error in line 140 of /var/lib/exim4/config.autogenerated.tmp: main option prdr_enable unknown [...] exim4-daemon-* on thissystem was older than 4.83, wasn't it? cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794334: ea-utils: /usr/bin/alc already used by amule-utils-gui
Package: ea-utils Version: 1.1.2+dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: affects -1 + amule-utils-gui Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package ea-utils. Preparing to unpack .../ea-utils_1.1.2+dfsg-1_amd64.deb ... Unpacking ea-utils (1.1.2+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/ea-utils_1.1.2+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/alc.1.gz', which is also in package amule-utils-gui 2.3.1+git1a369e47-3 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/ea-utils_1.1.2+dfsg-1_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/alc usr/share/man/man1/alc.1.gz Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html amule-utils-gui=2.3.1+git1a369e47-3_ea-utils=1.1.2+dfsg-1.log.gz Description: application/gzip
Bug#794264: systemd: System will no longer boot
Control: severity -1 important ael [2015-08-01 7:11 +0100]: Back to the i386 machine, the target in this report: when I tried to apt-get upgrade in case the bug had been fixed, it hung on systemd because udev could not be upgraded. The udev refusal to upgrade came with a message from dpkg about a group 'Input' already existing. This sounds like https://bugs.debian.org/794280 which was already discussed: Apparently you have an input group which is not already a system group. There is some broken advice out there (like http://ptichy.blogspot.pt/2014/08/configure-evrouter-on-ubuntu-1404.html) which creates the group in a wrong way, and e. g. https://bugs.debian.org/769948 changed that to make it more obvious what happened. But it sounds like the upgrade was interrupted in the middle? Please clean up the input group (either remove or make it a system group), and run apt-get -f install, to fix the broken upgrade. How does it look like then? Downgrading to non-RC for now as this does not affect a lot of machines and we don't have enough information yet. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- 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#794264: systemd: System will no longer boot
Processing control commands: severity -1 important Bug #794264 [systemd] systemd: System will no longer boot Severity set to 'important' from 'critical' -- 794264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794264 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#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails
On Mon, 27 Jul 2015, Michael Biebl wrote:
Not sure if that is happening here. But fixing [2] and making sure
pvscan is run via /bin/systemd-run look like should be done in any
case.
Michael
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783182
Just a minor point here.
I have 2 systems running lvm over raid0.
On one of them (non-systemd init unstable box, but with systemd and
udev 223-2 installed) there's no /bin/systemd-run:
# which systemd-run
/usr/bin/systemd-run
Hardly possible to use _before_ /usr (separate partition) is mounted.
On another system (stretch (104 upgraded, 0 newly installed, 0 to
remove and 141 not upgraded), uptime: 13:09:13 up 840 days, 23:13, 67
^^^
users), the systemd package is not even installed. udev 222-2 and
lvm2 2.02.111-2.2 are installed.
systemd-run is refered to in /lib/udev/rules.d/69-lvm-metad.rules:
ACTION!=remove, ENV{LVM_PV_GONE}==1, RUN+=/bin/systemd-run
/sbin/lvm pvscan --cache $major:$minor, GOTO=lvm_end
Cheers,
--
Cristian
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade
It should, that's the default path embedded in the libs. The en variable might be used to override it. As I said, doing unset QT_PLUGIN_PATH and then running anything qt4 does not work either. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf/ signature.asc Description: This is a digitally signed message part.
Processed: tagging 794320
Processing commands for cont...@bugs.debian.org: tags 794320 - moreinfo Bug #794320 [exim4-config] main option prdr_enable unknown Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 794320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794320 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: gbsplay: diff for NMU version 0.0.91-1.1
Processing control commands: tags 777862 + pending Bug #777862 [src:gbsplay] gbsplay: ftbfs with GCC-5 Added tag(s) pending. -- 777862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777862 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#777862: gbsplay: diff for NMU version 0.0.91-1.1
Control: tags 777862 + pending
Dear maintainer,
I've prepared an NMU for gbsplay (versioned as 0.0.91-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -u gbsplay-0.0.91/debian/changelog gbsplay-0.0.91/debian/changelog
--- gbsplay-0.0.91/debian/changelog
+++ gbsplay-0.0.91/debian/changelog
@@ -1,3 +1,11 @@
+gbsplay (0.0.91-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * util.c: Apply patch from Greg Pearson to fix FTBFS with GCC 5. (Closes:
+#777862)
+
+ -- Sebastian Ramacher sramac...@debian.org Sat, 01 Aug 2015 13:00:57 +0200
+
gbsplay (0.0.91-1) unstable; urgency=low
* New upstream version.
only in patch2:
unchanged:
--- gbsplay-0.0.91.orig/util.c
+++ gbsplay-0.0.91/util.c
@@ -10,7 +10,7 @@
#include stdlib.h
-inline long rand_long(long max)
+extern inline long rand_long(long max)
/* return random long from [0;max[ */
{
return (long) (((double)max)*rand()/(RAND_MAX+1.0));
signature.asc
Description: Digital signature
Processed: tagging 794320
Processing commands for cont...@bugs.debian.org: tags 794320 + moreinfo Bug #794320 [exim4-config] main option prdr_enable unknown Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 794320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794320 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#793888: ui-gxmlcpp includes autogenerated files that cannot be rebuilt from source
Hi, Quoting Stephan Sürken (2015-08-01 10:55:52) Ok, switching to autoreconf (with b-d on ui-auto) is an option I will consider. Could you ponder a bit more why you think this is a policy violation? It seems a bit harsh considering how autotools work, and everything can be rebuild within Debian/main -- but maybe I missed something ;). I reported it like that because I was not able to recreate ./configure and aclocal.m4 from source. When I deleted both files and tried to regenerate them, I ran into an error and I also got an error when I tried to rebuild with `dh --with autoreconf`. This made me believe that ./configure and aclocal.m4 can *not* be built from source. Or maybe they can but I'm missing some magic? Thanks! cheers, josch signature.asc Description: signature
Bug#794331: daptup: insane amounts of output on upgrades from testing or jessie to sid
Thanks for the explanation. I'll see how I can handle this in piuparts properly. You don't have any debconf question I could preseed to configure this? The output limit was introduced primarily to catch packages outputting continuously while being caught in a loop. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: sssd-common: deletes conffile owned by sssd: /etc/logrotate.d/sssd
Processing control commands: affects -1 + sssd Bug #794332 [sssd-common] sssd-common: deletes conffile owned by sssd: /etc/logrotate.d/sssd Added indication that 794332 affects sssd -- 794332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794332 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#794061: breeze: Breeze theme completely stopped working after the last upgrade
On Saturday 01 August 2015 09:22:30 Salvo Tomaselli wrote: [snip] The Debian qt4-x11 build looks for plugins in /usr/lib/arch/qt4/plugins. That's why it loads the breeze style even when the path is not explicitly listed in QT_PLUGIN_PATH. I don't think it does load it without the env-var :) It should, that's the default path embedded in the libs. The en variable might be used to override it. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#794332: sssd-common: deletes conffile owned by sssd: /etc/logrotate.d/sssd
Package: sssd-common Version: 1.12.5-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + sssd Hi, during a test with piuparts I noticed your package deletes an (obsolete) conffile owned another package. The chosen approach is wrong since it does not update dpkg's database. debsums reports modification of the following files, from the attached log (scroll to the bottom...): 2m6.8s ERROR: FAIL: debsums reports modifications inside the chroot: debsums: missing file /etc/logrotate.d/sssd (from sssd package) The correct approach should be (but I didn't test this): * drop manual cleanup from sssd-common maintainer scripts * add debian/sssd.maintscript containing = 8 = rm_conffile /etc/logrotate.d/sssd 1.12.5-3~ = 8 = cheers, Andreas sssd_1.12.5-2.log.gz Description: application/gzip
Bug#794333: cpl-plugin-naco-calib: fails to download naco-kit-4.4.0.tar.gz, does not exist
Package: cpl-plugin-naco-calib Version: 4.4.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package cpl-plugin-naco-calib. (Reading database ... (Reading database ... 7758 files and directories currently installed.) Preparing to unpack .../cpl-plugin-naco-calib_4.4.0+dfsg-1_all.deb ... Unpacking cpl-plugin-naco-calib (4.4.0+dfsg-1) ... Setting up cpl-plugin-naco-calib (4.4.0+dfsg-1) ... --2015-08-01 07:47:48-- ftp://ftp.eso.org/pub/dfs/pipelines/naco/naco-kit-4.4.0.tar.gz = '-' Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54 Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected. Logging in as anonymous ... Logged in! == SYST ... done.== PWD ... done. == TYPE I ... done. == CWD (1) /pub/dfs/pipelines/naco ... done. == SIZE naco-kit-4.4.0.tar.gz ... done. == PASV ... done.== RETR naco-kit-4.4.0.tar.gz ... No such file 'naco-kit-4.4.0.tar.gz'. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now dpkg: error processing package cpl-plugin-naco-calib (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: cpl-plugin-naco-calib There are naco-kit-4.4.0-1.tar.gz and naco-kit-4.4.0-3.tar.gz instead. cheers, Andreas cpl-plugin-naco-calib_4.4.0+dfsg-1.log.gz Description: application/gzip
Processed: ea-utils: /usr/bin/alc already used by amule-utils-gui
Processing control commands: affects -1 + amule-utils-gui Bug #794334 [ea-utils] ea-utils: /usr/bin/alc already used by amule-utils-gui Added indication that 794334 affects amule-utils-gui -- 794334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794334 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#794323: Should xmail be removed?
Package: xmail Severity: serious The last upstream release in was 2010, that's also when the last maintainer upload occured. It has longstanding RC bugs and already missed jessie. popcon is marginal and we have many good mail servers in Debian as alternatives. If anyone disgrees with the removal, please bring the package in shape, otherwise let's reassign this bug to ftp.debian.org for removal. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789914: apache2: fails to install: ERROR: Module mpm_event is enabled - cannot proceed due to conflicts. It needs to be disabled first!
On Monday 20 July 2015 13:33:04, Jean-Michel Vourgère wrote: We want to backport that to jessie, don't we? I mean a minimal fix. Yes, we do. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794353: python-rally: Uninstallable due to python-sqlalchemy version depends
Package: python-rally
Version: 0.0.3-4
Severity: grave
Justification: renders package unusable
A simple rebuild and upload of the package would be sufficient to pick up
the newer python-sqlalchemy depends, but it FTBFS when I tried to rebuild it.
https://release.debian.org/transitions/html/sqlalchemy.html
Scott K
process-returncode
process-returncode ... FAIL
==
FAIL:
tests.unit.deploy.serverprovider.providers.test_lxc.LxcHostTestCase.test_prepare
tests.unit.deploy.serverprovider.providers.test_lxc.LxcHostTestCase.test_prepare
--
_StringException: Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 1305, in patched
return func(*args, **keywargs)
File tests/unit/deploy/serverprovider/providers/test_lxc.py, line 101, in
test_prepare
fake_conf.write.assert_has_calls(call)
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 969, in
assert_has_calls
), cause)
File /usr/lib/python2.7/dist-packages/six.py, line 692, in raise_from
raise value
AssertionError: Calls not found.
Expected: call('LXC_DHCP_MAX=253\n')
Actual: [call('LXC_DHCP_MAX=253\n'),
call('LXC_NETMASK=255.255.255.0\n'),
call('LXC_ADDR=10.1.1.1\n'),
call('LXC_DHCP_RANGE=10.1.1.2,10.1.1.254\n'),
call('LXC_NETWORK=10.1.1.0/24\n'),
call('LXC_BRIDGE=lxcbr0\n'),
call('USE_LXC_BRIDGE=true\n')]
Traceback (most recent call last):
_StringException: Empty attachments:
stderr
stdout
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 1305, in patched
return func(*args, **keywargs)
File tests/unit/deploy/serverprovider/providers/test_lxc.py, line 101, in
test_prepare
fake_conf.write.assert_has_calls(call)
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 969, in
assert_has_calls
), cause)
File /usr/lib/python2.7/dist-packages/six.py, line 692, in raise_from
raise value
AssertionError: Calls not found.
Expected: call('LXC_DHCP_MAX=253\n')
Actual: [call('LXC_DHCP_MAX=253\n'),
call('LXC_NETMASK=255.255.255.0\n'),
call('LXC_ADDR=10.1.1.1\n'),
call('LXC_DHCP_RANGE=10.1.1.2,10.1.1.254\n'),
call('LXC_NETWORK=10.1.1.0/24\n'),
call('LXC_BRIDGE=lxcbr0\n'),
call('USE_LXC_BRIDGE=true\n')]
Traceback (most recent call last):
_StringException: Empty attachments:
stderr
stdout
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 1305, in patched
return func(*args, **keywargs)
File tests/unit/deploy/serverprovider/providers/test_lxc.py, line 101, in
test_prepare
fake_conf.write.assert_has_calls(call)
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 969, in
assert_has_calls
), cause)
File /usr/lib/python2.7/dist-packages/six.py, line 692, in raise_from
raise value
AssertionError: Calls not found.
Expected: call('LXC_DHCP_MAX=253\n')
Actual: [call('LXC_DHCP_MAX=253\n'),
call('LXC_NETMASK=255.255.255.0\n'),
call('LXC_ADDR=10.1.1.1\n'),
call('LXC_DHCP_RANGE=10.1.1.2,10.1.1.254\n'),
call('LXC_NETWORK=10.1.1.0/24\n'),
call('LXC_BRIDGE=lxcbr0\n'),
call('USE_LXC_BRIDGE=true\n')]
==
FAIL: tests.unit.deploy.test_lxc.LxcEngineTestCase.test_cleanup
tests.unit.deploy.test_lxc.LxcEngineTestCase.test_cleanup
--
_StringException: Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 1305, in patched
return func(*args, **keywargs)
File tests/unit/deploy/test_lxc.py, line 210, in test_cleanup
m_deployment.assert_has_calls(mock.call.delete_resource(res.id))
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 965, in
assert_has_calls
if expected not in all_calls:
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 454, in
__contains__
if sub_list == value:
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 2171, in __eq__
first, second = other
ValueError: too many values to unpack
Traceback (most recent call last):
_StringException: Empty attachments:
stderr
stdout
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 1305, in patched
return func(*args, **keywargs)
File tests/unit/deploy/test_lxc.py, line 210, in test_cleanup
m_deployment.assert_has_calls(mock.call.delete_resource(res.id))
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 965, in
assert_has_calls
if expected not in all_calls:
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 454, in
__contains__
if sub_list == value:
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 2171, in __eq__
first, second = other
ValueError: too many values to unpack
Traceback (most recent call last):
_StringException: Empty attachments:
stderr
stdout
Bug#794355: python-neutron-lbaas: Uninstallable due to python-sqlachemy version requirements
Package: python-neutron-lbaas
Version: 2015.1.0-2
Severity: grave
Justification: renders package unusable
A simple rebuild and upload of the package would be sufficient to pick up
the newer python-sqlalchemy depends, but it FTBFS when I tried to rebuild it.
https://release.debian.org/transitions/html/sqlalchemy.html
Scott K
2015-08-02 03:12:40,030ERROR [neutron_lbaas.drivers.radware.rest_client]
REST client is not able to recover since only one vDirect server is configured.
}}}
pythonlogging:'neutron.api.extensions': {{{2015-08-02 03:12:39,646ERROR
[neutron.api.extensions] Extension path 'neutron/tests/unit/extensions' doesn't
exist!}}}
Traceback (most recent call last):
File neutron_lbaas/tests/unit/drivers/radware/test_v2_plugin_driver.py,
line 173, in test_flip_servers
self.flip_servers_mock.assert_called_once()
File /usr/lib/python2.7/dist-packages/mock/mock.py, line 721, in __getattr__
raise AttributeError(name)
AttributeError: assert_called_once
==
FAIL: process-returncode
process-returncode
--
_StringException: returncode 1
--
Ran 842 tests in 386.992s
FAILED (failures=4, skipped=1)
debian/rules:19: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/home/neutron-lbaas-2015.1.0'
debian/rules:11: recipe for target 'build' failed
make: *** [build] Error 2
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#451535: This bug just ate my LVM2 volume group.
I totally empathise with Ian's frustration. I myself spent eight hours trying to circumvent this 'bug', to put it mildly. I tried to follow a half-dozen contradictory, inaccurate and incomplete walkthroughs with no success, so I'm giving up and starting from scratch. The walkthrough at http://wiki.debian.org/DebianInstaller/Rescue/Crypto does not exist. As this bug hasn't been addressed in 8 years, it may be worth giving up on it. If so, there should at least be bold warnings to anybody tempted to set up encrypted volumes that they will not be reusable if one needs to reinstall Debian unless they have highly advanced knowledge of hand-writing configuration files from rescue CDs. This would, at least, stop hundreds of aggregate human hours from being wasted. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792685: Unable to upgrade from wheezy to jessie
On Jul 30 2015, Sam Hartman hartm...@debian.org wrote: I'll try and reproduce this in the next day or so and give you access to a failing example. No need, I just managed to reproduce it locally with a filesystem freshly created in wheezy. I'll look into it. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 794344 with 794352 794353 794354 794355
Processing commands for cont...@bugs.debian.org: block 794344 with 794352 794353 794354 794355 Bug #794344 [release.debian.org] transition: python-sqlalchemy 794344 was not blocked by any bugs. 794344 was not blocking any bugs. Added blocking bug(s) of 794344: 794352, 794353, 794355, and 794354 Warning: Unknown package 'src:python-trove' thanks Stopping processing here. Please contact me if you need assistance. -- 794344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794344 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#792685: Updated package
Hi, I uploaded an updated package to mentors for easier testing (and also for someone to sponsor the upload if we've sorted out all problems, I'm not a DD): https://mentors.debian.net/package/s3ql http://mentors.debian.net/debian/pool/main/s/s3ql/s3ql_2.11.1+dfsg-3.dsc Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794352: python-trove: Uninstallable due to python-alchemy version
Source: python-trove Version: 2015.1.0-3 Severity: grave Justification: renders package unusable A simple rebuild and upload of the package should be sufficient to pick up the newer python-sqlalchemy depends. https://release.debian.org/transitions/html/sqlalchemy.html I'd be glad to do it if you prefer, just reply to the bug. Scott K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792685: Unable to upgrade from wheezy to jessie
Hi, Alright, I figured this one out. First, the reason you're having an s3ql_metadata_bak_0 object right after the upgrade is that the upgrade itself backups up the metadata *after* having added the _pre21 suffix to the existing backups. Secondly (and contrary to what I said before), this should nevertheless work fine, because the object metadata (metadata about the storage object holding the file-system metadata) is upgraded when the object is renamed (from s3ql_metadata to s3ql_metadata_bak_0). Thirdly, there is a bug in all versions of S3QL that prevent it to work properly if the bucket prefix contains a plus. This is what initially prevented me from reproducing your problem. Fourth, there is a bug in recent S3QL versions when reading object metadata created by S3QL 1.x. There is a function that appears to return a string, but it actually returns a email.headerregistry._UnstructuredHeader instance that looks and behaves like a string. During the upgrade of the metadata, this object (instead of a string) is then pickled and stored - and when it is then loaded again, S3QL correctly complains that this is an unsafe pickle that attempts to instantiate a weird class. The reason that this does not happen when doing the upgrade in two separate steps is that the more recent S3QL version never looks at the metadata object created by the 1.x version - it gets turned into a backup during the first upgrade, and gets a _pre21 suffix in the second upgrade. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792685: Unable to upgrade from wheezy to jessie
control: tags -1 +pending I've just uploaded a new package to mentors that should fix the issue with the unsafe metadata backup. If this works for you too, I think this is suitable for stable-updates. I'm not sure what the procedure is to get a package in there, so please let me know if I can do anything else to facilitate this. (While I recently became DM, I still haven't managed to get a DD to actually give me upload rights for the packages that I maintain :-/). Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- 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#792685: Unable to upgrade from wheezy to jessie
Processing control commands: tags -1 +pending Bug #792685 [s3ql] Unable to upgrade from wheezy to jessie Added tag(s) pending. -- 792685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792685 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#794354: python-sahara: Uninstallable due to python-sqalchemy version requirement
Package: python-sahara Version: 2015.1.0-6 Severity: grave Justification: renders package unusable A simple rebuild and upload of the package should be sufficient to pick up the newer python-sqlalchemy depends. https://release.debian.org/transitions/html/sqlalchemy.html I'd be glad to do it if you prefer, just reply to the bug. Scott K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792685: marked as done (Unable to upgrade from wheezy to jessie)
Your message dated Sat, 01 Aug 2015 21:34:19 -0700
with message-id 87h9oie2b8.fsf...@vostro.rath.org
and subject line Re: Bug#792685: Unable to upgrade from wheezy to jessie
has caused the Debian Bug report #792685,
regarding Unable to upgrade from wheezy to jessie
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.)
--
792685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
package: s3ql
severity: grave
version: 2.11.1+dfsg-1
Justification: Renders filesystem unusable and data accessible
Hi.
I'm upgrading a system from wheezy to jessie.
Wheezy ships s3ql 1.11, jessie ships version 2.11.
I have a filesystem that I can easily mount and fsck in wheezy, but when
I try to run the jessie s3qladm upgrade command I get:
Getting file system parameters..
File system revision too old to upgrade!
You need to use an older S3QL version to upgrade to a more recent
revision before you can use this version to upgrade to the newest
revision.
Uncaught top-level exception:
Traceback (most recent call last):
File /usr/bin/s3qladm, line 9, in module
load_entry_point('s3ql==2.11.1', 'console_scripts', 's3qladm')()
File /usr/lib/s3ql/s3ql/adm.py, line 96, in main
options.cachedir))
File /usr/lib/s3ql/s3ql/adm.py, line 316, in upgrade
print(get_old_rev_msg(param['revision'] + 1, 's3qladm'))
File /usr/lib/s3ql/s3ql/adm.py, line 224, in
get_old_rev_msg
''' % { 'version': REV_VER_MAP[rev],
KeyError: 17
It's critical that there be a documented procedure that works for
upgrading from the version in wheezy to the version in jessie using
tools in jessie.
There was another upgrade at version 2.5, which is not in either wheezy
or jessie. However, it needs to be possible to upgrade from one Debian
release to the next using the software in Debian.
I believe this problem is important enough to fix in a Jessie point
release and would be happy to help with any process issues that come up
in making that happen.
pgplokaIMQ7l8.pgp
Description: PGP signature
---End Message---
---BeginMessage---
Version: 2.13
Marking as fixed in testing. By definition, this bug only applies to
jessie.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«---End Message---
Bug#794342: gnote: Please rebuild gnote
Package: gnote Version: 3.16.2-1 Severity: grave Justification: renders package unusable Due to the transition to gcc-5 gnote needs a rebuild against libgcc1. Otherwise it would be removed or substituded by tomboy which blows up installations with mono stuff. Pick up the chance to upgrade to 5.17. Elimar -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-rc4-galadriel-lxtec-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnote depends on: ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii libatk1.0-0 2.16.0-2 ii libatkmm-1.6-1 2.22.7-2.1 ii libc62.19-19 ii libcairo-gobject21.14.2-2 ii libcairo21.14.2-2 ii libcairomm-1.0-1 1.10.0-1.1 ii libenchant1c2a 1.6.0-10.1 ii libgcc1 1:5.1.1-14 ii libgdk-pixbuf2.0-0 2.31.5-1 ii libglib2.0-0 2.44.1-1.1 ii libglibmm-2.4-1c2a 2.44.0-1 ii libgtk-3-0 3.16.6-1 ii libgtkmm-3.0-1 3.16.0-1 ii libgtkspell3-3-0 3.0.7-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangomm-1.4-1 2.36.0-1 ii libsecret-1-00.18.2-1 ii libsigc++-2.0-0c2a 2.4.1-1 ii libstdc++6 5.1.1-14 ii libuuid1 2.26.2-9 ii libx11-6 2:1.6.3-1 ii libxml2 2.9.2+dfsg1-3 ii libxslt1.1 1.1.28-2+b2 gnote recommends no packages. gnote 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#794329: marked as done (gdc-multilib: uninstallable in sid: Depends: gdc (= 4:5.2.1-2), but sid has gdc (5.2.1-2))
Your message dated Sat, 01 Aug 2015 19:04:37 + with message-id e1zlc5f-0003zg...@franck.debian.org and subject line Bug#794329: fixed in gcc-defaults 1.144 has caused the Debian Bug report #794329, regarding gdc-multilib: uninstallable in sid: Depends: gdc (= 4:5.2.1-2), but sid has gdc (5.2.1-2) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 794329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gdc-multilib Version: 4:5.2.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is not installable in sid: gdc-multilib/amd64 unsatisfiable Depends: gdc (= 4:5.2.1-2) gdc-multilib/i386 unsatisfiable Depends: gdc (= 4:5.2.1-2) since gdc | 5.1.1-1 | stretch | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x gdc | 5.1.1-1 | sid | arm64, armel gdc | 5.2.1-2 | sid | amd64, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x Cheers, Andreas ---End Message--- ---BeginMessage--- Source: gcc-defaults Source-Version: 1.144 We believe that the bug you reported is fixed in the latest version of gcc-defaults, 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 794...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated gcc-defaults 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, 01 Aug 2015 20:45:36 +0200 Source: gcc-defaults Binary: cpp g++ g++-multilib gobjc gobjc-multilib gobjc++ gobjc++-multilib gfortran gfortran-multilib gccgo gccgo-multilib libgcj-common libgcj-bc gcj-jdk gcj-jre-headless gcj-jre gcc gcc-multilib gdc gdc-multilib libphobos-dev Architecture: source amd64 all Version: 1.144 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers debian-...@lists.debian.org Changed-By: Matthias Klose d...@debian.org Description: cpp- GNU C preprocessor (cpp) g++- GNU C++ compiler g++-multilib - GNU C++ compiler (multilib files) gcc- GNU C compiler gcc-multilib - GNU C compiler (multilib files) gccgo - Go compiler, based on the GCC backend gccgo-multilib - Go compiler, based on the GCC backend (multilib files) gcj-jdk- gcj and Classpath development tools for Java(TM) gcj-jre- Java runtime environment using GIJ/Classpath gcj-jre-headless - Java runtime environment using GIJ/Classpath (headless version) gdc- D compiler (language version 2), based on the GCC backend gdc-multilib - D compiler (language version 2) (multilib files) gfortran - GNU Fortran 95 compiler gfortran-multilib - GNU Fortran 95 compiler (multilib files) gobjc - GNU Objective-C compiler gobjc++- GNU Objective-C++ compiler gobjc++-multilib - GNU Objective-C++ compiler (multilib files) gobjc-multilib - GNU Objective-C compiler (multilib files) libgcj-bc - Link time only library for use with gcj libgcj-common - Java runtime library (common files) libphobos-dev - Phobos D standard library Closes: 794329 Changes: gcc-defaults (1.144) unstable; urgency=medium . * Build gdc with an epoch. Closes: #794329. Checksums-Sha1: c61d721eab4316cc7330f9b0d010f793fd380380 3386 gcc-defaults_1.144.dsc e473877e2b199550e46633e9e9d620a37bb92e98 64596 gcc-defaults_1.144.tar.gz e4b8e95365138549668cb0180c2efaabbbf5987f 17646 cpp_5.2.1-3_amd64.deb 18c5dd64b5777ca54b69ddb9480517ed2f8e3666 892 g++-multilib_5.2.1-3_amd64.deb 8c3c338041ef38117a8c443248a38564eac0033b 1584 g++_5.2.1-3_amd64.deb d4b03c261362d1b2e43d885dd13ba7e1573e5376 1020 gcc-multilib_5.2.1-3_amd64.deb 75bb325ba480404a11012fee746da4977ee3a107 5218 gcc_5.2.1-3_amd64.deb 2f2786f9dc4b4f783cd54ce8d76773dfca95d48c 932 gccgo-multilib_5.2.1-3_amd64.deb ccbcbb89c455138a6d631aa581ca8bbd79bf8316 1126 gccgo_5.2.1-3_amd64.deb 48fda19680bb8762f7dcb90506e58d2612ab114c 6130 gcj-jdk_5.2.1-3_amd64.deb 8b74cfb26423dc7a2d23cd8a2906aceaf4261ce0 1622 gcj-jre-headless_5.2.1-3_amd64.deb
Bug#794342: gnote: Please rebuild gnote
* Elimar Riesebieter riese...@lxtec.de [2015-08-01 20:54 +0200]: Pick up the chance to upgrade to 5.17. Should be 3.17. Elimar -- Numeric stability is probably not all that important when you're guessing;-) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794331: daptup: insane amounts of output on upgrades from testing or jessie to sid
On 01.08.2015 21:34, Andreas Beckmann wrote: Thanks for the explanation. I'll see how I can handle this in piuparts properly. You don't have any debconf question I could preseed to configure this? No. One more option is maybe you could get rid of the daptup hook using dpkg path filtering (didn't use it myself, man page suggests something like '--path-exclude=/etc/apt/apt.conf.d/11daptup'). -- Eugene V. Lyubimkin aka JackYF, JID: jackyf(maildog)jabber.fsfe.org C++ GNU/Linux userspace developer, Debian Developer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777862: gbsplay: diff for NMU version 0.0.91-1.1
On 2015-08-01 20:47:19, Christian Garbs wrote: On Sat, Aug 01, 2015 at 01:02:15PM +0200, Sebastian Ramacher wrote: Dear maintainer, I've prepared an NMU for gbsplay (versioned as 0.0.91-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Hello Sebastian, thanks for the NMU! We've done a new upstream release of gbsplay that includes this patch as well as the fix for #715944. I've created a debian package for the new release as well (gbsplay_0.0.92-2). It looks like gbsplay 0.0.92-1 was never uploaded to the archive. Could you please merge 0.9.92-2 into the changelog entry for 0.9.92-1? lintian also reports W: gbsplay: copyright-refers-to-versionless-license-file usr/share/common-licenses/GPL Please fix that too. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Processed: Re: icu: library transition may be needed when GCC 5 is the default
Processing control commands: severity -1 serious Bug #791072 [src:icu] icu: library transition may be needed when GCC 5 is the default Severity set to 'serious' from 'important' tags -1 + patch Bug #791072 [src:icu] icu: library transition may be needed when GCC 5 is the default Added tag(s) patch. retitle -1 icu: library transition may be needed when GCC 5 is the default Bug #791072 [src:icu] icu: library transition may be needed when GCC 5 is the default Ignoring request to change the title of bug#791072 to the same title -- 791072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791072 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#792157: marked as done (flask-sqlalchemy: Not installable: Depends: python-sqlalchemy ( 0.10) but 1.0.6+ds1-1 is in sid)
Your message dated Sun, 02 Aug 2015 01:04:18 + with message-id e1zlhhk-lo...@franck.debian.org and subject line Bug#792157: fixed in flask-sqlalchemy 1.0-3 has caused the Debian Bug report #792157, regarding flask-sqlalchemy: Not installable: Depends: python-sqlalchemy ( 0.10) but 1.0.6+ds1-1 is 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.) -- 792157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: flask-sqlalchemy Version: 1.0-2 Severity: serious Tags: sid User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package cannot be installed in sid: # apt-get install python-flask-sqlalchemy The following packages have unmet dependencies: python-flask-sqlalchemy : Depends: python-sqlalchemy ( 0.10) but 1.0.6+ds1-1 is to be installed E: Unable to correct problems, you have held broken packages. This is causing e.g. flask-migrate to FTBFS. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-22-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Source: flask-sqlalchemy Source-Version: 1.0-3 We believe that the bug you reported is fixed in the latest version of flask-sqlalchemy, 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 792...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman sc...@kitterman.com (supplier of updated flask-sqlalchemy 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, 01 Aug 2015 20:43:19 -0400 Source: flask-sqlalchemy Binary: python-flask-sqlalchemy python3-flask-sqlalchemy Architecture: source all Version: 1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Scott Kitterman sc...@kitterman.com Description: python-flask-sqlalchemy - adds SQLAlchemy support to your Flask application python3-flask-sqlalchemy - adds SQLAlchemy support to your Flask application Closes: 792157 Changes: flask-sqlalchemy (1.0-3) unstable; urgency=medium . * Team upload. * Rebuild for SQLAlchemy 1.0 (Closes: #792157) * Update debian/watch to use pypi.debian.net redirector Checksums-Sha1: 44e9063fd82a744c13b2cb145ddb63298a0b6aaa 2320 flask-sqlalchemy_1.0-3.dsc d9c66560da7b2f32df5e7453617e93dde1cbddd5 2272 flask-sqlalchemy_1.0-3.debian.tar.xz 80324c60e5219e49d1700c95fbc7a0da499e9afc 12570 python-flask-sqlalchemy_1.0-3_all.deb 0bb5e887e6325b021a5bae3412142e84ce71f341 12548 python3-flask-sqlalchemy_1.0-3_all.deb Checksums-Sha256: 419accbdc850dbf2dcc8aeac999c9654decd300cf8aa4eb78f199181e5b04715 2320 flask-sqlalchemy_1.0-3.dsc 3f33df891830966db1258087c108b21c1ac91e7641d5bf3a88ce2fbdca7a17aa 2272 flask-sqlalchemy_1.0-3.debian.tar.xz dbdaf2d8ab09094e1e204eca02fcf8f769ffc51a2daf74003ef30039be4f7c4c 12570 python-flask-sqlalchemy_1.0-3_all.deb 68f3893d6a9ceb648ee350d957878712c7f74955df9725a72f3ba9ad85ce28bb 12548 python3-flask-sqlalchemy_1.0-3_all.deb Files: 64b913643d4e8ed310fc81590dccd72d 2320 python optional flask-sqlalchemy_1.0-3.dsc c157064cd2469dcb7890c0c87df4 2272 python optional flask-sqlalchemy_1.0-3.debian.tar.xz ec888e75886cefcffacc4023bafbdcb4 12570 python optional python-flask-sqlalchemy_1.0-3_all.deb 714b83d191d41686aba7f70d80e400e2 12548 python optional python3-flask-sqlalchemy_1.0-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVvWpDAAoJEHjX3vua1Zrxv2YP/jZXXb6qfvuwbfT2Kycwg6KJ 3SZG4mRUH/c8kZg1NcmehISzADQYtnua2yYC9+WMJIyIGRjBv3CGGxI4IdGVBP1Y ndgsQS6mmG3+8O3CLUD2yB1Bb3+oUu1rul8cOXBTGTCNUBc3h4Z0zCnhxFYKZ/rF zzf7RsjnXWpN21qEqZ7C/JYDbrQ30nLSYXNAuHFzD0g/6vqOnw4cnliIvLPH9wJy uzaSBBcwjJcMxE9tB7F7w/3USQ2LxHtA44y4yYh/0m99scP5J4RtboZQ+9wRzA52 T1o+STJ0MpaFRBoIAnaQdoCUWsaNfMKQqs3HcDCYM3NMBl5vaGyxxWGudlWncS1c
Bug#794045: hashdeep: fails to upgrade from md5deep/experimental
Control: severity -1 important On Thu, 30 Jul 2015, Andreas Beckmann wrote: during a test with piuparts I noticed your package fails to upgrade from 'md5deep' in 'experimental' to hashdeep in sid. While this is a problem, experimental packages are not widely used and I don't think this justifies a serious severity. Hence downgrading to important so that the testing migration is not blocked by this small issue (md5deep got removed from testing due to this transition and I would like its replacement to be there quickly). Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: hashdeep: fails to upgrade from md5deep/experimental
Processing control commands: severity -1 important Bug #794045 [hashdeep] hashdeep: fails to upgrade from md5deep/experimental Severity set to 'important' from 'serious' -- 794045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794045 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: libsdl-sge: library transition may be needed when GCC 5 is the default
Processing commands for cont...@bugs.debian.org:
reopen 791165
Bug #791165 {Done: m...@debian.org (Manuel A. Fernandez Montecelo)}
[src:libsdl-sge] libsdl-sge: library transition may be needed when GCC 5 is the
default
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libsdl-sge/030809dfsg-5.
severity 791165 serious
Bug #791165 [src:libsdl-sge] libsdl-sge: library transition may be needed when
GCC 5 is the default
Severity set to 'serious' from 'important'
tags 791165 + confirmed
Bug #791165 [src:libsdl-sge] libsdl-sge: library transition may be needed when
GCC 5 is the default
Added tag(s) confirmed.
retitle 791165 libsdl-sge: library transition is needed when GCC 5 is the
default
Bug #791165 [src:libsdl-sge] libsdl-sge: library transition may be needed when
GCC 5 is the default
Changed Bug title to 'libsdl-sge: library transition is needed when GCC 5 is
the default' from 'libsdl-sge: library transition may be needed when GCC 5 is
the default'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
791165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791165
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#791072: icu: library transition may be needed when GCC 5 is the default
Processing control commands: tags -1 pending Bug #791072 [src:icu] icu: library transition may be needed when GCC 5 is the default Added tag(s) pending. -- 791072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791072 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#791072: icu: library transition may be needed when GCC 5 is the default
Control: tags -1 pending
Hi Matthias,
On Sat, Aug 1, 2015 at 11:23 PM, Matthias Klose d...@debian.org wrote:
Control: tags -1 + patch
You missed attaching the patch, but I think you mean the one I do attach.
this is exactly what should *not* be done. A simple rebuild changing the
symbols
without renaming the library or without bumping the soname.
The patch renames the library to libicu52v5 (adds breaks/replaces)
and should provide an easy transition.
Pretty please
upload the version from experimental to unstable.
It would be a bigger transition as the API changed. Needs testing if
all packages can be built with the new, 55.1 version. Will do that in
the morning. Midnight is passed here. :-|
Regards,
Laszlo/GCS
diff -Nru icu-52.1/debian/changelog icu-52.1/debian/changelog
--- icu-52.1/debian/changelog 2015-08-01 08:16:21.0 +0200
+++ icu-52.1/debian/changelog 2015-08-01 23:41:33.0 +0200
@@ -1,3 +1,9 @@
+icu (52.1-12) unstable; urgency=low
+
+ * Rename library for GCC-5 transition (closes: #791072).
+
+ -- Laszlo Boszormenyi (GCS) g...@debian.org Sat, 01 Aug 2015 19:39:05 +
+
icu (52.1-11) unstable; urgency=medium
* Build using GCC 5.
diff -Nru icu-52.1/debian/control icu-52.1/debian/control
--- icu-52.1/debian/control 2015-08-01 08:13:29.0 +0200
+++ icu-52.1/debian/control 2015-08-01 23:39:10.0 +0200
@@ -7,12 +7,14 @@
Build-Depends-Indep: doxygen (= 1.7.1)
Homepage: http://www.icu-project.org
-Package: libicu52
+Package: libicu52v5
Section: libs
Multi-Arch: same
Architecture: any
Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends}, ${shlibs:Depends}
+Breaks: libicu52
+Replaces: libicu52
Description: International Components for Unicode
ICU is a C++ and C library that provides robust and full-featured
Unicode and locale support. This package contains the runtime
@@ -23,7 +25,7 @@
Priority: extra
Architecture: any
Pre-Depends: ${misc:Pre-Depends}
-Depends: ${misc:Depends}, libicu52 (= ${binary:Version})
+Depends: ${misc:Depends}, libicu52v5 (= ${binary:Version})
Description: International Components for Unicode
ICU is a C++ and C library that provides robust and full-featured
Unicode and locale support. This package contains debugging symbols
@@ -34,7 +36,7 @@
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
-Depends: ${misc:Depends}, ${shlibs:Depends}, libicu52 (= ${binary:Version}), icu-devtools (= ${binary:Version}), libc6-dev | libc-dev, libstdc++-5-dev (= 5.2.1-10), g++ (= 4:5-0)
+Depends: ${misc:Depends}, ${shlibs:Depends}, libicu52v5 (= ${binary:Version}), icu-devtools (= ${binary:Version}), libc6-dev | libc-dev, libstdc++-5-dev (= 5.2.1-10), g++ (= 4:5-0)
Suggests: icu-doc
Description: Development files for International Components for Unicode
ICU is a C++ and C library that provides robust and full-featured
diff -Nru icu-52.1/debian/libicu52.install icu-52.1/debian/libicu52.install
--- icu-52.1/debian/libicu52.install 2015-02-16 03:35:11.0 +0100
+++ icu-52.1/debian/libicu52.install 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
diff -Nru icu-52.1/debian/libicu52.lintian-overrides icu-52.1/debian/libicu52.lintian-overrides
--- icu-52.1/debian/libicu52.lintian-overrides 2015-02-16 03:35:11.0 +0100
+++ icu-52.1/debian/libicu52.lintian-overrides 1970-01-01 01:00:00.0 +0100
@@ -1,3 +0,0 @@
-# libicu52 installs multiple shared libraries, none of which is
-# actually called libicu.so.52, but all of which are libicu*.so.52.
-libicu52: package-name-doesnt-match-sonames
diff -Nru icu-52.1/debian/libicu52.shlibs icu-52.1/debian/libicu52.shlibs
--- icu-52.1/debian/libicu52.shlibs 2015-02-16 03:35:11.0 +0100
+++ icu-52.1/debian/libicu52.shlibs 1970-01-01 01:00:00.0 +0100
@@ -1,8 +0,0 @@
-libicudata 52 libicu52 (= 52~m1-1~)
-libicui18n 52 libicu52 (= 52~m1-1~)
-libicuio 52 libicu52 (= 52~m1-1~)
-libicule 52 libicu52 (= 52~m1-1~)
-libiculx 52 libicu52 (= 52~m1-1~)
-libicutest 52 libicu52 (= 52~m1-1~)
-libicutu 52 libicu52 (= 52~m1-1~)
-libicuuc 52 libicu52 (= 52~m1-1~)
diff -Nru icu-52.1/debian/libicu52v5.install icu-52.1/debian/libicu52v5.install
--- icu-52.1/debian/libicu52v5.install 1970-01-01 01:00:00.0 +0100
+++ icu-52.1/debian/libicu52v5.install 2015-02-16 03:35:11.0 +0100
@@ -0,0 +1 @@
+usr/lib/*/lib*.so.*
diff -Nru icu-52.1/debian/libicu52v5.lintian-overrides icu-52.1/debian/libicu52v5.lintian-overrides
--- icu-52.1/debian/libicu52v5.lintian-overrides 1970-01-01 01:00:00.0 +0100
+++ icu-52.1/debian/libicu52v5.lintian-overrides 2015-08-01 23:40:23.0 +0200
@@ -0,0 +1,3 @@
+# libicu52 installs multiple shared libraries, none of which is
+# actually called libicu.so.52, but all of which are libicu*.so.52.
+libicu52v5: package-name-doesnt-match-sonames
diff -Nru icu-52.1/debian/libicu52v5.shlibs icu-52.1/debian/libicu52v5.shlibs
--- icu-52.1/debian/libicu52v5.shlibs 1970-01-01 01:00:00.0 +0100
+++
Bug#789914: marked as done (apache2: fails to install: ERROR: Module mpm_event is enabled - cannot proceed due to conflicts. It needs to be disabled first!)
Your message dated Sat, 01 Aug 2015 23:05:22 + with message-id e1zlfqe-0006bc...@franck.debian.org and subject line Bug#789914: fixed in apache2 2.4.16-1 has caused the Debian Bug report #789914, regarding apache2: fails to install: ERROR: Module mpm_event is enabled - cannot proceed due to conflicts. It needs to be disabled first! 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.) -- 789914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: apache2.2-common Version: 2.4.12-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. This bug was triggered when installing (the dependencies of) fusionforge-web 6.0.1-1 in a minimal piuparts chroot. From the attached log (scroll to the bottom...): [...] Setting up apache2-bin (2.4.12-2) ... Setting up libapache2-mpm-itk (2.4.7-02-1.1) ... Package apache2 is not configured yet. Will defer actions by package libapache2-mpm-itk. Setting up apache2-utils (2.4.12-2) ... Setting up apache2-data (2.4.12-2) ... Setting up apache2 (2.4.12-2) ... Enabling module mpm_event. Enabling module authz_core. Enabling module authz_host. Enabling module authn_core. Enabling module auth_basic. Enabling module access_compat. Enabling module authn_file. Enabling module authz_user. Enabling module alias. Enabling module dir. Enabling module autoindex. Enabling module env. Enabling module mime. Enabling module negotiation. Enabling module setenvif. Enabling module filter. Enabling module deflate. Enabling module status. Enabling conf charset. Enabling conf localized-error-pages. Enabling conf other-vhosts-access-log. Enabling conf security. Enabling conf serve-cgi-bin. Enabling site 000-default. info: mpm_prefork: No action required info: Executing deferred 'a2enmod mpm_itk' for package libapache2-mpm-itk ERROR: Module mpm_event is enabled - cannot proceed due to conflicts. It needs to be disabled first! ERROR: Could not enable dependency mpm_prefork for mpm_itk, aborting dpkg: error processing package apache2 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of libapache2-mod-php5: libapache2-mod-php5 depends on apache2 (= 2.4); however: Package apache2 is not configured yet. dpkg: error processing package libapache2-mod-php5 (--configure): dependency problems - leaving unconfigured [...] cheers, Andreas fusionforge-web_6.0.1-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: apache2 Source-Version: 2.4.16-1 We believe that the bug you reported is fixed in the latest version of apache2, 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 789...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefan Fritsch s...@debian.org (supplier of updated apache2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 02 Aug 2015 00:44:07 +0200 Source: apache2 Binary: apache2 apache2-data apache2-bin apache2-utils apache2-suexec-pristine apache2-suexec-custom apache2-doc apache2-dev apache2-dbg Architecture: source amd64 all Version: 2.4.16-1 Distribution: unstable Urgency: medium Maintainer: Debian Apache Maintainers debian-apa...@lists.debian.org Changed-By: Stefan Fritsch s...@debian.org Description: apache2- Apache HTTP Server apache2-bin - Apache HTTP Server (modules and other binary files) apache2-data - Apache HTTP Server (common files) apache2-dbg - Apache debugging symbols apache2-dev - Apache HTTP Server (development headers) apache2-doc - Apache HTTP Server (on-site documentation) apache2-suexec-custom - Apache HTTP Server configurable suexec program for mod_suexec apache2-suexec-pristine - Apache HTTP Server standard suexec program for mod_suexec apache2-utils - Apache HTTP Server (utility
Processed: Re: Bug#791165: libsdl-sge: library transition may be needed when GCC 5 is the default
Processing control commands: severity -1 normal Bug #791165 [src:libsdl-sge] libsdl-sge: library transition is needed when GCC 5 is the default Severity set to 'normal' from 'serious' -- 791165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791165 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#791165: libsdl-sge: library transition may be needed when GCC 5 is the default
Control: severity -1 normal On 08/02/2015 01:33 AM, Manuel A. Fernandez Montecelo wrote: 2015-08-01 22:36 GMT+01:00 Matthias Klose d...@debian.org: reopen 791165 severity 791165 serious tags 791165 + confirmed retitle 791165 libsdl-sge: library transition is needed when GCC 5 is the default thanks this is exactly what you should *not* do: libsdl-sge (030809dfsg-5) unstable; urgency=medium . * Bump Policy Standars-Version to 3.9.6 (no changes needed) * Rebuild against GCC-5 (Closes: #791165) * Enable parallel compilation with dh * Fix mispelling in d/copyright (detected by lintian) Please rename the library package (and add a proper library version). Why not? I already explained in the bug report why IMO we don't need a transition: - no packages in Debian use the functions sorry, didn't see this. please could you mention this with your next upload in the changelog and then close the issue? In addition: - supertransball2 is going to be NMUd in the libstdc++ transition anyway - ruby-sdl has 200 reported installations in popcon, supertransball 129, infon-viewer 20 (the risk of breakage is not high, and it's in very unimportant packages) - it looks to me that RT are not very happy with unnecessary / gratuitous transitions [1], which to me it reads as if they can avoid them unless really needed [1] https://lists.debian.org/debian-release/2015/07/msg00333.html Cheers. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777862: gbsplay: diff for NMU version 0.0.91-1.1
On Sat, Aug 01, 2015 at 01:02:15PM +0200, Sebastian Ramacher wrote: Dear maintainer, I've prepared an NMU for gbsplay (versioned as 0.0.91-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Hello Sebastian, thanks for the NMU! We've done a new upstream release of gbsplay that includes this patch as well as the fix for #715944. I've created a debian package for the new release as well (gbsplay_0.0.92-2). As I can't upload packages by myself, I've created a sponsoring request over on mentors.debian.net. Bug #793737 is the request for sponsorship bug for the new package. Could you have a look at it and perhaps sponsor the newer package? (I seem to have done something wrong during the upload to mentors, because in the mentor's packagelist gbsplay is listed as needs no sponsor - that's wrong, we need one :-) Regards, Christian -- Christian.Garbs.http://www.cgarbs.de Wieviele humorlose Menschen braucht man, um eine Glühbirne zu wechseln? Einen. signature.asc Description: Digital signature
Bug#791165: libsdl-sge: library transition may be needed when GCC 5 is the default
2015-08-01 22:36 GMT+01:00 Matthias Klose d...@debian.org: reopen 791165 severity 791165 serious tags 791165 + confirmed retitle 791165 libsdl-sge: library transition is needed when GCC 5 is the default thanks this is exactly what you should *not* do: libsdl-sge (030809dfsg-5) unstable; urgency=medium . * Bump Policy Standars-Version to 3.9.6 (no changes needed) * Rebuild against GCC-5 (Closes: #791165) * Enable parallel compilation with dh * Fix mispelling in d/copyright (detected by lintian) Please rename the library package (and add a proper library version). Why not? I already explained in the bug report why IMO we don't need a transition: - no packages in Debian use the functions In addition: - supertransball2 is going to be NMUd in the libstdc++ transition anyway - ruby-sdl has 200 reported installations in popcon, supertransball 129, infon-viewer 20 (the risk of breakage is not high, and it's in very unimportant packages) - it looks to me that RT are not very happy with unnecessary / gratuitous transitions [1], which to me it reads as if they can avoid them unless really needed [1] https://lists.debian.org/debian-release/2015/07/msg00333.html Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 792157 + pending Bug #792157 [flask-sqlalchemy] flask-sqlalchemy: Not installable: Depends: python-sqlalchemy ( 0.10) but 1.0.6+ds1-1 is in sid Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 792157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792157 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#794061: breeze: Breeze theme completely stopped working after the last upgrade
Hello, Could you check with ldd /usr/bin/qweborf. That'll shows which Qt library is used. It's python. It uses pyqt4. I am attaching the ldd output for subsurface, which is a C++ thing that uses Qt4. The Debian qt4-x11 build looks for plugins in /usr/lib/arch/qt4/plugins. That's why it loads the breeze style even when the path is not explicitly listed in QT_PLUGIN_PATH. I don't think it does load it without the env-var :) -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf/ linux-vdso.so.1 (0x7ffd5374e000) libdivecomputer.so.0 = /usr/lib/x86_64-linux-gnu/libdivecomputer.so.0 (0x7f8c9544f000) libxslt.so.1 = /usr/lib/x86_64-linux-gnu/libxslt.so.1 (0x7f8c9521) libxml2.so.2 = /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x7f8c94e45000) libmarblewidget.so.19 = /usr/lib/libmarblewidget.so.19 (0x7f8c9469c000) libzip.so.2 = /usr/lib/x86_64-linux-gnu/libzip.so.2 (0x7f8c9448b000) libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f8c9426f000) libsqlite3.so.0 = /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7f8c93fa2000) libgit2.so.22 = /usr/lib/x86_64-linux-gnu/libgit2.so.22 (0x7f8c93cd6000) libQtWebKit.so.4 = /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 (0x7f8c917f5000) libQtSvg.so.4 = /usr/lib/x86_64-linux-gnu/libQtSvg.so.4 (0x7f8c9159d000) libQtGui.so.4 = /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x7f8c908a7000) libQtNetwork.so.4 = /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 (0x7f8c90555000) libQtCore.so.4 = /usr/lib/x86_64-linux-gnu/libQtCore.so.4 (0x7f8c90065000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f8c8fe48000) libstdc++.so.6 = /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f8c8fb3b000) libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f8c8f83a000) libgcc_s.so.1 = /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f8c8f624000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f8c8f27a000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f8c8f076000) libicui18n.so.52 = /usr/lib/x86_64-linux-gnu/libicui18n.so.52 (0x7f8c8ec64000) libicuuc.so.52 = /usr/lib/x86_64-linux-gnu/libicuuc.so.52 (0x7f8c8e8e6000) libicudata.so.52 = /usr/lib/x86_64-linux-gnu/libicudata.so.52 (0x7f8c8d079000) liblzma.so.5 = /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f8c8ce56000) libastro.so.1 = /usr/lib/libastro.so.1 (0x7f8c8cc16000) libQtDBus.so.4 = /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 (0x7f8c8c999000) libQtXml.so.4 = /usr/lib/x86_64-linux-gnu/libQtXml.so.4 (0x7f8c8c752000) libQtScript.so.4 = /usr/lib/x86_64-linux-gnu/libQtScript.so.4 (0x7f8c8c298000) libQtDeclarative.so.4 = /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 (0x7f8c8bce) libphonon.so.4 = /usr/lib/x86_64-linux-gnu/libphonon.so.4 (0x7f8c8ba62000) libhttp_parser.so.2.1 = /usr/lib/x86_64-linux-gnu/libhttp_parser.so.2.1 (0x7f8c8b85a000) libssl.so.1.0.0 = /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x7f8c8b5f) libcrypto.so.1.0.0 = /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x7f8c8b18f000) libssh2.so.1 = /usr/lib/x86_64-linux-gnu/libssh2.so.1 (0x7f8c8af65000) librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7f8c8ad5d000) libXrender.so.1 = /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x7f8c8ab53000) libjpeg.so.62 = /usr/lib/x86_64-linux-gnu/libjpeg.so.62 (0x7f8c8a8f8000) libpng12.so.0 = /lib/x86_64-linux-gnu/libpng12.so.0 (0x7f8c8a6d1000) libgstapp-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libgstapp-1.0.so.0 (0x7f8c8a4c4000) libgstpbutils-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libgstpbutils-1.0.so.0 (0x7f8c8a29b000) libgstvideo-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0 (0x7f8c8a04e000) libgstaudio-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 (0x7f8c89dff000) libgstbase-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0 (0x7f8c89b9f000) libgstreamer-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 (0x7f8c8988e000) libgobject-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7f8c8963c000) libglib-2.0.so.0 = /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7f8c8932c000) libfontconfig.so.1 = /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x7f8c890ef000) libQtXmlPatterns.so.4 = /usr/lib/x86_64-linux-gnu/libQtXmlPatterns.so.4 (0x7f8c88a98000) libQtOpenGL.so.4 = /usr/lib/x86_64-linux-gnu/libQtOpenGL.so.4 (0x7f8c88795000)
Bug#776292: marked as done (ffrenzy: FTBFS with -Werror)
Your message dated Sat, 01 Aug 2015 07:48:51 + with message-id e1zlrxh-00058d...@franck.debian.org and subject line Bug#776292: fixed in ffrenzy 1.0.2~svn20150731-1 has caused the Debian Bug report #776292, regarding ffrenzy: FTBFS with -Werror 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.) -- 776292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ffrenzy Version: 1.0.2~svn20070530-5 Tags: patch Usertags: origin-ubuntu ubuntu-patch vivid In Ubuntu, we've applied the attached patch to achieve the following: * debian/patches/fix-werror-usage-and-aclocal-regen.patch: - Do not pass Werror by default to avoid build failures. - Fix the aclocal flags to not include. We thought you might be interested in doing the same. diff -Nru ffrenzy-1.0.2~svn20070530/debian/patches/fix-werror-usage-and-aclocal-regen.patch ffrenzy-1.0.2~svn20070530/debian/patches/fix-werror-usage-and-aclocal-regen.patch --- ffrenzy-1.0.2~svn20070530/debian/patches/fix-werror-usage-and-aclocal-regen.patch 1970-01-01 01:00:00.0 +0100 +++ ffrenzy-1.0.2~svn20070530/debian/patches/fix-werror-usage-and-aclocal-regen.patch 2015-01-24 23:55:42.0 +0100 @@ -0,0 +1,44 @@ +Description: Do not pass Werror by default to avoid build failures. + In addition to fixing the Werror usage, fix the aclocal flags to not include. +Author: Ben Collins bcoll...@ubuntu.com + +--- ffrenzy-1.0.2~svn20070530.orig/Makefile.am ffrenzy-1.0.2~svn20070530/Makefile.am +@@ -1,5 +1,3 @@ + SUBDIRS = src po tests data utils + +-ACLOCAL_AMFLAGS = -I m4 +- + EXTRA_DIST = config.rpath +--- ffrenzy-1.0.2~svn20070530.orig/configure ffrenzy-1.0.2~svn20070530/configure +@@ -4347,7 +4347,7 @@ $as_echo $am_cv_python_pyexecdir 6; + + + # setting CFLAGS +-CFLAGS=$CLAGS -Wall -Werror -g -O2 -finline-functions ++CFLAGS=$CLAGS -Wall -g -O2 -finline-functions + + # gettext stuff + +--- ffrenzy-1.0.2~svn20070530.orig/Makefile.in ffrenzy-1.0.2~svn20070530/Makefile.in +@@ -198,7 +198,6 @@ target_cpu = @target_cpu@ + target_os = @target_os@ + target_vendor = @target_vendor@ + SUBDIRS = src po tests data utils +-ACLOCAL_AMFLAGS = -I m4 + EXTRA_DIST = config.rpath + all: config.h + $(MAKE) $(AM_MAKEFLAGS) all-recursive +--- ffrenzy-1.0.2~svn20070530.orig/configure.ac ffrenzy-1.0.2~svn20070530/configure.ac +@@ -20,7 +20,7 @@ AC_CHECK_HEADERS + AM_PATH_PYTHON(2.3) + + # setting CFLAGS +-CFLAGS=$CLAGS -Wall -Werror -g -O2 -finline-functions ++CFLAGS=$CLAGS -Wall -g -O2 -finline-functions + + # gettext stuff + AM_GNU_GETTEXT_VERSION(0.16.1) diff -Nru ffrenzy-1.0.2~svn20070530/debian/patches/series ffrenzy-1.0.2~svn20070530/debian/patches/series --- ffrenzy-1.0.2~svn20070530/debian/patches/series 2013-08-03 02:24:22.0 +0200 +++ ffrenzy-1.0.2~svn20070530/debian/patches/series 2015-01-24 12:45:15.0 +0100 @@ -1,2 +1,3 @@ fix-ffrenzy-menu-path.patch fix-libm-underlinkage.patch +fix-werror-usage-and-aclocal-regen.patch ---End Message--- ---BeginMessage--- Source: ffrenzy Source-Version: 1.0.2~svn20150731-1 We believe that the bug you reported is fixed in the latest version of ffrenzy, 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 776...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul van Tilburg pau...@debian.org (supplier of updated ffrenzy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 31 Jul 2015 21:59:28 +0200 Source: ffrenzy Binary: ffrenzy Architecture: source amd64 Version: 1.0.2~svn20150731-1 Distribution: unstable Urgency: medium Maintainer: Paul van Tilburg pau...@debian.org Changed-By: Paul van Tilburg pau...@debian.org Description: ffrenzy- multiplayer platform game with dwarfs fighting with/for food Closes: 751442 776292 Changes: ffrenzy (1.0.2~svn20150731-1) unstable; urgency=medium . * New upstream snapshot (closes: #751442, #776292) * debian/patches: drop fix-ffrenzy-menu-path.patch and fix-libm-underlinkage.patch; fixed upstream * debian/control: bump standards version to 3.9.6; remove old
Bug#794313: dahdi: DAHDI-modules build fails
Package: dahdi
Version: 1:2.10.2-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
After installing debain testing weekly build (from 2015-07-27) and installing
DAHDI modules:
sudo apt-get install module-assistant
sudo module-assistant auto-install dahdi
I get this: Build of the package dahdi-source failed!
Build log follows.
dh clean
dh_testdir
debian/rules override_dh_auto_clean
make[1]: Entering directory '/usr/src/modules/dahdi'
rm -f include/dahdi/version.h
rm -f dahdi/include/version.h
[ ! -f Makefile ] || /usr/bin/make dist-clean || true
make[2]: Entering directory '/usr/src/modules/dahdi'
/usr/bin/make -C /lib/modules/4.0.0-2-686-pae/build
SUBDIRS=/usr/src/modules/dahdi/drivers/dahdi
DAHDI_INCLUDE=/usr/src/modules/dahdi/include DAHDI_MODULES_EXTRA=
HOTPLUG_FIRMWARE=yes clean
make[3]: Entering directory '/usr/src/linux-headers-4.0.0-2-686-pae'
make[3]: Leaving directory '/usr/src/linux-headers-4.0.0-2-686-pae'
/usr/bin/make -C drivers/dahdi/firmware clean
make[3]: Entering directory '/usr/src/modules/dahdi/drivers/dahdi/firmware'
rm -f dahdi-fw-*.o
make[3]: Leaving directory '/usr/src/modules/dahdi/drivers/dahdi/firmware'
/usr/bin/make -C /lib/modules/4.0.0-2-686-pae/build
M='/usr/src/modules/dahdi/drivers/dahdi/oct612x' clean
make[3]: Entering directory '/usr/src/linux-headers-4.0.0-2-686-pae'
make[3]: Leaving directory '/usr/src/linux-headers-4.0.0-2-686-pae'
make[3]: Entering directory '/usr/src/modules/dahdi/drivers/dahdi/firmware'
rm -f dahdi-fw-*.o
rm -f dahdi-fw-*.bin
rm -f dahdi-fw-*.tar.gz
rm -f dahdi-fwload-*.tar.gz
rm -f make_firmware_object
make[3]: Leaving directory '/usr/src/modules/dahdi/drivers/dahdi/firmware'
make[2]: Leaving directory '/usr/src/modules/dahdi'
make[1]: Leaving directory '/usr/src/modules/dahdi'
dh_clean
/usr/bin/make -f debian/rules kdist_clean kdist_config binary-modules
make[1]: Entering directory '/usr/src/modules/dahdi'
dh clean
dh_testdir
debian/rules override_dh_auto_clean
make[2]: Entering directory '/usr/src/modules/dahdi'
rm -f include/dahdi/version.h
rm -f dahdi/include/version.h
[ ! -f Makefile ] || /usr/bin/make dist-clean || true
make[3]: Entering directory '/usr/src/modules/dahdi'
/usr/bin/make -C /lib/modules/4.0.0-2-686-pae/build
SUBDIRS=/usr/src/modules/dahdi/drivers/dahdi
DAHDI_INCLUDE=/usr/src/modules/dahdi/include DAHDI_MODULES_EXTRA=
HOTPLUG_FIRMWARE=yes clean
make[4]: Entering directory '/usr/src/linux-headers-4.0.0-2-686-pae'
Makefile:10: *** mixed implicit and normal rules: deprecated syntax
make[4]: Leaving directory '/usr/src/linux-headers-4.0.0-2-686-pae'
/usr/bin/make -C drivers/dahdi/firmware clean
make[4]: Entering directory '/usr/src/modules/dahdi/drivers/dahdi/firmware'
rm -f dahdi-fw-*.o
make[4]: Leaving directory '/usr/src/modules/dahdi/drivers/dahdi/firmware'
/usr/bin/make -C /lib/modules/4.0.0-2-686-pae/build
M='/usr/src/modules/dahdi/drivers/dahdi/oct612x' clean
make[4]: Entering directory '/usr/src/linux-headers-4.0.0-2-686-pae'
Makefile:10: *** mixed implicit and normal rules: deprecated syntax
make[4]: Leaving directory '/usr/src/linux-headers-4.0.0-2-686-pae'
make[4]: Entering directory '/usr/src/modules/dahdi/drivers/dahdi/firmware'
rm -f dahdi-fw-*.o
rm -f dahdi-fw-*.bin
rm -f dahdi-fw-*.tar.gz
rm -f dahdi-fwload-*.tar.gz
rm -f make_firmware_object
make[4]: Leaving directory '/usr/src/modules/dahdi/drivers/dahdi/firmware'
make[3]: Leaving directory '/usr/src/modules/dahdi'
make[2]: Leaving directory '/usr/src/modules/dahdi'
dh_clean
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_/4.0.0-2-686-pae/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in}
${templ%.modules.in}.backup 2/dev/null || true; \
sed -e 's/##KVERS##/4.0.0-2-686-pae/g ;s/#KVERS#/4.0.0-2-686-pae/g ;
s/_KVERS_/4.0.0-2-686-pae/g ; s/##KDREV##/4.0.8-2/g ; s/#KDREV#/4.0.8-2/g ;
s/_KDREV_/4.0.8-2/g ' $templ ${templ%.modules.in}; \
done
dh_testdir
dh_testroot
dh_prep
#cp -a /usr/src/modules/dahdi/debian/generated/* .
make modules KERNEL_SOURCES=/lib/modules/4.0.0-2-686-pae/build
MODVERSIONS=detect KERNEL=linux-4.0.0-2-686-pae
make[2]: Entering directory '/usr/src/modules/dahdi'
make -C /lib/modules/4.0.0-2-686-pae/build
SUBDIRS=/usr/src/modules/dahdi/drivers/dahdi
DAHDI_INCLUDE=/usr/src/modules/dahdi/include DAHDI_MODULES_EXTRA=
HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m
make[3]: Entering directory '/usr/src/linux-headers-4.0.0-2-686-pae'
Makefile:10: *** mixed implicit and normal rules: deprecated syntax
CC [M] /usr/src/modules/dahdi/drivers/dahdi/dahdi-base.o
In file included from
/usr/src/linux-headers-4.0.0-2-common/include/linux/fs.h:7:0,
from
/usr/src/linux-headers-4.0.0-2-common/include/linux/proc_fs.h:8,
from /usr/src/modules/dahdi/drivers/dahdi/dahdi-base.c:41:
Bug#778112: marked as done (schroot: ftbfs with GCC-5)
Your message dated Sat, 01 Aug 2015 10:10:14 +0200 with message-id 55bc7ee6.2000...@debian.org and subject line now fixed in gcc-5 5.2.1-14 has caused the Debian Bug report #778112, regarding schroot: ftbfs with GCC-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 778112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:schroot Version: 1.6.10-1 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/schroot_1.6.10-1_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] 6: - regex_error 6: 6: 6: 2) test: test_run_parts::test_run (E) 6: uncaught exception of type std::regex_error 6: - regex_error 6: 6: 6: 3) test: test_run_parts::test_run3 (E) 6: uncaught exception of type std::regex_error 6: - regex_error 6: 6: 6/8 Test #6: sbuild-run-parts .***Failed0.01 sec test 7 Start 7: schroot-base-option-action 7: Test command: /«PKGBUILDDIR»/debian/build/test/schroot-base-option-action 7: Test timeout computed to be: 9.99988e+06 7: 7: 7: 7: OK (8 tests) 7: 7: 7/8 Test #7: schroot-base-option-action ... Passed0.01 sec test 8 Start 8: cleanup-test-data 8: Test command: /«PKGBUILDDIR»/debian/build/test/cleanup-test-data 8: Test timeout computed to be: 9.99988e+06 8/8 Test #8: cleanup-test-data Passed0.01 sec 75% tests passed, 2 tests failed out of 8 Total Test time (real) = 0.17 sec The following tests FAILED: Errors while running CTest 2 - sbuild-chroot-chroot (Failed) 6 - sbuild-run-parts (Failed) make[2]: *** [test] Error 8 Makefile:117: recipe for target 'test' failed make[2]: Leaving directory '/«PKGBUILDDIR»/debian/build' make[1]: *** [install-arch] Error 2 debian/rules:83: recipe for target 'install-arch' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [binary-arch] Error 2 debian/rules:39: recipe for target 'binary-arch' failed dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 ---End Message--- ---BeginMessage--- the regex issue is now fixed in the default GCC in unstable. confirmed by a non-change rebuild of schroot.---End Message---
Bug#793888: ui-gxmlcpp includes autogenerated files that cannot be rebuilt from source
Hi Johannes! On Di, 2015-07-28 at 17:31 +0200, Johannes Schauer wrote: Source: ui-gxmlcpp Version: 1.4.3-1 Severity: serious Justification: Policy 2.2.1 (...) the source package for ui-gxmlcpp includes a ./configure and ../aclocal.m4 without including their source. If ./configure and ../aclocal.m4 are removed, then the package cannot be built anymore. For example, the current aclocal.m4 contains parts of ui-auto but ui-gxmlcpp does not build depend on that package. Please add the missing bits so that this source package can be built from source again and does not require autogenerated scripts like ../configure and ./aclocal.m4. Ok, switching to autoreconf (with b-d on ui-auto) is an option I will consider. Could you ponder a bit more why you think this is a policy violation? It seems a bit harsh considering how autotools work, and everything can be rebuild within Debian/main -- but maybe I missed something ;). Thanks! Stephan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794316: can't unlock desktop
Package: gdm3 Version: 3.14.1-7 Severity: serious This occurred on a jessie system using the default GNOME 3 desktop. My laptop screen had been locked for a while. I typed the password and nothing happened. After a few seconds, the screen went blank again. Looking at journalctl I observed: gdm-session-worker[23803]: 5AccountsService: Failed to monitor logind session changes: Too many open files I looked in Google and I came across some instructions at https://bugzilla.redhat.com/show_bug.cgi?id=1081004 and I tried them: # loginctl list-sessions SESSIONUID USER SEAT 150 1000 daniel seat0 352 1000 daniel 2 sessions listed. # loginctl show-session 150 Id=150 Name=daniel Timestamp=Fri 2015-07-31 08:16:35 CEST TimestampMonotonic=58211655247 VTNr=7 Display=:0 Remote=no Service=gdm-password Scope=session-150.scope Leader=9094 Audit=150 Type=x11 Class=user Active=yes State=active IdleHint=yes IdleSinceHint=1438349828896720 IdleSinceHintMonotonic=68154456351 # loginctl unlock-session 150 The unlock-session command unlocked the screensaver and I was able to see the desktop again. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794316: more details
# lsof -n | wc -l lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. 92842 # lsof -n | tr -s ' ' | cut -f2 -d' ' | uniq -c | sort -n | tail -10 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. **count PID** 1256 9348 1265 9189 2023 2543 2044 9318 2295 10971 2600 2899 3495 9094 9180 11168 10115 9267 12894 10422 # ps -p 10422,9267,11168 PID TTY TIME CMD 9267 ?00:13:34 gnome-shell 10422 pts/105:36:47 iceweasel 11168 pts/300:22:30 icedove These are processes that I use all the time and I haven't had problems like this before. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794320: main option prdr_enable unknown
Package: exim4-config Version: 4.86-1 Severity: serious After updating an old testing system I get this: Setting up exim4-config (4.86-1) ... 2015-08-01 15:04:52 Exim configuration error in line 140 of /var/lib/exim4/config.autogenerated.tmp: main option prdr_enable unknown Invalid new configfile /var/lib/exim4/config.autogenerated.tmp, not installing /var/lib/exim4/config.autogenerated.tmp to /var/lib/exim4/config.autogenerated dpkg: error processing package exim4-config (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: exim4-config prdr_enable is indeed contained in /etc/exim4/conf.d/main/02_exim4-config_options -- Package-specific info: Exim version 4.82_1-5b7a7c0-XX #3 built 22-Jul-2014 16:32:17 Copyright (c) University of Cambridge, 1995 - 2013 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2013 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to generate # exim configuration macros for the configuration file. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='smarthost' dc_other_hostnames='' dc_local_interfaces='127.0.0.1 ; ::1' dc_readhost='' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='mail.wrar.name' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='false' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' mailname:sabine.wrar.name -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.0-wrar-sabine-1+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages exim4-config depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.57 exim4-config recommends no packages. exim4-config suggests no packages. -- Configuration Files: /etc/exim4/passwd.client [Errno 13] Отказано в доступе: u'/etc/exim4/passwd.client' -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
