On 2019-12-06 08:19, Tom Horsley wrote:
> On Fri, 6 Dec 2019 07:57:21 +0800
> Ed Greshko wrote:
>
>> What does
>>
>> dnf module list --enabled
>>
>> show?
> Not a lot, certainly not eclipse:
>
> [root@zooty ~]# dnf module list --enabled
> Last metadata expiration check: 0:49:33 ago on Thu 05 Dec 20
On Fri, 6 Dec 2019 07:57:21 +0800
Ed Greshko wrote:
> What does
>
> dnf module list --enabled
>
> show?
Not a lot, certainly not eclipse:
[root@zooty ~]# dnf module list --enabled
Last metadata expiration check: 0:49:33 ago on Thu 05 Dec 2019 06:28:12 PM EST.
Fedora Modular 31 - x86_64
Name S
On 2019-12-06 07:40, Tom Horsley wrote:
> On Fri, 6 Dec 2019 06:58:30 +0800
> Ed Greshko wrote:
>
>> It sounds as if you have the eclipse:latest module enabled and that packages
>> conflict with those of non-module
>> packages.
> If anything remotely related to eclipse is on this machine,
> then t
On Fri, 6 Dec 2019 06:58:30 +0800
Ed Greshko wrote:
> It sounds as if you have the eclipse:latest module enabled and that packages
> conflict with those of non-module
> packages.
If anything remotely related to eclipse is on this machine,
then they have come up with some way to hide it because I
On 2019-12-05 20:53, Tom Horsley wrote:
> Doing a dnf update this morning and got a bazillion
> lines of complaints about lucene:
>
> Problem 1: package lucene-facet-7.7.0-2.fc31.noarch requires
> mvn(org.apache.lucene:lucene-core) = 7.7.0, but none of the providers can be
> installed
> - cann
Doing a dnf update this morning and got a bazillion
lines of complaints about lucene:
Problem 1: package lucene-facet-7.7.0-2.fc31.noarch requires
mvn(org.apache.lucene:lucene-core) = 7.7.0, but none of the providers can be
installed
- cannot install both lucene-8.1.1-2.module_f31+6793+1c93c3
