| 1 |
Hi all, |
| 2 |
|
| 3 |
There are a number of bugs about packages that are part of suitesparse |
| 4 |
in bugzilla. It strikes me that all the versions in portage are rather |
| 5 |
old. The various packages were last touched by bicatali and he split |
| 6 |
the main suite sparse tarball into its components and autotooling |
| 7 |
each one of them. Lots of work. |
| 8 |
There is another problem with that |
| 9 |
$ wget https://dev.gentoo.org/~bicatali/distfiles/amd-2.3.1.tar.bz2 |
| 10 |
--2019-03-18 22:46:02-- https://dev.gentoo.org/~bicatali/distfiles/amd-2.3.1.tar.bz2 |
| 11 |
Resolving dev.gentoo.org... 140.211.166.183, 2001:470:ea4a:1:5054:ff:fec7:86e4 |
| 12 |
Connecting to dev.gentoo.org|140.211.166.183|:443... connected. |
| 13 |
HTTP request sent, awaiting response... 404 Not Found |
| 14 |
2019-03-18 22:46:03 ERROR 404: Not Found. |
| 15 |
|
| 16 |
It’s all gone. Luckily we have the tarball on mirror but the dev-space |
| 17 |
that is the SRC_URI for the tarball is gone. |
| 18 |
|
| 19 |
I am volunteering to do some maintenance on those package, starting with |
| 20 |
updating everything to suitesparse 5.4.0. I have started working on this. |
| 21 |
But I am realising that if I go the same way as bicatali, I’ll need some |
| 22 |
dev space myself. I have a resource right now, tied to sage but I don’t |
| 23 |
know how long it will last. Suggestions welcome. |
| 24 |
|
| 25 |
My current plan is development in sage-on-gentoo and once it looks OK |
| 26 |
I’ll want assistance in shepherding a branch with all the ebuilds |
| 27 |
together in the tree. Hopefully, the next updates won’t be as painful. |
| 28 |
|
| 29 |
François |
Archives