Re: Help with changing gitlab based download urls in ports

[Matthias Fechner]

Am 07.04.2021 um 17:12 schrieb Matthias Fechner:

This also causes gitlab-ce to be not fetchable anymore.
I already created a review to fix this here (sry, it also includes an 
upgrade of gitlab-ce, but without the upgrade, it would not be 
possible to testbuild this modification):

https://reviews.freebsd.org/D29628


the problem is now fixed in main and 2021Q2.

Matthias

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

Help with changing gitlab based download urls in ports

[Matthias Fechner]

Dear all,

gitlab seems to have deactivated a path FreeBSD is currently using to 
download packages hosted on gitlab.com.


This also causes gitlab-ce to be not fetchable anymore.
I already created a review to fix this here (sry, it also includes an 
upgrade of gitlab-ce, but without the upgrade, it would not be possible 
to testbuild this modification):

https://reviews.freebsd.org/D29628

But I need some help.

If I do not define a new WRKSRC in the port itself, it does not compile.
It seems that somewhere I forgot to modify the WRKSRC.

I do not know the bsd.*.mk files to fully understand the problem.

Any help is really appreciated.

Thanks!

Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: When did pkg(8) drop support for 12-STABLE?

[Matthias Fechner]

Am 24.02.2021 um 00:31 schrieb Chris:
It was from a 12-STABLE usb stick (probably 12.1). Is there no way 
forward, save
building up to 12.2? 


yes:

freebsd-update upgrade -r 12.2-RELEASE
freebsd-update install
# nextboot -k GENERIC
reboot
freebsd-update install
# check that config files in etc are correct!
reboot
# Make sure you point pkg repo definition to correct FreeBSD version
pkg update -f
pkg-static install -f pkg
pkg-static upgrade -F -y
pkg upgrade -f -y
freebsd-update install
reboot

Check for more details the documentation:
https://docs.freebsd.org/en/books/handbook/updating-upgrading-freebsdupdate.html

Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Mailman 3 port

[Matthias Fechner]

Am 15.02.2021 um 23:08 schrieb Dan Mahoney (Gushi):

Is anyone working on a mailman 3 port?

(I'm guessing it would be several ports, actually, as mailman 3 is 
several different moving parts). 


I migrated everything to sympa.
I used the following scripts to do this:
https://gitlab.fechner.net/mfechner/mailman2sympa

But these script require python2 which does not exist anymore, so the 
migration can be a bit tricky.

But maybe you find some old packages for python2.

Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Github redirects for go based ports seems to be not working as expected

[Matthias Fechner]

Thanks Steve,

Am 22.10.2020 um 22:24 schrieb Steve Wills:
Probably some GitHub internal issue with the codeload.github.com site. 
Probably not much we can do except update the URLs. I'd love to be 
wrong tho.


I already tried to that this fixed upstream, but it seems that I have to 
manually patch for a longer time I wanted ;(


But thanks for your answer!

Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: poudriere merging multiple ports trees

[Matthias Fechner]

Am 25.01.2021 um 08:19 schrieb Guido Falsi via freebsd-ports:
There already is a git mirror of the ports tree, so you could also 
start doing this now. Only problem is, when the tree is converted you 
would probably have a messy time migrating to the new tree, which, I 
guess, will have new commit hashes, like it happened for source.


I think if you follow what is explained here:
https://github.com/bsdimp/freebsd-git-docs

Mainly this one:
https://github.com/bsdimp/freebsd-git-docs/blob/main/mini-primer.md#migrating-from-an-existing-git-clone

You should not have big problems even if the commit hashes will change.


Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: devel/ruby-gems strange ?

[Matthias Fechner]

Am 23.11.2020 um 07:09 schrieb KIRIYAMA Kazuhiko:

===>   rubygem-asciidoctor-2.0.10 depends on file: /usr/local/bin/gem30 - found
===>   Returning to build of rubygem-asciidoctor-2.0.10
ERROR:  While executing gem ... (Gem::Package::FormatError)
 package is corrupt, exception while verifying: wrong number of arguments 
(given 2, expected 1) (ArgumentError) in 
/var/ports/distfiles/rubygem/asciidoctor-2.0.10.gem
*** Error code 1


I saw a similar problem with gitlab-ce in the upgrade to 13.6.0.

The cause of this error for gitlab was, that is requires ruby 2.7 and 
does not work anymore with ruby 2.6.


The switch to ruby 2.7 is tracked here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244787

Maybe you want to give it a try with ruby 2.7?

Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Github redirects for go based ports seems to be not working as expected

[Matthias Fechner]

Dear all,

I maintain some ports having outdated information in the go definition.
With outdated I mean that the project as moved in github to another group.

An example you can find here:
https://gitlab.fechner.net/mfechner/Gitlab/-/commit/12380a1a2e726938175a7445396665091e3363d4

The link:
https://github.com/codahale/hdrhistogram

changed to:
https://github.com/HdrHistogram/hdrhistogram-go

So it was necessary to also modify the line in the Makefile from:
|codahale:hdrhistogram:3a0bb77429bd:codahale_hdrhistogram/vendor/github.com/codahale/hdrhistogram 
\|


to:
|HdrHistogram:hdrhistogram-go:3a0bb77429bd:codahale_hdrhistogram_go/vendor/github.com/codahale/hdrhistogram 
\|


|Only after this, the download was working again.
If a try to download the files manually in the browser, both links are 
working:|


https://codeload.github.com/|codahale|/hdrhistogram/tar.gz/3a0bb77429bd?dummy=/|codahale|-hdrhistogram-3a0bb77429bd_GH0.tar.gz 



https://codeload.github.com/HdrHistogram/hdrhistogram-go/tar.gz/3a0bb77429bd?dummy=/HdrHistogram-hdrhistogram-go-3a0bb77429bd_GH0.tar.gz

Does anyone have an idea why ports cannot download the old version but must use 
the one with renamed group and project?

Thanks a lot!


Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: grpc-1.22.0_4,2

[Matthias Fechner]

Dear Joseph,

Am 05.10.2020 um 18:58 schrieb Joseph Mingrone:

Are we able to update devel/grpc?

I can see from the commit logs that there were some constraints with
updates in the past, but we are now running into trouble, because other
ports in the tree require newer versions of grpc.  For example,
devel/bear requires gRPC >= 1.26.  If necessary, I can/try/  to create a
separate port, say devel/grpc13.


maybe you want to help, there is currently an issue with grpc, please 
see here:

https://github.com/grpc/grpc/issues/22845

I currently test a rubygem-grpc update I received from sunpoet, but have 
currently another problem, that blocks me from continue testing:

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

So if you want to help us, you are more than welcome ;)

Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Seeing packaging problems since about 1-2 days (Requesting argument %2 while only 1 arguments are available)

[Matthias Fechner]

Am 02.10.2020 um 13:22 schrieb Niclas Zeising:
There's been another round of fixes for this.   Try again after the 
update of pkg to 1.5.7.

Regards


thanks all, problem is fixed.
Will now be able to release a gitlab-ce security update ;)

Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Seeing packaging problems since about 1-2 days (Requesting argument %2 while only 1 arguments are available)

[Matthias Fechner]

Am 02.10.2020 um 10:32 schrieb Yasuhiro KIMURA:

Probably it is fixed with r550901.


I don't think so, as I build with r551051:

https://pkg.fechner.net/build.html?mastername=121amd64-default=2020-10-02_10h10m03s


Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Seeing packaging problems since about 1-2 days (Requesting argument %2 while only 1 arguments are available)

[Matthias Fechner]

Dear all,

I see recently new package errors like (this also affects ports I maintain):

===>  Building package for avahi-app-0.7_3
pkg-static: Requesting argument %2 while only 1 arguments are available
pkg-static: Requesting argument %2 while only 1 arguments are available

Anyone an idea what caused this and how to fix it?

Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Help with go based port (invalid flag in pkg-config --libs: -D_THREAD_SAFE )

[Matthias Fechner]

Am 23.09.2020 um 22:46 schrieb Fernando Apesteguía:

I found this:

https://fipress.org/knowledge/invalid-flags-in-cgo-ldflags-pkg-config-or-invalid-flag-in-pkg-config


thanks a lot, I was able to fix by whitelisting the linker flag:

https://gitlab.fechner.net/mfechner/Gitlab/-/commit/b279e2a7c597f7fc43750e3fbdea381d4ae0e7da#bb7d21b8cd0b80c3126fb42d4410d6178b8150aa_13_16


Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Help with go based port (invalid flag in pkg-config --libs: -D_THREAD_SAFE )

[Matthias Fechner]

Dear all,

I currently package a new gitaly version which is required for gitlab-ce 
13.4.0.


The current version I have now can be found here:
https://gitlab.fechner.net/mfechner/Gitlab/-/tree/13.4/devel/gitaly

But for this port there are a lot of upstream changes which causes now 
some problems compiling it.


It seems that a new go dependency is added that requires libgit2 as a 
dependency.


I used the following command to better see the error message:
poudriere testport -p gitlab -j 121amd64 -i devel/gitaly

In the shell I executed then:
cd 
/wrkdirs/usr/ports/devel/gitaly/work/gitaly-cf359cb573106371a6026bd85c3145caabf8c06b-cf359cb573106371a6026bd85c3145caabf8c06b/

gmake

And then a tried the following:
cd /root/go/pkg/mod/github.com/libgit2/git2go/v30@v30.0.5
pkg-config --cflags --static -- libgit2
pkg-config --libs --static -- libgit2
go build github.com/libgit2/git2go/v30: invalid flag in pkg-config 
--libs: -D_THREAD_SAFE


I think the problem is somehow related to the output of:
pkg-config --libs --static -- libgit

which shows:
-L/usr/local/lib -lgit2 -lrt -pthread -lz -L/usr/local/lib -lssh2 
-L/usr/local/lib -lssl -L/usr/local/lib -pthread -lcrypto -pthread 
-lpcre -D_THREAD_SAFE -pthread


The error message I was able to found in the log:
go build github.com/libgit2/git2go/v30: invalid flag in pkg-config 
--libs: -D_THREAD_SAFE


The full log is here:
https://pkg.fechner.net/data/121amd64-gitlab/2020-09-23_11h17m24s/logs/errors/gitaly-13.4.0.log

The log is really hard to read, as go executed several compiles at once.

I tried to limit it to one thread using:
GO_BUILDFLAGS+= "-x -p 1"

but this does not work.

I tried to add compiler:c11 to the use flags, but this does not help (it 
seems that pkgconfig is for sure required).
It would be really great if someone could help me, fixing this problem 
so I can release the next gitlab-ce 13.4 upgrade.


Thanks a lot.


Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook


___
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: devel/rubygem-rbtrace fails in 2019Q4

[Matthias Fechner]

Hi Steve,

Am 31.10.2019 um 18:10 schrieb Steve Wills:
> The packages aren't built with stage-qa run:
>
> http://beefy9.nyi.freebsd.org/data/112amd64-default/latest-per-pkg/rubygem-rbtrace-0.4.11.log
>
> http://beefy6.nyi.freebsd.org/data/120amd64-default/latest-per-pkg/rubygem-rbtrace-0.4.11.log
>
> http://beefy18.nyi.freebsd.org/data/head-amd64-default/latest-per-pkg/rubygem-rbtrace-0.4.11.log
>
>
> so they are showing no issue, your build has it enabled. I was able to
> reproduce the issue and put up a review with an ugly but functional
> patch:
>
> https://reviews.freebsd.org/D22207

thanks, build is running, but takes some hours to complete.

I will try to test it the coming week.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

devel/rubygem-rbtrace fails in 2019Q4

[Matthias Fechner]

Dear all,

has anyone an idea, why devel/rubygem-rbtrace  fails to build in 2019Q4
branch?
https://pkg.fechner.net/data/120amd64-2019Q4/2019-10-31_12h47m53s/logs/errors/rubygem-rbtrace-0.4.11.log

It must be something related not the the port itself, but I cannot find
what commit has to be MFHed to fix this.

Currently it prevents gitlab-ce from being buildable in 2019Q4:
https://pkg.fechner.net/build.html?mastername=120amd64-2019Q4=2019-10-31_12h47m53s

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook




signature.asc
Description: OpenPGP digital signature

Re: How to package maven based ports

[Matthias Fechner]

Am 14.07.2019 um 00:23 schrieb Jonathan Chen:
> Have a look at the java/eclipse port. It uses a pre-warmed maven
> repository that is fetched from github.
>
> You can create a localised repository that only contains the
> dependancies required by the project by specifying:
>   -D maven.repo.local=/my/local/repo
>
> Once your project builds correctly, you can create a repo as a project
> on Github with its contents that can be retrieved with the port for
> the build.

thanks a lot for this.
I'm not fully done with the port, but I was able to get this maven
repository to be pushed to github and the port downloads it and
compilation works as expected.
Thanks a lot for you answer, it helped a lot.

Now I need someone for testing the port, as I do not use it and are
therefor I'm not able to test it.

The final step would be to do some clean up a make the port more pretty.

I try later to write a short summary if some one else needs to build a
port with maven how it could be done.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

How to package maven based ports

[Matthias Fechner]

Dear all,

I just look into the port math/jts.
The new versions do provide only sources and they build with maven.

But as maven fetch all dependencies while building (which is not allowed
with poudriere) what is the best here to solve this problem?

The current version I have is:
https://gitlab.fechner.net/mfechner/Gitlab/tree/12.0/math/jts

I tried to search in the ports how other maintainers are solving the
problem, but I do not fully understand it.
I could also not find anything in the Porters Handbook:
https://www.freebsd.org/doc/en/books/porters-handbook/

It looks like, that they build the package, archive this built package
and upload it to a remote repository?

Any help is really appreciated.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook


___
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 to handle go dependencies

[Matthias Fechner]

Am 22.06.2019 um 11:58 schrieb Matthias Fechner:
> What is the correct way to getting these dependencies fetched and
> correctly included into the work-source in the fetch step using go?


Here a short summary what I had to do to build the port successfully
with go deps.
Thanks a lot for all that helped here!

Add:
USES=    go:modules

I had to use this USES as the port is using gmake to build everything:
USES=    gmake go:modules,no_targets

As gmake is used, the GOFLAGS must be passed to gmake with:

MAKE_ENV=    GOFLAGS="${GO_BUILDFLAGS}"

The port uses gitlab to fetch the distfiles, so I had to tell the ports
that github is not the default:
USE_GITHUB=    nodefault

The next step is then to create the GH_TUPLE and GL_TUPLE (depending
where the go libs are hosted, for they were on github and gitlab).
For this a very handy tool from Dmitri is existing: ports-mgmt/modules2tuple

To simplify it, I create a new target:
gomod-deps: patch
    (cd ${WRKSRC} && go mod vendor)
    (cd ${WRKSRC} && modules2tuple vendor/modules.txt)

Just execute `make gomod-deps` and you should see the required
GH/GL_TUPLE lines.

For the GL_TUPLE lines I had to put in the full length for the commit
hash, as the short one does not work.
I'm not sure if this is a port problem or a gitlab limitation, a task
for later to look into it.

The last section of the TUPLE line must not contain the character `-` if
this is the case, replace it by a `_`.
I think the script from Dmitri is doing this already for the GH_TUPLE lines.

Put the TUPLE lines into the Makefile, run `make makesum` and your port
should be prepare to be able to build.

If you need a full example, please have a look into devel/gitaly.

Have fun and thanks again to all that helped me!

   

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook




signature.asc
Description: OpenPGP digital signature

Re: How to handle go dependencies

[Matthias Fechner]

Dear Dmitri,

Am 07.07.2019 um 00:10 schrieb Dmitri Goutnik via freebsd-ports:
> It appears that Go build flags need to be passed down to `go build` 
> invocation 
> with MAKE_ENV:
>
> +MAKE_ENV=   GOFLAGS="${GO_BUILDFLAGS}"
>
> With that change, the build then fails later due to missing 
> statFileSystemType 
> func definition for freebsd:
>
> # gitlab.com/gitlab-org/gitaly/internal/helper/fstype
> internal/helper/fstype/fstype.go:7:15: undefined: statFileSystemType
>
> Which can be fixed by just copying the linux version (this probably needs to 
> be upstreamed):
>
> post-patch:
>   ${REINPLACE_CMD} -e "s|%%PREFIX%%|${PREFIX}|" 
> ${WRKSRC}/config.toml.example
>   ${MV} ${WRKSRC}/config.toml.example ${WRKSRC}/config.toml.sample
> +   ${CP} ${WRKSRC}/internal/helper/fstype/detect_linux.go 
> ${WRKSRC}/internal/helper/fstype/detect_freebsd.go

thanks a lot for your help!
Without your help the upgrade to www/gitlab-ce 12.0.3 would not have
been possible.
This go stuff is really not that simple.

I reported the upstream change here:
https://gitlab.com/gitlab-org/gitaly/issues/1768

Gitlab-ce 12.0.3 is now commited ;)

Thanks again.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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 to handle go dependencies

[Matthias Fechner]

Am 06.07.2019 um 21:48 schrieb Dmitri Goutnik:
> -USES= gmake go:no_targets
> +USES= gmake go:modules,no_targets
>
> It adds -mod=vendor build flag that tells Go to not try to download
> anything and assume that all dependencies are already in vendor directory.

hm, it does not seems to have any impact it does not stop to complain:
# go install
go: finding github.com/grpc-ecosystem/go-grpc-middleware v1.0.0
go: finding github.com/cloudflare/tableflip
v0.0.0-20190329062924-8392f1641731
go: finding google.golang.org/genproto v0.0.0-20181202183823-bd91e49a0898
go: finding github.com/libgit2/git2go v0.0.0-20190104134018-ecaeb7a21d47
go: finding github.com/prometheus/client_golang v0.9.3
go: finding golang.org/x/net v0.0.0-20190311183353-d8887717615a
go: finding gitlab.com/gitlab-org/gitaly-proto v1.32.0
go: finding github.com/stretchr/testify v1.2.2
go: finding gitlab.com/gitlab-org/labkit v0.0.0-20190221122536-0c3fc7cdd57c
go: finding github.com/BurntSushi/toml v0.3.1
go: golang.org/x/net@v0.0.0-20190311183353-d8887717615a: Get
https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20190311183353-d8887717615a.info:
dial tcp 172.217.20.113:443: connect: can't assign requested address
go: gitlab.com/gitlab-org/gitaly-proto@v1.32.0: Get
https://proxy.golang.org/gitlab.com/gitlab-org/gitaly-proto/@v/v1.32.0.info:
dial tcp 172.217.20.113:443: connect: can't assign requested address
go: github.com/prometheus/client_golang@v0.9.3: Get
https://proxy.golang.org/github.com/prometheus/client_golang/@v/v0.9.3.info:
dial tcp 172.217.20.113:443: connect: can't assign requested address
go: finding github.com/tinylib/msgp v1.1.0
go: github.com/cloudflare/tableflip@v0.0.0-20190329062924-8392f1641731:
Get
https://proxy.golang.org/github.com/cloudflare/tableflip/@v/v0.0.0-20190329062924-8392f1641731.info:
dial tcp 172.217.20.113:443: connect: can't assign requested address
go: finding golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a
go: finding gopkg.in/yaml.v2 v2.2.2
go: finding github.com/getsentry/raven-go v0.1.2
go: gitlab.com/gitlab-org/labkit@v0.0.0-20190221122536-0c3fc7cdd57c: Get
https://proxy.golang.org/gitlab.com/gitlab-org/labkit/@v/v0.0.0-20190221122536-0c3fc7cdd57c.info:
dial tcp 172.217.20.113:443: connect: can't assign requested address
go: google.golang.org/genproto@v0.0.0-20181202183823-bd91e49a0898: Get
https://proxy.golang.org/google.golang.org/genproto/@v/v0.0.0-20181202183823-bd91e49a0898.info:
dial tcp 172.217.20.113:443: connect: can't assign requested address
go: github.com/BurntSushi/toml@v0.3.1: Get
https://proxy.golang.org/github.com/%21burnt%21sushi/toml/@v/v0.3.1.info:
dial tcp 172.217.20.113:443: connect: can't assign requested address
go: github.com/grpc-ecosystem/go-grpc-middleware@v1.0.0: Get
https://proxy.golang.org/github.com/grpc-ecosystem/go-grpc-middleware/@v/v1.0.0.info:
dial tcp 172.217.20.113:443: connect: can't assign requested address
go: github.com/stretchr/testify@v1.2.2: Get
https://proxy.golang.org/github.com/stretchr/testify/@v/v1.2.2.info:
dial tcp 172.217.20.113:443: connect: can't assign requested address
go: finding google.golang.org/grpc v1.16.0
go: github.com/libgit2/git2go@v0.0.0-20190104134018-ecaeb7a21d47: Get
https://proxy.golang.org/github.com/libgit2/git2go/@v/v0.0.0-20190104134018-ecaeb7a21d47.info:
dial tcp 172.217.20.113:443: connect: can't assign requested address
go: finding github.com/sirupsen/logrus v1.2.0
go: finding github.com/golang/protobuf v1.3.1
go: finding golang.org/x/sync v0.0.0-20181221193216-37e7f081c4d4
go: finding github.com/grpc-ecosystem/go-grpc-prometheus v1.2.0
go: finding github.com/kelseyhightower/envconfig v1.3.0
go: golang.org/x/sys@v0.0.0-20190215142949-d0b11bdaac8a: Get
https://proxy.golang.org/golang.org/x/sys/@v/v0.0.0-20190215142949-d0b11bdaac8a.info:
dial tcp 172.217.20.113:443: connect: can't assign requested address
go: github.com/golang/protobuf@v1.3.1: Get
https://proxy.golang.org/github.com/golang/protobuf/@v/v1.3.1.info: dial
tcp 172.217.20.113:443: connect: can't assign requested address
go: google.golang.org/grpc@v1.16.0: Get
https://proxy.golang.org/google.golang.org/grpc/@v/v1.16.0.info: dial
tcp 172.217.20.113:443: connect: can't assign requested address
go: golang.org/x/sync@v0.0.0-20181221193216-37e7f081c4d4: Get
https://proxy.golang.org/golang.org/x/sync/@v/v0.0.0-20181221193216-37e7f081c4d4.info:
dial tcp 172.217.20.113:443: connect: can't assign requested address
go: github.com/tinylib/msgp@v1.1.0: Get
https://proxy.golang.org/github.com/tinylib/msgp/@v/v1.1.0.info: dial
tcp 172.217.20.113:443: connect: can't assign requested address
go: github.com/sirupsen/logrus@v1.2.0: Get
https://proxy.golang.org/github.com/sirupsen/logrus/@v/v1.2.0.info: dial
tcp 172.217.20.113:443: connect: can't assign requested address
go: gopkg.in/yaml.v2@v2.2.2: Get
https://proxy.golang.org/gopkg.in/yaml.v2/@v/v2.2.2.info: dial tcp
172.217.20.113:443: connect: can't assign requested address
go: github.com/getsentry/raven-go@v0.1.2: Get

Re: How to handle go dependencies

[Matthias Fechner]

Dear Dmitri,

at first thanks a lot for your suggestions.
The current version of the Makefile is always here:
https://gitlab.fechner.net/mfechner/Gitlab/blob/12.0/devel/gitaly/Makefile

Other answer under your suggestions.

Am 23.06.2019 um 23:40 schrieb Dmitri Goutnik via freebsd-ports:
> +USES= gmake 

I used now USES= gmake |go:no_targets|

|This pulls in go as dependency. Without go:no_targets I got an error
message that go was not found.
|

|
|

> "gitaly-proto" is not a valid group name (contains "-"); can be fixed by 
> changing the group name to e.g. "gitaly_proto"

thanks, now I was able to generate the distinfo file.

>  post-patch:
>   ${REINPLACE_CMD} -e "s|%%PREFIX%%|${PREFIX}|" 
> ${WRKSRC}/config.toml.example
>   ${MV} ${WRKSRC}/config.toml.example ${WRKSRC}/config.toml.sample
> - ${RM} ${WRKSRC}/go.mod

removed.

But now I have the problem that go does not find the libs.
I get now the error messages like:
# go install
go: finding github.com/getsentry/raven-go v0.1.2
go: finding golang.org/x/sync v0.0.0-20181221193216-37e7f081c4d4
go: finding github.com/golang/protobuf v1.3.1
go: finding gitlab.com/gitlab-org/gitaly-proto v1.32.0
go: finding github.com/stretchr/testify v1.2.2
go: finding github.com/cloudflare/tableflip
v0.0.0-20190329062924-8392f1641731
go: finding github.com/tinylib/msgp v1.1.0
go: finding github.com/sirupsen/logrus v1.2.0
go: finding github.com/libgit2/git2go v0.0.0-20190104134018-ecaeb7a21d47
go: finding github.com/BurntSushi/toml v0.3.1
go: github.com/BurntSushi/toml@v0.3.1: Get
https://proxy.golang.org/github.com/%21burnt%21sushi/toml/@v/v0.3.1.info:
dial tcp 172.217.19.209:443: connect: can't assign requested address
go: github.com/getsentry/raven-go@v0.1.2: Get
https://proxy.golang.org/github.com/getsentry/raven-go/@v/v0.1.2.info:
dial tcp 172.217.19.209:443: connect: can't assign requested address
go: github.com/cloudflare/tableflip@v0.0.0-20190329062924-8392f1641731:
Get
https://proxy.golang.org/github.com/cloudflare/tableflip/@v/v0.0.0-20190329062924-8392f1641731.info:
dial tcp 172.217.19.209:443: connect: can't assign requested address
go: github.com/sirupsen/logrus@v1.2.0: Get
https://proxy.golang.org/github.com/sirupsen/logrus/@v/v1.2.0.info: dial
tcp 172.217.19.209:443: connect: can't assign requested address
go: finding google.golang.org/grpc v1.16.0
go: finding google.golang.org/genproto v0.0.0-20181202183823-bd91e49a0898
go: github.com/libgit2/git2go@v0.0.0-20190104134018-ecaeb7a21d47: Get
https://proxy.golang.org/github.com/libgit2/git2go/@v/v0.0.0-20190104134018-ecaeb7a21d47.info:
dial tcp 172.217.19.209:443: connect: can't assign requested address
go: finding github.com/grpc-ecosystem/go-grpc-prometheus v1.2.0
go: github.com/stretchr/testify@v1.2.2: Get
https://proxy.golang.org/github.com/stretchr/testify/@v/v1.2.2.info:
dial tcp 172.217.19.209:443: connect: can't assign requested address
go: finding gopkg.in/yaml.v2 v2.2.2
go: golang.org/x/sync@v0.0.0-20181221193216-37e7f081c4d4: Get
https://proxy.golang.org/golang.org/x/sync/@v/v0.0.0-20181221193216-37e7f081c4d4.info:
dial tcp 172.217.19.209:443: connect: can't assign requested address
go: finding gitlab.com/gitlab-org/labkit v0.0.0-20190221122536-0c3fc7cdd57c
go: finding github.com/prometheus/client_golang v0.9.3
go: github.com/tinylib/msgp@v1.1.0: Get
https://proxy.golang.org/github.com/tinylib/msgp/@v/v1.1.0.info: dial
tcp 172.217.19.209:443: connect: can't assign requested address
go: github.com/golang/protobuf@v1.3.1: Get
https://proxy.golang.org/github.com/golang/protobuf/@v/v1.3.1.info: dial
tcp 172.217.19.209:443: connect: can't assign requested address
go: gitlab.com/gitlab-org/gitaly-proto@v1.32.0: Get
https://proxy.golang.org/gitlab.com/gitlab-org/gitaly-proto/@v/v1.32.0.info:
dial tcp 172.217.19.209:443: connect: can't assign requested address
go: finding github.com/kelseyhightower/envconfig v1.3.0
go: finding golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a
go: finding golang.org/x/net v0.0.0-20190311183353-d8887717615a
go: finding github.com/grpc-ecosystem/go-grpc-middleware v1.0.0
go: gitlab.com/gitlab-org/labkit@v0.0.0-20190221122536-0c3fc7cdd57c: Get
https://proxy.golang.org/gitlab.com/gitlab-org/labkit/@v/v0.0.0-20190221122536-0c3fc7cdd57c.info:
dial tcp 172.217.19.209:443: connect: can't assign requested address
go: github.com/grpc-ecosystem/go-grpc-middleware@v1.0.0: Get
https://proxy.golang.org/github.com/grpc-ecosystem/go-grpc-middleware/@v/v1.0.0.info:
dial tcp 172.217.19.209:443: connect: can't assign requested address
go: golang.org/x/net@v0.0.0-20190311183353-d8887717615a: Get
https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20190311183353-d8887717615a.info:
dial tcp 172.217.19.209:443: connect: can't assign requested address
go: github.com/grpc-ecosystem/go-grpc-prometheus@v1.2.0: Get
https://proxy.golang.org/github.com/grpc-ecosystem/go-grpc-prometheus/@v/v1.2.0.info:
dial tcp 172.217.19.209:443: connect: can't assign requested address
go: 

Re: PR236858 – [NEW PORT] www/grafana6: Dashboard and graph editor for multiple data stores

[Matthias Fechner]

Am 28.06.2019 um 15:49 schrieb David W:
> HiAny commiter care to look 
> athttps://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236858 ?Seems to be 
> tested and working.

testbuild is fine, I will commit it the next minutes.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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 to handle go dependencies

[Matthias Fechner]

Am 23.06.2019 um 11:57 schrieb Tobias Kortkamp:
> Please do not use it.  It is broken in many ways.  Use Dimtri's
> devel/modules2tuple instead.  Change to WRKSRC of your port and run
> `go mod vendor` then `modules2tuple vendor/modules.txt` and it will
> spit out an appropriate GH_TUPLE etc.

thanks that looks fine now. I added also a target `gomod-deps` to get
that more easily generated.
It currently seems to only support GH and not GL, this could maybe
improved later.

> Probably you need
> USE_GITHUB=   nodefault
>
> and it should work.

seems ok, I have now the following:
https://gitlab.fechner.net/mfechner/Gitlab/commit/e83876fb9de9c79c39ba85801ebb242a08f5412c

But now I get the error message:
===
The
https://gitlab.com/gitlab-org/gitaly-proto/repository/f4db5d05d437abe1154d7308ca044d3577b5ccba/archive.tar.gz?dummy=/:gitaly-proto
MASTER_SITES line has
a group with invalid characters, only use [a-zA-Z0-9_]
*** Error code 1

This seems to be a bug in the ports?
Why is a `-` an invalid character, it exists in:
https://gitlab.com/gitlab-org/gitaly/

Is there a way out?

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook




signature.asc
Description: OpenPGP digital signature

Re: How to handle go dependencies

[Matthias Fechner]

Am 22.06.2019 um 22:52 schrieb Dmitri Goutnik:
> Can be further simplified by using USES=go:modules. This will remove the need 
> to modify MAKE_ENV as go.mk will then add -mod=vendor flag automagically.

very interesting.

I also found a nice mechanism in devel/bingo.
It has a very nice awk script to generate the GH_TUPLE line
automatically (see Makefile target gomod-deps).

But I have now the problem that my source is hosted on gitlab, so I use
`USE_GITLAB`.
It seems to make problem if I try to also use `USE_GITHUB`.

I see now the following problem:
make: "/usr/ports/Mk/bsd.sites.mk" line 602: warning: duplicate script
for target "git-clone-DEFAULT" ignored
make: "/usr/ports/Mk/bsd.sites.mk" line 466: warning: using previous
script for "git-clone-DEFAULT" defined here
make: "/usr/ports/Mk/bsd.sites.mk" line 603: warning: duplicate script
for target "git-clone-DEFAULT" ignored
make: "/usr/ports/Mk/bsd.sites.mk" line 466: warning: using previous
script for "git-clone-DEFAULT" defined here
pkg-static: /tmp/pkgs/gitaly-1.47.0.txz: No such file or directory
pkg-static: Was 'pkg install /tmp/pkgs/gitaly-1.47.0.txz' meant?

Can I use GITLAB too fetch the main archive and use GITHUB to fetch the
go packages I need?

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook


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

How to handle go dependencies

[Matthias Fechner]

Dear all,

I just prepare the gitlab-ce upgrade to version 12.0.0.
But I have some problem with a package that uses go to compile.

The new version of devel/gitaly has changed the way the package is defined.
They removed now all files from the vendor/ folder and add dependencies
in a `go.mod` file.

If I now build the port it tries to fetch the files while no network
access is allowed.

What is the correct way to getting these dependencies fetched and
correctly included into the work-source in the fetch step using go?

Thanks a lot!

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook




signature.asc
Description: OpenPGP digital signature

Re: Request to change ruby default version to 2.5

[Matthias Fechner]

Am 20.04.2019 um 13:56 schrieb Hajimu UMEMOTO:
> w.schwarzenfeld> ===>>> Port directory: /usr/ports/databases/ruby-bdb
>
> w.schwarzenfeld>     ===>>> This port is marked BROKEN
> w.schwarzenfeld>     ===>>> does not build with Ruby 2.5
>
> How about this patch?

thanks for the patch!
Tested it and builds fine here, just commited it with r499463.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Request to change ruby default version to 2.5

[Matthias Fechner]

Am 20.04.2019 um 06:59 schrieb Walter Schwarzenfeld:
> After this change:
>
> |portmaster -R -r ruby-2.5|
>
> |
> ===>>> Port directory: /usr/ports/databases/ruby-bdb
>
>     ===>>> This port is marked BROKEN
>     ===>>> does not build with Ruby 2.5
>
>
>     ===>>> If you are sure you can build it, remove the
>        BROKEN line in the Makefile and try again. 

you have here several possibilities:

- keep on ruby 2.4 till portmaster is fixed, see UPDATING
- write a bug report upstream for ruby-bdb to get it fixed for ruby 2.5
- fix portmaster by yourself
- use a more recent package builder like poudriere

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Request to change ruby default version to 2.5

[Matthias Fechner]

Am 19.04.2019 um 17:43 schrieb Steve Wills:
> Yeah, it's fine, do it, just be sure to add an UPDATING entry similar
> to previous entries for changing ruby default version. 

thanks, committed with 499391.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Request to change ruby default version to 2.5

[Matthias Fechner]

Hi Steve,

Am 19.04.2019 um 15:06 schrieb Steve Wills:
> Yeah, there was an exp-run for it:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233901
>
> There are only 2 things to fix now and you can mark those broken with
> 2.5 if they are not already and do it. I should have done it in
> January, but was waiting for other things such as GitLab to catch
> up/officially support it. 

I marked them broken with 2.5 and referred to this PR.
So we should be save to switch ruby default version to 2.5?

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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 to use @preexec to test for installed packages

[Matthias Fechner]

Am 06.04.2019 um 20:59 schrieb Adam Weinberger:
> Especially since www/gitea does the same thing (and probably a number
> of others as well).

I did now a lot of tests and came to the conclusion that I will add
these checks into the startup script of gitlab-ce.

Maybe this problem will be fixed in a future version of pkg to be able
to use the CONFLICTS_ definition from the Makefile.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Request to change ruby default version to 2.5

[Matthias Fechner]

Dear all,

regarding this PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237222

and confirmation from gitlab developers here:
https://gitlab.com/gitlab-org/gitlab-ce/issues/60704

www/gitlab-ce requires at least ruby 2.5.x.

Is there a possibility to change the default version for ruby in the
ports from 2.4 to 2.5?
And if yes, how should this be done?

Thanks a lot.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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 to use @preexec to test for installed packages

[Matthias Fechner]

Am 06.04.2019 um 18:01 schrieb Adam Weinberger:
> What you're describing is
> Makefile:
>   CONFLICTS_INSTALL= gogs

does not work, please see here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234807

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

How to use @preexec to test for installed packages

[Matthias Fechner]

Dear all,

as pkg cannot handle CONFLICTS_INSTALL I tried now to implement this as
a preinstall command using @preexec in pkg-plist.

The command should check if a package is installed and stop the
installation or continue if the package is not installed.

I tried it with the following command:
@preexec `/usr/sbin/pkg -N info -e gogs`; if [ $? -eq 0 ]; then echo
"Gitlab cannot be installed together with gogs as both of them modify
.ssh/authorized_keys" && exit 1; else echo "Gogs not installed,
continue."; fi

But it does not work.
Now matter if gogs is installed or not.
If I execute the same line in a shell script, it works fine.

Anyone an idea?


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: databases/mongodb40 port proposal

[Matthias Fechner]

Am 02.03.2019 um 15:23 schrieb Kurt Jaeger:
> Sorry that I jumped the gun, I made those modifications, testbuilt and
> committed that port.
>
> I also shamelessly asked Andrew if he can provide a mongodb40-tools port 8-}

thanks Kurt.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: databases/mongodb40 port proposal

[Matthias Fechner]

Am 02.03.2019 um 03:30 schrieb Andrew Shevchuk:
> First of all, please make sure you have the latest patch file.
> You can apply this patch using one of the following examples:

I cannot apply your patch, but I use the repository now.

Could you please execute in the port the command `portlint -ACN` and fix
the warnings you get there?

WARN: Makefile: [18]: the arguments to ONLY_FOR_ARCHS are not sorted. 
Please consider sorting them.
WARN: Makefile: possible use of absolute pathname "/usr/local/bin/ar:de...".
WARN: Makefile: possible direct use of "BUILD_DEPENDS= 
${PYTHON_PKGNAMEPREFIX}cheetah>=2.4.4:devel/py-cheetah@${PY_FLAVOR} 
${PYTHON_PKGNAMEPREFIX}typing>=3.6.2:devel/py-typing@${PY_FLAVOR} 
${PYTHON_PKGNAMEPREFIX}yaml>=3.11:devel/py-yaml@${PY_FLAVOR} 
/usr/local" found. if so, use ${PREFIX} or ${LOCALBASE}, as appropriate.
WARN: Makefile: for new port, make $FreeBSD$ tag in comment section
empty, to make SVN happy.
WARN: Makefile: "USES" has to appear earlier.
0 fatal errors and 5 warnings found.

Please also update the MAINTAINER line to match you.

I currently test build the port, but this maybe takes some time.
You can find the current status here:
https://pkg.fechner.net/build.html?mastername=120amd64-default=2019-03-02_08h53m28s

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook


___
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: databases/mongodb40 port proposal

[Matthias Fechner]

Dear Kevin,

Am 01.03.2019 um 05:50 schrieb Kevin Oberman:
> Most patches against ports, including this one, assume that the current
> directory is /usr/ports or whatever directory is your ports tree base
> directory. Alternatively, you can use '-s N' to ignore the first N
> directories in the path specified in the patch.

thanks for your answer.
-s is the silent option, I think you wanted to write -spN where with N
you can define a number of directories to strip, like it is explained in
the man page:

 -p strip-count, --strip strip-count
 Sets the pathname strip count, which controls how pathnames
found
 in the patch file are treated, in case you keep your files in a
 different directory than the person who sent out the
patch.  The
 strip count specifies how many slashes are to be stripped from
...

But this is not the reason, it seems that the patch has a format that
patch cannot handle or you must define some parameters I do not know.

I tried to apply the patch on the source dir of the ports directory.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: databases/mongodb40 port proposal

[Matthias Fechner]

Dear Andrew,

Am 28.02.2019 15:48, schrieb Andrew Shevchuk:

Latest stable MongoDB (4.0.6) port proposal:
https://raw.githubusercontent.com/ashevchuk/mongodb40-freebsd-port/master/mongodb40.patch


thanks a lot for this patch!
I just tried to apply it so I can do some tests but I'm unable to apply 
your patch.

I tested it with:
patch -i mongodb40.patch

while beeing in the ports directory.
But it complains that it is not able to find the file to patch:

# patch -i mongodb40.patch
Hmm...  Looks like a normal diff to me...
The text leading up to this was:
--
|diff -rNd databases/Makefile.orig databases/Makefile
--
File to patch:


How to apply this patch?


--
Gruß
Matthias
___
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: Add conflicts to port

[Matthias Fechner]

Am 09.01.2019 um 13:27 schrieb Mathieu Arnold:
> CONFLICTS, CONFLICTS_BUILD and CONFLICTS_INSTALL exist to tell the user
> building the port that the port they are trying to install cannot be
> built-or-installed/build/installed while this other port is installed.

thanks for clarification, I created a PR for this:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234807

and added it as blocker for:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225309

To be consistent pkg should handle packages equal to ports.
Any difference here will only cause problems like this.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Add conflicts to port

[Matthias Fechner]

Hi Franco,

Am 08.01.2019 um 15:58 schrieb Franco Fichtner:
> Explicit CONFLICTS only exist within the ports tree
> during builds.
>
> pkg detects conflicts simply when files are attempted
> to be installed in the same place -- i.e. a file already
> belongs to another installed package.

hm, this will not help, as the conflicting file is created at runtime
and not by the installation of the package and can therefor not be
detected by pkg.

I do not understand why the CONFLICTS_INSTALL does exist:
http://www.si.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/conflicts.html

if it does not work.
Maybe a bug or has the documentation to be updated?

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Add conflicts to port

[Matthias Fechner]

Dear all,

I just implement some changes in the gitlab-ce port which requires some
conflicts.
I tried to add:

CONFLICTS_INSTALL=  gitolite-* \
    gitolite2-* \
    gogs-* \
    ${PYTHON_PKGNAMEPREFIX}-gitosis-*

My test machine has gitolite and gitlab-ce installed.

If I know execute pkg upgrade it does not trigger the conflict.
I had expected that pkg forces now a deinstallation of gitolite before
it continues with upgrading gitlab-ce.
But it just installs gitlab-ce and ignores the conflict definition.

Is this a bug in pkg or is something with the definition of the conflict
not correct?

Thanks.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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/dovecot sodium not enabled

[Matthias Fechner]

Hi Larry,

Am 04.12.2018 um 12:35 schrieb Larry Rosenman:
> I inherited that port, and I just added a libsodium option in r486595.

wow, this was amazingly fast.
Thanks a lot!

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook




signature.asc
Description: OpenPGP digital signature

mail/dovecot sodium not enabled

[Matthias Fechner]

Hi,

I just saw that sodium is explicitely disabled:
CONFIGURE_ARGS= --localstatedir=/var \
--with-statedir=/var/db/dovecot \
--without-shadow \
--without-sodium \

by disabling it, dovecot cannot use argon2 as hash for passwords which 
is recommended for new deployments and developments.


Is there a special reason why this was disabled?

Thanks a lot.

--
Gruß
Matthias
___
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: Poudriere building far more ports than it should

[Matthias Fechner]

Am 14.11.2018 um 19:57 schrieb Reko Turja via freebsd-ports:
> I guess one option would be blacklisting in poudriere those unneeded
> dependencies which shouldn't be linked with my packages, if my options
> are honoured by poudriere. 

have you made your options (maybe they are located on /var/db/ports)
available to poudriere?
(normally poudriere searches them in /usr/local/etc/poudriere.d/options)

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: BIND update gone bad

[Matthias Fechner]

Am 14.11.18 um 03:15 schrieb Kevin P. Neal:
> 13-Nov-2018 21:00:30.959 ENGINE_by_id failed (crypto failure)
> 13-Nov-2018 21:00:30.959 error:25066067:DSO support routines:DLFCN_LOAD:could 
> not load the shared 
> library:/usr/src/crypto/openssl/crypto/dso/dso_dlfcn.c:187:filename(/usr/lib/engines/libgost.so):
>  Cannot open "/usr/lib/engines/libgost.so"
> 13-Nov-2018 21:00:30.959 error:25070067:DSO support routines:DSO_load:could 
> not load the shared library:/usr/src/crypto/openssl/crypto/dso/dso_lib.c:233:
> 13-Nov-2018 21:00:30.959 error:260B6084:engine routines:DYNAMIC_LOAD:dso not 
> found:/usr/src/crypto/openssl/crypto/engine/eng_dyn.c:467:
> 13-Nov-2018 21:00:30.959 error:2606A074:engine routines:ENGINE_by_id:no such 
> engine:/usr/src/crypto/openssl/crypto/engine/eng_list.c:390:id=gost
> 13-Nov-2018 21:00:30.959 initializing DST: crypto failure
> 13-Nov-2018 21:00:30.959 exiting (due to fatal error)
> [root@gunsight1 ~]#

maybe an OPTION problem.
Make sure you disable the GOST option (in bind and openssl), I faced a
similar problem, but I thing this option was removed, but I think it is
a try worth.


Gruß,
Matthias

-- 
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook
___
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: Cleanup poudriere old data

[Matthias Fechner]

Am 26.10.2018 um 18:45 schrieb Renato Botelho:
> Try poudriere logclean

thanks, that did it.


Gruß
Matthias

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

Cleanup poudriere old data

[Matthias Fechner]

Dear all,

normally if I switch to a new release a remove the old jail by using:

poudriere jails -d -j 111amd64

But it seems that it does not remove everything, all the logs are not
deleted:
http://pkg.fechner.net/index.html

I created again the jail with:
poudriere jail -c -v 11.1-RELEASE -a amd64 -j 111amd64

I removed it again with:
poudriere jails -d -C all -j 111amd64

But it does not remove the entries from the website, the locale file system:
/usr/local/poudriere/data/logs/bulk/111amd64-default
/usr/local/poudriere/data/logs/bulk/111amd64-gitlab
/usr/local/poudriere/data/logs/bulk/111amd64-2018Q2
/usr/local/poudriere/data/logs/bulk/111amd64-2018Q3
...
/usr/local/poudriere/data/packages/amd64-default
...

Is this a bug or did I understand the man-page not correctly?
How can I get rid of all this old stuff (logs, cache, packages)?

Thanks.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook


___
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: RUN_DEPENDS and portmaster

[Matthias Fechner]

Dear Stefan,

Am 17.09.2018 um 14:31 schrieb Stefan Esser:
> But the behavior of portmaster will not be changed.
> RUN_DEPENDS are dependencies required to run a port, not dependencies
> required to install a port.
>
>
> And I do not care whether bsd.port.mk treats RUN_DEPENDS as if they
> were INSTALL_DEPENDS (which do not exist). The fact that bsd.port.mk
> works in that way is due to the fact, that it generally executes sub
> processes in a depth first manner. Portmaster distinguishes build and
> run dependencies and makes sure, that build dependencies not only exist,
> but are updated before the ports they depend on, while bsd.port.mk will
> use any build dependency that satisfies the range requirements (if any)
> and does not upgrade existing but outdated (in the sense that an upgrade
> is available) dependencies. Portmaster will then upgrade any out-dated
> run dependencies (again if an upgrade is available, not only if it is
> strictly required). Thus portmaster guarantees, that a port is built
> with the latest available build tools, and that run dependency upgrades
> see the upgraded port that requires them, in case they depend on it.

I fully understand you.

Maybe it will be a good idea to phase portmaster out as it seems to be a
unmaintable beast?

Maybe synth can replace it for users that are not used to poudriere?


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: RUN_DEPENDS and portmaster

[Matthias Fechner]

Am 10.09.18 um 12:16 schrieb Mathieu Arnold:
> Reading Mk/bsd.port.mk at line 5274, run-depends are installed before
> do-install runs.

thanks, I see it the same way and created a PR for it, to get this fixed
in portmaster.


Gruß,
Matthias

-- 
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook



signature.asc
Description: OpenPGP digital signature

Re: RUN_DEPENDS and portmaster

[Matthias Fechner]

Dear Stefan, Dear Mathieu,

Am 10.09.18 um 14:10 schrieb Stefan Esser:
> This is a design decision in portmaster that has existed for at least
> a decade.
> 
> Use INSTALL_DEPENDS if you depend on a port being available and upgraded
> before your port's do-install is invoked.
> 
> Changing the current portmaster version in ports is no option, since it
> does not offer to recursively upgrade or install any other port while
> working on some port and it cannot easily be made to support such a
> sequence of actions.

thanks a lot for your explanation, so it seems to be a problem with
portmaster.
But as I do not want to block all users from using gitlab-ce that are
using portmaster I think it is ok to define all RUN_DEPENDS also as
BUILD_DEPENDS?

I think this approach is already used by many ports...


Gruß,
Matthias

-- 
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook
___
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"

RUN_DEPENDS and portmaster

[Matthias Fechner]

Dear all,

I have a questions reagarding the RUN_DEPENDS and at which step
dependencies should be installed.
I'm the maintainer of gitlab-ce port and I added a feature that checks
in the install target:
do-install:
(cd ${WRKSRC} && ${RM} Gemfile.lock && bundle install --local)
${FIND} ${WRKSRC} -name '*.orig' -delete
...

that all gems available in the system do match the version required by
the Gemfile.
Poudriere works fine with this, but portmaster fails.
Regarding the documentation RUN_DEPENDS packages should be installed
before the install is happening.
Is this install related to the do-install target or the installation of
the package itself?

Is this maybe a problem with portmaster as poudiere handles this correctly?

Thanks.

Gruß,
Matthias

-- 
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook
___
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: Help building net/rubygem-grpc

[Matthias Fechner]

Dear Andrea,

Am 05.08.2018 um 12:09 schrieb Andrea Venturoli:
> Since a couple of days this port does not build anymore on my
> 11.2/amd64 box.
> I get the same error building directly from ports or with Poudriere.
> I'm attaching the Poudriere build log.
>
> Any help in solving this? 

this problem is related to an upgrade to devel/grpc.
Downgrade grpc to version 1.13.1 fixes it.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Delete a port

[Matthias Fechner]

Am 04.08.2018 um 17:06 schrieb René Ladan:
> How about the attached patch?

LGTM.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook




signature.asc
Description: OpenPGP digital signature

Re: Delete a port

[Matthias Fechner]

Thanks Eugene,

Am 04.08.2018 um 16:15 schrieb Eugene Grosbein:
> It seems, rmport script needs a patch:
>
> Index: Tools/scripts/rmport
> ===
> --- Tools/scripts/rmport(revision 476322)
> +++ Tools/scripts/rmport(working copy)
> @@ -39,6 +39,7 @@
>  # MAINTAINER=  cr...@freebsd.org
>  #
>
> +EDITOR=${EDITOR:-vi}
>  PORTSDIR=${PORTSDIR:-/usr/ports}
>  INDEX=${PORTSDIR}/`make -C ${PORTSDIR} -V INDEXFILE`

that fixes it for me.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook



signature.asc
Description: OpenPGP digital signature

Delete a port

[Matthias Fechner]

Dear all,

I just try to delete my first port, but I have some problems.
I tried it with the script Tools/scripts/rmport 
security/rubygem-omniauth-shibboleth12

But it fails with:

==> creating temporary directory
==> created /tmp/rmport.QRBlqG8d
==> getting ports/MOVED and ports/LEGAL from repository
 U   ports
Checked out revision 476345.
Updating 'ports/MOVED':
A    ports/MOVED
Updated to revision 476345.
Updating 'ports/LEGAL':
A    ports/LEGAL
Updated to revision 476345.
Summary of updates:
  Updated 'ports/MOVED' to r476345.
  Updated 'ports/LEGAL' to r476345.
==> security/rubygem-omniauth-shibboleth12: checking dependencies
==> security/rubygem-omniauth-shibboleth12: getting PRs having
rubygem-omniauth-shibboleth12 in the synopsis
==> security/rubygem-omniauth-shibboleth12: getting security/Makefile
and port's files from repository
Updating 'ports/security':
A    ports/security
Updated to revision 476346.
Updating 'ports/security/Makefile':
A    ports/security/Makefile
Updated to revision 476346.
Summary of updates:
  Updated 'ports/security' to r476346.
  Updated 'ports/security/Makefile' to r476346.
Updating 'ports/security/rubygem-omniauth-shibboleth12':
A    ports/security/rubygem-omniauth-shibboleth12
A    ports/security/rubygem-omniauth-shibboleth12/Makefile
A    ports/security/rubygem-omniauth-shibboleth12/distinfo
A    ports/security/rubygem-omniauth-shibboleth12/pkg-descr
Updated to revision 476346.
==> security/rubygem-omniauth-shibboleth12: checking if
rubygem-omniauth-shibboleth12-1.2.1 is in ports/LEGAL
==> security/rubygem-omniauth-shibboleth12: checking if
security/rubygem-omniauth-shibboleth12 is in ports/LEGAL
==> security/rubygem-omniauth-shibboleth12: adding entry to ports/MOVED
==> security/rubygem-omniauth-shibboleth12: removing from security/Makefile
==> security/rubygem-omniauth-shibboleth12: removing port's files
D ports/security/rubygem-omniauth-shibboleth12
D ports/security/rubygem-omniauth-shibboleth12/Makefile
D ports/security/rubygem-omniauth-shibboleth12/distinfo
D ports/security/rubygem-omniauth-shibboleth12/pkg-descr
==> security/rubygem-omniauth-shibboleth12: adding entry to commit
message template
==> creating diff
hit  to view svn diff output

you can now edit files under /tmp/rmport.QRBlqG8d/ by hand
do you want to recreate the diff? [yn] n
==> running svn update
./rmport: svnlog: not found


Anyone an idea what is wrong?


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Could someone else please review and approve these revision so I can commit them

[Matthias Fechner]

Am 02.05.2018 um 16:12 schrieb Mark Felder:
> MFH approved
>
I just saw while doing the MFH that we have an older version in Q2.
I try to prepare a list of commits we would need to merge and will send
an additional approval request for it.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Could someone else please review and approve these revision so I can commit them

[Matthias Fechner]

Am 02.05.2018 11:10, schrieb Eugene Grosbein:
as Torsten (tz) and Steve (swills) seems to be not available and I'm 
not allowed to commit before the reviews were approved could please 
someone else have a look to (they have security problems):

https://reviews.freebsd.org/D15248
https://reviews.freebsd.org/D15249

I would like to commit them ASAP to fix some critical security holes 
with gitlab.


Done.


thanks a lot, I committed them.
I will roll now all my production servers to the new version and will 
tomorrow MFH it.


@ports-secteam
could you please approve the MFH of r468821.

Thank you all!

--
Gruß
Matthias
___
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"

Could someone else please review and approve these revision so I can commit them

[Matthias Fechner]

Dear all,

as Torsten (tz) and Steve (swills) seems to be not available and I'm not 
allowed to commit before the reviews were approved could please someone 
else have a look to (they have security problems):

https://reviews.freebsd.org/D15248
https://reviews.freebsd.org/D15249

I would like to commit them ASAP to fix some critical security holes 
with gitlab.


Thanks a lot.

--
Gruß
Matthias
___
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"

Fetch deps for ports build with go

[Matthias Fechner]

Dear all,

I'm just in the process to upgrade gitlab to 10.7 but I have some
problems with the port www/gitlab-pages.

It is compiled using go.
It seems that the new version is pulling in data via:
all: gitlab-pages

setup: clean .GOPATH/.ok
    go get -u github.com/FiloSottile/gvt
    - ./bin/gvt fetch golang.org/x/tools/cmd/goimports
    - ./bin/gvt fetch github.com/wadey/gocovmerge
    - ./bin/gvt fetch github.com/golang/lint/golint
    - ./bin/gvt fetch github.com/fzipp/gocyclo

What is here the way to go to get these deps fetch in the fetch phase?


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Upgrade devel/libgit2-glib new version 0.27.0 not existing upstream

[Matthias Fechner]

Am 23.04.2018 um 09:25 schrieb Romain Tartière:
> Hi
>
> On Mon, Apr 23, 2018 at 09:18:47AM +0200, Matthias Fechner wrote:
>> I just prepare the upgrade for gitlab to version 10.7.0 which required
>> libgit2 version 0.27.0.
>> I already upgrade devel/libgit2 including py-pygit2 to version 0.27.0
>> but for an unknown reason version 0.27.0 of libgit2-glib is not existing
>> upstream.
> No real info, but supposition:
>   - You are looking for *rugged* 0.27.0, which was recently released and
> is ruby bindings for libgit2:
> https://rubygems.org/gems/rugged
>   - The dependency exist on some feature not yet released in libgit2
> upstream, so they used the version number of the future version of
> libgit2 which would make this feature available.  In this case, you
> may want to test with libgit's master branch…
sry, maybe I was not clear enough.
I upgraded libgit2 to 0.27.0 and py-pygit2 to 0.27.0 but I cannot
upgrade libgit2-glib to version 0.27.0 because it does not exist upstream.

I learned from the past that the following ports must be upgrade all at
once:
- devel/rubygem-rugged (done)
- devel/libgit2 (done)
- devel/libgit2-glib (missing upstream)
- devel/py-pygit2 (done)

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Upgrade devel/libgit2-glib new version 0.27.0 not existing upstream

[Matthias Fechner]

Dear all,

I just prepare the upgrade for gitlab to version 10.7.0 which required
libgit2 version 0.27.0.
I already upgrade devel/libgit2 including py-pygit2 to version 0.27.0
but for an unknown reason version 0.27.0 of libgit2-glib is not existing
upstream.

Does anyone know here more?

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Changing PHP default version from 5.6 to 7.2 timeframe?

[Matthias Fechner]

Am 19.04.2018 um 16:48 schrieb Kurt Jaeger:
> I'm not involved in the decision, but I've heard from problems
> with typo3 and php7.2.

I saw similar problems with other products.
For me I will stick to php7.1 for at least one year, this version seems
to be quiet stable to use.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Update devel/rubygem-default_value_for update to 3.0.5 which fixes a breaking change causing gitlab to fail

[Matthias Fechner]

Dear all,

could a committer please look into this:

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

It is fixing an upstream bug, that was introduced with version 3.0.4
which causes e.g. www/gitlab to stop working.

Thanks a lot!

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Upgrade rubygem port with strange version string

[Matthias Fechner]

Hi Jochen,

Am 11.02.2018 um 11:35 schrieb Jochen Neumeister:
> where is the new Version 5.1.0 from unicorn? On Github and the webpage
> i found only Version 1.0.1


look here:

https://rubygems.org/gems/unicorn/versions/5.1.0.4.gd5fbb

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Upgrade rubygem port with strange version string

[Matthias Fechner]

Dear all,

I need to update a rubygem port to version 5.1.0.4.gd5fbb
PORTNAME=   unicorn
PORTVERSION=    5.1.0
CATEGORIES= www rubygems

I tested it with:

PORTNAME=   unicorn
PORTVERSION=   5.1.0.4
DISTNAME=  ${PORTNAME}-${PORTVERSION}.gd5fbb
CATEGORIES= www rubygems

which fetches the correct version.
But it installs the version into port:

/usr/local/lib/ruby/gems/2.4/gems/unicorn-5.1.0.4.gd5fbb

which causes problems.

What is here the best way to make sure it will be installed into:
/usr/local/lib/ruby/gems/2.4/gems/unicorn-5.1.0.4

Thanks a lot!

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook


___
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 interactive ports with poudriere

[Matthias Fechner]

Am 30.01.2018 um 19:32 schrieb Yasuhiro KIMURA:
> I would like to build security/bruteforceblocker with poudriere. This
> port have one options. But it has nothing to do with my question. The
> source of problem is license information. There is no license
> information about this software either in source archive or on web
> site. So LICENSE is set to "NONE" in Makefile. And when LICENSE is set
> to it LICENSE_PERMS doesn't include 'auto-accept'. So if you build it
> on real environment dialog for confirmation is popped up. But if you
> set 'BATCH=yes' then build fails as following.
>
> yasu@maybe[2366]% pwd
> /usr/ports/security/bruteforceblocker
> yasu@maybe[2367]% make BATCH=yes
> ===>  bruteforceblocker-1.2.4 License NONE needs confirmation, but BATCH is
> defined.
> *** Error code 1
have you tried: DISABLE_LICENSES=yes

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Creating patch files, skip post-patch

[Matthias Fechner]

Am 02.01.2018 um 10:19 schrieb Jan Beich:
> Try do-patch e.g.,
>
>   $ make clean extract do-patch makepatch EXTRA_PATCHES= BATCH=

thanks a lot Jan!


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Creating patch files, skip post-patch

[Matthias Fechner]

Dear all,

I have some ports I maintain and in some of them I have
post-patch-{{OPTION}}-on Makefile targets in that is patching files.
But to update the files I need a file where only the patches from
files/patch-* are applied.

Is there a possibility to skip the post-patch target from the Makefile
so I can do:

make patch (without post-patch from Makefile)
modify the files
make makepatch

Thanks a lot.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: py27-fail2ban-0.10.1

[Matthias Fechner]

Hi Alex,

Am 17.10.17 um 14:20 schrieb Alex V. Petrov:

Need a working sample for the new version of the port for pf.


I have it working now.
Put into your pf.conf where the rules from fail2ban be added the line:
# Anchor for fail2ban
anchor "f2b/*"

In your jail.local:
[DEFAULT]
banaction = pf[actiontype=]

The rest you can keep on standard. Just add and enable your jails into 
fail2ban that should run.
This configuration will block all connections from the IP. If you want 
to only specific on some ports you can use another actiontype, but there 
is another bug that will cause this not to work in 0.10.1.



Gruß,
Matthias

--
"Programming today is a race between software engineers striving to 
build bigger and better idiot-proof programs, and the universe trying to 
produce bigger and better idiots. So far, the universe is winning." -- 
Rich Cook

___
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 does not upgrade if more than one repository is defined

[Matthias Fechner]

Am 28.07.2017 um 13:13 schrieb Matt Smith:
>
> This might also be related to the CONSERVATIVE_UPGRADE setting of
> pkg.conf. According to the man page:
>
> CONSERVATIVE_UPGRADE: boolean
> Ensure in multi repository mode that the priority is
> given as much as possible to the repository where a
> package was first installed from.  Default: YES. 

thanks, this helped.

Second solution that was working for me to temporarily disable the
standard repository (poudriere) and do the upgrade, after this enable
the standard repo again.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Pkg does not upgrade if more than one repository is defined

[Matthias Fechner]

Dear all,

I have a problem with pkg and I'm not sure if it is a bug in pkg or a 
configuration issue.
I work on new version on ports which are in a separate poudriere 
repository (to be able to easily test it).


I have now two configuration files in /usr/local/etc/pkg/repos, 
poudriere.conf:

poudriere: {
url: "https://pkg.fechner.net/packages/110amd64-default;,
mirror_type: "pkg+http",
signature_type: "pubkey",
pubkey: "/usr/local/etc/ssl/certs/pkg.cert",
enabled: yes,
priority: 1
}

this is the standard repo which contains all stable packages.
Now I have a new version (in this case for gitlab) at gitlab.conf:
gitlab: {
url: "https://pkg.fechner.net/packages/110amd64-gitlab;,
mirror_type: "pkg+http",
signature_type: "pubkey",
pubkey: "/usr/local/etc/ssl/certs/pkg.cert",
enabled: yes,
priority: 10
}

The priority is higher and some package there have a higher version 
number.


But if I execute now 'pkg upgrade' pkg does not upgrade packages which 
have a higher version from the gitlab repository, but stick to the 
poudriere repository.


I also tried to do a 'pkg update -f; pkg upgrade' but it does not help.

Is there something wrong with my configuration or is this a bug in pkg?


--
Thanks
Matthias
___
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: Maintainer Update for www/drush need committer

[Matthias Fechner]

Am 08.07.2017 um 12:30 schrieb Kurt Jaeger:
>> could please someone look look at this PR:
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219869
>>
>> It was closed but never committed.
>> I already contacted Martin, but he is maybe on holiday.
> Done.
>

thanks Kurt!


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Maintainer Update for www/drush need committer

[Matthias Fechner]

Dear all,

could please someone look look at this PR:

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

It was closed but never committed.
I already contacted Martin, but he is maybe on holiday.

Thanks.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Best practice to tail a log and start it as service using rc.d scripts

[Matthias Fechner]

Am 03.07.2017 um 20:21 schrieb Eugene Grosbein:
> For logs written using standard syslog service, there is much
> effective way.
> 1. The syslogd daemon can run a subprocess and duplicate log stream to its
> standard input. For example, write to its config:
>
> mail.*"|exec nc localhost 5699 -"
>
> See man syslog.conf for details. You can even pipe not full log
> but some part of it, f.e. `mail.notice' instead of `mail.*'
> for important event only (no debug lines, no informational mesages).
thanks for this, I will test that more in detail.
I correctly have the problem if the mailtrain app is stopped, it closes
the network socket which causes nc to terminate.
This is not what I would like to have, but maybe syslog is restarting nc
in this case?

If not syslog is maybe not the right solution, but I will test this first.

> 2. And you need not modify system /etc/syslog.conf but create file
> named like /usr/local/etc/syslog.d/mailtrain.conf with that single line.
> Then use `service syslogd reload' to apply additional configuration
> and syslogd will run your "addon" when corresponding logs is updated.

are you sure about this?
I cannot find that described in any man page, /etc/defaults/rc.conf neither.
I tested it but it is not working.
Just added a file: /usr/local/etc/syslog.d/mailtrain.conf with content:
mail.*  /var/log/maillog.err

I touched the /var/log/maillog.err and reloaded syslogd.
But nothing appears in that file.


Thanks
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Best practice to tail a log and start it as service using rc.d scripts

[Matthias Fechner]

Dear all,

I just in the process to test mailtrain (https://mailtrain.org/) and if
it is working I would like to create a port for FreeBSD.

That mailtrain can handle bounce message with postfix together it is
necessary to tail the postfix log and pass it to mailtrain, using a
command like this:
tail -F -n +0 /var/log/maillog | nc localhost 5699 -

Is there a best practice approach on how to do this on FreeBSD?
I would require now a startup script in /usr/local/etc/rc.d to start
this kind of tail or is there a better mechanism in FreeBSD available?
If not, does anyone have some kind of template/example on how to start a
program like tail as daemon so FreeBSD can stop/restart it with the
service command?

Thanks
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook


___
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: Should a package restart on upgrade itself

[Matthias Fechner]

Am 27.06.2017 um 18:50 schrieb Vlad K.:
> Will this cover libraries as well? Eg. Libre/Open SSL upgrades,
> restart all services that depend on it?
>
> Meanwhile, there's "lsop": 

thanks for this tool, that is indeed very helpful.

Maybe it is a good idea if pkg collects the information from each
package what should be restarted if:

HANDLE_RC_SCRIPTS = true;

is set.
In this case it is the responsibility of the package maintainer to mark which 
service should be started if it was upgraded.
And then do a single bulk restart operation at the end of the complete upgrade.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Should a package restart on upgrade itself

[Matthias Fechner]

Dear all,

it is always a pain if pkg upgrade a lot of packages to restart all
services to make sure update/security fixes are applied to all running
services.

Is there an option in pkg that it restart services automatically or is
it OK if I would add a post-install script to the packages (I maintain)
that will include a "service foo restart"?

What is best practice here?


Thanks
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Which license should be used for as-id

[Matthias Fechner]

Dear all,

which LICENSE tag in ports should be used if the package as the license
"AS IS"?


Thanks
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Maintainer Update apache-solr

[Matthias Fechner]

Dear all,


I search for a committer for this two reports:

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

Thanks!


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Update of devel/rubygem-google-api-client broke www/rubygem-rest-client (blocks security related update)

[Matthias Fechner]

Hi Kurt,

Am 11.04.2017 um 07:27 schrieb Kurt Jaeger:
> Which security bug does this fix ? Any link ?
> For rubygem-rest-client, we're still waiting for the maintainer to
> approve, as far as I can see.
>

the gitlab port has the following security bug:
https://about.gitlab.com/2017/04/05/gitlab-9-dot-0-dot-4-security-release/

But I cannot apply anything (you even can not run it currently) as the
rubygem-google-api-client upgrade has broken the dependency tree.
To explain it a little bit more:
the new rubygem-google-api-client depends on a module > 3.0.
but rubygem-rest-client needs version < 3.0

This is a run dependency, you will not see while building the port.

But gitlab depends on both ports, which makes it completely broken.
You cannot run it anymore.

I hope that makes it clear, that commiting this port 
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218366) is really crucial.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook


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

Update of devel/rubygem-google-api-client broke www/rubygem-rest-client (blocks security related update)

[Matthias Fechner]

Dear all,

the upgrade of devel/rubygem-google-api-client broke
www/rubygem-rest-client.

The new devel/rubygem-google-api-client points to a dependency that is
to new for
www/rubygem-rest-client.

The update of rubygem-rest-client 2.0.1 fixes that:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218366

Could a commit please commit this, as it blocks a critical security update for 
port www/gitlab.

Thanks a lot.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: net/samba46

[Matthias Fechner]

Am 05.04.2017 um 00:02 schrieb Doug Sampson:
> When I try to join a domain after building samba46, I get this error message:
>
> root@aries:/usr/local/etc # net ads join -U dspadmin%
> Failed to join domain: failed to create kerberos keytab
> root@aries:/usr/local/etc #
>

have you seen the following entry:
20170401:
  AFFECTS: net/samba44, net/samba45, net/samba46 and devel/p5-Parse-Pidl*
  AUTHOR: ti...@freebsd.org

  It turned out that arbitary versions of p5-Parse-Pidl may lead to the
  hard to explain crashes of the Samba server and utilities(in particular
  we suspect it was responsible for the troubles with the DC provisioning).

  So, from now on net/samba* ports use bundled version of Pidl. You need to
  remove external package from the system:

  pkg delete -f p5-Parse-Pidl p5-Parse-Pidl44


For me samba43 is working fine. Every newer version fails and all
windows PCs refuses to connect to samba.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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 to see package dependencies (scponly depends on ccache?)

[Matthias Fechner]

Am 05.02.2017 um 14:23 schrieb tech-lists:
> does your /etc/make.conf have a reference to ccache ?

/etc/make.conf is empty, only my poudiere make.conf holds the following:
DEFAULT_VERSIONS=php=5.6 apache=2.4 mysql=10.1m bdb=6 ssl=openssl
WITH_BDB6_PERMITTED=1
WITH_OPENSSL_PORT=yes
WANT_OPENLDAP_SASL=yes

WITH_MPM=event
OPTIONS_UNSET=DEBUG DOCBOOK EXAMPLES
OPTIONS_SET=proxy dav ssl ldap

DISABLE_LICENSES=yes

All packages (build with poudiere on another machine) are installed
using pkg.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

How to see package dependencies

[Matthias Fechner]

Hi all,


I just tried:

pkg delete ccache (as I do not need it on servers, poudriere should
install it automatically if required?)


But it tries to deinstall:

Installed packages to be REMOVED:
ccache-3.2.5_2
scponly-4.8.20110526_2

How can I find out why it tries to deinstall scponly if I try to
deinstall ccache?
(that does not make any sense)

Thanks a lot.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Maintainer timeout for patch reported (www/redmine)?

[Matthias Fechner]

Dear all,


could a commit please have a look here:

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


I reported it a long time ago and the fix is really simple and will not
break anything.
Thanks.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Samba43 install error

[Matthias Fechner]

Am 28.12.2016 um 14:32 schrieb Gerard Seibert:
> I am unable to update samba43. The following error message is displayed:
>
> samba43-4.3.13 cannot install: SASL support requested and
> openldap-client-2.4.44  is installed.
> *** Error code 1
>
> Stop.
> make: stopped in /usr/ports/net/samba43
>

make sure you have in your make.conf (if poudriere user, use
/usr/local/etc/poudriere.d/make.conf):

WANT_OPENLDAP_SASL=yes

Rerun poudriere to rebuild all necessary dependencies including samba43.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook


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

Maintainer-Upgrade textproc/apache-solr to version 6.3.0

[Matthias Fechner]

Dear all,


could a commiter please look into:

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


Many thanks!


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Security Update roundcube

[Matthias Fechner]

Dear all,


could a commiter please priorities:

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


It is a security related fix:

https://vuxml.freebsd.org/freebsd/125f5958-b611-11e6-a9a5-b499baebfeaf.html


Thanks a lot!


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Bug in heimdal dependency for bdb (forces version 5 and ignores defined version 6)

[Matthias Fechner]

Am 19.11.2016 um 14:13 schrieb Herbert J. Skuhra:
> security/heimdal/Makefile:64:BDB_USES=bdb:5 localbase
>
>> Is this wanted or an unwanted side effect?
> No, idea. Change the above line and find out yourself if the port
> builds/works with bdb6. Good luck!

I solved it by disabling the complete BDB support for this port.

Thanks.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Piwik 2.17.1

[Matthias Fechner]

Hi Torsten,

Am 16.11.2016 um 09:36 schrieb Torsten Zuehlsdorff:
> It was already assigned to and processed by me. And a second ago
> committed. :)
>

sry, was maybe to fast here :)

> Can you please elaborate on this? I couldn't find any hints for a
> security issue. Or do you mean critical in sense of "fix critical bugs"?

tested your new version and works perfectly fine!
Thanks for the new version.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Bug in heimdal dependency for bdb (forces version 5 and ignores defined version 6)

[Matthias Fechner]

Dear all,


I'm not sure what is happening but it seems that the heimdal port is a
little bit buggy.

I have in my poudiere builds the following defined:

DEFAULT_VERSIONS=php=5.6 apache=2.4 mysql=10.1m bdb=6 ssl=openssl
BDB_DEFAULT=6
WITH_BDB6_PERMITTED=1

But for an unclear reason it seems that heimdal pulls in bdb=5 and does
not use my bdb=6 definition.

Is this wanted or an unwanted side effect?

Thanks!


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Piwik 2.17.1

[Matthias Fechner]

Hi,


could a commit please look on:

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

As I see it, it is a critical update.

Thanks.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Commiter required

[Matthias Fechner]

Am 31. Oktober 2016 15:44:03 MEZ, schrieb Ben Woods :
>All done :)

Thanks a lot!

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

Commiter required

[Matthias Fechner]

Hi,


could a commiter please commit:

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


Thanks a lot!


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Commiter for www/drush update required

[Matthias Fechner]

Am 20.10.2016 um 08:36 schrieb Matthias Fechner:
> could a commiter please have a look on:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213612
>

anyone willing to commit it?
Thanks.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Commiter for www/drush update required

[Matthias Fechner]

Am 20.10.2016 um 08:40 schrieb Kubilay Kocak:
> Thank you Matthias, don't forget to set maintainer-approval to + on
> attachments for ports you are maintainer of. You can do this with:
>
> Attachment -> Details -> maintainer-approval [+]
>
> Note: The maintainer-*approval* flag (on attachments/patches) is
> different than the maintainer-*feedback* flag (at the bug level).
>
> The former is used to signal approval on a proposed change, the latter
> is not.
>

Thanks Koobs!
Will do it then next time, as you already did it for me ;)


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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

Commiter for www/drush update required

[Matthias Fechner]

Dear all,


could a commiter please have a look on:

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


Thanks a lot!


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: www/drush looking for commiter

[Matthias Fechner]

Thanks!

Am 7. Oktober 2016 20:35:33 MESZ, schrieb Kurt Jaeger :
>Hi!
>
>> looking for a commiter for:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213254
>
>Done.
>
>-- 
>p...@opsec.eu+49 171 3101372 4 years
>to go !

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
___
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"

www/drush looking for commiter

[Matthias Fechner]

Dear all,


looking for a commiter for:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213254

Thanks a lot!

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: Drush update 8.1.5

[Matthias Fechner]

Am 26.09.2016 um 12:47 schrieb Matthias Fechner:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213000
>

could a commiter please be so kind and look into it?
Thanks!


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

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