Xorg totally unusable with KMS and new Xorg on Sandy Bridge system: how to undo
Thomas Mueller writes: I built the newer Xorg and it falls flat: goes to a nongraphic screen that is blank except for a rectangular cursor in the upper left corner, and now I want to get back to the earlier Xorg. System is Intel Sandy Bridge with i7 CPU. You don't mention your graphics chip explicitly, but building libdrm with the KMS option was enough to prevent X from starting on a Radeon HD 3300. (Experimental, indeed! :-) Other will be able to help more if you could post the contents of /var/log/Xorg.0.log and your xorg.conf file. Respectfully, Robert Huff ___ 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
libtelepathy-qt4 issue causes failure when upgrading kde4.
Here is an en extract from the script: -- Found Sqlite: /usr/local/include -- Found Strigi: /usr/local/lib/libstreams.so -- Found QCA2: /usr/local/lib/libqca.so -- Found gpgme-config at /usr/local/bin/gpgme-config -- Found gpgme v1.3.2, checking for flavours... -- Found flavour 'vanilla', checking whether it's usable...yes -- Found flavour 'pthread', checking whether it's usable...yes -- Usable gpgme flavours found: vanilla pthread -- Found QGpgme: /usr/local/kde4/lib/libqgpgme.so -- Found libktorrent: /usr/local/kde4/lib/libktorrent.so -- Found libmms: /usr/local/lib/libmms.so CMake Error at /usr/local/lib/cmake/TelepathyQt4/TelepathyQt4Targets-debug.cmake:40 (MESSAGE): The imported target telepathy-qt4 references the file /usr/local/lib/libtelepathy-qt4.so.2.0.9.0 but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained /usr/local/lib/cmake/TelepathyQt4/TelepathyQt4Targets-debug.cmake but not all the files it references. Call Stack (most recent call first): /usr/local/lib/cmake/TelepathyQt4/TelepathyQt4Targets.cmake:25 (INCLUDE) /usr/local/lib/cmake/TelepathyQt4/TelepathyQt4Config.cmake:26 (include) /usr/local/kde4/share/apps/cmake/modules/MacroOptionalFindPackage.cmake:32 (find_package) CMakeLists.txt:62 (macro_optional_find_package) -- Configuring incomplete, errors occurred! *** Error code 1 Stop in /usr/ports/net/kdenetwork4. *** Error code 1 Stop in /usr/ports/net/kdenetwork4. *** Error code 1 Stop in /usr/ports/net/kdenetwork4. *** Error code 1 Stop in /usr/ports/x11/kde4. *** Error code 1 Stop in /usr/ports/x11/kde4. *** Error code 1 Stop in /usr/ports/x11/kde4. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20130208-54035-u2285t-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=kde-4.8.4 UPGRADE_PORT_VER=4.8.4 make reinstall --- Restoring the old version pkg_add: warning: package 'kde-4.8.4' requires 'kdemultimedia-ffmpegthumbs-4.9.5', but 'kdemultimedia-4.9.5' is installed ** Fix the installation problem and try again. -- David Southwell ARPS AFIAP Photographic Arts Trained experienced competition judge, mentor, trainer, lecturer, Advanced digital techniques, international project photography ___ 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
x11/kde4-runtime
I have (had) /shells/bash-devel installed on my system. When updating KDE4, I discovered that the x11/kde4-runtime port and others that depend on shells/bash will not build if shell/bash-devel is installed. Presently, these ports are identical. I am not sure if I should report this as a possible bug or not. I was forced to remove the bash-devel port and revert to the bash port in order to allow the builds to continue. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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
how to move 9.1 ports to HEAD?
I just installed 9.1-release including the ports tree: root@zzz:/usr/ports # svn info /usr/ports/ Path: . Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/branches/RELENG_9_1_0 Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311939 Node Kind: directory Schedule: normal Last Changed Author: beat Last Changed Rev: 307934 Last Changed Date: 2012-11-28 20:30:08 + (Wed, 28 Nov 2012) root@zzz:/usr/ports # I want to move the ports tree to HEAD. Is there an easy way (i.e. not involving rm -rf /usr/ports/* and then a fresh svn co) of achieving this? I tried svn switch and svn relocate, but it seems these are intended for just changing the root URL, i.e. when the tree itself is not changing. Please advise Thanks Anton ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: wbar-2.3.4 upgrade
2013-02-08 15:23, Nicola Vitale skrev: Hi, [2013/2/7 Leslie Jensen les...@eskk.nu] I'm now getting wbar in the middle of the screen standing vertically even though I use the command wbar -above-desk -bpress -pos bottom -nanim 7 I have just tried that command and it works fine on my system: wbar is placed on the bottom of the screen. What is the contents of your configuration file? Best regards. Hi Nicola. Thanks for answering :-) This is my .wbar file # The Bar Font # #wbarcommand=wbar -bpress -above-desk -pos bottom i: /usr/local/share/pixmaps/wbar/dock.png c: wbar --bpress --above-desk --vbar --pos bottom --isize 32 --idist 5 --nanim 4 --falfa 65 t: /usr/local/lib/X11/fonts/webfonts/arialbd.ttf/10 i: /usr/local/share/icons/hicolor/48x48/apps/xfce-terminal.png c: exo-open --launch TerminalEmulator t: Terminal i: /usr/local/share/pixmaps/xfe.png c: /usr/local/bin/xfe t: Filhanterare i: /usr/local/lib/thunderbird/chrome/icons/default/default48.png c: /usr/local/bin/thunderbird t: Thunderbird i: /usr/local/share/pixmaps/firefox.png c: exo-open --launch WebBrowser t: Firefox i: /usr/local/share/PySolFC/images/misc/pysol02.png c: /usr/local/bin/pysolfc t: Pysol i: /usr/local/share/icons/hicolor/48x48/apps/gimp.png c: gimp t: Gimp i: /usr/local/share/pixmaps/VBox.png c: /usr/local/bin/VirtualBox t: VirtualBox i: /usr/local/share/icons/hicolor/48x48/apps/libreoffice-writer.png c: /usr/local/bin/libreoffice t: Libreoffice i: /usr/local/share/pixmaps/xfce4_xicon4.png c: /usr/local/bin/xfce4-appfinder t: Xfce4-appfinder i: /usr/local/share/pixmaps/gsmartcontrol.png c: sudo /usr/local/bin/gsmartcontrol t: Gsmartcontrol i: /usr/local/share/remmina/icons/hicolor/22x22/emblems/remmina-vnc.png c: /usr/local/bin/remmina t: Remmina i: /usr/local/share/pixmaps/wbarconf.png c: wbarconf t: Config ___ 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: how to move 9.1 ports to HEAD?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/8/13 9:47 AM, Anton Shterenlikht wrote: I just installed 9.1-release including the ports tree: root@zzz:/usr/ports # svn info /usr/ports/ Path: . Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/branches/RELENG_9_1_0 Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311939 Node Kind: directory Schedule: normal Last Changed Author: beat Last Changed Rev: 307934 Last Changed Date: 2012-11-28 20:30:08 + (Wed, 28 Nov 2012) root@zzz:/usr/ports # I want to move the ports tree to HEAD. Is there an easy way (i.e. not involving rm -rf /usr/ports/* and then a fresh svn co) of achieving this? I tried svn switch and svn relocate, but it seems these are intended for just changing the root URL, i.e. when the tree itself is not changing. Please advise Thanks Anton Hi Anton, The command svn switch svn://svn.freebsd.org/ports/head/ will do what you want. svn relocate repoints a working copy to a new URL, if the repository has changed on the server side, but svn switch updates the local working copy to match a new URL within the same repository on the server. Hope it helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEVEW4ACgkQ0sRouByUApA/lgCgs9n9jTWiaJQe9VfW1umHk+U5 3fUAnixWFiC+nXRcu7EAYOCCyOUVICta =LBMV -END PGP SIGNATURE- ___ 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: how to move 9.1 ports to HEAD?
From da...@catwhisker.org Fri Feb 8 15:04:41 2013 On Fri, Feb 08, 2013 at 02:47:05PM +, Anton Shterenlikht wrote: I just installed 9.1-release including the ports tree: =20 root@zzz:/usr/ports # svn info /usr/ports/ Path: . Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/branches/RELENG_9_1_0 Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311939 Node Kind: directory Schedule: normal Last Changed Author: beat Last Changed Rev: 307934 Last Changed Date: 2012-11-28 20:30:08 + (Wed, 28 Nov 2012) =20 root@zzz:/usr/ports # =20 I want to move the ports tree to HEAD. Is there an easy way (i.e. not involving rm -rf /usr/ports/* and then a fresh svn co) of achieving this? You already have (achieved this): ports is (still) not brnched as src is. We use the head of the ports tree for all branches of FreeBSD. I don't think it's true. While still on 9.1 ports, the latest entry in UPDATING was (well I lost it now) about NOV-2012. I believe the revision was also substantially lower. AS soon as I switched to head, the latest entry in UPDATING is from 6-FEB-2013 and the revision is 311942. Or maybe I misunderstood you? Anton ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: wbar-2.3.4 upgrade
2013-02-08 15:23, Nicola Vitale skrev: Hi, [2013/2/7 Leslie Jensen les...@eskk.nu] I'm now getting wbar in the middle of the screen standing vertically even though I use the command wbar -above-desk -bpress -pos bottom -nanim 7 I have just tried that command and it works fine on my system: wbar is placed on the bottom of the screen. What is the contents of your configuration file? Best regards. I've been playing around with the position settings. If I don't have a setting the bar places itself on the right. Using the GUI command line settings and changing the position does not change where the bar is. It stays on the right! /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: how to move 9.1 ports to HEAD?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/8/13 10:04 AM, Anton Shterenlikht wrote: From glar...@freebsd.org Fri Feb 8 14:54:13 2013 On 2/8/13 9:47 AM, Anton Shterenlikht wrote: I just installed 9.1-release including the ports tree: root@zzz:/usr/ports # svn info /usr/ports/ Path: . Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/branches/RELENG_9_1_0 Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311939 Node Kind: directory Schedule: normal Last Changed Author: beat Last Changed Rev: 307934 Last Changed Date: 2012-11-28 20:30:08 + (Wed, 28 Nov 2012) root@zzz:/usr/ports # I want to move the ports tree to HEAD. Is there an easy way (i.e. not involving rm -rf /usr/ports/* and then a fresh svn co) of achieving this? I tried svn switch and svn relocate, but it seems these are intended for just changing the root URL, i.e. when the tree itself is not changing. Please advise Thanks Anton Hi Anton, The command svn switch svn://svn.freebsd.org/ports/head/ will do what you want. svn relocate repoints a working copy to a new URL, if the repository has changed on the server side, but svn switch updates the local working copy to match a new URL within the same repository on the server. Hope it helps, Greg - -- Greg Larkin I think I get it. What you suggested worked, thank you: root@zzz:/usr/ports # svn info Path: . Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311942 Node Kind: directory Schedule: normal Last Changed Author: tota Last Changed Rev: 311942 Last Changed Date: 2013-02-08 14:53:49 + (Fri, 08 Feb 2013) However, this didn't work: root@zzz:/usr/ports # svn switch svn://svn0.us-east.freebsd.org/ports/head svn: E155025: 'svn://svn.freebsd.org/ports/head' is not the same repository as 'svn://svn0.us-east.freebsd.org/ports' root@zzz:/usr/ports # I read somewhere that it is advisable to use these mirrors to offload the main server. So how can easily switch to east (or west)? Thanks Anton Hi Anton, Ok, in that case, I would try the following, assuming your repository root is still svn://svn.freebsd.org/ports: cd /usr/ports svn relocate svn://svn0.us-east.freebsd.org/ports/ svn switch svn://svn0.us-east.freebsd.org/ports/head/ Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEVG1IACgkQ0sRouByUApDE5ACeP1jf74aplcJmQSSEnpaUaith proAoKyA6nvVClMh/vCEfu3JEC0U67SI =poiq -END PGP SIGNATURE- ___ 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: how to move 9.1 ports to HEAD?
Anton Shterenlikht writes: You already have (achieved this): ports is (still) not brnched as src is. We use the head of the ports tree for all branches of FreeBSD. I don't think it's true. While still on 9.1 ports, the latest entry in UPDATING was (well I lost it now) about NOV-2012. I believe the revision was also substantially lower. AS soon as I switched to head, the latest entry in UPDATING is from 6-FEB-2013 and the revision is 311942. Or maybe I misunderstood you? You do. :-) The local _subversion repository_ (I know I'm using incorrent terminology) has a revision number: r##. Which is the same across different versions of FreeBSD. The individual ports _maintained within that repository_ have their individual ports numbers (e.g. libreoffice-3.6.5) ... which also does not vary with the FreeBSD release. One can have libreoffice-3.6.5 and libreoffice 3.5.4 - but those are two separate ports and both work (or should) on 8.3, 9.1, and -CURRENT. If a port has a minimum (or maximum) release of the OS it supports, there a mechanism for figuring that out and DTRT. Or did I misunderstand you? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: wbar-2.3.4 upgrade
2013-02-08 15:23, Nicola Vitale skrev: Hi, [2013/2/7 Leslie Jensen les...@eskk.nu] I'm now getting wbar in the middle of the screen standing vertically even though I use the command wbar -above-desk -bpress -pos bottom -nanim 7 I have just tried that command and it works fine on my system: wbar is placed on the bottom of the screen. What is the contents of your configuration file? Best regards. Can this be helpful? Whole command: wbar -bpress -above-desk -pos bottom -vbar -nanim 10.0 appending output to nohup.out SettingsDialog hid! Saving in ~/.wbar ... Saving failed. Traceback (most recent call last): File /usr/local/bin/wbarconf, line 780, in buttonSaveClicked saveconf(self.configuration, wbarcommand) File /usr/local/bin/wbarconf, line 736, in saveconf if (cfile.closed == False): UnboundLocalError: local variable 'cfile' referenced before assignment ___ 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: Xorg totally unusable with KMS and new Xorg on Sandy Bridge system: how to undo
Thomas Mueller writes: I built the newer Xorg and it falls flat: goes to a nongraphic screen that is blank except for a rectangular cursor in the upper left corner, and now I want to get back to the earlier Xorg. System is Intel Sandy Bridge with i7 CPU. Robert Huff responds: You don't mention your graphics chip explicitly, but building libdrm with the KMS option was enough to prevent X from starting on a Radeon HD 3300. (Experimental, indeed! :-) Other will be able to help more if you could post the contents of /var/log/Xorg.0.log and your xorg.conf file. My /var/log/Xorg.0.log has 0 bytes! To Andrey Fesenko f0and...@gmail.com: Were you able to start X with # cat /etc/make.conf WITH_NEW_XORG=true WITH_KMS=true X.Org X Server 1.10.6 Release Date: 2012-02-10 intel(0): Integrated Graphics Chipset: Intel(R) Sandybridge Mobile (GT2+) (end of quote from Andrey Fesenko) Xorg -configure (by root) produced an error message, failed but left a file Xorg.conf.new Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 Screen 1 Screen1 RightOf Screen0 Screen 2 Screen2 RightOf Screen1 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF/ FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ EndSection Section Module Load extmod Load record Load dbe Load dri Load dri2 Load glx EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Monitor Identifier Monitor1 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Monitor Identifier Monitor2 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz, ### percent: f% ### [arg]: arg optional #Option DRI # [bool] #Option ColorKey # i #Option VideoKey # i #Option FallbackDebug # [bool] #Option Tiling# [bool] #Option LinearFramebuffer # [bool] #Option Shadow# [bool] #Option SwapbuffersWait # [bool] #Option TripleBuffer # [bool] #Option XvMC # [bool] #Option XvPreferOverlay # [bool] #Option DebugFlushBatches # [bool] #Option DebugFlushCaches # [bool] #Option DebugWait # [bool] #Option HotPlug # [bool] #Option RelaxedFencing# [bool] Identifier Card0 Driver intel BusID PCI:0:2:0 EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz, ### percent: f% ### [arg]: arg optional #Option ShadowFB # [bool] #Option Rotate# str #Option fbdev # str #Option debug # [bool] Identifier Card1 Driver fbdev BusID PCI:0:2:0 EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz, ### percent: f% ### [arg]: arg optional #Option ShadowFB # [bool] #Option DefaultRefresh# [bool] #Option ModeSetClearScreen# [bool] Identifier Card2 Driver vesa BusID PCI:0:2:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ audio/pd| 0.44-1 | 0.44-2 +-+ www/tikiwiki| 9.2 | 10.1 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: wbar-2.3.4 upgrade
Hi, [2013/2/8 Leslie Jensen les...@eskk.nu] wbar -above-desk -bpress -pos bottom -nanim 7 I've been playing around with the position settings. Have you already tried with the long options? wbar --above-desk --bpress --pos bottom --nanim 7? Best regards. -- Nicola Vitale -- Nicola Vitale ___ 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: Why the port build log file has terminal escape sequences?
On 4 February 2013 05:24, Yuri y...@rawbw.com wrote: On 02/03/2013 03:13, Chris Rees wrote: I guess this is a cmake/clang port? Cmake, clang and several other tools give colorised output. This is achieved with escape sequences. I understand about colorized output. But aren't such tools normally expected to turn colors off when run not in terminal? This is achieved by checking isatty (ttyname(3)). Probably I should file such PR to cmake. This might be a regression there. Best check it really is a cmake bug, but it wouldn't go amiss. 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: how to move 9.1 ports to HEAD?
From bf1...@googlemail.com Fri Feb 8 17:33:09 2013 I don't think it's true. While still on 9.1 ports, the latest entry in UPDATING was (well I lost it now) about NOV-2012. I believe the revision was also substantially lower. AS soon as I switched to head, the latest entry in UPDATING is from 6-FEB-2013 and the revision is 311942. Or maybe I misunderstood you? You do. :-) The local _subversion repository_ (I know I'm using incorrent terminology) has a revision number: r##. Which is the same across different versions of FreeBSD. The individual ports _maintained within that repository_ have their individual ports numbers (e.g. libreoffice-3.6.5) ... which also does not vary with the FreeBSD release. One can have libreoffice-3.6.5 and libreoffice 3.5.4 - but those are two separate ports and both work (or should) on 8.3, 9.1, and -CURRENT. If a port has a minimum (or maximum) release of the OS it supports, there a mechanism for figuring that out and DTRT. Or did I misunderstand you? Yes, it is now branched, and he was probably using the equivalent of: http://svnweb.FreeBSD.org/ports/branches/RELENG_9_1_0/ rather than http://svnweb.FreeBSD.org/ports/head/ By the way, Anton, you may wish to use https:// rather than svn:// -- slightly less efficient, but more secure. ok, I'll give it a go Thanks Anton ___ 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: how to move 9.1 ports to HEAD?
From glar...@freebsd.org Fri Feb 8 17:33:07 2013 On 2/8/13 10:04 AM, Anton Shterenlikht wrote: From glar...@freebsd.org Fri Feb 8 14:54:13 2013 On 2/8/13 9:47 AM, Anton Shterenlikht wrote: I just installed 9.1-release including the ports tree: root@zzz:/usr/ports # svn info /usr/ports/ Path: . Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/branches/RELENG_9_1_0 Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311939 Node Kind: directory Schedule: normal Last Changed Author: beat Last Changed Rev: 307934 Last Changed Date: 2012-11-28 20:30:08 + (Wed, 28 Nov 2012) root@zzz:/usr/ports # I want to move the ports tree to HEAD. Is there an easy way (i.e. not involving rm -rf /usr/ports/* and then a fresh svn co) of achieving this? I tried svn switch and svn relocate, but it seems these are intended for just changing the root URL, i.e. when the tree itself is not changing. Please advise Thanks Anton Hi Anton, The command svn switch svn://svn.freebsd.org/ports/head/ will do what you want. svn relocate repoints a working copy to a new URL, if the repository has changed on the server side, but svn switch updates the local working copy to match a new URL within the same repository on the server. Hope it helps, Greg - -- Greg Larkin I think I get it. What you suggested worked, thank you: root@zzz:/usr/ports # svn info Path: . Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311942 Node Kind: directory Schedule: normal Last Changed Author: tota Last Changed Rev: 311942 Last Changed Date: 2013-02-08 14:53:49 + (Fri, 08 Feb 2013) However, this didn't work: root@zzz:/usr/ports # svn switch svn://svn0.us-east.freebsd.org/ports/head svn: E155025: 'svn://svn.freebsd.org/ports/head' is not the same repository as 'svn://svn0.us-east.freebsd.org/ports' root@zzz:/usr/ports # I read somewhere that it is advisable to use these mirrors to offload the main server. So how can easily switch to east (or west)? Thanks Anton Hi Anton, Ok, in that case, I would try the following, assuming your repository root is still svn://svn.freebsd.org/ports: cd /usr/ports svn relocate svn://svn0.us-east.freebsd.org/ports/ svn switch svn://svn0.us-east.freebsd.org/ports/head/ I was already on head, so just svn relocate svn://svn0.us-east.freebsd.org/ports/head was sufficient. I think I got the idea now for when to use switch and when relocate. Many thanks Anton ___ 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
mutt vs db44: Shared object libdb-4.4.so.0 not found, required by mutt
Hi,
there might be an issue with the mail/mutt port which interferes with
the db44-* Port.
In my build-jail (fbsd9.uugrn.org) I have db41, db42 and db44 due to
some dependencies:
[root@fbsd9 ~]# pkg_info | grep ^db4
db41-4.1.25_4 The Berkeley DB package, revision 4.1
db42-4.2.52_5 The Berkeley DB package, revision 4.2
db44-4.4.20.4 The Berkeley DB package, revision 4.4
When building mutt here, it depends on db41 and db42:
[root@fbsd9 ~]# pkg_info -Rr mutt*
Information for mutt-1.5.21_1:
Depends on:
Dependency: ispell-3.3.02_5
Dependency: openssl-1.0.1_6
Dependency: mime-support-3.52.2
Dependency: pkgconf-0.8.9
Dependency: sqlite3-3.7.14.1
Dependency: mysql-client-5.5.30
Dependency: db42-4.2.52_5 ***
Dependency: db41-4.1.25_4 ***
Dependency: cyrus-sasl-2.1.26_2
Dependency: libiconv-1.14
Dependency: gettext-0.18.1.1
Dependency: libidn-1.26
... but the mutt binary is linked against db44!
[root@fbsd9 ~]# ldd $(which mutt)
/usr/local/bin/mutt:
libncursesw.so.8 = /lib/libncursesw.so.8 (0x8008cf000)
libssl.so.8 = /usr/local/lib/libssl.so.8 (0x800b2a000)
libcrypto.so.8 = /usr/local/lib/libcrypto.so.8 (0x800d9)
libz.so.6 = /lib/libz.so.6 (0x801165000)
libsasl2.so.3 = /usr/local/lib/libsasl2.so.3 (0x801379000)
libintl.so.9 = /usr/local/lib/libintl.so.9 (0x801594000)
libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x80179e000)
libidn.so.17 = /usr/local/lib/libidn.so.17 (0x801a9a000)
*** libdb-4.4.so.0 = /usr/local/lib/libdb-4.4.so.0 (0x801ccc000) ***
libc.so.7 = /lib/libc.so.7 (0x801fd5000)
libthr.so.3 = /lib/libthr.so.3 (0x802328000)
[root@fbsd9 ~]# pkg_which /usr/local/lib/libdb-4.4.so.0
db44-4.4.20.4
db44* is (only!) required by the inn-Port:
[root@fbsd9 ~]# pkg_info -Rr db44-*
Information for db44-4.4.20.4:
Depends on:
Required by:
inn-2.5.2_3
Even so the recorded package dependencies. I verify packets (*.tbz)
in my qa-jail (qa.uugrn.org):
root@qa:/root # ldd /usr/local/bin/mutt
/usr/local/bin/mutt:
libncursesw.so.8 = /lib/libncursesw.so.8 (0x8008cf000)
libssl.so.8 = /usr/local/lib/libssl.so.8 (0x800b2a000)
libcrypto.so.8 = /usr/local/lib/libcrypto.so.8 (0x800d9)
libz.so.6 = /lib/libz.so.6 (0x801165000)
libsasl2.so.3 = /usr/local/lib/libsasl2.so.3 (0x801379000)
libintl.so.9 = /usr/local/lib/libintl.so.9 (0x801594000)
libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x80179e000)
libidn.so.17 = /usr/local/lib/libidn.so.17 (0x801a9a000)
*** libdb-4.4.so.0 = /usr/local/lib/libdb-4.4.so.0 (0x801ccc000) ***
libc.so.7 = /lib/libc.so.7 (0x801fd5000)
libthr.so.3 = /lib/libthr.so.3 (0x802328000)
root@qa:/root # pkg_info -Rr mutt-*
Information for mutt-1.5.21_1:
Depends on:
Dependency: ispell-3.3.02_5
Dependency: openssl-1.0.1_6
Dependency: mime-support-3.52.2
Dependency: pkgconf-0.8.9
Dependency: sqlite3-3.7.14.1
Dependency: mysql-client-5.5.30
Dependency: db42-4.2.52_5 ***
Dependency: db41-4.1.25_4 ***
Dependency: cyrus-sasl-2.1.26_2
Dependency: libiconv-1.14
Dependency: gettext-0.18.1.1
Dependency: libidn-1.26
root@qa:/root # pkg_which /usr/local/lib/libdb-4.4.so.0
db44-4.4.20.4
root@qa:/root # pkg_info -Rr /usr/ports/packages/All/mutt-1.5.21_1.tbz
Information for /usr/ports/packages/All/mutt-1.5.21_1.tbz: (!!!)
Depends on:
Dependency: ispell-3.3.02_5
Dependency: openssl-1.0.1_6
Dependency: mime-support-3.52.2
Dependency: pkgconf-0.8.9
Dependency: sqlite3-3.7.14.1
Dependency: mysql-client-5.5.30
Dependency: db42-4.2.52_5 ***
Dependency: db41-4.1.25_4 ***
Dependency: cyrus-sasl-2.1.26_2
Dependency: libiconv-1.14
Dependency: gettext-0.18.1.1
Dependency: libidn-1.26
The mutt-Makefile includes:
-
.if defined(WITH_MUTT_IMAP_HEADER_CACHE)
.if defined(WITH_TOKYOCABINET)
CONFIGURE_ARGS+=--enable-hcache --without-gdbm --without-bdb
--with-tokyocabinet
LIB_DEPENDS+= tokyocabinet.9:${PORTSDIR}/databases/tokyocabinet
.else
USE_BDB=42+
CONFIGURE_ARGS+=--enable-hcache --without-gdbm --with-bdb
.endif
.else
CONFIGURE_ARGS+=--disable-hcache
.endif
-
... so 44 matches 42+ but the recorded dependencies in the
mutt-package are db41 and(!) db42, maybe depending on other libs.
I guess there are some more issues with dependencies in the mutt port,
docbook-* seems to be a dependency not registered in the package.
---
=== Registering installation for docbook-xsl-1.76.1
=== Returning to build of mutt-1.5.21_1
=== mutt-1.5.21_1 depends on executable: lynx - found
=== mutt-1.5.21_1 depends on file: /usr/local/bin/automake-1.12 - found
=== mutt-1.5.21_1 depends on file: /usr/local/bin/autoconf-2.69 - found
=== mutt-1.5.21_1 depends on shared library: sasl2 - found
===
Re: how to move 9.1 ports to HEAD?
From bf1...@googlemail.com Fri Feb 8 17:33:09 2013 I don't think it's true. While still on 9.1 ports, the latest entry in UPDATING was (well I lost it now) about NOV-2012. I believe the revision was also substantially lower. AS soon as I switched to head, the latest entry in UPDATING is from 6-FEB-2013 and the revision is 311942. Or maybe I misunderstood you? You do. :-) The local _subversion repository_ (I know I'm using incorrent terminology) has a revision number: r##. Which is the same across different versions of FreeBSD. The individual ports _maintained within that repository_ have their individual ports numbers (e.g. libreoffice-3.6.5) ... which also does not vary with the FreeBSD release. One can have libreoffice-3.6.5 and libreoffice 3.5.4 - but those are two separate ports and both work (or should) on 8.3, 9.1, and -CURRENT. If a port has a minimum (or maximum) release of the OS it supports, there a mechanism for figuring that out and DTRT. Or did I misunderstand you? Yes, it is now branched, and he was probably using the equivalent of: http://svnweb.FreeBSD.org/ports/branches/RELENG_9_1_0/ rather than http://svnweb.FreeBSD.org/ports/head/ By the way, Anton, you may wish to use https:// rather than svn:// -- slightly less efficient, but more secure. yes, got it, cool! root@zzz:/root # svn info /usr/ports/ Path: /usr/ports Working Copy Root Path: /usr/ports URL: https://svn0.us-east.freebsd.org/ports/head Repository Root: https://svn0.us-east.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311950 Node Kind: directory Schedule: normal Last Changed Author: eadler Last Changed Rev: 311950 Last Changed Date: 2013-02-08 19:18:40 + (Fri, 08 Feb 2013) root@zzz:/root # Does svn://svn.freebsd.org/base/head support https too? Thanks Anton ___ 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: how to move 9.1 ports to HEAD?
On 2/8/13, Anton Shterenlikht me...@bristol.ac.uk wrote: From bf1...@googlemail.com Fri Feb 8 17:33:09 2013 I don't think it's true. While still on 9.1 ports, the latest entry in UPDATING was (well I lost it now) about NOV-2012. I believe the revision was also substantially lower. AS soon as I switched to head, the latest entry in UPDATING is from 6-FEB-2013 and the revision is 311942. Or maybe I misunderstood you? You do. :-) The local _subversion repository_ (I know I'm using incorrent terminology) has a revision number: r##. Which is the same across different versions of FreeBSD. The individual ports _maintained within that repository_ have their individual ports numbers (e.g. libreoffice-3.6.5) ... which also does not vary with the FreeBSD release. One can have libreoffice-3.6.5 and libreoffice 3.5.4 - but those are two separate ports and both work (or should) on 8.3, 9.1, and -CURRENT. If a port has a minimum (or maximum) release of the OS it supports, there a mechanism for figuring that out and DTRT. Or did I misunderstand you? Yes, it is now branched, and he was probably using the equivalent of: http://svnweb.FreeBSD.org/ports/branches/RELENG_9_1_0/ rather than http://svnweb.FreeBSD.org/ports/head/ By the way, Anton, you may wish to use https:// rather than svn:// -- slightly less efficient, but more secure. yes, got it, cool! root@zzz:/root # svn info /usr/ports/ Path: /usr/ports Working Copy Root Path: /usr/ports URL: https://svn0.us-east.freebsd.org/ports/head Repository Root: https://svn0.us-east.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311950 Node Kind: directory Schedule: normal Last Changed Author: eadler Last Changed Rev: 311950 Last Changed Date: 2013-02-08 19:18:40 + (Fri, 08 Feb 2013) root@zzz:/root # Does svn://svn.freebsd.org/base/head support https too? Apparently, yes. b. ___ 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: LibreOffice 3.6.5 on amd
On Fri, Feb 8, 2013 at 5:41 AM, Albert Shih albert.s...@obspm.fr wrote: Le 07/02/2013 ? 11:18:34+0100, Olivier Smedts a écrit 2013/2/6 Jung-uk Kim j...@freebsd.org: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-02-06 11:15:44 -0500, Olivier Smedts wrote: 2013/2/6 Denny Lin dennyli...@hs.ntnu.edu.tw: gmake[2]: *** [/tmp/lobuild/workdir/unxfbsd.pro/CustomTarget/testtools/uno_test.done] Segmentation fault: 11 (core dump crיי) I am also seeing this on -CURRENT amd64. For some reason uno causes a segmentation fault. I do not have Java enabled. Metoo : uno segfault during testtools stage. 10-CURRENT amd64, system and most ports compiled with clang. You can bypass the test with this patch: http://svn.redports.org/office/editors/libreoffice/files/patch-testtools__Module_testtools.mk Drop the file in libreoffice/files directory and rebuild. Actually, I am going to commit it soonish because I've seen enough complaints already. :-( On one of my pc everything compile, everything work but the registration don't work, the make install finish with : === Registering installation for libreoffice-3.6.5_1 pkg_create: read_plist: unknown command '@dirrmtry share/mimelnk/application' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/mimelnk' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/mime/packages' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/mime' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/locolor/32x32/mimetypes' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/locolor/32x32/apps' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/locolor/32x32' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/locolor/16x16/mimetypes' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/locolor/16x16/apps' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/locolor/16x16' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/locolor' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/scalable/mimetypes' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/scalable/apps' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/scalable' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/48x48/mimetypes' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/48x48/apps' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/48x48' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/32x32/mimetypes' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/32x32/apps' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/32x32' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/256x256/mimetypes' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/256x256/apps' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/256x256' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/16x16/mimetypes' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/16x16/apps' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/16x16' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/128x128/mimetypes' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/128x128/apps' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor/128x128' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/hicolor' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/gnome/scalable/mimetypes' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/gnome/scalable/apps' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/gnome/scalable' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry
Re: LibreOffice 3.6.5 on amd
Le 08/02/2013 ? 12:35:12-0800, Kevin Oberman a écrit On Fri, Feb 8, 2013 at 5:41 AM, Albert Shih albert.s...@obspm.fr wrote: complaints already. :-( On one of my pc everything compile, everything work but the registration don't work, the make install finish with : === Registering installation for libreoffice-3.6.5_1 pkg_create: read_plist: unknown command '@dirrmtry share/mimelnk/application' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/mimelnk' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/mime/packages' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/mime' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/locolor/32x32/mimetypes' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/locolor/32x32/apps' (package tools out of date?) pkg_create: write_plist: unknown command type -1 (share/mimelnk/application) *** [fake-pkg] Error code 2 Stop in /usr/ports/editors/libreoffice. *** [reinstall] Error code 1 Stop in /usr/ports/editors/libreoffice. Any idea ? I get the same thing and libreoffice puts up the splash screen, sits for about 6 seconds without updating the progress bar at all, and exits without error (0). Ugh! Absolutelyand work fine. But if you do pkg_info|grep libreoff you can see they are a little problem about the registration. Nothing to do with the compilation or the installation. Regards. JAS NB: By the way I would like to thanks all maintainer of all those ports -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: ven 8 fév 2013 21:41:18 CET ___ 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: how to move 9.1 ports to HEAD?
On Fri, Feb 8, 2013 at 10:17 PM, Anton Shterenlikht me...@bristol.ac.uk wrote: From bf1...@googlemail.com Fri Feb 8 17:33:09 2013 I don't think it's true. While still on 9.1 ports, the latest entry in UPDATING was (well I lost it now) about NOV-2012. I believe the revision was also substantially lower. AS soon as I switched to head, the latest entry in UPDATING is from 6-FEB-2013 and the revision is 311942. Or maybe I misunderstood you? You do. :-) The local _subversion repository_ (I know I'm using incorrent terminology) has a revision number: r##. Which is the same across different versions of FreeBSD. The individual ports _maintained within that repository_ have their individual ports numbers (e.g. libreoffice-3.6.5) ... which also does not vary with the FreeBSD release. One can have libreoffice-3.6.5 and libreoffice 3.5.4 - but those are two separate ports and both work (or should) on 8.3, 9.1, and -CURRENT. If a port has a minimum (or maximum) release of the OS it supports, there a mechanism for figuring that out and DTRT. Or did I misunderstand you? Yes, it is now branched, and he was probably using the equivalent of: http://svnweb.FreeBSD.org/ports/branches/RELENG_9_1_0/ rather than http://svnweb.FreeBSD.org/ports/head/ By the way, Anton, you may wish to use https:// rather than svn:// -- slightly less efficient, but more secure. yes, got it, cool! root@zzz:/root # svn info /usr/ports/ Path: /usr/ports Working Copy Root Path: /usr/ports URL: https://svn0.us-east.freebsd.org/ports/head Repository Root: https://svn0.us-east.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311950 Node Kind: directory Schedule: normal Last Changed Author: eadler Last Changed Rev: 311950 Last Changed Date: 2013-02-08 19:18:40 + (Fri, 08 Feb 2013) root@zzz:/root # Does svn://svn.freebsd.org/base/head support https too? Thanks Anton Just to repeat what others have tried to tell you. The ports tree is NOT branched. The branches/RELENG_9_1_0 thing is a tag in subversion terminology, a read only-snapshot of head from the time the release was made that will never be updated. -Kimmo ___ 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
openssl broken
I updated openssl on my system and ran into this bug: As noted numerous times on the openssl-dev list, OpenSSL 1.0.1d is broken. You need to grab http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=32cc247 and apply it to the 1.0.1d source to fix it. Will this patch be applied to the port version? -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: how to move 9.1 ports to HEAD?
On Fri, Feb 8, 2013 at 10:45 PM, Kimmo Paasiala kpaas...@gmail.com wrote: On Fri, Feb 8, 2013 at 10:17 PM, Anton Shterenlikht me...@bristol.ac.uk wrote: From bf1...@googlemail.com Fri Feb 8 17:33:09 2013 I don't think it's true. While still on 9.1 ports, the latest entry in UPDATING was (well I lost it now) about NOV-2012. I believe the revision was also substantially lower. AS soon as I switched to head, the latest entry in UPDATING is from 6-FEB-2013 and the revision is 311942. Or maybe I misunderstood you? You do. :-) The local _subversion repository_ (I know I'm using incorrent terminology) has a revision number: r##. Which is the same across different versions of FreeBSD. The individual ports _maintained within that repository_ have their individual ports numbers (e.g. libreoffice-3.6.5) ... which also does not vary with the FreeBSD release. One can have libreoffice-3.6.5 and libreoffice 3.5.4 - but those are two separate ports and both work (or should) on 8.3, 9.1, and -CURRENT. If a port has a minimum (or maximum) release of the OS it supports, there a mechanism for figuring that out and DTRT. Or did I misunderstand you? Yes, it is now branched, and he was probably using the equivalent of: http://svnweb.FreeBSD.org/ports/branches/RELENG_9_1_0/ rather than http://svnweb.FreeBSD.org/ports/head/ By the way, Anton, you may wish to use https:// rather than svn:// -- slightly less efficient, but more secure. yes, got it, cool! root@zzz:/root # svn info /usr/ports/ Path: /usr/ports Working Copy Root Path: /usr/ports URL: https://svn0.us-east.freebsd.org/ports/head Repository Root: https://svn0.us-east.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311950 Node Kind: directory Schedule: normal Last Changed Author: eadler Last Changed Rev: 311950 Last Changed Date: 2013-02-08 19:18:40 + (Fri, 08 Feb 2013) root@zzz:/root # Does svn://svn.freebsd.org/base/head support https too? Thanks Anton Just to repeat what others have tried to tell you. The ports tree is NOT branched. The branches/RELENG_9_1_0 thing is a tag in subversion terminology, a read only-snapshot of head from the time the release was made that will never be updated. -Kimmo Actually I'm talking slightly rubbish here, the tags are in the tags/* part of the repository, for example http://svn.freebsd.org/ports/tags/RELEASE_9_1_0. The branches/RELENG_9_1_0 thing is a proper branch but since there's no announcement of what it should used for I would guess it's someone's test branch. -Kimmo ___ 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: how to move 9.1 ports to HEAD?
On 2/8/13, Kimmo Paasiala kpaas...@gmail.com wrote: On Fri, Feb 8, 2013 at 10:45 PM, Kimmo Paasiala kpaas...@gmail.com wrote: On Fri, Feb 8, 2013 at 10:17 PM, Anton Shterenlikht me...@bristol.ac.uk wrote: From bf1...@googlemail.com Fri Feb 8 17:33:09 2013 I don't think it's true. While still on 9.1 ports, the latest entry in UPDATING was (well I lost it now) about NOV-2012. I believe the revision was also substantially lower. AS soon as I switched to head, the latest entry in UPDATING is from 6-FEB-2013 and the revision is 311942. Or maybe I misunderstood you? You do. :-) The local _subversion repository_ (I know I'm using incorrent terminology) has a revision number: r##. Which is the same across different versions of FreeBSD. The individual ports _maintained within that repository_ have their individual ports numbers (e.g. libreoffice-3.6.5) ... which also does not vary with the FreeBSD release. One can have libreoffice-3.6.5 and libreoffice 3.5.4 - but those are two separate ports and both work (or should) on 8.3, 9.1, and -CURRENT. If a port has a minimum (or maximum) release of the OS it supports, there a mechanism for figuring that out and DTRT. Or did I misunderstand you? Yes, it is now branched, and he was probably using the equivalent of: http://svnweb.FreeBSD.org/ports/branches/RELENG_9_1_0/ rather than http://svnweb.FreeBSD.org/ports/head/ By the way, Anton, you may wish to use https:// rather than svn:// -- slightly less efficient, but more secure. yes, got it, cool! root@zzz:/root # svn info /usr/ports/ Path: /usr/ports Working Copy Root Path: /usr/ports URL: https://svn0.us-east.freebsd.org/ports/head Repository Root: https://svn0.us-east.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311950 Node Kind: directory Schedule: normal Last Changed Author: eadler Last Changed Rev: 311950 Last Changed Date: 2013-02-08 19:18:40 + (Fri, 08 Feb 2013) root@zzz:/root # Does svn://svn.freebsd.org/base/head support https too? Thanks Anton Just to repeat what others have tried to tell you. The ports tree is NOT branched. The branches/RELENG_9_1_0 thing is a tag in subversion terminology, a read only-snapshot of head from the time the release was made that will never be updated. -Kimmo Actually I'm talking slightly rubbish here, the tags are in the tags/* part of the repository, for example http://svn.freebsd.org/ports/tags/RELEASE_9_1_0. The branches/RELENG_9_1_0 thing is a proper branch but since there's no announcement of what it should used for I would guess it's someone's test branch. Yes, it's a branch -- or a copy, I suppose, in subversion terms. I believe it was used to generate the package set for the 9.1 release. There probably won't be any future changes to it, but people can use it, as Anton apparently did. b. ___ 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: Zimbra Port
Chris, I dug into it hard just a few days ago. Here's their issues: Like most people who are solely Linux (I'm not solely anything, 25+ years in sysadmin, architecture, internet engineering, etc.), they don't understand where /opt came from and what its true, original purpose was. (Additional OS enhancement software - directory was created circa 1990). Most of the linux world believes that all additional software goes into /opt. Happily, we have nullfs but more happily, ZFS. ZFS creating /opt/zimbra or creating a zpool and zfs'ing it, whatever, solves this issue. (In other words, poor use of auto-configuration tools and make variables that allow you to define a DESTDIR instead of hardcoding it.) Performing a softlink or other things causes the install to totally blow up. They guy who did the attempt at FreeBSD installation, did a decent job at figuring this out. Everything, performing his procedure works as almost as directed. Things that are not to be liked about it: He builds specific packages for the install and bundles them up with the install. He creates three packages for the install, the builddeps, rundeps and source. He then almost forces you to use these packages and his 'blessed ports packages that he created to get it to install correctly instead of just using ports. After all this is installed with pkg_add (I couldn't find any indication of pkgng work) The supporting software is installed and ready to go. Now, you get to the Zimbra source. (All 3 software bundles are tar'd and gzip'd) Once the ZCS is unpacked, you run install.sh in its root directory and away it goes. Once you get by some very strange errors (DNS not configured but it was, you have to force it to be your domain, and some other strangeness), you work out those few issues and find no errors in the install log(s). Awesome The last part of it is the thing starts up and integrates everything (This is something truly impressive: Apache, OpenSSL (certs get gen'd) , LDAP, MySqeel, Postfix, all the spam, virus, etc packages that go with a mail system, and on and on. It then tells me everything is running and I have to connect to https://host:7071. it just hangs at that point *shrug* I've tried debugging it and I've tried over 10 times of going over possible errors. Nothing. I tried contacting the author but there seems to be an access issue. I'll try again soon, however, my company is being built right now so I have VERY, VERY LIMITED time. (Yes, it's PC-BSD and FreeBSD based) I was hoping to have a full collaboration suite for MS exchange and Outlook drop-in replacement and this looked very promising. *sigh* P. From: Chris Rees cr...@freebsd.org To: Paul Pathiakis pathia...@yahoo.com Cc: po...@freebsd.org po...@freebsd.org Sent: Friday, February 8, 2013 2:23 PM Subject: Re: Zimbra Port On 29 January 2013 15:22, Paul Pathiakis pathia...@yahoo.com wrote: Hi, It looks like they are s close here. Can't ports pick this up and put it in the collection? http://wiki.zimbra.com/wiki/Zimbra_on_FreeBSD If you look at the Zimbra site for threads there are quite few with people asking for Zimbra on FreeBSD. At a glance it's a little less trivial than picking it up and putting it in the collection :) It probably wouldn't be too difficult, but someone would need to make a tarball of the sources available, which may have licensing issues... perhaps you could ask the author how he made the packages? 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: openssl broken
Jerry je...@seibercom.net wrote: I updated openssl on my system and ran into this bug: As noted numerous times on the openssl-dev list, OpenSSL 1.0.1d is broken. You need to grab http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=32cc247 and apply it to the 1.0.1d source to fix it. Will this patch be applied to the port version? I'd like to second that. I ran into this issue as well, breaking dovecot, postfix and nginx. Thanks to zfs snapshots I've been able to recover within seconds ;-) Regards, Michael ___ 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: how to move 9.1 ports to HEAD?
From bf1...@googlemail.com Fri Feb 8 21:00:33 2013 On Fri, Feb 8, 2013 at 10:45 PM, Kimmo Paasiala kpaas...@gmail.com wrote: On Fri, Feb 8, 2013 at 10:17 PM, Anton Shterenlikht me...@bristol.ac.uk wrote: From bf1...@googlemail.com Fri Feb 8 17:33:09 2013 I don't think it's true. While still on 9.1 ports, the latest entry in UPDATING was (well I lost it now) about NOV-2012. I believe the revision was also substantially lower. AS soon as I switched to head, the latest entry in UPDATING is from 6-FEB-2013 and the revision is 311942. Or maybe I misunderstood you? You do. :-) The local _subversion repository_ (I know I'm using incorrent terminology) has a revision number: r##. Which is the same across different versions of FreeBSD. The individual ports _maintained within that repository_ have their individual ports numbers (e.g. libreoffice-3.6.5) ... which also does not vary with the FreeBSD release. One can have libreoffice-3.6.5 and libreoffice 3.5.4 - but those are two separate ports and both work (or should) on 8.3, 9.1, and -CURRENT. If a port has a minimum (or maximum) release of the OS it supports, there a mechanism for figuring that out and DTRT. Or did I misunderstand you? Yes, it is now branched, and he was probably using the equivalent of: http://svnweb.FreeBSD.org/ports/branches/RELENG_9_1_0/ rather than http://svnweb.FreeBSD.org/ports/head/ By the way, Anton, you may wish to use https:// rather than svn:// -- slightly less efficient, but more secure. yes, got it, cool! root@zzz:/root # svn info /usr/ports/ Path: /usr/ports Working Copy Root Path: /usr/ports URL: https://svn0.us-east.freebsd.org/ports/head Repository Root: https://svn0.us-east.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 311950 Node Kind: directory Schedule: normal Last Changed Author: eadler Last Changed Rev: 311950 Last Changed Date: 2013-02-08 19:18:40 + (Fri, 08 Feb 2013) root@zzz:/root # Does svn://svn.freebsd.org/base/head support https too? Thanks Anton Just to repeat what others have tried to tell you. The ports tree is NOT branched. The branches/RELENG_9_1_0 thing is a tag in subversion terminology, a read only-snapshot of head from the time the release was made that will never be updated. -Kimmo Actually I'm talking slightly rubbish here, the tags are in the tags/* part of the repository, for example http://svn.freebsd.org/ports/tags/RELEASE_9_1_0. The branches/RELENG_9_1_0 thing is a proper branch but since there's no announcement of what it should used for I would guess it's someone's test branch. Yes, it's a branch -- or a copy, I suppose, in subversion terms. I believe it was used to generate the package set for the 9.1 release. There probably won't be any future changes to it, but people can use it, as Anton apparently did. yes, that's what I thought. Anton P.S. Thanks for the https hint, I now moved both the ports and the src trees to it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: x11/kde4-runtime
On 8 February 2013 13:37, Jerry je...@seibercom.net wrote: I have (had) /shells/bash-devel installed on my system. When updating KDE4, I discovered that the x11/kde4-runtime port and others that depend on shells/bash will not build if shell/bash-devel is installed. Presently, these ports are identical. I am not sure if I should report this as a possible bug or not. I was forced to remove the bash-devel port and revert to the bash port in order to allow the builds to continue. This is symptomatic of the dependency being of the form bash=version, rather than simply depending on the bash binary. Please would you provide a log? I can't find from a cursory search the exact port that depends on bash in this way. 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: openssh-portable segmentation faults
On 2013-02-08 00:28, Konstantin Belousov wrote: On Fri, Feb 08, 2013 at 12:16:40AM +0100, Dimitry Andric wrote: ... I guess a similar approach as take in the above thread should be taken, e.g. rename the function in the port to openbsd_strnvis(), and have the port call that. Or use macro trickery to swap the arguments... :) I suggest taking a reverse approach, and rename our libc function to e.g. NetBSD_strnvis(). This way, at least linking binaries would result in the build-time failure. For shared libraries, we also get some semi-helpful message from rtld which would allow to identify the problem without obtaining the backtrace. Anyway, the porter will see the issue cleanly. This should be done before merging the libc changes to stable. The merge to stable/9 was already done in r245439. :-/ Unfortunately, this function is not standardized, but at first sight, the NetBSD prototype: int strnvis(char *dst, size_t dlen, const char *src, int flag); is more logical than the OpenBSD prototype: int strnvis(char *dst, const char *src, size_t siz, int flag) because the 'siz' argument is really the length of 'dst'. On the other hand, OpenBSD added this function in 2000, while NetBSD was late to the party in 2011... :) That said, it is possible the semantics of the NetBSD implementation are subtly different from what OpenSSH expects, so it is safer to let the port use its own implementation anyway. The question is also how many third-party software uses strnvis(), and what the prevalent expectation is about the argument order. If most external software expects the OpenBSD order, it would be better to use that instead. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: x11/kde4-runtime
On Fri, 8 Feb 2013 21:19:34 + Chris Rees articulated: This is symptomatic of the dependency being of the form bash=version, rather than simply depending on the bash binary. Please would you provide a log? I can't find from a cursory search the exact port that depends on bash in this way. I have come across several. In order to create a log, I will have to revert to bash-devel. I reverted to the bash port because of the problems I was having. The x11/kde4-runtime is one such port however. Both portupgrade and portmaster bitched about the conflict with bash. I had the bash-devel port installed at the time. I am not sure if it was that actual port or one in the chain though. If I had a test machine available, I would change the bash port and then try building the x11/kde4-runtime port. However, since I don't, it will just have to wait. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ The difficult we do today; the impossible takes a little longer. ___ 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: openssl broken
On Fri, 8 Feb 2013 21:03:07 + (UTC) Michael Grimm articulated: Jerry je...@seibercom.net wrote: I updated openssl on my system and ran into this bug: As noted numerous times on the openssl-dev list, OpenSSL 1.0.1d is broken. You need to grab http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=32cc247 and apply it to the 1.0.1d source to fix it. Will this patch be applied to the port version? I'd like to second that. I ran into this issue as well, breaking dovecot, postfix and nginx. Thanks to zfs snapshots I've been able to recover within seconds ;-) I heard that the nice folks who brought us 1.0.1d will be coming out with 1.0.1e any day now. The key words being any day now. Sometimes I really wonder if anyone actually tests this software before releasing it. Usually I never update any software to a new version until it has been in use for a while. However, since this was not a major update, but just a minor letter, I figured how badly could I get burnt. Once again, lady luck bit me in the ass. By the way, there is now a PR filed against it. Hopefully something will be done to correct the problem. I had to revert everything back to the old version. More time lost ... -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: openssl broken
Jerry je...@seibercom.net wrote: Usually I never update any software to a new version until it has been in use for a while. However, since this was not a major update, but just a minor letter, I figured how badly could I get burnt. Hmm, I did follow the advice in my daly security report: | Affected package: openssl-1.0.1_5 | Type of problem: OpenSSL -- TLS 1.1 1.2 denial of service. | Reference: http://portaudit.FreeBSD.org/00b0d8cd-7097-11e2-98d9-003067c2616f.html Hopefully something will be done to correct the problem. I'm very confident, that this issue will be resolved very soon, really. Shit happens. Thus, I do not complain. Regards, Michael ___ 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: mutt vs db44 // Bug in /usr/ports/Mk/bsd.database.mk ?
Hi again,
quick-fix / works for me (line breaks!)
--
[root@fbsd9 ~]# diff -u /usr/ports/mail/mutt/Makefile.orig
/usr/ports/mail/mutt/Makefile
--- /usr/ports/mail/mutt/Makefile.orig 2013-02-08 22:33:28.650075250
+0100
+++ /usr/ports/mail/mutt/Makefile 2013-02-08 22:33:39.249797810
+0100
@@ -527,7 +527,7 @@
CONFIGURE_ARGS+= --enable-hcache --without-gdbm --without-bdb
--with-tokyocabinet
LIB_DEPENDS+=
tokyocabinet.9:${PORTSDIR}/databases/tokyocabinet
.else
-USE_BDB= 42+
+USE_BDB= 44
CONFIGURE_ARGS+= --enable-hcache --without-gdbm --with-bdb
.endif
.else
--
will result in
--
[root@fbsd9 ~]# pkg_info -Rr /usr/ports/packages/All/mutt-1.5.21_1.tbz
Information for /usr/ports/packages/All/mutt-1.5.21_1.tbz:
Depends on:
Dependency: ispell-3.3.02_5
Dependency: openssl-1.0.1_6
Dependency: mime-support-3.52.2
Dependency: pkgconf-0.8.9
Dependency: sqlite3-3.7.14.1
Dependency: mysql-client-5.5.30
Dependency: db44-4.4.20.4
Dependency: db41-4.1.25_4
Dependency: cyrus-sasl-2.1.26_2
Dependency: libiconv-1.14
Dependency: gettext-0.18.1.1
Dependency: libidn-1.26
--
-- works for me.
On Fri, Feb 08, 2013 at 09:15:03PM +0100, Raphael Eiselstein wrote:
Depends on:
Dependency: db42-4.2.52_5 ***
Dependency: db41-4.1.25_4 ***
*** libdb-4.4.so.0 = /usr/local/lib/libdb-4.4.so.0 (0x801ccc000) ***
I took a look on /usr/ports/Mk/bsd.database.mk
##
# USE_BDB - Add Berkeley DB library dependency.
# If no version is given (by the
# maintainer via the port or
# by the user via defined variable), try
# to find the
# currently installed version. Fall
# back to default if
# necessary (db41+).
[…]
# For specifying [40, 41, ..]+
_DB_40P=40 ${_DB_41P}
_DB_41P=41 ${_DB_42P}
_DB_42P=42 ${_DB_43P}
_DB_43P=43 ${_DB_44P}
_DB_44P=44 ${_DB_46P}
[…]
It seems when USE_BDB=42+ it will probe for 43 but I only have 44
installed here. So USE_BDB=42+ results in 42.
Setting USE_BDB=44 in the Makefile results in a dependency on 44 which
is similar to the auto-detection of mutt's autoconf and therefore will
result in a correct dependency, as shown in my QA now:
--
[root@top3 /jails/shared/qa]# zfs rollback
zroot/jails/shared/qa@20130208_tiny_init
[root@top3 /jails/shared/qa]# jexec 29 su -
root@qa:/root # pkg_info
pkg_info: no packages installed
root@qa:/root # pkg_add /usr/ports/packages/All/mutt-1.5.21_1.tbz
Copy /usr/local/openssl/openssl.cnf.sample to
/usr/local/openssl/openssl.cnf
and edit it to fit your needs.
*** Added group `cyrus' (id 60)
*** Added user `cyrus' (id 60)
You can use sasldb2 for authentication, to add users use:
saslpasswd2 -c username
If you want to enable SMTP AUTH with the system Sendmail, read
Sendmail.README
NOTE: This port has been compiled with a default pwcheck_method of
auxprop. If you want to authenticate your user by /etc/passwd,
PAM or LDAP, install ports/security/cyrus-sasl2-saslauthd and
set sasl_pwcheck_method to saslauthd after installing the
Cyrus-IMAPd 2.X port. You should also check the
/usr/local/lib/sasl2/*.conf files for the correct
pwcheck_method.
root@qa:/root # ldd /usr/local/bin/mutt
mutt* mutt_dotlock* muttbug*
root@qa:/root # ldd /usr/local/bin/mutt
/usr/local/bin/mutt:
libncursesw.so.8 = /lib/libncursesw.so.8 (0x8008cf000)
libssl.so.8 = /usr/local/lib/libssl.so.8 (0x800b2a000)
libcrypto.so.8 = /usr/local/lib/libcrypto.so.8 (0x800d9)
libz.so.6 = /lib/libz.so.6 (0x801165000)
libsasl2.so.3 = /usr/local/lib/libsasl2.so.3 (0x801379000)
libintl.so.9 = /usr/local/lib/libintl.so.9 (0x801594000)
libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x80179e000)
libidn.so.17 = /usr/local/lib/libidn.so.17 (0x801a9a000)
libdb-4.4.so.0 = /usr/local/lib/libdb-4.4.so.0 (0x801ccc000)
libc.so.7 = /lib/libc.so.7 (0x801fd5000)
libthr.so.3 = /lib/libthr.so.3 (0x802328000)
--
So my workaround works here but I strongly suspect a logical bug in
/usr/ports/Mk/bsd.database.mk: if db41, db42 and db44 exists and a port
specifies USE_BDB=42+ then it will check for db43 and then will fall
back to db42 which is not incorrect.
But autoconf will detect db44 and will link mutt against db44, but our
port will record a dependency on db42.
Someone who really knows about
Re: Zimbra Port
On Fri, Feb 8, 2013 at 12:59 PM, Paul Pathiakis pathia...@yahoo.com wrote: Chris, I dug into it hard just a few days ago. Here's their issues: Like most people who are solely Linux (I'm not solely anything, 25+ years in sysadmin, architecture, internet engineering, etc.), they don't understand where /opt came from and what its true, original purpose was. (Additional OS enhancement software - directory was created circa 1990). Most of the linux world believes that all additional software goes into /opt. Happily, we have nullfs but more happily, ZFS. ZFS creating /opt/zimbra or creating a zpool and zfs'ing it, whatever, solves this issue. (In other words, poor use of auto-configuration tools and make variables that allow you to define a DESTDIR instead of hardcoding it.) Performing a softlink or other things causes the install to totally blow up. They guy who did the attempt at FreeBSD installation, did a decent job at figuring this out. Everything, performing his procedure works as almost as directed. Things that are not to be liked about it: He builds specific packages for the install and bundles them up with the install. He creates three packages for the install, the builddeps, rundeps and source. He then almost forces you to use these packages and his 'blessed ports packages that he created to get it to install correctly instead of just using ports. After all this is installed with pkg_add (I couldn't find any indication of pkgng work) The supporting software is installed and ready to go. Now, you get to the Zimbra source. (All 3 software bundles are tar'd and gzip'd) Once the ZCS is unpacked, you run install.sh in its root directory and away it goes. Once you get by some very strange errors (DNS not configured but it was, you have to force it to be your domain, and some other strangeness), you work out those few issues and find no errors in the install log(s). Awesome The last part of it is the thing starts up and integrates everything (This is something truly impressive: Apache, OpenSSL (certs get gen'd) , LDAP, MySqeel, Postfix, all the spam, virus, etc packages that go with a mail system, and on and on. It then tells me everything is running and I have to connect to https://host:7071. it just hangs at that point *shrug* I've tried debugging it and I've tried over 10 times of going over possible errors. Nothing. I tried contacting the author but there seems to be an access issue. I'll try again soon, however, my company is being built right now so I have VERY, VERY LIMITED time. (Yes, it's PC-BSD and FreeBSD based) I was hoping to have a full collaboration suite for MS exchange and Outlook drop-in replacement and this looked very promising. *sigh* P. From: Chris Rees cr...@freebsd.org To: Paul Pathiakis pathia...@yahoo.com Cc: po...@freebsd.org po...@freebsd.org Sent: Friday, February 8, 2013 2:23 PM Subject: Re: Zimbra Port On 29 January 2013 15:22, Paul Pathiakis pathia...@yahoo.com wrote: Hi, It looks like they are s close here. Can't ports pick this up and put it in the collection? http://wiki.zimbra.com/wiki/Zimbra_on_FreeBSD If you look at the Zimbra site for threads there are quite few with people asking for Zimbra on FreeBSD. At a glance it's a little less trivial than picking it up and putting it in the collection :) It probably wouldn't be too difficult, but someone would need to make a tarball of the sources available, which may have licensing issues... perhaps you could ask the author how he made the packages? Chris I may able to take a look at this. I was a Zimbra Administrator and have run into a number of issues that I can solve, and maybe can work with you on the port. mail/zimbra or java/zimbra lol. :) -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve ___ 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: lang/perl5.16: threaded perl vs -pthread?
On 02/08/13 20:59, Anton Shterenlikht wrote: What is the difference between building lang/perl5.16 with Build threaded perl vs Build with -pthread on amd64? What if I choose both options? The point of the -pthread option is to ensure that perl doesn't hang when you load a perl module which dlopens a threaded lib. You really want this. Threaded perl is completely different. You probably don't want this unless you know what you're doing. The two are not incompatible. The defaults were chosen wisely, for good reasons. Steve ___ 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: LibreOffice 3.6.5 on amd
On Fri, Feb 8, 2013 at 12:43 PM, Albert Shih albert.s...@obspm.fr wrote: Le 08/02/2013 ? 12:35:12-0800, Kevin Oberman a écrit On Fri, Feb 8, 2013 at 5:41 AM, Albert Shih albert.s...@obspm.fr wrote: complaints already. :-( On one of my pc everything compile, everything work but the registration don't work, the make install finish with : === Registering installation for libreoffice-3.6.5_1 pkg_create: read_plist: unknown command '@dirrmtry share/mimelnk/application' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/mimelnk' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/mime/packages' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/mime' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/locolor/32x32/mimetypes' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/icons/locolor/32x32/apps' (package tools out of date?) pkg_create: write_plist: unknown command type -1 (share/mimelnk/application) *** [fake-pkg] Error code 2 Stop in /usr/ports/editors/libreoffice. *** [reinstall] Error code 1 Stop in /usr/ports/editors/libreoffice. Any idea ? I get the same thing and libreoffice puts up the splash screen, sits for about 6 seconds without updating the progress bar at all, and exits without error (0). Ugh! Absolutelyand work fine. But if you do pkg_info|grep libreoff you can see they are a little problem about the registration. Nothing to do with the compilation or the installation. Ah. Didn't read my whole response, I guess. It does not work fine. It puts up the Libreoffice3 splash ofr 6 seconds and exits with no error (returns 0). That is a long way from work fine. I have still have libreoffice-3.6.5 on my laptop and it does work, but I don't know if the changes in PORTREVISION 1 broke it or if there is an issue with the i386 build. The one that works is an amd64. I'll try updating the amd64 system tonight and see how it does. I see jkim has fixed the plist issue. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.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: Zimbra Port
Gentlemen: I created an account on the Zimbra site and sent mail to the OSS Engineer, Solko, who has done most of the attempted post. I hope to hear from him soon and get this kicked off. At the present time, I'm in the middle of performing the buildout of my infrastructure and products for Atlantis Services, my company. I hope to do FreeBSD/PC-BSD proud. :-) I hope that Ports can pick up the mantle and run with this once I get all the parties to the table. (Heck, I've done an OK job over the years although OpenNMS (Thanks to getting Sevan to talk to ports) is not a complete port, the install is incredibly simple now... FrontAccounting is getting many of my client QuickBooks users :-) Zimbra could be yet another great addition to ports. As I get more feedback from my clients as to their needs, we'll round out even more useful ports for the small business user. ) (Sure my site isn't up, word of mouth is keeping me busy enough. :-) ) You gotta love the look of bewilderment: Not Microsoft? Free Office Suite? (OO, of course) No viruses? No SPAM? Free software? No license fees? It just keeps getting better. So, here's hoping we can get this to go quickly P. From: Jason Helfman j...@freebsd.org To: Paul Pathiakis pathia...@yahoo.com Cc: Chris Rees cr...@freebsd.org; po...@freebsd.org po...@freebsd.org Sent: Friday, February 8, 2013 5:31 PM Subject: Re: Zimbra Port On Fri, Feb 8, 2013 at 12:59 PM, Paul Pathiakis pathia...@yahoo.com wrote: Chris, I dug into it hard just a few days ago. Here's their issues: Like most people who are solely Linux (I'm not solely anything, 25+ years in sysadmin, architecture, internet engineering, etc.), they don't understand where /opt came from and what its true, original purpose was. (Additional OS enhancement software - directory was created circa 1990). Most of the linux world believes that all additional software goes into /opt. Happily, we have nullfs but more happily, ZFS. ZFS creating /opt/zimbra or creating a zpool and zfs'ing it, whatever, solves this issue. (In other words, poor use of auto-configuration tools and make variables that allow you to define a DESTDIR instead of hardcoding it.) Performing a softlink or other things causes the install to totally blow up. They guy who did the attempt at FreeBSD installation, did a decent job at figuring this out. Everything, performing his procedure works as almost as directed. Things that are not to be liked about it: He builds specific packages for the install and bundles them up with the install. He creates three packages for the install, the builddeps, rundeps and source. He then almost forces you to use these packages and his 'blessed ports packages that he created to get it to install correctly instead of just using ports. After all this is installed with pkg_add (I couldn't find any indication of pkgng work) The supporting software is installed and ready to go. Now, you get to the Zimbra source. (All 3 software bundles are tar'd and gzip'd) Once the ZCS is unpacked, you run install.sh in its root directory and away it goes. Once you get by some very strange errors (DNS not configured but it was, you have to force it to be your domain, and some other strangeness), you work out those few issues and find no errors in the install log(s). Awesome The last part of it is the thing starts up and integrates everything (This is something truly impressive: Apache, OpenSSL (certs get gen'd) , LDAP, MySqeel, Postfix, all the spam, virus, etc packages that go with a mail system, and on and on. It then tells me everything is running and I have to connect to https://host:7071. it just hangs at that point *shrug* I've tried debugging it and I've tried over 10 times of going over possible errors. Nothing. I tried contacting the author but there seems to be an access issue. I'll try again soon, however, my company is being built right now so I have VERY, VERY LIMITED time. (Yes, it's PC-BSD and FreeBSD based) I was hoping to have a full collaboration suite for MS exchange and Outlook drop-in replacement and this looked very promising. *sigh* P. From: Chris Rees cr...@freebsd.org To: Paul Pathiakis pathia...@yahoo.com Cc: po...@freebsd.org po...@freebsd.org Sent: Friday, February 8, 2013 2:23 PM Subject: Re: Zimbra Port On 29 January 2013 15:22, Paul Pathiakis pathia...@yahoo.com wrote: Hi, It looks like they are s close here. Can't ports pick this up and put it in the collection? http://wiki.zimbra.com/wiki/Zimbra_on_FreeBSD If you look at the Zimbra site for threads there are quite few with people asking for Zimbra on FreeBSD. At a glance it's a little less trivial than picking it up and putting it in the collection :) It probably wouldn't be too difficult, but someone would need to make a tarball of the
Re: Xorg totally unusable with KMS and new Xorg on Sandy Bridge system: how to undo
From Warren Block wbl...@wonkity.com: After adding those, graphics/libdrm must be rebuilt, and x11-drivers/xf86-video-intel must have the KMS option enabled and be rebuilt. If you just added WITH_NEW_XORG, there will be other xorg components that need to be updated. O no, I'm getting rid of KMS and WITH_NEW_XORG because they produce an unusable Xorg installation that just crashes the system and requires Reset button. I guess I need to use portmaster with --force-config on x11/xorg ? Tom ___ 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
