Hi Frank, On Mon, 2017-09-11 at 16:30 +0200, Frank Doepper wrote: > Am 11.09.17 um 15:09 schrieb Stephan Sürken: > > > commit a37e69c2bc8371b57531f4e65e0b271bc3b20617 (HEAD -> master) > > However, I don't know if or how the other logs/findings you posted > > here > > relate to this. Maybe there is still another bug? > > > > Could you retest with that patch applied? > > The patch fixes the save-daemon bug, thanks for that. > > But the "NOT NULL constraint failed: mini_buildd_uploader.user_id" > when > trying to add a new uploader's key is still there.
are you trying to *add* an actual Uploader instance? If so, that is not possible. An Uploader instance is created automatically for any new User (one-to-one relation). The only thing you need to do as admin is to *change* Uploader instances that are already there. That's why in mini-buildd's custom config overview, the "add" button is deliberately missing. It's not feasible afaik to phase out any adding of instances via django's generic admin interface, so admittingly, it sort of offers something that does not work ;). So do you also have a problem *changing* an uploader instances with a new public key? Thx! S
