My node was experiencing a strange error in which the manifests of directory uploads were corrupted but single file uploads functioned correctly. Troubleshooting with developer saces on the #freenet freenode channel revealed the problem to be ant-core-1.8. Freenet is developed with ant 1.7. Downgrading ant-core to ant-core-1.7.1-r4 resolved the upload problems. Reproducible: Always Steps to Reproduce:
Fixed with freenet-0.7.5_p1263-r1 You will find it on your local rsync mirror in a few hours,
(In reply to comment #1) > Fixed with freenet-0.7.5_p1263-r1 > You will find it on your local rsync mirror in a few hours, > freenet-9999 as well?
(In reply to comment #2) > (In reply to comment #1) > > Fixed with freenet-0.7.5_p1263-r1 > > You will find it on your local rsync mirror in a few hours, > > > > freenet-9999 as well? > Missed it, done now. Be warned, this will only downgrade ant-core, but not other ant-* packages. You might have to do that with the help of package.mask (i had issues with ant-nodeps not being the same minor version as ant-core).
1293 has same problem with ant
(In reply to comment #4) > 1293 has same problem with ant > Did you just want to report it or did you manually upgrade ant, also freenet requires 1.7* version of it?
I edit ebuild of net-p2p/freenet-0.7.5_p1308 and compile then with ant-core-1.8.1
This resolution is quite bad in the long term :( freenet should be made compatible with new ant. This also leads to bugs such as bug 353613 (which seems to me also to be a portage bug, I'm asking zmedico). According to comment 6, ant-core-1.8.1 works ?
No, nothing has changed on this topic. ant-core-1.8* still causes corruption of directory uploads as reported originally. This does of course not show up at compile time or when you download something else or just upload simple files, so while comment 6 is true (it does compile with ant-core-1.8*), it doesnt show, that the issue itself is fixed. And since freenet (like many other java projects) also uses bundled jars including a bundled jar for ant-core, noone else does see this issue and fixing it isnt a high priority for upstream.
OK, I will try build it with 1.7.1 and 1.8.1 and diff the result... Could be some trivial fix in the end.
After some talk on IRC, Caster and i got to the conclusion, that it might be the best for now to include a prebuilt ant.jar from ant-core-1.7.1. Upstream of freenet is made aware of this problem, but since they ship their own jars with freenet and their binary blob hasnt been updated for a long time, i dont see a chance, this will change in the near future. This change will remove the force on java team to keep an older version of ant-core in tree and to support it. I removed the latest version of freenet depending on ant-core-1.7* today, so while the problem itself still exists and has to be fixed upstream, i hope this workaround is now accepted by involved parties. Setting resolution to upstream, since they have to fix this finally.
Is freenet-0.7.5_p1352.ebuild still supposed to have =dev-java/ant-core-1.7* in CDEPEND?
(In reply to comment #11) > Is freenet-0.7.5_p1352.ebuild still supposed to have =dev-java/ant-core-1.7* in > CDEPEND? > Thanks for the catch, i missed the removal. Ebuilds are updated now and should be synced on your local mirror in a few hours.
