Hi again, Am Sonntag, den 24.05.2009, 18:49 +0200 schrieb Joachim Breitner: > Am Sonntag, den 24.05.2009, 15:11 +0200 schrieb Joachim Breitner: > > Am Sonntag, den 24.05.2009, 15:06 +0200 schrieb Joachim Breitner: > > > @d-haskell: This seems to affect most of our packages. So what do we do > > > about this? Revert to sourceful uploads again? Manually upload 1.4.5-3 > > > +b1 versions of the -doc packages (which won’t be allowed by .dak, I > > > guess)? Make -doc packages arch-dependent? > > > > Or: Make the dependency on ghc6-doc unversioned. This means that after a > > new upload of ghc6, the old -doc packages can continued to be used – or > > is it likely that links to base packages or the .haddock file format > > have changed? > > Or, at least to fix the situation now without doing sourceful uploads, > use recompilation NMUs as described in [1]: > * Get the source as it is in the archive > * Bump the changelog with a +b1 version (e.g. with dch --bin-nmu) > * Build the package with "dpkg-buildpackage -A" > * Rename the .changes file, e.g. from > haskell-x11_1.4.5-3+b1_amd64.changes > to > haskell-x11_1.4.5-3+b1_doc.changes > Otherwise dak will complain with > Rejected: haskell-x11_1.4.5-3+b1_amd64.changes: a file with this name already exists in the Done directory. > because of the amd64 buildd upload. > * Sign and upload this .changes file. > > I just did this with libghc6-x11-doc (sitting in incoming.d.o as we > speak) and it was accepted by dak. Never mind, this doesn’t word as the ghc6-doc-dependencies are hard-coded in the debian/rules file, so this can not be handled via a binNMU. This means that we will have to do sourceful uploads of all libraries... This makes me wonder why we generate the dependency only for the -dev package in dh_haskell_prep, and not for the -doc package as well. Could we please agree on a proper -doc package Dependency policy quickly and implement that in dh_haskell_prep/dh_haskell_depends? Open questions are: * Do we need to depend on ghc-doc (now that documentation is installed via triggers) at all? * If so, do we need a lower version bound? * If so, do we need an upper version bound? Which one? * Do we need to depend on the -doc packages of dependencies, and if so, do these need to be versioned? Thanks, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil