Add a release-upgrader task handler
Bug #462543 reported by
Free Ekanayaka
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
Medium
|
Free Ekanayaka | ||
landscape-client (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Intrepid |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned | ||
Karmic |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Add a new landscape-
perform release upgrades.
The release-upgrader should fetch, verify and run the upgrade tool for
the target release specified by the task being handled.
affects landscape-client
status inprogress
importance medium
assignee free.ekanayaka
milestone 1.4.1
Related branches
tags: | added: review |
Changed in landscape-client: | |
status: | In Progress → Fix Committed |
tags: | added: needs-testing |
tags: | added: 1.5-upgrade-client |
Changed in landscape-client (Ubuntu Lucid): | |
status: | New → Fix Committed |
Changed in landscape-client (Ubuntu Lucid): | |
status: | Fix Committed → Fix Released |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |
tags: | removed: verification-needed |
To post a comment you must log in.
[1] release) ,"hardy" ))
+ifneq (,$(findstring $(dist_
+ # We want update-motd in intrepid and jaunty
This comment, and the following, look wrong.
[2] Configuration( PackageTaskHand lerConfiguratio n): reporter. """
+class ReleaseUpgrader
+ """Specialized configuration for the Landscape package-
It seems to be the release upgrade configuration.
[3] grp.getgrnam( "landscape" ).gr_gid) pwd.getpwnam( "landscape" ).pw_uid) command( ) smart-update" ] "--config= %s" % self._config. config)
+ if os.getuid() == 0:
+ os.setgid(
+ os.setuid(
+
+ reporter = find_reporter_
+
+ # Force a smart-update run, because the sources.list has changed
+ args = ["--force-
+
+ if self._config.config is not None:
+ args.append(
+
As discussed, this code should be shared with the changer, possibly switching to use the uid/gid arguments to reactor. spawnProcess.
I didn't test the branch functionally, but it looked good. +1!