[Fusionforge-general] Seeking pre-upload approval (was Re: MW 1.19 for wheezy)

[Olivier Berger]

Hi.

Uh... Thorsten... may I suggest that you try and make a more explicit
version of who what when where why ?

I'm afraid that as such the message is really cryptic... and I even
don't imagine what non DD folks can grasp.

Or maybe the release team is much smarter than I'm expecting ;)

Just trying to help.

Best regards,

Thorsten Glaser <t.glaser at tarent.de> writes:

> On Thu, 30 Aug 2012, Thorsten Glaser wrote:
>
>> I’m hereby seeking pre-upload approval for new uploads (not new
>> upstream versions) of src:mediawiki-extensions (the most critical
>> one), src:fusionforge (very important, as otherwise the mediawiki
>> binary package must declare a Breaks on fusionforge-plugin-mediawiki
>> and thus would require a sourceful upload too) and src:mediawiki
>> (the least critical, but still containing bugfixes and better
>> integration).
>
> Hi,
>
> please disregard the src:fusionforge part of this request
> in its entirety. We discussed, in our IRC meeting, that a
> removal of src:fusionforge from testing will be requested
> by the lead developer soonish, so I will *still* want to
> make a coordinated upload of all three packages, but with
> src:fusionforge only targetting sid (although it *would*
> really be nice if the FF support changes were accepted in
> wheezy so users would not need to track that from sid, as
> well; they are in src:mediawiki; src:mediawiki-extensions
> is completely separate again, but a needed upload to sup‐
> port mediawiki-1.19 in wheezy).
>
> I’m sending this early to save on possible review work,
> now that I managed *ahem* to look at MW 1.19.2.
>
> So, if that agrees with you, I would like to upload to sid
> with eventual target wheezy the following:
>
> 1) mediawiki-extensions 2.8 (unchanged from the last mail)
>
> 2) mediawiki 1.19.2-1 (the debdiff I already sent against
>    1.19.1 rebased on top of 1.19.2, with suitable Breaks
>    for old fusionforge-plugin-mediawiki binary packages)
>
> And, in a coordinated upload, fusionforge to sid without
> transition to wheezy (but, for now, still based on what
> I had planned for that, to get the most urgent bugs fixed).
>
> This will not affect Alioth negatively, as it runs a
> slightly modified FusionForge install anyway, but having
> working MW core and extension packages in wheezy would
> help.
>
> Thanks,
> //mirabilos
> -- 
> tarent solutions GmbH
> Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
> Tel: +49 228 54881-393 • Fax: +49 228 54881-314
> HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
> Geschäftsführer: Boris Esser, Sebastian Mancke
>
> _______________________________________________
> Fusionforge-general mailing list
> Fusionforge-general at lists.fusionforge.org
> http://lists.fusionforge.org/cgi-bin/mailman/listinfo/fusionforge-general
-- 
Olivier BERGER 
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)