On 2008-04-21 Atsuhito Kohda <[EMAIL PROTECTED]> wrote:
> On Sat, 19 Apr 2008 17:14:28 +0200, Andreas Metzler wrote:

> > the situation seems to be rather simple:

> Might be so but it looks to me that simple situation
> is not understood correctly.  I almost lost motivation
> to argue this issue any more.  But anyway;

> > On top of that upstream tells us that the
> > version shipped in the package "lynx" is outdated and that only
> > lynx-cur should be shipped:

> from the above,

> > So we should not have a package lynx-cur in sid, and the package lynx
> > should be at version 2.8.7dev.8.

> it is natural or reasonable for me to concluse, we should 
> not have a package lynx in sid.

Hello,

well if we have a single version of lynx in the archive, calling the
package lynx-cur instead of simply lynx seems wrong. (If there is good
reason I just do not know it, but I might be wrong.) I did not intend
to say who should package it.

> > You'll need to arrange between you
> > two how to get this done.

> lynx and lynx-cur are maintained for quite a long time
> independently and I don't think I need any co-maintenace
> with lynx-cur at present.  Further, 
[...]
> But if I'm allowed to advice, it will be better to use
> the package name lynx-cur because it is the name of the 
> upstream source.

The binary is still called lynx, isn't it? Shouldn't "apt-get install
lynx" simply work? How about naming the source package lynx-cur and
the binary lynx?

> Zephaniah, I'd like to hear your opinion if possible.

The hijack of lynx was strange, two uploads, then quietness. 
http://packages.qa.debian.org/l/lynx/news/20070501T061703Z.html

> If my mail sounds unpleasant, it is not my intention
> but it is because my English ability prevents me from
> expressing my feeling correctly enough in Englisy ;-)

AOL!

cu andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to