Re: MacPorts 2.3.0-rc1 now available for testing (WAS Re: Call for Testers: MacPorts Statistics)

Hi, > I needed to run > --- > sudo chmod -R o+r /opt/local/libexec/macports/lib/tcllib1.15 > --- > to make stats submission work. > > > Is the non-readability of /opt/local/libexec/macports/lib/tcllib1.15 > intentional, or is it a bug? That certainly is a bug. The question is, how did it happen

Re: MacPorts 2.3.0-rc1 now available for testing (WAS Re: Call for Testers: MacPorts Statistics)

Turns out that I ran into this as a normal user: On 13 May 2014, at 00:14 , mk-macpo...@techno.ms wrote: > At least these two were needed here on my end: > — > $ sudo chmod o+r /opt/local/libexec/macports/lib/tcl8.5/. > $ sudo chmod o+r /opt/local/libexec/macports > — > but it looks like /opt/loca

Re: Call for Testers: MacPorts Statistics

Hi Arno, On 30 May 2014, at 02:54 , Clemens Lang wrote: > Nothing besides a commit doing that. If any committer reads this, feel > free to do it right away before I find time to do it myself. I’ve just committed it to the sysutils category. Greets, Marko

Re: Call for Testers: MacPorts Statistics

Hi, > Now that 2.3 is out, is trunk still a requirement for mpstats? No. > I tried installing the package from the original message, but I see > that it's installing mpstats 0.1.3, which is outdated. Is there a > 0.1.4 package? No, but you need 0.1.4 with MacPorts 2.3.0. > What needs to happe

Re: Call for Testers: MacPorts Statistics

Now that 2.3 is out, is trunk still a requirement for mpstats? I tried installing the package from the original message, but I see that it's installing mpstats 0.1.3, which is outdated. Is there a 0.1.4 package? I can put the files in a local tree if I need to, but I figured I'd check on the packag

Re: MacPorts 2.3.0-rc1 now available for testing (WAS Re: Call for Testers: MacPorts Statistics)

At least these two were needed here on my end: — $ sudo chmod o+r /opt/local/libexec/macports/lib/tcl8.5/. $ sudo chmod o+r /opt/local/libexec/macports — but it looks like /opt/local/libexec/macports/lib/tcllib1.15 — drwxr-x--x 111 root admin3774 May 11 16:22 tcllib1.15 — is another candidate.

Re: MacPorts 2.3.0-rc1 now available for testing (WAS Re: Call for Testers: MacPorts Statistics)

Hi Joshua, when trying to run mpstats submit I met a problem which is caused by the current RC1. On 11 May 2014, at 23:44 , Clemens Lang wrote: > It seems your tcl8.5 directory isn't readable by your user. Which user did > you use > to install it? Which umask was set while you installed it? Wh

Re: Call for Testers: MacPorts Statistics

Hi, > I am here on Mavericks running port 2.3.0-RC1. > Shall I file a ticket for that? It seems your tcl8.5 directory isn't readable by your user. Which user did you use to install it? Which umask was set while you installed it? What are the permissions of /opt/local/libexec/macports/lib/tcl8.5

Re: Call for Testers: MacPorts Statistics

Hi Clemens, this is what I get since I installed the current RC: — $ /opt/local/libexec/mpstats submit Error: couldn't read file "/opt/local/share/macports/Tcl/macports1.0/macports_fastload.tcl": no such file or directory — Luckily I had seen http://trac.macports.org/changeset/119760 so that I

Re: Call for Testers: MacPorts Statistics

Hi, On 30.04.2014, at 09:45, mk-macpo...@techno.ms wrote: > I am not sure whether it had been already said, but I think it would be nice > to let query list also generate links to the port’s home URL, which holds > just as well for the MacPorts port list! Patches welcome, I guess? The source i

Re: Call for Testers: MacPorts Statistics

I am not sure whether it had been already said, but I think it would be nice to let query list also generate links to the port’s home URL, which holds just as well for the MacPorts port list! ___ macports-dev mailing list macports-dev@lists.macosforge.o

Re: Call for Testers: MacPorts Statistics

Hi, > I see your point, but that’s probably something which might occur more often > than we think now, effectively making it impossible to find actually > existing ports. Probably it would make sense to handle cases like that > differently?! Yes, you're absolutely right: https://trac.macports.or

Re: Call for Testers: MacPorts Statistics

On 09 Feb 2014, at 22:12 , Clemens Lang wrote: > but it's really the port that's to blame here. I see your point, but that’s probably something which might occur more often than we think now, effectively making it impossible to find actually existing ports. Probably it would make sense to handl

Re: Call for Testers: MacPorts Statistics

> The problem here is that the aqbanking Portfile violates lint: Oh, good to know. Can be fixed. :) Will do so right away. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Call for Testers: MacPorts Statistics

(re-sent to the list) The problem here is that the aqbanking Portfile violates lint: :) clemens@cSchlepptop:[…]/dports/devel/aqbanking$ port lint ---> Verifying Portfile for aqbanking Error: Missing required variable: categories Warning: no license set ---> 1 errors and 1 warnings found. That

Re: Call for Testers: MacPorts Statistics

Hi Clemens, I am seeing a page stating this: — The page you were looking for doesn't exist. You may have mistyped the address or the page may have moved. — in case I try to search for a non-existing or replaced_by port, e.g. [1]. I guess one could rather state on this page that the port is repl

Re: Call for Testers: MacPorts Statistics

On 09 Feb 2014, at 20:42 , Jeremy Lavergne wrote: > You probably need to run trunk for access to POST, which isn’t available in a > release yet. Ooops, I see. I wasn’t aware of that trunk is a must for this feature. ___ macports-dev mailing list macport

Re: Call for Testers: MacPorts Statistics

You probably need to run trunk for access to POST, which isn’t available in a release yet. On Feb 9, 2014, at 14:40, mk-macpo...@techno.ms wrote: > Hi Clemens, > > I installed mpstats but when trying to submit my installation details I got > this error thrown: > — > $ /opt/local/libexec/mpstat

Re: Call for Testers: MacPorts Statistics

Hi Clemens, I installed mpstats but when trying to submit my installation details I got this error thrown: — $ /opt/local/libexec/mpstats submit Submitting to http://stats.macports.neverpanic.de/submissions Error: bad option "post": must be fetch, isnewer, or getsize while executing "curl pos

Re: Call for Testers: MacPorts Statistics

On Feb 8, 2014, at 4:55 PM, Eric Gallager wrote: > Really? That sounds dangerous, but if you say it works fine, I guess I can > give it a try... That's more or less what selfupdate already does. If you also want to switch to using a checkout of the ports tree, you'll have to edit your sources

Re: Call for Testers: MacPorts Statistics

Really? That sounds dangerous, but if you say it works fine, I guess I can give it a try... On Sat, Feb 8, 2014 at 4:49 PM, Clemens Lang wrote: > Just install right over it, that works fine. > > -- > Clemens Lang > ___ macports-dev mailing list macpo

Re: Call for Testers: MacPorts Statistics

Just install right over it, that works fine. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Call for Testers: MacPorts Statistics

Is there an easy way to convert a non-trunk installation of MacPorts into a trunk installation of it? The relevant guide section says: "If you installed MacPorts using the package installer, skip this section." I don't exactly have room for

Re: Call for Testers: MacPorts Statistics

On 2014-2-9 03:39 , Clemens Lang wrote: > Note that the port uses `startupitem.autostart` in a way that only works with > the most recent trunk [2]. If your MacPorts installation isn't compatible, > the auto-loading will fail and you'll have to run `port load mpstats` > manually. Trunk is actua

Call for Testers: MacPorts Statistics

Hello MacPorts Developers, I'd like to invite you to test the MacPorts statistics service that Derek Ingrouville wrote during GSoC 2011. I made some progress over the last few days and while I was running a copy of the server for quite a while now I never had time to look at the client to finis