Adeodato Simó <[EMAIL PROTECTED]> writes:
>> I'll leave is to others to determine which of those are actually relevant
>> for source compliance. A lot of them obviously are not.
>> I'll also leave it to others to decide whether or not to preventively
>> block uploads to unstable for certain buil
Thanks for picking up on this Adeodato.
On Thursday 02 October 2008, Adeodato Simó wrote:
> > This is only true for udebs that are included in installer initrds,
> > but as that varies per type of image and architecture it does need to
> > be checked on a case-by-case basis.
> > Examples: parted w
* Frans Pop [Tue, 30 Sep 2008 11:38:50 +0200]:
> Maybe it could be an option to use the "transition upload block" mechanism
> to prevent further uploads of (selected) D-I build dependencies to sid
> and thus prevent version skew between testing and unstable.
I don't mind doing this for lenny, b
On Tuesday 30 September 2008, Frans Pop wrote:
> Maybe it could be an option to use the "transition upload block"
> mechanism to prevent further uploads of (selected) D-I build
> dependencies to sid and thus prevent version skew between testing and
> unstable.
I've committed a simple script "check
On Tuesday 30 September 2008, Frans Pop wrote:
> A second related issue is that after the final D-I upload no updates
> for packages that have udebs or are D-I build dependencies can be
> accepted into testing, unless the version included in D-I is first
> saved in a special suite. This last was do
Debian Installer builds are a bit special when compared with other
packages or even udebs. The way the builds are done means some special
attention is needed to ensure full source compliance for the release.
debian-installer images consist of:
1) files unpacked udebs from testing
2) libraries th
6 matches
Mail list logo
