This is not strictly orphaning, more infanticide. I'm not sure
conventional orphaning fits, since the source package is not being
orphaned.
The PostgreSQL python interface (python-pygresql) has been separated
upstream into its own source tree. Since it no longer needs to be built
with
On Fri, 10 Oct 2003 14:46:15 +0100
Oliver Elphick olly@lfix.co.uk wrote:
Barring objection, and there may be some legitimate objection, as I am
well behind and feeling mighty damned guilty about it, I will pick it
up. This is somewhat natural because I am already PoPy packager, and
PoPy is being
On Fri, 2003-10-10 at 15:53, Jim Penny wrote:
On Fri, 10 Oct 2003 14:46:15 +0100
Oliver Elphick olly@lfix.co.uk wrote:
Barring objection, and there may be some legitimate objection, as I am
well behind and feeling mighty damned guilty about it, I will pick it
up. This is somewhat natural
On Fri, Oct 10, 2003 at 06:05:05PM +0100, Oliver Elphick wrote:
Go for it.
The existing python-pygresql packages will cease to be built when the
first postgresql 7.4 packages go into unstable. I will then ask the ftp
maintainers to remove them, so as to clear the way for your packages.
On Fri, Oct 10, 2003 at 12:56:08PM -0500, Luca - De Whiskey's - De Vitis wrote:
Just for curiosity: shouldn't the old python-pygresql be automatically
removed from the archive once it is no more builded?
It doesn't seem to work that way.
-- John
Quoting John Goerzen [EMAIL PROTECTED]:
On Fri, Oct 10, 2003 at 12:56:08PM -0500, Luca - De Whiskey's - De Vitis
wrote:
Just for curiosity: shouldn't the old python-pygresql be automatically
removed from the archive once it is no more builded?
It doesn't seem to work that way.
IIRC it
On Fri, Oct 10, 2003 at 02:16:56PM -0500, John Goerzen wrote:
On Fri, Oct 10, 2003 at 12:56:08PM -0500, Luca - De Whiskey's - De Vitis
wrote:
Just for curiosity: shouldn't the old python-pygresql be automatically
removed from the archive once it is no more builded?
It doesn't seem to
7 matches
Mail list logo
