[Reportbug-maint] Bug#522010: reportbug: FTBFS with bin-NMU version

[Sandro Tosi]

Hi Daniel,

On Tue, Mar 31, 2009 at 06:31, Daniel Schepler
<schepler at math.berkeley.edu> wrote:
> Package: reportbug
> Version: 4.0
> Severity: normal
>
> From my pbuilder build log, with a hook script installed which creates a dummy
> version "4.0+pb1":
>
> ...
>  debian/rules build
> dh_testdir
> # Test if versions are synchronized; this will bomb if not synced
> Please update reportbug/__version__
> make: *** [build-stamp] Error 1
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2

Yes, this is because debian/changelog and reportbug/__init__.py needs
to have the same version.

I agree it's not the most beautiful way to have those in sync, but
it's a working solution, that avoids upload with mismatched versions.

> This isn't that serious since reportbug is Architecture: all.  Still, it would
> be nice to be able to build a package locally with a different version from the
> official packages, so that apt doesn't get confused between the two.

Now, I'm a bit in trouble proposing a solution here, even because I'm
not sure it's a bug :)

Since arch:all binNMU are not allowed (as of now, at least) by our
buildd, the way to simulate it is a NMU.

And since you don't need to only schedule a simple rebuild, I don't
see the problem in editing also reportbug/__init__.py .

Moreover, I can't see why you would re-build reportbug on your machine
and install it; if you do it to change something in the code (for
example because you're so kind and want to prepare & send us a patch
:) ), you can also edit __init__.py ; if you do it to bring in other
versioned depends, we define none, only some versioned Suggests, so I
still fail to understand the request itself.

I hope I've clarified our situation, so if you want you can clarify
better your position :)

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi