Hi Marc, On Do, 2015-06-18 at 13:20 +0200, Marc Haber wrote: (...) > first thanks for the mini-buildd rewrite. This looks vastly better > than the 0.9 series, especially regarding documentation.
thx, but it's obviously still lacking. > However, the quickstart does not explain the role of an uploader too > well. Checking and activating the default uploader didn't work (the > text looked like some variable wasn't initialized), so I deleted it. > > Adding a new uploader fails. I exported the public key: yep, that isn't really well explained. You should not delete (or add) Uploader instances yourself, they are created automatically for each user (this is why, in the admin overview page, I patched away the "add" button, but it's not really feasable to patch it away from the whole django admin thing ;). I have updated the Quickstart to hopefully make this more understandable. See http://mini-buildd.installiert.net/doc/quickstart.html#epilogue http://mini-buildd.installiert.net/doc/quickstart.html#authorize-yourself-to-do-package-uploads for a preview. > [2/391]mh@spinturn:~$ sudo -H -u mini-buildd gpg --list-secret-keys (...) > Clicking "Save" leads to an "500 Internal Server Error: Sorry, > something went wrong" without any further explanation. Just ftr, when you set something like this (via dpkg-reconfigure) --verbose --verbose --debug=exception,http,webapp I am pretty sure you get a django trace with something moaning about missing user id or such. > What did I do wrong? Don't add or delete Uploader instances. Could you check if that (newly described) workflow works for a newly created user? Thx, S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
