Bug#964983: New Upstream Version
Hello, On Mon 13 Jul 2020 at 10:58PM +01, Barak A. Pearlmutter wrote: > Sometimes I wonder if Debian needs some serious process analysis and > restructuring. Should a new library version that happens to cross a major > version boundary really good though the same extra vetting queue that a new > browser goes through? I think in this case Clint meant that haskell-binary-instances would need to go through NEW, not the new github library. -- Sean Whitton signature.asc Description: PGP signature
Bug#964983: New Upstream Version
Sometimes I wonder if Debian needs some serious process analysis and restructuring. Should a new library version that happens to cross a major version boundary really good though the same extra vetting queue that a new browser goes through? tldr: What have we wrought???
Bug#964983: New Upstream Version
On Mon, Jul 13, 2020 at 09:05:28PM +0100, Barak A. Pearlmutter wrote: > There's a new upstream version available, and I cannot update the > github-backup package until libghc-github-dev (>= 0.23) is available. > So I hope to see the new version packaged. Someone would need to package binary-instances first, and then wait however many months until it gets through NEW.
Bug#964983: New Upstream Version
Package: libghc-github-dev Version: 0.20-2 Severity: wishlist There's a new upstream version available, and I cannot update the github-backup package until libghc-github-dev (>= 0.23) is available. So I hope to see the new version packaged. Cheers, --Barak.
