-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/2015 12:21 PM, Tianon Gravi wrote:
> Control: owner -1 tia...@debian.org
>
> On Thu, 17 Sep 2015 16:26:35 -0400 "Roderick W. Smith"
> wrote:
>> I'm rEFInd's upstream maintainer and a Canonical empl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/30/2015 05:22 PM, Tianon Gravi wrote:
> On 30 November 2015 at 11:31, Tianon Gravi
> wrote:
>> Oh nice; since it's working in QEMU, I'm personally all for
>> arch-enablement! :D
>
> Hmm, I tried compiling on an arm64 porterbox, and got the
> fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/30/2015 05:22 PM, Tianon Gravi wrote:
> On 30 November 2015 at 11:31, Tianon Gravi
> wrote:
>> Oh nice; since it's working in QEMU, I'm personally all for
>> arch-enablement! :D
>
> Hmm, I tried compiling on an arm64 porterbox, and got the
> fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've made some more packaging changes on my upstream Sourceforge git
repository. The debian/copyright file should be in good shape now
except for the outstanding question of Secure Boot public keys from
some sources. I've received an e-mail from Steve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm rEFInd's upstream maintainer and a Canonical employee, and I'm
interested in getting this packaged and the bug cleared.
I've done some Debian packaging, and in fact I've created an Ubuntu
PPA for rEFInd (see
https://launchpad.net/~rodsmith/+a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/06/2016 05:59 PM, Tianon Gravi wrote:
> On 6 April 2016 at 14:23, Tianon Gravi wrote:
>> This isn't really as important in the context of Debian, since
>> we'll supply a separate "debian/", but it's definitely nice to
>> keep them in parity, so
6 matches
Mail list logo
