Hello.
This is from my notes on the build of my Wed May 27 13:16:29 2020 JST
installation.
svnlite update -r 502567 www/seamonkey
svnlite update -r 505639 Mk/bsd.gecko.mk
svnlite update -r 505746 MOVED
svnlite update -r 491972 www/firefox/Makefile.options
svnlite update -r 509662
Hello Michael,
Thank you for bug report and patch. I confirmed your patch fixes the
problem with 12.1-RELEASE.
From: Michael Grimm
Subject: latest Makefile breaks compilation of security/clamav if base is
lacking sendmail
Date: Sun, 5 Jul 2020 15:37:13 +0200
> I managed to get compilation
> On 5 Jul 2020, at 16:42, Brandon helsley wrote:
>
>> For making changes to a port, I find ’svn diff’ to be the easiest way by
>> far. I tend to do this:
>> 1. svn up my work-in-progress ports tree
>> 2. Make the changes and run tests (portlint, poudriere testport etc)
>> 3. cd /ports; svn
# svn diff sysutils/toybox > /home/vidar/portdiffs/sysutils_toybox-0.8.4.diff
Yes the whole message cleared it up. But right here now I see
/home/vidar/portdiffs/sysutils_toybox-0.8.4.diff is where you keep the diff
before submiting it.
>
> On Jul
Hi!
> > You could grab packagesite.txz from your repo, untar that and then
> > grep '"name":"pkg"' packagesite.yaml
> > Any brokenness in /var/db/pkg/ ?
>
> How would I recognize brokenness ? The files that should be there
> are there.
>
> > There's a per-repo sqlite3 database which you could
Hi!
> So, had a second system, same pkg-version before, and
> it has the same problem.
Found a fix with:
pkg update -f
Then
pkg upgrade
does the necessary stuff.
--
p...@opsec.eu+49 171 3101372Now what ?
___
> On 5 Jul 2020, at 02:46, Brandon helsley wrote:
[…]
> The documentation for (diff -u) says "To create a suitable diff for a single
> patch, copy the file that needs patching to something.orig, save the changes
> to something and then create the patch:"
> % diff -u something.orig something
сб, 4 июл. 2020 г. в 08:11, Hiroki Sato :
> Mateusz Piotrowski <0...@freebsd.org> wrote
> in <34921b6e-ce3a-13e4-0cc1-3ca47b5a9...@freebsd.org>:
>
> 0m> > I am planning to revisit the multi-instance support shortly because
> I
> 0m> > am using it for a long time and I think it is useful.
Hi,
I am running 12.1-STABLE (r362940), ports head (541271) and compile all my
ports with poudriere-devel
My /etc/src.conf contains …
WITHOUT_SENDMAIL=yes
… thus I do not have /usr/lib/libmilter.so in base.
The recent modification of security/clamav/Makefile breaks my setup (again
In general:
1. extract the original sources elsewhere
2. hack it to compile
3. compare the hacks against the original sources again to generate diffs.
4. put the diffs into the files/ directory of the port
5. Tweak the Makefile for all targets (fetch, extract, build, stage, etc)
Im not sure
For making changes to a port, I find ’svn diff’ to be the easiest way by far. I
tend to do this:
1. svn up my work-in-progress ports tree
2. Make the changes and run tests (portlint, poudriere testport etc)
3. cd /ports; svn diff thecategory/theport >
Please be aware that this port is maintained by x...@freebsd.org and anyone
who is subscribed to the x11 mailing list will get the portscout messaged.
This does not mean it is intended that aloof those who subscribe to x11 are
responsible for making repaired.
If you have not done so, check
On Sat, 4 Jul 2020 10:23:09 -0600, @lbutlr stated:
>On 04 Jul 2020, at 08:30, Carmel wrote:
>> I see that you are putting it all on one line. That is probably
>> easier. I like the separate entries technique simply because I find
>> it easier to read myself or quickly comment out an entry.
>
>I
13 matches
Mail list logo
