Hi Jeremy,
On Thu, Nov 22, 2018 at 6:11 AM Jeremy Bicha wrote:
> Could you go ahead and do this upload now?
Sorry but I've been waiting for 2 months for the debian-keyring to be
uploaded to be able to upload my packages.
As long as it's not been released with my key I believe I can't upload
my p
Could you go ahead and do this upload now?
Since asciidctor didn't build on ia64, this upload is blocking
packages like ndctl from being available on that architecture.
I see there is a new asciidoctor 1.5.8 release now if you want to do
multiple things in this upload. :)
Thanks,
Jeremy Bicha
> I reported that bug.
Indeed, that's why I was confused! :D
> After reading my report three times, I see how you
> might have interpreted it that way. I wrote that there is a problem,
> "because asciidoctor is Architecture: all and implicitly Multi-Arch:
> no". The problem results from the combi
On Tue, Sep 18, 2018 at 09:47:34AM -0700, Joseph Herlant wrote:
> I think you can find the explanations to those questions in #893467
> which is the origin of th split of the asciidoc package.
I reported that bug. After reading my report three times, I see how you
might have interpreted it that wa
Hi Helmut,
Thanks for your report.
I think you can find the explanations to those questions in #893467
which is the origin of th split of the asciidoc package.
Let me know if there are still more questions about it after reading #893467.
Regarding the dependency version, that's a good point that
Package: asciidoctor
Version: 1.5.7.1-1
Severity: minor
The asciidoctor binary package is the only binary package in
src:asciidoctor that happens to be Architecture: any. Given that its
contents are bit-identical accross all release architectures, I wonder
why. Please consider switching the Archit
6 matches
Mail list logo
