[Bug 227836] sysutils/py-salt : update to 2018.3.0_2

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227836

Kubilay Kocak <koobs at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|---                         |Normal
           See Also|                            |https://github.com/saltstac
                   |                            |k/salt/issues/47006
             Status|New                         |Open
              Flags|                            |maintainer-feedback?(christ
                   |                            |er.edwards at gmail.com)
           Severity|Affects Only Me             |Affects Many People
                 CC|                            |christer.edwards at gmail.com,
                   |                            |python at FreeBSD.org
            Summary|sysutils/py-salt : update   |sysutils/py-salt : update
                   |to 2018.3.0_2 [maintainer]  |to 2018.3.0_2
           Keywords|                            |needs-qa

--- Comment #9 from Kubilay Kocak <koobs at FreeBSD.org> ---
@Christer 

I don't believe the proposed approach will be appropriate:

1) Wont these compiled files be created at first run, leaving leftovers after
pkg-deletion? QA (poudriere) wouldn't pick these up as salt would not have run
between installation/deinstallation.

2) Has upstream fixed this issue upstream since reporting? If so, can you point
us to any other issue(s) and/or commit(s) ?

Also, please remember to set maintainer-approval flag to + on attachments for
ports you maintain

Also noted from the upstream issue:

@jhujhiti says:

"Specifically, f_noext = f_noext.replace(BIN_PRE_EXT, '') is an attempt to
ignore the extra bits in the filename of a bytecode file, but it only removes
cpython-36, so we end up loading a module named fx2.opt-1."

Has there been an attempt to fix that section of the code to not load/match the
optimized file? 

It appears that that is the root cause, and addressing that will be the
correct, appropriate and permanent fix.

-- 
You are receiving this mail because:
You are on the CC list for the bug.