Hello, On Thu, Jun 19, 2014 at 08:50:33AM -0700, Joachim Breitner wrote: > Done: > $ grep ^nmu binNMUs.txt |grep -w amd64 > nmu haskell-yesod-persistent_1.2.3-1 . i386 sparc powerpc amd64 . -m 'missing libghc-warp-dev-3.0.0.1-1e258' > nmu haskell-wai-handler-launch_3.0.0-1 . i386 sparc s390x armel powerpc armhf amd64 . -m 'missing libghc-warp-dev-3.0.0.1-1e258' > nmu haskell-warp-tls_3.0.0-1 . i386 s390x armel powerpc armhf amd64 . -m 'missing libghc-warp-dev-3.0.0.1-41166' > nmu haskell-yesod-test_1.2.2-1 . i386 sparc powerpc amd64 . -m 'missing libghc-warp-dev-3.0.0.1-1e258' > nmu haskell-yesod-core_1.2.16.1-1 . i386 sparc powerpc amd64 . -m 'missing libghc-warp-dev-3.0.0.1-1e258' > nmu haskell-yesod-default_1.2.0-1 . i386 sparc powerpc amd64 . -m 'missing libghc-warp-dev-3.0.0.1-1e258' > nmu haskell-yesod-newsfeed_1.2.0-1 . i386 sparc powerpc amd64 . -m 'missing libghc-warp-dev-3.0.0.1-1e258' > nmu haskell-yesod-form_1.3.10-1 . i386 sparc powerpc amd64 . -m 'missing libghc-warp-dev-3.0.0.1-1e258' > > Note that I currently schedule binNMUs only for packages broken on > amd64, we can do the rest once we are consistent again. Thanks for this! Out of curiosity, where exactly do you issue those commands? I know the normal way is to submit a bug to the pseudo-package release.debian.org, but apparently[0] we the DHG do something different. [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750447#10 Greetings, -- Raúl Benencia
Attachment:
signature.asc
Description: Digital signature