Bug 848631 - repoclosure failure on 18 Alpha TC2 DVDs (control-center)
Summary: repoclosure failure on 18 Alpha TC2 DVDs (control-center)
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 18
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F18Alpha, F18AlphaBlocker
TreeView+ depends on / blocked
Reported: 2012-08-16 05:11 UTC by Andre Robatino
Modified: 2012-08-21 11:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-08-21 11:39:21 UTC
Type: Bug

Attachments (Terms of Use)

Description Andre Robatino 2012-08-16 05:11:05 UTC
Description of problem:
i386 DVD:

package: 1:control-center-3.5.5-2.fc18.i686 from myrepo
  unresolved deps: 

x86_64 DVD:

package: 1:control-center-3.5.5-2.fc18.x86_64 from myrepo
  unresolved deps: 

Version-Release number of selected component (if applicable):
18 Alpha TC2

Comment 1 Adam Williamson 2012-08-16 19:36:11 UTC
Discussed at 2012-08-16 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-08-16/f18-alpha-blocker-review-3.2012-08-16-16.00.html . Accepted as a blocker per criterion "There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (DVD) install".

Comment 2 Fedora Update System 2012-08-16 22:00:41 UTC
control-center-3.5.6-1.fc18 has been submitted as an update for Fedora 18.

Comment 3 Andre Robatino 2012-08-17 02:49:41 UTC
Fixed in 18 Alpha TC3. Closing.

Comment 4 Adam Williamson 2012-08-17 18:50:29 UTC
The update is not stable yet. Please don't close bugs until the associated updates go stable.

Comment 5 Fedora Update System 2012-08-21 11:39:21 UTC
control-center-3.5.6-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

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