Re: Has isc-dhcp31-server-3.1.ESV_1,1 been removed?
2011-10-18 08:28, Doug Barton skrev: On 10/17/2011 23:22, Leslie Jensen wrote: When I do pkg_version -vIL= It returns isc-dhcp31-server-3.1.ESV_1,1 ! Comparison failed I cannot find any mention in UPDATING that the port should be upgraded. How should I handle this? Upgrade to a supported version. I have replaced several old 3.1 servers with net/isc-dhcp42-server without any problems. If you have a very complex setup you'll want to test your dhcpd.conf file on an isolated network of course. Doug Thanks Doug. I'll look into it. /Leslie ___ 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 20111016 and KDE3
On Mon, 17 Oct 2011 20:13:30 +0200 Alberto Villa wrote: > On Mon, Oct 17, 2011 at 7:11 PM, Ion-Mihai Tetcu > wrote: > >> If you have both kdenetwork3 and 4, well, I don't know. You can try > >> proceeding with that step and seeing if kdenetwork3 still works, > >> and report back. I thought it was quite unlikely that people had > >> kdenetwork3 and 4 installed at the same time. Should this be a > >> problem, I'll end up making it optional in kdenetwork4. > > > > Please do, I have them both. > > I have some problems doing it at the moment. rakuco/makc, can you test > a fix for this? > > itetcu: did you try doing the replacement and seeing if kdenetwork3 > still works? No, I'll try sometime this week. -- IOnut ___ 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: Has isc-dhcp31-server-3.1.ESV_1,1 been removed?
On 10/17/2011 23:22, Leslie Jensen wrote: > > When I do > > pkg_version -vIL= > > It returns > > isc-dhcp31-server-3.1.ESV_1,1 ! Comparison failed > > > I cannot find any mention in UPDATING that the port should be upgraded. > > How should I handle this? Upgrade to a supported version. I have replaced several old 3.1 servers with net/isc-dhcp42-server without any problems. If you have a very complex setup you'll want to test your dhcpd.conf file on an isolated network of course. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADSUP]: ports feature freeze starts soon
On Fri, Oct 07, 2011 at 11:20:28AM +0200, Erwin Lansing wrote: > In preparation for 9.0 the ports tree will be in feature freeze > after release candidate 2 (RC2)is released, currently planned for > October 17. > Depending on your timezone, October 17 has come and gone and the ports tree has not frozen yet. As always, we'll follow the actual dates during the release cycle and not the estimated dates in the tentative schedule. A rough guess would be that RC2, and thus the ports feature freeze, will happed at the end of the month, so please take this as a reminder to get anything you want included in the release into the tree as soon as possible. Erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Has isc-dhcp31-server-3.1.ESV_1,1 been removed?
When I do pkg_version -vIL= It returns isc-dhcp31-server-3.1.ESV_1,1 ! Comparison failed I cannot find any mention in UPDATING that the port should be upgraded. How should I handle this? Thanks /Leslie ___ 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 20111016 and net/linphone-base -- can not be built.
Doug Barton writes: > On 10/17/2011 16:09, Chuck Burns wrote: >> On Monday, October 17, 2011 4:33:22 PM Douglas Berry wrote: >>> I found I needed to pkg_delete ortp\* first, >>> then linphone-base buit. >> Yes, this is indeed a working fix. I discovered this earlier as well, but by >> the time I had enough free time to search/mention it, you'd already posted. > > So it sounds like a case for CONFLICTS_BUILD ? I thought ortp was included in linphone (I haven't checked). Perhaps this is just a build system issue (/usr/local/include being used instead of the includes in the tarball, for example)? ___ 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: Does anyone use mail/demime
On 10/17/11 6:04 PM, Glen Barber wrote: >> maildrop, that was often mentioned on official site: >> http://wayback.archive.org/web/*/http://scifi.squawk.com/demime.html >> > > Active development has clearly ceased. > I misread your reply initially, I think. Sorry about that. -- Glen Barber ___ 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: [kde-freebsd] UPDATING 20111016 and net/linphone-base -- can not be built.
On 10/17/2011 16:09, Chuck Burns wrote: > On Monday, October 17, 2011 4:33:22 PM Douglas Berry wrote: >> I found I needed to pkg_delete ortp\* first, >> then linphone-base buit. > Yes, this is indeed a working fix. I discovered this earlier as well, but by > the time I had enough free time to search/mention it, you'd already posted. So it sounds like a case for CONFLICTS_BUILD ? -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [UPDATE] Re: Update on ports on 10.0
On 17. Oct 2011, at 20:51 , Stanislav Sedov wrote: Hi, I shrinked that Cc: list dramatically. > On Mon, 17 Oct 2011 15:35:51 +0300 > Ion-Mihai Tetcu mentioned: > >> >> >> Here's a little status update: >> We iterated through a few -exp runs (basically for ports/161404 -- >> committed and ports/161431 -- skv@ any problem with it?). With those two >> we can build around 7k packages. The majority of the rest can't be built >> because of a few high profile ports that don't package: expat (6581), >> curl (975), jpeg(5057), lcms(1080), libiconv(11180), libltdl(1187), >> libogg(1947), pcre(5737), python27(5935). >> >> http://pointyhat.freebsd.org/errorlogs/i386-10-latest/ >> >> What we'd like to do next is see how many ports we can package after >> individually fixing those above. This will require a few other -exps >> since undoubtedly we'll find other highly-depended-on ports broken that >> weren't tried because of the blockers above. >> > > It doesn't require an exp-run to understand that you won't move much further > with just fixinng these ports. Well, there was a significant update from ~2800 to ~7000 ports by just fixing 2 or 3? I think understanding these and handling them in a well defined manner is a good idea. > patching similar to the patch Ed, Doug and other people proposed. Actually, > that sed one-liner fixed like 99% of the ports in tree, excluding some complex > ones (like GCC). So why not commit that patch as a KNOB to bsd.port.mk like > it was initially proposed and let people use it in individual ports makefiles > to fix them (and portmgr@ can commit the initial bunch of these knobs)? This > is the easiest thing you can do now, and you will be able to abandon it when > the better solution is available (which is unlikely). I think that's what he was saying as a possible next step. If they have the cycles currently while waiting for RC1 to happen let them do it; we are talking in having things within a month not in spring next year already. I would assume that the aforementioned patch might go into the framework, would only be applied if a) OSVERSION>=10... and b) the port has a knob that says "I need this to run". > WRT your "submit upstream" comment, personanlly, I'd argue against this: We damn need it; they need to regen the stuff; it's going to take months if not years to get 80% to that point and a couple of projects might be dead and we might want to use a local patch then but the sed-KNOB is a bandaid that must die again. I would argue that no port must add the KNOB (once it would exist, should it) without having notified upstream. And you might know a lot better than I do but ideally there would be a new official libtool release before that and ideally the libtool people would have by now fixed all the !FreeBSD similar cases... /bz -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. ___ 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: Does anyone use mail/demime
On Tue, 18 Oct 2011, Ruslan Mahmatkhanov wrote: Matthias Andree wrote on 18.10.2011 00:14: Am 17.10.2011 04:00, schrieb Glen Barber: Hi, As it stands now, the mail/demime port has no "upstream", and development seems to have stopped at least 2 years ago. Does anyone use this? If so, would someone like to _become_ "upstream" and revive this piece of software? Otherwise, I'll mark this port as deprecated in 1 week and have it scheduled for removal 1 month afterwards. Do we have a suitable alternative that we can recommend? maildrop, that was often mentioned on official site: http://wayback.archive.org/web/*/http://scifi.squawk.com/demime.html This clamav-users thread talks about using maildrop's reformime along with uudeview (in ports at converters/uudeview). As a non-user of either, I don't know whether that combination replaces demime easily or completely. http://lurker.clamav.net/message/20030814.114335.e5d0c404.en.html ___ 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: [kde-freebsd] UPDATING 20111016 and net/linphone-base -- can not be built.
On Monday, October 17, 2011 4:33:22 PM Douglas Berry wrote: > I found I needed to pkg_delete ortp\* first, > then linphone-base buit. Yes, this is indeed a working fix. I discovered this earlier as well, but by the time I had enough free time to search/mention it, you'd already posted. Chuck Burns ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [UPDATE] Re: Update on ports on 10.0
On Mon, 17 Oct 2011 15:35:51 +0300 Ion-Mihai Tetcu mentioned: > > > Here's a little status update: > We iterated through a few -exp runs (basically for ports/161404 -- > committed and ports/161431 -- skv@ any problem with it?). With those two > we can build around 7k packages. The majority of the rest can't be built > because of a few high profile ports that don't package: expat (6581), > curl (975), jpeg(5057), lcms(1080), libiconv(11180), libltdl(1187), > libogg(1947), pcre(5737), python27(5935). > > http://pointyhat.freebsd.org/errorlogs/i386-10-latest/ > > What we'd like to do next is see how many ports we can package after > individually fixing those above. This will require a few other -exps > since undoubtedly we'll find other highly-depended-on ports broken that > weren't tried because of the blockers above. > It doesn't require an exp-run to understand that you won't move much further with just fixinng these ports. If you want, I and other people can tell you exactly what will break next (libX* being some of them). There's no way you can work this aroun by fixing few ports by hand: virtually any ports using libtool (and I mean using libtool, not having it in depends list) contains an embedded version of it inside "configure" and thus requires patching similar to the patch Ed, Doug and other people proposed. Actually, that sed one-liner fixed like 99% of the ports in tree, excluding some complex ones (like GCC). So why not commit that patch as a KNOB to bsd.port.mk like it was initially proposed and let people use it in individual ports makefiles to fix them (and portmgr@ can commit the initial bunch of these knobs)? This is the easiest thing you can do now, and you will be able to abandon it when the better solution is available (which is unlikely). WRT your "submit upstream" comment, personanlly, I'd argue against this: this is not the upstream maintainer's problem, it the buggy tools they use to generate the configure scripts, so until the fixed version of libtool is available in all major distributions and widely installed, they're not going to replace it or patch locally. Given the debian/ubuntu release schedule, this is not going to happen earlier that 1-2 years from now, and your patches/requests sent could potentially cause them to abandon FreeBSD support altogether requiring a lot of work to maintain which will be totally understandable. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ 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: Does anyone use mail/demime
On 10/17/11 4:19 PM, Ruslan Mahmatkhanov wrote: > Matthias Andree wrote on 18.10.2011 00:14: >> Am 17.10.2011 04:00, schrieb Glen Barber: >>> Hi, >>> >>> As it stands now, the mail/demime port has no "upstream", and >>> development seems to have stopped at least 2 years ago. >>> >>> Does anyone use this? >>> >>> If so, would someone like to _become_ "upstream" and revive this piece >>> of software? >>> >>> Otherwise, I'll mark this port as deprecated in 1 week and have it >>> scheduled for removal 1 month afterwards. >> >> Do we have a suitable alternative that we can recommend? > I don't see one in the Ports tree, but there may be something better that just had not been ported. To be honest, this is part of why I asked if anyone uses it. > maildrop, that was often mentioned on official site: > http://wayback.archive.org/web/*/http://scifi.squawk.com/demime.html > Active development has clearly ceased. -- Glen Barber ___ 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 20111016 and net/linphone-base -- can not be built.
I found I needed to pkg_delete ortp\* first, then linphone-base buit. -- cheers, Douglas ___ 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"
UPDATING 20111016 and net/linphone-base -- can not be built.
Hello, Freebsd-ports. # portmaster -o net/linphone-base ortp ... /bin/sh /usr/local/bin/libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I.. -I../include/ -I/usr/local/include -I.. -I../../oRTP/include -I/usr/local/include -I/usr/local/include/speex -I/usr/local/include -DORTP_INET6 -O2 -pipe -fno-strict-aliasing -Wall -pthread -D_REENTRANT -MT msrtp.lo -MD -MP -MF .deps/msrtp.Tpo -c -o msrtp.lo msrtp.c libtool: compile: cc -DHAVE_CONFIG_H -I. -I.. -I../include/ -I/usr/local/include -I.. -I../../oRTP/include -I/usr/local/include -I/usr/local/include/speex -I/usr/local/include -DORTP_INET6 -O2 -pipe -fno-strict-aliasing -Wall -pthread -D_REENTRANT -MT msrtp.lo -MD -MP -MF .deps/msrtp.Tpo -c msrtp.c -fPIC -DPIC -o .libs/msrtp.o In file included from ../include/mediastreamer2/msrtp.h:25, from msrtp.c:20: ../include/mediastreamer2/ice.h:60: error: expected specifier-qualifier-list before 'UInt96' msrtp.c: In function 'receiver_process': msrtp.c:333: warning: implicit declaration of function 'rtp_get_payload' gmake[5]: *** [msrtp.lo] Error 1 ... ===>>> make failed for net/linphone-base ===>>> Aborting update ... # uname -a FreeBSD blob.home.serebryakov.spb.ru 8.2-STABLE FreeBSD 8.2-STABLE #23: Mon Oct 3 22:43:14 MSD 2011 l...@blob.home.serebryakov.spb.ru:/usr/obj/usr/src/sys/BLOB amd64 # -- // Black Lion AKA Lev Serebryakov ___ 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: What is wrong here?
2011-10-17 22:13, Matthias Andree skrev: Am 17.10.2011 22:10, schrieb Leslie Jensen: I have a script that does portsnap fetch update pkg_version -vIL= on a Daily basis Today I got this little message about "corrupted record" and I would like to solve it ImageMagick-6.7.3.0_1
Re: audio/cdparanoia broken on -CURRENT, and probably on 9.0
On Sun, Oct 16, 2011 at 15:20:22 -0700, Kevin Oberman wrote: > On Tue, Oct 11, 2011 at 9:00 PM, Kevin Oberman wrote: > > On Tue, Oct 11, 2011 at 8:33 PM, Kenneth D. Merry wrote: > >> On Tue, Oct 11, 2011 at 15:52:35 -0700, Kevin Oberman wrote: > >>> > On Fri, Oct 07, 2011 at 03:46:22 -0400, b. f. wrote: > >>> > > Just a note to say that recent changes on -CURRENT (r225950, meaning > >>> > > that it is probably broken on 9.0 after r226067) have broken > >>> > > audio/cdparanoia, and it should be fixed or marked as BROKEN there. ?I > >>> > > haven't filed a PR, or attempted to patch it yet -- I think that it > >>> > > would be worthwhile to look into moving to 10.2, which has a large > >>> > > number of improvements, although suffering from some Linuxisms. > >>> > > >>> > This will be easy to patch, using one of two methods: > >>> > > >>> > ?- change struct scsi_sense_data to struct scsi_sense_data_fixed > >>> > or, better yet: > >>> > ?- use scsi_extract_sense_len(), which will work for fixed or > >>> > descriptor sense. > >>> > >>> Ken, > >>> > >>> OK. I have grepped through all of the cdparanoia sources and fine no > >>> instances of scsi_sense_data. Where in the heck do I find it so I can > >>> get this port built? 10.2 would be lovely, but I just need cdparanoia > >>> on 9-stable quickly and I fear that hte package will no longer work > >>> after r226067. > >> > >> There is no FreeBSD support in cdparanoia by default. ?It is patched in by > >> the ports system. > >> > >> Go into the directory for the port, do a 'make fetch' and then 'make > >> patch'. > >> > >> Then go into cdparanoia-III-alpha9.8/interface and copy the attached file > >> on top of scsi_interface.c. > >> > >> I've checked that it compiles on a system running code before the change, > >> but I think that change should work for systems before or after the change. > >> > >> Let me know whether it works for you. > > > > Thanks so much! > > > > Yes, the new scsi_interface.c compiled cleanly and cdparanoia built > > and installed. > > > > I am in the process of re-building all ports after I upgraded my > > system to 9-stable, so I really can't plug in my CD and try ripping > > aomething right now, but I'll try soonand let you know how it worked. > > Finally got all of my ports installed and re-booted with the DVD > installed. Sorry to have taken so long, but rebuilding over 1600 ports > on an old, slow laptop takes a lot of time and I had to tweak several > port to get them to build. > > With the modified scsi_interface.c file you sent, cdparanoia seems to > be working just fine. > > Thanks! Great, glad to hear it! > Should I submit a PR with the new file? Yes. I'm not a ports committer, it would be better for one of them (ideally the mantainer, if any) to go in and fix it. Ken -- Kenneth Merry k...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Does anyone use mail/demime
Matthias Andree wrote on 18.10.2011 00:14: Am 17.10.2011 04:00, schrieb Glen Barber: Hi, As it stands now, the mail/demime port has no "upstream", and development seems to have stopped at least 2 years ago. Does anyone use this? If so, would someone like to _become_ "upstream" and revive this piece of software? Otherwise, I'll mark this port as deprecated in 1 week and have it scheduled for removal 1 month afterwards. Do we have a suitable alternative that we can recommend? maildrop, that was often mentioned on official site: http://wayback.archive.org/web/*/http://scifi.squawk.com/demime.html -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: Does anyone use mail/demime
Am 17.10.2011 04:00, schrieb Glen Barber: > Hi, > > As it stands now, the mail/demime port has no "upstream", and > development seems to have stopped at least 2 years ago. > > Does anyone use this? > > If so, would someone like to _become_ "upstream" and revive this piece > of software? > > Otherwise, I'll mark this port as deprecated in 1 week and have it > scheduled for removal 1 month afterwards. Do we have a suitable alternative that we can recommend? ___ 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: What is wrong here?
Am 17.10.2011 22:10, schrieb Leslie Jensen: > > I have a script that does > > portsnap fetch update > > pkg_version -vIL= > > on a Daily basis > > > Today I got this little message about "corrupted record" and I would > like to solve it > > > ImageMagick-6.7.3.0_1 < needs updating (index has 6.7.3.1) > pkg_version: corrupted record (pkgdep line without argument), ignoring > pkg_version: corrupted record (pkgdep line without argument), ignoring > kdemultimedia-4.6.5 < needs updating (index has 4.7.2) > libgtop-2.28.3_1 < needs updating (index has 2.28.3_2) > > > Any suggestions? It might help to run: portmaster --check-depends and the corruption is either from a file system corruption (like: hard shutdown/power blackout with enabled write caches), or from an interrupted portmaster/portupgrade/portinstall or "bare-bones" ports make run. ___ 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"
What is wrong here?
I have a script that does portsnap fetch update pkg_version -vIL= on a Daily basis Today I got this little message about "corrupted record" and I would like to solve it ImageMagick-6.7.3.0_1 < needs updating (index has 6.7.3.1) pkg_version: corrupted record (pkgdep line without argument), ignoring pkg_version: corrupted record (pkgdep line without argument), ignoring kdemultimedia-4.6.5 < needs updating (index has 4.7.2) libgtop-2.28.3_1 < needs updating (index has 2.28.3_2) Any suggestions? Thanks /Leslie ___ 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 10.0-CURRENT: messed up the ports and system (gcc46 won't compile) and need to repair - how?
> > Did you rebuild ports/devel/binutils after change to 10.0 current. > > I was having same problem with gcc45 , then i rebuilt binutils with uname_r > > 9.0-Current and it went away. > > The most recent update to gcc46 also missed the shared library version > bump of mpfr to mpfr.so.5, I've had issues with mpfr and other libraries as a result of autoconf bugs. Notably, they use the glob 'freebsd1*' to identify FreeBSD 1.X, and therefore they assume that shared libraries aren't supported. I hope the fix for that isn't too painful. Apologies for In-reply-to munging; I'm not subscribed. ___ 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 20111016 and KDE3
On Mon, Oct 17, 2011 at 7:11 PM, Ion-Mihai Tetcu wrote: >> If you have both kdenetwork3 and 4, well, I don't know. You can try >> proceeding with that step and seeing if kdenetwork3 still works, and >> report back. I thought it was quite unlikely that people had >> kdenetwork3 and 4 installed at the same time. Should this be a >> problem, I'll end up making it optional in kdenetwork4. > > Please do, I have them both. I have some problems doing it at the moment. rakuco/makc, can you test a fix for this? itetcu: did you try doing the replacement and seeing if kdenetwork3 still works? -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla ___ 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 20111016 and KDE3
On Mon, 17 Oct 2011 10:08:57 +0200 Alberto Villa wrote: > On Mon, Oct 17, 2011 at 9:15 AM, Andrea Venturoli > wrote: > > Using KDE3, I have ortp as a dependency of kdenetwork. > > Should I follow the above or is it ok only for KDE4? > > Is it needed? Would it harm anything? > > linphone-base is required by kdenetwork4, if you don't have it you can > skip that line. I'll add it to UPDATING, thanks. > > If you have both kdenetwork3 and 4, well, I don't know. You can try > proceeding with that step and seeing if kdenetwork3 still works, and > report back. I thought it was quite unlikely that people had > kdenetwork3 and 4 installed at the same time. Should this be a > problem, I'll end up making it optional in kdenetwork4. Please do, I have them both. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
[UPDATE] Re: Update on ports on 10.0
On Tue, 11 Oct 2011 08:36:03 +0200 Erwin Lansing wrote: > Since the release has been pushed back some more since the last mail, > we do have some time to test a possible fix for the issues we're > seeing with libtool on FreeBSD 10.0. However, fixing libtool is only > part of the problem as hundreds, if not thousands, of ports roll > their own detection and need to be fixed individually. We are > currently running a fixed libtool (ports/161404) to assess how many > ports are fixed by this patch and how many need to be patches > manually before deciding how to move forward. Other options include > the big find/grep/awk solution that has been posted several times and > fiddling with uname to go to FreeBSD 9.99 for a while, while ports > can be fixed. > > Hopefully, we can move forward in a day or two, but needless to say > this needs a lot of testing both on 10.0 and earlier releases so we > are sure we don't break backwards compatability, especially on 9.0 > that is soon to be released. For those that cannot wait a few days, > several patches have been proposed on the lists, of which dougb's > seems most complete, so I recommend applying one of those locally. > Please note that these are not tested widely and may break when the > final fix is committed. > > To conclude with some "fun" facts, only 232 ports break on HEAD > currently. Unfortunately, some of these are pretty high profile and > prevent almost 19.000 other ports from building, leaving only slighty > more than 3000 ports to build successfully. Here's a little status update: We iterated through a few -exp runs (basically for ports/161404 -- committed and ports/161431 -- skv@ any problem with it?). With those two we can build around 7k packages. The majority of the rest can't be built because of a few high profile ports that don't package: expat (6581), curl (975), jpeg(5057), lcms(1080), libiconv(11180), libltdl(1187), libogg(1947), pcre(5737), python27(5935). http://pointyhat.freebsd.org/errorlogs/i386-10-latest/ What we'd like to do next is see how many ports we can package after individually fixing those above. This will require a few other -exps since undoubtedly we'll find other highly-depended-on ports broken that weren't tried because of the blockers above. Depending on this number and how long the whole process will take, we can decide what solution to adopt. If possible we'd like to avoid the big hammer of an uname fiddle or find/grep/sed/... (which most probably won't work for all ports anyway, irrespective of how smart it will be). If we need to adopt one of these hacks, it will be via some conditional KNOB in each port Makefile, in order to have an easy way to know which ports are fixed and which not, and an easy way to turn it off for test builds without it in the future. Basically we do not want to shove the dirt under the carpet, were it will rot for years. YOU can help by sending portmgr@ patches for above ports (or any other you know is broken) for the next -exp run. And PLEASE, pretty please once you have a patch that fixes this problem submit it upstream and bug upstream about it. (committers: please check this is the case when committing a patch from a PR). Thanks! -- IOnut ___ 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: About games/flightgear-aircrafts
On 17 Oct 2011 13:17, "Ganael LAPLANCHE" wrote: > > On Mon, 17 Oct 2011 13:10:26 +0100, Chris Rees wrote > > Hi Chris, > > > If you haven't committed it yet, can you please drop the 's' > > from aircraft? > > Yep, I am aware of that typo (Warren Block has > previously reported that in a previous mail) ; it's on my TODO list. > > Once the "limited" aircraft list is committed (and 9.0 released), I'll > ask for a repocopy from : > > games/flightgear-aircrafts => games/flightgear-aircraft > > I'll then change PORTNAME. > > Meanwhile, my awaiting patch already includes COMMENT/pkg-descr fixes. > > Best regards, > Thank you! Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Ports maintrainer mode?
On Sun, Oct 16, 2011 at 11:46:01PM +1100, Alexey Golodov wrote: > Looking through the ports, I see that sometimes maintrainers include in > Makefile block with actions for maintrain port. > There are different ways to define it (starting with MAINTRAINER_MODE in > devel/git, and ends if user = $maintrainer_username) The latter strikes me as a very bad idea. Do you happen to know which ports do that? -- WXS ___ 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: flashplugin does not work anymore
On 17/10/2011 12:25, Luchesar V. ILIEV wrote: On 17/10/2011 13:10, David Demelier wrote: Hello, My flash plugin has been broken a few days ago, now each time I try to access a flash content I can see the following output: (npviewer.bin:2177): Gtk-WARNING **: cannot open display: :0 *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client connection NOTE: child process received `Goodbye', closing down I use the latest linux-f10-flashplugin-10.3r183.10 version. Do you have any idea? Cheers, It looks exactly like the problem introduced with the last patch to the base system... http://security.freebsd.org/advisories/FreeBSD-SA-11:05.unix.asc "The patch provided with the initial version of this advisory exposed the pre-existing bug in FreeBSD's linux emulation code, resulting in attempts to use UNIX sockets from linux applications failing. The most common instance where UNIX sockets were used by linux applications is in the context of the X windowing system, including the widely used linux "flash" web browser plugin." So, perform whatever type of updating you typically use to apply the fixed patch. HTH, Luchesar Forget my last message, I restarted firefox and it works. Thanks -- David Demelier ___ 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: flashplugin does not work anymore
On 17/10/2011 12:25, Luchesar V. ILIEV wrote: On 17/10/2011 13:10, David Demelier wrote: Hello, My flash plugin has been broken a few days ago, now each time I try to access a flash content I can see the following output: (npviewer.bin:2177): Gtk-WARNING **: cannot open display: :0 *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client connection NOTE: child process received `Goodbye', closing down I use the latest linux-f10-flashplugin-10.3r183.10 version. Do you have any idea? Cheers, It looks exactly like the problem introduced with the last patch to the base system... http://security.freebsd.org/advisories/FreeBSD-SA-11:05.unix.asc "The patch provided with the initial version of this advisory exposed the pre-existing bug in FreeBSD's linux emulation code, resulting in attempts to use UNIX sockets from linux applications failing. The most common instance where UNIX sockets were used by linux applications is in the context of the X windowing system, including the widely used linux "flash" web browser plugin." So, perform whatever type of updating you typically use to apply the fixed patch. HTH, Luchesar I have updated my RELENG_8 src/ and rebuild my kernel but it does not change anything. Cheers, -- David Demelier ___ 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: About games/flightgear-aircrafts
On 17/10/2011 15:16, Luchesar V. ILIEV wrote: > On 17/10/2011 15:10, Chris Rees wrote: >> On 17 Oct 2011 10:09, "Ganael LAPLANCHE" >> wrote: >>> >>> On Fri, 14 Oct 2011 12:53:11 +0200, Alexey Shuvaev wrote >>> >>> Hi Alexey, >>> I don't know which aircraft are in the "base" package (flightgear-data), but IMHO: * harrier : British Aerospace Harrier is something known and interesting (vertical takeoff/landing), * il2 : Ilyoushin IL-2 is also quite famous WWII attack plane and * wrightFlyer1903 : 1903 Wright Flyer is must have :) >>> >>> They are not included in flightgear-data, so I'll add them to the "new" >>> flightgear-aircrafts port. >>> >>> Thanks for your feedback, >>> >> >> If you haven't committed it yet, can you please drop the 's' from aircraft? > > I guess he meant the new version, as the games/flightgear-aircrafts port > itself has been around since 2005. Oops, sorry, haven't realized it wasn't quite correct. :) L. ___ 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: About games/flightgear-aircrafts
On Mon, 17 Oct 2011 13:10:26 +0100, Chris Rees wrote Hi Chris, > If you haven't committed it yet, can you please drop the 's' > from aircraft? Yep, I am aware of that typo (Warren Block has previously reported that in a previous mail) ; it's on my TODO list. Once the "limited" aircraft list is committed (and 9.0 released), I'll ask for a repocopy from : games/flightgear-aircrafts => games/flightgear-aircraft I'll then change PORTNAME. Meanwhile, my awaiting patch already includes COMMENT/pkg-descr fixes. Best regards, -- Ganael LAPLANCHE http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac , http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: About games/flightgear-aircrafts
On 17/10/2011 15:10, Chris Rees wrote: > On 17 Oct 2011 10:09, "Ganael LAPLANCHE" > wrote: >> >> On Fri, 14 Oct 2011 12:53:11 +0200, Alexey Shuvaev wrote >> >> Hi Alexey, >> >>> I don't know which aircraft are in the "base" package >>> (flightgear-data), but IMHO: >>> * harrier : British Aerospace Harrier is something known and >>> interesting (vertical takeoff/landing), >>> * il2 : Ilyoushin IL-2 is also quite famous WWII attack plane and >>> * wrightFlyer1903 : 1903 Wright Flyer is must have :) >> >> They are not included in flightgear-data, so I'll add them to the "new" >> flightgear-aircrafts port. >> >> Thanks for your feedback, >> > > If you haven't committed it yet, can you please drop the 's' from aircraft? I guess he meant the new version, as the games/flightgear-aircrafts port itself has been around since 2005. http://www.freshports.org/games/flightgear-aircrafts/ Cheers, Luchesar ___ 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 20111016 and KDE3
2011/10/17 Leslie Jensen : > > > 2011-10-17 10:20, Andrea Venturoli skrev: >> >> On 10/17/11 10:08, Alberto Villa wrote: > > > > > I've got another problem with this update! Kdelibs wont build. > > I followed the instructions in UPDATE. > > > [ 56%] Building CXX object kio/CMakeFiles/kio.dir/kio/ksambasharedata.o > [ 56%] Building CXX object kio/CMakeFiles/kio.dir/bookmarks/kbookmark.o > In file included from > /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:33: > /usr/local/include/qdatetime.h:51: error: function definition does not > declare parameters > /usr/local/include/qdatetime.h:123: error: function definition does not > declare parameters > /usr/local/include/qdatetime.h:184: error: function definition does not > declare parameters > /usr/local/include/qdatetime.h:241: error: expected initializer before '&' > token > /usr/local/include/qdatetime.h:242: error: expected initializer before '&' > token > /usr/local/include/qdatetime.h:243: error: expected initializer before '&' > token > /usr/local/include/qdatetime.h:244: error: expected initializer before '&' > token > /usr/local/include/qdatetime.h:245: error: expected initializer before '&' > token > /usr/local/include/qdatetime.h:246: error: expected initializer before '&' > token > /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc: In > member function 'void KBookmark::updateAccessMetadata()': > /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:548: > error: incomplete type 'QDateTime' used in nested name specifier > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 1 > > Stop in /usr/ports/x11/kdelibs4. > > ===>>> make failed for x11/kdelibs4 > ===>>> Aborting update > > > I need help to solve this. > > Thanks > > /Leslie > > > > > > > ___ > 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" > Just a me to, but my error is slightly different. /usr/local/include/qdatetime.h:51: error: function definition does not declare parameters /usr/local/include/qdatetime.h:123: error: function definition does not declare parameters /usr/local/include/qdatetime.h:184: error: function definition does not declare parameters /usr/local/include/qdatetime.h:241: error: expected initializer before '&' token /usr/local/include/qdatetime.h:242: error: expected initializer before '&' token /usr/local/include/qdatetime.h:243: error: expected initializer before '&' token /usr/local/include/qdatetime.h:244: error: expected initializer before '&' token /usr/local/include/qdatetime.h:245: error: expected initializer before '&' token /usr/local/include/qdatetime.h:246: error: expected initializer before '&' token /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc: In member function 'void KBookmark::updateAccessMetadata()': /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:548: error: incomplete type 'QDateTime' used in nested name specifier *** Error code 1 In file included from /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmarkimporter.cc:28: /usr/local/include/qtextcodec.h:51: error: function definition does not declare parameters /usr/local/include/qtextcodec.h:57: error: function definition does not declare parameters /usr/local/include/qtextcodec.h:63: error: function definition does not declare parameters /usr/local/include/qtextcodec.h:125: error: invalid use of incomplete type 'struct QTextCodec' /usr/local/include/qt4/QtCore/qstring.h:95: error: forward declaration of 'struct QTextCodec' /usr/local/include/qtextcodec.h:126: error: invalid use of incomplete type 'struct QTextCodec' /usr/local/include/qt4/QtCore/qstring.h:95: error: forward declaration of 'struct QTextCodec' /usr/local/include/qtextcodec.h:127: error: invalid use of incomplete type 'struct QTextCodec' /usr/local/include/qt4/QtCore/qstring.h:95: error: forward declaration of 'struct QTextCodec' /usr/local/include/qtextcodec.h:128: error: invalid use of incomplete type 'struct QTextCodec' /usr/local/include/qt4/QtCore/qstring.h:95: error: forward declaration of 'struct QTextCodec' *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 1 Stop in /usr/ports/x11/kdelibs4. ===>>> make failed for x11/kdelibs4 ===>>> Aborting update ===>>> Update for x11/kdelibs4 failed ===>>> Aborting update ===>>> Update for multimedia/kdemultimedia4 failed ===>>> Aborting update after a portmaster -d -a regards Johan ___ 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: About games/flightgear-aircrafts
On 17 Oct 2011 10:09, "Ganael LAPLANCHE" wrote: > > On Fri, 14 Oct 2011 12:53:11 +0200, Alexey Shuvaev wrote > > Hi Alexey, > > > I don't know which aircraft are in the "base" package > > (flightgear-data), but IMHO: > > * harrier : British Aerospace Harrier is something known and > > interesting (vertical takeoff/landing), > > * il2 : Ilyoushin IL-2 is also quite famous WWII attack plane and > > * wrightFlyer1903 : 1903 Wright Flyer is must have :) > > They are not included in flightgear-data, so I'll add them to the "new" > flightgear-aircrafts port. > > Thanks for your feedback, > If you haven't committed it yet, can you please drop the 's' from aircraft? Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description f ports/161705devel/tortoisehg1: does not work with current devel/me o ports/161701New port: games/chocolate-doom Doom port o ports/161700[MAINTAINER] Replace a dead MASTER_SITE in several por o ports/161698New port databases/pecl-mysqlnd_ms o ports/161697[maintainer] [patch] editors/texmacs Update to 1.0.7.1 o ports/161696[maintainer] [patch] java/jrosetta Update to 1.0.4 o ports/161695[patch] devel/mspdebug update to 0.17 f ports/161694sysutils/dvd+rw-tools: growisofs fails to close disc o ports/161690New port: games/prboom-plus Port of ID Software's Doom f ports/161689net/nss-pam-ldapd doesn't honor PREFIX -- DANGEROUS fo o ports/161678New port: sysutils/acpi_call kernle module for calling o ports/161671[MAINTAINER] databases/cassandra: update to 0.8.7 o ports/161660Update port: net-im/icb o ports/161659Update port: games/battalion to 1.4b o ports/161658Update port: x11/dynamag o ports/161657Update port: audio/libgig o ports/161655Update port: security/clamtk to 4.35 o ports/161654Update port: devel/tla o ports/161653Update port: astro/pp3 o ports/161652Update port: devel/dotconf to 1.3 o ports/161651Update port: net/ldapsdk to 6.0.7 o ports/161649Update port: emulators/osmose to 0.9.96 o ports/161648Update port: converters/uudeview o ports/161647Update port: emulators/visualos o ports/161646Update port: audio/mctoolame-decoder o ports/161645Update port: audio/qsampler o ports/161644Update port: www/netsurf to 2.8 o ports/161643Update port: sysutils/namefix to 4.0.2 o ports/161642Update port: www/ffproxy o ports/161641Update port: devel/vtcl o ports/161640Update port: games/awele o ports/161639Update port: net-mgmt/flow-extract o ports/161638Update port: graphics/pstoedit to 3.60 o ports/161637Update port: multimedia/ogmrip to 0.13.7 o ports/161636Update port: games/bogged o ports/161635Update port: misc/tkman o ports/161634Update port: net/sl2tps to 0.4.2 o ports/161633Update port: net-mgmt/TkTopNetFlows o ports/161632Update port: audio/splaytk o ports/161630Update port: net-mgmt/netxms to 1.0.12 o ports/161629Update port: converters/xdeview o ports/161628Update port: graphics/xmms-gdancer o ports/161627Update port: devel/SpecTcl to 1.2.2a o ports/161625Update port: x11-wm/sawfish to 1.8.2 o ports/161624Update port: audio/fmit o ports/161623Update port: audio/timemachine o ports/161622Update port: misc/tkrunit o ports/161620Update port: games/tksol o ports/161619Update port: graphics/qslim o ports/161618Update port: graphics/glfw o ports/161616Update port: audio/qjackctl o ports/161615Update port: astro/planets o ports/161614Update port: databases/xmbase-grok o ports/161612Update port: misc/tkinfo o ports/161611Update port: audio/liblscp o ports/161610Update port: devel/noweb o ports/161609Update port: audio/discid o ports/161607Update port: deskutils/superswitcher to 0.6 o ports/161606Update port: textproc/roap o ports/161604Update port: audio/mctoolame-encoder o ports/161603Update port: audio/lv2core o ports/161602Update port: devel/gengetopt to 2.22.5 o ports/161601Update port: security/openfwtk o ports/161600Update port: devel/pccts to 1.33.33 o ports/161599Update port: graphics/agg o ports/161598Update port: graphics/togl o ports/161597Update port: www/august o ports/161596Update port: lang/bigloo to 3.7a o ports/161594Update port: x11/wmbutton o ports/161593Update port: math/xplot o ports/161592Update port: sysutils/cdargs o ports/161591[patch] audio/xmms2: workaround deadlock in waf (showi o ports/161578devel/strace is not working f ports/161570deskutils/vym: [UPDATE] to 1.99.0 f ports/161569[MAINTAINER] audio/libaacplus: aacplus.h has comma at o ports/161544graphics/ImageMa
Re: flashplugin does not work anymore
On 17/10/2011 13:10, David Demelier wrote: > Hello, > > My flash plugin has been broken a few days ago, now each time I try to > access a flash content I can see the following output: > > (npviewer.bin:2177): Gtk-WARNING **: cannot open display: :0 > *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC > client connection > NOTE: child process received `Goodbye', closing down > > I use the latest linux-f10-flashplugin-10.3r183.10 version. > > Do you have any idea? > > Cheers, > It looks exactly like the problem introduced with the last patch to the base system... http://security.freebsd.org/advisories/FreeBSD-SA-11:05.unix.asc "The patch provided with the initial version of this advisory exposed the pre-existing bug in FreeBSD's linux emulation code, resulting in attempts to use UNIX sockets from linux applications failing. The most common instance where UNIX sockets were used by linux applications is in the context of the X windowing system, including the widely used linux "flash" web browser plugin." So, perform whatever type of updating you typically use to apply the fixed patch. HTH, Luchesar -- i.dea.is/luchesar ___ 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 20111016 and KDE3
2011-10-17 10:20, Andrea Venturoli skrev: On 10/17/11 10:08, Alberto Villa wrote: I've got another problem with this update! Kdelibs wont build. I followed the instructions in UPDATE. [ 56%] Building CXX object kio/CMakeFiles/kio.dir/kio/ksambasharedata.o [ 56%] Building CXX object kio/CMakeFiles/kio.dir/bookmarks/kbookmark.o In file included from /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:33: /usr/local/include/qdatetime.h:51: error: function definition does not declare parameters /usr/local/include/qdatetime.h:123: error: function definition does not declare parameters /usr/local/include/qdatetime.h:184: error: function definition does not declare parameters /usr/local/include/qdatetime.h:241: error: expected initializer before '&' token /usr/local/include/qdatetime.h:242: error: expected initializer before '&' token /usr/local/include/qdatetime.h:243: error: expected initializer before '&' token /usr/local/include/qdatetime.h:244: error: expected initializer before '&' token /usr/local/include/qdatetime.h:245: error: expected initializer before '&' token /usr/local/include/qdatetime.h:246: error: expected initializer before '&' token /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc: In member function 'void KBookmark::updateAccessMetadata()': /usr/ports/x11/kdelibs4/work/kdelibs-4.7.2/kio/bookmarks/kbookmark.cc:548: error: incomplete type 'QDateTime' used in nested name specifier *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 1 Stop in /usr/ports/x11/kdelibs4. ===>>> make failed for x11/kdelibs4 ===>>> Aborting update I need help to solve this. Thanks /Leslie ___ 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"
flashplugin does not work anymore
Hello, My flash plugin has been broken a few days ago, now each time I try to access a flash content I can see the following output: (npviewer.bin:2177): Gtk-WARNING **: cannot open display: :0 *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client connection NOTE: child process received `Goodbye', closing down I use the latest linux-f10-flashplugin-10.3r183.10 version. Do you have any idea? Cheers, -- David Demelier ___ 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: About games/flightgear-aircrafts
On Fri, 14 Oct 2011 12:53:11 +0200, Alexey Shuvaev wrote Hi Alexey, > I don't know which aircraft are in the "base" package > (flightgear-data), but IMHO: > * harrier : British Aerospace Harrier is something known and > interesting (vertical takeoff/landing), > * il2 : Ilyoushin IL-2 is also quite famous WWII attack plane and > * wrightFlyer1903 : 1903 Wright Flyer is must have :) They are not included in flightgear-data, so I'll add them to the "new" flightgear-aircrafts port. Thanks for your feedback, Best regards, -- Ganael LAPLANCHE http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac , http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: UPDATING 20111016 and KDE3
On 10/17/11 10:08, Alberto Villa wrote: On Mon, Oct 17, 2011 at 9:15 AM, Andrea Venturoli wrote: Using KDE3, I have ortp as a dependency of kdenetwork. Should I follow the above or is it ok only for KDE4? Is it needed? Would it harm anything? linphone-base is required by kdenetwork4, if you don't have it you can skip that line. I'll add it to UPDATING, thanks. If you have both kdenetwork3 and 4, well, I don't know. You can try proceeding with that step and seeing if kdenetwork3 still works, and report back. I thought it was quite unlikely that people had kdenetwork3 and 4 installed at the same time. Should this be a problem, I'll end up making it optional in kdenetwork4. Thanks for the answer. In fact I have only kdenetwork3 and I don't plan on installing kdenetwork4 for the time being. So I'll just skip this step and stick with ortp. bye & Thanks av. ___ 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 20111016 and KDE3
On 10/17/11 10:08, Alberto Villa wrote: On Mon, Oct 17, 2011 at 9:15 AM, Andrea Venturoli wrote: Using KDE3, I have ortp as a dependency of kdenetwork. Should I follow the above or is it ok only for KDE4? Is it needed? Would it harm anything? linphone-base is required by kdenetwork4, if you don't have it you can skip that line. I'll add it to UPDATING, thanks. If you have both kdenetwork3 and 4, well, I don't know. You can try proceeding with that step and seeing if kdenetwork3 still works, and report back. I thought it was quite unlikely that people had kdenetwork3 and 4 installed at the same time. Should this be a problem, I'll end up making it optional in kdenetwork4. ___ 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: New Port for ACE-6.0.4
--On October 17, 2011 8:19:23 +0100 Matthew Seaman wrote: On 17/10/2011 02:45, Goran Lowkrantz wrote: - Both devel/ace5 and devel/ace6 installs version 5 of shared libraries. Should not devel/ace6 install version 6? Um... no. Not unless the ABI has changed. Which is why I put the question, the need to verify. I would not expect ACE to change major number due to marketing pressure so the probability that there are incompatible changes between major versions is significant. /glz --- "There is hopeful symbolism in the fact that flags do not wave in a vacuum." -- Arthur C. Clarke ___ 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 20111016 and KDE3
On Mon, Oct 17, 2011 at 9:15 AM, Andrea Venturoli wrote: > Using KDE3, I have ortp as a dependency of kdenetwork. > Should I follow the above or is it ok only for KDE4? > Is it needed? Would it harm anything? linphone-base is required by kdenetwork4, if you don't have it you can skip that line. I'll add it to UPDATING, thanks. If you have both kdenetwork3 and 4, well, I don't know. You can try proceeding with that step and seeing if kdenetwork3 still works, and report back. I thought it was quite unlikely that people had kdenetwork3 and 4 installed at the same time. Should this be a problem, I'll end up making it optional in kdenetwork4. -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla ___ 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: New Port for ACE-6.0.4
On 17/10/2011 02:45, Goran Lowkrantz wrote: > - Both devel/ace5 and devel/ace6 installs version 5 of shared libraries. > Should not devel/ace6 install version 6? Um... no. Not unless the ABI has changed. Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
UPDATING 20111016 and KDE3
Hello. I've seen UPDATING 20111016: having only a few bits of KDE4 left-over, I decided to clean them all, so I almost didn't need to mv and rm as reported. However, I'm a bit doubtful on: > portmaster -o net/linphone-base ortp Using KDE3, I have ortp as a dependency of kdenetwork. Should I follow the above or is it ok only for KDE4? Is it needed? Would it harm anything? bye & Thanks av. ___ 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: Subversion 1.7 and Apache
On 10/16/11 23:02, Lev Serebryakov wrote: Hello, Andrea. You wrote 17 октября 2011 г., 0:41:08: This is non critical for me and I'll just stay with 1.6; I just wanted to share. Fixed in 1.7.0_1 Thanks, no problems now. bye av. ___ 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"
