On Thu, Sep 29, 2005 at 12:52:46AM +0200, Adrian Bunk wrote:
> > Was there anything wrong with the current package?
> 
> Are you talking about the package currently in unstable?

No, the package on mentors.

> The last upload nearly 2 months ago was an NMU to fix an RC bug.
> 
> There are several issues in the current package, e.g.:
> - #327153: problem with randomisation present in recent 2.6 kernels
>            (Bart Oldeman said half a year ago that the problem is that 
>             the Debian package uses the deprecated comcom)
>            the workaround for this issue is easy, but a proper fix
>            in the dosemu package would be appreciated
> - #328652: new upstream version available
>            I don't see any good reason why Debian unstable still
>            ships 1.2.1
> 
> Even if you don't can immediately fix any of the open bugs it would be 
> nice if you would get a package uploaded for showing that you have taken 
> over maintainership.a

I'm sorry, I thought that you were the fellow I had previously
corresponded with about this.  Since I am not a Debian developer (and
had given up trying to get my key signed), Andreas Tille had offered to
upload my package once it was satisfactory.  We were waiting for
upstream to reply about some issues regarding filesystem locations of
things, but since they haven't replied in a long time and a new package
is badly needed, I thought it was a good idea to go ahead and upload a
new package even if it isn't perfect.  Nobody replied to the thread in
quite a while, so I assumed the discussion was dead.  I guess I'll
revive it, but at the moment I am quite busy with other things.

In the meantime, if you are interested in this package, can you look
over the package currently on mentors and tell me if you see any
problems with it that would prevent an upload or cause upgrades from
older versions to break?  I have received no feedback about it, so I
have no idea if it even works for anyone besides myself.

-- 
Ryan Underwood, <[EMAIL PROTECTED]>


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

Reply via email to