Re: SPDX Status for Rubygems in Fedora as of 2023-06-05

Hi Jarek, I see that there are 9 packages listed that are orphaned. Can we get those removed from the list. On Tue, Jun 6, 2023 at 1:54 AM Jarek Prokop wrote: > Hi all, > > another Thursday passed, so I am back with fresh report of current SPDX > status of Rubygems. > > Regards, > Jarek > > *

Re: Unexpected files included in rubygem doc packages

On Mon, Feb 24, 2020 at 2:55 PM Breno Brand Fernandes wrote: > > Hi all, > > I had an issue today with a package I submitted to code review [1]. > > The reviewer pointed out that I was shipping font files instead of requiring > them. > And, I was also not shipping their license. > > After that,

Question about rubyforge related packages

Hi, rubygem-rubyforge was dropped back in November with "rubyforge is dead long ago, retiring (mtasaka, 20191105)" I'm ok with that. I have a package that was part of rubyforge, rubygem-ci_reporter. Looking at it's codebase, it hasn't been touched for 5 years. I was debating on just

Re: "gem unpack" support in RPM's %setup macro

On Tue, Nov 10, 2015 at 8:52 AM, Vít Ondruch wrote: > Hi guys, > > For a long time, I thought that it would be interesting to have .gem > expansion support in %setup macro. This would simply our .spec files a > bit. Finally, I gave a go to this idea and proposed this to RPM

Re: Action needed - mass rebuild FTBFS

On Tue, Jul 21, 2015 at 1:55 AM, Vít Ondruch vondr...@redhat.com wrote: Hi all, There is plenty of packages which failed to build during F23 mass rebuild: http://alt.fedoraproject.org/pub/alt/mass-rebuild/f23-failures.html If I counted correctly, there is currently 93 ruby packages failing

Re: updating rails in epel to 4.x

Hi, Sorry for the late reply, but you didn't mention which EPEL you were updating? EPEL5,6 or 7? And in reality, this is the wrong list to be asking/stating that. You need to talk about it on the EPEL list. On this list, everyone is excited to get rails updated. On the EPEL list, you'll find

Check to make sure your rubygems are in epel7

repo after a day or so. But sometime during the end they didn't. I could have sworn mine should have at least been in testing. Anyway, long story short, if you think you have a rubygem in epel7, it would be good to check and make sure it really is in there. Troy Dawson

Re: Rubygem macros avilable in EPLE6!

On 11/29/2013 02:37 PM, Ken Dreyer wrote: On Fri, Nov 29, 2013 at 4:52 AM, Vít Ondruch vondr...@redhat.com wrote: Hi, Now I realized that I should not forgot to announce, that in RHEL 6.5 was released rubygems errata [1], which adds rubygems-devel subpackage with all rubygems macros you are

Re: I need rubygem-net-ssh-multi 1.20

Hi Julian, I see that you built it for rawhide and F20. Is there anyway we could get version 1.2.0 into F19? There is a bug open for that. https://bugzilla.redhat.com/show_bug.cgi?id=1033930 Troy On 10/28/2013 09:17 AM, Guillermo Gómez wrote: :) Thanks On Mon, Oct 21, 2013 at 5:09 PM, Julian

Re: Rails 4 update and dependent packages (aoelus, mongoid, openshift)

Hi Josef, Although I don't speak for Krishna or Marcela, I say Go for it. The change has got to come sometime, and since this is in rawhide it's better to get it done early than late. The big ruby change in F19 came right on Freeze day, and it broke every one of my rubygem packages. I'd much

Removing vendor dirs from rubygems

Hi, What is the best way to remove the vendor directories from rubygems? Is there a macro for it? The problem I keep having is that the vendor directory is in the gem. And this is what we need to have in the %prep section - %prep gem unpack %{SOURCE0} %setup -q -D -T -n

Re: [ANN] gem2rpm 0.9.2 released

Hi Vit, Thanks for doing that. I had just updated my own templates and was wondering where to send them. But you already got 90% of my changes. I had one question though. In the Fedora17-18 template you have the ext variable as %{gem_extdir_mri} Does that work with F17 and F18? I though it

Re: %gem_install macro

On 03/18/2013 04:10 AM, Vít Ondruch wrote: Hi everybody, I have noticed, that although you are updating your packages to be buildable with F19, you are not doing it properly. The %gem_install macro, which is mentioned in guidelines, was not introduced just to annoy you. It should help you.