Given the following facts: 1) The package is at the same version in both trusty and utopic 2) The bug can only be reproduced on utopic, but obviously exists in both
I propose the following unorthodox SRU procedure: 1) The SRU is uploaded to trusty-proposed, so it builds with trusty level deps 2) The SRU is copied from trusty-proposed to utopic-proposed 3) The SRU is validated in utopic, where the bug can be properly reproduced and verified fixed 4) The SRU is released to both trusty-updates and utopic-updates Since we'll be validating the identical binary, this should prevent us from having to validate on trusty, except to smoketest that it runs and doesn't appear to crash, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393105 Title: GNUbg crashes shortly after starting game To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1393105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
