Hi,
I wanted to remove all LibreOffice components so I tried the following command:
sudo dnf remove -y @libreoffice
This resulted in:
No packages marked for removal. Dependencies resolved. ============================================================================================================================================================================ Package Architecture Version Repository Size ============================================================================================================================================================================ Removing Groups: LibreOffice
Transaction Summary ============================================================================================================================================================================
Complete!
This was strange since the group had no packages in it.
Why is that ?
Just to confirm I installed the LibreOffice group once again via:
sudo dnf install -y @libreoffice
And that resulted in:
Dependencies resolved. ============================================================================================================================================================================ Package Architecture Version Repository Size ============================================================================================================================================================================ Installing Groups: LibreOffice
Transaction Summary ============================================================================================================================================================================
Complete!
Why is there a blank group of LibreOffice ?
Why aren't the required packages in it ?
On 21/11/2020 04:54, Sreyan Chakravarty wrote:
Why is there a blank group of LibreOffice ?
Why aren't the required packages in it ?
On my F33 system I get....
[egreshko@meimei ~]$ dnf group info @libreoffice Last metadata expiration check: 0:02:28 ago on Sat Nov 21 07:28:22 2020. Warning: Group @libreoffice does not exist.
but
[egreshko@meimei ~]$ dnf group info LibreOffice Last metadata expiration check: 0:01:08 ago on Sat Nov 21 07:28:22 2020.
Group: LibreOffice Description: LibreOffice Productivity Suite Mandatory Packages: libreoffice-calc libreoffice-emailmerge libreoffice-graphicfilter libreoffice-impress libreoffice-writer Optional Packages: libreoffice-base libreoffice-draw libreoffice-math libreoffice-pyuno
--- The key to getting good answers is to ask good questions.
On Sat, Nov 21, 2020 at 5:02 AM Ed Greshko ed.greshko@greshko.com wrote:
[egreshko@meimei ~]$ dnf group info @libreoffice Last metadata expiration check: 0:02:28 ago on Sat Nov 21 07:28:22 2020. Warning: Group @libreoffice does not exist.
but
[egreshko@meimei ~]$ dnf group info LibreOffice Last metadata expiration check: 0:01:08 ago on Sat Nov 21 07:28:22 2020.
Group: LibreOffice Description: LibreOffice Productivity Suite Mandatory Packages: libreoffice-calc libreoffice-emailmerge libreoffice-graphicfilter libreoffice-impress libreoffice-writer Optional Packages: libreoffice-base libreoffice-draw libreoffice-math libreoffice-pyuno
Ok can you tell me how DNF actually works ?
I mean what is the difference between @libreoffice and LibreOffice ?
dnf group info LibreOffice
Does this mean that LibreOffice is installed ? If so isn't there a single command to remove the group ?
How is
dnf group info LibreOffice
different from
dnf group info @libreoffice
What is going on here ?
On 21/11/2020 08:08, Sreyan Chakravarty wrote:
On Sat, Nov 21, 2020 at 5:02 AM Ed Greshko <ed.greshko@greshko.com mailto:ed.greshko@greshko.com> wrote:
[egreshko@meimei ~]$ dnf group info @libreoffice Last metadata expiration check: 0:02:28 ago on Sat Nov 21 07:28:22 2020. Warning: Group @libreoffice does not exist. but [egreshko@meimei ~]$ dnf group info LibreOffice Last metadata expiration check: 0:01:08 ago on Sat Nov 21 07:28:22 2020. Group: LibreOffice Description: LibreOffice Productivity Suite Mandatory Packages: libreoffice-calc libreoffice-emailmerge libreoffice-graphicfilter libreoffice-impress libreoffice-writer Optional Packages: libreoffice-base libreoffice-draw libreoffice-math libreoffice-pyunoOk can you tell me how DNF actually works ?
I mean what is the difference between @libreoffice and LibreOffice ?
Have you had the chance to read the dnf man page?
Each <spec> can be either a <package-spec>, which specifies a package directly, or a @<group-spec>, which specifies an (environ‐ ment) group which contains it.
You can use....
dnf group list
to get a list of the installed groups
dnf group info LibreOffice
Does this mean that LibreOffice is installed ? If so isn't there a single command to remove the group ?
No, see above.
How is
dnf group info LibreOffice
different from
dnf group info @libreoffice
I actually don't use the @form of group-spec as I forgot (or maybe never knew) how to get a list of the corresponding @forms. I just use the full name in quotes.
--- The key to getting good answers is to ask good questions.
On Sat, Nov 21, 2020 at 6:15 AM Ed Greshko ed.greshko@greshko.com wrote:
Have you had the chance to read the dnf man page?
Each <spec> can be either a <package-spec>, which specifies a package directly, or a @<group-spec>, which specifies an (environ‐ ment) group which contains it.
I did, but it is not clear (at least to me) about where to use the @ symbol and where not to. Which was kind of my point/question.
Any ways this does not still explain why the entire LibreOffice group is blank, and why I can't remove LibreOffice cleanly in one go via the group that it is supposed to be a part of.
You can use....
dnf group list
to get a list of the installed groups
The LibreOffice group does exist for me, but alas, it is empty.
I actually don't use the @form of group-spec as I forgot (or maybe never
knew) how to get a list of the corresponding @forms. I just use the full name in quotes.
I think this is the more unambiguous approach to take.
On 21/11/2020 09:37, Sreyan Chakravarty wrote:
On Sat, Nov 21, 2020 at 6:15 AM Ed Greshko <ed.greshko@greshko.com mailto:ed.greshko@greshko.com> wrote:
Have you had the chance to read the dnf man page? Each <spec> can be either a <package-spec>, which specifies a package directly, or a @<group-spec>, which specifies an (environ‐ ment) group which contains it.I did, but it is not clear (at least to me) about where to use the @ symbol and where not to. Which was kind of my point/question.
Samuel did answer that. It is the way to distinguish between a group name and package name.
You can see this by the difference in using
sudo dnf autoremove libreoffice
and
sudo dnf autoremove @libreoffice
Any ways this does not still explain why the entire LibreOffice group is blank, and why I can't remove LibreOffice cleanly in one go via the group that it is supposed to be a part of.
You can use.... dnf group list to get a list of the installed groupsThe LibreOffice group does exist for me, but alas, it is empty.
So.....
dnf group info LibreOffice
returns nothing?
--- The key to getting good answers is to ask good questions.
On 11/20/20 3:31 PM, Ed Greshko wrote:
On 21/11/2020 04:54, Sreyan Chakravarty wrote:
Why is there a blank group of LibreOffice ?
Why aren't the required packages in it ?
On my F33 system I get....
[egreshko@meimei ~]$ dnf group info @libreoffice Last metadata expiration check: 0:02:28 ago on Sat Nov 21 07:28:22 2020. Warning: Group @libreoffice does not exist.
When you're doing group commands, you don't use the "@". That's only for package management commands to distinguish it from a package name.
"LibreOffice" and "libreoffice" are equivalent. The latter is the short form which makes more sense with other groups, particularly ones with spaces.
Educational Software (education) Electronic Lab (electronic-lab) Engineering and Scientific (engineering-and-scientific) FreeIPA Server (freeipa-server) Headless Management (headless-management) MATE Applications (mate-applications) Milkymist (milkymist) Network Servers (network-server) Neuron Modelling Simulators (neuron-modelling-simulators)
On 21/11/2020 09:06, Samuel Sieb wrote:
On 11/20/20 3:31 PM, Ed Greshko wrote:
On 21/11/2020 04:54, Sreyan Chakravarty wrote:
Why is there a blank group of LibreOffice ?
Why aren't the required packages in it ?
On my F33 system I get....
[egreshko@meimei ~]$ dnf group info @libreoffice Last metadata expiration check: 0:02:28 ago on Sat Nov 21 07:28:22 2020. Warning: Group @libreoffice does not exist.
When you're doing group commands, you don't use the "@". That's only for package management commands to distinguish it from a package name.
"LibreOffice" and "libreoffice" are equivalent. The latter is the short form which makes more sense with other groups, particularly ones with spaces.
OK. I'll admit that I've not spent much time on the "@" form and when/how it is used. At least I did learn that using "dnf -v group list" provides both the long and non-space forms of group names. And using --hidden reveals additional defined groups.
--- The key to getting good answers is to ask good questions.
On 21/11/20 12:30 pm, Ed Greshko wrote:
On 21/11/2020 09:06, Samuel Sieb wrote:
On 11/20/20 3:31 PM, Ed Greshko wrote:
On 21/11/2020 04:54, Sreyan Chakravarty wrote:
Why is there a blank group of LibreOffice ?
Why aren't the required packages in it ?
On my F33 system I get....
[egreshko@meimei ~]$ dnf group info @libreoffice Last metadata expiration check: 0:02:28 ago on Sat Nov 21 07:28:22 2020. Warning: Group @libreoffice does not exist.
When you're doing group commands, you don't use the "@". That's only for package management commands to distinguish it from a package name.
"LibreOffice" and "libreoffice" are equivalent. The latter is the short form which makes more sense with other groups, particularly ones with spaces.
OK. I'll admit that I've not spent much time on the "@" form and when/how it is used. At least I did learn that using "dnf -v group list" provides both the long and non-space forms of group names. And using --hidden reveals additional defined groups.
Using dnf group list --ids also shows the long and short form of group names.
regards, Steve
The key to getting good answers is to ask good questions.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On Sat, Nov 21, 2020 at 6:36 AM Samuel Sieb samuel@sieb.net wrote:
When you're doing group commands, you don't use the "@". That's only for package management commands to distinguish it from a package name.
So what you mean to say is that when I am installing a group via dnf install the @ is required but when I am using dnf group install @ is not required since dnf already knows its a group.
Am I correct ?
"LibreOffice" and "libreoffice" are equivalent. The latter is the short form which makes more sense with other groups, particularly ones with spaces.
Yes but this still does not explain why LibreOffice does not have its own DNF Group (except for the one that does not work) .
On 11/20/20 5:40 PM, Sreyan Chakravarty wrote:
On Sat, Nov 21, 2020 at 6:36 AM Samuel Sieb <samuel@sieb.net mailto:samuel@sieb.net> wrote: So what you mean to say is that when I am installing a group via dnf install the @ is required but when I am using dnf group install @ is not required since dnf already knows its a group.
Am I correct ?
Yes.
"LibreOffice" and "libreoffice" are equivalent. The latter is the short form which makes more sense with other groups, particularly ones with spaces.Yes but this still does not explain why LibreOffice does not have its own DNF Group (except for the one that does not work) .
It does work, just not for what you're trying to do.
On 2020-11-20 12:54, Sreyan Chakravarty wrote:
Hi,
I wanted to remove all LibreOffice components so I tried the following command:
sudo dnf remove -y @libreoffice
This resulted in:
No packages marked for removal. Dependencies resolved. ============================================================================================================================================================================ Package Architecture Version Repository Size ============================================================================================================================================================================ Removing Groups: LibreOffice
Transaction Summary
Complete!
This was strange since the group had no packages in it.
Why is that ?
Just to confirm I installed the LibreOffice group once again via:
sudo dnf install -y @libreoffice
And that resulted in:
Dependencies resolved.
Package Architecture Version Repository Size ============================================================================================================================================================================ Installing Groups: LibreOffice
Transaction Summary
Complete!
Why is there a blank group of LibreOffice ?
Why aren't the required packages in it ?
-- Regards, Sreyan Chakravarty
Hi Sreyan,
Libre Office also does not remove prior major releases of itself as does their Windows version. Makes for a mess. You have to manually uninstall the old major release manually.
I reported it to them a while back, but they blew me off. Libre Office is not very good about taking bugs from their users.
I would drop Libre Office, if I could. Soft Maker looks like they are close to getting there. I will migrate to them as soon as they start supporting saving is ODX (spreadsheet) format. They currently support saving in ODT. Soft Maker loads both on ODX and ODT TEN times faster than Libre Office. No fooling!
Soft Maker also has a free version called Free Office, But the paid verions is very reasonable.
This is my keep on how to uninstall Libre Office
-T
RPM Removal of Libre Office:
# rpm --nodeps -e $(rpm -qa | grep -i -E "libobasis|^libreoffice.org|libreoffice|unoconv") # rpm -e $(rpm -qa *libreoffice* | grep -i menu)
Also, go into /opt and remove the stray libreoffice* directories
To remove Libreoffice 5.2 after installing (Upgrading) 5.3: # rpm --nodeps -e $(rpm -qa | grep -i -E "libobasis5.2|libreoffice5.2")
On Sat, Nov 21, 2020 at 5:13 AM ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
I reported it to them a while back, but they blew me off. Libre Office is not very good about taking bugs from their users.
Wow.
I would drop Libre Office, if I could. Soft Maker looks like they are close to getting there. I
Soft Maker also has a free version called Free Office, But the paid verions is very reasonable.
What about OnlyOffice ??
I am thinking of migrating to OnlyOffice.
On 2020-11-20 16:10, Sreyan Chakravarty wrote:
On Sat, Nov 21, 2020 at 5:13 AM ToddAndMargo via users <users@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> wrote:
I reported it to them a while back, but they blew me off. Libre Office is not very good about taking bugs from their users.Wow.
I would drop Libre Office, if I could. Soft Maker looks like they are close to getting there. I Soft Maker also has a free version called Free Office, But the paid verions is very reasonable.What about OnlyOffice ??
Never hear of it. I would love your feedback!
I am thinking of migrating to OnlyOffice.
-- Regards, Sreyan Chakravarty
On 11/20/20 3:42 PM, ToddAndMargo via users wrote:
Libre Office also does not remove prior major releases of itself as does their Windows version. Makes for a mess. You have to manually uninstall the old major release manually.
How is this relevant in the Fedora context? If you are installing LibreOffice with dnf, it will certainly clean up previous versions.
On 2020-11-20 17:00, Samuel Sieb wrote:
On 11/20/20 3:42 PM, ToddAndMargo via users wrote:
Libre Office also does not remove prior major releases of itself as does their Windows version. Makes for a mess. You have to manually uninstall the old major release manually.
How is this relevant in the Fedora context? If you are installing LibreOffice with dnf, it will certainly clean up previous versions.
The dnf version is typically out-of-date, which considering the quality issues and lack of bugs repairs from users, is a good thing. I also have to run the RPM from LibreOffice so I can be current with my Windows customers. And LibreOffice rejects any trouble tickets on RPM versions, not that they are likely to fix anything.
On Nov 20, 2020, at 18:43, ToddAndMargo via users users@lists.fedoraproject.org wrote:
Libre Office also does not remove prior major releases of itself as does their Windows version. Makes for a mess. You have to manually uninstall the old major release manually.
I reported it to them a while back, but they blew me off. Libre Office is not very good about taking bugs from their users.
If you are reporting issues with the Fedora packages to the LibreOffice package maintainers in Fedora, do you have a BZ for the ticket you filed? This absolutely should be tracked as part of Fedora updates. If you filed a bug with upstream LibreOffice about Fedora packaging issues, I am not surprised they ignored you.
RPM Removal of Libre Office:
# rpm --nodeps -e $(rpm -qa | grep -i -E "libobasis|^libreoffice.org|libreoffice|unoconv") # rpm -e $(rpm -qa *libreoffice* | grep -i menu)
Also, go into /opt and remove the stray libreoffice* directories
To remove Libreoffice 5.2 after installing (Upgrading) 5.3: # rpm --nodeps -e $(rpm -qa | grep -i -E "libobasis5.2|libreoffice5.2")
This isn’t advice I would offer anyone. There are very limited circumstances I’d ever suggest using the —nodeps parameter with rpm, and that’s for last ditch RPM database corruption or to fix interrupted transactions, it is never something involved in a regular package update or removal. If you are using Fedora packages, you absolutely should never need this to update r remove LibreOffice.
-- Jonathan Billings billings@negate.org
On 2020-11-22 04:47, Jonathan Billings wrote:
On Nov 20, 2020, at 18:43, ToddAndMargo via users users@lists.fedoraproject.org wrote:
Libre Office also does not remove prior major releases of itself as does their Windows version. Makes for a mess. You have to manually uninstall the old major release manually.
I reported it to them a while back, but they blew me off. Libre Office is not very good about taking bugs from their users.
If you are reporting issues with the Fedora packages to the LibreOffice package maintainers in Fedora, do you have a BZ for the ticket you filed? This absolutely should be tracked as part of Fedora updates. If you filed a bug with upstream LibreOffice about Fedora packaging issues, I am not surprised they ignored you.
RPM Removal of Libre Office:
# rpm --nodeps -e $(rpm -qa | grep -i -E "libobasis|^libreoffice.org|libreoffice|unoconv") # rpm -e $(rpm -qa *libreoffice* | grep -i menu)
Also, go into /opt and remove the stray libreoffice* directories
To remove Libreoffice 5.2 after installing (Upgrading) 5.3: # rpm --nodeps -e $(rpm -qa | grep -i -E "libobasis5.2|libreoffice5.2")
This isn’t advice I would offer anyone. There are very limited circumstances I’d ever suggest using the —nodeps parameter with rpm, and that’s for last ditch RPM database corruption or to fix interrupted transactions, it is never something involved in a regular package update or removal. If you are using Fedora packages, you absolutely should never need this to update r remove LibreOffice.
-- Jonathan Billings billings@negate.org
Hi Jonathan,
I should have been more clear I was talking about upstream's packages, not the fedora repo.
-T
On 11/20/20 12:54 PM, Sreyan Chakravarty wrote:
I wanted to remove all LibreOffice components so I tried the following command:
sudo dnf remove -y @libreoffice
This resulted in:
No packages marked for removal. Dependencies resolved. ============================================================================================================================================================================ Package Architecture Version Repository Size ============================================================================================================================================================================ Removing Groups: LibreOffice
Transaction Summary
Complete!
This was strange since the group had no packages in it.
Why is that ?
Why is there a blank group of LibreOffice ?
It's not blank.
Why aren't the required packages in it ?
From the man page: dnf [options] group remove <group-spec>... Mark the group removed and remove those packages in the group from the system which do not belong to another installed group and were not installed explicitly by the user.
I'm not sure exactly what the reason is, but on my system, removing the group only removes a few fringe packages. I tried adding and removing user and group markings and now it will remove less packages than before. :-)
I've never found group remove to be really useful at all. It's most useful for installing.
On Sat, Nov 21, 2020 at 7:17 AM Samuel Sieb samuel@sieb.net wrote:
It's not blank.
What do you mean it's not blank ?
On my system it removes nothing and adds nothing.
I'm not sure exactly what the reason is, but on my system, removing the
group only removes a few fringe packages. I tried adding and removing user and group markings and now it will remove less packages than before. :-)
I've never found group remove to be really useful at all. It's most useful for installing.
Can I add packages to the LibreOffice group now on my PC ?
On 11/20/20 6:06 PM, Sreyan Chakravarty wrote:
On Sat, Nov 21, 2020 at 7:17 AM Samuel Sieb <samuel@sieb.net mailto:samuel@sieb.net> wrote:
It's not blank.What do you mean it's not blank ?
On my system it removes nothing and adds nothing.
dnf group info libreoffice If the packages are already installed, then it won't add anything. And removing groups doesn't work well.
Can I add packages to the LibreOffice group now on my PC ?
No, there's a file that defines the groups.
-
Ed Greshko -
Jonathan Billings -
Samuel Sieb -
Sreyan Chakravarty -
Stephen Morris -
ToddAndMargo