On 09/15/2014 11:21 AM, Mark Wielaard wrote:
On Sun, 2014-09-14 at 11:42 +0200, Mark Wielaard wrote:
Thanks. That is a much bigger list than the packages I already filed
bugs for based on the reproquery against the debuginfo packages.
https://bugzilla.redhat.com/show_bug.cgi?id=1141461
Specifica
On Sun, 2014-09-14 at 11:42 +0200, Mark Wielaard wrote:
> Thanks. That is a much bigger list than the packages I already filed
> bugs for based on the reproquery against the debuginfo packages.
> https://bugzilla.redhat.com/show_bug.cgi?id=1141461
> Specifically missing are: cockpit, exim, gearmand
On Sun, Sep 14, 2014 at 12:03 PM, Mark Wielaard wrote:
> On Sat, 2014-09-13 at 08:49 +0300, Ville Skyttä wrote:
>>
>> FWIW, searchcode.com can search through Fedora sources, but I don't
>> know how up to date the sources they use are and the results for
>> __VALGRIND_H aren't that impressive, only
Hi Tom,
On Sun, 2014-09-14 at 10:38 +0100, Tom Hughes wrote:
> On 14/09/14 10:30, Mark Wielaard wrote:
> > On Sat, 2014-09-13 at 05:44 +0200, Ralf Corsepius wrote:
> >
> >> It also would seem reasonable to me to file a ticket to FPC, such that
> >> FPC can try to examine this case.
> >
> > I have
On Sun, 2014-09-14 at 06:14 +0200, Ralf Corsepius wrote:
> On 09/13/2014 01:52 PM, Florian Weimer wrote:
> > On 09/12/2014 06:25 PM, Michael Cronenworth wrote:
> >> You'll have to download all the source and perform a massive grep.
> >
> > You have to unpack the sources before the grep, which can b
On 14/09/14 10:30, Mark Wielaard wrote:
On Sat, 2014-09-13 at 05:44 +0200, Ralf Corsepius wrote:
It also would seem reasonable to me to file a ticket to FPC, such that
FPC can try to examine this case.
I have to apologize for not knowing how to file a ticket to FPC. Where
would I do that? I d
On Sat, 2014-09-13 at 05:44 +0200, Ralf Corsepius wrote:
> On 09/12/2014 10:53 PM, Mark Wielaard wrote:
> > Maybe people misunderstand that to mean they have to include the whole
> > file in their local source copy instead of just simply #include it?
>
> Possibly. I am not sufficiently familiar wi
On Sat, 2014-09-13 at 08:49 +0300, Ville Skyttä wrote:
> On Fri, Sep 12, 2014 at 11:44 PM, Mark Wielaard wrote:
> > On Fri, 2014-09-12 at 11:25 -0500, Michael Cronenworth wrote:
> >>
> >> You'll have to download all the source and perform a massive grep.
> >
> > Yeah, that is sadly not going to ha
On 09/13/2014 01:52 PM, Florian Weimer wrote:
On 09/12/2014 06:25 PM, Michael Cronenworth wrote:
You'll have to download all the source and perform a massive grep.
You have to unpack the sources before the grep, which can be quite a
challenge because SPEC files aren't declarative. The %prep s
On 09/12/2014 06:25 PM, Michael Cronenworth wrote:
You'll have to download all the source and perform a massive grep.
You have to unpack the sources before the grep, which can be quite a
challenge because SPEC files aren't declarative. The %prep stage
sometimes even needs build dependencies
On Fri, Sep 12, 2014 at 11:44 PM, Mark Wielaard wrote:
> On Fri, 2014-09-12 at 11:25 -0500, Michael Cronenworth wrote:
>>
>> You'll have to download all the source and perform a massive grep.
>
> Yeah, that is sadly not going to happen.
FWIW, searchcode.com can search through Fedora sources, but
On 09/12/2014 10:53 PM, Mark Wielaard wrote:
On Fri, 2014-09-12 at 19:38 +0200, Ralf Corsepius wrote:
On 09/12/2014 05:09 PM, Mark Wielaard wrote:
valgrind 3.10.0 was just released and I created packages for rawhide and
f21. Then I noticed some packages include their own copy of valgrind.h
(at
On Fri, 2014-09-12 at 19:38 +0200, Ralf Corsepius wrote:
> On 09/12/2014 05:09 PM, Mark Wielaard wrote:
> > valgrind 3.10.0 was just released and I created packages for rawhide and
> > f21. Then I noticed some packages include their own copy of valgrind.h
> > (at least libsecret, gcr, libgnome-keyr
On Fri, 2014-09-12 at 11:25 -0500, Michael Cronenworth wrote:
> On 09/12/2014 10:09 AM, Mark Wielaard wrote:
> > Is there a magic repoquery that I could run, or some other way to search
> > through all source rpm files?
>
> Unfortunately, no. Some packages compile with their local copy of valgrind
Hi Josh,
On Fri, 2014-09-12 at 08:47 -0700, Josh Stone wrote:
> On 09/12/2014 08:09 AM, Mark Wielaard wrote:
> > Is there a magic repoquery that I could run, or some other way to search
> > through all source rpm files?
>
> The header should be captured in debuginfo sources, so:
>
> $ repoquery
On 09/12/2014 05:09 PM, Mark Wielaard wrote:
Hi,
valgrind 3.10.0 was just released and I created packages for rawhide and
f21. Then I noticed some packages include their own copy of valgrind.h
(at least libsecret, gcr, libgnome-keyring, realmd, ipxe and pidgin).
Not directly related to your que
On 09/12/2014 10:09 AM, Mark Wielaard wrote:
Is there a magic repoquery that I could run, or some other way to search
through all source rpm files?
Unfortunately, no. Some packages compile with their local copy of valgrind.h and
it won't appear in a -devel or -debuginfo package due to special
On 09/12/2014 08:09 AM, Mark Wielaard wrote:
> Hi,
>
> valgrind 3.10.0 was just released and I created packages for rawhide and
> f21. Then I noticed some packages include their own copy of valgrind.h
> (at least libsecret, gcr, libgnome-keyring, realmd, ipxe and pidgin).
> That means they won't h
Hi,
valgrind 3.10.0 was just released and I created packages for rawhide and
f21. Then I noticed some packages include their own copy of valgrind.h
(at least libsecret, gcr, libgnome-keyring, realmd, ipxe and pidgin).
That means they won't have a bug fix for ppc32 (not that important since
f21 dro
19 matches
Mail list logo
