[Xmltv-devel] 6/19 release... any objections? _ar/_fr_kazer broken in windows binaries

[dekarl]

Hi Robert,

A reminder: I'm planning on a 6/19 release... any objections, now would be the time!

I have had a look at the alpha.exe today and noticed that

_ar uses "switch" which seems to be not supported in that version of perl
(_is uses it too, but is disabled on windows for other reasons)

_fr_kazer can't find it's IO::Uncompress::Unzip. I thought it's a core module
and didn't add it to the dependencies.


So both grabbers with prominent changes are broken in the windows binaries.


I can rewrite _ar's usage of switch into an if/elsif/else construct if that helps.
Can you take a look at the dependencies of _fr_kazer on windows?

Regards,
Karl

___________________________________________________________
Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die
Toolbar eingebaut! http://produkte.web.de/go/toolbar

[dekarl]

Post by dekarl

A reminder: I'm planning on a 6/19 release... any objections, now would be the time!

_ar uses "switch" which seems to be not supported in that version of perl
(_is uses it too, but is disabled on windows for other reasons)

I have prepared patches to drop usage of Switch.pm as it is giving me headaches
with different behaviour on various versions of perl. (core vs. noncore and bugs)

Both grabbers validate fine after the patch and return equal results as before the patch.
I'd prefer if they could be reviewed this close to the release.

Regards,
Karl
___________________________________________________________
Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die
Toolbar eingebaut! http://produkte.web.de/go/toolbar

[Nick Morrott]

Post by dekarl

Post by dekarl

A reminder: I'm planning on a 6/19 release... any objections, now would be the time!

_ar uses "switch" which seems to be not supported in that version of perl
(_is uses it too, but is disabled on windows for other reasons)

I have prepared patches to drop usage of Switch.pm as it is giving me headaches
with different behaviour on various versions of perl. (core vs. noncore and bugs)
Both grabbers validate fine after the patch and return equal results as before the patch.
I'd prefer if they could be reviewed this close to the release.

Both of these patches were applied 8 weeks ago - are there any other
issues holding up the release?

Cheers,
Nick

[Robert Eden]

Post by dekarl
I'd prefer if they could be reviewed this close to the release.
Both of these patches were applied 8 weeks ago - are there any other
issues holding up the release?

The release was made on 6/22. Do we need another one?

Robert

[Nick Morrott]

Post by dekarl
I'd prefer if they could be reviewed this close to the release.
Both of these patches were applied 8 weeks ago - are there any other
issues holding up the release?

The release was made on 6/22.  Do we need another one?

Apologies. I didn't notice any release notifications and sourceforge
is still advertising 0.5.59 as the latest release. I noticed the .60
and .61 tags in CVS, just didn't realise the release had been made.

Does SF need a poke to convince it that newer releases have been made?

Cheers,
Nick

[Robert Eden]

Apologies. I didn't notice any release notifications and sourceforge is still advertising 0.5.59 as the latest release. I noticed the .60 and .61
tags in CVS, just didn't realise the release had been made. Does SF need a poke to convince it that newer releases have been made? Cheers, Nick

Interesting.. I see it in the files section.

I'll poke around... I really liked the old SF release manager better.

Robert

[Karl Dietz]

Post by Robert Eden

Post by dekarl
I'd prefer if they could be reviewed this close to the release.
Both of these patches were applied 8 weeks ago - are there any other
issues holding up the release?

The release was made on 6/22. Do we need another one?

I missed that the fix for _huro is out, too :(

Just a heads up, I have already two new importers in the pipeline for
the next release (two more copies of _se_swedb) and _pt_meo doesn't
need much to be runable on windows. (just do the URL Encoding ourselves
instead of adding a new dependency)

If I get the time in the coming 2 weeks I'll likely ask for another
release.