On Tue, 4 Feb 2020 17:09:02 +
John Pilkington wrote:
> 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.
Good catch!
___
users mai
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 +
John Pilkington 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:
spec
On 01/02/2020 18:14, stan via users wrote:
On Sat, 1 Feb 2020 13:27:15 +
John Pilkington 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
--directo
On Sat, 1 Feb 2020 13:27:15 +
John Pilkington 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 $TMPS
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
giving
curl: (35) error:1409441:SSL routines:ssl3_re
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
giving
curl: (35) error:1409441:SSL routines:ssl3_read_bytes:sslv3 alert
handshake failure
I h