Bug#919953: /usrr/bin/dune and `dune' binary package should refer to dune-common

2019-02-28 Thread Paul Gevers
Control: found 919953 1.0~beta20-1
Control: severity 919953 important

On Sun, 20 Jan 2019 22:19:01 + Ian Jackson
 wrote:
> According to Debian policy file conflicts should be resolved by no-one
> using the conflicting name.  This applies to /usr/bin/dune.
> 
> Additionally, the only referent of `dune' that anyone has heard of
> (eg, wikipedia) is a C++ library which we have in Debian as
> `src:dune-commmon', `libdune*-dev', etc.
> 
> It is evident from actions taken in response to #916468 that the you
> (the maintainers of what is current `src:dune') do not agree.
> 
> Instead, it seems to me that you ahead and took the name despite a
> fairly clear consensus in debian-devel that you shouldn't.  I don't
> think you should have done that.
> 
> I am escalating this to the Technical Commitee in another bug.  In the
> meantime this bug needs to be open to keep this out of testing.

That TC bug got closed without the need for a resolution from the TC.
Hence, I don't consider this bug to qualify as RC anymore. (I personally
wouldn't mind if the *package* dune got renamed, but we shouldn't do
that before the buster release.)

Paul



signature.asc
Description: OpenPGP digital signature


Bug#919953: /usrr/bin/dune and `dune' binary package should refer to dune-common

2019-01-20 Thread Ian Jackson
Package: dune
Version: 1.6.2-2
Severity: serious
Control: block -1 by 919951

According to Debian policy file conflicts should be resolved by no-one
using the conflicting name.  This applies to /usr/bin/dune.

Additionally, the only referent of `dune' that anyone has heard of
(eg, wikipedia) is a C++ library which we have in Debian as
`src:dune-commmon', `libdune*-dev', etc.

It is evident from actions taken in response to #916468 that the you
(the maintainers of what is current `src:dune') do not agree.

Instead, it seems to me that you ahead and took the name despite a
fairly clear consensus in debian-devel that you shouldn't.  I don't
think you should have done that.

I am escalating this to the Technical Commitee in another bug.  In the
meantime this bug needs to be open to keep this out of testing.

Sorry,
Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.