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
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,
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
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:
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
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
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
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:
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
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
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
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
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:
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
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
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
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
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:
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 f
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
>
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
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=
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
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.
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
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`
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
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
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
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
>
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
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
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
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:
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
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
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
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
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
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
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
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
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
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
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
>
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
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
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
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
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
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)
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
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
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
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
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
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
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
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
-
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
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ß
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
--
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
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
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
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
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
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
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 =
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
>
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:
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
--
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
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
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:
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
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
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,
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
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:
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:
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
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
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
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
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
>
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
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
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
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
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
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
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
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
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 strivin
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
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
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
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
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
1 - 100 of 140 matches
Mail list logo