Closed Bug 527627 Opened 15 years ago Closed 5 years ago

Source tarballs missing for Fennec binaries

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Maemo
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: reed, Assigned: pavlov)

References

()

Details

(Whiteboard: [blocks-fennec][needs alphas/pre-alphas])

Unless I'm looking in the wrong place, it looks like the source tarballs for all Fennec releases except Fennec 0.8 are missing.

http://moff.mozilla.com/dists/chinook/release/source/
ftp://ftp.mozilla.org/pub/mozilla.org/mobile/dists/chinook/release/source/
ftp://ftp.mozilla.org/pub/mozilla.org/mobile/<every version>/

If this is true, we're in violation of the GPL and the MPL.

Please to be fixing. :)
I'll get to this this week.
Assignee: nobody → aki
I've got tarballs of the 1.0b? releases at http://ftp.mozilla.org/pub/mozilla.org/mobile/source/ ... I was able to unpack the debs and look at the source stamps, then hg archive the appropriate repositories.

The others will take some digging.
AFAIK we can also satisfy these requirements by clearly outlining the process for getting the relevant source directly from hg/hgweb. That would probably require that we consistently tag both repos for all releases, though (I noticed earlier that we don't seem to be tagging m-b consistently).
What's the status of this? The core problem still isn't fixed, and another Fennec version has been released without its source code being available.
Flags: blocking1.9.2?
We now have release factories for maemo, which include a source factory.
Aki: is that another way of saying "we've fixed this and the next release will have a source tarball"?

This is a licensing compliance issue, which makes it important. 

Gerv
That's correct.
(In reply to comment #7)
> That's correct.

This doesn't seem to be fixed for all the old releases, yet... From comment #0, both of these places are missing source tarballs:

http://moff.mozilla.com/dists/chinook/release/source/
ftp://ftp.mozilla.org/pub/mozilla.org/mobile/dists/chinook/release/source/

If I look in ftp://ftp.mozilla.org/pub/mozilla.org/mobile/repos/trunk_en-US/dists/chinook/release/, there's a source directory, but it's missing stuff for all releases, too. The same goes for all locales.
That is also correct, which is why this bug is still open, to track the previous tarballs.

You'll find the source bundles + tarball for fennec 1.0 rc1 build 1 at http://ftp.mozilla.org/pub/mozilla.org/mobile/candidates/1.0rc1-candidates/build1/
for the older releases, can we rely on hgweb's ability to generate tarballs of mozilla-central + mobile-browser? 

e.g.
http://hg.mozilla.org/mozilla-central/archive/caeba7562e49.tar.bz2
and
http://hg.mozilla.org/mobile-browser/archive/14bbac84b71c.tar.bz2
Marking blocking1.9.2, but really this just blocks the final release of Fennec.
Flags: blocking1.9.2? → blocking1.9.2+
Whiteboard: [blocks-fennec]
(In reply to comment #10)
> for the older releases, can we rely on hgweb's ability to generate tarballs of
> mozilla-central + mobile-browser? 

Sure - I mentioned this in comment 3. Adding a README to the directory that points to the relevant hgweb links is sufficient to satisfy the requirements, I think! (IANAL, etc.)
Betas are in http://ftp.mozilla.org/pub/mozilla.org/mobile/source/
RC candidates are in http://ftp.mozilla.org/pub/mozilla.org/mobile/candidates/*/buildN/source/

We're missing alphas and pre-alphas.  We need to track the revisions down somehow.

I don't think this should block, as the releases should have source built automatically from here on out.
Whiteboard: [blocks-fennec] → [blocks-fennec][needs alphas/pre-alphas]
Stuart -- do you have records on which revisions the alphas/M-releases were built off of?
Assignee: aki → pavlov
Component: Release Engineering → Linux/Maemo
Flags: blocking1.9.2+
Product: mozilla.org → Fennec
QA Contact: release → maemo-linux
Version: other → Trunk
Component: Linux/Maemo → General
OS: All → Linux (embedded)
Hardware: All → ARM
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.