[DebianGIS] [Fwd: Re: Hijack or remove postgis]
hi,
i wish to make a distinction between the postgis package currently in
sid, which is currently candidate to be removed (and i personally agree
on that), and the newer postgis package currently on debian-giswhich has
all comments fixed, and it's about to be re-proposed on new.
best regards,
alex
-------- Original Message --------
Subject: Re: Hijack or remove postgis
Date: Fri, 21 Apr 2006 16:37:48 +0300
From: alex bodnaru <alex@alex3>
To: Peter Eisentraut <peter_e@gmx.net>
CC: Thomas Bushnell BSG <tb@becket.net>, debian-qa@lists.debian.org,
postgis@packages.debian.org
References: <200604202057.34963.peter_e@gmx.net>
<u1hpsjcro20.fsf@kempis.becket.net> <200604211509.47540.peter_e@gmx.net>
hi all,
the package currently in sid was installable in sid for a very little
time only, untill multi-version postgresql has been introduced.
ironically, it is well suitable for sarge and woody.
as i have repeatedly answered previous initiatives, this package may be
removed from sid.
i have created a new postgis package, that has been candidate in new,
but has been bounced. as the only postgis package available is the one
above, almost all bug reports and the bouncing reasons for the newer
package are been filed against the older one.
note that both the old package (in sid now), and the newer one are
currently been used in various production applications.
anyway, i have made a new postgis package, that fixes the whole list of
bugs and bouncing reasons, and uploaded it on debian gis. the new
sponsor (fabio Tranchitella <kobold@debian.org>) is eager to cooperate
on uploading it asap.
alex
Peter Eisentraut wrote:
> Thomas Bushnell BSG wrote:
>
>>Peter Eisentraut <peter_e@gmx.net> writes:
>>
>>>Something has to be done about the postgis package. There are RC
>>>bugs on uninstallability and FTBFS as well as several functionality
>>>bugs and two new upstream releases and no one seems to do anything.
>>>The packaging seems to be sufficiently ugly that it may be better
>>>to request removal and start over later. Please orphan the package
>>>or request removal.
>>
>>Have you asked the maintainer?
>
>
> The maintainer is copied here and had also been alerted previously about
> the situation.
>
Reply to: