Bug#657405: update to 0.7.1?
On Sat, Oct 11, 2014 at 03:24:30PM -0400, Simon Fondrie-Teitler wrote:
> Sorry about the extended silence. I've been trying to find time/energy
> to work on it, and not doing a very good job. I'll hopefully get some
> work done this weekend, and if a DD wants to take a look and upload the
> 0.6.1 that would be great. I'm going to try to get in contact with
> Asheesh today.
If you're short on time, I'll be willing to land a hand as much as
needed doing work on it - time is very short before Jessie freeze,
and I think it would be a great shame if we missed it.
> Matija Nalis <mnalis-debianbug@voyager.hr> writes:
> > Could you update the package to more recent 0.7.1?
>
> I've been meaning to take a look at this, but it depends on
> sqlalchemy<0.9.0, >0.8.0. The version in unstable is 0.9.7. I'm not sure
> if that actually breaks anything, but I recall Chris Webber saying that
> some people had to run setup.py more than once to get it to work.
Well, it seems to works fine for me with 0.9.7. (setup.py supposedly
got run only when I built the package, I didn't touch it later).
Build machines would run it in clean environment (as did I) so I
guess it would probably be consistent (either in building or
failing).
> I'm not a DD either. You can create an account here:
> https://alioth.debian.org/account/register.php You'll then need apply
> for access to the collab-maint repository and have a DD request access
> for you. See here for more:
> https://lists.debian.org/debian-devel-announce/2012/01/msg00006.html
>
> Would any of the DDs following this be able to do that?
I did create alioth account as "mnalis-guest", and requested join on
"collab-maint".
So per instructions I'm hearby asking some interested DD or DM
(Martin?) to send a *signed* email to nm@debian.org saying
"Please accept the request of Matija Nalis mnalis-guest to join
collab-maint. We are going to work together on project mediagoblin".
> While you're waiting for that, feel free to push changes to any other
> location and I'll pull them in and push them up to the collab-maint
> repo.
by the way, is debian/* not in that repo? How should one manage that?
--
Opinions above are GNU-copylefted.
Reply to: