Launchpad has imported 4 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=773443.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-01-11T20:45:06+00:00 Zooko wrote: Description of problem: gcc-4.7.0 fixes a bug that various packages rely on Version-Release number of selected component (if applicable): 4.7.0 How reproducible: 100% deterministic. Steps to Reproduce: 1. Try to build a package such as Crypto++ v5.6.1 with a pre-release of gcc 4.7.0. 2. 3. Actual results: Compile failure. Expected results: Compile success. Additional info: As reported by Jakub Jellinek: http://lists.fedoraproject.org/pipermail/devel/2011-December/160723.html As tracked on launchpad: https://bugs.launchpad.net/gcc/+bug/915018, which has links to the issue trackers for Crypto++ and pycryptopp. Reply at: https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018/comments/12 ------------------------------------------------------------------------ On 2012-01-11T22:51:37+00:00 Jakub wrote: Why are you filing it against gcc? It is completely intentional. Just fix your package(s). Reply at: https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018/comments/13 ------------------------------------------------------------------------ On 2012-01-11T23:48:09+00:00 Zooko wrote: I didn't mean to denote that it was a (current) bug in gcc. I just meant to let myself and others track the fact that the gcc 4.7.0 release (and pre-releases) interact with this bug, and I meant to link to the original gcc ticket: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24163 I guess ideally I would mark this ticket as applying to the list of packages that you posted to the mailing list, but I don't know if that's possible and if it is I'm not going to take the time to do it manually. ;-) Reply at: https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018/comments/14 ------------------------------------------------------------------------ On 2012-01-11T23:52:57+00:00 Zooko wrote: P.S. I guess I was thinking of "the package of gcc that is shipped in Fedora" as being one of the subjects of this ticket, more than "gcc itself". I figured it might help other people to understand that if they are seeing these errors, it is the combination of gcc 4.7.0 pre-release and their other packages that results in the errors. But again, I didn't intend to say that the errors were caused by gcc having a bug. Also, of course, Crypto++ and quite a few other packages are also the subjects of this issue. The launchpad ticket -- https://bugs.launchpad.net/gcc/+bug/915018 -- has links to relevant tickets in various issue trackers. For my own future reference: 1. Is there a way to express in bugzilla.redhat.com that an issue affects a package of software $X version $Y within Fedora release $Z? Ideally I would have said "This is an issue you may have if you're using the 4.7.0 pre-release distributed in Fedora Rawhide.". Is there a way to express that in the bugzilla db? 2. Is there a way to denote "This is an issue that affects $X or that the presence of $X can trigger, but is not a bug in $X?". Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018/comments/15 ** Changed in: libcrypto++ (Fedora) Status: Unknown => Invalid ** Changed in: libcrypto++ (Fedora) Importance: Unknown => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915018 Title: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on To manage notifications about this bug go to: https://bugs.launchpad.net/cryptopp/+bug/915018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
