Re: [be] A new bibledit tarball and/or tags for the copyright fixes would help Ubuntu packaging

[Teus Benschop]

Hi Jonathan,

Thanks for taking it up so as to get it into the next Ubuntu release
just before the deadline.

I was about to release version 3.6 and have considering it since last
week. Your message was the last push needed to make this release, so
I've just done that.

My internet connection (from Africa) is now down, so I cannot actually
copy the tarball to the normal release locations. But I will email you
the tarball to your personal email address, so that, whenever the
internet connection comes back again, the mail will go out. The tarball
will be in the usual place on the release site, with the name 3.6 in it,
everything being the same as the 3.5 version, except that the "5"
becomes a "6".

I remember having tried to push git tags out, and it didn't work right
away, so I gave up, but will try the matter again to see if that can be
done.

Thanks for rushing this through, the translators will like it!

Teus.


On Thu, 2009-01-29 at 13:27 -0800, Jonathan Marsden wrote:
> Teus and team,
> 
> Thanks so much for the rapid copyright fixup changes!
> 
> In order for us to officially package bibledit including those changes, 
> the simplest way for us to go is to use a released source tarball, or 
> (mildly more work but doable) to be able to selectively pick patches 
> from git based on tags, so we can release the stable version 3.5 with 
> just those copyright changes (and no code changes).
> 
> (A) The really easy way for us:
> 
> Would you consider releasing (and putting on your download site) a 
> bibledit tarball which is just bibledit 3.5 with the copyright changes? 
>   Maybe name it bibledit-3.5.1.tar.gz or something similar?  There is no 
> need to publicize it widely to your userbase or anything, just release 
> it (and leave it available there among the other release tarballs), so 
> that we have an "official" tarball to point the packaging system at.
> 
> (B) The slightly harder (but still doable) way for us:
> 
> Apparently (I'm not a git expert!) the public bibledit git repository 
> does not currently have tags in it.  If that repository is currently 
> being pushed from a private master that *does* have tags, then the 
> suggestion is that you may well be able to do something like
> 
>    git push savannah --tags
> 
> and so make the tags visible in the public repository.  Then we can pick 
> out the copyright fixes from there as patches.
> 
> Actually, even if you do (A), doing (B) too would probably still be very 
> useful to us down the road, as bug reports emerge in future which are 
> fixed in your git code but are not yet in a stable release.
> 
> Timing:
> 
> I realize this may be totally unrealistic to ask you to do "right 
> now"... but tomorrow (Friday 30 Jan 2009) happens to be a Ubuntu "REVU" 
> day, which means that if I can get a clean bibledit 3.5 package, with 
> the copyright stuff addressed in it, into REVU tonight, we *may* (with 
> some work and some prayer!) be able to get it officially approved by the 
> Ubuntu MOTU team, and so into the Ubuntu Jaunty universe, tomorrow!
> 
> Even if we miss that (admittedly ridiculously close!) timeframe, getting 
> either or both of the above suggestions done for us, whenever you do 
> have time (if they are practical), would be most helpful in our attempt 
> to get this package into Ubuntu Jaunty.
> 
> Thanks,
> 
> Jonathan
> 
> 
>