On 2014-3-18 06:43 , Shreeraj Karulkar wrote:
>
> 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.macpo
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
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 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
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
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 AcceptLangu
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
reposi
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
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 wrote:
Hardcoded in /etc/hosts for some reason?
On Mar 17, 2014, at 16:47, Shreeraj Karulkar 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 wrote:
>
>> Ryan
>>
>> I am a litt
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 ar
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 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
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:
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 l
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 da
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
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
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
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
Completed
https://trac.macports.org/changeset/117933
On Mar 17, 2014, at 10:22, Ivan Larionov 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.
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
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 wrote:
> Thanks. The two pages are no
On Sat, Mar 15, 2014 at 2:31 PM, Ryan Schmidt 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/downlo
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 se
23 matches
Mail list logo
