BIND 9 ARM, html/pdf not in the source?

Ondřej Surý ondrej at
Mon May 17 11:41:40 UTC 2021


I am sorry, but what?  I would suggest to actually try the interface
before you write angry emails. There’s nothing of sorts as you
describe. The only hassle is that before forking, you need to ask
ISC to actually allow your user account to create forks.

There’s no requirement to use anything like “Git/Web”, I don’t even
know what you exactly mean by that.

Also for this

> After finding it necessary to download tens of megabytes of source

$ git clone --depth=1
Cloning into 'bind9'...
remote: Enumerating objects: 4755, done.
remote: Counting objects: 100% (4755/4755), done.
remote: Compressing objects: 100% (3558/3558), done.
remote: Total 4755 (delta 2009), reused 2211 (delta 865), pack-reused 0
Receiving objects: 100% (4755/4755), 6.81 MiB | 4.29 MiB/s, done.
Resolving deltas: 100% (2009/2009), done.

It’s less then 7MB when you use proper `git clone` options (and probably even less
on the wire as the compression is used transparently).

> I flatly refuse to even try to use a Git/Web interface any more.

So, here’s my blunt question - do you have any experience using ISC GitLab?

> Would it be too onerous for the ISC to make this available?

Well, unless the goal is to keep us busy with handling all the incoming spam…

Again, I don’t think that the creating user account is such high-entry barrier
that it would require shifting the costs from the reported to the already too-busy
open-source developers.

Ondřej Surý (He/Him)
ondrej at

> On 17. 5. 2021, at 12:23, G.W. Haywood via bind-users <bind-users at> wrote:
> Hi there,
> On Sun, 16 May 2021, Ond?ej Sur? wrote:
>> On Sun, 16 May 2021, Chuck Aurora wrote:
>> > On Sun, 16 May 2021, Ond?ej Sur? wrote:
>> > > > ... yes, you need ISC GitLab account to create new issues (unless
>> > > it's a security vulnerability then OpenPGP encrypted email is
>> > > accepted). We need to interact with the reporters from the issue and
>> > > we think this is a reasonable requirement.
>> > > FWIW I do not agree.
>> ... I don't think it's too much to ask a little bit of inconvenience
>> from the users, so we can actually focus on fixing bugs and
>> improving the software.
> I feel strongly that I should chime in with my experiences of trying
> to use Git/Web interfaces to report issues.  Not, I hasten to add,
> issues with BIND - I don't recall ever trying to use ISC's GitLab and
> I'd have no particular issues with creating an account except that I'd
> try to make sure that it could never be linked to me by criminals when
> it's almost inevitably compromised.
> I don't want this to sound like an attempt to pour fuel onto the flames
> but insisting on Git/HTTP is not just "a little bit of inconvenience".
> After finding it necessary to download tens of megabytes of source to
> make a ten character change to the code, and finding that the little
> 'Commit' button that you have to press to the pull request would not
> come out of its greyed-out state no matter what I do, and on enquiry
> after some hours of digging being told that I need to use a different
> browser (I use Palemoon; one suggestion was Firefox), I've now reached
> the point that if it says 'http' and 'git' I will look for the little
> 'X' in the tab near the top of my browser window.  Call me a dinosaur
> if you like but after wasting much time on it, I flatly refuse to even
> try to use a Git/Web interface any more.  If I expected to use it all
> day every day things might be different, but for chipping in a minor
> report or small improvement the bars to entry seem to be set too high.
> If I found a mistake in the ARM I'd cheerfully send an email, but I'd
> never even consider navigating through a GitLab maze to do the same
> thing and I'd just keep quiet about it.
> There is an email interface for GitLab.  It requires no account to be
> created by the user.  You get to keep the single repository of wisdom.
> Would it be too onerous for the ISC to make this available?
> -- 
> 73,
> Ged.
> _______________________________________________
> Please visit to unsubscribe from this list
> ISC funds the development of this software with paid support subscriptions. Contact us at for more information.
> bind-users mailing list
> bind-users at

More information about the bind-users mailing list