Bug 1165427

Summary: Update create-tar.sh for SeaMonkey 2.53.x
Product: [openSUSE] openSUSE Tumbleweed Reporter: Tristan Miller <psychonaut>
Component: FirefoxAssignee: Tristan Miller <psychonaut>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: create-tar.sh for new source checkout instructions

Description Tristan Miller 2020-03-02 11:31:36 UTC
The procedure for checking out the upstream source code for SeaMonkey has changed considerably.  (They're now using Git instead of Mercurial, etc.)  This means that the create-tar.sh script at <https://build.opensuse.org/package/view_file/mozilla/seamonkey/create-tar.sh?expand=1> that we use to check out the source to build our openSUSE RPMs needs to be rewritten.

The new procedure for checking out the upstream source code is being written at <https://bugzilla.mozilla.org/show_bug.cgi?id=1618806> and when finalized will eventually be posted at <https://archive.mozilla.org/pub/seamonkey/releases/2.53.1/README.txt>.
Comment 1 Tristan Miller 2020-03-05 13:40:59 UTC
Created attachment 832007 [details]
create-tar.sh for new source checkout instructions

The attached create-tar.sh, which has been submitted to the <https://build.opensuse.org/package/show/home:psych0naut:branches:mozilla/seamonkey> project, properly checks out and tarballs the SeaMonkey and Mozilla code from the new Git repositories.

It should be noted that the compare-locales code used in the building of language packs has now been superseded by an in-tree tool: <https://bugzilla.mozilla.org/show_bug.cgi?id=1618806#c5>  Our create-tar.sh and seamonkey.spec files need to be updated accordingly.  (They currently fetch and invoke the old tool, and while this works for the time being, this may break in the near future.)

I will have a go at updating the script and spec file soon.
Comment 2 Tristan Miller 2021-01-28 15:38:30 UTC
The entire build system used in the spec file is now broken, so this issue is effectively subsumed by Bug 1181525.

*** This bug has been marked as a duplicate of bug 1181525 ***