Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 17 Sep 2017 11:37:51 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 222389] ports-mgmt/synth: Fails to test proposed update of mail/postfix-policyd-spf-python
Message-ID:  <bug-222389-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222389

            Bug ID: 222389
           Summary: ports-mgmt/synth: Fails to test proposed update of
                    mail/postfix-policyd-spf-python
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs@FreeBSD.org
          Reporter: yasu@utahime.org
                CC: ericturgeon.bsd@gmail.com
                CC: ericturgeon.bsd@gmail.com

Created attachment 186455
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D186455&action=
=3Dedit
synth build log of mail/postfix-policyd-spf-python

About 2 months ago I submitted update of mail/postfix-policyd-spf-python as=
 bug
#220706. But it was hold off because of known issue of poudriere. That is,
while 'cd /usr/ports/mail/postfix-policyd-spf-python && make install' works
fine without any errors, 'poudriere testport -o
mail/postfix-policyd-spf-python' fails due to the issue reported in bug
#206067. This is an introduction of this PR.

And today I wonder if synth can build my update. So I installed synth,
configured it and tried 'synth test mail/postfix-policyd-spf-python'. But it
failed as following:

root@rolling-vm-freebsd1[1646]# synth test mail/postfix-policyd-spf-python
Stand by, building pkg(8) first ... done!




The task is complete.  Final tally:
Initial queue size: 15
    packages built: 14
           ignored: 0
           skipped: 0
            failed: 1

Duration: 00:05:00
The build logs can be found at: /usr0/synth/NoCustomization/log=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20
                                             root@rolling-vm-freebsd1[1647]=
#=20

By checking build log of mail/postfix-policyd-spf-python (it is attached to
this PR) and listing built packages in repository directory, I am convinced
that syth has same issue as poudriere. That is.

1. mail/postfix-policyd-spf-python has run-time dependency on mail/py-pyspf=
 and
mail/py-authres. So synth also build these ports.
2. mail/postfix-policyd-spf-python is Python 3 only ports (USES=3Dpython:3.=
3+).
So synth build it as package for default Python 3 version, that is, 3.6.
3. Since mail/postfix-policyd-spf-python is built as Python 3.6 package,
depending ports (mail/py-pyspf, maii/py-authres and there dependencies) also
have to be built as Python 3.6 packages.
4. But mail/py-pyspf, mail/py-authres and etc themselves are compatible with
all supported Python versions (USE=3Dpython). So synth build them as packag=
e for
default Python version, that is, 2.7.
5. So when synth completed build of all dependencies and start building
mail/postfix-policyd-spf-python, there are no required Python 3.6 packages =
in
repository, and it results in build failure.

After all it seems the root of this issue is that synth builds depending po=
rts
as if they were master one. So in order to fix this issue synth must be cha=
nged
so requirements of master port are inherited to build of dependencies in so=
me
way.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-222389-13>