Re: [removed ports] sysutils/cpuburn
On 11/15/2011 09:44, Andriy Gapon wrote:
It should be
MASTER_SITES= ${MASTER_SITE_LOCAL}
MASTER_SITE_SUBDIR= avg
Um, no. That's not an advantage over the previous situation, where the
distfile mirror became the only working master site by default.
Please provide a proper master site, or ask for help from someone who can.
--
We could put the whole Internet into a book.
Too practical.
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
___
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: Recent ports removal
On 11/15/2011 11:01, Matthew Seaman wrote: On 11/11/2011 22:23, Doug Barton wrote: By its nature, deprecated ports tends not to be updated for long time, port tools like portmaster, portupgrade will not even see it because no PORTREVISION bump happen. portmaster -L will warn you about ports marked DEPRECATED/FORBIDDEN/IGNORE/BROKEN if you run it against an updated ports tree. One area where we actually can improve here is to also put this information in the INDEX. I have an idea for that, just haven't been able to put the time into making it happen. How about something like the attached? Rather than adding to the INDEX, this appends DEPRECATED, FORBIDDEN, IGNORE, BROKEN and EXPIRATION_DATE values to pkg-message, creating one if the port doesn't already have it. Won't work for my use case, which is 'portmaster -L --index-only' -- We could put the whole Internet into a book. Too practical. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: [removed ports] sysutils/cpuburn
On 16 Nov 2011 08:19, Doug Barton do...@freebsd.org wrote:
On 11/15/2011 09:44, Andriy Gapon wrote:
It should be
MASTER_SITES= ${MASTER_SITE_LOCAL}
MASTER_SITE_SUBDIR= avg
Um, no. That's not an advantage over the previous situation, where the
distfile mirror became the only working master site by default.
Please provide a proper master site, or ask for help from someone who can.
I'll provide mine.
We now have a proper maintainer for the port, which was the majority of the
problem.
Chris
___
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: [removed ports] sysutils/cpuburn
On 11/16/2011 00:27, Chris Rees wrote:
On 16 Nov 2011 08:19, Doug Barton do...@freebsd.org
mailto:do...@freebsd.org wrote:
On 11/15/2011 09:44, Andriy Gapon wrote:
It should be
MASTER_SITES= ${MASTER_SITE_LOCAL}
MASTER_SITE_SUBDIR= avg
Um, no. That's not an advantage over the previous situation, where the
distfile mirror became the only working master site by default.
Please provide a proper master site, or ask for help from someone who can.
I'll provide mine.
We now have a proper maintainer for the port, which was the majority of
the problem.
Sounds great, thanks for volunteering. :)
--
We could put the whole Internet into a book.
Too practical.
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
can't fetch math/mpfr
=== Vulnerability check disabled, database not found === License LGPL3 accepted by the user = patch02 doesn't seem to exist in /usr/ports/distfiles//mpfr-3.1.0. = Attempting to fetch http://www.mpfr.org/mpfr-current/patch02 fetch: transfer timed out = Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mpfr-3.1.0/patch02 fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mpfr-3.1.0/patch02: File unavailable (e.g., file not found, no access) = Couldn't fetch it - please try to retrieve this = port manually into /usr/ports/distfiles//mpfr-3.1.0 and try again. *** Error code 1 Stop in /usr/ports/math/mpfr. Is the double slash in the path an error? -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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
SOLVED: Re: can't fetch math/mpfr
On Wed, Nov 16, 2011 at 08:43:24AM +, Anton Shterenlikht wrote: === Vulnerability check disabled, database not found === License LGPL3 accepted by the user = patch02 doesn't seem to exist in /usr/ports/distfiles//mpfr-3.1.0. = Attempting to fetch http://www.mpfr.org/mpfr-current/patch02 fetch: transfer timed out = Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mpfr-3.1.0/patch02 fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mpfr-3.1.0/patch02: File unavailable (e.g., file not found, no access) = Couldn't fetch it - please try to retrieve this = port manually into /usr/ports/distfiles//mpfr-3.1.0 and try again. *** Error code 1 Stop in /usr/ports/math/mpfr. All is fine now. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: Recent ports removal
On 16/11/2011 08:20, Doug Barton wrote: On 11/15/2011 11:01, Matthew Seaman wrote: On 11/11/2011 22:23, Doug Barton wrote: By its nature, deprecated ports tends not to be updated for long time, port tools like portmaster, portupgrade will not even see it because no PORTREVISION bump happen. portmaster -L will warn you about ports marked DEPRECATED/FORBIDDEN/IGNORE/BROKEN if you run it against an updated ports tree. One area where we actually can improve here is to also put this information in the INDEX. I have an idea for that, just haven't been able to put the time into making it happen. How about something like the attached? Rather than adding to the INDEX, this appends DEPRECATED, FORBIDDEN, IGNORE, BROKEN and EXPIRATION_DATE values to pkg-message, creating one if the port doesn't already have it. Won't work for my use case, which is 'portmaster -L --index-only' Orthogonal to your use case: adding this sort of stuff to the INDEX is a good idea too. Not everyone uses portmaster though. Also changing the format of the INDEX has ramifications with various 3rd party software that uses it, so it's going to be some effort to get it all sorted and debugged. (BTW. Very happy to code up any proposed experimental INDEX formats in my FreeBSD::Portindex modules or receive patches.) The change I propose here is fairly minimal, and it should ensure that any user of ports or packages sees notification through mechanisms that already exist. Since they will see this at the point they install a deprecated port -- coupling that with bumping PORTREVISION at the point the port is deprecated should bring such changes to the attention of users in time for them to raise any objections / provide fixes etc. In fact, as I think about it this morning, another idea is this sort of mechanism could be used to notify users of unmaintained ports and ask for volunteers to maintain them. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: [removed ports] sysutils/cpuburn
on 16/11/2011 10:19 Doug Barton said the following:
On 11/15/2011 09:44, Andriy Gapon wrote:
It should be
MASTER_SITES=${MASTER_SITE_LOCAL}
MASTER_SITE_SUBDIR= avg
Um, no. That's not an advantage over the previous situation, where the
distfile mirror became the only working master site by default.
Umm, I am not sure I understand the reasoning here, so would appreciate an
explanation. I agree that this is not a great improvement over the previous
status quo (except that it is now clear that the distfile is hosted by us on
purpose, not by accident). But do you suggest that having all freebsd mirrors
plus one site under avg's control (with unknown reliability characteristics) is
much better than just all freebsd mirrors ? Because it doesn't appear to be
that way to me.
Thank you.
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postfix-current broken on amd64 platform
On 2011/11/16 02:56, Sahil Tandon wrote: On Tue, 2011-11-15 at 17:55:57 +0100, Pav Lucistnik wrote: Jase Thew píše v út 15. 11. 2011 v 16:31 +: What networking/DNS configuration is Pointyhat lacking (or have sufficiently different to break the socket code inside of postconf)? It is a purposefully no-networking sandbox jail. What networking activity postconf wants to run? Wietse, in a post[1] on the Postfix mailing list, lends further credence to a suspicion that this issue is particular to pointyhat: Postconf opens a socket to determine the mynetworks value (it determines the local interfaces and their netmasks). I have heard about bizarre errors on FreeBSD (jail) systems where the user-land library was out of sync with kernel-land, resulting in data structure mis-matches and system calls returning nonsensical results. [1] http://archives.neohapsis.com/archives/postfix/2011-11/0385.html That's entirely possible. Is it a clever idea to hardcode local interfaces on build machine into a package that will then be redistributed to other machines? Sounds like postfix will have to do without official packages on FreeBSD from now on. -- Pav Lucistnik p...@oook.cz p...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
10-CURRENT ports/net/wireshark does not compile
Hello, /usr/ports is uptodate as of CVS of yesterday, kernel/world are r226986; the above mentioned port does not compile, it gives: # make install ... libtool: compile: cc -DHAVE_CONFIG_H -I. -I. -I../.. -I./../.. -I./.. -I/usr/local/include -I/usr/local/include/p11-kit-1 -I/usr/local/ nclude -I/usr/local/include -I/usr/local/include -I/usr/include/pcap -I/usr/local/lib/include -I/usr/include -DPLUGIN_DIR=\/usr/local/l b/wireshark/plugins/1.6.2\ -DINET6 -D_U_=__attribute__((unused)) -O2 -pipe -funit-at-a-time -fno-strict-aliasing -Wall -W -Wextra -Wd claration-after-statement -Wendif-labels -Wpointer-arith -Wno-pointer-sign -Wcast-align -Wformat-security -I/usr/local/include -I/usr/lo al/include -D_THREAD_SAFE -D_REENTRANT -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr local/include/cairo -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/local/i clude -I/usr/local/include/glib-2.0 -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -I/usr/include/pcap -I/usr/local/lib/in lude -I/usr/include -MT libdissectors_la-packet-kerberos.lo -MD -MP -MF .deps/libdissectors_la-packet-kerberos.Tpo -c packet-kerberos.c -fPIC -DPIC -o .libs/libdissectors_la-packet-kerberos.o packet-kerberos.c: In function 'read_keytab_file': packet-kerberos.c:653: error: 'krb5_principal_data' has no member named 'name' packet-kerberos.c:654: error: 'krb5_principal_data' has no member named 'name' packet-kerberos.c:654: error: 'krb5_principal_data' has no member named 'name' packet-kerberos.c:657: warning: format '%s' expects type 'char *', but argument 4 has type 'krb5_data' packet-kerberos.c:657: warning: format '%s' expects type 'char *', but argument 4 has type 'krb5_data' packet-kerberos.c:660: error: 'krb5_keytab_entry' has no member named 'keyblock' packet-kerberos.c:661: error: 'krb5_keytab_entry' has no member named 'keyblock' packet-kerberos.c:662: error: 'krb5_keytab_entry' has no member named 'keyblock' packet-kerberos.c:662: error: 'krb5_keytab_entry' has no member named 'keyblock' packet-kerberos.c: In function 'decrypt_krb5_data': packet-kerberos.c:702: error: 'krb5_crypto' undeclared (first use in this function) packet-kerberos.c:702: error: (Each undeclared identifier is reported only once packet-kerberos.c:702: error: for each function it appears in.) packet-kerberos.c:702: error: expected ';' before 'crypto' packet-kerberos.c:703: warning: ISO C90 forbids mixed declarations and code packet-kerberos.c:710: error: 'krb5_keytab_entry' has no member named 'keyblock' packet-kerberos.c:711: error: 'krb5_keytab_entry' has no member named 'keyblock' packet-kerberos.c:712: error: 'krb5_keytab_entry' has no member named 'keyblock' packet-kerberos.c:713: warning: implicit declaration of function 'krb5_crypto_init' packet-kerberos.c:713: error: 'krb5_keytab_entry' has no member named 'keyblock' packet-kerberos.c:713: error: 'crypto' undeclared (first use in this function) packet-kerberos.c:725: warning: implicit declaration of function 'krb5_decrypt_ivec' packet-kerberos.c:735: warning: implicit declaration of function 'krb5_crypto_destroy' gmake[5]: *** [libdissectors_la-packet-kerberos.lo] Error 1 gmake[5]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-1.6.2/epan/dissectors' gmake[4]: *** [all-recursive] Error 1 gmake[4]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-1.6.2/epan/dissectors' gmake[3]: *** [all] Error 2 gmake[3]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-1.6.2/epan/dissectors' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-1.6.2/epan' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-1.6.2' -- Matthias Apitz e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postfix-current broken on amd64 platform
On Wed, Nov 16, 2011 at 10:28:03AM +0100, Pav Lucistnik wrote: Is it a clever idea to hardcode local interfaces on build machine into a package that will then be redistributed to other machines? Am I misunderstanding something, or is this a local configuration script that customizes the installation for the target machine in a similar way the mai/qmail port runs post-install 'config/config-fast' scripts to identify the system hostname (which then populates the 'me' file, for example)? -- Glen Barber pgpLdYXoIPYiY.pgp Description: PGP signature
Re: postfix-current broken on amd64 platform
On Wed, 16 Nov 2011 10:28:03 +0100 Pav Lucistnik articulated: On 2011/11/16 02:56, Sahil Tandon wrote: On Tue, 2011-11-15 at 17:55:57 +0100, Pav Lucistnik wrote: Jase Thew píše v út 15. 11. 2011 v 16:31 +: What networking/DNS configuration is Pointyhat lacking (or have sufficiently different to break the socket code inside of postconf)? It is a purposefully no-networking sandbox jail. What networking activity postconf wants to run? Wietse, in a post[1] on the Postfix mailing list, lends further credence to a suspicion that this issue is particular to pointyhat: Postconf opens a socket to determine the mynetworks value (it determines the local interfaces and their netmasks). I have heard about bizarre errors on FreeBSD (jail) systems where the user-land library was out of sync with kernel-land, resulting in data structure mis-matches and system calls returning nonsensical results. [1] http://archives.neohapsis.com/archives/postfix/2011-11/0385.html That's entirely possible. Is it a clever idea to hardcode local interfaces on build machine into a package that will then be redistributed to other machines? Sounds like postfix will have to do without official packages on FreeBSD from now on. I would find that unacceptable. If the problem is with FreeBSD as Wietse has indicated, then the problem should be rectified on the FreeBSD side of the equation. In any case, since Postfix does apparently build on FreeBSD with the exception of pointyhat, perhaps the BROKEN tag should be removed from the port and just a warning message displayed that pointyhat cannot build/install the port successfully but that the end users mileage may vary. At the very least, it would be a more honest approach to the problem. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postfix-current broken on amd64 platform
Hi! Postconf opens a socket to determine the mynetworks value (it determines the local interfaces and their netmasks). [quote http://archives.neohapsis.com/archives/postfix/2011-11/0385.html] I have heard about bizarre errors on FreeBSD (jail) systems where the user-land library was out of sync with kernel-land, resulting in data structure mis-matches and system calls returning nonsensical results. Is it a clever idea to hardcode local interfaces on build machine into a package that will then be redistributed to other machines? No. Sounds like postfix will have to do without official packages on FreeBSD from now on. I would find that unacceptable. If the problem is with FreeBSD as Wietse has indicated, then the problem should be rectified on the FreeBSD side of the equation. Well, the problem is on both sides. On FreeBSD, one can have systems without any interface -- and postfix assumes that every system it is built on has some kind of interface. So, maybe it's time to change that assumption for the postfix built process, if possible ? -- p...@opsec.eu+49 171 3101372 9 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postfix-current broken on amd64 platform
Kurt Jaeger: Hi! Postconf opens a socket to determine the mynetworks value (it determines the local interfaces and their netmasks). [quote http://archives.neohapsis.com/archives/postfix/2011-11/0385.html] I have heard about bizarre errors on FreeBSD (jail) systems where the user-land library was out of sync with kernel-land, resulting in data structure mis-matches and system calls returning nonsensical results. Is it a clever idea to hardcode local interfaces on build machine into a package that will then be redistributed to other machines? No. Postfix does none of that. Can someone please explain what socket call is failing, and what the reasons for that might be? I tend to believe that network-less build environments are not representative for the environment where an Internet MTA would run, but hey, what do I know. Wietse ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postfix-current broken on amd64 platform
On 2011-11-16 10:28, Pav Lucistnik wrote:
On 2011/11/16 02:56, Sahil Tandon wrote:
On Tue, 2011-11-15 at 17:55:57 +0100, Pav Lucistnik wrote:
Jase Thew píše v út 15. 11. 2011 v 16:31 +:
What networking/DNS configuration is Pointyhat lacking (or have
sufficiently different to break the socket code inside of postconf)?
It is a purposefully no-networking sandbox jail. What networking
activity postconf wants to run?
Wietse, in a post[1] on the Postfix mailing list, lends further credence
to a suspicion that this issue is particular to pointyhat:
Postconf opens a socket to determine the mynetworks value (it
determines the local interfaces and their netmasks).
I have heard about bizarre errors on FreeBSD (jail) systems where the
user-land library was out of sync with kernel-land, resulting in data
structure mis-matches and system calls returning nonsensical results.
[1] http://archives.neohapsis.com/archives/postfix/2011-11/0385.html
That's entirely possible.
Is it a clever idea to hardcode local interfaces on build machine into a
package that will then be redistributed to other machines?
Sounds like postfix will have to do without official packages on FreeBSD from
now on.
What about the attached diff until we found the exact issue.
Unbreak the port, and use MANUAL_PACKAGE_BUILD instead.
Additional bump to latest postfix-current.
Since postfix-current should be current and not months behind I see no issue if
we
do not provide packages which are not updated regularly enough to reflect
current.
--
Regards,
olli
Index: Makefile
===
RCS file: /home/pcvs/ports/mail/postfix-current/Makefile,v
retrieving revision 1.263
diff -u -r1.263 Makefile
--- Makefile26 Oct 2011 22:44:50 - 1.263
+++ Makefile16 Nov 2011 13:11:03 -
@@ -6,7 +6,7 @@
#
PORTNAME= postfix
-DISTVERSION= 2.9-20111012
+DISTVERSION= 2.9-2013
PORTEPOCH= 4
CATEGORIES=mail ipv6
MASTER_SITES= ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/ \
@@ -25,6 +25,7 @@
postfix-current-2.[0-8]* postfix-current-base-2.[0-8]* \
sendmail-8.* sendmail+*-8.* smail-3.* zmailer-2.*
+MANUAL_PACKAGE_BUILD= build OK in tinderbox, broken on pointyhat (issue not
identified)
.if !defined(BATCH) !defined(PACKAGE_BUILDING)
IS_INTERACTIVE=yes
.endif
@@ -92,10 +93,6 @@
HTML1= body_checks.5.html bounce.5.html postfix-power.png \
scache.8.html tlsmgr.8.html
-.if ${ARCH} == amd64
-BROKEN=fails during installation
-.endif
-
.if !defined(DEBUG)
MAKEFILEFLAGS+=DEBUG=
.endif
Index: distinfo
===
RCS file: /home/pcvs/ports/mail/postfix-current/distinfo,v
retrieving revision 1.196
diff -u -r1.196 distinfo
--- distinfo18 Oct 2011 01:50:41 - 1.196
+++ distinfo16 Nov 2011 13:11:03 -
@@ -1,2 +1,2 @@
-SHA256 (postfix/postfix-2.9-20111012.tar.gz) =
fb3d55c8a16c687bcee7e7a26a84c69e8765cc19ba7ab47620e7ac6b19efd3be
-SIZE (postfix/postfix-2.9-20111012.tar.gz) = 3673596
+SHA256 (postfix/postfix-2.9-2013.tar.gz) =
c8f493b9206b4ac52fdfdae72fee214d22d29206d353a6110188305019d906e3
+SIZE (postfix/postfix-2.9-2013.tar.gz) = 3685450
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postfix-current broken on amd64 platform
Hi! Postconf opens a socket to determine the mynetworks value (it determines the local interfaces and their netmasks). [...] Postfix does none of that. The fbsd postfix-current port during the post-install script does something which fails on a jail-based build-cluster where the jail itself has no network connectivity. See this message for some analysis: http://lists.freebsd.org/pipermail/freebsd-ports/2011-November/071419.html And this message explains it: http://lists.freebsd.org/pipermail/freebsd-ports/2011-November/071421.html It says: -- It is a purposefully no-networking sandbox jail. What networking activity postconf wants to run? -- Can someone please explain what socket call is failing, and what the reasons for that might be? The reason is that postconf is called during post-install and fails because the build jail is without any interface. I tend to believe that network-less build environments are not representative for the environment where an Internet MTA would run, but hey, what do I know. The build environment seems to be network-less. It's not the environment where the package will run. -- p...@opsec.eu+49 171 3101372 9 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postfix-current broken on amd64 platform
On 2011/11/16 14:18, olli hauer wrote: On 2011-11-16 10:28, Pav Lucistnik wrote: On 2011/11/16 02:56, Sahil Tandon wrote: On Tue, 2011-11-15 at 17:55:57 +0100, Pav Lucistnik wrote: Jase Thew píše v út 15. 11. 2011 v 16:31 +: What networking/DNS configuration is Pointyhat lacking (or have sufficiently different to break the socket code inside of postconf)? It is a purposefully no-networking sandbox jail. What networking activity postconf wants to run? Wietse, in a post[1] on the Postfix mailing list, lends further credence to a suspicion that this issue is particular to pointyhat: Postconf opens a socket to determine the mynetworks value (it determines the local interfaces and their netmasks). I have heard about bizarre errors on FreeBSD (jail) systems where the user-land library was out of sync with kernel-land, resulting in data structure mis-matches and system calls returning nonsensical results. [1] http://archives.neohapsis.com/archives/postfix/2011-11/0385.html That's entirely possible. Is it a clever idea to hardcode local interfaces on build machine into a package that will then be redistributed to other machines? Sounds like postfix will have to do without official packages on FreeBSD from now on. What about the attached diff until we found the exact issue. Unbreak the port, and use MANUAL_PACKAGE_BUILD instead. MANUAL_PACKAGE_BUILD is fine with me. -- Pav Lucistnik p...@oook.cz p...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postfix-current broken on amd64 platform
Kurt Jaeger: Hi! Postconf opens a socket to determine the mynetworks value (it determines the local interfaces and their netmasks). [...] Postfix does none of that. The fbsd postfix-current port during the post-install script does something which fails on a jail-based build-cluster where the jail itself has no network connectivity. Would it be possible to give the jail a loopback interface? I don't mind if FreeBSD improves its build environment such that it breaks the build after 12 years. If adding a loopback interface fixes this, then we can all move on to more interesting things. Wietse ___ 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
science/avogadro compile failure
avogadro fails with the error reports shown below. Thanks in advance for any guidance David Scanning dependencies of target avogadro-app [ 90%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/editcommands.cpp.o [ 90%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/projecttreeitem.cpp.o [ 90%] Building C object avogadro/src/CMakeFiles/avogadro- app.dir/__/gl2ps/gl2ps.c.o [ 91%] Building CXX object libavogadro/src/python/CMakeFiles/python- module.dir/moleculefile.cpp.o [ 91%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/projectdelegates/atomdelegate.cpp.o [ 91%] Building CXX object libavogadro/src/python/CMakeFiles/python- module.dir/toolgroup.cpp.o [ 91%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/projectdelegates/bonddelegate.cpp.o [ 92%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/projectdelegates/labeldelegate.cpp.o [ 92%] Building CXX object libavogadro/src/python/CMakeFiles/python- module.dir/pluginmanager.cpp.o [ 92%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/projectdelegates/moleculedelegate.cpp.o [ 92%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/projectdelegates/residuedelegate.cpp.o [ 92%] Building CXX object libavogadro/src/python/CMakeFiles/python- module.dir/cube.cpp.o [ 92%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/projectdelegates/selectiondelegate.cpp.o [ 92%] Building CXX object libavogadro/src/python/CMakeFiles/python- module.dir/atom.cpp.o [ 92%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/projecttreemodel.cpp.o [ 93%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/projecttreemodeldelegate.cpp.o [ 93%] Building CXX object libavogadro/src/python/CMakeFiles/python- module.dir/elementtranslator.cpp.o [ 93%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/pluginitemmodel.cpp.o [ 93%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/flattabwidget.cpp.o [ 93%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/engineitemdelegate.cpp.o [ 94%] Building CXX object libavogadro/src/python/CMakeFiles/python- module.dir/eigen.cpp.o [ 94%] Building CXX object libavogadro/src/python/CMakeFiles/python- module.dir/tool.cpp.o [ 94%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/engineitemmodel.cpp.o [ 94%] Building CXX object libavogadro/src/python/CMakeFiles/python- module.dir/periodictableview.cpp.o [ 94%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/engineviewwidget.cpp.o [ 94%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/primitiveitemmodel.cpp.o [ 94%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/aboutdialog.cpp.o [ 94%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/pluginlistview.cpp.o [ 94%] Building CXX object libavogadro/src/python/CMakeFiles/python- module.dir/primitivelist.cpp.o [ 94%] Building CXX object libavogadro/src/python/CMakeFiles/python- module.dir/camera.cpp.o [ 94%] Building CXX object libavogadro/src/python/CMakeFiles/python- module.dir/sip.cpp.o [ 95%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/detachedview.cpp.o [ 95%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/glgraphicsview.cpp.o /usr/ports/science/avogadro/work/avogadro-1.0.1/libavogadro/src/python/sip.cpp: In static member function 'static void* QClass_convertersT::QClass_from_PyQt(PyObject*)': /usr/ports/science/avogadro/work/avogadro-1.0.1/libavogadro/src/python/sip.cpp:207: error: 'struct sipSimpleWrapper' has no member named 'u' [ 95%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/enginelistview.cpp.o *** Error code 1 [ 95%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/primitivetreeview.cpp.o [ 95%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/enginecolorswidget.cpp.o [ 95%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/projecttreeeditor.cpp.o 1 error *** Error code 2 [ 95%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/application.cpp.o [ 95%] Building CXX object avogadro/src/CMakeFiles/avogadro-app.dir/main.cpp.o [ 95%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/savedialog.cpp.o [ 96%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/addenginedialog.cpp.o [ 96%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/pluginsettings.cpp.o [ 96%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/settingsdialog.cpp.o [ 97%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/engineprimitiveswidget.cpp.o [ 97%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/importdialog.cpp.o [ 98%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/mainwindow.cpp.o [ 98%] Building CXX object avogadro/src/CMakeFiles/avogadro- app.dir/qrc_avogadro.cxx.o Linking CXX executable ../../bin/avogadro [ 98%] Built target avogadro-app 1 error ***
Re: postfix-current broken on amd64 platform
On 16 Nov 2011 16:00, Wietse Venema wie...@porcupine.org wrote: Kurt Jaeger: Hi! Postconf opens a socket to determine the mynetworks value (it determines the local interfaces and their netmasks). [...] Postfix does none of that. The fbsd postfix-current port during the post-install script does something which fails on a jail-based build-cluster where the jail itself has no network connectivity. Would it be possible to give the jail a loopback interface? I don't mind if FreeBSD improves its build environment such that it breaks the build after 12 years. If adding a loopback interface fixes this, then we can all move on to more interesting things. Wietse Clamav uses loopback on its testing phase, and works fine on the build cluster. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postfix-current broken on amd64 platform
On Nov 16, 2011, at 11:24 AM, Chris Rees utis...@gmail.com wrote: On 16 Nov 2011 16:00, Wietse Venema wie...@porcupine.org wrote: Kurt Jaeger: Hi! Postconf opens a socket to determine the mynetworks value (it determines the local interfaces and their netmasks). [...] Postfix does none of that. The fbsd postfix-current port during the post-install script does something which fails on a jail-based build-cluster where the jail itself has no network connectivity. Would it be possible to give the jail a loopback interface? I don't mind if FreeBSD improves its build environment such that it breaks the build after 12 years. If adding a loopback interface fixes this, then we can all move on to more interesting things. Wietse Clamav uses loopback on its testing phase, and works fine on the build cluster. What irks me is that all other Postfix versions (that also call postconf) have no problem building/installing on the cluster.___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postfix-current broken on amd64 platform
Wietse: Would it be possible to give the jail a loopback interface? I don't mind if FreeBSD improves its build environment such that it breaks the build after 12 years. If adding a loopback interface fixes this, then we can all move on to more interesting things. On Nov 16, 2011, at 11:24 AM, Chris Rees utis...@gmail.com wrote: Clamav uses loopback on its testing phase, and works fine on the build cluster. Sahil Tandon: What irks me is that all other Postfix versions (that also call postconf) have no problem building/installing on the cluster. It would be immensely helpful if run-time details could be made available including line of source code, and any system configuration details that are necessary to reproduce the condition. If this turns out to be highly-classified information, then we can communicate off-list. My PGP key is linked off http://www.porcupine.org/wietse/. Wietse ___ 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
ardour3 beta1 (use a midi keyboard with FreeBSD...)
Hi!
I still haven't got around to porting lv2 ui and more plugins (help
highly welcome there :) - but after the ardour guys posted a beta1
release of ardour3,
http://ardour.org/node/4658
I prepared another port update:
http://people.freebsd.org/~nox/tmp/ardour-3.0beta1-preliminary-r10637.patch
As posted earlier, this depends on an lv2core port change,
http://people.freebsd.org/~nox/tmp/lv2core-lv2config.patch
as well as lilv, serd, and sord:
http://people.freebsd.org/~nox/tmp/serd-0.5.0.shar
http://people.freebsd.org/~nox/tmp/sord-0.5.0.shar
http://people.freebsd.org/~nox/tmp/lilv-0.5.0r3601.shar
Here are some (hopefully) useful links again:
http://ardour.org/a3_features
http://ardour.org/a3_features_midi
http://ardour.org/a3_features_midi_editing
http://ardour.org/plugins
http://www.archive.org/details/Introduction_to_Ardour_3.0_MIDI
My original ardour3 alpha10 thread:
http://lists.freebsd.org/pipermail/freebsd-multimedia/2011-September/012432.html
I tested this with qjackctl, jack_umidi, and fluidsynth, as well
as with linuxsampler, here is a blog post about linuxsampler,
including about using it as an lv2 plugin with ardour3: (the LV2CORE
knob with the audio/linuxsampler port)
http://wootangent.net/2011/07/everything-you-always-wanted-to-know-about-linuxsampler/
The mentioned linuxsampler frontend gui that you can run with java -jar:
http://linuxsampler.org/downloads.html
http://downloads.sourceforge.net/jsampler/Fantasia-0.9.jar
And a piano bank .gig (Maestro Concert Grand) that you can use
with linuxsampler:
http://sonimusicae.free.fr/matshelgesson-maestro-en.html
TODO:
- Test (and possibly fix) the VST stuff (it uses wine and thus probably
only works on i386 and I'm on amd64 so I didn't attempt to build it.)
- Maybe fix the port so it respects C{,XX}FLAGS? (it now uses waf which
seems to ignore them.)
- Installation is not really supported yet by the ardour guys for
the betas so there may be files not getting installed, if you
notice something missing you can run the build from below the
work/ dir by invoking: (also without installing the port, i.e.
after just doing `make' in the port dir not `make install')
work/ardour-3.0alpha10_1/gtk2_ardour/ardev
- Test! (are the Ardour devs interested in FreeBSD bugreports?
I don't know. :) What I do know is they don't want the alphas/betas
discussed in their webforums, quote:
---snip---
This is a beta version of Ardour 3.0.
You are respectfully requested NOT to ask for assistance with build issues
and not to report issues with Ardour 3.0 on the forums at ardour.org.
Please use IRC, the bug tracker and/or the ardour mailing lists (-dev or -user)
Thanks for your co-operation with our development process.
---snip---
Enjoy, :)
Juergen
PS: The export function in the gui doesn't work for midi tracks, but
you can fork a track and after that grab a midi file out of:
session dir/interchange/name/midifiles
___
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
[sysutils/pwsafe] Useless X11 dependency
Hi, Pleaese Cc: me when replying, I'm not subscribed. I'm using sysutils/pwsafe on a headless server. My recent upgrade of the port pulled in numerous useless X11 libs. - The port doesn't seem to agree to issue the password on the terminal anymore; - The port compiles cleanly when the Makefile is reverted to rev 1.4. Can you please revert your change, or at least provide a WITHOUT_X11 knob as many other ports? Thanks. Regards, -- Jeremie Le Hen Men are born free and equal. Later on, they're on their own. Jean Yanne ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: cvs checkout ./. csup
On Tue, 15 Nov 2011 10:48:26 +0100
Matthias Apitz g...@unixarea.de wrote:
Since many years I'm fetching or updating /usr/ports with
# cd /usr
# setenv CVSROOT :pserver:anon...@anoncvs.fr.freebsd.org:/home/ncvs
# cvs checkout ports
and later do the updating just with:
# cd /usr/ports
# cvs update
# portupgrade -ai
The FreeBSD handbook describes (or recommends?) using 'csup' for
updating ports tree... What is the advantage (or reason, if any)?
Basically, for doing updates across the network, csup is the preferred
method (for reasons of efficiency and less strain on the server). If
you do need the versioning information provided by CVS (for example, to
create a diff to submit for a ports patch, or simply for convenient
access to the CVS history of a particular file), then you may want to
try the following method:
Use csup to maintain a local copy (default directory /home/ncvs) of the
parts of the CVS repo you need (src, ports, doc, etc.), using a modified
copy of /usr/share/examples/cvsup/cvs-supfile. You'll probably want to
setup a cron job to do this automatically at regular intervals.
Then use cvs to update your /usr/{src,ports,doc} trees from your local
copy of the CVS repo. Note that having a local CVS repo also eliminates the
need to use the pserver access method, if you're updating on the same
machine where the repo resides.
If you decide to do this, you'll need to remove your current working
{src,ports,doc} tree(s) and then do a 'cvs checkout' the first time
to setup the CVS-versioned tree(s). For example:
export CVSROOT=/home/ncvs
cd /usr
rm -rf ports
cvs checkout ports
After having done the initial checkout, you can then use cvs
update (or simply make update) to maintain the tree.
This gives you the best of both worlds: fast, efficient updates across
the network, while still providing access to all the versioning
features of CVS.
Hope this helps. :-)
--
Conrad J. Sabatier
conr...@cox.net
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postfix-current broken on amd64 platform
On Wed, 2011-11-16 at 13:16:34 -0500, Wietse Venema wrote: Wietse: Would it be possible to give the jail a loopback interface? I don't mind if FreeBSD improves its build environment such that it breaks the build after 12 years. If adding a loopback interface fixes this, then we can all move on to more interesting things. On Nov 16, 2011, at 11:24 AM, Chris Rees utis...@gmail.com wrote: Clamav uses loopback on its testing phase, and works fine on the build cluster. Sahil Tandon: What irks me is that all other Postfix versions (that also call postconf) have no problem building/installing on the cluster. It would be immensely helpful if run-time details could be made available including line of source code, and any system configuration details that are necessary to reproduce the condition. +1 I hope someone with access to the cluster machine can provide this information. As much as I've tried to mimic the cluster conditions myself, I am unable to reproduce the fatal socket error on any FreeBSD version. -- Sahil Tandon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: postfix-current broken on amd64 platform
On 16/11/2011 23:30, Sahil Tandon wrote: On Wed, 2011-11-16 at 13:16:34 -0500, Wietse Venema wrote: [SNIP] It would be immensely helpful if run-time details could be made available including line of source code, and any system configuration details that are necessary to reproduce the condition. +1 I hope someone with access to the cluster machine can provide this information. As much as I've tried to mimic the cluster conditions myself, I am unable to reproduce the fatal socket error on any FreeBSD version. I've just managed to reproduce the fatal socket error locally. It can occur when IPv6 is enabled, but you don't have any IPv6 addresses configured on any interfaces. (Yes, having an IPv6 enabled interface with no addresses assigned is non-RFC3513 compliant, but it can and does occur). The cause (at least locally) is the socket call on line 214 in util/inet_proto.c which fails with errno 43 (EPROTONOSUPPORT - Protocol not supported). Regards, Jase. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [sysutils/pwsafe] Useless X11 dependency
On Wed, Nov 16, 2011 at 10:47:19PM +0100, Jeremie Le Hen wrote:
Hi,
Pleaese Cc: me when replying, I'm not subscribed.
I'm using sysutils/pwsafe on a headless server. My recent upgrade of
the port pulled in numerous useless X11 libs.
- The port doesn't seem to agree to issue the password on the terminal
anymore;
- The port compiles cleanly when the Makefile is reverted to rev 1.4.
Can you please revert your change, or at least provide a WITHOUT_X11
knob as many other ports?
Thanks.
Regards,
--
Jeremie Le Hen
Men are born free and equal. Later on, they're on their own.
Jean Yanne
Hi,
Please test the attached patch. It defaults to not bring in X11 deps.
If it works, I'll submit a PR for it.
Thanks.
Regards,
sunpoet
Index: Makefile
===
RCS file: /home/pcvs/ports/sysutils/pwsafe/Makefile,v
retrieving revision 1.5
diff -u -r1.5 Makefile
--- Makefile21 Oct 2011 02:28:23 - 1.5
+++ Makefile17 Nov 2011 01:58:46 -
@@ -7,7 +7,7 @@
PORTNAME= pwsafe
PORTVERSION= 0.2.0
-PORTREVISION= 1
+PORTREVISION= 2
CATEGORIES=sysutils
MASTER_SITES= http://nsd.dyndns.org/pwsafe/releases/
@@ -18,19 +18,25 @@
GNU_CONFIGURE= yes
USE_GMAKE= yes
-USE_XORG= ice sm x11 xmu
MAN1= pwsafe.1
PLIST_FILES= bin/pwsafe
-.include bsd.port.pre.mk
+.if defined(WITH_X11)
+CONFIGURE_ARGS=--with-x
+USE_XORG= ice sm x11 xmu
+.else
+CONFIGURE_ARGS=ac_cv_have_x=have_x=no \
+ ac_cv_lib_ICE_IceConnectionNumber=no \
+ ac_cv_lib_X11_XOpenDisplay=no \
+ ac_cv_lib_Xmu_XmuInternAtom=no
+.endif
do-install:
- ${INSTALL_PROGRAM} ${WRKSRC}/pwsafe ${PREFIX}/bin
- ${INSTALL_MAN} ${WRKSRC}/pwsafe.1 ${PREFIX}/man/man1
+ ${INSTALL_PROGRAM} ${WRKSRC}/pwsafe ${PREFIX}/bin/
+ ${INSTALL_MAN} ${WRKSRC}/pwsafe.1 ${MAN1PREFIX}/man/man1/
.if defined(WITH_SETUID)
${CHMOD} u+s ${PREFIX}/bin/pwsafe
.endif
-.include bsd.port.post.mk
-
+.include bsd.port.mk
pgpAWHAlOBaOQ.pgp
Description: PGP signature
Re: postfix-current broken on amd64 platform
On 11/16/2011 05:03, Wietse Venema wrote: I tend to believe that network-less build environments are not representative for the environment where an Internet MTA would run, but hey, what do I know. I think you're right that having a network makes the MTA more useful. :) However given the prevalence and popularity of pre-packaged software in the Unix world it's probably worth thinking about what parts of the build/configuration process need to be done at build time, and what parts should be done at run time. Not only do I work on the FreeBSD project generally, I also maintain a package building system that we use at $JOB to install packages on the various remote hosts. Having those packages do the right thing even if the package builder and the remote systems don't have identical configurations is a huge advantage. Doug -- We could put the whole Internet into a book. Too practical. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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
