Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

On 02/08/17 11:56, scratch65...@att.net wrote: > So, what's the deal here? To "encourage" people to upgrade, pkg > will break their existing install? That is both hostile and > deeply arrogant! mat's response is more exasperation than anything else. This is a well known problem for which there

please fix the pkg downloads system

please work on having the "Latest" image in a directory that has the cvs revision number in its name and make the current names just be links to there. I ONCE AGAIN (for the third time) got half of one release (432891) and half of another (433120) because the newest snapshot of the pkgs was

updating ruby

On or about 20170109, the default version of ruby was updated from 2.2 to 2.3. However, "pkg install" wants to install version 2.2 for ports that require ruby. Is there a way to override this behavior? -- Carmel ___ freebsd-ports@freebsd.org mailing

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

On Wed, 8 Feb 2017 14:43:25 +, Matthew Seaman wrote: >On 02/08/17 11:56, scratch65...@att.net wrote: >> So, what's the deal here? To "encourage" people to upgrade, pkg >> will break their existing install? That is both hostile and >> deeply arrogant! > >mat's response

Re: ports and dependency hell

On 08/02/2017 08:03, Julian Elischer wrote: On 8/2/17 3:17 am, Grzegorz Junka wrote: On 07/02/2017 18:03, Julian Elischer wrote: This is a serious post on a serious issue that ports framework people seem unaware of. (...) The call "It just works under linux, select the versions you want

Re: please fix the pkg downloads system

On 02/08/17 09:06, Julian Elischer wrote: please work on having the "Latest" image in a directory that has the cvs revision number in its name and make the current names just be links to there. I ONCE AGAIN (for the third time) got half of one release (432891) and half of another (433120)

Re: please fix the pkg downloads system

On 02/ 8/17 08:06 AM, Julian Elischer wrote: please work on having the "Latest" image in a directory that has the cvs revision number in its name and make the current names just be links to there. I ONCE AGAIN (for the third time) got half of one release (432891) and half of another

misc/e2fsprogs-libuuid Issue

===>>> Launching child to install misc/e2fsprogs-libuuid ===>>> All >> misc/e2fsprogs-libuuid (1/5) ===>>> Currently installed version: e2fsprogs-libuuid-1.43.3_1 ===>>> Port directory: /usr/ports/misc/e2fsprogs-libuuid ===>>> Starting check for build dependencies ===>>> Gathering dependency

Re: Seamonkey update

On Sun, 5 Feb 2017 20:05:51 -0500, roberth...@rcn.com wrote: > > Jeffrey Bouquet writes: > > > pkg today updated seamonkey, now it segfaults, > > every which way I try to run it. > > I am running SeaMonkey 2.46_5 (compiled today) under: > > FreeBSD 11.0-RC2 #0 r304729:

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

On Wed, Feb 08, 2017 at 12:34:36PM -0500, scratch65...@att.net wrote: > For those people (I'm one) long version lifespans and bug-free > operation is a much bigger desideratum than winning the secret > race (I presume there is some kind of secret race going on, since > otherwise the crazy

qupzilla, etc. bus error at FreeBSD-current (was: Re: please fix the pkg downloads system)

08.02.2017 20:20, Jeffrey Bouquet via freebsd-ports пишет: qupzilla-qt4 bus error As for this particular error. I have seen those at FreeBSD-12 with qupzilla, otter browser, diligent and some other applications. All of them are regularly updated from the official repository. And only if I

Re: ports and dependency hell

On 8/2/17 3:17 am, Grzegorz Junka wrote: On 07/02/2017 18:03, Julian Elischer wrote: This is a serious post on a serious issue that ports framework people seem unaware of. (...) The call "It just works under linux, select the versions you want of each package and type make" is often heard

FreeBSD ports you maintain which are out of date

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,

Re: ports and dependency hell

Hi! > I'm discouraged to not hear back from any of the ports 'committee'. I'm not from the committee 8-), but I think you raise relevant points. It is not easy to cover them. All of the pkg-developers have their tables full of work, so ... Crafting a well-reflected answer takes time. --

Re: (Relevant?) article on package mgmt at lwn.net

On 5/2/17 7:18 pm, Kurt Jaeger wrote: Hi! There's an article on package mgmt, also referencing the topic of language-specific package mgmt, at lwn.net: Package managers all the way down https://lwn.net/Articles/712318/ very relevant FreeBSD ports/pkg issues are taking close to 50% of my

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

My bug report just got closed by Mathieu Arnold because "You are using an obsolete FreeBSD version, you need to update to 10.3." So, what's the deal here? To "encourage" people to upgrade, pkg will break their existing install? That is both hostile and deeply arrogant! I don't want to upgrade

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

[Default] On Wed, 8 Feb 2017 12:46:09 +0100, Franco Fichtner wrote: > >> On 8 Feb 2017, at 12:29 PM, >> wrote: >> >> I just tried to install the fuse-nfts pkg under 10.2 on my >> server-of-all-work. But after requiring me to

Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

I just tried to install the fuse-nfts pkg under 10.2 on my server-of-all-work. But after requiring me to "upgrade" pkg, the fuse-ntfs install failed, apparently because there's an undefined symbol ("utimenstat") in pkg itself! How do I extricate myself?

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

> On 8 Feb 2017, at 12:29 PM, > wrote: > > I just tried to install the fuse-nfts pkg under 10.2 on my > server-of-all-work. But after requiring me to "upgrade" pkg, the > fuse-ntfs install failed, apparently because there's an undefined > symbol

Re: ports and dependency hell

On 02/08/17 03:03, Julian Elischer wrote: > [...] > I'm discouraged to not hear back from any of the ports 'committee'. > [...] Possibly because this has been the topic of a number of rancorous mail threads in the last few months already, and everybody is fatigued. What there *hasn't* been is a

Re: ports and dependency hell

On Wed, 8 Feb 2017 16:03:56 +0800 Julian Elischer wrote: > On 8/2/17 3:17 am, Grzegorz Junka wrote: > > > > On 07/02/2017 18:03, Julian Elischer wrote: > >> This is a serious post on a serious issue that ports framework > >> people seem unaware of. > >> (...) > >> > >> The call "It just works