in my local version here; but I see no sense in uploading it, because it
won't fix the zope issue.
> It was 2.0.2-18. I will however reupload a new version of zope tonight.
> I need to fix a postinst. I let you know if there is a problem building
> your package. (I am using pbuilder to build my packages)
You should have used the -v switch... Do you plan an other NMU? Do you
think it's acceptable to upload a "debugging version" - it will take the
autobuilders time, but hopefully help us track down the problem.
Regards, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
Pierre Machard <email address hidden> wrote:
> Yes but in that case, find a conveniant way to repair broken
> installations.
I have implemented it, using a different approach,
db_fset/fget tetex-bin/ $changed_ question shown_again
in my local version here; but I see no sense in uploading it, because it
won't fix the zope issue.
> It was 2.0.2-18. I will however reupload a new version of zope tonight.
> I need to fix a postinst. I let you know if there is a problem building
> your package. (I am using pbuilder to build my packages)
You should have used the -v switch... Do you plan an other NMU? Do you
think it's acceptable to upload a "debugging version" - it will take the
autobuilders time, but hopefully help us track down the problem.
Regards, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie