From owner-freebsd-gnome@freebsd.org Sun Feb 26 08:28:12 2017 Return-Path: Delivered-To: freebsd-gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1696FCEEFA6 for ; Sun, 26 Feb 2017 08:28:12 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 03A78A6D for ; Sun, 26 Feb 2017 08:28:12 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 00621CEEFA5; Sun, 26 Feb 2017 08:28:12 +0000 (UTC) Delivered-To: gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F284DCEEFA4 for ; Sun, 26 Feb 2017 08:28:11 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D85CEA6C for ; Sun, 26 Feb 2017 08:28:11 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id v1Q8SBKq084094 for ; Sun, 26 Feb 2017 08:28:11 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v1Q8SBfL084093; Sun, 26 Feb 2017 08:28:11 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201702260828.v1Q8SBfL084093@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Sun, 26 Feb 2017 08:28:11 +0000 From: portscout@FreeBSD.org To: gnome@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2017 08:28:12 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/gnome@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ graphics/libgxps | 0.2.3.2 | 0.2.5 ------------------------------------------------+-----------------+------------ print/harfbuzz | 1.4.2 | 1.4.3 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-gnome@freebsd.org Sun Feb 26 21:00:26 2017 Return-Path: Delivered-To: freebsd-gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74E3FCEC6D3 for ; Sun, 26 Feb 2017 21:00:26 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 630598B9 for ; Sun, 26 Feb 2017 21:00:26 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6274ECEC6CC; Sun, 26 Feb 2017 21:00:26 +0000 (UTC) Delivered-To: gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 622B4CEC6CA for ; Sun, 26 Feb 2017 21:00:26 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 593A98B8 for ; Sun, 26 Feb 2017 21:00:26 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1QL01a4061275 for ; Sun, 26 Feb 2017 21:00:26 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201702262100.v1QL01a4061275@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: gnome@FreeBSD.org Subject: Problem reports for gnome@FreeBSD.org that need special attention Date: Sun, 26 Feb 2017 21:00:26 +0000 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2017 21:00:26 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 206197 | devel/dbus: help to identify & fix "Rejected send Open | 211071 | x11/gnome3: Spell checking doesn't work, missing New | 210718 | mail/geary: update to 0.11.1 New | 213498 | devel/libnotify: Update to 0.7.7 Open | 202269 | [patch] sysutils/consolekit update to 1.0.0 Open | 202006 | textproc/libxml2: xml2-config --libs output lists Open | 207243 | [exp-run] devel/glib20 and friends c++ bindings u Open | 202982 | Installation of gnome related ports (xfce, vbox, Open | 188840 | textproc/link-grammar: Update to latest (request) In Progress | 211201 | print/freetype2: update to 2.7, add V40 code New | 209870 | multiple ports: Building manpages with xsltproc - 11 problems total for which you should take action. From owner-freebsd-gnome@freebsd.org Tue Feb 28 07:39:42 2017 Return-Path: Delivered-To: freebsd-gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7352DCF10E4 for ; Tue, 28 Feb 2017 07:39:42 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 60B24CEC for ; Tue, 28 Feb 2017 07:39:42 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5D47FCF10E3; Tue, 28 Feb 2017 07:39:42 +0000 (UTC) Delivered-To: gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B5ECCF10E2 for ; Tue, 28 Feb 2017 07:39:42 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3985ACEA for ; Tue, 28 Feb 2017 07:39:42 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id v1S7dgSJ077461 for ; Tue, 28 Feb 2017 07:39:42 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v1S7dgqX077460; Tue, 28 Feb 2017 07:39:42 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201702280739.v1S7dgqX077460@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Tue, 28 Feb 2017 07:39:42 +0000 From: portscout@FreeBSD.org To: gnome@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2017 07:39:42 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/gnome@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ lang/gjs | 1.44.0 | 1.47.91 ------------------------------------------------+-----------------+------------ x11-toolkits/pango | 1.38.0 | 1.40.4 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-gnome@freebsd.org Wed Mar 1 07:49:16 2017 Return-Path: Delivered-To: freebsd-gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E3AACF29BE for ; Wed, 1 Mar 2017 07:49:16 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1B51593D for ; Wed, 1 Mar 2017 07:49:16 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1AABCCF29BD; Wed, 1 Mar 2017 07:49:16 +0000 (UTC) Delivered-To: gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A55DCF29BC for ; Wed, 1 Mar 2017 07:49:16 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0D96493C for ; Wed, 1 Mar 2017 07:49:16 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id v217nFPm061581 for ; Wed, 1 Mar 2017 07:49:15 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v217nFK3061580; Wed, 1 Mar 2017 07:49:15 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201703010749.v217nFK3061580@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Wed, 1 Mar 2017 07:49:15 +0000 From: portscout@FreeBSD.org To: gnome@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2017 07:49:16 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/gnome@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ archivers/file-roller | 3.20.3 | 3.22.3 ------------------------------------------------+-----------------+------------ graphics/gegl3 | 0.3.4 | 0.3.14 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-gnome@freebsd.org Wed Mar 1 15:48:35 2017 Return-Path: Delivered-To: freebsd-gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41B23CF2A65 for ; Wed, 1 Mar 2017 15:48:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2A42C67D for ; Wed, 1 Mar 2017 15:48:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 29961CF2A64; Wed, 1 Mar 2017 15:48:35 +0000 (UTC) Delivered-To: gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 293BFCF2A63 for ; Wed, 1 Mar 2017 15:48:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 17E8067A for ; Wed, 1 Mar 2017 15:48:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v21FmXJd053846 for ; Wed, 1 Mar 2017 15:48:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 202982] Installation of gnome related ports (xfce, vbox, abiword, gnumeric) cause CONFLICT: install of python3-3_3 conflicts with python2-2_3 Date: Wed, 01 Mar 2017 15:48:33 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: greinbold@nosheep.fr X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: python@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2017 15:48:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D202982 --- Comment #20 from Gr=C3=A9gory --- Same issue here: pkg-static: python3-3_3 conflicts with python2-2_3 (instal= ls files into the same place). Problematic file: /usr/local/bin/2to3-2 Informations: - FreeBSD 11.0 x64 - ports collection updated this day - issue appear when I try to compile xfce4 (In reply to Jon Chappelow from comment #19) I tried portmaster -iv lang/python3 and two tasks was completed: - upgrade pkg from 9 to 10 - install python3 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-gnome@freebsd.org Thu Mar 2 12:49:57 2017 Return-Path: Delivered-To: freebsd-gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED6B4CF220E for ; Thu, 2 Mar 2017 12:49:57 +0000 (UTC) (envelope-from andy.silva@snsresearchreports.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id CCFC8F98 for ; Thu, 2 Mar 2017 12:49:57 +0000 (UTC) (envelope-from andy.silva@snsresearchreports.com) Received: by mailman.ysv.freebsd.org (Postfix) id C92A0CF220D; Thu, 2 Mar 2017 12:49:57 +0000 (UTC) Delivered-To: gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C89D2CF220B for ; Thu, 2 Mar 2017 12:49:57 +0000 (UTC) (envelope-from andy.silva@snsresearchreports.com) Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 87B70F97 for ; Thu, 2 Mar 2017 12:49:57 +0000 (UTC) (envelope-from andy.silva@snsresearchreports.com) X-MSFBL: gVSGn7VYcTsUSlMMlDO5l6nXsyr21AToMYr+amEkROU=|eyJnIjoiU25zdGVsZWN vbV9kZWRpY2F0ZWRfcG9vbCIsInIiOiJnbm9tZUBmcmVlYnNkLm9yZyIsImIiOiI 3NF85MV84NV8yMzgifQ== Received: from [192.168.80.22] ([192.168.80.22:58370] helo=rs-ord-mta02-in2.smtp.com) by rs-ord-mta01-out2.smtp.com (envelope-from ) (ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP id 7C/7D-12339-BE418B85; Thu, 02 Mar 2017 12:49:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; d=snsreports.com; s=snskey; c=relaxed/simple; q=dns/txt; i=@snsreports.com; t=1488458987; h=From:Subject:To:Date:MIME-Version:Content-Type; bh=U0ZfyFicKFkjdSjZ+vG5SaU0OHsve5vkFghlwzxY4Fc=; b=fRNWzka4D9jHNNIZCHa7yCJ2daxhjidL/lUmg7uuC7k5ojSBbTPwSO7ojpdd7l9z CPtuC4+n0CZYXhpkn4v1iSWpTN6lR+hyxq7imgqfluFIyqPy2v6t/ZtlbSw1AZN2 fDfv7matood6dEMtxjdLGXGSEr0SPWT2wBxL4L6HRfI1IWGYpcEm2b/xLNqr0U6h nQYymXu3DNswPgu1DE0KqXVkQXLI6GuW3zerL0LkvGeyYFtBOHgdDy5WBxReTWv7 gV8/aP/MJcgf5bnrbanqSPgME+8T+Gb7EGSpJ1Ahmudnazc8LId+PTDtE8HsB0KA nLXGSlZ1UFIVbB2FRYI4RA==; Received: from [70.79.69.78] ([70.79.69.78:44748] helo=S01061c1b689e28c7.vc.shawcable.net) by rs-ord-mta02-in2.smtp.com (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id 6B/35-24837-BE418B85; Thu, 02 Mar 2017 12:49:47 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snsresearchreports.com To: gnome@freebsd.org Subject: ProSe (Proximity Services) for LTE & 5G Networks: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Thu, 2 Mar 2017 04:49:42 -0800 Message-ID: <6328393987704317232053@Ankur> X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation. X-SMTPCOM-Tracking-Number: 476e2d7a-9218-4952-a3dd-d872ed63b335 X-SMTPCOM-Sender-ID: 6008902 Feedback-ID: 6008902:SMTPCOM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 12:49:58 -0000 ProSe (Proximity Services) for LTE & 5G Networks: 2017 =96 2030 =96 Opportu= nities, Challenges, Strategies & Forecasts (Report) Hello Let me offer you the latest SNS Research report to you and your team, "ProS= e (Proximity Services) for LTE & 5G Networks: 2017 =96 2030 =96 Opportuniti= es, Challenges, Strategies & Forecasts" Below is the report highlight and i= f you like I can send you sample pages for your details inside. =20 By the end of 2025, SNS Research estimates that mobile operators can pocket= as much $17 Billion in ProSe based annual service revenue. Up to 55% of th= is revenue figure will be attributable to proximity advertising. Report Information: Release Date: Jan 2017 Number of Pages: 127 Number of Tables and Figures: 84 Key Questions Answered: How big is the ProSe opportunity=3F What trends, challenges and barriers are influencing its growth=3F How will the ecosystem evolve by segment and region=3F What will the market size be in 2020 and at what rate will it grow=3F How big is the ProSe service revenue opportunity for mobile operators=3F How will ProSe help public safety agencies in replacing legacy LMR systems = with LTE and 5G networks=3F How will consolidation in the chipset ecosystem affect the adoption of ProS= e=3F How can ProSe deliver localized V2X (Vehicle-to-Everything) connectivity=3F What strategies should chipset suppliers, device OEMs and mobile operators = adopt to remain competitive=3F Key Findings: The report has the following key findings: In comparison to existing D2D and proximity networking technologies, ProSe = offers several distinct benefits including but not limited to better scalab= ility, manageability, privacy, security and battery-efficiency. At present, efforts to commercialize ProSe are being spearheaded by the pub= lic safety and critical communications industry. The ongoing transition fro= m legacy LMR systems to LTE networks is expected to trigger the very first= investments in ProSe-enabled devices, as direct communication between devi= ces is an essential requirement for users in this domain. In the commercial area, mobile operators can leverage ProSe to offer a rang= e of B2B, B2B2C and B2C services that rely on proximity including advertisi= ng, social networking, gaming, relaying traffic for wearables and V2X (Vehi= cle-to-Everything) connectivity. By the end of 2025, SNS Research estimates that mobile operators can pocket= as much $17 Billion in ProSe based annual service revenue. Up to 55% of th= is revenue figure will be attributable to proximity advertising. =20 The report covers the following topics: =20 ProSe technology Market drivers and barriers Sidelink air interface and spectrum bands ProSe discovery and direct communication services ProSe coverage scenarios and modes of operation ProSe reference architecture, key functional elements and interfaces 3GPP standardization efforts for ProSe Competing D2D and proximity networking technologies Key applications, business models and monetization strategies Case studies of pre-commercial ProSe engagements Industry roadmap and value chain Strategic recommendations for key ecosystem players including chipset suppl= iers, device OEMs, infrastructure vendors, public safety agencies and mobil= e operators Market analysis and forecasts from 2018 till 2030 Forecast Segmentation: Market forecasts and historical revenue figures are provided for each of th= e following 5 submarkets and their 23 use case categories: ProSe Device Shipments & Revenue Submarkets Public Safety & Critical Communications Commercial Sector Form Factor Segmentation=20 Smartphones Tablets Wearables Vehicle Mount Devices V2X Devices Other Devices Regional Markets Asia Pacific Eastern Europe Middle East & Africa Latin & Central America North America Western Europe ProSe Based Mobile Operator Service Revenue Submarkets Advertising Social Networking V2X Connectivity Public Safety & Critical Communications Other Applications Additional forecasts are provided for the following: IoT connections for mHealth applications mHealth centric wearable device shipments Mobile video calling users Annual throughput of mobile network data traffic Smartphone, feature phone, tablet, desktop PC and notebook shipments Mobile network subscriptions by region Cost saving potential of mHealth by region Big Data & analytics technology investments in the healthcare sector =20 Report Pricing: =20 Single User License: USD 2,500 Company Wide License: USD 3,500 =20 Ordering Process: =20 Please provide the following information: Report Title - ProSe for LTE & 5G Network: 2017-2030 Report License - (Single User/Company Wide) Name - Email - Job Title - Company - Invoice Address - Please contact me if you have any questions, or wish to purchase a copy. Ta= ble of contents and List of figures mentioned in report are given below for= more inside. I look forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive andy.silva@snsresearchreports.com =20 _________________________________________________________________________ Table of Contents (page number): =20 1 Chapter 1: Introduction 1.1 Executive Summary 1.2 Topics Covered 1.3 Forecast Segmentation 1.4 Key Questions Answered 1.5 Key Findings 1.6 Methodology 1.7 Target Audience 1.8 Companies & Organizations Mentioned =20 2 Chapter 2: An Overview of ProSe 2.1 What is D2D (Device-to-Device) Technology=3F 2.2 ProSe (Proximity Services) for 3GPP Networks 2.3 ProSe Service Classification 2.3.1 ProSe Discovery 2.3.2 ProSe Direct Communication 2.4 ProSe Coverage Scenarios 2.4.1 In-Coverage 2.4.2 Partial Coverage 2.4.3 Out-of-Coverage 2.5 ProSe Modes of Direct Communication 2.5.1 Unicast 2.5.2 One-to-Many: Group Communication 2.5.3 One-to-All: Broadcast Communication 2.6 ProSe Modes of Discovery 2.6.1 Restricted Discovery 2.6.2 Open Discovery 2.7 Competing Technologies 2.7.1 P25, TETRA & Conventional LMR Systems 2.7.2 Wi-Fi 2.7.2.1 Wi-Fi Direct 2.7.2.2 Wi-Fi Aware/NAN (Neighbor Awareness Networking) 2.7.2.3 Ad-Hoc Mode D2D Connectivity & TDLS (Tunneled Direct Link Setup) 2.7.2.4 WAVE (Wireless Access in Vehicular Environments): IEEE 802.11p 2.7.3 Bluetooth 2.7.3.1 Classic Bluetooth 2.7.3.2 Bluetooth High Speed 2.7.3.3 BLE (Bluetooth Low Energy) 2.7.3.4 Bluetooth 5 Enhancements 2.7.4 Apple's iBeacon 2.7.5 ZigBee 2.7.6 GPS 2.7.7 Others 2.8 Market Growth Drivers 2.8.1 Adoption of LTE for Public Safety & Critical Communications 2.8.2 Extending Wide Area Connectivity to IoT Devices & Accessories 2.8.3 Better Scalability & Coverage Range Than Competing Technologies 2.8.4 New Revenue Streams & ARPU Growth for Mobile Operators 2.8.5 Enhanced Manageability, Privacy & Security 2.8.6 Alleviating Network Congestion & Improving Spectrum Utilization 2.9 Market Barriers 2.9.1 Potential Interference 2.9.2 Achieving UE Battery Efficiency 2.9.3 Impact on Network Resources 2.9.4 Dependency on New Chipsets & Devices 2.9.5 Interoperability & Other Technical Challenges =20 3 Chapter 3: ProSe Technology & Standardization 3.1 Sidelink Air Interface 3.1.1 Use of Uplink Resources 3.1.2 Transmission Scheme 3.1.3 Frequency Bands & Channel Bandwidths 3.1.4 New Physical, Transport & Logical Channels 3.1.4.1 Physical Channels 3.1.4.2 Transport Channels 3.1.4.3 Logical Channels 3.1.5 Synchronization Signals 3.1.6 Alternative Wi-Fi Direct Communication Path 3.2 Key Operational Capabilities of ProSe 3.2.1 Service Authorization & Provisioning 3.2.2 ProSe Discovery 3.2.2.1 Direct Discovery 3.2.2.2 Specific Direct Discovery Features for Public Safety 3.2.2.3 EPC-Level Discovery 3.2.2.4 EPC Support for Wi-Fi Direct Communication 3.2.3 ProSe Direct Communication 3.2.3.1 One-to-One Direct Communication 3.2.3.2 One-to-Many Direct Communication 3.2.4 UE-to-Network Relay 3.3 ProSe Reference Architecture, Key Functional Elements & Interfaces 3.3.1 ProSe-Enabled Devices & Applications 3.3.2 ProSe AS (Application Server) 3.3.3 ProSe Function 3.3.3.1 DPF (Direct Provisioning Function) 3.3.3.2 Direct Discovery Name Management Function 3.3.3.3 EPC-Level Discovery ProSe Function 3.3.4 ProSe Proxy 3.3.5 ProSe Key Management Function 3.3.6 MME (Mobility Management Entity) 3.3.7 P-GW (Packet Data Network Gateway) 3.3.8 S-GW (Serving Gateway) 3.3.9 HSS (Home Subscriber Server) 3.3.10 SLP (Secure User Plane Location Platform) 3.3.11 S-GW (Serving Gateway) 3.3.12 Interfaces 3.3.12.1 PC1 3.3.12.2 PC2 3.3.12.3 PC3 3.3.12.4 PC4a 3.3.12.5 PC4b 3.3.12.6 PC5 (Sidelink) 3.3.12.7 PC6 3.3.12.8 PC7 3.3.12.9 PC8 3.3.12.10 S6a 3.3.12.11 S1-MME 3.4 3GPP Standardization for ProSe 3.4.1 Release 12 3.4.2 Release 13 3.4.3 Release 14 & Beyond =20 4 Chapter 4: ProSe Applications, Business Models & Case Studies 4.1 Key Applications of ProSe 4.1.1 Public Safety & Critical Communications 4.1.1.1 Direct Communication for Coverage Extension 4.1.1.2 Direct Communication within Network Coverage 4.1.1.3 Infrastructure Failure & Emergency Situations 4.1.1.4 Additional Capacity for Incident Response & Special Events 4.1.1.5 Discovery Services for Disaster Relief 4.1.2 Commercial Applications 4.1.2.1 Proximity Advertising 4.1.2.2 Localized Social Networking 4.1.2.3 Online & Real-World Gaming 4.1.2.4 Enabling the Sharing Economy 4.1.2.5 Mobile Relaying & Network Sharing 4.1.2.6 Wide Area Connectivity for the IoT & Wearables 4.1.2.7 Local Data Transfer 4.1.2.8 Other Applications 4.1.3 Cellular V2X (Vehicle-to-Everything) Connectivity 4.2 Business Models: How Can Mobile Operators Monetize ProSe=3F 4.2.1 B2C: Premium Charge for ProSe Capabilities 4.2.2 B2B: D2D Services for Public Safety Agencies & Other Enterprises 4.2.3 B2B2C: Stacking Consumer Applications over ProSe 4.3 Case Studies of Pre-Commercial Engagements 4.3.1 Qualcomm: Accelerating Ecosystem Development with LTE Direct 4.3.2 DT (Deutsche Telekom): First Pre-Commercial Mobile Operator Trial for= ProSe 4.3.3 KT Corporation: Emergency Services, Social Networking & Personalized = Advertising with ProSe 4.3.4 TCL Communication: ProSe-Enabled Device Prototype Demonstration 4.3.5 NTT DoCoMo: Empowering the Sharing Economy with ProSe 4.3.6 M87: Expanding the Reach of Mobile Networks with ProSe 4.3.7 Compass.To: Successfully Conducting the First ProSe Trial in China 4.3.8 Others =20 5 Chapter 5: ProSe Industry Roadmap & Value Chain 5.1 Industry Roadmap 5.1.1 2017 =96 2020: Initial Adoption Driven by Public Safety LTE Networks 5.1.2 2020 =96 2025: Growing Focus on Consumer Applications 5.1.3 2025 =96 2030: Targeting Cellular V2X Connectivity 5.2 Value Chain 5.2.1 Chipset Suppliers 5.2.2 ProSe-Enabled Device OEMs 5.2.3 ProSe Infrastructure Vendors 5.2.4 Mobile Operators 5.2.5 Public Safety & Critical Communications Agencies 5.2.6 Commercial Enterprises 5.2.7 App Developers & Content Providers 5.2.8 Consumers 5.2.9 Test, Measurement & Performance Specialists =20 6 Chapter 6: Market Analysis & Forecasts 6.1 Global Outlook on ProSe-Enabled Devices 6.2 Submarket Segmentation 6.2.1 Public Safety & Critical Communications 6.2.2 Commercial Sector 6.3 Form Factor Segmentation 6.3.1 Public Safety & Critical Communications 6.3.1.1 Smartphones 6.3.1.2 Vehicle Mount Devices 6.3.1.3 Other Devices 6.3.2 Commercial Sector 6.3.2.1 Smartphones 6.3.2.2 Tablets 6.3.2.3 Wearables 6.3.2.4 V2X Devices 6.3.2.5 Other Devices 6.4 Regional Segmentation 6.4.1 Public Safety & Critical Communications 6.4.2 Commercial Sector 6.5 Asia Pacific 6.5.1 Public Safety & Critical Communications 6.5.2 Commercial Sector 6.6 Eastern Europe 6.6.1 Public Safety & Critical Communications 6.6.2 Commercial Sector 6.7 Latin & Central America 6.7.1 Public Safety & Critical Communications 6.7.2 Commercial Sector 6.8 Middle East & Africa 6.8.1 Public Safety & Critical Communications 6.8.2 Commercial Sector 6.9 North America 6.9.1 Public Safety & Critical Communications 6.9.2 Commercial Sector 6.10 Western Europe 6.10.1 Public Safety & Critical Communications 6.10.2 Commercial Sector =20 7 Chapter 7: Conclusion & Strategic Recommendations 7.1 Why is the Market Poised to Grow=3F 7.2 Public Safety LTE Engagements to Trigger Initial Investments 7.3 Synergies with IOPS (Isolated E-UTRAN Operation) 7.4 Interim Solutions to Fulfill Public Safety ProSe Requirements 7.5 How Big is the ProSe Service Revenue Opportunity for Mobile Operators=3F 7.6 Enhancements to Support IoT & Wearables 7.7 Consolidation in the Chipset Ecosystem: Implications for ProSe 7.8 Potential Impact on the V2X Sector 7.9 Strategic Recommendations 7.9.1 Recommendations for Chipset, Device & Infrastructure Suppliers 7.9.2 Recommendations for Mobile Operators 7.9.3 Recommendations for Public Safety & Critical Communications Agencies =20 List of Figures (page number) =20 Figure 1: Example Application Scenarios for D2D Technology Figure 2: Sidelink Air Interface for ProSe Figure 3: Use Cases & Service Scenarios for ProSe Figure 4: Key Differences Between LTE Uplink and Sidelink Figure 5: Operating Bands for ProSe Figure 6: ProSe Direct Discovery Channel Bandwidth Figure 7: ProSe Direct Communication Channel Bandwidth Figure 8: Physical, Transport & Logical Channels for Sidelink Figure 9: Architecture for ProSe UE-to-Network Relay Functionality Figure 10: ProSe Reference Architecture Figure 11: ProSe Industry Roadmap Figure 12: ProSe Value Chain Figure 13: Global ProSe-Enabled Device Shipments: 2018 =96 2030 (Millions o= f Units) Figure 14: Global ProSe-Enabled Device Shipment Revenue: 2018 =96 2030 ($ B= illion) Figure 15: Global ProSe-Enabled Device Shipments by Submarket: 2018 =96 203= 0 (Millions of Units) Figure 16: Global ProSe-Enabled Device Shipment Revenue by Submarket: 2018 = =96 2030 ($ Billion) Figure 17: Global ProSe-Enabled Device Shipments in the Public Safety & Cri= tical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 18: Global ProSe-Enabled Device Shipment Revenue in the Public Safet= y & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 19: Global ProSe-Enabled Device Shipments in the Commercial Sector: = 2018 =96 2030 (Millions of Units) Figure 20: Global ProSe-Enabled Device Shipment Revenue in the Commercial S= ector: 2018 =96 2030 ($ Billion) Figure 21: Global ProSe-Enabled Device Shipments in the Public Safety & Cri= tical Communications Sector, by Form Factor: 2018 =96 2030 (Thousands of Un= its) Figure 22: Global ProSe-Enabled Device Shipment Revenue in the Public Safet= y & Critical Communications Sector, by Form Factor: 2018 =96 2030 ($ Millio= n) Figure 23: Global ProSe-Enabled Smartphone Shipments in the Public Safety &= Critical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 24: Global ProSe-Enabled Smartphone Shipment Revenue in the Public S= afety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 25: Global ProSe-Enabled Vehicle Mount Device Shipments in the Publi= c Safety & Critical Communications Sector: 2018 =96 2030 (Thousands of Unit= s) Figure 26: Global ProSe-Enabled Vehicle Mount Device Shipment Revenue in th= e Public Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 27: Global ProSe-Enabled Other Device Shipments in the Public Safety= & Critical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 28: Global ProSe-Enabled Other Device Shipment Revenue in the Public= Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 29: Global ProSe-Enabled Device Shipments in the Commercial Sector, = by Form Factor: 2018 =96 2030 (Millions of Units) Figure 30: Global ProSe-Enabled Device Shipment Revenue in the Commercial S= ector, by Form Factor: 2018 =96 2030 ($ Billion) Figure 31: Global ProSe-Enabled Smartphone Shipments in the Commercial Sect= or: 2018 =96 2030 (Millions of Units) Figure 32: Global ProSe-Enabled Smartphone Shipment Revenue in the Commerci= al Sector: 2018 =96 2030 ($ Billion) Figure 33: Global ProSe-Enabled Tablet Shipments in the Commercial Sector: = 2018 =96 2030 (Millions of Units) Figure 34: Global ProSe-Enabled Tablet Shipment Revenue in the Commercial S= ector: 2018 =96 2030 ($ Billion) Figure 35: Global ProSe-Enabled Wearable Device Shipments in the Commercial= Sector: 2018 =96 2030 (Millions of Units) Figure 36: Global ProSe-Enabled Wearable Device Shipment Revenue in the Com= mercial Sector: 2018 =96 2030 ($ Billion) Figure 37: Global ProSe-Enabled V2X Device Shipments in the Commercial Sect= or: 2018 =96 2030 (Millions of Units) Figure 38: Global ProSe-Enabled V2X Device Shipment Revenue in the Commerci= al Sector: 2018 =96 2030 ($ Billion) Figure 39: Global ProSe-Enabled Other Device Shipments in the Commercial Se= ctor: 2018 =96 2030 (Millions of Units) Figure 40: Global ProSe-Enabled Other Device Shipment Revenue in the Commer= cial Sector: 2018 =96 2030 ($ Billion) Figure 41: ProSe-Enabled Device Shipments by Region: 2018 =96 2030 (Million= s of Units) Figure 42: ProSe-Enabled Device Shipment Revenue by Region: 2018 =96 2030 (= $ Billion) Figure 43: ProSe-Enabled Device Shipments in the Public Safety & Critical C= ommunications Sector, by Region: 2018 =96 2030 (Thousands of Units) Figure 44: ProSe-Enabled Device Shipment Revenue in the Public Safety & Cri= tical Communications Sector, by Region: 2018 =96 2030 ($ Million) Figure 45: ProSe-Enabled Device Shipments in the Commercial Sector, by Regi= on: 2018 =96 2030 (Millions of Units) Figure 46: ProSe-Enabled Device Shipment Revenue in the Commercial Sector, = by Region: 2018 =96 2030 ($ Billion) Figure 47: Asia Pacific ProSe-Enabled Device Shipments: 2018 =96 2030 (Mill= ions of Units) Figure 48: Asia Pacific ProSe-Enabled Device Shipment Revenue: 2018 =96 203= 0 ($ Billion) Figure 49: Asia Pacific ProSe-Enabled Device Shipments in the Public Safety= & Critical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 50: Asia Pacific ProSe-Enabled Device Shipment Revenue in the Public= Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 51: Asia Pacific ProSe-Enabled Device Shipments in the Commercial Se= ctor: 2018 =96 2030 (Millions of Units) Figure 52: Asia Pacific ProSe-Enabled Device Shipment Revenue in the Commer= cial Sector: 2018 =96 2030 ($ Billion) Figure 53: Eastern Europe ProSe-Enabled Device Shipments: 2018 =96 2030 (Mi= llions of Units) Figure 54: Eastern Europe ProSe-Enabled Device Shipment Revenue: 2018 =96 2= 030 ($ Billion) Figure 55: Eastern Europe ProSe-Enabled Device Shipments in the Public Safe= ty & Critical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 56: Eastern Europe ProSe-Enabled Device Shipment Revenue in the Publ= ic Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 57: Eastern Europe ProSe-Enabled Device Shipments in the Commercial = Sector: 2018 =96 2030 (Millions of Units) Figure 58: Eastern Europe ProSe-Enabled Device Shipment Revenue in the Comm= ercial Sector: 2018 =96 2030 ($ Billion) Figure 59: Latin & Central America ProSe-Enabled Device Shipments: 2018 =96= 2030 (Millions of Units) Figure 60: Latin & Central America ProSe-Enabled Device Shipment Revenue: 2= 018 =96 2030 ($ Billion) Figure 61: Latin & Central America ProSe-Enabled Device Shipments in the Pu= blic Safety & Critical Communications Sector: 2018 =96 2030 (Thousands of U= nits) Figure 62: Latin & Central America ProSe-Enabled Device Shipment Revenue in= the Public Safety & Critical Communications Sector: 2018 =96 2030 ($ Milli= on) Figure 63: Latin & Central America ProSe-Enabled Device Shipments in the Co= mmercial Sector: 2018 =96 2030 (Millions of Units) Figure 64: Latin & Central America ProSe-Enabled Device Shipment Revenue in= the Commercial Sector: 2018 =96 2030 ($ Billion) Figure 65: Middle East & Africa ProSe-Enabled Device Shipments: 2018 =96 20= 30 (Millions of Units) Figure 66: Middle East & Africa ProSe-Enabled Device Shipment Revenue: 2018= =96 2030 ($ Billion) Figure 67: Middle East & Africa ProSe-Enabled Device Shipments in the Publi= c Safety & Critical Communications Sector: 2018 =96 2030 (Thousands of Unit= s) Figure 68: Middle East & Africa ProSe-Enabled Device Shipment Revenue in th= e Public Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 69: Middle East & Africa ProSe-Enabled Device Shipments in the Comme= rcial Sector: 2018 =96 2030 (Millions of Units) Figure 70: Middle East & Africa ProSe-Enabled Device Shipment Revenue in th= e Commercial Sector: 2018 =96 2030 ($ Billion) Figure 71: North America ProSe-Enabled Device Shipments: 2018 =96 2030 (Mil= lions of Units) Figure 72: North America ProSe-Enabled Device Shipment Revenue: 2018 =96 20= 30 ($ Billion) Figure 73: North America ProSe-Enabled Device Shipments in the Public Safet= y & Critical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 74: North America ProSe-Enabled Device Shipment Revenue in the Publi= c Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 75: North America ProSe-Enabled Device Shipments in the Commercial S= ector: 2018 =96 2030 (Millions of Units) Figure 76: North America ProSe-Enabled Device Shipment Revenue in the Comme= rcial Sector: 2018 =96 2030 ($ Billion) Figure 77: Western Europe ProSe-Enabled Device Shipments: 2018 =96 2030 (Mi= llions of Units) Figure 78: Western Europe ProSe-Enabled Device Shipment Revenue: 2018 =96 2= 030 ($ Billion) Figure 79: Western Europe ProSe-Enabled Device Shipments in the Public Safe= ty & Critical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 80: Western Europe ProSe-Enabled Device Shipment Revenue in the Publ= ic Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 81: Western Europe ProSe-Enabled Device Shipments in the Commercial = Sector: 2018 =96 2030 (Millions of Units) Figure 82: Western Europe ProSe-Enabled Device Shipment Revenue in the Comm= ercial Sector: 2018 =96 2030 ($ Billion) Figure 83: Global Installed Base of ProSe-Enabled Devices by Submarket: 201= 8 =96 2030 (Millions of Units) Figure 84: Global ProSe Based Mobile Operator Service Revenue by Applicatio= n: 2018 =96 2030 ($ Billion) =20 Thank you once again and looking forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive =20 =20 To unsubscribe please send an email with unsubscribe in the subject line to= : remove@snsreports.com =20 From owner-freebsd-gnome@freebsd.org Fri Mar 3 08:02:24 2017 Return-Path: Delivered-To: freebsd-gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99947CF6363 for ; Fri, 3 Mar 2017 08:02:24 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 871721806 for ; Fri, 3 Mar 2017 08:02:24 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 866ACCF6362; Fri, 3 Mar 2017 08:02:24 +0000 (UTC) Delivered-To: gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8465ACF6361 for ; Fri, 3 Mar 2017 08:02:24 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6D2981805 for ; Fri, 3 Mar 2017 08:02:24 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id v2382ORT040999 for ; Fri, 3 Mar 2017 08:02:24 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v2382OYE040998; Fri, 3 Mar 2017 08:02:24 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201703030802.v2382OYE040998@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Fri, 3 Mar 2017 08:02:24 +0000 From: portscout@FreeBSD.org To: gnome@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2017 08:02:24 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/gnome@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ lang/vala | 0.30.2 | 0.34.5 ------------------------------------------------+-----------------+------------ x11/gdm | 3.16.4 | 3.22.2 ------------------------------------------------+-----------------+------------ x11-themes/adwaita-icon-theme | 3.18.0 | 3.23.91.1 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-gnome@freebsd.org Sat Mar 4 18:12:17 2017 Return-Path: Delivered-To: freebsd-gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE452CF8026 for ; Sat, 4 Mar 2017 18:12:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B7E281485 for ; Sat, 4 Mar 2017 18:12:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B7307CF8025; Sat, 4 Mar 2017 18:12:17 +0000 (UTC) Delivered-To: gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6D17CF8024 for ; Sat, 4 Mar 2017 18:12:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A6A461484 for ; Sat, 4 Mar 2017 18:12:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v24ICG9P020522 for ; Sat, 4 Mar 2017 18:12:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 217127] x11-wm/marco does not build Date: Sat, 04 Mar 2017 18:12:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: citrin+pr@citrin.ru X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: gnome@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Mar 2017 18:12:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217127 Anton Yuzhaninov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |citrin+pr@citrin.ru --- Comment #3 from Anton Yuzhaninov --- Please check output of: pkg-config --atleast-version 1.2.0 pangoxft ; echo $? command on a build box. If pangoxft is not found, check if file /usr/local/libdata/pkgconfig/pangoxft.pc is installed (as part of pango por= t). --=20 You are receiving this mail because: You are the assignee for the bug.=