Oops, I've copied my reply to the EPEL list as requested.
On Mon, Oct 31, 2016 at 1:17 PM, Tom Boutell wrote:
> There is no version 2.8 of Mongo, they renamed that to 3.0 before release of
> 3.0.
>
> Just to provide a sense of the thought process other EPEL7 users might be
> going through here:
There is no version 2.8 of Mongo, they renamed that to 3.0 before release of
3.0.
Just to provide a sense of the thought process other EPEL7 users might be going
through here:
I started researching this when I became aware that 2.6 was nearing upstream
end-of-life (that is now happening today)
Hi,
thanks for answers and suggestion that epel-de...@lists.fp.o would be better -
so I've posted it there
https://lists.fedoraproject.org/archives/list/epel-de...@lists.fedoraproject.org/thread/TQPBQ25T6F323WYOGNOB6XYMEZDCSFEK/
Marek
___
devel mailing
.
> But MongoDB 2.6 is going to EOL (probably this week), so MongoDB in
> EPEL7 will be unsupported.
>
> How to solve this - what EPEL/Fedora guidelines says about upgrades?
> Upgrade EPEL6 to EPEL7? Or keep unsupported version in EPEL7?
I would only look at upgrade paths within t
next major versions are
> released).
>
> But MongoDB 2.6 is going to EOL (probably this week), so MongoDB in
> EPEL7 will be unsupported.
>
> How to solve this - what EPEL/Fedora guidelines says about upgrades?
> Upgrade EPEL6 to EPEL7? Or keep unsupported version in EPEL7?
>
next major versions are
> released).
>
> But MongoDB 2.6 is going to EOL (probably this week), so MongoDB in
> EPEL7 will be unsupported.
>
> How to solve this - what EPEL/Fedora guidelines says about upgrades?
> Upgrade EPEL6 to EPEL7? Or keep unsupported version in EPE
), so MongoDB in
EPEL7 will be unsupported.
How to solve this - what EPEL/Fedora guidelines says about upgrades?
Upgrade EPEL6 to EPEL7? Or keep unsupported version in EPEL7?
Thanks,
Marek
___
devel mailing list -- devel@lists.fedoraproject.org
To
