On Mon, 2006-06-12 at 01:52 -0400, Dan Merillat wrote:
> David Nusinow wrote:
>
> > I am currently in the process of fixing it, but it requires a lot of
> > rebuilds and is not so critical as hosing people's systems on upgrade. Calm
> > down. It'll be fixed with 7.1, which is what I'm working on r
David Nusinow wrote:
I am currently in the process of fixing it, but it requires a lot of
rebuilds and is not so critical as hosing people's systems on upgrade. Calm
down. It'll be fixed with 7.1, which is what I'm working on right now.
Hey, I provided a fix for it rather then just complaining
On Sun, Jun 11, 2006 at 09:56:12PM -0400, Dan Merillat wrote:
>
> Use this rather then doing it manually while we wait for
>
> * upstream to fix it.
> * upstream to release the fix
> * Debian to package the fixed upstream release.
>
> I have no idea why this doesn't qualify as a Debian-fixable b
Use this rather then doing it manually while we wait for
* upstream to fix it.
* upstream to release the fix
* Debian to package the fixed upstream release.
I have no idea why this doesn't qualify as a Debian-fixable bug
rather then an upstream. If it is a Debian packaging issue,
in that upstr
4 matches
Mail list logo