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

Bug#704499: marked as done (Please include preseed examples, and a list of configurations variables)

Your message dated Sun, 21 Jul 2013 14:32:43 +0200
with message-id <201307211433.01341.holger@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #704499,
regarding Please include preseed examples, and a list of configurations variables
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.)


-- 
704499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704499
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source:   debian-installer
Version:  20130211
Severity: wishlist

  Am I right that there are no preseed examples in the package?
If so, please consider adding one, or more.  Perhaps in the doc 
directory.
  While at it, perhaps a comprehensive list of all the d-i 
configuration variables can be added?

--- End Message ---
--- Begin Message --- 
reassign 716710 preseed,release-notes
forcemerge 704881 552563
tags 633128 + confirmed
reassign 633128 src:linux,kernel-wedge
affects 633128 debian-installer
reassign 653391 archdetect
forcemerge 653390 653391 
reassign 655579 rootskel-gtk
reassign 690246 partman-lvm
affects 690246 debian-installer
severity 699430 wishlist
reassign 655124 kernel-wedge
affects 655124 debian-installer
thanks

Hi,

thank you for submitting bug reports concering debian-installer, much 
appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old and/or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - and that's often better, as the bug 
log will be clearer and shorter and not contain cruft.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: