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

Bug#781518: Please remove very outdated MakeHuman package



This is a perfectly acceptable solution. The main thing we wanted to achieve here was to get the four year old alpha 6 out of circulation, and that is the goal that has priority over other concerns. So yes, we would like to have the package removed from Unstable too.

I also saw the answer from the maintainer (and having written a PhD myself, I can sympathize).

If it is acceptable, we can at a later point contribute a new build written for the current MakeHuman branch (although, we would most likely wait with that until the next stable release which is upcoming within the near future). We would then also be willing to discuss maintaining the build in the future.

A question that have arisen in the project group is this though: Do we cause any irreparable harm for the possible (re-)inclusion of a new MakeHuman build at a later date by asking to have the current version removed?

The worries mainly concerned the recommendations for reintroducing removed packages, but also the recommendations against introducing packages depending on python 2.x (which is a hard dependency for MakeHuman).

Anyway, thank you for your quick response.

Den 2015-04-01 14:49, Charles Plessy skrev:
Le Mon, Mar 30, 2015 at 01:31:19PM +0200, Joel Palmius a écrit :

The version of MakeHuman currently included in the repo is a four year old
alpha. As per bug report (#781306) it does not even seem to start.

At this point it seems unlikely that an acceptable, less ancient, version
could be included in Debian. Thus, we in the MakeHuman crew humbly requests
that the currently available package at least be removed. It reflects poorly
upon both Debian and MakeHuman that the current package is still around.

Dear Joel,

thank you for contacting us.  I am sorry that we are causing trouble to your
project with our outdated package.

The bug report #781306 caused the package to be removed from our "Testing"
distribution, therefore it will not be part of our next Stable release.

This partially solves the problem, but as of today the package is still
distributed in our "Unstable" distribtion and while this distribution is not
directed at general users, I understand that you would like it to be removed as
well.

As you have seen, I have contacted the package maintainer, and I propose to
wait 15 days and transfer the request for removal to our FTP archive team in
the absence of a response, which will result in the final removal of the
package.

Is that good for you ?

Have a nice day,



Reply to: