Ricardo Wurmus <rek...@elephly.net> writes: > ng0 <n...@libertad.pw> writes: > >> ng0@wasp ~$ cd src/guix/guix >> ng0@wasp ~/src/guix/guix$ git grep googlecode >> gnu/packages/key-mon.scm: >> "http://key-mon.googlecode.com/files/key-mon-"; >> >> >> Are we done then and we only need to find the right source for >> key-mon if there is a new one? > > There’s more: > > $ grep -r 'code\.google' gnu/packages > > gnu/packages/key-mon.scm: (home-page "http://code.google.com/p/key-mon";) > gnu/packages/scheme.scm: (home-page > "https://code.google.com/p/chibi-scheme/";)
I will update Chibi's recipe promptly. It's on GitHub by now. > gnu/packages/python.scm: (home-page "https://code.google.com/p/py-bcrypt";) > gnu/packages/python.scm: (home-page "http://code.google.com/p/mock/";) > gnu/packages/python.scm: (home-page > "https://code.google.com/archive/p/socksipy-branch/";) > gnu/packages/python.scm: (home-page > "http://code.google.com/p/prettytable/";) > gnu/packages/java.scm: > "code.google.com/jarjar/jarjar-src-" version ".zip")) > gnu/packages/java.scm: (home-page > "https://code.google.com/archive/p/jarjar/";) > gnu/packages/boost.scm: (home-page > "https://code.google.com/p/multidimalgorithm/";) > gnu/packages/image.scm: ;; > https://code.google.com/p/tesseract-ocr/issues/detail?id=1436 Trying to access the link, I get a page saying Tesseract moved to GitHub as well. After a bit of struggling I managed to find a link to the archived issue report in JSON format: https://www.googleapis.com/storage/v1/b/google-code-archive/o/v2%2Fcode.google.com%2Ftesseract-ocr%2Fissues%2Fissue-1436.json?alt=media Apparently the report was closed at some point, and I think Leptonica also fixed the issue on the meanwhile. I'll see that I update the recipe suitably... > gnu/packages/games.scm: > "google-code-archive-downloads/v2/code.google.com/" > gnu/packages/games.scm: (home-page > "http://code.google.com/p/abbaye-for-linux/";) > gnu/packages/openstack.scm:(http://code.google.com/p/pymox/) to Python 3. It > was meant to be as compatible > gnu/packages/fontutils.scm: > "code.google.com/ttf2eot/" > gnu/packages/fontutils.scm: (home-page > "https://code.google.com/archive/p/ttf2eot/";))) > gnu/packages/patches/ttf2eot-cstddef.patch:From resolution of > https://code.google.com/p/ttf2eot/issues/detail?id=26 > gnu/packages/bioinformatics.scm: (home-page > "https://code.google.com/p/cutadapt/";) > gnu/packages/bioinformatics.scm: (home-page > "https://code.google.com/p/mosaik-aligner/";) > gnu/packages/bioinformatics.scm: (home-page > "https://code.google.com/p/pepr-chip-seq/";) > > Most of them are home page fields (will they also disappear?), but there > are some where the sources are affected. >From a bit of Googling I can't find any info on whether the homepages will still be available either... - Taylan, trying to at least maintain the packages he added!
