Re: Flavors *COMPLETELY* break the port system (synth and poudriere are useless)

On Tue, Dec 05, 2017 at 05:25:13PM -0500, Baho Utot wrote: > Thank you for taking a perfectly good system and breaking it as well as > making it unusable, unstable. You made your point 10 posts ago. You are repeating yourself. Why??? mcl ___

Re: Working on FLAVOR support in portmaster

On Tue, Dec 05, 2017 at 08:42:27AM -0800, Chris H wrote: > IMHO it might be a good idea to make a legacy branch, in the ports > tree before gutting the pre-NG stuff. Good lord, people. The pre-NG stuff has Left The Building. It is not coming back. The last (even trivial) revision to the pkg_*

Re: Welcome flavors! portmaster now dead? synth?

Let me see if I can clear up some common misconceptions ... On Mon, Dec 04, 2017 at 12:56:45AM +, Thomas Mueller wrote: > I believe portmaster and portupgrade work or worked on all supported > versions and architectures of FreeBSD In my experience I can only speak for amd64/i386, but AFAIK

Re: Welcome flavors! portmaster now dead? synth?

On Sat, Dec 02, 2017 at 11:53:58AM +, Carmel NY wrote: > Looking back at other port management utilities like "portmanager", > "portmaster", "portupgrade" and now "synth", The FreeBSD team has > done a pretty good job of obfuscating and rendering them impotent. That's one possible

Re: Spam on -ports

On Fri, Oct 27, 2017 at 07:50:40AM +1100, Dave Horsfall wrote: > Is it official FreeBSD policy to allow spammers free reign on this > list, or is the list owner merely incompetent? or is it 3) spam is a never-ending arms race, and the volunteers are struggling to keep up? ... Honestly, I do not

Re: Porters Handbook section 4.4

I had not commented before because I am on a long road trip. But I'm very glad you have taken on this work. I had always wanted to do something very much like this but never made the time to do it. My old thought was that we have conflated "User's Guide to Ports" and "Ports Reference Handbook".

Re: portmaster, portupgrade, etc

On Wed, Oct 04, 2017 at 09:56:53PM +, Grzegorz Junka wrote: > portmaster/portupgrade trade off doing less work with > less resources in an attempt to produce less rigorously > correct result That was what I thought I said :-) or at least was trying to say. mcl

Re: portmaster, portupgrade, etc

Please understand that I'm not trying to be obstinate, I'm trying to understand. Background: years ago I managed the cluster of i386 blades that we used in package building. 933MHz and 512MB IIRC. So I am familiar with constraint problems. On Wed, Oct 04, 2017 at 02:22:25PM -0700, Steve Kargl

Re: portmaster, portupgrade, etc

On Wed, Oct 04, 2017 at 08:56:00PM +, Grzegorz Junka wrote: > Maybe I am just too ambitious or maybe poudriere is more > idiot-proof? My possibly incorrect understanding is that poudriere trades off doing a lot more work in an attempt to produce more rigorously correct results. mcl

Re: portmaster, portupgrade, etc

On Wed, Oct 04, 2017 at 04:39:25PM -0400, Ernie Luzar wrote: > even the native ports system usage on personal machines > wwill fade away. I have seen this claim many times by users but AFAIR that was never a goal. The feeling was that _most_ users would migrate to using packages, once using

Re: portmaster, portupgrade, etc

On Wed, Oct 04, 2017 at 08:13:16PM +, Grzegorz Junka wrote: > I was trying > to compile with the system that was being updated at the > same time - this can't possibly work (or can it?). It works somewhere between "quite often" to "nearly all the time". It can vary depending on the

Re: gettng the port revision number associated with the pkg repo. [Please?)

On Tue, Oct 03, 2017 at 01:29:23AM +0800, Julian Elischer wrote: > can we just find out who runs the poudriere instances and > ask them to just append the svn revision number somewhere? > or maybe even the poudriere commands  used.. http://www.freebsd.org/portmgr/ ; port...@freebsd.org

Re: Status of portupgrade and portmaster?

On Sat, Sep 30, 2017 at 10:06:17AM -0700, Kevin Oberman wrote: > It is unclear to me whether this was in regard to pots > to the mailing lists or included private responses to > the mail list discussions. I know the former is true, not sure about the latter, but he also used the bugs database in

Re: Status of portupgrade and portmaster?

On Sat, Sep 30, 2017 at 12:30:14PM -0700, Don Lewis wrote: > it illustrates the problem of synth being the only real > consumer of the ADA toolchain (which John also maintained) > on FreeBSD. It's only fair to point out that John did a great deal of work on Ada on FreeBSD. However ... > Another

Re: Status of portupgrade and portmaster?

On Sat, Sep 30, 2017 at 10:06:17AM -0700, Kevin Oberman wrote: > as it makes FreeBSD unusable for those of us with only "small" > systems where the weight of poudriere simply can't be justified. I'm confused. I have been using poudriere for several years to build sparc64 packages. 2 * single

Re: FYI: qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use with poudriere; qemu-arm-static and qemu-aarch64-static work

On Wed, Aug 30, 2017 at 03:09:40AM -0700, Mark Millard wrote: > It appears that qemu-ppc64-static and qemu-ppc-static from > emulators/qemu-user-static are broken. Correct, and known for some time. (fwiw sparc64 hangs as well.) mcl ___

Re: [RFC] Why FreeBSD ports should have branches by OS version

On Tue, Jun 27, 2017 at 04:53:36PM -0400, scratch65...@att.net wrote: > Since that's what I integrate for my dev use, I'd be happy to > take a zero'th-order cut at defining it, if nobody else wants to. Fine. See http://www.lonesome.com/FreeBSD/poudriere/subsets/ for what I use. I'm not

Re: [RFC] Why FreeBSD ports should have branches by OS version

On Tue, Jun 27, 2017 at 09:01:39PM +, Thomas Mueller wrote: > raising the possibility of building for other targets. Which is very much not hardly even the same as "they are being resistant to change". In fact, about as far away from it as is possible to get. "techinically possible" !=

Re: [RFC] Why FreeBSD ports should have branches by OS version

On Tue, Jun 27, 2017 at 07:37:22AM +, Thomas Mueller wrote: > It seems NetBSD pkgsrc people are not catching on, preferring to stay > with the clumsy pkgsrc tools: creatures of habit, reluctant to change. Remember that NetBSD runs on dozens of targets*, of which only two support Ada AFAIK.

Re: [RFC] Why FreeBSD ports should have branches by OS version

On Tue, Jun 27, 2017 at 09:24:31AM -0400, scratch65...@att.net wrote: > The number of ports to build a server-of-all-work is not large. Now the problem is getting people to agree on exactly what that subset is. If there is interest, I can provide the examples and code I use whenever I start up a

Re: [RFC] Why FreeBSD ports should have branches by OS version

On Fri, Jun 23, 2017 at 01:09:26AM -0500, Mark Linimon wrote: > I'll go back to what I was doing before This was an unkind comment and I should not have made it. My apologies to all. mcl ___ freebsd-ports@freebsd.org mailing list ht

Re: [RFC] Why FreeBSD ports should have branches by OS version

You didn't read (or ignored) the last half of my post. Whatever. I'll go back to what I was doing before, e.g., cleaning up other people's messes. Your first two guesses of "what type of commit bits made the messes" don't count. mcl ___

Re: [RFC] Why FreeBSD ports should have branches by OS version

On Fri, Jun 23, 2017 at 01:36:26PM +0800, Julian Elischer wrote: > The problem is that such a set of sponsored branches does not exist so > knowing who'd sign up and who would't is just guesswork And that's why neither myself or the other people who have in the past considered such a business

Re: [RFC] Why FreeBSD ports should have branches by OS version

On Fri, Jun 23, 2017 at 11:58:14AM +0800, Julian Elischer wrote: > What we want is: > A "recent" starting point for our next project/upgrade to start from > and an ongoing version of that, which will get critical fixes only for > at LEAST 2 years, probably 5. > The key here is the *_*critical

Re: [RFC] Why FreeBSD ports should have branches by OS version

On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65...@att.net wrote: > My problem is that my industry experience tells me that reducing > the frequency of port releases is practically *guaranteed* to be > a Really Good Thing for everyone. I remember before we had the quarterly releases, and

Re: The future of portmaster [and of ports-mgmt/synth]

On Fri, Jun 02, 2017 at 01:31:19PM +0200, Torsten Zuehlsdorff wrote: > If someone likes synth please support it. This. Very much this. mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To

Re: The future of portmaster [and of ports-mgmt/synth]

On Wed, May 31, 2017 at 05:58:24PM +0100, Matthew Seaman wrote: > Core has some proposals around planning for such changes that they will > be talking about during the BSDCan devsummit next week. These should > also be published internally fairly soon afterwards for the benefit of > people not at

Re: The future of portmaster [and of ports-mgmt/synth]

On Tue, May 30, 2017 at 11:46:46PM +0200, Per olof Ljungmark wrote: > Hello, I have not followed this thread before but just wanted to say > that I use portmaster extensively, it works for us and I would miss > it if it went. Are there actually plans to retire it? To reiterate the status: *

Re: The future of portmaster [and of ports-mgmt/synth]

On Tue, May 30, 2017 at 12:00:14PM -0700, Mark Millard wrote: > Kevin Oberman rkoberman at gmail.com wrote on Tue May 30 16:52:19 UTC 2017 > > > I really suggest that you look at synth. synth is currently only available for x86 and unless someone steps up to do the work to make the Ada compilers

ports recently marked broken on -current

So during my pass over recent powerpc64 package errorlogs, I found a few ports that were actually broken across all archs on -current, and made those commits. I may not have enough cycles to investigate all these down by myself, so I'm asking for help. Does anyone recognize any of these failure

Re: Issue with pkg upgrade on diskless workstation

I am running a powerpc64 machine diskless but only with some awful hacks. I can make them available if need be, but I hope that someone else has a better recommendation for you. mcl ___ freebsd-ports@freebsd.org mailing list

Re: Systemic problem causing patch errors?

On Sun, Apr 23, 2017 at 01:47:16PM -0500, Lars Eighner wrote: > close to 50 ports fail to build because of patch errors I'm sure you have already checked this, but ... ... when I get this on my powerpc64 machine it is inevitably that I have run out of space somewhere, usually on /tmp. mcl

Re: Is pkg quarterly really needed?

I understand that having the quarterlies is not meeting your use case. You've said that. We get it. So you want some kind of running -quarterly branch. But where are the N hours of work per week to QA all the patches to the -quarterly branch, or a -stable branch, or whatever people seem to

Re: Is pkg quarterly really needed?

On Wed, Apr 19, 2017 at 04:37:05PM -0400, scratch65...@att.net wrote: > (Right now, it's quite hard to resist the paranoid suspicion that > maybe this crazy, anti-real-user behavior is a subtle way to kill > freebsd altogether by driving away the non-hobbyists.) That's one explanation. The

Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)

On Fri, Apr 14, 2017 at 08:27:29PM -0700, Mark Millard wrote: > I've seen material quoted from a exp-run that reported > that about 54(?) ports were then blocked by lang/gcc6-aux > not building. Although the first is an older run (the last complete run IIUC), there were 50 and 51 respectively as

Re: Building math/fftw3 on armv6

> See https://bugs.freebsd.org/215977 for the full story. I believe Michal Meloun is looking at a fix. mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

ports expiring soon due to Google Code site removal

As of 20170324 there are still 175 ports that are marked deprecated and broken due to the Google Code site having gone away. These are due to expire on 20170430. Please consider this a "last call" to find a current mastersite for these ports before then. Thanks. astro/gmapcatcher

Re: dependency tree display

or http://portsmon.freebsd.org/portdependencytree.py?category=sysutils=hal . This runs a make(1) command on the latest version of the tree, so it's slow, but accurate. mcl ___ freebsd-ports@freebsd.org mailing list

Re: sc-im marked broken on aarch64

I've committed the fix. Thanks for reporting and testing. fwiw, my goal in marking ports BROKEN on the various tier-2 archs is to bring more attention to them. We still have a lot of work to do on the arm archs in particular to bring things up to parity with amd64 (well, as much as we can, in

Re: sc-im marked broken on aarch64

If I marked it, it was as a result of it failing on FreeBSD's build cluster. I don't have hardware set up here yet myself. I'd go ahead and commit the fix but I have other distractions this week. mcl ___ freebsd-ports@freebsd.org mailing list

Re: How many versions of clang/llvm are currently required to maintain a system

On Mon, Mar 06, 2017 at 03:00:23PM +, r...@gid.co.uk wrote: > Let me rephrase that: the link http://purelang.bitbucket.org/ > quoted on https://wiki.freebsd.org/ObsoleteLLVMVersions doesn’t work, That's the URL in lang/pure/Makefile. > should be https://bitbucket.org/purelang/ Hmm. I

Re: buzilla 214400: is is ports/head/base/binutils that is being reported on, freebsd-powe...@freebsd.org assignee is wrong

On Tue, Mar 07, 2017 at 04:31:34PM +, Alexey Dokuchaev wrote: > May I ask what exactly makes you think that freebsd-ports-b...@freebsd.org > is correct assignee in this case? I'm away from my systems right now but I do know that this problem also affects sparc64. The original assignments of

Re: How many versions of clang/llvm are currently required to maintain a system

Please see https://wiki.freebsd.org/ObsoleteLLVMVersions . mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: HEADSUP: after r313194 on freebsd-current, lang/gcc ports require a rebuild

On Tue, Feb 28, 2017 at 11:24:27PM +0100, Ed Schouten wrote: > 2017-02-28 21:00 GMT+01:00 Konstantin Belousov : > > Ideally, ports should stop shipping mangled system includes, or even better, > > gcc stop doing fixincludes. > > Amen. Please let me know the magic wand you

Re: openjdk6-i386 not found

Do we even have the right to redistribute that? mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Ports search last database update 2016-01-01

On Sat, Feb 18, 2017 at 09:18:12AM +0100, Kurt Jaeger wrote: > http://portsmon.freebsd.org/portoverview.py I maintain portsmon. I'll take a look at it. mcl ___ freebsd-ports@freebsd.org mailing list

Re: The future of portmaster

On Thu, Feb 16, 2017 at 04:36:24PM -0500, Baho Utot wrote: > Oh no I am now banned as I use synth, whoa is me. This is overstating the matter. May we restrict ourselves to the technical problems/features of the various port maintainence tools, please? :-/ mcl

Re: The future of portmaster

I am glad to see that someone is taking on the work. Thanks. mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

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

On Sat, Feb 11, 2017 at 09:51:41AM +0100, Michelle Sullivan wrote: > Tell me What is the reason for me upgrading those few production > servers from 9.3 to 10/11?... bearing in mind the following: There isn't any ... oh, except for no new security updates. The flip side is the more

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

On Fri, Feb 10, 2017 at 11:02:41PM +0100, Michelle Sullivan wrote: > Or the last strong hold you have - the server owners - get so p**sed off in > reality they can't keep up with the OS updates that they migrate away... So we should give up on EFI, 4k drives, and SSD? mcl

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

On Fri, Feb 10, 2017 at 08:17:31AM -0500, scratch65...@att.net wrote: > A good rule of thumb from industry in the case of major software > would be "forever", meaning until it's very unlikely that anyone > is still using it because of hardware obsolescence, etc. (Sigh.) And how many people do

Re: what's the deal with portsmon? and beefy?

I have been working on it off and on the past 3 weeks. I do not have an ETA for the reworked codebase yet. mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

[CFD] changes to Handbook chapter on Ports

Executive summary: the chapter needed help, and still needs more. Full explanation: I have submitted https://reviews.freebsd.org/D9124 to add a section about ports-mgmt/synth, and a compare-and-contrast table for it and poudriere, portupgrade, and portmaster. I fully expect this section to be

Re: Ports' tips and gotchas

On Tue, Jan 03, 2017 at 06:16:26PM +0100, Vlad K. wrote: > However, what would be the best way to approach this via the FreeBSD wiki? > I'm sure that random wiki pages in various users' namespaces is not quite > the right thing to do. There currently are some ports Wiki pages but they're > all

Re: Welcome to our new portmgr members

On Thu, Dec 22, 2016 at 01:04:22PM +0100, René Ladan wrote: > Please join me in welcoming Adam and Mark. Congratulations guys. mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send

Re: Subscription for committer

On Mon, Dec 19, 2016 at 07:07:06PM -0600, John Marino wrote: > It's a natural reaction to stop attempting to contribute when previous > contributions don't get "attention they deserve". Which some people (including me) see as odds with: > the impression that portmaster is officially recommended

Re: The ports collection has some serious issues

This is the sixth "top of thread" post. Could you please arrange to stop breaking email threading? Thanks. mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

On Sun, Dec 11, 2016 at 02:59:36PM -0800, Mark Millard wrote: > I tend to have powerpc64 and powerpc patches because of my > experimenting with clang targeting them and that the standard > powerpc64 build does not boot PowerMac G5's reliably. Is that on 10, 11 or -current? On 10 I remember being

Re: mail/mixmaster port issue

On Sat, Dec 10, 2016 at 08:16:11PM +, RW via freebsd-ports wrote: > what's the point of supporting backup servers in the ports makefiles > if a port is marked as BROKEN every time it's useful. We've learned from experience that otherwise the problem will never be fixed. mcl

Re: really to pkg people

On Tue, Nov 29, 2016 at 01:21:44AM +0800, Julian Elischer wrote: > It's most disconcerting when a quarterly collection of packages disappears > and one has nowhere to get new packages that match all the ones out in the > field. I think this is more a question for clusteradm@ than for the ports

Re: Fwd: [package - 93i386-quarterly][cad/freecad] Failed for FreeCAD-0.17.g20160907_1 in build

On Mon, Nov 21, 2016 at 09:40:58PM -0500, Pedro Giffuni wrote: > I am not even the port maintainer anymore and I still get these error > messages. In branches/2016Q4/cad/freecad/Makefile you still are :-) > Log URL: >

Re: Binary for Ruby?

On Mon, Nov 21, 2016 at 01:23:28PM +1100, Dave Horsfall wrote: > Is a binary available for Ruby? http://pkg.freebsd.org/FreeBSD:9:i386/latest/All/ruby-2.2.6,1.txz http://pkg.freebsd.org/FreeBSD:9:i386/latest/All/ruby23-2.3.1_1,1.txz

Re: Ports update submission for multiple ports?

Back before we had Bugzilla, I used to recommend separate submissions for each port. But Bugzilla gives us a little more flexibility on Cc:ing and tracking maintainers, so it is not as hard for us to deal with now. Having said that, I personally still have a slight preference for individual PRs.

Re: openntpd-5.7p4_2,2 depends on libressl-2.2.6 ?!

On Wed, Oct 26, 2016 at 09:12:33PM +0100, Joe Holden wrote: > Yes, it is a ridiculous situation but since there appears to be zero > coordination between ports committers, probably expected. Thank you for making sure my motivation to work on fixing things stays at a nice, zero, level. You *do*

Re: misc/jive deleted

On Sun, Oct 23, 2016 at 03:56:07PM -0400, Mikhail T. wrote: > Technically, the only reason to remove a port is due to a failure to > build -- and that hasn't happened. Or: - expired, replaced by newer version - unfetchable - license does not allow anyone to package it - author requested(*)

Re: misc/sword should be removed

Thank you for your very nice troll. I was going to work on some FreeBSD stuff today but now I think I'll find something better to do. mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To

Re: misc/jive deleted

On Sun, Oct 23, 2016 at 02:44:11AM +0200, Alphons van Werven wrote: > > > > Answering opposition/criticism with violence isn't exactly my style. So. If you say something that makes me want to plow my face into my hands, that's violence? Wow. mcl

Re: misc/jive deleted

On Sat, Oct 22, 2016 at 05:46:15PM +0200, Julian H. Stacey wrote: > Censorship is offensive. Censor the offensive Censor: remove his/her commit > bit. IIUC correctly you will be removing more than one commit bit, but again, I cannot speak for those who made the decision. "Free Speech" means

Re: misc/jive deleted

On Sat, Oct 22, 2016 at 01:31:04PM +0200, Alphons van Werven wrote: > I'm still half waiting for someone with misguided delusions of moral > superiority to delete that port, thinking it's their decision to make > that FreeBSD must not enable people to display their system load as a > cartoon woman

Re: misc/jive deleted

disclaimer: I wasn't the person who made the decision. This change became contentious after it was made; however, that discussion only occurred on internal mailing lists. The "pro" removal points: some of these terms are no longer acceptable in polite society, and far cross the line from humor

Re: private ports and pkgs versioning

On Tue, Oct 18, 2016 at 02:52:34PM +0100, Matthew Seaman wrote: > Hmmm... looks like this is handled in the 30 or so lines starting at > line 1179 of bsd.port.mk Wouldn't the patch to ports/Makefile just be the following? .if exists(${.CURDIR}/Makefile.local) .include "${.CURDIR}/Makefile.local"

Re: private ports and pkgs versioning

On Tue, Oct 18, 2016 at 08:49:06AM +0100, Matthew Seaman wrote: > Yes, there is a lot of useful stuff in the ports tree to support local > ports or even whole local categories of ports. I can't recall now how I > learned about all this stuff -- it may well have been just be a > combination of

Re: pkg: PRE-INSTALL script failed

Is this with pkg 1.9.0 or the just-issued 1.9.1? mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap tardis

On Thu, Oct 13, 2016 at 04:58:56PM +0900, Randy Bush wrote: > Fetching snapshot tag from your-org.portsnap.freebsd.org... done. IIUC there was an outage on this server and it has been fixed. mcl ___ freebsd-ports@freebsd.org mailing list

Re: dependency explosions

On Tue, Oct 04, 2016 at 10:21:30AM +1100, Greg 'groggy' Lehey wrote: > Is there a way to display these dependencies in a tree structure? http://portsmon.freebsd.org/portdependencytree.py?category=x11=kde4 It's slow because I do not store dependencies in the database, so it recalculates it on the

Re: Google Code as an upstream is gone

On Fri, Sep 30, 2016 at 02:51:07PM +0200, David Demelier wrote: > We should provide a longer expiration date by keeping distfiles to our > FreeBSD mirrors for a while until the upstream moves to somewhere else. My past experience looking into such things tells me that once this happens the

Re: Installing ports via pkg on 11 [ports-mgmt/synth only available for amd64 and i386 on FreeBSD]

On Sat, Sep 24, 2016 at 10:06:07PM +0200, Luciano Mannucci wrote: > Ah, no ada for the Powerpc... that I didn't know. May I ask why? No one has done the work to try to make the compiler work. Please see the website that John Marino (marino@) has for more information:

Re: ${INSTALL_DATA} problems

On Fri, Sep 09, 2016 at 08:29:12AM +1000, Aristedes Maniatis wrote: > Maybe the Makefile language will become clearer to me one day, but > I've been using FreeBSD since 4.0 and it hasn't clicked yet. Don't worry, the FreeBSD ports framework does things with the Makefile language that was never

Re: suggested patch for bsd.ports.mk

On Sat, May 14, 2016 at 11:25:08AM +0800, Julian Elischer wrote: > so who or what decides if I can put this in? portmgr. From the portmgr pages: Changes to bsd.port.mk are not the only commits that can have a drastic effect on the tree. We request that any such changes also be tested on

Re: Removing documentation

On Sun, Feb 07, 2016 at 03:21:49PM +0100, John Marino wrote: > Anybody proposing to be maintainer, in my opinion, should first be > required to take over every open PR in bugzilla thus ensuring that no one would ever take it. IMVVHO. mcl ___

Re: Can we bring back sysutils/cronolog?

On Sun, Nov 29, 2015 at 02:24:53PM -0800, Chris H wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199851 > It has a workable patch. But no one appears to want to commit it. "No one has gotten to it yet" is different from "no one appears to want to commit it". The ports PR count stands

Re: Hi, I'd like to update the coreos-etcd port!

On Tue, Nov 10, 2015 at 09:36:48AM -0500, John Barker wrote: > I went through the earlier steps about finding any outstanding issues, I > can't see any pending PRs here: > http://portsmon.freebsd.org/portoverview.py?category=devel=etcd= > am I looking for it wrong? No, that should be correct.

Re: New pkg audit / vuln.xml failures (php55, unzoo)

On Wed, Jun 10, 2015 at 11:45:29PM -0600, Janky Jay, III wrote: Hrm... Numerous inquiries regarding this and no response is somewhat disappointing. This is not an excuse, but a number of us are at BSDCan and distracted. There have been discussions about how to solve the larger ports security

FreeBSD ports which are currently scheduled for deletion

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on

FreeBSD ports which are currently marked broken

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. One common problem is

FreeBSD unmaintained ports which are currently scheduled for deletion

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on

FreeBSD ports which are currently marked forbidden

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port,

FreeBSD unmaintained ports which are currently marked broken

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. One common problem is

FreeBSD ports which are currently marked broken

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. One common problem is

FreeBSD ports which are currently scheduled for deletion

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on

FreeBSD unmaintained ports which are currently marked broken

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. One common problem is

FreeBSD ports which are currently marked forbidden

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port,

FreeBSD unmaintained ports which are currently scheduled for deletion

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on

Re: Synchronising ports with package cluster

On Wed, Apr 15, 2015 at 08:55:23AM -0700, Kevin Oberman wrote: My thanks to whoever made this possible. New hardware of this sort is a bit expensive and the time of those who can integrate it all is invaluable. I'm not the one working on this so I'm somewhat butting in, however: You guys

FreeBSD ports which are currently marked broken

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. One common problem is

FreeBSD ports which are currently scheduled for deletion

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on

FreeBSD unmaintained ports which are currently marked forbidden

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port,

FreeBSD unmaintained ports which are currently scheduled for deletion

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on

FreeBSD ports which are currently marked forbidden

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port,

Re: Time to be real

Thank you for your troll. For your convenience, we will do our best not to reply to you any further, to waste either your time, or valuable electrons. mcl ___ freebsd-ports@freebsd.org mailing list

  1   2   3   4   5   6   7   8   9   10   >