I just updated mozilla-firefox from 1.5_rc3 to 1.5. The "Deer Park" label is still visible everywhere "Firefox" should be (title bar, Help->About, Deer Park Preferences). (I also have 32-bit mozilla-firefox-bin, but that was updated from 1.0.7 so no Deer Park there.) emerge -sv mozilla-firefox Searching... [ Results for search key : mozilla-firefox ] [ Applications found : 2 ] * www-client/mozilla-firefox Latest version available: 1.5 Latest version installed: 1.5 Size of downloaded files: 33,726 kB Homepage: http://www.mozilla.org/projects/firefox/ Description: Firefox Web Browser License: MPL-1.1 NPL-1.1 * www-client/mozilla-firefox-bin Latest version available: 1.5 Latest version installed: 1.5 Size of downloaded files: 8,247 kB Homepage: http://www.mozilla.org/projects/firefox Description: Firefox Web Browser License: MPL-1.1 NPL-1.1 emerge --info Portage 2.0.53_rc7 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r3, 2.6.14-ck5 x86_64) ================================================================= System uname: 2.6.14-ck5 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.12.0_pre11 ccache version 2.4 [enabled] dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.14 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.20-r1 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.osuosl.org/" LC_ALL="en_US" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/gentopia /usr/local/bmg-main /usr/local/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="amd64 X aac aalib alsa audiofile avi bash-completion berkdb bitmap-fonts bzip2 cdr crypt cups curl dbus eds emboss encode esd exif expat fam ffmpeg flac foomaticdb fortran gdbm gif glut gnome gpm gstreamer gtk gtk2 hal howl idn imagemagick imlib ipv6 jack java jpeg junit kde lcms ldap libwww lua lzw lzw-tiff mad mikmod mng mono motif mozilla mp3 mpeg ncurses nls nptl ogg openal opengl pam pcre pdflib perl pic png python qt quicktime readline recode ruby samba sdl speex spell sqlite ssl svg tcltk tcpd tetex theora tiff truetype truetype-fonts type1-fonts udev usb userlocales vorbis wmf xine xml2 xmms xpm xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LDFLAGS, LINGUAS, MAKEOPTS
this is something we can not do with ebuild at moment and that is enable-branding so deerpark will be shown sorry. If upstream gives me permission to enable-branding I will add it and do a -r1 release. Closing invalid.
*** Bug 114005 has been marked as a duplicate of this bug. ***
*** Bug 114023 has been marked as a duplicate of this bug. ***
Please reopen. This has nothing to do with invalid bug report, this simply means that Firefox thinks it's running as a pre-release. Deer Park was the production code name of Firefox 1.5, the final Deer Park release was renamed Firefox again. I don't know where this problem comes from (haven't looked deeper into it), but the version magic when accessing mozilla.org redirects us to deerpark/alpha2.html, which is actually the page used for a previous alpha release of Firefox 1.5. Seems like the Firefox source package the ebuild is using is still branded as such. Maybe someone can investigate this a little further, as this means that language packs won't work on it (installing the german language pack for Firefox 1.5 on the presumed Deer Park alpha2 doesn't work, it installs fine, but doesn't enable itself). PLEASE, PLEASE, reopen and investigate! If this doesn't happen, I'll open a new bug report tomorrow...
*** Bug 114136 has been marked as a duplicate of this bug. ***
Maybe you could modify your local ebuild to include official branding and see what difference that makes.
I don't have any issues as in #4, but I'm curious -- does each distro's version require official blessing from mozilla.com/org before it can be called firefox, or is this because of the source-based nature of Gentoo? And why wouldn't they have done this before the official release date, since RC3 was the final release?
(In reply to comment #7) > I don't have any issues as in #4, but I'm curious -- does each distro's version > require official blessing from mozilla.com/org before it can be called firefox, > or is this because of the source-based nature of Gentoo? And why wouldn't they > have done this before the official release date, since RC3 was the final release? http://www.mozilla.org/foundation/trademarks/policy.html
Thanks for the link. I'm still curious about the timing, though that's on the Mozilla end rather than Gentoo's. Presumably they've heard of Gentoo? Maybe I'm naive about the politics of open source projects, but I would think that smoothing the path for distro repositories would be a little higher on the todo list. Or am I preaching to the choir here? ;-)
I'll brand my Firefox as official first thing tomorrow. Let's see where we get then. The german language pack is unusable as of yet...
*** Bug 114339 has been marked as a duplicate of this bug. ***
*** Bug 114364 has been marked as a duplicate of this bug. ***
*** Bug 114866 has been marked as a duplicate of this bug. ***
*** Bug 89945 has been marked as a duplicate of this bug. ***
*** Bug 117093 has been marked as a duplicate of this bug. ***
Hi, The following URL states the following: http://www.mozilla.org/projects/firefox/roadmap.html On Naming... After some discourse, we have settled on the following naming structure for our releases going forward: 1. Each major release has a code name (e.g. 1.5 is "Deer Park") 2. The alpha releases are named
Hi, The following URL states the following: http://www.mozilla.org/projects/firefox/roadmap.html On Naming... After some discourse, we have settled on the following naming structure for our releases going forward: 1. Each major release has a code name (e.g. 1.5 is "Deer Park") 2. The alpha releases are named <codename> alpha 3. The public beta release is named Firefox 1.5 beta 4. The final release is named Firefox <version> If what we have is a "final release," should they not have changed the name to "Firefox"? It seems like maybe they just forgot to update it prior to releasing it?
(In reply to comment #16) > It seems like maybe they just forgot to update it prior to releasing it? No, it seems that you apparently missed the whole discussion above - such as comment #1 and comment #8
(In reply to comment #17) > (In reply to comment #16) > > It seems like maybe they just forgot to update it prior to releasing it? > > No, it seems that you apparently missed the whole discussion above - such as > comment #1 and comment #8 > Actually sir, I did read the discussion -- it just didn't make any sense. I assume you're not slapping "Gentoo" all over the thing. I also assume you're not making any "serious modification" to the source. I don't see anything there that suggests "if you compile it yourself, you can't call it 'Mozilla Firefox'". At the risk of another hateful response, I still think this is more likely and oversight in the release of the source.
(In reply to comment #18) OK, after taking a look at the installation package, I see the configuration option: --enable-official-branding Enable Official mozilla.org Branding Do not distribute builds with --enable-official-branding unless you have permission to use trademarks per http://www.mozilla.org/foundation/trademarks/ I assume from comment #1 that a trademark use request has been filed. If so, do you have a bugzilla.mozilla.org bugid to track the progress of that or was it done via e-mail?
Please, kindly stop bugspamming us, it won't help or make it any faster. When/if the permission is granted, it will be done. Meanwhile, making noise is pretty much pointless.
*** Bug 118828 has been marked as a duplicate of this bug. ***
