Epiphany doesn't mention Ubuntu in user agent string

thank you for your bug report, that would be a nice task for a new contributor to work on

the prefs you need to set are:

general.useragent.vendor=Ubuntu (get this from lsb_release -i)
general.useragent.vendorComment=jaunty (get this from lsb_release -c)
general.useragent.vendorSub=9.04 (get this from lsb_release -r)

e.g. put the prefs in /usr/share/epiphany-browser/default-prefs.js

I've never worked with Debian packages (other than with checkinstall) before, but would something like this do the trick?

The script depends on:
  echo
  mktemp
  lsb_release
  cut
  sed
  cat
  rm

It unconditionally replaces the default user-agent string every time the script is run.

I tested the script itself and it works for me. (user-agent came back as "Mozilla/5.0 (X11; U; Linux i686; en; rv:1.9.0.10) Gecko/20080528 Ubuntu/9.04 (jaunty) Epiphany/2.22 Firefox/3.0")

using postinst commands is the wrong way you can simply ship a .js with the pacakge or patch the source as debian is doing

I had a feeling that might be the case, but based on Alexander's suggestion above, I wasn't sure where the best place to modify the .js file would be.

If Debian already has this same fix in native code, then I agree, that's the way to go.

We could use the same script at the time of packaging rather than the time of installation. (But would 'lsb_release' always return the correct values when the .js file is being packaged? I assume there are other ways to get that data for the architecture the package is being generated for, but pre-determining it seems like more of a hack.)

We could use a similar postinst script to generate a separate .js file with the current lsb_release info, and modify the default default-prefs.js to comment out the lines that set the values to empty strings.

there is probably no need to bother using lsb values, static versions should work or use those in the rules to build the .js at build time rather

Okay, here's attempt #2.

This one integrates the script into the build process instead. I didn't do this at first, since I wasn't sure if whoever was building the package would always have the same /etc/lsb-release info as the target distribution.

Am I being too pedantic adding 'mktemp' and 'sed' to build-depends? I think the build scripts already used 'sed'. Maybe the dependency is buried elsewhere already. (lsb-release was already a dependency.)

Modified patch to not require sed, or a helper script.

please use lsb_release -s -c for the general.useragent.vendorComment text.

besides from that its ok. Please include a changelog entry in your diff (aka full debdiff).

... and here's the debdiff. (with a small bug fix as well)

Okay, I think I've really got it now. Better debdiff attached. Sorry for the spam.

This bug was fixed in the package epiphany-browser - 2.26.1-0ubuntu2

---------------
epiphany-browser (2.26.1-0ubuntu2) karmic; urgency=low

  * Fix default prefs file to use info from lsb_release (LP: #332253)

 -- Mike Pontillo <email address hidden> Wed, 06 May 2009 15:30:31 -0700