Summary: | x11-misc/obmenu-generator-0.85 missing gdbm flag dependency on dev-lang/perl | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | CaptainBlood <luc_pierard_de_maujouy> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | Keywords: | PATCH |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | patch |
Description
CaptainBlood
2019-12-06 21:16:44 UTC
Created attachment 598658 [details, diff]
patch
*** This bug has been marked as a duplicate of bug 702166 *** Just as a note of order, I think it's absolutely not alright to file a vague bug report that nobody else but you understands, and then not respond for hours. Even worse is when you then file another bug report with the exact same message but more specific and then you don't even respond to the clarification requests in the previous bug report. Try and be specific the first time next time. Please assume you are a human talking to other humans. I totally agree. But please let me summarize what happened here: No punt intended there, as we're all committed to strengthen beloved Gentoo. I didn't keep track of the ID of the first report. I wasn't online from 2019-12-06 14:20 UTC, before the request for details and 2019-12-06 21:16 UTC, creation of the second report. At that second timestamp, I couldn't retrieve the initial report that I by myself knew to needed additional information for consistency sake: i.e. it didn't appear in the bug list, and advanced search didn't help, maybe by lack of know-how. May be there is a way to retrieve all bugs report I created whatever status they're in. I couldn't find out. Surely keeping track of the bug ID, as I sometime do would have help avoid this situation. And a final word wondering if things would have escalated the same way should the initial bug been created about 9 hrs earlier, a likely situation as I'm currently located in the Indian Ocean area. *** Bug 702166 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 702166 *** Please stop reopening this bug report. |