FS#18016 - [gnunet] needs a rebuild due to libextractor update
Attached to Project:
Community Packages
Opened by Andrea Scarpino (BaSh) - Tuesday, 26 January 2010, 14:04 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 26 January 2010, 22:23 GMT
Opened by Andrea Scarpino (BaSh) - Tuesday, 26 January 2010, 14:04 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 26 January 2010, 22:23 GMT
|
Details
Description:
Wed Jan 13 16:22:09 CET 2010 | libextractor v0.6.0 released. This release breaks backwards compatibility in terms of the APIs. Additional info: * libextractor 0.6.0-1 * gnunet 0.8.1-2 |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Tuesday, 26 January 2010, 22:23 GMT
Reason for closing: Fixed
Additional comments about closing: libextractor downgraded
Tuesday, 26 January 2010, 22:23 GMT
Reason for closing: Fixed
Additional comments about closing: libextractor downgraded
Comment by Sergej Pupykin (sergej) -
Tuesday, 26 January 2010, 15:31 GMT
Comment by Andrea Scarpino (BaSh) -
Tuesday, 26 January 2010, 15:33 GMT
Comment by Sergej Pupykin (sergej) -
Tuesday, 26 January 2010, 15:36 GMT
Comment by Sergej Pupykin (sergej) -
Tuesday, 26 January 2010, 15:46 GMT
Comment by Andrea Scarpino (BaSh) -
Tuesday, 26 January 2010, 15:55 GMT
Comment by Sergej Pupykin (sergej) -
Tuesday, 26 January 2010, 15:57 GMT
Comment by Andrea Scarpino (BaSh) -
Tuesday, 26 January 2010, 15:59 GMT
Comment by Sergej Pupykin (sergej) -
Tuesday, 26 January 2010, 16:12 GMT
gnunet's svn says now 'libextractor >= 0.5.20b and < 0.6.0',
so rebuild would not be easy...
should I downgrade libextractor or can we wait for a patch?
I'll try to patch it, but it takes some time and not sure about
result :)
it seems quite complex. It would be better to downgrade
libextractor...
ok...do you want to maintain libextractor in [community]?
Can not say that I want... I have ~1500 packages already :)
yes but only gnunet needs it and libextractor is orphan
ok, I can maintain it