Bug#315592: Aboot: Orphan imminent / Good bye alpha ;-((
Hi Helge,
On Fri, Feb 22, 2008 at 06:56:51PM +0100, Helge Kreutzmann wrote:
> for over two years I have no physical access to an alpha anymore,
> since last year I have remote access though. But to maintain (and
> improve!) aboot this is not enough, especially since I notice how I
> loose my knowledge about alphas in general and aboot in special. Thus I
> intend to orphan aboot instead of pretending to still be able to
> maintain it. If necessary, I can still push changes upstream (though I
> cannot do releases there, unfortunately).
So as I had occasion at last today to commit to the package repo, I can
finally reply to this without my comments being a farce.
I will pick up the maintenance of the aboot package in Debian.
I don't know for how long that will be; I'm personally quite skeptical about
alpha's prospects for lenny+1, because I don't see much future demand for
the architecture, and my own alpha is only running for porting purposes so
I would honestly prefer to be able to power it off and save electricity.
But for the meantime, aboot has a home again.
Thank you for your contributions over the past few years! It's been a
pleasure to work with you, even though I have a terrible track record as a
sponsor for the package. :)
> So what is the status?
> *1.0~pre20040408-3 is "ready to go", 1.0~pre20040408-4 just started
> (could be folded in -3). So if you like you could start with an
> upload right away. I'm not a DD, so a "goodby upload" is impossible
> for me.
I don't see any -4 changelog entries in the CVS repository at all, only -3.
Are these uncommitted changes then, or was the changelog just not updated
with a new -4 version number?
> *Upstream is dead. I still have e-mail addresses, but both upstream
> maintainers do not respond for a prolonged time already.
> *I can still write in the CVS repository upstream, but I have no
> privileges there to do releases and similar things.
Under these circumstances, I'm going to treat the alioth project as the de
facto upstream. My first change in consequence of this is to request the
creation of a bzr repo to replace the current CVS repo on alioth; I'm long
past the point where I can stomach to work with CVS on a regular basis, so
leaving the package in CVS will only discourage me from working on it - and
furthermore, it's my hope that switching to a distributed VCS will encourage
better collaboration among whatever other alpha porters are still out there
on other distros, with the side benefit of cementing the legitimacy of this
new "upstream" source.
You, of course, continue to be welcome to commit to the alioth (bzr)
repository, whenever the desire strikes you. And maybe I can be somewhat
less of an absentee landlord, with the possibility that we will get a new
upstream release someday.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org
Reply to: