[03:42] <dhooligan> I'm a new person looking to contribute. If a bzr branch command has OUT-OF-DATE when it downloads the repository, is that a problem?
[03:43] <dhooligan> Even if the branch downloaded anyway
[04:27] <pleia2> dhooligan: when/where exactly does it say that, and what version of Ubuntu are you running?
[04:29] <pleia2> dhooligan: this seems relevent: http://packaging.ubuntu.com/html/udd-getting-the-source.html#ensuring-the-version-is-up-to-date
[04:40] <pleia2> ah, looks like you found help elsewhere
[04:40]  * pleia2 off to dinner
[04:43] <dhooligan> pleia2, thanks for your help! I've been looking at that page as well. I'm currently being helped in the ubuntu-quality channel
[18:25] <saiarcot895> Can someone nominate bug #1412246 for Utopic and Trusty?
[18:26] <teward> saiarcot895: nominated - confirm that vivid is unaffected before continuing with the sru procedures.
[18:26] <teward> nominated, but not approved*
[18:27] <saiarcot895> Based on build logs, Vivid appears to be unaffected (or rather, fixed).
[18:28] <teward> saiarcot895: if that's the case then we can 'Fix Released' Vivid - but you should check and confirm this, if possible
[18:28] <teward> (standard triage guideline, I know :P)
[18:31] <saiarcot895> teward: Would this work? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757271
[18:31] <saiarcot895> message 10 in that thread
[18:32] <saiarcot895> Vivid currently has 5.3.2-2build1, whereas that was fixed in 5.3.1.
[18:32] <teward> saiarcot895: is that the upstream equivalent bug?
[18:32] <teward> (upstream being Debian)
[18:32] <saiarcot895> yes
[18:37] <teward> saiarcot895: done, and I attached my reasonings.  I also linked the debian bug
[18:37] <saiarcot895> teward: thank you.
[18:40]  * teward needs to script this out next time >.<