Bugzilla – Bug 114106
archway mising dependency problem
Last modified: 2005-10-12 11:07:38 UTC
when i run archway Glib.pm was missing: $ archway $ Can't locate Glib.pm in @INC (@INC contains: /usr/bin/../perllib /usr/share/archway/perllib /usr/lib/perl5/5.8.7/i586-linux-thread-multi /usr/lib/perl5/5.8.7 /usr/lib/perl5/site_perl/5.8.7/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.7/i586-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl .) at /usr/share/archway/perllib/ArchWay/Session.pm line 23. I use yast to isntall package perl-Glib then $ archway $ *** This build of Glib was compiled with glib 2.8.1, but is currently running with 2.8.0, which is too old. We'll continue, but expect problems! Can't locate Gtk2.pm in @INC (@INC contains: /usr/bin/../perllib /usr/share/archway/perllib /usr/lib/perl5/5.8.7/i586-linux-thread-multi /usr/lib/perl5/5.8.7 /usr/lib/perl5/site_perl/5.8.7/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.7/i586-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl .) at /usr/share/archway/perllib/ArchWay/Session.pm line 24. BEGIN failed--compilation aborted at /usr/share/archway/perllib/ArchWay/Session.pm line 24. Compilation failed in require at /usr/bin/archway line 26. BEGIN failed--compilation aborted at /usr/bin/archway line 26. so i instaled also perl-Gtk2 after this archway run ok excep *** This build of Glib was compiled with glib 2.8.1, but is currently running with 2.8.0, which is too old. We'll continue, but expect problems! *** This build of Gtk2 was compiled with gtk+ 2.8.2, but is currently running with 2.8.0, which is too old. We'll continue, but expect problems!
reassign it to new maintainer
updated the package and fixed the dependencies *** This build of Gtk2 was compiled with gtk+ 2.8.2, but is currently running with 2.8.0, which is too old. We'll continue, but expect problems! this shouldn't be a big problem, but i'll file a bug anyway
...actually, i won't file a bug, because the versions match in the newest release