On Fri, Nov 21, 2003 at 09:26:45AM +0100, Yann Dirson wrote:
>...
> > Binary NMU for unstable:
> > Version: 1.0-2.0.1
> >
> > Your suggested pre-tesing package:
> > Version: 1.0-2.0.1
> >
> >
> > IOW:
> > There are two different packages with the same version number.
>
> But:
>
> - if they come into incoming the same day, the 1st one wins
There are two packages with the same version number.
This might e.g. cause much confusion when someone reports a bug against
version 1.0-2.0.1, and the problem is only in one of these two packages.
> - binary NMUs should AFAIU only occur when there's some
> important-enough problem for 1.0-2 on a given arch, right ? Then
> there is an arch-specific problem, and we can mandate that binary-only
> NMUs are only to be done to fix an arch-specific RC bugreport, which
> would then have prevented the attempt to promote into pre-testing.
>...
Binary NMUs usually occur when there are e.g. toolchain problems on one
architecture.
E.g. if an autobuilder built and uploaded 100 packages using a broken
gcc package.
There's often no arch-specific RC bugreport for problems that are fixed
by binary NMUs.
> Regards,
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
