[Bug 218712] mail/thunderbird: update to 52.0.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218712 --- Comment #1 from Jan Beich--- Comment on attachment 181853 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=181853 thunderbird and thunderbird-i18n, 52.0.1 > -#soundtouch>=1.9.0:audio/soundtouch \ Either drop or apply to other gecko@ ports. It's currently just a reminder what version of soundtouch is bundled. (In reply to Christoph Moench-Tegeder from comment #0) > linux-thunderbird is still at 45.8.0 - I propose to set that DEPRECATED OK. linux-thunderbird can go away first but other linux-* ports under gecko@ can follow as well. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
[Bug 218712] mail/thunderbird: update to 52.0.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218712 Jan Beichchanged: What|Removed |Added Attachment #181853||maintainer-approval+ Flags|| -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
On 17 Apr 2017, at 17:26, Mark Johnston wrote: On Mon, Apr 17, 2017 at 09:28:07PM +0100, Sevan / Venture37 wrote: On 17 April 2017 at 20:54, Ryan Stonewrote: On Sat, Apr 15, 2017 at 10:50 AM, George Neville-Neil wrote: Can you explain this grief? What is the problem? Best, George dtrace -G requires the ability to modify the object files in-place before linking. This causes havoc if the objects are in .a archives (dtrace can't read those) or if the objects need to be linked into multiple binaries. It also destroys the ability to do an incremental build, as dtrace -G can't be run on the same object twice. The whole process is really a hack. The build actions done by dtrace should be done by the compiler and linker instead. Getting the linker to support the process would go a long way, as then dtrace -G could be run on individual objects and most of my complaints go away. Not to detract from the issue with the -G flag, I just wanted to highlight that it's used for ELF binaries, until Apple switches away from Mach-o, this wont be an issue there (dtrace on OS X does not feature the -G flag). I think the more significant difference is that Apple has more control over their toolchain and have modified it to directly implement the functionality that's overwise implemented by dtrace -G. As Ryan pointed out, this functionality really belongs in the static linker; one more piece of evidence for this is the number of non-trivial modifications we've needed to make to dtrace -G to avoid relying on undocumented behaviour in the Sun link editor, and later, GNU ld 2.17. Now that FreeBSD is transitioning to lld, we have some opportunity to implement USDT support in the static linker, and at least one of the lld developers seems amenable to proposals along those lines. However, I don't know of any concrete plans or designs. Seems like something we could discuss in an RFD: https://github.com/opendtrace/rfd Best, George ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
On 17 Apr 2017, at 16:28, Sevan / Venture37 wrote: On 17 April 2017 at 20:54, Ryan Stonewrote: On Sat, Apr 15, 2017 at 10:50 AM, George Neville-Neil wrote: Can you explain this grief? What is the problem? Best, George dtrace -G requires the ability to modify the object files in-place before linking. This causes havoc if the objects are in .a archives (dtrace can't read those) or if the objects need to be linked into multiple binaries. It also destroys the ability to do an incremental build, as dtrace -G can't be run on the same object twice. The whole process is really a hack. The build actions done by dtrace should be done by the compiler and linker instead. Getting the linker to support the process would go a long way, as then dtrace -G could be run on individual objects and most of my complaints go away. Not to detract from the issue with the -G flag, I just wanted to highlight that it's used for ELF binaries, until Apple switches away from Mach-o, this wont be an issue there (dtrace on OS X does not feature the -G flag). Well at least I now "get" the issue. Thanks. Best, George ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
On 17 April 2017 at 20:54, Ryan Stonewrote: > On Sat, Apr 15, 2017 at 10:50 AM, George Neville-Neil > wrote: > >> >> Can you explain this grief? What is the problem? >> >> Best, >> George >> > > dtrace -G requires the ability to modify the object files in-place before > linking. This causes havoc if the objects are in .a archives (dtrace can't > read those) or if the objects need to be linked into multiple binaries. It > also destroys the ability to do an incremental build, as dtrace -G can't be > run on the same object twice. > > The whole process is really a hack. The build actions done by dtrace > should be done by the compiler and linker instead. Getting the linker to > support the process would go a long way, as then dtrace -G could be run on > individual objects and most of my complaints go away. Not to detract from the issue with the -G flag, I just wanted to highlight that it's used for ELF binaries, until Apple switches away from Mach-o, this wont be an issue there (dtrace on OS X does not feature the -G flag). Sevan ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
On Sat, Apr 15, 2017 at 10:50 AM, George Neville-Neilwrote: > > Can you explain this grief? What is the problem? > > Best, > George > dtrace -G requires the ability to modify the object files in-place before linking. This causes havoc if the objects are in .a archives (dtrace can't read those) or if the objects need to be linked into multiple binaries. It also destroys the ability to do an incremental build, as dtrace -G can't be run on the same object twice. The whole process is really a hack. The build actions done by dtrace should be done by the compiler and linker instead. Getting the linker to support the process would go a long way, as then dtrace -G could be run on individual objects and most of my complaints go away. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: FF nightly build help
## AN (a...@neu.net): Between this: > Last Changed Date: 2015-06-23 12:55:13 -0400 (Tue, 23 Jun 2015) and this: > ===> Configuring for firefox-nightly-41.0.353381,1 I really wouldn't expect anything to work. Why would one even try that? Seriously, Firefox pre-41 from nearly two years ago? Regards, Christoph -- Spare Space ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
maintainer-feedback requested: [Bug 218712] mail/thunderbird: update to 52.0.1
Christoph Moench-Tegederhas reassigned Bugzilla Automation 's request for maintainer-feedback to ge...@freebsd.org: Bug 218712: mail/thunderbird: update to 52.0.1 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218712 --- Description --- Created attachment 181853 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=181853=edit thunderbird and thunderbird-i18n, 52.0.1 attached patch updates thunderbird and thunderbird-i18n to 52.0.1. Update is rather trivial, passes poudriere and "works for me". linux-thunderbird is still at 45.8.0 - I propose to set that DEPRECATED, as I have neither the resources to test the changes under linux emulation (GTK3? pulseaudio?) nor do I believe many linux-only plugins to exist. (additionally, any dependencies on pulseaudio seem to get pushback lately, even if it "works for me"). If ok'd, I'll add the DEPRECATED line in a seperate commit. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
[Bug 218712] mail/thunderbird: update to 52.0.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218712 Bug ID: 218712 Summary: mail/thunderbird: update to 52.0.1 Product: Ports & Packages Version: Latest Hardware: Any URL: https://www.mozilla.org/en-US/thunderbird/52.0.1/relea senotes/ OS: Any Status: New Keywords: easy, patch, patch-ready Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ge...@freebsd.org Reporter: c...@freebsd.org Assignee: ge...@freebsd.org Flags: maintainer-feedback?(ge...@freebsd.org) Created attachment 181853 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=181853=edit thunderbird and thunderbird-i18n, 52.0.1 attached patch updates thunderbird and thunderbird-i18n to 52.0.1. Update is rather trivial, passes poudriere and "works for me". linux-thunderbird is still at 45.8.0 - I propose to set that DEPRECATED, as I have neither the resources to test the changes under linux emulation (GTK3? pulseaudio?) nor do I believe many linux-only plugins to exist. (additionally, any dependencies on pulseaudio seem to get pushback lately, even if it "works for me"). If ok'd, I'll add the DEPRECATED line in a seperate commit. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
[Bug 217713] Frequent freezes with recent www/firefox
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217713 rkober...@gmail.com changed: What|Removed |Added Severity|Affects Only Me |Affects Some People --- Comment #6 from rkober...@gmail.com --- To be clear, the "freezes" I see are fairly short... 5-10 seconds, though there may be several such freezes loading a single web page. Loading this bug report took about 40 seconds on my system. During the freeze, all firefox activity stops. I can't switch to a different tab and the "spinners" in any tabs that are updating stop spinning. It is certainly interesting that you see a long delay in firefox exiting.While I have, on occasion, seen this, it is not something I see normally. I do see a delay of up to 30 seconds (est.) after the firefox window is deleted and firefox actually exiting so that a new firefox can be launched, but this is not new and is dependent on system load. Still seeing this with 52.0.2. Will try 53 shortly. All suggested tweaks (ULE vs. 4BSD and firefox settings) have had no visible effect. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
[Bug 217713] Frequent freezes with recent www/firefox
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217713 peter.hender...@ieee.org changed: What|Removed |Added CC||peter.hender...@ieee.org --- Comment #5 from peter.hender...@ieee.org --- I've also had the same problem. It persisted from FreeBSD 10 to an installation, from a USB memstick of FreeBSD 11.0-RELEASE-p9 and a complete rebuild of all my ports. Most of these ports were built using the default configurations. In particular, the default configuration was used for firefox, although I've subsequently changed it by turning off Pulse Audio. This was to restore the sound I'd lost in the reinstallation, but this did not fix the freezing. It may be useful to know, a site it consistently freezes on is www.freebsd.org. Hence, this comment is being submitted via chrome. Also, when quitting, after such a freeze, the firefox icon on my kde4 tray persists for for a minute or more and firefox will not restart until the icon disappears, complaining that there is another firefox process running. To get rid of the icon, I have to click on the icon quit option twice. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
[Bug 218704] www/firefox has no sound.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218704 Bug ID: 218704 Summary: www/firefox has no sound. Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: ge...@freebsd.org Reporter: peter.hender...@ieee.org Assignee: ge...@freebsd.org Flags: maintainer-feedback?(ge...@freebsd.org) For www/firefox version 53.0_2,1, sound does not work when built with the standard configuration. I recently installed FreeBSD 11.0-RELEASE-p9 and built all ports from scratch, almost entirely with the default configurations. I found there was no sound in firefox, including YouTube videos. Other applications I tested for sound still worked, including opera, xmms, vlc-qt4 and the chrome browser. After much searching, the suggested solution in various forums is to turn off Pulse Audio in the configuration. This I did. After rebuilding firefox, the sound worked again. For reference, here is the configuration I used, after turning off Pulse Audio. ALSA : on BUNDLED_CAIRO : on CANBERRA : off DBUS : on DEBUG : off DTRACE : on FFMPEG : on GCONF : off GNOMEUI: off INTEGER_SAMPLES: off LIBPROXY : off OPTIMIZED_CFLAGS: on PGO: off PROFILE: off PULSEAUDIO : off RUST : on SNDIO : off TEST : off -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
maintainer-feedback requested: [Bug 218704] www/firefox has no sound.
peter.hender...@ieee.org has reassigned Bugzilla Automation's request for maintainer-feedback to ge...@freebsd.org: Bug 218704: www/firefox has no sound. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218704 --- Description --- For www/firefox version 53.0_2,1, sound does not work when built with the standard configuration. I recently installed FreeBSD 11.0-RELEASE-p9 and built all ports from scratch, almost entirely with the default configurations. I found there was no sound in firefox, including YouTube videos. Other applications I tested for sound still worked, including opera, xmms, vlc-qt4 and the chrome browser. After much searching, the suggested solution in various forums is to turn off Pulse Audio in the configuration. This I did. After rebuilding firefox, the sound worked again. For reference, here is the configuration I used, after turning off Pulse Audio. ALSA : on BUNDLED_CAIRO : on CANBERRA : off DBUS : on DEBUG : off DTRACE : on FFMPEG : on GCONF : off GNOMEUI: off INTEGER_SAMPLES: off LIBPROXY : off OPTIMIZED_CFLAGS: on PGO: off PROFILE: off PULSEAUDIO : off RUST : on SNDIO : off TEST : off ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
[exp - 103i386-default-build-as-user][www/firefox] Failed for firefox-53.0_2, 1 in configure
You are receiving this mail as a port that you maintain is failing to build on the FreeBSD package build server. Please investigate the failure and submit a PR to fix build. Maintainer: ge...@freebsd.org Last committer: jbe...@freebsd.org Ident: $FreeBSD: head/www/firefox/Makefile 438521 2017-04-14 15:19:30Z jbeich $ Log URL: http://package19.nyi.freebsd.org/data/103i386-default-build-as-user/438673/logs/firefox-53.0_2,1.log Build URL: http://package19.nyi.freebsd.org/build.html?mastername=103i386-default-build-as-user=438673 Log: >> Building www/firefox build started at Mon Apr 17 09:19:43 UTC 2017 port directory: /usr/ports/www/firefox building for: FreeBSD 103i386-default-build-as-user-job-03 10.3-RELEASE-p18 FreeBSD 10.3-RELEASE-p18 i386 maintained by: ge...@freebsd.org Makefile ident: $FreeBSD: head/www/firefox/Makefile 438521 2017-04-14 15:19:30Z jbeich $ Poudriere version: 3.1.17-9-gf49c6f78 Host OSVERSION: 1200028 Jail OSVERSION: 1003000 Job Id: 03 ---Begin Environment--- SHELL=/bin/csh UNAME_p=i386 UNAME_m=i386 OSVERSION=1003000 UNAME_v=FreeBSD 10.3-RELEASE-p18 UNAME_r=10.3-RELEASE-p18 BLOCKSIZE=K MAIL=/var/mail/root STATUS=1 SAVED_TERM= MASTERMNT=/poudriere/data/.m/103i386-default-build-as-user/ref UID=0 FORCE_PACKAGE=yes PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin POUDRIERE_BUILD_TYPE=bulk PKGNAME=firefox-53.0_2,1 OLDPWD=/ PWD=/poudriere/data/.m/103i386-default-build-as-user/ref/.p/pool MASTERNAME=103i386-default-build-as-user SCRIPTPREFIX=/usr/local/share/poudriere USER=root HOME=/root POUDRIERE_VERSION=3.1.17-9-gf49c6f78 SCRIPTPATH=/usr/local/share/poudriere/bulk.sh GID=0 LIBEXECPREFIX=/usr/local/libexec/poudriere LOCALBASE=/usr/local PACKAGE_BUILDING=yes POUDRIEREPATH=/usr/local/bin/poudriere ---End Environment--- ---Begin OPTIONS List--- ===> The following configuration options are available for firefox-53.0_2,1: BUNDLED_CAIRO=on: Use bundled fork of cairo-1.9.5 CANBERRA=off: Sound theme alerts DBUS=on: D-Bus IPC system support DEBUG=off: Build with debugging support DTRACE=on: Build with DTrace probes FFMPEG=on: FFmpeg support (WMA, AIFF, AC3, APE...) GCONF=off: GConf configuration backend support GNOMEUI=off: libgnomeui support module INTEGER_SAMPLES=off: Integer audio sample format LIBPROXY=off: Proxy support via libproxy OPTIMIZED_CFLAGS=on: Use extra compiler optimizations PGO=off: Use Profile-Guided Optimization PROFILE=off: Build with profiling support RUST=on: Build with components written in Rust language TEST=off: Build and/or run tests > Options available for the multi AUDIO: you have to choose at least one of them ALSA=on: ALSA audio architecture support PULSEAUDIO=on: PulseAudio sound server support SNDIO=off: Sndio audio support ===> Use 'make config' to modify these settings ---End OPTIONS List--- --CONFIGURE_ARGS-- --End CONFIGURE_ARGS-- --CONFIGURE_ENV-- MAKE=gmake ac_cv_path_PERL=/usr/local/bin/perl ac_cv_path_PERL_PATH=/usr/local/bin/perl PERL_USE_UNSAFE_INC=1 PKG_CONFIG=pkgconf PYTHON="/usr/local/bin/python2.7" XDG_DATA_HOME=/wrkdirs/usr/ports/www/firefox/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/firefox/work HOME=/wrkdirs/usr/ports/www/firefox/work TMPDIR="/tmp" SHELL=/bin/sh CONFIG_SHELL=/bin/sh CMAKE_PREFIX_PATH="/usr/local" --End CONFIGURE_ENV-- --MAKE_ENV-- PERL_USE_UNSAFE_INC=1 XDG_DATA_HOME=/wrkdirs/usr/ports/www/firefox/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/firefox/work HOME=/wrkdirs/usr/ports/www/firefox/work TMPDIR="/tmp" NO_PIE=yes WITHOUT_DEBUG_FILES=yes WITHOUT_KERNEL_SYMBOLS=yes SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local LOCALBASE=/usr/local LIBDIR="/usr/lib" CC="/usr/local/bin/clang36" CFLAGS="-O2 -pipe -O3 -DLIBICONV_PLUG -fstack-protector -isystem /usr/local/include -fno-strict-aliasing" CPP="/usr/local/bin/clang-cpp36" CPPFLAGS="-D_GLIBCXX_USE_C99 -D_GLIBCXX_USE_C99_MATH_TR1 -D_DECLARE_C99_LDBL_MATH -DLIBICONV_PLUG -isystem /usr/local/include" LDFLAGS=" -Wl,--as-needed -fstack-protector" LIBS="-lelf -L/usr/local/lib" CXX="/usr/local/bin/clang++36" CXXFLAGS="-O2 -pipe -O3 -DLIBICONV_PLUG -fstack-protector -isystem /usr/local/include -fno-strict-aliasing -DLIBICONV_PLUG -isystem /usr/local/include" MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install -m 555" BSD_INSTALL_LIB="install -m 0644" BSD_INSTAL L_SCRIPT="install -m 555" BSD_INSTALL_DATA="install -m 0644" BSD_INSTALL_MAN="install -m 444" --End MAKE_ENV-- --PLIST_SUB-- PYTHON_INCLUDEDIR=include/python2.7 PYTHON_LIBDIR=lib/python2.7 PYTHON_PLATFORM=freebsd10 PYTHON_PYOEXTENSION=pyo PYTHON_SITELIBDIR=lib/python2.7/site-packages PYTHON_SUFFIX=27 PYTHON_VER=2.7 PYTHON_VERSION=python2.7 PYTHON2="" PYTHON3="@comment " GTK2_VERSION="2.10.0" GTK3_VERSION="3.0.0" OSREL=10.3 PREFIX=%D LOCALBASE=/usr/local RESETPREFIX=/usr/local PORTDOCS="" PORTEXAMPLES="" LIB32DIR=lib
[Bug 218692] www/seamonkey vulnerabilities
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218692 Jan Beichchanged: What|Removed |Added Resolution|--- |Not A Bug Status|New |Closed --- Comment #1 from Jan Beich --- "pkg audit" reports vulnerabilities in the Gecko engine shared with Firefox. How many of those affect SeaMonkey is unclear but certainly not zero. Better ask upstream. https://lists.mozilla.org/listinfo/support-seamonkey -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: Firefox 53 options
ANwrites: > It seems version 53 removed the option for GTK2, is it still possible > to use a build option somewhere to maintain GTK2 style? No, it's being phased out[1]. If you can't use GTK3 for some reason make your voice heard by replying on upstream mailing list, file bugs or triage existing ones. www/firefox-esr still has GTK2 option. [1] https://www.mail-archive.com/dev-platform@lists.mozilla.org/msg20523.html ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"