Status

Differences between revisions 124 and 136 (spanning 12 versions)
Revision 124 as of 2020-06-30 08:47:11
Size: 5039
Editor: sil2100
Comment: The r transition is done
Revision 136 as of 2020-09-11 10:13:19
Size: 3697
Editor: rbalint
Comment:
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:
 * [rbalint] (needs review) retry-autopkgtest-regressions improvements (retry based on log regex, don't retry queued/running)
 [[https://code.launchpad.net/~rbalint/ubuntu-archive-tools/retry-intermittent/+merge/384468|review]]
 * [rbalint] (needs review) autopkgtest-cloud: retry on some frequent intermittent failures [[https://code.launchpad.net/~rbalint/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/384609|review]]
 * [rbalint] (needs review) Switch Britney hints to git [[https://code.launchpad.net/~rbalint/britney/hints-ubuntu-bzr-to-git/+merge/386139|review]]
 * [bdmurray] 2020-06-29 python3-scipy (src scipy) autopkgtest regression on ppc64el
 * [rbalint] Switch Britney hints to git [[https://code.launchpad.net/~rbalint/britney/hints-ubuntu-bzr-to-git/+merge/386139|review]]
Line 34: Line 30:
  * ubuntu-app-launcher, url-dispatcher, unity fallout
    Who to approach to remove those? xnox will look into them
    * bug number please? I see just an FTBFS on riscv64.
Line 40: Line 35:
    * this is blocking some potentially useful packages
Line 44: Line 38:
 * golang-github-miekg-dns, which is blocking golang-github-hashicorp-memberlist: integer overflow on armhf: https://github.com/miekg/dns/issues/1129, https://bugs.launchpad.net/ubuntu/+source/golang-github-miekg-dns/+bug/1884152

 * [[https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#golang-yaml.v2|golang-yaml.v2]]: upstream golang issue https://github.com/golang/go/issues/39651. If we really need to get golang-yaml.v2 migrated before a fixed golang hits the archive, we can apply this workaround patch: https://bugs.launchpad.net/ubuntu/+source/golang-yaml.v2/+bug/1883770/comments/4
Line 50: Line 40:
  * haskell-* seems like mass-FTBFS
    * [cpaelzer] this is due to a change in haddock-interface, per coordination with Debian the following need to be resolved first. I've asked to be pinged once things are ready to re-trigger builds/tests on Ubuntu as needed. That will be visible on [[https://lists.debian.org/debian-haskell/2020/06/msg00003.html|their ML as reply]] and I'll ping the current +1 duty people.
      * Because of the haddock-interface change, every single package needs a sourceful upload. This isn't relevant for Ubuntu.
      * All packages need to be updated to the version in the package-plan, which generally corresponds to Stackage LTS 15.13.
      * 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.
      * 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.
      * Build/test failures need to be addressed.
  * haskell-* seems like mass-FTBFS and build-dependency need
    * [cpaelzer] (snip remove old details ...) Per coordination with Debian several things need to be resolved first [[https://lists.debian.org/debian-haskell/2020/06/msg00003.html|their ML as reply]].
      * The above was early ~June, many but not all things are resolved by now (early August)
    * haskell-haskell-gi-base was downgraded for now which makes many haskell things show up as wait-on-dep
      * unblocking these would conflict with ICU, do not touch them yet
      * after ICU is done syncpackage 0.23 of haskell-haskell-gi-base to get many haskell builds and tests
        going again
    * On Aug 11th then:
     [18:53] <vorlon> cpaelzer: fyi after yesterday's conversation (and britney nagging me about a number of
     packages that I "uploaded" being stuck in -proposed too long ;), I am going ahead and rolling forward the
     various haskell packages that had been rolled back, after confirming they're not entangled with any current
     transitions. (e.g. the haskell-gi-* stuff can't be since it was all removed from release pocket)

+1 Maintenance Status

Proposed Migration

Known issues

In progress

Items that are being actively worked on. Please always mention the name / irc nick, who is working on that.

  • [rbalint] Switch Britney hints to git review

Things to pick from

These are issues that are not yet done, after somebody's rotation/shift ended. Or someone has spotted them but had no chance to work on it. If someone trying to pick them realized that it was resolved by time/someone-else please be so kind and remove the related entries.

  • Ongoing transitions
    • there are plenty of rust packages stuck in -proposed. Unfortunately the rust packages we sync from Debian are not generally in a consistent state allowing migration (to Debian testing or to the Ubuntu release). If someone takes a look at these, they will probably want to recommend removals of various leaf packages blocking transitions.
    • vcmi ftbfs, pinged xnox about it, boost 1.71 related
      • bug number please? I see just an FTBFS on riscv64.
    • rust-* some test and many "unsatisfiable depends", one needs to check how this was meant to work ...
      • the rust packages only build if uploaded in a very precise order, which they were to debian but the debian import freeze messes this up for us
      • it's not clear that any of these packages help users of Ubuntu at all, so putting effort into these packages has a low ROI IMO (I == mwhudson)
    • there is a mess of go packages that needs unpicking. It's the sort of thing where we/Debian has updated one package to a given version, but some of the rdeps upstream are still pinning an older version.
    • autopkgtest for r-cran-* is in excuses quite often, this needs to be checked and probably custom test triggers (there also is a whopping 1.8k r-cran-* tests in http://autopkgtest.ubuntu.com/running atm)

    • perl micro update 5.30.3 - On Monday there was another upload of 5.30.3-4 and someone overzealously removed all perl tests. Cpaelzer/xnox/Laney re-triggered the tests the results ahve to be re-checked.
  • Not ready yet
    • haskell-* seems like mass-FTBFS and build-dependency need
      • [cpaelzer] (snip remove old details ...) Per coordination with Debian several things need to be resolved first their ML as reply.

        • The above was early ~June, many but not all things are resolved by now (early August)
      • haskell-haskell-gi-base was downgraded for now which makes many haskell things show up as wait-on-dep
        • unblocking these would conflict with ICU, do not touch them yet
        • after ICU is done syncpackage 0.23 of haskell-haskell-gi-base to get many haskell builds and tests
          • going again
      • On Aug 11th then:
        • [18:53] <vorlon> cpaelzer: fyi after yesterday's conversation (and britney nagging me about a number of packages that I "uploaded" being stuck in -proposed too long ;), I am going ahead and rolling forward the various haskell packages that had been rolled back, after confirming they're not entangled with any current transitions. (e.g. the haskell-gi-* stuff can't be since it was all removed from release pocket)

PlusOneMaintenanceTeam/Status (last edited 2020-10-21 18:41:40 by rbalint)