Send Netdot-devel mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."


Today's Topics:

   1. [Netdot - Bug #1706] (New) Upgrade 0.9.10 to 1.0.2
      ([email protected])


----------------------------------------------------------------------

Message: 1
Date: Mon, 19 Nov 2012 00:08:20 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1706] (New) Upgrade 0.9.10 to
        1.0.2
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1706 has been reported by Alen F.

----------------------------------------
Bug #1706: Upgrade 0.9.10 to 1.0.2
https://osl.uoregon.edu/redmine/issues/1706

Author: Alen F
Status: New
Priority: Normal
Assignee: 
Category: 
Target version: 
Resolution: 


hello,

i cannot upgrade my database to 1.0.2. Following error occured.

cd upgrade; make all DIR=upgrade
make[1]: Entering directory `/home/netdot/netdot-1.0.2/upgrade'

Upgrading schema and data...
/usr/bin/perl updatedb 2>error.log
DEBUG: init: dbi:mysql:dbname=netdot;host=localhost;mysql_local_infile=1
make[1]: *** [db] Error 255
make[1]: Leaving directory `/home/netdot/netdot-1.0.2/upgrade'
make: *** [upgrade] Error 2



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://osl.uoregon.edu/redmine/my/account


------------------------------

_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel


End of Netdot-devel Digest, Vol 68, Issue 3
*******************************************

Reply via email to