Bug#1072244: Segmentation fault on startup

Package: wxglade Version: 1.0.5+repack-2 Severity: grave Tags: patch Wxglade crashes with a segmentation fault on startup. See below for the output. This is fixed upstream by this commit: https://github.com/wxGlade/wxGlade/commit/05943a8374a24b862e76f03643a775c09582703f I also attached this as

Bug#937184: Python 3 port of offlineimap underway

There is now a Python 3 port of offlineimap underway: https://github.com/OfflineIMAP/offlineimap/issues/670 AFAICS it looks promising. Please wait with removing from unstable. Gaudenz -- PGP: 836E 4F81 EFBB ADA7 0852 79BF A97A 7702 BAF9 1EF5 signature.asc Description: PGP signature

Bug#919898: Bug #919898 in ceph marked as pending

Control: tag -1 pending Hello, Bug #919898 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#919898: Bug #919898 in ceph marked as pending

Control: tag -1 pending Hello, Bug #919898 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#846950: Please explain what broke nfs-utils for you (Debian Bug #846950)

Control: severity -1 normal Hi Felix I was working through the list of release critical bugs on nfs-utils and looked at this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846950 where you increased the severity to "grave" some time ago. But you did not explain how this broke

Bug#901462: Turning off CONFIG_ACPI_DSDT is not enough

Hi I tried to work on this during the BSP in Bern. While I think that compatibility with QEMU 1.3 and older is no longer needed in Debian I failed to compile the package with CONFIG_ACPI_DSDT turned off. To me it looks like this is rather a runtime than a compile time option and the hex

Bug#891753: Will be fixed in Django 1.11.17

I looked into this issue at the BSP in Bern and it runs out that currently only the testsuite for Python 3.7 on Django 1.11.16 fails. All other Python versions as well as Django 2.1.x in experimental are fine. The next upstream minor release in the 1.11.x series will add Python 3.7

Bug#909312: Please provide some more information for bug #909312

Control: severity -1 important Control: tags -1 +moreinfo Hi Nicola I had a look at your bug report against initramfs-tools today. To me this looks rather like a bug in the 4.16 kernel specific to your setup. But without additional information about the exact configuration of the system

Bug#897338: Downgrading severity of 897338

Control: -1 severity normal As this is apparently does not happen without virtualbox and is fixed by installing virtualbox-guest-dkms and/or virtualbox-guest-x11 I'm downgrading this bug to normal. I let the SDDM maintainers decide if this is a bug at all or if this is expected if the

Bug#892859: NMU for 2.4.2-0.1

Hi Jeremy and Guido I created an NMU to fix #904635 and #892859 by uploading the new upstream version 2.4.2 and fixing the autopkgtests to run the new pytest based testsuite. This also contains a patch to remove a dependency on pytest-relaxed from the tests. This dependency is not packaged

Bug#888133: virt-manager builds successfully, is there still a bug in libvirt?

As virt-manager 1.5 is now in unstable and testing and builds fine, I think this bug can be closed. I'm unsure why it got reassigned to libvirt and there is unfortunately no reasoning in the bug log. I don't think there is a bug in libvirt which needs fixing. If you agree, please close this

Bug#913599: Bug #913599 in ceph marked as pending

Control: tag -1 pending Hello, Bug #913599 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#913599: Bug #913599 in ceph marked as pending

Control: tag -1 pending Hello, Bug #913599 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#913599: Bug #913599 in ceph marked as pending

Control: tag -1 pending Hello, Bug #913599 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#913599: Bug #913599 in ceph marked as pending

Control: tag -1 pending Hello, Bug #913599 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#913909: Bug #913909 in ceph marked as pending

Control: tag -1 pending Hello, Bug #913909 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#913600: Bug #913600 in ceph marked as pending

Control: tag -1 pending Hello, Bug #913600 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#913600: Bug #913600 in ceph marked as pending

Control: tag -1 pending Hello, Bug #913600 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#913909: [Ceph-maintainers] Bug#913909: Bug#913909: ceph: FTBFS on i386 and mipsel (regression)

Hi Salvatore Bonaccorso writes: Hi Gaudenz, and hi James, On Mon, Nov 19, 2018 at 03:48:14PM +0100, Gaudenz Steinlin wrote: James Page writes: > https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/ceph/tree/debian/patches?h=ubuntu/xenial > I think I hit the same issue in

Bug#913601: Bug #913601 in ceph marked as pending

Control: tag -1 pending Hello, Bug #913601 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#913909: [Ceph-maintainers] Bug#913909: Bug#913909: ceph: FTBFS on i386 and mipsel (regression)

James Page writes: https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/ceph/tree/debian/patches?h=ubuntu/xenial I think I hit the same issue in Ubuntu a while back for which I picked 3 rocksdb patches - see above URL - 000*.patch. Thanks James. It looks like these patches actually

Bug#913909: [Ceph-maintainers] Bug#913909: ceph: FTBFS on i386 and mipsel (regression)

Salvatore Bonaccorso writes: Hi Gaudenz, On Sat, Nov 17, 2018 at 05:28:18PM +0100, Gaudenz Steinlin wrote: Salvatore Bonaccorso writes: > Hi, On Fri, Nov 16, 2018 at 09:00:06PM +0100, Salvatore > Bonaccorso wrote: > > Source: ceph Version: 10.2.11-1 Sever

Bug#913601: Bug #913601 in ceph marked as pending

Control: tag -1 pending Hello, Bug #913601 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#913909: [Ceph-maintainers] Bug#913909: ceph: FTBFS on i386 and mipsel (regression)

Salvatore Bonaccorso writes: Hi, On Fri, Nov 16, 2018 at 09:00:06PM +0100, Salvatore Bonaccorso wrote: Source: ceph Version: 10.2.11-1 Severity: serious Justification: FTBFS Control: affects -1 release.debian.org,security.debian.org Hi Gaudenz, The security update for ceph released as

Bug#913601: [Ceph-maintainers] Bug#913601: ceph: FTBFS on mips/el: /usr/include/c++/8/bits/atomic_base.h:304: undefined reference to `__atomic_fetch_sub_8'

Hi Emilio Pozuelo Monfort writes: Your package failed to build on mips/el: /usr/bin/ld: CMakeFiles/ceph-mgr.dir/mgr/DaemonServer.cc.o: in function `RefCountedObject::~RefCountedObject()': /usr/include/c++/8/bits/atomic_base.h:396: undefined reference to `__atomic_load_8' /usr/bin/ld:

Bug#913600: [Ceph-maintainers] Bug#913600: ceph: bd-uninst on several architectures: libboost-context1.67-dev not available

Hi Emilio Pozuelo Monfort writes: Your package can no longer be built on several architectures, as libboost-context is not built everywhere. Possible solutions would be: 1) Make that build-dep optional I don't think that's possible. Or do you have any pointers how Ceph could be built

Bug#896400: Bug #896400 in ceph marked as pending

Control: tag -1 pending Hello, Bug #896400 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#867465: Bug #867465 in ceph marked as pending

Control: tag -1 pending Hello, Bug #867465 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#896400: Bug #896400 in ceph marked as pending

Control: tag -1 pending Hello, Bug #896400 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#867465: Bug #867465 in ceph marked as pending

Control: tag -1 pending Hello, Bug #867465 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#862075: tagged as pending

by 'git-post-receive-tag-pending-commitmsg' hook). --- commit a12798af80d903bbaa18d174a98ac5c6ae8b1204 Author: Gaudenz Steinlin <gaud...@debian.org> Date: Thu May 11 23:09:24 2017 +0200 Add fix-init-system-detection.patch This replaces the static init system detection b

Bug#862075: [Ceph-maintainers] Bug#862075: ceph-detect-init: Platform is not supported.: debian 9.0

The first version of the patch did not work as expected. Attached is a fixed version. Back to building and testing ... bug_862075_v2.debdiff Description: Binary data Gaudenz Steinlin <gaud...@debian.org> writes: > Control: forwarded -1 http://tracker.ceph.com/issues/19884 > C

Bug#862075: [Ceph-maintainers] Bug#862075: ceph-detect-init: Platform is not supported.: debian 9.0

Control: forwarded -1 http://tracker.ceph.com/issues/19884 Control: tags -1 +patch Simon McVittie writes: > On Mon, 08 May 2017 at 11:16:48 +0200, Pim van den Berg wrote: >> As you can see ceph assumes our init system is sysvinit in stretch, while it >> is systemd. > > No, our

Bug#809669: RC Bug NMU diff

Hi I uplaoded an NMU to unstable to fix this bug. I mostly used the debdiff prepared by Louis Bouchard but fixed the version number to be 0.93.1+nmu1 instead of 0.93.2 and actually fixed the systemd unit in the way proposed in this bug. The debdiff attached to the bug missed the critical

Bug#850906: tagged as pending

by 'git-post-receive-tag-pending-commitmsg' hook). --- commit e44a30d304059fbf94d68623e10f296f4d0284fb Author: Gaudenz Steinlin <gaud...@debian.org> Date: Wed Jan 11 09:39:36 2017 +0100 Disable running dh_auto_install with parallel jobs There seems to be a race condition i

Bug#850906: [Ceph-maintainers] Bug#850906: ceph FTBFS on armel, libtool/linker related issues.

peter green writes: > Package: ceph > Version: 10.2.5-5 > Severity: serious > x-debbugs-cc: debian-...@lists.debian.org > > The most recent upload of ceph fixed the build on most architectures but > unfortunately armel is still failing. > > libtool: relink: g++ -fPIC

Bug#849657: [Ceph-maintainers] Bug#849657: ceph: FTBFS on mips(el): g++: virtual memory exhausted: Cannot allocate memory

Aurelien Jarno <aurel...@aurel32.net> writes: > On 2017-01-05 14:00, Gaudenz Steinlin wrote: >> >> Hi >> >> Aurelien Jarno <aurel...@aurel32.net> writes: >> >> > On 2016-12-30 10:06, Emilio Pozuelo Monfort wrote: >> >> On 29/12

Bug#849657: [Ceph-maintainers] Bug#849657: ceph: FTBFS on mips(el): g++: virtual memory exhausted: Cannot allocate memory

Emilio Pozuelo Monfort <po...@debian.org> writes: > On 05/01/17 14:00, Gaudenz Steinlin wrote: >> >> Hi >> >> Aurelien Jarno <aurel...@aurel32.net> writes: >> >>> On 2016-12-30 10:06, Emilio Pozuelo Monfort wrote: >>>> On 29/

Bug#849660: tagged as pending

by 'git-post-receive-tag-pending-commitmsg' hook). --- commit eeff8d65bad5c8e2bdf966bfe725b75d63aa9bc5 Author: Gaudenz Steinlin <gaud...@debian.org> Date: Tue Dec 27 21:35:47 2016 +0100 Use -mfloat-abi=softfp on armel for NEON plugin Closes: #849660

Bug#849657: [Ceph-maintainers] Bug#849657: ceph: FTBFS on mips(el): g++: virtual memory exhausted: Cannot allocate memory

Hi Aurelien Jarno <aurel...@aurel32.net> writes: > On 2016-12-30 10:06, Emilio Pozuelo Monfort wrote: >> On 29/12/16 20:56, Gaudenz Steinlin wrote: > > The problem is indeed a memory issue, not that the buildd doesn't have > enough memory, but just that you can alloc

Bug#849660: [Ceph-maintainers] Bug#849660: ceph: FTBFS on armel: error: field 'result' has incomplete type 'std::promise'

Hi Emilio Emilio Pozuelo Monfort writes: > Source: ceph > Version: 10.2.5-2 > Severity: serious > > Your package failed to build on armel: > > utilities/backupable/backupable_db.cc:297:30: error: field 'result' has > incomplete type 'std::promise' > std::promise result;

Bug#849657: [Ceph-maintainers] Bug#849657: ceph: FTBFS on mips(el): g++: virtual memory exhausted: Cannot allocate memory

Hi Emilio Emilio Pozuelo Monfort writes: > Source: ceph > Version: 10.2.5-2 > Severity: serious > > Your package failed to build on mips/el: > > g++ -DHAVE_CONFIG_H -I. -D__CEPH__ -D_FILE_OFFSET_BITS=64 -D_THREAD_SAFE > -D__STDC_FORMAT_MACROS -D_GNU_SOURCE >

Bug#840383: ceph: Mon crash on startup

Control: severity -1 normal Control: tags -1 unreproducible Hi Thanks for your bugreport. Sorry that it took so long to get back to you. The ceph maintenance team is currently understaffed and struggeling to keep up with the work. Hans Grobler writes: > Package: ceph >

Bug#844937: owncloud-client at risk of not being in stretch [was Re: Bug#844937: fixed in owncloud-client 2.2.4+dfsg-2]

Hi Sébastien Thanks for the heads up. I'm mostly just doing backports uploads. So if Sandro disagrees, go for his opinion. Sébastien Villemot writes: > Dear owncloud-client maintainers, > > owncloud-client is scheduled for removal from testing on 2016-12-21, > because

Bug#844701: Fix for 844701 breaks installation of valgrind

reopen -1 retitle -1 dpkg-maintscript-helper: fails if no version is given Hi The fix for #844701 included in the upload from earlier today breaks the installation of valgrind. Preparing to unpack .../valgrind_1%3a3.12.0-1_amd64.deb ... dpkg-maintscript-helper: error: dpkg: error: version ''

Bug#839138: Ceph maintainership status

Hi Adrian Thanks for the heads up. We were probably all a bit burried in work and neglected ceph a bit too much. James Page writes: > Hi Adrian > > On Mon, 17 Oct 2016 at 20:34 Adrian Bunk wrote: > >> Hi, >> >> first of all thanks for your past work on

Bug#815880: Fails to update /etc/resolv.conf with network-manager 1.1.90

Package: dnssec-trigger Version: 0.13~svn685-4+b1 Severity: grave Tags: patch The /usr/lib/dnssec-trigger/dnssec-trigger-script fails to update /etc/resolv.conf with the version of network-manager now in testing and unstable. The problem is that calls to client.get_manager_running() return False

Bug#803669: Breaks QProcess in owncloud-client tests on mips an mipsel

Hi Dmitry Shachnev <mity...@debian.org> writes: > Hi Gaudenz, > > On Wed, 04 Nov 2015 15:51:40 +0100, Gaudenz Steinlin wrote: >> The testcase from the upstream bug report does not work on the porter >> box with 5.5.1+dfsg-6 as well. So this fix is either not appli

Bug#803669: Breaks QProcess in owncloud-client tests on mips an mipsel

Gaudenz Steinlin <gaud...@debian.org> writes: > Lisandro Damián Nicanor Pérez Meyer <perezme...@gmail.com> writes: > >> forwarded 803669 https://bugreports.qt.io/browse/QTBUG-49168 >> tag 803669 upstream >> thanks >> >> On Monday 02 Novembe

Bug#803669: Breaks QProcess in owncloud-client tests on mips an mipsel

Lisandro Damián Nicanor Pérez Meyer <perezme...@gmail.com> writes: > forwarded 803669 https://bugreports.qt.io/browse/QTBUG-49168 > tag 803669 upstream > thanks > > On Monday 02 November 2015 23:07:19 Gaudenz Steinlin wrote: > [snip] >> If I read the strace outpu

Bug#803669: Breaks QProcess in owncloud-client tests on mips an mipsel

Source: qtbase-opensource-src Version: 5.5.0+dfsg-3 Severity: serious Setting the severity of this bug to serious because it causes another package to fail to build from source. This version of Qt breaks the tests of owncloud-sync on mips and mipsel. Test also break when compiling version

Bug#801477: tagged as pending

by 'git-post-receive-tag-pending-commitmsg' hook). --- commit 2d14828a0914964316c9977f3f60418496fe6a2b Author: Gaudenz Steinlin <gaud...@debian.org> Date: Mon Oct 12 16:25:21 2015 +0200 Add upstream patch to fix building without libatomic-ops Closes: #801477

Bug#801477: [Ceph-maintainers] Bug#801477: ceph: FTBFS on armel: common/RWLock.h:29:11: error: 'atomic_t' does not name a type

Hi Emilio Pozuelo Monfort writes: > Source: ceph > Version: 0.80.10-1 > Severity: serious > > Hi, > > Thanks for the upload to fix the FTBFS in sid. Unfortunately this still failed > on armel: > > Excerpt from the log: > > In file included from common/HeartbeatMap.h:26:0, >

Bug#795178: tagged as pending

by 'git-post-receive-tag-pending-commitmsg' hook). --- commit c8b478a038cd879f0088a5a462d98495f9257c2e Author: Gaudenz Steinlin <gaud...@debian.org> Date: Tue Oct 6 14:37:06 2015 +0200 Add upstream patch to fix compiling with boost 1.58 Closes: #795178

Bug#795178: fixed in ceph 0.94.3-1

Emilio Pozuelo Monfort writes: > [ explicit Cc's as this goes to a list that seems to be moderated... ] > > On Sat, 26 Sep 2015 16:39:46 +0200 Emilio Pozuelo Monfort > wrote: >> Can we have this fixed in unstable as well? ceph currently fails to build >>

Bug#791445: [Ceph-maintainers] Bug#791445: ceph: uses bundled libjerasure library again

severity 791445 normal retitle 791445 Use system libjerasure with CPU optimizations thanks James Page james.p...@ubuntu.com writes: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/07/15 18:23, James Page wrote: The ceph Debian package git repository only contains very little

Bug#791445: [Ceph-maintainers] Bug#791445: Bug#791445: ceph: uses bundled libjerasure library again

[ Adding the jerasure maintainer to the CC ] Hi Loic Dachary l...@dachary.org writes: Hi, I'm co-maintainer of both jerasure and ceph. If the Debian jerasure package was orphaned, I would be happy to step in and maintain it as a standalone package. Jerasure was packaged without dialog

Bug#778618: [PKG-Openstack-devel] Bug#778618: Bug#778618: This patch is not enough

Moritz Muehlenhoff j...@inutil.org writes: On Fri, Feb 27, 2015 at 10:18:46PM +, Paul McMillan wrote: If you agree that the linked github patch is complete, I can do an upload if you lack the time to do so yourself. I can understand that sensitive security issues are involved, but a

Bug#778618: [PKG-Openstack-devel] Bug#778618: This patch is not enough

Thomas Goirand z...@debian.org writes: Hi, I'm not supposed to disclose too much yet, but I have to write in this bug still. The provided patch is *not enough* and the issue is still being discussed upstream. So I can't just patch novnc and be gone with it... I'll update this package as

Bug#773354: please add breaks: live-tools ( 4.0.1-1)

Andreas Henriksson andr...@fatal.se writes: Hello Gaudenz Steinlin! On Mon, Feb 02, 2015 at 10:25:07PM +0100, Gaudenz Steinlin wrote: Hi Andreas My NMU was in no way meant to critice your maintenance of util-linux or to attack you. It's just that in the current phase of the release

Bug#773354: please add breaks: live-tools ( 4.0.1-1)

Hi Andreas Andreas Henriksson andr...@fatal.se writes: Hi! On Thu, Feb 05, 2015 at 01:46:22PM +0100, Gaudenz Steinlin wrote: [...] I'll try to find a list of other packages affected by the live-tools bug and submit bug reports. Fwiw, I noticed live-tools is targeted for auto-removal

Bug#775795: Patch to use /usr/sbin/service in Debian service provider

Hi Gaudenz Steinlin gaud...@debian.org writes: Stephen Gran sg...@debian.org writes: Hi, This one time, at band camp, Stig Sandbeck Mathisen said: Hello, Thanks for the patch. It looks like it has the correct solution, using the Debian abstraction layer over the alternative init

Bug#775795: Patch to use /usr/sbin/service in Debian service provider

2eae3a2a71de50889535f0e917ac6f4ecaeb8975 Mon Sep 17 00:00:00 2001 From: Gaudenz Steinlin gaud...@soziologie.ch Date: Sat, 31 Jan 2015 16:09:08 +0100 Subject: [PATCH] Use /usr/sbin/service in Debian service provider Closes: #775795 --- .../0004-debian-service-provider-use-service.patch | 56

Bug#773354: please add breaks: live-tools ( 4.0.1-1)

you would appreciate this help. Andreas Henriksson andr...@fatal.se writes: Hello Gaudenz Steinlin. On Mon, Feb 02, 2015 at 11:25:55AM +0100, Gaudenz Steinlin wrote: Of course a fix in util-linux can't solve problems resulting from other packages. All packages that call update-initramfs

Bug#773354: please add breaks: live-tools ( 4.0.1-1)

Andreas Henriksson andr...@fatal.se writes: Hello Gaudenz Steinlin. On Sun, Feb 01, 2015 at 12:31:24PM +0100, Gaudenz Steinlin wrote: [...] - The version of live-tools in wheezy does not depend on initramfs-tools, but calls the original version of update-initramfs (diverted) without

Bug#773354: please add breaks: live-tools ( 4.0.1-1)

On 12/17/2014 6:27 PM, Daniel Baumann wrote: On 12/17/14 23:50, Andreas Henriksson wrote: I'd guess (without having looked) because live-tools diverts update-initramfs? no, it's about uptime. What? No this is not about uptime at all. The uptime diversion is a different bug. What

Bug#773354: please add breaks: live-tools ( 4.0.1-1)

Gaudenz Steinlin gaud...@debian.org writes: On 12/17/2014 6:27 PM, Daniel Baumann wrote: On 12/17/14 23:50, Andreas Henriksson wrote: I'd guess (without having looked) because live-tools diverts update-initramfs? no, it's about uptime. What? No this is not about uptime at all

Bug#775795: Patch to use /usr/sbin/service in Debian service provider

2001 From: Gaudenz Steinlin gaud...@soziologie.ch Date: Sat, 31 Jan 2015 16:09:08 +0100 Subject: [PATCH] Use /usr/sbin/service in Debian service provider Closes: #775795 --- .../0004-debian-service-provider-use-service.patch | 56 ++ debian/patches/series

Bug#774383: init script fails to start daemon

Package: designate-api Version: 2014.1-15 Severity: grave Tags: patch The designate-api service fails to start because the NAME variable in the init script is set to -api instead of designate-api. This is due to using a substitution variable $SERVICE_NAME which is not defined. The variable

Bug#773504: NMU patch on top of current GIT

Hi Please find attached the patch on top of the current git tree on Alioth for the NMU of version 2014.1.3-7.1. If you add me to the Alioth project I can also push these changes myself. Gaudenz From 6f8528cc0cd4d7c2bd0a8f2519971acec310cdf9 Mon Sep 17 00:00:00 2001 From: Gaudenz Steinlin gaud

Bug#770941: [PKG-Openstack-devel] Bug#770941: closed by Thomas Goirand z...@debian.org (Re: Bug#770941: closed by Thomas Goirand z...@debian.org (Re: Bug#770941: nova-common - Overrides database c

Hi Bastian Blank bastian.bl...@credativ.de writes: Control: reopen -1 On Wed, Nov 26, 2014 at 01:09:08AM +, Debian Bug Tracking System wrote: It is a valid DSN. In this: postgresql:///nova Where's the user and password? What's the hostname? User and password is not needed for

Bug#769395: [Ceph-maintainers] Bug#769395: ceph-dkms: module FTBFS for kernel 3.16.0-4

Hi Dmitry Smirnov only...@debian.org writes: On Thu, 13 Nov 2014 15:27:30 Gaudenz Steinlin wrote: Is this package still usefull? Perhaps it is not too useful right now but I'm planning to update it for kernel 3.16 eventually... Both the ceph filesystem module and the rbd module

Bug#769395: [Ceph-maintainers] Bug#769395: ceph-dkms: module FTBFS for kernel 3.16.0-4

Andreas Beckmann a...@debian.org writes: Package: ceph-dkms Version: 3.14+git20140429-1 Severity: serious The module fails to build for a recent kernel: /var/lib/dkms/ceph/3.14+git20140429/build/ceph/file.c:740:4: error: implicit declaration of function 'iov_iter_copy_from_user'

Bug#765132: user-mode-linux NMU

Hi Jakub Thanks for taking the time to do the user-mode-linux NMU. I was just looking into this because I was worried about nova being removed from testing. As this bug is already open for more than 2 weeks and kernel 3.13 was long gone from the archive before, I think you can directly upload

Bug#764441: sinfo and slurm-client: error when trying to install together

Hi Mehdi Dogguy me...@dogguy.org writes: Control: reassign 764441 sinfo Control: fixed 764441 0.0.47-2 Le 2014-10-11 23:58, Gaudenz Steinlin a écrit : Hi Mehdi Dogguy me...@dogguy.org writes: Le 2014-10-09 22:55, Gaudenz Steinlin a écrit : I will certainly update the Conflict

Bug#759559: RFH : Advice on bug/patch

Hi Martijn Martijn van Brummelen mart...@brumit.nl writes: Im not sure if the suggested patch is ok or not, or provide a better patch? I asked on debian devel mailinglist[0]]/irc but did not get much response. It would be a pitty if Jessie would be released without it. Can someone advice me

Bug#764441: sinfo and slurm-client: error when trying to install together

Hi Mehdi Dogguy me...@dogguy.org writes: Le 2014-10-09 22:55, Gaudenz Steinlin a écrit : I will certainly update the Conflict if we can't agree on a better solution in the next few days. But as the Conflict was a workaround from the begining I'd prefer a solution where we agree

Bug#764441: sinfo and slurm-client: error when trying to install together

Mehdi Dogguy me...@dogguy.org writes: Hi Gaudenz, On Wed, Oct 08, 2014 at 10:34:45AM +0200, Gaudenz Steinlin gaud...@debian.org wrote: Ralf Treinen trei...@free.fr writes: Here is a list of files that are known to be shared by both packages (according to the Contents file for sid

Bug#764441: sinfo and slurm-client: error when trying to install together

Ralf Treinen trei...@free.fr writes: Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/sinfo /usr/share/man/man1/sinfo.1.gz This happends because the sinfo binary in slurm

Bug#759559: libpam-script: suggested patch

Hi Andreas B. Mundt a...@debian.org writes: Control: tags -1 + patch Hi, I think the patch below should address the issue. I am not completely sure about the *-Type: Additional, but from [1] and [2] and the links there I think it should be as below. This modification follows the

Bug#725594: python-werkzeug: diff for NMU version 0.9.4+dfsg-1.1

:29.0 +0100 @@ -1,3 +1,11 @@ +python-werkzeug (0.9.4+dfsg-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Start memcached for tests, thanks to Sebastian Ramacher for the patch +(Closes: #725594) + + -- Gaudenz Steinlin gaud...@debian.org Mon, 06 Jan 2014 19:01:32 +0100

Bug#730626: No patch for CVE-2013-6396 available yet

tags 730626 -patch forwarded 730626 https://bugs.launchpad.net/python-swiftclient/+bug/1199783 Thanks Hi Salvatore Where did you find a patch for this issue? As you can see in the launchpad bug report[1] and the upstream review system[2] no final patch is available yet. Upstream is still

Bug#733729: [Openstack-devel] Bug#733729: python-bootstrapform and python-django-taggit: error when trying to install together

Hi Ralf Treinen trei...@free.fr writes: Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/python2.7/dist-packages/tests/__init__.py /usr/share/pyshared/tests/__init__.py

Bug#732547: [Openstack-devel] Bug#732547: Does not preserve modifications to /etc/default/cinder-common

Hi Thomas Thomas Goirand z...@debian.org writes: On 12/19/2013 03:43 AM, Gaudenz Steinlin wrote: This is some remaining from before I restarted working on the packaging of OpenStack, and a feature which I just didn't touch. Each time I see it, I think I should kill this functionality. Would

Bug#732547: Does not preserve modifications to /etc/default/cinder-common

Package: cinder-common Version: 2013.2.1-1 Severity: serious cinder-common fails to preserve modifications to the file /etc/default/cinder-common. There seems to be some code in the config script function manage_cinder_enable which tries to read the value from the file and set the debconf value

Bug#732547: [Openstack-devel] Bug#732547: Does not preserve modifications to /etc/default/cinder-common

Hi Thomas Thomas Goirand z...@debian.org writes: On 12/18/2013 11:52 PM, Gaudenz Steinlin wrote: Package: cinder-common Version: 2013.2.1-1 Severity: serious cinder-common fails to preserve modifications to the file /etc/default/cinder-common. There seems to be some code in the config

Bug#732367: Ceilometer 2013.2.1 depends on WSME=0.5b5,0.5b6

Package: ceilometer Version: 2013.2.1-1 Severity: grave Starting ceilometer-collector, ceilometer-agent-central or ceilometer-api leads to an error containing the following stacktrace (not at the end but this is the point where it fails): 2013-12-17 10:10:09.917 17447 TRACE stevedore.extension

Bug#732367: Ceilometer 2013.2.1 depends on WSME=0.5b5,0.5b6

) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash From 9e9ab905c55bcfa769144557f266c8c5f5101ccb Mon Sep 17 00:00:00 2001 From: Gaudenz Steinlin gaud...@debian.org Date: Tue, 17 Dec 2013 10:03:03 +0100 Subject: [PATCH] Fix for compatibility with WSME=0.5b6

Bug#732387: Adds user ceilometer to group nova and libvirt on every upgrade

Package: ceilometer-common Version: 2013.2.1-1 Severity: serious The ceilometer postinst scripts runs the following commands unconditionally on configure and even reconfigure: adduser ceilometer nova || true adduser ceilometer libvirt || true In the common case this is just annoying as the

Bug#729787: Does not remove everything on purge

Package: dspam Version: 3.10.1+dfsg-11 Severity: serious According to the Debian Policy packages should remove everything on purge. The dspam package does not remove /var/spool/dspam and /var/log/dspam if there are files (created by dspam) in there. The package should remove these directories in

Bug#729072: Leaves behing /var/spool/postfix/spamass after purge

Package: spamass-milter Version: 0.3.2-1 Severity: serious If spamass-milter is run together with postfix the init script creates /var/spool/postfix/spamass, but this directory is not removed on purge (or when the daemon is stopped). According to policy a package must clean up everything it

Bug#709603: recommends the non existing package nvidia-settings-legacy-96xx

Package: nvidia-glx-legacy-96xx Version: 96.43.23-4 Severity: serious The 96xx series of the nvidia driver do not have their own settings package. You should probably recommend nvidia-settings-legacy-173xx which works also with the 96xx series. Gaudenz -- System Information: Debian Release:

Bug#706112: debian-installer: Wheezy installer always install bootloader in /dev/sda

Hi Vince Vincent McIntyre vincent.mcint...@csiro.au writes: Sadly, this issue will probably be in wheezy as nobody digged enough to tackle this down and we get rid of it before the last version of D-I is released. Please see my working (for me), tested, waiting-for-review patch [1] sent

Bug#706012: terminal activity does not start

Package: sugar-terminal-activity Version: 28-1 Severity: grave Tags: patch After starting (clicking) the terminal activity a message Terminal failed to start appears instead of the terminal activity. This is becuase this outdated version of the terminal activity has a wrong activity.info file.

Bug#706017: jigsawpuzzle activity does not start

Package: sugar-jigsawpuzzle-activity Version: 8-1 Severity: grave The jigsaw puzzle activity does not start. It shows a message with Jigsaw Puzzle failed to start. See the attached log for a bit more details. Gaudenz -- System Information: Debian Release: 7.0 APT prefers unstable APT

Bug#706018: record activity does not start

Package: sugar-record-activity Version: 82-1 Severity: grave Tags: patch The record activity does not start when clicked. Just the message Record failed to start appears. The attached patch fixes this. The record activity uses an outdated format for the activity.info file. Gaudenz -- System

Bug#706019: physics activity does not start

Package: sugar-physics-activity Version: 7+dfsg-1 Severity: grave Tags: patch The physics activity does not start because of an outdated activity.info file. The attached patch fixes this. Gaudenz -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable')

Bug#706020: connect activity does not start

Package: sugar-connect-activity Version: 22-1 Severity: grave The connect activity does not start because of an incompatible activity.info file. The attached patch fixes this. Gaudenz -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable')

Bug#706021: irc activity does not start

Package: sugar-irc-activity Version: 8-1 Severity: grave The IRC activity does not start because of an incompatible activity.info file. The attached patch fixes this. Gaudenz -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64

Bug#688782: Moving of mount points in initramfs from /live to /root/live does not work in important cases

=UTF-8) Shell: /bin/sh linked to /bin/dash From 9339bf268e1d8b58db75228e30cedccffb47caeb Mon Sep 17 00:00:00 2001 From: Gaudenz Steinlin gaud...@debian.org Date: Tue, 25 Sep 2012 17:54:45 +0200 Subject: [PATCH 1/3] Move filesystems even if mountpoint exists If /live has a persistence layer

  1   2   >