[haiku-depot-web] Re: Update - Changelog and Adjusted Maintenance Tasks
- From: Andrew Lindesay <apl@xxxxxxxxxxxxxx>
- To: haiku-depot-web@xxxxxxxxxxxxx
- Date: Mon, 21 Sep 2015 00:02:31 +1200
Hello Oliver;
I've just patched as tag "haikudepotserver-1.0.55" which can be deployed
when you have a moment.
whenever one or more new packages have been uploaded, the respective git
hook iterates over the architectures that had changes and triggers both
__repository/haikuports
and
__repository/haikuports/source/haikuports_<arch>/import
via curl.
You can call...
/__repository/haikuports/import
...and it will iterate over all of the architectures it knows about and
import them. Using the other URL you could get it to import for
specific architectures. You do not need to call both of the URLs.
Looking at the logs, I have noticed that the repository import code is
logging a couple of warnings about having imported packages whose version
is older or the same as the existing version. For some of these, the stated
relation between the versions looks wrong, for instance there's a warning
about openssh-6.9p1-1 being older than openssh-6.0p1-8.
Andrew: could you please have a look?
Yes; this looks like a problem. The "openssh" case was because it was
stripping out the leading "0" digit on the _minor_ part of the version.
I've adjusted this now and the ordering appears to be working in the
automated testing.
I'm not entirely sure what to do with "beam" because it did have the
"2alpha" in the minor field, but this is now "2". I would have to check
the ordering provided by "/src/kits/shared/NaturalCompare.cpp" to see
how it handles this situation. I've added a ticket #94 to look into
this. The same sort of thing applies to the "friss" package.
I think the version comparison looks sound for warnings on;
* tiff_x86
* tiff_x86_devel
* dejavu
* ca_root_certificates
* beshare_x86
* ffmpeg
* ffmpeg_devel
NOTE: I have decided to leave the sysadmin team by the end of this year.
This means that I will no longer be in a position to do the
haikudepotserver upgrades by 2016. So someone else has to take on that role
- one simple solution would be to give Andrew admin rights on vmrepo, of
course.
Thanks for letting me know about that and for the help you have been
able to provide the last couple of years on this. I would be happy to
deploy the haikudepotserver application-server upgrades. For broader
support, is another member of the sysadmin team able to join this
mailing list in 2016 or is there a sysadmin mailing list running?
Regards
--
Andrew Lindesay
Other related posts:
