Hi GetMem,
Here are some more information about the version update process I've been using for BGRABitmap.
First:
- The JSON package information file is part of the master branch on the GitHub repository. So it is updated when the changes are merged.
Then (generally a few seconds afterwards but sometimes a bit later):
- The new version is released, adding a tag for the version, and then the zip archive of the package (mentioned in the JSON file) becomes available.
So I suppose the following can happen: OPM sees that there is a new version but when trying to access the zip file, it fails.
Could that be a reason for the problem of version update?
Hi circular,
Sorry for the late reply, somehow I did not noticed your post. OPM only checks the json in every few minutes, so I don't think the above mentioned reason is the problem.
Updating from the package maintainers webpage might fail because:
1. Many users did not liked the idea that OPM connects to various webpages(github, sourceforge, bitbucket, etc...) and downloads information about a particular package,
so this feature is disabled by default(OPM-->Options-->General-->Check for package update, then change never to some other value).
2. In order to connect to github, OPM needs the ssl libraries. In lazarus trunk the libraries are automatically downloaded, that's not the case with previous versions.
3. Since 2.0.10 was released with FPC 3.2.0, it introduced a new bug. I fixed yesterday in trunk, but unfortunately is to late for 2.0.10.
In the next major release, everything will work well again. Luckily the release is not so far away.
Today I saw that you released 11.2.0.0 and I updated the central repository, maybe too soon. I just noticed that the update json is only 11.1.0.0.