Bug 909 - Do not erase old chroot if the new one cannot be generated
Summary: Do not erase old chroot if the new one cannot be generated
Status: ASSIGNED
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: BuildSystem (show other bugs)
Version: unspecified
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 858
  Show dependency treegraph
 
Reported: 2011-04-20 22:20 CEST by Michael Scherer
Modified: 2012-01-28 15:26 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Michael Scherer 2011-04-20 22:20:30 CEST
Build system regenerate chroot for building package from time to time. Itshould be able to detect that a chroot was not correctly recreated and should sent a email to alert sysadmin about that. This would prevent breakage of build system, as it happened before on mandriva.
Michael Scherer 2011-04-20 22:20:57 CEST

Blocks: (none) => 858

Comment 1 Marja Van Waes 2011-10-09 23:14:50 CEST
Another dormant bug?

CC: (none) => marja11

Comment 2 Michael Scherer 2011-10-10 11:20:48 CEST
No news on it.
Comment 3 Marja Van Waes 2012-01-16 21:13:30 CET
Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED.

Please set status to ASSIGNED. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
Pascal Terjan 2012-01-26 11:27:39 CET

Status: NEW => ASSIGNED
CC: (none) => pterjan

Manuel Hiebel 2012-01-28 15:26:52 CET

Assignee: mageia-sysadm => sysadmin-bugs


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