I get the same segmentation fault when I try to launch the appcafe also in this new release. <br><br><div class="gmail_quote">On Sat, Feb 16, 2013 at 11:54 AM, Ira Taylor <span dir="ltr"><<a href="mailto:i.taylor1@verizon.net" target="_blank">i.taylor1@verizon.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Monday, February 04, 2013 03:01:20 PM Kris Moore wrote:<br>
</div><div><div class="h5">> Developers & Testers,<br>
><br>
> If you've been following the trac commit list with any regularity,<br>
> you've seen a lot of commits go by in the past months, all having to do<br>
> with pkgng, and a lot of internal churn to how we do our updates and<br>
> such. I've written an article for the upcoming BSD Magazine detailing<br>
> some of the reasons for this, and the "new direction" we are taking with<br>
> regard to PC-BSD releases, but I also want to post here to give<br>
> everybody a heads up.<br>
><br>
> First of all, I want to let you know, that I've personally not been<br>
> satisfied with the frequency of PC-BSD releases and updates. With us<br>
> tracking the upstream FreeBSD releases, it has really tied our hands<br>
> getting new releases out to the public. The past couple of releases had<br>
> a delay of almost a year between them, which is WAY too long in my<br>
> opinion. To further compound the problem, our build system wasn't<br>
> designed to do frequent updates of packages and our utilities, which<br>
> made getting updates out to the community a long and tedious process.<br>
> This is all going to change. What we are looking at going to now is more<br>
> of a "Rolling-Release" model, first for our utilities & system packages,<br>
> and eventually for the FreeBSD base itself.<br>
><br>
> So what benefits will this change bring? Well, for starters, we will now<br>
> be able to quickly get new features and bugfixes in our core utilities<br>
> out to PC-BSD & TrueOS users. Instead of having to wait for the next<br>
> point release, or some specific targeted bugfix, we can get you running<br>
> new features in a timely manner. In addition to the PC-BSD utilities, we<br>
> will also be able to keep your system packages (I.E. any FreeBSD binary<br>
> package) updated and in sync with the ports tree. This means when the<br>
> next KDE release hits, or NVIDIA driver, apache, etc, we can now make<br>
it<br>
> available to you within a matter of a few days.<br>
><br>
> To facilitate all this new rolling-release-goodness, I've been neck-deep<br>
> in converting our build framework into heavily using pkgng. Even all of<br>
> our PC-BSD utilities and system-modifications will now be distributed as<br>
> a pkgng package. What this means is not only do you get access to<br>
quick<br>
> updates, but it'll be possible for the first time to take a vanilla<br>
> FreeBSD system, switch to our pkgng repo, and turn your system into a<br>
> PC-BSD or TrueOS box. And this will not be some partial repository, the<br>
> plan is to offer a *complete* binary package repository, so if you now<br>
> want to install package X,Y, or Z you can do so without ever having to<br>
> touch the ports tree or compile by hand. PBI's will not be affected, so<br>
> you can run either depending upon personal preference. Plus this keeps<br>
> us independent from whats happening upstream with FreeBSD<br>
packages.<br>
><br>
> As for the base system, I am also looking to set us up running our own<br>
> "freebsd-update" server. This will allow us to create and run two<br>
> additional "branches" of PC-BSD, based upon FreeBSD -STABLE and<br>
> -CURRENT. This is a bit farther out, but I'm already moving bits and<br>
> pieces around to make this happen. This means when you go to the PC-<br>
BSD<br>
> website, you will now be able to download from three sets of images,<br>
> -RELEASE, -STABLE, -CURRENT, and these ISO's will be frequently<br>
updated<br>
</div></div>> with new installer fa features and packages.<br>
<div class="im">><br>
> So what if you want to run the same set of packages for a long period of<br>
> time? Well, the good news is that we aren't going to force this on you.<br>
> So if you want to grab an ISO, and run a particular desktop environment<br>
> version forever, then you can do so. The PBI system will still operate<br>
> independently, so you can keep running those releases without touching<br>
> your base system packages.<br>
><br>
> With all this said, what's the timeframe? I'm hoping to get the first<br>
> testing ISO out in the next several weeks, so we can begin beating up<br>
> the new updating system. I'll also make available an online update for<br>
> existing 9.1 users to switch to pkgng and jump on the new repository.<br>
><br>
> Thanks for reading, and looking forward to an exciting 2013 for PC-BSD!<br>
</div>I installed the new 9.1 RELEASE and it installed really fast. I updated all<br>
packages. The only problem I have found so far is that appcafe crashes<br>
with a Segmentation Fault.<br>
<br>
Ira Taylor<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
Testing mailing list<br>
<a href="mailto:Testing@lists.pcbsd.org">Testing@lists.pcbsd.org</a><br>
<a href="http://lists.pcbsd.org/mailman/listinfo/testing" target="_blank">http://lists.pcbsd.org/mailman/listinfo/testing</a><br>
</div></div></blockquote></div><br>