Re: mythtv 0.21 - trouble compiling the port
Hello, 2009/4/12 Greg Larkin glar...@freebsd.org: Hi Bernhard, Thank you for preparing that patch. I am testing it now on my machine here, and I will commit the change once verified. Can anyone else that has had compile errors on this OS/arch combination verify that Bernhard's patch has solved the compile problem? A small correction here: Bernhard's patch solves *one* compile problem, there are still one (or more) compilation problem(s) after applying his patch. Please see the other messages in this thread. HTH -- Regards, Torfinn Ingolfsen ___ 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: mythtv 0.21 - trouble compiling the port
On Mon, April 13, 2009 9:22 am, Torfinn Ingolfsen wrote: Hello, 2009/4/12 Greg Larkin glar...@freebsd.org: Hi Bernhard, Thank you for preparing that patch. I am testing it now on my machine here, and I will commit the change once verified. Can anyone else that has had compile errors on this OS/arch combination verify that Bernhard's patch has solved the compile problem? A small correction here: Bernhard's patch solves *one* compile problem, there are still one (or more) compilation problem(s) after applying his patch. Please see the other messages in this thread. Yes, that is correct. It took me some time to figure out why that only affects multimedia/mythtv and not the multimedia/mythtv-frontend port though they are nearly the same. The reason is that the mythtranscode patch got lost on the way because it was included in my PR but is not in the repository. So i have reattached it now. It is nearly useless to test them in a tinderbox because the problems are all conflicts with an installed ffmpeg and that does not happen in a tinderbox build. Here are the patches that i've needed to get both ports working again. multimedia/mythtv: http://home.bluelife.at/ports/mythtv/patch-libs-libmyth-libmyth.pro http://home.bluelife.at/ports/mythtv/patch-programs-mythtranscode-mythtranscode.pro multimedia/mythtv-frontend: http://home.bluelife.at/ports/mythtv/patch-libs-libmyth-libmyth.pro The good news is, that i've talked to the mythtv developers yesterday and they have already fixed the include path problems that we regularly stumble across. So that should not happen again with mythtv 0.22 Thanks to the testers! -- Bernhard Fröhlich http://www.bluelife.at/ ___ 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
2009/4/12 Craig Butler craig...@lerwick.hopto.org: On Sun, 2009-04-12 at 09:41 +0100, Chris Rees wrote: 2009/4/12 lini...@freebsd.org: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: audio/rosegarden description: The Rosegarden Editor and Sequencer suite maintainer: po...@freebsd.org deprecated because: tcl82 support is going to be dropped expiration date: 2009-04-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=rosegarden Woah! How do I save this? I'm thinking we could replace this with the new version (ironically called 1.7.3 rather than 2.1). What needs doing? Update the port following the port handbook, submit pr with your changes, including change of maintainer over to you if you want it... http://www.freebsd.org/doc/en/articles/contributing-ports/article.html also has a link to the port maintainers handbook. If you need a hand just shout. Cheers Craig B Chris Thanks a lot, I'll bear your offer in mind, Chris -- A: Because it messes up 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 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: Gnucash-2.2.7_2 - 7.2 - Core dump
Thomas Hummel wrote: Hello, I was running RELENG_7/amd64 and the gnucash-2.2.7_2 port. After the last portupgrade (I usually portupgrade -a each day) few days ago, gnucash started to launch but dumped core while trying to enter into an account. For additionnal reasons (including a half completed perl5.10 upgrade), I deleted all my installed ports and started again with packages (I know about how violent it is, but I hadn't much time) : I kept my base, pkg_deleted everything and pkg_added -r gnucash and xorg). At that moment, gnucash worked again. Then I portsnaped fetch extract, portsnaped fetch update, then portupgraded -a : gnucash dumped core again when accessing an account. [...] I guess the upgrade of one or more of those packages (through portupgrade -a, thus rebuilding needed dependencies) will make the gnucash core dump problem occur again. Any clue ? I'm having the same problem both with 7.2 and 8. It crashes when opening any account page, I think the problem is the glib update to 2.20, or perhaps the gtk. Gnucash already had this kind of problem in the past. Here is a backtrace: (gdb) bt #0 0x28205e70 in gnucash_sheet_styles_set_dimensions () from /usr/local/lib/gnucash/libgncmod-register-gnome.so #1 0x282060e1 in gnucash_sheet_compile_styles () from /usr/local/lib/gnucash/libgncmod-register-gnome.so #2 0x282069a9 in gnc_table_init_gui () from /usr/local/lib/gnucash/libgncmod-register-gnome.so #3 0x281b2fc8 in gnc_split_reg_new () from /usr/local/lib/libgnc-gnome.so.0 #4 0x281aeba5 in gnc_plugin_page_register_create_widget () from /usr/local/lib/libgnc-gnome.so.0 #5 0x2990f800 in ?? () #6 0x000a in ?? () #7 0x in ?? () #8 0x2ba0 in ?? () #9 0x0804c5c4 in ?? () #10 0xbfbfd968 in ?? () #11 0x2977be64 in pthread_mutex_unlock () from /lib/libthr.so.3 Previous frame inner to this frame (corrupt stack?) I'm unable to make much from it though. Thanks -- Thomas Hummel ___ 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 -- Guido Falsi m...@madpilot.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
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 o ports/133698New port: x11-themes/kde4-windeco-crystal theme for KD o ports/133689[UPDATE] mail/libpst update to 0.6.35 o ports/133674[maintainer update] net/freeradius2 - pkg-install.in b o ports/133669[patch] x11/printscreen update to 1.3 o ports/133667ports/dirvish does not work with non-Bourne shells f ports/133666[patch] net-mgmt/nagios silence config check warning o ports/133655New port: sysutils/megacli MegaCLI SAS RAID Management o ports/133652[Patch] squirrelmail-1.4.17: non-ascii text handling f f ports/133598[PATCH] lang/squeak: Fix build f ports/133578Update port: lang/swi-pl to version 5.6.64 o ports/133577[PATCH] japanese/ja-jpmobile: RUBYGEM_AUTOPLIST o ports/133564audio/cdplay ports - bad behavior when cd drive is emp o ports/133563security/cfs rc script needs mntudp option on 8-CURR f ports/133555fix for lang/tclX o ports/133553fix palm/pose on FreeBSD 7.x o ports/133533[PATCH] Add a static user/group for audio/musicpd port o ports/133501[patch] pthread_atfork breaks net/nss_ldap on RELENG_7 f ports/133487endianess detection wrong in devel/boost o ports/133484Port update: editors/yzis - Update to v1.0.a.1 f ports/133452Can't install www/linux-flashplugin9 f ports/133451www/plone3 build fails. Plone3 needs python-2.4 but li f ports/133449[PATCH] net-mgmt/zabbix: update to 1.6.4, take maintai f ports/133448[PATCH] net-mgmt/zabbix-agent: update to 1.6.4, take m o ports/133441graphics/sane-backends: epson2 sane-backend wants to r o ports/133435deskutils/egroupware dependency unresolved o ports/133421[NEW PORT] java/eclipse-xsd: EMF-XSD Runtime o ports/133414[patch] sysctls/libcdio-0.78.2 is broken for CDROM's o ports/133413[patch] sysctls/libcdio-0.78.2 is broken for CDROM's o ports/133408[NEW PORT] chinese/qq: Tencent QQ for Linux o ports/133387openoffice don't appear in 7.1-release/Latest f ports/133361www/free-sa: new version 1.6.0 f ports/133358[PATCH] net/bounce: add new -q option f ports/133353[PATCH] audio/rubygem-mp3info: fix packaging and updat f ports/133344net/nss_ldap fails to compile if world was installed w o ports/13ClamAV Milter passes 'Worm.Mydoom.I' and this virus tu f ports/133303lang/visualworks cannot load Jun because of lacking TG f ports/133261[patch] www/free-sa: respect system cflags and expose o ports/133254[bsd.fpc.mk] don't display bogus message for fpc-using o ports/133248New Port: security/scamp o ports/133242[PATCH] science/gromacs: fix sparc64, fix WITH_MPICH o ports/133241net/balance parameter -b does not accept numeric ip ad f ports/133220dns/ldns will not compile o ports/133085New Port: textproc/lexxia: A Multiformat Text Processo o ports/133068New port: audio/linux-genpuid o ports/133047[maintainer-update] Update graphics/linux-ac3d to 6.4. f ports/133036Update Port: x11-fonts/linuxlibertine Newer version an o ports/133033www/nspluginwrapper segfaults when NIS is used (amd64) f ports/133031ports/net/igmpproxy must be at least 2 Vif's where on o ports/132956[new port] mail/gml: Mbox Maildir to Gmail loader f ports/132909[PATCH] sysutils/htop: fix treeview bug f ports/132815add option to mail/nmzmail to override max number of m o ports/132792[new port] re-activating print/ifhp o ports/132786New port: sysutils/sispmctl Utility for controlling a o ports/132772[new port] lang/rakudo-devel The Rakudo Perl 6 Compil f ports/132578ports/net/isc-dhcp30-server: Compile error : dhcpd.c: o ports/132556New port: ftp/vsftpd-ext Extended build of ftp/vsftp f ports/132536mail/assp periodically hangs up I/O o ports/132391multimedia/mplayer does not work with pulseaudio o ports/132108Hard coded variables in the mail/postfix install scrip o ports/131856sysutils/virtualmin adds new users to www group - over o ports/131580port databases/frontbase upgraded to version 4.2.9 o ports/131526lang/cmucl: CMUCL for
gnome-session - half a year later, almost there
Hi guys, I know that FreeBSD Gnome team has spread pretty thin in past few months, but just in case (or as a reminder) - is someone from the Gnome staff keeping an eye on this issue? http://bugzilla.gnome.org/show_bug.cgi?id=552387 Basically, the single biggest Gnome regression (ever?) is back to its pre-2.24 state, it probably wouldn't hurt having it back in FreeBSD before 7.2 comes out (if that's still possible, and if there is time, resources for it, etc). m. ___ 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
[HEADSUP]: The ports tree is frozen.
The ports tree is now frozen for the 7.2 release cycle. No commits will be allowed without explicit portmgr approval. We hope we can keep the freeze short and go into slush after two weeks. The tree will be completely unfrozen after the release is announced. For the full schedule, see the release schedule http://www.freebsd.org/releases/7.2R/schedule.html As always, only commit that fix existing breakage will be allowed during the freeze and we encourage everyone will help fix as many ports as possible for this release. For more information about what kinds of commits are allowed during which period, please see the portmgr policies webpage: http://www.freebsd.org/portmgr/policies_committing.html -erwin -- Erwin Lansing http://droso.org Security is like an onion. (o_ _o) It's made up of several layers \\\_\ /_///er...@freebsd.org And it makes you cry.) (er...@aauug.dk pgp16EwV9WAl1.pgp Description: PGP signature
Re: gnome-session - half a year later, almost there
On Mon, 2009-04-13 at 14:15 +0200, Michal Varga wrote: Hi guys, I know that FreeBSD Gnome team has spread pretty thin in past few months, but just in case (or as a reminder) - is someone from the Gnome staff keeping an eye on this issue? http://bugzilla.gnome.org/show_bug.cgi?id=552387 I have been watching this, but I hesitated committing the 2.26.0.90 release of gnome-session because it was still unfinished. If they put out a stable 2.26.1 before the freeze lifts, I'll try to get it in the tree. Joe Basically, the single biggest Gnome regression (ever?) is back to its pre-2.24 state, it probably wouldn't hurt having it back in FreeBSD before 7.2 comes out (if that's still possible, and if there is time, resources for it, etc). m. ___ freebsd-gn...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gnome To unsubscribe, send any mail to freebsd-gnome-unsubscr...@freebsd.org -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
[PATCH] gnome-session with session support (duh)
As noted in my previous email today ( http://lists.freebsd.org/pipermail/freebsd-gnome/2009-April/022096.html ), gnome-session 2.26.0.90 is out, with working session save/restore, the one that has been exterminated with introduction of Gnome 2.24 and created an usability nightmare for many desktop users. Since moments later the ports tree has been frozen for the upcoming FreeBSD 7.2 release, here is a little local patch in case the new changes won't make it there for a while: (gmail will probably break the lines at 80 chars, does anyone know how to prevent this?) --snip--- --- Makefile 2009-04-10 07:56:18.0 +0200 +++ Makefile.new 2009-04-13 17:34:24.0 +0200 @@ -7,7 +7,7 @@ # PORTNAME= gnome-session -PORTVERSION= 2.26.0 +PORTVERSION= 2.26.0.90 CATEGORIES= x11 gnome MASTER_SITES= GNOME \ http://www.marcuscom.com/downloads/:local --- distinfo 2009-04-10 07:56:18.0 +0200 +++ distinfo.new 2009-04-13 18:18:05.0 +0200 @@ -1,6 +1,6 @@ -MD5 (gnome2/gnome-session-2.26.0.tar.bz2) = e17dbce7446b3e42fac2b1cea7dedffd -SHA256 (gnome2/gnome-session-2.26.0.tar.bz2) = 0a161c419718b83e18200fe51e7e5f827b9b72a5ef055782c8c896c550a7881b -SIZE (gnome2/gnome-session-2.26.0.tar.bz2) = 829541 +MD5 (gnome2/gnome-session-2.26.0.90.tar.bz2) = b715b1de0de24a49eb91b41a6731919b +SHA256 (gnome2/gnome-session-2.26.0.90.tar.bz2) = d13fd92dd85286eee8d322a9f4a91dbd464bff3507f3d300b7f829d45e31d9fb +SIZE (gnome2/gnome-session-2.26.0.90.tar.bz2) = 834138 MD5 (gnome2/freebsd-splashes-gnome-2.18_1.tar) = 80eb8c52fcf9fe977e0bf8ed48b85fe5 SHA256 (gnome2/freebsd-splashes-gnome-2.18_1.tar) = fcca0f6eb759a4ef0211ecd61340f84ce8ad4d7493f725ac8613724faadbb508 SIZE (gnome2/freebsd-splashes-gnome-2.18_1.tar) = 1630720 --snip--- I've been testing .90 for a while and it seems to be working just fine (though, I guess anything could be considered fine in opposition to the whole functionality missing). So far no problems encountered, so those who can't wait for the proper introduction (be it 2.26.0.90 or 2.26.1) can use these steps to upgrade to the .90 version now: # cd /usr/ports/x11/gnome-session # fetch http://varga.stonehenge.sk/temp/gnome-session-2.26.0.90.patch # patch gnome-session-2.26.0.90.patch # rm -fv *.orig gnome-session-2.26.0.90.patch # portupgrade -vRu gnome-session (portmaster users should replace the last step with proper portmaster equivalent, of course) Restart Gnome, start using the desktop as you did back in 2.22. In case you find something seriously wrong with .90, you can go back to original 2.26.0 any time later with basically the same steps, just answer 'yes' when asked for patch reversal: # cd /usr/ports/x11/gnome-session # fetch http://varga.stonehenge.sk/temp/gnome-session-2.26.0.90.patch # patch gnome-session-2.26.0.90.patch # rm -fv *.orig gnome-session-2.26.0.90.patch # portupgrade -vfu gnome-session m. ___ 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: mythtv 0.21 - trouble compiling the port
Hello, 2009/4/13 Bernhard Fröhlich de...@bluelife.at: Here are the patches that i've needed to get both ports working again. multimedia/mythtv: http://home.bluelife.at/ports/mythtv/patch-libs-libmyth-libmyth.pro http://home.bluelife.at/ports/mythtv/patch-programs-mythtranscode-mythtranscode.pro On a freshly updated ports tree and with those two patches, I still get this error: g++ -c -pipe -march=k8 -fomit-frame-pointer -O3 -g -Wall -Wno-switch -Wpointer-arith -Wredundant-decls -Wno-non-virtual-dtor -D__STDC_CONSTANT_MACROS -I/usr/local/include/artsc -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/freetype2 -I/usr/local/include -DPIC -fPIC -DMMX -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DPREFIX=\/usr/local\ -DLIBDIR=\/usr/local/lib\ -D_LARGEFILE_SOURCE -DUSING_OSS -DUSING_H264TOOLS -DUSING_X11 -DUSING_XV -DUSING_FRONTEND -DUSING_FFMPEG_THREADS -DUSING_V4L -DUSING_DBOX2 -DUSING_IPTV -DUSING_HDHOMERUN -DUSING_BACKEND -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_SHARED -DQT_TABLET_SUPPORT -I/usr/local/share/qt/mkspecs/freebsd-g++ -I. -I../../../../../../../local/include -I../../../../../../../local/include -I../.. -I.. -I. -I../libmyth -I../libavcodec -I../libavutil -I../libmythmpeg2 -Idvbdev -Impeg -Iiptv -I../libmythlivemedia/BasicUsageEnvironment/include -I../libmythlivemedia/groupsock/include -I../libmythlivemedia/liveMedia/include -I../libmythlivemedia/UsageEnvironment/include -I../../../../../../../local/include -I/usr/local/include -o pespacket.o mpeg/pespacket.cpp In file included from mpeg/pespacket.cpp:9: /usr/local/include/artsc/../libavcodec/avcodec.h:2353: warning: 'ImgReSampleContext' is deprecated (declared at /usr/local/include/artsc/../libavcodec/avcodec.h:2347) /usr/local/include/artsc/../libavcodec/avcodec.h:2363: warning: 'ImgReSampleContext' is deprecated (declared at /usr/local/include/artsc/../libavcodec/avcodec.h:2347) mpeg/pespacket.cpp: In member function 'uint PESPacket::CalcCRC() const': mpeg/pespacket.cpp:160: error: 'av_crc04C11DB7' was not declared in this scope gmake[2]: *** [pespacket.o] Error 1 gmake[2]: Leaving directory `/usr/ports/multimedia/mythtv/work/mythtv-0.21/libs/libmythtv' gmake[1]: *** [sub-libmythtv] Error 2 gmake[1]: Leaving directory `/usr/ports/multimedia/mythtv/work/mythtv-0.21/libs' gmake: *** [sub-libs] Error 2 *** Error code 1 Stop in /usr/ports/multimedia/mythtv. *** Error code 1 Stop in /usr/ports/multimedia/mythtv. This is on a machine running: r...@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #3: Sun Mar 29 14:46:57 CEST 2009 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64 Do I need to do something more than dropping the patches into 'files'? This is the contents of the 'files' drirctory: r...@kg-quiet# pwd /usr/ports/multimedia/mythtv r...@kg-quiet# ls -l files total 40 -rw-r--r-- 1 root wheel 764 Jan 17 2007 makedb -rw-r--r-- 1 root wheel 592 Feb 27 2007 mythbackend.in -rw-r--r-- 1 root wheel 935 Mar 20 22:59 patch-configure -rw-r--r-- 1 root wheel 1190 Mar 30 23:31 patch-libs-libmyth-libmyth.pro -rw-r--r-- 1 root wheel 428 Mar 10 22:08 patch-libs__libmyth__compat.h -rw-r--r-- 1 root wheel 338 Mar 10 22:08 patch-libs__libmyth__util.cpp -rw-r--r-- 1 root wheel 400 Mar 10 22:08 patch-libs__libmythdvdnav__dvd_input.c -rw-r--r-- 1 root wheel 293 Mar 10 22:08 patch-libs__libmythdvdnav__dvdnav_internal.h -rw-r--r-- 1 root wheel 437 Mar 10 22:08 patch-libs__libmythfreemheg__Programs.cpp -rw-r--r-- 1 root wheel 386 Mar 10 22:08 patch-libs__libmythtv__cardutil.cpp -rw-r--r-- 1 root wheel 1457 Mar 10 22:08 patch-libs__libmythupnp__httprequest.cpp -rw-r--r-- 1 root wheel 510 Apr 12 15:44 patch-programs-mythtranscode-mythtranscode.pro -rw-r--r-- 1 root wheel 738 Mar 10 22:08 patch-programs__mythbackend__mainserver.cpp -rw-r--r-- 1 root wheel 456 Mar 10 22:08 patch-programs__mythbackend__scheduler.cpp -rw-r--r-- 1 root wheel 458 Mar 10 22:08 patch-programs__mythfrontend__main.cpp -rw-r--r-- 1 root wheel 500 Mar 10 22:08 patch-programs__mythtv-setup__backendsettings.cpp -rw-r--r-- 1 root wheel 417 Mar 10 22:08 pkg-deinstall.in -rw-r--r-- 1 root wheel 2268 Mar 16 20:10 pkg-install.in -rw-r--r-- 1 root wheel 280 Mar 10 22:08 pkg-message.in multimedia/mythtv-frontend: http://home.bluelife.at/ports/mythtv/patch-libs-libmyth-libmyth.pro But 'make' in mythtv-frontend works with this patch (completes without errors), on the same machine. HTH -- Regards, Torfinn Ingolfsen ___ 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: mythtv 0.21 - trouble compiling the port
On Mon, April 13, 2009 8:34 pm, Torfinn Ingolfsen wrote: Hello, 2009/4/13 Bernhard Fröhlich de...@bluelife.at: Here are the patches that i've needed to get both ports working again. multimedia/mythtv: http://home.bluelife.at/ports/mythtv/patch-libs-libmyth-libmyth.pro http://home.bluelife.at/ports/mythtv/patch-programs-mythtranscode-mythtranscode.pro On a freshly updated ports tree and with those two patches, I still get this error: g++ -c -pipe -march=k8 -fomit-frame-pointer -O3 -g -Wall -Wno-switch -Wpointer-arith -Wredundant-decls -Wno-non-virtual-dtor -D__STDC_CONSTANT_MACROS -I/usr/local/include/artsc -D_REENTRANT [snip] Looks like another missing patch. Now i've double checked with your list and this is the last missing one. (also taken from mythtv-frontend) http://home.bluelife.at/ports/mythtv/patch-libs-libmythtv-libmythtv.pro multimedia/mythtv-frontend: http://home.bluelife.at/ports/mythtv/patch-libs-libmyth-libmyth.pro But 'make' in mythtv-frontend works with this patch (completes without errors), on the same machine. Jiha :o) -- Bernhard Fröhlich http://www.bluelife.at/ ___ 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
MailScanner w/sendmail - why no one listening on port 25?
I am trying to get sendmail and MailScanner running on a 7.2-PRERELEASE system and can't figure out how to get sendmail (or any other program) to listen on port 25. If I remove MailScanner from the setup and just run sendmail alone it works as expected but adding MailScanner into the mix and the system won't accept port 25 connections. I have pretty much the same configuration running on a 6.4-STABLE system (this is a new system scheduled to replace the 6.4 system) and it works fine. I'm using the same MailScanner configuration files and sendmail.mc files on both systems. Anyone have any idea what may have changed and/or what I may have overlooked doing? Any good debugging tips for this problem would be welcomed (I've used sendmail for years but have never learned too much about it). Thanks, Bob -- Bob Willcox The trouble with doing something right the first b...@immure.com time is that nobody appreciates how difficult it was. Austin, TX -- unknown ___ 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: GNOME 2.26 available for FreeBSD
On Fri, 10 Apr 2009, Joe Marcus Clarke wrote: JMC GNOME 2.26 has been merged into the ports tree. See [snip] After upgrading via portupgrade -a my home machine I can no longer use Treminal remote login using ssh keys with the following message in the logs (sorry, can't reproduce the message from Terminal popup window) Apr 12 11:54:37 console.info revamp kernel: Apr 12 11:54:37 auth.notice revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords and or keys from being written to the disk Any hints to fix this? RELENG_7/i386 Thanks in advance. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 03:47 +0400, Dmitry Morozovsky wrote: On Fri, 10 Apr 2009, Joe Marcus Clarke wrote: JMC GNOME 2.26 has been merged into the ports tree. See [snip] After upgrading via portupgrade -a my home machine I can no longer use Treminal remote login using ssh keys with the following message in the logs (sorry, can't reproduce the message from Terminal popup window) Apr 12 11:54:37 console.info revamp kernel: Apr 12 11:54:37 auth.notice revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords and or keys from being written to the disk Any hints to fix this? RELENG_7/i386 This error is normal, and not fatal. How do you have PAM configured for SSH? Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: JMC After upgrading via portupgrade -a my home machine I can no longer use Treminal JMC remote login using ssh keys with the following message in the logs (sorry, JMC can't reproduce the message from Terminal popup window) JMC JMC Apr 12 11:54:37 console.info revamp kernel: Apr 12 11:54:37 auth.notice JMC revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords and JMC or keys from being written to the disk JMC JMC Any hints to fix this? RELENG_7/i386 JMC JMC This error is normal, and not fatal. How do you have PAM configured for JMC SSH? Hrrm, this is from client side, not from server, how can PAM intervent with this? BTW, I have There was an error creating the child process for this terminal as a modal dialog box when I tried to open stored Terminal window to the host which requires authorized_keys authentication. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 04:30 +0400, Dmitry Morozovsky wrote: On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: JMC After upgrading via portupgrade -a my home machine I can no longer use Treminal JMC remote login using ssh keys with the following message in the logs (sorry, JMC can't reproduce the message from Terminal popup window) JMC JMC Apr 12 11:54:37 console.info revamp kernel: Apr 12 11:54:37 auth.notice JMC revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords and JMC or keys from being written to the disk JMC JMC Any hints to fix this? RELENG_7/i386 JMC JMC This error is normal, and not fatal. How do you have PAM configured for JMC SSH? Hrrm, this is from client side, not from server, how can PAM intervent with this? Then I guess I misunderstand the problem. Are you having a problem with seahorse-agent acting as an SSH agent? Joe BTW, I have There was an error creating the child process for this terminal as a modal dialog box when I tried to open stored Terminal window to the host which requires authorized_keys authentication. -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: JMC JMC remote login using ssh keys with the following message in the logs (sorry, JMC JMC can't reproduce the message from Terminal popup window) JMC JMC JMC JMC Apr 12 11:54:37 console.info revamp kernel: Apr 12 11:54:37 auth.notice JMC JMC revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords and JMC JMC or keys from being written to the disk JMC JMC JMC JMC Any hints to fix this? RELENG_7/i386 JMC JMC JMC JMC This error is normal, and not fatal. How do you have PAM configured for JMC JMC SSH? JMC JMC JMC Hrrm, this is from client side, not from server, how can PAM intervent with JMC this? JMC JMC Then I guess I misunderstand the problem. Are you having a problem with JMC seahorse-agent acting as an SSH agent? It seems to be so. Let me explain the situation a bit: My home machine, RELENG_7/i386, with fresh source and fresh ports tree, acts as my window to my work servers, some of them recognising my SSH key as trusted. Before the upgrade, I had once pop-up asking for my key passphrase, then let me use this private key during my (home) session without further asking. Now, when I try to connect to the host which even possibly want to check whether I want to present some key there, I got the pop-up. I even checked that I can connect to the host in question using plain xterm, and have usual password qiery. Any other hints? Thank you! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 04:46 +0400, Dmitry Morozovsky wrote: On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: JMC JMC remote login using ssh keys with the following message in the logs (sorry, JMC JMC can't reproduce the message from Terminal popup window) JMC JMC JMC JMC Apr 12 11:54:37 console.info revamp kernel: Apr 12 11:54:37 auth.notice JMC JMC revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords and JMC JMC or keys from being written to the disk JMC JMC JMC JMC Any hints to fix this? RELENG_7/i386 JMC JMC JMC JMC This error is normal, and not fatal. How do you have PAM configured for JMC JMC SSH? JMC JMC JMC Hrrm, this is from client side, not from server, how can PAM intervent with JMC this? JMC JMC Then I guess I misunderstand the problem. Are you having a problem with JMC seahorse-agent acting as an SSH agent? It seems to be so. Let me explain the situation a bit: My home machine, RELENG_7/i386, with fresh source and fresh ports tree, acts as my window to my work servers, some of them recognising my SSH key as trusted. Before the upgrade, I had once pop-up asking for my key passphrase, then let me use this private key during my (home) session without further asking. Now, when I try to connect to the host which even possibly want to check whether I want to present some key there, I got the pop-up. I even checked that I can connect to the host in question using plain xterm, and have usual password qiery. What versions of gnome-keyring and seahorse do you have? Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: JMC JMC Then I guess I misunderstand the problem. Are you having a problem with JMC JMC seahorse-agent acting as an SSH agent? JMC JMC It seems to be so. JMC JMC Let me explain the situation a bit: JMC JMC My home machine, RELENG_7/i386, with fresh source and fresh ports tree, acts as JMC my window to my work servers, some of them recognising my SSH key as trusted. JMC JMC Before the upgrade, I had once pop-up asking for my key passphrase, then JMC let me use this private key during my (home) session without further asking. JMC JMC Now, when I try to connect to the host which even possibly want to check JMC whether I want to present some key there, I got the pop-up. I even checked that JMC I can connect to the host in question using plain xterm, and have usual JMC password qiery. JMC JMC What versions of gnome-keyring and seahorse do you have? ma...@revamp:/usr/ports pkg_info | egrep 'gnome-keyring|seahorse' gnome-keyring-2.26.0 A program that keeps passwords and other secrets seahorse-2.26.0 GNOME application for managing encryption keys (PGP, SSH) -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 04:52 +0400, Dmitry Morozovsky wrote: On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: JMC JMC Then I guess I misunderstand the problem. Are you having a problem with JMC JMC seahorse-agent acting as an SSH agent? JMC JMC It seems to be so. JMC JMC Let me explain the situation a bit: JMC JMC My home machine, RELENG_7/i386, with fresh source and fresh ports tree, acts as JMC my window to my work servers, some of them recognising my SSH key as trusted. JMC JMC Before the upgrade, I had once pop-up asking for my key passphrase, then JMC let me use this private key during my (home) session without further asking. JMC JMC Now, when I try to connect to the host which even possibly want to check JMC whether I want to present some key there, I got the pop-up. I even checked that JMC I can connect to the host in question using plain xterm, and have usual JMC password qiery. JMC JMC What versions of gnome-keyring and seahorse do you have? ma...@revamp:/usr/ports pkg_info | egrep 'gnome-keyring|seahorse' gnome-keyring-2.26.0 A program that keeps passwords and other secrets seahorse-2.26.0 GNOME application for managing encryption keys (PGP, SSH) Go to 2.26.1 on both, and see if the problem persists. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, Apr 14, 2009 at 3:13 AM, Dmitry Morozovsky ma...@rinet.ru wrote: Dear Joe Marcus, DM JMC What versions of gnome-keyring and seahorse do you have? DM DM ma...@revamp:/usr/ports pkg_info | egrep 'gnome-keyring|seahorse' DM gnome-keyring-2.26.0 A program that keeps passwords and other secrets DM seahorse-2.26.0 GNOME application for managing encryption keys (PGP, SSH) After portupgrade -f seahorse gnome-keyring and reboot still the same effect... Of course, I can wipe packages installed and set it up from scratch, but I would prefer a bit safer way if at all possible ;-) Well, I have no idea what a Terminal remote login in this particular context is, so this may not be of any help, but I've seen this issue before: Before the upgrade, I had once pop-up asking for my key passphrase, then let me use this private key during my (home) session without further asking.. Now, when I try to connect to the host which even possibly want to check whether I want to present some key there, I got the pop-up. I even checked that I can connect to the host in question using plain xterm, and have usual password qiery. I've been in similiar situation some time ago, when new gnome-keyring/seahorse (it started with one of the recent versions, don't remember exactly when, but definitely before 2.26 was introduced) for some surely interesting reason insisted on creating a very own keyring every other reboot - while originally you were using one default keyring (let's call it default) for storing your passwords, now gnome-keyring kept creating a new one named login and always set it as the default one. That login keyring was even more special in that that nothing stored in it ever worked, it still kept asking for passwords and even then was not able to use them (and lost them on the next reboot anyway.. Maybe that's a feature, don't know, don't care). I've run into this on a few different machines, every time I needed to open 'seahorse', get to Passwords tab, delete the login keyring, set the original default as the default keyring (first time I wiped them all and created a clean one to be sure, but as it turned out later, this wasn't needed), after that, passwords worked fine again. This procedure again and again for a few days/reboots, until seahorse miraculously stopped this madness and let my default keyring be, well, default (yes, just like that). Anyway, if you weren't there yet, check seahorse gui for what keyring are you really using, maybe you've hit the same issue with the login stupidity.. m. ___ 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] gnome-session with session support (duh)
Additional small patch (attached) for ConsoleKit is needed for 'shutdown' from within Gnome to work with gnome-session 2.26.0.90. Logout alone works even without applying this patch. Diff is against consolekit-0.3.0_6 (latest). # cd /usr/local/etc/dbus-1/system.d/ # fetch http://varga.stonehenge.sk/temp/ConsoleKit.patch # patch ConsoleKit.patch # rm -fv *.orig ConsoleKit.patch Relog Gnome, shutdown works again. m. ConsoleKit.patch Description: Binary data ___ 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
