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

Bug#698933: marked as done (hangs on 'Configuring APT')

Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id <201308311252.51555.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #698933,
regarding hangs on 'Configuring APT'
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.)


-- 
698933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698933
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: Debian-6.0.6-amd64-netinst.iso

Hi.
I recently attempted to install Debian (for the first time) lastest stable small CD. Debian-6.0.6-amd64-netinst.iso. 

Machine is as below, W7 installed, Debian resize partition used.
However, the install hangs on 'Configuring APT' about 50%, when trying to download 'file 5 of 5'. 
Tried other mirrors, same problem.

I found this bug Bug#389285 from 2006 which was closed.
However, this appears to be the same bug 7 years on?
Please advise. Would a large complete DVD install avoid the configuring APT step? 

Regards
Mike

Processor Intel Core i3-3220 3.3Ghz
Memory 8GB DDR3 RAM
Hard Drive 1TB SATA HDD
Motherboard ASUS P8H61-MX
Wired internet connection

--- End Message ---
--- Begin Message --- 
reassign 699136 partman
retitle 699136 partman hangs with specific mbr/usbsticks
tags 696755 +confirmed
Hi,

thank you for submitting installation reports, 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 were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given 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 - thats 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: