Summary: | [NEW PORT] finance/bitcoin-armory | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Yuri Victorovich <yuri> | ||||||||||||
Component: | Individual Port(s) | Assignee: | Thomas Zander <riggs> | ||||||||||||
Status: | Closed FIXED | ||||||||||||||
Severity: | Affects Only Me | CC: | riggs | ||||||||||||
Priority: | --- | ||||||||||||||
Version: | Latest | ||||||||||||||
Hardware: | Any | ||||||||||||||
OS: | Any | ||||||||||||||
Attachments: |
|
Description
Yuri Victorovich
![]() ![]() Created attachment 145325 [details]
patch
Thanks! Do you have any verification available? In order of preference, examples of what I'm looking for are: 1) "poudriere testport" or "poudriere bulk -t" logs 2) Redports or tinderbox logs 3) "make check-plist" followed by "make stage-qa" output I am running "poudriere testport". However, poudriere html logs feature seems to be broken (https://github.com/bdrewery/poudriere/issues/12). So which log file(s) should I attach then? if it's a local installation of poudriere, just go to the data directory, logs, and you'll find the log. Either latest, latest-per-pkg, etc. It's on your drive, you don't need a web browser to find it. also, I don't think that error prevents you from right-click save the log from the web interface either. Created attachment 145381 [details]
updated patch
Created attachment 145384 [details]
poudriere build log
I have attached the updated patch and the build log. Package builds without any problems. okay, but next time don't compress the log, otherwise I can't see it in the browser. yuri: thanks For the committer that picks this up, it's patch ready: ====> Running Q/A tests (stage-qa) ====> Checking for pkg-plist issues (check-plist) ===> Parsing plist ===> Checking for items in STAGEDIR missing from pkg-plist ===> Checking for directories owned by MTREEs ===> Checking for directories handled by dependencies ===> Checking for items in pkg-plist which are not in STAGEDIR ===> No pkg-plist issues found (check-plist) ====>> Checking for staging violations... done Created attachment 145413 [details]
updated patch: added ONLY_FOR_ARCHS
Created attachment 146185 [details]
Corrected the submitter full name only
A commit references this bug: Author: riggs Date: Sat Aug 23 20:17:19 UTC 2014 New revision: 365805 URL: http://svnweb.freebsd.org/changeset/ports/365805 Log: - Import bitcoin-armory into finance, an implementation of desktop bitcoin management system - Assign maintainership to port submitter Yuri Victorovich <yuri@rawbw.com> PR: 192367 Submitted by: Yuri Victorovich <yuri@rawbw.com> Approved by: mentors (implicit) Changes: head/finance/Makefile head/finance/bitcoin-armory/ head/finance/bitcoin-armory/Makefile head/finance/bitcoin-armory/distinfo head/finance/bitcoin-armory/files/ head/finance/bitcoin-armory/files/patch-ArmoryQt.py head/finance/bitcoin-armory/files/patch-ArmoryUtils.py head/finance/bitcoin-armory/files/patch-Makefile head/finance/bitcoin-armory/files/patch-announcefetch.py head/finance/bitcoin-armory/files/patch-cppForSwig-Makefile head/finance/bitcoin-armory/files/patch-cppForSwig-cryptopp-Makefile head/finance/bitcoin-armory/files/patch-dpkgfiles-armory head/finance/bitcoin-armory/pkg-descr head/finance/bitcoin-armory/pkg-message head/finance/bitcoin-armory/pkg-plist Committed with minor polishing. Thanks! |