Bug 1052383

This does not look like Apache httpd bug, reassigning to info2html maintainer.

(In reply to Petr Gajdos from comment #1)
> This does not look like Apache httpd bug, reassigning to info2html
> maintainer.

Explain what an 

   File IO Error

does mean in your opinion?  If the links do exist and do point to the correct file then this is not a problem of info2html. This because info2html only delivers the link and nothing nmore or less.

Beside this I can not reproduce ... I guess a broken setup of the Apache like wrong owner and/or access rights as well as apparmor which forbids access as well

Please try the package from here, this one should work:
http://download.opensuse.org/repositories/home:/wolfi323:/branches:/Publishing/openSUSE_Leap_42.3/

The File IO error is caused by the (open)SUSE specific patch info2html-2.0.dif, in particular the call to DirnameCheck()...

(In reply to Wolfgang Bauer from comment #3)
> Please try the package from here, this one should work:
> http://download.opensuse.org/repositories/home:/wolfi323:/branches:/
> Publishing/openSUSE_Leap_42.3/
> 
> The File IO error is caused by the (open)SUSE specific patch
> info2html-2.0.dif, in particular the call to DirnameCheck()...

Interesting ... I'm not aware that had been a bug report about this nor about the misleading $* warning with newer perl 5+

(In reply to Wolfgang Bauer from comment #3)
> Please try the package from here, this one should work:
> http://download.opensuse.org/repositories/home:/wolfi323:/branches:/
> Publishing/openSUSE_Leap_42.3/
> 
> The File IO error is caused by the (open)SUSE specific patch
> info2html-2.0.dif, in particular the call to DirnameCheck()...

I am not sure if this suggestion if for me but I would prefer to wait for an official patch.

Installing the suggested package would change vendor info from opensuse to obs://build.opensuse.org/home:wolfi323.

Also couldn't verify the package signature.

(In reply to Eduardo Reyes from comment #5)
> (In reply to Wolfgang Bauer from comment #3)
> > Please try the package from here, this one should work:
> > http://download.opensuse.org/repositories/home:/wolfi323:/branches:/
> > Publishing/openSUSE_Leap_42.3/
> > 
> > The File IO error is caused by the (open)SUSE specific patch
> > info2html-2.0.dif, in particular the call to DirnameCheck()...
> 
> I am not sure if this suggestion if for me but I would prefer to wait for an
> official patch.
> 
> Installing the suggested package would change vendor info from opensuse to
> obs://rudin.suse.de:8894/home:wolfi323.
> 
> Also couldn't verify the package signature.

https://api.opensuse.org/build/home:WernerFink:branches:openSUSE:Leap:42.3:Update/openSUSE_Leap_42.3_Update/x86_64/info2html.openSUSE_Leap_42.3_Update/info2html-2.0-223.1.noarch.rpm

this is with a fixed DirnameCheck() which now allows empty infodir path

This is an autogenerated message for OBS integration:
This bug (1052383) was mentioned in
https://build.opensuse.org/request/show/514964 Factory / info2html
https://build.opensuse.org/request/show/514971 42.3 / info2html

(In reply to Dr. Werner Fink from comment #6)
> (In reply to Eduardo Reyes from comment #5)
> > (In reply to Wolfgang Bauer from comment #3)
> > > Please try the package from here, this one should work:
> > > http://download.opensuse.org/repositories/home:/wolfi323:/branches:/
> > > Publishing/openSUSE_Leap_42.3/
> > > 
> > > The File IO error is caused by the (open)SUSE specific patch
> > > info2html-2.0.dif, in particular the call to DirnameCheck()...
> > 
> > I am not sure if this suggestion if for me but I would prefer to wait for an
> > official patch.
> > 
> > Installing the suggested package would change vendor info from opensuse to
> > obs://rudin.suse.de:8894/home:wolfi323.
> > 
> > Also couldn't verify the package signature.
> 
> https://api.opensuse.org/build/home:WernerFink:branches:openSUSE:Leap:42.3:
> Update/openSUSE_Leap_42.3_Update/x86_64/info2html.openSUSE_Leap_42.3_Update/
> info2html-2.0-223.1.noarch.rpm
> 
> this is with a fixed DirnameCheck() which now allows empty infodir path

I can confirm that the issue is not present in the package http://download.opensuse.org/repositories/home:/wolfi323:/branches:/Publishing/openSUSE_Leap_42.3/noarch/info2html-2.0-421.1.noarch.rpm suggested by Wolfgang Bauer which BTW if far ahead version 2.0-223 suggested  by Dr. Werner Fink.

Hopefully the updated package will be included in the main stream soon.

Thanks to all!

(In reply to Eduardo Reyes from comment #8)
> which BTW if far ahead version 2.0-223 suggested
> by Dr. Werner Fink.

No, it is not "ahead" at all.
That's just the rebuild count...

Actually the latter one is the proper fix.

And I can confirm that it works here too.

> Hopefully the updated package will be included in the main stream soon.

It has been submitted to 42.3, so should be released as update in about a week.

You can already install that upcoming update from here btw:
http://download.opensuse.org/repositories/openSUSE:/Maintenance:/7086/openSUSE_Leap_42.3_Update/
(this does have "openSUSE" as vendor)

openSUSE-RU-2017:2159-1: An update that has one recommended fix can now be installed.

Category: recommended (low)
Bug References: 1052383
CVE References: 
Sources used:
openSUSE Leap 42.3 (src):    info2html-2.0-223.1

(In reply to Wolfgang Bauer from comment #9)
> (In reply to Eduardo Reyes from comment #8)
> > which BTW if far ahead version 2.0-223 suggested
> > by Dr. Werner Fink.
> 
> No, it is not "ahead" at all.
> That's just the rebuild count...
> 
> Actually the latter one is the proper fix.
> 
> And I can confirm that it works here too.
> 
> > Hopefully the updated package will be included in the main stream soon.
> 
> It has been submitted to 42.3, so should be released as update in about a
> week.
> 
> You can already install that upcoming update from here btw:
> http://download.opensuse.org/repositories/openSUSE:/Maintenance:/7086/
> openSUSE_Leap_42.3_Update/
> (this does have "openSUSE" as vendor)

I thought build numbers were auto-generated and reflected chronological builds hence my use of "ahead". Now I am curious about the meaning of the build #.

(In reply to Eduardo Reyes from comment #11)
> I thought build numbers were auto-generated and reflected chronological
> builds hence my use of "ahead".

Yes, that's true.
But only if you compare packages from the same repo/project.

In this case, they were from completely different (and independent) projects, the build number has absolutely no relevance in that case.