-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Tue, May 16, 2017 at 03:32:41PM +0200, Marek Marczykowski-Górecki wrote: > Unfortunately, as new GSoC org, we didn't get as many slots as we > requested, so we were forced to reject some, even good proposals.
Ah well. I hope you get more and more slots in the coming years -- Qubes definitely deserves a lot more "attention" (and mainstream adoption) than it's getting. > > Due to this, I decided to start working on my actual > > GSoC project instead (I hope it's not discouraged), > > Yes, that's fine. If you finish early, we can always extend the project > ;) Assuming it keeps going this smoothly and I get to finish even the TOTP token auth stretch goal, then sure. :) > > Is there a preferred way of dealing with forked repos > > under qubes-builder? Right now I've simply added a new > > remote for the antievilmaid component and I'm assuming > > simply running `make prepare-merge` and subsequently > > `make do-merge` should do the trick when the upstream > > repo has new, non-conflicting commits. > > Yes, exactly. Alright. > > As far as RPM package signing goes -- I guess it's not > > even worth setting that up for development since the > > only person installing the pkgs built by me would be > > just myself, in which case the signature would serve > > no practical purpose. Am I right? > > If you install packages on the same machine as you build them, then yes. > But if you transfer them using some untrusted channel (network or such), > signing may be useful. All you need for that is to have some key > generated, and adjust builder.conf: SIGN_KEY=<key-id>, NO_SIGN=0. Same machine, yeah. I tried to set up split-GPG signing but couldn't get it working and eventually decided to skip it since there would be no benefit in my case, anyway. Now, after a fair bit of debugging, I found out it was simply a silly typo -- writing the RPM macro config to `~/.rpmmacro` instead of `~/.rpmmacros`. All that's needed now is to `rpm --import` my public key in dom0 and I can start verifying my own RPMs. Too bad I only have one Qubes machine. :) > Pro tip: if you work on a single component (or some subset of them), you > can adjust COMPONENTS in builder.conf to include only what you need. It > will make things a lot faster. Yes, I was building just the AEM component pkgs, although with `make antievilmaid` (and now even `make sign-antievilmaid`). ;) Cheers, Patrik -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJZGxEMAAoJEFwecd8DH5rlL2gP/RhMSgoqcIT2tjlUDOjAif3u vgLuSwZy31EKsJquq13IxESo+WMb2Yozw43L58jIauNKPNZ3GvoEMhDkul0wMxzo 8SsatfIJCcoUkeulX+jqKtL3zwWw+Pl2C1HJzcQJ7xDK60L3ozjawIwSt7SJiPQp Wmb9S9iVkQRA+5SIIYrqWRr+Vf01FT8q9kDYJ5KkmEEpFlCwTAMb23NbduNQ9Rf1 B6r9ed5C9Nxr1nZOvpSP2JCJgyYyysl7P2UrIWf9xhR9Th0TcumAb3/cjSZBkSud wBodYyNSD1qwMPSIYxa/D8uuLJkmdOWHl8zCCqVH4ybfE2Gakpk5VKSYF4f21yBo ZIXSBqks0jV14xZAGjm00/nX9ad3/O18jBzIpskd6MFAk14zAsm5bRSvGHKJAsye 0wdUxuhLRitDznNokkWGB6tJ2VRvC/ZtZLghxxSV6o5ScDUkqZu82Zyd0GzI6gpu N8C6jui5K0FQ6EMX+kjy5II9WxVc0XWvwauEZnqI8SZnWu2KkIgrC5xRYUrlymcl d7WZPGxF5ngK/OHKvpAnX47CS9qxOsEiVsPdMw0vzjNApHfBnAi/zQn2OioFWOy5 pHmjqd0G7CL5WUcW7a27KYUrz56LbpVvesaqTfgPW6MqR20TwOILX73c73UbxX36 ooGF7tR26q2VmL8lKURH =g1jD -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/CAFfni-Fb0kxZ3n0R1q5YWTVec6yLTkrfCGJxHsU8m6nArg_pRA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
