that line 7 years ago, it's possible times have changed ;)
http://www.freebsd.org/cgi/query-pr.cgi?pr=65577
Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "
We need to upgrade to php5-5.3.6 or later for PCI compliance.
When I check the ports list (http://www.freebsd.org/ports/lang.html),
the latest version is php5-5.3.3.
What happened to 5.3.6, which was released in March?
___
freebsd-ports@freebsd.org mail
.
Date: Tue, 30 Aug 2011 13:52:12 +0100
From: Chris Whitehouse
To: User Questions
Subject: editors/zim
Hi,
I have a problem with Zim which I wrote to the author about he
replied and said;
"I'm afraid version 0.29 is no longer
On 31/08/2011 20:00, Ruslan Mahmatkhanov wrote:
Chris Whitehouse wrote on 31.08.2011 22:34:
On 31/08/2011 14:13, Ruslan Mahmatkhanov wrote:
per...@pluto.rain.com wrote on 31.08.2011 09:29:
Forwarding to ports@, which seems more likely to yield an answer to
this particular inquiry than
compatibility with existing ports is still
> undetermined as well as expressly requesting feedback on ports that
> break or otherwise fail with this new version would be advisable and
> welcome. Way too many ports are being released lately with no advanced
>
Mk in ports is ugly.
A preliminary patch is at [1], for the first part. Yes, I'm sure it'll
break horribly somewhere, but hopefully that'll show what needs
fixing/whether it's possible/practical.
Chris
[1] http://bugs.freebsd.org/160361
--
Chris Rees | FreeBSD De
On 1 September 2011 17:12, Eygene Ryabinkin wrote:
> Chris, good day.
>
> Fri, Aug 19, 2011 at 03:32:43PM +0100, Chris Rees wrote:
>> I'm having a look at modifying INDEX to have a field at the end (to
>> cause minimum breakage), but I've discovered that in a few po
No /pub/FreeBSD/branches/-current/ports/ports-mgmt/pkgin .
> I'm not familiar with pkgin, but nice to see OS co-operation.
>
So, what do you actually mean by this?
Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freeb
ml originally marked all versions of Apache vulnerable, if
portaudit complains that 2.2.20 is vulnerable please run portaudit -F.
Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, s
On 29 August 2011 18:14, Ade Lovett wrote:
> On Fri, 26 Aug 2011 11:10:30 +0100
> Chris Rees wrote:
>
>> http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/tinderweb/dbsrc/
>>
>> Watch out, there be dragons :(
>
> But they're happy dragons ;)
>
> As
disagree with your logic. None of the FreeBSD committers _want_ this
> to be difficult.
>
+1.
Most of us despise its very existence, but recognise that just sometimes, it
saves some horribly fragile code from being written.
Chris
___
freebsd-por
On 02/09/2011 09:18, Ruslan Mahmatkhanov wrote:
Chris Whitehouse wrote on 01.09.2011 02:30:
[skipping the details since original problem was solved]
did you see that I had to add a line for MD5 to distinfo to make it work
on my 8.1-R system? Though the last change was to remove MD5
oops not sent to list...
On 03/09/2011 00:34, Glen Barber wrote:
Hi Chris,
On 9/2/11 5:40 PM, Chris Whitehouse wrote:
did you see that I had to add a line for MD5 to distinfo to make it work
on my 8.1-R system? Though the last change was to remove MD5...
It sounds to me parts of your ports
Guys,
I've had to deprecate sysutils/cfs -- there's a confirmed issue with
failing locks [1] which has been open for two years with no fix.
Please would someone consider stepping up to fix and maintain it? It
has two months to live.
Thanks!
Chris
[1] http://www.freebsd.org/cgi/query
On 4 September 2011 17:56, Chris Rees wrote:
> Guys,
>
> I've had to deprecate sysutils/cfs -- there's a confirmed issue with
> failing locks [1] which has been open for two years with no fix.
>
> Please would someone consider stepping up to fix and maintain it?
... perhaps if there isn't a vulnerability. At the moment it's
marked FORBIDDEN, so it's useless -- anyone who is serious about
fixing it at whatever time is welcome to check it out of the Attic --
a slight inconvenience for which we apologise.
In the mean time, the ports tree
how much more of an emergency can it
get?
Next time I'm going to avoid these tantrums and just deprecate it, like
everyone else does. Have you even noticed the removal of any ports recently?
If you care so much, follow the cvs list and watch out for them.
Chris
_
office
> ===>>> Aborting update
>
> ===>>> Update for editors/libreoffice failed
> ===>>> Aborting update
>
>
> /Leslie
Please update your ports tree, make clean and try again.
Chris
___
freebsd-ports@freebsd
On 5 September 2011 15:16, Leslie Jensen wrote:
> 2011-09-05 15:51, Chris Rees skrev:
>>
>> On 5 Sep 2011 14:45, "Leslie Jensen" wrote:
>>> ===> libreoffice-3.4.3 depends on file: /usr/local/bin/perl5.14.1 -
>>
>> found
>>>
>>&
On 5 Sep 2011 18:15, "Mikhail T." wrote:
>
> On -10.01.-28163 14:59, Chris Rees wrote:
>>>
>>> I've had to deprecate sysutils/cfs -- there's a confirmed issue with
>>> failing locks [1] which has been open for two years with no fix.
>&g
he problems, or suggest an
alternative bit of software.
Patches gratefully received (this is a volunteer effort after all)
Chris
___
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"
On 7 Sep 2011 16:53, "Mikhail T." wrote:
>
> On -10.01.-28163 14:59, Chris Rees wrote:
>>
>> I don't actually think they've been divisive -- it's been policy for
years.
>
>
> The policy -- up until fairly recently -- was to remove ports, that *f
2011/9/7 Mikhail Tsatsenko :
> Hi,
> I want to maintain this ports:
> mail/milter-greylist-devel
> dns/py-adns
> dns/checkdns
>
Done. Thanks for volunteering.
I know it seems overkill, but for future reference a PR is less likely
to get lost in the ma
On 8 Sep 2011 02:29, "Julian H. Stacey" wrote:
>
> Hi,
> Reference:
> > From: Doug Barton
> > Date: Wed, 07 Sep 2011 15:45:51 -0700
> > Message-id: <4e67f41f.70...@freebsd.org>
>
> Doug Barton wrote:
> > On 9/7/2011 10:02 AM, per...@pluto.rain.com wrote:
> > > Doug Barton wrote
t got filtered out by the list.
--
> Chris Brennan
> --
> A: Yes.
> >Q: Are you sure?
> >>A: Because it reverses the logical flow of conversation.
> >>>Q: Why is top posting frowned upon?
> http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/
&g
is valid to some degree, but if a package is still
> usable (and useful), then aren't we shooting ourselves in the foot by
> dropping it?
>
Can we please change the subject line? Most of us are in agreement
that this particular case is not that questionable.
This thread is for volunteers to fix cfs.
Chris
___
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"
ittle section about Resurrecting dead ports with a quick cvs
tutorial into the Porter's Handbook?
Chris
> On 09/10/2011 01:08, Carsten Jensen wrote:
>> I've seen many requests of late, for ports that are no longer in
>> active development, abandoned etc but still work
On 10 September 2011 10:46, Alberto Villa wrote:
> On Saturday 10 September 2011 10:53:54 Chris Rees wrote:
>> I also don't think this is a terrible idea, but perhaps we could just
>> put a little section about Resurrecting dead ports with a quick cvs
>> tutorial
stinfo.
I solved the problem, as Bapt suggested by approaching the author and
politely asking if he would host the tarball on github. He agreed to
do this.
Most of the time developers using github simply overlook the problems
of autogenerated tarballs, and just don't think to host dedicated ones
ly have enough skills to check a port out of the
Attic at least-- it's one command line. I don't see how much simpler
it could get:
cvs -d __insert_anoncvs_host_here co -D "day_before_port_was_deleted"
ports/category/dead_port
Chris
___
On 10 September 2011 18:47, Ruslan Mahmatkhanov wrote:
> Chris Rees wrote on 10.09.2011 21:33:
>>
>>
>> Counterexamples welcome!
>>
>> Chris
>
> When i worked on net/erlyvideo port there on github were tarballs for some
> old versions of it. When i asked
On 10 September 2011 19:39, Warren Block wrote:
> On Sat, 10 Sep 2011, Chris Rees wrote:
>
>> On 10 September 2011 18:15, Chad Perrin wrote:
>>>
>>> On Sat, Sep 10, 2011 at 04:45:02PM +0200, Matthias Andree wrote:
>>>>
>>>> I want to ma
On 11 Sep 2011 00:14, wrote:
>
> Chris Rees wrote:
>
> > cvsweb can also be used to find the day the port was deleted.
>
> Shouldn't that date be available in the MOVED entry?
>
Hm, indeed, and creative use of read and exp
"
>> (for some value of 'wrong') with the software in question. I can't
>> speak for Matthias or Chris, but I think the point here is that (at
>> least some) people don't want to make foot-shooting easier.
>
> Slippery slope: consider PHP, or Apache,
o improve our general
> infrastructure along these lines.
>
Most people faced with this problem redefine PKGDEINSTALL to the location of
the pkg-install script.
Chris
___
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"
rting-wrkdir.html
> http://www.freebsd.org/doc/en/books/porters-handbook/porting-wrkdirprefix.html
>
> Are you talking about new policy?
Hm, a bit naughty. Perhaps something like:
WRKDIR= ${WRKDIR:S/${.CURDIR}/${MASTERDIR}/}
would be more appropriate?
Jasperserver seems to do some pret
ses it. I too avoided mentioning a port for fear of the
> immature kids who destroy ports. At least one only got his
> commit bit recently. Its time a few commit bits were revoked.
>
Destroyed? Hardly. Put away for 'safe keeping', if you prefer.
Chris
think you're upsetting anyone in the slightest with them.
Use rational and technical arguments, or take a break.
Chris
___
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"
On 13 September 2011 18:54, Julian H. Stacey wrote:
> Hi,
> Reference:
>> From: Chris Rees
>> Date: Tue, 13 Sep 2011 18:44:37 +0100
>> Message-id:
>>
>
> Chris Rees wrote:
>> On 12 September 2011 22:18, Julian H. Stacey wrote:
>&
On 13 Sep 2011 20:57, "Julian H. Stacey" wrote:
>
> Hi,
> Reference:
> > From: Chris Rees
> > Date: Tue, 13 Sep 2011 19:25:01 +0100
> > Message-id:
>
> Chris Rees wrote:
> > On 13 September 2011 18:54, Julian H. Stac
pinging the affected ports' maintainers about it.
Really? I thought it was supposed to be standard behaviour- the @stopdaemon
line in pkg-plist facilitates that.
I know the old pkg tools won't do this, but perhaps pkgng could have an
option to disable stopping if desired
Chris
___
On 15 Sep 2011 21:28, "Xin LI" wrote:
>
> On Thu, Sep 15, 2011 at 1:08 PM, Chris Rees wrote:
> > On 15 Sep 2011 20:52, "Matthias Andree" wrote:
> >>
> >> Am 15.09.2011 21:36, schrieb Łukasz Wąsikowski:
> >>
> >> >
o it myself, but meh it doesn't upset me that much.
However, having services not restarted after an upgrade can leave you
with a) a vulnerable older service and b) a nasty shock when you
decide to reboot six months later and it breaks :)
Chris
__
are some ports where this doesn't work. Here's the list I found:
> dns/adns
> lang/lua
> graphics/pho
> graphics/xzgv
> devel/cvsps
>
Drop the TARGET_ARCH.
Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.
#!/bin/sh
> PID_FILE="/var/db/mysql/server.mypc.hu.pid"
> PID=`cat $PID_FILE`
> EXECUTABLE="/usr/local/etc/rc.d/mysql-server start"
>
> if test -r $PID_FILE ; then
># pidfile exist, is it correct?
>if kill -CHLD $PID >/dev/null 2>&1; then
this.
>
> This is on a FreeBSD-8.2 amd64 system.
On second thoughts, this looks like EVERSIONNUMBERGOINGBACKWARDS;
alphabetical characters in versions usually indicate beta status and are
numerically less than the numeric version.
Perhaps a PORTEPOCH bump is in order, or some creativity with DISTVERSIO
ut to be more like this:
>
> apache-2.2.20_1 < needs updating (index has 2.2.21)
>
> I have never seen this before. Is there something broken? I have a
> suspicion that programs like "portupgrade" or "portmanager" will not
> properly handle thi
e Matthew pointed out that the versions were actually going forwards,
you can indeed fix this with make fetchindex.
Chris
___
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"
> LICENSE_PERMS is mandatory (otherwise use a known LICENSE)
> *** Error code 1
>
> Stop in /usr/ports/x11/xbitmaps.
>
> Not a big deal, I've not seen that message before, that I rememver anyway.
>
Please csup and try again.
Has a nice ring, doesn't it ;)
Chris
___
On 21 September 2011 18:16, Ruslan Mahmatkhanov wrote:
>
> Good day,
>
> i want to maintain this two:
>
> www/py-webkitgtk
> devel/dreampie
>
Just so no-one else starts it, sunpoet just did it five minutes ago :)
Chris
___
f
On 21 September 2011 00:09, Edwin L. Culp W. wrote:
> On Tue, Sep 20, 2011 at 7:13 AM, Chris Rees wrote:
>>
>> On 20 Sep 2011 13:10, "Edwin L. Culp W." wrote:
>>>
>>> Checked UPDATING and there isn't any mention. I get:
>>>
>&
rences http://www.avahi.org/ticket/303 -- look
there for more information on why it's marked as such.
Chris
___
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"
t to some people, so it was decided to revert the change in
defaults.
If 1.9 works for you, great, but for now you'll need
RUBY_DEFAULT_VER=1.9 in /etc/make.conf.
Please keep testing 1.9!
Chris
___
freebsd-ports@freebsd.org mailing list
http://lis
elect a few of them through OPTIONS, but I'd like to
> avoid going this way : this will not simplify the port at all, it will
> only make it harder to maintain as the OPTIONS list will be huge, and
> (maybe ?) pointless for the end-user.
>
ain to
show this. I can't commit this for you right now, but someone else
will be able to help soon.
Only if there's been no word from the maintainer in three months
should s/he be replaced.
Chris
___
freebsd-ports@freebsd.org mailing list
http
d.jp/pub/lang/CPAN/%CPANSORT%/%SUBDIR%/ \
> ftp://ftp.dti.ad.jp/pub/X/WindowMaker/%SUBDIR%/
> ftp://ftp.dti.ad.jp/pub/X/XFree86/mirror/X.Org/contrib/%SUBDIR%/ \
> ftp://ftp.dti.ad.jp/pub/unix/editor/xemacs/%SUBDIR%/ \
Hm, ping again if it's sti
intend to order.
>
> First attempt to build hplip on the new computer failed due to libieee1284
> dependency being for i386 only. Subsequently I turned off that option after
> finding it was for parallel-port scanners only, not USB.
>
CUP
eebsd2.2*)
I've mentioned this to an autotools member, who has offered to fix it
fairly soon :)
Chris
___
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"
9-BLAH'
>>
>>
>> Now I understand why some OS vendors have choosen the latin 10 'X' for
>> their tenth version of their operating system ...
>
> At least there will be a long rest after
> the move to 10 is complete.. until FreeBSD 100.
>
I'm afraid not;
freebsd2*)
We'll be just as screwed at 20.
Hopefully we can fix that at the same time.
Chris
___
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"
On 25 September 2011 21:50, Anton Shterenlikht wrote:
> On Sun, Sep 25, 2011 at 01:36:48PM -0700, Doug Barton wrote:
>> On 09/25/2011 08:18, Chris Rees wrote:
>> > On 25 September 2011 15:06, Anton Shterenlikht wrote:
>> >> > ftp ftp.dti.ad.jp
o have my patch accepted?
>
I've reopened the PR for you.
By the way, please _never_ mess with the Subject: line when copying in
bug-followup- it confuses GNATS and makes a junk PR that someone
(usually linimon) has to tidy up :)
Chris
___
freebsd-po
On 28 September 2011 10:49, Thomas Mueller wrote:
> from Chris Rees :
>
>> Some rather strange printers will be recognised by umass before ugen
>> recognises them; you have to plug it in before umass is loaded or it
>> becomes a mass storage device.
>
>> I&#x
in bsd.port.mk
>
> is more risky then that particular commit which can potentially break
> devel/ for all OSVERSIONs.
>
bsd.ruby.mk is only included for ports that ask for it- hardly the same.
Chris
___
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"
I'm unable
> > to do any ports work right now.
>
> I've poked portmgr@. :-)
>
But portmgr has already replied...
Chris
___
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"
can check status of your ports, and
> examine build logs
> - as a side effect, you have recent package set you may use to
> install software on your FreeBSD machines
>
Also, it has a fairly large development team, many of whom are very high
profile porters alongside the odd portmg
ing to fetch from http://voodoo.bawue.com/download/.
> portmon-2.0.tar.gz 100% of 104 kB 71 kBps
Looks like a false negative when bapt tested it, I've undeprecated it
since the stated reason is no longer true.
Chris
__
On 8 October 2011 10:22, Thomas Mueller wrote:
> from Erwin Lansing :
>
>> In preparation for 9.0 the ports tree will be in feature freeze
>> after release candidate 1 (RC2)is released, currently planned for
>> October 17.
>
> Was there a typo here? Did you mean release candidate 1 or 2?
>
> RC1
wasn't a solution obvious enough for me. :)
>
>
> This appears to have been "fixed" by the (reversion of a) change to
bsd.port.mk in SVN r226162 - I still used the "UNAME_r" kludge, however,
>
r226162 has been reverted for now, so your fix is still relevant.
Chris
On 8 Oct 2011 23:29, "Baptiste Daroussin" wrote:
>
> On Sat, Oct 08, 2011 at 10:27:12AM +0100, Chris Rees wrote:
> > On 8 October 2011 10:53, wrote:
> > > lini...@freebsd.org wrote:
> > >
> > >> portname: net-mgmt/portmon
add them to the "new"
> flightgear-aircrafts port.
>
> Thanks for your feedback,
>
If you haven't committed it yet, can you please drop the 's' from aircraft?
Chris
___
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"
On 17 Oct 2011 13:17, "Ganael LAPLANCHE"
wrote:
>
> On Mon, 17 Oct 2011 13:10:26 +0100, Chris Rees wrote
>
> Hi Chris,
>
> > If you haven't committed it yet, can you please drop the 's'
> > from aircraft?
>
> Yep, I am aware of that typo (
'ppl' for this
> port, should files installed under pwl just be specified as
> this:
>
> %%PORTDOCS%%/pwl/bar
> %%PORTDOCS%%/pwl/bar/a
> %%PORTDOCS%%/pwl/bar/b
> ...
>
> and omit %%DOCSDIR%% from their path?
>
> Thanks for any insights.
>
Depends if there are (or could be) symlinks involved
Chris
___
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"
they have to not migrate to more recent versions like 84 or 90
> (it's 85 in terms of backward compatibility). Also note that PostgreSQL 8.2
> will reach it's EOL on December 2011, so this port will be deprecated in
> near future with high probabilit
esql-plpython
>
>
How did this one get in this email? It was fixed two weeks ago...
Chris
___
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"
e
>
Cy has fixed this, just not in time for Erwin's script to get the cvs up
apparently.
Chris
___
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"
essage.in
> U www/phpmyfaq/Makefile
> U www/phpmyfaq/distinfo
> U www/rubygem-httparty/Makefile
> U www/rubygem-httparty/distinfo
> U x11-wm/e16/Makefile
> U x11-wm/e16/distinfo
Spoke too soon, sorry, looks like he missed one.
Chris
__
to CC them.
In (almost?) all of the PRs I closed I referenced the Wiki page on Clang,
where it is clearly explained how to and how not to help.
I'm not hostile to PRs, I'm just not a fan of filling the PR database with
a unhelpful PRs. I apprecia
>
>
Yeah, unfortunately p1 has the same trouble as r1; it makes the version
appear less.
Perhaps as a temporary fix we could set PORTVERSION to 1.8.3.1?
Portepoch would be a little strong for this case wouldn't it?
Chris
__
On 30 Oct 2011 14:14, "Chris Rees" wrote:
>
>
> On 30 Oct 2011 09:48, "Barbara" wrote:
> >
> >
> > $ pkg_info -Ix sudo
> > sudo-1.8.3 Allow others to run commands as root
> > $ grep DISTVERSION /usr/ports/security/sudo/Makef
On 30 Oct 2011 15:21, "Matthias Andree" wrote:
>
> Am 30.10.2011 15:14, schrieb Chris Rees:
> > On 30 Oct 2011 09:48, "Barbara" wrote:
> >>
> >>
> >> $ pkg_info -Ix sudo
> >> sudo-1.8.3 Allow others to run comman
uite a lot of things!
We either need to:
1) Rename to coreutils to gnu- like most of the rest of the non-GNU
world and deal with the breakage (!)
2) Make gstat an OPTION, off by default
3) Be horribly inconsistent and rename gstat to gnustat
Thoughts?
Chris
[1] http://www.freebsd.org/cgi/qu
included in the package, and run with @exec and @unexec.
>>
>> Note the Porters' Handboock chapter 6.23.1. The knob to stop services is
>> already there.
>
> That feature as it exists currently isn't even close to adequate, and is
> causing more problems than it solves. Hence the discussion.
I'd be happy to code this; I've offered once before. However, I had a
hard time convincing people that it wasn't something that
portmaster/portupgrade should be doing instead...
Chris
___
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"
_upgrade_of_authdaemon() {
> send notice to operator or write something to logfile
> chmod 0755 /var/run/authdaemond
> restart authdaemon
> execute "self-test" script to check SMTP auth is working
> }
>
> This in general is more useful than just call
-a4, thus duplicating INDEX
records. Unfortunately, the master port is indexed first, so
jpeg2ps-a4 is left with an incorrect origin...
Does anyone have any clever ideas around this?
Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.
On 31 October 2011 15:18, Wesley Shields wrote:
> On Mon, Oct 31, 2011 at 09:21:26AM +0000, Chris Rees wrote:
>> Hey all,
>>
>> Traditionally we've tended to use the 'g' prefix for GNU utilities;
>> gmake, gtar etc, but apparently with stat that is a
-a
> FreeBSD serene.no-ip.org 9.0-RC1 FreeBSD 9.0-RC1 #4: Mon Oct 31
> 19:06:02 CDT 2011
> conr...@serene.no-ip.org:/usr/obj/usr/src/sys/CUSTOM amd64
>
> I'm stumped for the moment. Anybody got a clue to share?
Thanks for posting your 'fixed' message, but try to keep i
ike this:
>
> ports/audio/jack/work/jack-audio-connection-kit-0.121.3:
>
> case $host_os in
> ...
> freebsd1*)
> dynamic_linker=no
>;;
> ...
>
> And now? I'm cluesless now how we could solve this :-(
>
Searching the archives of both these lists would help y
d used to patch over certain deficiencies in shared
> library handling. You only need it when there is a specific problem,
> and in very many FreeBSD installs (particularly of recent and supported
> OS versions) you won't need it at all.
I hope you're not suggesti
;
Hm.
The real problem of course is that although addport is written in
Perl, rmport is written in sh; thus making it much more convenient to
use on a machine without Perl.
Possible solutions:
- Reimport Perl to base
- Rewrite addport to sh (though that would undo a lot o
t;
>
> HIH
>
> matthias
This isn't a plist problem; it's an
autotools-doesn't-understand-FreeBSD-10 problem.
On previous versions it works fine;
[crees@pegasus]~/libgee% grep '^pkgconfigdir' work/libgee-0.6.2.1/Makefile
pkgconfigdir = $(prefix)/libdata/
Insecure/unmaintained
ports are harmful.
If you care, step up to maintain them. Seriously. Or stop complaining.
Chris
PS only replying to Doug because it's the latest email, not because I think
he disagrees with me.
___
freebsd-ports@freebsd.org
tion is easy :) Thanks for helping to keep the tree in good shape.
Chris
___
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"
ly can improve here is to also put
>>> this information in the INDEX. I have an idea for that, just haven't
>>> been able to put the time into making it happen.
>>
>> How about something like the attached?
>
> Ooops. Wrong diff. Like this:
Why hav
uation, where the
> distfile mirror became the only working master site by default.
>
> Please provide a proper master site, or ask for help from someone who can.
>
I'll provide mine.
We now have a proper maintainer for the port, which was the majority of the
problem.
Chris
_
the jail a loopback interface?
>
> I don't mind if FreeBSD improves its build environment such that
> it breaks the build after 12 years. If adding a loopback interface
> fixes this, then we can all move on to more interesting things.
>
>Wietse
>
Clamav
> LATEST_LINK PORTNAME MAINTAINER
> ==
> idnkit dns/idnkit2f...@grid.einherjar.de
> idnkit dns/idnkit po...@freebsd.
t;> Why do you think it doesn't work for you?
>
> Got it working a couple of days ago. Typo elsewhere in the makefile.
Great to hear.
I find that make -V can be your friend, but the thing that mostly
trips me up here is doing a conditional based on LOCALBASE or similar
before bsd.port.pre.mk.
Chris
___
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"
:
> This the wrong list to ask about upgrades.
> Read http://www.freebsd.org
> I dont personaly keep up to date with latest fancy BSD-specific
> update scripts (as I've been doing Unix decades, & by reflex
> make all of src/ & ports/ that I use, but certainly back up etc
> & var first )
> Others may have more time to add info, but better ask on hackers@
> (or questions@ re upgrades)
>
> I would guess jails from 8.0 would survive on 8.2, Try on a spare box.
This actually looks kinda like an INDEX issue.
# make -C /usr/ports fetchindex
should fix it. Also, since portupgrade is unmaintained, may I suggest
getting to know portmaster
Chris
___
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"
a look later today, if no-one beats me to it.
For future reference, patches sometimes get 'lost' in this mailing
list, better to send a PR.
http://www.freebsd.org/send-pr.html
Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd
s/udns-0.0.9/
> src/events.c: In function 'events_free':
> src/events.c:47: error: 'struct _fdevent' has no member named 'events'
> *** Error code 1
>
> Stop in /home/paul/APE-Project-APE_Server-7368a9c.
> MODULES
> "Makefile", line 1: Could not f
201 - 300 of 1527 matches
Mail list logo
