tag 402811 -pending
reassing 402811 linux-modules-nonfree-2.6, module-assistant, kqemu-source
thanks
> > Will this address the situation when package from
> > linux-modules-nonfree-2.6 has version in 'kernelver-modver' format,
> > while package from m-a has version in 'modver-kernelver' format?
>
tag 402811 -rending
reassing 402811 linux-modules-nonfree-2.6, module-assistant, kqemu-source
thanks
> > Will this address the situation when package from
> > linux-modules-nonfree-2.6 has version in 'kernelver-modver' format,
> > while package from m-a has version in 'modver-kernelver' format?
>
Nikita V. Youshchenko wrote:
> Will this address the situation when package from linux-modules-nonfree-2.6
> has version in 'kernelver-modver' format, while package from m-a has
> version in 'modver-kernelver' format?
No. This is a general glich in all the conglomeration packages.
--
Address:
> tags 402811 +pending
> thanks
>
> Nikita V. Youshchenko wrote:
> > I've just discovered that kqemu-modules-2.6.18-3-k7 package available
> > in debian unstable has version 2.6.18+1.3.0~pre9-2, while module
> > package for kqumu created from kqemu-source using module-assistant has
> > version 1.3
tags 402811 +pending
thanks
Nikita V. Youshchenko wrote:
> I've just discovered that kqemu-modules-2.6.18-3-k7 package available in
> debian unstable has version 2.6.18+1.3.0~pre9-2, while module package
> for kqumu created from kqemu-source using module-assistant has version
> 1.3.0~pre9-3+2.6.18
Package: linux-modules-nonfree-2.6
Version: 2.6.18-2
Severity: normal
I've just discovered that kqemu-modules-2.6.18-3-k7 package available in
debian unstable has version 2.6.18+1.3.0~pre9-2, while module package
for kqumu created from kqemu-source using module-assistant has version
1.3.0~pre9-3+2
6 matches
Mail list logo
