[REF] more often tagging or syncing with upstream

[Edward Nevill]

OK. I tried tagging the tree with

jdk8u76-b00-aarch32-160405

But I get

(trusty)ed at localhost:/work/ed/aarch32/jdk8u/hotspot$ hg push
pushing to ssh://enevill@hg.openjdk.java.net/aarch32-port/jdk8u/hotspot
running ssh enevill at hg.openjdk.java.net 'hg -R aarch32-port/jdk8u/hotspot serve --stdio'
searching for changes
1 changesets found
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: [jcheck d46eaf84b346 2015-12-01 13:15:54 -0800]
remote: 
remote: Illegal tag name: jdk8u76-b00-aarch32-160405
remote: 
remote: transaction abort!
remote: rollback completed
remote: abort: pretxnchangegroup.0.jcheck hook failed

So, it seems like there are upstream restrictions on the tags we can use.

Does anyone know the correct syntax of a tag?

All the best,
Ed.


On Fri, 2016-04-01 at 15:05 +0200, Jiri Vanek wrote:
> On 03/22/2016 12:33 PM, Jiri Vanek wrote:
> > On 03/17/2016 06:25 PM, Andrew Hughes wrote:
> >
> > Ping?
> 
> Ping ping? This would really help a lot!
> 
> See laready runnign review: https://bugzilla.redhat.com/show_bug.cgi?id=1318988#c18
> 
> >
> > FYI - https://bugzilla.redhat.com/show_bug.cgi?id=1318988 I already started the wheels of destiny, and I'm pretty sure the not-reproducible tarball will be the reelase blocker :(
> >
> > J.
> >> ----- Original Message -----
> >>> Hello!
> >>>
> >>> I would like to introduce the aarch32 project to Fedora arm repositories.
> >>> To create clearly reproducible source tarball I need some anchor.
> >>> I think you will agree that cloning "tip" do not cover the reproducibility.
> >>> Also I think you will agree that keeping somewhere list of changset ids used
> >>> for source tarball is
> >>> not exactly convenient.
> >>>
> >>> So I would like to kindly ask you for favour and to tag your project forest
> >>> once per day or at least
> >>> once per week or just when things look little bit more stable then yesterday
> >>> (eg tomorrow:) )
> >>>
> >>> We had chosen this approach for aarch64 releases [1] by prefixing by
> >>> "aarch64" and incrementing
> >>> build.  As upstream builds are not exactly continuous, it works fine. But of
> >>> course feel free to
> >>> chose whatever suits you.
> >>>
> >>> I think that having small fedora arm32 community in testing audience may be
> >>> just benefit for project.
> >>>
> >>> Thank you in advance!
> >>>
> >>>    J.
> >>>
> >>>
> >>>
> >>> [1]
> >>> http://hg.openjdk.java.net/aarch64-port/jdk8u/
> >>> 2 weeks ago     andrew     Added tag aarch64-jdk8u72-b16 for changeset
> >>> 92af9369869fdefault tip
> >>> 7 weeks ago     andrew     Added tag aarch64-jdk8u72-b15 for changeset
> >>> 618f7e7b68f4aarch64-jdk8u72-b16
> >>> 7 weeks ago     andrew     Merge jdk8u72-b15aarch64-jdk8u72-b15
> >>> 2 months ago     asaha     Merge
> >>>
> >>>
> >>
> >> I don't think it needs to be as often as "once per day" as I doubt
> >> the RPMs will be updated that frequently. It would however be good
> >
> > sure
> >
> >> to have a known good point to base Fedora RPMs on. This is beneficial
> >> to the AArch32 project as well, as it is then clear what is being used
> >> by these binaries out in the wild.
> >>
> >> Thanks,
> >>
> >
>