Re: binary package maintenance tool
Alexey V. Degtyarev wrote: >>> The port sysutils/bsdadminscripts has just been updated to >>> version 6.0, which features pkg_upgrade, a binary only >>> package maintenance tool. >>> It makes no use of the ports tree, so unlike other build >>> oriented tools, you do not need a copy of the ports tree >>> to keep your packages up to date. >>> It only requires an INDEX file from pointyhead or your >>> personal Tinderbox. >> Great! T've done some tests at my home machine and I really >> like this tool. I was deaming for it for a long time. And >> it works much faster than "portupgrade -PP". > > pkg_upgrade works very good for me too, except one thing: > > Assume package pkg-1.1 installed on the system and is going to upgrade. > The pkg-1.2 version of package requires a little bit more packages that > required by pkg-1.1: + a new one package newpkg-1.1 for example. After > pkg_upgrade upgrades package `pkg', there is no newpkg-1.1 installed on > the system and there is a error occured while updating. Here is the > illustration with some names screened: > > $ export PACKAGESITE=http://some.path.to/packages/ > $ pkg_upgrade -na > Update to (nice/pkg) > $ pkg_upgrade -a > /usr/ports/packages/All/pkg-1.2.tbz100% of 3537 B 5464 kBps > ===> Update to > (nice/pkg) > pkg_add: could not find package newpkg-1.1 (proceeding anyway) > pkg_add: can't open dependency file '/var/db/pkg/newpkg-1.1/+REQUIRED_BY'! > dependency registration is incomplete > => Update to > (nice/pkg) succeeded > $ pkg_info -Ex newpkg > $ pkg_info -Ex pkg > pkg-1.2 > > I think that pkg_upgrade should respect a new package's dependency list > and pre-fetch all the new dependencies before pkg_add. > > This means that the missing dependency is not listed in the index and hence not available for download or the index file provided by pointyhead is simply broken. Because pkg_upgrade does in deed download all dependencies (that are also listed in the index) and does not install a single package until all required packages have been downloaded. At least it did that in many, many tests I have performed. ___ 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: binary package maintenance tool
Alexander Churanov wrote: > 2009/5/4 Alexey V. Degtyarev : >> I think that pkg_upgrade should respect a new package's dependency list >> and pre-fetch all the new dependencies before pkg_add. > It does, if the dependencies are listed in the INDEX. > My $0.02: > > And calculate their size, and (in interactive mode) provide and option > for a user to cancel download :-) > > Alexander Churanov > There is no interactive mode. I plan to implement one, but this will be to perform roll-backs or resume interrupted upgrades and not be part of normal operation. The upgrading of packages is and will remain non-interactive. ___ 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"
pkg_add errors
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. A simple check whether the package has been fully installed using 'pkg_info -g' is not a solution, because many packages (e.g. scribus or gstreamer-plugins-bad) come with faulty PLISTs, so 'pkg_info -g' is not a reliable way to check for a successful install. Maintainers have successfully ignored my bitching about broken PLISTs for years, so I cannot expect this to be solved upstream. The problem I face is that there are cases when a package installs incompletely. I can detect this and attempt a reinstall or even a redownload and reinstall. But what if the install is still broken? Terminate pkg_upgrade with an error? That does not look like an option to me, because it would quit whenever a package with a broken PLIST is encountered and rendered almost useless by this. At least for as long as committers accept ports with broken PLISTs. What I need is a solution that is right most of the time, does not cause pkg_upgrade to stop and can be easily redeemed afterwards, if it hasn't been right after all. I have found such a solution for the conflict handling (existing packages take preference, so e.g. boost-python will be accepted as a dependency instead of boost, or a2ps-a4 instead of a2ps-letter). If the default solution was wrong the packages can easily be exchanged using -o or -C. I need something similar for the incomplete package problem. Should pkg_upgrade create a summary of apparently broken packages that have been installed? Should it bail out (and break with every package that has a broken plist)? Should it perform library checks and try to auto fix them? My preference would be to rely on 'pkg_info -g', but that would require all committers to run extensive checks before committing changes to the ports tree. Miwi has always done this and more than once revealed PLIST problems of my ports to me. But I wonder whether it is really sensible to ask committers to test everything on a Tinderbox (preferably on several platforms) before committing changes to the ports tree. ___ 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: pkg_add errors
Pav Lucistnik wrote: > 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) > Well, that's possible, but why would cups-base perform such an evil deed? It's a very soothing suggestion, though. At least as far as pkg_upgrade is concerned. ___ 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: pkg_add errors
Dominic Fandrey wrote: > Pav Lucistnik wrote: >> 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) >> > > Well, that's possible, but why would cups-base perform such an evil > deed? Stupid me, I just read UPDATING. That explains everything. But that puts the question forward how to deal with this. People using pkg_upgrade do not require a ports tree and hence do not have UPDATING. > It's a very soothing suggestion, though. At least as far as pkg_upgrade > is concerned. ___ 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: pkg_add errors
Boris Samorodov wrote: > Hello Dominic, List, > > Thanks for your work, much appreciated. You're welcome. > Dominic Fandrey writes: > >> I need something similar for the incomplete package problem. >> Should pkg_upgrade create a summary of apparently broken packages >> that have been installed? > > I would go with this option since one can use not only official > packages but home made ones (and without much testing). I suppose. So this goes into the list of feature requests. >> Should it bail out (and break with every >> package that has a broken plist)? > > That imho would be a little bit draconian. Pav Lucistnik suggested cups-base was to blame. Well, I just read /usr/ports/UPDATING and this is definitely one of the things that cannot be dealt with automatically. > BTW, current behaviour of "pkg_upgrade -F" to stop at the first package > that can't be downloaded is the same. Can this behaviour be changed > to proceeding but printing out the list of not downloaded packages > at the end? Or at least can you create an option for such behaviour? > >> Should it perform library checks > > That may be done via command line option. > >> and try to auto fix them? > > That task seems to be very hard to achieve. I've actually put some thought on this. It's been on the list of planned features for a long time. I'm pretty certain, I can deal with a large majority of library problems without human interaction. What irks me about it is that the sequence of actions would be broken by this. Features like fetching in advance and performing updates later would break. And all these problems could be avoided if library changes always resulted in a version bump of all dependencies. A path that has been followed more often recently, but still cannot be relied on. > >> My preference would be to rely on 'pkg_info -g', but that would >> require all committers to run extensive checks before committing >> changes to the ports tree. Miwi has always done this and more than >> once revealed PLIST problems of my ports to me. But I wonder whether >> it is really sensible to ask committers to test everything on a >> Tinderbox (preferably on several platforms) before committing >> changes to the ports tree. > > Hm, ports with broken PLISTS are, well, broken. And should be fixed > or marked BROKEN. I was sure that the FreeBSD packaging cluster does > not produce packages with broken plists (i.e. the package is not > created). Is that wrong? I think so. After all the Pointyhead packages are built from the same ports tree as the one everyone else uses. And that has a couple of persistently broken plists, not many, but some. > > > WBR ___ 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: pkg_add errors
Boris Samorodov wrote: > BTW, current behaviour of "pkg_upgrade -F" to stop at the first package > that can't be downloaded is the same. Can this behaviour be changed > to proceeding but printing out the list of not downloaded packages > at the end? Or at least can you create an option for such behaviour? It will happen. ___ 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: pkg_libchk: a missing library is not detected
Sorry for the late reply, this was auto-sorted into the ports@ mails and drowned there. Boris Samorodov wrote: > Hi! > > > Seems to me like a bug at pkg_libchk: > - > % eog > /libexec/ld-elf.so.1: Shared object "libgnome-desktop-2.so.7" not found, > required by "eog" > % ldd `which eog` | grep found > libgnome-desktop-2.so.7 => not found (0x0) > % pkg_libchk -vc eog\* This just means that it's an indirect dependency, meaning that updating eog wouldn't do any good, but a dependency needs to be updated. pkg_libchk only displays direct library missings, so the result is not everything affected, but instead only everything that needs fixing. > % pkg_info -xI bsdadmin > bsdadminscripts-6.1.1 A collection of administration scripts > % > - > > BTW, the library libgnome-desktop-2.so.7 was replaced by a new one > libgnome-desktop-2.so.11 while updating: > - > 1244027909 - Wed Jun 3 15:18:29 MSD 2009 - DONE: Update > to (x11/gnome-desktop) > - > > As I understand pkg_upgrade does not preserve old libraries at > /usr/local/lib/compat? That's true. I consider this common approach a security risk. I suggest running pkg_libchk -a and reinstalling the packages listed by it to fix that. Mostly dependent ports get version bumped if they depend on a library that was changed. Unfortunately this doesn't always happen. To ensure that you get the newest packages wipe /usr/ports/packages/All. > > > WBR ___ 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: pkg_libchk: a missing library is not detected
Mel Flynn wrote: > On Monday 15 June 2009 02:55:09 Dominic Fandrey wrote: >> Sorry for the late reply, this was auto-sorted into the ports@ mails >> and drowned there. >> >> Boris Samorodov wrote: > >>> As I understand pkg_upgrade does not preserve old libraries at >>> /usr/local/lib/compat? >> That's true. I consider this common approach a security risk. > > It is a service interruption to delete libraries that are still used and this > can also lead to security problems. > However, pkg_upgrade cannot ever hope to fix this problem, because the > buildservers do not unconditionally rebuild packages that mention the > upgraded > port in LIB_DEPENDS, therefore it is better to leave these shared libraries > around. To me something not working seems to be less of a security problem than linking to a vulnerable library. >> To ensure that you get the newest packages wipe >> /usr/ports/packages/All. > > Erm, the download time associated with that approach doesn't really speed up > things, nor does it guarantee that you will have working binaries if the port > maintainer forgot to version bump a port. Well, you don't ever need them again after having them installed once, so I don't see the problem. And at least from pointyhead I've never head broken linking, even when the package was not version bumped, so I think there's some kind of human intervention, or I was lucky. Proper version bumping solves both problems, though and it is rarely forgotten lately. So the issue is much smaller, now than it would have been a couple of years ago. Also I do not see a way for my tool to handle this in any acceptable way. If you've got an idea, go ahead and tell me. I actually want to deal with as many problems as possible without user intervention. It's about making life easier, after all. ___ 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: x11-drivers/input-wacom on FreeBSD 8
Peter Jeremy wrote: > Hi, > > Based on the "BROKEN" message and the kernel module, I presume that > this port has not been adapted for USB2. Do you have any plans to > upgrade this port to work with FreeBSD 8.x? > Bartosh told me he's working on it. But there is nothing like a date for this happening. Additionally the driver also cause problems with Xorg 7.4 for many people (even on RELENG_7), so there's a lot of work to be done on it. I suppose it would be nice if someone comfortable with USB stuff took a look at this. Bartosz told me he hasn't really had a look into the USB2 stuff, yet. He's working on RELENG_7 and the Xorg 7.4 stuff first it seems. ___ 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: pkg_libchk: a missing library is not detected
Mel Flynn wrote: > On Tuesday 16 June 2009 07:34:47 Dominic Fandrey wrote: >> Mel Flynn wrote: >>> On Monday 15 June 2009 02:55:09 Dominic Fandrey wrote: >>>> Sorry for the late reply, this was auto-sorted into the ports@ mails >>>> and drowned there. >>>> >>>> Boris Samorodov wrote: >>>>> As I understand pkg_upgrade does not preserve old libraries at >>>>> /usr/local/lib/compat? >>>> That's true. I consider this common approach a security risk. >>> It is a service interruption to delete libraries that are still used and >>> this can also lead to security problems. >>> However, pkg_upgrade cannot ever hope to fix this problem, because the >>> buildservers do not unconditionally rebuild packages that mention the >>> upgraded port in LIB_DEPENDS, therefore it is better to leave these >>> shared libraries around. >> To me something not working seems to be less of a security problem than >> linking to a vulnerable library. > > Depends what is not working. If it's the monitoring software, do you still > agree? Yes I do. Virus scanners and personal firewalls have proven to be security hazards in the past. Any kind of monitoring is as likely to be a gateway to be exploited, especially considering that monitoring software normally has a lot of privileges. > Also, a library with a vulnerability does not always constitute an > exploitable > library for the way a running vital application uses it. Do you have a convincing example? None comes to my mind. > Either way, I don't > think you should unconditionally interrupt service, because you think yours > is > the right way. It should be optional and because of your own conviction, you > could choose to make the default "security over service". Provide an example where it make sense to keep a vulnerable library around and I will add the option to preserve libraries. >>>> To ensure that you get the newest packages wipe >>>> /usr/ports/packages/All. >>> Erm, the download time associated with that approach doesn't really speed >>> up things, nor does it guarantee that you will have working binaries if >>> the port maintainer forgot to version bump a port. >> Well, you don't ever need them again after having them installed once, so I >> don't see the problem. > > True I guess for most cases, but if that's true, then why remove them if > you're not ever going to download them twice? Because you want to download them again if they have been rebuilt without a version change. Something that actually seems to be happening on pointyhead. > >> And at least from pointyhead I've never head >> broken linking, even when the package was not version bumped, so I think >> there's some kind of human intervention, or I was lucky. > > Luck. The app linking to the old library will have a dependency on the old > version. pkg_add will find the origin, issue a warning about "app-1.0 needing > lib-0.1 but lib-0.2 is installed" and proceed. app will not start, because of > the missing library. I've never had this case. I've got the impression that pointyhead rebuilds all dependencies. > >> Proper version bumping solves both problems, though and it is rarely >> forgotten lately. So the issue is much smaller, now than it would have been >> a couple of years ago. Also I do not see a way for my tool to handle this >> in any acceptable way. If you've got an idea, go ahead and tell me. I >> actually want to deal with as many problems as possible without user >> intervention. It's about making life easier, after all. > > You can't without the buildservers providing hashes for the packages (to > detect if a package has been repacked) or in less good case checking lastmod > time and size plus the buildservers rebuilding dependents. We've got a PR for this kind of thing around (actually we only request hashes for the INDEX, one step at a time), but I doubt someone is interested in providing this feature. Maybe one day I'll create patches for pointyhead myself, but not before I have done everything that I want to do with pkg_upgrade. There's still so much to be done, it does not yet seem worthwile to invest time into getting to know some else's code, patching it and complaining long enough to get the patches committed. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Possibly unbuildable ports reminder
Bill Fenner wrote: > Dear porters, > > This is just a reminder to please periodically check the list of > unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . > A list by MAINTAINER is > > http://people.freebsd.org/~fenner/errorlogs/ > > so you can easily check the status of ports that you maintain. In > addition, the list of ports with no MAINTAINER with build problems is > > http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html > > Since no one is responsible for these ports, the problem won't get > fixed unless someone on this list takes the initiative. > > Thanks for your help! This is about my ports: http://people.freebsd.org/~fenner/errorlogs/kamik...@bsdforen.de-date.html error no. 3: outdated, the port has long since been moved and updated error no. 2: cannot reproduce, I have a dim memory of an error like this, I think it got fixed a long time ago error no. 1: there's no error message in the log, it builds fine on my 7.2-stable/amd64 system ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg_libchk: a missing library is not detected
Boris Samorodov wrote: > Dominic Fandrey writes: > >>> Luck. The app linking to the old library will have a dependency on the old >>> version. pkg_add will find the origin, issue a warning about "app-1.0 >>> needing >>> lib-0.1 but lib-0.2 is installed" and proceed. app will not start, because >>> of >>> the missing library. >> I've never had this case. I've got the impression that pointyhead rebuilds >> all >> dependencies. > > Let me remind you the case with my original question: > 1. Graphics/eog was broken (as you said) by indirect dependency. > 2. Pkg_libchk didn't catch the case. > > Did it happen by design? > > > WBR Are you certain that this was a direct dependency? Maybe just a dependency of graphics/eog was broken. ___ 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"
devel/avr-gcc does not build
On my amd64 notebook (core2duo) devel/avr-gcc does not build: echo timestamp > stmp-fixproto gmake[2]: Leaving directory `/usr/obj/mobileKamikaze.norad/x86_64/usr/ports/devel/avr-gcc/work/build/gcc' Checking multilib configuration for libgcc... mkdir avr mkdir avr/libgcc Configuring in avr/libgcc configure: creating cache ./config.cache checking for --enable-version-specific-runtime-libs... no checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for gawk... gawk checking build system type... x86_64-portbld-freebsd7.2 checking host system type... avr-unknown-none checking for avr-ar... /usr/local/avr/bin/ar checking for avr-lipo... avr-lipo checking for avr-nm... /usr/obj/mobileKamikaze.norad/x86_64/usr/ports/devel/avr-gcc/work/build/./gcc/nm checking for avr-ranlib... /usr/local/avr/bin/ranlib checking for avr-strip... /usr/local/avr/bin/strip checking whether ln -s works... yes checking for avr-gcc... /usr/obj/mobileKamikaze.norad/x86_64/usr/ports/devel/avr-gcc/work/build/./gcc/xgcc -B/usr/obj/mobileKamikaze.norad/x86_64/usr/ports/devel/avr-gcc/work/build/./gcc/ -B/usr/local/avr/bin/ -B/usr/local/avr/lib/ -isystem /usr/local/avr/include -isystem /usr/local/avr/sys-include checking for suffix of object files... configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details. gmake[1]: *** [configure-target-libgcc] Error 1 gmake[1]: Leaving directory `/usr/obj/mobileKamikaze.norad/x86_64/usr/ports/devel/avr-gcc/work/build' gmake: *** [all] Error 2 ===> Compilation failed unexpectedly. You have chosen to use multiple make jobs (parallelization) for all ports. This port was not tested for this setting. Please remove FORCE_MAKE_JOBS and retry the build before reporting the failure to the maintainer. *** Error code 1 Stop in /usr/ports/devel/avr-gcc. I already tried without FORCE_MAKE_JOBS, this is not the cause. ___ 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: devel/avr-gcc does not build
Joerg Wunsch wrote: > As Dominic Fandrey wrote: > >> checking for suffix of object files... configure: error: cannot compute >> suffix of object files: cannot compile >> See `config.log' for more details. > > Did you look into config.log to figure out the reason? > > As I haven't got a notification from the QA Tindy, I don't think this > is going to be a general problem on amd64. (The QAT was *very* quick > in telling me I forgot to mention a couple of files in pkg-plist.) > Well, I did, but I didn't find anything that might be the reason for this. I can send it to you, if you think that might be of help. Regards ___ 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"
MOVED and UPDATING delivered with packages
The portmgr team has enhanced the pointyhead scripts to publish MOVED and UPDATING files together with the INDEX files that kports and pkg_upgrade use for binary package updating. http://www.freebsd.org/cgi/query-pr.cgi?pr=135024 Many thanks to the portmgr team! I hope I will find the time to update pkg_upgrade before the 8.0 release. ___ 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: MOVED and UPDATING delivered with packages
Marcin Wisnicki wrote: > On Tue, 11 Aug 2009 10:52:31 +0200, Dominic Fandrey wrote: > >> The portmgr team has enhanced the pointyhead scripts to publish MOVED >> and UPDATING files together with the INDEX files that kports and >> pkg_upgrade use for binary package updating. >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=135024 >> > > Very much appreciated but how about also providing them in bzip2 > compressed form ? > Especially INDEX, since it's is so large and compresses > so good: There is a different PR for this (by the author of kports): http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/131440 ___ 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"
CFT - ioquake3 1.36 port
I intend to take the games/ioquake3 port over and need some testers. This is the patch to the port (apply from /usr): http://www.home.hs-karlsruhe.de/~fado0011/patch-ports-games-ioquake3.diff This is a shar that creates a slave port installing SVN-snapshots of ioquake3 (extract from /usr): http://www.home.hs-karlsruhe.de/~fado0011/shar-ports-games-ioquake3-devel.sh The devel and release ports can both be installed side by side. The bugzilla entry at the ioq3 project is pretty detailed about what has been patched: http://bugzilla.icculus.org/show_bug.cgi?id=4271 Regards ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: CFT - ioquake3 1.36 port
Dominic Fandrey wrote: > I intend to take the games/ioquake3 port over and need some testers. > > This is the patch to the port (apply from /usr): > http://www.home.hs-karlsruhe.de/~fado0011/patch-ports-games-ioquake3.diff > > This is a shar that creates a slave port installing SVN-snapshots of > ioquake3 (extract from /usr): > http://www.home.hs-karlsruhe.de/~fado0011/shar-ports-games-ioquake3-devel.sh I just updated those to address some i386 problems. ___ 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"
bsd.python.mk broken
If one uses the OPTIONS framework like in graphics/opencv to trigger python support, bsd.python.mk breaks. Here is why: USE_PYTHON has to be set before including bsd.port.pre.mk Unfortunately it can only be set after bsd.port.pre.mk, because WITH_PYTHON wouldn't be set before. For this the _POSTMKINCLUDED variable is responsible. The following is from the beginning of bsd.python.mk:# .if !defined(_POSTMKINCLUDED) && !defined(Python_Pre_Include) It looks similar for bsd.perl.mk, so maybe the problem exists there as well. bsd.php.mk or bsd.java.mk are different: .if !defined(Java_Include) I suggest removing the !defined(_POSTMKINCLUDED) from both bsd.python.mk and bsd.perl.mk. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
php5-gd PNG support broken
I've got the following problem with php5-gd: Warning: imagecreatefrompng() [function.imagecreatefrompng]: gd-png: fatal libpng error: [00][00][00][00]: unknown critical chunk in /usr/home/kamikaze/devel/workspace/realmsofsorrow/nightmare/core/nmTemplate.class.php on line 385 Warning: imagecreatefrompng() [function.imagecreatefrompng]: gd-png error: setjmp returns error condition in /usr/home/kamikaze/devel/workspace/realmsofsorrow/nightmare/core/nmTemplate.class.php on line 385 Warning: imagecreatefrompng() [function.imagecreatefrompng]: './templates/neo/layout/header_stretch.png' is not a valid PNG file in /usr/home/kamikaze/devel/workspace/realmsofsorrow/nightmare/core/nmTemplate.class.php on line 385 I get this message for all PNGs. I checked the files with Firefox, and Gimp, they are all whole. They are also displayed by the e17 file browser, which relies on libpng. My system: FreeBSD mobileKamikaze.norad 7.2-STABLE FreeBSD 7.2-STABLE #0: Fri Jul 3 10:26:33 CEST 2009 r...@mobilekamikaze.norad:/usr/obj/HP6510b/amd64/usr/src/sys/HP6510b amd64 libpng: png-1.2.40 php5-gd: php5-gd-5.2.11_1 Regards ___ 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"
in search for sasquatch/committer
Does any one dare commit ports/138695? I want to update both games/ioquake3 and games/ioquake3-devel. But it's going to be a great hazzle without getting this PR committed first. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
sysutils/hal does not build on RELENG_8/amd64
sysutils/hal does not build on my system. I'm trying to rebuild after upgrading from RELENG_7. # uname -a FreeBSD mobileKamikaze.norad 8.0-RC1 FreeBSD 8.0-RC1 #0: Thu Oct 22 18:39:21 CEST 2009 r...@mobilekamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6510b-8 amd64 cc -DHAVE_CONFIG_H -I. -I../../.. -DPACKAGE_SYSCONF_DIR=\""/usr/local/etc"\" -DPACKAGE_DATA_DIR=\""/usr/local/share"\" -DPACKAGE_BIN_DIR=\""/usr/local/bin"\" -DPACKAGE_LOCALE_DIR=\""/usr/local/share/locale"\" -DPACKAGE_LOCALSTATEDIR=\""/var"\" -I../../.. -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -I/usr/local/include -DHAVE_CK_0_3 -O2 -pipe -march=nocona -fno-strict-aliasing -Wall -Wchar-subscripts -Wmissing-declarations -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -MT probe-hiddev.o -MD -MP -MF .deps/probe-hiddev.Tpo -c -o probe-hiddev.o probe-hiddev.c probe-hiddev.c: In function 'main': probe-hiddev.c:81: error: 'USB_GET_REPORT_ID' undeclared (first use in this function) probe-hiddev.c:81: error: (Each undeclared identifier is reported only once probe-hiddev.c:81: error: for each function it appears in.) gmake[5]: *** [probe-hiddev.o] Error 1 gmake[5]: Leaving directory `/usr/obj/mobileKamikaze.norad/amd64/usr/ports/sysutils/hal/work/hal-0.5.11/hald/freebsd/probing' gmake[4]: *** [all-recursive] Error 1 gmake[4]: Leaving directory `/usr/obj/mobileKamikaze.norad/amd64/usr/ports/sysutils/hal/work/hal-0.5.11/hald/freebsd' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/obj/mobileKamikaze.norad/amd64/usr/ports/sysutils/hal/work/hal-0.5.11/hald' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/obj/mobileKamikaze.norad/amd64/usr/ports/sysutils/hal/work/hal-0.5.11/hald' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/obj/mobileKamikaze.norad/amd64/usr/ports/sysutils/hal/work/hal-0.5.11' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/sysutils/hal. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/hal does not build on RELENG_8/amd64
Rene Ladan wrote: > 2009/10/23 Dominic Fandrey : >> sysutils/hal does not build on my system. I'm trying to >> rebuild after upgrading from RELENG_7. >> >> ... > > It builds on my 8.0RC-1/amd64 box, did you remove the devel/libusb > port before trying to upgrade? FreeBSD 8+ > comes with libusb built in. No, I didn't check UPDATING that far in the past. Thanks a lot that solved my problem! ___ 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: [patch] Make git dependencies optional.
Stef Walter wrote: > This patch ... Just for the future, patches should be submitted in a PR. If you wish to discuss patches you can also upload them somewhere and add a link to your e-mail. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: [patch] Make git dependencies optional.
Stef Walter wrote: > Dominic Fandrey wrote: >> Stef Walter wrote: >>> This patch ... >> Just for the future, patches should be submitted in a PR. If you >> wish to discuss patches you can also upload them somewhere and >> add a link to your e-mail. > > I believe I did that. Please see my original email [1]. Or am I missing > something? > > Cheers, > > Stef > > [1] http://www.mail-archive.com/freebsd-ports@freebsd.org/msg23708.html None the less you attached the patch. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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"
DeviceKit development?
This mail is a statement of a common opinion in a German BSD community. In depth information would be much appreciated, currently all our understanding and thus everything that follows is based on rumours. The German community is pretty upset about HAL and all the troubles we've had with it. In our eyes HAL is a polling nightmare that is technically obsolete because the FreeBSD kernel offers a register/notify model via devd, which is obviously superior. I.e. it only causes system load when an event occurs, as opposed to all the time with polling. Also many users used to have stability issues with HAL. I know of none, currently, but the common wisdom in the German community is that life without HAL is a better life. Seeing that the Linux world has trouble with HAL, too and appears to be abandoning it, it becomes necessary to implement the replacement DeviceKit, which appears to be going on as a part of porting Gnome3. Something which I have no first hand information about. While DeviceKit addresses the messy interface issue of HAL I am afraid that it still relies on the same polling methods as HAL. So it might prove as troublesome as HAL. What we wish for is a separate implementation that, though offering the same interface as DeviceKit, should be tightly coupled with FreeBSD facilities like devd. This would hopefully avoid the access right violations and stability issues that have been raised by HAL in the past. Of course, this would be a mighty endeavour and requires a stable DeviceKit API. But it appears to me (and others as well), that it might well prove to be the least troublesome path in the long run. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: audio/py-tagpy broken
Nicola Vitale wrote: > Hi Dominic, > >> [2009/11/5 Dominic Fandrey ] >> Whatever kind of information you require, I'm willing to provide. >> Sorry, your build failed. Try rerunning configure.py with different options. >> >> Traceback (most recent call last): >> File "setup.py", line 114, in >>main() >> File "setup.py", line 105, in main >>extra_compile_args=conf["CXXFLAGS"], > > It's strange, I have compiled it on my system and built in tinderbox > too (http://people.freebsd.org/~nivit/tb_logs/py26-tagpy-0.94.7.log ), > and there were not errors. > I'll check on an AMD64 system, thanks for the report. > > Ciao. I have found the strangest workaround, after the failure I just have to cd into the working directory, run make without parameters and it finishes building. It's only from the port that building doesn't work. I quickly found out that something in MAKE_ENV must be causing it, so I tried compiling repeatedly, each time stripping another variable and discovered that CXX causes my problem. If I leave it out of the MAKE_ENV it builds just fine. Considering that CXX is not even used this strikes me as quite strange and I know of no non-hacky way of removing it from MAKE_ENV. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Portmaster with package support ready for beta testing
Miroslav Lachman wrote: > Doug Barton wrote: >> Michel Talon wrote: >>> Miroslav Lachman wrote: I take a quick look at the code and I have one question. Can you explain way --no-deps and --force are used for pkg_add? >>> >>> >>> I can only venture an explanation. Once you have computed a good order >>> for upgrading via packages, you cannot accept that pkg_add ruins your >>> computation by doing things on its own. In principle you have a >>> global view of the problem, which is better than the local view embedded >>> in each package. Hence forcing pkg_add is the only sane way. >> >> Very elegantly stated. :) >> >> This is all subject to change of course based on refinement from >> experience, but this usage matches the way that ports are installed in >> the well-traveled port building code. > > Does it mean that one needs ports tree or provide custom INDEX in case > of custom packages with non default options (different dependencies) to > compute order od dependencies? > (AFAIK plain pkg_add works without ports tree and INDEX, that's why I am > asking) If you want to work without a ports tree use pkg_upgrade (sysutils/bsdadminscripts), it only requires an INDEX file. The next version will also require the MOVED file (as is now provided by Pointyhead). Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: remove BUILD_DEPENDS automatically after install
Sandra Kachelmann wrote: > (portmaster author cc:ed) > > On Mon, Nov 16, 2009 at 1:06 AM, Erik Trulsson wrote: >> On Sun, Nov 15, 2009 at 11:44:04PM +0100, Sandra Kachelmann wrote: >>> Is there a reason why BUILD_DEPENDS aren't being removed after a port >>> has been installed and if no other installed port depends on it? >> How do you know that the user does not want that port installed? >> And what if the user will install 20 other ports afterwards - all of which >> is that same port as a BUILD_DEPENDS - should that port be >> installed/deinstalled each and every time? > > It would be nice if this was configurable. Maybe it could be even > integrated into portupgrade or portmaster. If such a port is installed > directly it could get a package entry DIRECT_INSTALLED=yes in > /var/db/pkg/.. or something (there is probably a better way to do > this). If you installed from packages, they'd never get installed at all. portmaster and portupgrade both have ports tree based package support, pkg_upgrade (sysutils/bsdadminscripts) has index based package support and there's, in my opinion, rarely a reason to build your own packages, though I'm guilty of doing that, too. At least on one of my machines. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: OpenOffice.org packages
Gary Jennejohn wrote: > On Wed, 25 Nov 2009 05:01:19 -0600 > Mark Linimon wrote: > >> On Mon, Nov 23, 2009 at 09:05:46PM +0200, Aldis Berjoza wrote: >>> I and some other FreeBSD users are wondering why there are no >>> OpenOffice.org package available on FreeBSD Mirrors? >> OpenOffice is one of our most complex packages, and, depending on which >> package node it builds on, can take nearly a day to run. That plus the >> large number of dependencies it has makes it hard to build. >> >> I know that this is not a very satisfactory answer. I promise to once >> again look into the problem. >> > > Does the fact that it uses java cause a problem? Used to be that the > user had to manually download files from Sun, which would be impractical > for an automated run. > If it depended on OpenJDK by default it wouldn't be a problem. I do not know whether it does. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: cups-image build failure
Scott Nicholson wrote: > Hi, I'm having issues attempting to update cups via ports: > > ... > > Linking bannertops... > cc -L../cgi-bin -L../cups -L../filter -L../ppdc -L../scheduler > -L/usr/local/lib -Wl,-R/usr/local/lib -pie -fPIE -Wall -Wno-format-y2k > -fPIC -Os -g -fstack-protector -o bannertops bannertops.o pstext.o > common.o -lcupsimage \ > -lcups -pthread -lm -lcrypt > /usr/bin/ld: /usr/lib/crt1.o: relocation R_X86_64_32 can not be used > when making a shared object; recompile with -fPIC > /usr/lib/crt1.o: could not read symbols: Bad value > gmake[1]: *** [bannertops] Error 1 > gmake[1]: Leaving directory > `/usr/ports/print/cups-image/work/cups-1.4.2/filter' > gmake: *** [all] Error 1 > *** Error code 1 > > Stop in /usr/ports/print/cups-image. > *** Error code 1 > > Stop in /usr/ports/print/cups-image. > > > Yesterday I was getting this same error message during the cups-client > build, although that seems to have been fixed with today's commit to the > cups-base Makefile. Let me know if you need any more information. >>$ uname -a > FreeBSD xx.xx.local 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Thu Nov 26 > 21:41:57 PST 2009 r...@xx.xx.local:/usr/obj/usr/src/sys/GRENDEL amd64 Me too. FreeBSD mobileKamikaze.norad 8.0-STABLE FreeBSD 8.0-STABLE #2: Fri Nov 27 12:52:55 CET 2009 r...@mobilekamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6510b-8 amd64 All posters run amd64. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: cups-image build failure
Dominic Fandrey wrote: > Scott Nicholson wrote: >> Hi, I'm having issues attempting to update cups via ports: >> >> ... > > Me too. > ... It works, now. :) -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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"
creating a meta port ports-mgmt/pkg_upgrade
It has been suggested to me to split pkg_upgrade out of sysutils/bsdadminscripts and create a separate port in ports-mgmt/pkg_upgrade, because people have difficulty to find it, unless they stumble over one of my shameless advertisements. This however is not compatible with my plan to share code between scripts in the future. Hence the only alternative seems to me, a meta port in ports-mgmt/pkg_upgrade that depends on sysutils/bsdadminscripts. Would such a thing be accepted? I feel sceptical, because it does not even depend on several packages and the real solution in my opinion would be if people searched the ports tree with "make quicksearch cat=ports-mgmt" instead of browsing the file system. But they don't and I know of no way making them do it. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: creating a meta port ports-mgmt/pkg_upgrade
Freddie Cash wrote: > On Tue, Dec 1, 2009 at 5:59 AM, Dominic Fandrey wrote: > >> ... >> >> Would such a thing be accepted? I feel sceptical, because it does >> not even depend on several packages and the real solution in my >> opinion would be if people searched the ports tree with >> "make quicksearch cat=ports-mgmt" instead of browsing the file >> system. But they don't and I know of no way making them do it. >> > > You could always split out the common code into a library port, and make > that a dependency for the pkg_upgrade and bsdadminscripts ports. Yes, I could. Do you think it makes sense to split a package that is smaller than 100kB into several smaller packages? -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: [patch] fix config-recursive
Andrius Morkūnas wrote: > Anyone who uses config-recursive more often than once a year knows that > it's broken. Or at least they know it needs to be run multiple times until > it doesn't show options dialog. While some people might just live with it, > I think it should be fixed properly, and so did the person who introduced > this target: "it sufficed to run config-recursive twice to catch all of the > dependancies I had configured. Maybe we can figure out how to it all in one > pass later"[1]. The "later" is now, almost 5 years after config-recursive > was first introduced [2]. Nice work, did you PR this? -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: Pointyhat packages
Mark Linimon wrote: > On Tue, Dec 08, 2009 at 09:15:13AM -0300, oren.al...@gmail.com wrote: >> For the last couple of days I have been following the pointyhat build >> statistics provided at >> http://pointyhat.freebsd.org/errorlogs/packagestats.html > > Brave man :-) That's one I set up. > >> As seen on that page, the building process started on Dec 3rd but had >> not been completed yet. > > Apparently the build for www/p5-Gtk2-WebKit is now hanging on all buildenvs. > Pav already marked it so on amd64. > > It will continue to run until a reaper process kills it off (or one of > us portmgrs does it manually). I'd like to see the error log so I'm > going to let it run for now. The reaper process is IIRC 24 hours. > >> Why is there such a large difference between the build times on amd64 >> and i386? Are the i386 machines really that underpowered? > > Two data points: one, it looks like Pav having marked www/p5-Gtk2-WebKit > as broken had already been taken into account for the amd64 build, so it > didn't have that problem. And two, some of our i386 machines are indeed > underpowered. We've added several new, more modern, ones this year that > were donated to us: these are dual 2.4 or 2.8GHz machines, mostly with > 2G of RAM. (One of my background tasks is to try to characterize > performance on the nodes with various setups; my intuition is that 4G > would allow us to raise throughput, but I need to make a 'use case' for > that before I go ask for funding.) How much do you need? RAM isn't that expensive I think direct funding can be organized without all that overhead. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: Pointyhat packages
Pav Lucistnik wrote: > 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. :) > Can't you just take a jail? Just wondering ... -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: openoffice.org-3.1.1
Jerry wrote: > On Sun, 13 Dec 2009 10:12:38 +0100 > Baal Sebul replied: > > Is this some sort of joke? Two posts sans data approximately ten > minutes apart. > I bet he tried to send HTML mail or a similar folly. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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"
ioquake3 support more platforms
Hello, I'm maintaining games/ioquake3 and games/ioquake3-devel and I'd like to support more platforms than i386 and amd64. If anyone would like to support me, please apply the patch from ports/141453: http://www.freebsd.org/cgi/query-pr.cgi?pr=141453 Remove the ONLY_FOR_ARCHS line in games/ioquake3 and try to build games/ioquake3 and/or games/ioquake3-devel (the latter is more useful to send patches upstream). Send me the entire output. A committer explained to me that he doesn't want to deal with SVN snapshot based ports. Is that a common attitude and what should I do to remedy this? I'm providing distfiles, the web space for these is provided by a friend and the patches are all provided within the distfiles so they don't bloat the port. I've got no idea what else to do about this. I deem the devel port is necessary, because the switch from 1.34 to 1.36 was terrible. I'd been trying to port it for more than a month and just gave up. Half a year later I managed to solve all the major problems within a day, but all the patches in the original port had turned useless. This doesn't mean the addressed problems were gone. It just means they had been moved around into different files, the code all around changed and so on. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: ioquake3 support more platforms
Mark Linimon wrote: > On Thu, Dec 17, 2009 at 04:48:43PM +0100, Dominic Fandrey wrote: >> A committer explained to me that he doesn't want to deal with SVN >> snapshot based ports. Is that a common attitude and what should >> I do to remedy this? > > Well, the problem is that we (FreeBSD) can't guarantee whether the > contents of a resulting package are secure or not, or really, what > the contents are at all. I personally would only be comfortable with > a default setting of NO_PACKAGE in this case. Individual users could > manually override it. But that's not different for any port. E.g. sysutils/bsdadminscripts is all mine, I create the distfiles and maintain the port, their is no guarantee that I don't do evil apart from me being quite certain that I don't. Why can one assume that an ioquake release is safe? One really cannot. It's made by the same people who maintain the non-trustworthy SVN. What if I created a sourceforge project freebsd-ioquake and published my distfiles there as ioquake freebsd releases. Would it suddenly turn trustworthy? Also it's a -devel port. That kinda screams "At your own risk" right into your face. > I don't know if there is a formal policy about such ports. Probably, > there ought to be. I think there can be no guarantee given for anything whatsoever. So I do not see how a policy could be useful. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: ioquake3 support more platforms
Mark Linimon wrote: > On Fri, Dec 18, 2009 at 12:31:38PM +0100, Dominic Fandrey wrote: >> But that's not different for any port. E.g. sysutils/bsdadminscripts is >> all mine, I create the distfiles and maintain the port, their is no >> guarantee that I don't do evil apart from me being quite certain that >> I don't. > > Sure there is. That's why we have ports committers. They are supposed > to audit the changes to the port to make sure that the changes are safe. > In particular, I expect that they check that the changes are not so > extensive that they indicate the distributing system has been hacked. Are committers really supposed to read the code? I find that highly improbable, even for my shell scripts that only consist of a couple KBs of code. > >> Why can one assume that an ioquake release is safe? One really cannot. >> It's made by the same people who maintain the non-trustworthy SVN. > > There's no such check as the above possible with checkouts from a source > control system. You get whatever is on that box at time T. And I'm checking what those changes are to keep this stuff running on FreeBSD. The ioquake3 project doesn't hand commit right to everyone. Look at the e17 ports. Someone takes SVN snapshots, fixes them up for FreeBSD and bundles them as distfiles. It's exactly the same process I use for ioquake3, but no one thinks the ports are untrustworthy. >> Also it's a -devel port. That kinda screams "At your own risk" right >> into your face. > > And NO_PACKAGES would further guarantee it. I don't see that. But I see a lot of disadvantages. E.g. ioquake releases only occur every couple of years. Long before the next release occurs it might not make sense to maintain the last release, because it's simply depending on a lot of outdated infrastructure. Regards ___ 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: ioquake3 support more platforms
Mark Linimon wrote: > On Fri, Dec 18, 2009 at 01:43:20PM +0100, Dominic Fandrey wrote: >> Are committers really supposed to read the code? > > Yes. So when I submitted ioquake3-1.36 I condemned some poor committer to read 366609 lines of code? ___ 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: ioquake3 support more platforms
Doug Barton wrote: > Dominic Fandrey wrote: >> But that's not different for any port. E.g. sysutils/bsdadminscripts is >> all mine, I create the distfiles and maintain the port, their is no >> guarantee that I don't do evil apart from me being quite certain that >> I don't. > > Mark already pointed out that maintainers and committers actually _do_ > have a responsibility to dig into changes, be knowledgeable about > upgrades, etc. I agree with his perspective on this. > >> Why can one assume that an ioquake release is safe? One really cannot. >> It's made by the same people who maintain the non-trustworthy SVN. >> >> What if I created a sourceforge project freebsd-ioquake and published >> my distfiles there as ioquake freebsd releases. Would it suddenly >> turn trustworthy? > > The security problems involved in trying to audit a fixed, known set > of files are miniscule compared to the problems involved in auditing a > set of files that can change on a minute by minute basis. The whole > concept of creating a FreeBSD port that checks source files out of a > third-party svn repository is anathema to the whole concept of ports > security. Even if the files were directly checked out from SVN, they'd be checked out from a tested point in time. But this is not the case we're talking about (I explained the process in sufficient detail, I think). I take an up to date snapshot, apply my patch set, make a couple of test builds and runs, update the patch set until everything works as expected. Than I wrap the whole thing (SVN snapshot and my patches) up in a tar.gz and upload it to an ftp server. There's no danger that anything changes. I'm not about to break md5 and sha256. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: ioquake3 support more platforms
b. f. wrote: >> On Fri, Dec 18, 2009 at 02:50:31PM +0100, Dominic Fandrey wrote: >>> So when I submitted ioquake3-1.36 I condemned some poor committer >>> to read 366609 lines of code? >> We expect them to test-install the initial code to make sure it's >> not malware. >> >> We expect them to scan the diffs to make sure the system isn't rooted. > >> What's your alternate suggestion? Just let everyone commit whatever >> they want and hope for the best? > > Aren't the two of you talking at cross-purposes here? It seems to me > that the OP is looking for a way to update a port to a distfile > created from a snapshot of project sources -- not in the sense of > sources that are recreated each and every build by fetching a snapshot > from a remote VCS, but an actual tarball that has been audited, > checksummed, and uploaded to a project server. Surely this is needed > for a few ports, including some now in the tree? I have the same impression. I'm wondering how this could be the case. In the OP I wrote: > I'm providing distfiles, ... I don't see the wiggle room for anything spontaneously changing when properly checksummed distfiles are involved. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: ioquake3 support more platforms
Doug Barton wrote: > Dominic Fandrey wrote: >> But this is not the case we're talking about (I explained the process >> in sufficient detail, I think). I take an up to date snapshot, apply my >> patch set, make a couple of test builds and runs, update the patch set >> until everything works as expected. Than I wrap the whole thing (SVN >> snapshot and my patches) up in a tar.gz and upload it to an ftp server. > > Well then I misunderstood what was proposed, and I apologize for that. > What you described is supported, and some ports are already doing it. I'm really glad this is just a misunderstanding, I was about to panic. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: status of x11-drivers/input-wacom
Frank Staals wrote: > Hey everyone, > > Does anyone know of there is someone working on updating the input-wacom > driver ? The current port is broken on FreeBSD >= 8 and outdated. It > would be a shame if the driver realy dies; without the absolute > positioning the pen-tablets are not as usefull as they could be. I'm > don't have enough experiance in C to try and fix it myself, but I will > do what I can to help. > The developer (Bartosz) told me he'd get back to work on the driver around Christmas. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: Binary packages for releases and portupgrade
Lars Engels wrote: > On Wed, Jan 06, 2010 at 08:46:38PM +0100, Peter Ulrich Kruppa wrote: >> On Wed, 6 Jan 2010, Martin Cracauer wrote: >>> So the verdict is to hunt down OpenOffice packages manually and >>> install them so that portupgrade ignores them, then go from there. >>> >>> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/ >>> seems to have what `portupgrade -P` should expect, right? >>> >>> So I wouldn't have to move from stable to release+sec. >> I wonder if people who succeed in building OOo (happens about >> twice a year to me) could put their packages on some kind of ftp >> server. From their mailing list I get the impression OOo-porting >> team could need all kind of help. > > There are already some builds (english and german) at > http://wiki.bsdforen.de/anwendungen/openoffice_aus_inoffiziellen_paketen > > They're updated on a unregularly basis. That means you sometimes have to wait for a whole week after the port has been updated. ;) -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: Binary packages for releases and portupgrade
Lars Engels wrote: > On Wed, Jan 06, 2010 at 08:46:38PM +0100, Peter Ulrich Kruppa wrote: >> On Wed, 6 Jan 2010, Martin Cracauer wrote: >>> So the verdict is to hunt down OpenOffice packages manually and >>> install them so that portupgrade ignores them, then go from there. >>> >>> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/ >>> seems to have what `portupgrade -P` should expect, right? >>> >>> So I wouldn't have to move from stable to release+sec. >> I wonder if people who succeed in building OOo (happens about >> twice a year to me) could put their packages on some kind of ftp >> server. From their mailing list I get the impression OOo-porting >> team could need all kind of help. > > There are already some builds (english and german) at > http://wiki.bsdforen.de/anwendungen/openoffice_aus_inoffiziellen_paketen Actually there are more packages on the FTP than the ones listed there. Some people don't update the wiki page after uploading a new package. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: Build of sysutils/polkit, sysutils/policykit, docbook-410 Problem
Ralf Folkerts wrote: > Hi, > > I just updated my Ports-Tree and tried to rebuild sysutils/policykit (to > 0.9_6) and sysutils/polkit (to 0.96_1) as per UPDATING. > > ... > However, as I have no clue who's correct (the pol.*kit Makefiles by > assuming "catalog" in /share/sgml/docbook/4.1/ or the docbook-410 who > installs into the dtd Subdir) it would be cool if someone could check > this... I second this. > Btw: This is on > > FreeBSD 7.2-STABLE FreeBSD 7.2-STABLE #0: Fri Dec 11 22:19:58 CET 2009 > /usr/obj/usr/src/sys/GENERIC amd64 FreeBSD mobileKamikaze.norad 8.0-STABLE FreeBSD 8.0-STABLE #0: Fri Jan 22 22:51:14 CET 2010 r...@mobilekamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6510b-8 amd64 Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [CFT] Firefox 3.6 for FreeBSD
Greg Lewis wrote: > On Fri, Feb 05, 2010 at 07:48:37AM +1100, Peter Jeremy wrote: >> On 2010-Feb-04 01:19:33 +0100, Martin Wilke wrote: >>> The problem was that starting Firefox 3.6 with certain >>> addons installed was not possible. Now it looks like all >>> problems are solved and we can start a CFT. >> Thanks to all for your efforts. >> >>> weekend. We should also note that the java plugin currently >>> does not work with 3.6. >> This is a blocker for me. What is involved in building a >> java plugin to suit the new FF36 interface? Please let me know >> if there's anything I can do to assist the effort. > > Well, I don't believe the java plugin works with Firefox 3.5, so this isn't > a new development. You are mistaken here, the Java plugin works fine with firefox35. A real annoyance is that the OpenJDKs don't build the plugin, you need one of the SUN or Diablo JDKs. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [CFT] Firefox 3.6 for FreeBSD
Greg Lewis wrote: > On Fri, Feb 05, 2010 at 09:27:49AM +0100, Dominic Fandrey wrote: >> Greg Lewis wrote: >>> On Fri, Feb 05, 2010 at 07:48:37AM +1100, Peter Jeremy wrote: >>>> On 2010-Feb-04 01:19:33 +0100, Martin Wilke wrote: >>>>> The problem was that starting Firefox 3.6 with certain >>>>> addons installed was not possible. Now it looks like all >>>>> problems are solved and we can start a CFT. >>>> Thanks to all for your efforts. >>>> >>>>> weekend. We should also note that the java plugin currently >>>>> does not work with 3.6. >>>> This is a blocker for me. What is involved in building a >>>> java plugin to suit the new FF36 interface? Please let me know >>>> if there's anything I can do to assist the effort. >>> Well, I don't believe the java plugin works with Firefox 3.5, so this isn't >>> a new development. >> You are mistaken here, the Java plugin works fine with firefox35. > > Hmm. So I've got the plugin installed from the current diablo-jre16 port > and firefox35 doesn't find it. What does your set up look like? For me > its: > >> ls -l /usr/local/lib/browser_plugins/libjavaplugin_oji.so > lrwxr-xr-x 1 root wheel 63 Nov 8 10:50 > /usr/local/lib/browser_plugins/libjavaplugin_oji.so -> > /usr/local/diablo-jre1.6.0/plugin/i386/ns7/libjavaplugin_oji.so > > Are you using it from jdk16 perhaps? Yes, I'm using the JDK. # ll /usr/local/lib/browser_plugins/libjavaplugin_oji.so lrwxr-xr-x 1 root wheel 68 4 Feb 10:17 /usr/local/lib/browser_plugins/libjavaplugin_oji.so -> /usr/local/diablo-jdk1.6.0/jre/plugin/amd64/ns7/libjavaplugin_oji.so What does your about:plugins page say? > >> A real annoyance is that the OpenJDKs don't build the plugin, you >> need one of the SUN or Diablo JDKs. > > They don't build it because Sun doesn't include it... There's a project named IcedTea that builds OpenJDK with the plugin (http://openjdk.java.net/projects/icedtea/). ___ 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"
CONFLICTS checks during the wrong stage
It appears CONFLICTS is checked before build instead of checking it before install. Why? # portmaster -Do lang/perl5.10 lang/perl5.8 ===>>> Currently installed version: perl-threaded-5.8.9_3 ===>>> Port directory: /usr/ports/lang/perl5.10 ===>>> Launching 'make checksum' for lang/perl5.10 in background ===>>> Gathering dependency list for lang/perl5.10 from ports ===>>> No dependencies for lang/perl5.10 ===>>> Starting build for lang/perl5.10 <<<=== ===>>> All dependencies are up to date ===> Cleaning for perl-threaded-5.10.1 ===> perl-threaded-5.10.1 conflicts with installed package(s): perl-threaded-5.8.9_3 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/lang/perl5.10. ===>>> make failed for lang/perl5.10 ===>>> Aborting update ___ 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: CONFLICTS checks during the wrong stage
Matthew Seaman wrote: > On 06/02/2010 09:36, Dominic Fandrey wrote: >> It appears CONFLICTS is checked before build instead of checking >> it before install. Why? >> ... > > There was a discussion about this over on questions recently, starting here: > http://lists.freebsd.org/pipermail/freebsd-questions/2010-January/211053.html Thanks a lot for the pointer. I see I'm not alone with that. > > Lots of people are less than completely satisfied with the change. The > whole argument boils down to: > >* Having to jump through extra hoops in order to do some perfectly > reasonable operations such as > portupgrade -o new/port -f old/port-it-conflicts-with > > versus: > >* Accidentally spending a long time compiling a port when a > conflicting port is already installed. It really boils down to the choice of wasting: a) CPU time and bandwidth b) brain time I'd rather waste CPU time. > > Personally I feel that this change is in error -- it's ticking off the > vast majority of people that manage their ports day-to-day for the sake > of avoiding some newbie errors that you'ld only tend to make once or > twice. Printing out great big warnings at fetch and compile time when a > conflict is detected seems a much more reasonable response. The pkg_delete stuff messes up the dependency record in /var/db/pkg. Not acceptable. One of the arguments is that some ports link against old versions of themselves when old versions are around, so it's safer to remove stuff before building a new version. I can only disagree here (qt33 and kde3 do this). It means those ports are broken and ought to be fixed! The ports framework shouldn't be built to tolerate broken ports. My workaround is to remove the CONFLICTS line from the Makefiles. Also not really acceptable, but at least /var/db/pkg doesn't get corrupted. Anyway, I have decided to follow evil to its root and request revocation: http://www.freebsd.org/cgi/query-pr.cgi?pr=137855 -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: xterm 253 DECRQSS Again?
Anon wrote: > Hi > > long ago I read about the bug in Xterm CVE-2008-2383 and updated xterm. Now > I have the version of xterm 253 and on occasion being in xterm to run a cat > on binary file (executable, images, etc) appear repeatedly on Shell "2c1: > command not found". You will see in the picture you take > > http://lh3.ggpht.com/_1zYIthtq7IY/S24v__tlDAI/AJk/aWhG5E3fJ4o/s800/xterm_bug.png > > This can be a bug again? > > Regards Some of that binary data is probably interpreted as escape sequences. A terminal simply isn't meant to display binary data. Regards ___ 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: CONFLICTS checks during the wrong stage
Dominic Fandrey wrote: > It appears CONFLICTS is checked before build instead of checking > it before install. Why? > > # portmaster -Do lang/perl5.10 lang/perl5.8 Just a couple of minutes ago I answered a post by someone who thought both portupgrade and portmaster are broken. And yesterday I got the kudos for complaining here. I always thought portmgr is pretty conservative about changes. This can be annoying, when you try to get something reasonable committed, but really it's protecting the infrastructure. And now all of a sudden, with a flip of a finger compatibility gets broken, year long practised work flows go down the drain. I'm told there's something coming up that will satisfy all parties, which is great. But until then I'd prefer the old behaviour. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Ports Problem - Please help
jhell wrote: > > > On Fri, 12 Feb 2010 07:27, lenzi.sergio@ wrote: >> try to make it work again (with the now missing libjpeg.so.10... >> by inserting a line in the /etc/libmap.conf > >> echo "libjpeg.so.10 libjpeg.so" >> /etc/libmap.conf > >> than probably all will work again... by the time you build all ports, >> the later will be linked agains version 11.. and than you can >> delete the line in the libmap.conf > > >> Hope this will help. > > > Among all these you may find it useful to install sysutils/libchk. > > This utility can play a key role in locating just the packages/ports > that need to be rebuilt against the new library. Hmm, I just tested it, because my port sysutils contains pkg_libchk, which has a very similar function. My script needs 6m14.73s for a full run, whereas libchk only requires 3m56.38s. However libchk yields a lot of false positives, it's quite difficult to find the information you need. The output of pkg_libchk looks like that: hdf5-1.6.9_1: /usr/local/bin/h5perf misses libh5test.so.0 So it's a lot easier to make a list of broken ports. It also only lists directly linked libraries, so it really only lists the packages that need relinking. A lot of its runtime is dedicated to detecting false positives. It doesn't have libchk's ability to list unused libraries, though. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Ports Problem - Please help
jhell wrote: > > On Fri, 12 Feb 2010 13:25, kamikaze@ wrote: >> jhell wrote: >>> >>> >>> On Fri, 12 Feb 2010 07:27, lenzi.sergio@ wrote: try to make it work again (with the now missing libjpeg.so.10... by inserting a line in the /etc/libmap.conf >>> echo "libjpeg.so.10 libjpeg.so" >> /etc/libmap.conf >>> than probably all will work again... by the time you build all ports, the later will be linked agains version 11.. and than you can delete the line in the libmap.conf >>> >>> Hope this will help. >>> >>> >>> Among all these you may find it useful to install sysutils/libchk. >>> >>> This utility can play a key role in locating just the packages/ports >>> that need to be rebuilt against the new library. >> >> Hmm, I just tested it, because my port sysutils contains pkg_libchk, >> which has a very similar function. >> >> My script needs 6m14.73s for a full run, whereas libchk only >> requires 3m56.38s. >> >> However libchk yields a lot of false positives, it's quite difficult >> to find the information you need. The output of pkg_libchk looks >> like that: >> hdf5-1.6.9_1: /usr/local/bin/h5perf misses libh5test.so.0 >> >> So it's a lot easier to make a list of broken ports. It also only >> lists directly linked libraries, so it really only lists the packages >> that need relinking. A lot of its runtime is dedicated to detecting >> false positives. >> >> It doesn't have libchk's ability to list unused libraries, though. > > Never the less its more of a hands on experience when something goes > wrong and especially with jpeg. Needless to say the only output your > really looking for is anything with jpeg in it and the file it lists > above. False positives are just a side effect of a system that uses > shared libs and the way that installed programs use them. > > Some of the programs that I have noticed that looks like false positives > are firefox mono octave hdf5 and when found usually you can just surf > the text file by eye and its not to hard to recognize the path that the > file installed in and dismiss them. hdf5 is not a false positive. The port is and has been installing incompletely for a long time. The maintainer is not willing to patch that himself and I have no idea what it's even good for, so I won't bother either. For the other libraries mentioned - it's not necessary to burden the user with checking for them manually, so why should it be done? Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD ports which are currently scheduled for deletion
On 21/02/2010 08:30, lini...@freebsd.org wrote: > portname: java/eclipse-emf > description:Eclipse Modeling Framework > maintainer: freebsd-ecli...@freebsd.org > deprecated because: This plugin can be installed from within eclipse via > the updater > expiration date:2010-01-19 > build errors: none. > overview: > http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=eclipse-emf > > > portname: java/eclipse-gef > description:Graphical Editing Framework for the Eclipse IDE > maintainer: freebsd-ecli...@freebsd.org > deprecated because: This plugin can be installed from within eclipse via > the updater > expiration date:2010-01-19 > build errors: none. > overview: > http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=eclipse-gef It is my conviction that these updaters only exist, because Microsoft OSs come without a packaging system. I prefer to have my plugins installed once and maintained by the system administrator instead of delegating this task to each user, such multiplying disk use and work. I'm aware I could do this by running eclipse as root, but I shudder at the thought of such abominal behaviour. I'm willing to take maintainership to preserve my ideal of using one packaging system for all software. Should I write a PR? Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: make package-noinstall does not include rc.d scripts?
On 20/02/2010 16:55, Christer Solskogen wrote: > Hi! > > I've just discovered the make option "make package-noinstall" which > makes a tbz in /usr/ports/packages from a already installed package. > But I've also found a bug(?) with that option. The package it creates > seems not to include rc.d script which will be included if you use > "make package" > I've tried this now with two ports (stunnel and mysql51-server) - but > I guess that it will happen to other ports as well. Does the same problem appear with "pkg_create -b"? I'd expect such a target simply calling that and if that would be broken it would affect the use of almost every package maintenance tool for the FreeBSD ports. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: make package-noinstall does not include rc.d scripts?
On 21/02/2010 10:33, Christer Solskogen wrote: > On Sun, Feb 21, 2010 at 9:12 AM, Dominic Fandrey wrote: > >> Does the same problem appear with "pkg_create -b"? > > No. pkg_create -b does the job. The only "problem" with pkg_create is > that it dont create packages and symlinks in /usr/ports/packages/. So the right solution might be for the "package-noinstall" target to use "pkg_create -b" and additionally create the symlinks. I do not like have different code for doing the same thing in this context. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: make package-noinstall does not include rc.d scripts?
On 21/02/2010 10:47, Christer Solskogen wrote: > On Sun, Feb 21, 2010 at 10:44 AM, Dominic Fandrey > wrote: > >> So the right solution might be for the "package-noinstall" target to >> use "pkg_create -b" and additionally create the symlinks. >> >> I do not like have different code for doing the same thing in this >> context. >> > > Does the target 'package' use pkg_create? Yes it does. I have a patch that should do the trick. Would you be so kind to test it? http://www.home.hs-karlsruhe.de/~fado0001/patch-ports-Mk-bsd.port.mk.txt If it does, please open a PR and post the number here. wxs and I can post our patches there and portmgr can decide. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: make package-noinstall does not include rc.d scripts?
On 21/02/2010 11:02, Dominic Fandrey wrote: > On 21/02/2010 10:47, Christer Solskogen wrote: >> On Sun, Feb 21, 2010 at 10:44 AM, Dominic Fandrey >> wrote: >> >>> So the right solution might be for the "package-noinstall" target to >>> use "pkg_create -b" and additionally create the symlinks. >>> >>> I do not like have different code for doing the same thing in this >>> context. >> >> Does the target 'package' use pkg_create? > > Yes it does. More precisely, do-package does. > I have a patch that should do the trick. Would you be so kind to test > it? > http://www.home.hs-karlsruhe.de/~fado0001/patch-ports-Mk-bsd.port.mk.txt > > If it does, please open a PR and post the number here. wxs and I can > post our patches there and portmgr can decide. After testing my patch to my satisfaction I went ahead and opened a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=144164 -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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"
pkg_upgrade perl update
If you run 'pkg_upgrade -a' and see the following message: pkg_add: can't open dependency file '/var/db/pkg/perl-5.10.1/+REQUIRED_BY'! dependency registration is incomplete pkg_upgrade: Add dependency (lang/perl5.8). Run pkg_upgrade -C lang/perl5.10 to update to the right version of perl. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: php5-gd PNG support broken
On 22/10/2009 08:26, Dominic Fandrey wrote: > I've got the following problem with php5-gd: > > Warning: imagecreatefrompng() [function.imagecreatefrompng]: gd-png: fatal > libpng error: [00][00][00][00]: unknown critical chunk in > /usr/home/kamikaze/devel/workspace/realmsofsorrow/nightmare/core/nmTemplate.class.php > on line 385 > > Warning: imagecreatefrompng() [function.imagecreatefrompng]: gd-png error: > setjmp returns error condition in > /usr/home/kamikaze/devel/workspace/realmsofsorrow/nightmare/core/nmTemplate.class.php > on line 385 > > Warning: imagecreatefrompng() [function.imagecreatefrompng]: > './templates/neo/layout/header_stretch.png' is not a valid PNG file in > /usr/home/kamikaze/devel/workspace/realmsofsorrow/nightmare/core/nmTemplate.class.php > on line 385 > > > I get this message for all PNGs. I checked the files with Firefox, > and Gimp, they are all whole. They are also displayed by the e17 > file browser, which relies on libpng. The problem still persists! > My system: > FreeBSD mobileKamikaze.norad 7.2-STABLE FreeBSD 7.2-STABLE #0: Fri Jul 3 > 10:26:33 CEST 2009 > r...@mobilekamikaze.norad:/usr/obj/HP6510b/amd64/usr/src/sys/HP6510b amd64 My system, now: FreeBSD mobileKamikaze.norad 8.0-STABLE FreeBSD 8.0-STABLE #1: Tue Feb 23 10:37:52 CET 2010 r...@mobilekamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6510b-8 amd64 > libpng: > png-1.2.40 libpng, now: png-1.2.42 > php5-gd: > php5-gd-5.2.11_1 php5-gd, now: php5-gd-5.2.12 I have found a workaround: # env LD_PRELOAD=/usr/local/lib/libpng.so.5 /usr/local/etc/rc.d/apache22 restart I find the implications deeply troubling. Note that ldd has no problems locating the library: # ldd /usr/local/lib/php/20060613/gd.so /usr/local/lib/php/20060613/gd.so: ... libpng.so.5 => /usr/local/lib/libpng.so.5 (0x80120d000) ... So why does the apache module fail to load it? Why do I have to force the runtime linker to do so? -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: make package for ports, general question
On 25/02/2010 06:25, Jason wrote: > That being said, I ran into an item today that had me perplexed. > > Basically, it comes down to this: > http://www.freebsd.org/doc/en/books/porters-handbook/pkg-install.html > > Why is it that "make package" doesn't include the execution instructions > noted in the Makefile. To me, with my new knowledge of the ports system, > seems like double the work for development and maintaining a port and > package. ... It's not like that at all. You should only add stuff into the ports Makefile that installs new files into the system. Everything else, like creating groups and users, updating an index and so forth, should only be done in the pkg-install script. There is no redundancy. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: make package for ports, general question
On 25/02/2010 16:52, Jason wrote: > On Thu, Feb 25, 2010 at 09:25:09AM +0100, Dominic Fandrey thus spake: >> On 25/02/2010 06:25, Jason wrote: >>> That being said, I ran into an item today that had me perplexed. >>> >>> Basically, it comes down to this: >>> http://www.freebsd.org/doc/en/books/porters-handbook/pkg-install.html >>> >>> Why is it that "make package" doesn't include the execution instructions >>> noted in the Makefile. To me, with my new knowledge of the ports system, >>> seems like double the work for development and maintaining a port and >>> package. ... >> >> It's not like that at all. You should only add stuff into the ports >> Makefile that installs new files into the system. >> > > This make much more sense now. > >> Everything else, like creating groups and users, updating an index >> and so forth, should only be done in the pkg-install script. >> > > That's unfortunate for the user installation, as you can use the native > USERS directive in Makefiles to install users. I've started using local UID > and GID files to install users, and it has worked out rather well. I > suppose > removing the functionality from the Makefile, yet keeping those files > up-to-date for reference, is still a good idea. My error, USERS and GROUPS are official ports features and hence should be used. That kind of information also makes it into packages just fine. I don't maintain any ports that create users, so I overlooked it. Sorry for providing false information. > > Do: > > BINMODE > SHAREMODE > CHOWN > CHMOD > need to go into a pkg-install file? No, because the package is a tar archive that preserves these file properties. > I saw that there is a "Do & Dont's" on the todo list at wiki.freebsd.org > for > Ports. Maybe adding some of this information in there would be good. As you can see, the cases where a pkg-install script is actually needed are rather rare. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: Shoud devel port be RC or GIT based?
On 15/02/2010 01:45, CeDeROM wrote: > In a moments of hard testing just before a software release, releases > of a RC (Release Candidate) packages are done to alow some final > tests. I am wondering if it is convenient to create the devel port, to > allow better testing for non-freebsd-aware users. Would that be more > convenient to base such devel port on a RC releases, or directly the > GIT repository? This approach is not very popular. An RC release is fine, but if you want to test builds right from a repository, you are well advised to create snapshots, package them and base your ports on these. An example for this is the games/ioquake3-devel port: ftp://deponie.yamagi.org/freebsd/distfiles/ioquake3/ I update that whenever significant changes occur on SVN. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portmaster usage for a list of ports
On 27/02/2010 11:10, Michael Reifenberger wrote: > Hi, > for compiling a list of ports inside a emulated FreeBSD-current environment > I would need to use portmaster as: > > cat ./myports.txt | xargs portmaster -r -R -G -g -d -m "WITHOUT_GSSAPI=YES" > (myports.txt contains a list of to be installed/updated ports) Useless use of cat. xargs < ./myports.txt portmaster ... > Unfortunately this doesn't work (specifying -m "BATCH=yes" doesn't help > too). xargs(1) holds the solution, this one will work: xargs -o < ./myports.txt portmaster ... -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Ports with same name
On 09/03/2010 19:32, Shaun Amott wrote: > On Tue, Mar 09, 2010 at 10:23:51AM -0500, Steven Kreuzer wrote: >> As documented in http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/144277 >> we have two ports with the same name: >> >> Port:gag-2.9 >> Path:/usr/ports/security/gag >> Info:A stacheldraht (DOS attack) agent detector > > [...] > >> Port:gag-4.9 >> Path:/usr/ports/sysutils/gag >> Info:Graphical Boot Manager > > [...] > >> I am looking for some advice on whats the best course of action to deal with >> this. >> >> My gut feeling is that sysutils/gag should remain the same and that >> security/gag should be >> renamed to security/gag-stacheldraht. >> pkg_upgrade behaves in this kind of situation in the following way: It checks the matching package names. If more than one package matches, it checks whether one matches an already installed origin. If only one of them is installed, it updates that one. If both are installed (very rare), it fails and the user has to provide an origin instead of a package name. >> Anyone vehemently opposed to this? > > The new name sounds reasonable, but it would probably make sense just to > change LATEST_LINK rather than "move" the port. > I agree, LATEST_LINK is the appropriate change. Port names are not unique identifiers. category/port is. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: Full Unicode Support for FreeBSD
On 12/03/2010 19:23, 葉佳威 Jiawei Ye wrote: > On Sat, Mar 13, 2010 at 1:43 AM, Elmar Stellnberger wrote: >> Isn`t it time for FreeBSD to fully support Unicode/UTF-8 by now? >> It is considered to be standard charset by now. XML uses it by default. >> If you are working with texts in different languages there is no >> alternative to UTF-8. >> If you chat with a Linux machine you can easily run into charset >> troubles if you are >> still using the old iso-8859-1. >> >> By now it is no problem to activate UTF-8 for your console. >> However a comprehensive Unicode support would require much more: >> i.e. configuring all user packages like KDE for Unicode support and >> asserting that also file names (f.i. from ext2 partitions) are interpreted >> correctly. > Do you have a concrete example of how FreeBSD fails to support UTF-8? > I have been setting my LANG to zh_TW.UTF-8 for years without problem > with modern software. As this is the ports list, I guess you have some > issues with the software in the ports collection? I second this. I've been using en_GB.UTF-8 since 5.3. Even the file system can deal with UTF-8 encoded file names. I tried to create files with Arabian, Chinese, Russian and other characters. It all worked. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [ HEADS UP ] Ports unstable for the next 10 days
On 28/03/2010 15:38, Ion-Mihai Tetcu wrote:
> We do _NOT_ recommend updating ports until this commits are all done,
> and the problems are fixed, except if you want to help testing / fixing.
A small fix for graphics/php5-gd. It builds without the patch, but
doesn't work without it.
diff -Nur php5-gd.orig/files/patch-ext-gd-libgd-gd_png.c
php5-gd/files/patch-ext-gd-libgd-gd_png.c
--- php5-gd.orig/files/patch-ext-gd-libgd-gd_png.c 1970-01-01
01:00:00.0 +0100
+++ php5-gd/files/patch-ext-gd-libgd-gd_png.c 2010-03-29 09:38:38.0
+0200
@@ -0,0 +1,11 @@
+--- libgd/gd_png.c.orig2010-03-29 09:33:02.0 +0200
libgd/gd_png.c 2010-03-29 09:35:15.0 +0200
+@@ -139,7 +139,7 @@
+ return NULL;
+ }
+
+- if (!png_check_sig (sig, 8)) { /* bad signature */
++ if (png_sig_cmp (sig, 0, 8) != 0) { /* bad signature */
+ return NULL;
+ }
+
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [ HEADS UP ] Ports unstable for the next 10 days
On 28/03/2010 15:38, Ion-Mihai Tetcu wrote:
> We do _NOT_ recommend updating ports until this commits are all done,
> and the problems are fixed, except if you want to help testing / fixing.
Fix for graphics/evas-loader-png.
diff -Nur
evas-loader-png.orig/files/patch-src-modules-loaders-png-evas_image_load_png.c
evas-loader-png/files/patch-src-modules-loaders-png-evas_image_load_png.c
---
evas-loader-png.orig/files/patch-src-modules-loaders-png-evas_image_load_png.c
1970-01-01 01:00:00.0 +0100
+++ evas-loader-png/files/patch-src-modules-loaders-png-evas_image_load_png.c
2010-03-29 09:54:23.0 +0200
@@ -0,0 +1,11 @@
+--- src/modules/loaders/png/evas_image_load_png.c.orig 2010-03-29
09:51:19.0 +0200
src/modules/loaders/png/evas_image_load_png.c 2010-03-29
09:52:29.0 +0200
+@@ -44,7 +44,7 @@
+ fclose(f);
+ return 0;
+ }
+- if (!png_check_sig(buf, PNG_BYTES_TO_CHECK))
++ if (png_sig_cmp(buf, 0, PNG_BYTES_TO_CHECK) != 0)
+ {
+ fclose(f);
+ return 0;
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [ HEADS UP ] Ports unstable for the next 10 days
On 29/03/2010 09:58, Dominic Fandrey wrote:
> On 28/03/2010 15:38, Ion-Mihai Tetcu wrote:
>> We do _NOT_ recommend updating ports until this commits are all done,
>> and the problems are fixed, except if you want to help testing / fixing.
>
> Fix for graphics/evas-loader-png.
Sorry, wrong patch. This is the one:
diff -Nur
evas-loader-png.orig/files/patch-src-modules-loaders-png-evas_image_load_png.c
evas-loader-png/files/patch-src-modules-loaders-png-evas_image_load_png.c
---
evas-loader-png.orig/files/patch-src-modules-loaders-png-evas_image_load_png.c
1970-01-01 01:00:00.0 +0100
+++ evas-loader-png/files/patch-src-modules-loaders-png-evas_image_load_png.c
2010-03-29 10:01:37.0 +0200
@@ -0,0 +1,20 @@
+--- src/modules/loaders/png/evas_image_load_png.c.orig 2007-10-28
11:35:13.0 +0100
src/modules/loaders/png/evas_image_load_png.c 2010-03-29
10:01:31.0 +0200
+@@ -44,7 +44,7 @@
+ fclose(f);
+ return 0;
+ }
+- if (!png_check_sig(buf, PNG_BYTES_TO_CHECK))
++ if (png_sig_cmp(buf, 0, PNG_BYTES_TO_CHECK) != 0)
+ {
+ fclose(f);
+ return 0;
+@@ -121,7 +121,7 @@
+
+/* if we havent read the header before, set the header data */
+fread(buf, 1, PNG_BYTES_TO_CHECK, f);
+- if (!png_check_sig(buf, PNG_BYTES_TO_CHECK))
++ if (png_sig_cmp(buf, 0, PNG_BYTES_TO_CHECK) != 0)
+ {
+ fclose(f);
+ return 0;
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [ HEADS UP ] Ports unstable for the next 10 days
On 28/03/2010 15:38, Ion-Mihai Tetcu wrote:
> We do _NOT_ recommend updating ports until this commits are all done,
> and the problems are fixed, except if you want to help testing / fixing.
The already committed graphics/imlib2 patch does not work,
i.e. it compiles, but png doesn't work, with this one it does:
diff -Nur imlib2.orig/files/patch-loader_png.c imlib2/files/patch-loader_png.c
--- imlib2.orig/files/patch-loader_png.c2010-03-29 10:12:43.0
+0200
+++ imlib2/files/patch-loader_png.c 2010-03-29 10:08:41.0 +0200
@@ -5,7 +5,7 @@
/* if we haven't read the header before, set the header data */
fread(buf, 1, PNG_BYTES_TO_CHECK, f);
-if (!png_check_sig(buf, PNG_BYTES_TO_CHECK))
-+if (png_check_sig(buf, 0, PNG_BYTES_TO_CHECK))
++if (png_sig_cmp(buf, 0, PNG_BYTES_TO_CHECK) != 0)
{
fclose(f);
return 0;
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [ HEADS UP ] Ports unstable for the next 10 days
On 28/03/2010 15:38, Ion-Mihai Tetcu wrote:
> We do _NOT_ recommend updating ports until this commits are all done,
> and the problems are fixed, except if you want to help testing / fixing.
graphics/inkscape needs a dependency fix.
diff -Nur inkscape.orig/Makefile inkscape/Makefile
--- inkscape.orig/Makefile 2010-03-29 12:06:39.0 +0200
+++ inkscape/Makefile 2010-03-29 12:07:39.0 +0200
@@ -22,7 +22,7 @@
gtkspell.0:${PORTSDIR}/textproc/gtkspell \
lcms.1:${PORTSDIR}/graphics/lcms \
wpg-0.1.1:${PORTSDIR}/graphics/libwpg \
- Magick++.2:${PORTSDIR}/graphics/ImageMagick
+ Magick++.3:${PORTSDIR}/graphics/ImageMagick
RUN_DEPENDS= ${SITE_PERL}/XML/XQL.pm:${PORTSDIR}/textproc/p5-XML-XQL
USE_BZIP2= yes
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [ HEADS UP ] Ports unstable for the next 10 days
On 29/03/2010 11:27, Ion-Mihai Tetcu wrote: > On Mon, 29 Mar 2010 10:15:23 +0200 > Dominic Fandrey wrote: > >> On 28/03/2010 15:38, Ion-Mihai Tetcu wrote: >>> We do _NOT_ recommend updating ports until this commits are all >>> done, and the problems are fixed, except if you want to help >>> testing / fixing. >> >> The already committed graphics/imlib2 patch does not work, >> i.e. it compiles, but png doesn't work, with this one it does: > > [ .. ] > > Committed, thanks. > Someone committed the broken code again. :( ___ 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: "stable" ports?
On 29/03/2010 17:57, Ivan Voras wrote: > One way to do it, my proposal, would be to maintain a stable "overlay" > of the ports, one for each major supported branch (i.e. 6.x, 7.x, 8.x), > containing ports deemed "important" for some reason. Who would be doing the additional work? I figure we'd need additional maintainers for the different branches. I don't see myself maintaining several branches of my ports, apart from ioquake3 and ioquake3-devel. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: Unresolvable link(s) found in: /usr/local/lib/firefox3/
On 31/03/2010 17:49, Henk van Oers wrote: > > After recompiling all png depends I ran libchk, just to be shure. > ... > Unresolvable link(s) found in: > /usr/local/lib/firefox3/components/libbrowsercomps.so > libxul.so > libxpcom.so Those are false positives, the libraries belong to firefox and are even part of the same package. You can try the pkg_libchk command coming with sysutils/bsdadminscripts, which takes great care to avoid false positives. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: processing the MOVE file
On 06/04/2010 17:08, Zane C. B. wrote: > When it comes to processing the MOVE file, how does one check if the > a move is relevant to the currently installed package? If the origin of your package is no longer available, I'd use the last matching MOVED entry. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: processing the MOVE file
On 06/04/2010 18:45, Zane C.B. wrote: > On Tue, 06 Apr 2010 18:31:38 +0200 > Dominic Fandrey wrote: > >> On 06/04/2010 17:08, Zane C. B. wrote: >>> When it comes to processing the MOVE file, how does one check if >>> the a move is relevant to the currently installed package? >> >> If the origin of your package is no longer available, I'd use >> the last matching MOVED entry. > > The problem with this method is I've seen it fail before on gstreamer > and a few others. If you knew the date of the ports tree the package was built from, you could pick the first match after said date. This is what I'd like to do for the coming version of pkg_upgrade. There's no way to get this information, though. So I'll use the latest entry approach as this is the one I expect to fail least often (is that proper English?). -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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"
Trivial PR, fix package-noinstall
This morning I took a look at my outstanding PRs. There are is a ports PR I consider old and trivial: This one fixes a bug in the package-noinstall target. wxs told me that he prefers my proposed fix over his own: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/144164 Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: Trivial PR, fix package-noinstall
On 10/04/2010 12:49, Garrett Cooper wrote:
> On Sat, Apr 10, 2010 at 3:44 AM, Dominic Fandrey wrote:
>> On 10/04/2010 12:18, Garrett Cooper wrote:
>>> On Sat, Apr 10, 2010 at 2:29 AM, Dominic Fandrey
>>> wrote:
>>>> This morning I took a look at my outstanding PRs. There are
>>>> is a ports PR I consider old and trivial:
>>>>
>>>> This one fixes a bug in the package-noinstall target. wxs told
>>>> me that he prefers my proposed fix over his own:
>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/144164
>>>
>>> This suggested fix completely breaks pkg_creates operation because it
>>> does a chdir(2) prior to package creation (from
>>> .../usr.sbin/pkg_install/create/perform.c:555):
>>>
>>> if (chdir(log_dir) == FAIL) {
>>> warnx("can't change directory to '%s'!", log_dir);
>>> return FALSE;
>>> }
>>
>> I don't see what appears to be the problem. The fix is tested,
>> there is no chdiring and pkg_create is not modified in any way.
>>
>> All it does is change the parameters pkg_create is called with.
>
> Have you tested in the following cases:
>
> 1. With the pkg_install scripts.
> 2. Without the pkg_install scripts.
>
> If not, then you need to do that before asking for someone to
> commit your code :).
The do-package code is used by the package and the package-noinstall
targets.
package-noinstall is called by package-recursive on ALL-DEPENDS.
I.e. it is only used on completely installed packages, just what
"pkg_create -b" was made for.
The regular package target is always run after install (search for
"Main logic" in bsd.port.mk). So do-package is only called after
install has completed, hence the code can, in every case, rely on
logdir containing all required data.
Regards
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
___
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: Trivial PR, fix package-noinstall
On 10/04/2010 13:11, Gary Jennejohn wrote: > On Sat, 10 Apr 2010 03:18:42 -0700 > Garrett Cooper wrote: >> FWIW, I've thought this over and and user modifiable scripts should >> not be in packages; they should instead be example files which don't >> conflict with real configuration files. This is already the case for >> several ports, but not all ports. If we did this, it would solve the >> problem we've had with ports removing or overwriting user config files >> simply and easily. I wonder if other folks agree with me or not. >> > > I agree as long as the port emits a message pointing the user at the > example configuration files. I think noone ever agreed that installing user changeable configuration files was a good idea and .sample files or include folders are both prominent and widely accepted solutions. However this only ever entered the discussion because of a misunderstanding. I'd prefer to keep the discussion on topic and avoid the million "I agree" posts on something no one ever disagreed to. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: Trivial PR, fix package-noinstall
On 10/04/2010 23:30, Garrett Cooper wrote:
> On Sat, Apr 10, 2010 at 4:26 AM, Dominic Fandrey wrote:
>> On 10/04/2010 12:49, Garrett Cooper wrote:
>>> On Sat, Apr 10, 2010 at 3:44 AM, Dominic Fandrey
>>> wrote:
>>>> On 10/04/2010 12:18, Garrett Cooper wrote:
>>>>> On Sat, Apr 10, 2010 at 2:29 AM, Dominic Fandrey
>>>>> wrote:
>>>>>> This morning I took a look at my outstanding PRs. There are
>>>>>> is a ports PR I consider old and trivial:
>>>>>>
>>>>>> This one fixes a bug in the package-noinstall target. wxs told
>>>>>> me that he prefers my proposed fix over his own:
>>>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/144164
>>>>>
>>>>> This suggested fix completely breaks pkg_creates operation because it
>>>>> does a chdir(2) prior to package creation (from
>>>>> .../usr.sbin/pkg_install/create/perform.c:555):
>>>>>
>>>>> if (chdir(log_dir) == FAIL) {
>>>>> warnx("can't change directory to '%s'!", log_dir);
>>>>> return FALSE;
>>>>> }
>>>>
>>>> I don't see what appears to be the problem. The fix is tested,
>>>> there is no chdiring and pkg_create is not modified in any way.
>>>>
>>>> All it does is change the parameters pkg_create is called with.
>>>
>>> Have you tested in the following cases:
>>>
>>> 1. With the pkg_install scripts.
>>> 2. Without the pkg_install scripts.
>>>
>>> If not, then you need to do that before asking for someone to
>>> commit your code :).
>>
>> The do-package code is used by the package and the package-noinstall
>> targets.
>>
>> package-noinstall is called by package-recursive on ALL-DEPENDS.
>> I.e. it is only used on completely installed packages, just what
>> "pkg_create -b" was made for.
>>
>> The regular package target is always run after install (search for
>> "Main logic" in bsd.port.mk). So do-package is only called after
>> install has completed, hence the code can, in every case, rely on
>> logdir containing all required data.
>
> Ok, interesting. If you look at another spot in bsd.port.mk, there's
> another area where +INSTALL and friends are installed:
>
> fake-pkg:
> # ...
> if [ -f ${PKGINSTALL} ]; then \
> ${CP} ${PKGINSTALL} ${PKG_DBDIR}/${PKGNAME}/+INSTALL; \
> fi; \
> if [ -f ${PKGDEINSTALL} ]; then \
> ${CP} ${PKGDEINSTALL} ${PKG_DBDIR}/${PKGNAME}/+DEINSTALL; \
> fi; \
> if [ -f ${PKGREQ} ]; then \
> ${CP} ${PKGREQ} ${PKG_DBDIR}/${PKGNAME}/+REQUIRE; \
> if [ -f ${PKGMESSAGE} ]; then \
> ${CP} ${PKGMESSAGE} ${PKG_DBDIR}/${PKGNAME}/+DISPLAY; \
> fi; \
> # ...
>
> So if I don't define NO_PKG_REGISTER and I define FORCE_PKG_REGISTER,
> then this logic will be executed.
Maybe it's because it's 2 AM, but once again I fail to see the
connection to my patch.
> This change does need to be tested for the make package-noinstall case
> with pkg-install, pkg-deinstall, etc being present and not being
> present [in their .in files form and non-.in files form]. Otherwise
> this is going to potentially introduce a regression into bsd.port.mk.
If you have a case you suspect might go wrong, please go ahead.
I find myself unable to follow your logic, so I wouldn't even know
the symptoms of something going wrong.
As far as I can see you are talking about install, something my patch
does in no way interfere with. The only connection between install and
package I see is, that the order in which they can be executed is
carved in stone.
Regards
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Recent nc(1) changes
On 15/04/2010 21:24, Xin LI wrote: > ... I'd say that the data loss (~1%) when I tried to use nc with UNIX sockets (on both ends) is much more troublesome than your changes. Even when I used lockf to synchronize socket access this loss occured and I have fallen back to using files for messaging in my scripts. Back then I thought I must have done something wrong, but I cannot think of anything. Obviously an option with disadvantages. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Recent nc(1) changes
On 15/04/2010 21:48, Xin LI wrote: > On 2010/04/15 12:41, Dominic Fandrey wrote: >> On 15/04/2010 21:24, Xin LI wrote: >>> ... > >> I'd say that the data loss (~1%) when I tried to use nc with UNIX sockets >> (on both ends) is much more troublesome than your changes. >> Even when I used lockf to synchronize socket access this loss occured >> and I have fallen back to using files for messaging in my scripts. > > Data loss? Sounds like a bug to me. Do you have any reproduction scripts? No, but I'll put something together over the weekend if you want to look at something. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: Dynamic plists
On 22/04/2010 01:45, Rob Farmer wrote:
> I maintain math/scilab and am preparing to update it. This port has a
> huge plist (slightly under 15000 lines), hundreds of which change
> depending on what options are selected. It is a bit of a pain to
> update. The porters handbook makes vague reference to dynamic plists -
> so I was wondering, would this be a good idea? And if so, what is the
> best way to make one?
You normally base it on the output of
${FIND} -s PATH -type f
${FIND} -d PATH -type d | ${SED} 's,^,@dirrm ,'
Of course there's normally more to it, but that's the basic principle.
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
___
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: Unable to build /lang/ruby18
On 04/04/2010 23:37, Sahil Tandon wrote: > On Sun, 04 Apr 2010, Jerry wrote: > >> I have tried three times in the past 24 hours to build the >> 'lang/ruby18' port without success. This is on a FreeBSD-7.3 machine. >> >> The build log follows: >> >> Script started on Sun Apr 4 03:59:59 2010 >> ===> Found saved configuration for ruby+nopthreads-1.8.7.248,1 > > OK, +nopthreads; but during build: > >> -rpath=/usr/local/lib -pthread -o miniruby rbconfig.rb updated cc > > Odd. FWIW, my lang/ruby18 build log WITHOUT_PTHREADS=yes on 7.3: > > http://pastie.org/903044.txt I had this issue, too. It worked after running 'make rmconfig', because WITHOUT_PTHREADS was stored in the options file and breaking the ports logic. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Error building ruby+nopthreads-1.8.7.248,1
On 28/04/2010 10:55, Paul Macdonald wrote: > > Same error after a cvs update of ports tree and from deinstalling ruby > and an attempted reinstall.. > Adding the newline in version.h didn;t change the final error. > > In file included from version.c:14: > version.h:29:41: warning: no newline at end of file > cc -I/usr/include -O2 -fno-strict-aliasing -pipe -fPIC-DRUBY_EXPORT > -I. -I. -I/usr/include-c dmyext.c > ar rcu libruby18-static.a array.o bignum.o class.o compar.o dir.o > dln.o enum.o enumerator.o error.o eval.o file.o gc.o hash.o > inits.o io.o marshal.o math.o numeric.o object.o pack.o parse.o > process.o prec.o random.o range.o re.o regex.o ruby.o signal.o > sprintf.o st.o string.o struct.o time.o util.o variable.o > version.o dmyext.o > cc -I/usr/include -O2 -fno-strict-aliasing -pipe -fPIC-DRUBY_EXPORT > -I. -I. -I/usr/include-c main.c > cc -I/usr/include -O2 -fno-strict-aliasing -pipe -fPIC-DRUBY_EXPORT > -L. -rpath=/usr/lib:/usr/local/lib -rdynamic main.o > libruby18-static.a -lcrypt -lm -L/usr/lib > -rpath=/usr/lib:/usr/local/lib -o miniruby > libruby18-static.a(process.o)(.text+0xb59): In function `proc_exec_v': > : undefined reference to `rb_thread_stop_timer_fake' > libruby18-static.a(process.o)(.text+0xdc6): In function `rb_proc_exec': > : undefined reference to `rb_thread_stop_timer_fake' > *** Error code 1 > Run 'make rmconfig'. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Error building ruby+nopthreads-1.8.7.248,1
On 28/04/2010 11:34, Paul Macdonald wrote: > Dominic Fandrey wrote: >> On 28/04/2010 10:55, Paul Macdonald wrote: >> >>> Same error after a cvs update of ports tree and from deinstalling ruby >>> and an attempted reinstall.. >>> Adding the newline in version.h didn;t change the final error. >>> >>> In file included from version.c:14: >>> version.h:29:41: warning: no newline at end of file >>> cc -I/usr/include -O2 -fno-strict-aliasing -pipe -fPIC-DRUBY_EXPORT >>> -I. -I. -I/usr/include-c dmyext.c >>> ar rcu libruby18-static.a array.o bignum.o class.o compar.o dir.o >>> dln.o enum.o enumerator.o error.o eval.o file.o gc.o hash.o >>> inits.o io.o marshal.o math.o numeric.o object.o pack.o >>> parse.o process.o prec.o random.o range.o re.o regex.o ruby.o >>> signal.o sprintf.o st.o string.o struct.o time.o util.o >>> variable.o version.o dmyext.o >>> cc -I/usr/include -O2 -fno-strict-aliasing -pipe -fPIC-DRUBY_EXPORT >>> -I. -I. -I/usr/include-c main.c >>> cc -I/usr/include -O2 -fno-strict-aliasing -pipe -fPIC-DRUBY_EXPORT >>> -L. -rpath=/usr/lib:/usr/local/lib -rdynamic main.o >>> libruby18-static.a -lcrypt -lm -L/usr/lib >>> -rpath=/usr/lib:/usr/local/lib -o miniruby >>> libruby18-static.a(process.o)(.text+0xb59): In function `proc_exec_v': >>> : undefined reference to `rb_thread_stop_timer_fake' >>> libruby18-static.a(process.o)(.text+0xdc6): In function `rb_proc_exec': >>> : undefined reference to `rb_thread_stop_timer_fake' >>> *** Error code 1 >>> >>> >> >> Run 'make rmconfig'. >> >> > no difference for me, i'd tried setting pthreads in the make file anyway > so i'm not sure its that. Which version of FreeBSD are you running? What are the contents of /var/db/ports/ruby/options What is the output of # make -VWITHOUT_PTHREADS Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Error building ruby+nopthreads-1.8.7.248,1
On 28/04/2010 13:33, Paul Macdonald wrote: > Dominic Fandrey wrote: >> On 28/04/2010 11:34, Paul Macdonald wrote: >> >>> Dominic Fandrey wrote: >>> >>>> On 28/04/2010 10:55, Paul Macdonald wrote: >>>> >>>> >>>>> Same error after a cvs update of ports tree and from deinstalling ruby >>>>> and an attempted reinstall.. >>>>> Adding the newline in version.h didn;t change the final error. >>>>> >>>>> In file included from version.c:14: >>>>> version.h:29:41: warning: no newline at end of file >>>>> cc -I/usr/include -O2 -fno-strict-aliasing -pipe -fPIC >>>>> -DRUBY_EXPORT >>>>> -I. -I. -I/usr/include-c dmyext.c >>>>> ar rcu libruby18-static.a array.o bignum.o class.o compar.o dir.o >>>>> dln.o enum.o enumerator.o error.o eval.o file.o gc.o hash.o >>>>> inits.o io.o marshal.o math.o numeric.o object.o pack.o >>>>> parse.o process.o prec.o random.o range.o re.o regex.o ruby.o >>>>> signal.o sprintf.o st.o string.o struct.o time.o util.o >>>>> variable.o version.o dmyext.o >>>>> cc -I/usr/include -O2 -fno-strict-aliasing -pipe -fPIC >>>>> -DRUBY_EXPORT >>>>> -I. -I. -I/usr/include-c main.c >>>>> cc -I/usr/include -O2 -fno-strict-aliasing -pipe -fPIC >>>>> -DRUBY_EXPORT >>>>> -L. -rpath=/usr/lib:/usr/local/lib -rdynamic main.o >>>>> libruby18-static.a -lcrypt -lm -L/usr/lib >>>>> -rpath=/usr/lib:/usr/local/lib -o miniruby >>>>> libruby18-static.a(process.o)(.text+0xb59): In function `proc_exec_v': >>>>> : undefined reference to `rb_thread_stop_timer_fake' >>>>> libruby18-static.a(process.o)(.text+0xdc6): In function >>>>> `rb_proc_exec': >>>>> : undefined reference to `rb_thread_stop_timer_fake' >>>>> *** Error code 1 >>>>> >>>>> >>>> Run 'make rmconfig'. >>>> >>>> >>> no difference for me, i'd tried setting pthreads in the make file anyway >>> so i'm not sure its that. >>> >> >> Which version of FreeBSD are you running? >> >> What are the contents of /var/db/ports/ruby/options >> >> What is the output of >> # make -VWITHOUT_PTHREADS >> >> Regards >> >> > > 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Wed Dec 12 18:06:52 UTC 2007 > r...@--:/usr/obj/usr/src/sys/IPFW i386 > #make -VWITHOUT_PTHREADS > no > # > > same problem on > FreeBSD xxx 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 > make -VWITHOUT_PTHREADS > yes WITHOUT_PTHREADS=no and WITHOUT_PTHREADS=yes have exactly the same effect. It appears that the variable is not intended to be set by the user and doing so breaks the internal ports logic. The first thing you should check is whether it is set anywhere in your system, e.g. /etc/make.conf, /etc/src.conf, your environment /var/db/ports/ruby/options ... It shouldn't be in any of these. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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"
xf86-video-intel-2.7.1_2 problem
After a surprisingly smooth update Xorg-7.5 update (good job there) it's time for me to complain about a change in the intel driver. The driver suddenly seems to be hard-coded to come up with 96dpi. This is quite ridiculous as the driver perfectly knows the correct display size: LVDS connected 1440x900+0+0 (normal left inverted right x axis y axis) 304mm x 190mm 1440px / 304mm * 25.4(mm/") ~= 120dpi Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: GSoC: Making ports work with clang
On 03/05/2010 12:38, "C. Bergström" wrote: > What's really the goal here? In my opinion it's about staying away from the GPLv3. According to my understanding of the situation, GPLv3 code is not accepted into the project and that means we're stuck with gcc 4.2, which has already reached its EOL. The way I see it we /desperately/ need a new compiler for the base system. Having GPLv3 stuff in Ports is all right, so getting the base system to compile was the most important step. Now that it does I think the change should be made as soon as all the supported architectures work with clang. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: xf86-video-intel-2.7.1_2 problem
On 02/05/2010 23:56, Dominic Fandrey wrote: > After a surprisingly smooth update Xorg-7.5 update (good job there) > it's time for me to complain about a change in the intel driver. > > The driver suddenly seems to be hard-coded to come up with 96dpi. > This is quite ridiculous as the driver perfectly knows the correct > display size: > LVDS connected 1440x900+0+0 (normal left inverted right x axis y axis) > 304mm x 190mm > 1440px / 304mm * 25.4(mm/") ~= 120dpi This is just wicked, xdpyinfo says: dimensions:1440x900 pixels (381x238 millimeters) resolution:96x96 dots per inch xrandr says: LVDS connected 1440x900+0+0 (normal left inverted right x axis y axis) 304mm x 190mm Of course xrandr is right, that's the values supplied by the screen. I suspect xdpyinfo just takes the pixel dimensions and resolutions and calculates the screen dimensions: 25.4 * 1440 / 96 = 381 Or the intel driver does it. But why should xrandr show the correct values? After running "xrandr --dpi 120" xdpyinfo shows the correct values. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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"
OpenJDK6 not building
I have no idea, why it tries to download something during build, and no idea why it fails to do so. Fetching https://jaxp.dev.java.net/files/documents/913/147491/jdk6-jaxp-2010_01_15.zip manually works fine. But if I do that the file will just be deleted by the build script and it will again try unsuccessfully to get it. -jaxp_src-url-bundle: [echo] Downloading from https://jaxp.dev.java.net/files/documents/913/147491/jdk6-jaxp-2010_01_15.zip [get] Getting: https://jaxp.dev.java.net/files/documents/913/147491/jdk6-jaxp-2010_01_15.zip [get] To: /usr/obj/mobileKamikaze.norad/amd64/usr/ports/java/openjdk6/work/build/bsd-amd64/jaxp/drop/bundles/jdk6-jaxp-2010_01_15.zip.temp [get] Error getting https://jaxp.dev.java.net/files/documents/913/147491/jdk6-jaxp-2010_01_15.zip to /usr/obj/mobileKamikaze.norad/amd64/usr/ports/java/openjdk6/work/build/bsd-amd64/jaxp/drop/bundles/jdk6-jaxp-2010_01_15.zip.temp BUILD FAILED java.net.SocketException: Invalid argument at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:310) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:176) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:163) at java.net.Socket.connect(Socket.java:542) at java.net.Socket.connect(Socket.java:492) at sun.net.NetworkClient.doConnect(NetworkClient.java:174) at sun.net.www.http.HttpClient.openServer(HttpClient.java:409) at sun.net.www.http.HttpClient.openServer(HttpClient.java:530) at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:289) at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:346) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:755) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153) at org.apache.tools.ant.taskdefs.Get.doGet(Get.java:145) at org.apache.tools.ant.taskdefs.Get.execute(Get.java:78) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1189) at org.apache.tools.ant.Main.runBuild(Main.java:758) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) Total time: 0 seconds gmake[1]: *** [all] Error 1 gmake[1]: Leaving directory `/usr/obj/mobileKamikaze.norad/amd64/usr/ports/java/openjdk6/work/jaxp/make' gmake: *** [jaxp-build] Error 2 *** Error code 1 Stop in /usr/ports/java/openjdk6. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: OpenJDK6 not building
On 19/05/2010 10:25, Alex Dupre wrote: > Dominic Fandrey ha scritto: >> I have no idea, why it tries to download something during build, >> and no idea why it fails to do so. > > Theoretically a port should not download anything in the build stage, > but currently the openjdk6 port does it. I don't know why it fails for > you, but I built the port in tinderbox without problems. Have you re-tried? I tried it in three different environments, (NAT, UMTS, University VPN). No clue what causes the exception. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: OpenJDK6 not building
On 19/05/2010 20:10, Olivier Smedts wrote: > 2010/5/19 Dominic Fandrey : >> I have no idea, why it tries to download something during build, >> and no idea why it fails to do so. >> >> Fetching >> https://jaxp.dev.java.net/files/documents/913/147491/jdk6-jaxp-2010_01_15.zip >> manually works fine. But if I do that the file will just be >> deleted by the build script and it will again try unsuccessfully >> to get it. >> >> -jaxp_src-url-bundle: >> [echo] Downloading from >> https://jaxp.dev.java.net/files/documents/913/147491/jdk6-jaxp-2010_01_15.zip >> [get] Getting: >> https://jaxp.dev.java.net/files/documents/913/147491/jdk6-jaxp-2010_01_15.zip >> [get] To: >> /usr/obj/mobileKamikaze.norad/amd64/usr/ports/java/openjdk6/work/build/bsd-amd64/jaxp/drop/bundles/jdk6-jaxp-2010_01_15.zip.temp >> [get] Error getting >> https://jaxp.dev.java.net/files/documents/913/147491/jdk6-jaxp-2010_01_15.zip >> to >> /usr/obj/mobileKamikaze.norad/amd64/usr/ports/java/openjdk6/work/build/bsd-amd64/jaxp/drop/bundles/jdk6-jaxp-2010_01_15.zip.temp >> >> BUILD FAILED >> java.net.SocketException: Invalid argument >>at java.net.PlainSocketImpl.socketConnect(Native Method) >>at >> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:310) >>at >> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:176) >>at >> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:163) >>... >>at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) >> >> Total time: 0 seconds >> gmake[1]: *** [all] Error 1 >> gmake[1]: Leaving directory >> `/usr/obj/mobileKamikaze.norad/amd64/usr/ports/java/openjdk6/work/jaxp/make' >> gmake: *** [jaxp-build] Error 2 >> *** Error code 1 >> >> Stop in /usr/ports/java/openjdk6. > > By any chance do you use "FORCE_MAKE_JOBS=yes" ? > java/openjkd6 should be marked MAKE_JOBS_UNSAFE, it failed last time I > tried with 4 jobs (last time was maybe 3 months ago but I don't think > the port has changed much). # cd /usr/ports/java/openjdk6 # make -VFORCE_MAKE_JOBS # Nope. I'll try to rebuild ant. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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"
OpenArena 0.8.5 port
For those of you interested in playing OpenArena on FreeBSD, I submitted a patch to games/openarena and a shar for OAX (OpenArena Xpanded): http://www.freebsd.org/cgi/query-pr.cgi?pr=146818 Unfortunately I'm not the maintainer so there's no saying if and when this will be committed, so I recommend to apply the patches yourself. Have fun fragging! -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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"
issues unveiled by devel/gettext
Error 1: The configure script of devel/gettext pulls in gawk if installed, which depends on gettext and causes install to fail. Error 2: I updated with "portmaster -Da" so I stumbled over lots of stuff that didn't get version bumped, even though it directly links to gettext. This is the list of packages that miss a direct dependency on devel/gettext and should be version bumped: textproc/libcroco devel/glib20 shells/bash textproc/libxslt security/libgcrypt devel/dbus-glib devel/eggdbus sysutils/polkit devel/libIDL devel/ORBit2 devel/gconf2 devel/gio-fam-backend x11-toolkits/pango devel/gamin x11-toolkits/gtk20 (also links against its old version during build) More missing direct dependencies were uncovered by pkg_libchk: graphics/ImageMagick audio/arts net/avahi-app devel/avr-gcc sysutils/consolekit devel/desktop-file-utils textproc/enchant net-im/farsight2 graphics/gegl graphics/gimp-app print/gimp-gutenprint devel/glibmm devel/gnome-vfs textproc/gsed multimedia/gstreamer-ffmpeg multimedia/gstreamer-plugins multimedia/gstreamer-plugins-bad audio/gstreamer-plugins-cdparanoia multimedia/gstreamer-plugins-dvd audio/gstreamer-plugins-esound audio/gstreamer-plugins-flac devel/gstreamer-plugins-gnomevfs multimedia/gstreamer-plugins-gnonlin graphics/gstreamer-plugins-jpeg audio/gstreamer-plugins-lame multimedia/gstreamer-plugins-good graphics/gstreamer-plugins-libpng audio/gstreamer-plugins-ogg audio/gstreamer-plugins-pulse audio/gstreamer-plugins-shout2 audio/gstreamer-plugins-sndfile multimedia/gstreamer-plugins-ugly audio/gstreamer-plugins-wavpack multimedia/gstreamermm x11-toolkits/gtkglext textproc/gtkspell print/gutenprint-base x11-toolkits/gtkmm24 print/gutenprint-ijs science/hdf5 irc/irssi sysutils/k3b devel/libbonobo x11-toolkits/libbonoboui multimedia/libdv x11/libgnome graphics/libgnomecanvas x11-toolkits/libgnomeui devel/libgsf graphics/liblqr-1 net-im/libnice devel/libnotify graphics/libopenraw net-im/libpurple graphics/librsvg2 devel/libsoup textproc/libwpd textproc/libxml++26 multimedia/mjpegtools audio/mpc textproc/openjade x11-toolkits/pangomm net-im/pidgin graphics/poppler-gtk graphics/pstoedit devel/py-dbus multimedia/py-gstreamer multimedia/smpeg multimedia/vcdimager editors/vim www/webkit-gtk2 net/wireshark Error 3: "make fetch" fails for postgresql related ports prior to the postgresql-client update (not really a gettext issue)! I figure they should all get a FETCH_DEPENDS line. ===>>> Returning to update check of installed ports /libexec/ld-elf.so.1: Shared object "libintl.so.8" not found, required by "pg_config" ===>>> Launching child to update php5-pdo_pgsql-5.3.2 to php5-pdo_pgsql-5.3.2_1 /libexec/ld-elf.so.1: Shared object "libintl.so.8" not found, required by "pg_config" ===>>> Port directory: /usr/ports/databases/php5-pdo_pgsql /libexec/ld-elf.so.1: Shared object "libintl.so.8" not found, required by "pg_config" ===>>> Gathering dependency list for databases/php5-pdo_pgsql from ports /libexec/ld-elf.so.1: Shared object "libintl.so.8" not found, required by "pg_config" ===>>> Starting recursive 'make config' check ===>>> Recursive 'make config' check complete for databases/php5-pdo_pgsql ===>>> Returning to update check of installed ports /libexec/ld-elf.so.1: Shared object "libintl.so.8" not found, required by "pg_config" ===>>> Launching child to update postgresql-server-8.3.11 to postgresql-server-8.3.11_1 /libexec/ld-elf.so.1: Shared object "libintl.so.8" not found, required by "pg_config" ===>>> Port directory: /usr/ports/databases/postgresql83-server /libexec/ld-elf.so.1: Shared object "libintl.so.8" not found, required by "pg_config" /libexec/ld-elf.so.1: Shared object "libintl.so.8" not found, required by "pg_config" /libexec/ld-elf.so.1: Shared object "libintl.so.8" not found, required by "pg_config" /libexec/ld-elf.so.1: Shared object "libintl.so.8" not found, required by "pg_config" -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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"
