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

[Mark Linimon]

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
___
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: Working on FLAVOR support in portmaster

[Mark Linimon]

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_* codebase was Mon Aug 19
14:04:35 2013 UTC:

  https://svnweb.freebsd.org/base?view=revision=254525

The corresponding bsd.port.mk version was:

  https://svnweb.freebsd.org/ports?view=revision=324051

For comparison:

  ports is currently at r455604 [*]
  USES= had recently been introduced at r313517 Wed Mar 6 14:28:57
2013 UTC (4 years, 9 months ago)
  options handling had recently been reworked at r321785 Wed Jun 26
07:22:06 2013 UTC (4 years, 5 months ago)
  LIB_DEPENDS had recently been reworked at r322328 Fri Jul 5 14:10:55
2013 UTC (4 years, 5 months ago) by bapt
  staging came in at r327910 Mon Sep 23 05:56:35 2013 UTC (4 years,
2 months ago) 
  the warning about pkg_* EOL was r342537 Tue Feb 4 14:23:08 2014
UTC (3 years, 10 months ago) 
  and I'm not going to iterate over all the refactoring and bug-
fixing since that time.

(Most likely, pkg_* was not thoroughly tested since early 2013, so I've
included the first 4 big reworks above.)

If you want to look at the diffs to bsd.port.mk since the last time pkg_*
was even trivially maintained:

  https://svnweb.freebsd.org/ports/head/Mk/bsd.port.mk?r1=324051=455280

The diff is 5528 lines.  It's unreadable.

If you're staying with pkg_*, you're basically saying "I don't mind
running with something that hasn't really been QAed with those 5528 lines
of changes."

IMVVHO: madness.

I really don't have anything more I can say on the matter.

mcl

* Because I'm now annoyed, I'm going to do some math:

  455604 - 324051 = 131553

That's over One. Hundred. Thousand. Ports. Commits. Ago.

That's 7 pages of commits to bsd.port.mk itself, per svnweb.
___
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: Welcome flavors! portmaster now dead? synth?

[Mark Linimon]

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 yes.

> but synth is limited.

Synth is written in Ada which IIUC limits it to amd64/i386.  I think
there was work to get Ada going under some arm variant but AFAIK it
was never completed.

Synth was never an option for mips/mips64/powerpc/powerpc64/sparc64.
 
> Does poudriere work on all supported versions and architectures of
> FreeBSD?

I personally run it native on amd64/powerpc64/sparc64 and cross on
aarch64/armv6/armv7, on various combinations of 10, 11, and -CURRENT.
I've had it running, under load, on these buildenvs for several years,
both with and without ZFS.  It is my go-to system.

It is also used to build packages on the freebsd.org cluster, including
mips/mips64.

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: Welcome flavors! portmaster now dead? synth?

[Mark Linimon]

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 explanation.  Or, as Occam's Razor suggests, they
continue to try to modernize the Ports Collection, despite obstacles
(including stale codebases and stubborn maintainers).

I'll admit some of the transitions have been pretty rough.  But when
you go back and look at Ports as of e.g. FreeBSD 4, there have been a
lot of good changes -- including some which were necessary due to sheer
scale.

If we had stayed with what we had then, the whole thing would have
collapsed by now.

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: Spam on -ports

[Mark Linimon]

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 understand why people make posts like this.

Speaking as someone who, behind the scenes, helps people try to stay
motivated, all you're doing is make other people's lives miserable --
including mine.

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: Porters Handbook section 4.4

[Mark Linimon]

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".  Certainly the bulk of the existing text is
the latter type (even if not well organized; it kind of "grew".)

I'm indifferent if the Guide parts (basically what you have been working
on) remain in the PH or become a separate piece.  But depending on the
degree of rewrite, do you think that might be easier?  It's certainly
true that the current PH is too bloated.

I won't have the cycles to look at your work for another week or two,
so consider this just "a voice from the peanut gallery".

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: portmaster, portupgrade, etc

[Mark Linimon]

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
___
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: portmaster, portupgrade, etc

[Mark Linimon]

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 wrote:
> Can't find info on whether jails can be avoided.

I have not checked the code but IIRC, no.  I thought jails
had low memory overhead, though.

> If you only have 1 Gb of memory and 5-10 GB diskspace,
> then using poudriere with zfs and jails is a nonstarter.

For point of comparison, with those constraints, I do not
understand how modern llvms can build at all.

What happens if you use the manual approach on this same
system?  e.g.

  cd /usr/ports/devel/llvm40
  mkdir -p /usr/ports/packages
  make && make package
  pkg install /usr/ports/packages/llvm.txz

Do you still run out of resources?

In that case, there's not much that can be done.  The
compilers, the office suites, and certain math packages
are huge beasts.  However you try to build them won't
matter.

I would think having a copy of the llvm workfiles in a jail
is going to be equivalent to having them in /tmp?

I must be missing something.

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: portmaster, portupgrade, etc

[Mark Linimon]

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
___
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: portmaster, portupgrade, etc

[Mark Linimon]

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 packages had been made
much easier and more robust than the previous packaging
technology.  (Disclaimer: I was much more familiar with the
internals of the old pkg-* tools and the bad state that they
had gotten into.)

> The past 2 years a great
> amount of effort has gone into bring the handbook up to
> date with the current status of the operating system. But
> it is a very far cry from a teaching aid.

I have some proposed patches for the ports section that
need to be dusted off and committed.  But I think your
critism is valid -- it works as a reference better than as
a tutorial.  The latter is not fixable in the near-term
(simply due to volunteer cycles).

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: portmaster, portupgrade, etc

[Mark Linimon]

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 complexity of
the ports you have installed, what state the tree is in,
how much the ports you use are often used by others, and
subtle differences in changes to port dependencies.

This is complex enough to be indistinguishable from "phase
of the moon."

In this case I really wish I were joking.

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: gettng the port revision number associated with the pkg repo. [Please?)

[Mark Linimon]

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

Specifically, QA Policies, although due to staleness the
page does not _specifically_ mention poudriere as the
current technology.

None of this is especially secret.

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: Status of portupgrade and portmaster?

[Mark Linimon]

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 a fashion I can only
describe as caustic.  (That drove at least one person away
from the project.)

John is ably qualified technically.  If you agree with him
on such things as goals and design decisions, he is easy to
work with.  But my experience was that if you did not, you
were in for a long fight.

Obvious disclaimer: I was in the latter category.

People will have to come to their own conclusions.

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: Status of portupgrade and portmaster?

[Mark Linimon]

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 issue is that synth is only available on x86 because that
> is what the toolchain limits it to

This, to me, is what always stuck in my craw.

I think John may have done some work on Ada on armv6 and/or aarch64
but I would have to go check to be sure.  There is a _possibility_
that with sufficient effort it could be made to work there.  But
AFAICT there was never any realistic chance it could work on
mips,
powerpc, or sparc64.

Now, you might claim those aren't deal-breakers, but IMVHO
not
having it working on both armv6 and aarch64, at production
quality,
*is* one -- those two need to be first-class citizens going forward
(e.g. for 12.0).

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: Status of portupgrade and portmaster?

[Mark Linimon]

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 core 1.5GHz CPU, 16GB
RAM, 2 * 72GB SCSI-3 disks.  Yes, it can get disk-bound,
especially I am not using ZFS.  No, it's not particularly
fast.  Yes, the machine is solely dedicated to this task.

I do believe poudriere will struggle on the smaller ARM
boards, solely due to the RAM limitations.  I intend to do
some further investigation.

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: FYI: qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use with poudriere; qemu-arm-static and qemu-aarch64-static work

[Mark Linimon]

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
___
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: [RFC] Why FreeBSD ports should have branches by OS version

[Mark Linimon]

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 particularly interested in maintaining it as a general
set of files, but if someone can build on it, fine.

> By "unnecessary", Mark, I mean the fact that the bits are not
> controlled locally, and thus potentially change from moment to
> moment such that it's impossible to guarantee that two people
> building the same app with the same options on two different
> days, or even hours, will get the same result.

I don't understand this.

The distinfo mechanism is the solution for this problem for released
code.

If people are relying on "whatever is in git at the moment" to
mean "release", well then that's upstream not understanding what
is meant by "release".  Either educated them or fork their code
and become the new upstream.

> Switching to a central repository model, where the bits are
> fetched from around the globe only once per cycle, sanitised, and
> thereafter read only from the repository, would drop the number
> of file-not-founds and wrong-versions down pretty close to zero.

Again, I simply don't understand this.

> >No one has ever done the work on "most minimal set of dependencies"
> >in the ports tree -- and that's because it's hard work.  Add to that
> >the fact that the technology has never supported partial checkouts
> >and it complicates things.
> 
> No argument from me!   IMO a big contributor to the problem is
> that the bits haven't been normalised and integrated into
> libraries.  So the process is frankensteinean:  odds and bobs
> dredged up wherever they can be found and stuck together in hope
> that they'll cooperate.

And this is where the hard work lies.

By comparison, defining "which ports are canonical" is easy.

IMHO.

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: [RFC] Why FreeBSD ports should have branches by OS version

[Mark Linimon]

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" != "feasible in the immediate future".

I feel like I'm repeating myself in this thread, again.

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: [RFC] Why FreeBSD ports should have branches by OS version

[Mark Linimon]

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.

mcl

* http://ftp.netbsd.org/pub/NetBSD/NetBSD-7.1/
___
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: [RFC] Why FreeBSD ports should have branches by OS version

[Mark Linimon]

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 new machine here at the house, e.g. powerpc64,
sparc64, etc.  And we'll see how close to agreement people can get.

(Yes, I'm quite skeptical.)

> Unnecessarily complex and a source of uncontrolled errors, yes,

One person's "unnecessary" is another person's "necessary".

> Specialist workstations such as sound/video editing?  Maybe.

You'll immediately go from a few hundred ports to a few thousand ports.

No one has ever done the work on "most minimal set of dependencies"
in the ports tree -- and that's because it's hard work.  Add to that
the fact that the technology has never supported partial checkouts
and it complicates things.

tl;dr: I do have long-time experience building subsets of the ports
tree and in my experience it's harder than people think, once you
get beyond a few dozen targets.

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: [RFC] Why FreeBSD ports should have branches by OS version

[Mark Linimon]

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
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

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

[Mark Linimon]

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
___
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: [RFC] Why FreeBSD ports should have branches by OS version

[Mark Linimon]

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 have gone into it.

I rejected it as "a fantastic way to work hard and lose tons of money".
I've had enough of those in my career, 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: [RFC] Why FreeBSD ports should have branches by OS version

[Mark Linimon]

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 fixes only*_* part.

And how much is that worth to you and/or your company?

I mean, honestly.  You constantly criticize the volunteers for not doing
what you need.  Well _need_, to me, implies the existence of some kind
of incentive.  I can state to you, flatly, that "a feeling of a job well
done" isn't _sufficient incentive_ to do professional-level QA.  There's
a reason people get _paid to do it_: it's hard, long, tedious, unrewarding
work, and it never ends.

Clearly, relying on _volunteers_ to do professional-level QA isn't working
out for you.

Thus, IMVVHO, at this point, to get what you _need_, you need to get out
your checkbook and provide a _financial_ incentive.  In my experience,
with the volunteers that we have, we can barely keep things afloat as
it is.  It's sufficiently hard to recruit people, and burnout is high
-- especially given the grief we take.

(I won't even start on how even "critical fixes" can drag in the need
to update dependencies, which then conflict with each other, and so on
and so forth, and thus even "critical fixes" aren't trivial.)

Summary: you are providing negative incentive to the ports crew, with
no upside for them, and you can't understand why it doesn't work.

tl;dr: you want us to be RedHat but with no paid employees.

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: [RFC] Why FreeBSD ports should have branches by OS version

[Mark Linimon]

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 people on the
mailing lists complained constantly about the ports bits only being
available once per release, or rolling with -head.

In other words, the exact opposite of what you are suggesting.

tl;dr: there is no way to satisfy everyone.

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: The future of portmaster [and of ports-mgmt/synth]

[Mark Linimon]

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 unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

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

[Mark Linimon]

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 BSDCan.

I'll look forward to seein what the conclusions are.

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: The future of portmaster [and of ports-mgmt/synth]

[Mark Linimon]

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:

 * some extensive changes to the ports framework are coming;
 * these will require large changes to all the port upgrade tools;
 * no one has stepped forwards to offer to do the work for anything
   other than poudriere AFAIK.

If no one does the work, at the time the large changes come, the
other tools will break.

People have been wanting subpackages (aka flavors) for many years;
IIUC these are parts of the changes that are coming.

Someone needs to step forwards and say "yes, I will do the work."

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: The future of portmaster [and of ports-mgmt/synth]

[Mark Linimon]

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 run on the other architectures
that is certain to remain to the case.

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"

ports recently marked broken on -current

[Mark Linimon]

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
modes, and if so, can recommend a fix?

I've grouped them together based on my analysis, which may not be
correct.  Note: error messages from gcc and clang are intermixed.

Thanks.

mcl

benchmarks/dbs  tcp_debug.h: field has incomplete type 'struct tcpcb'
security/revealrk   revealrk.c: 'struct xtcpcb' has no member named 
'xt_socket'
security/pidentdk_freebsd2.c: storage size of 'pcbp' isn't known

japanese/nethack34  stdlib.h: conflicting types for 'srandom'

net-mgmt/netdatafreebsd_sysctl.c: storage size of 'vmmeter_data' isn't 
known
sysutils/asmem  read_mem.c: invalid use of undefined type 'struct 
vmmeter'

net/lft lft_types.h: pcap-int.h: No such file or directory
security/dsniff pcaputil.c: '/usr/include/pcap-int.h' file not found
sysutils/pftop  sf-gencode.h: pcap-int.h: No such file or directory

sysutils/scprotect  scprotect.c: 'sysctl__' undeclared (first use in this 
function)

www/cherokeeunable to detect data struct is used by crypt_r
___
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: Issue with pkg upgrade on diskless workstation

[Mark Linimon]

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
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Systemic problem causing patch errors?

[Mark Linimon]

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
___
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: Is pkg quarterly really needed?

[Mark Linimon]

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 demand, to come from?

This is a serious -- if very irritated -- request.

We've moved from a "we don't have enough person-power to manage a ports
branch" to "we kinda have enough person-power to manage both head and a
kinda-branch."  OK.  That isn't meeting all the use cases.  Understood.

Are you going to volunteer for a team to run that QA?  Who else do you
think should be on it?  Clearly the current volunteers don't have the
bandwidth.  It is hard enough just to kep ports-head building.  Where
do the hours come from?

You're comparing your expectations of the output of what a professional
QA team would do, to the work that N volunteers do.  Obviously the results
are not comparable.  It's crazy to think that they would be.

Honestly without some volunteers to do the _hard_, _unrewarding_, work
to QA the ports tree, this is all either a) just talk, or b) people
wanting volunteers to provide professional-level support, for free.

tl;dr: provide some resources, or don't.  I am getting to the point where
I don't care either way.  All I see is the people who are doing actual work
get poked in the eye.

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: Is pkg quarterly really needed?

[Mark Linimon]

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 other, possible, explanation, is that the efforts of a group of
volunteers isn't adequate enough for every use case -- including your own.

But, of course, feel free to cast aspersions wherever and whenever.  We're
just machines, we have no feelings whatsoever.

Now if no one minds, I'm going to go back to contemplate the existential
question of "why do I even bother trying to fix things".

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: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)

[Mark Linimon]

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 of:

http://thunderx1.nyi.freebsd.org/build.html?mastername=110arm64-default=423029
http://beefy8.nyi.freebsd.org/build.html?mastername=head-armv6-default=p437390_s316341

I think you're fairly deep into unexplored territory here.

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: Building math/fftw3 on armv6

[Mark Linimon]

> 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 "freebsd-ports-unsubscr...@freebsd.org"

ports expiring soon due to Google Code site removal

[Mark Linimon]

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   ke...@freebsd.org
audio/last-cmus po...@freebsd.org
audio/logitechmediaserver-superdatetime m...@tranquillussoftware.co.uk
audio/mehdiaplayer  v...@freebsd.org
audio/pidgin-musictracker   po...@freebsd.org
audio/xpi-musicpm   po...@freebsd.org
biology/treeviewx   po...@freebsd.org
chinese/fcitx-googlepinyin  lich...@gmail.com
chinese/fortune po...@freebsd.org
chinese/fqterm  darc...@gmail.com
chinese/ibus-table-chinese  dennyli...@hs.ntnu.edu.tw
chinese/libgooglepinyin lich...@gmail.com
chinese/p5-cconvsunp...@freebsd.org
chinese/php-cconv   sunp...@freebsd.org
chinese/py-cconvsunp...@freebsd.org
chinese/ydict   po...@freebsd.org
comms/esmskagam...@users.sf.net
databases/akonadi-googledatapo...@freebsd.org
databases/jdbm2 a...@freebsd.org
databases/powerarchitectjjuan...@gmail.com
deskutils/epoch v...@freebsd.org
deskutils/libgcal   po...@freebsd.org
deskutils/nagaina   po...@freebsd.org
deskutils/plasma-applet-playwolfjh...@freebsd.org
deskutils/superswitcher po...@freebsd.org
deskutils/vboxgtk   po...@freebsd.org
devel/arduino-glcd  le...@ee.lbl.gov
devel/bncsutil-ghost++  po...@freebsd.org
devel/c-unittak@gmail.com
devel/ccons dan...@freebsd.org
devel/cld   de...@freebsd.org
devel/dissy s...@freebsd.org
devel/freeocl   ohart...@zedat.fu-berlin.de
devel/fuel  nukama+maintai...@gmail.com
devel/google-styleguide po...@freebsd.org
devel/guiloader-c++ po...@freebsd.org
devel/guiloader po...@freebsd.org
devel/libfreefare   rom...@freebsd.org
devel/liblouisxml   w...@freebsd.org
devel/libmpsse  po...@freebsd.org
devel/nglogcv...@freebsd.org
devel/nxt-pythonacier...@awesom.eu
devel/plan9port po...@freebsd.org
devel/privman   bdrew...@freebsd.org
devel/py-cmdln  pyt...@freebsd.org
devel/py-coil   ghostonthew...@gmail.com
devel/py-px po...@freebsd.org
devel/spdictvani...@freebsd.org
devel/stormlib-ghost++  po...@freebsd.org
devel/streamhtmlparser  itechb...@gmail.com
devel/winpdbpo...@freebsd.org
dns/hostdb  rodr...@freebsd.org
dns/py-adns m.tsatse...@gmail.com
dns/py-bonjour  jpaet...@freebsd.org
emulators/wxmupen64plus a...@freebsd.org
ftp/py-pyftpdliblw...@freebsd.org
games/dcrosspo...@freebsd.org
games/hexglass  po...@freebsd.org
games/libfovpo...@freebsd.org
games/lostfeathers  po...@freebsd.org
games/robocalypto   po...@freebsd.org
games/tinymux   po...@freebsd.org
graphics/delaboratory   po...@freebsd.org
graphics/iulib  hiroto.kagot...@gmail.com
graphics/ocropushiroto.kagot...@gmail.com
graphics/py-gchartwrapper   ni...@freebsd.org
graphics/py-graph-dot   de...@freebsd.org
graphics/py-graphy  po...@freebsd.org
graphics/py-pyggel  koalat...@gmail.com
graphics/py-pyglet  amd...@freebsd.org
graphics/qiviewer   v...@freebsd.org
graphics/seam-carving-gui   bugan...@gmail.com
graphics/sk1libsamd...@freebsd.org
graphics/svgfig po...@freebsd.org
graphics/uniconvertor   amd...@freebsd.org
graphics/uniconvw   amd...@freebsd.org
irc/dircproxy   m...@freebsd.org
irc/py-gozerbot s...@blinkenlights.nl
irc/tircd   ga...@freebsd.org
japanese/nhocr  

Re: dependency tree display

[Mark Linimon]

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
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: sc-im marked broken on aarch64

[Mark Linimon]

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 any case.)  All help is welcome!

For more, please see:

  https://wiki.freebsd.org/arm64/ports
  https://wiki.freebsd.org/armv6/ports

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: sc-im marked broken on aarch64

[Mark Linimon]

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
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

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

[Mark Linimon]

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 looked and it seems like https://purelang.bitbucket.io/ is
a better choice?  What do you think?

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: buzilla 214400: is is ports/head/base/binutils that is being reported on, freebsd-powe...@freebsd.org assignee is wrong

[Mark Linimon]

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 those 3 PRs were correct.

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: How many versions of clang/llvm are currently required to maintain a system

[Mark Linimon]

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

[Mark Linimon]

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 folks want us to wave to fix up all the
bad usages in ports.

We are barely keeping our heads above water as it is.

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: openjdk6-i386 not found

[Mark Linimon]

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

[Mark Linimon]

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
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: The future of portmaster

[Mark Linimon]

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
___
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: The future of portmaster

[Mark Linimon]

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!?!

[Mark Linimon]

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 important question.  Why should we ask
developers to support a version of the OS that doesn't have:

>From https://www.freebsd.org/releases/10.0R/relnotes.html:

 * bhyve, drm2, rasbpi, nvme, several overhauled drivers and carp.

>From https://www.freebsd.org/releases/11.0R/relnotes.html:

 * mpr, mrsas, pms, autofs, other overhauled drivers.

I recommend folks reading this thread should examine those links.

As for things removed from base, my understanding is:

 * we have limited people to fix/regression test all the security problems
   in base/ software.  A few notorious candidates have been factored out
   into ports.

 * there is an overall drive to move to an entirely GPL-free base system.
   Perhaps this is not important to you but there are others to whome this
   is important.

I have some other thoughts on this but I am being called away to deal with
some other crisis ATM.

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!?!

[Mark Linimon]

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
___
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!?!

[Mark Linimon]

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 you think it takes to do such support?

> Why is Linux able to so easily replace FreeBSD?  The desktop is
> gone.  Servers are going.  The new AMD chips are being tested
> against Intel on Linux boxes, not FreeBSD boxes.  FreeBSD is
> being made obsolete.

In other words, if we move fast enough to try to keep up with Linux
changes, FreeBSD is obsolete.  If we move more slowly than Linux, then
FreeBSD is obsolete.

I'm being serious.  We get criticized either way.

Also, for package sets, consider that size * each OS release * each
architecture (ok, some architectures) = a lot of disk space.  We
simply have finite disk space.

IMHO, the days that we can expect ports maintainers and committers to
keep e.g. a FreeBSD 4.11 viable for years are over.  By the EOL of 4.11,
we were asking volunteers to support *4* major OS releases.  That was
crazy.

As for the OS releases, we're trying to keep up with new disk technologies,
new ways of booting, new wireless techniques, graphics APIs that change
rapidly, and on and on.  The pace of these changes is outside our control.
We can keep up or become irrelevant.

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: what's the deal with portsmon? and beefy?

[Mark Linimon]

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 "freebsd-ports-unsubscr...@freebsd.org"

[CFD] changes to Handbook chapter on Ports

[Mark Linimon]

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 controversial.

My aim is twofold:

 - try to make our documentation as useful for our users as possible
   (while still trying to be succinct)

 - try to meet the objections that have arisen about its favorable
   treatment of portupgrade and portmaster.

I don't think the Handbook is the place for a full discussion of
the controversy around these tools (see "succinct").  I'll leave the
judgement about whether that should be a wiki entry, or a new Article,
to someone else.

When I started working on this task, I found that the whole chapter
was stale and sometimes awkward.  I submitted changes to Phabricator as:

  https://reviews.freebsd.org/D8838
  https://reviews.freebsd.org/D8839

which now correspond, respectively, to:

  https://svnweb.freebsd.org/doc?view=revision=49827
  https://svnweb.freebsd.org/doc?view=revision=49828

Although the reviews were made public, only my doc mentor (wblock)
commented.

A followup commit:

  https://svnweb.freebsd.org/doc?view=revision=49829

was only reviewed between he and I.

I am somewhat hopeful that the above commits will invite minimum
controversy.  However, I am reasonably confident that D9124 will.

And now I'll sit back and await feedback.

References: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214679

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' tips and gotchas

[Mark Linimon]

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 over the place and not nicely organized.

For right now I think your pages are fine.

The wiki doesn't have much of a "structure" right now.  I did some prototype
pages for a restructuring but it got bogged down due to internal politics.

It needs several months' worth of surgery.  I nibble at parts of it every
once in a while until I remember why I got frustrated :-)

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: Welcome to our new portmgr members

[Mark Linimon]

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 any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Subscription for committer

[Mark Linimon]

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 [has] to be
> stamped out

People tend to put off working on topics that include "demands".

It's just human nature.

Plus, there are thousands of other PRs to work on that don't involve such
charged language.  Working on those is more rewarding and less frustrating.

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: The ports collection has some serious issues

[Mark Linimon]

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 "freebsd-ports-unsubscr...@freebsd.org"

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

[Mark Linimon]

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 able to boot reliably but would get random crashes
every few days.  That machine has been offline for months, however.

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: mail/mixmaster port issue

[Mark Linimon]

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
___
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: really to pkg people

[Mark Linimon]

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 team.
My supposition is that this is constrained by space on the mirrors.

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: Fwd: [package - 93i386-quarterly][cad/freecad] Failed for FreeCAD-0.17.g20160907_1 in build

[Mark Linimon]

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:
> http://beefy4.nyi.freebsd.org/data/93i386-quarterly/426753/logs/FreeCAD-0.17.g20160907_1.log

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: Binary for Ruby?

[Mark Linimon]

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
http://pkg.freebsd.org/FreeBSD:9:amd64/latest/All/ruby-2.2.6,1.txz
http://pkg.freebsd.org/FreeBSD:9:amd64/latest/All/ruby23-2.3.1_1,1.txz

looks fine ...

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 update submission for multiple ports?

[Mark Linimon]

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.  Bugzilla also gives us the ability to track related
PRs via "Depends on:" and "Blocks:" to help recommend ordering and
dependencies.

You may hear from other people that they don't agree with the above :-)

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: openntpd-5.7p4_2,2 depends on libressl-2.2.6 ?!

[Mark Linimon]

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* know it is harder to fix things and coordinate with people
rather than just bitch, correct?

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: misc/jive deleted

[Mark Linimon]

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(*) removal

I have personally removed ports fitting each of these criteria at various
times.  I am sure I am missing some other criterion as well.

So, your claim is simply false.

mcl

(*) ok, in one case, it was actually a demand, with the threat of legal
action appended.
___
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: misc/sword should be removed

[Mark Linimon]

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 unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: misc/jive deleted

[Mark Linimon]

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
___
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: misc/jive deleted

[Mark Linimon]

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 _you_ can publish anything _you_ want.  It doesn't
mean _you_ can make _other people_ publish what you want them to.

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: misc/jive deleted

[Mark Linimon]

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 in various stages of undress.



It's not delusions of moral superiority.  It's common decency.

There's no "censorship" if the FreeBSD developers make a collective
decision that they don't want to be associated with juvenile junk
that makes them look like a bunch of out-of-touch clueless old white
guys; that instead they would like to look like adults rather than
some adolescent clique; and that instead they would like to seem more
welcoming to people that don't look, think, and talk exactly like
they do.

But your mileage may vary, and in this case, I'm practically certain
of it.

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: misc/jive deleted

[Mark Linimon]

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 to offensive.
If FreeBSD is trying to be more inclusive, having this around isn't
the way.

The "anti" removal point: well, just don't install it, then.

I fall firmly into the former camp, and for the reason stated.  At
least one of the terms could never possibly have been interpreted
as humor in my native Texas.

And particularly in Houston, Texas, where in the late 1970s the term
was used in a police incident, in which the suspect later died.

tl:dr; it's pretty difficult to offend me personally, but when I read
that particular entry, I turned pale.

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: private ports and pkgs versioning

[Mark Linimon]

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"
.endif

Again, I _think_ this is only necessary if you are building INDEX.

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: private ports and pkgs versioning

[Mark Linimon]

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 reading Makefiles and hints dropped on mailing lists.  I
> cannot recall a document describing this stuff anywhere.

I don't believe that there is one.

I'm sure there are N locally-grown solutions out in the wild.

We ought to work together to poll people on what they use.

As for adding the category, I think there's a quick fix, if you don't
care about building INDEX.  Add USE_LOCAL_MK=yes to your Makefile
invocations, and use the patch below.

Note: I haven't tried this yet, so adding the category to ports/Makefile
may also be necessary to pacify ports/Mk/bsd.port.subdir.mk (e.g. INDEX.)

Index: ports/Mk/bsd.local.mk
===
--- ports/Mk/bsd.local.mk   (revision 423944)
+++ ports/Mk/bsd.local.mk   (working copy)
@@ -14,6 +14,8 @@
 # time should live.
 #
 
+VALID_CATEGORIES+= local
+
 .endif # !defined(_POSTMKINCLUDED) && !defined(Local_Pre_Include)
 
 .if defined(_POSTMKINCLUDED) && !defined(Local_Post_Include)

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: pkg: PRE-INSTALL script failed

[Mark Linimon]

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

[Mark Linimon]

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
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: dependency explosions

[Mark Linimon]

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 fly.

(disclaimer: I had to go fix it because it had bitrroted due to some kind
of change in the make -V output somewhere.)

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: Google Code as an upstream is gone

[Mark Linimon]

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 underlying problem will never be fixed.

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: Installing ports via pkg on 11 [ports-mgmt/synth only available for amd64 and i386 on FreeBSD]

[Mark Linimon]

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:

  http://www.dragonlace.net/

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_DATA} problems

[Mark Linimon]

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 intended by make's designers :-)

We do try to document things in the Porter's Handbook, but sometimes
the only thing to do is wade into bsd.port.mk and friends and read the
code.  (Not recomended for the faint of heart, though.)

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: suggested patch for bsd.ports.mk

[Mark Linimon]

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
  the cluster. Examples of such changes that should be tested before 
  committing include:

changes to packages with many dependencies, including X11 servers,
GNOME, KDE, gettext, autotools, and so forth

changes that change the "accepted best practice" for ports Makefiles,
such as definitions or usage of common make variables (or Makevars).
(e.g. consolidation of various implementations of USE_*, WITH_*, and
so forth)

large repocopies (such as when an existing port category is divided up)

  If you are unsure of whether your proposed change will require a regression
  test, please send email to port...@freebsd.org.



What this doesn't say is that, by convention, portmgr tests all changes to
bsd.port.mk on an experimental (exp-) run on the cluster.  The motivation is
that many people auto-update their ports trees every day, and any breakage
generates immediatel, ah, feedback.

In general minor changes are piggybacked onto major changes during an exp-
run.

tl;dr: file a PR and assign to it portmgr@ under 'ports infrastructure'.

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: Removing documentation

[Mark Linimon]

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
___
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: Can we bring back sysutils/cronolog?

[Mark Linimon]

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 at 2116.

We definitely need more ports committers.

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: Hi, I'd like to update the coreos-etcd port!

[Mark Linimon]

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.  You can always use bugzilla to make sure
that portsmon has gotten it right:

  https://bugs.freebsd.org/bugzilla/query.cgi

> The next step in the guide is:
> 
> > If there is no pending PR, the next step is to send an email to the
> > port's maintainer, as shown by make maintainer.

I've always hated that advice :-)  I'd say open a PR.  It gives much
more information as an audit trail.

There is another reference you might want to look at:

  https://wiki.freebsd.org/KubilayKocak/ThePerfectPortsIssue

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: New pkg audit / vuln.xml failures (php55, unzoo)

[Mark Linimon]

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
problem but no conclusive decision yet.  It is, however, a hot topic.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Synchronising ports with package cluster

[Mark Linimon]

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 did.

The hardware was purchased by the FreeBSD Foundation.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Time to be real

[Mark Linimon]

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
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: BIND REPLACE_BASE option

[Mark Linimon]

On Sun, Jan 11, 2015 at 10:38:50PM -0800, Craig Rodrigues wrote:
 Wrong.  I've worked at 3 companies over the years that make direct use of
 the ports tree when creating an embedded product based on FreeBSD.

OK, then this is the first I've heard of it.  My mistake.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: BIND REPLACE_BASE option

[Mark Linimon]

On Mon, Jan 12, 2015 at 01:29:32PM +0100, Michelle Sullivan wrote:
 Just a thought: FreeNAS

FreeNAS uses ports ... in their own way.  Yes, they do contribute back
changes as well.

The point that I was trying to make, even though I used bad data, was
that Ports aren't being driven by external influence.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: BIND REPLACE_BASE option

[Mark Linimon]

On Sun, Jan 11, 2015 at 03:54:39PM -0800, Roger Marquis wrote:
 time for it to go, by whose definition?  Good code doesn't have a
 fixed lifespan and the claimed rationale doesn't constitute a good
 business case.

It was believed to be a bad design pattern to let ports modify anything
in base.  There had been a few exceptions that crept in over the years,
for one reason or another.  Apparently 10.0 seemed like the appropriate
time to get rid of the bad pattern.  (Note: I was not involved in the
decision.)

We've been essentially rewriting the entire ports infrastructure in-place
for the past 6 or 7 years.  IMVHO this was entirely necessary: the old
pkg_* tools were buggy, underdocumented, and no longer suited to the task
of keeping up with over 20,000 ports.  Along the way we've had to throw
out a lot of rotten code both in the infrastructure and various ports --
*and* keep the absolute majority of ports working in the meantime.  This
was no mean feat.
 
 Sometimes you really have to wonder whether these feature deprecations
 are due less to resource shortages than to special interests outside of
 FreeBSD's user-base.

They are mostly due to the idea of not shipping things that do not work
consistently, and in the way one might expect.  On rare occasion, yes,
that will mean breaking POLA.

(Also note I'm not defending the way this change was or was not documented.)

As for special interests, this is specious.  AFAIK the companies that
embed FreeBSD into their products are primarily interested in the kernel,
the networking stack, the file systems, and so on.  I do not know of any
such company that even _uses_ FreeBSD ports.

Thus, they could have no influence on the outcome.

tl;dr: the FreeBSD ports community is pretty well self-contained.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: How does the Additional FreeBSD Contributors page work?

[Mark Linimon]

On Thu, Jan 01, 2015 at 06:05:38PM -0800, Chris H wrote:
 Would anyone be willing to clarify? Or am I simply blacklisted? ;)

The list is not complete.  No doubt you've merely been overlooked, sorry.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: https://svnweb.freebsd.org/ Attic URLs, eg for ports/mail/demime ?

[Mark Linimon]

On Sat, Dec 27, 2014 at 08:20:45AM -0700, Warren Block wrote:
 I think I could make a good case for moving that ports FAQ into the
 Porter's Handbook, even if it is for committers.

Sounds good.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Giving Up Maintainership

[Mark Linimon]

On Mon, Dec 15, 2014 at 08:09:48AM -0600, Rusty Nejdl wrote:
 Sorry guys, but I will have to give up maintainership on my 10 ports as
 I have completely run out of time and am not keeping up with my ports
 and keeping them to standards. I'll jump back in when I can and thank
 you all in advance. 

Thanks for doing this rather than letting them tmie out and stress
yourself.  As a former portmgr I can say this makes portmgrs' lives
easier :-)

Please feel free to send PRs on anything you are still working on.

Thanks.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: what's up with portsmon?

[Mark Linimon]

On Tue, Aug 26, 2014 at 04:34:01PM -0700, Don Lewis wrote:
 What's going on with portsmon.freebsd.org these days?   A number of my
 ports have been updated quite a while ago, but there isn't any updated
 build status on portsmon.

portsmon suffered some bitrot when a vuxml URL grew a | in it.  This
caused index updates to not be updated.  I fixed the bitrot last Sunday
but I should probably do a force-rebuild of the metadata.

 I poked around on one of the pkg.freebsd.org, and stuff looks pretty
 old there as well.  For instance, the timestamps of the files under
 freebsd:10:x86:32/latest/ are 13-Aug-2014.

portsmon only knows about the packages provided by pkg.freebsd.org.
That's a question for the currently active portmgrs.

 But ... if I go to this page
 http://portsmon.freebsd.org/portsoverall.py and select the
 84amd64-default link, I end up at
 http://beefy2.isc.freebsd.org/bulk/84amd64-default/latest/.  If I then
 click on the logs/ link, I find a bunch of build logs dated
 24-Aug-2014.  Looking at protobuf-c-1.0.1.log, it looks like the build
 was a success.

IIUC, the build machines' outputs (e.g. *.isc.freebsd.org) are not automatically
uploaded to pkg.freebsd.org in order to provide a sanity check.

 Other observations:
 
   It would probably be helpful if the individual port pages reported
   the status for the new_xorg versions.

portsmon never had the idea of multiple repositories engineered into it.
This would take a bit of retrofitting.  I'll put it on the todo list.

A shortcut would be to build a new-xorg only version of portsmon.  I
would need to get clusteradm to provision me a new, separate, jail to do
that.  (I have an outstanding request for another one anyways that seems
to be stalled.)

   It would be nice if there was a way to find out what the ports build
   cluster was currently working on.  Things like the svn revision of the
   ports tree, what OS and ARCH versions were currently being built, and
   how far along the build was (basically what you see when you type ^T
   during a poudriere run), and what's next the the queue.

portsmon is not really tightly coupled to the build machines.  I suppose
I could teach it more about poudriere but that makes the code a lot more
specific than it is right now.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Building subversion-1.8.10 under poudriere

[Mark Linimon]

On Wed, Aug 27, 2014 at 05:30:22PM -0500, Lawrence K. Chen, P.Eng. wrote:
 Wonder if there's still time to now see what ports I have installed that
 haven't been staged yet?

This doesn't quite answer your question, but there's a portsmon page
listing all nonstaged ports:

http://portsmon.freebsd.org/portsconcordancefornostage.py?sortby=portname

The current count shown is 637.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Some suggestions about PKGNG documentation

[Mark Linimon]

On Fri, Jul 04, 2014 at 07:00:00PM -0600, Mike Brown wrote:
 After starting down this road, you may decide it's less of an ordeal just to 
 write something yourself and put it up on your own blog. :/

There are those of us who will do our best to pick up changes and run with
them.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.

[Mark Linimon]

On Wed, Jul 02, 2014 at 07:43:17PM +0200, Daniel Ryslink wrote:
 I was quite seriously ill for some time, and I have only now noticed
 these messages. I am the maintainer of the games/gnarr port.

Please take care of yourself.  Fixing ports should be secondary.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: maven and ports that try to fetch files during build stage

[Mark Linimon]

On Sat, Jun 21, 2014 at 12:02:32PM -0500, Pedro Giffuni wrote:
 This is a problem with the Apache POI port but it is also an issue
 with a potential Apache hadoop update: apparently our cluster
 doesn't like ports that download stuff as part of their build

s/doesn't like/doesn't allow/

This is intentional so that we can understand exactly what it being
installed by the port.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: FreeBSD ports that you maintain require staging updates

[Mark Linimon]

On Fri, Jun 13, 2014 at 09:35:53AM +0900, oyaaji wrote:
 Dear Sir/Madam,
 
 I have received following e-mail.
 However I am not a port maintainer and never was.

Apparently this was sent to a mailing list:

 To: v...@freebsd.org

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: FreeBSD ports that you maintain require staging updates

[Mark Linimon]

On Tue, Jun 10, 2014 at 04:53:17PM +1000, Dylan Leigh wrote:
 Don't know anything about staging yet but I will take maintainership
 and do it if noone else is willing to save the port.

If you're not familiar with port maintainership, here are the best
places to start:

  http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/

  http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/

  https://wiki.freebsd.org/ports/StageDir

Please feel free to ask questions.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: FreeBSD ports that you maintain require staging updates

[Mark Linimon]

On Mon, Jun 09, 2014 at 08:20:52PM +0200, Eric Masson wrote:
 I don't use lpr-wrapper anymore, it seems to me that lpr-wrapper  psdim
 have been superseded by P. Selinger's upprint :
 http://www.mathstat.dal.ca/~selinger/upprint/
 
 Thanks for resetting maintainer, please.

Done, thanks.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Who was the mental genius

[Mark Linimon]

On Sun, Jun 08, 2014 at 12:42:27AM +0200, John Marino wrote:
 The next time you are right will be the first time. [...] You are being
 ridiculed because you're a boor and consistently wrong, which is not a
 good combination.

None of the above represents what I think FreeBSD ought to be about.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org