Bug#811593: FTBFS with GCC 6: statement indented as if it were guarded by

Yeah, I think it's time. There are other good option libraries for c++ around, and config manager is superceded by myrepos. On 14 Jan 2017 8:23 AM, "Simon McVittie" wrote: > On Sun, 08 Jan 2017 at 17:16:56 +0100, John Paul Adrian Glaubitz wrote: > > Hi Mike! > > > > > The attached patch should f

Bug#665018: python-fixtures: FTBFS: AttributeError: 'BrokenFixture' object has no attribute 'items'

This looks like an incompatible change in testtools; I'm fairly sure its fixed in trunk in one of testtools/fixtures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#571422: pandora-build: diff for NMU 0.98-1.1

Thanks a lot! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#571422: [patch]: pandora-build: FTBFS: autoreconf: failed to run libtoolize: No such file or directory

Thanks, care to NMU? If not thats fine, I'll try to get to it shortly. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#577908: gnu-smalltalk: FTBFS: tests failed

Sorry for not getting to this yet, extremely busy moving house just now. Haven't forgotten though.

Bug#560518: can't update to this yet

Upstream have fixed the bug but regressed the install paths; will get that fixed then do a upload to grab it all. -Rob -- signature.asc Description: This is a digitally signed message part

Bug#561549: Accepted subunit 0.0.4-2 (source all amd64)

On Sun, 2009-12-20 at 09:30 +0100, Cyril Brulebois wrote: > > > Well, hopefully you will be happy to contact me with less feeling of > > desperation if a future, similar situation arises. > > If you: > - start doing some QA checks before uploading your package; I already do such checks. > - s

Bug#561549: Accepted subunit 0.0.4-2 (source all amd64)

On Sun, 2009-12-20 at 08:27 +0100, Cyril Brulebois wrote: > Robert Collins (20/12/2009): > > Thank you for drawing my attention to this bug. > > You're very welcome. > > > I'm not the maintainer, and uploaders don't get copied on new bugs, > > so I

Bug#561549: Accepted subunit 0.0.4-2 (source all amd64)

On Sun, 2009-12-20 at 01:08 +0100, Cyril Brulebois wrote: > Robert Collins (19/12/2009): > Don't you think it might have been a good time to try and fix the > *obvious* FTBFS? Thank you for drawing my attention to this bug. I'm not the maintainer, and uploaders don't ge

Bug#560532: autoconf regression

So, this bug is a regression/change in autoconf 2.63 [http://old.nabble.com/--gnits,-AC_INIT-and-VERSION-td25572855.html]; We should forward the bug upstream in subunit to work around it,and perhaps build dep on autoconf2.59 for now. -Rob signature.asc Description: This is a digitally signed mes

Bug#544796: fl-cow: FTBFS due to autoreconf issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Cyril Brulebois wrote: > Package: fl-cow > Version: 0.6-2 > Severity: serious > Justification: FTBFS > > Hi, > > your package FTBFS due to autoreconf issues: ... Thanks, shall look at this this evening. -BEGIN PGP SIGNATURE- Version: GnuPG v

Bug#266003: should -dev libraries depending on other -dev packages?

On Wed, 2009-05-13 at 08:06 +0200, Josselin Mouette wrote: > Le mercredi 13 mai 2009 à 11:23 +1000, Brian May a écrit : > > Is this still considered to be a libtool issue? > > Yes, but instead of dropping the .la entirely, I’d recommend to simply > purge it from the dependency libs. > See /usr/sha

Bug#484305: bicyclerepair: bike.vim imports untrusted python files from cwd

thanks, yes - I concur. -Rob signature.asc Description: This is a digitally signed message part

Bug#484305: bicyclerepair: bike.vim imports untrusted python files from cwd

On Tue, 2008-08-05 at 23:07 -0400, James Vega wrote: > While this does provide a workaround for the issue, this is behavior > inherent in the way Python is designed and should be fixed in Python. > If we choose to instead address every application that embeds Python, > we're just creating an endl

Bug#454313: FTBFS: PANIC: exiting on botched invariant

On Wed, 2008-06-18 at 00:02 +0100, Anand Kumria wrote: > Upstream, Robert Collins, actually request that bazaar depend on bzr > so that anyone inadvertedly 'apt-get'ing that bazaar had the newer > version. > > Rather than remove -- even thought the package is buggy and &g

Bug#394239: testresources: FTBFS: Test failure

On Thu, 2008-01-24 at 10:06 -0500, Barry deFreese wrote: > > > I have prepared an NMU that seems to resolve this issue as well as > conform to the new python policy. I'm not quite sure exactly why it ... thanks! -Rob -- GPG key available at: . signa

Bug#394239: Should we keep testresources in the archive ?

On Tue, 2007-09-11 at 13:11 +0100, Regis Boudin wrote: > Hi, > > This package has been in an FTBS situation for almost one year now, > without a fix or a reply to the bugs. Please tell us what your plans are > regarding testresources, whether you plan to maintain it actively, orphan > it, or if it

Bug#439876: libopensync0: copyright file does not list upstream URL

On Tue, 2007-08-28 at 09:35 +0200, Michael Meskes wrote: > Package: libopensync0 > Version: 0.19-1.2 > Severity: serious > Justification: Policy 12.5 > > Header says it all. Policy 12.5 says: > > In addition, the copyright file must say where the upstream sources (if > any) were obtained. > >

Bug#396818: opensync_0.19-1.1 (alpha/unstable): FTBFS: not sudo-safe

On Thu, 2006-11-02 at 21:21 -0800, Steve Langasek wrote: > On Fri, Nov 03, 2006 at 04:10:24PM +1100, Robert Collins wrote: > > On Thu, 2006-11-02 at 18:40 -0800, Steve Langasek wrote: > > > > opensync is failing to build on alpha, mips, and mipsel because the > > >

Bug#396818: opensync_0.19-1.1 (alpha/unstable): FTBFS: not sudo-safe

On Thu, 2006-11-02 at 18:40 -0800, Steve Langasek wrote: > > opensync is failing to build on alpha, mips, and mipsel because the > debian/rules file assumes the availability of the $PWD environment > variable, > which will not be the case on systems building with dpkg-buildpackage > -rsudo > with

Bug#393720: opensync: FTBFS: /opensync-0.19/tests/check_ipc.c:2062: warning: passing argument 3 of 'create_case' from incompatible pointer type

On Tue, 2006-10-17 at 16:48 +0200, Andreas Jochens wrote: Thanks, its a file in the test suite, which we can probably disable, but I've started a dialog upstream about it http://www.opensync.org/ticket/363 -Rob -- GPG key available at: . signature.asc De

Bug#387576: Thanks

Thanks for the bug report about the autoreconf race condition. As the depends upon debian/rules is for packager convenience, I've just remove the build-stamp depends upon configure. Now packagers just need to do 'debian/rules configure build', without forcing it every time. Cheers, Rob -- GPG key

Bug#378049: diff for 0.18-2.2 NMU

On Mon, 2006-08-07 at 10:02 +0200, Pierre HABOUZIT wrote: > Hi, > > as promised, now that python-support deals with that, attached is the > diff for my opensync 0.18-2.2 NMU. Thanks! Rob -- GPG key available at: . signature.asc Description: This is a d

Bug#378049: python-opensync: python-gammu broken

On Wed, 2006-07-12 at 23:40 +0200, Matthias Bläsing wrote: > Package: python-opensync > Version: 0.18-2.1 > Severity: grave > Justification: renders package unusable > > > Hey, > > this is what I got when using python-opensync: > > [EMAIL PROTECTED]:~$ python2.4 > Python 2.4.4c0 (#2, Jun 14 200

Bug#366598: I have fixed this upstream

On Fri, 2006-06-02 at 11:18 +0200, Julien Danjou wrote: > On Mon, May 15, 2006 at 11:18:58PM +1000, Robert Collins wrote: > > This is fixed in my branch. > > I cannot find upstream version, URL in copyright file is 404. > > However, this package is not buildable anymore, be

Bug#366598: I have fixed this upstream

This is fixed in my branch. Cheers, Rob -- GPG key available at: . signature.asc Description: This is a digitally signed message part

Bug#345100: patch for segfault

calls. (Closes lp: #2397) + * Disabled xine [temporarily] - the xine opengl plugin was killing X randomly. + + -- Robert Collins <[EMAIL PROTECTED]> Thu, 23 Mar 2006 18:26:10 +1100 + pornview (0.2pre1-5build1) dapper; urgency=low * Rebuild against new libxine-main1 diff -u pornview-0.2

Bug#358403: Info received (was Bug#358403: testresources: FTBFS: SyntaxError: invalid syntax)

Meh, I've just noticed its a FTBFS. I'll check the source deps as soon as I get a chance. But the symptoms are those of a python2.3 build happening. Rob -- GPG key available at: . signature.asc Description: This is a digitally signed message part

Bug#358403: testresources: FTBFS: SyntaxError: invalid syntax

On Wed, 2006-03-22 at 17:25 +0100, Andreas Jochens wrote: > Package: testresources > Version: 0.1-1 > Severity: serious > > When building 'testresources' on unstable, > I get the following error: > > running build > running build_py > PYTHONPATH=lib ./test_all.py > Traceback (most recent call las

Bug#342532: fl-cow: does not work, assuming it to work can cause data loss

On Thu, 2005-12-08 at 12:28 +0100, Wolfgang Weisselberg wrote: > Package: fl-cow > Version: 0.6-1 > Severity: grave > Justification: renders package unusable > > I cannot get fl-cow to COW at all. Maybe I am stupid, but I > don't see what I did wrong. > > According to > /usr/share/doc/fl-cow

Bug#326864: fl-cow: FTBFS: ./flcow-test.sh: line 3: 21173 Segmentation fault

tags 32684 + fixed pending thanks Yup, looks good, forwarding upstream too. Cheers, Rob -- GPG key available at: . signature.asc Description: This is a digitally signed message part

Bug#326864: fl-cow: FTBFS: ./flcow-test.sh: line 3: 26795 Segmentation fault

On Tue, 2005-09-06 at 11:16 +0200, Andreas Jochens wrote: > Package: fl-cow > Version: 0.4-2 > Severity: serious > > When building 'fl-cow' on unstable, I get the following error: Thanks, I have a sid chroot here, i'll give it a test this weekend. Rob -- GPG key available at: