[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: haskell-cryptocipher (+yesod) entangled with pandoc



On Wed, 2012-07-25 at 19:47 +0100, Adam D. Barratt wrote:
> On Mon, 2012-07-23 at 23:14 +0200, Joachim Breitner wrote:
> > A fixed pandoc has been uploaded (1.9.4.2-2)
[...]
> Ignoring tests and the Slideous stuff makes it a little happier to look
> at, although it's still larger than I'd like.  Unblocked in any case,
> let's hope it doesn't need any more help to get things unbunged.

Following on from a discussion on IRC this morning, the stack including
pandoc is not currently in a position to migrate, and some of the
packages that have been blocked behind pandoc will lose their
auto-exceptions soon.

With pandoc aged, britney attempts two auto-hints.  The first is small -
highlighting-kate,gitit,pandoc - and fails due to breaking
libghc-hakyll-{dev,prof} on several architectures.  haskell-hakyll
appears to have been binNMUed already, but the binNMUs are waiting for
haskell-cryptohash, which is waiting for (at least) haskell-cereal and
haskell-crypto-api. 

With apologies for the noise... The larger auto-hint ends up
considering:

highlighting-kate gitit pandoc haskell-yesod-markdown
haskell-hakyll/kfreebsd-i386 haskell-hakyll/amd64 haskell-hakyll/i386
haskell-hakyll/kfreebsd-amd64 haskell-yesod-core haskell-yesod-form
haskell-yesod-json haskell-yesod-default haskell-yesod-persistent
haskell-yesod-auth haskell-yesod  haskell-cereal haskell-clientsession
haskell-yesod-static haskell-http-conduit haskell-authenticate
haskell-socks/kfreebsd-amd64 haskell-puremd5/kfree bsd-amd64
haskell-puremd5/s390 haskell-pem/mips haskell-puremd5/armel
haskell-socks/mips haskell-socks/kfreebsd-i386 haskell-skein/armhf
haskell-acid- state/i386 haskell-acid-state/kfreebsd-amd64
haskell-pem/i386 haskell-acid-state/amd64 haskell-acid-state/sparc
haskell-pem/armhf haskell-crypto-api/k freebsd-i386 haskell-skein/s390x
haskell-socks/armel haskell-cryptohash/powerpc
haskell-openpgp-asciiarmor/s390x haskell-crypto-api/armel haskell-cryp
to-api/mips haskell-crypto-conduit/mipsel haskell-pem/powerpc
haskell-pem/s390x haskell-safecopy/kfreebsd-i386
haskell-cryptohash/sparc haskell-puremd 5/armhf
haskell-crypto-conduit/mips haskell-skein/i386
haskell-crypto-api/powerpc haskell-pem/s390 haskell-socks/armhf
haskell-acid-state/kfreebsd-i38 6 haskell-puremd5/amd64
haskell-socks/amd64 haskell-socks/powerpc haskell-crypto-conduit/sparc
haskell-skein/sparc haskell-crypto-api/sparc haskell-sk
ein/kfreebsd-amd64 haskell-skein/powerpc haskell-puremd5/mipsel
haskell-pem/kfreebsd-amd64 haskell-crypto-conduit/s390x
haskell-openpgp-asciiarmor/pow erpc haskell-skein/s390
haskell-crypto-api/armhf haskell-socks/s390x haskell-crypto-api/s390
haskell-puremd5/i386 haskell-openpgp-asciiarmor/mipsel ha
skell-openpgp-asciiarmor/mips haskell-safecopy/i386
haskell-openpgp-asciiarmor/armhf haskell-cryptocipher
haskell-safecopy/kfreebsd-amd64 haskell-pure md5/powerpc
haskell-crypto-conduit/powerpc haskell-crypto-conduit/armhf
haskell-openpgp-asciiarmor/sparc haskell-tls haskell-pem/armel
haskell-puremd5 /s390x haskell-crypto-conduit/s390 haskell-skein/mipsel
haskell-openpgp-asciiarmor/kfreebsd-amd64 haskell-cryptohash/s390
haskell-cprng-aes haskell-cr ypto-api/mipsel
haskell-cryptohash/kfreebsd-i386 haskell-puremd5/mips
haskell-puremd5/kfreebsd-i386 haskell-socks/i386 haskell-pem/sparc
haskell-crypt ohash/armhf haskell-safecopy/amd64 haskell-puremd5/sparc
haskell-skein/kfreebsd-i386 haskell-pem/amd64 haskell-cryptohash/armel
haskell-crypto-api/amd 64 haskell-socks/sparc haskell-crypto-api/i386
haskell-cryptohash/kfreebsd-amd64 haskell-openpgp-asciiarmor/s390
haskell-pem/mipsel haskell-openpgp-as ciiarmor/i386
haskell-openpgp-asciiarmor/amd64 haskell-crypto-conduit/armel
haskell-cryptohash/mips haskell-cryptohash/mipsel
haskell-pem/kfreebsd-i38 6 haskell-openpgp-asciiarmor/kfreebsd-i386
haskell-crypto-conduit/kfreebsd-i386 haskell-socks/mipsel
haskell-skein/amd64 haskell-safecopy/sparc haskel l-skein/armel
haskell-cryptohash/amd64 haskell-crypto-conduit/kfreebsd-amd64
haskell-cryptohash/s390x haskell-socks/s390 haskell-cereal-conduit
haskel l-crypto-api/s390x haskell-cryptohash/i386
haskell-crypto-conduit/i386 haskell-skein/mips
haskell-openpgp-asciiarmor/armel haskell-crypto-api/kfreebsd -amd64
haskell-crypto-conduit/amd64 haskell-dbus haskell-github
haskell-tls-extra haskell-wai-app-file-cgi haskell-warp-tls 

and breaking:

    * i386: libghc-ami-dev, libghc-ami-prof, libghc-authenticate-dev,
libghc-authenticate-prof, libghc-certificate-dev,
libghc-certificate-prof, libghc-clientsession-dev,
libghc-clientsession-prof, libghc-cprng-aes-dev, libghc-cprng-aes-prof,
libghc-crypto-pubkey-types-dev, libghc-crypto-pubkey-types-prof,
libghc-cryptocipher-dev, libghc-cryptocipher-prof, libghc-debian-dev,
libghc-debian-prof, libghc-github-dev, libghc-github-prof,
libghc-hoauth-dev, libghc-hoauth-prof, libghc-http-conduit-dev,
libghc-http-conduit-prof, libghc-ixset-dev, libghc-ixset-prof,
libghc-monadcryptorandom-dev, libghc-monadcryptorandom-prof,
libghc-pwstore-fast-dev, libghc-pwstore-fast-prof, libghc-rsa-dev,
libghc-rsa-prof, libghc-tls-dev, libghc-tls-extra-dev,
libghc-tls-extra-prof, libghc-tls-prof, libghc-unixutils-dev,
libghc-unixutils-prof, libghc-wai-app-file-cgi-dev,
libghc-wai-app-file-cgi-prof, libghc-wai-app-static-dev,
libghc-wai-app-static-prof, libghc-warp-tls-dev, libghc-warp-tls-prof,
libghc-yesod-auth-dev, libghc-yesod-auth-prof, libghc-yesod-core-dev,
libghc-yesod-core-prof, libghc-yesod-default-dev,
libghc-yesod-default-prof, libghc-yesod-dev, libghc-yesod-form-dev,
libghc-yesod-form-prof, libghc-yesod-json-dev, libghc-yesod-json-prof,
libghc-yesod-markdown-dev, libghc-yesod-markdown-prof,
libghc-yesod-persistent-dev, libghc-yesod-persistent-prof,
libghc-yesod-prof, libghc-yesod-static-dev, libghc-yesod-static-prof,
libghc6-debian-dev, libghc6-debian-prof, libghc6-hoauth-dev,
libghc6-unixutils-dev, libghc6-unixutils-prof

plus similar for the other architectures.  I don't know enough about the
stack to judge what needs doing to resolve this.

Regards,

Adam


Reply to: