Displaying 5 results from an estimated 5 matches for "bluecedar".
2019 Jan 23
4
Curl spec file
Hi,
I saw this spec file for curl-7.29:
https://git.centos.org/blob/rpms!curl.git/c7/SPECS!curl.spec
And was wondering if you have one for a later version.
And if not, how hard is it to modify the existing one to support later versions.
Thanks!
Roee.
2019 Jan 23
0
Curl spec file
On Jan 23, 2019, at 16:55, Roee Agami <ragami at bluecedar.com> wrote:
>
> Hi,
> I saw this spec file for curl-7.29:
> https://git.centos.org/blob/rpms!curl.git/c7/SPECS!curl.spec
>
> And was wondering if you have one for a later version.
> And if not, how hard is it to modify the existing one to support later versions.
There?s a...
2019 Jan 24
3
Curl spec file
...ows which patches should be applied to each release, do they publish it somewhere?
Roee.
?On 1/23/19, 6:35 PM, "CentOS on behalf of Jonathan Billings" <centos-bounces at centos.org on behalf of billings at negate.org> wrote:
On Jan 23, 2019, at 16:55, Roee Agami <ragami at bluecedar.com> wrote:
>
> Hi,
> I saw this spec file for curl-7.29:
> https://git.centos.org/blob/rpms!curl.git/c7/SPECS!curl.spec
>
> And was wondering if you have one for a later version.
> And if not, how hard is it to modify the existing one to suppor...
2018 Nov 06
3
openSSH versions
Hi,
I notice here:
https://www.openssh.com/releasenotes.html
That the versions always have a <number> and a <number>p1.
Does the p1 indicate a patch? So does it mean that <number> and <number>p1 are two different versions?
It doesn?t describe the differences between the two in case they are different versions.
I would appreciate some clarification.
Thanks,
Roee.
2019 Jan 29
0
Several tests failing
Hi,
I?m attempting to build a 7.63.0 RPM for centos from a spec file I created.
I am getting the following tests failures:
?These test cases failed: 206 1049 1060 1061 1232 1241 1421?
Here is an example of an output for test 206, any help to get insights into it would be greatly appreciated:
test 0206...[HTTP proxy CONNECT auth Digest]
../libtool --mode=execute /usr/bin/valgrind