I'm seeing this error with tdelibs. I updated GIT this morning but saw the same error yesterday after updating GIT.
/dev/shm/tdelibs/dcop/dcopidl2cpp/main.cpp:44: error: 'qVersion' was not declared in this scope /dev/shm/tdelibs/dcop/dcopidl2cpp/main.cpp:96: error: 'qFatal' was not declared in this scope
I can patch the problem by adding the "t" prefix: tqVersion, tqFatal, etc.
But with each patch a new error appears. For example, qWarning -> tqWarning, qt_xrootwin -> tqt_xrootwin, qt_xdisplay -> tqt_xdisplay, qDebug -> tqDebug, qt_use_xrender -> tqt_use_xrender, etc.
TQt3, tqtinterface, arts and other dependencies build without failure.
Darrell
I'm seeing this error with tdelibs. I updated GIT this morning but saw the same error yesterday after updating GIT.
/dev/shm/tdelibs/dcop/dcopidl2cpp/main.cpp:44: error: 'qVersion' was not declared in this scope /dev/shm/tdelibs/dcop/dcopidl2cpp/main.cpp:96: error: 'qFatal' was not declared in this scope
I can patch the problem by adding the "t" prefix: tqVersion, tqFatal, etc.
But with each patch a new error appears. For example, qWarning -> tqWarning, qt_xrootwin -> tqt_xrootwin, qt_xdisplay -> tqt_xdisplay, qDebug -> tqDebug, qt_use_xrender -> tqt_use_xrender, etc.
TQt3, tqtinterface, arts and other dependencies build without failure.
Darrell
GIT contains the t* prefixes (see http://git.trinitydesktop.org/cgit/tdelibs/tree/dcop/dcopidl2cpp/main.cpp for an example), so something must be preventing an update on your end. Does GIT spew any warning messages? If you don't have any local changes in your GIT tree, you could always try this command:
git reset --hard HEAD
to reset the tree to a pristine state.
Tim
GIT contains the t* prefixes (see http://git.trinitydesktop.org/cgit/tdelibs/tree/dcop/dcopidl2cpp/main.cpp for an example), so something must be preventing an update on your end. Does GIT spew any warning messages? If you don't have any local changes in your GIT tree, you could always try this command:
git reset --hard HEAD
to reset the tree to a pristine state.
That did not work, nor did other commands I found around the web, but I found the problem.
Administrative Summary: GIT sucks. Oh, wait, many of us already knew that. :)
Every module that I have modified through commits, which now require an account name and password, have not been updating.
Is there a way to anonymously sync a local repository after a module's config file is set to use an account name?
Yes, I know about GIT_ASKPASS, but a local sync should not require a password. I understand needing a password to commit changes but to synchronize locally should not.
Darrell
On Mon, 5 Mar 2012 14:39:55 -0800 (PST) Darrell Anderson humanreadable@yahoo.com wrote:
GIT contains the t* prefixes (see http://git.trinitydesktop.org/cgit/tdelibs/tree/dcop/dcopidl2cpp/main.cpp for an example), so something must be preventing an update on your end. Does GIT spew any warning messages? If you don't have any local changes in your GIT tree, you could always try this command:
git reset --hard HEAD
to reset the tree to a pristine state.
That did not work, nor did other commands I found around the web, but I found the problem.
Administrative Summary: GIT sucks. Oh, wait, many of us already knew that. :)
Every module that I have modified through commits, which now require an account name and password, have not been updating.
Is there a way to anonymously sync a local repository after a module's config file is set to use an account name?
Yes, I know about GIT_ASKPASS, but a local sync should not require a password. I understand needing a password to commit changes but to synchronize locally should not.
From Gitorious help: ----- Adding this repository as a pushable origin:
# Add the push url to your already existing origin: git remote set-url --push origin git@gitorious.org:$project/$repo.git # to push the master branch to the origin remote we added above: git push origin master # after that you can just do: git push
Cloning this repository:
git clone git://gitorious.org/$project/$repo.git $repo cd $repo
Add this repository as a remote to an existing local repository:
git remote add $repo git://gitorious.org/$project/$repo.git git fetch $repo git checkout -b my-local-tracking-branch $repo/master_or_other_branch ----- so apparently you can use both an anonymous url to pull and your identified one to push.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
/dev/ammo42 -
Darrell Anderson -
Timothy Pearson