[arch-dev-public] Todos for language specific rebuilds

[Anatol Pomozov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi

On 2020-01-12 at 00:04, arch-dev-public at archlinux.org wrote:
> On 1/10/20 4:42 PM, Christian Rebischke via arch-dev-public wrote:
> > Hi everybody,
> >
> > I would like to propose that we create todos for rebuilds of language
> > specific packages.
> >
> > We had two major rebuilds in the last months: python3.8 and ruby2.7.
> >
> > Can we agree that we create a todo before such rebuilds?
> > The advantages outweigh the disadvantages. We would gain:
> >
> > * More people help rebuilding the packages.'
>
> What help is needed? If this is just about having more people sed the
> pkgrel variable with "$pkgrel + 1", then try to build it, more people
> doesn't actually help. We have automated rebuilders which are very
> capable in this regard.
>
> > * Every maintainer gets informed about the rebuild.
>
> I agree with you that this is indeed a problem, and I would like to
> propose a pretty simple solution. Let's post on arch-dev-public to give
> people a heads-up.
>
> This means even if your package failed to be detected for rebuilding and
> would never appear on any TODO, you as a maintainer know that it
> happened and can manually rebuild your package.
>
> > * Maintainers have the possibility to test the packages.
>
> At least for the python rebuilds, the process of rebuilding the
> ecosystem is long and painfully drawn out, *because* packages with
> failing testsuites cannot be rebuilt automatically and go onto a TODO
> list of broken packages.
>
> Given this thread started because we just rebuilt ruby, can I assume
> that PKGBUILDs for ruby packages are in the general habit of not
> containing check() functions for running unittests? Either because
> upstream does not have unittests or because they are not being run?
>
> If packages have upstream unittests but don't run them, then the
> maintainer of the package has been derelict in his or her duty.
>
> If packages do NOT have upstream unittests, then this is unfortunate,
> and I don't currently have an answer for what we should do. :(
>
> > If tools exist for creating todos, I would like to ask the persons with
> > such tools to make them available for everybody (if not already
> > happened).
>
> It's a website submission form that expects you to write some
> explanatory message, then fill in a newline-separated list of pkgnames.
> Any rebuilder must by definition have the latter, even if that rebuilder
> is "I scrolled through archweb and did it all manually by flipping back
> and forth between my terminal and my browser".
>
> No "tool for creating todos" need exist. Ask instead about tools for
> enumerating language dependencies.
>
> ...
>
> For python, it's pretty simple.
>
> pkgfile -d '/usr/lib/python3.8/'
>
> For ruby, it's also pretty simple:
>
> pkgfile -d '/usr/lib/ruby/'
Here are the instructions that I used to find the ruby packages
https://gist.github.com/anatol/670a2768a97789d6a96b33010b7fedca
-----BEGIN PGP SIGNATURE-----
Version: FlowCrypt 7.4.2 Gmail Encryption
Comment: Seamlessly send and receive encrypted email

wsFcBAEBCgAGBQJeGmgKAAoJELAoVO11Pg8fwTsQAJtOyNvia5wXkkTsdjrQ
LLkLRw2EF79mMbJa+zN6/H7m/lJAIdZKXFjWmhar3lt+52d0J+7+WHPrqHH0
151hpuJ6SJpceGDkzbfIST9/i+++HcUB6a9vDcJPEx8RqYQFMPH/4JxGndCR
Dg7bi2f9PzmYsv9KkZ6JsJ13Z/jRfiVozGf0J9b+xi79Z5Y5RMM91Q2hp8gR
6HFRw+S8+0j5P+1MlDlSSjPmflvC3wsYDRqcDZuaXtArmqb1BiGAK6s6d4aQ
L11LQSdP8clgYfGPJpk4U37SDSyrkTaBM5yWQLPaKVB7DY2Z81OGd3Z34tMj
QWsh/LZjgqtEOl+WkGcF2ykSa+mjpdyxrttotDh6Mwwa+7YFNxWMQiSO8Hmd
Z1iI3SCzIhQ33t/3raE0MDSJM8nEQwwrkyI2nr0C2BFUEIwMkiRkcLr3KDwf
MQI3Q9X3A0Fo5xwzWcEEjbJjwjGz9fzPcDh0JeOUs/e9Ck1TL/n4qwqhPeUr
kJFrrzEAD6YcXCTdbudHFnbmrdDd0wdTpb2SAYZuKWhYusEMWn1oxDK6TnLe
5ufVTXP9uQyG5xoEUX95L4S0GAGqJ6jU9dY+B1TTfRZg+bG6nq+FdpverzHB
WVN9opo7WqL8sE1fifViBbWo20KV0BCv3vUyFFBYkCLVcoIWgeeLHFZUegmr
p/nl
=4pkk
-----END PGP SIGNATURE-----