On Thu, Dec 03, 2020 at 04:57:53PM -0600, Bob Willcox wrote:
> I am trying to upgrade a 12.1-stable system installed back in July to
> 12.2-stable.
> I downloaded the new ports hierarchy and now when I attempt to run 'make
> fetchindex'
> I get these errors:
>
>
On Thu, 3 Dec 2020, Bob Willcox wrote:
I am trying to upgrade a 12.1-stable system installed back in July to
12.2-stable. I downloaded the new ports hierarchy and now when I
attempt to run 'make fetchindex'
I get these errors:
/usr/bin/env fetch -am -o /usr/ports/INDEX-12.
I am trying to upgrade a 12.1-stable system installed back in July to
12.2-stable.
I downloaded the new ports hierarchy and now when I attempt to run 'make
fetchindex'
I get these errors:
/usr/bin/env fetch -am -o /usr/ports/INDEX-12.bz2
https://www.FreeBSD.org/ports/INDEX-12.bz2
C
Eugene M. Zheganin :
>
> Found this:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=174087
>
> and this:
>
> https://svnweb.freebsd.org/base?view=revision&revision=361228
>
> How do I determine if the latter is merged into STABLE
By mergeinfo or inspecting stable branch.
It is merged to s
ds, so I will get more of socket tuples.
So, seems like FreeBSD isn't reusing client ports out-of-the-box.
Linux, on the other hand, does reuse ports for client connection, as
long as the socket tuple stays unique. How do I get the same behavior
on FreeBSD ?
Found this:
https://bugs.freebs
Hello,
I have a situation where I'm running out of client ports on a huge
reverse-proxy.
Say I have an nginx upstream like this:
upstream geoplatform {
hash $hashkey consistent;
server 127.0.0.1:4079 fail_timeout=10s;
server 127.0.0.1:4080 fail_timeou
Eugene Grosbein writes:
> 14.08.2020 17:46, Bengt Ahlgren wrote:
>
>> Then the question is whether I need openssl libraries from ports, when I
>> use that for all ports with DEFAULT_VERSIONS+=ssl=openssl due to QT5
>> requirements?
>>
>> If I want to link wi
14.08.2020 17:46, Bengt Ahlgren wrote:
> Then the question is whether I need openssl libraries from ports, when I
> use that for all ports with DEFAULT_VERSIONS+=ssl=openssl due to QT5
> requirements?
>
> If I want to link with openssl from ports, it looks like I anyway need
>
doc/en/books/handbook/SMTP-Auth.html
>> # depends on port security/cyrus-sasl2
>> SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL
>> SENDMAIL_LDFLAGS=-L/usr/local/lib
>> SENDMAIL_LDADD=-lsasl2
>>
>> Since I'm still using 11.4, I had to start using openssl from ports
/en/books/handbook/SMTP-Auth.html
>> # depends on port security/cyrus-sasl2
>> SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL
>> SENDMAIL_LDFLAGS=-L/usr/local/lib
>> SENDMAIL_LDADD=-lsasl2
>>
>> Since I'm still using 11.4, I had to start using openssl fr
curity/cyrus-sasl2
> SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL
> SENDMAIL_LDFLAGS=-L/usr/local/lib
> SENDMAIL_LDADD=-lsasl2
>
> Since I'm still using 11.4, I had to start using openssl from ports due
> to qt5 5.15. Then the above didn't work anymore, so a bit rel
curity/cyrus-sasl2
> SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL
> SENDMAIL_LDFLAGS=-L/usr/local/lib
> SENDMAIL_LDADD=-lsasl2
>
> Since I'm still using 11.4, I had to start using openssl from ports due
> to qt5 5.15. Then the above didn't work anymore, so a bit rel
SENDMAIL_LDFLAGS=-L/usr/local/lib
SENDMAIL_LDADD=-lsasl2
Since I'm still using 11.4, I had to start using openssl from ports due
to qt5 5.15. Then the above didn't work anymore, so a bit reluctantly I
added -I/usr/local/include to the CFLAGS above, fearing that some other
random include fil
lar dependencies.
>
[snip]
> I no longer have stack crashes so I can operate, but I want synth to
> work well because I'd love to dance with this bear to good music. I
> have yet to resolve my FOSS database preference issues...
>
> I have tried ' make deinstall &&am
did run out of swap space.
I now have my machine configured with 40GB of swap space (on a half-TB
HDD) after trying unsuccessfully to create swap files within the
current /usr installation. I also have ccache working well. I haven't
solved the Handbook dependencies but perhaps we can get ther
Summing up the time cost for a clean svn co and make buildkernel
buildworld release is around 75minutes while the chroot build with
release(7) is around 100minutes for my hardware setup. Builds using
make are more reasonable for driver fixes because then I can only
rebuild small part of the code wh
On Wed, Apr 8, 2020 at 8:19 PM Ruslan Garipov wrote:
> > I need to see how it works with `make release` :-)
> This is what I meant when saying "you can build the source tree for
> 13.0-CURRENT on 12.1-RELEASE"; sorry if I've confused you.
No worries, my little confusion came from `make release` be
for 13-CURRENT on
> 12-STABLE, thank you! Also will compare the time cost with the one
> presented below :-)
>
>
> Creating a "release" also has this advantage that I have memstick
> images that I can boot from directly, test what I need, even no need
> to inst
at I can boot from directly, test what I need, even no need
to install :-)
Here are my build times, for a release for AMD64/12-STABLE, I did not
select DOC nor PORTS to build, only Kernel and Base :-)
BUILD HOST (~$500): HP PROLIANT DL380G7X (HDD 1TB, 128GB RAM, 24vCPU =
2 x Intel Xeon X5660 @2.8GH
On 4/5/2020 10:05 PM, Tomasz CEDRO wrote:
> On Sun, Apr 5, 2020 at 4:59 PM Ruslan Garipov wrote:
>> I'm sorry, I forgot to ask how do you call /usr/src/release/release.sh?
>> Do you pass a configuration file to this script?
>>
>> By default /usr/src/release/release.sh checks out the source tree for
On Sun, Apr 5, 2020 at 4:59 PM Ruslan Garipov wrote:
> I'm sorry, I forgot to ask how do you call /usr/src/release/release.sh?
> Do you pass a configuration file to this script?
>
> By default /usr/src/release/release.sh checks out the source tree for
> the CURRENT branch (svn://svn.FreeBSD.org/bas
he
> binary release, which seems a bit more flexible to have just
> everything in one place, may be used to install on an external machine
> without NFS access, etc :-)
>
> It would be also nice to know the time cost of those two methods, so I
> want to verify :-)
>
>
>
he
> binary release, which seems a bit more flexible to have just
> everything in one place, may be used to install on an external machine
> without NFS access, etc :-)
>
> It would be also nice to know the time cost of those two methods, so I
> want to verify :-)
>
>
>
sed to install on an external machine
without NFS access, etc :-)
It would be also nice to know the time cost of those two methods, so I
want to verify :-)
> > 3. During /usr/src/release/release.sh I get following error as pasted
> > below. Does release.sh update /usr/ports just as it s
ork too as above?
>
> 3. During /usr/src/release/release.sh I get following error as pasted
> below. Does release.sh update /usr/ports just as it snaps from svn or
> it will use the /usr/porst that are just there and I need to provide
> /usr/ports in a state that will be bindled in
right?
2. When that works, I would like to cross-compile for ARM in a similar
manner, then attach pyOCD + GDB to debug ARM target. I guess that
should work too as above?
3. During /usr/src/release/release.sh I get following error as pasted
below. Does release.sh update /usr/ports just as it snaps from
> On 14 Mar 2020, at 12:56 , Andrew Reilly wrote:
>
> By the way, the current Samba stable release is 4.12.0 (one week old) and
> 4.11.0 was released last September. Is there some particular incompatibility
> with FreeBSD that is keeping these out of Ports? I got quite close
Not sure, i havent had a need to manually fetch a ports index in years,
portsnap auto does it all.
On Tue, 11 Feb 2020 12:19:01 -0500 Bob Willcox wrote
Thanks alot Mike. That worked for me.
Out of curriosity, is this a fairly recent change? For some reason I've
rote:
> Hi Bob,
>
>
>
> You need to install the root certificate bundle.
>
>
>
> cd /usr/ports/security/ca_root_nss/ && make install clean
>
>
>
> Cheers.
>
>
> On Tue, 11 Feb 2020 09:07:12 -0500 Bob Willcox wrote
>
>
Hi Bob,
You need to install the root certificate bundle.
cd /usr/ports/security/ca_root_nss/ && make install clean
Cheers.
On Tue, 11 Feb 2020 09:07:12 -0500 Bob Willcox wrote
Hi All,
I just installed a recent snapshot of 12.1 on a new system and when I r
Hi All,
I just installed a recent snapshot of 12.1 on a new system and when I run 'make
fetchindex'
in the /usr/ports directory I get this:
bob@han:0 /usr/ports> make fetchindex
/usr/bin/env fetch -am -o /usr/ports/INDEX-12.bz2
https://www.FreeBSD.org/ports/INDEX-12.bz
architectures.
Looks like ufs only systems do not have any problems booting.
No hints about any changes to boot processes. ZFS loads, finds zfs:zroot.
After this message some usb related stuff is printed, the last line then is
"usb2: 7 ports with 7 removable, self powered". Module opensol
Where would be the most appropriate place to track ports that are failing
to build/run due to enabling ALSR on FreeBSD12.1Prerelease?
I note that the issue regarding ntp has been addressed (refer
https://reviews.freebsd.org/D21581) but I've also come across another which
failed to run with
On Mar 6, 2019, at 3:58 PM, tech-lists wrote:
> On Wed, Mar 06, 2019 at 06:23:49PM +0100, Stefan Bethke wrote:
>>> Am 05.03.2019 um 15:09 schrieb tech-lists :
>
>>> Basically I'm looking for exclude mask functionality when updating a
>>> ports tree with pou
On Wed, Mar 06, 2019 at 06:23:49PM +0100, Stefan Bethke wrote:
Am 05.03.2019 um 15:09 schrieb tech-lists :
Basically I'm looking for exclude mask functionality when updating a
ports tree with poudriere ports.
Do I need to do this manually or have I missed something?
I don’t think it’s
> Am 05.03.2019 um 15:09 schrieb tech-lists :
>
> Hi,
>
> There are several categories of ports I'd like to avoid for some
> architectures. For example, I don't want x11 for mips.mips64. Or astronomy.
> But let's say, for this architecture, I want to build
Hi,
There are several categories of ports I'd like to avoid for some
architectures. For example, I don't want x11 for mips.mips64.
Or astronomy. But let's say, for this architecture, I want to
build everything else.
I can't see a way of excluding categories with poudriere
pon., 17 gru 2018 o 00:42 Alex McKeever
napisał(a):
>
> I ran into problems compiling the CDE in FreeBSD 12.0 RC3 (PowerPC) on my
> eMac. It says it is broken and cannot be compiled. Also, any ETA on when this
> port of the OS will go into Tier 1? Compiling software, desktop environments,
> X11
The server-class ports on powerpc64 have been in good shape for several
years. However, the desktop ports are lagging way behind. For
instance,
we are still working to get gnome and kde working properly. Other
desktop
environments are going to require more people to take up working on
them
Hi!
> > > PPC64 with the advent of Power9 is the only real alternative platform
> > > to amd64 in the data center [...]
> > I'm curious, isn't arm64 also a contender in this market ?
> Supposedly. The FF has invested in it greatly. Nonetheless, none of the
> offerings have been very good in prac
On Sun, Dec 16, 2018 at 23:10 Kurt Jaeger wrote:
> Hi!
>
> > PPC64 with the advent of Power9 is the only real alternative platform
> > to amd64 in the data center [...]
>
> I'm curious, isn't arm64 also a contender in this market ?
>
Supposedly. The FF has invested in it greatly. Nonetheless, no
Hi!
> PPC64 with the advent of Power9 is the only real alternative platform
> to amd64 in the data center [...]
I'm curious, isn't arm64 also a contender in this market ?
--
p...@freebsd.org +49 171 3101372 2 years to go !
___
fre
On Sun, Dec 16, 2018 at 08:21:14PM -0600, Justin Hibbits wrote:
> You can try to build the broken ports either by deleting the BROKEN
> line in the Makefile
True, but see below ...
> or through some poudriere trickery
-T Try building BROKEN ports by defining TRYBROKEN for
file bug reports so they can at least be
tracked. You can try to build the broken ports either by deleting the
BROKEN line in the Makefile, or through some poudriere or make variable
trickery (don't recall how in either case off-hand). That would let us
at least know why it's broken
On Sun, Dec 16, 2018, 6:33 PM Alan Somers CC the package maintainer.
>
> As for powerpc on tier 1, I'm afraid that it's not likely to ever
> happen. Powerpc is dying. If anybody were buying new ppc hardware,
> then it would be a different story. But I predict that powerpc is
> likely to be drop
If we are talking powerpc32 and not powerpc64 (as I assumed), the one
developer continuing to actively work on it is jhibbits@. Perhaps he
can give you a status report.
mcl
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/li
Let's speak with a bit more precision. PowerPC (32-bit), with only a
lingering handful of embedded uses is "dying" and is only marginally
more relevant than the likes of sparc64.
PPC64 with the advent of Power9 is the only real alternative platform
to amd64 in the data center and the only platfor
On Sun, Dec 16, 2018 at 04:35:32PM -0500, Alex McKeever wrote:
> I ran into problems compiling the CDE in FreeBSD 12.0 RC3 (PowerPC)
> on my eMac.
I don't know of anyone else who has tried to run it.
The server-class ports on powerpc64 have been in good shape for several
years. H
en working on bringing powerpc64 ports up to parity for quite
some time. If you are not aware of the effort that myself, and many
others, have been putting in, then you are obviously not reading the
svnports@ list, and should not be speaking as an authority.
src work on supporting P8 and P9
CC the package maintainer.
As for powerpc on tier 1, I'm afraid that it's not likely to ever
happen. Powerpc is dying. If anybody were buying new ppc hardware,
then it would be a different story. But I predict that powerpc is
likely to be dropped than to go Tier 1. Sorry.
-Alan
On Sun, Dec 1
I ran into problems compiling the CDE in FreeBSD 12.0 RC3 (PowerPC) on my eMac.
It says it is broken and cannot be compiled. Also, any ETA on when this port of
the OS will go into Tier 1? Compiling software, desktop environments, X11,
using 11.1 and the now unsupported 10.4 failed when I tried t
do a complete
reinstallation of all ports' and worked perfect.
Thanks for your interest.
Raúl.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-
sion ~6) lots of big changes
on the ports tree have happened. It has more than 800 ports installed so
it's a bit complex setup. I try everything on this box. Maybe I broke
some port dependencies, or I miss something, I'm not sure. Build fails
for me with:
[]
Dumper.c loadable library an
mooth, performant, snappy ...
well rounded.
Before deleting old-libs I tried a 'portmaster -Raf' and there is where
I'm getting into trouble. This installation has survived three server
boxes and in the meantime (since FreeBSD version ~6) lots of big changes
on the ports tree have h
On Monday, May 14 at 05:39:33 CEST, Kevin Oberman wrote:
>
> Kernel modules are NOT guaranteed to work between kernels. It is
> recommended that all kernel modules from ports and lsof be added to
> PORTS_MODULES so they are re-built after each kernel update. Rebuild
> virtualbox-o
just after to complete the
> > upgrade and reboot, the system panics just after to load kernel module
> > vboxdrv.
> >
> > The workaround is rebuild both emulators/virtualbox-ose and
> > emulators/virtualbox-ose-kmod ports from within 11.2-BETA1, and
> > after
Jose
If you have not rebuilt the virtualbox-ose-kmod package from ports with the
11.2-beta1 sources on disk ; please do so . This should resolve this issue .
---
Mark Saad | nones...@longcount.org
> On May 13, 2018, at 3:41 PM, Jose G. Juanino wrote:
>
>> On Sunday, May 13 at 1
d kernel module
> vboxdrv.
>
> The workaround is rebuild both emulators/virtualbox-ose and
> emulators/virtualbox-ose-kmod ports from within 11.2-BETA1, and
> after that everything works nicely as before the upgrade. I hope this
> help other people suffering a similar issue. Best
emulators/virtualbox-ose-kmod ports from within 11.2-BETA1, and
after that everything works nicely as before the upgrade. I hope this
help other people suffering a similar issue. Best regards.
--
José G. Juanino
___
freebsd-stable@freebsd.org mailing
Hi!
> yes
> a lot of "> 10.4 RELEASE" and " current version"
Ah, so you skipped some of the questions during the update.
Well, that takes a bit of work to clean up, but it's no deal breaker.
--
p...@opsec.eu+49 171 3101372 3 years to go !
___
yes
a lot of "> 10.4 RELEASE" and " current version"
Im fighting now trying to install some packages
tks
On Tue, Oct 24, 2017 at 3:24 PM, Kurt Jaeger wrote:
> Hi!
>
> > After second freebsd-update install
>
> Boot single-user and edit /etc/defaults/rc.conf and/or /etc/rc.conf,
> th
Hi!
> After second freebsd-update install
Boot single-user and edit /etc/defaults/rc.conf and/or /etc/rc.conf,
there's some typo somewhere.
--
p...@opsec.eu+49 171 3101372 3 years to go !
___
freebsd-stable@freebsd.
Hi!
> Im with a 9.3 Release now (thanks Kurt)
> but When I try to install a port, same error
>
> root@avvio-fw:/usr/src # cd /usr/ports/net-mgmt/rancid3/
> root@avvio-fw:/usr/ports/net-mgmt/rancid3 # make delete-old-libs
> "/usr/ports/Mk/bsd.port.mk", line 1045:
Im with a 9.3 Release now (thanks Kurt)
but When I try to install a port, same error
root@avvio-fw:/usr/src # cd /usr/ports/net-mgmt/rancid3/
root@avvio-fw:/usr/ports/net-mgmt/rancid3 # make delete-old-libs
"/usr/ports/Mk/bsd.port.mk", line 1045: Unknown directive
Unknown modifier &#x
Ok its worked
Entered in single mode
Make installworld
Mergemaster -UiP
now server is alive in 9.3
Tomorrow I check the ports
On Oct 19, 2017 5:36 PM, "Kurt Jaeger" wrote:
> Hi!
>
> > ok, I will try this, becausa I did everthing, then I reboot, like this
> steps
&
Hi!
> ok, I will try this, becausa I did everthing, then I reboot, like this steps
>
> svn checkout https://svn.freebsd.org/base/release/9.3.0/ .
> make buildworld
> make buildkernel
> make installkernel
> make installworld
>
> mergemaster -UiP
> shutdown -r now
Yes, this works for small upgrad
stems, so
> your first step needs to be a source upgrade.
>
> Please note: Your binaries from 9.1-PRE will work on 9.3, and probably on
> 10.x, so no need to worry about the packages installed for now.
>
> You can rebuild your ports when you're on 10.x.
>
&g
ok, I will try this, becausa I did everthing, then I reboot, like this steps
svn checkout https://svn.freebsd.org/base/release/9.3.0/ .
make buildworld
make buildkernel
make installkernel
make installworld
mergemaster -UiP
shutdown -r now
On Thu, Oct 19, 2017 at 5:02 PM, Kurt Jaeger wrote:
> H
Hi!
> yes I can boot single mode, mount / , etc
Try to boot single user mode with the new kernel, then re-run
make installworld
mergemaster -UiP
The normal way to do it is to reboot after
make installkernel
If you ran the installworld before the reboot, some files might
not be copied.
Anothe
yes I can boot single mode, mount / , etc
Why you think its a kernel problem not some file that I change
in mergemaster questions
because, I boot the serve once and the 9.1-> 9.3 worked
after mergemaster and reboot that happened
On Thu, Oct 19, 2017 at 4:39 PM, Kurt Jaeger wrote:
> Hi!
>
> > I
our first step needs to be a source upgrade.
>
> Please note: Your binaries from 9.1-PRE will work on 9.3, and probably on
> 10.x, so no need to worry about the packages installed for now.
>
> You can rebuild your ports when you're on 10.x.
>
> --
> p...@opsec.eu
Hi!
> I follow the steps (that Kurt sent with his help)
> After the mergemaster -UiP
> the server stop at boot, after this point (see pictures attached)
Can you boot single-mode ?
Can you boot the old kernel ?
--
p...@opsec.eu+49 171 3101372 3 years to go !
d.Fetching public
> > key
> > > from update6.freebsd.org... failed.Fetching public key from
> > > update5.freebsd.org... failed.Fetching public key from
> > > update4.freebsd.org... failed.No mirrors remaining, giving up*
> >
> > Well, freebsd-update onl
ublic key from
> > update5.freebsd.org... failed.Fetching public key from
> > update4.freebsd.org... failed.No mirrors remaining, giving up*
>
> Well, freebsd-update only works on GENERIC kernels and systems, so
> your first step needs to be a source upgrade.
>
> Please no
On 18/10/2017 05:41, Kurt Jaeger wrote:
> Please note: Your binaries from 9.1-PRE will work on 9.3, and probably on
> 10.x, so no need to worry about the packages installed for now.
>
> You can rebuild your ports when you're on 10.x.
>
If you have trouble running anyth
, and probably on
10.x, so no need to worry about the packages installed for now.
You can rebuild your ports when you're on 10.x.
--
p...@opsec.eu+49 171 3101372 3 years to go !
___
freebsd-stable@freebsd.org mailing
> So, what does
>
> uname -a
>
>
>
> *server# uname -aFreeBSD server.avgroup.loc 9.1-PRERELEASE FreeBSD
> 9.1-PRERELEASE #0 r238721: Mon Jul 23 17:34:45 BRT 2012
> r...@server.avgroup.loc:/usr/obj/usr/stable9/sys/AVVIO_FW i386You have new
> mail.*
>
> What does
>
> freebsd-version -ku
>
> *dont ha
Hi!
> Yes, I need help, its exactly what Im trying to do, upgrade
> to a newer version
So, what does
uname -a
say ?
What does
freebsd-version -ku
say ?
Can you try to do these steps to get to a slightly newer version first ?
freebsd-update -r 9.3-RELEASE upgrade
# installation kernel
freeb
Hi Kurt
Yes, I need help, its exactly what Im trying to do, upgrade
to a newer version
tks
On Tue, Oct 17, 2017 at 3:32 PM, Kurt Jaeger wrote:
> Hi!
>
> > I have a 9.1 freebsd server, and every ports I try to install I get
> > the follow error
>
> 9.1 is no longer
> Am 17.10.2017 um 19:29 schrieb Denis Granato :
>
> Hello everyone
>
> I have a 9.1 freebsd server, and every ports I try to install I get
> the follow error
>
>
>
>
>
>
>
> *server# cd /usr/ports/devel/subversionserver# make install
> clean&
Hi!
> I have a 9.1 freebsd server, and every ports I try to install I get
> the follow error
9.1 is no longer supported. Any chance to upgrade ? Do you need
help to upgrade that box ?
--
p...@opsec.eu+49 171 3101372 3 years
Hello everyone
I have a 9.1 freebsd server, and every ports I try to install I get
the follow error
*server# cd /usr/ports/devel/subversionserver# make install
clean"/usr/ports/Mk/bsd.port.mk <http://bsd.port.mk>", line 1045: Unknown
directiveUnknown modifier '
On 10/13/17 15:26, Gary Palmer wrote:
On Fri, Oct 13, 2017 at 12:59:17PM +0200, Werner Griessl wrote:
No answer on ports, next try stable
Werner
Date: Wed, 11 Oct 2017 15:48:51 +0200
From: Werner Griessl
To: freebsd-po...@freebsd.org
Subject: ports index after upgrade 10.4 --> 11.1Sta
On Fri, Oct 13, 2017 at 12:59:17PM +0200, Werner Griessl wrote:
> No answer on ports, next try stable
> Werner
> Date: Wed, 11 Oct 2017 15:48:51 +0200
> From: Werner Griessl
> To: freebsd-po...@freebsd.org
> Subject: ports index after upgrade 10.4 --> 11.1Stable ?
>
>
No answer on ports, next try stable
Werner
--- Begin Message ---
After an Upgrade from 10.3 Stable --> 11.1 Stable, the
/usr/ports/INDEX-11 doesnt build after a "portsnap fetch upgrade"
Have always to do "cd /usr/ports; make index" after a portsnap.
What is wrong w
On Wed, Oct 4, 2017 at 6:03 AM, Gerhard Schmidt wrote:
> Hi,
>
> I've got a new Workstation last week with the Main HD as M2 Card.
>
> FreeBSD recognizes the card as nvd0
> nvd0: NVMe namespace
> nvd0: 488386MB (1000215216 512 byte sectors)
>
> When compi
Hi,
I've got a new Workstation last week with the Main HD as M2 Card.
FreeBSD recognizes the card as nvd0
nvd0: NVMe namespace
nvd0: 488386MB (1000215216 512 byte sectors)
When compiling some ports (in this example VirtualBox-ose) I
experiencing lockups on the Harddisk when many file
ackages go
>>>>> (rather than
>>>>> # going locally to each port).
>>>>> # Default: ${PORTSDIR}/packages
>>>>>
>>>>> Since r438901 (
>>>>> https://svnweb.freebsd.o
;> # Default: ${PORTSDIR}/packages
>>>>
>>>> Since r438901 (
>>>> https://svnweb.freebsd.org/ports?view=revision&sortby=date&revision=438901
>>>>
>>>> )
>>> Actually, r438058 broke PACKAGES. For the
>>> old. I have a question, not sure if you know, but I will toss it out.
>>> As I mentioned I update using svn for both src and ports, and I am curious
>>> to know if I can actually bring my src tree up to the most current 10.x
>>> stable, recompile
. As
>> I mentioned I update using svn for both src and ports, and I am curious to
>> know if I can actually bring my src tree up to the most current 10.x stable,
>> recompile, and install and have it all run?
So here is my take on the update . For starters if you are using a sto
On Sat, Jun 3, 2017 at 12:19 PM, Howard Leadmon wrote:
>Thanks for the update, I had the feeling the issue was from it being to
> old. I have a question, not sure if you know, but I will toss it out.
> As I mentioned I update using svn for both src and ports, and I am curious
>
Thanks for the update, I had the feeling the issue was from it being
to old. I have a question, not sure if you know, but I will toss it
out. As I mentioned I update using svn for both src and ports, and I
am curious to know if I can actually bring my src tree up to the most
current 10
Howard
There are 3 options . One upgrade to 10.x or 11.x and ports/pkg will work .
Support for the 9 series and 10.1 and 10.2 was removed from ports a few months
ago . Two check out ports via svn and use the tag RELEASE_9_EOL and use that as
your starting point . This is ports before the
I know 9.3 is kinda dated, but it had been running fine so I left the
servers alone as they were in a remote location many hours away.
That said, if I try and do anything with ports (I keep everything
updated using SVN), I get the following error:
"/usr/ports/Mk/bsd.port.mk",
AGES - A top level directory where all packages go
>>> (rather than
>>> # going locally to each port).
>>> # Default: ${PORTSDIR}/packages
>>>
>>> Since r438901 (
>>> http
y to each port).
# Default: ${PORTSDIR}/packages
Since r438901 (
https://svnweb.freebsd.org/ports?view=revision&sortby=date&revision=438901
)
Actually, r438058 broke PACKAGES. For the records, see
https://bugs.freebsd.org/bugzilla/show_
locally to each port).
> # Default: ${PORTSDIR}/packages
>
> Since r438901 (
> https://svnweb.freebsd.org/ports?view=revision&sortby=date&revision=438901
> )
Actually, r438058 broke PACKAGES. For the records, see
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218827
___
Mk&bsd.ports.mk still tells:
# PACKAGES - A top level directory where all packages go
(rather than
# going locally to each port).
# Default: ${PORTSDIR}/packages
Since r438901 (
https://svnweb.freebsd.org/ports?
Oh, and WITH_SVN= in src.conf installs svnlite as svn.
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/SVN-UPDATE-not-respected-by-usr-ports-Makefile-tp6164511p6169002.html
Sent from the freebsd-stable mailing list archive at Nabble.com
1 - 100 of 864 matches
Mail list logo
