Re: Let's get a new release out in the next week
Geoff Westcott via xmltv-devel <[email protected]> Wed, 22 Feb 2023 13:10:45 +0000
| Newsgroups | gmane.comp.tv.xmltv.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 22 Feb 2023 12:06:33 +0000, Nick Morrott wrote: > On Tue, 21 Feb 2023 at 19:44, Geoff Westcott via xmltv-devel > <[email protected]> wrote: > > > > I've looked at those 3 grabbers... > > > > ar > > Source site broken: Probably permanent (company defunct - taken over by TVArgentina). > > > > fi_sv > > Fixed. (Credit stefanb2) > > Needed an Accept-Language header as per #197. > > > > tr > > Agreed. It only works with a forged User-Agent string. (It's probably nothing personal against XMLTV - it seems to be passing known browser UA strings only.) > > Dear Geoff, > > Thanks for the "borrowed" fix from tv_grab_fi from #197 and another > pair of eyes on _ar (which has always caused issues when testing) > > Let's go ahead and disable _ar and _tr. Probably best to push out a > 1.2.1 patch release to fix _fi_sv and drop _ar. Serves me right for > not waiting another day... > > Cheers, > Nick Hi Nick, Nah it was my fault - I forgot to do it on Monday. I was going to email you to say I was working on them..but then forgot to do that as well! :-( I've just tried to replace "win32" with "win64" - since we no longer build 32-bit Win exe - please can you check I've updated everything correctly on the build/make front? I note that https://github.com/XMLTV/xmltv/tree/master/doc shows the readme.win32 by default - do you know how to get it to display the README.win64 instead? (Perhaps we need a copy of README.win64 as README.md - would that take precedence?) Geoff