You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the epoch jump, eopkg.py2 (and Solus SC) will no longer be present, but it will still be possible to build the ported-to-py3 3rd party package recipes w/eopkg.py3, assuming that each recipe is successfully ported to use a #!/usr/bin/env/python3 shebang.
3rd party packages builds use BuildXML.
After the epoch jump, eopkg.py2 (and Solus SC) will no longer be present, but it will still be possible to build the ported-to-py3 3rd party package recipes w/eopkg.py3, assuming that each recipe is successfully ported to use a
#!/usr/bin/env/python3
shebang.@Staudey has a PR for this here
The text was updated successfully, but these errors were encountered: