-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi!
First off, thanks to whoever was responsible for me being accepted into the GSoC program and congrats to both Andrew and Paras for getting in, too! :) On Fri, May 05, 2017 at 08:27:34AM -0700, John Casey wrote: > Unfortunately, my Qubes project wasn't accepted John, sorry to hear your Qubes Manager proposal wasn't accepted. It really could use a generous dose of (not only) UI changes. So... I've spend the last few days setting up my dev env and getting familiar with qubes-builder. While skimming through issues on GitHub labeled as "minor" and "help wanted", searching for something quick and easy just to get a hang of the dev workflow, I haven't stumbled upon anything "right up my alley". Due to this, I decided to start working on my actual GSoC project instead (I hope it's not discouraged), implementing the first step as outlined in my project proposal -- the AEM install script is now able to generate, enroll and encrypt a LUKS key file and the sealing script then seals (duh) and copies it to the AEM media. You can find my fork of the AEM repo on GitHub under phagara. Now to my questions. :) 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. 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? Cheers, Patrik -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJZGusaAAoJEFwecd8DH5rlTFsQALtCO7EtmRWh6sDPlN2BOVdX lq9h1g4hc3GMvAkWaDEUItrU6Sszu8Oh7dicUuV9PD73sJ6WG+XaLOIbYlVxnaAv ZG149jZjTXmnh04kjMyM86WPoSrlJjmT+4bov/eafmwTKkDyMtv9sX9mzyfRixdm kNW2sJgL+RviEUwUrYYJi4oTd2c/PgeBiwZjhyyeb0VeEj7diwNdHDdJQj+pymU2 G4wtcsFQV6+EAwtI8qa580xYRcaSNUVE5RhYl3Tz4GG55KoWgHFWdfM9UiXaHrxD 2syRtgL8M2myiQnrJu092LDQOTuYa98v4H6gj42IAiGK3STP+egyJFQOkK7pqdlE wv2qRO66RBl9UfkbT+fShBli1eOkjrhXsgqCO/LKI6zWzDEbxVsRD89haWlPCTg9 DlZUWi64HQmqrdwbjTl6XEN24Etq6EYu94pfVOE0agAnyTLHMHBc+oZoPgeTam3O 5oHlrtXNi6qJc+pNgIFaP+Fh8x1KDftnXTT12GBja2Cf5MPv6aE8n5r6WquMJpwz 6peONSzMwkOGk69v8xl/oOtPE/csPxKu8GedeDeJzHkYRKyeY1k6Hs+IgKZOxkk+ tcB2sJRXdblVdn19p72/n01GFUpbTDWOQzDJ3zrV+96nO9vCH4I7PlJAn/447hOy T0bT2XFcyee8tJN4BqDm =zm3L -----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-GGs%2BF2kVUE5GDNhCKJvpfYtbrv0jh2EFWk5xt%2B%3DJuK0Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
