Hi Baptiste, On 26/07/20 at 10:39 +0200, Baptiste BEAUPLAT wrote: > Package: qa.debian.org > User: qa.debian.org@packages.debian.org > Usertags: udd > > Hi, > > mentors.debian.net has changed its framework and its database schema. > The UDD importer named `mentors_gatherer.rb`[1] is not compatible with > this new schema and will stop working. > > See the new proposal for the mentors UDD tables (attached to this mail): > > - mentors-core-schema.dot: The core schemas of mentors with all data > tables (without internal django stuff) > - mentors-useful-table-schema.dot: A proposal of tables that could be > used by the UDD gatherer to import data from > - mentors-udd-schema.dot: A proposal of tables that could be used by the > UDD gatherer to import data to > > Once we agree on the new schema for UDD for the mentors tables, I'll be > happy to provide a patch for the gatherer and the schema. > > Note that currently the password of udd postgresql mentors account lives > in cleartext, in the gatherer, in the repository. Thus, I'm disabling > immediately that access. I'll provide the new password but that will > have to stay out of the repo. > > [1]: https://salsa.debian.org/qa/udd/-/blob/master/udd/mentors_gatherer.rb I think that it would be better if mentors.d.n would provide a JSON export of its data that it useful for UDD. Regarding data that should be replicated in UDD, I would prefer something simpler that is enough, typically for DMD, to notify that there's a new version waiting, but that still requires going to mentors.d.n for details. I wonder if we should have more than one table, that just describes the last upload for a given source or (source,user) (it's not clear to me if several users can simultaneously upload competing versions of the same source package). Lucas
Attachment:
signature.asc
Description: PGP signature