##// END OF EJS Templates
.
Marcin Kasperski -
r247:c379e751 default
parent child Browse files
Show More
@@ -1,313 +1,311 b''
1 1 1.1.8
2 2 ~~~~~~~~~~~~~
3 3
4 4 Updated links after bitbucket changes.
5 5
6 hg 4.1 and 4.2 added to tested versions.
7
8 6 1.1.7
9 7 ~~~~~~~~~~~~~~~~~~
10 8
11 9 #52 hg keyring_check and hg keyring_clear did not work since
12 10 Mercurial 3.9 (incompatibility caused by commit 2c019aac6b99,
13 11 introducing passwdb).
14 12
15 13 1.1.6
16 14 ~~~~~~~~~~~~~~~~~~
17 15
18 16 Fixed NameError showing up in some password saving scenarios, in
19 17 particular in case of password save failures (thanks to Andrew
20 18 Taumoefolau for reporting and fixing).
21 19
22 20 1.1.5
23 21 ~~~~~~~~~~~~~~~~~~
24 22
25 23 Mercurial 3.9 compatibility.
26 24
27 25 1.1.4
28 26 ~~~~~~~~~~~~~~~~~~
29 27
30 28 Gracefully handle failures to save passwords - they are reported
31 29 as warnings, but don't break the operation being executed.
32 30
33 31 Compatibility fixes for upcoming 3.9 release (which changes SSL API
34 32 noticeably, what impact SMTP passwords handling in mercurial_keyring).
35 33
36 34 1.1.3
37 35 ~~~~~~~~~~~~~~~~~~
38 36
39 37 Mercurial 3.8 compatibility for email over SSL/TLS (SMTPS/STARTTLS
40 38 constructors changed). Should not spoil older versions.
41 39
42 40 1.1.2
43 41 ~~~~~~~~~~~~~~~~~~
44 42
45 43 The keyring_check and keyring_clear commands can be run outside
46 44 repository (if given some path as parameter).
47 45
48 46 Fixed some messages.
49 47
50 48 README updates (a few language fixes, added note about GUI tools).
51 49
52 50 1.1.1
53 51 ~~~~~~~~~~~~~~~~~~
54 52
55 53 #49 Fixed the bug due to url-stored usernames did not work (introduced
56 54 in 1.0.0 and not completely fixed in 1.0.1).
57 55
58 56 #50 Bad doc url in error message
59 57
60 58
61 59 1.1.0
62 60 ~~~~~~~~~~~~~~~~~~
63 61
64 62 Forward compatibility for Mercurial 3.8 (should not break old mercurials)
65 63
66 64 1.0.1
67 65 ~~~~~~~~~~~~~~~~~~
68 66
69 67 URLs containing usernames (https://John@some.service/somewhat) were
70 68 not working unless username was also configured separately (username
71 69 presence in url was not detected properly).
72 70
73 71 Liberated prefix matching, path https://John@some.service/somewhat can
74 72 be matched both against prefix https://some.service and against
75 73 https://John@some.service. That mostly matches what mercurial itself
76 74 does.
77 75
78 76 1.0.0
79 77 ~~~~~~~~~~~~~~~~~~
80 78
81 79 Added
82 80 hg keyring_check
83 81 and
84 82 hg keyring_clear PATH-OR-ALIAS
85 83 commands
86 84
87 85 Removed obsolete workarounds (compatibility for very old Mercurials -
88 86 some for pre-1.0, some for 1.4, some for 1.8/1.9).
89 87 Mercurial 2.0 is now required.
90 88
91 89 Improved information about path prefix. In particular it is shown
92 90 whenever user is asked for password, for example:
93 91 hg pull bitbucket
94 92 http authorization required
95 93 realm: BitBucket
96 94 url: https://bitbucket.org/Mekk
97 95 user: Mekk (fixed in hgrc or url)
98 96 password:
99 97
100 98 Improved README.
101 99
102 100 Improved debug information.
103 101
104 102 0.8.0
105 103 ~~~~~~~~~~~~~~~~~~
106 104
107 105 Module is simplified a bit, but requires mercurial_extension_utils.
108 106 Debug messages are prefixed with keyring: not [HgKeyring]
109 107
110 108 0.7.1
111 109 ~~~~~~~~~~~~~~~~~~
112 110
113 111 #48 NullHandler import failure no longer breaks the extension.
114 112 May help python 2.6 compatibility.
115 113
116 114 0.7.0
117 115 ~~~~~~~~~~~~~~~~~~~
118 116
119 117 Delaying keyring module import until passwords are really needed. It
120 118 can noticeably improve Mercurial (non pull/push) performance in some
121 119 cases (no longer slow hg status because D-Bus is busy an keyring tries
122 120 to activate KDE Wallet through it…).
123 121
124 122 0.6.7
125 123 ~~~~~~~~~~~~~~~~~
126 124
127 125 #46 Fixed syntax of smtp.tls configuration setting (current Mercurials
128 126 doesn't handle "true" anymore, TortoiseHG crashed with mercurial
129 127 keyring enabled while currently recommended starttls/smtps/none values
130 128 were in use).
131 129
132 130 0.6.6
133 131 ~~~~~~~~~~~~~~~~~
134 132
135 133 #44 Handling some more mercurial versions in demandimport-detection
136 134 logic.
137 135
138 136 0.6.5
139 137 ~~~~~~~~~~~~~~~~~
140 138
141 139 #36 Shutting up warning about no logging handlers.
142 140
143 141 0.6.4
144 142 ~~~~~~~~~~~~~~~~~
145 143
146 144 #44 Pre-2.9.1 Mercurials compatibility (probing for active
147 145 demandimport differently).
148 146
149 147 0.6.3
150 148 ~~~~~~~~~~~~~~~~~
151 149
152 150 #41 Fix for incorrect demandimport activity check logic, which could
153 151 cause various problems with imports after mercurial_keyring is
154 152 imported.
155 153
156 154 0.6.2
157 155 ~~~~~~~~~~~~~~~~~
158 156
159 157 #33 Fix for UnicodeDecodeErrors happening on some backends (especially
160 158 Vault) when passwords with non-ascii characters are in use and native
161 159 locale is not utf-8. Passwords are no longer saved to keyring backends
162 160 as-entered, they are now decoded from local encoding (whichever is
163 161 detected by Mercurial), then encoded to unicode.
164 162
165 163 0.6.1
166 164 ~~~~~~~~~~~~~~~~~
167 165
168 166 #30 Yet another demandimport conflict fixed.
169 167
170 168 0.6.0
171 169 ~~~~~~~~~~~~~~~~~
172 170
173 171 #28 Disable demandimport completely during keyring import. Mayhaps it
174 172 will resolve (most) demandimport conflict errors.
175 173
176 174 0.5.7
177 175 ~~~~~~~~~~~~~~~~~
178 176
179 177 #27 Some more demandimport ignores.
180 178
181 179 0.5.6
182 180 ~~~~~~~~~~~~~~~~~
183 181
184 182 #24, #25 Demandimport fixes (import failures in specific cases).
185 183
186 184 Better way of demandimport-ignoring modules. In particular, we append
187 185 more of them if gobject happens to be on the list.
188 186
189 187 0.5.5
190 188 ~~~~~~~~~~~~~~~~~
191 189
192 190 Fix for gnome keyring import problems.
193 191
194 192 0.5.4
195 193 ~~~~~~~~~~~~~~~~~
196 194
197 195 #22 Some more demandimport ignores (fix import failures).
198 196
199 197 SMTP password was not cleared properly (after detecting that it is
200 198 invalid).
201 199
202 200 Clarified license to be modified BSD style license.
203 201
204 202 0.5.3
205 203 ~~~~~~~~~~~~~~~~~
206 204
207 205 Remove useless import which caused problems on Mercurial 2.3 when
208 206 demandimport was not enabled
209 207
210 208 0.5.1
211 209 ~~~~~~~~~~~~~~~~~
212 210
213 211 Add help text to output for hg help.
214 212
215 213 0.5.0
216 214 ~~~~~~~~~~~~~~~~~
217 215
218 216 Improved bad password detection. Internally: extension is now able to
219 217 properly differentiate between an authentication failure and a new
220 218 request to the same url.
221 219
222 220 Fixes in debug message
223 221
224 222 Further debug messages patching
225 223
226 224 Improving debug messages handling.
227 225
228 226 Mercurial Keyring debug messages are now prefixed with
229 227 [HgKeyring] to make distinguishing them easier
230 228
231 229 0.4.6
232 230 ~~~~~~~~~~~~~~~~~
233 231
234 232 More compatibility (changed signature of httpconnection.readauthforuri
235 233 , introduced post Mercurial 1.9 - since hg.0593e8f81c71)
236 234
237 235 Fix compatibility code which did not work due to demandimport issues
238 236 (attempts to catch ImportErrors on "from mercurial.url import
239 237 readauthforuri" were not working properly).
240 238
241 239 0.4.5
242 240 ~~~~~~~~~~~~~~~~~
243 241
244 242 Mercurial 1.9 compatibility (readauthforuri has been moved into new
245 243 httpconnection module).
246 244
247 245 0.4.4
248 246 ~~~~~~~~~~~~~~~~~
249 247
250 248 Mercurial 1.8 compatibility (passwordmgr.readauthtoken() has been
251 249 moved into mercurial.url.readauthforuri).
252 250
253 251 0.4.3
254 252 ~~~~~~~~~~~~~~~~~
255 253
256 254 Keyring fork no longer is needed as keyring releases are available
257 255 again.
258 256
259 257 Workaround for gnomekeyring mercurial.demandimport incompatibility:
260 258 mercurial.demandimport, which is enabled while in a mercurial
261 259 extensions, prevents the correct import of gobject._gobject and
262 260 consequently doesn't allow the loading of the gnomekeyring module,
263 261 which can be used by keyring. This just adds the proper module to
264 262 demandimport ignore list.
265 263
266 264 0.4.2
267 265 ~~~~~~~~~~~~~~~~~
268 266
269 267 No longer raising an error when username is specified both in ~/.hgrc
270 268 and <repo>/.hg/hgrc if it is the same in both places.
271 269
272 270 Docs recommend sborho keyring fork.
273 271
274 272 0.4.1
275 273 ~~~~~~~~~~~~~~~~~
276 274
277 275 Some tweaks and docs related to prefix handling.
278 276
279 277 Explicit information that keyring is not used due to lack of username.
280 278
281 279 0.4.0
282 280 ~~~~~~~~~~~~~~~~~
283 281
284 282 Store and lookup prefix from [auth] so that password is shared amongst
285 283 shared auth entries
286 284
287 285 0.3.3
288 286 ~~~~~~~~~~~~~~~~~
289 287
290 288 Better error message
291 289
292 290 0.3.2
293 291 ~~~~~~~~~~~~~~~~~
294 292
295 293 Doc tweaks
296 294
297 295 0.3.1
298 296 ~~~~~~~~~~~~~~~~~
299 297
300 298 Introduced and documented PyPi package, added setup.py
301 299
302 300 0.2.0
303 301 ~~~~~~~~~~~~~~~~~
304 302
305 303 Added handling of SMTP passwords (tested on patchbomb extension but
306 304 should work on anything what utilizes mercurial.mail)
307 305
308 306 Docstrings mention Debian keyring packages.
309 307
310 308 0.1.1
311 309 ~~~~~~~~~~~~~~~~~
312 310
313 311 Initial public release
General Comments 0
You need to be logged in to leave comments. Login now