Bug 1043237 - 'yum group mark convert' far too aggressive
Summary: 'yum group mark convert' far too aggressive
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 20
Hardware: All
OS: All
unspecified
urgent
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: https://fedoraproject.org/wiki/Common...
: 1024872 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-15 09:55 UTC by Adam Williamson
Modified: 2015-06-29 13:31 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 13:31:55 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1031374 0 unspecified CLOSED `yum update` should give reasoning for installing new packages 2021-02-22 00:41:40 UTC

Internal Links: 1031374

Description Adam Williamson 2013-12-15 09:55:32 UTC
This is basically https://bugzilla.redhat.com/show_bug.cgi?id=1024872 , but that report was a bit messy and got closed, so I thought a clean new one would be better.

I've seen several reports of people running 'yum group mark convert' then running 'yum update' and it wanting to install hundreds of new packages, so I thought I'd investigate. A couple of trivial tests indicate that it is, indeed, far too aggressive.

Test #1: do a clean minimal install of Fedora 20, then run 'yum group mark convert'. Result: it decides the groups 'core', 'development-tools', 'dial-up', 'network-server' and 'system-tools' are all installed. 'yum update' wants to install "38 Packages (+205 Dependent packages)". This about doubles the size of the installed package base. As a sanity check, 'yum --setopt group_command=compat upgrade' wants to upgrade 21 packages and not add any at all. A 'minimal' install of Fedora only installs the group @core (plus any packages anaconda decides the target hardware needs to be installed), so it is incorrect for mark convert to consider any other group as installed.

Test #2: do a clean default DVD install of Fedora 20, then run 'yum group mark convert'. Result:

Installed groups:
   Cloud Infrastructure
   Core
   Critical Path (Applications)
   Critical Path (GNOME)
   DNS Name Server
   Design Suite
   Development Tools
   Dial-up Networking Support
   Electronic Lab
   Firefox Web Browser
   Fonts
   Graphical Internet
   Graphics
   Guest Agents
   Guest Desktop Agents
   Hardware Support
   Input Methods
   Java
   Legacy Fonts
   LibreOffice
   Mail Server
   Multimedia
   Network Servers
   Office/Productivity
   Printing Support
   Security Lab
   Server Configuration Tools
   Sound and Video
   Standard
   System Tools
   Text-based Internet

"yum update" wants to add "509 Packages (+866 Dependent packages)", totalling 1.7GB(!)

Conclusion: 'yum group mark convert' is so inaccurate and over-aggressive as to be more harmful than useful. It should be hedged around in warnings, and yumcommands.py certainly shouldn't be printing "Maybe run: yum groups mark convert"" messages.

Comment 1 Adam Williamson 2013-12-15 10:03:13 UTC
*** Bug 1024872 has been marked as a duplicate of this bug. ***

Comment 2 Dario Lesca 2013-12-17 08:20:41 UTC
Fedora 20 (beta). After last yum update (yesterday):

yum-3.4.3-122.fc20.noarch
yum-langpacks-0.4.3-1.fc20.noarch
yum-metadata-parser-1.1.4-9.fc20.x86_64
yum-plugin-fastestmirror-1.1.31-19.fc20.noarch
yum-utils-1.1.31-19.fc20.noarch

now when I run "yum update", I see this warning:
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * fedora: mirror.de.leaseweb.net
 * rpmfusion-free-rawhide: mirror.de.leaseweb.net
 * rpmfusion-nonfree-rawhide: mirror.de.leaseweb.net
 * updates: mirror.de.leaseweb.net
Warning: group korean-support does not exist.
Warning: group punjabi-support does not exist.
Warning: group firefox does not exist.
Warning: group office does not exist.
Warning: group khmer-support does not exist.
Warning: group graphics does not exist.
Warning: group assamese-support does not exist.
Warning: group dogri-support does not exist.
Warning: group dial-up does not exist.
Warning: group bodo-support does not exist.
Warning: group rpm-development-tools does not exist.
Warning: group bengali-support does not exist.
Warning: group gujarati-support does not exist.
Warning: group virtualization does not exist.
Warning: group legacy-software-development does not exist.
Warning: group mail-server does not exist.
Warning: group traditional-chinese-support does not exist.
Warning: group education does not exist.
Warning: group georgian-support does not exist.
Warning: group hebrew-support does not exist.
Warning: group dns-server does not exist.
Warning: group server-cfg does not exist.
Warning: group sanskrit-support does not exist.
Warning: group java does not exist.
Warning: group sound-and-video does not exist.
Warning: group ruby does not exist.
Warning: group multimedia does not exist.
Warning: group arabic-support does not exist.
Warning: group editors does not exist.
Warning: group window-managers does not exist.
Warning: group directory-server does not exist.
Warning: group admin-tools does not exist.
Warning: group system-tools does not exist.
Warning: group tamil-support does not exist.
Warning: group japanese-support does not exist.
Warning: group critical-path-apps does not exist.
Warning: group simplified-chinese-support does not exist.
Warning: group buildsys-build does not exist.
Warning: group hindi-support does not exist.
Warning: group smb-server does not exist.
Warning: group robotics-suite does not exist.
Warning: group legacy-software-support does not exist.
Warning: group oriya-support does not exist.
Warning: group core does not exist.
Warning: group bhutanese-support does not exist.
Warning: group authoring-and-publishing does not exist.
Warning: group input-methods does not exist.
Warning: group cloud-infrastructure does not exist.
Warning: group web-server does not exist.
Warning: group critical-path-lxde does not exist.
Warning: group development-tools does not exist.
Warning: group manipuri-support does not exist.
Warning: group legacy-fonts does not exist.
Warning: group konkani-support does not exist.
Warning: group yiddish-support does not exist.
Warning: group milkymist does not exist.
Warning: group graphical-internet does not exist.
Warning: group burmese-support does not exist.
Warning: group thai-support does not exist.
Warning: group santali-support does not exist.
Warning: group network-server does not exist.
Warning: group c-development does not exist.
Warning: group kashmiri-support does not exist.
Warning: group kannada-support does not exist.
Warning: group malayalam-support does not exist.
Warning: group security-lab does not exist.
Warning: group design-suite does not exist.
Warning: group electronic-lab does not exist.
Warning: group fonts does not exist.
Warning: group hardware-support does not exist.
Warning: group sinhala-support does not exist.
Warning: group online-docs does not exist.
Warning: group telugu-support does not exist.
Warning: group russian-support does not exist.
Warning: group maithili-support does not exist.
Warning: group games does not exist.
Warning: group critical-path-gnome does not exist.
Warning: group text-internet does not exist.
Warning: group ethiopic-support does not exist.
No packages marked for update

My F20 is update from f19 via fedup last week.

I have run this command:

# yum-config-manager --save --setopt=group_command=compat
(from here: https://bugzilla.redhat.com/show_bug.cgi?id=1024872#c5 )

and the warning have vanished

Comment 3 Adam Williamson 2013-12-19 08:12:05 UTC
Dario: the warnings are well-known, see https://fedoraproject.org/wiki/Common_F20_bugs#yum-group-errors .

Comment 4 Tom Georgoulias 2013-12-24 01:00:40 UTC
Saw this on F19 after running the "yum group mark convert" command as suggested by yum.   Upgraded to yum-3.4.3-128.fc19.noarch from updates-testing but the problem peristed.  The suggested workaround 

yum-config-manager --save --setopt=group_command=compat

from the wiki did address the issue.

Wanted to share my experience just in case another data point helps.

Comment 5 Adam Williamson 2013-12-24 01:09:35 UTC
Tom: right, once you've done a 'too aggressive' conversion there's really no way we can magically clean it up on update, unfortunately. The -128 update 'fixes' this bug in the sense that it will do a less aggressive conversion when it's used to run one.

Comment 6 Fedora End Of Life 2015-05-29 09:59:46 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2015-06-29 13:31:55 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.