Re: [RFC] NO_INSTALL in meta-ports considered harmful
On Sun, May 10, 2009 at 1:01 PM, Marcin Wisnicki wrote: > Some metaports (like print/cups) use NO_INSTALL. > > This will prevent such port from registering its installation in /var/db/ > pkg, which is different behaviour from installing it from prebuilt > package (where it registers just fine). > > IMHO not registering installation makes no sense and serves only to > confuse users (I've installed cups yet pkg_info claims I didn't!) and > causes unnecessary differences between software installed from ports vs > pkgs, which may lead to other unexpected problems (like missing > RUN_DEPENDS). > > Thus I advocate for more uniform handling of ports and packages by > treating it as a bug and replacing any such use of NO_INSTALL with empty > do-install target. Maybe even add a note to Porter's Handbook (though I > see no reference to NO_INSTALL there). > > If anyone has some insightfull comments why NO_INSTALL is not evil then > I'm all ears. > I'm not sure if this is the 'right answer', but NO_INSTALL allows the proper installation of numerous ports from one location (the meta-port). An example of this is the misc/instant-server port (though unmaintained, IIRC). If you remove the NO_INSTALL line from the Makefile, 'make' thinks misc/instant-server should be installed, rather than the collection of ports it is intended to install. Again, this is my interpretation of it. If I'm wrong, I gladly accept corrections to my thinking. :) -- Glen Barber ___ 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"
Re: [RFC] NO_INSTALL in meta-ports considered harmful
On Sun, May 10, 2009 at 2:51 PM, Marcin Wisnicki wrote: > On Sun, 10 May 2009 13:08:56 -0400, Glen Barber wrote: > >> I'm not sure if this is the 'right answer', but NO_INSTALL allows the >> proper installation of numerous ports from one location (the meta-port). >> An example of this is the misc/instant-server port (though >> unmaintained, IIRC). >> >> If you remove the NO_INSTALL line from the Makefile, 'make' thinks >> misc/instant-server should be installed, rather than the collection of >> ports it is intended to install. > > They will be installed since they are run dependencies. > >From what I can tell (from several metaports) -- they, themselves, are not installed. The ports defined in the metaport are installed. There is no source code for, using your example, CUPS[1]. CUPS (in the FreeBSD ports tree) is, for lack of a better explanation, a pointer to which specific ports you need to have in order to get a fully operation CUPS system running. Looking at the Makefile for print/cups [2] you can see the dependencies and that CUPS is not actually built (which in definition is what makes this a metaport). [1] http://www.freebsd.org/cgi/pds.cgi?ports/print/cups [2] http://www.freebsd.org/cgi/cvsweb.cgi/ports/print/cups/Makefile?rev=1.43 -- Glen Barber ___ 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"
Re: [Call For Testing] VirtualBox for FreeBSD!
On Thu, May 14, 2009 at 3:12 PM, Martin Wilke wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Howdy Guys, > > After the announcement from Alexander Eichner about > Virtualbox on FreeBSD, we started the work on a port > for FreeBSD. Now we think that we solved the most > problems and are ready for the first Call for Testing. > Fantastic! Can't wait to test it out. (And "thank you!") -- Glen Barber ___ 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"
Re: [Call For Testing] VirtualBox for FreeBSD!
On Thu, May 14, 2009 at 3:12 PM, Martin Wilke wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Howdy Guys, > > After the announcement from Alexander Eichner about > Virtualbox on FreeBSD, we started the work on a port > for FreeBSD. Now we think that we solved the most > problems and are ready for the first Call for Testing. > Runs great for me. (uname -a included.) Thanks for porting this! FreeBSD phoenix 7.2-STABLE FreeBSD 7.2-STABLE #0 r192129M: Thu May 14 22:53:56 UTC 2009 r...@phoenix:/usr/obj/usr/src/sys/GENERIC i386 -- Glen Barber ___ 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"
Re: [Call For Testing] VirtualBox for FreeBSD! take2
On Sun, May 17, 2009 at 2:09 PM, Martin Wilke wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > We rolled a new tarball with the patch from Juergen Lock [1] > with a posible fix for AMD64 users, tested on 3 machines > which now works without problems. Many Thanks to him for > his nice work! > Is there need for the i386 folks to rebuild, or does it only affect amd64? -- Glen Barber ___ 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"
Re: Question about the devel/subversion port
Hi, Doug On Thu, May 28, 2009 at 10:00 AM, Doug Poland wrote: > Hello, > > I have a question about this port. If one wants a client only > install, and one wants to use https as the communication protocol, > does one choose the "static" config option? > > In my case I choose: > > WITHOUT_MOD_DAV_SVN=true > WITH_APACHE2_APR=true > WITHOUT_MOD_DONTDOTHAT=true > WITH_NEON=true > WITHOUT_SERF=true > WITHOUT_SASL=true > WITHOUT_BDB=true > WITHOUT_ASVN=true > WITHOUT_MAINTAINER_DEBUG=true > WITHOUT_SVNSERVE_WRAPPER=true > WITHOUT_STATIC=true > WITHOUT_BOOK=true > > and was surprised to get a full installation of the apache webserver. > I understand that libapr and libapr-util are required but is a full > install of apache the only way to get those libraries? > > Subversion is one of those "you either have it or you don't" situations, meaning that it doesn't differentiate between "server" and "client." The 'svnserve' binary will be installed either way. As far as apr, there is a devel/apr-db42 port available (which, IIRC negates the need to install a full apache instance). Either way, if you plan on using https, you will need apache20 at a minimum (with openssl support). -- Glen Barber ___ 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"
Re: Question about the devel/subversion port
On Thu, May 28, 2009 at 10:59 AM, Doug Poland wrote:
>
> On Thu, May 28, 2009 09:20, Glen Barber wrote:
>> Hi, Doug
>>
>> On Thu, May 28, 2009 at 10:00 AM, Doug Poland
>> wrote:
>>> Hello,
>>>
>>> I have a question about this port. If one wants a client only
>>> install, and one wants to use https as the communication protocol,
>>> does one choose the "static" config option?
>>>
>>> and was surprised to get a full installation of the apache
>>> webserver. I understand that libapr and libapr-util are required
>>> but is a full install of apache the only way to get those
>>> libraries?
>>>
>>>
>>
>> Subversion is one of those "you either have it or you don't"
>> situations, meaning that it doesn't differentiate between "server"
>> and "client." The 'svnserve' binary will be installed either way.
>>
>> As far as apr, there is a devel/apr-db42 port available (which, IIRC
>> negates the need to install a full apache instance).
>>
>> Either way, if you plan on using https, you will need apache20 at a
>> minimum (with openssl support).
>>
> Thanks for the explanation. What is the purpose of building a static
> binary? Are all the bits (neon, apr, svn) rolled into one binary?
>
According to the Makefile:
.if defined(WITH_STATIC)
@${ECHO_MSG} "Static binaries will be built."
So, no. Not one binary, but (if I am understanding the Makefile
correctly) statically linked libraries.
--
Glen Barber
___
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"
Re: portsnap can't access portsnap[124].freebsd.org
On Fri, May 29, 2009 at 8:59 PM, Scott Bennett wrote: [snip] > > Script started on Fri May 29 19:33:32 2009 > hellas# portsnap fetch > Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. > Fetching public key from portsnap1.FreeBSD.org... failed. > Fetching public key from portsnap2.FreeBSD.org... failed. > Fetching public key from portsnap4.FreeBSD.org... failed. > No mirrors remaining, giving up. > hellas# exit > exit > > Script done on Fri May 29 19:33:46 2009 > > Can anyone tell me what the problem is? Is some portsnap service not > operational at freebsd.org currently for some reason? Is the up-to-date > portsnap trying to reach the wrong systems? [snip] Scott, I was able to do a 'fetch' using portsnap a little over an hour ago, as well as just now (10:15PM EDT). I successfully fetched from 'portsnap2'. Can you paste the 'ANSWER SECTON' from: 'dig portsnap2.freebsd.org' -- Glen Barber ___ 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"
Re: portsnap can't access portsnap[124].freebsd.org
On Sat, May 30, 2009 at 12:48 AM, Scott Bennett wrote: >> >>Can you paste the 'ANSWER SECTON' from: >> >> 'dig portsnap2.freebsd.org' >> > Sure, but I'm curious to know why. The names all do resolve to A RRs, > and pings to each by name did get echos back. Here it is, although I did > terminate the domain name by habit. Surely portsnap must not be so silly > as to pass unterminated names to the resolver. (Actually, I'm including > the whole output, not just the answer section.) > To make sure it wasn't a DNS problem (or DNS poisoning / hijacking). > > ;; ANSWER SECTION: > portsnap2.freebsd.org. 3600 IN A 72.21.59.250 > Same output for me.. -- Glen Barber ___ 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"
Re: [Call For Testing] VirtualBox for FreeBSD!
Good evening everyone.
Earlier today, I finished a VBox build on a fresh system.
After the build succeeded, I 'kldload /boot/modules/vboxdrv.ko' which
caused a panic. The machine runs a GENERIC kernel with KDB and
KDB_UNATTENDED added -- no other changes.
-- The machine --
FreeBSD orion 7.2-STABLE FreeBSD 7.2-STABLE #1 r193481: Sat Jun 6
10:22:25 EDT 2009 r...@orion:/usr/obj/usr/src/sys/ORION i386
-- Snippet from 'dmesg' --
FreeBSD 7.2-STABLE #0 r193481: Fri Jun 5 01:55:06 EDT 2009
r...@orion:/usr/obj/usr/src/sys/ORION
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz (2217.69-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x6fd Stepping = 13
Features=0xbfebfbff
Features2=0xe39d
AMD Features=0x2010
AMD Features2=0x1
Cores per package: 2
real memory = 2128793600 (2030 MB)
avail memory = 2073436160 (1977 MB)
ACPI APIC Table:
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
ioapic0: Changing APIC ID to 2
-- The panic --
orion# kgdb kernel.debug /var/crash/vmcore.0
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...
Unread portion of the kernel message buffer:
!!Assertion Failed!!
Expression: cMillies != RT_INDEFINITE_WAIT
Location : /usr/home/gbarber/virtualbox/virtualbox/work/virtualbox-2.2.2r19980/
src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c(212) rtSemEventWait
Fatal trap 3: breakpoint instruction fault while in kernel mode
cpuid = 1; apic id = 01
instruction pointer = 0x20:0xc5e180be
stack pointer = 0x28:0xe7a73c08
frame pointer = 0x28:0xe7a73c34
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= IOPL = 0
current process = 1838 (TIMER)
trap number = 3
panic: breakpoint instruction fault
cpuid = 1
Uptime: 6h58m4s
Physical memory: 2017 MB
Dumping 180 MB: 165 149 133 117 101 85 69 53 37 21 5
Reading symbols from /boot/kernel/coretemp.ko...Reading symbols from /boot/kerne
l/coretemp.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/coretemp.ko
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/ac
pi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/modules/vboxdrv.ko...done.
Loaded symbols for /boot/modules/vboxdrv.ko
#0 doadump () at pcpu.h:196
196 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) bt
#0 doadump () at pcpu.h:196
#1 0xc07e45a7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2 0xc07e48b2 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:574
#3 0xc0ae6d83 in trap_fatal (frame=0xe7a73bc8, eva=0)
at /usr/src/sys/i386/i386/trap.c:939
#4 0xc0ae7bdc in trap (frame=0xe7a73bc8) at /usr/src/sys/i386/i386/trap.c:726
#5 0xc0acc05b in calltrap () at /usr/src/sys/i386/i386/exception.s:159
#6 0xc5e180be in rtSemEventWait (EventSem=0xc5d2a110, cMillies=4294967295,
fInterruptible=false)
at /usr/home/gbarber/virtualbox/virtualbox/work/virtualbox-2.2.2r19980/src/V
Box/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:212
#7 0xc5e181b0 in RTSemEventWait (EventSem=0xc5d2a110, cMillies=4294967295)
at /usr/home/gbarber/virtualbox/virtualbox/work/virtualbox-2.2.2r19980/src/V
Box/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:240
#8 0xc5e157f1 in rtTimerThread (Thread=0xc5d2b990, pvUser=0xc5d2be90)
at /usr/home/gbarber/virtualbox/virtualbox/work/virtualbox-2.2.2r19980/src/V
Box/Runtime/generic/timer-generic.cpp:238
#9 0xc5e1a6c0 in rtThreadMain (pThread=0xc5d2b990, NativeThread=3316025600,
pszThreadName=0xc5d2b9d0 "TIMER")
at /usr/home/gbarber/virtualbox/virtualbox/work/virtualbox-2.2.2r19980/src/V
Box/Runtime/common/misc/thread.cpp:635
#10 0xc5e26ee7 in rtThreadNativeMain (pvThreadInt=0xc5d2b990)
at /usr/home/gbarber/virtualbox/virtualbox/work/virtualbox-2.2.2r19980/src/V
Box/Runtime/r0drv/freebsd/thread2-r0drv-freebsd.c:112
---Type to continue, or q to quit---
#11 0xc07bdbc9 in fork_exit (callout=0xc5e26ec0 ,
arg=0xc5d2b990, frame=0xe7a73d38) at /usr/src/sys/kern/kern_fork.c:811
#12 0xc0acc0d0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264
(kgdb)
Any thoughts? If needed, I will test patches.
--
Glen Barber
___
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"
Re: [Call For Testing] VirtualBox for FreeBSD! take 6
Hi, Martin et al This latest version builds fine for me and no panic on kldload vboxdrv.ko uname -a: FreeBSD orion 7.2-STABLE FreeBSD 7.2-STABLE #3 r193905: Wed Jun 10 08:42:33 EDT 2009 r...@orion:/usr/obj/usr/src/sys/ORION i386 Thanks for taking the time to port this! -- Glen Barber ___ 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"
Re: [CFT] GTK frontend for VirtualBox
On Tue, Jun 16, 2009 at 10:45 AM, Alexander Logvinov wrote: > Hello! > > For GTK lovers I've created a port for vboxgtk 0.4.1: Great! > http://www.logvinov.ru/files/dist/vboxgtk.tar . Sometimes it works. :) Heh. "Sometimes". :) > > 2VBox Team: The latest 0.5.0-beta1 version of vboxgtk wants python > bindings for the VirtualBox Python API support. Any chance to get it? > -- Glen Barber ___ 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"
Re: VirtualBox regression in the ports tree
On Tue, Jun 16, 2009 at 10:37 AM, Richard Kuhns wrote: > Martin Wilke wrote: > ... > >> http://people.freebsd.org/~miwi/vbox/virtualbox_6.tgz >> >> Happy Testing! > > This worked perfectly when built and installed under 7.2-STABLE (i386) as of a > couple of days ago. > > I just uninstalled it, and built and installed VirtualBox in the ports tree. > My > machine paniced when I tried to kldload vboxdrv (running X, so I couldn't see > the message(s)). Take a look in /var/crash for a 'vmcore.N' dump. If it exists, you can get debugging information by doing: cd /usr/obj/usr/src/sys/MYKERNEL kgdb kernel.debug /var/crash/vmcore.N (replacing 'N' with the latest crash file number). To get the backtrace, type 'bt' in kgdb. Full debugging information can be found at: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html -- Glen Barber ___ 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"
Re: Possibly unbuildable ports reminder
On Sun, Jun 28, 2009 at 6:00 AM, Bill Fenner wrote: > > so you can easily check the status of ports that you maintain. In > addition, the list of ports with no MAINTAINER with build problems is > > http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html > Bill, There may be something wrong here, unless commits were made on the ports I have checked so far -- math/bamg and mail/crm114 are both listed as BROKEN on this link, but the Makefile of both do not reflect this. Both ports were listed BROKEN for fetch errors, and as far as I can tell, fetch fine. mail/crm114 specifically, according to cvsweb, was last updated: Wed May 13 16:03:16 2009 UTC (6 weeks, 3 days ago) by beat If there is no problem, I apologize for the noise -- just wanted to bring this to your attention in case there really is a problem. Thanks -- Glen Barber ___ 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"
Re: Question about a failure report
On Fri, Jul 3, 2009 at 2:18 PM, Paul Schmehl wrote: > I just got a failure report for one of my ports: security/barnyard-squil. > That port is a slave port to security/barnyard. > > The error is: > ** > ERROR: unable to find mysql headers (mysql.h) > checked in the following places > /mysql.h > ** > > This is what I have in the Makefile of security/barnyard: > > .if defined(WITH_MYSQL) > USE_MYSQL= yes > CONFIGURE_ARGS+= --enable-mysql > .endif > > How do I fix this since I'm using the builtin macro? > I remember seeing another post a few days ago about mysql.h -- IIRC, it was a perl binding that could not find it. Unfortunately, I don't remember what list it was, nor the subject of the email. Does your port define which version of mysql to use? -- Glen Barber ___ 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"
security/rkhunter and sysutils/lsof using 100% CPU but not producing output
Hi, folks. I'm running: FreeBSD orion 8.0-CURRENT FreeBSD 8.0-CURRENT #6 r195343: Sat Jul 4 12:23:04 EDT 2009 r...@orion:/usr/obj/usr/src/sys/ORION i386 Once security/rkhunter reaches the 'Performing malware checks', there appears to be no I/O -- this check used to take less than 2 minutes on 7-STABLE (and previous). I was running the check as I was writing this email -- here's what top(1) shows: last pid: 52370; load averages: 0.98, 0.77, 0.48up 0+02:54:16 16:13:35 74 processes: 2 running, 72 sleeping CPU: 8.3% user, 0.0% nice, 45.8% system, 0.0% interrupt, 45.8% idle Mem: 224M Active, 203M Inact, 124M Wired, 1484K Cache, 112M Buf, 1432M Free Swap: 4027M Total, 4027M Free PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 52298 root 1 1160 3348K 1732K RUN 1 2:12 92.09% lsof Any thoughts on how I should proceed troubleshooting this? The basics are covered, of course, such as an up-to-date tree, and fresh rebuilds on the port(s) in question. Thanks for any tips. -- Glen Barber ___ 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"
Re: Possibly unbuildable ports reminder
On Tue, Jul 14, 2009 at 2:07 PM, Charlie Kester wrote: > On Tue 14 Jul 2009 at 03:00:04 PDT Bill Fenner wrote: >> >> Dear porters, >> >> This is just a reminder to please periodically check the list of >> unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . >> A list by MAINTAINER is >> >> http://people.freebsd.org/~fenner/errorlogs/ >> >> so you can easily check the status of ports that you maintain. In >> addition, the list of ports with no MAINTAINER with build problems is > > Is the portstree updated before running these build tests? > > My sysutils/rdup port is shown as failing a build test on 7 July, and > that it's using the port's Makefile v 1.1, dated 19 June. But I already > submitted a fix for the reported error , and it was committed on 4 July > as Makefile v 1.2. > I swear I asked about this a few weeks ago... http://lists.freebsd.org/pipermail/freebsd-ports/2009-June/055553.html The problems I reported then are still present in the latest build error report. -- Glen Barber ___ 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"
Re: error updating Postfix
On Mon, Jul 20, 2009 at 7:42 PM, Per olof Ljungmark wrote: > Wesley Shields wrote: >> >> On Tue, Jul 21, 2009 at 12:23:16AM +0200, Per olof Ljungmark wrote: >>> >>> cc -DDEF_CONFIG_DIR=\"/usr/local/etc/postfix\" >>> -DDEF_DAEMON_DIR=\"/usr/local/libexec/postfix\" >>> -DDEF_COMMAND_DIR=\"/usr/local/sbin\" >>> -DDEF_SENDMAIL_PATH=\"/usr/local/sbin/sendmail\" >>> -DDEF_NEWALIAS_PATH=\"/usr/local/bin/newaliases\" >>> -DDEF_MAILQ_PATH=\"/usr/local/bin/mailq\" >>> -DDEF_MANPAGE_DIR=\"/usr/local/man\" >>> -DDEF_README_DIR=\"/usr/local/share/doc/postfix\" >>> -DDEF_HTML_DIR=\"/usr/local/share/doc/postfix\" >>> -DDEF_QUEUE_DIR=\"/var/spool/postfix\" -DDEF_DATA_DIR=\"/var/db/postfix\" >>> -DDEF_MAIL_OWNER=\"postfix\" -DDEF_SGID_GROUP=\"maildrop\" -DHAS_PCRE >>> -I/usr/local/include -DUSE_SASL_AUTH -DUSE_CYRUS_SASL -I/usr/local/include >>> -I/usr/local/include/sasl -DUSE_TLS -I/usr/include -O2 -fno-strict-aliasing >>> -pipe -I. -DFREEBSD7 -c attr_clnt.c >>> In file included from attr_clnt.c:77: >>> /usr/include/unistd.h:329: error: conflicting types for 'closefrom' >>> ./sys_defs.h:1404: error: previous declaration of 'closefrom' was here >>> *** Error code 1 >> >> It was fixed on 2009/07/09. Make sure you have the latest ports tree. > > Hm, I updated an hour ago... from cvsup.FreeBSD.org, the makefile is dated > July 17th when the system was also updated. > > 7.2-STABLE FreeBSD 7.2-STABLE #0: Fri Jul 17 17:27:43 CEST 2009 > > Just for the sake of it I cvsupped again just now to be sure but no change. > What was fixed in the 9th.? I obviously need to check if something went > wrong when I updated the system. > Try: cd /usr/ports/mail/postfix; make clean distclean; make install -- Glen Barber ___ 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"
Re: this time it's vim/distfiles
On Wed, Jul 29, 2009 at 3:26 PM, Esa Karkkainen wrote: > On Wed, Jul 29, 2009 at 02:59:56PM +0100, N.J. Mann wrote: >> Try changing distinfo accordingly. > > You can use your favourite editor or run the following commands as root > > # cd /usr/ports/editors/vim > # sed -I .orig -e 's/7\.2\.041%/7.2.041^/' distinfo > That shouldn't fix the problem, because according to the OP's error: => No MD5 checksum recorded for vim/7.2.041^. => No SHA256 checksum recorded for vim/7.2.041^. => No suitable checksum found for vim/7.2.041^. Meaning, there is no checksum for the file with '^' in place of '%'. -- Glen Barber ___ 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"
Re: SourceForge changing file distribution scheme!
On Tue, Aug 11, 2009 at 11:36 AM, Erwin Lansing wrote: > On Tue, Aug 11, 2009 at 07:20:54PM +0400, Dmitry Marakasov wrote: >> Hi! > > hi Dmitry, >> >> I've noticed that SF is changing file distribution scheme significantly, >> and I guess that will affect many ports and maybe infrastructure. > > I fear the same, unfortunately. However, I haven't as yet been able to > identify a consistency in the new scheme. Is it only new files that are > put in the /project/ folder? It doesn't appear so. See the PR I filed recently to fix a 'fetch failed' port [1]. I believe it is safe to assume this port was 'fetch'able until recently. [1] - http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/137597 -- Glen Barber ___ 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"
Re: SourceForge changing file distribution scheme!
On Tue, Aug 11, 2009 at 8:44 PM, Dmitry Marakasov wrote: > * Dmitry Marakasov (amd...@amdmi3.ru) wrote: > >> I've noticed that SF is changing file distribution scheme significantly, > > So, what do we do? May I commit the patch (+portmgr)? I believe this to > be the best solution (even if a temporary one if we'll be able to > resolve things with SF) as it will be clear which port uses the new > scheme and there will be no variety of workarounds. > Hi, Perhaps I've lost it in this thread, but is it only a certain amount of ports affected? It appears the two SF ports I maintain hiccup a bit, but are able to eventually find the distfile. -- Glen Barber ___ 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"
Re: SourceForge changing file distribution scheme!
On Wed, Aug 12, 2009 at 10:03 AM, Dmitry Marakasov wrote: > * Glen Barber (glen.j.bar...@gmail.com) wrote: > >> > So, what do we do? May I commit the patch (+portmgr)? I believe this to >> > be the best solution (even if a temporary one if we'll be able to >> > resolve things with SF) as it will be clear which port uses the new >> > scheme and there will be no variety of workarounds. >> >> Perhaps I've lost it in this thread, but is it only a certain amount >> of ports affected? It appears the two SF ports I maintain hiccup a >> bit, but are able to eventually find the distfile. > > This should only affect updating SF ports to new versions. I've checked > your ports, they seem to fetch just fine. > In that case, do you have GNATS access to close the PR I recently filed because of SF fetch errors[1]? If not, I will post a followup to have it closed. Regards, [1] - http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/137597 -- Glen Barber ___ 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"
Re: SourceForge changing file distribution scheme!
On Wed, Aug 12, 2009 at 12:01 PM, Dmitry Marakasov wrote: > * Glen Barber (glen.j.bar...@gmail.com) wrote: > >> In that case, do you have GNATS access to close the PR I recently >> filed because of SF fetch errors[1]? If not, I will post a followup >> to have it closed. >> >> [1] - http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/137597 > > That one is the case, it was updated in Aug, so it needs to switch to > the new scheme. Also, additional mirror is never a bad thing. I'll watch > that PR and commit it if danfe@ timeouts. > Even better. :-) Thanks! -- Glen Barber ___ 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"
Re: SourceForge changing file distribution scheme!
On Wed, Aug 12, 2009 at 3:16 PM, Lars Engels wrote: > On Tue, Aug 11, 2009 at 07:55:00PM +0400, Dmitry Marakasov wrote: >> * Erwin Lansing (er...@freebsd.org) wrote: >> >> > > I've noticed that SF is changing file distribution scheme significantly, >> > > and I guess that will affect many ports and maybe infrastructure. >> > >> > I fear the same, unfortunately. However, I haven't as yet been able to >> > identify a consistency in the new scheme. > > There can also be very weird subdir names: :-( > http://downloads.sourceforge.net/project/tvbrowser/TV-Browser (Java 5 and > higher)/2.7.4/tvbrowser-2.7.4.tar.gz > > If it helps any, I can host the weird-named distfiles on my site. Let me know if you would like me to do so. -- Glen Barber ___ 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"
Re: installing X in FreeBSD 7.2 RELEASE
On Sat, Sep 5, 2009 at 3:08 PM, st ellis wrote: > i've been using freebsd for about 12 years. my latest working version is 6.2, > which works aok. > this week i tried 7.2, but i cannot find the command to set up X. in 6.2, it > was xorgcfg which worked beautifully. can anyone email me the correct > command, or procedure? You are probably looking for: X -configure to set up Xorg. To test the configuration: X -config /root/xorg.conf.new HTH. -- Glen Barber ___ 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"
Re: Creating a New Port: /usr/ports/security/pecl-kadm5
Hi.
On Thu, 10 Sep 2009 20:36:25 -0400, Tim Gustafson wrote:
I'm trying to create a new port. To get myself started, I copied
pecl-hash and then modified the Makefile and the distinfo file. When I
try to make my port, it downloads the file from the PECL repository,
extracts it, runs configure and then starts compiling, but in the end I
get a bunch of errors from cc about undefined constants:
[snip]
So, my first question is: How can I tell my port to patch
work/kadm5-0.2.3/kadm5.c with the needed line above?
You will want to create a '-patch' line in the Makefile. See the
following as a reference:
http://www.freebsd.org/doc/en/books/porters-handbook/slow-patch.html
My second question is: Is there a "proper way" to hack the needed values
into kadm5_err.h? Should I make a new .h file and include it as part of
the port only?
You can create a ${PORTNAME}/files directory containing the file(s) you
need, specific to your port and FreeBSD.
See the following link for more information:
http://www.freebsd.org/doc/en/books/porters-handbook/install.html
And last but not least:
After I manually patched the kadm5.c file and hacked the missing
declarations into kadm5_err.h, I get a different set of errors:
[snip]
Sorry. There are lots of experienced folks who can help with C errors.
I, unfortunately, am not one of them.
You may want to bookmark this, as well:
http://www.freebsd.org/doc/en/books/porters-handbook/
Cheers,
--
Glen Barber
___
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"
Re: audio/sox bump to 14.3.0 request
Hi. On Thu, 10 Sep 2009 21:31:53 -0400, Peter Beckman wrote: I haven't heard back from the maintainer of sox yet on the requested bump to sox 14.3.0. I didn't find any process outlined in the handbook or the porters handbook, and I would have searched the archives but the search index hasn't been rebuilt since 2007. Regarding ports that are maintained, there is generally a 2 week timeout with PRs regarding port upgrades (which is noted in the handbook), assuming a patch is provided. The most likely delay with your situation is that you did not support a patch to actually perform the update - simply the request. Upgrading ports that has other maintainers is time consuming to begin with - even moreso when you do not provide a patch to aide in the process. I searched the archives via google with no real results on any process on how to poke the maintainer to life. You CC'd the maintainer. That is sufficient. -- Glen Barber ___ 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"
Re: audio/sox bump to 14.3.0 request
On Thu, 10 Sep 2009 22:01:00 -0400, Peter Beckman wrote: I'll work on learning how to build the package so I can submit a diff rather than a request. The Porter's Handbook is a good place to start: http://www.freebsd.org/doc/en/books/porters-handbook/ The Handbook recommends the ports-mgmt/porttools port. I personally suggest the ports-mgmt/genplist port as well. Cheers, -- Glen Barber ___ 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"
multimedia/linux-gspca-kmod fails to build on 8.X
Hi I'm trying to build multimedia/linux-gspca-kmod on my laptop for my integrated SuYin camera (build errors below). The devel/linux-kmod-compat port which is a dependency of this port builds correctly. /usr/local/share/linux-kmod-compat/linux_compat/ldev_stub.h includes usb_port.h, which does not exist on 8.X. To rule out the obvious, I pulled down usb_port.h from 7-STABLE and created a symlink in /usr/include, which failed to no surprise. In my searches prior to this attempt at hackery, I've found hints to try ports such as graphics/vid (and a few others, whose names elude me at the moment), however these ports are marked BROKEN for OSVERSION >=800064. I have tried to track what this port needs from usb_port.h to modify ldev_stub.h, but have had no luck thus far. I assume this is related to the new USB stack in 8.X - please correct me if this assumption is incorrect. Should linux-kmod-compat and multimedia/linux-gspca-kmod be marked BROKEN on 8.X? (If I've missed something obvious, I apologize in advance.) Regards, -- build errors -- ===> Building for linux-gspca-kmod-1.0.20_1 @ -> /usr/src/sys machine -> /usr/src/sys/i386/include awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/kern/device_if.m -h :> opt_usb.h rm -f .depend mkdep -f .depend -a -nostdinc -DUSB_DEBUG -DGSPCA_ENABLE_DEBUG -DGSPCA_ENABLE_COMPRESSION -DCONFIG_USB_GSPCA_MODULE=1 -DVID_HARDWARE_GSPCA=0xFF -DGSPCA_VERSION=\"01.00.20\" -D__KERNEL__ -DDRIVER_NAME=gspca -DDEV_NAME=\"video\" -D_KERNEL -DKLD_MODULE -ISunplus -ISunplus-jpeg -ISonix -IConexant -IVimicro -Idecoder -I/usr/local/share/linux-kmod-compat/linux_compat -I. -I@ -I@/contrib/altq gspca_core.c /usr/ports/multimedia/linux-gspca-kmod/work/gspcav1-20071220/decoder/gspcadecoder.c /usr/local/share/linux-kmod-compat/linux_compat/ldev_stub.c /usr/local/share/linux-kmod-compat/linux_compat/linux_compat.c In file included from /usr/local/share/linux-kmod-compat/linux_compat/ldev_stub.c:44: /usr/local/share/linux-kmod-compat/linux_compat/ldev_stub.h:69:22: error: usb_port.h: No such file or directory In file included from /usr/local/share/linux-kmod-compat/linux_compat/linux_compat.c:44: /usr/local/share/linux-kmod-compat/linux_compat/ldev_stub.h:69:22: error: usb_port.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/ports/multimedia/linux-gspca-kmod/work/gspcav1-20071220. *** Error code 1 Stop in /usr/ports/multimedia/linux-gspca-kmod. -- Glen Barber ___ 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"
Re: cvs commit: ports/mail/p5-qpsmtpd/files qpsmtpd.in
Hi,
On Mon, Dec 14, 2009 at 4:29 PM, Glen Barber wrote:
> On Mon, Dec 14, 2009 at 4:04 PM, Doug Barton wrote:
>> Philip M. Gollucci wrote:
>>> I need to update it 0.83 anyway.
>>> I was going to rewrite the whole rc.d script from sratch at that time.
>>> In the meantime though this particular thing should help that person
>>> until I have time.
[...]
>
> I can have another look at this either tonight or tomorrow evening,
> unless someone updates it beforehand. I will even update to 0.83 in
> the process.
>
I have attached two diffs of the rc script, however I have run into a
few issues with both.
The first diff still uses 'stop_cmd(){kill `cat $pidfile`}' for the
following reasons:
- adding ': qpsmtpd_pidfile="$pidfile"' would never create
/var/run/qpsmtpd.pid, thus the rc script would never find it to kill
the process. To work around this, I added the pidfile creation to
start_cmd().
- as a side effect of the above workaround, stopping the process
would kill the PID, however leave the pidfile. As a second
workaround, I have kept the stop_cmd() function, and forcibly removed
the pidfile after the process was killed.
The second replaces the pidfile line with this:
[ -z "$pidfile" ] && pidfile="/var/run/${name}.pid"
and adds a command_args line, however the pidfile is still not cleaned
after stopping the service, so stop_cmd() is used again. Is there a
more correct way to clean up the pidfile that what I have attached?
Regards, and have a happy and safe new year.
--
Glen Barber
--- qpsmtpd.in.1.orig 2009-12-31 14:02:16.0 -0500
+++ qpsmtpd.in.12009-12-31 14:04:16.0 -0500
@@ -16,85 +16,30 @@
name="qpsmtpd"
rcvar=`set_rcvar`
-load_rc_config $name
+pidfile="/var/run/qpsmtpd.pid"
command="%%PREFIX%%/bin/qpsmtpd-forkserver"
-pidfile="/var/run/qpsmtpd/qpsmtpd.pid"
-start_precmd="start_precmd"
start_cmd="start_cmd"
stop_cmd="stop_cmd"
-start_precmd()
-{
-#exits if no user is specified
-if [ -z $qpsmtpd_user ]; then
- echo "qpsmtpd_user not set"
- exit 1
-fi
-
-#exits if no group is specified
-if [ -z $qpsmtpd_group ]; then
- echo "qpsmtpd_group not set"
- exit 1
-fi
-
-#sets it to the default if the port is not specified
-if [ -z $qpsmtpd_port ]; then
- qpsmtpd_port="2525"
-fi
-
-#set it to the default max per ip
-if [ -z $qpsmtpd_max_per_ip ]; then
- qpsmtpd_max_per_ip="5"
-fi
-
-#set it do the max number of connections total
-if [ -z $qpsmtpd_max_connections ]; then
- qpsmtpd_max_connections="15"
-fi
-
-#set the default listen on to everything
-if [ -z $qpsmtpd_listen_on ]; then
- qpsmtpd_listen_on="0.0.0.0"
-fi
-
-if [ ! -d /var/run/qpsmtpd/ ] ; then
- mkdir /var/run/qpsmtpd
-fi
-
-chown $qpsmtpd_user:$qpsmtpd_group /var/run/qpsmtpd
-}
-
-start_cmd()
-{
- if [ -e $pidfile ]; then
- echo "$name already running as PID `cat $pidfile`."
- exit 1
- else
- eval $command \
- -p $qpsmtpd_port \
- -c $qpsmtpd_max_connections \
- -u $qpsmtpd_user \
- -m $qpsmtpd_max_per_ip \
- -l $qpsmtpd_listen_on \
- --pid-file $pidfile \
- -d \
- && echo "$name started as PID `cat $pidfile`." \
- || echo "Failed to start $name"
- fi
-}
-
-stop_cmd()
-{
- if [ -e $pidfile ]; then
- kill `cat $pidfile` \
- && echo "$name stopped." \
- || echo "Could not stop `cat $pidfile`."
- else
- echo "Cannot find $pidfile - $name not running?"
- exit 1
- fi
+load_rc_config $name
+: qpsmtpd_enable="NO"
+: qpsmtpd_user="smtpd"
+: qpsmtpd_group="smtpd"
+: qpsmtpd_port="2525"
+: qpsmtpd_max_per_ip="3"
+: qpsmtpd_max_connections="15"
+: qpsmtpd_listen_on="0.0.0.0"
+
+start_cmd() {
+ echo "Starting $name."
+ eval $command -d --pid-file $pidfile
+}
+
+stop_cmd() {
+ echo "Stopping $name."
+ kill `cat $pidfile` && rm $pidfile
}
run_rc_command "$1"
--- qpsmtpd.in.2.orig 2009-12-31 14:02:18.0 -0500
+++ qpsmtpd.in.22009-12-31 14:05:17.0 -0500
@@ -16,85 +16,27 @@
name="qpsmtpd"
rcvar=`set_rcvar`
-load_rc_config $name
command="%%PREFIX%%/bin/qpsmtpd-forkserver"
-pidfile="/var/run/qpsmtpd/qpsmtpd.pid"
-start_precmd="start_precmd"
-start_cmd="start
Re: cvs commit: ports/mail/p5-qpsmtpd/files qpsmtpd.in
Hi Doug,
I really appreciate the feedback.
On Thu, Dec 31, 2009 at 5:30 PM, Doug Barton wrote:
> Glen Barber wrote:
[...]
>
> I've attached a diff for a script that works, please test it and if
> you're satisfied I will commit it for you. However, there is
> apparently an additional problem with the port because when I
> installed it the "smtpd" user was not created. If that is mandatory
> for the script to work it should be added by the port. I could get it
> started if I specified another unprivileged user/group in rc.conf.local.
>
Initially, they were the user/group I was using to run this service.
I later found it was not necessary, and in changing the rc script, I
had forgotten to remove them. This service runs fine with
nobody/nogroup, which is reflected in an attached patch, which
incorporates your changes.
[...]
> 11. Properly sets the defaults for the options. (FYI, in your patch
> you used: ': foo="bar"', spend a few minutes thinking about why that's
> bad.) :)
I'm glad embarrassment doesn't translate well over the internet... :-)
A diff against the port version with your modifications and my
nobody/nogroup changes is attached. If it is okay with the maintainer
(cc'd), I think this can be committed.
Thanks again for the feedback, and I really appreciate your explanations.
Regards,
--
Glen Barber
diff -ruN /usr/ports/mail/p5-qpsmtpd/Makefile
/usr/local/ports/mail/p5-qpsmtpd/Makefile
--- /usr/ports/mail/p5-qpsmtpd/Makefile 2009-12-26 17:20:35.0 -0500
+++ /usr/local/ports/mail/p5-qpsmtpd/Makefile 2009-12-31 17:59:14.0
-0500
@@ -36,6 +36,7 @@
USE_RC_SUBR= qpsmtpd
+SUB_LIST+= PERL=${PERL}
SUB_LIST+= PORTNAME=${PORTNAME}
SUB_FILES+=pkg-message
diff -ruN /usr/ports/mail/p5-qpsmtpd/files/qpsmtpd.in
/usr/local/ports/mail/p5-qpsmtpd/files/qpsmtpd.in
--- /usr/ports/mail/p5-qpsmtpd/files/qpsmtpd.in 2009-12-10 00:07:07.0
-0500
+++ /usr/local/ports/mail/p5-qpsmtpd/files/qpsmtpd.in 2009-12-31
18:13:14.0 -0500
@@ -1,100 +1,56 @@
#!/bin/sh
+# $FreeBSD$
+#
# PROVIDE: qpsmtpd
-# REQUIRE: NETWORKING SERVERS
-# BEFORE: securelevel
+# REQUIRE: LOGIN
+# KEYWORD: shutdown
+#
+# Add the following lines to /etc/rc.conf.local or /etc/rc.conf
+# to enable this service:
+#
+# qpsmtpd_enable (bool): Set to NO by default
+# Set it to YES to enable qpsmtpd
+# qpsmtpd_user (string): Set to "nobody" by default
+# The user to run qpsmtpd-forkserver as
+# qpsmtpd_group (string): Set to "nogroup" by default
+# The group the pid dir will be chowned to
+# qpsmtpd_port (int): Set to 2525 by default
+# The port it should listen on
+# qpsmtpd_max_per_ip (int):Set to 3 by default
+# Max connections per IP
+# qpsmtpd_max_connections (int): Set to 15 by default
+# Maximum total connections
+# qpsmtpd_listen_on (address): Set to 0.0.0.0 by default
+# IP address to listen on
-#variables
-#qpsmtpd_user = the user to run qpsmtpd-forkserver under
-#qpsmtpd_group = the group the pid dir will be chowned to
-#qpsmtpd_port = the port it should listen on
-#qpsmtpd_max_per_ip = max connections per IP
-#qpsmtpd_max_connections = maximum total connections
-#qpsmtpd_listen_on = IP to listen on
-
-. "/etc/rc.subr"
+. /etc/rc.subr
name="qpsmtpd"
rcvar=`set_rcvar`
-load_rc_config $name
command="%%PREFIX%%/bin/qpsmtpd-forkserver"
+command_interpreter=%%PERL%%
pidfile="/var/run/qpsmtpd/qpsmtpd.pid"
-start_precmd="start_precmd"
-start_cmd="start_cmd"
-stop_cmd="stop_cmd"
+start_precmd=${name}_prestart
-start_precmd()
+qpsmtpd_prestart()
{
-#exits if no user is specified
-if [ -z $qpsmtpd_user ]; then
- echo "qpsmtpd_user not set"
- exit 1
-fi
-
-#exits if no group is specified
-if [ -z $qpsmtpd_group ]; then
- echo "qpsmtpd_group not set"
- exit 1
-fi
-
-#sets it to the default if the port is not specified
-if [ -z $qpsmtpd_port ]; then
- qpsmtpd_port="2525"
-fi
-
-#set it to the default max per ip
-if [ -z $qpsmtpd_max_per_ip ]; then
- qpsmtpd_max_per_ip="5"
-fi
-
-#set it do the max number of connections total
-if [ -z $qpsmtpd_max_connections ]; then
- qpsmtpd_max_connections="15"
-fi
-
-#set the default listen on to everything
-if [ -z $qpsmtpd_listen_on ]; then
- qpsmtpd_listen_on="0.0.0.0"
-fi
-
-if [ ! -d /var/run/qpsmtpd/ ] ; then
- mkdir /var/run/qpsmtpd
-fi
-
-chown $qpsmtpd_user:$qpsmtpd_group /var/run/qpsmtpd
+ [ -d /var/run/qpsmtpd ] || mkdir /var/run/qpsmtpd
+ chown $qpsmtpd_user:$qpsmtpd_group /var/run/qpsmt
Re: Recent massive port update.
Hi, jhell wrote: > > On Fri, 5 Feb 2010 17:50, ertr1013@ wrote: > > On Fri, Feb 05, 2010 at 06:25:42PM +0300, cvs-...@yandex.ru wrote: > >> Fetching 4282 patches. > > I could have swore that I recently heard an announcement that barred this > type of activity until after 7.3-RELEASE was made > The only "no sweeping changes" announcement I've seen regarding 7.3 was the recent doc freeze, not anything regarding ports. Regards, -- Glen Barber ___ 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"
Re: Call for testers: www/shellinabox (Shell in a Box)
On 6/24/10 6:51 PM, Olivier Cochard-Labbé wrote: Hi all, I've just finished my port of Shell in a Box: It's a secure web server that provide ajax terminal emulator. More information on the official website: http://code.google.com/p/shellinabox/ Before to submit it, Can someone test it ? You can found the port here: http://gugus69.free.fr/tools/shellinabox.tgz Here is how to proceed: cd /usr/ports/www fetch http://gugus69.free.fr/tools/shellinabox.tgz tar zxvf shellinabox.tgz cd shellinabox make install clean /usr/local/etc/rc.d/shellinaboxd onestart Then start your browser and connect to: https://127.0.0.1:4200 Cool stuff. Builds/runs fine on: FreeBSD orion 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #2 r209399: Mon Jun 21 20:36:54 EDT 2010 r...@orion:/usr/obj/usr/src/sys/ORION amd64 Safari doesn't play nice with it, but neat little tool. -- Glen Barber ___ 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"
Re: meta port issue
Hi Richard, On 7/8/10 4:26 PM, Richard E,. Neese wrote: Following is not happening I have a meta port of /usr/ports/net/freeswitch wich builds and installs other freeswitch ports of -core -sounds -music if you type make in the meta port it is not calling up the options screens for the other ports. but if you go into the other ports of freeswitch-core -sounds -music and type make the options screens come up fine. it seems that meta porta are broken in the mk files You can use 'make config-recursive' to display all the configuration option screens. -- Glen Barber ___ 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"
Re: meta port issue
On 7/8/10 5:56 PM, Doug Barton wrote: On Thu, 8 Jul 2010, Glen Barber wrote: Hi Richard, On 7/8/10 4:26 PM, Richard E,. Neese wrote: Following is not happening I have a meta port of /usr/ports/net/freeswitch wich builds and installs other freeswitch ports of -core -sounds -music if you type make in the meta port it is not calling up the options screens for the other ports. but if you go into the other ports of freeswitch-core -sounds -music and type make the options screens come up fine. it seems that meta porta are broken in the mk files You can use 'make config-recursive' to display all the configuration option screens. The fact that you can work around it doesn't mean that it's not a bug. :) I agree. I didn't have a chance to look further into it at the time, and knew -recursive would work in this situation. :) -- Glen Barber ___ 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"
Re: security/clamav: Segmentation fault when running clamav in a 32-bit jail on a 64-bit host
On 8/27/10 12:33 PM, Kurt Jaeger wrote: > Hi! > >> I have a few clamav instances running in jails on 32-bit hosts without >> any issues. A few days ago one of these jails was migrated to a 64-bit >> host (8.1-RELEASE), where I noticed clamd (0.96.2_1) segfaults when queried. >> >> The issue seems specific to 32bit/64bit compatibility. I have a gdb >> session available here: http://gist.github.com/549964 >> >> Any thoughts on if this is possible? > > Try > > Bytecode no > > in clamd.conf ? > It was set to 'yes' initially. I thought it was disabled with building without JIT. At any rate, no, it still segfaults with the same backtrace. Regards, -- Glen Barber ___ 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"
security/clamav: Segmentation fault when running clamav in a 32-bit jail on a 64-bit host
Hello, I have a few clamav instances running in jails on 32-bit hosts without any issues. A few days ago one of these jails was migrated to a 64-bit host (8.1-RELEASE), where I noticed clamd (0.96.2_1) segfaults when queried. The issue seems specific to 32bit/64bit compatibility. I have a gdb session available here: http://gist.github.com/549964 Any thoughts on if this is possible? Regards, -- Glen Barber ___ 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"
Re: security/clamav: Segmentation fault when running clamav in a 32-bit jail on a 64-bit host
On 8/27/10 12:54 PM, Jeremy Chadwick wrote: > On Fri, Aug 27, 2010 at 12:46:48PM -0400, Glen Barber wrote: >> On 8/27/10 12:33 PM, Kurt Jaeger wrote: >>> Hi! >>> >>>> I have a few clamav instances running in jails on 32-bit hosts without >>>> any issues. A few days ago one of these jails was migrated to a 64-bit >>>> host (8.1-RELEASE), where I noticed clamd (0.96.2_1) segfaults when >>>> queried. >>>> >>>> The issue seems specific to 32bit/64bit compatibility. I have a gdb >>>> session available here: http://gist.github.com/549964 >>>> >>>> Any thoughts on if this is possible? >>> >>> Try >>> >>> Bytecode no >>> >>> in clamd.conf ? >>> >> >> It was set to 'yes' initially. I thought it was disabled with building >> without JIT. At any rate, no, it still segfaults with the same backtrace. > > 1) Is clamd built with debugging symbols enabled? If not, you might want > to rebuild it with such, else it might be difficult to debug the > problem. > It wasn't initially, but is now. > Also, if the segfault happens after performing the above, can you > provide output from "bt full" instead of just "bt"? > Of course. The new backtrace is here: http://gist.github.com/553734 > 2) Was the software rebuilt from source after the upgrade from i386 to > amd64, or are you expecting the software to work without any hitches > running on amd64 with lib32 (32-bit compatibility libaries)? The latter > is not always possible/the case. > clamav was rebuilt from ports. I previously went as far as downgrading to the previous version, to rule out something between 0.96.1 and 0.96.2; same results there. > I have no familiarity with the software or functions in question, but an > initial guess would be that some piece of the code is making assumptions > about the size of pointers (expecting 4 (32-bit) rather than 8 > (64-bit)). Speculative on my part, but I ponder such when seeing code > like somefunc(sizeof(int)). > Thanks and regards, -- Glen Barber ___ 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"
Re: security/clamav: Segmentation fault when running clamav in a 32-bit jail on a 64-bit host
On 8/27/10 1:32 PM, Jeremy Chadwick wrote:
>> Of course. The new backtrace is here: http://gist.github.com/553734
>
> I want to make sure I understand the environment -- on a native i386
> (32-bit) FreeBSD host, the software works fine. But on a native amd64
> (64-bit) FreeBSD host, the software segfaults. Correct?
>
The clamav instance runs on a 64-bit host in a 32-bit jail. In a 32-bit
host/32-bit jail environment, the software runs fine, as you suggest above.
> If so -- it appears as if the system you're providing the backtrace from
> is a 32-bit system, or within a 32-bit environment? I would expect to
> see 64-bit addresses in the backtrace, yet they're all 32-bit.
>
> I'm not familiar with jailed environments (or the concept/possibility of
> running a mixed-architecture jail (e.g. 64-bit host OS with 32-bit
> jails)). I don't use lib32 on my amd64 systems.
>
To be honest, this is the first non-base software I've had an issue with
in a mixed-arch environment.
> I did take a look at the clamav code itself (I'd have to spend a few
> hundred lines outlining it here and would rather not). My guess is that
> there's a conflict between what the running OS architecture is and what
> the build process determines the architecture is.
>
> Given that you have jails, and possibly a mixed architecture environment
> on a single host (e.g. 64-bit host OS with 32-bit jails), can you
> explain exactly how you go about building clamav, followed by how you go
> about running it?
>
The build is done from ports with no special options excluding the
latest build, being:
make -DWITH_DEBUG DEBUG_FLAGS=-g
The only make.conf entry is PERL_VERSION=5.10.1.
The clamd service runs under djb's supervise (/usr/local/sbin/clamd).
Additionally, port builds were done after setting UNAME_m and UNAME_p
[1], but I haven't had luck with that overriding the machine hardware type.
If this provides any clues, here's what file(1) sees, as well as ldd:
% file /usr/local/sbin/clamd
/usr/local/sbin/clamd: ELF 32-bit LSB executable, Intel 80386, version 1
(FreeBSD), dynamically linked (uses shared libs), for FreeBSD 8.1, not
stripped
% ldd /usr/local/sbin/clamd
/usr/local/sbin/clamd:
libclamav.so.7 => /usr/local/lib/libclamav.so.7 (0x280ac000)
libz.so.5 => /lib/libz.so.5 (0x281f8000)
libbz2.so.4 => /usr/lib/libbz2.so.4 (0x2820a000)
libm.so.5 => /lib/libm.so.5 (0x2821b000)
libthr.so.3 => /lib/libthr.so.3 (0x28235000)
libc.so.7 => /lib/libc.so.7 (0x2824a000)
[1] - http://www.mail-archive.com/freebsd-am...@freebsd.org/msg00248.html
Cheers,
--
Glen Barber
___
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"
Re: security/clamav: Segmentation fault when running clamav in a 32-bit jail on a 64-bit host
On 8/27/10 2:20 PM, Jeremy Chadwick wrote: >> To be honest, this is the first non-base software I've had an issue with >> in a mixed-arch environment. > > Okay, so it's sort of what I thought. Your system has a series of > include files on it that are for amd64 (64-bit), but clamav, when built > within a 32-bit jail on that system, is (probably -- no proof, but it's > an educated guess based on what's happening) detecting some 64-bit > pieces through include files and making some incorrect assumptions about > the size of some types. > > I'd really need to set up a testbed system/VM and get full instructions > from start to finish on how to set up a 32-bit jail and so on, given > that I've never done it. Otherwise, you're probably going to need to > find someone who has a similar setup and can reproduce the problem, or > give a developer root-level access to your system. > I've also posted to the clamav-users@ list (but it was the backtrace before -DWITH_DEBUG was set), but haven't had a reply. Unfortunately, this particular setup, I can't provide root access, however I might be able to do so on one of my personal machines. It will be some time before I get everything set up properly though. [snip] > > I'm not sure how to explain this in a way that's easily understandable > (I'm assuming you're not a programmer. :-) ). My guess is that during > compile-time, the compiler is kicking out some code that's based on > sizeof(int) == 8 (64-bit), when that shouldn't be the case in a 32-bit > environment. Include files could cause this problem too. > Not a C programmer. :-) > There may be some "black magic" in the ports infrastructure (maybe even > on a per-port basis) to work around this problem that the clamav port > isn't making use of. I really don't know. > > Sorry I can't be of more help. I'm one of those guys who if he needs a > 32-bit and 64-bit system, buys two physical systems. > No problem. I appreciate you taking the time to look at it this far. Cheers, -- Glen Barber ___ 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"
Re: security/clamav: Segmentation fault when running clamav in a 32-bit jail on a 64-bit host
Hello Kostik, On 8/27/10 2:58 PM, Kostik Belousov wrote: >> Of course. The new backtrace is here: http://gist.github.com/553734 > > I suspect that this was fixed in r210796/HEAD and r211138/RELENG_8. > I will check this out on a test machine. Thanks. >> >>> 2) Was the software rebuilt from source after the upgrade from i386 to >>> amd64, or are you expecting the software to work without any hitches >>> running on amd64 with lib32 (32-bit compatibility libaries)? The latter >>> is not always possible/the case. >>> >> >> clamav was rebuilt from ports. I previously went as far as downgrading >> to the previous version, to rule out something between 0.96.1 and >> 0.96.2; same results there. > > Was clamav rebuilt in the 32-bit jail ? At least your backtrace shows > 32-bit image being executed. > Yes, this is correct. Thanks again, -- Glen Barber ___ 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"
Re: security/clamav: Segmentation fault when running clamav in a 32-bit jail on a 64-bit host
On 8/27/10 3:26 PM, Miroslav Lachman wrote: > Can you try it with original clamav 32-bit binary package? > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.1-release/Latest/clamav.tbz > > (or can you build your own on real 32-bit system instead of 32-bit jail > on 64-bit host?) > I've tried that already, unfortunately. Same result. Regards, -- Glen Barber ___ 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"
Re: security/clamav: Segmentation fault when running clamav in a 32-bit jail on a 64-bit host
On 8/27/10 5:03 PM, Paul Macdonald wrote: > On 27/08/2010 20:53, Glen Barber wrote: >> On 8/27/10 3:26 PM, Miroslav Lachman wrote: >>> Can you try it with original clamav 32-bit binary package? >>> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.1-release/Latest/clamav.tbz >>> >>> >>> (or can you build your own on real 32-bit system instead of 32-bit jail >>> on 64-bit host?) >>> >> I've tried that already, unfortunately. Same result. >> >> Regards, >> > > On 27/08/2010 12:39, Frank Wall wrote: >> Hi, >> >> I'm experiencing problems running ClamAV 0.96.2 on FreeBSD 7.1 (i386). >> The clamd will stop working immediately after startup. The process >> is still there, but unresponsive: >> >> > > i had something similar and eventually found that disabling JIT > Bytecode compiler option, returned it to being stable. > This only happened on one of my boxes though so i figured it was 'me'. > > Paul. > > > you've tried this yeah? Yes. -- Glen Barber ___ 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"
Re: security/clamav: Segmentation fault when running clamav in a 32-bit jail on a 64-bit host
On 8/27/10 3:04 PM, Glen Barber wrote: > Hello Kostik, > > On 8/27/10 2:58 PM, Kostik Belousov wrote: >>> Of course. The new backtrace is here: http://gist.github.com/553734 >> >> I suspect that this was fixed in r210796/HEAD and r211138/RELENG_8. >> > > I will check this out on a test machine. Thanks. > Hi Kostik, That was it. Thanks. -- Glen Barber ___ 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"
Re: vmware-guestd6: error during make install
Hi, On 9/3/10 4:31 AM, Matthias Apitz wrote: >>> I'm trying to install the port /usr/ports/emulators/vmware-guestd6 (even >>> the freshest from FreeBSD server) in 8-CURRENT: >> >> Do you have a particular reason for using this port? Assuming you mean >> 8.X, > > My FreeBSD is a CVS 8-CURRENT from May 2009 to be exactly, i.e. after > 8-RELEASE but before 8.1. > 9-CURRENT was after 8.0-RELEASE. Can you provide the output of 'uname -a'? Regards, -- Glen Barber ___ 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"
Re: Where did sunbird go?
Hi Robert, On 9/11/10 2:02 PM, Robert wrote: > Greetings > > I updated my ports today and "deskutils/lightning" was install and > sunbird is gone. I see nothing listed in "UPDATING" and the mozilla > site still show a download for sunbird. > > Did I miss something or is sunbird no longer available? > /usr/ports/MOVED shows this: deskutils/sunbird|deskutils/lightning|2010-09-07|Upstream development discontinued Meaning, sunbird was moved to lightning. Regards, -- Glen Barber ___ 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"
Re: Web feed for /usr/ports/UPDATING
On 9/23/10 11:39 PM, Alexander Kojevnikov wrote: > Hi list, > > Since the only SUBJ I could find [0] is long since dead I created my own: > > http://updating.versia.com/ > > Any feedback is welcome. > Great idea! -- Glen Barber ___ 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"
Re: Idea: entries in UPDATING for each release
On 9/28/10 2:07 PM, Warren Block wrote: > Right now, people who install ports from a -release CD and then start > upgrading don't have a clear marker for how far back to go in UPDATING. > +1 > A simple entry would be enough: > > 20100703: > AFFECTS: > AUTHOR: > > FreeBSD 8.1-RELEASE > > Not sure what AFFECTS should say. There might be other useful > information that could be included in the note. Comments? Maybe the AFFECTS line can be left out completely, and just state FreeBSD X.Y-RELEASE. Regards, -- Glen Barber ___ 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"
Re: Problem (again) with portsnap5.FreeBSD.org?
On 10/20/10 7:14 PM, Chip Camden wrote: > Quoth Barbara on Wednesday, 20 October 2010: >> >> My only intention was to report that and not complaining about the annoyance. >> I just wanted to alter people maintaining #5. >> If it's "expected", no problem. >> > > Was "alter" a parapraxis? > I'd imagine 's/alter/alert/'. Cheers, -- Glen Barber ___ 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"
Re: configure options
On 9/2/11 7:01 AM, Anton Shterenlikht wrote:
> I'm having problems building www/firefox on ia64.
> I was advised to:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=683879
>
> --- Comment #3 from Boris Zbarsky (:bz) 2011-09-01
> 10:36:27 PDT ---
> Do things work if you do use --disable-ipc?
>
> --
>
> How should I specify this option within
> the ports framework? Should it be something
> like
> make disable-ipc=yes
>
No, it would need to be specified in the port's Makefile. I haven't
tried it, but the attached patch may work. (Again, I haven't tried it.) :)
Regards,
--
Glen Barber
--- /usr/ports/www/firefox/Makefile 2011-08-31 17:26:12.0 -0400
+++ Makefile2011-09-02 07:30:47.330998597 -0400
@@ -49,6 +49,7 @@
--enable-application=browser \
--enable-official-branding --disable-updater \
--enable-canvas --enable-libxul --disable-necko-wifi \
+ --disable-ipc \
--with-system-libevent=${LOCALBASE}
OPTIONS= DBUS "Enable D-BUS support" on \
___
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"
Re: tinderbox: how to drop unneded Jail and Build
On 9/2/11 10:12 AM, Chris Rees wrote: > Any docs people happy to attempt to migrate the build system for the > Tinderbox README to FreeBSD-doc format? I'm pretty sure marcus would > rather keep it where it is; it's an upstream thing rather than an OS > thing. > I'll be happy to help. -- Glen Barber ___ 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"
Re: editors/zim
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 tree may be out of sync. MD5 distfile validation was removed from ports some time ago. How do you update your ports tree? Regards, Glen -- Glen Barber ___ 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"
Re: sysutils/cfs
On 9/7/11 9:28 PM, Julian H. Stacey wrote: >> And what we have been trying to explain to you is that this has never >> been a supported mode of operation. We don't tie the ports tree to >> specific releases, > > FreeBSD doese "tie the ports tree to specific releases". We have ports > freezes before each release, it gets tagged & goes on cdrom images, > packages get rolled. (Yes, Not quite the same as src/ ) > Packages are tied to a specific release (and are distributed with said release). Ports are not. -- Glen Barber ___ 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"
Re: Standalone mksh
On 9/9/11 9:48 PM, Chris Brennan wrote: > On 9/9/2011 7:35 AM, Aioanei Rares wrote: >> Attached is the modified Makefile. >> >> Thanks, > > Aioanei, > No attachment, I think it got filtered out by the list. > I received the Makefile. -- Glen Barber ___ 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"
Re: ports-system priorities rant (Re: sysutils/cfs)
On 9/13/11 4:52 PM, Chris Rees wrote: > I'm rather tired of being called to defend myself, I see no reason why you should find it necessary. Bravo for the work you've done. > I've plenty of better things to be doing. > Agreed. Julian, amongst others this past few weeks, have successfully made it indefinitely to my bit bucket. I suggest you do the same, and take the advice of /etc/motd: Shut Up and Code!!! :-) -- Glen Barber | g...@freebsd.org FreeBSD Documentation Project ___ 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"
Does anyone use mail/demime
Hi, As it stands now, the mail/demime port has no "upstream", and development seems to have stopped at least 2 years ago. Does anyone use this? If so, would someone like to _become_ "upstream" and revive this piece of software? Otherwise, I'll mark this port as deprecated in 1 week and have it scheduled for removal 1 month afterwards. Thanks. -- Glen Barber ___ 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"
Re: Does anyone use mail/demime
On 10/17/11 4:19 PM, Ruslan Mahmatkhanov wrote: > Matthias Andree wrote on 18.10.2011 00:14: >> Am 17.10.2011 04:00, schrieb Glen Barber: >>> Hi, >>> >>> As it stands now, the mail/demime port has no "upstream", and >>> development seems to have stopped at least 2 years ago. >>> >>> Does anyone use this? >>> >>> If so, would someone like to _become_ "upstream" and revive this piece >>> of software? >>> >>> Otherwise, I'll mark this port as deprecated in 1 week and have it >>> scheduled for removal 1 month afterwards. >> >> Do we have a suitable alternative that we can recommend? > I don't see one in the Ports tree, but there may be something better that just had not been ported. To be honest, this is part of why I asked if anyone uses it. > maildrop, that was often mentioned on official site: > http://wayback.archive.org/web/*/http://scifi.squawk.com/demime.html > Active development has clearly ceased. -- Glen Barber ___ 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"
Re: Does anyone use mail/demime
On 10/17/11 6:04 PM, Glen Barber wrote: >> maildrop, that was often mentioned on official site: >> http://wayback.archive.org/web/*/http://scifi.squawk.com/demime.html >> > > Active development has clearly ceased. > I misread your reply initially, I think. Sorry about that. -- Glen Barber ___ 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"
Re: Alpine mail client discontinued?
On 10/24/11 5:49 AM, Gautam wrote: > On Mon, Oct 24, 2011 at 2:41 AM, Sean C. Farley wrote: > >> >> On 10/16/2011 15:49, Ted Hatfield wrote: >>> >>>> >>>> re-alpine >>>> >>>> >>>> Of course, this could (should?) wait until 9 is out the door. >> >> >> Alpine is also documented in the handbook > http://www.freebsd.org/doc/handbook/mail-agents.html ; so that also should > be updated. > Does the way in which re-alpine is used differ? If so, the Handbook can be updated if/when alpine is replaced with re-alpine, that's not a problem. I suspect, based on this thread, it won't be necessary other than noting the port is mail/re-alpine instead of mail/alpine. The Documentation people would be happy to update the alpine section in the Handbook in either case. Though, not all doc people are subscribed to ports@ - can someone ping us if/when re-alpine is in the tree as a replacement? -- Glen Barber | g...@freebsd.org FreeBSD Documentation Project ___ 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"
Re: "postfix-current" broken on amd64 platform
On Mon, Nov 14, 2011 at 09:24:30PM -0500, Sahil Tandon wrote:
> [ pav@ and those who tested mail/postifx-current on amd64 added to Cc: ]
>
> On Mon, 2011-11-14 at 08:37:13 -0500, Jerry wrote:
>
> > The "postfix-current" port is still marked as broken:
> >
> > .if ${ARCH} == "amd64"
> > BROKEN= fails during installation
> > .endif
> >
> > Since all previous releases of Postfix worked on FreeBSD, and since
> > Postfix is/was developed on FreeBSD, I was wondering what the problem
> > is with this release. Is there a possibility that this phenomena might
> > be rectified in the near future?
>
> Thanks for your report, Jerry. You are correct that FreeBSD is the main
> development platform for Postfix. It seems that pointyhat's amd64
> machine throws an error during the install phase. Pav noticed this and
> marked the port BROKEN; however, neither I nor a few others I've
> enlisted can reproduce the error. Would you mind removing the
> conditional that marks this port BROKEN, try to build/install in your
> amd64 environment, and report the results?
>
> Pav, if nobody else can reproduce the error seen on pointyhat, can
> portmgr look into whether there is something quirky with the amd64
> pointyhat machine?
>
I don't have the successful build logs anymore, so I've just re-queued a
build of postfix-current on 9-STABLE (-RC2) amd64 in my tinderbox if
the results are of interest to those that can investigate any potential
pointyhat anomalies.
Regards,
Glen
--
Glen Barber | g...@freebsd.org
FreeBSD Documentation Project
pgpY4wWj429FM.pgp
Description: PGP signature
Re: "postfix-current" broken on amd64 platform
On Wed, Nov 16, 2011 at 10:28:03AM +0100, Pav Lucistnik wrote: > Is it a clever idea to hardcode local interfaces on build machine into a > package that will then be redistributed to other machines? > Am I misunderstanding something, or is this a local configuration script that customizes the installation for the target machine in a similar way the mai/qmail port runs post-install 'config/config-fast' scripts to identify the system hostname (which then populates the 'me' file, for example)? -- Glen Barber pgpLdYXoIPYiY.pgp Description: PGP signature
Re: More lame portmgr poetry
Hmm.. Why does portmgr get to have all the fun? :) freefall-in' Apologies to: Tom Petty, Jeff Lynne It was a long day, been workin' too long. I should be sleeping, but after this change. I can fix this, it won't take much time. But I've been staring at this Makefile too long... And I'm free... freefall-in' Yeah, I'm free... freefall-in' portmgr@ warned me, about makin' this change. There's a ports freeze, don't want disruption. But I don't listen, it should be Feature Safe. Plus they're busy, they won't notice this change. And I'm free... freefall-in' Yeah, I'm free... freefall-in' Here comes Pav-mail, just as I log out. pointy-hat's unhappy, it can't apply a patch. I'm a bad boy, for not tinderboxin'. I'm a bad boy, for breaking that port. Now I'm free... freefall-in' Yeah, I'm free... freefall-in' -- Glen pgpoobr2xw3DN.pgp Description: PGP signature
Re: More lame portmgr poetry
On Fri, Dec 23, 2011 at 07:42:19PM -0500, Eitan Adler wrote: > On Fri, Dec 23, 2011 at 4:45 PM, Glen Barber wrote: > > Hmm.. Why does portmgr get to have all the fun? :) > > Do we get to hear you both sing at this year's BSDCAN? I'm quite certain none of us want that. Glen pgpLsXSNJU3Y6.pgp Description: PGP signature
Anyone interested in taking over games/robocode
Hi porters, I've recently lost the spare cycles to keep this port happy in my tinderbox (Java updates, manually fetching stuff, etc). I'd prefer not to reset maintainership to ports@; anyone interested in taking this? -- Glen Barber ___ 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"
Re: cvs commit: ports UPDATING
On 6/30/11 11:22 PM, Doug Barton wrote: > This is not the first time this issue (ports doing the wrong thing if > you try to build them while they are installed) has come up, and I've > been thinking ... do we need something like a NO_REINSTALL flag that can > be added to a port's Makefile to indicate the problem? I realize that in > many cases the problem is better solved by fixing the real problem. > However I think that there are likely situations like this where there > is a legitimate problem that can only be overcome by removing the > installed ports first. > I think it would be nice to have a "I_KNOW_I_HAVE_THIS_PORT_INSTALLED_ALREADY_BUT_UPGRADE_IT_ANYWAY" flag for situations that seem to be what caused this reply, unless I misunderstand the cause of the UPDATING entry. In either case, see below. More specifically, I think it would be nice if 'PACKAGE_SITE=$mylocaltinderbox pkg_add ' didn't complain that I already have a prerequisite packages, though lesser-versioned that is required for installed currently, while failing to upgrade the prerequisite package when I know it's necessary for the upgrade. Maybe I've missed various flags in various manual pages - I would be thrilled to be proven that this is the case. -- Glen Barber ___ 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"
[Request for Comments] Adding a JAILED meta-variable to bsd.port.mk
Hi,
I would like to propose a change to bsd.port.mk which, similarly to
obtaining the OSVERSION, checks if the system on which a port is being
built is a jailed environment.
This change can allow port maintainers to mark ports that do not run in
jailed environments as IGNORE, or adjust PKG_MESSAGE to inform the user
of special conditions or changes that will be needed to run a port from
within a jail. One particular example of the latter is
databases/postgresql*-server, where the user must enable
security.jail.sysvipc_allowed. I am sure this feature could expand to
other cases I have not considered yet, as well.
I have included three patches:
0-Mk-bsd.port.mk.txt - the proposed change to bsd.port.mk
1-ircservices-Makefile.txt - an example usage of disallowing a port from
being built within a jail
2-sshguard-Makefile.txt - an example usage of disabling a port from
being built within a jail conditionally (in this example, it is assumed
security/sshguard-pf is the target port)
Comments, etc, are welcome.
Regards,
Glen
--
Glen Barber | g...@freebsd.org
FreeBSD Documentation Project
--- bsd.port.mk.orig2011-08-12 12:39:23.0 -0400
+++ bsd.port.mk 2011-08-20 06:15:19.644576050 -0400
@@ -46,6 +46,7 @@
#"FreeBSD," "NetBSD," or "OpenBSD" as
appropriate.
# OSREL- The release version (numeric) of the
operating system.
# OSVERSION- The value of __FreeBSD_version.
+# JAILED - The system is a FreeBSD jail.
#
# This is the beginning of the list of all variables that need to be
# defined in a port, listed in order that they should be included
@@ -1196,6 +1197,11 @@
.endif
.endif
+# Check if the system is a jail
+.if !defined(JAILED)
+JAILED!= ${SYSCTL} -n security.jail.jailed
+.endif
+
MASTERDIR?=${.CURDIR}
.if ${MASTERDIR} != ${.CURDIR}
--- Makefile.orig 2009-08-31 09:50:55.0 -0400
+++ Makefile2011-08-20 06:14:04.987796133 -0400
@@ -27,6 +27,10 @@
.include
+.if ${JAILED}
+IGNORE=Does not run from within a jail
+.endif
+
.if ${OSVERSION} > 700042
CFLAGS+= -fno-stack-protector
.endif
--- Makefile.orig 2011-07-24 14:16:29.0 -0400
+++ Makefile2011-08-20 06:14:24.513106022 -0400
@@ -40,6 +40,9 @@
CONFIGURE_ARGS+= --mandir=${MANPREFIX}/man
.if ${SSHGUARDFW} == pf
+. if ${JAILED}
+IGNORE=Cannot use with pf within a jail
+. endif
PKGMSG_FWBLOCK=" To activate or configure PF see
http://sshguard.sf.net/doc/setup/blockingpf.html";
.elif ${SSHGUARDFW} == ipfw
PKGMSG_FWBLOCK=" Verify that IPFW is active with \"ipfw show\"."
signature.asc
Description: OpenPGP digital signature
Re: [Request for Comments] Adding a JAILED meta-variable to bsd.port.mk
On 8/20/11 7:52 AM, Kostik Belousov wrote:
> On Sat, Aug 20, 2011 at 07:09:49AM -0400, Glen Barber wrote:
>> Hi,
>>
>> I would like to propose a change to bsd.port.mk which, similarly to
>> obtaining the OSVERSION, checks if the system on which a port is being
>> built is a jailed environment.
>>
>> This change can allow port maintainers to mark ports that do not run in
>> jailed environments as IGNORE, or adjust PKG_MESSAGE to inform the user
>> of special conditions or changes that will be needed to run a port from
>> within a jail. One particular example of the latter is
>> databases/postgresql*-server, where the user must enable
>> security.jail.sysvipc_allowed. I am sure this feature could expand to
>> other cases I have not considered yet, as well.
>
> I do not think this is good idea. The machine or environment where
> the port is built sometimes (or, in my setups, quite often) is not
> the same as where it is run. Your proposal gives a tool to tightly
> tie the ports to build environments, that is detrimental for some
> setups, and also diminish the value of packaging. IMHO.
Hi Kostik,
Thank you for the comments.
I had neglected that some package building environments are jails with
the intent to install the packages on physical hardware or other
non-jailed environment, so this change would break those environments.
I had only tested the patches in a tinderbox environment.
One thing I can think of off-hand to fix this in that case is setting a
local environment variable to disable a check for security.jail.jailed.
Would this be an ok solution for those cases? If not, I happily agree
that this change should not be made then.
I have an updated patch to bsd.port.mk that looks for a local
environment variable, PKGJAIL - if it is set, then JAILED is unset.
Would this be acceptable?
Regards,
Glen
--
Glen Barber | g...@freebsd.org
FreeBSD Documentation Project
--- bsd.port.mk.orig2011-08-12 12:39:23.0 -0400
+++ bsd.port.mk 2011-08-20 08:07:12.656834897 -0400
@@ -46,6 +46,7 @@
#"FreeBSD," "NetBSD," or "OpenBSD" as
appropriate.
# OSREL- The release version (numeric) of the
operating system.
# OSVERSION- The value of __FreeBSD_version.
+# JAILED - The system is a FreeBSD jail.
#
# This is the beginning of the list of all variables that need to be
# defined in a port, listed in order that they should be included
@@ -1196,6 +1197,15 @@
.endif
.endif
+# Check if the system is a jail
+.if !defined(JAILED)
+. if !defined(PKGJAIL)
+JAILED!= ${SYSCTL} -n security.jail.jailed
+. else
+JAILED=
+. endif
+.endif
+
MASTERDIR?=${.CURDIR}
.if ${MASTERDIR} != ${.CURDIR}
signature.asc
Description: OpenPGP digital signature
Re: [Request for Comments] Adding a JAILED meta-variable to bsd.port.mk
On 8/20/11 8:44 AM, Kostik Belousov wrote: >> One thing I can think of off-hand to fix this in that case is setting a >> local environment variable to disable a check for security.jail.jailed. >> Would this be an ok solution for those cases? If not, I happily agree >> that this change should not be made then. >> >> I have an updated patch to bsd.port.mk that looks for a local >> environment variable, PKGJAIL - if it is set, then JAILED is unset. >> Would this be acceptable? > The change would require user to do a configuration for a thing that > previously just worked. What is the point ? > I suppose the specific problem I am trying to solve is a case where a user builds a port within a jail with the expectation that the port will in fact run within the jail with little or no changes. Perhaps security/sshguard-pf and databases/postgresql*-server are not the most ideal examples of where this would be relevant. I agree that a configuration change for something that worked before is not the best solution. So, I retract this change proposal. Again, thank you for the feedback and pointing out that this would have had negative impact on those using jails for package building. Regards, Glen -- Glen Barber | g...@freebsd.org FreeBSD Documentation Project ___ 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"
Re: More lame portmgr poetry
On Mon, Dec 26, 2011 at 11:40:56AM -0500, Thomas Abthorpe wrote: > On Fri, Dec 23, 2011 at 08:46:06PM -0500, Glen Barber wrote: > > On Fri, Dec 23, 2011 at 07:42:19PM -0500, Eitan Adler wrote: > > > On Fri, Dec 23, 2011 at 4:45 PM, Glen Barber wrote: > > > > Hmm.. Why does portmgr get to have all the fun? :) > > > > > > Do we get to hear you both sing at this year's BSDCAN? > > > > I'm quite certain none of us want that. > > > > +1 > > I can't speak for Glen per se, but a chorus of chain saws sound better > than my singing :) > Well, in case there was interest, Thomas and I did sing a quick song together in the Hacker's Lounge during BSDCan. The YouTube link is here: https://www.youtube.com/watch?v=2Mb6w4q_Gb0 I hope it was as good as expected. Cheers, Glen ___ 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"
Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
On Sat, Aug 25, 2012 at 01:25:15AM +0100, Jonathan Anderson wrote: > On 24 Aug 2012, at 23:38, Doug Barton wrote: > > Let me rephrase that more simply ... very few users are ever going to > > need the bootstrapping tool that will be in the base. > So, then they won't use it. I fail to see the problem here. > But surely the whole point of pkgng is that people *will* use pkg > as the default method of acquiring third-party software, so they'll > want to "pkg install foo" and have it Just Work. To say either "you > must download the ports tree in order to use binary packages" or > "you must use pkg_add to install pkg" seems to miss the point... > /usr/sbin/pkg installs /usr/local/sbin/pkg without requiring the Ports Collection to be available locally. Glen pgp33mgeXS1QX.pgp Description: PGP signature
Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
On Sat, Aug 25, 2012 at 01:47:26AM +0100, Jonathan Anderson wrote: > On Saturday, 25 August 2012 at 01:33, Glen Barber wrote: > > On Sat, Aug 25, 2012 at 01:25:15AM +0100, Jonathan Anderson wrote: > > > On 24 Aug 2012, at 23:38, Doug Barton > > (mailto:do...@freebsd.org)> wrote: > > > > Let me rephrase that more simply ... very few users are ever going to > > > > need the bootstrapping tool that will be in the base. > > > > > > > > > So, then they won't use it. I fail to see the problem here. > > I also fail to see the problem. :) Just to be clear, my post was > arguing against Doug's assertion that few will use pkg's bootstrapper > (and that this is a problem): I hope that pkgng and package sets > will vastly increase the use of binary packages by FreeBSD consumers. > I was avoiding writing two separate emails about this thread - yes, I did realize we had a similar point of view on this. Sorry if it came out differently. > > /usr/sbin/pkg installs /usr/local/sbin/pkg without requiring the Ports > > Collection to be available locally. > > Which is exactly the behaviour that I want: I view the ports tree > as a last resort to be used only if binary packages fail to fulfil > my needs. Sometimes I don't even bother fetching it. Once again, > we may be in violent agreement here. :) > Understood. I misinterpreted your last sentence. What I would like to know, is why all the anti-progress emails[1] have to wait until the Last Minute(tm) when information on pkgng availability has been available for quite some time now. Welcome to 2012. [1] - Doing the same things we've done keeps us in the same place we've been. Glen pgpxZUyUkivgk.pgp Description: PGP signature
Re: Plugins support in pkgng
On Fri, Aug 31, 2012 at 06:27:09PM +0300, Vitaly Magerya wrote: > Marin Atanasov Nikolov wrote: > > This is just to share with you that soon after the official 1.0 > > release of pkgng we now have basic plugins support in pkgng's > > development branch. > > [...] > > It's not perfect or covering everything, but it will give you a quick > > start though :) > > How about the ability to add new commands to "pkg"? > For example something like "pkg cutleaves" via plugins would be cool. I think 'pkg autoremove' already does this. Glen pgpwxHdhAqOpU.pgp Description: PGP signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 03:44:21PM +0200, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. > Congratulations, and thank you for all of your hard work on this! Glen pgpyzUneqltJg.pgp Description: PGP signature
Re: Cannot upgrade ghostscript9.
On Thu, Oct 18, 2012 at 07:19:29PM +0200, Andrea Venturoli wrote: > On 10/18/12 18:10, Bryan Drewery wrote: > > On 10/18/2012 5:34 AM, Andrea Venturoli wrote: > >> Hello. > >> > >> I'm getting an error when I try to upgrade ghostscript9. > >> > >>> # uname -a > >>> FreeBSD xx.x 8.2-RELEASE-p8 FreeBSD 8.2-RELEASE-p8 #0: Thu May > >>> 31 17:47:40 CEST 2012 > >>> root@xx.x:/usr/obj/usr/src/sys/XX i386 > >>> # portversion -v | grep ghostscript > >>> ghostscript9-9.05_5 < needs updating (port has 9.06_1) > >> > >> Please find attached the output of "portupgrade ghostscript9". > >> All dependencies are up to date (I did "portupgrade -R" and even "-Rf" > >> before). > > > > I see no attached output here. > > Sorry, I'll try again without zipping it. > This is being looked into, and was reported via the PR system. Thank you for the report. Glen pgpkMWQv44zfi.pgp Description: PGP signature
Re: Updating "Bash"
On Tue, Jan 08, 2013 at 06:15:45AM -0800, David O'Brien wrote: > On Thu, Jan 03, 2013 at 08:32:49AM -0500, Jerry wrote: > > Bash is currently at Bash-Release: 4.2, patch level 42. The port's > > version is only at patch level 37, which was released on 16-Jul-2012. > > This is an important port and since the freeze is over with, I was > > wondering if this port will be updated? > > It will be once the dust settles over the 9.1 release. > I think the dust has settled. Glen pgpz2078U9NOj.pgp Description: PGP signature
Re: Updating "Bash"
On Tue, Jan 08, 2013 at 06:20:30PM -0500, Jerry wrote: > > > It will be once the dust settles over the 9.1 release. > > > > > > > I think the dust has settled. > > The dust never settles; it just gets swept under the rug. > Unhelpful response noted. Glen pgpaXN8t3T25q.pgp Description: PGP signature
Re: Updating "Bash"
On Sat, Jan 12, 2013 at 11:04:32AM +, Chris Rees wrote: > >> It will be once the dust settles over the 9.1 release. > > > > I think the dust has settled. > > I agree, but I'm not clear on what the "dust" was. > Same here. As I do not see any, I assume it has either settled or never existed at all. I like to refer to the phenomenon as "illuminatiware." Glen pgpCB1COqLqzs.pgp Description: PGP signature
Re: linux-ePSXe
On Fri, Dec 19, 2008 at 6:35 PM, Gonzalo Martínez-Sanjuan Sánchez wrote: > Hello! > > Would someone take care of the port emulators/linux-ePSXe? > Theres a new version since 8 months in their website: 1.7.0 > http://www.epsxe.com/ > > Thnx everybody for their work in freebsd ports tree. > Good thing I looked at the epsxe site before investigating my errors further... The 1.7.0 release is win32 only. -- Glen Barber ___ 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"
Re: linux-ePSXe
On Mon, Dec 22, 2008 at 10:16 AM, Sean McAfee wrote: > Boris Samorodov wrote: >> >> On Sat, 20 Dec 2008 00:35:33 +0100 Gonzalo Martínez-Sanjuan Sánchez wrote: >> >> This port is maintained by po...@freebsd.org. That is noone. Or >> if you wish that means all of us. As well as you. Hence you may >> contrubute to the project. Try it, it's not so hard: >> >> . change PORTVERSION at the makefile accordingly; >> . reset PORTREVISION (to zero or delete the line) at the makefile; >> . delete distinfo file; >> . fetch the new port (make fetch); >> . create a new distinfo (make makesum); >> . fix plist (linux ports tend to use PORTVERSION at directory names); >> . test building/installing/packageing/removing; >> . finally send a PR (send-pr). > > To add to that, the official documentation (and detailed instructions) can > be found in Chapter 10 of the Porter's Handbook: > http://www.freebsd.org/doc/en/books/porters-handbook/port-upgrading.html. > Oddly enough, I was looking at this port yesterday. I'm running test builds at the moment. If no one else wants maintanership of it, I'll take it. -- Glen Barber ___ 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"
Re: general ports problem
On Fri, Dec 26, 2008 at 5:02 PM, t-u-t wrote: > hi, > i have a quick question and don't know what this problem is related to. > > i am getting an error on *every* port i try to build -- Script "configure" > failed unexpectedly. etc,etc, please check log. > > searching the net i am finding pages on particular ports (not same as mine > yet) -- but baffled as to why every port giving this error. > > I have no clue what is in these log files and was wondering whether the > "unknown' entries is normal at "/bin/arch=" below. > > this below is the topmost part of config.log and just noticed the parts with > win32 and don't know what that means. > > the very last line in the log file reads configure. exit 77. > Is there anything odd in /etc/make.conf ? Are your ports up to date? -- Glen Barber ___ 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"
Re: math/R fails to build
On Tue, Jan 13, 2009 at 5:10 PM, Philipp Ost wrote: > Hi, > > math/R fails to build: > # make > [...] > cc -std=gnu99 -I. -I../../src/include -I../../src/include > -I/usr/local/include -DHAVE_CONFIG_H -fpic -O2 -fno-strict-aliasing -pipe > -march=athlon-xp -c Rmain.c -o Rmain.o > cc -std=gnu99 -export-dynamic -L/usr/local/lib -o R.bin Rmain.o -L../../lib > -lR > /usr/local/lib/libblas.so.2: undefined reference to > `_gfortran_runtime_error_at' > *** Error code 1 > > Stop in /usr/ports/math/R/work/R-2.8.1/src/main. > *** Error code 1 > > Stop in /usr/ports/math/R/work/R-2.8.1/src/main. > *** Error code 1 > > Stop in /usr/ports/math/R/work/R-2.8.1/src. > *** Error code 1 > > Stop in /usr/ports/math/R/work/R-2.8.1. > *** Error code 1 > > Stop in /usr/ports/math/R. > *** Error code 1 > > Stop in /usr/ports/math/R. > # > > I run RELENG_7 as of 23 Dec. 2008 (on i386). > > Any hints? (Apart from rebuilding blas, which I did. It didn't solve the > problem) > Is it a safe assumption that you have recently updated your ports tree? -- Glen Barber ___ 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"
Re: portmaster some_port vs. portmaster 'some_port*'
On Wed, Jan 14, 2009 at 1:39 PM, Ion-Mihai Tetcu wrote: > Hi, > > > Maybe I'm not reading the man page correctly, but I would expect > portmaster, if invoked with a wild-card, to: > - first update the dependencies of the ports matched by the 'some_port*' it > gets on the command line > - then to update the ports matched by said wild-card in dependency order. > > At least #1 above doesn't seem to happen for wild-card invocation, but > it happens when invoked with one or two ports: > http://people.tecnik93.com/~itetcu/FreeBSD/errors/portmaster/ > > Bug? Feature? :-) > If that were to work, I'd imagine the '*' wildcard would need to be escaped. IE: portmaster 'someport\*' Note: I do not use portmaster, so this is a guess, not a solution. -- Glen Barber ___ 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"
Re: X drivers depend on Gnome?
On Tue, Feb 3, 2009 at 2:03 PM, Alex Goncharov wrote: > I am slowly moving down the X ports dependency stack, trying to > understand what I should leave in a frozen state and what keep > upgrading. I know this isn't your real question in this thread, but for what it's worth, I've found that xorg-drivers, xorg-server, and xf86-*, when kept at the 'pkg_add' version provides me with a somewhat stable X. Just thought I'd provide this, in case you were still digging about at all. -- Glen Barber ___ 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"
Re: Xorg strange behavior
On Wed, Feb 4, 2009 at 8:13 AM, L Campbell wrote: > I experienced the same symptoms after the recent upgrade. I found that > rebuilding x11-servers/xorg-server without HAL fixed the problem. I > think there are a couple of other ways to fix it, but AFAIK the root > of the problem is HAL not playing nicely with other components (ie, > moused). Interestingly, this solution did *not* work for me yesterday. The only solution was to install the binary xorg-server and xorg-drivers. -- Glen Barber ___ 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"
Re: Xorg strange behavior
On Wed, Feb 4, 2009 at 2:07 PM, Jung-uk Kim wrote: > Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and > xorg-server-1.5.3_4,1, which I just committed. If the problem does > not go away, please send us /var/log/Xorg.0.log. > I, unfortunately, got tied up in a few things this evening. I'll build these tomorrow and provide feedback one way or another. Regards, -- Glen Barber ___ 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"
Re: Xorg strange behavior
Jung-uk Kim said: > Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and > xorg-server-1.5.3_4,1, which I just committed. If the problem does > not go away, please send us /var/log/Xorg.0.log. > I wish I could report success on this, but unfortunately, I cannot. Attached is my Xorg.0.log. Any other information I can provide, let me know, but I think I am going to stick with xorg-server from pkg_add for quite some time after this point. Regards, -- Glen Barber X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.1-PRERELEASE i386 Current Operating System: FreeBSD phoenix.local 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #0: Sun Feb 1 11:31:52 EST 2009 r...@phoenix.local:/usr/obj/usr/src/sys/PHOENIX i386 Build Date: 08 September 2008 12:37:00PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 5 20:15:36 2009 (EE) Unable to locate/open config file (II) Loader magic: 0x81ced80 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: "pcidata" (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.4.2, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000f908, mode1Res1 = 0x8000 (WW) OS did not count PCI devices, guessing wildly (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2590 card 1028,01c9 rev 03 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,2592 card 1028,01c9 rev 03 class 03,00,00 hdr 80 (II) PCI: 00:02:1: chip 8086,2792 card 1028,01c9 rev 03 class 03,80,00 hdr 80 (II) PCI: 00:1b:0: chip 8086,2668 card 1028,01c9 rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,2660 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:3: chip 8086,2666 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2658 card 1028,01c9 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2659 card 1028,01c9 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,265a card 1028,01c9 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:3: chip 8086,265b card 1028,01c9 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,265c card 1028,01c9 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card , rev d3 class 06,04,01 hdr 01 (II) PCI: 00:1f:0: chip 8086,2641 card 1028,01c9 rev 03 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,266f card 1028,01c9 rev 03 class 01,01,8a hdr 00 (II) PCI: 02:00:0: chip 14e4,170c card 1028,01c9 rev 02 class 02,00,00 hdr 00 (II) PCI: 02:03:0: chip 14e4,4318 card 1028,0005 rev 02 class 02,80,00 hdr 00 (II) PCI: End of PCI scan (II) Intel Bridge workaround enabled (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,12), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 11: bridge is at (0:28:0), (0,11,11), BCTRL: 0x0002 (VGA_EN is cleared) (II) PCI-to-PCI bridge: (II) Bus 12: bridge is at (0:28:3), (0,12,13), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 12 I/O range: [0] -1 0 0xd000 - 0xdfff (0x1000) IX[B] (II) Bus 12 non-prefetchable memory range: [0] -1 0 0xdfc0 - 0xdfdf (0x20) MX[B] (II) Bus 12 prefetchable memory range: [0] -1 0 0xd000 - 0xd01f (0x20) MX[B] (II) Subtractive PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:30:0), (0,2,2), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 2 non-prefetchable memory range: [0] -1 0 0xdfb0 - 0xdfbf (0x10) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:2:0) Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller rev 3, Mem @ 0xdff0/19, 0xc000/28, 0xdfec/18, I/O @ 0xeff8/3 (--) PCI: (0:2:1) Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller rev 3, Mem @ 0xdff8/19 New driver is "i810" (==) Using default built-in
Re: Xorg strange behavior
For what it's worth, adding 'option "AutoAddDevices" "off"' to xorg.conf enables the mouse, but the keyboard is still not functional. -- Glen Barber ___ 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"
Re: Xorg disaster
On Thu, Feb 5, 2009 at 10:51 PM, Alex Goncharov wrote: > The path is (roughly): > > 1. Find the dependencies of xproto and xextproto: > > pkg_info -R xproto-\* xextproto-\* | wc -l > > Prepare to remove those (new) packages from your system. > I, too, chose plan 'b'. However, I did it differently. After building Xorg, I removed xorg-server, xorg-drivers, and hal, and re-installed them w/ pkg_add. -- Glen Barber ___ 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"
Re: Call for potential ports maintainers
On Thu, Feb 12, 2009 at 12:32 PM, Thomas Abthorpe wrote: > The gauntlet has been thrown down, who among you is prepared to pick it up? I'll take the following: lang/open-cobol lang/tinycobol devel/c_c++_reference Should I submit a separate PR for each? -- Glen Barber ___ 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"
Re: Call for potential ports maintainers
On Thu, Feb 12, 2009 at 5:41 PM, Thomas Abthorpe wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On February 12, 2009 05:04:07 pm Glen Barber wrote: >> I'll take the following: >>lang/open-cobol >>lang/tinycobol >>devel/c_c++_reference >> >> Should I submit a separate PR for each? > > Thanks Glen > > In this case, a PR is not necessary, we will queue it up on our todo list. > Thanks. You can put me down for the following, if they aren't spoken for, also: databases/kmysqladmin palm/palmpower palm/palmos-sdk palm/prc-tools security/portsentry Regards, -- Glen Barber ___ 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"
Re: URLs to fetch packages are wrong
On Thu, Feb 19, 2009 at 4:29 PM, Yuri wrote: > When I do "portupgrade -aP" I get a lot of errors like this: > > fetch: > ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/kdepim-4.2.0_1.tbz: > No address record^M > ** The command returned a non-zero exit status: 1^M > ** Failed to fetch > ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/kdepim-4.2.0_1.tbz^M > fetch: > ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/kdepim-4.2.0_1.tgz: > No address record^M > ** The command returned a non-zero exit status: 1^M > ** Failed to fetch > ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/kdepim-4.2.0_1.tgz^M > > fetch: > ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/jdk-1.5.0.14p8_5,1.tbz: > No address record^M > ** The command returned a non-zero exit status: 1^M > ** Failed to fetch > ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/jdk-1.5.0.14p8_5,1.tbz^M > fetch: > ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/jdk-1.5.0.14p8_5,1.tgz: > No address record^M > Not sure if you're posting a question or an answer, based on how it's worded. :) If it is a question "why", the "/" between ".org" and "pub" is missing. -- Glen Barber ___ 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"
Re: URLs to fetch packages are wrong
On Thu, Feb 19, 2009 at 5:43 PM, Yuri wrote: > > I am sorry for the confusion. > > This is a question. > Why on the current 71-PRERELEASE ports there is no '/' in URLs? > Just a typo. Submit a PR. I'd do it for you, but I don't have access to a BSD box at the moment. -- Glen Barber ___ 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"
Re: "My race is just nothing": Some thoughts on the political psychology of women
On Fri, Feb 20, 2009 at 1:29 PM, Carlos A. M. dos Santos > Could somebody living in US please call Mr Auster and ask him to stop > sending his newsletter to this list? > Mark it as spam and move on. -- Glen Barber ___ 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"
Re: restart a script in etc/rc.d
On Mon, Mar 2, 2009 at 2:25 PM, Oliver Lehmann wrote:
> Hi Doug,
>
> Doug Barton wrote:
>
>> Also, the assignment of pidfile should really come after the defaults are
>> set.
>>
>> If you do all that and it still doesn't work, send a diff of your two rc.d
>> scripts to the list.
>
> PROVIDE is in both cases "utility" (probably a generic unchanged default)
> - I've changed it to utility2 for bacula-fd2 with no changes. Here the diff:
>
> r...@nudel rc.d> diff -u bacula-fd*
> --- bacula-fd 2009-02-15 23:25:03.0 +0100
> +++ bacula-fd2 2009-03-02 20:22:40.0 +0100
> @@ -16,16 +16,16 @@
>
> . /etc/rc.subr
>
> -name="bacula_fd"
> +name="bacula_fd2"
> rcvar=${name}_enable
> command=/usr/local/sbin/bacula-fd
>
I didn't see anyone else mention this -- did you change 'bacula-fd' to
'bacula-fd2'?
--
Glen Barber
___
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"
Re: restart a script in etc/rc.d
On Mon, Mar 2, 2009 at 4:10 PM, Glen Barber wrote:
> On Mon, Mar 2, 2009 at 2:25 PM, Oliver Lehmann wrote:
>> Hi Doug,
>>
>> Doug Barton wrote:
>>
>>> Also, the assignment of pidfile should really come after the defaults are
>>> set.
>>>
>>> If you do all that and it still doesn't work, send a diff of your two rc.d
>>> scripts to the list.
>>
>> PROVIDE is in both cases "utility" (probably a generic unchanged default)
>> - I've changed it to utility2 for bacula-fd2 with no changes. Here the diff:
>>
>> r...@nudel rc.d> diff -u bacula-fd*
>> --- bacula-fd 2009-02-15 23:25:03.0 +0100
>> +++ bacula-fd2 2009-03-02 20:22:40.0 +0100
>> @@ -16,16 +16,16 @@
>>
>> . /etc/rc.subr
>>
>> -name="bacula_fd"
>> +name="bacula_fd2"
>> rcvar=${name}_enable
>> command=/usr/local/sbin/bacula-fd
>>
>
> I didn't see anyone else mention this -- did you change 'bacula-fd' to
> 'bacula-fd2'?
>
Actually... That may not work (although, you could create a symlink,
but I doubt that'll help). Ignore my noise.
--
Glen Barber
___
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"
Re: HEADS UP multi processor compilations for everyone
On Tue, Mar 24, 2009 at 10:28 AM, Niclas Zeising wrote: > Great work! Indeed. > > Not to nitpick or be an annoyance, but you might want to document this in > ports(7) or make.conf(5) (or both) so it doesn't get lost in the mail-lists > or if people are not reading ports@ > Can it be added to UPDATING as well? -- Glen Barber 570.328.0318 ___ 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"
Re: FreeBSD Port: sysutils/webmin & perl 5.8.9
On Sat, Mar 28, 2009 at 3:53 PM, Dan Langille wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > After upgrading perl to 5.8.0 because of a vuln, I found webmin would > not start. > > $ tail /var/log/webmin/miniserv.error > /libexec/ld-elf.so.1: > /usr/local/lib/perl5/5.8.9/mach/auto/SDBM_File/SDBM_File.so: Undefined > symbol "sdbm_open" > > FWIW, perl-after-upgrade has been run. > I don't know what 'perl-after-upgrade' actually does, but have you tried rebuilding webmin? 'make deinstall; make reinstall' -- Glen Barber ___ 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"
Re: FreeBSD Port: sysutils/webmin & perl 5.8.9
On Sun, Mar 29, 2009 at 11:09 AM, Dan Langille wrote: >> I don't know what 'perl-after-upgrade' actually does, but have you >> tried rebuilding webmin? 'make deinstall; make reinstall' > > I didn't do exactly that, but I did do a 'portupgrade -f webin'. > I've never used portupgrade. What does: pkg_info | grep webmin display? -- Glen Barber ___ 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"
Re: FreeBSD Port: sysutils/webmin & perl 5.8.9
On Sun, Mar 29, 2009 at 11:18 AM, Dan Langille wrote: > $ pkg_info | grep webmin > webmin-1.470_1 Web-based interface for system administration for Unix Erm... Yeah... pkg_version | grep webmin Sorry. Doing this from memory -- not in front of a FreeBSD box currently. -- Glen Barber ___ 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"
Re: FreeBSD Port: sysutils/webmin & perl 5.8.9
2009/3/29 Dan Langille : > > $ pkg_version | grep webmin > webmin = > Interesting. I assume your ports tree is up to date? Unless anyone else has another ideas, I'd try to contact the maintainer (if there is one). If that fails, submit a PR. -- Glen Barber ___ 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"
