RE: Begone, accursed poudriere partitions!

[driesm.michiels]

> -Original Message-
> From: owner-freebsd-po...@freebsd.org 
> On Behalf Of George Mitchell
> Sent: Wednesday, 7 April 2021 20:18
> To: freebsd ports 
> Subject: Begone, accursed poudriere partitions!
> 
> On one occasion, probably a couple of years ago, I tried poudriere out.
> I decided it was too heavy for my use case and uninstalled it.  Ever since,
> though, every time my build machine reboots, *something* recreates a whole
> poudriere tree on my ZFS file system, with a total of ten mountpoints 
> littering
> my daily report (though apparently only 139K of actual data).  Then I have to
> repeat a ritual of "chflags -R noschg", "rm -r", "zfs umount $x" for each of 
> the
> mount points.

So what you happen to do is manually unmount each ZFS dataset.
That does not mean the ZFS datasets are gone or wont be mounted on the next 
(re)boot.
As long as the datasets exist and canmount=on, it will get mounted every time.

The easiest fix is to delete the zfs datasets that poudriere created.
You can find the correct dataset with
# zfs list

 And then most probably
# zfs destroy -r zroot/poudriere

> 
> How do I stop them from coming back from the dead?-- George


___
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: FreeBSD Port: dhcpcd-9.1.0

[driesm.michiels]

> -Original Message-
> From: owner-freebsd-po...@freebsd.org  po...@freebsd.org> On Behalf Of Douglas Thrift
> Sent: zondag 7 juni 2020 1:54
> To: woods...@freebsd.org
> Cc: po...@freebsd.org
> Subject: FreeBSD Port: dhcpcd-9.1.0
> 
> Hello,
> 
> I just upgraded to dhcpcd 9.1.0 and I'm running into some weird issues.
> The first thing I noticed was that the value for `pidfile` changed which
made a
> `service dhcpcd restart igb0` fail initially. After figuring this out, I
was able to
> stop the previous dhcpcd manually and then I discovered that the `pidfile`
> was still incorrect:
> 
> pidfile="/var/run/dhcpcd/dhcpcd-$ifn.pid"
> 
> should actually be:
> 
> pidfile="/var/run/dhcpcd/$ifn.pid"
> 
> However, even after changing that, running `service dhcpcd start igb0` was
> sticking to the foreground rather than daemonizing and returning me to a
> prompt. I tried a number of ways to pass the -b/--background flag, but
even
> just running `dhcpcd -b igb0` manually did not daemonize.

I reckon you are running FreeBSD 13-CURRENT (as I am)?
I actually had the same problem and noticed some error messages in
/var/log/messages.log.
Roy has provided a patch for the dhcpcd source in attachments, this fixed it
for me.
It has already been committed to master and should be fixed in the new
dhcpcd-9.1.1 release. 

> Could you look into these issues?
> 
> Thanks!
> --
> Douglas William Thrift
> 
> ___
> 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"


dhcpcd-buf.diff
Description: Binary data
___
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"

Committer needed: multimedia/emby-server Update to 4.4.2.0

[driesm.michiels]

Hi ports mailing list!

 

Could a committer take a look at the following PR please?

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

 

Thanks!

Dries

___
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: Porting of Smallstep CA

[driesm.michiels]

> -Original Message-
> From: owner-freebsd-po...@freebsd.org 
> On Behalf Of Markus Wipp
> Sent: dinsdag 7 april 2020 22:08
> To: freebsd-ports@freebsd.org
> Subject: Porting of Smallstep CA
> 
> Hi all,
> 
> I would like to create a port of the CA tool (basically two ports: cli and
> certificates) found on https://github.com/smallstep https://smallstep.com/
> 
> What I tried so far was:
> 1) make it on my machine without the ports infrastructure. This basically
> works fine and without any errors and modifications needed ( I just do a
> gmake bootstrap and then a gmake build )
> 2) tried to create a port using the guide at
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-
> handbook/quick-porting.html
> 3) tried Slow porting, but I think I’m not really understanding how and where
> to begin
> 
> The main issue is, that I don’t really know what I have to do here, to achieve
> what’s required to correctly build the port.
> It is the very first time I’m trying to create a port.
> 
> My Makefile looks like this:
> 
> # $FreeBSD $
> 
> PORTNAME= step-cli
> DISTVERSIONPREFIX=v
> DISTVERSION=  0.14.0-rc.4
> CATEGORIES=   security
> MASTER_SITES=
>   https://github.com/smallstep/cli/releases/download/v${DISTVERSION
> }/
> #PKGNAMESUFFIX=   0.14.0-rc.4
> DISTNAME= ${PORTNAME}_${DISTVERSION}
> MAINTAINER=   mw@wipp.bayern
> COMMENT=  Smallstep step-ca command line client
> LICENSE=  APACHE20
> 
> #WRKSRC=  ${WRKDIR}/step-cli
> WRKSRC=   ${WRKDIR}/
> NO_WRKSUBDIR= yes
> 
> BUILD_DEPENDS=go>1:lang/go \
>   bash>5:shells/bash \
>   curl>7:ftp/curl \
>   golint:devel/golint
> 
> USES= gmake
> MAKE_ARGS=build
> 
> 
> .include 
> 
> 
> When I try to run make stage on this I get:
> root@pkgbuild:/usr/ports/security/step-cli # make stage ===>  Building for
> step-cli-0.14.0.r.4
> gmake[1]: Entering directory '/usr/ports/security/step-cli/work'
> /bin/sh: golangci-lint: not found
> gmake[1]: *** [make/common.mk:101: lint] Error 127
> gmake[1]: *** Waiting for unfinished jobs
> go: finding module for package github.com/envoyproxy/protoc-gen-
> validate/tests/harness/cases/go
> go: finding module for package
> github.com/shurcooL/github_flavored_markdown
> go: finding module for package github.com/samuel/go-zookeeper/zk
> go: finding module for package github.com/mozilla/scribe
> go: finding module for package golang.org/x/mobile/event/lifecycle
> go: finding module for package github.com/lyft/protoc-gen-star
> go: finding module for package github.com/ethereum/go-ethereum/ethclient
> go: finding module for package github.com/BurntSushi/xgb
> go: finding module for package github.com/ethereum/go-ethereum/rlp
> go: finding module for package github.com/oklog/oklog/pkg/group
> go: finding module for package github.com/influxdata/influxdb1-client/v2
> go: finding module for package gopkg.in/yaml.v1
> go: finding module for package github.com/hashicorp/consul/api
> go: finding module for package github.com/openzipkin/zipkin-go
> go: finding module for package github.com/iancoleman/strcase
> go: finding module for package github.com/BurntSushi/xgb/shm
> go: finding module for package golang.org/x/mobile/event/key
> go: finding module for package golang.org/x/image/math/fixed
> go: finding module for package github.com/gorilla/mux
> go: finding module for package github.com/ianlancetaylor/demangle
> go: finding module for package github.com/openzipkin-contrib/zipkin-go-
> opentracing
> go: finding module for package go.mozilla.org/mozlog
> go: finding module for package github.com/nats-io/nats.go
> go: finding module for package github.com/envoyproxy/protoc-gen-
> validate/tests/harness/go
> go: finding module for package github.com/Sirupsen/logrus
> go: finding module for package bitbucket.org/creachadair/shell
> go: finding module for package github.com/envoyproxy/protoc-gen-
> validate/tests/harness/gogo
> go: finding module for package
> sourcegraph.com/sourcegraph/appdash/opentracing
> go: finding module for package github.com/remyoudompheng/go-misc/zipfs
> go: finding module for package github.com/benlaurie/gds-registers/register
> go: finding module for package github.com/BurntSushi/xgb/render
> go: finding module for package github.com/shurcooL/gopherjslib
> go: finding module for package github.com/openzipkin/zipkin-
> go/reporter/http
> go: finding module for package golang.org/x/mobile/event/paint
> go: finding module for package sourcegraph.com/sourcegraph/appdash
> go: finding module for package github.com/VividCortex/gohistogram
> go: finding module for package github.com/shurcooL/httpfs/vfsutil
> go: finding module for package github.co

RE: Question for users and consumers of lang/mono and NuGet

[driesm.michiels]

> All;
> 
> Since I work with Mono extensively at home and at work, I've been working
> closely with the Mono Project folks to get things compiling and running
much
> more cleanly on FreeBSD. And I'm very happy to say that excellent progress
> has been made including a number of patches upstream.
> 
> The Mono Project has just released the latest stable, 6.0.0.313, which is
a
> major upgrade. Not all Mono 5.x projects may work on it, they need tested,
> etcetera. But 6.0.0.313 needs only two patches already committed upstream
> and one corefx patch. The Mono Project honestly seems pretty keen on
> having FreeBSD as a 'first class' citizen, and is even working on adding
> FreeBSD to their CI pipeline.

Just my 2 cents; this is awesome news! 
Many will be happy about a new mono version getting in the tree.

> 
> But at the same time, lang/mono has basically languished on 5.10, which
has
> numerous known bugs and performance issues. These have been addressed
> in later versions, which also compile MUCH easier. Add to that,
> Uses/mono.mk is still using obsoleted repositories and setups that haven't
> been current in more than a year now.
> 
> Simply put, leaving lang/mono 'as-is' should not be viewed as a realistic
> option. Yes, it's still 'supported' upstream 'officially.' But it's really
not, and
> it's really a problem. That said, it's also not necessarily feasible to
just
> replace lang/mono with 5.18 stable as this may break some consumers.
> I have already completed the work to get Mono versions 5.14 through 5.20
> and 6.0.0.313 building and passing all Mono tests on FreeBSD. These are
all
> ready to go. And not solely on amd64; most are ready to go on aarch64, and
> 5.18+ should be able to do ppc64.
> 
> The question therefore, is one of versions and layout. Mono does NOT have
> a DEFAULT_VERSIONS and to be quite honest, adding one to the existing
> infrastructure is beyond my abilities. (Believe me, I tried.) I also do
not know
> what out there is using the existing NuGet stuff in Uses/mono.mk. So I
don't
> know if it's safe to just rip it all out.
> 
> My personal preference here would be to add DEFAULT_VERSIONS+=mono,
> rename lang/mono to mono5.10, and add lang/mono5.[16,18,20] and
> lang/mono6[.0,-devel]. This isn't something I've had any luck with, and I
> never heard back from mono@ when I reached out for guidance and
> assistance there. So I would need someone to help me with adding that
> support. If someone can give me a DEFAULT_VERSIONS switch, I can carry it
> the rest of the way, no problem.
> Option two is to leave lang/mono to rot and to create new ports for each
> version, and rely on the user or consumer to select the correct version.
> This however, creates a problem in that now net-p2p/sonarr might want
> 5.18 and net-p2p/radarr wants 5.20, and both versions of Mono require
files
> be installed in the same locations. So obviously, it's not the preferred
or
> optimal solution. (Generally speaking anything good with
> 5.18 will run with 5.20 and vice versa since it's more about the .NET
level, but
> there are bugs and known issues a given app may be impacted by.)
> 
> So if your port or you use mono or NuGet, I would very much appreciate
your
> feedback here before I submit a raft of patches that might have impacts to
> your stuff. ;) But I most definitely would appreciate any feedback or
guidance
> folks could provide here so I can get these updates into the tree as soon
as
> possible.
> 
> Thanks in advance!
> 
> -Phillip R. Jaenke | p...@rootwyrm.com
>  "I didn't break it. I made it a test of common sense." -anon.
> ___
> 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"

___
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"

Committer needed multimedia/emby-server update to 4.1.1.0

[driesm.michiels]

Hi Ports Mailing list,

 

Can a committer take a look at the following PR:

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

This PR updates emby-server to the latest version and also fixes another bug
regarding the port.

If there's anything else that needs to be done to get this in the tree
please post in the PR.

 

Thanks!

Dries

___
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: Conditionally install the correct binary

[driesm.michiels]

> -Original Message-
> From: Jonathan Chen 
> Sent: donderdag 9 mei 2019 21:56
> To: driesm.michi...@gmail.com
> Cc: freebsd-ports@freebsd.org
> Subject: Re: Conditionally install the correct binary
> 
> On Fri, 10 May 2019 at 07:47,  wrote:
> [...]
> > What is the easiest way to conditionally fetch and install a binary
> > depending on FreeBSD OS version.
> 
> x11-fonts/fantasque-sans-mono uses conditional fetching depending on
> OPTIONS. The distinfo contains checksums for all the tarballs, but the port
> only fetches tarballs matching the selection options.


So I have to make the FreeBSD version an option in the port and get it toggled 
based on OS_VERSION.


> 
> You can adapt this strategy to depend on OSVERSION.
> 
> Cheers.
> --
> Jonathan Chen 

___
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"

Conditionally install the correct binary

[driesm.michiels]

Hi ports mailling list!

 

What is the easiest way to conditionally fetch and install a binary
depending on FreeBSD OS version.

Lets say that upstream has 2 tarballs in the repo; tarball11 and tarball12.

Tarball11 is only necessary to download and install when the OS version is
FreeBSD 11.

Tarball12 is only necessary to download and install when the OS version is
FreeBSD 12.

 

Any port as an example to look at? I tried grepping OSVERSION in the
Makefiles but didn't really find what I was looking for.

 

Regards,

Dries

 

___
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"

dbus getting installed with vim

[driesm.michiels]

Hi ports,

 

I like to keep my system free of DBUS, HAL and CUPS.

For the above reason stated I use a package builder that has following
options set:

*   OPTIONS_UNSET += CUPS DBUS HAL

 

I noticed that with the newest update of vim it tries to install dbus with
it.

*   For reference:
https://svnweb.freebsd.org/ports?view=revision&revision=491810

 

Is there anything I can do to avoid this beside unsetting the above stated
options?

 

Thanks!

 

 

___
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"