Description of problem: issue 'yum changelog openssl' with increasing date/time resolution. According to the man page, a resolution of one month e.g. 2013-12 should work, and does. I can go further, and specify a date e.g. 2013-12-20. If I go further, things get stange. If I specify an hour e.g. 2013-12-20-04, the hour is ignored. At least the output contains 'Listing changelogs since 2013-12-20'. The first time I tried specifying a minute, yum crashed. Attempted to duplicate with 'yum changelog 2013-Dec-20-0-01 openssl', and got identical traceback: Output of 'rpm -qa | grep 'yum-' PackageKit-yum-0.8.9-6.fc19.x86_64 anaconda-yum-plugins-1.0-9.fc19.noarch yum-metadata-parser-1.1.4-8.fc19.x86_64 PackageKit-yum-plugin-0.8.9-6.fc19.x86_64 yum-3.4.3-132.fc19.noarch yum-langpacks-0.4.1-3.fc19.noarch yum-utils-1.1.31-18.fc19.noarch yum-plugin-changelog-1.1.31-18.fc19.noarch Version-Release number of selected component: yum-3.4.3-132.fc19 Additional info: reporter: libreport-2.1.12 cmdline: /usr/bin/python /usr/bin/yum changelog 2013-Dec-20-04-00-01 openssl dso_list: yum-plugin-changelog-1.1.31-18.fc19.noarch executable: /usr/bin/yum kernel: 3.13.6-100.fc19.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: changelog.py:215:doCommand:TypeError: can't compare offset-naive and offset-aware datetimes Traceback (most recent call last): File "/usr/bin/yum", line 29, in <module> yummain.user_main(sys.argv[1:], exit_code=True) File "/usr/share/yum-cli/yummain.py", line 355, in user_main errcode = main(args) File "/usr/share/yum-cli/yummain.py", line 174, in main result, resultmsgs = base.doCommands() File "/usr/share/yum-cli/cli.py", line 570, in doCommands return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds) File "/usr/lib/yum-plugins/changelog.py", line 215, in doCommand if self._since_dto == dateutil_parser.parse('garbage', fuzzy=True): TypeError: can't compare offset-naive and offset-aware datetimes Local variables in innermost frame: tt: time.struct_time(tm_year=2013, tm_mon=12, tm_mday=20, tm_hour=4, tm_min=0, tm_sec=0, tm_wday=4, tm_yday=354, tm_isdst=0) since: '2013-Dec-20-04-00-01' extcmds: ['openssl'] base: <cli.YumBaseCli object at 0x1247ad0> msg_warn: <function msg_warn at 0x1437320> msg: <function msg at 0x14377d0> logger: <logging.Logger object at 0x1247a90> self: <changelog.ChangeLogCommand instance at 0x125a830> basecmd: 'changelog'
Created attachment 876528 [details] File: backtrace
Created attachment 876529 [details] File: environ
OK to close. Problem no longer exists in the current yum-plugin-changelog-1.1.31-18.fc19.noarch. I was talking to a wall. Never a word back over a period of months, problem somehow goes away, and there was never any indication that this bug report was in any way helpful, or even *seen*. I wonder if this update will be any different. Either way, it tells me something useful. I've found some other bugs in yum, some of which exist downstream. As other reporting channels (which seem more likely to get a response) exist, why would I bother with this one in future? You are tilting people toward the No More Free Bugs movement.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.