Hi,
some files in libraries/fpdf/font seem to be corrupted in SVN. I mean trunk, MAINT_2_9_0 and QA_2_9.
To test this, I try to generate a PDF schema and get an error about FreeSansBold.
I can try to commit them from a known good source but anyone know why they could have been corrupted? The migration? but icons got migrated fine.
Marc
Hi
On Wed, 25 Oct 2006 11:01:03 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
some files in libraries/fpdf/font seem to be corrupted in SVN. I mean trunk, MAINT_2_9_0 and QA_2_9.
To test this, I try to generate a PDF schema and get an error about FreeSansBold.
I can try to commit them from a known good source but anyone know why they could have been corrupted? The migration? but icons got migrated fine.
Maybe they didn't have correct flags in CVS?
--On Wednesday, October 25, 2006 5:27 PM +0200 "Michal?iha?" michal@cihar.com wrote:
Maybe they didn't have correct flags in CVS?
CVS defaults to ASCII, while SVN defaults to binary. So if a CVS file lacks a binary flag, it gets imported as ASCII and things that look like line endings are likely to get munged.
Kenneth Porter a écrit :
--On Wednesday, October 25, 2006 5:27 PM +0200 "Michal?iha?" michal@cihar.com wrote:
Maybe they didn't have correct flags in CVS?
CVS defaults to ASCII, while SVN defaults to binary. So if a CVS file lacks a binary flag, it gets imported as ASCII and things that look like line endings are likely to get munged.
I'm trying to fix the problem with removing the files, copying them from a known good source and adding them (FreeSansBold.ctg.z is not recognized as being bin). Then I do
svn propset svn:mime-type 'application/octet-stream' FreeSansBold.ctg.z
but I have problems committing. I must leave now, I'll continue on Tuesday.
Marc
Hi
On Fri, 27 Oct 2006 07:26:18 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
I'm trying to fix the problem with removing the files, copying them from a known good source and adding them (FreeSansBold.ctg.z is not recognized as being bin). Then I do
svn propset svn:mime-type 'application/octet-stream' FreeSansBold.ctg.z
but I have problems committing.
Eh? You did the commits :-).
--On Friday, October 27, 2006 7:26 AM -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
Then I do
svn propset svn:mime-type 'application/octet-stream' FreeSansBold.ctg.z
but I have problems committing.
What was the problem?
Kenneth Porter a écrit :
--On Friday, October 27, 2006 7:26 AM -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
Then I do
svn propset svn:mime-type 'application/octet-stream' FreeSansBold.ctg.z
but I have problems committing.
What was the problem?
I don't have the exact error message but it said that the commit was not complete. Maybe because Michal and I were working on the same files at the same time.
I just exported and the files are correct so tomorrow I'll release 2.9.0.3 and 2.9.1-rc2 (from a new MAINT_2_9_1 branch).
Marc
On Tue, 31 Oct 2006 20:50:55 -0500 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
I don't have the exact error message but it said that the commit was not complete. Maybe because Michal and I were working on the same files at the same time.
I doubt it could be concurrent access problem, svn handles this fine.
However I sometimes get following error:
Transmitting file data .....svn: Commit failed (details follow): svn: MERGE request failed on '/svnroot/phpmyadmin/trunk/phpMyAdmin' svn: MERGE of '/svnroot/phpmyadmin/trunk/phpMyAdmin': 500 Internal Server Error (https://svn.sourceforge.net) svn: Your commit message was left in a temporary file: svn: '/home/mic/private/phpMyAdmin/svn-commit.tmp'
The changes seem to be commited in repository, but my local tree is not updated and I have to run svn up manually.
Michal Čihař a écrit :
On Tue, 31 Oct 2006 20:50:55 -0500 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
I don't have the exact error message but it said that the commit was not complete. Maybe because Michal and I were working on the same files at the same time.
I doubt it could be concurrent access problem, svn handles this fine.
However I sometimes get following error:
Transmitting file data .....svn: Commit failed (details follow): svn: MERGE request failed on '/svnroot/phpmyadmin/trunk/phpMyAdmin' svn: MERGE of '/svnroot/phpmyadmin/trunk/phpMyAdmin': 500 Internal Server Error (https://svn.sourceforge.net) svn: Your commit message was left in a temporary file: svn: '/home/mic/private/phpMyAdmin/svn-commit.tmp'
The changes seem to be commited in repository, but my local tree is not updated and I have to run svn up manually.
Indeed, svn update fixed my local tree.
Marc
--On Thursday, November 02, 2006 3:07 PM +0100 "Michal?iha?" michal@cihar.com wrote:
The changes seem to be commited in repository, but my local tree is not updated and I have to run svn up manually.
If I understand correctly, you're saying that the WC isn't updated to indicate that it's no longer out-of-date.
What version of client and server is involved? (Does SF say what server version they use? Is it 1.4, and do they use BDB or FSFS for the back end?) I'd recommend reporting all that on the subversion-users list.
Kenneth Porter a écrit :
--On Thursday, November 02, 2006 3:07 PM +0100 "Michal?iha?" michal@cihar.com wrote:
The changes seem to be commited in repository, but my local tree is not updated and I have to run svn up manually.
If I understand correctly, you're saying that the WC isn't updated to indicate that it's no longer out-of-date.
What version of client and server is involved? (Does SF say what server version they use? Is it 1.4, and do they use BDB or FSFS for the back end?) I'd recommend reporting all that on the subversion-users list.
My client is 1.3.1, I don't know about their server. If it happens again I'll take notes about the exact error message; this will make a better error report. Hmmm, maybe I should first upgrade my client :)
Marc
Hi
On Thu, 02 Nov 2006 16:35:47 -0800 Kenneth Porter shiva@sewingwitch.com wrote:
If I understand correctly, you're saying that the WC isn't updated to indicate that it's no longer out-of-date.
Exactly... because svn things commit went wrong. But it actually didn't.
What version of client and server is involved? (Does SF say what server version they use? Is it 1.4, and do they use BDB or FSFS for the back end?) I'd recommend reporting all that on the subversion-users list.
I'm using client 1.4.0, don't have idea about server...
On Monday, November 06, 2006 5:03 PM +0100 MichalČihař michal@cihar.com wrote:
Exactly... because svn things commit went wrong. But it actually didn't.
FWIW, I've seen a couple of crashes in the 1.4.0 Win32 client after a lengthy server transaction completed successfully. They seem to be in the APR hash that holds translation handles for console output translation. For instance, following a successful commit the svn.exe client crashed preparing the "successfully committed" message to send to the console. I haven't yet got a repeatable one that would let me properly debug it. What I've figured out has been from post-mortem dumps.
Hi
On Wed, 25 Oct 2006 11:01:03 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
I can try to commit them from a known good source but anyone know why they could have been corrupted? The migration? but icons got migrated fine.
Looks like we both got to this issue at same time :-). The reason was that those files didn't have binary flag in CVS and thus were converted as text to SVN. It didn't matter to CVS as it did only keywords replacement, which were none in the file. With SVN and automatic EOL feature, it got broken.
While I was digging in that I also checked other files and all other seems to be okay, I only set better MIME type for images (maybe some SVN frontend can make use of that).
-
Kenneth Porter -
Marc Delisle -
Michal Čihař