For those of us that like to be test new development, I used the packages created by github actions. However a few months ago, you change the CI process and the new packages can not be used as they don’t contain picard.exe
Split CI package tasks into separate files #4283
Is there a chance this can be changed back? Or is there another place to obtain nightlys? Thanks!
I don’t understand. That change was just restructuring of the GitHub actions, they still build the same packages.
E.g. the latest build run for the master branch was Translated using Weblate (Lithuanian) · metabrainz/picard@547d1ce · GitHub , and there are the windows installer and portable builds available the same as before.
Be aware that the master branch switched to Qt6 a while ago and that plugins currently are not compatible.
If you are interested in builds for Picard 2 have a look at the CI runs for the 2.10.x branch.
You can also use the daily builds I provide at Picard daily builds . Those are currently run on the 2.10.x branch.
I’m guessing you didn’t even bother to try to download and install the windows-installer from Translated using Weblate (Lithuanian) · metabrainz/picard@547d1ce · GitHub
I see, the installer packages contains not the full package. I’ll get this fixed, you can use the portable in the meantime.
Thanks.
Is there a command line variable to tell it to use my appdata picard.ini, or is my only option to copy that over to the portable dir?
I also apologize. I shouldn’t have been rude.
You can specify the config file to use as a command line argument. See Appendix C of the Picard User Guide for more details. You can find the location of your config file from the Maintenance section of the Advanced Options settings.
The installer package is fixed now.
@Echelon69 Diffing the Picard exe or installer files is rather pointless and also totally unrelated to the topic here. All that it will tell you is that the files are different, which is to be expected.
