On Fri, 20 Dec 2024 02:35:01 +0100
Daniel Engberg wrote:
> On 2024-12-20T02:06:46.000+01:00, Michael Gmelin
> wrote:
>
> >> On 20. Dec 2024, at 00:18, Daniel Engberg
> >> wrote:
> >
> >>
> >>
> >> O
On 20. Dec 2024, at 00:18, Daniel Engberg
wrote:
>
>
> On 2024-12-19T23:30:41.000+01:00, Michael Gmelin
> wrote:
>
>>
>>
>> On 19. Dec 2024, at 22:26, Daniel Engberg
>> wrote:
>>>
>>> On 2024-12-19T21:33:14.000+01:00, Mich
On 20. Dec 2024, at 00:18, Daniel Engberg wrote:On 2024-12-19T23:30:41.000+01:00, Michael Gmelin <gre...@freebsd.org> wrote:On 19. Dec 2024, at 22:26, Daniel Engberg <daniel.engberg.li...@pyret.net> wrote:On 2024-12-19T21:33:14.000+01:00, Michael Gmelin <gre...@freebsd.org> wr
On 19. Dec 2024, at 22:26, Daniel Engberg wrote:On 2024-12-19T21:33:14.000+01:00, Michael Gmelin <gre...@freebsd.org> wrote:On Thu, 19 Dec 2024 20:39:54 +0100Daniel Engberg <daniel.engberg.li...@pyret.net> wrote: Hi, While this should be uneventful if possible please try PR 28326
i?id=283266
>
> Best regards,
>
> Daniel (diizzy@)
>
Prior to testing, one question: The bug indicates that the port
maintainer was not involved in these changes - is this true and has it
been resolved in the meantime?
Best
Michael
--
Michael Gmelin
23 | struct _LIBCPP_TEMPLATE_VIS char_traits;
| ^
1 error generated.
.. which appears to be similar to the issue with devel/poco and fixed
in commit c55157301f317ab8166349340d4cc0765deaac12,
Michael
the link.
I resolved it with ..
pkg delete -f gstreamer1-plugins
cd /usr/ports/multimedia/gstreamer1-plugins
make clean
make
make reinstall
Michael
Hi,
It's really excellent news.
I'll be glad to test it, plz share patch.
Best regards,
Michael
On Thu, 22 Aug 2024, 14:06 Norbert Grundmann, wrote:
> So for all who may want to use eclipse sdk - I got a native version 4.32
> working on FreeBSD 13. At lest I could call it w
eebsd.org/threads/nut-2-8-0-generic-ups-blazer_usb-cant-claim-usb-device.90744/
Best
Michael
--
Michael Gmelin
On 6/17/24 02:06, Gleb Popov wrote:
On Sun, Jun 16, 2024 at 5:14 PM Michael Butler
wrote:
I have KDE5 installed; this pulls in devel/kf5-solid which has a
dependency on sysutils/bsdisks like so ..
imb@d5540:/usr/ports/devel/kf5-solid> less Makefile
PORTNAME= solid
DISTVERS
ils/bsdisks: Switch to Qt 6
PR: 279168
.. I now have to build and maintain *both* versions of QT.
This makes no sense to me. Can this be fixed to build with just the
installed version?
Michael
ot exit in a
> timely manner. Continuing to wait for it to stop..
>
> Any help will be appreciated.
>
> Thank you.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279362
That's regarding 10.11.8
Dunno if that fix will deal with 10.6.18 as well
Regards,
Michael
> On 27. Apr 2024, at 08:56, Andrea Venturoli wrote:
>
> Hello.
>
> First of all, thanks for your work.
>
> I've got a 14.0/amd64 system where I run Poudriere in a jail, but if I
> upgrade it from 3.4.0 to 3.4.1_1 it stops working.
> E.g.
>
>> # poudriere bulk -f /root/133amd64.lst -v -j 1
install
'mail/spamassassin'.
Is anyone aware of an alternative to 'sa-update' that uses DNS for checking
channels and updating if appropriate? Only downloading needed, no compilations,
no gpg, … [2]
Thanks and regards,
Michael
[1] Sorry, German, only:
https://www.hei
On 4/17/24 17:40, Dimitry Andric wrote:
On 17 Apr 2024, at 23:07, Michael Butler wrote:
In a clean environment with default options on -current, I get ..
error[E0412]: cannot find type `_Pred` in this scope
-->
/usr/ports/mail/thunderbird/work/.build/x86_64-unknown-freebsd/release/bu
tor<_Pred> {
| +++
Any hints?
Michael
> On 4. Apr 2024, at 09:31, Chris wrote:
>
> I do all of my development in jails. As such I have no use for poudriere(8).
> But an attempt to build editors/vscode threw the following:
>
> The limit imposed by poudriere(8) for the maximum number of files allowed to
> be
> opened by a jail (de
Gleb Popov wrote:
>
> On Wed, Mar 20, 2024 at 11:16 PM Michael Grimm wrote:
>> Compilation fails:
>>
>> cc -pthread -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG
>> -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC
>&g
5 errors generated.
error: command '/usr/bin/cc' failed with exit code 1
FAILED: install script '/bin/bash
/wrkdirs/usr/ports/dns/knot-resolver-current/work/knot-resolver-v6.0.6/manager/scripts/install.sh
/usr/local/bin/python3' failed with exit code 1.
Both SO_PASSCRED and SCM_CREDENTIALS aren't defined in the complete git
repository.
Is there a way to include Linux compatibility regarding sockets?
Thanks and regards,
Michael
> On 16. Mar 2024, at 10:45, void wrote:
>
> On Sat, 16 Mar 2024, at 08:28, Miroslav Lachman wrote:
>
>> For vulnerabilities, there is VuXML and pkg audit, not removing
>> vulnerable port from the tree.
>
> I'm talking about *moving* them to a *different* tree, with different
> priorities
> On 14. Mar 2024, at 23:59, Daniel Engberg
> wrote:
> On 2024-03-14T23:27:53.000+01:00, Tomoaki AOKI
> wrote:
>> On Thu, 14 Mar 2024 22:17:39 +0100
>> Daniel Engberg wrote:
>>
>>
>>> On 2024-03-14T21:49:46.000+01:00, Michael Gmelin
>
> On 14. Mar 2024, at 21:38, Daniel Engberg
> wrote:
>
> On 2024-03-12T15:15:49.000+01:00, Eugene Grosbein wrote:
>> 12.03.2024 3:24, Daniel Engberg пишет:
>>
>> [skip]
>>
>>
>>> Another possible option would be to add something to the port's matedata
>>> that makes pkg aware and easy
While I'm not using 515, I needed something like this patch to build
drm-61 after the BUS_RELEASE_RESOURCE changes in commit 9dbf5b0:
--- drivers/gpu/drm/i915/intel_freebsd.c.orig 2024-02-24 10:15:24 UTC
+++ drivers/gpu/drm/i915/intel_freebsd.c
@@ -74,9 +74,9 @@ bsd_intel_pci_bus_release_mem(de
> On 28. Feb 2024, at 20:22, Florian Smeets wrote:
>
> Dear ports community,
>
> as the removal of ports is a recurring source of friction and dispute we
> would like to add a ports removal and deprecation policy to the porters
> handbook.
>
> We tried to find a sensible middle ground bet
Mark Millard wrote:
> On Feb 26, 2024, at 01:06, Michael Grimm wrote:
>> Possible solutions:
>>
>> 1) dns/knot3-lib should store its libraries and includes into a different
>> location as dns/knot3 does
>
> A variation of that is that dns/knot-resolv
Mark Millard wrote:
> Michael Grimm wrote on
> Date: Sun, 25 Feb 2024 19:46:22 UTC :
>> I am trying to install dns/knot3 and dns/knot-resolver simultaneously.
>>
>> Compilation is achieved with the help of poudriere which complains about
>> dns/knot-resolver:
&
-3.3.3_1 as part of dns/knot3 shouldn't conflict with dns/knot3.
Questions:
#) Bug?
#) How to resolve this conflict?
#) Anyone running both ports in parallel?
Thanks and regards,
Michael
Moin Rahman wrote:
>> On Feb 25, 2024, at 6:15 PM, Michael Grimm wrote:
>> P.S. Please forgive my lack in experience with PRs ;-)
>>Please let me know, what to correct if neccessary
>
> Well as a starter:
> 1. You do not need PORTREVISION when you alr
Moin Rahman wrote:
>> On Feb 25, 2024, at 5:04 PM, Michael Grimm wrote:
>>
>> a new version of this port has been released two month ago.
>>
>> The maintainer normally updates knot3 shortly after the release of a new
>> version. He didn't react on a
dency :-(
Michael
fully compiling with poudriere, and
running well for 1 month now.
What can I do to get this patch committed?
Shall I create a PR like
https://cgit.freebsd.org/ports/commit/?id=11f44f375254e07a262455aaf8311bfd4bbedb67
Regards,
Michael
knot3-3.3.4_1.diff
Description: Binary data
Hi,
It is nice to hear that I'm not only user of Eclipse and somebody still
loves it.
I'll prepare patch soon and come back to you for testing if possible.
Thank you,
Michael
On Tue, 23 Jan 2024, 18:39 Norbert Grundmann, wrote:
> Hallo Ronald,
>
> I figured out, that the
Michael Grimm wrote:
> I do not understand why the recent fix
> https://cgit.freebsd.org/ports/commit/?id=9eb1bbbe39f24802e8dbd45074b4c2f319d4d2c0
> might have broken that port.
After recompilation of all ports and subsequent reinstallation of all of them,
this issue doesn't
that port.
After reverting back to dns/libidn2-2.3.4 /usr/local/bin/host works as usual.
Regards,
Michael
Hi Ivan,
Looks good. Could you please put patch on reviews.freebsd.org?
Thx,
Michael
On Fri, 19 Jan 2024, 14:11 Rozhuk Ivan, wrote:
> Hi!
>
>
> graphics/mesa-* uses SYS_kcmp [1] to compare two fds:
>
> int
> os_same_file_description(int fd1, int fd2)
> {
> On 29. Dec 2023, at 07:24, Yuri wrote:
>
>
> Hi,
>
>
>
>
>
> I have a valid ZFS pool assigned to the ZPOOL variable.
>
> poudriere creates these directories in this pool:
>
> poudriere/
>
> poudriere/jails
>
>
>
> These directories remain empty.
>
>
>
> poudriere works fine, b
Moin Rahman wrote:
>> On Dec 20, 2023, at 4:06 PM, Michael Grimm wrote:
>>
>> Hi,
>>
>> today's commit broke misc/freebsd-release-manifests need fixing. There are
>> no longer 12.3 versions available.
>>
> [snip]
> Thanks for the he
ASE
/usr/ports/misc/freebsd-release-manifests/files/MANIFESTS/powerpc-powerpc64-12.4-RELEASE
/usr/ports/misc/freebsd-release-manifests/files/MANIFESTS/powerpc-powerpcspe-12.4-RELEASE
/usr/ports/misc/freebsd-release-manifests/files/MANIFESTS/sparc64-sparc64-12.4-RELEASE
Regards,
Michael
Guido Falsi wrote:
> On 02/12/23 21:37, Michael Grimm wrote:
>> Hi,
>> I am following the git repository for ports and using poudriere to compile
>> those.
>> Today I stumbled over:
>> 20231125:
>> AFFECTS: users of lang/php81
>> AUTHOR: b...@f
I am doing wrong. And I would appreciate if
someone could explain it to me.
Thanks in advance and regards,
Michael
Colin Percival wrote
> On 11/20/23 14:05, Michael Grimm wrote:
>> after the 14.0 release announcement, port misc/freebsd-release-manifests is
>> broken, due to legacy 'RC4' references:
>
> Thanks, I forgot to update the plist when I updated the MANIFEST files.
&g
o access file
/wrkdirs/usr/ports/misc/freebsd-release-manifests/work/stage/usr/local/share/freebsd/MANIFESTS/riscv-riscv64-14.0-RC4:No
such file or directory
*** Error code 1
Regards,
Michael
Charlie Li wrote:
> The next bump will be to 3.11, in keeping with the n-1 cadence. 3.12 is not
> ready yet, not without the setuptools overhaul amongst other things.
Just out of curiosity: does a time schedule exist, yet?
Regards,
Michael
Herbert J. Skuhra wrote:
>
>
> On Sat, Oct 07, 2023 at 04:59:31PM +0200, Michael Grimm wrote:
>> Hi
>>
>> I am running net/openntpd with a constraint:
>>
>> …
>> constraint from "9.9.9.9"
>>
>> After the recent upgrade of sec
ly get you back to consistency.
You may also wish to check the output of ..
cd /usr/ports
git status
git diff
.. for any wider scale issues,
Michael
tions and usage,
Michael
On 2023-08-17 06:46, Koichiro Iwao wrote:
On Mon, Aug 14, 2023 at 11:24:54AM +0200, Osipov, Michael (IN IT IN) wrote:
Folks,
can someone review my open patches for ports where maintainers aren't
responding:
* Bug 272899 - devel/maven: improve port for multiple parallel versions (I
a
urity/openssl30: files/extra-patch-util_find-doc-nits
does not apply cleanly
* Bug 272995 - dns/bind-tools (dns/bind918): fails to build with
MANPAGES=off if sphinx is installed
Thanks in advance,
Michael
> On 17. Jun 2023, at 02:27, Danilo G. Baio wrote:
>
>
>
>> On Fri, Jun 16, 2023, at 17:55, Yuri wrote:
>> It looks like portscout is stuck again.
>>
>> The numbers changed once 27+ hours ago, and didn't change again.
>>
>> Normally portscount updates numbers at least several times a day.
Rahman :
>
>
>> On Mar 30, 2023, at 6:13 PM, Michael wrote:
>>
>> Hi,
>> as it seems the horde upstream repos contain some php8 fixes.
>> Wouldn't it be possible to create *horde*-devel ports instead of
>> just deleting the *horde* ports en
Hi,
as it seems the horde upstream repos contain some php8 fixes.
Wouldn't it be possible to create *horde*-devel ports instead of
just deleting the *horde* ports end of the month.
cu
...
Michael
--
sender_key.asc
Description: application/pgp-keys
Folks,
another plea and look and apply my patch for PR 267690? Fully tested and
described. The patch is for OpenJDK 8 for now, but supply for 11 and 17
as well since the issue is present there too.
Regards,
Michael
> On 6. Mar 2023, at 21:29, Dave Horsfall wrote:
>
> On Mon, 6 Mar 2023, portsc...@freebsd.org wrote:
>
> [...]
>
>> +-+
>> cad/ifcopenshell| 0.6.0 |
>> blenderbim-230306
>
Guys,
can someone please have a look at this new port? Fully developed patch,
has now been production for a long time here. I worked closely with the
upstream maintainer to bring all relevant changes upstream.
Thanks,
Michael
Juraj Lutter wrote:
>> On 16 Jan 2023, at 16:49, Michael Grimm wrote:
>> I wonder if the following condition for triggering blacklistd is appropriate:
>>
>>
>> /* notify blacklistd of SASL authentication failure */
>> pfilter_no
On Fri, 20 Jan 2023 17:54:15 +0100 (CET)
free...@oldach.net (Helge Oldach) wrote:
> Michael Gmelin wrote on Fri, 20 Jan 2023 17:31:43 +0100 (CET):
> > The CA_BUNDLE knob was enabled on ftp/curl by default for many years
> > and was just recently disabled (in c63a8f65af, j
On Fri, 20 Jan 2023 17:15:07 +0100 (CET)
free...@oldach.net (Helge Oldach) wrote:
> Michael Gmelin wrote on Fri, 20 Jan 2023 17:07:41 +0100 (CET):
> > Well, whatever is done, such a change needs to be managed properly,
> > which includes adding an entry to UPDATING in p
On Fri, 20 Jan 2023 09:15:32 +0100 (CET)
free...@oldach.net (Helge Oldach) wrote:
> Michael Gmelin wrote on Fri, 20 Jan 2023 08:51:31 +0100 (CET):
> > > On 20. Jan 2023, at 07:45, free...@oldach.net wrote:
> > > Definitely however ca_root_nss should go away in favor of th
> On 20. Jan 2023, at 09:15, free...@oldach.net wrote:
>
> Michael Gmelin wrote on Fri, 20 Jan 2023 08:51:31 +0100 (CET):
>>>> On 20. Jan 2023, at 07:45, free...@oldach.net wrote:
>>> Definitely however ca_root_nss should go away in favor of the built-in
>>
ILES+=Private_Root_CA.pem
> post-build:
>for f in ${EXTRA_DISTFILES}; do \
>${CAT} ${DISTDIR}/"$${f}" >> ${WRKDIR}/ca-root-nss.crt; \
>done
> .endif
>
> Definitely however ca_root_nss should go away in favor of the built-in
> cert infrastructure and the ports still referring to this legacy should
> be updated.
Without tooling in base to update certs independently of updating the OS this
will be very painful.
Michael
gt; into ca-root-nss port, which can be run from cron or by hand, is needed?
>
Whatever we do, let’s make sure we don’t break existing setups - this needs to
be well coordinated. Personally, I don’t want to update (and reboot) the OS in
order to get a current list of trusted CAs (at least as long as pkgbase isn’t
mainstream this is an issue).
Michael
x27;Temporary
authentication failure'.
Has this been intended?
Regards,
Michael
I'm having a problem creating a jail @home that I had no problems
building at work. The build environment at work was 13-RELEASE
(GENERIC) amd64
@home
UNAME:
Build system: FreeBSD firewall.mikej.com 13.1-STABLE FreeBSD 13.1-STABLE
#21 stable/13-n253337-16603f60156e: Wed Dec 28 08:22:48 EST 20
__
On Monday, December 12, 2022, wrote:
> Dear port maintainers,
>
> The portscout new distfile checker has detected that one or more
> unmaintained ports appears to be out of date. Please take the opportunity
> to check each of the ports listed below, and if possible and appropriate,
> submit/c
Folks,
can your some look at my patch for PR 267625? The port contains a
CJK-related fonts custom patch which breaks vanilla GS and fails when
converting valid PS files to PDF. My patch removes those custom patches
from files/ to make it work as with vanilla GS.
Regards,
Michael
Folks,
can your some look at my patch for PR 267690? Fully tested and
described. The patch is for OpenJDK 8 for now, but supply for 11 and 17
as well since the issue is present there too.
Regards,
Michael
On 8. Dec 2022, at 08:24, Kevin Oberman wrote:On Wed, Dec 7, 2022 at 7:33 AM Martin Neubauer wrote:On Wed, 7 Dec 2022, Einar Bjarni Halldórsson wrote:
> Hi,
>
> I created a PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261148
> which I've been updating when new ve
e more careful in placing
kernel directives in src.conf!
--mikej
On 11/24/2022 10:33 AM, David Wolfskill wrote:
On Thu, Nov 24, 2022 at 10:22:01AM -0500, Michael Jung wrote:
...
As of 2022-11-24 ~10:00 AM EST if you have /usr/ports made using
portsnap or poudriere tracking main
...
poudriere:
===&
Hi!
This has been an issue for several weeks(months?) and I'm just getting
around to digging into the issue.
As of 2022-11-24 ~10:00 AM EST if you have /usr/ports made using
portsnap or poudriere tracking main
[root@firewall /usr/local/poudriere/ports/default]# git remote get-url
origin
> On 7. Nov 2022, at 19:58, Yuri wrote:
>
> This happened several times to me. I had to revert commits. Now this
> happened again.
>
>
> When several ports have changes in the tree and one of the ports is committed
> with 'cd / && git commit .' - other ports sometimes also get
> into the
Folks,
can someone have a look at my trivial, one line patch?
Thanks,
Michael
I've seen that you upgraded this port already, but may I remind you at the
following glitch:
Michael Grimm wrote:
> BTW: One glitch in fail2ban.conf file:
>
> # Option: allowipv6
> # Notes.: Allows IPv6 interface:
> # Default: auto
> #
Michael Grimm wrote:
> Cy Schubert wrote
>> I've been able to reproduce the problem here. Please try the attached patch
>> obtained from our upstream. It fixes a dovecot regression that crept into
>> the latest release.
>
> Yes, I am running dovecot jails
ate arm64?
>
I documented the procedure I used to build arm64 packages on amd64 using
poudriere a couple of years ago, maybe it helps:
https://blog.grem.de/sysadmin/FreeBSD-On-rpi3-With-crochet-2018-10-27-18-00.html
Best
Michael
Cy Schubert wrote
> In message , Roger
> Marquis w
> rites:
>> Cy Schubert wrote:
>>> Michael Grimm writes:
>>>> this is a recent stable/13-n252672-2bd3dbe3dd6 running =
>>>> py39-fail2ban-1.0.1_2 and python39-3.9.14
>>>> I hav
x27;. Using default one: 'auto'
After activating this entry to "allowipv6 = auto" those warnings disappear.
Regards,
Michael
Folks,
I have prepared and tested a Git-formatted patch [1].
Kindly rebase and apply the patch. This is crucial for the next quarterly and
PHP 7.x removal.
I am the port maintainer.
Thanks,
Michael
[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266448
> On 8. Sep 2022, at 05:03, Tomek CEDRO wrote:
>
> On Mon, Sep 5, 2022 at 11:52 PM Michael Gmelin wrote:
>> On 5. Sep 2022, at 22:45, Tomek CEDRO wrote:
>> Hello world :-)
>> After `git pull` I get this warning now on each port build:
>> /!\ ERROR: /!\
>
> On 5. Sep 2022, at 22:45, Tomek CEDRO wrote:
>
> Hello world :-)
>
> After `git pull` I get this warning now on each port build:
>
> /!\ ERROR: /!\
> Ports Collection support for your FreeBSD version has ended, and no
> ports are guaranteed to build on this system. Please upgrade to a
> su
fourth one,
which is still in its planning stage, is requiring much more efforts and I
would be happy to work with anyone interested in it.
Michael
Good Morning Folks,
I now have lurch built over Poudriere; please see
https://paste.mozilla.org/EcEH1jPw.
I enabled portlint and developer_mode.
How do I push this to freshports?
Is there anything else to do?
On Sat, 27 Aug 2022 at 21:33, Felix Palmen wrote:
> * Michael A. Oshin [20220827
> On 29. Aug 2022, at 00:33, Pete Wright wrote:
>
> On Sun, Aug 28, 2022 at 11:05:24PM +0200, Michael Gmelin wrote:
>>
>>
>>>> On 28. Aug 2022, at 19:23, Pete Wright wrote:
>>>
>>> hey there - i had a question about an apparent ve
> On 28. Aug 2022, at 23:05, Michael Gmelin wrote:
>
>
>
>
>>> On 28. Aug 2022, at 19:23, Pete Wright wrote:
>>>
>> hey there - i had a question about an apparent version numbering issue
>> with the nginx-full port:
>> https://www.
> On 28. Aug 2022, at 19:23, Pete Wright wrote:
>
> hey there - i had a question about an apparent version numbering issue with
> the nginx-full port:
> https://www.freshports.org/www/nginx-full/
>
> on April 10th the version number is: 1.20.2_9,2
> then on the next update (may 31) the vers
On Sun, 28 Aug 2022 03:21:24 -0700
Cy Schubert wrote:
> In message <16b4-76a1-4e46-b7c3-60492d379...@freebsd.org>,
> Michael Gmelin w
> rites:
> >
> >
> >
> > > On 28. Aug 2022, at 10:42, free...@oldach.net wrote:
> > >=20
> >
ports
would be more clear. Another advantage would be that directories are only
created for services that are actually enabled/started.
Cheers
Michael
> On 27. Aug 2022, at 15:18, free...@oldach.net wrote:
>
> Michael Gmelin wrote on Sat, 27 Aug 2022 15:02:04 +0200 (CEST):
>> (you're removing /var/run, which shouldn't be removed
>
> Not quite. It's actually not uncommon to boot with an empty /var. Ple
> On 27. Aug 2022, at 12:54, FreeBSD User wrote:
>
> Am Sat, 27 Aug 2022 11:21:40 +0200
> Michael Gmelin schrieb:
>
>>>> On 27. Aug 2022, at 08:31, FreeBSD User wrote:
>>>
>>> Hello,
>>>
>>> I'm referencing to Bug 259
On Sat, Aug 27, 2022, 17:31 Felix Palmen wrote:
> * Michael A. Oshin [20220827 17:26]:
> > Thanks everyone. I missed those reply because I subscribed to a daily
> > digest.
>
> I took you on CC now. Please also consider my other answers I added to
> the list only.
into the
~/.purple/plugins dir for pidgin to use. I think that is where the otr lib
goes into too.
I shall drop the use GH then, @Cy had earlier recommended it.
On Sat, Aug 27, 2022, 15:22 Ronald Klop wrote:
> Hi Michael,
>
> This was answered yesterday.
>
> https://lists.
> It is really hard to always chenge our local repository and patch whenever
> clamav has been
> patched and modified for what reason ever.
>
> Tahanks for reading,
>
Why don’t you simply add an rc script to your appliance that creates the
missing directory/directories on boot before clamav is started?
Best
Michael
it built? I think
the do-install throws error too for GH.
On a final note, what other steps do I need to do to finalise and publish
into ports? I have read the pages but need quicker porting.
Michael
On Fri, Aug 26, 2022, 16:12 Ronald Klop wrote:
> Mmm, lets take another look at it.
>
Good Morning folks,
I made a few changes to the liblurch Makefile. It now points to the
developer's github for the pkg. See
https://github.com/micadeyeye/freebsd-ports/blob/master/security/liblurch/Makefile
.
One problem I have with the liblurch is that it wants to run '.configure'.
See the below
ert can be more secure if you pin it, but since their
approach was ignoring cert verification completely, this level of security
probably isn’t what they were going for.
Cheers
Michael
> .
>
> Michael Gmelin wrote on 2022/08/04 07:58:
>>> Thanks, I simply copy and pasted
> On 4. Aug 2022, at 00:55, Michael Gmelin wrote:
>
>
>
>> On 4. Aug 2022, at 00:38, Tatsuki Makino wrote:
>> Hello.
>>
>> In git-2.37.1/http.c...
>>
>> ︙
>> if (!curl_ssl_verify) {
>>
ng they already
tested that exact value outside of poudriere), since my response was about the
mechanics of how to get that variable in and not its name.
Cheers
Michael
> Regards.
er way to achive that
> task?
>
If you read /usr/local/bin/poudriere you see that it filters the
environment. So neither GIT_NO_SSL_VERIFY will come through, nor HOME
(which also means that git can't read $HOME/.gitconfig).
The pragmatic solution would be to create a git wrapper script and tell
poudriere to use it:
cat >/tmp/git_wrap <>/usr/local/etc/poudriere.conf
Cheers
Michael
--
Michael Gmelin
> On 3. Aug 2022, at 01:07, Dan Mahoney wrote:
>
> Hey there all,
>
> At the dayjob we have a fleet of Dell Poweredge servers that can use either
> mptsas or mrsas -- if you use mptsas, you use mptutil (in base) to check the
> state of the card.
>
> If you use mrsas, you need megacli, whi
Look at what you’re trying to commit and check if there are any conflict marker
(>>>, <>, =).
> On 28. Jul 2022, at 23:44, Nuno Teixeira wrote:
>
>
> Hello,
>
> I'm trying to commit to 2022Q3 PR 265530 and after solving Makefile conflicts
> (PORTREVISIONs), git push
Guys,
please commit the supplied patch. devel/py-click is broken for months.
Michael
1 - 100 of 147 matches
Mail list logo