Re: Working with git-svn or hgsubversion (was: Move part of macports infrastructure to GitHub)
On Mar 16, 2014, at 17:18, Rainer Müller wrote: a) No support for svn:ignore property Easy to accomplish, we would just keep the equivalent in .gitignore and .hgignore files in the repository root. The svn:ignore property would still be the authoritative value. As these are barely set at all in the ports tree, that should not be a problem. Agreed. To Clemens’ point that these could get out of sync, a pre-commit hook on the Subversion server could ensure that they are not out of sync (or else block the commit, with a message telling the user how to make them sync). b) No support for svn:keywords property Most notably we are using svn:keywords to replace the $Id$ string in every Portfile. I think this string is of limited use and we could do without it. See also this ticket for a detailed discussion of the problem: http://trac.macports.org/ticket/38902 (Following the comments in the ticket, it's not even an issue with newer versions of git-svn any more. What about hgsubversion?) Agreed, we could get rid of the $Id$ line and stop using svn:keywords. c) No support for svn:eol-style property Do we need that at all, anyway? I don't think anybody is editing this on Windows, so I doubt we would ever see a file with CRLF line endings. We want our text files to have only LF line endings—not CRLF line endings, and certainly not a mix of LF and CRLF line endings. I don’t know if anyone uses an editor that defaults to other than LF line ending styles, but I don’t want to find out about it after a lot of bad commits have already been made. svn:eol-style is enforced on the client side. To prevent problems caused by clients that don’t do this, we could write a pre-commit hook to enforce this in the repository. A hook to enforce that the required properties are set was already planned for a long time: https://trac.macports.org/ticket/12594 The idea to write a hook to prevent non-respected properties is here: https://trac.macports.org/ticket/38902 ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [117812] trunk/dports/www/mongrel2
On Sat, Mar 15, 2014 at 2:31 PM, Ryan Schmidt ryandes...@macports.org wrote:
Dropping the github portgroup breaks the livecheck. Is there something we
need to change in the github portgroup to make it easier for this port to use
it?
+master_sites
https://github.com/zedshaw/mongrel2/releases/download/v1.9.0/
Is it just that we need to commit this patch?
https://trac.macports.org/ticket/42273
Not even that, the port can switch back to github portgroup with the
simple addition of
distname${name}-${git.branch}
I also replied to the ticket.
--
Andrea
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Could we get a status update on these remaining migration issues: * MySQL database for web site offline or inaccessible * Online http servers not responding to pings * Buildbot/buildslaves not working Thanks. -Ryan On Mar 15, 2014, at 06:10, Ryan Schmidt ryandes...@macports.org wrote: Thanks. The two pages are now responding without the 21-second delay, but still say the database is offline. Also, we still have no responses to pings to distfiles.macports.org and packages.macports.org (though web services are functioning correctly). On Mar 14, 2014, at 01:46, Shreeraj Karulkar skarul...@apple.com wrote: Ryan I have put a request for the MySQL ports. We missed those while focusing on PSQL ports. We should be good by tomorrow evening. Shree Sent from my iPhone On Mar 13, 2014, at 11:14 PM, Ryan Schmidt ryandes...@macports.org wrote: Shree: A gentle reminder: Another outstanding issue for us is the MySQL database on the web site. It feeds the ports page at: https://www.macports.org/ports.php The database server is either not running or is not accessible to the web server, so the ports page displays only the message “Our database is currently unavailable. We hope to have it back soon!” It also waits 21 seconds before displaying that message, suggesting some kind of network timeout. The database is also queried on the homepage to display the total number of ports in the database: https://www.macports.org/ This too takes 21 seconds before giving up and finally loading the page without the count. If getting the MySQL database back online will take some time, I can modify the homepage to remove the database connection to at least get our homepage displaying speedily again. Note that work was already done to convert the MySQL database to PostgreSQL, as Bill had hinted we should do some time ago: https://trac.macports.org/ticket/40579 I have also done some thus-far unpublished work in this area and would be happy to help with getting this online, if this would be easier than getting the old MySQL server running again. -Ryan ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
redis port update
Could someone take a look at https://trac.macports.org/ticket/42583 please Ticket was opened 3 weeks ago and there were no updates from maintainer so I’ve prepared a patch and attached it to the ticket. It updates redis to the latest stable version and adds livecheck url/regex. And please close https://trac.macports.org/ticket/39434 since it will be done by this patch as well. -- With best regards, Ivan Larionov. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: redis port update
Completed https://trac.macports.org/changeset/117933 On Mar 17, 2014, at 10:22, Ivan Larionov xeron.os...@gmail.com wrote: Could someone take a look at https://trac.macports.org/ticket/42583 please And please close https://trac.macports.org/ticket/39434 since it will be done by this patch as well. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: build-bot subport conflict issue
On Sat, Mar 15, 2014, at 12:12 AM, Joshua Root wrote: All ports are deactivated between builds. The only way this would happen is if something had both gnuradio and gnuradio-legacy in its dependency tree, which gr-osmosdr-legacy does (via gr-fcdproplus). Yes, gr-osmosdr-legacy did have this issue (grrr). I hopefully just fixed this in r117936 https://trac.macports.org/changeset/117936 ; thanks for pointing out the issue! As I said, TTBOMK == to the best of my knowledge; but, my knowledge clearly wasn't good enough! - MLD ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Move part of macports infrastructure to GitHub
Besides all the things mentioned in this thread so far, I would like to note that there are some options to have it both ways and have a bigger presence on GitHub, even if we still keep our Trac infrastructure as well. For one, there is the mirrors account that has a bunch of read-only mirrors set up for other popular open-source projects that are hosted elsewhere: https://github.com/mirrors We could try to get that account to put up a mirror of the MacPorts read-only git mirror as well, or just put up a read-only mirror similarly ourselves. Second, GitHub has a Trac service hook that can be enabled under a repo's settings under Webhooks Services, although the notes there say that that hook is deprecated in favor of the trac-github plugin: https://github.com/aaugustin/trac-github We could try using that plugin to be able to still do everything in Trac and yet also have a presence on GitHub at the same time. Third, even if we do not want to move the MacPorts infrastructure itself to GitHub, we could at least make a MacPorts Organization on GitHub that MacPorts developers could be added to if they wanted: https://github.com/organizations/new Having a GitHub organization could at least show the GitHub community that we do at least have a human presence there, even if we do not necessarily also have a code presence there as well. Anyways, I bring up these ways to have it both ways because while I do use GitHub a lot, it is becoming harder and harder to do so, as they dropped support for the Snow Leopard version of the GitHub desktop a while ago, and more recently they made some change to the website that broke it in the Snow Leopard version of Safari, so now whenever I am using Safari, I have to remember to open all links to GitHub in Firefox or Chrome instead, which is annoying. While I can still use it, it is part of a trend of dropping compatibility that has me worried that if we move entirely to GitHub, users on older OSes might eventually get left behind, without Trac still being there as a backup. Hence why I prefer having both instead of just one. On 3/16/14, Joshua Root j...@macports.org wrote: On 2014-3-17 05:42 , Sean Farley wrote: If MacPorts really wants to switch to distributed version control, then I would suggest Mercurial. I have experimented with using Mercurial for the MacPorts repo and found that the mercurial UI is much, much more consistent than git coming from Subversion. I would certainly agree with that. However I would also agree with what Landon said here: https://lists.macosforge.org/pipermail/macports-dev/2013-September/024252.html Rainer also did a great job of explaining why moving to github is a bad idea earlier in the thread. Much the same applies to bitbucket. I should note that I've used both git and hg for real work, and a modern DVCS certainly has its advantages. But that said, I really haven't felt like I was being restricted by svn while working on MacPorts. In fact, sometimes being able to check out a single file or directory deep in the tree comes in handy. If the majority of contributors really find that they are being held back by svn, I guess I would support moving our repos to hg. We could at least add an official hg mirror. But the OP said that the thread was about github and the convenience of pull requests, not git as such. If the problem is that people find it's too much trouble to svn diff and attach the output to a ticket, maybe client side automation is the solution. We have a script to apply a patch straight from a Trac URL, so why not one to create a ticket and attach a patch. It would be more complicated certainly, but if saving that handful of clicks gets more people involved, I guess it's worth it. - 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: Mac OS Forge Migration update
Ryan 1) MySQL database: I have enabled access from the www.macports server and tested access successfully. Restarted mysqld on the data server and restarted httpd on the www server. I still can’t get to https://www.macports.org/ports.php. There is something missing that I can’t figure out. 2) Ping issue: I have reopened the ticket which IST had resolved earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge - ICMP . Will let you know as soon as I find out. 3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine you are probably referring to the deploy_archives.sh is failing for Mavericks right? I have tried send a file via rsync with similar options (-rlDzv) from build.macports to rsync.macports and it went through successfully. I also did a su to user buildbot and sent a test file through successfully. It did prompt me to accept the RSA key though. Can you check if it has worked? There is also a reference to use -e in the rsync options to pass ssh options like the --ignore-existing” optionthat is being used in the script. However the script has not changed 2013 so I am not sure it thats an issue. I am still working on this and would appreciate any clues from anyone, sorry for the delay in the resolution of these issues. Shree On Mar 17, 2014, at 5:58 AM, Ryan Schmidt ryandes...@macports.org wrote: Could we get a status update on these remaining migration issues: * MySQL database for web site offline or inaccessible * Online http servers not responding to pings * Buildbot/buildslaves not working Thanks. -Ryan On Mar 15, 2014, at 06:10, Ryan Schmidt ryandes...@macports.org wrote: Thanks. The two pages are now responding without the 21-second delay, but still say the database is offline. Also, we still have no responses to pings to distfiles.macports.org and packages.macports.org (though web services are functioning correctly). On Mar 14, 2014, at 01:46, Shreeraj Karulkar skarul...@apple.com wrote: Ryan I have put a request for the MySQL ports. We missed those while focusing on PSQL ports. We should be good by tomorrow evening. Shree Sent from my iPhone On Mar 13, 2014, at 11:14 PM, Ryan Schmidt ryandes...@macports.org wrote: Shree: A gentle reminder: Another outstanding issue for us is the MySQL database on the web site. It feeds the ports page at: https://www.macports.org/ports.php The database server is either not running or is not accessible to the web server, so the ports page displays only the message “Our database is currently unavailable. We hope to have it back soon!” It also waits 21 seconds before displaying that message, suggesting some kind of network timeout. The database is also queried on the homepage to display the total number of ports in the database: https://www.macports.org/ This too takes 21 seconds before giving up and finally loading the page without the count. If getting the MySQL database back online will take some time, I can modify the homepage to remove the database connection to at least get our homepage displaying speedily again. Note that work was already done to convert the MySQL database to PostgreSQL, as Bill had hinted we should do some time ago: https://trac.macports.org/ticket/40579 I have also done some thus-far unpublished work in this area and would be happy to help with getting this online, if this would be easier than getting the old MySQL server running again. -Ryan ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Shree, thanks for your reply: On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote: 1) MySQL database: I have enabled access from the www.macports server and tested access successfully. Restarted mysqld on the data server and restarted httpd on the www server. I still can’t get to https://www.macports.org/ports.php. There is something missing that I can’t figure out. The web site is trying to connect to a MySQL server running on localhost (i.e. running on the same machine serving www.macports.org). Is the MySQL server now running on a different server? If so, we need to plug its address into the includes/common.inc file. 2) Ping issue: I have reopened the ticket which IST had resolved earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge - ICMP . Will let you know as soon as I find out. 3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine you are probably referring to the deploy_archives.sh is failing for Mavericks right? I have tried send a file via rsync with similar options (-rlDzv) from build.macports to rsync.macports and it went through successfully. I also did a su to user buildbot and sent a test file through successfully. It did prompt me to accept the RSA key though. Can you check if it has worked? There is also a reference to use -e in the rsync options to pass ssh options like the --ignore-existing” optionthat is being used in the script. However the script has not changed 2013 so I am not sure it thats an issue. I meant that when I look at: https://build.macports.org/console the last revision it shows is r117767, whereas the last revision in the repository right now is r117968. So it hasn’t tried to build any of the 200 most recent revisions. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Ryan MySQL is not running on www.macports.org. There is no startup file in the /etc/ini.d/ and that is something that was not changed as a part of migration. I also did not see an entry for local host in /var/www/html/includes/common.inc”, but then it might be another file. MySQL runs on data.macports.org and www.macports is able to connect to it at port 3306. Shree On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote: Shree, thanks for your reply: On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote: 1) MySQL database: I have enabled access from the www.macports server and tested access successfully. Restarted mysqld on the data server and restarted httpd on the www server. I still can’t get to https://www.macports.org/ports.php. There is something missing that I can’t figure out. The web site is trying to connect to a MySQL server running on localhost (i.e. running on the same machine serving www.macports.org). Is the MySQL server now running on a different server? If so, we need to plug its address into the includes/common.inc file. 2) Ping issue: I have reopened the ticket which IST had resolved earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge - ICMP . Will let you know as soon as I find out. 3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine you are probably referring to the deploy_archives.sh is failing for Mavericks right? I have tried send a file via rsync with similar options (-rlDzv) from build.macports to rsync.macports and it went through successfully. I also did a su to user buildbot and sent a test file through successfully. It did prompt me to accept the RSA key though. Can you check if it has worked? There is also a reference to use -e in the rsync options to pass ssh options like the --ignore-existing” optionthat is being used in the script. However the script has not changed 2013 so I am not sure it thats an issue. I meant that when I look at: https://build.macports.org/console the last revision it shows is r117767, whereas the last revision in the repository right now is r117968. So it hasn’t tried to build any of the 200 most recent revisions. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on the
server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in the
/etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to it at
port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server and
tested access successfully. Restarted mysqld on the data server and
restarted httpd on the www server. I still can’t get to
https://www.macports.org/ports.php. There is something missing that I can’t
figure out.
The web site is trying to connect to a MySQL server running on localhost
(i.e. running on the same machine serving www.macports.org). Is the MySQL
server now running on a different server? If so, we need to plug its address
into the includes/common.inc file.
2) Ping issue: I have reopened the ticket which IST had resolved earlier.
exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge - ICMP . Will
let you know as soon as I find out.
3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine
you are probably referring to the deploy_archives.sh is failing for
Mavericks right? I have tried send a file via rsync with similar options
(-rlDzv) from build.macports to rsync.macports and it went through
successfully. I also did a su to user buildbot and sent a test file through
successfully. It did prompt me to accept the RSA key though. Can you check
if it has worked?
There is also a reference to use -e in the rsync options to pass ssh
options like the --ignore-existing” optionthat is being used in the
script. However the script has not changed 2013 so I am not sure it thats
an issue.
I meant that when I look at:
https://build.macports.org/console
the last revision it shows is r117767, whereas the last revision in the
repository right now is r117968. So it hasn’t tried to build any of the 200
most recent revisions.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Ryan
I am a little confused, what is the complete path of the file you have listed
below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on the
server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in the
/etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to it
at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server and
tested access successfully. Restarted mysqld on the data server and
restarted httpd on the www server. I still can’t get to
https://www.macports.org/ports.php. There is something missing that I
can’t figure out.
The web site is trying to connect to a MySQL server running on localhost
(i.e. running on the same machine serving www.macports.org). Is the MySQL
server now running on a different server? If so, we need to plug its
address into the includes/common.inc file.
2) Ping issue: I have reopened the ticket which IST had resolved earlier.
exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge - ICMP .
Will let you know as soon as I find out.
3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine
you are probably referring to the deploy_archives.sh is failing for
Mavericks right? I have tried send a file via rsync with similar options
(-rlDzv) from build.macports to rsync.macports and it went through
successfully. I also did a su to user buildbot and sent a test file
through successfully. It did prompt me to accept the RSA key though. Can
you check if it has worked?
There is also a reference to use -e in the rsync options to pass ssh
options like the --ignore-existing” optionthat is being used in the
script. However the script has not changed 2013 so I am not sure it thats
an issue.
I meant that when I look at:
https://build.macports.org/console
the last revision it shows is r117767, whereas the last revision in the
repository right now is r117968. So it hasn’t tried to build any of the 200
most recent revisions.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [macosforge-leaders] Mac OS Forge Migration update
Can’t hellp thinking there must be some place referencing the old IP of
data.macports.org?
Shree
On Mar 17, 2014, at 2:15 PM, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
I am a little confused, what is the complete path of the file you have listed
below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on the
server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in the
/etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to it
at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server and
tested access successfully. Restarted mysqld on the data server and
restarted httpd on the www server. I still can’t get to
https://www.macports.org/ports.php. There is something missing that I
can’t figure out.
The web site is trying to connect to a MySQL server running on localhost
(i.e. running on the same machine serving www.macports.org). Is the MySQL
server now running on a different server? If so, we need to plug its
address into the includes/common.inc file.
2) Ping issue: I have reopened the ticket which IST had resolved
earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge -
ICMP . Will let you know as soon as I find out.
3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine
you are probably referring to the deploy_archives.sh is failing for
Mavericks right? I have tried send a file via rsync with similar options
(-rlDzv) from build.macports to rsync.macports and it went through
successfully. I also did a su to user buildbot and sent a test file
through successfully. It did prompt me to accept the RSA key though. Can
you check if it has worked?
There is also a reference to use -e in the rsync options to pass ssh
options like the --ignore-existing” optionthat is being used in the
script. However the script has not changed 2013 so I am not sure it thats
an issue.
I meant that when I look at:
https://build.macports.org/console
the last revision it shows is r117767, whereas the last revision in the
repository right now is r117968. So it hasn’t tried to build any of the
200 most recent revisions.
___
macosforge-leaders mailing list
macosforge-lead...@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macosforge-leaders
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
I see, so the file differs from what’s in our repository. Are there any other
uncommitted changes? Having uncommitted changes in the working copy on the
server would cause conflicts if we committed changes to similar lines of the
file. We should commit those changes to the repository so there are no
surprises. Since I don’t think you have commit access, if you want to send a
diff of all the changes I can commit them.
And since the connection parameters seem to be what they should be, we still
don’t know why it’s not connecting. I don’t see any commands in the file to
cause anything to be logged to the web server logfiles. I could try to add
that, so that we could see what the error actually is, but that would probably
log a lot of stuff, since it would log once per hit, and the MacPorts web site
probably gets a lot of hits.
On Mar 17, 2014, at 16:15, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
I am a little confused, what is the complete path of the file you have listed
below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on the
server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in the
/etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to it
at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server and
tested access successfully. Restarted mysqld on the data server and
restarted httpd on the www server. I still can’t get to
https://www.macports.org/ports.php. There is something missing that I
can’t figure out.
The web site is trying to connect to a MySQL server running on localhost
(i.e. running on the same machine serving www.macports.org). Is the MySQL
server now running on a different server? If so, we need to plug its
address into the includes/common.inc file.
2) Ping issue: I have reopened the ticket which IST had resolved
earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge -
ICMP . Will let you know as soon as I find out.
3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine
you are probably referring to the deploy_archives.sh is failing for
Mavericks right? I have tried send a file via rsync with similar options
(-rlDzv) from build.macports to rsync.macports and it went through
successfully. I also did a su to user buildbot and sent a test file
through successfully. It did prompt me to accept the RSA key though. Can
you check if it has worked?
There is also a reference to use -e in the rsync options to pass ssh
options like the --ignore-existing” optionthat is being used in the
script. However the script has not changed 2013 so I am not sure it thats
an issue.
I meant that when I look at:
https://build.macports.org/console
the last revision it shows is r117767, whereas the last revision in the
repository right now is r117968. So it hasn’t tried to build any of the
200 most recent revisions.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [macosforge-leaders] Mac OS Forge Migration update
Hardcoded in /etc/hosts for some reason?
On Mar 17, 2014, at 16:47, Shreeraj Karulkar skarul...@apple.com wrote:
Can’t hellp thinking there must be some place referencing the old IP of
data.macports.org?
Shree
On Mar 17, 2014, at 2:15 PM, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
I am a little confused, what is the complete path of the file you have
listed below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on the
server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in the
/etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to it
at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server
and tested access successfully. Restarted mysqld on the data server and
restarted httpd on the www server. I still can’t get to
https://www.macports.org/ports.php. There is something missing that I
can’t figure out.
The web site is trying to connect to a MySQL server running on localhost
(i.e. running on the same machine serving www.macports.org). Is the MySQL
server now running on a different server? If so, we need to plug its
address into the includes/common.inc file.
2) Ping issue: I have reopened the ticket which IST had resolved
earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge -
ICMP . Will let you know as soon as I find out.
3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine
you are probably referring to the deploy_archives.sh is failing for
Mavericks right? I have tried send a file via rsync with similar options
(-rlDzv) from build.macports to rsync.macports and it went through
successfully. I also did a su to user buildbot and sent a test file
through successfully. It did prompt me to accept the RSA key though. Can
you check if it has worked?
There is also a reference to use -e in the rsync options to pass ssh
options like the --ignore-existing” optionthat is being used in the
script. However the script has not changed 2013 so I am not sure it
thats an issue.
I meant that when I look at:
https://build.macports.org/console
the last revision it shows is r117767, whereas the last revision in the
repository right now is r117968. So it hasn’t tried to build any of the
200 most recent revisions.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Ryan
Diff of which changes? Not sure what I should be sending you? The one thing I
have done is change its IP address, update the ldap-client (which I am having
some issues with but should not be related) and move the VM it to a new VLAN.
Shree
On Mar 17, 2014, at 2:53 PM, Ryan Schmidt ryandes...@macports.org wrote:
I see, so the file differs from what’s in our repository. Are there any other
uncommitted changes? Having uncommitted changes in the working copy on the
server would cause conflicts if we committed changes to similar lines of the
file. We should commit those changes to the repository so there are no
surprises. Since I don’t think you have commit access, if you want to send a
diff of all the changes I can commit them.
And since the connection parameters seem to be what they should be, we still
don’t know why it’s not connecting. I don’t see any commands in the file to
cause anything to be logged to the web server logfiles. I could try to add
that, so that we could see what the error actually is, but that would
probably log a lot of stuff, since it would log once per hit, and the
MacPorts web site probably gets a lot of hits.
On Mar 17, 2014, at 16:15, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
I am a little confused, what is the complete path of the file you have
listed below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on the
server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in the
/etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to it
at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server
and tested access successfully. Restarted mysqld on the data server and
restarted httpd on the www server. I still can’t get to
https://www.macports.org/ports.php. There is something missing that I
can’t figure out.
The web site is trying to connect to a MySQL server running on localhost
(i.e. running on the same machine serving www.macports.org). Is the MySQL
server now running on a different server? If so, we need to plug its
address into the includes/common.inc file.
2) Ping issue: I have reopened the ticket which IST had resolved
earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge -
ICMP . Will let you know as soon as I find out.
3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine
you are probably referring to the deploy_archives.sh is failing for
Mavericks right? I have tried send a file via rsync with similar options
(-rlDzv) from build.macports to rsync.macports and it went through
successfully. I also did a su to user buildbot and sent a test file
through successfully. It did prompt me to accept the RSA key though. Can
you check if it has worked?
There is also a reference to use -e in the rsync options to pass ssh
options like the --ignore-existing” optionthat is being used in the
script. However the script has not changed 2013 so I am not sure it
thats an issue.
I meant that when I look at:
https://build.macports.org/console
the last revision it shows is r117767, whereas the last revision in the
repository right now is r117968. So it hasn’t tried to build any of the
200 most recent revisions.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [macosforge-leaders] Mac OS Forge Migration update
I did get hit by one host with the /etc/hosts hardcoding, so I’ve even more
vigilant now.
[root@www /]# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost.localdomain localhost4
localhost4.localdomain4 localhost www
::1 localhost.localdomain localhost.localdomain localhost6
localhost6.localdomain6 localhost www
[root@www /]# uname -n
www.macports.org
[root@www /]#
===
On Mar 17, 2014, at 3:02 PM, Ryan Schmidt ryandes...@macports.org wrote:
Hardcoded in /etc/hosts for some reason?
On Mar 17, 2014, at 16:47, Shreeraj Karulkar skarul...@apple.com wrote:
Can’t hellp thinking there must be some place referencing the old IP of
data.macports.org?
Shree
On Mar 17, 2014, at 2:15 PM, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
I am a little confused, what is the complete path of the file you have
listed below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on
the server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in the
/etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to
it at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server
and tested access successfully. Restarted mysqld on the data server and
restarted httpd on the www server. I still can’t get to
https://www.macports.org/ports.php. There is something missing that I
can’t figure out.
The web site is trying to connect to a MySQL server running on localhost
(i.e. running on the same machine serving www.macports.org). Is the
MySQL server now running on a different server? If so, we need to plug
its address into the includes/common.inc file.
2) Ping issue: I have reopened the ticket which IST had resolved
earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge
- ICMP . Will let you know as soon as I find out.
3) Buildbot/Slaves: While all the build-slaves seem to be compiling
fine you are probably referring to the deploy_archives.sh is failing
for Mavericks right? I have tried send a file via rsync with similar
options (-rlDzv) from build.macports to rsync.macports and it went
through successfully. I also did a su to user buildbot and sent a test
file through successfully. It did prompt me to accept the RSA key
though. Can you check if it has worked?
There is also a reference to use -e in the rsync options to pass ssh
options like the --ignore-existing” optionthat is being used in the
script. However the script has not changed 2013 so I am not sure it
thats an issue.
I meant that when I look at:
https://build.macports.org/console
the last revision it shows is r117767, whereas the last revision in the
repository right now is r117968. So it hasn’t tried to build any of the
200 most recent revisions.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
In the Subversion repository, our common.inc says the host is localhost:
http://trac.macports.org/browser/trunk/www/includes/common.inc#L34
On the actual web server, you’ve told me common.inc says the host is
data.macports.org. There should not be any differences between the files in the
repository and the files on the web server, so I’m hoping you can run “svn
diff” in the www folder on the web server and send me the result so that I can
commit it to the repository so that there won’t be any differences anymore.
On Mar 17, 2014, at 17:02, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
Diff of which changes? Not sure what I should be sending you? The one thing I
have done is change its IP address, update the ldap-client (which I am having
some issues with but should not be related) and move the VM it to a new VLAN.
Shree
On Mar 17, 2014, at 2:53 PM, Ryan Schmidt ryandes...@macports.org wrote:
I see, so the file differs from what’s in our repository. Are there any
other uncommitted changes? Having uncommitted changes in the working copy on
the server would cause conflicts if we committed changes to similar lines of
the file. We should commit those changes to the repository so there are no
surprises. Since I don’t think you have commit access, if you want to send a
diff of all the changes I can commit them.
And since the connection parameters seem to be what they should be, we still
don’t know why it’s not connecting. I don’t see any commands in the file to
cause anything to be logged to the web server logfiles. I could try to add
that, so that we could see what the error actually is, but that would
probably log a lot of stuff, since it would log once per hit, and the
MacPorts web site probably gets a lot of hits.
On Mar 17, 2014, at 16:15, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
I am a little confused, what is the complete path of the file you have
listed below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on
the server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in the
/etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to
it at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server
and tested access successfully. Restarted mysqld on the data server and
restarted httpd on the www server. I still can’t get to
https://www.macports.org/ports.php. There is something missing that I
can’t figure out.
The web site is trying to connect to a MySQL server running on localhost
(i.e. running on the same machine serving www.macports.org). Is the
MySQL server now running on a different server? If so, we need to plug
its address into the includes/common.inc file.
2) Ping issue: I have reopened the ticket which IST had resolved
earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge
- ICMP . Will let you know as soon as I find out.
3) Buildbot/Slaves: While all the build-slaves seem to be compiling
fine you are probably referring to the deploy_archives.sh is failing
for Mavericks right? I have tried send a file via rsync with similar
options (-rlDzv) from build.macports to rsync.macports and it went
through successfully. I also did a su to user buildbot and sent a test
file through successfully. It did prompt me to accept the RSA key
though. Can you check if it has worked?
There is also a reference to use -e in the rsync options to pass ssh
options like the --ignore-existing” optionthat is being used in the
script. However the
Re: Mac OS Forge Migration update
If its not this please let me know, I’ll be more than happy to give you more
info.
—
[root@www includes]# pwd
/var/www/html/includes
[root@www includes]# ls
AcceptAbstract.class.php AcceptEncoding.class.php AcceptMime.class.php
footer.inc warnings.inc
AcceptCharset.class.php AcceptLanguage.class.php common.inc
header.inc
[root@www includes]# svn diff common.inc
Index: common.inc
===
--- common.inc (revision 114267)
+++ common.inc (working copy)
@@ -34,10 +34,10 @@
#
# Ports database connection parameters:
-$portsdb_host = 'localhost';
+$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
-$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
+$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
[root@www includes]#
On Mar 17, 2014, at 3:06 PM, Ryan Schmidt ryandes...@macports.org wrote:
In the Subversion repository, our common.inc says the host is localhost:
http://trac.macports.org/browser/trunk/www/includes/common.inc#L34
On the actual web server, you’ve told me common.inc says the host is
data.macports.org. There should not be any differences between the files in
the repository and the files on the web server, so I’m hoping you can run
“svn diff” in the www folder on the web server and send me the result so that
I can commit it to the repository so that there won’t be any differences
anymore.
On Mar 17, 2014, at 17:02, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
Diff of which changes? Not sure what I should be sending you? The one thing
I have done is change its IP address, update the ldap-client (which I am
having some issues with but should not be related) and move the VM it to a
new VLAN.
Shree
On Mar 17, 2014, at 2:53 PM, Ryan Schmidt ryandes...@macports.org wrote:
I see, so the file differs from what’s in our repository. Are there any
other uncommitted changes? Having uncommitted changes in the working copy
on the server would cause conflicts if we committed changes to similar
lines of the file. We should commit those changes to the repository so
there are no surprises. Since I don’t think you have commit access, if you
want to send a diff of all the changes I can commit them.
And since the connection parameters seem to be what they should be, we
still don’t know why it’s not connecting. I don’t see any commands in the
file to cause anything to be logged to the web server logfiles. I could try
to add that, so that we could see what the error actually is, but that
would probably log a lot of stuff, since it would log once per hit, and the
MacPorts web site probably gets a lot of hits.
On Mar 17, 2014, at 16:15, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
I am a little confused, what is the complete path of the file you have
listed below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on
the server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in
the /etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to
it at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org
wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server
and tested access successfully. Restarted mysqld on the data server
and restarted httpd on the www server. I still can’t get
Re: Python 3.4 support for ports
On 2014-03-03 21:11, Wahlstedt Jyrki wrote:
Can you use ’python3.4m-config’? It should give you the correct include
directories. (I looked at the patch-python3.diff, configure script seems to
take a simplistic view on directory naming:( )
Thanks for the hint. I learned now that the 'm' is called an abiflag and
is used to distinguish different python configurations. However, I don't
understand why this suddenly appears for python 3.4 now and is not
present in previous versions, although they also have this flag set:
$ python3.4 -c 'import sys; print(sys.abiflags);'
m
$ python3.3 -c 'import sys; print(sys.abiflags);'
m
The config dir also has the suffix for both 3.3 and 3.4:
$ python3.3-config --configdir
/opt/local/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/config-3.3m
$ python3.4m-config --configdir
/opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/config-3.4m
But there is no python3.3m-config, it is called python3.3-config.
I had tried to get this to work by including the ABI flag for the command:
${vi_cv_path_python3}${vi_cv_var_python3_abiflags}-config --ldflags
The configure script extracts these from the python interpreter. This
works for python34, but fails for python33 because they differ in the
way the ABI flags are exposed in the various commands.
How am I supposed to detect which flags I have to include for the
python3.*-config command?
Rainer
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Ok, I’ve committed that in r117979
Are there any other changes, i.e. outside of the includes directory?
On Mar 17, 2014, at 17:13, Shreeraj Karulkar skarul...@apple.com wrote:
If its not this please let me know, I’ll be more than happy to give you more
info.
—
[root@www includes]# pwd
/var/www/html/includes
[root@www includes]# ls
AcceptAbstract.class.php AcceptEncoding.class.php AcceptMime.class.php
footer.inc warnings.inc
AcceptCharset.class.php AcceptLanguage.class.php common.inc
header.inc
[root@www includes]# svn diff common.inc
Index: common.inc
===
--- common.inc(revision 114267)
+++ common.inc(working copy)
@@ -34,10 +34,10 @@
#
# Ports database connection parameters:
-$portsdb_host = 'localhost';
+$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
-$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
+$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
[root@www includes]#
On Mar 17, 2014, at 3:06 PM, Ryan Schmidt ryandes...@macports.org wrote:
In the Subversion repository, our common.inc says the host is localhost:
http://trac.macports.org/browser/trunk/www/includes/common.inc#L34
On the actual web server, you’ve told me common.inc says the host is
data.macports.org. There should not be any differences between the files in
the repository and the files on the web server, so I’m hoping you can run
“svn diff” in the www folder on the web server and send me the result so
that I can commit it to the repository so that there won’t be any
differences anymore.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
The only file that I usually change as part of network changes is the .conf
file inside the /etc/httpd/conf.d/ directory which usually is not a svn file.
In this case I didn’t not even have to change that since it had no IP
references inside it. I am not aware of any other changes.
[root@www conf.d]# ls -ld /etc/httpd/conf.d/www.macports.org.conf
-rw-r--r--. 1 root root 8783 Mar 3 14:57
/etc/httpd/conf.d/www.macports.org.conf
[root@www conf.d]# svn diff /etc/httpd/conf.d/www.macports.org.conf
svn: '/etc/httpd/conf.d/www.macports.org.conf' is not a working copy
[root@www conf.d]#
Shree
On Mar 17, 2014, at 4:18 PM, Ryan Schmidt ryandes...@macports.org wrote:
Ok, I’ve committed that in r117979
Are there any other changes, i.e. outside of the includes directory?
On Mar 17, 2014, at 17:13, Shreeraj Karulkar skarul...@apple.com wrote:
If its not this please let me know, I’ll be more than happy to give you more
info.
—
[root@www includes]# pwd
/var/www/html/includes
[root@www includes]# ls
AcceptAbstract.class.php AcceptEncoding.class.php AcceptMime.class.php
footer.inc warnings.inc
AcceptCharset.class.php AcceptLanguage.class.php common.inc
header.inc
[root@www includes]# svn diff common.inc
Index: common.inc
===
--- common.inc (revision 114267)
+++ common.inc (working copy)
@@ -34,10 +34,10 @@
#
# Ports database connection parameters:
-$portsdb_host = 'localhost';
+$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
-$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
+$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
[root@www includes]#
On Mar 17, 2014, at 3:06 PM, Ryan Schmidt ryandes...@macports.org wrote:
In the Subversion repository, our common.inc says the host is localhost:
http://trac.macports.org/browser/trunk/www/includes/common.inc#L34
On the actual web server, you’ve told me common.inc says the host is
data.macports.org. There should not be any differences between the files in
the repository and the files on the web server, so I’m hoping you can run
“svn diff” in the www folder on the web server and send me the result so
that I can commit it to the repository so that there won’t be any
differences anymore.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
