-
-
Notifications
You must be signed in to change notification settings - Fork 14k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xcircuit: 3.9.73 -> 3.10.10 #42418
xcircuit: 3.9.73 -> 3.10.10 #42418
Conversation
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/xcircuit/versions. These checks were done: - built on NixOS - /nix/store/rl0z1s01yhpymjwwi5w2gh9550cc6qai-xcircuit-3.10.10/bin/xcircuit passed the binary check. - 1 of 1 passed binary check by having a zero exit code. - 0 of 1 passed binary check by having the new version present in output. - found 3.10.10 with grep in /nix/store/rl0z1s01yhpymjwwi5w2gh9550cc6qai-xcircuit-3.10.10 - directory tree listing: https://gist.github.com/1f8753adc5ffc9a253cb223072cffcd2 - du listing: https://gist.github.com/50dbec8988a1f5476256dfab53d165cd
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: xcircuit Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: xcircuit Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: xcircuit Partial log (click to expand)
|
The xcircuit 3.10.* releases are development releases and should not be taken as a replacement for the 3.9.* releases. So, I would object to this automatic update. @ryantm Does your bot have a means to distinguish development release cycles from stable ones? |
@spacefrogg No, but Repology, the main source of information for nixpkgs-update, has a system for dealing with this. Unfortunately, it looks like xcircuit does not have a system for indicating if a release is development just by looking at the version number, so it would require constant updates to the repology-rules to avoid issues. |
As a possible solution, I can just blacklist this package from automatic updates entirely. @spacefrogg Do you want me to do that? |
@ryantm If you can, blacklist every 3.10.* until further notice. |
@spacefrogg I emailed the development list of xcircuit and the developer seems willing to adopt a versioning scheme where stable versions are different from development versions http://opencircuitdesign.com/pipermail/xcircuit-dev/2018-June/000986.html |
@ryantm Thanks a lot! Keep me posted, here. I will make separate packages for xcircuit stable and dev once the new versioning scheme is in place. |
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/xcircuit/versions.
These checks were done:
meta.description for xcircuit is: '"Generic drawing program tailored to circuit diagrams"'.
cc @spacefrogg for testing.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
Test this build: