Re: Fixes in zopectl Re: Removing zope
They're done -- Fixed in NMUs zopectl 0.3.4.1 and zope 2.6.4-1.1 Everyone, let me know if you see any problems. Thanks. Steve Langasek <[EMAIL PROTECTED]> writes: > Since testing has not been frozen, an upload to unstable is sufficient. > It will still take a few days to propagate, of course, but removing zope > from testing would be enough of a PITA that just about any progress at > all will be enough to convince me not to remove it. ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Removing zope
On Sat, Apr 03, 2004 at 12:17:32PM -0600, Steve Langasek wrote: >... > I would expect that if there isn't clear progress on fixing zope's > RC bugs within a week, I would be hinting it for removal, along with any >... You are already hinting it for removal: * -zope (2.6.4-1 to -) + Removal request by vorlon + Package is broken, will try to remove Only thanks to zope-textindexng2 and zope-zpatterns it wasn't already removed from testing. > Thanks, > Steve Langasek cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Re: Fixes in zopectl Re: Removing zope
On Sat, Apr 03, 2004 at 11:55:18AM -0500, David Coe wrote: > Matthias Klose <[EMAIL PROTECTED]> writes: > > Gregor Hoffleit writes: > >> * Matthias Klose <[EMAIL PROTECTED]> [040403 12:25]: > >> > Steve Langasek writes: > >> > The zope maintainers seem to be quiet ... Please before removing > >> > qmtest, let me separate out the python-extclass package from the zope > >> > package. > >> No reaction from Luca indeed, but Andrea is suggesting to upgrade to his > >> 2.7.0-13 package. During the next week, I'll try and see if that sounds > >> possible and feasable without breaking to much other packages. Fixing > >> the grave bugs in 2.6.4 doesn't look impossible, but then, I really > >> don't like to mess with Luca's zopectl code... > > that would be great, to have plone-2.0 in sarge ... > That's a great idea, though plone 2.0 doesn't actually *need* zope 2.7 > (it works with 2.6 as well). > I'm fixing the remaining zope 'grave' bugs, all with small changes in > zopectl. I'll NMU it tonight, I believe. > QUESTION: is an NMU to unstable with priority high sufficient to get > this into testing, or do I have to upload to testing-proposed-updates > (or someplace else) as well? Since testing has not been frozen, an upload to unstable is sufficient. It will still take a few days to propagate, of course, but removing zope from testing would be enough of a PITA that just about any progress at all will be enough to convince me not to remove it. ;) -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Removing zope
On Sat, Apr 03, 2004 at 12:22:27PM +0200, Matthias Klose wrote: > Steve Langasek writes: > > On Wed, Mar 31, 2004 at 09:34:18PM -0600, Steve Langasek wrote: > > > On Mon, Mar 29, 2004 at 05:33:57AM -0500, Nathanael Nerode wrote: > > > > For zope to be removed, one must also do this: > > > > remove zope-textindexng2/2.05-1 > > > > remove zope-zpatterns/0.4.3p2-17 > > > > > Cc'ing the maintainers of those packages, as they have an obvious vested > > > interest in keeping zope from being removed from sarge. Any takers for > > > NMU'ing (or MU'ing) zope to get these RC bugs fixed? Time is short. > > > > also cc:ing the maintainers of the various other zope packages that > > are arch: all, and would also have to be removed in order for zope to be > > removed from testing. > > > > The total list of packages that must be removed if zope is not > > releasable with sarge is as follows: > > > > plone > > python-extclass > > qmtest > The zope maintainers seem to be quiet ... Please before removing > qmtest, let me separate out the python-extclass package from the zope > package. I would expect that if there isn't clear progress on fixing zope's RC bugs within a week, I would be hinting it for removal, along with any packages depending on it at that time. If you are concerned that zope won't be fixed in this time period, I would suggest you start working on qmtest's dependencies immediately, so it can get back into testing ASAP. Since there has been an NMU offer, I'm still hopeful it won't come to that. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Fixes in zopectl Re: Removing zope
David Coe writes: > Matthias Klose <[EMAIL PROTECTED]> writes: > > > Gregor Hoffleit writes: > >> * Matthias Klose <[EMAIL PROTECTED]> [040403 12:25]: > >> > Steve Langasek writes: > >> > > >> > The zope maintainers seem to be quiet ... Please before removing > >> > qmtest, let me separate out the python-extclass package from the zope > >> > package. > >> > >> No reaction from Luca indeed, but Andrea is suggesting to upgrade to his > >> 2.7.0-13 package. During the next week, I'll try and see if that sounds > >> possible and feasable without breaking to much other packages. Fixing > >> the grave bugs in 2.6.4 doesn't look impossible, but then, I really > >> don't like to mess with Luca's zopectl code... > > > > that would be great, to have plone-2.0 in sarge ... > > That's a great idea, though plone 2.0 doesn't actually *need* zope 2.7 > (it works with 2.6 as well). OTOH, zope 2.7 does work with the recent python2.3. just dreaming to drop python2.2 from unstable ... (python2.1 is still needed for jython). Matthias
Fixes in zopectl Re: Removing zope
Matthias Klose <[EMAIL PROTECTED]> writes: > Gregor Hoffleit writes: >> * Matthias Klose <[EMAIL PROTECTED]> [040403 12:25]: >> > Steve Langasek writes: >> > >> > The zope maintainers seem to be quiet ... Please before removing >> > qmtest, let me separate out the python-extclass package from the zope >> > package. >> >> No reaction from Luca indeed, but Andrea is suggesting to upgrade to his >> 2.7.0-13 package. During the next week, I'll try and see if that sounds >> possible and feasable without breaking to much other packages. Fixing >> the grave bugs in 2.6.4 doesn't look impossible, but then, I really >> don't like to mess with Luca's zopectl code... > > that would be great, to have plone-2.0 in sarge ... That's a great idea, though plone 2.0 doesn't actually *need* zope 2.7 (it works with 2.6 as well). I'm fixing the remaining zope 'grave' bugs, all with small changes in zopectl. I'll NMU it tonight, I believe. QUESTION: is an NMU to unstable with priority high sufficient to get this into testing, or do I have to upload to testing-proposed-updates (or someplace else) as well?
Re: Removing zope
Gregor Hoffleit writes: > * Matthias Klose <[EMAIL PROTECTED]> [040403 12:25]: > > Steve Langasek writes: > > > On Wed, Mar 31, 2004 at 09:34:18PM -0600, Steve Langasek wrote: > > > > On Mon, Mar 29, 2004 at 05:33:57AM -0500, Nathanael Nerode wrote: > > > > > For zope to be removed, one must also do this: > > > > > remove zope-textindexng2/2.05-1 > > > > > remove zope-zpatterns/0.4.3p2-17 > > > > > > > Cc'ing the maintainers of those packages, as they have an obvious vested > > > > interest in keeping zope from being removed from sarge. Any takers for > > > > NMU'ing (or MU'ing) zope to get these RC bugs fixed? Time is short. > > > > > > also cc:ing the maintainers of the various other zope packages that > > > are arch: all, and would also have to be removed in order for zope to be > > > removed from testing. > > > > > > The total list of packages that must be removed if zope is not > > > releasable with sarge is as follows: > > > > > > plone > > > python-extclass > > > qmtest > > > > The zope maintainers seem to be quiet ... Please before removing > > qmtest, let me separate out the python-extclass package from the zope > > package. > > No reaction from Luca indeed, but Andrea is suggesting to upgrade to his > 2.7.0-13 package. During the next week, I'll try and see if that sounds > possible and feasable without breaking to much other packages. Fixing > the grave bugs in 2.6.4 doesn't look impossible, but then, I really > don't like to mess with Luca's zopectl code... that would be great, to have plone-2.0 in sarge ...
Re: Removing zope
* Matthias Klose <[EMAIL PROTECTED]> [040403 12:25]: > Steve Langasek writes: > > On Wed, Mar 31, 2004 at 09:34:18PM -0600, Steve Langasek wrote: > > > On Mon, Mar 29, 2004 at 05:33:57AM -0500, Nathanael Nerode wrote: > > > > For zope to be removed, one must also do this: > > > > remove zope-textindexng2/2.05-1 > > > > remove zope-zpatterns/0.4.3p2-17 > > > > > Cc'ing the maintainers of those packages, as they have an obvious vested > > > interest in keeping zope from being removed from sarge. Any takers for > > > NMU'ing (or MU'ing) zope to get these RC bugs fixed? Time is short. > > > > also cc:ing the maintainers of the various other zope packages that > > are arch: all, and would also have to be removed in order for zope to be > > removed from testing. > > > > The total list of packages that must be removed if zope is not > > releasable with sarge is as follows: > > > > plone > > python-extclass > > qmtest > > The zope maintainers seem to be quiet ... Please before removing > qmtest, let me separate out the python-extclass package from the zope > package. No reaction from Luca indeed, but Andrea is suggesting to upgrade to his 2.7.0-13 package. During the next week, I'll try and see if that sounds possible and feasable without breaking to much other packages. Fixing the grave bugs in 2.6.4 doesn't look impossible, but then, I really don't like to mess with Luca's zopectl code... Gregor
Re: Removing zope
Steve Langasek writes: > On Wed, Mar 31, 2004 at 09:34:18PM -0600, Steve Langasek wrote: > > On Mon, Mar 29, 2004 at 05:33:57AM -0500, Nathanael Nerode wrote: > > > For zope to be removed, one must also do this: > > > remove zope-textindexng2/2.05-1 > > > remove zope-zpatterns/0.4.3p2-17 > > > Cc'ing the maintainers of those packages, as they have an obvious vested > > interest in keeping zope from being removed from sarge. Any takers for > > NMU'ing (or MU'ing) zope to get these RC bugs fixed? Time is short. > > also cc:ing the maintainers of the various other zope packages that > are arch: all, and would also have to be removed in order for zope to be > removed from testing. > > The total list of packages that must be removed if zope is not > releasable with sarge is as follows: > > plone > python-extclass > qmtest The zope maintainers seem to be quiet ... Please before removing qmtest, let me separate out the python-extclass package from the zope package.
Re: Removing zope
On Wed, Mar 31, 2004 at 09:34:18PM -0600, Steve Langasek wrote: > On Mon, Mar 29, 2004 at 05:33:57AM -0500, Nathanael Nerode wrote: > > For zope to be removed, one must also do this: > > remove zope-textindexng2/2.05-1 > > remove zope-zpatterns/0.4.3p2-17 > Cc'ing the maintainers of those packages, as they have an obvious vested > interest in keeping zope from being removed from sarge. Any takers for > NMU'ing (or MU'ing) zope to get these RC bugs fixed? Time is short. also cc:ing the maintainers of the various other zope packages that are arch: all, and would also have to be removed in order for zope to be removed from testing. The total list of packages that must be removed if zope is not releasable with sarge is as follows: plone python-extclass qmtest squishdot zope zope-backtalk zope-btreefolder2 zope-callprofiler zope-cmf zope-cmfcalendar zope-cmfcore zope-cmfdefault zope-cmfforum zope-cmfldap zope-cmfpgforum zope-cmfphoto zope-cmfphotoalbum zope-cmfplone zope-cmftopic zope-cmfworkflow zope-devguide-example zope-docfindereverywhere zope-dtmlcalendar zope-emarket zope-epoz zope-externaleditor zope-extfile zope-exuserfolder zope-formulator zope-kinterbasdbda zope-ldap zope-ldapuserfolder zope-localizer zope-lockablefolder zope-loginmanager zope-mysqlda zope-parsedxml zope-photo zope-popyda zope-psycopgda zope-sqlrelayda zope-testcase zope-textindexng2 zope-tinytable zope-translationservice zope-ttwtype zope-xmlmethods zope-znavigator zope-zpatterns zope-zshell zope-zwiki There are three additional zope-using packages not yet in sarge, zope-rdfgrabber, zope-tinytableplus, and zope-zms; also cc'ed. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
