Joe Zeff wrote:
On 12/02/2017 11:58 AM, Richard Hughes wrote:
> Not DONTCARE, more "really busy with other stuff". If somebody else
> figures out a good way to invalidate the cache (probably done in
> libdnf), I'm happy to review patches and build packages. It can't
> *all* be on my shoulders, right? Richard
That's good to know. However, over the years I've had bug reports
that were never followed up or assigned, with the only comment after
the original report being an announcement that it was being closed
at EOL for that version. AFAICT, nobody even looked at them, and
the closing was simply an autobot.
While I'm sure some bugs are not viewed by any maintainers, I'd wager
that's far fewer than thoss which are viewed and the maintainer simply
lacks enough time to do anything with it. There's no way to see if a
bug was viewed, so as a reporter we can only guess. It would be ideal
if all bug reports led to fixes, but that's not likely.
With this particular PackageKit issue, I think that it might be
lingering for longer because the users most affected are less likely
to be folks that would dig into the problem and submit patches to the
appropriate component (as Richard said, the place for a fix might be
in libdnf). I know personally, I don't make use of PackageKit and
Gnome Software, so I "solve" this for myself by removing those
packages rather than trying to fix it.
It does seem like as long as it's been around that someone who cared
might have submitted a patch. I've long told people on projects I
contribute to that complaints/bug reports/suggestions in unified diff
format are the best. ;)
--
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Whenever you find yourself on the side of the majority, it is time to
pause and reflect.
-- Mark Twain