Re: FreeBSD Port: boinc-einsteinathome-4.18_4,2
Hello, I don't know. David Whytcross píše v so 24. 03. 2012 v 14:52 +1100: Hi guys, am hoping you may be able to assist with an enquiry my FreeBSD 9.0 machine is fitted with an NVIDIA GEForce 210 card is it possible to utilize its CUDA GPU operability into boinc_setiathome_enhanced 6.12_1 regards, Dave Whytcross -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org A)bort, R)etry, H)it with big hammer signature.asc Description: This is a digitally signed message part
Re: [PATCH] proposal for x11-wm/windowmaker
On 2012/03/19 08:59, Arrigo Marchiori wrote: Hello, I am attaching a quick-and-dirty patch that should reallow compilation of x11-wm/windowmaker under 7-STABLE. The problem seems to be the missing macro HAVE_SYS_SELECT_H; the patch just forces it in the configure script if a FreeBSD system is detected. Have you sent this to the windowmaker port maintainer? -- 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: kdelibs3
Committed, thanks! Oliver Pinter píše v út 21. 02. 2012 v 01:41 +0100: Hi all! Please apply the attached patch to x11/kdelibs3/Makefile. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org With sufficient thrust, pigs fly just fine. -- RFC 1925 signature.asc Description: This is a digitally signed message part
Re: Plan to add a bsd.pure.mk
Brooks Davis píše v po 05. 12. 2011 v 10:15 -0600: On Mon, Dec 05, 2011 at 01:28:33AM -0600, Mark Linimon wrote: I would like to hold off on any more disruptive changes to the tree until we can get this release out the door. If that means devel/clang needs to stay at its current value (and only clang-devel updated), then that's fine. We don't actually need to add a bsd.pure.mk to upgrade llvm. We would need to complete the repocopy in ports/163030 and change the build and run depends in lang/pure which would change the depends of the 12ish ports involved. Similar changes are needed in a couple other ports. I'll leave it up to portmgr to decide if that's too disruptive. IMO if any change of this scope (an upgrade triggering less than dozen rebuilds, mostly of ports that aren't widely used) should be approved, it should be this one given our general toolchain focus. Just put it under /usr/ports/lang/pure/bsd.pure.mk and be done with it. We can always move it to /usr/ports/Mk later. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org God is real unless declared integer. signature.asc Description: This is a digitally signed message part
Re: postfix-current broken on amd64 platform
Sahil Tandon píše v so 19. 11. 2011 v 15:48 -0500: Wietse has made the change upstream and I plan to commit that in a little bit. Just running it through my tinderbox if folks don't mind the wait (a few hours). Not at all, and thanks both! -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org ... the obese drugged penguin used by Linux. -- Scott Long signature.asc Description: This is a digitally signed message part
Re: postfix-current broken on amd64 platform
Wietse Venema píše v čt 17. 11. 2011 v 15:41 -0500:
Pav Lucistnik:
Wietse Venema p??e v ?t 17. 11. 2011 v 13:23 -0500:
Actually, a Postfix built-in default setting changed on 20110918.
It now enables IPv6 unless this is turned off in a configuration
file. I can fix that at compile time, and thereby not trigger
the error on build systems with unexpected IPv6 configurations.
This is interesting.
The build jails are configured to have only IPv4 address on lo0,
but the host have both IPv4 and IPv6 configured on its lo0.
Changing the jail configuration is possible but if a reasonable
workaround can be made in postfix-current port I'd prefer not to touch
pointyhat configuration (unexpected consequences and all that...)
I can competely fix this specific error instance with a one-line
config file change, but I don't want to end up in the same boat
again when some other program needs to be run during build time.
A more proactive workaround would be to treat protocol not supported
as a non-fatal error, just like address family not supported is.
Please let me know if this works in the build cluster. It will log
a warning but that should be justfied, because the system does have
an abnormal configuration.
Yes, this works on the build cluster.
Sahil, can I commit it to the port?
Wietse
*** src/util/inet_proto.c-Tue Jan 8 15:36:13 2008
--- src/util/inet_proto.c Thu Nov 17 08:49:31 2011
***
*** 219,225
pf-dns_atype_list = make_unsigned_vector(3, T_A, T_, 0);
pf-sa_family_list = make_uchar_vector(3, AF_INET, AF_INET6, 0);
break;
! } else if (errno == EAFNOSUPPORT) {
msg_warn(%s: IPv6 support is disabled: %m, context);
msg_warn(%s: configuring for IPv4 support only, context);
/* FALLTHROUGH */
--- 219,225
pf-dns_atype_list = make_unsigned_vector(3, T_A, T_, 0);
pf-sa_family_list = make_uchar_vector(3, AF_INET, AF_INET6, 0);
break;
! } else if (errno == EAFNOSUPPORT || errno == EPROTONOSUPPORT) {
msg_warn(%s: IPv6 support is disabled: %m, context);
msg_warn(%s: configuring for IPv4 support only, context);
/* FALLTHROUGH */
--
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
Why does the Earth have colors?
signature.asc
Description: This is a digitally signed message part
Re: postfix-current broken on amd64 platform
Wietse Venema píše v čt 17. 11. 2011 v 13:23 -0500: Wietse Venema: Jase Thew: 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). ... Thanks, this is very helpful. That code has not changed in 6 years, so we are looking at an incompatible change in build environment. Actually, a Postfix built-in default setting changed on 20110918. It now enables IPv6 unless this is turned off in a configuration file. I can fix that at compile time, and thereby not trigger the error on build systems with unexpected IPv6 configurations. This is interesting. The build jails are configured to have only IPv4 address on lo0, but the host have both IPv4 and IPv6 configured on its lo0. Changing the jail configuration is possible but if a reasonable workaround can be made in postfix-current port I'd prefer not to touch pointyhat configuration (unexpected consequences and all that...) -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org MIPS: Meaningless Information Provided by Salesmen signature.asc Description: This is a digitally signed message part
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
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
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? -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org You have acquired a scroll entitled 'irk gleknow mizk' (n). This is an IBM Manual scroll. You are permanently confused. signature.asc Description: This is a digitally signed message part
Re: kdelibs3
Wouldn't it be better to flip CUPS options to default to off? Oliver Pinter píše v ne 09. 10. 2011 v 21:09 +0200: Hi pav! Is there any chance to include the attached patch to kdelib3 or something like that? thanks, Oliver -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org The number you dialed is imaginary. Please turn your phone by 90 degrees and try again. signature.asc Description: This is a digitally signed message part
Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
Warren Block píše v pá 15. 07. 2011 v 07:15 -0600: It could also be made polymorphic, basing what it does on the number of fields rather than a new DESKTOP_ENTRIESv2 define. I believe that's impossible because you can create several desktop entries by repeating the quadruple of values in this variable. Quite similar to OPTIONS. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org ... the obese drugged penguin used by Linux. -- Scott Long signature.asc Description: This is a digitally signed message part
Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
On 2011/07/14 00:57, Jung-uk Kim wrote: links.diff, metalink-editor.diff, tome.diff: - Add static desktop files to work around DESKTOP_ENTRIES limitations. This is a step backwards and I'll oppose it. -- 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: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
Stephen Montgomery-Smith píše v čt 14. 07. 2011 v 11:57 -0500: entry. I assume that the filename of the desktop entry is unimportant, The filename of desktop entry should be 100% inconsequential, and our only care should be not have two ports installing same file. and is used only internally by Gnome or whatever. Sounds like a bug to me. But maybe it would have been better to have had one more entry in DESKTOP_ENTRIES that was the actual filename of the desktop entry. Yes, but is it worth the effort? Note you'll have to introduce it somehow not to break existing ports. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org Cats happen. signature.asc Description: This is a digitally signed message part
Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
Jung-uk Kim píše v čt 14. 07. 2011 v 15:07 -0400:
entry. I assume that the filename of the desktop entry is
unimportant,
The filename of desktop entry should be 100% inconsequential, and
our only care should be not have two ports installing same file.
I believe the original intention was to use executable name to make
desktop file, i.e., ${PREFIX}/bin/foo - ${DESKTOPDIR}/foo.desktop.
Yes, and then came ports that needed to install several icons for same
executable, with different arguments. That was the reason for the
change.
and is used only internally by Gnome or whatever.
Sounds like a bug to me.
Why do you think there is a bug? Basically, desktop files are
meta-data for OSes which cannot handle extended attributes within a
No, .desktop files are just gnomeish equivalent of windows .pif files.
If they are used for something more significant, that's poor design by
my standards. That's why I wanted to get an opinion from gnome team
before taking any steps on this issue.
file (e.g., resource fork of Mac), if I understand it correctly. I
don't see anything wrong with GNOME referencing its window manager by
desktop file name rather than by executable name with obscure
options.
If that .desktop file was that critical for GNOME functionality, then
why it is not installed by vendor Makefiles and have to be hacked in in
the port??
DESKTOP_ENTRIES are for *basic* stuff and bsd.port.mk clearly says
complex desktop files cannot use it:
Yes but I see no need to abandon DESKTOP_ENTRIES for a simple port like
links..
--
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
Ragtime contained about forty-five seconds of Elizabeth McGovern
completely topless, but it got a PG in 1980. I have no idea why that
did, or Titanic got PG-13, yet Merchant of Venice gets tagged with
an R. The MPAA is an intellectual and aesthetic embarassment. --
comment from IMDb board on US movie rating system
signature.asc
Description: This is a digitally signed message part
Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
Jung-uk Kim píše v čt 14. 07. 2011 v 15:15 -0400:
On Thursday 14 July 2011 01:55 pm, Stephen Montgomery-Smith wrote:
On 07/14/2011 12:47 PM, Jung-uk Kim wrote:
Anyhow, I guess we can do it much simpler:
--- Mk/bsd.port.mk 3 Jul 2011 15:51:18 - 1.687
+++ Mk/bsd.port.mk 14 Jul 2011 17:26:43 -
@@ -6432,7 +6432,7 @@
${ECHO_CMD} @cwd ${DESKTOPDIR} ${TMPPLIST}; \
fi; \
while [ $$# -gt 6 ]; do \
- filename=`${ECHO_CMD} $$4 | ${TR} -cd [:alnum:]`.desktop;
\ + filename=`${BASENAME} $$4 | ${SED} -E
's/[[:space:]]+.*//'`.desktop; \
pathname=${DESKTOPDIR}/$$filename; \
categories=$$5; \
if [ -z $$categories ]; then \
I think this is much simpler and better fix.
Jung-uk Kim
I agree.
I'll commit this version tomorrow unless I see more objection.
Eh, don't you need to get portmgr@ approval before touching bsd.port.mk
by any chance ???
I could support allowing dash as one extra allowed char, and having that
change exp-run'ed.
--
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
With a 10 MHz 386 the downloading speed would most likely drop to a
crawl or stop with the decoding process etc. I think most 10MHz 386
users are quite accustomed to things dropping to a crawl.
signature.asc
Description: This is a digitally signed message part
Re: [RFC] A trivial change for DESKTOP_ENTRIES
On 2011/07/13 00:25, Jung-uk Kim wrote: After I updated x11-wm/compiz, GNOME was not able to start the window manager. Basically, it complained that compiz-manager was not found. Then, I realized compiz-manager.desktop was automagically replaced by compizmanager.desktop. Now I tracked it down to this commit: Sat Nov 27 17:42:46 2010 UTC (7 months, 2 weeks ago) by pav - DESKTOP_ENTRIES: commandline is used to name installed .desktop file, this can lead to files containing whitespace and funny characters; thus strip all non-alphanumeric characters http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk.diff?r1=1.656;r2=1.657 To me, it looks far too restrictive. At least, I'd like to allow '-' and '_'. Please see the attached patch. Any objections? Shouldn't you fix whatever is trying to call compizmanager not to use .desktop file instead? -- 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: [RFC] A trivial change for DESKTOP_ENTRIES
Jung-uk Kim píše v st 13. 07. 2011 v 11:41 -0400: On Wednesday 13 July 2011 07:39 am, Pav Lucistnik wrote: On 2011/07/13 00:25, Jung-uk Kim wrote: After I updated x11-wm/compiz, GNOME was not able to start the window manager. Basically, it complained that compiz-manager was not found. Then, I realized compiz-manager.desktop was automagically replaced by compizmanager.desktop. Now I tracked it down to this commit: Sat Nov 27 17:42:46 2010 UTC (7 months, 2 weeks ago) by pav - DESKTOP_ENTRIES: commandline is used to name installed .desktop file, this can lead to files containing whitespace and funny characters; thus strip all non-alphanumeric characters http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk.diff?r 1=1.656;r2=1.657 To me, it looks far too restrictive. At least, I'd like to allow '-' and '_'. Please see the attached patch. Any objections? Shouldn't you fix whatever is trying to call compizmanager not to use .desktop file instead? GNOME session manager calls the compiz-manager, i.e., the user has to change it manually. Actually, x11-wm/compiz/pkg-message recommended this: If you are using gnome, you can use the configuration editor to set the value of: desktop-gnome-session-required_components-windowmanager = compiz-manager ^^ This will enable compiz as your default window manager. What does the gnome@ people said about this whole issue? -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org KDE is for the techies who feel they can't be productive without being able to control the exact amount of bevel in their window frames in 2% increments. signature.asc Description: This is a digitally signed message part
Re: devel/geany-plugins
Committed, thanks!
Sergey V. Dyatko píše v čt 16. 06. 2011 v 13:44 +0300:
Hi,
pav@, can you remove BROKEN= from devel/geany-plugins? it doesn't build
with GEANY_GEANYLUA enabled, so quickdirty patch is:
--- /usr/ports/devel/geany-plugins/Makefile.orig2011-06-16
13:41:15.0 +0300
+++ /usr/ports/devel/geany-plugins/Makefile 2011-06-16
13:42:12.0 +0300 @@ -16,8 +16,6 @@ BUILD_DEPENDS=
geany:${PORTSDIR}/devel/geany RUN_DEPENDS=
geany:${PORTSDIR}/devel/geany
-BROKEN=does not compile
-
USE_GMAKE= yes
USE_GNOME= gtk20
USE_BZIP2= yes
@@ -28,7 +26,7 @@
GEANY_GEANYGDB GDB support (broken) off \
GEANY_GEANYLATEXImprove work with LaTeX on \
GEANY_GEANYLIPSUM GEANYLIPSUM on \
- GEANY_GEANYLUA LUA support on \
+ GEANY_GEANYLUA LUA support (broken) off \
GEANY_GEANYPRJ Alternative project
management on \ GEANY_GEANYSENDMAIL Sending mail from geany on \
GEANY_GEANYVC Version-control systems
support on \
--
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
Cry Havoc! And let slip the Dogs of Waw.
signature.asc
Description: This is a digitally signed message part
Re: Why archivers/thunar-archive plugin is broken
Olivier Duchateau píše v út 26. 04. 2011 v 19:23 +0200: Hi, I noticed port, archivers/thunar-archive-plugin is marked as broken. I'm using it, and it works fine under FreeBSD 8.2-RELEASE i386. May I have log, please ? Sure, http://portsmon.freebsd.org/portoverview.py?category=portname=thunar-archive-plugin Missing dependency most probably. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org Two sausages are in a frying pan. One says, Geez, it's hot in here isn't it? And the other one says, Aah! A talking sausage! signature.asc Description: This is a digitally signed message part
Re: Why archivers/thunar-archive plugin is broken
Ruslan Mahmatkhanov píše v út 26. 04. 2011 v 23:14 +0400: 26.04.2011 21:49, Pav Lucistnik пишет: Olivier Duchateau píše v út 26. 04. 2011 v 19:23 +0200: Hi, I noticed port, archivers/thunar-archive-plugin is marked as broken. I'm using it, and it works fine under FreeBSD 8.2-RELEASE i386. May I have log, please ? Sure, http://portsmon.freebsd.org/portoverview.py?category=portname=thunar-archive-plugin Missing dependency most probably. This patch should work. It does. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org It also explains why paper clips just lie there while you look at them, but as soon as you turn your back, they run away, giggling wildly, and transform themselves into coat hangers. signature.asc Description: This is a digitally signed message part
Re: [HEADS UP] Ports Infrastructure Changes
Henk van Oers píše v so 19. 03. 2011 v 23:29 +0100: From: Pav Lucistnik p...@freebsd.org Matthias Andree pí¹e v so 19. 03. 2011 v 09:52 +0100: [...] Where do you see the dividing line between web apps on one hand and on the other hand http servers ... everything related to apache? IOW, how do I decide if I put a new port into www-webapps or into www-servers for its primary category? Basically, everything that serves network is server and everything that generates pages on these servers is webapp. So: why is p5-Mojolicious in webapp, it serves network (main deployment). And it's a client too... COMMENT=A high level MVC web framework written in Perl Screams webapp to me, but, I don't know every existing software in detail so maybe I'm wrong here. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org In the beginning was the word, and the word was content-type: text/plain signature.asc Description: This is a digitally signed message part
Re: [HEADS UP] Ports Infrastructure Changes
Philip M. Gollucci píše v so 19. 03. 2011 v 00:51 -0400: If might be useful to coordinate this with the default switch from 1.3 No. Let's keep things simple, one thing at a time. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org The use of the lavatory is restricted to the train's cat. signature.asc Description: This is a digitally signed message part
Re: [HEADS UP] Ports Infrastructure Changes
Alex Dupre píše v so 19. 03. 2011 v 08:52 +0100: Martin Wilke ha scritto: www-clients - browsers, rss clients, wget-alike, webapi/soap clients, benchmarks www-servers - http servers, proxy servers, everything related to apache www-webapps - web apps, frameworks, libraries www (rest, not moved) - html editors, authoring tools, search engines .. I was wondering where you put httpcore and httpclient, two java libraries. Even if they are not webapp, from this categorization I'd say they should go there, but I found one in www and one in www-clients. Both will be moved to -clients, thanks. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org A mouse is a device used to point at the xterm you want to type in. signature.asc Description: This is a digitally signed message part
Re: [HEADS UP] Ports Infrastructure Changes
Alex Dupre píše v so 19. 03. 2011 v 14:29 +0100: Pav Lucistnik ha scritto: I was wondering where you put httpcore and httpclient, two java libraries. Even if they are not webapp, from this categorization I'd say they should go there, but I found one in www and one in www-clients. Both will be moved to -clients, thanks. So -clients is the container for client libraries, too? And which libraries goes into -webapp? Yes, client libraries go to -clients, SOAP/webservice/page slurpers go to -clients. Various frameworks, modules, and libraries used in these frameworks, ie stuff running on the server, goes to -webapps. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org Quantum physics was developed in the 1930's, as a result of a bet between Albert Einstein and Niels Bohr, to see who could come up with the most ridiculous theory and still have it published. signature.asc Description: This is a digitally signed message part
Re: [HEADS UP] Ports Infrastructure Changes
Alex Dupre píše v so 19. 03. 2011 v 14:24 +0100:
Miroslav Lachman ha scritto:
Maybe I misunderstand something, but where is Apache or Lighttpd server?
I can't find them on the www-server list or www.
Good catch, they aren't in any category :-) but should be in www-server.
Good God, they are really missing. Embarassing .. :)
They go to www-servers, of course.
--
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
An arrow (+0,+0) {@f0} finds a mark. It dies.
signature.asc
Description: This is a digitally signed message part
Re: [HEADS UP] Ports Infrastructure Changes
Thomas Sandford píše v so 19. 03. 2011 v 14:12 +: On 19/03/2011 01:49, Martin Wilke wrote: as the Ports Collection continue to grow, we have decided to do some changes to the category layout. The www category, second largest with over 2000 individual ports, will have three subcategories spinned out. On the other side, x11-servers category, with only 10 ports, will be folded into regular x11 category. ... Whilst we are at it, is now the time to create a voip or telephony category? Generally yes, this is one possibility. Another nice category would be xml. PS libvorbis is not voip-specific and should stay in audio. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org 42.7 percent of all statistics are made up on the spot. signature.asc Description: This is a digitally signed message part
Re: HEADS UP: Merge of binutils 2.17
Erik Cederstrand píše v ne 09. 01. 2011 v 00:10 +0100: I was pretty sure I couldn't improve anything with 5 minutes of thinking. I'm glad the most obvious things have already been done, and I'm sure you and others have put a lot of effort into this. My question was more what, if anything, can be done to speed up the cluster. Performance and numbers of build nodes is okay. What we really need here is faster, more robust scheduling infrastructure (master node software), linimon@ is working hard on this task. Also, how long does it take to complete an exp-run on the cluster? If everything goes smoothly, 20 hours wall time. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org Do not meddle in the fashions of wizards, for they are seasonal and quick to fall out of style! signature.asc Description: This is a digitally signed message part
Re: patch net/ushare: fix build on 8.1
Gennady píše v út 09. 11. 2010 v 23:51 +0200: With this patches port ushare compile and work. Checked up on FreeBSD 8.1 amd64. Committed, thanks! -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org You can't expect to wield supreme executive power just 'cause some watery tart threw a sword at you. signature.asc Description: This is a digitally signed message part
Re: Wrong lib version in UPDATING for devel/gettext
On 2010/05/31 13:46, Denny Lin wrote: Hi, I just upgraded to gettext 0.18, and I noticed that the entry in UPDATING seems to document the wrong version numbers: (from intl.7 to intl.8) should be (from intl.8 to intl.9) $ grep 'intl\.so' devel/gettext/pkg-plist lib/libintl.so lib/libintl.so.9 You're totally correct. I have just fixed the entry. -- 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: Mk/bsd.database.mk update for db50
Matthias Andree píše v po 26. 04. 2010 v 09:46 +0200: I have recently committed databases/db50. It is not yet hooked up for automatic inclusion through Mk/bsd.database.mk; please review the attached diff. This looks good to me. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Why did the stoplight turn red? You would too, if you had to change in front of all those people. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: boost 1.41 and net-p2p/deluge
Michal Varga píše v st 30. 12. 2009 v 01:01 +0100: After the recent boost upgrade to 1.41, net-p2p/deluge needs to be recompiled to actually start, otherwise one just gets a nice crash/deadlock (I didn't investigate as I already remember the exactly same issue with previous boost upgrade, so went directly for recompilation). I have bumped deluge, thanks for the report. Anyway, just an idea - shouldn't be those apps that depend on boost also bumped, to prevent issues like these? (again, might need some more investigation, this is just a quick notice) Bumping all ports en-masse sounds excessive to me. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Russians in the rear view mirror ... are closer than they appear. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Pointyhat packages
Dominic Fandrey píše v po 14. 12. 2009 v 16:54 +0100: Can't you just take a jail? Just wondering ... No, unfortunately, jail won't do. The box must be fully dedicated. -- Pav Lucistnik p...@oook.cz p...@freebsd.org See file. Click file. Get file. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: port www/libxul broken on sparc64, but builds even on ia64
Anton Shterenlikht píše v po 14. 12. 2009 v 17:04 +: Port www/libxul is marked as broken on sparc64. HOwever, it builds even on ia64! Could anybody comment on why this port is broken for sparc64? Here is the relevant log http://pointyhat.freebsd.org/errorlogs/sparc64-errorlogs/e.7.20090622032229/libxul-1.9.0.10.log.bz2 -- Pav Lucistnik p...@oook.cz p...@freebsd.org On real UNIX, /usr/bin/more prints -More-. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Pointyhat packages
Jonathan píše v čt 10. 12. 2009 v 09:50 -0500: On 12/8/2009 7:52 PM, Miroslav Lachman wrote: What is the policy for package building nodes? I mean, is it possible to use some machines not owned directy by FreeBSD.org? For example, I have spare machine in our rack which I can lend for some period (until some production machine goes down and needs to be replaced by this spare machine) or maybe I can set up some older unused machine (IBM x336). Is deploying of new node easy task or is it something special that is not useful to do for relatively short period of time? I was wondering about this myself. I have a dual quad system that is almost completely idle most of the time and would love to see it used for something helpful to the project. I can guarantee access to it for at least a year if that helps. That would be a remote node. It's possible, but it's not for everybody. First, it will generate an obscene amount of network traffic, both ways. Second, you need to fully surrender it and give us root on it. Also remote console access or at least power toggle would be good. Then Mark can borg it. :) -- Pav Lucistnik p...@oook.cz p...@freebsd.org Eat when you are hungry, sleep when you are tired. Chase butterflies when you want some fun. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: amd64 9-current packages
AN píše v út 08. 12. 2009 v 19:20 +: Is there an estimate for when packages will be available for amd64 9-current? Hi, currently no estimate. Really, running on CURRENT you should be building your own packages from source. With the limited horsepower available on amd64 side of pointyhat lately, I'm concentrating on getting useful packages of new GNOME/KDE for 7 and 8 done first. -- Pav Lucistnik p...@oook.cz p...@freebsd.org What do we know about love? Love is like a pear. Pear is sweet and have a specific shape. Try to exactly define the shape of a pear. -- Marigold: 50 Years Of Poetry signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Pointyhat packages
Mark Linimon píše v út 08. 12. 2009 v 14:17 -0600: On Tue, Dec 08, 2009 at 09:15:13AM -0300, oren.al...@gmail.com wrote: and some poinyhat build runs are never uploaded. Hmm, they should be. I'll forward this on to pav. (The way we have the work divided up is that pav does amd64; erwin does i386; I do sparc64 and Yes, I have decided not to upload some of the recent amd64 builds. The reasoning is that it's better to have a complete packageset on the mirrors with older software, than a new incomplete set that lacks popular software like GNOME or KDE. Ie. people can still add GNOME alas it's still previous GNOME release, instead of being unable to add GNOME at all. Hope this makes sense. -- Pav Lucistnik p...@oook.cz p...@freebsd.org MIPS: Meaningless Information Provided by Salesmen signature.asc Description: Toto je digitálně podepsaná část zprávy
[HEADS UP] ports tree fully unfrozen
With the impending public release of 8.0-RELEASE, we decided to lift the soft freeze that was in effect on the Ports Collection in past weeks. The ports tree is now fully open to commits. -- Pav Lucistnik p...@oook.cz p...@freebsd.org The Linimon's Rule: The More You Close, The More Will Come signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: FreeBSD Port: gtkam-0.1.16.1_1
Sven Göttner píše v po 16. 11. 2009 v 21:26 +0100: Adding add path 'ugen*' 0660 group operator to /etc/devfs.rules (as done before for USB sticks) and restarting devfs and devd via the /etc/rc.d/dev* scripts finally solved the problem and now also non-root users are able to connect to the camera via PTP. Yes, this is even included in the gphoto online docu at http://gphoto.sourceforge.net/doc/manual/permissions-usb.html#usb-on-FreeBSD But I just keep running sudo gphoto2, simpler for me :) -- Pav Lucistnik p...@oook.cz p...@freebsd.org Any Palm app requiring an 90+ page manual has lost its vision. -- words about DateBk4 on Action Names list signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Latest/perl.tbz symlink missing on FTP mirrors
Philip M. Gollucci píše v po 21. 09. 2009 v 01:15 -0400: Pav Lucistnik wrote: Hi Jeremy, yes, we (portmgr) noticed this too. But we don't know why it happens, yet. I'm 99% sure its because lang/perl5.10 is built after lang/perl5.8 and the latter sets NO_LATEST_LINK=yes. If that's the cause, we have a serious bug in our infrastructure. 1) lang/perl5.10 should set latest link to perl5.10 2) it should not set no latest link 3) lang/perl5.8 should set latest link to perl5.8 No, pkg_add -r perl needs to keep working with intuitive results. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Two sausages are in a frying pan. One says, Geez, it's hot in here isn't it? And the other one says, Aah! A talking sausage! signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Latest/perl.tbz symlink missing on FTP mirrors
Philip M. Gollucci píše v po 21. 09. 2009 v 16:19 -0400: Well that might be the 'current' case, but lang/perl5.10's latest link has not been present for 6+ months. Because the port declares NO_LATEST_LINK in it's Makefile! -- Pav Lucistnik p...@oook.cz p...@freebsd.org I want to earn the right to be obnoxious before I'm too bitter to really enjoy it. -- Able signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Latest/perl.tbz symlink missing on FTP mirrors
Hi Jeremy,
yes, we (portmgr) noticed this too. But we don't know why it happens,
yet.
Jeremy Chadwick píše v ne 20. 09. 2009 v 08:34 -0700:
I came across the below today while rebuilding one of my boxes. It
appears the perl.tbz symlink in Latest/ on the FTP mirrors has gone
missing:
gujoja# pkg_add -r perl
Error: FTP Unable to get
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-7-stable/Latest/perl.tbz:
File unavailable (e.g., file not found, no access)
pkg_add: unable to fetch
'ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-7-stable/Latest/perl.tbz'
by URL
gujoja# ftp
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-7-stable/Latest/
Trying 204.152.184.73...
Connected to ftp.freebsd.org.
220 Welcome to freebsd.isc.org.
{snip}
ftp dir perl*
227 Entering Passive Mode (204,152,184,73,216,226)
150 Here comes the directory listing.
lrwxr-xr-x1 110 1002 26 Aug 03 14:39 perlconsole.tbz -
../All/perlconsole-0.4.tbz
lrwxr-xr-x1 110 1002 24 Aug 03 14:39 perldap.tbz -
../All/perldap-1.4.1.tbz
lrwxr-xr-x1 110 1002 24 Sep 07 05:21 perlftlib.tbz -
../All/perlftlib-1.2.tbz
lrwxr-xr-x1 110 1002 28 Sep 07 05:21 perltidy.tbz -
../All/perltidy-20090616.tbz
ftp cd ../All
250 Directory successfully changed.
ftp dir perl*
227 Entering Passive Mode (204,152,184,73,123,76)
150 Here comes the directory listing.
-rw-r--r--1 110 1002 13542336 Jul 12 06:04 perl-5.10.0_4.tbz
-rw-r--r--1 110 1002 12015615 Jun 14 20:59 perl-5.8.9_3.tbz
-rw-r--r--1 110 100241343 Jun 15 19:01 perl2html-0.9.2_1.tbz
-rw-r--r--1 110 1002 9633 Aug 01 11:34 perlconsole-0.4.tbz
-rw-r--r--1 110 1002 116249 Aug 19 07:03 perldap-1.4.1.tbz
-rw-r--r--1 110 100239772 Aug 19 09:57 perlftlib-1.2.tbz
-rw-r--r--1 110 1002 263681 Aug 17 07:52 perltidy-20090616.tbz
226 Directory send OK.
The workaround should be obvious, but here it is for users anyway:
gujoja# pkg_add -r
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-7-stable/All/perl-5.8.9_3.tbz
Fetching
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-7-stable/All/perl-5.8.9_3.tbz...
Done.
{snip}
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
On second thought, let's not go to Camelot. It is a silly place.
signature.asc
Description: Toto je digitálně podepsaná část zprávy
Re: Migration to new SourceForge URL scheme part 2, SFE and some statistics
This looks quite impressive. Please commit it. Dmitry Marakasov píše v st 02. 09. 2009 v 07:14 +0400: Hi! Second (smaller) part ready. This eliminates SOURCEFORGE_EXTENDED as it is not really needed, also translates all SFE ports to new SF scheme. Patch: http://people.freebsd.org/~amdmi3/sourceforge-extended.patch Here's a little stats on SF mirrors (mirrors were taken from sourceforge mirror selection pages as well as our sites.mk): MIRROR OK REDIRFAIL (*) biznetnetworks: 94.71% 5.16% 0.13% (*)dfn: 26.01% 73.91% 0.08% easynews: 0.00% 99.95% 0.05% (*) freefr: 94.81% 5.16% 0.03% (*) garr: 54.40% 45.47% 0.13% (*) heanet: 94.84% 5.16% 0.00% (*) internode: 91.41% 8.52% 0.08% (*) iweb: 94.76% 5.16% 0.08% (*) jaist: 89.83% 5.16% 5.01% keihanna: 0.00% 0.00% 100.00% (*) kent: 91.43% 8.54% 0.03% mesh: 0.00% 99.82% 0.18% (*) nchc: 91.38% 8.57% 0.05% osdn: 94.76% 0.00% 5.24% (*)ovh: 34.22% 65.78% 0.00% puzzle: 0.00% 38.92% 61.08% (*) softlayer: 91.41% 8.54% 0.05% (*) sunet: 94.66% 5.16% 0.18% superb-east: 0.00% 99.79% 0.21% (*)surfnet: 94.76% 5.16% 0.08% switch: 94.81% 5.16% 0.03% (*) transact: 91.38% 8.54% 0.08% (*) ufpr: 94.81% 5.16% 0.03% (*) voxel: 91.46% 8.54% 0.00% There also are belnet and (*)ncu which were completely unreachable. Asterisk means the mirror is listed in SF mirror selection page. FAIL is any reply beside HTTP 200 and 302 from mirror. This was tested against all SF ports, so as you can see, SFE is of no use as all mirrors generally mirror all projects. Not sure what's the cause of redirects for several mirrors though, maybe load balancing thingy. Statistics made separately for SFE ports are roughtly similar. Thus, all mirrors are merged into MASTER_SITE_SOURCEFORGE. I've also resorted them based on availability and quick download speed survey from some machines across the world I have access for: MirrorFreefall Pegasus Localhost iweb 1.89 MB/s 2.60 MB/s 1.15 MB/s heanet 1.02 MB/s 5.70 MB/s 2.16 MB/s sunet732 KB/s 4.85 MB/s 1.42 MB/s freefr590 KB/s 1.13 MB/s 1.96 MB/s jaist893 KB/s 1.62 MB/s548 KB/s switch520 KB/s 10.4 MB/s 1.57 MB/s surfnet515 KB/s 7.53 MB/s 1.72 MB/s nchc 1.01 MB/s 1.11 MB/s503 KB/s voxel 2.19 MB/s461 KB/s637 KB/s osdn403 KB/s544 KB/s621 KB/s softlayer447 KB/s420 KB/s399 KB/s transact732 KB/s791 KB/s370 KB/s kent353 KB/s 1.33 MB/s 2.65 MB/s internode969 KB/s758 KB/s167 KB/s biznetnetworks189 KB/s381 KB/s 92.0 KB/s garr failed failed failed ufpr989 KB/s519 KB/s failed dfn failed failed failed ovh failed failed failed Hosts are freefall.freebsd.org (US, CA), pegasus.timeweb.ru (RU, SPB), and amdmi3-ext.interlan.ru (RU, MSK). Sorting is based on minimal speed out of three. If you can propose better sorting - please go ahead. Also, you can use this script: http://people.freebsd.org/~amdmi3/sf-speed.sh to find the fastest mirrors for you (to override MASTER_SITE_SOURCEFORGE) and/or to mail me so I improve sorting. Expect the script to download 200MB - it downloads ~10MB file from 20 mirrors. -- Pav Lucistnik p...@oook.cz p...@freebsd.org How will you recognize experienced hacker from beginner? Beginner thinks that kilobyte have 1000 bytes. Experienced hacker thinks one kilometer have 1024 meters. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Migration to new SourceForge url scheme now inevitable, solution
Dmitry Marakasov píše v pá 21. 08. 2009 v 07:50 +0400: [1] http://people.freebsd.org/~amdmi3/sfp.patch [2] http://people.freebsd.org/~amdmi3/sfp.log This looks good so far. PS. Btw, SOURCEFORGE_EXTENDED and SOURCEFORGE_JP still use an old scheme. Because of that SFE can no longer include SF, and honestly, I JP is completely separate thing, so I'd leave it alone for now. SF_E can be axed if all the files fetch from regular SF. IIRC there were some projects in the past that were only distributed on SF_E sites, not on SF sites? -- Pav Lucistnik p...@oook.cz p...@freebsd.org Why does the Earth have colors? signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Migration to new SourceForge url scheme now inevitable, solution
Dmitry Marakasov píše v pá 21. 08. 2009 v 22:12 +0400: Which also worries me is that I'm going out of city till monday - will it be OK to commit the patch this night? Well, it shouldn't break anything not yet broken, but still. If it's ok, I'll commit it in ~6hrs after finishing manual work and running a quick check for fetchability. I think it should go in tonight. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Video games don't affect kids, I mean if Pac Man affected us as kids, we'd all run around in a darkened room munching pills and listening to repetitive music. -- Kristian Wilson, CEO at Nintendo Gaming Corporation Inc signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Migration to new SourceForge url scheme now inevitable, solution
Dmitry Marakasov píše v čt 20. 08. 2009 v 20:40 +0400: * Paul Schmehl (pschmehl_li...@tx.rr.com) wrote: I've been following this discussion closely since several of my ports fetch from Sourceforge. Is it safe to assume that some global solution will be applied to the ports tree? Or are we maintainers going to need to submit PRs for affected ports once a solution is agreed upon? This should be done globally, or else we'll end up with 90% unfetchable SF ports for 8.0 release. I'm preparing the patch currently. Once you have a patch, send it over for eyeball-review and approval. Thanks for attacking this! -- Pav Lucistnik p...@oook.cz p...@freebsd.org 42.7 percent of all statistics are made up on the spot. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: devel/boost: request for an exp-run
Hi Alexander, unfortunately no, as pointyhat has been busy with other patches. Suddenly everyone wants to get their changes in before 8.0-RELEASE. Alexander Churanov píše v út 21. 07. 2009 v 19:50 +0400: Hi Pav! Did you manage to start an exp-run? I'd like to start fixing issues as soon as possible, if there are any. Looks like we have chances for the boost-1.39 to be included in 8.0. Sincerely, Alexander Churanov 2009/7/15 Pav Lucistnik p...@freebsd.org: Okay Alexander Churanov píše v st 15. 07. 2009 v 19:58 +0400: Folks, I've created an updated version of boost ports that fixes almost all issues reported after an exp-run. Please, make another exp-run, if possible. The updated diff is at http://alexanderchuranov.com/boost-port/boost-2009-07-14-15-33.diff The updated tarball is at http://alexanderchuranov.com/boost-port/boost-ports-20090710.tar.bz2 The procedure is as follows: 1) Download the tarball and unpack under /usr/ports/devel 2) Go to /usr/ports, download and apply the patch 3) Remove 'devel/boost' and 'devel/boost-python' ports 4) Rebuild ports Sincerely, Alexander Churanov, maintainer of devel/boost-* -- Pav Lucistnik p...@oook.cz p...@freebsd.org Orfax's hip flask contained Old Janx Spirit, a mixture of potions of stupidity, paralysis, naivery, ruination, lose memories, confusion, and slime mold juice, with a twist of lemon. - from a post on Angband Community Forum -- Pav Lucistnik p...@oook.cz p...@freebsd.org Pain clots and unformed lice pat this train. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: devel/boost: request for an exp-run
Okay Alexander Churanov píše v st 15. 07. 2009 v 19:58 +0400: Folks, I've created an updated version of boost ports that fixes almost all issues reported after an exp-run. Please, make another exp-run, if possible. The updated diff is at http://alexanderchuranov.com/boost-port/boost-2009-07-14-15-33.diff The updated tarball is at http://alexanderchuranov.com/boost-port/boost-ports-20090710.tar.bz2 The procedure is as follows: 1) Download the tarball and unpack under /usr/ports/devel 2) Go to /usr/ports, download and apply the patch 3) Remove 'devel/boost' and 'devel/boost-python' ports 4) Rebuild ports Sincerely, Alexander Churanov, maintainer of devel/boost-* -- Pav Lucistnik p...@oook.cz p...@freebsd.org Orfax's hip flask contained Old Janx Spirit, a mixture of potions of stupidity, paralysis, naivery, ruination, lose memories, confusion, and slime mold juice, with a twist of lemon. - from a post on Angband Community Forum signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Request for exp-run (devel/boost)
Alexander Churanov píše v čt 11. 06. 2009 v 02:00 +0400: I've created an update for devel/boost, but did not verify that ALL software that depends on it builds and runs successfully. Some ports are really huge, like OpenOffice or KDE. Could we have and exp-run for updated devel/boost? You should really send these to portmgr@ otherwise they might be overlooked. Anyway, I have started the exp-run. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Every man is as God made him, ay, and often worse. -- Miguel de Cervantes signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: request for exp-run, comments: eliminate USE_X_PREFIX
Dmitry Marakasov píše v út 09. 06. 2009 v 18:33 +0400: * Pav Lucistnik (p...@freebsd.org) wrote: Here's it: http://people.freebsd.org/~amdmi3/xprefix_obliterate.1.patch Thank you, queued. Ok, it's already finished and the only failure is x11/libsx which I've mistakingly patched in another working copy. I've checked in and two ports dependent on it locally. So, may I commit it? Where are you tracking the progress of it? I'm curious. There's still few hundreds to go. I will send you an email when it's really finished. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Homer 1. American bonehead 2. Pull a Homer - to succeed despite idiocy signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: request for exp-run, comments: eliminate USE_X_PREFIX
Dmitry Marakasov píše v út 09. 06. 2009 v 18:48 +0400: * Pav Lucistnik (p...@freebsd.org) wrote: Where are you tracking the progress of it? I'm curious. http://pointyhat.freebsd.org/errorlogs/amd64-7-exp-latest/ Btw, I remember there was some more useful view, something like `previously unknown failures list'. Was there really, and where? This page is as useful as it gets. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Any sufficiently advanced technology is indistinguishable from magic. -- Arthur C. Clarke signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: request for exp-run, comments: eliminate USE_X_PREFIX
Dmitry Marakasov píše v so 06. 06. 2009 v 07:13 +0400: * Pav Lucistnik (p...@freebsd.org) wrote: The experimental run is nearly over, so far 15 failures found and sent in separate mails. Once you have next iteration of the patch, I'll be happy to run it again. Here's it: http://people.freebsd.org/~amdmi3/xprefix_obliterate.1.patch Thank you, queued. Also I forgot to mention that this is better to be run on i386, as many ports depend on xview which is i386-only. i386 is operated by erwin@ so try talking to him. But I must warn you that i386 run will take about a week, due to much older hardware we have available for it. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Quantum physics was developed in the 1930's, as a result of a bet between Albert Einstein and Niels Bohr, to see who could come up with the most ridiculous theory and still have it published. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: emulators/linux_base-f10 = Fedora 8?
Doug Barton píše v út 02. 06. 2009 v 13:50 -0700: Mark Linimon wrote: Then mark the port BROKEN, or some such. User confusion is a bad thing. :) s/BROKEN/IGNORE/ Just wonder, can/should it be implemented automagically via the repocopy script? I have no opinion, but will note that as long as you don't connect the ports to the category Makefile, you don't need to worry about things like this :-) The problem that I responded to was users who surf into those directories that expect useful things to happen. That problem isn't fixed by not hooking them up. If it's easy to add this feature to the repocopy script then I would suggest it be done. How about abandoning the whole concept of repocopies instead? -- Pav Lucistnik p...@oook.cz p...@freebsd.org Bento's Law: If It Can Break, It Will Break Bento's Corollary: If It Can Break, Kris Can Send Mail About It signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: request for exp-run, comments: eliminate USE_X_PREFIX
Dmitry Marakasov píše v po 01. 06. 2009 v 20:02 +0400: Thought we've switched to modular xorg more than a year ago, some ports still define USE_XLIB and thus depend on all X libraries (even when it's not really required). Which is even worse, USE_XLIB is implicitely defined for ports that define USE_IMAKE, some of which don't require any X libraries at all. This patch adds USE_XORG to (hopefully) all USE_IMAKE ports and some (but not all) USE_XLIB ports. It also makes USE_IMAKE ports no more implicitely define USE_XLIB and eliminates all mentions of USE_X_PREFIX from bsd.port.mk. It requires an exp-run, as though I've tested all changed ports in a local tinderbox, there may be ports with incomplete X dependencies further down dependency chains. http://people.freebsd.org/~amdmi3/xprefix_obliterate.patch Comments are welcome. Actually I think we could drop X11BASE related bits as well. This looks very useful, indeed, I was tempted to try to do some work in this direction myself. Your patch looks like a lot of work went into it already - let me run it on pointyhat. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Sun couldn't care less about Linux other than it now being necessary in order to be buzzword compliant. -- Al Dente signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Proposal: USE_GNU89 switch
Ed Schouten píše v pá 29. 05. 2009 v 14:36 +0200: This is why I'm proposing a USE_GNU89 switch, to force the ports framework to add -std=gnu89 to the CFLAGS. Placing CFLAGS+= -std=gnu89 would not work? Would the flag do anything else except adding to CFLAGS? -- Pav Lucistnik p...@oook.cz p...@freebsd.org Me go and see Elves and all! Hooray! signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: pkg_add errors
Dominic Fandrey píše v st 27. 05. 2009 v 18:43 +0200: During my last run of 'pkg_upgrade -a', cups-client forgot to install the library libcups.so.2, which I fortunately recognized due to my routine of running pkg_libchk after every package/port upgrade. Running 'pkg_upgrade cups-client' fixed that problem. The interesting part is, that the reinstallation of cups-client was done from the same package. So either pkg_add, tar or the file system were to blame, because the package is without fault. I expect that this unreliability of pkg_add (or the underlying systems) has a severe impact on my further development of pkg_upgrade. I think it was entirely different story -- installation of cups-client (put libcups on disc) upgrade of cups-base (remove libcups from disc) -- Pav Lucistnik p...@oook.cz p...@freebsd.org 94 outdated ports on the box, 94 outdated ports. Portupgrade one, an hour 'til done, 82 outdated ports on the box. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: MAKE_JOBS_UNSAFE (some more ports)
David Naylor píše v po 25. 05. 2009 v 10:11 +0200:
This part looks OK, I wonder if there's any reason t ain't like
this now; Pav?
-.if defined(MAKE_JOBS_NUMBER)
+MAKE_JOBS_NUMBER?= `${SYSCTL} -n kern.smp.cpus`
_MAKE_JOBS= -j${MAKE_JOBS_NUMBER}
-.else
-_MAKE_JOBS= -j`${SYSCTL} -n kern.smp.cpus`
-.endif
Wouldn't that mean an evaluation of the backtick command in every
make(1) invocation? That would be highly undesirable.
I don't believe that is the case.
Here is what I get with the patch applied (MAKE_JOBS_NUMBER not defined):
/usr/ports/editors/openoffice.org-3# make -V MAKE_JOBS_NUMBER -V
_MAKE_JOBS `/sbin/sysctl -n kern.smp.cpus`
-j`/sbin/sysctl -n kern.smp.cpus`
Wouldn't this indicate that the backtick command is not being evaluated?
Seems correct. But explain again, why you need this change?
Not all ports use make but are concurrent capable and require different
arguments to be passed which is why I needed to expose MAKE_JOBS_NUMBER
(since it is just a number) and why _MAKE_JOBS was not an option.
Ok, how about doing a dirty hack and using ${_MAKE_JOBS:C/-j//} ?
Then we wouldn't have to modify bsd.port.mk ..
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
Why do we need a film of Lord of the Rings when we have the book?
Because watching a cg enhanced Legolas fire a flaming arrow
into the heart of a warg is cool?
- a...@asdf.com in rec.games.roguelike.angband
signature.asc
Description: Toto je digitálně podepsaná část zprávy
Re: MAKE_JOBS_UNSAFE (some more ports)
Ion-Mihai Tetcu píše v so 23. 05. 2009 v 13:51 +0300:
- MAKE_JOBS_NUMBER defaults (but user defined) to number of cores
This part looks OK, I wonder if there's any reason t ain't like this
now; Pav?
-.if defined(MAKE_JOBS_NUMBER)
+MAKE_JOBS_NUMBER?= `${SYSCTL} -n kern.smp.cpus`
_MAKE_JOBS= -j${MAKE_JOBS_NUMBER}
-.else
-_MAKE_JOBS= -j`${SYSCTL} -n kern.smp.cpus`
-.endif
Wouldn't that mean an evaluation of the backtick command in every
make(1) invocation? That would be highly undesirable.
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
See file. Click file. Get file.
signature.asc
Description: Toto je digitálně podepsaná část zprávy
Re: [announce] bsd.port.options.mk available
Dmitry Marakasov píše v pá 22. 05. 2009 v 18:31 +0400: * Pav Lucistnik (p...@freebsd.org) wrote: we finally decided that enough users migrated to recent enough FreeBSD versions that we can finally suggest that maintainers can start using bsd.port.options.mk file in their ports. The examples in Porter's Handbook had been updated to illustrate a new usage. This will solve the problem with USE_* flags people were seeing. Perhaps we can also start to deprecate WANT_*? Looks a bit radical to me. Or is there a good reason to do so? -- Pav Lucistnik p...@oook.cz p...@freebsd.org Silence is an oasis in the desert of everlasting chatter. -- Quincy signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: [announce] bsd.port.options.mk available
Dmitry Marakasov píše v ne 24. 05. 2009 v 19:33 +0400:
* Pav Lucistnik (p...@freebsd.org) wrote:
Perhaps we can also start to deprecate WANT_*?
Looks a bit radical to me. Or is there a good reason to do so?
I meant slow transition from WANT_, like we do with
${MASTER_SITE_SOURCEFORCE} - SF. WANT_* feel clumsy and inconsistent,
as sometimes it is not needed (i.e. I can use USE_* after pre.mk),
and sometimes it is not available (i.e. not WANT_QT4).
I'm okay with slow transition. BTW I never understood why we need SF in
place of MASTER_SITE_SOURCEFORGE...
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
But soft, what light through yonder window breaks? It is the East, and
Juliet is the sun! Arise, fair sun, and kill the envious moon, who is
already sick and pale with grief that thou her maid art far more fair
than she.
signature.asc
Description: Toto je digitálně podepsaná část zprávy
Re: MAKE_JOBS_UNSAFE (some more ports)
Ion-Mihai Tetcu píše v ne 24. 05. 2009 v 19:01 +0300:
On Sun, 24 May 2009 16:10:23 +0200
Pav Lucistnik p...@freebsd.org wrote:
Ion-Mihai Tetcu píše v so 23. 05. 2009 v 13:51 +0300:
- MAKE_JOBS_NUMBER defaults (but user defined) to number of
cores
This part looks OK, I wonder if there's any reason t ain't like this
now; Pav?
-.if defined(MAKE_JOBS_NUMBER)
+MAKE_JOBS_NUMBER?= `${SYSCTL} -n kern.smp.cpus`
_MAKE_JOBS= -j${MAKE_JOBS_NUMBER}
-.else
-_MAKE_JOBS= -j`${SYSCTL} -n kern.smp.cpus`
-.endif
Wouldn't that mean an evaluation of the backtick command in every
make(1) invocation? That would be highly undesirable.
Umm, why? it shouldn't be evaluated if MAKE_JOBS_NUMBER is defined, no?
Am I missing some make magic here?
But for 99.99% of the users, MAKE_JOBS_NUMBER is not defined.
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
... the obese drugged penguin used by Linux. -- Scott Long
signature.asc
Description: Toto je digitálně podepsaná část zprávy
Re: bsd.port.options.mk
Philip M. Gollucci píše v čt 21. 05. 2009 v 22:34 -0400: +20090521: +AUTHOR: port...@freebsd.org + + * bsd.port.options.mk is now clear to be widely used. + Are there any existing examples of how one should use this or porters handbook sections ? There is an example in Porter's Handbook, all you need is to look :) -- Pav Lucistnik p...@oook.cz p...@freebsd.org EMACS: Eight Megabytes And Continually Swapping signature.asc Description: Toto je digitálně podepsaná část zprávy
[announce] bsd.port.options.mk available
Dear, we finally decided that enough users migrated to recent enough FreeBSD versions that we can finally suggest that maintainers can start using bsd.port.options.mk file in their ports. The examples in Porter's Handbook had been updated to illustrate a new usage. This will solve the problem with USE_* flags people were seeing. -- Pav Lucistnik p...@oook.cz p...@freebsd.org In the computer industry, there are three kinds of lies: lies, damn lies, and benchmarks. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: MAKE_JOBS_UNSAFE (some more ports)
On Thu, 21 May 2009 12:05:22 +0200, David Naylor wrote The following ports failed to build on my system (with a quad core) and FORCE_MAKE_JOBS set. They did success to build once I added MAKE_JOBS_UNSAFE=yes to their Makefile's. Marked in CVS, thank you! Is there any effort to mark ports as MAKE_JOBS_SAFE: is it desired for ports that are successful with FORCE_MAKE_JOBS to be reported? Yes, I believe they should be reported. -- 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
Duplicate LATEST_LINKS
...@ipfw.ru spandsp-devel/space/portstreesports/comms/spandsp-devel5 po...@freebsd.org squirrelmail-compatibility-plugin /space/portstreesports/mail/squirrelmail-compatibility-plugin tabtho...@freebsd.org squirrelmail-compatibility-plugin /space/portstreesports/mail/squirrelmail-compatibility-plugin1 tabtho...@freebsd.org stardict /space/portstreesports/textproc/stardict3 d9364...@mail.nchu.edu.tw stardict /space/portstreesports/textproc/stardict2 delp...@freebsd.org subcommander /space/portstreesports/devel/subcommander cyberb...@cyberbotx.com subcommander /space/portstreesports/devel/subcommander2 cyberb...@cyberbotx.com swt /space/portstreesports/x11-toolkits/swt31 freebsd-ecli...@freebsd.org swt /space/portstreesports/x11-toolkits/swt rnol...@freebsd.org tftp-hpa /space/portstreesports/ftp/tftp-hpa bro...@freebsd.org tftp-hpa /space/portstreesports/net/tftp-hpa ed...@mavetju.org tinymce /space/portstreesports/www/tinymce n...@foobar.org tinymce /space/portstreesports/www/tinymce3 sunp...@sunpoet.net tk85-threads /space/portstreesports/x11-toolkits/tk84-thread m...@freebsd.org tk85-threads /space/portstreesports/x11-toolkits/tk85-thread m...@freebsd.org tolua/space/portstreesports/lang/tolua ed...@mavetju.org tolua/space/portstreesports/lang/tolua50 ed...@mavetju.org vmware-guestd/space/portstreesports/emulators/vmware-guestd5 matus...@freebsd.org vmware-guestd/space/portstreesports/emulators/vmware-guestd6 matus...@freebsd.org vmware-tools /space/portstreesports/emulators/vmware-tools5 matus...@freebsd.org vmware-tools /space/portstreesports/emulators/vmware-tools6 matus...@freebsd.org xdelta /space/portstreesports/misc/xdelta s...@freebsd.org xdelta /space/portstreesports/misc/xdelta3 s...@freebsd.org -- Pav Lucistnik p...@oook.cz p...@freebsd.org lofi My _sympathetic_ opinion about kdevelop is that it's a huge pile of shit that might at least work okay if used in Linux. lofi My neutral opinion is that it's just a huge pile of shit. signature.asc Description: Toto je digitálně podepsaná část zprávy
[HEADS UP] ports tree now fully open
With the availability of 7.2-RELEASE, the ports collection is now fully open for changes. Have fun :) -- Pav Lucistnik p...@oook.cz p...@freebsd.org Bento's Law: If It Can Break, It Will Break Bento's Corollary: If It Can Break, Kris Can Send Mail About It signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: broken INDEX
Dominic Fandrey píše v ne 19. 04. 2009 v 11:30 +0200: ftp://ftp.uk.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/INDEX lists the package youtube_dl-2009.04.06_1, however ftp://ftp.uk.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/All/youtube_dl-2009.04.06_1.tbz does not exist. The package does exist on pointyhat, so perhaps you hit into a middle of the mirror updating from its upstream server. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Fairy tales do not tell children that dragons exist. Children already know dragons exist. Fairy tales tell children that dragons can be killed. -- G. K. Chesterton signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Ports requiring MAKE_JOBS_UNSAFE
David Naylor píše v ne 12. 04. 2009 v 10:28 +0200: Thanks. I've found another port, although this one appears to work with MAKE_JOBS_NUMBER=1 (but not above 1). audio/nas Marked unsafe, thank you for report. -- Pav Lucistnik p...@oook.cz p...@freebsd.org The Linimon's Rule: The More You Close, The More Will Come signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: [rubygems-]: Request for Review and -exp Run
Philip M. Gollucci píše v st 08. 04. 2009 v 12:10 -0400:
Hi guys,
If this is something good, I'll file a pr with it.
CVS Log:
- convert to RUBYGEM_AUTOPLIST
remove x-generate-plist and friends
- use RF macro and remove SUBDIR where possible
- remove some uneeded GEM_NAME=${DISTNAME}
(this c/should be handled better in bsd.*.mk)
None of this changes the resultant packages, so no PORTREVISIONs
where bumped except the 1 noted below.
individual ports:
audio/rubygem-mp3info - unbreak, fix packaging, bump PORTREVISION
devel/rubygem-rapt- adopt
devel/rubygem-rspec - remove BUILD_DEPENDS=RUN_DEPENDS -- neither set
devel/rubygem-ruby2ruby - add #' for vim highlight
graphics/rubygem-extifr - drop PORTREVISION=0
graphics/rubygem-gd2 - add #' for vim highlight
www/rubygem-rubyfulsoup - swap GEM_NAME / DISTNAME for constistency
Diff:
-
http://people.freebsd.org/~pgollucci/rubygems.diff
If only the individual ports are changed, we does not need to waste
resources on exp run. Just run these seven ports in Tinderbox...
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
What do we know about love? Love is like a pear. Pear is sweet and have
a specific shape. Try to exactly define the shape of a pear. --
Marigold: 50 Years Of Poetry
signature.asc
Description: Toto je digitálně podepsaná část zprávy
Re: [rubygems-]: Request for Review and -exp Run
Philip M. Gollucci píše v st 08. 04. 2009 v 14:50 -0400: Diff: - http://people.freebsd.org/~pgollucci/rubygems.diff If only the individual ports are changed, we does not need to waste resources on exp run. Just run these seven ports in Tinderbox... Would have helped if you looked at the diff or did you and that still applies ? Those seven ports have the deltas listed in *ADDITION* to the first 3 which are global across all remaining rubygem-* ports (except maybe mongrel and merb) $ grep -c Index: rubygems.diff 111 Ah. Was misled by the proposed commit log. I will queue it for exp-run. But cannot guarantee it will run before the freeze starts. -- Pav Lucistnik p...@oook.cz p...@freebsd.org It whines, glows and fades... signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: [rubygems-]: Request for Review and -exp Run
Philip M. Gollucci píše v st 08. 04. 2009 v 15:03 -0400: When is the freeze supposed to be over ? Max two weeks, hopefully. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Bento's Law: If It Can Break, It Will Break Bento's Corollary: If It Can Break, Kris Can Send Mail About It signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Status of devel/boost upgrade
Dmitry Marakasov píše v út 07. 04. 2009 v 20:13 +0400: * Alexander Churanov (alexanderchura...@gmail.com) wrote: We'll need an exp-run for it anyway, so I guess it's OK. If you have a patch ready, I suggest to file a PR and mail pav@ to do exp-run for it. If there are no major failures, we can push it into the tree, else we won't be bored during the freeze fixing it. As I understand this, it's OK to file a PR for just updating to 1.38, but port re-organization is delayed until 7.2 is released. Is this correct? Better ask pav (cc'd). I myself see no reason why not do both update and split in one go. If it passes testing, you can do it in one pass. BTW what's the proposed new ports? -- Pav Lucistnik p...@oook.cz p...@freebsd.org Maybe I should go ask that elvish wizard standing over there (YES A REAL ELF IS STANDING IN MY ROOM!), he should be able to tell me. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: devel/bison - NO* vars
Philip M. Gollucci píše v út 07. 04. 2009 v 13:38 -0400: === Checking filesystem state list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) 494798 -r--r--r--1 root wheel2180 Apr 7 07:51 usr/local/lib/charset.alias build of /usr/ports/devel/bison ended at Tue Apr 7 07:51:16 UTC 2009 You have a very broken system. This file means bison used bundled gettext instead of system-wide installation. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Why do we need a film of Lord of the Rings when we have the book? Because watching a cg enhanced Legolas fire a flaming arrow into the heart of a warg is cool? - a...@asdf.com in rec.games.roguelike.angband signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Ports requiring MAKE_JOBS_UNSAFE
David Naylor píše v út 07. 04. 2009 v 20:07 +0200: I've recently added FORCE_MAKE_JOBS to my make.conf and the following ports popped up as failling. This is on a quad core system (running FreeBSD 7.1p2-i386). I tried MAKE_JOBS_NUMBER=3,2,1 in tern and all failed (even with =1). The ports did complete properly with DISABLE_MAKE_JOBS set. The list of ports (so far): converters/libiconv databases/firebird20-client security/libgpg-error Could someone please commit the changes required. Done. P.S. Why did the ports fail with # make clean all MAKE_JOBS_NUMBER=1 FORCE_MAKE_JOBS=yes -j1 and no -j are two different internal logics... -- Pav Lucistnik p...@oook.cz p...@freebsd.org Autumn changed into Winter ... Winter changed into Spring ... Spring changed back into Autumn and Autumn gave Winter and Spring a miss and went straight on into Summer signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: devel/bison - NO* vars
Philip M. Gollucci píše v út 07. 04. 2009 v 19:30 -0400: Pav Lucistnik wrote: Philip M. Gollucci píše v út 07. 04. 2009 v 13:38 -0400: === Checking filesystem state list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) 494798 -r--r--r--1 root wheel 2180 Apr 7 07:51 usr/local/lib/charset.alias build of /usr/ports/devel/bison ended at Tue Apr 7 07:51:16 UTC 2009 You have a very broken system. This file means bison used bundled gettext instead of system-wide installation. So if I have WITHOUT_NLS=yes in /etc/ports.conf devel/bison doesn't work ? And how are we supposed to guess you set this flag? I say the ports system is foobar'ed. Thanks for telling us. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Bento's Law: If It Can Break, It Will Break Bento's Corollary: If It Can Break, Kris Can Send Mail About It signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: LATEST_LINK not in index
Dominic Fandrey píše v pá 03. 04. 2009 v 11:46 +0200: Pav Lucistnik wrote: Dominic Fandrey píše v st 01. 04. 2009 v 00:12 +0200: Upgrades are easy. Look up @comment ORIGIN line in +CONTENTS file of the port being upgraded, then look up this value in second column of INDEX file. I don't see how this is connected to my question. I want people to be able to use LATEST_LINK to identify ports, e.g. apache for www/apache13, apache20 form www/apache20 and so forth. LATEST_LINK is a unique identifier, unfortunately neither recorded in the INDEX nor +CONTENTS. Also, to read it from +CONTENTS (if it were there) I'd have to know, which package is actually meant, which I don't know, because this is the information I want to find out. Maybe you really want people to specify ports by ORIGIN, not by LATEST_LINK ... Actually I want people to be able to do both. Since this is a binary package only tool, I want people to be able to use the same parameters as they'd be able to use with pkg_add -r. I have implemented some guessing by now and it fails very rarely. But it's not the kind of solution I like. You could ls -l Latest/ directory on the ftp server and parse the output, but it's a huge hack.. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Said Helvetica Narrow to Helvetica Bold: Hey, you're just my type. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: LATEST_LINK not in index
Dominic Fandrey píše v st 01. 04. 2009 v 00:12 +0200: Upgrades are easy. Look up @comment ORIGIN line in +CONTENTS file of the port being upgraded, then look up this value in second column of INDEX file. I don't see how this is connected to my question. I want people to be able to use LATEST_LINK to identify ports, e.g. apache for www/apache13, apache20 form www/apache20 and so forth. LATEST_LINK is a unique identifier, unfortunately neither recorded in the INDEX nor +CONTENTS. Also, to read it from +CONTENTS (if it were there) I'd have to know, which package is actually meant, which I don't know, because this is the information I want to find out. Maybe you really want people to specify ports by ORIGIN, not by LATEST_LINK ... -- Pav Lucistnik p...@oook.cz p...@freebsd.org You can't expect to wield supreme executive power just 'cause some watery tart threw a sword at you. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: LATEST_LINK not in index
Dominic Fandrey píše v so 28. 03. 2009 v 19:23 +0100: I'm working on a binary package upgrade tool that gets all required information from the INDEX file downloadable from the package repositories. This means you do not need a local copy of the ports tree to use it. The only information required and missing is the LATEST_LINK. Normally this is easily done by stripping the package name of the version, but some ports define a proprietary LATEST_LINK to avoid conflicts. This leads to the following problem, my program has to do some guessing and in these cases it fails: # pkg_upgrade firefox3 # # pkg_upgrade firefox www/firefox;firefox-2.0.0.20_4,1 www/firefox3;firefox-3.0.7,1 # It either matches none or more than one port. I could build some guessing logic, but the real solution would be to have the LATEST_LINK name in the index file. Is there any chance a LATEST_LINK column will be added if I file a PR? Upgrades are easy. Look up @comment ORIGIN line in +CONTENTS file of the port being upgraded, then look up this value in second column of INDEX file. -- Pav Lucistnik p...@oook.cz p...@freebsd.org It's now using GIFs instead of JPEGs. This is similar to replacing triangular wheels with round ones. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations for everyone
Dmitry Marakasov píše v pá 27. 03. 2009 v 15:48 +0300:
* Pav Lucistnik (p...@freebsd.org) wrote:
second
also improves MAKE_JOBS_* handling, shortening it a bit and exposing
MAKE_JOBS_NUMBER to the ports, so it can be used for other build systems
without having to parse out -j from _MAKE_JOBS (and defaults to 1 if
jobs support is disabled).
This one I cannot accept, because it adds back != call I made a big
effort to avoid. We can't have one != call per port during building
INDEX.
Understood. I still think it'd be nice to expose number of jobs as a
plain number to the ports.
If you figure it out without != call, let me know.
Also, [ x != x${BUILD_FAIL_MESSAGE} ] thing seems to be a bit unsafe,
and inconsistent to IGNORE/BROKEN/... vars, in which we don't use
quotes.
It's consistent with CONFIGURE_FAIL_MESSAGE. Why are you removing the
parenthesis around the ${ECHO_CMD} ${BUILD_FAIL_MESSAGE}, BTW?
Because they are present in do-configure target too - should they be
removed there too?
I just didn't like them :)
Good enough reason for me :)
Are they really needed around single command?
No idea.
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
On real UNIX, /usr/bin/more prints -More-.
signature.asc
Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations for everyone
Dmitry Marakasov píše v pá 27. 03. 2009 v 04:02 +0300:
* Pav Lucistnik (p...@freebsd.org) wrote:
Btw, this change broke build failures. If vendor's make fails,
.build_done.xxx._usr_local is still created in work and $? = 0 as if it
have succeeded.
Can you give me a hard example?
Test port consisting of a sole Makefile attached.
I've made two patches for bsd.port.mk.
First one fixes this issue by adding some false's to do-build,
Ah right, I have stolen do-configure targets and missed the ${FALSE}.
Will fix.
second
also improves MAKE_JOBS_* handling, shortening it a bit and exposing
MAKE_JOBS_NUMBER to the ports, so it can be used for other build systems
without having to parse out -j from _MAKE_JOBS (and defaults to 1 if
jobs support is disabled).
This one I cannot accept, because it adds back != call I made a big
effort to avoid. We can't have one != call per port during building
INDEX.
Also, [ x != x${BUILD_FAIL_MESSAGE} ] thing seems to be a bit unsafe,
and inconsistent to IGNORE/BROKEN/... vars, in which we don't use
quotes.
It's consistent with CONFIGURE_FAIL_MESSAGE. Why are you removing the
parenthesis around the ${ECHO_CMD} ${BUILD_FAIL_MESSAGE}, BTW?
Because they are present in do-configure target too - should they be
removed there too?
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
Pain clots and unformed lice pat this train.
signature.asc
Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations for everyone
Dmitry Marakasov píše v čt 26. 03. 2009 v 20:46 +0300: * Pav Lucistnik (p...@freebsd.org) wrote: Btw, this change broke build failures. If vendor's make fails, .build_done.xxx._usr_local is still created in work and $? = 0 as if it have succeeded. Can you give me a hard example? -- Pav Lucistnik p...@oook.cz p...@freebsd.org Eat when you are hungry, sleep when you are tired. Chase butterflies when you want some fun. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations for everyone
Garrett Cooper píše v čt 26. 03. 2009 v 11:55 -0700: On Thu, Mar 26, 2009 at 10:46 AM, Dmitry Marakasov amd...@amdmi3.ru wrote: * Pav Lucistnik (p...@freebsd.org) wrote: Btw, this change broke build failures. If vendor's make fails, .build_done.xxx._usr_local is still created in work and $? = 0 as if it have succeeded. Another thing that may have failed to have been mentioned earlier: if a python package uses easy_install, there's a potential for corrupted data and missing install registries, so everything that uses easy_install cannot be parallelized at this time. This is a bug in easy_install that I need to provide a quick hack to fix upstream because it's affecting my group at Cisco right now too. Simple fix - don't mark easy_install port with SAFE flag. That's why it's whitelist. -- Pav Lucistnik p...@oook.cz p...@freebsd.org If God is perfect, why did He create discontinuous functions? signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations for everyone
Anonymous píše v st 25. 03. 2009 v 09:26 +0300: Pav Lucistnik p...@freebsd.org writes: If you are FreeBSD port maintainer: I'm not one. Nothing changes for you, if you don't want. If you want to enable the use of multiple cores in your port, add MAKE_JOBS_SAFE=yes to a block somewhere below dependency declarations. If you know your port does not handle -jX well, and want to disable it from using -jX even when user forces this feature, use MAKE_JOBS_UNSAFE=yes. And that's all to it. Not all ports build using make/gmake. Wouldn't it be better to export the number of parallel processes so maintainer can decide whether to use it in his port build system? For example Is this completely discouraged? I suppose you can use internal variable _MAKE_JOBS directly. Why are you stripping -j just to add it back again? -- Pav Lucistnik p...@oook.cz p...@freebsd.org Any Palm app requiring an 90+ page manual has lost its vision. -- words about DateBk4 on Action Names list signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations and packages
per...@pluto.rain.com píše v st 25. 03. 2009 v 00:23 -0700: Pav Lucistnik p...@freebsd.org wrote: Brian Whalen p??e v ?t 24. 03. 2009 v 12:08 -0700: On a related topic, I wonder what the cost would be of acquiring enough hardware so that the probability of actually getting a package with portupgrade -aP would go up substantially ... It's more a question of creating a new delivery platform, because the currently used ftp mirrorring is useless for packages. The whole process of synchronizing from upstream server introduces _days_ of delay into the process, presumably addressable by adding bandwidth, which would need to be included in the cost ... of acquiring enough hardware ... Bandwidth is okay, but rsync is just too slow. Serial synchronization on this amount of data does not work feasibly. and there is no guarantee that you don't catch an upload in progress, which renders whole mirror useless for a time period. I would have thought that judicious use of snapshots could avoid problems with in-progress updates. Yes, but current ftp mirrors does not have enough space to hold several snapshots of same package set. Thus, the need for new platform. -- Pav Lucistnik p...@oook.cz p...@freebsd.org See file. Click file. Get file. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations for everyone
Anonymous píše v st 25. 03. 2009 v 12:51 +0300: FYI, that example went to ports/133054. Cool. Just a side note -- boost is having a major overhaul, so you might want to coordinate with the folks who currently do the work, too. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Like 'Do Notte Buye Betamacks.' That was a prediction for 1972. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations for everyone
Dmitry Marakasov píše v st 25. 03. 2009 v 19:36 +0300: * Pav Lucistnik (p...@freebsd.org) wrote: Great, that was just about time. My question is whenther that would be enabled on pointyhat. I fear that error logs may become far less readable with output from multiple commands mixed together. pointyhat observes the same rules and conditions as the end user, for obvious reasons. So ports marked 'safe' will be parallelized, others will not. -- Pav Lucistnik p...@oook.cz p...@freebsd.org It's the classic Microsoft security-bulletin formula: The vulnerability is important (never dangerous); you have nothing to fear and no reason to regret trusting us; we have no intention of apologizing for it or even explaining it adequately; now go get your patch, shut up, and be grateful nothing bad has happened. -- The Register signature.asc Description: Toto je digitálně podepsaná část zprávy
HEADS UP multi processor compilations for everyone
Two days ago, I have checked in probably most requested feature of last few years. Ports framework now systematically supports building ports on multiple processing cores. It is achieved by passing -jX flag to make(1) running on vendor code. Of course not all ports handle this well, experimental run on pointyhat with this flag globally enabled turned up shy of 400 failures. Because of that, the feature was designed as a whitelist. Individual ports need to be enabled, and indeed, fellow developers took on and already started adding required declarations to popular ports like Firefox and others. If you are FreeBSD ports user: You don't need to do anything to enable the new feature. Whitelisted ports will automatically make use of all processors available in your computer. If you want, for some reasons, to disable this feature, put DISABLE_MAKE_JOBS=yes to your /etc/make.conf. By default, the level of parallelization will be equal to a number of processing cores in your machine. If you want to override this number, use for example MAKE_JOBS_NUMBER=6, again in /etc/make.conf. And if you are extra brave, or you want to check out all the yet unmarked ports, if they will build, you can define FORCE_MAKE_JOBS=yes in /etc/make.conf. If you are FreeBSD port maintainer: Nothing changes for you, if you don't want. If you want to enable the use of multiple cores in your port, add MAKE_JOBS_SAFE=yes to a block somewhere below dependency declarations. If you know your port does not handle -jX well, and want to disable it from using -jX even when user forces this feature, use MAKE_JOBS_UNSAFE=yes. And that's all to it. -- Pav Lucistnik p...@oook.cz p...@freebsd.org What do we know about love? Love is like a pear. Pear is sweet and have a specific shape. Try to exactly define the shape of a pear. -- Marigold: 50 Years Of Poetry signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations for everyone
Niclas Zeising píše v út 24. 03. 2009 v 15:28 +0100: Not to nitpick or be an annoyance, but you might want to document this in ports(7) or make.conf(5) (or both) so it doesn't get lost in the mail-lists or if people are not reading ports@ I will document it soon, thinking The Handbook would be best place. -- Pav Lucistnik p...@oook.cz p...@freebsd.org East or west, ~ is best. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations for everyone
Coleman Kane píše v út 24. 03. 2009 v 10:58 -0400: On Tue, 2009-03-24 at 15:54 +0100, Pav Lucistnik wrote: Niclas Zeising píše v út 24. 03. 2009 v 15:28 +0100: Not to nitpick or be an annoyance, but you might want to document this in ports(7) or make.conf(5) (or both) so it doesn't get lost in the mail-lists or if people are not reading ports@ I will document it soon, thinking The Handbook would be best place. Definitely add it to UPDATING too. This will allow people who typically do something like make configure make -j3 to now know that they This would break very fast -- it's passing -j3 to port Makefile instead of vendor Makefile. don't have to. It will also allow others to know why ports compilation on their multi-core boxes suddenly uses a lot more CPU time. Same CPU time, less wall time, more CPU utilization :) -- Pav Lucistnik p...@oook.cz p...@freebsd.org If God didn't mean for us to juggle, tennis balls wouldn't come three to a can. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations for everyone
Coleman Kane píše v út 24. 03. 2009 v 12:28 -0400: On Tue, 2009-03-24 at 16:19 +0100, Pav Lucistnik wrote: Coleman Kane píše v út 24. 03. 2009 v 10:58 -0400: On Tue, 2009-03-24 at 15:54 +0100, Pav Lucistnik wrote: Niclas Zeising píše v út 24. 03. 2009 v 15:28 +0100: Not to nitpick or be an annoyance, but you might want to document this in ports(7) or make.conf(5) (or both) so it doesn't get lost in the mail-lists or if people are not reading ports@ I will document it soon, thinking The Handbook would be best place. Definitely add it to UPDATING too. This will allow people who typically do something like make configure make -j3 to now know that they This would break very fast -- it's passing -j3 to port Makefile instead of vendor Makefile. This has worked fine for me for countless years, except where the vendor's Makefiles were not parallel-safe. This has been my trick to get larger things (like mysql or xorg-server) to make in parallel. It *did* work. If this has changed, then it definitely warrants mention in UPDATING. Then it must have worked all these years by pure chance :) -- Pav Lucistnik p...@oook.cz p...@freebsd.org 94 outdated ports on the box, 94 outdated ports. Portupgrade one, an hour 'til done, 82 outdated ports on the box. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations for everyone
Christian Weisgerber píše v út 24. 03. 2009 v 18:09 +: If you are FreeBSD port maintainer: Nothing changes for you, if you don't want. If you want to enable the use of multiple cores in your port, add MAKE_JOBS_SAFE=yes to a block somewhere below dependency declarations. What is the goal here? Should all ports that can be safely built in parallel eventually have MAKE_JOBS_SAFE=yes? Ideally yes. Or should we not bother with ports where the gain is likely to be minimal? That would be sensible. -- Pav Lucistnik p...@oook.cz p...@freebsd.org As to floating eyes, let them float :). - r.g.r.a signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP multi processor compilations and packages
Brian Whalen píše v út 24. 03. 2009 v 12:08 -0700: Pav Lucistnik wrote: Two days ago, I have checked in probably most requested feature of last few years. Ports framework now systematically supports building ports on multiple processing cores. It is achieved by passing -jX flag to make(1) running on vendor code. Of course not all ports handle this well, experimental run on pointyhat with this flag globally enabled turned up shy of 400 failures. Because of that, the feature was designed as a whitelist. Individual ports need to be enabled, and indeed, fellow developers took on and already started adding required declarations to popular ports like Firefox and others. On a related topic, I wonder what the cost would be of acquiring enough hardware so that the probability of actually getting a package with portupgrade -aP would go up substantially. I imagine the time required for the build servers to build packages with the above mod would go down substantially. It's more a question of creating a new delivery platform, because the currently used ftp mirrorring is useless for packages. The whole process of synchronizing from upstream server introduces _days_ of delay into the process, and there is no guarantee that you don't catch an upload in progress, which renders whole mirror useless for a time period. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Do not meddle in the fashions of wizards, for they are seasonal and quick to fall out of style! signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Gphoto2 fails to build on -current
Derek Tattersall píše v so 07. 03. 2009 v 10:12 -0500: Error message from make: LIBUSB_LIBS=-L/usr/lib -lusb20 LIBUSB_CFLAGS=-I/usr/include * Fatal: libgphoto2 port access library by default requires libusb = 0.1.5 to build. config.log is attached. Do you have a fix? I don't have a -current machine, so I can't test myself. -- Pav Lucistnik p...@oook.cz p...@freebsd.org It's ten o'clock; do you know where your processes are? signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Gphoto2 fails to build on -current
Joe Marcus Clarke píše v so 07. 03. 2009 v 15:11 -0500: On Sat, 2009-03-07 at 20:30 +0100, Pav Lucistnik wrote: Derek Tattersall píše v so 07. 03. 2009 v 10:12 -0500: Error message from make: LIBUSB_LIBS=-L/usr/lib -lusb20 LIBUSB_CFLAGS=-I/usr/include * Fatal: libgphoto2 port access library by default requires libusb = 0.1.5 to build. config.log is attached. Do you have a fix? I don't have a -current machine, so I can't test myself. I do. Change the include path to be /usr/include/dev/usb. Builds just fine for me. Done, thanks! -- Pav Lucistnik p...@oook.cz p...@freebsd.org Go back to bed America, your government is in control again. Here's American Gladiators. Watch this, shut up. Here's 56 channels of it. Watch these pituitary retards bang their fuckin skulls together and congratulate you on living in the land of freedom. -- Bill Hicks signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: astro/boinc-einsteinathome outdated
Peter Jeremy píše v pá 06. 03. 2009 v 06:00 +1100: On 2008-Aug-17 21:19:42 +0200, Pav Lucistnik p...@freebsd.org wrote: Peter Jeremy pí?e v po 18. 08. 2008 v 05:11 +1000: I notice that einst...@home have stopped generating S5R3 workunits and a new client is needed to handle the new S5R4 workunits. Do you have any plans to upgrade the port? I will update the port but unfortunately FreeBSD app for S5R4 is not yet released. OK. It's six months later and there's still no sign of any update. If we're not going to get an update, the port might as well be removed. :( Can you at least mark it broken until (if?) it's updated? I have marked the port IGNORED. -- Pav Lucistnik p...@oook.cz p...@freebsd.org On real UNIX, /usr/bin/more prints -More-. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: FreeBSD Port: boinc-client-6.4.5_1
Maxim Maslennikov píše v ne 18. 01. 2009 v 20:46 +0300: I have problem with starting WCG applications they immediately stop after start. Can you be more specific? -- Pav Lucistnik p...@oook.cz p...@freebsd.org And the sign said long haired, freaky people need not apply. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Dependent ports get does not exist errors
Warren Block píše v po 12. 01. 2009 v 12:36 -0700: cd /usr/ports/graphics/gimp make install [...] === Compressing manual pages for bash-3.2.48_1 === Registering installation for bash-3.2.48_1 === Returning to build of rarian-0.8.1 Error: file bash does not exist *** Error code 1 Can you verify you have /usr/ports/Mk/bsd.port.mk revision 1.606? -- Pav Lucistnik p...@oook.cz p...@freebsd.org With sufficient thrust, pigs fly just fine. -- RFC 1925 signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Dependent ports get does not exist errors
Warren Block píše v po 12. 01. 2009 v 13:51 -0700: On Mon, 12 Jan 2009, Pav Lucistnik wrote: Warren Block p??e v po 12. 01. 2009 v 12:36 -0700: cd /usr/ports/graphics/gimp make install [...] === Compressing manual pages for bash-3.2.48_1 === Registering installation for bash-3.2.48_1 === Returning to build of rarian-0.8.1 Error: file bash does not exist *** Error code 1 Can you verify you have /usr/ports/Mk/bsd.port.mk revision 1.606? Yes. Update to 1.607 should help. If not, contact me. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Alignment: Neutral Greedy signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
Alexander Churanov píše v ne 11. 01. 2009 v 21:38 +0300: 2009/1/11 Pav Lucistnik p...@freebsd.org That's certainly a possibility -- but can two boost versions coexist in a single system? That's a real problem. To my mind there are no problems for shared libraries, but for header files the suggested solution would require placing headers under /usr/local/include/boost-134/boost and modify all ports' build processes to include /usr/local/include/boost-134 in a search path. I'll carry out this experiment. Let's see if there's an easy way to make all the ports respect it, say, if it would mean just modifying pkg-config output. If it's non-trivial, we'll have to go with two conflicting ports. I want to run an experimental package build with new boost, to see how many ports will still need the old one. Is the patch on rapidshare (ports/129241) still valid? Or is there a new patch you want to send me? -- Pav Lucistnik p...@oook.cz p...@freebsd.org One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: HEADS UP: GNOME 2.24.2 is now available for FreeBSD
Lowell Gilbert píše v so 10. 01. 2009 v 11:54 -0500: Is the Gnome update what caused this? Generating INDEX.tmp - please wait../usr/ports/Mk/bsd.gnome.mk, line 784: Inconsistent operator for post-install make: fatal errors encountered -- cannot continue === editors/xemacs failed *** Error code 1 1 error Fixed! Thanks for reporting. -- Pav Lucistnik p...@oook.cz p...@freebsd.org Go back to bed America, your government is in control again. Here's American Gladiators. Watch this, shut up. Here's 56 channels of it. Watch these pituitary retards bang their fuckin skulls together and congratulate you on living in the land of freedom. -- Bill Hicks signature.asc Description: Toto je digitálně podepsaná část zprávy
