Hello, On Tue 26 May 2020 at 07:41PM +00, PICCA Frederic-Emmanuel wrote: > Hello Sean > >> I'm currently working my way through `dht what-to-upgrade | xargs dht >> upgrade` -- you can do some of that too, but please coordinate on IRC as >> we need not to be trying to do it at the same time. > > How long does it takes on your machine to run a make-all ? Haven't done it for a while, so not sure, sorry. Probably a long time. >> I have a propellor config to produce a machine like this and some >> credits which were donated by Exoscale for DHG to use. Shall I fire it >> up? Send me an SSH public key. > > I will have acces to an amd-ryzen-threadripper-3990x at my work, next week > So I will see how long it takes to rebuild all the haskell stack :). Cool. > The problem I see is that as Debian Developper we should have a dedicated (porter box ?) hardware > with lot's of memory and core where we can run dht what-to-upgrade | xargs dht as a team. > > do you think that it could be interesting to ask the salsa guyes a dedicated runner in order to create a > customizer pipeline for dht ?, and how to obtain the artefacted (a huge number of artefact in order to do the upload...). > > Maybe a shared dedicated hardware should be the best solution, with maybe a common account to run dht on only one account ? I don't think we should be making commits to our repos from machines we don't personally control. Porterboxes are generally considered to be insecure, suitable for testing things, but not as part of the package delivery pipeline. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature