Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 251606 - cobbler is outdated in rawhide since ages now
cobbler is outdated in rawhide since ages now
Product: Fedora
Classification: Fedora
Component: cobbler (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Michael DeHaan
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-08-09 18:49 EDT by Rudolf Kastl
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-10 10:47:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rudolf Kastl 2007-08-09 18:49:09 EDT
Description of problem:
rawhide still has cobbler 0.4.8 while we are currently at cobbler 0.6.0

it is actually no fun to deal with old already fixed bugs when there are
important releases skipped that really should be field tested.

please update cobbler in rawhide to 0.6.0
Comment 1 Michael DeHaan 2007-08-10 08:48:56 EDT
0.6.0 stable released /yesterday/, not ages ago.  You are correct in that I
missed the devel branch.  

Since Cobbler is a method of deploying production software (and also supports
quite a few other distros), only the stable releases hit the mirrors.  Running
rawhide on an infrastructure server is not wise.    If you want to live on the
bleeding edge, you can still build off head in git, which is ridiculously easy
on rawhide.

When dealing with a boot server, I want /users/ to be in control of when they
upgrade to non-stable releases, we don't want to suprise them, especially when
updates to cobbler may require an update to koan they don't know about, etc.

Comment 2 Michael DeHaan 2007-08-10 10:47:16 EDT
0.6.0 for both cobbler and koan now built for devel

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