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: Problem with some gnustep ports after upgrade from 12.1 to 12.2

On 12 Mar 2021, at 21:32, Edwin Ancaer wrote: > $ sudo pkg install gnumail > Updating FreeBSD repository catalogue... > FreeBSD repository is up to date. > All repositories are up to date. > pkg: No packages available to install matching 'gnumail' have been found in > the repositories > > Out of

Re: Testing www/chromium before installing

On Sat, Mar 13, 2021 at 06:11:06PM +0100, Michael Gmelin wrote: > > > On Sat, 13 Mar 2021 08:50:07 -0800 > bob prohaska wrote: > > > Hi Michel, > > > > On Sat, Mar 13, 2021 at 05:01:16PM +0100, Michael Gmelin wrote: > > > What about ???make stage > > > > > Never heard of it, and can't

Re: Testing www/chromium before installing

> On 13. Mar 2021, at 18:51, bob prohaska wrote: > > On Sat, Mar 13, 2021 at 06:11:06PM +0100, Michael Gmelin wrote: >> >> >>> On Sat, 13 Mar 2021 08:50:07 -0800 >>> bob prohaska wrote: >>> >>> Hi Michel, >>> >>> On Sat, Mar 13, 2021 at 05:01:16PM +0100, Michael Gmelin wrote: What

Testing www/chromium before installing

After a _very_ long time www/chromium finished compiling on a Pi3B+. I'd like to test it before installing, since I have a (mostly) working version in /usr/local/bin and don't want to overwrite it until I know the new version works at least as well as the old one. Poking around in the source

Re: On 14-CURRENT: no ports options anymore?

On 13/03/21 20:17, Hartmann, O. wrote: Since I moved on to 14-CURRENT, I face a very strange behaviour when trying to set options via "make config" or via poudriere accordingly. I always get "===> Options unchanged" (when options has been already set and I'd expect a dialog menu). This

Re: On 14-CURRENT: no ports options anymore?

If this isn’t at least in /usr/ports/UPDATING it sure should be. -Dan > On Mar 13, 2021, at 12:58 PM, Guido Falsi via freebsd-ports > wrote: > > On 13/03/21 20:17, Hartmann, O. wrote: >> Since I moved on to 14-CURRENT, I face a very strange behaviour when trying >> to set >> options via

On 14-CURRENT: no ports options anymore?

Since I moved on to 14-CURRENT, I face a very strange behaviour when trying to set options via "make config" or via poudriere accordingly. I always get "===> Options unchanged" (when options has been already set and I'd expect a dialog menu). This misbehaviour is throughout ALL 14-CURRENT

Re: On 14-CURRENT: no ports options anymore?

Am 13.03.21 um 20:17 schrieb Hartmann, O.: Since I moved on to 14-CURRENT, I face a very strange behaviour when trying to set options via "make config" or via poudriere accordingly. I always get "===> Options unchanged" (when options has been already set and I'd expect a dialog menu). This

Re: On 14-CURRENT: no ports options anymore?

On Sat, Mar 13, 2021 at 2:51 PM Dan Mahoney (Ports) wrote: > If this isn’t at least in /usr/ports/UPDATING it sure should be. > > -Dan > Ditto! While it did not take me long to discover that the ncurses shareable had bumped the version, I wasted a lot of time rebuilding ports one by one. At

Re: On 14-CURRENT: no ports options anymore?

You mention release notes. Slightly off-topic, but I never understood why, if there was a beta or RC available, the release-notes of the time weren’t available on www.freebsd.org . Wouldn’t that make sense to see if there were things you wanted to try out and test?

Re: On 14-CURRENT: no ports options anymore?

I have same problem days ago when dialog4ports crashed. just reinstall/install ports-mgmt/dialog4ports/ Hartmann, O. escreveu no dia sábado, 13/03/2021 à(s) 19:17: > Since I moved on to 14-CURRENT, I face a very strange behaviour when > trying to set > options via "make config" or via