> > 5) We can develop tooling to detect when Debian contains two > > projects vX > > and vY where Y>X from the same upstream, and file a > > Severity:important > > bug on the vX package asking that all consumers of the package > > should > > file upstream bug reports asking upstream to migrate to vY (or > > later). > > Probably more issue if upstream uses both X and Y. > > And here is an example that upstream is using more than only X and V: > https://github.com/throttled/throttled/blob/v2.15.0/go.mod
I assume you mean:
require (
github.com/go-redis/redis v6.15.8+incompatible
github.com/go-redis/redis/v8 v8.4.2
Yeah, that is clearly bad, and worthy of an upstream bug report.
Still, with out proposed multi-vX scheme, it won't be a problem to
support in Debian.
There is potential for problems if two package A and B depend on
different versions of library X and those are in the same namespace.
This happens from time to time too, but almost always a real upstream
issue to resolve (although upstream priority to these issues isn't
always ideal).
/Simon
signature.asc
Description: This is a digitally signed message part
