On Wed, Jun 3, 2020 at 10:32 PM Clint Adams <[email protected]> wrote:

> On Wed, Jun 03, 2020 at 10:10:05PM +0200, Christian Ehrhardt wrote:
> > I was wondering if you have a dependency graph, or an upload staging
> order
> > that you usually use for your uploads and that I could now apply to the
> > Ubuntu builds and rebuilds on the Ubuntu side.
>
> Once upon a time we used a dependency graph to order uploads.  I think
> we more or less abandoned that when we switched to mostly tracking
> Stackage LTS versions or when we developed the package-plan tooling or
> some other milestone I can't remember.
>
> The current situation is that
>     (a) Because of the haddock-interface change, every single package
>         needs a sourceful upload.  This isn't relevant for Ubuntu.
>     (b) All packages need to be updated to the version in the
>         package-plan, which generally corresponds to Stackage LTS 15.13.
>     (c) Both packages which do not need a version update and packages
>         which do need to be upgraded also need patching because we do
>         not automatically apply Hackage metadata updates which help
>         keep Stackage consistent.
>     (d) All new packages pulled in as dependencies of the new versions
>         need to be packaged, and get processed through NEW.  Some of
>         these packages have been stuck in NEW for weeks, but most of
>         them have not been packaged at all.
>     (e) Build/test failures need to be addressed.
>
> > Sure I could just retry all of them in loops, but that would be a waste
> of
> > computer time, so if there is some ordering that would make sense please
> > let me know.
> >
> > OTOH - if many of these are even expected fails (could be) and there are
> > other uploads coming to fix it, let me know as well and I'll just step
> back
> > until you tell me it is expected to work.
>
> Judging by the current rate of progress, I think it will be quite a while
> before all the Haskell packages in unstable are buildable.
>

Thank you so much Clint for summarizing the current state!

In that case I can't really help much right now. I can't help:
- you as I'm a haskell-noob
- the packages in Ubuntu as we just have to wait until (a-e) as you
outlined come together correctly.

Any upload that you do will be auto-synced to Ubuntu and tried there
anyway, so for now we will follow what you do in Debian to resolve this
without further action.

FYI - since I was checking test results, build dependencies and build
results the two cases that seemed not to be "just build dependencies" are:
- riscv64 FTFBS [1] (it seems we have the risc build dep, while on [2] it
seems Debian hasn't)
- autopkgtest issues for GHC [3]. Since eventually everything will lock on
GHC to migrate together this needs to be fixed sooner or later.
  - currently these all seem to be related to haddock-interface [4][5][6],
but once that is resolved the tests might need a retriggering

Once you think Haskell is in an overall good shape again
with all pieces of the puzzle matching each other and things should build
let me know.
I can then recheck if - by then - Ubuntu needs to trigger any rebuilds or
tests for it.

[1]: https://launchpad.net/ubuntu/+source/haskell-text-icu/0.7.0.1-13
[2]: https://buildd.debian.org/status/package.php?p=haskell-text-icu
[3]:
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ghc
[4]:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/h/haskell-hoogle/20200529_174423_46e79@/log.gz
[5]:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/h/haskell-hoogle/20200531_123812_25053@/log.gz
[6]:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/h/haskell-hopenpgp/20200529_174439_ae2a1@/log.gz

-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

Reply via email to