[Debian-med-packaging] autobuilding of mgltools-*?
tille at debian.org
Tue Jun 29 06:47:39 UTC 2010
would it help if we do a team upload which sets
and does polishing Standards-Version etc. a bit. I might dedicate some
time to it next week when I'm at LSM in Bordeaux. But considering the
Mail from Steffen below I would not like to touch the Python 2.6 issue.
If this might be the main point I would prefer to wait until Steffen is
able to maintain the updated upstream stuff.
On Tue, Jun 29, 2010 at 08:29:37AM +0200, Steffen Möller wrote:
> Dear Andy,
> On 06/29/2010 07:51 AM, Andreas Barth wrote:
> > * Andreas Barth (aba at not.so.argh.org) [100621 19:20]:
> >> can these packages be autobuilt? If so, can you send an gpg signed
> >> mail confirming that (with the package names).
> >> If not, can you please upload these packages on all relevant
> >> architectures to cope with the new python default version?
> > As we didn't hear back yet, these packages are about to be removed
> > from testing as soon as the testing migration of the new python
> > packages is otherwise ready.
> apparently I have only drafted an email but have not actually sent it.
> All the mgltools-* packages and autodocktoolkit can be autobuilt,
> which should also be indicated respectively in debian/control.
> The real task however is to upload a yet unreleased version from
> upstream's CVS which is now compatible with Python 2.6, which the
> current version is said not to be. ... not to be completely at least.
> Thank you for your warning. I don't have time for anything in the
> first half of July and would address the update then right afterwards.
> My suggestion is that you please go ahead with the autobuilding, even
> if not all the functionality shall be available with 2.6 for some days.
> Many thanks
More information about the Debian-med-packaging