Bug 634759
| Summary: | Review Request: rubygem-pkg-config - A pkg-config implmenetation by Ruby | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mamoru TASAKA <mtasaka> |
| Component: | Package Review | Assignee: | Michael Stahnke <mastahnke> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | fedora-package-review, mastahnke, notting |
| Target Milestone: | --- | Flags: | mastahnke:
fedora-review+
j: fedora-cvs+ |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-09-25 21:38:47 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 635302 | ||
|
Description
Mamoru TASAKA
2010-09-16 22:12:57 UTC
I'll take this one. I'll check it out in depth once rubygem-hoe is in fc14 testing. (tomorrow I would guess) Should this build in rawhide? It looks like perhaps hoe was not updated in rawhide? I am pulling in rubygem-hoe.noarch 0:2.6.2-2.fc14 from mock. This is a snip of build.log from mock, fedora-rawhide-i386 Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.yQiJNx + umask 022 + cd /builddir/build/BUILD + cd rubygem-pkg-config-1.0.3 + unset DISPLAY + pushd ./usr/lib/ruby/gems/1.8/gems/pkg-config-1.0.3 ~/build/BUILD/rubygem-pkg-config-1.0.3/usr/lib/ruby/gems/1.8/gems/pkg-config-1.0.3 ~/build/BUILD/rubygem-pkg-config-1.0.3 + rake test --verbose --trace (in /builddir/build/BUILD/rubygem-pkg-config-1.0.3/usr/lib/ruby/gems/1.8/gems/pkg-config-1.0.3) rake aborted! No such file or directory - Manifest.txt /usr/lib/ruby/gems/1.8/gems/hoe-2.6.2/lib/hoe.rb:626:in `initialize' /usr/lib/ruby/gems/1.8/gems/hoe-2.6.2/lib/hoe.rb:626:in `open' /usr/lib/ruby/gems/1.8/gems/hoe-2.6.2/lib/hoe.rb:626:in `read_utf' /usr/lib/ruby/gems/1.8/gems/hoe-2.6.2/lib/hoe.rb:355:in `define_spec' /usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:425:in `initialize' (In reply to comment #2) > Should this build in rawhide? > > It looks like perhaps hoe was not updated in rawhide? I am pulling in > rubygem-hoe.noarch 0:2.6.2-2.fc14 from mock. - Yes, once rubygem-hoe-2.6.2-3.fc14 is pushed into F14 stable repository, it is also inherited into rawhide tree. And I won't build packages for F-15 for now unless it is really needed. > This is a snip of build.log from mock, fedora-rawhide-i386 > > > Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.yQiJNx > + umask 022 > + cd /builddir/build/BUILD > + cd rubygem-pkg-config-1.0.3 > + unset DISPLAY > + pushd ./usr/lib/ruby/gems/1.8/gems/pkg-config-1.0.3 > ~/build/BUILD/rubygem-pkg-config-1.0.3/usr/lib/ruby/gems/1.8/gems/pkg-config-1.0.3 > ~/build/BUILD/rubygem-pkg-config-1.0.3 > + rake test --verbose --trace > (in > /builddir/build/BUILD/rubygem-pkg-config-1.0.3/usr/lib/ruby/gems/1.8/gems/pkg-config-1.0.3) > rake aborted! > No such file or directory - Manifest.txt > /usr/lib/ruby/gems/1.8/gems/hoe-2.6.2/lib/hoe.rb:626:in `initialize' > /usr/lib/ruby/gems/1.8/gems/hoe-2.6.2/lib/hoe.rb:626:in `open' > /usr/lib/ruby/gems/1.8/gems/hoe-2.6.2/lib/hoe.rb:626:in `read_utf' > /usr/lib/ruby/gems/1.8/gems/hoe-2.6.2/lib/hoe.rb:355:in `define_spec' > /usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:425:in `initialize' - Yes, so rubygem-hoe >= 2.6.2-3 is needed (this issue is reported on hoe bug tracker)
>
> - Yes, once rubygem-hoe-2.6.2-3.fc14 is pushed into F14 stable
> repository, it is also inherited into rawhide tree.
> And I won't build packages for F-15 for now unless it is really
> needed.
>
FESCo officially recommended publishing separate rawhide builds a few weeks ago. I would also like to see a rawhide build.
rubygem-pkg-config.src: W: spelling-error Summary(en_US) implmenetation -> implementation
I assume you can fix that upon import. Everything else looks good.
---------------------------------------------
Package rubygem-pkg-config is APPROVED.
---------------------------------------------
Thank you for review! New Package SCM Request ======================= Package Name: rubygem-pkg-config Short Description: A pkg-config implmenetation by Ruby Owners: mtasaka Branches: f14 f13 f12 InitialCC: Git done (by process-git-requests). Rebuilt for F-14/13/12, submitted push requests on bodhi. Thank you for the review and GIT procedure, closing. Mamoru, can I maintain this in EPEL? (In reply to comment #8) > Mamoru, can I maintain this in EPEL? Please feel free to do so. Package Change Request ====================== Package Name: rubygem-pkg-config New Branches: el5 el6 Owners: stahnma InitialCC: Mamoru has stated I may maintain any of his ruby packages in EPEL Git done (by process-git-requests). |