Summary: | dev-db/tokumx-2.0.2-r2 : GIT-NOTFOUND: error: | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Tony Vroon (RETIRED) <chainsaw> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | ultrabug |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dev-db:tokumx-2.0.1:20160703-201406.log.bz2
emerge-history.txt environment emerge-info.txt dev-db:tokumx-2.0.2:20161124-151341.log.bz2 emerge-history.txt environment |
Description
Toralf Förster
![]() Created attachment 439596 [details]
dev-db:tokumx-2.0.1:20160703-201406.log.bz2
Created attachment 439598 [details]
emerge-history.txt
Created attachment 439600 [details]
environment
Changed upstream practices in 2.0.2 will prevent this from happening again. Removing all old ebuilds from tree. (In reply to Tony Vroon from comment #4) erm, happened today again at : amd64-gnome-unstable_20161122-180956//tmp/issues/20161124-163454 (In reply to Toralf Förster from comment #5) > (In reply to Tony Vroon from comment #4) > erm, happened today again at : > amd64-gnome-unstable_20161122-180956//tmp/issues/20161124-163454 Will there be a build log please? Is it 2.0.1 or 2.0.2? Created attachment 454260 [details]
emerge-info.txt
oh yes, here it is
Created attachment 454262 [details]
dev-db:tokumx-2.0.2:20161124-151341.log.bz2
Created attachment 454264 [details]
emerge-history.txt
Created attachment 454266 [details]
environment
*** Bug 592542 has been marked as a duplicate of this bug. *** The package has been removed on 2020-10-01. |