Rpmvenv

The file_extras plugin now allows for setting special permissions and ownership on individual files. For example:

json
{"file_extras": {
"files": [
{
"src": "somedir/project_init_script",
"dest": "etc/init.d/project",
},
{
"src": "somedir/with/perms",
"dest": "etc/with/perms",
"attr": {
"permissions": "0644",
"user": "testuser",
"group": "testgroup"
}
},


By default, all extra files keep their permissions and are owned to the user and group configured in the file_permissions settings.


Note: This is identical to 2.1.0 except that it includes a change to the setup.py version. I forgot to do this in the 2.1.0 tag.

The `file_extras` plugin now allows for setting special permissions and ownership on individual files. For example:

json
{"file_extras": {
"files": [
{
"src": "somedir/project_init_script",
"dest": "etc/init.d/project",
},
{
"src": "somedir/with/perms",
"dest": "etc/with/perms",
"attr": {
"permissions": "0644",
"user": "testuser",
"group": "testgroup"
}
},


By default, all extra files keep their permissions and are owned to the user and group configured in the `file_permissions` settings.

This change drops support for all Python versions that have reached their end of life. This includes all Python 2 versions and all Python 3 versions below 3.5.

The 2.x.x series, unlike the 1.x.x series, will no longer attempt to support end of life Python versions.

Python 2, itself, was discontinued on 2020-01-01. Since then, libraries that rpmvenv depends on have started breaking compatibility with Python 2 or even adding code that prevents the use of that library in Python 2 regardless of compatibility. It has also become increasingly difficult to support code that works from Python 2.6 to the most recent versions of Python 3.

The last releases that support Python 2 are version 0.27.0 and 1.0.0. These are both the same release. There will be no more releases in the 0.x or 1.x ranges.

If you are using Python 2 then here is an example requirements.txt that has dependencies pinned to the last known versions that support Python 2:


jinja2==2.11.3
venvctrl>=0.5.0,<2.0.0
argparse>=1.4.0,<2.0.0
confpy>=0.11.0,<2.0.0
ordereddict>=1.1.0,<2.0.0
semver>=2.9.1,<3.0.0

Python 2, itself, was discontinued on 2020-01-01. Since then, libraries that rpmvenv depends on have started breaking compatibility with Python 2 or even adding code that prevents the use of that library in Python 2 regardless of compatibility. It has also become increasingly difficult to support code that works from Python 2.6 to the most recent versions of Python 3.

The last releases that support Python 2 are version 0.27.0 and 1.0.0. These are both the same release. There will be no more releases in the 0.x or 1.x ranges.

If you are using Python 2 then here is an example requirements.txt that has dependencies pinned to the last known versions that support Python 2:


jinja2==2.11.3
venvctrl>=0.5.0,<2.0.0
argparse>=1.4.0,<2.0.0
confpy>=0.11.0,<2.0.0
ordereddict>=1.1.0,<2.0.0
semver>=2.9.1,<3.0.0

This release updates the tests and requirements files to use the latest venvctrl==0.5.0.

This fixes build failures for the most recent versions of virtualenv which include a nu shell activation script
that contains the BUILDROOT. The latest version of venvctrl rewrites the paths in the activate.nu file so that
the check-buildroot script passes.