As an update on this, I've gotten acmetool 0.2 to build on buster. The
following packages need backporting:
- golang-github-gofrs-uuid
- golang-golang-x-xerrors
- golang-github-google-go-cmp
- golang-gopkg-square-go-jose.v2
- golang-gopkg-hlandau-acmeapi.v2
- acmetool
The 5 golang-* packages are
On Sun, 2020-08-09 at 20:22 -0400, Peter Colberg wrote:
> Please feel free to go ahead with backporting acmetool and needed
> golang dependencies to buster.
Thanks for the approval, Peter! We'll backport and follow-up with the
go-team if there are issues.
Cheers,
Ralph
signature.asc
Descriptio
Hi,
I wanted to request approval from the maintainer team to upload the
acmetool 0.2.1-2 package currently in testing/unstable to buster-
backports.
The version currently in buster (0.0.63) only supports the deprecated
ACME v1 protocol, which no longer works for new registrations, and will
stop w
Please backport the 0.2.1 package from bullseye to buster. The 0.0.62
package currently in buster no longer works for new installs, and will
stop working for renewals of current domain certificates in July 2020.
The 0.2.1 tag of acmetool is two years old and should build with the
golang 1.11 packa
On 2015-12-10 12:19 PM, Luca Bruno wrote:
> We had an informal discussion on IRC a bunch of days ago, and we
> now feel confident enough to let rustc+cargo into testing. rustc
> 1.5.0 has been tagged today, and together with cargo 0.6.0 we plan
> to let them migrate to testing.
Thanks Luca and
On 2015-12-10 10:58 AM, Sylvestre Ledru wrote:
> I will be at the meeting [1] in 30 minutes :p , we can discuss about
> that if you want :)
I'll be there too, but there may not be time after gecko requirements
for rust and rust requirements for the gecko build system and...
But we should talk re
On Tue, 26 May 2015 00:15:50 +0200 Luca Bruno wrote:
> Even though Rust recently reached the 1.0 milestone, compiler and
> ecosystem packaging still has to reach a "ready for the masses"
> status.
What needs to happen to resolve this bug?
We're starting to use rust code in Firefox, and I'd like
On Mon, 29 Jun 2015 11:32:43 -0400 Martin Michlmayr wrote:
> You're using the "H" float option. According to
> https://en.wikibooks.org/wiki/LaTeX/Floats,_Figures_and_Captions
> you need \usepackage{float} for that, but it seems simpler solution
> is to replace it with "!h".
Thanks for the rep
On Mon, Jan 24, 2005 at 05:43:04PM -0800, Josh Coalson wrote:
> because of the mess and since there have been API changes and
> additions in both libFLAC and libOggFLAC since 1.1.1 I plan on
> bumping all the libtool numbers as follows: current++, revision=0
> age=0. if this will cause problems p
On Tue, Jan 25, 2005 at 12:59:59AM +, Dafydd Harries wrote:
> Ok, I'd be happier if I knew of some ways I could perform QA on the
> modifications which I make.
>
> How would I go about checking the metrics?
Use Fontforge to generate .afm files for the new fonts, then compare
them with the f
Your summary is more or less accurate. We've never had much success
coordinating with fillippov. I don't know if it's a language barrier,
lack of interest, or what.
Fontforge is the preferred editing tool for these fonts and the solution
is as you suggest. In addition, after the new fontset is w
On Mon, Jan 10, 2005 at 09:37:18PM -0800, Josh Coalson wrote:
> as far as I can piece together, the last releases went like:
>
> FLAC release libOggFLAC went to
> - --
> 1.1.0 1:2:0 from 1:1:0 (code changes only I think)
> 1.1.1-beta
12 matches
Mail list logo
