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
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.
14. By Felix Zweig

correct change owner :)

Revision history for this message
Stefano Rivera (stefanor) wrote :

-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/StableReleaseUpdates

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.

review: Needs Fixing
Revision history for this message
Felix Zweig (f.zweig) wrote :

Thank you for your comment, I really appreciate it. However, I can't see how a port number would be a string. GNOME's proxy settings only allow for an Integer, and I'm not able to find a correct scenario why one would have setup a string.

And how can I target "development" from a "stable" installation? Thank you!

Revision history for this message
Stefano Rivera (stefanor) wrote :

Sorry for delayed reply.

I was assuming that in the past it stored as a string and now it's stored as an integer. Therefore old, existing settings may still be strings. However, this is an assumption, it'd need some research.

Redhat seem to have had the same assumption: https://bugzilla.redhat.com/attachment.cgi?id=440308&action=diff

As to targetting development Ubuntu from a stable release. I recommend you install it in a VM / spare machine / dual boot for live testing, but you can get pretty far building with PBuilder / Launchpad PPAs.

https://wiki.ubuntu.com/PbuilderHowto

Unmerged revisions

14. By Felix Zweig

correct change owner :)

13. By Felix Zweig

Retrieve secure proxy port as int (LP: #650928)

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'debian/changelog'
2--- debian/changelog 2010-09-21 19:43:51 +0000
3+++ debian/changelog 2010-11-04 17:58:41 +0000
4@@ -1,4 +1,10 @@
5-guake (0.4.2-2ubuntu1) maverick; urgency=low
6+guake (0.4.2-2ubuntu2) maverick; urgency=low
7+
8+ * Retrieve secure proxy port as int (LP: #650928)
9+
10+ -- Felix Zweig <f.zweig@yahoo.de> Thu, 4 Nov 2010 18:55:43 +0100
11+
12+guake (0.4.2-1) unstable; urgency=low
13
14 * New versions did not provided the TERM variable (LP: #621927)
15
16
17=== modified file 'src/guake.py'
18--- src/guake.py 2010-07-31 01:16:57 +0000
19+++ src/guake.py 2010-11-04 17:58:41 +0000
20@@ -1099,7 +1099,7 @@
21 ssl_port = port
22 else:
23 ssl_host = self.client.get_string('/system/proxy/secure_host')
24- ssl_port = self.client.get_string('/system/proxy/secure_port')
25+ ssl_port = self.client.get_int('/system/proxy/secure_port')
26
27 if self.client.get_bool(proxy + 'use_authentication'):
28 auth_user = self.client.get_string(

Subscribers

People subscribed via source and target branches

to all changes: