This was fixed in 0.4.0+2016.05.20.git.40ee44c664-6, and plucky now has
-7. Therefore I'm marking the plucky task as fix released.
** Also affects: python-seamicroclient (Ubuntu Plucky)
Importance: Undecided
Status: Confirmed
** Changed in: python-seamicroclient (Ubuntu Plucky)
S
I'm not sure this warrants an SRU for noble and oracular, as it's just a
warning. I agree it pollutes the upgrade output a bit, but there is no
other ill effect at the moment, is there?
In any case, the patch is at [1]. If someone wants to follow the SRU
process, I believe at the very least it cou
> how long should it take for this fix to land in Noble?
The documentation seems to have moved around since the last time I
looked at it, but you may want to check the Stable Release Updates
https://canonical-sru-docs.readthedocs-
hosted.com/en/latest/howto/standard/
The short version is:
Once th
given that this is fixed in Debian already, how long should it take for
this fix to land in Noble?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2090954
Title:
SyntaxWarning: invalid escape sequence
Thanks for reporting.
Marking confirmed based on corresponding Debian bug report
** Bug watch added: Debian Bug tracker #1086960
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086960
** Also affects: python-seamicroclient (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1
** Changed in: python-seamicroclient (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2090954
Title:
SyntaxWarning: invalid escape sequence
To manage no
