Hello Nikolaus, or anyone else affected, Accepted s3ql into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/s3ql/1.12-1ubuntu0.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: s3ql (Ubuntu Raring) Status: New => Fix Committed ** Tags added: verification-needed ** Changed in: s3ql (Ubuntu Raring) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179281 Title: Data corruption with eglibc 2.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1179281/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
