On Tuesday, April 11, 2017 at 9:32:46 AM UTC-7, Matthew Lavigne wrote: > > I looks like the 12759 defect is what we are seeing. What we were seeing > previously and expected to see was the validation of the username as an > email and then continued use forward. Looking at it, it looks like I will > have to be broken until I can figure out a quick way to patch or until we > get a 1.2.2 release with the fix in it. This is only of the few instances > where I did this hot and I have a reasonably grounded belief that with the > DB update that I can't roll back (too many new tickets in the system). > Lesson learned; validate before rolling forward next time. > > Any assistance on a quick way to get back up and running would be greatly > appreciated. > > Matthew >
You could install 1.2.2dev directly from the 1.2-stable branch. There have been few commits to the branch since the release of 1.2.1, and we work hard to avoid regressions on the -stable branches. All commits on 1.2-stable since release of 1.2.1: https://trac.edgewall.org/log/branches/1.2-stable?action=stop_on_copy&mode=stop_on_copy&rev=15761&stop_rev=15728&limit=100 Installing directly from repository branch using pip: https://trac.edgewall.org/wiki/1.3/TracInstall#Usingpip - Ryan -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
