Re: macports ssh slower than osx ssh
On 2014-04-09 16:47, Brad Allison wrote: Why is macports ssh 4 seconds slower than osx built in ssh when using gss-api? brad-allison-pro:~ brad.allison$ time /opt/local/bin/ssh -2 -v -l root m2inf-kerberostest-01 date /tmp/kerbtest-ssh-macports.txt 21 real0m20.890s user0m0.007s sys 0m0.008s brad-allison-pro:~ brad.allison$ time /usr/bin/ssh -2 -v -l root m2inf-kerberostest-01 date /tmp/kerbtest-ssh-osx.txt 21 real0m15.894s user0m0.011s sys 0m0.008s It's really hard to tell where the additional time is spent without doing full profiling of the processes. Maybe the implementation in kerberos5 used by the openssh port is just slower than Heimdal used by the system openssh? Could also be that the MacPorts version makes more attempts to verify different host keys (for example supporting ECDSA) and that adds additional filesystem lookups and round trip times. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Incorrect $PATH value for root user
Hello. I can't create ticket in Trac, it always says Trac error when submitting ticket form, so i'm posting it here. Actions Type command sudo -i and fill your password. Type command echo $PATH. Result /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/opt/local/bin:/opt/local/sbin Expected result /opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin Mac OS X 10.9.2 -- Виталий ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Incorrect $PATH value for root user
On Thu, Apr 10, 2014 at 6:39 AM, Помазёнков Виталий vit...@yandex.ruwrote: Type command sudo -i and fill your password. Type command echo $PATH. *Result* /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/opt/local/bin:/opt/local/sbin This is sudo's doing (and Apple's insofar as Apple determines both sudo configuration and how the root account works), because you used -i. MacPorts can't control either one. Try sudo -s instead; it preserves your environment. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Incorrect $PATH value for root user
Yes, but MacPorts can control this. Instead of specifying export PATH=/opt/local/bin:/opt/local/sbin:$PATH in ~/.bash_profile it can (and should) specify it system-wide in /etc/bashrc - in this way there will be no problem with programs which is also installed by Apple like svn - all programs will be the same version (installed by MacPorts). # svn --version svn, version 1.7.10 (r1485443) $ sudo -i svn --version svn, version 1.8.8 (r1568071) -- Виталий 10 апр. 2014 г., в 18:37, Brandon Allbery allber...@gmail.com написал(а): On Thu, Apr 10, 2014 at 6:39 AM, Помазёнков Виталий vit...@yandex.ru wrote: Type command sudo -i and fill your password. Type command echo $PATH. Result /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/opt/local/bin:/opt/local/sbin This is sudo's doing (and Apple's insofar as Apple determines both sudo configuration and how the root account works), because you used -i. MacPorts can't control either one. Try sudo -s instead; it preserves your environment. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Incorrect $PATH value for root user
On 10/04/14 15:48, Помазёнков Виталий wrote: Yes, but MacPorts can control this. Instead of specifying export PATH=/opt/local/bin:/opt/local/sbin:$PATH in ~/.bash_profile it can (and should) specify it system-wide in /etc/bashrc - in this way there will be no problem with programs which is also installed by Apple like svn - all programs will be the same version (installed by MacPorts). I for one, (and I am sure others too) do not want MacPorts editing system files like /etc/bashrc itself. If you want this, by all means do it yourself, but it should remain an action you have to manually have to do, if you want it. Chris # svn --version svn, version 1.7.10 (r1485443) $ sudo -i svn --version svn, version 1.8.8 (r1568071) -- Виталий 10 апр. 2014 г., в 18:37, Brandon Allbery allber...@gmail.com mailto:allber...@gmail.com написал(а): On Thu, Apr 10, 2014 at 6:39 AM, Помазёнков Виталий vit...@yandex.ru mailto:vit...@yandex.ru wrote: Type command sudo -i and fill your password. Type command echo $PATH. *Result* /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/opt/local/bin:/opt/local/sbin This is sudo's doing (and Apple's insofar as Apple determines both sudo configuration and how the root account works), because you used -i. MacPorts can't control either one. Try sudo -s instead; it preserves your environment. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com mailto:allber...@gmail.com ballb...@sinenomine.net mailto:ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net http://sinenomine.net/ ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Incorrect $PATH value for root user
On Thu, Apr 10, 2014 at 10:50 AM, Chris Jones jon...@hep.phy.cam.ac.ukwrote: On 10/04/14 15:48, Помазёнков Виталий wrote: Yes, but MacPorts can control this. Instead of specifying export PATH=/opt/local/bin:/opt/local/sbin:$PATH in ~/.bash_profile it can (and should) specify it system-wide in /etc/bashrc - in this way there will be no problem with programs which is also installed by Apple like svn - all programs will be the same version (installed by MacPorts). I for one, (and I am sure others too) do not want MacPorts editing system files like /etc/bashrc itself. If you want this, by all means do it yourself, but it should remain an action you have to manually have to do, if you want it. Strong agreement; this is part of what I meant by it being Apple's. For one thing, I don't think Apple promises that /etc/bashrc won't be replaced by an OS upgrade. (Also, seriously don't place path settings in .bashrc / bashrc, it belongs in .profile / .bash_profile / /etc/profile and things like rvm / virtualenv / perlbrew etc. will randomly lose their settings if you do it in the per-shell file as it overwrites their changes.) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Gnumeric
On Apr 9, 2014, at 1:47 PM, Stan Sanderson stans...@gmail.com wrote: Ticket #43241 (trac.macports.org) reports a problem upgrading gnumeric. Two days ago, it appears that a patch was successfully applied to correct the issue. However, the patched file apparently has not been committed to the portfiles since gnumeric still fails to build. …or am I missing something? You’re not missing anything. No patch has been committed yet. Cheers! Frank ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Gnumeric
On 4/9/14 12:47 PM, Stan Sanderson wrote: Ticket #43241 (trac.macports.org) reports a problem upgrading gnumeric. Two days ago, it appears that a patch was successfully applied to correct the issue. However, the patched file apparently has not been committed to the portfiles since gnumeric still fails to build. …or am I missing something? Thanks r118756 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
dbus obsolete variants?
Hi all, today on selfupdate and upgrade, I got the following warning on upgrading dbus: Warning: You have requested an obsolete variant Warning: Installation of startup items are now determined by /opt/local/etc/macports/macports.conf Warning: See https://guide.macports.org/#reference.startupitems (it then eplaced dbus @1.6.12_0+startupitem+universal with dbus @1.8.0_0+universal) Can anyone explain this or tell me whether there needs to be done anything? dbus is not something I set out to install directly, but got installed through gimp, so I have no idea about startupitems and what changed or needs to be changed. https://guide.macports.org/#reference.startupitems doesn’t shed any light on this warning AFAICT. Thanks and take care Dominik___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
MacPorts Self-Update Failure?
I haven’t used any MacPorts software since moving to Mavericks. I have been updating Xcode consistently but not MacPorts. I attempted a self update today but it basically “hung” at the following point. spielplatz:Finances mcc$ sudo port selfupdate --- Updating MacPorts base sources using rsync MacPorts base version 2.2.1 installed, MacPorts base version 2.2.1 downloaded. --- Updating the ports tree Using tcpdump, I discovered no network traffic indicating that the ports tree was being updated. Do I need to use the MacPorts pkg to update the ports tree? I recall doing this once before but ran into a problem with older applications that were installed before using the pkg update. Will this be a problem? And, if so, what is the best way to remove old installed ports? -- Merton Campbell Crockett e-mail: m.c.crock...@roadrunner.com mobile: 1(805)377-6762 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts Self-Update Failure?
Okay, I found the notes on clearing out the previously installed MacPorts software and downloaded the MacPorts.pkg. The PKG installer is now hung running the package scripts. It appears that there is a problem with rsync on rsync.macports.org. It could also be a problem with Apple’s firewall that connects to the Level3 network. At any rate, ps indicates that the two rsync processes that were started are not accumulating any run time. Also, tcpdump shows no data being received from the server. On Apr 10, 2014, at 16:31 , Merton Campbell Crockett m.c.crock...@roadrunner.com wrote: I haven’t used any MacPorts software since moving to Mavericks. I have been updating Xcode consistently but not MacPorts. I attempted a self update today but it basically “hung” at the following point. spielplatz:Finances mcc$ sudo port selfupdate --- Updating MacPorts base sources using rsync MacPorts base version 2.2.1 installed, MacPorts base version 2.2.1 downloaded. --- Updating the ports tree Using tcpdump, I discovered no network traffic indicating that the ports tree was being updated. Do I need to use the MacPorts pkg to update the ports tree? I recall doing this once before but ran into a problem with older applications that were installed before using the pkg update. Will this be a problem? And, if so, what is the best way to remove old installed ports? -- Merton Campbell Crockett e-mail: m.c.crock...@roadrunner.com mobile: 1(805)377-6762 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Incorrect $PATH value for root user
On Apr 10 18:48:01, vit...@yandex.ru wrote: Yes, but MacPorts can control this. Instead of specifying export PATH=/opt/local/bin:/opt/local/sbin:$PATH in ~/.bash_profile it can (and should) specify it system-wide in /etc/bashrc Absolutely not. Don't any program dare touch things in /etc. These are to be edited manually, under the assumption that you know what you are doing. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Incorrect $PATH value for root user
On Apr 11 07:55:47, h...@stare.cz wrote: On Apr 10 18:48:01, vit...@yandex.ru wrote: Yes, but MacPorts can control this. Instead of specifying export PATH=/opt/local/bin:/opt/local/sbin:$PATH in ~/.bash_profile it can (and should) specify it system-wide in /etc/bashrc Absolutely not. Don't any program dare touch things in /etc. These are to be edited manually, under the assumption that you know what you are doing. Also, the role of ~/.profile and ~/.shrc is not what you think. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
