Closed texierp closed 3 years ago
Looking at the Github list of tags, I see v3.2 at the top. And in my local copy I see:
git tag | grep 3.2
v3.2
Yes you're right, but I don't know why it seems missing on master (e.g git log - - oneline) :/
Probably because I haven't committed any more changes after the tag...
But this commit https://github.com/michaelrsweet/mxml/commit/38b044ed8ca2a611ed9ed3e26c4b46416335194e is missing on master
In fact,the real problem is about the maintenance. If I try to upgrade the package that we have in openembedded side [1], I have the following issue:
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 20 (0% match, 100% complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and all succeeded.
INFO: Extracting upgraded version source...
ERROR: Execution of 'git checkout 38b044ed8ca2a611ed9ed3e26c4b46416335194e' failed with exit code 128:
fatal: reference is not a tree: 38b044ed8ca2a611ed9ed3e26c4b46416335194e
Normal because the commit 38b044ed8ca2a611ed9ed3e26c4b46416335194e (the reference for the version 3.2) is not on master or at least not on a specific branch ...
@texierp I have no idea what went wrong with this tagging that you don't see the tag on master. All of my releases are automated with a script so I don't screw it up... :) I will investigate further on my other machines in case something from a local clone wasn't pushed, but since Github sees the tag I'm not sure that will yield anything.
For your OpenEmbedded recipe you should be pointing at the signed tarballs I post for every release and not pulling a Git revision, since the exported tarballs omit Git-specific source files that are not part of a normal release.
Hi @michaelrsweet,
It seems that the tag
v3.2
is missing on master branch, see [1]:Is it possible to push it ? :)
Thanks
../Pierre-Jean
[1] - https://github.com/michaelrsweet/mxml/commit/38b044ed8ca2a611ed9ed3e26c4b46416335194e