Re: vim ports broken.
matt donovan wrote: On Fri, Jun 19, 2009 at 5:37 AM, Albert Shih wrote: I think the vim ports is broken. Nope not broken just takes a long time to grab that patch since it pulls from FreeBSD ftp localdistfiles mirror under obrien The port *is* broken: # fetch ftp://ftp.freebsd.org/pub/FreeBSD/ports/local-distfiles/obrien/7.2.041% fetch: ftp://ftp.freebsd.org/pub/FreeBSD/ports/local-distfiles/obrien/7.2.041%: Bad Request # as fetch cannot handle "%" correctly. -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: vim ports broken.
Philip M. Gollucci wrote: Helmut Schneider wrote: matt donovan wrote: On Fri, Jun 19, 2009 at 5:37 AM, Albert Shih wrote: I think the vim ports is broken. Nope not broken just takes a long time to grab that patch since it pulls from FreeBSD ftp localdistfiles mirror under obrien The port *is* broken: # fetch ftp://ftp.freebsd.org/pub/FreeBSD/ports/local-distfiles/obrien/7.2.041 fetch: ftp://ftp.freebsd.org/pub/FreeBSD/ports/local-distfiles/obrien/7.2.041%: Bad Request # as fetch cannot handle "%" correctly. sure it can, it just needs '' around the url. Then there should be quotes around the URL in the port which obviously is not -> unable to fetch -> unable to install -> port broken. -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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"
portupgrade does not find updates
Hi, since a week or so portupgrade does not find updates on all of my machines (~15, all 7.2-RELEASE) anymore: [r...@bsdhelmut ~]# portversion -v | grep -v "=" amavisd-new-2.6.4_1,1 < needs updating (port has 2.6.4_2,1) firefox-3.0.13,1< needs updating (port has 3.0.14,1) libxml2-2.7.3_1 < needs updating (port has 2.7.4) lzma-9.06 < needs updating (port has 9.07) p5-Archive-Tar-1.52 < needs updating (port has 1.54) pear-Net_SMTP-1.3.2 < needs updating (port has 1.3.3) phpMyAdmin-3.2.1< needs updating (port has 3.2.2) python26-2.6.2_2< needs updating (port has 2.6.2_3) xcb-util-0.3.5 < needs updating (port has 0.3.6) [r...@bsdhelmut ~]# portupgrade -av ---> Session started at: Mon, 14 Sep 2009 13:50:56 +0200 ** None has been installed or upgraded. ---> Session ended at: Mon, 14 Sep 2009 13:51:24 +0200 (consumed 00:00:28) [r...@bsdhelmut ~]# I updates both portsdb and pkgdb manually without success. Any ideas? Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: portupgrade does not find updates
Helmut Schneider wrote: since a week or so portupgrade does not find updates on all of my machines (~15, all 7.2-RELEASE) anymore: cvsup5.de.freebsd.org seems down - since a few days. ___ 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"
How to upgrade perl 5.8 to 5.10?
Hi, /usr/ports/UPDATING says: portupgrade -o lang/perl5.10 -f perl-5.8.\* # BATCH=YES portupgrade -o lang/perl5.10 -f perl-threaded-5.8.\* ---> Upgrading 'perl-threaded-5.8.9_3' to 'perl-threaded-5.10.1' (lang/perl5.10) ---> Building '/usr/ports/lang/perl5.10' with make flags: -DWITH_THREADS ===> Cleaning for perl-threaded-5.10.1 ===> perl-threaded-5.10.1 conflicts with installed package(s): perl-threaded-5.8.9_3 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/lang/perl5.10. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20100120-80814-1ge6b2r-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=perl-threaded-5.8.9_3 UPGRADE_PORT_VER=5.8.9_3 make -DWITH_THREADS ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! lang/perl5.10 (perl-threaded-5.8.9_3) (unknown build error) # Currently the only solution seems to remove perl.5.8 which as a result deletes all dependencies which requires *all* ports to be reinstalled. Did I miss an important detail? Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: How to upgrade perl 5.8 to 5.10?
Matthew Seaman wrote: > Helmut Schneider wrote: > > > > ===> perl-threaded-5.10.1 conflicts with installed package(s): > > perl-threaded-5.8.9_3 > > > > They install files into the same place. > > Please remove them first with pkg_delete(1). > > *** Error code 1 > > Yes. This has been the subject of some debate on the questi...@... > list recently. The behaviour you're seeing is the result of a recent > commit affecting the conflicts handling code in bsd.port.mk. It now > checks for conflicts much earlier -- during the fetch and build > phases of installing from a port. Consequently the common idiom of: > ># portupgrade -o new-variant -f old-variant > > will almost always result in an error as you've seen. Many people > (myself included) think this change is not a good idea. > > To work around the problem, try: > ># portupgrade -m DISABLE_CONFLICTS=yes -o lang/perl5.10 -f > perl-threaded-5.8.\* > > and then carry on the process as described in UPDATING by > force-upgrading all perl modules and any applications that embed a > perl interpreter (mod_perl, net-snmpd, nagios, etc) top-notch! Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: How to upgrade perl 5.8 to 5.10?
Michal Varga wrote: > On Wed, Jan 20, 2010 at 1:54 PM, Helmut Schneider > wrote: > > [...] > > Currently the only solution seems to remove perl.5.8 which as a > > result deletes all dependencies which requires all ports to be > > reinstalled. > > > > No way, only if you decide to deinstall everything recursively. What > about: > > # pkg_deinstall -vfu perl-threaded-5.8.9_3 > # portinstall -v lang/perl5.10 > # portupgrade -vfu p5\* # pkg_info -R perl-threaded-5.8.9_3 | grep -v ^p5 Information for perl-threaded-5.8.9_3: Required by: amavisd-new-2.6.4_4,1 apache-2.2.14_5 bsdpan-SNMP-Extension-PassPersist-0.03 gamin-0.1.10_3 gio-fam-backend-2.22.4 glib-2.22.4 mailgraph-1.14_2 nagios-plugins-1.4.14,1 net-snmp-5.4.2.1_6 pango-1.26.2 razor-agents-2.84 rpm2cpio-1.2_2 rrdtool-1.3.9 # > (Also, cross-checking with /usr/local/bin/perl-after-upgrade helps > with some other specific cases). I did so when I upgraded from 5.8.8 to 5.8.9. I finally found myself doing a portupgrade -af. :) -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: How to upgrade perl 5.8 to 5.10?
Michal Varga wrote: > I'm not a heavy Perl user, but I don't remember anything ever melting > "too much", while doing it this way. Of course, there are things like > irssi, that break -every time- you reinstall Perl (even the same > version), but one gets used to it quickly. Then there is the rest that > probably only execs some scripts with Perl and doesn't care about your > versions (much). Majority of your, or mine, installed ports have Perl > only as an inherited dependency and never directly use it, so -af is a > bit overkill in such cases, i mean: > > pkg_info | wc -l > 805 Hell! > So even when you're switching near-major versions, recompiling p5-* > and maybe some of those in your list (I'd randomly pick, say amavisd, > bsdpan- and razor) should be enough, the fallout will be minimal, if > any (and if so, you just rebuild that one more that still fails). > Nevertheless, your list in't that extensive, recompiling all of it > shouldn't take more than half an hour, that's still a bit cheaper than > -af :) # pkg_info | wc -l 457 # And this machine is even my package-building station! Anyway, portupgrade -af took 45 minutes. *g* # dmesg -a [...] CPU: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz (2500.10-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x10676 Stepping = 6 Features=0xbfebfbff Features2=0xce3bd AMD Features=0x2800 AMD Features2=0x1 TSC: P-state invariant real memory = 8589934592 (8192 MB) avail memory = 8256348160 (7873 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: How to upgrade perl 5.8 to 5.10?
Michal Varga wrote: > > # pkg_info | wc -l > > 457 > > # > > > > And this machine is even my package-building station! > > > > Anyway, portupgrade -af took 45 minutes. g > > > Well, it's a dedicated blade after all :) And those 8 cores seem > pretty nasty, I'm envious. Well, afaik I even cannot use more than one CPU when building ports. There were plans/rumors that this would change. Does anyone know more about it? ___ 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: How to upgrade perl 5.8 to 5.10?
Boris Kochergin wrote: > Helmut Schneider wrote: > > Michal Varga wrote: > > > > > > > > # pkg_info | wc -l > >>>457 > > > > # > > > > > > > > And this machine is even my package-building station! > > > > > > > > Anyway, portupgrade -af took 45 minutes. g > > > > > >>> > > > Well, it's a dedicated blade after all :) And those 8 cores seem > > > pretty nasty, I'm envious. > >> > > > > Well, afaik I even cannot use more than one CPU when building ports. > > There were plans/rumors that this would change. Does anyone know > > more about it? > > It has happened: > > http://lists.freebsd.org/pipermail/freebsd-ports/2009-March/053736.html That'd explain a lot :) ___ 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"
CPAN Packages not registered
Hi, I upgraded perl 5.8.9 to 5.10.1. I have a single CPAN Module which is not part of the ports. With 5.8.9 the package was registered as bsdpan-SNMP-Extension-PassPersist-0.03 With 5.10 the package is not registered anymore. The build process cpan SNMP::Extension::Persist prints: [...] FreeBSD: Registering installation in the package database SAPER/SNMP-Extension-PassPersist-0.03.tar.gz ./Build install -- OK but actually nothing happens: # pkg_info | grep -ir bsdpan # pkg_info | grep -ir PassPersist # pkgdb -Fu ---> Updating the pkgdb [Updating the pkgdb in /var/db/pkg ... - 173 packages found (-1 +0) (...)(? bsdpan-SNMP-Extension-PassPersist-0.03) done] ---> Checking the package registry database # grep -ir PassPersist /var/db/pkg Binary file /var/db/pkg/pkgdb.db matches # What happend? Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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"
php5-snmp broken on some systems for more than 2 months
Hi, I fully understand that the current and past actions on php, png and so on were very time consuming. Anyway php5-snmp (5.2.12 *and* 5.3.2) are broken on obviously a few systems, including mine. A PR was opened 2 months ago but I even cannot find a reply from any of the maintainers. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/144137 Again, I fully understand that people also have to do other things but in my (and others) case it is sooo painful not being able to move ahead to 5.3 or back to 5.2 because of this problem. Any advise what I can do to support this process? It is meanwhile a real pain. Thanks and Regards, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: php5-snmp broken on some systems for more than 2 months
Matthew Seaman wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 26/04/2010 11:32:45, Helmut Schneider wrote: > > Hi, > > > > I fully understand that the current and past actions on php, png > > and so on were very time consuming. Anyway php5-snmp (5.2.12 and > > 5.3.2) are broken on obviously a few systems, including mine. A PR > > was opened 2 months ago but I even cannot find a reply from any of > > the maintainers. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/144137 > > > > Again, I fully understand that people also have to do other things > > but in my (and others) case it is sooo painful not being able to > > move ahead to 5.3 or back to 5.2 because of this problem. > > > > Any advise what I can do to support this process? It is meanwhile a > > real pain. > > > > Thanks and Regards, Helmut > > > > This is actually a problem in net-mgmt/net-snmp. > > There's a patch in ports/141238 which will let you compile, but > pkg-plist for net-mgmt/net-snmp needs attention. The patch is ASCII-corrupted, do you have the original you could post? -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: php5-snmp broken on some systems for more than 2 months
Matthew Seaman wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 26/04/2010 12:52:11, Helmut Schneider wrote:
> > Matthew Seaman wrote:
> >
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA1
> > >
> >> On 26/04/2010 11:32:45, Helmut Schneider wrote:
> >>> Hi,
> > > >
> >>> I fully understand that the current and past actions on php, png
> >>> and so on were very time consuming. Anyway php5-snmp (5.2.12 and
> >>> 5.3.2) are broken on obviously a few systems, including mine. A PR
> >>> was opened 2 months ago but I even cannot find a reply from any of
> >>> the maintainers.
> > > >
> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/144137
> > > >
> >>> Again, I fully understand that people also have to do other things
> >>> but in my (and others) case it is sooo painful not being able to
> >>> move ahead to 5.3 or back to 5.2 because of this problem.
> > > >
> >>> Any advise what I can do to support this process? It is meanwhile
> a >>> real pain.
> > > >
> >>> Thanks and Regards, Helmut
> > > >
> > >
> >> This is actually a problem in net-mgmt/net-snmp.
> > >
> >> There's a patch in ports/141238 which will let you compile, but
> >> pkg-plist for net-mgmt/net-snmp needs attention.
> >
> > The patch is ASCII-corrupted, do you have the original you could
> > post?
> >
>
> happy-idiot-talk:...ports/net-mgmt/net-snmp:% diff -u Makefile.orig
> Makefile
> - --- Makefile.orig 2010-04-26 13:09:49.0 +0100
> +++ Makefile 2010-04-26 13:09:58.0 +0100
> @@ -106,6 +106,10 @@
> NET_SNMP_MIB_MODULE_LIST+= sctp-mib
> .endif
>
> +.if ${OSVERSION} >= 80
> +CONFIGURE_ARGS+= --with-libs="-lssp_nonshared"
> +.endif
> +
> .if defined(WITH_MFD_REWRITES)
> CONFIGURE_ARGS+=--enable-mfd-rewrites
> NET_SNMP_MIB_MODULE_LIST+= if-mib
Great. I can confirm that with the patch php5-snmp (tested with 5.3.2)
builds fine now.
Thanks, Helmut
--
No Swen today, my love has gone away
My mailbox stands for lorn, a symbol of the dawn
___
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: php5-snmp broken on some systems for more than 2 months
Wesley Shields wrote: > On Mon, Apr 26, 2010 at 03:20:24PM +0100, Matthew Seaman wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On 26/04/2010 13:56:56, Wesley Shields wrote: > > > Thanks for bringing this up. I will take it over, get the plist > > > fixed up and get it in the tree. > > > > Cool. Thank you very much indeed. And as an added bonus, you can > > probably close ports/144137 and maybe even ports/140791. > > I've closed ports/144137 as it's clearly the issue here. Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: Apache 22 - FreeBSD 8.0 - (httpd), uid 80: exited on signal 11
Hans F. Nordhaug wrote: > I recently upgrade to FreeBSD 8.0 (from 7.2) and suddenly I get a lot > of "(httpd), uid 80: exited on signal 11" in my logs. I have similar > problems with amavisd - see > http://lists.freebsd.org/pipermail/freebsd-questions/2010-April/thread.html#215757 > I'm have updated and recompiled all ports. The logs /var/log/messages > and the httpd error log both just report > "exited on signal 11" or "Segmentation fault (11)" > > Any hints? Find the .core file, start gdb with the core file, type "bt", post the output. Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: Apache 22 - FreeBSD 8.0 - (httpd), uid 80: exited on signal 11
Hans F. Nordhaug wrote: > * Helmut Schneider [2010-05-02]: > > Hans F. Nordhaug wrote: > > > > > I recently upgrade to FreeBSD 8.0 (from 7.2) and suddenly I get a > > > lot of "(httpd), uid 80: exited on signal 11" in my logs. I have > > > similar problems with amavisd - see > > > > > http://lists.freebsd.org/pipermail/freebsd-questions/2010-April/thread.html#215757 > > > I'm have updated and recompiled all ports. The logs > > > /var/log/messages and the httpd error log both just report > > > "exited on signal 11" or "Segmentation fault (11)" > > > > > > Any hints? > > > > Find the .core file, start gdb with the core file, type "bt", post > > the output. > > Sorry, I should have mentioned that I can't find any core files. > "find / -name '*.core'" returns nothing. I guess one can assume that - you already checked RAM with memtest or so. - you already check your hard drive (you mentiened you fsck'ed your hard drive and found errors that wer corrected) - you are running one or more perl apps within apache? ___ 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: Apache 22 - FreeBSD 8.0 - (httpd), uid 80: exited on signal 11
Matthew Seaman wrote: > On 03/05/2010 11:49:35, Helmut Schneider wrote: > > I guess one can assume that > > > > - you already checked RAM with memtest or so. > > - you already check your hard drive (you mentiened you fsck'ed your > > hard drive and found errors that wer corrected) > > - you are running one or more perl apps within apache? > > - - You've checked the order of the loadable PHP modules in > /usr/local/etc/php/extensions.ini ? > > That's been the number one cause of apache crashes mentioned on this > list in the last several years. I guess the problem is with perl and not with php - otherwise you're right. ___ 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: Port Dansguardian
Matthew Seaman wrote: > On 10/05/2010 24:30:19, Celso Viana wrote: > > > I already have Apache 2.0.x installed on a machine, but the > > "dansguardian" has dependency on apache 1.3.x, how do I run > > dansguardian with apache 2.0.x? > > Put: > > APACHE_PORT=www/apache20 > > into /etc/make.conf Is there a list of ports-related knobs for make.conf? Thanks, Helmut ___ 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: Port Dansguardian
Matthew Seaman wrote: > On 10/05/2010 17:12:47, Helmut Schneider wrote: > > > Is there a list of ports-related knobs for make.conf? > > Other than /usr/ports/KNOBS you mean? No. :) ___ 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"
ncftp broken for more than 6 months
Hi, http://www.freebsd.org/cgi/query-pr.cgi?pr=140934 Still patient, but is there a chance to get my backups succeeding again? Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: ncftp broken for more than 6 months
Kostik Belousov wrote: > On Fri, May 21, 2010 at 08:49:06AM +0000, Helmut Schneider wrote: > > Hi, > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=140934 > > > > Still patient, but is there a chance to get my backups succeeding > > again? > > I just committed supposed fix to the HEAD, r208374. You may apply it > to stable/8 manually and report back whether it helped. Forgive my ignorance, how can I find r208374? I know how to access cvs via web or cvsup but that particular patch? -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: ncftp broken for more than 6 months
Kostik Belousov wrote: > On Fri, May 21, 2010 at 12:09:01PM +0000, Helmut Schneider wrote: > > Kostik Belousov wrote: > > > > > On Fri, May 21, 2010 at 08:49:06AM +, Helmut Schneider wrote: > > > > Hi, > > > > > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=140934 > > > > > > > > Still patient, but is there a chance to get my backups > > > > succeeding again? > > > > > > I just committed supposed fix to the HEAD, r208374. You may apply > > > it to stable/8 manually and report back whether it helped. > > > > Forgive my ignorance, how can I find r208374? I know how to access > > cvs via web or cvsup but that particular patch? > > This is svn revision for src/, you can see it at > http://svn.freebsd.org/viewvc/base?view=revision&revision=208374 I'm running RELEASE so I need a certain time to prepare a STABLE installation but I'll report back as soon as possible. Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: ncftp broken for more than 6 months
Kostik Belousov wrote: > On Fri, May 21, 2010 at 12:30:20PM +0000, Helmut Schneider wrote: > > Kostik Belousov wrote: > > > > > On Fri, May 21, 2010 at 12:09:01PM +, Helmut Schneider wrote: > > > > Kostik Belousov wrote: > > > > > > > > > On Fri, May 21, 2010 at 08:49:06AM +, Helmut Schneider > > > > > wrote: > > > > > > Hi, > > > > > > > > > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=140934 > > > > > > > > > > > > Still patient, but is there a chance to get my backups > > > > > > succeeding again? > > > > > > > > > > I just committed supposed fix to the HEAD, r208374. You may > > > > > apply it to stable/8 manually and report back whether it > > > > > helped. > > > > > > > > Forgive my ignorance, how can I find r208374? I know how to > > > > access cvs via web or cvsup but that particular patch? > > > > > > This is svn revision for src/, you can see it at > > > http://svn.freebsd.org/viewvc/base?view=revision&revision=208374 > > > > I'm running RELEASE so I need a certain time to prepare a STABLE > > installation but I'll report back as soon as possible. > > I think, but did not checked, that the patch is applicable to the > 8.0 release as well. I applied the 1-line "patch" you provided in the PR to both my i386 and amd64 installations (~15 x 8.0-RELEASE-p2) and it seems fine, I also can not see any negative side effects (probably not expected at all). Thanks a lot, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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"
PR not assigned yet
Hi, I created a PR 2 days ago but it is yet not assigned. Anything wrong with it? http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/147468 Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: PR not assigned yet
Doug Barton wrote: > On 06/06/10 12:14, Helmut Schneider wrote: > > I created a PR 2 days ago but it is yet not assigned. Anything wrong > > with it? > > Yes. :) In order for the automated tools to work the category/name > of the port in the synopsis needs to be exactly as it is in the ports > tree. You had net-mgmt/net-snmp55 which should have been just > net-mgmt/net-snmp. I fixed that for you, and assigned it to sylvio. OK, I thought, because the old PR had the same subject, but the previous version, and - thanks. :) ___ 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"
amavisd-new does not compile because of db42
Hi, I cannot compile amavisd-new because db42 is not recognized as already installed: http://www.freebsd.org/cgi/query-pr.cgi?pr=147718 As stated in the (unfortunately closed) PR I already removed all packages and tried from scratch but it still fails. The point is that the following ports also depending on db42 compile successfully: # pkg_info -R db42-4.2.52_5 Information for db42-4.2.52_5: Required by: apache-2.2.15_9 apr-ipv6-devrandom-gdbm-db42-ldap24-1.4.2.1.3.9_1 cacti-0.8.7f joomla15-1.5.18 nagios-3.2.1 pecl-pdflib-2.1.8 php5-5.3.2_1 php5-ctype-5.3.2_1 php5-filter-5.3.2_1 php5-gd-5.3.2_1 php5-json-5.3.2_1 php5-mysql-5.3.2_1 php5-session-5.3.2_1 php5-snmp-5.3.2_1 php5-sockets-5.3.2_1 php5-xml-5.3.2_1 php5-zlib-5.3.2_1 typo3-4.3.3_1 wordpress-mu-2.9.2,2 # Anyone an idea what to do to fix it? Unlike stated in the PR amavisd-new also fails when trying to compile it manually: # env make depends -DWITH_BDB -DWITH_SNMP -DWITH_POF -DWITH_RAR -DWITH_UNRAR -DWITH_UNARJ -DWITH_NOMARCH -DWITH_UNZOO -DWITH_TNEF ===> amavisd-new-2.6.4_6,1 depends on shared library: db-4.2.2 - not found ===>Verifying install for db-4.2.2 in /usr/ports/databases/db42 ===> Installing for db42-4.2.52_5 ===> Generating temporary packing list ===> Checking if databases/db42 already installed ===> db42-4.2.52_5 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of databases/db42 without deleting it first, set the variable "FORCE_PKG_REGISTER" in your environment or the "make install" command line. *** Error code 1 Stop in /usr/ports/databases/db42. *** Error code 1 Stop in /usr/ports/security/amavisd-new. # E.g. apr1 correctly identifies db42: # env make -DWITH_BDB cd /usr/ports/devel/apr1 && make config; [...] ===> apr-ipv6-devrandom-gdbm-db42-1.4.2.1.3.9_1 depends on shared library: db-4.2.2 - found [...] # Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: amavisd-new does not compile because of db42
Gabor Kovesdan wrote: > > Helmut 'Ingrid' Schneider wrote: > > > > > > > I cannot compile amavisd-new because db42 is not recognized as > > > already installed: > > > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=147718 > > > > > > As stated in the (unfortunately closed) PR I already removed all > > > packages and tried from scratch but it still fails. > >> > > Might be by accident but I checked 5 machines, it failed on both > > amd64 platforms while on the other 3 i386 platforms it succeeded... > > > Could you please try the following on the machines where it fails? > > env FORCE_PKG_REGISTER=yes portupgrade amavisd-new\* # env FORCE_PKG_REGISTER=yes portupgrade -N amavisd-new\* [Gathering depends for security/amavisd-new done] ---> Installing 'amavisd-new-2.6.4_6,1' from a port (security/amavisd-new) ---> Building '/usr/ports/security/amavisd-new' with make flags: -DWITH_BDB -DWITH_SNMP -DWITH_POF -DWITH_RAR -DWITH_UNRAR -DWITH_UNARJ -DWITH_NOMARCH -DWITH_UNZOO -DWITH_TNEF [...] cd /usr/local/bin/db42 ; for i in * ; do /bin/ln -s -f db42/$i ../$i-4.2 ; done ===> Running ldconfig /sbin/ldconfig -m /usr/local/lib ===> Registering installation for db42-4.2.52_5 ===> Returning to build of amavisd-new-2.6.4_6,1 Error: shared library "db-4.2.2" does not exist *** Error code 1 Stop in /usr/ports/security/amavisd-new. *** Error code 1 Stop in /usr/ports/security/amavisd-new. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20100611-69218-1df6udu-0 env make -DWITH_BDB -DWITH_SNMP -DWITH_POF -DWITH_RAR -DWITH_UNRAR -DWITH_UNARJ -DWITH_NOMARCH -DWITH_UNZOO -DWITH_TNEF ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! security/amavisd-new (dependent libraries) # -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: amavisd-new does not compile because of db42
Helmut 'Ingrid' Schneider wrote: > I cannot compile amavisd-new because db42 is not recognized as already > installed: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=147718 > > As stated in the (unfortunately closed) PR I already removed all > packages and tried from scratch but it still fails. Might be by accident but I checked 5 machines, it failed on both amd64 platforms while on the other 3 i386 platforms it succeeded... -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: amavisd-new does not compile because of db42
Gabor Kovesdan wrote: > > > >===>Running ldconfig > > /sbin/ldconfig -m /usr/local/lib > >===>Registering installation for db42-4.2.52_5 > >===>Returning to build of amavisd-new-2.6.4_6,1 > > Error: shared library "db-4.2.2" does not exist > > *** Error code 1 > > > > Stop in /usr/ports/security/amavisd-new. > > *** Error code 1 > > > > > It seems that it cannot find the library but amavisd-new uses the > USE_BDB know from bsd.databases.mk just like quite a bunch of other > ports, so the dependency definition is obviously correct. I don't > know what causes this error and I haven't got any more PRs from other > users. Soon, I'll bump the required version again because after the > last change I got some mails that say newer versions operate even > better with amavisd-new. I'll just talk to the developer to see, > which version would be the optimal one or we can just pull in the > latest bdb version. I'd say let's wait for that update and hopefully > that will also solve your problem. # make clean ===> Cleaning for amavisd-new-2.6.4_6,1 # env make depends ===> amavisd-new-2.6.4_6,1 depends on shared library: db-4.2.2 - found [...] # env make depends -DWITH_RAR ===> amavisd-new-2.6.4_6,1 depends on shared library: db-4.2.2 - not found [...] # I then commented out "IA32_BINARY_PORT=yes" from the WITH_RAR section in the Makefile and guess what?! :) # env make depends -DWITH_RAR ===> amavisd-new-2.6.4_6,1 depends on shared library: db-4.2.2 - found [...] # portupgrade -N amavisd-new\* [Updating the pkgdb in /var/db/pkg ... - 224 packages found (-0 +1) . done] [Gathering depends for security/amavisd-new .. done] ---> Installing 'amavisd-new-2.6.4_6,1' from a port (security/amavisd-new) ---> Building '/usr/ports/security/amavisd-new' with make flags: -DWITH_BDB -DWITH_SNMP -DWITH_POF -DWITH_RAR -DWITH_UNRAR -DWITH_UNARJ -DWITH_NOMARCH -DWITH_UNZOO -DWITH_TNEF ===> Cleaning for amavisd-new-2.6.4_6,1 cd /usr/ports/security/amavisd-new && make config; [...] ===> amavisd-new-2.6.4_6,1 depends on shared library: db-4.2.2 - found [...] # Does that help? :) -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: amavisd-new does not compile because of db42
Scot Hetzel wrote:
> The use as defined in bsd.port.mk for the IA32_BINARY_PORT variable is
> incorrectly being used in the amavisd-new port:
>
> # IA32_BINARY_PORT
> # - Set this instead of ONLY_FOR_ARCHS if the
> given port
> # fetches and installs compiled i386 binaries.
>
> When this variable is set it changes how ldconfig searches for
> libraries by setting the -32 to ldconfig. This prevents the port from
> properly detecting any 64bit libraries and only looks for 32bit
> libraries. The reason that only db42 is being affected is because
> most of the ports dependancies are RUN_DEPENDS.
>
> The correct way to the amavisd-new port would be to change this:
>
> .if defined(WITH_RAR)
> IA32_BINARY_PORT= yes
> RUN_DEPENDS+= ${LOCALBASE}/bin/rar:${PORTSDIR}/archivers/rar
> .endif
>
> To this:
>
> .if defined(WITH_RAR)
> # support for archivers/rar is broken on ia64
> .if ${ARCH} =="i386" || ${ARCH} == "amd64"
> RUN_DEPENDS+= ${LOCALBASE}/bin/rar:${PORTSDIR}/archivers/rar
> .else
> IGNORE= archviers/rar is a 32-bit binary port and is not compatible
> with ${ARCH} .endif
> .endif
>
> Note: This may need to be moved after the bsd.port.pre.mk.
I put suggested changes before bsd.port.pre.mk and amavisd-new installs
fine.
Thanks, Helmut
___
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/133758 and net-snmp-5.5 - inactive memory stil not counted as free memory
Thomas Steen Rasmussen wrote: > I am experiencing what seems like the problem in > http://www.freebsd.org/cgi/query-pr.cgi?pr=133758 > > I have net-snmp-5.5 installed on FreeBSD 7.2 i386 and it returns this: > UCD-SNMP-MIB::memAvailReal.0 = INTEGER: 189072 kB > UCD-SNMP-MIB::memTotalFree.0 = INTEGER: 273204 kB > > When this is what 'top' says: > Mem: 157M Active, 1467M Inact, 189M Wired, 8580K Cache, 112M Buf, 176M > Free IMHO ucd-snmp is completely foobar. See my PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=147468 But see also: # snmpwalk -v2c -cpublic localhost .1.3.6.1.4.1.2021.4 UCD-SNMP-MIB::memIndex.0 = INTEGER: 0 UCD-SNMP-MIB::memErrorName.0 = STRING: swap UCD-SNMP-MIB::memTotalSwap.0 = INTEGER: 3583872 kB UCD-SNMP-MIB::memAvailSwap.0 = INTEGER: 3583872 kB UCD-SNMP-MIB::memTotalReal.0 = INTEGER: 4179676 kB UCD-SNMP-MIB::memAvailReal.0 = INTEGER: 1482980 kB UCD-SNMP-MIB::memTotalFree.0 = INTEGER: 1589660 kB UCD-SNMP-MIB::memMinimumSwap.0 = INTEGER: 16000 kB UCD-SNMP-MIB::memShared.0 = INTEGER: 133364 kB UCD-SNMP-MIB::memBuffer.0 = INTEGER: 427888 kB UCD-SNMP-MIB::memCached.0 = INTEGER: 180428864 kB UCD-SNMP-MIB::memSwapError.0 = INTEGER: noError(0) UCD-SNMP-MIB::memSwapErrorMsg.0 = STRING: # snmpwalk -v2c -cpublic localhost .1.3.6.1.4.1.2021.4 UCD-SNMP-MIB::memIndex.0 = INTEGER: 0 UCD-SNMP-MIB::memErrorName.0 = STRING: swap UCD-SNMP-MIB::memTotalSwap.0 = INTEGER: 3583872 kB UCD-SNMP-MIB::memAvailSwap.0 = INTEGER: 3583872 kB UCD-SNMP-MIB::memTotalReal.0 = INTEGER: 4179676 kB UCD-SNMP-MIB::memAvailReal.0 = INTEGER: 1317912 kB UCD-SNMP-MIB::memTotalFree.0 = INTEGER: 3260720 kB UCD-SNMP-MIB::memMinimumSwap.0 = INTEGER: 16000 kB UCD-SNMP-MIB::memShared.0 = INTEGER: 109740 kB UCD-SNMP-MIB::memBuffer.0 = INTEGER: 427888 kB UCD-SNMP-MIB::memCached.0 = INTEGER: 0 kB UCD-SNMP-MIB::memSwapError.0 = INTEGER: noError(0) UCD-SNMP-MIB::memSwapErrorMsg.0 = STRING: # Within one or two seconds memTotalFree changed from 1589660 kB to 3260720 kB. According to "top" ~1.5GB is the correct value. Same for memCached, flip-flopping from 180428864 kB(!!) to 0 kb within the same second. -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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/133758 and net-snmp-5.5 - inactive memory stil not counted as free memory
Thomas Steen Rasmussen wrote: > I am experiencing what seems like the problem in > http://www.freebsd.org/cgi/query-pr.cgi?pr=133758 > > I have net-snmp-5.5 installed on FreeBSD 7.2 i386 and it returns this: > UCD-SNMP-MIB::memAvailReal.0 = INTEGER: 189072 kB > UCD-SNMP-MIB::memTotalFree.0 = INTEGER: 273204 kB > > When this is what 'top' says: > Mem: 157M Active, 1467M Inact, 189M Wired, 8580K Cache, 112M Buf, 176M > Free > > Clearly the "Inact" isn't counted as free memory which is causing my > monitoring to throw alerts when there is actually lots of "free" > memory left (where free=free+inact). net-snmp now reports inactive memory as cache memory (actually inactive memory is not free memory). Please check. Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: Fwd: Wordpress outputs an empty page after ports upgrade
Yuri wrote: > After one of the recent upgrades I only get an empty page from > wordpress. While _a_bit_more_ information would be helpdul check the order of the php modules in your extensions.ini -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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"
PRs for Typo3 time out
Hi, in the past I created a few PRs with patches for important security updates for typo3. Unfortunately they all timed out. 10 days ago I created a new one: http://www.freebsd.org/cgi/query-pr.cgi?pr=149236 I guess it will also time out. Now, there is another update: http://www.freebsd.org/cgi/query-pr.cgi?pr=149493 I also expect it to time out. What is the time GNATS is waiting for feedback of the maintainer? Does it make a difference if importance and/or severity are raised? IMHO it is a problem if important security fixes are approved only after a 14-day-or-more timeout. Are there mechanisms to avoid such a delay? Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: PRs for Typo3 time out
Mark Linimon wrote: > On Tue, Aug 10, 2010 at 10:56:44AM +0000, Helmut Schneider wrote: > > in the past I created a few PRs with patches for important security > > updates for typo3. Unfortunately they all timed out. > > > > What is the time GNATS is waiting for feedback of the maintainer? > > It's 14 days for a normal update or bugfix. For security problems, > that doesn't matter: they should be fixed as soon as possible. If > the security problem is not serious, I think it's fair to notify the > maintainer before the commit; otherwise, it can go in immediately. > > > Does it make a difference if importance and/or severity are raised? > > No, not really. The values of these have been so over-set in GNATS > that the only people that notice them are the bugbusting team. I try > to keep the Severity=critical ones in order, but everything else is > meaningless. > > > IMHO it is a problem if important security fixes are approved only > > after a 14-day-or-more timeout. Are there mechanisms to avoid such a > > delay? > > a) you can try adding "[security]" to the Synopsis line; this may help > make it more visible. > > b) I will email the maintainer and ask if he is willing to transfer > maintainership to you. Me?! Huh! What does that mean? :) I mean, what if I run into problems? > In general, if people are having problems with how individual ports > are maintained, they should email port...@freebsd.org and bring it to > our attention directly. Thanks. I didn't mean to blame others, I'm just concerned about security. ___ 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"
How long does a repocopy take?
Hi, sorry for my impatience but I asked for a repocopy about one week ago and now I'm wondering how long normally a repocopy takes. http://www.freebsd.org/cgi/query-pr.cgi?pr=150937 Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: How long does a repocopy take?
Max Brazhnikov wrote: > On Mon, 4 Oct 2010 18:57:35 + (UTC), Helmut Schneider wrote: > > sorry for my impatience but I asked for a repocopy about one week > > ago and now I'm wondering how long normally a repocopy takes. > > Submit patch vs existing port ask for repocopy. Commiter will request > repocopy from portmgr@ Did so. Thanks, Helmut ___ 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"
Entries in /usr/ports/UPDATING
Hi, a repocopy for typo3 was done recently and I would like to suggest users to change origin if they want to stay at the 4.3 branch. I guess UPDATING is the right place to do so but who does so, who changes/decides that a hint in UPDATING might be useful? Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: Entries in /usr/ports/UPDATING
Wesley Shields wrote: > On Thu, Oct 14, 2010 at 11:59:53AM +0000, Helmut Schneider wrote: > > a repocopy for typo3 was done recently and I would like to suggest > > users to change origin if they want to stay at the 4.3 branch. I > > guess UPDATING is the right place to do so but who does so, who > > changes/decides that a hint in UPDATING might be useful? > > Committers make the changes but if a maintainer thinks it's important > enough he/she can note that in the PR and the committer should honor > that. If you have a blurb you would like to see in UPDATING for this > please let me know and I will commit it. See my PM. Thanks, Helmut ___ 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: Print +REQUIRED_BY as tree?
Lev Serebryakov wrote: > Is here console tool, which shows dependency tree of installed ports > from "required" port to "users"? pkg_tree performs opposite task. > > +REQUIRED_BY is flat list, unfortunately. > > I need to investigate exact path why this port is installed on my > system :) Neither I'm a perl expert nor it is final but hth anyway. http://www.charlieroot.de/bsd/pkg_depends.pl ___ 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"
Problem with genplist replacing PORTVERSION
Hi, To create a new version of a port (let's say typo3) I copy typo3 to typo3.org. Then I run sudo make clean && sudo port fetch sudo rm -r /tmp/typo3* sudo genplist clean; sudo genplist create /tmp/ As a result on my 8.2 machine $PORTVERSION in pkg-plist is replaced with %%PORTVERSION%% as defined in the Makefile: %%WWWDIR%%_src-%%PORTVERSION%%/ChangeLog If I do so on my new 9.0 machine, it does not: %%WWWDIR%%_src-4.6.4/ChangeLog Why? What did I miss? Thanks, Helmut ___ 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 with genplist replacing PORTVERSION
Olli Hauer wrote:
> On 2012-03-06 21:30, Helmut Schneider wrote:
> > Hi,
> >
> > To create a new version of a port (let's say typo3) I copy typo3 to
> > typo3.org. Then I run
> >
> > sudo make clean && sudo port fetch
> > sudo rm -r /tmp/typo3*
> > sudo genplist clean; sudo genplist create tmp
> >
> > As a result on my 8.2 machine $PORTVERSION in pkg-plist is replaced
> > with %%PORTVERSION%% as defined in the Makefile:
> >
> > %%WWWDIR%%_src-%%PORTVERSION%%/ChangeLog
> >
> > If I do so on my new 9.0 machine, it does not:
> >
> > %%WWWDIR%%_src-4.6.4/ChangeLog
> >
> > Why? What did I miss?
>
>
> genplist does not replace by default PORTVERSION (not defined in the
> genplist code) Maybe you have a custom script which looks like
>
> cat ~/.genplist/typo3
>
> #!/bin/sh
> PV=$(make -V PORTVERSION)
>
> sed -i '' "|${PV}|%%PORTVERSION%%|g" $1
Ah, yes, I indeed patched genplist and added
| sed "s|${portversion}|%%PORTVERSION%%|g"
Thanks!
___
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 with genplist replacing PORTVERSION
Olli Hauer wrote:
> On 2012-03-06 21:30, Helmut Schneider wrote:
> > Hi,
> >
> > To create a new version of a port (let's say typo3) I copy typo3 to
> > typo3.org. Then I run
> >
> > sudo make clean && sudo port fetch
> > sudo rm -r /tmp/typo3*
> > sudo genplist clean; sudo genplist create tmp
> >
> > As a result on my 8.2 machine $PORTVERSION in pkg-plist is replaced
> > with %%PORTVERSION%% as defined in the Makefile:
> >
> > %%WWWDIR%%_src-%%PORTVERSION%%/ChangeLog
> >
> > If I do so on my new 9.0 machine, it does not:
> >
> > %%WWWDIR%%_src-4.6.4/ChangeLog
> >
> > Why? What did I miss?
>
> genplist does not replace by default PORTVERSION (not defined in the
> genplist code) Maybe you have a custom script which looks like
>
> cat ~/.genplist/typo3
>
> #!/bin/sh
> PV=$(make -V PORTVERSION)
>
> sed -i '' "|${PV}|%%PORTVERSION%%|g" $1
sed -i '' "s|${PV}|%%PORTVERSION%%|g" $1 ?! :)
___
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"
[portupgrade] ArgumentError
Hi, since friday or so I have a problem with portupgrade: # portupgrade -av ---> Session started at: Mon, 15 Nov 2010 13:22:41 +0100 ---> Skipping 'bsdpan-SNMP-Extension-PassPersist-0.03' because it is held by user (specify -f to force) ---> Session ended at: Mon, 15 Nov 2010 13:23:19 +0100 (consumed 00:00:38) /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:953:in `initialize': ArgumentError (ArgumentError) from /usr/local/sbin/portupgrade:1004:in `new' from /usr/local/sbin/portupgrade:1004:in `do_upgrade' from /usr/local/sbin/portupgrade:814:in `main' from /usr/local/sbin/portupgrade:810:in `each' from /usr/local/sbin/portupgrade:810:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:791:in `initialize' from /usr/local/sbin/portupgrade:231:in `new' from /usr/local/sbin/portupgrade:231:in `main' from /usr/local/sbin/portupgrade:2219 # I recursively reinstalled portupgrade. Any further ideas? Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: [portupgrade] ArgumentError
Helmut Schneider wrote: > # portupgrade -av > ---> Session started at: Mon, 15 Nov 2010 13:22:41 +0100 > ---> Skipping 'bsdpan-SNMP-Extension-PassPersist-0.03' because it is > held by user (specify -f to force) > ---> Session ended at: Mon, 15 Nov 2010 13:23:19 +0100 (consumed > 00:00:38) > /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:953:in `initialize': > ArgumentError (ArgumentError) > from /usr/local/sbin/portupgrade:1004:in `new' > from /usr/local/sbin/portupgrade:1004:in `do_upgrade' > from /usr/local/sbin/portupgrade:814:in `main' > from /usr/local/sbin/portupgrade:810:in `each' > from /usr/local/sbin/portupgrade:810:in `main' > from /usr/local/lib/ruby/1.8/optparse.rb:791:in `initialize' > from /usr/local/sbin/portupgrade:231:in `new' > from /usr/local/sbin/portupgrade:231:in `main' > from /usr/local/sbin/portupgrade:2219 > # > > I recursively reinstalled portupgrade. Any further ideas? Seems the problem is caused by a(ny) bsdpan package. Unregistered it and now it succeeds. -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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"
Typo3, submit port, mirrors
Hi, I'd like to release a new version of Typo3, version 4.5: [helmut@BSDHelmut832 ~/typo3]$ sudo port fetch ===> Vulnerability check disabled, database not found ===> License GPLv3 accepted by the user => typo3_src-4.5.0.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from http://heanet.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://heanet.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Du mmy/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://sunet.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://sunet.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dum my/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://iweb.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://iweb.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dumm y/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://switch.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://switch.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Du mmy/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://surfnet.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://surfnet.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20D ummy/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://kent.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://kent.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dumm y/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://freefr.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://freefr.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Du mmy/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://voxel.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://voxel.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dum my/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://jaist.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://jaist.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dum my/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://osdn.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://osdn.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dumm y/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Not Found => Attempting to fetch from http://nchc.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://nchc.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dumm y/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://transact.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://transact.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20 Dummy/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://softlayer.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://softlayer.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%2 0Dummy/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://internode.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://internode.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%2 0Dummy/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from http://ufpr.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dummy/TYPO3%204.5.0/. fetch: http://ufpr.dl.sourceforge.net/project/typo3/TYPO3%20Source%20and%20Dumm y/TYPO3%204.5.0/typo3_src-4.5.0.tar.gz: Moved Temporarily => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/typo3_src-4.5.0.tar.gz : File unavailable (e.g., file not found, no access) => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles/ and try again. *** Error code 1 Stop in /usr/home/helmut/typo3. [helmut@BSDHelmut832 ~/typo3]$ Who needs to change what? Thanks, Helmut ___ 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: Typo3, submit port, mirrors
Hi Wen,
wen heping wrote:
> Do you mean the fetch error?
Yes.
> Seems typo3_4.5.0 changed download site , now it is:
> http://dl1.typo3.org/TYPO3_4.5.0/introductionpackage-4.5.0.zip
>
> So you should change MASTER_SITES.
Currently
MASTER_SITES=
SF/${PORTNAME}/TYPO3%20Source%20and%20Dummy/TYPO3%20${PORTVERSION}
is defined. According to bsd.sites.mk SF aka SOURCEFORGE resolves to
http://${mirror}.dl.sourceforge.net/project/%SUBDIR%/
But the correct link is
http://sourceforge.net/projects/typo3/files/TYPO3%20Source%20and%20Dummy/
project*s*.
___
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: Typo3, submit port, mirrors
Helmut Schneider wrote:
> Hi Wen,
>
> wen heping wrote:
>
> > Do you mean the fetch error?
>
> Yes.
>
> > Seems typo3_4.5.0 changed download site , now it is:
> > http://dl1.typo3.org/TYPO3_4.5.0/introductionpackage-4.5.0.zip
> >
> > So you should change MASTER_SITES.
>
> Currently
>
> MASTER_SITES=
> SF/${PORTNAME}/TYPO3%20Source%20and%20Dummy/TYPO3%20${PORTVERSION}
>
> is defined. According to bsd.sites.mk SF aka SOURCEFORGE resolves to
>
> http://${mirror}.dl.sourceforge.net/project/%SUBDIR%/
>
> But the correct link is
>
>
http://sourceforge.net/projects/typo3/files/TYPO3%20Source%20and%20Dummy/
>
> project*s*.
It seems they completely changed the mirroring system. Never mind.
___
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"
bump of PORTREVISION mandatory?
Hi, with the release of Typo3 4.5, 4.4 becomes "old stable", 4.3 becomes "deprecated". Therefore a change at pkg_descr is required. That is the only change. Do I need to bump PORTREVISION before I submit the updated port? Is that mandatory? I don't like the idea that someone is asked to update his/her installed package only because of a changed pkg_descr. Thanks, Helmut ___ 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: bump of PORTREVISION mandatory?
Jason Helfman wrote: > On Thu, Jan 27, 2011 at 05:30:45PM +0000, Helmut Schneider thus spake: > > Hi, > > > > with the release of Typo3 4.5, 4.4 becomes "old stable", 4.3 becomes > > "deprecated". Therefore a change at pkg_descr is required. That is > > the only change. > > > > Do I need to bump PORTREVISION before I submit the updated port? Is > > that mandatory? > > > > I don't like the idea that someone is asked to update his/her > > installed package only because of a changed pkg_descr. > > > > Thanks, Helmut > > If 4.3 is deprecated, shouldn't it be removed from the tree? (ie. > MOVED/UPDATING) It is still supported (estimated until 06/11) but already called "deprecated". > Why would you need to update the portrevision for a pkg-descr change? > If it isn't changing the behavior of the port, I don't see why that > is necessary, but others may have different ideas on this topic. OK. ___ 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: bump of PORTREVISION mandatory?
Eitan Adler wrote: > > Do I need to bump PORTREVISION before I submit the updated port? Is > > that mandatory? > > PORTREVISION should only be changed if you need the users of a port to > recompile the port. > Typos and documentation typically don't require such a change. Thanks. ___ 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: Typo3, submit port, mirrors
Helmut Schneider wrote: [mirrors down] Might be related: http://sourceforge.net/apps/wordpress/sourceforge/2011/01/27/service-downtime/ Helmut ___ 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: bump of PORTREVISION mandatory?
Sahil Tandon wrote: > On Thu, 2011-01-27 at 17:30:45 +0000, Helmut Schneider wrote: > > > with the release of Typo3 4.5, 4.4 becomes "old stable", 4.3 becomes > > "deprecated". Therefore a change at pkg_descr is required. That is > > the only change. > > In such scenarios, please be aware of the following from the Porter's > Handbook: > > "When it makes sense to do so, users can be warned about a pending > port removal with DEPRECATED and EXPIRATION_DATE. The former is > simply a string stating why the port is scheduled for removal; the > latter is a string in ISO 8601 format (-MM-DD). Both will be > shown to the user." Good point, I'll add DEPRECATED. Would it make sense to have the making process sleep for a few seconds or have the user to press a key before proceeding? If I didn't wait for the lines I wouldn't really have noticed it. ___ 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"
PR153950, Repocopy complete but port not available yet
Hi, http://www.freebsd.org/cgi/query-pr.cgi?pr=153950 The repocopy is complete but the port is not available yet. A few poeple already emailed me so I just would like to know why it is not available yet. Due to the upcoming release of 8.2? Thanks, Helmut ___ 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: PR153950, Repocopy complete but port not available yet
Mark Linimon wrote: > On Fri, Feb 04, 2011 at 07:07:40PM +0000, Helmut Schneider wrote: > > The repocopy is complete but the port is not available yet. A few > > poeple already emailed me so I just would like to know why it is not > > available yet. Due to the upcoming release of 8.2? > > No, adding new ports is allowed during most of the release cycle. > > I'll forward your email to the committer who asked for the repocopy. OK, thanks. ___ 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"
Makefile, ${VARIABLE}= vs. ${VARIABLE}?=
Hi, [helmut@BSDHelmut ~]$ grep -ir latest /usr/ports/www/apache2? /usr/ports/www/apache20/Makefile:LATEST_LINK= apache20 /usr/ports/www/apache22/Makefile:LATEST_LINK?= apache22 [helmut@BSDHelmut ~]$ So, what's the difference between e.g. "LATEST_LINK=" and "LATEST_LINK?="? Thanks, Helmut ___ 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: Makefile, ${VARIABLE}= vs. ${VARIABLE}?=
Chris Rees wrote: > On 13 February 2011 14:14, Helmut Schneider wrote: > > [helmut@BSDHelmut ~]$ grep -ir latest /usr/ports/www/apache2? > > /usr/ports/www/apache20/Makefile:LATEST_LINK= apache20 > > /usr/ports/www/apache22/Makefile:LATEST_LINK?= apache22 > > [helmut@BSDHelmut ~]$ > > > > So, what's the difference between e.g. "LATEST_LINK=" and > > "LATEST_LINK?="? > > ?= can be overridden in make.conf or on the command line. Is it up to the maintainer to decide which variables shall be overwritable, or are there rules? ___ 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"
Update of ImageMagick to 6.6.7.10, dependencies
Hi, I updated ImageMagick from 6.6.6.10 to 6.6.7.10 and a *bunch* of new ports were installed[1]. Holy...!! Are they really necessary? Thanks, Helmut [1] ORBit2-2.14.19 atk-1.32.0 compositeproto-0.4.2 cups-client-1.4.6 damageproto-1.2.1 dbus-glib-0.88 dconf-0.5.1_3 docbook-4.1_4 docbook-xsl-1.75.2_1 eggdbus-0.6_1 fixesproto-4.1.2 gconf2-2.32.0_2 gdk-pixbuf-2.22.1 gnomehier-2.3_12 gtk-2.22.1_1 gtk-engines2-2.20.2 hicolor-icon-theme-0.12 iso8879-1986_2 libIDL-0.8.14_1 libXcomposite-0.4.3,1 libXcursor-1.1.11 libXdamage-1.1.3 libXfixes-4.0.4 libXi-1.3.2,1 libXinerama-1.1,1 libXrandr-1.3.0 libcroco-0.6.2_1 libgee-0.6.1 libgsf-1.14.19 librsvg2-2.32.1_1 p5-MIME-Tools-5.502,2 polkit-0.99 randrproto-1.3.2 shared-mime-info-0.80 vala-0.10.1 xineramaproto-1.2 xmlcatmgr-2.2 ___ 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: Update of ImageMagick to 6.6.7.10, dependencies
Martin Wilke wrote: > On Thu, Mar 10, 2011 at 7:10 AM, Helmut Schneider > wrote: > > I updated ImageMagick from 6.6.6.10 to 6.6.7.10 and a bunch of new > > ports were installed[1]. Holy...!! Are they really necessary? > > thats happend because svg is now enabled by default, xfce requested > that. A hint at UPDATING would have been nice, I run/ran ImageMagick only because of MediaWiki/Typo3... :) ___ 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: Update of ImageMagick to 6.6.7.10, dependencies
Anton Shterenlikht wrote: > On Wed, Mar 09, 2011 at 11:32:25PM +0000, Helmut Schneider wrote: > > Martin Wilke wrote: > > > > > On Thu, Mar 10, 2011 at 7:10 AM, Helmut Schneider > > > wrote: > > > > I updated ImageMagick from 6.6.6.10 to 6.6.7.10 and a bunch of > > > > new ports were installed[1]. Holy...!! Are they really > > > > necessary? > > > > > > thats happend because svg is now enabled by default, xfce > > > requested that. > > > > A hint at UPDATING would have been nice, I run/ran ImageMagick only > > because of MediaWiki/Typo3... :) > > svg is cool! I have no doubt and I really appreciate the "Fresh Blood" initiative... > Give it a go. ...but ImageMagick is only an optional dependency for Typo3 I maintain and... > Firefox has now (or maybe had for some time) > a native(?) svn engine. I like it! ...most of "my" users won't run Typo3 *and* X on the same machine. :) ___ 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: Update of ImageMagick to 6.6.7.10, dependencies
Warren Block wrote: > On Thu, 10 Mar 2011, Doug Barton wrote: > > On 03/10/2011 02:40, Helmut Schneider wrote: > > > > > > ...most of "my" users won't run Typo3 and X on the same machine. > > > :) > > > > Sounds like it's time for imagemagick-nox11 slave port. > > Would that be different from turning off the X11 config option of the > ImageMagick port? Can I turn off X11 via (Typo3-)Makefile? ___ 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: Update of ImageMagick to 6.6.7.10, dependencies
Doug Barton wrote: > On 03/10/2011 13:29, Warren Block wrote: > > On Thu, 10 Mar 2011, Doug Barton wrote: > > > On 03/10/2011 02:40, Helmut Schneider wrote: > > > > > > > > ...most of "my" users won't run Typo3 and X on the same > > > > machine. :) > > > > > > Sounds like it's time for imagemagick-nox11 slave port. > > > > Would that be different from turning off the X11 config option of > > the ImageMagick port? > > The idea of having a slave port would be to allow ports like typo3 to > depend on it directly, and reduce the chances of user confusion. Where should I request/ask for a nox11 port? (And no, ImageMagick, even a "simple" subport, is nothing I can maintain) ___ 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: Update of ImageMagick to 6.6.7.10, dependencies
David Demelier wrote: > On 10/03/2011 00:10, Helmut Schneider wrote: > > I updated ImageMagick from 6.6.6.10 to 6.6.7.10 and a bunch of new > > ports were installed[1]. Holy...!! Are they really necessary? > > Try defining WITHOUT_GCONF=yes in your /etc/make.conf, SVG support > need librsvg which needs libgsf and this one require a lot of gnome > dependency if gconf is added. > > So add this knob and you will have SVG support without gnome > dependency :) Well, Thanks, but I'm writing this as maintainer, not as user. So I guess that solution is not suitable here. :) ___ 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] Ports Infrastructure Changes
Doug Barton wrote: > On 03/23/2011 03:48, Peter Jeffery wrote: > > If I was looking for the Opera port, I'd look in www-clients and if > > it wasn't in there then the next thing that I would be doing is hand > > searching the INDEX file > > cd /usr/ports/ && make search name=opera This would be a good time to include ports-mgmt/pkg_search into the base system... ___ 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"
${CD}
Hi,
I need 'cd' in my Makefile. It seems that the variable ${CD} is not
defined and people are using 'cd' instead.
Is there a certain reason for that?
Thanks, Helmut
___
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: ${CD}
Doug Barton wrote:
> On 05/24/2011 12:39, Helmut Schneider wrote:
> > I need 'cd' in my Makefile. It seems that the variable ${CD} is not
> > defined and people are using 'cd' instead.
> >
> > Is there a certain reason for that?
>
> Probably because there is no point in making a variable for it? :)
OK, seems I've been fooled:
[helmut@BSDHelmut ~]$ which cd
/usr/bin/cd
[helmut@BSDHelmut ~]$
I too late looked at /usr/bin/cd a bit closer:
[helmut@BSDHelmut ~]$ file /usr/bin/cd
/usr/bin/cd: POSIX shell script text executable
[helmut@BSDHelmut ~]$ cat /usr/bin/cd
#!/bin/sh
# $FreeBSD: src/usr.bin/alias/generic.sh,v 1.2.10.1.6.1 2010/12/21
17:09:25 kensmith Exp $
# This file is in the public domain.
builtin ${0##*/} ${1+"$@"}
[helmut@BSDHelmut ~]$
___
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"
Perl is non-threaded. Building ImageMagick without threads.
Hi, While updating ImageMagick from 6.6.7.10 to 6.7.0-2 the build process says: ===> Configuring for ImageMagick-nox11-6.7.0.2 ### NOTICE: Perl is non-threaded. Building ImageMagick without threads. ### But: [helmut@BSDHelmut832 ~]$ pkg_info | grep perl perl-threaded-5.10.1_3 Practical Extraction and Report Language [helmut@BSDHelmut832 ~]$ uname -rms FreeBSD 8.2-RELEASE-p1 i386 [helmut@BSDHelmut832 ~]$ Any hints? Thanks Helmut ___ 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: Perl is non-threaded. Building ImageMagick without threads.
Daniel Nebdal wrote:
> On Sun, May 29, 2011 at 3:27 PM, Robert Huff
> wrote:
> >
> > Helmut Schneider writes:
> >
> >> While updating ImageMagick from 6.6.7.10 to 6.7.0-2 the build
> >> process says:
> > >
> >> ===> Configuring for ImageMagick-nox11-6.7.0.2
> >>
> ###
> >> NOTICE: Perl is non-threaded. Building ImageMagick without
> >> threads.
> ###
> > >
> >> But:
> > >
> >> [helmut@BSDHelmut832 ~]$ pkg_info | grep perl
> >> perl-threaded-5.10.1_3 Practical Extraction and Report Language
> >> [helmut@BSDHelmut832 ~]$ uname -rms
> >> FreeBSD 8.2-RELEASE-p1 i386
> >> [helmut@BSDHelmut832 ~]$
> >
> > I have a similar issue:
> >
> > huff@> portupgrade InageMagick-6
> > ** Port marked as IGNORE: graphics/ImageMagick:
> > OpenEXR requires threads. . Perl is non-threaded. Reinstall
> > Perl with threads or undefine WITH_IMAGEMAGICK_PERL ** Listing the
> > failed packages (-:ignored / *:skipped / !:failed) -
> > graphics/ImageMagick (marked as IGNORE) huff@> dir /var/db/pkg |
> > grep perl drwxr-xr-x 2 root wheel 512 May 27 08:09
> > perl-threaded-5.14.0
> >
> > System info:
> >
> > FreeBSD 9.0-CURRENT #0: Mon Apr 18 11:59:37 EDT 2011 amd64
> >
> >
> > Robert Huff
>
>
> Try enabling threading in the ImageMagic port - I ran into this
> earlier, and if I remember it correctly, the error message is a bit
> misleading.
I see:
.if defined(WITH_THREADS)
_IMAGEMAGICK_THREADS=yes
_IMAGEMAGICK_THREADS_MSG=with threads
PERL_THREADED!= ${SH} -c 'case `perl --version` in *freebsd-thread*)
${ECHO_CMD} yes ;; esac'
.else
_IMAGEMAGICK_THREADS=no
_IMAGEMAGICK_THREADS_MSG=without threads
_IMAGEMAGICK_THREADS_IGNORE_MSG=. Define WITH_THREADS
.endif
PERL_THREADED is only set when also WITH_THREADS is set. Maybe should
be something like
--- Makefile.org2011-05-30 20:24:54.0 +0200
+++ Makefile2011-05-30 20:46:50.0 +0200
@@ -80,10 +80,11 @@
CONFIGURE_ARGS+= --disable-hdri
#.endif
+PERL_THREADED!=${SH} -c 'case `perl --version` in
*freebsd-thread*) ${ECHO_CMD} yes ;; esac'
+
.if defined(WITH_THREADS)
_IMAGEMAGICK_THREADS=yes
_IMAGEMAGICK_THREADS_MSG=with threads
-PERL_THREADED!=${SH} -c 'case `perl --version` in
*freebsd-thread*) ${ECHO_CMD} yes ;; esac'
.else
_IMAGEMAGICK_THREADS=no
_IMAGEMAGICK_THREADS_MSG=without threads
___
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"
[squid 3.1.14] fails to start
Hi, after upgrading squid from 3.1.12 to 3.1.14 I encounter the following error: Starting squid. 2011/07/06 22:13:21| cache_cf.cc(376) parseOneConfigFile: squid.conf:20 unrecognized: 'useragent_log' 2011/07/06 22:13:21| cache_cf.cc(376) parseOneConfigFile: squid.conf:21 unrecognized: 'referer_log' /etc/rc: WARNING: failed to start squid [helmut@BSDHelmut ~]$ sudo grep -Eir '(useragent_log|referer_log)' /usr/local/etc/squid/squid.conf useragent_log /var/squid/logs/usragent.log referer_log /var/squid/logs/referer.log [helmut@BSDHelmut ~]$ Regression in squid?! Fallback to 3.1.12 resolves the problem. Thanks, Helmut ___ 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: [squid 3.1.14] fails to start
Florian Smeets wrote: > On 06.07.11 22:33, Helmut Schneider wrote: > > after upgrading squid from 3.1.12 to 3.1.14 I encounter the > > following error: > > > > Starting squid. > > 2011/07/06 22:13:21| cache_cf.cc(376) parseOneConfigFile: > > squid.conf:20 unrecognized: 'useragent_log' > > 2011/07/06 22:13:21| cache_cf.cc(376) parseOneConfigFile: > > squid.conf:21 unrecognized: 'referer_log' > > /etc/rc: WARNING: failed to start squid > > > > [helmut@BSDHelmut ~]$ sudo grep -Eir '(useragent_log|referer_log)' > > /usr/local/etc/squid/squid.conf > > useragent_log /var/squid/logs/usragent.log > > referer_log /var/squid/logs/referer.log > > [helmut@BSDHelmut ~]$ > > Are you sure you still have the required knobs set? > > .if defined(WITH_SQUID_REFERER_LOG) > > .if defined(WITH_SQUID_USERAGENT_LOG) Weird. I did a 'portupgrade' from 3.1.12 but the knobs obviously got lost. After recompiling with WITH_ it works now as expected. Thanks, Helmut ___ 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"
net-snmpd56 port
Hi, seems I'm not the only one with problems with net-snmpd 5.7. I created a new PR a few seconds ago because snmpd core dumps and there are still a few PRs in the pipe. While it is only human that errors happen may I suggest to have a net-snmpd56 port in addition to the most recent one? Thanks, Helmut ___ 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: net-snmpd56 port
Helmut Schneider wrote: > seems I'm not the only one with problems with net-snmpd 5.7. I created > a new PR a few seconds ago because snmpd core dumps and there are > still a few PRs in the pipe. > > While it is only human that errors happen may I suggest to have a > net-snmpd56 port in addition to the most recent one? net-snmpd55 of course... ___ 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"
Big patches
Hi, I've been told that dynamic pkg-plists are bad or at least should be avoided´at most costs. Now, all my patches for Typo3 seem blocked by a "SPAM Filter" or at least take 2 days until I get reply. See PR159878-81, I submitted the patches on tuesday. So, what should I do? Still create full pkg-plists and hope that the patch passes the FreeBSD PR system or fall back to dynamic pkg-plists? Thanks, Helmut ___ 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: Big patches
Mark Linimon wrote: > Sorry, I did not see your message and emailed you separately. > > GNATS has a spamcatcher for > 500k messages (mostly this catches > viruses). Normally I handle such PRs manually before the cleanup > process runs, but I forgot to do it this time. (I only took a > glance.) > > Does the plist change dramatically every time the ports are updated? Yes. > Is there any way around this if so? Such large changes put stress > not only on GNATS (it is, after all, a database), but also on the CVS > repository when the updates are committed. I generated the plist in the past but not very long time ago I was told (and let me quote): "generation the plist is not considered a good practice" :) ___ 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: Big patches
Chris Rees wrote: > On 19 August 2011 08:55, Helmut Schneider wrote: > > Mark Linimon wrote: > > > >> Sorry, I did not see your message and emailed you separately. > >> > >> GNATS has a spamcatcher for > 500k messages (mostly this catches > >> viruses). Normally I handle such PRs manually before the cleanup > >> process runs, but I forgot to do it this time. (I only took a > >> glance.) > >> > >> Does the plist change dramatically every time the ports are > >> updated? > > > > Yes. > > > >> Is there any way around this if so? Such large changes put stress > >> not only on GNATS (it is, after all, a database), but also on the > >> CVS repository when the updates are committed. > > > > I generated the plist in the past but not very long time ago I was > > told (and let me quote): "generation the plist is not considered a > > good practice" :) > > > > Except when the plist changes dramatically. See Perter's Handbook :) Will the maintainer who proposed me to create a static plist please stand up, please stand up, please stand up? ;) ___ 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: Big patches
Boris Samorodov wrote: > On Thu, 18 Aug 2011 19:11:22 + (UTC) Helmut Schneider wrote: > > > I've been told that dynamic pkg-plists are bad or at least should be > > avoided´at most costs. > > > Now, all my patches for Typo3 seem blocked by a "SPAM Filter" or at > > least take 2 days until I get reply. See PR159878-81, I submitted > > the patches on tuesday. > > > So, what should I do? Still create full pkg-plists and hope that the > > patch passes the FreeBSD PR system or fall back to dynamic > > pkg-plists? > > You may try to reduce pkg-plist changes. Are you speaking about > www/typo* ports? If yes, those ports have hardcoded PORTVERSION > at pkg-plist. One can use make variables to dramatically reduce > pkg-plist changes: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/plist.html#PLIST-SUB "dramatically reduce"? How? Currently it seems it gets even bigger: [helmut@BSDHelmut ~]$ ls -s /usr/ports/www/typo3.org/pkg-plist 592 /usr/ports/www/typo3.org/pkg-plist [helmut@BSDHelmut ~]$ ls -s /usr/ports/www/typo3/pkg-plist 672 /usr/ports/www/typo3/pkg-plist [helmut@BSDHelmut ~]$ ___ 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: Big patches
Chris Rees wrote: > On 19 August 2011 11:18, Helmut Schneider wrote: > > Boris Samorodov wrote: > >> You may try to reduce pkg-plist changes. Are you speaking about > >> www/typo* ports? If yes, those ports have hardcoded PORTVERSION > >> at pkg-plist. One can use make variables to dramatically reduce > >> pkg-plist changes: > > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/plist.html#PLIST-SUB > > > > "dramatically reduce"? How? Currently it seems it gets even bigger: > > > > [helmut@BSDHelmut ~]$ ls -s /usr/ports/www/typo3.org/pkg-plist > > 592 /usr/ports/www/typo3.org/pkg-plist > > [helmut@BSDHelmut ~]$ ls -s /usr/ports/www/typo3/pkg-plist > > 672 /usr/ports/www/typo3/pkg-plist > > [helmut@BSDHelmut ~]$ > > > > Just the once, but then the changes each time it's updated are > smaller. I see. I patched genplist to do the job. Thanks. ___ 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"
cacti broken in 6.3?
Hi, I started a long thread at http://forums.cacti.net/about25481.html but it turns out that FreeBSD 6.3 might be the problem. FreeBSD 6.2 and 7.0-RC1 (see below) are not affected. Here is what I did: I had an existing cacti infrastructure/cacti server on FreeBSD 6.2. Everything was fine and I upraded to 6.3-RELEASE a few days ago. I recognized that I can't query some values anymore. These values are e.g.: SNMP - Get Mounted Partitions SNMP - Get Processor Information Both show "Success [0 Items, 0 Rows]" even when querying localhost. I tried on 3 different hosts (all running 6.3-RELEASE). Now I set up two virtual machines, one with 6.2-RELEASE-p10 and one with 7.0-RC1. Both query the same targets as the 6.3 ones do and return the expected value: Success [33 Items, 11 Rows] Success [1 Item, 1 Row] I read about the problem with 6.3 and nagios (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/119246) and now I'm wondering if there is a similar problem with cacti. Can anyone confirm/disprove? I already recompiled all of the cacti stuff recursive without success. As said before, on 6.2 and 7.0 cacti still works fine but due to lack of time I wasn't able to set up 6.3 in a VM from scratch yet. Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cacti broken in 6.3?
Edwin Groothuis <[EMAIL PROTECTED]> wrote: On Wed, Jan 30, 2008 at 10:22:31PM +0100, Helmut Schneider wrote: I started a long thread at http://forums.cacti.net/about25481.html but it turns out that FreeBSD 6.3 might be the problem. FreeBSD 6.2 and 7.0-RC1 (see below) are not affected. Here is what I did: Silly question from me maybe: did you recompile the net-snmp and phpX-snmp libraries? Yes, I forced a portupgrade of net-snmp-5.3.2_1 and php5-snmp-5.2.5_1 and I even completly removed cacti, .*PHP.* and .*snmp.* and did a 'portinstall -Rf cacti'. I also tried with cacti 0.8.7 and 0.8.6j. I also dropped the cacti database and recreated it. Does your question imply that you are running cacti on 6.3 without problems? -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cacti broken in 6.3?
Edwin Groothuis <[EMAIL PROTECTED]> wrote: On Wed, Jan 30, 2008 at 11:33:37PM +0100, Helmut Schneider wrote: Edwin Groothuis <[EMAIL PROTECTED]> wrote: >On Wed, Jan 30, 2008 at 10:22:31PM +0100, Helmut Schneider wrote: >>I started a long thread at http://forums.cacti.net/about25481.html but >>it turns out that FreeBSD 6.3 might be the problem. FreeBSD 6.2 and >>7.0-RC1 (see below) are not affected. Here is what I did: > >Silly question from me maybe: did you recompile the net-snmp and >phpX-snmp libraries? Yes, I forced a portupgrade of net-snmp-5.3.2_1 and php5-snmp-5.2.5_1 and I even completly removed cacti, .*PHP.* and .*snmp.* and did a 'portinstall -Rf cacti'. I also tried with cacti 0.8.7 and 0.8.6j. I also dropped the cacti database and recreated it. Does your question imply that you are running cacti on 6.3 without problems? No, but I have planned an upgrade of a lot of machines this weekend, including one which runs Cacti :-) The only reason I wondered if net-snmp was recompiled is because it takes some low-level things like CPU usage and memory, so I thought maybe it is related. I'm a bit concerned as I can't reproduce the problem on a freshly installed 6.3. Currently I'm rebuilding *all* ports on the system (the cacti server itself is the problem, not the clients) and if that doesn't help I will rebuild the userland, too. When you upgraded your servers it would be nice to know if it worked for you, or not. I did the upgrade using freebsd-update. Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ntop does not compile on 7.0-RC2
Hi, ntop stops with: [...] then mv -f ".deps/iface.Tpo" ".deps/iface.Plo"; else rm -f ".deps/iface.Tpo"; exit 1; fi cc -DHAVE_CONFIG_H -I. -I. -I. -I. -I/usr -I/usr/include -DINET6 -O2 -Dfreebsd7 -DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.8/BSDPAN -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/lib/perl5/5.8.8/mach/CORE -I. -I/usr/local/include -DFREEBSD -I/usr/local/include -I/usr/local/include -I/usr/include -g -O2 -fno-strict-aliasing -pipe -I/usr/local/include -g -Wshadow -Wpointer-arith -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fPIC -DPIC -MT iface.lo -MD -MP -MF .deps/iface.Tpo -c iface.c -fPIC -DPIC -o .libs/iface.o In file included from /usr/local/include/net-snmp/utilities.h:54, from /usr/local/include/net-snmp/net-snmp-includes.h:78, from iface.c:766: /usr/local/include/net-snmp/library/container.h: In function 'CONTAINER_FREE': /usr/local/include/net-snmp/library/container.h:416: error: lvalue required as left operand of assignment In file included from /usr/local/include/net-snmp/mib_api.h:24, from /usr/local/include/net-snmp/net-snmp-includes.h:81, from iface.c:766: /usr/local/include/net-snmp/library/parse.h:32:1: warning: "MAXLABEL" redefined In file included from /usr/include/arpa/nameser.h:579, from ntop.h:321, from iface.c:26: /usr/include/arpa/nameser_compat.h:104:1: warning: this is the location of the previous definition gmake[2]: *** [iface.lo] Error 1 gmake[2]: Leaving directory `/usr/ports/net/ntop/work/ntop-3.3' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/net/ntop/work/ntop-3.3' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/net/ntop. *** Error code 1 Stop in /usr/ports/net/ntop. Bug or a local problem? Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntop does not compile on 7.0-RC2
James <[EMAIL PROTECTED]> wrote: On Sun, 2008-02-17 at 17:20 +0100, Helmut Schneider wrote: Hi, ntop stops with: [...] then mv -f ".deps/iface.Tpo" ".deps/iface.Plo"; else rm -f ".deps/iface.Tpo"; exit 1; fi cc -DHAVE_CONFIG_H -I. -I. -I. -I. -I/usr -I/usr/include -DINET6 -O2 -Dfreebsd7 -DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.8/BSDPAN -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/lib/perl5/5.8.8/mach/CORE -I. -I/usr/local/include -DFREEBSD -I/usr/local/include -I/usr/local/include -I/usr/include -g -O2 -fno-strict-aliasing -pipe -I/usr/local/include -g -Wshadow -Wpointer-arith -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fPIC -DPIC -MT iface.lo -MD -MP -MF .deps/iface.Tpo -c iface.c -fPIC -DPIC -o .libs/iface.o In file included from /usr/local/include/net-snmp/utilities.h:54, from /usr/local/include/net-snmp/net-snmp-includes.h:78, from iface.c:766: /usr/local/include/net-snmp/library/container.h: In function 'CONTAINER_FREE': /usr/local/include/net-snmp/library/container.h:416: error: lvalue required as left operand of assignment In file included from /usr/local/include/net-snmp/mib_api.h:24, from /usr/local/include/net-snmp/net-snmp-includes.h:81, from iface.c:766: /usr/local/include/net-snmp/library/parse.h:32:1: warning: "MAXLABEL" redefined In file included from /usr/include/arpa/nameser.h:579, from ntop.h:321, from iface.c:26: /usr/include/arpa/nameser_compat.h:104:1: warning: this is the location of the previous definition gmake[2]: *** [iface.lo] Error 1 gmake[2]: Leaving directory `/usr/ports/net/ntop/work/ntop-3.3' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/net/ntop/work/ntop-3.3' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/net/ntop. *** Error code 1 Stop in /usr/ports/net/ntop. Bug or a local problem? Local problem. I don'thave a net-snmp directory installed; looks like some library there is clobbering a needed definition. Indeed, net-snmp breaks ntop. I removed net-snmp and ntop compiles fine. Installed net-snmp and rebuilded ntop, fails. What should I do now, report the maintainer of ntop and/or net-snmp? -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntop does not compile on 7.0-RC2
Wesley Shields <[EMAIL PROTECTED]> wrote: On Mon, Feb 18, 2008 at 08:02:13AM -0700, James wrote: Sounds like an entirely reasonable course of action. The maintainers' email addresses ought to be in the Makefile for each port. That would be me. :) I imagine it's the ntop person you want to report to. If other ports install fine, then net-snmp is also (probably) installing as it should and the ntop Makefile just needs to be tweaked. I'll look into this, but any relevant information should be submitted as a PR so there is a more permanent record of it. I'll go about getting it fixed as time permits. done. For more information don't hesitate to contact me. Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[portupgrade] Argument must be String class object
Hi, I have a few problems with portupgrade, some ports fail with error above: [EMAIL PROTECTED] ~]# portupgrade -fPP snort-2.7.0.1_1 postfix-2.4.6,1 apache-2.0.63 ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! www/apache20 (apache-2.0.63) (Argument must be String class object.) ! security/snort (snort-2.7.0.1_1) (Argument must be String class object.) ! mail/postfix (postfix-2.4.6,1)(Argument must be String class object.) [EMAIL PROTECTED] ~]# The package itself is fine: [EMAIL PROTECTED] ~]# rm /usr/ports/packages/All/apache-2.0.63.tbz [EMAIL PROTECTED] ~]# pkg_delete -f apache-2.0.63 pkg_delete: package 'apache-2.0.63' is required by these other packages and may not be deinstalled (but I'll delete it anyway): [...] pkg_delete: unable to completely remove directory '/usr/local/www/icons-dist' pkg_delete: unable to completely remove directory '/usr/local/www/data-dist' pkg_delete: unable to completely remove directory '/usr/local/www/cgi-bin-dist' ===> If you plan to do not reinstall apache2, you can safely remove /usr/local/etc/apache2. pkg_delete: couldn't entirely delete package (perhaps the packing list is incorrectly specified?) [EMAIL PROTECTED] ~]# portinstall -PP apache-2.0.63 [Updating the pkgdb in /var/db/pkg ... - 276 packages found (-1 +0) (...) done] [Gathering depends for www/apache20 .. done] ---> Checking for the latest package of 'www/apache20' ---> Fetching the package(s) for 'apache-2.0.63' (www/apache20) ---> Fetching apache-2.0.63 /var/tmp/portupgrade7ddeL9hD/apache-2.0.63.tbz100% of 2437 kB 4001 kBps ---> Downloaded as apache-2.0.63.tbz ---> Identifying the package /var/tmp/portupgrade7ddeL9hD/apache-2.0.63.tbz ---> Saved as /usr/ports/packages/All/apache-2.0.63.tbz ---> Found a package of 'www/apache20': /usr/ports/packages/All/apache-2.0.63.tbz (apache-2.0.63) ---> Located a package version 2.0.63 (/usr/ports/packages/All/apache-2.0.63.tbz) ---> Installing 'apache-2.0.63' from a package ---> Installing the new version via the package [Updating the pkgdb in /var/db/pkg ... - 277 packages found (-0 +1) . done] [EMAIL PROTECTED] ~]# This happens with 6.3 and 7.0. Any ideas? Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [portupgrade] Argument must be String class object
Stuart Barkley <[EMAIL PROTECTED]> wrote: On Sat, 1 Mar 2008 at 16:05 +0100, Helmut Schneider wrote: I have a few problems with portupgrade, some ports fail with error above: [EMAIL PROTECTED] ~]# portupgrade -fPP snort-2.7.0.1_1 postfix-2.4.6,1 apache-2.0.63 ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! www/apache20 (apache-2.0.63) (Argument must be String class object.) ! security/snort (snort-2.7.0.1_1) (Argument must be String class object.) ! mail/postfix (postfix-2.4.6,1) (Argument must be String class object.) [EMAIL PROTECTED] ~]# I've been seeing the same problem lately (probably since the update to 2.4). It seems to be related to having MAKE_ARGS overrides set in /usr/local/etc/pkgtools.conf. So far I haven't looked much further at this problem since portupgrade is being actively worked upon by others. I build packages on one machine and then use the packages to install on my various other machines. I use the same pkgtools.conf on each machine. I created a PR. -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [portupgrade] Argument must be String class object
Stuart Barkley <[EMAIL PROTECTED]> wrote: On Sat, 1 Mar 2008 at 16:05 +0100, Helmut Schneider wrote: I have a few problems with portupgrade, some ports fail with error above: [EMAIL PROTECTED] ~]# portupgrade -fPP snort-2.7.0.1_1 postfix-2.4.6,1 apache-2.0.63 ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! www/apache20 (apache-2.0.63) (Argument must be String class object.) ! security/snort (snort-2.7.0.1_1) (Argument must be String class object.) ! mail/postfix (postfix-2.4.6,1) (Argument must be String class object.) [EMAIL PROTECTED] ~]# I've been seeing the same problem lately (probably since the update to 2.4). It seems to be related to having MAKE_ARGS overrides set in /usr/local/etc/pkgtools.conf. So far I haven't looked much further at this problem since portupgrade is being actively worked upon by others. I build packages on one machine and then use the packages to install on my various other machines. I use the same pkgtools.conf on each machine. I created a PR. -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mailman2.1.x and python2.5 in a jail
Hi,
I'm trying to setup mailman and python2.5 in a jail for a long time. With
python2.4 it works like a charm but not with python2.5. Maybe someone here
has a clue what's wrong. I asked 6 months ago at the mailman mailing list
but without success:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg46480.html, Removing
python2.4 from the system does not solve the problem.
#!/bin/sh
export JAIL="/home/python25"
mkdir -p $JAIL/usr/local/lib $JAIL/usr/local/bin $JAIL/lib $JAIL/usr/lib
$JAIL/libexec
cp -rp /usr/local/mailman $JAIL/usr/local/
cp -rp /usr/local/lib/python2.4 $JAIL/usr/local/lib/
cp -rp /usr/local/lib/python2.5 $JAIL/usr/local/lib/
cp -p /usr/local/bin/python2.4 $JAIL/usr/local/bin/
cp -p /usr/local/bin/python2.5 $JAIL/usr/local/bin/
With the help of 'ldd /usr/local/bin/python2.4' and 'ldd
/usr/local/bin/python2.5':
cp -p /lib/libutil.so.7 $JAIL/lib/
cp -p /usr/lib/libstdc++.so.6 $JAIL/usr/lib/
cp -p /lib/libm.so.5 $JAIL/lib/
cp -p /lib/libgcc_s.so.1 $JAIL/lib/
cp -p /lib/libthr.so.3 $JAIL/lib/
cp -p /lib/libc.so.7 $JAIL/lib/
cp -p /lib/libutil.so.7 $JAIL/lib/
cp -p /lib/libm.so.5 $JAIL/lib/
cp -p /lib/libthr.so.3 $JAIL/lib/
cp -p /lib/libc.so.7 $JAIL/lib/
cp -p /libexec/ld-elf.so.1 $JAIL/libexec/
If I start e.g. mailmanclt from jail I get this:
[EMAIL PROTECTED] ~]# chroot -u root /home/python25/
/usr/local/mailman/bin/mailmanctl
Traceback (most recent call last):
File "/usr/local/mailman/bin/mailmanctl", line 107, in
from Mailman import Utils
File "/usr/local/mailman/Mailman/Utils.py", line 32, in
import sha
File "/usr/local/lib/python2.5/sha.py", line 6, in
from hashlib import sha1 as sha
File "/usr/local/lib/python2.5/hashlib.py", line 133, in
md5 = __get_builtin_constructor('md5')
File "/usr/local/lib/python2.5/hashlib.py", line 60, in
__get_builtin_constructor
import _md5
ImportError: No module named _md5
[EMAIL PROTECTED] ~]#
When I edit '/home/python25/usr/local/mailman/bin/mailmanctl' and change the
first line '#! /usr/local/bin/python2.5' to '#! /usr/local/bin/python2.4'
everything works fine.
I appreciate any ideas.
Thanks, Helmut
--
No Swen today, my love has gone away
My mailbox stands for lorn, a symbol of the dawn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mailman2.1.x and python2.5 in a jail
Alex Vasylenko <[EMAIL PROTECTED]> wrote:
Helmut Schneider wrote:
[EMAIL PROTECTED] ~]# chroot -u root /home/python25/
/usr/local/mailman/bin/mailmanctl
Traceback (most recent call last):
File "/usr/local/mailman/bin/mailmanctl", line 107, in
from Mailman import Utils
File "/usr/local/mailman/Mailman/Utils.py", line 32, in
import sha
File "/usr/local/lib/python2.5/sha.py", line 6, in
from hashlib import sha1 as sha
File "/usr/local/lib/python2.5/hashlib.py", line 133, in
md5 = __get_builtin_constructor('md5')
File "/usr/local/lib/python2.5/hashlib.py", line 60, in
__get_builtin_constructor
import _md5
ImportError: No module named _md5
[EMAIL PROTECTED] ~]#
you would need all libraries required by
/usr/local/lib/python2.5/lib-dynload/*.so available in the jail too.
Works fine, thanks a lot.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
net-snmp5.4.x unusable, PR times out, what should I do next?
Hi, first of all I fully understand that all ports are maintained by volunteers. I also appreciate their work very much. net-snmp5.4.x is (only for me?!) unusable. Some OIDs don't exist anymore, some OIDs report wrong values. I tried to bypass those problems by still using net-snmp5.3.x (which still is fine) but more and more ports depend on 5.4. I already sent mails to the maintainer and created a PR (ports/123276, ports/122263) but both timed out. I don't blame anyone, I'm sure all of the maintainers have a lot of things to. Rather I would like to know what I should do/can do next. As I'm using snmp with cacti and nagios to monitor some systems I rely on snmp a bit. I'm not able to fix those things myself so I feel a bit lost. Thanks, Helmut ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
INDEX-7 outdated?
Hi, Is this a local problem? [EMAIL PROTECTED] /usr/ports]# grep PORTREVISION sysutils/screen/Makefile PORTREVISION= 4 [EMAIL PROTECTED] /usr/ports]# make fetchindex [EMAIL PROTECTED] /usr/ports]# grep -ir ^screen-4.0.3 /usr/ports/INDEX-7 screen-4.0.3_3|/usr/ports/sysutils/screen|/usr/local|A multi-screen window manager|/usr/ports/sysutils/screen/pkg-descr|[EMAIL PROTECTED]|sysutils|||http://www.gnu.org/software/screen/||| [EMAIL PROTECTED] /usr/ports]# portversion -vl ">" [Updating the portsdb in /usr/ports ... - 18607 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.. . done] clamav-0.93.1 > succeeds port (port has 0.93_1) gtk-2.12.10_2 > succeeds port (port has 2.12.10_1) openldap-client-2.3.42 > succeeds port (port has 2.3.41) p5-version-0.75 > succeeds port (port has 0.74) pecl-APC-3.0.19 > succeeds port (port has 3.0.18_1) screen-4.0.3_4 > succeeds port (port has 4.0.3_3) snort-2.8.2_1 > succeeds port (port has 2.8.1_1) [EMAIL PROTECTED] /usr/ports]# Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: INDEX-7 outdated?
Helmut Schneider <[EMAIL PROTECTED]> wrote: [EMAIL PROTECTED] /usr/ports]# grep PORTREVISION sysutils/screen/Makefile PORTREVISION= 4 [EMAIL PROTECTED] /usr/ports]# make fetchindex [EMAIL PROTECTED] /usr/ports]# grep -ir ^screen-4.0.3 /usr/ports/INDEX-7 screen-4.0.3_3|/usr/ports/sysutils/screen|/usr/local|A multi-screen window manager|/usr/ports/sysutils/screen/pkg-descr|[EMAIL PROTECTED]|sysuti ls|||http://www.gnu.org/software/screen/||| [EMAIL PROTECTED] /usr/ports]# portversion -vl ">" [Updating the portsdb in /usr/ports ... - 18607 port entries found .1000.2000.3000.4000.5000. 6000.7000.8000.9000.1.11000... ..12000.13000.14000.15000.16000... ..17000.18000.. . done] clamav-0.93.1 > succeeds port (port has 0.93_1) gtk-2.12.10_2 > succeeds port (port has 2.12.10_1) openldap-client-2.3.42 > succeeds port (port has 2.3.41) p5-version-0.75 > succeeds port (port has 0.74) pecl-APC-3.0.19 > succeeds port (port has 3.0.18_1) screen-4.0.3_4 > succeeds port (port has 4.0.3_3) snort-2.8.2_1 > succeeds port (port has 2.8.1_1) [EMAIL PROTECTED] /usr/ports]# Whoever fixed it, thanks. -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to upgrade openssl after upgrading from 6.2 to 7.0
Attos <[EMAIL PROTECTED]> wrote: I just upgraded my workstation from 6.2 to 7.0 but I haven't been able to upgrade all the ports. OpenSSL is giving me problems when trying to upgrade (with portupgrade). The message I get is that the it's marked as ignore because it conflicts with the base: # portupgrade security/openssl-stable ** Port marked as IGNORE: security/openssl-stable: Conflicts with version in the base ** Listing the failed packages (-:ignored / *:skipped / !:failed) - security/openssl-stable (marked as IGNORE) How do I fix this? pkg_delete openssl-stable pkgdb -Fu openssl-stable is 0.9.7m while 7.0 ships with 0.9.8e. Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Apache
Dennis Kirschling <[EMAIL PROTECTED]> wrote: I have a wealth of experience with SCO products, but I have to admit I am stumped with BSD and specifically upgrading a customers Apache from 2.0.55 to 2.0.63 on BSD 5.4. I have downloaded the product, unsipped it and extracted the tar volume. Where do I go from here?. I have read many articles until I'm blue in the face. Please read on here: http://www.freebsd.org/ports/ portupgrade might also be helpful. See also: http://www.freebsd.org/doc/en/books/handbook/ports-using.html BTW, 5.x is EOL: http://lists.freebsd.org/pipermail/freebsd-security/2008-April/004699.html http://www.freebsd.org/releases/6.3R/installation-i386.html#UPGRADING HTH, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
apache 2.2.22_6 to _8 fails
Hi, ** Detected a package name change: apache (www/apache22) -> 'apache22' (www/apache22) ---> Upgrading 'apache-2.2.22_6' to 'apache22-2.2.22_8' (www/apache22) ---> Building '/usr/ports/www/apache22' with make flags: -DWITH_PROXY -DWITH_PROXY_CONNECT -DWITH_PROXY_FTP -DWITH_PROXY_HTTP -DWITH_LDAP -DWITH_AUTHNZ_LDAP -DWITH_BDB -DWITH_APR_FROM_PORTS ===> Cleaning for apache22-2.2.22_8 > You must check at least one option in the PROXY multi *** Error code 1 The options worked fine up to 2.2.22_6 and I'm not sure how to read the error message. Thanks, Helmut ___ 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: apache 2.2.22_6 to _8 fails
Bryan Drewery wrote: > On 9/8/2012 7:28 AM, Helmut Schneider wrote: > > ** Detected a package name change: apache (www/apache22) -> > > 'apache22' (www/apache22) > > ---> Upgrading 'apache-2.2.22_6' to 'apache22-2.2.22_8' > > (www/apache22) ---> Building '/usr/ports/www/apache22' with make > > flags: -DWITH_PROXY -DWITH_PROXY_CONNECT -DWITH_PROXY_FTP > > -DWITH_PROXY_HTTP -DWITH_LDAP -DWITH_AUTHNZ_LDAP -DWITH_BDB > > -DWITH_APR_FROM_PORTS ===> Cleaning for apache22-2.2.22_8 > > > You must check at least one option in the PROXY multi > > *** Error code 1 > > > > The options worked fine up to 2.2.22_6 and I'm not sure how to read > > the error message. > > It needs you to "upgrade" your selected options to a the new set > available. This is due to the maintainer changing the defaults, > changing options, etc. It needs manual intervention. > > Just re-config: > > make -C /usr/ports/www/apache22 config Thanks, but this really should have been noted in UPGRADING. ___ 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: apache 2.2.22_6 to _8 fails
Hi Olli, olli hauer wrote: > On 2012-09-08 14:28, Helmut Schneider wrote: > > ** Detected a package name change: apache (www/apache22) -> > > 'apache22' (www/apache22) > > ---> Upgrading 'apache-2.2.22_6' to 'apache22-2.2.22_8' > > (www/apache22) ---> Building '/usr/ports/www/apache22' with make > > flags: -DWITH_PROXY -DWITH_PROXY_CONNECT -DWITH_PROXY_FTP > > -DWITH_PROXY_HTTP -DWITH_LDAP -DWITH_AUTHNZ_LDAP -DWITH_BDB > > -DWITH_APR_FROM_PORTS ===> Cleaning for apache22-2.2.22_8 > > > You must check at least one option in the PROXY multi > > *** Error code 1 > > > > The options worked fine up to 2.2.22_6 and I'm not sure how to read > > the error message. > > with options NG the WITH... parameters do no longer work. > If you want to specify them in make.conf you have to do it this way I'm using pkgtools.conf, removing -DWITH_PROXY seems to do the trick (I also removed the typo of DBD and the obsolete DWITH_APR_FROM_PORTS, but they are not related). > apache22_SET=PROXY PROXY_CONNECT PROXY_FTP ... > > The downside with options NG is if you already have an OPTIONSFILE > the make.conf parameters will have a lower priority. Please note this in UPDATING. Thanks, Helmut ___ 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: apache 2.2.22_6 to _8 fails
olli hauer wrote: > On 2012-09-08 14:57, Helmut Schneider wrote: > > Hi Olli, > > > > olli hauer wrote: > > > >> On 2012-09-08 14:28, Helmut Schneider wrote: > >>> ** Detected a package name change: apache (www/apache22) -> > >>> 'apache22' (www/apache22) > >>> ---> Upgrading 'apache-2.2.22_6' to 'apache22-2.2.22_8' > >>> (www/apache22) ---> Building '/usr/ports/www/apache22' with make > >>> flags: -DWITH_PROXY -DWITH_PROXY_CONNECT -DWITH_PROXY_FTP > >>> -DWITH_PROXY_HTTP -DWITH_LDAP -DWITH_AUTHNZ_LDAP -DWITH_BDB > >>> -DWITH_APR_FROM_PORTS ===> Cleaning for apache22-2.2.22_8 > >>> > You must check at least one option in the PROXY multi > >>> *** Error code 1 > > > > > >>> The options worked fine up to 2.2.22_6 and I'm not sure how to > >>> read the error message. > > > > >> with options NG the WITH... parameters do no longer work. > >> If you want to specify them in make.conf you have to do it this way > > > > I'm using pkgtools.conf, removing -DWITH_PROXY seems to do the > > trick (I also removed the typo of DBD and the obsolete > > DWITH_APR_FROM_PORTS, but they are not related). > > > >> apache22_SET=PROXY PROXY_CONNECT PROXY_FTP ... > > > > >> The downside with options NG is if you already have an OPTIONSFILE > >> the make.conf parameters will have a lower priority. > > > > Please note this in UPDATING. > > That's not an apache limitation, it comes from options NG and is > already documented on many places and was also discussed a view times > on the list. > > Only a view interesting links > http://wiki.freebsd.org/Ports/Options/OptionsNG > http://lists.freebsd.org/pipermail/freebsd-ports/2012-July/077016.html > http://lists.freebsd.org/pipermail/freebsd-ports/2012-June/076241.html Not all users can track any available resources all the time, this is what /usr/ports/UPDATING is for (IMO). Or v.v., if there was an entry in UPDATING I didn't have to ask here. :) ___ 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: apache 2.2.22_6 to _8 fails
Helmut Schneider wrote: > Hi Olli, > > olli hauer wrote: > > > On 2012-09-08 14:28, Helmut Schneider wrote: > > > ** Detected a package name change: apache (www/apache22) -> > > > 'apache22' (www/apache22) > > > ---> Upgrading 'apache-2.2.22_6' to 'apache22-2.2.22_8' > > > (www/apache22) ---> Building '/usr/ports/www/apache22' with make > > > flags: -DWITH_PROXY -DWITH_PROXY_CONNECT -DWITH_PROXY_FTP > > > -DWITH_PROXY_HTTP -DWITH_LDAP -DWITH_AUTHNZ_LDAP -DWITH_BDB > > > -DWITH_APR_FROM_PORTS ===> Cleaning for apache22-2.2.22_8 > > > > You must check at least one option in the PROXY multi > > > *** Error code 1 > > > > > > The options worked fine up to 2.2.22_6 and I'm not sure how to > > > read the error message. > > > > with options NG the WITH... parameters do no longer work. > > If you want to specify them in make.conf you have to do it this way > > I'm using pkgtools.conf, removing -DWITH_PROXY seems to do the trick > (I also removed the typo of DBD and the obsolete > DWITH_APR_FROM_PORTS, but they are not related). > > > apache22_SET=PROXY PROXY_CONNECT PROXY_FTP ... > > > > The downside with options NG is if you already have an OPTIONSFILE > > the make.conf parameters will have a lower priority. > > Please note this in UPDATING. Thanks! ___ 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"
Status of ports/169660
Hi, ports/169660 is waiting for the maintainer for more than 2 months, any update here? Thanks, Helmut ___ 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"
