Michelle
Just 2c.
On Fri, Feb 09, 2018 at 11:52:16AM +1100, Michelle Sullivan wrote:
LuKreme wrote:
On Feb 7, 2018, at 20:06, Michelle Sullivan wrote:
Just saying telling people not to call the product the same as the trademark if
there are any changes to the product is the way to p
LuKreme wrote:
On Feb 7, 2018, at 20:06, Michelle Sullivan wrote:
Just saying telling people not to call the product the same as the trademark if
there are any changes to the product is the way to protect the trademark.
But is there a trademark? It seems not from an earlier post.
Don't
Dave Horsfall wrote:
On Thu, 8 Feb 2018, Michelle Sullivan wrote:
The reaction to the repo in question is also very weird to me, and
possibly what worries me the most. He is hurting his own trademarked
(heh) product by doing this.
Quite the opposite. He has done the right thing to protect
very weird to me, and possibly
what worries me the most. He is hurting his own trademarked (heh) product
by doing this.
Quite the opposite. He has done the right thing to protect his trademark.
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-
Lars Engels wrote:
On Mon, Dec 11, 2017 at 09:09:39AM +1100, Dave Horsfall wrote:
On Sun, 10 Dec 2017, Adam Weinberger wrote:
DMA is a phenomenal program and is totally sufficient for a large
percentage of our user-base. I wasn’t aware of the lack of .forward
support, and I completely agree th
Chris H wrote:
P.S. Please try to keep it civil.
Ok..
.
Michelle
:)
___
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"
Steven Hartland wrote:
On Mon, 4 Dec 2017 at 03:02, Michelle Sullivan wrote:
You mean if you're not into security or part of a security company stay
on quarterly, but if you need to keep patched up because you are in the
top 100 of most attacked sites/companies in the world, deploy a te
Baho Utot wrote:
On 12/3/2017 5:04 PM, Carmel NY wrote:
I just checked out <
https://github.com/jrmarino/Ravenports/wiki/quickstart-freebsd>
and < http://ravenports.ironwolf.systems/> and I have to admit that I
am interested.
I am wondering if it will ever get accepted into the ports system.
Adam Weinberger wrote:
On 3 Dec, 2017, at 14:31, Michelle Sullivan wrote:
Adam Weinberger wrote:
You seem very angry about things breaking in HEAD, Baho. Things break in HEAD
sometimes. This is why we recommend that end-users who can't have breakages, or
users who depend on undeve
Adam Weinberger wrote:
You seem very angry about things breaking in HEAD, Baho. Things break in HEAD
sometimes. This is why we recommend that end-users who can't have breakages, or
users who depend on undeveloped tools, stay on the quarterly branch. Portmaster
works perfectly on quarterly. Al
Martin Waschbüsch wrote:
Am 23.06.2017 um 23:53 schrieb Michelle Sullivan :
Matt Smith wrote:
I use FreeBSD *precisely* because it mostly keeps up with the latest stable
versions of things. I have postfix 3.2, pgsql 9.6, nginx 1.13, libressl 2.5
etc. It's usually impossible to do this
at the millions per day, and serving DNS
requests at a rate of over 70,000 queries per second (averaged over a
week)... you can't just f**k with that. Patches have to be evaluated,
tested, built and regression tested
--
Michelle Sullivan
o it our
way... pay us to do it your way or do it yourself" vs the users, that
are shouting, "come on guys we can't keep up, we need stability, we're
not using this as a desktop here"
And both sides are diametrically opposed and steadfast
ait - that's exactly what I did
as well... you get the idea.. don't argue for it, just do it yourself
its a lot less of a waste of energy and you get exactly what you want/need.
Regards,
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-
server side of things as I use OSX as my desktop
which funnily enough is using guess what... a BSD Kernel!.,,
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsu
D one... and with stuff fixed
that was just marked BROKEN on FreeBSD 9.x... Of course thats for my
package/patch set so YMMV and there are a lot that are not upgraded to
the current FreeBSD set - but then it's only me on it.
Michelle
--
Michelle Sullivan
http://ww
Mark Linimon wrote:
On Sat, Feb 11, 2017 at 09:51:41AM +0100, Michelle Sullivan wrote:
Tell me What is the reason for me upgrading those few production
servers from 9.3 to 10/11?... bearing in mind the following:
There isn't any ... oh, except for no new security updates.
But that&
Mark Linimon wrote:
On Fri, Feb 10, 2017 at 11:02:41PM +0100, Michelle Sullivan wrote:
Or the last strong hold you have - the server owners - get so p**sed off in
reality they can't keep up with the OS updates that they migrate away...
So we should give up on EFI, 4k drives, and SSD?
s - get so p**sed off
in reality they can't keep up with the OS updates that they migrate away...
FreeBSD seems to have entered (trying to enter) the desktop market...
good luck competing with Apple and Microsoft... I guess FreeBSD will be
the next Solaris.
--
Michell
Dave Horsfall wrote:
(Many responses)
I note that no-one has answered the question which caused me to post the
message in the first place viz: why weren't the files being removed
automatically? Everyone appears to have missed this point...
I didn't and some of the answers are helpful even if n
Julian Elischer wrote:
So this seems to be a speciality of mine.
I often find that I need a ports tree at rev X except for some port
foo/bar that needs to be at some different rev (Y) to pick up a
fix/change needed by the application. Now there is no reason that I
can't just edit the distin
Matthieu Volat wrote:
On Thu, 15 Dec 2016 19:31:22 +0100
list-freebsd-po...@jyborn.se wrote:
On Thu, Dec 15, 2016 at 01:18:05PM -0500, George Mitchell wrote:
On 12/15/16 09:40, Warren Block wrote:
On Thu, 8 Dec 2016, Matt Smith wrote:
On Dec 08 05:16, Daniil Berendeev wrote:
Although portm
Vlad K. wrote:
The quarterly branch (Q) is intended to provide a set of "stable"
packages that in the lifetime of such a branch, receive only bug and
security fixes. That is the theory and intent behind the branch. In
practice, however:
1. The Q branch is cut off at predetermined dates (ie. n
Torfinn Ingolfsen wrote:
This one can easily be compiled:
tingo@kg-core1$ mkdir focal
tingo@kg-core1$ cd focal
tingo@kg-core1$ fetch ftp://www.cozx.com/pub/langs/focal.tar.gz
focal.tar.gz 100% of 42 kB 116 kBps 00m00s
untar, then
tingo@kg-core1$ cd focal-1.0.
Julian Elischer wrote:
Some friends and I have a pdp8 here.. we replaed the bulbs with leds
about 25 years ago, but
last time we tried it, it still ran.. model number escapes me.. its
currently at a friend's place.
It was the controller for a DISTEC (?) display, the predecessor for
the wonderf
t BROKEN on OSVERSION > X with that option?
___
I would suggest that is the correct way to do it.
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.
Kevin Oberman wrote:
On Mon, Jul 11, 2016 at 1:10 PM, Michelle Sullivan <mailto:miche...@sorbs.net>> wrote:
Wojciech Puchar wrote:
Interesting question. Perl was removed from the base
system years ago
with no ill affects.
Wojciech Puchar wrote:
Interesting question. Perl was removed from the base system years ago
with no ill affects.
ssh ...?
Do ssh use ssl protocol?
Actually I don't know, just takign a wild stab in the dark.. certainly
fetch etc as others have already pointed out.
Michelle
--
Mic
))
--
Michelle Sullivan
http://www.mhix.org/
___
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"
andards, and we recommend ALL
users who are still on FreeBSD 9.x to use port version of OpenSSL.
Did that a long time ago when I realised how FreeBSD actually supports
the people using it instead of the developers.. not that it worries me
now, shortly I won't have any FreeBSD hosts.
--
Mi
e certain some will
just deploy and get nailed... remote access only via SSH and no SU on
non console etc..)
And I am not sure that this is a problem of poudriere. I think it's
rather issue in ports options framework. Isn't it?
Correct (but also poudriere wouln't get the cha
Mathieu Arnold wrote:
+--On 29 juin 2016 13:15:44 +0200 Michelle Sullivan
wrote:
| Baptiste Daroussin wrote:
|> On Tue, Jun 28, 2016 at 11:15:56PM +0200, Matthias Andree wrote:
|>>
|>> And I do think we should, opposite to what you are proposing, make the
|>> committer spen
ndom list of what you think is important is a short sighted
and unprofessional methodology as it creates more uncertainty and
confusion..
My opinion, feel free to ignore as usual.
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@
le for the port.. so someone goes makes blanket
changes which actually breaks stuff.. that reflects on the person in the
Maintainer line - whether you want it to do so or not, whether you
believe it or not..
Regards,
--
Michelle Sullivan
http://www.mhix.org/
___
Would be good but don't see it happening.
--
Michelle Sullivan
http://www.mhix.org/
___
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"
nding upon the number of ports you actually need to work
with. This approach may be worth it. A determination, only *you*
can decide. :)
More than one person has done this already (myself included)
Michelle
--
Michelle Sullivan
http://www.mhi
x27;m now a bit confused.
I will re-run the single port in my poudriere oven, as well with DOCS
disabled, and report back.
matthias
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
https://lists.free
s.stat(filename).st_mtime
OSError: [Errno 2] No such file or directory:
'/wrkdirs/usr/ports/devel/llvm37/work/llvm-3.7.1.src/tools/clang/docs/ReleaseNotes.rst'
The full traceback has been saved in /tmp/sphinx-err-1UMMZi.log, if you want to
report the issue to the developers.
Please also report this if it was a user error, so that a better error message
can be provided next time.
A bug report can be filed in the tracker at
<https://github.com/sphinx-doc/sphinx/issues>. Thanks!
ninja: build stopped: subcommand failed.
*** Error code 1
Stop.
make: stopped in /usr/ports/devel/llvm37
[1;33m>>[0;0m [1;33mWarning: Leftover processes:
[0;0mUSER PID %CPU %MEM VSZ RSS TT STAT STARTEDTIME COMMAND
build of devel/llvm37 ended at Mon May 2 22:27:28 CEST 2016
build time: 24:19:52
!!! build failure encountered !!!
--
Michelle Sullivan
http://www.mhix.org/
___
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"
Don Lewis wrote:
On 28 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
I'd thought that poudriere was using the host copy of pkg to do the
final part of the respository build, but since poudriere doesn't list
pkg as a dependency, that appears not to be the case. It looks like
po
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Rick Miller wrote:
On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
wrote:
Kevin Oberman wrote
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Rick Miller wrote:
On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
wrote:
Kevin Oberman wrote:
On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Rick Miller wrote:
On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
wrote:
Kevin Oberman wrote:
On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
wrote:
After a portsnap
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Don Lewis wrote:
On 27 Apr, Rick Miller wrote:
On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
wrote:
Kevin Oberman wrote:
On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
wrote:
After a portsnap update it seems all my jails
Don Lewis wrote:
On 27 Apr, Michelle Sullivan wrote:
Rick Miller wrote:
On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
wrote:
Kevin Oberman wrote:
On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
wrote:
After a portsnap update it seems all my jails won't build the current
Don Lewis wrote:
On 27 Apr, Rick Miller wrote:
On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
wrote:
Kevin Oberman wrote:
On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
wrote:
After a portsnap update it seems all my jails won't build the current tree
returning the foll
Rick Miller wrote:
On Wed, Apr 27, 2016 at 12:53 PM, Michelle Sullivan
wrote:
Kevin Oberman wrote:
On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
wrote:
After a portsnap update it seems all my jails won't build the current tree
returning the following error:
>> MOVE
Kevin Oberman wrote:
On Wed, Apr 27, 2016 at 8:06 AM, Michelle Sullivan
wrote:
After a portsnap update it seems all my jails won't build the current tree
returning the following error:
>> MOVED: sysutils/puppet renamed to sysutils/puppet38
>> MOVED: textproc/rubygem-
usr/local/bin/ccache' not found.
>> Computing deps for databases/memcached
>> Error: Invalid port origin '/usr/local/bin/automake-1.15' not found.
>> Umounting file systems
Checked updating but don't see anything to suggest that port origins of
'/usr/local/bin/ccache' are normal..
Regards,
--
Michelle Sullivan
http://www.mhix.org/
___
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"
spam
list?
No comment :P
--
Michelle Sullivan
http://www.mhix.org/
___
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"
kage' otherwise, freebsd-update to the
latest and then update the ports or erase and start again... Sorry for
your pain.
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listi
ion is mandated), and do not
compile against OpenSSL 1.1.x. Most can no doubt be patched, but
waiting for upstream providers to do so may be problematic, and many
porters lack the skills.
Personally I'm surprised there is not more than one major version of
openssl in the ports tree alre
laced by something you have chosen to configure... that
said.. you have the same problem even if you have USE_OPENSSL_PORTS
defined anyhow...)
There are grey areas, and I guess it will be like that for 9.x.
--
Michelle Sullivan
http://www.mhix.org/
_
looks a *lot* better now. Would
be interested as to an explanation of why the distinction between the
two... especially as the port is 'broken' if you try and compile it
against the wrong version of SSL... Mathieu?
--
Michelle Sullivan
http://ww
y impossible until someone changes compile options.)
--
Michelle Sullivan
http://www.mhix.org/
___
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"
dependency/library issues that could happen.
Regards,
--
Michelle Sullivan
http://www.mhix.org/
___
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"
uild ? Should the
default for 9.3 probably be something else like gnutls or polarssl ?
OPENSSL from Ports is newer and will compile on 9.3amd64... the base
OpenSSL is too old and 9.3 is legacy... according to re@
--
Michelle Sullivan
http://www.mhix.org/
__
en in the ports
tree for 9.x ... basically for many things now the ports tree is
unusable and quarterlies are unusable because they contain known
security issues in most cases which will never be backported "Because
its too hard".. According to the same email thread the answer to th
ipts to create the portsnap files which I currently
publish on a publicly accessible server so my own servers can get it.
So if you have the time and/or desire/or need, you can create your own
portsnap distributable tree with your own version of ports.
Regards,
--
don't
> know about that.
>
> HTH,
>
> AvW
>
>
You know you can all run your own portsnap server to allow you to
include local changes?
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
ht
Jim Ohlstein wrote:
> Hello,
>
> On 2/15/16 3:40 PM, Michelle Sullivan wrote:
>> John Marino wrote:
>>> On 2/15/2016 6:32 PM, Roger Marquis wrote:
>>>
>>>>> This makes no sense. Ports are not tied to base releases.
>>>>>
John Marino wrote:
> On 2/15/2016 9:40 PM, Michelle Sullivan wrote:
>
>> Yeah, I'd agree with this... except...
>>
>> pkg_* tools don't exist on 10.x only pkgng... that makes it base os
>> thing.. even if it's downloaded in/via ports..
>>
7;d agree with this... except...
pkg_* tools don't exist on 10.x only pkgng... that makes it base os
thing.. even if it's downloaded in/via ports..
So sorry don't claim it's only part of the ports system, because whilst
it maybe built and administered there, the tools it
rowing of so many of us under the bus was by far the
>> worst.
>>
>
> And now the fully circle. This is FreeBSD's Godwin's law. You know the
> discussion is over when somebody says that "[issue] of the day" is the
> root cause of BSD being eclip
Steven Hartland wrote:
> On 14/02/2016 11:25, Michelle Sullivan wrote:
>> Kevin Oberman wrote:
>>> My experience is that pkg(8) has been wonderfully robust since 1.3.
>>> before
>>> 1.3 it was a real pain in the neck, though I never had a need to
>>>
lt to pkg for a bit. Much as I like it, it
> really was not ready for prime time when it became the default. The early
> issues chased too many people away. E.g. you.
>
Nailed it!
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@
nths) in the "you're going to use this now
whether you like it or not and whether it works or not phase".. since
then I've made the ports system work with pkg_tools again so no longer
have anything to do with pkg. Its a good stop-gap until I can get the
build environment i
go with BerkeleyDB .. oh wait, nevermind... how
about going the whole hog and putting in a registry...that'll work,
somewhere to store those pesky DWORDs so you could move rc.conf there as
well... oh and the registry of installed ports there as well...
No further comment necessary.
--
/usr/ports/UPDATING. This is another sign that something
> is deeply wrong. Any software management solution that does not kill
> /usr/ports/UPDATING forever is insufficient.
>
Personally I think the system should be usable without /usr/ports at
all which funnily enough is (was
least create a project to analyze the ports system "Maintainer
> email address" to see just what would be involved in populating it
> with a dummy value so every place it is viewable to the public the
> real content is masked, this includes the down loadable ports tree.
>
I&#x
so I can
> see how to use the options framework in this case?
>
> Thanks in advance.
>
> AvW
>
>
Do that in your processing of options (if defined etc). It's your
choice whether to force a default or to error out of the build if
options are no
uld think everything would build as well, but that isn't the case
either.
IIRC the point is it stops the targets and dependencies being a moving
target and you can standardise across all your machines the same
non-buildable ports.
--
Michelle Sullivan
http://www.mhix.org/
makefile-naming.html
-> It is expected that PORTEPOCH will not be used for the majority of
ports, and that sensible use of PORTVERSION can often preempt it
becoming necessary if a future release of the software changes the
version structure.
Regards,
--
Michelle Sullivan
http://www.mhix.org/
_
the one with a list of ports
that should be updated along with it, and mark it 'affects many'...
hopefully someone will take the time to pick it up and fix it.
Regards,
Michelle
>
> Regards,
>
> ---
> José Pérez
>
> El 2015-10-04 12:56, Michelle Sullivan escribió:
&g
Michelle Sullivan wrote:
> José Pérez wrote:
>
>> Hi Michelle,
>> thank you for your suggestion. Is this another workaround?
>>
>
> As far as I was aware if you need Uses/compiler.mk it should be
> specified (there are params if a particular compiler/fea
manager take care of
it as it's probably a change in default behavior that has caused the
mess... how many are we talking about? 10+, 100+, 1000+?
Regards,
Michelle
>
> Thank you.
>
> Regards,
>
>
> ---
> José Pérez
>
> El 2015-10-02 02:29, Michelle Sullivan es
ut this
> is just an ugly hack.
>
> Can some expert trow a little light on this? Thank you.
>
> Regards,
>
Try adding:
USES+= compiler
to the makefile first...
(and it still has some issues but that should solve the first)
--
Michelle Sullivan
http://www.mhix.org/
. The usage difference
is the one with the ECC is the 'backup' (a rsync'd mirror of the first)
... now off to get ready, wish me luck and I'll deal with all of this
when back from honeymoon. ;-)
Michelle
--
Michelle Sullivan
http://www.mhix.org/
___
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"
y and I just wanted to get the mail done so I
could forget about it.
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to &quo
t rc scripts should not fail if it is undefined.
+1 to that.
--
Michelle Sullivan
http://www.mhix.org/
___
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"
a bet as it's running as a user the process is being called to
shutdown and there is some permissions issue on the PID file (I see the
same thing with bucardo when running bucardo as non root)
Regards,
Michelle
--
Michelle Sullivan
http://www.mhix.org/
___
ill be added at the end of May when
>>> released, and switched to at the beginning of September.
>> mod_perl is still broken with 5.22. Which is very sad. So maybe
>> it's premature to switch the default ?
>>
>
>
--
Michelle Sullivan
http://www.
ill be added at the end of May when
>>> released, and switched to at the beginning of September.
>> mod_perl is still broken with 5.22. Which is very sad. So maybe
>> it's premature to switch the default ?
>>
>
>
--
Michelle Sullivan
http://www.m
irst is the correct way to do it, and the
second is legacy that may not have any effect now.
DEFAULT_VERSIONS+=apache=2.4 perl5=5.16 pgsql=9.4
PERL5_DEFAULT=5.16
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
https://
r did I misread the intent?
[michelle@colossus /usr/home/michelle]$ grep LATEST_LINK
/usr/ports/databases/pgpool-II-33/*
[michelle@colossus /usr/home/michelle]$ grep PKGNAMESUFFIX
/usr/ports/databases/pgpool-II-33/*
/usr/ports/databases/pgpool-II-33/Makefile:PKGNAMESUFFIX=33
--
Michell
d the existing 9.0 (using
pkg_delete ) and installed 9.4 normally using '( cd
/usr/ports/databases/postgresql94-server && make install )'
and now I can use pkg_upgrade ...
My failing point is ip4r 1.x -> 2.x but that's a completely separate
issue in many ways... (and has it's own solutions).
Regards,
--
Michelle Sullivan
http://www.mhix.org/
___
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"
stall? (or is that only what it displays and it doesn't
actually do it?)
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ient connecting to the new server
and the new client connecting to the old server. They are rare and only
usually affect the use of 'short cut' commands (ie things like: \d and
\dt in the client)... the connection itself is usually both backwards
and forwards compatible.... just not the
Baptiste Daroussin wrote:
> On Tue, Jul 21, 2015 at 01:15:27PM +0200, Michelle Sullivan wrote:
>
>> Michelle Sullivan wrote:
>>
>>> That is where your proposal will not work for us that have massive
>>> production infrastructure...without m
Michelle Sullivan wrote:
>
> That is where your proposal will not work for us that have massive
> production infrastructure...without modification... sounds very debianish.
>
> Here's my thought which follows yours mostly (maybe the same, but not
> the way I read yours.)
>
packages themselves are not dependent on one
another (hypothetical example: if DBD::Pg won't link against 9.4 and
postgresql 9.4 is needed for python, both could be installed at the same
time... a more real example (from my servers) not all that long ago,
slony wouldn't link against
Mathieu Arnold wrote:
> +--On 19 juillet 2015 23:20:11 +0200 Michelle Sullivan
> wrote:
> |> No, he's either fixing that was broken,
> |
> | So you're saying anything that is deemed broken can be changed/fixed
> | without the maintainer's comment or appro
Mathieu Arnold wrote:
> +--On 19 juillet 2015 22:30:45 +0200 Michelle Sullivan
> wrote:
> |> In fact what I am working on is enforcing openssl (or libressl at user
> |> choice) from ports directly (which is why I worked on the ports in the
> |> first place - after someon
Mathieu Arnold wrote:
> +--On 19 juillet 2015 14:02:53 +0200 Michelle Sullivan
> wrote:
> | please correct me if I'm wrong but isn't self committing (those with the
> | commit bit committing their own patches without QA/review/adding
> | patchfiles to the PR) against the
Baptiste Daroussin wrote:
> On Sun, Jul 19, 2015 at 06:44:26PM +0200, Michelle Sullivan wrote:
>
>> Baptiste Daroussin wrote:
>>
>>> On Sun, Jul 19, 2015 at 05:19:08PM +0200, Michelle Sullivan wrote:
>>>
>>>
>>>> Dimitry A
Baptiste Daroussin wrote:
> On Sun, Jul 19, 2015 at 05:19:08PM +0200, Michelle Sullivan wrote:
>
>> Dimitry Andric wrote:
>>
>>> On 19 Jul 2015, at 14:02, Michelle Sullivan wrote:
>>>
>>>
>>>> please correct me if I'
Dimitry Andric wrote:
> On 19 Jul 2015, at 14:02, Michelle Sullivan wrote:
>
>> please correct me if I'm wrong but isn't self committing (those with the
>> commit bit committing their own patches without QA/review/adding
>> patchfiles to the PR) against the
please correct me if I'm wrong but isn't self committing (those with the
commit bit committing their own patches without QA/review/adding
patchfiles to the PR) against the rules?... or is it just a free-for-all
now?
Michelle
--
Michelle Sullivan
http://ww
Michelle Sullivan wrote:
>
>>
>>
>>
> You need "CATEGORIES += myports" (or something similar) as well...
>
> Michelle
>
>
Sorry I'm talking out of my butt
you can add a "local" top level add add it with "CATEGORIES +
ned and there isn't much
> useable documentation or prior art for how to do it 'by hand'.
>
> Cheers,
>
> Matthew
>
>
You need "CATEGORIES += myports" (or something similar) as well...
Michelle
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Matthew Donovan wrote:
> You might want to look at
> http://svnweb.freebsd.org/base/user/cperciva/portsnap-build/ might help you
> with portsnap.
>
Fantastic! Exactly what I need.
--
Michelle Sullivan
http://www.mhix.org/
___
f
1 - 100 of 218 matches
Mail list logo
