Hey Seth,

While I agree with this goal, I don't feel this is realistic without a focused 
effort within the distro itself as a global goal as I explained in detailed in 
my answer:
- most of those deps are shared between snapd, juju, ubuntu-report and zsys at 
least (like the yaml config parser). All of them are using vendoring. I don't 
feel we should only have the new entree separately or the other will never be 
ported, and so, we will have no gain doing that work.
- I don't feel it's fair and realistic to have zsys doing this work alone for 
the eoan time-goal while it was ok for the others to skip this process. (Hence 
the "should that be a goal for the LTS?"). Note that between direct and 
transitive deps, we have 31 packages to MIR.
- As stated before, even if zsys we were doing that work for zsys, MIRing all 
dependencies, we are not sure that other projects like snapd could transition. 
Indeed, most of those modules are version 0.x, and they are breaking their API 
quite regularly. So the version zsys is compatible with wouldn't be the version 
snapd, or juju, or ubuntu-report will be compatible with.

Is there a way to set that to a particular release goal and answer all
the above?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839271

Title:
  [MIR] zsys

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1839271/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to