Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 702194 - x11-misc/obmenu-generator-0.85 missing gdbm flag dependency on dev-lang/perl
Summary: x11-misc/obmenu-generator-0.85 missing gdbm flag dependency on dev-lang/perl
Status: RESOLVED DUPLICATE of bug 702166
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2019-12-06 21:16 UTC by CaptainBlood
Modified: 2019-12-07 14:37 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
patch (obmenu-generator-0.85-gdbm.ebuild.patch,390 bytes, patch)
2019-12-06 21:48 UTC, CaptainBlood
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description CaptainBlood 2019-12-06 21:16:44 UTC
eix dev-lang/perl
[I] dev-lang/perl
Installed versions:  5.30.1(0/5.30)(00:05:41 07/12/2019)(-berkdb -debug -doc -gdbm -ithreads)
--------------------------------------------------------------------------------
obmenu-generator -s -i
Can't locate GDBM_File.pm in @INC (you may need to install the GDBM_File module) (@INC contains: /etc/perl /usr/local/lib64/perl5/5.30.1/x86_64-linux /usr/local/lib64/perl5/5.30.1 /usr/lib64/perl5/vendor_perl/5.30.1/x86_64-linux /usr/lib64/perl5/vendor_perl/5.30.1 /usr/lib64/perl5/5.30.1/x86_64-linux /usr/lib64/perl5/5.30.1) at /usr/bin/obmenu-generator line 441.
-------------------------------------------------------------------------------
eix dev-lang/perl
[I] dev-lang/perl
Installed versions:  5.30.1(0/5.30)(22:43:40 06/12/2019)(gdbm -berkdb -debug -doc -ithreads)
--------------------------------------------------------------------------------
obmenu-generator -s -i
[*] A static menu has been successfully generated!

Reproducible: Always
Comment 1 CaptainBlood 2019-12-06 21:48:39 UTC
Created attachment 598658 [details, diff]
patch
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2019-12-06 22:31:43 UTC

*** This bug has been marked as a duplicate of bug 702166 ***
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2019-12-06 22:47:17 UTC
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.
Comment 4 CaptainBlood 2019-12-07 14:10:36 UTC
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.
Comment 5 CaptainBlood 2019-12-07 14:12:23 UTC
*** Bug 702166 has been marked as a duplicate of this bug. ***
Comment 6 Jeroen Roovers (RETIRED) gentoo-dev 2019-12-07 14:36:33 UTC

*** This bug has been marked as a duplicate of bug 702166 ***
Comment 7 Jeroen Roovers (RETIRED) gentoo-dev 2019-12-07 14:37:43 UTC
Please stop reopening this bug report.