# cd /usr/src
> # patch -p2 < ~/A.patch
> # patch -p2 < ~/B.patch
> 3. Save your existing kernel for future updates (security patches or 10.2)
> # cp /boot/kernel/kernel /boot/GENERIC
> 4. Rebuild the kernel
> # make buildkernel (If you have multiple core
st what was being built at
>> the time you did Ctrl-C. If you run poudriere bulk again, it will continue
>> the build.
>>
>
> Is this also true if a port is not yet finished, or only for created
> packages?
>
Only those that have been completed.
--
Michelle Sullivan
; USE_PACKAGE_DEPENDS_ONLY set - not building missing dependency
from source
*** [build-depends] Error code 1
Stop in /usr/ports/net/unison.
===> Cleaning for unison-2.48.3_1
build of /usr/ports/net/unison ended at Sat Mar 21 12:32:36 CET 2015
-BUILD_DEPENDS+=ocamlc:${PORTSDIR}/lang/
Guido Falsi wrote:
> On 03/21/15 11:49, Michelle Sullivan wrote:
>
>> Jeremie Le Hen wrote:
>>
>>> Actually, I've just realized that I fixed net/unison232 in my local tree
>>> :o).
>>>
>>> Would you mind submitting it and
Guido Falsi wrote:
> On 03/21/15 13:26, Michelle Sullivan wrote:
>
>> Guido Falsi wrote:
>>
>>> On 03/21/15 11:49, Michelle Sullivan wrote:
>>>
>>>
>>>> Jeremie Le Hen wrote:
>>>>
>>>>
d reject the config or override one (though then do
you override nox11 or with x11.)
Anyhow... enough of my comments, looks like you're on top of it and
others in this thread are being a lot more helpful that I ever will be.
Regards,
--
Michelle Sullivan
http://www.mhix.org/
_
A.J. "Fonz" van Werven wrote:
> Mark Linimon wrote:
>
>
>> to waste either your time, or valuable electrons.
>>
>
> Come now, electrons are overrated.
There's a lot of negativity over electrons here...
e would be stupid to ocaml-nox11 + unison (which a conflict of
ocaml-nox11* should solve) and therefore just test for ocaml is
installed by filesystem test and not via pkg test when building without
X11 which would seem to be the solution to all of the above
unless I'm missing something.
Guido Falsi wrote:
> On 03/26/15 12:59, Michelle Sullivan wrote:
>
>> Guido Falsi wrote:
>>
>>> On 03/26/15 03:21, Geoffrey Mainland wrote:
>>>
>>>
>>>> On Sat, Mar 21, 2015 at 07:02:47PM +0100, Guido Falsi wrote:
>>
Got your message via the webform, tried to reply and got:
This report relates to a message you sent with the following header fields:
Message-id: <553a7998.2090...@sorbs.net>
Date: Fri, 24 Apr 2015 19:12:56 +0200
From: Michelle Sullivan
To: portmas...@bsdforge.com
Subje
s to be no fix for 0.9.8
which 8.4 and 9.3 has 0.9.8zd in base - i expect 8.4 to get ignored as
it EoLs on Jun 30, 2015, but 9.3 EoLs on Dec 31, 2016)
Michelle
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
ht
Andrea Venturoli wrote:
> On 06/12/15 01:34, Michelle Sullivan wrote:
>> Roger Marquis wrote:
>>> The ports-secteam knows about this but posting here in case someone
>>> wants to
>>> update ahead of the port, from this morning's Hackernews:
>>>
&
s
> in the thread that I started, someone mentioned that it could be a
> problem if a port uses libfetch because that shared library is linked to
> openssl from base, but none of the ports that I use appear to use
> libfetch.
>
SSH would
Don Lewis wrote:
> On 13 Jun, Michelle Sullivan wrote:
>
>
>> SSH would be the biggie that most security departments are scared of...
>>
>
> Well, ssh is available in ports, though I haven't checked to see that it
> picks up the correct version of ope
Matt Smith wrote:
> On Jun 13 13:13, Michelle Sullivan wrote:
>> Don Lewis wrote:
>>> On 13 Jun, Michelle Sullivan wrote:
>>>
>>>
>>>> SSH would be the biggie that most security departments are scared
>>>> of...
>>>>
>>&
ne remember.
Regards,
Michelle
PS: There is a workaround for ssh clients in /etc/ssh/ssh_config to stop
it falling back to "insecure" protocols - though every freebsd-update
attempts to change this file back to the default... fortunately I have
puppet to reset
Carmel NY wrote:
> On Sat, 13 Jun 2015 14:48:04 +0200, Michelle Sullivan stated:
>
>
>> Carmel NY wrote:
>>
>>> On Sat, 13 Jun 2015 12:36:44 +0100, Matt Smith stated:
>>>
>>>
>>>> The other alternatives are as you say, put
up my own freebsd-update server - if only there were docs
about how to do it... I'd have done it a couple of months ago, Google
didn't reveal anything to me when I looked though...
Michelle
--
Michelle Sullivan
http://www.mhix.org/
___
freebs
Miroslav Lachman wrote:
> Michelle Sullivan wrote on 06/13/2015 14:29:
>
> [...]
>
>> 57 servers around the world that I have to maintain, patch and upgrade
>> at the same time as devel and maintain my applications... yeah I don't
>> do source stuff ;-)
>>
Eitan Adler wrote:
> On 13 June 2015 at 15:48, Michelle Sullivan wrote:
>
>
>> I'd love to setup my own freebsd-update server - if only there were docs
>> about how to do it... I'd have done it a couple of months ago, Google
>> didn't
Matthew Seaman wrote:
> On 13/06/2015 19:41, Michelle Sullivan wrote:
>
>> How about one for how to make your own portsnap ? :P
>>
>
> Presumably you're wanting to re-distribute local modifications to the
> ports tree sources around your machines?
>
>
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
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"
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 +
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
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
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'
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
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
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 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
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
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.)
>
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
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
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"
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"
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
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://
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
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.
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/
___
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"
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
. 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"
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/
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
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
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
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/
_
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/
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
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
/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
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.
--
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
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@
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
>>>
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
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
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..
>>
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.
>>>>>
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
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,
--
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
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/
__
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"
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"
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
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/
_
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
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
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"
? one
assumes some of the skipped are needed to build or run something else...
but that's not skipped, and it builds...
Pointers would be nice...
Michelle
Michelle Sullivan wrote:
> Seems every week or two my build servers all fail and it's mostly one of
> 2 packages
>
ook patches sent to the ports I maintain.
>>
>
> Its on the list of things we want to get done ASAP. The requirements
> are simple but someone that knows perl needs to volunteer to help :)
>
>
>
You've got me - but I'm busy for a couple of days due to the da
bases/pgpool-II-33.
>
> Please test and approve.
>
> Second step: merging the diverse set of pgpool related ports into one ?
>
>
Maybe pg-pool-II and pg-pool-devel...? (3.1/2 in stable and 3.3 in
devel - until it changes?)
Michelle
--
Michelle Sullivan
http://www.mhix.org/
keep the last version of pgpool-I ... but move it to
pgpool-I (or pgpool-v2) and mark it as 'no further developement' (as I
think that's true)
> I don't think there's any particular reason to have ports of all the
> different pgpool-II branches in tree, BICBW. If the
Matthew Seaman wrote:
> On 15/06/2014 22:49, Michelle Sullivan wrote:
>
>> Personally I think:
>>
>> databases/pgpool (3.1.x)
>> databases/pgpool-devel (3.3.x)
>>
>>>> Given the lack of history in the ports, I'd say lets just skip
>
mething like
> OPTIONS_SLAVE_DEFAULT, which will work as OPTIONS_SLAVE if here is no
> ${OPTIONS_FILE} and could be overridden by ${OPTIONS_FILE}, if it is
> present.
>
>
Have a look at editors/pico-alpine and mail/alpine that does exactly
what you're asking I think.
Michelle
t;>> present.
>>>
>>>
>>>
> MS> Have a look at editors/pico-alpine and mail/alpine that does exactly
> MS> what you're asking I think.
> Nope. "make config" in "editoris/pico-alpine" shows di
/bmon-devel - straight from github info here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191249
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
Melvyn Sopacua wrote:
> Hi Michelle,
>
> On Sat, 21 Jun 2014, Michelle Sullivan wrote:
>
>> Don't know if maintainer of bmon is around as port is unstaged and 2.x
>> (and the distfiles don't seem to exist in the master site) so submitted
>> new port for ne
Kubilay Kocak wrote:
> On 22/06/2014 7:48 PM, Michelle Sullivan wrote:
>
>> Melvyn Sopacua wrote:
>>
>>> Hi Michelle,
>>>
>>> On Sat, 21 Jun 2014, Michelle Sullivan wrote:
>>>
>>>
>>>> Don't know if
Michelle Sullivan wrote:
> Kubilay Kocak wrote:
>
>> On 22/06/2014 7:48 PM, Michelle Sullivan wrote:
>>
>>
>>> Melvyn Sopacua wrote:
>>>
>>>
>>>> Hi Michelle,
>>>>
>>>> On Sat, 2
ined.
>
> What version of /usr/ports do you use ?
>
>
I had a load of problems with the same dependency... for me the solution
was to run poudriere with -c on all packages (it wasn't getting rebuild)
... then eventually I worked out what depended on it and disabled the
option
h in any negative way as MySQL is case insensitive for table
names - unlike PostgreSQL and others.)
Best regards,
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/free
Maintainer nudge (timeout?)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190104
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any
First,
Thanks Matthew and Dimitry, and indeed Jesse is still listed as the
maintainer - however I have had no reply from him over the last few
weeks, I could be wrong but I think he no longer works for Best Practical.
Matthew Seaman wrote:
> On 03/07/2014 03:52, Michelle Sullivan wr
Michelle Sullivan wrote:
> First,
>
> Thanks Matthew and Dimitry, and indeed Jesse is still listed as the
> maintainer - however I have had no reply from him over the last few
> weeks, I could be wrong but I think he no longer works for Best Practical.
>
> Matthew Seaman wr
Dmitry Sivachenko wrote:
>
>
> Did you file an issue for RT at https://bestpractical.com/rt/issues.html ?
>
I filed a bug on CPAN against DBIx::SearchBuilder
Here:
https://rt.cpan.org/Public/Bug/Display.html?id=96902
Michelle
--
Michelle Sullivan
http://
Michelle Sullivan wrote:
> Dmitry Sivachenko wrote:
>
>> Did you file an issue for RT at https://bestpractical.com/rt/issues.html ?
>>
>>
>
> I filed a bug on CPAN against DBIx::SearchBuilder
>
> Here:
>
> https://rt.cpan.org/Public/Bug/Display.
Dmitry Sivachenko wrote:
> On 09 июля 2014 г., at 0:10, Michelle Sullivan wrote:
>
>
>> Michelle Sullivan wrote:
>>
>>> Dmitry Sivachenko wrote:
>>>
>>>
>>>> Did you file an issue for RT at https://bestpractical.com/rt/iss
t :))
>
One would have hoped that mod_perl2 would have had this removed first:
.if ${APACHE_VERSION} > 22
BROKEN= Does not build with apache24
.endif
Just my small (557 packages) build set:
>> Skipped ports: devel/bugzilla44 devel/p5-Log-Dispatch
www/p5-Apache-DBI www/p5-HTM
>> was something we even expect to work for bulk port builds.
>>
I'm not building all ports, but I am building ImageMagick with nox11...
This is what I have in my 10.0 make.conf for poudriere:
OPTIONS_UNSET=X11 NLS
Using the old WITHOUT_X11=yes builds -nox11 versions of the p
Dmitry Sivachenko wrote:
> On 09 июля 2014 г., at 0:10, Michelle Sullivan wrote:
>
>
>> Michelle Sullivan wrote:
>>
>>> Dmitry Sivachenko wrote:
>>>
>>>
>>>> Did you file an issue for RT at https://bestpractical.com/rt/iss
package] Error code 1
Stop in /usr/ports/print/tex-formats.
===> Cleaning for tex-formats-20120701_2
build of /usr/ports/print/tex-formats ended at Thu Jul 24 17:57:25 CEST 2014
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@fr
s cups-client...) ...!)
Michelle
Michelle Sullivan wrote:
> ===
> ===
> ===> Building package for tex-formats-20120701_2
> pkg_create: read_plist: unknown command
Matthew D. Fuller wrote:
> On Thu, Jul 24, 2014 at 10:19:55PM +0200 I heard the voice of
> Michelle Sullivan, and lo! it spake thus:
>
>> pkg_create: read_plist: unknown command '@fmtutil
>> /usr/local/share/texmf-var/web2c/pdftex/amstex.log
>> /usr/local/share/t
live does not add -base ? I might
try removing it and explicitly adding texlive (-base) to the build list
and see if that fixes it (will let everything build successfully first.)
Michelle
--
Michelle Sullivan
http://www.mhix.org/
___
freebsd-ports@fre
Michelle Sullivan wrote:
> Kurt Jaeger wrote:
>
>> Hi!
>>
>>
>>
>>> If that were true then everyone should switch to pkgng now..
>>>
>>>
>> Well, I've tested it and, yes, everyone should switch 8-)
>
1 - 100 of 218 matches
Mail list logo
