Status

Differences between revisions 135 and 136
Revision 135 as of 2020-08-28 15:01:47
Size: 3877
Editor: rbalint
Comment: orcania & hoel seem to be solved
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] autopkgtest-cloud: retry on some frequent intermittent failures [[https://code.launchpad.net/~rbalint/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/384609|review]]

+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-09-11 10:13:19 by rbalint)