Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#17070 - [ruby-gdkpixbuf2] is empty

Attached to Project: Community Packages
Opened by Giuseppe Borzi (gborzi) - Sunday, 08 November 2009, 22:08 GMT
Last edited by Stefan Husmann (stefanhusmann) - Monday, 09 November 2009, 19:56 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Stefan Husmann (stefanhusmann)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: ruby-gdkpixbuf2 has been recently updated to 0.19.3-1, but the package is empty. For example "pacman -Ql ruby-gdkpixbuf2" returns nothing and a "tar -tzf /var/cache/pacman/pkg/ruby-gdkpixbuf2-0.19.3-1-x86_64.pkg.tar.gz " returns only ".PKGINFO". I've tried to rebuild the package, but the compilation fails with this error message

....
creating ruby-gdkpixbuf2.pc
/home/gborzi/store/lab/aurbuild/ruby-gdkpixbuf2/src/ruby-gtk2-0.19.3/glib/src/lib/pkg-config.rb:89:in `description': undefined method `[]' for nil:NilClass (NoMethodError)
from /home/gborzi/store/lab/aurbuild/ruby-gdkpixbuf2/src/ruby-gtk2-0.19.3/glib/src/lib/mkmf-gnome2.rb:153:in `block in create_pkg_config_file'
from /home/gborzi/store/lab/aurbuild/ruby-gdkpixbuf2/src/ruby-gtk2-0.19.3/glib/src/lib/mkmf-gnome2.rb:146:in `open'
from /home/gborzi/store/lab/aurbuild/ruby-gdkpixbuf2/src/ruby-gtk2-0.19.3/glib/src/lib/mkmf-gnome2.rb:146:in `create_pkg_config_file'
from /home/gborzi/store/lab/aurbuild/ruby-gdkpixbuf2/src/ruby-gtk2-0.19.3/gdkpixbuf/extconf.rb:30:in `<main>'
extconf.rb: Leaving directory 'gdkpixbuf'

makepkg doesn't detect the error and builds the empty package.


Additional info:
* package version(s): ruby-gdkpixbuf2 0.19.3-1
* config and/or log files etc.


Steps to reproduce:
Download ruby-gdkpixbuf2-0.19.3-1package for x86_64 and check the content.
This task depends upon

Closed by  Stefan Husmann (stefanhusmann)
Monday, 09 November 2009, 19:56 GMT
Reason for closing:  Fixed
Comment by Giuseppe Borzi (gborzi) - Sunday, 08 November 2009, 23:50 GMT
I've found the culprit of the above problem. It's ruby-gconf2 0.19.3, whose pkgfile is a directory containing the actual pkgfile, i.e.

tar -tzf /var/cache/pacman/pkg/ruby-gconf2-0.19.3-1-x86_64.pkg.tar.gz|grep pkgconfig

returns

usr/lib/pkgconfig/
usr/lib/pkgconfig/ruby-gconf2.pc/
usr/lib/pkgconfig/ruby-gconf2.pc/ruby-gconf2.pc

after fixing ruby-gconf2 0.19.3, ruby-gdkpixbuf compiles without problems. Please note that ruby-gtk2 is still at 0.19.1. I successfully compiled ruby-gtk2 0.19.3 only after correcting the problems in ruby-gconf2 and ruby-gdkpixbuf.
There are similar problems on i686: ruby-gdkpixbuf doesn't install because the package contains a file "usr/lib/pkgconfig" instead of "/usr/lib/pkgconfig/ruby-gdkpixbuf2.pc" and ruby-pango is empty. The problem is still in ruby-gconf2 0.19.3 pkgfile. Fixed by recompiling ruby-gconf2, ruby-gdkpixbuf, and ruby-pango.
Please note that:
for ruby-gconf2 there is no need to move the pkgfile;
for ruby-gdkpixbuf2 you need to correct the the pkgfile from /usr/lib/pkgconfig to /usr/lib/pkgconfig/ruby-gdkpixbuf2.pc;
for ruby-gtk2 there is no need to move the pkgfile;
for ruby-pango there is no need to move the pkgfile.
Comment by Stefan Husmann (stefanhusmann) - Monday, 09 November 2009, 09:40 GMT
Thank you! Should be fixed in -2 pkgver of both packages.
Comment by Giuseppe Borzi (gborzi) - Monday, 09 November 2009, 11:07 GMT
Please note that ruby-pango needs to be fixed, because on i686 it's an empty package.
Comment by Stefan Husmann (stefanhusmann) - Monday, 09 November 2009, 15:23 GMT
ruby-pango is now also fixed.
Comment by Giuseppe Borzi (gborzi) - Monday, 09 November 2009, 19:02 GMT
Thanks, now it's OK on i686 too. Do you have problems compiling ruby-gtk2 which is still at 0.19.1?
Comment by Stefan Husmann (stefanhusmann) - Monday, 09 November 2009, 19:56 GMT
No, just overlooked it. It is on the way now.

Loading...