I was trying to rebuild rubygem-passenger to fix a minor issue (Bug 6714), but it doesn't build: http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20120707170818.luigiwalser.valstar.30603/log/rubygem-passenger-2.2.9-5.mga3/build.0.20120707171102.log So, I tried syncing it with Mandriva, who has updated it once since we imported it. There is a bug in the patch to the RPM package for gem support that makes it fail to extract. It has been fixed in Mandriva, and an updated patch that would fix it in our rpm package has been provided here: https://www.mageia.org/pipermail/mageia-dev/2012-June/016522.html In the meantime, while that bug is still present, the "%setup -q" in the SPEC file has to be replaced with: %setup -q -c -T -n %{oname}-%{version} gem unpack %{SOURCE0} --target %{_builddir} Ugh, so hopefully we can fix that in Cauldron. Anyway, even building the new version still fails to build, seemingly because of a problem in our rpm package. I don't know if the patch from Mandriva would fix this too, but I'll attach the build log for that failure.
Created attachment 2530 [details] log.rubygem-passenger Log from trying to build 3.0.5
CC: (none) => shlomifWhiteboard: (none) => MGA2TOO
CC: (none) => johnny
CC: (none) => mageia
The current package actually builds in Mageia 2, so this is just a Cauldron problem.
Whiteboard: MGA2TOO => (none)
David: what should we do? Can you provide a patch for the subversion working copy at «mgarepo checkout rubygem-passenger» ? Should we simply remove/obsolete this package? Regards, -- Shlomi Fish
Shlomi: That's a good question. If it was obvious how to fix the build problems I would have fixed it, but neither the Mageia 2 version which was previously in SVN or the updated version I synced from Mandriva will build in Cauldron. As I mentioned in Bug 6487 this package seems to not fit our naming policy anyway, and furthermore, it installs a configuration file in /etc/httpd/modules.d that doesn't fit the naming standards for files that go there either (there should be a number at the beginning). I think that if nobody is interested in fixing this one, it would be a good candidate for removal. We can ask on the -dev list.
(In reply to comment #4) > Shlomi: That's a good question. If it was obvious how to fix the build > problems I would have fixed it, but neither the Mageia 2 version which was > previously in SVN or the updated version I synced from Mandriva will build in > Cauldron. As I mentioned in Bug 6487 this package seems to not fit our naming > policy anyway, and furthermore, it installs a configuration file in > /etc/httpd/modules.d that doesn't fit the naming standards for files that go > there either (there should be a number at the beginning). I think that if > nobody is interested in fixing this one, it would be a good candidate for > removal. We can ask on the -dev list. OK, let's ask there. Regards, -- Shlomi Fish
build is fixed, david can you look now ? this is an error with rpm. + /usr/lib/rpm/mageia/gem_helper.rb build -fhelper-scripts -j2 /usr/lib/rpm/mageia/gem_helper.rb:60:in `open': No such file or directory - metadata.gz (Errno::ENOENT) from /usr/lib/rpm/mageia/gem_helper.rb:60
CC: (none) => dmorganec
Fixed by D Morgan.
Status: NEW => RESOLVEDResolution: (none) => FIXED