Hi, Am Samstag, den 30.05.2009, 10:47 +1000 schrieb Erik de Castro Lopo: > I'm a new maintainer and my first haskell package is haskell-curl > version 1.3.5-1 which my sponsor uplaoded on May 18th, a day before > Kari Pahula uploaded the new 6.10.3 compiler. > > Its my understanding that to kick off a rebuild of my package with > the new compiler I basically need to upload a new version. Now, if > the upstream version (1.3.5) hasn't changed, but the package > metadata has changed I should just increment the version from say > 1.3.5-1 to 1.3.5-2. > > However, if there has been neither an upstream version change, nor a > metadata change, is there some recommended way to signify this in the > package version number? If you upload a new version, you should build-depend on ghc6 (>= 6.10.3) to make sure your package is not auto-built on an architecture that hasn’t successfully built ghc6 yet. I assume that haddock (>= 2.4.2) is a good idea as well. But note that you do not need to do a sourceful upload to have your package rebuilt. It is enough to send a mail to debian-release@d.o, saying: =================== Hi, here are some more packages that need to be rebuilt against the new ghc version: nmu haskell-curl-1.3.5-1 . ALL . -m 'Rebuild against GHC 6.10.3' dw haskell-curl-1.3.5-1 . ALL . -m 'haddock (>= 2.4.2), libghc6-network-dev (>> 2.2.0.1-4)' =================== But then I notice that haskell-network is not yet updated, and no binNMUs were requested, which means that you cannot build haskell-curl yourself anyways. @kaol: Is that an oversight or is there a reason for not binNMUing haskell-network? Greetings, 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