[Tahoe-debian] tahoe-lafs uploaded on mentors

[micah anderson]

On Fri, 10 Jun 2011 20:30:49 +0200, bertagaz at ptitcanardnoir.org wrote:
> On Fri, Jun 10, 2011 at 08:58:46AM -0400, micah anderson wrote:
> > 
> > Hi,
> > 
> > On Fri, 10 Jun 2011 10:29:58 +0200, bertagaz at ptitcanardnoir.org wrote:
> > > I've finally managed to upload a new zfec package as well as the
> > > tahoe-lafs package itself on mentors.debian.net.
> > 
> > Great!
> > 
> > > I haven't tested them as much as last week, but it seems to install and
> > > run fine.
> > > 
> > > http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=zfec
> > > http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=tahoe-lafs
> > 
> > How come mentors.debian.net? Not that its bad, but we already have a git
> > repository to build from, and mentors is a mechanism for finding
> > sponsors for things, and I've already said I would do it. I am guessing
> > there are some other advantages to using it that I am just not seeing
> > thouough, but that is why I ask.
> 
> Ah, my fault, I was probably a bit confused and didn't realized you might
> just use the git repo. I thought we had to use the same process than for
> the python-zfec package.

Is there a git repo for python-zfec that I can use?


> > > Hope I didn't forgot/broke/missed something, but I trust micah to look at
> > > it and find any issue :)
> > 
> > I will try to find something :)
> 
> ooooh, /me getting nervous :)

Nothing to worry about, i just went over it again and it seems fine. I
made only a couple changes to add me as Uploader and bump the Standards
Version.

I also updated the git tag debian/1.8.2-1 because the one that was
uploaded was different from the tag. I think that we should only tag
after the package has been uploaded.

Because that tag was already pushed, you will need to delete the old one
and then fetch the new one by doing this:

                   git tag -d debian/1.8.2-1
                   git fetch origin tag 1.8.2-1

You can test which tag you have by doing

                   git rev-parse debian/1.8.2-1

which should return ed01cd86e952c5f0471d0ddfdad7702c662a7957 if you have
the new version.

> > > I'll post the remaining todo items soon.
> > 
> > does this mean that I should *not* upload tahoe until these items are
> > done? or are these todo items that are independent of the upload?
> 
> No, sorry for the confusion, the todo item I'm referring to are long terms
> one we discussed some times ago : init scripts, FHS compliance, some more
> packages to do (pyutils and zbase32 basically) and upgrading pycryptopp...
> We agreed to upload a release of this package without this features, so I
> guess it's ok if you upload the package in the current state.

Sounds good!

micah
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/tahoe-debian/attachments/20110611/52de4b2c/attachment-0001.pgp>