[Bug 218323] www/firefox: firefox-esr (v45) package fails to run

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218323

Jan Beich <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@FreeBSD.org,
| |***@FreeBSD.org
Assignee|***@FreeBSD.org |***@FreeBSD.org

--- Comment #4 from Jan Beich <***@FreeBSD.org> ---
Debugging pkg-install(8) issues is outside gecko@ scope. Re-assigning.

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218323

--- Comment #5 from MMacD <***@att.net> ---
Okay, I'm baffled. You reassigned it as a pkg bug. Who built those FF
packages? Surely it was one of the gecko team? How were the problems not
caught during those builds?

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218323

--- Comment #6 from Jan Beich <***@FreeBSD.org> ---
Each build is automated on the package cluster in a clean jail. The list of
jails is available on http://pkg-status.freebsd.org/ where with enough clicks
you can get to the build logs e.g.,

http://beefy2.nyi.freebsd.org/data/103amd64-quarterly/436927/logs/firefox-esr-45.8.0_1,1.log
(last 2017Q1)
http://beefy2.nyi.freebsd.org/data/103amd64-quarterly/437473/logs/firefox-esr-45.8.0_3,1.log
(first 2017Q2)

2017Q1 has reached EOL as soon as 2017Q2 was built. comment 0 shows firefox-esr
from 2017Q1 installed on top of what appears 2016Q[1-3] set. Even then the
solver should be able to figure out when to upgrade dependencies. Maybe it's
confused by some packages built with non-default options or coming from a
custom repo (only guesses due to not enough details). A year ago (or more)
firefox dependend on gstreamer but it has never pulled libav port (bundled
version was used until ports r397984).

In short, "pkg install" alone is usually safe on a /quarterly repo until it
switches to a new set. No one does QA for mixed sets - too many permutations.

comment 0 also said "it fails to run" without quoting the actual errors
suggests the reporter knows better than maintainer which is why the focus is on
pkg and not firefox. ;)

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218323

--- Comment #7 from MMacD <***@att.net> ---
"comment 0 also said "it fails to run" without quoting the actual errors
suggests the reporter knows better than maintainer which is why the focus is on
pkg and not firefox. ;)"

Well, that's the thing -- it didn't say anything, it just failed to run. If it
wrote something to some log (what log?) it didn't say anything about that,
either. It should at a *minimum* write STDOUT with "I couldn't run. Details
in /usr/local/logs/firefox-esr.log" or similar.

The way fBSD apps report problems gets up my human-factors nostril. It reminds
me of the original C compiler: "you have an error". Oh? Do you think you're
adding to my knowledge, you ridiculous piece of software? I actually worked
out for myself that there was an error when my code didn't execute!

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218323

Oleksandr Tymoshenko <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC|***@FreeBSD.org |***@FreeBSD.org

--- Comment #8 from Oleksandr Tymoshenko <***@FreeBSD.org> ---
Removing bugmeister@ from Cc: bug scope does not include bugtracker operations
or triage/resolution procedures.

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218323

***@utanet.at changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@utanet.at

--- Comment #9 from ***@utanet.at ---
We have version 52.5.3. Overcome by events?

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218323

***@utanet.at changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|New |Closed
Resolution|--- |Overcome By Events