[Pkg-zope-developers] Re: zope-common and dh-zope, new packages

[Fabio Tranchitella]

--LwW0XdcUbUexiWVK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 29, 2005 at 06:39:25PM +0200, martin f krafft wrote:
> Oh yeah, there is that. Note that this is not trivial to get right.
> Thus, if you think it's top priority, we should concentrate only on
> this at first. I would like to talk to Scott also about his changes.
> We should try to successively merge his stuff so as to make the
> Ubuntu people's job easier in the long run.

AFAIK the changes has been made by Matthias, Scott wrote the script
to publish the diff between ubuntu and debian packages.

However, I've prepared fixed zope/zopectl packages which depends on
zope-common (and so include the fixes by Matthias). Also, clean up=20
a lot of old bugs, small fixes, i18n updated templates and a
debconf-based initial admin user creation. Nothing has changed so
much, just a full clean-up of the package.

I've tested (not deeply) that here, but I'd like to receive some
feedback on upgrading from the package in sarge (I haven't machine
with zope installed).

After some review, we could upload zope-common and ask politely=20
ftpmasters to let zope-common enter unstable ASAP, and the upload
this fixed zope and zopectl packages: this should be enough for
sarge.

> For instance,
>=20
>   http://people.ubuntu.com/~scott/patches/zope/

> already contains the patch for #256615. I wish Scott would somehow
> name his patches to make them easier to identify.

=2E. based on zope-common. I've included them in my package.

> Anyway, a good way to go about this would be to obtain all of
> Scott's patches and to successively assess them to see in what stage
> they apply.

Most of those package has been applied to my packages (because they
use debhelper-zope and zope-common) on my personal repository.

> Right now, I see our roadmap as:
>=20
> 1. Close #256615. Do this sooner rather than later because
>    zope-common will be in NEW for some days anyway.

IMHO we should close that *with* zope-common.

> 2. Migrate all of Fabio's packages and all other stuff to an arch
>    repository. If I am to do this, I need to be added as a developer
>    to pkg-zope. Anyone? Note that Roland Mas already created the
>    arch space for us on my request.
>=20
> 3. Upload all the stuff using dzhandle/dh_zope to experimental and
>    get people to use it.
>=20
> 4. Set up a number of test cases to be able to assess the usability
>    of the new method on
>      - new 2.7 installs.
>      - 2.6 to 2.7 upgrades.
>      - 2.6 and 2.7 parallel installs.
>      - 2.6 installs which must remain at 2.6.
>    note that we should use a moderately complex site (e.g. maybe
>    a dump of plone.org) for the testing. Simple sites tend to work
>    in most cases. Anything more complex tends to fail a lot. This is
>    the problem we need to address!

Agree. We *need* the arch repository! :)

> How many times, and how much time has elapsed since you first tried?
> From what you told me, it seems like we can go ahead with a friendly
> takeover and leave Luca in the Uploaders field, should he ever want
> to pick up again.

In the last four months, I've emailed him three or four times: never
received answers.

> Could you start a list? Maybe we can use
>=20
>   http://wiki.debian.net/?ZopeMigrationScratch

I'm starting it.

Thanks,
Fabio

--=20
Fabio Tranchitella                         http://www.kobold.it
Studio Tranchitella Assoc. Professionale   http://www.tranchitella.it
_____________________________________________________________________
1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564

--LwW0XdcUbUexiWVK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCSaFTK/juK3+WFWQRAmigAJ9XAheETGaixOh2R8q8At0pD7BwLwCaAkTM
GcWop4MiThaY8KzUrsraJXA=
=nWoC
-----END PGP SIGNATURE-----

--LwW0XdcUbUexiWVK--