[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#782976: marked as done (debian-installer-netboot-images packages kfreebsd images but kfreebsd is not in jessie.)



Your message dated Sat, 25 Apr 2015 00:47:40 +0100
with message-id <553AD61C.8000106@p10link.net>
and subject line Re: Bug#782976: debian-installer-netboot-images packages kfreebsd images but kfreebsd is not in jessie.
has caused the Debian Bug report #782976,
regarding debian-installer-netboot-images packages kfreebsd images but kfreebsd is not in jessie.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
782976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782976
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer-netboot-images
Severity: serious

The RC policy states "Packages must be buildable within the same release.". In this context I interpret "buildable" as buildable from actual sourcecode (not just package together) and "the same release" as the collection of stuff that Debian will be officially releasing as jessie.

kfreebsd was removed from the jessie release. AIUI this means it will not be possible to build the kfreebsd debian installer on any official jessie system. As such IMO kfreebsd images should not be included in this package.
--- End Message ---
--- Begin Message ---
Version: 20150422

On 24/04/15 23:59, Steven Chamberlain wrote:
Hi peter,

I think it's been removed today already:
https://packages.qa.debian.org/d/debian-installer-netboot-images/news/20150423T215008Z.html

Do you agree?  And this bug can be closed.
Looks like it, closing.

--- End Message ---

Reply to: