Ticket #739 (closed task: fixed)

Opened 2 years ago

Last modified 2 years ago

GCC-4.7 rebuild

Reported by: ausil Owned by:
Priority: major Keywords: meeting
Cc: harald@…, petersen@…, paul@… Blocked By:
Blocking:

Description

phenomenon

GCC 4.7 just landed http://koji.fedoraproject.org/koji/buildinfo?buildID=280790 http://lists.fedoraproject.org/pipermail/devel/2011-December/160723.html http://fedoraproject.org/wiki/Features/GCC47

background analysis

Mass rebuild needs to start this week if we let people do their own builds. we are 5 weeks away from branching for F17 Mass rebuild needs to be completed before that happens.

implementation recommendation

We announce immediately that a mass rebuild is happening, anything not built this week will be rebuilt by releng starting next thursday Jan 12. that should give us just over 2 weeks to clean up failures.

Change History

comment:1 follow-up: ↓ 2 Changed 2 years ago by jsmith

I seem to recall some discussion before the holiday break regarding the UsrMove? feature and whether it would require any kind of mass rebuild, but I don't remember if any sort of consensus was reached. Are there any other features that require a mass rebuild this cycle, and if so are they ready for mass rebuild?

comment:2 in reply to: ↑ 1 Changed 2 years ago by mmaslano

  • Cc harald@… added

Replying to jsmith:

I seem to recall some discussion before the holiday break regarding the UsrMove? feature and whether it would require any kind of mass rebuild, but I don't remember if any sort of consensus was reached. Are there any other features that require a mass rebuild this cycle, and if so are they ready for mass rebuild?

Adding Harald into CC.

comment:3 Changed 2 years ago by mmaslano

  • Cc petersen@… added

Jens, do you want rebuild of your ghc packages also in mass rebuild?

comment:4 Changed 2 years ago by harald

The UsrMove? does not require a complete mass rebuild. We will rebuild individual packages manually and check in changes for other packages (which do not have to rebuild immediately). Also the time frame is to tight for us. But thanks for consideration.

comment:5 Changed 2 years ago by notting

  • Keywords meeting added

In order to attempt to expedite this, I'm +1 to doing the mass rebuild asap.

comment:6 Changed 2 years ago by kevin

sure, +1 here as well. Other fesco folks?

comment:7 Changed 2 years ago by limb

+1 from me.

comment:8 Changed 2 years ago by tmraz

+1 from me for the rebuild as well.

comment:9 Changed 2 years ago by mmaslano

+1, which makes +5 -> you can start.

comment:10 Changed 2 years ago by sgallagh

+1 (belatedly)

comment:11 Changed 2 years ago by pghmcfc

The perl dependency generator seems to be missing some dependencies in Rawhide at the moment, so any mass rebuild done now might introduce a host of dependency-related bugs that require a rebuild of much of the (large) perl ecosystem.

http://lists.fedoraproject.org/pipermail/devel/2012-January/160958.html

Unfortunately I've haven't yet identified what has changed to cause this.

comment:12 Changed 2 years ago by pghmcfc

The update of "file" from 5.09 to 5.10 triggered this breakage.

https://bugzilla.redhat.com/show_bug.cgi?id=772632

I think this needs to be fixed (it's a simple fix) before the mass rebuild happens.

comment:13 Changed 2 years ago by pghmcfc

  • Cc paul@… added

comment:14 Changed 2 years ago by pghmcfc

comment:15 Changed 2 years ago by pghmcfc

comment:16 Changed 2 years ago by limb

  • Resolution set to fixed
  • Status changed from new to closed

APPROVED, vote was +8, -0, 0:0

Note: See TracTickets for help on using tickets.