On 04/10/2015 08:40 AM, Jan Zelený
wrote:
Mr. Zeleny,On 10. 4. 2015 at 07:16:30, Steve Clark wrote:On 04/10/2015 07:04 AM, Jan Zelený wrote:On 10. 4. 2015 at 09:34:15, Reindl Harald wrote:Am 10.04.2015 um 09:18 schrieb Jan Zelený:On 10. 4. 2015 at 08:53:46, Petr Spacek wrote:I very much agree with this. As a user, I expect that 'dnf upgrade' will give me latest packages and that DNF will tell me the fact that newer packages are available but not installable. Maybe it could have a form of plugin, at least for the beginning?Again, dnf check-update already does thatAgain: that argument is pointless because *nobody* is calling it by hand after "dnf upgrade" and so that information is *not* available for the regular dnf/yum userThe vision for dnf is to be more simple and more effective tool for admins that will not try to solve problems of other components. On the other hand we want to enable package maintainers and other advanced users to achieve their use cases somehow but dnf will never be a debugging tool. Bottom line, we will consider this feature request but considering it is the only promise I can give you. Thanks JanMr. Zeleny, As an admin and user how does this behavior make it simpler for me? I now have to do 2 steps to make sure things worked as expected. How is this simpler?What we envision is for the admin not to debug the problem himself, it's not his responsibility. Packaging problems should be discovered automatically when an update is created. This is being worked on by Fedora QA IIUIC. Package maintainers are the second line of defense, as they should resolve these problems before updates go stable. But these issues should never get to the end user. Bottom line, if an update is in a repo but it's not installable, it's technically not available to the client as some of the bits are obviously missing. Maybe you could help me understand what value does the information have for you when you can't install the packages anyway. Thanks Jan It is naive, in my opinion, to assume that Fedora is going to supply all the packages one might need. I quite frequently run into the problem of dependencies from other repos clashing with Fedora's, and others and have to use the information provided by yum to determine how to clean things up. In what is proposed now I will have to do two steps to determine there is a problem. Regards, --
Stephen Clark NetWolves Managed Services, LLC. Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark@xxxxxxxxxxxxx http://www.netwolves.com |
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct