Re: dns/djbdns [do-package] Error code 1
On 02/27, Chad J. Milios wrote: root@kakashi:~ # dnscache-conf dnscache dnslog /var/service/dnscache dnscache-conf: fatal: unable to switch to /usr/ports/dns/djbdns/work/stage/usr/local: file does not exist root@kakashi:~ # strings `which dnscache-conf` | grep stage /usr/ports/dns/djbdns/work/stage/usr/local HOWEVER the software works properly ONCE it manages to get installed by the normal `make clean install` method (where i have to try about 15 times with my fingers crossed and by the grace of God it works one of the times) and strings reports no 'stage' anywhere in dnscache-conf Bapt figured it out. The it target included the install target, making prog the more appropriate build target. I'm still rather confused as to why this made the issues timing-sensitive (and apparently only in some environments), but it should work now. Similar issues may be affecting other djb ports; I'll investigate that this week. ___ freebsd-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: dns/djbdns [do-package] Error code 1
On 02/27, Michael Gmelin wrote: I stumbled over the same problem today on 10.0, make NO_STAGE=1 install worked for me on the first attempt though. I can also confirm the problem with dnscache-conf when installing the binary package using pkg install. Can you confirm the exact version you installed via pkg install, including PORTREVISION? I'm not certain about the maintainer situation of the port, if you want me to I could take a closer look at this in a few days. The difficulty here is that the maintainer can't reproduce the problem at all, and I'm not intimately familiar with the internals of stage support. I don't see anything in the port that looks timing-dependent, so I'm not sure where to go. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: dns/djbdns [do-package] Error code 1
Interesting, I can't seem to replicate it here. It doesn't seem like
MAKE_JOBS_UNSAFE would apply, but perhaps try that?
On 02/19, Chad J. Milios wrote:
there seems to be a timing issue. can anyone else please confirm this
problem is happening? I haven't gone ahead and tried any non-default
values of vfs.timestamp_precision.
make package
fails 26/30 times
make sleep 1 make package
succeeds 50/50 times
Thanks in advance.
here is the full output of a failed run:
=== Found saved configuration for djbdns-1.05_14
=== Fetching all distfiles required by djbdns-1.05_17,1 for building
=== Extracting for djbdns-1.05_17,1
= SHA256 Checksum OK for djbdns-1.05.tar.gz.
= SHA256 Checksum OK for djbdns-1.05-man-20031023.tar.gz.
=== Patching for djbdns-1.05_17,1
=== Applying FreeBSD patches for djbdns-1.05_17,1
=== Configuring for djbdns-1.05_17,1
=== Building for djbdns-1.05_17,1
cat warn-auto.sh dnstracesort.sh | sed s}HOME}`head -1 conf-home`}g
dnstracesort
cat warn-auto.sh rts.sh | sed s}HOME}`head -1 conf-home`}g rts
( cat warn-auto.sh; echo 'main=$1; shift'; echo exec `head -1
conf-ld` '-o $main $main.o ${1+$@}' ) load
( cat warn-auto.sh; echo exec `head -1 conf-cc` '-c ${1+$@}' )
compile
chmod 755 dnstracesort
chmod 755 compile
chmod 755 load
chmod 755 rts
( cat warn-auto.sh; echo CC=\'`head -1 conf-cc`\'; echo LD=\'`head -1
conf-ld`\'; cat find-systype.sh; ) | sh systype
cat warn-auto.sh choose.sh | sed s}HOME}`head -1 conf-home`}g choose
./compile alloc.c
./compile alloc_re.c
chmod 755 choose
./compile auto-str.c
auto-str.c:8: warning: conflicting types for built-in function 'puts'
./compile axfrdns-conf.c
./compile buffer.c
./compile buffer_1.c
./compile buffer_2.c
./compile buffer_copy.c
./compile buffer_get.c
./compile buffer_put.c
./compile buffer_read.c
./compile buffer_write.c
./compile byte_chr.c
./compile byte_copy.c
./compile byte_cr.c
./compile byte_diff.c
./compile byte_zero.c
./compile case_diffb.c
./compile case_diffs.c
./compile case_lowerb.c
./compile chkshsgr.c
./compile droproot.c
./compile env.c
./compile error.c
./compile error_str.c
./compile fmt_ulong.c
./compile generic-conf.c
./compile getln.c
./compile getln2.c
./compile hier.c
./compile install.c
./compile instcheck.c
./compile ip4_fmt.c
./compile ip4_scan.c
./compile ndelay_off.c
./compile ndelay_on.c
./compile okclient.c
./compile open_read.c
./compile open_trunc.c
./compile openreadclose.c
./compile pickdns-conf.c
./compile qlog.c
./compile rbldns-conf.c
./compile readclose.c
./compile scan_ulong.c
./compile seek_set.c
./compile sgetopt.c
./compile socket_accept.c
./compile socket_bind.c
./compile socket_conn.c
./compile socket_listen.c
./compile socket_recv.c
./compile socket_send.c
./compile socket_tcp.c
./compile socket_udp.c
./compile str_chr.c
./compile str_diff.c
./compile str_len.c
./compile str_rchr.c
./compile str_start.c
./compile stralloc_cat.c
./compile stralloc_catb.c
./compile stralloc_cats.c
./compile stralloc_copy.c
./compile stralloc_eady.c
./compile stralloc_num.c
./compile stralloc_opyb.c
./compile stralloc_opys.c
./compile stralloc_pend.c
./compile strerr_die.c
./compile strerr_sys.c
./compile subgetopt.c
./compile tinydns-conf.c
./compile uint16_pack.c
./compile uint16_unpack.c
./compile utime.c
./compile walldns-conf.c
( ( ./compile trylsock.c ./load trylsock -lsocket -lnsl ) /dev/null
21 echo -lsocket -lnsl || exit 0 ) socket.lib
( ( ./compile tryulong32.c ./load tryulong32 ./tryulong32 )
/dev/null 21 cat uint32.h2 || cat uint32.h1 ) uint32.h
./choose c trydrent direntry.h1 direntry.h2 direntry.h
rm -f trylsock.o trylsock
./choose clr trypoll iopause.h1 iopause.h2 iopause.h
./choose c trysysel select.h1 select.h2 select.h
./choose clr tryulong64 uint64.h1 uint64.h2 uint64.h
rm -f tryulong32.o tryulong32
( case `cat systype` in sunos-5.*) cat hasdevtcp.h2 ;; *) cat
hasdevtcp.h1 ;; esac ) hasdevtcp.h
( cat warn-auto.sh; echo 'main=$1; shift'; echo 'rm -f $main';
echo 'ar cr $main ${1+$@}'; case `cat systype` in sunos-5.*) ;;
unix_sv*) ;; irix64-*) ;; irix-*) ;; dgux-*) ;; hp-ux-*) ;; sco*)
;; *) echo 'ranlib $main' ;; esac ) makelib
./load chkshsgr
chmod 755 makelib
./compile cdb.c
./compile cdb_hash.c
./compile cdb_make.c
./compile rbldns-data.c
./compile uint32_pack.c
./compile uint32_unpack.c
./makelib alloc.a alloc.o alloc_re.o getln.o getln2.o stralloc_cat.o
stralloc_catb.o stralloc_cats.o stralloc_copy.o stralloc_eady.o
stralloc_num.o stralloc_opyb.o stralloc_opys.o stralloc_pend.o
./makelib buffer.a buffer.o buffer_1.o buffer_2.o buffer_copy.o
buffer_get.o buffer_put.o strerr_die.o strerr_sys.o
./makelib env.a env.o
./makelib getopt.a sgetopt.o subgetopt.o
./makelib unix.a buffer_read.o buffer_write.o error.o error_str.o
ndelay_off.o ndelay_on.o open_read.o open_trunc.o
Re: FreeBSD Port: prosody-0.9.3 IPv6 status.
Hi Kelly, The more testers the better, especially if you have IPv6. The updated luasec and Prosody seem to be working well, but the new luasocket hasn't been extensively tested. Thanks! David On 02/11, Kelly Hays wrote: Thanks for the update. I have a small server with just a couple of users that I could to test with if needed. Thanks, Kelly Hey. The lack of a newer luasocket. David already has a patch for that (luasocket 3.0rc1) and it works (with ipv6 support) on his and my server. So I'd expect to see that limitation go away Real Soon(tm). Thanks to that very responsive maintainer. Ben On Feb 11, 2014 9:19 PM, Kelly Hays kelly.h...@jkhfamily.org wrote: Hello, First I would like to thank you for the work that you put into updating this port. It is good to see it up to date again. I noticed that the pkg message says that IPv6 is not working. Do you know what the issue is? Thanks, Kelly ___ freebsd-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: prosody-0.8.2
On 02/06, Benjamin Podszun wrote: If you can try to coordinate with the luasec and luasocket maintainers ? Actually I think that's a non-issue (now). The comment from lx/the maintainer of prosody claims that s2s is broken (no idea, haven't tried the patch just yet) and wonders if we'd need the forked lua dependencies. Looking at the prosody project page [1] even THEY don't realize that the situation has changed and they still point to [2] as a 'fork just to get a release out'. The luasec bug [3] was closed just a week ago - in other words: luasec proper, the official version, got a new release out and the fork should be irrelevant now. A quick chat with the prosody developers seems to confirm that. Well, that's good, at least. Thanks for investigating. That said: The luasec changes _shouldn't_ break s2s (merely disable some features, such as PFS for TLS for example). I agree! However, I was not able to successfully debug the issue with the Prosody developers. Things may well have changed now, I just want to get things fully in compliance with what the Prosody developers are using, as a test cycle of all of Prosody's functionality is quite time-consuming. So .. this probably now needs a bump for lua51-luasec (which lists no individual maintainer, points to po...@freebsd.org only) from 0.4 to 0.5. How would I approach that? Looking at the port myself and giving it a try? Attaching that to a bug of sorts (similar to the prosody one)? Tell you what -- I'll try to tackle LuaSec. If you can take a look at the Luasocket situation and perhaps bring that up with the maintainer, that'd certainly be useful. Thanks, David ___ freebsd-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: prosody-0.8.2
On 02/06, Benjamin Podszun wrote: Maybe I can help with that - since I plan to migrate/relocate and that's a core part of what I need here (which is why I'm diving into ports about 30min after my first FreeBSD installation in years). So - one tester, ready to help out. ;-) Thanks! Luasocket: Well, can you explain what you mean? Are you talking about luasec including luasocket (and again, in a prerelease 3.x version)? If you could tell me a bit more I'd be happy to invest some time/give it a go. Ugh, I forgot about this part of the mess. So, Prosody says that Luasocket 2 is required, but the new Luasec includes luasocket 3. Do we update the Luasocket port to 3, hosted on its new GitHub repo? Does this mean that the updated Luasec and luasocket ports would actually conflict with each other? If you know or can find those answers, that'd be useful. ___ freebsd-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: Updating the texmaker-3.5.2,2 and texmakerx-2.1_4 ports
I'm afraid I'm going to have to hand this port off, as last time I checked, the update was rather fiddly, and I don't actually use it anymore. Is there anyone who'd like to take ownership? On 07/12, Jerry wrote: Is there any possibility of getting the texmakerx-2.1_4 port, now officially renamed TeXstudio as of 2011-06-15 updated to the new release TeXstudio 2.6.0, released on 2013-06-05. Also, the texmaker-3.5.2,2 port is now at Version 4.0.2 (May 8 2013). Are there any plans to update that port? I have been informed that Texmaker requires QT5, and FreeBSD is not robust enough to handle QT5, hence it cannot be done. If so, then that is a real pity. I use the latest version of TeXstudio on a Windows machine and would like to be able to use it on my FreeBSD one also. I am not really a fan of TexMaker but would use it if TeXstudio was not available. ___ freebsd-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: graphics/shotwell needs a new home
On 04/20, Christoph Moench-Tegeder wrote: Hi, ## David Thiel (l...@freebsd.org): A year or two ago, I fixed up shotwell and took maintainership from gnome@. Unfortunately, the build broke a month ago or so, and it needs some love from someone much more familiar with gnomeisms to make it functional. gnome@ has indicated they don't want it back, for which I can't necessarily blame them. Is there some brave soul that might be willing to adopt it? Is there a volunteer yet? You're the first! If not - I massaged it into a works for me state. I'm just about to file some PRs for upgrading shotwell, if nobody else has already adopted this port, I'll take maintainership. There was a slightly earlier PR (177913) that also was supposed to fix issues as well - it looks like there are a few differences between the two. I'll try to merge those together and make you the maintainer. Thanks! David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
graphics/shotwell needs a new home
Hello, A year or two ago, I fixed up shotwell and took maintainership from gnome@. Unfortunately, the build broke a month ago or so, and it needs some love from someone much more familiar with gnomeisms to make it functional. gnome@ has indicated they don't want it back, for which I can't necessarily blame them. Is there some brave soul that might be willing to adopt it? Thanks, David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
graphics/shotwell needs a new home
Hello, A year or two ago, I fixed up shotwell and took maintainership from gnome@. Unfortunately, the build broke a month ago or so, and it needs some love from someone much more familiar with gnomeisms to make it functional. gnome@ has indicated they don't want it back, for which I can't necessarily blame them. Is there some brave soul that might be willing to adopt it? Thanks, David ___ freebsd-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: py24-wmgeneral-0.1_1
On Tue, May 22, 2007 at 11:26:51PM +0200, Mario Frasca wrote: since something like a year or so I've taken over the project pywmdockapps, previously by Kristoffer Erlandsson. the main web site has changed: it's now hosted on sourceforge. http://pywmdockapps.sourceforge.net I actually rolled a port of the new version last week, not realizing it was a renamed project. It's ready to be put in after the ports freeze ends. I've recently added some more functionality... I'm using it in a few small dockapps, very compact and quite useful. the 'long description' should be corrected, shall I write down an updated version? Certainly, feel free to send one along. Thanks, David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: xorg upgrade plans
So, I've upgraded one more machine, an X60 Tablet, and have run into some issues on this one. First and most important, my ability to use the 1920x1200 resolution has disappeared. I've been using the 915resolution tool to add this mode to the 945GM bios, but Xorg now insists there is no mode of this name. Also, in 7.2, the wacom driver seems to have disappeared. Seems like this is intentional by the Xorg folks, but any suggestions as to where to get a replacement driver would be appreciated. Compositing is also now incredibly slow, much more so than in X11R6. Not a big deal, I don't really need it. Log is at: http://redundancy.redundancy.org/Xorg.0.log Note that I've currently been trying to get Xinerama working, but the same problems appear without Xinerama. Any suggestions or experiences on similar hardware would be welcome. Thanks, David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg7.2 upgrade and glxgears
On Sun, May 13, 2007 at 10:49:45PM +0200, [LoN]Kamikaze wrote: It seems that the WITH_NVIDIA_GL=0 triggers the ifdef statements in yuvrect_client.c. So I suggest this is a bug in the port. Setting WITH_NVIDIA_GL simply shouldn't happen. After fixing the port it builds and installs fine. However, glxgears also reports a failed request. I cannot help but think that mesa with radeon is broken. I get the same problem (I think) with an i945GM: [EMAIL PROTECTED] ~ 755 ] glxgears libGL warning: 3D driver claims to not support visual 0x5b X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 159 (DAMAGE) Minor opcode of failed request: 4 () Serial number of failed request: 37 Current serial number in output stream: 41 With the nvidia driver I was able to disable Damage events, but the i810 driver doesn't seem to have this option... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg7.2 upgrade and glxgears
On Fri, May 18, 2007 at 10:47:58AM -0700, David Thiel wrote: [EMAIL PROTECTED] ~ 755 ] glxgears libGL warning: 3D driver claims to not support visual 0x5b X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 159 (DAMAGE) Minor opcode of failed request: 4 () Serial number of failed request: 37 Current serial number in output stream: 41 With the nvidia driver I was able to disable Damage events, but the i810 driver doesn't seem to have this option... Aha - Option DAMAGE Disable fixes this problem for me. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg7.2 upgrade and glxgears
On Sun, May 13, 2007 at 08:05:18AM +0200, [LoN]Kamikaze wrote: David Thiel wrote: On Sun, May 13, 2007 at 01:42:23AM +0200, [LoN]Kamikaze wrote: After the upgrade I don't have glxgears or glxinfo on my system. Could anyone tell me which port they belong to? graphics/mesa-demos. Thanks a lot for the pointer. It really doesn't look pretty on my system: Hrm, maybe try WITH_NVIDIA_GL=yes? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: xorg 7.2 ready for testing
On Thu, May 10, 2007 at 05:28:17PM -0400, Kris Kennaway wrote: Once we have enough success reports and have dealt with all reported failures, we will proceed with the next stage, which is to import into CVS. I finally finished last night. The only bumps that I had were duplicates in /usr/local and /usr/X11R6 during the mergebase step, which I suspect is normal, and the fact that I had to remove my old .Xauthority file. I think the latter part should be mentioned in the upgrade path. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg7.2 upgrade and glxgears
On Sun, May 13, 2007 at 01:42:23AM +0200, [LoN]Kamikaze wrote: After the upgrade I don't have glxgears or glxinfo on my system. Could anyone tell me which port they belong to? graphics/mesa-demos. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xorg 7.2 index problem
On Fri, May 11, 2007 at 05:35:11PM -0600, Coleman Kane wrote: I have the same error using en_US.UTF-8 Just unsetting LC_CTYPE in the shell doing the portupgrade should fix it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
