Padre: Ticket #170: unset DISPLAYhttp://padre.perlide.org/trac/ticket/170
<p>
The packaging of Padre-0.20 is impossible, because rpm unset display, before the build. It creates this failure:
Error: Unable to initialize gtk, is DISPLAY set properly?
Error while autoloading 'Wx::wxVERSION_STRING' at ./Build.PL line 122
</p>
<p>
I suppose this bug was introduced by checking the Wx version. It is regression to 0.17, which was the last packaged version. Maybe I can simply remove this check from Fedora distro, because rpm is checking the correct version itself.
</p>
<p>
perl -MWx -le'print "Wx Version: $Wx::VERSION " . Wx::wxVERSION_STRING()'
Wx Version: 0.89 wxWidgets 2.8.9
</p>
en-usPadre/static/logo.pnghttp://padre.perlide.org/trac/ticket/170
Trac 1.0.1szabgabFri, 12 Dec 2008 12:34:13 GMThttp://padre.perlide.org/trac/ticket/170#comment:1
http://padre.perlide.org/trac/ticket/170#comment:1
<p>
We added it there in an attempt to make it easier to get bug reports.
</p>
<p>
I wonder if we should check $ENV{DISPLAY} before doing so or to make a special case for Fedora.
Is there a way the Build.PL can recognize it is running in the Fedora build environment?
</p>
TicketmmaslanoFri, 12 Dec 2008 13:05:48 GMThttp://padre.perlide.org/trac/ticket/170#comment:2
http://padre.perlide.org/trac/ticket/170#comment:2
<p>
This is not only Fedora bug, but it's a problem for all rpm builds or for all build systems, which don't have display set as default. Is there any other way how to check Wx version?
</p>
TicketmmaslanoThu, 18 Dec 2008 11:47:04 GMThttp://padre.perlide.org/trac/ticket/170#comment:3
http://padre.perlide.org/trac/ticket/170#comment:3
<p>
Hm, I was able to switch the problematic test in 0.20. But in 0.21 I wasn't able to track down, which package is trying to initialize gtk.
</p>
TicketmmaslanoThu, 18 Dec 2008 12:00:09 GMThttp://padre.perlide.org/trac/ticket/170#comment:4
http://padre.perlide.org/trac/ticket/170#comment:4
<p>
My last attempt to install Padre-0.21 from cpan also failed. I assume this problem can't be distro specific.
...
Padre-0.21/script/
Padre-0.21/script/padre
Padre-0.21/META.yml
Padre-0.21/Makefile.PL
Padre-0.21/MANIFEST
Padre-0.21/HACKING.txt
CPAN: File::Temp loaded ok (v0.20)
</p>
<blockquote>
<p>
CPAN.pm: Going to build S/SM/SMUELLER/Padre-0.21.tar.gz
</p>
</blockquote>
<p>
Checking if your kit is complete...
Looks good
Error: Unable to initialize gtk, is DISPLAY set properly?
Warning: No success on command<a href="http://padre.perlide.org/trac/usr/bin/perl">Makefile.PL</a>
</p>
<blockquote>
<p>
SMUELLER/Padre-0.21.tar.gz
/usr/bin/perl Makefile.PL -- NOT OK
</p>
</blockquote>
<p>
Running make test
</p>
<blockquote>
<p>
Make had some problems, won't test
</p>
</blockquote>
<p>
Running make install
</p>
<blockquote>
<p>
Make had some problems, won't install
</p>
</blockquote>
<p>
Failed during this command:
</p>
<blockquote>
<p>
SMUELLER/Padre-0.21.tar.gz : writemakefile NO '/usr/bin/perl Makefile.PL' returned status 6
</p>
</blockquote>
TicketszabgabThu, 18 Dec 2008 13:45:01 GMThttp://padre.perlide.org/trac/ticket/170#comment:5
http://padre.perlide.org/trac/ticket/170#comment:5
<p>
When we used Module::Build (up till 0.20) it could check the require minimum version of the
Wx related things without a DISPLAY.
</p>
<p>
Once we switched to Module::Install the requires Wx, gives that error when calling <a class="missing wiki">WriteAll?</a>
</p>
<p>
We could skip that requires call when the DISPLAY is not set but maybe something in MI can be fixed so it won't create that error about gtk.
</p>
TicketszabgabFri, 26 Dec 2008 09:49:18 GMTstatus changed; resolution sethttp://padre.perlide.org/trac/ticket/170#comment:6
http://padre.perlide.org/trac/ticket/170#comment:6
<ul>
<li><strong>status</strong>
changed from <em>new</em> to <em>closed</em>
</li>
<li><strong>resolution</strong>
set to <em>fixed</em>
</li>
</ul>
<p>
supposed to be fixed in 0.22
please reopen this bug if it is still there.
</p>
Ticket