Dropping primary ownership of several ruby packages

I haven't had the time to be a good steward on a number of these packages. Several I picked up when I was much more involved with EPEL, and others when I was just doing lots of ruby. Please feel free to take them over, as I will be orphaning them in pkgdb soon. - rpms/ruby-dbus

Re: Puppet 4

As a point of moderation, we could probably break out the FHS/stateless discussion into its own thread, as at this point this has nearly nothing to do with Puppet. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: htt

Re: Puppet 4

On Fri, Jun 5, 2015 at 8:15 AM, Michael Stahnke wrote: > > > On Fri, Jun 5, 2015 at 6:31 AM, John Florian > wrote: > >> On Fri, 2015-06-05 at 01:12 -0400, Nico Kadel-Garcia wrote: >> > On Thu, Jun 4, 2015 at 2:21 PM, John Florian >> wrote: >> > &

Re: Puppet 4

On Fri, Jun 5, 2015 at 6:31 AM, John Florian wrote: > On Fri, 2015-06-05 at 01:12 -0400, Nico Kadel-Garcia wrote: > > On Thu, Jun 4, 2015 at 2:21 PM, John Florian > wrote: > > > I’ve been curious how Fedora plans to tackle inclusion of Puppet 4, but > > > haven’t heard even a peep on the subject

Re: Puppet 4

On Thu, Jun 4, 2015 at 2:21 PM, Haïkel wrote: > 2015-06-04 20:21 GMT+02:00 John Florian : > > I’ve been curious how Fedora plans to tackle inclusion of Puppet 4, but > > haven’t heard even a peep on the subject. As described[1], they’ve > moved to > > an all-in-one packaging process that “includ

Re: Remove gcc, gcc-c++ and make from minimal build root

> > Vít Ondruch wrote: > >> I'd like to collect some feedback about the $SUBJECT, i.e. making > >> minimal build root really minimal, explicitly specifying build > >> dependencies, etc. > +1 As somebody who works on software that sometimes get rebuilt by other people not using koji or mock, I

Re: Contact info - Jeroen van Meeuwen (kanarip)

+Ruby-sig bcc fedora-devel > > > > Hey, sorry for not getting some of these updated (you also didn't stay > on #fedora-ruby long enough for me to respond). I find that updating many > of these breaks API, because ruby library authors are really good at fixing > security problems while introducing

Re: Contact info - Jeroen van Meeuwen (kanarip)

g.cgi?id=771151 > > Looks scary, but it the end it`s just rails, rubygems and rack. All of > these are co-maintained with Michael Stahnke, which I have no luck > contacting either. There are actually more unfixed vulnerabilities, but I > am confident they can be fixed by more active mainta

Re: New version of Copr

On Mon, Jan 27, 2014 at 5:12 PM, Miroslav Suchy wrote: > Hi, > I just deployed new version of Copr. > > Changes: > * copr-cli has been build for epel6 (no planned build for el5 due > dependency on python-requests) > * you should see less internal server errors. Especially when deleting > tasks

Re: Re: Re: F20: Puppet depchain pulls in Java

On Sat, Jan 18, 2014 at 5:55 AM, Mo Morsi wrote: > On 01/18/2014 01:40 AM, Michael Stahnke wrote: > > On Fri, Jan 17, 2014 at 6:53 PM, Rahul Sundaram > wrote: > > Hi > > > On Fri, Jan 17, 2014 at 9:43 PM, Mo Morsi wrote: > > Yes as others have mentioned pu

Re: Re: F20: Puppet depchain pulls in Java

On Fri, Jan 17, 2014 at 6:53 PM, Rahul Sundaram wrote: > Hi > > > On Fri, Jan 17, 2014 at 9:43 PM, Mo Morsi wrote: >> >> Yes as others have mentioned puppet requires ruby(release) which is >> satisfied by both ruby-mri and jruby So should it just require ruby-mri? The divergence from the way up

Re: Software management: Call for RFEs results!

On Mon, Oct 14, 2013 at 6:46 AM, Matthew Miller wrote: > On Sun, Oct 13, 2013 at 10:19:16PM -0700, Michael Stahnke wrote: >> Developers don't do deployments with RPM...at least not inside Fedora. >> Anything sane is actually against Packaging Guidelines. So that >&

Re: Software management: Call for RFEs results!

On Fri, Oct 4, 2013 at 5:34 AM, Jan Zelený wrote: > Hello everyone, > as you might remember I issued a call for RFEs on this list during the spring. > The participation was not bad at all, we have collected so many data that it > took us several months to discuss and process it. > > Now I have som

Re: using rpms for non-root installs

You actually may have an option. It's dirty, and here be dragons. I know this from working on RPM on AIX, so again, it's hacky. I did this on a CentOS 6.3 box for my example, should work on Fedora. You can do something like: ls zip-3.0-1.el6.x86_64.rpm mkdir $HOME/.myrpm cp -pr /var/lib/rpm

Re: What would it take to make Software Collections work in Fedora?

So the point of view on SC matters. If you live the EL/EPEL world and have some Fedora, SC make a lot of sense. If you only use Fedora, Fedora moves fast enough to likely not have a ton of use for them. I think that's been hit. As for Puppet, I've proposed several ideas on how to improve Puppet

Re: Fixing Puppet in Fedora/EPEL

On Tue, Oct 23, 2012 at 2:50 PM, Jan-Frode Myklebust wrote: > On Sat, Oct 20, 2012 at 1:04 AM, Michael Stahnke > wrote: >> Puppet in the Fedora/EPEL ecosystem is a bit wonky currently. >> >> I'd really like to fix it. >> >> Problems: >> * Fedora 1

Re: Fixing Puppet in Fedora/EPEL

I am still not in favor of a puppet3 package. This is largely due to overall compatibility. Puppet is a distributed system. Having the package be called puppet in some repositories and puppet3 in others (along with bin files/utils) will only the make the overall user-experience of Puppet worse IM

Re: Fixing Puppet in Fedora/EPEL

On Mon, Oct 22, 2012 at 7:51 PM, Todd Zullinger wrote: > Ken Dreyer wrote: >> >> On Fri, Oct 19, 2012 at 5:35 PM, Matthew Miller >> wrote: >>> >>> I'm not opposed to putting puppet 3 in, but it'd really be helpful if it >>> went in as "puppet3" or something, and left the stable version as is, >>>

Re: Fixing Puppet in Fedora/EPEL

On Mon, Oct 22, 2012 at 5:31 AM, wrote: >> From: Seth Vidal >> >> On Fri, 19 Oct 2012, Michael Stahnke wrote: >> >> > On Fri, Oct 19, 2012 at 4:22 PM, Seth Vidal >> >> >> >> >> >> >> >> On Fri, 19 Oct 2012, Michael

Re: Fixing Puppet in Fedora/EPEL

On Fri, Oct 19, 2012 at 5:02 PM, Seth Vidal wrote: > > > > On Fri, 19 Oct 2012, Ken Dreyer wrote: > >> On Fri, Oct 19, 2012 at 5:04 PM, Michael Stahnke >> wrote: >>> >>> My proposal would be the following: >>> * Move EPEL 6, Fedora >= 17

Re: Fixing Puppet in Fedora/EPEL

On Fri, Oct 19, 2012 at 4:22 PM, Seth Vidal wrote: > > > > On Fri, 19 Oct 2012, Michael Stahnke wrote: > >> I (we) completely realize this isn't totally awesome either. This is >> a problem when you have a distributed application that is trying to >&

Re: Fixing Puppet in Fedora/EPEL

On Fri, Oct 19, 2012 at 4:05 PM, Seth Vidal wrote: > > > > On Fri, 19 Oct 2012, Michael Stahnke wrote: > >> Puppet in the Fedora/EPEL ecosystem is a bit wonky currently. >> >> I'd really like to fix it. >> >> Problems: >> * Fedora 17 (and h

Fixing Puppet in Fedora/EPEL

tes#Important-Deprecations Michael Stahnke stahnma on freenode Puppet Labs Software Delivery -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Packages with inactive owners orphaned and inactive comaintainers removed

I grabbed ruby-shadow, as it's needed for Puppet. I would love co-maintainers. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

Orphaning some packages

Due to my job changing and me using some of these packages less and less, I will orphaning several packages. jabberpy -- (Fedora + EPEL) jss - (EPEL) perl-Business-CreditCard (Fedora + EPEL) perl-Frontier-RPC (EPEL) php-magpierss (Fedora + EPEL) php-spyc (Fedora + EPEL) python-pygooglechart (Fedor

Re: New Bugzilla URL to create Fedora Review Requests coming

I believe this has it as well. http://fedoraproject.org/wiki/Extras/NewPackageProcess -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

Orphaning packages

I am no longer using several packages that I have maintained and will be orphaning them. Some need love, others I just don't use anymore. kflickr php-pear-Phlickr pastebin x2vnc Most have very limited upstream movement, but again, I don't use them anymore. stahnma -- devel mailing list devel@