59648 – emerge --resume doesn't [always] work, starts from the beginning after lockup

Bug 59648 - emerge --resume doesn't [always] work, starts from the beginning after lockup

Summary: emerge --resume doesn't [always] work, starts from the beginning after lockup

Status:	RESOLVED CANTFIX

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-08-06 16:31 UTC by Vadim Trochinsky
Modified:	2004-09-24 20:04 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Vadim Trochinsky 2004-08-06 16:31:15 UTC

I wanted to rebuild my whole system with -fstack-protector -Os (for VIA Nehemiah CPU). So I started "emerge --emptytree world". Somewhere in the middle, the computer locked up for some unknown reason.

I tried "emerge --resume". It said that it was resuming, then started compiling from the first package.

Reproducible: Always
Steps to Reproduce:
1. emerge --emptytree world
2. computer locks up after compiling about 40 packages. Maybe pressing reset would do.
3. reboot
4. emerge --resume

Actual Results:  
emerge starts compiling from the beginning, instead of continuing after the 
crash 

Expected Results:  
emerge should continue at the point where it was stopped, or re-compile the 
package where it failed, and continue from there.

Comment 1 Nicholas Jones (RETIRED) gentoo-dev

2004-09-08 22:06:27 UTC

What portage version was this?

Comment 2 Nicholas Jones (RETIRED) gentoo-dev

2004-09-24 20:04:42 UTC

It's a crash... hence the system is unstable.