On 16/08/16 06:24, Tom Callaway wrote:
> I'd like to propose that we enable the Developer Toolset repo in EPEL
> and allow packages to depend on it. Thoughts?
There is one issue with this that I don't think others have addressed
yet on this list. EPEL 6 supports i686 as a build target, but
On Fri, Aug 26, 2016 at 6:24 PM, dani wrote:
>
> I think it is high time to rethink the single version of a package policy,
> and come up with some scheme that would allow for any package to maintain
> multiple versions in a consistent manner.
We wouldn't even be the first
On 08/26/2016 12:26 PM, Sérgio Basto wrote:
> On Sex, 2016-07-01 at 13:04 -0400, Honza Šilhan wrote:
>> Hi,
>>
>> DNF is in EPEL for more than one year, unfortunately there was still
>> the old
>> DNF-0.6.4
>> version. Over that time in DNF were implemented a lot of great
>> features and
>> plenty
On Sex, 2016-07-01 at 13:04 -0400, Honza Šilhan wrote:
> Hi,
>
> DNF is in EPEL for more than one year, unfortunately there was still
> the old
> DNF-0.6.4
> version. Over that time in DNF were implemented a lot of great
> features and
> plenty of bugs
> have been fixed. DNF (especially its
On 26 August 2016 at 12:58, Stephen John Smoogen wrote:
> On 26 August 2016 at 06:00, Daniel Letai wrote:
>>
>>
>> On 08/25/2016 11:40 PM, Kevin Fenzi wrote:
>>
>> Perhaps you could explain exactly what you want to propose here again?
>> Just epel6? or 7 as
On 08/25/2016 07:35 PM, Stephen John Smoogen wrote:
> So the RHEL7.3 beta is now available for testing. Doing a simplified
> check of what packages I could find in centos-7.2 and beta 7.3 it
> looks like there are 220+ packages with version updates and maybe 60
> added packages.
>
>
On 08/25/2016 07:35 PM, Stephen John Smoogen wrote:
> So the RHEL7.3 beta is now available for testing. Doing a simplified
> check of what packages I could find in centos-7.2 and beta 7.3 it
> looks like there are 220+ packages with version updates and maybe 60
> added packages.
>
>
On Thu, 25 Aug 2016 15:04:58 -0600
Dave Johansen wrote:
> On Thu, Aug 25, 2016 at 2:34 PM, Kevin Fenzi wrote:
>
> > On Wed, 24 Aug 2016 21:59:55 -0600
> > Dave Johansen wrote:
> >
> > > I agree that how to handle SCLs can get
On Fri, 26 Aug 2016 07:24:33 +0200
Timotheus Pokorra wrote:
> Hello,
>
> Just to give a heads up: I am now working on this upgrade to Mono 4.2.
> I will build the mono package and the depending packages in a
> BuildRoot Override, and submit them for testing.
The following Fedora EPEL 6 Security updates need testing:
Age URL
414 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031
python-virtualenv-12.0.7-1.el6
408 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168
rubygem-crack-0.3.2-2.el6
340
On 08/25/2016 11:40 PM, Kevin Fenzi wrote:
Perhaps you could explain exactly what you want to propose here again?
Just epel6? or 7 as well? Do you have co-maintainers in case you get
busy, etc?
I propose adding several gnu packages (namely gcc, binutils and gdb)
with versions following those
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If
13 matches
Mail list logo