Le 21/11/2018 à 23:04, Xavier a écrit : > > Le 21/11/2018 à 23:00, Xavier a écrit : >> Le 21/11/2018 à 22:57, Xavier a écrit : >>> Le 21/11/2018 à 22:51, Raphael Hertzog a écrit : >>>> On Tue, 20 Nov 2018, Xavier wrote: >>>>>> Unable to reproduce now, this bug seems fixed now. I'm going to provide >>>>>> a new .deb after adding other requests. >>>>> >>>>> I built a new .deb: >>>>> http://people.debian.org/~yadd/devscripts_2.18.10_amd64.deb >>>> >>>> It's actually worse. I'm attaching my pkg-security.conf and here's the >>>> call I'm doing: >>>> >>>> $ salsa --conf-file +./pkg-security.conf check_repo --debug --verbose --all >>>> salsa info: Found 7 projects >>>> grub: >>>> email-on-push missing >>>> irker missing >>>> tagpending missing >>>> debian.org: >>>> email-on-push missing >>>> irker missing >>>> tagpending missing >>>> ^C >>>> >>>> Those packages are not part of pkg-security... >>>> >>>> My .devscripts has this: >>>> $ grep SALSA ~/.devscripts >>>> SALSA_TOKEN_FILE=/private/config-sensible/salsa-token >>>> $ cat /private/config-sensible/salsa-token >>>> SALSA_TOKEN=xxxxxxxxxx >>>> SALSA_URL=https://salsa.debian.org/api/v4 >>> >>> SALSA_URL here isn't read. Set it in ./pkg-security.conf or .devscripts >>> if you want to overwrite default value (not needed)
salsa looks only for a token in /private/config-sensible/salsa-token. Any other values are ignored >>> I don't see any SALSA_GROUP in your conf file, so salsa looks at your >>> forks. The "grub" project seen above is "hertzog/grub" which exists ;-) >> >> Seems to work fine with "SALSA_GROUP security-tracker-team" (not really >> tested since I've no rights on this group but tested on another group) > > SALSA_GROUP=security-tracker-team > > or > > SALSA_GROUP_ID=2102 > >>>> (I just replaced the token, the rest is exactly as-is) >>>> >>>> Cheers, >>
