Skip to content

Conversation

@SwampRabbit
Copy link

It looks like this repo is being used for updates rather than master?

  • create debian/copyright file
  • update debian/control file
  • update debian/changelog file

corrections to changelog to reduce errors when trying to use dch to add more entries
add debian/copyright
reformat and update debian/control
- enforce python3-psutil required version
- add nvidia-smi to recommends
@KrispyCamel4u
Copy link
Owner

Hi,
V1.x.x is more of a buffering branch for master. So to test the feature addition and for any incoming changes.

@SwampRabbit
Copy link
Author

@KrispyCamel4u ok thanks for the info.

So would this PR be considered "incoming changes" or would you like me to make one against master?

The updated debianization changes brings it closer into compliance with Debian packaging standards, reduces build warnings and errors, and allows this to be included in actual Debian based Distro repos. It will save time later if it does get considered to be included upstream.

For example its ok to have your GitHub branch named 1.x.x, but its not a legitimate release version, so I'm tracking it as 1.3.9+git20211212 when I just built from 1.x.x with commits on 20211212 since 1.3.9 was the last official release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants