On Sat, Sep 27, 2014 at 07:45:14PM -0400, Antoine Beaupré wrote:
> At this point, moreutils doesn't conflict with gnu parallel, and that is
> intentional. It is gnu parallel that conflicts with moreutils.
> 
> I talked briefly with Joey about this. Obviously, it's a rather annoying
> issue for him, since the whole thing went as far as a CTTE bug
> (#665851). The result of that discussion were unclear: no decision was
> reached by the CTTE.
> 
> From what I understand, joey doesn't want to be bothered with this. He
> barely has time to maintain moreutils at all and has critical opinion of
> gnu parallel, which breaks his ikiwiki-hosting package. Therefore,
> ikiwiki-hosting conflicts with gnu parallel.

understood, thanks for the context!

> So I doubt we can coninve Joey to fix this problem the way we are
> proposing now, but it's possible.
> 
> If someone wants to go forward here, there would need to be a set of
> patches that would create conflicting binary packages for both that will
> divert /usr/bin/parallel. A patch on ikiwiki-hosting to depend on
> moreutils-parallel would also then be necessary.

Is dpkg-divert a strict requirement? Would alternatives suffices (e.g. like
netcat does)?

> Then we send this to the moreutils and gnu parallel maintainers to see
> if they would accept the fix, and we can simply NMU it.
> 
> But the main problem, to restate what Joey has said here, is time: it
> takes time to do that work and unless someone steps up to help the
> maintainers patiently to clear things up, things will stay as they
> currently are.

true, I am willing to give it a shot but we're probably far too late in the
release cycle to get this into jessie (won't be wasted work anyway tho!)

filippo
-- 
http://esaurito.net - 0x99D49B6B00CAD1E5 - ⠠⠵

God may not play dice with the universe, but something strange is going on
with the prime numbers.
-- Paul Erdos


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to