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

Bug#680675: marked as done (debian-installer: Prompts when InRelease file cannot be downloaded)

Your message dated Mon, 22 Jul 2013 01:12:11 +0200
with message-id <201307220112.30643.holger@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #680675,
regarding debian-installer: Prompts when InRelease file cannot be downloaded
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.)


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

When installing using debian-installer 20120508 wheezy mini.iso netboot image,
and using a mirror that doesn't support InRelease files (squeeze's version of 
approx), during the "Installing the base system" step it prompts with a message 
that the InRelease file cannot be downloaded.

Selecting continue seems to work fine, presumably falling back to debootstrap's 
handling of old-style Release and Release.gpg files.

It seems like debian-installer shouldn't bother to warn the user at that point 
if the fallback methods haven't yet been tried...


live well,
  vagrant

--- End Message ---
--- Begin Message --- 
reassign 690832 choose-mirror
reassign 687488 netcfg
retitle 709319 wheezy 7.1: scanning for more DVDs is confusing
tags 709319 + confirmed
tags 626219 + confirmed
reassign 616722 partman-md
reassign 616125 partman-crypto
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: