[Pkg-postgresql-public] Dropping postgresql 8.3 for squeeze

Gerfried Fuchs rhonda at deb.at
Mon Jan 11 10:25:22 UTC 2010

* Martin Pitt <mpitt at debian.org> [2010-01-11 11:08:27 CET]:
> Julien Danjou [2010-01-11 10:28 +0100]:
> > Is there any change to regenerate d/control at build-time?
> That's utterly crackful, and wouldn't even work. The buildds unpack
> the .dsc, the install build dependencies according to debian/rules,
> and then runs debian/rules. If this then changes build dependencies,
> it's too late.

 That part could get waived - that's what the common dev package is
suggested for which would depend on the versioned dev packages.

> Likewise, if the source package claims to build postgresql-foo-{X,Y}
> but doesn't actually build them, you'd horribly confuse the
> archive/NEW processing, etc.

 _This_ actually is the core problem. The source from which the package
is built claims at extraction stage to build a completely different set
of packages than it actually would produce afterwards. I actually think
that there are hooks in sbuild or dak or similar sanity checking tools
that would catch that and block the upload.

 So a source-full upload _is_ needed for transitions that produce a
different set of binary packages. I can't see how this part would be
possible to get worked around.

 So long,
Rhonda [but I am only the devil's advocate and objecting to any
   enhancement anyway, so feel free to rant against me again]

More information about the Pkg-postgresql-public mailing list