Bug#715426: Bug # 715426: Interested in getting this done
-----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 Langasek stating that
these keys aren't copyrightable, which is why there's no such claim on
the Canonical key; but I'm not sure how to express that in
debian/copyright. In a worst-case scenario, we can drop the Microsoft,
ALT, and Canonical keys from the Debian package.
I've also added some basic debconf support. The package tools should
now ask whether to install rEFInd to the ESP when the package is
installed or reconfigured. (I've tested this and it works for me.) If
somebody else could review this, I'd appreciate it. This could be
improved in the future, but for now I think it's a good start.
Upstream, I've replaced debian/changelog with the version I use on my
PPA. I realize the Debian package will need something else. I need to
review how patches to the debian subdirectory are usually handled for
situations like this.
- --
Rod Smith
Server and Cloud Certification Engineer
rod.smith@canonical.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJWaJe/AAoJEFgyRI+V0FjmvT0IAJIKXcvQxVns6KXGqAlrveL6
vYo7Vj61enGQjemZuI7C405GCNfv51bKku78kh/hDrhhWxcnTVik5jIa4BD8xkHY
z0PkFpAMsUaOeDb35+fr8osV9ISJr/i1nlLxdLNdopA8DhigCwF5Kp+6PyzbafN5
QNosxniowXKKnIXy3aiv/ClLHCWKQ89pgKgWjGgSUZE0b7ZU4Dg95pjeXfKtQydy
LdNUQYKngs+11MrLsVIdAnR0ERzXobIVSQz0W2ZH7QhjeTip6HfSj405Z2ebeCYJ
9vw2gdHGwEU44QGIwbVvMIqgJXeOba3UclvVC1Qq0k0McPIb7VgG12GMpNcxd9A=
=jbiK
-----END PGP SIGNATURE-----
Reply to: