Re: Removing python-pygresql and libpqpp packages
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 merged into pygresql. Jim Penny 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 postgresql itself, and since I do not use python, the python binaries will no longer be built when postgresql 7.4 is released (in a few weeks).
Re: Removing python-pygresql and libpqpp packages
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 because I am already PoPy packager, and PoPy is being merged into pygresql. Jim Penny 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. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C He that covereth his sins shall not prosper; but whoso confesseth and forsaketh them shall have mercy. Proverbs 28:13
Re: Removing python-pygresql and libpqpp packages
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. Just for curiosity: shouldn't the old python-pygresql be automatically removed from the archive once it is no more builded? ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG=[EMAIL PROTECTED] | don't depend on the language.
Re: Removing python-pygresql and libpqpp 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
Re: Removing python-pygresql and libpqpp packages
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 does. At least, it used to work for one of my packages last year. -- Jérôme Marant
Re: Removing python-pygresql and libpqpp packages
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 work that way. It does, but only semi-automatically. -- Colin Watson [EMAIL PROTECTED]
