Merge lp:~f.zweig/ubuntu/maverick/guake/guake-fix-650928 into lp:ubuntu/maverick/guake
Proposed by
Felix Zweig
Status: | Work in progress |
---|---|
Proposed branch: | lp:~f.zweig/ubuntu/maverick/guake/guake-fix-650928 |
Merge into: | lp:ubuntu/maverick/guake |
Diff against target: |
28 lines (+8/-2) 2 files modified
debian/changelog (+7/-1) src/guake.py (+1/-1) |
To merge this branch: | bzr merge lp:~f.zweig/ubuntu/maverick/guake/guake-fix-650928 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Stefano Rivera | Needs Fixing | ||
Review via email: mp+40129@code.launchpad.net |
Commit message
Retrieve secure proxy port as int (LP: #650928)
Description of the change
A naive try to fix bug #650928. :)
To post a comment you must log in.
Unmerged revisions
- 14. By Felix Zweig
-
correct change owner :)
- 13. By Felix Zweig
-
Retrieve secure proxy port as int (LP: #650928)
-guake (0.4.2-2ubuntu1) maverick; urgency=low
+guake (0.4.2-1) unstable; urgency=low
Err, why?
At what point did this change from a string to an int? Well, my real question is: Will some users still have strings, do you have to touch your proxy settings to get it to become an int? If so, the Redhat patch is preferable.
Also, note that as this is an SRU, it should have an SRU version number, i.e. 0.4.2-2ubuntu1.1 and be aimed at maverick-proposed, not maverick. https:/ /wiki.ubuntu. com/StableRelea seUpdates
We usually prefer to fix bugs like this in the development release before the stable one (so we don't provide an update that causes regressions), but in this case it can probably just be done as an SRU.