Bug 206067 - ports-mgmt/poudriere: failure at check-sanity phase and issue of python version dependency
Summary: ports-mgmt/poudriere: failure at check-sanity phase and issue of python versi...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Bryan Drewery
URL:
Keywords: needs-qa
Depends on:
Blocks: 220706
  Show dependency tree / graph
 
Reported: 2016-01-09 11:16 UTC by Yasuhiro Kimura
Modified: 2018-01-24 19:07 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (bdrewery)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yasuhiro Kimura freebsd_committer freebsd_triage 2016-01-09 11:16:09 UTC 
I proposed following patch to Bug #205789:

https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165035&action=diff

The intention of my patch is to make the port always use python 3
regardless of default python version setting.

On real 10.2-RELEASE environment it just works as is intended. That
is:

* "cd /usr/ports/mail/postfix-policyd-spf-python; make install"
  succeeds without any error.
* Both mail/postfix-policyd-spf-python itself and dependents (such as
  mail/py-authres or mail/py-pyspf) are built and installed as
  python 3 packages (py34-postfix-policyd-spf-python-1.3.2_2,
  py34-authres-0.800, py34-pyspf-2.0.12_3, and etc.).

But on poudriere with 10.2-R jail the result is different as
following:

* "poudriere testport -j 102release -o mail/postfix-policyd-spf-python"
  fails at check-sanity phase. 
* Some dependents (such as mail/py-authres or mail/py-pyspf) are build
  as python 2 packages (py27-authres-0.800, py27-pyspf-2.0.12_3, and
  etc.)

I asked to freebsd-ports ML what is cause of the difference and got
the answer that it is bug of poudriere.

http://lists.freebsd.org/pipermail/freebsd-ports/2016-January/101572.html
http://lists.freebsd.org/pipermail/freebsd-ports/2016-January/101573.html
Comment 1 Bryan Drewery freebsd_committer freebsd_triage 2016-01-11 20:23:29 UTC 
https://github.com/freebsd/poudriere/issues/313 is a tracking bug for this. It's not really a Poudriere problem and not likely going to be fixed soon. The python framework has dug itself a hole with the version handling.
Comment 2 VK freebsd_triage 2016-10-02 19:58:26 UTC 
New tracking issue here: https://github.com/freebsd/poudriere/issues/259
Comment 3 Yasuhiro Kimura freebsd_committer freebsd_triage 2017-12-03 20:22:45 UTC 
I updated patch for bug #220706. It works fine on real 11.1-RELEASE amd64 environment with ports r455417. But when testing with poudriere 3.2.2, again  "poudriere testport -j 111amd64 -o mail/postfix-policyd-spf-python" fails at check-sanity phase. So it seems something is still wrong.
Comment 4 Yasuhiro Kimura freebsd_committer freebsd_triage 2017-12-07 04:59:06 UTC 
(In reply to Yasuhiro KIMURA from comment #3)

It seems last comment lacked some words, so I explain it again.

Bug #220706 update mail/postfix-policyd-spf-python from 1.3.2 to 2.0.1, and from 2.0.0 this application only support Python 3.3 and later.

When I submitted this bug report first, there isn't flavor support yet. So this update resulted in same problem as comment #0 of this bug report.

But now flavor has come to port framework and poudriere also supports it. I expected the problem of this bug report is fixed so I updated patch of bug #220706 and test it with following environment.

* 11.1-RELEASE amd64
* poudriere 3.2.2
* ports r455417

First I confirmed "cd /usr/ports/mail/postfix-policyd-spf-python ; make install" succeeded without any error. And then I tried "poudriere testport -j 111amd64 mail/postfix-polycyd-spf-python". This time all dependencies were built correctly. That is, all python ports were built as py36-* packages. But building mail/postfxi-policyd-spf-python still failed at check-sanity phase. So something is still wrong with poudriere.
Comment 5 Bryan Drewery freebsd_committer freebsd_triage 2018-01-24 18:31:23 UTC 
What exactly is the error from 'make check-sanity' post-FLAVORS?
Comment 6 Bryan Drewery freebsd_committer freebsd_triage 2018-01-24 19:07:38 UTC 
With the latest poudriere and ports tree and your latest patch, it all builds fine. Nothing more to do here.