monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] Packages for Debian testing


From: Ludovic Brenta
Subject: Re: [Monotone-devel] Packages for Debian testing
Date: Mon, 09 Jul 2007 00:03:28 +0200
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)

Zack Weinberg writes:
> On 7/7/07, Shaun Jackman <address@hidden> wrote:
>>
>> A team of maintainers is great. In fact, it's done quite regularly.
>> Just search google for 'debian maintainer team'. If the team's well
>> coordinated, it can work much better than a single maintainer.
>
> So thinking about it a bit more, I don't want to put
> address@hidden as the Maintainer: list, since most people
> on that list don't care about Debian packaging issues.  Can we get a
> address@hidden list?  I *think* this just requires one of
> the people with project admin rights on Savannah to fill out a form
> ...  (cc:ing njs, as I know graydon is not available right now)
>
> My feeling on how to move forward is that once we have that list, we
> should do ASAP an 0.35-1 which is basically the same as the 0.35-0.2 I
> did last week, plus corrections as discussed in this thread - I have
>
> 1) add po-debconf to the dependencies
> 2) pull in the Dutch debconf translation from #415496
> 3) new Maintainer: and Uploaders: control lines
> 
> -- did I miss anything?  That will get us working packages in
> unstable.  We can then worry about testing transition problems and
> uncoupling from boost at our leisure.

4) Add something like this in the changelog, too:

  * New maintainers.  Closes: #431797.

5) Really close #422396, which was reopened.  This is weird; the
   buildds did build 0.33 just fine in fresh chroots, and they didn't
   call makeinfo at all.  The bug says the build fails when calling
   makeinfo on i386.  What's happening?

6) Close #427687, too.  The bug is that boost 1.33.1 is no longer in
   unstable (only in testing), and therefore monotone 0.31-8 won't
   install on unstable.  I believe that's fixed since 0.33-3, but I
   haven't checked.

0.33-3 being in unstable already, there is no emergency there, so
"ASAP" should really be "as soon as you feel like it" :)

-- 
Ludovic Brenta.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]