[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dash Debian package - RC bugs



On 15 April 2010 12:58, Gerrit Pape <pape@smarden.org> wrote:
> Raphael sent a mail rudimentarily stating how to proceed.  I must
> confess, I don't really understand the plan, or why it should be done
> this way.  But I might miss information since I was not available when
> the /bin/sh transition was discussed, planned, and initiated.

It would be great if we could discuss that, but for that I need to
know what isn't clear, etc.

> Not standing behind the plan, I'm not about to implement it.  And it
> looks like nobody else is doing it either.

I started to prepare the test packages but haven't had time to setup
the multiple test environments.
Also, I'm aware you've prepared a new version that is blocked by the
package-uses-local-diversions auto-reject. Lintian's detection can be
workarounded by rewriting the preinst script in c (I think that one of
the bug reports has a user submission doing that), which is required
to make dash the only package providing the /bin/sh symlink.

I tried to clone your git repository but it 404s, so I can't check
what other changes you've made so far and see if there's any conflict.
Is your repository available anywhere else?

Like others have mentioned, it might be more convenient if dash's
maintenance was moved to alioth, but I'm not going to push on that.
That's your call.

>  If there's no progress
> within the next weeks, I most probably will rollback the changes, and
> possibly simply change the debconf question's default from no to yes.

Please don't. I know I have not been very active on that front, but
I'm now going to dedicate more time to it.

>  I
> have ideas about different ways to implement the real /bin/sh transition
> from bash to dash, but don't want to invest time as long as the
> situation is not clear.

Could you please explain them? I would like to know what you think.

Regards,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


Reply to: