bug#40029: Preventing automatic python2 transformation of some packages

2020-07-25 Thread Marius Bakke
Ludovic Courtès writes: > Hi! > > Marius Bakke skribis: > >> 'python2-sphinx' is obsolete and increasingly a maintenance burden, >> because we need to keep special versions around just to make it build. >> >> The only reason we have this package is because it gets pulled in >> automatically when

bug#40029: Preventing automatic python2 transformation of some packages

2020-03-12 Thread Ludovic Courtès
Hi! Marius Bakke skribis: > 'python2-sphinx' is obsolete and increasingly a maintenance burden, > because we need to keep special versions around just to make it build. > > The only reason we have this package is because it gets pulled in > automatically when using (package-with-python2 ...) on

bug#40029: Preventing automatic python2 transformation of some packages

2020-03-12 Thread Leo Prikler
> The only reason we have this package is because it gets pulled in > automatically when using (package-with-python2 ...) on a Python 3 > package that has 'python-sphinx' in inputs. I think the problem here, is that (package-with-python2 ...) overwrites all sorts of inputs per package-mapping. Per

bug#40029: Preventing automatic python2 transformation of some packages

2020-03-11 Thread Marius Bakke
Guix, 'python2-sphinx' is obsolete and increasingly a maintenance burden, because we need to keep special versions around just to make it build. The only reason we have this package is because it gets pulled in automatically when using (package-with-python2 ...) on a Python 3 package that has 'py