On 01/02/2020 22:22, John Pilkington wrote:
On 01/02/2020 18:14, stan via users wrote:
> On Sat, 1 Feb 2020 13:27:15 +0000
> John Pilkington <johnpilk222(a)gmail.com> wrote:
>> On 01/02/2020 12:03, John Pilkington wrote:
>>> I have been using a script in F30 to build rpms for MythTV. It
>>> worked yesterday. Today it fails:
>>> spectool --get-files --force --source=0
>>> --directory=$TMPSDIR/SOURCES $TMPSDIR/SPECS/mythtv.spec
>>> curl: (35) error:1409441:SSL routines:ssl3_read_bytes:sslv3 alert
>>> handshake failure
>>> I have rebooted.
>>> Does this need a BZ?
> I think is does.
Thanks for the suggestions.
The --verbose log showed a connection to github, but whois identified it
as BT, my ISP. Power-cycling my BT Hub appears to have fixed things.
Sorry for the noise.
> Try commenting the --insecure in the curlrc file and see what happens.
> Then post both the original problem and the result with --insecure
> disabled in the bugzilla.
> If you could get better error information that would be useful. Try
> adding -v or --verbose to the curlrc file temporarily while testing
>>> John P
>> That was in 5.4.14. The same thing happens in 5.4.12. Seven
>> packages were updated yesterday. 'spectool --help' references
>> /etc/rpmdevtools/curlrc, which contains '--insecure', and that seems
>> to be no longer in effect.