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
-Deprecations
Michael Stahnke
stahnma on freenode
Puppet Labs Software Delivery
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Fri, Oct 19, 2012 at 4:05 PM, Seth Vidal skvi...@fedoraproject.org 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 higher) ships with Ruby 1.9.x and Puppet 2.7.x
On Fri, Oct 19, 2012 at 4:22 PM, Seth Vidal skvi...@fedoraproject.org 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
support the widest variety
On Fri, Oct 19, 2012 at 5:02 PM, Seth Vidal skvi...@fedoraproject.org wrote:
On Fri, 19 Oct 2012, Ken Dreyer wrote:
On Fri, Oct 19, 2012 at 5:04 PM, Michael Stahnke stah...@puppetlabs.com
wrote:
My proposal would be the following:
* Move EPEL 6, Fedora = 17 to use Puppet 3.0.
* Move
On Mon, Oct 22, 2012 at 5:31 AM, john.flor...@dart.biz wrote:
From: Seth Vidal skvi...@fedoraproject.org
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 Stahnke wrote:
I (we) completely realize this isn't
On Mon, Oct 22, 2012 at 7:51 PM, Todd Zullinger t...@pobox.com wrote:
Ken Dreyer wrote:
On Fri, Oct 19, 2012 at 5:35 PM, Matthew Miller mat...@fedoraproject.org
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
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
On Tue, Oct 23, 2012 at 2:50 PM, Jan-Frode Myklebust janfr...@tanso.net wrote:
On Sat, Oct 20, 2012 at 1:04 AM, Michael Stahnke stah...@puppetlabs.com
wrote:
Puppet in the Fedora/EPEL ecosystem is a bit wonky currently.
I'd really like to fix it.
Problems:
* Fedora 17 (and higher) ships
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
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
On Fri, Oct 4, 2013 at 5:34 AM, Jan Zelený jzel...@redhat.com 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.
On Mon, Oct 14, 2013 at 6:46 AM, Matthew Miller
mat...@fedoraproject.org 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
becomes
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
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
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
On Fri, Jan 17, 2014 at 6:53 PM, Rahul Sundaram methe...@gmail.com 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
On Sat, Jan 18, 2014 at 5:55 AM, Mo Morsi mmo...@redhat.com wrote:
On 01/18/2014 01:40 AM, Michael Stahnke wrote:
On Fri, Jan 17, 2014 at 6:53 PM, Rahul Sundaram methe...@gmail.com
methe...@gmail.com wrote:
Hi
On Fri, Jan 17, 2014 at 9:43 PM, Mo Morsi wrote:
Yes as others have
On Mon, Jan 27, 2014 at 5:12 PM, Miroslav Suchy msu...@redhat.com 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
/show_bug.cgi?id=909088
https://bugzilla.redhat.com/show_bug.cgi?id=814725
https://bugzilla.redhat.com/show_bug.cgi?id=771152
https://bugzilla.redhat.com/show_bug.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
+Ruby-sig
bcc fedora-devel
snip
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
snip
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
On Thu, Jun 4, 2015 at 2:21 PM, Haïkel hgue...@fedoraproject.org wrote:
2015-06-04 20:21 GMT+02:00 John Florian john.flor...@dart.biz:
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
On Fri, Jun 5, 2015 at 6:31 AM, John Florian john.flor...@dart.biz 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 john.flor...@dart.biz
wrote:
I’ve been curious how Fedora plans to tackle inclusion of Puppet 4, but
haven’t
On Fri, Jun 5, 2015 at 8:15 AM, Michael Stahnke stah...@puppetlabs.com
wrote:
On Fri, Jun 5, 2015 at 6:31 AM, John Florian john.flor...@dart.biz
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 john.flor...@dart.biz
wrote
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:
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
On Wed, Aug 7, 2013 at 4:22 PM, Jeff Sheltren j...@tag1consulting.com wrote:
On Wed, Aug 7, 2013 at 9:43 AM, Kevin Fenzi ke...@scrye.com wrote:
So, could you remind us again of the various interactions of the
versions? (or is there a doc on it?)
Ie, of 2.6, 2.7, 3.0, which versions clients
I'm curious as to why. Feel to reply off list if you think this is too
off-topic.
On Wed, Nov 6, 2013 at 7:54 AM, Peter Lemenkov lemen...@gmail.com wrote:
Hello All!
I'm going to stop further maintaining all EL branches of the following
packages:
*
What's the process opt-in at this point? I'm a bit unclear. I see that
epel-release was built for EPEL7 (and that the git branch is epel7
instead of el7).
On Wed, Dec 25, 2013 at 3:03 AM, Karel Volný kvo...@redhat.com wrote:
Hi,
Dne pátek, 13. prosince 2013 17:42:24 CEST, Kevin Fenzi
snip lots of stuff
Smooge thanks for the write-up.
Great points are being brought up by all parties here.
I think I'm +1 on a second repo that moves faster and can be incompatible
with the right type of announce-list. (maybe even put the uri for that list
in the .repo file or something). It
On Sun, Aug 17, 2014 at 12:15 PM, Kevin Fenzi ke...@scrye.com wrote:
On Sun, 17 Aug 2014 18:52:53 +0200
Till Maas opensou...@till.name wrote:
On Thu, Aug 14, 2014 at 05:51:04PM -0600, Stephen John Smoogen wrote:
I am proposing that the EPEL community hold a meeting in #epel on
Friday
On Fri, Aug 29, 2014 at 11:48 AM, Stephen John Smoogen smo...@gmail.com
wrote:
At last week's EPEL meeting, it was proposed that at least a short term
governing committee be put together to help on the following items:
1) EPEL.next (EPIC or EPEL-rolling, etc)
2) Formalizing various amounts
After a very long period of neglect, (sorry), I worked on updating the
rails stack in EPEL5 to 2.3.18. This includes activesupport, activerecord
and actionpack thus far. Rails still to come.
Moving from 2.1.x to 2.3.x *should* be a clean upgrade, but I know in some
cases it's not, as some
34 matches
Mail list logo
