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

2014-07-16 Thread Marko Käning
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/local/libexec/macports/lib/tcllib1.15
 —
 drwxr-x--x 111 root admin3774 May 11 16:22 tcllib1.15
 —
 is another candidate.

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?

I am running
---
$ port version
Version: 2.3.1
---

Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


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

2014-07-16 Thread Clemens Lang
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. Did you use
the installer? Did you run selfupdate?

I'm pretty sure we actually fixed the Makefiles to correctly set the
permissions after the beta, so unless you had that folder created during
beta when this was still broken, I don't think it could be caused by our
current build scripts.

But then again, maybe somebody should re-check. I'll see if I have some
time this weekend to do that.

-- 
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

2014-05-30 Thread Marko Käning
Hi Arno,

On 30 May 2014, at 02:54 , Clemens Lang c...@macports.org 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
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Call for Testers: MacPorts Statistics

2014-05-11 Thread Clemens Lang
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?

I'm fairly confident the Tcl Makefiles get this right by installing using
  install -m$explicitMode
but let's make sure that's really the case.

-- 
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

2014-04-30 Thread MK-MacPorts
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.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Call for Testers: MacPorts Statistics

2014-04-30 Thread Clemens Lang
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 is right there on 
http://trac.macports.org/browser/branches/gsoc11-statistics/stats-server and 
http://trac.macports.org/browser/trunk/www/ports.php and the modification 
shouldn’t be very difficult.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Call for Testers: MacPorts Statistics

2014-02-09 Thread MK-MacPorts
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 post submission\[data\]=$json $stats_url
—

What can be done about this?

Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Call for Testers: MacPorts Statistics

2014-02-09 Thread Jeremy Lavergne
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/mpstats submit
 Submitting to http://stats.macports.neverpanic.de/submissions
 Error: bad option post: must be fetch, isnewer, or getsize
while executing
 curl post submission\[data\]=$json $stats_url
 —
 
 What can be done about this?

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Call for Testers: MacPorts Statistics

2014-02-09 Thread MK-MacPorts
On 09 Feb 2014, at 20:42 , Jeremy Lavergne jer...@lavergne.gotdns.org 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
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Call for Testers: MacPorts Statistics

2014-02-09 Thread MK-MacPorts
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 replaced_by or 
simply non-existing?!

Greets,
Marko



[1] http://stats.macports.neverpanic.de/ports/search/name/aqbanking
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Call for Testers: MacPorts Statistics

2014-02-09 Thread Clemens Lang
(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 causes the categories property of the aqbanking port to be nil and thus 
doesn't match any path router in the webinterface, effectively causing the 404 
you're seeing. I agree this fails in an unexpected way, but it's really the 
port that's to blame here.

-- 
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

2014-02-09 Thread MK-MacPorts
 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

2014-02-09 Thread MK-MacPorts
On 09 Feb 2014, at 22:12 , Clemens Lang c...@macports.org 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 handle cases like that differently?!

And, do I need trunk to be able to run mpstats?
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Call for Testers: MacPorts Statistics

2014-02-09 Thread Clemens Lang
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.org/changeset/116902.

 And, do I need trunk to be able to run mpstats?

Yes. 2.2.1 doesn't have curl post from pextlib, which is needed to send the 
data.

-- 
Clemens Lang
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Call for Testers: MacPorts Statistics

2014-02-08 Thread Clemens Lang
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 finish it.

Luckily, Joshua was keeping a work-in-progress port version of the statistics 
client in his user directory and I found it almost complete. With some 
modifications and some server-side bugfixes, I'm pleased to announce that it 
works fine for me.

Because statistics aren't any fun without data, I'd like to invite you to test 
the statistics service. To do that, you can install the `mpstats` port from my 
user directory [1] or use the shortcut (feel free to inspect the tarball before 
installing)
  port -yourflags install https://www.neverpanic.de/documents/mpstats.tar

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. If 
you'd like to get your statistics data out there immediately, I'd also 
recommend to run `$prefix/libexec/mpstats submit` after you've installed the 
port. The webinterface [3] will update immediately. Please also test the web 
application extensively and fix any typos or bad wording you might encounter in 
SVN [4] – remember I'm not a native speaker.

NOTE: The mpstats port from my user directory is currently configured to submit 
to my development installation of the statistics server at 
http://stats.macports.neverpanic.de/. We do not have an installation as 
MacOSForge at the moment.

[1] https://trac.macports.org/browser/users/cal/ports/macports/mpstats
[2] https://trac.macports.org/changeset/116820
[3] http://stats.macports.neverpanic.de/
[4] https://trac.macports.org/browser/branches/gsoc11-statistics/stats-server

-- 
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

2014-02-08 Thread Joshua Root
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 actually a hard requirement since it also needs the curl post
command.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Call for Testers: MacPorts Statistics

2014-02-08 Thread Eric Gallager
Is there an easy way to convert a non-trunk installation of MacPorts into a
trunk installation of it? The relevant guide
sectionhttp://guide.macports.org/#installing.macports.subversion
says:
If you installed MacPorts using the package installer, skip this section.
I don't exactly have room for multiple installations of MacPorts on my
current drive... I also found two different HowTo guides on the Wiki, but I
am not sure which one would be better to follow:
https://trac.macports.org/wiki/howto/SyncingWithSVN and
https://trac.macports.org/wiki/howto/RunningTrunk



On Sat, Feb 8, 2014 at 2:46 PM, Joshua Root j...@macports.org wrote:

 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 actually a hard requirement since it also needs the curl post
 command.

 - Josh
 ___
 macports-dev mailing list
 macports-dev@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-dev

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: Call for Testers: MacPorts Statistics

2014-02-08 Thread Clemens Lang
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

2014-02-08 Thread Eric Gallager
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 c...@macports.org wrote:

 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

2014-02-08 Thread Lawrence Velázquez
On Feb 8, 2014, at 4:55 PM, Eric Gallager eg...@gwmail.gwu.edu 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.conf accordingly.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev