On Thu, 4 Mar 2010, Dirk Eddelbuettel wrote: > | > I think we can close this. Ggobi is more or less frozen upstream; normal > | > releases would not require autopoint and I only needed auto* as I worked > off > | > SVN for one interim release due to the recent libtool CVE. > | > | Please note that I have only reported this bug against packages which > | are known to use autopoint. I verified this using sbuild and a > | modified autopoint which says "Hello, I'm autopoint" and then looking > | at the build logs. > | > | In other words: If you receive this bug, most likely there is > | actually something to fix. > > You _completely_ missed what I wrote. Let me try again: > > You happen to have hit a single one-off upload due to a CVE > issue. Regular buids don't use it. Hence no fix as I'll simply roll back > the one-off. Clearer?
Hmm, I'm not 100% sure, but I infer from your explanations that your plans were for version -1 to use autopoint and for version -2 not to use it anymore (is this right?). But I didn't check version -1, I checked version -2, so I reported it against version -2. Here is an excerpt from the build log, note the version number: ggobi_2.1.9~20091212-2.dsc exists in .; copying to chroot [...] autoreconf: Entering directory `.' autoreconf: running: autopoint --force HELLO. I AM AUTOPOINT. (output from the modified autopoint) Is it clear that the report is against version -2, not against version -1? Believe me, I have been very careful to ensure that the "Version:" pseudoheader in the report matches a version actually showing the bug. Thanks. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
