Marius Bakke <[email protected]> writes: > Adonay Felipe Nogueira <[email protected]> writes: > >> I can't work on this issue right now, but I can at least do some >> preliminary listing of affected recipes, so here's a small contribution >> (although some removal of false-positives must be done): >> >> From root of git repository (binary matches removed). >> >> $ grep -r 'googlecode' > > Thanks for the list! > > Here's a pro tip: `git grep` is recursive by default and excludes the > .git directory :) > > Patches to update any of these welcome.
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? >> gnu/packages/key-mon.scm: >> "http://key-mon.googlecode.com/files/key-mon-"; >> >> $ grep -r 'code\.google' >> 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/";) >> 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/protobuf.scm: (home-page >> "http://code.google.com/p/protobuf/";) >> 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/scheme.scm: (home-page >> "https://code.google.com/p/chibi-scheme/";) >> gnu/packages/boost.scm: (home-page >> "https://code.google.com/p/multidimalgorithm/";) >> gnu/packages/key-mon.scm: (home-page >> "http://code.google.com/p/key-mon";) >> gnu/packages/image.scm: ;; >> https://code.google.com/p/tesseract-ocr/issues/detail?id=1436 >> gnu/packages/mtools.scm: (home-page >> "https://code.google.com/p/exfat";) >> gnu/packages/fontutils.scm: >> "code.google.com/ttf2eot/" >> gnu/packages/fontutils.scm: (home-page >> "https://code.google.com/archive/p/ttf2eot/";))) >> gnu/packages/openstack.scm:(http://code.google.com/p/pymox/) to Python >> 3. It was meant to be as compatible >> gnu/packages/patches/ttf2eot-cstddef.patch:From resolution of >> https://code.google.com/p/ttf2eot/issues/detail?id=26 >> gnu/packages/linux.scm: (home-page "http://code.google.com/p/exfat/";) >> doc/guix.texi:@url{http://code.google.com/p/cryptsetup,Linux Unified Key >> Setup}, a -- ♥Ⓐ ng0 | ng0.chaosnet.org
